Scheduler services domain's generic gates
| Gate | Trace | Function | Format |
|---|---|---|---|
| DMDM | SH 0101 |
PRE_INITIALISE |
DMDM |
| XMAC | SH 0121 |
INIT_XM_CLIENT |
XMAC |
| TISR | SH 0701 |
NOTIFY |
TISR |
| KETI | SH 0701 |
NOTIFY_RESET |
KETI |
When invoked for the DMDM INITIALIZE_DOMAIN function scheduler services obtains its anchor block and initializes its various classes. This would include starting the scheduler services system task , CSHY and obtaining the name of the distributed routing exit program named on the DSRTPGM system initialization parameter.
When invoked by transaction manager via the XMAC generic gate, for INIT_XM_CLIENT SH domain obtains a user token in order to set up the correct transaction environment. For BIND_XM_CLIENT SH domain initializes recoverable resources, which includes setting the RM work token and logging a backout request for this UOW. SH domain also determines the name of the program to be invoked on the initial program link.
When invoked for the RMRO PERFORM_PREPARE function SH domain prepares to commit the pending request for the UOW by adding them to the local request queue (LRQ). On receipt of the RMRO PERFORM_COMMIT the schedule requests for this UOW are committed or destroyed, depending upon whether we are committing forwards or backwards.
When invoked for the RMDE DELIVER_RECOVERY function SH domain re-creates the pending request queues and in the case of inflight UOWs attempts to retry the associated BTS activation.
Scheduler services makes use of the TISR functions, REQUEST_ NOTIFY_INTERVAL and NOTIFY to deal with delayed schedule requests i.e. EXEC CICS(R) DEFINE TIMER calls.
The KETI interface is used when the time is adjusted, causing the time at which delayed schedule requests are to expire to be recalculated.