| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 147.1 | Alpha CHIP & ARCHITECTURE announcement. | KERNEL::TRAVELL | John T, UK_Remote_Services_Support | Tue Feb 25 1992 20:52 | 762 |
| Well, ARA as a label did not last long....
We have announced the CHIP and ARCHITECTURE, today's PRESS release follows.
February 25, 1992
DIGITAL ANNOUNCES THE WORLD'S FASTEST MICROPROCESSOR
...New Alpha open computing architecture and new business
practices lead way into 21st century computing
Digital Equipment Corporation today unveiled the world's fastest
microprocessor, code-named Alpha, marking a breakthrough in open
chip architecture. The new generation of computer technology was
revealed to European journalists at Digital's $200 million
state-of-the-art facility at South Queensferry, Scotland, one of
two plants worldwide which will manufacture the chip.
"Alpha is a totally new, open computing environment that will give
users the benefits of advanced 21st century computing," said Pier
Carlo Falotti, President of Digital Europe. "It will create a new
industry standard - one which supports multiple operating systems
and will increase in performance by a factor of 1,000 over its
anticipated 25-year life".
The new, open architecture will form the 'heart' of systems that
span from the palmtop to the supercomputer. Users will have the
flexibility to deploy current applications on popular operating
environments at peak performance, beginning with OSF/1 and VMS.
Digital also announced that it planned to license the Alpha
architecture to other semiconductor manufacturers, and actively
market the Alpha technology at all levels of integration - chip,
board, and system.
ALPHA - A BREAKTHROUGH IN CHIP TECHNOLOGY
The first product which results from the Alpha programme will be
Digital's 21064 RISC microprocessor. The 64-bit chip has up to
four billion times more address space than 32-bit implementations
from IBM, Hewlett Packard, and Sun. Its clock speed is twice as
fast as any competitor, roughly the same peak performance as a
Cray-1 supercomputer for the cost of today's workstation. It is
priced at $3375 each in units of 1 to 100; $1650 in units of 101
to 1,000; and $1559 for over 1,000.
Alpha's delivery of affordable supercomputing power to the desktop
will open a whole new area of power-hungry applications once
handled only by supercomputers or large mainframes. Seismic data
analysis, financial closing, molecular modelling, engineering
design and many others will be able to run on Alpha at a fraction
of today's mainframe costs. Alpha's power will provide the colour
and graphics for emerging personal use applications that are
straining the limits of today's PCs, such as voice and video,
visualisation systems, imaging, and artificial intelligence.
"Alpha places Digital ahead, not only of current high-end chips
from our competitors, but of their next generation as well. The
beauty of the technology is that users will have the freedom to
choose the best applications today in the knowledge that all their
existing investments, will be protected," said Peter Graham, Alpha
Business Manager.
NEW OPEN BUSINESS PRACTICES
With Alpha set to become the new standard in computing, Digital
will license the new technology to third party vendors. Cray
Research Inc. has already announced that Alpha will form the basis
of its first-generation massively parallel processor
supercomputer, and Kubota Inc. will use the chip in its
high-performance graphics workstation, available in late 1992.
"The Alpha chip delivers leading edge single-chip functionality
and performance,' said Cray Research Chairman, John Rollwagen, at
the time of its announcement.
Digital is offering a comprehensive support programme to help
companies migrate their applications to Digital's Alpha platform.
Extensive porting activities are already underway with many
application software vendors. Over the next months, Digital will
announce additional alliances and partnerships that will highlight
third-party Alpha support.
Such alliances and partnerships will ensure the broadest use of
the architecture with the widest possible range of operating
environments. The company will partner with software vendors and
provide an extensive portfolio of applications on Alpha, and
license its operating systems (including DEC OSF/1 and VMS),
compilers, and layered software products.
"Licensing Alpha is in line with Digital's committment to deliver
the Open Advantage", said Falotti. "It will accelerate Alpha's
acceptance as a new industry standard, which in turn will generate
revenue for applications developers and broaden the range of
products available. Thus third parties have a stake in Digital's
future, and vice versa, and the ultimate beneficiary of this open
approach is the customer".
COMPLETE CUSTOMER AND OEM SUPPORT FOR ALPHA
Customers will continue to buy leading UNIX and VMS systems from
Digital knowing that they have a clear migration path to 21st
century computing. Digital will support Alpha customers and
vendors with services ranging from consulting to education and
training, client/server systems management, product design, and
integration and migration services - all designed to make users
successful in planning, designing, implementing, and managing new
Alpha computing environments.
Concluded Falotti:"Alpha is the distillation of expertise Digital
has gained from 35 years of innovative architectural design and
chip technology. With its unsurpassed power and ability to run
different operating systems, Alpha is one of the most significant
advances in the computer industry for many years.
"In the next five years only a handful of computer manufacturers
will be able to design and build microprocessors, and enjoy the
inherent advantage in performance and time to market. The rest
will use off-the-shelf components and will compete on the basis of
services. With Alpha, Digital will be one of those few, and first
among equals".
-ends-
ALPHA AT A GLANCE
The Alpha programme consists of two elements:
> the first 21st century computing architecture - a totally new,
64-bit reduced instruction set computing (RISC) architecture
designed to be fast, reliable and open.
> a single chip implementation of this new architecture. The 21064
chip has double the clock speed and up to four billion times
more address space than competitors' 32-bit implementations,
with roughly the same peak performance as a Cray-1
supercomputer.
Why is Alpha an industry first ?
Alpha is the first microprocessor architecture to combine the
following:
> it is designed to be scalable by over 1,000 times over its
25-year lifetime to meet user demands for more power.
> its open technology is able to run multiple operating systems.
> its design supports both single processor and massively
parallel systems.
> it will be licensed at every level of integration - chip, board
and system: the most compelling example of open business
practices to date.
> it will be implemented in successive generations of 64-bit
microprocessors spanning from palmtop to supercomputer.
ALPHA KEY FACTS
Open Advantage
> Alpha is another proof of Digital's committment to openness as
embodied in its Open Advantage. The chip will create a new
industry standard and is a world first - a full RISC
implementation with no operating system or language bias.
> Alpha is the first microprocessor with the ability to run
different operating systems. It is capable of running not just
VMS software but also OSF/1 and a dozen other operating systems
and languages.
> The OSF/1 operating system can be run on Alpha, MIPS and Intel
platforms, offering varying price points and performance to
customers. OSF/1 and Open VMS will be the first operating
systems available on Alpha.
Open Business Practices
> Digital has lead the way in formulating standards, licensing
software, supporting other vendors' equipment and applications,
and working closely with third parties.
> In line with a set of open business practices, Digital will now
license the new technology to third party vendors. Cray Research
- the world's leading supercomputing manufacturer - has already
announced its choice of Alpha for its first-generation massively
parallel processing system.
> Digital will license Alpha at all levels of integration - chip,
board and system - to other computer companies and to original
equipment manufacturers. Such alliances will ensure the
broadest use of the architecture with the widest possible range
of operating environments, and guarantee that it will reach the
market at the most attractive price.
> Digital will partner with software vendors and application
developers to deliver a broad portfolio of applications, and
license its operating systems (including DEC OSF/1 and VMS),
compilers, and layered software products.
Outstanding performance
> Alpha is the world's fastest single chip microprocessor, and the
first 64-bit RISC chip from a major computer vendor. Alpha runs
at twice the speed of HP's latest chip, and is thousands of
times more cost-effective than IBM's mainframes. Digital
believes it will outlive, outscale and outperform all current
architectures in the industry.
> The Alpha architecture will form the heart of Digital's strategy
for 21st century computing, going beyond the current RISC curve.
Its 64-bit technology has 4 billion times the address space of a
32-bit system, and should last at least 25 years.
> It represents the industry's first ever simultaneous leap
forward in power, size, compatibility and industry standards.
> Alpha will deliver all the power of a Cray-1 supercomputer for
the price of a workstation, able to run power-hungry
applications at a fraction of today's mainframe costs. Over the
next 25 years it will scale up to 1,000 times, perhaps even
10,000 times, as user demands increase.
> Alpha systems will be industry-leading in price/performance and
performance, providing the assurance that users will never have
to upgrade again in their career lifetime.
More choice
> The Alpha architecture will complement Digital's support of
other industry standards, including the ACE initiative. OSF/1 on
Alpha will be compatible with OSF/1 on ACE.
> Products coming out of the Alpha programme will coexist with -
not replace - Digital's current product range of VAX and UNIX
systems.
> Alpha powerfully underlines Digital's operating philosophy: one
architecture scalable from palmtop to mainframe, from the
simplest of invoicing tasks to the most complex of scientific
challenges.
Investment Protection
> Digital will continue to protect its customers' investments in
IT. Alpha's open architecture and system design provides a
clear migration path, giving investment protection for data,
applications, interfaces and peripherals.
> Digital's eight million VAX customers, running over 8,000
applications, have a clear upgrade path into the 21st century
with minimum inconvenience.
> Migrating applications to OSF/1 and VMS on ALPHA is easy. All
OSF/1 and VAX/VMS users can port and run the same software with
the same data storage applications.
Enabling Technology
> Alpha is an enabling technology; it is the 'engine' that will
drive applications and solutions that were previously
unachievable or too costly.
> The Alpha microprocessor is a new generation of technology which
will open new opportunities for interacting with computers at
work and home, up to and well beyond the year 2000.
> Alpha's power will provide the colour and graphics for emerging
personal use applications that are straining the limits of
today's PCs, such as voice and video, visualisation systems and
imaging.
Made in Europe
> Alpha will be manufactured both in Hudson (Massachusetts) and
at the South Queensferry plant in Scotland from spring 1992.
> Digital is the only company with this type of manufacturing
capability in Europe. It has invested an extra $54 million to be
able to produce the Alpha chip in South Queensferry on top of
its $137 million in the plant to date.
Complete support
> Digital is offering a comprehensive support programme to help
companies migrate any vendor's applications to Alpha. Extensive
porting activities are already underway with many application
software vendors.
> Digital's full range of support services include consulting,
education and training, client/server systems management, and
integration and migration services. All are designed to make
users successful in planning, designing, implementing, and
managing new Alpha computing environments.
> Digital will support vendors during product design,
implementation, and subsequent marketing. Digital can also
become the service provider for the vendor's Alpha-based
products through different distribution channels, OEMs, VARs, or
direct.
> The first of 30 Alpha Upgrade Centres have already been
established in the USA, Europe and the Asia Rim, staffed by
software support personnel with expertise in VMS, ULTRIX and DEC
OSF/1.
ANALYST OPINION OF ALPHA
"In the constant 'leapfrog' race Digital has definitely taken a
giant step ahead of the competition with Alpha. The R&D costs of
developing a new chip architecture are incredibly high, out of
reach of many smaller vendors. This chip offers them a broad based
technology with operating systems that are generally available,
which makes it very attractive. Alpha will also provide the very
high power required for countless multimedia applications for the
next several generations."
Lars Mieritz, Technology Investment Strategies Corporation Ltd
(UK)
"Alpha represents a new performance generation, both in terms of
the type of chip it is and the very high speeds at which Digital
will run the chip. It is definitely the most powerful chip
available in the whole world today. At the same time, Digital is
entering the market as an original equipment manufacturer (OEM)
chip supplier, and will be able to extend its external industry
importance by making the chips available to other companies. If
the Alpha programme continues to develop partnerships such as that
with Cray Research, Digital will re-assert itself as a full range
supplier and win back its reputation for being a leading edge
component designer."
Martin Hingley, International Data Corporation (UK)
"Alpha breaks new ground in chip design. This technology should
place Digital in front of Sun and HP's current high-end chips and
in front of their next generation as well."
Harry William, Sanford C. Bernstein (US)
"If the figures are correct, Digital has moved in one year from
last to first in hardware technology".
Marc Schulman, UBS Securities (US)
ALPHA - A 21ST CENTURY COMPUTING ARCHITECTURE
Key to every computing solution is a set of rules about how data
is addressed and instructions are handled. It's called a
"computing architecture".
To the extent that a computing architecture is robust and
long-lived-spanning a large range of systems, many kinds of
applications, and multiple generations of technology - it delivers
important benefits: Transitions to new systems and new
technologies are smooth and non-disruptive; Investments in
hardware, software, and data are protected; Operational and
support requirements are simplified and the overall cost of
ownership is lowered.
DOES THE WORLD NEED ANOTHER COMPUTING ARCHITECTURE ?
Thirty years of computing have shown that today's mainframe is
tomorrow's notebook. Customers need a range of computing solutions
to address variously "sized" problems. A computing architecture
that does not scale well across a broader range of systems is soon
limited in its usefulness. At a minimum, an architecture for the
21st century must be able, from the beginning, to be implemented
on a single chip on the low end - and to support a very large,
even massively parallel multiprocessing system on the high end.
While systems based on both CISC and RISC 32-bit architectures
will continue to deliver leading-edge performance for years to
come, they will not be able to keep pace with improvements in
memory technology to meet the demands of the "supercomputing-like"
applications of the 21st century, such as visualization, very
large databases, imaging, multimedia, simulation and modelling.
Quite simply, the 32-bit systems are going to run out of address
space.
64-BIT ARCHITECTURE
The answer will be a computing architecture which will be a
full-speed 64-bit computing architecture. The development of this
technology will open a whole new area of applications for
computers. The last ten years have seen tremedous growth in demand
for power from CAD/CAM and simulation packages, massive databases,
multimedia, electronic publishing systems, econometric modelling
software, and so on. All of these packages have increasingly used
memory-hungry colour and graphics to improve their user
interfaces.
Moving from a 32-bit to 64-bit architecture should provide a
comfortable 50 years of growth. The move from a 32-bit to 64-bit
is not just a doubling, it provides four billion times the address
space - and the architectural underpinnings and performance to
last 25 years.
A 25 YEAR DESIGN HORIZON
Over the last ten years, computing performance has improved by a
factor of 100. Given the ever-accelerating rate of technical
advancement and demand for performance, it is very likely that a
25-year architecture will need to be scalable by a factor of
1,000.
This means that a 21st century architecture must be able to take
advantage of performance improvements in all three dimensions of
performance: CPU clock speed, multi-issue instruction
(superscalar), and multiple processors, including massively
parallel processing.
For Digital's customers, the Alpha architecture will do just that.
It represents a simultaneous leap forward in power, size,
compatibility and industry standards. It combines supercomputing
levels of power with the ability to scale up by at least 1,000
times as user needs increase, and designed to be the 'heart' of
any size of machine from the palmtop to the supercomputer.
OPEN TECHNOLOGY
Perhaps the most dramatic change to come will be the idea of an
open computing architecture - one that can be implemented by many
different vendors at all levels of integration. Unlike all past
architectures, a computing architecture for the 21st century will
not be targeted for, nor show any bias towards, any particular
operating system, language, or style of computing.
As the computing industry moves into the 21st century, computer
vendors and users alike are experiencing both the benefits and the
necessities of 'multi-vendor' solutions. To be open, an
architecture must be designed to allow customers to mix and match
chips, systems, compilers, and software from multiple sources to
meet their needs.
Again, this 'openness' is built into the Alpha architecture. By
offering the OSF/1 operating system on Alpha, MIPS and Intel
platforms, users will have the choice of varying price points and
performance. Most applications can migrate to Alpha very easily,
and simply need to be recompiled into the Alpha code.
THE IMPACT OF MICROPROCESSOR TECHNOLOGY
One of the key competitive factors in the computer industry is
microprocessor technology. In the past few years, the power of the
microprocessor has soared, so much so that computers built using
multiple off-the-shelf microprocessors are competing with
traditional mainframes and supercomputers at a fraction of the
cost.
Microprocessors have set the entire industry on a trend towards
standard hardware platforms. But the cost of developing new
microchip technologies - and building a factory to make them - is
several hundred million dollars. It would cost $500 million to set
up South Queensferry today. By 1995, the entry bar will have been
raised to $1 billion.
Over the next five years this will cause a convergence on a few
microprocessor architectures. Only a handful of computer
manufacturers will be able to design and build their own. They
will enjoy an advantage in performance and time to market, while
other will use off-the-shelf components and will compete on the
basis of services.
In short, only those companies with control over their own
technological destinies will survive.
ALPHA - TECHNICAL CHARACTERISTICS
> Alpha is a multiple-instruction issue, pipelined, 64-bit,
load/store, reduced instruction set architecture.
> It's the world's fastest IEEE compatible floating point chip.
> It is a dual-instruction processor, meaning that it can handle
two instructions at once.
> It is a CMOS (Complimentary Metal Oxide Semiconductor) with 1.7m
of transistors. Minimum feature size is 0.75 microns, transistor
channel length is 0.5 microns and the chip operates at 3.3
volts.
> It handles 30 watts of power with 64-bit virtual and physical
addresses and 64-bit integers and floating points, with no
operating system or language bias and four billion times the
addressable space of existing chips.
> With clock rates of up to 200MHz, the chip is capable of
delivering 400 peak MIPs and 200 peak MFLOPS - over twice most
of Digital's competitors.
> With a total transistor count of 1.68 million devices, the chip
is a complete CPU, including full integer and floating-point
execution units. These units, together with related addressing
and branching units, are fully pipelined, and each is capable of
launching a new operation every cycle.
> The chip includes two high speed memory caches. An eight Kbyte
instruction cache provides two full 32-bit instructions per
clock cycle to the instruction dispatch unit, and an eight Kbyte
data cache can provide a 64-bit data access during each cycle.
The resulting cache bandwidth of 3.2 Gigabytes/second far
exceeds what could be accomplished if these cache units were not
fully integrated.
> Initially, Alpha systems will be able to run OSF/1 and VMS -
there is no bias towards a particular operating system or
programming language in the architecture.
ALPHA PERFORMANCE & COMPETITIVE POSITIONING
Vendor Digital MIPS Sun/TI IBM HP Intel Motorola
Device 21064 R4000 Viking RIOS PA-4 i860XP 88110
Max.Freq
Internal 200 Mhz 100 Mhz 50 Mhz 50 Mhz 66 Mhz 50 Mhz 50 Mhz
No.Chips
Required 1 1 1 7-9 2 1 1
Peak MIPS 400 100 150 200 132 150 150
Peak MFLOPS 200 50 50 100* 132* 100* 100
Base Arch
Design 64-bit 64-bit 32-bit 32-bit 32-bit 32-bit 32-bit
Samples
Available Now Now N/A N/A N/A Now Mid-1992
* = combined fmul/fadd
Editor's Notes:
> Digital's CMOS technology runs faster than any other
semiconductor manufacturer (including Intel, Motorola, IBM, TI,
Cypress, NEC and Toshiba). CMOS-4 is the fourth generation of
CMOS chip from Digital.
> Previous CMOS generations have delivered the world's fastest
CISC microprocessors into Digital's products (for example VAX
6000 Model 500 with CMOS-3 chips operating at 62.5 MHz in 1990).
> CMOS-4 continues this world leading position in the VAX 6000
Model 600 with the 83MHz chip. This same technology is used to
manufacture the Alpha CPU and a wide range of peripheral chips.
BUSINESS/INDUSTRY APPLICATIONS
Alpha will enable users to compete effectively on a global scale,
significantly reduce operational costs, communicate and trade with
other businesses at unprecedented speed and take advantage of
extensive information resources to create and thrive within new
markets.
The high performance of Alpha will act as a catalyst in the
development of new "intuitive" user interfaces and applications
which can keep pace with the speed of the working environment:
> Supercomputer Applications
Until recently, supercomputers had been confined to the
laboratories of the scientific and research community. Today,
increasingly, they are found in a variety of commercial
applications - econometric forecasting, designing aircraft,
simulating car crashes, modelling molecular chains for drug
development, studying the stresses on artificial implants, and
many others.
Alpha will put the power required for these computer aided
design and engineering applications onto the desktop - at prices
equivalent to today's workstation. In essence, there will be a
paradigm shift from what was once only conceivable on a
supercomputer to a wide-ranging business environment.
> Voice Interactive Computing
Digital predicts that by 1995 users will be able to talk to -
and be understood by - their computers. This could mark the
beginning of the end for the keyboard. DIDDLY*, for example, is
a commercial system developed by Digital which enables the user
to give commands by voice - and to hear the computer talk back.
Hospital operating theatres are already testing its ability to
allow surgeons to call up a variety of data while operating.
Other potential applications could include voice interactive
navigation between a pilot and the control tower computer, route
finders for cars and buses, and television shopping for the home
user. The list is endless.
* Digital Integrated Distributed Data Library
> Multimedia and Video Communications
The ability to combine image, text, graphics and voice on the
desktop is one ideally suited to Alpha's cost-effective
performance. Jabberwocky is a prototype system from Digital that
combines phone, computer and video systems to provide such
applications as 'video-conferencing' and 'video mail.' With
Alpha, users will be able to communicate on-line with clear and
instaneous video transmission, while exchanging text and
graphics.
> "Active Badges"
"Active Badges" systems use infra red beams to track wearers
through a building. The badge's signal enables a central
computer system, or other colleagues, to keep track of their
wherabouts. Telephone calls can be transferred, security doors
opened and computers logged on and off automatically. Again,
Alpha will provide the cost-effective power to bring this
technology to the wider marketplace within the next few years.
> Virtual Reality
Virtual reality is the ability to experience the world of the
computer from "within." Estate agents for example, will be able
to "take" prospective buyers from room to room, getting a feel
for the condition and dimensions of a house for sale. For
training purposes, learner drivers will be able to go out on the
road without leaving the comfort of their home and in the world
of entertainment, who knows, users could get in a good round of
golf without even leaving the office !
> Pen Based Computing
Alpha will increase the power of systems that recognise
handwriting and freehand drawing instead of keyboard commands.
With Alpha, writing and graphics will be reproduced instantly
and not subject to current delay times. Furthermore, users will
be able to write or draw directly onto the screen instead of
onto a special tablet as used now.
ALPHA - DID YOU KNOW ?
> The Alpha chip, which is barely a quarter of an inch square,
contains nearly two million transistors.
> To make each individual transistor on an Alpha chip visible to
the naked eye, the chip would have to be enlarged to the size of
Switzerland.
> With a peak speed of 400 million instructions/second, the Alpha
chip can launch two instructions in the time it takes light to
travel across a room.
> A single Alpha chip has roughly the same peak performance as a
Cray-1 system, a small supercomputer.
> The power which Alpha provides on a single chip the size of a
fingernail would have occupied a large room as little as 10
years ago.
> In 1975 it took Concorde approx. 3 hours to fly from London to
Washington. If Concorde had achieved a comparable improvement in
speed as Digital has from its first VAX to today's Alpha, the
flight would take less than two minutes !
> By the year 2000, Digital predicts that 80 % of businesses in
Europe will be using Alpha technology in some shape or form.
SOUTH QUEENSFERRY - THE WORLD'S MOST
ADVANCED SEMICONDUCTOR PLANT
> The $200 million facility at South Queensferry - officially
opened in September 1990 - is one of the most advanced
semiconductor plants in the world and Digital's second largest
investment outside the USA to date.
> Digital is committed to the European market, which now accounts
for 40 % of the corporation's worldwide revenues.
> Digital is the only company with this type of manufacturing
capability in Europe, and the only computer manufacturer in the
UK able to work from the raw silicon, through design and
production, to the finished computer.
> Digital has invested over $50 million to prepare South
Queensferry for worldwide production of the Alpha chip, from
spring 1992.
> Digital's investment in South Queensferry has created 450 new
jobs. In the last year alone a record $6 million has been spent
on staff training.
> The wafers at South Queensferry are manufactured in a Class I
clean room, where the air is kept a thousand times cleaner than
an operating theatre and a million times cleaner than an
ordinary office. Working at one micron tolerances, the smallest
impurity - even a fleck of dust one hundredth the diametre of a
human hair - could short circuit the wafer.
> Each day, two hundred thousand gallons of water - one million
times cleaner than tap water - are used in the washing and
fabrication process.
> The air supply goes through a series of temperature controls and
filtration processes before being fed into the clean room. After
use, it is put through a scrubbing process and discharged - as
clean as when it came in.
....ooooOOOOoooo....
|
| 147.2 | ********* SO SOON ????? ************ | KERNEL::GARNETT | | Sat Oct 03 1992 09:24 | 237 |
| From: NAME: David Hessom
FUNC: Digital Services - UK PTG
TEL: DTN-833-3917 <HESSOM AT A1_KERNEL @THESUN @UVO>
To: See Below
CC: See Below
Hello All,
Attached is a PCO (prototype change order) for an ALPHA system called the
FLAMINGO.
The modules are in very short supply at the moment so I would appreciate you
not putting any orders in yet except for Welwyn who look after INSIGNIA.
Apparently this customer is writing some OSF code for DIGITAL so it is
important these get done first and this is in hand.
Please let me know A.S.A.P. (according to the list) how many sets of modules
you still need and I will work with John Minns @WLC to prioritise delivery as
modules come available.
Many regards,
David
Author: David Hessom
Date: 02-Oct-1992
Posted-date: 01-Oct-1992
Subject: Flamingo PCO Document.
FLAMINGO PCO (PROTOTYPE CHANGE ORDER)
=====================================
The prototype Flamingo systems which are available within most
countries in Europe do require a change of the CPU and I/O
module. Please find below a brief description of the problem
and the process to be followed. This message has been send to
the Country FCO coordinators and system owners. Existing FCO
channels will be used to execute this PCO.
PURPOSE:
=======
The Flamingo Prototype Program is implementing a PCO (preliminary
Change Order) to all prototypes containing revision levels lower than
54-21149-01--C07 and/or 54-21147-01--C07. The purpose of this PCO is
to fix a SCSI data miscompare and corruption problem discovered with
OSF software. In addition, we will be fixing a problem with the ISDN
transformer. All European systems requiring the PCO will be upgraded
via system and I/O module swaps. The Nijmegen Repair Center has been
provided with 10 sets of modules with which to begin a rolling upgrade
process.
PROCESS:
========
->Flamingo prototype machine owners request the service branch
responsible for your hardware to change the CPU and I/O module
(partnrs. 54-21149-01 and 54-21147-01).
->Branch to order this material on the Country Subsidiary, the
contact person is the country Logistics FCO coordinator
(see TO: distribution list from this memo).
->Country FCO coordinators order material on JGO and as soon as
material is available this will be shipped from Nijmegen.
->Upon receipt, material needs to be installed ASAP. After this
below rev. material needs to be returned immediately to the
subsidiary (it is very important that material is returned asap
as this needs to be used to upgrade other systems).
->Subsidiary to return material to JGO, additional material will
only be released after receipt of the defectives.
AFFECTED UNITS
==============
A list is attached, where and with whom we believe European (and some
GIA) systems requiring this PCO are located. If any of this
information is incorrect, or if you know of additional systems
requiring rework, please forward the information to Adrianna
Swartout@MLO
PRIORITY:
========
This PCO is MUCH MORE critical to OSF (rather than VMS) users and we
will be prioritizing orders based on operating system usage. Please
forward your operating system usage to myself and Peter Schoenmaker
(JGO::SCHOENMAKER) and it probably wouldn't hurt to include the
information when you call into your branch.
COST
====
Any cost associated with implementation of this PCO will be paid by the
Workstations PCU with a special PCO charge number. JGO will use normal
cost procedures. JGO will charge (low) repair charges to the Digital
Service Logistics Organization.
The Branch will charge system owners for the repair costs, and for
the costs of the call.
The system owner will be able to cross-charge the cost to the programm
cost-center:
CC: Y2Q Charge Number: E098-10685 Flamingo/Sandpiper PCOs -
rework, shipping and
labor,etc
If you (or your finance group) have any questions, they should contact
Peter Schoenmaker/Paul Mooren @JGO for details.
REVISION MATRIX:
===============
These are the currently used Firmware Baselevel Revisions on Flamingo.
As outlined in the table below, BL6 of the onboard Firmware is NOT
compatible with AVMS FT1/FT2 and OSF BL6
VMS OSF Firmware Base level (CPU &IO)
=======================================================
FT1/FT2 BL6 BL4.1 (JGO shipping level)
FT3 (NOT FT1/FT2) BL7 BL6
=======================================================
NOTE:
Do NOT update to Firmware BL6 unless you are using BL7 OSF or
FT3 VMS. This firmware will NOT work with FT2 VMS!!
Firmware release locations:
BL4.1 : LEDDEV::DISK$FLAMINGO:[FLAMINGO.RELEASE.BL4_1]
BL6 : LEDDEV::DISK$FLAMINGO:[FLAMINGO.RELEASE.BL6]
LIST OF SYSTEMS REQUIRING PCO
=============================
FLAMINGO
LOCATION: NUMBER SYSTEM OWNER
--------- ----------- ------------
JGO/NETHERLANDS 0255 PETER SCHOENMAKER
JGO/NETHERLANDS 0268 PETER SCHOENMAKER
JGO/NETHERLANDS 0302 PETER SCHOENMAKER
BRO/BELGIUM 0267 FELIX DANIELS
DMO/DENMARK 0263 SOREN CHRISTOFFERSEN
ILO/IRELAND 0193 JOHN GIBLIN
EVT/FRANCE 0298 BERNARD OURGHANLIAN
FNO/FINLAND 0265 PEKKA HEISKANEN
HEL/GREECE 0299 CHRIS TRIZOGLOU
** NWO/NORWAY 0159 MARTIN RINGEL DONE **
NWO/NORWAY 0253 ARVE VORKINN
HGO/HONG KONG 0507 FRANCIS NG
ISO/ISRAEL 0266 SHLOMO SNOPKOWSKI
ISO/ISRAEL 0348 SCHLOMO SNOPKOWSKI
EDO/SCOTLAND 0032 NIGEL HARRIS
EDO/SCOTLAND 0033 NIGEL HARRIS
INSIGNIA/ENGLAND 0203 JUSTIN KOPROWSKI
INSIGNIA/ENGLAND 0204 JUSTIN KOPROWSKI
INSIGNIA/ENGLAND 0205 JUSTIN KOPROWSKI
REO/ENGLAND 0196 JOHN KELL
REO2-F/F9-ENGLAND 0201 DONNA HUBBARD
** SBP/ENGLAND 0157 SIMON COLE DONE **
HIGHFIELD HOUSE/ENGLAND 0102 JULIAN ELLIS
KINEZLE/GERMANY 0181 RALF OHLHAUSEN
*** MUH/MUNICH 0134 THOMAS SIEBOLD
MUH/MUNICH 0156 JIM KLUMPP
*** RIO/ITALY 0303 BRUNO CIPOLLA
*** RIO/ITALY 0325 BRUNO CIPOLLA
SQO/SPAIN 0264 ANTONIO G-ORTIZ
THR/SWITZERLAND 0254 ROBERT INDERBITZI
UTO/NETHERLANDS 0286 RUUD PLATENKAMP
VBE/VALBONNE 0197 BRIAN MOTTERSHEAD
** VBO/VALBONNE 0160 PETE KAISER
MLO3-1 LAB//England(REO) 0036 BOB CLARK
JRD/JAPAN 0185 HIROYUKI KOMATSU
JRD/JAPAN 0444 KIROYUKI KOMATSU
JRD/JAPAN 0508 HIROYUKI KOMATSU
TRO/CHIBA, JAPAN 0331 SHUJI YAMAGUCHI
TRO/CHIBA, JAPAN 0332 SHUJI YAMAGUCHI
** Done
*** Because of failures, these systems have replaced (Italy)
or have been repaired with upgraded spares.
To Distribution List:
sue banfield @bso,
richard ellis @sbp,
neil maidment @sbp,
mike rhodes @bio,
mike sanderson @not,
colin houston @bvo,
janet blythe @ubo,
mervyn owen @ubo,
gerry lay @ubo,
ian dempsey @ubo,
john milton @eso,
terry woodjetts @eso,
trevor bromley @rkg,
barry wells @lzo,
graham carr @lzo,
janice johnson @hhl,
stephen tennant @edo,
paul walton @olo,
revcon @dbo,
dave bazley @wlo,
wayne walker @eso,
karen clifton @wlc,
alison codner @wlc,
_jockey::nkt_revcon AT A1_KERNEL @THESUN @UVO,
alan james @uvo,
nigel garnett @uvo,
andrew heydn @hhl,
steve blackett @rkg,
malcolm crozier @eda,
bill neilson @edo,
ed kennedy @hhl,
chris tadd @sbp,
mike smith @sbp
CC Distribution List:
john minns @wlc,
alan maskell @ubo
|
| 147.3 | More Alpha CBI's to look at... | KERNEL::TRAVELL | John T, UK_Remote_Services_Support | Thu Oct 08 1992 11:47 | 26 |
| After a little theft and hackery, I have a number of ALPHA related CBI's
working on the KERNEL cluster. It is possible these may move, but until they do
the command needed to invoke them is:-
$ CBI == "@RSWS$DISK:[BASINGSTOKE.CBI]CBI_SELECT.COM"
$ CBI
This brings up a menu :-
CBI selection menu, enter CBI name or index number.
1 Alpha_concepts
2 Futurebus
3 Turbochannel
4 Flamingo
5 Cobra
6 Laser
Select CBI to study (or <cr> to exit) -
i.e. choose a number...
Most of these CBI's are primarily aimed at teach hardware engineers how to
service the various platforms.
John Travell. 833-3020
|
| 147.4 | AXP Newsletter. | KERNEL::ADAMS | Brian Adams CSC-Viables '833-3026 | Wed Feb 24 1993 08:39 | 2192 |
| *******************************************************************************
*******************************************************************************
#### ##### ##### ## # ## ## ## ## ######
## ## ## ## ## # # # ## ## ### ### ###
## ## ##### ##### # # # ## ## ### ### ##
## ## ## ## # ## ### ## # ## ###
#### ## ##### # # # ## ## ######
### # # #####
## ## # # ## ##
##### # #####
## ## # # ##
## ## # # ##
The Newsletter
***** D I G I T A L C O N F I D E N T I A L *****
*******************************************************************************
*******************************************************************************
_______________________________________________________________________________
The OpenVMS AXP Newsletter February 1993
______________________________________________________________ VOLUME 12 ______
The OpenVMS AXP Newsletter is an occasional newsletter produced
by OpenVMS product management to disseminate information about
the OpenVMS AXP project, and related Alpha information.
Your contributions are welcome and encouraged. They should be
reviewed and approved prior to their submission and the content
should be appropriate for a large audience.
If you have topics that you would like coverage on, please send
mail to STAR::GEORJEAN.
------------------------------------------------------------------------
CONTENTS
This newsletter covers the following topics:
WINNING WITH ALPHA
26 ADDITIONAL LAYERED PRODUCTS FOR OPENVMS AXP SHIPPING NOW
UPDATED ALPHA AXP SOFTWARE CHARTS
ALPHA AXP COMMERCIAL PERFORMANCE PARTY LINE
THE OPENVMS AXP OPERATING SYSTEM NAME
PORTING OPENVMS FROM VAX TO ALPHA AXP
MIGRATION ARTICLES IN PRINT
MIGRATION TOOLKIT V1.1 AVAILABLE ONLINE
UPDATED ALPHA AXP BENCHMARKING POLICY
POSIX FOR OPENVMS AXP V1.0 EFT KIT AVAILABLE
OPENVMS AXP EPSILON RELEASE PHASE 0 EXIT
OPENVMS AXP, VMSCLUSTERS, RMS JOURNALING V1.5 PHASE 2 EXIT
OPENVMS AXP V1.5 FIELD TEST #3 KIT AVAILABLE
HOW TO SUBSCRIBE
------------------------------------------------------------------------
<><><><><><><><><><><><><><><><><><><><>
| |
| WINNING WITH ALPHA |
| |
<><><><><><><><><><><><><><><><><><><><>
+---------------------------+ TM
| | | | | | | |
| D | I | G | I | T | A | L | INTEROFFICE MEMORANDUM
+___|___|___|___|___|___|___+
To: WINNING WITH ALPHA.DIS Date: February 10, 1993
From: Susan Shapiro
Dept: CSG/Alpha Marketing
Loc: BXB 1-2/E06
Tel: 293-5337
Mail: MSBCS::SHAPIRO, @BXB
Subject: "WINNING WITH ALPHA Program": 70 References in First 90 Days!
It has been 90 days since we announced Alpha AXP systems and customer
enthusiasm continues to build for our solutions. We are publicizing
these customer success stories in various internal and external
communications and press releases. Attached are 56 profiled ALPHA AXP
and Alpha-Ready wins contributed by the Field, and a listing of 14
others on Reference Exchange. We have placed an asterisk (*) next to
the 16 newest profiles added since January 15, 1993.
HERE ARE JUST A FEW OF THE EXCITING NEW ALPHA AXP WINS ADDED THIS
MONTH!
NEW DIGITAL ACCOUNT
* Otis Manufacturing Co. (Malaysia) Pro/Engineer MCAD/OSF/1
NEW CUSTOMER APPLICATION WINS
* Banque Paribas (Belgium) International Payments/OSF/1
BULL Displacement/Downsizing Win
* Bank Tefachot (Israel) Customized Retail Banking/OpenVMS
IBM Displacement, Downsizing Win
* Weavexx (ASK Computer) MRP2 MANMAN/X, Alpha Ready/OSF/1
* Cray Research Multi-Million $$ Alpha Chip Win
* Quaker Oats-Europe (Belgium) Process Manufacturing/OpenVMS
IBM Displacement/Downsizing Win
WINNING WITH ALPHA: Success Stories Any Digital Employee Can Access!
This is the last time we will be distributing a large package of
WINNING WITH ALPHA success stories. Below are the three ways you will
be able to access Alpha wins in the future;
1. $ VTX REFERENCE EXCHANGE
Everyday, new Alpha AXP wins are added to the worldwide Reference
Exchange database. Every Digital employee worldwide can access these
Alpha AXP and Alpha-Ready wins by typing $ VTX REF.
2. PUBLIC NOTES FILES
Below are two pointers to public notesfiles containing the latest
"Winning With Alpha" success stories in either ASCII and Postscript
formats.
Human::Alpha_Public:WINNING_WITH_ALPHA.txt (or .PS)
VMSMKT"OpenVMS_Info"::WINNING_WITH_ALPHA_WINS.txt (or .PS)
3. READER'S CHOICE
By adding the WINNING WITH ALPHA Newsletter to your Reader's Choice
profile, you will automatically receive a 1-2 page electronic
summary of the newest customer wins profiled each month. Why not do
it right now?
Type at the $ VTX PROFILE to access Reader's Choice.
Momentum is the name of the game! We need a continuous flow of
exciting, strategic wins in EVERY industry to impress our customers and
prospects and aid our salesforce in closing new business. Please give
this memo widespread distribution in your organization. We also ask for
your help in identifying and profiling new wins in your industry or
geography. As a "thank you" for completing a brief profile (see next
page), we will send each sales rep two gold WINNING WITH ALPHA lapel
pins; one for the rep, and one to personally present to their customer.
We would be glad to assist them in any way. Please feel free to contact
Donna Bekier (DTN 293-5377) or me for assistance or with your
suggestions for improving the WINNING WITH ALPHA Program.
"WINNING WITH ALPHA" CUSTOMER PROFILE
CUSTOMER: CPU MODELs:
ADDRESS: OPENVMS or OSF or NT:
Alpha Ready Sale? Y/N
ACCOUNT MANAGER: DTN: MAIL:
1) Please describe your customer's industry and their application?
INDUSTRY:
PRIMARY APPLICATION:
Other KEY Applications:
2) Was this sale a NEW application for us at the account? NEW/EXISTING
OR did we add more power to an EXISTING application?
3) Did we have strong COMPETITION for the sale? Y/N
If so WHO and what system? Why did we win?
4) Will we DISPLACE another vendor's application or hardware? Y/N
If so, specify application or hardware to be displaced
5) What are the key software products required for your
customer to be successful in this application?
6) Estimated Alpha implementation date ____________
7) Can we use your customer's name and application in:
- Reference Exchange Y/N
- customer presentations Y/N
Would your customer be interested in publicity? Y/N
- press release (i.e. having their name mentioned) Y/N
- having the press contact them about Alpha AXP Y/N
- testimonial/success story for external use Y/N
8) What was the most important reason why the customer chose Digital?
9) Will this application benefit from Alpha's 64 bit
architecture? Y/N
10) Was an Alpha Seed Unit instrumental in closing this
sale? Y/N
11) What about this customer, sale, or application would
our sales force and/or customers find interesting?
Please return this information to Donna Bekier at MSBCS::Bekier, or
@BXB (293-5377 or 508-264-5377) or FAX it 508-264-5602, or submit
directly to REFERENCE EXCHANGE via Karen Cadrin @MRO or Sales::Cadrin
(297-3540).
*** DIGITAL CONFIDENTIAL ***
--------------------------------------------------------------------------
<><><><><><><><><><><><><><><><><>
| |
| 26 Additional LP's for |
| OpenVMS AXP Shipping Now! |
<><><><><><><><><><><><><><><><><>
Stephanie Parish
Software Group
(603)881-0341
DIGITAL SHIPS 37 SOFTWARE PRODUCTS FOR ALPHA AXP ON CD-ROM
MAYNARD, Mass. -- February 12, 1993 -- Today, Digital Equipment Corporation
delivered to customers worldwide an additional 26 layered software products for
OpenVMS AXP systems via CD-ROM technology. Eleven software products began
shipping last November.
The OpenVMS AXP platform now has a complete software development environment,
allowing customers to easily move their existing applications to the Alpha AXP
platform. In addition, a complete suite of database products are now available,
enabling full strength commercial applications on Alpha AXP systems.
"We are ahead of schedule on our commitments made last May to ship a
significant proportion of our software for OpenVMS Alpha systems by June of
this year," stated Dennis A. Roberson, vice president, Software. "The early
software shipment clearly demonstrates that Digital has renewed its commitment
to more rapidly meeting customer requirements. At the same time, both Digital
and our customers save money and valuable resources through the delivery of
software on CD-ROMs," added Roberson.
Digital is shipping new releases of software for the Alpha AXP platform every
quarter on CD-ROM. All the code and documentation needed to install and operate
the software products on OpenVMS AXP systems is contained on the disks. In
addition, the CD-ROMs contain an installation guide and warranty information.
Collectively called Alpha AXP Layered Products Software Library for OpenVMS,
the 37 software components shipped today represent a major thrust in offering a
complete software suite to developers, system integrators and end-users of
Alpha AXP systems. (See attached list of software products.)
Digital Equipment Corporation, headquartered in Maynard, Massachusetts, is the
leading worldwide supplier of networked computer systems, software and
services. Digital pioneered and leads the industry in interactive, distributed
and multivendor computing. Digital and its business partners deliver the power
to use the best integrated solutions - from desktop to data center - in open
information environments.
####
Note to Editors: The following are trademarks of Digital Equipment Corporation:
OpenVMS, Alpha AXP, DEC FORTRAN, DECmigrate, DECset, DECwindows, DECforms,
PATHWORKS, DBMS, DEC Ada, CDD/Repository, DECmessageQ, DEC Rdb, POLYCENTER, DEC
PHIGS, DEC GKS, DSM.
Motif is a trademark of the Open Software Foundation, Inc.
CORP/93/005
Alpha AXP Layered Products Software Library for OpenVMS
Shipping on CD-ROM as of February 12, 1993
CDD/Repository Version 5.2 for OpenVMS AXP Systems
DEC ACA Services Version 2.1 for OpenVMS AXP Systems (Development)
DEC ACA Services Version 2.1 for OpenVMS AXP Systems (Run-Time)
DEC Ada Version 3.0 for OpenVMS AXP Systems
DEC C Version 1.2 for OpenVMS AXP Systems
DEC DBMS Version 5.0 for OpenVMS AXP Systems
DEC Distributed Computing Services (DECdcs) Version 1.0 for
OpenVMS AXP Systems (Server)
DEC Distributed Computing Services (DECdcs) Version 1.0 for
OpenVMS AXP Systems (Client)
DEC Distributed Queuing Service Version 1.2 (DQS) for
OpenVMS AXP Systems
DEC FMS Version Version 2.4 for OpenVMS AXP Systems (Development)
DEC FMS Version 2.4 for OpenVMS AXP Systems (Run-Time)
DEC Fortran Version 6.0 for OpenVMS AXP Systems
DEC GKS Version 5.1 for OpenVMS AXP Systems
DEC PHIGS Version 2.4 for OpenVMS AXP Systems
DEC Rdb Version 5.0 for OpenVMS AXP Systems
DEC Rdb Version 5.0 for OpenVMS AXP Systems (Multi-Version)
DECforms Runtime System Version 1.4 for OpenVMS AXP Systems
DECmessageQ Version 2.0 for OpenVMS AXP Systems
DECmigrate Version 1.0 for OpenVMS AXP Systems
DECram Version 1.1 for OpenVMS AXP Systems
DECset Release 11 for OpenVMS AXP Systems
DECwindows Motif Version 1.1 for OpenVMS AXP Systems
DECwindows Motif Version 1.1 for OpenVMS AXP Systems - Deutsch
DECwindows Motif Version 1.1 for OpenVMS AXP Systems - Svenska
DECwindows Motif Version 1.1 for OpenVMS AXP Systems - Francais
DECwindows Motif Version 1.1 for OpenVMS AXP Systems - Espanol
DECwindows Motif Version 1.1 for OpenVMS AXP Systems - Italiano
Digital Extended Math Library Version 2.0 for OpenVMS AXP Systems
(Development)
Digital Extended Math Library Version 2.0 for OpenVMS AXP Systems
(Run-Time)
DSM Version 6.2 for OpenVMS AXP Systems
KAP for DEC C Version 1.0 for OpenVMS AXP Systems
KAP for DEC FORTRAN Version 1.0 for OpenVMS AXP Systems
MACRO-64 Assembler Version 1.0 for OpenVMS AXP Systems
PATHWORKS Version 4.2 for OpenVMS AXP Systems
POLYCENTER Software Distribution Version 2.3A for OpenVMS AXP Systems
SQL Multimedia for DEC Rdb Version 1.1 for OpenVMS AXP Systems
SQL/Services Version 5.0 for OpenVMS AXP Systems
-------------------------------------------------------------------------
<><><><><><><><><><><><><><><><><><>
| |
|Updated Alpha AXP Software Charts |
| |
<><><><><><><><><><><><><><><><><><>
New versions of the ROLLOUT and PHASES charts for both OpenVMS O/S AXP
and DEC OSF/1 V1.2 for AXP can be found at this location:
HUMAN::ALPHA_PUBLIC:AXP_SOFTWARE_PHASES_PUBLIC.PS
HUMAN::ALPHA_PUBLIC:AXP_SOFTWARE_ROLLOUT_PUBLIC.PS
*** DIGITAL CONFIDENTIAL ***
-------------------------------------------------------------------------
<><><><><><><><><><><><><><><><><>
| |
|Alpha AXP Commercial Party Line |
| |
<><><><><><><><><><><><><><><><><>
FOR DISTRIBUTION AS PUBLIC INFORMATION
======================================
Alpha AXP COMMERCIAL PERFORMANCE PARTY-LINE
Digital's Alpha AXP systems are designed as balanced and scalable
platforms to ensure that they deliver excellent performance across a
wide range of applications.
At this point in the development of Alpha AXP, we have demonstrated
leadership price/performance across a wide range of industry-standard
benchmarks in the traditional technical environments. We are currently
working on all the components that are necessary to complete a similar
benchmark for Alpha AXP in commercial environments. Until this work is
complete, we are unable to release commercial figures such as TPC-A. We
expect to have TPC-A numbers for OpenVMS AXP and DEC OSF/1 AXP database
systems in the April-June 1933 timeframe.
Alpha AXP systems will deliver leadership commercial performance
through leadership I/O and computer performance. Top performing system
platforms, database systems, languages and other commercial
capabilities will provide the underpinnings to achieve this. To help
establish the size of system required in a commercial environment,
compare Alpha AXP with its major RISC based competitors based on the
integer technical performance of the relative systems.
As a proof point of leadership commercial performance, we decided to
demonstrate the capability of the Alpha AXP architecture and the
DEC21064 implementation by breaking the world's record for SORT
performance. The benchmark we used is the one defined in the 1985
Datamation article which also defined the Debit-Credit bench- mark. The
benchmark sorts 1 Million 100-byte records containing 10-byte keys. The
"now old" world's record was 26 seconds performed under UNIX on a CRAY
Y-MP. Using a new sort algorithm, the 21064's large on-chip cache and
the DEC 7000's high-bandwidth I/O channels, we have already shaved
practically 7 seconds off that record. Our current best time is 19.07
seconds. These are preliminary results for a single processor AXP
system. Our goal is to sort a million records in 10 seconds and to sort
a gigabyte in one minute.
For more information refer to:
HUMAN::ALPHA_PUBLIC:AXP_THE_WORLDS_FASTEST_SORT.TXT
-------------------------------------------------------------------------
<><><><><><><><><><><><><><><><><>
| |
| OpenVMS Operating System Name |
| |
<><><><><><><><><><><><><><><><><>
+---------------------------+ TM
| | | | | | | |
| d | i | g | i | t | a | l | I N T E R O F F I C E M E M O
| | | | | | | |
+---------------------------+
To: OpenVMSInterest Dist. From: Mark Gorham
Date: 1-FEB-93
Dept: OpenVMS Product Management
Ext: 381-0134
Loc: ZK3-4/T61
Enet: VMSDEV::GORHAM
Subject: OpenVMS Operating System
The VMS Operating System name has been changed to the OpenVMS Operating
System. Although this name change has happened with the V5.5 release, there
are several references in literature, business plans, presentations to
VMS. I would appreciate it if you could use our new name 'OpenVMS Operating
System'. Below are a list of reasons for the name change as well as some
of the common misconceptions.
Over the past several years, Digital has added significantly to the
OpenVMS Operating Environment. These additions include:
o X.400 and X.500 o OSF/Motif
o IEEE POSIX o X/Open XPG3 Base Branding
o NAS Packages o Competitive pricing and licensing
o TCP/IP o Shipment on the RISC platform Alpha AXP.
As a result of these and other changes, users can build Open Systems that are
cost effective, adaptable, robust and multi-vendor, using OpenVMS as a base.
In recognition of this real capability, available today, Digital changed the
name of the Operating System to OpenVMS.
This is a full-scale change of the name only. Here are some common
misconceptions:
1. Some think VMS is a different system than OpenVMS - Not so!
- OpenVMS is the same software as VMS (same part number).
- All we changed was the name, permanently, in July '92.
- All VMS is now OpenVMS, no matter where it is.
- Documentation and literature will catch up over time.
2. Some think VMS is for VAX and OpenVMS is for Alpha AXP - Not so!
- OpenVMS is for both VAX and Alpha AXP.
- OpenVMS is OpenVMS.
3. Some think they are now forced to use the Open Components - Not so!
- Users who want to use IEEE POSIX or OSF DCE with OpenVMS can.
- Users who don't want to use Open Components need not.
- Many use the components, but do not recognize them as such.
Thank you for your cooperation.
*** DIGITAL CONFIDENTIAL ***
-------------------------------------------------------------------------
<><><><><><><><><><><><><><><><><><><><><>
| |
| Porting OpenVMS from VAX to Alpha AXP |
| |
<><><><><><><><><><><><><><><><><><><><><>
The February issue of the "Communications of the ACM" as well as
the "Digital Technical Journal" (Volume 4, Number 4), are on
Alpha AXP and feature articles on various aspects of Alpha AXP.
Below is a short overview of the "Porting OpenVMS from VAX to Alpha"
article which appears in both.
PORTING OPENVMS FROM VAX TO ALPHA
By: Tom Benson, Wayne Cardoza, Ravindran Jagannathan,
Nancy Kronenberg, and Ben Thomas
ABSTRACT: OpenVMS is the Virtual Memory operating system developed by
Digital Equipment Corporation (DEC) for the VAX family of computers.
Recently, this system has been moved from VAX to the Alpha
architecture. Alpha is a new RISC architecture introduced by DEC in
1992. This paper describes two aspects of the move: how we dealt
with the large volume of VAX assembly language; and how we modified
the kernel which had a number of VAX architecture dependencies.
1 INTRODUCTION
VAX is a Complex Instruction Set Computing (CISC) architecture.
Although VAX has been a popular and successful architecture, it has
been widely recognized that CISC architectures have some performance
disadvantages compared with Reduced Instruction Set Computing (RISC)
architectures. The main purpose of moving OpenVMS to the Alpha
architecture was to deliver the performance advantages of RISC to VMS
applications.
We had two important requirements in moving OpenVMS to Alpha.
Today, there is a large volume of applications on OpenVMS VAX and a
large installed base. We wanted to make it easy to move software and
users from OpenVMS VAX to OpenVMS Alpha. The second requirement was
to deliver a first version of the product as early as possible. The
combination of these requirements led us to adopt a fairly
straightforward porting strategy with minimal redesigns or rewrites.
We view the first version of the OpenVMS Alpha product as a beginning,
with other evolutionary steps to follow.
The Alpha architecture was designed for high performance but also
with migration from VAX to Alpha in mind. We included in Alpha some
VAX features which ease the migration without compromising hardware
performance. The VAX features in Alpha that are important to OpenVMS
are: four protection modes, per page protection, and 32 interrupt
priority levels (IPLs). The Alpha architecture also defines a
Privileged Architecture Library (PAL) environment as having interrupts
disabled and running in the most privileged of the four modes
(kernel.) PALcode is a set of Alpha instructions which execute in the
PAL environment. Basic system software functions such as translation
buffer (TB) miss service are in PALcode. For OpenVMS Alpha, PALcode
also implements some VAX features such as software interrupts and
asynchronous traps (ASTs). The combination of hardware architecture
assists and OpenVMS PALcode made it easier to port OpenVMS to Alpha
and also provide better VAX compatibility for applications which have
used VAX features such as ASTs.
VAX is a 32-bit architecture. It has 32 bits of virtual address
space, 32-bit registers and a comprehensive set of byte, word
(16-bit), and longword (32-bit) instructions. Alpha is a 64-bit
architecture with 64 bits of virtual address space, 64-bit registers,
and instructions that load, store, and operate on 64-bit quantities.
Alpha also defines a set of longword load, store, and operate
instructions, and a canonical form for a longword loaded from memory
into a 64-bit register.
OpenVMS Alpha has anticipated the move from 32-bit address space
size to 64-bit address space by changing to a page table format that
supports large address spaces. However, OpenVMS has pervasive
assumptions that an integer = an address = 32-bits. This kind of
assumption can exist in applications as well. Therefore, the first
version of OpenVMS Alpha supports 32-bit address spaces only.
Most of the OpenVMS kernel is in VAX assembly language (VAX
MACRO-32), Instead of rewriting the VAX MACRO-32, we developed a
compiler for it. We required inspection and manual modification of
the VAX MACRO-32 to have better structure and to deal with many VAX
architecture dependencies. Parts of the kernel that were heavily
dependent on the VAX architecture required redesign and rewrites, but
this was a minority of the total volume of VAX MACRO-32.
-----------------------------------------------------------------------
<><><><><><><><><><><><><><><><><>
| |
| Migration Articles in Print |
| |
<><><><><><><><><><><><><><><><><>
Below is a listing of some articles which have appeared or will
soon appear in various publications on OpenVMS AXP Migration.
---------------------------------------------------------------------
"Understanding Data Alignment On OpenVMS AXP(tm) Systems",
Digital Systems Journal, coming in future 1993 issue, by
Eric LaFranchi, DEMAX Software, Inc., and Kathleen D. Morse,
Digital Equipment Corp.
---------------------------------------------------------------------
"Understanding and Identifying Page-Size Dependencies in Migrating
Applications to Alpha AXP(tm) Systems", Digital Systems Journal,
coming in Feb 1993 issue, by Eric LaFranchi, DEMAX Software, Inc.,
and Kathleen D.Morse, Digital Equipment Corp.
---------------------------------------------------------------------
"Migrating VAX/VMS MACRO-32 Sources to Alpha VMS", VAX Professional
Magazine, Sept/Oct 1992, by Eric M. LaFranchi and Kathleen D. Morse.
---------------------------------------------------------------------
"Preparing for Migration to Alpha VMS", DEC Professional
Magazine, July 1992 and August 1992 issues (2 part article),
by Kathleen D. Morse and Phil A. Naecker.
---------------------------------------------------------------------
<><><><><><><><><><><><><><><><><>
| |
| Migration Toolkit V1.1 |
| Available Online Now! |
<><><><><><><><><><><><><><><><><>
The ARAM Migration Services team announces network availability
of the pre-SSB release of the Migration Toolkit V1.1.
These tools (compilers, DECmigrate, and other cross-utilities)
run on VAX/VMS systems supporting OpenVMS AXP development without
the need for Alpha AXP hardware.
This release of the Migration Toolkit (V1.1) is compatible with
OpenVMS AXP V1.0.
==============================================================================
LOCATION:
Please access the toolkit at the following location:
VAXWRK::ALPHA$TOOLS:MIGTOOLS011.A
MIGTOOLS011.B
MIGTOOLS011.C
$ DIR VAXWRK::ALPHA$TOOLS:
MIGTOOLS011.A;1 162/162 25-JAN-1993 09:21:06.00
MIGTOOLS011.B;1 31572/31572 25-JAN-1993 09:21:07.00
MIGTOOLS011.C;1 97668/97668 25-JAN-1993 09:21:34.00
Total of 3 files, 129402/129402 blocks.
==============================================================================
CONTENTS:
The following crosstools are included in the toolkit:
ALPHA_ANALYZOBJ - T05-10
ALPHA_BACKUP - X5F7-VAX
ALPHA_CDU - T05-05
ALPHA_LIBRARIAN - T09-09
ALPHA_LINK - T10-55
ALPHA_MACRO - X1.6-18
ALPHA_MESSAGE - T02-08
WRITEBOOT - X5F7-VAX
PFORT - VX3.2-317-25CF
GEMC$CC - C X1.3-003B
MACRO-64 - MACRO64V1.0-213
BLISS32E - T1.0-020
BLISS64E - T1.0-020
VEST - V1.0
==============================================================================
DOCUMENTS:
The Release Notes and User's Guide are still in production. A
followup note will be posted here when the final SSB kit, including
documentation, is available.
==============================================================================
QARs:
The QAR database for the MIGTOOLS011 toolkit is under discussion.
In lieu of this database, send mail of problems directly to
ALPHAZ::HARNEY.
*******************************************************************************
*******************************************************************************
Summary of all OpenVMS AXP Migration Services Offerings
Application Reengineering and Migration (ARAM) Services has created a
comprehensive and flexible suite of service packages to help customers
migrate from OpenVMS to OpenVMS AXP systems. These services include:
OpenVMS [TM] Migration Contains tools (C, Fortran,
Service Package for OpenVMS AXP BLISS, Macro-32 cross compilation
system, Macro-64 assembler,
DECmigrate binary translator,
windows libraries), extensive
(offered at a substantial documentation, phone support, Alpha
discount than if purchased Architecture CBI, and five days of
separately) training.
OpenVMS [TM] Migration Contains tools (C, Fortran,
Tools Package for OpenVMS AXP BLISS, Macro-32 cross compilation
system, Macro-64 assembler,
DECmigrate binary translator,
windows libraries), documentation,
and telephone support.
The tools allow the customer to:
o Start now to recompile or translate applications to run on
OpenVMS AXP [TM] systems. The porting tools run on OpenVMS
systems, so customers can use them today, even if they do not have
access to an AXP system.
o Use existing OpenVMS development resources to begin the
porting process.
One way to take advantage of the porting toolkit is to perform
development tasks on OpenVMS systems until a complete
development environment has been established on the AXP system.
o Use the included documentation as a guide for migration planning
and implementation.
In addition to the tools packages, there are additional services at various
levels to assure that customers will successfully move to the OpenVMS AXP
environment.
Application Migration Designed for use with the tools packages,
Orientation Service provides an on-site migration expert to review
the customer's environment, provide a prelim-
inary analysis, and provide an introduction
to the migration process.
Application Migration Provides an on-site consultant to conduct an
Detailed Analysis Service in-depth assessment of the scope and impact
of the migration project.
Application Migration Supplements the customer's staff by providing
Project Support Service a migration expert to assist in the migration
project at whatever level the customer
requires: project engineering, support, or
technical or project management.
Application Migration Provides a detailed analysis necessary to
Project Planning Service understand the size and scope of the migration
project. The result is a quality assurance
strategy and a comprehensive project plan
which provides a clear picture of the human
and technology requirements for the migration
project.
Application Migration Uses a phased approach and involves the
Custom Project Service customer and Digital jointly specifying the
scope and tangible solutions to be produced.
Most often, this service is used when the
customer wants Digital to "do it all." Rely-
ing on Digital's software specialists reduces
demand on the customer's internal resources,
ensures predictable costs and timetables, and
lets your customer focus on core business
activities.
SSD Description (US) LIST PART NUMBER
----------------------------------------------------------------------------
961 OpenVMS AXP Migration Service Package $6900 YS-ALPAA-OH
967 OpenVMS AXP Migration Tools Package $4900 YS-ALAAA-OH
962 Application Migration Orientation Service $5200 QS-ALPAA-CA
963 Application Migration Detailed Analysis Service *T&M,Quote QS-ALPAA-CE
964 Application Migration Support Engineer I:
hourly rate $130/hr QS-ALPAA-TH
>900/<1799 hrs $117/hr QS-ALPAA-T2
>1800 hrs $111/hr QS-ALPAA-T3
964 Application Migration Support Engineer II:
hourly rate $145/hr QS-ALAAA-TH
>900/<1799 hrs $131/hr QS-ALAAA-T2
>1800 hrs $123/hr QS-ALAAA-T3
965 Application Migration Project Planning Service *T&M,Quote QS-ALPAA-52
966 Application Migration Custom Project Service *T&M,Quote QS-ALPAA-53
----------------------------------------------------------------------------
*Will be custom quoted as T&M or Fixed Price Quote.
----------------------------------------------------------------------------
*** DIGITAL CONFIDENTIAL ***
<><><><><><><><><><><><><><><><><>
| |
| POSIX for OpenVMS AXP V1.0 EFT |
| Kit is Available |
<><><><><><><><><><><><><><><><><>
INTEROFFICE MEMORANDUM
+---------------------------------------+
| |
+---------------------------+ TM | E N G I N E E R I N G - I T A L Y |
| | | | | | | | | V A R E S E |
| d | i | g | i | t | a | l | +---------------------------------------+
| | | | | | | |
+---------------------------+
To: VMS Interest Date: February, 10th 1993
Project Leaders From: Gianluca Michencigh
Product Managers Dept: VMS/Italy Engineering
Engineering Italy DTN: 787-8365
Loc: VAR
Email: AIRONE::MICHENCIGH
Subject: POSIX for OpenVMS AXP V1.0 EFT kit is Available
Announcement
------------
The POSIX for OpenVMS AXP V1.0 EFT kit is now available to be used and
tested. It contains all functionality planned for the product.
See the $README.FIRST and Release Notes for further details.
NOTE
This kit supports only OpenVMS AXP V1.5 FT3
(Delta base level X5GY-D3A). All users that
intend to use it need to install on their system
this OpenVMS AXP version.
Kit location
------------
The kit is available on:
BOESIO::POSIX$KITS:[AXP-V10] (Located in Varese, Italy)
BULOVA::POSIX$KITS:[AXP-V10] (Located in Nashua, N.H., USA)
A $README.FIRST file explains all the files in this directory, including
the available documentation.
Bugs reporting
--------------
A QAR database on TRIFID (POSIX_AXP_V10-EFT) is available. See the
$README.FIRST for instructions on how to access it.
Notes conference
----------------
The unrestricted notesfile AIRONE::VMS_POSIX is available for general
discussions and questions about the product (not bug reports).
The development team would like to understand how the product is being used
internally. Please enter a note in our notes conference describing your
planned or actual usage.
*** DIGITAL CONFIDENTIAL ***
-------------------------------------------------------------------------
<><><><><><><><><><><><><><><><><><><><>
| |
| Updated Alpha AXP Benchmarking Policy|
| |
<><><><><><><><><><><><><><><><><><><><>
BENCHMARKING ON Alpha AXP SYSTEMS 14-January-1993
POLICY, version 3.1 Page 1
*** DIGITAL INTERNAL USE ONLY ***
APPLICABILITY:
This policy only applies to unreleased products (hardware and software).
Standard operational policies apply to currently-shipping products.
POLICY:
DEC OSF/1 AXP SYSTEMS---Benchmarking may be performed for compute-
intensive C and FORTRAN programs on all Alpha AXP systems using
| DEC OSF/1 BL10 or later release and DEC FORTRAN EFT2 (T3.3).
OpenVMS AXP SYSTEMS---Benchmarking may be performed for any "Stage 2"
layered software products listed below using OpenVMS V1.0 and the
Stage 2 EFT2 versions for each of the software component products.
| WINDOWS NT AXP SYSTEMS---No benchmarking.
EXPLANATION:
This policy applies to all Digital employees. It conforms to the
Corporate Policy, especially on honesty: "We want to be not only
technically honest, but also to make sure that the implication of what
we say and the impressions we leave are correct."
Our public party line is as follows:
"Benchmarking may be performed on both DEC OSF/1 AXP and OpenVMS AXP
(stage 2 products) systems. For DEC OSF/1 AXP systems, this applies
to compute-intensive C and FORTRAN programs. For OpenVMS AXP
systems, restrictions on benchmarking all stage 2 products is lifted.
Volume Alpha AXP systems are expected to achieve performance and
price performance leadership in most applications for target
markets. Performance on Alpha AXP systems will continue to increase
indefinitely through additional performance optimizations in
software and increased experience in tuning Alpha AXP systems."
The following statements will be valid for Alpha AXP systems until
production-level systems are shipping:
o Some Alpha AXP systems currently at field locations (field test,
business partner (CSO) sites and Digital locations) are running
on hardware which is functioning below full production
performance levels, in particular, those with DECchip 21064 pass2
microprocessors, pass3 is the up-to-date revision level;
o The DEC OSF/1 AXP operating systems is running with extensive
sanity checking enabled;
o Layered products have incomplete or not fully tuned optimizing
algorithms.
Any performance measurements (benchmarks or otherwise) taken on these
systems must be interpreted within this context and communicated as
such. In particular, any such measurements cannot reflect performance
levels we expect production- level Alpha AXP systems and software to
achieve.
*** DIGITAL INTERNAL USE ONLY ***
BENCHMARKING ON Alpha AXP SYSTEMS 14-January-1993
POLICY, version 3.1 Page 2
EUROPEAN POLICY
For the first half of FY93 benchmarking will be restricted to the Area
benchmark centre in Valbonne and qualification of other centres will be
started, e.g., in Galway. The intent is to allow the country ARCs to
focus their resources on CSO and strategic end-user application porting
support. Local benchmarking will be considered on an exception basis and
approval is required from the Area benchmark centre in Valbonne.
Since benchmarking represents a cost of sale, benchmarks will be
cross-charged to Account teams. There will be standard terms and
conditions for this across all benchmark centres as they come on board.
Benchmarking will only be done when the sales situation absolutely
requires it.
This policy will be reviewed on an ongoing basis by the European Alpha AXP
Program Office.
---------------------------------------------------------------------------
HANDLING OTHER Alpha AXP BENCHMARK REQUESTS
All other benchmarking requires approval by Alpha AXP Program Office
which is responsible for weighing strategic advantage vs. tactical risk
for this category. Submit requests using Alpha AXP Benchmark Request and
Information Form to HUMAN::ALPHA_AXP_BENCHMARK. After approval follow
standard Area benchmark procedures.
[end of policy]
*** DIGITAL INTERNAL USE ONLY ***
BENCHMARKING ON Alpha AXP SYSTEMS 14-January-1993
POLICY, version 3.1 Page 3
GENERAL COMMENTS
Maturity and degree of code optimization are the two main factors used
to determine a product's approval category. Additional system software
and system environments will be approved as performance optimizations
are included and tested and as the software matures.
---------------------------------------------------------------------------
APPROVED Alpha AXP BENCHMARKING SPECIFICS
The following system software and system environments are approved for
benchmarking Alpha AXP systems:
SYSTEM Single-processor Single-processor
ENVIRONMENTS compute-bound programs
| HARDWARE DEC 3000 model 400 DEC 3000 model 400
| PLATFORMS DEC 3000 model 500 DEC 3000 model 500
| DEC 4000 model 610 DEC 4000 model 610
| DEC 7000 model 610 DEC 7000 model 610
| DEC 10000 model 610 DEC 10000 model 610
SYSTEM OpenVMS AXP DEC OSF/1 AXP BL10
SOFTWARE Stage 2 SW products C
(see Addendum B) DEC FORTRAN for OSF/1,
T3.3 (EFT2 release)
Alpha AXP Area Benchmark Centers, P/PEG
EXPERTISE CENTERS AMCs (�) and ARCs (�)
PROCEDURE Follow standard area benchmark procedures. For the
Alpha AXP AXP program's tracking purposes, when
possible, submit an Alpha AXP Benchmark Request &
Information Form.
Notes: (�) Dependent upon Area policy and available Alpha AXP systems
---------------------------------------------------------------------------
ADDENDUM A--ANTICIPATED DEC OSF/1 AXP V1.2 LAYERED PRODUCTS
Product Name Version
------------------------------------------------------------
DEC AVS for DEC OSF/1 AXP 4.1
DEC C++ for DEC OSF/1 AXP 1.2
DEC FUSE for DEC OSF/1 AXP 1.2
DEC Fortran for DEC OSF/1 AXP Systems 3.3
DEC GKS for DEC OSF/1 AXP 5.1
DEC Object/DB for OSF/1 AXP 1.1
DEC PHIGS for DEC OSF/1 AXP 2.4
DEC Pascal V5.0 for DEC OSF/1 AXP Systems 5.0
DEC X.25 for DEC OSF/1 AXP 1.0
DECmigrate for DEC OSF/1 AXP 3.2
DECnet/OSI for DEC OSF/1 AXP 1.0
Digital Extended Math Library V2.0 for DEC OSF/1 AXP 2.0
KAP for DEC C V1.0 for DEC OSF/1 AXP 1.0
KAP for DEC Fortran V1.0 for DEC OSF/1 AXP 1.0
*** DIGITAL INTERNAL USE ONLY ***
BENCHMARKING ON Alpha AXP SYSTEMS 14-January-1993
POLICY, version 3.1 Page 4
ADDENDUM B--ANTICIPATED OpenVMS AXP STAGE 2 LAYERED SOFTWARE PRODUCTS
Product Name Version
------------------------------------------------------
DECforms[TM] Runtime System for OpenVMS AXP 1.4
PATHWORKS[TM] for OpenVMS AXP 4.2
DEC DBMS[TM] for OpenVMS AXP 5.0
KAP for DEC C[TM] for OpenVMS AXP 1.0
KAP for DEC FORTRAN[TM] for OpenVMS AXP 1.0
DEC Ada[TM] for OpenVMS AXP 3.0
DEC Distributed Computing Services (DECdcs) for 1.0
OpenVMS AXP (Server)
DEC Distributed Computing Services (DECdcs) for 1.0
OpenVMS AXP (Client)
CDD/Repository for OpenVMS AXP 5.2
DECmessageQ for OpenVMS AXP 2.0
DEC Distributed Queuing Service (DQS) for 1.2
OpenVMS AXP
DEC Rdb[TM] for OpenVMS AXP 5.0
DEC Rdb[TM] for OpenVMS AXP (Multi-Version) 5.0
SQL/Services 5.0
DEC ACA Services for OpenVMS AXP (Development) 2.1
DEC ACA Services for OpenVMS AXP (Run-Time) 2.1
SQL Multimedia for DEC Rdb 1.1
Polycenter Software Distribution 2.3A
DEC PHIGS[TM] for OpenVMS AXP 2.4
DEC GKS[TM] for OpenVMS AXP Systems 5.1
DECwindows[TM] Motif OpenVMS User 1.1
Interface/Deutsch
DECwindows[TM] Motif OpenVMS User 1.1
Interface/Svenska
DECwindows[TM] Motif OpenVMS User 1.1
Interface/Francais
DECwindows[TM] Motif OpenVMS User 1.1
Interface/Espanol
DECwindows[TM] Motif OpenVMS User 1.1
Interface/Italiano
DSM[TM] Version 6.2 for OpenVMS AXP
*** DIGITAL INTERNAL USE ONLY ***
BENCHMARKING ON Alpha AXP SYSTEMS 14-January-1993
POLICY, version 3.1 Page 5
Alpha AXP BENCHMARK REQUEST AND INFORMATION FORM
================================================
1. CUSTOMER: - Company name
- Address
- Contact person
2. DIGITAL: - Responsible account representative including DTN and
electronic mail address
- Digital office
- Support person
- Benchmark/Resource Center & contact person
3. BACKGROUND: (Brief description of reason for requesting restricted
benchmark--customer need, Digital need, etc)
4. TIMELINESS: (When/date must the benchmark results be available)
5. EXPECTATIONS: (Describe how you are managing the customer's
expectations with respect to the potential benchmark
outcomes taking into consideration hardware and
software maturity.)
6. BENCHMARK CHARACTERISTICS: (Brief description of the salient
characteristics of the benchmark, in particular, any risks
which might affect Digital's ability to win the benchmark
and which should be weighed in making a GO or NO-GO
decision. Describe the relevant system configuration,
including 3rd party products required):
List of Hardware List of Software
---------------- ----------------
| CPU = DEC OP SYS =
| model
1. 1.
2. 2.
3. 3.
4. 4.
5. 5.
6. 6.
7. 7.
8. 8.
Send completed form to HUMAN::ALPHA_AXP_BENCHMARK.
*** DIGITAL INTERNAL USE ONLY ***
-------------------------------------------------------------------------
<><><><><><><><><><><><><><><><><>
| |
| OpenVMS AXP Epsilon Release |
| Phase 0 Exit |
<><><><><><><><><><><><><><><><><>
+---------------------------+ TM
| | | | | | | |
| d | i | g | i | t | a | l | INTEROFFICE MEMORANDUM
| | | | | | | |
+---------------------------+
TO: Alpha Interest DATE: January 21, 1992
VMS Interest FROM: Mary Jane Vazquez
VMS Team DEPT: OpenVMS AXP Prod. Mgmt.
EVMS Staff DTN: 381-0518
VMS Staff LOC: ZKO3-4/T61
ENET: STAR::VAZQUEZ
SUBJECT: OpenVMS AXP EPSILON Release Phase 0 Exit
OpenVMS Product Management is electronically closing Phase 0 for the
third release of the OpenVMS AXP operating system, code named EPSILON.
Closing Phase 0 along with OpenVMS AXP is Volume Shadowing and
VMSclusters.
PRODUCT DESCRIPTION:
EPSILON is the third release of the OpenVMS AXP operating system
for Digital's 64-bit Alpha Architecture. This release will be
compatible with OpenVMS VAX Version 5.5-2, and be the basis for
initial product deployment and mission critical computing on
OpenVMS AXP systems. EPSILON plans to deliver:
o Full mixed clustering capability.
o Phase II Host Based Volume Shadowing, including SCSI shadowing
and performance assists.
o RMS Journaling (if not shipped prior to Epsilon).
o User Written Device Drivers.
o V5.5, V5.5-n bugfixes and features
Additional features which have been requested in Epsilon will be
reviewed during Phase 1. For further information the following
documents are available for your review in the public directory,
BULOVA::ALPHA$DISK:[EPSILON_PHASE_REVIEW]:
0 EPSILON Product Requirements Document
0 OpenVMS AXP Manufacturing Impact Statement
0 Preliminary EPSILON Documentation Impact Statement
For information not yet publicly available, please contact the author
of the following plans:
0 Business Plans
0 OpenVMS AXP Family Draft Eileen McDonough (STAR::)
0 VMSclusters Draft Nick Carr (STAR::NCARR)
0 Volume Shadowing Final Susan Azibert (VMSDEV::)
0 Marketing Plan Draft Phil Auberg (VMSMKT::)
The following is a projected schedule for EPSILON:
Milestone Planned Date
Phase 0 January, 1993
Phase 1 Q1CY93
Phase 2 Q3CY93
Phase 3 Q1CY94
FRS Q1CY94
If you have any questions or concerns on this release please contact
the appropriate Product Manager:
Volume Shadowing, Susan Azibert (VMSDEV::)
VMSclusters, Nick Carr (STAR::NCARR)
OpenVMS AXP (Epsilon) Operating System, Mary Jane Vazquez (STAR::)
*** DIGITAL CONFIDENTIAL ***
-------------------------------------------------------------------------
<><><><><><><><><><><><><><><><><>
| |
| OpenVMS AXP, VMScluster, RMS |
| Journaling V1.5 Phase 2 Exit |
<><><><><><><><><><><><><><><><><>
+---------------------------+ TM
| | | | | | | |
| d | i | g | i | t | a | l | INTEROFFICE MEMORANDUM
| | | | | | | |
+---------------------------+
TO: VMSINTEREST DATE: January 18, 1993
ALPHAINTEREST FROM: Susan Azibert
VMSTEAM Brian Breton
Nick Carr
DEPT: OpenVMS Product Management
SUBJECT: OpenVMS AXP V1.5 (DELTA) Phase 2 Exit
VMSclusters V1.5 Phase 2 Exit
RMS Journaling for OpenVMS AXP V1.5 Phase 2 Exit
With the successful completion of a Phase 2 Review meeting held January 15,
1993 in ZKO OpenVMS Product Management is closing Phase 2 for the second
release of the OpenVMS AXP operating system, Version 1.5, code named DELTA.
Also closed by OpenVMS Product Management at the January 15 Phase 2 Review
meeting was Phase 2 for the initial releases of the OpenVMS System
Integrated Products VMSclusters Version 1.5, and RMS Journaling for OpenVMS
AXP Version 1.5.
PRODUCT DESCRIPTIONS:
OpenVMS AXP V1.5 (DELTA) is the second release of the OpenVMS AXP operating
system for Digital's 64-bit Alpha AXP architecture. The initial release,
OpenVMS AXP V1.0, does not contain full OpenVMS VAX functionality. OpenVMS
AXP V1.5 adds more of the OpenVMS VAX functionality to OpenVMS AXP. The
Alpha Program's software plan is to roll out functionality over 1-2 years.
The main goal for OpenVMS AXP V1.5 to deliver additional functionality in
order to become closer to OpenVMS VAX functional parity. OpenVMS AXP V1.5
plans to deliver:
o Cluster support for limited configurations
o Symmetric Multiprocessing (SMP) support for limited configurations
o DECdtm V1.1 support
o InforServer Initial System Loading
o Xterminal support
o ISO 9660 CD-ROM support
o Multiple disk volume sets
o Base system support for POSIX
o Pelican workstation support
o Jensen server support
VMSclusters Version 1.5 is the initial release of clustering capabilities
for both OpenVMS AXP systems and mixed OpenVMS VAX and AXP systems. The
initial release will support full clustering capabilities from a software
perspective however the system configurations which will be initially
supported will be restricted. In order to meet time to market needs
VMScluster software must ship as soon as possible with a subset of
configuration testing complete. After the software begins to ship
configuration testing will continue and the supported configurations will be
expanded as testing completes.
RMS Journaling for OpenVMS AXP V1.5 helps maintain the data integrity of RMS
files in the event of a number of failure scenarios. RMS Journaling helps
to protect RMS file data from becoming lost or inconsistent. Although the
RMS Journaling software ships as a system integrated product with the
OpenVMS AXP operating system it is not scheduled to be supported until some
time after the operating system reaches First Revenue Ship (FRS).
Further information on OpenVMS AXP V1.5, the Phase 2 Closure, and other
associated documents can be copied from:
BULOVA::ALPHA$DISK:[DELTA_PHASE_REVIEW]
DELTA_EFT_PLAN.PS
DELTA_MANUFACTURING_PLAN.PS
DELTA_MASTER_DOCPLAN.PS
DELTA_SUMMARY_PROJECT_PLAN.PS
DELTA_PHASE_2_MINUTES.TXT
For information which is not yet publicly available please contact the
author of the following plans:
Plan Status Date Author
o Business Plan
o OpenVMS AXP Draft Dec 4, 1992 Eileen (STAR::)McDonough
o VMSlusters Draft Dec 4, 1992 Nick Carr (STAR::NCARR)
o RMS Journaling Draft Dec 4, 1992 Susan (STAR::)Azibert
o Marketing Plan Draft Dec 11, 1992 Phil (VMSMKT::)Auberg
Milestone Planned Date
EFT1 Start 25-Jan-1993
EFT2 Start 08-Mar-1993
OpenVMS AXP V1.5 SSB 30-Apr-1993
OpenVMS AXP V1.5 FRS 10-May-1993
If you have any questions or concerns on any of these products please
contact the appropriate Product Manager:
1. RMS Journaling, Susan (VMSDEV::)Azibert
2. OpenVMS AXP, Brian (STAR::)Breton
3. VMSclusters, Nick (STAR::NCARR) Carr
*** DIGITAL CONFIDENTIAL ***
-------------------------------------------------------------------------
<><><><><><><><><><><><><><><><><>
| |
| OpenVMS AXP V1.5 FT3 Available |
| |
<><><><><><><><><><><><><><><><><>
+---------------------------+ TM
| | | | | | | |
| d | i | g | i | t | a | l | INTEROFFICE MEMORANDUM
| | | | | | | |
+---------------------------+
To: OpenVMS Alpha Engineering Date: 25 January 1993
From: Paula Fitts
Nitin Karkhanis
Harold Schultz
Dept: OpenVMS Alpha
DTN: 381-0255
Mail: ZKO3-4/T61
Enet: EVMS::HSCHULTZ
Subject: OpenVMS AXP (TM) Operating System V1.5 Field Test #3 Available
The OpenVMS AXP (TM) Operating System V1.5 Field Test #3 kit is now
available to Digital internal users over the EasyNet. This kit will be
made available to the Alpha Migration Centers and Alpha Resource
Centers worldwide, and to external field test customers.
The OpenVMS AXP (TM) V1.5 FT3 release provides all of the features
contained in OpenVMS AXP (TM) V1.0 plus some additional new features.
Some of the features that are either new or changed in FT3 are:
* SMP
* VMScluster support
* New Batch/Print queuing system
* Infoserver (ISL) support
* ISO 9660 support
* X Terminal support
* Virtual I/O cache
* DECdtm
* CIXCD-AC adapter storage support (referred to as XCDAC
adapter in the release notes)
* Base system support for POSIX
For a complete list of these and other changes, please refer to the
OpenVMS AXP (TM) V1.5 FT3 release notes.
This kit, its contents, and all related documentation and project
information are Digital Confidential. They should not be
distributed or shown to non-Digital employees without the
express, written consent of OpenVMS product management.
The major system ID number for FT3 has been changed and is different
from OpenVMS AXP (TM) V1.0. Therefore, any privileged layered products
linked against the V1.0 system image (SYS$BASE_IMAGE.EXE) will not
execute on FT3 without re-linking these products.
The DECwindows Motif kit supported for FT3 is the same kit that was
released for OpenVMS AXP V1.0.(DECwindows Motif for OpenVMS AXP V1.1 (SSB))
The Delta FT3 kit contains files that are installed on a disk, which is
then used to run OpenVMS AXP on an Alpha hardware platform, and consists
of the following components:
o nine savesets containing the OpenVMS AXP files to be
installed,
o Release Notes
o this cover letter
o and documentation
Kit Contents (CDROM Locations)
------------------------------
FT3 Kit contents:
cdrom:[000000]
OPENVMSALPHA015.A
OPENVMSALPHA015.B
OPENVMSALPHA015.C
OPENVMSALPHA015.D
OPENVMSALPHA015.E
OPENVMSALPHA015.F
OPENVMSALPHA015.G
OPENVMSALPHA015.H
OPENVMSALPHA015.I
OPENVMSALPHA015.J
OPENVMSALPHA015.K
OPENVMSALPHA015.L
cdrom:[DOCUMENTATION.V015]
CD_USERS_GUIDE_EFT.PS
COMPARE_SYSMGT_EFT.PS
DEBUGGER_SUP_EFT.PS
OPENVMSAXP015_INSTALL_EFT.PS
OPENVMSAXP015_RELEASE_NOTES_EFT.PS
OPENVMSAXP015_RELEASE_NOTES_EFT.TXT
OPENVMS_DOC_OVERVIEW_EFT.PS
OPENVMS_PROG_CONCEPTS_EFT.PS
SYSMGT_1_EFT.PS
SYSMGT_2_EFT.PS
VMSCLUSTER_MANUAL_EFT.PS
OPENVMSALPHA015_COVER_LETTER.TXT
cdrom:[DECW$BOOK]
APH_SHLF.DECW$BOOKSHELF
CALL_STD.DECW$BOOK
CDU_LIB.DECW$BOOK
CD_USE.DECW$BOOK
D32VBKRD.DECW$BOOK
DCL_DICT.DECW$BOOK
DCNT_MAN.DECW$BOOK
DEBUG.DECW$BOOK
DECTHRED.DECW$BOOK
DELTA.DECW$BOOK
DOC_OVRV.DECW$BOOK
DPML.DECW$BOOK
EVE_REF.DECW$BOOK
FILE_APP.DECW$BOOK
GDE_DCNT.DECW$BOOK
GLOSS.DECW$BOOK
HELP_MSG.DECW$BOOK
INSTL_10.DECW$BOOK
IO_REF.DECW$BOOK
LIB.DECW$BOOK
LIBRARY.DECW$BOOKSHELF
LINKER.DECW$BOOK
MOD_PROC.DECW$BOOK
NCP_DCNT.DECW$BOOK
OTS.DECW$BOOK
PLAN_MIG.DECW$BOOK
PORT_MAC.DECW$BOOK
PPL.DECW$BOOK
PREF_SHF.DECW$BOOKSHELF
PRG_CONC.DECW$BOOK
PRG_ENVR.DECW$BOOK
PRG_INTF.DECW$BOOK
PRG_SHLF.DECW$BOOKSHELF
RECOMLNK.DECW$BOOK
REL_SHLF.DECW$BOOKSHELF
RMS_REF.DECW$BOOK
RMS_UTIL.DECW$BOOK
RNTS_10.DECW$BOOK
SDA_ALP.DECW$BOOK
SECUR_AL.DECW$BOOK
SMG.DECW$BOOK
STR.DECW$BOOK
SYS_COMP.DECW$BOOK
SYS_MAN.DECW$BOOK
SYS_SERV.DECW$BOOK
SYS_SHLF.DECW$BOOKSHELF
SYS_UTIL.DECW$BOOK
TPU_GD.DECW$BOOK
TPU_REF.DECW$BOOK
USR_MAN.DECW$BOOK
USR_SHLF.DECW$BOOKSHELF
UTIL_RTS.DECW$BOOK
VMSINSTL.DECW$BOOK
WAN_IO.DECW$BOOK
The first twelve files are the savesets to be installed. The other files
are the release notes, installation guide, this cover letter, and general
documentation in bookreader, postscript, and text format.
Internal Network FT3 Kit Locations
----------------------------------
For the FT3 kits, we will be using the following sites as
network distribution points in order to offload BULOVA. The entire kit,
including the documentation and licenses (for internal sites), will be
available at each of these sites. Please note that all of the files
listed above are included at these locations in the [DELTA_FT3] directory.
BULOVA::ALPHA$KITS:[DELTA_FT3] Nashua, NH, USA
CACTO6::ALPHA$KITS:[DELTA_FT3] Chicago, IL, USA
XLIB::ALPHA$KITS:[DELTA_FT3] Marlboro, MA, USA
AMCUCS::ALPHA$KITS:[DELTA_FT3] Mountain View, CA, USA
AVOLUB::ALPHA$KITS:[DELTA_FT3] Livingston, Scotland, UK
AMCDCO::ALPHA$KITS:[DELTA_FT3] Landover, MD, USA
VISA::ALPHA$KITS:[DELTA_FT3] Valbonne, France
Revised Documentation for FT3
-----------------------------
The following manuals have been revised for FT3 (External Field Test)
and are available in both PS and DECW$BOOK formats. If you have a
mixed cluster running VAX VMS Version 5.5-2 and FT3, please refer
to your VAX VMS Version 5.5-2 documentation set for information on
VAX VMS functionality. The differences in system management between
VAX VMS Version 5.5-2, OpenVMS AXP Version 1.5, and OpenVMS VAX
Version 6.0 are described in the manual "A Comparison of System
Management on OpenVMS VAX and OpenVMS AXP."
OpenVMS Debugger Supplement for Version 1.5 EFT
DEBUGGER_SUP_EFT.PS;1
DEBUG_EF.DECW$BOOK
OpenVMS System Managers Manual: Essentials
SYSMGT_1_EFT.PS;1
SYS_MAN.DECW$BOOK;1
OpenVMS System Managers Manual: Tuning, Monitoring, & Complex Systems
SYSMGT_2_EFT.PS;1
SYS_MAN.DECW$BOOK;1
OpenVMS AXP V1.5 Upgrade and Installation Manual
OPENVMSAXP015_INSTALL_EFT.PS;1
INSTL_15.DECW$BOOK;1
A Comparison of System Management on OpenVMS VAX and OpenVMS AXP
COMPARE_SYSMGT_EFT.PS;1
SYS_COMP.DECW$BOOK;1
OpenVMS AXP V1.5 Release Notes Manual
OPENVMSAXP015_RELEASE_NOTES_EFT.PS;1
OPENVMSAXP015_RELEASE_NOTES_EFT.TXT;1
RNTS_15.DECW$BOOK;1
OpenVMS AXP Version 1.5 Compact Disc User's Guide
CD_USERS_GUIDE.PS
CD_USE.DECW$BOOK
Overview of OpenVMS Documentation
OPENVMS_DOC_OVERVIEW_EFT.PS;1
DOC_OVRV.DECW$BOOK;1
OpenVMS Programming Concepts Manual
OPENVMS_PROG_CONCEPTS_EFT.PS;1
PRG_CONC.DECW$BOOK;1
VMScluster Systems for OpenVMS
VMSCLUSTER_MANUAL_EFT.PS;3
CLUSTER.DECW$BOOK;1
Bookshelf files
----------------
APH_SHLF.DECW$BOOKSHELF;4
LIBRARY.DECW$BOOKSHELF;3
PREF_SHF.DECW$BOOKSHELF;2
PRG_SHLF.DECW$BOOKSHELF;2
REL_SHLF.DECW$BOOKSHELF;2
SYS_SHLF.DECW$BOOKSHELF;1
USR_SHLF.DECW$BOOKSHELF;2
The following manuals have not been updated for FT3 (EFT) but are
provided on this kit in their Version 1.0 format:
OpenVMS Users Manual
USR_MAN.DECW$BOOK;1
OpenVMS DCL Dictionary
DCL_DICT.DECW$BOOK;1
Guide to OpenVMS Alpha Security
SECUR_AL.DECW$BOOK;1
OpenVMS System Management Utilities Reference Manual
SYS_UTIL.DECW$BOOK;1
DECnet for OpenVMS Networking Manual
DCNT_MAN.DECW$BOOK;1
DECnet for OpenVMS Guide to Networking
GDE_DCNT.DECW$BOOK;1
DECnet for OpenVMS Network Management Utilities
NCP_DCNT.DECW$BOOK;1
OpenVMS Glossary
GLOSS.DECW$BOOK;1
OpenVMS System Messages: Companion Guide for Help Message Users
HELP_MSG.DECW$BOOK;1
Migrating to an OpenVMS Alpha System: Planning for Migration
PLAN_MIG.DECW$BOOK;1
Migrating to an OpenVMS Alpha System: Porting VAX MACRO Code
PORT_MAC.DECW$BOOK;1
Migrating to an OpenVMS Alpha System: Recompiling and Relinking
Applications
RECOMLNK.DECW$BOOK;1
Using Bookreader
D32VBKRD.DECW$BOOK;2
OpenVMS Calling Standard
CALL_STD.DECW$BOOK;1
DPML, Digital Portable Mathematics Library
DPML.DECW$BOOK;1
Guide to OpenVMS File Applications
FILE_APP.DECW$BOOK;1
OpenVMS I/O User's Reference Manual
IO_REF.DECW$BOOK;1
OpenVMS Linker Utility Manual
LINKER.DECW$BOOK;1
OpenVMS Alpha System Dump Analyzer Utility Manual
SDA_ALP.DECW$BOOK;1
OpenVMS Command Definition, Librarian, and Message Utilities Manual
CDU_LIB.DECW$BOOK;1
OpenVMS Debugger Manual
DEBUG.DECW$BOOK;2
Guide to DECthreads
DECTHRED.DECW$BOOK;2
OpenVMS System Services Reference Manual
SYS_SERV.DECW$BOOK;1
OpenVMS Programming Environment Manual
PRG_ENVR.DECW$BOOK;1
OpenVMS Utility Routines Manual
UTIL_RTS.DECW$BOOK;1
OpenVMS Record Management Services Utilities Reference Manual
RMS_UTIL.DECW$BOOK;2
OpenVMS Record Management Services Reference Manual
RMS_REF.DECW$BOOK;1
OpenVMS RTL Library (LIB$) Manual
LIB.DECW$BOOK;1
OpenVMS RTL General Purpose (OTS$) Manual
OTS.DECW$BOOK;1
OpenVMS Parallel Processing (PPL$) Manual
PPL.DECW$BOOK;2
OpenVMS RTL Screen Management (SMG$) Manual
SMG.DECW$BOOK;1
OpenVMS String Manipulation (STR$) Manual
STR.DECW$BOOK;1
OpenVMS Programming Interfaces: Calling a System Routine
PRG_INTF.DECW$BOOK;1
Guide to Creating OpenVMS Modular Procedures
MOD_PROC.DECW$BOOK;1
OpenVMS Wide ARea Network I/O User's REference Manual
WAN_IO.DECW$BOOK;1
Guide to DECtpu
TPU_GD.DECW$BOOK;1
DECTPU Reference Manual
TPU_REF.DECW$BOOK;1
OpenVMS Delta/Xdelta Debugger Manual
DELTA.DECW$BOOK;1
EVE Reference Manual
EVE_REF.DECW$BOOK;1
OpenVMS Developer's Guide to VMSINSTAL
VMSINSTL.DECW$BOOK;1
Installing the Kit
------------------
The Installation Guide for FT3 is available in the file
OPENVMSAXP015_INSTALL_EFT.PS. Please refer to the Installation
Guide for detailed installation instructions. You should copy
and read the Installation Guide and the Release Notes before
attempting installation of the kit.
FT3 will support the following two system upgrades:
OpenVMS AXP V1.0 ----> FT3
OpenVMS AXP T1.5 (IFT2) ----> FT3
Bug Fixes During FT3
--------------------
All of the bug fixes accepted into OpenVMS AXP V1.0 have been folded
into FT3. As other bug fixes and workarounds are identified, they will
be placed into the following location (for internal sites only).
BULOVA::ALPHA$KITS:[DELTA_FT3.UPDATE]
Bug fixes and workarounds to problems will also be announced in the
VAXWRK::ALPHANOTES notes conference. Topic 1517 has already been
reserved for this purpose. This mechanism will only be used for
critical bug fixes.
Licenses
--------
Paper licenses will be issued for FT3 for external field test sites.
Licenses for the base kit, DECwindows Motif, DECnet, and VMSCLUSTERS
are provided for internal sites and may be found on:
BULOVA::ALPHA$KITS:[DELTA_FT3.PAKS]
Cross tools for FT3
-------------------
Associated with the FT3 kit is another release of the Alpha VMS
Cross-Development Tools kit, containing the tools used to build
FT3. Please refer to the Release Notes for the Cross-Development
Tools kit for further details. The Cross-Development Tools kit
can be found in BULOVA::ALPHA$XTOOL_KITS:[X026]. Please note that
this toolkit is for internal use only.
Bug Reporting
-------------
To report a bug, please use the QAR system. Two separate QAR
databases have been established for FT3. Internal Digital sites
should continue to use "EVMS-DELTA". All external customer field
test sites should use "EVMS-DELTA-FT". Both of these databases are
located on node TRIFID. To log a problem report for an internal site,
set host to TRIFID, username QAR_INTERNAL, password QAR. At the "QAR>"
prompt, use the ENTER command to log a new problem report. Please give
the version as "T1.5-FT3". External field test customers will be
given their own special QAR accounts to use in accessing TRIFID. Online
HELP is available.
Notes Conference for OpenVMS Alpha
----------------------------------
Continuing with FT3, we will use the VAXWRK::ALPHANOTES
conference for kit announcements and general discussion of
OpenVMS Alpha. Please use the QAR system to report actual bugs.
Do not assume that a problem reported only in the ALPHANOTES
conference will be adequately investigated or resolved.
Alpha Systems Firmware Tested for OpenVMS
-------------------------------------------
System DEC/3000 DEC/3000 DEC/3000
Component Model 300 Model 400 Model 500 DEC/4000 DEC/7000
(Pelican) (Sandpiper) (Flamingo) (Cobra) (Laser/Ruby)
PALcode 5.37 5.37 5.37 5.37 5.37
Console V2.0 V2.0 V2.0 T2.7 X2.0
We recommend updating the firmware before performing the upgrade
from OpenVMS AXP (TM) V1.0 to FT3
Last Minute Notes, Restrictions, and bug fixes.
-----------------------------------------------
1. ANALYZE/PROCESS_DUMP
This is currently only working properly when the DELTA debugger is
the default debugger by setting the logical name LIB$DEBUG to DELTA.
Ordinarily, DEBUG is the default debugger used with
ANALYZE/PROCESS_DUMP, but this will either not work at all or
produce unpredictable results. To use DELTA as the debugger for
ANALYZE/PROCESS_DUMP, it must be installed. Once SYS$LIBRARY:DELTA.EXE
is installed, it is only necessary to define LIB$DEBUG to be DELTA
to make DELTA the default debugger for ANALYZE/PROCESS_DUMP.
2. ISL
If you are using the Infoserver to perform installations, you must
set the Infoserver group code to 0 (the default). The ability to
change group codes will be available in FT4.
3. DEC 3000 Model 300 (Pelican) console
If you use Alternate console to boot your DEC 3000 Model 300 system,
(Pelican) the graphics monitor will not work correctly.
4. DEC COBOL
This field test of the OpenVMS AXP Operating System V1.5
replaces certain run-time files needed by sites using DEC COBOL
T1.0-583. The DEC COBOL T1.0-583 kit (also known as the external
field test kit, dated January 13, 1993) contains newer versions of
these files. Please re-install the COBOL kit after installing FT3
This is a temporary problem for this field test. We do not expect
this to be necessary for the general release of either DEC COBOL or
the OpenVMS AXP Operating System V1.5.
5. Batch/Print
Due to incompatibilities between the Batch/Print subsystems in
OpenVMS AXP V1.0 and FT3, data in the old queue file will be lost
during the course of performing an upgrade. Therefore, make sure
to flush all of your queues before performing an upgrade to FT3
6. DECthreads Restriction
Use the Default extern Model when Compiling DECthreads Programs
Written in C. The DEC C compiler on OpenVMS AXP supplies several
different models for providing storage for extern
variables. Code compiled separately using different extern
models does not necessarily interoperate. DECthreads
exports several values via extern variables; in particular,
predefined exception objects.
In FT3 and previous releases of OpenVMS AXP, the
DECthreads header files do not specify a particular extern
model for these variables. Therefore, because DECthreads
is compiled using the default extern model ("RELAXED_
REFDEF") in FT3 and previous releases, any code
that uses DECthreads in these releases should be compiled
with the default extern model or should explicitly specify
"RELAXED_REFDEF" or "STRICT_REFDEF". Compiling with the
other extern models may cause strange behavior, such as
causing exceptions and alerts or cancels to be caught in a
CATCH_ALL block instead of an explicit CATCH block.
If specifying one of the other extern models is required in
order to compile the code correctly, bracket the inclusion
of any DECthreads header files with lines similar to the
following:
#pragma __extern_model __save
#pragma __extern_model __strict_refdef
#include <cma.h>
#pragma __extern_model __restore
This problem will be resolved and the restriction lifted
for the final version of OpenVMS AXP V1.5 by including the
#pragma statements inside the DECthreads header files.
7. DECwindows transport attach problem
A process will hang attempting to attach to a transport which
is not installed on the system. For example, the server process
will hang at startup if the server logical DECW$SERVER_TRANSPORTS
is defined to be LAT and the image DECW$TRANSPORT_LAT is not
installed. A process will also hang when attempting to run a
DECwindows application using a transport type for which there is
no transport image installed.
Therefore, if the server is hanging, make sure that the logical
DECW$SERVER_TRANSPORTS is defined to be transport types which
are installed on the system. Make sure that the SET DISPLAY command
defines the transport type properly if a DECwindows application
hangs. A typo made in the SET DISPLAY command will cause the
process to hang.
8. System hang in shutdown during an Upgrade
Performing upgrades to FT3 on a DEC/3000 Model 500 may sometimes
result in the system hanging during the 2nd shutdown (after Phase 4
completes). This problem occurs intermittently and is currently
under investigation. If you should encounter this problem, power-
cycle your system and re-boot (you would have been required to
manually reboot the system at this time regardless of whether or not
you had encountered this problem). Please note that encountering this
problem and applying the workaround does NOT affect the success
of the upgrade.
*** DIGITAL CONFIDENTIAL ***
-------------------------------------------------------------------------
<><><><><><><><><><>
| HOW TO SUBSCRIBE |
<><><><><><><><><><>
Send requests to STAR::GEORJEAN.
Please put the following line in your request:
node::user_name ! organization country (if outside U.S.)
example:
star::georjean ! OpenVMS AXP Product Management
*** DIGITAL CONFIDENTIAL ***
|
| 147.5 | CLUSTER SUPPORT FOR ALPHA AXP AHEAD OF SCHEDULE | KERNEL::CLARK | STRUGGLING AGAINST GRAVITY... | Thu Mar 25 1993 09:20 | 107 |
|
DIGITAL ANNOUNCES VMSCLUSTER SUPPORT FOR ALPHA AXP SYSTEMS
WILL SHIP AHEAD OF SCHEDULE
-- Allows customers to integrate VAX and leading price/performance
Alpha AXP RISC systems in the same cluster, or cluster AXP systems
MAYNARD, Mass. -- March 3, 1993 -- Digital Equipment Corporation
today announced that, for the first time, the functionality of the
world's premier clustering environment -- OpenVMS-based clusters --
is now available with the speed and leadership price/performance of
Alpha AXP advanced RISC architecture. Previously scheduled for
delivery in mid-1994, the new Digital offering will provide its
customers the ability to cluster OpenVMS VAX systems with OpenVMS
AXP systems nearly one year earlier.
Now called VMSclusters, to reflect its support on both VAX and
Alpha AXP platforms, the new release will include support for
several types of clustering:
-- Cluster Interconnect (CI)
-- Digital Storage Systems Interconnect (DSSI)
-- Network Interconnect (NI)
-- Mixed Interconnect (combinations of above interconnects)
-- Mixed Architecture Clusters (Alpha AXP and VAX systems in
same cluster)
-- Alpha AXP Clusters
"More than ninety percent of today's VAXcluster customers will
be able to extend the value of their existing configuration by
adding a leading price/performance Alpha AXP RISC system," said
William R. Demmer, Vice President, Computer Systems Group. "Only
Digital can provide such investment protection with the
price/performance and functionality that our open systems can now
deliver. This new VMScluster release is further proof that we are
committed to providing our customers with the dependability and rich
features upon which their businesses have come to rely." He went on
to say, "Our philosophy is to provide choice for users on VAX
systems or Alpha AXP systems -- or a combination of both, for those
who want a mixed architecture environment."
Clustering technology, pioneered by Digital in the early '80s,
allows multiple systems to operate as a single system providing
fault resilience and high availability for applications. In addition
Digital's leadership Cluster technology provides for the ability to
scale application capabilities, as well as sharing of data and
computing resources. Because the physically distributed systems work
as a single virtual system, significant productivity is also
realized by operational support and system management staff. Digital
began shipping VAXclusters in 1983. Since that time, over 25,000
clusters have been built, supporting more than 10 million OpenVMS
users worldwide. With this new announcement, it will now be possible
to build a cluster comprised of 15 Alpha AXP systems with computing
power well in excess of 3,000 SPECmarks of performance which
processes more than 4 Billion Instructions Per Second (BIPS).
Digital's VAXcluster product was rated number one in a
recently-published, industry-wide clusters technology study by the
Aberdeen Group, Inc. of Boston, Mass. "Based on our technology
ratings, and bolstered by broad market acceptance, Aberdeen
concludes that Digital's VAXcluster is today's most mature
clustering implementation," according to the study. Aberdeen Group
examined key areas of cluster functionality on six industry
platforms from four major suppliers: VAXcluster, IBM's MVS mainframe
sysplex and the RS/6000, Hewlett-Packard's MPE Shareplex/iX and
HP-UX, and Sun's Sparcservers.
Volume Shadowing for OpenVMS and VAX Disk Striping software are
separately purchased and licensed layered products, and will be
available for the Alpha AXP platform in the near future. This
release of OpenVMS AXP fully supports the use of native FDDI
adapters as a network interconnect, and VMSclusters fully supports
the use of FDDI as a network backbone interconnecting clusters
nodes. Support for native FDDI adapters as a cluster interconnect
will be available in the near future.
VMSclusters for OpenVMS AXP systems can be ordered today and
will start shipping in the Spring of 1993.
Digital Equipment Corporation, headquartered in Maynard,
Massachusetts, is the leading worldwide supplier of networked
computer systems, software, and services. Digital pioneered and
leads the industry in interactive, distributed, and multivendor
computing. Digital and its business partners deliver the power to
use the best integrated solutions - from desktop to data center -
in open information environments.
####
Note to Editors: Alpha AXP, AXP, the AXP mark, Digital, the Digital
logo, OpenVMS, VAX, VAXclusters, VMS, and
VMSclusters are trademarks of Digital Equipment
Corporation.
Hewlett-Packard, HP-UX, and MPE Shareplex/iX are
registered trademarks of Hewlett-Packard, Inc.
IBM, MVS, sysplex and RS/6000 are registered
trademarks of International Business Machines.
Sparcserver is a trademark of Sun Microsystems,
Inc.
CORP/93/028
|
| 147.6 | CONFIGURATION RULES FOR ALPHA AXP IN CLUSTERS | KERNEL::CLARK | STRUGGLING AGAINST GRAVITY... | Thu Mar 25 1993 09:23 | 216 |
|
Now that VMSclusters for OpenVMS AXP Version 1.5 has been announced and
is public. This information is not considered company confidential and can
be used externally with customers and business partners.
Configuration Support Rules:
CI Support
----------
- A maximum of 3 DEC 7000 and/or DEC 10000 systems are supported on a
single CI bus
- The total number of systems supported (both VAX and AXP ) on a single CI bus
is 8 systems
- A maximum of 2 XMI to CI controllers (CIXCD) are supported in any DEC 7000
and/or DEC 10000 system
- A maximum of two Star Couplers in a single cluster is supported
DSSI Support
------------
- A maximum of 2 DEC 4000 systems are supported on a single DSSI bus
- Tri-host DSSI configurations are supported as long as at least one of the
three hosts on the DSSI bus is a VAX system
- DEC 4000 systems are supported and can co-exist on a DSSI bus with VAX 4000,
VAX 6000, VAX 7000 and VAX 10000 systems connected to it
- DEC 4000 systems are not supported connected to a DSSI bus which has
MicroVAX 3000 class systems connected to it
- DEC 4000 systems cannot co-exist on a DSSI bus with a VAX system which is
connected to that bus using a KFQSA controller
- DEC 7000 and DEC 10000 systems cannot be connected to the DSSI bus
under OpenVMS AXP Version 1.5
Ethernet Support
----------------
- Up to 12 DEC 3000 satellites are supported in a cluster under OpenVMS AXP V1.5
- Up to 2 Ethernet adapters are supported on Alpha AXP systems within a cluster
- DEC 3000, DEC 4000, DEC 7000 and DEC 10000 systems can all serve as boot
nodes for DEC 3000 satellite systems.
Additional Configuration Support Guidelines:
SUPPORTED Configurations
------------------------
- VAX systems running OpenVMS VAX V5.5-2 in a mixed architecture
cluster with OpenVMS AXP systems running OpenVMS AXP V1.5
- Dual Path disks and automatic failover
- Mixed interconnect configurations
- Cluster alias for entire cluster (both VAX and AXP systems)
- Up to 96 nodes in a single cluster (both VAX and AXP systems)
- Up to 15 AXP systems in a single cluster (3 CI AXP, 12 Satellite AXP)
- Unlimited number of HSC's - Limited only by Star Coupler size
- VAX systems serving tape drives to AXP systems
- VAX satellites booting off VAX systems
- Alpha AXP satellites booting off Alpha AXP systems
- Alpha systems sharing a common OpenVMS AXP V1.5 system disk
- VAX systems sharing a common OpenVMS VAX V5.5-2 system disk
- A separate system disk for each architecture (1 for VAX and 1 for Alpha AXP)
- Systems running the OpenVMS V5.5 batch/queue manager
- Clustering 2 DEC 4000 systems using ethernet as the cluster interconnect bus
- Clustering 2 DEC 7000 or DEC 10000 systems using ethernet as the cluster
interconnect bus
UNSUPPORTED Configurations
--------------------------
- Volume Shadowing on Alpha AXP systems (planned for 1st half CY94)
- Disk Striping
- Accessing VAX-based shadowed disks from Alpha AXP systems
- Accessing VAX-based striped disks from Alpha AXP systems
- VAX systems which are not running OpenVMS VAX V5.5-2, and Alpha AXP
systems which are not running OpenVMS AXP V1.5
- More than 96 nodes in a single cluster
- AXP systems serving tape drives to VAX systems or to other Alpha AXP systems
- VAX satellites booting off Alpha AXP systems
- Alpha AXP satellites booting off VAX systems
- VAX and Alpha AXP systems sharing a common system disk containing both
OpenVMS VAX version V5.5-2 and OpenVMS AXP version V1.5 on a single disk
- Systems not running the OpenVMS V5.5 batch/print manager
- Clustering more than 2 DEC 4000 systems using ethernet as the cluster
interconnect bus
- Clustering more than 2 DEC 7000 and/or DEC 10000 systems using ethernet as the
cluster interconnect bus
Software Functionality Included:
- Cluster-wide Shared Disks - Cluster-wide Operator Communications
- Cluster-wide Mount and Dismount - Cluster-wide Show Users
- Cluster-wide Locking - SHOW CLUSTER
- Cluster-wide MSCP Disk Serving - Cluster-wide SHOW SYSTEM
- TMSCP Tape Serving from VAX to AXP - Shared Audit Logs
- Cluster Alias - Shared Mail Profile Database
- Shared Mail Files - Shared User Files
- Shared Rightslist (security) - Shared Proxy Files
- Shared System Authorization File - Cluster-wide Process Services
- Distributed Lock Manager
Ordering Information:
VMScluster Software Licenses (Part Number QL-MUZA*-AA) will be required for
Alpha AXP CPU's in order to enable the use of OpenVMS clustering software under
OpenVMS AXP Version 1.5. VMScluster Software is fully described in the
VMScluster Software Product Description (SPD 42.18.xx)
VAXcluster Software Licenses (Part Number QL-VBRA*-AA) will continue to be
required for VAX CPU's in order to enable the use of OpenVMS clustering
software. VAXcluster software is fully described in the VAXcluster Software
Product Description (SPD 29.78.xx)
Note that every Alpha AXP workstation already includes the NAS250 package.
VMScluster software is bundled with and included in each NAS250 license
package.
Questions and Answers:
Q: A VAX system has a disk which is shadowed to another disk on the same
HSC. Can I access this shadow set of disks by MSCP serving the disks
from VAX to Alpha systems in the cluster?
A: Volume Shadowing is a seperate layered product from the VMScluster layered
product. Volume Shadowing on AXP-based systems requires the presence of
Volume Shadowing for OpenVMS AXP software. To clarify, you cannot access
any shadowed disks in the cluster from an Alpha AXP system. Even if those
disks are shadowed by a VAX in the cluster. This is true for both
Phase I and Phase II shadow sets. The restriction on Phase II shadow sets
will be eliminated when the Volume Shadowing for OpenVMS AXP layered product
becomes available in the near future.
Q: When is Volume Shadowing for OpenVMS Software scheduled to be available
for OpenVMS AXP?
A: Volume Shadowing for OpenVMS AXP is currently scheduled to be available at
the same time as the Epsilon release of OpenVMS AXP (first half calendar
1994).
Q: Can I serve a tape drive from my Alpha AXP system to the other Alpha AXP
systems in the same cluster?
A: No. There is no support under this release of OpenVMS AXP for serving
AXP-based tape drives to any other cluster member (either VAX or Alpha AXP).
This functionality is known as TMSCP serving and will be available with a
future release of OpenVMS AXP. However, VAX attached tape drives
can be served to OpenVMS AXP systems in the same cluster today. Also,
HSC attached tape drives are accessible by both Alpha and VAX systems
in the same cluster.
Q: Can I use FDDI as an interconnect under OpenVMS AXP version 1.5?
A: A native FDDI adapter can be used as a network interconnect under OpenVMS
AXP version 1.5 but it CANNOT be used as a cluster interconnect from Alpha
AXP systems within a cluster. However, FDDI can be used as the cluster
interconnect from VAX systems within a mixed architecture cluster.Native
FDDI adapters will be supported as a cluster interconnect on Alpha AXP
systems in the Epsilon release of OpenVMS AXP currently scheduled to be
available in the first half of CY94. Note that the use of FDDI backbones
with Alpha AXP systems and clustering software is fully supported, what
is not supported is native FDDI adapters with clustering software.
Q: Can I boot an Alpha system off a VAX system if there is an OpenVMS AXP
system disk accessible to the VAX?
A: No. Cross architecture booting is not supported by OpenVMS AXP V1.5
Q: How many Alpha AXP systems could I configure into a single cluster?
A: Three CI based AXP systems and 12 Satellite AXP systems for a total of 15.
Note that such a cluster has more than 3,000 SPECmarks and 4 BIPS (Billion
Instructions Per Second) of processing power!
Q: Can I connect a VAX system running OpenVMS VAX version A5.5-2 to a
cluster which contains AXP systems?
A: OpenVMS VAX version A5.5-2 uses the pre-5.5 OpenVMS batch/que subsystem.
This version of the batch/queue subsystem is NOT supported in a cluster
containing Alpha AXP systems.
Q: Is the cluster-wide distributed lock manager running on Alpha AXP systems
as well as VAX within the cluster?
A: Yes. The same distributed lock manager that runs on OpenVMS VAX systems
has been ported and also runs on all OpenVMS AXP systems within a cluster.
Q: I have a CI-based cluster today which consists of 6 VAX systems and 5
HSC's. How many DEC 7000 AXP systems can I connect to this existing cluster
using OpenVMS AXP Version V1.5?
A: The above rules state that a mixed architecture CI cluster can consist
of 8 systems maximum - this means you can add up to 2 DEC 7000 AXP systems
to your existing cluster.
Q: I have a dual-host VAX 4000-300 cluster with 15 satellites today. Can I
add a DEC 4000 AXP system to the DSSI which would create a tri-host?
A: Yes. This configuration is fully supported given the above guidelines.
Q: Could I then add 12 DEC 3000 AXP satellite systems to this cluster (even
though it already has 15 VAX satellites)?
A: Yes. The addition of these satellites is fully supported under the above
configuration guidelines. Note however, that the configuration will require
at least one AXP-based boot node and the server capacity of the cluster
should be evaluated to make sure that this is a proper configuration
for the layered product and applications (workload) that it will be running.
Q: I know that DECnet Phase IV routing is not available on OpenVMS AXP, what
license is required on OpenVMS AXP systems in order for them to act as
a cluster alias router?
A: A DECnet extended function license is required on a least one DECnet for
OpenVMS AXP node within the cluster in order to use the cluster alias
feature. Alternatively, a VAX node in a mixed architecture cluster could
act as the cluster alias router for both VAX and AXP systems.
|
| 147.7 | ALPHA INFORMATION PACKAGE | KERNEL::CLARK | STRUGGLING AGAINST GRAVITY... | Thu Mar 25 1993 09:45 | 2320 |
|
******** COMPANY CONFIDENTIAL *********
Date : 30-10-1992
Subject : ALPHA Info package
Revision : 1.0
Compiled by : HPS SERVER and CLIENT Segment Teams
Urban Hofstrom/Allan Topp/Richard Lambert/
Guenter Mannsberger/Jean-Jacques Merlet/
Bob Straatsburg
Contents
1 ALPHA Overview
2 Financial overview
3 Service Pricing strategy
COBRA
RUBY
SANDPIPER/FLAMINGO
4 Systems rollout overview
5 Service Delivery
Executive summary by Peter Miller ALPHA Business Director.
PURPOSE OF THIS DOCUMENT
The purpose of this document is to provide the Country HPS Mgrs
with sufficient information to prepare the ALPHA launch.
The document is intentionally made HPS specific. The overall
DS coordination is done by Geroge Mcgee @VBO.
Chapter 2 covers the pricing for the first Alpha products to be announced.
Executive Summary
Market Analysis
By 1995 ALPHA can permeate most of the computer marketplace.
Initial products in 1992 will primarily address high-end,
compute-bound, technical applications. However the hardware,
operating systems and layered software introduced throughout 1993
will expand ALPHA into all markets currently addressed by OpenVMS,
ULTRIX and high-end Intel-based systems.
Low cost ALPHA chips, available by 1994, will permit the development
of competitive personal systems, intelligent peripherals and non
information management but computer controlled appliances. In order
to drive down costs we need volume and so a major early objective is
to build market demand for the ALPHA architecture.
Assuming widespread deployment of the architecture we will see high
volume platforms for software sales and for product support and
consulting services. These latter businesses will deliver the
majority of European profit by FY97.
There are 5 major sources of revenue and profit from ALPHA these
being :-
o Systems sales - desktop to datacentre
o Services - all lines of business
o Software - operating systems, middleware, applications and
networking
o Components - chips, boards and software
o Licenses - architecture, chip manufacture, software etc
Significant work will be necessary to build the appropriate channels
models for both sales and services. This is a critical success
factor to achieving volume for Digital's own systems sales.
ALPHA, whilst having about a 20% performance advantage for the next
two years and also being leadership technology, will not alone
create customer demand. Investments must be made to attract
applications from major ISV's outside of our current base and from
other existing Digital platforms on to ALPHA.
Key Business Strategies
ALPHA & New Business Development:
o Make ALPHA the preferred development platform for CSO's -
re-attract lost partners and keep new ones.
o Re-establish Digital as a preferred supplier to embedded TOEM's.
o Make ALPHA the preferred platform for Windows-NT for both client
and server environments.
o Ensure that ALPHA has access to the best UNIX software based on
OSF technologies.
o Capitalise on the downsizing trend in the mainframe business.
o Reach 10% market share of desktop systems in $3K to $25K price
bands by FY95.
o Develop necessary volume channels of distribution.
o Develop a "Let's Beat SUN" strategy.
ALPHA Systems Business Strategies:
o Establish ALPHA as the pre-eminent open architecture - ensure
that the widest possible audience can use the systems through the
availability of multiple operating systems, license the
architecture, the chip manufacturing process, software etc
o Use ALPHA in the short term (to mid FY94) to sell todays VAX and
MIPs based products through the ALPHA-ready programme - really
promote investment protection.
o Generate excitement through incremental, off-the base activity
focused on the applications now possible because of ALPHA's
unique selling propositions (performance, scalability and
open-ness).
o Implement an aggressive seed unit programme to attract the best
applications from targeted CSO's and ISV's.
o Sell ALPHA products at all levels of integration - re-establish
our TOEM presence.
ALPHA Services Business Strategies:
* Manage the installed-base revenue stream by providing support and
services to end-users (both technical and commmercial)who want to
port their applications to an Alpha platform
* Use Alpha as a catalyst to develop an application re-engineeering
portfolio/capability (targetted at the IT downsizing market) and
integrate with the SI business enterprise
* Extend the installed base by supporting cross-industry
competitive replacement programmes with tools and services to
move customers from competitive UNIX platforms to ALPHA/OSF
* Create a comprehensive service offering to help attract other
vendors and TOEMs to Alpha
* Work within overall MVS strategy to make Digital the premier
services provider for non-Digital Alpha based-systems and related
software
* Exploit the volume opportunity for desktop services around the
ALPHA/PC business initiatives
* Invest in technology-related services for "new-wave"
applications enabled by ALPHA
ALPHA Partnering Strategies
o Target major European IT companies as licensees of the ALPHA
architecture (Olivetti, ICL, Siemens-Nixdorf and Bull)
o Target telecom equipment manufacturers for volume chip and board
design-in (Thompson, Alcatel, Ericcson...)
o License chip fabrication to one major European semi-conductor
manufacturer (preferrably Siemens)
o Encourage European micro-electronics industry to converge on
ALPHA as the preferred European micro-processor architecture.
o Negotiate a licensing arrangement to get access to UNIX System V
(Destiny) on ALPHA.
ALPHA Applications Strategies
o Ensure Digital has the most complete portfolio of applications in
all its target markets available on ALPHA-based products.
o Work with the IBU's and the European Industry Enterprises to
target new and innovative uses of ALPHA.
o Ensure that all required applications on existing Digital
platforms are ported and available on ALPHA-based products.
o Ensure sufficient resources are in place to help end-users port
their in-house developed applications (a DS revenue generation
opportunity).
ALPHA Channel Strategies
o Aggressively develop VAR channels - particularly for the
ALPHA-PC.
o Exploit existing channels such as DEE and DECdirect.
o Transition end-user account teams towards demand creation
activities with fulfilment being handled by indirect methods.
o Use TOEM capability to win design-ins outside of the computer
industry.
o Ensure that DPP and Product-by-Channel are implemented
consistently and effectively.
o Implement "Value Selling" principles within all Account Teams.
o Use ALPHA as a catalyst to change the cost model for selling.
1 ALPHA Overview
Digital Product Services makes Alpha AXP happen for customers by
acting as the catalyst for their seamless transition to 21st century
computing. Digital does this through a worldwide service
organization that ensures the successful integration of people,
business and technology.
For both vendors and direct customers, Digital makes Alpha AXP work
with a complete range of Alpha AXP services that provide the easy
transition to the benefits of Alpha AXP technology. Digital is the
only information technology vendor offering a dedicated set of
multivendor services focused on smoothly integrating Alpha AXP
technology with existing multivendor environments.
Digital's Alpha AXP Vendor Services provide a full range of vendor
support services including: design-in consulting, vendor training,
application porting and management support (hotline, helpdesk), as
well as support for the vendor's products and end-users.
Digital's network and system management services also include new
DecAthena Services for Alpha AXP/OSF.
Hardware/Software System Services
---------------------------------
Digital extends the the same consistent quality of hardware,
software and applications support on Alpha-AXP systems that customers
have come to expect on existing Digital systems. Hardware services
include next day and 4 hour on-site response services as well as a
variety of carry-in and mail-in services. Software support is
available for initial and update installation, media and
documentation distribution, telephone support from Customer Support
Centers worldwide, as well as services for system optimization and
software resource management. Flexible choices of support, matching
the specific needs of the customer, are available electronically, by
phone or on-site.
Vendor/Developer Support Services
---------------------------------
With the announcement of Alpha-AXP, Digital re-affirms it's
commitment to multivendor support, both to vendors designing with the
Alpha chip as well as to Software Developers. Among the services
included are :
- Design-In Integration Services - customized design, manufacturing
and integration services targetted to TOEMs and volume end-users who
will employ the Alpha-AXP technology but require unique
specifications to operating systems, I/O buses or other
interconnects.
- Vendor Training courses
- Application Porting and Developer Software support
- Multivendor Support Programs: Digital is committed to support
other vendor's systems that utilize Alpha AXP with the same
level of support supplied to Digital products.
Overall Marketing message:
Digital Services
.The smooth way into the new era of 21th century computing.
.Getting the maximum out of your Alpha AXP systems.
Systems and maintenance support
Succesful Information Technology systems require more than state of the
art technology components.
A wide range of services to meet your specific needs, designed primeraly
to prevent system downtime and detect potential performance degradation in
early stages are required for optimal and cost effective usage.
With the introduction of the Alpha-AXP systems, Digital provides you with
a broad services product selection that best suits your individual needs,
irrespective where you are between the large, experienced (OEM) customer who
prefers to maintain all or part of the Alpha systems or if you are the Alpha
end-user, who should not be worried about continuity and integrity of the
applications.
Maintenance for optimal usage requires high-tech methods:
Like for the VAX family, it is all available for Alpha:
.Round the clock Expert System Monitoring and early fault detection
.Automatic reassignment of critical subsystems
.Predictive Service technology and diagnostic tools.
.Integrated Remote diagnostics and performance monitoring capabilities
.Access to International network of highly qualified technical specialists,
using Expert systems technologies and extensive solution databases from
our customer support centres and engineering groups.
.Automatic distribution of new software releases on CD-ROM
.Single point of contact for hardware-software problems through customer
support centres.
.Guaranteed response times are the standards from where we start,
specific arrangements to meet your critical needs and specific service
coverage extensions are possible of course.
.Customized Service arrangements with our new partners using the exciting
new Alpha technology and software platforms to maximize each other's
capabilities and experience.
2 FINANCIAL OVERVIEW
HPS NOR MODEL FOR ALPHA
Financial Model
NOR GROWTH MODEL
ITEM 92 93 94 95 96 97
------------------------------------------------------------------
ALPHA SERVER
BASE 0 0 8 13
LOSS 0 0 1 1
SHIPS 0 154 648 728
XFER 0 8 32 36
PENETR 0 0 6 26
------------------------------------------------------------------
NOR (M$) 0 8 45 74
__________________________________________________________________
ALPHA CLIENT (workstations)
NOR 8 57 123
------------------------------------------------------------------
TOT (M$) 16 102 197
------------------------------------------------------------------
A total Alpha impact analysis is being performed and will be published
in December.
ASSUMPTIONS AND NOTES
NOR GROWTH MODEL
1. Shipment data is taken from the 8 quarter volume plan (Jun 92
version) and includes High end,Mid range and Entry level categories.
2. Revenue transfer is taken as 5% of list price for both VAX and
ALPHA.
3. The shipment data used is based on Kernel shipments plus 50% of all
storage product.
4. Alpha losses are assumed to be 10% per annum and Alpha penetration
onto contract is taken to be 90% throughout.
5. The model assumes that maintenance revenue will be the same as
Revenue Transfer i.e 5% of Selling Price.
6. The storage element of the Shipment plan is $250M for FY92, FY93,
FY94 and FY95. The model assumes a drop to $200M in FY96 and to
$150M in FY97.
7. All values are in constant Dollars (Millions)
8.The model calculates in the following way.....
(a) Losses are the defined % of the BASE.
(b) XFER is 5% of that year's SHIPS.
(c) PENETRATION is the defined % of the previous year's XFER.
(d) BASE is the BASE less LOSSES plus PENETRATION of the previous
year.
(e) NOR is the BASE less the LOSS plus the XFER plus the PENETRATION
for any year in question.
9. Revenue generating programs have not been accounted for in this
revenue model.
10. 65% penetration and on that 80% retention for the WS space
3 SERVICE PRICING STRATEGY
The pricing strategy for the ALPHA family of products is described below.
The strategy is to keep service price constant with each succeeding
generation of systems.
Service Pricing Strategy for the ALPHA products.
1. Support the Product Business strategy to double performance and keep price
constant with each succeeding generation of systems.
2. Position service pricing to be relatively constant and consistent with
those prices established for the existing systems as well as
with those of the replaced.
3. Work toward matching competitive service pricing at the system level
while recognizing the very different service revenue goals for Digital
vs competition.
4. Support the Product Businiess price positioning goal which is to achieve
proper competitive positioning at the solution cost of ownership level.
5. Achieve a minimum 50% gross margin for services.
3.1 COBRA
The Cobra Family of systems is targeted to capture increased shares of
two distinct markets - the UNIX systems market and the non-UNIX systems
market in the $75K to $250K price bands.
The UNIX market is the fastest growing segment within the target price band.
Growth in this segment is at the expense of non-UNIX (proprietary) systems.
The objective of these products is to capture 8% of the market by 1995.
Estimates of the market size, in the price band of interest, is $ 6.1B,
making the Cobra revenue from this segment $490M.
The non-UNIX segment of the market in this price band in 1995 is estimated
at $ 8.9B. The Cobra objective is the maintain the current Digital share
in this market at 14%. This translates into a revenue of $ 1.3B for Cobra
with OpenVMS in 1995.
Service Pricing Objective and Strategies
========================================
Service Price Objective
. Complement the product pricing strategy to be the best
price performance system (high performance,aggressive price)
. Deliver a 50% margin for service
. Price competitively with a focus on the future
Service Price Strategy
. Price DSS for all Cobra systems. SUSL and SW Telephone support
have the same price component for both OSF and VMS Systems
. Set a service price that is competitive at the entry level that
reflect the competitive situation six months in to the future
when the competitors have equal products.
. Balance the service price to compete a the DSS level.
Service Warranty / Profile
===========================
In Europe Cobra Warranty is one year DEC System Support (DSS)
3.2 INTERNAL/EXTERNAL POSITIONING COBRA
Service Positioning
===================
Cobra, as the only OSF/1 and AlphaVMS product in the $75k to $250K price
range has an extensive competitive situation to cope with. The same
situation applies to service environment.
The Cobra service price is designed to compete at the entry level of the
technical market where the Cobra systems will make there initial
thrust. The hardware for Cobra H and B is similar which accounts for
the similarity in service prices.
The IBM service price comparison is at the Cobra 24X7 rates with is
standard for IBM.
The ADSS% is increasing as a function of the decreased ASV values of the
new ALPHA systems.
Internal Competition
====================
ENTRY LEVEL SYSTEMS
-------------------------------------------------------
| VAX/VMS VAX/VMS FLAMINGO DECsystem COBRA |
| 5900 |
|Entry 4000-500 4000-600 OSF/1 Ultrix OSF/1 |
|Level |
|System $94K $134K $52 $162k |
| |
|HPS |
|Service $449 $550 $320 $684 |
|Price |
|ADSS% 6% 5% 7% 5.1% |
-------------------------------------------------------
External Competition
====================
Comparison based on UK and US data.
External External
Commercial Market Competitive Technical Market Competitive
Positioning for Services Positioning for Services
--------------------------------------- ---------------------------------------
| Company System MLP Service | | Company System MLP Service |
| ------------------------------------| | ------------------------------------|
| ------------------------------------| | ------------------------------------|
| HP 3000 957 $120.8K $432 | | SUN 630MP M-120 $66.3K $456 |
| 4.3% | | SPARC 8.2% |
| 967LX $130.8K $432 | | Server M-140 $89..2K $496 |
| 4.0% | | 6.7% |
| 967 $189.8K $592 | |-------------------------------------|
|-------------------------------------| | SUN 670MP M-120 $81.9K $496 |
| HP 9000 847S $101.8K $352 | | SPARC 7.2% |
| 4.1% | | Server M-140 $89..2K $536 |
| 857S $129.5K $595 | | |
| 5.5% | |-------------------------------------|
| 867S $134k $632 | | SUN 690MP M-120 $114.9K $628 |
| 5.7% | | SPARC 6.5% |
| 877S $162.4K $712 | | Server M-140 $137.2K $688 |
|-------------------------------------| |-------------------------------------|
| IBM AS/400 E60 $278.9K $1273* | | IBM 550 $69KK $625* |
| 4.4% | | RS/6000 10.8% |
| (today E70 $393K $1437* | | 560 $74K $625* |
|-------------------------------------| |-------------------------------------|
| Digital Cobra $162K $684 | | Digital Cobra $162K $684 |
| 5.1 | | 5.1% |
--------------------------------------- ---------------------------------------
All competitive product prices include one year Warranty
(*****) Most likely Competitors * Service = 24X7
HP Pricing is expected to be brought down 20% to 30% from the indications in
the chart.
Risks
=====
Product acceptance is based on the migration strategy and application
available to attract new markets. The current volumes which drive
service revenue are still changing. The PCU is working to educate the
sale force about the product to aid in the forecasting process.
The engineering group for Cobra is the same group the produced todays
MicroVAX. The experience this group plus the new design tool that
were employed minimize the reliability risk.
The service delivery process is at the greatest risk. Advance service
tools are still in development and two new operating systems are being
introduced (OSF/1 and AlphaVMS). And, the cost of material is such
there is no room for trial and error.
3.3 SERVICE PRICING COBRA
For the COBRA the new otions to be priced are the COBRA CPU and
I/O Board.
All other components are standard components and are already priced.
In order to support the product business to maximaize their market share
and maintain our service penetration the following pricing has been set.
ESRP Service Prices
===================
DSS
KN430 COBRA B CPU $180
KNF40 COBRA I/O SCSI $123
KNF4X COBRA I/O DSSI $164
BA640 COBRA P/S -PLATFORM $ 65
COBRA SYSTEM To be priced Sum Of Pieces by using the 2020 config sheet
distrubuted by EPG (European Pricing Group).
COBRA RACK MOUNTED SYSTEM SOP
UNIQUE OPTIONS
- MEMORY 2.5% CLP
3.4 RUBY
Ruby is a new Alpha processor design. It operates with either of the new
operating systems, OpenVMS or OSF1. Ruby will replace the VAX 6000 series
of systems. The previous NEON system is the VAX version RUBY is the ALPHA
version.
Neon is a new implementation of the NVAX processor, the VAX 6000 processor.
This processor operates with the standard VMS and is viewed as a transition
product. It allows customers with existing VMS systems to add NeonL
systems to their clusters with a minimum of concern.
In the future customers with NeonL systems will upgrade to RubyL or RubyB
systems. That upgrade will consist of changing the CPU and one other
assembly in the system together with the software.
SERVICE STRATEGY
Service Pricing Strategy
Ruby were priced using the following strategy:
o Systems prices are competitive in the marketplace.
o Neon and Ruby priced the same.
This pricing strategy supports both the business goals of HPS and the PCU
strategy of using Neon as a transitional product. Whatever the product
selection criteria of the customer, service pricing will not be an issue.
Warranty Portfolio
RubyL are VAX6000 replacement products and are offered with
traditional warranty one year DSS in Europe.
RUBY POSITIONING
================
Positioning based on US data and UK data.
----------------------------------+--------------------------------------
RUBY VAX6610 | RS6000 Sun HP9000 HP9000
| 950 690 MP M877 H897
|
__________________________________|______________________________________
RANK | #1 #2 #3
|
SYSTEM PRICE $160K $183K | $95K $100K $166K $112
1 YR HW WARR |
& INSTL. |
__________________________________|______________________________________
MEMORY 64 MB 64 MB | 64 MB 64 MB 64 MB 64 MB
|
DISK 1.3 GB 1.0 GB | 1.7 GB 2.6 GB 4 GB 1.6 GB
|
TAPE RRD 42 - - | - - 644 MB CD 2 GB 2 GB
|
O/S OSF1/VMS VMS | AIX V3 SunOS HPUX HPUX
2 User 0 User | 0 User 2 User 8 User 8 USER
|
HW SVC $780 $871 | $833 $936 $1113 $720
| $900(4hr)
|
ADSS HPS % 5.9% 5.7% | 10.5% 11.3% 8.0% 8%
(10%)
==========================================================================
3.4.1 SERVICE PRICING RUBY
Price the Ruby CPU the same as the NEON CPU.
All other components are standard components and are already priced.
New Part ESRP
Numbers Noun DSS
H9F00 POWER & PACK 147 $
AA/AB/AC
H9F00B Exp Cab 60 $
KN7AA-AA RUBY CPU 410 $
KZMSA-AB XMI TO SCSI ADA 58 $
H7263-AA/AB 48V REG 27 $
RUBY systems to be priced Sum Of Pieces using the 2020 config
spreadsheet distributed by EPG ( European Pricing Group ).
3.5 FLAMINGO/SANDPIPER
These products represents the new ALPHA technology in the workstation
space. Flamingo is positioned in the high-end workstation range and
has performance above 117 spec marks. Flamingo is proposed either as
workstation or workstation server.
Sandpiper is positioned in the workstation midrange space and is ranked
103 spec marks. In the near future other ALPHA workstation will be
announced for the low-end workstation segment.
For FY93 these new workstations will exist in parallel with the actual
Vaxstation family and DECstation family (MIPSCO R3000/4000).
From now specific migration programs will be proposed to our Customers
from installed base to the New ALPHA technology.
Flamingo and Sandpiper service pricing will be positioned according to
the same strategy as Cobra and Ruby.
The Kernel Flamingo will be priced slightly above Cougar. The Sandpiper
Kernel will be priced slightly lower.
The ALPHA-AXP workstation announcement is split as below :
- New systems :
ALPHA-AXP SANDPIPER WORKSTATIONS OSF/1,
ALPHA-AXP SANDPIPER WORKSTATIONS OpenVMS,
ALPHA-AXP SANDPIPER SERVERS OSF/1,
ALPHA-AXP SANDPIPER SERVERS OpenVMS,
ALPHA-AXP FLAMINGO WORKSTATIONS OSF/1,
ALPHA-AXP FLAMINGO WORKSTATIONS OpenVMS,
ALPHA-AXP FLAMINGO SERVERS OSF/1,
ALPHA-AXP FLAMINGO SERVERS OpenVMS,
- Upgrades : - based on Flamingo/sandpiper -
ALPHA-AXP WORKSTATIONS Upgrades,
ALPHA-AXP SERVERS Upgrades.
New Systems :
ALPHA-AXP SANDPIPER WORKSTATIONS OSF/1
SA-PE400-BA 32MB, 19"M, HX, CD, RZ26
SA-PE400-BB 32MB, 19"M, HX, RZ25
SA-PE400-BC 32MB, 16"C, HX, CD, RZ26
SA-PE400-BD 32MB, 16"C, HX, RZ25
SA-PE400-BE 32MB, 19"C, HX, CD, RZ26
SA-PE400-BF 32MB, 19"C, TX, CD, RZ26
SA-PE400-BG 48MB, 19"C, PXG+, CD, RZ26
DH-PE400-CB 64MB, 16"C, HX, TCE, TLZ06, 2xRZ26, 2 Floorstands
ALPHA-AXP SANDPIPER WORKSTATIONS OpenVMS
SY-PE400-EA 32MB, 19"M, HX, CD, RZ26
SY-PE400-EB 32MB, 16"C, HX, CD, RZ26
SY-PE400-EC 32MB, 19"C, HX, CD, RZ26
DH-PE400-FB 64MB, 16"C, HX, TCE, TLZ06, 2xRZ26, 2 Floorstands
ALPHA-AXP SANDPIPER SERVERS OSF/1
SA-PE410-LA 32MB, CD, 2xRZ26, TLZ06, TCE, 2 Floorstands
SA-PE410-BB 32MB, CD, 2xRZ26, TLZ06, STORME, 2 Floorstands,
ALPHA-AXP SANDPIPER SERVERS OpenVMS
SY-PE410-LA 32MB, CD, 2xRZ26, TLZ06, TCE, 2 Floorstands
SY-PE410-EB 32MB, CD, 2xRZ26, TLZ06, STORME, 2 Floorstands
ALPHA-AXP FLAMINGO WORKSTATIONS OSF/1
DH-PE500-AA 32MB, 19"C, HX, CD, RZ26
DH-PE500-AB 32MB, 19"C, TX, CD, RZ26
DH-PE500-AC 32MB, 19"C, PXG+, CD, 2xRZ26
DH-PE500-CB 64MB, 19"C, PXG+ 24PL, Z Buffer, CD, 2xRZ26
DH-PE500-CC 64MB, 19"C, PXGT+ 96PL, CD, 2xRZ26
ALPHA-AXP FLAMINGO WORKSTATIONS OpenVMS
DH-PE500-BB 32MB, 19"C, HX, CD, RZ26
ALPHA-AXP FLAMINGO SERVERS OSF/1
SY-PE511-AA 64MB, CD, RZ26,TLZ06
SY-PE511-AB 64MB, CD, 3xRZ26, TLZ06
ALPHA-AXP FLAMINGO SERVERS OpenVMS
SA-PE511-BA 64MB, CD, RZ26, TLZ06
SA-PE511-BB 64MB, CD, 3xRZ26, TLZ06
IMPORTANT Note :
+-----------------------------------------------------------------------+
| SANDPIPER kernels are as below : |
| |
| -PE4xx-xx -+ |
| +-- -KN15 -BA |
| +-- -MS15 -CA (32MB memory) or -MS15 -DA (64MB memory) |
| |
| FLAMINGO kernels are as below : |
| |
| -PE5xx-xx -+ |
| +-- -KN15 -AA |
| +-- -MS15 -CA (32MB memory) or -MS15 -DA (64MB memory) |
| |
+-----------------------------------------------------------------------+
Other items |
not indicated +-- -VSXXX-GA Mouse
in the document+-- QL-xxxxx-xx Software licences ... / ...
EPG PACS inf
Components Part-Id Price$ ESRP$
Sandpiper CPU -KN15 -BA 63
16MB(4 x 4 SIMMS) -MS15 -BA 2000 4
32MB(8 x 4 SIMMS) -MS15 -CA 4000 17
64MB(8 x 8 SIMMS) -MS15 -DA 8000 33
3K400 32MB OSF/1 -PE400-BB 18414 80
3K400 64MB OSF/1 -PE400-CB 23014 96
3K400 32MB VMS -PE400-EB 18414 80
3K400 64MB VMS -PE400-FB 23014 96
3K400S 32MB OSF/1 -PE410-BB 18414 80
3K400S 32MB VMS -PE410-EB 18414 80
HX board 8PL -PMAGB-BE 1995 15
PXG+ 8PL -PMAGB-DA 5000 37
TX 24PL -PMAGB-JA 3995 37
19" Mono monitor -VR319-DA 1400 12
16" C T monitor -VRT16-HA 2500 16
19" C T monitor -VRT19-HA 3800 22
600MB CDROM -RRD42-HM 850 12
426MB disk -RZ25 -EJ 1500 32
1.05GB disk -RZ26 -EH 2900 45
1.05GB disk -RZ26 -EJ 2900 45
16MB memory ext -MS15 -BA 2000 4
Floorstand -BA47X-AA 375 0
Expansion box -PMTCE-AA 2500 19
STORME Exp. Box -BA350-SA 399 0
Storme Box Mountg -BA35X-VA 129 0
4GB DAT tape -TLZ06-DA 4000 40
OSF 2 users lic. QL-MT7A9-BC 500 0
VMS 4 users lic. QL-MT2A9-BD 1200 0
12-34567-89 1 0
----------------------------------------------------------------
EPG PACS inf
Components Part-Id Price$ ESRP$
Flamingo CPU -KN15 -AA 97
16MB(4 x 4 SIMMS) -MS15 -BA 2000 4
32MB(8 x 4 SIMMS) -MS15 -CA 4000 17
64MB(8 x 8 SIMMS) -MS15 -DA 8000 33
3K500 32MB OSF/1 -PE500-AB 28975 114
3K500 32MB VMS -PE500-BB 28975 114
3K500 64MB OSF/1 -PE500-CB 33775 130
3K500 64MB OSF/1 -PE500-CD 33775 130
3K500 64MB VMS -PE500-DB 33775 130
3K500 64MB VMS -PE500-DD 33775 130
PXG+ 8PL -PMAGB-DA 5000 37
PXG+ 24PL -PMAGB-EA 12000 90
PXGT+ 96PL -PMAGB-FA 25000 190
TX 24PL -PMAGB-JA 3995 37
19" C monitor -VRT19-HA 3800 22
600MB CDROM -RRD42-HM 850 12
1.05 GB disk -RZ26 -EJ 2900 45
ped 3K500S 64MB OSF/1 -PE510-CB 33775 130
rack 3K500S 64MB OSF/1 -PE510-CD 33775 130
ped 3K500S 64MB VMS -PE510-DB 33775 130
rack 3K500S 64MB VMS -PE510-DD 33775 130
1.05 GB disk -RZ26 -EH 2900 45
4GB DAT tape -TLZ06-MF 4000 40
VMS 4 users lic. QL-MT2A9-BD 1200 0
OSF 2 users lic. QL-MT7A9-BC 500 0
12-34567-89 0 0
----------------------------------------------------------------
Service Pricing Positioning
============================
product kernel Proposed Product ADSS%
Product (Box,CPU,memory) ESRP Price ESRP/PP
----------+---------------------+--------+----------+---------+
FLAMINGO DEC3K/500 32MB OSF/1 130$ 33775$ 4.62%
SANDPIPER DEC3K/400 32MB OSF/1 80$ 18414$ 5.21%
service contract penetration rate % = 60%
retention rate % = 70%
Total configuration positioning
===============================
Product ADSS% HP 750+ IBM 560 SUN SS10
Product Price ESRP/PP BMC HW
-----------+------------+----------+----------+--------+-----------+
FLAMINGO 38400$ 6.03% 3% 6% 6.8%
SANDPIPER 30000$ 6.96% 4% 5% 6.7%
assuming : FLAMINGO avg. system 75 % volume sales
SANDPIPER avg. system 80 % volume sales
* package system defined as :
FLAMINGO DEC/3000/500 32MB, 19"C, HX 8PL, CD, 1GB, OSF/1
SANDPIPER DEC/3000/400 32MB, 19"C, HX 8PL, CD, 1GB, OSF/1
4 SYSTEMS ROLLOUT OVERVIEW
+----------FY93-----------+
Name Type ASV OS PPA ESP LRS VRS
-------------------------------------------------------------------
JENSEN highend PC 8k VMS - - ? ?
70 Spec OSF - - ? ?
NT Q2 Q3 ? ?
PELICAN lowend WS 12k VMS - Q3 Q4 Q1
DEC3000 70 Spec OSF - Q3 Q4 Q1
NT - - ? ?
SANDPIPER midrange WS 28k VMS - Q2 Q2 Q3
DEC3000 110 Spec OSF - Q2 Q2 Q4
FLAMINGO highend WS 45k VMS Q4FY92 Q1 Q2 Q3
DEC3000 120 Spec OSF Q1 Q2 Q3 Q4
COBRA lowend DC 180k VMS Q1 Q2 Q2 Q3
DEC4000 120 Spec OSF Q1 Q2 Q3 Q4
TRADEWIND mr, Faultol. 250k OSF - - - Q4
100 Spec
RUBY Midrange DC 400k VMS Q3FY92 Q2 Q2 Q3
DEC7000 600+ Spec OSF - Q2 Q3 Q4
BLAZER highend DC ?k VMS ? ? ? ?
DEC10000 600+ Spec OSF ? ? ? ?
-------------------------------------------------------------------
PPA = Pilot Porting Activity
ESP = Early Shipment Program
LRS = Limited Revenue Shipment
VRS = Volume Revenue Shipment
4.1 EUROPEAN ALPHA AXP SYSTEM SHIPMENTS
+---FY93---+ +---FY94---+
Name Type ASV OS units units
-------------------------------------------------------------------
JENSEN highend PC 8k NT 1240 26000
70 Spec
PELICAN lowend WS 12k
DEC3000 70 Spec
SANDPIPER midrange WS 28k 2200 7200
DEC3000 110 Spec
SANDPIPER server 28k 865 270
DEC3000 110 Spec
FLAMINGO server 45k 860 1100
DEC3000 110 Spec
FLAMINGO highend WS 45k 1180 7000
DEC3000 120 Spec
COBRA lowend DC 180k 217 5550
DEC4000 120 Spec
RUBY Midrange DC 400k 169 740
DEC7000 600+ Spec
BLAZER highend DC ?k 25 45
DEC10000 600+ Spec
-------------------------------------------------------------------
Based on preliminary data. Shipment forecast will be updated by
product marketing.
5 SERVICE DELIVERY
5.1 ALPHA RESOURCE CENTER STATUS - JULY 1992
+------+------+-----------------------------+------------------------------+
| C | Type | A R C H E A D C O U N T | D S E Q U I P M E N T |
| T | of +-----+-----------------------+-----------+------------------+
| R | | FY92| FY93 | FY92 | FY 93 |
| Y | ARC +-----+-----+-----+-----+-----+---+---+---+---+----+----+----+
| | | Q4 | Q1 | Q2 | Q3 | Q4 | R | C | F | R | C | F | S |
+------+------+-----+-----+-----+-----+-----+---+---+---+---+----+----+----+
| AU | Full | 7 | 7 | 7 | 7 | 7 | 1 | - | 4 | 1 | 3 | 5 | 8 |
| BE | Lim. | 2 | 2 | 3 | 3 | 3 | - | - | 2 | 1 | 3 | 6 | 4 |
| CDG | Lim. | 3 | 3 | 3 | 3 | 3 | - | - | 2 | - | - | 1 | 2 |
| DK | Lim. | 1.6| 2 | 2 | 3 | 3 | - | - | 2 | 1 | 1 | 1 | - |
| EAST | - | ? | ? | ? | ? | ? | - | - | - | - | - | 6 | - |
| FN | Lim. | 2 | 2 | 2 | 3 | 3 | - | - | 2 | - | 3 | 12 | 15 |
| FR | Full | 6 | 7 | 7 | 7 | 7 | 1 | - | 4 | 2 | 14 | 43 | 30 |
| GY | Full | 6 | 7 | 7 | 7 | 7 | 1 | - | 4 | 9 | 11 | 46 | 49 |
| GR | Lim. | 1 | 2 | 2 | 3 | 3 | - | - | 2 | - | 1 | 1 | 2 |
| IR | Lim. | ? | ? | ? | ? | ? | - | - | - | - | 1 | 5 | 4 |
| IS | Lim. | 1 | 2 | 2 | 3 | 3 | - | - | 2 | - | - | 3 | 1 |
| IT | Full | 9 | 9 | 12 | 12 | 12 | 1 | - | 4 | - | 1 | 11 | 8 |
| NL | Lim. | 1 | 3 | 3 | 3 | 3 | - | - | 2 | 2 | 3 | 5 | 1 |
| NW | Lim. | 2.1| 3 | 3 | 3 | 3 | - | - | 3 | 1 | 2 | 5 | 3 |
| PL | - | ? | ? | ? | ? | ? | - | - | - | - | 1 | 4 | 1 |
| SP | Lim. | 3 | 3 | 3 | 3 | 3 | - | - | 2 | 1 | 2 | 6 | 2 |
| SW | Full | 4 | 6 | 6 | 7 | 7 | 1 | - | 4 | - | 1 | 2 | 4 |
| CH | Lim. | 4 | 4 | 4 | 4 | 4 | - | - | 2 | 2 | 3 | 18 | 6 |
| TU | - | ? | ? | ? | ? | ? | - | - | - | - | - | 1 | 1 |
| UK | Full | 10 | 10 | 10 | 10 | 10 | 1 | - | 6 | 3 | 19 | 48 | 48 |
+------+------+-----+-----+-----+-----+-----+---+---+---+---+----+----+----+
| Tot Country | 63 | 72 | 76 | 81 | 81 | 6 | - | 47| 23| 69 | 229| 189|
+-------------+-----+-----+-----+-----+-----+---+---+---+---+----+----+----+
+-------------+-----+-----+-----+-----+-----+---+---+---+---+----+----+----+
| TIG/VBO | 9 | 10 | 10 | 10 | 10 | 1 | 1 | 6 | 1 | 4 | 3 | 6 |
| TPAG/REO | 4 | 4 | 4 | 4 | 4 | 1 | - | 3 | ? | ? | ? | ? |
| SDE/EICs | 3 | 6 | 6 | 6 | 6 | - | - | 3 | - | 7 | 5 | 3 |
| Others | 2 | 2 | 2 | 2 | 2 | - | - | 3 | - | - | - | - |
+-------------+-----+-----+-----+-----+-----+---+---+---+---+----+----+----+
| Euro-ARC | 13 | 18 | 22 | 22 | 22 | 1 | 1 | 15| 1 | 11 | 8 | 9 |
+-------------+-----+-----+-----+-----+-----+---+---+---+---+----+----+----+
+-------------+-----+-----+-----+-----+-----+---+---+---+---+----+----+----+
| Tot Eur. | 81 | 94 | 98 | 103 | 103 | 8 | 1 | 62| 24| 80 | 237| 198|
+-------------+-----+-----+-----+-----+-----+---+---+---+---+----+----+----+
5.2 EUROPEAN ALPHA AXP INTERNAL TRAINING
Official HW training from Education Services on LASER (RUBY/NEON),
FLAMINGO, SANDPIPER and COBRA. For bookings and schedule information
on future courses contact your local Learning Services or the UK
desk on 7830-8020.
Country Alpha training managers: Belgium Christian Meersman
France Alain Dagois
Germany Lothar Mey
Holland Rob De Maat
Israel Edna Kulik
Italy Enzo Esposito
Norway Terje Holkestad
Portugal Fernando Faustino
Sweden Peter Larsson
Switzerland Sandro Polenta
UK Eric Perks
European Learning Services: NICK DEBNEY @REO, 830-6376
+--------------------------------------------------------------------+
| Course Title | Course Number |
+--------------------------------------------------------------------+
| Alpha AXP Architecture Concepts Seminar | EY-J018E |
| | |
| Alpha AXP Architecture Concepts CBI | EY-I156E |
| | |
| Alpha AXP Architecture | EY-K022E |
| | |
| FutureBus+ Concepts CBI | EY-F479E |
| | |
| TurboChannel Concepts CBI | EY-F480E |
| | |
| Cobra System CBI | EY-I090E |
| | |
| Cobra Maintenance (UK local course) | EY-K410E |
| | |
| Flamingo System CBI | EY-I087E |
| | |
| Laser Platform Inst. & Maint. (Ruby/Neon) | EY-L730E |
| | |
| Flamingo/Sandpiper Service Overview Seminar (UK lcl) EY-K403E |
| | |
| Jensen | EY-L889E-P0 |
(This course IS NOT yet available - Check with Edu Services at a later date)
| | |
| OpenVMS AXP Installation/Utilities | tbd |
| | |
| OpenVMS AXP System Management Seminar | tdb |
| | |
| OpenVMS AXP System Support Seminar | tbd |
| | |
| OpenVMS AXP Migration | EY-H008E |
| | |
| OpenVMS AXP Migration Workshop | EY-H009E |
| | |
+---------------------------------------------------+----------------+
These SPIs are available and on-line.........
For Preliminary Training.
Please send mail to PHAROS::CST_DELIVERY if you need help locating
a course.
Each course has its own directory:
PHAROS::$77$DUA1:[CST_DELIVERY.AVAILABLE.NNNN]
where NNNN is the 4 alpha-numeric characters in the EY number.
PRELIMINARY courses (those distributed to meet field test training
needs) are located in their individual directories:
PHAROS::$77$DUA1:[CST_DELIVERY.NNNN]
PRELIMINARY courses are usually incomplete, and represent the most
accurate information available before their release.
Most of the courses are stored as compressed save sets which you can
copy. Some courses have been moved to conserve disk space. If you need
a course moved back to its directory, please send a mail request to
PHAROS::CST_DELIVERY.
PRELIMINARY-ALPHA
EY-I087E-C0-0001 DEC 3000 Installation and Troubleshooting
Note: This is a preliminary release of the DEC 3000 CBT to
support PPA activity. Read the README.FIRST and READ.ME files
for an explanation of the course files which include:
3 save-sets, Installation instructions, and two preliminary
service guides.
PRELIMINARY- ALPHA
EY-I090E-C0-0001 DEC 4000 Installation and Troubleshooting
Note: This is a preliminary release of the DEC 4000 CBT to
support PPA activity. Read the READ.ME file for an explanation
of the course files which include: 3 save-sets, Installation
instructions, and preliminary service guide.
PRELIMINARY- ALPHA
EY-I882-C0-0001 7000/10000 Systems Level 1 Maintenance Course
Note: This is a preliminary CBT course release to support PPA
activity. The course files include: 3 save-sets,
Installation instructions, and a PostScript student
guide.
5.3 SERVICE DELIVERY OVERVIEW
During PPA phase the level of agreement and customers
expectations are 8h/5d. During LRS and VRS, business as
usual with standard offerings.
All installations must be performed by a Trained Services Engineer.
(Even if the workstations are defines as "customer installable" for
state state purpose, we want to ensure customer satisfaction for the
strategic developement sites during the early ship programs).
The following diagram is a proposal which deals with the areas
of Customer call flow, Service Delivery and Escalation path.
The proposal covers the flow during PPA, FT and LRS Phases.
During the PPA and FT phase it is expected the ARC is involved
in the Support/Call Flow.
Any Remote Diagnosis, SDD or AES requirements is to be decided and
will be following the overall AES implementation plan (no Alpha AXP
specific remote services available today).
Non-critical and pure technical escalation follows the QAR process
and product matrix attached.
Critical and business escalation follows the ECSO/IPMT/CLD process
as defined in the European Call Flow Architecture.
INSTALLATION FLOW
+---------------------------+
| PPA/FT/LRS Installation |
+---------------------------+
|
V
+-------------------+
| Inform ARC |
+------->| HW/SW Specialist |
| | Register System |
| +-------------------+
| |
| V
| +---------------+
| | Installation |
| | either |
| | Customer site |
| | or Internal |
| +------+--------+
| |
+--------N----- problem ------------Y----+
|
v
If problem see
Customer Call Flow
CUSTOMER CALL FLOW
+----------+ |
| CUSTOMER | |
| CALL | +-------------- Problem -------Y--------+
+----------+ |
| +----------------------+ |
+---------->| -CSC- |<------------------+
| NICE call logged |
+----------------------+
|
V
+----------------------+
+---------------->| CSC Diagnosis |
| +----------------------+
| |
| V
| / \
| / \ +------------+
| / Fixed \---Y--->| Close Call |
| \ ? / | END |
| \ / +------------+
| \ N /
| |
| V
| / \
| / \ +-------------+
| /Escalate \---Y--->| Call ARC |
| \ ? / | Specialist |
| \ / | |
| \ N / +-------------+
| | |
| V V
| +-----------------+ / \
| | Service Centre | / \
| +-------------+ | Engineer to site| / Fixed \----N---+
| |Inform HW ARC| +-------|---------+ \ / |
| | Specialist | V \ / V
| | |<-Y--| Spares Needed | \ Y / | Escalation |
| +-------------+ +---------------+ | | EURO-ARC |
| | N | | 7828-6500 |
| +-------------------->| |
| V +------V--------+
| / \ | Contact CSC |
+--------------------N---/ Fixed \--Y---->| to close call.|
\ / | -END- |
\ / +---------------+
SERVICE DELIVERY ON FLAMINGO SYSTEMS
IMPACT SUMMARY:
Technical call screening will be the standard service delivery mechanism
Some remote service delivery techniques can be used to deliver efficient
and cost effective off-site delivery. Customers will be participating in
running diagnostics and reporting error codes to the support center.
The implementation of system event management tools, configuration and
information management, and remote system analysis capabilities will
further reduce service on-site labor cost, as these features are added.
New value added services beyond the traditional break-fix will also
minimize the need for on-site service personnel.
PRODUCT SERVICE STRATEGY:
Customer installable (as defined by product marketing) pedestal work-
station and add-on options. Standard workstation service strategy
applies. Customers will be able to upgrade firmware on their systems.
Rackmount systems are not customer installable or customer
upgradeable. Standard workstation service strategy applies.
Customers will be able to upgrade firmware on their systems.
SERVICE STRATEGY:
Service Strategy will be FRU replacement. Standard practice
applies.
PREVENTIVE MAINTENANCE: None required for workstations or servers.
PRODUCT SERVICE FEATURES:
Front mounted power switch, DC okay LED, diagnostic error code
LEDS, Fans okay LEDS, and halt/reset switch. FEPROM's for
electronic upgradeable firmware, ROM based self-test.
Additional features for pedestal mount workstations and servers
are: customer installable add-on options,
DIAGNOSTIC TOOLS:
Firmware Update Utility on CDROM. ROM based Self test, extended
self tests, and console utilities. Error report formatter with
the operating system.
EMBEDDED SOFTWARE: N/A
SERVICE AIDS/TOOLS/TEST EQUIPMENT:
Loopback connectors are required for complete diagnostic error
checking. These are commonly available loopbacks and will not be
part of the service kit. These loopbacks will be provided with
the system for the Customers use:
LOOPBACK PART NUMBER
10BaseT H4082-AA
THICKWIRE 12-22196-01
PRINTER PORT H3103
MODEM PORT 29-24795
SERVICE DELIVERY STRATEGY:
Service Delivery will be via traditional workstations service
delivery model.
Remote console access to the DEC/3000 M500 is possible by a
network connection using DECNET MOP commands. Remote system
access is possible by operating system SET HOST command, and if
so configured via direct dialin to a modem on the modem control
port. The full modem control port or alternate console port does
NOT support remote connection at the console level.
Security for remote console access is provided by a 16 hex
character password, a console level firmware enable command, and
a physical jumper inside the system. Manufacturing default is
security not enabled. The system has a keyed lock integral to
the top cover. Only the Customer has keys, and the default is
unlocked.
SUPPORT/ESCALATION:
Traditional support processes will apply. Escalation via the
geographies call flow diagrams, into the corporate problem
managment system of the day, (CLD or IPMT).
SERVICE METRICS:
WORKSTATION
METRIC | VALUE | UNIT | COMMENTS
----------------------------------------------------------------
MTTI .5 Hours Customer installable system
MTTR 1.8 Hours Total on-site time
MTBC 8.8 Months
MTBF 12.3 Months 9000 hrs @ 100%
MTBPR 21.9 Months 12000 hrs @ 75%
Duty Cycle 75 %
Support Ratio 2 %
NMU 40 %
RACKMOUNT
METRIC | VALUE | UNIT | COMMENTS
----------------------------------------------------------------
MTTI 4.0 Hours Requires 2 people
MTTR 3.0 Hours Requires 2 people
MTBC 8.8 Months
MTBF 12.3 Months 9000 hrs @ 100%
MTBPR 21.9 Months 12000 hrs @ 75%
Duty Cycle 75 %
Support Ratio 2 %
NMU 40 %
MTTR, MTBC, MTBF, MTBPR based on the following configuration:
Kernal (including mouse, keyboard, 64 mb), monitor, .5 RZ24,
2 RZ25, .5 RZ26, .8 QIC tape TZK10, 1 RRD42.
SITE PREP. and INSTALLATION:
Customer installable pedestal mount and options. Environment is
typical open office.
Rackmount installation requires 2 people. Environment is typical
computer room.
SERVICE ENGINEER PROFILE:
The Service Engineer must be able to troubleshoot DEC/3000 M500
systems via console commands, basic operating systems commands
(OpenVMS AXP or DEC OSF/1 AXP), and error logs.
Skill set should include a working knowledge of the following:
o ALPHA AXP architecture
o VAX or MIPS RISC workstation architectures
o SCSI bus and devices
o TurboChannel bus
o Color and monochrome monitors
o NCP and networks
TRAINING STRATEGY:
The DEC/3000 M500 course will be developed utilizing Icon Author
DECwindows (computer based instruction). This computer based
instruction training provides interactive participation between
the student and course-ware thereby eliminating the need for
labs requiring hardware. FLAMINGO training will be on the
Desktop via TIMA and FTC locations worldwide. In addition, the
DEC/3000 M500 course format will adhere to information mapping
techniques, and adapt to the same path-finder approach utilized
on FBUS Concepts course.
PRE-REQUISITES: ALPHA AXP Concepts
TURBOchannel Concepts EY-F480E-BO, EY-F480E-P0
OpenVMS AXP Installation & User
The intended audience for this course will be Customer Service
Engineers who are responsible for the Installation, Maintenance,
and Support of ALPHA AXP systems.
Delivery location:
This course (DEC/3000 M500 EY-I087E-C0) will be delivered from TIMA
Worksystems and worldwide FTC sites.
LOGISTICS IMPACT SUMMARY:
CPU module is expensive. Correct isolation via troubleshooting
and training is critical to maintain cost effective support
capabilities.
RSL:
PART NUMBER DESCRIPTION COST
----------- ----------- -------
12-23609-12 FAN 15.82
00-H7883-AA POWER SUPPLY 201.26
54-21149-01 SYSTEM MODULE 8221.98
54-21147-01 I/O MODULE 857.20
54-21141-01 MEMORY MOTHERBOARD 126.25
54-21139-CA 4 MB MEMORY SIMM 160.15
54-21139-DA 8 MB MEMORY SIMM 309.93
54-21145-01 LSM MODULE (RACKMOUNT) TBD
54-21145-02 LSM MODULE (PEDESTAL) 58.67
54-21167-01 AUDIO INTERFACE MODULE 76.75
DOCUMENTATION
DEC/3000 M500 Service Manual - EK-FLAMI-SV
AVAILABILITY:
Draft Service documentation is available in .PS format from the
PROTO Support Starterkit. Use "JARED::DKA700:[hardware.docs]"
as a pointer.
Final Technical signoff is gated by several weeks of External
Field Test runtime. Signoff is scheduled for 8/31/92.
Final hard copy on the shelf 10/30/92.
REFERENCE DOCUMENTATION:
The following manuals are available now from the PROTO support
starter kit. They are draft manuals in postscript format for
external field test. Use JARED::DKA700:[HARDWARE.DOCS]
Flamingo Owner's Manual FLAM_OWNER_08APR92.PS *
Flamingo Options Guide FLAM_OPTIONS_GUIDE_19MAY92.PS *
Flamingo Macrocoders Manual FLAM_MACROCODER_08-JUN92.PS *
Flamingo Hardware Spec. FLAM_HARDWARE_SPEC_V20.PS *
Flamingo Power Supply Spec. FLAM_H7883_POWER_SPEC_V20.PS *
* newer versions may exist.
SSK:
Proto support starter kit available now.
Use JARED::DKA700:[HARDWARE] as top level directories
JARED::DKA700:[FIRMWARE]
JARED::DKA700:[SOFTWARE]
Final SSK will be via TIMA. availability starting August
TIMA:
Service documentation will be available on TIMA 9/30/92. The
TIMA/STARS database will be used to post technical support
information about the DEC/3000 M500 product which is needed by
the Customer Services organization.
REVISION CONTROL/COMPATIBILITY:
Revision Control will be maintained by the RM document.
Continuation Engineering will maintain the RM document as part
of the DEC/3000 M500 Engineering Documentation.
FCO STRATEGY:
DEC/3000 M500's will likely revenue ship with EV4-2.1 CPU chips.
Final revenue quality systems will be upgraded to EV4-P3 CPU
chips for sale to Custmers. SPE, with input from the
geographies, and key members of the Digital Services Team will
document and implement a NON-standard FCO implementation to
efficiently upgrade all DEC/3000 M500 systems in a timely and
cost-effective manner.
System Firmware Upgrades will be done electronically via the
DEC/3000 M500 Update Utility available to the Customer on CDROM.
This utility does not require under the cover hardware access.
No firmware revisions are tracked to the hardware revision.
PRODUCT PHASEDOWN:
Phase 4 exit 9/94
Phase 5 exit 12/94
SERVICE DELIVERY ON COBRA SYSTEMS
IMPACT SUMMARY
COBRA is a new platform architecture, it supports a new console ar-
chitecture, a new CPU architecture and two new operating systems. The
end result is that present field personnel must be trained on the new
hardware/software as it becomes available.
PRODUCT SERVICE STRATEGY
COBRA service strategy will for the most part be a continuation of
the VAX 4000 for the COBRA-H4 (Hot Box) but will be similiar to the
VAX6000 (detection/isolation done by the Remote Diagnosis Center
(RDC) with local personnel dispatched by the RDC) for the COBRA-B4T
(Balanced system). The COBRA-B4T will be a production system while
the COBRA-H4 will be targeting non-critical applications. The
Cobra-H systems will receive the standard Basic Service coverage
during the warranty period. The Cobra-B4T system is expected to
receive a standard level of 24X7 (24 hours per day, 7 days per week)
coverage during the warranty period and this level of coverage will
be recommeded for follow-on contracts in all production and
commercial environments.
PRODUCT SERVICE FEATURES
o COBRA Firmware can be updated off-line, locally and eventually
remotely
o Non-volatile storage (EEPROM) for failure/error data logging on
each COBRA system bus module
o High level of commonalty between the COBRA system console and
LASER/BLASER consoles
o Integrated remote console access via the auxillary serial port
o Expanded diagnostic and console firmware
o Hex display showing the fan (1-4) or disk (A-D) failure.
o Multi-tasking console allows background and foreground operations.
o Support for CTRL P
PREVENTIVE MAINTENANCE
At present, there is no required hardware PM activity defined for the
COBRA family of systems. A 2-4 hour PM once a year has been built-in
to the Cobra Life-Cycle-Business-Model for the purpose of auditing
configuration and diagnostic information. This PM would be optional
based upon whether the local branch tracked revision and serial
numbers for the Cobra system hardware,software and firmware.
Firmware updates are not considered PMs but may be performed during
this optional once a year PM.
DIAGNOSTIC TOOLS
Differences from the VAX4000 Diagnostic strategy
Console diagnostics and excersizers will be rom-based. VET will re-
place UETP as the online system excersizer. MDM will not be ported to
ALPHA AXP systems.
COBRA provides ROM-based diagnostics and exercisers for all kernel
devices.
The SDD Strategy for COBRA will be:
o Next Generation Fault Management (ANASAZI)
o On-module NVM failure logging (EEPROMS on all COBRA system bus
modules)
o Information Based Repair (IBR) support
o Logging of hardware, software and firmware configuration manage-
ment information to OSF/VMS error logs.
The chief use of power-on self test (POST) will be installation and
repair verification.
Distribution
Current plans call for all firmware upgrade images to ship on CDROM.
EMBEDDED SOFTWARE
Factory Installed Software (FIS) will be provided on COBRA. This is
expected to consist of OSF or OpenVMS AXP plus some applications.
The Next Generation Fault Management Tools are also under consider-
ation for distribution using FIS.
SERVICE AIDS/TOOLS/TEST EQUIPMENT
No special tools are required for Cobra.
Faults crossing a predetermined threshold will result in a message to
the operators console in a condensed theory code format. This
condensed code can then be translated to a FRU using the pocket
service guide.
The Goal is to have some FRU callout information included in the er-
ror log. This would permit the use of ANALYZE/ERROR to determine the
failing FRU directly without CSC assistance in most instances.
Mandatory installation and setup of Fault Management Tools is being
considered for COBRA. These tools would be factory installed for war-
ranty customers. The capability to de-install the tools would be pro-
vided to address customers not renewing service contracts. Fault man-
agement tools are not available at FCS but are scheduled to coincide
with the COBRA-B platform.
Diagnostic and configuration management information will be logged to
the VMS or OSF error logs. Information related to locating and inter-
preting this data will be included in the pocket service guide. Co-
bra system modules (CPU, memory,and I/O) along with FBUS modules have
machine readable serial numbers that can be accessed from console
mode and are logged to the error logs. A machine readable system
serial is provided as part of the environmental variables stored on
the I/O module.
SERVICE DELIVERY STRATEGY
Remote fault detectionn and isolation is the primary service deliv-
ery strategy for the COBRA Platform, independent of operating system
(where remote connections are allowed by our customers). The service
metrics will vary significantly based upon whether remote diagnosis
is used to provide service support for a system. Two sets of metrics
are shown below.
Method
The diagnostic activity, in most cases, may be provided remotely
(e.g. from a RDC or other distributed support centers) or even from
a local office which has that ability. Whenever possible, actual
repair activity (e.g. FRU replacement and verification) should be
scheduled so as to minimize the impact on customer operations. The
COBRA platform can be supported via modem or Ethernet connections.
COBRA provides access to console diagnostics remotely through an
auxiliary EIA RS232 modem port, or across one of the built-in
Ethernet ports. The new remote console feature is independant of the
operating system being loaded.
The auxiliary port will eventually support the full set of features
available from the local console port including boot audit trail,
deposit and analyze.
The Ethernet ports will offer a limited set of features that may not
include boot audit trail. A remote console connection through the
Ethernet port will become disconnected after initiating a boot and
will require reconnecting to the system. The Ethernet port utilizes
MOP console carrier as the connecting protocol and is therefore
limited to connection from another host attached to the same segment.
MOP console carrier does not work across routers or most bridges.
SUPPORT/ESCALATION
Refer to the H/W PASS entry (#5757) for this product for the specific
Support/Escalation processes defined by the three geographies.
SERVICE METRICS
METRIC____________REMOTE______LOCAL________UNIT________COMMENTS____
MTTI 4.7 3 Hours
MTTR 1.5 3 Hours
MTBC 12 8 Months
MTBF 20 20 Months
DUTY CYCLE 90 90 %
MTBPR 12 8 Months
SUPPORT RATIO 10 10 %
NMU_______________25__________50___________%_______________________
SITE PREP. and INSTALLATION
Site Prep information will be provided via TIMA and made available
for inclusion in XSITE. The site prep information for PPA, Field
Test and Early Ship Program (ESP) units will be different from FCS
systems because of the plans to upgrade from a 15amp Front End Unit
(FEU) to a 20amp FEU at FCS.
SERVICE ENGINEER PROFILE
The service engineer(s) profile for COBRA is a cross between the
VAX6000 and VAX4000 systems. The new ALPHA AXP midrange systems will
utilize the same console as COBRA. The COBRA-H4 system requires the
same profile as the VAX4000 while the COBRA-B4T system may require
additional training as a result of the production environment and
applications running on this platform.
TRAINING STRATEGY
The training strategy for COBRA systems will be built on the COBRA
Platform and the initial system to ship (COBRA-H4). A more detailed
description of the training strategy is contained in the training
section on HWPASS. The following lists the planned courses:
Title__________________Course_#____Audience___________Format_______
COBRA L1 EY-I090E-CO DS Unit Engineer CBI via TIMA
FutureBus+ L1 EY-F479E-CO DS Unit Engineer CBI via TIMA
ALPHA AXP Concepts L1 TBD DS Unit Engineer CBI via TIMA
ALPHA_Architecture_L2__TBD_________DS_Support_EngineerLecture/Lab__
Pre-requisites
Previous experience with ULTRIX/UNIX/OSF, VAX/VMS, and VAX4000 or
VAX6000 based systems.
Delivery Location
COBRA CBI courses are designed to be delivered at the local branch
via a TIMA workstation. Corporate training has recommended separate
TIMA workstation for training specific use.
Course availability: At FCS, CBI courses will be available worldwide
via TIMA.
NOTE: Training was provided prior to Field test to support that ac-
tivity.
LOGISTICS IMPACT SUMMARY
The Logistics impact assessment and RSL are provided in the PLP
available in TIMA.
Logistics is required to support the two potential FCOs on the power
supply and CPU modules. This will impact initial stocking
requirements and material required to start the FCOs.
DOCUMENTATION
The COBRA documentation set will consist of three types of manuals:
User, Service and Reference. Except where noted, all manuals will be
produced in both printed, postscript and online (BOOKREADER)
versions.
User Documentation
Title________________________________________________Part_Number___
COBRA Information Map EK-KN430-IM
COBRA Site Prep Card (printed and ps only) EK-KN430-SP
COBRA Installation Card (printed and ps only) EK-KN430-IN
COBRA Owner's Guide EK-KN430-OP
COBRA Options EK-KN430-OG
COBRA Glossary and Master Index EK-KN430-MI
DEC VET Diagnostics TBS
Futurebus+ Handbook TBS
ALPHA AXP Handbook TBS
ALPHA AXP Family Technical Summary TBS
COBRA Factory Installed Software TBS
Installing_OpenVMS_AXP_on_COBRA______________________TBS___________
Service_Documentation
Title________________________________________________Part_Number___
COBRA Pocket Service Guide (printed and ps only) EK-KN430-PS
COBRA Service Information EK-KN430-SV
COBRA 600 Series Enclosure IPB EK-EN430-IP
COBRA 600 Series Mass Storage IPB EK-MS430-IP
COBRA Pedastal System IPB EK-SY430-IP
COBRA_Technical_Information__________________________EK-KN430-TM___
All documentation, except where noted above will be available on
CDROM and therefore available to TIMA. All COBRA documents will be
available in postscript. All documentation available 30 days prior
to FRS will be submitted for the SSK.
SUPPORT STARTER KIT (SSK) AVAILABILITY: JUNE 1992
REVISION CONTROL/COMPATIBILITY
Since COBRA is a new platform it is expected that there will be no
compatibility issues at FRS at the Kernel level. FutureBus+ will
also be so new that compatibility issues should not be a high risk
during this time frame.
The FBUS adapter revisions for the COBRA Platform will be defined in
the Revision Matrix document and be available on TIMA.
FCO Strategy
The only change in FCO strategy over the VAX4000 is the added capa-
bility to do firmware upgrades via CDROM.
There are presently several FCO's planned for this product. The first
FCO is for the ESP units (approximately 200 - 500 units) to be
upgraded from 15amp to 20 amp power supplies. The second FCO is to
upgrade the CPU module's to a later CPU version that contains ECC.
There are also firmware upgrades which will be required to address
functionality.
The SASE continuing engineering organization will be generating and
handling the FCO work for Cobra.
PRODUCT PHASE DOWN
Phase 5 exit is presently TBD.
SERVICE DELIVERY ON RUBY (LASER) SYSTEMS
IMPACT SUMMARY:
THE RUBY PLATFORM IS BASED ON THE LASER. WHAT RELATES TO LASER
ALSO RELATES TO RUBY.
LASER is a new platform architecture, it supports a new console
architecture, a new CPU architecture and a new operating system.
The end result is that present field personnel must be
trained on the new hardware/software as it becomes available.
Service Strategy:
LASER systems service strategy will for the most part be a
continuance of the VAX6000 (detection/isolation done by the RDC
with local personnel dispatched by the RDC). The differences come
from the changes being proposed/implemented in conjunction with
the ALPHA program. As the proposed mechanisms become
funded/implemented they will be defined in a later release of
this document.
Product Service Features:
o LASER Firmware can be updated off-line, locally and remotely
o Warm swap of embedded DSSI disks
o Non-volatile storage(EEPROM) for failure/error data logging
on each LSB module, including memorys
o N+1 Power system allows for potential scheduled maintenance
and availability improvement
o Remote diagnosis of Power System
o High level of commonality between the LASER systems consoles
and other consoles being developed for other ALPHA AXP platforms.
o Higher reliability and availability goals than the VAX6000
Preventive maintenance:
At present, there is no planned or required PM activity defined
for the LASER family of systems. However, it should be noted that
there are filters within the cabinetry that should be checked and
cleaned periodically. There should also be provisions made for
periodic battery testing/replacement if applicable.
Diagnostics Tools:
Differences from the VAX6000 Diagnostic strategy:
Despite the fact that LASER will support VAX products it will not
follow the VAX Family diagnostic strategy (i.e. the VAX diagnostic
Supervisor will not be ported to run on the LASER/NEON system).
The LASER/NEON Console's Diagnostic Execution environment will
be developed to provide a common run-time environment for all
ROM-based and off-line loadable diagnostics/exercisers. Programs
run under the diagnostic executive will run like any other program
in the console's operating environment.
The first generation LASER CPU designs are such that no diagnostic
code will be runable from ROM; all ROM code must be loaded into
cache or main memory before being executed.
LASER will provide ROM-based exercisers for all kernel devices
and loadable exercisers for all supported boot devices.
The SDD Strategy for LASER will be dependent on the type of CPU in the
system (refer to specific CPU/System plans for Detail). The following
applies independent of CPU type:
o ERF and UERF
o On-module NVM failure logging (EEPROMS on all LSB modules)
o Information Based Repair (IBR) support
TDD Strategy for LASER is the same for all CPU/System types. The
chief use of BIST and loadables will be installation and repair
verification.
DISTRIBUTION:
Current plans call for all off-line loadable diagnostics and ROM
diagnostic firmware upgrade images to ship on CDROM.
Part numbers will be added to this plan when they become available.
EMBEDDED SOFTWARE: N/A for this product
SERVICE AIDS/TOOLS/TEST EQUIPMENT: TBS
SERVICE DELIVERY STRATEGY:
Remote detection/isolation is the primary service delivery strategy
for the LASER Platform, independent of CPU type or operating system
(where remote connections are allowed by our customers).
Method:
The diagnostic activity, in most cases, may be provided remotely
(e.g. from a RDC or other distributed support centers) or even
from a local office which has that ability. Whenever possible,
actual repair activity (e.g. FRU replacement and verification)
should be scheduled so as to minimize the impact on customer
operations. The LASER platform can be supported via DSNLink or
the MDS01 or its replacement.
Support/Escalation:
Refer to the H/W PASS entry for this product for the specific
Support/Escalation processes defined by the three geographies.
SERVICE METRICS: (for Kernel only)
METRIC | VALUE | UNIT | COMMENTS
----------------------------------------------------------------
MTTI 8.0 Hours
MTTR 1.5 Hours
MTBC 19.0 Months
MTBF 27.4 Months
Duty Cycle 100.0 %
MTBPR 21.0 Months
Support Ratio 15-20 % See specific system plans
NMU 30 %
SITE PREP. and INSTALLATION:
Site Prep information will be provide via TIMA and made available
for inclusion in XSITE.
SERVICE ENGINEER PROFILE:
The service engineer(s) profile for LASER is the same
as the VAX6000
TRAINING STRATEGY:
The training strategy for LASER systems will be built on the
LASER Platform and the initial system to ship on LASER (NEON).
The XMI I/O subsystem will be included in the initial
course offering. As new systems become available they will
be added as differences modules. LASER systems training will
available as a lecture/lab course at the major training centers
as determined by the geographies. The following lists the
planned courses:
Title Course # Audience Format
----- -------- -------- ------
7000/10000 SYSTEMS EY-I882E-P0-0001 DS Unit CBI (Computer-
LEVEL 1 MAINTENANCE Engineer based instruction
7000/10000 SYSTEM EY-L885E-V0 DS Service Video Tape
INSTALLATION VIDEO Engineers
7000/10000 SYSTEMS EY-L884E-L0 DS Support Lecture/Lab
SUPPORT LEVEL 2 Engineer
PRE-REQUISITES:
XMI Concepts, XMI Handbook (refer to specific CPU/Systems
Plans for further detail.
DELIVERY LOCATION
First delivery was in Galway, further deliveries TBS
LOGISTICS IMPACT SUMMARY:
The VAX/DEC 7000, 10000 and subsequent supported systems will rely
heavily on IBR to simplify repair, lower the costs of repair, and
dramatically lower the incident of defective spares, and FRU's
returned with no problem found. Just-In-Time inventory strategies
will be implemented for these systems to lower inventory values and
write-offs. In the case of high priced FRU's (i.e. memory)
allocations will be implemented.
For details see European Products Logistics Plan in TIMA.
DOCUMENTATION
The LASER documentation set will consist of three types of manual:
user, service and reference. Except where noted, all manuals will
be produced in both printed and online versions.
DEC 7000, VAX 7000 USER Documentation:
Title Part Number Availability
o DEC 7000, VAX 7000 Installation Kit EK-7000B-DK Nov. 1992
- DEC 7000, VAX 7000 Site Prep Guide EK-7000B-SP Nov. 1992
- DEC 7000, VAX 7000 Installation EK-700EB-IN Nov. 1992
Guide
o DEC 7000, VAX 7000 Hardware User EK-7001B-DK Nov. 1992
Information Kit
- DEC 7000, VAX 7000 Operational EK-7000B-OP Nov. 1992
Manual
- DEC 7000, VAX 7000 Basic EK-7000B-TS Nov. 1992
Troubleshooting
- VAX 7000, DEC 7000 Platform EK-7000B-HB Dec. 1992
Handbook
DEC 7000, VAX 7000 SERVICE Documentation:
Title Part Number Availability
o DEC 7000, VAX 7000 Service EK-7002B-DK Nov. 1992
Information Kit
- DEC 7000, VAX 7000 Advanced EK-7001B-TS Nov. 1992
Troubleshooting
- DEC 7000, VAX 7000 System Service EK-7002B-SV Nov. 1992
Manual
- DEC 7000, VAX 7000 Platform EK-7000A-SV Nov. 1992
Service Manual
- DEC 7000, VAX 7000 Pocket Service EK-7700A-PG Nov. 1992
Guide
VAX/DEC 10000 USER Documentation:
Title Part Number Availability
o DEC 10000, VAX 10000 Installation Kit EK-1000B-DK Nov. 1992
- DEC 10000, VAX 10000 Installation EK-100EB-IN Nov. 1992
Guide
- DEC 10000, VAX 10000 Site Prep EK-1000B-SP Nov. 1992
Guide
o DEC 1000, VAX 10000 Hardware User EK-1001B-DK Nov. 1992
Information Kit
- DEC 10000, VAX 10000 Operational EK-1000B-OP Nov. 1992
Manual
- DEC 10000, VAX 10000 Basic EK-1000B-TS Nov. 1992
Troubleshooting
- DEC 7000, VAX 7000 Platform EK-7000A-HB Dec. 1992
Handbook
DEC 10000, VAX 10000 SERVICE Documentation:
Title Part Number Availability
o DEC 10000, VAX 10000 Service EK-1002B-DK Nov. 1992
Information Kit
- DEC 10000, VAX 10000 Advanced EK-1001B-TS Nov. 1992
Troubleshooting
- DEC 10000, VAX 10000 System EK-1002B-SV Nov. 1992
Service Manual
- DEC 10000, VAX 10000 Platform EK-1000A-SV Nov. 1992
Service Manual
- DEC 10000, VAX 10000 Pocket EK-1000A-PG Dec. 1992
Service Guide
DEC/VAX 7000, DEC/VAX 10000 REFERENCE Manuals:
Title Part Number Availability
o VAX 7000 Console Reference Manual EK-70C0A-TM SEP. 1992
o KA7AA CPU Technical Manual EK-KA7AA-TM SEP. 1992
o KN7AA CPU Technical Manual EK-KN7AA-TM NOV. 1992
o MS7AA Technical Manual EK-MS7AA-TM SEP. 1992
o KFMSB/KZMSA Adapter Technical Manual EK-KXMSA-TM NOV. 1992
o DEC 7000, VAX 7000, Platform Handbook EK-7000A-HB DEC. 1992
o DEC 7000, VAX 7000, Platform Technical EK-7000A-TM NOV. 1992
Manual
o DEC 7000, VAX 7000, I/O System EK-70I0A-TM NOV. 1992
Technical Manual
DEC/VAX 7000, DEC/VAX 10000 Upgrade Manuals:
Title Part Number Availability
o KFMSB/KFMSA Adapter Installation EK-KXMSX-IN
Guide
o H7237 Batery PIU Installation Guide EK-H7237-IN
o DWLMA XMI PIU Installation Guide EK-DWLMA-IN
o Futurebus+ PIU Installation Guide EK-DWLAA-IN
o BA654 Disk PIU Installation Guide EK-BA654-IN
o BA655 Disk PIU Installation Guide EK-BA655-IN
o KN7AA CPU Installation Guide EK-KN7AA-IN
o KA7AA CPU Installation Guide EK-KA7AA-IN
o MS7AA Memory Installation Guide EK-MS7AA-IN
o DWMBB VAXBI PIU Installation Guide EK-DWMBB-IN
All documentation, except where noted above will be available on
CDROM and therefore available to TIMA. All documentation available
30 days prior to FRS will be submitted for the SSK.
EXTERNAL VENDORS:
o ABB CEAG GMBH
CEAG will be the vendor for the Bulk AC to DC convertors
and the AC Front End.
BOA #: TBD Vendor Contact: TBD
o SOLA the vendor for the PIU (Plug-in Unit) Power
supplies (supplies for the XMI, FutureBus+ etc.)
BOA #: TBD Vendor Contact: TBD
o EBM Blower Assy Vendor for all systems
BOA #: TBD Vendor Contact: TBD
o East Penn, Battery vendor for U.S. and GIA systems
BOA #: TBD Vendor Contact: TBD
o Sonnenschein, Battery vendor for systems built in Europe.
BOA #: TBD Vendor Contact: TBD
REVISION CONTROL/COMPATIBILITY:
Since LASER is a new platform it is expected that there will be
no compatibility issues at FRS at the Kernel level.
FutureBus+ will also be so new that compatibility issues should
not be a high risk during this time frame.
The XMI and BI adapter revisions for the LASER Platform will be
defined in the Revision Matrix document and be available on TIMA.
FCO STRATEGY:
The only change in FCO strategy over the VAX6000 is the added
ability to do firmware upgrades via CDROM.
There are presently no known FCO's planned for this product.
PRODUCT PHASE DOWN:
LASER is expected to be the platform for the 90's Phase 5 exit
is presently TBD.
|
| 147.8 | ALPHA CD-LIBRARY PRICING AND PACKAGING | KERNEL::CLARK | STRUGGLING AGAINST GRAVITY... | Thu Mar 25 1993 09:49 | 109 |
|
From: ZEKE::SADTLER "22-Feb-1993 0642" 22-FEB-1993 12:44:08.48
To: ACESPS::KEILLOR,DONVAN::CICALESE,SONATA::SULLIVAN,SHIRE::FITZGERALD
CC: SONATA::MERCURY,BOARDS::FORKEY,VELVET::BAKER,SADTLER
Subj: Alpha CD-Library Pricing and Packaging
+---------------------------+ TM
| | | | | | | |
| d | i | g | i | t | a | l | INTEROFFICE MEMORANDUM
| | | | | | | |
+---------------------------+
To: Distribution Date: February 21, 1993
From: Tom Sadtler
Dept: Software Business
Policy & Practices
Loc: ZKO1-3/D23
Net: ZEKE::SADTLER
DTN: 381-2924
(603)881-2924
cc:
Subject: Alpha CD-Library Pricing and Packaging
=============
Over the last several months, we have been developing the pricing and
packaging for the Alpha CD-Library. This has involved extensive
negotiations with SPS and the geography sales organizations. We
believe we have the pricing and packaging which returns the most
revenue and profitability to Digital.
Description: The CD-Library is a major distribution vehicle for
layered products on Digital's Alpha AXP systems (OpenVMS, OSF/1 and
NT). CD is the only distribution media currently planned for Alpha AXP
systems. The Alpha CD-Lib includes binaries and on-line documentation
for all Digital layered products running on Alpha AXP. The CD-lib
allows the customer to buy one distribution media kit for all their
Digital layered products. For large customers this reduces the
complexity and cost of installing and up-dating their Digital software
environment. The CD-Lib also allows them to have a central repository
and point of control for all on-line documentation.
The current product is in stage two of a five stage roll-out process.
During the roll-out the number of products is increasing from 11 in
stage one (1) to about 200 in stage five. Alpha AXP CD-Lib has an
introductory price of $300.
Issues requiring clarification: There are four pricing and packaging
decisions to be made.
1. What price should Digital charge for CD-Lib.
One price will not meet the needs of both the low-end
workstation/PC customer and the requirements of the large
customer. Because the high-end customer see the perceives the
greatest value in CD-Lib and because low-end customers may
perceive more complexity than value in the product, we are
pricing CD-Lib for the high-end customer. Our plan is to raise
the single release price of CD-Lib to $600 in stage three and
$800 at stage five, at the end of the ramp. This positions
CD-Lib at $200 less than the combined VMS/VAX CON-DIST and
Con-OLD. It also provides customers with a significant discount
if they buy the Alpha CDDS Subscription at $2,000, instead of
buying the four single versions for $3,200.
2. Should Digital offer individual products (IPOs), on-line
documentation and Bookreader on CDs?
For quality assurance reasons, IPO will not be offered unless
they are part of the quarterly consolidated database that is
used to master the CD-Lib.
IPOs are necessary to be able to meet the needs of the low-end
customer, and it allows for the continuation of the MDDS
service. IPOs will be priced in the $100 - $200 range. However,
the specific strategy for pricing the IPOs will be decided at
the Software and Services Pricing and Packaging Committee
meeting on March 4th.
3. Offering a separate CD-OLD product.
Many customers want to purchase additional copies of the on-line
documentation component of CD-Lib. CD-OLD has value for many
customers that want to manage all of their documentation from a
central location. However, the size of their user population and
the need for fast response times often necessitates to use of
more than one set of on-line documentation. This should be
offered at half the CD-Lib price, $150 through stage 2, $300 for
stages 3 and 4 and $400 from stage 5 on-ward.
4. Whether to include the operating systems on the CD-Lib?
Including the operating system on the CD-Lib adds additional
product cost and complexity to the release schedules. It should
not be included as part of Alpha AXP Cd-Lib.
5. Should ECOs be available for subscription service customers?
ECOs are available through TEMA. They will not be part of the
CD-Lib, but can be part of a service offering.
These decisions were all made to enable a relative smooth migration of
service customers from OpenVMS/VAX to OpenVMS/Alpha AXP. These
services were all developed as part of Digital's minicomputer
business. What is needed now is a new set of products an services that
will help establish Alpha as the preeminent client-server platform.
|
| 147.9 | CIXCD �-CODE ON ALPHA/VAX VMS CLUSTERS | KERNEL::CLARK | STRUGGLING AGAINST GRAVITY... | Thu Mar 25 1993 10:10 | 67 |
|
+---------------------------+TM
| | | | | | | |
| d | i | g | i | t | a | l | TIME DEPENDENT BLITZ
| | | | | | | |
+---------------------------+
BLITZ TITLE: CIXCD Microcode on Alpha/VAX VMSclusters
DATE: March 5, 1993
AUTHOR: Mike Johnson TD #: 1336
DTN: 226-6315
ENET: VCSESU::JOHNSONS CROSS REFERENCE #'s:
DEPARTMENT: VAXcluster Support Eng'g (PRISM/TIME/CLD#'s)
INTENDED AUDIENCE: (U.S./EUROPE/GIA) PRIORITY LEVEL: 2
(1=TIME CRITICAL,
2=NON-TIME CRITICAL)
=====================================================================
As many of your, hopefully, have heard, Digital has publicly announced
that we will be supporting both pure Alpha and mixed Alpha/VAX
VMSclusters in the very near future. As must be expected, the
introduction of Alpha clustering has some aspects which MUST be
communicated to the people who will install, maintain, operate, and
support these systems and clusters. One item of particular interest
and concern to me is the CIXCD and its associated microcode.
PLEASE BE AWARE OF THE FOLLOWING !!!
* ONLY the CIXCD-AC option (and T2080-YA module) are compatible with
the LASER platform.
* All CIXCD-AC options and T2080-YA modules are loaded with VAX
compatible microcode prior to shipment from option manufacturing.
Obviously, a CIXCD which has been factory integrated into an
DEC7000 or DEC10000 system will be re-loaded with AXP compatible
microcode.
* HOWEVER.....if a CIXCD option is field installed into a DEC7000 or
DEC10000, the Digital Services Engineer ***MUST*** re-load the
CIXCD microcode by using the console's LFU facility.
* FURTHER.....since a Services "spare" F6-T2080-YA module may be
used in EITHER a VAX or DEC system, the replacement module has an
equal chance of having the wrong version of microcode installed.
In either case, the LFU facility ***MUST*** be used to load the
correct code for the particular CPU type.
* Currently, but subject to change at any time, the MINIMUM usable
microcode revisions are CIXCD.BIN V46 for VAX systems and
CIMNA.BIN V01 for DEC systems. The LASER console will display
these as:
CIXCD (0C05) 4611 for VAX systems
CIXCD (0C2F) 0111 for DEC systems
*** DIGITAL INTERNAL USE ONLY ***
|
| 147.11 | ALPHA AXP GOOD NEWS BULLETIN | KERNEL::CLARK | STRUGGLING AGAINST GRAVITY... | Thu Mar 25 1993 12:52 | 128 |
|
+---------------------------+ TM
| | | | | | | |
| d | i | g | i | t | a | l | INTEROFFICE MEMORANDUM
| | | | | | | |
+---------------------------+
TO: ALPHA AXP "GOOD NEWS" DIST. DATE: February 25, 1993
FROM: Sarah Miller
DEPT. AR/PR Manager, CSG/AVS
MAIL: BXB1-1/F04
DTN: 293-5420
ENET: MSBCS::MILLER
Subject: ALPHA AXP WEEKLY "GOOD NEWS" BULLETIN
This is a special bulletin marking the first anniversary
of the Alpha AXP architecture and chip technology. It is
being distibuted to all audiences today.
DISTRIBUTION SCHEDULE:
Thursday, 2/25/93 - Internal
- Industry and Financial Analysts
- Press and Customers
February 25, 1993
ALPHA AXP MILESTONES - THE FIRST YEAR
February 25, 1992: Digital introduces its new Alpha AXP 64-bit
RISC architecture and 150-MHz DECchip 21064 microprocessor.
Cray Research and Kubota Pacific Computer announce they will
license Alpha AXP technology.
April, 1992: Digital unveils a software roll-out road map for
the DEC OSF/1 for AXP and OpenVMS AXP operating systems.
April, 1992: Digital and Microsoft jointly announce that the
Microsoft Windows NT operating system will be made available
on Alpha AXP-based computer systems.
April-May, 1992: Digital displays 25 working third-party
applications on early production Alpha AXP systems during
DECWORLD '92 in Boston. More than 30,000 people view
demonstrations of deskside/desktop workstations, a departmental
system, and a data center system. The "Wall of Fame" listing
of 700 companies pledging to port 1,200 applications to the
Alpha AXP architecture debuts.
June, 1992: Digital announces plans to build a $425-million
semiconductor manufacturing facility in Hudson, Mass. to
produce future generations of Alpha AXP microprocessors. The
facility is scheduled to be in use by 1996.
June, 1992: Digital and UNIX System Laboratories jointly
announce plans to ensure that UNIX System V Release 4.2 will
be made available to run on Alpha AXP-based computer systems.
June, 1992: Ing. C. Olivetti & Co. licenses Alpha AXP
technology.
July, 1992: Digital officially renames the VMS operating system
to "OpenVMS" and introduces 13 Alpha-ready OpenVMS VAX systems
and servers.
July, 1992: Raytheon Company licenses licenses the Alpha AXP
architecture for military computer systems.
September, 1992: Digital completes opening of 34 application
migration centers worldwide and shipping of more than 1,000
AXP systems to software developers.
November, 1992: Digital formally introduces Alpha AXP computing
-- systems, software, applications, and services -- including
the first Alpha AXP-based computer systems ranging from
workstations to mainframes, the OpenVMS AXP operating system
and 11 OpenVMS AXP layered software products, and a DEC OSF/1
for AXP software development environment. Encore Computer
Corporation announces it will license Alpha AXP technology.
November, 1992: Four hundred software development partners
worldwide announce availability dates for nearly 900 technical
and commercial applications for Alpha AXP computing. More
than 400 of these OpenVMS AXP and DEC OSF/1 for AXP
applications are scheduled to be available by March, 1993.
January, 1993: The "Wall of Fame" listing now includes 1,084
companies and more than 2,000 commercial and technical
applications.
February, 1993: Digital and Europe's Advanced Computer Research
Institute (ACRI) jointly announce that the Alpha AXP
architecture will be incorporated into the orginal ACRI
high-performance computing architecture and that Digital and
ACRI will cooperate on optimizing the DEC OSF/1 for AXP
operating system for parallel multiprocessor systems.
February, 1993: Digital targets OEM markets with cost-optimized
Alpha AXP microprocessor family, plus the DECelx real-time
operating system and DEC OSF/1 operating system real-time
extensions for Alpha AXP microprocessors. Digital is now
working with more than 35 OEM partners to design Alpha AXP
technology into their products.
February, 1993: Digital ships 26 OpenVMS AXP layered software
products ahead of schedule. With the 11 layered products
introduced in November, 1992, Digital now provides a complete
software suite to developers, systems integrators, and
end-users of Alpha AXP systems.
February 25, 1993: Digital announces availability and pricing
for its 200-MHz DECchip 21064 microprocessor, price reductions
for its 150-MHz DECchip 21064 microprocessor, and expansion of
the DECchip Alpha AXP microprocessor family into the desktop
and embedded markets.
IN THE YEAR AHEAD... More Alpha AXP applications, including
database enablers... more layered software products...
DEC OSF/1 for AXP and Microsoft Windows NT operating systems...
new workstations, desktop systems, and servers... new chip
technology... more technology partners...
|
| 147.12 | ALPHA SUPPORT LIBRARY ON CD-ROM | KERNEL::CLARK | STRUGGLING AGAINST GRAVITY... | Fri Mar 26 1993 13:00 | 110 |
|
From: ZEKE::SADTLER "22-Feb-1993 0642" 22-FEB-1993 12:44:08.48
To: ACESPS::KEILLOR,DONVAN::CICALESE,SONATA::SULLIVAN,SHIRE::FITZGERALD
CC: SONATA::MERCURY,BOARDS::FORKEY,VELVET::BAKER,SADTLER
Subj: Alpha CD-Library Pricing and Packaging
+---------------------------+ TM
| | | | | | | |
| d | i | g | i | t | a | l | INTEROFFICE MEMORANDUM
| | | | | | | |
+---------------------------+
To: Distribution Date: February 21, 1993
From: Tom Sadtler
Dept: Software Business
Policy & Practices
Loc: ZKO1-3/D23
Net: ZEKE::SADTLER
DTN: 381-2924
(603)881-2924
cc:
Subject: Alpha CD-Library Pricing and Packaging
=============
Over the last several months, we have been developing the pricing and
packaging for the Alpha CD-Library. This has involved extensive
negotiations with SPS and the geography sales organizations. We
believe we have the pricing and packaging which returns the most
revenue and profitability to Digital.
Description: The CD-Library is a major distribution vehicle for
layered products on Digital's Alpha AXP systems (OpenVMS, OSF/1 and
NT). CD is the only distribution media currently planned for Alpha AXP
systems. The Alpha CD-Lib includes binaries and on-line documentation
for all Digital layered products running on Alpha AXP. The CD-lib
allows the customer to buy one distribution media kit for all their
Digital layered products. For large customers this reduces the
complexity and cost of installing and up-dating their Digital software
environment. The CD-Lib also allows them to have a central repository
and point of control for all on-line documentation.
The current product is in stage two of a five stage roll-out process.
During the roll-out the number of products is increasing from 11 in
stage one (1) to about 200 in stage five. Alpha AXP CD-Lib has an
introductory price of $300.
Issues requiring clarification: There are four pricing and packaging
decisions to be made.
1. What price should Digital charge for CD-Lib.
One price will not meet the needs of both the low-end
workstation/PC customer and the requirements of the large
customer. Because the high-end customer see the perceives the
greatest value in CD-Lib and because low-end customers may
perceive more complexity than value in the product, we are
pricing CD-Lib for the high-end customer. Our plan is to raise
the single release price of CD-Lib to $600 in stage three and
$800 at stage five, at the end of the ramp. This positions
CD-Lib at $200 less than the combined VMS/VAX CON-DIST and
Con-OLD. It also provides customers with a significant discount
if they buy the Alpha CDDS Subscription at $2,000, instead of
buying the four single versions for $3,200.
2. Should Digital offer individual products (IPOs), on-line
documentation and Bookreader on CDs?
For quality assurance reasons, IPO will not be offered unless
they are part of the quarterly consolidated database that is
used to master the CD-Lib.
IPOs are necessary to be able to meet the needs of the low-end
customer, and it allows for the continuation of the MDDS
service. IPOs will be priced in the $100 - $200 range. However,
the specific strategy for pricing the IPOs will be decided at
the Software and Services Pricing and Packaging Committee
meeting on March 4th.
3. Offering a separate CD-OLD product.
Many customers want to purchase additional copies of the on-line
documentation component of CD-Lib. CD-OLD has value for many
customers that want to manage all of their documentation from a
central location. However, the size of their user population and
the need for fast response times often necessitates to use of
more than one set of on-line documentation. This should be
offered at half the CD-Lib price, $150 through stage 2, $300 for
stages 3 and 4 and $400 from stage 5 on-ward.
4. Whether to include the operating systems on the CD-Lib?
Including the operating system on the CD-Lib adds additional
product cost and complexity to the release schedules. It should
not be included as part of Alpha AXP Cd-Lib.
5. Should ECOs be available for subscription service customers?
ECOs are available through TEMA. They will not be part of the
CD-Lib, but can be part of a service offering.
These decisions were all made to enable a relative smooth migration of
service customers from OpenVMS/VAX to OpenVMS/Alpha AXP. These
services were all developed as part of Digital's minicomputer
business. What is needed now is a new set of products an services that
will help establish Alpha as the preeminent client-server platform.
|
| 147.13 | DEC 3000 MODEL 400/400S PRODUCT SUPPORT PLAN | KERNEL::CLARK | STRUGGLING AGAINST GRAVITY... | Fri Mar 26 1993 13:04 | 284 |
| *******************************************************************************
* *
* *
* | | | | | | | | ************************** *
* |D|I|G|I|T|A|L| * COMPANY CONFIDENTIAL * *
* | | | | | | | | ************************** *
* *
* *
* UK Product & Technology Group *
* *
* U K S E R V I C E P L A N *
* ------------------------------------ *
* *
* ***** ACTION REQUIRED ***** *
* *
* Ref: UKsp/tp/Mar93 *
* *
* PRODUCT NAME: DEC3000 Model 400 & 400S - PROJECT Sandpiper *
* *
* *
* FCS: Q2/FY93 *
* *
*******************************************************************************
UK SERVICE PLAN
************************
DEC 3000 AXP Model 400 & 400S
****************************************
1 DESCRIPTION
The DEC 3000 AXP Model 400 is a high performance desktop
workstation, the DEC 3000 AXP Model 400S is the server version of
this product and differs to the workstation in that the graphics
capabilities are not used and no graphics display device is
supplied.
The DEC 3000 AXP Model 400 employs the DEC 21064 microprocessor
which is the first implementation of DIGITAL's Alpha AXP
Architecture. The CPU is run at 133 MHz (7.5 nS cycle time) and
provides approximately 105 SPECmarks of system performance.
The DEC 300 AXP Model 400/400S is supported by OpenVMS AXP and
DEC OSF/1 AXP operating systems.
The DEC 3000 AXP Model 400/400S consists of:
o A desktop enclosure
o System module
o I/O module
o Memory subsystem
o Power supply
o Graphics card (Model 400 only)
o Monitor (Model 400 only)
o Keyboard (Model 400 only)
o Mouse (Model 400 only)
Support is provided for:
o Two internal half-height fixed disk drives (RZ series)
o One 5 1/4 inch or 3 1/2 inch removable media device
o Up to 9 additional external SCSI devices
System Module:
o 133 MHz DEC 21064 CPU chip
o 256 Kb secondary instruction and data cache
o Main memory controller
o TURBOCHANNEL controller
I/O Module:
o 3 TURBOCHANNEL connectors
o Dual SCSI controllers
o Ethernet, ISDN, Printer and Sync/Async Comms ports
o 512 Kb FEPROM for system firmware
o Console security jumper
o Audio input/output capability
Memory Subsystem:
o Supports up to 128 Mb
o ECC double bit detection and single bit correction
Physical dimensions (enclosure system only):
o Height 12.7 cm - 5.00 in
o Width 51.0 cm - 20.09 in
o Depth 44.5 cm - 17.50 in
o Weight 20 Kg - 45.00 lbs
Electrical Specifications:
o Input Voltage 100-120 and 220-240 VAC (autosensing)
o Current 10 A at 110 VAC, 5 A at 230 VAC
o Frequency 47-63 Hertz
o Power 300-400 W (depends on internal options)
o Power Factor 0.6 maximum
2 UK FCS (FIRST CUSTOMER SHIP) = Q2FY93
3 ENGINEERS REQUIRED
Training:
EY-1156E Alpha AXP Architecture Concepts 1 day CBI
EY-F480E TurboChannel Concepts 1 day CBI
EY-I087E DEC 3000 AXP Model 400 Inst & T/S 1 day CBI
Diagnostics:
There are no loadable diagnostics applicable to the DEC 3000 AXP
Model 400. All product specific diagnostics are contained within
the system firmware stored in flash ROM. See the DEC 3000 AXP Model
400 Service Information Manual for further details.
Special Tools and Test Equipment:
There are no special tools or test equipment required to service the
DEC 3000 AXP Model 400 in the field.
System firmware (includes operating system specific PALcode) is stored
in Flash ROM and may be updated in the field. System firmware is
normally distributed on CDROM but updates may also be obtained over the
internal DIGITAL network. Flash ROM firmware may be updated from the
local CDROM reader, from a local copy installed on a hard disc or via
the customer network.
Documentation available:
Order Number Description
------------ -----------
EK-SNDPR-OP DEC 3000 AXP Model 400/400S Options Guide
EK-SNDPR-QC DEC 3000 AXP Model 400 Workstation Set Up
EK-SNDSV-QC DEC 3000 AXP Model 400S Server Set Up
EK-SNDPR-SV DEC 3000 AXP Model 400/400S Service Guide
EK-SNDPR-TM DEC 3000 AXP Model 400/400S Technical Summary
EK-A0377-UG OpenVMS Factory Installed Software User Information
EK-SFFIS-UG DEC OSF/1 AXP Factory Installed Software User Info
EK-SNDPR-IC BA47-AA Virtical Floor Stand Installation
5 CALL FLOW
Call flow for the DEC 3000 AXP Model 400/400S will follow the
processes already in place for current workstation products.
Escalation of product related problems should follow current
procedures and should employ the CLD process for escalation to
engineering.
6 LOGISTICS/ESSB
There are no special logistic procedures for the DEC 3000 AXP Model
400/400S. Spares will be obtained via normal logistics channels.
Part Numbers:
Part No. Description RSL
-------- ----------- ---
54-21149-02 System Board YES
54-21813-01 I/O Board YES
54-21815-01 MMB (Memory Mother Board) YES
54-21139-BA SIM, 2Mb YES
54-21139-CA SIM, 4Mb YES
54-21139-DA SIM, 8Mb YES
H7816-AA Power Supply YES
17-03489-01 Drive Power Cable YES
17-03487-01 SCSI Cable, Long YES
17-02488-01 SCSI Cable, Short YES
54-21833-01 Turbochannel Dual DMA SCSI YES
54-21856-01 Turbochannel NVRAM(1Mb) YES
12-25083-01 Printer Port Loopback YES
12-22196-01 Thickwire Ethernet Loopback YES
12-30552-01 SCSI Terminator YES
H4082-AA 10BaseT Ethernet Loopback YES
29-24795-01 Modem Port Loopback YES
54-19876-01 SCSI Controller(PMAZ-AB) NO
54-19874-01 Ethernet Controller(PMAD-AA) NO
54-20609-01 Monchrome Frame Buffer(MX)(PMAG-BA) NO
Logistics ..../continued....
Part No. Description RSL
-------- ----------- ---
54-19815-01 Colour Frame Buffer(CX)(PMAG-BA) NO
DEFZA-AA FDDI Interface Module NO
54-20623-01 TCE Interface Module NO
54-21143-01 Smart Frame BUffer(HX)(PMAGB-BA) NO
54-21143-02 Smart Frame Buffer(HX)(PMAGB-BC) NO
54-21143-03 Smart Frame Buffer(HX)(PMAGB-BE) NO
54-20314-01 2D Graphics Accelerator(PX)(PMAG-CA) NO
30-35790-01 True Colour Frame Buffer 66Hz(TX)(PMAG-JA) NO
30-35790-02 True Colour Frame Buffer 72Hz(TX)(PMAG-JA) NO
30-35788-01 True Colour Frame Buffer, Picture-in-Picture NO
54-21085-01 3D Graphics Accelerator 66Hz(PXG)(PMAG-DA) NO
54-21085-02 3D Graphics Accelerator 72Hz(PXG+)(PMAGB-DA) NO
54-21085-04 3D Graphics Accelerator 66Hz(PXG+)(PMAGB-DC) NO
54-21085-02 3D Graphics Accelerator 66Hz(PXG+)(PMAG-EA) NO
54-20185-05 3D Graphics Accel, Z-buffer 72HZ(PXG+)(PMAGB-EA) NO
54-20185-06 3D Graphics Accel, Z-buffer 66HZ(PXG+)(PMAGB-EC) NO
54-20114-01 3D Graphics Accel. 66Hz(PXG Turbo)(PMAG-FA) NO
54-20114-02 3D Graphics Accel. 72Hz(PXG Turbo+)(PMAGB-FA) NO
54-20410-AA 8 Bit Z-buffer NO
54-20352-AA 16 Bit Z-buffer NO
54-20116-AA 8 Plane Video SIMM NO
7 HARDWARE SALES FORECASTS
FY93 FY94 FY95 TOTAL
----------------------------------------------
770 3000 2200 5970
8 HARDWARE CONFIGURATION
The DEC 3000 AXP Model 400/400S is a bounded system with dual SCSI
busses and three TURBOCHANNEL connections. A dual SCSI TURBOCHANNEL
option is also available. Numerous interface/controller options are
available for the TURBOCHANNEL including; graphics accelerators,
FDDI and Ethernet.
9 PRODUCT SERVICEABILITY
MTTI - 0.5 Hours
MTBF - TBD Months
MTBI - TBD Months
MTTR - 1.0 Hours
(Some of this information is not yet available - an updated service
plan will be released at a later date.)
UK Digital Product Services Product Focus Engineer:
John Kennedy - John Kennedy @UVO, PSTVX1::KENNEDY
UK Digital Product Services HW Product Planner:
Toze Pena - Toze Pena @UVO, KERNEL::PENAT
10 MIGRATION
To assist customers in migrating their applications from OpenVMS
VAX, ULTRIX (and other UNIX environments) to Alpha AXP platforms,
DIGITAL has developed the DECmigrate application. DECmigrate is
available to run on OpenVMS VAX and Alpha AXP platforms (running
OpenVMS AXP or DEC OSF/1 AXP) and DEC MIPS (running OSF/1 and
ULTRIX) platforms so that migration effort is not conditional on
the availability of the ALPHA AXP system. DECmigrate is capable of
translating VAX or DEC MIPS image files directly into Alpha AXP
executable images.
A range of migration services are available from DIGITAL SERVICES,
contact your local TCC (Technology Consulting Centre) for further
information.
...oooOOOooo...
|
| 147.14 | DEC 7000/10000 MODEL 600 PLATFORM PRODUCT SUPPORT PLAN | KERNEL::CLARK | STRUGGLING AGAINST GRAVITY... | Wed Mar 31 1993 10:20 | 684 |
|
*******************************************************************************
* | | | | | | | | ************************** *
* |D|I|G|I|T|A|L| * COMPANY CONFIDENTIAL * *
* | | | | | | | | ************************** *
* *
* UK Product & Technology Group *
* *
* U K S E R V I C E P L A N *
* ------------------------------------ *
* *
* ***** ACTION REQUIRED ***** *
* *
* Ref: UKsp/tp/Oct92 REV A (VAX7000) *
* UKsp/tp/Dec92 REV A (VAX10000) *
* *
* UKsp/tp/Mar93 REV B (VAX7000/VAX10000) *
* *
* PRODUCT NAME: VAX7000 Model 600 - Project LASER Model Neon *
* VAX10000 Model 600 - Project BLASER Model Neon *
* *
* FCS: Q2/FY93 *
* *
*******************************************************************************
UK SERVICE PLAN - VAX 7000 & VAX10000 Model 600
**********************************************************
1.0 DESCRIPTION
Product Description
The VAX 7000 Model 600 and the VAX 10000 Model 600 are
based on the LASER platform. The main difference between the
VAX 7000 and VAX 10000 are the cabinet configurations:
o The VAX 7000 is normally a single cabinet system
o The VAX 10000 is normally a three cabinet system with
two optional half-width battery cabinets
The VAX 10000 can be looked on as a fully expanded VAX 7000.
The VAX 7000/10000 is based on the LASER platform. Internally this
product has been known as LASER/BLASER Model NEON, in future it
must be referred to as the VAX 7000 Model 600 or VAX 10000
Model 600 as appropriate.
The term "LASER" refers to the multiprocessor system platform
which includes power and packaging, system interconnect, and
I/O structure in a single cabinet. LASER supports multiple
CPU architectures (VAX and Alpha AXP), multiple I/O architectures
(XMI,FutureBus+) and multiple operating systems (OpenVMS VAX
and OpenVMS AXP). LASER is the next generation platform for
future high performance systems.
Functional Description
The LASER System Bus or LSB is a limited length, non-pended,
synchronous 128 bit wide bus with distributed arbitration. Its
effective bandwidth is 753MB/sec (21nS clock rate). The LSB has
nine (9) slots which can support up to fsix (6) CPU's, up to
seven (7) memory array boards (Memory arrays can be put in
unoccupied CPU slots) and has one dedicated slot for the IOPC
or I/O Port Controller.
The LASER Platform uses a distributed power system with 48V DC
delivered to all functional areas of the platform. Voltages re-
quired for LSB boards, Plug-In-Units (PIU's) or other functional
sub-assemblies are derived from the 48V. Power sequencing is
controlled by the Cabinet Control Logic module (CCL).
Physical Description
LASER is slightly larger in dimensions than the VAX6000 but
conforms to IEEE 1301 (metric) standards. Footprint is 800mm
x 865mm and the height is 1700mm or somewhat taller than the
VAX6000. The weight of the LASER platform is dependent on the
number and type of PIU's or Plug-in-Units installed in the LASER
Cabinet.
The top portion of the LASER Cabinet contains the LSB (LASER
System Bus with CPU's, Memory array boards, I/O Port controller
and the AC front end and Bulk 48V converters. The top portion
also contains the OCP (Operator Control panel). The centre of
the cabinet contains the Blower Assembly. The lower portion of
the cabinet houses the PIU's, either I/O, Storage, or Battery-
Backup-Unit (BBU) or combinations of these PIU's. An example of
a PIU would be the XMI PIU enclosure, backplane/cardcage, power
supplies, and any adapters present in the XMI cardcage.
2.0 UK FCS (FIRST CUSTOMER SHIP) = Q2FY93
3.0 ENGINEERS REQUIRED
The service engineer profile for VAX7000/10000 is the same as the
VAX6000. The VAX7000/10000 utilises the XMI bus as its main I/O bus,
with the possibility Futurebus+ sometime in the future.
Current VAX6000 engineers, who will have XMI experience, are
most suited for development to VAX7000/10000 service engineers.
VAX7000/10000 Model 600 systems service strategy will be a
continuance of the VAX6000 (detection/isolation done by the RDC
with local personnel dispatched by the RDC).
Servicability Features:
o LASER Firmware can be updated off-line, locally and remotely
o Warm swap of embedded DSSI disks
o Non-volatile storage(EEPROM) for failure/error data logging
on each LSB module, including memories
o N+1 Power system allows for potential scheduled maintenance
and availability improvement
o Remote diagnosis of Power System
o High level of commonalty between the VAX7000/10000 system
console and other consoles developed for VAX based platforms.
o Higher reliability and availability goals than the VAX6000
o No Preventative Maintenance activity required.
VAX7000/10000 Model 600 SPECIFIC TRAINING
+--------------------------------------------------------------------+
| Course Title | Course Number |
+--------------------------------------------------------------------+
| Laser Platform Inst. & Maint. (AXP/VAX) | EY-L730E |
| FutureBus+ Concepts CBI | EY-F479E |
| VAX7000/10000 System Maint. Level 1 | EY-I882E |
+--------------------------------------------------------------------+
4.0 TOOLS & RESOURCES
The VAX7000/10000 will not follow the VAX Family diagnostic strategy
(i.e. the Diagnostic Supervisor will not be ported to run on the
VAX7000/10000 system). The VAX7000/10000 Console's Diagnostic
Execution environment has been developed to provide a common
run-time environment for all ROM-based and off-line loadable
diagnostics/exercisers. Programs run under the diagnostic executive
will run like any other program in the console's operating
environment.
VAX7000/10000 provides ROM-based exercisers for all kernel devices
and loadable exercisers for all supported boot devices.
The SDD Strategy for LASER is as follows:
o ERF and UERF
o VAXSimPlus, AES
o On-module NVM failure logging (EEPROMS on all LSB modules)
o Information Based Repair (IBR) support
VAX7000/10000 Model 600 DOCUMENTATION
-------------------------------------
Note: Several manuals are common with the VAX7000/10000.
VAX 7000 User Documentation:
Title Part Number Availability
---------------------------------------------------------------------
o DEC 7000, VAX 7000 Installation Kit EK-7000B-DK Nov. 1992
- DEC 7000, VAX 7000 Site Prep Guide EK-7000B-SP Nov. 1992
- DEC 7000, VAX 7000 Installation EK-700EB-IN Nov. 1992
Guide
o DEC 7000, VAX 7000 Hardware User EK-7001B-DK Nov. 1992
Information Kit
- DEC 7000, VAX 7000 Operational EK-7000B-OP Nov. 1992
Manual
- DEC 7000, VAX 7000 Basic EK-7000B-TS Nov. 1992
Troubleshooting
- VAX 7000, DEC 7000 Platform EK-7000B-HB Dec. 1992
Handbook
DEC 7000, VAX 7000 SERVICE Documentation:
Title Part Number Availability
---------------------------------------------------------------------
o DEC 7000, VAX 7000 Service EK-7002B-DK Nov. 1992
Information Kit
- DEC 7000, VAX 7000 Advanced EK-7001B-TS Nov. 1992
Troubleshooting
- DEC 7000, VAX 7000 System Service EK-7002B-SV Nov. 1992
Manual
- DEC 7000, VAX 7000 Platform EK-7000A-SV Nov. 1992
Service Manual
- DEC 7000, VAX 7000 Pocket Service EK-7700A-PG Nov. 1992
Guide
VAX/DEC 10000 USER Documentation:
Title Part Number Availability
--------------------------------------------------------------------
o DEC 10000, VAX 10000 Installation Kit EK-1000B-DK Nov. 1992
- DEC 10000, VAX 10000 Installation EK-100EB-IN Nov. 1992
Guide
- DEC 10000, VAX 10000 Site Prep EK-1000B-SP Nov. 1992
Guide
o DEC 1000, VAX 10000 Hardware User EK-1001B-DK Nov. 1992
Information Kit
- DEC 10000, VAX 10000 Operational EK-1000B-OP Nov. 1992
Manual
- DEC 10000, VAX 10000 Basic EK-1000B-TS Nov. 1992
Troubleshooting
- DEC 7000, VAX 7000 Platform EK-7000A-HB Dec. 1992
Handbook
DEC 10000, VAX 10000 SERVICE Documentation:
Title Part Number Availability
--------------------------------------------------------------------
o DEC 10000, VAX 10000 Service EK-1002B-DK Nov. 1992
Information Kit
- DEC 10000, VAX 10000 Advanced EK-1001B-TS Nov. 1992
Troubleshooting
- DEC 10000, VAX 10000 System EK-1002B-SV Nov. 1992
Service Manual
- DEC 10000, VAX 10000 Platform EK-1000A-SV Nov. 1992
Service Manual
- DEC 10000, VAX 10000 Pocket EK-1000A-PG Dec. 1992
Service Guide
DEC/VAX 7000, DEC/VAX 10000 REFERENCE Manuals:
Title Part Number Availability
----------------------------------------------------------------------
o VAX 7000 Console Reference Manual EK-70C0A-TM SEP. 1992
o KA7AA CPU Technical Manual EK-KA7AA-TM SEP. 1992
o KN7AA CPU Technical Manual EK-KN7AA-TM NOV. 1992
o MS7AA Technical Manual EK-MS7AA-TM SEP. 1992
o KFMSB/KZMSA Adapter Technical Manual EK-KXMSA-TM NOV. 1992
o DEC 7000, VAX 7000, Platform Handbook EK-7000A-HB DEC. 1992
o DEC 7000, VAX 7000, Platform Technical EK-7000A-TM NOV. 1992
Manual
o DEC 7000, VAX 7000, I/O System EK-70I0A-TM NOV. 1992
Technical Manual
DEC/VAX 7000, DEC/VAX 10000 Upgrade Manuals:
Title Part Number Availability
---------------------------------------------------------------------
o KFMSB/KFMSA Adapter Installation EK-KXMSX-IN
Guide
o H7237 Batery PIU Installation Guide EK-H7237-IN
o DWLMA XMI PIU Installation Guide EK-DWLMA-IN
o Futurebus+ PIU Installation Guide EK-DWLAA-IN
o BA654 Disk PIU Installation Guide EK-BA654-IN
o BA655 Disk PIU Installation Guide EK-BA655-IN
o KN7AA CPU Installation Guide EK-KN7AA-IN
o KA7AA CPU Installation Guide EK-KA7AA-IN
o MS7AA Memory Installation Guide EK-MS7AA-IN
o DWMBB VAXBI PIU Installation Guide EK-DWMBB-IN
All documentation will be available CDROM and available via TIMA.
5.0 CALL FLOW
The call flow and problem escalation follows normal procedures
and is identical to the VAX6000.
6.0 LOGISTICS
VAX7000/10000 Model 600 RSL - Recommended Spares List
-------------------------------------------------------
Part MTBF Qty/ Laser LOS STD
Number Description K hrs Sys Unique Spare cost
------ ----------- ----- ---- ------ ----- ----
LASER LSB
---------
-E2045-AA VAX 7000 CPU Module 112 1-4 Y Y $5803
-E2040-AA Ruby CPU Module (180 Mhz) 112 1-4 Y Y $5803
-E2040-?? Ruby CPU Module (200 Mhz) 112 1-4 Y Y $????
-E2044-AA IOPC Module 206 1 Y Y $2771
-E2043-AA 64mb Memory Module (MS7AA-AA) 100 1-7 Y Y $4385
-E2043-BA 128mb Memory Module (MS7AA-BA) 200 1-7 Y Y $6533
-E2043-CA 256mb Memory Module (MS7AA-CA) 173 1-7 Y Y $10774
-E2056-AA 512mb Memory Module (MS7AA-DA) ? 1-7 Y Y $14000
LASER Platform
--------------
- TK85-BX Tape Drive 30 0-1 N Y $1063
-RRD42-AA CDROM (Ruby Only) ? 1 N Y $244
12-35173-01 Main Blower Assembly 500 1 Y Y $880
30-33796-01 Bulk Regulator (North America) 200 1-3 Y Y $1935
30-33796-02 Bulk Regulator (Europe,GIA,Japan)200 1-3 Y Y $1935
30-33798-01 AC Input Box (N. America) 1,500 1 Y N $495
30-33798-02 AC Input Box (Europe & GIA) 1,500 1 Y N $495
30-33798-03 AC Input Box (Japan) 1,500 1 Y N $495
30-35143-01 DC Dist. Assy (Subrack) 750 1 Y N $529
54-19089-01 TF85 Controller ? 0-1 N Y $438
54-20300-01 Cabinet Control Logic 500 1 Y Y $201
54-20306-01 Operator Control Panel 1,000 1 Y Y $34
70-28574-01 LSB Centerplane/Cardcage 1,500 1 Y N $1613
XMI PIU Option [Quanties for single option]
-------------------------------------------
-T2020-00 XMI to NI Cont. 146 ? N Y $1421
-T2027-00 XMI to FDDI Cont. 94 ? N Y $2355
-T2028-AA LAMB Module (Laser to XMI) 135 1-4 Y Y $1944
-T2029-AB XMI/SCSI CONT. (AXP only) 146 ? Y Y $1348
-T2029-AC XMI/DSSI CONT. (AXP only) 146 ? Y Y $1348
-T2030-YA ARB(Clock & Arbitration) Module 390 1-4 Y Y $565
-T2036-AA XMI to DSSI Cont. (VAX only) 146 ? N Y $1848
-T2080-YA XMI to CI Cont. 218 ? Y Y $1792
30-36009-01 Module B (PWR) 200 1-4 Y Y $310
30-36010-01 Module A1 (PWR) 200 1-4 Y Y $237
70-30396-01 XMI Backplane Assy 500 1-4 Y N ?
FBUS+ PIU Option [Quanties for single option]
---------------------------------------------
(Supports RUBY Only - MARCH 1993 FRS)
--------------
-B2003-AA FLAG Module (Laser to FBUS+) ? 1 Y Y ?
30-36009-01 Module B (PWR) 200 1 Y Y $310
30-36011-01 Module A2 (PWR) ? 1 Y Y $237
54-21662-01 FBUS+ Backplane Assy ? 1 N N ?
Disk PIU Option [Quanties for single option]
--------------------------------------------
RZ35-E0 RZ35 Disk Drive (SCSI) 60 ? N Y $1004
54-19110-01 RZ73 Module ? ? N Y $330
54-19119-01 RF73-EA ECM Module ? ? N Y $361
54-20868-01 Local Disk Convertor 250 2-6 Y Y $230
54-21664-01 Disk Control Panel (DSSI) 1000 ? Y Y $98
54-21664-02 Disk Control Panel (SCSI) 1000 ? Y Y $98
70-28814-01 RF73/RZ73 HDA ? ? N Y $1040
Battery Backup PIU Option [Quanties are for single option]
----------------------------------------------------------
12-36168-02 Batteries * Y N $106
12-39982-01 Fuse [LPN-RK-90] 1-3 Y Y $10
17-03421-01 Battery Sensor Cable 1 Y N $7
17-03492-01 "A" Intermediate 1 Y N $55
17-03493-01 "B" or "C" Intermediate 2 Y N $55
17-03494-01 "A" to CEAG (Green Label)-Laser 1 Y N ?
17-03494-02 "B" to CEAG (Blue Label) -Laser 1 Y N ?
17-03494-03 "C" to CEAG (White Label)-Laser 1 Y N ?
17-03496-01 Balancing Cable - Blazer Expander ? Y N $6
17-03496-02 Balancing Cable - Blazer Expander ? Y N $6
17-03497-01 "A" to CEAG (Green Label)-Blazer CPU 1 Y N $29
17-03497-02 "B" to CEAG (Blue Label) -Blazer CPU 1 Y N $29
17-03497-03 "C" to CEAG (White Label)-Blazer CPU 1 Y N $29
17-03497-04 "A" to CEAG (Green Label)-Blazer Exp 1 Y N $15
17-03497-05 "B" to CEAG (Blue Label) -Blazer Exp 1 Y N $15
17-03497-06 "C" to CEAG (White Label)-Blazer Exp 1 Y N $15
Miscellaneous Cables
--------------------
17-00811-03 Console Terminal Cable 1 N N $3
17-02382-02 9' External DSSI Cable 1 N N $38
17-02382-07 DSSI Brick Jumper Cable 1 N N $26
17-03085-01 IO HOSE Cable, Long "114 1-4 Y Y $220
17-03085-02 IO HOSE Cable, Short "53 1-2 Y Y $199
17-03118-01 48V LSB PWR (GRY) 1 Y N $12
17-03118-02 48V LSB PWR (YEL) 1 Y N $12
17-03119-01 48V Pwr/Sig PIU (4:1 Cable) 1 Y Y $217
17-03120-01 Sig OCP/CCL 1 Y N $8
17-03121-01 Sig CCL/LSB Bulk 1 Y N $20
17-03122-01 Sig LSB Bulk/LSB BP 1 Y N $41
17-03123-01 Sig LDC/CCL 1 Y N $8
17-03124-01 Sig AC/CCL 1 Y N $10
17-03126-01 48V Pwr/Sense Blower 1 Y N $12
17-03127-01 Pwr 48V AC to LDC 1 Y N $6
17-03153-01 SCSI Brick Jumper Cable 1 N N $33
17-03153-03 9' External SCSI Cable 1 Y N $41
17-03162-01 Sig X-PIU 1 Y N $14
17-03163-01 48V Pwr X-PIU 1 Y N $42
17-03164-01 Pwr +5/+12 LDC/TF 1 Y N $6
17-03201-01 DEC Power Bus 1 Y N $3
17-03202-01 Pwr Dist X-PIU 1 Y N $55
17-03348-01 Sig, DSSI/Bulk {TK85} 1 Y N $49
17-03415-01 SCSI Bus Cable 1 Y N $32
17-03416-01 +5vb Jumper X-PIU 2 Y N $1
17-03417-01 RF73 Signal Cable 2 Y N $6
17-03418-01 LDC Power Cable 2 Y N $1
17-03419-01 LDC Signal Cable 2 Y N $2
17-03420-01 RF73 Power Cable 2 Y N $4
17-03422-01 Signal & Power Cable 1 Y N $2
17-03423-01 DCP to B/H 1 Y N $10
17-03424-01 DSSI Bus Cable 1 Y N $35
17-03443-01 Pwr LDC/Bulk 1 Y N $1
17-03444-01 Sig LDC/Bulk 1 Y N $10
17-03445-01 PWR, LDC to RRD42 2 Y N $3
17-03448-01 DSSI Bus TF to B/H 1 Y N ?
17-03505-01 5V VTERM Power Cable ? Y N $4
17-03508-01 48V CEAG to B/H 1 Y N $15
17-03511-01 Expander Cab to Host OCP 1 Y N $6
17-03531-01 SCSI RRD to B/H 1 Y N ?
17-03532-01 Storme Signal & Power Cable 1 Y N ?
17-03533-01 Bulkhead to XMI Signal Cable 1 Y N ?
7.0 HARDWARE SALES FORECASTS predicted for the UK are as follows:
Note: These figures are for VAX7000 _and_ VAX10000
Year UK Volume
---- ---------
FY93 ~300
FY94 ~250
FY95 ~ 60
---------
~610
---------
8.0 HARDWARE CONFIGURATION
___________________ ____________________
| | | | | |
| | | | | |
| 1 to 6 CPU's | | 1 to 7 Memories |
| | | | | |
| | | | | |
---------|--------- ---------|----------
| |
| (Nine slots) |
| LASER SYSTEM BUS (LSB) |
<========|=================|===================|==============>
|
|
---------|---------
| |
| I/O |
| PORT |
| MODULE |
| |
---|---|---|---|---
| | | |
| | | -----> Four I/O ports from the
| | ---------> IOP can connect to XMI or
| -------------> FutureBus+ PIU's
----------------->
HW Prerequisites
LASER being a new hardware platform has the following prerequi-
sites:
o SW - OpenVMS VAX V5.5
o HW - DEC Infoserver, required for Firmware updates and operating
system loading.
9.0 PRODUCT SERVICEABILITY
METRIC_____________VALUE_________UNIT
MTTI 8.0 Hours
MTTR 1.5 Hours
MTBC 19.0 Months
MTBF 27.4 Months
DUTY CYCLE 100.0 %
MTBPR 21.0 Months
SUPPORT RATIO 10-15 %
NMU 30%
10.0 Product & Technology Group (PTG):
The Product Focus Engineer within the PTG is John Kennedy
(PSTVX1::KENNEDY, John Kennedy @UVO)
....ooooOOOOoooo....
|
| 147.15 | DECchip 21064A-225 & 21064A-275 | KERNEL::BLAND | Norman Bland 833 3797 CSC, Basingstoke | Tue Nov 09 1993 04:02 | 142 |
| DECchip 21064A-225 & 21064A-275 Alpha AXP Microprocessors
Author
o Dave Jessel
o Kurt Benedini
Business partners can obtain further information from their Digital sales
contact.
Highlights
o Leadership performance
o State of the art 0.5 micron, 3.3 volt, four layer metal CMOS process
o Pin compatible with the existing family of DECchip 21064 products
o DECchip 21064A-225 samples available December 1993, volume quantities will
ship July 1994
o DECchip 21064A-275 samples available March 1994, volume quantities will
ship autumn 1994
Customer Problem
OEMs need to provide unmatched performance solutions spanning PCs and
enterprise servers for the emerging Windows NT market.
Digital Solution
DECchip 21064A-225 and 21064A-275 single-chip microprocessors enable Server
and PC OEMs to offer systems with two to three times the performance of
Pentium based systems at an equivalent price.
The DECchip 21064A-225 and DECchip 21064A-275 are single-chip microprocessors
that implement Digital's Alpha AXP architecture. They are manufactured using
a 0.5 micron CMOS process that provides a 50% improvement in clock speed and
allows for double the on-chip cache of previous DECchip 21064 products. These
chips provide unmatched performance for high end Windows NT desktop systems
and servers.
The DECchip 21064A-225 and DECchip 21064A-275 allow operation at 225 MHz and
275 MHz respectively. They are superscalar, using dual instruction issue and
superpipelined processors, that implement largely the same microarchitecture
as the original DECchip 21064.
The two versions of the DECchip 21064A also improve performance with an
enhanced floating-point divider and improved branch prediction logic over the
previous DECchip 21064 implementation.
The DECchip 21064A-225 microprocessor delivers an estimated performance of 135
SPECint92 and 205 SPECfp92 in a typical desktop system.
The DECchip 21064A-275 microprocessor delivers an estimated industry leading
performance of 170 SPECint92 and 290 SPECfp92 in a typical server system;
making it the highest performance commercially available chip.
The DECchip 21064A is the first member of Digital's advanced 0.5 micron, 3.3
volt, four layer metal CMOS process. Digital manufactures both versions of
the DECchip 21064A in Hudson, Massachusetts and South Queensferry, Scotland.
The new chips are pin compatible with the existing family of DECchip 21064
products. This enables DECchip 21064 customers to improve performance
significantly with minimal investment.
Customer Benefits
PC Windows NT and Server OEMs will be able to increase their market share by
producing leadership systems with unmatched performance based on DECchip
21064A microprocessors.
The new DECchip 21064A-225 and 21064A-275 chips are pin compatible with the
family of DECchip 21064 products. This allows DECchip 21064 customers to
improve performance without the cost of redesigning their motherboards.
Competitive Comparison
Vendor Digital Intel Sun MIPS HP IBM Digital
--------------------------------------------------------------------------------
Product supported 21064A Pentium SPARC R4400 PA7100 Power2 21064A
Frequency (MHz) 225 66 60 150 99 71.5 275
Number of chips 1 1 1 1 3 8 1
SPECint92 performance* 135 65 80 94 80 126 170
SPECfp92 performance* 205 56 100 105 150 260 290
64-Bit architecture Yes No No Yes No No Yes
Commercially available Yes Yes Yes Yes No No Yes
Price (1K Units) $965 $965 $934 $857 na na $1586
SPECint92 / $ (1K) 140 67 85 110 na na 107
* 21064A Performance numbers are estimates.
Channels Strategy
Contact your local Components and Peripherals Business Unit or TOEM Sales
group to place orders.
Ordering Information
Model No. Description
--------------------------------------------------------------------------------
21064-BB 21064A-225 MHz
21064-DB 21064A-275 MHz
Please contact your territory TOEM Sales Manager for pricing information.
Services
Return-to-factory warranty is provided.
Resources
Internal use only; business partners can obtain further information from their
Digital sales contact.
Comprehensive support for all Alpha AXP microprocessors is provided through
Digital's worldwide Application Engineering resources. This support includes
development tools and evaluation boards which will be available early in 1994.
If your customer is interested in designing with Alpha AXP chips, contact your
TOEM Account Manager or one of the following:
o Kurt Benedini, TOEM Business Development Manager Europe,
DTN: 865-3813, [49](89)95913813, RTO
o Elmar Selbach, TOEM Applications Engineering Europe,
DTN: 865-2937, [49](89)95912037
o Parivash Aram, Customer Marketing Engineer Europe,
DTN: 225-5038, [1](508)5685038
For additional information, please contact the DECchip Information Line on
800-DEC-2717.
AXP, Alpha AXP, DEC, and DECchip are trademarks of Digital Equipment
Corporation. OSF/1 is a registered trademark of Open Software Foundation, Inc.
Windows NT is a trademark of Microsoft Corporation. Pentium is a trademark of
Intel Corporation and Intel is a registered trademark of Intel Corporation.
|