Conference koolit::vms_curriculum

    	A draft of the second Sysnet II chapter entitled:
    
    	Handling Input and Output in a Command Procedure
    
    	is available for review in:
    
    	SUPER::ES$REVIEW:[SYSNET_II]SYNETII_CHAP2.PS
    
    			Wendy

    Review comments on the chapter:
    
    	Handling Input and Output in a Command Procedure
    
    Some particularly useful instructor pages in this chapter. The point
    about non-closure of files, for example, (page 1-15a) cannot be
    stressed too much. A good level of technical tips and hints
    
    Page	Comment
    ----	-------
    1-3		Line 6: typo sepcified -> specified
    		Penultimate line: typo sepcifically -> specifically
    
    1-7a	Line 2/3: "...system logical commands..." should
    		read "...system logical names..."
    		Final line: typo comman -> command
    
    1-18	Penultimate line: nit - word write should be uppercase

The following are comments on Module 2 of SYSNET II

Page 1-4	Might also want to list the DCL Dictionary as a resource.

Page 1-11 	Should say something here about inquire putting user input
		on the command stack (Recall Buffer) and read/prompt not 
		not doing it.

    
	Review of chapter:

	HANDLING INPUT AND OUTPUT IN A COMMAND PROCEDURE

Page 1-7a: line 4:
           typo: comman ---> command

Page 1-11: remark to re 75-3.
           It's on the instructor page 1-11a

Page 1-12: The blank lines in example 1-5.
	   Please use $! instead of a $

Page 1-17: Example 1-8 wrong labelname.

           GOTO LOOP must be ......  GOTO WRITE_LOOP (label name) 


So far the review of this chapter.

Bye arjen.
    

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

		Handling Input and Output in a Command Procedure
		Chapter 2

Great - Objectives truly match the topics and what is taught in this
chapter.
Could the topics go on the same page as the objectives?  This saves
money and also is more attractive to the eye than the current page 1-5.

1-7a	First sentence should read "Before explaining..... want to explain
	the system logical names in general..."

1-7	Maybe state what the word execution file and device refer to.
	Also could the chart be expanded to include BATCH?

1-8	An example of concatenating would be super.

1-17	In the example the line $GOTO LOOP should be $GOTO WRITE_LOOP


Lynn White
Washington D.C.

    Since logical name tables are mentioned in this & later modules, we're
    restoring some of the material on logical names.
    
    	A draft of the new module, entitled:
    
    	Using Logical Name Tables
    
    	is available for review in:
    
    	SUPER::ES$REVIEW:[SYSNET_II]SYNETII_CHAP1A.PS
    
    Please post review comments by August 19. They won't be incorporated
    before the pilot, but we'll be able to incorporate them during the
    post-pilot revision pass. 
    
    			Val
    

1-8     An example of concatenating would be super.

Well... we discuss concatenation in chapter 3 so I think I'll leave it
there. Is there anything specific that you want covered that's not in
chapter 3?
 

This reply is limited to technical errors only.  I'll refrain from making
comments one way or the other about content, style, etc....

Module 2 (Using Logical Name Tables) in SYSNET II



p. 2-12		Example 2-5 is a great example of what NOT to do and most
		System MAnager I students have discovered it the hard way.
		Also, we should not use $ RUN SYS$SYSTEM:AUTHORIZE in our
		examples.  It doesn't work the way students expect it to
		if there is no logical name assignment for SYSUAF.  (Without
		the logical, the above command expects SYSUAF.DAT in the
		current default directory.

		The correct syntax for changing a user's default device in
		SYSUSAF.DAT is as follows:

		$ SET PROC/PRIV=SYSPRV
		$ SET DEFAULT SYS$SYSTEM
		$ RUN AUTHORIZE
		UAF> MODIFY ROUNDS/DEVICE=USERDISK	!NOT /DEFAULT=



				Susan

    1.  I would add the creation of logical name tables and what and
    how to change the search list.  This should take about 3 pages.
    
    2.  put the info (when they go away) from page 20 on page 5 and
    talk about this then.  It would add only 4 lines there and drop a
    full page later.                                      
    
    3.  Page 2-12  Typo  in ex. 2-5   UAF> modify Rounds /default=
    		should be:            UAF> modify Rounds /device=
    
    

I agree with .10; I'd also like to see the creation of logical name tables and
the search list added to this course.

				Susan

   Those little 3-page topics can add up, so that's one where we drew the
   line, but OK, we can put it back in if there is consensus -- thanks,
   
   					Val
   

    they may "add up" but they could make the difference between "where's
    the beef??" (and why did you bother mentioning it?) 
    
    versus 
    
    "thanks - I needed to know that!"