  
 		ACCOUNT FILE MAINTANENCE
 HELP on specific topics is available by typing
 HELP $ACCOUNT keyword, where keyword is one of the following.
 
	COMMANDLINE	COMMANDLINE for the ...RSE program.
	ERROR 		Error messages for the enhancements.
	ERROR		Error messages for ACCLOG.
	ERROR BYE	Error messages for BYE.
	ERROR HELLO	Error messages for HELLO.
	ERROR INSTALL	Error message from INS.
	ERROR RESET	Error messages for RESET.
	ERROR TRUNCATE	Error messages for TRUNC.
	ERROR UPDATE	Error messages for UPDATE.
	ERROR WHO	Error messages for WHO.
	LOG		Getting a ACCOUNT status report.
	MAIL		Using the MAIL utility
	MAIL SEND	Sending mail to another user
	MAIL RECEIVE	Receiving mail sent by yourself or another user.
	SET BLOCKS	Setting the users allowed number of disk blocks.
	SET PRIVLEGES	Setting the users privleges.
	SET TASK	Setting a task to run after logon.
	RESET		The account maintanance program RESET(/Task=...RSE).
	RESET ALL	Resetting the LOGON TIME, LOGON FLAGS, LOGON NUMBER(all accounts).
	RESET FLAGS	Resetting the ACCOUNT BUSY FLAGS.
	RESET LOGONS	Resetting the number of logons(all entries).
	RESET TIME	Resetting the LOGON TIME(all entries).
	UPDATE		Updateing the users disk block usage.(...UPD).
	WHO		Finding out who is on the system.
  
  
1	LOG
 READING THE TOTAL LOGON TIME, THE # OF LOGONS, THE PRIVLEGE MASK, and the TASK
 	To read the status of the account file at any time , type  RUN  $ACCLOG
 ACCLOG is a task which will provide a printed record of virtually every item in 
 the account file with the exception of the password, the system device, and the 
 date and time of the last logon.  In addition it indicates which accounts are 
 currently in useby flagging an active account with the terminal number logged  
 onto the account.  This entry is of the form TTn.
 
1	MAIL
	Users may leave messages for themselves or other users by
	means of an intra-user MAIL utility, MAIL.  When a user logs
	on he/she is notified if ther is any mail waiting to be looked at.
 
			>>>YOU HAVE MAIL<<<
 
	Immediately following logon, or any time thereafter, a user may
	request that mail be displayed at their termina.  The user is
	given the option of having the MAIL.TXT file entered into their
	directory at that time or deleting the MAIL.  The directory
	entering operation only works if the user's SY: is LB1:.  Further
	HELP on using the MAIL utility may be requested by typing
	HELP $ACCOUNT MAIL keyword     where keywords are
 
		SEND		Sending mail to another user.
		RECEIVE		Receiving mail from another user.
 
2	RECEIVE
	A user who is notified that he/she has MAIL waiting, may receive
	mail by typing MAIL ME, or  ME in response to the  TO WHO?  prompt.
	The user is given the oportunity of retaining the mail by having
	it entered into their directory on LB1:.  Otherwise, the MAIL is
	"burned" after reading.  If the user's  SY: is not LB1:, his mail
	can never be saved(regardless of what MAIL says).  When the system
	prints out the MAIL message it prefixes it with the date it was sent,
	the UIC of the sender, and the sender's last name.
 
2	SEND
	MAIL may be sent to another user by either typing
 
			MAIL username
		or
			MAIL
 
	If 'username' is omitted, the SYSTEM prompts for the name with
	TO WHO?, at which time the 'username' is entered.  The SYSTEM will
	inform the user if the 'username' does not represent a valid account.
	If the 'username' is accepted the SYSTEM prompts with MAIL>, at which
	time the user may type in up to 80 characters followed with a carriage
	return.  Text lines may be entered in this manner until done, at
	which time the user enters a Control Z(^Z) to signify the end of
	the MAIL file.
		Valid 'username's are either the user's last name or
	their account number specified as [GGG,MMM],[GGG/MMM], or
	GGG,MMM.  The correct user name must be known to send MAIL.
  
  
1	RESET
 The task RESET is used to RESET the account file(#logons, terminal
 connect time, account busy flags).  It must be run with the UIC=[1,54].
 It must be installed as ...RSE (for RESET).  For help with the command line
 for RSE, type HELP $ACCOUNT COMMANDLINE.
2	TIME
 RESETING THE TOTAL LOGON TIME(ALL ENTRIES)
 	This entry is zeroed or reset using RESET
  
 			INS $RESET
 			RSE TIME
 			REM RSE
  
2	FLAGS
 RESETTING THE ACCOUNT BUSY FLAG(ALL ENTRIES)
  
 	In rare cases(system crash, etc.) it is possible for the system to
 stop without a user logging off.  In this event the flag entry in the account
 file of the form  TTn is not cleared.  This means that a non-privleged user
 may not log on until this flag in his section of the account
 file is cleared.  This is accomplished using
  
 			INS $RESET
 			RSET FLAGS
  			REM RSE
  
 All non-privleged users should be off the system when this is done since
 all terminal flags in the account file will be zeroed together.  This will
 not adversely effect a privleged user who is logged on.  A non-prvleged user
 would not get screwed up, but upon logging off, the accumulated terminal time
 for his session would not get added into his account.
  
 RESETTING THE ACCOUNT BUSY FLAG FOR JUST ONE USER
 	Install RESET,   then enter the command string
  
 		RSE USER=NAME:PASSWORD/FLAG
  
 where NAME is the user's last name(in the account) and PASSWORD is the user's
 password.  Only the user's account busy flag will be reset.
  
2	LOGONS
 RESETTING THE TOTAL NUMBER OF LOGONS ENTRIES
 	This is accomplished using  RSE.
  
 			INS $RESET
 			RSE LOGONS
 			REM RSE
  
2	ALL
 RESETTING ACCOUNT FLAGS, # OF LOGONS, AND LOGON TIME AT ONCE
 	For ease in monthly reseting of the account file, the account
 flags, the # of logons entries, ad the total terminal connect time
 entries can be all zeroed out with one command.
  
 			INS $RESET
 			RSE ALL
 			REM RSE
  
1	SET
2	PRIVLEGES
 SETTING AND CLEARING THE PRIVILEGE MASK WORD
  
 	At present the first three BITS and BIT 15 of the PRIVLEGE MASK word
 in U.PRV1 of the terminal UCB are defined.
  
 	BIT	0	User may not use the RUN command
 	BIT	1	User may only run tasks owned by him or by [377,377]
 	BIT	2	A task(6 letter name) in the account file will be run
 			as HELLO exits.
 	BIT	3	When set the user's terminal is logged on SLAVE.
 	BIT	4	When set, the non privleged tasks are not aborted on logoff
 	BIT	6	When the user logs off BYE sends an MCR command to ...UPD
 			to update the user's account file to reflect the number of
 			files and disk blocks in use on that account.
 	BIT	15	The user is logged on as privleged even if his UIC is 
 			nonprivileged
  
 The PRIVLEGE MASK word is set using
  
 			RSE USER=NAME:PASSWORD/PRIV=NNNNNN
  
 	where NNNNNN is a 6 character octal number.
  
 cleared using, 
  
 			RSE USER=NAME:PASSWORD/PRIV=
  
2	TASK
 INSERTING A TASK NAME INTO THE ACCOUNT FILE
  
 	Inserting a task name into the account file is done using
  
 			RSE USER=NAME:PASSWORD/TASK=XXXXXX
  
 where XXXXXX is a 6 character ASCII task name.
  
2	BLOCKS
 SETTING THE NUMBER OF BLOCKS THE USER IS ALLOWED TO USE
  
 	The account file has an entry for the number of blocks the user is  
 allowed to use.  When the user logs on, HELLO checks to see if this number has 
 been exceeded.  If it has, HELLO prints a warning message at the terminal.
 To set the number of blocks the user is allowed to use the syntax is
  
 			RSE USER=NAME:PASSWORD/BLKS=NNNN
  
 where NNNN is a decimal number.
  
  
  
  
1	COMMANDLINE
 		THE ACCOUNT FILE UTILITY -- RESET
  
 	The ACCOUNT FILE utility, RESET, installed as ...RSE (for RESET)
 supports the following syntax in its command line.
  
 		RSE COMMAND[=qualifier]/SW1[=XX]/SW2[=ZZ].....
  
 The allowed commands are
  
 				FLAGS
 				TIME
 				LOGINS
 				ALL
 				USER
  
 Of these commands only the last command, USER, requires a qualifier.   It's
 syntax is
  
 			USER=name:password
  
 where the ":" is required syntax to seperate the user's name from his password.
 Also the USER command requires one or more switches.  Three switches exist
  
 			/TASK=XXXXXX
 			/PRIV=NNNNNN
 			/FLAG
 			/BLKS=NNNN
  
 In all cases the account file entry is set by following the "=" with either
 a task name or octal or decimal digit, or reset by not following the "=" 
 with anything.  The switch /FLAG need not be followed by anything.  If present 
 the user's account busy flag is cleared.
  
  
1	UPDATE
 UPDATING THE USERS ACCOUNT WITH THE NUMBER OF FILES AND BLOCKS IN USE
  
 	If BIT 6 in the terminal PRIVLEGE MASK (U.PRV1) is set BYE sends a
 message to UPD to update the users account with the total number of files
 and blocks the user had on his system device when he logged off.
 The format of the message is
  
 			UPD DEV:[UIC]password/UP
  
 For this procedure to work the task UPDATE (Account for disk block usage) must
 be installed as ...UPD.  UPD may be run at any time by any user to find out the 
 of files and blocks on use by any account.  However, if the desire is to update
 the account file [0,0]RSX11.SYS, then UPD must be run from a privleged terminal
 and both the password and the /UP switch must be present.  The /UP switch is to
 safegard UPD from accidental use by a privleged.  The non privleged account
 account syntax requires that the password and the /UP switch be omitted.
 However,  a privleged account might accidently type a file specifier after the
 [UIC].  The/UP switch is to insure that aything following the [UIC] is intended
 and justifies reading through the account file to search for a match.
 Finally, ...UPD will not UPDATE an account of a privleged UIC regardless of
 the setting of BIT 6 in U.PRV1.
 
1	WHO
	To quickly find out 'who' is on the system type
 
			WHO
 
	The information displayed is the user's LOGON UIC, Terminal Number,
	First Name, and Last Name.
 
		[GGG,MMM]  TTn	Firstname    Lastname
 
	For a nonprivleged user, the LOGON UIC will be their Current UIC.
	A privleged user, however, may have changed their UIC to other than
	the initial LOGON UIC.
 
1	ERROR
 
	Request HELP on error messages using the keword specific to the program
	giving the error message, ie.
 
		HELP $ACCOUNT ERROR keyword
 
	where keyword is ACCLOG,BYE,HELLO,RESET,TRUNCATE,UPDATE, or WHO.
 
2	ACCLOG
  
	ACCLOG -- ACCOUNT FILE OPEN FAILURE
		The account file, LB0:[0,0]RSX11.SYS, could not be opened.  Either
		the account file is busy(try again), LB0: is dismounted or offline,
		or the file is locked.  The file only will get locked if the system
		or an account file task crashes while the file is being updated.
	ACCLOG-- ACCOUNT FILE READ ERROR
		A FCS error was detected during a read operation.  If ACCLOG gets
		part of the way through the file, a parity error on the disk(bad block) 
		may have developed.
 
