IBM RELEASE 7.3 Management Manual page 122

HPSS will use any Cartridge Access Port (CAP) in the STK Robot that has a priority greater than zero.
When it needs a CAP, HPSS will pick the highest priority CAP that is currently available. At least one
CAP must be assigned a non-zero priority. See the STK Automated Cartridge System Library Software
(ACSLS) System Administrator's Guide for procedures to set CAP priority.
ACSLS Packet Version
See the STK Automated Cartridge System Library Software (ACSLS) System Administrator's Guide for
details. The environment variable ACSAPI_PACKET_VERSION will override the value entered in the
ACSLS Packet Version field of the STK PVR Specific Configuration Window. If neither are set, a
default value of 4 is used since ACSLS 6.x generally uses packet version 4.
Starting the STK Client Processes
In order for the HPSS PVR to communicate with the STK robot, it is required that STK client side
processes be running on the node where the HPSS PVR is executing. These client side processes are the
Server System Interface (SSI) and the Toolkit event logger. These binaries and associated script files are
distributed with the HPSS, but are maintained by Sun Microsystems Inc.
The AIX binaries and script files for starting the STK client side processes on an AIX platform are
located in the $HPSS_PATH/stk/bin directory. Documentation files describing the files in the bin
directory are located in the $HPSS_PATH/stk/doc directory. Refer to these doc files for additional
information. Similarly, Linux binaries and script files for starting the STK client side processes on a
Linux platform are located in the $HPSS_PATH/stk_linux/bin directory; and associated documentation
is located in the $HPSS_PATH/stk_linux/doc directory.
The t_startit.sh file must be executed to start the STK client processes on those nodes where the HPSS
PVR is executing. The script will prompt for the following options:
1. Multi-Host or Single-Host - specify m for multiple host.
2. Server side or Client side - Specify c for client side.
3. Remote Host Name - specify the name of the host where the ACSLS software is running.
4. Real ACSLS server or simulated test – specify r for real ACSLS server.
5. Remote Host Version - specify the remote host version which is listed for the ACSLS Release
Number. This will usually be 4:
ACSLS Release Number
5.x, 6.x
6. Whether processes created should be listed (Y or N) - specify either y or n.
7. Whether t_cdriver should be started - specify n.
To terminate the STK client processes, the script t_killit.sh may be executed.
Sample output from t_startit.sh follows:
***** Welcome to t_startit.sh, Version 2.3 *****
This is the automated tester and startit script for the TOOLKIT.
Simply answer the questions which follow.
Executables live in: /opt/hpss/stk/bin
HPSS Management Guide
Release 7.3 (Revision 1.0)
Remote Host Version Number
4
November 2009
122