Current plan operation event object

This option is valid for the current plan operation event object:

CREATE request with key type SAME.

The default key type is SAME.

Table 1. CP_OPER_EVENT Object Fields
Field	Type	Len	Description	APPSEL	APPFLD
SUBSYSTEM_NAME	CHAR	4	Subsystem name	O	N
WS_NAME	CHAR	4	Workstation name	O	N
JOBNAME	CHAR	8	Job name	O	N
APPL_ID	CHAR	16	Application ID	O	N
OPER_NUM	BIN	15	Operation number (decimal 1–99)	O	N
APPL_IA_DATE	CHAR	6	Input arrival date	O	N
APPL_IA_TIME	CHAR	4	Input arrival time	O	N
FORM_NUMBER	CHAR	8	Form number for operations at print workstations	O	N
CLASS	CHAR	1	SYSOUT class for operations at print workstations	O	N
OPER_TOKEN	CHAR	8	Operation token	O	N
STATUS	CHAR	1	New status: C Complete E Ended in error I Interrupted Q Extended status of a started operation (S) is Q (queued awaiting execution) S Started T Extended status of a started operation (S) is S (operation is executing) X Reset the current status for this operation	N	O
ERROR_CODE	CHAR	4	Error code (for new status E)	N	O
ACT_DUR	CHAR	4	Actual duration HHMM (for new status C or E)	N	O
EV_CREATION_DATE	CHAR	4	Event creation date. The field format is 00YYDDDF for dates in the 20th century, and 01YYDDDF for dates in the 21st century. Default is current date	N	O
EV_CREATION_TIME	BIN	31	Event creation time (100 * secs). Default is current time	N	O
JOB_NUMBER	CHAR	5	Job number	N	O

Note:

To select an operation, specify at least OPER_TOKEN, or WS_NAME with either JOBNAME or APPL_ID. The remaining values can be initialized to zeros or blanks.
OPER_TOKEN is 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 identify the operation. OPER_TOKEN is valid only for operations at workstations that have a user-defined destination.
SUBSYSTEM_NAME is the name of the HCL Workload Automation for Z subsystem that the event should be reported to. It is used only to select the target for the event and is not stored in the representation of the object.
If you specify SUBSYSTEM_NAME in APPSEL but do not provide a value in the APPVAL section, or you specify MSTR, the event is broadcast to all HCL Workload Automation for Z subsystems on the same z/OS image. If you do not specify SUBSYSTEM_NAME, the event is reported to the HCL Workload Automation for Z subsystem that owns the target LU.

If your ATP invokes the EQQUSIN subroutine directly, and you do not specify SUBSYSTEM_NAME, the event is broadcast to all HCL Workload Automation for Z subsystems on the same z/OS image.
If you do not provide enough information to uniquely identify the operation, and HCL Workload Automation for Z finds more than one operation that matches the criteria you specified, HCL Workload Automation for Z must determine the most applicable operation to update. HCL Workload Automation for Z selects the operation from operations in status R, A, *, S, I, or E, 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.
In the APPFLD section, you must specify at least STATUS.
JOB_NUMBER is a number that you can provide for the job. It is valid only for operations at general automatic workstations and workstations that have a user-defined destination. Do not specify JOB_NUMBER for operations that are submitted through a tracker.