z/OS messages

This topic contains error messages that are specific to the z/OS platform.

The following messages appear:

• CRIHS0001I IHS {0} is active. {1} {2}:{3} {4}:{5}. Use jobname {6} for console commands.
  • Explanation: Message provides information such as server name, server PPID, and job name after the server starts up. Issued by module mod_zos_cmds.
  • User action: None
• CRIHS0002I IHS {0} is stopping.
  • Explanation: The server is preparing to shutdown. Issued by module mod_zos_cmds.
  • User action: None
• CRIHS0003E apr_pollset_create failure could be caused by a failure to allocate an IPC message queue. Check the system availability of message queues, IPCMSGNIDS.
  • Explanation: Event poll set could not be created.
  • User action: Check the system availability of message queues: IPCMSGNIDS.
• CRIHS0004W {1} mpmstats: approaching MaxClients ({2}/{3})
  • Explanation: The server with job name {1} is approaching 100% thread usage. The threshold is defined by the MPMStatsBusyThreshold directive and defaults to 90%
  • User action: Check application response time and inbound workload, raising MaxClients if needed.
• CRIHS0005W {1} mpmstats: reached MaxClients ({2}/{3})
  • Explanation: The server with job name {1} is at 100% thread usage.
  • User action: Check application response time and inbound workload, raising MaxClients if needed.
• CRIHS0006I {1} mpmstats: Threads now below threshold of {2} ({3}/{4})
  • Explanation: The server with job name {1} has crossed back below the threshold {2} of busy threads. The threshold is defined by the MPMStatsBusyThreshold directive and defaults to 90%.
  • User action: No action is required. The transition is logged for retrospective purposes.