Previous Topic: CAIENF/DB2 Troubleshooting Checklist

Next Topic: CAICCI Troubleshooting Checklist

CAIENF/USS Troubleshooting Checklist

The following items may help you identify the problem.

  1. Are z/OS UNIX Services initialized properly and running in full function mode?

    CAIENF/USS does not install any of its intercepts until the UNIX kernel successfully initializes, so a z/OS USS configuration problem will prevent CAIENF/USS from starting.

    Without CAIENF/USS running, verify that you can initiate an interactive UNIX shell session using OMVS or a Telnet session.

  2. Are there any unusual startup messages from CAIENF?

    CAIENF/USS initializes during CAIENF startup, and many times, unusual conditions are detected and reported at this point.

  3. Is the DCM module for CAIENF/USS installed, along with the DCMs for any products that require CAIENF/USS?
  4. Are your security settings correct?

    The user that the CAIENF address space runs with must be defined with z/OS UNIX Services superuser privileges (UID 0).

  5. In the event of an extreme error, CAIENF/USS will generate a system SVC dump. These dumps should be retained for CA service personnel.

    If you suspect a problem with CAIENF/USS and are trying to gather your own dumps, you need to ensure that you include the OMVS address space along with any applications you suspect are having problems.

    Also, CAIENF/USS uses a dataspace named "#UVT#", and this dataspace should also be included in any system dumps you generate. Due to the amount of data involved, you may need to create larger dump data sets.