OpenVMS Alpha Version 7.1
Upgrade and Installation Manual

The highest recommended baud rate for the Megahertz 28.8 FAX/Modem card is 9600. For access to the modem, Digital recommends that you use the following DCL and modem commands:

$ SET TERM/PERM/SPEED=9600/ALT/MODEM TTB0:
$ SET HOST/DTE TTB0:
at&s1 
at&r1

Audio Feedback Supported on PCMCIA Modem

Audio feedback is available for the telephone call status.

PCMCIA FAX Support

The Apex Data ClipperCom V.34 International Data/FAX Modem works correctly with the PMDF FAX and Gold-FAX software to transmit data.

The Megahertz 28.8 FAX/Modem works correctly with the PMDF FAX software to send and receive with line speeds up to 19.2 baud. However, if you are using Gold-FAX software to send a Fax, the maximum baud rate allowed with a Megahertz 28.8 FAX/Modem card is 9600 baud.

D.1.8 Audio Support

The DECsound utility included with DECwindows Motif Version 1.2--3 does not support the sound processor on the ALPHAbook 1 system. Audio support is available on the OpenVMS Multimedia services kit, a separately licensed layered product available from Digital.

D.1.9 Keyboard Mapping

The ALPHAbook 1 keyboard is an 88-key, PC layout keyboard. The following notes describe how to set up the keyboard and enable particular key functions.

Keyboard Setup

You can set up the keyboard to either follow the engravings or to map the keys in a manner that makes it easier for you as an OpenVMS user. To set up your keyboard either way, do the following:

Click on Options in the Session Manager box.
Select Keyboard from the list of options.

Select one of the following LK443 or LK444 keyboard types:

A keyboard type with the suffix _PC maps the keyboard to follow the engravings. For example, US_LK443AA_PC.
A keyboard type with the suffix _LK sets the keyboard to follow the LK style mapping common to OpenVMS systems. For example, US_LK443AA_LK.

Notes

The procedure for setting up your keyboard is the same as that required for all current AlphaServer and AlphaStation systems. The only difference is that the ALPHAbook 1 keyboard does not have all of the keys directly on it. (The next section describes how to generate those missing keys.)
You can also attach an LK411 (LK401 layout) compatible keyboard or a PCXAL (PS2 layout) keyboard directly to the AlphaBOOK 1 computer using the mini-docking station.

Key Functions

When mapping to an LK style keyboard, note the following:

The right ALT key does not transmit any code. Instead, the keyboard controller generates missing LK style keys when pressed in combination with this key. These alternate keys are engraved in grey on the keyboard. For example, pressing RIGHT-ALT-U ([grey 4]) provides the function of KP4.
Note
By default, the right ALT key is set for the special functions described in the ALPHAbook 1 User Guide (such as increasing or decreasing display brightness). To set the right ALT key to perform different functions so you can emulate a LK style keyboard, you must change this setting at the console level by entering the following command at the console prompt:
>>> SET HOTKEY OFF

After you enter this command, either enter the INIT command or powercycle the system. You can then use the right ALT key to perform the LK style keyboard actions described in this section.
Two keys are mislabeled. The KP_Subtract and KP_Add are engraved in grey on the minus (-) and plus (+) keys. However, the 0 (zero) and P keys actually provide the function for KP- and KP+ respectively.
NUMLOCK is generated by SHIFT-NUMLOCK and KP_ENTER is generated by RIGHT-ALT-ENTER.
There is no way to generate directly RIGHT-ALT, RIGHT-COMPOSE, or LEFT-COMPOSE. You can provide the function of the compose key by pressing LEFT ALT-SPACE.
You can generate missing function keys by pressing CAPS LOCK-Fn. Pressing CAPS LOCK adds a value of 10 to the function key (Fn) that you also press. For example, pressing CAPS LOCK-F1 generates the F11 key; pressing CAPS LOCK-F2 generates the F12 key.

Use the following table to help you determine which keys to press to provide the function of the corresponding LK style key.

