SpyderByte.com: OpenVMS.org dba.OpenVMS.org dcl.OpenVMS.org de.OpenVMS.org fr.OpenVMS.org it.OpenVMS.org
   
Home Contribute News, Jobs, Press Releases, etc. Advertise on OpenVMS.org About/Contact Search News Archives
More Links
  • here
  • TCO_WP_Feb04.pdf
  • straightforward
  • Thoughts on the Alpha->Itanium
  • OpenVMS Consultant
  • Robert Gezelter
  • www.rlgsc.com
  • Server Consolidation - Back to the Future
  • Pitfalls of F$LOCATE and other Functions
  • Logical Names
  • Logical Names
  • Report from the 1st OpenVMS Technical Symposium
  • Logical Names
  • Logical Names
  • Logical Names
  • Printer friendly version
    Share this story

    Navigation
    VMS Audio Network (VAN)
    Featured Articles
    Vendors
    Training
    Golden Eggs
    Golden Eggs x86
    Help for VMS Beginners
    Documentation
    Developer Resources
    Books
    Commercial Software
    Open Source & Freeware
    OpenSource ported to VMS
    Resources
    FAQs/How-to
    Lists/Newsgroups/Forums
    Security Advisories & Info
    OpenVMS Patches

    Forums
     HP ITRC OpenVMS forum
     OpenVMS Hobbyist forums
     Usenet: comp.os.vms

    Mailing Lists
    OpenVMS.org Newsletter
    OpenVMS.org Alerts
    Rdb Managers

    Roadmaps
    OpenVMS Roadmap (2009)
    Itanium Roadmap
    HP Roadmaps (2002)
    BCS Roadmap FAQ (2002)
    Storage Roadmap FAQ (2002)


    OpenVMS.org Info
    OpenVMS.org Admin Staff:
    Ken Farmer, Ian Miller
    About
    Search OpenVMS.org
    News Archives
    Mobile Edition
    Submit News
    Advertising Information

    OpenVMS.org Websites

    Databases running on OpenVMS


    Digital Command Languauge


    French



    German


    Italian



    Latest News

    The OpenVMS Consultant: HPWORLD 2004 -- Noteworthy OpenVMS Technical News
    Posted by Robert Gezelter on Sunday September 05 2004 @ 08:34PM EDT
    Recently returned from HPWORLD 2004 in Chicago, I can report that there is interesting news in the OpenVMS arena. On the technical front, much of the news was expected, with OpenVMS 8.2 for both Alpha and Itanium having entered field test at the end of July, as projected. OpenVMS VAX 8.2 will be a few months later in the cycle, due to scheduling reasons.

    On product line issues, the strong suggestion is that the economics of OpenVMS on Integrity servers, the proper name for the HP IA-64-based systems, will be extremely attractive. In addition, there are strong hints that even more positive information remains to be unveiled.

    The technical improvements on version 8.2, on the 64-bit platforms, provide major enhancements for multiprocessor environments. Ongoing attention to multiprocessor scalability, and the resulting changes, such as the redistribution of spinlock use from IOLOCK8 to dedicated device-specific spinlocks, greatly reduces spinlock contention. Contention for shared spinlocks in high IO activity has often been a limit on multiprocessor scaling.

    Other changes are more visible to a far wider audience. Some of these changes debuted with the 7.3-2 intermediate release, others are totally fresh for 8.2. The new release includes support for the latest generation of Gigabit Ethernet adapters, enhancements to the C/C++ Run Time library, and other internals improvements. In some cases, these changes remove restrictions (e.g. DCL symbols may now contain up to 8192 characters, a substantial increase from the prior limit of 255 characters). The MONITOR program has also been re-written, as opposed to translated from the VAX image.

    For those unsure of image translation technology's viability in migrating applications from Alpha to Itanium, the history of MONITOR is telling. It provides a counter-example to the old saw that "image translation cannot work". Until now, MONITOR on Alpha has been a translated version of the MONITOR image running on the VAX. Millions of OpenVMS Alpha users have used MONITOR on a daily basis, with no awareness that it was a translated image. For more than a decade, successive versions of MONITOR were translated from VAX to Alpha.

    There will also be substantial advances in mass storage management, including:

    • Host-based Mini-Merge
    • Dynamic Volume Expansion
    • Dissimilar Device Support for Volume Shadowing
    • Enhancements to multi-site support in Host-based Volume Shadowing

    Used in concert, these features reduce operational limitations. Combining Host-based volume shadowing, dissimilar device support for volume shadowing, and dynamic volume expansion makes it possible to seamlessly migrate users, without interruption, to larger volumes. There is no need to dismount disks, or otherwise interfere with normal system operation and use. The need to expand or change mass storage can be realized without system shutdowns, a useful feature in 24x7x365 systems.

    In the Business practices arena, there are substantial changes promised with OpenVMS licensing on Integrity. Most significantly, OpenVMS will be licensed on a per-processor basis, with an unlimited number of users. Additionally, software licenses will be packaged on an ensemble basis, with the different ensembles referred to as Operating Environments. The smallest ensemble is the Foundation Operating Environment, which includes:

    • OpenVMS (unlimited user)
    • DECnet (Phase IV and V)
    • TCP/IP Services
    • Motif
    • Secure WWW Server (Apache), and
    • the Internet technologies suite (JAVA, XML, SOAP, NetBeans, etc.)
    Beyond the basic ensemble is the Enterprise Operating Environment, which expands the Foundation Operating Environment with the addition of:
    • RMS Journaling
    • Volume Shadowing
    • DECram
    • OpenVMS Management Station
    • Enterprise Capacity Planner, and
    • Availability Manager
    The third ensemble, the Mission Critical Operating Environment expands the Enterprise Operating Environment with the addition of:
    • OpenVMS Clusters, and
    • Reliable Transaction Router Backend

    A copy of the diagram illustrating which products are included in a presentation on the HP OpenVMS www site here, on Slide 40.

    While the Foundation Operating Environment will be obligatory, the products included in the enhancement ensembles remain available on an individual basis. The pre-defined Enterprise Operating Environment and Mission Critical Operating Environment ensembles merely reduce the paperwork and cost of dealing with common collections of software components. Individual products remain available to enhance an Operating Environment in situations where a basic Operating Environment is missing a needed product. For example, if VMSclusters are needed, they are available as additions to the Foundation or Enterprise Operating Environments without requiring the purchase of the high-end Mission Critical Operating Environment, just as Volume Shadowing is a potential addition to the Foundation Operating Environment.

    The choice of whether to purchase a more embracive Operating Environment, or a basic Operating Environment with additional layered products is an administrative and economic decision. Different customers will come to different conclusions on the appropriate purchase depending on their finances, plans, and organizational politics. Customers will be able to choose an alternative that dramatically reduces the volume of PAKs for their base environments, together with a simplified policy on processor tiers. The simplifications in license administration and cost will improve on all of OpenVMS's impressive advantages.

    These packages and pricing changes, together with OpenVMS's leadership position in Total Cost of Ownership (TCO) bodes well for the future. (see the February 2004 whitepaper by TechWise, available from the OpenVMS WWW Site at TCO_WP_Feb04.pdf).

    The developments in technical and business practices on Integrity servers underscore the fundamental truth about OpenVMS. OpenVMS is an operating system for which processors have been designed, first the VAX and then the Alpha, not a system designed for a particular processor. The assimilation of Itanium, with little fundamental difficulty, underscores this simple truth. The strength of OpenVMS is that the issues in porting to IA-64 from Alpha are, for most applications, straightforward. The business practices instituted by HP are also along the lines I predicted in my response to the initial June 2001 announcement (see Thoughts on the Alpha->Itanium).

    The OpenVMS Consultant welcomes questions from readers about OpenVMS and related technologies. Please submit your questions to the OpenVMS Consultant.


    Biography:

    Robert Gezelter, CDP, Software Consultant, guest lecturer and technical facilitator, has more than 25 years of international consulting experience in private and public sectors. He is a regular guest speaker at technical conferences worldwide such as HPWORLD (formerly DECUS).

    His firm's practice emphasizes in-depth technical expertise in computer architectures, operating systems, networks, security, APIs, and related matters. Mr. Gezelter has worked with OpenVMS since the initial release of VAX/VMS in 1978.

    His clients include small businesses to the Fortune 10, locally, nationally, and internationally on matters spanning the range from individual telephone questions to major projects.

    He can be reached via the web at www.rlgsc.com.


    Additional articles by The OpenVMS Consultant...

    » Server Consolidation - Back to the Future
    » Pitfalls of F$LOCATE and other Functions
    » Logical Names (Part 5)
    » Logical Names (Part 4)
    » Report from the 1st OpenVMS Technical Symposium (Part 1)
    » Logical Names (Part 3)
    » Logical Names (Part 2)
    » Logical Names (Part 1)


    < How to monitor RAM usage and automatically send warning email | Taking stock of Fiorina >



    ADVERTISEMENT:
    Sponsors







    The OpenVMS Consultant
    OpenVMS Consulting


    The Minimum You Need to Know book series
    Books by Roland Hughes


    Alpha and VAX Replacement
    StanQ.com



    Interested in Advertising? Click here...

    Friends of VMS
    Connect (HP User Community):
    Connect Home
    Connect Chapters
    Connect Special Interest Groups

    United Kingdom
    Canada
    Encompasserve/DECUServe
    OpenVMS Hobbyist
    More usergroups...
    Other Sites:
    Aaron's OpenVMS blog
    Alexey Chupahin
    Arne Vajhoej
    DECUS Library Compendium
    DJE Systems
    Dr OpenVMS blog
    Francesco Gennai
    Eight-Cubed blog
    Free OpenVMS Software
    Galen Tackett
    HoffmanLabs
    Hunter Goatley
    Ian Miller
    Itanium Solutions Alliance
    Jeff Cameron
    John Fisher
    Syltrem VMS Page (French)
    Kednos PL/I
    Keith Parris
    Migration Specialties
    Noetic Systems, Inc
    OpenOffice Port to VMS
    OpenVMSPlanet.org
    OpenVMS Rocks
    Preatorian.net
    Retrobeep
    Steven M. Schweda
    SYSMGR Blog
    TMESIS Software
    Trends That Matter
    VAMP (VMS, Apache, MySQL, PHP)
    VIM
    Vaxination
    Visio Cafe (HP Templates)
    VMSresource.org.uk
    XDelta
    Free VMS Accounts:
    Deathrow Public OpenVMS Cluster
    Encompasserve/DECUServe/EISNER
    Polarhome
    Fafner
    Poetry Hacklab
    Marway.Org
    In Memory:
    John Wisniewski Memorial Site
    Terry Shannon Memorial Site


    OpenVMS Rings

    OpenVMS Webring

    Prev

    Random

    Next

    Prev5

    List

    Next5

    OpenVMS Gurus

    Prev

    Random

    Next

    Prev5

    List

    Next5




    Home About & Contact Search Archive Mobile Submit News Sponsorship & Advertising
         Copyright © 2001-2007 SCORSE, LLC
    OpenVMS® is a trademark of HP
    All other trademarks are those of their owners.
        
      SpyderByte.com ;Technical Portals