Debugging Db2 programs in full-screen mode
In full-screen mode, you can decide at debug time what debugging commands you want issued during the test.
Using z/OS® Debugger Setup Utility (DTSU)
The z/OS Debugger Setup Utility is available through IBM® z/OS Debugger Utilities.
- Start DTSU by using the TSO command or the ISPF panel option, if available. Contact your system administrator to determine if the ISPF panel option is available.
- Create a setup file. Remember to select the Initialize New setup file for Db2 field.
- Enter appropriate information for all the fields. Remember to enter the proper commands in the DSN command options and the RUN command options fields.
- Enter the
RUN
command to run the Db2® program.
Using TSO commands
- Ensure that either you or your system programmer has allocated all the required data sets through a CLIST or REXX EXEC.
- Issue the
DSN
command to start Db2. - Issue the
RUN
subcommand to execute your program. You can specify theTEST
runtime option as a parameter on theRUN
subcommand. The following example starts a COBOL program:RUN PROG(progname) PLAN(planname) LIB('user.library') PARMS('⁄TEST(,*,;,*)')
The following example starts a non-Language Environment® COBOL program:RUN PROG(EQANMDBG) PLAN(planname) LIB('user.library') PARMS('progname,⁄TEST(,*,;,*)')
Using TSO/Call Access Facility (CAF)
- Link-edit the CAF language interface module DSNALI with your program.
- Ensure that the data sets required by z/OS Debugger and your program have been allocated through a CLIST or REXX procedure.
- Enter the
TSO CALL
commandCALL 'user.library(name of your program)'
, to start your program. Include theTEST
run-time option as a parameter in this command.
In full-screen mode using a dedicated terminal without Terminal Interface Manager
- Specify the
MFI%LU_name
parameter as part of theTEST
runtime option. - Follow the other requirements for debugging Db2 programs either under TSO or in batch mode.
In full-screen mode using the Terminal Interface Manager
- Specify the
VTAM%userid
parameter as part of theTEST
runtime option. - Follow the other requirements for debugging Db2 programs either under TSO or in batch mode.
After your program has been initiated, debug your program by issuing the required z/OS Debugger commands.
Note: If your source does not come up in z/OS Debugger when
you launch it, check that the listing or source file name corresponds
to the MVS library name, and
that you have at least read access to that MVS library.
Refer to the following topics for more information related to the material discussed in this topic.
- Related tasks
- Preparing a Db2 program
- Starting z/OS Debugger for programs that start outside of Language Environment
- Related references
- DB2® UDB for z/OS Administration Guide