Space announcement This documentation space provides the same content as before, but the organization of the content has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Code Debug TSO utilities for C

The Code Debug TSO utility functions are accessed by selecting option 5 on the Primary Menu. The Utilities Menu shown in the 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

-------------------------------- UTILITIES MENU --------------------------
OPTION ===>


  1  REGION SIZE           - Display memory available for testing
  2  LIST ALLOCATES        - Display files allocated to your test session
  3  CSS UTILITIES         - Execute CSS Source Listing File Facility
   4  DB2SP INTERCEPT       - Display status of DB2 Stored Procedure Intercept
  5  IMS INTERCEPT         - Display status of IMS Intercept
  6  MULTI-BATCH INTERCEPT - Display status of Multi-Batch Intercept
  7  MERGE                 - Merge profiles from alternate users
  8  SELECTIVE DELETE      - Prepare JCL for Selective Delete Utility




          Press ENTER to process  or  enter END command to terminate

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 a Code Debug TSO debugging session. The condensed storage specification screen is displayed.

Code Debug TSO Storage Specifications

 .-----------------------------------------------------------------.
 |                     Percent TSO storage used                    |
|        ----10---20---30---40---50---60---70---80---90---        |
 |       [                                                 ]       |
|  <16m  *****                                                    |
|  >16m  *                                                        |
|                     Current usage                               |
|                  0.44     Mb Below ( private )                  |
|                  0.43     Mb Below ( system )                   |
|                  0.71     Mb Above ( private )                  |
|                  9.21     Mb Above ( system )                   |
|                                                                 |
|                     System information                          |
|          Region size below the line ====> 4.06     Mb           |
|          Region size above the line ====> 32.00    Mb           |
|_________________________________________________________________|

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

BATCH

1,500,000 bytes

TSO

1,500,000 bytes

IMS

2,000,000 bytes

BTS

2,500,000 bytes

Db2

2,000,000 bytes

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 a Code Debug TSO debugging session. The following line commands are available, entered in the SEL column:

A

Concatenation destination (After)

B

Browse individual data set

C

Concatenation source (Copy)

D

Deconcatenate request

E

Edit individual data set

S

Data set status

U

Unallocation request

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

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

List Allocates Screen

---------------------------------- LIST ALLOCATES ---------- ROW 1 TO 13 OF 89
COMMAND ===>                                                   SCROLL ===> CSR

SEL DDNAME   DSNAME (fully qualified)                          ATTR  STA DISP
-------------------------------------------------------------------------------

   -------- ------------------------------------------------------- ---
    STEPLIB  SYS1.DUMMY.LINKLIB                                 IA   SHR KEEP
    SYSPRINT (TERM) NULLFILE                                     A   NEW DELETE
    SYSTERM  (TERM) NULLFILE                                     A   NEW DELETE
    SYSLBC   SYS1.BRODCAST                                        VD SHR KEEP
    SYS0003  CATALOG.TSO.USRCAT                                 I VD SHR KEEP
    ISPPROF  ASJUSR1.ISP.ISPPROF                                I VD SHR KEEP
    SYSPROC  SYS1.CMDPROC                                      C A D SHR KEEP
      +1    ADSA99XP.CLIST                                    C A D SHR KEEP
      +2    SYS2.XPEDITER.V7R7M0.CLIST                        C A D SHR KEEP
    SYSHELP  SYS1.HELP                                         C A D SHR KEEP
    ISPLLIB  SYS2.XPEDITER.V7R7M0.LOADLIB                      CIA D SHR KEEP
      +1    SYS2.PROD.ISPLLIB                                 CIA D SHR

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.

In some cases, a DDIO file was created and formatted during the installation of BMC AMI's Common Shared Services. If not, you can use this utility to create a DDIO file.

Language Processor (LP) Databases and Shared Directories are required for C language processing when using C language LONGNAME compiler support. They are formatted DDIO files that allow member names greater than the previous DDIO limit of eight characters. The LP database is a formatted DDIO file that contains the source listing from the language processor, and the Shared Directory contains all of the keys necessary to handle C language LONGNAME support. To clarify, C language member names can be up to 1024 characters in length and may also be mixed case. For more information regarding shared directories and LP databases, see the Common Shared Services User/Reference space.


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 space for more information.

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 the following figure:

Select Alternate Profiles Screen

-------------------------  SELECT ALTERNATE PROFILES  ----------------------
COMMAND ===>


 Enter the dataset name of the input ISPF user profiles to select.

        DSNAME ===>












           Enter END Command to Cancel Without Updating the Defaults

The option on the Select Alternate Profiles 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.

Merge Profile Screen

 ------------------------------------- MERGE PROFILE ---------------------------
 COMMAND ===>                                                  SCROLL ===> PAGE

 LINE COMMANDS:  S
PRIMARY COMMANDS:  Locate/Find/RFIND (Reposition table)

 CMD  PROFILE   NEW NAME      DESCRIPTION

-------------------------------------------------------------------------------
  _   CPDRIVER  ________ > Command Processor Driver                           <
  _   DEFAULT   ________ > *** NO DESCRIPTION ***                             <
  _   DEF2      ________ > *** NO DESCRIPTION ***                             <
  _   FAXGATE   ________ > *** NO DESCRIPTION ***                             <
  _   CV230     ________ > TESTING C V2R3 PROGRAMS                            <
******************************* Bottom of data ********************************

The list provided on the Merge Profile screen 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.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*