OSI/MHS Configuration and Management Manual

Starting, Stopping, and Updating Your OSI/MHS
Subsystem
OSI/MHS Configuration and Management Manual424827-003
6-11
Defining and Starting the Entry and Wait Managers
set server out $S.#EMSERV.OUTF
set server autorestart 3
set server program $volX.QMGR.EMSERV
set server process $ZTEM
To define the wait manager:
reset server
set server (assign QUEUEFILE, $volx.qmgr.dsqfil)
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.#WMSERV.INF
set server out $S.#WMSERV.OUTF
set server autorestart 3
set server program $voXl.QMGR.WMSERV
set server process $ZTWM
To define queue and log files:
RESET
SET TYPE K
SET CODE 266
SET REC 2128
SET BLOCK 4096
SET IBLOCK 4090
SET KEYLEN 56
SET KEYOFF 0
SET AUDIT
SET EXT (100,2)
CREATE $VOLX.QMGR.DSQFIL
RESET
SET TYPE E
SET REC 4072
SET BLOCK 4096
SET NO BUFFERED
SET EXT (100,2)
CREATE $VOLX.QMGR.DSLFIL
Assign security attributes that give the GIP process read/write access to the queue and
log file. The user ID of the GIP process is that of the user who started the OSI/MHS
subsystem.
Use the PATHCOM command to start the entry and wait managers from inside
Pathway. For example:
PATHCOM $XXPM; RUN $ZTEM, $ZTWM
For additional examples of entry and wait managers as Pathway server classes, see
the Queue Manager Manual.