The files in this submission represent a set of procedures which are in use by the system manager at G. D. Searle. They are not striking examples of programming style nor are they warranted to work under all circumstances. They do however, behave as the author expects under VMS V2.2 on our 11/780. They all reside in [SYSMGR] and may even assume that [SYSMGR] is the default directory. Persons new to system management on the VAX may find them of interest just as a way of avoiding reinventing the particular utility. PROGRAMS: FORCEX is a program used to force an image with a known PID to exit. It is much cleaner than the brutal STOP/ID= , although as a pair they work out quite nicely. The user gets "ABORTED BY OPERATOR" status. HANGUP is a program which periodically hangs up remote lines that are not allocated to anyone. Very useful if you have a lot of dialup lines or inhouse port contention system that tweaks LOCAL/REMOTE bits. TAPECHECK is a tape verifier program designed for a TU77, although it shouldn't be too hard to modify for any particular drive. See comments in the source file for customization tips. COMMAND PROCEDURES: DISCOUNT is a procedure to total up the blocks allocated and the disk quotas on a given device. The information is derived from the quota file itself. MODQUOTA is a procedure to display and optionally modify a user's disk quota on his default device. Basically, it looks up the person's default device and UIC for you and then runs DISKQUOTA. MODUIC is a procedure which makes changing an accounts' UIC easy. It requires the program SETOWN from the FALL 1980 DECUS TAPE. It changes the UIC in SYSUAF, removes and enters a disk quota entry, and uses SETOWN to change the ownership of all the files. SEARLUSER is a procedure to automate the addition of user accounts to the System Authorization File. It reflects the account management policies of the author, but is easy to modify to your tastes. Questions or comments can be directed to: Jim Lellman G. D. Searle & Co. P. O. Box 5110 Chicago, IL 60680 These command files and programs were rather hurriedly documented at the last minute, for the most part, since it hadn't occurred to me that anybody might want to see them. By and large they are explained by the comments within the sources themselves. The command files have long names for documentation purposes, but in practice I define short symbolic names for use as foreign commands. Afterthought: some of the command procedures may assume the symbol SYS$MANAGER :== SYS$DISK:[SYSMGR]