LK Style Key	ALPHAbook Key Combination
PF1	[SHIFT] [grey Numlock]
PF2	[RIGHT ALT] [grey /]
PF3	[RIGHT ALT] [grey *]
PF4	[RIGHT ALT] [0]
KP,	[RIGHT ALT] [P]
KP-	[LOCK] [RIGHT ALT] [P]
KP_ENTER	[RIGHT ALT] [ENTER]
KP.	[RIGHT ALT] [grey .]
KP0	[RIGHT ALT] [grey 0]
KP1	[RIGHT ALT] [grey 1]
KP2	[RIGHT ALT] [grey 2]
KP3	[RIGHT ALT] [grey 3]
KP4	[RIGHT ALT] [grey 4]
KP5	[RIGHT ALT] [grey 5]
KP6	[RIGHT ALT] [grey 6]
KP7	[RIGHT ALT] [grey 7]
KP8	[RIGHT ALT] [grey 8]
KP9	[RIGHT ALT] [grey 9]
FIND	INS
INS	HOME
REMOVE	PAGE UP
SELECT	DEL
PREV	END
NEXT	PAGE DOWN
HELP	PRINT SCREEN
DO	SCROLL LOCK

D.1.10 Shutting Down the System

Previously, turning off the ALPHAbook 1 computer without first shutting down the system caused excessive battery drain. Although Digital recommends that you still run the OpenVMS shutdown procedure (@SYS$SYSTEM:SHUTDOWN.COM) before turning off your computer, it is no longer a requirement.

D.1.11 OpenVMS Cluster Restrictions

Due to controller limitations of the PCMCIA Ethernet card, Digital recommends that you use the ALPHAbook 1 computer only as a satellite node in a cluster environment, rather than as a cluster boot node.

D.1.12 Booting Across the Ethernet

On a busy network segment, the ALPHAbook 1 system may require several retries to downline load a MOP image if you are booting the system as a cluster satellite member. In addition, the system will be unable to reboot until the system has been powercycled. These console problems will be fixed in a future release.

D.2 AlphaServer 1000A Notes

The following sections contain release notes specific to the AlphaServer 1000A computer.

D.2.1 Bus Probe Algorithm

You cannot set the console variable BUS_PROBE_ALGORITHM to OLD on AlphaServer 1000A computers. The default setting is NEW. If you reset the bus probe algorithm to OLD, your OpenVMS system will not boot correctly.

D.2.2 Installation Failure with DEFPA Adapter

When you attempt to install the OpenVMS operating system on an AlphaServer 1000A computer that uses a DEFPA adapter, the installation might fail, resulting in a KERNEL STACK NOT VALID HALT error message. Should this failure occur, powercycle your system and restart the installation.

D.3 AlphaServer 41000 Notes

The following sections contain release notes specific to the AlphaServer 4100 computer.

D.3.1 MEMORY_TEST EV Console Variable

Be sure the AlphaServer 4100 console setting MEMORY_TEST EV is set to FULL. The following console commands illustrate how to show and set this variable:

>>> SHOW MEMORY_TEST 
>>> SET MEMORY_TEST FULL

D.3.2 EISA Configuration Utility (ECU)

AlphaServer 4100 systems do not support automatic startup of the ECU (EISA Configuration Utility). Instead, follow the procedure described in this section.

Note
The OpenVMS operating system does not support the EISA bus on AlphaServer 4100 systems. If your computer is running another operating system that supports the EISA bus and you want to switch to the OpenVMS operating system, you may have to remove your EISA boards before running the ECU.
For more information about using the ECU, see the AlphaServer 4100 System Drawer User's Guide.

In the SRM console, enter the arc command. This starts the AlphaBIOS facility.

Press the F2 key after the following display:

 +----------------------------------------------------+ 
 |      No Operating System Selections Found          | 
 +====================================================+ 
 |                                                    | 
 | Press <F2> to enter Setup and configure the system.| 
 |                                                    | 
 +====================================================+ 
 | F2=Setup                                           | 
 +----------------------------------------------------+

