Prime Time Guide This describes the commands for the control of the Prime Time Monitor. To invoke the Prime Time Monitor Control Program type: MCR PTC or RUN SYS$SYSTEM:PTC Commands available (unless otherwise noted, the user must have at least Limited Privileges to execute any commands): ADD Adds a record to the Cluster, Terminal or User database files. (Requires System Privileges) COUNT Displays count of active terminals per cluster. CRASH Forces the Prime Time Monitor to terminate. (Requires System Privileges) EXIT Exit from control program (may also use CONTROL Z). FIXUSER Modifies a user's login status to allow immediate login. HELP List the commands available. KILLUSER Terminates any normal interactive process. LOAD Forces the prime time monitor to reload a database file and re-scan the current users. (Requires System Privileges) MODIFY Modifies the Cluster, Terminal or User database and modifies or creates the Default database file. (Requires System Privileges) MONITOR Creates the Prime Time Monitor Process. REMOVE Removes a record from the Cluster, Terminal or User database files. (Requires System Privileges) SHOW Display Cluster, Default, Terminal or User database. SHUTDOWN Change the status of a cluster to be immune. STARTUP Change the status of a cluster to be monitored. All commands requiring information from the user to complete a request will prompt for it. Data typed on the command line will be ignored. ADD COMMAND Page 2 The ADD command allows you to add a record to either the Cluster, Terminal, or User database. THE CLUSTER option prompts you for the new cluster number, the cluster status (immune or monitored) the prime time slice and the location of the cluster (20 characters). The TERMINAL option prompts for the device and controller and then generates the terminal numbers for all eight terminal on that controller (DZ). You are then prompted for the cluster in which the terminal resides, the terminal status (immune or monitored) and the prime time slice. To add the operator console type "OP" at the controller prompt. The terminal "OPA0" will be added as an immune terminal in cluster "0" . The USER option allows you to add a record for a user who has not logged in yet, you are prompted for the login status of the user (no login: the user is not permitted to login, immune: no prime time restriction, login: user can login without a wait, wait: user must wait a certain period of time to login). You will also be prompted for the wait time and prime time slice. Examples of the ADD command: PTC> add Cluster,Terminal,User: cluster Cluster Number: 10 Cluster status (0=immune,1=monitored,CR=immune): 1 Prime time slice in minutes (CR=default): Location: Burlington PTC> add Cluster,Terminal,User: terminal Device and controller (first 3 characters of terminal #): tta Terminal= TTA0 Cluster number :10 Terminal status (0=immune,1=monitored,CR=immune): 1 Prime time slice in minutes (CR=default): Terminal= TTA1 Cluster number :10 . . Continued dialogue for each terminal (8 in total) on the A DZ. . PTC-ADD Records TTA0 through TTA7 added. PTC> add Cluster,Terminal,User: user Username: test Login status (-1=no login,0=immune,1=login,2=wait,CR=immune): 1 Wait time in minutes (CR=default): Prime time slice in minutes (CR=default): 90 PTC> CRASH, EXIT, FIXUSER AND HELP COMMANDS Page 3 The CRASH command allows you to force the prime time monitor to exit (the monitor is a detached process that normally runs from system boot to system shutdown) Example for bringing down the monitor process: PTC> crash OK to shutdown Prime Time Monitor? yes PTC-SEND-MAIL Message sent to Prime Time Monitor. PTC-SEND-MAIL Message received by Prime Time Monitor. PTC-CRASH Request complete. PTC> The EXIT command or CONTROL Z causes the Prime Time Control program (PTC) to exit and return control to DCL level. The FIXUSER command changes the login status of a user to allow immediate login. No change will be made if the users current status is No Login, Immune or Login. Example: PTC> fixuser Username: test Last logout time/time stamp: 5-MAY-1982 09:03:14.17 Login status (-1=no login,0=immune,1=login,2=wait): 2 Wait time in minutes (0=default): 0 Prime time slice in minutes (0=default): 0 Is this the username to be fixed? yes PTC-FIXUSER Users login status changed to LOGIN. PTC> The HELP command displays a list of the commands available and a short explanation of each. Only commands the user has the privileges to use will be displayed. KILLUSER AND LOAD COMMANDS Page 4 The KILLUSER command allows you to terminate an interactive process. Users with a group number less than or equal to the SYSTEM PRIVILEGE GROUP may terminate any interactive user. Users with a group number less than or equal to the LIMITED PRIVILEGE GROUP may terminate any interactive user whose group number is greater than the SYSTEM PRIVILEGE GROUP. Example on how to kill a user: PTC> killuser Username: test Victim Terminal Location 1 TTA4 ACS Staff 2 TTH6 12 Hayden Enter Victim number (CR = abort request): 2 PTC-KILLUSER Killed user: TEST, terminal: TTH6, cluster: 12 Hayden PTC> The LOAD command will force the Prime Time Monitor to reload its temporary database from the permanent database and re-assess the status of the system. The LOAD command is used in conjunction with the MODIFY command or if the user wants to reset the temporary database to its default (permanent) values. Example for doing a LOAD: PTC> load Cluster,Defaults,Terminal,User: cluster PTC-SEND-MAIL Message sent to Prime Time Monitor. PTC-SEND-MAIL Message received by Prime Time Monitor. PTC-LOAD Request complete. PTC> MODIFY COMMAND Page 5 The MODIFY command allows you to change a record in the CLUSTER, TERMINAL and USER database and allows you to create a new DEFAULTS database. The possible fields that can be modified are the same that can be set using the ADD command, with the exception of the DEFAULTS database (not an option with the ADD command). To make a change type in the new value after the current value is printed, if no change is to be made hit the carriage return. If you select the DEFAULTS options you are prompted for the DEFAULT PRIME TIME SLICE, the DEFAULT WAIT TIME, the DEFAULT THRESHOLD, the SYSTEM GROUP, the SYSTEM PRIVILEGE GROUP, the LIMITED PRIVILEGE GROUP, and the the PERMITTED LOGINS PER USERNAME (see the SHOW COMMAND). The MODIFY command updates the permanent database and any changes do not go into effect until you execute the LOAD command or the Prime Time Monitor is restarted (operating system boot time). Examples of using the MODIFY command: PTC> modify Cluster,Defaults,Terminal,User: cluster Cluster Number: 0 Cluster status (0=immune, 1=monitored): 0 Prime time slice in minutes (0=default): 0 Location: ACS Staff Is this the cluster to be modified? yes Enter new value, hit CR to leave unchanged. Cluster status (0=immune, 1=monitored): 0 :1 Prime time slice in minutes (0=default): 0 :120 Location: ACS Staff : PTC> MODIFY COMMAND EXAMPLES Page 6 More examples of using the MODIFY command: PTC> modify Cluster,Defaults,Terminal,User: terminal Terminal to be modified: tta0 Cluster number : 0 Terminal status (0=immune, 1=monitored): 0 Prime time slice in minutes (0=default): 0 Is this the terminal to be modified: yes Enter new value, hit CR to leave unchanged. Cluster Number: 0 : Terminal status (0=immune, 1=monitored): 0 :1 Prime time slice in minutes (0=default): 0 : PTC> modify Cluster,Defaults,Terminal,User: user Username: test Last logout time/time stamp: 5-MAY-1982 09:03:14.17 Login status (-1=no login,0=immune,1=login,2=wait): 0 Wait time in minutes (0=default): 0 Prime time slice in minutes (0=default): 0 Is this the username to be modified? yes Enter new value, hit CR to leave unchanged. Login status (-1=no login,0=immune,1=login,2=wait): 0 :-1 Wait time in minutes (0=default): 0 : Prime time slice in minutes (0=default): 0 : PTC> modify Cluster,Defaults,Terminal,User: defaults Defaults: Prime time slice: 60 Wait time: 30 Threshold: 15 System group (octal): 013 System Privilege Group (octal): 010 Limited Privilege Group (octal): 013 Permitted logins per username (0 = unlimited): 1 Do you want to make any changes? yes Prime time slice: 60 :90 Wait time: 30 : Threshold: 15 : System group (octal): 013 : System Privilege Group (octal): 010 : Limited Privilege Group (octal): 013 : Permitted logins per username (0 = unlimited): 1 : PTC> MONITOR AND REMOVE COMMANDS Page 7 The MONITOR command allows you to create the prime time monitor process (the monitor is a detached process that normally runs from system boot to system shutdown). This command allows you to restart the the monitor without rebooting. Example for creating the monitor process: PTC> monitor OK to start Prime Time Monitor? yes PTC-SEND-MAIL Message sent to Prime Time Monitor. PTC-SEND-MAIL Message received by Prime Time Monitor. PTC-MONITOR_STARTUP Request complete. PTC> The REMOVE command allows you to remove a record from the CLUSTER, TERMINAL or USER database. You are prompted for the cluster number, terminal controller or the username depending on the option you select. Data pertaining to your selection will be displayed and you will be prompted for permission to remove it from the database. PTC> remove Cluster,Terminal,User: cluster Cluster Number: 0 Cluster status (0=immune, 1=monitored): 0 Prime time slice in minutes (0=default): 0 Location: ACS Staff Is this the cluster to be removed? yes PTC> remove Cluster,Terminal,User: terminal Device and controller to be removed: a (no data displayed) PTC> remove Cluster,Terminal,User: user Username: test Last login time/time stamp: 5-MAY-1982 09:03:14.17 Login status (-1=no login,0=immune,1=login,2=wait): 0 Wait time in minutes (0=default): 0 Prime time slice in minutes (0=default): 0 Is this the username to be removed? yes PTC> SHOW COMMAND Page 8 The SHOW command allows you to examine the database files used by the monitor system. The command prompts you for one of four categories (Cluster,Defaults,Terminal,User) and will prompt for more information as required. If you select the CLUSTER option, you will be prompted for the type of data (Permanent or Active). The active data is the data actually being used by the monitor system. This database is the one to be concerned with. (The permanent data is used only when the monitor system is started at operating system boot time). The command also displays the location of the cluster and the prime time slice. If you select the show all (CR) when prompted for the cluster number the display is put in table format. SHOW DEFAULTS will display the default values used by the monitor system to control the users. The values are: 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 users who are immune) SHOW TERMINAL allows you to check the status of a particular terminal, it displays the cluster the terminal is in, the status of the terminal (immune or monitored) and the prime time slice. If you select the show all (CR) when prompted for the terminal or wild card part of the terminal number (example: TTA*) the display will be put in table format. SHOW USER displays information about a username. Information given includes the last logout time of the user in which the user was being monitored. 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), the prime time slice and wait time. If you select the show all (CR) when prompted for the username or wild card part or all of the username (example: SYS*) the display will be put in table format. SHOW COMMAND EXAMPLES Page 9 The use of the SHOW command is shown in the following example: $ mcr ptc PTC> show Cluster,Defaults,Terminal,User: cluster Permanent or Active data (CR=Active): permanent Cluster Number (CR=show all): 1 Permanent Cluster Information Location: 12 Hayden Cluster number: 1 Cluster status: Immune Prime time slice in minutes : 60 PTC> show Cluster,Defaults,Terminal,User: defaults Defaults: Prime time slice: 60 Wait time: 30 Threshold: 15 System group (octal): 013 System Privilege Group (octal): 010 Limited Privilege Group (octal): 013 Permitted logins per username (0 = unlimited): 1 PTC> show Cluster,Defaults,Terminal,User: terminal Terminal (CR=show all): tta4 Location: ACS Staff Terminal status: Immune Prime time slice in minutes: 60 PTC> show Cluster,Defaults,Terminal,User: user Username (CR=show all): test Last logout time/time stamp: 5-MAY-1982 09:03:14.17 Login status: Login Wait time in minutes: 30 Prime time slice in minutes: 60 PTC> STARTUP AND SHUTDOWN COMMAND Page 10 The STARTUP command prompts for the cluster number and then returns the location of the cluster, it then asks if this is the cluster to STARTUP. Example for the STARTUP of a cluster: Use the SHOW command to check the status of cluster number 1. The cluster status is immune and therefore not currently being monitored. Use the STARTUP command to change the status of the cluster to the monitored state. The startup command prompts for the cluster number and then returns the location of the cluster, it then asks if this is the cluster to startup. $ mcr ptc PTC> show Cluster,Defaults,Terminal,User: cluster Permanent or Active data (CR=Active): active Cluster Number (CR=show all): 1 Active Cluster Information Location: 12 Hayden Cluster Number: 1 Cluster status: Immune Prime time slice in minutes: 60 PTC> startup Cluster number: 1 Location: 12 Hayden Is this the cluster to startup? yes PTC-SEND-MAIL Message sent to Prime Time Monitor. PTC-SEND-MAIL Message received by Prime Time Monitor. PTC-STARTUP Request complete. PTC> To SHUTDOWN a cluster you may use the SHOW command as in the above example to find the correct cluster number and check the state and the location for the cluster you want to shutdown. The SHUTDOWN command prompts for the cluster number and then returns the location of the cluster, it then asks if this is the cluster to shutdown. $ mcr ptc PTC> shutdown Cluster number: 1 Location: 12 Hayden Is this the cluster to be shutdown? yes PTC-SEND-MAIL Message sent to Prime Time Monitor. PTC-SEND-MAIL Message received by Prime Time Monitor. PTC-SHUTDOWN Request complete. PTC>