DSM/Tape Catalog User's Guide

Storage Server Interface (SSI) to the Tape Library
Control Path
DSM/Tape Catalog User’s Guide — 520233-008
8 - 3
Startup Sequence
To give the server the required information to pass along to the $ZSSI, alter the OBEY
file used to start $ZSVR to:
#FRAME
#PUSH #PARAM
DELETE DEFINE =TCPIP^HOST^FILE
ADD DEFINE =TCPIP^HOST^FILE, CLASS MAP, FILE $system.ztcpip.hosts
#SET #PARAM CSI^HOSTNAME hostname
ZSERVER/NAME $ZSVR,NOWAIT,PRI 199,CPU 2/6
#UNFRAME
Startup Sequence
Along with TCP/IP, $ZSSI also uses RPC services to communicate with the CSI. RPC
must be started to enable $ZSSI to communicate with the CSI. For more information
on RPC, see Remote Procedure Call (RPC) Facility on page 8-6.
This is a typical startup sequence as it relates to $ZSSI:
1. Start TCP/IP.
2. Start the portmapper. See
Running the Portmapper on page 8-4.
RPC and the portmapper depend on TCP/IP
.
3. Start $ZSVR.
$ZSVR creates the $ZSSI process when it is requested to communicate with the
t
ape library
$ZSSI cannot start processing requests until:
1. Connection through TCP/IP is made with the ACSLS library server
.
2. Release 3.00 - Version 2 or later of the CSI process (program 300031) on the
ACSLS library server is ready and waiting.
To determine whether the CSI process on the ACSLS library server
T
APES.COMPANY.COM is up and running:
TACL 6>RPCINFO -t TAPES.COMPANY.COM 300031 2
CSI^CONNECT^AGETIME Optional; # seconds connection aging (default 172800,
minimum 600, maximum 31536000)
CSI^RETRY^TIMEOUT Optional; per try network interface timeout (default 3)
CSI^RETRY^TRIES Optional; number of retries (default 5)
DEFINE name Class Description
=TCPIP^HOST^FILE MAP Optional; if present, the NonStop Kernel TCP/IP
sof
tware uses the HOSTS file specified by this
DEFINE to resolve the CSI hostname instead of
using the Domain Name resolver
PARAM name Description