Function

To modify the specified trace identifiers.

Parameters

nn

The subscript that defines the trace IDs to modify. The subscript might specify a specific trace ID or a range of trace IDs. The range of trace IDs reserved by IBM® is 1 to 47. Trace IDs 48 to 255 are available for customer use. For more information about specific identifier meanings, see z/OS JES2 Diagnosis, GA32-0993.

ASID= xxxx

Specifies the ASID used when filtering this JES2 trace point.

JOBNAME=nnnnnnn

Specifies the jobname used when filtering this JES2 trace point.

JOB_NUMBER=nnnnnnn

Specifies the job number used when filtering this JES2 trace point.

Note: If more than one of ASID=, JOBNAME=, and JOB_NUMBER= are specified for a specific trace ID, only one of the conditions must match the trace to be taken. In the JES2 address space, the values specified refer to the job that is being processed by JES2. For example, never specify the JES2 address space as ASID= because JES2 is never processing requests on the behalf of JES2. Outside the JES2 address space, these filters refer to the address space where the trace is being taken. For jobs being submitted through the internal reader, it is the job name, number, and ASID of the submitter of a job that are compared to the filters, not the values of the job being submitted. The same is true for FSS or SAPI devices. The filters refer to the SAPI or FSS address space, not the job that the FSS or SAPI application is processing.

TCB_ADDRESS=xxxxxxxx

Specifies the further limit tracing to the specified TCB. This is in addition to any filtering that is applied. This operand is ignored if ASID=. JOBNAME=, and JOB_NUMBER= are not specified. The TCB address must match even in the JES2 address space.

Authority Required

This command requires system authority. The description of the $T RDRnn command explains how to ensure that the authority of the appropriate MVS™ system command group is assigned.

This command requires control security access authority. For a description of assigning command input authority, see z/OS JES2 Initialization and Tuning Guide, SA32-0991.

Processing Considerations

• Each trace ID may be started independent of the overall trace facility. However, no tracing is done unless the trace facility is also started. See the description of the TRACE facility and the TRACEDEF initialization statement in z/OS JES2 Initialization and Tuning Reference, SA32-0992 for information about starting the trace facility.
• The trace table entries are added to JES2 trace tables as they are generated. These tables are reused if trace logging is not in effect. If trace logging is enabled, then full trace tables are formatted and added to the JES2 event trace log.

Scope

Single member. This command will be in effect for this member only.

However, you might want this command to be applied to all members of the MAS (to ensure a consistent environment across the MAS). If so, you can use the MVS ROUTE *ALL command to issue this command to all active members (if the JES2 command character is the same on all members). See z/OS MVS System Commands, SA38-0666 for more information on using the ROUTE *ALL command.

Messages

The $HASP667 message displays the current status of the specified trace IDs.

JES2 changes ASID, JOBNAME, and JOB_NUMBER parameters.