Misplaced Pages

#783216

69-628: The NVAX and NVAX+ was used in late-model VAX systems released in 1991 such as the MicroVAX 3100 , VAXstation 4000 , VAX 4000 , VAX 6000 , VAX 7000/10000 and VAXft . Although Digital updated the design throughout the early 1990s, the processors, and the VAX platform itself, were ultimately superseded by the introduction of the DECchip 21064 , an implementation of the Alpha (then Alpha AXP) architecture, and

138-671: A Microsoft Windows , macOS or Linux workstation. DEC created a number of optional database products for VMS, some of which were marketed as the VAX Information Architecture family. These products included: In 1994, DEC sold Rdb, DBMS and CDD to Oracle , where they remain under active development. In 1995, DEC sold DSM to InterSystems , who renamed it Open M , and eventually replaced it with their Caché product. Examples of third-party database management systems for OpenVMS include MariaDB , Mimer SQL ( Itanium and x86-64 ), and System 1032 . VMS

207-449: A single system image abstraction. Nodes may be connected to each other via a proprietary hardware connection called Cluster Interconnect or via a standard Ethernet LAN . OpenVMS supports up to 96 nodes in a single cluster. It also allows mixed-architecture clusters. OpenVMS clusters allow applications to function during planned or unplanned outages. Planned outages include hardware and software upgrades. The DECnet protocol suite

276-637: A terminal server such as one of the DECserver family. DEC (and its successor companies) provided a wide variety of programming languages for VMS. Officially supported languages on VMS, either current or historical, include: Among OpenVMS's notable features is the Common Language Environment , a strictly defined standard that specifies calling conventions for functions and routines, including use of stacks , registers , etc., independent of programming language. Because of this, it

345-549: A 16.67 MHz (60 ns cycle time) CVAX chip set. They supported up to 64 MB of memory. MicroVMS OpenVMS , often referred to as just VMS , is a multi-user , multiprocessing and virtual memory -based operating system . It is designed to support time-sharing , batch processing , transaction processing and workstation applications. Customers using OpenVMS include banks and financial services, hospitals and healthcare, telecommunications operators, network information services, and industrial manufacturers. During

414-481: A VirtualBox VM with certain limitations; most significantly, few layered products were available, and code can only be compiled for x86-64 using cross compilers which run on Itanium-based OpenVMS systems. Following the V9.0 release, VSI released a series of updates on a monthly or bimonthly basis which added additional functionality and hypervisor support. These were designated V9.0-A through V9.0-H. In June 2021, VSI released

483-744: A common definition. DEC provided a collection of software development tools in a layered product named DECset (originally named VAXset ). This consisted of the following tools: The OpenVMS Debugger supports all DEC compilers and many third-party languages. It allows breakpoints, watchpoints and interactive runtime program debugging using either a command line or graphical user interface . A pair of lower-level debuggers, named DELTA and XDELTA , can be used to debug privileged code in additional to normal application code. In 2019, VSI released an officially supported Integrated Development Environment for VMS based on Visual Studio Code . This allows VMS applications to be developed and debugged remotely from

552-603: A desktop form factor. The final model in the series was the NVAX++, or NV5, offering 50 VUPs. This was the last VAX processor, DEC had moved entirely to the DEC Alpha after that point. NVAX contained 1.3 million transistors on a die measuring 16.2 by 14.6 mm in size (236.52 mm²). The die was fabricated in Digital's fourth-generation CMOS process, CMOS-4, a 0.75 μm process with three layers of aluminium interconnect . The NVAX

621-477: A distinction between 32-bit and 64-bit executables, but instead allows for both 32-bit and 64-bit pointers to be used within the same code. This is known as mixed pointer support. The 64-bit OpenVMS Alpha releases support a maximum virtual address space size of 8TiB (a 43-bit address space), which is the maximum supported by the Alpha 21064 and Alpha 21164 . One of the more noteworthy Alpha-only features of OpenVMS

690-531: A four-stage floating-point and integer multiply pipeline and a non-pipelined floating-point divider. MicroVAX The MicroVAX is a discontinued family of low-cost minicomputers developed and manufactured by Digital Equipment Corporation (DEC). The first model, the MicroVAX I, was first shipped in 1984. They used processors that implemented the VAX instruction set architecture (ISA) and were succeeded by

759-541: A higher level of privilege than most user code. This is in order to prevent accidental or malicious manipulation of the CLI's code and data structures by user-mode code. OpenVMS supports clustering (first called VAXcluster and later VMScluster ), where multiple computers run their own instance of the operating system. Clustered computers (nodes) may be fully independent from each other, or they may share devices like disk drives and printers. Communication across nodes provides

SECTION 10

#1732775872784

828-466: A layered architecture, consisting of a privileged Executive , an intermediately privileged Command Language Interpreter, and unprivileged utilities and run-time libraries (RTLs). Unprivileged code typically invokes the functionality of the Executive through system services (equivalent to system calls in other operating systems). OpenVMS' layers and mechanisms are built around certain features of

897-628: A project to design a 32-bit extension to its PDP-11 computer line. The hardware component was code named Star ; the operating system was code named Starlet . Roger Gourd was the project lead for VMS. Software engineers Dave Cutler , Dick Hustvedt , and Peter Lipman acted as technical project leaders. The Star and Starlet projects culminated in the VAX-11/780 computer and the VAX/VMS operating system. The Starlet project's code name survives in VMS in

966-475: A prototype Alpha EV3 -based Alpha Demonstration Unit in early 1991. The main challenge in porting VMS to a new architecture was that VMS and the VAX were designed together, meaning that VMS was dependent on certain details of the VAX architecture. Furthermore, a significant amount of the VMS kernel, layered products, and customer-developed applications were implemented in VAX MACRO assembly code. Some of

1035-423: A team was set up to design new VAX/VMS systems of comparable performance to RISC -based Unix systems. After a number of failed attempts to design a faster VAX-compatible processor, the group demonstrated the feasibility of porting VMS and its applications to a RISC architecture based on PRISM. This led to the creation of the Alpha architecture. The project to port VMS to Alpha began in 1989, and first booted on

1104-501: Is developed and supported by VMS Software Inc. (VSI). OpenVMS offers high availability through clustering —the ability to distribute the system over multiple physical machines. This allows clustered applications and data to remain continuously available while operating system software and hardware maintenance and upgrades are performed, or if part of the cluster is destroyed. VMS cluster uptimes of 17 years have been reported. In April 1975, Digital Equipment Corporation embarked on

1173-617: Is further subdivided between the Kernel , which consists of the code which runs at the kernel access mode, and the less-privileged code outside of the Kernel which runs at the executive access mode. The components of the Executive which run at executive access mode include the Record Management Services , and certain system services such as image activation. The main distinction between the kernel and executive access modes

1242-587: Is limited to 2 TiB volumes. DEC attempted to replace it with a log-structured file system named Spiralog, first released in 1995. However, Spiralog was discontinued due to a variety of problems, including issues with handling full volumes. Instead, there has been discussion of porting the open-source GFS2 file system to OpenVMS. An OpenVMS Command Language Interpreter (CLI) implements a command-line interface for OpenVMS, responsible for executing individual commands and command procedures (equivalent to shell scripts or batch files ). The standard CLI for OpenVMS

1311-478: Is packaged in a 339-pin pin grid array . The NVAX was offered at a variety of clock speeds, 83.3 MHz (12 ns), 71 MHz (14 ns) and 62.5 MHz (16 ns), while the NVAX+ is clocked at a frequency of 90.9 MHz (11 ns). The NVAX offered about 25 VAX Unit of Performance (VUPs). The NVAX+, introduced at the same time, was identical in terms of the processor design but used a different bus, cache system and its external connection

1380-584: Is possible to call a routine written in one language (for example, Fortran) from another (for example, COBOL), without needing to know the implementation details of the target language. OpenVMS itself is implemented in a variety of different languages and the common language environment and calling standard supports freely mixing these languages. DEC created a tool named the Structure Definition Language (SDL), which allowed data type definitions to be generated for different languages from

1449-447: Is that most of the operating system's core data structures can be read from executive mode, but require kernel mode to be written to. Code running at executive mode can switch to kernel mode at will, meaning that the barrier between the kernel and executive modes is intended as a safeguard against accidental corruption as opposed to a security mechanism. The Kernel comprises the operating system's core data structures (e.g. page tables,

SECTION 20

#1732775872784

1518-529: Is the DIGITAL Command Language , although other options are available. Unlike Unix shells , which typically run in their own isolated process and behave like any other user-mode program, OpenVMS CLIs are an optional component of a process, which exist alongside any executable image which that process may run. Whereas a Unix shell will typically run executables by creating a separate process using fork-exec , an OpenVMS CLI will typically load

1587-549: Is tightly integrated into VMS, allowing remote logins, as well as transparent access to files, printers and other resources on VMS systems over a network. VAX/VMS V1.0 featured support for DECnet Phase II, and modern versions of VMS support both the traditional Phase IV DECnet protocol, as well as the OSI-compatible Phase V (also known as DECnet-Plus ). Support for TCP/IP is provided by the optional TCP/IP Services for OpenVMS layered product (originally known as

1656-440: The $ CMEXEC and $ CMKRNL system services, respectively. This allows code outside of system space to have direct access to the Executive's routines and system services. In addition to allowing third-party extensions to the operating system, Privileged Images are used by core operating system utilities to manipulate operating system data structures through undocumented interfaces. The typical user and application interface into

1725-592: The Apple Macintosh to serve as a terminal for VMS systems, or to use VMS systems as a file or print server. PATHWORKS was later renamed to Advanced Server for OpenVMS , and was eventually replaced with a VMS port of Samba at the time of the Itanium port. DEC provided the Local Area Transport (LAT) protocol which allowed remote terminals and printers to be attached to a VMS system through

1794-626: The KA650 CPU module. The MicroVAX 3300 and MicroVAX 3400, code-named Mayfair II , were entry-level to mid-range server computers introduced on 19 October 1988 intended to compete with the IBM AS/400 . They used the KA640 CPU module. The MicroVAX 3800 and MicroVAX 3900 , code-named Mayfair III , were introduced in April 1989. They were high-end models in the MicroVAX family, replacing

1863-461: The VAX 4000 . Many members of the MicroVAX family had corresponding VAXstation variants, which primarily differ by the addition of graphics hardware. The MicroVAX family supports Digital's VMS , ULTRIX and VAXELN operating systems. Prior to VMS V5.0, MicroVAX hardware required a dedicated version of VMS named MicroVMS . The MicroVAX I , code-named Seahorse , introduced in October 1984,

1932-755: The VMS/ULTRIX Connection , then as the ULTRIX Communications Extensions or UCX). TCP/IP Services is based on a port of the BSD network stack to OpenVMS, along with support for common protocols such as SSH , DHCP , FTP and SMTP . DEC sold a software package named PATHWORKS (originally known as the Personal Computer Systems Architecture or PCSA) which allowed personal computers running MS-DOS , Microsoft Windows or OS/2 , or

2001-573: The file system is the Record Management Services (RMS), although applications can interface directly with the underlying file system through the QIO system services. The file systems supported by VMS are referred to as the Files-11 On-Disk Structures (ODS), the most significant of which are ODS-2 and ODS-5 . VMS is also capable of accessing files on ISO 9660 CD-ROMs and magnetic tape with ANSI tape labels . Files-11

2070-522: The 1990s and 2000s, there were approximately half a million VMS systems in operation worldwide. It was first announced by Digital Equipment Corporation (DEC) as VAX/VMS ( Virtual Address eXtension/Virtual Memory System ) alongside the VAX-11/780 minicomputer in 1977. OpenVMS has subsequently been ported to run on DEC Alpha systems, the Itanium -based HPE Integrity Servers , and select x86-64 hardware and hypervisors . Since 2014, OpenVMS

2139-511: The 2 KB direct-mapped virtual instruction cache (VIC) and the 512-entry by 4-bit branch history table. The I-box aimed to fetch eight bytes of instruction data from the VIC during every cycle. The E-box executes most non-floating-point instructions. It is controlled by microcode from a 1,600-word control store with the capability to patch 20 words. The F-box executes floating-point instructions as well as 32-bit integer multiply instructions. It has

NVAX - Misplaced Pages Continue

2208-651: The Alpha architecture in favour of adopting the then-new Itanium architecture. The porting began in late 2001, and the first boot on took place on January 31, 2003. The first boot consisted of booting a minimal system configuration on a HP i2000 workstation, logging in as the SYSTEM user, and running the DIRECTORY command. The Itanium port of OpenVMS supports specific models and configurations of HPE Integrity Servers . The Itanium releases were originally named HP OpenVMS Industry Standard 64 for Integrity Servers , although

2277-725: The CPU module via the backplane through the C and D rows and a 50-conductor ribbon cable. The backplane served as the address bus and the ribbon cable as the data bus. The MicroVAX II came in three models of enclosure: The Robotron K 1820 is a copy of the MicroVAX II developed in the GDR and was produced for a short period of time in 1990. KA620 referred to a single-board MicroVAX II designed for automatic test equipment and manufacturing applications which only ran DEC's real-time VAXELN operating system. A KA620 with 1 MB of memory bundled with

2346-521: The DEC native Unix operating system. At least one non-DEC commercial operating system was available, BSD Unix from mt Xinu . It used the KA630-AA CPU module, a quad-height Q22-Bus module, which featured a MicroVAX 78032 microprocessor and a MicroVAX 78132 floating-point coprocessor operating at 5 MHz (200 ns cycle time). Two gate arrays on the module implemented the external interface for

2415-510: The I/O database and scheduling data), and the routines which operate on these structures. The Kernel is typically described as having three major subsystems: I/O, Process and Time Management, Memory Management. In addition, other functionality such as logical name management, synchronization and system service dispatch are implemented inside the Kernel. OpenVMS allows user-mode code with suitable privileges to switch to executive or kernel mode using

2484-472: The MicroVAX 3500 and MicroVAX 3600, and were intended to compete with the IBM AS/400 . At introduction, the starting price of the MicroVAX 3800 was US$ 81,000 and that of the MicroVAX 3900 was US$ 120,200. A variant of the MicroVAX 3800, the rtVAX 3800, was intended for real-time computing (RTC) applications such as computer-aided manufacturing (CAM). These systems used the KA655 CPU module, which contained

2553-646: The V3.0 release, all compatibility-mode utilities were replaced with native implementations. In VAX/VMS V4.0, RSX AME was removed from the base system, and replaced with an optional layered product named VAX-11 RSX . A number of distributions of VAX/VMS were created: With the V5.0 release in April 1988, DEC began to refer to VAX/VMS as simply VMS in its documentation. In July 1992, DEC renamed VAX/VMS to OpenVMS as an indication of its support of open systems industry standards such as POSIX and Unix compatibility, and to drop

2622-588: The V9.1 Field Test, making it available to VSI's customers and partners. V9.1 shipped as an ISO image which can be installed onto a variety of hypervisors, and onto HPE ProLiant DL380 servers starting with the V9.1-A release. During the 1980s, the MICA operating system for the PRISM architecture was intended to be the eventual successor to VMS. MICA was designed to maintain backwards compatibility with VMS applications while also supporting Ultrix applications on top of

2691-402: The VAX architecture, including: These VAX architecture mechanisms are implemented on Alpha, Itanium and x86-64 by either mapping to corresponding hardware mechanisms on those architectures, or through emulation (via PALcode on Alpha, or in software on Itanium and x86-64). The OpenVMS Executive comprises the privileged code and data structures which reside in the system space. The Executive

2760-813: The VAX connection since a migration to a different architecture was underway. The OpenVMS name was first used with the OpenVMS AXP V1.0 release in November 1992. DEC began using the OpenVMS VAX name with the V6.0 release in June 1993. During the 1980s, DEC planned to replace the VAX platform and the VMS operating system with the PRISM architecture and the MICA operating system. When these projects were cancelled in 1988,

2829-582: The VAXELN Run-Time Package 2.3 was priced at US$ 5,000. Mira referred to a fault-tolerant configuration of the MicroVAX II developed by DEC's European Centre for Special Systems located in Annecy in France. The system consisted of two MicroVAX 78032 microprocessors, an active and standby microprocessor in a single box, connected by Ethernet and controlled by a software switch. When a fault

NVAX - Misplaced Pages Continue

2898-492: The changes included using the Extensible Firmware Interface (EFI) to boot the operating system, reimplementing the functionality previously provided by Alpha PALcode inside the kernel, using new executable file formats ( Executable and Linkable Format and DWARF ), and adopting IEEE 754 as the default floating point format. As with the VAX to Alpha port, a binary translator for Alpha to Itanium

2967-595: The changes needed to decouple VMS from the VAX architecture included the creation of the MACRO-32 compiler, which treated VAX MACRO as a high-level language , and compiled it to Alpha object code , and the emulation of certain low-level details of the VAX architecture in PALcode , such as interrupt handling and atomic queue instructions. The VMS port to Alpha resulted in the creation of two separate codebases: one for VAX , and another for Alpha. The Alpha code library

3036-407: The establishment of the company, as well as the development of VSI's own Itanium and Alpha releases of OpenVMS V8.4-x. The x86-64 port is targeted for specific servers from HPE and Dell , as well as certain virtual machine hypervisors . Initial support was targeted for KVM and VirtualBox . Support for VMware was announced in 2020, and Hyper-V is being explored as a future target. In 2021,

3105-430: The executable image into the same process, transfer control to the image, and ensure that control is transferred back to CLI once the image has exited and that the process is returned to its original state. Because the CLI is loaded into the same address space as user code, and the CLI is responsible for invoking image activation and image rundown, the CLI is mapped into the process address space at supervisor access mode,

3174-531: The four privilege levels of OpenVMS in software since only two of x86-64's privilege levels are usable by OpenVMS. The first boot was announced on May 14, 2019. This involved booting OpenVMS on VirtualBox, and successfully running the DIRECTORY command. In May 2020, the V9.0 Early Adopter's Kit release was made available to a small number of customers. This consisted of the OpenVMS operating system running in

3243-549: The higher end complement of the MicroVAX family. These new machines featured more than three times the performance of the MicroVAX II and supported 32 MB of ECC main memory (twice that of the MicroVAX II). The performance improvements over the MicroVAX II resulted from the increased clock rate of the CVAX chip set, which operated at 11.11 MHz (90 ns cycle time) along with a two-level, write-through caching architecture. It used

3312-611: The lack of Q-Bus or any expansion bus. The system could have a Shugart -based harddrive with ST412 interface and MFM encoding and had a built in 5.25-inch floppy drive (named RX33 in DEC jargon) for software distribution and backup. Supported operating systems were VMS and ULTRIX. It was packaged in a desktop form factor. The MicroVAX 3100 Series was introduced in 1987. These systems were all packaged in desktop enclosures. The MicroVAX 3500 and MicroVAX 3600, code-named Mayfair , were introduced in September 1987 and were meant to be

3381-597: The microprocessor, Q22-bus interface and the scatter-gather map for DMA transfers over the Q22-Bus. The module also contained 1 MB of memory, an interval timer, two ROMs for the boot and diagnostic facility, a DZ console serial line unit and a time-of-year clock. A 50-pin connector for a ribbon cable near the top left corner of the module provided the means by which more memory was added to the system. The MicroVAX II supported 1 to 16 MB of memory through zero, one or two memory expansion modules. The MS630 memory expansion module

3450-851: The name of several of the system libraries, including STARLET.OLB and STARLET.MLB . VMS was mostly written in VAX MACRO with some components written in BLISS . One of the original goals for VMS was backward compatibility with DEC's existing RSX-11M operating system. Prior to the V3.0 release, VAX/VMS included a compatibility layer named the RSX Application Migration Executive (RSX AME), which allowed user-mode RSX-11M software to be run unmodified on top of VMS. The RSX AME played an important role on early versions of VAX/VMS, which used certain RSX-11M user-mode utilities before native VAX versions had been developed. By

3519-487: The names OpenVMS I64 or OpenVMS for Integrity Servers are more commonly used. The Itanium port was accomplished using source code maintained in common within the OpenVMS Alpha source code library, with the addition of conditional code and additional modules where changes specific to Itanium were required. This required certain architectural dependencies of OpenVMS to be replaced, or emulated in software. Some of

SECTION 50

#1732775872784

3588-538: The pre-production quality releases of OpenVMS AXP confused some customers, and was not repeated in the subsequent ports of OpenVMS to new platforms. When VMS was ported to Alpha, it was initially left as a 32-bit only operating system. This was done to ensure backwards compatibility with software written for the 32-bit VAX. 64-bit addressing was first added for Alpha in the V7.0 release. In order to allow 64-bit code to interoperate with older 32-bit code, OpenVMS does not create

3657-681: The primary command language interpreter (CLI) of OpenVMS since the first release. Other official CLIs available for VMS include the RSX-11 Monitor Console Routine (MCR) (VAX only), and various Unix shells . DEC provided tools for creating text-based user interface applications – the Form Management System (FMS) and Terminal Data Management System (TDMS), later succeeded by DECforms . A lower level interface named Screen Management Services (SMG$ ), comparable to Unix curses , also exists. Over

3726-401: The resulting systems in November 1992. The NVAX was offered at a variety of clock speeds, 83.3 MHz (12 ns), 71 MHz (14 ns) and 62.5 MHz (16 ns), while the NVAX+ is clocked at a frequency of 90.9 MHz (11 ns). The NVAX offered about 25 VAX Unit of Performance (VUPs), while the NVAX+ was roughly 35 VUPs. This was only slightly less than the VAX 9000 mainframe's roughly 40 VUPs, but available in

3795-613: The same kernel. MICA was ultimately cancelled along with the rest of the PRISM platform, leading Dave Cutler to leave DEC for Microsoft. At Microsoft, Cutler led the creation of the Windows NT operating system, which was heavily inspired by the architecture of MICA. As a result, VMS is considered an ancestor of Windows NT , together with RSX-11 , VAXELN and MICA, and many similarities exist between VMS and NT. A now-defunct project named FreeVMS attempted to develop an open-source operating system following VMS conventions. FreeVMS

3864-413: The x86-64 port was demonstrated running on an Intel Atom -based single-board computer . As with the Alpha and Itanium ports, the x86-64 port made some changes to simplify porting and supporting OpenVMS on the new platform including: replacing the proprietary GEM compiler backend used by the VMS compilers with LLVM , changing the boot process so that OpenVMS is booted from a memory disk, and simulating

3933-526: Was OpenVMS Galaxy , which allowed the partitioning of a single SMP server to run multiple instances of OpenVMS. Galaxy supported dynamic resource allocation to running partitions, and the ability to share memory between partitions. In 2001, prior to its acquisition by Hewlett-Packard , Compaq announced the port of OpenVMS to the Intel Itanium architecture. The Itanium port was the result of Compaq's decision to discontinue future development of

4002-483: Was a 431-pin array. These were identical to those on the Alpha, allowing an NVAX+ machine to be upgraded to an Alpha simply by changing the CPU. These changes also allowed it to operate with slightly higher performance, and the NVAX+ ran at roughly 35 VUPs. This was only slightly less than the VAX 9000 mainframe's roughly 40 VUPs. In 1994, the NVAX++ (also known as NV5) was introduced in VAX 7000 Model 7x0 and VAX 10000 Model 7x0 systems. It operated at 133 MHz (7.5 ns) and

4071-458: Was a low-cost MicroVAX introduced on 10 February 1987. In January 1987, the MicroVAX 2000 was the first VAX system targeted at both universities and VAX programmers who wanted to work from remote locations. The MicroVAX 2000 used the same microprocessor and floating-point coprocessor as the MicroVAX II, but was feature reduced in order to lower the cost. Limitations were a reduced maximum memory capacity, 14 MB versus 16 MB in MicroVAX II systems and

4140-413: Was based on a snapshot of the VAX/VMS code base circa V5.4-2. 1992 saw the release of the first version of OpenVMS for Alpha AXP systems, designated OpenVMS AXP V1.0 . In 1994, with the release of OpenVMS V6.1, feature (and version number) parity between the VAX and Alpha variants was achieved; this was the so-called Functional Equivalence release. The decision to use the 1.x version numbering stream for