Use the DownArrow key to select Utilities. Then use either the RightArrow or Enter key to highlight the first submenu entry, "Run ECU From Floppy...". The display is as follows:

   +--------------------------------------------------------------------------+ 
   |                            AlphaBIOS Setup                       F1=Help | 
   +==========================================================================+ 
   | +---------------------------------+                                      | 
   | | Display System Configuration... |                                      | 
   | | Upgrade AlphaBIOS               |                                      | 
   | | Hard Disk Setup...              |                                      | 
   | | CMOS Setup...                   |                                      | 
   | | Install Windows NT             +----------------------------+          | 
   | | Utilities                    >>| Run ECU From Floppy...     |          | 
   | | About AlphaBIOS...             | OS Selection Setup...      |          | 
   | +--------------------------------| Run Maintenance Program... |          | 
   |                                  +----------------------------+          | 
   |                                                                          | 
   |                                                                          | 
   |                                                                          | 
   |                                                                          | 
   |                                                                          | 
   | +----------------------------------------------------------------------+ | 
   | |                                                                      | | 
   | | Press ENTER to highlight available utilities                         | | 
   | |                                                                      | | 
   | |                                                                      | | 
   | +----------------------------------------------------------------------+ | 
   +==========================================================================+ 
   | ESC=Exit                                                                 | 
   +--------------------------------------------------------------------------+

