Starting z/OS Debugger from a program

The instructions in this section apply to programs that run in Language Environment®. For programs that do not run in Language Environment, refer to the instructions in Starting z/OS Debugger for programs that start outside of Language Environment.

z/OS Debugger can also be started directly from within your program using one of the following methods:

  • Language Environment provides the callable service CEETEST that is started from Language Environment-enabled languages.
  • For C or C++ programs, you can use a __ctest() function call or include a #pragma runopts specification in your program.
    Note: The __ctest() function is not supported in CICS®.
  • For PL/I programs, you can use a call to PLITEST or by including a PLIXOPT string that specifies the correct TEST run-time suboptions to start z/OS Debugger.

However, you cannot use these methods in Db2® stored procedures with the PROGRAM TYPE of SUB.

If you use these methods to start z/OS Debugger, you can debug non-Language Environment programs and detect non-Language Environment events only in the enclave in which z/OS Debugger first appeared and in subsequent enclaves. You cannot debug non-Language Environment programs or detect non-Language Environment events in higher-level enclaves.

To start z/OS Debugger using these alternatives, you still need to be aware of the TEST suboptions specified using NOTEST, CEEUOPT, or other "indirect" settings.

Refer to the following topics for more information related to the material discussed in this topic.