![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
When you start an instance of the Gateway, you are connected to TIBCO Object Service Broker. When the Execution Environment requests an access to IMS data, the Gateway establishes a connection to IMS (DL/I, BMP, DRA or CICS) and builds the corresponding DL/I request that retrieves the data from IMS. Connection to DB2 is established on the first request for DB2 data.You can start multiple Gateways concurrently using the SERVERID parameter. The number of instances of the Gateway that you can start concurrently 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.If using the DL/I and BMP interface, you can start only one Gateway task per address space. You use the DRA interface to start multiple Gateways in a single address space. If using the CICS interface, you can start multiple Gateway tasks.
•
•
• Service Gateway for IMS/DB executes within the following TIBCO Object Service Broker Execution Environments:
In a Batch Execution Environment Use… In a Native Execution Environment Use… In a CICS Execution Environment Use... IMS/DB2 DL/I IMS/DB2 BMP TIBCO Object Service Broker Messages With Identifiers for information on the messages produced by the Gateway.TIBCO Object Service Broker for z/OS Installing and Operating for more information on starting multiple Gateways.If using the DL/I interface, the sample JCL for running in a Batch Execution Environment is in member IMSBDR in the JCL data set; for running in a Native Execution Environment it is in member IMSEDS.If using the BMP interface, the sample JCL for running in a Batch Execution Environment is in member IMSBBR in the JCL data set; for running in a Native Execution Environment it is in member IMSEBS.Use IMSEBS (for BMP) and IMSEDS (for DL/I) if you want to start an instance of the Gateway (where the Gateway stays up and users can run their rules from a workbench, edit or browse the IMS table, and so on).Use IMSBBR (for BMP) and IMSBDR (for DL/I) if you want to start an instance of the Gateway in a batch Execution Environment. In this case, you must supply the rule to execute the user ID, password and library where the rule is located. The Gateway terminates after successful execution of the rule.In the BMP interface, the sample JCL for running in a Batch Execution Environment is in member IMSBBR in the JCL data set; for running in a Native Execution Environment, in member IMSEBS.
• Do not specify USERTYPE=ONLINE for the Gateway running in a Batch Execution Environment.
• The Execution Environment uses the value of the SERVERPARM parameter specified in the HRNIN DDname as the parm string for DFSRRC00.
• If you are using the BMP interface, you must define the IMS APPLCTN macro to your IMS online system as described in Defining the Gateway to the IMS Online System.Starting in a TIBCO Object Service Broker CICS Execution Environment Using the CICS InterfaceSample JCL for running the Gateway in a CICS Execution Environment using the CICS interface is in member IMSCDS in the JCL data set. The Gateway tasks are initialized when the CICS Execution Environment starts.
• You must specify the CICSHURONTRAN=aaaa parameter, where aaaa represents the TIBCO Object Service Broker CICS transaction identifier (trans ID) that the CICS Execution Environment assigns to all CICS transactions associated with the Gateway. Refer to Supplying Gateway Startup Parameters for more information. This trans ID must be defined in the CICS Program Control Table and the CICS Process Program Table.
• Each task requires approximately 644 KB plus the POOLSIZE of memory above the line. For example, if the POOLSIZE gateway startup parameter (defined in the IMSSRV00 SYSIN file) is set to the default size of 256 KB, each Gateway task requires 900 KB above the line.
• You can start multiple Gateways concurrently that reside in different CICS Regions. Use the SERVERID gateway startup parameter (defined in the IMSSRV00 SYSIN file) to group together Gateways with common characteristics. The number of instances of the Gateway that you can start concurrently 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.
• If you want to access the Gateway from a Batch Execution Environment, you must specify the gateway startup parameter USERTYPE=ANY or USERTYPE=LOCAL in the IMSSRV00 SYSIN file.If using the DRA interface, the sample JCL for running in a Native Execution Environment is in member IMSEDRA.The Gateway must load DFSPRRC0. The system programmer can copy the routine from IMS.RESLIB library or can concatenate the IMS.RESLIB library to the TIBCO Object Service Broker Gateway step library.
2. The system programmer must place the DFSPZPxx load module (DRA startup table) in a Gateway load library.On the initialization request, the Gateway specifies the startup table name suffix (DRASUFFIX=xx). The default load module, DFSPZP00, contains default values for the DRA initialization parameters. If values other than the defaults are required, the system programmer can modify the module (naming it DFSPZPxx), assemble and linkedit it, and load it into the TIBCO Object Service Broker load library. See the current IMS Customization Guide IBM manual for more information.Starting to Access Both IMS and DB2 Data in a TIBCO Object Service Broker Batch or Native Execution Environment Using the DL/I InterfaceIf using the DL/I interface, the sample JCL for running in a Batch Execution Environment is in member IM2BDR in the JCL data set; for running in a Native Execution Environment it is in member IM2EDS.
• Do not specify USERTYPE=ONLINE for an instance of the Gateway concurrently accessing DB2 data running in a Batch Execution Environment.
• The Execution Environment uses the value of the SERVERPARM parameter specified in the HRNIN DDname as the parm string for DFSRRC00.
• The DDITV02 DD statement specifies the data set that contains the input parameters used by the IMS subsystem attach facility for DB2. Member XIM2DB21 in the CNTL data set contains sample input parameters:
The DB2 subsystem identifier. This OSEMOD parameter must be modified. The resource translation table. If no RTT is required, this parameter must be set to null. The region error option. When set to R, it returns any SQL return codes to the Service Gateway for IMS program. The connection name that represents the name of the job step that is the coordinator for the DB2 activity. This OSEMOD parameter must be modified.If not specified, the connection name defaults to the job name (if the Gateway is running as a batch job) or the started task job name (if the Gateway is running as a started task).
• If the gateway parameter FSLEVEL=1, the PLAN defined in the DDITV02 statement must be rebound with the current TIBCO Object Service Broker DBRMLIB library.
• The DDOTV02 DD statement specifies an output data set used to receive messages from the IMS subsystem attach facility about in-doubt and diagnostic information.The DB2 Application Programming & SQL Guide IBM manual for information about DB2 DL/I batch support. See TIBCO Object Service Broker for z/OS Installing and Operating for more information on starting multiple Gateways concurrently.Starting to Access Both IMS and DB2 Data in a TIBCO Object Service Broker Batch or Native Execution Environment Using the BMP InterfaceIf using the BMP interface, the sample JCL for running in a Batch Execution Environment is in member IM2BBR in the JCL data set; for running in a Native Execution Environment it is in member IM2EBS.
• Do not specify USERTYPE=ONLINE for an instance of the Gateway running in a Batch Execution Environment.
• The Execution Environment uses the value of the SERVERPARM parameter specified in the HRNIN DDNAME as the parameter string for DFSRRC00.
• If you are using the BMP interface, you must define the IMS APPLCTN macro to your IMS online system as described in Defining the Gateway to the IMS Online System.
• Include the SSM parameter in the startup JCL, in the IMS Control Region startup JCL, or in both.
• Specify the DB2 subsystem to which the IMS Control Region is to connect in the IMS PROCLIB Subsystem Specification Member (SSM).The DB2 Application Programming & SQL Guide IBM manual for information about DB2 support.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |