DSM/SCM Messages Manual

Transcription

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.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 Mar 2015

2 Document History Part Number Product Version Published DSM/SCM D31 and D46 December DSM/SCM D31 and D46 April DSM/SCM D31 and D46 December DSM/SCM D31, G01 (ABP), and H01 July DSM/SCM G02 September DSM/SCM G02, H02 February DSM/SCM G02, H02 May DSM/SCM G02, H02 Mar 2015

3 DSM/SCM Messages Manual Tables Legal Notices What s New in This Manual iii Manual Information iii New and Changed Information iii About This Manual v What Is DSM/SCM? v Who Should Use This Manual v What s in This Manual vi Other DSM/SCM Information Sources Notation Conventions vii vi 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 Target Interface Messages Warning and Error Messages 2-1 Status Messages Archive and Database Maintenance Interface Messages 4. ZPHIRNM Messages ZPHIRNM Messages 4-1 Error Severity Levels 4-1 Syntax Error Message 4-1 Termination Messages 4-2 Hewlett-Packard Company i

4 Contents 4. ZPHIRNM Messages (continued) File Error and Warning Messages ZPHIRNM Messages (continued) 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 ii

5 Legal Notices Copyright 2015 Hewlett-Packard Development Company L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR and , 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. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Export of the information contained in this publication may require authorization from the U.S. Department of Commerce. Microsoft, Windows, Windows NT, Windows 95, Windows Version 3.11, Windows XP, Windows Vista, and Windows - 7 (32 Bit) are U.S. registered trademarks of Microsoft Corporation. Intel, Itanium, Pentium, and Celeron are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Motif, OSF/1, UNIX, X/Open, and the "X" device are registered trademarks and IT DialTone and The Open Group are trademarks of The Open Group in the U.S. and other countries. Open Software Foundation, OSF, the OSF logo, OSF/1, OSF/Motif, and Motif are trademarks of the Open Software Foundation, Inc. OSF MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THE OSF MATERIAL PROVIDED HEREIN, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. OSF shall not be liable for errors contained herein or for incidental consequential damages in connection with the furnishing, performance, or use of this material. 1990, 1991, 1992, 1993 Open Software Foundation, Inc. This documentation and the software to which it relates are derived in part from materials supplied by the following: 1987, 1988, 1989 Carnegie-Mellon University. 1989, 1990, 1991 Digital Equipment Corporation. 1985, 1988, 1989, 1990 Encore Computer Corporation Free Software Foundation, Inc. 1987, 1988, 1989, 1990, 1991 Hewlett-Packard Company. 1985, 1987, 1988, 1989, 1990, 1991, 1992 International Business Machines Corporation. 1988, 1989 Massachusetts Institute of Technology. 1988, 1989, 1990 Mentat Inc Microsoft Corporation. 1987, 1988, 1989, 1990, 1991, 1992 SecureWare, Inc. 1990, 1991 Siemens Nixdorf Informationssysteme AG. 1986, 1989, 1996, 1997 Sun Microsystems, Inc. 1989, 1990, 1991 Transarc Corporation. This software and documentation are based in part on the Fourth Berkeley Software Distribution under license from The Regents of the University of California. OSF acknowledges the following individuals and institutions for their role in its development: Kenneth C.R.C. Arnold, Gregory S. Couch, Conrad C. Huang, Ed James, Symmetric Computer Systems, Robert Elz. 1980, 1981, 1982, 1983, 1985, 1986, 1987, 1988, 1989 Regents of the University of California. Printed in the U.S.

6

7 What s New in This Manual Manual Information Abstract DSM/SCM Messages Manual 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 Mar 2015 Document History Part Number Product Version DSM/SCM D31 and D DSM/SCM D31 and D DSM/SCM D31 and D DSM/SCM D31, G01 (ABP), and H DSM/SCM G DSM/SCM G02, H DSM/SCM G02, H DSM/SCM G02, H02 Published December 2003 April 2004 December 2004 July 2005 September 2005 February 2006 May 2008 Mar 2015 New and Changed Information Changes to the H06.19 manual Removed the following redundant chapters available in Operator Messages Manual (OMM), Chapter 5, Chapter 6, Chapter 7, and Chapter 8 from this manual. 3

8 What s New in This Manual Changes to the H06.05 manual Changes to the H06.05 manual Added event messages 2033, 2034, 2162, 2163, 2164, 2165, 2166, 5370, 5371, 5372, and Updated the description of event messages 2047, 2161, 5350, and Changes to the G06.27 manual DSM/SCM EMS message 4285 was added. INITENV messages was added. 4

9 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. Technical information about the interfaces is available through the online help in each DSM/SCM interface. Who Should Use This Manual Readers of this manual should be familiar with DSM/SCM and HP NonStop operating system fundamentals. This manual is a reference for DSM/SCM users who need more information about a message or error that you might encounter while using DSM/SCM. 5

10 About This Manual What s in 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 3 Archive and Database Maintenance Interface Messages Other DSM/SCM Information Sources The DSM/SCM User s Guide provides detailed step-by-step procedures for performing the various tasks possible through each of the DSM/SCM interfaces and tools. The DSM/SCM Online Help provides information about using the interfaces, specific to the screen from which you call the help. Online help is available in the Planner Interface, the Maintenance Interfaces, the Target Interface, and CNFGINFO. The DSM/SCM Quick Reference Guide provides concise procedures for common DSM/SCM tasks. It is intended only for expert DSM/SCM users. The DSM/SCM Event Management Programming Manual provides information about the token-oriented event messages from the programmatic interface to DSM/SCM. It is a reference manual for DSM/SCM event message token information and for programmers writing applications and filters to select DSM/SCM event messages. Notation Conventions Hypertext Links Messages issued by the Target Interface and suggests a corrective action for each message. Messages issued by the Archive and Database Maintenance Interfaces and suggests a corrective action for each message. 4 ZPHIRNM Messages Messages issued by ZPHIRNM and suggests a corrective action for each message. 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

11 About This Manual General Syntax Notation General Syntax Notation This list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words. Type these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH lowercase italic letters. Lowercase italic letters indicate variable items that you supply. Items not enclosed in brackets are required. For example: file-name computer type. Computer type letters within text indicate C and Open System Services (OSS) keywords and reserved words. Type these items exactly as shown. Items not enclosed in brackets are required. For example: myfile.c italic computer type. Italic computer type letters within text indicate C and Open System Services (OSS) variable items that you supply. Items not enclosed in brackets are required. For example: pathname [ ] Brackets. Brackets enclose optional syntax items. For example: TERM [\system-name.]$terminal-name INT[ERRUPTS] A group of items enclosed in brackets is a list from which you can choose one item or none. The items in the list can be arranged either vertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: FC [ num ] [ -num ] [ text ] K [ X D ] address { } 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 } 7

12 About This Manual Notation for Messages Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: INSPECT { OFF ON SAVEABEND } Ellipsis. An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times. For example: M address [, new-value ] [ - ] { } An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times. For example: "s-char " Punctuation. Parentheses, commas, semicolons, and other symbols not previously described must be typed as shown. For example: error := NEXTFILENAME ( file-name ) ; LISTOPENS SU $process-name.#su-name Quotation marks around a symbol such as a bracket or brace indicate the symbol is a required character that you must type as shown. For example: "[" repetition-constant-list "]" Item Spacing. Spaces shown between items are required unless one of the items is a punctuation symbol such as a parenthesis or a comma. For example: CALL STEPMOM ( process-id ) ; If there is no space between two items, spaces are not permitted. In this example, no spaces are permitted between the period and any other items: $process-name.#su-name Line Spacing. If the syntax of a command is too long to fit on a single line, each continuation line is indented three spaces and is separated from the preceding line by 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. 8

13 About This Manual Notation for Messages Bold Text. Bold text in an example indicates user input typed at the terminal. For example: ENTER RUN CODE?123 CODE RECEIVED: The user must press the Return key after typing the input. Nonitalic text. Nonitalic letters, numbers, and punctuation indicate text that is displayed or returned exactly as shown. For example: Backup Up. lowercase italic letters. Lowercase italic letters indicate variable items whose values are displayed or returned. For example: p-register process-name [ ] Brackets. Brackets enclose items that are sometimes, but not always, displayed. For example: Event number = number [ Subject = first-subject-value ] A group of items enclosed in brackets is a list of all possible items that can be displayed, of which one or none might actually be displayed. The items in the list can be arranged either vertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: proc-name trapped [ in SQL in SQL file system ] { } Braces. A group of items enclosed in braces is a list of all possible items that can be displayed, of which one is actually displayed. 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: 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. A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: Transfer status: { OK Failed } 9

14 About This Manual Notation for Management Programming Interfaces % Percent Sign. A percent sign precedes a number that is not in decimal notation. The % notation precedes an octal number. The %B notation precedes a binary number. The %H notation precedes a hexadecimal number. For example: % %B %H2F P=%p-register E=%e-register Notation for Management Programming Interfaces This list summarizes the notation conventions used in the boxed descriptions of programmatic commands, event messages, and error lists in this manual. UPPERCASE LETTERS. Uppercase letters indicate names from definition files. Type these names exactly as shown. For example: ZCOM-TKN-SUBJ-SERV lowercase letters. Words in lowercase letters are words that are part of the notation, including Data Definition Language (DDL) keywords. For example: token-type!r.!o. The!r notation following a token or field name indicates that the token or field is required. For example: ZCOM-TKN-OBJNAME token-type ZSPI-TYP-STRING.!r The!o notation following a token or field name indicates that the token or field is optional. For example: ZSPI-TKN-MANAGER token-type ZSPI-TYP-FNAME32.!o 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). The CRE has many new message types and some new message type codes forold message types. In the CRE, the message type SYSTEM includes all messages except LOGICAL-CLOSE and LOGICAL-OPEN. 10

15 About This Manual HP Encourages Your Comments HP Encourages Your Comments HP encourages your comments concerning this document. We are committed to providing documentation that meets your needs. Send any errors found, suggestions for improvement, or compliments to Include the document title, part number, and any comment, error found, or suggestion for improvement you have concerning this document. 11

16 About This Manual HP Encourages Your Comments 12

17 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 Starts the internal processes needed to run DSM/SCM 1-24 VERIFYI Verifies that the internal processes required by DSM/SCM are present and that all steps performed by INITENV have finished successfully 1-26 Certain INITENV messages are issued when a file-system error occurs during an attempt to access an internal file. When this occurs, INITENV issues a general message indicating where the error occurred and reports the file-system error number. For brief descriptions of file-system errors, see Chapter Appendix, B File-System Errors in Operator Messages Manual. For detailed descriptions, see the Guardian Procedure Errors and Messages Manual. Some INITENV messages are issued when an internal stage called by INITENV detects an error. In these cases, INITENV issues its own general message and includes a detailed message issued by the stage. These messages are identified by the stage name, such as INITSQL ERROR or INITTDB ERROR. For most errors, the suggested recovery action involves correcting the error, then rerunning INITENV. When you rerun INITENV, it performs only tasks that were not completed. It does not repeat previously completed tasks. 1-1

18 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. Informational message; no corrective action is needed. INITENV ERROR: CHANGE-HOST not allowed on a host system. Run INITENV interactively, select the Change option, indicate that this system is a target, and specify the host system. Cause. You attempted to use the CHANGE-HOST run-line option on a host system. Effect. INITENV terminates. Recovery. Run INITENV interactively, select the Change option, indicate that this system is a target, and specify the host system. INITENV ERROR: Invalid parameters to INITENV, DEFAULTS and CHANGE-HOST not allowed together. Cause. The run-line options CHANGE-HOST and DEFAULTS were used together. Effect. INITENV terminates. Recovery. Do not use run-line options CHANGE-HOST and DEFAULTS together. INITENV ERROR: Invalid or missing host system name after CHANGE-HOST. A valid system name must follow CHANGE-HOST. Cause. You either entered an invalid system name or no system name for the CHANGE-HOST option. Effect. INITENV terminates. Recovery. Enter a valid system name. 1-2

19 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. A file-system error occurred when INITENV tried to access one of its required internal files. Effect. INITENV terminates. Recovery. For a description of the error code displayed in this message, see Chapter Appendix, B File-System Errors in Operator Messages Manual. Correct the file-system error; then rerun INITENV. INITENV 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 when INITENV tried to open one of its required internal files. Effect. INITENV terminates. Recovery. For a description of the error code displayed in this message, see Chapter Appendix, B File-System Errors in Operator Messages Manual. Correct the file-system error; then rerun INITENV. 1-3

20 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. Recovery. To continue without a log file, enter Y. To leave INITENV, enter N. If you leave INITENV, correct the file-system error; then rerun INITENV. For a description of the error code displayed in this message, see Chapter Appendix, B File-System Errors in Operator Messages Manual. (All INITENV messages are sent to the terminal whether or not a log file is used.) INITENV: All log files ILOG ILOG9999 exist. Purge some of these old log files. 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. INITENV cannot create a new log file for this session because all possible log file names from ILOG0000 through ILOG9999 already exist on your system. Effect. INITENV pauses and lets you indicate whether or not you want to continue without a log file. Recovery. To continue without a log file, enter Y. To leave INITENV, enter N. If you leave INITENV, purge some old log files, then rerun INITENV. (All INITENV messages are sent to the terminal whether or not a log file is used.) INITENV ERROR: This question requires that you enter either "I" for Initialize DSM/SCM or "C" for Change default settings. Please retry. Cause. You entered a value other than I or C. Effect. INITENV pauses and lets you reenter the value. Recovery. If you are initializing DSM/SCM, enter I. If you are changing default settings, enter C. 1-4

21 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. The Remote Server Call (RSC) product was not installed before you ran INITENV. Effect. INITENV stops. Recovery. Install, configure, and initialize RSC; then rerun INITENV. INITENV ERROR: The entered system name is not accessible or does not exist: file error error-number. Please retry. Cause. You entered the name of a system that either does not exist or cannot be accessed over the network. Effect. INITENV pauses and lets you reenter the system name. Recovery. Enter the name of a system that is connected to your NonStop network. INITENV ERROR: The entered value is not a valid file name, or the file is not accessible, or it does not exist. 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: The entered value is not a valid IP Port number. Please retry. Cause. The IP port number is not valid. Effect. INITENV pauses and lets you enter a new IP port number. Recovery. Enter a valid IP port number from 1025 through

22 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. Check that the volume is mounted on the host system. INITENV ERROR: The entered value is not a valid name for a hometerm, or the device/process is not accessible, or it does not exist. Please retry. Cause. Either the hometerm name you entered had an incorrect format, the hometerm does not exist, or the hometerm could not be accessed over the network. Effect. INITENV pauses and lets you reenter the hometerm name. Recovery. Enter a valid hometerm name. Check that the name has the correct format and the hometerm is network accessible from your system. INITENV ERROR: The entered value is not a valid system name. Please retry. Cause. The system name you entered had an incorrect format. Effect. INITENV pauses and lets you reenter the system name. Recovery. Enter a system name that follows standard NonStop naming conventions. INITENV ERROR: The entered value is not a valid userid. Please retry. Cause. The user ID you specified as the database owner must be a valid user ID known to the system. Effect. INITENV pauses and lets you enter a new user ID. Recovery. Enter a valid user ID. 1-6

23 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. Only systems that already have DSM/SCM installed may be used as a remote database system. Please retry. (You may enter <CTRL-Y> to exit now.) Cause. You specified a volume for the DSM/SCM database that is on a remote system, but DSM/SCM is not installed on that system. Effect. INITENV cannot create the database on the remote system. INITENV pauses and lets you reenter the volume name. Recovery. Either enter a new volume name; or break out of INITENV, take corrective action (such as installing DSM/SCM on the remote system), and then rerun INITENV. INITENV ERROR: The question requires that you enter either H for the Host system or T for a Target system. Please retry. Cause. You entered a value other than H or T. Effect. INITENV pauses and lets you reenter the value. Recovery. Enter H if you are initializing a host system or T if you are initializing a target system. INITENV ERROR: The SERVICES and/or PORTCONF files were either not found or not secured so INITENV can modify them. Please retry. Cause. The SERVICES or PORTCONF file in the subvolume you entered either does not exist, has an incorrect format, or is not secured so INITENV can modify it. Effect. INITENV asks if you want to modify the file. Recovery. If you do not want INITENV to modify the files, enter No. Otherwise, enter the name of a subvolume that contains the SERVICES and PORTCONF files so INITENV can modify it. 1-7

24 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. Enter a new IP port number, ensuring that it is the same one specified when running the SETUP program on the PC. INITENV ERROR: This question requires that you enter either R for Re-installation or C for Continuation. Cause. You entered a value other than R or C. Effect. INITENV pauses and lets you reenter the value. Recovery. Enter R if this is a reinstallation of DSM/SCM or C if this is a continuation of the current installation of DSM/SCM. INITENV ERROR: This question requires that you enter either R or W. Please retry. Cause. You entered a value other than R or W. Effect. INITENV pauses and lets you reenter the value. Recovery. Enter R if you will use RSC or W if you will use Winsock. INITENV ERROR: This question requires that you enter either R, W, or C. Please retry. Cause. INITENV could not find the TCP/IP LISTNER program in the current SYSnn on your system. When prompted for more information, you did not enter a valid response. Effect. INITENV pauses and lets you enter a new response. Recovery. Enter one of: R W C To use RSC instead of Winsock To obtain TCP/IP for this host and select Winsock again To either skip setting up the DSM/SCM Winsock Service or to modify the SERVICES and PORTCONF files without starting the LISTNER process 1-8

25 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. The TACL segment file INITSEGF must be present in the current subvolume before INITENV can run. Effect. INITENV cannot begin. Recovery. Check for the existence and location of the INITSEGF file. If necessary, create the file or move it to the current subvolume. INITENV INTERNAL ERROR: Please contact your Tandem support representative. Cause. An internal problem with INITENV occurred. Effect. INITENV terminates. Recovery. Contact your service provider, and provide all relevant information: Descriptions of the problem and accompanying symptoms Details from the messages generated Supporting documentation such as the $ZPHI Event Management Service (EMS) 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. INITENV ERROR: The entered priority is not valid, please retry. Cause. You entered a value other than the specified range from 30 to 150. Effect. INITENV pauses and lets you reenter the value. Recovery. Enter a value in the specified range from 30 to

26 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). Because you are not logged on as the super ID, INITENV cannot set the PROGID of the indicated DSM/SCM process to the super ID. If you log on as the super ID, INITENV automatically sets the PROGID to the super ID. (You can override that setting.) Effect. None, but if you want the PROGID set to the super ID, you must do it manually. Otherwise, the super ID needs to perform certain future activities such as those indicated in the message. Recovery. Informational message only; no corrective action is needed. Note: This system has number OSS environments. DSM/SCM work files were cleaned only from the currently running OSS environment. To clean other environments managed by DSM/SCM, run the CLEANOSS tool next time you start each OSS environment. If DSM/SCM tries to manage an OSS environment that contains old DSM/SCM work files, the Apply will fail. You must run CLEANOSS before the Apply can continue. Cause. INITENV was run on a system that has more than one OSS environment. Effect. None. DSM/SCM work files were cleaned from the current OSS environment. Recovery. Informational message; no corrective action is needed. Note: This system has number OSS environment(s). None are currently running. To clean DSM/SCM work files from the OSS environments, run the CLEANOSS tool next time you start each OSS environment. If DSM/SCM tries to manage an OSS environment that contains old DSM/SCM work files, the Apply will fail. You must run CLEANOSS before the Apply can continue. Run CLEANOSS only if DSM/SCM will manage an OSS environment containing old DSM/SCM work files. Cause. INITENV was run on a system that has no currently running OSS environments. Effect. None. Recovery. Informational message; no corrective action is needed. 1-10

27 INITENV Messages INITTMF Errors 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. INITENV tried to initialize the TMF environment on a remote system, but DSM/SCM has not been installed on that system. Therefore, the TMF environment could not be initialized on it. Effect. INITENV stops. Recovery. Either install the TMF component on the remote system or specify a system on which the TMF component has been installed. Then rerun INITENV. INITTMF ERROR: Entered value is not a valid userid. Please retry. Cause. The user ID you entered is not known to the system. Effect. INITENV pauses and lets you reenter the user ID. Recovery. Enter a valid user ID. INITTMF ERROR: INITTMF is unable to access the remote system, \system, due to file system error error-number. Please correct the problem and run INITENV again. Cause. A file-system error occurred when INITENV tried to access a remote system. Effect. INITENV stops. Recovery. For a description of the error code displayed in this message, see Chapter Appendix, B File-System Errors in Operator Messages Manual. Correct the file-system error; then rerun INITENV. INITTMF ERROR: The entered value is not a valid volume name. Please retry. Cause. The volume name you entered has an incorrect format. Effect. INITENV pauses and lets you reenter the volume name. Recovery. Reenter the volume name using the standard NonStop naming convention. 1-11

28 INITENV Messages INITTMF Errors 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. That volume may not be used for a remote DSM/SCM database until it has been enabled using TMFCOM. Please enable this volume or choose another volume, then run INITENV again. Cause. The volume you specified for use as a DSM/SCM remote database cannot be used because it has not been enabled for audit by the TMF subsystem. Effect. INITENV stops. Recovery. Use the TMFCOM process to enable the volume, or choose an enabled volume; then rerun INITENV. INITTMF ERROR: TMF has been configured, but is not active on \system. That system may not be used for a remote DSM/SCM database unless TMF is active. Please start TMF, or take other appropriate action, then run INITENV again. Cause. INITENV tried to initialize the TMF environment on a remote system, but the TMF subsystem is not active on that system. The TMF subsystem must be active on a remote system if that system is to be used for a database. Effect. INITENV stops. Recovery. Either start the TMF subsystem on the remote system or select another system for the database. To start the TMF subsystem, you can use the TMFSTART procedure or your own standard operational procedures. Then rerun INITENV. 1-12

29 INITENV Messages INITTMF Errors 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. Use TMFCOM to start the TMF subsystem on the local system; then rerun INITENV. INITENV will correctly handle the case where the TMF subsystem is already configured and running. INITTMF ERROR: TMF is configured and it is active, but the requested database volume, $volume, is not enabled for TMF audit. INITTMF will not enable any volumes if it did not also initialize TMF. Please enable this volume using TMFCOM or choose another volume, then run INITENV again. Cause. INITENV found that the TMF subsystem is already configured and started on the system you specified, but the volume you specified for the database has not been enabled for TMF audit. INITENV will not make any changes to an existing TMF configuration and therefore will not enable the volume. Effect. INITENV stops. Recovery. Use TMFCOM to enable the volume; then rerun INITENV. INITTMF will handle the case where the TMF subsystem has already been configured and started and the volume is already enabled. INITTMF ERROR: TMF needs to be initialized, but you are not logged on as a super group userid. Please logon as a super group userid, then run INITENV again. (Note that SQL must be initialized after TMF. That step will require the user to be the super ID, not just a member of the super group.) Cause. You must be logged on as a super-group user (255,n) in order to initialize the TMF subsystem. However, to initialize SQL (the next step in the initialization process), you must be logged on as the super ID (255,255) and not simply as a super-group user (255,n). Effect. INITTMF stops. Recovery. Log on as a super-group user (255,n) or as the super ID (255,255); then rerun INITENV. 1-13

30 INITENV Messages INITSQL 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. INITENV attempted to create a database on a remote system but failed because DSM/SCM is not installed on that system. If a remote system is to be used for a database, DSM/SCM must be installed on that system. Effect. INITENV stops. Recovery. Install DSM/SCM on the remote system, or select a system for the remote database that has DSM/SCM installed; then rerun INITENV. INITSQL 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 there first, or choose another system to use for a remote database, then run INITENV again. Cause. INITENV tried to create a database on a remote system but failed because DSM/SCM is not installed on that system. If a remote system is to be used for a database, DSM/SCM must be installed on that system. Effect. INITENV stops. Recovery. Install DSM/SCM on the remote system, or select a system for the remote database that has DSM/SCM installed; then rerun INITENV. INITSQL ERROR: File error error-number occurred while attempting to resecure the system catalog. Please correct the problem, then run INITENV again. Cause. The indicated file-system error occurred when INITENV attempted to set the appropriate security level for the system catalog. Effect. INITENV stops. Recovery. For a description of the error code displayed in this message, see Chapter Appendix, B File-System Errors in Operator Messages Manual. Correct the file-system error; then rerun INITENV. 1-14

31 INITENV Messages INITSQL 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 Chapter Appendix, B File-System Errors in Operator Messages Manual. Correct the file-system error; then rerun INITENV. INITSQL ERROR: SQL needs to be initialized, but you are not logged on as the super ID. Please logon as super ID, then run INITENV again. Cause. You must be logged on as the super ID (255,255) to initialize SQL on a system. Effect. INITENV stops. Recovery. Log on as the super ID (255,255); then rerun INITENV. INITSQL ERROR: SQLCI error error-number occurred while using the name command. Please correct the problem, then run INITENV again. Cause. The SQLCI error occurred when INITENV issued the indicated command. Effect. INITENV stops. Recovery. Correct the condition that led to the SQLCI error; then rerun INITENV. For a description of the SQLCI error, use the SQL ERROR command or see the SQL/MP Messages Manual. INITSQL ERROR: The entered value is not a valid volume name. Please retry. Cause. The volume name you entered had an incorrect format. Effect. INITENV pauses and lets you reenter the volume name. Recovery. Enter a volume name that follows standard NonStop naming conventions. 1-15

32 INITENV Messages INITSQL 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. These files are probably from an obsolete release, because the current versions of these files should only be found in the SYSnn subvolume. Please remove these files, then run INITENV again. Cause. INITSQL requires current versions of the internal files SORT and SORTPROG to be in the SYSnn subvolume. However, INITSQL found files named SORT, SORTPROG, or both on the indicated system-load volume. Effect. INITENV stops. Recovery. Purge or move the SORT and SORTPROG files from the system-load volume. Check that the current versions are on the SYSnn subvolume; then rerun INITENV. INITSQL ERROR: The requested type volume, $volume, is not enabled for audit on \system. That volume may not be used for a remote DSM/SCM database until it has been enabled using TMFCOM. Please enable this volume or choose another volume, then run INITENV again. Cause. The indicated database or system catalog volume has not been enabled for audit by the TMF subsystem. INITENV does not create a database on a volume that has not been enabled. Effect. INITENV stops. Recovery. Either select an enabled volume or use TMFCOM to enable the volume; then rerun INITENV. 1-16

