![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
Use the @CONFIGURESERVER tool to set and modify the configuration parameters. Execute the following from the workbench:
Command ==> Scroll P
NUMBER SERVERTYPE SERVERID
----------- ---------- --------
_ 1 ADA ANDY
_ 2 ADA EXTRACT
_ 3 ADA IMZADA
_ 4 ADA SUB
A-ADD D-DELETE S-SELECT
PFKEYS: 12=EXIT 13=PRINT 3=END 5=FIND NEXT 9=RECALL
1. Type A beside an existing entry on the screen and use Enter.A screen similar to the one shown below appears, prompting you to enter a value into the SERVERTYPE and SERVERID fields.
To complete this command:
NUMBER SERVERTYPE SERVERID
----------- ---------- --------
A 1 ADA ADA001
Enter parameter(s):
SERVERTYPE ===> ADA
SERVERID ===> EXTRACT
PFKEYS: ENTER=PROCESS 3=PROCESS 12=CANCEL
3. Type the server ID for which you want to set the configuration parameters and press Enter. A default configuration settings screen appears similar to the one shown below.
External Server Configuration Utility
COMMAND ==>
Server Type: ADA Server ID: EXTRACT
Recommended/
Name Value Allowed Values
---------------- -------------------------------------------- -------------------
DEBUGLEVEL 0 '0...3'
DUMP N Y, N
DUMPLIMIT 512 '0...2147483647'
EXTERNALROUTINE ADALNK
KEEPLOG N Y, N
LOGMEDIA TBL TBL, SCR, PRT
PROGRAMLIBRARY EXL EXL, SMG
RUNAWAY 0 '0...2147483647'
SERVERSTATISTICS N Y, N
TRACE N Y, N
FCNKEYS: ENTER=VALIDATE 3=SAVE & EXIT 12=EXIT
Valid values are shown in the Recommended/Allowed Values field. Refer to Available Configuration Parameters for parameter descriptions.
If the server you are modifying is active, it must be recycled for the new values to be applied. Refer to TIBCO Object Service Broker for z/OS Installing and Operating for instructions on recycling.Use the @CONFIGURESERVER tool for customization according to the server ID. To modify the load point and the name of the Adabas interface module, add an entry for a server type of ADA and a server ID that identifies the server to be customized, and then set the appropriate values for the module.For example, you can customize the Adabas extract utility by using @CONFIGURESERVER to add an entry for a server type of ADA and a server ID of EXTRACT, and then set the values appropriate for the interface module to be used to issue Adabas LF commands.Refer to Configuration Parameters for more information on using the @CONFIGURESERVER tool.
Used during problem analysis to determine which portion of code is in error. Valid values are listed below. The default is 0.0 – Used during normal processing.1 – Produces TRACE and/or DUMP information if they are selected. DUMP information shows the Adabas control blocks after the call to ADALNK.2 – Produces TRACE and/or DUMP information if they are selected. DUMP information shows the Adabas control blocks before and after the call to ADALNK.3 – Produces TRACE and/or DUMP information if they are selected. DUMP information shows the Adabas control blocks before and after the call to ADALNK; ESTAE and ADALNK are not called. Specifies whether Adabas messages and control blocks should be logged (in the location specified in the LOGMEDIA configuration parameter). Valid values are listed below. The default is N.Y – Both TIBCO Object Service Broker and Adabas messages and control blocks are logged.N – No logging is in effect. Specifies the amount (in bytes) of TIBCO Object Service Broker and Adabas messages and control blocks that can be logged. The default is 512 bytes. Valid values are between 0 and 2147483647 bytes. Specifies the name of the load module that provides the ADALNK functionality. The default is ADALNK. Specifies whether to keep the previous server login startup. This applies only if the LOGMEDIA configuration parameter is set to TBL. Valid values are listed below. The default is N.Y – The log that matches the current server type, server ID, and server user ID is deleted on startup.N – The log that matches the current server type, server ID, and server user ID is kept on startup. Subsequent logs are appended. Specifies where to store DUMP, TRACE, and error message information. Valid values are listed below. The default is TBL.PRT – DUMP, TRACE, and error message information is sent to the default print file for the TIBCO Object Service Broker user ID. Set the desired print destination with the UP user profile option on the workbench.SCR – DUMP, TRACE, and error message information appears in the session.log file. This can be viewed only after the server is shut down.TBL – DUMP, TRACE, and error message information is inserted into the @SERVERLOG TDS table, which is parameterized by the servertype, server ID, and server user ID. You can browse this table while the server is running.
• The server type is always ADA for Adabas data, and is specified by the SERVERTYPE startup parameter.
• The server user ID is the thread ID used by the transaction specified by the IDPREFIX startup parameter. It is generated and consists of the IDPREFIX concatenated with four characters derived from the server number.The Data Object Broker log displays the servertype (ADA), server ID (ADANT), and server user ID (ADAB0001) in the S6BUA023I message as follows: Specifies where the routine named by EXTERNALROUTINE is loaded from. Valid values are listed below. The default is EXL.EXL – DD statement HRNEXTRSMG – Standard z/OS load library search path conventions STEPLIB, JOBLIB, LINKLIB, and LPA Specifies the maximum number of calls to Adabas that can be issued to satisfy one TIBCO Object Service Broker request. Valid values are between 0 and 2147483647 bytes. The default is 0.Use this feature in development to test access statements in the application code. When the limit is exceeded, the request is terminated with a SERVERERROR exception passing back an appropriate error message, and a message is written to the @SERVERLOG table. A value of 0 disables this parameter. Controls how the server transaction is managed. Valid values are listed below. The default is N.Y – Transactions are recycled at the end of the TIBCO Object Service Broker transaction.N – An endless TIBCO Object Service Broker transaction runs.For best performance, do not change the default of N, since this transaction is independent of the client transaction. Specifies whether TIBCO Object Service Broker requests and Adabas statements should be logged (in the location specified in the LOGMEDIA configuration parameter). Valid values are listed below. The default is N.Y – Both TIBCO Object Service Broker requests and Adabas statements are logged.N – No logging is in effect.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |