General questions concerning CA SymDump for CICS usage and requirements.

Document ID : KB000027721
Last Modified Date : 14/02/2018
Show Technical Document Details
  1. CICS already has it's own dump capture program and I can print the dumps out with DFHDUP.  Why should I use CA SymDump for CICS?

    CA SymDump for CICS offers many of the same capabilities of CA InterTest for CICS to help resolve abends.  Unlike CA InterTest for CICS, which prevents problems BEFORE they occur, CA SymDump for CICS uses the same facilities offered by CA InterTest for CICS to quickly find and resolve problems after they have occurred.  You can use the same symbolic displays to show the line of code that abended, the same CORE displays to show the values of relevant variables, storage addresses, CICS control blocks, etc. to see what led to the problem.

  2. What releases of CICS does CA SymDump for CICS support?

    CA SymDump for CICS supports all releases of CICS from CICS/TS 3.1 to CICS/TS 5.3.

  3. I am running more than one CICS release at my location.  Can I share the same CA SymDump for CICS loadlib across all regions?

    No, CA SymDump for CICS is CICS release dependent.  The installed CA SymDump for CICS loadlib must correspond to the CICS release of the region.

  4. Is the CA SymDump for CICS Dump File (PROTDMP) upward and downward compatible between releases of CICS?

    No.  Since CA SymDump for CICS also uses the corresponding CICS DFHDUP program for some of it's processing, the same dump file cannot be shared between different CICS releases.

  5. Do I need a separate Dump File (PROTDMP) for each CICS region where CA SymDump for CICS is executed?

    Yes.  Each CICS region must have it's own unique dump file.

  6. How much space should I allocate for my PROTDMP file?

    There really is no answer to that as it depends upon the activity from site to site.  It may take some experimentation on your part to determine how much space is necessary.  If you find that the file runs out of space too quickly, then you should redefine the file with more space.  The PROTDMP file can be defined with different CI sizes, 4k, 8k, 16k, or 32k.  The larger the CI size, the larger the number of dumps that can be held.

  7. What will happen if my PROTDMP file fills up?

    CA SymDump for CICS is installed with a specific number of days that a dump will be held; the default is 1 day.  Assuming that a given dump has been on the dump file for the specified time or longer, a new dump coming in will overwrite the first eligible dump with enough contiguous space to hold the new one.  If no dumps can be deleted, then the dump will be written to the CICS dump dataset.  Deletion can be age driven or demand driven.  This can occur at startup or dynamically as needed.  The rules for deletion can be modified during PROTDMP definition and initialization via IN25INIT or online using the SYMI transaction.

  8. Can I delete dumps automatically and start with an empty PROTDMP file?

    Yes, at CICS region startup, there are two programs you can add to your PLTPI, IN25INST will start the dump capture automatically and IN25INST1 will delete any dumps found in the PROTDMP file when CA SymDump for CICS is started.

  9. If I have CA SymDump for CICS installed in multiple regions, can I view all dumps from one region?

    Yes.  CA SymDump for CICS will only write to the dump file with an FCT name of PROTDMP.  By defining the dump files from the other CICS regions read/browse only, you can enter the local FCT name on the the Dump/Trace Analysis display and view the dumps contained in that file.

  10. What is the CA SymDump for CICS trace formatting region?

    The trace formatting region was introduced with CA SymDump for CICS 6.1 to provide a more sophisticated approach to trace formatting than what was previously available with earlier releases of CA SymDump for CICS.  It runs as a separate address space and allows you to display all trace entries in full DFHTUxx0 format.  You can filter the display, to show only EIP entries, for example, and you have the ability to view the trace in abbreviated, short, or full format.

  11. What are the requirements for the trace formatting region?

    The trace format region requires that the TNG/CCI (CAICCI) component be up and active before the trace formatting region is started.  CA SymDump for CICS uses CAICCI to communicate with the trace formatting region.

  12. Can CA SymDump for CICS suppress CICS dumps for me?

    Yes, Symdump can suppress AP0001, SR0001, and CICS transaction dumps that would be written to the DFHDMPA or DFHDMPB datasets.  This will improve on performance and cut down on DASD utilization.