File Utility Program (FUP) Management Programming Manual

ORSERV Programmatic Interface
File Utility Program (FUP) Management Programming Manual—523322-001
4-10
Common ORSERV Command Syntax Elements
Object Types
The object type designates the object of each command. Each ORSERV command
(except GETVERSION) requires the ZORS-OBJ-FILE object type. GETVERSION
requires the ZORS-OBJ-NULL object type.
Table 4-1. ORSERV Commands and Object Types
Additional ORSERV Command and Response Buffer Tokens
These paragraphs contain additional tokens that are used in ORSERV command or
response buffers—including simple token codes, token types, predefined value names,
field types, token maps and structured tokens.
Simple Token Codes
These are represented by symbolic names using the form Zsss-TKN-name, where
sss is the subsystem abbreviation and name is the token code. An example of a
simple token code for ORSERV is ZORS-TKN-FILE. This identifies the target file for a
command.
Token Types
These are represented by symbolic names using the form Zsss-TYP-name, where
sss is the subsystem abbreviation and name is the token type. ORSERV does not
define any private token types (such as token types with the name ZORS-TYP-name).
Table 4-2, Standard SPI Token Types Used by ORSERV, on page 4-11 shows the
standard SPI token types used by ORSERV.
Predefined Value Names
These are represented by symbolic names using the form Zsss-VAL-name, where sss
is the subsystem abbreviation and name is the predefined value. An example of a
predefined value name for ORSERV is ZORS-VAL-BUFLEN. The recommended buffer
length for the ORSERV command and response buffer.
Note. For more information about object names, see SPI Programming Considerations for
ORSERV on page 4-12.
Symbolic Name (ZORS-CMD-) Object Type (ZORS-OBJ-)
GETVERSION NULL
ONLINERELOAD FILE
STATUS FILE
SUSPEND FILE
Note. For more information about the token codes defined by ORSERV, see Section 5,
ORSERV Commands and Responses.