4209-543: Was built on top of the L4 microkernel and supported the x86-64 architecture. Prior work investigating the implementation of VMS using a microkernel-based architecture had previously been undertaken as a prototyping exercise by DEC employees with assistance from Carnegie Mellon University using the Mach 3.0 microkernel ported to VAXstation 3100 hardware, adopting a multiserver architectural model. The OpenVMS operating system has

SECTION 60

#1732775872784

4278-472: Was detected in the active microprocessor, the workload was switched over to the standby microprocessor. A MicroVAX II in BA213 enclosure. BA23- or BA123-enclosure MicroVAX upgraded with KA650 CPU module containing a CVAX chip set. BA23- or BA123-enclosure MicroVAX upgraded with KA655 CPU module. BA23- or BA123-enclosure MicroVAX upgraded with KA660 CPU module. The MicroVAX 2000 , code-named TeamMate ,

4347-563: Was fabricated in Digital's fifth-generation CMOS process, CMOS-5, a 0.50 μm process. It improved performance to 50 VUPs. In 1996, a 170.9 MHz NV5 was introduced, used in the VAX 7000/10000 Model 8x0. The NVAX is partitioned into five semi-autonomous units, the I-box, E-box, F-box, M-box and C-box. The NVAX is macropipelined. Multiple VAX macroinstructions are processed in parallel by autonomous units, which have their own micropipelines. The I-box fetches and decodes VAX instructions. It also contains

4416-509: Was implemented on two quad-height Q-bus cards - a Data Path Module (DAP) and Memory Controller (MCT). The MicroVAX I used Q-bus memory cards, which limited the maximum memory to 4MiB. The performance of the MicroVAX I was rated at 0.3 VUPs , equivalent to the earlier VAX-11/730 . The MicroVAX II , code-named Mayflower , was a mid-range MicroVAX introduced in May 1985 and shipped shortly thereafter. It ran VAX/VMS or, alternatively, ULTRIX ,

4485-708: Was made available, allowing user-mode OpenVMS Alpha software to be ported to Itanium in situations where it was not possible to recompile the source code. This translator is known as the Alpha Environment Software Translator (AEST), and it also supported translating VAX executables which had already been translated with VEST. Two pre-production releases, OpenVMS I64 V8.0 and V8.1, were available on June 30, 2003, and on December 18, 2003. These releases were intended for HP organizations and third-party vendors involved with porting software packages to OpenVMS I64. The first production release, V8.2,

4554-523: Was one of DEC's first VAX computers to use very-large-scale integration (VLSI) technology. The KA610 CPU module (also known as the KD32 ) contained two custom chips which implemented the ALU and FPU while TTL chips were used for everything else. Two variants of the floating point chips were supported, with the chips differing by the type of floating point instructions supported, F and G, or F and D. The system

4623-630: Was originally designed to be used and managed interactively using DEC's text-based video terminals such as the VT100 , or hardcopy terminals such as the DECwriter series. Since the introduction of the VAXstation line in 1984, VMS has optionally supported graphical user interfaces for use with workstations or X terminals such as the VT1000 series. The DIGITAL Command Language (DCL) has served as

4692-480: Was released in February 2005. V8.2 was also released for Alpha; subsequent V8.x releases of OpenVMS have maintained feature parity between the Alpha and Itanium architectures. When VMS Software Inc. (VSI) announced that they had secured the rights to develop the OpenVMS operating system from HP, they also announced their intention to port OpenVMS to the x86-64 architecture. The porting effort ran concurrently with

4761-507: Was used for expanding memory capacity. Four variants of the MS630 existed: the 1 MB MS630-AA , 2 MB MS630-BA , 4 MB MS630-BB and the 8MB MS630-CA . The MS630-AA was a dual-height module, whereas the MS630-BA, MS630-BB and MS630-CA were quad-height modules. These modules used 256 Kb DRAMs and were protected by byte-parity, with the parity logic located on the module. The modules connected to

#783216