DSM/Tape Catalog Messages Manual Abstract This manual describes the error, warning, and informational messages that are returned to users in the Distributed Systems Management/Tape Catalog (DSM/TC) environment. Product Version DSM/TC H01 Supported Release Version Updates (RVUs) This manual supports G06.27 and all subsequent G-series RVUs, H06.03 and all subsequent H-series RVUs, and J06.03 and all subsequent J-series RVUs until otherwise indicated by its replacement publication.
Document History Part Number Product Version Published 422947-003 DSM/TC G06 May 2003 422947-004 DSM/TC G06 April 2004 422947-005 DSM/TC G06 August 2005 422947-006 DSM/TC H01 February 2008 422947-007 DSM/TC H01 February 2013
Legal Notices Copyright 2013 Hewlett-Packard Development Company L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
DSM/Tape Catalog Messages Manual Index Tables Legal Notices What’s New in This Manual v Manual Information v New and Changed Information About This Manual vii Notation Conventions v viii 1. Catalog Manager (MEDIADBM) Error Messages Error Numbers 1 Through 999 1-1 2. MEDIACOM Syntax Error Message Error Numbers 1000 Through 2000 3. MEDIACOM to MEDIASRV Communications Error Messages Error Numbers 2200 Through 3000 3-1 4.
Contents 9. Storage Server Interface Messages 9. Storage Server Interface Messages Storage Server Interface Message Handling SSI EMS Output Syntax 9-1 SSI Example Output 9-1 $ZSSI EMS Message Text 9-3 Event Messages 1 and 2 9-3 Event Message 3 9-3 Event Message 4 9-11 Events 5 Through 10 9-17 Other Error Codes 9-19 9-1 10.
Contents 12. MEDIACOM Warning Messages 12. MEDIACOM Warning Messages Warning Messages 100, 900, and 6306 12-1 13. File-System OPEN Errors Error 197 13-1 Errors 594 and 595 13-1 Index Tables Table 3-1.
Contents DSM/Tape Catalog Messages Manual — 422947-007 iv
What’s New in This Manual Manual Information DSM/Tape Catalog Messages Manual Abstract This manual describes the error, warning, and informational messages that are returned to users in the Distributed Systems Management/Tape Catalog (DSM/TC) environment. Product Version DSM/TC H01 Supported Release Version Updates (RVUs) This manual supports G06.27 and all subsequent G-series RVUs, H06.03 and all subsequent H-series RVUs, and J06.
What’s New in This Manual Changes in the H06.13 manual: Changes in the H06.13 manual: Updated the following error messages: 639 on page 1-12. 1087 on page 2-18. 1123 on page 2-26. 1131 and 1132 on page 2-28. 6007 on page 5-2. Changes in the H06.07 manual: Warning message 638 was added on page 1-12 of Catalog Manager (MEDIADBM) Error Messages. Changes for the G06.
What’s New in This Manual Changes for the G06.
What’s New in This Manual Changes for the G06.
About This Manual This manual contains the error, warning, and informational messages that are returned from the Distributed Systems Management/Tape Catalog (DSM/TC) environment: Section Description Section 1, Catalog Manager (MEDIADBM) Error Messages Contains error messages that are returned to any console that is executing a DSM/TC operator interface (MEDIACOM) session. These messages are returned at the MEDIACOM prompt after you try to complete a command.
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 Notation for Messages … Ellipsis. An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times. For example: M address [ , new-value ]… [ - ] {0|1|2|3|4|5|6|7|8|9}… An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times. For example: "s-char…" Punctuation.
About This Manual Notation for Management Programming Interfaces Nonitalic text. Nonitalic letters, numbers, and punctuation indicate text that is displayed or returned exactly as shown. For example: Backup Up. 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 Change Bar Notation The CRE has many new message types and some new message type codes for old message types. In the CRE, the message type SYSTEM includes all messages except LOGICAL-CLOSE and LOGICAL-OPEN.
About This Manual Change Bar Notation DSM/Tape Catalog Messages Manual — 422947-007 xiv
1 Catalog Manager (MEDIADBM) Error Messages Error Numbers 1 Through 999 The error messages documented in this section are returned from the DSM/TC catalog manager (MEDIADBM). The errors in this section are listed in numeric order. However, not all of the available error numbers in the range 1 through 999 are used. Error numbers not listed are reserved for future use. 100 **WARNING-100** No records matched the search pattern. Cause.
Catalog Manager (MEDIADBM) Error Messages Error Numbers 1 Through 999 304 **ERROR-304** The volume catalog already exists. Cause. The volume catalog you specified already exists. Effect. The volume catalog you are trying to create is not created. Recovery. Because the volume catalog already exists, no recovery is necessary. If you specified a volume catalog name incorrectly, retype and resubmit the correct name. 305 **ERROR-305** The volume catalog specified does not exist. Cause.
Catalog Manager (MEDIADBM) Error Messages Error Numbers 1 Through 999 308 **ERROR-308** The pool is not empty. Use the DELETE TAPEVOLUME command to empty the pool. Cause. You attempted to delete a pool that contains existing tape volumes. Effect. The pool is not deleted. Recovery. To delete the pool, first delete the tape volume entries using the DELETE TAPEVOLUME command. 309 **ERROR-309** The pool specified does not exist. Cause. You specified a pool that does not exist. Effect.
Catalog Manager (MEDIADBM) Error Messages Error Numbers 1 Through 999 603 **ERROR-603** Unable to a create catalog manager on system name because of error-number Cause. Due to a problem indicated by error-number, you cannot create a catalog manager on a remote node. Effect. The command does not execute. Recovery. Analyze the error message. These error conditions might exist: a NEWPROCESS error, CREATE_ERROR, or security violation. Or possibly DSM/TC does not exist on that system.
Catalog Manager (MEDIADBM) Error Messages Error Numbers 1 Through 999 Recovery. Analyze the error. 608 **ERROR-608** Unable to alter the tape volume because the current status must be BAD, RELEASED, or SCRATCH. Cause. Because the tape is either assigned, selected, or in use, its status cannot be altered. Effect. The status does not change. The command does not execute. Recovery. If the tape is selected or in use, you must wait for it to be written to before you can change its status.
Catalog Manager (MEDIADBM) Error Messages Error Numbers 1 Through 999 Recovery. Analyze the error. 612 **ERROR-612** A pool constraint violation in the LABELS field has been detected. Cause. An attempt to execute an ALTER POOL command to alter the label formats has failed. For example, you might have specified that a pool allowing only ANSI tapes is to use IBM tapes, but ANSI tapes already exist in the pool. Effect. The command does not execute. Recovery. Delete the tapes that are causing the conflict.
Catalog Manager (MEDIADBM) Error Messages Error Numbers 1 Through 999 Recovery. Enter the name of this tape in an excluded pool. 616 **ERROR-616** Unable to add the tape volume name because of the following error: Cause. An attempt to add a tape name failed. Effect. The tape is not added. Recovery. Analyze the error. 617 **ERROR-617** The pool has no scratch tapes. ADD/LABEL TAPEVOLUME command to create more. Use the Cause.
Catalog Manager (MEDIADBM) Error Messages Error Numbers 1 Through 999 619 **ERROR-619** The EXPIRE process has not run in the past 3 days. The RESET EXPIRATION option of the ALTER MEDIADEFS command must be used to confirm that the system time is correct. Cause. The DSM/TC clean-up process has not run in the last three days. Effect. Because an unknown condition exists, the clean-up process will not run in the future. Recovery.
Catalog Manager (MEDIADBM) Error Messages Error Numbers 1 Through 999 622 **ERROR-622** The pool specified already exists in the volume catalog. Cause. An attempt to create a pool in a volume catalog failed because the pool already exists in the volume catalog. Effect. The command does not execute. Recovery. No action is required. 623 **ERROR-623** Either the catalog name specified already exists, or the SUBVOL specified already has a file or volume catalog. Cause.
Catalog Manager (MEDIADBM) Error Messages Error Numbers 1 Through 999 626 **ERROR-626** File system error error-number occurred while accessing the CONFIG table. Cause. A file-system error was received while trying to access the file catalog. Effect. The command does not execute. Recovery. Analyze the error. 627 **ERROR-627** File system error error-number occurred while accessing the POOL table. Cause. A file-system error was received while trying to access the volume catalog. Effect.
Catalog Manager (MEDIADBM) Error Messages Error Numbers 1 Through 999 630 **ERROR-630** Unable to alter the tape volume because the current status must be ASSIGNED or FULL, or is valid only for append capable pools. Cause. An attempt to alter the status of a tape volume between ASSIGNED and FULL failed because either the specified tape volume is in an incorrect state or the pool is not append capable. Effect. The requested operation terminates. Recovery. No recovery, the operation cannot occur.
Catalog Manager (MEDIADBM) Error Messages Error Numbers 1 Through 999 identified as incorrect, the ALTER MEDIADB, LONGNAME command cannot be used to perform this update. Effect. The media catalog tables cannot be updated for use with Backup Restore 2 using the ALTER MEDIADB, LONGNAME command. Recovery. Contact the Global Customer Support Center (GCSC) for upgrade help. 638 **WARNING-638** Default Mediadefs Updated Cause. The absence of an expected single row in CATDEFS table. Effect.
Catalog Manager (MEDIADBM) Error Messages Error Numbers 1 Through 999 903 **WARNING-903** Media Catalog tables need to be upgraded to support LONGNAME. Cause. A LONGNAME-capable Media Catalog version is installed, but the underlying tables have not yet been upgraded. Effect. The requested operation terminates. Recovery. Execute the ALTER MEDIADB, LONGNAME directive. 907 **WARNING-907** No tape volumes matching volume-name were found. Cause. No tape volumes matching the search pattern were found. Effect.
Catalog Manager (MEDIADBM) Error Messages Error Numbers 1 Through 999 DSM/Tape Catalog Messages Manual — 422947-007 1 -14
2 MEDIACOM Syntax Error Message Error Numbers 1000 Through 2000 The error messages documented in this section are returned if you enter the incorrect syntax for MEDIACOM commands. The errors in this section are listed in numeric order. However, not all of the available error numbers in the range 1000 through 2000 are used. Error numbers not listed are reserved for future use. 1000 **ERROR-1000** Number expected. Cause. A number is expected for this part of the command. Effect. The command does not run.
MEDIACOM Syntax Error Message Error Numbers 1000 Through 2000 1004 **ERROR-1004** Only one tape label is allowed when NEWNAME is specified. Cause. The ADD TAPELABEL command with the NEW NAME option was specified with more than one tape name. Effect. The command does not run. Recovery. Specify only one tape name. 1005 **ERROR-1005** SCRATCH cannot be specified with NEWNAME. Cause. The SCRATCH option cannot be used with NEWNAME option in an ADD TAPELABEL command. Effect. The command does not run. Recovery.
MEDIACOM Syntax Error Message Error Numbers 1000 Through 2000 1008 **ERROR-1008** Unknown system. Cause. An unknown node was specified. Effect. The command does not run. Recovery. Specify an existing node. 1009 **ERROR-1009** The SUBVOL system and the catalog system must match. Cause. The creation of a file catalog or volume catalog failed because the logical name and physical name are on different subvolumes. Effect. The command does not run. Recovery.
MEDIACOM Syntax Error Message Error Numbers 1000 Through 2000 1013 **ERROR-1013** Priority must be in the range 1-199. Cause. The priority specified was not in the range 1 through 199. Effect. The command does not run. Recovery. Specify a priority value within the allowed range 1 through 199. 1014 **ERROR-1014** CPU number must be in the range 0-15. Cause. The CPU number specified was not in the range 0 through 15. Effect. The command does not run. Recovery.
MEDIACOM Syntax Error Message Error Numbers 1000 Through 2000 1018 **ERROR-1018** Expecting BRIEF or DETAIL. Cause. Something other than BRIEF or DETAIL was specified for this command. Effect. The command does not run. Recovery. Specify BRIEF, DETAIL, or no option. 1020 **ERROR-1020** Expecting BLPCHECK or NLCHECK or LSM. Cause. Something other than BLPCHECK, NLCHECK, or LSM was specified for this part of the command. Effect. The command does not run. Recovery.
MEDIACOM Syntax Error Message Error Numbers 1000 Through 2000 1024 **ERROR-1024** Expecting a file-id. Cause. You did not specify a tape file ID. Effect. The command does not run. Recovery. Specify a tape file ID. 1025 **ERROR-1025** Expecting TAPEMOUNT. Cause. You did not specify the TAPEMOUNT keyword for this command. Effect. The command does not run. Recovery. Specify TAPEMOUNT. 1026 **ERROR-1026** Expecting TAPEVOLUME. Cause. You did not specify the TAPEVOLUME keyword for this command. Effect.
MEDIACOM Syntax Error Message Error Numbers 1000 Through 2000 1029 **ERROR-1029** Missing final quote. Cause. A final quotation mark (“) is required for this command. Effect. The command does not run. Recovery. Specify a final quote character. 1030 **ERROR-1030** Illegal character. Cause. An invalid character was specified for this command. Effect. The command does not run. Recovery. Check the syntax for this command and reenter valid characters only.
MEDIACOM Syntax Error Message Error Numbers 1000 Through 2000 1033 **ERROR-1033** Expecting a quoted string. Cause. A string was not specified or was not enclosed with quotation marks (“). Effect. The command does not run. Recovery. Specify a string and enclose it with quotation marks. 1034 **ERROR-1034** Keyword too long. Cause. A command keyword is too long. Effect. The command does not run. Recovery. Check the syntax of the command and specify the keyword in the proper length.
MEDIACOM Syntax Error Message Error Numbers 1000 Through 2000 1037 **ERROR-1037** Expecting semicolon or return. Cause. A semicolon or return key character was not entered. Effect. The command does not run. Recovery. Enter a semicolon or return key character. 1038 **ERROR-1038** Missing parameter. Cause. A command parameter is missing. Effect. The command does not run. Recovery. Specify the missing parameter. 1039 **ERROR-1039** SUBVOL must be specified. Cause. The SUBVOL parameter was not specified.
MEDIACOM Syntax Error Message Error Numbers 1000 Through 2000 1042 **ERROR-1042** Process name required. Cause. A process name was not specified. Effect. The command does not run. Recovery. Specify a process name. 1043 **ERROR-1043** Expecting comma or return. Cause. Either a comma or a return key character was not specified. Effect. The command does not run. Recovery. Specify either a comma or return key character. 1044 **ERROR-1044** Expecting comma or ")". Cause.
MEDIACOM Syntax Error Message Error Numbers 1000 Through 2000 1047 **ERROR-1047** Unrecognized object. Cause. An object is unrecognized. Effect. The command does not run. Recovery. Specify a recognized object. 1048 **ERROR-1048* Illegal LEVEL. Cause. An invalid value for was specified for the LEVEL option. Effect. The command does not run. Recovery. Specify a valid value for LEVEL. 1049 **ERROR-1049** Expecting TAPEDRIVE, TAPEMOUNT, or SERVER. Cause.
MEDIACOM Syntax Error Message Error Numbers 1000 Through 2000 1052 **ERROR-1052** Expecting VALID or INVALID. Cause. The VALID or INVALID keyword was not specified. Effect. The command does not run. Recovery. Specify the VALID or INVALID keyword. 1053 **ERROR-1053** Unrecognized tape volume status. Cause. The specified tape status is not recognized. Effect. The command does not run. Recovery. Specify a recognized tape status. 1054 **ERROR-1054** Illegal COUNT. Cause.
MEDIACOM Syntax Error Message Error Numbers 1000 Through 2000 1057 **ERROR-1057** Illegal disk file name. Cause. An invalid disk file name was specified. Effect. The command does not run. Recovery. Specify a valid disk file name. 1058 **ERROR-1058** Illegal tape file attribute. Cause. An invalid tape file parameter was specified. Effect. The command does not run. Recovery. Specify a valid tape file parameter. 1059 **ERROR-1059** Illegal DSM/TC parameter specified. Cause.
MEDIACOM Syntax Error Message Error Numbers 1000 Through 2000 1063 **ERROR-1063** Expecting ANSI, IBM, BACKUP, or ANY. Cause. The ANSI, IBM, BACKUP, or ANY keyword was not specified. Effect. The command does not run. Recovery. Specify ANSI, IBM, BACKUP, or ANY. 1064 **ERROR-1064** Unrecognized option. Cause. The option you specified is not recognizable. Effect. The command does not run. Recovery. Check the syntax of this command and respecify the option. 1065 **ERROR-1065** Unrecognized command. Cause.
MEDIACOM Syntax Error Message Error Numbers 1000 Through 2000 1068 **ERROR-1068** Colon expected between hour and minute. Cause. A colon was not placed between the hour and minute. Effect. The command does not run. Recovery. Place a colon between the hour and minute. 1069 **ERROR-1069** Expecting 1600, or 6250. Cause. The 1600 or 6250 keyword was not specified. Effect. The command does not run. Recovery. Specify 1600 or 6250. 1070 **ERROR-1070** Expecting 1600, 6250, or ANY. Cause.
MEDIACOM Syntax Error Message Error Numbers 1000 Through 2000 1073 **ERROR-1073** Expecting an absolute generation number. Cause. The value specified for the GEN parameter was not an absolute generation number. Effect. The command does not run. Recovery. Specify an absolute generation number for GEN. 1074 **ERROR-1074** Expecting SUBVOL. Cause. The SUBVOL parameter was not specified. Effect. The command does not run. Recovery. Specify the SUBVOL parameter. 1075 **ERROR-1075** Expecting ON or OFF. Cause.
MEDIACOM Syntax Error Message Error Numbers 1000 Through 2000 1078 **ERROR-1078** Expecting return. Cause. A return key character was not specified. Effect. The command does not run. Recovery. Specify a return key character. 1079 **ERROR-1079** Illegal device or volume specified. Cause. An invalid device or disk was specified. Effect. The command does not run. Recovery. Specify a valid device or disk. 1080 **ERROR-1080** Illegal default volume specified. Cause. An invalid default volume was specified.
MEDIACOM Syntax Error Message Error Numbers 1000 Through 2000 1083 **ERROR-1083** Illegal file name. Cause. An invalid file name was specified. Effect. The command does not run. Recovery. Specify a valid file name. 1084 **ERROR-1084** Unable to open OUT file. Cause. Cannot open the OUT file. Effect. The command does not run. Recovery. Specify a correct OUT file 1085 **ERROR-1085** Illegal node name. Cause. An invalid node name was specified. Effect. The command does not run. Recovery.
MEDIACOM Syntax Error Message Error Numbers 1000 Through 2000 Recovery. Use HELP for respective command to view the valid media types for that command. 1088 **ERROR-1088** The first character must be alphabetic. Cause. The first character specified was not alphabetic. Effect. The command does not run. Recovery. Enter an alphabetic first character. 1089 **ERROR-1089** Comment exceeds maximum length. Cause. The comment string exceeded the maximum length. Effect. The command does not run. Recovery.
MEDIACOM Syntax Error Message Error Numbers 1000 Through 2000 Effect. The command does not run. Recovery. Specify the USER, BACKFILE, BACKVOLUME, or ALL keyword. 1093 **ERROR-1093** Expecting USER, BACKFILE, or BACKVOLUME. Cause. The USER, BACKFILE, or BACKVOLUME keyword was not specified. Effect. The command does not run. Recovery. Specify the USER, BACKFILE or BACKVOLUME keyword. 1094 **ERROR-1094** Expecting FIXED or UNDEFINED. Cause. The FIXED or UNDEFINED keyword was not specified. Effect.
MEDIACOM Syntax Error Message Error Numbers 1000 Through 2000 1097 **ERROR-1097** VOLCAT must be specified. Cause. The VOLCAT parameter was not specified. Effect. The command does not run. Recovery. Specify the VOLCAT parameter. 1098 **ERROR-1098** FILECAT must be specified. Cause. The FILECAT parameter was not specified. Effect. The command does not run. Recovery. Specify the FILECAT parameter. 1100 **ERROR-1100** POOL must be specified. Cause. The POOL parameter was not specified. Effect.
MEDIACOM Syntax Error Message Error Numbers 1000 Through 2000 1103 **ERROR-1103** STATUS or TAPEDRIVE must be specified. Cause. Either the STATUS or TAPEDRIVE parameter was not specified. Effect. The command does not run. Recovery. Specify the STATUS or TAPEDRIVE parameter. 1104 **ERROR-1104** STATUS must be specified. Cause. The STATUS parameter was not specified. Effect. The command does not run. Recovery. Specify the STATUS parameter.
MEDIACOM Syntax Error Message Error Numbers 1000 Through 2000 1108 **ERROR-1108** MODE must be specified. Cause. The MODE parameter was not specified. Effect. The command does not run. Recovery. Specify the MODE parameter. 1109 **ERROR-1109** GEN must be specified. Cause. The GEN parameter was not specified. Effect. The command does not run. Recovery. Specify the GEN parameter. 1110 **ERROR-1110** TAPEFILE must be specified. Cause. The TAPEFILE parameter was not specified. Effect.
MEDIACOM Syntax Error Message Error Numbers 1000 Through 2000 1112 **ERROR-1112** Expecting LSM Drive ID: #, Drive #). (ACS #, LSM #, Panel Cause. LSM option ID information (ACS ID, LSM ID, Panel ID, Drive ID) was not specified. Effect. The command does not run. Recovery. Specify LSM option ID information. 1113 **ERROR-1113** Expecting POOL, TAPEFILE, or TAPEVOLUME. Cause. The POOL, TAPEFILE, or TAPEVOLUME keyword was not specified. Effect. The command does not run. Recovery.
MEDIACOM Syntax Error Message Error Numbers 1000 Through 2000 1116 **ERROR-1116** Illegal security specified. Cause. An invalid security code was specified. Effect. The command does not run. Recovery. Specify a valid security code. 1117 **ERROR-1117** Expecting a quote. Cause. The quotation mark (“) was not specified. Effect. The command does not run. Recovery. Specify the required quotation mark. 1118 **ERROR-1118** Expecting SECURE or OWNER. Cause. The SECURE or OWNER option was not specified. Effect.
MEDIACOM Syntax Error Message Error Numbers 1000 Through 2000 1121 **ERROR-1121** No concatenated commands are allowed after !, ?, or FC. Cause. Other characters were specified after the exclamation point, question mark, or FC characters. Effect. The command does not run. Recovery. Once you finish with these commands, you cannot specify anything after them. 1122 **ERROR-1122** ?, !, and FC are not allowed with obey or outfiles. Cause.
MEDIACOM Syntax Error Message Error Numbers 1000 Through 2000 1125 **ERROR-1125** Cannot use Options and IN file in same command. Cause. A RECOVER DISKFILE command was entered with both a Restore IN file and Restore run options specified. You can specify an IN file or run options, but not both. Effect. The command does not run. Recovery. Retry the command using only an IN file or Restore options, not both. 1126 **ERROR-1126** Internal parsing error, an illegal code path was executed. Cause.
MEDIACOM Syntax Error Message Error Numbers 1000 Through 2000 1129 **ERROR-1129** Expecting: LONGNAME. Cause. An ALTER MEDIADB command was entered with an invalid option. Effect. The command does not run. Recovery. Specify LONGNAME as an option in the command (ALTER MEDIADB, LONGNAME). 1130 **ERROR-1130** LOCALTOREMOTE or TIME option not allowed with OSS nor SQL/MX objects. Cause.
3 MEDIACOM to MEDIASRV Communications Error Messages Error Numbers 2200 Through 3000 The error messages in this section are returned when a communications error occurs between MEDIACOM and the MEDIASRV server process. The errors are listed in numeric order. However, not all available error numbers in the range 2200 through 3000 are used. Error numbers not listed are reserved for future use. 2202 **ERROR-2202** File system error error-number occurred on the I/O. Cause.
MEDIACOM to MEDIASRV Communications Error Messages Error Numbers 2200 Through 3000 2207 **ERROR-2207** File system error error-number occurred on the WRITEREAD. Cause. A file-system error occurred on the WRITEHEAD to the MEDIASRV process. Effect. The command does not execute. Recovery. Analyze the error. 2208 **ERROR-2208** The NEWPROCESS failed with error error-number. Cause. NEWPROCESS failed due to the specified error Effect. The command does not execute. Recovery. Analyze the NEWPROCESS error.
MEDIACOM to MEDIASRV Communications Error Messages Error Numbers 2200 Through 3000 2211 **ERROR-2211** The buffer returned is not from MEDIASRV. Cause. The buffer returned is not from MEDIASRV. Effect. The command cannot be processed. Recovery. Contact your service provider. 2214 **ERROR-2214** No server is currently running. Cause. No server is running. Effect. The command does not execute. Recovery. Execute a command to start a server or create your own server.
MEDIACOM to MEDIASRV Communications Error Messages Error Numbers 2200 Through 3000 2219 **ERROR-2219** The system default volumecatalog value was unattainable, please use the VOLCAT command to set a session default. Cause. When this session started, MEDIASRV was unable to find the system default name for the file catalog. Effect. The command cannot run. Recovery. You can specify a default file catalog using the VOLCAT command.
MEDIACOM to MEDIASRV Communications Error Messages Error Numbers 2200 Through 3000 2993 **ERROR-2993** DSM/TC error xxxx failed to print due to IMMU error-x. Cause. Printing fails because of an error in the Informational Message Management Utilities (IMMU). For possible error values, see Table 3-1. Effect. No error text is displayed. Recovery. IMMU is used for handling message text, help text, and keyword substitution.
MEDIACOM to MEDIASRV Communications Error Messages Error Numbers 2200 Through 3000 2994 **ERROR-2994** Command history returned error number, number Cause. An error was returned when you entered ?, !, FC, or HISTORY. Effect. The command does not execute. Recovery. Attempt to correct the problem. If the problem persists, contact your service provider.
4 MEDIASRV Syntax and Content Error Messages Error Numbers 5001 Through 6000 The error messages in this section are returned from MEDIASRV when you enter the incorrect syntax or values for MEDIACOM commands. These messages can also be received if you are accessing MEDIASRV programmatically. However, the text will reflect the names of various options and keywords as they are seen through MEDIACOM. The errors are listed in numeric order.
MEDIASRV Syntax and Content Error Messages Error Numbers 5001 Through 6000 5004 **ERROR-5004** AUTOSCRATCH must be ON or OFF. Cause. A reset value was specified for the AUTOSCRATCH option. Effect. The command does not execute. Recovery. Use the HELP command to see what is valid for AUTOSCRATCH and specify a valid value. 5005 **ERROR-5005** The TIME and GEN options are mutually exclusive. Cause. The TIME option was used with GEN. Effect. The command does not execute. Recovery.
MEDIASRV Syntax and Content Error Messages Error Numbers 5001 Through 6000 5008 **ERROR-5008** ABENDRETENTION is invalid. Cause. The value specified for the ABENDRETENTION option is invalid. Effect. The command does not execute. Recovery. Specify a valid value for ABENDRETENTION. 5009 **ERROR-5009** TAPEVOLUME cannot be wildcarded. Cause. Wild-card characters were specified for TAPEVOLUME. Effect. The command does not execute. Recovery. Do not specify wild-card characters.
MEDIASRV Syntax and Content Error Messages Error Numbers 5001 Through 6000 5013 **ERROR-5013** APPEND must be ON or OFF. Cause. An attempt to add or alter a pool specifying an APPEND attribute other than ON or OFF occurred. Effect. The requested operation terminates. Recovery. Correct the syntax. 5014 **ERROR-5014** APPEND must be ON or OFF. Cause. An attempt was made to add a pool specifying an APPEND attribute other than ON or OFF. Effect. The requested operation terminates. Recovery.
MEDIASRV Syntax and Content Error Messages Error Numbers 5001 Through 6000 5017 **ERROR-5017** SUBVOL cannot be reset. Cause. An attempt was made to reset the SUBVOL option. Effect. The command does not execute. Recovery. Do not attempt to reset the SUBVOL option. 5018 **ERROR-5018** COMMENT comment-text, is invalid. Cause. The comment string is invalid. Effect. The command does not execute. Recovery. Enter a valid comment string. 5019 **ERROR-5019** Only one COMMENT is allowed. Cause.
MEDIASRV Syntax and Content Error Messages Error Numbers 5001 Through 6000 5022 **ERROR-5022** COUNT cannot be reset. Cause. An attempt was made to reset the COUNT option. Effect. The command does not execute. Recovery. Do not attempt to reset the COUNT option. 5023 **ERROR-5023** COUNT exceeded maximum for the TAPEVOLUME specified. Cause. The number of tapes specified with the COUNT option exceeds the number of tapes specified in the tape-name part of the LABEL TAPEVOLUME command.
MEDIASRV Syntax and Content Error Messages Error Numbers 5001 Through 6000 5026 **ERROR-5026** DENSITY cannot be reset. Cause. An attempt was made to reset the DENSITY option. Effect. The command does not execute. Recovery. Do not reset the DENSITY option. 5027 **ERROR-5027** STATUS is invalid. Cause. The value specified for STATUS is invalid. Effect. The command does not execute. Recovery. Specify a valid STATUS value. 5028 **ERROR-5028** STATUS cannot be reset. Cause.
MEDIASRV Syntax and Content Error Messages Error Numbers 5001 Through 6000 5031 **ERROR-5031** Only one FILECAT is allowed. Cause. More than one file catalog token was found in the buffer. Effect. The command does not execute. Recovery. Specify only one file catalog in the SPI buffer. 5032 **ERROR-5032** FILECAT is required. Cause. The file catalog was not specified in the SPI buffer. Effect. The command does not execute. Recovery. Specify the file catalog value in the SPI buffer.
MEDIASRV Syntax and Content Error Messages Error Numbers 5001 Through 6000 5035 **ERROR-5035** RESERVE must be ON, OFF, or RESET. Cause. An ALTER TAPEDRIVE command was entered with an invalid RESERVE setting. Effect. The command does not execute. Recovery. Retry the command, either resetting RESERVE or setting it to ON or OFF. 5042 **ERROR-5042** TAPEFILE tape-file-id, is invalid. Cause. An invalid tape file ID value was specified. Effect. The command does not execute. Recovery.
MEDIASRV Syntax and Content Error Messages Error Numbers 5001 Through 6000 5046 **ERROR-5046** STATUS is invalid. Cause. An invalid STATUS value was specified. Effect. The command does not execute. Recovery. Specify a valid STATUS value. 5047 **ERROR-5047** Expecting a maximum of 30 file ids. Cause. More than 30 tape file IDs were specified. Effect. The command does not execute. Recovery. Specify up to 30 tape file IDs. 5048 **ERROR-5048** DISKFILE disk-file-name, is invalid. Cause.
MEDIASRV Syntax and Content Error Messages Error Numbers 5001 Through 6000 5052 **ERROR-5052** DISKFILE cannot be reset. Cause. An attempt was made to reset the disk file name. Effect. The command does not execute. Recovery. Do not attempt to reset the disk file name. 5053 **ERROR-5053** Expecting a maximum of 80 disk file names. Cause. More than 80 disk file names were specified. Effect. The command does not execute. Recovery. Specify up to 80 disk file names. 5055 **ERROR-5055** STATUS is invalid.
MEDIASRV Syntax and Content Error Messages Error Numbers 5001 Through 6000 5058 **ERROR-5058** GEN cannot be reset. Cause. RESET with a reset value was specified for the GEN option. Effect. The command does not execute. Recovery. Use the HELP command to see what is valid for GEN, and specify a valid value. 5059 **ERROR-5059** LABELS is invalid. Cause. An invalid LABELS value was specified. Effect. The command does not execute. Recovery. Specify a valid LABELS value. 5060 **ERROR-5060** LSM is invalid.
MEDIASRV Syntax and Content Error Messages Error Numbers 5001 Through 6000 5062 **ERROR-5062** LOGICAL must be 1-2. Cause. The value for LOGICAL was not specified as 1 or 2. Effect. The command does not execute. Recovery. Specify a LOGICAL value of either 1 or 2. 5063 **ERROR-5063** LOGICAL cannot be reset. Cause. RESET with a reset value was specified for the LOGICAL option. Effect. The command does not execute. Recovery. Use the HELP command to see what is valid for LOGICAL, and specify a valid value.
MEDIASRV Syntax and Content Error Messages Error Numbers 5001 Through 6000 5066 **ERROR-5066** TYPE is invalid. Cause. An invalid TYPE value was specified. Effect. The command does not execute. Recovery. Specify a valid TYPE value. 5067 **ERROR-5067** TYPE cannot be reset. Cause. RESET with a reset value was specified for the TYPE option. Effect. The command does not execute. Recovery. Use the HELP command to see what is valid for TYPE, and specify a valid value.
MEDIASRV Syntax and Content Error Messages Error Numbers 5001 Through 6000 5075 **ERROR-5075** NEWNAME new-tape-name is invalid. Cause. An invalid NEWNAME value was specified. Effect. The command does not execute. Recovery. Specify a valid NEWNAME value. 5076 **ERROR-5076** NEWNAME cannot be specified if TAPENAME has been specified. more than one Cause. More than one tape name was specified in the SPI buffer with the NEWNAME option. Effect. The command does not execute. Recovery.
MEDIASRV Syntax and Content Error Messages Error Numbers 5001 Through 6000 5079 **ERROR-5079** OPERATORTERM is invalid. Cause. The OPERATORTERM token specified in the SPI buffer is invalid. Effect. The command does not execute. Recovery. Specify a valid OPERATORTERM token in the SPI buffer. 5080 **ERROR-5080** OPERATORTERM is required. Cause. The OPERATORTERM token was not specified in the SPI buffer. Effect. The command does not execute. Recovery. Specify a valid OPERATORTERM token in the SPI buffer.
MEDIASRV Syntax and Content Error Messages Error Numbers 5001 Through 6000 5084 **ERROR-5084** INFILE cannot be reset. Cause. An attempt was made to reset the INFILE in a command. Effect. The command does not execute. Recovery. INFILE is not a resettable command option. Retry the command without resetting INFILE. 5085 **ERROR-5085** OPEN of infile failed with File System error system-error. Cause. An attempt to open an input file failed due to the specified file-system error. Effect.
MEDIASRV Syntax and Content Error Messages Error Numbers 5001 Through 6000 5088 **ERROR-5088** WRITE to temporary infile failed, File System error system-error. Cause. An attempt to write to a temporary input file failed due to the specified filesystem error. Effect. The command does not execute. Recovery. Correct the problem indicated by the file-system error and then retry the command. 5090 **ERROR-5090** Only one value for the output file is allowed. Cause. More than one OUT file was specified.
MEDIASRV Syntax and Content Error Messages Error Numbers 5001 Through 6000 5093 **ERROR-5093** OVERRIDE not allowed with NEWNAME or SCRATCH. Cause. The NEWNAME or SCRATCH options were used with the OVERRIDE option. Effect. The command does not execute. Recovery. Do not use the NEWNAME or SCRATCH options with the OVERRIDE option. 5094 **ERROR-5094** OVERRIDE must be ON or OFF. Cause. The value specified for OVERRIDE was not ON or OFF. Effect. The command does not execute. Recovery.
MEDIASRV Syntax and Content Error Messages Error Numbers 5001 Through 6000 5097 **ERROR-5097** POOL pool-name is invalid. Cause. An invalid POOL value was specified. Effect. The command does not execute. Recovery. Specify a valid POOL value. 5098 **ERROR-5098** Only one POOL is allowed. Cause. More than one POOL was specified. Effect. The command does not execute. Recovery. Specify only one POOL. 5099 **ERROR-5099** At least one POOL is required. Cause. The value for POOL was not specified. Effect.
MEDIASRV Syntax and Content Error Messages Error Numbers 5001 Through 6000 5101 **ERROR-5101** Too many POOLs were specified. The limit is 30. Cause. More than 30 pools were specified. Effect. The command does not execute. Recovery. Specify up to 30 pools. 5102 **ERROR-5102** POOL pool-name cannot be wildcarded. Cause. The pool name contained wild-card characters. Effect. The command does not execute. Recovery. Specify a pool name without wild-card characters.
MEDIASRV Syntax and Content Error Messages Error Numbers 5001 Through 6000 5115 **ERROR-5115** RETENTION is invalid. Cause. An invalid RETENTION value was specified. Effect. The command does not execute. Recovery. Specify a valid RETENTION value. 5116 **ERROR-5116** RETENTION cannot be reset. Cause. RESET with a reset value was specified for the RETENTION option Effect. The command does not execute. Recovery. Use the HELP command to see what is valid for RETENTION, and specify a valid value.
MEDIASRV Syntax and Content Error Messages Error Numbers 5001 Through 6000 5119 **ERROR-5119** SEARCHSPACE must be INCLUDED or EXCLUDED. Cause. The value specified for SEARCHSPACE was not INCLUDED or EXCLUDED. Effect. The command does not execute. Recovery. Specify either INCLUDED or EXCLUDED. 5120 **ERROR-5120** SEARCHSPACE cannot be reset. Cause. RESET with a reset value was specified for the SEARCHSPACE option Effect. The command does not execute. Recovery.
MEDIASRV Syntax and Content Error Messages Error Numbers 5001 Through 6000 5124 **ERROR-5124** SSLIST list is invalid. Cause. An invalid SSLIST value was specified. Effect. The command does not execute. Recovery. Specify a valid SSLIST value. 5125 **ERROR-5125** Too many SSLISTs were specified. 30. The limit is Cause. More than 30 nodes were specified for the system search list. Effect. The command does not execute. Recovery. Specify up to 30 nodes for the system search list.
MEDIASRV Syntax and Content Error Messages Error Numbers 5001 Through 6000 5129 **ERROR-5129** Only one SYSTEM is allowed. Cause. More than one SYSTEM was specified. Effect. The command does not execute. Recovery. Specify only one SYSTEM. 5130 **ERROR-5130** SYSTEM is required. Cause. SYSTEM was not specified. Effect. The command does not execute. Recovery. Specify a SYSTEM. 5131 **ERROR-5131** SYSTEM cannot be reset. Cause. RESET with a reset value was specified for the SYSTEM option Effect.
MEDIASRV Syntax and Content Error Messages Error Numbers 5001 Through 6000 5144 **ERROR-5144** TAPEDRIVE $tape must be on the same system as MEDIASRV. Cause. The tape drive specified in the SPI buffer is on a different node than MEDIASRV is. Effect. The command does not execute. Recovery. To communicate with remote tape drives, the MEDIASRV process must be started on the same node as the tape drives. 5145 **ERROR-5145** TAPEDRIVE is required. Cause. The TAPEDRIVE option was not specified. Effect.
MEDIASRV Syntax and Content Error Messages Error Numbers 5001 Through 6000 5148 **ERROR-5148** MODE must be ALL, USER, BACKFILE, or BACKVOLUME. Cause. An incorrect value was specified for the MODE. The value must be ALL, USER, BACKFILE, or BACKVOLUME. Effect. The command does not execute. Recovery. Specify ALL, USER, BACKFILE, or BACKVOLUME as the MODE value. 5149 **ERROR-5149** MODE cannot be reset. Cause. RESET with a reset value was specified for the MODE option Effect. The command does not execute.
MEDIASRV Syntax and Content Error Messages Error Numbers 5001 Through 6000 5156 **ERROR-5156** OWNER is invalid. Cause. An invalid OWNER value was specified. Effect. The command does not execute. Recovery. Specify a valid OWNER value. 5157 **ERROR-5157** Only one OWNER is allowed. Cause. More than one OWNER was specified. Effect. The command does not execute. Recovery. Specify only one OWNER. 5158 **ERROR-5158** STATUS is invalid. Cause. An invalid tape volume STATUS value was specified. Effect.
MEDIASRV Syntax and Content Error Messages Error Numbers 5001 Through 6000 5161 **ERROR-5161** Only one TAPEVOLUME parameter is allowed. Cause. More than one TAPEVOLUME parameter was specified. Effect. The command does not execute. Recovery. Specify only one TAPEVOLUME. 5162 **ERROR-5162** TAPEVOLUME is required. Cause. The TAPEVOLUME was not specified. Effect. The command does not execute. Recovery. Specify the TAPEVOLUME. 5163 **ERROR-5163** Too many TAPEVOLUMEs were specified. limit is 100. Cause.
MEDIASRV Syntax and Content Error Messages Error Numbers 5001 Through 6000 5166 **ERROR-5166** UNLOAD is invalid. Cause. An invalid UNLOAD value was specified. Effect. The command does not execute. Recovery. Specify a valid UNLOAD value. 5167 **ERROR-5167** UNLOAD cannot be reset. Cause. RESET with a reset value was specified for the UNLOAD option. Effect. The command does not execute. Recovery. Use the HELP command to see what is valid for UNLOAD, and specify a valid value.
MEDIASRV Syntax and Content Error Messages Error Numbers 5001 Through 6000 5172 **ERROR-5172** VERSION cannot be reset. Cause. RESET with a reset value was specified for the VERSION option. Effect. The command does not execute. Recovery. Use the HELP command to see what is valid for VERSION, and specify a valid value. 5173 **ERROR-5173** VOLUMESET and STATUS VALID are mutually exclusive. Cause. The VOLUMESET option was used with STATUS VALID. Effect. The command does not execute. Recovery.
MEDIASRV Syntax and Content Error Messages Error Numbers 5001 Through 6000 5176 **ERROR-5176** Only one VOLCAT is allowed. Cause. More than one volume catalog was specified. Effect. The command does not execute. Recovery. Specify only one volume catalog. 5177 **ERROR-5177** VOLCAT is required. Cause. A volume catalog was not specified. Effect. The command does not execute. Recovery. Specify a volume catalog. 5178 **ERROR-5178** VOLCAT cannot be reset. Cause.
MEDIASRV Syntax and Content Error Messages Error Numbers 5001 Through 6000 5180 **ERROR-5180** IF TAPEFILE is wildcarded, STATUS VALID cannot be specified. Cause. The tape file ID contained wild-card characters, and STATUS VALID was used. Effect. The command does not execute. Recovery. Do not use STATUS VALID if the tape file ID contains wild-card characters. 5181 **ERROR-5181** PROMPT is invalid. Cause. An invalid PROMPT value was specified. Effect. The command does not execute. Recovery.
MEDIASRV Syntax and Content Error Messages Error Numbers 5001 Through 6000 5184 **ERROR-5184** VERSION is required with STATUS VALID. Cause. STATUS was specified, but VERSION was not. Effect. The command does not execute. Recovery. Specify VERSION with STATUS. 5185 **ERROR-5185** STATUS is not allowed with PHYSICAL ALL. Cause. STATUS was used with PHYSICAL ALL. Effect. The command does not execute. Recovery. Do not use STATUS with PHYSICAL ALL. 5186 **ERROR-5186** STATUS is not allowed with LOGICAL ALL.
MEDIASRV Syntax and Content Error Messages Error Numbers 5001 Through 6000 5188 **ERROR-5188** VOLUMEINDEX is invalid. Cause. An invalid VOLUMEINDEX value was specified. Effect. The command does not execute. Recovery. Specify a valid VOLUMEINDEX value. 5189 **ERROR-5189** The tape file on the tape volume, file-name, does not match the tape file specified. Cause. The tape file read from the tape does not match the tape file specified in the command line. Effect. The command does not execute. Recovery.
MEDIASRV Syntax and Content Error Messages Error Numbers 5001 Through 6000 5192 **ERROR-5192** Only one TAPEFILE is allowed if VOLUMESET is specified. Cause. More than one tape file ID was specified when VOLUMESET was used. Effect. The command does not execute. Recovery. Specify only one tape file ID when you use VOLUMESET. 5193 **ERROR-5193** The TAPEFILE cannot be wildcarded if VOLUMESET is specified. Cause. The tape file ID contained wild-card characters when VOLUMESET was used. Effect.
MEDIASRV Syntax and Content Error Messages Error Numbers 5001 Through 6000 5196 **ERROR-5196** LOCALREMOTE \NODE is required if multiple DISKFILEs are specified and the DISKFILEs specified are from different nodes. Cause. A RECOVER DISKFILE command was issued specifying multiple disk files from different nodes, but the command did not include the LOCALREMOTE option. Effect. The command does not execute. Recovery. Retry the command specifying the LOCALREMOTE option.
MEDIASRV Syntax and Content Error Messages Error Numbers 5001 Through 6000 5201 **ERROR-5201** REPOSITION is invalid. Cause. A command was issued using REPOSITION when it is not valid. REPOSITION is an option of the INFO TAPELABEL command and can be set only to ON or OFF. Effect. The command does not execute. Recovery. Retry the command, using REPOSITION only when valid. 5202 **ERROR-5202** REPOSITION cannot be RESET. Cause. An INFO TAPELABEL command was issued to reset the REPOSITION option. Effect.
MEDIASRV Syntax and Content Error Messages Error Numbers 5001 Through 6000 Effect. The command does not execute. Recovery. Use the HELP command to check what is valid for TAPEFORMAT and specify a valid TAPEFORMAT value. 5206 **ERROR-5206** OUTCOMMAND file filename is invalid. Cause. An invalid OUTCOMMAND file value was specified. Effect. The command does not execute. Recovery. Specify a valid OUTCOMMAND file value. 5207 **ERROR-5207** Only one OUTCOMMAND file is allowed. Cause.
MEDIASRV Syntax and Content Error Messages Error Numbers 5001 Through 6000 DSM/Tape Catalog Messages Manual — 422947-007 4 - 40
5 MED Error Messages Error Numbers 6000 Through 6200 The errors in this section are returned as a result of conditions that exist outside of MEDIASRV. The errors in this section are listed in numeric order. However, not all of the available error numbers in the range 6000 through 6200 are used. Error numbers not listed are reserved for future use. 6001 **ERROR-6001** At least one option is required. Cause. No options were specified for the command in the SPI buffer. Effect. The command does not execute.
MEDIASRV Command Execution Error Messages Error Numbers 6000 Through 6200 6004 **ERROR-6004** OPEN for ZSERVER failed with file system error error-number. Cause. The OPEN for ZSERVER failed with a file-system error. Effect. The command does not execute. Recovery. Analyze the file-system error. 6005 **ERROR-6005** AWAITIO to ZSERVER failed with file system error error-number. Cause. The AWAITIO to ZSERVER failed with a file-system error. Effect. The command does not execute. Recovery.
MEDIASRV Command Execution Error Messages Error Numbers 6000 Through 6200 6008 **ERROR-6008** TMF must be configured on your system. Cause. TMF has not been configured on your system. Effect. No DSM/TC command can execute. Recovery. Configure TMF on your system. 6009 **ERROR-6009** Only members of the super group can execute this command. Your user ID is id. Cause. You tried to execute a super-group authority command without authority. Effect. The command does not execute. Recovery.
MEDIASRV Command Execution Error Messages Error Numbers 6000 Through 6200 6012 **ERROR-6012** DEFINE creation error error-number. Cause. An error was returned while you tried to create a DEFINE. Effect. The command does not execute. Recovery. Analyze the error.
MEDIASRV Command Execution Error Messages Error Numbers 6000 Through 6200 6013 **ERROR-6013** DEFINE add error error-number. Cause. An error was returned when you tried to add a DEFINE. Effect. The command does not execute. Recovery. Analyze the error. 6014 **ERROR-6014** DEFINE open error, error-number. Cause. An error was returned when you tried to open the DEFINE. Effect. The command does not execute. Recovery. Analyze the error. 6015 **ERROR-6015** Processing stopped by user. Cause.
MEDIASRV Command Execution Error Messages Error Numbers 6000 Through 6200 6018 **ERROR-6018** Tape drive READ error, error-number. Cause. An error was returned while trying to read the tape drive. Effect. The command does not execute. Recovery. Analyze the error. 6019 **ERROR-6019** Tape drive WRITE error, error-number. Cause. An error was returned while trying to write to the tape drive. Effect. The command does not execute. Recovery. Analyze the error.
MEDIASRV Command Execution Error Messages Error Numbers 6000 Through 6200 6023 **ERROR-6023** The tape volume mounted is not expired. Cause. The tape mounted still has assigned files on it. The tape mounted is not expired. Effect. The command does not execute. Recovery. Mount the appropriate, expired tape. If you need this tape, you must expire the files on it. 6024 **ERROR-6024** SETMODE error, error. Cause. A SETMODE error was received. Effect. The command does not execute. Recovery. Analyze the error.
MEDIASRV Command Execution Error Messages Error Numbers 6000 Through 6200 6027 **ERROR-6027** A tape with that name is already cataloged. Use the OVERRIDE option to allow the creation of a duplicate named tape volume outside DSM/TC control. Cause. A tape with a name you specified is already cataloged in DSM/TC. Effect. By default, MEDIACOM does not create two tapes with the same name. Recovery. If you want two tapes with the same name, use the OVERRIDE option (with caution).
MEDIASRV Command Execution Error Messages Error Numbers 6000 Through 6200 6031 **ERROR-6031** Unable to access the Media Defines information because of the following error: error Cause. ZSERVER could not access the ZSVRCONF file due to the returned filesystem error. Effect. The command does not execute. Recovery. Analyze the error. 6032 **ERROR-6032** The creation of RESTORE process failed with file system error system-error. Cause. The creation of the RESTORE process failed due to a file-system error.
MEDIASRV Command Execution Error Messages Error Numbers 6000 Through 6200 6035 **ERROR-6035** Invalid Restore options was specified. Cause. The options specified for the RESTORE process are invalid. Effect. Files are not restored. Recovery. For the correct RESTORE options, see the Guardian Disk and Tape Utilities Reference Manual. Then retry the RESTORE process. 6036 **ERROR-6036** Restore Abended. Cause. The RESTORE process abended. Effect. Files are not restored. Recovery.
MEDIASRV Command Execution Error Messages Error Numbers 6000 Through 6200 6039 **ERROR-6039** OPEN error error. Cause. When trying to execute an OPEN, the specified error occurred. Effect. The open fails. Recovery. Recovery actions vary based on the specified error number. For descriptions of file-system errors, see the Operator Messages Manual. 6040 **ERROR-6040** The tape block position size expected was expected-number bytes when actual-number bytes were actually received. Cause.
MEDIASRV Command Execution Error Messages Error Numbers 6000 Through 6200 6043 **ERROR-6043** The creation of BRCOM process failed with file system error system-error. Cause. The RECOVER DISKFILE directive attempted to create a BRCOM process (to effect a restore operation), but the attempt failed. Effect. The RECOVER DISKFILE directive fails. Recovery. The file-system error indicates the problem that needs to be resolved.
MEDIASRV Command Execution Error Messages Error Numbers 6000 Through 6200 Recovery. The file-system error indicates the problem that needs to be resolved. For descriptions of file-system errors, see the Guardian Procedure Errors and Messages Manual.
MEDIASRV Command Execution Error Messages Error Numbers 6000 Through 6200 DSM/Tape Catalog Messages Manual — 422947-007 5 - 14
6 MEDIASRV SPI Command Language Standard (CLS) Error Messages Error Numbers 6201 Through 6300 The errors in this section are returned by MEDIASRV as a result of conditions that violate the SPI Command Language Standard (CLS). The errors in this section are listed in numeric order. However, not all of the available error numbers in the range 6201 through 6300 are used. Error numbers not listed are reserved for future use.
MEDIASRV SPI Command Language Standard (CLS) Error Messages Error Numbers 6201 Through 6300 6204 **ERROR-6204** The SPI buffer MEDIASRV received contained an unknown tokencode: code. Cause. The MEDIASRV process received an unknown token code. Effect. The command does not execute. Recovery. Specify only known token codes. 6205 **ERROR-6205** The SPI buffer MEDIASRV received contained an unknown command: command, the object was: object. Cause. MEDIASRV received the SPI buffer with an unknown command.
7 $ZSVR Error Messages Error Numbers 6300 Through 6500 The messages in this section are error messages that are returned to any console that is executing a DSM/TC operator interface (MEDIACOM) session. These messages are returned at the MEDIACOM prompt after attempting to complete a command. For the text portions of EMS messages from the Tape Server Process, $ZSVR, see Section 11, Tape Server Process Messages. The errors are listed in numeric order.
$ZSVR Error Messages Error Numbers 6300 Through 6500 6304 **ERROR-6304** ALTER TAPEMOUNT is not allowed on this request. Cause. You specified ALTER TAPEMOUNT for a request that cannot be altered. Effect. The command does not execute. Recovery. Mount a requested tape or reject the request. 6305 **ERROR-6305** The LEVEL cannot be lowered with outstanding tape requests. Cause. You attempted to alter the tape support level while outstanding tape requests still exist. Effect. The command does not execute.
$ZSVR Error Messages Error Numbers 6300 Through 6500 6308 **ERROR-6308** The default values cannot be altered with outstanding tape requests. Cause. You attempted to alter default values while there are outstanding tape requests. Effect. The command does not execute. Recovery. Wait until the outstanding tape requests are satisfied and reexecute the command. 6309 **ERROR-6309** The LSM drive is in use, the drive address cannot be altered. Cause.
$ZSVR Error Messages Error Numbers 6300 Through 6500 6312 **ERROR-6312** The console is in use. Use the RESET DEVICE option of this command before altering the console. Cause. An attempt to alter the console failed because the console is in use. Effect. The console is not altered. Recovery. Use the RESET DEVICE option before attempting to alter the console. 6313 **ERROR-6313** The operation has been aborted by the third party tapes manager with error error-number. Cause.
$ZSVR Error Messages Error Numbers 6300 Through 6500 6316 **ERROR-6316** The AUTOMATED specified is invalid. Cause. An ALTER MEDIADEFS command was entered with an invalid AUTOMATED setting. Effect. The command does not execute. Recovery. Reenter the command, setting AUTOMATED to ON or OFF. 6317 **ERROR-6317** The ZServer VERSION is incompatible. Cause. The current version of ZServer is incompatible with other components. Effect. ZServer does not function properly. Recovery.
$ZSVR Error Messages Error Numbers 6300 Through 6500 DSM/Tape Catalog Messages Manual — 422947-007 7-6
8 MEDIASRV/SPI Internal Error Messages Error Numbers 6700 Through 6799 The error messages in this section are returned as a result of internal errors between MEDIASRV and the Subsystem Programmatic Interface (SPI). The errors are listed in numeric order. However, not all available error numbers in the range 6700 through 6799 are used. Error numbers not listed are reserved for future use. 6701 **ERROR-6701** MEDIASRV replied with internal error, errornumber. Cause.
MEDIASRV/SPI Internal Error Messages Error Numbers 6700 Through 6799 6704 **ERROR-6704** MEDIASRV encountered SPI error, error-number, while using the token token. Cause. The MEDIASRV process received an SPI error while using the specified token. Effect. The command does not execute. Recovery. Contact your service provider. 6705 **ERROR-6705** MEDIASRV encountered error, error-number, while initializing the SPI buffer. Cause. The MEDIASRV process received an error while initializing the SPI buffer.
MEDIASRV/SPI Internal Error Messages Error Numbers 6700 Through 6799 6708 **ERROR-6708** MEDIACOM encountered error, error-number, while using the token token-value. Cause. MEDIACOM received an error while using the token value returned in this message. Effect. The command does not execute. Recovery. Contact your service provider. 6709 **ERROR-6709** MEDIACOM encountered error, error-number, while initializing the SPI buffer. Cause. MEDIACOM received an error while initializing the SPI buffer. Effect.
MEDIASRV/SPI Internal Error Messages Error Numbers 6700 Through 6799 DSM/Tape Catalog Messages Manual — 422947-007 8-4
9 Storage Server Interface Messages Storage Server Interface Message Handling The Storage Server Interface process ($ZSSI) generates EMS events. Event message text contains a prefix, followed by one or more lines of message text. The prefix contains the date and time of entry, standard format EMS header name, and the request ID generated by $ZSSI. For more information on the Storage Server Interface, see the DSM/Tape Catalog User’s Guide.
Storage Server Interface Messages SSI Example Output Undefined Host Name This example shows a series of EMS messages reporting a fatal fault because a PARAM value was not specified for CSI^HOSTNAME: 92-11-30 17:17:16 \SYS1.$ZSSI 92-11-30 17:17:21 \SYS1.$ZSSI 92-11-30 17:17:22 \SYS1.$ZSSI 92-11-30 17:17:22 \SYS1.$ZSSI TANDEM.SSI.G06 000001 SSI activated:Initiation Started; t_ssi_init(); TANDEM.SSI.
Storage Server Interface Messages $ZSSI EMS Message Text $ZSSI EMS Message Text These $ZSSI messages are arranged in numeric order, first by event number and then by error code for events that could report different codes. Event Messages 1 and 2 1 ZSSI activated: Initiation started. Cause. $ZSSI has started. Effect. $ZSSI is establishing a connection with the Communications Server Interface (CSI) server. Recovery. Informational message only; no corrective action is needed.
Storage Server Interface Messages Event Message 3 Cause. $ZSSI cannot find specific members in an internal queue. Effect. $ZSSI does not find a specific member in an internal queue. Recovery. None of the queue members are dropped because they are older than the connection queue aging time (defined by the CSI_CONNECT_AGETIME environment variable). However, if this error occurs more frequently than the connections queue aging time, contact your service provider.
Storage Server Interface Messages Event Message 3 Recovery. Depending on the errors found in the EMS log, reestablish communication with the portmapper and RPC. If the error is repeated, contact your service provider. For more information, see the DSM/Tape Catalog User’s Guide. 3 (19) Invalid network protocol. Cause. An unsupported network protocol was passed to the csi_rpccall() function. Effect. $ZSSI terminates. Recovery. This is a $ZSSI programming error. Contact your service provider.
Storage Server Interface Messages Event Message 3 Insufficient disk space. Even if an allowance was made for extensible memory, the swap volume does not have sufficient space to accommodate the needs of the process. Overload of CPU. Too many demands were made of the CPU, causing it to use up internal resources such as memory allocated for time-list elements (TLEs). Effect. The request fails. Recovery.
Storage Server Interface Messages Event Message 3 3 (27) Message for unknown client discarded. Cause. $ZSSI detected a message from the CSI for an invalid or unknown client. Effect. The message for unknown client is discarded. Recovery. If the error is repeated, contact your service provider. 3 (34) Invalid communications service. Cause. Invalid information was received for communications. Effect. $ZSSI might ignore the request or terminate. Check the EMS log for more events. Recovery.
Storage Server Interface Messages Event Message 3 3 (44) Duplicate packet from Network detected: discarded. Remote IP address: address, Process-ID: ident, Sequence number: numb, ID: id Cause. $ZSSI received a duplicate packet from CSI. Values for address, ident, numb, and id identify the packet. Effect. $ZSSI automatically drops the duplicate packet. Recovery. Informative message only; no corrective action needed. 3 (45) Network timeout. Cause. $ZSSI cannot connect to the network. Effect.
Storage Server Interface Messages Event Message 3 3 (48) Invalid type. Cause. The SSI received a packet from the network interface with either an unrecognizable type in the IPC_HEADER portion of the CSI REQUEST_HEADER or an unrecognizable IDENTIFIER type in the message packet. A problem exists with the server software that tried to communicate with the SSI. Effect. $ZSSI ignores the request. Recovery. If the error recurs, contact your network or UNIX-based server support representative.
Storage Server Interface Messages Event Message 3 3 (52) Invalid version number, number. Cause. The version number in the message header is not supported. Effect. $ZSSI discards the message. Recovery. This is a programming error. If the error is repeated, contact your service provider. For more information, see the DSM/Tape Catalog User’s Guide. 3 (54) Validation warning. Cause.
Storage Server Interface Messages Event Message 4 3 (501) Non-successful status returned from CSI. Cause. CSI cannot successfully complete the request. Effect. None. Recovery. Informative message only; no corrective action needed. Event Message 4 Event message 4 can report many different error codes, described in this subsection. All instances of event message 4 are formatted like this: Fatal fault: error-code-text 4 (2) Create of RPC TCP service failed, Address: address, Port: port Cause.
Storage Server Interface Messages Event Message 4 4 (9) Creation of connect queue failed. Cause. $ZSSI cannot initialize the internal address connection queue. Possible causes of this event are: Insufficient configured memory. The process was initiated with a fixed amount of memory, and that memory was insufficient. Insufficient disk space. Even if an allowance was made for extensible memory, the swap volume does not have sufficient space to accommodate the needs of the process. Overload of CPU.
Storage Server Interface Messages Event Message 4 Recovery. Recovery depends on the cause of the error: If the configured memory was insufficient, the PMAP_MAXENTRIES define (default 1000) in the portmapper might need to be increased. If disk space was insufficient, move the data-swap volume to a disk with more available space.
Storage Server Interface Messages Event Message 4 4 (17) RPC TCP client connection failed: Address: address, Port: port rpc_error_msg, rpc_error_msg is a detailed error message generated by the RPC service itself. In most cases, this message is “Program number not registered,” which indicates that either the CSI or the $ZSSI is not running. address is the address of the client host. port is the port number of the client where a connection was attempted. Cause.
Storage Server Interface Messages Event Message 4 If disk space was insufficient, move the data-swap volume to a disk with more available space. If a CPU overload occurred, the process might need to be run on another CPU that is not heavily loaded, or the system might need to be reconfigured to increase the amount of system resources such as system data space for TLEs and process control blocks (PCBs). 4 (32) Cannot send message to NI: discarded. Cause.
Storage Server Interface Messages Event Message 4 4 (38) Undefined hostname. Cause. $ZSSI encountered an undefined client host on startup. Effect. $ZSSI terminates. Recovery. Check that the NonStop operating system and UNIX-based server system host names are defined for both system configurations: either a host file or the domain_name resolver process. Check that the NonStop server and the UNIX-based server are assigned the appropriate host names.
Storage Server Interface Messages Events 5 Through 10 4 (52) Invalid version number, number. Cause. The version number in the message header is not supported. Effect. $ZSSI discards the message. Recovery. This is a programming error. If the error is repeated, contact your service provider. For more information, see the DSM/Tape Catalog User’s Guide. 4 (205) Creating socket socket-name failed on error-number. Cause. $ZSSI cannot initialize the socket. Effect. $ZSSI terminates. Recovery.
Storage Server Interface Messages Events 5 Through 10 Effect. None. Recovery. Informational message only; no corrective action needed. 7 I/O error: error, filename: filename. Cause. An I/O error occurred. This is most likely due to an Open Error 12, which is a file-system error indicating that the specified file is in use. Effect. The specified file could not be opened. Recovery. Correct the indicated file-system error. 8 Unrecognized system message on $RECEIVE, code: message-code. Cause.
Storage Server Interface Messages Other Error Codes Other Error Codes These other error codes might be indicated in SSI event messages. (1) Unmapped previously registered RPC service. Cause. $ZSSI notifies you that an RPC number previously assigned to $ZSSI still exists. Effect. $ZSSI unmaps the number and remaps to a new one as a normal part of the initiation. $ZSSI is initiated. Recovery. Informative message only; no corrective action needed.
Storage Server Interface Messages Other Error Codes than the connection queue aging time, there is no action. If the previous messages indicates that the client cannot receive messages after retries, report the error. Invalid $RECEIVE sender. Cause. $ZSSI does not recognize the sender process. Effect. $ZSSI terminates. Recovery. This is a programming error by the client software that attempted communication with $ZSSI.
10 Remote Procedure Call Messages Remote Procedure Call Message Handling The Remote Procedure Call (RPC) facility on the NonStop operating system generates EMS events. Event message text contains a prefix, followed by one or more lines of message text. The prefix contains the date and time of entry, standard format EMS header name, and the request ID generated by RPC. For more information on RPC and the portmapper, see the DSM/Tape Catalog User’s Guide.
Remote Procedure Call Messages RPC Event Message Descriptions RPC Event Message Descriptions This subsection contains each message that the RPC subsystem can issue. The descriptions are in ascending order by event number; that is, in ascending order by ZRPC-EVT- values. -1: ZRPC-EVT-CPU-SWITCH The backup portmapper process has taken over for the primary process because of a hardware error, an operator request, a primary processor abend, or a primary process CPU failure.
Remote Procedure Call Messages -1: ZRPC-EVT-CPU-SWITCH ZCOM-TKN-SUBJ-PROC is the only possible value that can be returned as the subject token. ZCOM-TKNSUBJ-PROC indicates the name of the portmapper process that switched CPUs. ZEMS-TKN-EMPHASIS is a header token that contains the value ZSPI-VAL-TRUE, indicating a critical event. ZCOM-TKN-NEW-CPU indicates the number of the new primary CPU. ZCOM-TKN-OLD-CPU indicates the number of the old primary CPU.
Remote Procedure Call Messages -1: ZRPC-EVT-CPU-SWITCH Recommended Action The recommended action depends on the reason the primary processor was terminated: If the primary processor stopped unexpectedly, report the problem to your service provider. The primary process should not stop unexpectedly during normal operations. If the primary process abended, report the problem to your service provider. The primary process should not abend during normal operations.
Remote Procedure Call Messages 1: ZRPC-EVT-PMAP-STARTED 1: ZRPC-EVT-PMAP-STARTED The portmapper process started. Unconditional Tokens ZCOM-TKN-OBJTYPE ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-PROC ZEMS-TKN-EMPHASIS token-type token-type token-type token-type token-type ZSPI-TKN-SERVER-BANNER ZSPI-TYP-ENUM. ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-STRING. ZSPI-TYP-BOOLEAN. token-type ZSPI-TYP-CHAR50.
Remote Procedure Call Messages 2: ZRPC-EVT-IO-ERR ZSPI-TKN-SERVER-BANNER indicates the version of the RPC subsystem used by the portmapper process. Event-Message Text In the text message, subjname corresponds to the value in ZCOM-TKN-SUBJ-PROC, and rpc-version corresponds to the value in ZSPI-TKN-SERVER-BANNER. Probable Cause A portmapper process started. Recommended Action This event provides information only; no action is required.
Remote Procedure Call Messages 2: ZRPC-EVT-IO-ERR ZEMS-TKN-EVENTNUMBER is a header token that contains the event number. Its value is ZRPC-EVT-IO-ERR (2) ZEMS-TKN-SUBJECT-MARK is the standard EMS token that always immediately precedes the subject token; in this case, ZCOM-TKN-SUBJ-FILE. ZCOM-TKN-SUBJ-FILE is the only possible value that can be returned as the subject token. ZCOM-TKNSUBJ-FILE indicates the name of the file where the I/O error occurred.
Remote Procedure Call Messages 3: ZRPC-EVT-INIT-FAIL 3: ZRPC-EVT-INIT-FAIL The portmapper process failed to initialize. Unconditional Tokens ZCOM-TKN-OBJTYPE ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-PROC ZEMS-TKN-EMPHASIS token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-STRING. ZSPI-TYP-BOOLEAN. ZRPC-TKN-INIT-ERR ZRPC-TKN-BAD-ARG token-type ZSPI-TYP-INIT-ERR-NUM. token-type ZSPI-TYP-STRING.
Remote Procedure Call Messages 3: ZRPC-EVT-INIT-FAIL ZRPC-TKN-INIT-ERR indicates the reason the portmapper process failed to initialize. The possible values are: ZRPC-VAL-INIT-ERR-NO-MOM indicates that the portmapper process was unable to locate the MOM. ZRPC-VAL-INIT-ERR-ARGS indicates that an invalid argument list was specified. ZRPC-VAL-INIT-ERR-MULT-BCPU indicates that more than one BACKUPCPU value was specified. ZRPC-VAL-INIT-ERR-INV-BCPU indicates that an invalid BACKUPCPU value was specified.
Remote Procedure Call Messages 3: ZRPC-EVT-INIT-FAIL ZRPC-VAL-INIT-ERR-NOT-SUPER indicates that the user starting the portmapper process is not a super-group user. ZRPC-TKN-BAD-ARG contains additional information, if available, such as the argument or process that caused the error. The token type is ZSPI-TYP-STRING. Event-Message Text In the text message, initerr corresponds to the value in ZRPC-TKN-INIT-ERR, and errarg corresponds to the value in ZRPC-TKN-BAD-ARG.
Remote Procedure Call Messages 4: ZRPC-EVT-SLR-ERR 4: ZRPC-EVT-SLR-ERR A call to the NonStop TCP/IP Sockets Library Routine (SLR) failed or returned an error. Unconditional Tokens ZCOM-TKN-OBJTYPE ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-FILE ZEMS-TKN-EMPHASIS token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-STRING. ZSPI-TYP-BOOLEAN. ZSPI-TKN-ERRLIST ... ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST.
Remote Procedure Call Messages 4: ZRPC-EVT-SLR-ERR ZCOM-TKN-SUBJ-FILE is the only possible value that can be returned as the subject token. ZCOM-TKNSUBJ-FILE indicates the socket file name where the error occurred. ZEMS-TKN-EMPHASIS is a header token that contains the value ZSPI-VAL-TRUE, indicating that this is a critical event. ZRPC-TKN-SOCK-TYPE indicates the type of socket where the error occurred. Possible values are: 1 indicates the socket was a TCP stream socket.
Remote Procedure Call Messages 4: ZRPC-EVT-SLR-ERR Probable Cause A call to the NonStop TCP/IP Sockets Library Routine (SLR) failed or returned an error. The value returned for the Z-ERROR field in ZSPI-TKN-ERROR within the error list indicates the cause of the error. This value can be interpreted as follows: Values in the range 301 through 342 indicate a NonStop TCP/IP socket error. NonStop TCP/IP socket errors are defined in the ZTCPIP.PARAMH source file.
Remote Procedure Call Messages 5: ZRPC-EVT-RPC-ERR 5: ZRPC-EVT-RPC-ERR A procedure in the Remote Procedure Call (RPC) library failed or returned an error. Unconditional Tokens ZCOM-TKN-OBJTYPE ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-FILE ZEMS-TKN-EMPHASIS token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-STRING. ZSPI-TYP-BOOLEAN. ZSPI-TKN-ERRLIST ... ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST.
Remote Procedure Call Messages 5: ZRPC-EVT-RPC-ERR ZEMS-TKN-EMPHASIS is a header token that contains the value ZSPI-VAL-TRUE, indicating that this is a critical event. Event-Message Text In the text message, sockfile corresponds to the value in ZCOM-TKN-SUBJ-FILE; rpc corresponds to the value in ZSPI-TKN-PROC-ERR within the error list. error corresponds to the Z-ERROR field in ZSPI-TKN-ERROR within the error list.
Remote Procedure Call Messages 6: ZRPC-EVT-CREATE-ERR 6: ZRPC-EVT-CREATE-ERR A call to the NEWPROCESS procedure failed to create the backup process or a remote process. The backup process is used for fault tolerance. A remote process is used to handle broadcast RPC requests. Unconditional Tokens ZCOM-TKN-OBJTYPE ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-FILE ZEMS-TKN-EMPHASIS token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-ENUM. ZSPI-TYP-MARK.
Remote Procedure Call Messages 6: ZRPC-EVT-CREATE-ERR ZCOM-TKN-SUBJ-FILE is the only possible value that can be returned as the subject token. ZCOM-TKNSUBJ-FILE indicates the program file name of the process that could not be created. ZEMS-TKN-EMPHASIS is a header token that contains the value ZSPI-VAL-TRUE, indicating that this is a critical event. ZRPC-TKN-NEWPROC-TYPE indicates the type of process that the NEWPROCESS call was attempting to create.
Remote Procedure Call Messages 7: ZRPC-EVT-CONN-LOST Probable Cause Most likely resources were unavailable in the CPU in which the new process was trying to start. Check the value of ZRPC-TKN-CREATE-ERR for the specific cause. Recommended Action In most cases, the portmapper logs the event and continue running. Check the value of ZRPC-TKN-CREATE-ERR for the specific cause.
Remote Procedure Call Messages 7: ZRPC-EVT-CONN-LOST ZCOM-OBJ-PROC the portmapper process. ZEMS-TKN-EVENTNUMBER is a header token that contains the event number. Its value is ZRPC-EVT-CONN-LOST (7) ZEMS-TKN-SUBJECT-MARK is the standard EMS token that always immediately precedes the subject token; in this case, ZCOM-TKN-SUBJ-PROC. ZCOM-TKN-SUBJ-PROC is the only possible value that can be returned as the subject token.
Remote Procedure Call Messages 8: ZRPC-EVT-BKUP-FAIL If the connection was lost due to a network connection failure, restore the network connection to an operational state. Under most conditions, the portmapper process logs the event, continues running, and periodically reattempts the communication. 8: ZRPC-EVT-BKUP-FAIL The backup portmapper process terminated, resulting in a loss of fault tolerance.
Remote Procedure Call Messages 8: ZRPC-EVT-BKUP-FAIL ZCOM-TKN-SUBJ-PROC is the only possible value that can be returned as the subject token. ZCOM-TKNSUBJ-PROC indicates the name of the backup portmapper process that terminated. ZEMS-TKN-EMPHASIS is a header token that contains the value ZSPI-VAL-TRUE, indicating that this is a critical event. ZRPC-TKN-CPU indicates the CPU number where the backup process was running. ZRPC-TKN-BKUP-FAIL-REASON indicates the reason the backup process terminated.
Remote Procedure Call Messages 9: ZRPC-EVT-BAD-VSN If the processor in which the backup was running went down, change the backup processor assignment to restore the process to full backup status, or wait until the processor is restored. The primary portmapper process automatically attempts to restart the backup on the designated processor. 9: ZRPC-EVT-BAD-VSN The indicated portmapper process was initiated on an inappropriate system. The process terminates.
Remote Procedure Call Messages 9: ZRPC-EVT-BAD-VSN ZEMS-TKN-EMPHASIS is a header token that contains the value ZSPI-VAL-TRUE, indicating a critical event.
Remote Procedure Call Messages 10: ZRPC-EVT-MEM-FULL Event-Message Text The text message does not contain any variables. Probable Cause The portmapper process started on an incompatible version of the operating system. Recommended Action Restart the process on a suitable host processor. 10: ZRPC-EVT-MEM-FULL Insufficient memory is available. If this occurs at process startup, the affected process terminates.
Remote Procedure Call Messages 10: ZRPC-EVT-MEM-FULL ZEMS-TKN-SUBJECT-MARK is the standard EMS token that always immediately precedes the subject token; in this case, ZCOM-TKN-SUBJ-PROC. ZCOM-TKN-SUBJ-PROC is the only possible value that can be returned as the subject token. ZCOM-TKNSUBJ-PROC indicates the name of the portmapper process with the memory shortage. ZEMS-TKN-EMPHASIS is a header token that contains the value ZSPI-VAL-TRUE, indicating a critical event.
Remote Procedure Call Messages 11: ZRPC-EVT-PROG-ERR If a CPU overload occurred, the process might need to be run on another CPU that is not as heavily loaded, or the system might need to be reconfigured to increase the amount of system resources such as system data space for TLEs and process control blocks (PCBs). 11: ZRPC-EVT-PROG-ERR The portmapper process detected an unrecoverable internal error and abended. This event should not occur during normal operation.
Remote Procedure Call Messages 11: ZRPC-EVT-PROG-ERR ZCOM-OBJ-PROC the portmapper process. ZEMS-TKN-EVENTNUMBER is a header token that contains the event number. Its value is ZRPC-EVT-PROG-ERR (11). ZEMS-TKN-SUBJECT-MARK is the standard EMS token that always immediately precedes the subject token; in this case, ZCOM-TKN-SUBJ-PROC. ZCOM-TKN-SUBJ-PROC is the only possible value that can be returned as the subject token. ZCOM-TKNSUBJ-PROC indicates the name of the portmapper process that detected the error.
Remote Procedure Call Messages 12: ZRPC-EVT-UNEXP-IO-CMPL fname corresponds to the value in ZSPI-TKN-PROG-FNAME. bindtime corresponds to the value in ZGRD-TKN-BINDTIMESTAMP. entrypt corresponds to the value in ZGRD-TKN-ENTRYPOINTLABEL. s-reg corresponds to the value in ZGRD-TKNSREGISTER. p-reg corresponds to the value in ZGRD-TKN-PREGISTER. env-reg corresponds to the value in ZGRD-TKN-STACKENV. l-reg corresponds to the value in ZGRD-TKN-LREGISTER.
Remote Procedure Call Messages 13: ZRPC-EVT-MAX-ABENDS ZEMS-TKN-SUBJECT-MARK is the standard EMS token that always immediately precedes the subject token; in this case, ZCOM-TKN-SUBJ-FILE. ZCOM-TKN-SUBJ-FILE is the only possible value that can be returned as the subject token. ZCOM-TKNSUBJ-FILE indicates the name of the file where the unexpected I/O completion occurred. ZEMS-TKN-EMPHASIS is a header token that contains the value ZSPI-VAL-TRUE, indicating that this is a critical event.
Remote Procedure Call Messages 13: ZRPC-EVT-MAX-ABENDS Unconditional Tokens ZCOM-TKN-OBJTYPE indicates which type of process reported the event. The only possible value for the RPC subsystem is: ZCOM-OBJ-PROC the portmapper process. ZEMS-TKN-EVENTNUMBER is a header token that contains the event number. Its value is ZRPC-EVT-MAX-ABENDS (13). ZEMS-TKN-SUBJECT-MARK is the standard EMS token that always immediately precedes the subject token; in this case, ZCOM-TKN-SUBJ-PROC.
Remote Procedure Call Messages 14: ZRPC-EVT-UNKWN-MSG-SRC 14: ZRPC-EVT-UNKWN-MSG-SRC An inbound message was received that originated from a process that did not have a current open of the portmapper process. Unconditional Tokens ZCOM-TKN-OBJTYPE ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-PROC ZEMS-TKN-EMPHASIS token-type token-type token-type token-type token-type ZRPC-MAP-RECV-INFO def ZRPC-DDL-RECV-INFO ZNODE type ZCPU type ZPIN type ZIOTYPE type ZPAID type end. ZSPI-TYP-ENUM.
Remote Procedure Call Messages 14: ZRPC-EVT-UNKWN-MSG-SRC ZCOM-TKN-SUBJ-PROC is the only possible value that can be returned as the subject token. ZCOM-TKNSUBJ-PROC indicates the name of the process that sent the message. ZEMS-TKN-EMPHASIS is a header token that contains the value ZSPI-VAL-FALSE, indicating this is not a critical event. ZRPC-MAP-RECV-INFO is an extensible structured token that contains information about the process that issued the message.
Remote Procedure Call Messages 15: ZRPC-EVT-UNEXP-SYS-MSG Event-Message Text In the text message, procname corresponds to the value in ZCOM-TKN-SUBJ-PROC, and node, cpu, pin, iotype, and paid correspond to the values of the ZNODE, ZCPU, ZPIN, ZIOTYPE and ZPAID fields of ZRPC-MAP-RECV-INFO;. Probable Cause This event can occur when the portmapper process is restarted in a CPU and has the same PIN as a previously running process opened by the process that issued the message.
Remote Procedure Call Messages 15: ZRPC-EVT-UNEXP-SYS-MSG ZEMS-TKN-EVENTNUMBER is a header token that contains the event number. Its value is ZRPC-EVT-UNEXP-SYS-MSG (15). ZEMS-TKN-SUBJECT-MARK is the standard EMS token that always immediately precedes the subject token; in this case, ZCOM-TKN-SUBJ-PROC. ZCOM-TKN-SUBJ-PROC is the only possible value that can be returned as the subject token. ZCOM-TKNSUBJ-PROC indicates the name of the portmapper process that received the message.
Remote Procedure Call Messages 16: ZRPC-EVT-CLNT-STAT-ERR 16: ZRPC-EVT-CLNT-STAT-ERR The portmapper coprocess received a client status error from an RPC library routine. Tokens in Event Message ZCOM-TKN-OBJTYPE ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-PROC ZEMS-TKN-EMPHASIS ZRPC-TKN-CS-ERR ZRPC-TKN-RPC-PROC ZRPC-TKN-PROGRAM-NUM ZRPC-TKN-VERSION ZRPC-TKN-IP-ADDR token-type token-type token-type token-type token-type <1> <2> <3> <4> <5> ZSPI-TYP-ENUM. ZSPI-TYP-ENUM. ZSPI-TYP-MARK.
Remote Procedure Call Messages 16: ZRPC-EVT-CLNT-STAT-ERR ZRPC-TKN-CS-ERR indicates the client status error that occurred and the corresponding error text. Possible values are: # ZRPC-VAL-CSE-... Indicates...
Remote Procedure Call Messages 17: ZRPC-EVT-PORTMAP-ERR Recovery. Informational message only; no corrective action is needed. 17: ZRPC-EVT-PORTMAP-ERR The portmapper process received an invalid RPC request from the indicated host. Tokens in Event Message ZCOM-TKN-OBJTYPE ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-PROC ZEMS-TKN-EMPHASIS ZRPC-TKN-PMAPPROC ZRPC-TKN-IP-ADDR token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-ENUM. ZSPI-TYP-MARK.
Remote Procedure Call Messages 17: ZRPC-EVT-PORTMAP-ERR ZRPC-TKN-PMAPPROC is the name of the portmapper procedure that is being invoked, or the procedure number in the request if the number does not correspond to one of these valid portmapper RPC procedures: PMAPPROC_CALLIT PMAPPROC_GETPORT PMAPPROC_SET PMAPPROC_DUMP PMAPPROC_NULL PMAPPROC_UNSET ZRPC-TKN-IP-ADDR is the IP address, in dotted decimal notation (d.d.d.d), of the remote RPC host that sent the invalid request. Cause.
Remote Procedure Call Messages 18: ZRPC-EVT-FUNC-CALL-FAIL 18: ZRPC-EVT-FUNC-CALL-FAIL A function call returned an error. Tokens in Event Message ZCOM-TKN-OBJTYPE ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-PROC ZEMS-TKN-EMPHASIS ZRPC-TKN-FUNC-NAME ZRPC-TKN-RET-STATUS ZRPC-TKN-RESP-TEXT token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-STRING. ZSPI-TYP-BOOLEAN. <1> token-type ZSPI-TYP-STRING. <2> token-type ZSPI-TYP-INT2.
Remote Procedure Call Messages 18: ZRPC-EVT-FUNC-CALL-FAIL ZRPC-TKN-RESP-TEXT is a detailed description of the error of the failed function call. Cause. An error is returned by the specified function call. Examine the error details to learn more about the cause of the error. Effect. The effect depends on the severity of the error. Recovery. If the error is not severe, the process recovers by itself. Otherwise, the process abends.
11 Tape Server Process Messages Tape Server Process EMS Message Text The messages in this section are the text portions of EMS messages generated by the tape server process $ZSVR. Error 1005 - Error creating DSM/TC: error error is a file-system error. Cause. $ZSVR could not create the MEDIADBM process. Effect. No DSM/TC cataloging can be done. Recovery. Correct the error, and $ZSVR automatically creates the MEDIADBM process when needed.
Tape Server Process Messages Tape Server Process EMS Message Text Error 1008 - Error creating DSM/TC expiration process: error error is a file-system error. Cause. $ZSVR could not create the MEDDEM process because of a file-system error. Effect. No DSM/TC cleanup can be done. No tape volumes expire automatically. Recovery. Correct the error, and $ZSVR will automatically create the MEDDEM process tomorrow. If cleanup is needed now, use the MEDIACOM EXPIRE TAPEFILE command.
Tape Server Process Messages Error 1011 - SSI retryable error: Tape Server Process EMS Message Text ssi-errornum ssi-errornum is determined by the SSI process. Cause. $ZSVR received a nonfatal error from the SSI process. Effect. The tape request is retried automatically. Recovery. Use the MEDIACOM command REJECT TAPEMOUNT if you do not want to retry the request. Error 1012 - SSI non-retryable error: ssi-errornum ssi-errornum is determined by the SSI process. Cause.
Tape Server Process Messages Tape Server Process EMS Message Text Error 1014 - Ejecting mismatched tape, internal: volser1, external volser2 volser1 volser2 are the tape label names. Cause. $ZSVR detected a mismatched tape mounted by the StorageTek ACS. Effect. The application receives file-system error 595, and the tape volume is ejected from the StorageTek ACS. For more information on this error, see Section 13, FileSystem OPEN Errors. Recovery.
Tape Server Process Messages Tape Server Process EMS Message Text Error 1017 - Excluded pool requests need to specify device in the DEFINE Cause. An application requested a tape volume residing in an excluded pool but did not specify a DEVICE in the TAPECATALOG DEFINE. Effect. The application request fails with file-system error 594. For more information on this error, see Section 13, File-System OPEN Errors. Recovery. Specify a DEVICE in the TAPECATALOG DEFINE and retry the application.
Tape Server Process Messages Tape Server Process EMS Message Text Error 1020 - Volume volser not used for FILEID fileid volser is the volume name. fileid is the file identification. Cause. The VOLUME specified in the TAPECATALOG DEFINE was not used for the specified FILEID. Effect. The application read request fails with file-system error 594. Recovery. Correct the VOLUME attribute of the TAPECATALOG DEFINE or let DSM/TC automatically chose an appropriate tape volume.
Tape Server Process Messages Tape Server Process EMS Message Text Error 1023 - Need volume specified if writing multi-file sets Cause. The VOLUME attribute must be specified in the TAPECATALOG DEFINE when writing multifile volume sets (FILESEQ > 1). Effect. The application request fails with file-system error 594. For more information on this error, see Section 13, File-System OPEN Errors. Recovery.
Tape Server Process Messages Tape Server Process EMS Message Text tapes. For more information on this error, see the DSM/Tape Catalog Management Programming Manual. Error 1027 - Error error on DSM/TC console device Cause. An error occurred while the system was trying to send a message to the Distributed Systems Management/Tape Catalog (DSM/TC) console (using the MEDIACOM ALTER CONSOLE command). Effect. The DSM/TC console is automatically closed. Recovery.
Tape Server Process Messages Tape Server Process EMS Message Text Error 1029 - Tapefile tapefile terminated abnormally Cause. An application using a tape drive terminated without calling CLOSE. This message occurs only when processing Distributed Systems Management/Tape Catalog (DSM/TC) controlled tape volumes. Effect. ABENDRETENTION is used instead of the normal retention. Recovery. To change the retention from the ABENDRETENTION value, use the MEDIACOM ALTER TAPEFILE command.
Tape Server Process Messages Tape Server Process EMS Message Text ERROR 1033 - TPTM REJECTED LABELING REQUEST WITH ERROR error Cause. The third-party tape management system (TPTM) disallowed a tape labeling request because of file-system error error. Effect. The tape request fails and returns file-system error 751. Recovery. For recovery information, refer to the TPTM documentation. ERROR 1034 - TPTM RETURNED ERROR error, CONTINUING REQUEST Cause.
Tape Server Process Messages Tape Server Process EMS Message Text ERROR 1036 - ALTER TAPEMOUNT mount-sequence FAILED WITH ERROR error error is the error number returned from the TMF catalog. Possible values are: -3 TMF out of scratch tapes -4 Alternate copy not found -5 Cannot use alternate series copy after first tape -6 No such TMF tape -7 No such TMF dump Cause. An error was returned from the TMF catalog when a MEDIACOM ALTER TAPEMOUNT mount-sequence command was attempted. Effect.
Tape Server Process Messages Tape Server Process EMS Message Text Cause. The requested ACS tape volume is security protected through the StorageTek server so that this NonStop operating system is denied access to the tape. Effect. The application requesting the tape receives file-system error 48 on the open request. Recovery. Restart the application, specifying a different ACS tape volume. ERROR 1039 - LOCAL MEDIADBM VERSION IS INCOMPATIBLE WITH $ZSERVER Cause.
Tape Server Process Messages Tape Server Process EMS Message Text ERROR 1042 - TPTM IS NOT CONFIGURED, REQUEST ABORTED Cause. An attempt was made to access a tape drive or label a tape while a third-party tape management system (TPTM) is configured so that the MEDIADEFS support level is set to INTEGRATED, TPTM, or TPTMCOMPATIBLE, but the TPTM process is not running. This error occurs if the $ZSVR process was started after the TPTM process. Effect. The request is aborted with file-system error 751.
Tape Server Process Messages Tape Server Process EMS Message Text Effect. After a tape switch, BACKUP does not proceed until the drive completes the previously initiated dismount operation. After the drive is free, the BACKUP operation completes. Recovery. This is an informational message only; no corrective action is needed.
12 MEDIACOM Warning Messages Warning Messages 100, 900, and 6306 The warning messages in this section are returned to any console executing a MEDIACOM session. Messages 100 and 900 originate from the DSM/TC catalog manager (MEDIADBM). Message 6306 originates from the tape server process, $ZSVR. 100 **WARNING-100** No records matched the search pattern. Cause. A command was specified that did not match any information in the SQL database. Effect. The command does not execute. Recovery.
MEDIACOM Warning Messages Warning Messages 100, 900, and 6306 909 **WARNING 909** - volser ON drive DOES NOT ALLOW REQUESTED DENSITY/TAPEMODE Cause. The requested and actual tape density or tape mode did not match. $ZSVR selects only those tape drives that support the requested DENSITY/TAPEMODE. If the tape drive does not support the requested DENSITY/TAPEMODE, the specified tape volume is not mounted. Effect.
13 File-System OPEN Errors Error 197 The error message in this section is returned to any console in response to a failed access attempt on the SQL/MP database. 197 **ERROR-197** An SQL error has occurred. Cause. An unexpected SQL/MP database access error occurred when trying to access a DSM/TC VOLCAT or FILECAT, or the DSM/TC configuration tables. DSM/TC returned an SQL error to $ZSVR, so this error message is returned to the open of a CLASS TAPE or CLASS TAPECATALOG DEFINE. Effect.
File-System OPEN Errors Errors 594 and 595 595 **ERROR-595** A ZSSI error was returned to $ZSVR. the EMS log for detailed information. Refer to Cause. A ZSSI error was returned to $ZSVR. Effect. The OPEN fails, and processing does not continue. Recovery. Use the EMS log to analyze the specific file-system error. Correct the problem and retry the operation.
Index Numbers C MEDIASRV/SPI internal error messages 8-1 Messages RPC 10-1/10-40 $ZSSI 9-1/9-20 CSL standards violation error messages 6-1 O 638 1-12 E OPEN errors 13-1 Error messages conditions outside of MEDIASRV 5-1/5-10 CSL standards violations 6-1/6-2 MEDIACOM syntax 2-1/2-27 MEDIACOM/MEDIASRV communications 3-1/3-6 MEDIADBM 1-1/1-13 MEDIASRV 4-1/4-38 MEDIASRV syntax/content 4-1 MEDIASRV/SPI internal 8-1/8-3 $ZSVR 7-1/7-5, 11-1/11-7 Event message descriptions, RPC 10-2 R F File-system errors 1
Index Z ZSSI example output SSI activation event 9-1 SSI available event 9-1 SSI deactivating event 9-1 SSI host name not found 9-2 SSI not available event 9-1 SSI undefined host name 9-2 ZSSI messages EMS output syntax 9-1 example output 9-1 ZSSI, message text 9-3 ZSVR error messages 7-1, 11-1 DSM/Tape Catalog Messages Manual — 422947-007 Index - 2
