Conference koolit::vms_curriculum

    	In order to keep to a timely schedule, we are requesting that all
    review comments for the Sysnet II posted chapter be entered into this
    notes file or received by us (SUPER::REGNELL for the first 6 chapters -
    SUPER::WTHOMAS for the last 10 chapters) within two weeks of being
    posted here.

    	Any comments received after the two week review date will be
    considered dependent on time and resources.

    	The first 6 chapters have been posted, the next 10 are scheduled to
    be posted by June 14.

    				Wendy

    I have the table of contents for this course.  Wanted to comment
    on it but not individual chapter pages.  Hope this place is o.k.
    to do this.
    
    	Module I is module 10 UC II.  Is UC II going away?
    
    	Module II  Page 2-14  Belongs here.  It also shows up
    in sysnet III (mod 6)
    

Hi,

I am preparing to teach SYSNET II for the first time next week and would 
like to pass along information on how it goes.  However, I'm not sure about
WHERE my comments should go since the final copy of the course changes the 
order in which the modules appear.  How about new notes with titles that 
indicate subject matter instead of module numbers?

Thanks,
Susan

    Good point... is it OK by everybody if I just change the note title on
    the existing note for each chapter?
    
    					Val

    good idea - the titles are more useful at this point!

I'll just make general comments here for now....

I've just finished day 2 of SYSNET II and quite frankly it has become an
extremely frustrating exercise in futility.  I have eight students.  

Student 1 took a variety of VMS courses back under version 4 so this is just 
a refresher for him.

Student 2 has already taken U&C I, Sys Mgr I, Network Mgr I and 
VAXcluster System Mgmt.  She was hoping to get advanced DCL this week!  
Of course we just offered both U&C II and Sys Mgr II LAST week out here!

Student 3 took U&C and received the bridge course.  He had no course 
administrator available so he was only marginally ahead of the others.

The rest do not meet the prereq's.  They either took U&C I but didn't receive
the bridge course or they took the VMS for Programmers class last week after 
being told it was a good substitute for SYSNET I (which we didn't offer last 
week) or they haven't taken ANY VMS courses.

Every one of my students had heard a different story when trying to register.
They just gave up and came to class to sort it out.  I spent the first hour
soothing feathers and trying to sort through the maze for them.  We have to 
fix this.  The new curriculum should be easy to figure out but is proving to 
be a nightmare.

I have no hope of finishing on time and doing justice to the material.
I didn't start module 1 until 3:00.  Since so many of them had never heard of
Authorize or the System Disk directory structure, I had no choice but to teach 
them something of the prereq material.  Otherwise the week would have been a 
total wash out, but now I'm going to have to skim some of the topics for this
class.  Since I get the first SYSNET III class here, I'll have to pay the 
piper a second time on this one.

I'll stop this reply here and make specific comments about the technical 
errors in different notes.

Susan

    I had about the same experience as Susan in .6 and I DID NOT 
    teach SYSNET I previously. I also made a few adjustments to the 
    order of chapters... I tried to associate Ch. 2 with Ch. 11 to help 
    differentiate between symbols and logicals (more like "old U&C I"). 
    Also Ch.1 with Ch.4 to relate Backup with Disks....
    
    I like the fact that most of the modules can be done without direct
    reference to each other (with a few exceptions...) For example,
    referring to setting up queues in a cluster, we refer to symbol
    substitution (at least I did!), but don't discuss SYMBOLS until
    chapter 11...
    
    I think we need a HOT LINE (800 #) maybe with DECtalk or something
    (possibly even a real voice recording) to explain the content of 
    each SYSNET course, the "bridge SPI courses" and how it all fits 
    together in the "grand scheme of things". That way we instructors
    won't have to waste so much time covering prerequisite topics and
    trying to smooth ruffled feathers!!

I finished teaching sysnet II last week and it was the worst week I 
have had in 5 years.  I had 19 people.  Only 5 took sysnet I. And that 
was just the week before.  Sysnet I the week before does not prepare
you for sysnetII.  Then on Wed morning I was notified by one of the students
that when she registered she was told she would get the sysnet bridge course
from me.  I checked on it and she registered late.  I asked about her
course and at that time found 10 sysnet courses for people in my class.
Almost all of them registered at least 2 weeks before the class.  How 
helpful to get sysnetI bridge half way thru sysnetII.

I think the course itself is poor. Its a jumbled up mess.  Did you possible
think the modules could be taught in order when you wrote the course?
I would say only 5 people were ready for this class and they were not the ones
in sysnet I. They were ones who had some system experience.  Otherwise
for the new user which most of these people are, its to much.  I had the
worst Q.A.'s ever this week.  We let anybody into these classes to get some
money.  The people who wrote this book didn't suffer last week, niether did
the registrars who let everybody in.  I did, and these Q.A.'s are mine, and 
they are how I'm rated, and I'm pretty ticked off.

1-6 Right off the bat here is a sysgen parameter. They do not know what
parameters are, but you have to talk about them here with Alloclass.

3-47 Here is sysmbol substitution and lexical functions which are not
until chapter 11.

3-39 Your talking about qualifiers used when setting up batch queues such
as /ws ones and /disable swapping.  No where in sysnet I or II does it even
talk about working sets or swapping.  They do not understand these qualifiers.

This brings up a point. Somewhere you have to do a small memory
management lecture.  I found it pretty hard to talk about sypagswapfiles.com
when they do not know what a pagefile was.  So how could they possible
imagine having two of them? They don't know what paging is. Memory
may not be till sysnet III, but you have to talk about it and some what
how it works to do paging.

3-15 Your comments do not match your example.  Your queue is line_printer
and the comments are sys$print.

4-11 This does not submit the procedure every other night at 11:00, but
every night at 11:00.

4-16 Whay are you using the /record qualifier on the image restore?

5-12 Lexicals. If, then. Goto, Symbol substituion all in your command
procedure yet it isnt explained until chapter 11. Next time I teach I
see chapter 11 has to be taught first. 

5-27 Take it out.

6-28 A cluster common modparams.dat?? I have never heard of that. How
would SCSNODE work?????

10-8 Monitor Page output???!!  They know nothing about memory.  This
display is way, way to much for them.  They asked about it and want to
know numbers, what they mean, what certain fields mean.  They do not need to
see this yet.

10-19 You need the full PID #

11-10 You need to pass p1 when you invoke this command procedure which
you forgot to do.

11-28 Show the entire command procedure not just part of it.  This really
confused the class.  Also you just show p2. Why didnt you use p1? I
could only assume it was in the first part of the command procedure which
you opted not to show us.  Also where was p2 defined. Show them it all.

11-32 F$cvtime() is a bit much for the first lexical they ever see.
Why not f$time() and f$extract() to show a lexical with arguments?
F$cvtime has so many arguments and two of the ones you supplied were
not even on your list of arguments.

I teach sysnet II next week and will again re-order the modules, even
a bit differently now that I know exactly what is in each.  Although
I really never want to teach this again.  Its not on my schedule again
thru June!!!!!!!!!

Wendy Mullenhoff

Wendy,

While I agree with most of your comments, this one is correct as stands:

>6-28 A cluster common modparams.dat?? I have never heard of that. How
>would SCSNODE work?????

Since V5.4, a common MODPARAMS.DAT file is possible.  I use it on all the 
VAXcluster systems that I build, manage or support...  (NI)

SYS$SYSDEVICE:[SYS0.SYSEXE]MODPARAMS.DAT contains all the parameters for the
boot server.

SYS$SYSDEVICE:[SYSn.SYSEXE]MODPARAMS.DAT (where n is a hex value beginning 
with 10 and continuing up to the last satellite) contains just the SCSNODE and
SCSSYSTEMID for each satellite.  The last statement in these files is a call
to the common file:

AGEN$INCLUDE_PARAMS SYS$COMMON:[SYSEXE]COMMON_MODPARAMS.DAT

The common file contains all the remaining parameters for the satellites.  The
beauty of this is that I now only have two MODPARAMS files to change before I
AUTOGEN the VAXcluster (instead of one for each root).

This works well for me since the satellites are identical in their hardware.  
The same mechanism would work well in a CI if you had a common environment and
similar hardware.

Take a deep breath and punt!

			Susan Swierkowski

         I hate to be the lone dissenter in this NOTES file.  But, I 
         taught SYSNET II last week and loved it.
         
         It's not perfect.  What is?
         
         I had the usual class mix.  Of 7 students:
         
         	3 had never had a class before,
         	1 had taken lots of UNIX classes (no VMS),
         	2 had old Utilities and Commands (one of these also had 
         		SYSNET I), and
         	1 had taken everything through old System Mgt. II.
         
         This mix hasn't changed since I first taught System Mgt., seven 
         years ago.  My solution for the novices is to write commands on 
         the board that I want them to type.  I remind the "experts" how 
         good reviews are.
         
         They loved the class too.  One commented that the course was 
         exactly what s/he wanted.
         
         The only complaints were:
         
         	Should have covered LAT print Queues,
         	Lunches were slightly long,
         	Some of the chairs are too low, and
         	WE WANT WINDOWS (me too!).
         
         My comments:
         
         Very good course.  
         
         John Cole was right.  It takes a very experienced instructor to 
         teach it.  They must have System Management, Network 
         Management, Clusters, Performance and Architecture knowledge.  
         Because it covers all of these subjects.
         
         The Instructor's Guide says to take all of these courses, 
         except Clusters (add it to the list, please).  It even 
         recommends Internals.
         
         I did not have time to look at the books before I opened them 
         Monday morning.  But I've taught all the classes except 
         Internals.
         
         The book has some minor typos.  Big deal, so do the VMS 
         manuals.
         
         I would add one page: a copy of the system disk layout from 
         SYSNET I, near the discussion of system logical names.
         
         The flow seems well thought-out.  Most of the subjects follow 
         very logically.  And when they don't... well to quote a 
         wonderful old (but younger than me) red headed instructor from 
         Maine "We don't get paid for what we know, but for how well we 
         dance."  And, I've been dancing since before many of my 
         students were born.
         
         By "dancing" I mean using the information that isn't on the 
         page as an excuse to launch into a freewheeling discussion of 
         whatever is missing.  That's our job.  Anybody can read the 
         book.
         
         So when a SYSBOOT parameter comes up, I explain that there are 
         hundreds of them and that we'll see how to set them later.  If 
         that doesn't satisfy someone, I dance off into 
         
         	MC SYSMAN PARAMETER SHOW /ALL
         
         for a while.  Then I explain that we'll see a real explanation 
         later and we're back on course.  The big holes are places to
         advertise for the other courses.
         
         I display overheads of many of the pages that I am talking 
         from.  That way when a typo crops up, I just say "Well Fred had 
         an off day on that page."  Then I correct it before their very 
         eyes.  That way they can correct the book.  Of course, some 
         will try to prove that Fred was right!
         
         ENOUGH.
         
         The way I look at it is:  I was asked a year ago to be a 
         reviewer.  I think that everyone in this conference was.  I 
         decided that UNIX needed more of my time.  Therefore I don't 
         have the right to complain about anything but typos.  That 
         won't stop me of course.
         
         Yours,
         
         Chuck

    Thanks for everyone's comments so far. It may seem kind of quiet on our
    end since we're working on other projects at the moment, but some of us
    are still reading. 
    
    There is a budget for updating these courses in FY93, by which time
    we should have a sense of how to make them work better in the
    classroom. 
    
    I'm forwarding notes on US Area registration to Roger Towne, and you
    should make your experience known through your management chain too
    (I'm sure you are...)
    
    					Val

The following erros were found in SYSNETII when I did my first teach the 
week of January 27th.

Chapter 3 
	Page 3-47 the INIT command lines are missing the closing
		apostrophe after the symbol

Chapter 4
	Page 4-11 the BACKUP command line has just  dra0: yet
		in the instructor's notes on page 4-9a you stated
		"when you do incremental backups it is necessary to
		explicitly use the notation  [*...] 
		Please you the notation for page 4-11.


Chapter 5
	Page 5-23    files name

Chapter 6
	Page 6-20 the dash in ADD_GBLSECTIONS should be an underscore

Chapter 8
	Page 8-7 The 5th bullet should have the file name SYSUAF.LIS
		not SYSUAF.DAT

	Page 27-a mentions the identifier CHEMISTRY - please explain
		just what you are talking about.

	Page 8-39 the second sentence is not complete.  Please add to
		the end  "to a value of one."

Chapter 11
	Page 11-28 the command should look like  /COPIES='NCOPY' 'P2'

Chapter 13
	Page 13-74 the GET UIC is just a comment so please precede it
		with the !


Lynn White
Washington, D.C.

Here are some more mistakes in sysnetII.

2-12 When running authorize there is no qualifier /default=.
You need /device=.

2-15 This is'nt a mistake its just very unclear.  You should mention
that it is the user APON who is isssuing these commands. Unless they
figure that out the example makes no sense.

3-18 You are showing commands inside a queue startup file. You
did not start the queue LPC0.  In smI where you got this, they did not
start the queue because that course taught logical queues (which do not
get started).  Since this course does not cover logical queues you 
should either take lpc0 out all together or start it.

8-7 I think you meant -Do not permit WORLD acccess to sysuaf.lis.
You said sysuaf.dat.  WOrld does not have access to that.

10-13 this is a typo. you have $@sys$monitor:submon.com). The )
is the typo.

10-26 You are talking about creating a show cluster initialization
file.   You do a bunch of show cluster commands and then do a
Write cluster2_out.  Write creates a listing file you can print.
You needed only to say SAVE. That creates show_cluster.com by default.
Also the students wonder where did you get the id # from when
you removed two nodes from the display.  You really should show
the command that gave you these numbers.  Also this would have 
been much better if you stuck with the node names in the circus
cluster that we have been looking at all week.

11-10 in you example of report3.com the first thing we get is-->

Day to print a report for:

Yet in the command procedure there is no INQUIRE command. you
need to fix the command procedure to $inquire p1 "day to print..."

13-48 (LABS) 6. solution says $account/type=batch/summary=hour

It should be $account/process=batch/summary=hour

Wendy Mullenhoff

    ok folks -- after teaching Sysnet II twice (and succeeding to my
    surprise if the measurement was SOFs, though that is another rathole
    ;-), I gave rearranging the command procedure module (teach it prior
    to the Network & Monitor modules) a shot.  
    
    While someone once wisely told me to "beware the 3rd teach", 
    I blindly toyed with fate and experimented. 
    
    Maybe it was just my turn, 3rd teach or POSSIBLY the flow and lack of
    background so that they really weren't ready for command procedures and
    experienced frustration, but this was not a "100%" run (ok - so 93% is
    fine on paper, but read on...)  
    
    
    The story really hits the fan when your customer
    looks you in the eye, says they understand your obligation to cover the
    material in the book, acknowledge that you met the paper objectives
    printed right there in the student guide, but DID NOT PREPARE HIM FOR
    SYSTEM MANAGEMENT TASKS HIS MANAGER EXPECTS AFTER 2 WEEKS OF CLASSES
    CALLED "SYSTEM & NETWORK MANAGEMENT n".  The customer basically
    declared what almost any of us here have stated in different ways - the new
    curriculum is like the emporor.  . .. 
    
    Yes, you can discuss the concept of a 3 week curriculum (tho Sysnet II
    and III are not meant to be taken back to back), you can try all the
    approaches short of lying, but he was right, and I think he called our
    bluff for what it is.  
    
    I was frankly embarassed.
    

>    ...DID NOT PREPARE HIM FOR
>    SYSTEM MANAGEMENT TASKS HIS MANAGER EXPECTS AFTER 2 WEEKS OF CLASSES
>    CALLED "SYSTEM & NETWORK MANAGEMENT n". 
   
   Given the benefit of hindsight at this point, is there a list of those
   tasks that his manager expected him to learn? Are we going to get the
   same list if we ask any two different managers?
   
   					Val
   

  Good question Val, but I think the real issue is that SysNetI implies in
  name that it is a Management course, not a user course with a few manager
  topics sprinkled in it.  After 2 weeks they basically have 1 weeks worth
  of System Management skill.  Following SysNet3 they should have a better
  grasp on management, but that's note really the point.  
  
  The names imply a lot and the course description in the Digest (see the
  March-August issue on page 20) has a REALLY spiffy write-up that does NOT
  accurately reflect that information covered.  Under SysNet2 they list:
  
    "Go beyond the basics and return equipped to manage the day-to-day 
     operations of VMS systems in VAXcluster and networked environments."
  
     HA, HA!!  Do we cover NETCONFIG or STARTNET in detail?  How about 
     CLUSTER_CONFIG?
  
    "Course topics target the tasks system managers perform on a daily
     basis...as well as monitoring network activity."
  
     Poo!  The average system manager need NETCONFIG more than a few TELL
     commands.
  
    "Advanced topics include how to use the utilities and tools for system
     monitoring." 
  
     A very misleading statement.  This info is not covered to a  reasonable 
     level until SysNet3.
     
    "Once back on the job, you'll prove the value of your training through
     improved overall system functionality [what does that mean?] and
     increased user satisfaction."
  
     GAG!!  I can't believe we actually approved this line for inclusion in
     a course description!!  This is ALL sales hype and only adds to the
     confusion.
  
   When we quite trying to "sell" the course with words and instead begin
   selling the course on it technical merits, we'll be much more successful
   in the delivery even if it means a slightly smaller (but more appropriate) 
   audience.
  
  $

>    ...DID NOT PREPARE HIM FOR
>    SYSTEM MANAGEMENT TASKS HIS MANAGER EXPECTS AFTER 2 WEEKS OF CLASSES
>    CALLED "SYSTEM & NETWORK MANAGEMENT n". 
   
>   Given the benefit of hindsight at this point, is there a list of those
>   tasks that his manager expected him to learn? Are we going to get the
>   same list if we ask any two different managers?
   
Heavy sigh....

I know that this rathole is deadly, but we have to come up with something
better (assuming we want to stay in business).  We are getting entirely too
many comments like the one Irene had to deal with.  The customers are passing
us on paper, but verbally they are not happy.  Let's face it: with the 
unlimited program, we see many faces over and over; they know what the SOFs 
are for and how to fill them out if they like us personally.  They *tell* us
something entirely different!!!!  The bottom line is they don't like the
cookbook approach; they feel lied to and cheated and they will not recommend
the courses to others.  So do we win when the SOF passes?  Only temporarily.

On occasion, I have had a student complain that it takes too long to learn VMS, 
too many weeks of training, too many weeks away from the office.  The rest of 
the class always jumps in to explain that it takes time to learn a complex
operating system.  You don't sign up for calculus without taking algebra, etc.
first!!!!  The fix may very well necessitate a modified return to the old 
curriculum.  Teach the same topics but interleaf network and VAXcluster stuff 
where appropriate.  Keep the specialty courses.  Like Irene said, the emperor
ain't got no clothes.


				Susan

PS.  We could still keep the mastery series but change the name to Operator I, 
II and III.

     
    Back in Nov 89 I attended an Instructor Product Forum in Bedford.  At
    that time this "New Curriculum" was in the planning stages.  If my
    memory serves me correctly, Andy Sadler described a survey that had been
    done on a significant number of customers.  The plan was for a
    "Generalist" and a "Specialist" curriculum.
      
    As I read the digest for the new courses, I do not find any meaningful
    discussion on the specialist vs generalist theme.
      
    The digest needs imediate action.  The courses need accurate names, and
    descriptions that reflect their content.  
      
    My current approach is to call my students, before the class starts,
    and ask questions such as, "In the VMS for Programmers class do you
    anticipate that you will actually be programming?"  The digest states,
    "Plenty of time for programming...", so I am not surprized that some
    students believe that it is a programming class.
     
    Just this week I got a call from a training coordinator, who heard of
    my call to one of their employees, and inquired about the course. She
    was very pleased when I directed her student to Utilizing ...
      
    Arnold Tarling, DLO10::TARLING
    

   Right, the survey is still in SUPER::ES$PUBLIC:SYSMGT_JOB_ANALYSIS.PS
   for anyone who wants to see it. We used it as one of our inputs, but not
   the only one. (This is not to be defensive about our work, but just to
   let you know the survey was not done in vain.)
   
   That's a good point about specialists vs. generalists. Unfortunately it
   wasn't possible to address that in the new curriculum announcement,
   since we hadn't set our schedules for updating the specialist courses
   (VAXcluster, performance, network) in time to meet the Digest
   publication deadline.  The VAXcluster course is our next priority.
   
   					Val

Val,

Does your comment about the specialty courses mean that:

1. VAXcluster Mgr is not slated to terminate?

2. The death date of June 30 for Network Mgr I is not real?

According to memos I've received, Net Mgr I is going away and there's been no
firm word on the fate of VAXcluster.  Is it still possible that some of the old
curriculum will be revived?


				Susan

    Re: marketing language chosen in the Digests...
    
    This problem has been around for years; and, it's worsening.  The best
    curriculum in the world would be subverted by inaccurate depictions in
    the literature.  My understanding of the process is that the writeup
    submitted by the developer is 'jazzed up' by some nontechnical
    marketing person and shipped, with no review for technical accuracy by
    the original developer!  If this perception is correct, then call me
    wacky, but this thing sounds fractured and badly in need of fixing.  It's
    difficult enough to design and deliver these curricula and individual 
    courses without being bushwacked by the advertising.  Can anyone tell
    me what, if anything, can be done to remedy this?  I really don't
    believe that any instructor or developer has the ability to fix this;
    so, this is a general question thrown out to anybody further up the
    food chain who knows/cares.
    
    Mark Thorne
    Chicago Training Center

    If you've found typos, spellos, inconsistencies, etc. in the final
    materials for Sys/Net II, please post them as replies to this note by
    Monday, June 1. If you've already posted comments, you can post a
    pointer to your previous note(s).
    
    A small favor we ask of you, please:  make your comments as specific as
    possible (for example, instead of telling us "this qualifier is
    misspelled," tell us "this qualifier should be IO instead of I/O.") To
    make this project feasible we are having our production editors do the
    bulk of the work, so your comments need to be intelligible to a
    nontechnical person.
    
    If you are pointing out something that needs additional research by a
    course developer, you can flag it as such and the editor will pass it
    along to one of us.	
    
    Thanks very much!
    
    					Val
    

    Val,
    
    	I taught system and network management for the second time last
    week and the customers found errors that I hadn't caught yet.  One
    general comment - the people who had system management experience with
    other operating system were generally happier than those new to system
    management.  For those who are new, the topics seemed disconnected
    because they don't know the bigger picture yet.  A comment in the
    instructor guide to perhaps start out with the System Manager's Manual,
    chapter 1, page 1 gives an overview and list of tasks that are included
    in system management.  I used this on Friday for review.  I asked for
    topics and tools covered that helped managers perform the tasks.  The
    feedback I received was that I should have done an overview on Monday.
    
    Student guide:
    p 1-17 example omits the oper privilege on second line
    	$ SET PROC/PRIV=(SYSPRV,OPER)
    
    P 1-18 people wanted to know about shadow sets and stripe sets.  A
    brief mention in the student guide with an example show DCL commands in
    the insstructor guide would be nice.
    
    p 1-23 Table 1-2 mentions that the OPER privilege is needed to run
    sysman.  I think the note needs to also point out that write access to
    the master file is needed to create QUOTA.SYS so they may also need
    SYSPRV privilege. 
    
    p 2-19 in the example the process is assigned the privilege SYSPRV -
    OPER is also needed
    
    ! I have the Labs assignments at the end of the chapter
    
    p13-15 In number 3 the directions say to create a logical name with the
    attributes CONCEALED and TERMINAL. I number 4 they are directed to use
    sysman to create the same logical name cluster wide.  I would think
    that means to give the logical the same attributes also. Therefore, I
    think the sysman command needs to include the word after concealed TERMINAL
    
    Chapter 3 - People in my class had version 4.7 to 5.4 of VMS so some
    explanation of what changes occurred in V5.5 is necessary.  I'd like to
    have an example in the instructor guide on SERVER queues.  I am lucky
    we use DQS (distributed queuing system) but I know many training
    centers do not have server queues.
    
    p 3-25 note that a burst page implies a flag page so both are not
    needed in example 3-6 /separate=(burst,trailer) gives the same results
    as the example
    
    
    p 3-26 I think the order is incorrect.  I think it is:
    	Job burst page (/separate=burst)
    	Job flag page  (/separate=flag)
    	file burst page (/default=burst)
    	file flag page (/default=flag)
    	file contents
    	file trailer page (/default=trailer)
    	repeate previous 4 steps
    	job trailer page (/separate=trailer)
    
    p 12-4 Please add comment that answer is for VMS V5.5
    
    p 13-17, 13-26, 13-27 Print queue labs must be modified since many
    locations do not have LP devices.  Perhaps alternate labs or a note
    in the lab to look first ($ SHOW DEVICE LP) and ask the instructor if
    there are devices that can be used.
    
    p 4-9 the last paragraph, last sentence, before example 4-2, seems to
    imply that backup would over write data if the label were not checked. 
    Without the /REWIND qualifier, backup will append to the end.
    
    p 4-10 nothing is wrong, I just strongly disagree with showing examples
    that give a process all privileges!  One of the things I stress is that
    good managers need to know what privileges do what so they don't set up
    their users with privileges they don't need.  System managers are
    usually responsible for implementing security policy and understanding
    privileges is very important to security.  I'd like to see the example
    changed to also show how to use the lexical functions to capture the
    current privileges and restore them.
    	$ PRIV=F$SETPRV("OPER,READALL")
    	.
    	.
    	.
    	$ NORMAL=F$SETPRV(PRIV)
    
    I also think the example could benefit from using /ignore=interlock
    since you can't be sure all the files are closed.
    
    P 4-11 the backup command is incomplete.  I think it should be:
    	$ BACKUP/RECORD/SINCE=BACKUP DRA0:[*...],DRA1:[*...],DRA2:[*...]
    The examples on 4-9 are correct.  Also note that using [*...] assumes
    there are no new files in the master file except directories. using
    [000000...] is an alternative.
    
    p 5-13 The example 5-4 is to show how to install additional paging and
    swapping files.  They also need to know how to create them.  One or two
    lines commenting that the files are created first using the sysgen
    commands:  SYSGEN> CREATE $1$DUA4:[SYSEXE]PAGEFILE.SYS/SIZE=20000
    	       SYSGEN> CREATE $1$DUA4:[SYSEXE]SWAPFILE.SYS/SIZE=20000
    
    p 5-15 why were the examples of the command procedures executed from
    the startup procedure eliminated?
    
    p 5-18 example 5-7 if you turn off recognition on Ctrl/Y with the
    command: $ SET NOCONTROL=Y  you cannot successfully test for Ctrl/Y
    with the command: $ ON CONTROL_Y THEN LOGOUT ! note the underscore the
    example shows a hyphen.
                                
    p 6-17 BYTLM is misspelled.
    	   Before talking about changing user's quotas and limits, they
    need to know how to read an installation guide.  I show them how to
    look for the resources needed to do the installation and point out that
    every installation guide will mention what resources the installer
    needs as well as the user.  
    	A comment that the installer needs to read the installation guide
    listing the requirement they need to look for would help.  Give them a check
    list.  I suggest: Disk space, Memory, Installer's quotas & privileges,
    Logical names, Dependancies.
    
    p 6-20 change hyphens to underscores in the sysgen parameters
    
    In chapter 7 or 8, I think the audit utility needs to be mentioned.  I
    prefer to add it to chapter 7 because 8 is so long but then auditing
    was introduced as a security enhancement.
    
    
    p 13-48 change answer to 6. $accounting /process=batch /summary=hour
    
    p 8-12 Table 8-3 step 2 can't work for environments that use terminal
    servers. Perhaps a reference to the sysgen paramater TTY_DEFCHAR2 as
    was done in Table 8-5.  
    
    p 8-16 secure server and disconnect characteristics can also be
    assigned by TTY_DEFCHAR2 for pseudo terminals.
    
    p 8-22 Perhaps a note in the instructor's guide that to delete
    intrusion records when the source is a lat terminal requires quotes and
    the use of uppercase.  $ DEL/INTRU "SRV7A/PORT_3:JONES"
    
    P 8-25 I disagree with assigning more that one user the same UIC. I
    cannot think a valid example even if the manager thinks they don't need
    to protect anything.  I'd rather point out that it is not recommended
    and point out the difficulties of maintaining such a situation.
    
    p 8-27 needs an example of creating an ACL, at least an identifier
    example and a comment that there are other types.
    
    Chapter 9 I think it should be pointed out that the network needs to be
    licensed and the executor address, name and type need to be defined
    before starting a DECnet node even if it is covered in SYSNET III.  I find 
    it difficult to talk about the network without showing them a few DCL
    commands that access the network without using set host and explaning
    that there has to be a network process on the target node to complete
    my request.  They want to know why network access sometimes fails.  I
    don't go into details.
    
    p 13-64 in the answer for 2. the list command will display "Node
    Permanent Summary" not Volatile
    
    p13-68 the answer to 2 should refer to REMOTE.DAT not LOCAL.DAT. The
    answer is the same as 1. (cut and paste I suppose.)
    
    Chapter 10 now that many people are starting with SYSNET I, fewer and
    fewer people in SYSNET II have the concepts and terminology to
    understand what to look for when monitoring.  Perhaps a note in the
    instructor's guide that a presentation of the concepts of paging,
    pagefaulting, a working set, page table, free and modified lists, I/O
    requests and swapping may be needed.
    
    p 10-27 you can press any key to get the command> prompt in show
    cluster/cont
    
    Chapter 11 Many agree that this needs to come earlier since modifing
    command procedures is discussed in so many chapters before this.
    
    p 11-7 last line would be clearer if character string were followed by
    (ie. quoted string).  Same for p 11-9. 
    
    p 11-9 Table 11-1 some of the examples are incomplete and must be
    preceeded by other commands.  The example for the symbol is complete. 
    The symbols count and name need to be equated to something before they
    can be used in the second example such as $ COUNT=0 and $ NAME =
    "DATA".  Same is true for the forced substitution examples.
    
    p 11-10 The example at the bottom needs to pass the parameter TUESDAY; 
    It is omitted.
    
    Alas alak - a course developer's work is not easy!  Thanks for
    listening.
    
    Andrea

I found that in SYSNETII the student guide does not answer my students
questions about the Show Cluster Utility. For that reason I have written
a supplement that can be taught interactively.  Enjoy!!!



		SHOW  CLUSTER  UTILITY



	Show Cluster covers approximately 100 fields of data organized in
	terms of fields, classes and windows.


	The Windows are:
		SCS - SCS database
		CLUSTER - connection manager database
		LOCAL_PORTS - port database

	The Classes are:
		CLUSTER
		SYSTEMS
		MEMBERS
		CIRCUITS
		CONNECTIONS
		COUNTERS
		CREDITS
		LOCAL_PORT
		ERROR

	The Fields vary for each class.
	For examples the CLUSTER class has the following fields:
		CL_EXPECTED_VOTES
		CL_MEMBERS
		CL_QDVOTES
		CL_QUORUM
		CL_VOTES
		FORMED
		LAST_TRANSITION
		MEMSEQ	
		QD_NAME
		QF_VOTE

	This SHOW CLUSTER UTILITY has the following basic commands:
		ADD
		REMOVE
		SET
		INIT
		HELP
		EXIT
		SAVE
		WRITE
		@file-spec

	See page 10-27 in your SYSNETII student book.




		SHOW CLUSTER   -   Page 2




	Lets issue the following commands together.

	 1.	$SHOW CLUSTER/CONTINUOUS

	 2.	ADD DIR_WT	(This adds one field.)

	 3.  	REMOVE MEMBER	(This removes the entire class.)

	 4.  	ADD VOTES,EXPECTED_VOTES	(This adds two fields.)

	 5. 	ADD CIRCUITS	(This adds one class. Each class will have
				 its own default fields.)

	 6.	REMOVE RPORT	(This removes a field.)

	 7.	REMOVE CIRCUIT	(This removes a class.)
		
	 8. 	ADD TRANSITION_TIME	(This adds a field.)

	 9.	SET VOTES/WIDTH=2	(This will adjust the width of
						 the column.)

	10.	SAVE LYNN.SCD		(This will write back to disk the format
					 of the display.)

	11.	INIT			(This will return you to the default
					 display without doing ADD or REMOVE.)

	12.  	WRITE LYNN.DISPLAY	(This takes a snapshot of the terminal
					display and writes it back to disk.)

	13.	CONTROL-Z  or EXIT

	14.	$TYPE LYNN.DISPLAY/PAGE	(Here is the information that was on
					 our screen earlier.)

	15.	$SHOW CLUSTER/CONTINUOUS

	16.	@LYNN.SCD		(This file will re-create our display
					 without us having to use ADD commands.)





Lynn White
Washington,D.C.

SYSNET II - EY-G987E-SG-0001

I'd like to thank all the instructors who have entered corrections - they have
been a big help in preparing for this course. 

Some items that I don't think have yet been reported:

pg 3-14 or 3-15 - Show initializing an execution queue for a printer on a
	terminal server (using /PROCESSOR=LATSYM)

pg 3-15 - in the terminal queue column:
		$ INITIALIZE/QUEUE/TERMINAL...
	should be
		$ INITIALIZE/QUEUE/DEVICE=TERMINAL...
	or just
		$ INITIALIZE/QUEUE...
	since the symbiont figures out the type automatically

pg 5-11, 2nd sentence:
		... files you would set up ...
	should be
		... files you could set up ...
	(since they are optional)

pg 5-15 - As of v5.5, the line
		$ @SYS$MANAGER:LTLOAD.COM
	should be changed to
		$ @SYS$STARTUP:LAT$STARTUP.COM

pg 7-11, Example 7-3:
		_$ /SUMMARY=USER /REPORT=PROCESSOR
	should be
		_$ /SUMMARY=(HOUR,USER) /REPORT=PROCESSOR
	(to get the output as shown)

pg 7-14, 2nd last line:
		... BATCH, INTERACTIVE, DETACHED, and others
	Since there are only two others (NETWORK and SUBPROCESS), why
	not just list them?  Change to
		... BATCH, INTERACTIVE, DETACHED, NETWORK and SUBPROCESS

pg 8-14, 2nd line:
		on former system-generated ...
	should be
		on for system-generated ...

pg 8-14, 4th bullet:
		... a list of 100 passwords ...
	should be
		... a list of 60 passwords ...
	(according to VMS v5.5 New Features Manual, page B-64)

pg 8-17, Table 8-6:
	The last sentence in the comment for LGI_BRK_TERM concerning LAT has 
	not been valid since, I believe, v5.2, and so should be removed.

pg 8-17, Table 8-6:
	One LGI parameter, LGI_PWD_TMO, is missing from the table and should 
	be added.

pg 9-8, Table 9-2:
	In the Reason column for SHOW, add
		BYPASS privilege is needed to display password information.

pg 11-45, Example 11-14, A.COM:
		$ C = P1 + P2
	should be		
		$ C == P1 + P2
	to match notes 5 and 8.

pg 11-77, Example:
		$ FULL_FILE_SPEC = F$PARSE("TEST.COM",,,version,"NO_CONCEAL")
	should be
		$ FULL_FILE_SPEC = F$PARSE("TEST.COM",,,"VERSION","NO_CONCEAL")
	but this still would not produce the output shown - it would give only
		  FULL_FILE_SPEC = ";"
	Perhaps a better example would be to replace the last four lines with:
		$ DIR_SPEC = F$PARSE("TEST.COM",,,"DIRECTORY","NO_CONCEAL")
		$ SHOW SYMBOL DIR_SPEC
		  DIR_SPEC = "[SMITH]"
		$
		
pg 13-25 and pg 13-26, #1 and #2:
	They can't all use the same queue names.  Tell them to use something 
	like username_PRINT in #1, and username_printername in #2.

pg 13-26, #2:
	Also show what a solution looks like for a printer on a terminal server:
	$ INITIALIZE/QUEUE/SEPARATE=FLAG/PROCESSOR=LATSYM/ON=LTA10: SMITH_LTA10

	My first and what I feel my most important concern for SYSNETII
is with Chapter 11.  Please move it to the beginning of the course and
make the appendix a part of the chapter. Take something out so there is
time to cover this important material. In SYSNETIII a prerequisite is
the advanced skills of writing command procedures.

Page 1-6	Students see the words "allocation class" and immediately
		ask what is this?

1-7		Change the order of page 1-7 and 1-8/  The way it is
	organized you jump back and forth on one topic.

1-17	Up to this point the customers have never seen SYSMAN. Do
	a good job and completely cover it here and now.

2-5	Are we going to show the customers how to make their own logical
	name tables like we did in UC2? This chapter needs some new material.
	Too much is a review from SYSNETI.

2-18	For the first series of commands add two more commands after
	the SHOW DEVICE and before DEASSIGN. 

	The second series of commands add $SHOW TIME and the result to
	verify that the output returns to the terminal.

Chapter 3	What about the AUTOSTART that is new with version 5.5
		What about how to set up server queues???

3-21	As of version 5.5 there is a new queue state  "IDLE"  if
	the queue is empty.

3-40	Please add   "queue_name"  to the first two commands.

5-18	The example 5-7 is very confusing. Why SET NOCONTROL=Y
	when we set up a cative account?
	This implies to the customer that maybe the captive doesn't
	really work all of the time.

5-23	Fix the output file names. (TWICE)  AGEN$FEEDBACK.REPORT


5-25	This is fine if back on 1-17 you truly/fully introduce SYSMAN.

6-15	I thought you updated for Version 5.5.  This menu now has
	options 1 through 12 and 99.

8-7	Fifth bullet - Should be SYSUAF.LIS (This is the correct file
	name.)

8-15	This is for hardwired terminals. Are we ever going to tell the 
	customer how to set up passwords on the server?

8-28	Make the account and the group identifier the same to avoid
	a major discussion.

9-16	Since the NCP command SET EXECUTOR is used for multiple commands
	add more command after the third bullet.

10-12	Move page 10-33 up here.  They go together.

10-25	Bad example/section. Maybe you can use this interactive handout
	I created to improve this section.

***********

I found that in SYSNETII the student guide does not answer my students
questions about the Show Cluster Utility. For that reason I have written
a supplement that can be taught interactively.  Enjoy!!!



		SHOW  CLUSTER  UTILITY



	Show Cluster covers approximately 100 fields of data organized in
	terms of fields, classes and windows.


	The Windows are:
		SCS - SCS database
		CLUSTER - connection manager database
		LOCAL_PORTS - port database

	The Classes are:
		CLUSTER
		SYSTEMS
		MEMBERS
		CIRCUITS
		CONNECTIONS
		COUNTERS
		CREDITS
		LOCAL_PORT
		ERROR

	The Fields vary for each class.
	For examples the CLUSTER class has the following fields:
		CL_EXPECTED_VOTES
		CL_MEMBERS
		CL_QDVOTES
		CL_QUORUM
		CL_VOTES
		FORMED
		LAST_TRANSITION
		MEMSEQ	
		QD_NAME
		QF_VOTE

	This SHOW CLUSTER UTILITY has the following basic commands:
		ADD
		REMOVE
		SET
		INIT
		HELP
		EXIT
		SAVE
		WRITE
		@file-spec

	See page 10-27 in your SYSNETII student book.

	Lets issue the following commands together.

	 1.	$SHOW CLUSTER/CONTINUOUS

	 2.	ADD DIR_WT	(This adds one field.)

	 3.  	REMOVE MEMBER	(This removes the entire class.)

	 4.  	ADD VOTES,EXPECTED_VOTES	(This adds two fields.)

	 5. 	ADD CIRCUITS	(This adds one class. Each class will have
				 its own default fields.)

	 6.	REMOVE RPORT	(This removes a field.)

	 7.	REMOVE CIRCUIT	(This removes a class.)
		
	 8. 	ADD TRANSITION_TIME	(This adds a field.)

	 9.	SET VOTES/WIDTH=2	(This will adjust the width of
						 the column.)

	10.	SAVE LYNN.SCD		(This will write back to disk the format
					 of the display.)

	11.	INIT			(This will return you to the default
					 display without doing ADD or REMOVE.)

	12.  	WRITE LYNN.DISPLAY	(This takes a snapshot of the terminal
					display and writes it back to disk.)

	13.	CONTROL-Z  or EXIT

	14.	$TYPE LYNN.DISPLAY/PAGE	(Here is the information that was on
					 our screen earlier.)

	15.	$SHOW CLUSTER/CONTINUOUS

	16.	@LYNN.SCD		(This file will re-create our display
					 without us having to use ADD commands.)

*********

10-26	Redo the initialization example to an easier one.  They may not
	know what in the world SYSTEM/ID is referring to at this time.

11-10	Bad example.  You invoke this file without any parameters yet it
	had P1 without even testing to see if P1 exists or not.

11-28	This syntax works but doesn't match the general formats from the
	previous page.

11-32	Why not introduce an easier lexical than CVTIME?  This may be
	a first lexical for some students.

********

The following erros were found in SYSNETII when I did my first teach the 
week of January 27th.

Chapter 3 
	Page 3-47 the INIT command lines are missing the closing
		apostrophe after the symbol

Chapter 4
	Page 4-11 the BACKUP command line has just  dra0: yet
		in the instructor's notes on page 4-9a you stated
		"when you do incremental backups it is necessary to
		explicitly use the notation  [*...] 
		Please you the notation for page 4-11.


Chapter 5
	Page 5-23    files name

Chapter 6
	Page 6-20 the dash in ADD_GBLSECTIONS should be an underscore

Chapter 8
	Page 8-7 The 5th bullet should have the file name SYSUAF.LIS
		not SYSUAF.DAT

	Page 27-a mentions the identifier CHEMISTRY - please explain
		just what you are talking about.

	Page 8-39 the second sentence is not complete.  Please add to
		the end  "to a value of one."

Chapter 11
	Page 11-28 the command should look like  /COPIES='NCOPY' 'P2'

Chapter 13
	Page 13-74 the GET UIC is just a comment so please precede it
		with the !

***********

Lynn White
Washington, D.C.

                  This reply is for sysnet II.

Organization:  I do not know anyone who teaches this course
		in the order of the book.

On instructor does  11, 1, 2, 3, 5, 8, 7, 9, 10, 4, 6.
another does        2, 11, 10, 1, 3, 4, 5, 8, 9, 6, 7.

I do the later.
	Monday: 2 & 11.
	Tuesday: 10, 1, 3.
	Wednesday: 3(continued), 4, 5.
	Thursday: 8, 9.
	Friday: 6, 7.

I put this here to show the pace and why I am  not following the
normal module flow below.

2 before 11 because logical names should precede command procedures.
11 second rather than last because it is important and the appendix
that should be taught is pointed out for a reading assignment and
any questions can be handled in lab.  (The appendix info should be 
taught in some course).

Page 2-12  Remove example 2-5.  We are not here to show how to
	use Authorize in this module.  We already showed this in
	sysnet I. We have shown a logical and equal a read device
	name: we do not have to list all occurrences.

		If you keep this, "/default=" is incorrect. It should
	"/device=".  You may also add "/directory=[rounds]

Page 2-16, 2-17 & 2-18 were already covered sufficiently in sysnet I.

Page 2-19 at bottom add another bullet or continue the last sentence

	...and also use the appropriate qualifiers for the table you
want the name to go into and the mode you want.  (/system/exec)

I would combine the info on page 2-5 and page 2-20 by having 
page 2-5 read this way(It will stretch to the next page).

                        ***

LOGICAL NAME TABLES

The system stores logical names and their equivalence strings in four
default logical name tables and possibly additional user-defined tables:

o Process logical name table
  - used only by your process
  - created when you log in
  - goes away when you log out
  - no special privilege needed
  - use "/PROCESS" to refer to this table.(this is the default on most commands)

o Job logical name table
  - Shared by your process and its subprocesses.
  - created when you log in
  - goes away when your main process logs out
  - no special privilege needed
  - use "/JOB" to refer to this table

o Group logical names table
  - Shared by all processes in a UIC group
  - created when the first user in a particular UIC group logs in
  - goes away when the system goes down
  - GRPNAM privilege is needed to add logical names to this table
  - use "/GROUP" to refer to this table

o System logical name table
  - Shared by all processes on the system
  - created when the system comes up
  - goes away when the system goes down
  - SYSNAM privilege is needed to add logical names to this table
  - use "/SYSTEM" to refer to this table

o Many other logical name tables can be created for system use or
	private use.
  - Used for special applications
  - For example, the table DECW$LOGICAL_NAMES holds logical names used
    by DECwindows software
  - use "/TABLE=table_name" to refer to these tables
			***



Page 2-19  I would change to top of this page to read:

                        ***
	DEFINING LOGICAL NAMES CLUSTERWIDE ON A RUNNING SYSTEM

	You can define a name on each node of the cluster or you
	can use the SYSMAN UTILITY to do it on all nodes at once.
			*** 

The title "defining names in the system table" is not real meaningful
here do to the fact we are doing this cluster wide and we are using
SYSMAN to do it and with SYSMAN we can put them on any node and in
any table.  Granted we would normally only use it to put names in the
system table, but we could be creating a special system wide table.

Chapter 11

	This chapter should be made into 2.  The first up to the
summary, the second the appendix.  The second can be the next module
here or a module in sysnet III or IV. Or better yet, put module 11
in sysnet I and make the appendix a module in sysnet II.

Biggest problem in this chapter is the report command procedures.
There is no report1.com to show what we are trying to do.  We need
it to build on with the others.  Report2.com is fine. It shows using
the P1 parameter.  I cannot figure out what report3.com is showing
us that report2.com did not.  How about we go to Utilities and 
commands course and pick up the report command procedures from there
and use them here.  They were tried and true.  (I think there was a 
report4.com also.  One thing they had and we should talk about is
the inquire command.  At the bottom of page 11-10 "@report3" supplied
no P1.  How do we know it is Tuesday?  Well how about in the command
procedure we put the following command after the first note:

    If P1 .eq. "" then inquire P1 "please type in the day for the report"

Also on page 11-10 the line after $ @reports should be removed.  The 
next line says almost the same thing and is the correct one.

Page 11-16

	Bullet 3 = only 1 space between  "name:" and "Fred"


	Bullet 6 = no space between  "name" and "Fred"

Page 11-32  Can we move this page to later.  I would like to start
	My discussion of lexicals with a few simple ones like f$mode()
and f$time(), followed by f$length(), f$locate(), and f$extract.  The
last 3 give a user great control of a "string" and can be manipulated
together to show the use and value of lexicals.  Then f$time and 
F$getsyi.

Page 11-43  ?? "FLOW OF CONTROL" ??  How about "HOW TO USE SUBROUTINES"

Pages 11-53 to 11-55 has been taught in mod 9 of sysnet I.  You have
to teach it there or there is no reason for local AND global tables.

Page 10-4  Monitor and show cluster is covered here and in sysnet III.
	It only needs to be done once.  They are in sysnet III twice
right now because they are in a module of their own and in the performance 
module.  I would keep the discussion here and drop them from sysnet III
all together.

Page 10-26 Example 10-18 should match the setup in example 10-17.
	I do not think it does.

Module 10 good chapter.  Just do not do it again in sysnet III.

page 1-5 already done in sysnet I.  At least we can now show the students
	the system manager manual page sgn-3/4 where most of the devices
	are listed.

Page 1-19  bullet 6   I feel uncomfortable with the logical name dev1
	here.  If dev1 is still in his PROCESS table this should work.
	I do not have any way of proving that it is.  To avoid getting
	into that kind of discussion could we substitute one of the 
	logicals the system put in the system table. 

Page 1-22  We should add here that the default diskquota account is
	[0,0].  We should set up [0,0] to be what we want it to be,
	if we are going to add a lot of users or do a rebuild.

Page 1-27  In all diskquota commands you MUST use "/device=" qualifier
	or the command will reference the disk you are on.

Page 3-5 to 3-8 is or should be in sysnet I.  

Page 3-9  I do not think we need to talk about the copy and write
	commands here.  It is probably never done this way.  The first
	set of bullets makes it look like you can allocate a printer
	that is assigned to a print queue.  More importantly the students
	do not care.

Page 3-10 We need a process called Queue_manager in this display.
	It is version 5.5.

Page 3-15  Add /queue=line_printer to the print command at the 
	bottom of each column.

	Take out the last paragraph starting with "Since".
	It has no meaning now that you have changed the queues
	from being SYS$PRINT.

Page 3-22  This is where I stop on Tuesday.

    
Page 3-26  Pages order is wrong see note 73.23 for correct order.
        
Page 3-47  Add "$" for each line that does not start with one.  Don't put "!"
	 as the first thing on a line.

more to come. Chuck
    

  Good stuff Chuck!  I like your outline - obvious merit to that approach.
  
  $

         This is for Sysnet II starting with mod 4

Page 4-6   How about adding the results of "backup/list " command
		to show what a save set looks like.

Page 4-8   Bullet 1 could read "...label name for the volume on MUA0:"

Chap 4 in general.    Image backup and incremental backup could easily
		      be in sysnet I.  
I would drop pages 4-10 & 4-11.   I do not like teaching the use of
command procedures to do backup. But if it stays:

	Page 4-10  This procedure will run now and then again
		at 2 A.M. tomorrow.

		   for the privs do you really want "ALL"?

	Page 4-11  First sentence, delete the word "other".  This 
	procedure will resubmit itself every night.
	
		We check for Friday but could also check for Saturday
		and Sunday too.

		Bypass will bypass all protection and is dangerous.
		could readall be better here because we are only
		reading files.  However if we do /record we need
		bypass.

Page 4-16  second line in the top procedure should not have /record.
		I know lit is in some books but it makes no sense
		to have it here. 

This whole chapter 4 could be done in 1/3 the time if it was just
added into the chapter 12 of sysnet I and re ordered so it flows.
Example: incremental save and restore talked about at the same time.
/Image save and restore talked about at the same time.  If this chapter
stays where it is then the same things need to be done here.  Reorder
the chapter so it flows faster.


Page 5-7  Have the four basic phases names changed?  they were
	different than we see this on this page. 

Page 5-8 add we need cmkrnl to do this.

		We also should say that /noadapter is for software dev.
		and /adapter is for hardware devices.

Page 5-13 Ex. 5-4 "Set nocontrol_y" should be "Set nocontrol=Y"

Page 5-16 This page does not belong here.  It is for someone logging
in to the system.  Not he system coming up.

Page 5-18 ex 5-7  "On control-y" should be "ON control_Y"

Page 8-7  Add a bullet " Do not keep SYSUAF.LIS on the system."

Page 8-16  Add  that this will only work on "hardwired terminals"

 
    

         	This is a continuation of sysnet II problems

         For my comments on module 9 please look in the notes for
         this chapter.  My comments them are still valid.

         Pages 6-17 through 6-21 Should be removed.  It is not
         necessary to show them how to run authorize again.
         It is very confusing to some students to now talk about
         the install utility in the middle of a "TASK" to use the
         VMSinstal.com to install a product.  Sysgen is also
         confusing do to them never having seen it before.  We
         have been using SYSMAN for all things until now.  It is
         not necessary to point out that a produce may need to
         have GBLSECTIONS AND GBLPAGES modified.  Do you see on
         these few pages the wealth of questions you are opening
         the instructor up for.  All this previously unknown stuff
         in not needed here.

         	What is needed is a statement/note:

         			NOTE:

         	Whenever installing a new product it is
         imperative that you read the release notes for that
         product before starting the install.  In those notes
         you will be told of any requirements the product needs
         to function on your system.  Some system parameters may
         need to be changed, you may need to give the users of
         the produce special privileges or change the users
         accounts in other ways such as memory size.  It may even
         tell you that you need X free blocks on the system disk
         before you can start.  READ RELEASE NOTES FIRST!


         Once we have removed these pages and added a note like
         above we should then continue with the chapter and 
         show how to install a produce, move savesets to disk and
         make a copy of the release notes.

         	Then we should show how to do an UPDATE, UPGRADE
         and INSTALL of VMS.  It is only a few short pages more
         and much more valuable than the ones we took out.  It
         fits here and it would not later need to be put in
         another chapter and rehashed from the start.  This flows
         from a "logical" point of view and from a "TASK" point
         of view.

         page 6-22  FORTO50 should be FORTO54

         Page 6-28  WE run into trouble with modparams.dat in the
         common area.  Many parameters are node specific and some
         of them need to be mentioned in modparams.dat. Also running
         Autogen is node specific and may suggest changes that would
         not be valid for the other nodes.  Does anyone really put
         modparams.dat in the common area?

          
    

>         Page 6-28  WE run into trouble with modparams.dat in the
>         common area.  Many parameters are node specific and some
>         of them need to be mentioned in modparams.dat. Also running
>         Autogen is node specific and may suggest changes that would
>         not be valid for the other nodes.  Does anyone really put
>         modparams.dat in the common area?
          
    
				YES!