A From:	CSBVAX::MRGATE!OBERMAN@icdc.llnl.gov@SMTP 25-APR-1988 17:35  To:	ARISIA::EVERHART< Subj:	DEC has announced VMS V5.0, but don't hold you breath.    O Received: from icdc.llnl.gov by KL.SRI.COM with TCP; Fri 22 Apr 88 09:19:12-PDT  Date: Fri, 22 Apr 88 09:15 PDTI From: "Kevin Oberman, LLNL, (415)422-6955, L-156" <OBERMAN@icdc.llnl.gov> ? Subject: DEC has announced VMS V5.0, but don't hold you breath.  To: info-vax@kl.sri.COM # X-VMS-To: IN::"info-vax@kl.sri.com"   I DEC announced VMS V5.0 on the 19th. It will be shipped with 6200 and 8000 I mult-processor systems starting more or less immediately, but won't go to E the real world for a while. The official satement is Q1 of 1989 which ! translates to the summer of 1988.   N Here is some info on V5.0. This is NOT making any commercial endorsment! And IL don't promise that I didn't make errors in this. It involved a lot of typingI and is based on a combination of experiance playing with V5.0 and the DEC  announcement information.   N I have tried to avoid making this a look like a sales pitch, but since quite aM bit of the info comes from DEC marketing types, it does seem a bit `pushy'. I O assume the readers of this list already have VMS and are interested in V5.0 for L planning or are UNIX users and don't really care. I don't work for DEC and IO don't care which operating system you use. And, yes, I am tired of the OS wars!    MAIN FEATURES   I Symmetric multiprocessing capability added--improves multistream workload & performance on multiprocessor systems   M Local Area VAXcluster Systems Phase II--The ability to add CI-based resources E to LAVc's provides more compute resources, more disk storage and more N availability for work groups. Mixed mode clusters can get up to 42 nodes, only 16 of which can be CI based.    N Improved system management features including a new system management utility,2 SYSMAN, and the License Management Facility (LMF)   @ MicroVMS merged into VMS operating system. uVMS is dead! Hooray!  O VMS V5.0 is a major functional enhancement. The new functional additions to VMS B provide a greater capability to build networked computing systems.   The key points are:   " o  Symmetric multiprocessing (SMP)) o  Local Area VAXcluster Systems Phase II , o  SMP systems complement VAXcluster systems$ o  New internationalization features> o  New SYStem MANagement utility to simplify system management+ o  Enhancements for application programmers    Symmetric Multiprocessing   I VMS V5.0 offers full symmetric multiprocessing support for multiprocessor F systems in the VAX 6200 series, VAX 8800 series, and the 83xx systems.O Symmetric multiprocessing is a form of tightly coupled multiprocessing in which M all processors perform operations in parallel, including all VAX access modes L (user, supervisor, executive and kernel.)  For example, processors in an SMPN system can simultaneously execute user-mode programs, execute system services, or even initiate I/O.   H VMS symmetric multiprocessing configurations consist of multiple centralJ processing units executing from a single shared memory address space. ThisI allows users and jobs to share a single copy of VMS as well as frequently J used VAX programs and subroutine libraries.  It also provides simultaneousG shared access to common data in global sections to all processors.  VMS G symmetric multiprocessing balances the execution of all jobs across all 0 available processors on a priority-driven basis.  L SMP support is an integral part of VMS, and is provided transparently to theK user.Since an SMP system is a single system entity, it is configured into a 0 network and VAXcluster system as a single node.   H VMS asymmetric multiprocessing (ASMP) has been replaced by the much moreL comprehensive SMP capabilities.  In addition, the VAX-11/782 (which does notK have a symmetric hardware configuration) will not be supported in VMS V5.0.     & Local Area VAXcluster Systems Phase II  M Local Area VAXcluster systems Phase II allows the addition of CI resources to M an Ethernet-based VAXcluster system.  The resulting configuration is termed a N mixed interconnect VAXcluster system and includes CI-based VAXcluster systems,I Local Area VAXcluster systems and mixed interconnect VAXcluster systems.    N In a mixed interconnect configuration, the VAX systems, which are connected toL the CI bus and HSC series controllers, perform the functions of an LAVc bootN node. Any of the CI-connect VAX systems may service boot and I/O requests fromH the satellite systems.  Access to HSC-based disks from satellite systemsI provides MicroVAX systems with volume shadowing for higher availability.    M A Local Area VAXcluster or mixed interconnect VAXcluster system may contain a J maximum of 42 VAX nodes, with the total number of CI-based VAX systems not9 exceeding 16.  Configuration rules are not yet available.     ( NEW VAXcluster SOFTWARE LICENSING POLICY  D This really does not change anything, mearly clears up some existing inconsistancies in the policy.  K The VAXcluster functionality will now be enabled with a VAXcluster Software O V5.0 license.  Both a VMS and a VAXcluster Software license will be required on G each node in any Local Area VAXcluster Phase II configuration.  This is L consistent with the licensing policy for all previous versions of Local Area VAXcluster software.    K Existing VAXcluster and Local Area VAXcluster customers will be granted the / VAXcluster Software V5.0 license at no charge.      # IMPROVED SYStem MANagement FEATURES   F The SYStem MANagement (SYSMAN) utility centralizes the management of aM VAXcluster system.  Rather than logging in to different nodes and repeating a K set of management tasks, SYSMAN allows customers to define their management O environment as the entire VAXcluster system or any subset of VAX systems within N that VAXcluster system.  Prior to VMS V5.0, a command to define a logical nameN had to be issued once per VAX node in a VAXcluster system.  With VMS V5.0, theO command need only be issued once per VAXcluster system.  From the point of view I of a system manager, the VAXcluster system now functions much more like a J single system. Take my word fo it, this is GREAT! SYSMAN also implement anM object oriented approach to system startup. It is much cleaner and eliminates * most modifications to the SYSTARTUP file.   ! License Management Facility (LMF)   G At the moment, this looks like a nice tool for keeping track of layered I products and handling licensing of products on a cluster, but it contains G the ability to (should DEC so desire) make the manipulation of software H on multiple systems a real pain. It has a plethora of options and hooks.J The basic system is cleverly thought out and should not cause any problems& in moving software to a backup system.  K LMF is a system management tool that allows the system manager to register, # manage and track software licenses.   I The LMF supports new types of software licensing and prepares the way for ? software and documentation consolidated distribution on CDROM.    F Other new features added to simplify system management, in addition to SYSMAN and LMF include:    BACKUP  H Finally an attempt to provide something that looks like tape management!' It ain't perfect, but its a real start.   J It provides checks to  prevent accidental initialization of input disk. ItJ allows multiple operations per stand-alone backup. Passwords are no longerL output in BACKUP save set listings. It provides tape label processing (which may be bypassed).    AUTOGEN Feedback Option   H Allows user workload to determine recommended values for most memory andH page/swap file parameters. VMS continuously maintains usage information;K AUTOGEN snapshots the data to determine recommended values. It looks really M good. With a system that has adequate memory, swapfiles may simply disappear!   J AUTOGEN should be used after a typical workload has been run. I try to run it about once a week.    BATCH/PRINT Enhancements  O The whole scheme of the system has been reworked to allow for easier management O of queues and MUCH improved response. Lexical access to the system is availableE% and ACLs may now be placed on queues.3  F New features important for system and application programmers include:   DEBUG:  J The ability to dynamically reformat register displays, several improvementG to bring MACRO debug to a level similar to that of other languages, and4 support for SMP.   Screen Management (SMG)   O This area has had lots of improvements! Some of the problems discussed at greatrL length on this list have been worked on (and maybe even fixed). There is nowJ support for many usage modes, including block mode (VT3xx SETUP), verticalI (pull-down) menus and horizontal (strip) menus, provision for up to eighthH programmer-defined renditions, and (in my opinion most importantly) SMG$N Subprocess Support, including both the ability to control subprocesses and I/OK via virtual displays; and a method to have several concurrent subprocesses,y each with its own display   2 Parallel Processing Library (PPL) Run-Time Library  L Routines that allow users to implement parallel algorithms in any language.   : MERGE OF MicroVMS AND VMS INTO A SINGLE STYLE OF PACKAGING  M MicroVMS was initially created due to the limitations of system disk size andlN distribution media; these limitations have been removed.  The MicroVMS name isO no longer being used. MicroVMS systems with a service contract will receive theoN VMS update when it is distributed. This does not remove the user limits now in% uVMS. It just moves tham to the LMF. m  ! NEW INTERNATIONALIZATION FEATURESm  I V5.0 has many new enhancements of interest to those of you in non-English @ speaking countries. These internationalization features include:  M The Terminal Fallback Utility -- Provides terminal input and output characterrM conversion for multinational character sets.  It is enabled on a per terminaleL basis, and will allow such characters as an o with an umlaut or an e with anJ accent mark to be displayed.  VMS V5.0 will provide character set tables.   H The National Character Set Utility -- Allows implementation of non-ASCIII collating sequences, and provides a facility for implementing conversionslI between character sets from within programs.  The user-defined  collationiO sequences may be used by both the SORT utility and as the primary and secondaryl keys in RMS ISAM files.   M Date and Time Formatting -- Allows for specification of date and time formatsyM other than the standard VMS format, and specification of non-English formats.uL For example, Date and Time Formatting provides the ability of using a format! such as:  Mardi, le 6 Mars 1988. 6     IMPACT TO EXISTING CUSTOMERS  L All non-privileged applications that ran on any previous release of VMS will
 run on V5.0. c  O In most cases, changes in VMS V5.0 will have a minor impact on privileged code. I Some privileged programs will have to be re-assembled, and all privilegedPN programs will have to be relinked. After assembly and linking, most privileged programs will run on V5.0. M   Exceptions to that rule:  E Programs which use specialized data structures formerly in the systemoN executive.  These programs will have to be modified to use a pointer to accessM the data structure.  This change is simple and requires very little new code.a, Very few programs use these data structures.  J For multiprocessor systems only:  code that synchronizes via the InterruptM Priority Level (IPL) must be modified.  The changes are described in the "VMSoI Device Support Manual."  The most common use of IPL synchronization is innJ device drivers.  (Note:  device drivers will continue to run, without code# changes, on uniprocessor systems.)    K For multiprocessor systems only:  applications that use process priority toiM provide synchronization to shared data in global sections must be modified toI4 use a synchronization technique to call new macros.   F A rolling upgrade from VMS V4.7 to VMS V5.0 is supported in a CI-basedJ VAXcluster system.  This allows you to work with V5.0 before upgrading the entire cluster.    PERFORMANCEu  K The overall system performance for most multistream applications running ont% multiprocessor systems will improve.    B V5.0 does require approximately 1/4 MB more additional memory (500  additional pages) than VMS V4.7.    
 DOCUMENTATION   I The VMS Base Documentation set is intended for system managers of smallereD systems or for end users of any system. It replaces the old MicroVMS documentation.  K The VMS Extended Documentation Set provides detailed technical information.h) It is the equivalent of the old VMS kit. i  D Existing MicroVMS customers under contract will receive the VMS BaseN Documentation Set.  Existing VMS customers under contract will receive the VMS Extended Documentation Set.   B Release notes will be included in doc kits for contract customers.