900 Series HP 3000 Computer Systems AutoRestart/iX User's Guide ABCDE HP Part No. 36375-90001 Printed in U.S.A.
The information contained in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability or tness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for direct, indirect, special, incidental, or consequential damages in connection with the furnishing or use of this material.
Printing History The following table lists the printings of this document, together with the respective release dates for each edition. The software version indicates the version of the software product at the time that this document was issued. Many product releases do not require changes to the document; therefore, do not expect a one-to-one correspondence between product releases and document editions.
iv
Preface The AutoRestart/iX User's Guide (36375-90001) provides the information necessary to con gure and manage AutoRestart/iX, a product that enables a 900 Series HP 3000 to automatically reset itself in the event of a system abort, to save dump failure state information to disk, and to restart itself, all without the need for operator intervention. This user's guide is written for the system administrator who has completed Hewlett-Packard system administrator training courses.
Conventions UPPERCASE In a syntax statement, commands and keywords are shown in uppercase characters. The characters must be entered in the order shown; however, you can enter the characters in either uppercase or lowercase.
Conventions (Continued) [ ... ] In a syntax statement, horizontal ellipses enclosed in brackets indicate that you can repeatedly select the element(s) that appear within the immediately preceding pair of brackets or braces. In the example below, you can select parameter zero or more times. Each instance of parameter must be preceded by a comma: [,parameter][...
Contents 1. Introduction What Is AutoRestart/iX? . Product Features . . . . . Dump-to-disk feature . . Restart feature . . . . . Autoboot feature . . . . Mini-dump feature . . . Overview of AutoRestart/iX Con guration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation and . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 1-2 1-2 1-2 1-2 1-3 . . . 1-3 2. Preparing Your System Determining Your Dump-to-Disk Needs . . . . . .
Build the mini-dump le . . . . . . . . . . . Initialize the mini-dump contents. . . . . . . . Specify mini-dump criteria . . . . . . . . . . . List mini-dump information . . . . . . . . . . Create the autoboot le to invoke SAT . . . . . Managing the Dump-to-Disk and Mini-Dump Features Specify the alternate dump device strategy . . . TAPE command syntax . . . . . . . . . . . TAPE command parameters . . . . . . . . . TAPE command example . . . . . . . . . . Building a dump le . . . . . . . . . . . . .
Using the BLDDUMP help facility HELP command syntax . . . . HELP command parameters . . HELP command example . . . Exiting the BLDDUMP utility . . EXIT command syntax . . . . EXIT command example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4. Con guring and Managing the Autoboot Feature Overview of Autoboot Con guration . . . . . . . Creating the Autoboot Format File . . . . . . . . Adding the Autoboot File to Your System's Con guration . .
Tables 2-1. Dump File Size Estimates . . . . . . . . . . . 3-1. Summary of BLDDUMP Commands . . . . . .
1 Introduction AutoRestart/iX is intended for users of 900 Series HP 3000 computer systems who are concerned with the following: maintaining a high level of system availability eliminating the need for operator intervention after system software failures This user's guide provides the information necessary to con gure and manage AutoRestart/iX on your 900 Series HP 3000 computer system.
Product Features Dump-to-disk feature AutoRestart/iX supports the following features: dump-to-disk restart autoboot mini-dump The dump-to-disk feature enables MPE/iX to write system dump information directly to a preallocated disk le. This feature is an addition to the dump-to-tape feature available on all MPE/iX-based systems. Use the BLDDUMP utility to con gure and manage the dump-to-disk feature. Using BLDDUMP, you can create, manage, and purge dump les.
Mini-dump feature In an environment with many systems with similar con gurations and operating system versions, duplicate problems can occur. This feature is used to bypass a full memory dump for system failures. When a system failure occurs, the mini-dump feature enables MPE/iX to write the system failure information to a disk le, which can be analyzed at a later time. Speci cally, a mini-dump is an ASCII le containing output from the SAT utility summarizing the system failure.
2 Preparing Your System This chapter describes how to prepare your system for successful con guration of AutoRestart/iX. System preparation for AutoRestart/iX consists of the following steps: 1. Determine your dump-to-disk needs. 2. Determine your mini-dump needs. 3. Add one or more disk drives to your system's con guration. 4. Physically install the disk drives. 5. Create the AutoRestart/iX account structure.
Estimate size of largest dump file Calculating the actual size of a system dump is di cult. The following variable factors contribute to the size of a dump: number of active jobs and sessions number of child processes associated with the jobs and sessions memory size To ensure that the size of the dump le that you create covers all possible cases, you must estimate the largest dump possible on your system.
Use DTODSIZ utility to estimate largest dump size If you have already installed AutoRestart/iX on your system, you can use the DTODSIZ utility to estimate dump size, based on system activity occurring when DTODSIZ is executed. The DTODSIZ utility can be run either interactively or from a job. At the system prompt, enter: :RUN DTODSIZ.HP36375.TELESUP When DTODSIZ runs, it estimates the size of a dump that would occur at that time, and recommends the megabyte size required to hold that dump.
Determine the number of dump files required Determine the number of disk drives required Note Determining Your Mini-Dump Needs Note 2-4 Preparing Your System Determine the number of dump les that you want to preallocate. Base your decision on the cost of additional disk drives versus the risk of losing important dump information. You can lose information if a dump occurs before you can examine existing dump information and there are no additional dump les to store subsequent dump information.
Adding an AutoRestart/iX Disk Drive to Your This section describes the steps necessary to logically con gure disk drives on your system. Note that a disk drive is not completely con gured until your con guration is saved to a new system load tape (SLT) and your system is rebooted. System's Configuration Note This section assumes that you are installing disk drives on your system for use by AutoRestart/iX.
5. Decide on the path of the added disk drive. View the LPATH command output. If you are adding the drive to a newly installed HP-IB card, you must rst use the APATH command to de ne the path down to the device adapter level. For example, assume that you plan to add the drive to a newly installed HP-IB card (ID number, HP27113A) and the card was placed in the CIO expander (CA 36) on channel adapter 2, and device adapter slot 2. At the IO prompt, enter: io>APATH 36.2 HP27113A 6. Add the device.
9. Mount a write-enabled tape on the tape drive. Put the tape online. Use the TAPE command at the SYSGEN prompt to generate a customized system load tape (SLT) that includes the new con guration. At the SYSGEN prompt, enter: sysgen>TAPE Reply to the tape request. The system indicates when the tape is completed: **Boot tape is successfully built** This is your system's new SLT. Label the tape, and store it in a secure location. 10.
Installing the AutoRestart/iX Disk Drive Physically install the disk drive using directions located in the disk drive installation manual. The physical connection must match the logical connection that you con gured in the previous section. The disk drive, once logically con gured and physically installed, is ready for use. You must now con gure the volume for use by AutoRestart/iX.
2. Enter the DSTAT command to determine which volumes can be initialized. Precede this command with a colon (DSTAT is a system command, not a VOLUTIL command). At the VOLUTIL prompt, enter: volutil: :DSTAT The DSTAT command displays information about nonsystem volume sets. The following example shows three nonsystem volumes sets, each in a di erent state (UNKNOWN, SCRATCH, and LONER).
5. Enter the DSTAT command to verify that the volume set was created. At the VOLUTIL prompt, enter: volutil: :DSTAT DSTAT displays the updated volume information. In the d c Note Adding member volumes to a master volume set following example, the volume on LDEV 11 has been con gured as the master volume, named MEMBER1 volume set DISKDUMP_VOLUME_SET .
3. Use the NEWVOL command to add a member volume to a master nonsystem volume set. For example, to add the SCRATCH volume as a member volume to the master nonsystem volume set DISKDUMP_VOLUME_SET, at the VOLUTIL prompt, enter: volutil: NEWVOL DISKDUMP_VOLUME_SET:MEMBER2 LDEV13 The system asks you to verify that the information that you entered is correct. When you respond 4Y5 followed by 4Enter5, the system displays process information. 4.
Creating the HP36375 and DISKDUMP groups AutoRestart/iX requires two groups, HP36375 and DISKDUMP, located in the TELESUP account. Two NEWGROUP commands are required (if you are creating a nonsystem volume set) to con gure each of the new groups in both the system volume set and the nonsystem volume set. The following enables you to create both groups on your system: 1. Log on as MANAGER.SYS. At the system prompt, enter: :HELLO MANAGER[/userpass].SYS[/acctpass] 2.
4. Ensure that the group HP36375.TELESUP resides on your system. At the system prompt, enter: :LISTGROUP HP36375.TELESUP If HP36375.TELESUP does not reside on your system, go to step 5. If HP36375.TELESUP resides on your system, it was created on your system master volume set (MPE XL_SYSTEM_VOLUME_SET) when you installed AutoRestart/iX, during an update or an installation. To move HP36375.TELESUP to the nonsystem volume set (for example, DISKDUMP_VOLUME_SET), perform the following steps: a.
8. If you had to purge HP36375.TELESUP prior to recreating it on the nonsystem volume set, you must restore the AutoRestart/iX les to HP36375.TELESUP, now located on the nonsystem volume set. a. Mount a write-enabled tape on the tape drive. Put the tape drive online. b. Restore AutoRestart/iX les to HP36375.TELESUP. At the system prompt, enter: :FILE T;DEV=TAPE :RESTORE *T;@.@.@;SHOW c. Reply to the tape request. 9.
Configuring and Managing the Dump-to-Disk and 3 Mini-Dump Features This chapter describes how to con gure and manage the dump-to-disk and mini-dump features on your system. The rst part of this chapter details the steps that you need to perform to successfully con gure the dump-to-disk feature on your system. If you are performing an initial con guration of the dump-to-disk feature, start by reading \Overview of Dump-to-Disk Con guration.
Overview of Dump-to-Disk Configuration Following is a summary of the steps necessary to con gure the dump-to-disk feature: De ne your alternate dump device strategy. De ne your dump le protection scheme. Con gure the dump-to-disk feature. Many of the steps described in this chapter require you to log on to the console, to an account with system manager capability. For convenience, this manual recommends that you perform all steps from the console.
Defining Your Alternate Dump Device Strategy Before you con gure the dump-to-disk feature, you must de ne what the system should do if complete dump information is not stored to a dump le on disk. If either of the following are true, then complete dump information is not stored to disk: No dump les are available because existing dump les contain dump information and are protected from overwrites. The size of the dump is larger than the size of the available dump le.
Dump-to-tape You can have the dump facility initiate a dump-to-tape if it cannot write complete dump information to a dump le; however, operator intervention is required to mount tapes and put the tape drive online. In this case, valuable dump information is guaranteed at the expense of an operator-less environment. If a dump-to-tape was initiated because the size of the dump is larger than the size of the dump le, you must use the ALTSIZE command to change the dump le size.
Defining Your Protection Scheme Protected dump files Use the BLDDUMP BUILD command to de ne the protection scheme for a dump le when you create it. The PROTECT command enables you to change the protection scheme of an existing dump le. You can either protect a dump le from overwrites by subsequent dumps-to-disk or leave it unprotected. The BLDDUMP utility enables you to protect valuable dump information from accidental overwrites by subsequent dumps.
Configuring the Dump-to-Disk Feature Note This section describes the steps necessary to initially con gure the dump-to-disk feature, using the BLDDUMP utility. You should have already de ned your protection scheme and alternate dump device strategy. Before proceeding with this section, read each of the steps and become familiar with the BLDDUMP commands BUILD and TAPE. Both commands are described in detail later in this chapter.
4. Use the TAPE command to specify your alternate dump device strategy. At the BLDDUMP prompt, enter: (#2) blddump > TAPE dump strategy where: dump strategy If Y[es] is speci ed, the dump facility initiates dump-to-tape if dump-to-disk is unsuccessful. If N[o] is speci ed, the dump facility terminates immediately if dump-to-disk is unsuccessful. If neither is speci ed, TAPE defaults to YES. 5.
Configuring the Mini-Dump Feature Overview of mini-dump configuration This section describes the steps necessary to con gure the mini-dump, using the BLDDUMP utility. The following is a summary of the steps required to con gure the mini-dump feature: Initialize and de ne the contents of the mini-dump. Initialize and de ne the criteria for a full dump to be taken. Create the autoboot format le specifying that the SAT utility must be invoked.
Initialize the mini-dump contents. To initialize the mini-dump contents, you must initialize a le that contains the SAT commands for creating the mini-dump. A template (MDINPUT.HP36375.TELESUP) contains the minimum set of SAT commands that must be used. This le also de nes the contents of the mini-dump; a date and time stamp, the MPE/iX version identi cation, the system failure number, and a stack trace. To initialize the data structures required by SAT, use the BLDDUMP command INITMD.
2. If a mini-dump does not contain enough information to analyze all system failures, then each subsequent line should contain a system failure number pre xed with SA (system abort) or SD (sudden death). On the same line, you must specify the SAT macro that is to take the full dump when the system fails with this number. The macro that takes the full dump is included in the template MDINPUT.HP36375.TELESUP and is called FULLDUMP.
List mini-dump information d Use the LISTMD command to display the name and size of the mini-dump le that you created and to display the les that were initialized with the INITMD command. At the BLDDUMP prompt, enter: (#2) blddump> LISTMD Mini-Dump Version A.00.00 Autoboot Status Restart Enabled Mini-Dump Enabled ON YES YES a MINI-DUMP FILE: MINIDUMP.MPEXL.SYS MAXIMUM RECORDS: 500 INPUT FILE: MDINPUT.MYGROUP.
Use the AutoRestart/iX BLDDUMP utility to manage dump les. The BLDDUMP utility provides a set of easy-to-use commands that allow you to perform the tasks required to manage the dump-to-disk and mini-dump features. Following is a summary of BLDDUMP commands and their functions: Managing the Dump-to-Disk and Mini-Dump Features Table 3-1. Summary of BLDDUMP Commands Command Name Function ALTSIZE Alters the size of a speci ed dump le.
The BLDDUMP prompt provides a number in parentheses that indicates the number of BLDDUMP commands invoked during the current session of BLDDUMP (helpful for use with the DO and REDO commands). For example, (#4) blddump > indicates that three previous BLDDUMP commands have been invoked in the current session of BLDDUMP.
Building a dump file Use the BUILD command to build a dump le. You can build up to 10 dump les. The BUILD command enables you to specify the following about the dump le: the dump le ID the maximum number of megabytes that can be written to the le the protection scheme BUILD command syntax 2 BUILD leid, le size ,protection Note 3 Building dump les on the MPEXL_SYSTEM_VOLUME_SET can cause problems.
BUILD command example To build a protected dump le named DUMP1 with a size of 417 megabytes and its contents protected from overwrites, enter the following at the BLDDUMP prompt: (#2> blddump > BUILD DUMP1 417 Y Building new Dumpfile. This can take a while... Note The process of building a large dump le takes time. Large dump les can take 15 minutes or more to create. If you invoke BUILD, you must invoke both VSCLOSE and VSOPEN against the nonsystem volume set when you exit BLDDUMP.
Building a mini-dump file Use the BUILDMD command to build a mini-dump le. One mini-dump le only is allowed. In order to protect it from being overwritten by a subsequent mini-dump, you must copy it to another le prior to invoking the INITMD command. The BUILDMD command enables you to specify the maximum number of records that can be written to the le. BUILDMD command syntax BUILDMD lesize BUILDMD command parameters lesize Required. The size, in 80-byte records, of the mini-dump le.
Initializing a mini-dump file The INITMD command initializes two les; the mdinput le that de nes the contents of the mini-dump, and the mdinfo le that contains the criteria action to be taken for speci ed system failures. INITMD command syntax INITMD mdinput mdinfo INITMD command parameters Note If no parameters are speci ed, all les currently initialized become uninitialized, and the mini-dump feature is disabled. mdinput mdinfo Optional.
For example, to create an mdinfo le that will perform a mini-dump for all system failures except a system abort number 1451 and a sudden death number 311, you would create the following unnumbered temporary (TEMP) le: DEFAULT SA1451 SD311 EOF NULLDUMP FULLDUMP FULLDUMP When you have completed the contents of your temporary le (TEMP), keep the contents as an unnumbered le, build a permanent mdinfo le, and copy the contents of the TEMP le to it.
Purging a dump file Note Use the PURGE command to purge a dump le from the nonsystem volume set. Dump les are specially protected les and can be purged only through the BLDDUMP utility. The PURGE command available through the command interpreter does not remove a dump le from your system. Do not purge a dump le until you have determined that you no longer need its contents and that you no longer need the space allocated. PURGE command syntax PURGE leid PURGE command parameters leid Required.
Purging a mini-dump file Note Use the PURGEMD command to purge a mini-dump le. Mini-dump les are specially protected les and can be purged only through the BLDDUMP utility. When you use the PURGEMD command to purge your mini-dump le, it invalidates the system data structures that contain information regarding the mini-dump; therefore, if you use the BUILDMD command to build another mini-dump le, the INITMD command must be invoked to reinitialize the les that contain the SAT commands and dump criteria.
Reseting a dump file Note Use the RESET command to delete or reset the contents of a dump le without altering the le's size or protection scheme. Invoking RESET on a dump le empties it. After you reset a dump le, a subsequent dump-to-disk can write to the empty dump le. You should reset a dump le after you analyze the dump information.
Altering the size of a dump file Note Use the ALTSIZE command to alter the size of a dump le. Use this command when the dump le is too large (wasting disk space) or too small (causing unsuccessful dumps to disk). ALTSIZE purges the dump le, then creates a new dump le of the same name and protection scheme. Any contents in the dump le are lost. Do not alter the size of a dump le until you have determined that you no longer need its contents.
ALTSIZE command example To alter the maximum con gurable size of a dump le DUMP1 to 417 megabytes, enter the following at the BLDDUMP prompt: (#5 blddump > ALTSIZE DUMP1 417 If you invoke ALTSIZE, you must invoke both VSCLOSE and VSOPEN against the nonsystem volume set when you exit BLDDUMP. This ensures posting of directory information. You must enter VSCLOSE and VSOPEN at the console.
Changing a dump file's protection scheme Use PROTECT to alter the protection scheme of a dump le. You can either protect a dump le from overwrites by subsequent dumps to disk, or leave it unprotected. PROTECT command syntax 2 PROTECT leid ,protection scheme 3 PROTECT command parameters leid protection scheme Required. The leid parameter is the name of an existing dump le with a protection scheme that you want to alter. Do not specify the characters MEM, appended by BLDDUMP. Optional.
Listing dump-to-disk information Use the LIST command to review the following information: Current status of all dump les, including le size, size of contents, and protection scheme. Alternate dump device strategy. Determine if the dump facility initiates dump-to-tape if it cannot write complete dump information to a disk dump le. Current status of the autoboot feature. Determine if the autoboot feature is enabled or disabled.
Listing mini-dump information Use the LISTMD command to review the following information: current mini-dump version current status of the autoboot, restart, and mini-dump features current mini-dump record size, input le and when it was initialized, and the criteria le and when it was initialized LISTMD command syntax LISTMD LISTMD command example d To list the current status of the mini-dump feature, enter the following at the BLDDUMP prompt: a (#1) blddump > LISTMD Mini-Dump Version A.00.
Displaying the autoboot status Use the AUTOBOOT command to display the current status of autoboot and toggle the autoboot ag. AUTOBOOT command syntax AUTOBOOT 8 < ON : 9 = OFF ; STATUS AUTOBOOT command parameters ON OFF STATUS Optional. The ON option enables the autoboot feature. Optional. The OFF option disables the autoboot feature. Optional. The STATUS option displays the current status of the autoboot feature. For example, a message similar to the following is displayed: Autoboot is enabled.
Using the BLDDUMP help facility Use the HELP command to review detailed information about BLDDUMP commands. If you enter HELP alone, you see a syntax description of all BLDDUMP commands. If you enter HELP with a command name, you see detailed information about that command. HELP command syntax 2 HELP cmd name 32 options 3 HELP command parameters cmd name options Optional. The name of a BLDDUMP command.
Exiting the BLDDUMP utility Use the EXIT command to exit the BLDDUMP utility. If you invoke BUILD, PURGE, or ALTSIZE, you must invoke both VSCLOSE and VSOPEN against a nonsystem volume set when you exit BLDDUMP. This ensures posting of directory information. You must enter VSCLOSE and VSOPEN at the console specifying the nonsystem volume set name.
4 Configuring and Managing the Autoboot Feature This chapter describes how to con gure and manage the autoboot feature on your system. The rst part of this chapter details the steps that you must perform to successfully con gure the autoboot feature on your system. If you are performing an initial con guration of autoboot, start by reading \Overview of Autoboot Con guration." The remaining sections in this chapter deal with managing the autoboot feature after initial con guration.
Overview of Autoboot Configuration The following steps are necessary to con gure the autoboot feature: 1. Create the autoboot format le. 2. Add the autoboot feature to your system's con guration. 3. Halt system activity. 4. Perform a con guration update and test for successful con guration of AutoRestart/iX. 5. Return your system to a normal operating state. The nal step in autoboot con guration is a test for successful con guration of all three AutoRestart/iX features: dump-to-disk, restart, and autoboot.
Creating the Autoboot Format File This section describes how you create the autoboot format le. The autoboot format le is a specially formatted le and is required to add a system autoboot le. To create the autoboot format le, follow these steps: 1. Log on to the console as MGR.TELESUP,HP36375 . At the system prompt, enter: :HELLO MGR[/userpass].TELESUP[/acctpass],HP36375 2. Create a text le named AUTOIN, containing the sequence of ISL commands that you want the system to perform at system boot.
3. Use the AutoRestart/iX FORMAT utility to convert the contents of AUTOIN.HP36375.TELESUP to a le named AUTOOUT with the required format. The FORMAT utility looks for a le named AUTOIN in your current logon group. Format then creates the format le AUTOOUT in the same group. At the system prompt, enter: :RUN FORMAT.HP36375.TELESUP d c The following is displayed: Autoutil 1.0: A.43.11 AUTOIN converted to autoboot format file AUTOOUT END OF PROGRAM : 4. Purge the le AUTOIN.HP36375.TELESUP.
Adding the Autoboot File to Your System's Configuration Note This section describes the steps necessary to do the following: Add an autoboot le to a system without one. Replace an existing autoboot le with the AutoRestart/iX autoboot le. Perform a con guration update to your system. This manual assumes that you are making con guration changes to the default con guration group of the 900 Series HP 3000 system that you are currently logged on to.
5. If you do not have an autoboot le installed on your system, use the AAUTO command to add the AutoRestart/iX autoboot format le AUTOOUT.HP36375.TELESUP to your system's con guration. The FILE= parameter speci es the autoboot format le. The TYPE=DISK parameter indicates that the autoboot le contents will be invoked only during a boot from disk. At the SYSFILE prompt, enter: sysfile> AAUTO FILE=AUTOOUT.HP36375.TELESUP TYPE=DISC Go to step 7. 6.
10. Use the KEEP command to store to disk the changes that you have made to your system's con guration. At the SYSGEN prompt, enter: sysgen> KEEP d c The SYSGEN utility saves to the default con guration group the con guration changes made in the SYSFILE con gurator. Respond Y when SYSGEN asks if it should overwrite that group: keeping to group CONFIG.SYS Purge old configuration (yes/no)? Y ** configuration files successfully saved ** b 11. Mount a write-enabled tape on the tape drive.
Halting System Activity Note This section describes the steps necessary to perform an orderly shutdown of your system prior to a con guration update. This section describes procedures associated with shutting down your system. Read through this section before you attempt a shutdown based on these instructions. Go over the areas that you want to customize for your system.
6. To verify that the printer is available and to shut down spool queues, follow these steps: a. Verify that the printer is active. At the system prompt, enter: :SHOWDEV nn (nn is your printer's LDEV number.) b. Use the SHUTQ command to shut down the spool queues. This prevents users from sending reports to the printer. At the system prompt, enter: :SHUTQ nn (nn=printer's LDEV number) or :SHUTQ devname (devname=device name of spooled device) 7.
11. To shut down the system, enter: 4CTRL5 4A5 =SHUTDOWN d c The console responds by listing shutdown messages similar to these: Shutdown Shutdown Shutdown Spoolers Shutdown Shutdown Shutdown of operating system begins. (Shut 1) of user processes begins. (Shut 2) of jobs & sessions begins. (Shut 3) notified of a shutdown. (Shut 16) of system processes begins. (Shut 4) of system managers begins. (Shut 5) of operating system complete. (Shut 6) All system activity is now halted. 12.
Performing a Configuration Update Note This section describes how to perform a con guration update, so that you can complete con guration of your autoboot feature and test for successful con guration of AutoRestart/iX. This section describes procedures associated with rebooting your system and performing a con guration update. Read this section before you follow the instructions, and review the areas that you want to customize for your system.
6. Respond Y to the Interact with IPL (Y or N)?> prompt. d The following example represents a boot sequence received at the console for a Series 950/980 with autoboot enabled, ending with the system displaying the ISL prompt. Sequences for other installations can vary. a 4CTRL5 4B5 CM> TC Processor-Dependent Code (PDC) revision 2.8 Console path = 2/4.1.0.0.0.0.0 Primary boot path = 2/4.0.0.0.0.0.0 Alternate boot path = 6/4.3.0.0.0.0.0 48 MB of memory configured and tested.
8. To con rm that FASTSIZE is set to 0000000F, follow these steps: a. Display the current FASTSIZE value. At the ISL prompt, enter: ISL> DISPLAY Fastsize value is 0000000F . . . b. If FASTSIZE is any value other than 0000000F, you must change the value of FASTSIZE to 0000000F. At the ISL prompt, enter: ISL>FASTSIZE F c. If you changed the value of FASTSIZE, you must reset the system for the new value to take e ect. Repeat the steps described in \Performing a Con guration Update," beginning with step 2. 9.
14. When startup is complete, perform a soft reset of your system, to test successful installation and con guration of AutoRestart/iX. At the console, enter: 4CTRL54B5 CM> TC After resetting itself, the system executes the ISL commands in the system autoboot le. The rst ISL command invoked is usually DUMP. If the dump-to-disk feature has been correctly con gured, the DUMP facility locates the rst dump le and proceeds to dump-to-disk.
Returning the System to Normal Operation Returning to a normal operating state When you complete the update process and successful testing of AutoRestart/iX, you must do the following: Return the system to its normal operating state. Remove system dependency on the autoboot format le. Return dump-to-disk to its pre-test state, if you tested for successful con guration of AutoRestart/iX. This section describes many of the steps required to return your system to its normal operating state.
Removing dependency on the autoboot format file Note This section describes how to replace AUTOOUT.HP36375.TELESUP with the system autoboot le AUTOBOOT.MPEXL.SYS. Whenever you create a system load tape (SLT) in SYSGEN on a system that has an autoboot le, SYSGEN searches for the speci ed autoboot le before creating the SLT. If SYSGEN does not locate the autoboot le, it does not create the SLT.
8. Use the KEEP command to store to disk the changes that you have made to your system's con guration. At the SYSGEN prompt, enter: sysgen> KEEP d c The SYSGEN utility saves to the default con guration group the con guration changes made in the SYSFILE con gurator. Respond Y when SYSGEN asks if it should overwrite that group. keeping to group CONFIG.SYS Purge old configuration (yes/no)? Y ** configuration files successfully saved ** b 9. Exit SYSGEN. At the SYSGEN prompt, enter: sysgen> EXIT 10.
3. Use the LIST command to determine the current state of dump les. At the BLDDUMP prompt, enter: (#1) blddump > LIST The BLDDUMP utility displays the current state of all dump les.
5. Use the LIST command to con rm that DUMP1 has been reset. At the BLDDUMP prompt, enter: (#1) blddump > LIST BLDDUMP displays the following: d Autoboot Status Dump-to-tape if dump-to-disk is not successful? DUMP FILE NAME (ID + "MEM") c -------------DUMP1MEM DUMP FILE MAXIMUM SIZE (megabytes) -----------400 CURRENT SIZE OF CONTENTS (megabytes) ------------0 a ON YES PROTECTED? ---------YES b The current size of DUMP1 is 0 megabytes, indicating a successful reset.
Managing the Autoboot Feature Using the autoboot toggle This section deals with managing the autoboot feature after initial con guration. The tasks described are as follows: using the autoboot toggle temporarily disabling autoboot modifying the autoboot le removing the autoboot feature The autoboot toggle allows you to access the current status of autoboot and turn it on or o .
Toggling the autoboot flag To toggle the autoboot ag, perform the following steps: 1. Log on to the console as MANAGER.SYS. 2. Execute the BLDDUMP utility. At the system prompt, enter: :RUN BLDDUMP.HP36375.TELESUP 3. Use the AUTOBOOT xx command to determine the current status of autoboot. At the BLDDUMP prompt, enter: (#1) blddump > AUTOBOOT xx Where: xx is either on or o . The ON option enables autoboot, and the OFF option disables autoboot.
Temporarily disabling autoboot There are two ways to temporarily disable the autoboot feature; however, both require operator intervention during the startup sequence. These are as follows: Override the autoboot sequence at the console. Get into ISL and disable the autoboot ag. Both options require an operator's presence during system startup. If the autoboot feature is con gured on your system, it is invoked each time your system is reset.
You are now at the ISL prompt. From here you can invoke ISL commands, including START -R. Note Remember to use the -R option with START if you want the system to restart after the next system abort. If you do not use the -R option, the system does not reboot after the next system abort. Disabling the autoboot flag You can temporarily disable autoboot by getting into ISL and disabling the autoboot ag. To disable the autoboot ag, follow these steps: 1. Log on to the console as MANAGER.SYS. 2.
Modifying your autoboot sequence To modify the sequence of ISL commands in the system autoboot le, replace the contents of the system autoboot le with the modi ed contents of AUTOOUT.HP36375.TELESUP. This process is similar to the one used to add an autoboot le. You must perform an update to allow the system to write the new autoboot contents to the system autoboot le. Follow these steps: 1. Log on to the console as MGR.TELESUP,HP36375. 2. Purge the le AUTOOUT.HP36375.TELESUP.
11. Use the RAUTO command to replace the existing autoboot le with the AutoRestart/iX autoboot format le AUTOOUT.HP36375.TELESUP. The FILE= parameter speci es the autoboot format le. The TYPE=DISK parameter indicates that the autoboot le contents are invoked only during a reboot from disk. At the SYSFILE prompt, enter: sysfile> RAUTO FILE=AUTOOUT.HP36375.TELESUP TYPE=DISK 12. Use the SHOW AUTO command to con rm that SYSGEN has temporarily accepted AUTOOUT.HP36375.TELESUP.
18. Exit SYSGEN after building the SLT. At the SYSGEN prompt, enter: sysgen> EXIT When you exit SYSGEN without keeping the modi cations to disk, the system autoboot le AUTOBOOT.MPEXL.SYS remains in SYSGEN (not AUTOOUT.HP36375.TELESUP). Deleting the autoboot feature To permanently delete the autoboot feature from your system, you must delete the autoboot le from your system con guration, create a new SLT, then reinstall your system using the ISL INSTALL command.
5 Managing Your AutoRestart/iX System This chapter describes various tasks used to manage your system after initial AutoRestart/iX installation and con guration.
Checking for the Occurrence of a Dump Note Because AutoRestart/iX guarantees automatic startup and dump-to-disk after a system software failure, you might not notice that a dump has occurred on your system. It is important that you establish procedures requiring regular checks for dump information in your dump les. You should check your system daily for evidence of a system abort and dump. One way that you can check your system is to execute BLDDUMP and use the LIST command to list dump le information.
Handling an Occurrence of a Dump Note Protecting Critical Data If a dump has occurred on your system, follow your site's de ned procedures for handling dumps. These procedures could include contacting an Hewlett-Packard response center. It is important that dumps are handled immediately so that you can free the lled dump le for subsequent dumps.
Resetting an AutoRestart/iX System Whenever you perform either a soft reset (4Ctrl54B5 TC) or a hard reset (4Ctrl54B5 RS) on a system with the autoboot feature con gured, your system invokes the commands located in the autoboot le. In this case (and any case where a system abort did not occur), you do not want to invoke the DUMP command located in your autoboot le.
Remember to reenable the autoboot ag immediately after completion of the update or installation and before you enter START -R. To reenable autoboot, enter the following at the ISL prompt: ISL> AUTOBOOT ON If you did not disable the autoboot ag prior to installation or update, then, upon an update or install completion, you should override the autoboot sequence by pressing any key within 10 seconds after you see this display on the console: Autoboot from primary boot path enabled.
Reviewing the Mini-Dump File The mini-dump le is an ASCII format le that can be viewed with the PRINT command, an editor, or any way you are able to view an ASCII le. Following is an example mini-dump le: FRI, JUL 3, 1992 3:49 PM RELEASE A.41.00 MPEXL HP31900 A.51.07 USER VERSION: A.41.00 SYSTEM ABORT #1789 FROM SUBSYSTEM #107 PC=a.00196ec0 system_abort NM* 0) SP=402c5e58 RP=a.003e50ac unlock_range_from_cache+$94 NM 1) SP=402c5e58 RP=a.003e8a68 unlock_from_vpn_cache+$c4 NM 2) SP=402c5de8 RP=a.
Index A AAUTO command, 4-6 abort checking for, 5-2 handling, 5-3 access current status, autoboot, 4-20 ACCESS option, 3-28 accounts TELESUP, 2-12 account structure, 2-11 activating network services, 4-15 activating NS3000/XL, 4-15 adding autoboot le, 4-6 disk drives, 2-5 drive paths, 2-6 nonsystem volume sets, 2-8 ALL option, 3-28 alternate dump device strategy, 3-2, 3-13, 3-25 alternate path booting, 4-12 ALTSIZE command, 3-12, 3-21, 3-22, 3-23, 3-28, 3-29, 5-1 analysis, problem local, 1-1 remote, 1-1 ana
autoboot feature, 1-2 adding autoboot le, 4-5 AUTOOUT le, 4-4 con guration, 1-3 con guring, 4-1 deleting, 4-26 disabling, 4-22 disabling autoboot ag, 4-12 disabling ag, 4-23 enabling autoboot ag, 4-13 format le, 4-3 FORMAT utility, 4-4 initial con guration, 4-1 management, 1-3 managing, 4-1, 4-20 modifying autoboot le, 4-24 overriding, 4-11, 4-22 remove dependency on format le, 4-16 removing, 4-26 testing con guration, 4-14 autoboot le adding, 4-6 adding to system con guration, 4-5 con rming existence of, 4
FORMAT utility, 1-2, 4-4 installation, 1-3 managing, 5-1 nonsystem volume set, 2-8 overview, 1-1 preparing your system, 1-3 resetting a system, 5-4 restart feature, 1-2 system requirements, 2-1 AutoRestart/iX disk drives con guring, 2-8 installing, 2-8 B backup AutoRestart/iX, 5-3 dump le, 5-3 scheduling, 4-8 tapes, 4-8 BLDDUMP commands, 3-12, 3-28 ALTSIZE, 3-12, 3-28 AUTOBOOT, 3-12 BUILD, 3-12, 3-28 BUILDMD, 3-12 DO, 3-12 EXIT, 3-12, 3-28 HELP, 3-12, 3-28 INITMD, 3-12 LIST, 3-12, 3-28 LISTMD, 3-12 LISTRED
C Index-4 changes to con guration, holding, 2-6 changing dump le size, 3-22 protection schemes, 3-24 changing FASTSIZE, 4-13 changing the autoboot le, 4-24 checking dump size, 5-1 dump-to-disk, 3-5 checking FASTSIZE, 4-13 checking for dump occurrence, 5-2 checking for dumps, 5-1 checking for system abort, 5-2 commands AAUTO, 4-6 ALTSIZE, 3-12, 3-21, 3-22, 3-23, 3-29, 5-1 AUTOBOOT, 3-12, 3-27, 4-23 BLDDUMP, 3-12, 3-28 BUILD, 3-5, 3-6, 3-7, 3-12, 3-14, 3-15, 3-21, 3-29 BUILDMD, 3-12, 3-16 DO, 3-12 DSTAT, 2-
SHOWDEV, 4-9 SHUTQ, 4-9 START, 1-2, 4-13 STORE, 5-3 TAPE, 3-3, 3-6, 3-12, 3-13, 4-7 TELL, 4-8 VOLUTIL, 2-10 VOLUTIL NEWSET, 2-8, 2-9 VSCLOSE, 3-7, 3-15, 3-19, 3-23, 3-29 VSOPEN, 2-11, 3-7, 3-19, 3-23, 3-29 WARN, 4-9 CONFIG.
D Index-6 data overwriting, 5-3 protecting, 5-3 default con guration group, 4-7 deleting the autoboot feature, 4-26 dependency on autoboot format le, 4-16 DESC option, 3-28 directory information, posting, 3-15 disable autoboot, 4-21 disabling autoboot, 4-11, 4-22 during install, 5-4 during update, 5-4 disabling AutoRestart/iX, 5-4 disabling the autoboot feature, 4-22 disabling the autoboot ag, 4-23 disk drives adding, 2-5 adding to system con guration, 2-5 capacity, 2-4 con guring, 2-1, 2-5, 2-8 installin
disk space, 5-3 leid, 3-6, 3-14, 3-19, 3-21, 3-22, 3-24 le size, 3-6, 3-14 listing information about, 3-25 managing, 3-1 number, 3-14 number required, 2-4 overwriting, 3-5 preallocation, 2-1 protected, 3-5, 3-6, 3-14, 3-24, 3-25 purging, 3-19 resetting, 3-21, 5-4 size, 3-4, 3-14, 3-22, 3-25 size estimates, 2-2, 2-3 status, 3-25 unprotected, 3-5, 3-24 zero contents, 3-4 dump le size estimating, 5-1 dump information risk of losing, 2-4 dump size calculating, 2-2, 2-3 checking, 5-1 estimating, 2-3, 5-1 using D
E F G H Index-8 enable autoboot, 4-21 enabling the autoboot ag, 4-13 estimating dump le size, 2-2, 5-1 using DTODSIZ, 2-3 using number of active jobs/sessions, 2-2 using the DTODSIZ utility, 2-2 EXAMPLE option, 3-28 EXIT command, 2-6, 3-6, 3-12, 3-28, 3-29 FASTSIZE checking, 4-13 modifying, 4-13 feature mini-dump, 1-3 features autoboot, 1-2 dump-to-disk, 1-2 restart, 1-2 le dump, 3-6 leid dump le name, 3-6, 3-14, 3-19, 3-21, 3-22, 3-24 les autoboot, 3-4 dump, 3-1, 3-4, 3-5 dump-to-disk, 2-10 le size du
I J K L ID, dump le, 3-6, 3-14, 3-19, 3-21, 3-22, 3-24 identify repeat problems, 1-3 information losing, 3-5 posting, 3-15 initial con guration autoboot feature, 4-1 returning dump-to-disk to, 4-17 initialize mini-dump, 3-17 initialize SAT macro, 3-9 initializing, volume sets, 2-10, 2-11 INITMD command, 3-12, 3-17 install, 5-5 after deleting autoboot le, 4-26 disabling AutoRestart/iX, 5-4 installing disk drives, 2-5, 2-8 DISKDUMP.
M N Index-10 managing AutoRestart/iX, 5-1 dump le, 3-1 dump-to-disk, 3-1, 3-12 mini-dump, 3-17 the autoboot feature, 4-1, 4-20 member volumes, 2-10 memory dump bypass, 1-3 mini-dump initialize, 3-17 initially con guring, 3-8 listing information, 3-26 managing, 3-17 mini-dump feature, 1-3 mini-dump le con guring, 3-8 listing information about, 3-26 number, 3-16 purging, 3-20 size, 3-16, 3-26 status, 3-26 mini-dump output SAT, 3-2 modifying autoboot le, 4-24 modifying FASTSIZE, 4-13 monitoring dump-to-disk
O P OCLOSE command, 2-5 o , autoboot, 4-20 on, autoboot, 4-20 ONVS option, 2-13 opening spooler queues, 4-15 OPENQ command, 4-15 operatorless environment, 3-4 options ACCESS, 3-28 ALL, 3-28 DESC, 3-28 EXAMPLE, 3-28 HOMEVS, 2-13, 2-14 ONVS, 2-13 PARMS, 3-28 USE, 3-28 orderly shutdown, 4-8 overriding autoboot, 4-22 AutoRestart/iX, 5-4 dump, 5-4 overriding autoboot, 4-11 overview, autoboot con guration, 4-2 overwriting data, 5-3 dump le, 3-5 information, 3-5 protection from, 3-6, 3-14, 3-24 PARMS option, 3-2
changing, 3-24 PURGE command, 3-12, 3-19, 3-28, 3-29 PURGEGROUP command, 2-13 PURGEMD command, 3-12, 3-20 purging dump le, 3-19 mini-dump le, 3-20 R S Index-12 RAUTO command, 4-6, 4-16 REDO command, 3-12 removing dependency on autoboot format le, 4-16 removing the autoboot feature, 4-26 repeat problems identify, 1-3 replacing autoboot le, 4-6, 4-16 RESET command, 3-5, 3-12, 3-21, 3-28, 5-4 resetting dump le, 5-4 resetting a system, 5-4 resetting, dump le, 3-21 restart feature, 1-2 option, 4-13, 4-23 your
dumps, 5-1 mini-dump le, 3-16 SLT, 4-11 spooler queues opening, 4-15 shutting down, 4-9 START command, 1-2 restart option, 4-13 starting the system -R option, 1-2 startup state con gurator, 4-15 status autoboot, 3-25, 3-26, 3-27, 4-20, 4-21 STORE command, 5-3 store to tape, 3-5 SYSFILE con gurator, 4-5 SYSGEN, 4-5 AAUTO command, 4-6 creating an SLT, 4-7 exiting, 4-7 HOLD command, 4-6 KEEP command, 4-7 RAUTO command, 4-6, 4-16 saving changes to disk, 4-7 SHOW command, 4-5, 4-6 SYSFILE con gurator, 4-5 TAPE c
T U V W Z Index-14 TAPE command, 3-3, 3-6, 3-12, 3-13, 3-28, 4-7 tape drive, online during a system abort, 5-3 TELESUP account, 2-12, 4-3 TELL command, 4-8 telling users about a shutdown, 4-8 terminating dumps, 3-3, 3-13 test autoboot con guration, 4-14 toggle autoboot, 4-20 autoboot ag, 4-21 UNKNOWN volume state, 2-9 unprotected dump le, 3-5 update, 4-13, 5-5 con guration, 4-11 disabling AutoRestart/iX, 5-4 USE option, 3-28 using the system console, 4-2 utilities BLDDUMP, 1-2, 3-3, 3-5, 3-6, 3-8, 3-1
