OSI/MHS Configuration and Management Manual

Troubleshooting Your OSI/MHS Subsystem
OSI/MHS Configuration and Management Manual—424827-003
9-55
Problem: Insufficient Memory for Gateway
GPI_Initialize_, based on anticipated message size and other factors, and how much
space must be available on the swap volume.
The GPI library needs up to 80.5 MB for two object trees of the maximum size.
The swap space for a GI process is required not only to manage object trees, but also
to support mapping between the object and value trees that represent X.400
messages. When the application opens the GIP process, the process allocates the
amount of memory dictated by the GPI_Initialize_ parameters. (Remember that the
GIP does not necessarily use the same volume as the GPI library.) Later, while
transferring messages in and out, the GIP allocates additional memory for its value
tree. If the memory available on the swap volume is insufficient, either initially or
during transfer of a message, the GIP reports the following event and stops running:
ZMHS-EVT-NO-MEM - event message 21
The MHS manager produces other event messages as it attempts to restart the GIP,
as the example later in this section demonstrates.
If the application makes a library call requiring interaction with the GIP and the GIP is
no longer present, the library returns one of the following primary codes to the
application:
primary code = ZGPI_RC_OPEN_ERROR (on an open call) or
= ZGPI_RC_WRITEREADX_ERROR or
= ZGPI_RC_SESSION_ABORTED (during a session)
The disk space required for a value tree is approximately 10 times the size of the
encoded message; it can reach up to 20 times the size of a message if the message
contains a large number of multivalued attributes, such as recipient names. If an
application is likely to send or receive very large messages (for example, 10 MB
messages), each GIP will require up to 60 MB of memory for its value tree and object
tree combined.
In the following example, the volume $postc is specified as the swap volume for GI
group GIGRP1, and the output of the DSAP utility shows how much free space there is
on that volume.
-> info group $zg1.#gi.gigrp1,detail
MHS Detailed info GROUP GI.\las.GIGRP1
GENERAL:
*CPU.............. 13
*Backup-CPU....... 4
*Priority......... 145
*PDU-Store........ \las.$POSTC.GDB1.PDUGI1
*PDU-Log-file..... \las.$POSTC.GDB1.LOGGI1
*Work-SV.......... \las.$POSTC.ZG1
GI-SPECIFIC:
*GI-Process-name.. \las.$ZG1.#PG11
*GI-CPU........... -1