The Source Listing Facility › Display and Search Through Nested Programs

Display and Search Through Nested Programs

CA SymDump for CICS provides support for COBOL II nested programs when the COBOL nested programs are recompiled with the COBOL II post‑compiler provided with CA SymDump for CICS.

COBOL II nested programs allow non‑unique paragraph and data names to be defined across nested programs. Therefore, CA SymDump for CICS can support qualified names for COBOL programs. A qualified name consists of a one‑ to 30‑byte COBOL program name, a colon, and a one‑ to 30‑byte paragraph or data name. For example, program1:datanam1 is a qualified name. Qualified names ensuring that the correct version of datanam1 (which can be defined in multiple programs) displays.

When CA SymDump for CICS displays the source code for a nested program, the Nested= field displays below the Program= field. The Nested= field is 30 bytes long and indicates the name of the nested program for the currently displayed source code. If you are using the Source Listing facility to display a COBOL nested program and you press PF8 to scroll through the entire source code of the program, the Nested= field changes each time the source code for a different nested program displays.

The names of all nested programs within a specific COBOL program are listed at the end of the Procedure Name Cross Reference section (Option # 7).

              CA InterTest ‑ PROTDEM FILE SOURCE LISTING DISPLAY              
COMMAND ===>                                                                   
Program= ACME2000 Option #       Stmt #                             Margin= 01 
 Nested=                                Search=                                
OPTS 1 Proc div  2 Work-stor 3 Link sect 4 D-map      5 Clst/Pmap More:   +    
     6 Data xref 7 Proc xref 8 Err msgs  9 Srch fwd  10 Srch bwd                
PFKS 1 Help      2           3 End        4 Profile    5 Monitor    6 Menu      
     7 Backward  8 Forward   9           10           11           12 Status    
‑‑‑‑‑‑‑‑‑+‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑
 _ DEFINED      PROCEDURE NAMES         REFERENCES                             
 _   122 3000‑REGISTER‑HANDLER          P107                                   
 _   131 4000‑FORCE‑ABEND               P108                                   
 _   139 5000‑HANDLE‑ROUTINE            D129                                   
 _   152 9000‑RETURN                    P109                                   
 _   168 9999‑GOBACK                                                           
 _   227 9999‑GOBACK                    P221                                   
 DEFINED   CROSS‑REFERENCE OF PROGRAMS     REFERENCES                          
EXTERNAL   ACME200A . . . . . . . . . . . 120                                 
     171   ACME200N . . . . . . . . . . . 229 114                             
       2   ACME2000 . . . . . . . . . . . 230                                 
EXTERNAL   ACME2001 . . . . . . . . . . . 117                                 
EXTERNAL   DFHEI1 . . . . . . . . . . . . 127 137 147 160 166                 
NESTED PROGRAM MAP                                                             
PROGRAM ATTRIBUTE CODES (RIGHTMOST COLUMN) HAVE THE FOLLOWING MEANINGS:     

The Nested= field also indicates the nested program that Option # 1, 2, and 3 apply to, and the nested program that CA SymDump for CICS searches first for any data name or paragraph name that you specify in the Search= field. If a paragraph name or data name is not found in the specified nested program, CA SymDump for CICS then searches the main program.

For example, if Option # 2 and Nested=program2 are specified, the Working Storage section for nested program program2 is displayed. Also, if Nested=program3 and Search=datanam1 are specified, nested program program3 is searched first for datanam1; if datanam1 is not found, the main program is searched for datanam1.