OSI/MHS Management Programming Manual

Commands and Responses
OSI/MHS Management Programming Manual—424824-001
5-69
ADD GATEWAY
If the ZGW-MAX-TIME-EXPIRED value is set to 0, then the attribute is turned
off, and event 52 is not generated.
Gateways that are migrated from D20, D21, or D22 have the
ZGW-MAX-TIME-EXPIRED value set to 0.
ZMHS-MAP-GW-PNAME
is the process name of the gateway process. This token is required. It must appear
at least once and can be repeated up to five times. The process name must be unique
both within and between GATEWAY objects.
ZMHS-MAP-GW-AUX-PNAME
is the process name of the auxiliary process associated with the gateway process.
This attribute is required for a GPI gateway and is optional for a TRANSFER
gateway. The specified process name must be unique both within and between
GATEWAY objects.
ZMHS-TKN-GW-TYPE
specifies the type of gateway being defined. Only one P1-EXIT gateway object can
be configured per OSI/MHS subsystem. This field can have the following values:
ZMHS-VAL-GW-TYPE-NORMAL
ZMHS-VAL-GW-TYPE-P1-EXIT
NORMAL defines a gateway to which messages are routed normally. NORMAL
can be used for both GPI and TRANSFER gateways. NORMAL is the default
value.
P1-EXIT defines a special exit gateway. P1-EXIT is used only for GPI gateways.
If P1-EXIT is specified, subsequent MPDUs received from the RTS are sent directly
to the P1-EXIT gateway before OSI/MHS decodes or routes them. Typically, a P1-
EXIT exit gateway is configured in cases where messages received from remote
systems are to be examined or modified by an external GPI-based application prior
to normal processing by OSI/MHS.
If you do not specify P1-EXIT, OSI/MHS processes messages normally.
ZSPI-TKN-ALLOW-TYPE
ZSPI-TKN-RESPONSE-TYPE
ZSPI-TKN-COMMENT
are described in the SPI Programming Manual.
Note. After every twentieth message queued to the gateway input queue, the
OSI/MHS MTA retrieves the time of enqueue for the first message on the queue. If the
first enqueued message has remained on the queue longer than the maximum time
configured in the gateway object, event 52 is generated. This event is also generated
every time an additional 20 messages are enqueued, as long as the message has not
been retrieved from the queue. After the message is retrieved, no additional event is
generated.