Conference koolit::vms_curriculum

    Perry;
     
    I have taught this course three times and it has been well recieved.
    The fact that the developer was allowed to spend time at the CSC is
    very apparent.
     
    I have, however, recieved requests from our students for some data
    on network trouble shooting.  To that end I have added a full day on
    "The Rules of Access Control".  Why can I copy a file from node A,
    but can't copy a file from node B?  I also have the students build
    their own object database and then we manipulate various Access
    Control Information strings etc.
     
    Arnold Tarling, DLO10::TARLING, 483-4325
    

Arnold, could I take a look at your material? It probably makes sense to
add it to the course.

Perry

    Perry;
    I have sent you mail (on BROWNY) regarding these materials. I hope you
    find them useful.  Please call if you need more data.
    
    Arnold
    

Chapter 1, "Dependable Systems Overview," is available for review. The
files are at BROWNY::VMS_TS_DEPENDABLE*.PS.

Please note that my VMS and AXP V6.1 systems are not yet ready, so the code
examples in this chapter are not the ones that will be in the course (there
are only a few).

Comments here or to BROWNY::DONHAM.

Perry

    Perry, 
    
    I have taught this course 3 times with good results overall.
    
    The BIG negative is this student comment:
    
    	"Basically a rehash of System and Network Management II & III"
    
    I think 10% of students have felt this. Technically I agree. Some
    customers really expect more in the way of tracking down information
    and problems such as locking, resource usage, resource waits...
    
    The BIG positive is these comments:
    
    	"The best course yet!"
    	"I really liked the hands on experience."
    	"The other courses didn't give us this much good lab time."
    
    I have made sure that they have at least 50% lab time. The book
    labs plus "on the fly bugs, as the configuration allows" keep
    them busy all day.  90% really love it.
    
    
    The print problem chapter seemed to be cumbersome with little
    "flow". I use an alternate presentation. The labs have not worked
    out too well because the queue environment can get so gummed up.
    In fixing something they can mess up something else to confuse
    the issue to the point that it can become an unproductive experience.
    
    My solution (to be tested on my next teach in FEB 94) is a command
    procedure I wrote during the holidays.  Each student will use this
    menu driven procedure to set his own queue to a KNOWN working state.
    This queue has its own device control library (with working portrait
    and landscape modules), form definitions, lat port and DECserver port.
    
    The student selects any one of 7 bugs from the menu. The procedure
    inserts the bug, issues a print job in behalf of a "user", and
    sends a problem report to the students terminal. Once a fix is made,
    the menu can set the queue back to a know working state ready for the
    next bug.
    
    
    The procedure should be modular enough to add or change bug situations.
    The comment header follows at the end. If this if of interest, I can
    transport it to an enet node for access.
    
    BTW, I'm interested in using the muliple queue manager capability
    of V6.0 to reduce the chances of each trouble shooting group from
    interfering with each other. Has any one tried this?
    
    Leon Baldwin @lqo    or   SWAM1::BALDWIN_LE
    
    
    $!++ Automated queue lab bug insertion
    $!************************************************************************
    $!
    $! This procedure is intended to supplement the course:
    $! OpenVMS Troubleshooting for System Managers
    $!
    $! Students use this procedure to set a DECserver port, a lat port
    $! and a VMS print queue to a known working state. Then a menu
    $! selection will insert bugs into student queues, libraries, lat ports,
    $! or decserver ports.
    $!
    $! Students can procede at their own pace.
    $!
    $! Author:      Leon Baldwin
    $!              Digital Learning Services
    $!              Los Angeles, California
    $!              (310) 416-6578
    $!              DTN   520-6578
    $!
    $! Date:        5-JAN-1994
    $!
    $! Requrirements:
    $!
    $!      TSM must be installed on each system where this procedure is
    $!	    used.
    $!
    $!      Student account UIC member numbers must be in the range 1-16
    $!
    $!      One DECserver 200 or DECserver 300 must be available per 8
    $!	    students
    $!      Ports 1 thru 8 will be used on each server.
    $!      The DECservers must have lat node names LAB_01 and LAB_02 and
    $!      be added to the TSM directory with:
    $!      TSM> add server lab_01
    $!            (then follow prompts for ethernet address, decnet
    $!	    address, etc.)
    $!
    $!      TSM> add server lab_02
    $!              o
    $!              o
    $!
    $!      System logical name INSTRUCTOR must be defined to the location
    $!	    ofthe following files:
    $!                              portrait.txt
    $!                              landscape.txt
    $!                              userfile.txt
    $!                              user_report.txt
    $!                              decserver_bug6.com
    $!                              decserver_bug7.com
    $!                              decserver_printer_port.com
    $!
    $!      Problem synopsis:
    $!
    $!      Problem 1:      No device control library. Causes error message
    $!			    on job.
    $!      Problem 2:      Landscape form width is 80. Causes wrapping.
    $!      Problem 3:      Terminal width is 80.  Causes wrapping.
    $!      Problem 4:      Lat port mapped to bad server node name. Causes
    $!			    pausing
    $!      Problem 5:      Queue set to nonexistant lat device. Queue
    $!			    won't start
    $!      Problem 6:      Decserver port set to ACCESS LOCAL. Queue
    $!			    pauses.
    $!      Problem 7:      Decserver port set to wrong speed. Jobs
    $!			    complete with
    $!                      no output or with garbage.
    $!
    $!**********************************************************************
    

  Perry,
  
    I entered a few comments in this conference just after I finished the
  pilot.  The course really needs a bit more "stuff", as I can successfully
  teach it in 4 days the way it is.  The chapter that was going to be added
  originally was on Installation and/or Upgrades.  LOTS of problems there,
  but Emmalee either ran out of time or money, I forget which, so it never
  got added.
  
    As for a repeat of SysNet III (and II), yes, my same comments during
  the pilot, but considering the number of problems that the CSC gets on
  queues and lats and the boot process, it was decided to leave it in
  there.  Originally I think we had decided to pull some of the queue stuff
  to an appendix for reference, but again...time or money.
  
  $

Chapter 2, "System Initialization Problems," is available for review. The
files are at BROWNY::VMS_TS_INITIALIZATION*.PS.

Please note that my VMS and AXP V6.1 systems are not yet ready, so the code
examples in this chapter are not the ones that will be in the course (there
are only a few).

Comments here or to BROWNY::DONHAM.

Perry

    Perry,
    
    I'd like to pull the VMS_TS_*.PS files to have a read; can you post the
    full location spec please?
    
    Ta,
    
    Geoff 

The student guide for this course is available at 

	BROWNY::VMS_TROUBLESHOOTING_STUDENT.PS

Please note that our editors are taking care of the words; comment on the
content.

Regards,

Perry