.lm 1 .rm 72 .skip 4 .c;VAX CLUSTER USER GUIDE .skip 4 .hl 1 WELCOME .lt This document is available both as the VAX Cluster User Guide (part of the Central Computing Facility User Guide), and to interactive users through HELP @USERGUIDE. The VAX computer system is available to all Fermilab staff and users as a part of the Fermilab Central Computing Facility. The Cluster is accessed through class VC on the Fermilab port selector. The Cluster is presently composed of six VAX processors (two each 8600, 11/785 and 11/780 processors). They share about 3 Gigabytes of permanent user disk storage, and run the VMS operating system. This system is particularly well suited to interactive computing, and jobs with large memory requirements. As a rule of thumb, the 8600 will execute programs at a 1/2 to 2/3 the speed of the Fermilab Cyber 175 processors. The Cyber to VAX speed ratio may vary substantially from program to program. The relative speed of the VAX 8600/785/780 processors is about 4:1.5:1 The VAX system serves as Fermilab's gateway to external networks for file exchange and electronic mail. The VAX Cluster is node FNAL on the BITNET and DECnet networks. The NET program provides access to high speed file transfer and job submission between the various Central Computing Facility systems. In order to maintain program portability between these systems, the use of standard (ANSI X3.9-1978) FORTRAN-77 is urged. Documents to assist in producing portable code are available from the Computing Department Librarian. .el .hl 1 ACCOUNTS .lt To obtain a new account on the Fermilab Central Computing Facility, contact the Computing Department Secretary for a Computer Account Request form. This form will request certain general information about you, and require a Fermilab budget code and the signature of your department head or experiment spokesman. The form establishes your username and first-time password for use in logging onto the system. Your new account will be set up with a pre-expired password. This means that you must change the password the first time you log in. Be sure not to log out of the initial session until the password is changed. The system only allows you to log in once to an account with an expired password. The Fermilab computer system is now connected to several external networks, and your password is your primary protection. You may want to restrict the length of your password to eight characters, for compatibility with some of these networks. You are required to change your password with the SET PASSWORD command at least every 6 months. The system will require that your new password be at least six characters long. Passwords identical to your name, username, charge code, or group name will not be permitted. You are urged not to use English words, the name of your spouse or pet, or other 'obvious' passwords, and not to place passwords in disk files. Accounts having more than a single authorized charge code may have separate VAX accounts and directories established for each charge, with usernames of the form 'username_charge'. You may request request a mnemonic username, usually based on your name or initials. Such names will be assigned on request, as long as they do not match an existing name, or potential group or experiment name. Because of BITNET restrictions, alphanumeric usernames no longer than eight characters are recommended. As on the Cyber system, an account may be obtained for storage of shared files for a group or experiment. The username for such an account will be the experiment number or group name. .el .hl 1 LOGIN .lt The Vax Cluster is accessed through code VC on the Fermilab port selector. Enter one carriage return after you receive the GO prompt. You will be prompted for your username and password. If you have received any mail or network files, you will be automatically informed at login. The Cluster is nodes FNAL, FNALA, FNALB, FNALC, CDF, or CDFSFT on both BITNET and the High Energy Physics DECnet network. You may start an interactive session by issuing the SET HOST command when logged into any other machine on the DECnet network. There is a substantial network overhead, so you should expect some sluggishness in screen displays during such remote sessions. The standard command for logging off the Vax is LOGOFF. If a LOGOUT.COM file is present, it will be executed at logoff. At Fermilab, for the convenience of Cyber users, we have also defined a BYE command for logging off. The program ARGUS inspects all timesharing lines, and logs out users who have been idle for thirty minutes, giving warnings every ten minutes. The port selector hardware disconnects dial-in lines showing no activity for fifteen minutes. .el .hl 1 HELP .lt The HELP command gives you interactive access to an extensive library of information about VMS system commands. The HELP command may be used to access both user and installation provided help libraries. The following HELP topics are particularly useful: HELP Instructions Usage of the HELP command HELP Lexical Useful DCL symbolic functions HELP RTL RunTime Library, routines to provide system information, math functions, string functions HELP Hints Summary of available DCL commands HELP SET Set various file, terminal, device characteristics HELP SHOW Show device, terminal, file, system information HELP Specify Format for various types of command parameters, such as Filespec, Time, or Protection. The HELP for DCL commands usually includes, in addition to the specific command parameters and qualifiers, two standard subtopic names: Parameters, to describe specification of command parameters, and Qualifiers or Command_qualifiers, to describe all available command qualifiers. See the Librarian section of the VAX-11 Utilities Reference Manual for information on how to create and use your own help libraries. You may make a HELP library available through an interactive program by using the LBR$OUTPUT_HELP subroutine, as described in the Utilities Reference Manual. The VMSCAI on-line instruction program provides a useful introduction to the VMS operating system, when run from a VT-100 compatible terminal. .el .hl 1 FILES .lt File specifications provide the system with the information necessary to identify a unique file or device. Normally, only the file name, with type, needs to be used. The fully qualified file specification has the following format: node::device:[directory]filename.type;version The punctuation marks are required to separate the fields of the file specification. These fields are: node Network node name device Device name directory Directory name or sequence filename File name type File type version File version number All the fields but filename and type have default values. Node - Your local DECnet node name (SHOW NETWORK) Device - Your default device, usually USR$ROOTn (SHOW DEFAULT) Directory - Your default directory (SHOW DEFAULT) Version - highest version When a new version of a file is created, as with a text editor, the old version remains. Be sure to use the PURGE command, when appropriate, to delete all but the most recent version(s) of your files. You should rename old copies of files which you wish to keep, both for identification, and to prevent accidental purging. You should always use logical device names, such as USR$SCRATCH or SYS$PRINT, rather than device names such as DUK3 or LCA0. Changes in system configuration and future software releases are expected to require occasional changes in the the actual hardware names assigned to some system logical names. At Fermilab, your Username is used for the name of your root directory. You may create up to eight levels of subdirectory, using the CREATE/DIR [directory_name] command. For example, you may wish to place items related to program X in a directory such as [username.X], and test procedures for that program in subdirectory [username.X.TEST]. Wild cards may be used in specifying most parts of the file spec. % matches any single character, while * matches any number of characters in a given field. Some programs accept default type extensions. Some of these are COM - DCL Procedure EXE - Executable program FOR - FORTRAN HLP - HELP source text HLB - HELP library LIS - TYPE, PRINT MAI - MAIL folder MEM - RUNOFF output MAR - MACRO (VAX assembler source) OBJ - LINKER (output from compiler) OLB - LINKER (object library) RNO - RUNOFF input TLB - Text library .el .hl 1 SCRATCH .lt The USR$SCRATCH disk, with large quotas for all users, should be used for the temporary storage of files which are too large to be stored within the quotas available on the permanent disks. The USR$SCRATCH disk is not backed up by the scheduled system backups, and files will be periodically deleted, according to announced policies, by the management. Do not place any file on the Scratch device which cannot be regenerated or recovered from independent sources. Directories are established on USR$SCRATCH for all users. If you find that you do not have such a directory ,contact a consultant or GRIPE for assistance in having the directory established. Currently, files over a threshold product of size and days since last access are being removed from the scratch device daily. The BLOCKDAYS utility may be used to obtain a sorted list of your current files. First set up the product with @BLOCKDAYS_COMMANDS:SETUP, set default to the scratch device, then type BLOCKDAYS. .el .hl 1 BACKUPS .lt Full backups are made of the user disks on a daily basis. Backup tapes are retained for six months, then recycled. This is done only for the purpose of emergency recovery of lost files, and does not replace the normal users' archiving of files which should be performed. The VMS BACKUP utility may be used to easily and reliably archive files or entire directories to tape, and to restore desired files or directories. Users wishing to restore one or more files from the system backup tapes should send MAIL to SYSTEM, telling the full name of the file or files to be restored, when the file last existed on disk, and the circumstances of the file loss . .el .hl 1 PROTECT .lt File protection is specified, for each file, to determine which type of access each of four increasingly inclusive classes of users have to the file. The classes of users are System, Owner (your own UIC), Group (users with the same group code in their UIC), and World (all other users). The types of access are Read, Write, Execute, and Delete. You may use the EDIT/ACL command to create an Access Control List for any file. The ACL controls the access of individual users and classes of users to a file. The SET PROTECTION command lets you change the protection of any file. You should issue a SET PROTECTION/DEFAULT command in your LOGIN.COM procedure file to change the protection for newly created files, if the default of (SYSTEM:RWED,OWNER:RWED,GROUP:RE,WORLD:) is not satisfactory. This command will remain in effect for all subsequent files you create in the current session or batch job. To apply a protection different than the default to an entire subdirectory, apply that protection to the subdirectory.DIR index file with the SET PROTECTION command. For details of how to specify file or volume protections, see HELP SET PROTECTION and HELP SPECIFY PROTECTION. .el .hl 1 EDITORS .lt The EDT editor is the standard DEC supported editor for the VAX. It provides good full-screen editing when used with VT-52 or VT-100 terminals. It may be invoked by user application programs, allows keys to be software-programmed, has a macro definition capability which lets you define your own commands, supports multiple text buffers, and even has a good basic line-editing mode for non-DEC terminals. A good way to get started with EDT is to run the EDTCAI tutorial program, using a VT-100 compatible terminal. The EDT program itself has an extensive HELP facility, available by typing HELP in line mode, or hitting PF2 in screen mode. Several editors are available through the EDIT command (see HELP EDIT for details), but EDT is now the default. Other editors are available for users already familiar with them: SOS - The old line editor. May be dropped soon. TECO - Early DEC character editor. WYLVAX - SLAC's WYLBUR, for advanced line editing. .el .hl 1 COMMANDS .lt A few commands have been added as local Fermilab symbols, to provide convenient access to optional products available at Fermilab. For more information on standard VMS commands, see HELP HINTS and the DCL Commands and Lexical Functions quick reference guide. Bye Log out DTR32 DEC Datatrieve Logoff Log out Net Fermilab Hyperchannel file transfer Netty MFE network remote terminal connection Netout MFE network file transmission Netin MFE network file receiving Receive BITNET file receiving Send BITNET command, file, and message transmission Who User directory .el .hl 1 DEBUG .lt The VMS Symbolic Debugger provides an extensive interactive debugging facility. Capabilities include : Full screen display of source, output, and commands Breakpoints Tracepoints Variable monitoring Subroutine monitoring Instruction stepping Instruction examination (source) Variable examination and deposit Expression evaluation Subroutine calling The FORTRAN User's Guide contains an overview of Debugger usage with FORTRAN programs. Other language manuals contain similar sections. More detailed information is available in the VAX-11 Symbolic Debugger Reference Manual. .el .hl 1 BATCH .lt You may use the SUBMIT command to run a command procedure as a batch job. Several queues have been defined, each with an intended usage, and corresponding priority and limits. Type SHO QUE/BAT/FUL to see current queues, limits and priorities. Type SHO QUE/BAT/ALL to list individual jobs and scheduling priorities (not executing priorities).The SUBMIT command is of the form: $ SUBMIT/QUEUE=queue-name filespec Queue Priority Intended Use ----- -------- ------------ LOWPRI 2 Long or large (overnight) SYS$BATCH 3 Normal (hour) HIGHPRI 4 Short/small (minutes) You may use SUBMIT/NOPRINT/LOG=filespec to save output in a disk file. You may stop one of your currently executing jobs or remove a job pending in a queue with a command of the form $ DELETE/ENTRY=entry queue The VAX cluster has been configured, and will be managed to give priority to interactive computing. In order to improve system responsiveness, interactive Jobs requiring more than two minutes of CPU time per step during peak usage hours (weekdays 8#AM to 5#PM), should be submitted to one of the batch queues. These time recommendations may be adjusted as the system is expanded. .el .hl 1 PRINTER .lt The VAX Cluster printer is located with the other Central Computer Facility Printers on the seventh floor of Wilson Hall. Output is sorted and binned by the operators, based on the last two digits of your Fermilab ID number. The present default printer is an 800 line per minute Printronix dot-matrix printer. Talaris laser printers are available for text and graphics printing on letter size paper. Print queues are assigned names by the geographic location of the printer. The WH7W_PRINT 24 page per minute printer is serviced by the operators, with output placed in the normal printer output bins. Files may be routed for printing between the Cyber and VAX central facility systems using the PRINT function of the NET command. .el .hl 1 TAPES .lt 6250/1600 bpi tape drives have been installed for use with the VAX cluster. Tapes will be mounted by the operators in much the same manner as is done for the Cyber system. Labeled tapes stored in the tape vault must have identical internal and external labels. These labels are six characters long; a two letter prefix assigned by the laboratory to a group or experiment, followed by a four digit number assigned by the users. "NO-VAULT" tapes stored outside the vault system may have any valid label, but must be properly identified. The tape wrapper must contain a 'NO-VAULT' sticker, as well as the name of the tape. To avoid confusion due to duplicate labels, you are urged to also identify your non-vaulted tapes with your Username and experiment or group name. Your program should always address a tape by referring to a logical device name, and not the actual name of the drive being used. To assign the first free tape drive to your logical name, use the command $ ALLOCATE MU: drive-logical Once a drive has been allocated, you can mount the tape with $ MOUNT [/FOR] [/COM="WRITE"] drive-logical volume-label The /FOR option specifies an unlabeled, or foreign, tape. The /COM option requests that a write enable ring be placed in the tape. When you mount a tape interactively, the system will not process further commands until the tape has been mounted, at which time the system prompt will reapper. If you wish to cancel a requested mount, type CTRL-Y. You may communicate with the operator while a mount is in progress by using the command $ REQUEST "message-text" When your program has finished using the drive, issue the commands $ DISMOUNT logical-name $ DEALLOCATE logical-name Please send mail to user GRIPE on the FNAL VAX Cluster if you have any questions, problems, or suggestions. .el .hl 1 FINGER .lt Finger is a "SHOW SYSTEM" like program with options to provide : $ FINGER "Show System"-like output, showing the personal name, executing program, and other information for all users currently logged in. $ FINGER username Detailed information about a specified user including the contents of the user's FINGER.PLN file (if the user has one) and the status of the user's mailbox. In addition, if the user is logged in, the session information is displayed. $ FINGER personalname Finger will look up the user ID of a person whose name you know. $ FINGER @node Finger information at a DECnet or BITNET node, if the remote node runs a compatible version of FINGER. Finger is a non-DEC product. See HELP @LIB FINGER for more information. .el .hl 1 LIBRARY .lt Fermilab supported programs, procedures and load libraries are contained under the LIB:[LIB] directory. They should be named using the logical name LIB: rather than the corresponding physical disk name. The history of any product, and all support information and programs are contained under the appropriate subdirectory of the LIB account, LIB:[LIB.product] Program usage : $ RUN LIB:[LIB.product]program.EXE To run a program $ @LIB:[LIB.product]procedure.COM To execute a procedure $ LINK ...,LIB:[LIB.product]product.OLB/LIBRARY,... To link with a library LIB:[LIB.WRITEUP.IV]IV2.MEM describes Fermilab product maintenance standards. .el .hl 1 NET .lt The NET program provides file transfer, file printing and job submission between mainframes of the Fermilab central facility. On the Cyber system, you must GET,NET/UN=PRLIB before using NET. You will be prompted for any omitted parameters. The function and file parameters may be followed by optional qualifiers. Any qualifiers not processed by NET are appended to the appropriate batch job command. You may use these qualifiers to specify such things as alternate user names, file protection, print file routing, or batch job queues. Note that on the Cyber, a period must separate any parameters from NET. VAX > NET function file remotefile node account password CDC > NET.function file remotefile node account password _________________ PARAMETERS and QUALIFIERS _________________________ function - MAIL, PRINT, RECEIVE, SEND, or SUBMIT /DISPLAY - (default) Translate to/from Cyber display code /ASCII - Translate to/from Cyber 8/12 ASCII code /BIT - direct binary transfer /DEBUG - Full session messages, dayfile in Cyber WAIT queue localfile - Name of the permanent file to mail/print/send/receive/submit /SAVE(default),/REPLACE,/DEFINE,/PURGE /GET(default),/ATTACH - apply specified action(s) to Cyber file remotefile - Remote file name (User for MAIL, dummy for PRINT, SUBMIT) Qualifiers are the same as for localfile, described above node - Name of the remote node, CDC for Cyber, VAX for Vax Cluster account - Username for your remote node batch job. password - Password of the remote account. _______________________ E X A M P L E S ________________________________ ( For example, username E100, password ABROHAT on VAX or Cyber ) * * Copy from user E100's file MYPROG on Cyber to file MYPROG.FOR on VAX VAX> NET REC MYPROG.FOR MYPROG CDC E100 ABROHAT * * Print VAX file MYFILE.LIS on TC=2 printer, upper and lower case. VAX> NET PRINT/ASCII,TC=2,EC=A9 MYFILE.LIS DUM CDC E100 ABROHAT * * Submit a low priority batch to the Cyber system, output in WAIT queue VAX> NET SUBMIT/TO BITJOB.CDC DUMMY CDC E100 ABROHAT * * Send E103's direct access file MYPROG to user E100 on VAX CDC> NET.SEND MYPROG/UN=E103/ATTACH MYPROG.FOR VAX E100 ABROHAT __________________________________________________________________________ Net operates by submitting batch jobs on both the local and remote systems. Your Cyber account must have a default charge code. On the VAX, the batch job generates a NET.LOG log file in your USR$SCRATCH root directory. The Cyber batch job dayfile will be printed unless the /DEBUG function qualifier is specified. If a transfer fails, look in the batch job output for diagnostic messages. Procedure LIB:[LIB]SIX12.COM may be used on the VAX to convert files between ASCII and Cyber 6/12 ASCII encoding. .el .hl 1 BITNET .lt BITNET is a large, voluntary network of Universities and laboratories, connected by 9600 baud leased lines. This network supports electronic mail, file transfer, and real-time commands and messages. The Fermilab VAX Cluster is connected to BITNET as node FNAL. Because the network is voluntary, a direct link to any node may not always be available. However, mail and file items are stored and forwarded one link at a time, so that an item sent will eventually be received by the destination node once it enters the network. Mail is sent using the standard VAX/VMS MAIL utility, with a special form of address. BITNET items should be send to JNET%::"USER@NODE", where the item is to be sent to USER at BITNET node NODE. BITNET mail is received as standard VAX/VMS mail. Files are sent and received over BITNET with the SEND and RECEIVE commands. You are automatically notified at login time of any received files. These commands have been added locally, and are not part of the standard VMS operating system. See HELP SEND or HELP RECEIVE for details. By default, SEND and RECEIVE take care of any character conversions necessary for sending ASCII text between the IBM and DEC systems in the network. To send a file, use a command of the form $ SEND/FILE file node user To copy all pending received files into your current default directory, $ RECEIVE * To send a one line message to a remote user, $ SEND/REMOTE node user "message ..... " To send a one line message to a local user, $ SEND user "message ..... " You may define or assign logical names for use by MAIL and SEND. The equivalence name should have the same form as used for BITNET MAIL. For example, $ DEFINE nickname "JNET%::""user@node""" Since the logical name includes both the node and user names, the SEND command used with a logical name requires only one argument in place of the normal node and user arguments. .el .hl 1 DECnet .lt DECnet is a combination of DEC supported hardware and software providing a connection between your local operating system and the systems of remote computers , or nodes, connected to the network. You may, for example, access remote files, send and receive mail, use the PHONE utility, submit batch jobs, and start interactive sessions. In a DECnet style filename, the normal file specification is prefixed with the remote node name and two colons (node::). DECnet files may be used with almost all programs and utilities. The Fermilab Vax Cluster DECnet (and BITNET) node name is FNAL. Access remote file node::filespec Owner access to remote file node"Account Password"::filespec Send mail To: node::username Submit job SUBMIT/REMOTE node"acct pass"::filespec Phone PHONE node::username PHONE directory node:: The VAX Cluster is connected to the SLAC/LBL DECnet, giving access to over 100 High Energy Physics and university computer systems. Type the SHOW NET command to see a list of currently available DECnet nodes. .el .page