Troubleshooting data for dynamic LIBRARY management problems

CICS® MustGather for dynamic LIBRARY management problems

Unexpected errors of dynamic LIBRARY management might occur under the following circumstances:

  1. Installing a dynamic LIBRARY
  2. Using SET LIBRARY to change a dynamic LIBRARY
  3. Loading programs
  4. Using SET PROGRAM NEWCOPY

Also, if an error results in a system dump that is taken by the CICS Loader, the error might be a dynamic LIBRARY management problem.

Gather the following diagnostic information before contacting the CICS support team to troubleshoot your dynamic LIBRARY management problems.

Required data:
  1. The CICS message log that contains the messages that lead up to the failure, including all the DFHLDnnnn messages that report the problem. For more information, see CICS messages.
  2. LIBRARY audit trail messages that are sent to the CSLB transient data queue, which by default is an indirect queue to CSSL. The most recent instances of audit trail messages are very useful:
    1. DFHLD0555 and DFHLD0556 that give the dynamic LIBRARY configuration at the time of the error
    2. DFHLD0505, DFHLD0506, and DFHLD0507 that give details for each LIBRARY when it is installed
    The audit trail also contains messages that indicate the success or failure of LIBRARY management operations.
  3. The MVS™ system dump that is taken at the point of failure. If a dump is not created by CICS when the problem occurs and you can re-create the problem, take a system dump manually, or add the pertinent DFHLDnnnn message to the dump table. If system dumping is permitted for the dump code and system dumping is not disabled, a system dump is taken when the error is detected. If you do not get a dump when the abend occurs, see number 3 under the MVS system dump section in Using dumps for CICS problem determination on z/OS®.
  4. The CICS internal trace that is included in the MVS system dump when tracing is active. Ensure that the internal trace table size is big enough to contain sufficient data for diagnosis; for example, you can use a table size of 20480K. When possible, turn on level 1 tracing for all CICS components and level 1-2 tracing for the LD component. If this is not possible, turn on a minimum of level 1-2 for the LD component, and turn on level 1 for LM and SM when possible. For more information, see Using trace for CICS problem determination on z/OS.
Optional data:
  1. Output from the CEMT INQUIRE LIBRARY command. The output shows the LIBRARY resources that are installed in the system and the details for each LIBRARY. This command is particularly helpful if audit trail information is not available.
  2. Output from the CEMT INQUIRE PROGRAM command for programs that are affected by the problem. The output shows the information in the LIBRARY and LIBRARYDSN parameters.
  3. The CICS auxiliary trace might be useful if you can re-create the problem. As with the CICS internal trace, when possible, turn on level 1 tracing for all CICS components and level 1-2 tracing for the LD component. If this is not possible, turn on a minimum of level 1-2 for the LD component and if possible, level 1 for LM and SM. For more information, see Using trace for CICS problem determination on z/OS.