TERMINALS 3.0 The TERMINALS program creates STATISTICS or a TABLE for terminal usage. A banner page is included with the statistical output that will describe some of the things that can destroy the integrity of the statistics. Refer to the .HLP file for more information on how to use TERMINALS. This program will only work with VMS 5.2 or higher and works with VMS audit files and not some batch routine that runs every 15 minutes to record what was being used at that time. If you need to recompile, Pascal 4.0 or higher will be needed or you will have to define the system routines yourself (CLI$ routines are already defined). The program will handle hard wired terminals, virtual terminals, network terminal connections as well has multiple terminal sessions created from terminals connected to a terminal server. Even rucks, mauls and an occasional scrum down. ******************************************************************************* Modifications since last release: 1. Internal program additions and modifications that are not visible to the user. 2. (new) Routine to test if input files are available before continuing to process. 3. (new) Error messages that go with system calls. 4. (new) Directory and device specification of audit files and terminal location files will be displayed on banner page when no directory or device specification is specified. (finds current directory and device settings.) 5. (fix) Pointer error if first two records extracted from the AUDIT files were related. 6. (new) Display on the banner page the date of found extracted data as well as the dates used in the inquiry of data. The following pages of statistical data will also display the dates of informa- tion found not searched. 7. (mod) New method of determining if no information was extracted from AUDIT files. 8. (mod) Added routine to extract trailing colons (seriously) for conformity among decwindows and all other terminals. 9. (new) /TABLE option to create a table of usage. 10. (new) Consolidate all remote computer system connections. 11. (new) /FULL qualifier to display terminals even if no information. 12. (new) /BRIEF qualifier to suppress output of terminals with no information. 13. (fix) Network connections are now handled. 14. (fix) /EXTRACT qualifier default. ** The program is internally documented with a section of modifications in the main program, as well as within the individual routines. I have tried to keep up the internal documentation as well as possible incase you need or want to make modifications of your own. ******************************************************************************* The included files in this directory are: BUILD.TERM - compiles and links program with options. TERM030.RELEASE_NOTES - this file you idiot. TERMINALS.CLD - the command language definition file. TERMINALS.DAT_EXAMPLE - an example file for location information. TERMINALS.EXE - the executable. TERMINALS.HLP - help file. TERMINALS.INFO_EXAMPLE - example information file. TERMINALS.OBJ - object file. TERMINALS.OPT - option file. TERMINALS.PAS - the source code, hoss. TERMINALS.STAT_EXAMPLE - example statistics output file. TERMINALS.TABL_EXAMPLE - example table output file. ******************************************************************************* Things to do to make this booger work: 1. Modify the file TERMINALS.CLD to reflect the proper image location and AUDITFILE default and the TERMFILE default. 2. Modify TERMINALS.DAT to reflect the proper terminal location information. THE FIRST TWO RECORDS OF THE FILE ARE NEVER USED SO THAT COLUMN HEADERS MAY BE DISPLAYED. It does not key in on any specific column, each record is free format as long as the terminal is first and the location second. It takes the first information as the terminal and the second as a location. The location has a maximum of 30 characters, the server has a maximum of 35 characters. 3. A setting of 10000 to 20000 for the WSEXTENT parameter in AUTHORIZE is recommended but may not be needed. This can be gauged by the amount of data that has to be processed. If you get an insufficient virtual memory error when running the program, you will have to boost this parameter even more. PGFLQUO may also have to be manipulated in the same way. 4. Start the auditing files. TERMINALS extracts and manipulates the data from the SECURITY AUDIT files. The command to get the needed information is: $ SET AUDIT/ALARM/ENABLE=(LOGIN=(ALL),LOGOUT=(ALL)) This will then be set up permanently, unless you change it of course. For more information concerning this command, consult your local set of VMS manuals. Variations on this command are acceptable, TERMINALS locates the 'LOCAL' type of logins and logouts. This command will create a file: SYS$COMMON:[SYSMGR]SECURITY_AUDIT.AUDIT$JOURNAL We close this file daily and put it into the directory: SYS$COMMON:[SYSMGR.AUDITVMS] To close the file, use the command: $ SET AUDIT /SERVER=NEW_LOG 5. If you are working with large data files, you may wish this to run in batch with all desired qualifiers. ******************************************************************************* Important information: 1. The audit files will have two entries for each terminal, a login entry and a logout entry. If one entry cannot be found, the program will compensate by putting the login or logout (whichever is missing) into the file. The program assumes that the user was either logged in at the beginning of the shift or until the end of the shift. It may be possible that the user was logged in before or after these times, but since a dropped session is more likely the case, I chose to limit excluded data by shifts. The shifts are: 00:00:00.00 - 07:59:59.99 shift1 08:00:00.00 - 15:59:59.99 shift2 16:00:00.00 - 23:59:59.99 shift3 2. The program will display inclusive dates. If the qualifiers /BEFORE and/or /SINCE are used, these dates will make up the begin and end dates. If these qualifiers are not used, the program will display the earliest and/or latest dates that it encountered. 3. The program will create several temporary files in the area that the program is being run. These files are deleted as they are no longer needed. If the program is rudely interrupted during execution you will have to delete these files on your own. The program only deletes the most current version of the temporary files. ******************************************************************************* Future of TERMINALS: I am looking into providing more information for windowing terminals. If you have any information, concerning these two topics, I would be very grateful. I have not had much luck with this topic in concerns with accounting. ******************************************************************************* Problems, Questions & Suggestions: Jonathan C. Baker Naval Surface Warfare Center Code N86 Dahlgren, VA 22448-5000 703-663-8705 Mailer address: system_jb@128.38.14.201 system_jb@unode1.nswc.navy.mil