VMS 4.4 Release Notes

This document, "VAX/VMS Release Notes Version 4.4" (April 1986), provides comprehensive information for users, system managers, and developers regarding the VAX/VMS Version 4.4 operating system. It supersedes previous release notes and covers new features, changes, problems, restrictions, documentation updates, and detailed upgrade procedures.

Key areas covered include:

1. Upgrade Information:

   • Procedures: Detailed steps for upgrading a single system (including 5 phases) and VAXcluster environments (rolling or concurrent upgrades).
   • Considerations: Emphasizes backing up the system disk, specific system parameter (SYSGEN) settings, and managing layered products (some require re-installation, others are incompatible with VMS 4.4).
   • Console Media: Instructions for building and updating console diskettes (e.g., for VAX-11/782 systems) due to increased VMB.EXE size.
   • Mixed Clusters: Notes on running VAXcluster nodes with mixed VAX/VMS 4.3 and 4.4 versions, including specific SYSGEN parameter (VMSD1) adjustments for batch/print and RMS compatibility.

2. New and Changed Features:

   • General User: Expanded command line recall, new DCL commands (CALL, GOSUB, RETURN, SET SYMBOL/SCOPE, SUBROUTINE, ENDSUBROUTINE), and allowing hyphens in file specifications and logical names.
   • System Manager:
     • Networking: DECnet-VAX now supports cluster alias node identifiers, shared permanent database files (NETNODE.DAT split), a new Ethernet circuit device (DELUA), and enhanced X.25 protocol support.
     • Utilities: Updates to Show Cluster Utility (new commands, definable keys, multiple display windows), Authorize Utility (new /ATTRIBUTES keyword, enhanced /ACCESS, changes to Secondary Passwords, new AUTOLOGIN flag), Batch/Print Facility (new START/QUEUE/MANAGER qualifiers, default forms), SYSGEN (CONNECT CONSOLE /REMOTE, MOUNT/CACHE=TAPE_DATA), Monitor Utility (new CLUSTER class for performance data, CONVERT command, /NODE qualifier), and AUTOGEN command procedure (automatic calculation of LRPSIZE, VAXCLUSTER, page/swap file sizes).
     • File Management: RMS now supports full shared sequential files.
     • Hardware Support: VAX 8600 memory additional error logging.
   • Application Programmer: Linker utility now permits debugging for shareable images, Debugger enhancements (screen mode, new commands), ANALYZE/RMSFILE utility new commands for interactive file structure examination, Error Log Utility improvements, SORT/MERGE utility changes (universal message symbols, /INCLUDE and /OMIT qualifier fixes), Print Symbiont now supports user-defined I/O routines, new VAX/VMS System Services ($CHECKACCESS, $GETUAI, $SETUAI, DYNAMIC attribute), and new Run-Time Library features (including DTK$ facility for DECtalk devices).
   • System Programmer: System Dump Analyzer (SDA) new commands (ATTACH, SPAWN) and qualifiers, CSMA/CD Data Link Drivers (IEEE 802 standard support), and CI Port Driver (PADRIVER) updates (microcode support, SCS virtual circuit timeouts and related SYSGEN parameters).

3. Problems, Restrictions, and Notes:

   • Incompatibilities: VAX-11/730 Dual-RL02 systems are no longer supported. VAX LISP Version 1.2 is incompatible with VAX/VMS 4.4. VAX ACMS Version 1.2 will make the VAX/VMS system unusable.
   • Cautions: Extended file names/types (longer than 9 characters or with '$', '_') may not be compatible with older VAX/VMS 3.x systems or PDP-11 processors. A *mandatory rebuild* of the Standalone Backup Kit is required after upgrade. Mail Utility has a restriction in mixed VAXcluster versions (4.4 and older).
   • System Configuration: Specific CI port microcode revision levels are required. Restrictions apply to booting from multiple UDA50 systems. A time limit exists during SYSBOOT on HSC-controlled disks. User-created cluster quorum files can lead to corruption.
   • Documentation: Numerous corrections and additions across various VAX/VMS manuals are detailed. TECO requires compatibility mode on VAX systems without built-in compatibility mode hardware.

The document emphasizes careful reading of all sections before attempting an upgrade, especially concerning compatibility and mandatory post-upgrade procedures.