Troubleshooting data for policy problems
CICS® MustGather for policy problems
Policy problems occur for different reasons. To identify the source of errors that affect policies:
- For CICS TS 5.1, see Troubleshooting for policies.
- For CICS TS 5.2 or later, see Troubleshooting platforms, applications, and policies.
After that, follow these guidelines to gather complementary diagnostic information before contacting the CICS support team.
- Required data:
-
- Relevant messages from the CICS console log. These messages typically include any DFHMPnnnn message. For more information, see CICS messages.
- The CICS internal trace that is included in the MVS™ system dump when tracing is active. For more information, see Using trace for CICS problem determination on z/OS®.
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 2
tracing for the MP component and level 1 tracing for all other CICS components. If this is not possible, turn on level 1 tracing by following these rules:
- For problems during the installation of a policy, turn on a minimum of level 1 tracing for MP, PI, SM, PG, and RL components.
- For runtime problems, turn on a minimum of level 1 tracing for MP, EI, ME, and SM components. If the problem involves Time policies, also turn on level 1 tracing for the DS component. For policies with an action of event, also turn on level 1 tracing for EC, EP, and PG components.
- The MVS system dump that is taken when the problem occurs. The way that you get the dump depends on whether or not you get a message, transaction abend, or no output when the problem occurs. For more information, see Using dumps for CICS problem determination on z/OS.
- If you are unable to get a system dump, take a CICS
auxiliary trace that leads up to the error. For more information, see Using trace for CICS problem determination on z/OS. If possible, turn on level 2 tracing
for the MP components, and level 1 tracing for all other CICS
components. If this is not possible, turn on level 1 tracing by using the following rules:
- For problems during the install of a policy, turn on a minimum of level 1 tracing for MP, PI, SM, PG, and RL components.
- For runtime problems, turn on a minimum of level 1 tracing for MP, EI, ME, and SM components. If the problem involves Time policies, also turn on level 1 tracing for the DS component. For policies with an action of event, also turn on EC, EP, and PG components.