From: MERC::"uunet!CRVAX.SRI.COM!RELAY-INFO-VAX" 12-SEP-1992 04:29:53.98 To: info-vax@kl.sri.com CC: Subj: Operations Manual (ascii) 1/3 Thanks to all who wrote! I just made a Postscript version and it turned out to be 1.9MB. Not wanting to post a 50-part file here, an ascii version is below. Again, please note that the thing I thought was most valuable was the existing format of the original document - not necessarily the information contained in this one. The original should make it fairly easy to set up a site-specific document for individual sites. This ascii version doesn't do it justice. As some have guessed, I no longer have access to a VAX - and so can't provide anything with VMS SHARE or any other VAX-specific utilities. My only access to Internet is through NETCOM (I pay for an account), which runs on a UNIX box (gosh I hate UNIX :). I also can't place anything on an FTP site. On the ascii version below, page breaks are marked with "--". If you'd like a version in any of these formats: Word 5.0 for Macintosh (original format) Word 3.x for Macintosh MacWrite II 1.x RTF (interchange format) Word for Windows 1.0 Word for Windows 2.0 Word for DOS Word Perfect 5.0 Word Perfect 5.1 ASCII/TEXT You can get them for a limited time by sending a self-addressed, stamped disk-mailer to: Michael Pye 2910 Santez Drive Pomona, CA 91768 Please specify the format(s) wanted and an e-mail address. If someone else wishes to put any or all of these versions on an FTP site somewhere in the world, that would be great! Thanks again! -- Michael Pye mpye@netcom.com -- Table of Contents Useful Phone Numbers 1 General Numbers 1 Computer Lab Numbers 1 Service Contracts 1 Miscellaneous Numbers 1 Computer Class Summary 2 Computer & Systems Bring-Up Order 2 Normally 2 Quarter Break 2 Computer Status Hotline 3 Updating the Hotline message 3 The message 3 Sample message #1 3 Sample message #2 3 Lab Alarm Procedures 4 Moisture Alarm Procedures 5 Shutdown Procedures for VAX Systems 6 Powerdown Procedures for VAX Systems 7 Power Failure Procedures for VAX Systems 8 Powerup Procedures for VAX Systems 9 Startup Procedures for VAX Systems 10 VMS/DCL Control Key List 11 HEGIS Program 11 Directory Specifications 12 File Security 13 General File Permissions 13 SET PROTECTION 13 Specific File Permissions 14 DIR/ACL 14 SET ACL 14 Monitoring & Balancing the System 15 What to do For a System SlowDown 15 What to do If The System is Hung 15 Miscelanious Monitoring Commands 16 SHOW CPU/ALL 16 SHOW DEFAULT 16 SHOW DEVICE/FULL device-name 16 SHOW DEVICES/MOUNTED 16 SHOW ENTRY/FULL 16 SHOW ERROR 16 SHOW MAGTAPE 16 SHOW NETWORK 16 SHOW PROCESS 16 SHOW PROCESS/CONTINUOUS/ID=pid 17 SHOW QUEUE 17 SHOW QUEUE/FORM 17 SHOW QUOTA 17 SHOW SYSTEM 17 SHOW USERS 17 Displaying & Modifying Queues/Jobs 18 Displaying Print Queues 18 Starting & Stopping Print Queues 18 Changing Printer Forms 19 Moving Queues 19 Reprinting Damaged Jobs 20 Aligning Standard Paper 20 Miscellaneous Commands 21 Delay printing job until after specified time 21 Change number of copies to print 21 Change form type for job 21 Hold a job for later processing 21 Assign an operator message to a job 21 Print selected portions of a job 21 Set the priority of a job 21 Release a job that is on hold 21 -- Table of Contents Initializing Tapes 22 Electronic Mail on the VAX 23 Your Electronic Mail Address 23 Sending Mail to Other Addresses 23 The Basics of Using Mail 23 Some More Advanced Mail Features 24 Sending Mail to Other Networks 24 AMERICA ONLINE 24 COMPUSERVE EASYPLEX 24 MCI MAIL 24 FIDONET MAIL 24 FTP (File Transfer Protocol) 25 Using FTP 25 When Do I "GET" And When Do I "PUT"? 26 Nationwide List of Anonymous FTP Sites 26 USENET News 27 What is USENET News? 27 Reading USENET and Other News 27 Some Common News Commands 27 Utilities 28 No BIN# on Printouts 28 Printing Executable & Object Files 28 Banners (Line Printer Generated Signs) 29 Fortune Cookies 29 Line Printer Calendars 30 On-Screen Calendars 30 Miscellanious Useful Commands 31 DIRECTORY 31 CREATE/DIR 31 TYPE 31 RENAME 31 COPY 31 DELETE 31 PRINT 31 PURGE 31 HELP 31 SET PASSWORD 31 LOGOUT 32 SET TIME 32 SHOW 32 /Device 32 /Default 32 /Error 32 /User 32 /System 32 REPLY 32 /Enable 32 /Status 32 /To 32 /ABORT 32 /USER 32 /Term 32 /All 32 /URGENT 32 VAX Operator Hotkey Summary 33 ASCII Character Table 34 -- Useful Phone Numbers General Numbers Computer Lab Numbers 911 EMERGENCY Bldg.Room# Phone# Lab Title 3070 Police 4000 Health Center 2 109B 4143 Agriculture Classrooms 3030 Physical Plant 2 135 3148 Agriculture Classrooms 0 Information *6 113 2355 CIS Dept. Micro Lab 4451 Mainframe Consultant *7 213A 2668 Environmental CAD 4193 Micro Consultant 8 52 3138 Advanced Workstation Lab 3133 Computer Status 8 146 3139 Science Hotline *8 301 3450 CS Dept. Lab 3235 CIS Department *9 101 2486 CAE Engineering 3440 CS Department 9 139 3466 Engineering 3280 Computer Store 9 141 2606 Engineering Faculty Lab 3073 Library Reserve Desk 10 106 3144 Metal Processes Lab 6900 Telecommunications 11 133 3145 CE/ME/MPE Engineering 3022 Stephanie Dota 13 108 3996 Aerospace Engineering 1 4411 Lino Barro 13 207 3146 Aerospace Engineering 2 15 1 3147 Library Lab 45 111 4108 Agriculture Engineering 97 121 4184 Campus Center * Denotes a non-Computing Resource Center Lab Service Contracts Miscellaneous Numbers DIGITAL/VAX 1-310-985-9599 SWRL Operations M-F 8am - 5pm: 1-800-624- 1-310-985-9622 SWRL Operations 3852 1-310-985-9533 SWRL Communications After Hours: 1-800-432- 1-310-985-9571 SWRL Communications 3373 (evening) Remote Dialup: 1-714-xxx- 1-310-985-9616 SWRL Analyst of the Day xxxx 1-310-985-9614 SWRL Temp Cyber Analyst 1-310-985-9407 SWRL Tieline problems - IBM 3174 SERVICE Alex 1-800-426-7378 1-805-756-5512 SLO Operations (IBM 3090) Cust#xxxxxxx 1-805-756-1295 SLO Communications (James Serial# xxxxxxxx Model# Feld) xxxx 1-805-756-1296 SLO Communications (Ralph IBM 3191 Console Serial# Nicovich) xxxxx 1-805-756-2516 SLO George Westlund 714-773-3910 Fullerton Operations (Mike CDC SERVICE NUMBER Rojo) Look on the top left 714-595-5993 ISN Dialup Modem Pool corner of 714-595-3779 X.25 Pad Modem Pool Console screen for the xxx-xxx-xxxx ADVAX Remote Dialup Modem latest Phone# and Customer ID# vmx access # 4777 ID#xxxx- Operations ID#xxxx - Hotline Message CDC Tech: 1-818-xxx-xxxx Home# - Only use if necessary MICOM SERVICE CONTRACT 8am - 8pm: 1-800-833-3282 Maint Agreement #xxxxx -- Computer Class Summary Below is a list of most of the computers accessible through the ISN. The steps necessary to access these systems depends on several factors. Basically, what you enter at the DIAL: prompt will either be ##, 1/##, or 2/##. For example, to go to the ACVAX cluster, this would be 85, or 1/85, or 2/85. Without going into a lengthy explanation of why this is so, just try one. If it responds with the message WRONG ADDRESS, try another. (1/85 works in most of the labs.) Class# Description 11 Engr. VAX 11/750 13 X.25 PAD 15 Library Inquiry System ( or 1/15 or 2/15) 16 CS Department PC BBS System 31 SLO IBM 3174 link IBM SLO IBM 3174 link 34 Port Selector 35 AT&T 3b15 70 Renex 75 9600 baud Cyber lines 83 Local Cyber 830 85 ACVAX Cluster 86 ISN 90 ADVAX Cluster 91 ADVAX Cluster 99 Micom PAD> CCS/30 ELXIS (embos) PAD> CCS/31 ELXIS (bsd) PAD> CCS/32 ELXIS (enix) PAD> SWRL/80 Telnet vmsa.is.csupomona.edu Cal Poly Pomona's ACVAX Cluster IP address vmsc.is.csupomona.edu Cal Poly Pomona's ADVAX Cluster IP address ibm.calpoly.edu Cal Poly SLO's IBM 3090 IP address The IP addresses above are just for reference. They cannot be entered from the DIAL: prompt. The addresses following the PAD> prompt are accessible through computer 13, the X.25 Pad. From the DIAL: prompt, enter 13. This should bring up the PAD> prompt. You can then enter these addresses. Computer & Systems Bring-Up Order Normally Quarter Break Air Conditioners Air Conditioners MICOM/Port Selector MICOM/Port Selector ACVAX Cluster ADVAX Cluster AT&T 3b15 Cyber 830 IBM 3174 ACVAX Cluster ADVAX Cluster AT&T 3b15 Cyber 830 IBM 3174 -- Computer Status Hotline The "Hotline" informs users of the current status of all the computer systems. It should be updated at the beginning of each shift. It should also be updated whenever there is a change in the status of a particular computer or computers. Updating the Hotline message y Call VoiceNet from any phone @ extension 4777. y Enter the Hotline extension and password - xxxx. y Enter 072 when requested to enter the address. y As requested, after the beep, enter 1 - followed by the status message. When you're through with the message, enter 5. If a mistake was made, you may enter a * instead of the 5 to start over. y When you're finished with the status message, type ** to leave VoiceNet. y Dial extension 3133 to verify the new status message. The message y Give the current date and time. y Give the current status of all the computer systems and estimated time up if one is down. If all systems are operational, you may state it that way. If an abnormality occurs (a computer being down, no operator on duty, etc.), this should be stated here. y Give the distribution of output schedule. y Give the Dial Up modem number along with related text. y Give numbers to call for further information. Sample message #1 (All's well) This is a recording. This is the Cal Poly Computing Resource Center for Monday, January 1, 8am. All systems are up. Distribution of output is made every half hour. The Dialup number for modems is (714) 595-5993. There are 15 lines running from 300 through 9600 baud. For further information, call a consultant at 869-4451 or a receptionist at 869-3120. Thank you. Sample message #2 (Various troubles) This is a recording. This is the Cal Poly Computing Resource Center for Monday, December 31, 8am. The Academic VAXCluster is currently down. Estimated time up is 4pm. All other systems are up. There will be no operator on duty until 7am on January 2. Distribution of output is made every half hour. The Dial up number for modems is (714) 595-5993. There are 15 lines running from 300 through 9600 baud. For further information, call a consultant at 869-4451 or a receptionist at 869-3120. Thank you. -- Lab Alarm Procedures What to do What to do Building Room# Description (DayTime) (After Hours) 2 135 SIL Call Sadru Option 1 2 109B SIL " Option 1 8 52 SIL " Option 2 8 146 SIL " Option 1 9 139 SIL " Option 1 9 141 Faculty Lab " Option 1 10 106 SIL " Option 2 11 133 SIL " Option 1 13 108 SIL " Option 2 13 207 SIL " Option 1 13 213 Training Lab " Option 2** 15 1 SIL - Library " Option 2 45 111 SIL " Option 1 97 120 Training Lab " Option 2** 97 121 SIL " Option 2 Option #1: Ask Public Safety to close the Lab and send a staff mail message on the Administrative VAX. Also leave a note for the Computing Resource Center Receptionist. If Public Safety isn't able to send someone to close the lab within a reasonable period of time, you can do it yourself with the operator's master lab key. Option #2 y Call Glenn at (714) xxx-xxxx. If he is not available - y Call Jim at (714) xxx-xxxx. If he is not available - y Call Sadru at (310) xxx-xxxx. If he is not available - y Ask Police Department to close the Lab as in Option #1 above. ** Option 2 only if during a training session, otherwise, Option 1. SIL = Self Instructional Laboratory -- Moisture Alarm Procedures When this alarm sounds, it means that there is water underneath the floor. Perform the following procedures: y Push the "alarm stop" button. y Determine the extent of the water level by lifting the floor panels in and around the A/C units, the VaxClusters, and the Cyber/Prime room. y If the situation looks serious, power down the computer(s) in the area of the water using normal shutdown procedures. Also, if warranted, shut down all electrical equipment, A/C units, and main circuit breakers using normal shutdown procedures. y Report problem: If during weekday, Physical Plant at extension 3030. If after hours, Police Dept. at extension 3070. Always notify supervisor. y Send "staff" mail on ADVAX cluster, if possible. y See below for diagram of water sensor locations. [Insert your favorite graphic here] -- Shutdown Procedures for VAX Systems y Before the Shutdown command is executed, it is a good idea to send all the users logged in a message informing them of the shutdown. If possible, this should be done about an hour in advance. If the shutdown is a non-scheduled one, it may also be a good idea to put a temporary message in the WELCOME.TXT file so that all users logging in will immediately be aware that the system is going to be shutdown. See the EWELCOME "Hotkey" for information on how to edit the WELCOME.TXT file. To send a message to all users, use the WARN "Hotkey". Example: WARN "VAX Systems going down in 1 hour for maintenance." or.... Example: REPLY/ALL/BELL/URGENT "VAX Systems going down in 1 hour for maintenance." y Execute the shutdown procedure for each of the VAX systems to be shut down. To execute the shutdown procedure, type the following command at each console to be shutdown: @SYS$SYSTEM:SHUTDOWN After this command is entered, several questions will be asked concerning the nature of the shutdown. The system will use your answers to these questions to display imminent shutdown warnings to the users every few minutes. So if there are users on the system, it is a good idea to make the answers to the questions meaningful for their sake. An example shutdown is shown below. Note that this is an EXAMPLE - your mileage may vary. $@SYS$SYSTEM:SHUTDOWN How many minutes until final shutdown [0]? 15 (or whatever) Reason for shutdown [standalone]? Weekly maintenance (or whatever). Do you want to spin down the disk volumes [No]? No Do you want to invoke the site-specific shutdown procedure [Yes]? Yes Should an automatic system boot be performed [No]? No When will the system be rebooted [later]? at 1300 (or whenever). Shutdown options [None]? REBOOT, SAVE, CLUSTER, REMOVE (use CLUSTER ONLY if entire cluster is being shut down). (use REMOVE ONLY if a single node is being shut down and NOT the entire cluster). (REMOVE and CLUSTER cannot be used at the same time). The above is an example only. You will likely want to change the answers to the questions depending on the circumstances. After all the above questions have been answered, the system(s) will proceed in shutting down. When the system(s) are completely shutdown, the following message will be displayed on the console of each: SYSTEM SHUTDOWN COMPLETE - USE CONSOLE TO HALT SYSTEM y After the above message is displayed, the systems are logically shutdown. If you wish to completely HALT the system (such as preparing for a power down), you need to do the following: For the VAX 6000 series, make sure that the CPU key switch is on ENABLE, and not SECURE. For the 9000 series, make sure the Service Processor Access switch is set to LOCAL/SPU. Then, enter the following on each system console you wish to halt: CTRL-P >>> H At this point, the systems are halted. If needed, you may now proceed to the Power Down Procedures. -- Powerdown Procedures for VAX Systems ( if systems will be down for more than 5 hours ) y Execute the Shutdown Procedures for VAX Systems for each system to be powered down. y To power off the 6000 series, turn the CPU switch next to the tape cartridge counter-clockwise until it is vertically positioned (in the OFF position). y To power off the 9000 series, turn the POWER switch from ON to OFF. y Because the VAXs are clustered, they share many of the resources between them. DO NOT CONTINUE PAST THIS POINT unless ALL systems in the cluster are logically shutdown and HALTed. y Power off the VT320 terminals on the consoles. y Power off all disk drives. First, push in the WRTE PROT button and then release the RUN STOP button on each of the disk drives. Both buttons are located on the front of the drives. y Power off all tape drives. The TU81 tape drives may be powered off with the on/off switch located inside the tape drive (where tapes are loaded) to the rear and right. The power switch for the TA79 tape drives is in the front of the unit inside the bottom swinging door. The power switch for the 8mm tape drives is on the rear of the unit. y Power off all printers. y Power off the HSC50 and the HSC70s. The power switch for the HSC50 is located behind the maintenance access panel inside the front door. The panel is located in the upper right-hand corner of the HSC50. To open the access panel, turn the screw in the top right corner counter-clockwise. The power switch for the HSC70s is near the upper right hand corner inside the front door - to the left side of the HSC disk drives. y Power off the DECservers and DELNIs in the Communications Cabinets (the short racks). Turn off the red illuminated power switch inside the rear door. All VAXcluster components should now be powered off. -- Power Failure Procedures for VAX Systems y If the power only fluctuated, the systems will probably try to re- boot themselves. This will usually work. Let the systems try to bring themselves back up while you go around to all components, such as disk drives, tape drives, and HSCs to make sure there are no faults. If there are faults, or a system will not come up automatically, refer to the sections below. y You may wish to refer to the Power Down Procedures, Power Up Procedures, Shutdown Procedures, and Startup Procedures for instructions on how to accomplish certain items on this page. y If the power has failed and it appears that the power will be down for an extended period of time, do the following: Push the WRITE PROTECT button followed by the RUN/STOP button on all disk drives. Follow this with using the power switch and breakers to power off all system components. Refer to the Power Down Procedures for VAX Systems for information on how to do this. This will protect the systems when the power does eventually come back on - as the power sometimes fluctuates on/off several times before it remains on. y If there are no faults on any of the devices and it appears as if the systems were successful in bringing themselves back up, refer to the ending portions of the Startup Procedures to make sure the systems are all the way up. y If a particular system was unsuccessful in bringing itself back up, refer to the Shut Down Procedures to bring that system logically down. The system should be at some point between being powered off completely and completely operational. Take whatever action necessary to bring the system from the current non-operational status to a logically shut down status. Refer to the Shutdown Procedures and Powerdown Procedures. It is probably not necessary to physically power down, however, it is possible for several things to get mangled enough so that this is necessary. Also, it is possible for some of the systems to be operational while others are down. Only shut down those systems which were unable to bring themselves back to operational status. In addition the HSC's are particularly troublesome and may need to be power-cycled. y Check all disk drives to make sure they are on, on-line, and no fault conditions exist. If any are off, press the WRITE PROTECT button followed by the RUN/STOP button. The RUN/STOP button may have to be pressed twice, once to turn it off, (what you're doing is turning the RUN/STOP button off - the drive is already off) and again to turn it on. The on position is with the button depressed. On the RA70 and RA90 drives, you must refer to the digital display or the LED switch to tell whether the drive is write protected or running. On RA90's, a 'W' will appear on the digital display if the drive is write protected, and an 'R' will appear if it is 'Running'. On the RA70's, a lit LED means that the drive is write protected or running. What you want to do is make sure the drives are write protected before bringing them to a 'Running' status. When the drive comes on- line, turn the WRITE PROTECT off. Faults can be cleared by pressing the FAULT button. Do this for each drive down. y Check all tape drives in the same manner as the disk drives. If powered off, they can be powered on again with the power switch located inside the drive (where tapes are loaded) for the TU81 drives. The TA79 drives power switch is located inside the lower swinging door on the front of the drive. Faults can be cleared by pressing the RESET button. y Check the HSC50 and HSC70 disk controllers. It may take a couple more minutes to come up than the disk drives. Faults can be cleared by pressing the FAULT button. It is possible that the HSCs may need to be powered off and on again. y Check the VT320 terminals on the consoles and on top of the HSCs. y Check all printers. They may have to be turned off and on again. Faults can be cleared by turning them off-line and then on-line or by pressing the CLEAR button on the printer. Leave the printers off- line until the systems are up and you can check to see if the paper is still aligned with a test print job (see the ALIGN print command in this manual). y If at this point, one or more systems are still down and all system components are on and operational, proceed to the Startup Procedures for VAX Systems, and use those instructions to bring the downed systems up to operational status. -- Powerup Procedures for VAX Systems y Power on the VT320 terminals on the consoles and on top of the HSCs. y Power on the HSC50/HSC70s disk controllers. The power switch is located behind the maintenance access panel inside the front door. The panel is located in the upper right-hand corner of the HSC50. To open the access panel, turn the screw in the top right corner counter- clockwise. The power switch for the HSC70s is near the upper right hand corner inside the front door - to the left side of the HSC disk drives. y Power on all disk drives. The circuit breakers for these are located inside the back of the drive at the very bottom of the units. The circuit breaker should not be off, but in case it is, an Allen wrench may be used to open the back door of the drive to get to the breakers. y Spin up all disk drives. Make sure the WRITE PROT button is depressed and that the drive is Write Protected and press the RUN STOP button for each drive. After the drive spins up and comes on- line/ready, release the WRITE PROT button. Do this for each drive on the system. y For the ADVAX cluster only: The digital display on the drives will display something like "R AB". It may only display "R A" or "R B" or just "R". "A" and "B" here signify one of the two HSCs that the drives are connected to. If the display is "AB", it means that the drive has access to both, but will only be using one. What you want to do is make sure all drives display "R AB". Treat the RA70 drive the same way. The RA70 drive uses LEDs and not a digital display. The LEDs corresponding to "Run", "A", and "B" should all be lit. Do this by depressing the A or B buttons on the drives. y Power on all printers. The printers should probably be left off- line until you can check to see that the paper is aligned properly. y Power on all tape drives. The TU81 tape drives may be powered on with the power switch located inside the tape drive (where tapes are loaded) to the rear and right of the tape drive. The power switch for the TA79 tape drives is in the front of the unit inside the bottom swinging door. The power switch for the 8mm tape drives is in the back of the unit y BEFORE CONTINUING ANY FURTHER, make sure that all disk drives and the HSC disk controller are powered on and on-line. The HSC should also be in a "ready state". If the STATE indicator on the HSC (shown below) is blinking on/off in approximately half-second intervals and the HSC is on-line, it is in a "ready state". y At this point, all VAX components should be powered up. y Refer to the Startup Procedures for VAX Systems to bring the systems to an on-line and operational status. -- Startup Procedures for VAX Systems y Make sure all components to the VAX cluster are powered up as in the Powerup Procedures for VAX Systems. y Startup the VAX 6000 series by turning the CPU key next to the tape cartridge three steps clockwise from the OFF position to the ENABLE position. This will initialize the VAX and return the subsystem prompt (>>>). If the key switch below the CPU key was set to AUTOSTART, the VAX should initialize and boot itself. If it was set to HALT, initialize and boot the VAX by entering the following command on the console after the subsystem (>>>) prompt. >>> B y Power on the VAX 9000 series by first turning the Service Processor Access switch to LOCAL/SPU. Then turn the Power switch from OFF to ON. Like the 6000 series, the 9000 may automatically boot up depending on the setting of the Startup switch. If the system doesn't start up automatically, but returns with the subsystem prompt (>>>), enter the following: >>> I/K >>> @CLEAR_MEMORY >>> B y Power on the DECservers and DELNIs in the Communication cabinets. These may be powered on with the power switch located by opening the cabinet door in the rear. The switch should light up when lit. y After the boot process is complete on each system brought up (this will probably take around a half hour), log into the operator account on each console. In order to make sure that the systems are up and operational, enter the following commands on each console in the cluster: $ SHOW NETWORK $ SHOW DEVICES D $ SHOW SYSTEM y The system should display a network node for each operational system as outlined below for the SHOW NETWORK command. If any node is unintentionally missing, the system is not completely operational and steps should be taken to find out why and correct the problem. (It is possible for one of the systems to take longer than the other to boot. In this case the slower system will not show up as a node in the cluster until it is finished booting.) Only the ACVAX nodes are shown below. VAX/VMS Network status for local node 5.2 ACVAX2 on 24-JUN-1992 09:01:00.89 The next hop to the nearest area router is node 5.5 CISCOA. Node Links Cost Hops Next Hop to Node 5.2 ACVAX2 2 0 0 (Local) -> 5.2 ACVAX2 5.1 ACVAX1 0 4 1 BNA-0 -> 5.1 ACVAX1 5.10 CLSTAC 0 0 0 (Local) -> 5.2 ACVAX2 Total of 21 nodes. y The information shown above may vary, but all expected nodes should be present and visible. An example of the SHOW DEVICES D command is below. Again, the numerical information may change, or drives may be added, but the status of all the devices should usually be "Mounted" - especially if that volume has a volume label and is a DUAx drive. Device Device Error Volume Free Trans Mnt Name Status Count Label Blocks Count Cnt HSC000$DUA0: Mounted 0 SYSFILES 161520 201 2 HSC000$DUA1: Mounted 0 APPFILES 418857 15 2 HSC000$DUA4: Mounted 0 USER1 1755582 4 2 y You should also log in to the systems from a normal terminal (non- console) as an additional check to make sure they're up. y After the systems are operational, turn the CPU key on the 6000 series next to the tape cartridge unit clockwise to the SECURE position. Turn the Service Processor Access switch on the 9000 series to the LOCAL/OS position. y Check all printer queues to make sure they are in their proper state with SHOW QUEUE/FULL/ALL *PRINT*. -- VMS/DCL Control Key List The following table is a list of control keys. All the keys listed are almost universally used in the same manner with the majority of VMS commands, procedures, and programs - where they are applicable. A control key sequence is represented as CTRL/?, where CTRL represents the [CONTROL] key and ? represents a control character. To type a control key sequence, press and hold the [CONTROL] key while typing the control character. Return key DELETE (rubout) Delete character (left of cursor) CTRL/A Toggle between insert and overwrite mode CTRL/B, ( -, or / ) Recall last command(s) CTRL/C Cancel CTRL/E Position cursor to End Of Line CTRL/H (backspace) Position cursor to Beginning Of Line CTRL/J (linefeed)Delete word (left of cursor) CTRL/O Toggle suppression of screen output CTRL/Q Continue to display output (negates CTRL/S) CTRL/S Suspend display output CTRL/T Display system and CPU time CTRL/X Discard current input line CTRL/Y Interrupt (a more powerful version of CTRL/C) CTRL/Z Exit HEGIS Program HEGIS is a program that gives information about standard Computer Center computer accounts. Supported are the standard seven character accounts on cybers as well as the eight character VAX and UNIX accounts. These accounts are distinguished by the second digit of the account, ex: CVADR001 & CUADR001. Also supported are the individual HEGIS codes themselves, ex: DR stands for Computer Science. Format: HEGIS account#. Where account# is a valid account or a valid HEGIS code. Examples: HEGIS CADR001 CADR001 is a Computer Sciences account for Course Work at Pomona HEGIS CVADR001 CVADR001 is a Computer Sciences account for Course Work at Pomona HEGIS DR DR is a Computer Sciences code All of the previous will give the department represented by the code 'DR'. Alternatively, the format HEGIS account# account# account# is supported. This will display the HEGIS departments for each of the given accounts. The limit is the number of accounts that can fit into the 255 character limit for VMS commands. -- Directory Specifications To locate a file, it is necessary to specify its directory path, also known as a directory specification or DIR-SPEC. The general format of a DIR-SPEC is: Device:[Directory.Subdirectory.Subdirectory...] For example, operator accounts are located on the device (or disk drive) named USER_DISK:. A directory structure (with corresponding DIR-SPECS) could be set up like this: [insert a diagram here] Most of the time, you will be able to leave out the device from your DIR-SPEC. For example, Nancy's account could be referenced with just [DAC.NEKING], and not USER_DISK:[DAC.NEKING]. Either one will work. When you initially log in to your account, the system automatically sets up your "default directory". Nancy's default directory is [DAC.NEKING]. Everything you do will be in relation to your default directory. You can change your default directory at any time with the SET DEFAULT command. For example, let's assume Nancy just logged in: After logging in Default directory starts at: [DAC.NEKING] SET DEFAULT [.REPORTS] or Default directory is now: [DAC.NEKING.REPORTS] DOWN REPORTS Nancy could then reference all files underneath the REPORTS directory. SET DEFAULT [-] or Default directory is now: [DAC.NEKING]. UP This is back where we started from. SET DEFAULT [-] or Default directory is now: [DAC]. UP From here, she can see other accounts under the [DAC] directory. SET DEFAULT [.GRCREWS] or Default directory is now: [DAC.GRCREWS]. DOWN GRCREWS This assumes Nancy has been given access to GRCREWS. SET DEFAULT [OPR.MPYE] Default directory is now: [OPR.MPYE]. This assumes Nancy has been given access to [OPR.MPYE]. SET DEFAULT SYS$LOGIN or Default directory is now: GRCREWS. [DAC.NEKING]. This HOME will always return you to your original login directory. -- File Security General File Permissions: Every file contains security information regarding ownership and access control. When a file is created from a particular account, that account automatically becomes the owner of the file. The owner of a file always has privilege to modify the file's protection field. The protection field dictates, in general terms, who else on the system has access to that file. The protection field consists of four parts: System Defines file/directory accessibility to the system and privileged users. Owner Defines file/directory accessibility to the file owner. Group Defines file/directory accessibility to all users within the owners group (ex: [OPR]). World Defines file/directory accessibility to ALL users. Each part above can have the following authorizations set: Read Allows users to Read the given file. If on a directory, allows access and listing of files within that directory. Write Allows users to modify or Write to that file. If on a directory, allows creation of deletion of files within that directory. Execute Allows users to run or Execute the given file. If on a directory, allows Executable access to files within a directory. Delete Allows users to Deletion the specified file. If on a directory, allows the deletion of the directory. Note: As indicated above, the protection fields for files and directories are interpreted differently. The command SET PROTECTION allows the file owner to alter protection fields. In addition, it is possible (through the use of Access Control Lists and System Identifiers) to make special provisions for only certain users to gain access to a file. As an example of the SET PROTECTION command, let's assume that Nancy (once again) has logged in and wants to change the security for her directory REPORTS directory to give the WORLD (everyone) Read and Execute permission, and to give her GROUP ([DAC]), Read, Write, Execute, and Delete permission. This is how she would do that: