Prime Time Monitor Installation Guide The Prime Time Monitor is a set of three executable images, plus a database, which can be used to control the length of interactive sessions. The three images are: The Prime Time Monitor (PTM) which is run as a detached process. This process monitors all interactive processes and controls the length of the session using information in the database. The file must reside in then SYS$SYSTEM: directory. The Prime Time Control Program (PTC) is used to start/stop the PTM and to create and modify the database. This file should reside in SYS$SYSTEM:, for simplicity sake, but it is not necessary. The Logintest routine is run each time a user logs into the system and controls login ability. This file should also reside in SYS$SYSTEM: but again it is not necessary. The database consists of four permanent files, one temporary file (only exists when the monitor (PTM) is actually running), and a mailbox used for communication between the monitor and the control program (PTC). An additional log file is kept to record significant events in the PRIME TIME system. The files reside in a directory by the name of MANAGER:[PTDATA], and the mailbox is referenced by the logical name PTC$MAILBOX. The PTDEFAULT.DAT file contains the following information: 1) PRIME TIME SLICE, the amount of time a user can be logged in. 2) WAIT TIME, the amount of time a user must wait to login. 3) THRESHOLD, the amount of time which a user can be logged in and be allowed to login again without waiting. 4) SYSTEM GROUP, usernames with group numbers less than or equal to this value are immune to prime time monitoring. 5) SYSTEM PRIVILEGE GROUP, usernames with group numbers less than or equal to this value have access to all monitor control commands. 6) LIMITED PRIVILEGE GROUP, usernames with group numbers less than or equal to this value have access to some monitor control commands. 7) NUMBER OF LOGINS PER USERNAME, number of times a particular username can login to the system concurrently. (Does not affect immune users) Page 2 8) NUMBER OF LOGINS PER CLUSTER, number of times a particular username can login to a given monitored cluster concurrently. (Does not affect immune users) The PTCLUSTER.DAT contains information pertaining to a particular cluster of terminals. Terminals are assigned a cluster number to allow the monitor to control different clusters using different parameters. For example, a student terminal room can be considered one cluster and all dial-up lines considered another, if these terminals are assign different cluster numbers, the monitor can control the login session in each cluster independent of each other. This file is used by the monitor as the defaults for each cluster at monitor startup time. A copy of this file is then made to a file called PTCLUSTER.TMP and this file is used by the monitor during its lifetime. The information include in this file is: 1) The CLUSTER NUMBER, an integer number from 0 to 999. 2) The CLUSTER STATUS, immune to monitoring, or monitored. 3) The PRIME TIME SLICE, if different from the default slice, see PTDEFAULT.DAT file. 4) The LOCATION is the actual location or description of the cluster. The TERMINAL.DAT file contains information pertaining to the status of each terminal to be monitored. Terminals connected to the system but not included in the database are considered immune to prime time monitoring. The information in this file is: 1) The device or TERMINAL name, (ex. TTA1, OPA0) 2) The CLUSTER the terminal is assigned to. 3) The TERMINAL STATUS, immune or monitored. 4) The PRIME TIME SLICE, if different from the default slice, see PTDEFAULT.DAT file. The PTUSER.DAT file contains information pertaining to users who have logged into the system, or users who have had a record added to the database using the controller program (PTC). Information in this file is: 1) The USERNAME as exists is the SYSUAF.DAT file. 2) The LAST LOGOUT TIME of the username in which the user was being monitored. 3) The LOGIN STATUS of the user (no login: user cannot login, immune: user has no prime time restrictions, login: user can login without a wait, wait: the user must wait before login). 4) The PRIME TIME SLICE, if different from the default slice, see Page 3 PTDEFAULT.DAT file. 5) The WAIT TIME, the amount of time a user must wait to login, if different from the default wait, see PTDEFAULT.DAT file. 6) The cluster number this user was last logged into. The distribution is in four subdirectories ( [.DOC] [.PTC] [.PTM] and [.LOGINTEST] All sources required for the facility are contained within the subdirectory, so there are some duplicate source files. You will have to modify some open statements to point to appropriate places for your system. The easiest way to find which files to modify is to do "search *.for open(". The code has good comments; read for further information. In particular, some common blocks must be dimensioned to match sysgen MAXPROCESSCNT. To find these, do "search *.for maxproc" and modify to fit your system. Each save set contains a command procedure called COMPILE.COM which will compile and link the routines, it is considerably easier to use the procedure than to type the commands by hand. After the image files have been built they should be copied to SYS$SYSTEM:. The image files should also have the following protections and must be installed (using the DEC INSTALL utility) with the following privileges. LOGINTEST.EXE File protection (S:RE,O:RE,G:RE,W:E) Installed OPEN, SHARED, HEADER_RESIDENT PRIVILEGES=(GROUP,SYSPRV,ALTPRI) PTC.EXE File protection (S:RE,O:RE,G:RE,W:E) Installed OPEN, SHARED, HEADER_RESIDENT PRIVILEGES=(GROUP,WORLD,BYPASS,DETACH,ALTPRI,PSWAPM) PTM.EXE File protection (S:RE,O:RE,G:RE,W:) Installed PRIVILEGES=(GROUP,WORLD,BYPASS,SYSNAM,PRMMBX,OPER) Page 4 After the images have been built, moved to their respective directories and install, you may invoke the Prime Time Controller and build your database. The directory MANAGER:[PTDATA] ( or its equivalent) must exist, PTC will not create it for you. See the Prime Time User's Guide for information on how to use PTC. The files will not exist when you start. However, you can create them by running PTC and executing the ADD and MODIFY instructions. The first time you run PTC, try the HELP command first.