Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 2 Operating Service Gateway for IDMS/DB : Supplying Service Gateway for IDMS/DB Startup Parameters

Supplying Service Gateway for IDMS/DB Startup Parameters
You must specify the gateway parameters in the SYSIN member associated with DDname IDMSSRV0. For more information on how to specify the gateway parameters, refer to Specifying Service Gateway for IDMS/DB Parameters.
Available Parameters
Available parameters are listed below:
 
Specify that debugging messages (the type of request and the TIBCO Object Service Broker transaction number) should be echoed on the Gateway and placed in the JES job log for batch jobs and appear on the console for started tasks. At normal transaction end, the physical I/O count from the CA‑IDMS statistics block also appears.
 
Has meaning only if SECLEVEL=1, an external security package is used to verify user IDs against subschemas and/or areas, and you have the TIBCO Object Service Broker external security interface macros installed. The TIBCO Object Service Broker session ID or the current security group is passed to an external security package (for example, CA-ACF2) to verify access to subschemas and/or areas. The default is EXTERNAL.
If CA-ACF2 security is used, the Gateway must be installed and executed from an authorized library. For CA‑IDMS Release 12.0 and greater, the TIBCO Object Service Broker external security interface can use any CA‑IDMS supported external security package.
 
Has meaning only if SECLEVEL=1. Specifies the ID to be used for external security validation. The default is USERID.
 
Note  Ensure that all security groups used to verify CA‑IDMS resources are between one and eight characters long. A SECURITYFAIL occurs for more than eight characters.
 
 
Activate Fail Safe Level 1. The Gateway informs the Data Object Broker that it can support Fail Safe level‑1 processing. If the Gateway is to attach to a z/OS Data Object Broker, the Data Object Broker’s connection attribute setting “commit level” must be set to 1. If not, the Gateway connection is rejected. Refer to Implementing Fail Safe Processing for more information.
De-activate Fail Safe processing. The Gateway informs the Data Object Broker that it does not support Fail Safe level‑1 processing. If the Gateway is to attach to a z/OS Data Object Broker, the Data Object Broker’s connection attribute setting “commit level” must be set to 0. If not, the Gateway connection is rejected. Refer to Implementing Fail Safe Processing for more information.
 
Required only if FSLEVEL=1. Specifies the name of the IDM table that maps to the CA‑IDMS transaction file. The default is @IDMFSTRXDB.
 
 
Each instance of TIBCO Service Gateway for IDMS/DB must have a unique IDPREFIX. The Gateway appends two decimal digits to the prefix to create a unique name for each instance of TIBCO Service Gateway for IDMS/DB, and uses the result to log in to TIBCO Object Service Broker. This parameter must have four characters; the default is IDMS.
 
Only one subschema can be actively accessed per transaction. If multiple subschemas are found to be referenced in processing multiple IDM type tables, the gateway takes the following action, depending on the value specified or defaulted for this parameter. The values are as follows:
I – Ignore this condition.
W – Display a message in the gateway log on the discrepancy but allow the transaction to continue. This value is the default.
E – Display the message in the gateway log and end the transaction with an error.
 
The pattern for selecting the VTAM ACB name that the Gateway uses for communications. If not specified, the Gateway uses the TDS parameter as the pattern. If you do not specify the MDL parameter, ensure that the TDS parameter is a valid VTAM ACB model. For example, if TDS=HRN001 and you do not include an MDL parameter, the model HRNnnn is used.
 
 
Set the amount of space (in kilobytes) to hold IDM table definitions in each instance of TIBCO Service Gateway for IDMS/DB. This parameter can be up to a maximum of 16384 KB. The default value is 256 KB. An estimate of the number of IDM tables that can be accessed in a single transaction is POOLSIZE divided by CTABLESIZE. Refer to Estimating the CTABLESIZE Parameter for more information.
 
The mode that the Gateway uses to respond to requests. You can use this mode to free up a Gateway more quickly for a new transaction in read-only situations. For use only with a Data Object Broker on z/OS. The default is ASYNC. Valid entries:
 
