File Utility Program (FUP) Management Programming Manual

ORSERV Commands and Responses
File Utility Program (FUP) Management Programming Manual—523322-001
5-8
Considerations
ZSPI-TKN-ERRLIST
is the standard SPI token that begins an error list. The error list ends with
ZSPI-TKN-ENDLIST.
Considerations
When using the ONLINERELOAD command, consider the audit records, the
ZZRELOAD file, and slack values.
Audit Records
The reload operation generates audit records describing the movement of data within
the file. These records can be two or three times the length of the file (not counting free
space).
ZZRELOAD File
ORSERV maintains information about the reload operation in the ZZRELOAD file,
which is located on the same disk volume and subvolume as the target file. If
ZZRELOAD does not exist when you execute the ONLINERELOAD command,
ORSERV creates it.
When ORSERV receives an ONLINERELOAD command, it uses the ZZRELOAD file:
1. Before it sends a response to the requester, ORSERV reads the ZZRELOAD file to
determine if it contains information about a reload operation for the same target file
as specified for the ONLINERELOAD command. ORSERV continues execution:
•
If ORSERV determines that a reload operation is already in progress for the
target file, it returns the ZORS-ERR-ORELOAD-INPROGRESS error and
terminates. The first reload operation continues for the target file.
•
If ORSERV determines that a previous reload operation for the same target file
was stopped or suspended, it continues the reload operation depending on the
value of the ZNEW Boolean field in the ZORS-MAP-PAR-ONLINERELOAD
token. This value is one of:
°
ZSPI-VAL-TRUE—ORSERV starts the reload operation from the beginning
even if a previous reload operation was suspended. ORSERV does not
restart a reload operation that is already in progress.
Note. For more information about all ORSERV error numbers and their corresponding
error lists, see Appendix C, ORSERV Error Messages
.
Note. The structure of the ZZRELOAD file changed for the D20 release. This could cause a
problem if ORSERV and the target file are not on the same node. Requests for STATUS,
RELOAD, or SUSPEND operations do not execute properly unless you start ORSERV on the
same node as the target file.