 .ps 58 .lm 10 .rm 70 .sp 1  .setdark .nnm .ap  .literal<                                           December 1st, 1983    8                                                  ** * **:                                                **** * ****;                                               ***** * ***** <                                              ****** * ******<                                              ****** * ******;                                               ***  ***  ***               7                                                   ***** 8                                                  ******* .end literal .la120 8 .literal    0                                         ROCKWELL0                                    INTERNATIONAL .end literal .la120 6 .s 3 .i 10  ^&VAX Planning Committee\& .la120 8 .s .i 40  VOLUME 1 .la120 .literal    < ____________________________________________________________   .end literal .la120 5 .i 2 ^&VAX OPERATOR AND SYSTEM  .i 1         MANAGER JOB DESCRIPTIONS\& .la120 .literal  < ____________________________________________________________ .end literal .s -8  .literal< ____________________________________________________________  <                        Collins Transmission Systems Division<                                       Rockwell International<                                               P.O. Box 10462<                                         Dallas, Texas  75207                                                        < ____________________________________________________________ .end literal .pg  .literal$ First Printing:   December 1st, 1983   .end literal
 .X Preface .p 0E The information in this document is subject to change without notice. E Rockwell International reserves the right to make enhancements to its G products which may affect the accuracy of this document. Although every H attempt has been made to assure accuracy, Rockwell International assumes                                                      C no responsibility for any errors that may appear in this document.    H The software described in this document is furnished under a license andI may be used or copied only in accordance with the terms of such license.    F No responsibility is assumed for the use or reliability of software on: equipment that is not supplied by Rockwell International.  .s 3/ .c 70 Copyright#(c)#1983 Rockwell International  .c 70 All Rights Reserved. .s 3 .c 70 Printed in U.S.A.  .s 3                                > The following are trademarks of Digital Equipment Corporation: .s .lm +10  .literal+ DEC       VAX       VMS       PDP       RSX  .end literal .lm -10  .pg    #  .s 8 .c 70 ^&PREFACE\&  .s 3 ^&MANUAL OBJECTIVES\&   H This manual describes the VAX system manager and operator jobs.  It alsoH lays the groundwork for the procedures that will be necessary to run theI VAX system. These procedures are divided between those done by the system / manager and those done by the system operator.        C This intent of this manual is not have all the answers for what the J operational procedures should be. Rather, it should serve as the basis forB discussion of what procedures are necessary and how they should be< partitioned between the system manager and system operator.  .s 2 ^&INTENDED AUDIENCE\&   J This manual is for members of the VAX project team charged with doing the F initial groundwork prior to the arrival of the Engineering VAX system. .s 2 ^&STRUCTURE OF THIS DOCUMENT\&                E This document is broken into two chapters.  The first covers the VAX  J operator, his responsibilities and his duties.  The second covers the VAX  system manager.  .nm    .ch VAX OPERATOR .t ##########VAX OPERATOR  .lm 10 .rm 70 .ap J The VAX operator plays a key role in running a VAX system.  He is the one I that keeps the system running smoothly, answers user's questions and does I a lot of the mechanics of keeping the system running.  The following list                                         1 identifies the operator's major responsibilities:  .ls  .le; Backups  H The operator sees to it that backups are successfully done on a regular K basis.  He is the one that recovers lost or accidentally deleted files for  
 the users.  D Normally, incremental backups are done during the week and complete H system backups on Fridays.  Once a month, the complete system backup is I placed into a safe to guard against accidental loss due to Mother Nature.                                                   H After one year, these archive tapes are moved to the normal tape storageJ area and are replaced with a new complete system backup.  The incremental D tapes are recycled each week.  The complete system backup tapes are J recycled once a month.  The complete archival tapes are cycled out once a  year.   J This procedure minimizes the loss due to disk failures and/or human error.J The critical part of all this is that the backups have verified integrity.                                                    J Thus, the operator, by doing these backups, takes on the principle role in/ assuring the recoverability of the user's data.    .le; Mount disks and tapes  J The operator must mount and dismount user's tapes and disks.  These tapes J and disks are normally "privately" owned by the user and have information 4 on them that should not or need not be kept on line.    .le; Keep line printers in paper .le; Manage batch/print queues  G VAX/VMS can have several batch and/or print queues.  The operator must    J keep a watch over these queues to assure their normal operation.  He must H also intercede whenever necessary to keep these queues running smoothly.F For example, it might be necessary or desirable to stop a batch queue K whenever the system is busy with interactive users.  The batch queue could  J then be resumed later when some of the activity had subsided.  As another F example, a line printer could break during the middle of a job.  Then                                                               H operator would have to requeue all the jobs destined for the printer to 5 another printer and take then printer out of service.   * .le; General operation of system utilities  K The operator should know how to monitor the system to check on things like  K processor load, memory utilization, I/O rate and what not.  He should also  K be able to adjust the system to take these things into account.  He should  I also know enough to answer user questions like, "How do I edit my file?"                         and "How do I run my program?".   % .le; Preliminary hardware diagnostics   H The operator should be able to make some initial diagnosis for hardware H problems.  In one case, a user calls up and complains that his terminal I isn't working or that his program is taking too long to run.  In another  J case, the disk or tape drive might not be working properly.  The operator J should be able to check the normal things (is it plugged in, is it turned 2 on, is the fuse blown, is the disk spun up, etc.).    3 .le; Keep computer room, tapes, materials organized   > One of the key ingredients in a successful computer system is I organization.  Without it, life will be nothing but chaos.  With it, the  / computer operation will run much more smoothly.    .le; Maintainance contracts   F All hardware and software eventually break.  Whether this is a law of K nature or just a paraphrase of Murphy's Law, I do not know.  However, when  G something does break, it will have to be fixed.  This is normally done        K thru maintainance contracts.  It is important that these contracts be kept  J up to date so that one, we have a way to fix the problem, and two, we can D keep to hardware and software up to date as changes are made to the 	 products.   F The operator should keep track of these contracts and keep the system I manager appraised of their status.  In this manner, the contracts can be   reviewed and renewed as needed.  .els   .ch VAX SYSTEM MANAGER .t ##########VAX SYSTEM MANAGER  .lm 10 .rm 70 .ap   K A good system manager is the corner stone for keeping a computer system up  D and running.  In essence, if there is a problem with the system, he H "knows" the answer.  The following list summarizes the system manager's  responsibilities:    .ls " .le; Responsible for entire system  I The system manager is responsible for the entire computer system.  Think  J about that for a moment.  If the system is down, then the users have lost                                                                       I the service of the system.  That also means that these users are costing  G the company money by not being able to do their job.  Thus, the system  F manager must take all necessary steps to insure that the hardware and I software function properly and that the system is up as much as possible.    .le; Guru for all software  I The system manager knows everything about all the software on the system. G This includes the operating system as well as the application programs.                               I Thus, if something doesn't work for a user, the system manager should be  J able to either fix it and make it work or show the user how to get around  the problem.   .le; Keep software up to date   F All software has bugs.  These bugs are fixed as they are discovered.  D Software purchased from vendors then have updates sent out to their K customers.  The system manager must install this updated software and test  F it to make sure it at least appear to work.  Software updates include                 = everything from the operating system to application packages.    .le; Good with hardware   E Although it is not necessary for the system manager to be a hardware  K technician, he should nonetheless understand the peripherals on the system  I so that he can make the initial diagnosis about problems when they occur. F This ability is a tremendous aid to the vendor's field service people 5 since it helps remedy the problem in a timely manner.   - .le; Teach classes on various areas of system             G The system manager must also be a teacher.  As new users come onto the  I system, they will need to know how to use it.  The system manager should  J be able to teach a wide variety of course from an introductory level thru I advanced as the need dictates.  He should also be able to show the users  H how to help themselves thru such things as the HELP command and thru CBI (Computer Based Instruction).    .le; Work with networks   D Since the eventual goal is to allow a single terminal access to the   K division's computer facilities, this means that the system manager must be  O able to work with networks.  This means not only understanding how the network  R operates and its various protocols, but also knowing how to debug to network when C it doesn't work plus understanding the interface packages used for  # communicating with other computers.    .le; Interface to purchasing  I The system manager will need to order supplies (paper, ribbons, etc.) as                                                  C well as new hardware and software.  He should therefore be able to  K interface to purchasing in order to buy these items.  This also means that  J he will have to obtain the necessary signatures to authorize the purchase  of these items.    .le; Capacity planning  G The system manager should monitor the system use in order to anticipate F when new hardware and/or software will be needed. The VAX system beingJ purchased has sufficient capacity to handle its expected use for the first                  E year or so.  But, as more users get onto the system and they run more I applications, the system will need additional hardware and/or software to E meet these needs.  These needs must be anticipated so that an orderly $ growth can be planned and budgeted.    .le; Management presentations H Management needs to be kept appraised of how their investment in the VAXK computer system is being utilized.  These presentations can cover a variety - of subjects.  Examples presentations include:  .s .lm +7 .i -2  o System utilization .i -2 ! o Who is using the system and how  .i -2 < o Software available and its effect on users doing their job .i -2 - o New hardware/software's effect on the users  .lm -7  J In general, the system manager should keep management informed about theirG VAX system and should be able to make presentations to management about = different areas of their system when requested by management.    .le; Manage user accounts                                                                 H User accounts give the users access to the system.  They also define theI privileges and limits for that user.  The system manager needs to keep a  H close watch over these accounts to make sure only authorized users have H active accounts, that privileges are granted only where needed, and that/ the users with privileges are not abusing them.   ! .le; Keep user community informed   A The users need to be informed about their system.  This includes                                                        J information about new hardware or software.  It also includes miniclasses J and seminars about different areas of the system.  A newsletter about new L things on the system could be mailed to each user via the MAIL utility thus B keeping the users informed and doing away with the paper normally  associated with newsletters.   .le; Interface with vendors   L The system manager should be able to work with different vendors to do such                                                                       J things as purchase new software, fix existing software and hardware, keep K maintainance contracts up to date, and, in general, serve as the interface  ) between Rockwell and each of the vendors.     .le; Must be a system programmer  L The system manager must be a system programmer.  He needs to be able to fix E software when it breaks.  This includes not only the exec and system  L software but user programs as well.  In essence, this goes along with point                                               8 made that he must understand all software on the system.  ! .le; Set up procedures for system   J The system manager is responsible for setting up the procedures to run theJ system.  These procedures may originate from the system manager himself orJ from the committee in charge of managing the VAX system.  These proceduresC cover such things as backing up the system, adding or deleting user B accounts, maintaining system security and handling system resource# allocation within the user groups.          + .le; Responsible for security and integrity   I Last but perhaps most importantly, the system manager is responsible for  D system security and integrity.  He must take precautions to prevent J breeches of security.  He must also take steps in insure the integrity of  the system and its software. .els