ALPHA MICROSYSTEMS RIGHT. FROM THE START. ALPHA MICROSYSTEMS RIGHT. FROM THE START. ALPHA MICROSYSTEMS RIGHT. FROM THE START. ALPHA MICROSYSTEMS RIGHT. FROM THE START. ALPHA MICROSYSTEMS RIGHT. FROM THE START. ALPHA MICROSYSTEMS RIGHT. FROM THE START. ALPHA MICROSYSTEMS RIGHT. FROM THE START. ALPHA MICROSYSTEMS RIGHT. FROM THE START. ALPHA MICROSYSTEMS RIGHT. FROM THE START. ALPHA MICROSYSTEMS RIGHT. FROM THE START. ALPHA MICROSYSTEMS RIGHT. FROM THE START. ALPHA MICROSYSTEMS RIGHT. FROM THE START.
© 1997 Alpha Microsystems REVISIONS INCORPORATED REVISION DATE 00 March 1988 01 April 1991 02 September 1996 03 May 1997 AMOS System Operator’s Guide to the System Initialization Command File To re-order this document, request part number DSO-000025-00. This document applies to AMOS 2.3A and later. The information contained in this manual is believed to be accurate and reliable. However, no responsibility for the accuracy, completeness or use of this information is assumed by Alpha Microsystems.
TABLE OF CONTENTS CHAPTER 1 - INTRODUCTION 1.1 WHAT IS A SYSTEM INITIALIZATION COMMAND FILE? . . . . . . . . . . . 1.2 GRAPHICS CONVENTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 1-3 CHAPTER 2 - WHAT DOES A SYSTEM INITIALIZATION FILE DO? 2.1 SAMPLE SYSTEM INITIALIZATION FILE . . . . . . . . . . . . . . . . . . . . . . . . 2-2 CHAPTER 3 - EDITING YOUR SYSTEM INITIALIZATION FILE CHAPTER 4 - DEFINING JOBS 4.1 DISPLAYING THE INITIALIZATION FILE ON BOOTUP (:T) . . . . . . . .
Page ii CHAPTER 6 - SETTING UP YOUR SYSTEM 6.1 SHARED MEMORY ALLOCATION (SMEM) . . . . . . . . . . . . . . . . . . . . . . 6.2 INITIALIZING MEMORY BOARDS (PARITY) . . . . . . . . . . . . . . . . . . . . . 6.3 THE SCSI DISPATCHER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4 DEFINING DEVICES (DEVTBL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.5 DEFINING DISK BITMAPS (BITMAP) . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.
Page iii DEFAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DELIMITER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISK DRIVE CONTROLLER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISK FILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DSK0: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CHAPTER 1 INTRODUCTION Almost every function of the System Operator requires you to be familiar with the system initialization command file. This manual introduces you to this most important part of your computer system. It answers these general questions: What is the system initialization command file? What makes up the system initialization command file? How do you modify the file to customize your system? 1.
Page 1-2 Chapter 1 A "command file" is a text file that contains system commands. When you call the command file, the monitor reads and obeys the instructions contained in the file. Each time the system is powered up or reset, the Alpha Micro hardware causes the monitor program—which has the system name and a .MON extension—for example, AMOSL.MON), to be loaded into memory and executed.
Introduction Page 1-3 1.2GRAPHICS CONVENTIONS This manual conforms to the other Alpha Micro publications in its use of a standard set of graphics conventions. We hope these graphics simplify our examples and make them easier for you to use. Any example that shows you pressing the RETURN key (see below) is a command entered at AMOS command level. We do not show an AMOS prompt symbol in these examples. The AMOS prompt defaults to a period (.), but may be set to any symbol or group of up to 19 characters.
Page 1-4 Chapter 1 SYMBOL MEANING {} Braces are used in some examples to indicate optional elements of a command line. In the example: DIR{/switch} the braces tell you /switch is not a required portion of the DIR command line. / The slash symbol precedes a command line switch or "option request." For example: DIR/WIDE:3 RETURN This command requests a directory display of the disk account you are currently logged into. The switch (/WIDE:3) indicates you want the display to be three columns wide.
CHAPTER 2 WHAT DOES A SYSTEM INITIALIZATION FILE DO? Later chapters will treat each of the points below in detail. initialization command file does the following: Briefly, however, the system Defines how many jobs will run on your computer, and gives them names. Performs any initialization required by the memory boards in your computer.
Page 2-2 Chapter 2 2.1SAMPLE SYSTEM INITIALIZATION FILE :T JOBS 3 TRMDEF ; PARITY TRMDEF TRMDEF TRMDEF TDVDEF ; Define number of jobs CRT0,AM100L=0,ALPHA,80,80,80,EDITOR=5 PRINTR,AM100L=1,ALPHA,80,80,80 MANAGR,PSEUDO,NULL,25,25,25 SRVTTM,PSEUDO,NULL,100,100,100 * JOBALC OPR,TASK,SERVNT ; DEVTBL DSK1 DEVTBL /VCR0 BITMAP DSK ERSATZ ERSATZ.INI MSGINI 16K ; SYSTEM SYSMSG.USA SYSTEM TRM.DVR SYSTEM VCR.DVR SYSTEM QFLOCK.
CHAPTER 3 EDITING YOUR SYSTEM INITIALIZATION FILE Your computer was delivered to you with a system initialization command file configured for the particular hardware that made up your initial computer. However, you will probably want to set your computer up in your own way by adding jobs, changing memory allocations, and so on. In addition, if you want to add a new piece of hardware, you will need to modify your system initialization command file to define the new device to the monitor.
Page 3-2 Chapter 3 If you did modify the file directly, and made a mistake, before you could again use the disabled disk as a System Disk, you would need to bring the computer up off of another System Disk or warm boot tape, and transfer over a copy of a good system initialization command file.
CHAPTER 4 DEFINING JOBS This chapter tells you how you set up jobs on your computer. A "job" is a "workplace" in memory that has a name for identification purposes, and has a terminal attached to it. 4.1DISPLAYING THE INITIALIZATION FILE ON BOOTUP (:T) The first line in a system initialization command file is usually :T. This tells the monitor to display the system initialization command file on a terminal as it is processing.
Page 4-2 Chapter 4 Specify an extra job for the use of the BACKUP command in your JOBS statement. At AMOS command level, the JOBS command tells you how many jobs have been allocated, and how many have been attached to terminals. 4.3ASSIGNING JOB NAMES (JOBALC) Once the maximum number of jobs is defined (by JOBS), you may assign names and allocate JCB’s (Job Control Blocks) to those jobs you wish to use.
CHAPTER 5 DEFINING TERMINALS The TRMDEF command defines a terminal to AMOS. Every terminal has a name (1 to 6 characters), a specific hardware interface, and a terminal driver (a program that does any necessary character conversions). The TRMDEF command also specifies the size of the various buffers used in the data transfers between the terminal and the computer.
Page 5-2 Chapter 5 5.1TERMINAL NAME The terminal name consists of one to six alphanumeric characters chosen by you. Every terminal on the computer must have a different name, although you may choose to use a terminal name that duplicates a job name or a program name. The computer uses the terminal name to identify the terminal you want to attach to a job or you want to access using the TRM device driver. 5.2INTERFACE-DRIVER The interface is the hardware board connecting the terminal to the computer.
Defining Terminals Page 5-3 5.2.1DISABLING SUPER I/O In AMOS 2.3 and later, Super I/O is enabled by default for all I/O boards which support it, such as the AM-318 and AM-359. However, if you have an application program that does not run properly on a Super I/O-enabled serial port, you can disable Super I/O.
Page 5-4 Chapter 5 5.3TERMINAL The terminal statement tells the computer what kind of terminal is connected to the interface board, and thus what kind of terminal driver to load into system memory from account [1,6] of the System Disk. Different terminals process characters differently. A terminal driver is the program that does the necessary code conversion and character processing required by the particular terminal that it supports.
Defining Terminals Page 5-5 5.3.4In-width The in-width statement specifies the maximum terminal line-width allowed before a carriage return. Allowing a large width, such as 100, gives an added margin of safety when typing long lines. 5.3.5In-buffer There are times when the computer cannot immediately process characters you type from the keyboard. Instead, it stores the characters in an input buffer until it can get around to them. The in-buffer statement specifies the size of this buffer.
Page 5-6 Chapter 5 5.5MODEM-DRIVER If you want the terminal defined to be able to work with a modem (using telephone lines to transmit data), enter the name of the modem driver program at the end of your TRMDEF line. If you have not specified the EDITOR option, remember to include an extra comma as a placeholder. Some examples: TRMDEF TERM1,AM355=1,ALPHA,100,100,100,EDITOR=3,MODEM.DVR TRMDEF TERM1,AM355=1,ALPHA,100,100,100,,MDM2.DVR 5.
Defining Terminals Page 5-7 where tcb-number is the number of TCBs to allocate. All the other parts of the line are the same as in normal TRMDEF statements. For example: TRMDEF #10 100,100,100,EDITOR=10 would allocate 10 TCBs for use by remote job connections, each with buffers 100 bytes long. Also, the line editor is enabled for all TCBs, with 10 recall buffers available. The number of TCBs allocated should be equal to the greatest number of remote connections on your system.
CHAPTER 6 SETTING UP YOUR SYSTEM This chapter discusses the commands you use to get your computer running, to set up memory, and to customize your system memory with the programs you use most often. 6.1SHARED MEMORY ALLOCATION (SMEM) The SMEM command allocates a shared memory pool for programs. The format is: SMEM size{K}{M} size is the amount of memory to allocate, K is Kilobytes, and M is Megabytes. You may put one and only one SMEM command in your .INI file.
Page 6-2 Chapter 6 6.3THE SCSI DISPATCHER All newer Alpha Micro computers (AM-4000, Roadrunners, Eagles, and later) use a SCSI dispatcher program to communicate with the SCSI controller chip. For each type of computer, there are two versions of the SCSI dispatcher: the "simple" dispatcher and the "enhanced" (PIC-encoded) dispatcher.
Setting up Your System Page 6-3 operate in non-synchronous mode only by entering a /N at the end of the command line. For example: SCZDSP SCZ190.SYS/N The SCZR60 dispatcher accepts several switches: Switch Meaning /EW{:id#} Enable wide SCSI operation for all devices or for just the device at SCSI ID id#. /NQ{:id#} Disable command queueing for all devices or for just the device at SCSI ID id#. /NS{:id#} Disable synchronous negotiation for all devices or for just the device at SCSI ID id#.
Page 6-4 Chapter 6 6.4DEFINING DEVICES (DEVTBL) Following the TRMDEF command lines is the DEVTBL command. It defines the devices your computer can access. You must always have at least one DEVTBL command line in the system initialization command file. The computer already knows the System Disk, DSK0:, is present, so don’t put DSK0: in the DEVTBL command line. If your computer has no devices other than DSK0:, enter DEVTBL alone on a line, and do not follow it with any arguments.
Setting up Your System Page 6-5 If you have three identical system drives, and each drive has 10 logical units, then you can define each physical drive as follows: DEVTBL DSK1-9 DEVTBL DSK10-19 DEVTBL DSK20-29 If you have identical SCSI drives divided into the same number of logical units, and they have consecutive SCSI IDs, you can identify all of them with a single DEVTBL statement.
Page 6-6 Chapter 6 the same controller. Also, several types of hard drives can run under the control of the same Hard Disk Controller—but because these devices are different sizes, each type may have to have its own name and bitmap area. See your System Operator’s Guide for information on hard disks. The BITMAP command specifies the name of the device the bitmap is for. AMOS then sets up the bitmap for that device.
Setting up Your System Page 6-7 You may find you need more queue space if your computer makes heavy use of the file locking system. The STAT program will show you the number of queue blocks available—if this number often drops below 20, you may want to allocate more blocks. The monitor initially contains 80 queue blocks; you may add more by using the QUEUE command in the system initialization command file. Place the QUEUE command before any SYSTEM commands.
Page 6-8 Chapter 6 There are two options available with the ERSATZ statement. The /B option lets you add blank entries to the ersatz definition list, so you can later use the ERSATZ command from command level to define additional ersatz names while the system is running. Normally, if an ersatz definition file contains an ersatz name that has already been defined (in a previous file), the new definition is ignored.
Setting up Your System Page 6-9 One of the common uses of SYSTEM in the system initialization command file is to include the AlphaBASIC runtime package (RUN.LIT or RUNP.LIT) in the monitor so each user does not need to load RUN into his or her own memory partition. You may also include the interactive compiler (BASIC.LIT) itself if you expect heavy development work by more than one user.
Page 6-10 Chapter 6 After the computer is up and running, the SYSTEM command performs a new function as a user command telling you what programs are in system memory and the total size (in decimal bytes) of the monitor. 6.9.1Including Device Drivers in System Memory All SCSI drivers for non-DSK devices, and all AM-219 device drivers, must be loaded in system memory.
Setting up Your System Page 6-11 dev is the name of the disk device you want to set up write buffering for. buffer-size is the size of the write buffer; flush-time is the maximum length of time data can be in the write buffer before being written to disk. For example: SYSTEM DVR:SUB/N 200K 30 This sets up write buffering for all drives using the SUB driver. The write buffer can hold up to 200K of data, and, even if the disk is busy, any pending data will be written to disk after 30 seconds.
Page 6-12 Chapter 6 6.9.3Front Panel Write Buffer Display If your computer has a front panel with three bar graph LEDs, you can use the LEDs to display write buffer usage for up to three device drivers. This command is only useful for SCSI disks which have had write-caching enabled. To enable this feature, use this SYSTEM statement: SYSTEM SCZWCD.SYS/N dev {dev} {dev} dev is the name of the device driver you want to display buffer usage for.
CHAPTER 7 FINISHING THE SYSTEM INITIALIZATION After the monitor processes the SYSTEM commands in the system initialization command file, the computer is technically up and running. There are a couple of things still left to do, however, before the initialization procedure is complete. You may now include any commands in the system initialization command file you want the monitor to perform automatically at the time of computer start-up.
Page 7-2 Chapter 7 7.2SETTING UP JOBS When the computer is reset or powered up, it automatically attaches the first job to the first terminal defined in your system initialization command file. Except for that special case, however, the computer does not automatically attach any jobs to terminals. If you want a job to be able to use a terminal for input and output, you must explicitly attach the job and the terminal. This process involves the use of such commands as ATTACH, KILL, FORCE, MEMORY, WAIT, etc.
Finishing the System Initialization Page 7-3 service calls or the general TRM driver. You cannot attach a job to a detached terminal from that terminal itself; you must do it from another terminal. To attach jobs and terminals, use the ATTACH command. Once a job is attached to a terminal, it uses that terminal for input and output. You can use the ATTACH command in several different ways: ATTACH Terminal,Job This command attaches the terminal and job named.
Page 7-4 Chapter 7 7.2.3Forcing Input to Jobs The FORCE command gives you a way of sending input to another job. To send one line of input to another job, use the FORCE command followed by the jobname and the input. For example: FORCE SANDI LOG DSK2:22,2 The line above logs SANDI into the computer under account DSK2:[22,2]. You can also send several lines of input to a job by entering a carriage return after the jobname.
Finishing the System Initialization Page 7-5 FORCE OLIVER MEMORY 32K WAIT OLIVER Once again, SETJOB will do this too! 7.2.5The VER Command When your computer boots, all of the keyboards connected to active terminals are "locked," preventing any signals from those keyboards from interfering with the booting process. You need to use the VER command to unlock the keyboard of each terminal defined in your initialization file. See the example in Appendix A. 7.
Page 7-6 Chapter 7 JOBALC LOGJOB TRMDEF LOGTRM,PSEUDO,NULL,100,100,100 ; ATTACH LOGTRM,LOGJOB KILL LOGJOB FORCE LOGJOB MEMORY 10K LOG SYSTEM SERVICE LOGGER 7 ; Name the job ; Set pseudo-terminal ; Initialize the job ; ; ; ; Force input into job Give job 10K Log job onto system Execute LOGGER ; Blank line above ends FORCE The background job that runs LOGGER needs at least 10K of memory. The 7 in the above example sets the minimum severity an event needs to have to get logged.
Finishing the System Initialization Page 7-7 7.7SETTING UP ALPHACD If you want an AlphaCD CD-ROM drive to be accessible to all users after booting, load ACD.DVR into memory using a SYSTEM statement. Then, if you want to mount all the CD logicals during bootup (be sure the CD is installed in the drive), enter this command after the last SYSTEM statement: ACD This makes all of the logical devices on the CD available. They do not have to be defined in a DEVTBL statement.
CHAPTER 8 TESTING YOUR SYSTEM INITIALIZATION FILE Once you have completed your initialization file, you need to test it to be sure it works correctly. This chapter explains the testing process, and shows you how to set up a minimal system initialization file. 8.1THE MONTST Log into the System Operator’s account (OPR:). Type MONTST, followed by the name of your System Monitor file, and the initialization file you wish to test. For example: MONTST AMOSL.MON,TEST.
Page 8-2 Chapter 8 8.3CREATING A MINIMAL FILE There are times during addition of new hardware to the computer or when troubleshooting an existing computer when it is handy to create a minimal system initialization command file. This is a system initialization command file that contains the minimum number of commands under which your computer will boot.
Testing your System Initialization File A MSGINI command. A SYSTEM SYSMSG.USA command (or other system message file). A final SYSTEM command with no arguments. A MEMORY 0 command at the end of the file. A typical minimal initialization file might look like this: :T JOBS 1 TRMDEF CRT0,AM355=0:57600,ALPHA,80,80,80 PARITY JOBALC OPR DEVTBL DSK1 BITMAP DSK SYSTEM SYSMSG.USA SYSTEM MOUNT DSK1: MEMORY 0 System Operator’s Guide to the System Initialization Command File, Rev.
APPENDIX A SAMPLE SYSTEM INITIALIZATION COMMAND FILE NOTE: The following sample INI file is based on an Eagle 300 system. Some line statements may not be applicable to your system configuration. The sample INI is only meant to show some of the various configuration methods, and a proper sequence of events. Be careful if using a SCSI dispatcher—you must use the correct version for your system, and you can only have one dispatcher enabled at any time.
Page A-2 SAMPLE SYSTEM INITIALIZATION COMMAND FILE TRMDEF TRM2,AM318=1:19200,AM62A,100,100,100,EDITOR=10 TRMDEF TRM3,AM318=2:19200,AM62A,100,100,100,EDITOR=10 TRMDEF TRM4,AM318=3:19200,AM62A,100,100,100,EDITOR=10 TRMDEF TRM5,AM318=4:19200,AM62A,100,100,100,EDITOR=10 TRMDEF TRM6,AM318=5:19200,AM62A,100,100,100,EDITOR=10 TRMDEF TRM7,AM318=6:19200,AM62A,100,100,100,EDITOR=10 TRMDEF TRM8,AM318=7:19200,AM62A,100,100,100,EDITOR=10 ; TRMDEF EPPA,PSEUDO,NULL,50,50,2 ; EPP0 parallel printer dummy TRMDEF EPPB,PSEUD
Sample System Initialization Command Files Page A-3 LOG OPR: SYSTEM SERVICE SET DSKERR SET HEX ; MOUNT DSK: ; Mount all DSK logicals ; SETJOB JOB2,TRM2,256K,JOBSET.INI ; Attach additional jobs SETJOB JOB3,TRM3,256K,JOBSET.INI SETJOB JOB4,TRM4,256K,JOBSET.INI SETJOB JOB5,TRM5,256K,JOBSET.INI SETJOB JOB6,TRM6,256K,JOBSET.INI SETJOB JOB7,TRM7,256K,JOBSET.INI SETJOB JOB8,TRM8,256K,JOBSET.
APPENDIX B GLOSSARY AMOS COMMAND LEVEL When you are at AMOS command level, you are communicating directly with AMOS (the Alpha Micro Operating System) and not with a program AMOS is executing. AMOS PROMPT When you’re at AMOS command level, you see the AMOS prompt symbol, which tells you the operating system is ready for you to enter a command. This prompt may be the system default, a period (.), or it may be defined using SET. BASIC Beginners All-purpose Symbolic Instruction Code.
Page B-2 CONTROL SEQUENCE GLOSSARY A control sequence is when you use the CONTROL key (sometimes labeled CTRL) in combination with other keys to affect what is occuring on your screen or during the execution of a command or program. To use a control sequence, hold down the CTRL key and press another key. One of the most common control sequences is Control-C, which is used to interrupt commands and programs. To do this, hold down CTRL and press C .
Glossary Page B-3 ECHO A response by your terminal to what you press on the keyboard. If you press a key (say the "a"), and you see a response on your terminal screen (an "a" appears), then your terminal is in ECHO mode (the normal way for it to be). Sometimes—for instance, when you are entering a password, the terminal echoing can be turned off, so what you type goes to the computer, but is not displayed on the screen.
Page B-4 GLOSSARY MOUNT The process of preparing a disk device for use. NON-SELF-CONFIGURING DISK A disk drive that must have a specific disk driver program made for it so it can communicate with AMOS. PHYSICAL ADDRESS A Winchester controller board has a certain number of fixed addresses, or ports, to which Winchester technology disk devices may be physically attached by cables.
Glossary Page B-5 SEQUENTIAL A type of file storage in which each item of data follows the previous item of data in order in the storage on the disk. Sequential data files are slower for data retrieval than random files, but are easier to access and work with. SPOOLING A method of sending a file to a printer queue, so it can await printing. SWITCH or OPTION Many AMOS commands and programs allow you to select among several options by including switches on a command line.
Page B-6 WILDCARD GLOSSARY A symbol that can represent a range of other characters. You might want to think of it as a joker in a deck of cards. For example, if you wanted to erase three files: FILE01.DAT, FILE02.DAT, and FILE03.DAT, you could type all this: ERASE FILE01.DAT RETURN ERASE FILE02.DAT RETURN ERASE FILE03.DAT RETURN or you could type: ERASE FILE0?.DAT RETURN where the question mark symbol "?" represents all characters, or: ERASE *.
Document History Revision 00 - AMOS Release 2.0 - (Printed 3/88) - New Document Adapted and separated from the AMOS System Operator’s Guide. Revision 01 - AMOS Release 2.2 - (Printed 4/91) Added information on separating the .INI file into more than two files to Chapter 3. Added a note to Chapter 4 about a JOB for BACKUP. Added information about terminal drivers to Chapter 5. Added information about shared memory and floppy disk buffered I/O to Chapter 6. Revision 02 - AMOS Release 2.
Index Page Index-1 INDEX .IDV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2 :T . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Account number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ACD command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Allocating memory to jobs . . . . . . . . . . . . . . . .
Page Index-2 Index Device drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Device independence . . . . . . . . . . . . . . . . . . . . . . . . . . . . Device-name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Devn: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DEVTBL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabling Super I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Index Page Index-3 Keycap symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 KILL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3 LOGGER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5 Logical device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3 MEMORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MEMORY 0 . . . . . . . . . . . . . . . . . . . . . . . . .
Page Index-4 Index Sequential . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SET TERMINAL DRIVER . . . . . . . . . . . . . . . . . . . . . . . . . SETJOB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sharable devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Index Page Index-5 Unlocking keyboards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5 User memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5 User name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5 VER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5 VTSER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6 WAIT . . . . . . . . . . . . . . . . . . . . . . . . . . .
