Conference koolit::vms_curriculum

    Hello out there................
    
    Is anyone out there?.............
    
    
    Hi folks,
    
    I find it  hard to believe that these labs are just PERFECT 8-)))).
    Please try to get your comments on these to us soon, we are running out
    of review time.
    
    Hannah

    I felt these exercises to be pitched at the correct level.
    
    How many of us REALLY remember what it was like learning to drive VMS
    from scratch? The hallmark of a sympathetic instructor?
    
    It was frustrating not to find ANY serious typos but a great pleasure
    to report that fact. Well done!
    
    One irritation was the outdatedness of some of the system displays.
    OK call it a nit but dates like 1988 (page 2) must be 199%.
    
    (Can't VAX DOCUMENT [version 2, that is] of DECwrite with its LiveLink
    go off and get the latest display every time a book build is done? ;-} )
    
    On page 10  5.c. I think "...prompt, enter C." should either be
    highlighted as short for CHANGE or have the word CHANGE instead.
    Yes, I know its another nit but I was getting desperate!
    
    The exercise on page 35 prompted me to question whether we tell
    students at this level about removing all protection codes from the
    owner. Removing all owner access appears to the new user to deny the
    owner rights to do anything to the file or its protection. Perhaps this
    is best left as a class "...what if we remove all protection codes from
    the OWNER field..."?
    
    -- Keith

    It is a lot easier to review the labs if it is clear to which modeule
    they belong.
    
    Lab. Ex. Logging in and out
    - Stick user and name together
    - Include an exercise with logging in on a remote system (maybe the
      same as used for exercise 1)
    
    Lab. Sol. Logging in and out
    - Give also the solution when an user logs in via a terminal server.
    - Output SHOW USERS in not correct since VMS version V5.2.
    
    Lab. Ex. EDT editor
    - First give the exercises about the EVE editor, while the EDT-editor
      is optional to teach (it's in the appendix)
    
    Lab. EX. EVE editor revisited
    - Include an exercise with journalling. Let the student press CTRL-Y
      and then recover the file.
    
    Lab Ex. Using the SHOW command
    - Does the student already know how to handle the HELP-utility?
    - Exercise 2 is too vague. Give direct exercise like
        with which SHOW command can I know which system are in the network?
        with which SHOW command can I know what time its is?
        with which SHOW command can I know which user there are on the
             system?
        with which SHOW command can I know what my terminal characteristics
             are?
        with which SHOW command can I know what my process characteristics
             are?
    
    Lab. Sol. Using the SHOW command
    - Please put the both solutions of exercise 8 on a new line.
    
    Lab. Ex. Subdirectories
    - Create an exercise about building up a directorytree, ie.
                         [STUDENTA]   
              _______________|______________
             |                              |
        [.WORK]                          [.PROGRAM]
                                   _________|__________
                                  |                    |
                              [.PASCAL]            [.BASIC]
                         _________|_________
                        |         |         |
                     [.SRC]     [.OBJ]    [.EXE]
    
        * Let the students go from their login directory to the directory
          [.BASIC]
        * Then go to the subdirectory [.WORK]
        * Then to the subdirectory [.SRC]
      This is a good exercise for using the command SET DEFAULT and the file
      spec. A lot of starting VMS users have problems with jumping in a
      directorytree.
    - Delete exercise 9. The theory of protections is not yet teached.
    - Reedit exercise 2 into Create some files in your subdirectory
      [.SUB1]
    - Delete exercise 5
    - Reedit exercise 7 into Create some files in your subdirectory
      [.SUB2]
    
    Lab. Ex. UIC based file protection
    - Include exercise 9 from lab. exercise subdirectories (deleteing the
      subdirectories [.SUB1] and [.SUB2].
    
    
    Lab. Ex. ACL based file protection
    - This exercises are not necessary for a "simple" application user. The
       whole theory can be skipped from the VMS for appl. users.
    
    Lab. Ex. Print
    - Rename the title of these exercises into Using VMS file specification
    - Include exercises with the copy, rename, delete commands
    - Delete in exercise 1 the words "using the generic print queue
      SYS$PRINT. Not each side has a generic queue SYS$PRINT
    
    Lab. Ex. Batch
    - This exercises do not fit in this course VMS for appl. users, because
      which "simple" appl. user will create command procedures and submit
      them. I think no appl. user., an adv. appl. user will do this.
    
    Lab. Ex. Mail
    - Put more exercise in it about extracting a message, replacing a
      message form wastebasket back to another folder, printing a message
      and using a distribution list
    
    Lab. Ex. Request
    - Skip this exercise. totaly useless.
    
    Lab. Ex. Login.com
    - Where does this exercise belong, which module.
      This exercises do not fit in this course VMS for appl. users, because
      which "simple" appl. user will create his own login.com.
      Thereby you have to talk about symbols, logicals and writing command
      procedure, again subject for an adv. appl. user.
      The exercise in itself is ok.
    
    
    Ed.

Hi Hannah,

I have a few labs about defining keys, symbols, logical names, writing "simple"
command procedures. My opinion is that these labs actually belong in the course
VMS for adv. appl. users.

Defining keys
=============
Define interactive or via a LOGIN.COM the next keys:
    key  |    definition
  -------|--------------------
    PF2  |    HELP
    KP1  |    DIRECTORY
    KP2  |    DIRECTORY/FULL
    KP3  |    SET DEFAULT 
    KP4  |    SET PROMPT = "> "
    KP5  |    SET PROMPT
    KP0  |    RECALL/ALL
   PERIOD|    RECALL
    PF17 |    erase the command line

Symbols
=======
1) Define interactive or via LOGIN.COM the next symbols:
    a. displaying the directory-listing with owner and size of each file in the
       default directory.
    b. displaying the system time
    c. displaying all the global symbols
    d. changing the default directory 
    e. jumping back to your login-directory

2) Test all your just defined symbols.


