HP OpenVMS Systems Documentation
OpenVMS Version 7.3
This chapter provides information on the e-Business technologies that are included in the Compaq OpenVMS e-Business Infrastructure Package with OpenVMS Alpha Version 7.3. This package provides key Internet and e-Business software technology that enhances the base OpenVMS Alpha operating system. These technologies are licensed with the OpenVMS Alpha operating system.
The Compaq OpenVMS e-Business Infrastructure Package Version 1.1 contains the following software and accompanying documentation:
Refer to the Compaq OpenVMS e-Business Infrastructure Package Version 1.1 CD-ROM Booklet and the Compaq OpenVMS e-Business Infrastructure Package Version 1.1 Software Product Description, 80.58.00 included in the e-Business package for more detailed information.
For up-to-date information on OpenVMS e-Business technologies, refer to the following web site:
The following sections briefly describe the e-Business software and
provide pointers and web sites for further information. Refer to the
Compaq OpenVMS e-Business Infrastructure Package SPD for
technology descriptions, other software requirements, and licensing
information. The technology on the e-Business CD-ROM has been tested
and qualified with OpenVMS Alpha Version 7.2-1 and later.
2.1 Compaq Secure Web Server for OpenVMS Alpha
Compaq Secure Web Server for OpenVMS Alpha (CSWS) is based on the popular Apache Web Server from the Apache Software Foundation. Building on the source code from the Apache Software Foundation (http://www.apache.org), Compaq OpenVMS engineering has incorporated and fully integrated OpenSSL with mod_ssl, the most popular open-source implementations of SSL.
The product is also available to download from the CSWS web site:
Component Object Model (COM) is a technology from Microsoft that allows
developers to create distributed network objects. Digital Equipment
Corporation and Microsoft jointly developed the COM specification. The
Compaq COM for OpenVMS kit included on the e-Business CD-ROM provides
all the code and documentation you need to install Compaq COM for
OpenVMS on your system and to develop COM applications.
2.3 Compaq Java 2 SDK, Standard Edition, for OpenVMS Alpha
The Java Software Development Kit (SDK) provides an environment in which to develop and deploy Java applications on OpenVMS Alpha. Java applications can be written once and run on any operating system that implements the Java run-time environment, which consists primarily of the Java Virtual Machine (JVM).
The Java 2 SDK, Standard Edition, for OpenVMS Alpha kit is included on the e-Business CD-ROM, or you can download this kit from the Compaq Java home page at the following web address:
The Compaq Fast VM for Java 2 is new Just-In-Time (JIT) compiler technology designed to provide optimal Java run-time performance on OpenVMS Alpha systems. The Fast VM for Java 2 offers significant performance advantages over the Classic JIT provided with the Compaq Java 2 SDK, Standard Edition.
The Fast VM for OpenVMS Alpha kit is included on the e-Business CD-ROM, or you can also download this kit from the Compaq Java home page at the following web address:
The following components are provided on the e-Business CD-ROM using open source software from the Apache Software Foundation:
This technology provides applications the ability to parse, generate,
manipulate, validate, and transform Extensible Markup Language (XML)
documents and data.
2.6 Attunity Connect "On Platform" Package
Attunity Connect is object-oriented middleware that facilitates the development of applications that access, integrate, and update data from multiple, heterogeneous sources across a wide range of operating system platforms. With Attunity Connect, you can extend the life of your existing data and applications and preserve your significant IT investments.
The e-Business CD-ROM contains the Attunity Connect "On Platform" Package for OpenVMS Alpha. You can also download the Attunity Connect "On Platform" Package from the following OpenVMS web site:
Compaq OpenVMS Enterprise Directory for e-Business combines the best of both industry standard LDAPv3 and X.500 capabilities, and delivers robust and scalable directory services across intranets, extranets, and the Internet to customers, suppliers and partners. Lightweight Directory Access Protocol (LDAP) support allows access by a myriad of LDAP-based clients, user agents, and applications. The X.500 support brings high performance, resilience, advanced access controls, and easy replication across the enterprise.
For further information, refer to the Compaq OpenVMS Enterprise
Directory for e-Business Software Product Description (SPD
40.77.xx) included on the e-Business CD-ROM in the Enterprise
Directory Services documentation directory.
2.8 Reliable Transaction Router (RTR)
Reliable Transaction Router (RTR) is fault tolerant transactional messaging middleware used to implement large, distributed applications using client/server technology. Reliable Transaction Router enables computing enterprises to deploy distributed applications on OpenVMS Alpha and VAX systems.
Refer to the Reliable Transaction Router for OpenVMS Software Product Description (SPD 51.04.xx) included on the e-Business CD-ROM for additional information; or you can access the RTR web site at:
Compaq BridgeWorks is a distributed application development and deployment tool for OpenVMS 3GL applications. BridgeWorks consists of a GUI development tool on the Windows NT desktop, a server manager component on OpenVMS, and extensive online help. BridgeWorks provides developers with an easy means to create distributed applications using OpenVMS as the enterprise server and Windows NT as the departmental server.
For more information on Compaq BridgeWorks, refer to the Compaq OpenVMS e-Business Infrastructure Package Software Product Description.
This chapter provides new features information for all users of the
Compaq OpenVMS Operating System.
3.1 DCL Commands and Lexical Functions
This section describes new and changed DCL commands, qualifiers, and lexical functions for OpenVMS Version 7.3. The following table contains a summary of these changes.
|DCL Command||Documentation Update|
|ANALYZE/IMAGE||A new qualifier, /SELECT, has been added, along with an example.|
|ANALYZE/OBJECT||A new qualifier, /SELECT, has been added, along with an example.|
|ANALYZE/PROCESS||A new qualifier, /[NO]IMAGE_PATH, has been added, along with an example.|
|DELETE||A new qualifier, /BITMAP, has been added to support Write Bitmap.|
|DELETE/INTRUSION||A new qualifier, /NODE, has been added, along with an example, to support Cluster-wide Intrusion.|
|DIRECTORY||A new qualifier, /CACHING_ATTRIBUTE, has been added to support Extended File Cache (XFC).|
A new qualifier, /POLICY, has been added to support Write Bitmap.
A new qualifier, /FORCE_REMOVAL, has been added to support Volume Shadowing.
|DUMP||A new qualifier, /PROCESS, has been added.|
The INITIALIZE description has been updated to include information
about Extended File Cache (XFC).
A new qualifier, /SHADOW, has been added to support Volume Shadowing.
The MOUNT command has been moved to the OpenVMS DCL Dictionary from the
OpenVMS System Management Utilities Reference Manual.
The MOUNT description has been updated to include information about Extended File Cache (XFC).
A new qualifier, /POLICY, has been added to support Write Bitmap.
A new keyword, SERVER, has been added under the LOGFAILURE, LOGIN, and
New text has been added to the /NEW_LOG qualifier.
|SET CACHE/RESET||This new DCL command has been added to support Extended File Cache (XFC).|
|SET DEVICE||The following new qualifiers have been added to support Volume Shadowing: /FORCE_REMOVAL, /MEMBER_TIMEOUT, /MVTIMEOUT, /READ_COST, /SITE, /COPY_SOURCE, /ABORT_VIRTUAL_UNIT.|
|SET DISPLAY||The logical, DECW$SETDISPLAY_DEFAULT_TRANSPORT, has been added to this command.|
|SET FILE||Two new qualifiers, /SHARE and /CACHING_ATTRIBUTE, have been added. The /CACHING_ATTRIBUTE qualifier supports Extended File Cache (XFC).|
|SET PROCESS||The functionality of the qualifier, /[NO]DUMP, has been extended to include other processes. The /DUMP qualifier also has a new option, NOW, to initiate an immediate dump of another process.|
|SET RMS_DEFAULT||Two new qualifiers, /CONTENTION_POLICY and /QUERY_LOCK have been added, and the examples have been updated.|
|SET SERVER||Added support for the Registry, including new qualifiers and examples.|
A new qualifier, /[NO]WRITETHROUGH, has been added to support Extended
File Cache (XFC).
The /HIGHWATER qualifier is valid for Files-11 On-Disk Structure Level 5 disks.
|SHOW CPU||The following new qualifiers have been added: /EXACT, /HIGHLIGHT, /OUTPUT, /PAGE, /SEARCH, and /WRAP.|
A new qualifier, /BITMAP, has been added to support Write Bitmap, along
The /FULL qualifier now displays the worldwide identifier (WWID) for Fibre Channel tape devices.
|SHOW INTRUSION||A new qualifier, /NODE, has been added, along with an example, to support Cluster-wide Intrusion.|
|SHOW LICENSE||The qualifier, /CHARGE_TABLE, has been added as a synonym for the /UNIT_REQUIREMENTS qualifier.|
The /CACHE qualifier and examples have been updated for Extended File
The /FILES and /FULL qualifiers and examples have been updated for Large Page Files.
|SHOW RMS_DEFAULT||The example has been updated.|
|SHOW SERVER||This command has been added in support of the Registry.|
|UNLOCK||This command is now obsolete. Use the SET FILE/UNLOCK command.|
|DCL Lexical||Documentation Update|
|F$GETDVI||The item codes, MT3_DENSITY, MT3_SUPPORTED, and WWID have been added, and the MOUNTCNT item code has been updated.|
|F$GETQUI||The JOB_STATUS item code list has been updated.|
|F$GETJPI||The MULTITHREAD item code has been added.|
|F$GETSYI||The MULTITHREAD and DECNET_VERSION items have been added.|
As of Version 7.3, online help now includes all the OpenVMS utility routines that are described in OpenVMS Utility Routines Manual, including the following:
For OpenVMS Version 7.3, several online help topics have been renamed, as follows:
|Old Topic Name||New Topic Name|
The following new commands and qualifiers have been added to the Multipurpose Internet Mail Extension (MIME) utility:
|ADD/BINARY||Sets the Content-Type to application/octet-stream and Content-Transfer-Encoding to Base64. This format can be used to represent an arbitrary binary data stream.|
|SHOW option||Displays information about the MIME environment. Possible options are CONTENT_TYPE, FILE_TYPES, and VERSION.|
For more information about the MIME utility commands and qualifiers,
refer to the OpenVMS User's Manual.
3.4 WWPPS Utility (Alpha)
The World-Wide PostScript Printing Subsystem (WWPPS) is a utility that allows you to print a PostScript file with various language characters on any PostScript printer. By embedding font data within the PostScript printable file, you can print the language characters even if the printer does not have the local language character fonts.
For detailed instructions about using the WWPPS utility, refer to the OpenVMS User's Manual.
For more information about the installation and administration of the WWPPS utility, refer to the OpenVMS System Manager's Manual.
This chapter provides information about new features, changes, and
enhancements for system managers.
4.1 OpenVMS Support for New AlphaServer GS Series Systems
OpenVMS Alpha Version 7.3 provides support for Compaq's AlphaServer GS80, GS160 and GS320 systems, which was introduced in OpenVMS Version 7.2-1H1, and includes:
Hard partitioning is a physical separation of computing resources by hardware-enforced access barriers. It is impossible to read or write across a hard partition boundary. There is no resource sharing between hard partitions.
Soft partitioning is a separation of computing resources by software-controlled access barriers. Read and write access across a soft partition boundary is controlled by the operating system. OpenVMS Galaxy is an implementation of soft partitioning.
The way customers choose to partition their systems depends on their
computing environments and application requirements. For more
information about using hard partitions and OpenVMS Galaxy, refer to
the OpenVMS Alpha Partitioning and Galaxy Guide.
4.1.2 OpenVMS Resource Affinity Domain (RAD) Support for Applications
OpenVMS Alpha Version 7.3 provides non-uniform memory awareness (NUMA) in OpenVMS memory management and process scheduling, which was introduced in OpenVMS Version 7.2-1H1. This capability provides application support for resource affinity domains (RADs), to ensure that applications running on a single instance of OpenVMS on multiple quad building blocks (QBBs) can execute as efficiently as possible in a NUMA environment. A RAD is a set of hardware components (CPU, memory, IO) with common access characteristics, and corresponds to a QBB in an AlphaServer GS160 or GS320 system.
For more information about using the OpenVMS RAD support for
application features, refer to the OpenVMS Alpha Partitioning and Galaxy Guide.
4.1.3 OpenVMS Support for CPU Online Replace
With OpenVMS Alpha Version 7.3, you can replace secondary CPUs on a running system without rebooting, which provides increased system maintainability and serviceability. This feature is supported only on AlphaServer GS160/320 systems. Note that replacing the primary CPU requires rebooting.
To use this feature, you must first download console firmware Version 5.9B from the following location:
After you upgrade the console with the latest firmware, you can then use the following DCL commands to replace a CPU without rebooting:
$ STOP/CPU n
$ SET CPU/POWER=OFF n
$ SET CPU/POWER=ON n
OpenVMS automatically adds the CPU to the active set of processors.
Note that the Galaxy Configuration Utility (GCU) also supports this
4.2 Automatic Setting of Daylight Savings Time
System parameter AUTO_DLIGHT_SAV controls whether OpenVMS will automatically change system time to and from Daylight Savings Time when appropriate. A value of 1 tells OpenVMS to automatically make the change. The default is 0 (off). This is a static parameter.
However, if you have a time service (such as DTSS), that time service continues to control time changes, and OpenVMS does not interfere. Do not enable automatic daylight savings time if you have another time service.
For more information, refer to the OpenVMS System Manager's Manual.
4.3 Class Scheduler for CPU Scheduling
With OpenVMS Version 7.3, there is a new SYSMAN-based interface for class scheduling. This new class scheduler, implemented on both VAX and Alpha systems, gives you the ability to designate the amount of CPU time that a system's users may receive by placing the users into scheduling classes. Each class is assigned a percentage of the overall system's CPU time. As the system runs, the combined set of users in a class are limited to the percentage of CPU execution time allocated to their class. The users may get some additional CPU time if /windfall is enabled for their scheduling class. Enabling the /windfall allows the system to give a small amount of CPU time to a scheduling class when a CPU is idle and the scheduling class' allotted time has been depleted.
To invoke the class scheduler, you use the SYSMAN interface. SYSMAN allows you to create, delete, modify, suspend, resume, and display scheduling classes. Table 4-1 shows the SYSMAN command, CLASS_SCHEDULE, and its sub-commands.
|ADD||Creates a new scheduling class|
|DELETE||Deletes a scheduling class|
|MODIFY||Modifies the characteristics of a scheduling class|
|SHOW||Shows the characteristics of a scheduling class|
|SUSPEND||Suspends temporarily a scheduling class|
|RESUME||Resumes a scheduling class|
By implementing the class scheduler using the SYSMAN interface, you create a permanent database that allows OpenVMS to class schedule processes automatically after a system has been booted and rebooted. This database resides on the system disk in SYS$SYSTEM:VMS$CLASS_SCHEDULE.DATA. SYSMAN creates this file as an RMS indexed file when the first scheduling class is created by the SYSMAN command, CLASS_SCHEDULE ADD.
In a cluster environment, SYSMAN creates this database file in the SYS$COMMON root of the [SYSEXE] directory. As a result, the database file is shared among all cluster members. By using SYSMAN's SET ENVIRONMENT command, you can define scheduling classes either on a cluster-wide or per-node basis.
If desired, a system manager (or application manager) uses the permanent class scheduler to place a process into a scheduling class at process creation time. When a new process is created, Loginout determines whether this process belongs to a scheduling class. Given process information from the SYSUAF file, Loginout then class schedules the process if Loginout determines that the process belongs to a scheduling class.
By using the SYSMAN utility to perform class scheduling operations instead of $SCHED system service, you gain the following benefits:
For more detailed information, refer to the following manuals:
OpenVMS Programming Concepts Manual, Volume I
OpenVMS DCL Dictionary: N--Z
OpenVMS System Services Reference Manual: A--GETUAI