![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
The following sections describe where Execution Environment and session parameters are obtained and which DD names are required by the Native Execution Environment.The Native Execution Environment session defaults apply to all sessions running within it. The following table describes where to specify the values for your sessions and their order of evaluation, from highest to lowest:
Execution Environment startup string Specified on the EXEC PGM= S6BDR000 card in PARM=‘Execution Environment startup string’. Execution Environment parameter input file TIBCO Object Service Broker default Loaded from STEPLIB. Default configuration is S6BDRCN0 except when overridden by the CONFIGURATION parameter.
Certain parameters, such as SECURITY, cannot be specified in the HRNIN PARM=‘Execution Environment startup string’. They must be added to the PARMNEE member in the TIBCO Object Service Broker CNTL data set, and followed by an EECONFIG assembly and link-edit job that creates a new S6BDRCN0 load module.In addition to providing session defaults for TIBCO Object Service Broker VTAM LU2 sessions, the session defaults also apply to TIBCO Object Service Broker IMS TM sessions, peer servers, and instances of TIBCO Service Gateway for Adabas, TIBCO Service Gateway for Datacom, and TIBCO Service Gateway for IMS/DB that are running in the Native Execution Environment. For further information about these additional topics, refer to Chapter 8, Using the TIBCO Service Gateway for IMS TM or the appropriate TIBCO Service Gateway.
Optional partitioned data set containing load modules for user external routines. Sequential file containing the Execution Environment and session parameter defaults. Optional APF authorized partitioned data set containing the load modules required to run the Execution Environment when STEPLIB is not APF authorized. The load library (partitioned data set) containing the load modules required to run the Execution Environment. Optionally, user external routines can be stored in this library.TIBCO Object Service Broker for z/OS Installing and Operating for more information on using HRNLIB to make sure that the TIBCO Object Service Broker load library is authorized.
• Do not include the DDnames HRNOUT or HRNPRNT. These are session print files for single-session Execution Environments such as batch or TSO.
• Do not use the name S6BDRPRT as a print destination in a JES complex. This name is used by TIBCO Object Service Broker to run the SPOOLSTRIP job.Communication is established with the Data Object Broker specified by the TDS parameter. Use the syntax below to log in to the Native Execution Environment that you require.
The EENAME parameter value specified when the Native Execution Environment was initialized. Ask your system administrator to provide you with this value. A valid TIBCO Object Service Broker user ID that the Native Execution Environment uses to create a TIBCO Object Service Broker session. The password of the user ID set by the U parameter can be optionally specifiedOther session parameters can be specified in the DATA parameter, up to the VTAM restriction on the length of the DATA parameter string (64 characters).TIBCO Object Service Broker for z/OS Installing and Operating for additional information about installing and configuring the Native Execution Environment interface.TIBCO Object Service Broker Parameters about parameters.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |