AAREADME.DOC Advanced Users Login Utility: LOGIN V2.0-01 VAX/VMS: V3.x (origonally edition) V4.1a (compatable distribution) VAX11-C: V1.4 (origonal edition) V1.5 (compatable distribution) Address comments, questions, large sums of cash and/or goods to one: - Thomas Charles Gray TDB Systems Development VOLT Delta Resources, Incorporated. 2323 West Lincon Avenue Anaheim, California 92801 This distribution contains a login-time utility, LOGIN, which was designed to expidite access to user accounts by defining (presumably) all logical and symbols from within a single image (as opposed to the DCL utility) and to allow easy modifications of these tables. Also provided is a brilliant login page describing all of the traditional garb on your newly created process --virtually everything you need to stimulate your ego into oblivion during those long login waits on your favorite VAX. LOGIN was origonally written in MACRO to run on a large (!) timesharing VAX-11/780 (where DCL is commonly refered to as Discusting Common-Language for its speed), and was rewritten in FORTRAN at a later point in time to improve source maintainability, user-friendliness, and author-sanity. This latest release is written entirely in C to take advantage of all of the benifits (datastructures!) of this (relatively) new and (subjectively) exciting language. Due to copyright problems, the MACRO and FORTRAN versions cannot be released. (You'll just have to bug management to buy "that C compiler everyone is talking about.") --BLISS32 users, forgive me, I am being held hostage at a site without the compiler! I have this up and running under V4.1a (8600 version of V4.1) right now . . . a version taking advantage of the new facilities of V4 (ie, $CRLNM) is underway. . . To setup LOGIN in a user account, do the following - $ SET DEFAULT SYS$LOGIN $ CREATE/DIRECTORY [.ACCOUNT] $ SET DEFAULT [.ACCOUNT] ! !Setup your LOGICALS.CAT, SYMBOLS.CAT, CONSTANTS.CAT, ! DIRECTORY.CAT, and HARDWARE.CAT files ! by creating the files in an editor with the ! following format: ! ! [[defineetranslation],...] ! ! Example: ! LOGICALS.CAT ! MAINSYS$LOGIN ! DOCUMENTSMYDISK:[ME.DOCUMENTS] ! $ EDIT LOGIN.COM ! ! Add the following lines... ! $ ASSIGN mydisk:[me.ACCOUNT] ACNT $ LOGIN :== $ACNT:LOGIN.EXE $ LOGIN Usage - $ LOGIN [SUBPROCESS|NETWORK|BATCH] If no parameters are specified, LOGIN assumes a context of interactive process. If SUBPROCESS is specified, LOGIN performs only logical and symbol definitions (great for All-In-One's OAINI procedure). If BATCH or NETWORK are specified, no accounting or user display is performed, however logical and symbol definitions are made. One of these days I will add a $GETJPI item to find out how LOGIN is being invoked without requiring a parameter. Distribution - AAREADME.DOC ....... This file DECCRT.H ....... VT screen stuff LOGIN.C ....... VAX-11 C Source for LOGIN LOGIN.OBJ ....... VAX-11 C Object for FORTRAN low-lifes LOGIN.EXE ....... V4.1A (8600ized V4.1) image file LOGINMSG.MSG ....... VMS Message Utility Source File LOGINMSG.OBJ ....... VMS Message Utility Object File LOGICALS.CAT ....... Sample LOGICAL.CAT file SYMBOLS.CAT ....... " SYMBOLS.CAT " DIRECTORY.CAT ....... " DIRECTORY.CAT " HARDWARE.CAT ....... " HARDWARE.CAT " Rebuild - To rebuild LOGIN from sources ... From a directory containing DECCRT.H . . . $ CC LOGIN $ MESSAGE LOGINMSG To rebuild LOGIN from objects ... $ LINK LOGIN,LOGINMSG