Conference koolit::vms_curriculum

    	A draft of the fourteenth Sysnet II chapter entitled:

    			System Monitoring

    	 	is available for review in:

    	  SUPER::ES$REVIEW:[SYSNET_II]SYSNETII_CHAP14.PS

    			Wendy

    I just copied over this module, and it's missing the Instructor
    pages.  Also, the Introduction is on the title page.
    
    -Sherry

    Omissions 	- prefixed [O]
    Nits	- prefixed [N]
    Typos 	- prefixed [T] 
    
    As .2 points out, this module has been run with /CONDITION=STUDENT
    (or maybe there is NO instructor information :-( ...)
    
    We also seem to have acquired the exercises - not complaining you
    understand!
    
    
    Page	Comment
    -------------------
    1-15	[T] Third line of table: DECnet VAX -> DECnet-VAX - this
    		    is a Corporate trademark
    
    1-19	[T] Notes on example: callout 1: the third line time
    		    field is wrong. It should be 13-JUN-1991 13:53:30.89
    
    		[T] Callout 2: third line: current process) per cpu ->
    					   current process per cpu)
    
    1-22	[T] Example 1-17: the command SHOW PROCESS must
    		    use the full PID not the last N characters
    		    For example:
    			$ SHOW PROCESS /CONTINUOUS /ID=206007CC
    
    1-26	[O] Table 1-4 entry INIT: Reset the display to a known...
    		    what?
    
    1-29	[N] The alignment could be better on this page

Please copy the following file for review of Chapter 14 System Monitoring,
(and Chapter 15 Performance). Sorry, it was originally compiled under DOCUMENT 
as a mini-course section; TABLE of CONTENTS, Index, Labs, etc.

Directory ES$REVIEW:[SYSNET_II]

SYSNETII_CHAP14_15.PS;1
                        898  18-JUN-1991 11:17:11.40  18-JUN-1991 11:17:12.72

Total of 1 file, 898 blocks.


The pagination problems, etc., are noted. The last edit was posted in parallel 
to reviewing. Isn't that always the way it goes when you try to hurry?  Thanks 
for the comments.


						Regards,

						Paul M.

    Firstly a thank you to Paul for posting the new version so quickly.
    
    Secondly: Wow! An index. What a difference that makes. Keep up the
    GREAT work in that department, please.
    
    Finally, I'm really only nitpicking in this reply. I've restricted my
    picking to the instructor pages after my review posted at .3.
    
    Page	Comment
    -------------------
    
    1-3		Last line: the VAX DOCUMENT reference tag, now expanded,
    		provides us with too many "module"s
    
    Remember most of these are nits:
    
    1-5a	Line 2: get in the -> get into the
    		Line 3: of data: later, -> of data. Later,
    
    1-17a	Bullet 1: display -> display)  ! closing parenthesis
    		Last line: and . . .      and what?
    
    1-19a	Three lines from foot: System manager -> System managers
    
    1-24a	SHOW PROCESS /CONTINUOUS - CTRL/Z also serves as an
    		exit, for consistency with other facilities under VMS
    		(Yes, I know CTRL/Y does as well!)
    
    		Three lines from foot: versus a idle -> versus an idle

                         Chapter 14
                       System Monitoring


1-9 Cna't we just mention these three command procedures and that they
are in sys$examples. Or how about putting them in an appendix? I think
it a bit much to go over them in class.

1-17 Why not put all the MONITOR classes at the beginning of the chapter
instead of halfway through it and after we have already gone over some of these.

1-18 Clusters are'nt until sysnetIII and therefore how will they understand
monitoring one if they dont know what a cluster is, especially the
different types and how if a disk is MSCP served it would have an effect on
monitor disk and a multinode summary.

1-23 I think its funny, but I don't know if nodenames HARLEY and WASTED
are appropriate.

1-27 I really don't think show cluster should be in here because they don't
know enough about clusters to see all this stuff!! Like CL_QDV votes or
CL_Q. Please that is a bit much.


Wendy Mullenhoff

		System  Monitoring
		Chapter 14

Introduction 	The last paragraph does not fit with this chapter when
		it mentions Module 2.

Objectives	The last one should read "various SHOW CLUSTER utility 	
		commands...."

1-6	Add a note to the student that this display is only since you
	went into the monitor utility not since boot time.

1-9,1-10
1-11 and 	
1-12	I am not really clear from the instrutor's page how this should
	be used.  Would you use all 3 at the same time.  Please clarify
	more.  Thank you.

1-10a	Mails a summary report.  Where?

1-15	Place page 16 before this and then follow this with page 18.
	
1-16	Change the last node name to anything but AND.

1-17	I would like to see this after page 5 if possible.

1-19	Please explain in the instructors guide and/or student book
	why the pagefile is a negative number.  I have been asked
	that question multiple times by both students and coworkers.

1-23	You could shorten what is displayed for each node without losing
	the concept.

1-25	Same as page 24 but there is another page 25. I'm confused.

1-25	I like introducing the SHOW CLUSTER here.  It is a utility that
	can be taught early without much knowledge about the cluster.
	Maybe stress in the instructor's page that even though they may
	not know what the different fields represent they can at least learn
	here how to create a display of their choice.

1-26	Before this page include a page that explains how to add and remove
	fields and classes in the SHOW CLUSTER utility.

1-28	Maybe move this page after 25.

1-29a	Last bullet mentions VAXcluster COMMAND PROCEDURE. What
	command procedure.  I didn't see it.

1-29	Why not have some of these displayed in an appendix for discussion
	purposes? Just a thought.

I know it is hard to include cluster information without teaching everything
about the cluster software.  Since these SYSNET courses were designed to
incorporate both cluster and networking I just wanted to say that this
chapter does a good job in achieving that goal.  What we will sell to
the customer is what we have stated in our internal goals.

Lynn White
Washington D.C.

    
    	The two week time period for reviews is over.
    
    	Any comments entered after this note will be considered, time
    permitting.
    
    			Wendy

I just wanted to let you know that your comments (most) have
been implemented. I appreciate the feedback and am sorry it took 
so long to respond; vacation, Pilots, SYSNET III, etc.

Added some basic Network Monitoring:

	Show Net
	NCP>SHOW KNOWN LINKS

etc.

						Paul

    I copied the last material of SYSNET II, and went throug it. Here are
    my comments. I hope nobody will be confused, because this entry is
    numbered chapter 14. In the last revised material this chapter is
    chapter 9. 

    In the chapter SYSTEM MONITORING there are some network related items
    included. Also an additional chapter about networking items is added to
    this course.

    page 9-10:
	MONITOR DECNET 
	Include on the instructor page how to talk about this command.
	Not indepth, but just globally: you can see how many packets are
	leaving, arriving and sent through.

    9-21:
	SHOW NETWORK on a routing node need to be completed. In a
	correctly set up node the nodenames will be displayed, and not 
	only the network addresses.

    9-22/27:
	It is correct to include some NCP information into this course, but 
	be carefull to 	include not too much, because all the network items, 
	known at this moment are from SYSNET I:
		- how to use SET HOST
		- how to use a terminal server
		- how to startup DECnet and LAT
	
	What is the objective of this paragraphs:
	(my idea) to give the student the tools to monitor the connection
	with the network, to see whether all is up and running.

	Second remark:
	In the next chapter the item to be discussed is Managing a Network
	Node. There is completely discussed what is the use of the 
	permanent and volatile database. there is discussed what is NCP,
	and how it must be used.

	Third remark:
	Talk only about lines and circuits, not about links.
	Leave the table with all the NCP commands away.

	My proposal about what is left about NCP:
	Leave these items in chapter 10 (the networking chapter), and move
    	this MOnitoring part to chapter 10 in a slightly different form. I
    	will enter that remarks to the notesentry about chapter 10.

Regards,

Joop

    re .10
    
    from the Pilot in LQO 2 weeks ago I think the instructor teaching the
    pilot and developer (as well as myself, sitting and doing QA)
    agreed on this as we talked about it and even reversed
    modules 9 & 10 for better order/clarity.  
    
    maybe Bonnie or Val have an update on this part.  
    
    irene

    Yup, we're switching chapters 9 & 10.
    

Hi,

Pg. 10-13 - Tyyypppo.

Pg 10-26 - Yea it might look a little confusing. We are creating an init file.
	   I was trying to show some useful commands. The save being one.
	   The write being another. They can look at their cluster info later.
	   See the Instructor Note.

	   I was writing a note befor as far as the nodenames and we CRASHED!
	   So suffice to say that there are restrictions on using nodenames,
	   usernames etc. It's trouble editing displays- we always get caught.
	   The format changes, old date, and so on. I don't like editing them
	   but again, we have to because of above, or we can't easily 
	   duplicate the same display. 

	   It's a pain to match up different displays from different systems
	   making them look the same - same disk.... I did some of that in the
	   in the ERRLOG stuff in Monitor for SYSNET III. So hence the 
	   different nodes. Things got changed a lot, moved, or deleted toward 
	   pilot. But we should be able to smooth it out in the update.

	   I used /ID= instead of /NODE= just for something different and
	   I didn't have to make up more nodes. I received their ID's from
	   a previous SAVE command. 

						Regards,
						Paul