DSM/Tape Catalog Management Programming Manual

DSM/Tape Catalog Management Programming Manual—520481-003
2-1
2
Communicating With MEDIASRV
To route commands to most subsystems, a management application must open a
MEDIASRV server process. If no MEDIASRV process exists, the management
application or an interactive user must start one.
The management application opens the MEDIASRV process, specifying that
messages be in SPI format. The management application and the MEDIASRV process
then exchange SPI command and response messages using the operating-system
WRITEREAD and READUPDATE procedures. When the application completes its
management tasks, it can stop the MEDIASRV process or close it without stopping it.
Starting a MEDIASRV Process
There are two ways to start a MEDIASRV process:
•
Issue a RUN command to a command interpreter.
•
Call the Guardian PROCESS_CREATE_ procedure.
You declare MEDIASRV process run options and startup parameters in the RUN
command or in the PROCESS_CREATE_ procedure call and subsequent startup
message. For a description of these parameters, see Starting a MEDIASRV Process
Using the RUN Command on page 2-2 and Starting a MEDIASRV Process Using the
PROCESS_CREATE_ Procedure on page 2-4.
The MEDIASRV process object file is initially installed in the subvolume
$SYSTEM.SYSnn, but your system manager might move it to another location.
The MEDIASRV process object file must be properly secured:
•
Owned by the super ID
•
PROGID set to the super ID
•
LICENSE set
•
Process access xxNx for network access or xxAx for local system access
Topic Page
Starting a MEDIASRV Process
2-1
Opening a MEDIASRV Process 2-8
Sending Commands and Retrieving Responses 2-9
Stopping a MEDIASRV Process 2-9
Abnormal Process Termination 2-9