DSM/Tape Catalog Management Programming Manual

Communicating With MEDIASRV
DSM/Tape Catalog Management Programming Manual—520481-003
2-7
Creating a High-PIN MEDIASRV Process
BEGIN
INT volume [0:3],
subvol [0:3],
filename [0:3];
END
STRING param [0:n-1];
END;
message-len
is the length of the startup message.
Creating a High-PIN MEDIASRV Process
The MEDIASRV program distributed by HP has the HIGHPIN object-file attribute set to
OFF so processes generated from it always run at a low PIN (a process identification
number less than 255). However, you can reset the HIGHPIN attribute to ON and
create high-PIN MEDIASRV processes by issuing these Binder commands:
add * from old-scp-object-file-name
set highpin on
build new-scp-object-file-name
Be sure to set the license and PROGID for the new MEDIASRV object file.
Once the HIGHPIN object-file attribute ON, you can create a high-PIN MEDIASRV
process using the HIGHPIN process option of the RUN command or the
PROCESS_CREATE_ procedure create-options parameter.
Selecting a LOG File
A MEDIASRV process uses the log file specified in the LOG or LOGFILE startup
parameter. Regardless of how you specify it, when selecting a log file:
•
Do not use a terminal as the logging file unless special circumstances require it.
Logging uses waited I/O operations, and terminals are frequently unavailable due
to manual input operations. This can adversely affect MEDIASRV process
performance. A terminal can be an appropriate log file in testing and debugging
environments but usually not in production environments.
•
Using a printer as the log file is subject to the same concerns. Printers can become
not-ready, and the resulting interruption of logging activity can severely impact
performance.
•
Using a spooling process as the log file lets the resulting files be examined online
with the PERUSE program.
•
The use of a disk file as the logging file is the most common choice. Specifying a
disk file as the log file assumes that the file already exists. The types of operations
performed on such files preclude the use of an edit file. Typically, an entry-
sequenced file with a record size of at least 132 bytes is adequate for log output.
You can create such a file with the File Utility Program (FUP):