KDPRT01E Wait for OMPE server, <reason>

Explanation

The agent is unable to connect to the OMPE server. One of these reasons is displayed:
  • OMPECT not inited
  • OMPECT access error
  • OMPECT struct error
  • PE STOKEN loc error
  • D2_STC not active
  • D2_STC not found
  • Routtbl not inited

System action

Agent waits for the connection to OMPE server.

User response

Contact IBM support after verifying the following:
  1. If HLQ.RKANPARU(KD5ENV) has environment variable KDP_D2_STC set, make sure the specified OMPE server task is running. If not, start the OMPE server task.
  2. There could be a delay before the agent can communicate with OMPE server task. The delay is configurable using environment variable KDP_STATUS_REFRESH in HLQ.RKANPARU(KD5ENV). While waiting, you may see KD5ASSCT messages.
  3. If OMPE server task is running, check the server log to see if there are any error associated with D5API. The expected messages from OMPE server log are:

    KO2I0100I D5API COLLECTOR INITIALIZATION IN PROGRESS

    KO2I0149I D5API ASM BUILD IS 04/17/15 11.11

    KO2I0130I D5API REGISTRY ENTRY SUCCESSFULLY REBUILT

    KO2I0148I D5API USING REGISTRY XE_D5APIRTB_V530

    KO2I0141I D5API COLLECTOR TRACE SET TO NO

    KO2I0141I D5API COLLECTOR STIMER SET TO 00003000

    KO2I0101I D5API COLLECTOR INITIALIZATION COMPLETE

    KO2I0154I D5API COLLECTOR CONNECTED TO DB2 ssid ON BEHALF OF AGENT agenttask

    If you do not see above messages, check HLQ.RKD2PAR(ompetask), make sure that you have common collector started. 
    *                              
*  Starts the Common Collector.
*                              
EXEC OMPECCPC