Logical names
=============
1) Create the subdirectories [.SUB1] and [.SUB2] beneath your login-directory.

2) Define the logical name HOMEDIR equal to your login-device and
   login-directory.

3) Check in which table the logical is placed.

4) Display the contents of a file in your login-directory, using the logical
   HOMEDIR.

5) Change your default directory to the subdirectory [.SUB1] and display the
   contents of a file in your login-directory, using the logical HOMEDIR.

6) Produce some error messages.

7) Try to pick up the error messages in a file. Display the contents of that
   file.


Command procedores
==================
Create a subdirectory [.COM] an place the next command procedures in this
subdirectory.

1) Write a command procedure UP.COM, which changes your default directory to
   the directory above your default directory.
   Define a symbol UP for runnning this command procedure.

2) Write a command procedure LOGOUT.COM, which purges all the file from the
   login-directory and the logs you off.
   Define a symbol for running this command procedure when you want to log off.

3) Write a command that asks for a filename, a file-extension and then in
   capitals displays the filename and file-extension.

4) Write a command procedure CD.COM, which changes your default directory to
   that one gave up.
   Define a symbol for running this command procedure, ie.
       $ CD  SUB1
    or 
       $ CD
       subdirectory: .....

5) Write a command procedure which displays the contents of a file gave up
   running the procedure via a parameter, otherwise the procedure has to ask
   for the filename
  
6) Write a command procedure which asks for a password. After three failures,
   the system has to log you off.   

7) Write a comand procedure which asks for an integer, to square the integer
   and then adds up 6. Display the result.

Ed.

    

Hello

As I promised, here is the translation of the lab we use here in Portugal
for the EVE editor. The lab is in two different files (EVE1.TXT and
EVE2.TXT). What we usually do is to send the first one by MAIL and tell the
students to extract it and then edit the file. The file itself is the exercise.
The second one is sent after the students have already begun editing the first
file. 

Hope this helps.

Regards,

Jo�o Paulo
Ed Services - Portugal





********************************************************************************
                            THIS IS THE FIRST FILE
********************************************************************************




               This text file will be used for the EVE exercise

The goal is that students be familiar to some basic EVE commands and know ho to
move inside the editor.