33 INITENV Messages INITSQL 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. INITSQL ERROR: TMF has been configured on \system, but it is not currently active. That system may not be used for a remote DSM/SCM database unless TMF is active. Please start TMF, or take other appropriate action, then run INITENV again. Cause. INITENV tried to create a database on the remote system but found that the TMF subsystem was not active on that system. The TMF subsystem must be configured and active before INITENV can create a database. Effect. INITENV stops. Recovery. Using your normal operational procedures, start the TMF subsystem on the remote system; then rerun INITENV. INITSQL ERROR: TMF has not been initialized on this system. Please edit the INITSTAT file, remove all INITTMF DONE lines, if any exist, then run INITENV again. Cause. Although the INITENV status file INITSTAT indicates that the TMF subsystem has been initialized, something altered its status. The TMF subsystem must be initialized again before SQL can be initialized. Effect. INITENV stops. Recovery. INITENV checks the INITSTAT file to determine which stages have completed successfully. Edit INITSTAT as suggested in the message and rerun INITENV to initialize the TMF subsystem. 1-17

34 INITENV Messages INITHDB 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 Chapter Appendix, B File-System Errors in Operator Messages Manual. Correct the file-system error; then rerun INITENV. INITHDB Messages These errors are related to the initialization of the host database: INITHDB ERROR: DBINIT detected volume name conflicts, as reported above. Please correct the problem, then run INITENV again. Cause. When attempting to initialize the database, the database initialization function DBINIT detected a problem with the database volume name. Effect. INITENV stops. Recovery. Resolve the naming conflicts; then rerun INITENV. INITHDB ERROR: DBINIT error error-number reported. Please contact your Tandem support representative for assistance. Cause. An internal error occurred during the initialization of the host database. Effect. INITHDB stops. Recovery. Contact your service provider, and provide all relevant information: Descriptions of the problem and accompanying symptoms Details from the messages generated Supporting documentation such as the $ZPHI Event Management Service (EMS) 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. After the error is corrected, rerun INITENV. 1-18

35 INITENV Messages INITHDB 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. For a description of the error code displayed in this message, see Chapter Appendix, B File-System Errors in Operator Messages Manual. Correct the file-system error; then rerun INITENV. INITHDB ERROR: Insufficient space exists on requested database volume. Please correct the problem or choose another volume, then run INITENV again. Cause. Not enough space is available on the requested volume to initialize the DSM/SCM database. Effect. INITENV stops. Recovery. Either clean up the volume to free additional space, or choose another volume for the DSM/SCM database. INITHDB ERROR: SQLCOMP error error-number reported while attempting to compile file filename1. See listing filename2 for details. Please correct the problem, then run INITENV again. Cause. An error occurred during the compilation of the DSM/SCM database. Effect. INITENV stops. Recovery. For details on the specific error, check the SQLCOMP output listing; then correct the error and rerun INITENV. 1-19

36 INITENV Messages INITHDB 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. If you cannot diagnose the problem, contact your service provider, and provide all relevant information: Descriptions of the problem and accompanying symptoms Details from the messages generated Supporting documentation such as the $ZPHI Event Management Service (EMS), 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. After the error is corrected, rerun INITENV. INITHDB WARNING: The SQL compiles may take a long time. You may BREAK out of this function at any time and resume later by running INITENV again. Cause. This informational message indicates that the compilation of the database is about to begin. Effect. None, but special Break key processing is enabled during the compile, letting you leave INITENV while the compile is in progress. Restart INITENV after the compile finishes or while it is still running. Recovery. Either press the Break key to leave INITENV and allow the compile to run in the background, or press Return to run the compile in the foreground. 1-20