NetBatch Management Programming Manual

SPI Programming Considerations for the NetBatch
Subsystem
NetBatch Management Programming Manual—522462-003
3-8
Version Compatibility
Version Compatibility
Versions of the NetBatch subsystem that support SPI and EMS are:
To ensure upward compatibility between your applications and later versions of the
NetBatch subsystem, the applications must comply with the SPI and EMS
programming guidelines in the SPI Programming Manual and the EMS Manual.
Security
NetBatch commands are either sensitive or nonsensitive:
•
Sensitive commands affect the configuration or state of objects and are usually
restricted to NetBatch supervisors (users with execute access to the NETBATCH
program file).
•
Nonsensitive commands do not affect the configuration or state of objects and are
available to all users.
For more information, see Section 5, Commands and Responses.
File Names
File names specified in NetBatch SPI commands must have the volume, subvolume,
and file ID components specified. (If the node is not specified, the scheduler uses the
requester’s node.)
•
The scheduler returns a fully qualified file name in a response message except
when the volume is eight characters long (including the dollar sign). In that case,
only the volume, subvolume, and file ID components are returned.
•
The scheduler rejects file names that do not have the volume, subvolume, and file
ID components specified. It also rejects remote file names containing eight-
character volume names.
Displaying SPI Traffic
To display SPI messages that the scheduler receives from and sends to requesters
such as BATCHCOM, do one of:
•
Include the DISPLAY-SPI parameter in the RUN NETBATCH command. For
example:
37> NETBATCH /NAME $ZBAT, NOWAIT/ $DATA7.ZBAT DISPLAY-SPI
The parameter causes the scheduler to write to its log file the contents of each
command buffer received and each response buffer sent.
SPI NetBatch D21 and later
EMS NetBatch D20 and later