You can start Debug Tool to debug batch programs in full-screen mode and from DB2® stored procedures.
You can debug batch programs interactively by using a full-screen mode debugging session through a VTAM® terminal. Before you start this debugging session, contact your system administrator to verify that your system was customized to support this type of debugging session, and for instructions on how to access a terminal that supports this mode.
You need to decide whether you will use the Debug Tool Terminal Interface Manager. The Debug Tool Terminal Interface Manager enables you to associate a user ID with a specific VTAM terminal, which removes the need to update your runtime parameter string whenever the VTAM terminal LU name changes.
To start a debugging session in full-screen mode through a VTAM terminal without the Debug Tool Terminal Interface Manager, do the following steps:
TEST(,,,MFI%luname:*)
TEST(,,,MFI%network_identifier.luname:*)
Place a slash (/) before or after the parameter, depending on your programming language. luname is the VTAM LU name of the second terminal emulator. network_identifier is the name of the VTAM network node that contains luname.
To start a debugging session in full-screen mode through a VTAM terminal with the Debug Tool Terminal Interface Manager, do the following steps:
A panel similar to the following panel is then displayed on the second terminal emulator session:
DEBUG TOOL TERMINAL INTERFACE MANAGER
EQAY001I Terminal TRMLU001 connected for user USER1
EQAY001I Ready for Debug Tool
PF3=EXIT PF12=LOGOFF
The terminal is now ready to receive a Debug Tool full-screen mode through a VTAM terminal session.
TEST(,,,VTAM%userid:*)
Place a slash (/) before or after the parameter, depending on our programming language. userid is the TSO user ID that you provided to the Terminal Interface Manager.
Before you run the stored procedure, verify that you have completed all the instructions in Preparing a DB2 stored procedures program.
To verify that the stored procedure has started, enter the following DB2 Display command, where xxxx is the name of the stored procedure:
Display Procedure(xxxx)
If the stored procedure is not started, enter the following DB2 command:
Start procedure(xxxx)
If Debug Tool or the remote debugger do not start when the stored procedure calls them, verify that you have correctly specified connection information (for example, the TCP/IP address and port number) in the Language Environment EQADDCXT exit routine or the DB2 catalog.
Refer to the following topics for more information related to the material discussed in this topic.