Rational Developer for System z, Version 7.6

Starting Debug Tool in other environments

You can start Debug Tool to debug batch programs in full-screen mode and from DB2® stored procedures.

Starting a debugging session in full-screen mode through a VTAM terminal

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:

  1. Ask your system programmer if you need to specify a VTAM network identifier to communicate with the terminal LU you will use for display. If so, make a note of the network identifier.
  2. Start two terminal emulator sessions. Connect the second emulator session to a terminal that can handle a full-screen mode debugging session through a VTAM terminal.
  3. On the first terminal emulator session, log on to TSO.
  4. On the second terminal emulator session, note the LU name of the terminal. If a session manager is displayed, exit from it.
  5. Edit the PARM string of your batch job so that you specify the TEST run time parameter in one of the following ways:

    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.

  6. Submit the batch job.
  7. On the second terminal emulator session, a full-screen mode debugging session is displayed. Interact with it the same way you would with any other full-screen mode debugging session.
  8. After you exit Debug Tool, a USSMSG10 or Telnet Solicitor Logon panel is displayed on the second terminal emulator session.
  9. Go back to step 6 if you need to restart the debugging session.

To start a debugging session in full-screen mode through a VTAM terminal with the Debug Tool Terminal Interface Manager, do the following steps:

  1. Start two terminal emulator sessions. Connect the second emulator session to a terminal that can handle a full-screen mode debugging session through a VTAM terminal, and that also starts the Terminal Interface Manager.
  2. On the first terminal emulator session, log on to TSO.
  3. On the second terminal emulator session, provide your TSO user ID and password to the Terminal Interface Manager and press Enter.
    Note:
    When you provide your user ID and password to the Terminal Interface Manager, you are not logging on TSO. You are only indicating that your user ID is to be associated with this terminal LU.

    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.

  4. Edit the PARM string of your batch job so that you specify the TEST run time parameter as follows:
    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.

  5. Submit the batch job.
  6. On the second terminal emulator session, a full-screen mode debugging session is displayed. Interact with it the same way you would with any other full-screen mode debugging session.
  7. After you exit Debug Tool, the second terminal emulator session displays the panel and messages you saw in step 3. This indicates that Debug Tool can use this session again. (this will happen each time you exit from Debug Tool).
  8. If you want to start another debugging session, return to step 5. If you are finished debugging, you can do one of the following tasks:

Starting Debug Tool from DB2 stored procedures

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.


Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)