[KMSKIT.SYSMGR.CMDFIL] This directory contains command files we have found to be of general use for system management. Typically all command files reside on SYS$SYSROOT:[SYSMGR.CMDFIL]. Many command files assume that TESTFILE is defined as a foreign command, ie TESTFILE==@SYS$SYSROOT:[SYSMGR.CMDFIL]TESTFILE.COM. Help files are supplied for command files as appropriate. 1. BROADCAST. Emulates the RSX BROADCAST command. User needs OPER privilege for it to use REPLY for sending messages. 2. CMD. Starts up command files on SYS$SYSDEVICE:[SYSUTL] and passes them command lines. 3. ERRORDSP. Quick and dirty to display the error message associated with a VMS error number. If defined as a foreign command, type ERRORDSP , or if using the CMD procedure, CMD ERRORDSP to see why VMS is rejecting your efforts. 4. JNLBACKUP. Provides an easy way for users to back up their files. Creates a journal file of files backed up and a directory log file of all kinds of things (tape name, backup set name, tape number, backup date range, errors encountered on tape, etc). Insures that all backup sets have unique names. Nifty. 5. LARGE. Puts V100 in 80 column mode & width =80. 6. PAGE. Erases the screens on a variety of terminals. 7. SMALL. Sets VT100 to 132 colum mode and width=132. 8. SPR. Automatic SPR generator for VMS and RSX. This is neat. SPR administration will take SPRs prepared this way if you staple them to a blank SPR form. Maybe someone could modify it to run without operator intervention. Start it up at night, come in in the morning and find a neatly typed list of SPRs describing all current system problems known and unknown. However, until then, you do have to type in the problem but editors are so much more fun than typing a multi-part form!! 9. SYSTARTUP. Example of the command procedure used to bring up our system. This is included because it represents a very clean formalism for booting the system. SYSTARTUP.COM does very little except execute a series of @SYS$SYSROOT:[SYSMGR.SYSBOOT]cmdfile commands. All command files as they start print out a heading of the form CMDFILE -- text-describing-action-being-done The "--" and text from each command file line up. Only if errors occur does anything else get printed out and then the system manager knows exactly where the problem occured. An example of our SYSTARTUP.COM is on this directory and a few sample command files are on [KMSKIT.SYSMGR.SYSBOOT]. 10. TERM. Used during SYSLOGIN to find out the type of terminal in use. Writen for V2.x prior to being able to find out info using GETDVI. 11. TESTFILE. Emulates the .TESTFILE on RSX. Faster (by far) than using an image to check for the existance of a file. 12. UTL. Automatically starts up tasks on [SYSUTL] and passes them command lines. Saves having a zillion foreign commands. 13. XQT. Simulate the RSX .XQT command.