DSM/SCM Messages Manual

ManualsBrandsHP ManualsServerHP NonStop G-Series

DSM/SCM Messages

Manual

Abstract

This manual provides cause, effect, and recovery information for messages and errors

that you might encounter while using the Distributed Systems Management/Software

Configuration Manager (DSM/SCM).

Product Version

DSM/SCM G02

DSM/SCM H02

Supported Release Version Updates (RVUs)

This publication supports J06.03 and all subsequent J-series RVUs, H06.03 and all

subsequent H-series RVUs, and G06 and all subsequent G-series RVUs, until

otherwise indicated by its replacement publications.

Part Number Published

529845-006 May 2008

Summary of content (291 pages)

PAGE 1
DSM/SCM Messages Manual Abstract This manual provides cause, effect, and recovery information for messages and errors that you might encounter while using the Distributed Systems Management/Software Configuration Manager (DSM/SCM). Product Version DSM/SCM G02 DSM/SCM H02 Supported Release Version Updates (RVUs) This publication supports J06.03 and all subsequent J-series RVUs, H06.
PAGE 2
Document History Part Number Product Version Published 520609-007 DSM/SCM D31 and D46 December 2004 529845-003 DSM/SCM D31, G01 (ABP), and H01 July 2005 529845-004 DSM/SCM G02 September 2005 529845-005 DSM/SCM G02 and H02 February 2006 529845-006 DSM/SCM G02 and H02 May 2008
PAGE 3
Legal Notices  Copyright 2008 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.
PAGE 4
PAGE 5
DSM/SCM Messages Manual Tables Legal Notices What’s New in This Manual ix Manual Information ix New and Changed Information ix About This Manual xi What Is DSM/SCM? xi Who Should Use This Manual xi What’s in This Manual xii Other DSM/SCM Information Sources Notation Conventions xiii xii 1. INITENV Messages INITENV Messages 1-2 INITTMF Errors 1-11 INITSQL Messages 1-14 INITHDB Messages 1-18 INITTDB Messages 1-21 INITPATH Messages 1-23 STARTSCM Messages 1-24 VERIFYI Messages 1-26 2.
PAGE 6
4. ZPHIRNM Messages (continued) Contents 4. ZPHIRNM Messages (continued) File Error and Warning Messages 4-4 File Rename Error and Warning Messages 4-6 Correcting Rename Errors 4-6 Other Rename Messages 4-31 Undo TSV or TDL Processing Messages 4-31 Volume Name Validation Messages 4-32 EMS Event Generation Messages 4-34 Log-File-Related Messages 4-35 5.
PAGE 7
5. DSM/SCM EMS Messages (continued) Contents 5.
PAGE 8
5. DSM/SCM EMS Messages (continued) Contents 5.
PAGE 9
5. DSM/SCM EMS Messages (continued) Contents 5.
PAGE 10
5. DSM/SCM EMS Messages (continued) Contents 5.
PAGE 11
5. DSM/SCM EMS Messages (continued) Contents 5.
PAGE 12
5. DSM/SCM EMS Messages (continued) Contents 5. DSM/SCM EMS Messages (continued) 6025 7000 5-149 5-150 6. EMS Messages From Other Subsystems BACKUP and Tape Reader Messages 0001 6-1 0002 6-2 0003 6-2 0004 6-3 0005 6-3 0006 6-4 0007 6-4 0008 6-5 0009 6-5 0010 6-6 0011 6-6 SYSGEN Message 6-6 0001 6-6 6-1 7. File-System Errors 8. BACKUP Errors Tables Table i. Table 5-1. Table 5-2. Table 7-1. Table 8-1.
PAGE 13
What’s New in This Manual Manual Information DSM/SCM Messages Manual Abstract This manual provides cause, effect, and recovery information for messages and errors that you might encounter while using the Distributed Systems Management/Software Configuration Manager (DSM/SCM). Product Version DSM/SCM G02 DSM/SCM H02 Supported Release Version Updates (RVUs) This publication supports J06.03 and all subsequent J-series RVUs, H06.
PAGE 14
Changes to the G06.27 Manual What’s New in This Manual page 5-41, 5370 on page 5-144, 5371 on page 5-145, 5372 on page 5-145, and 5373 on page 5-146. • Updated the description of event messages 2047 on page 5-21, 2161 on page 5-37, 5350 on page 5-142, and 5360 on page 5-143. Changes to the G06.27 Manual • • DSM/SCM EMS message 4285 was added. INITENV messages was added.
PAGE 15
About This Manual This manual provides cause, effect, and recovery information, as relevant, for messages and errors that you might encounter while using the Distributed Systems Management/Software Configuration Manager (DSM/SCM). What Is DSM/SCM? The Distributed Systems Management/Software Configuration Manager (DSM/SCM) is a tool for managing and configuring software installation on distributed target systems. For information about using DSM/SCM, see the DSM/SCM User’s Guide.
PAGE 16
What’s in This Manual About This Manual What’s in This Manual Table i. Summary of Contents Section Title This section lists . . . 1 INITENV Messages Messages issued by INITENV and suggests a corrective action for each message. 2 Target Interface Messages Messages issued by the Target Interface and suggests a corrective action for each message.
PAGE 17
Notation Conventions About This Manual 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.
PAGE 18
General Syntax Notation About This Manual { } Braces. A group of items enclosed in braces is a list from which you are required to choose one item. The items in the list can be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: LISTOPENS PROCESS { $appl-mgr-name } { $process-name } ALLOWSU { ON | OFF } | Vertical Line.
PAGE 19
Notation for Messages About This Manual a blank line. This spacing distinguishes items in a continuation line from items in a vertical list of selections. For example: ALTER [ / OUT file-spec / ] LINE [ , attribute-spec ]… Notation for Messages This list summarizes the notation conventions for the presentation of displayed messages in this manual. Bold Text. Bold text in an example indicates user input typed at the terminal. For example: ENTER RUN CODE ?123 CODE RECEIVED: 123.
PAGE 20
Notation for Management Programming Interfaces About This Manual either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: obj-type obj-name state changed to state, caused by { Object | Operator | Service } process-name State changed from old-objstate to objstate { Operator Request. } { Unknown. } | Vertical Line.
PAGE 21
Change Bar Notation About This Manual Change Bar Notation Change bars are used to indicate substantive differences between this revision of the manual and the preceding revision. Change bars are vertical rules placed in the right margin of changed portions of text, figures, tables, examples, and so on. Change bars highlight new or revised information. For example: The message types specified in the REPORT clause are different in the COBOL85 environment and the Common Run-Time Environment (CRE).
PAGE 22
Change Bar Notation About This Manual DSM/SCM Messages Manual—529845-006 xviii
PAGE 23
1 INITENV Messages This section describes the warning and error messages issued by INITENV and by the stages INITENV performs during its initialization processing: Stage Description Page INITTMF Initializes the HP NonStop Transaction Management Facility (TMF) environment 1-11 INITSQL Initializes the SQL environment 1-14 INITHDB Creates the host database 1-18 INITTDB Creates the target system database 1-21 INITPATH Configures and coldstarts a DSM/SCM Pathway environment 1-23 STARTSCM Sta
PAGE 24
INITENV Messages INITENV Messages INITENV Messages These errors are related to the initialization of the DSM/SCM environment: CLEANOSS is about to remove all the DSM/SCM target work files from the OSS environment. This will not affect the current set of installed files. If you are unsure, you can run CLEANOSS with the LISTONLY option to list the files that will be removed. Cause. A user ran the CLEANOSS macro. Effect. All DSM/SCM target work files are removed from the OSS environment. Recovery.
PAGE 25
INITENV Messages INITENV Messages INITENV ERROR: A required file, filename, does not exist. INITENV cannot proceed. Cause. The indicated internal file, required by INITENV, is missing. Effect. INITENV terminates. Recovery. Create the required file, possibly by copying it from a correct source. Then rerun INITENV. INITENV ERROR: File system error error-number occurred on file filename. Please correct the problem then run INITENV again. Cause.
PAGE 26
INITENV Messages INITENV Messages INITENV: INITENV either cannot create its log file, filename, or it cannot open it, due to file error error-number on file-name. The log file is used to provide a record of this INITENV session, but INITENV will operate correctly without a log. Do you wish to continue without a log file (Y/N)? Cause. A file-system error occurred when INITENV tried to open the log file. Effect. INITENV pauses and lets you indicate whether or not you want to continue without a log file.
PAGE 27
INITENV Messages INITENV Messages INITENV ERROR: Invalid [[\system.]$vol.]subvol entered. Please retry. Cause. The file name you entered does not exist or has an incorrect format. Effect. INITENV pauses and lets you enter a new file name. Recovery. Enter a valid file name using standard NonStop naming conventions. INITENV ERROR: RSC must be installed and configured before DSM/SCM can be installed. Please install RSC then run INITENV again. Cause.
PAGE 28
INITENV Messages INITENV Messages INITENV ERROR: The entered value is not a valid local volume name, or the volume is not accessible, or it does not exist. Please retry. Cause. You entered the name of a volume for the host database that cannot be accessed, does not exist, or is not local to the host system. The host database must be on a volume that is local to the host system. Effect. INITENV pauses and lets you enter a new volume name. Recovery. Enter a valid volume name.
PAGE 29
INITENV Messages INITENV Messages INITENV ERROR: The entered value is not a valid volume name, or the volume is not accessible, or it does not exist. Please retry. Cause. You entered the name of a volume that cannot be accessed or does not exist. Effect. INITENV pauses and lets you reenter the volume name. Recovery. Enter the name of a valid volume. Check that the volume is mounted on the target system. INITENV ERROR: The entered volume is on a system that has not had DSM/SCM installed on it.
PAGE 30
INITENV Messages INITENV Messages INITENV ERROR: This IP Port number is in use by the service defined on line n in the file filename. Please choose a different IP Port number (must be the same number specified in SETUP on the PC). Cause. The IP port number you entered is in use. This message lists the name of the file and the line number that define the service using the IP port number. Effect. INITENV pauses and lets you enter a new IP port number. Recovery.
PAGE 31
INITENV Messages INITENV Messages INITENV ERROR: This question requires that you enter either "Y" for Yes or "N" for No. Please retry. Cause. You entered a value other than Y or N. Effect. INITENV pauses and lets you reenter the value. Recovery. Enter Y if your response is yes or N if your response is no. INITENV ERROR: The required DSM/SCM file, INITSEGF, is not located in the current subvolume. INITENV cannot proceed. Cause.
PAGE 32
INITENV Messages INITENV Messages INITENV WARNING: INITENV is unable to PROGID the DSM/SCM filename because you are not currently logged on as the super ID. Unless PROGID is manually set to the super ID, some intervention by the super ID will be required when build tools or distributed files require licensing. Cause. This informational message appears if you are not logged on as the super ID (255,255).
PAGE 33
INITTMF Errors INITENV Messages INITTMF Errors These errors are related to the initialization of the TMF environment in DSM/SCM: INITTMF ERROR: DSM/SCM has not been installed on \system (TMF has not been initialized). That system may not be used for a remote DSM/SCM database until DSM/SCM has been installed on it. Please install DSM/SCM first, or choose another system to use for a remote database; then run INITENV again. Cause.
PAGE 34
INITTMF Errors INITENV Messages INITTMF ERROR: The entered volume name is not accessible or does not exist. Please retry. Cause. You entered the name of a volume that either does not exist or is not mounted. Effect. INITENV pauses and lets you reenter the volume name. Recovery. Enter the name of the volume that is mounted on the current system. INITTMF ERROR: The requested database volume, $volume, is not enabled for audit on \system.
PAGE 35
INITTMF Errors INITENV Messages INITTMF ERROR: TMF has been configured but is not active. INITTMF will not start a TMF subsystem it did not initialize. Please start TMF, or take other appropriate action, then run INITENV again. Cause. INITENV tried to initialize and start the TMF subsystem on a local system but found that the subsystem had already been configured and was not running. INITENV does not attempt to start an existing TMF subsystem. Effect. INITENV stops. Recovery.
PAGE 36
INITSQL Messages INITENV Messages INITSQL Messages These errors are related to the initialization of HP NonStop SQL/MP in the DSM/SCM environment: INITSQL ERROR: DSM/SCM has not been installed on \system. (SQL has not been initialized). That system may not be used for a remote DSM/SCM database until DSM/SCM has been installed on it. Please install DSM/SCM there first, or choose another system to use for a remote database, then run INITENV again. Cause.
PAGE 37
INITSQL Messages INITENV Messages INITSQL ERROR: File error error-number occurred while duplicating $systemload-vol.SYSTEM.ZZSQLCI2. Please correct the problem, then run INITENV again. Cause. The indicated file-system error occurred when INITENV tried to create a backup copy of the ZZSQLCI2 file. Effect. INITENV stops. Recovery. For a description of the error code displayed in this message, see Section 7, File-System Errors. Correct the file-system error; then rerun INITENV.
PAGE 38
INITSQL Messages INITENV Messages INITSQL ERROR: The entered volume name is not accessible or it does not exist or it is not on the same system as was chosen for the DSM/SCM database. Please retry. Cause. The volume you select for the system catalog must be mounted on the same system being used for the database. Effect. INITENV pauses and lets you reenter the volume name. Recovery. Enter a valid volume name. INITSQL ERROR: The files, SORT and/or SORTPROG, were found in the on $systemload-vol.SYSTEM.
PAGE 39
INITSQL Messages INITENV Messages INITSQL ERROR: TMF has been configured, but it is not active. Please start TMF, or take other appropriate action, then run INITENV again. Cause. The TMF subsystem has been configured but not started on the local system. INITENV does not create a database on a local system if the TMF subsystem is not active on that system. Effect. INITENV stops. Recovery. Use TMFCOM or your normal operational procedures to start the TMF subsystem; then rerun INITENV.
PAGE 40
INITHDB Messages INITENV Messages INITSQL ERROR: Unable to access remote database system \system, due to file system error error-number. Please correct the problem, then run INITENV again. Cause. The indicated file-system error occurred when INITENV tried to initialize a database on a remote system. Effect. INITENV stops. Recovery. For a description of the error code displayed in this message, see Section 7, File-System Errors. Correct the file-system error; then rerun INITENV.
PAGE 41
INITHDB Messages INITENV Messages INITHDB ERROR: FUP reported file system error error-number while setting progid on file filename to userid userid. Please correct the problem, then run INITENV again. Cause. Certain internal programs must be run by the super ID (255,255). A file-system error occurred when INITENV called FUP to set the PROGID for the indicated file. This error might be accompanied by additional details. Effect. INITENV stops. Recovery.
PAGE 42
INITHDB Messages INITENV Messages INITHDB ERROR: SQLCOMP terminated abnormally without reporting an error. This may have been caused by a failure of the SQLCOMP cp or by an internal error in SQLCOMP or by a similar problem. Please correct the problem, if possible, then run INITENV again. Contact Tandem support for assistance, if needed. Cause. An internal error occurred during the compilation of the host database. Effect. The compile stops, and INITENV stops. Recovery.
PAGE 43
INITTDB Messages INITENV Messages INITTDB Messages These errors are related to the initialization of the target database: INITTDB ERROR: FUP reported file system error error-number while setting progid on file filename to userid userid. Please correct the problem, then run INITENV again. Cause. Certain internal programs must be run by the super ID (255,255). A file-system error occurred when INITENV called FUP to set the PROGID for the indicated file. This error might be accompanied by additional details.
PAGE 44
INITTDB Messages INITENV Messages INITTDB ERROR: Unable to access the remote system, due to file system error error-number. Please correct the problem or choose another system, then run INITENV again. Cause. A file-system error occurred while INITENV was trying to access the remote system. Effect. INITENV stops. Recovery. For a description of the error code displayed in this message, see Section 7, File-System Errors. Correct the file-system error; then rerun INITENV.
PAGE 45
INITPATH Messages INITENV Messages INITPATH Messages These errors are related to the initialization of the Pathway environment in DSM/SCM: INITPATH ERROR: DSM/SCM Pathmon process, $YPHI, has already been started, but not by this INITPATH function. If another user is executing INITPATH, do not attempt to restart INITENV. (Only one user should be running INITENV at a time.) Otherwise, use Pathcom to SHUTDOWN the $YPHI Pathway subsystem, then run INITENV again. Cause.
PAGE 46
STARTSCM Messages INITENV Messages INITPATH ERROR: File system error error-number occurred while attempting to open file filename. Please correct the problem, then run INITENV again. Cause. A file-system error occurred while INITENV was trying to open the indicated internal file. Effect. INITENV stops. Recovery. For a description of the error code displayed in this message, see Section 7, File-System Errors. Correct the file-system error; then rerun INITENV.
PAGE 47
STARTSCM Messages INITENV Messages STARTSCM ERROR: File system error error-number occurred while attempting to open file filename. Please correct the problem, then run STARTSCM again. Cause. A file-system error occurred while INITENV was trying to open a required internal file. Effect. INITENV stops. Recovery. For a description of the error code displayed in this message, see Section 7, File-System Errors. Correct the file-system error; then rerun INITENV.
PAGE 48
VERIFYI Messages INITENV Messages STARTSCM: TCP/IP and its LISTNER process do not appear to be running from the current SYSnn subvolume. They must be running to allow communication between the Planner Interface and this Host. Start TCP/IP and its LISTNER process before using the Planner Interface. Cause. STARTSCM cannot find TCP/IP and its LISTNER process using the program files on the current SYSnn subvolume. Effect. DSM/SCM issues this message. Recovery.
PAGE 49
VERIFYI Messages INITENV Messages VERIFYI ERROR: The required DSM/SCM Host System TDP process is not running. Please run STARTSCM to start all processes. Cause. The DSM/SCM host transaction delivery process (TDP) must be running in order to run DSM/SCM. However, INITENV found that the host TDP is not running. Effect. You cannot run DSM/SCM. Recovery. Run the DSM/SCM startup file STARTSCM. STARTSCM starts all processes that DSM/SCM requires.
PAGE 50
VERIFYI Messages INITENV Messages DSM/SCM Messages Manual—529845-006 1- 28
PAGE 51
2 Target Interface Messages Warning and Error Messages These messages appear at the bottom of the Target Interface screens: item not found or invalid format, expected expected-format. Cause. You have incorrectly entered a spooler, tape, or disk location. Effect. DSM/SCM displays the expected format. Recovery. Depending on the screen, enter the correct information: If you are on this screen... Enter a correct... and press...
PAGE 52
Warning and Error Messages Target Interface Messages Audit process is running. Only cancel is allowed. Cause. An audit request is already running. Effect. DSM/SCM warns that you have already submitted an Audit request, and the request is still being processed. Recovery. You can press F6 to cancel the Audit. Otherwise, you can perform no additional activities until the Audit finishes. Cannot begin another activity until the current one completes. Cause. A request is already running for this target. Effect.
PAGE 53
Warning and Error Messages Target Interface Messages Could not process request. Review EMS messages for further information. Cause. An internal DSM/SCM error occurred. Effect. DSM/SCM stops in a nonrestartable state. Recovery. If you are on the Logon screen, press Shift-F16 to exit DSM/SCM. On all other screens: 1. If F4-Show messages is not available on the screen, press F16 until you are back to the main menu. 2. Press F4 to display the EMS messages for this request. 3.
PAGE 54
Warning and Error Messages Target Interface Messages Error in communicating with the Inventory Collector process. Cause. There is no copy of the Inventory Collector on the ZSOFTWAY subvolume. Effect. You cannot continue in the Target Interface. Recovery. Place a copy of the Inventory Collector (x9299rrr.
PAGE 55
Warning and Error Messages Target Interface Messages Invalid selection number. Cause. You entered an invalid selection number. Effect. DSM/SCM issues this message and waits for you to enter a valid selection. Recovery. Depending on the screen, enter the correct information: If you are on this screen... Enter a selection number... and press F1 to...
PAGE 56
Warning and Error Messages Target Interface Messages No more items to list. Cause. You pressed Page Up or Page Down, but there are no previous or additional items (targets, subvolumes, messages, or instructions) to list. Effect. DSM/SCM warns that you are at the beginning or end of a list. Recovery. Informational message only; no corrective action is needed. No previous SYSnn available. Cannot BACKOUT or GET PREVIEW. Cause. No previous configuration exists for this target.
PAGE 57
Warning and Error Messages Target Interface Messages The audit process has stopped. Either cancel or restart request. Cause. Either you canceled the Audit to perform another activity, or a problem occurred. Effect. The audit request stops in a restartable state. Recovery. If you canceled the Audit and now want it to resume processing, press F3 to restart the request. If a problem occurred, review the EMS messages issued by the Audit request to determine why the request stopped.
PAGE 58
Status Messages Target Interface Messages Task submitted and is being processed. Cause. DSM/SCM submitted a batch task. Effect. You can now perform another task. Recovery. Informational message only; no corrective action is needed. Trace already enabled and an output location already exists. Cause. You have already enabled Trace for the selected modules. Effect. Depending on the module enabled, the trace output is being written to a location shown either on the screen or in a message in the EMS log.
PAGE 59
Status Messages Target Interface Messages Cancelled. Cause. An operator pressed F6 to cancel the request. Effect. DSM/SCM cancels the request. Recovery. Informational message only; no corrective action is needed. Cancel processing stopped in restart state. Cause. A problem occurred while DSM/SCM was processing a cancel request issued by an operator. Effect. DSM/SCM stops in a restartable state. Recovery. Restart the cancel request: 1. Press F4 to view the EMS messages for this request. 2.
PAGE 60
Status Messages Target Interface Messages Complete with errors. Cause. The request finished processing, but errors occurred. Effect. DSM/SCM displays this message. Recovery. Submit this or a new request: 1. Press F4 to view the EMS messages for this request. 2. Correct any problems if necessary. 3. Submit the request again or start a different request. Complete with warnings. Cause. The request finished processing, but warning messages were issued. Effect. DSM/SCM displays this message. Recovery.
PAGE 61
Status Messages Target Interface Messages Processing stopped in non-restartable state. Cause. A problem occurred while DSM/SCM was processing the request. Effect. DSM/SCM stops in a nonrestartable state. Recovery. Fix the problem and resubmit the request: 1. Press F4 to view the EMS messages for this request. 2. Correct the problems, exiting DSM/SCM if necessary. 3. Use the Maintenance Interface (ZPHITMI) to delete the request from the system. 4. After the problem is corrected, submit the request again.
PAGE 62
Status Messages Target Interface Messages DSM/SCM Messages Manual—529845-006 2- 12
PAGE 63
3 Archive and Database Maintenance Interface Messages These warning and error messages are displayed on the Maintenance Interface screens: An internal error has occurred. SF16 to exit application. Cause. An internal DSM/SCM error occurred. Effect. The requested activity stops in a nonrestartable state. Recovery.
PAGE 64
Archive and Database Maintenance Interface Messages Cannot delete or deny access to the last DB Administrator. Cause. You are trying to delete the last database administrator allowed to change security settings; or only one database administrator record exists, and you have indicated that this administrator is not allowed to change security settings. Effect. DSM/SCM issues this warning and does not delete the database administrator. Recovery.
PAGE 65
Archive and Database Maintenance Interface Messages • • • Descriptions of the problem and accompanying symptoms Details from the messages generated Supporting documentation such as the $ZPHI Event Management Service (EMS) logs and trace files (if requested by your service provider) If your local operating procedures require contacting the Global Customer Support Center (GCSC), supply your system number and the numbers and versions of all related products as well. DSM/SCM found duplicate in database.
PAGE 66
Archive and Database Maintenance Interface Messages Error on writing to archive volume. Cause. An error occurred while a software input was being restored. Effect. The requested activity stops in a nonrestartable state. Recovery. Review the Event Management Service (EMS) messages that the restore process issued, correct the problem that caused the error; then resubmit the restore request. Error reading tape during restore. See EMS events for details. Cause.
PAGE 67
Archive and Database Maintenance Interface Messages FROM volume has no DSM/SCM archive subvolumes. Cause. While trying to either relocate the archive or estimate the disk space required to do so, you entered the name of a volume that does not contain any DSM/SCM archive subvolumes. Effect. DSM/SCM issues this warning. Recovery. Enter the name of a volume that contains DSM/SCM subvolumes in the Relocate Archive from field; then press either F1 to relocate the archive or F5 to estimate the disk space.
PAGE 68
Archive and Database Maintenance Interface Messages Internal error. Error code: code. code-text Cause. An internal DSM/SCM error occurred. Effect. DSM/SCM stops in a nonrestartable state. Recovery. Note the error number; then press Shift-F16 to exit from the Maintenance Interface. Use this list of error codes to determine the cause of the error.
PAGE 69
Archive and Database Maintenance Interface Messages Code Meaning (page 2 of 4) 224 The UFN flag value is not a known value. 225 A calling function has passed a request type that is an unknown or invalid value. 226 There is an inconsistency in an activity record for a function. The activity code does not match a valid activity code for the function. 227 The check of status codes in an array of activity records failed. The status code passed does not match a status code in any of the activity records.
PAGE 70
Archive and Database Maintenance Interface Messages Code Meaning (page 3 of 4) 271 An attempt to convert an external resource name to an internal resource name failed during Object Manager trace processing. 272 An attempt to create a file to be used for an Object Manager trace failed because the trace processing routine could not find an unused file name in the range ZZOM0000 through ZZOM9999. 273 An error of an unknown type occurred while trying to generate a trace error message.
PAGE 71
Archive and Database Maintenance Interface Messages Code Meaning (page 4 of 4) 501 An unexpected error (probably a Guardian error) occurred during an archive relocation operation. 502 An error occurred while trying to create the archive directory file during a software input backup request processing. 503 An error occurred while trying to delete old archive files during the processing of an archive relocation request. 504 A MALLOC request failed.
PAGE 72
Archive and Database Maintenance Interface Messages Invalid action; expected checked out SW Input Name. Cause. You entered a character in a Selection field that is not next to the name of a software input. Effect. DSM/SCM issues this warning. Recovery. Enter a character in the Selection field of a line that contains a software input name; then press F4. Invalid action; expected checked out System Name. Cause. You entered a character in a Selection field that is not next to the name of a system profile.
PAGE 73
Archive and Database Maintenance Interface Messages Invalid field format; expected 1, 2, 3, or ' ' (blank). Cause. You entered an invalid selection number. Effect. DSM/SCM issues this warning. Recovery. Enter one of the valid Usage Flag values shown in the message; then press Shift-F2 to modify the volume. Invalid field format; expected 1, 2, 3, or 4. Cause. You entered an invalid selection number. Effect. DSM/SCM issues this warning. Recovery.
PAGE 74
Archive and Database Maintenance Interface Messages Invalid field format; expected 1 through 10, or 99. Cause. You entered an invalid selection number. Effect. DSM/SCM issues this warning. Recovery. Enter a selection number from 1 through 10, or 99; then press F1 to select the activity. Invalid field format; expected \system. Cause. You entered an invalid system name. Effect. DSM/SCM issues this warning. Recovery. Enter a valid system name in the indicated field before pressing a function key.
PAGE 75
Archive and Database Maintenance Interface Messages Invalid field format; expected N if Build security is N. Cause. You indicated that the planner could perform Build/Apply requests but denied the ability to perform Build requests. Effect. DSM/SCM issues this warning. Recovery. Change either the Build access or the Build/Apply access so that both fields contain the same value (Y or N). Invalid field format; expected numeric field. Cause. You entered an invalid site ID or number of days to retain requests.
PAGE 76
Archive and Database Maintenance Interface Messages Invalid field format; expected value in field. Cause. You did not enter a value in the specified field. Effect. DSM/SCM issues this warning. Recovery. Depending on the screen, enter the correct information: If you are on this screen... Enter a correct... and press...
PAGE 77
Archive and Database Maintenance Interface Messages Invalid field format; expected value in Selection field. Cause. You did not enter a value in the Selection field. Effect. DSM/SCM issues this warning. Recovery. Depending on the screen, enter the correct information: If you are on this screen... Enter a character in the... and press...
PAGE 78
Archive and Database Maintenance Interface Messages Logon successfully verified. Cause. DSM/SCM verified your user ID and password. Effect. You successfully logged on to the Maintenance Interface. Recovery. Informational message only; no corrective action is needed. Multiple inputs have this name. Use PI to rename duplicates. Cause. The archive contains more than one input with this name. Effect. DSM/SCM issues this warning. Recovery. Rename this input so that it has a unique name: 1.
PAGE 79
Archive and Database Maintenance Interface Messages No Software Input is currently checked out. Cause. You selected 3 on the Check-out Cancellation Management Menu, but no software input is currently checked out. Effect. DSM/SCM issues this warning. Recovery. Informational message only; no corrective action is needed. No Target System Profile is currently checked out. Cause. You selected 2 on the Check-out Cancellation Management Menu, but no system profile is currently checked out. Effect.
PAGE 80
Archive and Database Maintenance Interface Messages Pathway error. See error log and Pathway manual. Cause. DSM/SCM detected a Pathway error. Effect. Depending on the error, the request stops in either a restartable or a nonrestartable state. Recovery. Review the messages on your Pathway hometerm to determine the problem. For the appropriate action, see the error messages section of the TS/MP Pathsend and Server Programming Manual. Press F6- Delete again to delete the object. Cause.
PAGE 81
Archive and Database Maintenance Interface Messages Specified software input name not in archive directory. Cause. DSM/SCM could not find the software input name you entered. Effect. DSM/SCM issues this warning. Recovery. Check that you spelled the input name correctly and that the correct tape containing the input has been mounted; then resubmit the request.
PAGE 82
Archive and Database Maintenance Interface Messages Task successfully completed. Run STOPSCM, then STARTSCM. Cause. The request finished processing. Effect. This message prompts you to shut down and restart DSM/SCM. Recovery. Informational message only. Run the STOPSCM program; then run the STARTSCM program. Task successfully completed. Trace file: trace-filename Cause. Trace has been enabled. Effect. Output from the trace is written to the indicated file. Recovery.
PAGE 83
Archive and Database Maintenance Interface Messages User ID or password invalid. Cause. You entered an invalid user ID or password. Effect. You cannot log on. Recovery. Enter a valid NonStop user ID (groupname.username) and password; then press F1 to log on. User is not secured for this task. Cause. You do not have the authority to performed the selected task. Effect. DSM/SCM does not let you perform the task. Recovery.
PAGE 84
Archive and Database Maintenance Interface Messages DSM/SCM Messages Manual—529845-006 3- 22
PAGE 85
4 ZPHIRNM Messages ZPHIRNM Messages ZPHIRNM issues these types of error and warning messages: Message Type Issued When Syntax error ZPHIRNM encounters a syntax error on a RUN ZPHIRNM command. Termination ZPHIRNM terminates, either successfully or with errors. General error and warning An error occurs during ZPHIRNM’s renaming of files. Undo TSV processing An error occurs while ZPHIRNM is attempting to back out target subvolume (TSV) changes following a fatal error.
PAGE 86
Termination Messages ZPHIRNM Messages Termination Messages Termination messages are issued when ZPHIRNM terminates, either normally or because of errors. The termination message is written to the OUT file and to the log file, if one exists. Some of the messages refer to a file named ZSSLIST. This file contains a list of the TSVs that ZPHIRNM is to process. For termination caused by error or warning conditions, additional details are written to the log file. ZPHIRNM [preview] for SYSnn.
PAGE 87
Termination Messages ZPHIRNM Messages ** E01/E02 ZPHIRNM has detected that an APPLY activity is in progress for this system (according to a flag in filename). ZPHIRNM should not be run while an APPLY is in progress. O - Override, E - Exit, ? - More info [E]: Cause. A flag in the ZPHISYS file indicates that an Apply is in progress. You should not run ZPHIRNM during an Apply. Effect. ZPHIRNM prompts you to override this error, to exit ZPHIRNM, or to request more information. (The default is to exit.
PAGE 88
File Error and Warning Messages ZPHIRNM Messages File Error and Warning Messages ZPHIRNM issues fatal, nonfatal, and warning messages if problems occur while renaming individual files. Fatal messages are written to the OUT file and to the log file if one was specified. Nonfatal and warning messages are written to the log file if one was specified. Otherwise, they are written to the OUT file. Fatal error error-number occurred on file filename during description processing for SYSnn. Cause.
PAGE 89
File Error and Warning Messages ZPHIRNM Messages • Supporting documentation such as the $ZPHI Event Management Service (EMS) logs and trace files (if requested by your service provider) If your local operating procedures require contacting the Global Customer Support Center (GCSC), supply your system number and the numbers and versions of all related products as well. $vol.subvol.mapfile is not a valid [map file | ZPHIFI]: incorrect file structure. Processing for this subvolume has been aborted. Cause.
PAGE 90
File Rename Error and Warning Messages ZPHIRNM Messages File Rename Error and Warning Messages ZPHIRNM maintains an internal record of files as they exist under their temporary and real names. This internal record is kept in these files: Guardian File OSS File Description subvolume.ZPHIFI .dsmscm.ZPHIFI This file contains a list of all files on the subvolume as last processed. These are the current files until ZPHIRNM is run again. subvolume.ZMPnnnn .dsmscm.ZMPnnnn nnnn is a 4-digit number.
PAGE 91
Correcting Rename Errors ZPHIRNM Messages ** E05 Data files indicate a rename to filename is not needed, but file error error-number was returned from a FILEINFO check of the last modification time of this file. I - Ignore, A - Ignore all, R - Retry, U - Undo TSV, ? - More info [U]: Cause. An error occurred while checking the existence and last modification time of the specified file. Effect.
PAGE 92
Correcting Rename Errors ZPHIRNM Messages ** E07 Required file filename has the wrong last modification time. Actual : real-mod-time Expected: expected-mod-time I - Ignore, A - Ignore all, R - Retry, U - Undo TSV, ? - More info [U]: Cause. The specified file was expected only in its real name because the file version is the same in the previous configuration and the configuration being activated.
PAGE 93
Correcting Rename Errors ZPHIRNM Messages ** E09 Required file filename missing. Data files indicate a rename of fab-name to real-name is not needed, but fab-name is not present and real-name is present with the wrong last modification time. I - Ignore, A - Ignore all, R - Retry, U - Undo TSV, ? - More info [U]: Cause. The specified file was expected only in its real name because the file version is the same in the previous configuration and the configuration being activated.
PAGE 94
Correcting Rename Errors ZPHIRNM Messages ** E11 Required file filename has wrong last mod. time. Actual : real-mod-time Expected: expected-mod-time Data files indicate a rename of fab-name to real-name is not needed, but both files exist and both have the wrong last modification time. I - Ignore, A - Ignore all, R - Retry, U - Undo TSV, ? - More info [U]: Cause.
PAGE 95
Correcting Rename Errors ZPHIRNM Messages this error in this run of ZPHIRNM. You can also use the file with the fabricated name and continue. Otherwise, undo the processing performed on this TSV and continue with the next TSV. This TSV is marked as incomplete and can be reprocessed later. ** E13 Required file real-filename(fab-filename) missing. Expected last modification time: expected-mod-time Data files indicate a rename of fab-name to real-name is needed, but neither file exists.
PAGE 96
Correcting Rename Errors ZPHIRNM Messages ** E15 Required file real-filename(fab-filename) missing. Data files indicate a rename of fab-name to real-name is needed, but fab-filename is missing and realfilename is present with an incorrect last modification time. Actual : real-mod-time Expected: expected-mod-time I - Ignore, A - Ignore all, R - Retry, U - Undo TSV, ? - More info [U]: Cause.
PAGE 97
Correcting Rename Errors ZPHIRNM Messages ** E17 Required file real-filename(fab-filename) has wrong mod. time. Actual : real-mod-time Expected: expected-mod-time Data files indicate a rename of fab-name to real-name is needed, but fab-filename has the wrong last modification time. I - Ignore, A - Ignore all, R - Retry, U - Undo TSV, ? - More info [U]: Cause.
PAGE 98
Correcting Rename Errors ZPHIRNM Messages undo the processing performed on this TSV and continue with the next TSV. This TSV is marked as incomplete and can be reprocessed later. ** E19 error error-number was returned from a FILEINFO check of filename. Continuing as if file doesn’t exist. Cause. The specified error was returned when checking the specified file. Effect. ZPHIRNM continues, ignoring the specified file. Recovery. Determine why the error occurred and correct the problem.
PAGE 99
Correcting Rename Errors ZPHIRNM Messages of the configuration and continue with the next file in the TSV, ignore this error or ignore all occurrences of this error in this run of ZPHIRNM. Otherwise, undo the processing performed on this TSV and continue with the next TSV. This TSV is marked as incomplete and can be reprocessed later. If RENAME error 82 is reported, the file is an SQL program file and cannot be renamed unless TMF is running. Make sure TMF is running, then select the Retry option.
PAGE 100
Correcting Rename Errors ZPHIRNM Messages If RENAME error 82 is reported, the file is an SQL program file and cannot be renamed unless TMF is running. Check that TMF is running, then select the Retry option. ** E24 SYSnn is not the Current Configuration. filename is the filename according to the filename file. ZPHIRNM can only be run to rename the Current Configuration. O - Override, E - Exit ? - More info [E]: Cause. The specified SYSnn is not the current configuration. Effect.
PAGE 101
Correcting Rename Errors ZPHIRNM Messages ** E26 RENAME error error-number on file filename. Data files indicate a rename of fab-name to real-name and fab-name to real-name is needed. I - Ignore, A - Ignore all, R - Retry, U - Undo TSV, ? - More info [U]: Cause. The specified file was expected in its real and fabricated names because a different version of this file is part of the previous configuration.
PAGE 102
Correcting Rename Errors ZPHIRNM Messages ** E28 OPEN error error-number occurred on map file filename. This TSV can not be renamed unless this map file can be opened. S - Skip TSV, R - Retry, E - Exit, ? - More info [E]: Cause. The specified map file could not be opened for this TSV. The map file contains required information on the files in the TSV for the configuration being activated. Effect. The TSV cannot be activated.
PAGE 103
Correcting Rename Errors ZPHIRNM Messages Cause. The specified file was expected in the real name and fabricated name because the version of the file changed between the previous configuration (fromcnfg) and the configuration being activated (to-cnfg). No files exist in the fabricated name.
PAGE 104
Correcting Rename Errors ZPHIRNM Messages Recovery. Retrieve the file from the DSM/SCM archive. Place the new file in fabricated filename and select the Retry option. To leave the wrong version of the file in place if it exists and continue with the next file in the TSV, ignore this error or ignore all occurrences of this error in this run of ZPHIRNM. Otherwise, undo the processing performed on this TSV and continue with the next TSV. This TSV is marked as incomplete and can be reprocessed later.
PAGE 105
Correcting Rename Errors ZPHIRNM Messages Cause. The specified file was expected in real name and fabricated name because the version of the file changed between the previous configuration (from-cnfg) and the configuration being activated (to-cnfg). The file in real name has the wrong last modification time. No files exist in fabricated name. Both from-cnfg fabricated file and to-cnfg fabricated file have the same fingerprints, but different last modification time and fabricated names. Effect.
PAGE 106
Correcting Rename Errors ZPHIRNM Messages W01 Warning: FILEINFO error on file filename Unable to verify LMT on file. Continuing. Data files indicate a rename of fab-name to real-name, and fab-name to real-name is needed. It appears that these renames have already been done because real-name and real-name exist, but fab-name does not exist. This is unexpected but it is not a problem. The files will be kept as they are. Cause. A FILEINFO error occurred on the specified file.
PAGE 107
Correcting Rename Errors ZPHIRNM Messages Cause. The specified file has a different last modification time than expected. Effect. This file belongs to the previous configuration only, so it does not prevent the successful activation of the configuration. Recovery. Informational message; no corrective action is required. W05 Warning: Data files indicate a rename of fab-name (strict) to real-name is not needed, but real-name is not present and fab-name is present with the correct modification time.
PAGE 108
Correcting Rename Errors ZPHIRNM Messages Effect. Because the file is obsolete, the rename not occurring has no impact. Recovery. Informational message; no corrective action is required. W09 Warning: Expected file filename to be in real name but (strict) was found in fabricated name(fab-name) instead. This is unexpected but it is not a problem. Cause. The specified file was found in its fabricated name instead of its real name, which was expected instead. Effect. Because the file is present, it is used.
PAGE 109
Correcting Rename Errors ZPHIRNM Messages W13 Warning: Obsolete file, filename, could not be renamed because it is missing. Cause. The specified obsolete file could not be renamed because it was not found. Effect. Because the file is obsolete, the rename not occurring has no impact. Recovery. Informational message; no corrective action is required. W14 Warning: FILEINFO error on open file filename. Unable to verify LMT on file. Continuing. Cause.
PAGE 110
Correcting Rename Errors ZPHIRNM Messages W17 Warning: Data files indicate a rename of fab-name (strict) to real-name is needed but both files exist. real-name has the correct last modification time. fab-name has the wrong last modification time. Actual : real-mod-time Expected: expected-mod-time This is unexpected but it is not a problem. The real-name file will be used. Cause. For a file that needs to be renamed, files already exist that use both the real and fabricated file names.
PAGE 111
Correcting Rename Errors ZPHIRNM Messages W20 Warning: Data files indicate a rename of fab-name (strict) to real-name, and fab-name to real-name is needed. It appears that these renames have already been done because real-name and real-name exist, but fab-name does not exist. This is unexpected but it is not a problem. The files will be kept as they are. Cause. ZPHIRNM found that the specified files already exist in their real names, which was not expected. Effect.
PAGE 112
Correcting Rename Errors ZPHIRNM Messages W24 Warning: Wrong last modification time for real-name(fab-name) (strict) Actual : real-mod-time Expected: expected-mod-time Cause. The specified file has a different last modification time than expected, possibly because the file changed. Effect. This file belongs to the previous configuration only, so it does not prevent the successful activation of the configuration. Recovery. Informational message; no corrective action is required.
PAGE 113
Correcting Rename Errors ZPHIRNM Messages W27 Warning: Obsolete file, filename, could not be renamed because of file OPEN error error-number. Cause. The specified obsolete file could not be renamed because the specified OPEN error occurred. Effect. Because the file is obsolete, the rename not occurring has no impact. Recovery. Informational message; no corrective action is required. W28 Warning: Obsolete file, filename, could not be renamed because of file RENAME error error-number. Cause.
PAGE 114
Correcting Rename Errors ZPHIRNM Messages W31 Warning: filename was an unmanaged file that was adopted and is now managed. Received error error-number while attempting to record this in the from-config map file. If a backout is done, this file will not be kept in real name. ZPHIRNM will rename this file to fab-name. Cause. ZPHIRNM cannot add a record to the from-config map file. Effect. If a backout is performed, this file is not restored to its original name. Recovery.
PAGE 115
Other Rename Messages ZPHIRNM Messages Other Rename Messages Other messages might be displayed during the rename process. Undo TSV or TDL Processing Messages If a nonfatal error occurs while processing a target subvolume (TSV) or target directory location (TDL), ZHPIRNM tries to restore the TSV or TDL to its original state.
PAGE 116
Volume Name Validation Messages ZPHIRNM Messages Volume Name Validation Messages Before ZPHIRNM begins processing, it checks the volume containing the target subvolumes (TSVs). These messages might be issued during this check: Both volume1 and volume1 have the same primary and alternate volume names. ZPHIRNM is unable to determine which volume to use. Cause. If primary and alternate volume names are used, DSM/SCM requires that at least one of the names in each pair be unique.
PAGE 117
Volume Name Validation Messages ZPHIRNM Messages ZPHIRNM can’t find label information for either volume1 or volume2. Cause. ZPHIRNM attempted to rename the files on a volume but could not find the volume label information for either the primary or alternate volume names. There is probably an error on the disk volume. Effect. ZPHIRNM terminates. Recovery. Correct the disk error; then rerun ZPHIRNM.
PAGE 118
EMS Event Generation Messages ZPHIRNM Messages EMS Event Generation Messages When an error occurs during an attempt to create an EMS message, ZPHIRNM issues these messages: SPI error spi-error occurred while invoking spi/ems function. Zphirnm is unable to issue the EMS termination message. Cause. An error occurred when ZPHIRNM attempted to create an EMS termination message.
PAGE 119
Log-File-Related Messages ZPHIRNM Messages Log-File-Related Messages Unable to write message to log file logfile due to file error error-number. Cause. A file-system error occurred when ZPHIRNM tried to write a message to the log file. Effect. ZPHIRNM continues processing but does not write the message to the log file. Recovery. For a description of the error indicated by error-number, see the Guardian Procedure Errors and Messages Manual.
PAGE 120
Log-File-Related Messages ZPHIRNM Messages DSM/SCM Messages Manual—529845-006 4- 36
PAGE 121
5 DSM/SCM EMS Messages The messages in this section are sent to $ZPHI by DSM/SCM. You can view operator messages using the: • Planner Interface, which lets you display the Event Management Service (EMS) messages generated during the processing of a request. To display the EMS messages for a request on the Planner Interface: 1. Select Requests>Requests list.... 2. Select a request name. 3. Select Show EMS events... (or click Status details..., then click Show EMS events...).
PAGE 122
1000 DSM/SCM EMS Messages 1000 file-type files(s) is/are located at filename. file-type is the type of file whose location is being reported. Typical values returned and the file types they represent are: Activation package Report file System snapshot Target file Trace file For a complete list of possible file-type values, see 5095 on page 5-117. filename is the file name in the internal format of the file whose location is being reported. Cause.
PAGE 123
1010 DSM/SCM EMS Messages 1010 activity-name completed completion-code. activity-name is the activity that just completed execution by DSM/SCM.
PAGE 124
1015 DSM/SCM EMS Messages 1015 Snapshot needed for host host-name to correct Apply error. Run Target Interface and select CREATE SNAPSHOT activity. host-name is the host name where the error occurred. Cause. An error occurred during an Apply activity. A target system snapshot must be input at the host to synchronize the host and target. Effect. The host cannot complete the Apply activity. Recovery. Run the Target Interface and select the Create Snapshot activity to produce a current system snapshot.
PAGE 125
1025 DSM/SCM EMS Messages non restartable. Correct error, CANCEL activity The DSM/SCM activity stopped because of an error and cannot be restarted. The activity must therefore be cancelled. cancelled restartable. Correct error, RESTART activity A planner or operator cancelled the activity. The activity stopped while it was being cancelled. It can be restarted after the error condition is corrected. cancelled non restartable. Correct error, CANCEL activity A planner or operator cancelled the activity.
PAGE 126
2000 DSM/SCM EMS Messages The problem might be within DSM/SCM, or it might be a PATHMON configuration error. 2000 Error returned from SWID utility, p-error, s-error on filename. Correct the error and RESTART the activity. p-error is the P error value. For possible P error values that can be returned and brief descriptions of their meanings, see Table 5-1. s-error is the S error value. For possible S error values that can be returned and brief descriptions of their meanings, see Table 5-1.
PAGE 127
2005 DSM/SCM EMS Messages 2005 File error file-error with description utility-error returned from utility utility-name, during action-name on file-type, filename. Correct error, if necessary, or Contact HP. RESTART activity. file-error is the file-system error that occurred. File-system errors are defined in Section 7, File-System Errors. utility-error is the error text from the utility server. utility-name is the name of the utility where the file-system error occurred.
PAGE 128
2010 DSM/SCM EMS Messages 2010 Error proc-name error-code returned from SWARC. SWARC failed to compress/decompress file. Contact HP. proc-name is the name of the procedure where the error occurred. error-code is the error code returned by the Software Archive (SWARC) utility. For SWARC error codes, see the Software Identification (SWID) User’s Guide. Cause. The SWARC utility could not compress or decompress a file. Effect. The activity stops in a nonrestartable state. Recovery.
PAGE 129
2015 DSM/SCM EMS Messages 2015 Specified file-type file filename on medium has incorrect error-entity. Ensure filename is correct and created by DSM/SCM. Otherwise, save file, CANCEL activity. Contact your HP representative. file-type is the file type of the file where the error occurred. Possible values: Activation Package Archive File System Snapshot filename is the file name in the internal format of the file where the error occurred. medium is the type of medium where the error occurred.
PAGE 130
2017 DSM/SCM EMS Messages 2017 You specified a snapshot file filename created at a target target-name not managed by this host host-name. Ensure you have the correct medium for this host. filename is the file name in the internal format of the system snapshot file. target-name is the node name of the target contained in the snapshot file. This target is not managed by this host. host-name is the node name of this host. medium is the type of medium where the error occurred.
PAGE 131
2020 DSM/SCM EMS Messages 2020 Correctable database error db-error-num. SQL/data base manager returned db-error-buf. Correct error. RESTART activity. db-error-num is the SQL error code that identifies the error. For SQL error codes, see the SQL/MP Messages Manual. Some common values are described here. db-error-buf contains the structured query language communications area (SQLCA) error text passed from SQL/MP. Cause. A database error occurred that caused DSM/SCM to stop processing. Effect.
PAGE 132
2020 DSM/SCM EMS Messages 23 DB_ERR_BEGIN_TRANSACTION_FAILED Cannot begin a transaction. Check the TMF status for errors. 38 DB_ERR_UNABLE_TO_RET_TARGETS_DEFINE The transaction tag passed to the database manager does not match the tag that corresponds to the transaction that this database manager process started. -8300 SQL/MP encountered a file-system error. The file-system error and a one-line description are displayed as part of db-error-buf.
PAGE 133
2030 DSM/SCM EMS Messages 2030 error-type file-error on action-name of file/process filename. If error type is Warning, decide upon corrective action. If error type is Restartable, correct error and RESTART activity. error-type indicates whether the error is restartable or a warning. Possible values: Restartable error Warning file-error is the file-system error that occurred. For file-system error definitions, see Section 7, File-System Errors.
PAGE 134
2031 DSM/SCM EMS Messages If the error is a warning, the operator or planner might need to decide if corrective action is needed. If the error is restartable, correct the error and restart the activity. If the filename was $EMSLOGF.ILEERROR, the server process could not send an EMS message out to the DSM/SCM EMS collector. Instead, this error was reported back to the Schedule Manager on behalf of the server that could not send out the message.
PAGE 135
2032 DSM/SCM EMS Messages filename is the program name in the internal format of the process where the error occurred. Cause. A warning or restartable file error occurred during the specified procedure or action. Effect. If the error is a warning, the activity continues processing. If the error is restartable, the activity stops in a restartable state. Recovery. Check the file-system error code in the message. For a definition of the specified error, see Section 7, File-System Errors.
PAGE 136
2033 DSM/SCM EMS Messages Cause. A warning or restartable error occurred during the specified procedure or action. Effect. For a warning, the activity continues processing. For a restartable error, the activity stops in a restartable state. Recovery. Check the OSS file-system error code in the message. For a definition of the specified error and recovery actions, see the Open System Services System Calls Reference Manual.
PAGE 137
2034 DSM/SCM EMS Messages filename is the file name in the internal format of the file where the error occurred. Cause. A warning or restartable file error occurred during the specified procedure or action. Effect. If the error is a warning, the activity continues processing. If the error is restartable, the activity stops in a restartable state. Recovery. Check the file-system error code in the message. For a definition of the specified error, see Section 7, File-System Errors.
PAGE 138
2035 DSM/SCM EMS Messages DSC SPI command CONFIG DSC SPI command LISTDEV EDITREAD EDITREADINIT FILEINFO FILEINQUIRE FUP Dup NEWPROCESS NEXTFILENAME Safeguard access check Safeguard command ADD FILE Safeguard command DELETE FILE SETMODE STOP TAPEMOUNT UNLOCK WRITE WRITEREAD filename is the file name in the internal format of the file where the error occurred. Cause. A warning or restartable file error occurred during the specified procedure or action. Effect.
PAGE 139
2040 DSM/SCM EMS Messages 2040 Memory allocation error. RESTART the activity. If the error persists, contact your HP representative. Cause. A memory allocation error occurred. Effect. The activity stops in a restartable state. Recovery. Restart the activity.
PAGE 140
2046 DSM/SCM EMS Messages process stopped processing the activity (if the server stops with errors). If the server process stops with errors, the activity stops in a restartable state. Recovery. The recovery procedure depends on the returned value of the server completion code: • • • If the server process completes the activity successfully, this is an informational message only. No corrective action is needed.
PAGE 141
2047 DSM/SCM EMS Messages filename is the file name of the output file for the server process. This file might contain more information about the errors or warnings. Cause. A server process completed an activity for DSM/SCM. The activity completed successfully, with warnings, or with errors. Effect.
PAGE 142
2050 DSM/SCM EMS Messages 2050 PATHSEND link down, processing terminated. Correct any associated error(s). RESTART the activity. Cause. A PATHSEND link that DSM/SCM uses was down. Effect. The activity stops in a restartable state. Recovery. Determine why the link is down or unavailable, correct any associated errors, and restart the activity when the link is available. For Pathsend error definitions, see the TS/MP Pathsend and Server Programming Manual.
PAGE 143
2057 DSM/SCM EMS Messages 2057 Cannot create unique name for file-type file in directory TDL-name. Delete unneeded files. RESTART activity. file-type is the file type of the affected file. For this event message, the value is always OSS map file. TDL-name is the target directory location name where the problem occurred. Cause. DSM/SCM could not create a unique name for a file because of a problem with the cleanup of a previous DSM/SCM activity. The needed filename is .dsmscm.
PAGE 144
2065 DSM/SCM EMS Messages 2065 Existence check on file-type file filename received error file-error. file-type is the file type of the file that could not be found. Typical returned values are: Activation Package System Snapshot SYSGEN Input Product File Target File Tool File For a complete list of the possible file-type values, see the description of message 5095 on page 5-117. filename is the file name in the internal format of the file that could not be found.
PAGE 145
2066 DSM/SCM EMS Messages 2066 Existence check on file-type OSS file filename received error file-error. Ensure filename is correct and file has not been removed, renamed, or deleted. file-type is the file type of the file that could not be found. For this event message, the type is always OSS target file. filename is the file name in the internal format of the OSS file that is missing or has an unexpected last modification time. file-error is the OSS file-system error that occurred.
PAGE 146
2070 DSM/SCM EMS Messages 2070 Server class parameter missing or invalid: parameter parameter-name, value parameter-value. Planner must correct Pathway configuration to correct parameter. parameter-name is the name of the server class parameter that is missing or invalid. parameter-value is the value of the server class parameter that is invalid. If the server class parameter is missing, the value of this parameter is null. Cause.
PAGE 147
2075 DSM/SCM EMS Messages 2075 file-type file filename on medium contains invalid data. Correct the error and RESTART the activity. file-type is the file type of the file. Possible values: Activation Package System Snapshot Target File filename is the filename in the internal format of the file. medium is the type of medium where the error occurred. Possible values: disk tape Cause. The specified file contains invalid data.
PAGE 148
2080 DSM/SCM EMS Messages 2080 Error file-error renaming file from current-filename to proposed-filename. Contact security administrator or Planner if problem is a security or user error. file-error is the file-system error that is returned. For file-system error definitions, see Section 7, File-System Errors. current-filename is the current file name in the internal format of the file. proposed-filename is the proposed new file name in the internal format of the file. Cause.
PAGE 149
2085 DSM/SCM EMS Messages Effect. The activity stops in a restartable state. Recovery. Check the OSS error code in the message. For a definition of the specified error, see the Open System Services System Calls Reference Manual. If the error resulted from a security problem at your site, the security administrator should correct the problem. If the error resulted from a user purging the file, contact the planner. 2085 filename is incorrectly specified.
PAGE 150
2095 DSM/SCM EMS Messages 2095 Pathway configuration error. Server class server-class-name, PATHMON pmon-name must run on host-name node. server-class-name is the name of the Pathway server class that is running on an incorrect node. pmon-name is the name of the PATHMON process associated with the Pathway server class. host-name is the host name of the node where the Pathway server class should be running. Cause. A Pathway server class was running on the incorrect node.
PAGE 151
2101 DSM/SCM EMS Messages 2101 An empty ZDLLrrr[a] subvolume to place public DLLs in could not be found. An empty public-dll-subvolume[A-Z] subvolume could not be found to place public DLLs in. Remove or rename one or more of these subvolumes and restart the Apply. public-dll-subvolume is the fully qualified subvolume name that DSM/SCM uses to create a new target subvolume (TSV) for public DLLs. Cause. All 27 possible subvolumes already exist. Effect. The Apply stops restartable. Recovery.
PAGE 152
2110 DSM/SCM EMS Messages 2110 filename needs to be licensed before activity can proceed. RESTART the activity after the file has been licensed. filename is the file name in the internal format of the file that is not licensed. Cause. The activity could not proceed because it required the use of a program file that was not licensed. Effect. The activity stops in a restartable state. Recovery. License the file and restart the activity. 2115 Invalid username user-name.
PAGE 153
2125 DSM/SCM EMS Messages Cause. The specified user-ID is assigned to a file but does not have a defined group-name member-name. Running USERS group-ID,member-ID will return "NO SUCH USERS WERE FOUND." for this user-ID. This is usually caused by a file being copied to a system from another system Effect. The activity stops in a restartable state. Recovery. Find the files that are owned by this user-ID with the FUP INFO $*.*.*,OWNER user-ID command.
PAGE 154
2140 DSM/SCM EMS Messages 2140 file-type file filename on media-type has incorrect version. Expected version: version-1 or lower. Actual version: version-2. Current internal DSM/SCM version: version-3. This file was created by a later version of DSM/SCM who believes our Internal DSM/SCM version is later than indicated. CANCEL Apply, Perform an Independent Snapshot, and repeat the Build/Apply. file-type is the type of file—always an activation package file for this message.
PAGE 155
2150 DSM/SCM EMS Messages Effect. The request stops in a restartable state. A version of ZPHIUTL might be available to downgrade these activation package files to an appropriate version that this target system can read. Recovery. Check if the ZPHIUTL program on the host system can convert the activation package file to a lower version, using the CONVERT command. If so, convert the file to a lower version and restart the activity.
PAGE 156
2150 DSM/SCM EMS Messages updated before this Build/Apply. (To avoid this, when you lower the DSM/SCM PVU on a host, perform a Build/Apply immediately to update the target database before the next snapshot is requested.) Effect. The request stops in a restartable state. Recovery. You have two options: • • Upgrade the host to the version of the target, then restart the receive snapshot request. On the target system, try to use the ZPHIUTIL CONVERT command to convert the snapshot file to a lower version.
PAGE 157
2161 DSM/SCM EMS Messages 2161 DSM/SCM requires version server-program-version or later of server file-name. The current server appears to be an earlier version. Manually put a new version of the server in place, and restart the activity. server-program-version indicates the required minimum PVU of SWID; for example, T9298AAJ. file-name is the fully qualified external server program file name. For example: \NODE.$SYSTEM.SYSTEM.SWID Cause.
PAGE 158
2163 DSM/SCM EMS Messages 2163 WARNING: Clone target target-name_logical-target-name specifies undefined system name as its master: clone-text. target-number is the system name of the target defined as a clone. logical-target-name is the logical target name of the target system defined as a clone. clone-text is either the valid system name specified as the master or a portion of the logical target description text and error text describing the problem. Cause.
PAGE 159
2164 DSM/SCM EMS Messages 2164 WARNING: Clone target target-name_logical-target-name specifies master master-name that does not have a target by this name. target-name is the system name of the target defined as a clone. logical-target-name is the logical target name of the target system defined as a clone. master-name is the system name of the master target. Cause. The target description text for this target contains “CLONE \system”.
PAGE 160
2165 DSM/SCM EMS Messages 2165 WARNING: Clone target target-name_logical-target-name specifies Master master-name which is not defined as a master. target-name is the system name of the target defined as a clone. logical-target-name is the logical target name of the target system defined as a clone. master-name is the system name of the master target. Cause. The target description text for this target contains “CLONE \system”.
PAGE 161
2166 DSM/SCM EMS Messages 2166 WARNING: Clone group targets have different CPU types: target-name_logical-target-master is master-cpu-type, hostname_logical-target-clone is clone-cpu-type. target-name is the system name of the target defined as a master. logical-target-master is the logical target name of the target system defined as a master. master-cpu-type is the processor type of the master. host-name is the system name of the clone target in the same clone group.
PAGE 162
2997 DSM/SCM EMS Messages 2997 Internal error error-num, error-buf. error-num is the internal error code that identifies the error. For possible values and brief descriptions of their meanings, see Table 5-2, DSM/SCM Internal Error Codes in EMS Messages, on page 5-47. error-buf is a buffer containing additional information associated with the error. The contents of this buffer vary based on error-num. For a brief description of the contents of this token, see Table 5-2 on page 5-47. Cause.
PAGE 163
2998 DSM/SCM EMS Messages 2998 Fatal data base error db-error-num. SQL/data base manager returned db-error-buf. Contact your HP representative. db-error-num is the SQL error code that occurred. For SQL error code descriptions (indicated by a negative number or 100), see the SQL/MP Messages Manual. db-error-buf contains the structured query language communication area (SQLCA) error text passed from SQL/MP. Cause. An SQL error occurred that caused DSM/SCM to stop processing. Effect.
PAGE 164
2998 DSM/SCM EMS Messages 11 DB_ERR_NOT_FOUND The object does not exist in the database. 13 DB_ERR_INCORRECT_ACTION_CODE The action code for the transaction is incorrect. 14 DB_ERR_ALREADY_CHECKED_OUT The object has already been checked out by the user. 15 DB_ERR_ALREADY_EXISTS The object already exists in the database. 16 DB_ERR_CHECKED_OUT_BY_DIFF_USER The object has already been checked out by a different user.
PAGE 165
2998 DSM/SCM EMS Messages 31 DB_ERR_UNABLE_TO_OPEN_CURSOR An error occurred while DSM/SCM was trying to open an SQL cursor. 32 DB_ERR_GET_TRANSID_FAILED An error occurred while DSM/SCM was trying to obtain a TMF transaction ID. 33 DB_ERR_SUSPEND_TRANSACTION_FAILED An error occurred while DSM/SCM was performing a suspend transaction. 34 DB_ERR_TOO_MANY_RECORDS The number of records that the database manager returned is greater than the number of records that the response buffer can accommodate.
PAGE 166
2998 DSM/SCM EMS Messages 56 DB_ERR_CKOUT_NO_CKR The variant is checked out, but there is no associated checker variant. 58 DB_ERR_NOT_CHECKED_OUT The object has not been checked out. 62 DB_ERR_WRONG_USAGE_STATE An internal error occurred. Most likely the database has been corrupted. 66 DB_ERR_DIFFERENT_NODE In the list of files passed by the inventory collector, one of the files has a different node name than the others.
PAGE 167
2999 DSM/SCM EMS Messages 2999 Internal error internal-error, internal-error-buf. internal-error is the internal error code that identifies the error. For possible values and brief descriptions of their meanings, see Table 5-2, DSM/SCM Internal Error Codes in EMS Messages, on page 5-47. internal-error-buf is a buffer containing additional information associated with the error. The contents of this buffer vary based on the value of internal-error.
PAGE 168
2999 DSM/SCM EMS Messages Table 5-2.
PAGE 169
3000 DSM/SCM EMS Messages 3000 Specified snapshot file is not most recent for target-name. Not processed. target-name is the node name of the target that received the outdated file. Cause. An outdated system snapshot file was received at a host. Effect. The specified system snapshot file is not processed. Recovery. Informational message only; no corrective action is needed. 3005 The DSV subvolume-name does not contain A0CINFO file.
PAGE 170
3006 DSM/SCM EMS Messages 3006 The DSV subvolume-name does not contain A1CINFO file. DSV skipped, processing continues. subvolume-name is the name of the distribution subvolume (DSV) where the error occurred. Cause. The specified DSV did not contain an A1CINFO file, or the A1CINFO file has an incorrect file code. Effect. The activity finishes with warnings. The DSV is not processed as part of the current input. Recovery. A new DSV must be generated. Contact the product vendor.
PAGE 171
3007 DSM/SCM EMS Messages 3007 The DSV subvolume-name has an entry in the A0CINFO file for A7CINFO file, which is not present in the DSV. DSV skipped, processing continues. subvolume-name is the name of the distribution subvolume (DSV) where the error occurred. Cause. The A7CINFO file was removed from the DSV after the A0CINFO file was generated. Effect. The activity finishes with warnings. The DSV is not processed as part of the current input. Recovery. A new DSV must be generated.
PAGE 172
3008 DSM/SCM EMS Messages 3008 pax archive file pax-filename in DSV DSV-name contains invalid file filename. File in /G or /E are not allowed. DSV skipped, processing continues. pax-filename is the pax archive file that contains the invalid file record. DSV-name is the name of the DSV where the error occurred. filename is the name of the invalid OSS file. Cause. The A7CINFO file contains a record for an OSS file that is in the /G or /E directory. DSM/SCM does not support OSS files in these directories.
PAGE 173
3009 DSM/SCM EMS Messages 3009 pax archive file pax-filename in DSV DSV-name contains invalid file filename which has an OSS file type other than Regular File, Directory, Symbolic Link, Hard Link, or FIFO. DSV skipped, processing continues. pax-filename is the pax archive file that contains the invalid file record. DSV-name is the name of the DSV where the error occurred. filename is the name of the invalid OSS file. Cause.
PAGE 174
3010 DSM/SCM EMS Messages 3010 The DSV subvolume-name file filename has no entry in A0CINFO. Planner must use CNFGINFO tool to update A0CINFO file for DSV and bring it into DSM/SCM as a separate input, then assign two inputs to the same Input Group. DSV skipped, processing continued. subvolume-name is the name of the distribution subvolume (DSV) where the error occurred. filename is the file name in the internal format of the DSV file that is not listed in the A0CINFO file. Cause.
PAGE 175
3011 DSM/SCM EMS Messages 3011 pax archive file pax-filename in DSV DSV-name contains duplicate records for file filename. DSV skipped, processing continues. pax-filename is the pax archive file that contains the duplicate file records. DSV-name is the name of the DSV where the error occurred. filename is the name of the invalid OSS file. Cause. The A7CINFO file contains two records for the same OSS file. Effect. The activity finishes with warnings.
PAGE 176
3012 DSM/SCM EMS Messages 3012 pax archive file pax-filename in DSV DSV-name contains invalid file filename with a relative path name. Relative path names are not allowed by DSM/SCM. DSV skipped, processing continues. pax-filename is the pax archive file that contains the invalid file record. DSV-name is the name of the DSV where the error occurred. filename is the name of the invalid OSS file. Cause.
PAGE 177
3013 DSM/SCM EMS Messages 3013 pax archive file pax-filename is missing from the A0CINFO file in DSV DSV-name. According to the A0CINFO file, paxfilename contains OSS file filename. DSV skipped, processing continues. pax-filename is the pax archive file that contains the invalid file record. DSV-name is the name of the DSV where the error occurred. filename is the name of the invalid OSS file. Cause.
PAGE 178
3014 DSM/SCM EMS Messages 3014 pax archive file pax-filename in DSV DSV-name is not placed in the ZOSSUTL TSV. According to the A7CINFO file, paxfilename contains OSS file filename. DSV skipped, processing continues. pax-filename is the pax archive file that contains the invalid file record. DSV-name is the name of the DSV where the error occurred. filename is the name of the invalid OSS file. Cause. The pax archive file, referred to by records in the A7CINFO file, must be placed in the ZOSSUTL TSV.
PAGE 179
3015 DSM/SCM EMS Messages 3015 The DSV subvolume-name has an entry in the A0CINFO file for the file filename, which is not in the DSV. DSV skipped, processing continues. subvolume-name is the name of the distribution subvolume (DSV) where the error occurred. filename is the file name in the internal format of the missing file. Cause. The A0CINFO file had an entry for a file that was not in the DSV. Effect. The activity finishes with warnings. The DSV is not processed as part of the current input.
PAGE 180
3016 DSM/SCM EMS Messages 3016 A7CINFO file format error error occurred on record number record of pax archive file pax-filename in DSV DSV-name. OSS file name is oss-filename. DSV skipped, processing continues. error is one of these A7CINFO format errors: • • • 1: The pax archive file specified in the record should be in the form: /G/dsmscm/md100ga7/t8100px1. No ‘/’ characters were found in this field. 2: The OSS filename in the variable length record should be in the form: dir1/dir2/file.
PAGE 181
3020 DSM/SCM EMS Messages If your local operating procedures require contacting the Global Customer Support Center (GCSC), supply your system number and the numbers and versions of all related products as well. 3020 Invalid A0CINFO file detected in DSV subvolume-name. DSV processing skipped. subvolume-name is the name of the distribution subvolume (DSV) with the invalid A0CINFO file. Cause. You attempted to input a DSV, but the DSV contained an invalid A0CINFO file.
PAGE 182
3022 DSM/SCM EMS Messages 3022 The A0CINFO file in DSV dsv-name is version 3, which this version of DSM/SCM cannot read. Processing of this DSV stopped. Upgrade to a newer DSM/SCM version and retry your request. dsv-name is the name of the distribution subvolume (DSV) with the version 3 A0CINFO file. Cause. DSM/SCM tried to input a DSV containing a product that uses a version 3 A0CINFO file. The DSM/SCM PVU you are running cannot read version 3 A0CINFO files. Effect.
PAGE 183
3030 DSM/SCM EMS Messages 3030 The A a-site-id subvolume subvolume-name has invalid/missing RLSEID/CUSTFILE files. Contact HP. a-site-id is the name of the first subvolume on the site update tape (SUT). subvolume-name is the name of the subvolume containing the invalid files. Cause. You attempted to input a SUT with invalid or missing RLSEID or CUSTFILE files. Effect. The activity stops in a restartable state. Recovery.
PAGE 184
3032 DSM/SCM EMS Messages 3032 A Receive-All-Files software input is in progress. No other software inputs can be received or cancelled until the Receive-All-Files software input completes. Restart this request after the Receive-All-Files software input completes. Cause. A software input request was started while a Receive-All-Files software input request was already being processed. Effect. DSM/SCM cannot process the input. Recovery.
PAGE 185
3045 DSM/SCM EMS Messages 3045 Specified software input name input-name already exists. Specify another name and process the input again. input-name is the name specified for the software input. Cause. You specified a software input name that already exists. Effect. The activity finishes with errors. DSM/SCM does not process the input. Recovery. Start a new activity, specify a different software input name, and process the input again. 3050 Duplicate product in software input.
PAGE 186
3060 DSM/SCM EMS Messages 3060 The DSV DSV-name has an inconsistent A0CINFO file. File filename has an incorrect file size. DSV-name is the name of a distribution subvolume (DSV) in the software input. filename is the name of the A0CINFO file in the DSV. Cause. The actual file size of the filename file was different from the file size specified in the A0CINFO file itself. Effect. The activity stops in a restartable state. Recovery. Fix the A0CINFO file and restart the activity, or cancel the activity.
PAGE 187
3070 DSM/SCM EMS Messages 3070 The DSV DSV-name has an A1CINFO file with an unknown file format version. A more recent version of DSM/SCM is required to receive this software. DSV-name is the name of a distribution subvolume (DSV) in the software input. Cause. The format of the A1CINFO file in this DSV is not readable by this DSM/SCM PVU. Information included in the A1CINFO file might cause the format of the file to change in the future. Effect. The receive software request stops in a restartable state.
PAGE 188
3080 DSM/SCM EMS Messages 3080 WARNING: The DSV DSV-name requires the Capability-name capability to be installed correctly. The Product-version and later versions of DSM/SCM have this capability. If this DSV can not be received then the Product-version or later version of DSM/SCM must be used to receive this software. DSV-name is the name of the distribution subvolume (DSV) in the software input. Capability-name is the name of the capability required.
PAGE 189
4010 DSM/SCM EMS Messages 4010 Error file-error accessing scratch volume volume-name. Correct problem indicated in error. RESTART activity. file-error is the file-system error that occurred. For file-system error definitions, see Section 7, File-System Errors. volume-name is the name of the scratch volume that could not be accessed. Cause. DSM/SCM could not access the specified scratch volume on the target scratch list. Effect. The activity stops in a restartable state. Recovery.
PAGE 190
4020 DSM/SCM EMS Messages 4020 Current database information for operator activation instructions out of sync with request information. Cause. The Configuration Builder and the Planner Interface received conflicting database information regarding operator activation instructions. Possibly a new system snapshot has been received, the CONFTEXT file has been changed, or database corruption has occurred. Effect. The activity finishes with errors. Recovery. Try to start a new Build or Build/Apply activity.
PAGE 191
4031 DSM/SCM EMS Messages 4031 product-file contains OSS files DSM/SCM and OSS files that will pax file filename is one of the contains OSS files that will be that will be managed by not be managed by DSM/SCM. pax archive files that managed by DSM/SCM. product-file is the product number that is partially OSS-enabled for DSM/SCM. filename is the name of one of the pax archive files that DSM/SCM will install the OSS files from. Cause.
PAGE 192
4033 DSM/SCM EMS Messages 4033 The following OSS products either have unprocessed A7CINFO files, or contain non-pax files in ZOSSUTL: product-list. To process the A7CINFO files, re-receive these products into the archive using the Receive All Files option. Use CNFGINFO to remove any non-pax files from ZOSSUTL. CANCEL Build. Perform another Build request. product-list is one or more product numbers. Cause.
PAGE 193
4040 DSM/SCM EMS Messages 4040 WARNING: SRL mismatch, num1 relocatable files versus num2 executable files. num1 is the number of shared run-time library (SRL) relocatable files in the configuration. num2 is the number of SRL executable files in the configuration. Cause. The number of SRL relocatable files does not match the number of SRL executable files. Effect. The Build continues. This configuration might have a problem with its SRL files. Recovery.
PAGE 194
4060 DSM/SCM EMS Messages 4060 WARNING: The file SRL-exec-file from product Product-version is an SRL executable file for which no corresponding SRL executable was built by DSM/SCM. The file will not be placed. SRL-exec-file is an SRL executable file. Product-version is the product version for the SRL executable file. Cause. This product did not release an SRL relocatable file that DSM/SCM could use to build a corresponding SRL executable. Effect. The Build continues. Recovery.
PAGE 195
4080 DSM/SCM EMS Messages 4080 The number of SRL relocatable and ZTILT files, num1, does not match the number of SRL executable and ZTILT files, num2, that were built by DSM/SCM. num1 is the number of SRL relocatable files. num2 is the number of SRL executable files produced from the Build. Cause. The SRL build was not successful. For each SRL relocatable, one SRL executable and one ZTILT file should be produced. Effect. The Build stops nonrestartable. Recovery.
PAGE 196
4100 DSM/SCM EMS Messages 4100 The SRL executable file SRL-exe-file referred to in the SRL log file could not be found in the build subvolume subvolname. SRL-exe-file is the name of the SRL executable file indicated in the NSKCOM output file ZASRL*.SRLBLDOF. subvolname is the name of the SRL build subvolume where the SRL executable files were built. Cause. This file was not found in the Build subvolume. It should have been created by the SRL build. Effect. The Build stops nonrestartable. Recovery.
PAGE 197
4110 DSM/SCM EMS Messages 4110 server-process completed server-completion-code. Examine server warning(s)/error(s) in file log-file, correct error(s) if necessary, RESTART activity if stopped in a restartable state. server-process is NSKCOM. server-completion-code is the server completion status of the activity. Possible values: with error(s) Server completed activity with errors. successfully Server completed activity successfully. with warning(s) Server completed activity with warnings.
PAGE 198
4116 DSM/SCM EMS Messages 4116 A set of public dynamic-link libraries (DLLs) is being built for the reason indicated. Public DLL build required because: reason. reason is the reason a public DLL build is required. Possible values: • • • • • • FORCE-PUBLIC-DLL-BUILD parameter specified Never been built ZIMPIMP changed ZCOBDLL (T1234) added ZCOBDLL (T1234) removed ZCOBDLL (T1234) changed Cause. A public DLL build was required for the reason indicated. Effect. The set of public DLLs is built. Recovery.
PAGE 199
4130 DSM/SCM EMS Messages 4130 Invalid SRL executable name in the SRL build output file Filename in the build subvolume Subvolname. Filename is the name of the SRL build output file created during the SRL build. Subvolname is the name of the subvolume where the SRL build output file is located. Cause. An inconsistency occurred in the SRL build output file. The expected executable name was not there or contained too many characters. Effect. The Build stops nonrestartable. Recovery.
PAGE 200
4150 DSM/SCM EMS Messages 4150 The SRL ZTILT source file does not exist. Cause. DSM/SCM is attempting to build the SRL executable files. A ZTILT source file is required to build but cannot be found in the configuration. The ZTILT source file should be supplied as file TPRETILT in product T7898. This can occur if: • • The ZTILT source file was not included in the configuration properly, or A product that releases SRLs has incorrectly released an A1CINFO file on a SUT that does not support SRL builds.
PAGE 201
4152 DSM/SCM EMS Messages 4152 Executable shared-runtime libraries (SRLs) were found in the TNS/E configuration. WARNING: Executable SRL found in the TNS/E configuration. SRLs are not valid for a TNS/E configuration. This file will be excluded. The file is srl-file-name (). srl-file-name is the name of the SRL file. product-number is the number of the product. Cause. Executable SRLs were found in a TNS/E configuration. Effect. DSM/SCM ignores these files. Recovery.
PAGE 202
4160 DSM/SCM EMS Messages 4160 WARNING: Internal error. A duplicate Product product-number was found. This product will be processed normally once. The duplicate entry will be ignored. product-number is the number identifier for the duplicated product. Cause. A single product is present in two different inputs. Effect. The second occurrence of the product is discarded. Recovery. This is a warning message. The Build/Apply continues unaffected. No recovery is necessary.
PAGE 203
4171 DSM/SCM EMS Messages 4171 ERROR: A duplicate OSS file was found. Product first-productnumber (first-paxfile) and Product second-product-number (second-paxfile) both place file filename. These two files have different fingerprints or file types. first-product-number is the product number for the first occurrence of the duplicated product. first-paxfile is the name of the pax archive file that contains the OSS file for the first occurrence of the duplicated product.
PAGE 204
4180 DSM/SCM EMS Messages 4180 ERROR: A duplicate file was found. Product first-productnumber and Product second-product-number both place file filename in TSV subvolume-name. These two files have the same fingerprints. One file is used. The duplicate file will be ignored. first-product-number is the number identifier for the first occurrence of the duplicated product. second-product-number is the number identifier for the second occurrence of the duplicated product.
PAGE 205
4181 DSM/SCM EMS Messages 4181 WARNING: A duplicate OSS file was found. Product firstproduct-number (first-paxfile) and Product second-productnumber (second-paxfile) both place file filename. These two files have the same fingerprint. The file from first-productnumber (first-paxfile) will be used. The file from secondproduct-number (second-paxfile) will be ignored. first-product-number is the product number for the first occurrence of the duplicated product.
PAGE 206
4190 DSM/SCM EMS Messages 4190 WARNING: Internal error on read of verification list file. Verification will be partial with regard to restart. Cause. An error occurred reading verified instructions from the restart verification list. Effect. Verification is not performed against the instructions that could not be read from the list file. All instructions left to verify are verified against what was recovered from the list file. Recovery. This is a warning message. No recovery is necessary.
PAGE 207
4220 DSM/SCM EMS Messages 4220 WARNING: Internal error on open of verification list file. A restart will result in partial verification. Cause. An error occurred opening the file for instructions that will be saved for restart. Effect. If a restart occurs before the activation package instructions have all been processed, the remaining instructions cannot be verified against the instructions processed before the restart. Recovery. This is a warning message. No recovery is necessary.
PAGE 208
4250 DSM/SCM EMS Messages 4250 WARNING: You must restore the labeled Activation Tape onto the target system and do the apply from disk. Cause. DSM/SCM finished building a configuration, putting its activation package onto a labeled tape. The Apply process cannot read an activation package directly from a labeled tape. Effect. The activation package cannot be applied until it is restored to disk. Recovery.
PAGE 209
4261 DSM/SCM EMS Messages 4261 Internal Error: DSM/SCM can not find the manufactured ZIMPIMP file in the TNS/E configuration. CANCEL Build. Perform another Build request that requires a sysgen. Cause. The ZIMPIMP file is not found in the TNS/E configuration in the host database. Effect. The Build stops restartable. Recovery. Cancel the Build. Then perform another Build request that requires system generation. You can force system generation by changing the CONFTEXT file with a comment.
PAGE 210
4270 DSM/SCM EMS Messages 4270 Running SYSGEN (with SIT creation). Cause. DSM/SCM is ready to run a system generation program because system generation is required for the Build, and the user has requested a SIT be created. When the message “DSM/SCM COMPLETED FOR DSM/SCM” appears, the SIT creation has completed as well. Effect. Informational message only; no corrective action is needed. Recovery. Informational message only; no corrective action is needed. 4280 Running SYSGEN (because of SIT creation).
PAGE 211
4285 DSM/SCM EMS Messages Cause. The spooler was not available when the Build attempted to spool the CONFLIST. Effect. The Build continues without spooling the CONFLIST file. Recovery. None needed. For future Builds, start the spooler if spooling is required. 4285 Unable to create non-essential activation dial-out report and continuing... Cause. The creation of the activation dial-out report (SWCONFIG) failed. Effect. The activation dial-out report (SWCONFIG) is not created. Recovery.
PAGE 212
4310 DSM/SCM EMS Messages Effect. Informational message only; no corrective action is needed. Recovery. Informational message only; no corrective action is needed.
PAGE 213
5000 DSM/SCM EMS Messages 5000 Error file-error setting GUARDIAN security attributes for filename to OWNER owner-name, PROTECTION protection, PROGID progid, CLEARONPURGE clearonpurge, LICENSE license. Change the GUARDIAN security attributes on the file. RESTART the activity. file-error is the file-system error that occurred. For file-system error definitions, see Section 7, File-System Errors. filename is the file name in the internal format of the file where the error occurred.
PAGE 214
5005 DSM/SCM EMS Messages 5005 Error sfg-error setting SAFEGUARD security attributes for filename like the file like-filename. Change the SAFEGUARD security attributes on the file. RESTART the activity. sfg-error is the Subsystem Programmatic Interface (SPI) error that occurred on a command to the Safeguard subsystem. Safeguard SPI errors are defined in the Safeguard Management Programming Manual. filename is the file name in the internal format of the file whose Safeguard attributes are being set.
PAGE 215
5010 DSM/SCM EMS Messages 5010 TSV volume primary-volume-name alternate-volume-name not online. Verify Database for target-name skipped. Ensure TSVs to verify are online. primary-volume-name is the name of the primary target subvolume (TSV) volume. alternate-volume-name is the name of the alternate TSV volume. target-name is the system name of the target. Cause. A Target Interface request to perform a Verify Database activity included a TSV that was not online.
PAGE 216
5014 DSM/SCM EMS Messages 5014 DSM/SCM will install OSS files for target system-name. system-name is the name of the logical target for which the configuration is being applied. Cause. The Manage OSS Files check box for this target is checked, and the configuration qualifies for OSS file management. Effect. OSS files are installed and managed by DSM/SCM for this logical target. Recovery. Informational message; no corrective action is necessary.
PAGE 217
5020 DSM/SCM EMS Messages 5020 Insufficient disk space exists for APPLY/BACKOUT of configuration config-name. Space required: space-required bytes, space exists: space-exists bytes, volume volume-name. Correct the error by freeing up space on the volume disk. RESTART the activity. config-name is the name of the configuration where the error occurred. space-required is the amount of disk space (in bytes) required to execute the Apply or Backout activity.
PAGE 218
5021 DSM/SCM EMS Messages 5021 DSM/SCM has detected that the new filename file is different (fingerprint) from the file in SYSnn sysnum. The OVERRIDESYSNN param (and possibly OVERRIDE-SYSNN-DIFFERENT-OS params) has been specified to allow the APPLY to go to SYSnn sysnum anyway. The existing file in SYSnn sysnum will be retained. filename is the name of the file manufactured by a system generation program. sysnum is the octal number of the currently executing SYSnn. Cause.
PAGE 219
5023 DSM/SCM EMS Messages 5023 DSM/SCM has detected that the new filename file is different (fingerprint) from the existing filename file in SYSnn sysnum. The OVERRIDE-SYSNN param has been specified to allow the APPLY to go to SYSnn sysnum anyway. However, a change in this file indicates that the OS has really changed. If you specify the OVERRIDE-SYSNN-DIFFERENT-OS param and restart the request, the existing file will not be replaced.
PAGE 220
5024 DSM/SCM EMS Messages 5024 OVERRIDE-SYSNN specified. File filename has changed and will be replaced in the running SYSnn. filename is the name of the file manufactured by a system generation program. Cause. DSM/SCM detected that the new file manufactured by a system generation program is different from the one in the executing SYSnn. OVERRIDE parameters were specified to ignore the difference. Effect. The Apply continues. Recovery. No action is required.
PAGE 221
5026 DSM/SCM EMS Messages 5026 DSM/SCM has detected that the OSIMAGE file is different from the currently executing OSIMAGE file in SYSnn sysnn-num. If you know that the new OSIMAGE file is really the same as the ‘currently executing’ OSIMAGE file, you can force the APPLY to adopt the ‘currently executing’ OSIMAGE by specifying OVERRIDE Pathway params and RESTART the APPLY.
PAGE 222
5027 DSM/SCM EMS Messages 5027 DSM/SCM has detected that the OSIMAGE file is different from the currently executing OSIMAGE file in SYSnn sysnn-num. The OVERRIDE-SYSNN and OVERRIDE-SYSNN-DIFFERENT-OS params have been specified to allow the APPLY to go to SYSnn sysnn-num anyway. The new OSIMAGE file and the ‘currently executing’ OSIMAGE file are different sizes. The ‘currently executing’ OSIMAGE file will be retained. sysnn-num is the octal number of the currently executing SYSnn. Cause.
PAGE 223
5028 DSM/SCM EMS Messages 5028 DSM/SCM has detected that the new OSIMAGE file is different from the currently executing OSIMAGE in SYSnn sysnn-num. The OVERRIDE-SYSNN param has been specified to allow the APPLY to go to SYSnn sysnn-num anyway. However, the current OSIMAGE and new OSIMAGE file are different sizes. If you are sure the two OSIMAGE files are the same version, specify the OVERRIDESYSNN-DIFFERENT-OS param and restart the request.
PAGE 224
5029 DSM/SCM EMS Messages 5029 DSM/SCM has detected that the new OSIMAGE file is different from the currently executing OSIMAGE in SYSnn sysnn-num. The OVERRIDE-SYSNN param has been specified to allow the APPLY to go to SYSnn sysnn-num anyway. The new OSIMAGE file and the currently executing OSIMAGE file are the same size. The ‘currently executing’ OSIMAGE file will be retained. sysnn-num is the octal number of the currently executing SYSnn. Cause.
PAGE 225
5031 DSM/SCM EMS Messages 5031 DSM/SCM has detected that the new OSIMAGE file is same version as the ‘currently executing’ OSIMAGE file in SYSnn sysnn-num. The OVERRIDE-SYSNN param for this configuration is not allowed. Remove the param and restart the request. sysnn-num is the octal number of the currently executing SYSnn. Cause. DSM/SCM detected that the new OSIMAGE file is the same version as the current OSIMAGE file. OVERRIDE-SYSNN parameters are not allowed. Effect. The Apply stops restartable.
PAGE 226
5039 DSM/SCM EMS Messages 5039 According to the /zzDSMSCM.Managed file, target-name manages files in the current OSS environment. target-name does not exist or does not manage OSS files. Run CLEANOSS to remove old DSM/SCM work files from the current OSS environment. target-name is the name of the logical target that had managed OSS files in the current OSS environment. Cause.
PAGE 227
5040 DSM/SCM EMS Messages 5040 DSM/SCM has detected that SYSnn TSV subvolume-name is missing from volume-name. Initialization apply for target target-name cannot proceed. subvolume-name is the name of the missing target subvolume (TSV). volume-name is the name of the volume where the TSV was expected to be located. target-name is the system name of the target where the error occurred. Cause. The specified SYSnn TSV is not present in the list of volumes you supplied. Effect.
PAGE 228
5042 DSM/SCM EMS Messages 5042 OSS file verification for logical target target-name will not be done because that OSS environment is not available(different $SYSTEM disk). target-name is the name of the logical target that manages OSS files. Cause. The OSS environment associated with this logical target is not running. Only the OSS environment associated with the current $SYSTEM can be started. This logical target does not manage the current $SYSTEM volume. Effect.
PAGE 229
5044 DSM/SCM EMS Messages name that manages OSS files will add all DSM/SCM work files for target-name. Clear the Manage OSS Files check box for oss-target if it is checked. If oss-target is supposed to manage OSS files in this OSS environment, clear the Manage OSS Files check box for target-name. The next Apply for target-name removes OSS management from target-name. 5044 The current OSS environment is managed by target oss-target (according to /zzDSMSCM.Managed).
PAGE 230
5046 DSM/SCM EMS Messages 5046 OSS file management is being removed from target target-name. The current OSS environment is not associated with any logical target. target-name is the name of the logical target that manages OSS files according to the DSM/SCM target database. Cause. The /zzDSMSCM.Managed file was removed from the OSS environment for this logical target. Effect. OSS file management is removed for this logical target from the target database and OSS environment.
PAGE 231
5048 DSM/SCM EMS Messages 5048 DSM/SCM has detected that OSS file filename has been removed, or replaced with a different version. The DSM/SCM database will be updated accordingly. filename is the name of the OSS file that is missing or changed. Cause. A target OSS file managed by DSM/SCM was removed or replaced with a different version from its expected directory, or a target OSS directory was removed. Effect. The DSM/SCM database is updated to reflect that the file is missing or changed. Recovery.
PAGE 232
5055 DSM/SCM EMS Messages 5055 TSV volume primary-volume-name alternate-volume-name not online. Apply request cannot proceed. Correct error, RESTART the activity. primary-volume-name is the name of the primary target subvolume (TSV) volume. alternate-volume-name is the name of the alternate TSV volume. Cause. The Apply activity to the specified TSV stopped because the volume was not online. Effect. The Apply activity stops in a restartable state. Recovery.
PAGE 233
5070 DSM/SCM EMS Messages 5070 DSM/SCM has detected that TSV subvolume-name move-action from target-volume-name free-text destination-volume-name. The DSM/SCM database will be updated accordingly. subvolume-name is the name of the target subvolume (TSV) that was moved. move-action is the situation that caused the TSV location change to be reported. Possible values and their meanings are: COPIED A COPY operation occurred. MISSING The TSV is missing. MOVED A MOVE operation occurred.
PAGE 234
5075 DSM/SCM EMS Messages 5075 DSM/SCM has detected that TSV file filename has been removed, or replaced with a different version, from expected subvolume subvolume-name. The DSM/SCM database will be updated accordingly. filename is the name of the file that has been removed. subvolume-name is the name of the expected subvolume location. Cause. A target file managed by DSM/SCM has been removed or replaced with a different version from its expected volume and subvolume location. Effect.
PAGE 235
5085 DSM/SCM EMS Messages 5085 DSM/SCM cannot continue processing your request. Two disk volumes may not have the same primary and alternate name pair primary-volume-name alternate-volume-name. Ensure that you have labelled the disks correctly. primary-volume-name is the name of the primary volume that is being shared. alternate-volume-name is the name of the alternate volume that is being shared. Cause.
PAGE 236
5090 DSM/SCM EMS Messages 5090 File filename with fingerprint fingerprint does not exist at target on TSV tsv-name. filename is the name of the missing file. fingerprint is the file fingerprint of the file that is missing. A file fingerprint is a calculated checksum that uniquely identifies the file. tsv-name is the name of the subvolume where the file is missing. Cause. The file with the specified fingerprint is missing from the target. Effect. The activity finishes with errors. Recovery.
PAGE 237
5095 DSM/SCM EMS Messages 5095 Bad file-type file filename on medium. file-type is the file type of the file. Possible values: Activation Package Archive File Configuration Information File FAB File Map File Process PURGME File Report File(s) RLSEID File System Snapshot Software Input SYSGEN Input Product File SYSGEN Output File Target File Tool File Trace ZPHIFI File ZPHI6030 File ZPHISYS File ZSSLIST File filename is the file name in the internal format of the file.
PAGE 238
5100 DSM/SCM EMS Messages 5100 Incomplete AP from subvolume-name on medium. subvolume-name is the name of the subvolume where the incomplete activation package (AP) is located. medium is the medium where the incomplete activation package is located. Possible values: disk tape Cause. An activation package was incomplete. Effect. DSM/SCM completes the activity with errors. Recovery.
PAGE 239
5110 DSM/SCM EMS Messages 5110 An unmanaged file has been successfully renamed old-filename to new-filename. old-filename is the previous file name in the internal format of the file. new-filename is the new file name in the internal format of the file. Cause. A new file managed by DSM/SCM had the same name as an existing unmanaged file. The unmanaged file was renamed into the PURGEME subvolume. Effect. DSM/SCM renames the file, issues this informational message, and continues processing. Recovery.
PAGE 240
5125 DSM/SCM EMS Messages Recovery. If you perform a system load, TACL attempts to build the TACLSEGF file. After a system load, check that the TACLSEGF file was built without errors. If the system load TACL reports an error, contact your service provider and provide all relevant information: • • • • Descriptions of the problem and accompanying symptoms A copy of the file that caused the error (SYSnn.
PAGE 241
5130 DSM/SCM EMS Messages 5130 Volume pair primary-volume-name alternate-volume-name. Cannot action-name file filename on subvol subvolume-name. primary-volume-name is the name of the primary volume. alternate-volume-name is the name of the alternate volume. action-name is the name of the procedure or action that was in progress when the file error occurred.
PAGE 242
5135 DSM/SCM EMS Messages 5135 Change in target system environment detected. Cause. One or more files have been modified since DSM/SCM placed them on the target system. Effect. The requested activity finishes nonrestartable. Recovery. Cancel the current request; then: 1. Use the Target Interface to perform a Verify Database request. 2. Use the Target Interface to perform an Independent Snapshot request. 3. Use the Planner Interface to rebuild and apply the last configuration.
PAGE 243
5145 DSM/SCM EMS Messages 5145 DSM/SCM has detected an inconsistency between the database and the system. Apply request cannot proceed. Perform the following recover action: recovery-action recovery-action lists the steps needed to correct the problem. These steps include one or more of: • • • • • • Cancel Apply request. Perform database verify. Create system snapshot. Resubmit Apply request. Perform Receive snapshot at host. Perform Build/Apply. Cause.
PAGE 244
5151 DSM/SCM EMS Messages 5151 Managed TSV tsvname has become obsolete. DSM/SCM is no longer managing this TSV. Delete files from this TSV manually once this TSV is no longer needed. tsvname is the name of the obsolete target subvolume (TSV). Cause. The last two configurations (the new configuration being placed and the previous configuration) share the same SYSnn. The (now obsolete) configuration prior to them went to a different SYSnn. Effect. This is an informational message.
PAGE 245
5153 DSM/SCM EMS Messages 5153 Managed TDL tdlname has become obsolete. DSM/SCM is no longer managing this directory. Remove files from this directory manually once they are no longer needed. tdlname is the name of the obsolete OSS directory. Cause. The last two configurations (the new configuration being placed and the previous configuration) share the same SYSnn. The (now obsolete) configuration prior to them went to a different SYSnn. Effect. This is an informational message.
PAGE 246
5161 DSM/SCM EMS Messages 5161 Error file-error encountered attempting to remove obsolete managed OSS file filename. Remove the specified file manually. file-error is the OSS file-system error that occurred. For OSS file-system error definitions, see the Open System Services System Calls Reference Manual. filename is the name of the OSS file that could not be removed. Cause. DSM/SCM could not delete the obsolete file because of the indicated error. Effect. The activity finishes with warnings. Recovery.
PAGE 247
5171 DSM/SCM EMS Messages 5171 Public DLL TSV from-vol-name.subvol-name has been moved or copied to to-vol-name.subvol-name. The new subvolume name does not conform to the ZDLLrrr[a] naming convention. DSM/SCM will no longer manage this subvolume. from-vol-name.subvol-name is the name of the volume and subvolume where the public DLL was moved from. to-vol-name.subvol-name is the name of the volume and subvolume where the public DLL was moved to. Cause.
PAGE 248
5180 DSM/SCM EMS Messages 5180 WARNING: DSM/SCM has detected that TSV source-volume.sourcesubvolume has been moved to destination-volume.destinationsubvolume. destination-subvolume is not bootable because SYSnn-number is not an octal number. source-volume is the name of the source volume of the TSV. source-subvolume is the name of the source subvolume of the TSV. destination-volume is the name of the destination volume of the TSV.
PAGE 249
5190 DSM/SCM EMS Messages 5190 The SYSnn subvolume-name for the current configuration of target target-name is missing from system-volume and was not found anywhere else on the system. The target target-name is being deleted from the target system. The DSM/SCM database will be updated accordingly. subvolume-name is the name of the SYSnn subvolume related to the current configuration. target-name is the name of the logical target.
PAGE 250
5200 DSM/SCM EMS Messages 5200 The SYSnn subvolume-name for the previous configuration of target target-name is missing from system-volume and was not found anywhere else on the system. Backout will not be allowed. The DSM/SCM database will be updated accordingly. subvolume-name is the name of the SYSnn subvolume related to the previous configuration. target-name is the name of the logical target. system-volume is the name of the system volume where the SYSnn subvolume was expected to reside. Cause.
PAGE 251
5210 DSM/SCM EMS Messages 5210 DSM/SCM has detected that TSV source-volume.source-subvolume has been moved to destination-volume.destination-subvolume for target target-name. The DSM/SCM database will be updated accordingly. source-volume.source-subvolume is the name of the source volume and subvolume of the target subvolume (TSV). destination-volume.destination-subvolume is the name of the destination volume and SYSnn subvolume of the TSV. target-name is the name of the target system. Cause.
PAGE 252
5220 DSM/SCM EMS Messages 5220 DSM/SCM has detected that the SYSnn and CSSnn were not moved to the same volume and nn number. SYSnn: SYSnn-volume.SYSnnsubvolume CSSnn: CSSnn-volume. CSSnn-subvolume. Verification for target target-name skipped. SYSnn-volume is the name of the SYSnn volume. SYSnn-subvolume is the name of the SYSnn subvolume. CSSnn-volume is the name of the CSSnn volume. CSSnn-subvolume is the name of the CSSnn subvolume. target-name is the name of the logical target being verified.
PAGE 253
5221 DSM/SCM EMS Messages 5221 TSV first-vol-name.subvol-name and second-vol-name.subvolname are required to be on the same volume. Verification for target target-name skipped. first-vol-name.subvol-name is the name of the volume and subvolume where the first TSV is located. Example: $SYSTEM.SYS00 second-vol-name.subvol-name is the name of the volume and subvolume where the second TSV is located. Example: $DATA.ZDLL005 target-name is the name of the logical target being verified. Cause.
PAGE 254
5230 DSM/SCM EMS Messages 5230 WARNING: File filename is incorrect or missing and needs to be placed. The correct files is not available from the activation package/archive. The correct file is available on the target system in another location. The ‘Place all files using host files’ or ‘Place files that have changed using host files’ option has been seleted. A target file is being used anyway to allow the apply to continue. Further messages of this type will be suppressed.Continuing.
PAGE 255
5250 DSM/SCM EMS Messages 5250 ASSIGN assign-filename has an invalid value of actualfilename. Correct the assign value in the Pathway server class. RESTART the activity. assign-filename is the name assigned to the actual file. actual-filename is the ASSIGN value. This file name is the actual file. Cause. A file name was expected as the ASSIGN value. The subvolume or file name portion is missing. Effect. The activity stops in a restartable state. Recovery.
PAGE 256
5270 DSM/SCM EMS Messages 5270 File filename has an invalid alternate key filename. Correct the alternate key value for this file with FUP ALTER filename, ALTFILE alt-file command. RESTART activity. filename is the file that contains an invalid alternate key file reference. Cause. DSM/SCM received error 21 from the File Utility Program (FUP) when attempting to copy (DUP) this file. The file has an incorrect alternate key attribute. Effect. The activity stops in a restartable state. Recovery.
PAGE 257
5300 DSM/SCM EMS Messages 5300 The target SYSNN volume primary-volume alternate-volume is not up as $SYSTEM. The target SYSNN volume must be the coldload volume because OSS files are being installed. CANCEL the Apply. Coldload from the target SYSNN volume and RESTART the Apply. primary-volume is the volume primary name for the target SYSnn. alternate-volume is the volume alternate name for the target SYSnn. Cause. The target SYSnn is not up as $SYSTEM. Effect. The activity stops in a restartable state.
PAGE 258
5310 DSM/SCM EMS Messages If you do not want target-system to manage OSS files, cancel the Apply, clear the Manage OSS Files check box for this target, and perform another Build/Apply. 5310 The current OSS environment contains old DSM/SCM work files. Run CLEANOSS to remove all DSM/SCM work files from this OSS environment. RESTART the activity. Cause. An unexpected /zzDSMSCM.Managed file was found in the OSS environment, and no other logical targets manage this OSS environment. Effect.
PAGE 259
5321 DSM/SCM EMS Messages 5321 OSS management cleanup is required because of a recent Backout. CANCEL the Apply. Run CLEANOSS, then Verify Database to remove prior OSS file management for Logical Target target-name. Then start Apply. Management of OSS files will be restored. target-name is the name of the logical target that OSS files are being installed for. Cause. The last configuration, which managed OSS files, was backed out. The current configuration does not manage OSS files.
PAGE 260
5330 DSM/SCM EMS Messages 5330 Management of OSS files will be removed from the target target-name. DSM/SCM OSS work files will not be removed because the /OSS environment for this target is not available. Run CLEANOSS to remove these files when this OSS environment becomes available. target-name is the name of the logical target on which OSS file management will be removed. Cause. The OSS environment is not available because a different $SYSTEM volume was system loaded. Effect.
PAGE 261
5335 DSM/SCM EMS Messages 5335 Management of OSS files has been removed for target targetname. target-name is the name of the logical target for which OSS file management was removed. Cause. The Manage OSS Files check box was cleared for this logical target before this Build/Apply request. The previous Build/Apply for this logical target managed OSS files. Effect. All DSM/SCM work files (.dsmscm.* and zzDSMSCM.Managed files) used to manage OSS files are removed. All other OSS files are left in place.
PAGE 262
5350 DSM/SCM EMS Messages 5350 A coldload will be required to activate the public DLLs in this new configuration because the active DLLs are not correct. A correct set of public DLLs will be placed in $SYSTEM.correct-dll-subvolume. The set of public DLLs has not changed from configuration-name. The active set of public DLLs in active-dll-subvolume is incorrect because dll-file is reason. No other correct dll-subvolume-template [a] TSVs were found.
PAGE 263
5360 DSM/SCM EMS Messages 5360 A coldload will be required to activate the public DLLs in this new configuration because the active DLLs are not correct. The active set of public DLLs in $SYSTEM.active-dllsubvolume is incorrect because dll-file is reason. A correct set of public DLLs were found in $SYSTEM.correct-dllsubvolume. active-dll-subvolume is the subvolume where the active set of public DLLs is located. dll-file is the name of the first active public DLL file found to be incorrect.
PAGE 264
5370 DSM/SCM EMS Messages 5370 Waiting for the clone Applies to complete on the following system(s): system-names. If any of these Clone Applies can not be completed, their Apply completion file, named X(system-name) in AP subvolume subvolume, must be renamed to M(system-name) in order for this master Apply to complete. system-names is a list of systems that have not yet completed the clone Apply; for example, “\XYZ02, \XYZ04”. subvolume is the location of the activation package subvolume. Cause.
PAGE 265
5371 DSM/SCM EMS Messages 5371 Clone Apply system-name logical-target-name completionmessage. system-name is the name of the target system defined as a master. logical-target-name is the name of the logical target on system-name. completion-message is one of these completion status messages: • • • • completed successfully completed with warning(s) completed with error(s) was abandoned Cause. A clone apply completed. Effect.
PAGE 266
5373 DSM/SCM EMS Messages 5373 Warning: The clone group Apply completion file filename is missing. Clone group Apply status may not be complete for all the clone group target systems. filename is the name of the apply completion file for the master apply. Cause. The master apply completion file is missing. The entire activation package subvolume might have been purged by a clone Apply performed with an earlier DSM/SCM product version. Effect.
PAGE 267
6005 DSM/SCM EMS Messages 6005 Cannot communicate with server, PATHWAY error psend-error, file system error file-error, serverclass server-class-name, PATHMON pmon-name. Correct PATHWAY error. RESTART the activity. psend-error is the Pathsend error code returned. Pathsend error codes are defined in the TS/MP Pathsend and Server Programming Manual. file-error is the file-system error that occurred (if any). For file-system error definitions, see Section 7, File-System Errors.
PAGE 268
6010 DSM/SCM EMS Messages 6010 Cannot cancel request-name at this node. Planner must issue a CANCEL at the local node target-name. request-name is the text of the request that was not cancelled. target-name is the system name of the local node where the request must be canceled. Cause. A DSM/SCM cancel operation could not be performed at this node because the activity to be canceled is being performed at a remote node. A DSM/SCM activity must be canceled at the local node. Effect.
PAGE 269
6020 DSM/SCM EMS Messages 6020 request-name currently executing on target-name. Cannot start a activity-name activity at this time. Start activity-name activity after current activity has completed. request-name is the name of the request that is currently executing. target-name is the system name of the node where the request is executing. activity-name is the name of the request you are trying to submit. Cause. A second activity was requested while one activity was in progress.
PAGE 270
7000 DSM/SCM EMS Messages 7000 export-type file(s) exported to export-subvolume-name. export-type is the type of file that was exported. Possible values: EMS Template Privileged Declaration SPI Definition export-subvolume-name is the name of the destination subvolume (DSV) where the files were exported. Cause. The user requested that DSM/SCM export files from the DSM/SCM archive. Effect. The request was completed. The files are on the specified subvolume. Recovery.
PAGE 271
6 EMS Messages From Other Subsystems Some utilities (BACKUP, DISKGEN, File Manager, SYSGEN, and Tape Reader) share use of the DSM/SCM message header and report their EMS messages to DSM/SCM. This section describes the content and meaning of the Event Management Service (EMS) messages that the BACKUP, Tape Reader, and SYSGEN subsystems generate that are returned by DSM/SCM. BACKUP and Tape Reader Messages 0001 DSM/SCM TapeReader *0001* : *ERROR* Tape-error-num: error-text.
PAGE 272
EMS Messages From Other Subsystems 0002 0002 DSM/SCM TapeReader *0002* : *WARNING* Tape-error-num: error-text. error-num is the numeric value of the tape warning that occurred. For possible values, see Section 8, BACKUP Errors. error-text is a text translation of the error. For possible values, see Section 8, BACKUP Errors. Cause. The Tape Reader subsystem returned a tape warning. Effect. The effect varies depending on the specific error returned. Recovery.
PAGE 273
EMS Messages From Other Subsystems 0004 0004 DSM/SCM TapeReader *0004* : *ERROR* Tape-error-num: error-text. error-num is the numeric value of the tape mount warning that occurred. For possible values, see Section 8, BACKUP Errors. error-text is a text translation of the error. For possible values, see Section 8, BACKUP Errors. Cause. The Tape Reader subsystem returned a tape mount warning. Effect. The effect varies depending on the specific error returned. Recovery.
PAGE 274
EMS Messages From Other Subsystems 0006 0006 Backup *0001* : *ERROR* Tape-error-num: error-text. error-num is the numeric value of the tape error that occurred. For possible values, see Section 8, BACKUP Errors. error-text is a text translation of the error. For possible values, see Section 8, BACKUP Errors. Cause. The BACKUP subsystem returned a tape error. Effect. The effect varies depending on the specific error returned. Recovery. Check the error code and text reported in the message.
PAGE 275
EMS Messages From Other Subsystems 0008 0008 Backup *0003* : *ERROR* Tape-error-num: error-text. error-num is the numeric value of the tape mount error that occurred. For possible values, see Section 8, BACKUP Errors. error-text is a text translation of the error. For possible values, see Section 8, BACKUP Errors. Cause. The BACKUP subsystem returned a tape mount error. Effect. The effect varies depending on the specific error returned. Recovery. Check the error code and text reported in the message.
PAGE 276
EMS Messages From Other Subsystems 0010 0010 Backup *0005* : *Mount Message*: message-text. message-text contains the text of the tape mount message. Cause. The BACKUP subsystem returned a tape mount message to prompt you to mount a tape. Effect. The BACKUP subsystem waits for you to perform the task in the mount message. Recovery. Perform the task in the mount message. 0011 BACKUP *0006* : error-num error-num indicates the BACKUP error number and a brief description of the error.
PAGE 277
7 File-System Errors This section lists file-system errors and briefly describes each error. For information about correcting file-system errors, see the Guardian Procedure Errors and Messages Manual. Note. To display the message text of a file-system error, at a TACL prompt, enter error followed by the error number; for example, error 2. To display the message text and number of all file-system and SQL/MP errors, type: error -1. Table 7-1.
PAGE 278
File-System Errors Table 7-1.
PAGE 279
File-System Errors Table 7-1.
PAGE 280
File-System Errors Table 7-1.
PAGE 281
File-System Errors Table 7-1.
PAGE 282
File-System Errors Table 7-1.
PAGE 283
File-System Errors Table 7-1.
PAGE 284
File-System Errors Table 7-1.
PAGE 285
File-System Errors Table 7-1. File-System Errors (page 9 of 12) Decimal Number Octal Number 584 %1110 Operation cannot be performed because a software component does not support format 2 disk files.
PAGE 286
File-System Errors Table 7-1. File-System Errors (page 10 of 12) Decimal Number Octal Number 712 %1310 An attempt was made to register a recoverable resource manager using the TMF_REC_RM_CREATE_ procedure, but the name was already registered. 713 %1311 An attempt was made to remove a recoverable resource manager from the directory using the TM_REC_RM_REMOVE_ procedure, but the resource manager still has unresolved transactions outstanding.
PAGE 287
File-System Errors Table 7-1. File-System Errors (page 11 of 12) Decimal Number Octal Number 727 %1327 An attempt was made to create a recoverable resource manager, but the maximum allowable recoverable resource managers for the system is exceeded.
PAGE 288
File-System Errors Table 7-1.
PAGE 289
8 BACKUP Errors This section lists BACKUP errors and their text descriptions. These errors appear as the value of error-num and error-text in the BACKUP and Tape Reader Event Management Service (EMS) messages described in Section 6, EMS Messages From Other Subsystems. For information about correcting these errors, see the Guardian Disk and Tape Utilities Reference Manual. Table 8-1.
PAGE 290
BACKUP Errors Table 8-1.
PAGE 291
Content Feedback First Name: __________________ Phone: _____________________ Company: ___________________ Last Name: _________________ e-mail address: ______________ (All contact information fields are required.) If you’re reporting an error or omission, is your issue: Minor: I can continue to work, but eventual resolution is requested. Major: I can continue to work, but prompt resolution is requested. Critical: I cannot continue to work without immediate response.