2	BYE
 
	BYE -- STILL LOGGED ONTO FIRST TERMINAL?
		Privleged users with UIC group numbers <=10, may if they
		so desire log onto more than one terminal at a time on the
		same account.  However, only the first terminal logged onto
		is marked with the Account Busy Flag.  The second and subsequent
		terminals logged onto have no flag set.  When BYE finds no flag,
		it logs off the terminal and reminds the user he may be logged
		on elsewhere also.
	BYE -- ACCOUNT FILE BUSY -- TRY AGAIN
		The account file could not be opened, most likely it was busy.
		See also discussion of ACCLOG error messages.
	BYE -- PRIVLEGED LOGOFFS DISABLED
		BYE will not let a privleged user logoff if logons are disabled.
	BYE -- ACCOUNT READ ERROR -- GET HELP!
		The system can't read the account file.  See also discussion of
		ACCLOG errors.
	BYE -- ACCOUNT FILE LOCKED -- TRY AGAIN
		When the account file was opened it wasn't locked.  When BYE went
		out to actually write to the file, it found the file locked.  More
		than likely, someone flipped on the write protect switch on LB0:
 
2	HELLO
  
	HEL -- MULTIPLE LOGONS ILLEGAL
		Only a bonifide privleged user with a group number <=10 may log onto
		more than one terminal at a time on the same account.
	HEL -- REQUESTED TASK NOT FOUND -- LOGGING OFF
		If a task is specifed in the account file to be run at logon and
		either the task is busy, or not found(not installed), this message
		is displayed.
2	RESET
 
	RESET -- ACCOUNT FILE WRITE ERROR
		An error occured in writing the account file.  Most likely
		only one block(4 accounts) are corrupted, but who knows?
	RESET -- ACCOUNT FILE READ ERROR
		Problems reading file. See explanation under ACCLOG.
	RESET -- ACCOUNT FILE BUSY
		Account file locked either because in use, or because improperly
		closed.
	RESET -- COMMAND SYNTAX ERROR
	RESET -- COMMAND ERROR
		The command to reset is not syntactically correct.
	RESET -- COMMAND WORD NOT RECOGNIZED
		An unrecognized keyword has been used.
	RESET -- ILLEGAL OCTAL VALUE
		Numbers between 0 - 7 only.
	RESET -- MISSING PASSWORD
		The password is required if the USER=NAME:PASSWORD  form of
		a command line is used.
	RESET -- ILLEGAL DECIMAL NUMBER
		Non-numeric character detected.
	RESET -- ALL ACCOUNT BUSY FLAGS RESET
	RESET -- ALL TOTAL LOGIN TIME ENTRIES ZEROED
	RESET -- ALL # OF LOGINS ENTRIES ZEROED
 
2	TRUNCATE
 
	SYNTAX ERROR		Invalid command line
	FCS ERROR nn		An FCS error number nn occured.
	NO SUCH FILE		The file specified in the command line does not exist.
2	UPDATE
 
	UPD -- SYNTAX ERROR
	UPD -- BAD DIRECTORY NAME
		[GGG,MMM] was not a valid UIC.
	UPD -- DISK OPEN ERROR NN
	UPD -- DISK WRTE ERROR NN
		An FCS error number NN was detected during a READ or
		WRITE.
	UPD -- ACCOUNT NOT UPDATED, ACCOUNT FILE BUSY OR LOCKED
	UPD -- ACCOUNT FILE READ ERROR, GET HELP!
	UPD -- ACCOUNT FILE WRITE ERROR, GET HELP!
	UPD -- ACCOUNT NOT FOUND
		The account specified in the command line could not be found.
	UPD -- PRIVLEGE VIOLATION
		A non-privleged user is not allowed to use the /UP switch
 
2	WHO
 
	See the error messages for ACCLOG.  WHO's messages have identical 
	meaning.
 
2	INSTALL
 
	INS -- PRIVLEGE VIOLATION - RUN COMMAND NOT ALLOWED
		The user is prohibited from using the RUN (INS/RUN=REM)
		command.
	INS -- PRIVLEGE VIOLATION -TASK OWNERSHIP
		The user may not run tasks which he doesn't own.
