For each event, this section defines the key (but not all) inputs and outputs and the actions that can be requested for the event.
Event-specific data
The following action applies to all events:
- The action-continue action code (which is the default action code) indicates to the system that it should continue with normal processing as if the exit had never been invoked for that event.
The event names listed below correspond in part to the level-78 name assigned to the event code. Similarly, action code names listed correspond in part to the level-78 name assigned to the action code. Having access to
mfjdsxit.cpy,
mfjyooda.cbl
and
subsys1b.jcl files will help your understanding of the facilities being described here.
This event indicates that the source for the DD is about to be allocated. The purpose of this event is to allow the subsystem exit to verify and/or modify the DD that is being processed.
This event and Event-before-PGM-call occur in the child process. All other events occur in the parent process. Your exit cannot remember any events that occurred in the parent process.
Data available for this event includes:
- The subsystem-subparameter string length
- A pointer to the subsystem-subparameter string
- A dataset name if available
- The type of dataset (permanent, SYSOUT, etc.)
The exit can view or change the information and request that the system use the changed information. The information that can be changed includes:
- The subsystem-subparameter string length
- The subsystem-subparameter string
- The type of dataset
Actions that can be requested:
