Starting z/OS Debugger for non-Language Environment programs under CICS

You can start z/OS® Debugger to debug a program that does not run in the Language Environment® run time by using the debug profile transaction DTCN.

To debug CICS® non-Language Environment programs, the z/OS Debugger non-Language Environment Exits must have been previously started.

To debug non-Language Environment assembler programs or non-Language Environment COBOL programs that run under CICS, you must start the required z/OS Debugger global user exits before you start the programs. z/OS Debugger provides the following global user exits to help you debug non-Language Environment applications: XPCFTCH, XEIIN, XEIOUT, XPCTA, and XPCHAIR. The exits can be started by using either the DTCX transaction (provided by z/OS Debugger), or using a PLTPI program that runs during CICS region startup. DTCXXO activates the non-Language Environment Exits for z/OS Debugger in CICS. DTCXXF inactivates the non-Language Environment Exits for z/OS Debugger in CICS.

If you want to start z/OS Debugger when a non-Language Environment LOAD of an assembler program is done, one of the following is required:
  • The load module program resource is defined to CICS when the language is assembler.
  • The EQAOPTS command CICSASMPGMND value is YES.