|
HP OpenVMS Systems Documentation |
|
OpenVMS VAX Version 7.3
|
| Previous | Contents | Index |
The procedure displays the following message:
The OpenVMS Management Station is a client-server application that provides OpenVMS system management capabilities through a client application on a personal computer (PC) running Microsoft Windows. The server application runs on OpenVMS systems and is automatically installed as part of the OpenVMS operating system. This option provides the files used to install the PC client software. If you want to use the OpenVMS Management Station, you must install these optional files on at least one OpenVMS system and then use one or both of them to install the PC client on one or more PCs. There are two files: TNT030_I.EXE for Intel systems (Windows 95 and Windows NT), and TNT030_A.EXE for Alpha Windows NT systems. The OpenVMS Management Station optional files consume approximately 20000 blocks and will be placed on your system disk in SYS$COMMON:[TNT.CLIENT]. * Do you want to install the optional OpenVMS Management Station files? (Y/N) Space remaining on system disk: 1573110 blocks |
If you want to use the OpenVMS Management Station software, you must
install these files. After the upgrade procedure completes, follow the
instructions in Appendix G to prepare your OpenVMS system and your
PC to run the OpenVMS Management Station server and client software.
7.3.7 Choosing DECwindows Support Options
Next, the procedure displays messages about the DECwindows components shipped with OpenVMS VAX Version 7.3.
The OpenVMS VAX operating system no longer ships the OpenVMS DECwindows product. The operating system now ships only the DECwindows base support and DECwindows workstation support components. To get full DECwindows support, you must also install the separate DECwindows Motif for OpenVMS VAX (previously called VMS DECwindows Motif) layered product, which supports both Motif and XUI environments.
Note that the DECwindows base support and DECwindows workstation support components are not shipped with the DECwindows Motif for OpenVMS VAX layered product. If you want to install these options, you must select them now or use the DECW$TAILOR option after the installation procedure completes.
Before you indicate whether you want to install DECwindows support software, consider the following:
| If you... | Then choose... |
|---|---|
| Intend to install the DECwindows Motif for OpenVMS VAX layered product | DECwindows base support |
| Intend to install the DECwindows Motif for OpenVMS VAX layered product on a workstation or on an OpenVMS Cluster system that contains workstations |
DECwindows base support and
DECwindows workstation support |
| Are not planning to install the DECwindows Motif for OpenVMS VAX layered product but are installing OpenVMS VAX on a workstation or on an OpenVMS Cluster system that includes workstations |
DECwindows base support and
DECwindows workstation support |
| Want to provide font files for X terminals |
DECwindows base support and
DECwindows workstation support |
| Have a workstation monitor (for example, a VR150, VR160, or VR295) capable of displaying 100 dots/inch or a VAXstation 4000 series computer, which uses 100 dots/inch video fonts by default |
DECwindows base support and
DECwindows workstation support with the 100 dots/inch option. By selecting the workstation support files, you automatically get 75 dots/inch video font files, and you will be prompted to indicate if you want to install 100 dots/inch video font files |
The procedure displays the following:
You can select DECwindows now, or you can use the DECW$TAILOR utility
to provide or remove DECwindows support after the upgrade.
Some media, TK50s in particular, can be very slow when tailoring on files.
You might want to select DECwindows now and tailor off unwanted files later.
NOTE: This kit does NOT contain full DECwindows.
To obtain full DECwindows, you must also install the separate
layered product, DECwindows Motif for OpenVMS VAX.
Version 1.2-4 is the minimum version of DECwindows Motif for OpenVMS VAX
that can be used with OpenVMS VAX V7.3.
The DECwindows components provided in this kit require approximately
34400 blocks, broken down as follows:
o DECwindows base support - 4400 blocks
o DECwindows workstation support - 23800 blocks
- 75 dots per inch video fonts (included)
- 100 dots per inch video fonts (optional) - 6200 blocks
You must select the DECwindows base support option if
- you plan to run DECwindows software, or
- you are installing this kit on
* a workstation or
* an OpenVMS Cluster that contains workstations, or
- you want to provide font files for Xterminals.
If you are installing this kit on a system that includes Xterminals
and you do NOT select DECwindows base support, then you will have to use
the DECW$TAILOR utility to provide font files.
* Do you want the DECwindows base support? (Y/N) y
Space remaining: 1568710 blocks
You must select the DECwindows workstation support option if
- you are installing this kit on
* a workstation or
* an OpenVMS Cluster that contains workstations, or
- you want to provide font files for Xterminals.
If you are installing this kit on a system that includes Xterminals
and you do NOT select DECwindows workstation support, then you will have
to use the DECW$TAILOR utility to provide font files.
* Do you want to provide DECwindows workstation support? (Y/N) y
Space remaining: 1544910 blocks
DECwindows workstation support includes the 75 dots per inch video fonts.
All DECwindows applications run with 75 dots per inch video fonts.
By default, most systems start up with 75 dots per inch video fonts.
Certain applications can take advantage of 100 dots per inch video fonts.
For the VAXstation 4000 series machine, 100 dots per inch video fonts
are used by default. If you decide not to install 100 dots per inch
video fonts, you must edit SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM
to force 75 dots per inch video fonts to be the default. Otherwise,
certain applications may not space text properly.
For instructions on how to configure your system with both 75 and 100
dots per inch video fonts, see the installation guide or look at the
template command procedure SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.TEMPLATE.
*Do you want 100 dots per inch video fonts installed? (Y/N) y
Space remaining: 1538710 blocks
|
Next, the procedure displays messages describing the DECnet options. For more information, refer to Section 1.1.2.
Beginning with OpenVMS V7.1, the DECnet-Plus kit is provided with
the OpenVMS operating system kit. Compaq strongly recommends that
DECnet users install DECnet-Plus. DECnet Phase IV applications are
supported by DECnet-Plus.
DECnet Phase IV is also provided as an option. Support for DECnet
Phase IV is available through a Prior Version Support Contract.
If you install DECnet-Plus and TCP/IP you can run DECnet
applications over a TCP/IP network. Please see the OpenVMS
Management Guide for information on running DECnet over TCP/IP.
If you plan to install DECnet Phase IV, do NOT select DECnet-Plus.
* Do you want to install DECnet-Plus. (Y/N) y
|
If you are upgrading from OpenVMS VAX Version 7.2 and are changing DECnet products, the procedure prompts you to remove the version of DECnet installed on your system. You must remove this DECnet product because both Compaq DECnet-Plus for OpenVMS VAX and DECnet Phase IV for OpenVMS VAX products cannot run concurrently on your system.
The following message shows an upgrade from DECnet Phase IV for OpenVMS VAX to Compaq DECnet-Plus for OpenVMS VAX:
* Do you want to install DECnet-Plus? (Y/N) y
DECnet Phase IV is intalled on your system.
Before installing DECnet-Plus, you must remove DECnet Phase IV.
*Do you want to remove DECnet Phase IV? (Y/N) y
The following product has been selected:
DEC VAXVMS DECNET_PHASE_IV V7.2 Layered Product
Do you want to continue? [YES]
The following product will be removed from destination:
DEC VAXVMS DECNET_PHASE_IV V7.2 DISK$VAXV72INS:[VMS$COMMON.]
Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...100%
The following product has been removed:
DEC VAXVMS DECNET_PHASE_IV V7.2 Layered Product
Space remaining on system disk: 1458710 blocks
|
The procedure displays a list of the OpenVMS VAX and DECwindows support options you have selected and then provides a prompt that gives you the opportunity to change your selected options before they are installed:
The following options will be provided:
OpenVMS library
OpenVMS optional
OpenVMS Help Message
OpenVMS Management Station Software -- PC files
DECwindows base support
DECwindows workstation support with:
- 75 dots per inch video fonts
- 100 dots per inch video fonts
DECnet-Plus
Space remaining on system disk: 1458710 blocks
* Is this correct? (Y/N) y
|
If you answer Yes to this prompt, the procedure restores the OpenVMS required save set (VMS073.B) and purges the page, swap, dump, and authorization files.
If you answer No to this prompt, you can respecify the OpenVMS VAX and DECwindows options that you want to install. The procedure restores the DECwindows components you have chosen during Phase 2. For example:
During Phase 2 you will be required to provide input if:
o Your OpenVMS kit is multivolume
o You chose an alternate device
o You chose DECwindows options
Now copying over the OpenVMS and DECwindows V7.3 REQUIRED save set
%BACKUP-I-STARTVERIFY, starting verification pass
Purging pagefile, swapfile, dump file, and authorization
files back to one version.
Entering old page, swap, dump, errlog, and authorization files
in new directory tree.
Setting the startup command file for the next phase of the upgrade.
Renaming SYS$SYSDEVICE:[SYS0.SYSEXE]MODPARAMS.DAT to
SYS$SYSDEVICE:[SYS0.SYSEXE]MODPARAMS.DAT_OLD
Renaming SYS$SYSDEVICE:[SYS0.SYSEXE]MODPARAMS.DAT_NEW to
SYS$SYSDEVICE:[SYS0.SYSEXE]MODPARAMS.DAT
Renaming SYS$SYSDEVICE:[SYS0.SYSEXE]VAXVMSSYS.PAR_NEW to
SYS$SYSDEVICE:[SYS0.SYSEXE]VAXVMSSYS.PAR
|
After several minutes, the upgrade procedure indicates that the system will shut down to reboot the partially upgraded OpenVMS VAX system and displays information about how to reboot the system:
System shutting down to boot the new kernel system.
(Please ignore any error messages during the SHUTDOWN procedure.)
The distribution kit must remain on DKB200: and the system disk
must remain on VXPCSI$DKB100: in order to proceed to the next phase
of the upgrade.
The sysgen parameters are set to boot any system. Do not
change them during the reboot or the upgrade may fail
to execute properly!
Once the shutdown is complete, stop the system using the HALT
button on the computer control panel, or the BREAK key on the
console terminal if your system has no HALT button. Reboot the
system with the following command, replacing "ddcu" with the
name of the disk drive that contains the system disk.
B/F0000000 ddcu
The upgrade is set up to continue once the system reboots.
If, for some reason, the kernel V7.3 system should fail to boot,
you can boot into SYSBOOT by entering:
B/F0000001 ddcu
* Press RETURN to shut down system:
|
Once you have read the information displayed on the screen, press
Return to begin the shutdown.
7.3.11 Automatic System Reboot
If your system uses console media, it should automatically reboot from the SYSF directory when the shutdown is complete. If you have a MicroVAX or if your system does not reboot from SYSF, halt the system and boot from the [SYSF] directory. For most MicroVAX and VAXstation computers, use the BOOT command in the following format and substitute the device name of the system disk for ddcu:
>>> B/F0000000 ddcu |
If the system fails to boot, you can boot into SYSBOOT by entering the following:
>>> B/F0000001 ddcu |
For more information on booting your computer from the SYSF directory,
refer to the upgrade and installation supplement for your VAX computer.
7.3.13 Verifying System Time
When the system reboots, it displays a message similar to the following:
OpenVMS (TM) VAX Version V7.3 Major version id = 1 Minor version id = 0
System time is: 13-NOV-2000 10:46:26.34
Enter Yes to the next question to leave the system time unchanged
(the system clock continues to run unaffected)
Enter No to set a new system time
Enter ? to redisplay the time
* Is this correct? (Y/N/?)
|
Enter your response and press Return.
7.4 Upgrade Phase 2
At the beginning of Phase 2, the procedure displays a message similar to the following:
Continuing with OpenVMS VAX V7.3 Upgrade Procedure.
Upgrade Phase 2 13-NOV-2000 10:46:31.86
*********************************************************
%SYSTEM-W-TZGMT, your local timezone has defaulted to GMT
%SYSTEM-I-SETTZ, to set your local timezone use:
$ @SYS$MANAGER:UTC$TIME_SETUP.COM
*********************************************************
On MIN or UPGRADE system startup - CLUE is not run.
.
.
.
13-NOV-2000 10:53:26.27
|
You can ignore the time zone message. The UTC$TIME_SETUP.COM procedure runs during the final phase of the upgrade procedure.
During Phase 2, the upgrade procedure restores the rest of the library
(C), optional (D), Help Message (E), and OpenVMS Management Station
software (F) save sets and DECwindows support files if you elected to
install them.
7.4.1 Mounting Additional Magnetic Tape and Tape Cartridge Volumes
If your distribution kit is contained on open reel magnetic tapes or TK50 CompacTape cartidges, you may be asked to mount the second volume of the kit. If you need to mount the second volume, your system will display a message similar to the following:
Please mount volume 2 of the OpenVMS kit on <device> |
where: <device> is the magnetic tape or tape cartridge drive.
After you respond to the prompt, the system displays one of the following messages:
* Is the volume labeled OVMS VAX V7.3 BIN MT9 2/2 ready to be mounted? |
* Is the volume labeled OVMS VAX V7.3 BIN TK50 2/2 ready to be mounted? |
To respond to either message, do the following:
For information on which save sets are located on which tape volumes,
refer to Section 1.3.2.
7.5 Upgrade Phase 3
At the beginning of Phase 3, the procedure displays a message similar to the following:
Continuing with OpenVMS VAX V7.3 Upgrade Procedure.
Upgrade Phase 3 13-NOV-2000 11:05:47.14
|
During Phase 3, the upgrade procedure does the following:
At the beginning of Phase 4, the procedure displays a message similar to the following:
Continuing with OpenVMS VAX V7.3 Upgrade Procedure.
Upgrade Phase 4 13-NOV-2000 11:21:40.65
|
During Phase 4, the upgrade procedure does the following:
If the procedure requires that you manually reboot the system from the original system root (usually SYS0), do the following:
>>> EXIT $ COPY DEFBOO.SAV DEFBOO.COM $ COPY dddGEN.SAV dddGEN.COM |
>>> B ddcu |
>>> B/1 ddcu |
For more information on booting your system, refer to the upgrade and installation supplement for your VAX computer.
When the system reboots, the procedure displays a message similar to the following:
OpenVMS (TM) VAX Version V7.3 Major version id = 1 Minor version id = 0 |
After the system reboots, the procedure continues with upgrade Phase 5.
Do not move the system disk to a different drive. The system disk must
remain in the same drive for the procedure to continue with Phase 5.
7.7 Upgrade Phase 5
At the beginning of Phase 5, the procedure displays a message similar to the following:
Continuing with OpenVMS VAX V7.3 Upgrade Procedure.
Upgrade Phase 5 13-NOV-2000 11:36:36.95
|
During Phase 5, the upgrade procedure does the following:
At the beginning of Phase 6, the procedure displays a message similar to the following:
Continuing with OpenVMS VAX V7.3 Upgrade Procedure.
Upgrade Phase 6 13-NOV-2000 11:38:46.83
Configuring all devices on the system ...
|
| Previous | Next | Contents | Index |