Code Debug TSO environment test screens

The first time you invoke an Code Debug test session using option 2 (TSO) on the Primary Menu, the Code Debug TSO Environments Menu shown in following figure is displayed.

Each option on the Environments Menu accesses a test screen. The environment test screens are used to specify the name of the program to be tested and other parameters associated with the program and the test session. For example, if you are testing a program in a standard environment with no special services, you would select option 1 (Standard). The Standard Environment Test screen shown in Standard Test Screen – Environments Menu - Option 1 is displayed.

Code Debug TSO Environments Menu

The structure diagram in following figure shows the menu hierarchy of the execution environments you can select.

Diagram of the Execution Environments

Each option in above figure represents the test screen for the environment. The test screens let you specify the environment parameters for initiating a debugging session.

Some test screens have commands that will access submenus. The commands that may appear on a test screen are described as follows:

SE (SETUP)

Displays the Setup Menu. The options on the Setup Menu display submenus that are used to override the default values defined at your site. You can specify the load libraries, DDIO files, test script libraries, session log and test script data set disposition, DSN libraries, and PANEXEC load libraries. The SETUP command is valid on all test screens.

PROFile (PROFILE)

Displays a list of current user profiles that retain information about Code Debug test environments. You may Select (S), Delete (D), Copy (C), Rename (R), or Use (U) the profiles stored in the displayed file by entering the appropriate line command in the CMD (Command) field. You may also utilize the only Primary Command, the Merge command. This command lets you copy other user’s profiles to your own profile.

L, LO (LOG)

Browses the session log. The session log file contains a record of the commands that were entered during the debugging session and the responses to them.

The LOG command is valid on all the test screens where it is displayed. However, the session log cannot be viewed until you return to the test screen after testing has been performed.

SC (SCRIPT)

Browses and edits the test script created during the debugging session. A sequential test script file contains commands recorded during the debugging session. The generated test script must be moved to a member of an INCLUDE library for it to be executed.

The SCRIPT command is valid on all test screens where it is displayed, but the script cannot be viewed until you return to the test screen after testing has been performed.

BT (BTSIN)

Displays a list of BTS transactions that you can select to debug. Any transactions selected through the use of the BTSIN command are automatically entered on the BTS or Hogan IMSPEM screen.
The BTSIN command is valid only on the BTS and Hogan IMSPEM test screens.

SY (SYSIN)

Displays the Hogan SYSIN data set, so you can edit the control cards. The SYSIN command is valid only on the Hogan test screens.

IN (INTER)

Displays a list of transactions that are intercepted by Code Debug IMS.

UP (UP)

Scrolls toward the top of your screen. Scrolling up rolls the screen downward, bringing the previous section of the data into view.

DO (DOWN)

Scrolls toward the end of your screen. Scrolling down rolls the screen upward, bringing the following section of the data into view.

D (DOCEDIT)

Browses and edits the document data set. The document data set is a sequential file that contains JCL used to collect site information for later transfer to Code Debug TSO Technical Support.

The DOCEDIT command is valid on all test screens where it is displayed, but the JCL cannot be viewed unless the DOCUMENT command has been entered during the test session.

This section provides more information about the following topics: