Conference koolit::vms_curriculum

    
    	A draft of the seventh Sysnet III chapter entitled:
    
    		Maintaining Queues
    
    		is available for review in:
    
    		SUPER::ES$REVIEW:[SYSNET_III]SYSNETIII_CHAP7.PS
    
    			Wendy

                             Chapter 7
                     Maintaining Queues


7-4 1st bullet says
     Your system must be connected to a network when it meets any one of
the following conditions
     .Your computer is part of a Vaxcluster configuration.

If you have a strict CI cluster is does not have to be on E-net

7-5 The distributed Job Controller

Maybe tell them the directory and name of the common queue file.
  -some examples of the generic queue feeding or not feeding specific
execution queues.

You mention the distributed job controller directs print jobs to the execution
queue with the lowest ratio of jobs to queue limit.  (perhaps mention that
is only done if your job is submitted to the generic queue.

7-6
More info on RSM and DQS. I know virtually nothing about those two, and the
instuctor notes need serious help here.

7-7
Examples.

	SYSNETIII-MAINTAINING QUEUES
	Chapter 7

Overall comments - For the customer this chapter is without any
		substance.  The information on Remote System Management
		and DQS should be removed since they are layered
		products that not all customers have. Take these away
	        and there is nothing left.  Maybe the best bet would be to put
		this information in the other SYSNET course. 

page 7-5	Typo fourth bullet "queues first nad" should be "and"


Lynn White
Washington D.C.

    First.  The title leads us to beleive we are going to learn about
    maintaining queues.  We don't!!!  Lets confuse them.  The title
    should be changed to "Maintaining queues in a Multi-node
    enciornment".  The chapter still does not do this but this title
    is closer to the intent. 
    
    	We have students who make decisions on what courses to take
    based on the table of contents or just titles of chapters.
    
    Second.  Read the objectives.  I know nothing about the two topics.
    I have read the module and still do not know anything about or how
    to impliment the objectives.  We mention a few things, some wrong
    and some layered products not everyone has but no substance on
    how to meet the objectives.
    
    Third.  Bullit one. page 4.  In a vax cluster all that is needed is
    the CI bus.  No network needed.  Even a cluster on a network does
    not need all nodes to be on the network: just one
    
    page 5.  bullit 4 "nad" should be "and".
    
    
    Forth.  If we mention the layered products and not "how to" it is
    a waste.  If we don't mention them there is nothing here.  Either
    case we could lose this module on way to the printer and no one
    would know.  Add this info else where in another course.

    
    
        In order to make the pilot schedule, Monday 9/23/91 will be the 
        review cutoff date. 
    
    	Any comments entered after that date will be considered after the
        pilot.

                      Thanks for all of your comments,
        			Bonnie
    	

  Well, this module doesn't look much like the one that was originally
  reviewed here.  Best I can guess it's "overflow" stuff from SysNet II
  and several pages from SysMgr II.  Content is rather basic and I didn't
  spot any bad errors, just 'nits'. 

  It seems as if this module is just wedged in between two non-related
  modules.  Maybe if you reversed the Disk and the LAT (or moved Disk
  behind this module) modules we could transition much more easily into 
  this module.

  7-5a, 2nd note --
       This page redundantly restates the same info as the 2nd paragraph
       on this page.

  7-9a, note --
       Same basic info as 2nd sentence on page 7-7a

  7-15 --
       We are discussing ACLs here as they relate to queues, but we haven't 
       talked about ALCs until module 8 (yes, I saw the 1st line on page 
       7-16a, but I disagree).

  7-16, 3rd "operation" --
       All the word wrapping on this example is terrible.  I have to write
       it on the board so the students understand what they are reading. 
       We need a different format for these very long commands.

  $

>  7-15 --
>       We are discussing ACLs here as they relate to queues, but we haven't 
>       talked about ALCs until module 8 (yes, I saw the 1st line on page 
>       7-16a, but I disagree).
    
    Fair comment. In the interim, can you delay this one topic until after
    chapter 8? 
    
>  7-16, 3rd "operation" --
>       All the word wrapping on this example is terrible.  I have to write
>       it on the board so the students understand what they are reading. 
>       We need a different format for these very long commands.
    
    That is pretty awful, isn't it. How about I make sure it gets fixed in
    the TBI, and then post a copy of that table here. Remind me if I
    forget.
    
    						Val

|>  7-16, 3rd "operation" --
|>       All the word wrapping on this example is terrible.  I have to write
|>       it on the board so the students understand what they are reading. 
|>       We need a different format for these very long commands.
|    
|    That is pretty awful, isn't it. How about I make sure it gets fixed in
|    the TBI, and then post a copy of that table here. Remind me if I
|    forget.
  
  How about breaking it into 2 SET ACL commands and maybe using R+W+E+D
  syntax as an example of common abbreviations.  I usually don't like
  abbreviations, but system managers are well aquainted with the "S:RWED" 
  type displays from DIR/FULL, etc.
  
  $

  I found another one....
  
  
  7-12, 4th "DCL" commands --
        This line references LN03_BORDER.TXT, when in fact it should be
        LN03_PORTRAIT.TXT
  
  $