Scenario A: Running IMS and managing TEST runtime options with a user exit

Do the following steps to enable this scenario:

Include the z/OS® Debugger hlq.SEQAMOD¹ data set and the Language Environment® CEE.SCEERUN² runtime library in the STEPLIB concatenation of your IMS region.
To give IMS users enough time to run and debug their applications, increase the time-out limit in the message-processing region (MPR) region to 1440.
If you need to change the naming pattern of the data set containing the user's TEST runtime options, see the following topics for details:
- Specifying the TEST runtime options through the Language Environment user exit
- Customizing z/OS Debugger User Exit Data Set
The user will use DTU option 'z/OS Debugger User Exit Data Set' to set the TEST runtime options they want.
If the IMS transaction is initiated from the web or MQ gateway, it is run with a generic ID. z/OS Debugger supports a cross reference table to tie such a transaction to a user's ID. To set the name of that cross reference table, see the following topics for details:
- Specifying the TEST runtime options through the Language Environment user exit
- Customizing IMS Transaction and User ID Cross Reference Table
The user will use DTU option 'IMS Transaction and User ID Cross Reference Table' to specify the transaction name to user ID cross reference.
See Specifying the TEST runtime options through the Language Environment user exit and Customizing z/OS Debugger User Exit Data Set for information about customizing the user exit (if needed).
If the IMS transaction is initiated from the web or MQ gateway, it is run with a generic ID. If your site has this situation, see Activate the cross reference function and modifying the cross reference table data set name for information about customizing the user exit to enable a cross reference table and Customizing IMS Transaction and User ID Cross Reference Table for setting up IBM® z/OS Debugger Utilities so that the user can access the table.

¹ Add hlq.SEQAMOD to STEPLIB only if it is not already in the system search path (for example, link list). If you create a custom EQAOPTS (as described in EQAOPTS commands) that is not stored in hlq.SEQAMOD, then place the data set containing it in STEPLIB (ahead of hlq.SEQAMOD if it is in STEPLIB). hlq.SEQAMOD must be placed before any other library in the STEPLIB that contains CEEEVDBG for z/OS Debugger to get control of a debug session.

² Add CEE.SCEERUN to STEPLIB only if it is not already in the system search path (for example, link list). If you create a private copy of the z/OS Debugger Language Environment user exit for IMS that is linked into CEEBINIT (as described in Specifying the TEST runtime options through the Language Environment user exit), then place the data set containing it in STEPLIB (ahead of CEE.SCEERUN if it is in STEPLIB).