File Utility Program (FUP) Management Programming Manual Abstract This manual describes the programmatic interface for the File Utility Program (FUP) and the Online Reload Server (ORSERV). It is intended for programmers who are writing applications that communicate with FUP or ORSERV. Product Version Utilities D46 Supported Releases This manual supports G06.00, D46.00, and all subsequent G0x.xx and D4x.xx releases until otherwise indicated in a new edition.
Document History Part Number Product Version Published 098213 Utilities D20 September 1993 136591 Utilities D46 April 1998 425743-001 Utilites D46 August 2000 429477-001 Utilities D46 July 2001 523322-001 Utilities D46 February 2002
File Utility Program (FUP) Management Programming Manual Index Figures What’s New in This Manual ix Manual Information ix New and Changed Information Tables ix About This Manual xi Who Should Read This Manual? Organization of This Manual xi Related Reading xii Your Comments Invited xii Notation Conventions xiii xi 1.
2. FUP Programmatic Interface (continued) Contents 2. FUP Programmatic Interface (continued) Specifying Object Names 2-12 Discontinuing a Command in Progress 2-13 Receiving and Decoding a Response Buffer 2-13 Handling FUP Errors 2-17 Common Definitions 2-24 SPI Standard Definitions 2-24 FUP Definitions 2-27 3. FUP Commands and Responses CHECKSUM Command 3-2 DUPLICATE Command 3-10 GETVERSION Command 3-22 LOAD Command 3-24 LOADALTFILE Command 3-33 RESTART Command 3-39 4.
. ORSERV Commands and Responses (continued) Contents 5. ORSERV Commands and Responses (continued) ONLINERELOAD Command 5-4 Tokens in the Command Buffer Tokens in the Response Buffer Considerations 5-8 Example 5-9 STATUS Command 5-12 Tokens in the Command Buffer Tokens in the Response Buffer Example 5-16 SUSPEND Command 5-18 Tokens in the Command Buffer Tokens in the Response Buffer Example 5-20 5-5 5-7 5-13 5-13 5-18 5-19 A. Management Application Example B.
B. FUP Error Messages (continued) Contents B.
B. FUP Error Messages (continued) Contents B.
C. ORSERV Error Messages Contents C.
Figures (continued) Contents Figures (continued) Figure 3-3. Figure 4-1. Figure 4-2. Figure 4-3. Figure 4-4. Figure 4-5. Figure 4-6. Figure 4-7. Figure 4-8. Figure 4-9. Figure 5-1. Figure 5-2. Figure 5-3. Figure A-1.
Tables Contents File Utility Program (FUP) Management Programming Manual—523322-001 viii
What’s New in This Manual Manual Information File Utility Program (FUP) Management Programming Manual Abstract This manual describes the programmatic interface for the File Utility Program (FUP) and the Online Reload Server (ORSERV). It is intended for programmers who are writing applications that communicate with FUP or ORSERV. Product Version Utilities D46 Supported Releases This manual supports G06.00, D46.00, and all subsequent G0x.xx and D4x.xx releases until otherwise indicated in a new edition.
What’s New in This Manual New and Changed Information File Utility Program (FUP) Management Programming Manual—523322-001 x
About This Manual Who Should Read This Manual? This manual describes the programmatic interface for the File Utility Program (FUP) and its Online Reload Server (ORSERV) process. The Subsystem Programmatic Interface (SPI) and its message-based, token-oriented interface let programmers write management applications that can communicate with the FUP subsystem.
Related Reading About This Manual Section/Appendix Description Appendix A, Management Application Example Displays an example listing output using the COBOL85 management application to communicate with FUP and execute the programmatic DUPLICATE command Appendix B, FUP Error Messages Describes the FUP errors and supplies a recommended course of action to correct or alleviate each one of them Appendix C, ORSERV Error Messages Describes the ORSERV errors and supplies a recommended course of action to
About This Manual Notation Conventions Notation Conventions Hypertext Links Blue underline is used to indicate a hypertext link within text. By clicking a passage of text with a blue underline, you are taken to the location described. For example: This requirement is described under Backup DAM Volumes and Physical Disk Drives on page 3-2. General Syntax Notation This list summarizes the notation conventions for syntax presentation in this manual: UPPERCASE LETTERS.
About This Manual General Syntax Notation { } Braces. A group of items enclosed in braces is a list from which you are required to choose one item. The items in the list may be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: LISTOPENS PROCESS { $appl-mgr-name } { $process-name } ALLOWSU { ON | OFF } | Vertical Line.
Notation for Messages About This Manual a blank line. This spacing distinguishes items in a continuation line from items in a vertical list of selections. For example: ALTER [ / OUT file-spec / ] CONTROLLER [ , attribute-spec ]... !i and !o. In procedure calls, the !i notation follows an input parameter (one that passes data to the called procedure); the !o notation follows an output parameter (one that returns data to the calling program).
About This Manual Notation for Management Programming Interfaces lowercase italic letters. Lowercase italic letters indicate variable items whose values are displayed or returned. For example: p-register process-name [ ] Brackets. Brackets enclose items that are sometimes, but not always, displayed.
About This Manual Notation for Management Programming Interfaces lowercase letters. Words in lowercase letters are words that are part of the notation, including Data Definition Language (DDL) keywords. For example: token-type !r. The !r notation following a token or field name indicates that the token or field is required. For example: ZCOM-TKN-OBJNAME !o. token-type ZSPI-TYP-STRING. !r The !o notation following a token or field name indicates that the token or field is optional.
About This Manual Notation for Management Programming Interfaces File Utility Program (FUP) Management Programming Manual—523322-001 xviii
1 Introduction You use the File Utility Program (FUP) and its Online Reload Server (ORSERV) process to create and manage disk files. Applications can use the Subsystem Programmatic Interface (SPI) to communicate with FUP or its ORSERV process. Topic Page Subsystem Programmatic Interface (SPI) Overview 1-1 FUP Subsystem Overview 1-2 Using SPI With FUP and ORSERV 1-4 FUP Command and Procedure Differences 1-7 Note. This manual describes SPI information that is specific to FUP and ORSERV.
FUP Subsystem Overview Introduction Figure 1-1. A Management Application and a Subsystem Process A management application sends a command to the subsystem in an SPI command buffer. Management Application Subsystem Process The subsystem executes the command (if no errors occur) and returns a reply to the management application in an SPI response buffer. CDT 004.CDD FUP Subsystem Overview The FUP subsystem consists of the FUP and ORSERV processes.
STATUS Introduction • • An increased number of index levels that cause slower random access time Physical declustering of data on the disk causing slower sequential access time (due to an increased amount of disk read/write head movement), and a reduced capability to perform large I/O transfers An online reload operation performed by ORSERV eliminates these abnormalities. During the reload operation, ORSERV allows the shared-exclusion mode and the read/write access mode for the target file.
Using SPI With FUP and ORSERV Introduction Using SPI With FUP and ORSERV Your management application (COBOL85, C, TACL, or TAL) communicates with FUP and ORSERV processes using SPI. These two programmatic interfaces (FUP and ORSERV) are used to execute specific commands. Figure 1-3 shows an example of a management application communicating with both a FUP and ORSERV process. Figure 1-3.
SPI With ORSERV Introduction SPI With ORSERV You can use the ORSERV programmatic interface to execute the ONLINERELOAD, STATUS, SUSPEND, and GETVERSION commands. Use your management application to create an ORSERV process, open the process, and then send your command request to it. Your management application sends commands directly to the ORSERV process. For more information, see Section 4, ORSERV Programmatic Interface.
SPI With ORSERV Introduction Executing a Sequence of ORSERV Commands The management application you use must create an ORSERV process for each programmatic ORSERV command it executes: 1. Your management application creates an ORSERV process and sends it an ONLINERELOAD command (to perform an online reload operation for a target file).
FUP Command and Procedure Differences Introduction FUP Command and Procedure Differences Table 1-1 shows the interactive FUP commands that you can execute with FUP or ORSERV programmatic commands. This table also provides the NonStop Kernel filesystem procedure for executing the commands (if applicable) and distinguishes between the C-series and D-series file-system procedures. Programmatic commands were developed for most of the FUP functions that did not have a file-system procedure. Note.
FUP Command and Procedure Differences Introduction Table 1-1.
FUP Command and Procedure Differences Introduction Table 1-1.
FUP Command and Procedure Differences Introduction Table 1-1.
FUP Command and Procedure Differences Introduction Table 1-1.
Introduction FUP Command and Procedure Differences File Utility Program (FUP) Management Programming Manual—523322-001 1- 12
2 FUP Programmatic Interface This section describes how a management application program uses the Subsystem Programmatic Interface (SPI) to communicate with a FUP process.
Communicating With FUP FUP Programmatic Interface FUP uses the default volume and subvolume in the startup message unless ZSCRATCH is specified only for the LOAD or LOADALTFILE commands. They are not used for the other commands. The text portion of the startup message must be filled with zeros. Figure 2-1. Communicating With FUP Management Application 1. Start a FUP process. 2. Open the FUP process and send a startup message. 3. Close the FUP process. 4.
FUP Programmatic Interface Communicating With FUP 3. After you send the startup message, close FUP. 4. Open FUP for programmatic use. Use #ZSPI as the first qualifier (in the process file name) when you open FUP. The process file name must have the format: $process-name.#ZSPI You can include backup OPENs and CLOSEs in FUP, but the first qualifier of the process file name for a backup OPEN must also be #ZSPI.
FUP Programmatic Interface Communicating With FUP 6. Initialize the command buffer. Call the SSINIT procedure to specify the FUP command and initialize the buffer (including the addition of header tokens). 7. Initialize and set the fields of structured tokens. Call the SSNULL procedure to initialize the fields of each extensible structured token to null values, then set the individual fields of each structured token. 8. Add the tokens to the buffer.
FUP Programmatic Interface Starting and Opening FUP (TAL Example) Starting and Opening FUP (TAL Example) Figure 2-2 shows an example of a TAL integer procedure that is used to start and open a FUP process for programmatic use. Figure 2-2. TAL Procedure to Start and Open a FUP Process (page 1 of 2) !-------------------------------------------------------! Procedure START^AND^OPEN^PUP^PROCESS starts a new FUP ! process and opens the process for programming use.
FUP Programmatic Interface Starting and Opening FUP (TAL Example) Figure 2-2.
FUP Programmatic Interface Sending a Buffer to FUP (TAL Example) Sending a Buffer to FUP (TAL Example) Figure 2-3 shows an example of a TAL integer procedure that sends and receives a buffer using the WRITEREADX procedure. Figure 2-3. TAL Procedure to Send a Buffer to FUP !--------------------------------------------------------! Procedure SEND^TO^SPI^PROCESS sends and receives a buffer ! using the WRITEREAD procedure. The FUP process must al! ready be started and opened.
Elements of SPI Messages for FUP FUP Programmatic Interface Elements of SPI Messages for FUP A command and response buffer contains special codes called tokens. Each token contains a specific piece of information such as the command number or object type. Examples of these tokens are ZFUP-CMD-CHECKSUM, which is the command number token for the CHECKSUM command, and ZFUP-OBJ-FILE, which is the object-type token.
Common Syntax Elements FUP Programmatic Interface parameter identifies the command.) For example, the symbolic name for the LOAD command is ZFUP-CMD-LOAD. Object Types Each FUP command (except GETVERSION) supports the object type ZFUP-OBJFILE. GETVERSION supports the ZFUP-OBJ-NULL object type. FUP object-name tokens designate a file name or a file set. Table 2-1 shows the FUP programmatic commands and object types. Note.
Common Syntax Elements FUP Programmatic Interface Table 2-2.
Standard SPI Token Types FUP Programmatic Interface Event Messages Although FUP does not report event messages to the Event Management Service (EMS), event messages can be generated by the NonStop Kernel or the disk process when you use the programmatic interface to FUP. Note. For more information, see the Operator Messages Manual. Standard SPI Token Types Table 2-3.
FUP Programmatic Interface SPI Programming Considerations for FUP SPI Programming Considerations for FUP The SPI Programming Manual provides general programming considerations for management applications that use SPI command and response buffers to communicate with subsystems such as FUP. This subsection provides considerations specific to FUP. Building the Command Buffer Your application must allocate a command and response buffer to communicate with FUP.
Discontinuing a Command in Progress FUP Programmatic Interface Specifying a File Set The CHECKSUM command and the DUPLICATE command (without the restartable option specified) support a template using the asterisk (*) to specify a file set within a volume or subvolume. A file set can be a single file, all files in a subvolume, or all files in a volume. You cannot use the asterisk to specify the volume name or the subvolume name when you specify a file name. Table 2-4 shows examples of file-set templates.
Receiving and Decoding a Response Buffer FUP Programmatic Interface You should also check the values of these tokens in the SPI message header to ensure that the response matches the original command: ZSPI-TKN-COMMAND FUP command from the request. ZSPI-TKN-OBJECT-TYPE Object type from the request. ZSPI-TKN-SSID Subsystem ID of the FUP server that performed the command. If no errors are found, you can extract the remaining tokens from the buffer and continue processing.
FUP Programmatic Interface Receiving and Decoding a Response Buffer To checksum or duplicate the next file in the file set, return the original command buffer and ZSPI-TKN-CONTEXT to FUP. FUP uses ZSPI-TKN-CONTEXT to determine which file to process next. After FUP processes the last file in the file set, it returns a reply without ZSPI-TKN-CONTEXT. Your application is not required to continue a command when a response record buffer contains the ZSPI-TKN-CONTEXT token.
FUP Programmatic Interface Receiving and Decoding a Response Buffer Each data list contains a ZSPI-TKN-RETCODE token to indicate the error status of the response for a specific file. Figure 2-6 on page 2-16 shows a single response record in a data list. The error list is present only if an error occurred, as indicated by ZSPI-TKN-RETCODE. Figure 2-6. Single FUP Record in a Data List ZSPI-TKN-DATALIST ZSPI-TKN-RETCODE ZFUP-TKN-FILE token-1 token-2 . . .
FUP Programmatic Interface Handling FUP Errors If the value of ZSPI-TKN-RESPONSE-TYPE is ZSPI-VAL-ERR-AND-WARN, and a warning occurs for the command (not caused by the execution of the command on a file), FUP holds the warning until it generates a response caused by an error or warning for one of the files. If no warnings or errors are generated for any of the files, FUP returns the command warning in an empty response.
Handling FUP Errors FUP Programmatic Interface Types of FUP Errors When your application sends a command buffer to FUP, these types of errors can be returned: • • • Syntax errors in the FUP command format Command failure errors encountered by FUP Command failure errors encountered by a subsystem or software component other than FUP Syntax Errors in the Command Format FUP evaluates the command format in the buffer to determine if any syntax errors exist.
Handling FUP Errors FUP Programmatic Interface Figure 2-9.
Handling FUP Errors FUP Programmatic Interface Figure 2-10.
Handling FUP Errors FUP Programmatic Interface Figure 2-11.
FUP Programmatic Interface Handling FUP Errors Figure 2-12. Extracting Tokens From a Nested Error List (page 1 of 2) ! Get the FASTSORT error CALL SSGETTKN (buffer, ZSPI^TKN^ERROR, sort^error, 1); . . . ! Extracting tokens from a nested error list ! Variables to extract a token map from the buffer INT .cmd^error^resp^map [0:(ZFUP^MAP^CMD^ERROR^WLN-1)] := ZFUP^MAP^CMD^ERROR; STRUCT .error^info (ZFUP^DDL^CMD^ERROR^DEF); . . .
Handling FUP Errors FUP Programmatic Interface Figure 2-12. Extracting Tokens From a Nested Error List (page 2 of 2) ! Get the FASTSORT error CALL SSGETTKN (buffer, ZSPI^TKN^ERROR, sort^error, 1); . . .
Common Definitions FUP Programmatic Interface Continuing After an Error An error can occur on only one of the files in a file set for the commands that process more than one file (CHECKSUM and DUPLICATE without the restartable option). If an error does occur on a file, the SPI token ZSPI-TKN-ALLOW-TYPE determines if FUP should continue processing the remaining files in the file set.
SPI Standard Definitions FUP Programmatic Interface Table 2-6.
FUP Programmatic Interface SPI Standard Definitions ZSPI-TKN-COMMAND contains the command number for these FUP programmatic commands: CHECKSUM, DUPLICATE, GETVERSION, LOAD, LOADALTFILE, or RESTART. ZSPI-TKN-ERROR is the error token that is present in an error list. This token contains the FUP subsystem ID and error number. For more information about all FUP numbers and their associated error lists, see Appendix B, FUP Error Messages.
FUP Definitions FUP Programmatic Interface FUP Definitions FUP definitions begin with ZFUP- and are found in the source definition files ZFUPTAL, ZFUPCOB, ZFUPTACL, and ZFUPC. For more information about FUP definitions, see Section 3, FUP Commands and Responses. FUP Message Buffer Declaration ZFUP-DDL-MSG-BUFFER is the SPI buffer you use for the FUP commands. For example: def ZFUP-DDL-MSG-BUFFER. 02 Z-MSGCODE 02 Z-BUFLEN 02 Z-OCCURS 02 Z-FILLER type ZSPI-DDL-INT. type ZSPI-DDL-UINT. type ZSPI-DDL-UINT.
FUP Definitions FUP Programmatic Interface ZNAME is the name of the file that FUP was processing (or attempting to process) when the error occurred. ZCOMMAND is the FUP command that was executing when the error occurred. ZOBJECT is the object type for the FUP command. Note. For more information about all FUP error numbers and their corresponding error lists, see Appendix B, FUP Error Messages. Table 2-7.
3 FUP Commands and Responses This section describes the FUP programmatic commands and responses for: Command Page CHECKSUM 3-2 DUPLICATE 3-10 GETVERSION 3-22 LOAD 3-24 LOADALTFILE 3-33 RESTART 3-39 Each description contains: • • • • • • A header showing the command name A summary of the function of the command A box that lists these elements for each command: ° ° ° ° The symbolic name for the command number The symbolic name of the object type A list of tokens that can be used in the comm
CHECKSUM Command FUP Commands and Responses CHECKSUM Command The CHECKSUM command recomputes the checksum value for blocks of data in disk files. Command ZFUP-CMD-CHECKSUM Object Type ZFUP-OBJ-FILE Tokens in the Command Buffer ZFUP-TKN-FILE token-type ZSPI-TYP-FNAME. ZFUP-MAP-PAR-CHECKSUM def ZFUP-DDL-PAR-CHECKSUM. 02 ZPART-ONLY type ZSPI-DDL-BOOLEAN. end.
FUP Commands and Responses CHECKSUM Command ZFUP-MAP-PAR-CHECKSUM is an optional structured token that specifies whether primary or secondary partitions of a partitioned file are to have the checksum value recomputed. Only one of these tokens is allowed per command. ZPART-ONLY is a Boolean field with these values: ZSPI-VAL-TRUE specifies to have the checksum value recomputed for only the primary or secondary partitions of a partitioned file (defined by the file-set template).
FUP Commands and Responses CHECKSUM Command ZSPI-VAL-ERR-AND-WARN FUP returns a response record only for a file that caused an error or a warning. The response buffer contains at least one error list (despite the value of ZSPI-TKN-RETCODE). ZSPI-VAL-ERR-WARN-AND-NORM FUP returns a response record for each file processed. This is the default.
CHECKSUM Command FUP Commands and Responses ZFUP-TKN-FILE is the name of the file on which the CHECKSUM command was attempted. The file name is in the Guardian internal file-name format. This token is returned with every response. ZSPI-TKN-RETCODE is the standard SPI return token that is returned in the response buffer by all Compaq subsystems. ZSPI-TKN-RETCODE contains zero if the command was successful or an error number if an error occurred.
FUP Commands and Responses CHECKSUM Command Considerations • • • CHECKSUM reads each block of data from each file specified by ZFUP-TKN-FILE and recomputes the checksum value for each block. However, CHECKSUM rewrites only the blocks with incorrect checksum values. Checksum errors usually indicate a potential data integrity problem. CHECKSUM recomputes the checksum value for blocks of data but does not correct any data that might have changed.
CHECKSUM Command FUP Commands and Responses Figure 3-1. TAL Example of a CHECKSUM Procedure (page 1 of 3) !---------------------------------------------------------! Procedure CHECKSUM is a high-level procedure that ! demonstrates the use of the programmatic FUP interface ! with file-name templates. RESPONSE-TYPE is set to the ! default value, and MAXRESP is set to -1. ! ! FUP returns a response record for each file and returns ! as many response records as will fit in the buffer.
CHECKSUM Command FUP Commands and Responses Figure 3-1. TAL Example of a CHECKSUM Procedure (page 2 of 3) index, number^returned; INT(32) token^code; ! Index variable ! Tokens returned ! Token codes ! Variables to extract a map token from the buffer INT .checksum^par^def [0: (ZFUP^MAP^PAR^CHECKSUM^WLN - 1)] := ZFUP^MAP^PAR^CHECKSUM; STRUCT .params (ZFUP^DDL^PAR^CHECKSUM^DEF); STRUCT .
CHECKSUM Command FUP Commands and Responses Figure 3-1.
DUPLICATE Command FUP Commands and Responses DUPLICATE Command The DUPLICATE command makes a copy of one or more disk files. Command ZFUP-CMD-DUPLICATE Object Type ZFUP-OBJ-FILE Tokens in the Command Buffer ZFUP-TKN-SOURCE-FILE ZFUP-TKN-DEST-FILE ZFUP-TKN-RESTART-FILE token-type ZSPI-TYP-FNAME. token-type ZSPI-TYP-FNAME. token-type ZSPI-TYP-FNAME. ZFUP-MAP-PAR-DUP def ZFUP-DDL-PAR-DUP.
DUPLICATE Command FUP Commands and Responses Tokens in the Response Buffer ZSPI-TKN-DATALIST ZFUP-TKN-FILE ZSPI-TKN-RETCODE ZSPI-TKN-ERRLIST ... ZSPI-TKN-ENDLIST ZSPI-TKN-ENDLIST ZSPI-TKN-CONTEXT token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-FNAME. ZSPI-TYP-RETCODE. ZSPI-TYP-LIST. token-type ZSPI-TYP-SSCTL. token-type ZSPI-TYP-SSCTL. token-type ZSPI-TYP-BYTESTRING.
FUP Commands and Responses DUPLICATE Command ZPART-ONLY is a Boolean field with these values: ZSPI-VAL-TRUE specifies only the primary or secondary partitions of a partitioned file (and any nonpartitioned files) are to be duplicated, if they are designated by the source template. Entire partitioned files are not duplicated. ZSPI-VAL-FALSE specifies any primary partitions of a partitioned file (all partitions) are to be duplicated, if they are designated by the source template.
FUP Commands and Responses DUPLICATE Command ZSPI-VAL-FALSE specifies that the destination file assumes the default security of the executor of the DUPLICATE command. The default is ZSPI-VAL-FALSE. ZDEST-OPTION is an enumerated field that specifies the destination file options. The values are: ZFUP-VAL-NEW FUP creates a new destination file with the same characteristics as the source file. If a duplicate destination file already exists, FUP returns an error. The default is ZFUP-VAL-NEW.
FUP Commands and Responses DUPLICATE Command ZPART-NAME specifies the new volume name for the partition specified by ZPART-NUMBER. This field does not have a default value. To rename the volume, supply a value that is not null. ZPRIEXT-SIZE specifies the primary extent size (in pages) of the destination file. The allowable values are in the range 0 through 512,000,000. The default is one page (2,048 bytes). If you specify an extent size over 65,535 pages, you must assign Format 2 to your files.
FUP Commands and Responses DUPLICATE Command ZSPI-TKN-MAXRESP is the standard SPI token that indicates the maximum number of response records that FUP returns in a response buffer. The values for ZSPI-TKN-MAXRESP are: 0 FUP returns one response record per buffer (not enclosed in a data list). This is the default. -1 FUP returns as many response records per buffer as the buffer can hold (with each response record enclosed in a data list).
FUP Commands and Responses DUPLICATE Command ZSPI-VAL-NORM-ONLY FUP processes the next file only if the command was successful for the current file (that is, FUP did not return an error list for the file). This is the default. ZSPI-VAL-WARN-AND-NORM FUP processes the next file if the command completed for the current file. A warning might have occurred for the file, but the ZSPI-TKN-RETCODE value is zero.
DUPLICATE Command FUP Commands and Responses Table 3-2. Errors Returned by DUPLICATE (page 1 of 2) Error Number Symbolic Name (ZFUP-ERR-) Description 21 BAD-KEY FUP found invalid alternate-key parameters. 30 AKNOUP FUP did not change the alternate-key files. 32 DUP-SEC-PART FUP found an invalid renames option. 33 EBCDICIN-CONFLICT The TAPE DEFINE value for EBCDIC conflicts with ZEBCDIC. 34 SEC-PART A secondary partition file is not allowed.
DUPLICATE Command FUP Commands and Responses Table 3-2. Errors Returned by DUPLICATE (page 2 of 2) Error Number Symbolic Name (ZFUP-ERR-) 85 ALT-FILE-MISSING An alternate key does not have an alternate-key file. 100 REST-TOO-MANY-FILES More than one source file is specified, and the restartable option is selected. 101 OPTICAL-RESTART-FILE The restart file is located on an optical disk volume. Description ZSPI-TKN-ERRLIST is the standard SPI token that begins an error list.
DUPLICATE Command FUP Commands and Responses • If an application specifies an existing file for the restart file, or if the ZZRSTART file already exists (and ZFUP-TKN-RESTART-FILE contains all blanks), FUP returns the error ZFUP-ERR-FILESYS. This error indicates that a file-system error occurred. The response buffer contains a second error list indicating file-system error 10 (file already exists). Example Figure 3-2 shows a TAL example of a high-level procedure for the DUPLICATE command: Figure 3-2.
FUP Commands and Responses DUPLICATE Command Figure 3-2. TAL Example of a DUPLICATE Procedure (page 2 of 3) BEGIN ! Global variables used ! STRUCT .EXT buffer (ZFUP^DDL^MSG^BUFFER^DEF); ! STRUCT .EXT save^buffer (ZFUP^DDL^MSG^BUFFER^DEF); ! INT fup^file^number; ! Local Definitions INT error, spi^error, done; INT .dup^par^def [0:(ZFUP^MAP^PAR^DUP^WLN - 1)] := ZFUP^MAP^PAR^DUP; STRUCT .params (ZFUP^DDL^PAR^DUP^DEF); STRUCT .
FUP Commands and Responses DUPLICATE Command Figure 3-2. TAL Example of a DUPLICATE Procedure (page 3 of 3) BEGIN CALL SSNULL (dup^par^def, params); IF $PARAM (partonly) THEN params.zpart^only := partonly; IF $PARAM (preserve^timestamp ) THEN params.zpreserve^timestamp := preserve^timestamp; IF $PARAM (preserve^owner ) THEN params.zpreserve^owner := preserve^owner; IF $PARAM (preserve^security ) THEN params.zpreserve^security := preserve^security; IF $PARAM (destoption ) THEN params.
GETVERSION Command FUP Commands and Responses GETVERSION Command The GETVERSION command returns the FUP server version in the ZSPI-TKNSERVER-VERSION token (in the SPI header) and the server ID string in the token ZSPI-TKN-SERVER-BANNER. Command ZFUP-CMD-GETVERSION Object Type None. Tokens in the Command Buffer ZSPI-TKN-COMMENT token-type ZSPI-TYP-STRING. Tokens in the Response Buffer ZSPI-TKN-SERVER-BANNER ZSPI-TKN-RETCODE token-type ZSPI-TYP-CHAR50. token-type ZSPI-TYP-RETCODE. ZSPI-TKN-ERRLIST ...
FUP Commands and Responses GETVERSION Command release-date is the FUP release date. An example is 01APR01. compilation-date is the FUP compilation date. An example of this is 01APR97. ZSPI-TKN-RETCODE is the standard SPI return token that is returned in the response buffer by all Compaq subsystems. ZSPI-TKN-RETCODE contains zero if the command was successful, or an error number if an error occurred. Note.
LOAD Command FUP Commands and Responses LOAD Command The LOAD command loads data into a structured disk file without affecting any associated alternate-key files. Command ZFUP-CMD-LOAD Object Type ZFUP-OBJ-FILE Tokens in the Command Buffer ZFUP-TKN-SOURCE-FILE token-type ZSPI-TYP-FNAME. ZFUP-TKN-DEST-FILE token-type ZSPI-TYP-FNAME. ZFUP-MAP-LOAD-SOURCE-OPTS def ZFUP-DDL-LOAD-SOURCE-OPTS.
LOAD Command FUP Commands and Responses 02 02 02 02 02 02 end. ZPARTOF ZSORTED ZMAX-RECS ZSCRATCH ZDSLACK ZISLACK type type type type type type ZSPI-TKN-MAXRESP ZSPI-TKN-RESPONSE-TYPE ZSPI-TKN-ALLOW-TYPE ZSPI-TKN-COMMENT ZSPI-DDL-DEVICE. ZSPI-DDL-BOOLEAN. ZSPI-DDL-INT4. ZSPI-DDL-FNAME. ZSPI-DDL-INT. ZSPI-DDL-INT. token-type token-type token-type token-type ZSPI-TYP-INT. ZSPI-TYP-ENUM. ZSPI-TYP-ENUM. ZSPI-TYP-STRING.
FUP Commands and Responses LOAD Command ZBLOCK-SIZE specifies the number of bytes in an input block. The allowable values are in the range 1 through 32,767. ZRECORD-SIZE specifies the maximum number of bytes in an input record. The allowable values are in the range 1 through 4096. ZVAR-REC is a Boolean field with these values: ZSPI-VAL-TRUE FUP reads variable-length, blocked records. ZSPI-VAL-FALSE FUP does not read variable-length, blocked records. The default is ZSPI-VAL-FALSE.
FUP Commands and Responses LOAD Command ZSPI-VAL-TRUE FUP assumes that the source file contains EBCDIC characters and translates the characters to their ASCII equivalents. ZSPI-VAL-FALSE FUP assumes that the source file contains ASCII characters. The default is ZSPI-VAL-FALSE. ZUNLOAD is a Boolean field that applies only to magnetic tape. It can have these values: ZSPI-VAL-TRUE FUP unloads the tape after rewinding. The default is ZSPI-VAL-TRUE. ZSPI-VAL-FALSE FUP does not unload the tape after rewinding.
FUP Commands and Responses LOAD Command ZTRIMCHAR-IS-PRESENT is a Boolean field with these values: ZSPI-VAL-TRUE specifies that the trim character (ZTRIMCHAR) is supplied. You must use this field if a value is supplied in ZTRIMCHAR. ZSPI-VAL-FALSE specifies that the trim character (ZTRIMCHAR) is not supplied. This is the default. ZTRIMCHAR specifies an ASCII trim character. Any trailing characters matching this character are deleted from the input record.
FUP Commands and Responses LOAD Command ZPADCHAR is a field that specifies an ASCII pad character. If an input file record length contains fewer bytes than the output file record length, FUP pads the destination file record with this character (up to the output file record length). To supply this field, specify ZSPI-VAL-TRUE with ZPADCHAR-IS-PRESENT. ZFUP-MAP-LOAD-KEYSEQ-OPTS is an optional structured token that specifies options for a key-sequenced destination file.
LOAD Command FUP Commands and Responses ZSPI-TKN-MAXRESP, ZSPI-TKN-RESPONSE-TYPE, ZSPI-TKN-ALLOW-TYPE are standard SPI response-control tokens. If you can set these tokens, they have no effect on the execution of the command. ZSPI-TKN-COMMENT is the standard SPI token that allows you to include an 80-byte arbitrary comment in the command buffer. Although FUP ignores ZSPI-TKN-COMMENT in the command buffer, the token can be useful when you are debugging an application.
LOAD Command FUP Commands and Responses Table 3-3. Errors Returned by LOAD (page 2 of 2) Error Number Symbolic Name (ZFUP-ERR-) Description 43 INV-FTYPE FUP could not load an unstructured file. 55 RECIN-CONFLICT FUP encountered a TAPE DEFINE conflict with the record length. 56 RECLEN-BIG A TAPE DEFINE RECLEN is too large. 62 TRUNC Truncation is occurring. 64 USE-EXT-N-READ FUP encountered a TAPE DEFINE USE EXTEND error. 65 USE-OUT-N-READ FUP encountered a TAPE DEFINE USE OUT error.
FUP Commands and Responses • • • • • • • • LOAD Command If you specify the ZPARTOF option when loading a nonpartitioned file, FUP returns an error message. If the base partition specified with ZPARTOF does not exist, filesystem error #11 (file not in directory) is returned. If the base partition specified with ZPARTOF is not a partitioned file (or is not a partition of the file being loaded), FUP returns the ZFUP-ERR-BAD-PARTS error list.
LOADALTFILE Command FUP Commands and Responses LOADALTFILE Command The LOADALTFILE command generates alternate-key records from a specified primary file and loads the alternate-key records into an alternate-key file. Command ZFUP-CMD-LOADALTFILE Object Type ZFUP-OBJ-FILE Tokens in the Command Buffer ZFUP-TKN-SOURCE-FILE ZFUP-TKN-ALTFILE-NUM ZFUP-MAP-PAR-LOADALTFILE token-type ZSPI-TYP-FNAME. token-type ZSPI-TYP-INT. def ZFUP-DDL-PAR-LOADALTFILE.
FUP Commands and Responses LOADALTFILE Command Tokens in the Command Buffer ZFUP-TKN-SOURCE-FILE is a required token that specifies an existing primary file whose alternate-key records are to be generated and loaded into the file indicated by the alternate-key file number (ZFUP-TKN-ALTFILE-NUM token). The file name must be in the Guardian internal file-name format. Only one of these tokens is allowed per command.
FUP Commands and Responses LOADALTFILE Command ZSPI-TKN-COMMENT is the standard SPI token that allows you to include an 80-byte arbitrary comment in the command buffer. Although FUP ignores ZSPI-TKN-COMMENT in the command buffer, the token can be useful when you are debugging an application. Tokens in the Response Buffer ZSPI-TKN-DATALIST is the standard SPI token that begins a data list. The data list ends with ZSPI-TKN-ENDLIST.
LOADALTFILE Command FUP Commands and Responses Table 3-4. Errors Returned by LOADALTFILE Error Number Symbolic Name (ZFUP-ERR-) Description 21 BAD-KEY FUP detected invalid alternate-key parameters. 37 FILE-KEY-INCOM An alternate-key file is invalid with the specified alternate keys. 47 NO-ALT-FILE An alternate-key file does not exist. 59 SHORT-KEYS FUP detected incomplete alternate-key fields. ZSPI-TKN-ERRLIST is the standard SPI token that begins an error list.
LOADALTFILE Command FUP Commands and Responses Example Figure 3-3, TAL Example of a LOADALTFILE Procedure shows a TAL example of a high-level integer procedure for the LOADALTFILE command. Figure 3-3. TAL Example of a LOADALTFILE Procedure (page 1 of 2) !---------------------------------------------------------! LOADALTFILE is an example of a high-level procedure ! for the FUP LOADALTFILE command. This procedure assumes ! that the FUP process has already been started.
FUP Commands and Responses LOADALTFILE Command Figure 3-3. TAL Example of a LOADALTFILE Procedure (page 2 of 2) STRUCT STRUCT .params (ZFUP^DDL^PAR^LOADALTFILE^DEF); .
RESTART Command FUP Commands and Responses RESTART Command The RESTART command continues a duplication operation for a DUPLICATE command that failed before it was finished. The DUPLICATE command must have been executed with the restartable option specified. RESTART uses information stored in a disk restart file to determine where the restart should begin. Command ZFUP-CMD-RESTART Object Type ZFUP-OBJ-FILE Tokens in the Command Buffer ZFUP-TKN-RESTART-FILE token-type ZSPI-TYP-FNAME.
RESTART Command FUP Commands and Responses ZSPI-TKN-MAXRESP, ZSPI-TKN-RESPONSE-TYPE, ZSPI-TKN-ALLOW-TYPE are standard SPI response-control tokens. If you set these tokens, they have no effect on the execution of the command. ZSPI-TKN-COMMENT is the standard SPI token that allows you to include an 80-byte arbitrary comment in the command buffer. Although FUP ignores ZSPI-TKN-COMMENT in the command buffer, the token can be useful when you are debugging an application.
FUP Commands and Responses RESTART Command ZSPI-TKN-ERRLIST is the standard SPI token that begins an error list. The error list ends with ZSPI-TKNENDLIST. Note. For more information about all FUP error numbers and their corresponding error lists, see Appendix B, FUP Error Messages. Considerations • • • • When the RESTART command is issued, FUP verifies: ° ° ° ° The destination file is corrupt.
FUP Commands and Responses RESTART Command File Utility Program (FUP) Management Programming Manual—523322-001 3- 42
4 ORSERV Programmatic Interface This section describes how a management application program uses the Subsystem Programmatic Interface (SPI) to communicate with an ORSERV process.
Communicating With ORSERV ORSERV Programmatic Interface 2. Open ORSERV. The process file name must have the internal file-name format. You can include backup OPENs and CLOSEs in ORSERV. Figure 4-1. Communicating With ORSERV Management Application 1. Start an ORSERV process. 2. Open ORSERV. 3. Send a startup message. 4. Close ORSERV. 5. Open ORSERV using #ZSPI. 6. Allocate the command and response buffer. 7. Initialize the command buffer. 8. Initialize and set the fields of structured tokens. ORSERV 9.
ORSERV Programmatic Interface • • • Communicating With ORSERV You can have only one ORSERV process open. You must not open ORSERV using NOWAIT I/O. The SYNC depth cannot be greater than one. Check for any file-system errors after you open ORSERV. File-system errors associated with applications using SPI include: • • • • (Error 12) Your management process tried to open ORSERV more than once. (Error 17) A problem occurred during the backup OPEN.
ORSERV Programmatic Interface Communicating With ORSERV 8. Initialize and set the fields of structured tokens. Call the SSNULL procedure to initialize the fields of each extensible structured token to null values, then set the individual fields of each structured token. 9. Add the tokens to the buffer. Call the SSPUT procedure for each token that you want put in the buffer. Specify the command buffer, the unique token code, and a token value for each token. SSPUT places the token values in the buffer. 10.
ORSERV Programmatic Interface Starting and Opening ORSERV (TAL Example) of the reload operation, use the STATUS command. The ORSERV process stops after it completes the RELOAD. Note. ORSERV and the target file must be on the same system, or you receive an error message (ZORS-ERR-WRONG-SERVER). • STATUS and SUSPEND commands The response buffer is returned, and stops after ORSERV executes a STATUS or SUSPEND command.
ORSERV Programmatic Interface Starting and Opening ORSERV (TAL Example) Figure 4-2. TAL Procedure to Start and Open ORSERV (page 2 of 2) ! --------------------------------------------------------! Open the ORSERV process and check for an error.
ORSERV Programmatic Interface Sending a Buffer to ORSERV (TAL Example) Sending a Buffer to ORSERV (TAL Example) Figure 4-3, TAL Procedure to Send a Buffer to ORSERV shows an example of a TAL integer procedure that sends and receives an ORSERV command and response buffer using the WRITEREAD procedure. This example searches for a file-system error, verifies that it is an SPI buffer, and checks if the entire buffer was read. Note.
ORSERV Programmatic Interface Sending a Buffer to ORSERV (TAL Example) Figure 4-3. TAL Procedure to Send a Buffer to ORSERV (page 2 of 2) CALL WRITEREAD (ORSERV^file^number, buffer, used^length, ZORS^VAL^BUFLEN); IF < THEN BEGIN CALL FILEINFO(ORSERV^file^number,error); ! ! ! ! IF error THEN CALL fs^error^handler (error); END; --------------------------------------------------------Check that the response buffer is an SPI buffer and that ORSERV read all of the buffer.
ORSERV Programmatic Interface Elements of SPI Messages for ORSERV 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.
ORSERV Programmatic Interface 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. Note. For more information about object names, see SPI Programming Considerations for ORSERV on page 4-12. Table 4-1.
Standard SPI Token Types ORSERV Programmatic Interface Token Maps and Structured Tokens A token map is a variable-length integer array that contains decoding information and a reference name for an extensible structured token. A token map contains a token code and a description of the token value—including the token fields, the null values for the fields, and the version number for the fields. An application uses a token map to pass information in an extensible structured token to ORSERV. Note.
ORSERV Programmatic Interface SPI Programming Considerations for ORSERV Table 4-2.
Discontinuing a Command in Progress ORSERV Programmatic Interface ORSERV accepts a single file name as the object of a command. The name cannot be a file set or file-set list. You specify the target file name in the ZORS-TKN-FILE token. The file name must be in the Guardian internal file-name format and must be fully qualified. If the file is not on the same system as ORSERV, the name must be in Guardian network internal filename format.
ORSERV Programmatic Interface Handling ORSERV Errors Extracting Tokens From an ORSERV Response Record An ORSERV command generates a single response record in the response buffer. This response record describes the action of the ORSERV command on a single file. Figure 4-4 shows a single ORSERV response record. The tokens are not necessarily in the same order as the ones displayed here. Figure 4-4. Tokens in a Response Buffer token-1 token-2 . . .
ORSERV Programmatic Interface • Handling ORSERV Errors All of the ORSERV errors (including a cause and recovery for each error) in Appendix C, ORSERV Error Messages. An error list begins with ZSPI-TKN-ERRLIST and ends with ZSPI-TKN-ENDLIST. Each error list describes an error or warning. The ZSPI-TKN-ERROR error token, which is included in the error list, specifies the error that occurred.
Handling ORSERV Errors ORSERV Programmatic Interface • • Command failure errors encountered by ORSERV Command failure errors encountered by a subsystem or software component other than ORSERV Syntax Errors in the Command Format ORSERV first evaluates the command format in the buffer to determine if any syntax errors exist. Examples are an invalid token value or an invalid command.
Handling ORSERV Errors ORSERV Programmatic Interface Figure 4-7.
ORSERV Programmatic Interface Handling ORSERV Errors Figure 4-9. Extracting Tokens From an ORSERV Nested Error List ! Get ZSPI^TKN^RETCODE from the response buffer. SSGETTKN (buffer, ZSPI^TKN^RETCODE, return^code, 1) ! -------------------------------------- ORSERV error list ! Enter the ORSERV error list. SSGETTKN (buffer, ZSPI^TKN^ERRLIST, 1); ! Get the ORSERV error number and SSID.
Common Definitions ORSERV Programmatic Interface Common Definitions The ORSERV programmatic commands use SPI standard definitions and ORSERV definitions. Although this subsection provides a general description of these definitions, for specific information about each definition, see Section 5, ORSERV Commands and Responses, or Appendix C, ORSERV Error Messages. Note. All definitions are shown in DDL (or COBOL85) format using hyphens (-) as separators.
SPI Standard Definitions ORSERV Programmatic Interface Table 4-3.
SPI Standard Definitions ORSERV Programmatic Interface ZSPI-TKN-OBJECT-TYPE contains the object-type number for the ORSERV object. The object-type for ORSERV commands is ZORS-OBJ-FILE (except for the GETVERSION command, which is ZORS-OBJ-NULL). ZSPI-TKN-RETCODE is the return token. Table 4-4 shows the ZSPI-TKN-RETCODE values common to all ORSERV commands: Table 4-4. Errors Returned by All ORSERV Commands Error Number Symbolic Name (ZORS-ERR-) Description 0 OK The command completed successfully.
ORSERV Definitions ORSERV Programmatic Interface ZSPI-TKN-SERVER-VERSION contains the server version of the ORSERV subsystem. ORSERV Definitions ORSERV definitions begin with ZORS- and appear in the source definition files ZORSTAL, ZORSCOB, ZORSTACL, and ZORSC. The ORSERV definitions are described here. Note. For more information about the ORSERV definitions, see Section 5, ORSERV Commands and Responses. ORSERV Message Buffer Declaration ZORS-DDL-MSG-BUFFER is the SPI buffer you use for ORSERV commands.
ORSERV Programmatic Interface ORSERV Definitions Simple and Structured Tokens These simple tokens are specific to ORSERV: ZORS-TKN-FILE specifies the name of the target file that is the object of the reload operation. ZORS-TKN-VOLUME specifies the name of a disk volume. Note. For definitions of the structured tokens specific to ORSERV, see Section 5, ORSERV Commands and Responses.
ORSERV Programmatic Interface ORSERV Definitions File Utility Program (FUP) Management Programming Manual—523322-001 4- 24
5 ORSERV Commands and Responses This section describes the ORSERV programmatic commands and responses for: Command Page GETVERSION 5-2 ONLINERELOAD 5-4 STATUS 5-12 SUSPEND 5-18 Each description contains: • • • • • • A header showing the command name A summary of the function of the command A box that lists these elements for each command: ° ° ° ° The symbolic name for the command number The symbolic name of the object type A list of tokens that can be used in the command buffer A list of toke
GETVERSION Command ORSERV Commands and Responses GETVERSION Command The GETVERSION command returns the ORSERV server version in the ZSPI-TKNSERVER-VERSION token (in the SPI header) and the server ID string in the ZSPITKN-SERVER-BANNER token. Command ZORS-CMD-GETVERSION Object Type ZORS-OBJ-NULL Tokens in the Command Buffer ZSPI-TKN-COMMENT token-type ZSPI-TYP-STRING. Tokens in the Response Buffer ZSPI-TKN-SERVER-BANNER token-type ZSPI-TYP-CHAR50. ZSPI-TKN-RETCODE token-type ZSPI-TYP-RETCODE.
ORSERV Commands and Responses Tokens in the Response Buffer release-date is the ORSERV release date. An example is 01APR01. compilation-date is the ORSERV compilation date. An example is 01APR01. ZSPI-TKN-RETCODE is the standard SPI return token returned in the response buffer by all Compaq subsystems. ZSPI-TKN-RETCODE contains zero if the command was successful, or an error number if an error or warning occurred. Note.
ONLINERELOAD Command ORSERV Commands and Responses ONLINERELOAD Command Command ZORS-CMD-ONLINERELOAD Object Type ZORS-OBJ-FILE Tokens in the Command Buffer ZORS-TKN-FILE ZORS-TKN-VOLUME token-type ZSPI-TYP-FNAME. token-type ZSPI-TYP-CHAR8. ZORS-MAP-PAR-ONLINERELOAD def ZORS-DDL-PAR-ONLINERELOAD. 02 ZNEW type ZSPI-DDL-BOOLEAN. 02 ZDUMP type ZSPI-DDL-BOOLEAN. 02 ZRATE type ZSPI-DDL-INT. 02 ZMIN-DSLACK type ZSPI-DDL-INT. 02 ZMAX-DSLACK type ZSPI-DDL-INT. 02 ZMIN-ISLACK type ZSPI-DDL-INT.
ORSERV Commands and Responses • Tokens in the Command Buffer It can be unaudited. Reloading an unadited file might take longer than reloading an audited file. Tokens in the Command Buffer ZORS-TKN-FILE is a required token that specifies a key-sequenced target file or SQL object for the reload operation. Only one of these tokens is allowed per command. The target file must be a single file or SQL object in the Guardian internal file-name format. A file set or file-set list is not allowed.
ORSERV Commands and Responses Tokens in the Command Buffer To minimize any performance degradation to your system caused by the reload operation, set the ZRATE field. For example, if ZRATE is 10, ORSERV uses 10 percent of its execution time to perform the reload and delays 90 percent of its time. This lets system resources (such as processor time and memory) be available for use by other applications. ZMIN-DSLACK specifies the minimum percentage of slack space to be left in data blocks.
ORSERV Commands and Responses Tokens in the Response Buffer Zero ORSERV does not enclose the response in a data list. Nonzero ORSERV encloses the response in a data list. ZSPI-TKN-RESPONSE-TYPE and ZSPI-TKN-ALLOW-TYP are standard SPI response-control tokens. Although you can set these tokens, they have no effect on the execution of the command. ZSPI-TKN-COMMENT is the standard SPI token that lets you include an 80-byte arbitrary comment in the command buffer.
ORSERV Commands and Responses Considerations ZSPI-TKN-ERRLIST is the standard SPI token that begins an error list. The error list ends with ZSPI-TKN-ENDLIST. Note. For more information about all ORSERV error numbers and their corresponding error lists, see Appendix C, ORSERV Error Messages. Considerations When using the ONLINERELOAD command, consider the audit records, the ZZRELOAD file, and slack values.
ORSERV Commands and Responses ° Example ZSPI-VAL-FALSE—ORSERV continues the reload operation from the point indicated in ZZRELOAD. 2. After ORSERV initiates the reload operation, it returns a response buffer to its requester. ORSERV then continues the reload operation and does not communicate with the requester. You can close ORSERV at this point. 3. ORSERV records any reload warnings or errors in the ZZRELOAD file. 4. After completing the reload operation, ORSERV stops itself.
ORSERV Commands and Responses Example Figure 5-1. Example of the ONLINERELOAD Command (page 2 of 3) rate, ! Percentage of execution time for reload min^dslack, ! Data slack minimum max^dslack, ! Data slack maximum min^islack, ! Index slack minimum max^islack, ! Index slack maximum deallocate; ! Deallocates extents beyond EOF ! --------------------------------------------------------BEGIN ! Global variables used are: ! STRUCT .buffer (ZORS^DDL^MSG^BUFFER^DEF); ! STRUCT .
ORSERV Commands and Responses Example Figure 5-1. Example of the ONLINERELOAD Command (page 3 of 3) BEGIN CALL SSNULL (onlinereload^par^def, params); IF $PARAM (new) THEN params.znew := new; IF $PARAM (rate) THEN params.zrate := rate; IF $PARAM (min^dslack) THEN params.zmin^dslack := min^dslack; IF $PARAM (max^dslack) THEN params.zmax^dslack := max^dslack; IF $PARAM (min^islack) THEN params.zmin^islack := min^islack; IF $PARAM (max^islack) THEN params.
STATUS Command ORSERV Commands and Responses STATUS Command After receiving a STATUS command, ORSERV reads the ZZRELOAD file to determine the status of the reload operation for the specified target file. If ORSERV cannot read the ZZRELOAD file, it returns an error to the requester. An ORSERV process accepts only one STATUS command. After returning the status in the response buffer, ORSERV stops itself.
ORSERV Commands and Responses Tokens in the Command Buffer Tokens in the Command Buffer ZORS-TKN-FILE is a required token that specifies the target file or SQL object for the STATUS command. Only one of these tokens is allowed per command. The target file must be a single file or SQL object in the Guardian internal file-name format. A file set or file-set list is not allowed. ZSPI-TKN-MAXRESP is the standard SPI token that specifies the number of responses that a subsystem returns in the response buffer.
ORSERV Commands and Responses Tokens in the Response Buffer ZORS-MAP-STATUS-RESPONSE is a structured token that specifies the status of the reload operation. Only one of these tokens is returned in a response buffer. The fields are as follows: ZSTATUS-AVAILABLE is a Boolean field with these values: ZSPI-VAL-TRUE The status information is available, and ORSERV returns meaningful values for the remaining fields.
ORSERV Commands and Responses Tokens in the Response Buffer ZPERCENT-DONE specifies the percentage of the reload operation that has completed—if the reload is still executing. ZERROR specifies the last error that occurred for the reload operation. ZERROR-FILE is the file on which the last error occurred. This file is either the ZZRELOAD file or the target file specified by ZORS-TKN-FILE.
ORSERV Commands and Responses Example ZSPI-TKN-RETCODE is the standard SPI return token that is returned in the response buffer by all Compaq subsystems. ZSPI-TKN-RETCODE contains zero if the command was successful or an error number if an error or warning occurred. Note. Table 4-4, Errors Returned by All ORSERV Commands, on page 4-21 shows the ZSPI-TKN-RETCODE values common to all ORSERV commands. ZSPI-TKN-ERRLIST is the standard SPI token that begins an error list.
ORSERV Commands and Responses Example Figure 5-2. Example of the STATUS Command (page 2 of 2) ORSERV^ssid, ZSPI^VAL^CMDHDR, ZORS^CMD^STATUS, ZORS^OBJ^FILE); IF error THEN CALL spi^proc^error^handler (error); ! --------------------------------------------------------! Put the file name parameter into the buffer.
SUSPEND Command ORSERV Commands and Responses SUSPEND Command ORSERV reads the ZZRELOAD file to determine the process ID of the ORSERV process performing the reload operation, then stops it. ORSERV records the timestamp when the process is stopped in the ZZRELOAD file. An ORSERV process accepts only one SUSPEND command. After stopping the process performing the reload operation (and returning the response buffer), ORSERV stops itself.
ORSERV Commands and Responses Tokens in the Response Buffer Zero ORSERV does not enclose the response in a data list. Nonzero ORSERV encloses the response in a data list. ZSPI-TKN-RESPONSE-TYPE and ZSPI-TKN-ALLOW-TYPE are standard SPI response-control tokens. Although you can set these tokens, they have no effect on the execution of the command. ZSPI-TKN-COMMENT is the standard SPI token that allows you to include an 80-byte arbitrary comment in the command buffer.
ORSERV Commands and Responses ° Example A procedure call (such as KEYPOSITION) when ORSERV tried to access the ZZRELOAD file. Note. Table 4-4, Errors Returned by All ORSERV Commands, on page 4-21 shows the ZSPI-TKN-RETCODE values common to all ORSERV commands. ZSPI-TKN-ERRLIST is the standard SPI token that begins an error list. The error list ends with ZSPI-TKN-ENDLIST. Note. For more information about all ORSERV error numbers and their corresponding error lists, see Appendix C, ORSERV Error Messages.
ORSERV Commands and Responses Example Figure 5-3. Example of the SUSPEND Command (page 2 of 2) error := SSINIT (buffer, ZORS^VAL^BUFLEN, ORSERV^ssid, ZSPI^VAL^CMDHDR, ZORS^CMD^SUSPEND, ZORS^OBJ^FILE); IF error THEN CALL spi^proc^error^handler (error); ! --------------------------------------------------------! Put the required file-name parameter into the buffer.
ORSERV Commands and Responses File Utility Program (FUP) Management Programming Manual—523322-001 5- 22 Example
A Management Application Example This listing output is an example of using the COBOL85 management application to communicate with FUP and execute the programmatic DUPLICATE command. Figure A-1. Management Application Example (page 1 of 8) *========================================================= * FUP DUPLICATE Program *========================================================= ?SYMBOLS, INSPECT ?SAVE STARTUP ?LIBRARY $SYSTEM.SYSTEM.COBOLLIB IDENTIFICATION DIVISION. PROGRAM-ID. FUP-COPY.
Management Application Example Figure A-1. Management Application Example (page 2 of 8) 01 01 01 01 01 COBOL-VAL-FALSE RETCODE EXTERNAL-NAME IN-EXTERNAL-NAME OUT-EXTERNAL-NAME PIC XX VALUE LOW-VALUES. NATIVE-2. PIC X(35). PIC X(35). PIC X(35). *========================================================= * Copy SPI definitions from ZSPICOB, ZFUPCOB and ZFILCOB. *========================================================= COPY ZSPI-DDL-FNAME OF "$SYSTEM.ZSPIDEF.
Management Application Example Figure A-1. Management Application Example (page 3 of 8) *========================================================= * Form the name to open FUP for SPI commands and assign * it to the #DYNAMIC file. STRING FUP-PROCESS-NAME ".#ZSPI" DELIMITED BY " " INTO FUP-SPI-NAME. ENTER "COBOLASSIGN" USING FUP-FILE FUP-SPI-NAME GIVING ERR. IF ERR NOT = 0 DISPLAY "COBOLASSIGN error: " ERR DISPLAY "Operation terminated." STOP RUN.
Management Application Example Figure A-1. Management Application Example (page 4 of 8) ENTER TAL "FNAMEEXPAND" USING USER-TYPED-FILENAME SOURCE-FILE DEFAULT-VOL GIVING LEN. IF LEN = 0 DISPLAY "Invalid file name. Try again." GO TO P100. *========================================================= * Ask the user for the destination file name and convert * the name to internal format. P200. DISPLAY "Enter the destination file name:". ACCEPT USER-TYPED-FILENAME.
Management Application Example Figure A-1. Management Application Example (page 5 of 8) P400. DISPLAY "Do you want to preserve the file owner?". ACCEPT Y-OR-N. ENTER TAL "SHIFTSTRING" USING Y-OR-N, 1, 0. EVALUATE Y-OR-N WHEN "Y" MOVE COBOL-VAL-TRUE TO ZPRESERVE-OWNER OF ZFUP-DDL-PAR-DUP WHEN "N" MOVE COBOL-VAL-FALSE TO ZPRESERVE-OWNER OF ZFUP-DDL-PAR-DUP WHEN " " CONTINUE WHEN OTHER DISPLAY "Enter Y or N (or blank for N)." GO TO P400 END-EVALUATE. P500. DISPLAY "Do you want to preserve the file security?".
Management Application Example Figure A-1. Management Application Example (page 6 of 8) *========================================================= * Build the command buffer. ENTER TAL "SSINIT" USING ZFUP-DDL-MSG-BUFFER ZFUP-VAL-BUFLEN ZFUP-VAL-SSID 0 ZFUP-CMD-DUPLICATE ZFUP-OBJ-FILE GIVING ERR. IF ERR NOT = 0 DISPLAY "SSINIT error: " ERR DISPLAY "Operation terminated." GO TO P700. ENTER TAL "SSPUT" USING ZFUP-DDL-MSG-BUFFER ZFUP-TKN-SOURCE-FILE SOURCE-FILE GIVING ERR.
Management Application Example Figure A-1. Management Application Example (page 7 of 8) *========================================================= * Get the return code token. Specify an index of 1 in * the SSGET call so that the order of tokens in the * buffer doesn’t matter. ENTER TAL “SSGET” USING ZFUP-DDL-MSG-BUFFER ZSPI-TKN-RETCODE RETCODE 1 GIVING ERR. IF ERR NOT = 0 DISPLAY “SSGET error on ZSPI-TKN-RETCODE: “ ERR DISPLAY “Operation terminated.” GO TO P700.
Management Application Example Figure A-1. Management Application Example (page 8 of 8) * * * token, which contains the file-system error number and the ZFIL-TKN-FILENAME token, which contains the name of the file that FUP was processing when the error occurred. DISPLAY-FILESYS-ERROR. ENTER TAL "SSGET" USING ZFUP-DDL-MSG-BUFFER ZSPI-TKN-ERRLIST OMITTED 1 GIVING ERR. IF ERR NOT = 0 DISPLAY "SSGET error on the FUP error list: " ERR DISPLAY "Operation terminated." GO TO P700.
B FUP Error Messages The FUP process returns an error list in the response buffer when it detects an error in the command syntax or during execution of a command. The error lists are organized by error number (ZFUP-ERR-value) in ascending order.
1: ZFUP-ERR-INV-COMMAND FUP Error Messages 1: ZFUP-ERR-INV-COMMAND An application sent an invalid programmatic command to FUP. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL. Tokens ZSPI-TKN-ERROR is the standard SPI error token, which consists of the FUP subsystem ID and the error number ZFUP-ERR-INV-COMMAND (1).
2: ZFUP-ERR-INV-OBJECT FUP Error Messages 2: ZFUP-ERR-INV-OBJECT An application specified an invalid object type for a FUP programmatic command. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
3: ZFUP-ERR-INVALID-TOKEN FUP Error Messages 3: ZFUP-ERR-INVALID-TOKEN An application specified an invalid token in the command buffer. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZSPI-TKN-PARM-ERR Z-TOKENCODE Z-INDEX Z-OFFSET ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-TOKENCODE. type ZSPI-DDL-UINT. type ZSPI-DDL-UINT. token-type ZSPI-TYP-SSCTL.
4: ZFUP-ERR-MISS-TOKEN FUP Error Messages 4: ZFUP-ERR-MISS-TOKEN An application omitted a required token from the command buffer. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZSPI-TKN-PARM-ERR Z-TOKENCODE Z-INDEX Z-OFFSET ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-TOKENCODE. type ZSPI-DDL-UINT. type ZSPI-DDL-UINT. token-type ZSPI-TYP-SSCTL.
5: ZFUP-ERR-MISS-FIELD FUP Error Messages 5: ZFUP-ERR-MISS-FIELD An application failed to set a required field of a structure to a specific value, and the field has a null value. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZSPI-TKN-PARM-ERR Z-TOKENCODE Z-INDEX Z-OFFSET ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-TOKENCODE. type ZSPI-DDL-UINT. type ZSPI-DDL-UINT. token-type ZSPI-TYP-SSCTL.
6: ZFUP-ERR-EXTRA-TOKEN FUP Error Messages 6: ZFUP-ERR-EXTRA-TOKEN An application specified an extra token in the command buffer. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZSPI-TKN-PARM-ERR Z-TOKENCODE Z-INDEX Z-OFFSET ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-TOKENCODE. type ZSPI-DDL-UINT. type ZSPI-DDL-UINT. token-type ZSPI-TYP-SSCTL.
7: ZFUP-ERR-INV-VALUE FUP Error Messages 7: ZFUP-ERR-INV-VALUE An application set a token or field within a token to an invalid value. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZSPI-TKN-PARM-ERR Z-TOKENCODE Z-INDEX Z-OFFSET ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-TOKENCODE. type ZSPI-DDL-UINT. type ZSPI-DDL-UINT. token-type ZSPI-TYP-SSCTL.
8: ZFUP-ERR-INV-CONTEXT FUP Error Messages 8: ZFUP-ERR-INV-CONTEXT An application specified an invalid context token in the command buffer. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
9: ZFUP-ERR-INV-TEMPLATE FUP Error Messages 9: ZFUP-ERR-INV-TEMPLATE An application specified an invalid template name for a file set. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZSPI-TKN-PARM-ERR Z-TOKENCODE Z-INDEX Z-OFFSET ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-TOKENCODE. type ZSPI-DDL-UINT. type ZSPI-DDL-UINT. token-type ZSPI-TYP-SSCTL.
10: ZFUP-ERR-LONG-COMMAND FUP Error Messages 10: ZFUP-ERR-LONG-COMMAND An application specified a command that was too long for the buffer. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. token-type ZSPI-TYP-SSCTL. Tokens ZSPI-TKN-ERROR is the standard SPI error token, which consists of the FUP subsystem ID and the error number ZFUP-ERR-LONG-COMMAND (10). This token is always in the error list.
12: ZFUP-ERR-WRONG-SERVER FUP Error Messages 12: ZFUP-ERR-WRONG-SERVER An application specified a command that requires a newer version of the FUP server. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. token-type ZSPI-TYP-SSCTL. Tokens ZSPI-TKN-ERROR is the standard SPI error token, which consists of the FUP subsystem ID and the error number ZFUP-ERR-WRONG-SERVER (12). This token is always in the error list.
14: ZFUP-ERR-NO-MEM FUP Error Messages 14: ZFUP-ERR-NO-MEM FUP ran out of internal memory space while trying to execute the command. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL. Tokens ZSPI-TKN-ERROR is the standard SPI error token, which consists of the FUP subsystem ID and the error number ZFUP-ERR-NO-MEM (14).
FUP Error Messages 14: ZFUP-ERR-NO-MEM If local operation procedures require contacting the Global Customer Support Center (GCSC), supply your system number and the numbers and versions of related products.
FUP Error Messages 15: ZFUP-ERR-EDITREAD 15: ZFUP-ERR-EDITREAD A command failed with an error from the EDITREAD or EDITREADINIT procedure. ZSPI-TKN-ERRLIST token-type ZSPI-TYP-LIST. ZSPI-TKN-ERROR token-type ZSPI-TYP-ERROR. ZFUP-MAP-CMD-ERROR ZNAME type ZSPI-DDL-FNAME. ZCOMMAND type ZSPI-DDL-INT. ZOBJECT type ZSPI-DDL-INT. ZSPI-TKN-ERRLIST token-type ZSPI-TYP-LIST. Error list owned by ZSPI-SSN-ZGP1 ZSPI-TKN-ENDLIST token-type ZSPI-TYP-SSCTL. ZSPI-TKN-ENDLIST token-type ZSPI-TYP-SSCTL.
FUP Error Messages 16: ZFUP-ERR-SORT 16: ZFUP-ERR-SORT The command (LOAD or LOADALTFILE) failed with an error from the FASTSORT utility. ZSPI-TKN-ERRLIST token-type ZSPI-TYP-LIST. ZSPI-TKN-ERROR token-type ZSPI-TYP-ERROR. ZFUP-MAP-CMD-ERROR ZNAME type ZSPI-DDL-FNAME. ZCOMMAND type ZSPI-DDL-INT. ZOBJECT type ZSPI-DDL-INT. ZSPI-TKN-ERRLIST token-type ZSPI-TYP-LIST. Error list owned by ZSPI-SSN-ZSRT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-SSCTL. ZSPI-TKN-ENDLIST token-type ZSPI-TYP-SSCTL.
FUP Error Messages 17: ZFUP-ERR-FILESYS 17: ZFUP-ERR-FILESYS The command failed with a Guardian file-system error. ZSPI-TKN-ERRLIST token-type ZSPI-TYP-LIST. ZSPI-TKN-ERROR token-type ZSPI-TYP-ERROR. ZFUP-MAP-CMD-ERROR ZNAME type ZSPI-DDL-FNAME. ZCOMMAND type ZSPI-DDL-INT. ZOBJECT type ZSPI-DDL-INT. ZSPI-TKN-ERRLIST token-type ZSPI-TYP-LIST. Error list owned by ZSPI-SSN-ZFIL ZSPI-TKN-ENDLIST token-type ZSPI-TYP-SSCTL. ZSPI-TKN-ENDLIST token-type ZSPI-TYP-SSCTL.
FUP Error Messages 18: ZFUP-ERR-GUARD 18: ZFUP-ERR-GUARD The command failed with a NonStop Kernel error. ZSPI-TKN-ERRLIST token-type ZSPI-TYP-LIST. ZSPI-TKN-ERROR token-type ZSPI-TYP-ERROR. ZFUP-MAP-CMD-ERROR ZNAME type ZSPI-DDL-FNAME. ZCOMMAND type ZSPI-DDL-INT. ZOBJECT type ZSPI-DDL-INT. ZSPI-TKN-ERRLIST token-type ZSPI-TYP-LIST. Error list owned by ZSPI-SSN-ZGRD ZSPI-TKN-ENDLIST token-type ZSPI-TYP-SSCTL. ZSPI-TKN-ENDLIST token-type ZSPI-TYP-SSCTL.
FUP Error Messages 19: ZFUP-ERR-SPI 19: ZFUP-ERR-SPI The command failed with a Subsystem Programmatic Interface (SPI) error. ZSPI-TKN-ERRLIST token-type ZSPI-TYP-LIST. ZSPI-TKN-ERROR token-type ZSPI-TYP-ERROR. ZSPI-TKN-ERRLIST token-type ZSPI-TYP-LIST. Error list owned by ZSPI-SSN-ZSPI ZSPI-TKN-ENDLIST token-type ZSPI-TYP-SSCTL. ZSPI-TKN-ENDLIST token-type ZSPI-TYP-SSCTL. Tokens ZSPI-TKN-ERROR is the standard SPI error token, which consists of the FUP subsystem ID and the error number ZFUP-ERR-SPI (19).
20: ZFUP-ERR-PE FUP Error Messages 20: ZFUP-ERR-PE An internal programming error occurred. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZFUP-TKN-PE-NUM ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-INT token-type ZSPI-TYP-SSCTL. Tokens ZSPI-TKN-ERROR is the standard SPI error token, which consists of the FUP subsystem ID and the error number ZFUP-ERR-PE (20).
FUP Error Messages 20: ZFUP-ERR-PE Recommended Action FUP ends abnormally. An internal software error might have occurred. Enter the command again with the INSPECT SAVEABEND RUN option to produce a saveabend file.
21: ZFUP-ERR-BAD-KEY FUP Error Messages 21: ZFUP-ERR-BAD-KEY An application specified a LOADALTFILE command to load an existing alternate-key file, but the file had invalid alternate-key parameters. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZFUP-TKN-ALTFILE-NUM ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-INT. token-type ZSPI-TYP-SSCTL.
22: ZFUP-ERR-BAD-PARTS FUP Error Messages 22: ZFUP-ERR-BAD-PARTS An application specified a command with invalid partition parameters. FUP found the file that it expected to be the primary file, but the file was either not a partitioned file or was the primary partition for the destination file. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT.
23: ZFUP-ERR-BAD-TAPELABEL FUP Error Messages 23: ZFUP-ERR-BAD-TAPELABEL An application specified a command with a TAPE DEFINE that does not match the actual tape label. (The tape label might be invalid.) The attempt to open the labeledtape file failed with file-system error 196. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT.
24: ZFUP-ERR-BAD-VAR-BLOCKLEN FUP Error Messages 24: ZFUP-ERR-BAD-VAR-BLOCKLEN An application specified an invalid block length for a file with variable-length record blocking. An attempt to load the file with variable-length records failed because the length of a block was one or zero bytes. This error can occur if the file to be loaded was filled without specifying the VAROUT option for the FUP COPY command. Also, the data in the file might be corrupt.
25: ZFUP-ERR-BAD-VAR-RECLEN FUP Error Messages 25: ZFUP-ERR-BAD-VAR-RECLEN An application specified an invalid variable record length for a file. An attempt to load the file failed because the record length specified for a variable-length record was invalid (for example, the record length was a negative number). This error can occur if the file to be loaded was filled without specifying the VAROUT option of the FUP COPY command. Also, data in the file might be corrupt.
26: ZFUP-ERR-BLOCKIN-CONFLICT FUP Error Messages 26: ZFUP-ERR-BLOCKIN-CONFLICT An application specified a TAPE DEFINE for the source file, but the TAPE DEFINE has a value for BLOCKLEN that conflicts with ZBLOCK-SIZE. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
27: ZFUP-ERR-BLOCKLEN-BIG FUP Error Messages 27: ZFUP-ERR-BLOCKLEN-BIG An application specified a TAPE DEFINE for the source file, but the TAPE DEFINE BLOCKLEN value is too large (greater than 32,767—the largest block size that FUP can process). ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZFUP-TKN-BLOCKLEN ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-INT2.
28: ZFUP-ERR-DEFINE-CONFLICT FUP Error Messages 28: ZFUP-ERR-DEFINE-CONFLICT FUP attempted to alter a TAPE DEFINE BLOCKLEN or RECLEN value to match ZBLOCK-SIZE or ZRECORD-SIZE, but the FUP value is not a valid TAPE DEFINE value. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
30: ZFUP-ERR-AKNOUP FUP Error Messages 30: ZFUP-ERR-AKNOUP FUP did not change the alternate-key files. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL. Tokens ZSPI-TKN-ERROR is the standard SPI error token, which consists of the FUP subsystem ID and the error number ZFUP-ERR-AKNOUP (30).
32: ZFUP-ERR-DUP-SEC-PART FUP Error Messages 32: ZFUP-ERR-DUP-SEC-PART An application attempted to rename multiple partitions to the same volume name in a DUPLICATE command rename options. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
33: ZFUP-ERR-EBCDICIN-CONFLICT FUP Error Messages 33: ZFUP-ERR-EBCDICIN-CONFLICT An application specified a TAPE DEFINE for the source file, but the TAPE DEFINE value for EBCDIC conflicts with ZEBCDIC; for example, if the EBCDIC value in the TAPE DEFINE was OFF, and ZEBCDIC was set to ZSPI-VAL-TRUE. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT.
34: ZFUP-ERR-SEC-PART FUP Error Messages 34: ZFUP-ERR-SEC-PART An application specified a secondary partition name in a context where secondary partitions are not allowed. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
35: ZFUP-ERR-EMPTY-SOURCE FUP Error Messages 35: ZFUP-ERR-EMPTY-SOURCE An application specified an empty source file (zero records) for a LOAD command but did not set ZEMPTYOK to ZSPI-VAL-TRUE. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
36: ZFUP-ERR-ENSURE-PARTS FUP Error Messages 36: ZFUP-ERR-ENSURE-PARTS An application attempted to duplicate a partition with a new extent size with ZPART-ONLY set to ZSPI-VAL-TRUE. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
37: ZFUP-ERR-FILE-KEY-INCOM FUP Error Messages 37: ZFUP-ERR-FILE-KEY-INCOM The alternate-key file is incompatible with the alternate keys. The existing alternate-key file characteristics contradict the keys defined in the primary-key file. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZFUP-TKN-ALTFILE-NUM ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-INT.
38: ZFUP-ERR-IGN-COMPACT FUP Error Messages 38: ZFUP-ERR-IGN-COMPACT An application attempted to LOAD a nonrelative file with ZCOMPACT set to ZSPI-VAL-TRUE. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
40: ZFUP-ERR-IGN-RENAME-OPTS FUP Error Messages 40: ZFUP-ERR-IGN-RENAME-OPTS An application attempted to duplicate a file with ZDEST set to ZFUP-VAL-OLD with either the rename or extent size option specified. These options are mutually exclusive. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
41: ZFUP-ERR-INCOMPAT-FILE FUP Error Messages 41: ZFUP-ERR-INCOMPAT-FILE An application specified a DUPLICATE command with incompatible source and destination files. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
42: ZFUP-ERR-INCON-PARTS FUP Error Messages 42: ZFUP-ERR-INCON-PARTS The file attributes of the individual partitions of a partitioned file are inconsistent with each other. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
43: ZFUP-ERR-INV-FTYPE FUP Error Messages 43: ZFUP-ERR-INV-FTYPE An application attempted to load an unstructured file, which is not allowed for this file type. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
44: ZFUP-ERR-MISS-ALTFILE FUP Error Messages 44: ZFUP-ERR-MISS-ALTFILE An application attempted to rename a nonexistent alternate-key file in a DUPLICATE command (the source file does not have the specified alternate-key file). ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZFUP-TKN-ALTFILE-NUM ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-INT. token-type ZSPI-TYP-SSCTL.
45: ZFUP-ERR-MISS-PART FUP Error Messages 45: ZFUP-ERR-MISS-PART An application attempted to rename a nonexistent partition file in a DUPLICATE command. (The source file does not have the specified partition.) ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZFUP-TKN-PART-NO ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-INT. token-type ZSPI-TYP-SSCTL.
47: ZFUP-ERR-NO-ALT-FILE FUP Error Messages 47: ZFUP-ERR-NO-ALT-FILE An application specified an alternate-key file that does not exist in a LOADALTFILE command. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZFUP-TKN-ALTFILE-NUM ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-INT. token-type ZSPI-TYP-SSCTL.
48: ZFUP-ERR-NO-EXTSIZE FUP Error Messages 48: ZFUP-ERR-NO-EXTSIZE An application attempted to duplicate a relative or entry-sequenced file with a new extent size and ZPART-ONLY set to ZSPI-VAL-TRUE. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
49: ZFUP-ERR-NO-ZSVR FUP Error Messages 49: ZFUP-ERR-NO-ZSVR The labeled-tape server ($ZSVR) is not available. An attempt to open a tape file failed with file-system error 195. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
50: ZFUP-ERR-NOT-ON-PARTF FUP Error Messages 50: ZFUP-ERR-NOT-ON-PARTF An application attempted to duplicate a partitioned file with the ZDEST-OPTION set to ZFUP-VAL-OLD. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
51: ZFUP-ERR-OP-REJECT FUP Error Messages 51: ZFUP-ERR-OP-REJECT An operator rejected a request to mount a tape, and the attempt to open the tape file failed with a file-system error 194. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
52: ZFUP-ERR-PNAME-BAD FUP Error Messages 52: ZFUP-ERR-PNAME-BAD A partition name in the file label is missing a back-slash (\) or dollar sign ($). ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
53: ZFUP-ERR-PNAME-NOT-NET FUP Error Messages 53: ZFUP-ERR-PNAME-NOT-NET A partition name in the file label cannot be transformed into the network form because the name is seven characters long. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
54: ZFUP-ERR-MUST-REARRANGE-DATA FUP Error Messages 54: ZFUP-ERR-MUST-REARRANGE-DATA An application attempted to duplicate a partition with ZPART-ONLY set to ZSPIVAL-TRUE. FUP determined that the partition data would be reshuffled among the various partitions. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
55: ZFUP-ERR-RECIN-CONFLICT FUP Error Messages 55: ZFUP-ERR-RECIN-CONFLICT An application specified a TAPE DEFINE for the source file, but the TAPE DEFINE RECLEN value conflicts with ZRECORD-SIZE. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
56: ZFUP-ERR-RECLEN-BIG FUP Error Messages 56: ZFUP-ERR-RECLEN-BIG An application specified a TAPE DEFINE for the source file, but the TAPE DEFINE RECLEN value is too large (greater than 4096). ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZFUP-TKN-RECLEN ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-INT2. token-type ZSPI-TYP-SSCTL.
57: ZFUP-ERR-PART-KEY-LONG FUP Error Messages 57: ZFUP-ERR-PART-KEY-LONG A partial key is too long (greater than 255 bytes). ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL. Tokens ZSPI-TKN-ERROR is the standard SPI error token, which consists of the FUP subsystem ID and the error number ZFUP-ERR-PART-KEY-LONG (57).
58: ZFUP-ERR-RELOAD-ALTFILES FUP Error Messages 58: ZFUP-ERR-RELOAD-ALTFILES An application duplicated a relative or entry-sequenced file from one volume type to another volume type, and the record positions in the alternate-key files have changed. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
59: ZFUP-ERR-SHORT-KEYS FUP Error Messages 59: ZFUP-ERR-SHORT-KEYS An application specified the LOADALTFILE command, but a number of records contain incomplete alternate-key fields. FUP does not generate them in the destination file. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZFUP-TKN-ALTFILE-NUM ZFUP-TKN-REC-COUNT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-INT.
60: ZFUP-ERR-SOURCEDATE-NOT-SAVED FUP Error Messages 60: ZFUP-ERR-SOURCEDATE-NOT-SAVED An application executed a DUPLICATE command, but FUP did not preserve the source date for the destination file. An attempt was made to duplicate a file to a remote system that is running an operating system older than B00. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT.
62: ZFUP-ERR-TRUNC FUP Error Messages 62: ZFUP-ERR-TRUNC FUP is truncating the input records of the current file. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL. Tokens ZSPI-TKN-ERROR is the standard SPI error token, which consists of the FUP subsystem ID and the error number ZFUP-ERR-TRUNC (62).
63: ZFUP-ERR-UNSTR-NO-EXTSIZE FUP Error Messages 63: ZFUP-ERR-UNSTR-NO-EXTSIZE An application specified the extent size when converting partitioned unstructured files, but this is not allowed. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
64: ZFUP-ERR-USE-EXT-N-READ FUP Error Messages 64: ZFUP-ERR-USE-EXT-N-READ An application specified a TAPE DEFINE for an input file (read access) with the USE attribute set to EXTEND. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
65: ZFUP-ERR-USE-OUT-N-READ FUP Error Messages 65: ZFUP-ERR-USE-OUT-N-READ An application specified a TAPE DEFINE for an input file (read access) with the USE attribute set to OUT. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
66: ZFUP-ERR-VAR-TRUNC FUP Error Messages 66: ZFUP-ERR-VAR-TRUNC An application specified a LOAD command with ZVAR-REC set to ZSPI-VAL-TRUE, and FUP truncated the last variable-length record in the block. This record extended beyond the end of the block (according to the record length at the beginning of the record). ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT.
67: ZFUP-ERR-VOL-NOT-FOUND FUP Error Messages 67: ZFUP-ERR-VOL-NOT-FOUND A partition or alternate-key file name points to a nonexistent volume. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
68: ZFUP-ERR-AUDITED-FILE FUP Error Messages 68: ZFUP-ERR-AUDITED-FILE An application attempted a CHECKSUM command on an audited file. This is not allowed. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
69: ZFUP-ERR-SKIPIN-CONFLICT FUP Error Messages 69: ZFUP-ERR-SKIPIN-CONFLICT An application attempted to use the ZSKIP option when the source file for the operation was a TAPE DEFINE (with the LABELS attribute set to label processing). ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
70: ZFUP-ERR-REELS-CONFLICT FUP Error Messages 70: ZFUP-ERR-REELS-CONFLICT An application attempted to use the ZREELS option when the source file for the operation was a TAPE DEFINE (with the LABELS attribute set to label processing). ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
71: ZFUP-ERR-CORRUPT-FILE FUP Error Messages 71: ZFUP-ERR-CORRUPT-FILE An application executed a DUPLICATE command, but FUP determined that a file is corrupt. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
72: ZFUP-ERR-BROKEN-FILE FUP Error Messages 72: ZFUP-ERR-BROKEN-FILE An application executed a DUPLICATE command, but FUP determined that a file is broken. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
73: ZFUP-ERR-SAFEGUARD-LOST FUP Error Messages 73: ZFUP-ERR-SAFEGUARD-LOST An application executed a DUPLICATE command for a file with Safeguard protection, but the new file does not have Safeguard protection. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
74: ZFUP-ERR-CONVERT-CORRUPT FUP Error Messages 74: ZFUP-ERR-CONVERT-CORRUPT An application attempted to duplicate a corrupt file between different disk process types (DP1 or DP2), but this operation is not allowed. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
75: ZFUP-ERR-NO-DEFINE FUP Error Messages 75: ZFUP-ERR-NO-DEFINE An application specified a TAPE DEFINE for the source file, but FUP could not find the DEFINE. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
76: ZFUP-ERR-KEPT FUP Error Messages 76: ZFUP-ERR-KEPT An application executed a DUPLICATE command with ZDEST-OPTION set to ZFUP-VAL-KEEP. FUP did not duplicate the file because the destination file name matched the source file name. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
77: ZFUP-ERR-ALTKEY-LEN0 FUP Error Messages 77: ZFUP-ERR-ALTKEY-LEN0 An application specified an alternate key with an invalid length of zero (0). ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
78: ZFUP-ERR-ALTKEY-LONG FUP Error Messages 78: ZFUP-ERR-ALTKEY-LONG An alternate key extends beyond the length of the record. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL. Tokens ZSPI-TKN-ERROR is the standard SPI error token, which consists of the FUP subsystem ID and the error number ZFUP-ERR-ALTKEY-LONG (78).
79: ZFUP-ERR-ALTFILE-PRIKEY-LONG FUP Error Messages 79: ZFUP-ERR-ALTFILE-PRIKEY-LONG A primary key is too long for an alternate-key file. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
80: ZFUP-ERR-UNIQUE-N-NON-UNIQUE FUP Error Messages 80: ZFUP-ERR-UNIQUE-N-NON-UNIQUE Both unique and nonunique keys were specified in an alternate-key file. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
81: ZFUP-ERR-VARYING-UNIQUE-ALT-KEYS FUP Error Messages 81: ZFUP-ERR-VARYING-UNIQUE-ALT-KEYS Unique keys were not the same length in the same alternate-key file. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
82: ZFUP-ERR-KEYLEN-ZERO FUP Error Messages 82: ZFUP-ERR-KEYLEN-ZERO A primary key length is zero, which is invalid. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL. Tokens ZSPI-TKN-ERROR is the standard SPI error token, which consists of the FUP subsystem ID and the error number ZFUP-ERR-KEYLEN-ZERO (82).
83: ZFUP-ERR-PART-KEY-MISSING FUP Error Messages 83: ZFUP-ERR-PART-KEY-MISSING A partial key for a key-sequenced file partition is missing. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
84: ZFUP-ERR-ALT-FILE-MISSING FUP Error Messages 84: ZFUP-ERR-ALT-FILE-MISSING An alternate key does not have a corresponding alternate-key file. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
85: ZFUP-ERR-ALT-KEY-MISSING FUP Error Messages 85: ZFUP-ERR-ALT-KEY-MISSING An alternate-key file is missing a corresponding alternate key. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
86: ZFUP-ERR-NOT-ON-OPTICAL FUP Error Messages 86: ZFUP-ERR-NOT-ON-OPTICAL An application specified an optical-disk file in a FUP command (such as LOAD or CHECKSUM) that does not support optical disks. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
89: ZFUP-ERR-MUST-SQL-RECOMPILE FUP Error Messages 89: ZFUP-ERR-MUST-SQL-RECOMPILE A DUP command duplicated a file sensitive to SQL. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
90: ZFUP-ERR-NOT-ON-SQL-OBJECT FUP Error Messages 90: ZFUP-ERR-NOT-ON-SQL-OBJECT An application specified an SQL object in a FUP command that does not allow SQL objects. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
91: ZFUP-ERR-ALT-NOT-SQL FUP Error Messages 91: ZFUP-ERR-ALT-NOT-SQL An application specified a LOADALTFILE command with an SQL object as an alternate-key file. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
92: ZFUP-ERR-NOT-ON-VIEW FUP Error Messages 92: ZFUP-ERR-NOT-ON-VIEW An application specified an SQL shorthand view or protection view in a CHECKSUM command. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
93: ZFUP-ERR-OUT-IS-SQL FUP Error Messages 93: ZFUP-ERR-OUT-IS-SQL An application specified an SQL object as an OUT (or list) file in the FUP startup message. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
94: ZFUP-ERR-PART-IS-SQL FUP Error Messages 94: ZFUP-ERR-PART-IS-SQL An application specified a DUPLICATE command for a partitioned file (with ZPART-ONLY set to ZSPI-VAL-FALSE), and one of the partitions was an SQL object. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
100: ZFUP-ERR-REST-TOOMANY-FILES FUP Error Messages 100: ZFUP-ERR-REST-TOOMANY-FILES An application specified more than one source file for the ZFUP-TKN-SOURCE-FILE token for a DUPLICATE command (with the restartable option specified). ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
101: ZFUP-ERR-OPTICAL-RESTART-FILE FUP Error Messages 101: ZFUP-ERR-OPTICAL-RESTART-FILE An application specified a restart file that is located on an optical disk volume for a DUPLICATE command (with the restartable option specified)—or for a RESTART command. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
103: ZFUP-ERR-SRC-FILE-CHANGED FUP Error Messages 103: ZFUP-ERR-SRC-FILE-CHANGED An application attempted a RESTART command, but the source file was modified since the original DUPLICATE command was issued. FUP checks the time of the last modification in the file label to determine if the source file was modified. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT.
104: ZFUP-ERR-DEST-NOT-CORRUPT FUP Error Messages 104: ZFUP-ERR-DEST-NOT-CORRUPT An application attempted a RESTART command, but the destination file is not corrupt. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
105: ZFUP-ERR-REST-INFO-INVALID FUP Error Messages 105: ZFUP-ERR-REST-INFO-INVALID An application attempted a RESTART command, but the RESTART file contains invalid information. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
106: ZFUP-ERR-DP-CHANGED FUP Error Messages 106: ZFUP-ERR-DP-CHANGED An application attempted a RESTART command, but the disk-process format of the volume containing the source or destination file was changed since the original DUPLICATE operation was executed. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
107: ZFUP-ERR-NOT-REST-FILECODE FUP Error Messages 107: ZFUP-ERR-NOT-REST-FILECODE An application attempted a RESTART command, but the restart file does not have a file code of 855. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
112: ZFUP-ERR-COMPACT FUP Error Messages 112: ZFUP-ERR-COMPACT An empty RELATIVE file was found and not transferred during a FUP LOAD operation with ZCOMPACT set to ZSPI-VAL-TRUE. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZFUP-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
C ORSERV Error Messages The ORSERV process returns an error list in the response buffer when an error is detected in the command syntax or during execution of a command. The error lists are organized by error number (ZORS-ERR- value) in ascending order.
1: ZORS-ERR-INV-COMMAND ORSERV Error Messages 1: ZORS-ERR-INV-COMMAND An application sent an invalid command to ORSERV. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZORS-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL. Tokens ZSPI-TKN-ERROR is the standard SPI error token, which consists of the ORSERV subsystem ID and the error number ZORS-ERR-INV-COMMAND (1).
2: ZORS-ERR-INV-OBJECT ORSERV Error Messages 2: ZORS-ERR-INV-OBJECT An application specified an invalid object type for an ORSERV command. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZORS-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
3: ZORS-ERR-INVALID-TOKEN ORSERV Error Messages 3: ZORS-ERR-INVALID-TOKEN An application specified an invalid token in an ORSERV command. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZSPI-TKN-PARM-ERR Z-TOKENCODE Z-INDEX Z-OFFSET ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-TOKENCODE. type ZSPI-DDL-UINT. type ZSPI-DDL-UINT. token-type ZSPI-TYP-SSCTL.
4: ZORS-ERR-MISS-TOKEN ORSERV Error Messages 4: ZORS-ERR-MISS-TOKEN An application omitted a required token from an ORSERV command. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZSPI-TKN-PARM-ERR Z-TOKENCODE Z-INDEX Z-OFFSET ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-TOKENCODE. type ZSPI-DDL-UINT. type ZSPI-DDL-UINT. token-type ZSPI-TYP-SSCTL.
5: ZORS-ERR-MISS-FIELD ORSERV Error Messages 5: ZORS-ERR-MISS-FIELD A required field of a structured token has a null value. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZSPI-TKN-PARM-ERR Z-TOKENCODE Z-INDEX Z-OFFSET ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-TOKENCODE. type ZSPI-DDL-UINT. type ZSPI-DDL-UINT. token-type ZSPI-TYP-SSCTL. Tokens ZSPI-TKN-ERROR is the standard SPI error token, which consists of the ORSERV subsystem ID and the error number ZORS-ERR-MISS-FIELD (5).
6: ZORS-ERR-EXTRA-TOKEN ORSERV Error Messages 6: ZORS-ERR-EXTRA-TOKEN An application specified an extra token in an ORSERV command buffer. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZSPI-TKN-PARM-ERR Z-TOKENCODE Z-INDEX Z-OFFSET ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-TOKENCODE. type ZSPI-DDL-UINT. type ZSPI-DDL-UINT. token-type ZSPI-TYP-SSCTL.
7: ZORS-ERR-INV-VALUE ORSERV Error Messages 7: ZORS-ERR-INV-VALUE An application specified an invalid value for a token or for a field within a token. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZSPI-TKN-PARM-ERR Z-TOKENCODE Z-INDEX Z-OFFSET ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-TOKENCODE. type ZSPI-DDL-UINT. type ZSPI-DDL-UINT. token-type ZSPI-TYP-SSCTL.
8: ZORS-ERR-LONG-COMMAND ORSERV Error Messages 8: ZORS-ERR-LONG-COMMAND An application specified an ORSERV command that is too long for the command buffer. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. token-type ZSPI-TYP-SSCTL. Tokens ZSPI-TKN-ERROR is the standard SPI error token, which consists of the ORSERV subsystem ID and the error number ZORS-ERR-LONG-COMMAND (8). This token is always in the error list.
10: ZORS-ERR-WRONG-SERVER ORSERV Error Messages 10: ZORS-ERR-WRONG-SERVER An application specified an ORSERV command that requires a newer version of the ORSERV server. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. token-type ZSPI-TYP-SSCTL. Tokens ZSPI-TKN-ERROR is the standard SPI error token, which consists of the ORSERV subsystem ID and the error number ZORS-ERR-WRONG-SERVER (10). This token is always in the error list.
11: ZORS-ERR-SPI ORSERV Error Messages 11: ZORS-ERR-SPI The command failed with a Subsystem Programmatic Interface (SPI) error. ZSPI-TKN-ERRLIST token-type ZSPI-TKN-ERROR token-type ZSPI-TKN-ERRLIST token-type Error list with error returned by ZSPI-TKN-ENDLIST token-type ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-LIST. ZSPI-SSN-ZSPI ZSPI-TYP-SSCTL. ZSPI-TYP-SSCTL.
12: ZORS-ERR-PE ORSERV Error Messages 12: ZORS-ERR-PE An internal programming error occurred. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZORS-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZORS-TKN-PE-NUM ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-INT token-type ZSPI-TYP-SSCTL. Tokens ZSPI-TKN-ERROR is the standard SPI error token, which consists of the ORSERV subsystem ID and the error number ZORS-ERR-PE (12).
ORSERV Error Messages 13: ZORS-ERR-FILESYS 13: ZORS-ERR-FILESYS The ORSERV command failed with a Guardian file-system error. ZSPI-TKN-ERRLIST token-type ZSPI-TYP-LIST. ZSPI-TKN-ERROR token-type ZSPI-TYP-ERROR. ZORS-MAP-CMD-ERROR ZNAME type ZSPI-DDL-FNAME. ZCOMMAND type ZSPI-DDL-INT. ZOBJECT type ZSPI-DDL-INT. ZSPI-TKN-ERRLIST token-type ZSPI-TYP-LIST. Error list with error returned by ZSPI-SSN-ZFIL ZSPI-TKN-ENDLIST token-type ZSPI-TYP-SSCTL. ZSPI-TKN-ENDLIST token-type ZSPI-TYP-SSCTL.
ORSERV Error Messages 14: ZORS-ERR-GUARD 14: ZORS-ERR-GUARD The command failed with a NonStop Kernel error. ZSPI-TKN-ERRLIST token-type ZSPI-TYP-LIST. ZSPI-TKN-ERROR token-type ZSPI-TYP-ERROR. ZORS-MAP-CMD-ERROR ZNAME type ZSPI-DDL-FNAME. ZCOMMAND type ZSPI-DDL-INT. ZOBJECT type ZSPI-DDL-INT. ZSPI-TKN-ERRLIST token-type ZSPI-TYP-LIST. Error list with error returned by ZSPI-SSN-ZRD ZSPI-TKN-ENDLIST token-type ZSPI-TYP-SSCTL. ZSPI-TKN-ENDLIST token-type ZSPI-TYP-SSCTL.
15: ZORS-ERR-ORELOAD-INPROGRESS ORSERV Error Messages 15: ZORS-ERR-ORELOAD-INPROGRESS An application specified the ZORS-CMD-ONLINERELOAD command for a file, but an online reload operation was already in progress for the file. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZORS-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
16: ZORS-ERR-NO-ORELOAD ORSERV Error Messages 16: ZORS-ERR-NO-ORELOAD An application specified the ZORS-CMD-SUSPEND command for a file, but an online reload operation had not been initiated for the file. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZORS-MAP-CMD-ERROR ZNAME ZCOMMAND ZOBJECT ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. type ZSPI-DDL-FNAME. type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-SSCTL.
17: ZORS-ERR-CANT-SUSPEND ORSERV Error Messages 17: ZORS-ERR-CANT-SUSPEND An application specified the ZORS-CMD-SUSPEND command for a file, but the online reload operation cannot be suspended because: • • ORSERV called the KEYPOSITION file-system procedure for the ZZRELOAD file, but an error occurred on the call (for example, a NOWAIT operation has not yet completed for ZZRELOAD file).
ORSERV Error Messages 17: ZORS-ERR-CANT-SUSPEND File Utility Program (FUP) Management Programming Manual—523322-001 C -18
Index A D APPENDV TACL function ASSIGN messages 2-1 Asterisk (*) in FUP file sets 2-13 AUTOSTOP parameter 2-1 Backup opens and closes 2-3 Backup process-name qualifier 2-3 DDL format 2-8, 2-24 DDL statements 3-1 DEF DDL statement 3-1 Definition files, Compaq 2-8 Definitions, Compaq Description 2-24 ZFUP- 2-27 ZSPI- 2-24 C E CANCEL file-system procedure 2-13 CANCEL requests 2-13 CHECKSUM command 3-2 Circumflex (^) in symbolic names 2-8 COBOL85 example A-1 Codes, FUP token (table) 2-9 Command and respo
F Index Examples COBOL85, FUP DUPLICATE command A-1 TAL FUP CHECKSUM command 3-6 FUP DUPLICATE command 3-19 FUP LOADALTFILE command 3-37 Starting and opening FUP 2-5 G GETVERSION command description 3-22 GUARDIAN See Operating system H Hyphen (-) in symbolic names 2-8 I F IN file parameter 2-1 FASTSORT utility 2-19 Field types 2-10 File names 2-12 File sets 2-12 File-system errors, opening FUP 2-3 File-system procedures CANCEL 2-13 EDITREAD 2-19 EDITREADINIT 2-19 FUP functions 1-7 NEWPROCESS 2-1 NEW
P Index P PARAM messages 2-1 Predefined values, FUP Description 2-10 ZFUP-VALBUFLEN 2-3, 2-10, 2-12, 2-27 KEEP 3-13 NEW 3-13 OLD 3-13 PURGE 3-13 SSID 2-26, 2-27 VERSION 2-27 Process-name qualifier 2-3 Programming, ORSERV management 1-5 R READ WITH PROMPT command, COBOL85 2-4 REPLYV TACL function Requester-server programming, FUP 2-1 Response record, FUP Multiple records 2-15 Single record 2-14 Single record in data list 2-16 RESTART command 3-39 Restartable option for DUPLICATE command 3-11, 3-39 S Send
W Index W Warning messages 2-16, 2-17, B-1, C-1 WRITEREAD file-system procedure 2-4 Z ZALT-NAME field ZFUP-MAP-ALT-RENAME-OPTS 3-14 ZALT-NUMBER field ZFUP-MAP-ALT-RENAME-OPTS 3-14 ZBLOCK-SIZE field ZFUP-MAP-LOAD-SOURCEOPTS 3-26 ZCOMMAND field ZFUP-MAP-CMD-ERROR 2-28 ZCOMPACT field ZFUP-MAP-LOAD-DEST-OPTS 3-28 ZCOUNT field ZFUP-MAP-LOADALT-XFERCNTS 3-35 ZFUP-MAP-LOAD-XFER-CNTS 3-31 ZDEST-OPTION field ZFUP-MAP-PAR-DUP 3-13 ZDSLACK field ZFUP-MAP-LOAD-KEYSEQOPTS 3-29 ZFUP-MAP-PAR-LOADALTFILE 3-34 ZEBCDIC fi
Z Index ZFUP-ERR- (continued) INV-TEMPLATE B-10 INV-VALUE B-8 KEPT B-72 KEYLEN-ZERO B-78 LONG-COMMAND B-11 MISS-ALTFILE B-42 MISS-FIELD B-6 MISS-PART B-43 MISS-TOKEN B-5 MUST-REARRANGE-DATA B-51 MUST-SQL-RECOMPILE B-83 NOT-ON-OPTICAL B-82 NOT-ON-PARTF B-47 NOT-ON-SQL-OBJECT B-84 NOT-ON-VIEW B-86 NOT-REST-FILECODE B-95 NO-ALT-FILE B-44 NO-DEFINE B-71 NO-EXTSIZE B-45 NO-MEM B-13 NO-ZSVR B-46 OPTICAL-RESTART-FILE B-90 OP-REJECT B-48 OUT-IS-SQL B-87 PART-IS-SQL B-88 PART-KEY-LONG B-54 PART-KEY-MISSING B-79 PE
Z Index ZFUP-MAP-LOAD-KEYSEQOPTS (continued) ZMAX-RECS field 3-29 ZPARTOF field 3-29 ZSCRATCH field 3-29 ZSORTED field 3-29 ZFUP-MAP-LOAD-SOURCE-OPTS Description 3-25 ZBLOCK-SIZE field 3-26 ZEBCDIC field 3-26 ZEMPTYOK field 3-26 ZMOUNT-MSG-FILE field 3-27 ZRECORD-SIZE field 3-26 ZREELS field 3-27 ZREWIND field 3-27 ZSHARE field 3-26 ZSKIP field 3-27 ZTRIMCHAR field 3-28 ZTRIMCHAR-IS-PRESENT field 3-28 ZUNLOAD field 3-27 ZVAR-REC field 3-26 ZFUP-MAP-LOAD-XFER-CNTS Description 3-31 ZCOUNT field 3-31 ZNAME f
Z Index ZOBJECT field ZFUP-MAP-CMD-ERROR 2-28 ZORS-ERRCANT-SUSPEND C-17 EXTRA-TOKEN C-7 FILESYS C-13 GUARD C-14 INVALID-TOKEN C-4 INV-COMMAND C-2 INV-OBJECT C-3 INV-VALUE C-8 LONG-COMMAND C-9 MISS-FIELD C-6 MISS-TOKEN C-5 NO-ORELOAD C-16 ORELOAD-INPROGRESS C-15 PE C-12 SPI C-11 WRONG-SERVER C-10 WRONG-SSID C-9 ZPADCHAR field ZFUP-MAP-LOAD-DEST-OPTS 3-29 ZPADCHAR-IS-PRESENT field ZFUP-MAP-LOAD-DEST-OPTS 3-28 ZPARTOF field ZFUP-MAP-LOAD-KEYSEQOPTS 3-29 ZPART-NAME field ZFUP-MAP-PART-RENAMEOPTS 3-14 ZPART-NU
Special Characters Index ZSPI-TKNALLOW-TYPE 2-24, 3-4, 3-15 COMMAND 2-14, 2-26 CONTEXT 2-14 DATALIST 2-15 ENDLIST 2-15 ERROR 2-17, 2-26 MAXRESP 2-15 OBJECT-TYPE 2-14, 2-26 PARM-ERR 2-26 RESPONSE-TYPE 2-16 RETCODE 2-17, 2-26 SSID 2-14 USEDLEN 2-13 ZSPI-TYP- (SPI Token Types) FUP (table) 2-11 ZSPI-VALERR-AND-WARN 2-16 FALSE 2-24 TANDEM 2-26 TRUE 2-24 ZTRIMCHAR field ZFUP-MAP-LOAD-SOURCEOPTS 3-28 ZTRIMCHAR-IS-PRESENT field ZFUP-MAP-LOAD-SOURCEOPTS 3-28 ZUNLOAD field ZFUP-MAP-LOAD-SOURCEOPTS 3-27 ZVAR-REC fie
Contact NonStop Himalaya Publications Mail, E-Mail, or Fax Your Comments To ATTN: Product Manager—Software Publications LOC CAC-03 Compaq Computer Corporation NonStop Division Cupertino, CA 95014-2599 pubs.comments@compaq.
What’s New in This Manual What’s New in This Manual ix Manual Information ix New and Changed Information ix About This Manual xi Who Should Read This Manual? Organization of This Manual xi Related Reading xii Your Comments Invited xii Notation Conventions xiii xi 1.
3. FUP Commands and Responses 3. FUP Commands and Responses CHECKSUM Command 3-2 DUPLICATE Command 3-10 GETVERSION Command 3-22 LOAD Command 3-24 LOADALTFILE Command 3-33 RESTART Command 3-39 4.
A. Management Application Example Example 5-16 SUSPEND Command 5-18 Tokens in the Command Buffer Tokens in the Response Buffer Example 5-20 5-18 5-19 A. Management Application Example B.
B.
C.
Index 13: ZORS-ERR-FILESYS C-13 14: ZORS-ERR-GUARD C-14 15: ZORS-ERR-ORELOAD-INPROGRESS 16: ZORS-ERR-NO-ORELOAD C-16 17: ZORS-ERR-CANT-SUSPEND C-17 C-15 Index File Utility Program (FUP) Management Programming Manual—523322-001 6
Examples Examples File Utility Program (FUP) Management Programming Manual—523322-001 1
Examples File Utility Program (FUP) Management Programming Manual—523322-001 2
Figures Figures Figure 1-1. Figure 1-2. Figure 1-3. Figure 2-1. Figure 2-2. Figure 2-3. Figure 2-4. Figure 2-5. Figure 2-6. Figure 2-7. Figure 2-8. Figure 2-9. Figure 2-10. Figure 2-11. Figure 2-12. Figure 3-1. Figure 3-2. Figure 3-3. Figure 4-1. Figure 4-2. Figure 4-3. Figure 4-4. Figure 4-5. Figure 4-6. Figure 4-7. Figure 4-8. Figure 4-9. Figure 5-1. Figure 5-2. Figure 5-3. Figure A-1.
Figures File Utility Program (FUP) Management Programming Manual—523322-001 2
Tables Tables Table 1-1. Table 2-1. Table 2-2. Table 2-3. Table 2-4. Table 2-5. Table 2-6. Table 2-7. Table 3-1. Table 3-2. Table 3-3. Table 3-4. Table 3-5. Table 4-1. Table 4-2. Table 4-3. Table 4-4.