Insert the ECU diskette in the floppy drive (if it isn't there already).
Press the Enter key to run the ECU.
After the ECU has run and returns control to AlphaBIOS, press the reset button to restart the system.

The OpenVMS operating system does not support the EISA bus on AlphaServer 4100 systems. If you switch from another operating system to OpenVMS on AlphaServer 4100 systems, you may have to remove your EISA boards and run the EISA Configuration Utility (ECU).

To run the ECU on other platforms, use the ECU command. To run the ECU on the AlphaServer 4100, use the ALPHABIOS command; and then run the ECU from the ALPHABIOS utility menu.

For more information about using the ECU, see the AlphaServer 4100 System Drawer User's Guide.

D.3.3 FRU Table Error

After you boot the OpenVMS operating system, the following message might display on the screen:

*****Config packet buffer allocation failure: Continuing without writing Errorlog

This message indicates that the FRU (Field Replaceable Units) table is too large for the default SYSGEN parameter ERLBUFFERPAGES. It is a warning message only and indicates that the FRU table was not written in the Error Log on this reboot.

If your system displays this message, Digital recommends that you change the ERLBUFFERPAGES parameter from 4 (the default) to 6. Following is an example of how to use the SYSGEN utility to accomplish this task:

$ MCR SYSGEN 
SYSGEN>use current 
SYSGEN>set erlbufferpages 6 
SYSGEN>write current 
SYSGEN>exit

If this warning appears again after you reboot the system, increase the ERLBUFFERPAGES parameter in increments of 2 (maximum value is 32) until the warning message is no longer displayed. The final size of ERLBUFFERPAGES (the value that resolves the problem) will vary depending on the configuration of your system.

D.4 AlphaServer 2100 Notes

The following section contains information specific to the AlphaServer 2100 series computer.

D.4.1 Console Display

On AlphaServer 2100 and 2100A systems, a console display similar to the following is normal and does not represent system errors:

P00>>>SET CONSOLE SERIAL 
P00>>>INIT 
 
VMS PALcode X5.48-112, OSF PALcode X1.35-81 
 
starting console on CPU 0 
initialized idle PCB 
initializing semaphores 
initializing heap 
initial heap 1c0c0 
memory low limit = 132000 
heap = 1c0c0, 13fc0 
. 
. 
. 
probing hose 0, PCI 
probing PCI-to-EISA bridge, bus 1 
probing PCI-to-PCI bridge, bus 2 
*** unable to assign PCI base address 
*** bus 2, slot 7, function 0, size 00001000 (16 bit I/O) 
bus 1, slot 1 -- fra -- DEFEA 
bus 1, slot 2 -- vga -- Compaq Qvision 
bus 1, slot 3 -- pua -- KFESA 
bus 2, slot 1 -- pka -- NCR 53C810 
bus 2, slot 6 -- pkb -- NCR 53C810 
bus 2, slot 7 -- pkc -- DEC KZPSA 
bus 0, slot 7 -- ewa -- DECchip 21041-AA 
initializing keyboard 
Memory Testing and Configuration Status 
Module   Size    Base Addr   Intlv Mode  Intlv Unit  Status 
------   -----   ---------   ----------  ----------  ------ 
  0       64MB   00000000      1-Way         0       Passed 
Total Bad Pages 0 
Testing the System 
Testing the Disks (read only) 
Testing the Network 
econfig:            20041 99 
econfig:            20042 04 
econfig:            20043 00 
AlphaServer 2100A Console V4.3-130, built on Oct 26 1996 at 19:44:57 
P00>>>P

Note that in the previous display, the KZPSA adapter is successfully installed despite the error message displayed in the following lines:

*** unable to assign PCI base address 
*** bus 2, slot 7, function 0, size 00001000 (16 bit I/O)

D.4.2 SCSI Controller Restriction

The Adaptec 1740/1742 SCSI controller (PB2HA--SA) is not supported on AlphaServer 2100 systems having more than 1 gigabyte (GB) of memory. If the controller is connected to such a system, the following message appears on the operator's console:

%PKJDRVR-E- The direct DMA window does not map all of memory. Port is going OFF LINE.

D.5 AlphaServer 2100A Notes

The following section contains information specific to the AlphaServer 2100A computer.

D.5.1 Trio64 Graphics Adapter

You must have a Trio64 "Plug and Play" (PNP) graphics adapter for the graphics card to operate behind the PCI-PCI bridge (on the secondary PCI bus) on all models of the AlphaServer 2100A computer. This graphics adapter will also operate if placed in front of the bridge (the primary PCI bus).

D.6 Graphics Support

The following sections contain information about support for Alpha computers with graphics capabilities.

D.6.1 TGA Graphics

AlphaServer computers do not support TGA graphics.

D.6.2 S3 Multihead Graphics

For this release of the OpenVMS operating system, Alpha computers equipped with S3 Trio32 or Trio64 graphics cards support single screen display only. Multihead graphics are not supported.

D.6.3 Console Window

System operator console window support (for example, pressing Ctrl/F2) has been disabled. Support for the operator console is now provided using a Motif-based window option that is enabled during DECwindows startup. Refer to the DECW$PRIVATE_APPS_SETUP.TEMPLATE file in SYS$COMMON:[SYSMGR] for details about how to enable this feature.

Caution
Directing any output directly to the operator console window (OPA0: device) might cause a system crash during a simultaneous graphics operation.

Appendix E
Preparing to Use OpenVMS Management Station

During the OpenVMS Version 7.1 installation or upgrade procedure, the OpenVMS Management Station software is automatically installed on your OpenVMS system disk when you accept all the default values. If you did not accept the default values and did not manually select the OpenVMS Management Station component, you must add those files to your OpenVMS system disk before you follow the instructions in this appendix. Use the OpenVMS Version 7.1 operating system CD--ROM and the DCL command PRODUCT RECONFIGURE VMS to add the OpenVMS Management Station files to your system. (See OpenVMS System Management Utilities Reference Manual: M--Z for complete information about using the PRODUCT command.)

After you have ensured that OpenVMS Management Station software is installed on your system, follow the procedures described in this appendix.

E.1 Preparing Your OpenVMS System

You must prepare your OpenVMS system to run the server software so that your system can properly interact with the PC running the client software. The procedures include the following:

Set up within a mixed-architecture cluster environment (if applicable).
Start the server on other nodes.
Update the printer database.
Edit the system files.
Allow OpenVMS Management Station to control the printer environment.
Keep your printer environment up to date.
Check if running third-party TCP/IP stacks.
Recover from a failure.
Determine and report problems.

E.1.1 Files Installed on Your OpenVMS System

The following files are created on your OpenVMS system when the OpenVMS Management Station server is installed:

SYS$SYSTEM:TNT$SERVER.EXE
SYS$STARTUP:TNT$STARTUP.COM
SYS$STARTUP:TNT$SHUTDOWN.COM
SYS$STARTUP:TNT$UTILITY.COM
SYS$TEST:TNT$IVP.COM
SYS$COMMON:[SYSTEST.TNT]TNT$SERVER_IVP.EXE
SYS$HELP:TNTV20.RELEASE_NOTES

These optional files are created when you install PC installation media files:

SYS$COMMON:[TNT.CLIENT]DISKIMAG.EXE
SYS$COMMON:[TNT.CLIENT]TNTCLID1.IMG
SYS$COMMON:[TNT.CLIENT]TNTCLID2.IMG
SYS$COMMON:[TNT.CLIENT]TNTCLID3.IMG
SYS$COMMON:[TNT.CLIENT]TNTCLID4.IMG
SYS$COMMON:[TNT.CLIENT]TNTCLID5.IMG
SYS$COMMON:[TNT.CLIENT]TNTCLID6.IMG

These files are created when the server is started:

SYS$COMMON:[SYSEXE]TNT$UADB.DAT
SYS$COMMON:[SYSEXE]TNT$ACS.DAT
SYS$COMMON:[SYSEXE]TNT$JOURNAL.TNT$TRANSACTION_JOURNAL

E.1.2 Setting Up in a Mixed-Architecture Cluster Environment

The OpenVMS Management Station server creates three main configuration files:

TNT$UADB.DAT
TNT$ACS.DAT
TNT$JOURNAL.TNT$TRANSACTION_JOURNAL

In a common-environment cluster with one common system disk, you use a common copy of each of these files located in the SYS$COMMON:[SYSEXE] directory on the common system disk, or on a disk that is mounted by all cluster nodes. No further action is required.

However, to prepare a common user environment for an OpenVMS Cluster system that includes more than one common VAX system disk or more than one common Alpha system disk, you must coordinate the files on those disks.

Rules: The following rules apply:

Disks holding common resources must be mounted early in the system startup procedure, such as in the SYLOGICALS.COM procedure.
You must ensure that the disks are mounted with each cluster reboot.

Follow these steps to coordinate files:

Decide where to locate the files. In a cluster with multiple system disks, system management is much easier if the common system files are located on a single disk that is not a system disk.
Copy TNT$UADB.DAT, TNT$ACS.DAT, and
TNT$JOURNAL.TNT$TRANSACTION_JOURNAL to a location other than the system disk.

Edit the file SYS$COMMON:[SYSMGR]SYLOGICALS.COM on each system disk and define logical names that specify the location of the cluster common files.
Example: If the files will be located on $1$DJA16, define logical names as follows:

$ DEFINE/SYSTEM/EXEC TNT$ACS - 
_$ $1$DJA16:[VMS$COMMON.SYSEXE]TNT$ACS.DAT
 
$ DEFINE/SYSTEM/EXEC TNT$UADB - 
_$ $1$DJA16:[VMS$COMMON.SYSEXE]TNT$UADB.DAT
 
$ DEFINE/SYSTEM/EXEC TNT$JOURNAL - 
_$ $1$DJA16:[VMS$COMMON.SYSEXE]TNT$JOURNAL.TNT$TRANSACTION_JOURNAL

To ensure that the system disks are mounted correctly with each reboot, follow these steps:
1. Copy the SYS$EXAMPLES:CLU_MOUNT_DISK.COM file to the [VMS$COMMON.SYSMGR] directory, and edit it for your configuration.
2. Edit SYLOGICALS.COM and include commands to mount, with the appropriate volume label, the system disk containing the shared files.
  Example: If the system disk is $1$DJA16, include the following command:
```
$ @SYS$SYSDEVICE:[VMS$COMMON.SYSMGR]CLU_MOUNT_DISK.COM -
_$ $1$DJA16: volume-label
```

E.1.3 Start the Server on Other Nodes

If you plan to run OpenVMS Management Station on more than one node in an OpenVMS Cluster without a reboot, you need to start the software on those nodes. Enter the following command:

$ @SYS$STARTUP:TNT$STARTUP.COM

If you are performing an upgrade or a reinstallation and OpenVMS Management Station is already running on the node, add the RESTART parameter to the startup command, as follows:

$ @SYS$STARTUP:TNT$STARTUP.COM RESTART

E.1.4 Update the Printer Database

When you installed OpenVMS Management Station, the installation started the OpenVMS Management Station server on the installation node and created an initial version of the printer database file TNT$ACS.DAT. However, this initial version of the database might not contain complete device and queue information for your OpenVMS Cluster system.

To complete the database, first start the OpenVMS Management Station server on each node in your cluster. The instances of the server communicate with each other to determine device and queue information, and the server must be running on each node for this communication to take place.

Once you have started the server on each node, run the following procedure to update the printer database:

$ @SYS$STARTUP:TNT$UTILITY UPDATE PRINTERS

E.1.5 Edit the System Files

To start the OpenVMS Management Station server from your system startup files, insert the following line into your system startup procedures (usually SYS$MANAGER:SYSTARTUP_VMS.COM) after both the Queue Manager and network are started, but before ENABLE AUTOSTART/QUEUES.

$ @SYS$STARTUP:TNT$STARTUP BOOT

(The best place for this is immediately prior to the ENABLE AUTOSTART/QUEUES command.)

Note
Remove any other invocations of TNT$STARTUP you might have added in previous releases of the OpenVMS Management Station.
OpenVMS Management Station cannot start until the network has started. If you start your network using a batch process, OpenVMS Management Station might start before the batch process completes and the network is started.

Add the following command line to the system shutdown file,
SYS$MANAGER:SYSHUTDWN.COM:

$ @SYS$STARTUP:TNT$SHUTDOWN.COM

E.1.6 Allow OpenVMS Management Station to Control the Printer Environment

Placing the server startup before ENABLE AUTOSTART/QUEUES in the system startup procedure allows the server to start any queues not already started by your existing DCL command procedures.

It is not necessary to remove your existing queue startup DCL procedures immediately. The OpenVMS Management Station server will recognize that you started a queue with your command procedures and will assume that you want it that way.

As you become familiar with the server's management ability, you can remove or comment out the DCL commands and procedures that perform these tasks and allow OpenVMS Management Station to control your printer environment.

E.1.7 Keep Your Printer Environment Up to Date

The OpenVMS Management Station server installation creates a file named SYS$STARTUP:TNT$UTILITY.COM. This command procedure scans the OpenVMS system and updates the database of known printers, queues, and related devices. TNT$UTILITY.COM runs at regular intervals to keep the database files synchronized with the actual system.

E.1.7.1 When Does TNT$UTILITY.COM Run?

This TNT$UTILITY.COM runs:

As part of the OpenVMS Management Station installation.
When you specifically invoke it.

At periodic intervals as a background thread. Two logical names control how often it runs:

Logical Name	Description
TNT$PRINTER_RECON_INTERVAL	How often TNT$UTILITY.COM should run, in minutes, from when the server was last started on this node. If you do not define this logical, the default value is 1440 minutes (24 hours).
TNT$PRINTER_RECON_INTERVAL_MIN	The minimum number of minutes that must elapse before TNT$UTILITY.COM should run again, starting from when the database was last updated. If you do not define this logical, the default value is 60 minutes (1 hour).

You can think of these logicals as meaning "run TNT$UTILITY.COM this often (TNT$PRINTER_RECON_INTERVAL), but make sure this much time has elapsed since the database was last updated (TNT$PRINTER_RECON_INTERVAL_MIN)."

  6486P010.HTM
  OSSG Documentation
   6-DEC-1996 10:35:22.63

Legal

OpenVMS Alpha Version 7.1 Upgrade and Installation Manual