Code Debug TSO utilities

The Code Debug TSO utility functions are accessed by selecting option 5 on the Primary Menu. The Code Debug TSO Utilities Menu shown in following figure is displayed. From this menu, you can select the following functions:

1. Display the memory available for debugging (REGION SIZE).
2. Display the ddnames and dsnames currently allocated to your TSO session (LIST ALLOCATES).
3. Execute CSS Source Listing File Facility (CSS UTILITIES).
4. Display the status of the Db2 Stored Procedure Intercept.
5. Display the status of the IMS Intercept.
6. Display the status of the Multi-Batch Intercept.
7. Merge profiles from other user IDs (MERGE).
8. Prepare JCL for Selective Delete Utility (SELECTIVE DELETE).

Code Debug TSO Utilities Menu

Displaying Available Memory (REGION SIZE)

Selecting option 1 (REGION SIZE) on the Utilities Menu will display an example of a condensed screen of memory and storage specifications available for debugging. This menu screen is similar to the screen displayed when you enter a SHOW REGION command from within an Code Debug TSO debugging session. The condensed storage specification screen is displayed in following figure.

Code Debug TSO Storage Specifications

The following lines give you some idea as to what the memory requirements are for the different Code Debug TSO execution environments:

If you are using DATACOM/DB, IDMS/DB, or System 2000, the recommended memory is 2,000,000 bytes.

The listed figures are approximate; your actual memory requirements will vary depending on the size of the program being debugged. The amount of memory required by Code Debug TSO is related to the number of statements in each program that has a DDIO loaded into memory.

Displaying File Allocations (LIST ALLOCATES)

Option 2 (LIST ALLOCATES) on the Utilities Menu displays the files allocated to your TSO debugging session. The same display can be reached by entering the ALC command from within an Code Debug TSO debugging session. The following line commands are available, entered in the SEL column:

The SHOW ALLOCATES command displays the same information in essentially the same format, but the line commands are not available.

Following figure (List Allocates Screen) is a sample of the output from this function.

List Allocates Screen

DDIO File Facility

A DDIO file is required during compile time to store source listings containing the information necessary for Code Debug TSO to reference various elements of your program during testing.

Option 3 (DDIO FILE FACILITY) on the Utilities Menu invokes the CSS Utilities Source Listing File Facility. This facility enables you to:

• create and format a DDIO file, a shared directory, or an LP database
• obtain format information about the file
• copy, move, export, or import files
• obtain a list of file members
• browse, delete, print, lock, or unlock members from a list of file members.

See the Common Shared Services User/Reference Guide for more information.

Viewing Status of Db2 Stored Procedures Intercept

This utility provides information on the status of the Code Debug Db2 Stored Procedures Intercept. Typical output from the utility is shown in following figure.

Db2 Stored Procedures Intercept Status

Viewing Status of IMS Intercept

This utility provides information on the status of the Code Debug IMS Intercept. Typical output from the utility is shown in following figure.

IMS Intercept Status

Viewing Status of Multi-Batch Intercept

This utility provides information on the status of the Code Debug Multi-Batch Intercept. Typical output from the utility as shown in above figure.

Multi-Batch Intercept Status

Selecting Alternate Profiles (MERGE)

Option 7 on the Utilities Menu merges profiles from other user IDs into your personal profile. The Select Alternate Profiles screen shown in following figure is displayed.

Select Alternate Profiles Screen

The option on this screen is:

DSNAME

Enter the name of the ISPF profile data set in the DSNAME field to identify the source of the Code Debug TSO profiles. Entering a data set name results in the display of the Merge Profile screen—a scrollable list from which you can make your selection.

After you have typed the name of the ISPF profile data set in the DSNAME field, press Enter to display the Merge Profile screen (following figure).

Merge Profile Screen

The list provided on the Merge Profile screen (above figure) displayed above shows the alternate profiles that exist in another user’s Code Debug profile table. To merge one or more of these profiles into your profile, use the Select command. By using SELECT, you can change the profile name and/or description by simply typing new values. Profile entries are sorted in the same manner as selected on the Profile screen. See Specifying User Profiles for more information.

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. See Specifying User Profiles for more information.

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.