Production Strategies › Symbolic Support

Symbolic Support

To take full advantage of CA SymDump for CICS, you need an up‑to‑date symbolic listing of the application programs that execute in your test or production CICS regions. When you are ready to move a program from test to production, ensure you save its symbolic listing so it is available if the program needs further debugging.

To get an up‑to‑date symbolic listing of the application programs that execute in your test or production CICS regions:

1. Move the listing to a separate production symbolic file.
2. Use the IN25UTIL batch program to unload the listing from the test symbolic file to an intermediate data se
3. Reload it to the production symbolic file. For more information, see the CA Application Quality and Testing Tools Symbolic Guide.

The examples in the following sections detail transaction dump analysis with symbolic support and assume that there are:

• Multiple symbolic files (for information on defining and maintaining multiple files, see the Installation Guide)
• Up‑to‑date symbolic listings of production programs

You may have several different versions of a program and, consequently, several different symbolic listings on various symbolic files.

• For COBOL and COBOL II programs, CA SymDump for CICS automatically finds the right symbolic listing for the program version you are debugging, if it exists
• For PL/I and Assembler programs, and for COBOL and COBOL II programs that do not have matching listings, CA SymDump for CICS displays all of the symbolic files containing listings for the program so you can select the one you want

If you do not have an up‑to‑date symbolic listing for the program, you can get symbolics by recompiling or reassembling the program with the appropriate post‑processor program after the dump is generated, but before you examine it online. For more information, see the CA Application Quality and Testing Tools Symbolic Guide.