![[Digital logo]](../../IMAGES/DIGITAL-LOGO.GIF){kind=logo}
![[HR]](../../IMAGES/REDBAR.GIF)
For more information, see Section 1.2.1.
If you have a shared system dump file in SYS$COMMON:[SYSEXE], the shared dump file cannot have the name SYSDUMP.DMP. If you have a shared system dump file with this name, Digital recommends that you rename it to SYS$COMMON:[SYSEXE]SYSDUMP_COMMON.DMP.
The upgrade procedure is designed so that you should not have to reinstall most layered products after the upgrade. However, you might need to reinstall certain layered products because of product-specific installation procedures.
If a layered product is available yet exhibits unexpected behavior once Version 7.1 of the OpenVMS VAX operating system is running, check the OpenVMS Version 7.1 Release Notes for possible layered-product restrictions.
Before you begin to upgrade the OpenVMS VAX operating system, be sure you have all the required hardware and software components.
Examine your hardware for the following:
Examine your software for the following:
After the upgrade is finished, AUTOGEN runs. If it finds valid feedback data on your system, it tries to use AUTOGEN feedback.
If your feedback data is not valid, AUTOGEN will run without feedback (all previous feedback-generated parameters will be replaced by the AUTOGEN NOFEEDBACK calculations).
To ensure that AUTOGEN feedback will run after the upgrade, do the following:
$ @SYS$UPDATE:AUTOGEN GETDATA TESTFILES
$ @SYS$UPDATE:AUTOGEN SAVPARAMS TESTFILES
Digital recommends that you make a standalone backup copy of the system disk and, if your configuration allows it, upgrade the backup copy. If there are problems, you will still have a working system disk.
To make a backup copy of the system disk, follow the instructions in the upgrade and installation supplement for your VAX computer. If you do not have a removable system disk, back up your system disk to tape and restore the image backup to the system disk. This eliminates disk fragmentation on the system disk and creates contiguous free disk blocks required for the upgrade. (The upgrade can fail if there are not sufficient contiguous free blocks.) Store the backup tapes in a safe place.
If you have one of the following VAX computers, you also must make a backup copy of the console media:
To make a backup copy of the console media, use the SYS$UPDATE:CONSCOPY.COM procedure, as described in the upgrade and installation supplement for your VAX computer. Use the backup copy of the console media during the upgrade procedure. The upgrade procedure updates the console media for you.
If your VAX computer uses one of the following console media, you did not receive a new standalone BACKUP kit with your OpenVMS VAX distribution kit:
Before beginning the upgrade, make sure you have a standalone BACKUP kit on one of these media. If you do not have one, create a standalone BACKUP kit using the STABACKIT.COM procedure as described in the upgrade and installation supplement for your VAX computer.
Note
You cannot build standalone BACKUP on TU58 or RX01 console media because the OpenVMS VAX Version 7.1 kit is too large. If your VAX computer uses a TU58 or RX01, build a standalone BACKUP kit before upgrading and retain the backup copies for use with future versions of OpenVMS VAX.
To prepare the system disk for the upgrade, log in to the SYSTEM account and, depending on your configuration, complete some or all of the tasks described in the sections that follow.
If you are using a volume-shadowed system disk, you must create a nonshadowed system disk to upgrade. Follow the instructions in the Volume Shadowing for OpenVMS manual to prepare a nonshadowed system disk for the upgrade.
If you need to boot the backup copy of your system disk or if you are upgrading a VAXcluster environment, enter the following command (otherwise, go to the next step):
$ @SYS$SYSTEM:SHUTDOWN
When the procedure asks if an automatic system reboot should be performed, press Return for NO. If you are a VAXcluster member, choose the CLUSTER_SHUTDOWN option. When the procedure is finished, halt the system as described in the upgrade and installation supplement for your VAX computer.
If applicable, remove the system disk and replace it with the backup copy.
Boot the system from the backup copy of the system disk. If you do not know how to boot the system, refer to the upgrade and installation supplement for your VAX computer.
The current copies of the SYSUAF.DAT and the VMS$AUDIT_SERVER.DAT files must be on the system disk; otherwise, you cannot proceed with the upgrade.
If you have moved your copy of SYSUAF.DAT to another location, copy it to the SYS$COMMON:[SYSEXE] directory for the duration of the upgrade.
If you have moved your copy of VMS$AUDIT_SERVER.DAT to another location, copy it to the SYS$COMMON:[SYSMGR] directory.
Note that, if you are doing a rolling upgrade, the shared version of SYSUAF.DAT is not updated.
Move any files that you do not want changed into a user directory.
If you have a shared system dump file in SYS$COMMON:[SYSEXE], the shared dump file cannot have the name SYSDUMP.DMP. If you have a shared system dump file with this name, Digital recommends that you rename it to SYS$COMMON:[SYSEXE]SYSDUMP-COMMON.DMP.
To analyze the system disk for inconsistencies and errors in the file structure, enter the following command:
$ ANALYZE/DISK_STRUCTURE SYS$SYSDEVICE
The following message represents normal behavior; you can ignore it:
%ANALDISK-I-OPENQUOTA, error opening QUOTA.SYS
If you find any other errors on the system disk, repair the errors by entering the following command:
$ ANALYZE/DISK_STRUCTURE/REPAIR SYS$SYSDEVICE
Refer to the OpenVMS System Management Utilities Reference Manual for more information on the ANALYZE/DISK_STRUCTURE command.
Digital recommends that the page file be located on the system disk in SYS$SPECIFIC:[SYSEXE] for the upgrade.
The swapfile (SWAPFILE.SYS) does not need to be located on the system disk for the upgrade, but if it is located on the system disk, the file must be located in SYS$SPECIFIC:[SYSEXE].
If the upgrade procedure finds the page files and swap files in the common directory, it will move them to the system-specific directory before continuing.
The page file must be at least 4600 blocks. If the upgrade procedure detects fewer than 4600 blocks, it displays a message that gives you the option of continuing the upgrade or exiting the procedure and increasing the size of the page file. If you get this message, Digital recommends that you exit the procedure, increase the page file to at least 4600 blocks, and restart the upgrade procedure.
To check the size of your page file and enter a new size if needed, use the following procedure:
$ @SYS$UPDATE:SWAPFILES
Enter new size for paging file:
Check the system disk to make sure there is enough room for the upgrade. To determine whether you have enough room, enter the following command:
$ SHOW DEVICE SYS$SYSDEVICE
To upgrade the OpenVMS VAX required files, the minimum number of free blocks required is 48,950. Even if you plan to upgrade the OpenVMS library or optional files, you might not need more than 48,950 free blocks because many files are deleted as the upgrade progresses, thus freeing up additional space.
Use the Authorize utility (AUTHORIZE) to make sure the SYSTEM account has sufficient quotas and limits. To check and, if necessary, modify quota and limit values, do the following:
$ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE UAF> SHOW SYSTEM
| Quota or Limit Name | Minimum Value |
|---|---|
| Open file quota (FILLM) | 300 |
| Buffered I/O limit (BIOLM) | 18 |
| Direct I/O limit (DIOLM) | 18 |
| AST limit (ASTLM) | 24 |
| Enqueue quota (ENQLM) | 200 |
| Buffered byte quota count (BYTLM) | 32768+ |
MODIFY SYSTEM/limit=new_valueFor example:
UAF> MODIFY SYSTEM/DIOLM=18
UAF> EXIT
During the upgrade procedure, the system is shut down and rebooted a number of times. You must boot the system minimum (STARTUP_P1 set to MIN) before you begin the upgrade (see Section 5.7). This prevents startup of certain system integrated products and layered products on the system during each reboot. To set the system parameter STARTUP_P1 to MIN, enter the following commands:
$ RUN SYS$SYSTEM:SYSMAN SYSMAN> PARAMETERS USE CURRENT SYSMAN> PARAMETERS SET STARTUP_P1 "MIN" SYSMAN> PARAMETERS WRITE CURRENT SYSMAN> EXITMake sure the system parameters SCSNODE and SCSSYSTEMID are defined on your system. To determine whether these parameters are defined on your system, enter the following commands:
$ RUN SYS$SYSTEM:SYSMAN SYSMAN> PARAMETERS SHOW SCSNODE SYSMAN> PARAMETERS SHOW SCSSYSTEMID
If SCSNODE and SCSSYSTEMID are not set correctly, enter the following commands where node is a 1- to 6-character unique DECnet node name and systemid is (DECnet area * 1024) + node number:
SYSMAN> PARAMETERS USE CURRENT SYSMAN> PARAMETERS SET SCSNODE "node" SYSMAN> PARAMETERS SET SCSSYSTEMID systemid SYSMAN> PARAMETERS WRITE CURRENT . . .Make sure the system parameter VMS5 is set to 0. If your system has a KFQSA controller, the VMS5 parameter might have been set to a nonzero value for a previous upgrade. The VMS5 parameter is reserved for Digital's use only.
To check the value of the VMS5 parameter, enter the following commands:
$ RUN SYS$SYSTEM:SYSMAN SYSMAN> PARAMETERS USE CURRENT SYSMAN> PARAMETERS SHOW VMS5 Parameter Name Current Default Minimum Maximum Unit Dynamic -------------- ------- ------- ------- ------- ---- ------- VMS5 1 0 0 -1
If the current value of VMS5 is not 0, set it to 0 by entering the following commands:
SYSMAN> PARAMETERS USE CURRENT SYSMAN> PARAMETERS SET VMS5 0 SYSMAN> PARAMETERS WRITE CURRENT SYSMAN> EXIT
If you used the Snapshot facility to boot your current system with a system snapshot image, you must change the BOOT_STYLE system parameter to 0 before you can perform an upgrade. To change the BOOT_STYLE system parameter to 0, enter the following commands:
$ RUN SYS$SYSTEM:SYSMAN SYSMAN> PARAMETERS USE CURRENT SYSMAN> PARAMETERS SET BOOT_STYLE 0 SYSMAN> PARAMETERS WRITE CURRENT SYSMAN> EXIT $
You can reexecute the Snapshot command procedure (SYS$MANAGER:SNAPSHOT.COM) after the upgrade is completed, as described in the OpenVMS System Manager's Manual: Essentials.
During an upgrade, user disks are not mounted and SYLOGICALS.COM is not invoked, so AUTOGEN can access only data files that are on the system disk and whose file specification includes a logical name that is shipped as part of the OpenVMS operating system. Therefore, if you use AGEN$INCLUDE in SYS$SYSTEM:MODPARAMS.DAT to point to data files that are not on the system disk, follow these steps before you perform an upgrade:
If you do not move referenced data files to the system disk, AUTOGEN uses whatever information is available during the upgrade and parameters might be set to values considerably different from what you intend.
Any system parameter values that you modified and did not enter in MODPARAMS.DAT are lost during the upgrade. To retain the values of these parameters, enter their names in MODPARAMS.DAT and the value that AUTOGEN needs to add to the default minimum value.
For example, if you modified GBLPAGES by 128 pages above the default, add the following line to SYS$SYSTEM:MODPARAMS.DAT:
ADD_GBLPAGES=128
When AUTOGEN runs after the upgrade, it uses the values in MODPARAMS.DAT.
Section 5.7 tells you how to get your system ready for an upgrade.
To prepare the system for the upgrade, use the procedure described in the following rdsections.
If your computer uses console media, set the computer to restart automatically. For some VAX computers this means setting one or more switches. For others, this means entering certain console mode commands. To determine how to enable auto restart, refer to the upgrade and installation supplement for your VAX computer.
If you have a system that does not use console media, set your system so you can reboot it manually. For more information, refer to the upgrade and installation supplement for your VAX computer.
Shut down and reboot the system to activate any system parameters that you changed (STARTUP_P1, for example). To shut down the system, enter the following command:
$ @SYS$SYSTEM:SHUTDOWN
When the procedure asks if an automatic system reboot should be performed, type Y (for YES) and press the Return key.
After the system reboots, log in to the SYSTEM account.
To prevent users from logging in to the system during the upgrade, enter the following command:
$ SET LOGINS/INTERACTIVE=0
To determine whether your system is running DECnet for OpenVMS software, enter the following command:
$ SHOW LOGICAL SYS$NODE
If the system displays the following message, DECnet is not running on your system and you can proceed to Section 5.7.6:
%SHOW-S-NOTRAN, no translation for logical name SYS$NODE
If the system responds with a translation for SYS$NODE, then DECnet is running on your system.
If you set STARTUP_P1 to MIN as described in Section 5.6.9, DECnet should not be running. To set STARTUP_P1 to MIN, repeat all of the preceding steps beginning with Section 5.6.9. Note that you must shut down and reboot the system for any changes you make to system parameters to take effect.
Phase I (controller-based) shadowing is no longer available. Phase II (host-based) shadowing is designed to fully replace phase I shadowing with significantly enhanced features.
If you have volume shadowing installed on your system but are unsure which phase, you can enter the following commands:
$ RUN SYS$SYSTEM:SYSMAN SYSMAN> PARAMETERS USE CURRENT SYSMAN> PARAMETERS SHOW SHADOWINGIf the SHADOWING parameter is 1 or 3, then you have phase I shadowing currently loaded on your system. For information about migrating to phase II, see Volume Shadowing for OpenVMS.
At the beginning of an upgrade, the procedure checks the setting of the SHADOWING system parameter. If you have not migrated to phase II and the procedure detects the presence of phase I shadowing, it displays the following message and asks if you want to continue the upgrade:
The SHADOWING system parameter (currently set to 1) specifies phase I of volume shadowing, which is no longer available as of OpenVMS VAX Version 6.1. If you continue with this upgrade, volume shadowing will not be present on your system after the upgrade has completed. Please consult the Volume Shadowing for OpenVMS manual for instructions about moving to phase II of volume shadowing. * Do you want to continue the upgrade?
At that point, you can exit the upgrade procedure, follow the instructions in Volume Shadowing for OpenVMS for migrating to phase II shadowing, and restart the upgrade procedure from the beginning. If you continue with the upgrade without migrating to phase II, volume shadowing will not be present on your system after the upgrade has completed.
To stop all batch and print queues on the node you are upgrading, enter the following command:
$ STOP/QUEUES/ON_NODEIt is not necessary to stop queues on nodes that you are not upgrading.
At different points during the upgrade, the procedure prompts you to supply information. To save time once the procedure begins, be sure you have the following information readily available. Remember, entering incorrect information during the upgrade could force you to repeat the entire upgrade procedure.
| Required Information | Explanation |
|---|---|
| Device names | You will need to specify the device names for the drives that will hold the distribution media and the system disk. |
| Passwords | You will be prompted to type passwords of at least 8 characters for the SYSTEM, SYSTEST, and FIELD accounts. |
| Optional components and OpenVMS Management Station files |
The upgrade procedure prompts you to specify whether you want to
install the library (VMS071.C), optional (VMS071.D) OpenVMS components,
and OpenVMS Management Station software PC files (VMS071.F).
Appendix D lists the files included in these save sets.
You can save some space on your system disk if you choose not to install these components, but be sure to review Appendix D before deciding. |
| Location for Help Message utility | Save set VMS071.E contains the online Help Message utility, which you can install on your system disk or on an alternate disk. (However, if you copied the distribution kit to some other media from which you will be performing the installation, you cannot install this save set on that media.) |
| DECwindows components |
The installation procedure prompts you to specify which of the
following DECwindows components you want to install:
Note that you must install the DECwindows Motif for OpenVMS (previously called VMS DECwindows Motif) layered product if you want to run the DECwindows software. DECwindows Motif for OpenVMS Version 1.2--3 (or 1.2 if the VAXMOTF05_012 remedial kit is installed) is the minimum supported version for systems running OpenVMS VAX Version 7.1. If you do not know which version of DECwindows Motif you are currently running on your system, you can check by entering the following command: $ ANALYZE/IMAGE SYS$LIBRARY:DECW$XLIBSHR.EXE
Also note that the layered product does not have the DECwindows base and workstation support components. To get full DECwindows support, you must select the DECwindows components provided with the OpenVMS VAX Version 7.1 kit and install the separate DECwindows Motif for OpenVMS VAX layered product, which supports both Motif and XUI environments. |
| PAK information | The information listed on Product Authorization Keys (PAKs) for any new products you will register. You do not need to register your OpenVMS VAX license or the licenses for any System Integrated Products (SIPs) you are already running. |
Before you begin the upgrade procedure, use the following checklist to make sure you have completed all the necessary preupgrade tasks.
6487P005.HTM OSSG Documentation 9-DEC-1996 10:53:55.28
Copyright © Digital Equipment Corporation 1996. All Rights Reserved.