| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 37.1 | Bill's nodename | SUPER::REGNELL | Smile!--Payback is a MOTHER! | Wed Feb 20 1991 20:31 | 9 |
|
Sorry Folks...Mind is popcorn tonight...
Bill's node is:
SUCCES::PRICE
Mel
|
| 37.2 | Is it soup yet?!? | MELKOR::HENSLEY | nil illegitimi carborundum | Tue Mar 05 1991 14:40 | 6 |
| Is it likely that this manual will be added to booklists for VMS
operations courses?
I know my students would be thrilled to have it!
irene
|
| 37.3 | Tentative 'yes' | SUPER::REGNELL | Smile!--Payback is a MOTHER! | Wed Mar 06 1991 08:47 | 7 |
|
Ummmm...
I think so...Andy? Emmalee? Is that the plan?
Mel
|
| 37.4 | Yes Yes Yes | CECV03::TARRY | | Thu Mar 07 1991 08:08 | 11 |
| Yes! The hardware manual will be included in appropriate courses such as VMS
for Operators, System and Network Management I, VMS Small System Environment.
and anywhere else it is deemed appropriate.
This is to replace references to hardware specifics in these courses. Nothing
makes a course look older than a picture of a VAX 11/785 or an RM05 disk drive.
All hardware pictures and start up, shut down, console procedures will be
included in the manual. Hardware will be added as it is introduced. Old
hardware need not be removed until the manual gets too thick to manage.
|
| 37.5 | thanks -- made my week!! | MELKOR::HENSLEY | nil illegitimi carborundum | Thu Mar 07 1991 12:15 | 1 |
| Wonnnerful wonnnerful wonnerful!!!!!
|
| 37.6 | Ayup! | CECV01::SADLER | anyone change a Flainian Pobble Bead? | Thu Mar 07 1991 18:35 | 12 |
| >
> I think so...Andy? Emmalee? Is that the plan?
>
That is the plan. We will include the book in the booklist for ALL courses that
need it. Obvious ones are Operator, System Manager I, Small System Manager.
Other suggestions welcome.
Cheers,
Andy
|
| 37.7 | Why not older hardware? | SUPER::MATTHEWS | | Mon Apr 08 1991 16:32 | 10 |
| I do have a question. Maybe it's rhetorical since nobody from the
field has raised it.
The book covers all the newer hardware, but what good does it do the
student if the labs are being run on old hardware? Last time I taught
in the field, it was on a 780 and a 785, and that was just a few months
ago.
Val
|
| 37.8 | Project plan | SUPER::MATTHEWS | | Mon Apr 08 1991 16:33 | 623 |
| In case you're wondering what the whole project plan looks like, here
it is:
ESDP Course Development Project Plan
Project Name: VMS Hardware Operations Lab Guide
Funding Group: Educational Services Corporate Marketing
ESDP Project Manager: Todd Nelson
Job Number: 050-000093
Date issued: 11-Dec-1990
Date revised: 8-April-1991
Version: 1.1
VMS Hardware Specific Operators Guide
Issued by: Date
________________________________________________________________
Todd Nelson
Approved by:
ESDP Project Plan
DIGITAL Internal Use Only
________________________________________________________________
Emmalee Tarry-ESCM Funding Representative
________________________________________________________________
Andy Sadler-ESCM Funding Representative
________________________________________________________________
Dave Killelea -ESDP Cost Center Manager
________________________________________________________________
Todd Nelson-ESDP VMS Course Development Unit Manager
ii
ESDP Project Plan
DIGITAL Internal Use Only
Informational copies:
Joe Guth Financial Analyst
Nancy Oliveira System Manager
Other Project Related People:
John Shack ESCM Operations
Manager
Andrea Kovacs ESCM U.S. Distribu-
tion Center Contact
Chris Lipscombe ES Reading U.K.
Translation Contact
Digital Equipment Corporation
iii
________________________
8-April-1991
__________
The information in this document is subject to change without
notice and should not be construed as a commitment by Digital
Equipment Corporation. Digital Equipment Corporation assumes no
responsibility for any errors that may appear in this document.
The software described in this document is furnished under a
license and may be used or copied only in accordance with the
terms of such license.
No responsibility is assumed for the use or reliability of
software on equipment that is not supplied by Digital Equipment
Corporation or its affiliated companies.
Restricted Rights: Use, duplication, or disclosure by the U.S.
Government is subject to restrictions as set forth in subpara-
graph (c)(1)(ii) of the Rights in Technical Data and Computer
Software clause at DFARS 252.227-7013.
__________
Copyright �1990 by Digital Equipment Corporation
All Rights Reserved.
Printed in U.S.A.
__________
The postpaid READER'S COMMENTS form on the last page of this
document requests the user's critical evaluation to assist in
preparing future documentation.
The following are trademarks of Digital Equipment Corporation:
DEC DIBOL UNIBUS
DEC/CMS EduSystem VAX
DEC/MMS IAS VAXcluster
DECnet MASSBUS VMS
DECsystem-10 PDP VT
DECSYSTEM-20 PDT
DECUS RSTS
DECwriter RSX DIGITAL
This document was prepared using VAX DOCUMENT, Version 1.2
ESDP Project Plan
DIGITAL Internal Use Only
1 PROJECT DEFINITION
1.1 Overview
We are going to create a guide for use by students attending VMS
courses. The guide will be used as a reference manual. It will
contain specific information about VAX 3000, 6000, 8000 and 9000
series of computers.
1.2 Problem Statement
It is difficult for students attending a VMS course to get the
information they need quickly because of the large number of
manuals they now have to reference.
2 COURSE DESIGN
2.1 Document Title
VMS Hardware Specific Operators Guide
2.2 Document Overview
The document will cover information on the VAX 9000, 8000, 6000
and 3000 systems.
2.3 Document Format
Lab Guide using LL doctype (student workbook .sdml coding)
2.3.1 Target Audience
This Lab Guide is designed to be used in the following courses:
VMS for Operators, System and Network Management 1, VMS System
Management: Single CPU.
1
ESDP Project Plan
DIGITAL Internal Use Only
2.4 Outline
VMS Hardware Lab Guide Outline
I. VAX 9000
A. Systems Configurations
1. System Cabinet overview
2. Physical Layout
3. I/O Bus Configuration
B. Operator Control Panel
1. Keyswitches
2. Indicators
C. System Operation
1. Powering up the System
2. Boot Operation
3. Halt Operation
4. Powering down the System
D. Console Commands
1. Console Command Language
2. Command Descriptions
E. Crash Procedures
1. Machine Check Handling
2. Keep-Alive Fail Handling
F. Peripherals
1. Disks
2. Tapes
3. Modems
4. VAXcluster
5. Network Hardware
II. VAX 8000
A. Systems Configurations
1. System Cabinet overview
2. Physical Layout
3. I/O Bus Configuration
2
ESDP Project Plan
DIGITAL Internal Use Only
B. Operator Control Panel
1. Keyswitches
2. Indicators
C. System Operation
1. Powering up the System
2. Boot Operation
3. Halt Operation
4. Powering down the System
D. Console Commands
1. Console Command Language
2. Command Descriptions
E. Crash Procedures
1. Machine Check Handling
2. Keep-Alive Fail Handling
F. Peripherals
1. Disks
2. Tapes
3. Modems
4. VAXcluster
5. Network Hardware
III. VAX 6000
A. Systems Configurations
1. System Cabinet overview
2. Physical Layout
3. I/O Bus Configuration
B. Operator Control Panel
1. Keyswitches
2. Indicators
C. System Operation
1. Powering up the System
2. Boot Operation
3. Halt Operation
4. Powering down the System
D. Console Commands
1. Console Command Language
2. Command Descriptions
3
ESDP Project Plan
DIGITAL Internal Use Only
E. Crash Procedures
1. Machine Check Handling
2. Keep-Alive Fail Handling
F. Peripherals
1. Disks
2. Tapes
3. Modems
4. VAXcluster
5. Network Hardware
IV. VAX 4000
A. Systems Configurations
1. System Cabinet overview
2. Physical Layout
3. I/O Bus Configuration
B. Operator Control Panel
1. Keyswitches
2. Indicators
C. System Operation
1. Powering up the System
2. Boot Operation
3. Halt Operation
4. Powering down the System
D. Console Commands
1. Console Command Language
2. Command Descriptions
E. Crash Procedures
1. Machine Check Handling
2. Keep-Alive Fail Handling
F. Peripherals
1. Disks
2. Tapes
3. Modems
4. VAXcluster
5. Network Hardware
4
ESDP Project Plan
DIGITAL Internal Use Only
V. VAX 3000
A. Systems Configurations
1. System Cabinet overview
2. Physical Layout
3. I/O Bus Configuration
B. Operator Control Panel
1. Keyswitches
2. Indicators
C. System Operation
1. Powering up the System
2. Boot Operation
3. Halt Operation
4. Powering down the System
D. Console Commands
1. Console Command Language
2. Command Descriptions
E. Crash Procedures
1. Machine Check Handling
2. Keep-Alive Fail Handling
F. Peripherals
1. Disks
2. Tapes
3. Modems
4. VAXcluster
5. Network Hardware
2.5 Instructional Strategy
The information is presented in text format.
2.5.1 Document Organization
This guide is organized into a series of chapters. Each chapter
has its own VAX system information.
5
ESDP Project Plan
DIGITAL Internal Use Only
2.5.2 Field Review
The course developer will use instructor feedback from the
course notes conference as field review.
2.5.3 Module Review
Module review will come from instructors and other course de-
velopers that have reviewed the updated course modules via the
posted electronic files.
For module review, a note will be posted in the notes conference
SUPER::VMS_CURRICULUM pointing to a copy of the postscript file
for each module when it is available for review. The location
where the modules will be posted is SUPER::WORK6:[ES$REVIEW]VMS_
*.ps..
A note will be posted in the notes conference with a date that
will reflect the last day that review comments for each module
will be considered for input into the course. If time allows in-
put after that date may be considered. All comments in the notes
conference before the start of the project will be considered
also.
2.6 Publishing Strategy
2.6.1 Use of VAX DOCUMENT
The project will be done in VAX DOCUMENT. The style files used
will be LL for Lecture/Lab and .SDML coding standards will be
used to meet STYLE15B and ONLINE doctypes.
The style file version used will be V1.2B. Any changes in the
style files will NOT affect this project unless agreed upon by
the project manager and the funder.
The course deliverables will be published under the ESCM Lec-
ture/Lab guidelines. ESDP Release Engineering will insure that
deliverables meet or exceed ESCM guidelines and standards.
6
ESDP Project Plan
DIGITAL Internal Use Only
The course paging and contents will change based on the module
information provided in the Problem Statement section of this
plan.
2.6.2 Art
The course materials will contain approximately 50 Illustra-
tions. There may be additional illustrations covering any new
topics covered as part of this project.
2.6.3 Preliminary Materials
As required.
7
ESDP Project Plan
DIGITAL Internal Use Only
3 PROJECT DELIVERY
3.1 Quality Assurance Strategy
The quality strategy will be to use the course notes conference
and electronic module review as the methods of receiving review
from the delivery organizations.
3.2 Pilot
N/A
8
ESDP Project Plan
DIGITAL Internal Use Only
3.3 Deliverables
Unless otherwise stated, the deliverables listed will be one
master delivered to the funder or his/her representative. The
funder will be responsible for reproduction and distribution of
all deliverables.
________________________________________________________________
Table_1:__VMS_Hardware_Operations_Lab_Guide_Deliverables________
Item____________________Page/Size_______________Comment_________
Student Workbook approx. 400 pages EY-G995E-XX-0001
Source Files for See section on
Translation_____________Translation_____________________________
METHOD OF DELIVERY
All guides will be available as electronic masters and
will be posted for electronic transfer to Reading and Ni-
jmegan. Educational Services Corporate Marketing will send
the electronic masters to the U.S. distribution center.
3.4 Translation/Internationalization
This course will be written and edited in accordance with trans-
lation and internationalization guidelines. These guidelines
are established in the International Engineering, Producing
International Products Reference Set.
9
|
| 37.9 | HSC controllers? | SUPER::MATTHEWS | | Mon Apr 08 1991 16:34 | 3 |
| I'd also like to know whether the various HSC controllers are being
covered or not. The outline says something about "VAXcluster," but
that's not very specific.
|
| 37.10 | List of chapters | SUPER::MATTHEWS | | Sat Jul 13 1991 16:21 | 32 |
| Here's a list of the chapters. I'm not posting every single one for
review unless you'd like me to, just a few representative ones (marked
below with *) so you can see what kind of information we are including.
CHAP 1... VAX 9000
" 2... VAX 8820, 8830, 8840
" 3... VAX 8600, 8650 *
" 4... VAX 8530, 8550, 8810, 8820 *
" 5... VAX 8200, 8300
" 6... VAX 6000 *
" 7... VAX 11/780, 11/785 *
" 8... VAX 11/750
" 9... MicroVAX, VAXstation,and VAXserver 3400, 3600, 3900
" 10... VAXstation 3520, 3540
" 11... VAXstation 3100, MicroVAX 3100
" 12... VAXstation 2000, MicroVAX 2000
" 13... VAXstation II, II/GPX & MicroVAX II *
" 14... Peripherals
|
| 37.11 | | GOONS::BAKER | What does "ignorant" mean? | Sun Jul 21 1991 17:07 | 35 |
| Hi,
I have a few comments on the machines which seem to be covered. I
haven't looked at any of the modules yet, so I'm just "judging-by-title"...
>> " 2... VAX 8820, 8830, 8840
>> " 4... VAX 8530, 8550, 8810, 8820 *
The machine details have faded a bit now, but if I remember correctly
there was (originally) the 8500, 8530, 8550, 8700 and 8800 which all
boot via the Pro console. Later came the 8810/20/30/40.
I think the 8810 may have been a renamed 8700 (with a Pro), but at
least some of these later 88x0 machines had a microVAX console, which made
booting different yet again.
I think it would be better to group the machines into their relevant
Pro/mVAX console types.
>> " 5... VAX 8200, 8300
For completeness, it might be better to include the 8250/8350 in the
title as well (and the body obviously!)
>> " 9... MicroVAX, VAXstation,and VAXserver 3400, 3600, 3900
Again, for completeness, I'd like to see 3300, 3500, 3800 mentioned (or
perhaps 3400 Series, 3600 Series... instead.)
Lastly, although it's not in the "spec", I'd definately like to see
some info on booting the 4000(s).
My 2� worth... (less than two pence :-) )
Stephen
|
| 37.12 | | SUPER::MATTHEWS | | Tue Jul 23 1991 17:46 | 14 |
| Thanks, Stephen!
The groupings are identical to those in the corresponding "VMS
Installation and Operations" books in the VMS doc set (the contents
themselves are lifted from those books), so we're pretty much stuck
with them. They are grouped by console as far as I can tell; Chapter 4
should have said " ...8820-N" to distinguish it from the 8820 with the
MicroVAX console.
We'd like to do the 4000, but there's no VMS book for it yet and
we don't have the resources to develop the information from scratch.
Val
|
| 37.13 | | SUPER::MATTHEWS | | Tue Jul 23 1991 17:50 | 4 |
| Oops, I thought I posted the chapter locations in .10, which was the
whole idea (blush). They are in
{HARDY,SUPER}::ES$REVIEW:[HW_OPS]CHAP*.PS
|
| 37.14 | already presentable and accurate 4000 material | MELKOR::HENSLEY | ratbag in training | Mon Aug 12 1991 20:55 | 7 |
| Val - I sent you a pointer - but we may have VERY usable material for
the 4000 since the hardware course has been written.
See private mail for contact info, or contact the Unit Manager: Paula
Cassano (dtn 521-6534)
ih
|