[an error occurred while processing this directive]

HP OpenVMS Systems

DII COE
» 

HP OpenVMS Systems

OpenVMS information

» What's new on our site
» Upcoming events
» Configuration and buying assistance
» Send us your comments

HP OpenVMS systems

» OpenVMS software
» Supported Servers
» OpenVMS virtualization
» OpenVMS solutions and partners
» OpenVMS success stories
» OpenVMS service and support
» OpenVMS resources and information
» OpenVMS documentation
» Education and training

Solutions and Applications

» OpenVMS e-Business
» Cross Industry Solutions
» Application Development and Integration
» Data Access
» Enterprise File and Print Services
» Mail and Messaging
» Network and Systems Management
» Web-Enabled Computing
» Base Infrastructure
» OpenVMS Solutions Status Report
» OpenVMS Server Consolidation
» Adaptive Enterprise

Evolving business value

» Business Systems Evolution
» AlphaServer systems transition planning
» Alpha RetainTrust program

Related links

» HP Integrity servers
» HP Alpha systems
» HP storage
» HP software
» HP products and services
» HP solutions
» HP support
disaster proof
HP Integrity server animation
HP Integrity server animation
Content starts here
Defense Information Infrastructure Common Operating Environment
  (DII COE) FAQ

Q:  Is OpenVMS present in the defense industry?

A:  Yes. Because of its inherent qualities of performance, scalability, availability, flexibility, security, and reliability, several customers in the defense market have adopted OpenVMS. Among them are agencies and services of the U. S. Department of Defense and several other defense operations worldwide.


Q:  What are HP's plans and strategy for OpenVMS in the defense industry?

A: To further reinforce its presence in the defense industry, HP has initiated a project that allows the OpenVMS operating system and HP AlphaServer technology to continue to participate in bids of the U.S. Department of Defense. To do so, the platform substantially complies with U.S. government specifications known as DII COE.


Q:  What does DII COE stand for and what is it?

A: DII COE (or COE) is the acronym for Defense Information Infrastructure Common Operating Environment. DII COE is a set of standards and guidelines that describe a "plug and play" open architecture designed around a client/server model defined by the Defense Information System Agency (DISA). DISA collects the requirements from the U.S. Army, the Navy, the Air Force, and so on, and then works with the Jet Propulsion Laboratory in Pasadena, CA, to create a platform-independent environment called the COE Kernel. DISA distributes this code to vendors and integrators for porting to various platforms. DISA also distributes a set of requirements concerning features of the environment (for example, minimal required tools for networking, system, and account management) and the procedures to be followed in order to be certified.


Q:  What are the goals and functionality of the COE kernel?

A:  The Department of Defense has a variety of multivendor and multiplatform environments that must be able to interoperate seamlessly. Also, nontechnical users must be able to easily operate such environments in critical environments where there is no room for error (such as military operations and on-board systems). The COE kernel addresses these requirements by providing interoperability and connectivity using a client/server approach across multiple platforms from different vendors. Also, DII COE provides a simple and intuitive interface for operations like account and security management, system management, disk management, application installation, and network management.


Q:  What did HP OpenVMS need to do to achieve DII COE compliance?

A:  Two main tasks had to be accomplished: port the COE Kernel to OpenVMS, and satisfy DISA requirements as listed in their certification process (including conformance to open standards and passing DII COE validation tests). Moreover, HP modified OpenVMS, added UNIX-style interfaces and features in order to ease the porting of the COE Kernel that was originally developed on UNIX platforms.


Q:  Will I be able to purchase DII COE?

A: The OpenVMS implementation of DII COE is distributed with OpenVMS version 7.2-6C2. The OpenVMS V7.2-6C2 kit is available only to customers and partners involved in bids with the U.S. Department of Defense. Also, because of restrictions imposed by the U.S.State Department, the distribution of OpenVMS V7.2-6C2 is limited to North America. However, the changes and improvements to OpenVMS (including industry standard APIs) that allow the porting of DII COE are released in mainstream versions of the operating system, starting with Version 7.3-1.


Q:  What standards are included in the DII COE specifications?

A:  Some of the standards are POSIX (1003.1 & 1003.2), X11, Motif, CDE, TCP/IP.


Q:  What is the status of the DII COE OpenVMS Program?

A: OpenVMS has completed the program. OpenVMS V7.2-6C2 was released in July 2002, and was submitted to DISA in order to start the official COE certification process in September 2002.


Q:  Where can I find more information about DII COE?

A: The following links provide more information about DII COE.
» OpenVMS DII COE FAQ answers key questions about the initiative.
» Official web site of the U.S Department of Defense
» Defense Information Systems Agency (DISA)
» DISA Common Operating Environment (COE)
» DISA Common Operating Environment (COE) POSIX-based Platform Compliance (PPC)
» DISA Common Operating Environment (COE) Kernel Platform Compliance (KPC) Program
» OpenVMS DII COE Compliance