TRANSFER Installation and Management Guide

Customizing X400 Gateway Servers
Customizing a TRANSFER System
068837, Update 1 to 013198 Tandem Computers Incorporated 7–19
Customizing the
TRANSFER X400
Gateway Servers
You also customize your TRANSFER X400 gateway servers to meet the special needs
of your TRANSFER X400 network. In addition to the general considerations for
customizing your TRANSFER system given earlier in this section, you need to define
the parameters discussed in the following sections.
X400 Export Server
(X400-EXPORTER)
TRANSFER X400 export servers are defined in PATHWAY only if the TRANSFER
X400 gateway is configured. This server is responsible for translating TRANSFER
messages into the X.400-format equivalent so that a TRANSFER correspondent can
send a message to an X400 correspondent.
The export server does not have a requester. Export server processes look for work in
the X400 queue file. For this reason, the PARAM HANGAROUND "TRUE" must be
specified, and the NUMSTATIC value must be set to the same value as MAXSERVERS
to start all the processes and keep them running.
Most of the export server PARAMs are required to define other processes that it has to
communicate with. It needs to know about the TDB-SERV, the X400-gateway queue
entry manager, and the X400-gateway queue wait manager.
The export server has a single log file, defined with the out parameter. Serious
problems are always logged, but information messages are logged only if the PARAM
DEBUGLOGLEVEL parameter is reset to 0 from the default value of 3. The PARAM
DEBUGLOGRECSPEROPEN defines how many lines are written before the log file is
reopened; its default is 20.
For example:
ALTER X400-EXPORTER, out $S.#EXPLOG
ALTER X400-EXPORTER, PARAM DEBUGLOGLEVEL "0"
ALTER X400-EXPORTER, PARAM DEBUGLOGRECSPEROPEN "100"
Note Export servers do not support an ASSIGN DEBUGLOG server command. You must use an OUT location
to get debuglog information.