Preliminary checks

Before looking further for the cause of the problem, review the following preliminary checks. These checks might highlight a simple cause or, at least, narrow the range of possible causes.

About this task

As you go through the questions, make a note of anything that might be relevant to the problem. Even if the observations you record do not at first suggest a cause, they could be useful later if you need to carry out systematic problem determination.
  1. Has CICS® IA executed successfully before?

    If CICS IA has not run successfully before perhaps an error has occurred during installation.

    Have you applied all the prerequisite APARs?

    Have you reviewed all the information in the CICS IA Program Directory and the latest information in the Preventive Service Planning (PSP) upgrade for CICS IA Version 3.2?

  2. Are there any messages explaining the failure?

    If a problem is encountered, the CICS IA run time issues messages to the CINT transient data destination.

    Check the CICS MSGUSR and JESMSGLG logs for any security-related messages: for example, message DFHXS1111 or ICH408I. Insufficient authority to start required CICS IA transactions can result in various failure symptoms.

  3. Can you reproduce the error?

    If the failure can be reproduced, note the exact sequence of events required to re-create the problem. IBM® support personnel might request the activation of various traces to determine the cause of the error situation.

  4. What to do next

    If the preliminary checks have enabled you to find the cause of the problem, you can now resolve it. Use other information in the CICS library and in the libraries of other licensed programs. If you have not yet found the cause, look at the problem in greater detail. Begin by trying to classify the type of problem.


Task Task

Feedback


Timestamp icon Last updated: Friday, 22 November 2013


http://pic.dhe.ibm.com/infocenter/cicsts/v5r1/topic///ciuug9j.html