Rocket® Enterprise Developer (formerly a product of Micro Focus or formerly a product of Open Text) documentation, created before Rocket Software acquired certain products from OpenText, may include outdated references to "Micro Focus" or "OpenText", both of which are trademarks of OpenText or its affiliates. Rocket Software is not affiliated with Micro Focus or OpenText and has since rebranded these products as Rocket® products. You may also encounter outdated links in this documentation. If you do, please contact Rocket Support (support@rocketsoftware.com) for assistance.
JCL/TSO Events and Actions
For each event, this section defines the key (but not all) inputs and outputs and the actions that can be requested for the event. The following actions apply to all events:
- The action-continue action code (which is the default action code) indicates to JCL/TSO that it should continue with normal processing as if the exit had never been invoked for that event..
- The action-shut-exit action code indicates to JCL/TSO that it should stop calling the user exit for all future events in this process for the current job or TSO session. This is intended as a performance aid. The user exit should still be coded so that it can receive future events and ignore them using the default action code action-continue.
The event names listed below correspond in part to the level-88 name assigned to the event code. Similarly, action code names listed correspond in part to the level-88 name assigned to the action code. Having access to the mfjdxit.cpy file will help your understanding of the facilities being described here.
Important: Not all of the events described in this section are currently implemented. The description
of an event indicates if it is not currently implemented. If any of the unimplemented
events would be of use in your organization, please contact your Micro Focus Sales
or Support representative.