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


Chapter 12 Starting and Shutting Down TIBCO Object Service Broker : Starting an Execution Environment

Starting an Execution Environment
After starting a Data Object Broker, you must start an Execution Environment under CICS or TSO, or as a Native Execution Environment. The different operating environments are discussed separately below. For details on Execution Environments, see TIBCO Object Service Broker for z/OS External Environments.
Parameters, usually set at installation time, determine operating characteristics of your Execution Environment. You can modify Execution Environment parameters through operator commands. For more information about operator commands refer to Chapter 16, Operator Commands and for a description of the parameters refer TIBCO Object Service Broker Parameters.
Starting a CICS Execution Environment
Benefits of the CICS Execution Environment
Starting a CICS Execution Environment enables you to run multiple TIBCO Object Service Broker sessions concurrently in the CICS environment. The benefit of using a CICS Execution Environment is that it reduces overhead resource consumption, and enables you to run significantly more user sessions on a given system.
Authorizing the CICS Execution Environment
The CICS Execution Environment runs as a z/OS subtask of CICS. To run this as an authorized subtask of CICS (enabling Cross Memory Services), install the TIBCO Object Service Broker SVC. Refer to Installing the TIBCO Object Service Broker SVC for details.
Starting the CICS Execution Environment Automatically
To bring up the CICS Execution Environment automatically when you start CICS, define the program S6BCSINT in the CICS startup PLT. If the startup PLT program detects that it cannot start the Execution Environment interface in an authorized state, a message prompts you to type one of the following values:
Establishing Sessions
When the initialization completes successfully, a message notifies you that the CICS Execution Environment subtask is attached. At this point users can, from a terminal in CICS, establish TIBCO Object Service Broker sessions with the Data Object Broker by entering the transaction code HURN or the transaction code assigned at installation time.
Restarting or Starting a CICS Execution Environment
If it is necessary to reestablish communications with the Data Object Broker after CICS is already initialized, complete the following steps:
Step 1: Define S6BCSINT
Make sure that the initialization program name S6BCSINT is defined to CICS. This enables communications to be reestablished with the Data Object Broker.
Step 2: Enter HINT Transaction Code
If you need to restart communications or you want to start a selected Execution Environment, enter the transaction code HINT from the z/OS system console or CICS session. Use this code as follows:
HINT<Enter>
MODIFY cics_jobname,HINT<Enter>
Optional Parameters for HINT
You can specify the following optional parameters for HINT, in any order:
MDL=value
TDS=value
SYSLIB=value
For More Information
For more information about customizing CICS transaction codes or defining programs to the CICS Initialization and Shutdown PLTs, refer to Installing the Service Gateway for CICS.
Starting a TSO Execution Environment
Sample EXECs for Starting a TSO Execution Environment
TIBCO Object Service Broker comes with sample REXX EXECs for starting a TSO Execution Environment as a user, a system administrator, and an operator. These EXECs are customized at installation time. For information on how these EXECs are customized, refer to Step 3: Customize TSO Execution Environment EXEC.
Example
For example, at your site you could be directed to use a customized copy of the USER EXEC that was renamed OSB. From a TSO session, type:
OSB<Enter>
The appearance of the TIBCO Object Service Broker workbench or initial application screen confirms that TIBCO Object Service Broker is ready for use.
Starting a Native Execution Environment
Benefits of the Native Execution Environment
By setting up a Native Execution Environment, you can avoid intermediate software layers (such as CICS or TSO) and improve response time. Multiple users can access the Data Object Broker concurrently through one Native Execution Environment. In an IMS TM environment, the IMS Message Processing Region that communicates with TIBCO Object Service Broker connects to a Native Execution Environment.
JCL for starting the Native Execution Environment
You can start the Native Execution Environment as either a started task or a batch job. Sample JCL is provided in the JCL data set as member NATIVEEE. For information on how this JCL can be customized, refer to Start a Native Execution Environment.
Logging In to TIBCO Object Service Broker
When the Native Execution Environment is running, users can log in to TIBCO Object Service Broker by referencing its VTAM application ID (applid) in their login statement as follows:
logon applid(applid) data(U=’userid’,P=’password’)
 
The model applid (MDL=parameter value) can be defined using either of the following values:
1 – The MDL parameter value specified at TIBCO Object Service Broker installation time for the Native Execution Environments.
2 – MDL value specified by the JCL keyword PARM on the EXEC statement used to start the Native Execution Environment. Parameters specified in the EXEC statement override the defaults coded at TIBCO Object Service Broker installation time.
This can be any valid applid that is not already used for a pool of TIBCO Object Service Broker applids or for Data Object Brokers.
Optional: If P=password is not specified, the user is prompted for a password.
Including Other Execution Environment Parameters
Other Execution Environment session parameters can be included in the login statement to a maximum of 64 characters.
See Also
TIBCO Object Service Broker for z/OS External Environments for more information about Execution Environments.
TIBCO Object Service Broker Parameters for more information about Execution Environment and session parameters.

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