OPTIONS parameter

The OPTIONS parameter for the CTnRRSxx parmlib member or reply for a TRACE command contains keyword subparameters. These subparameters allow you to control the information that RRS component trace collects. The first subparameter, EVENTS, specifies the events to be traced; the other subparameters act as filters to screen the events with up to three checks. An event must pass all checks for component trace to generate a trace record. The order for the checks is:

That the event is specified.
That the event matches, in an OR check, one of the following filters:
- The address space ID (ASID) in the REPLY command or CTnRRSxx TRACEOPTS statement
- The job name (JOBNAME) in the REPLY command or CTnRRSxx TRACEOPTS statement
- The user ID (USERID) in the OPTIONS parameter
- The logical work unit ID (LUWID) in the OPTIONS parameter
That the event matches a resource manager name (RMNAME) in the OPTIONS parameter.

OPTIONS=([EVENTS(event[,event]...)]
         [USERID(userid[,userid]...)]
         [RMNAME(rmname[,rmname]...)]
         [LUWID((luwid)[,(luwid)]...)])
         [EID((eid)[,(eid)]...)

Note: In the REPLY to the TRACE CT command, separate the options by one or more blanks.

EVENTS(event[,event]...)

Indicates the events to be traced. An EVENTS parameter is required if any other options are specified. The events, in alphabetical order, are:

ALL: Traces all events. Component trace ignores other events, if specified.
CONTEXT: Traces calls to context services.
EXITS: Traces events related to running the RRS exit routines provided by the resource managers.
FLOW: Traces entry into and exit from RRS entry points.
LOGGING: Traces events related to logging data by RRS.
RESTART: Traces events related to RRS initialization and restart.
RRSAPI: Traces events related to the application programming interface, which consists of calls to the Application_Commit_UR service and the Application_Backout_UR service.
STATECHG: Traces events involving changes in the state of units of recovery (URs).
URSERVS: Traces general events related to services for a UR (traced by default).

USERID(userid[,userid]...)

Specifies 1 to 16 user IDs as filters for specified events. The system traces only events relating to the user IDs.

RMNAME(rmname[,rmname]...)

Specifies 1 to 16 resource manager names as filters for specified events. For trace events sensitive to the resource manager name, the system traces only events relating to the resource managers.

LUWID((luwid)[,(luwid)]...)

Specifies 1 to 16 logical unit of work identifiers (LUWIDs) as filters for specified events. The system traces only events relating to the LUWIDs. Each luwid consists of:

netid.luname[,instnum][,seqnum]

Component trace ignores leading and trailing blanks.

netid.luname

Specifies the network ID and the local logical unit name. These portions of the LUWID are required.

You can use an asterisk (*) as a wildcard character as:

The last character in the netid, the luname, or both
The only character in the either the netid or the luname, but not as the only character in both

instnum

Specifies the instance number as a 1 - 12 hexadecimal integer. You can omit leading zeros.

seqnum

Specifies the sequence number as a 1 - 4 hexadecimal integer. You can omit leading zeros.

Examples of LUWIDs are:

(A.B,5,1)
(A.B,5)
(A.B,,1)
(A.B)
(A.*,5,1)
(A*.B*)

EID((eid)[,(eid)]...)

Specifies 1 to 16 Enterprise identifiers (EIDs) as filters for specified events. The system traces only events relating to the EIDs. Each eid consists of:

[tid][,gtid]

You can omit leading zeros. Component trace ignores leading and trailing blanks.

tid: Specifies the 4-byte hexadecimal transaction identifier (TID).
gtid: Specifies the 8-40 byte hexadecimal global transaction identifier (GTID).

You can obtain the EID for a UR by using the RRS ISPF panels to browse the RRS log streams. The Retrieve_Work_Identifier service can also return an EID.

Examples of EIDs are:

(1,C)
(,C)
(1)