1. Start moving within the text using the arrow keys. Press <DO> key and enter
the command MOVE BY WORD and MOVE BY LINE. Use this commands in both FORWARD
and REVERSE directions (you can shift the direction using the <F11> key).


2. But if the text is too long you can use the <Prev Screen> and <Next Screen>
keys. Try also the commands TOP and BOTTOM to position the cursor at the
beginning and end of the text (remember that you can enter the commands pressing
the <DO> key).


3. If you want to return to a line in your text file many times during an
editing session you can define a MARK. Try to get the information about MARKS
from the HELP. Define a mark called "QUESTION 3" at the * sign; go to the
bottom of the text and return to the *.
*
To access the EVE HELP, enter <DO> and HELP MARK at the "Command:" prompt.


4. If you make a typing mistake you may want to erase a character, a word or a
whole line. To erase the character at the left of the current cursor position,
use the  <x| key. To erase a word or a line use the commands ERASE WORD and
ERASE LINE. The last word / line erase can be recovered by issuing the command
RESTORE WORD / RESTORE LINE. Some text for you to practice this:

	"Please do not erase this words I wrote"


5. Now we want to cut a few lines from the text and put them in another place.
First of all we have to position the cursor at the beginning of the area we want
to cut (use the arrow keys). Then press the <Select> key and move the cursor to
the end of the area. Press <Remove>. The lines are now stored in a temporary 
place called buffer (this one in particular is called "INSERT HERE BUFFER"). To
write those lines in some other place we only have to position the cursor there
and press the <Insert Here> key. Using this try to position question 3 after
question 4.


6. From here to the end you have an encrypted text. You have to make some
substitutions before you can read it. How to make this? Well, it is easy: enter
the command REPLACE and the system will prompt for the old string and the new
string. Then you will be asked weather you want to replace (type YES), not to
replace (type NO), replace all occurrences of the old string (type ALL), replace
this one and quit replacing (type LAST) or simply quit replacing (type QUIT).
Important: if you choose ALL, EVE will search for all occurrences of the string
in the current search direction and then it will search in the opposite
direction.
		OLD STRING		NEW STRING

	i.	GOOD MORNING		E
	ii.	XX			A
	iii.	O			<space>
	iv.	$			O

******Before a new substitution position the cursor here******



7. FINDOXXLLOTHGOOD MORNINGOW$RDSOINOTHGOOD MORNINGOTGOOD MORNINGXTOFILGOOD MORNINGOBGOOD MORNINGGININGOWITHOPLOXXNDOPLXXCGOOD MORNINGOTHGOOD MORNINGMOINOXXOBUFFGOOD MORNINGR
CXXLLGOOD MORNINGDO"PL*OW$RDS".OT$OCRGOOD MORNINGXXTGOOD MORNINGOXXOBUFFGOOD MORNINGROXXNDOT$OM$VGOOD MORNINGOFR$MO$NGOOD MORNINGOBUFFGOOD MORNINGROT$OXXN$THGOOD MORNINGR
SGOOD MORNINGXXRCHOTHGOOD MORNINGOHGOOD MORNINGLPOBUFFGOOD MORNINGROHGOOD MORNINGLP.OITOWILLOBGOOD MORNINGOGOOD MORNINGXXSIGOOD MORNINGROIFOY$UOCRGOOD MORNINGXXTGOOD MORNINGOTW$OWIND$WSOXXND
PLXXCGOOD MORNINGOXXODIFFGOOD MORNINGRGOOD MORNINGNTOBUFFGOOD MORNINGROINOGOOD MORNINGXXCHO$NGOOD MORNING.OT$OCRGOOD MORNINGXXTGOOD MORNINGOTW$OWIND$WSOUSGOOD MORNINGOTHGOOD MORNINGOC$MMXXNDOTW$
WIND$WS.OT$OM$VGOOD MORNINGOFR$MOXXOWIND$WOT$OXXN$THGOOD MORNINGROY$UOCXXNOUSGOOD MORNINGOTHGOOD MORNINGOC$MMXXNDSO$THGOOD MORNINGR
WIND$W,ONGOOD MORNINGXTOWIND$WO$ROPRGOOD MORNINGVI$USOWIND$W.OY$UOXXLS$OHXXVGOOD MORNINGOC$MMXXNDSOT$OGOOD MORNINGNLXXRGGOOD MORNINGOXXND
SHRINKOWIND$WS.OT$OC$MGOOD MORNINGOBXXCKOT$O$NGOOD MORNINGOWIND$WOINTGOOD MORNINGRFXXCGOOD MORNINGOUSGOOD MORNINGO$NGOOD MORNINGOWIND$W.


