Specifying selection criteria

The field selection values that you can provide in APPSEL and APPVAL for each object type are described here. They are used to identify the instance of the object that you want to create an event for.

Selecting an operation to change the status (CP_OPER_EVENT)

You can specify these fields to identify a current plan operation for which you want to change the status:

Table 29. CP_OPER_EVENT selection fields
Field Type Size Description
SUBSYSTEM_NAME CHAR 4 Subsystem name
WS_NAME CHAR 4 Workstation name
JOBNAME CHAR 8 Job name
APPL_ID CHAR 16 Application ID
OPER_NUM BIN 15 Operation number
APPL_IA_DATE CHAR 6 Input arrival date (YYMMDD)
APPL_IA_TIME CHAR 4 Input arrival time (HHMM)
FORM_NUMBER CHAR 8 Form number
CLASS CHAR 1 SYSOUT class
OPER_TOKEN CHAR 8 Operation token

SUBSYSTEM_NAME
The name of the tracker subsystem that the event should be reported to. If SUBSYSTEM_NAME is not specified or has the value MSTR, the event is broadcast using the subsystem interface (SSI) to all Tivoli Workload Scheduler for z/OS subsystems on the z/OS image where EQQUSIN is invoked.
WS_NAME
The name of the workstation.
JOBNAME
The name of the job that an event is being reported for.
APPL_ID
The name of the current application.
OPER_NUM
The number, in binary format, of the current operation. The number can have a decimal value from 1 to 255.
APPL_IA_DATE
The input arrival date of the current occurrence in the format YYMMDD.
APPL_IA_TIME
The input arrival time of the current occurrence in the format HHMM.
FORM_NUMBER
Contains the printer form number for operations at printer workstations.
CLASS
Contains the SYSOUT class for operations at printer workstations.
OPER_TOKEN
A hexadecimal value that uniquely identifies an operation. If you stored the token set in the OPCTOKEN parameter of the operation-initiation exit (EQQUX009), you can provide this token to EQQUSIN to uniquely identify the operation. OPER_TOKEN is valid only for operations at workstations that have a user-defined destination.
Note:
As the OPCTOKEN is defined as a full-word, the OPER_TOKEN should be filled as follows:
FIRST WORD    = X'00000000'
SECOND WORD   = OPCTOKEN FROM EXIT EQQUX009
Notes:
  1. You must specify at least OPER_TOKEN, or WS_NAME with either JOBNAME or APPL_ID.
  2. If you do not provide enough information to uniquely identify the operation, Tivoli Workload Scheduler for z/OS must determine the most applicable operation to update. Tivoli Workload Scheduler for z/OS considers only operations in status R, A, *, S, I, or E when selecting the operation. Tivoli Workload Scheduler for z/OS selects the operation to update by investigating these characteristics in the stated order:
    1. The operation has priority 9.
    2. Earliest latest start time.
    3. Priority 8-1.
    4. Input arrival time specified for the operation or the occurrence input arrival if the operation does not have input arrival specifically defined.

    So from the operations that match the selection criteria, the operation with priority 9 is updated. If more than one operation has priority 9, the operation with the earliest latest start time is updated. If latest start is equal, the operation with the highest priority is updated. If priority is equal, the operation with the earliest input arrival time is updated. If input arrival is also equal, the update is performed on a first-in-first-out basis.

Selecting a special resource (CP_SR_EVENT)

You can specify these fields to identify a current plan special resource:

Table 30. CP_SR_EVENT selection fields
Field Type Size Description
SUBSYSTEM_NAME CHAR 4 Subsystem name
SR_NAME CHAR 44 Name of special resource
SUBSYSTEM_NAME
The name of the tracker subsystem that the event should be reported to. If SUBSYSTEM_NAME is not specified or has the value MSTR, the event is broadcast using the subsystem interface (SSI) to all Tivoli Workload Scheduler for z/OS subsystems on the z/OS image where EQQUSIN is invoked.
SR_NAME
The name of the special resource.

Selecting an operation to supply user data (CP_OPINFO_EVENT)

You can specify these fields to identify a current plan operation for which you want to update the USERDATA field:

Table 31. CP_OPINFO_EVENT selection fields
Field Type Size Description
SUBSYSTEM_NAME CHAR 4 Subsystem name
WS_NAME CHAR 4 Workstation name
JOBNAME CHAR 8 Job name
APPL_ID CHAR 16 Application ID
OPER_NUM BIN 15 Operation number
APPL_IA_DATE CHAR 6 Input arrival date (YYMMDD)
APPL_IA_TIME CHAR 4 Input arrival time (HHMM)
FORM_NUMBER CHAR 8 Form number
CLASS CHAR 1 SYSOUT class
STATUS CHAR 1 Operation status

SUBSYSTEM_NAME
The name of the tracker subsystem that the event should be reported to. If SUBSYSTEM_NAME is not specified or has the value MSTR, the event is broadcast using the subsystem interface (SSI) to all Tivoli Workload Scheduler for z/OS subsystems on the z/OS image where EQQUSIN is invoked.
WS_NAME
The name of the workstation.
JOBNAME
The name of the job that an event is being reported for.
APPL_ID
The name of the current application.
OPER_NUM
The number, in binary format, of the current operation. The number can have a decimal value from 1 to 255.
APPL_IA_DATE
The input arrival date of the current occurrence in the format YYMMDD.
APPL_IA_TIME
The input arrival time of the current occurrence in the format HHMM.
FORM_NUMBER
Contains the printer form number for operations at printer workstations.
CLASS
Contains the SYSOUT class for operations at printer workstations.
STATUS
The current status of the operation.
Note:
If the OPINFOSCOPE keyword of the JTOPTS statement is IP, which is the default, you must specify WS_NAME. If OPINFOSCOPE is ALL, you must specify either APPL_ID or JOBNAME. The OPINFOSCOPE keyword is described on page ***.

Selecting a Tivoli Workload Scheduler for z/OS data set (BACKUP_EVENT)

You can specify these fields to identify an IBM Tivoli Workload Scheduler for z/OS data set:

Table 32. BACKUP_EVENT selection fields
Field Type Size Description
SUBSYSTEM_NAME CHAR 4 Subsystem name
FILENAME CHAR 2 Name of data set (CP or JS)
SUBSYSTEM_NAME
Is the name of the tracker subsystem that the event should be reported to. If SUBSYSTEM_NAME is not specified or has the value MSTR, the event is broadcast using the subsystem interface (SSI) to all Tivoli Workload Scheduler for z/OS subsystems on the z/OS image where EQQUSIN is invoked.
FILENAME
Is either CP (current plan) or JS (JCL repository).
Note:
The APPSEL values are sufficient to create a BACKUP event. The APPFLD and APPDAT sections are not used for this event type.

Selecting a workstation (CP_WS_EVENT)

You can specify these fields to identify a current plan workstation:

Table 33. CP_WS_EVENT selection fields
Field Type Size Description
SUBSYSTEM_NAME CHAR 4 Subsystem name
DESTINATION CHAR 8 Destination name
WS_NAME CHAR 4 Workstation name
SUBSYSTEM_NAME
Is the name of the tracker subsystem that the event should be reported to. If SUBSYSTEM_NAME is not specified or has the value MSTR, the event is broadcast using the subsystem interface (SSI) to all Tivoli Workload Scheduler for z/OS subsystems on the z/OS image where EQQUSIN is invoked.
DESTINATION
Is the name specified in the destination field of the workstation. This must be a user-defined destination.
WS_NAME
Is the workstation name.
Note:
You must select at least WS_NAME for a workstation event.