Specifying session defaults

You can set or override the defaults to be used during debugging sessions with option 0 (DEFAULTS) on the Code Debug TSO Primary Menu. The Code Debug TSO Defaults Menu shown in following figure is displayed. The defaults you specify remain in effect across all Code Debug TSO debugging sessions.

The Defaults menu

Code Debug TSO Defaults Menu

From this menu you can select to:

1. Modify Code Debug PF key settings used during your debugging session.
2. Specify color selections on a color terminal.
3. Specify session defaults, such as the default dsname high-level qualifier, and enable the jump function.
4. Select a profile to be used and tailor user profiles for all your different libraries and environments.

Specifying PF key definitions

Code Debug TSO has two sets of PF keys. When using Code Debug TSO, you use ISPF PF key settings. These PF keys are used throughout the product, except when you are within a debugging session. Then you use Code Debug debugging session PF keys.

To modify the Code Debug debugging session PF key settings, select option 1 (TEST PF KEYS). The Code Debug PF Key Definitions and Labels - Primary Keys screen shown in Code Debug PF Key Definitions and Labels - Primary Keys Screen is displayed. For terminals with 24 PF keys, press Enter to display the CODE DEBUG PF Key Definitions and Labels - Alternate Keys screen shown in Code Debug PF Key Definitions and Labels - Alternate Keys Screen.

Code Debug PF Key Definitions and Labels - Primary Keys Screen 

Code Debug PF Key Definitions and Labels - Alternate Keys Screen 

Changes can be made to the PF key designations by typing over the appropriate fields. PF keys can also be labeled to have a descriptive name as well as the actual command mapped to the key.

Specifying screen colors

The next option on the Defaults Menu gives you color defaults for use with a color terminal. A full range of colors is offered for the various display areas on the screen, whether in ISPF or the Source display. Both intensity and highlight choices are available for each color. This option lets you change color, highlight, and intensity on all ISPF, source, and tutorial screens.

Select option 2 (COLORS) from the Defaults Menu to access the ISPF Color Defaults screen shown in following figure. You can also enter the COLOR command anywhere within Code Debug TSO to invoke this screen.

ISPF Color Defaults Screen

The entry values are listed on the screen. Note that color, highlight, and intensity choices can be indicated by the first character.

The following indicates some guidelines regarding the use of color:

• Colors take affect only on a 3279-B or ISPF-supported 7-color terminal.
• Enter the ON or DEMO command on the Color Default screens for an example of its use.
• Enter the OFF or RESTORE command to restore standard ISPF color settings.
• Intensity is ignored on IBM color terminals.
• Color is ignored on monochrome terminals.

Entering S or SOURCE from the ISPF Color Defaults screen invokes the Source Color Defaults/1 screen, shown in following figure. You can also enter the COLOR S command anywhere within Code Debug TSO, except within a dialog box debugging session, to invoke this screen.

There are three screens for source color defaults. Press Enter without any changes to cycle through the screens.

Source Color Defaults/1 Screen

Typing ON or DEMO on the Source Color Defaults screen causes the COLOR, HIGHLIGHT, and INTENSITY fields to automatically change (see to following figure) to the following:

Changing Source Color Defaults

Typing OFF or RESTORE causes the COLOR, HIGHLIGHT, and INTENSITY fields on the Source Color Defaults/1 screen to return to the default values shown in follwoing figure.

Entering T or TUTORIAL from the ISPF Color Defaults screen invokes the Tutorial Color Defaults screen. You can also enter the COLOR T command anywhere within Code Debug TSO to invoke this screen.

Tutorial Color Defaults Screen 

Typing ON or DEMO in the Tutorial Color Defaults screen (above figure) causes the COLOR, HIGHLIGHT, and INTENSITY fields to automatically change (see to following figure):

Changing Tutorial Color Defaults

Typing OFF or RESTORE causes the COLOR, HIGHLIGHT, and INTENSITY fields on the Changing Tutorial Color Defaults screen (above figure) to return to the default values shown in Tutorial Color Defaults Screen.

Specifying Other Default Values

Select option 3 (OTHERS) from the Defaults Menu to access the Others screen for specifying other default values as shown in following figure. This screen does two things:

1. Sets up a default prefix for your dsname high-level qualifier that will be automatically appended to all dsnames not enclosed in quotes.
2. Enables the jump function.

Specifying Other Default Values

The fields on the Others screen are as follows:

DSNAME HIGH-LEVEL QUALIFIER

The string entered here is automatically prefixed to any dsname not enclosed in quotes. Your user ID is the default value pre-filled in this field.

If your site requires a high-level qualifier that is not your user ID, enter that qualifier in the Prefix field. This will become your default high-level qualifier. Do not blank out this field. The prefix is used as the high-level qualifier in names generated by Code Debug TSO for the session log and script data sets. Therefore, unless you explicitly name them, any attempt to allocate these data sets will fail. Also, in many sites, a data set cannot be cataloged without a user ID.

ENABLE JUMP FUNCTION

Turning on the jump function (YES, the default) lets you move from one screen to another without passing through the Primary Menu. The jump function is the same as that provided inside ISPF.

The equal sign (=) is used to take you to a Primary Menu. Entering =2 takes you to option 2 of the Primary Menu. If the jump function is turned on (enabled) and the equal sign convention is used, you are referred to the Code Debug TSO Primary Menu. If the jump function is off, you are referred to the ISPF Primary Menu.

Specifying user profiles

The user profile contains all the changes you make to the Code Debug defaults. This includes installation defaults established by your system programming staff, and most importantly, environment parameters and setup options for your debugging session.

