System Generation Manual for G-Series RVUs Abstract This manual describes how to use the SYSGENR program on G-series release version updates (RVUs) to create a new set of operating system files. It describes the contents of the CONFTEXT configuration file and how to run the SYSGENR program to create a new operating system image. This manual is intended for system managers, analysts, and support persons responsible for installing and configuring HP NonStop™ S-series servers.
Document History Part Number Product Version Published 132134 SYSGEN G02 May 1997 136016 SYSGEN G03 August 1997 422998-001 SYSGEN G06 August 1999 429591-001 SYSGEN G06 April 2001 523407-001 SYSGEN G06 August 2002
System Generation Manual for G-Series RVUs Glossary Index What’s New in This Manual v Manual Information v New and Changed Information Figures Tables v About This Manual vii Who Should Use This Manual vii What’s in This Manual vii Where to Get More Information viii Your Comments Invited ix Notation Conventions x 1.
2. Contents of the CONFTEXT File Contents 2.
3. Using Preprocessing Commands (continued) Contents 3. Using Preprocessing Commands (continued) Combining ASSIGNs and PARAMS for the Number of SIDs and SITs You Want A Helpful Command File 3-24 4. Running DSM/SCM and SYSGENR Overview 4-1 What Happens When You Run DSM/SCM 4-2 Creating a System Image Disk (SID) 4-3 Responding to Further DISKGEN Prompts 4-8 Creating a System Image Tape (SIT) 4-9 Responding to Further BACKUP Prompts 4-11 Contents of the New Operating System 4-12 5.
B. XLLINK Messages Contents SYSGENR Message Descriptions A-2 B. XLLINK Messages Items Needed Before Contacting Your Service Provider XLLINK Message Descriptions B-1 B-1 C. nld Messages Items Needed Before Contacting Your Service Provider nld Message Descriptions C-1 C-1 D. Comparing SYSGENR for D-Series RVUs With SYSGENR for G-Series RVUs Changes to the System Configuration Utilities D-1 Changes to the ALLPROCESSORS Paragraph D-2 Glossary Index Figures Figure D-1.
What’s New in This Manual Manual Information System Generation Manual for G-Series RVUs Abstract This manual describes how to use the SYSGENR program on G-series release version updates (RVUs) to create a new set of operating system files. It describes the contents of the CONFTEXT configuration file and how to run the SYSGENR program to create a new operating system image.
What’s New in This Manual New and Changed Information System Generation Manual for G-Series RVUs —523407-001 vi
About This Manual This manual describes how to use the SYSGENR program on G-series RVUs to create a new set of operating system files. It describes the contents of the CONFTEXT configuration file and how to run the SYSGENR program to create a new operating system image. Who Should Use This Manual This manual is written for system managers, analysts, and support persons who are responsible for installing and configuring HP NonStop S-series servers.
Where to Get More Information About This Manual Section or Appendix Title Description B XLLINK Messages Lists the messages generated by XLLINK and displayed in the CONFLIST output file of SYSGENR. C nld Messages Lists the messages generated by NLD, the native mode linker program called by SYSGENR to build the SYSCLR and SYSDP2 files.
Your Comments Invited About This Manual • Guardian Disk and Tape Utilities Reference Manual This manual describes how to use the disk and tape utilities for the HP NonStop Kernel operating system. The utilities are BACKCOPY, BACKUP, Disk Compression Program (DCOM), Disk Space Analysis Program (DSAP), RESTORE, and TAPECOM. This manual is written for system operators, system managers, and all other users of the disk and tape utilities.
Notation Conventions About This Manual • Sending an e-mail message to the address included on the form. We'll immediately acknowledge receipt of your message and send you a detailed response as soon as possible. Be sure to include your name, company name, address, and phone number in your message. If your comments are specific to a particular manual, also include the part number and title of the manual. Many of the improvements you see in manuals are a result of suggestions from our customers.
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 may be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: LISTOPENS PROCESS { $appl-mgr-name } { $process-name } ALLOWSU { ON | OFF } | Vertical Line.
Notation for Messages About This Manual a blank line. This spacing distinguishes items in a continuation line from items in a vertical list of selections. For example: ALTER [ / OUT file-spec / ] DISK [ , attribute-spec ]... Notation for Messages The following list summarizes the notation conventions for the presentation of displayed messages in this manual. Bold Text. Bold text in an example indicates user input entered at the terminal. For example: ENTER RUN CODE ?123 CODE RECEIVED: 123.
Change Bar Notation 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. A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces.
Change Bar Notation About This Manual System Generation Manual for G-Series RVUs —523407-001 xiv
1 SYSGENR Overview This section provides an overview of SYSGENR, the system generation program for HP NonStop S-series servers, and the components needed by SYSGENR to create a new set of operating system files.
Online Configuration With SCF SYSGENR Overview Online Configuration With SCF The Subsystem Control Facility (SCF) is the online configuration facility for G-series RVUs. After DSM/SCM runs SYSGENR to create the basic configuration, you use SCF to configure the rest of the operating system objects. SCF is documented in the SCF Reference Manual for G-Series RVUs. The following manuals describe how to configure specific objects. To configure... Refer to...
Changing the System Configuration Offline With DSM/SCM SYSGENR Overview Changing the System Configuration Offline With DSM/SCM Most system configuration changes are now performed online using the Subsystem Control Facility (SCF). Refer to the SCF Reference Manual for G-Series RVUs or the product-specific configuration or SCF manual. For G-series RVUs, changes to the CONFTEXT file require you to change the system configuration offline. To bring CONFTEXT file changes into effect, a system load is needed.
Input Files for SYSGENR SYSGENR Overview • XLLINK (TNS linker program) – Links (file code 100) accelerated TNS system files to create system code and system library files for the new system image.
Input Files for SYSGENR SYSGENR Overview CONFAUX File The CONFAUX file is an EDIT-format file created by DSM/SCM. The CONFAUX file contains a list of process code files and a series of statements that define the locations of the system code and system library files that are used by the CONFTEXT file and SYSGENR to build the new operating system files.
Optional Preprocessing Commands for SYSGENR SYSGENR Overview and system library. To accelerate user-created program files before running SYSGENR, you run the Accelerator program specifying the LINKABLE option. For information on how to run the Accelerator program, see the Accelerator Manual. Optional Preprocessing Commands for SYSGENR Using DSM/SCM, you can enter ASSIGN and PARAM commands to specify unique run-time parameters that can override your default system parameters.
System Management Considerations SYSGENR Overview System Image Tape (SIT) DSM/SCM allows you to optionally create a system image tape (SIT) as an emergency backup. Caution. You should perform a SIT load only in an emergency and on the advice of a service provider. A SIT load is a destructive function that erases all files on the system disk, including all information in the system configuration database.
Comparing DISKGEN to BACKUP SYSGENR Overview that you must restart DSM/SCM) and let it run to completion to ensure that your operating system file set is complete. You can press the Break key to exit SYSGENR while it is running and use the terminal for another purpose (for instance, using Peruse to monitor progress on the CONFLIST file). To return to SYSGENR, type PAUSE at the prompt and press Enter. SYSGENR displays a prompt for the next step when it has finished processing the current step.
Disaster Recovery SYSGENR Overview Disaster Recovery To ensure proper recovery from a disaster, you must always have a copy of the current system image available at a safe location.
Disaster Recovery SYSGENR Overview System Generation Manual for G-Series RVUs —523407-001 1- 10
2 Contents of the CONFTEXT File This section describes the format and contents of the $DSMSCM.SYS.CONFTEXT configuration file. It includes the following topics: Topic Page DEFINES Paragraph (Optional) 2-1 ALLPROCESSORS Paragraph 2-2 The CONFTEXT file is an EDIT-format configuration file that contains one or two paragraphs: DEFINES and ALLPROCESSORS.
Contents of the CONFTEXT File ALLPROCESSORS Paragraph text-string is a variable-length sequence of ASCII characters, including spaces. As used by SYSGENR, text-string is one or more file names as listed in CONFAUX file. Do not include a pound sign (#) within text-string, because #; signals the end of a DEFINES entry. Do not use the word “ALLPROCESSORS” in a DEFINES entry. The word “ALLPROCESSORS” signals the end of the DEFINES paragraph and the beginning of the ALLPROCESSORS paragraph.
ALLPROCESSORS Paragraph Contents of the CONFTEXT File Each entry is described in alphabetic order in Table 2-1 on page 2-4. You begin the ALLPROCESSORS paragraph with the following statement: ALLPROCESSORS: The syntax for an ALLPROCESSORS paragraph entry is shown here. ALLPROCESSORS-term [ value ] ; ALLPROCESSORS-term is one of the names listed in Table 2-1 on page 2-4. value is described in the definitions of the entries in Table 2-1. ; terminates the entry.
COLDLOAD_DISK_LOWPIN (Optional) Contents of the CONFTEXT File Table 2-1. ALLPROCESSORS Paragraph Entries and Descriptions ALLPROCESSORS Entry Required or Optional? COLDLOAD_DISK_LOWPIN Optional Configures the system disk to run at a low PIN so that it is visible from C-series systems. FILES_TO_COPY_TO_NEW_ SYSTEM Required Specifies RVU-dependent or systemdependent object files, data files, configuration files, and millicode files to be included in the new system.
Contents of the CONFTEXT File FILES_TO_COPY_TO_NEW_SYSTEM (Required) FILES_TO_COPY_TO_NEW_SYSTEM (Required) You use this entry to specify RVU-dependent or system-dependent object files, data files, configuration files, and optional-product millicode files to be included in the new operating system. When creating the system image disk or tape, SYSGENR copies the files to the $SYSTEM.SYSnn subvolume specified by the SYSTEM_VOLUME_SUBVOL entry, keeping their security settings.
Contents of the CONFTEXT File FORMATTER_TEMPLATE_FILES (Required) The following example is a partial list of the files in a FILES_TO_COPY_TO_NEW_SYSTEM entry. They are listed in the order in which DSM/SCM places them in the TANDEM^FILES^TO^COPY portion of the CONFAUX file. FILES_TO_COPY_TO_NEW_SYSTEM $S11B.CONFIG.RLSEID, $S11B.ZSNMPMGR.SNMPTMUX, $S11B.ZCEV.CEVETF, $S11B.ZCEV.CEVEVX, $S11B.ZCEV.CEVINX, … $S11B.ZSECURE.USERID RENAME_TO SYSTEM.USERID, $S11B.ZSECURE.USERIDAK RENAME_TO SYSTEM.
INITIAL_COMMAND_FILE or INITIAL_COMINT_INFILE (Required) Contents of the CONFTEXT File CIIN file) if both the CIIN file is specified in the CONFTEXT file and the CIIN disabled option is not checked (CIIN is enabled) in the TSM client software. When all the commands in the CIIN file have been executed, the startup TACL process terminates. The CIIN file contains a limited set of commands that reload the remaining processors and start a TACL process pair on the system console.
Contents of the CONFTEXT File INITIAL_COMMAND_FILE or INITIAL_COMINT_INFILE (Required) SYSGENR copies the file specified in this entry to the new SYSnn subvolume on the system disk and renames it CIIN. If you do not specify a CIIN file in the INITIAL_COMMAND_FILE or INITIAL_COMINT_INFILE entry, the following occurs: • • The operating system does not look for the startup file (SYSnn.CIIN) at system startup; therefore, you cannot simply copy your startup file to the SYSnn subvolume and name it CIIN.
INITIAL_COMMAND_FILE or INITIAL_COMINT_INFILE (Required) Contents of the CONFTEXT File in the TSM client software (the System Startup dialog box of the TSM Low-Level Link Application). Table 2-2. Results of Startup TACL Process CONFTEXT CIIN Entry and CIIN File CIIN Option Results 1. CONFTEXT file has CIIN entry and file is available in specified location. Enabled CIIN is executed by initial (startup) TACL process. Upon completion, this TACL process terminates.
STANDARD_MICROCODE (Required) Contents of the CONFTEXT File Example CIIN File for G-Series RVUs Comment Comment Comment Comment ----- This is the initial command input (CIIN) file for the system. CIIN is specified in your CONFTEXT file and the CIIN disabled option is not checked in the System Startup dialog box, the initial TACL process will read this file and then terminate.
Contents of the CONFTEXT File SUPER_SUPER_IS_UNDENIABLE (Optional) semicolon (;) after the last file name listed. The following example is a list of the files in a STANDARD_MICROCODE entry for a G-series RVU. STANDARD_MICROCODE $S11B.ZLIBSTD.EHHI8, $S11B.ZLIBSTD.EHLO8, $S11B.ZLIBSTD.KUFH8, $S11B.ZLIBSTD.DBOOTVER, $S11B.ZLIBSTD.DSKBOOT, $S11B.ZLIBSTD.TAPBOOT, $S11B.ZLIBSTD.DISKPRT1, $S11B.ZLIBSTD.DISKPRT2, $S11B.ZLIBSTD.TAPEPRT1, $S11B.ZLIBSTD.
Contents of the CONFTEXT File • SYSTEM_PROCESS_CODE_FILES (Required) You must list the SYSTEM_LIBRARY_CODE_FILES entry first, followed by the name of each library code file required for your system. For multiple files, enter a comma (,) after each file name and a semicolon (;) after the last file name listed. The following example is a partial list of the files in a SYSTEM_LIBRARY_CODE_FILES entry.
Contents of the CONFTEXT File SYSTEM_PROCESS_LIBRARY_FILES (Required) SYSTEM_PROCESS_LIBRARY_FILES (Required) This entry defines user library files for DP2. Through SYSGENR, the native linker program (NLD) links these files to the DP2 file. If you use the CONFAUX file (the normal procedure), you need enter only the installation descriptor TANDEM^PROCESS^LIBRARY^FILES. The form of this entry is shown here.
TAPE_LABEL_PROCESSING (Optional) Contents of the CONFTEXT File Only if you are running SYSGENR outside of DSM/SCM should you change the CONFTEXT configuration file to specify the new SYSnn subvolume. The syntax of this entry is shown here. SYSTEM_VOLUME_SUBVOL $SYSTEM.SYSnn; nn is a user-specified 2-digit octal number in the range %00 through %77. To determine the location of the current SYSnn subvolume, use the SYSINFO command. Following is an example display.
3 Using Preprocessing Commands This section lists and provides the syntax for helpful ASSIGN and PARAM commands that you can create using the Distributed System Management/Software Configuration Manager (DSM/SCM). Also included in this section is a sample command file for a TNS/R system. When using DSM/SCM, HP recommends using the information in this section only under the advice of a service provider, usually in order to help resolve a migration problem.
Using Preprocessing Commands ASSIGN Command ASSIGN Command You use the TACL ASSIGN command to connect a physical file name to a logical file name. Specifically, you can use an ASSIGN command to: • • • Specify the tape drive to be used by SYSGENR when making the system image tape Specify the location of a program to be used by SYSGENR Specify the location where SYSGENR is to save a work file after SYSGENR ends The syntax for the ASSIGN command is shown here. ASSIGN filename, [[[\system.]$volume.
Assigning a Tape Drive Using Preprocessing Commands Assigning a Tape Drive You can use an ASSIGN command to specify the tape drive that SYSGENR uses to create a system image tape (SIT). As a result, SYSGENR does not prompt you for the tape drive name; it writes to the tape drive you have specified in the ASSIGN command. The syntax is shown here. ASSIGN SYSGEN^TAPE, [\system.]$tape [\system.]$tape is the physical system and file name of the tape drive you want SYSGENR to use.
Using Preprocessing Commands Making SYSGENR Work Files Permanent Examples • The following example specifies that SYSGENR use a remote version of BACKUP: ASSIGN SYSGEN^BACKUP, \EAST.$SYSTEM.ZUTIL.BACKUP • The following example specifies that, for a migration from D40 to G00, SYSGENR run G00 BIND from the PDTSYS subvolume on the volume where installation tools are located, instead of the D40 BIND at the default location at $SYSTEM.SYSTEM: ASSIGN SYSGEN^BINDER, $S11B.PDTSYS.
Making SYSGENR Work Files Permanent Using Preprocessing Commands Table 3-1 gives the names and contents of the SYSGENR work files. Table 3-1. SYSGENR Work Files (page 1 of 2) Work File Name Contents SYSCLR The combined native system code and native system library. SYSGENR renames this file-code 700 file TSYSCLR and copies it to the system image disk (SID) or system image tape (SIT). SYSCOD00 The TNS and accelerated portion of system code.
Making SYSGENR Work Files Permanent Using Preprocessing Commands Table 3-1. SYSGENR Work Files (page 2 of 2) Work File Name Contents SYSGENT A list of all SYSTEM_LIBRARY_CODE_FILES to be sent to NLD, the native mode linker, to build SYSCLR. SYSGENU A list of all files to be sent to NLD, the native mode linker, to build the DP2 process. SYSGENW The OSCONFIG database, which is built by SYSGENR and contains SPIFF and SWID records. SYSLIB00 The TNS and accelerated portion of system library.
Using Preprocessing Commands PARAM Command [[[\system.]$volume.]subvolume.]filename can be either the work-file location to be used by SYSGENR or any valid file name that you desire. If you supply a partial file name, SYSGENR expands the file name using the default information in the RUN SYSGENR command. Examples • In the following example, SYSGENR makes permanent work files from the object files for system code and system library: ASSIGN SYSCOD00, $BCX.SYSDATA.FILEA ASSIGN SYSLIB00, $BCX.SYSDATA.
PARAM Command Using Preprocessing Commands • To delete an individual parameter, enter the following command: > CLEAR PARAM paramname • To delete all PARAMS and ASSIGNS in effect, enter the following command: > CLEAR ALL See the TACL Reference Manual for more information on the PARAM command. SYSGENR uses for the PARAM command are summarized in Table 3-2 and detailed in the following pages. Table 3-2.
Using Preprocessing Commands PARAM BACKUPONLY PARAM BACKUPONLY If you have not entered a PARAM SYSGEN^DISKGENPARAM or an ASSIGN SYSGEN^TAPE command, you can use this PARAM to request that SYSGENR not send you a prompt for a system image on disk (SID) before the prompt for a system image tape (SIT). If you do not specify this PARAM, SYSGENR issues DISKGEN prompts. The syntax is shown below.
Using Preprocessing Commands PARAM EXTENTSIZE NRZI | 800 specifies the nonreturn-to-zero tape formatting standard, equivalent to a recording density of 800 bits/inch. PE | 1600 specifies the phase-encoded tape formatting standard, equivalent to a recording density of 1600 bits/inch. GCR | 6250 specifies the group-code recording tape formatting standard, equivalent to a recording density of 6250 bits/inch.
Using Preprocessing Commands PARAM PROMPT PARAM PROMPT You can use this PARAM to specify the BACKUP prompt after SYSGENR asks, “Do you want to write a system image tape?” Use the NO option of this PARAM if you want SYSGENR to write a SIT on a tape drive that has an automatic tape changer. The syntax is shown below. PARAM PROMPT { YES | NO } YES (the default) causes BACKUP to give its standard prompt after you enter BACKUP parameters: > $tapename: Not Ready? Press return.
PARAM REUSEDP2 Using Preprocessing Commands PARAM REUSEDP2 You can use this PARAM to tell SYSGENR to reuse a previously built SYSDP2 file. Doing this saves system generation time by not invoking BIND, XLLINK, and NLD to rebuild this file. The syntax is shown below. > PARAM REUSEDP2 { 1 | YES } 1 | YES causes the SYSDP2 file to be reused. You must also enter the following ASSIGN command to tell SYSGENR where the SYSDP2 file is located: ASSIGN SYSDP2, [[$volume.]subvolume.
Using Preprocessing Commands PARAM REUSESYSFILES ALL | YES | 3 causes SYSGENR to reuse the previously built system code file (SYSCOD00) and system library file (SYSLIB00). In addition, SYSGENR reuses the previously built native system code and system library file (SYSCLR). You must also enter the following ASSIGN commands to tell SYSGENR where the three files are located: ASSIGN SYSCOD00, [[$volume.]subvolume.]filename ASSIGN SYSLIB00, [[$volume.]subvolume.]filename ASSIGN SYSCLR, [[$volume.]subvolume.
PARAM REUSETEMPLATES Using Preprocessing Commands PARAM REUSETEMPLATES If you haven’t made changes to the EMS formatter template files, you can use this PARAM to specify that SYSGENR reuse the EMS resident and nonresident template files. Doing this saves system generation time by not invoking TEMPLI to rebuild these files. The syntax is shown below. PARAM REUSETEMPLATES YES YES causes SYSGENR to reuse the resident and nonresident EMS templates files.
Using Preprocessing Commands PARAM SYSGEN^BACKUPPARAM PARAM SYSGEN^BACKUPPARAM You can use this PARAM to specify the tape device (and tape options) to which the system image must be written. Using this PARAM overrides any of the following commands, regardless of when entered: • • • • • ASSIGN SYSGEN^TAPE PARAM TAPEMODE PARAM DENSITY PARAM UNLOAD PARAM PROMPT The syntax is shown below. PARAM SYSGEN^BACKUPPARAM " [\system.
Using Preprocessing Commands PARAM SYSGEN^DISKGENPARAM Examples • The following example specifies the density and block size for one system image to be copied to $TAPE01, and also specifies that the tape be kept online at the end of the operation: > PARAM SYSGEN^BACKUPPARAM "$TAPE01, DENSITY 1600, & BLOCKSIZE 28, NOUNLOAD !" • The following example specifies the block size and inhibits SYSGENR from displaying any BACKUP prompts: > PARAM SYSGEN^BACKUPPARAM "TAPE01, BLOCKSIZE 28, NOPROMPT !" Refer to T
Using Preprocessing Commands PARAM TAPEMODE LISTALL specifies that all files copied are listed to the terminal specified by the TERM option in the RUN SYSGENR command. This defaults to the TACL home terminal. ! indicates that you do not wish to be prompted for further responses.
Using Preprocessing Commands PARAM UNLOAD TAPEMODE with an ASSIGN SYSGEN^TAPE command, SYSGENR produces a SIT without operator intervention. The syntax is shown below. PARAM TAPEMODE { STARTSTOP | STREAM } STARTSTOP specifies that the tape drive is to operate in start-stop mode. One record at a time is written to the tape. STREAM specifies that the tape drive is to be operated in stream mode. One block of the size specified by the BLOCKSIZE option is written to the tape at a time.
Using Preprocessing Commands PARAM WORKFILE NO specifies that the SIT is to remain online after it has been created. Use this option if you intend to immediately load the system image. Caution. You should perform a SIT load only in an emergency and on the advice of a service provider. A SIT load is a destructive function that erases all files on the system disk, including all information in the system configuration database.
Using Preprocessing Commands PARAM XLLINKCPU Example The following example requests that SYSGENR save its work files on $DISK1.SYSSAV: > PARAM WORKFILE $DISK1.SYSSAV PARAM XLLINKCPU You can use this PARAM to specify the processors in which XLLINK will run. Using this PARAM allows you to improve SYSGENR performance by specifying that XLLINK run in processors other than the processor in which SYSGENR is running, ideally in processors that are not very busy. The syntax is shown below.
Using Preprocessing Commands Combining ASSIGNs and PARAMS for the Number of SIDs and SITs You Want Combining ASSIGNs and PARAMS for the Number of SIDs and SITs You Want Table 3-3 lists the different combinations of system image disks (SIDs) and system image tapes (SITs) that you can request with the following PARAMs or ASSIGNs: • • • PARAM SYSGEN^DISKGENPARAM PARAM SYSGEN^BACKUPPARAM ASSIGN SYSGEN^TAPE Table 3-3. SID and SIT Options (page 1 of 3) No.
Using Preprocessing Commands Combining ASSIGNs and PARAMS for the Number of SIDs and SITs You Want Table 3-3. SID and SIT Options (page 2 of 3) No. Quantity PARAM Command SYSGENR Processing Sequence 4. 1 or more SIDs and 1 or more SITs PARAM SYSGEN^DISKGEN PARAM"text" 1. 2. PARAM SYSGEN^BACKUPP ARAM "text" 3. 4. 5. 0 SIDs and 1 SIT ASSIGN SYSGEN^TAPE, $tapename 1. Create the SIT without issuing a BACKUP prompt. 6. 1 SID and no SITs PARAM SYSGEN^DISKGEN PARAM"text ! " 1. 2.
Using Preprocessing Commands Combining ASSIGNs and PARAMS for the Number of SIDs and SITs You Want Table 3-3. SID and SIT Options (page 3 of 3) No. Quantity PARAM Command SYSGENR Processing Sequence 10. 1 SID and 1 or more SITs PARAM SYSGEN^DISKGEN PARAM"text" 1. Create the SID without issuing a prompt. 2. Prompt for another SID until you specify NO. Create the SIT without issuing a prompt. Prompt for another SIT until you specify NO. PARAM SYSGEN^BACKUPP ARAM "text " 11.
Using Preprocessing Commands A Helpful Command File A Helpful Command File To ensure a uniform system-generation environment, you can create a command file containing the desired ASSIGN, PARAM, and RUN SYSGENR commands. The following is a sample command file for a TNS/R system. This command file is useful only if you plan to run SYSGENR outside of DSM/SCM, an act that is not recommended.
4 Running DSM/SCM and SYSGENR This section describes how to run the Distributed Systems Management/Software Configuration Manager (DSM/SCM), which in turn runs SYSGENR; lists SYSGENR prompts and messages that appear during its run; and describes how to create a system image disk (SID) and a system image tape (SIT). This section also lists the contents of the new operating system created by SYSGENR.
Running DSM/SCM and SYSGENR What Happens When You Run DSM/SCM DSM/SCM automatically runs SYSGENR when creating a new configuration. After you are certain the CONFTEXT file is free of errors, you must run DSM/SCM to generate a new operating system. What Happens When You Run DSM/SCM After using DSM/SCM to specify all needed PARAMs and ASSIGNs, you are ready to run DSM/SCM, which automatically runs SYSGENR. To start DSM/SCM, perform the following steps: 1. Be sure that ZDSMSCM is the current subvolume. 2.
Running DSM/SCM and SYSGENR Creating a System Image Disk (SID) _L[IST] E[DIT] / OUT CONFLIST, NOWAIT / A[LL] Or, you can save the SYSGENF file by entering the following ASSIGN before running SYSGENR: ASSIGN SYSGENF, $volume.subvolume.filename Creating a System Image Disk (SID) This subsection applies only if you are running SYSGENR outside of DSM/SCM, an action that is not recommended.
Creating a System Image Disk (SID) Running DSM/SCM and SYSGENR If you enter “Y” or “Yes”, you receive the following prompt: SUPPLY THE DISK INFORMATION AND DISKGEN OPTIONS: {[\system.][.SYSNN], [ ] [ ! ]} To respond, use the syntax shown below. [\syst.]$vol.[SYSnn], DISKGEN-option [, NOLASTMOD] [, LISTALL ] [\syst.]$vol.[SYSnn] is the location where SYSGENR should write the SID.
Creating a System Image Disk (SID) Running DSM/SCM and SYSGENR [[[ \system.]$volume.]subvolume.]file-id and is one or more files of the following form: { ( fileset [ , fileset ]… ) | *.*.* } As a wild-card character, you can use an asterisk (*) in place of the volume, subvolume, or file name. qualifier is one or any combination of the following: [ EXCLUDE fileset-list ] [ START filename ] [ WHERE expression ] Each qualifier value can be specified only once for a given fileset.
Creating a System Image Disk (SID) Running DSM/SCM and SYSGENR expression can be OWNER = userid timestamp-field conditional time-value FILECODE conditional number EOF conditional number OWNER = user-id specifies one or all user IDs in a group: {group-name.
Creating a System Image Disk (SID) Running DSM/SCM and SYSGENR where hh (hour) is an integer from 0 through 23; mm (minute) and ss (second) are 2-digit integers from 00 through 59. The default for time is 0:00:00, that is, midnight. FILECODE conditional number specifies selection of a file based on its file code.
Running DSM/SCM and SYSGENR • Responding to Further DISKGEN Prompts In the following example, DISKGEN copies to \DATA.$SYSTEM.SYS05 (connected to this system by Expand) all updated files, excluding files on the SYSTEM subvolume, and sends to the home terminal a list of all files copied: \DATA1.$SYSTEM.SYS05, *.*.* EXCLUDE SYSTEM.*, LISTALL • In the following example, DISKGEN runs only once, to make a copy of the justmodified CONFLIST and OSIMAGE files: $SYSTEM.
Running DSM/SCM and SYSGENR Creating a System Image Tape (SIT) Creating a System Image Tape (SIT) This subsection applies only if you are running SYSGENR outside of DSM/SCM, an action that is not recommended. DSM/SCM has its own way of creating a SIT. Caution. You should perform a SIT load only in an emergency and on the advice of a service provider. A SIT load is a destructive function that erases all files on the system disk, including all information in the system configuration database.
Running DSM/SCM and SYSGENR Creating a System Image Tape (SIT) BACKUP-option is one of the following subset of options to the BACKUP program: BLOCKSIZE n DENSITY { 800 | NRZI} {1600 | PE } {6250 | GCR } IGNORE LISTALL NOPROMPT NOUNLOAD OPEN TAPEMODE { STARTSTOP | STREAM } For a complete description of these BACKUP options, refer to the Guardian Disk and Tape Utilities Reference Manual. Using a BLOCKSIZE greater than the default of 2 speeds the tape-writing process and produces a more compact tape.
Running DSM/SCM and SYSGENR Responding to Further BACKUP Prompts Responding to Further BACKUP Prompts After entering BACKUP options, the BACKUP banner appears and the system image is written to tape: BACKUP Program - T9074ACR (26MAY95) Copyright Tandem Computers 1981-1994 $tape : Not Ready? Mount a reel of tape (with a write-enable ring) on the appropriate tape drive and bring it on line. Press RETURN twice on the terminal to start the backup operation.
Running DSM/SCM and SYSGENR Contents of the New Operating System Contents of the New Operating System The operating system created by SYSGENR contains the following files: • • • Files located in the $SYSTEM.
5 Reading the CONFLIST Report This section lists and describes the contents of the SYSGENR output file. Overview After SYSGENR terminates, the OUT file, by convention called the CONFLIST report, contains all SYSGENR processing activity. Table 5-1 lists the report sections, in the order in which they appear. As SYSGENR processes each line of the CONFTEXT input file, it writes any action taken to the CONFLIST output file. It then creates maps describing how it builds the new operating system image.
Overview Reading the CONFLIST Report Table 5-1.
CONFAUX File Reading the CONFLIST Report CONFAUX File SYSGENR begins by reading the CONFAUX file and listing it to the CONFLIST file. Following is a partial example. SYSGEN - T9023 GUARDIAN 90 - $S11B.A000001.CONFAUX 15 APR 1996 11:19 PAGE 1 … 1. 2. 3. ! INSTALL - T9612C30 - (10APR95) System \EAST, Release D30.00 ! Date 11 Apr 1996, 11:39:43 ! COPYRIGHT TANDEM COMPUTERS INCORPORATED 1985, 1987-1993 … 9. 10. 11. 12. 13. ! DEFINES: TANDEM^LIBRARY^CODE^FILES = $S11B.ZGUARD.TMIOPJ, $S11B.ZGUARD.
Files Going to the Native Mode Linker Reading the CONFLIST Report Files Going to the Native Mode Linker SYSGENR creates a list of native (file code 700) TNS/R system files from the CONFAUX file entry SYSTEM_LIBRARY_CODE_FILES. Following is a partial example. FILES GOING TO THE NATIVE MODE LINKER 15 APR 1996 11:19 PAGE 41 \EAST.$S11B.ZGUARD.TMIOPJ \EAST.$S11B.ZGUARD.TMIOPMD \EAST.$S11B.ZGUARD.TXIOINT.... \EAST.$S11B.ZGUARD.
XLLINK Log Reading the CONFLIST Report In addition, SYSGENR runs BIND twice to join the TNS code portions of all TNS file code 100 files, first for system code and then for system library. Only the TNS code portions (not the accelerated portions) of system code and system library are bound together in this step. The resulting two files (one for system code and one for system library) are referred to as TNS object files. For each object file created, Binder produces a log of its activities.
Reading the CONFLIST Report • Files Going to the Native Mode Linker Creates system library by joining the combined accelerated code for system library with the TNS object file created by BIND to produce the accelerated system library file SYSLIB00. The following is a partial example of an error-free XLLINK listing for system code. XLLINK LOG - [$s11b.PDTSYS.XLLINK] 15 APR 1996 11:19 PAGE 53 XLLINK - T6166C30 - (Aug 2 1993 13:36:02) Copyright Tandem Computers, Inc.
Millicode Map in Memory Order Reading the CONFLIST Report Millicode Map in Memory Order SYSGENR then lists the TNS/R system millicode in memory order. Note that an entrypoint value starting with “80” identifies a KSEG0 (NonStop Kernel text) address for a millicode routine in an EHHIn millicode file. Similarly, an entrypoint value starting with “7E” identifies a KUSEG (resident text) address for a millicode routine in a KUFHn millicode file.
System Spaces Map in Memory Order Reading the CONFLIST Report System Spaces Map in Memory Order SYSGENR generates a system spaces map from the files specified under SYSTEM_LIBRARY_CODE_FILES in the CONFTEXT file and lists the accelerated procedures for system code and system library. The column headings and their meanings are as follows: Column Heading Meaning PROCEDURE NAME The name of the system code or system library procedure. % BASE The base address (in octal) of the procedure within the MP.
Reading the CONFLIST Report System Spaces Map in Alphabetic Order Following is a partial example of a TNS/R system memory order map for the accelerated procedures in system code and system library. SYSTEM SPACES -- MEMORY ORDER MAP 15 APR 1996 11:19 PAGE 83 PROCEDURE NAME % BASE %ENTRY ATTR MAP %SEG MP.%ID %PEP NAT BASE NAT ENTRY TFDS_HALT_ 000756 000764 PR 0 00005 SC.05 020 8042.0000 8042.0028 7A6A.0BA0 TFDS_FREEZE_ 000756 000772 PRE 0 00005 SC.05 021 8042.0000 8042.0054 7A6A.
Native System Spaces Map in Alphabetic Order Reading the CONFLIST Report Native System Spaces Map in Alphabetic Order After producing the memory order and alphabetic maps of TNS system spaces, SYSGENR produces a map of native system spaces in alphabetic order by procedure name. The column headings and their meanings are as follows: Column Heading Meaning PROCEDURE NAME The name of the system code or system library procedure. NAT BASE The native base address (in hexadecimal) of the procedure.
Native System Spaces in RPDR Order Reading the CONFLIST Report Native System Spaces in RPDR Order After producing the alphabetic map of native system spaces, SYSGENR then produces a map of native system code and native system library, based on the table of Run-time Procedure Descriptor Records (RPDR) built earlier by NLD when creating the SYSCLR file. This map information is useful for debugging purposes.
Native System Spaces in RPDR Order Reading the CONFLIST Report follows this map indicates the starting byte address of each segment that native system space occupies in the OSIMAGE. NATIVE SYSTEM SPACES NAT_ENTRY ATTR -- RPDR LISTING PC FRAMEOFFSET 7C00.03F0 none 31 00000000 7C00.0400 none 31 00000000 7C00.0410 none 31 00000000 7C00.0420 none 31 00000000 … 7C01.04A0 P 31 00000100 … 809D.AF34 PR 31 00000020 … DISC ADDRESSES: SCR.00: %000075.134000 SCR.03: %000103.134000 SCR.06: %000111.134000 SCR.
System Process Load Map in Memory Order Reading the CONFLIST Report System Process Load Map in Memory Order SYSGENR generates a system process load map from the accelerated object files specified under SYSTEM_PROCESS_CODE_FILES in the CONFTEXT file, and lists the procedures. The memory order map lists all these user code procedures in ascending order by memory location. The column headings and their meanings are as follows: Column Heading Meaning PROCEDURE NAME The name of the user code procedure.
System Process Load Map in Alphabetic Order Reading the CONFLIST Report System Process Load Map in Alphabetic Order The alphabetic-order system process load map has the same columns as the memory order process load map, except entries are listed in an alphabetic order by procedure name. The following is a portion of an alphabetic-order load map for the TNS/R system process named LINKMON in user code.
Native Load Map in Alphabetic Order Reading the CONFLIST Report Native Load Map in Alphabetic Order After producing maps of TNS user code, SYSGENR produces maps of native user code. For each native user code program object file specified under SYSTEM_PROCESS_CODE_FILES in the CONFTEXT file, SYSGENR displays an alphabetic-order list of all its procedures.
Native Load Map in RPDR Order Reading the CONFLIST Report Native Load Map in RPDR Order After producing the first alphabetic map of a native user code program object file, SYSGENR then produces (for that same program object file) entry-point addresses to each procedure, based on the table of Run-Time Procedure Descriptor Records (RPDR) built earlier by NLD.
TEMPLI Log Reading the CONFLIST Report TEMPLI Log SYSGENR runs TEMPLI to generate the Event Management Service (EMS) resident and nonresident template files from the template object files specified in the CONFTEXT file. It then places the resident template file SYSGENK in the operating system image and the nonresident template file SYSGENL in the SYSnn subvolume specified by the SYSTEM_VOLUME_SUBVOL entry. TEMPLI warning and error messages are documented in the DSM Template Services Manual.
Device Control Table Reading the CONFLIST Report Device Control Table SYSGENR produces a device control table showing, for each device in the minimal system, the device number and name, the primary and the backup process IDs (cpu,pin), the device type and subtype, and the RSIZE value. The following is an example of a device control table for a TNS/R system.
SIV Listing Reading the CONFLIST Report SIV Listing The System Interrupt Vector (SIV) listing is a table of system interrupt vector addresses for the interrupt handlers located in memory. The column headings and their meanings are as follows: Column Heading Meaning IH A list of the 24 interrupt handlers. SIV_L The KSEG0 address of the regsave area for the interrupt handler. SIV_SP The KSEG0 address for the pointer into its interrupt stack.
System Image List Reading the CONFLIST Report The following is an example of a system image list for processor 0.
A SYSGENR Messages The following messages are generated by SYSGENR and are listed in alphabetic order. There are three types of messages: • • • Those that are sent to the home terminal. Those that are found in the SYSGENF and CONFLIST log files at the point where an error was detected. Those that appear at the end of the SYSGENF and CONFLIST files to indicate termination status. The type of message is indicated in the message description. Items Needed Before Contacting Your Service Provider Note.
SYSGENR Message Descriptions SYSGENR Messages SYSGENR Message Descriptions ALLOCATESEGMENT ERROR nnn ON VOLUME $vol. VOLUME. USE DIFFERENT SWAP Cause. The swap volume and the default volume (or just the default volume, if you did not give a swap volume) have ALLOCATESEGMENT file-system errors when attempting to allocate an extended segment.
SYSGENR Message Descriptions SYSGENR Messages BACKUP HAS ABENDED Cause. BACKUP has terminated. This message appears on the home terminal. Effect. SYSGENR continues and prompts for another tape device name. Recovery. If BACKUP has terminated because the tape device is nonexistent (filesystem error 14) or is in use (file-system error 12), then correct or redefine the specified tape device and retry the operation. Otherwise, take corrective action for the error condition, and rerun SYSGENR.
SYSGENR Message Descriptions SYSGENR Messages BAD SYSGEN OR OSIMAGE VERSION STRING ENCOUNTERED Cause. A version procedure beginning with “T9050” is missing or incorrect in either SYSGENR itself or in the system library being built by SYSGENR. This message appears in the body of the listing, at the point where the error was detected. Effect. SYSGENR finishes scanning the CONFTEXT file and then terminates. Recovery. Gather the items listed on page A-1, then call your service provider.
SYSGENR Message Descriptions SYSGENR Messages CAN'T OPEN filename: nnn Cause. Because of file-system error nnn, SYSGENR cannot open one of the following values of filename: BACKUP NLD BIND SWID DISKGEN TEMPLI XLLINK This message appears in the body of the listing, at the point where the error was detected. Effect. SYSGENR terminates. Recovery. Refer to the Guardian Procedure Errors and Messages Manual for corrective action for file-system error nnn. CAN'T OPEN BACKUP PROCESS: nnn Cause.
SYSGENR Message Descriptions SYSGENR Messages CAN'T OPEN filename FILE: nnn Cause. SYSGENR cannot open the auxiliary configuration file. This message appears on the home terminal. Effect. SYSGENR terminates. Recovery. Refer to the Guardian Procedure Errors and Messages Manual for corrective action for file-system error nnn. CAN'T OPEN "IN" FILE: nnn Cause. SYSGENR cannot open the CONFTEXT file. This message appears on the home terminal. Effect. SYSGENR terminates. Recovery.
SYSGENR Message Descriptions SYSGENR Messages CAN'T PURGE DATA IN FILE filename - FILE ERROR nnn Cause. SYSGENR cannot purge old data in the permanent work file filename, specified in a PARAM command. This message appears on the home terminal. Effect. SYSGENR terminates. Recovery. Refer to the Guardian Procedure Errors and Messages Manual for corrective action for file-system error nnn. CAN'T WRITE TO BACKUP PROCESS: nnn Cause.
SYSGENR Message Descriptions SYSGENR Messages filename CONTAINS ILLEGAL GLOBAL DATA Cause. The file filename cannot reside in the system code or system library because it contains global data. This message appears in the body of the listing, at the point where the error was detected. Effect. SYSGENR finishes scanning the CONFTEXT file and then terminates. Recovery. Remove the global data from filename. CPU nn FAILURE. PROCESSOR WAS RUNNING sysgen-process Cause.
SYSGENR Message Descriptions SYSGENR Messages DIRECTORY OVERFLOW : CPU nn Cause. Processor nn in the OSIMAGE file has overflowed the directory size limit. This message appears in the body of the listing, at the point where the error was detected. Effect. SYSGENR terminates. Recovery. Gather the items listed on page A-1, then call your service provider. DISKGEN HAS ABENDED Cause. The attempt to copy the system image to disk has failed. This message appears on the home terminal. Effect.
SYSGENR Message Descriptions SYSGENR Messages DUPLICATE "DEFINE" ENTRY - descriptor Cause. The DEFINES descriptor name descriptor has been given to more than one entry in the DEFINES paragraph. This message appears in the body of the listing, at the point where the error was detected. Effect. SYSGENR finishes scanning the CONFTEXT file and then terminates. Recovery. Assign a unique name for each descriptor. DUPLICATE PROCEDURE NAMES FOUND IN SYSTEM LIBRARY BIND LISTING: SEE BIND WARNING 22’s ABOVE Cause.
SYSGENR Message Descriptions SYSGENR Messages DUPLICATELY DEFINED PROCEDURE IN SYSTEM AREA: procedure Cause. Files listed for SYSTEM_LIBRARY_CODE_FILES specify a procedure name, procedure, that appears more than once. This message appears in the body of the listing, at the point where the error was detected. Effect. SYSGENR finishes scanning the CONFTEXT file and then terminates. Recovery. Assign each procedure a unique name.
SYSGENR Message Descriptions SYSGENR Messages FILE ERROR nnn ON filename Cause. File-system error nnn has occurred on an I/O operation to file filename. This message appears in the body of the listing, at the point where the error was detected. Effect. SYSGENR terminates. Recovery. Refer to the Guardian Procedure Errors and Messages Manual for corrective action for file-system error nnn. FILE ERROR nnn ON filename (WORK FILE SYSGENc) Cause.
SYSGENR Message Descriptions SYSGENR Messages FIRST 30 CHARACTERS OF SHELL PROC procname MATCHES ANOTHER SHELL PROC Cause. There are two native procedures whose first 30 characters are the same after the "$" in the shell procedure. This is an internal problem, as it results in two shells with the same name. Effect. SYSGENR terminates. Recovery. Gather the items listed on page A-1, then call your service provider. GATEWAY ADDRESS WRONG OR CAN'T BE FOUND FOR PROC procname Cause.
SYSGENR Message Descriptions SYSGENR Messages ILLEGAL FILE TYPE FOR INITIAL COMMAND FILE Cause. The ALLPROCESSORS paragraph entry for INITIAL_COMMAND_FILE or INITIAL_COMINT_INFILE specifies a file name of an invalid file type. The CIIN file must be type 101. Effect. SYSGENR finishes scanning the CONFTEXT file and then terminates. Recovery. Correct the entry and rerun SYSGENR. ILLEGAL FOR LIBRARY FILE TO HAVE ENTRYPOINT, FILE filename Cause.
SYSGENR Message Descriptions SYSGENR Messages ILLEGAL SYSTEM SUBVOL NAME Cause. In the ALLPROCESSORS paragraph, the volume or subvolume name for the system disk is not formatted in a valid form. This message appears in the body of the listing, at the point where the error was detected. Effect. SYSGENR finishes scanning the CONFTEXT file and then terminates. Recovery. Change the system volume and subvolume name to $volume.SYSnn, where nn is a user-specified 2-digit octal number in the range %00..
SYSGENR Message Descriptions SYSGENR Messages Recovery. Gather the items listed on page A-1, then call your service provider. INTERNAL IDTABLE OVERFLOW Cause. The SYSGENR ID table has overflowed. This is an internal problem. Effect. SYSGENR terminates. Recovery. Gather the items listed on page A-1, then call your service provider. INTERNAL SEGMENT TABLE OVERFLOW Cause. The SYSGENR segment-table space needs more than 4096 data segments.
SYSGENR Message Descriptions SYSGENR Messages INVALID FILE SIZE FOR RESIDENT TEMPLATE FILE: filename Cause. The resident template file size exceeds 64 pages. Effect. SYSGENR terminates. Recovery. Correct the file size and rerun SYSGENR. INVALID FILE TYPE FOR RESIDENT TEMPLATE FILE: filename Cause. You specified an invalid value for the resident template file type. A resident template file is file type 844 or 839. Effect. SYSGENR terminates. Recovery. Correct the file type and rerun SYSGENR.
SYSGENR Message Descriptions SYSGENR Messages Recovery. Verify that the file name being referred to is correct. If it is an object file supplied by HP, gather the items listed on page A-1, then call your service provider. INVALID PARAM BACKUPONLY SPECIFIED. PARAM WILL BE IGNORED. Cause. You have given a value for PARAM BACKUPONLY other than YES or ON. Effect. SYSGENR continues to scan the CONFTEXT file, ignoring the PARAM. Recovery.
SYSGENR Message Descriptions SYSGENR Messages INVALID PARAM REUSETEMPLATES SPECIFIED. IGNORED PARAM WILL BE Cause. You have specified an invalid value for PARAM REUSETEMPLATES. This message is displayed on the home terminal. Effect. SYSGENR continues to scan the CONFTEXT file, ignoring the PARAM. Recovery. If you meant to specify a legal PARAM REUSETEMPLATES value, stop SYSGENR and begin it again after entering a correct PARAM command. INVALID PARAM SECURENUNU SPECIFIED. PARAM WILL BE IGNORED. Cause.
SYSGENR Message Descriptions SYSGENR Messages INVALID PARAM XLLINKCPU SPECIFIED. PARAM WILL BE IGNORED Cause. You have specified an invalid value for the PARAM XLLINKCPU command. The processor numbers must be two two-digit numbers, using leading zeros, if necessary, and with no spaces between them. (For example, PARAM XLLINKCPU 0910 is correct for processors 09 and 10). The processors specified must be in the system and running. This message is displayed on the home terminal. Effect.
SYSGENR Message Descriptions SYSGENR Messages INVALID WORKFILE SPECIFIED - WORKFILE WILL BE workfiledev Cause. You have specified an incorrect work file option in the PARAM WORKFILE command. Valid options are volume name, subvolume name, or both. SYSGENR will use the device name of the default disk as workfiledev. This message appears in the body of the listing, at the point where the error occurred. Effect. SYSGENR places the work file in the default volume and subvolume. Recovery.
SYSGENR Message Descriptions SYSGENR Messages LAST ACCELERATED : dd mmm yyyy hh:mm Cause. The string dd mmm yyyy hh:mm is the date that the object file was last accelerated, where dd=day, mmm=month, yyyy=year, hh=hour, and mm=minute. Effect. SYSGENR continues. Recovery. Informational message only; no corrective action is needed. LIBRARY TABLE OVERFLOW Cause. The SYSGENR internal table space is exhausted. This message appears in the body of the listing, at the point where the error was detected.
SYSGENR Message Descriptions SYSGENR Messages Recovery. Supply the name of the microcode file and rerun SYSGENR. MISSING PROCESSOR DEFINITION - definition Cause. The CONFTEXT file does not contain required processor definition definition. This message appears in the body of the listing, at the point where the error was detected. Effect. SYSGENR finishes scanning the CONFTEXT file and then terminates. Recovery. Supply the missing definition. MISSING REQUIRED ENTRYPOINT IN FILE filename Cause.
SYSGENR Message Descriptions SYSGENR Messages MORE THAN 200 ASSIGNS Cause. Too many ASSIGN commands are entered for file-name assignments. The number of such ASSIGN commands is limited to 200. This message appears in the body of the listing, at the point where the error was detected. Effect. SYSGENR terminates. Recovery. Delete any unnecessary ASSIGN commands, and rerun SYSGENR. NAMED SYSTEM PROCESS TABLE OVERFLOW Cause.
SYSGENR Message Descriptions SYSGENR Messages ASSIGN Command SYSGENR Uses Instead SYSGEN^BINDER The version SYSGEN^DISKGEN The version SYSGEN^SWID of BINDER in $SYSTEM.SYSTEM of DISKGEN at the SYSGENR default volume and subvolume The version of SWID in $SYSTEM.SYSTEM Effect. If SYSGENR cannot start the version of the program listed in the table above, SYSGENR terminates.
SYSGENR Message Descriptions SYSGENR Messages Cause. SYSGENR has been unable to find the procedure returned by filename in system code or system library. Effect. SYSGENR finishes scanning the CONFTEXT file and then terminates. Recovery. Gather the items listed on page A-1, then call your service provider. ONE OR MORE OF ABOVE ENTRIES HAVE NAME LONGER THAN 6 CHARACTERS Cause. One or more logical device numbers have been assigned a name with more than six characters.
SYSGENR Message Descriptions SYSGENR Messages Recovery. If you want to reuse a SYSCLR file, then specify the ASSIGN for this. Otherwise, omit the PARAM REUSESYSFILES command. PARAM REUSESYSFILES USED WITH NO SYSCOD00 ASSIGN Cause. You have specified a PARAM REUSESYSFILES 1, 3, YES, or TNS command, but omitted a corequisite ASSIGN SYSCOD00 command. Effect. SYSGENR terminates. Recovery. If you want to reuse a SYSCOD00 file, then specify the ASSIGN for this. Otherwise, omit the PARAM REUSESYSFILES command.
SYSGENR Message Descriptions SYSGENR Messages PIN pinnum ALREADY USED IN CPU cpunum Cause. An internal error occurred. SYSGENR has tried to assign a PIN that has already been used. Effect. SYSGENR finishes scanning the CONFTEXT file and then terminates. Recovery. Gather the items listed on page A-1, then call your service provider. PREVIOUSLY SET PARAM OF DENSITY OR TAPEMODE IS OVERRIDDEN Cause.
SYSGENR Message Descriptions SYSGENR Messages PROCEDURE procname IN TNS/R CODE BUT NOT IN TNS CODE, FILE filename Cause. The procedure procname contains code in the accelerated code section of the object file filename but not in the TNS code section. Effect. SYSGENR finishes scanning the CONFTEXT file and then terminates. Recovery. Make sure that filename has not been corrupted or modified.
SYSGENR Message Descriptions SYSGENR Messages RECEIVE READ ERROR: nnn Cause. SYSGENR has detected file-system error nnn while reading from $RECEIVE. This message appears in the body of the listing, at the point where the error was detected. Effect. SYSGENR terminates. Recovery. Refer to the Guardian Procedure Errors and Messages Manual for corrective action for file-system error nnn. RECURSIVE DEFINE: descriptor Cause.
SYSGENR Message Descriptions SYSGENR Messages REUSESYSFILES SET ! TSC AND TSL WILL BE REUSED. Cause. You have entered a PARAM RESUSESYSFILES command to reuse system code and system library files. Effect. SYSGENR continues. Recovery. Informational message only; no corrective action is needed. REVISION OF SWID PROCESS IS NOT COMPATIBLE WITH THIS VERSION OF SYSGEN Cause. The version of the SWID DDL process being used by SYSGENR is not compatible with the version of SWID on the system.
SYSGENR Message Descriptions SYSGENR Messages SPOOLER ERROR - %nn Cause. Spooler error %nn has occurred on a write operation to the spooler. This message is printed on the home terminal and in the SYSGENR output. Effect. SYSGENR terminates. Recovery. Create an Inspect saveabend file. Gather the items listed on page A-1, then call your service provider. SWID OBJECT FILE NOT FOUND IN DEFAULT LOCATIONS. FINGERPRINTING WILL NOT BE PERFORMED. OBJECT FILE Cause.
SYSGENR Message Descriptions SYSGENR Messages SYSGENR COMPLETED -- nnn ERRORS DETECTED *** Cause. One or more errors have occurred during SYSGENR processing. This message appears at the end of the listing to report the number of errors detected. Effect. SYSGENR terminates normally, having completed successfully. If nnn exceeds 100, SYSGENR stops scanning the CONFTEXT file. Recovery. Correct the errors in the listing and rerun SYSGENR. SYSGEN COMPLETED -- NO ERRORS DETECTED *** Cause.
SYSGENR Message Descriptions SYSGENR Messages SYSTEM CODE MUST START AT SEGMENT 5 Cause. The file specified as system code has not been bound starting at segment 5. This error can occur if you create system code by using BIND outside of SYSGENR. Effect. SYSGENR terminates. Recovery. Ensure that you are using the correct version of BIND when running SYSGENR. SYSTEM DATA SPACE OVERFLOW Cause.
SYSGENR Message Descriptions SYSGENR Messages SYSTEM PROCESS NOT FOUND: process Cause. The required system process process is not among the supplied process files. This message appears in the body of the listing, at the point where the error was detected. Effect. SYSGENR finishes scanning the CONFTEXT file and then terminates. Recovery. Supply the missing file, by ordering a new SUT, if necessary. SYSTEM PROCESS USER LIBRARY CAN NOT CONTAIN MULTIPLE FILES Cause.
SYSGENR Message Descriptions SYSGENR Messages TERMINAL IS NOT ALLOWED AS "IN" FILE Cause. You have not specified a configuration file in the command to run SYSGENR, or you have specified the home terminal in place of a configuration file. However, you cannot run SYSGENR interactively. This message appears on the home terminal. Effect. SYSGENR terminates. Recovery. You must supply a configuration file in the command to run SYSGENR. THE EXTENTSIZE ASSIGNED FOR SYSGENA IS NOT LARGE ENOUGH Cause.
SYSGENR Message Descriptions SYSGENR Messages THE PROCEDURE IS CALLED FROM filename Cause. A procedure that is called from the system process library or process code file filename cannot be found. Either the procedure should not have been called, or it should have been found. Effect. SYSGENR lists all the library or code files that called the missing procedure. Then SYSGENR continues. Recovery. Gather the items listed on page A-1, then call your service provider.
SYSGENR Message Descriptions SYSGENR Messages THIS IS A REQUIRED INTERRUPT HANDLING PROCEDURE Cause. SYSGENR has not found a required interrupt handling procedure in the system library. The procedure is identified in an accompanying message, “PROCEDURE name NOT FOUND...”. This is an internal problem. Effect. SYSGENR terminates. Recovery. Gather the items listed on page A-1, then call your service provider. THIS SYSGEN MUST RUN ON A B00 OR GREATER RELEASE Cause.
SYSGENR Message Descriptions SYSGENR Messages TOO MANY ENTRY POINTS DEFINED Cause. You have configured more than 511 library procedures for the system. This message appears in the body of the listing, at the point where the error was detected. Effect. SYSGENR terminates. Recovery. Reduce the number of library procedures and rerun SYSGENR. TOO MANY ERRORS! Cause. SYSGENR has identified more than 100 errors. This message appears at the end of the listing to indicate its termination status. Effect.
SYSGENR Message Descriptions SYSGENR Messages UNEXPECTED TERMINATION BY NLD PROCESS Cause. The native linker (NLD) has terminated in a way that is not expected by SYSGENR. Effect. SYSGENR terminates. Recovery. Check the listing file for the cause of the termination, and fix it. UNEXPECTED TERMINATION BY TEMPLI PROCESS Cause. The TEMPLI process has terminated unexpectedly. TEMPLI puts out an error message in the CONFLIST listing. Effect. SYSGENR finishes scanning the CONFTEXT file and then terminates.
SYSGENR Message Descriptions SYSGENR Messages 3. Change the home terminal in the Pathway configuration file: EDIT PATHHOST C/old-hometerm/new-hometerm/A GET INITSTAT C/old-hometerm/new-hometerm/A EXIT 4. Incorporate the new values: RUN PATHCOLD 5. Restart SCM: RUN STARTSCM 6. Using the DSM/SCM Planner Interface, create a new configuration and start a build/apply. You can safely ignore the warning message about the previous build/apply, which completed with errors.
SYSGENR Message Descriptions SYSGENR Messages Recovery. Correct the value, and rerun SYSGENR. VMEM ARRAY ALLOCATION FAILED Cause. SYSGENR is unable to allocate internal buffer space. This message appears in the body of the listing, at the point where the error was detected. Effect. SYSGENR terminates. Recovery. Gather the items listed on page A-1, then call your service provider. WORKFILE filename1 NOT CREATED, filename2 USED INSTEAD Cause.
SYSGENR Messages SYSGENR Message Descriptions Recovery. Gather the items listed on page A-1, then call your service provider. YOUR ASSIGNED PROCESS FAILED -- SYSGEN WILL TRY THE VERSION ON $SYSTEM Cause. A process specified in an ASSIGN command has failed. Possible processes are BACKUP, BIND, DISKGEN, NLD (LINKER), SWID, TEMPLI, and XLLINK. Effect. SYSGENR attempts to use the process version on $SYSTEM.SYSTEM or $SYSTEM.SYSnn. Recovery.
SYSGENR Messages SYSGENR Message Descriptions System Generation Manual for G-Series RVUs —523407-001 A -44
B XLLINK Messages The following error messages are generated by XLLINK and are displayed in the CONFLIST output of SYSGENR. They are listed in numerical order. Items Needed Before Contacting Your Service Provider Note. These items apply only if you are running SYSGENR outside of DSM/SCM. You will need to gather the following items if the XLLINK message you receive directs you to contact your service provider. These items supply HP with the information needed to help resolve the problem. 1.
XLLINK Message Descriptions XLLINK Messages 2 Disk $volume is full. Cause. $volume does not have enough free space to hold the XLLINK output file. XLLINK requires about 25 megabytes of disk swap space. Effect. XLLINK terminates. Recovery. Refer to the Guardian Procedure Errors and Messages Manual for corrective action.
XLLINK Message Descriptions XLLINK Messages Recovery. If you receive this message when running DSM/SCM or SYSGENR, gather the items listed on page B-1, then call your service provider. 6 More than one TNS object file was provided. Cause. XLLINK has found more than one fully bound TNS system code or system library file (by a TNS file option). You must not run XLLINK outside of SYSGENR. Effect. The file supplied in the TNSFile option is copied as the TNS region in the executable output file. Recovery.
XLLINK Message Descriptions XLLINK Messages Recovery. Verify that all the data needs to be global and shared. If it does, cluster the read-write data into one global data block. If some of the data does not, redefine it in a private data block. 11 Component file filename is not type-100. Cause. One of the files listed in the SYSTEM_LIBRARY_CODE_FILES entry is not a type 100 file. You must not run XLLINK outside of SYSGENR. Effect. XLLINK terminates. Recovery.
XLLINK Message Descriptions XLLINK Messages 14 Attributes of procedure procname differ between the TNS object file filename1 and the component file filename2. Callable bit set in TNS object file, not in component. Cause. Attributes that are privileged, callable, resident, and so on in the object file filename1 of the procname procedure are different from those in the filename2 component file. The message tells which attribute is different. You must not run XLLINK outside of SYSGENR. Effect.
XLLINK Message Descriptions XLLINK Messages 17 Options must be separated by a comma. See obey file filename. Cause. XLLINK syntax requires a comma separator between options. If the problem was found in a command file, then the message identifies the command file filename. You must not run XLLINK outside of SYSGENR. Effect. XLLINK terminates. Recovery. If you receive this message when running DSM/SCM or SYSGENR, gather the items listed on page B-1, then call your service provider.
XLLINK Message Descriptions XLLINK Messages 21 XLLINK did not recognize text as an option. See obey file filename. Cause. XLLINK cannot recognize text as an option. If the problem is found in a command file, then the message names the file. You must not run XLLINK outside of SYSGENR. Effect. XLLINK terminates. Recovery. If you receive this message when running DSM/SCM or SYSGENR, gather the items listed on page B-1, then call your service provider. 22 XLLINK cannot link the TNS object file filename.
XLLINK Message Descriptions XLLINK Messages 25 File filename has no BIND region. Cause. The file filename contains no BIND region. You must not run XLLINK outside of SYSGENR. Effect. XLLINK terminates. Recovery. If you receive this message when running DSM/SCM or SYSGENR, make sure that you have not deleted the BIND region from file filename, and, after gathering the items listed on page B-1, call your service provider. 26 XLLINK cannot link the file filename. Cause.
XLLINK Message Descriptions XLLINK Messages Recovery. If you receive this message when running DSM/SCM or SYSGENR, gather the items listed on page B-1, then call your service provider. 30 Obey file filename is not type-101. Cause. The command file you specified in your XLLINK command is not a type 101 (EDIT) file. Effect. XLLINK terminates. Recovery. Correct the file type of the command file. 31 Option SSV0 given twice. Check options and ASSIGNs. Cause.
XLLINK Messages XLLINK Message Descriptions System Generation Manual for G-Series RVUs —523407-001 B -10
C nld Messages The following are some of the messages generated by nld, the native linker program called by SYSGENR to build the SYSCLR and SYSDP2 files. nld messages begin with the text **** ERROR **** and are listed below in alphabetic order. Items Needed Before Contacting Your Service Provider Note. These items apply only if you are running SYSGENR outside of DSM/SCM. You will need to gather the following items if the nld message you receive directs you to contact your service provider.
nld Message Descriptions nld Messages Can’t {purge|rename} existing file ‘filename‘, file error nnn. Cause. nld has created a temporary file, but cannot purge the existing file of the same name in order to rename the temporary file to that name. This can happen if filename is secured so that nld cannot purge it, or if filename is currently open. Effect. SYSGENR terminates. Recovery. Depending on file-system error nnn, resecure or close the file and rerun SYSGENR. Can’t re-open filename, file error nnn.
nld Message Descriptions nld Messages Fatal error nnn writing to filename. Cause. nld has encountered file-system error nnn when writing to filename. Effect. SYSGENR terminates. Recovery. If the error is insufficient disk space, at least 5 megabytes is needed. Use an ASSIGN SYSGEN^LINKER command to specify a volume with more free space. Then rerun SYSGENR. Filecode not 700 for: filename Cause.
nld Message Descriptions nld Messages object file: jump relocation out-of-range,filename bad object file produced, can’t jump from addr1 to addr2. Cause. nld has found inconsistent information among two or more input files. Effect. SYSGENR terminates. Recovery. Rerun SYSGENR. If the problem persists, gather the items listed on page C-1, then call your service provider. object file: filename Can’t read... Cause. nld cannot read object file filename. Effect. SYSGENR terminates. Recovery.
D Comparing SYSGENR for D-Series RVUs With SYSGENR for G-Series RVUs Many changes have been made to the role of SYSGENR in G-series RVUs. This appendix focuses on two affected SYSGENR areas: system configuration utilities and the ALLPROCESSORS paragraph. Changes to the System Configuration Utilities For D-series RVUs, SYSGENR builds the I/O processes (IOPs) specified in the CONFTEXT file into the OSIMAGE file, as it has always done. For G-series RVUs, IOPs are not built by SYSGENR.
Comparing SYSGENR for D-Series RVUs With SYSGENR for G-Series RVUs Changes to the ALLPROCESSORS Paragraph Figure D-1. Comparing D-Series and G-Series System Generation D-Series System Generation COUP Online Configuration G-Series System Generation SCF Online Configuration CONFTEXT File OSCONFIG File Minimal CONFTEXT File CONFIG File SYSGENR Offline Configuration OSIMAGE File SYSGENR Offline Configuration OSIMAGE File VST007.
Comparing SYSGENR for D-Series RVUs With SYSGENR for G-Series RVUs Changes to the ALLPROCESSORS Paragraph for G-series RVUs, along with their replacements. Many of the obsolete entries are configured automatically or can be specified using an SCF command. Table D-1. Obsolete ALLPROCESSORS Paragraph Entries (page 1 of 2) D-Series Entry Replacement on G-Series Reference BREAKPOINT_CONTROL_ BLOCKS Automatically set to 50 (the maximum for each processor).
Comparing SYSGENR for D-Series RVUs With SYSGENR for G-Series RVUs Changes to the ALLPROCESSORS Paragraph Table D-1. Obsolete ALLPROCESSORS Paragraph Entries (page 2 of 2) D-Series Entry Replacement on G-Series Reference SYSTEM_TERMINAL Entry no longer needed. The system console is not a configured object. TSM Configuration Guide TIME_LIST_CONTROL_BLOCKS Automatically set to 4400 (the maximum for each processor). -- TIME_ZONE_OFFSET Initially set to 0:00 (London).
Glossary accelerated mode. The operational environment in which Accelerator-generated RISC instructions execute. accelerated object code. The RISC instructions that result from processing a TNS object file with the Accelerator program. accelerated object file. The object file that results from processing a TNS object file with the Accelerator program.
Glossary Binder Binder. A program development tool that enables you to read, link, and modify TNS and accelerated object files. boot. A synonym for load. Load is the preferred term used in this and other NonStop S-series system manuals. See load. central processing unit (CPU). Historically, the main data processing unit of a computer. A NonStop system has multiple cooperating processors rather than a single CPU. CIIN.
Glossary TSM package information to be updated in the TSM client software. The TSM Notification Director Application passes TSM notifications to the TSM client software where they are used to update resource information. TSM package. A software product for HP NonStop S-series servers that provides the information needed to perform functions such as querying resources and testing, provides notification of problems on the system, and allows local or remote access to the system for service and maintenance.
Glossary DEFINES paragraph DEFINES paragraph. An optional paragraph in the CONFTEXT configuration file that contains one or more identifiers, each with its associated text string. The DEFINES paragraph, if used, precedes the ALLPROCESSORS paragraph. DISKGEN. A SYSGENR option that invokes the DISKGEN program to copy directly to disk those files necessary to generate a NonStop Kernel operating system. DISKGEN can be used instead of a system image tape (SIT).
Glossary Guardian Guardian. An environment available for interactive or programmatic use with the NonStop Kernel operating system. Processes that run in the Guardian environment use the Guardian system procedure calls as their application program interface; interactive users of the Guardian environment use the TACL or another HP product’s command interpreter. identifier.
Glossary operating system image Distributed Systems Management/Software Configuration Manager (DSM/SCM) (which in turn runs SYSGENR) to generate a system image for the new configuration. operating system image. See OSIMAGE. OSCONFIG file. In G-series RVUs, a configuration file built by SYSGENR that contains only Software Problem Isolation and Fix Facility (SPIFF) and Software Identification (SWID) tool records. In D-series and earlier RVUs, the Configuration Utility Program (COUP) uses the $SYSTEM.SYSnn.
Glossary RELOAD peripherals, and restructuring a database. Reconfiguring a system might or might not require a planned outage. RELOAD. A TACL command to load the NonStop Kernel operating system image from disk over the ServerNet fabrics into the memory of the processor. RESTORE. A utility for the NonStop range of servers that copies files from a backup tape to disk. See also BACKUP. service provider. (1) A person trained and qualified to service field-replaceable units (FRUs).
Glossary system code system code. A logically distinct part of the NonStop Kernel operating system that consists of operating-system procedures shared by all processors. system console. An TSM workstation configured as the primary or backup dial-out point. The TSM workstation configured as the primary dial-out point is called the primary system console. The TSM workstation configured as the backup dial-out point is called the backup system console. system generation.
Glossary tape bootstrap tape bootstrap. The program on a system image tape (SIT) that reads the rest of the SIT during tape load and writes it to the system disk. tape load. A system load. A tape load is the process of reading a system image tape (SIT) and writing it to the system disk. In the event of a disaster, the normal procedure for loading a system is to restore the SIT from tape to a SYSnn subvolume and load the system from that subvolume.
Glossary TSM Low-Level Link Application TSM Low-Level Link Application. See TSM Low-Level Link Application. TSM notification. See TSM notification. TSM Service Application. See TSM Service Application. user code. A logically distinct part of the NonStop Kernel operating system that consists of the code for user processes. user library. A logically distinct part of the NonStop Kernel operating system that consists of procedures that the operating system can link to a program file at run time. volume.
Index A Accelerator program 1-6 ALLPROCESSORS paragraph 2-1, 2-2/2-14 COLDLOAD_DISK_LOWPIN entry 2-4 contents 2-2 example 2-3 FILES_TO_COPY_TO_NEW_ SYSTEM entry 2-5 FORMATTER_TEMPLATE_FILES entry 2-6 INITIAL_COMMAND_FILE or INITIAL_COMINT_INFILE entry 2-6 STANDARD_MICROCODE entry 2-10 SUPER_SUPER_IS_UNDENIABLE entry 2-11 syntax 2-3 SYSTEM_LIBRARY_CODE_FILES entry 2-11 SYSTEM_PROCESSOR_TYPE entry 2-13 SYSTEM_PROCESS_CODE_FILES entry 2-12 SYSTEM_PROCESS_LIBRARY_ FILES entry 2-13 SYSTEM_VOLUME_SUBVOL entry 2-1
Index D COLDLOAD_DISK_LOWPIN ALLPROCESSORS paragraph entry 2-4 Command file containing SYSGENR commands 3-24 Command interpreter IN file 2-6/2-10 Comparing SYSGENR for D-series and Gseries RVUs D-1/D-3 CONFAUX file as input for SYSGENR 1-5 entries, in ALLPROCESSORS 2-2 if not using 2-5, 2-6, 2-11, 2-12, 2-13 list of entries 1-5 listing in CONFLIST report 5-3 relation to CONFTEXT file 1-5 relation to DEFINES paragraph 2-1 TANDEM^FILES^TO^COPY entry 2-5 TANDEM^FORMATTER^ TEMPLATE^FILES entry 2-6 TANDEM^LIBR
Index F Error messages See Messages Expand 1-8, 4-8 EXPAND node number, displayed by SYSINFO command 2-14 EXTENTSIZE, PARAM command 3-10 F File security information 1-8 Files going to native mode linker, listing in CONFLIST report 5-4, 5-6 FILES_TO_COPY_TO_NEW_SYSTEM ALLPROCESSORS paragraph entry 2-5/2-6 files keep old security 1-8 FORMATTER_TEMPLATE_FILES, ALLPROCESSORS paragraph entry 2-6 G GCR, tape recording density 3-10 I INITIAL_COMMAND_FILE or INITIAL_COMINT_INFILE, ALLPROCESSORS paragraph entry
Index O O Object files as input to SYSGENR 1-5 created by NLD native 5-4, 5-6 TNS 5-5 Offline configuration with SYSGENR 1-1 Online configuration with SCF 1-2 Operating system contents, after running SYSGENR 4-12 Operating system image See OSIMAGE file OSIMAGE file keeping accessible 1-9 SYSGENA work file 3-6 PARAM commands (continued) UNLOAD 3-18 overridden by PARAM SYSGEN^BACKUPPARAM 3-15 WORKFILE 3-19 XLLINKCPU 3-20 Peruse to monitor SYSGENR progress 4-2 PE, tape recording density 3-10 Preprocessing c
Index S SECURENUNU, PARAM command 3-14 Segment address in system process map 5-13 in system spaces map 5-8 SID creating 4-3/4-8 specifying number you want 3-21/3-23 SIT as output from SYSGENR 1-7 creating 4-9/4-11 specifying number you want 3-21/3-23 Site update tape (SUT) See SUT SIV listing in CONFLIST report 5-19 Software configuration, performing 1-2/1-3 changing your configuration 1-3 installing a new RVU 1-2 installing an IPM 1-2 STANDARD_MICROCODE, ALLPROCESSORS paragraph entry 2-10 Stopping and re
Index T System disk configured on a low PIN 2-4 System image disk (SID) See SID System image list, in CONFLIST report 5-19 System image tape (SIT) See SIT System interrupt vector (SIV), listing in CONFLIST report 5-19 System library See System code and system library System management considerations 1-7/1-9 System process load map, in CONFLIST report 5-13 System spaces maps, in CONFLIST report 5-9 SYSTEM_LIBRARY_CODE_FILES, ALLPROCESSORS paragraph entry 2-11/2-12 SYSTEM_PROCESSOR_TYPE, ALLPROCESSORS parag
Index X WORKFILE, PARAM command 3-19 X XLLINK log, in CONFLIST report 5-5 messages B-1/B-9 used by SYSGENR 1-4 XLLINKCPU, PARAM command 3-20 Z ZSYSDISC.SYSDISC file, disk bootstrap file 4-12 Special Characters # (pound sign) in DEFINES paragraph 2-2 $DSMSCM.SYS.CONFTEXT file See CONFTEXT file $SYSTEM See system disk $SYSTEM.
Index Special Characters System Generation Manual for G-Series RVUs —523407-001 Index-8
