The CICS segment
The CICS® segment of the RACF® user profile contains data for CICS users.
For information on the order in which CICS searches for the operator information, see Obtaining CICS-related data for a user.
The information you can specify in the CICS segment is as follows:
- OPCLASS({1|number})
- CICS uses
the operator classes when routing basic mapping support (BMS) messages
initiated within a CICS transaction.
The operator classes are numeric values in the range 1–24.
Specify operator classes for users who use CICS transactions that issue EXEC CICS ROUTE commands with the (optional) OPCLASS parameter. For automatic routing to occur, you specify the corresponding value as an operator class in the CICS segment of the user profile.
For more information about message routing, see Message routing.
- OPIDENT({blank|name})
- The 1- to 3-character operator identification
code that you assign to each operator.
CICS stores the code in the operator's terminal entry in the CICS terminal control table (TCTTE) when the operator signs on. This operator ID is displayed in certain CICS messages and can also be used in the EXEC CICS ROUTE command for routing BMS messages. It is also used when using the CEDA LOCK command.
For more information about message routing, see Message routing.
- OPPRTY({0|number})
- The operator priority value—a decimal
number that you want CICS to
use when determining the task priority for CICS transactions that the operator invokes
at a CICS terminal. The priority
value can be in the range 0 through 255, where 255 is the highest
priority.
CICS uses the sum of operator priority, terminal priority, and transaction priority to determine the dispatching priority of a transaction.
- TIMEOUT({0000|hhmm})
- The time that must elapse since
the user last used the terminal before CICS
times-out
the terminal.The time must be a decimal integer in the range 0 through 9959 (the last two digits represent a number of minutes, and must be 00 through 59. Any digits to the left of these represent hours).
To specify one hour and eight minutes you would code a value here of 0108. For example:
The value of 0 (the default) means that the terminal is not timed out.ALTUSER userid CICS(TIMEOUT(0108)) - XRFSOFF({NOFORCE|FORCE})
- The CICS persistent sessions restart and extended
recovery facility (XRF) sign-off option. You specify this to indicate
whether or not you want CICS to
sign off the operator following a persistent sessions restart or an
XRF takeover.
- FORCE
- Specify FORCE if you want CICS to sign off the operator automatically in the event of a persistent sessions restart or an XRF takeover.
- NOFORCE
- Specify NOFORCE if you want CICS to leave an operator signed on in the event of a persistent sessions restart or an XRF takeover.
You can specify the XRFSOFF function at the level of groups of similar terminals, and at the CICS system level:- Use the RSTSIGNOFF attribute of the TYPETERM resource definition to specify the XRFSOFF function for groups of similar terminals.
- Use the RSTSIGNOFF system initialization parameter to specify the function at the system level.
Table 1 shows how specifying FORCE or NOFORCE in the system initialization parameters, on the TYPETERM definition, and in the CICS segment together determine whether a terminal remains signed on after a persistent sessions restart or an XRF takeover. For a terminal to remain signed-on after a persistent sessions restart or an XRF takeover, NOFORCE must be specified in all three locations.
Table 1. Effects of FORCE and NOFORCE options TYPETERM definition CICS segment System initialization parameter Resulting terminal status FORCE FORCE FORCE Signed off FORCE FORCE NOFORCE Signed off FORCE NOFORCE FORCE Signed off FORCE NOFORCE NOFORCE Signed off NOFORCE FORCE FORCE Signed off NOFORCE FORCE NOFORCE Signed off NOFORCE NOFORCE FORCE Signed off NOFORCE NOFORCE NOFORCE Signed on Note: If takeover has exceeded the time specified by the RSTSIGNTIME system initialization parameter, users at terminals that have a nonzero TIMEOUT value do not remain signed on after takeover. For example, suppose the following has been specified in a system that has XRFSOFF=NOFORCE:ALTUSER USER1 CICS(XRFSOFF(NOFORCE) TIMEOUT(10)) ALTUSER USER2 CICS(XRFSOFF(NOFORCE) TIMEOUT(1))If a persistent sessions restart or an XRF takeover occurs to a system in which XRFSTME=5 is specified in the system initialization parameters, and the restart or takeover takes longer than five minutes, USER1 does not remain signed on, but USER2 does.