[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference koolit::vms_curriculum

Title:VMS Curriculum
Moderator:SUPER::MARSH
Created:Thu Nov 01 1990
Last Modified:Sun Aug 25 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:185
Total number of notes:2026

63.0. "SYSNET I CHAP 12 REVIEW" by SUPER::REGNELL (Smile!--Payback is a MOTHER!) Tue Mar 19 1991 14:38

    
T.RTitleUserPersonal
Name
DateLines
63.1View from the UKUKEDU::SHONEKeith Shone @RKA 830-4074Fri May 10 1991 13:1428
   Module: Managing System Users

   My views - not necessarily those of my colleagues.

    
   Page	    Comment

   1-3	    A little rephrasing and typo fixing needed, I felt:

	    "In this chapter we start tying together some of the
	    bits and pieces of information that you have been
	    learning, to show how all the parts relate..."
   
   1-7a	    sub-head 4.: for manual read module?

   1-8	    Callout 4: Look at that date - positively prehistoric!
   
   1-9	    Don't think the NOTE adds anything to the foregoing text
   
   1-15	    Line 5: "The following comments are keyed to Example 1-4"
	    - are they, where?
   
   1-19	    Line 3 of para "Responding to User Requests": typo
	    opertaor -> operator

	    Next line: typo suntaxes -> syntaxes (Freudian slip?)

   1-22	    Didn't see specifics on: access mode or CLI tables
63.2Chapter 12 ViewsDLO10::TARLINGMon May 13 1991 16:0810
    Val, et all;
     
    1. Page 1-15, The "outcalls" in example 1-4 seem to have been left out!
      
    2. Page 1-18, Changing a process priority only requires "ALTPRI" when
       you wish to chage to a priority higher than your base priority.
       Also, if the PID is not your own you need GROUP or WORLD privilege.
      
    Arnold.
    
63.3view of HollandNWGEDU::WIERSMADrive a BENTLEY or walk...Mon May 20 1991 18:061
    
63.4GOONS::BAKERWhat does "ignorant" mean?Wed May 22 1991 11:40123
Review comments for the Managing System Users chapter. Good content again.

Stephen
--------------------------------------------------------------------------

1-3		Typo:  tieing = tying
		2 missing <REFERENCE>s.

1-5a		Missing <REFERENCE>
  Penult. para	"Example 1-3" should really be "Example 1-1"

1-5 1st bull	I don't think that this item has anything to do with the
		"user's environment".

1-6  Title	The title "Displaying a User Record" implies that we're going
		to be told the UAF command to do this. We only get the output
		shown.  Suggest using a different title or add the appropriate
		UAF command.

		Also, example 1-3 should be 1-1.

1-7 Table	SYSMAN commands crept into the UAF command sequence.
		Suggest moving them after UAF> EXIT

		UAF> ADD SMITH.../UIC=[ADMIN,SMITH]  won't work. The
		identifiers ADMIN and SMITH must be present first. Yeah, I know
		the comments say this, but I doubt that this is ever the case.

		Suggest changing the example to ".../UIC=[11,15]" and removing
		the relevant text from the comments.

1-8 Example	Looks like the issuer had non-default message display format.
		The authorize messages are usually seen preceded by "%UAF-I-"

		Query use of EASYnet nodenames again

		The logging in example is inaccurate with 5.4.  Creating a new 
		account will cause the initial password to be expired.
		Therefore the user gets prompted to change it upon logging in.

1-9a  2nd para	I think "..system manager's login file" should be "..system
		wide login file"

1-9  The note	I don't think the note is necessary. All that it says seems to
		have been said elsewhere on the page.

1-10. 2nd line	The callouts are also keyed to table 1-3

1-11 Table	I think the last column (key) would be better as the fist
		column. Suggest rearranging the table.

		Title of "Key" column. Suggest "Key to Example 1-3"

	Password entry: The work OPEN is in capitals. 

	UIC entry. Last line.
		Suggest rewording thus: "(UIC will be displayed in a numerical
		form and possibly character string form as well)"

1-12 Table	Key column position and title as above.
	LGICMD entry:  text says "The manager typically assigns the same login
		file to all members of a group, or to all users on the system".
		I query whether this really is "typical". Suggest changing
		"typically assigns" to "can assign".

	Prim/Second day entry: Suggest putting a reference to Table 1-4 here.

	Limits entry.  Suggest making this "Quotas and Limits"
		Typos:  /TQELm = /TQELM and /ASTLm = /ASTLM

	Privileges entry: The sentence "Privileges to add to user record or
		remove from user record" seems out of place. I suggest that it
		is not needed here and can be removed.

1-13  Table, /NETWORK entry. Function text says "...network batch.." Suggest
		removing word "batch".

1-14  End of point 3:  Suggest slight rewording

	"..(/DEVICE) qualifier).." = "..(with the /DEVICE qualifier).."
	"..(/UIC) qualifier).." = "..(with the /UIC qualifier).."

