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


Chapter 3 Setting Execution Environment Parameters : Determining Session Characteristics

Determining Session Characteristics
You can set session parameters in a number of ways, as described in the following sections. You can also configure your session to use either a pre-supplied workbench or to execute a user-supplied or an installation-supplied rule.
When your session is activated, session parameter and Execution Environment parameter values are merged to determine the characteristics of your session. How this data is merged is decided by the order of evaluation described in the two tables below.
Login Authentication Required
Before your session can be activated you must pass login authentication. This authentication is based on the user ID you are using to activate your session.
See Also
TIBCO Object Service Broker Parameters for more information about parameters.
Where to Specify Parameters for Single-Session Clients
The following table shows where you can specify the session parameters for clients running single sessions. If the same parameter appears in more than one place, the parameter value of the highest priority specification is used.
Y4, 5
Yd, e
TIBCO Object Service Broker-supplied default

1
Specified on the EXEC card using PARM='session startup string'. Maximum 100 characters.

2
The TIBCO Object Service Broker CLIST creates a temporary file allocated to DDname HRNIN to pass all parameters.

3
Parameter input file must be allocated to DDname HRNIN.

4
The User Profile is bypassed if the session parameter NOPROFILE is used.

5
The profile of the user ID is always used.

6
The installation default configuration module name is determined by the type of Execution Environment. The default module name can be overridden by specifying the Execution Environment CONFIGURATION parameter.

7
Refer to TIBCO Object Service Broker for z/OS Installing and Operating for TIBCO Object Service Broker default values.
h. The second last character represents the type of Execution Environment, i.e., B=Batch and N=Native. This information is displayed in the Execution Environment startup message.
 

Where to Specify Parameters for Multiple-Session Clients
The following table shows where you can specify the parameters for clients running multiple sessions. If the same parameter appears in more than one place, the parameter value of the highest priority specification is used.
Y4, 5
Yd, e
Yd, 6
Execution Environment startup string
Execution Environment parameter input file
TIBCO Object Service Broker supplied default

1
Specified on the command line in the HURN session startup string or in the parameter area of the COMMAREA passed to a non-seamless TIBCO Object Service Broker/CICS interface program. Cannot be specified to a seamless TIBCO Object Service Broker/CICS interface program.

2
Specified on the command line in the S6BLOGON session startup string or in the parameter segment to a non-seamless TIBCO Object Service Broker IMS TM client program.

3
Specified when logging in to the Native Execution Environment using the DATA('session startup string') operand. Maximum 64 characters.

4
The User Profile is bypassed if the NOPROFILE session parameter is used.

5
The external transaction profile is used for seamless clients, and the user profile is used for non-seamless clients.

6
The profile of the user ID is always used.

7
Specified in the command line HINT region startup string.

8
Specified on the EXEC PGM=S6BDR00 card in PARM='region startup string'. Max: 100 characters.

9
Parameter input file must be allocated to the HRNIN DDname.

10
The installation default configuration module name is determined by the type of Execution Environment. The default module name can be overridden by specifying the CONFIGURATION Execution Environment parameter.

11
IMS TM sessions run in a Native Execution Environment.

12
Refer to TIBCO Object Service Broker for z/OS Installing and Operating for TIBCO Object Service Broker default values.
m. The second last character represents the type of Execution Environment, i.e., C=CICS, I=IMS, and N=Native. This information is displayed in the Execution Environment startup message.

See Also
TIBCO Object Service Broker Parameters for detailed information about session parameters.
TIBCO Object Service Broker for z/OS Installing and Operating for detailed information about creating default configuration modules.
TIBCO Object Service Broker Managing Security about TIBCO Object Service Broker security and logging in to TIBCO Object Service Broker.

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