OSI/MHS Configuration and Management Manual

Troubleshooting Your OSI/MHS Subsystem
OSI/MHS Configuration and Management Manual—424827-003
9-53
Problem: Missing Entry or Wait Manager Process
problem, you can usually look for the process name in your configuration and startup
files and identify either a missing START command or a name mismatch between the
ADD and START commands.
If the required process was not defined in the configuration, the status codes are
different, and there might or might not be an event message. For example, the GPI
requires a wait manager; if you did not specify one, the primary and secondary codes
are
primary code = ZGPI_RC_INVALID_GATEWAY_INFO
secondary code = ZGPI_IGIC_BAD_AUX_PNAME
and there is no event message. (For information about how errors are reported to a
GPI application, see the OSI/MSH Gateway Programmatic Interface (GPI)
Programming Guide.
Event message 12 (ZMHS-EVT-IO-ERR) cannot signify the failure of an MHS process,
because the MHS manager attempts to restart a process or group, or to find another
group that can handle the request. In this case, the event log contains messages
reporting process failures (event message 18, ZMHS-EVT-PROC-FAIL). If a group
cannot be restarted, OSI/MHS reports event 17 (ZMHS-EVT-GROUP-TOO-MANY-
FAILS).
Event message 12 can, however, signify the failure of a process such as an entry
manager, which is external to OSI/MHS and therefore not restarted by the MHS
manager. If the process named in the event message does not match any name in the
file that contains your SCF START commands, check the TACL or Pathcom files you
use to start the entry and wait managers.
In the following example, TACL is used to start the entry and wait manager processes.
A subsequent CPU failure causes the entry manager to fail before the GPI application
is started. Here is an excerpt from the TACL macro file that starts the entry and wait
managers (and possibly other external processes such as password servers):
ASSIGN DEBUGLOG, \las.$ml.gdb0.ZG10EML
ASSIGN QUEUEFILE, \las.$ml.gdb0.ZG10EMQ
ASSIGN WAITMANAGER, $WG10
PARAM HANGAROUND "TRUE"
PARAM IOTIMEOUT 300
PARAM MAXLINKS 20
PARAM DEBUGLOGFORMAT "TRUE"
PARAM DEBUGLOGLEVEL 3
\las.$ml.testools.emserv /name $eg101, nowait/
\las.$ml.testools.wmserv /name $wg10, nowait/
...