The Data Object Broker releases the Gateway from the TIBCO Object Service Broker transaction when the end-of-transaction request is sent, provided no updates are requested. The next transaction can then be scheduled before the previous transaction is completed. ASYNC is recommended for online Gateways. If SYNC is used, performance can be affected.
Causes the Data Object Broker to wait for the Gateway to complete end-of-transaction processing. SYNC is recommended for Gateways running in batch mode.
 
 
If an external security package is used to verify user IDs against subschemas and/or areas:
The user ID that submits the Gateway job is used for the Gateways running as batch jobs.
If program registration is used to verify access to subschemas, the TIBCO Object Service Broker session ID or current security group name is used as the program ID.
If an external security package is used to verify user IDs against subschemas and/or areas and the TIBCO Object Service Broker external security interface macros are not installed:
The user ID that submits the Gateway job is used for the Gateways running as batch jobs.
If an external security package is used to verify user IDs against subschemas and/or areas, and the TIBCO Object Service Broker external security interface macros are installed, you must specify EXTERNALSECURITY=EXTERNAL; this means the TIBCO Object Service Broker session ID or current security group name is used as the user ID.
 
Identify a pool of the Gateways with common characteristics. If you have multiple TIBCO Object Service Broker IDMS/DB initializer programs with the same SERVERID, ensure that the FSLEVEL and FSTABLENAME or TRXDB gateway parameters have the same values for each initializer program. This parameter can be up to eight characters; the default is DEFAULT.
 
The number of the Gateway tasks that the TIBCO Object Service Broker IDMS/DB initializer program should attach to the Gateway address space at startup. If running the Gateway in Local mode, only one task is available. If accessing data through the Central Version, this number can be from 1 to a value less than or equal to the value set in the Maximum Connection Count field in your Network Configuration. The default value is 3. Refer to Adding the Gateway Tasks or the TIBCO Object Service Broker for z/OS Installing and Operating manual for more information.
 
 
Required only if FSLEVEL=1. Specifies the name of the CA‑IDMS subschema that defines the CA‑IDMS transaction ID database. The default is HRNSS001.
 
If you have multiple TIBCO Object Service Broker IDMS/DB initializer programs with the same SERVERID, the FSLEVEL and FSTABLENAME or TRXDB parameters must have the same values for each initializer program.
Estimating the CTABLESIZE Parameter
When you select CA‑IDMS elements as TIBCO Object Service Broker IDMS/DB fields, the number of fields you can access using an IDM table definition is dependent upon the CTABLESIZE Data Object Broker parameter. To estimate the number of bytes required to support a specified number of fields, invoke the ESTIMATETBLDFN shareable tool from the workbench as follows:
ESTIMATETBLDFN(num_fields)
You must supply one argument, the maximum number of fields accessed by an IDM table in your system. The rule returns an estimate of the maximum CTABLESIZE required (for each TIBCO Object Service Broker table type) to support this number of fields.
The following screen illustrates the result of executing the rule for 50 fields.

 
----------------------------- INFORMATION LOG --------------------------------
COMMAND ===> SCROLL ===> P
DATE: Mar 28,2007 REPORT ON ESTIMATE CTABLESIZE
FOR "50" FIELDS
 
Table Type CTablesize(K)
---------- -------------
 
ADA 5
DAT 7
DB2 5
IDM 6
IMS 6
MAP 4
SLK 4
204 6
TDS 3
 
 
 
 
 
 
 
PFKEYS: 2=NEXT LOG 3=EXIT 5=REPEAT FIND 12=EXIT 13=PRINT 9=RECALL

 
If the CTABLESIZE parameter is set to its maximum of 31 KB, you can access approximately 380 fields using one IDM table definition, providing the data does not exceed 31744 bytes per row.
See Also
TIBCO Object Service Broker Shareable Tools for more information on ESTIMATETBLDEFN.
TIBCO Object Service Broker Parameters for more information about the CTABLESIZE Data Object Broker parameter.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved