Conference koolit::vms_curriculum

    The course specification for VMS System and Network I

    is ready for review. The specification PostScript file 
    is in the location:

             SUPER::ES$REVIEW:[SYSNET_I]SYSNET_I_SPECIFICATION.PS

    Please review the specification. Modules will begin being posted
    shortly. It is important that you review the specification for
    topic location and flow and the modules for informational content.

     
    NOTE: The first 9 chapters of this course will be the same as the
          3 day course VMS for Application Users I. This course has
          just piloted. The changes to the course will be reflected
          in this course. When the revised list of topics is available,
          the specification will be updated.

             

    I've read the course specification.  I hope this can be assembled
    without the total page count getting out of hand.  Even if the
    materials are well written, if it comes to 93,000 pages there may be
    minor problems with pacing!
    
    Mark Thorne

   
Fred;
  
  I have just completed a review of the "SYSNET_I_SPECIFICATION" and have
  the following originations about the spec:
  
  1. Page 1, Section 1.6, "Prerequisites None".  I feel that the student
     should be familiar with basic computer terms.
  
  2. Page 2, Section 1.9, This section essentially says that one of the
     topics that we are "not" going to talk about in "System and Network
     management I" is DECnet Network Management; we may need a different
     title for this course.
  
  3. Page 7, Section 2.4.5, Does a discussion of "ON-LINE BOOKREADER
     DOCUMENTATION SET" include any labs using bookreader?  I would
     venture to say that not all training centers (make that Campuses)
     will have the needed hardware.
  
  4. Page 17, Section 2.10.5, I would have hoped to see something on 
     installing the DECnet license and runing NETCONFIG.COM; possibly
     you intend to include these items under "Operational Functions"
     near the bottom of the page.
  
  Overall this spec looks pretty good to me.  It covers quite a bit of
  ground.
  
  Looking forward to the modules,
  
  Arnold Tarling.

    First off lets make it clear that I DO NOT teach system management
    courses at any level.
    
    Second, I don't believe this course is viable as it stands.
    I wouldn't like to attend it even with the knowledge I have of VMS.
    There seems just too much material
    
    The spec has quietly omitted any entries for:
    
    	Day:
    	Lecture Time: and
    	Lab Time:
    
    My guess is that Chaps 1-4 would be Monday, Chaps 5-8 Tuesday,
    Chaps 9-12 Wednesday, Chaps 13-15 Thursday and the rest Friday.
    
    If one assumes no formal prereqs (really?), attendees are going to have
    a hard time. This is a course I would like to have seen delivered over
    four days. No wonder you folks went quiet when I asked about four-day
    courses :-}
    
    Some other points (I choose not to put these as replies to other notes
    in this conference because these are not module review points).
    
    Chapter 6:
    	Objectives: Move around a text file (as opposed to move around
    		    a document, having introduced text file).
    		    Similarly in the topics.
    
    Chapter 10:
    	It seems impossible to achieve the final objective - Describe the
        structure of VMS files and directories. The final topic on system
    	files directories and logical names does hint at it but I would
    	expect a discussion of sequential, relative and indexed structures
    	from the objective.
    
    Chapter 11:
    	Topic: VMS DEVICE NAMES sits uncomfortably at the bottom of the
    	page. Are there some sub topics missing?
    
    Chapter 12:
    	This topics list rings rather vague and lacking detail in
    	the early headings.
    
    Chapter 13:
    	Not sure why Operator Log File is included in the sub topics
    	to COMMUNICATING WITH USER PROCESSES. There is a sort of
    	tenuous link but...
    
    Chapter 14:
    	TOO BIG! The list of topics looks like a course in itself.
    	
    Page 31, Table 1: I would like to have the course media on-line as
    		      well as on tape.	

I'm about to post the next rev. of the spec for Sysnet I. It describes a
smaller course, which I hope corresponds closely to the topic list revised
at the instructor forum. It also states objectives in a task-oriented
manner, unlike the previous rev.

It doesn't address a few of your comments, which I answer here in random 
order.  

-  I don't know yet whether we can put in the project plan that we will provide
   lab files on line (of course I want to). Will check with management.

-  We haven't figured out the teaching times yet. (I hope we can do
   that with the help of the field reviewer.) 

