OSI/MHS Configuration and Management Manual

Starting, Stopping, and Updating Your OSI/MHS
Subsystem
OSI/MHS Configuration and Management Manual—424827-003
6-10
Defining and Starting the Entry and Wait Managers
You can use management programming commands to write the entry and wait
manager processes, and then use TACL commands to define and start the processes.
As an alternative, you can write and compile the processes by using TAL, C, or another
supported language. You can then define the processes as Pathway servers and run
them under Pathcom.
The following example uses TACL commands to define and start the entry and wait
managers.
CLEAR ALL
ASSIGN DEBUGLOG, $S.#EMSERV.DEBUGLOG
ASSIGN QUEUEFILE, $VOLX.QMGR.DSQFIL
ASSIGN WAITMANAGER, $ZTWM
PARAM HANGAROUND "TRUE"
PARAM IOTIMEOUT 300
PARAM MAXLINKS 20
PARAM DEBUGLOGFORMAT "TRUE"
PARAM DEBUGLOGLEVEL "3"
RUN $VOLX.QMGR.EMSERV /OUT $S.#EMSERV, NAME $ZTEM, NOWAIT, &
PRI 130, CPU 6/
RUN $VOLX.QMGR.WMSERV /OUT $S.#WMSERV, NAME $ZTWM, NOWAIT, &
PRI 130, CPU 6/
The following examples define the entry and wait managers as Pathway server
classes. An advantage of this approach is that if the servers stop because of a system
error, PATHMON will automatically restart them. Note the following requirements:
•
Pathway server classes must be on the same system as the GPI with which they
are associated.
•
Pathway must be running before you can add a server class.
To define an entry manager:
reset server
set server (assign QUEUEFILE, $VOLX.QMGR.DSQFIL)
set server (assign WAITMANAGER $ZTWM)
set server (param HANGAROUND TRUE)
set server (param IOTIMEOUT 300)
set server (param MAXLINKS 20)
set server maxservers 1
set server numstatic 1
set server linkdepth 1
set server maxlinks 0
set server in $S.#EMSERV.INF
Note. The entry manager and wait manager for each gateway association are defined through
SCF as attributes of the corresponding GATEWAY object. For a general user X.400 gateway,
the wait manager process name ($ZTWM in the examples below) must match the value of the
GW-AUX-PNAME attribute for the associated OSI/MHS GATEWAY object. For a TRANSFER
X400 gateway, the GW-AUX-PNAME attribute is informative only.
For either type of gateway connection, the entry manager process name ($ZTEM in the
examples below) must match the value of GW-PNAME for the associated GATEWAY object.