Make the modifications necessary to implement your preferred method of starting z/OS Debugger
In this topic, you will use the information you gathered after completing 2 in Planning your debug session and Choosing a method or methods for starting z/OS Debugger to write the
TEST runtime options string, then save that string in the appropriate location.
You might have to write several different TEST runtime options strings. For
example, the TEST runtime options string that you write for your CICS® programs might not be the same TEST runtime options
string you can use for your IMS programs. For
this situation, you might want to use Table 1 to record the string you
want to use for each type of program you are debugging.
Test runtime options string (for example,
TEST(ALL,,,MFI%SYSTEM01.TRMLU001:)) |
|
|---|---|
| TSO | |
| JES batch | |
| UNIX System Services | |
| CICS | |
| Db2® | |
| Db2 stored procedures (PROGRAM TYPE=MAIN) | |
| Db2 stored procedures (PROGRAM TYPE=SUB) | |
| IMS TM | |
| IMS batch | |
| IMS BTS |
If you are not familiar with the format of the TEST runtime option string, see
the following topics:
- Description of the TEST runtime option in IBM z/OS Debugger Reference and Messages
- Writing the TEST runtime option string
After you have written the TEST runtime option strings, you need to save them in
the appropriate location. Using the information you recorded in Table 1, review the following list, which directs you to the instructions on where and how to save the
TEST runtime options strings:
- Through the EQAD3CXT user exit routine
- See Specifying the TEST runtime options through the Language Environment user exit.
- Through the DFSBXITA user exit routine
- See Setting up the DFSBXITA user exit routine.
- Using the DTCN transaction
- See Creating and storing a DTCN profile.
- Using the Db2 catalog
- See Preparing a Db2 stored procedures program.
- By coding a call to CEETEST, __ctest(), or PLITEST
- See one of the following topics:
- Through CEEUOPT or CEEROPT
- See one of the following topics:
- Using the CEEOPTS DD statement in JCL or CEEOPTS allocation in TSO
- Use the JCL for Batch Debugging option in IBM® z/OS® Debugger Utilities.
- Using the parms on the EXEC statement when you start your program
- When you specify the EXEC statement, include the
TESTruntime option as a parameter. - Use the parms on the RUN statement when you start your program
- When you specify the RUN statement, include the
TESTruntime option as a parameter. - Using the parms on the CALL statement when you start your program
- See the example in Starting z/OS Debugger.
- Through the EQASET transaction
- See Running the EQASET transaction for non-Language Environment IMS MPPs.
- Through the EQANMDBG program
- See Starting z/OS Debugger for programs that start outside of Language Environment.