1 V731_Features The following topics summarize the new features for OpenVMS Alpha Version 7.3-1. 2 e-Business This topic provides information about the e-Business technologies that are included in the Compaq OpenVMS e-Business Infrastructure Package with OpenVMS Alpha Version 7.3-1. 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 contains the following software and accompanying documentation: o Attunity Connect "On Platform" Package o Compaq BridgeWorks o COM for OpenVMS o Compaq Enterprise Directory for e-Business o NetBeans for OpenVMS o Reliable Transaction Router (RTR) o Compaq Secure Web Browser for OpenVMS Alpha (based on Mozilla) o Compaq Secure Web Server for OpenVMS Alpha (based on Apache) o Simple Object Access Protocol (SOAP) Toolkit o Compaq Software Development Kit (SDK) for the OpenVMS Operating System, for the Java[TM] Platform o Compaq XML (Extensible Markup Language) Technology Refer to the Compaq OpenVMS e-Business Infrastructure Package CD-ROM Booklet and the Compaq OpenVMS e-Business Infrastructure Package Software Product Description, 80.58.xx 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: http://www.openvms.compaq.com/ebusiness/ The following topics 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-2 and later. 3 Attunity_Connect 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: http://www.openvms.compaq.com/openvms/products/ips/attunity/ 3 Bridgeworks Compaq BridgeWorks is an automated component creation tool that produces ready-to-build, distributable components from your existing OpenVMS applications. By creating standard reusable components, you extend the reach of your OpenVMS applications so that they can serve many of today's Web- and desktop-based clients. Compaq BridgeWorks provides a quick and reliable way to integrate OpenVMS applications on Alpha or VAX systems with the world of components and distributed objects. Using Compaq BridgeWorks, you can readily reuse your applications with some of the latest technologies, making them accessible from the desktops and the Web browsers of users while maintaining the high availability of the OpenVMS operating system. For more information about Compaq BridgeWorks, refer to the Compaq OpenVMS e-Business Infrastructure Package Software Product Description, or go to the Compaq BridgeWorks Web site: http://www.openvms.compaq.com/commercial/bridgeworks/ 3 COM 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. COM was first released as NetOLE (Network OLE), renamed DCOM (Distributed COM), and then renamed COM for OpenVMS. OpenVMS Version 7.3-1 includes COM for OpenVMS Version 1.2. This version of COM has upgraded the source base to Windows NT 4.0 Service Pack 5. Previous versions of COM for OpenVMS were based on SP3. COM Version 1.2 for OpenVMS has removed all C compiler requirements for building applications, and provides the ability to run components in DLL surrogate processes. COM Version 1.2 has also fixed several problems found in COM Version 1.1-B. For more detailed information, refer to the COM, Registry, and Events for OpenVMS Developer's Guide. 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. This product is also available to download from the following Web site: http://www.openvms.compaq.com/openvms/products/dcom/ 3 Enterprise_Directory 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. This latest release includes support for SSL/TLS between clients and directory servers, Selective Shadowing of data to consumer directories, and a new Java based Management GUI. For further information, refer to the Compaq OpenVMS Enterprise Directory for e-Business Software Product Description (SPD 81.03.01) included on the e-Business CD-ROM in the Enterprise Directory Services documentation directory. This product is also available to download from the following Web site: http://www.openvms.compaq.com/commercial/edir/ 3 NetBeans_for_OpenVMS NetBeans provides an open-source, modular, and integrated development environment (IDE) for Java and JavaBeans development implemented in pure Java[TM]. The popularity of NetBeans is a result of its versatility, extensible architecture, and relative ease of use. NetBeans for OpenVMS is included on the e-Business CD-ROM. This product is also available to download from the following Web site: http://www.openvms.compaq.com/openvms/products/ips/netbeans/ 3 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: http://www.compaq.com/rtr/ 3 Secure_Web_Browser Compaq Secure Web Browser (CSWB) is the officially supported Web browser for OpenVMS Alpha, based on the Mozilla Milestone 1.0 Release Candidate 2. The Mozilla open-source project (http://mozilla.org/) was started in 1998 by Netscape Communications Corporation. The Mozilla Web Browser is designed for standards compliance, performance and portability. Mozilla uses the same code base as Netscape 6.x. CSWB includes support for the following features: o HyperText Markup Language (HTML 4.01) o Cascading Style Sheets (CSS1/2) o Document Object Model (DOM1/2) o eXtensible Markup Language (XML) o Resource Definition Framework (RDF) o Secure Socket Layer (SSL) o JavaScript o Java For more information about CSWB, refer to the Compaq Secure Web Browser for OpenVMS Alpha Installation Guide and Release Notes. This product is also available to download from the CSWB Web site: http://www.openvms.compaq.com/openvms/products/ips/cswb/cswb.html 3 Secure_Web_Server 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. Compaq Secure Web Server for OpenVMS Alpha Version 1.2 is supplied by Compaq Computer Corporation under the terms of the open source license from the Apache Software Foundation, and is based on the Version 1.3.20 release from the Apache Software Foundation. New features in Version 1.2 include two new modules, mod_proxy and mod_rewrite, and support for clusterwide shared memory on OpenVMS Galaxy system clusters. Version 1.2 also includes a new optional kit, CSWS_PHP. 3 SOAP The Simple Object Access Protocol (SOAP) Toolkit provides a simple, lightweight mechanism for exchanging structured and typed information between peers in a decentralized, distributed environment. SOAP is an XML-based protocol that consists of three parts: an envelope that defines a framework for describing the contents of a message and how to process it, a set of encoding rules for expressing application-defined datatypes, and a convention for representing remote procedure calls and responses. SOAP defines a simple mechanism for expressing application semantics that allows SOAP to be used in a wide variety of systems. SOAP is included on the e-Business CD-ROM. This product is also available to download from the following Web site: http://www.openvms.compaq.com/openvms/products/ips/soap/ 3 Java_SDK The Compaq 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 Compaq SDK now includes the Compaq Fast VM, a new Just-In- Time (JIT) compiler technology designed to provide optimal Java run-time performance on OpenVMS Alpha systems. Fast VM offers significant performance advantages over the Classic JIT provided with the Compaq Software Development Kit (SDK). The Compaq Software Development Kit (SDK) for the OpenVMS System, for the Java[TM] Platform 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: http://www.compaq.com/java/download/index.html 3 XML The following components are provided on the e-Business CD-ROM using open source software from the Apache Software Foundation: o XML parsers in Java and C++ o XSLT style sheet processors in Java and C++ This technology provides applications the ability to parse, generate, manipulate, validate, and transform Extensible Markup Language (XML) documents and data. This product is also available to download from the following Web site: http://www.openvms.compaq.com/openvms/products/ips/xml/ 2 User This topic describes new features of interest to OpenVMS users. 3 Documentation In an effort to provide timely updates for our customers, OpenVMS Documentation will post new, supplemental, and updated information to all OpenVMS product documentation sets on the World Wide Web. We encourage customers to check the OpenVMS Documentation web site for changes to the OpenVMS and layered product manuals, as well as pertinent papers and other documents of interest to our customers. Documents posted on the site will be clearly marked and will include the revision date. Our Web site is located at the following URL: http://www.openvms.compaq.com/doc The following new manuals are now included in the OpenVMS documentation set: o COM, Registry, and Events for OpenVMS Developer's Guide o Open Source Security for OpenVMS Alpha, Volume 1: Common Data Security Architecture o Open Source Security for OpenVMS Alpha, Volume 2: Compaq SSL (Secure Sockets Layer) for OpenVMS Alpha o Compaq C Run-Time Library Reference Manual for OpenVMS Systems The following manuals have been archived: o OpenVMS Master Index o OpenVMS Guide to Extended File Specifications The information contained in OpenVMS Guide to Extended File Specifications has been distributed to the following manuals in the OpenVMS documentation set: o OpenVMS User's Manual o Guide to OpenVMS File Applications o OpenVMS System Services Reference Manual o OpenVMS Programming Concepts Manual 3 Oxygen_Graphics OpenVMS Alpha Version 7.3-1 incorporates 2D support for the 3Dlabs Oxygen VX1-AGP4X graphics module. This module can be plugged into an AGP slot on a supported platform (for example, the AlphaServer ES45 Model 1B). To learn which platforms offer AGP device support, ask a Compaq customer service representative or refer to the following Web site: http://www.compaq.com/alphaserver/technology/index.html. 2D support of the 3Dlabs Oxygen VX1-PCI graphics module, introduced with OpenVMS Alpha Version 7.3, continues to be supported in OpenVMS Alpha Version 7.3-1. AlphaServer ES45 users with multihead configurations now have the choice of using only VX1-PCI modules or of using one or more VX1-PCI modules in combination with a VX1-AGP module. For details about using the 3Dlabs Oxygen VX1-AGP4X graphics module, refer to the 3Dlabs OXYGEN VX1 PCI and AGP Graphics Controller Installation Guide, order number EK-VX1GC-IG. 3 DCL This section describes new and changed DCL commands, qualifiers, and lexical functions for OpenVMS Version 7.3-1. The following tables summarize these changes. For more information, refer to the OpenVMS DCL Dictionary. DCL Command Documentation Update ANALYZE/PROCESS A restriction note has been added to the /IMAGE_ PATH qualifier. COPY/FTP A new qualifier, /PASSIVE, has been added. CREATE/DIRECTORY The /ALLOCATE qualifier has been updated to include ODS-5 files. DELETE A new qualifier, /IGNORE=INTERLOCK, has been added. INITIALIZE The following tape-density keywords have been added to the /DENSITY qualifier: AIT2, AIT3, AIT4, DLT8000, 89000, SDLT, and SDLT320. INITIALIZE/QUEUE A new qualifier, /RAD, has been added, along with an example. MOUNT The following tape-density keywords have been added to the /DENSITY qualifier: AIT2, AIT3, AIT4, DLT8000, 89000, SDLT, and SDLT320. PURGE A new qualifier, /IGNORE=INTERLOCK, has been added. READ The Description section has been updated with new information about network block count. RECALL/ALL A new parameter has been added, along with a new example. SET AUDIT The /ENABLE qualifier text has been updated, and DECnet-Plus has been added to the CONNECTION keyword list. SET COMMAND A note has been added to the /OBJECT qualifier to describe the use of the CDU$TABLE_SPACE logical name that lets you increase the value of virtual memory. SET CPU The following new qualifiers have been added: /AUTO_START, /FAILOVER, /MIGRATE, /OVERRIDE_ CHECKS, /POWER, /REFRESH, /START SET ENTRY A new qualifier, /RAD, has been added, along with an example. SET MAGTAPE The following tape-density keywords have been added to the /DENSITY qualifier: AIT2, AIT3, AIT4, DLT8000, 89000, SDLT, and SDLT320. SET QUEUE A new qualifier, /RAD, has been added, along with an example. SET SERVER Support for ACME, including new qualifiers, has been added. SET VOLUME The ODS-5 system disk restriction has been removed. SHOW/CPU The following new qualifiers have been added: /CONFIGURE_SET, /POTENTIAL_SET, /STANDBY_SET, /SYSTEM SHOW DEVICES A new qualifier, /SIZE, has been added to display free space in bytes, along with an example. SHOW ENTRY This command has been enhanced to display RAD information. SHOW NETWORK New examples have been added. SHOW This command has been enhanced to display RAD QUEUE/FULL information. SHOW SERVER Support for ACME, including new qualifiers and examples, has been added. SPAWN A note has been added to the /PROCESS qualifier regarding the use of the DCL_CTLFLAGS system parameter. START/CPU A new qualifier, /POWER, has been added. START/QUEUE A new qualifier, /RAD, has been added, along with an example. STOP Two new qualifiers, /EXIT and /IMAGE, have been added. STOP/CPU Two new qualifiers, /MIGRATE and /POWER, have been added. SUBMIT A new qualifier, /RAD, has been added, along with an example. DCL Lexical Documentation Update F$CVTIME The following keywords have been added, along with an example: DAYOFYEAR, HOUROFYEAR, MINUTEOFYEAR, SECONDOFYEAR F$GETDVI Two new item codes, MPDEV_CURRENT_PATH and MULTIPATH, have been added. F$GETJPI The following items have been added: CLASSIFICATION, CURRENT_CAP_MASK, IMAGE_ AUTHPRIV, IMAGE_PERMPRIV, IMAGE_WORKPRIV, INSTALL_RIGHTS, INSTALL_RIGHTS_SIZE, PERMANENT_ CAP_MASK, PERSONA_AUTHPRIV, PERSONA_ID, PERSONA_ PERMPRIV, PERSONA_RIGHTS, PERSONA_RIGHTS_SIZE, PERSONA_WORKPRIV, SCHED_CLASS_NAME, SUBSYSTEM_ RIGHTS, SUBSYSTEM_RIGHTS_SIZE, SYSTEM_RIGHTS_ SIZE F$GETQUI A new example for deleting retained entries from queues has been added. A restriction has been added to the Description section regarding the use of wildcards and DCL queue-related commands. F$GETSYI The following items have been added: ACTIVE_CPU_MASK, AVAIL_CPU_MASK, COMMUNITY_ ID, CPU_AUTOSTART, CPU_FAILOVER, CPUCAP_MASK, GALAXY_ID, GALAXY_MEMBER, GALAXY_PLATFORM, GALAXY_SHMEMSIZE, GLX_FORMATION, GLX_MAX_ MEMBERS, GLX_MBR_MEMBER, GLX_MBR_NAME, GLX_ TERMINATION, HP_ACTIVE_CPU_CNT, HP_ACTIVE_ SP_CNT, HP_CONFIG_SBB_CNT, HP_CONFIG_SP_CNT, MAX_CPUS, PARTITION_ID, POTENTIAL_CPU_MASK, POTENTIALCPU_CNT, POWERED_CPU_MASK, POWEREDCPU_ CNT, PRESENT_CPU_MASK, PRESENTCPU_CNT, PRIMARY_ CPUID, SCSNODE For information on the DCL commands and lexicals related to case sensitivity, hard links, and access dates, see File Service Extensions. 4 RECALL/ALL The RECALL/ALL command now accepts a parameter that allows you to display multiple occurrences of an individual command within the recall buffer. For example: $ RECALL/ALL SHOW 1 show system 4 show users 5 show intrusion 6 show error 7 show time 4 SET_COMMAND/OBJECT You can now use the new logical, CDU$TABLE_SPACE, to increase the value of virtual memory allocated by the SET COMMAND/OBJECT command. Prior to Version 7.3-1, when compiling very large command definition (CLD) files, you may have encountered the following error: %CDU-F-INTNODESPACE, Internal error: node space exhausted The default value of virtual memory allocated by SET COMMAND/OBJECT is 384KB. This value may not be sufficient to process large CLD files. To increase this size, use the CDU$TABLE_SPACE logical name to specify a larger value and reissue the command. For example: $ DEFINE CDU$TABLE_SPACE 2048 $ SET COMMAND/OBJECT MYCLD.CLD $ DIR *.OBJ Directory $1$DKA600:[GUY.CDU] MYCLD.OBJ;1 4 SHOW_DEVICES You can now use the SHOW DEVICES command to display free space in bytes to accommodate large disk sizes. Prior to Version 7.3-1, the SHOW DEVICES command displayed free space only in blocks. Beginning with Version 7.3-1, you can use the SHOW DEVICES/SIZE=BYTES command to display free space in bytes. 3 WWPPS The World-Wide PostScript Printing Subsystem (WWPPS) now supports the new, compulsory standard, codeset GB18030-2000 for simplified Chinese and traditional Chinese. Support for codeset GB18030 is required for all vendors who want to do business in the People's Republic of China (PRC). For more information about WWPPS, refer to the OpenVMS User's Manual. 2 System_Management This topic describes new features of interest to OpenVMS system managers. 3 ACCOUNTING The /WIDE qualifier in the ACCOUNTING utility changes the width of Buffered I/O and Direct I/O fields in a report from 8 to 10 characters. Without the /WIDE qualifier, these fields print asterisks (*****), if the field overflows. For more information, refer to the OpenVMS System Management Utilities Reference Manual. 3 AlphaServer_DS25 OpenVMS Alpha Version 7.3-1 supports the AlphaServer DS25, the newest addition to the AlphaServer DS20 family. With a processor speed of 1 GHz and support for the latest Gigabit Ethernet adaptor architecture, the AlphaServer DS25 provides superior performance in a high-powered computing environment. 4 Gigabit_Ethernet The AlphaServer DS25 supports the 3COM Gigabit Ethernet adaptor (DEGXA) as a LAN device and a cluster interconnect device. This support will be included in future AlphaServers as well. 4 CDRECORD.COM Read and write-once support for CD-R and CD-RW drives is introduced in OpenVMS Alpha Version 7.3-1 on the AlphaServer DS25 system. On these systems, and future AlphaServer systems as well, you can create your own CD-ROMs for distributing or backing up files. To create a CD-ROM, you need a CD-Recordable (CD-R or CD-RW) drive and a blank CD-R disk. CD-R and CD-RW drives use a laser beam to write (or burn) data to a blank CD-R disk. A CD-R disk is "write once." This means you can write data on it one time only. It is not rewritable. The write process creates a CD-ROM in Files-11 format. Any supported CD-ROM reader on a computer running OpenVMS will be able to read the CD-ROMs you create. NOTE You can create a CD-ROM that contains data files, but audio recording is not supported at this time. OpenVMS supports only qualified CD-R and CD-RW drives. For more information on Alpha systems and the drives they support, refer to the appropriate page at the following Web site: http://www.compaq.com/alphaserver/configure.html You cannot use COPY commands to transfer files from a hard drive to a CD-R disk. You use a program called CDRECORD.COM. The sources for CDRECORD.COM are provided on the Open Source Tools for OpenVMS CD-ROM (see Open Source Tools for OpenVMS CD-ROM.) For more detailed information on using CDRECORD.COM, refer to the OpenVMS System Manager's Manual, Volume 1: Essentials. 3 ANALYZE_DISK The /LOCK_VOLUME qualifier in the ANALYZE/DISK_STRUCTURE utility provides a way to prevent file system activity on a volume while you are analyzing that volume with the ANALYZE/DISK_STRUCTURE utility. For more information, refer to the OpenVMS System Management Utilities Reference Manual. 3 ACME The Authentication and Credentials Management Extensions (ACME) subsystem provides authentication and persona-based credential services. Applications can use these services to interact with the user to perform one or more of the following functions: o User authentication o Password change o Persona creation and modification ACME supports standard OpenVMS authentication and external authentication policies; therefore, applications utilize the same mechanisms as used by the system's LOGINOUT and SET PASSWORD components. For general information on the ACME subsystem, refer to OpenVMS Guide to System Security. Information about the ACME subsystem components is located in the following manuals: ACME Component Documentation Location SYS$ACM system OpenVMS System Services Reference Manual and service OpenVMS Programming Concepts Manual ACME_SERVER OpenVMS Guide to System Security process and ACME policy-provider agents SET and SHOW OpenVMS DCL Dictionary SERVER ACME DCL commands 3 BACKUP The BACKUP command /DENSITY qualifier allows you to specify the recording density of an output magnetic tape. The following table shows the new /DENSITY keywords that are supported beginning in OpenVMS Version 7.3-1: Keyword Description AIT1 Sony Advanced Intelligent Tape 1 - Alpha only AIT2 Sony Advanced Intelligent Tape 2 - Alpha only AIT3 Sony Advanced Intelligent Tape 3 - Alpha only AIT4 Sony Advanced Intelligent Tape 4 - Alpha only DLT8000 DLT 8000 - Alpha only 8900 Exabyte 8900 - Alpha only SDLT SuperDLT1 - Alpha only SDLT320 SuperDLT320 - Alpha only Refer to the OpenVMS System Management Utilities Reference Manual for more information. 3 Batch_Job_Support_for_NUMA_RADs This topic describes updates to the OpenVMS batch processing subsystem in support of Resource Affinity Domains (RADs) in a NUMA environment. System managers now have the ability to assign batch queues to a RAD, and users can specify a RAD on which to run a batch job. These new features are restricted for use on batch execution queues and batch jobs. For information about the system services updates to $GETQUI and $SNDJBC, see System Services and NUMA RADs. For information about DCL commands, refer to the OpenVMS DCL Dictionary. 4 Batch_Queue_Level A new qualifier, /RAD, is available for use with the following DCL commands: INITIALIZE/QUEUE, SET/QUEUE, and START/QUEUE. The system manager specifies the RAD number on which to run batch jobs assigned to the queue. The RAD value is validated as a positive integer between 0 and SYI$_RAD_MAX_RADS. The SHOW/QUEUE/FULL command now displays the RAD in its output, and the F$GETQUI lexical function now accepts a new RAD item. 4 Job-Level_RAD_Support The new qualifier /RAD is added for use with the following commands: SUBMIT and SET ENTRY. The user specifies in the qualifier value the RAD number on which the submitted batch job is to execute. The SHOW ENTRY and SHOW QUEUE/FULL commands are enhanced to list the RAD setting on batch jobs. 4 Run-Time_Behavior When you specify a RAD on a batch job, the job controller creates the process with the $CREPRC home_rad argument set to the RAD value on the job. If the RAD specified on the job is invalid on the target system, the job fails to execute and the job controller sends a message to the operator console indicating that a bad RAD was specified. If the bad RAD value matches the RAD setting on the batch queue, the batch queue is stopped and the job remains in the queue. 5 RAD_Modifications_on_Batch_Queues When you change the RAD value on a batch queue, the jobs currently in the batch queue are not dynamically updated with the new RAD value specified on the queue. Any executing jobs will complete processing using the original RAD value. Jobs in the pending, holding, or timed execution state will retain the old RAD value on the job; however, when such a job becomes executable, the job is updated with the new RAD value and runs on the RAD specified on the queue. 3 DECram_Support_for_Galaxy DECram is a disk device driver that enables system managers to create logical disks in memory to improve I/O performance. Data on an in-memory DECram disk can be accessed at a faster rate than data on hardware disks. DECram Version 3.1 runs on OpenVMS Alpha systems, including Galaxy configurations, running OpenVMS Alpha Version 7.2-1H1 or higher. DECram Version 3.1 takes advantage of the advanced capabilities of the newest Alpha systems, such as Galaxy shared memory. Additionally, the change to I/O post processing described in Performance is a significant performance enhancement. Version 3.1 allocates memory across Resource Affinity Domains (RADs). It moves the virtual device addressing from the S1 address space into the S2 address space, allowing for the creation and addressing of devices larger than 2 gigabytes (GBs). You can easily upgrade an Alpha-based system to DECram Version 3.1. With Version 3.1, you can either use the improved new DECram command interface or continue using the familiar SYSMAN commands for creating, initializing, and mounting DECram disks. DECram Version 3.1 disks are created and formatted at the DECRAM> prompt and are initialized with the DCL INITIALIZE (INIT) command. If you are configuring DECram Version 3.1 on OpenVMS Alpha, you can generate a DECram startup procedure to set up the disk and copy any required files to it. Usually, this procedure is called from the system startup procedure SYS$MANAGER:SYSTARTUP_VMS.COM. REQUIREMENT A DECram disk must have 516 bytes of free page list per block (512 bytes) of disk space allocated. DECram Version 3.1 and supporting documentation are included on the Software Products Library and the Online Documentation Library CD-ROMs. 3 Performance DECram for OpenVMS Version 3.1 and Version 2.5, the Mailbox driver, and Volume Shadowing for OpenVMS have been modified to improve performance on multiprocessor systems. A change has been made in OpenVMS Alpha Version 7.3-1 that enables device drivers to specify that I/O post processing be done on the local CPU. DECram, Mailbox driver, and Volume Shadowing have all been modified to use this performance enhancement. The performance gains are greatest for DECram and can be significant for Mailbox driver. For configurations that use Volume Shadowing, if the primary CPU is saturated, such systems will derive modest benefits. Prior to the introduction of this capability, two routines were called to complete an input-output (I/O) operation, IOC$REQCOM and IOC$ALTREQCOM. These routines cause non-fast-path I/O completion to be performed by the primary CPU, thus potentially degrading performance. As of Version 7.3-1, a device driver writer can improve performance by setting a bit in the unit control block (UCB) initialization routine to indicate that I/O postprocessing should be done on the local CPU. This bit is in the UCB$L_STS field and is called UCB$[V,M]_IOPOST_LOCAL. It causes IOC$REQCOM and IOC$ALTREQCOM to queue the IRP to the CPU-specific post processing queue and do a SOFTINT #IPL$_IOPOST, if necessary. NOTE Because of ordering requirements, network drivers should not utilize the IOPOST_LOCAL feature. 3 Fast_Path Prior to OpenVMS Alpha Version 7.3-1, all hardware interrupts took place on the primary CPU. Interrupts from Fast Path enabled devices would have to be redirected from the primary CPU to a "preferred" CPU. This redirection still involved the primary CPU, and also incurred interprocessor overhead. Furthermore, the algorithm for assigning preferred CPUs to ports did not take into account the performance implications of Resource Affinity Domains (RADs). 4 Distributed_Interrupts Starting with OpenVMS Alpha Version 7.3-1, hardware interrupts for a Fast Path port can be directed to an interrupt CPU, which need not be the primary CPU. Fast Path performance is greatly enhanced when the preferred CPU for a Fast Path port is also the interrupt CPU for that port. In this case, interrupts go directly to the interrupt CPU, eliminating all I/O processing on the primary CPU. This major Fast Path performance enhancement is known as distributed interrupts. You can use SHOW DEVICES/FULL to display the interrupt CPU ID of a Fast Path port. (If a system does not support distributed interrupts, the interrupt CPU is the primary CPU and does not appear in the SHOW DEVICES display.) NOTE Distributed interrupts are supported on AlphaServer DS20, ES40/45, and GS series systems on Fibre Channel, CI, and some SCSI ports. 4 Fast_Path_Code_and_RAD The Fast Path code now takes into account the performance implications of the port's Resource Affinity Domain (RAD) in assigning preferred CPUs and interrupt CPUs. Systems without RADs are treated as systems consisting of one RAD. In some systems that support distributed interrupts, not all CPUs can handle them. An interrupt CPU must either be the primary CPU or must be in the RAD of the port. Although the Fast Path code attempts to take all this into consideration in assigning preferred CPUs, you can use the SET DEVICE/PREFERRED_CPUS command to limit activity to a subset of available CPUs. In a Galaxy configuration, its choice can be overridden by the movement of CPUs in and out of an instance. The default value for PREFERRED_CPUS is NOPREFERRED_CPU, which gives the Fast Path code the greatest latitude in optimizing for performance. For More Information On See Fast Path VMS I/O User's Reference Volume RADs OpenVMS Alpha Partitioning and Galaxy Guide Fibre Channel, Guidelines for OpenVMS Cluster Configurations SCSI, and CI configurations 3 File_Service_Extensions OpenVMS Version 7.2 implemented Extended File Specifications. OpenVMS Version 7.3-1 provides new file system features to further comply with POSIX requirements. These features are supported for ODS-5 volumes, which you can now use as system disks. The result is greater flexibility for OpenVMS Alpha systems to store, manage, and access files created by Windows 95, Windows NT, and UNIX applications. Applications now require less change in porting from these platforms and POSIX compliant environments to OpenVMS Alpha. The file service extensions consist of support for the following: o Additional file times o Access dates o Hard links o Case sensitivity 4 Additional_File_Times To support POSIX-compliant file timestamps on ODS-5 disks, OpenVMS Alpha Version 7.3-1 includes three new file attributes: o ATR$C_ACCDATE - corresponds to POSIX st_atime and reflects the last time a file was accessed. o ATR$C_ATTDATE - corresponds to POSIX st_ctime and reflects the last time a file attribute was modified. o ATR$C_MODDATE - corresponds to POSIX st_mtime and reflects the last time data was modified. Modifications to the file header are recorded as ATTDATE unless the file is actually accessed. The REVDATE ACP/QIO attribute is the most recent of the MODDATE and ATTDATE timestamps. A new ACP/QIO attribute returns the stored REVDATE. When a file is closed, if "norecord" is set, ACCDATE and REVDATE are not altered. Otherwise, if data has been read from the file, closing a file updates the file's access date. If data has been written to the file, closing a file updates the file's modification date. Because access dates must be written out to disk, using these new file attributes impacts performance. The system manager can use the following command to enable or disable access date support and the frequency for changing access dates: $ SET VOLUME/VOLUME_CHARACTERISTICS=([[NO]HARDLINKS,] - _$ [[NO]ACCESS_DATES[=delta-time]]) To limit the performance impact if a file is accessed frequently, you can suppress update of the access time if the change is small. A delta time is used to determine when a new access time is significant. 5 ACP/QIO_Access_Dates Changes in access dates for ACP/QIO depend on whether file dates are being read or maintained. 5 Compaq_C_Run-Time_Library_Dates For information about how to set correct time values, refer to the descriptions of the utime(), stat(), and fstat() functions in the Compaq C Run-Time Library Reference Manual for OpenVMS Systems. 4 DCL_Access_Dates To enable automatic update of access dates on ODS-5 volumes, use the SET VOLUME/VOLUME_CHARACTERISTICS command. For example: $ SET VOLUME/VOLUME_CHARACTERISTICS=ACCESS_DATES= - _$ [delta-time] NODE$COE1 The default value for delta-time is 1 second, chosen to comply with the "seconds since EPOCH" time interface required by POSIX st_atime. A site can choose a larger delta time to reduce overhead if 1-second granularity is not required. Another way to enable automatic update of access dates is to use the INITIALIZE/VOLUME_CHARACTERISTICS=ACCESS_DATES command, as follows: $ INITIALIZE/VOLUME_CHARACTERISTICS=ACCESS_DATES NODE$COE1 $ MOUNT NODE$COE1 To disable access date support on a volume, use the SET VOLUME/VOLUME_CHARACTERISTICS=NOACCESS_DATES command. This command affects only the node on which the command is issued. Other nodes are not affected by the change until the next time the volume is mounted. The DCL commands DIRECTORY or DUMP/HEADER support the new timestamps. Use the following qualifiers: Qualifier Description /DATE=ACCESSED Specifies the last access date. /DATE=ATTRIBUTES Specifies the last attribute modification date. /DATE=DATA_ Specifies the last data modification date. MODIFIED For example, the following command displays the last time data was read from the file: $ DIRECTORY/DATE=ACCESSED 4 Hard_Links A link, or directory entry, is an object in a directory that associates a file name and a version number with a specific file. All links on a volume must represent files on the same volume. With the introduction of hard link support in OpenVMS Alpha Version 7.3-1, OpenVMS now supports three kinds of links on ODS-5 volumes: primary links, aliases, and hard links. OpenVMS Alpha supports files with zero or more links. The first link to a file is referred to as the primary link and is distinguished by having the directory ID and name of the link stored in the file header. Additional links are either aliases or hard links, depending on whether the volume on which the file resides has hard links enabled or disabled. On OpenVMS Alpha systems, you can enable hard links on ODS-5 volumes. On volumes where hard links are not enabled, nonprimary links are aliases. If you choose to enable hard links, you cannot create OpenVMS aliases for files on that volume. A volume can support either hard links or aliases, but not both. The essential difference between hard links and aliases is in the effect of a delete operation. What is usually referred to as deleting a file is more precisely deleting a link to that file. When a link to a file is deleted, the associated file might also be deleted. Whether or not a file is deleted depends on whether the volume on which the file resides has hard links enabled, and on whether a hard link to that file has been created. If hard links are enabled, a file is actually deleted when there are no more links to that file. If hard links are not enabled and you have not created an alias for a file, only one link to that file exists: the primary link. If you create an alias for the file and you then delete the alias, the file still exists because the primary link to that file has not been deleted. The alias is just another name in a directory for this link. Deleting the primary link deletes the file and leaves the alias entries. Attempting to access a file through an alias link to a deleted file results in a "no such file" error. With a primary link and hard links, many links exist. You delete a file when you delete both the primary link and all hard links to that file. An important related consideration is disk quota. On OpenVMS, the size of each file is charged to the file owner's disk quota. If other users create hard links to a file, they are not charged disk quota. The file's owner can delete any links to the file in directories the owner can access, whereas hard links in other users' directories might cause the file to be retained; the owner continues to be charged for its quota. When you enable hard link support on an existing volume, be sure to also use the ANALYZE/DISK/REPAIR command to ensure the proper operation of hard links. OpenVMS supports hard links, or aliases, to directories as well as to files. Most UNIX systems limit hard links to normal files only. The following table shows the commands you use with hard links: To Use Enable hard links INITIALIZE or SET VOLUME Disable hard SET VOLUME device/VOLUME_ links CHARACTERISTICS=NOHARDLINKS Create a hard SET FILE/ENTER link (or an alias for a file) Examples To enable hard links on a mounted Files-11 volume, use the following command: $ SET VOLUME/VOLUME_CHARACTERISTICS=HARDLINKS To initialize an ODS-5 disk with hard links enabled, use the following command: $ INIT/VOLUME_CHARACTERISTICS=HARDLINKS If you have a volume that has hard links enabled, and you want to disable hard links, use the following command: $ SET VOLUME SYS$DISK/VOLUME_CHARACTERISTICS=NOHARDLINKS Note that disabling hard links can result in some strange file behavior. For example, assume that you have disabled hard links, as shown in the preceding example, but you would like to create an alias for your file FOO. First you create an alias for FOO.A called FOO.B, as follows: $ CREATE FOO.A $ SET FILE FOO.A/ENTER=FOO.B Now delete the original file: $ DELETE FOO.A;1 However, if you look for FOO.B on the volume by entering the DIRECTORY command, you receive a "file not found" error because the primary link to that file no longer exists. To fix this problem, or to check the number of hard links to a file, enter the following command: $ ANALYZE/DISK/REPAIR ANALYZE/DISK/REPAIR counts the number of directory entries that reference each file and sets the link count if it is incorrect. Before you create aliases for files on disks that have previously had hard links enabled, be sure to use the ANALYZE/DISK/REPAIR command to set the link count correctly. If you are unsure whether hard links are currently enabled or disabled, use the SHOW DEVICE/FULL command. To report link counts, use DIRECTORY/FULL and DUMP/HEADER. To check the number of links, enter the following command: $ DIRECTORY/LINK 4 Case-Sensitive_File_Operations Traditionally, OpenVMS stored all alphabetic characters in filename specifications as uppercase characters. In addition, file system operations using filename specifications were case insensitive. The introduction of Extended File Specifications enabled system tools and applications to store and display file specifications containing lowercase as well as uppercase alphabetic characters on ODS-5 volumes. Filename specification operations were still case insensitive. With OpenVMS Version 7.3-1 it is now possible for tools and applications to distinguish among filename specifications containing the same alphabetic characters that differ in case only. You can set processes to ignore or notice the case sensitivity of file names. NOTE Enable case sensitivity only when it is known to be supported by the layered product or application you are working with. To match all case variants, use the SET PROCESS/CASE_LOOKUP=BLIND command. If your process is set to CASE_LOOKUP=BLIND and you create more than one file with the same name differing, only in case, DCL treats these files as new versions of the older file and converts them to the same case as the original file. In the following example, DKA500 is an ODS-5 disk. $ SET DEFAULT DKA500:[TEST] $ SET PROCESS /CASE=BLIND /PARSE_STYLE=EXTENDED $ CREATE COEfile.txt $ CREATE COEFILE.TXT $ CREATE CoEfile.TXT $ DIRECTORY Directory DKA500:[TEST] COEfile.txt;3 COEfile.txt;2 COEfile.txt;1 To create a case-sensitive process environment, use the SET PROCESS/CASE=SENSITIVE command. If your process is set to CASE=SENSITIVE and you create more than one file with the same name differing only in case, DCL treats subsequent files as new files and lists them as such. In the following example, DKA500 is an ODS-5 disk. $ SET DEFAULT DKA500:[TEST] $ SET PROCESS /CASE=SENSITIVE /PARSE_STYLE=EXTENDED $ CREATE COEfile.txt $ CREATE COEFILE.TXT $ CREATE CoEfIlE.txt $ DIRECTORY Directory DKA500:[TEST] CoEfIlE.txt;1 COEFILE.TXT;1 COEfile.txt;1 Although an ODS-5 volume preserves the case of a file as it is first entered, file searches are performed in a case-blind manner. Therefore, be careful when you do file comparisons, such as using DCL string functions like .EQS. and F$LOCATE, in a DCL command procedure. If you are using an application that expects case sensitivity, or if you depend on case sensitivity in your environment, set your process to /CASE=SENSITIVE. Be aware that using case sensitivity can create problems, if you do not pay attention to your environment. The default is SET PROCESS /CASE=BLIND /PARSE_STYLE=EXTENDED. RMS uses the process default for case sensitivity as described in Case-Sensitive File Operations. The NAML block was introduced in OpenVMS Alpha Version 7.2 to support long file names. The NAML block has a new field, NAML$V_CASE_LOOKUP, to override the process default case sensitivity. Within NAML$V_CASE_LOOKUP, you can set the following values for case sensitivity: Field Name Description NAML$C_CASE_LOOKUP_BLIND Set by the user to tell RMS to ignore case when creating, deleting, and searching for files. NAML$C_CASE_LOOKUP_SENSITIVE Set by the user to tell RMS to include case as a criteria when creating, deleting, and searching for files. If NAML$V_CASE_LOOKUP is zero, or if a NAML block is not used, the current process setting is used. Directory entries are listed in case-blind order. Case-sensitive operations occur when a new FIB option, FIB$V_CASE_SENSITIVE, is set. ACP/QIO operations with the bit clear are case blind. The process default for case sensitivity does not apply to XQP. The following changes have been made to system services to support case sensitivity: o New values for properties for the $SET_PROCESS_PROPERTIES system service o Changes to the $GETJPI system service The $SET_PROCESS_PROPERTIES system service sets a simple value associated with a service. OpenVMS Alpha Version 7.3-1 supports the following two new property codes for case sensitivity: Property Code Description PPROP$C_CASE_LOOKUP_TEMP The type of case lookup to use. This value is set for only the life of the image. The value reverts to the permanent style on image rundown. Valid values are PPROP$K_CASE_BLIND and PPROP$K_ CASE_SENSITIVE. PPROP$C_CASE_LOOKUP_PERM The type of case lookup to use. This value is set for the life of the process unless the style is set again. The value reverts to the permanent style on image rundown. Valid values are PPROP$K_CASE_BLIND and PPROP$K_ CASE_SENSITIVE. The two new item codes for the $GETJPI system service are: o JPI$_CASE_LOOKUP_TEMP o JPI$_CASE_LOOKUP_PERM These item codes return the values that are set by the $SET_ PROCESS_PROPERTIESW system service, which can be either PPROP$K_ CASE_BLIND or PPROP$K_CASE_SENSITIVE. For more information about the $SET_PROCESS_PROPERTIESW system service, refer to the OpenVMS System Services Reference Manual. The F$GETJPI lexical function has two new item codes, CASE_ LOOKUP_IMAGE and CASE_LOOKUP_PERM, to return information about the case sensitivity of a process. To change the case of a file name, use the RENAME command. You must previously have set your process to CASE=SENSITIVE for RENAME to work properly. For example, to change the case of a file named JANCALENDAR.TXT, enter the following command: $ RENAME JANCALENDAR.TXT JanCalendar.txt This RENAME command renames JANCALENDAR.TXT to JanCalendar.txt. As of OpenVMS Alpha Version 7.3-1, the Compaq C Run-Time Library has greatly improved support for Extended File Specifications, with 250 of the 254 ODS-5 8-bit characters supported, as opposed to only 214 supported previously. Furthermore, file names can now be reported without file types. To enable the new support, you must define one or more C RTL logical names. The settings of these logical names affect the behavior of C applications at run-time. o DECC$EFS_CHARSET With DECC$EFS_CHARSET enabled, UNIX names may contain ODS-5 extended characters. Support includes multiple dots and all ASCII characters in the range 0-255 except , (/), ("), (*) and (?). Unless DECC$FILENAME_UNIX_ONLY is enabled, some characters may be interpreted as OpenVMS characters, depending on the context. These are (:), ([), (<), (^), (;). o DECC$DISABLE_TO_VMS_LOGNAME_TRANSLATION With DECC$DISABLE_TO_VMS_LOGNAME_TRANSLATION enabled, the conversion routine decc$tovms() treats the first element of a UNIX style name as a logical name only if there is a leading slash (/). o DECC$FILENAME_UNIX_NO_VERSION With DECC$FILENAME_UNIX_NO_VERSION enabled, OpenVMS generation numbers are not supported in UNIX style file names. With DECC$FILENAME_UNIX_NO_VERSION disabled, in UNIX style names, generation numbers are reported preceded by a dot. o DECC$FILENAME_UNIX_REPORT With DECC$FILENAME_UNIX_REPORT enabled, all file names are reported in UNIX style unless the caller specifically selects OpenVMS style. This applies to getpwnam(), getpwuid(), argv[0], getname(), and fgetname(). With DECC$FILENAME_UNIX_REPORT disabled, and unless it is specified in the function call, file names are reported in OpenVMS style. o DECC$READDIR_DROPDOTNOTYPE When DECC$READDIR_DROPDOTNOTYPE is enabled and files are being reported in UNIX style, readdir() reports the trailing dot for files with no file type only if the file name contains a dot. With DECC$READDIR_DROPDOTNOTYPE disabled, all files without a file type are reported with a trailing dot. o DECC$RENAME_NO_INHERIT With DECC$RENAME_NO_INHERIT enabled, the new name for the file does not inherit anything from the old name. The new name must be specified completely. With DECC$RENAME_NO_INHERIT disabled, the new name inherits missing components of the file name such as the device, directory, file type and version from the old file in the same way as the DCL RENAME command. Enter the command DEFINE name ENABLE to define each logical name you need. For example: $ DEFINE DECC$EFS_CHARSET ENABLE To disable this logical name, enter: $ DEFINE DECC$EFS_CHARSET DISABLE There are six unsupported ODS-5 characters. o The OpenVMS file system does not support two characters that are not restricted on UNIX, as follows: 042 0x2a (*) Asterisk 063 0x3f (?) Question mark o The C RTL and UNIX cannot handle the following two characters, which are supported by the OpenVMS file system: 000 0x00 (\0) NUL (the string terminating character) 047 0x2f (/) Slash (the directory delimiter) o The C RTL restricts two other characters, as follows: 033 0x21 (!) Exclamation point (interpreted as node delimiter) 034 0x22 (") Double quotation marks (reserved by C RTL) 3 GCM It is now easier for system managers to administer partitioned OpenVMS systems. The Compaq Graphical Configuration Manager (GCM) for OpenVMS is a portable client/server application that provides a visual means of viewing and controlling the configuration of partitioned AlphaServer systems running OpenVMS. A GCM server runs on each OpenVMS partition in one or more AlphaServer systems. The GCM client is a JAVA-based application that can run on any operating system that supports the JAVA runtime environment (JDK V1.2.2 or higher) and a TCP/IP network. From a GCM client, an OpenVMS system manager can establish a secure connection to one or more GCM servers, and perform the following functions: o Display the configuration of partitioned AlphaServer systems o Utilize hot-swap characteristics of the current hardware platform o Execute distributed commands among OpenVMS partitions o Reassign resources among OpenVMS soft partitions o View resource-specific characteristics o Shutdown or reboot one or more partitions o Invoke additional management tools o Create and engage Galaxy configuration models o View online documentation For more detailed information, refer to the OpenVMS Alpha Partitioning and Galaxy Guide. 3 Kerberos Starting with OpenVMS Alpha Version 7.3-1, Kerberos for OpenVMS ships as part of the OpenVMS operating system. Previously, Kerberos shipped as a layered product. Kerberos is a network authentication protocol designed to provide strong authentication for client/server applications by using secret-key cryptography. For more information, refer to the Kerberos Version 1.0 Security Client for OpenVMS Release Notes. 3 New_LANCP_Qualifiers_for_SET_DEVICE_and_SHOW_DEVICES SET DEVICE Command Qualifiers lists the new qualifers for the SET DEVICE command. Table 4-1 SET DEVICE Command Qualifiers Qualifier Meaning /AUTONEGOTIATE Enables or disables the use of auto-negotiation /NOAUTONEGOTIAGE to determine the settings. You need to disable link auto-negotiation only when connected to a switch or device that does not support auto- negotiation. /AUTONEGOTIAGE is the default. /CONTENDER Specifies that the Token Ring is to participate /NOCONTENDER in the Monitor Contention process when it joins the ring. The /NOCONTENDER qualifier directs the device not to challenge the current ring server. /DEVICE_ Allows some device-specific parameters to be SPECIFIC=FUNCTIONadjusted. For the device-specific function commands, see the OpenVMS System Management Utilities Reference Manual: A-L. /JUMBO Enables the use of jumbo frames on a LAN device. /NOJUMBO Only the Gigabit Ethernet NICs support jumbo frames. /NOJUMBO is the default. SHOW DEVICES Command Qualifiers lists the new qualifiers for the SHOW DEVICES command. Table 4-2 SHOW DEVICES Command Qualifiers Qualifier Meaning /INTERNAL_ Displays internal counters. By default, it does COUNTERS not display zero counters. To see all counters, including zero, use the additional qualifier /ZERO. To see debug counters, use the additional qualifier /DEBUG. /TRACE Displays LAN driver trace data. For more information, see the OpenVMS System Management Utilities Reference Manual: A-L. 3 LIBDECOMP.COM Several enhancements have been made to the Library Decompression utility (LIBDECOMP.COM): o In previous releases, LIBDECOMP.COM could perform only one function: expand (decompress) library files. Now the command procedure accepts parameters, which allow you to select any of the following four functions: - EXPAND (default) - Expands (decompresses) libraries that ship in data-reduced (compressed) format. - REDUCE - Reduces (compresses) libraries to the data-reduced format in which they originally shipped. - LIST - Lists all the VAX and Alpha libraries known to the utility. The list displays the size and status (reduced or expanded) of libraries on your system. - HELP - Outputs a brief help display that outlines the parameters and rules for their use. o The selection of libraries that ship in data-reduced format has been changed to maximize the benefits of this utility. Libraries Recognized by LIBDECOMP.COM lists all the libraries known to LIBDECOMP.COM on both VAX and Alpha systems. Table 4-3 Libraries Recognized by LIBDECOMP.COM Library Name Platform Description [SYSHLP] directory; help library files (.HLB) ACLEDT.HLB Both Access Control List Editor help BKM$HELP.HLB Both Backup Manager help DBG$HELP.HLB Both OpenVMS Debugger help DBG$UIHELP.HLB Both OpenVMS Debugger help EDTHELP.HLB Both EDT editor help EVE$HELP.HLB Both EVE editor help EVE$KEYHELP.HLB Both EVE keypad help EXCHNGHLP.HLB Both Exchange utility help HELPLIB.HLB Both DCL help LANCP$HELP.HLB Both LAN Control Program help LATCP$HELP.HLB Both LAT Control Program help MAILHELP.HLB Both Mail utility help NCPHELP.HLB Both Network Control Program help SDA.HLB Both System Dump Analyzer help SHWCLHELP.HLB Both Show Cluster utility help SYSGEN.HLB Both System Generation utility help SYSMANHELP.HLB Both System Management utility help TPUHELP.HLB Both Text Processing Utility help UAFHELP.HLB Both Authorize utility help [SYSLIB] directory; macro library files (.MLB) LANIDEF.MLB Alpha LAN internal driver macros only LIB.MLB Both Operating system macros STARLET.MLB Both Operating system macros SYSBLDMLB.MLB VAX only System build files [SYSLIB] directory; object library files (.OLB) DECCRTL.OLB VAX only Compaq C Run-time Library STARLET.OLB Both System object library and run-time library SYSBLDLIB.OLB VAX only System build files VAXCRTL.OLB Both Compaq C RTL routine name entry points; VAX G_floating double- precision, floating-point entry points VAXCRTLD.OLB Alpha Limited support for VAX D_floating only double-precision, floating-point entry points VAXCRTLDX.OLB Alpha VAX D_floating support; support only for /L_DOUBLE_SIZE=128 compiler qualifier VAXCRTLT.OLB Alpha IEEE T_floating double-precision, only floating-point entry points VAXCRTLTX.OLB Alpha IEEE T_floating support; support only for /L_DOUBLE_SIZE=128 compiler qualifier VAXCRTLX.OLB Alpha G_floating support; support for /L_ only DOUBLE_SIZE=128 compiler qualifier VMS$VOLATILE_ Alpha OpenVMS bugcheck processing codes PRIVATE_ only INTERFACES.OLB [SYSLIB] directory; text library files (.TLB) ERFLIB.TLB Both ANALYZE/ERROR device descriptions LIB_ADA_ Both Ada programmers toolkit of SUBSET.TLB operating system definitions NTA.TLB Both Files to build against NTA facility STARLET_RECENT_ Both Ada programmers toolkit of ADA_SUBSET.TLB operating system definitions STARLETSD.TLB Both STARLET definitions used during layered product installations SYS$LIB_C.TLB Alpha Header files for C language; only derived from LIB SYS$STARLET_C.TLB Both Public header files for Compaq C The following libraries used to be compressed but are no longer shipped in data-reduced format: [SYSHLP]FMG_HELP_FILE__AMERICAN_ENGLISH.HLP [SYSHLP]ANALAUDIT$HELP.HLB [SYSHLP]ANLRMSHLP.HLB [SYSHLP]DISKQUOTA.HLB [SYSHLP]EDFHLP.HLB [SYSHLP]INSTALHLP.HLB [SYSHLP]MNRHELP.HLB [SYSHLP]PATCHHELP.HLB [SYSHLP]PE$HELP.HLB [SYSHLP]PHONEHELP.HLB [SYSHLP]TECO.HLB [SYSHLP]TFF$TFUHELP.HLB [SYSLIB]DECCCURSE.OLB [SYSLIB]DECCRTLG.OLB [SYSLIB]IMAGELIB.OLB [SYSLIB]VAXCCURSE.OLB [SYSLIB]VAXCRTLG.OLB The following libraries were not compressed in the past but now ship in data-reduced format: [SYSHLP]BKM$HELP.HLB [SYSHLP]LANCP$HELP.HLB [SYSLIB]LANIDEF.MLB [SYSLIB]LIB_ADA_SUBSET.TLB [SYSLIB]NTA.TLB [SYSLIB]STARLET_RECENT_ADA_SUBSET.TLB [SYSLIB]SYSBLDLIB.OLB [SYSLIB]SYSBLDMLB.MLB [SYSLIB]VAXCRTLDX.OLB [SYSLIB]VAXCRTLTX.OLB [SYSLIB]VAXCRTLX.OLB For detailed information about using LIBDECOMP.COM and its parameters, refer to the OpenVMS System Manager's Manual. 3 ODS-5 ODS-5 is an optional volume structure that provides support for longer file names with a greater range of legal characters. The legal character set has been extended. Now you can use all the characters from the ISO Latin-1 Multinational character set, except the asterisk (*) and the question mark (?), in file names. Some of the characters from the ISO Latin-1 character set require an escape character to be interpreted properly. For more information, refer to the OpenVMS User's Manual. In previous versions of OpenVMS, ODS-5 volumes could not be used as system disks, and it was recommended that ODS-5 disks be used in homogeneous Alpha clusters only. These restrictions have been removed. OpenVMS Version 7.3-1 supports the use of ODS-5 volumes as system disks and in heterogeneous Alpha clusters. The ODS-5 volume structure supports many new file system features, including hard links and support for case sensitivity. For detailed information about the new file system features, see File Service Extensions. For more information about the system management of ODS-5 disks, refer to the OpenVMS System Manager's Manual, Volume 1: Essentials. 3 OpenVMS_Clusters This section briefly describes the new OpenVMS Cluster features introduced in this release. 4 Performance_Improvements Many modules that are used to send messages or transfer data in an OpenVMS Cluster system have been optimized for speed of execution on the Alpha architecture. Several major modules have been completely rewritten, routine by routine, for performance, correctness, and clarity. The resultant images are significantly smaller, invoke far fewer memory accesses, and generate much more efficient code. The benefits of these changes are: o Reduced system overhead for frequent cluster operations o Improved throughput for cluster locking, messages, and data transfers o Improved throughput for local locking o Reduced hold time for the IOLOCK8 spinlock o Introduction of SYS$CLUSTER_MON.EXE image for automatic additional sanity checks when SYSTEM_CHECKS is enabled Background The cluster communication subsystem consists of several layers: o System application (SYSAP) o System Communications Services (SCS) o Port (SCS port driver, such as PEDRIVER or PNDRIVER) o Device (for example, LAN adapter or CI adapter) The major system applications used by OpenVMS are the disk class driver (DUDRIVER), the MSCP server (MSCP), and the cluster connection manager (part of the SYS$CLUSTER image). SYS$CLUSTER is a shared system application encompassing many subfacilities, notably: o Distributed lock manager o Cluster server process (CSP) messages o Clusterwide logical names messages o Clusterwide process services (CWPS) o Distributed Get Lock Information Service (GETLKI) o Cluster connection manager (CNXMAN) o Distributed write bitmap messages These subfacilities have many subfunctions and services themselves. For example, the distributed lock manager has services for sending $ENQ and $DEQ messages, remastering resource trees, deadlock detection, failover recovery, and others. To send a message: 1. A system application invokes common interfaces to SCS routines that handle messages or data transfer. 2. The SCS layer calls through a common interface to access port- specific routines for the adapters used to reach the remote system or controller. 3. The Port layer calls the specific device driver or adapter interface. Incoming messages reverse this ordering. Within the connection manager, an additional layer to provide sequenced message and block transfer services is available to all of its subfacilities. Revised Components The following subsystems have been totally or incrementally rewritten for speed of execution on Alpha, resulting in performance improvement for all system applications in the cluster: o Entire mainline code for the SCS layer o Entire SCS Fast Path layer (DUdriver is the only client) o SCS port interface layer for: - PEdriver (LAN) - PNdriver (CI) - PMdriver (Shared Memory CI for Galaxy) - Remaining port types o CI interrupt handler o Common I/O interrupt dispatcher o Common subroutines within the local lock manager o Various common system macros The following subsections of SYS$CLUSTER have also been totally rewritten to optimize performance: o Connection manager (common across subcomponents): - Sequenced message send/receive handler (completion of updates begun in OpenVMS Version 7.3) - Block transfer handling - Resource allocation/deallocation/initialization o Distributed lock manager: - ALL send/receive LCKMGR message paths - Streamlined mainline of block transfer remastering o Write bitmap: - Received message dispatching 4 Fibre_Channel For OpenVMS Alpha Version 7.3-1, the Fibre Channel driver has been optimized to reduce I/O lock hold time by 3-6 microseconds per I/O, resulting in significant I/O performance improvements. This optimization, coupled with the coalescing of the I/O completion interrupts, has reduced I/O lock times by as much as 50%, potentially doubling Fibre Channel throughput. Unlike the coalescing of the I/O completion interrupts, the Fibre Channel driver optimizations cannot be backported to earlier versions of OpenVMS Alpha. For more information about Fibre Channel configurations, refer to Guidelines for OpenVMS Cluster Configurations. 4 I/O_Interrupt OpenVMS Alpha Version 7.3-1 contains a major enhancement to the processing of I/O completion interrupts in the host bus adapter. Instead of being sent one at a time, the I/O completion interrupts are grouped together and then transmitted as a group. This major enhancement improves I/O performance in environments with high I/O work loads. Initial tests show a 25% reduction in IOLOCK8 hold time, which translates directly into a 25% increase in I/O throughput performance. This feature will be backported to OpenVMS Alpha Version 7.2-2 and OpenVMS Alpha Version 7.3. For more information about Fibre Channel configurations, refer to Guidelines for OpenVMS Cluster Configurations. 4 MSCP_Disk_Limit OpenVMS Alpha Version 7.3-1 contains a major enhancement to MSCP serving. The previous limit of 512 disks that could be MSCP served by any system in an OpenVMS Cluster system has been raised to 1000. This allows greater flexibility in configuring OpenVMS Cluster storage. A further increase making the supported limit greater than 1000 will be considered for a future release. Note that this increase affects Alpha systems, only. There is no intent to increase the number of disks served by VAX nodes. A VAX node can still be a client of as many disks as are presented in the cluster, within memory resource limits. For more information about MSCP serving, refer to OpenVMS Cluster Systems and Guidelines for OpenVMS Cluster Configurations. 4 MSCP_Multipath_Failover In a multipath SCSI or Fibre Channel configuration, OpenVMS supports failover, from one path to another path, to a device. Establishing multiple paths to a device has the following advantages: o Increases the availability of the device o Provides higher overall performance Prior versions of OpenVMS Alpha supported failover between direct paths. OpenVMS Alpha Version 7.3-1 introduces support for failover between direct-attached and MSCP-served paths to disks in the following OpenVMS Cluster configurations: o Multihost SCSI o Multihost Fibre Channel If all direct paths to a device are broken, the I/O automatically fails over to an MSCP-served path. When the direct paths are restored, the I/O is automatically rerouted from the MSCP-served paths to the direct-attached paths. Use the MPDEV_REMOTE system parameter to enable this capability. For more information about multipath support, including failover to an MSCP-served path, refer to Guidelines for OpenVMS Cluster Configurations. 4 Multipath_Balancing A major enhancement to multipath failover in OpenVMS Alpha Version 7.3-1 for Fibre Channel and SCSI disk and tape devices is automatic path balancing. The path selection of each device is now biased toward the connected path with the fewest devices using it as a current path. In addition to the introduction of automatic, multipath path balancing, the path selection algorithm for multipath failover has been modified to improve performance. For more information, see Section 6.7.8, Path Selection by OpenVMS, in Guidelines for OpenVMS Cluster Configurations. 4 Multipath_Tape_Support Tapes are supported in Fibre Channel configurations as of OpenVMS Alpha Version 7.3. You can attach SCSI tape devices to the Fibre Channel via a Fibre-to-SCSI bridge known as the Modular Data Router (MDR). The MDR is dual ported, allowing two paths into the MDR. For example, if an Alpha system has four KGPSA adapters, there are four distinct paths to a tape drive on the Fibre Channel. An Alpha system with four KGPSA adapters leading to a dual-ported MDR actually has eight different paths to a tape drive. OpenVMS Alpha Version 7.3 did not take advantage of multiple paths. It used only the first path detected during autoconfiguration. The remaining paths were never recognized or made available, even if the first path broke. This single-path model had two limitations: o One KGPSA must handle all the tape activity. o There is no failover capability in the event of a path failure. The first limitation has a workaround that uses the selective storage presentation (SSP) feature of the MDR utility; the second limitation has no workaround at all. OpenVMS Alpha Version 7.3-1 removes both limitations. All possible paths from an Alpha system to a Fibre Channel tape are configured and made available. You can specify a particular path with the DCL command SET DEVICE/SWITCH. In the event of a broken connection, automatic failover takes place. NOTE Multipath failover is supported between tape devices directly connected to the Fibre Channel that are members of a multipath set. If one member of the set fails, another member provides the tape device to the client. However, multipath failover between direct and MSCP-served paths is not supported for tape devices. For more information about tape support in Fibre Channel configurations, refer to Guidelines for OpenVMS Cluster Configurations. 4 SCA_Circuits_and_Ports The following sections explain new functionality available for SCA circuits and ports and new support for SCS dynamic load class. In addition, you can independently enable or disable checksumming on individual PEdriver virtual circuits (VCs). These changes provide a more dynamic connection environment for improving overall performance in an OpenVMS Cluster system. Ability to Set Port and Circuit Priorities OpenVMS Cluster code has always attempted to assign SCS connections automatically to a circuit on the highest performance cluster interconnect. These assignments were based on the interconnect-specific load class value. Automatic circuit selection does not always produce connection assignments that are optimal for a customer's particular performance or availability requirements. Unfortunately, no mechanism has existed to override automatic circuit selection. This problem has been corrected in OpenVMS Version 7.3-1. Beginning with OpenVMS Version 7.3-1, you can exercise direct management control over the circuits chosen for SCS connections. To tune your cluster to your specific performance or availability requirements, now you can override automatic selection of the circuit with the highest load class value. To override automatic circuit selection, use either the SCACP utility or the Availability Manager to assign a management priority value to a specific circuit or SCA port. (A circuit's current priority value is the sum of the local port's management- assigned priority and the management priority value assigned to that circuit.) Connections are assigned to a circuit with the highest priority. If multiple circuits have the highest priority value, then the circuit with the highest load class is selected. A change in a circuit's current priority has one of the following effects: o If a circuit's new priority value is higher than another circuit's current priority, the connection moves to the circuit with the higher current priority. o If a circuit's new priority value is lower than another circuit's current priority, the connection moves to the circuit with the highest current priority. CIRCUIT MANAGEMENT PRIORITY IS VOLATILE Whenever a circuit is closed, its management priority setting is lost. This is because the data structure containing information about a circuit is deallocated each time a circuit is closed. When a circuit is reopened, the structure is initialized with default values. Thus, circuit management priority does not propagate across VC closures. PEdriver Checksumming Prior to OpenVMS Version 7.3-1, checksumming could be enabled or disabled on all of the circuits of a node only. This sometimes resulted in unnecessary use of the CPU for circuits on which the additional robustness of checksumming was not needed. Beginning with OpenVMS Version 7.3-1, you can enable or disable checksumming on individual LAN circuits. This lets you specify the use of checksumming for only those circuits where it is needed, such as circuits between the sites of a disaster-tolerant cluster. Dynamic Load Class Support Prior to OpenVMS Version 7.3-1, the load class of SCS circuits was determined only by the port's hard-coded load class value. As a result, CI or DSSI circuits were chosen over a GigaBit Ethernet circuit. Beginning with OpenVMS Version 7.3-1, PEdriver dynamically updates the load class value of its SCS circuits to reflect the performance of the underlying LAN path or paths currently in use. If the circuits have the same priority, a change in a circuit's load class has one of the following effects: o If a circuit's new load class value is higher than another circuit's current load class, the connection moves to the higher load class circuit. o If a circuit's new load class value is lower than another circuit's load class, the connection moves to the circuit with the highest load class. 3 Registry New features for the OpenVMS Registry include two enhancements to the Registry Control Program (REG$CP) and performance improvement through indexing. 4 Database_Version_Support The Registry Control Program, REG$CP, has been enhanced to support the creation of distinct Registry database versions. The CREATE DATABASE command now accepts a /VERSION qualifier. For OpenVMS Version 7.3-1, a Version 1 or Version 2 database may be specified. By default, CREATE DATABASE creates a Version 2 database. 4 Value_Type_Support In addition to value types of SZ, EXPAND_SZ, MULTI_SZ, and DWORD, the Registry Control Program, REG$CP, has been enhanced to support the BINARY value type when creating or modifying values (/TYPE_CODE=BINARY). When listing values with BINARY value type, the data is displayed in hexidecimal radix. Creating and modifying values has also been enhanced with the addition of the /INPUT qualifer to allow the value data to be read from a file. The input data type is specified with embedded keywords in the file records. These keywords are compatible with those found in an exported database file. The storage data type, as specified by the /TYPE_CODE qualifier, is independent of the input data type. For example, you may specify the value type as SZ (Unicode string) but input the value data in hexidecimal. Combined, these features allow large amounts of raw data to be entered via REG$CP. By contrast, entering the data with the /DATA qualifier and the DWORD data type, while allowing raw data to be input, imposes restrictions on the length of the data. Similarly, entering SZ value types with /DATA, while not imposing a length restriction, does impose a restriction on the type of data that can be input, that is, you can enter only Unicode strings. The command line also restricts the amount of data that can be input with /DATA. The /INPUT qualifier provides a way to overcome these restrictions. 4 New_Registry_Database_Version The performance of the OpenVMS NT Registry has been improved in Version 7.3-1. This was accomplished primarily by indexing the Registry database. This, however, resulted in the need to create a new Registry database version. The Registry server will continue to support the previous database format, Version 1.0; however, to take advantage of the indexing, you must convert the current database to Version 2.0. Converting a Version 1 database to Version 2 is optional. Do not convert the Registry database if you plan to run Registry servers on nodes in a mixed-version cluster, while upgrading your cluster. Registry servers on nodes running versions of OpenVMS prior to Version 7.3-1 would not be able to access a Version 2 database. For further information on converting an OpenVMS Registry database, refer to the COM, Registry, and Events for OpenVMS Developer's Guide. 3 SHOW_CLUSTER The OpenVMS Show Cluster utility (SHOW CLUSTER) is used to monitor nodes in an OpenVMS Cluster and to display information about cluster-specific activity and performance. It has been enhanced to provide additional information about virtual circuits and local ports. CIRCUITS Class New Fields describes the new fields that you can use with the CIRCUITS class to display virtual circuit information. Table 4-4 CIRCUITS Class New Fields Field name Description LD_CLASS The circuit's current capacity rating. MGT_ Priority value assigned to the circuit by management PRIORITY action. PRIORITY Circuit's current priority, which is the sum of the management priorities assigned to the circuit and the associated local port. LOCAL_PORTS Class New Fields describes the new fields that you can use with the LOCAL_PORTS class to display additional local port information. Table 4-5 LOCAL_PORTS Class New Fields Field name Description LP_LD_ Hard-coded capacity value of the port, based on the CLASS megabits per second rate of the interconnect of the port. LP_ Management priority assigned to the port. PRIORITY For more information about the SHOW CLUSTER utility, refer to the OpenVMS System Management Utilities Reference Manual. 3 Spawning The way OpenVMS names spawned subprocesses has been changed to improve performance. DCL_CTLFLAGS is a bitmask used to alter default behavior for certain commands on a systemwide basis. At present, only the low bit of the bitmask is defined. The low bit controls the default process-name assignment for a subprocess created using the SPAWN command or LIB$SPAWN routine. Prior to OpenVMS Version 7.3-1, if no process name was supplied, the system constructed a name by appending _n to the username, where n was the next available non-duplicate integer for any process currently in the system. For example, the first spawned process from user SYSTEM would be called SYSTEM_1, the second, SYSTEM_2, and so on. The next available number was chosen, as soon as a gap was found. A problem with this technique is that determining the next available number is very expensive in terms of performance, because the mechanism attempts to create the process by incrementing names until one is found that is unique. When several subprocesses already exist, the cost of creating the subprocess iteratively becomes even more expensive. When many processes are in the same OpenVMS group, the cost multiplies because process names must be unique throughout the group. Beginning with OpenVMS Version 7.3-1, the default-constructed process name for subprocesses has changed. Instead of incrementally searching for the next unique number, a random number is chosen to append to the username. Therefore, the first processes that are spawned from user SYSTEM might be SYSTEM_ 154, SYSTEM_42, SYSTEM_87, and so on. This procedure results in a very high probability of finding a unique name on the first try, because it is unlikely that the same number is already in use. This greatly reduces the cost of process creation, and applications that rely on spawned subprocesses might see a dramatic performance improvement due to this change. However, some applications might rely on the prior method of assigning subprocess names. The DCL_CTLFLAGS parameter is available to allow you to configure the system as necessary. Bit 0 of DCL_CTLFLAGS selects the behavior for assigning default subprocess names: o If the bit is clear, the new behavior is used. If you do not specify a process name, the system assigns the username with a random number suffix. This is the default setting. o If the bit is set, the prior behavior is used. If you do not specify a process name, the system assigns the username with the next available number. 4 SYSMAN The SYSMAN utility has new qualifiers for the existing RESERVED_ MEMORY ADD and RESERVED_MEMORY MODIFY commands and two new commands, described in New SYSMAN Utility Commands. Table 4-6 New SYSMAN Command Qualifiers Command Qualifier Description RESERVED_ /RAD Specifies the RAD for the reservation MEMORY ADD you want to make in the Reserved Memory Registry data file. RESERVED_ /RAD Modifes an existing RAD in the MEMORY Reserved Memory Registry data file. MODIFY /NEW_RAD Specifies the RAD you want to substitute in the Reserved Memory Registry data file. New SYSMAN Utility Commands describes the new SYSMAN commands in OpenVMS Version 7.3-1. Table 4-7 New SYSMAN Utility Commands Command Description RESERVED_MEMORY The RESERVED_MEMORY ADD command reserves an EXTEND amount of physical memory, referred to as a memory reservation. Use the RESERVED_MEMORY EXTEND command when you want to add memory sections to accommodate more than one resource affinity domain (RAD) for a single memory reservation. It has two qualifiers: o /RAD Specifies one ore more RADs for a memory section. o /NORAD Adds a memory section without specifying a RAD. RESERVED_MEMORY Previews a reservation as it is currently LIST stored in the Reserved Memory Registry data file. If you don't specify a reservation, all current reservations are displayed. 3 New_Sys_Parameters The following sections describe system parameters that are new in OpenVMS Version 7.3-1. 4 DCL_CTLFLAGS The new system parameter DCL_CTLFLAGS allows users to continue to use the previous default behavior for assigning subprocess names on a systemwide basis when processes are spawned. Refer to Spawning for more information. 4 DELPRC_EXIT Use DELPRC_EXIT to control $DELPRC system service options that call exit handlers prior to final cleanup and deletion of a process. The following table describes these options: Option Description 0 Disable the exit handler functionality with $DELPRC. 4 Execute kernel-mode exit handlers. 5 (de- Execute exec- and more privileged-mode exit handlers. fault) 6 Execute supervisor- and more privileged-mode exit handlers. 7 Execute user- and more privileged-mode exit handlers. DELPRC_EXIT is a dynamic parameter. 4 MPDEV_AFB_INTVL MPDEV_AFB_INTVL specifies the automatic failback interval in seconds. The automatic failback interval is the minimum number of seconds that must elapse before the system attempts another failback from an MSCP path to a direct path on the same device. MPDEV_POLLER must be ON to enable automatic failback. You can disable automatic failback without disabling the poller by setting MPDEV_AFB_INTVL to 0. The default is 300 seconds. 4 RMS_SEQFILE_WBH RMS_SEQFILE_WBH can enable the RMS write-behind feature as a system default for any unshared sequential disk file if the file is opened for image I/O with write access specified. The following table describes the possible settings: Setting Description 0 (de- Do not enable write-behind feature. Preserve prior fault) behavior of using write-behind only if the user requests it by setting RAB$V_WBH in RAB$L_ROP. 1 Enable write-behind feature as system default, including the allocation of at least two local buffers. RMS_SEQFILE_WBH is a dynamic parameter. 3 SCACP Beginning with OpenVMS Version 7.3-1, you can use SCACP to manage SCA communications on all OpenVMS Cluster interconnects. These interconnects are in addition to SCA use of LAN devices and LAN paths, which was supported beginning in OpenVMS Version 7.3. 4 Cluster_Ports_and_Circuits SCACP allows you to display port and circuit information for any cluster interconnect. You can also set the management priority field in ports or circuits. This lets you optimize the cluster's choice of circuits and ports used for cluster configuration. 4 New_Commands_and_Qualifiers New SCACP SET and SHOW Commands and Their Qualifiers describes the new SCACP SET and SHOW commands in OpenVMS Version 7.3-1 and lists their qualifiers. Table 4-8 New SCACP SET and SHOW Commands and Their Qualifiers Command Function SET Allows a user to set a management priority value for CIRCUIT the selected circuit or circuits. This command can be used with the following qualifiers: o /EXCLUDE Allows you to exclude a specific circuit to a node. If multiple circuits to the same node exist, you can use the /PORT and /RSTATION qualifiers to uniquely identify the circuit. o /PORT=portname[/RSTATION=n] If multiple circuits to the same node exist, you can use the /PORT and /RSTATION qualifiers to uniquely identify the circuit. You can use the /RSTATION qualifier only in conjunction with the /PORT qualifier for the selected circuit or circuits. o /PRIORITY=n Sets the management priority value for the selected circuits. n can be any value between -127 and +127. SET Allows a user to set a management priority value for PORT the selected port or ports. This command can be used with the following qualifiers: o /EXCLUDE=(portname[,...]) Excludes specific ports from the operation. o /PRIORITY=n Sets the management priority value for the selected ports. n can be any value between -127 and +127. SHOW Shows information about all circuits between this CIRCUIT node and other cluster nodes, including LAN circuit (node- information. This command can be used with the names) following qualifiers: o /EXCLUDE Allows you to exclude a specific circuit to a node. If multiple circuits to the same node exist, you can use the /PORT and /RSTATION qualifiers to uniquely identify the circuit. o /PORT=portname[/RSTATION=n] If multiple circuits to the same node exist, you can use the /PORT and /RSTATION qualifiers to uniquely identify the circuit. You can use the /RSTATION qualifier only in conjunction with the /PORT qualifier. SHOW Displays information about all SCA ports on the node, PORT including the LAN port, PEA0. This command can be used with the following qualifiers: o /EXCLUDE=(portname[,...]) Excludes specific port names from the display. You cannot use wildcards to specify port names. o /OUTPUT=filespec Creates the specified file and directs the output of the command to this file. New SCACP Command Qualifiers describes the new SCACP command qualifiers in OpenVMS Version 7.3-1. Table 4-9 New SCACP Command Qualifiers Command Qualifier Description SET VC /CHECKSUMMING Enables or disables checksum /NOCHECKSUMMING verification on the VC to each (default) specified node. You can use this command alone or in combination with the system parameter NISCS_ PORT_SERV. (Refer to online help for NISCS_POST_SERV for more information.) VC CLOSURE SIDE-EFFECT When you enable or disable checksumming on a circuit, the circuit closes briefly and then reopens using the specified operating mode. This is necessary to ensure that both ends of the circuit are synchronized. SHOW LAN_ /EXCLUDE=(landeviceExcludes.specific LAN devices, DEVICE which you can use wildcards to specify. 3 Ultra3_SCSI_Adapter OpenVMS Alpha Version 7.3-1 supports the KZPEA, an Ultra3 SCSI host adapter that offers a maximum bus speed of 160 MB/s. PKAdriver is the software component that supports KZPEA. The KZPEA is supported for direct-attached storage only. OpenVMS Alpha Version 7.3-1 also provides Fast Path support for the KZPEA. Fast Path support is designed for use in a multiprocessor system. Fast Path automatically redirects I/O from the primary CPU to different CPUs. You can change it either programmatically or by DCL commands. NOTE Support for the KZPEA adapter on OpenVMS Alpha Version 7.2-2 and Version 7.3 is available in remedial kits. Fast Path support is not provided for the KZPEA for OpenVMS Alpha Version 7.2-2 or Version 7.3. For more information about Fast Path support, refer to the OpenVMS I/O User's Reference Manual. 3 DECdtm DECdtm is a distributed transaction manager that coordinates the activity of resource managers used by an application. DECdtm services are embedded in the OpenVMS operating system and fully support distributed databases using a two-phase commit protocol. The DECdtm services provide the technology and features for distributed processing, ensuring both transaction and database integrity across multiple Compaq resource managers. DECdtm V2.0 implements the XA standard interface from the X/Open distributed transaction model. The XA interface provides transaction processing interoperability across OpenVMS Oracle/Rdb, OpenVMS Oracle 8i/9i, RMS Journaling, and ACMS. DECdtm V2.0 can interface with XA compliant transaction managers, such as BEA Tuxedo and Compaq's Reliable Transaction Router (RTR). DECdtm with XA provides: o Distributed transaction coordination between applications and Oracle 9i, Oracle RDB, and RMS databases. o ACMS access to the Oracle 9i databases, in addition to Oracle RDB and RMS. o Transaction and data integrity, allowing for greater transaction interoperability. For More Information On See DECdtm system OpenVMS System Services Reference Manual services Managing OpenVMS System Manager's Manual DECdtm and XA transactions XGCP Utility and OpenVMS System Management Utilities Reference DECdtm/XA Manual Programming with OpenVMS Programming Concepts Manual, Volume II DECdtm and XA 2 Programming This topic describes new features of interest to application and system programmers. 3 Alpha_Processors Each generation of Alpha processors has different characteristics. Applications built to run on one generation of processors continue to run on newer generations. However, newer generations of processors are usually more capable and perform better than previous generations. By rebuilding applications for newer processors, you can take advantage of their new performance-enhancing capabilities and features. A white paper tells image-providers-ISVs or product developers- how they can take advantage of some of the performance-enhancing features of newer Alpha processors. The HTML and PDF versions of the paper are at the following web site: 3 ANALYZE_Usage_Summary The /SHADOW_MEMBER qualifier in the Alpha System Analysis tool ANALYZE Usage Summary specifies which member of a shadow set contains the system dump to be analyzed, or allows the user to determine what system dumps have been written to the member of the shadow set. For more information, refer to the OpenVMS Alpha System Analysis Tools Manual. 3 C_RTL The following sections describe the Compaq C RTL enhancements included in OpenVMS Version 7.3-1. These enhancements provide improved UNIX compatibility and the flexibility of user- controlled feature selections. For more details, refer to the Compaq C Run-Time Library Reference Manual for OpenVMS Systems. 4 Files_Larger_Than_2_Gigabytes Support has been added for compiling applications to use file sizes and offsets that are 2 gigabytes or larger. This is accomplished by allowing file offsets of 64-bit integers. Two new functions have been added: fseeko ftello These are identical to fseek and ftell, but they accept or return values of type off_t, which allows for a 64-bit variant of off_t to be used. Modifications to accommodate a 64-bit file offset have been made to the following existing C RTL functions: fstat ftruncate ftw lseek mmap stat truncate The new 64-bit interfaces can be selected at compile time by defining the _LARGEFILE feature macro: $ CC /DEFINE=_LARGEFILE 4 Enabling_C_RTL_Features_at_Compile/Link_Time The C RTL now provides an extensive list of feature switches that affect an application's behavior. They can be used to enable new behaviors or preserve previous, depreciated behaviors. You can enable or disable these features at run time using DECC$ logical names. For more information, see (crup) and refer to the Compaq C Run-Time Library Reference Manual for OpenVMS Systems. A programmable interface is also available to sense or set feature switches within an application. By using this interface in a function referenced by the global symbol LIB$INITIALIZE, you can enable or disable features before the C RTL is initialized. In many instances, you can enable new behaviors by using feature switches. This will preserve existing behavior as the default. If an application needs to select a different default behavior, a user can then modify the run-time behavior using a logical name. For some applications, some feature-switch settings may be necessary. In this case, they can be set in a way that a logical name cannot override the value. There are four functions provided to do this: int decc$feature_get_index(char *name); char *decc$feature_get_name(int index); int decc$feature_get_value(int index, int mode); int decc$feature_set_value(int index, int mode, int value); 4 Enhanced_Support_for_UNIX_Style_File_Names The Compaq C RTL can be instructed to accept UNIX style file and directory path names that contain the extended ASCII character set supported by OpenVMS Extended File Specifications (EFS) on ODS-5 devices. NOTE This feature is intended for use by applications ported from UNIX systems and not for native OpenVMS applications. To enable this feature, define the DECC$FILENAME_UNIX_ONLY logical name to ENABLE before program execution: $ DEFINE DECC$FILENAME_UNIX_ONLY ENABLE With this feature enabled, all file and path specifications input to the Compaq C RTL are assumed to be UNIX style and therefore can consist of the full, printable ASCII character set (20-7E hexadecimal), with the following exceptions: * (asterisk) ? (quotation mark) / (forward slash) " (double quotation mark) The Compaq C RTL provides any necessary enclosing quotation marks for special characters when presenting the file specification to the OpenVMS file system. OpenVMS file and path specifications that are output by the Compaq C RTL are converted to UNIX style where appropriate, and any special characters quoted by the OpenVMS file system are unquoted before being returned to the Compaq C RTL caller. In addition, the OpenVMS version number field is stripped from the file name on output. For example, assume the following UNIX style path name is input: ./abc.d/data.dat.dat The Compaq C RTL converts it to the following before passing it on to the OpenVMS file system: [.abc^.d]data^.dat.dat The caret (^) character is the EFS quote or escape character. (For more information about escape characters and name and type delimiters, refer to the OpenVMS User's Manual.) When this file name is retrieved, it is output to the Compaq C RTL caller just as it was input, with quoted characters unquoted. Note that, under normal Compaq C RTL parsing rules, an OpenVMS version field in a UNIX style input file name is passed directly to the file system. Therefore, the following example accesses version number 3 of the file with name data and type dat: data.dat;3 With the new feature, this file name is passed to the OpenVMS file system as the following (a file with name data and type dat;3): data.dat^;3 The OpenVMS version number associated with the file is not returned on output. The scope of this feature applies to allowable characters in both the directory and file-name fields of a UNIX style specification. Enabling this feature does not affect other features of the Compaq C RTL UNIX-to-OpenVMS and OpenVMS-to-UNIX path conversion. If logical-name expansion of the first element in the UNIX specification is enabled, the Compaq C RTL does not quote any special characters that appear in the logical-name equivalence string before presentation to the file system. 4 POSIX_Root_Support Support has been added to provide OpenVMS with a UNIX style root that behaves like a real directory. This allows such actions as the following: % cd / % mkdir /dirname % tar -xvf tarfile.tar /dirname % ls / Previously, the C RTL did not recognize the slash (/) character as a directory name. The normal processing for a file path starting with the slash character was to interpret the first element as a logical name or device name. If this failed, there was special processing for the name /dev/null and names starting with /bin and /tmp: /dev/null NLA0: /bin SYS$SYSTEM: /tmp SYS$SCRATCH: These behaviors are retained for compatibility purposes. In addition, support has been added to the C RTL for the logical name SYS$POSIX_ROOT as an equivalent to the slash character. To enable this feature for use by the C RTL, define SYS$POSIX_ ROOT as a concealed logical name. For example: $ DEFINE/TRANSLATION=(CONCEALED,TERMINAL) - _$ SYS$POSIX_ROOT "$1$DKA0:[SYS0.coe.]" To disable this feature, enter the following command: $ DEFINE DECC$DISABLE_POSIX_ROOT {1, ENABLE 0, DISABLE} Enabling SYS$POSIX_ROOT results in the following behavior: o If the existing translation of a UNIX path starting with the slash (/) character fails and SYS$POSIX_ROOT is defined, the name is interpreted as if it starts with /sys$posix_root. o When converting from an OpenVMS to a UNIX style file name, and the OpenVMS name starts with SYS$POSIX_ROOT:, then the SYS$POSIX_ROOT: portion is removed. For example, SYS$POSIX_ ROOT:[dirname] becomes /dirname. If the resulting name could be interpreted as a logical name or as one of the special cases listed, the result is /./dirname instead of /dirname. 4 32-Bit_Group_Identifiers The C RTL supports 32-bit user identification (UID) and group identification (GID). 32-bit UID and GID support was added to some versions of the OpenVMS operating system to provide support for POSIX style identifiers. Although OpenVMS 7.3-1 does not support POSIX style IDs, it does support 32-bit UID and GID. When an application is compiled to use 32-bit UID/GID, the UID and GID are derived from the UIC, as in previous versions of the operating system. In some cases, such as with the getgroups function, more information might be returned when the application supports 32-bit GIDs. To compile an application for 32-bit UID or GID support, define the macro __USE_LONG_GID_T. To compile an application for 16-bit UID or GID support, define the macro _DECC_SHORT_GID_T. In addition, although you cannot compile with POSIX style IDs enabled on OpenVMS Version 7.3-1, you can run programs that were compiled with POSIX style IDs enabled on OpenVMS systems that do provide that support. 4 New_and_Changed_C_RTL_Functions The Compaq C RTL includes the following new or modified functions for OpenVMS Version 7.3-1: o New feature switch-setting functions: decc$feature_get_index decc$feature_get_name decc$feature_get_value decc$feature_set_value o New scanf functions: vfscanf vfwscanf vscanf vwscanf vsscanf vswscanf o New functions to support 64-bit file sizes and offsets: fseeko ftello o Functions modified to support 64-bit file sizes and offsets: fstat ftruncate ftw lseek mmap stat truncate 3 DECdtm DECdtm provides basic infrastructure for a distributed transaction processing system. Several DECdtm system services are now documented. For information about the XA capability with DECdtm, see DECdtm. DECdtm System Services lists all newly documented DECdtm system services. Table 5-1 DECdtm System Services System System Service with Service Wait Description $ABORT_TRANS $ABORT_ Aborts a transaction. TRANSW $ACK_EVENT Acknowledges an event reported to an RM participant or an RMI. $ADD_BRANCH $ADD_BRANCHW Authorizes a new branch to be added to a transaction. $CREATE_UID Generates a universally unique identifier. $DECLARE_RM $DECLARE_RMW Creates a new resource manager instance (RMI). $END_BRANCH $END_BRANCHW Removes a branch from a transaction and returns the transaction outcome. $END_TRANS $ENDTRANSW Ends a transaction. $FORGET_RM $FORGETRMW Deletes an RMI from the calling process. $GET_ Returns the default transaction of DEFAULT_ the calling process. TRANS $GETDTI $GETDTIW Returns information about the state of individual transactions. $JOIN_RM $JOIN_RMW Adds a new RM participant to a transaction. $SET_ $SET_ Sets or clears the default DEFAULT_ DEFAULT_ transaction of the calling process. TRANS TRANSW $SETDTI $SETDTIW Sets process current transaction and removes resource managers from transactions. $START_ $START_ Adds a new branch to a transaction. BRANCH BRANCHW $START_TRANS $START_ Starts a transaction. TRANSW $TRANS_EVENT $TRANS_ Forces certain transaction state EVENTW changes. For More Information On See DECdtm system OpenVMS System Services Reference Manual services Managing OpenVMS System Manager's Manual DECdtm and XA transactions XGCP Utility used OpenVMS System Management Utilities Reference with DECdtm/XA Manual Programming with OpenVMS Programming Concepts Manual, Volume II DECdtm and XA 3 CDSA_and_SSL Common Data Security Architecture (CDSA) is a multiplatform, industry-standard security infrastructure. It provides a standards-based, stable programming interface that applications can use to access operating system security services, allowing developers to create cross-platform, security-enabled applications. Applications request security services, such as cryptography and other public key operations, through a dynamically extensible application programming interface (API). These requests are serviced by a set of plug-in security service provider interfaces (SPIs), which can be supplemented or changed as business needs and technologies evolve. Compaq SSL (Secure Sockets Layer) for OpenVMS Alpha provides industry standard tools that enable secure and accurate network communications with OpenVMS systems in the enterprise. Using strong cryptography and sophisticated hashing algorithms, messages are encrypted for secure transmission and the integrity of the data is validated, ensuring that all data arrived intact and unmodified. Secure Sockets Layer (SSL) is the open standard security protocol for the secure transfer of sensitive information over the Internet. SSL provides three major capabilities: o Privacy through encryption o Server authentication o Message integrity Client authentication is available as an optional function. Compaq SSL V1.0 for OpenVMS Alpha ports the SSL 0.9.6B toolkit and cryptography library to OpenVMS Alpha Version 7.3-1. Compaq SSL for OpenVMS Alpha provides a certificate tool that is a simple interface for viewing and creating SSL certificates. The SSL Certificate Tool enables you to perform the most important certification functions with ease: o View certificates and certificate requests o Create certificate requests o Sign your own certificate o Create your own certificate authority o Sign client certificate requests Additional hash functions are included. For more detailed information, refer to the Open Source Security for OpenVMS Alpha, Volume 1: Common Data Security Architecture or Open Source Security for OpenVMS Alpha, Volume 2: Compaq SSL (Secure Sockets Layer) for OpenVMS Alpha. 3 LDAP_with_SSL Customers who need added security protection for their enterprise information stored in an LDAP directory can now use Compaq SSL for OpenVMS Alpha in an LDAP session. SSL uses X.509 public key technology to provide the following security functions: o Integrity and confidentiality of the LDAP dialogue o Authentication of the client o Authentication of the server When you connect to an LDAP directory, you need to log in to use certain services. This involves sending a bind() request to the server. The username/password in a simple bind is sent in clear text. SSL is important because, with Compaq SSL, this bind request is encrypted making the password unreadable except to the server. For details, refer to the LDAP chapter in the OpenVMS Utility Routines Manual. 3 FREDs A new structure, the floating-point registers and execution data block (FRED), is a combined structure that contains the HWPCB, the floating-point register save area, and the per-kernel thread data. Prior to Version 7.2, OpenVMS supported 16 kernel threads per process. With Version 7.2 and later, OpenVMS supported 256 kernel threads per process. Also, prior to Version 7.3-1, OpenVMS allocated the maximum number of FRED blocks for a given process when that process was created, even if the process did not become multithreaded. With Version 7.3-1, OpenVMS allocates all FRED blocks on an as-needed basis. This results in improved scaling and performance for applications using kernel threads. For more information, refer to the OpenVMS Programming Concepts Manual, Volume I. 3 Future_Changes NOTE This information pertains to a future version of OpenVMS and does NOT affect OpenVMS Version 7.3-1. With the upcoming port of the OpenVMS operating system to the Intel Itanium processor architecture, customers should be aware of conflicts arising from the use of the SYI$_HW_MODEL system service to determine the processor architecture. Previously, HW_MODEL 1024 and greater indicated an Alpha system. With the Itanium-based systems, this will no longer be true. Compaq recommends that customers determine the system achitecture by using either the SYI$_ARCH_TYPE or SYI$_ARCH_NAME system services on all platforms. The following table lists the specific system services and their current return values or working suggestions: Processor Value Returned System Marketing Model (SMM), SYI$_HW_MODEL, word field VAX 1:1023 VAX$K_name highest issued: 541 Alpha 1024:4095 ALPHA$K_name highest issued: 2006 Itanium 4096:8191 IPF$K_name Processor CPQ 8191:32767 Reserved ISV 32768:65535 Reserved SYI$_ARCH_NAME, fifteen characters VAX "VAX" Alpha "Alpha" Itanium "IA-64" Processor OTHER "OTHER" SYI$_ARCH_TYPE, longword OTHER 0 VAX 1 Alpha 2 Itanium 3 Processor SYI$_NODE_SWTYPE, longword All "VMS" SYI$_CPU, longword VAX CPU code Others SS$_NOTAVAX SYI$_CPUTYPE (and SYI$_REAL_CPUTYPE), longword Alpha Alpha microprocessor core code Others SS$_NOTALPHA (new) SYI$_CPULID (new) (and SYI$_REAL_CPULID), longword Itanium Itanium Processor Processor LID value Others SS$_NOTIA64 (new) SYI$_SID, longword VAX CPU code Others 256 SYI$_CPULID (new) (and SYI$_REAL_CPULID), longword Itanium Itanium Processor Processor LID value Others SS$_NOTIA64 (new) SYI$_SID, longword VAX CPU code Others 256 SYI$_SYSTYPE, longword VAX Not implemented on VAX Alpha Alpha platform highest issued: 40 family code 1:63 Itanium Itanium Processor Processor platform family code (64:255) 256:32767 Compaq reserved 32768:~0 ISV reserved SYI$_XCPU, longword All Implementation- specific SYI$_XSID, longword All Implementation- specific 3 Image_Sections_in_Galaxy OpenVMS Galaxy offers the ability to share data between Galaxy instances, (provided by OpenVMS as Galaxy global sections). OpenVMS Version 7.3-1 adds support in the INSTALL utility and the image activator to place write shared image sections in Galaxy global sections. This feature allows existing applications that share data using writeable image sections to be extended to a Galaxy environment. INSTALL/ADD WRITABLE=GALAXY places write shared image sections in Galaxy global sections. You can also use the IDENT keyword with GALAXY to include the image identity in the name of the Galaxy global section. Doing this lets you use multiple versions of an image simultaneously in a Galaxy system. Refer to the OpenVMS Alpha Partitioning and Galaxy Guide for more details. 3 Larger_Mailbox_Buffer_Quotas Prior to Version 7.3-1, the maximum size for the mailbox buffer quota was 64,000 bytes. OpenVMS Alpha Version 7.3-1 supports the creation of mailboxes with larger buffer quotas for improved application scaling. When creating a mailbox with the $CREMBX system service, you can explicitly supply a mailbox buffer quota with the BUFQUO parameter. If not, the mailbox buffer quota is implicitly supplied by the system parameter DEFMBXBUFQUO. Note the following: o Temporary mailboxes do not have a specific size limit. o The size of the mailbox is subtracted from the BYTLM quota of the process. o Permanent mailboxes do not consume process quota; however, any data in a mailbox consumes nonpaged pool. 3 RMS_New_Features The following topics describe new RMS features added to the OpenVMS Alpha Version 7.3-1 operating system that improve I/O performance and enable easier porting from UNIX to OpenVMS Alpha. 4 IO_Transfer_Size The multiblock count for a sequential disk file sizes the RMS intermediate buffer for disk block transfers; this count serves as the I/O transfer size. The system default multiblock count is increased from 16 to 32. This increase reduces sequential file read or write I/O requests by a factor of 2. If the application does not assign the multiblock count explicitly (using the RAB$B_ MBC setting) or as a process default (using the DCL command SET RMS_DEFAULT), the new system default multiblock count of 32 applies. The process or system multiblock count default parameters (set with the SET RMS_DEFAULT/BLOCK_COUNT or SET RMS_ DEFAULT/SYSTEM/BLOCK_COUNT command, or with or the SYSGEN parameter RMS_DFMBC) can dynamically restore the default value for a process or system to the former value of 16 blocks. You can also increase the multiblock count to greater than 32 at either the process or system level, after making appropriate changes to working set quotas. The maximum multiblock count is 127 blocks. Because a larger RMS buffer can lead to increased page faulting by a process with a small working set quota, the increase in the system default is limited to 32. Because files opened as process-permanent files (PPF) by DCL are not affected by process or system multiblock defaults, DCL file opens are not affected by this improvement. However, note that the change to the system multiblock count default can affect any privileged application that uses the FAB$V_PPF (undocumented) option to open a process-permanent file, if the application does not assign the multiblock count explicitly in the application itself (using the RAB$B_MBC setting). While this multiblock increase is compatible in a mixed cluster, it has an indirect effect on VAX or older Alpha versions. If a shared sequential file is first opened from the new release, the system multiblock default is 32 blocks. Because the first accessor determines the multiblock count for all subsequent accessors, 32 is the multiblock count for any subsequent accessors opening the file from an older system. This new feature also indirectly changes the default extend quantity, which uses 64 blocks (two times the multiblock count of 32) instead of the current 32 blocks (two times the default multiblock count of 16). 4 Support_for_POSIX-Compliant_File_Timestamps To enable easier porting of UNIX applications to OpenVMS Alpha, RMS adds support for POSIX-compliant file timestamps. The XABDAT structure has been extended to include the POSIX-compliant access date, attribute modification date, and data modification date ($OPEN and $DISPLAY). This mechanism can also be used to set all dates on a $CREATE, which is likely to happen in the case of a file restoration. Support for these dates is restricted to ODS-5 volumes and requires the volume to be enabled for access date support. Updating the POSIX-compliant access date, attribute modification date, and data modification date values through RMS is supported using the XABITM structure. XABITM$_NORECORD can be used to suppress update of access time. 4 Write-Behind_Option An existing user write-behind (RAB$V_WBH setting in RAB$L_ROP) option is available for unshared sequential files to request that RMS overlap writes to disk. Specifying the write-behind option ensures that at least two buffers are allocated by RMS at connect time. When one buffer has been filled with records, RMS switches to the second buffer and issues an asynchronous QIO to write the contents of the first buffer out to disk. RMS does not stall the process, but rather continues to process records in the second buffer while the QIO for the first buffer is completing. Overlapping I/O can be a big performance win for some applications. OpenVMS Alpha Version 7.3-1 introduces a new system RMS write- behind performance option as a dynamic SYSGEN parameter (RMS_ SEQFILE_WBH) to externally request RMS to implement the write- behind feature as a system default (refer to the OpenVMS System Management Utilities Reference Manual). If this system option is set, RMS implements the existing RMS user write-behind option as a system default (regardless of the RAB$L_ROP RAB$V_WBH setting) whenever write access is requested for an unshared sequential file that is opened for image I/O. This feature is a system option. It is not the default, however, for the following reasons: o Enabling write-behind involves a change in error reporting that could affect some applications. (A write error might be reported for a subsequent operation rather than for the write on which the error occurred.) o The allocation of an additional RMS intermediate buffer might result in more page faulting if process working set quotas are insufficient. 3 SDA OpenVMS Alpha Version 7.3-1 performs a faster large memory dump that significantly reduces the time to write a system crash dump file. There are also a number of new commands and qualifiers for the System Dump Analyzer (SDA), including the new SDA Extended File Cache (XFC) commands. For more information, refer to the OpenVMS Alpha System Analysis Tools Manual. 4 VALIDATE_TQE The new VALIDATE TQE command validates all the data structures associated with timer queue entries (TQEs). 4 New_TQE_Type The SHOW TQE command displays timer queue entries (TQEs), including the following new TQE type: Column Symbol Description 6 N TQE should not be deallocated at AST completion. - TQE should be deallocated at AST completion. 4 New_Qualifiers New SDA Command Qualifiers describes the new SDA command qualifiers in OpenVMS Version 7.3-1. Table 5-2 New SDA Command Qualifiers Command Qualifier Description SHOW /POOL Displays the dynamic storage pool of PROCESS the process P0 (process) or P1 (control) region. The following qualifiers from the SHOW PROCESS command now also apply to the SHOW PROCESS/POOL command: /FREE, /HEADER, /MAXIMUM_BYTES, /STATISTICS, /SUBTYPE, /SUMMARY, /TYPE, and /UNUSED. /TQE Displays all timer queue entries associated with the current process. SHOW /LIST Displays summary information for each RESOURCES resource, followed by a list of all locks associated with the resource. 4 XFC_Commands The SDA Extended File Cache (XFC) commands along with their parameters and qualifiers are described in New SDA Extended File Cache (XFC) Commands. These commands provide analysis tools for tuning the extended file cache to improve the performance of your programs. Table 5-3 New SDA Extended File Cache (XFC) Commands Command Function EXIT Exits the XFC SDA extensions. This command has no parameters or qualifiers. LOAD Loads the symbols in the specified debug symbol file DSF (DSF) for use with the SDA> FORMAT command. This command has no parameters or qualifiers. SHOW Displays the contents of an XFC context structure CONTEXT (CTX). It has one parameter, address, which is the address of the CTX. If no address is supplied, then all the context structures are displayed. It has three qualifiers: o /BRIEF Displays a brief summary for each context; for example, the I/O type, start VBN, and length of I/O. o /FULL Displays the complete context structure. This is the default. o /STALLING Displays only contexts that are stalling; for example, those that have a stall reason code other than estrNotStalling. SHOW Displays the contents of an extent control block (ECB). EXTENT It has one parameter, address, which is the address of the ECB. It has no qualifiers. SHOW Displays the contents of the cache file block (CFB). It FILE has one parameter, address, which is the address of the CFB. The /OPEN and /CLOSED qualifiers, if present, are ignored. If no address is supplied, then all the CFBs are displayed. It has eight qualifiers: o /BRIEF Displays summary information for each cache file block (CFB), such as the CFB address, control volume block (CVB) address, access count, active I/O count, and file ID. o /CLOSED Displays only CFBs whose access count is zero. o /CVB=address Displays only information about any files matching the given Cache Volume Block address. o /EXTENTS Displays the cache extents held in cache for any displayed files. This shows the primary and secondary cache extents along with their data state and VBNs. It also shows a summary of memory usage (pagelets used and pagelets valid) for any displayed files. The /EXTENTS qualifier is incompatible with the /BRIEF qualifier. o /FULL Displays all fields for each Cache File Block. This is the default. o /ID=file-id Displays only information about any files matching the given file-identification. The file ID (FID) is the hexadecimal file-number component in a (file- number, sequence number, relative volume number) format file ID. o /OPEN Displays only CFBs whose access count is greater than zero. o STATISTICS Displays more statistics about the specified file. The /STATISTICS qualifier is incompatible with the /BRIEF qualifier. SHOW Displays information about memory used by the cache. It MEMORY has no parameters. It has two qualifiers: o /BRIEF Displays summary statistics on XFC memory use. o /FULL Displays full statistics on XFC memory use. SHOW Displays general information about the Extended File SUMMARY Cache. It has no parameters. It has one qualifier, /STATISTICS, which displays read and write activity arranged by I/O size. SHOW Displays both the extent hash table (EHT) and the file TABLES hash table (FHT). It has no parameters. It has four qualifiers: o /ALL Displays the contents of the EHT and FHT. This is the default. o /EXTENT Displays the contents of the EHT. o /FILE Displays the contents of the FHT. o /SUMMARY Displays summary information about EHT and FHT. SHOW Displays all or selected portions of the XFC trace TRACE buffer, starting with the most recent entry and moving backward in time. It has no parameters. It has six qualifiers: o /ALL Displays the entire trace buffer. This is the default. o /CONTAINING=value Displays only records where any of the traced parameters are equal to value. o /CPU=cpu-num Displays only records from threads executing on CPU cpu-num. o /LINENUMBER=linenumber Displays only records from tracepoints at line linenumber in the relevant source files. o /MATCH [=AND|OR] Alters the sense of the match condition when more than one of the filter qualifiers /CPU, /LINENUMBER, /FILENAME, /Px, or /CONTAINING are specified. o /Px=value Displays only records where one of the traced parameters P1, P2, P3, or P4 are equal to value. SHOW Displays the contents of a cache volume block (CVB). VOLUME It has one parameter, address, which is the address of a CVB. If no address is supplied, then all volumes are displayed. It has four qualifiers: o /BRIEF Displays summary information for each volume. o /FULL Displays a complete list of information about the volume(s). This is the default. o /NAME=DISK$volume_label Displays information for the volume with the specified name. o /STATISTICS Displays the read and write I/O activity for this volume. The /STATISTICS qualifier is incompatible with the /BRIEF qualifier. 3 SDA_Spinlock_Tracing The SHOW TRACE and SHOW COLLECT commands from the SDA Spinlock Tracing utility have the following new qualifiers: Qualifier Description /RATES Reports activity as a rate per second and hold/spin time as a percentage of time. This is the default. /TOTALS Reports activity as a count and hold/spin time as cycles. 3 System_Services System Service/Project Documentation Update DECdtm The following services have been added: $ACK_EVENT, $ADD_BRANCH[W], $CREATE_UID, $DECLARE_RM[W], $END_BRANCH[W], $FORGET_RM[W], $GETDTI[W], $GET_DEFAULT_TRANS, $JOIN_RM[W], $SETDTI[W], $SET_DEFAULT_TRANS[W], $START_ BRANCH[W], $TRANS_EVENT[W] The following services have been updated: $ABORT_TRANS[W], $END_TRANS[W], $START_TRANS[W] $ACM[W] New services for Authentication and Credentials Management (ACM). $ASSIGN A new status code, SS$_EXBYTLM, has been added. $CPU_ Two symbolic names, CST$K_CPU_POWER_OFF and TRANSITION CST$K_CPU_POWER_ON, have been added to the tran_ code argument. $CREMBX The text has been updated for the SS$_BADPARAM condition value and the bufquo and maxmsg arguments. Note that the maximum value limit of 60,000 bytes for the bufquo argument no longer applies. $DELPRC A new argument, flag, has been added. $ERAPAT The code example has been updated. $GETDVI Two new item codes, DVI$_MPDEV_CURRENT_PATH and DVI$_MULTIPATH, have been added. The following bits have been added to the DVI$_ STS item code: UCB$V_ALTBSY, UCB$V_CLUTRAN, UCB$V_DISMOUNT, UCB$V_EXFUNC_SUPP, UCB$V_FAST_PATH, UCB$V_FP_ HWINT, UCB$V_IOPOST_LOCAL, UCB$V_LCL_VALID, UCB$V_MNTVERPND, UCB$V_NO_ASSIGN, UCB$V_ PATHVERIP, UCB$V_SNAPSHOT, UCB$V_SUPMVMSG, UCB$V_SVPN_END, UCB$V_WRTLOCKMV. $GETTIM The Description section has been updated. $GETJPI The item code description for JPI$_ASTEN has been updated to include all processes. The following persona item codes have been added: JPI$_CLASSIFICATION, JPI$_PERSONA_ID, JPI$_ PERSONA_AUTHPRIV, JPI$_PERSONA_PERMPRIV, JPI$_ PERSONA_WORKPRIV, JPI$_IMAGE_WORKPRIV, JPI$_ IMAGE_AUTHPRIV, JPI$_IMAGE_PERMPRIV, JPI$_ PERSONA_RIGHTS, JPI$_SUBSYSTEM_RIGHTS, JPI$_ INSTALL_RIGHTS, JPI$_PERSONA_RIGHTS_SIZE, JPI$_ SUBSYSTEM_RIGHTS_SIZE, JPI$_SYSTEM_RIGHTS_SIZE, JPI$_INSTALL_RIGHTS_SIZE $GETQUI The following items have been added for NUMA RAD Batch Job Support: o QUI$_RAD item code o QUI$V_JOB_RAD symbolic name for the QUI$_JOB_ FLAGS item code o QUI$V_QUEUE_RAD symbolic name for the QUI$_ QUEUE_FLAGS item code The QUI$_TRANSLATE_QUEUE function code has been added to the QUI$_QUEUE_NAME item code list. The string length limit has been changed to 255 characters for the QUI$_DEVICE_NAME item code. $GETSYI The SYI$_NODE_HWVERS item code text has been updated. A new error status, SS$_UNREACHABLE, has been added. The following item codes have been added: SYI$_ACTIVE_CPU_MASK, SYI$_AVAIL_CPU_MASK, SYI$_ CPU_AUTOSTART, SYI$_CPU_FAILOVER, SYI$_CPUCAP_ MASK, SYI$_GLX_FORMATION, SYI$_GLX_MAX_MEMBERS, SYI$_GLX_MBR_MEMBER, SYI$_GLX_MBR_NAME, SYI$_ GLX_TERMINATION, SYI$_HP_ACTIVE_CPU_CNT, SYI$_ HP_ACTIVE_SP_CNT, SYI$_HP_CONFIG_SBB_CNT, SYI$_ HP_CONFIG_SP_CNT, SYI$_MAX_CPUS, SYI$_POTENTIAL_ CPU_MASK, SYI$_POTENTIALCPU_CNT, SYI$_POWERED_ CPU_MASK, SYI$_POWEREDCPU_CNT, SYI$_PRESENT_CPU_ MASK, SYI$_PRESENTCPU_CNT, SYI$_PRIMARY_CPUID $GETUAI The context argument restriction for VAX only has been removed. $ICC_CONNECT A new status code, SS$_NOPRIV, has been added. $PROCESS_ A new item code, CAP$M_PURGE_WS_IF_NEW_RAD, has AFFINITY been added. $PROCESS_ A new item code, CAP$M_PURGE_WS_IF_NEW_RAD, has CAPABILITIES been added. $PURGWS A new condition value, SS$_NOPRIV, has been added. $REGISTRY The item code, REG$_VALUEDATASIZE, has been added. $SNDJBC The following item codes have been added for NUMA RAD Batch Job Support: SJC$_RAD and SJC$_ NO_RAD. A new item code, SJC$_JOB_COMPLETION_STATUS, has been added. The string length limit has been changed to 255 characters for the SJC$_DEVICE_NAME item code. $SUSPND A cluster-related note has been added to the description section. 3 System_Services_and_NUMA_RADs The following services have been updated to support batch jobs for NUMA Resource Affinity Domains (RADs): o $GETQUI o $SNDJBC For information about the system management updates, see Batch Job Support for NUMA RADs in this manual, and refer to the OpenVMS System Services Reference Manual. 4 $GETQUI_Updates This section describes updates to the $GETQUI service. 5 New_Item_Code The QUI$_RAD output item code is used to return the value of the RAD attribute attached to a queue or a job. The item code expects a 32-bit buffer in which to write the value of the RAD. A value of -1 is returned to the buffer if no RAD is specified for the queue or the job. The QUI$_RAD item code is valid for the following function codes: o QUI$_DISPLAY_ENTRY o QUI$_DISPLAY_JOB o QUI$_DISPLAY_QUEUE 5 New_RAD_Flags New bits have been added to the queue flags and job flags item codes for RAD support. The QUI$V_JOB_RAD bit of the QUI$_JOB_FLAGS item indicates whether the job will use the RAD processing option. The QUI$V_QUEUE_RAD bit of the QUI$_QUEUE_FLAGS item indicates whether the RAD processing option attribute is specified for the batch queue. 4 $SNDJBC_Updates There are two new $SNDJBC item codes: SJC$_RAD and SJC$_NO_RAD. The SJC$_RAD input item code is used to specify a RAD number on which to create a batch process. The item accepts a 32-bit integer value as input. The input is validated to be within the range of 0 to SYI$_RAD_MAX_RADS. The SJC$_NO_RAD input item code is a boolean input item code. When the SJC$_NO_RAD code is specified in a request, the RAD value for the queue or job is removed. The new item codes are valid for the following function codes: o SJC$_ALTER_JOB o SJC$_ALTER_QUEUE o SJC$_CREATE_JOB o SJC$_CREATE_QUEUE o SJC$_ENTER_FILE o SJC$_START_QUEUE 3 NUMA_Support_Added_to_Threads_Libraries To improve application scaling and performance on GS Series Alpha (NUMA) systems, a threaded program can now utilize more than one RAD of a NUMA system. For applications with a high degree of parallelism, using multiple RADs can increase performance. 2 Associated_Products This topic describes new features of Compaq OpenVMS operating system associated products. For a listing and directory information about the OpenVMS associated products, refer to the Guide to OpenVMS Version 7.3-1 CD-ROMs. 3 Advanced_Server Version 7.3 of the Compaq Advanced Server for OpenVMS is supported on OpenVMS Alpha Version 7.3-1. Version 7.3 of the Advanced Server for OpenVMS includes support of the following features: o Member server role (allowing the server to participate in Windows 2000 native-mode domains) o Greater compatibility with a wide variety of clients and legacy applications, with support of: - Extended character sets, in addition to Extended File Specifications - Alias file names, created for shared files whose names do not comply with the more restricted file-naming conventions of legacy applications, such as MS-DOS o Remote Windows NT printer management (SpoolSS) for printers shared on the Advanced Server for OpenVMS o DNS for resolving NetBIOS names o Cluster load balancing using DNS to resolve the server cluster alias name o PCSI for installing the server o Windows 2000 client and domain support o Windows XP Professional client support To access Advanced Server for OpenVMS, clients must be licensed using the Advanced Server V7.3 license PAK: PWLMXXXCA07.03. For more information, refer to the Compaq Advanced Server for OpenVMS Guide to Managing Advanced Server Licenses. For information about installing Advanced Server for OpenVMS, refer to the Compaq Advanced Server for OpenVMS Installation and Configuration Guide provided with the kit documentation. For information about upgrading from Compaq PATHWORKS for OpenVMS to the Advanced Server for OpenVMS, see OpenVMS Alpha Version 7.3-1 Release Notes. For more information on upgrading PATHWORKS for OpenVMS and about installing Advanced Server for OpenVMS, refer to the Compaq Advanced Server for OpenVMS Installation and Configuration Guide provided with the kit documentation. For information about the latest release of the PATHWORKS for OpenVMS (Advanced Server) product, see PATHWORKS. 3 Compaq_C_Run-Time_Header_Files_Library The Compaq C Run-Time Library provides functions and macros for developing flexibile and highly portable applications. To install the header files library from the Compaq C Run-Time Library, do the following: 1. After installing the other Compaq C products and kits, mount the OpenVMS Alpha Version 7.3-1 Layered Products CD-ROM. 2. Read any README files in the following directory: [.CRTL.DOCUMENTATION] 3. Copy [.CRTL.KIT]DECC$RTLDEF.TLB from the CD-ROM to the SYS$LIBRARY directory. Use a command in the following format: $ COPY device:[CRTL]DECC$RTLDEF.TLB SYS$LIBRARY where device is the device name for the CD-ROM drive (for example, DKA0:). NOTE Always copy this file after you have installed the other Compaq C products and kits so that DECC$RTLDEF.TLB does not get overwritten. 3 PATHWORKS Version 6.1 of the Compaq PATHWORKS for OpenVMS (Advanced Server) is supported on OpenVMS Version 7.3-1; Version 6.1 of the PATHWORKS product is currently available on the Software Products Library. Earlier versions of PATHWORKS for OpenVMS servers must be upgraded. For more information, see OpenVMS Alpha Version 7.3-1 Release Notes. PATHWORKS for OpenVMS (Advanced Server) is supported on OpenVMS VAX as well as OpenVMS Alpha systems. New features of Version 6.1 of the PATHWORKS for OpenVMS (Advanced Server) product include the following: o Member server role (allowing the server to participate in Windows 2000 native-mode domains) o Greater compatibility with a wide variety of clients and legacy applications, with support of alias file names, created for shared files whose names do not comply with the more restricted file-naming conventions of legacy applications such as MS-DOS o DNS for resolving NetBIOS names, expanding support of dynamic cluster load balancing to WANs o Windows 2000 client and domain support o Windows XP Professional client support To access PATHWORKS 6.1 for OpenVMS (Advanced Server) on OpenVMS Version 7.3 or 7.3-1, clients must be licensed using the license PAK PWLMXXXCA07.03. For more information, refer to the Compaq Advanced Server for OpenVMS Guide to Managing Advanced Server Licenses. For information about the latest release of Compaq Advanced Server for OpenVMS, see Advanced Server. 3 TCPIP Version 5.3 of TCP/IP Services provides performance improvements and software enhancements, including: o IPv6 tunneling, providing support for: - 6-to-4 tunnelling - Anycast address - ICMPv6 MIBs - An updated API - Mobile IPv6 correspondent node - Mobile IPv6 in the UNIX management tools o NTP (Time Service) Version 4 o BIND Version 9 server (on Alpha systems only) o IMAP mail server o Kerberos authentication for Telnet client connections o Subsystem configuration using the SYSCONFIGTAB database (as on UNIX systems) o Expanded online help for error messages o Enhancements to the LPD server to improve network printing and printer management in OpenVMS cluster environments o Support for an editable text file that associates Internet service names and aliases with a port number and protocol (as on UNIX systems) o Support for OpenVMS Extended File Specifications in the NFS server and the FTP server o Support for UNIX path names in the FTP server and FTP client (on Alpha systems only) o Support for the configuration and management of user-written network services (services not supplied with the TCP/IP Services software) Details on these features and information about upgrading to Version 5.3 of TCP/IP Services for OpenVMS are available in the Compaq TCP/IP Services for OpenVMS Release Notes. Additional product information is available at: http://www.openvms.compaq.com/network/tcpip.html 3 Management_Station OpenVMS Management Station Version 3.2 is included with this release of OpenVMS. OpenVMS Management Station is a powerful Windows based management tool for managing printers, user accounts, and storage devices. With this version of OpenVMS Management Station, you can manage a wide range of storage devices across multiple OpenVMS Cluster systems. It also provides Fibre Channel disk device support and other enhancements. For more information, refer to the OpenVMS Management Station Overview and Release Notes. 3 Powerstorm Version 2.0 of this product was released in May 2002. It is supported on OpenVMS Alpha Version 7.2-1 and later. Version 2.0 includes new features for the OpenGL Utility Toolkit (GLUT) and fixes to former problems. For complete details about Powerstorm 300/350 Graphics Support Version 2.0 for OpenVMS, refer to the release notes that ship with the product. The release notes are supplied in HTML, PDF, and text format and are located in the SYS$HELP directory after the software kit is installed: P300_350_V2_README.HTML P300_350_V2_README.PDF P300_350_V2_README.TXT 3 UNIX_Portability 3 UNIX_Portability_Features Starting with OpenVMS Alpha Version 7.3-1, we are introducing UNIX portability features into the base operating system. We will continue to add more UNIX features into the base operating system over time. To start the UNIX portability effort, we are extending our C Run-Time Library (CRTL) and ODS-5 file system to support UNIX features such as case-sensitive file names, time of last file access, hard links, and more. In addition, we are introducing a UNIX shell and utilities environment with the GNV Early Adopter's Kit on the Open Source Tools for OpenVMS CD-ROM. 3 Open_Source_Tools_for_OpenVMS_CD-ROM An Open Source Tools for OpenVMS CD-ROM is included with the OpenVMS Version 7.3-1 kit. It is a collection of various ports of Open Source projects to OpenVMS that our Engineering team has facilitated. Please note that these ports are provided as free software under the terms of the GNU Public License. The Open Source Tools for OpenVMS include the following: o GNV Early Adopter's Kit The GNV product is an open source, GNU-based, UNIX-style environment for OpenVMS for UNIX application developers, system managers, and users. It facilitates development and porting of UNIX software to OpenVMS. GNU is a UNIX-like operating system provided as free software. GNV provides a UNIX-like shell (command-line interpreter) environment and a C Run-Time Library (C RTL) supplemental library that provides utilities typically found on UNIX systems. The shell used by GNV is bash (Bourne-Again Shell, from GNU, using the POSIX.2 specification). o CDRECORD sources Open Source CDRECORD capability ships as part of OpenVMS Alpha Version 7.3-1. The full source kit used to create the CDRECORD images is provided. o Stunnel Stunnel is a program that allows you to encrypt arbitrary TCP connections inside an SSL (Secure Sockets Layer) connection from your OpenVMS system to another system. Stunnel also lets you secure non-SSL aware applications (such as Telnet, IMAP, and LDAP) by having Stunnel provide the encryption. Changes to the original application are then not required. Both images and sources are provided. o VMSTAR VMSTAR is a TAR reader/writer for the OpenVMS operating system. It can read archives ("tarfiles") on disk or tape created by the Un*x "tar" command. It can also create archives. o Zip Zip is a utility that compresses large or multiple files into a single ZIP archive. UnZip decompresses the files stored in a ZIP archive, restoring them to their original state. o OpenVMS Migration Software This utility enables software written for OpenVMS VAX to be executed on an OpenVMS Alpha system. It includes translated sharable images of the runtime libraries from OpenVMS 7.3, native images of the DECmigrate utilities, and much more. Additional information is available at http://www.softresint.com/AlphaMigrate.htm o SSL sources OpenSSL (Secure Socket Layer) ships as an optional Layered Product with OpenVMS Alpha Version 7.3-1. The sources used to build the port of OpenSSL 0.9.6b for OpenVMS are provided.