Select option 0 (Defaults) from the Primary Menu to display the Defaults Menu. Select option 4 (PROFILE) from the Defaults Menu to access the Code Debug Profile screen shown in following figure. This screen can also be reached by entering a question mark (?) as a profile identifier on the Primary Menu or by using the PROFILE command from a test screen. See to Using the PROFILE Command for additional information. This screen lets you:

• Switch to a new profile
• Change the description of a profile
• Make a particular profile current
• Delete a profile
• Copy a profile
• Rename a profile
• Use a profile.

Code Debug Profile Screen

The Profile screen has a fixed (body) area and a scrollable area. The fixed body area has a command line, a list of available commands, a sort indicator, and the Current Profile.

You can perform several operations in this area.

1. Use the MERGE command to merge another user’s profile into your profile library or use the LOCATE, FIND, or RFIND command to reposition the scrollable area.
2. Use the PROFILE field to:
   
   • Switch to a new profile: To do this, type over the profile identifier with a new identifier. The identifier can be any 8-character name or number. When you change the profile specified in this field, the profile change becomes effective immediately. This lets you execute debugging sessions with different environments, load libraries, levels of systems software, and so on.
   • Change the description of a profile: To do this, type over the DESCRIPTION field. You can combine this with selecting a new profile, in which case, the description is associated with the new profile.
3. Use the Sort Last Modified field to change the order of profile entries.
   
   • N (default) - displays profile entries alphabetically in ascending order.
   • Y - displays profile entries by the date the profile was last modified in descending order. Modifying setup information unique to a single profile, modifying a profile description, or changing environments for a profile constitute a change. The LOCATE command will automatically be disabled when profile entries are sorted by date last modified.

The scrollable area of the screen has a line for each existing profile and includes a line command area. An asterisk (*) preceding a profile identifier indicates the current profile. You can use the following line commands:

• S (Select)—to make a particular profile current. You can combine this command with a copy function by entering the identifier of the new profile in the NEW NAME field. This makes the new profile the current profile.
• D (Delete)—to delete a profile.
• C (Copy)—to copy a profile. Enter the identifier of the new profile in the NEW NAME field. Press Enter, and a new profile with the given identifier is created. If you also type over the DESCRIPTION field, the new description goes only with the new profile. If the new profile identifier already exists, you must verify that you really want to overwrite the profile.
• R (Rename)—to rename a profile. Enter the new profile identifier in the NEW NAME field. You can also change the description by typing over the DESCRIPTION field. Press Enter, and the profile is renamed.
• U (Use)—to use a profile. This line command takes you directly to Code Debug TSO with the selected profile.
• I (Info)—to display profile setup information.

Using the MERGE Command

The MERGE command copies profiles from an alternate profile data set to the current profile data set. See Selecting Alternate Profiles (MERGE) for more information. The profile entries on the Merge Profile screen are sorted in the same manner as selected on the Profile screen.

Using the LOCATE Command

The LOCATE command positions the list of profiles to the profile name preceding the name you specify. L and LOC are acceptable abbreviations for the LOCATE command. The LOCATE command will automatically be disabled when profile entries are sorted by date last modified.

Using the FIND Command

The FIND command will position the profile table at the profile name whose requested character string matches some or all of the characters in the profile name or description. F is an acceptable abbreviation for the FIND command.

Using the RFIND Command

The RFIND command will position the profile table at the profile name whose requested character string from the previous FIND command matches some or all of the characters in the Profile name or Description.

Using the PROFILE Command

The PROFILE command is available on the test screens to change the current profile without leaving the test screen itself. You can also use the PROFILE command from the Primary Menu. The syntax of the command is:

Where xxxxxxxx is the profile identifier. Use this command as follows:

1. Enter the command and a profile identifier to change to another profile. If the profile identifier does not currently exist, the Code Debug Profile screen shown in Code Debug Profile Screen is displayed so that you can enter the description for the new profile or select a different profile identifier.
2. Enter the command without an identifier or with a question mark (?) to go to the Code Debug Profile screen shown in Code Debug Profile Screen.

When you leave the Profile screen, you are returned to the test screen, and the profile you selected is displayed in the message area. If you selected a new profile (i.e., a profile that did not currently exist), the Environments Menu is displayed.

Displaying Test Session Settings

You can use SET commands to override a number of Code Debug TSO test session defaults in order to achieve your debugging objectives. For example, you can control whether or not to intercept program abends, control the speed of program trace, or control the way Code Debug TSO deals with modules. You can control numerous Code Debug functions including display settings, session log options, and PF key settings. For full descriptions of all SET command parameters, see to the Command-and-syntax-reference.

The current status of your test session settings can be displayed by entering SHOW SETS or SHOW OPTIONS on the command line. Based on your current settings and testing environment, Code Debug will display a list similar to the one shown in SHOW SET/OPTIONS First Screen through SHOW SET/OPTIONS Fifth Screen. Some values are set only for the duration of the test session, while others are maintained across test sessions. A few values are environmental settings implemented by other methods and have no corresponding SET command.

All the settings that affect module management must be in effect before loading your program into memory. This can be done by editing an INCLUDE script that contains the SET commands and specifying it on the test screen as an initial script before entering the test session.

SHOW SET/OPTIONS First Screen 

SHOW SET/OPTIONS Second Screen

SHOW SET/OPTIONS Third Screen

SHOW SET/OPTIONS Fourth Screen

SHOW SET/OPTIONS Fifth Screen