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


Chapter 18 TIBCO Object Service Broker SDK (C/C++) Server : Additional Requirements for CICS Execution Environments

Additional Requirements for CICS Execution Environments
SIT Parameter Requirements
To run the SDK (C/C++) session CICS background task under the SDK (C/C++) client session’s user ID (USERID1) and to enable CICS surrogate user checking, you must start CICS with the following SIT parameters:
DFLTUSER=USERID2,SEC=YES,XUSER=YES
The following parameters are optional, although you can specify these if you are not implementing security for them at this time:
XCMD=NO
XDCT=NO
XFCT=NO
XJCT=NO
XPCT=NO
XPPT=NO
XPSB=NO
XTRAN=NO
XTST=NO
Specifying the CICS Session Background Task Transaction
To set up the SDK (C/C++), use the following background task:
Specifying RACF Definitions
When the TIBCO Object Service Broker CICS SDK (C/C++) server receives a CONNECT request from the SDK (C/C++) client, it starts a special type of HURN transaction (HCLI), which runs under USERID2, the value specified by the DFLTUSER parameter, from the z/OS console. This HURN transaction in turn starts the SDK (C/C++) background task by issuing:
   EXEC CICS START TRANSID('HCLI') userid('USERID1')
USERID2 must be defined to your security system, as a surrogate of USERID1 (with READ authority) as illustrated in the following RACF definition commands:
RDEFINE  SURROGAT  USERID1.DFHSTART UACC(NONE) OWNER(USERID1)
PERMIT   USERID1.DFHSTART CLASS(SURROGAT) ID(USERID2) ACCESS(READ)
See Also
Selecting a TIBCO Object Service Broker CICS Client Program
TIBCO Object Service Broker for z/OS Installing and Operating about installing the CICS component of TIBCO Object Service Broker.
TIBCO Object Service Broker Parameters about parameters.

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