| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 64.1 | View from the UK | UKEDU::SHONE | Keith Shone @RKA 830-4074 | Fri May 10 1991 12:14 | 25 |
| Module: Starting Up and Shutting Down a VMS System
My views - not necessarily those of my colleagues.
This module developed and flowed very well.
Page Comment
1-3 Bit of English and phrasing again:
"A VMS system usually remains running for long periods
of time. Under certain circumstances, however, you must
shut down the system."
Similarly in the next paragraph:
"The VMS system provides a command procedure that shuts
down the system at a..."
1-5 Bullet 3: add word "are" before "starting"
1-6 Bullet 4: typo know -> known
1-7 Bullet 4: odd "<" at end of line
|
| 64.2 | view of Holland | NWGEDU::WIERSMA | Drive a BENTLEY or walk... | Mon May 20 1991 17:19 | 31 |
| Review of chapter
STARTING UP AND SHUTTING DOWN A VMS SYSTEM
Page 1-6: After the fourth bullet.
STARTUP.COM should never be edited. Say never NEVER.
There are some products (CDD, DTR, ALL-in-1) where the installation
guide is saying that you have to edited STARTUP.COM
Page 1-10: Callout 9. Since VMS V5.0 there is always 2 shutdown options:
REBOOT_CHECK
SAVE_FEEDBACK
Page 1-11: Callout 14. After >>>H the messages looks different I thought.
I checked to be sure some machines here. (Micro vaxes) The said at
the end
PC EXT HLTD AT xxxxxxxx
Page 1-13 typo third shutdown messages UPER --> SUPER
An extra point. Do we leave @CRASH behind. It is a very important command to
have a stack dump. So you can analyze what has happened
For the rest is this a very good and SHORT chapter.
Bye Arjen.
|
| 64.3 | | GOONS::BAKER | What does "ignorant" mean? | Wed May 22 1991 10:42 | 62 |
|
Nice overview of starting/shutting. Just right for the intended audience.
I found the content differs from the SYSNET I Spec, but agree with the
decision. Leave startup phases for later.
Stephen
--------------------------------------------------------------------------
1-4 RESOURCES. The sentence "To complete..." implies that the manuals
are needed, or else the student won't be able to acheive the
objectives. There may be cases where these manuals are
unavailable during the course. I suggest removing the sentence
and just listing relevant books (as with earlier chapters).
1-5a 1st para. This is misleading, as the majority of todays disks cannot have
"volumes loaded into them".
4th para What is the "one final step"?
1-5 1st para Loading volumes again.
Next para & 2nd bull. Use of the word "almost" implies something else
has to be done. In the normal/simple cases there
is nothing else to do, unless you mean typing "B".
1-6 1st sent. Text implies the system is booted. Then STARTUP.COM is invoked.
I guess interpretation of the term "booted" is key here. A
possible alternative is "SYS$SYSTEM:STARTUP.COM is a major
component of the startup sequence. It executes shortly after
entering the BOOT command at the console."
1st bull. I'm not sure which logicals are defined for some of the listed
examples (lang/help processors). Perhaps use "system disk
directories (SYS$MANAGER etc)" instead.
4th bull Typo: know = known
7th bull Suggest rewording "SYS$MANAGER:SYLOGIN.COM - command procedure
all users execute upon logging in".
1-7 I'm unsure what "local DECnet" means.
3rd bull Suggest rewordinng to "After you establish DECnet
communications in this manner, users can SET HOST to and from
remote nodes"
4th bull Extraneous "<" at the end.
1-10a All the bulleted items are listed on p1-12. Do they need to be
here as well? Some do have additional text which could be
placed on 1-12a.
1-10/11 Title Suggest dropping reference to 11/780. This is a generic
example. Only the HALT command output is CPU specific.
Callouts could be shifted left a bit.
Query use of EASYnet nodename.
1-13a All of this text is on p1-14. Is it needed here as well? (I
guess it make life easier for the instructor though - no page
turning) .
1-13 Query use of EASYnet nodename
Nit: VMS version is 5.4, Example 1-1 (p1-10) was 5.2
1-16 Summary The majority of the summary items were not mentioned in the
chapter!
|
| 64.4 | Glad it worked... | SUPER::REGNELL | Modularity Maven | Wed May 22 1991 15:42 | 7 |
|
Thanks, Stephen. Yes, it does differ from the spec, but once I
started to write it, I just couldn't picture it working unless
I really slashed it back. [whew]
M_
|
| 64.5 | @CRASH not lost | SUPER::MATTHEWS | | Thu May 23 1991 11:18 | 5 |
| @CRASH and (or the corresponding method for systems that don't have
@CRASH) will be covered in the hardware operations guide (see note 37
in this conference; we'll post a review draft when it's ready).
Val
|
| 64.6 | more objectives & >>>@crash | TEACH::CHUCK | | Sat Jun 01 1991 01:00 | 6 |
| module 13: Page 1-3 Objectives could be more descriptive.
Maybe more of them (see summary for hints).
Page 1-15 Add ">>>@crash" to this module.
They need to know this. It can be told here
quick and clean.
|
| 64.7 | Comments from DC Training Center | TEACH::WENDY | | Mon Jun 03 1991 12:23 | 18 |
|
Module 13
Startup and Shutdown
1-5 2nd bullet
. If the system volume is mounted on the default system device *(drive)
3. boot the system *(you never tell them how)
1-6 You mention all the startup files but not how to edit them, does
SYSNET II cover those.?
1-7 3rd bullet from the bottom *(extra < at the end of the sentence)
Wendy Mullenhoff
|
| 64.8 | Comments from DC Training Center | TEACH::WENDY | | Mon Jun 03 1991 12:23 | 49 |
|
Module 14
Working with Queues
Why not rename the module to WORKING WITH PRINT AND BATCH QUEUES
1-3 INTRODUCTION- maybe say as a system manager you are responsible for
setting up print and batch queues, you make it sound as they have to set up
all queues.
1-4 Creating a queue *(Maybe say print and batch)
Controlling queues *(Print and batch)
1-5.Start/Queue/Manager device:[sysque]jbcsysque.dat
This forces all nodes to access the same queue manager and queue list.
*(maybe mention that all nodes in the cluster would have to issue
this same command)
1-6 In a vaxcluster, jobs are directed to *(an execution queue on a) specific
node
1-9 1. $show device L
Lists the devices and selects one. *(how does this select one?)
4.
<code example> *(is this supposed to be there?)
1-10 3. This queue will recieve default print jobs and dispense them to any
execution print queues that do not use the /NOENABLE_GENERIC qualifier
*(at the time the execution queue is set up.)
4. $Initialize/Queue/Start/Generic=(LPA0,LPB0) sys$print
*(maybe take out the name LPB0 so they see how to direct traffic to
just one of the exection queues that you set up in step 2.
The last sentecnce on this page makes no sense to me.
1-19 Delete/Entry *(you mention this, but you never talked about this command
in the chapter, isnt it Delete/entry=)
Wendy Mullenhoff
|
| 64.9 | Capitol Ideas | TEACH::LYNN | | Mon Jul 08 1991 07:36 | 27 |
| Starting Up and Shutting Down a VMS System
Chapter 13
Overall Comment - Are you going to add shutting down a cluster since the
new course design is to include cluster and network issues? You may want
to display the options that appear with shutdown.com when you are running
the cluster software.
1-7a The last sentence mentions "instead of the command shown above".
What command are you referring to at this time?
1-7 I thought LTLOAD.COM was changed recently with different files
being used.
Also at the end of the fourth bullet remove the < symbol.
You failed to show the third kind of shutdown from the CCL level.
1-16 This page needs some work. You have at the third bullet "use
SYSBOOT utility to change system parameters" but it was never
mentioned.
The emergency shutdown from CCL was never mentioned.
You also failed to cover the items under automatic restart.
Lynn White
Washington D.C.
|