Analyze your VAX

• Inventory checklist, Microsoft Word format
• Inventory checklist, Adobe PDF format  (fax to 1-614-868-1671

• For some of these things, we have to assume that VMS (OpenVMS or VAX/VMS) is being used. If you're using VAXELN or Digital Unix, please call 1-888-I-LUV-VAX (1-888-458-8829) toll-free in the US or Canada, or send email.
• For some tests, a  console terminal is necessary, connected to the console port.  Which connector is the console depends on the type of VAX, but is usually a "phone" type connector with the plastic clip off to one side (called a "MMJ" connector).  Set the terminal to 9600 baud, no parity, 1 stop bit.  If you need to borrow hardware to conduct these tests, it is available from Quayle Consulting.
• If your system has a label that says "AlphaServer", you actually have an Alpha, not a VAX.  Most of the following steps apply, since VMS is still VMS, but there will be differences.
  

Please note:  This procedure is copyrighted by Quayle Consulting Inc., 2004, and is for the sole use by customers of Quayle Consulting.

System Information

• Please tell us what you call your system.
• Indicate how mission-critical it is.  If you have more than one VAX, fill out a separate list for each system, if possible.

• There should be a nameplate on the front of system.  Copy the string exactly.  For example, "MicroVAX 3100-M38".  "VAX", "MicroVAX", and "VAXstation" are all different.
  
• The following require that the VAX be shut down properly and then powered-cycled.
• Some VAX systems display a code (like "KA42-1") when initially powered on.
• After the self-test is complete, the VAX will display the "dagger" prompt (>>>)".  Some VAX models allow you to type "SHOW CONFIG" at the prompt.
• Some VAX models allow the command "SHOW VERSION" at the dagger prompt.  This will list the firmware version information.
  

• If the VAX is at the dagger prompt (see previous section), you may be able to type "SHOW MEM".  Please report this information.  Other systems will display total memory when powered-cycled.
• (VMS) Total memory can be displayed with the command "SHOW MEMORY" when logged in as username SYSTEM.  The "Main Memory" line gives the total size.

• (VMS) The beginning of the very first line from command "SHOW SYSTEM" shows the VMS version.  It usually starts with "VAX/VMS" or "OpenVMS".  The entire version number is important.

Process Information

• Count the number of processes from the "SHOW SYSTEM" output (see previous section).  If this is not typical, please provide an estimate.
• The first column of numbers from "SHOW USERS" shows the number of users on the system.  If this is not typical, please estimate the peak number of concurrent users.
• Enter the command "MONITOR SYSTEM".  This will display CPU utilization.  It is possible to run MONITOR over a long period to capture peaks.
• If the I/O rates exceed 50 per second, total between Direct and Buffered, please make a note of it.
• A "SHOW NETWORK" command may report the availability of DECnet and/or TCP/IP.
  

    Users can be connected to a VAX several ways.  Many systems use more than one method.

•  Telnet.  One of the TCP/IP protocol family.  Used to create a terminal session on a remote host, including a VMS system.
  
• SSH.  A newer version of Telnet, which supports encrypted traffic.  A freeware implementation of SSH version 1 is available for VAX.
• Serial lines.  Also known as "RS-232" or possibly "current loop", these typically connect to "dumb terminals" (VT52, VT100, VT220, etc.).  All VAX systems have at least one serial line for the console.  Most VAX systems have a maximum of 3 MMJ (look sort of like a phone jack) connectors.  Some also have a DB-25 modem connector.  Expansion boards can be added to many systems to provide more serial ports, including the infamous "harmonica connector".
• Terminal server serial lines.  These are like direct serial lines, but connect to a separate device, usually a DECserver.  This is then connected to the VAX via an Ethernet (coax or Cat 5).  Please specify the type of terminal server(s).
  
• Pathworks allows Windows users to "see" files on the VAX.  SAMBA is an open-source equivalent.
  
• LAT.  This protocol is used to support connections from terminal severs and PC's running Linux.  Lightweight and fast, but cannot be routed through the Internet like TCP/IP.
• DECnet.  This set of protocols is similar to TCP/IP.  There's a "SET HOST" capability like Telnet.  VMS machines can share files almost as though they were local, unlike FTP transfers.
• Modem.  External users can "dial in" to the VAX.  Many VAX models have a DB-25 on the back to which to attach a modem.  Some terminal server models also support modem connections.
• DECwindows.  This is the VMS version of X-windows, a graphical interface.  A VAXstation has a "local" DECwindows session that appears on its dedicated monitor.  PC's, X terminals, and other VMS machines can display DECwindows via TCP/IP, DECnet or LAT.  All these tend to be more resource-intensive that character-only sessions like Telnet.
• Clustering.  VMS machines can be collected into a "cluster" for high availability and resource sharing.

Disk Drives

At the dagger prompt:

• Some VAX models allow you to type "SHOW DEV".  This will list all the disks and tapes.  The SCSI or DSSI ID of the adapter(s) will also be displayed.

• The command "SHOW DEVICE D/FULL" will display a list of all the disk drives.
• This may be a long listing.  Press Ctrl-S to stop the listing, and Ctrl-Q to resume.
  
• Disks mapped using the NFS protocol (part of TCP/IP) start with "DNFS" and can be ignored for the checklist.
  
• Disks that start with DSA are RAID-1 "shadow" sets that are composed of one to three other disks.  Once the RAID set up is up-to-date, all members have the same information.  Report only one of the shadow set members.
• On a clustered system, disks served from other VMS systems will appear on the list.  The device names will start the other system's name, followed by a "$".  Include these on only that system's checklist.
• If an InfoServer is present, disk devices starting with "DAD" will appear.  These can be ignored, unless the InfoServer functionality is being migrated into the VAX replacement.
  
• A "block" is 512 bytes.  So, to get the size in MB, divide the number of blocks by 2048.
• Enter the controller type, if known.
  

"Which of the listed disks are used as removable devices?"    On VAX  systems, this will usually be RF-series disk packs and CD-ROM drives.

"Are the removable disks used to exchange information with other systems or only as backup?"   This might identify other systems which need to be replaced.

Tape Drives

At the dagger prompt:

• Some VAX models allow you to type "SHOW DEV".  This will list all the disks and tapes.  The SCSI or DSSI ID of the adapter(s) will also be displayed.

• Commands "SHOW DEVICE MU/FULL" and "SHOW DEVICE MK/FULL" will list all the tape drives..
• These may be long listings.  Press Ctrl-S to stop the listing, and Ctrl-Q to resume.
  
• Disks mapped using the NFS protocol (part of TCP/IP) start with "DNFS" and can be ignored for the checklist.
  
• Disks that start with DSA are RAID-1 "shadow" sets that are composed of one to three other disks.  Once the RAID set up is up-to-date, all members have the same information.  Report only one of the shadow set members.
• On a clustered system, tapes served from other VMS systems will appear on the list.  The device names will start the other system's name, followed by a "$".  Include these on only that system's checklist.
• If an InfoServer is present, tape devices starting with "MAD" will appear.  These can be ignored, unless the InfoServer functionality is being migrated into the VAX replacement.
• Tape formats typical on VAXes are:  TK-50, TK-70, DAT (4 mm), and 8 mm.  IBM 3480 is less common.  If the drives were made by DEC, and start with "TZK" or "TKZ", these drives can be moved to CHARON-VAX immediately.
  
• Enter the controller type, if known.
  

"Used for Multi-Volume Operations?"    Tape emulation is available in some versions of CHARON-VAX.  Multi-volume operations are not a supported configuration for emulated tape drives.

If tape is only used for backup, there are other ways to back up a CHARON-VAX system that can be more convenient and faster.  If tapes are used for archival storage or data exchange, these functions may have to be supported in the migrated system.

Serial Lines

All serial lines should be listed.  If connected to a terminal server, please indicate under "controller".  If directly connected to the VAX, include the controller type, if known.

Under VMS:

• The command "SHOW DEVICE T/FULL" lists all the hardware serial ports (start with "TT") and TCP/IP Telnet connections (start with "TN").  Ignore the "TN" devices.
• On VAXstations, when DECwindows is installed, two of the TT devices will be "device type DECwindows input device".  These are the keyboard and mouse.
• If the "Owner process ID" is not zero, the "Owner process" field shows the name of the process that is using the line.  It can be cross-checked against the "SHOW SYSTEM" output..
  
• The command "SHOW DEVICE LT/FULL" lists all the LAT ports that connect directly to the VAX.
• LAT ports with a "Owner process" of "DECW$FD" can be ignored, as those are the DECwindows font server.
• If the "Owner process ID" is not zero, the "Owner process" field shows the name of the process that is using the line.  It can be cross-checked against the "SHOW SYSTEM" output..

"Are any of the serial lines connected to any programmable devices that change the baud rate during the communication?"   If true, the target machine's serial port hardware becomes critical.  Fortunately, this is encountered very rarely in production systems.

Ethernet Adapters

VAX systems can have a maximum of two Ethernet interfaces.  Some VAX models can only have one.

• Depending on the VAX model, Ethernet interfaces can be plugged into the bus (DEQNA, DELQA, DESTA), or are on the motherboard. If unknown, enter "unknown" under "Type".
• Connectors vary on Ethernet interfaces.  Common ones are coaxial cable (usually black), AUI (usually white), or twisted-pair (Cat 5 wire).  If the cable goes to a device known as a DELNI, DEMPR, or DESPR, please indicate.
• Any other comments that might be useful.
  

Printers

VAX systems are frequently connected to printers.  Please specify all printers and how they are connected.

• Serial printers are connected either to the VAX directly or through a terminal server.
• Some VAX systems have one or more connectors that are called "parallel" or "Centronics".
• Network printers connect through the Ethernet, using TCP/IP or LAT.

Q-Bus Hardware

IEEE 488 Controllers

• The card made by Digital was the IEQ-11.  Other companies, including National, also made IEEE 488 interfaces.  Specify the kind of interface under "Type".
• The list of devices and which ones are talkers and listeners will be used to create custom test plans for this interface.

Synchronous Connections

Various synchronous cards (as opposed to serial) were available for Q-bus systems.  Please specify all items as fully as possible.

Other

Disk, tape, and Ethernet interfaces should not be included, since they are replaced by modern or emulated hardware.  DMA support should be confirmed with the manufacturer's documentation.

Software Applications and Middleware

While CHARON-VAX emulates a VAX in all respects, creating a complete test plan requires a list of application software.  Include all VMS layered products such as PathWorks and language compilers.

Starting with VMS 5.0, most VMS products require a Product Authorization Key (PAK) license.  From VMS, logged in as SYSTEM, capture the output from command "SHOW LICENSE".

Some applications require special license keys, such a specific system ID number or Ethernet adapter with a particular address.  Please report these items.

TCP/IP is an optional component for VMS, and so it may not be installed.  Also, there are three different TCP/IP implementations available:  UCX (from DEC/Compaq/HP), Multinet (from Process Software), and TCPware (also from Process Software).  Do the following to determine the the type and version number, if installed.  All commands are from VMS when logged in as SYSTEM.

• If the UCX stack is installed, the type and ECO level will be reported by command "UCX SHOW VERSION".
• If the Multinet stack is installed, the type and product elements will be reported by command "MULTINET SHOW /LICENSE".
• If the TCPware stack is installed, it will be reported, along with other VMS licenses, by command "SHOW LICENSE".

Support Status

Listing each type of support on the system provides the opportunity to realize cost-savings possible by migration.

Migration Goals

• Increase performance
•  Increase reliability
• Move to newer hardware
• Move to industry-standard platform
•  Reduce hardware support costs
•  Reduce system size
• Reduce power consumption

How did you hear about CHARON-VAX and Quayle Consulting?

Quayle Consulting advertises on all these sites.  Please help us to identify the effectiveness of our advertising, and send a "thank-you" to any referrer!

• Newsgroup comp.os.vms
• google.com
• Openvms.org site
• HP ITRC site
• Stromasys’ list of authorized resellers
• Reference from Stromasys
• Internet search (please specify search engine)

Cluster Analysis