File Utility Program (FUP) Management Programming Manual

ORSERV Programmatic Interface

File Utility Program (FUP) Management Programming Manual—523322-001

4-9

Elements of SPI Messages for ORSERV

A command and response buffer contains special codes called tokens. Each token

contains a specific piece of information such as the ORSERV command number or

object type.

For example, ZORS-CMD-ONLINERELOAD is the command number token for the

ONLINERELOAD command, and ZORS-OBJ-FILE is the object type token for a file.

Source Definition Files

When you write your application, each module must include the SPI standard

definitions and the ORSERV definitions. Depending on the language you are using,

include these files with your source code (the disk volume is selected at your site):

Naming Rules for Applications

Compaq uses names beginning with the letter Z for all definitions and all fields of

structures in definition files. To avoid conflicts with names defined by Compaq, do not

begin any names you define in your application with an uppercase or lowercase Z.

Common ORSERV Command Syntax Elements

Command Numbers

Each ORSERV command is assigned a unique command number. A command

number is represented by a symbolic name in the form ZORS-CMD-name (name

identifies the command). For example, the symbolic name for the STATUS command is

ZORS-CMD-STATUS. Table 4-1 on page 4-10 show the ORSERV programmatic

commands and object types.

C Use the #INCLUDE directive to include the ZSPIDEF.ZSPIC and

ZSPIDEF.ZORSC files.

COBOL85 Use the COPY statement to include ZSPIDEF.ZSPICOB and

ZSPIDEF.ZORSCOB. Use the COPY statement with the REPLACING

option to include a section of a file.

TACL Load the ZSPIDEF.ZSPITACL and ZSPIDEF.ZORSTACL files. To avoid

buffer overflows during loading, load each file:

PUSH X

#LOAD / LOADED X / $volume.ZSPIDEF.ZORSTACL

POP X

TAL Use the ?SOURCE directive to include ZSPIDEF.ZSPITAL and

ZSPIDEF.ZORSTAL files.