Table 92 summarizes the scheduler services domain’s specific gate. It shows the level-1 trace point IDs of the modules providing the functions for the gate, the functions provided by the gate, and whether or not the functions are available through the exit programming interface (XPI).
Gate | Trace | Function | XPI |
---|---|---|---|
SHPR |
SH 0151 SH 0152 |
ADD_PENDING_REQUEST DELETE_PENDING_REQUEST SET_BOUND_REQUEST |
NO NO NO |
SHRT |
SH 0141 SH 0142 |
SET_EXIT_PROGRAM INQUIRE_EXIT_PROGRAM |
NO NO |
SHRQ |
SH 0111 SH 0112 |
PERFORM_RESTART_DREDGE PERFORM_REGULAR_DREDGE PERFORM_SHUTDOWN |
NO NO NO |
SHRR |
SH 0161 SH 0162 |
ROUTE_REQUEST RECEIVE_REQUEST RETRY_REQUEST |
NO NO NO |
The ADD_PENDING_REQUEST function of the SHPR gate is used to add a pending schedule request to the scheduler services queue associated with this UOW. The pending schedule requests are hardened to the scheduler services local request queue (LRQ) as part of syncpoint processing.
YES|NO
OK|EXCEPTION|INVALID|DISASTER|KERNERROR|PURGED
The DELETE_PENDING_REQUEST of the SHPR gate is used to delete a pending request queue.
OK|EXCEPTION|PURGED|INVALID|DISASTER|KERNERROR
RESPONSE | Possible REASON values |
---|---|
EXCEPTION | REQUEST_NOT_FOUND |
The SET_BOUND_REQUEST function of the SHPR gate is used to update the schedule request to indicate that a process and/or activity has completed.
YES|NO
YES|NO
OK|EXCEPTION|INVALID|DISASTER|KERNERROR
RESPONSE | Possible REASON values |
---|---|
EXCEPTION | REQUEST_NOT_FOUND |
The SET_EXIT_PROGRAM function of the SHRT gate is used to alter the distributed routing exit program, initially named on the DSRTPGM system initialisation parameter. The sysid of the local system is passed during CICS® initialisation.
OK|EXCEPTION|INVALID|DISASTER|KERNERROR|PURGED
RESPONSE | Possible REASON values |
---|---|
DISASTER | ABEND |
The INQUIRE_EXIT_PROGRAM function of the SHRT gate is used to return the name of the distributed routing exit program, initially named on the DSRTPGM system initialisation parameter.
OK|EXCEPTION|INVALID|DISASTER|KERNERROR|PURGED
RESPONSE | Possible REASON values |
---|---|
DISASTER | ABEND |
The PERFORM_RESTART_DREDGE of the SHRQ gate is used to initiate the dredging of expired schedule requests on the local request queue (LRQ) after a CICS system restart.
OK|EXCEPTION|INVALID|DISASTER|KERNERROR|PURGED
The PERFORM_REGULAR_DREDGE function of the SHRQ gate initiates the periodic dredging of expired schedule requests on the local request queue (LRQ).
OK|EXCEPTION|INVALID|DISASTER|KERNERROR|PURGED
The PERFORM_SHUTDOWN function of the SHRQ gate is used to stop dredging of schedule requests on the local request queue (LRQ), preventing any further CICS BTS work from being initiated.
OK|EXCEPTION|INVALID|DISASTER|KERNERROR|PURGED
The ROUTE_REQUEST function of the SHRR gate is used to identify a target region to which a schedule request should be routed.
OK|EXCEPTION|INVALID|DISASTER|KERNERROR|PURGED
RESPONSE | Possible REASON values |
---|---|
EXCEPTION |
NO_REQUEST_FOUND REQUEST_BUFFER_TOO_SMALL NO_SYSTEM |
The RECIEVE_REQUEST function of the SHRR gate is used to receive a schedule request once it has been routed to the target region.
OK|EXCEPTION|INVALID|DISASTER|KERNERROR|PURGED
RESPONSE | Possible REASON values |
---|---|
EXCEPTION | INVALID_REQUEST_RECEIVED |
The RETRY_REQUEST function of the SHRR gate is used obtain another target region if the initial attempt at routing the schedule request fails.
SYSID_NOT_FOUND|SYSID_OUT_OF_SERVICE|NO_SESSIONS|
ALLOCATE_REJECTED|QUEUE_PURGED|FUNC_NOT_SUPPORTED|
LEGERR|PGMIDERR|INVREQ|NOTAUTH|TERMERR
YES|NO
OK|EXCEPTION|INVALID|DISASTER|KERNERROR|PURGED
RESPONSE | Possible REASON values |
---|---|
EXCEPTION |
NO_REQUEST_FOUND REQUEST_BUFFER_TOO_SMALL NO_SYSTEM |