8. THGOOD MORNINGORGOOD MORNINGSTO$FOTHGOOD MORNINGOGOOD MORNINGXGOOD MORNINGRCISGOOD MORNINGOISOG$INGOT$OBGOOD MORNINGOSGOOD MORNINGNDOBYOMXXIL.OUSGOOD MORNINGOTHGOOD MORNINGOSPXXWNOC$MMXXNDOT$
CRGOOD MORNINGXXTGOOD MORNINGOXXOSUBPR$CGOOD MORNINGSS.OXXTOTHGOOD MORNINGO$OPR$MPTOINV$KGOOD MORNINGOTHGOOD MORNINGOMXXILOUTILITY.ORGOOD MORNINGXXDOTHGOOD MORNINGOMGOOD MORNINGSSXXGGOOD MORNING
WITHOTHGOOD MORNINGOSGOOD MORNINGC$NDOPXXRTO$FOTHGOOD MORNINGOGOOD MORNINGXGOOD MORNINGRCISGOOD MORNING,OGOOD MORNINGXTRXXCTOITOT$OXXOFILGOOD MORNINGOXXNDOL$G$UTOFR$MOTHGOOD MORNING
SUBPR$CGOOD MORNINGSS.ON$WOY$UOCXXNOINCLUDGOOD MORNINGOTHISOFILGOOD MORNINGOHGOOD MORNINGRGOOD MORNINGOWITHOTHGOOD MORNINGOINCLUDGOOD MORNINGOFILGOOD MORNING-NXXMGOOD MORNING
C$MMXXND.OWHXXTOW$ULDOBGOOD MORNINGOTHGOOD MORNINGODIFFGOOD MORNINGRGOOD MORNINGNCGOOD MORNINGOIFOY$UOHXXVGOOD MORNINGOUSGOOD MORNINGDOTHGOOD MORNINGOGGOOD MORNINGTOFILGOOD MORNINGOFILGOOD MORNING-NXXMGOOD MORNING
C$MMXXND?





********************************************************************************
                 THIS IS THE SECOND FILE OF THE EVE EXERCISE
********************************************************************************

                       


9. Using EVE you can define keys with EVE commands and then save those
definitions to a file and use them in every EVE session. To define a key use
the command DEFINE KEY and answer the questions. Define a key for the ERASE
WORD command and another one for the RESTORE WORD command. You can also define
a key for some other commands you use often: TWO WINDOWS, ONE WINDOW, NEXT
WINDOW, PREVIOUS WINDOW, etc. After defining some keys press the <Help> key;
EVE shows a keypad diagram with all the keys you have defined! and if you press
one of those keys you get help on that command! Store those definitions in a
file (get the information you need from the HELP). How could you have all the
keys you have defined in every editor session? 


10. Some typing sequences are repeated for several times in a editor session.
You can define a learn sequence and use it as many times as you want. Example:
if you are writing something and you want to place a title in the beginning of a
new chapter you can give the following commands:
                       
		<DO> LEARN
		type ---------------------------------------
		<DO> CENTER
		<RETURN>
		type TITLE
		<DO> CENTER
		<RETURN>
		type ---------------------------------------
		<DO> CENTER
		<RETURN>
		<Ctrl> <R>
		<F20>
In this example you associate those commands to the F20 key. A learn sequence
finishes with the <Ctrl> <R> keys.
The result will be this:

                   ---------------------------------------
                                    TITLE
                   ---------------------------------------