1-15 2nd para	Says points are keyed to Example 1-4.  They're not!  Suggest
		adding callouts to the example and listing them in place of 1,
		2, 3 and 4.

     item 2	Missing <REFERENCE>.  Will students have found this command
		procedure before now?

     Example	As before, the UAF messages are missing preceding "%UAF-I-"

1-16a 		Missing <REFERENCE>. I suggest the sentence following it reads
		"..gives an overview of the methods the VMS operating system
		provides for the system manager to regulate processes."

1-16  Limits section, 1st sentence.  Suggest adding "They:" to the end.
		      1st bull.  This has just been said in the previous
				sentence, I suggest removing the item.

1-18  Table. Chg Base Prio:  Suggest further qualifying the need of ALTPRI priv
by adding "to change the base priority above the authorized value" to thelast
sentence.

1-19a	Last para.  Missing <REFERENCE>.

1-19 2nd para:	Typo: braodcasts = broadcasts
     Next sent.  Suggest rewording "To send a message to a user or users enter
				    one of the following commands:"

     "Responding..." para.
		Typo:  opertaor = operator
     Next line:	Typo:  suntaxes = syntaxes. I think "command" would be better.

1-21  Title 	"... and User TAPES"  I think the user is TAPEOPR. (See first
		OPCOM message)

		Also change all example labels for "Tapes:" to "Tapeopr:"

1-22  1st bull	Nit:  "Defines" = "defines"
      7th bull  Suggest changing to "Quotas and limits"
     10th bull  Suggest "Access times".  Mode could confuse with Kernel, Exec,
		Super and User at some stage.
63.5detached process info sourceTEACH::CHUCKSat Jun 01 1991 01:5717
         	module 12:  Page 1-10 & 1-11 should face each other.

         		    Page 1-10.a or 1-11.a  Could you add a
         		    detailed explanation of how the character
         		    string form of the UIC is developed & how
         		    it can be changed.  This question is always
         		    asked and I have not found a complete answer.

         		    Up through page 1-15 the only authorize commands
         		    that are mentioned are ADD, REMOVE & EXIT.
         		    I would like to see at least MODIFY added.
         		    (more than # 1 on page 1-15)

         		    Page 1-13  If you do not put examples here
         		    of how to set up the hours, it will be a
         		    road block each week.  There is a good example
         		    in chapter 2 of SYS. man. I.
63.6Comments from DC Training CenterTEACH::WENDYMon Jun 03 1991 13:2234

                                 module 12
                        Managing System Users

1-5
   As mentioned in the first chapter, the UAF is used to define a user's user
   name and password.  It is also used to define much of the user's enviornment
   such as:

   .Specifying who may use the system by adding users *(this has nothing to do
   with defining the users enviornment)

   .Setting limits on other resources *(like working set size)
   *( maybe mention some other things they have heard of like UIC's)

1-7 Maybe have this page as a summary since it shows you everything.

1-8 Step #2 Diskquota
    You show them how to put an entry in diskquota, but you never show them
    how the utility works and this will force the instructor to address the
    utility now. You also assume diskquota is enabled.

1-9 2. A group login command procedure

       .If this is left blank, the VMS system looks for the next possibility.
       *(What does this tell the student. What is the next possibiliy??)

1-14  Step 3 I think Diskquota should be incleded in here or taken out completly

1-15 Again you mention Diskquota
        
Wendy Mullenhoff

63.7Capitol IdeasTEACH::LYNNSun Jul 07 1991 00:2745
	Managing System Users
	Chapter 12


Objectives	Why not cover Disk Quotas completely in this chapter?
		That would be one loose end you never have to worry with
		in later chapters or courses. The student will see it in
		lab and ask all the questions you have to lecture on
		at a later time.
		Bullet 5. Was restrict the abilities of certain users
		or applications really covered?

1-6	To avoid confusion for the new student make the "Account" and the
	"UIC" match. That is:
	Account: ADMIN     UIC: [11,2] [ADMIN,SMITH]

1-8a	Add to the instructor's page that students should watch the
	messages being returned from the authorize utility. They are
	telling you want files you are actually writing to with your
	request.

1-8	Once again - Make the /ACCOUNT field match the UIC identifier.

1-10	Read page 1-6 comment.

1-11	Why mention open accounts at this level of instruction?

1-13	If you are going to include this table give examples.  The page
	just seems to appear and then disappear.

1-14	When you remove a user I was always told the steps had to be in
	this order.

1-18	The section Changing the Base Priority
	You don't show an example of using the process name but the
	first sentence makes reference to one.  Include one for this
	section.

1-19	First sentence after "Sending Messages to Users"  Typo 
	"braodcasts" should be "broadcasts"

1-22	Fourth word should not be captialized.

Lynn White
Washington D.C.
63.8Wrong objectiveTEACH::CHUCKThu Feb 27 1992 17:535
    This topic is now chapter 14.
    
    In the objectives on page 14-3, the last objective is not covered
    in this module.  It should be removed. (the one about communication
    with users).