-  About module 14 being too long: noted. I'm not breaking it up in the
   spec yet, but we can still break it up in the material.

-  Plan all along has been that this course should have no prereq. We'll
   have to discuss this further, since the User courses are prereqless.

-  Several reviewers have expressed the opinion that there is too much on 
   queues. No two agree on which topics to leave in. Needs further discussion.

-  Operator Log File is in the "communicating" module because it relates to
   REQUEST/REPLY. That's where it is in the current Sys Mgt course. Got a 
   better place for it?

-  NETCONFIG.COM will not be in Sysnet I; the presumption is that we're 
   teaching how to manage an already-configured system. Consensus at the 
   instructor forum was to put it in Sysnet II as part of "installing &
   updating system software."  Stay tuned for revised Sysnet II spec.

					Val   

    Revised spec. for Sysnet I is now in 
    
    	{HARDY,SUPER}::ES$REVIEW:[SYSNET_I]SYSNET_I_SPECIFICATION.PS
    
    

         Chapters 1 through 9 of SYSNET I are ready for review. Copy 
	 them from:

         	ES$REVIEW:[SYSNET_I]SYSNET_CHAPn.PS

         where n is the number 1 through 9.

         These first chapters are a somewhat reorganized version
         of the USER I course and are intended to be taught in
         the first 2.5 - 3 days of the SYSNET I course.

         We have tried to slant the presentations so they relate
         more closely to system management tasks.

         We're specifically looking in these chapters for
         suggestions on doing this more successfully. Of course,
         if you think we did it well, you could tell us that too
         %-)

         Thanks in advance for the review comments.

    I don't think I updated the "module to review" dates in the course spec
    -- expect the remainder to be posted throughout this week, with the
    last one on May 10.
    
    					Val

    Val;
     
    A quick pass through the revised Sysnet I spec yeilds the following
    observations:
      
    1. Page 1, Section 1.6, I still have difficulty with prerequisites
    "none". When you describe the UICs you start talking about "octal".
    This will be quite a chalange if the student has never herd of
    relational numbering systems beyond decimal.
      
    2. Page 2, Section 1.9, I noticed the clean-up in the "non-goals".
      
    3. The key to this course would appear to be "keep it on the light
       side"; there is still quite a bit of material.
      
    Arnold.
    

    
    I must agree with previous concerns anout the prerequisites being
    "None".
    
    I feel that at least an "Introduction to Computer Concepts" is
    necessary, with perhaps a few weeks experience of using any computer.
    
    This course is aimed at new VMS System *Management* staff, after all!  
    
    Someone who sits this course with no knowledge or concept of what computers
    are or do is going to have a nasty experience and could well be lost for 
    ever by Monday lunchtime.  That is bad for the Student, bad for the
    Instructor, bad for Educational Services ... and bad for Digital!!
    
    
    Geoff

	Chapter 11: "Managing System Hardware" is ready
	for review.

		ES$REVIEW:[SYSNET_I]SYSNET_CHAP_11.PS

	Note:

	This chapter and all chapters that reference hardware
	related material have been drastically cut-back since
	we are currently also developing the Hardware Manual
	[Bill Price's project] that will be available to students
	in class.

	Chapter 10: "A Closer Look at the VMS Environment" 
	is ready for review.

		ES$REVIEW:[SYSNET_I]SYSNET_CHAP_10.PS

	Note:

	This chapter and all chapters that reference hardware
	related material have been drastically cut-back since
	we are currently also developing the Hardware Manual
	[Bill Price's project] that will be available to students
	in class.

Also...

	This one contains a description of the system manager's
	role...please take a good long look at it...

	Chapter 12: "Managing System Users"
	is ready for review.

		ES$REVIEW:[SYSNET_I]SYSNET_CHAP_12.PS

	Note:

	This chapter and all chapters that reference hardware
	related material have been drastically cut-back since
	we are currently also developing the Hardware Manual
	[Bill Price's project] that will be available to students
	in class.

For this one...

	I remember rumblings at the Fall IPF about onoy doing
	ADDUSER.COM. That is not what we did here...what do you
	think?...

	Chapter 13: "Starting Up And Shutting Down A VMS System"
	is ready for review.

		ES$REVIEW:[SYSNET_I]SYSNET_CHAP_12.PS

	Note:

	This chapter and all chapters that reference hardware
	related material have been drastically cut-back since
	we are currently also developing the Hardware Manual
	[Bill Price's project] that will be available to students
	in class.

Folks,

Just a sanity reminder...[grin]

	The first nine chapters [from USER] of SYSNET I
	have 168 student pages...[a little better than 50
	page per day clip]. [There are actually a few
	more pages in the USER version, but we have
	consolidated some of the information for the
	SYSNET version.]

	Chapters 10-13 of SYSNET I currently stand at 95
	pages. We have two more chapters to go [Managing
	Queues and Managing Disks and Tapes]

	The conclusion is inevitable.

	Please lend a hand in either cutting the materials
	even further [we have slashed a good 50 percent of
	the original content already] or in pointing out
	information that should/could be moved 'up a course'
	into the second week [which will have the effect
	of pushing stuff from there into the 3rd week...and
	so on.]

	Thanks.

	Chapter 14: "Working with Queues"
	is ready for review.

		ES$REVIEW:[SYSNET_I]SYSNET_CHAP_14.PS

	Note:

	This chapter and all chapters that reference hardware
	related material have been drastically cut-back since
	we are currently also developing the Hardware Manual
	[Bill Price's project] that will be available to students
	in class.

Folks,

	This one has been chopped and re-chopped and is suffering
	from battle fatigue. [grin]We have to get the page count
	down...so we have really slashed on this. Help us out?

	Chapter 15: "Managing Tape and Disk Volumes"
	is ready for review.

		ES$REVIEW:[SYSNET_I]SYSNET_CHAP_15.PS

	Note:

	This chapter and all chapters that reference hardware
	related material have been drastically cut-back since
	we are currently also developing the Hardware Manual
	[Bill Price's project] that will be available to students
	in class.

Folks,

	This one has been chopped and re-chopped and is suffering
	from battle fatigue. [grin] We have to get the page count
	down...so we have really slashed on this. Help us out?

Also...

	BACKUP is missing...we know it...we are working on it.
	Suggestions happily accepted.

    
    A few administrative notes and a QUESTION:
    
    NOTE:
    
    This course has been moved back into the USER curriculum...so
    send your fan mail to the USER team. [grin] Specificall, Hannah
    and I will be working on the SYSNET I course since it parallels
    the OPERATOR USER course quite closely. Mail to either of us
    will get an immediate [if not desired] response. [chuckle]
    
    QUESTION:
    
    Both of the instructors who have come to ZKO to review this course with
    us have strengthened our own misgivings about the length of it. So...
    how can we adress this. We are hovering at the 300 page mark. Still too
    many I fear.
    
    Current suggestions to cut the count include:
    
    	Making some of the introductory chapters such as
    	EVE and FILENAMING reading/Labs only. In other words, there
    	would be a separate reading book that would have the
    	background for the labs, but students would receive no
    	formal lecture on them. [This would cut out about
    	2-3 hours of lecture and about 60 pages.]
    
    	Elliminating some major topic in the last two days.
    	The feeling is that there is just TOO MUCH to cover in two or two
    	and a half days. So if you were to pick...what topic would go?
    
    		My favorite here is MANAGING USERS. All the other
    		chapters deal with the management on non-user related
    		information...static types of tasks. The User chapter
    		is HUGE...it introduces a multiple layered decision
    		type of task, and it only barely scratches the surface 
    		at that. Certainly not enough to really have the student
    		return to a site and do anything particularly useful.
    
    		My vote would be to concentrate on the physical managment
    		type stuff and start USERS with the second week.
    
    	Other options? Please? I don't think this is really teachable at
    	this length and with this number of topics covered.
    
    	Thanks
    
    Melinda

    Melinda;
      
    1. I am not very excited about making EVE and FILENAMING read only
       labs.  A selfpaced type of (lab) treatment to these topics with about
       30 min lecturer on each topic would work I believe.
      
    2. Back in the chapter with MAIL I recall thinking, "I don't use hardly
       any of these MAIL features.
      
    3. I very much agree with you on moving "Managing Users" to week two.
      
    Arnold.
    

    I beg to differ about removing "managing users" from week I.
    
    If you've ever been a junior system manager, what was one of the first
    tasks you had to do? Probably adding/removing users (if only because the
    senior system manager was tired of doing it...)
    
    The Job Analysis report supports this opinion. Small-system managers
    list only two tasks as being "very important": setting up user accounts
    and performing full backups. System managers list it as "important." 
    
    Of the tasks we now cover in Sys/Net I, the ones having lesser
    importance than adding users (again, according to the Job Analysis
    report) are: "monitor user activity," "set up and define batch queues,"
    "prepare/partition disks for use," "examine & interpret error log
    files," "monitor queues." 
    
    					Val

    Re .20 - I agree...
    
    I would rate myself as a junior system manager if I had to take over a
    VMS system - either within Digital or outside Digital.
    
    What would petrify me is a "clever" or "smart" user coming along
    and asking for an account or, if they've already an account, some
    more privileges "...can't work without SETPRV, PRMMBX..." etc.
    
    Fundamentals on what adding a user means, what access they should
    have, what low-level privs permit and so on, would be vital knowledge
    early in my career.
    
    The crass use of $ SET PROCESS /PRIVILEGE=ALL should be exterminated at
    SysNet I. It's all too prevalent at customer sites I visit. Often
    inappropriate privileges are bestowed on too many "ordinary" users.
    
    As a new system manager I would be looking to an introductory course,
    like SysNet I, to give me the comfort I need - protection from those
    who might seek to take advantage of my limited knowledge.

    
    We need to take a vote I guess...the suggestion came from the
    intructor reviewer who is going over the material this
    week. 
    
    I hadn't checked the job analysis report, thanks Val. I guess
    based on that I would go for something different...but...what?
    
    I need some suggestions on what to elliminate...not just
    admonitions NOT to elliminate a certain topic. Or do we sail
    into pilot with a huge course and see if we can make it
    fit in the classroom.
    
    Comments? Suggestions? Thoughts?
    
    Mel
    

    Well, I was suggesting these as candidates:
    
    >Of the tasks we now cover in Sys/Net I, the ones having lesser
    >importance than adding users (again, according to the Job Analysis
    >report) are: "monitor user activity," "set up and define batch queues,"
    >"prepare/partition disks for use," "examine & interpret error log
    >files," "monitor queues." 
    
    
    					Val

    Given the data that Val referenced in the Job Analysis Report I would
    agree that "Adding Users" should remain in week one.
      
    The topics Val mentions in .23 are less important and I would rank that
    list as follows (which to cut first):
     
    1. Set up and define batch queues.
    2. Examine & interpret error log files.
    3. Prepare/partition disks for use.
    4. Monitor queues.
    5. Monitor user activity.
      
    Arnold.
    

    
    I love it! [grin] Batch queues has been in and out at least three times
    that I am aware of...I can only support the vote to take 'em out
    again...
    
    How do you folks feel about the discussion in ?49? I think...one fo the
    geenral topics about deleting a bunch of the MAIL stuff? I am hestant
    to muddle the first nine chapters, but how do you folks feel?
    
    How would you feel about elliminating the QUEUES chapter altogether?
    
    I will take a look-see at how much we gain by hitting the first two or
    three of the topics listed and post it here.
    
    Thanks
    
    Mel

>    I beg to differ about removing "managing users" from week I.

I agree with Val about the importance of including "Managing Users" in week I
for all the reasons she gives and one more.  

My experience with running a data center was that we did 2-3 accounts changes
per day with a client base of 300 users.  By changes I mean: Adds,
Deletes,Modifications including disk quota, password problems etc.  This was an
easy thing to turn over to a new person.

    
My turn to add tuppence worth...

I've just reviewed the management chapters of SYSNET I. Review comments are in
the appropriate places, but on the whole I found their content and level just
right for the intended audience.  They give a good introduction to the system
management tasks. I guess a lot of the success, however, will be in the
Instructor giving just enough information for the students to feel confident in
performing the tasks "back home", and not talking too much about each topic.

Perhaps the course title should be "An Introduction to VMS for System
Managers"? 

Re: What can be removed, if anything?  I vote for keeping (some) queue
information.  I haven't seen the Operator's course content, but I feel that
there should be (at least) the same material.  System Manager's have *got* to
know more than their Operators :-)

If you want to drop some queue information, then I'd remove the "creating
queues" part. As the Curriculum Program Plan says, new system managers are
expected to have access to "support" people/resources.

Other candidate topics for "chopping" are: 

Managing System Hardware

	- Handling Hardware Problems. I feel the detail here is too deep.
	  I don't expect novice system managers to (want to) look at the error
	  log, or issue SDA commands, or care too much about diagnostics.

	- Any of these can be "learned on the job" if they're needed between
	  SYSNET I and II - from the "support" available to the new manager.

Closer Look at the VMS Environment.

	- This is a good chapter. I like it. It gives a good, general
	  introduction to all sorts of things. However, I feel that some
	  topics could be dropped *if* room is needed for others.

	- Topics that I feel can be removed are:

		o DCL and CLIs - surely mentioned earlier in the course
		o Discussions on scheduling, working sets, balance set,
		  swapping. These could be introduced early in SYSNET II.

	- Process-related information could be "pruned" also.

All the rest, I feel, has to stay.

Stephen

The following milestones have been identified for the development of the System
and Network Management Curriculum to help the instructors schedule time for
field review.

Posted Date is the date at which ESDP expects to start posting pointers to the
modules.

Preparation Week is the week the instructor from Bedford will be in ZKO to
review the course materials and consult with the developer.

Pilot is the start of the week in which the Bedford Pilot will be held.


			Posted		Preparation	Pilot
                        ______		___________	_______

Sys Net I		done		done		5-Aug-1991

Sys Net II		28-May		29-July		12-Aug

Sys Net III		12-July		7-Oct		28-Oct

    I've posted one more revision of the spec; it reflects more accurately
    what's in the course and might be a useful reference. 
    
    It's in the same place:
    
    	ES$REVIEW:[SYSNET_I]SYSNET_I_SPECIFICATION.PS]
    

    The pilot draft of the Sys/Net I instructor guide is in:
    
    	ES$REVIEW:[SYSNET_I]SN1_IGPROFILE.PS (5599 blocks)
    
    This is the version that will be used in the course pilot on August 5.
    
    If you have any further comments, please get them to us by August 9 so
    that we can look at incorporating them in the post-pilot revision pass.
    
    Again, thanks to those who have given us comments.
       
    					Val

    

    
    

    
    
    I read that the master Sysnet I was available in
    
        SUPER::ES$CM:[EY-G986E]EY-G983E-IG-0001.PS_LZ
   
   but, it does not seem to be there.  Is it available anywhere?
   One of the instructors here wants to start prepping it.
      
    
    Wendy Mullenhoff
     
     

    Ah, sorry! Sys/Net I was completed and then put on hold so we can do
    the minor work necessary to update it to VMS Version 5.5.
    
    In the meantime, the (V5.4) instructor guide is in
    	
    	SUPER::ES$REVIEW:[EY-G986E]EY-G986E-IG-0001.PS
    
    As far as I know, the biggest changes will be new examples for the SHOW
    QUEUE and SHOW ENTRY output, and changing LTLOAD.COM to
    LAT$STARTUP.COM.
    
    					Val

    The  final IG (compressed) is in 
    
    SUPER::ES$INSTRUCTOR_GUIDES:EY-G986E-IG-0001.PS_LZ
    
    					Val

    
    NOTE: 
    
    This reply is directed at no one body in particular....in fact, it
    addresses everyone! Developers, Instructors, Marketing/Sales,
    Management...just in different ways.
    
    I am disgusted! as well as frustrated with the roll out of the new
    curriculum. This is the story...
    
    I had been on the phone numerous times with management as well as other
    instructors and system admin persons discussing whether or not, I
    should install v5.5 for the new SYSNET courses which I was to teach in
    St. Louis this week. I was told that the new courses would not be OTS
    until 2/28 for SYS/NET I and 1/27 for SYS/NET II. 
    
    OK...the decision was made...I would teach the SYS/NET I course this
    week with the PRLM materials I had received some time ago. The 500+
    overhead transparencies had been made with the PRLM materials. It was a
    go.
    
    BOMB...I set up the classroom on Friday afternoon; had an extra course
    kit; opened it, just to verify what was going to be taught and 
    
    WHAM!!! the student guide reflected this number: EY-G986E-SG-0001
    
    OUCH!!! Panic! My systems are all currently running 5.4-2, not 5.5.
    Sunday morning, I compared, page for page, the new student guide to the
    one I was told we (ed. svcs.) would be using. The pages were different.
    The material was different...
    
    WHAT TO DO: You tell me...what choices did I have....
    
    Upgrade to v5.5? NO...what customers on the 13th of January are going
    to have 5.5 installed on their machines....NONE! It hasn't yet shipped.
    
    Recopy the entire manual? NO...in this day and age when a 100-count box
    of overheads costs $45.00 at a discount office supply, I couldn't
    justify recopying the entire manual...YES? Piece it together as best I
    could and run with it.
    
    Apologize to the customers....NO.
    
    Explain...market....schmoooze?...YES. I painfully explained to the
    customers that the system they would be working on was running 5.4-2
    and the course materials would reflect 5.5; I sold them our good
    intentions of providing them with up to date info for 5.5 and I
    schmoozed them by teaching both 5.4-2 and 5.5....namely in the queue
    management area.
    
    In practice, I didn't have a problem with this....I have been ready for
    the new release. But, I am appalled at the way in which it was handled.
    
    SURPRISE! Fortunately, I had a half day to quick-think through my
    ideas. I am sympathetic for other instructors who didn't.
    
    I enjoy challenges but at the same time I like to avoid embarrassment.
    It doesn't make me look bad when I'm doing a tap-dance of
    explanation....it makes Education and Training look bad. 
    
    Let's learn to communicate better....so development is ahead of
    schedule....YAHOO. Let the delivery groups know and allow us commend that
    achievement. We really need to work together.
    
    ONE OTHER NOTE:
    
    In the course kits...the new hardware guide was warmly
    welcomed....however, the absence of a three-ring binder was ludicrous.
    To solve this problem, I actually went digging in someone's trash and
    found enough binders to appease the customers. 
    
    I really want to come down off the soapbox....I am not superman, nor do
    I pretend to be, however, these things seem to add to unproductive
    time to my rather hectic schedule. This is a joke.
    
    Once, again, I will reiterate....let's work together....and good luck
    to all of us in the education and training environments. Times are
    hard....only we can make them better.
    
    Regards...

Here are some errors I found in teaching the new SYSNETI course.

Page
2-18	Two typos
        "ther curser" should be "the cursor"

4-11	The device name starts out as $1$DUA1: and then changes
	to VMS$COM  -  make the devices all the same.

6-27	You actually deleted 7 files.  The system message says 6.

6-33	The file names do not match. The displays are LISTA.DAT and LISTB.DAT
	but the last line showing the command list LIST1.DAT and LIST2.DAT

8-14	In the last display the ACE should have "PERSONNEL,ACCESS"
	not "ASSCESS"

9-6	In the table 9-2 the DEFINE needs the qualifier /SYSTEM.

9-7	Just a thought. Since this is the first time students are seeing
	logicals don't use a logical for the device name.  That is instead
	of using WORK1: use DUA2:  

11-3	Objective - The first bullet should read "Describe the different
	components of the hardware environment" not the "console system".

11-12	Typo - Use the the

13-5	The file name is spelled incorrectly, it should be
	SYS$QUEUE_MANAGER.QMAN$JOURNAL

13-5a	Same as above

13-14	Last sentence has a typo  -  commad should be command.

13-15	DELETE/ENTRY was not talked about in this chapter so you should
	remove it from the summary.

15-7	"ZEUS" should be listed in the display since it is the
	nearest area router.

15-11	Since this course is to include cluster information all the
	shutdown options should be listed.

	They are:
	REMOVE_NODE
	CLUSTER_SHUTDOWN
	REBOOT_CHECK
	SAVE_FEEDBACK

16-47	Change Question 2 to read "A system process that performs system
	wide queue management and control tasks.  (We will no longer talk
	about JOB_CONTROL here.)

	Also the word display is spelled disp[ay.

16-48	Incorrect answer to question #2. It should be Queue_manager.

17-50	Directions say to delete the [.TEST] directory but in the solutions
	you have [.MEMO]*.*;*

18-27	b. Should read "Listing messages you have "received."
	Also correct the question part.


Glad to see the HELP chapter moved to the beginning of the course.
I did get all the topics covered in the 5 days. Comments from the
students were very positive. The only negative item was the fact that
they felt the objectives were ambiguous.