Copyright © Cloud Software Group, Inc. All Rights Reserved

Creating Control Table Definitions

Single CICS Region

If you are running a single CICS region, define the following programs in Resource Definition Online (RDO). You can also use the CICSDEFS member in the JCL data set to define these programs in LIST $OSTARNMR$.

Transaction ID	Transaction	Pointing to Program...
HAPI	Call Level API Test Program.	HRNCALIN
HCLI	Application Processing: Standby Session Server.	S6BCSCLI
HCSS	Internal Timeout.	S6BCSCSS
HCUS	Canceluser.	S6BCSCUS
HFUS	FORCE Canceluser.	S6BCSFUS
HINQ	Operator Inquiry.	S6BCSINQ
HINT	Operator Initialization.	S6BCSINT
HREL	HCS RELAY Operator Command Processor.	S6BCSREL
HSC1	Application Processing: Display / Seamless.	S6BCSSC1
HSN1	Application Processing: non-Display / Seamless.	S6BCSSN1
HSN2	Application Processing: non-Display / non-Seamless.	S6BCSSN2
HSRV	External Database Server Operator Control.	S6BCSSRV
HTC1	Application Processing: Display / Seamless.	S6BCSTC1
HTC2	Application Processing: Display / non-Seamless.	S6BCSTC2
HTN1	Application Processing: non-Display / Seamless.	S6BCSTN1
HTN2	Application Processing: non-Display / non-Seamless.	S6BCSTN2
HTRM	Operator System Termination.	S6BCSHUT
HURN	Application Processing: Display / non-Seamless.	S6BCSSC2

Usage Notes

Note the following when defining the transactions:

•	You must specify TASKDATAKEY(USER) and TASKDATALOC(ANY).

Note: You can specify TASKDATAKEY(CICS) but doing so is overrestrictive, preventing users from calling CICS external routines with EXECKEY(USER). Instead, users must define their program as EXECKEY(CICS), which allows the external CICS routine, if it contains an addressing error, to corrupt CICS storage.

•	TIBCO Object Service Broker is sensitive only to the specific transaction names HCUS, HOPT, and HCSS. You can assign your own names, one to four characters in length, or PF keys for the other transactions.

•	If you do use your own transaction name instead of HURN, you must specify the Execution Environment parameter CICSHURONTRAN=yourname. This is required for proper initialization of TIBCO Object Service Broker peer servers.

•	If you require a lowercase transaction name, use the ALIAS parameter.

•	If you are running in a Multi-Region Option (MRO) environment or using Inter System Communications (ISC), you must include the following information so the user ID is passed to the Application Owning Region (AOR):

ATTACHSEC(IDENTIFY) (Connection definitions)

Multi-Region Option (MRO) Environment

If you are running in an MRO environment, define these transactions to both the Terminal Owning Region (TOR) and the AOR. The Execution Environment executes within the AOR.

Setting Up an MRO Environment

To set up an MRO environment, define the TIBCO Object Service Broker transactions as being remote to the TOR and local to the AOR. For pseudo-conversational CICS environments, the transaction invoking S6BCSSC2 must use the same transaction identification for both the TOR remote definition and the AOR local definition. It is recommended that the same transaction identification be used in both the TOR and AOR, whether or not you are using pseudo-conversational processing. Refer to TIBCO Object Service Broker Parameters for a description of the CICSPSEUDOCONVERSE parameter.

Define TOR Transaction Definitions

Define the following TOR transaction definitions using RDO. You can also use the CICSDEFS member in the JCL data set to define these definitions in LIST $OSTARTOR$.

Transaction ID	Transaction
HAPI	Call Level API Test Program.
HCUS	Canceluser.
HFUS	FORCE Canceluser.
HINQ	Operator Inquiry.
HINT	Operator Initialization.
HOPT	Internal TOR Function Shipping Canceluser.
HREL	HCS RELAY Operator Command Processor
HSC1	Application Processing: Display / Seamless.
HSN1	Application Processing: non-Display / Seamless.
HSN2	Application Processing: non-Display / non-Seamless.
HSRV	External Database Server Operator Control.
HTC1	Application Processing: Display / Seamless.
HTC2	Application Processing: Display / non-Seamless.
HTN1	Application Processing: non-Display / Seamless.
HTN2	Application Processing: non-Display / non-Seamless.
HTRM	Operator System Termination.
HURN	Application Processing: Display / non-Seamless.

Refer to Notes on Usage for additional information about defining the transactions.

All transactions are remote to the attached AOR except HOPT, which executes in the TOR and must be associated with the program S6BCSOPT. HOPT must not be defined as remote and it must run in the TOR.

Define AOR Transaction Definitions

Define the following AOR transaction definitions using RDO. You can also use the CICSDEFS member in the JCL data set to define these definitions in LIST $OSTARAOR$.

Transaction ID	Program
HAPI	S6BCALIN
HCLI	S6BCSCLI
HCSS	S6BCSCSS
HCUS	S6BCSCUS
HFUS	S6BCSFUS
HINQ	S6BCSINQ
HINT	S6BCSINT
HREL	S6BCSREL
HSC1	S6BCSSC1
HSN1	S6BCSSN1
HSN2	S6BCSSN2
HSRV	S6BCSSRV
HTC1	S6BCSTC1
HTC2	S6BCSTC2
HTN1	S6BCSTN1
HTN2	S6BCSTN2
HTRM	S6BCSHUT
HURN	S6BCSSC2

Notes on Usage

When defining the TOR and AOR transactions:

•	You must specify TASKDATAKEY(USER) and TASKDATALOC(ANY).

•	TIBCO Object Service Broker is sensitive only to the specific transaction names HCUS, HCSS, and HOPT. You can assign your own names, one to four characters in length, or PF keys for the other transactions.

•	If you are running TIBCO Object Service Broker in multiple CICS AORs off the same TOR, the HINT, HTRM, HURN, HINQ, HCUS, and HFUS transactions must have different names for each AOR.

•	If you require a lowercase transaction name, use the ALIAS parameter.

•	When running MRO or using ISC, include the following information so the user ID is passed to the Application Owning Region (AOR):

ATTACHSEC(IDENTIFY) (Connection definitions)

Select a number of ISC sessions appropriate to your site. The greater the number of users you expect to be logged in to TIBCO Object Service Broker, the higher this number should be. The minimum required by TIBCO Object Service Broker is 2. The IBM default is 1.

Copyright © Cloud Software Group, Inc. All Rights Reserved