OSI/MHS Configuration and Management Manual

Troubleshooting Your OSI/MHS Subsystem
OSI/MHS Configuration and Management Manual—424827-003
9-54
Problem: Insufficient Memory for Gateway
The GPI application receives the error OM_RC_PERMANENT_ERROR in response to
an open call. The primary code returned by the status call is
ZGPI_RC_OPEN_ERROR, and the secondary code is 14 (device does not exist). The
operations staff discovers the following event messages in the event log:
94-12-10 10:43:29 \LAS.0,0 TANDEM.CPU.D20 000101
Processor Down, CPU 2
...
94-12-10 10:45:04 \LAS.$PG11 TANDEM.MHS.D20 000012
$ZG1 GI.\LAS.GIGRP1 $PG11: File system
error 14 from procedure 11, file
\LAS.$EG101
Event message 101 indicates a CPU failure. Event message 12 identifies the file
$EG101. The same name appears in the OSI/MHS configuration file, in the definition
of the GATEWAY object:
ADD GATEWAY $ZG1.#GATEWAY,&
GW-TYPE NORMAL, &
VINTAGE 88, &
VALIDATION OFF, &
PASSWORD GATEWAY, &
GW-PNAME $EG101, &
GW-AUX-PNAME $WG10
The short-term solution to this problem is to restart the entry manager and possibly the
GPI application. To avoid the problem in the future, you could use Pathway rather than
TACL to control the entry and wait manager processes. (The Pathmon process, like
the MHS manager, restarts processes after they fail.) Alternatively, you can define
multiple entry managers (running in different CPUs) for the gateway; the GIP looks for
each entry manager process in turn, returning an error only if none is found—a
condition unlikely to be caused by a single CPU failure.
For more information about the entry and wait managers, see the OSI/MHS Gateway
Programmatic Interface (GPI) Reference Manual.
Problem: Insufficient Memory for Gateway
When you use the GPI, sufficient swap space must be available for the GPI library and
the GI processes. You specify the swap volume for the library in the GPI_INITIALIZE_
call, and the swap volume for each GIP process in the ADD GROUP commands that
define the GI groups.
The swap space for the GPI library is required primarily to enable the GPI to manage
the object trees that represent root objects (messages, probes, reports, and
P1-encoded objects.). Upon initialization, the library allocates memory based on the
parameters you specify in the call. Then it allocates additional memory as new object
trees are created. If the swap volume does not have enough space to provide the
memory for a session, the library returns a ZGPI_RC_ALLOCATESEGMENT_ERROR
to the application. The OSI/MHS Gateway Programmatic Interface (GPI) Programming
Guide includes a discussion of how to specify appropriate parameters to