Troubleshooting the CIM server

Use this information if the CIM server does not start or if the CIM server starts, but does not run as expected.

The CIM server does not start

If the CIM server does not start, follow these steps:

  1. Ensure that the correct options and product are installed on your system.
  2. Ensure that the CIM server is configured correctly.

The CIM server does not run as expected

If you have trouble with the CIM server, follow these steps:

  1. Check whether the certificate is expired.

    To check whether the CIM server is running, type WRKACTJOB JOB(QUMECIMOM) at a command line. If there is no active job, type the STRTCPSVR *CIMOM command to start a server.

  2. Check whether the CIMOM repository is corrupted.

    Verify whether the repository directory and configuration files exist in the /QOpenSys/QIBM/UserData/UME/Pegasus/ directory of the integrated file system. If any of these files are missing, restore all the repository directories and files from your backup.

  3. Verify whether you are attempting to process a request when the provider is not registered or enabled:
    1. Type cimprovider -l -s to list the name and status of the registered provider modules.
    2. Type cimprovider -l-m module-name to see the individual providers in that module.
  4. Check the job log file.
    1. Type WRKACTJOB at a command line.
    2. Check the QSYSWRK subsystem to find the QUMECIMOM job.
    3. Select 5 (Work with), and then type 10 (Display job log, if active, on job queue, or pending).
    4. If the QUMECIMOM job is not running, type WRKJOB QUMECIMOM.
    5. Select the most recent job by typing 1 (Select) next to it.
    6. If the status is OUTQ, type 4 (Work with spooled files), and then type 5 (Display) next to the QPJOBLOG file.