a 9|P^ CLUSTER COMMUNICATIONS SPECIFICATION GENERAL ------- The general protocol of the operating system dictates that the master workstation poll the cluster workstations, and that the master workstation and the cluster workstations exchange messages. The protocol requires that every workstation on the cluster communucations line (or all workstations in a minicluster) have a unique workstation identification number. The master workstation initiates all communications; a cluster workstation recognizes messages intended for it by the workstation identification number. The cluster workstation picks a workstation identification number by: o minitoring the cluster communications line to find an unused number o taking an unused number o monitoring the cluster communications line again to see if it has collided with another workstation that may have picked the same number If a collision occurs, both workstations wait a random time interval before restarting the search for another identicication number. The workstation identification number ranges from 1 to 15 (the largest number of cluster workstations allowed on a single cluster communications line). Identification numbers are not the same as user numbers. User numbers are assigned to cluster workstations by the operating system of the master workstation and are different for every workstation in a cluster. Identification numbers are determined by the cluster workstations and are duplicated on the different cluster communications lines of a cluster. PROTOCOL DEFINITION ------------------- The link-level cluster communications protocol is a subset of the American National Standars for Advanced Data Communications Control Procedures (ADCCP), as defined in ANSI X3.66-1979, published by the American National Standards Institute, Inc., using UN (Unbalanced Normal) Class of Procedure, Two-way Alternate transmission with optional functions 4, 5 and 6 (Unnumbered Information, Initialization and Unnumbered Polling) used for booting and dumping. The bootstrap/dump protocol is illustrated in Figure 1. Symbols are as follows: Symbol Function ------ -------- SNRM Set normal response mode RIM Request initialization mode SIM Set initialization mode XID Identification frame* UP Unnumbered poll UI Unnumbered data frame RD Request disconnect DISC Disconnect UA Unnumbered acknowledge UI' Unnumber data frame (with termination data) * XID sent by the cluster workstation has an I-field five bytes in length, containing the parameters desired by the workstation. (Refer to the "XID Command/Response I-Field Definition" sub-section, below.) Upon an XID of the format given in the "XID Command/Response I-Field Definition" subsection, below, the master workstation sends an XID of the same format, indicating the desired parameters, and expects to receive a UA in response. (This also occurs on a protocol startup not involving a boot or dump; for example, a local file system.) DUMP Master Workstation: Bootstrap ROM: SNRM -----------------------> SNRM -----------------------> SNRM -----------------------> <----------------------- RIM SIM -----------------------> <----------------------- XID XID -----------------------> <----------------------- UA UP -----------------------> <----------------------- UI * * * UP -----------------------> <----------------------- UI UP -----------------------> <----------------------- RD DISC -----------------------> <----------------------- UA BOOTSTRAP Master Workstation: Bootstrap ROM: SNRM -----------------------> SNRM -----------------------> SNRM -----------------------> <----------------------- RIM SIM -----------------------> <----------------------- XID XID -----------------------> <----------------------- UA UP -----------------------> <----------------------- UA UI -----------------------> * * * <----------------------- UA UI -----------------------> <----------------------- UA UI' -----------------------> Figure 1. Cluster Communications Bootstrap/Dump Protocol. When SYSGENed to run the line at 307 kilobaud to support B22 and B21 workstations, a master will not send XID; if the workstation does not receive an XID from the master, the workstation will assume the line is to be run at 307 kilobaud. Note that the RIM and XID that start off the bootstrap/dump sequence are always sent at 307 kilobaud; if XID negotiation so indicates, the parties then switch to the speed selected by the master workstation. XID COMMAND/RESPONSE I-FIELD DEFINITION --------------------------------------- Byte No. Function -------- -------- 0 OS type 1 Software revision level 2 Maximum line speed allowed 0 = 1200 baud 1 = 2400 baud 2 = 4800 baud 3 = 9600 baud 4 = 19.2 kilobaud 5 = 56 kilobaud 6 = 153 kilobaud 7 = 307 kilobaud 8 = 615 kilobaud 9 = 1.23 megabaud 10 = 1.54 megabaud 11 = 1.84 megabaud 3 Window size (default = 1) 4 Higher level protocol version: 0 = Current cluster, big reads split at cluster workstation (default) 1 = Current cluster, big reads split at master workstation 2 = BT-Net low interconnect 3 = BT-Net medium interconnect 4 = BT-Net high interconnect 5 Hardware type 0 = B22 1 = B21 2 = B25 3 = XE500 6 Error indicator2.@'@8ƢƂy&?؈ W ة , `mgƸ.Ҩ @ (P((!x,@@ !x,@ @ !x,@ x@!x,vx.=L[ṇ̵̑ &v@xvx@ (P((@@@ (  ()P xxxx Courier 72G@ "3.0.6. 9253 Printer Control Codes |----------------------------------------------------------------| | Command | Function code | Description | | | Decimal Hexidecimal | | | LF 10 0A Moves paper up one line | | CR 13 0D Returns print head | | FF 12 0C Feeds paper to the first line| | of next format (TOF). | | VT 11 0B Feeds paper to tab position | | Channel 49 to 31 to of same channel number as set| | No. 60 3C in VFU. | | DC1 17 11 Sets the printer in select | | (on-line) condition. | | DC3 19 13 Releases the printer from | | select condition. and sets it| | in deselect (off-line) cond. | | DC4 20 14 Loads tab position in VFU. | | RS 30 1E Designates 10 CPI | | GS 29 1D Designates 16.5 CPI | | US 31 1F Designates 5 CPI with RS | | Designates 8.3 CPI with GS | | ESC,VT 27,11 1B,0B Directly skips the designated| | 00 48,48 30,30 number of lines. | | to 99 to 57,57 to 39,39 | | ESC,F 27,70 1B,46 Designates the number of | | 00 48,48 30,30 lines for page length. | | to 99 to 57,57 to 39,39 | | ESC,5 27,53 1B,35 Sets TOF to Current Line | | ESC,6 27,54 1B,36 Designates 6 LPI | | ESC,8 27,56 1B,38 Designates 8 LPI | | ESC,A 27,65 1B,41 Designates long line | | ESC,B 27,66 1B,42 Designates short line | | SO 14 0E Shifts out character set in | | case of 7-bit code | | SI 15 0F Shifts in character set in | | case of 7-bit code | | CAN 24 18 Clears print buffer |2`ajl҅Ȍ£:d=aS}$]"Fp`@ſ @ 08p`  @ @,  ()P xxxxElite 12 Courier 72G@"3.0.7 Elite 12  () ~ ! @ # $ %  & * ( ) _ + ()( )() ^ 1 2 3 4 5 6 7 8 9 0 - = Q W E R T Y U I O P  < > | \ q w e r t y u i o p  [ ] 7 8 9 A S D F G H J K L : " { } a s d f g h j k l ; ' 4 5 6 - Z X C V B N M , . ? ` z x c v b n m , . / 1 2 3 Those characters enclosed in ( ) are not available on this print wheel. 2 ac @ @F@G@@@@@@'@(@b@@@@@@@`@a@cac@ ,  ()P xxxxElite 12G@ca"3.0.7 Disk Structures Overview The base element of the BTOS file system is a 512 byte sector which is defined either by logical file address (lfa), or by a cylinder, head and sector number. One or more contiguous sectors comprise a disk extent, which is definable by its starting lfa and its length. Files consist of one or more disk extents. A lfa is used to locate a particular sector of a file. It specifies the byte position within a file; that is, it is the number (the offset) that would be assigned to a byte in a file if all the bytes were numbered consecutively starting with zero. A lfa is 32 bits in length. Bits 0-29 of the lfa define a disk address, bit 30 can be set to suppress retries, and bit 31 can be set to override normal system checks to access defective disks. Files are grouped into user-defined sets called directories, such that a file may belong to only one directory. A disk, or volume contains at least one directory (sys), which minimally contains the files which describe the disk. The number of directories per volume, and the number of files per directory are finite numbers set at volume or directory creation time. Hierarchy The root structure of the file system is the Volume Home Block (VHB), which contains pointers to the other structures of the file system. Two VHB's are allocated at initialization time, one at lfa zero and one at mid-point on the volume. The VHB contains the lfa of the Master File Directory (MFD), which defines the volume's directories. Each active entry in the MFD contains the lfa of its directory, which is a hashed table of file names and their pointers into the File Headers. Each file is allotted at least one entry in the File Headers. This entry defines up to 32 disk extents of which the file is comprised. In the rare case that a file requires more than 32 extents, file headers are chained. The base address of the File Headers is also found in the VHB. There exists the option to write secondary, or backup file headers, to be used in the event that the primary is unreadable. (Secondary file headers is the default option in the standard volume initialization). The secondary headers are placed after every N primary headers, where N is defined in the VHB as AlternateFileHdrPageOffset. The VHB also keeps track of the next free file header, and the total number of free file headers. +----------+ +-----------+ | |-------------------->|-----------| | | |-----------| | Volume | | File | | Home | | Headers | | | | | | Block | |-----------| | | |-----------| | |->+-----+ +-----+ | . | | | |-----|->| DIR |->| . | | | |-----| +-----+ | . | | | | . | +-----+ | . | | | | . | | DIR | | . | | | | MFD | +-----+ | . | +----------+ +-----+ +-----+ +-----------+ | DIR | +-----+ . . . Figure 1 Figure 1 illustrates that the Volume Home Block has a pointer to the first sector of the File Headers, as well as to the first sector of the Master File Directory. Each Directory has entries for all the files in the directory and a pointer to the File Header which describes the file. Each File Header has pointers to the extents of the file. The other structures which comprise the file system are the Bad Block File (BadBlk.Sys), which keeps a count of bad spots by cylinder/head/sector address, and the Allocation Bit Map, which contains a bit for every disk sector. The bit is set if the sector is available. The Volume Home Block The VHB contains the locations and sizes of the other structures which comprise the BTOS file system as well as pointers to other system files such as the operating system (sysImage.sys), crash dump file (crashDump.sys), log file (log.sys), etc. BTOS initialization writes two Volume Home Blocks per disk, one at logical file address zero and one at a mid-point on the media. The VHB is accessible by reading lfa zero, by calling the BTOS function GetVHB, or by accessing the pointer to the memory resident VHB found in the Device Control Block (DCB). The VHB itself has no entry in the File Headers. Offset Size Field 0 2 Checksum See Appendix. 2 4 lfaSysImagebase Address of the first sector of the operating system. 6 2 cPagesSysImage Size in sectors of the operating system. 8 4 lfaBadBlkbase Address of the first sector of the bad sector file (badBlk.sys). 12 2 cPagesBadBlk Size in sectors of the bad block file . 14 4 lfaCrashDumpbase Address of the first sector of the crash dump file (crashDump.sys). 18 2 cPagesCrashDump Size in sectors of the crash dump file. 20 13 VolName Volume Name; first byte contains the count of bytes in the volume name. Offset Size Field 33 13 volPasssword Volume Password; first byte contains the count of bytes in the Password. 46 4 lfaVHB Address of the first sector of the second (active) VHB. 50 4 lfaInitialVHB Address of the first sector of the first (backup) VHB. 54 4 creationDT The date of initialization in System Date/Time format. 58 4 modificationDT The date of last modification in System Date/Time format. 62 4 lfaMFDbase Address of the first sector of the Master File Directory. 66 2 cPagedMFD Size in sectors of the MFD. 68 2 lfaLogbase Address of the first sector of the system log file (log.sys). 72 2 cPagesLog Size in sectors of the system log file. 74 2 currentLogpage The sector offset from lfaLogbase where the current log entry is to be written. 76 2 currentLogbyte The byte offset within currentLogpage where the current log entry is to be written. 78 4 lfaFileHeadersbase Address of the first sector of the File Headers The Volume Home Block (cont). Offset Size Field 82 2 cPagesFileHeaders Size in sectors of the File Headers. 84 2 altFileHeaderPageOffset The number of file headers that separate a primary file from its secondary file header. 86 2 iFreeFileHeader The offset from lfaFileHeadersbase to the next available file header. 88 2 cFreeFileHeaders The total number of unused file headers. 90 2 clusterFactor Not used. Contains a 1. 92 2 defaultExtend Not used. Contains a 1. 94 2 allocSkipCnt Not used. Contains a 1. 96 4 lfaAllocBitMapbase Address of the the first sector of the allocation bit map. 100 2 cPagesAllocBitMap Size in sectors of the allocation bit map. 102 2 lastAllocBitMapPage When combined with lastAllocWord and lastAllocBit, forms a pointer into the bit map for the next available sector. 104 2 lastAllocWord see lastAllocBitMapPage 106 2 lastAllocBit see lastAllocBitMapPage 108 4 cFreePages Total number of unallocated sectors. Offset Size Field 112 2 iDev Offset into the array of device control blocks. 114 105 rgLruDirEntries An array of the three Last Recently Used MFDs (35 bytes each, see MFD structure). 219 2 magicWd Used to calculate the checksums for the Volume Home Block and the File Headers. Value is 7C39. 221 1 SysImageBaseSector 222 1 SysImageBaseHead 223 2 SysImageBaseCylinder 225 2 SysImageMaxPageCount The above fields describe for the bootstrap ROM the location and file size of the program to be bootstrapped. 227 1 BadBlkBaseSector 228 1 BadBlkBaseHead 229 2 BadBlkBaseCylinder 231 2 BadBlkBaseMaxPageCount The above fields describe the location of the Bad Block map used by IVolume when reinitializing a volume. 233 1 DumpBaseSector 234 1 DumpBaseHead 235 2 DumpBaseCylinder 237 2 DumpBaseMaxPageCount The above fields describe the location and file size of the crashdump area to be used by the Bootstrap ROM when a memory dump is performed. The Volume Home Block (cont). Offset Size Field 239 2 BytesPerSector 241 2 SectorsPerTrack 243 2 TracksPerCylinder 245 2 CylindersPerDisk The above fields describe the physical characteristics of the disk drive. 247 1 InterleaveFactor see Sector interleaving 248 2 SectorSize 250 1 SpiralFactor see Sector spiraling 251 1 StartingSector The above four fields describe formatting parameters used by IVolume. 252 4 Reserved for expansion. The Master File Directory. The master file directory contains hashed entries for each directory on the volume. An entry for the MFD exists in the file headers under the file name "Mfd.Sys". The sector address of the MFD is found in the Volume Home Block, as is its length in sectors. Up to fourteen entries can be stored in each sector of the MFD, and each sector has a one byte header before the MFD entries begin. MFD entry: Offset Size Field 0 13 DirectoryName Name of the directory; first byte contains the count of bytes in the directory name. Offset Size Field 13 13 DirPassword Name of the password; first byte contains the count of bytes in the password name. 26 4 lfaDirbase Address of the the first sector of the directory. 30 2 cPages Size in sectors of the directory. 32 1 defaultAccessCode Password protection level of the directory. 33 2 lruCnt Last recently used count; the last used directory has a zero lruCnt. The other directories lruCnts are incremented when a file is accessed which does not belong to the directory. MFD sector: Offset Size Field 0 2 Header 2 490 rgMFDentries(14) an array of fourteen MFD entries described above. The Directory The Master File Directory contains the sector address and the sector size of all the directories on the volume. The Directory has no entry for itself in the File Headers and so may be accessed only through the Master File Directory itself. File names are hashed into the list using the algorithm described in the appendix. All other bytes in the list are set to zero; a sequential search for files within the directory searches for the first non-zero byte, signifying start of entry. The Directory (cont). Offset Size Field 0 1 cbFileName The count of bytes in the filename. 1 cbFileName The File name. 1+cbFilename 2 FileHeaderOffset. The offset from the start of the file headers to the entry for this file. File Headers The File Headers contain primary, and optionally, secondary file headers. Secondary file headers reside N sectors past the primary file header, where N is "AltFileHeaderPageOffset" as described in the VHB. Non-active file headers contain a zero length in the file name field. Since there is no notion of the "last" active file header, the file headers are rarely read sequentially - rather the Directory entries are searched for a pointer to the file headers. The file headers reside in a file describing itself called "FileHeaders.Sys". Offset Size Field 0 2 checksum see appendix 2 2 FileHeaderPageNumber. The sector offset from the start of the file headers of the primary file header. 4 51 sbFileName. File name, the first byte contains the length of the file name. If the first byte is zero the file header is inactive. 55 13 sbFileNamePassword. File password, first byte contains the length. Offset Size Field 68 13 sbDirectoryName. Directory name the file is located in. The first byte contains the length of the name. 81 2 FileHeaderNumber. The sector offset from the start of the file headers of the primary file header. 83 2 ExtensionFileHeaderNumber. The sector offset from the start of the file headers of the extension file header in the case of a file with more than 32 extents. 85 1 bHeaderSequenceNumber. Sequential number assigned to extension file headers. 86 1 bFileClass. Not Implemented. 87 1 bAccessProtection. File protection level. 88 4 lfaDirPage. Sector address of the master file directory entry for the file's directory. 92 4 CreationDate. 96 4 ModificatioDate. 100 4 AccessDate. 104 4 ExpirationDate. Not implemented. 108 1 fNoSave. Used by the BackUp Volume utility to determine whether to backup the file. Set to TRUE for FileHeaders.Sys, Mfd.Sys, etc. 109 1 fNoDirPrint. Not Implemented File Headers (cont). Offset Size Field 110 1 fNoDelete Set to TRUE for system files which should not be deleted. 111 4 cbFile Size of the file in bytes. 115 4 defaultExpansion The sector size by which to expand the file if a new extend is to be created. 119 2 iFreeRun Index into the rgLfaExtent and rgoExtent tables below of the next available empty extent. 121 128 rgLfaExtents. Array of 32 sector addresses of the file extents. 249 128 rgcbExtents Array of 32 byte lengths of extents, where the length is a multiple of the sector size. 377 71 Reserved 448 64 application specific field Bad Block File The Bad Block file records up to 128 bad sectors on the volume. Its lfa is contained in the VHB, and its length is always one sector. For information on converting cylinder, head, and sector addresses into a lfa, see appendix. Offset Size Field 0 128 rgbBadSector Array of 128 bytes defining the sector number of the first 128 bad spots. 128 128 rgbBadHead Array of 128 bytes defining the head number of the first 128 ad spots. Offset Size Field 256 256 rgwBadCylinder Array of 128 words defining the track number of the first 128 bad spots. Allocation Bit Map The lfa and size of the Allocation Bit Map is described in the VHB. Each bit in the map describes the availability of one sector on the volume; the bit is set to on if the sector is available. Since the bit map has no entry in the file headers, and hence no end of file description, it can be read successfully by determining the total number of sectors on the volume (this information can be extrapolated from the Device Control Block), and reading only the first nSectors/8 bytes of the bit map. (The DCB is described in the "Memory Structures", below). Memory Structures Overview Information about the disk devices available to the system is found in the Device Control Blocks which describe the characteristics of the device (eg, tracks, sectors, sector size, number of retries), as well as the name and password. The DCB also contains an offset to the memory resident VHB for the device, and offsets to the first and active IO Blocks for it. The pointer to the offset to an array of offsets to the system DCBs is located at 27Ch (in the System Common Address Table, described in the BTOS manual). The number of DCBs is a sysgen parameter. When a request to open a file is issued, the OS allocates a File Control Block, does a search of the file header block for the filename, and loads the file header number of the file into the FCB (a new file header number is returned if the file did not previously exist). The lfa's and sizes of the file's disk extents are read from the file header and loaded into a linked list of File Access Blocks; the FCB remembering the first FAB. Also a File User Block is allocated which contains a pointer to the FCB and contains the user number. A file handle is assigned to the file and returned to the caller for subsequent operations as an offset to the correct FUB. The User Control Block associated with the task contains a pointer to an array of offsets which point to the FCB's of the task. Pointers to the offset of an array of offsets to FCBs and UCBs are stored in the System Common Address Table (SCAT) at addresses 280h and 284h respectively. (Note: these offsets must be combined with the segment address of DGroup of the Operating System, which is found at 242h of the SCAT). The number of FCBs and FABs are sysgen parameters: the number of FCBs should be equal to the number of files to be open at one time; the number of FABs is a factor of the number of FCBs and how fragmented the volume becomes (i.e., disk extents per open file). Device Control Block The DCB can be accessed via the BTOS call "QueryDCB", or through the pointer in the SCAT described above. Offset Size Field 0 1 fMountable 1 1 fNonSharable 2 1 fDoubleDensity 3 1 fNoMultiTrack 4 1 fAttention 5 1 fTimeout 6 13 sbDeviceName 19 13 sbDevicePassword 32 1 controllerNum 33 1 iUnit 34 1 state 35 1 unitStatus 36 1 deviceClass 37 1 cUsers 38 2 oVHB 40 2 oIOBfirst 42 2 oIOBactive 44 4 lfaMax 48 4 lfaMask 50 2 verifyKey 52 2 ovlyProcOpen 54 2 ovlyProcClose 56 2 cRetryMax 58 2 cSoftSectors 60 2 cHardErrors Offset Size Field 62 2 currentCylinder 64 1 sectorSizeCode 65 2 GapLength 67 1 DataLength 68 2 BytesPerSector 70 2 SectorsPerTrack 72 2 TracksPerCylinder 74 2 CylindersPerDisk File Access Block Offset Size Field 0 2 oChainFAB 2 4 lfaDiskExtent 6 4 sizeDiskExtent File Control Block Offset Size Field 0 2 oFAB 2 2 devNum 4 2 userCount 6 2 openMode 8 2 FileHeaderNum File User Block Offset Size Field 0 2 oFCB 2 2 userNum 4 1 fhStatus Appendix Sector Spiraling Spiraling is a performance mechanism of the floppy device driver on the B20 Series used to reduce the wait time for a sector to come under the head when the head must switch tracks or diskette sides. During the time the head switches or seeks the next track approximately 3 sectors have spun past it; to avoid waiting for the next cSectorsPerTrack-3 to spin past the head, the first sector of the next track/head is assigned the sector number of nSectorPrevTrack+3. The first three tracks of a B20 16 sector diskette are shown below: Physical Sector Position 1 1 1 1 1 1 1 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 1 1 1 1 1 1 1 Track 1 1 2 3 4 5 6 7 8 9 1 1 2 3 4 5 6 1 1 1 1 1 1 1 1 Track 2 4 5 6 1 2 3 4 5 6 7 8 9 1 1 2 3 1 1 1 1 1 1 1 Track 3 1 2 3 4 5 1 1 2 3 4 5 6 7 8 9 0 Sector Interleaving Interleaving is a sector mapping technique used on B20 winchesters to match the spin speed of the disk to the disk controllers's ability to read sectors. Since 3 sectors spin by the head in the time it takes the controller to be ready to read the next sector. Sector numbers are assigned which are three past the last physical position read. The sectors of a track of an interleaved disk are shown here: Physical Sector Position 1 1 1 1 1 1 1 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 1 1 1 1 1 1 1 Track 1 1 4 7 0 3 6 3 6 9 2 5 2 5 8 1 4 Hashing Algorithm The following hashing algorithm is used to place and locate entries within the Master File Directory and the Directories to determine the sector within which the entry resides. The arguments the hasher takes are name (directory or file) and the size in sectors of the table (Mfd.cDirectory or Vhb.cMfd). "Name" is an array[1..n] of bytes; "Divisor" is the size in sectors of the structure; "n" is the length of Name; "b" is a byte; "x" is a word; x := 0; For i := 1 to n do begin b := name[i]; if b >= 'a' and b <= 'z' then b := b-#20; {make upper case} x := 73*x+b; end; hashSectorNumber := x Mod Divisor; Checksum Algorithm The Volume Home Block and the File Headers use this checksum, however the VHB checksums the first 128 words only, while the FHB checksums 256 words. The value of magicWord is 7C39h, and can be found in the VHB. "w" is a word; "nLastWdSector" is the number of words to checksum; "wBuffer" is the sector to be checksummed; w := magicWord; for i := 1 to nLastWdSector do w := w - wBuffer[i]; if w <> 0 then erc := ercBadCheckSum; Appendix Computing Lfa's from head/cylinder/sector. The algorithm for computing a logical file address (lfa) given the cylinder, head, and sector number (where sector number is zero based) is : Lfa = ((cylinder * Dcb.TracksPerCylinder + Head) * (Dcb.SectorsPerTrack * Dcb.BytesPerSector)) + ((iSector-1) * Dcb.BytesPerSector). Terminology Prefix Meaning lfa logical file address, 4 bytes in length. sb character string where the first byte is the length of the string. p memory pointer, 4 bytes; most significant word is segment address, least is offset. o offset, the register address portion of a pointer rg array of. c count of, displaces a word. b byte. (note that words are in Intel format, most significant byte last) 2 _ BTOS File System _ Page # EP‘†ې¿£kwšVyך@ 0 @ 0 @  ( !$%<&()<*,7'vى¨"|߷Xk}|@ @ @ 0 * !$%<&()<*,67'vىww׶ @ 0  (D@ 0 (D@ (D ( !$%<&()<*,7'vى  @GIMNS1|ڻLڨ@TڲDڍ,YکHڲ?* !$%<&()<*,67'vى@ $  #7@  7 ')-.34 4@  7 @  P  Bl ( !$%<&()<*,7'vى˜¡¦f>εS΀έ/u3`ΘVΡκwΎΣμgf@  7 * !$%<&()<*,67'vى@ $  #7')-.35 5@  7 @  P  Bl ( !$%<&()<*,7'vى ™ҴCNVX\]bc/IέxΙ޵_BNOc@  7 @ 0 @ 0 @  P  Bl @ $  #7krtxy~gk+[fsj@   ":@  7 * !$%<&()<*,67'vى@ $  !7  xÇs -x{ts@ 0 @  P  Bl @   ): @   ":%)0566@  7 @  P  Bl ( !$%<&()<*,7'vى $&*+01Gp1@  7 @ 0 @ 0 @  P  Bl @ l  #7_fhlmrЉ_sMFjЛ';d^@  7 * !$%<&()<*,67'vى@ $  #7  $%*++)@  7 @  P  Bl ( !$%<&()<*,7'vى 9H/68<=BLvIΔ9HI/C@ $  7@  7 @ 0 @  P  Bl @ $  #7 xwxؐ@  P  Bl@ $  7@  7 * !$%<&()<*,67'vى E`ҭ%Q`1C ] d f j k p q Eaٔ٭ ] q  @  7 ( !$%<&()<*,7'vى@ 0 @  P  Bl $¢«°]^"6IYgzΒΦβξ '5EXl|ΐ΢-E\]^y @  7 * !$%<&()<*,67'vى@  P  "6 !&_rsz|ՀҁՆ'6I]_sއ @  P  "6@  7 @  P  Bl    h 6Ekh @ @ 0  @ * !$%<&()<*,7'vىŸܲ³Ht@ 0 <@  @ 0 @  * !$%<&()<*,67'vى¤ϭ@ * !$%<&()<*, 7{@  <@ 0 <@ 0 < +,GST[\d͝+,׻FSTd2gtu@ ` (Z@ (Z @ 0 <@ <@ 0 <@  CEFįBC@FCEݨ@ ,@  ,@ h <Z@ (Z  ((()P xxxx Letter Gothic 15G BPePA)"10.3%Z"$%''*0>0<44%?ABIKM"P Section 1: Introduction Operating Systems An operating system is that part of the computer's software, or programming, that supervises the running of individual programs. An operating system serves you by performing many important basic functions, including loading programs to be executed, enabling concurrent execution of two or more programs, scheduling different processes within the system, and providing management of information. B25 System Software The B25 system software is interactive; that is, you communicate with the system by entering commands. The system responds to each command by displaying a command form, which requests additional information. The function of the B 25 Operating System (BTOS) can be accessed by application programs like Multiplan, the B25 Executive, or system utilities. The B25 Executive is a special program that acts as an interface between you and the operating system. It also performs tasks such as copying, renaming or deleting files, creating directories, setting security, and running programs. Files, Directories, and Volumes The B25 organizes storage for data and programs into volumes, directories, and files. A volume is a floppy disk or a hard disk that has been formatted and initialized to store data or programs. You organize each of your volumes into units called directories. A directory is a group of related documents, programs, or other data stored on a volume. You organize directories into units called files. A file is a document, program, or other set of related data within a directory. You can think of the B25 file system as an office: each volume is like a file drawer, the directories within each volume are like the file folders in that drawer, and the files within each directory are like the documents in each file folder. Directories and files provide an index for the volume. You can list the directories contained within a volume by using the Volume Status command, and you can list the files within a directory by using the Files command. Volume Names You can assign a volume name that is descriptive of the volumes contents. For example, a floppy disk containing accounting files can be designated Accounting, and one containing John Smith's files can be designated JohnSmith. You can assign the volume name when you initialize a volume, but you can also assign it with the Change Volume Name command. Volume names can contain up to twelve alphanumeric characters, a period, and/or a hyphen. You can also use other symbols, including [, +, =, <, &, and @; however, it is not recommended. In addition, you can refer to a volume by the default name of the disk drive in which it is mounted, regardless of its assigned name. Typically, the default volume name is one of the following: [D0] The first hard disk drive. [!D0] The first hard disk at the Master workstation. [F0] The first floppy disk drive. [f1] The second floppy disk drive on a system with two floppy disks. Section 2: Using the Executive From this point on you will interact with the system through a series of commands and responses, using the Executive to activate the functions of the B20 Operating System (BTOS). To enter an Executive command, specify the command name in the field next to the command prompt, which appears on the screen, as follows: Command _______________________________________ Pressing the HELP key once displays a list of all available commands; pressing it twice displays a brief explanation of each command. The HELP key is located in the first column of keys on the left side of the keyboard. Enter a command name (or an abbreviation of a command name) to complete the command prompt field. You need enter only as many characters of the command name as necessary to uniquely identify it. Press RETURN to display the command form (you can also use the Down Arrow, TAB, or NEXT keys). Fill in the command form's parameter fields, then press GO to execute the command. A complete description of all the standard commands is contained in the manual titled, B20 Systems Standard Software Operations Guide. Volume initialization IVolume The IVolume (Initialize Volume) command prepares a floppy or a hard disk for use as a B25 volume. IVolume formats the disk, performs write/read tests to identify surface defects, writes volume control structures onto the disk, and creates system files. When initializing a floppy disk, the system prompts you to mount the disk. It also recognizes whether the volume has already been formatted and requests confirmation before reinitializing a disk containing valid volume information. IVolume does not allow you to initialize a volume currently in use. At the Command line type in IVolume and press Return. Fill in the IVolume form using the example below. IVolume Device name F0 [Device password] Volume name Your last name (Note: 12 letters Max.) [Volume password] [System Image (default = 384)] 0 [Log file (default = 2)] 0 [Crash file (default = 0)] [Max. directories] [Max. files on volume] [Primary file headers only?] [Max. files in Sys Directory] [Sys Directory password] [Write protect Sys Directory?] [Suppress format of medium?] [Surface tests] 1 [Debug?] [Log file] [Extended floppy tracks?] [Hard disk type code (def = A)] [Bad spots (See Documentation)] Press the GO key. When the computer prompts you, make sure you have inserted the disk and then press GO. The B25 will now prepare your floppy disk for data storage. This process takes about 3 minutes to complete. During this process the B25 will test the surface of your disk for defects. If any bad spots are found the B25 will tell you where they are on the disk. (It is recommended that if a disk contains more than 10 bad spots that you consider discarding the disk.) Create Directory The Create Directory command allows you to create a new directory on the volume of your choice. Directories are the way to organize your data on a disk. On the command line type C D and press Return. Fill in the Create Directory form using the example below. Create Directory New directory name [F0]WorkSpace [Protection level (default = 15)] [Maximum number of files (default = 45)] 100 [Password for new directory] [Volume password] If you do not enter a volume name then the directory will be created on your default volume. The recommended number of files is 100 if this disk is to be used to contain WRITEone documents. Create another directory on the floppy disk using the example below. Create Directory New directory name [F0]Letters [Protection level (default = 15)] [Maximum number of files (default = 45)] [Password for new directory] [Volume password] NOTE A specialized command has been created that combines the two commands Ivolume and Create Directory. It is named the Make Floppy command. You may use this command to automatically initialize a floppy an create a directory called workspace. Volume Status The Volume Status command displays the status of the specified disk volume or of the specified volume mounted on the specified disk drive. This command can be used to determine the names of the directories on a volume and also to see how much space (free sectors) is left on a volume. Below is an example of a volume status. Volume Status [Volume or device name (e.g., Accounting)] f0 Status of volume Pascal <--Volume Name Created Jul 5, 1985 7:35 PM Last modified Jul 7, 1985 9:41 PM Number of free sectors 78 <-- Unused sectors Number of free file headers 39 <-- Number of files that can be created Directory Name Sectors Default Protection SYS 3 15 <-- Names of the ActCopy 3 15 Directories on this DcSend 3 15 Volume Functs&Mods 3 15 MakeCmds 3 15 MakeFmtSet 3 15 Misc 3 15 Printers 3 15 Pictures 3 15 ReadDisk 3 15 ScreenDumper 3 15 SystemStatus 3 15 WriteLog 3 15 Execute a volume status command on the floppy disk you have created. On the command line type Volume Status and press Return. Volume Status [Volume or device name (e.g., Accounting)] F0 Press GO. Observe the Volume name and the names of the directories. Section 3: Working with files File Specification File name B25 programs and data are stored in files. A file is a set of related items stored as a unit in a directory on a single disk volume. Each file has a unique name, which should describe the contents of that file and be meaningful to you. A file name can contain up to 50 alphanumeric characters including upper- and lowercase letters, periods, hyphens, and right angle bracket (>). NOTE Although other special characters ([, +, =, <, &, @) are allowed in file names, their use is not recommended. File Extension You can add a file extension to each file name to further identify the type of file. A file extension consists of a period (.), followed by three or four alphabetic characters, appended to the end of the file name. Some commonly used file extensions are the following: .Run Run file (a program) .Sub Submit file .Sys A system file .Lst A list file .Txt A text file .mp A Multiplan file Complete file specification The file specification is one of the most frequently used parameters in B25 commands. A complete file specification uniquely defines a particular file within a specific directory and volume. It has the following form: [volume name]file name The right square bracket (]) and the left and right angle bracket (<>) characters cannot have any spaces before or after them. Use the complete file specification when you want to access a file in a different volume or directory than the one in which you are currently working. Default Volume and Directory Specification When you specify a file name only, the system assumes that the file is located in the current volume and directory. The [volumename] and default to those displayed in the upper left corner of the Executive screen as follows: Path: [volumename] The Path display shows the route that the operating system takes to access the file you are currently working with, showing the disk volume (hard or floppy) and the specific directory located on that volume. To access a file in another directory, you must specify the directory as well as the file name; to access a file in another volume, you must provide the complete file specification, including volume, directory, and file name. For example, if you are currently signed onto the directory on the volume [Accounting], entering the file specification Expenses is equivalent to entering [Accounting]Expenses To specify a file in another directory (for example, ) on the same volume, you must include the directory name; for example Expenses is equivalent to [Accounting]Expenses To specify a file in another volume (for example, [Purchasing]), you must enter the complete file specification: [Purchasing]Expenses It is often convenient to refer to volumes by the device name of the disk drive on which they exist. For example, you can specify any floppy disk inserted in the system's first floppy drive by entering the device name [f0], instead of its individual [volumename]. Path The Path command allows you to change your default Volume and/or Directory (Workarea). On the command line type path and press Return. Fill in the Path form using the example below. Path [Volume] D0 [Directory] WorkSpace [Default file prefix] [Password] [Node] Press GO. Observe in the upper left corner of your screen that your path has changed to the new value you entered. Path: [d0] Copy The Copy command is used to copy one file to another. On the command line type copy and press Return. Fill in the copy form using the example below. Copy File from Example.file File to [f0]Example [Overwrite ok?] [Confirm each?] This will copy the file [d0]Example.File to [f0]Example. Observe that it is not necessary to specify [D0] as this is your default path. If only a file name is given to the computer it will assume you mean a file in the default path. Execute another copy command using the example below. Copy File from [f0]Example File to [f0]Example [Overwrite ok?] [Confirm each?] This puts a copy of the file Example into the directory Letters. The Wild Card Character You can replace the file name or the directory name with an asterisk (*) in the complete file specification. The asterisk is a wild card which represents any character or group of characters. If you specify a wild card in the file name instead of a complete file name, the system expands the wild card into a list of file names which match the remainder of the file specification. For example, if you enter the file name E*, the system searches for all files in the current directory beginning with the letter E; if you specify the file name as E*S, the system searches for all files in the current directory beginning with E and ending with S, and so on. You can use a question mark (?) as a wild card to represent a single character instead of a string of characters. For example, if you enter a filename E?.Lst, the system searches for the files in the current directory beginning with the letter E, end with the suffix .Lst, and have only one character in between (for example, Ea.Lst, Eb.Lst, etc.). When you enter a specification containing a wild card in a parameter field, the system replaces it with the list of matching files as soon as you press RETURN. Exceptions to this rule are Copy, Files, and Rename commands, which do not expand the wild card characters until you press GO. Parameters you enter in a command form can include a file specification with an asterisk (*). For example, you can enter the Files command with the following parameters: Files [File list] Test <*>Wp.ts Personnel* [Details?] [Print file] This has the system search for the file Test, all files with the name Wp.ts in all directories, and all files in the current directory with names starting with Personnel. NOTE Use extreme caution when specifying wild cards with the Delete command. Files The Files command allows you to search a volume or a directory for a specific file or a list of files. There are two wild card characters (* or ?) that can be used to perform a general search. Some examples to try are below. Files [File list] [f0]<*>* [Details?] [Print file] This will display ALL the files in ALL the directories on the volume f0. Notice that the files copied above exist in the appropriate directories. Files [File list] [Details?] [Print file] This will display ALL the files in the default path. Files [File list] <*>s*run [Details?] yes [Print file] This will display ALL of the files in ALL of the directories that begin with the letter 'S' and end with the letters 'run'. Entering yes to the [Details?] parameter will show the sizes of the files. Files [File list] [f0]* [Details?] [Print file] [spl] Displays ALL the files on the volume F0 in the directory workspace and print them to the print spooler. Files [File list] ?????.run [Details?] [Print file] Displays any file in the directory Sys that has a name exactly five characters long followed by ".run". Rename The Rename command is used to change the name of a file. On the command line type rename and press Return. Fill in the Rename form using the example below. Rename Old file name [f0]example New file name [f0]Example2 [Overwrite ok?] [Confirm each?] Press GO. Execute a Files command to see that the file was renamed. Files [File list] [f0]* [Details?] [Print file] Now let's rename a file to a different directory. Rename Old file name [f0]example2 New file name [f0]Example2 [Overwrite ok?] [Confirm each?] Note: The rename command allows you to rename files between directories and volumes. If you rename a file to a different directory or volume the file no longer exists in the original directory and volume. Execute another files command to verify this. Files [File list] [f0]<*>* [Details?] [Print file] Type The Type command displays the contents of the specified files, one screen at a time. The type command expects the file to be a text file. A text file can be produced by WRITEone or the Editor. Unpredictable results will be displayed by typing a non text file. On the command line enter type and press Return. Fill in the Type form using the example below. Type File list [f0]example [Confirm each?] Delete The Delete command removes each file you specify in the File list parameter field, permanently erasing the contents of those files. If you answer yes to the Confirm Each? parameter then the computer will ask for verification from you before deleting a file. A deleted file can not be recovered. On the command line type Delete and press Return. Fill in the Delete form using the example below. Delete File list [f0]Example2 [Confirm each?] Execute a files command to verify that the file was deleted. Files [File list] [f0]* [Details?] [Print file] The file list may contain more than one name and wild cards may be used. Use extreme caution when using the delete command with wild cards. If you wanted to delete all of the -old documents on your floppy disk you could do this with one delete command using the example below. Delete File list [f0]*-old [Confirm each?] This will delete all the files on the floppy disk in the directory workspace that end with -old. Section 4: Archiving and backup of your data Floppy Copy The Floppy Copy command allows you to make an exact duplicate, for backup purposes, of a floppy disk. You need not enter any parameters in the floppy copy form. Floppy copy will assume the correct parameters for the type of system you are using (dual floppy or single floppy system). On the command line type floppy and press Return. Floppy Copy [Number of copies] [Overwrite OK?] [Dual floppy?] [Suppress verify?] [Device name(s)] [Device password(s)] Follow the prompts displayed by the floppy copy command. Change Volume Name The Change Volume Name command changes a volume's name and/or password. You also can use it to add or delete a volume password. On the command line type c v n and press Return. Fill in the Change Volume Name form using the example below. Change Volume Name Device name f0 [Device Password] [Old volume password] New volume name Archive [New volume password] Note: You can not change the name of the System disk. Selective Backup The Selective Backup command copies individual files or directories from one volume to an archive file, thus allowing archiving of personal files and requiring only read access to these files. The Selective Backup command expects to back up files to a floppy disk having the volume name archive. If it takes more than one floppy disk to backup your directories, be sure to have enough disks available with the volume name of archive before you start the backup process. On the command line type selective backup and press Return. Fill in the Selective Backup form using the example below. Selective Backup File list [d0]* [Incremental from (e.g., Mon Jun 1 1981 8:00 pm)] [Confirm each?] [Archive file] [Delete existing archive file?] [Log file] Observe the prompts and press GO to confirm. Note: Selective backup is MUCH faster than a copy if you have many files that need to be backed up. Backup Volume The Backup Volume command copies files from one volume to an archive file, verifies the integrity of volume control structures and reclaims any data that is readable from a corrupted or damaged disk. A disk that you think has become unreadable should not be discarded until backup volume has been run on the suspect volume. Note: The backup volume command expects to back files up to a floppy disk with a volume name of archive. Therefore, you should have enough disks available with the volume name of archive before you start the backup process. The example below shows how you would backup a floppy disk to your hard disk and specify where the archive file is to be placed. Backup Volume Volume or device name f0 [Volume or device password] [Incremental from (e.g., Mon Jun 1 1981 8:00 pm)] [Suppress backup?] [Suppress verification?] [Archive file] [d0] [Delete existing archive file?] [Log file] [Display structures?] Restore The Restore command moves files from and archive file onto a volume. The archive file will have been created with the Selective Backup or Backup Volume commands. The restore command looks for a disk with the name of archive from which to get the data. The example below shows how to restore data to a floppy disk and specify where the archive file is located. Note: When you are restoring data to a floppy disk your path should be set to F0 before this command is executed. Restore [Archive file] [d0] [File list from] [File list to] [Overwrite ok?] [Confirm each?] [Sequence number] [Merge with existing file?] [List files only?] [Log file] Section 5: The text Editor Edit The Edit command allows you to edit information in a file. Like most modern test editors, it shows the text as it appears on a typewritten page. The screen acts as a window for viewing the text file. The Editor displays the data as it actually appears on disk. Note: Most word processors add formating information to a file that is invisible to the user. The Edit command does not do this. On the command line type Edit and press Return. Fill in the Edit form using the example below. Edit File [f0]Example2 [Your name] The Editor has the following commands: CANCEL FINISH Jump Redo (F1) Write Everything HELP Normalize Substitute Zoom Find Insert Read Visible CANCEL - The Cancel key Cancels the last edit. This is the undo key. Everything - CODE-E This command selects the entire file. This is like the MARK DOC command in WRITEone. Find - CODE-F The Find string command searches the file for the specified text, starting at the cursor position. This command is upper/lower case sensitive. Find String: <> FINISH - The Finish key This key ends the Editor session. The session WILL be save unless no, NO, n or N is entered to the Save? prompt. Finish Save? : <> Insert - CODE-I The Insert hexidecimal command allows you to insert a character, whose code is a specified hexidecimal value, at the current cursor position. Enter the hexidecimal value (00 through FF) to be placed into the file. Insert Code: <> Jump - CODE-J The Jump command moves the cursor to a specified location in the file. Percent : <> Normalize - CODE-N The normalize command moves selected text close to the center of the screen. If no data is selected then the cursor moves near to the middle line on the screen. Read - CODE-R The Read command copies characters from another file and inserts them into the file you are editing, starting at the cursor position. Read File: <> Number of Characters: <> Position: <> Redo - F1 key Repeats the previous editing operation. Substitute - CODE-S The Substitute command changes all occurrences of old text to new text. The substitution occurs only within selected text. This command is sensitive to upper/lower case letters. Substitute New: <> Old: <> Visible - CODE-V The Visible command displays non printing characters. This helps you to see exactly what formating is in you file. Write - CODE-W The write command appends selected text to another file. Write File: <> 2 Business School BTOS Utilities Computing Services August 8, 1985 BTOS Utilities Tutorial Page 1-# BTOS Utilities Tutorial Page 2-# BTOS Utilities Tutorial Page 3-# BTOS Utilities Tutorial Page 4-# BTOS Utilities Tutorial Page 5-#=?EOV\aQb04Ÿԧ¸»&(:Cԗ$*0y¢0G[p#ª h ԇ œ ף © ԯ B O NPV@W@@@9@@@@@@@@@@@h@i@$@%@^@_@@@C@D@N@O@P@@@@@@@@@@@@@ @ @ @N @ @ @ @ @ @ @ @ @ O$&(*,@ x $&(*,@$&(*, @ xxh@ xhE<_ŀ'(Zz+0;bhœŦDW]ouw½&,< ( ¼  Ƞ   N [ ¥ Ŵ ¤ų {ȋȜo@C@@@@'@@>@?@@@@@+@G@H@z@{@ @B@C@DW@X@@@ @G@@&@'@O@@@: @u @v @[ @ @ @ @B @C # $ @ @ @@@@m@n$&(*,@ x $&(*,@ $&(*, "7  *F ¨Ŭ*# % &    _ ` b ® L M @@@@@@ @ ٍَ@@@@9@:abݯ<݂݁ݜݝ&;<#67݌ݜݝQR! " Y Z A B # @& @t @ @ @a @ @ @M "# %  ` M ,,,,,,$&(*,@ L@ x  @$&(*,  ()P xxxx Courier 72Elite 12G@db93"3.0.7=_(:FW BURROUGHS 9252 PRINTER SWITCH SETTINGS Switches (0 = OFF, 1 = ON) +-------------------------------+--------------------------+ | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | | +-------------------------------+--------------------------+ | 0 | 0 | | | 0 | | | | USA ASCII Character Set | +-------------------------------+--------------------------+ | 0 | 0 | | | 1 | | | | Germany Character Set | +-------------------------------+--------------------------+ | 0 | 1 | | | 0 | | | | Canada Character Set | +-------------------------------+--------------------------+ | 0 | 1 | | | 1 | | | | Finland Character Set | +-------------------------------+--------------------------+ | | | 0 | | | | | | CR causes LF | +-------------------------------+--------------------------+ | | | 1 | | | | | | CR does not cause LF | +-------------------------------+--------------------------+ | | | | | | 1 | | | Skip over perforation | +-------------------------------+ | | | | | | | | | | to Top Of Form when | +-------------------------------+ | | | | | | | | | | printer is .75 inch of | +-------------------------------+ | | | | | | | | | | perforation. | +-------------------------------+--------------------------+ | | | | | | 0 | | | Do not skip over perf. | +-------------------------------+--------------------------+ | | | | | | | 1 | | 17.2 Characters per Inch | +-------------------------------+--------------------------+ | | | | | | | 0 | | 10 Characters per Inch | +-------------------------------+--------------------------+ 9252 Printer Control Codes Control Hex Dec Description Code _ _ _ _ _ _ _ BEL 07 07 Causes an audiable alarm to sound for approx. 1.5 seconds. HT 09 09 Moves print head to the next Horizontal Tab (HT) position. These positions are a fixed 8 characters apart. LF 0A 10 Advances the paper one line. VT 0B 11 Advances paper to next Vetical Tab (VT) position. On power up VT positions are one inch apart, but can be changed under program control. FF 0C 12 Advances paper to Top Of Form. CR 0D 13 Used as a PRINT COMMAND causing that line of data to be printed. Can also cause an automatic line feed (LF) if Switch 3 is on. SO 0E 14 Causes subsequent data up to and/or CR codes or the End Of Line to print double width (5 CPI) characters. SI 0F 15 Terminates extended character mode and causes a return to normal print. DC2 12 18 Same as ESC 7 (force to condensed print 17.2 CPI) 9252 Printer Control Codes Control Hex Dec Description Code _ _ _ _ _ _ _ ESC 0 1B,30 27,48 Makes current print line TOF. ESC 1 1B,31 27,49 Clears all vertical tabs and sets page length to 24 inches. ESC 2 1B,32 27,50 Enables 8 LPI Switch. ESC 3 1B,33 27,51 Makes current print line a vertical tab position. ESC 4 1B,34 27,52 Causes printer to space at 6 LPI until ESC 5, ESC 2 or RESET. ESC 5 1B,35 27,53 Causes printer to space at 8 LPI until ESC 4, ESC 2 or RESET. ESC 6 1B,36 27,54 Forces printer to print in normal print mode (10 CPI). ESC 7 1B,37 27,55 Forces printer to print in condensed print mode (17.2 CPI). ESC 8 1B,38 27,56 Puts printer into whichever print mode is set by switch 7. ESC 6 SO 1B,36,0E 27,54,14 Puts printer into EXTENDED (5 CPI) print mode . ESC 7 SO 1B,37,0E 27,55,14 Puts printer in CONDENSED or EXTENDED (8.6 CPI) mode.2 -#- (/0MNk(@)@*@+F0KLM/ 4@ <x )  !"%<&'<)<*+<,@ 4'  !"%<&'<)<*+<,4 ;\]z{ǘğǠģǤĨǩ;рѬ\ ]xyzQyѽ ]ѦAKюї@\,@ <x @)  !"%<&'<)<*+<, 4@  0K 44 4  ((()P xxxxElite 12G BRK "10.3k B20 Comm Port A or B Multi-Function Printer Protective Ground 1 <-------------------> 37 Protective Ground _ _ +---> 34 Serial Cable | +---> 33 jumper (Ground) Receive Data 3 <-------------------> 18 Transmit Data Transmit Data 2 <-------------------> 16 Receive Data Logic Ground 7 <-------------------> 36 Logic Ground Data Set Ready 6 <-------------------> 17 Data Terminal Ready Clear to Send 5 <-------------------> 19 Ready (Fault) Thinks we have to learn; 1) we may have to do more with the cable at the B20 end. Pins 6 & 8 tied together, for example. 2) what flow contol mechinism does the printer use? This may cause us to redisign the cable. 3) does this work and is it reliable? What distance are we talking about.2 0uˁ*,0%\ɒ  #*@,*, @ Z x,  ((()P xxxxLetter Gothic 12 LaserG B,*"10.3 BEACON Installation Guide and MTS Visual Mode Reference Manual Version 0.6 May 15, 1986 Systems & Communications Group Computing Services School of Business Administration University of Michigan Here is a brief description of using BEACON (the DEC VT100 terminal emulator) in MTS's visual editor. If you don't have a copy of BEACON, ask John Parliament for a BEACON installation diskette. Note that the versions of BEACON with version numbers 0.1 through 0.9 are considered BETA TEST VERSIONS and are not applications which are currrently supported by Computing Services. To use BEACON on your Burroughs B25. A) Install BEACON on your system. The installation procedure will place the following files on the [Sys] volume in the directory. i) [Sys]BEACON.Run ii) [Sys]BEACONCommands iii) [Sys]BEACONEscapeSequences iv) [Sys]BEACONDefault.Key v) [Sys]BEACONHelp vi) [Sys]BEACONExplain B) Issue the new command named BEACON. This will then load and execute the program. (Executes the file [Sys]BEACON.Run) C) If the program loaded correctly, the screen should look something like BLink. Establish connection with MTS by hitting any key. D) Now, change the UMNet terminal type by entering... %TERMINAL=VT100 E) Everything should be ready to go. F) NOTE: terminates the program. Here is a list of the control sequences supported by MTS's visual editor. Use the key on the B25 as the ASCII control key. Control-E Exit visual mode Control-C Exit visual mode and leave contents of work area in conversation buffer Control-Z Cursor to end of line Control-B Cursor to start of line Control-V Cursor to work field Control-T Cursor to top left of screen Control-K Cursor to start of previous line Control-M Cursor to start of next line (Return) Control-H Cursor to previous character (Backspace) Control-I Tab Control-D Delete character at cursor Control-W Delete word at cursor Control-X Delete from cursor to end of line Control-A Turn insert mode on and off Control-G Rewrite line w/o current changes Control-L Rewrite screen w/o current changes Control-R Rewrite screen with current changes keyboard - map as DEC's PF1 - PF4 + terminates the emulator. Here is description of the mapping of the numeric keypad on the B25 to match the keypad of the VT100. Note that the physical keyboard layouts are a little different. On a real VT100, the control key is needed to use the cursor keys. Here, the cursor keys don't need the control key to be pressed. Also, the B25 function keys F1 through F4 are used to replace the function keys PF1 through PF4 on a real VT100. Function Key Definitions F1 F2 F3 F4 +---------------+---------------+---------------+ +---------------+ | VPF 10 | VPF 11 | VPF 12 | | VPF 13 | | | | | | | | Insert null | Extend | Display to | | Display | | lines | current line | previous file | | back | | | | location | | 10 lines | | | | | | | +---------------+---------------+---------------+ +---------------+ Keypad Definitions +---------------+---------------+---------------+---------------+ | VPF 7 | VPF 8 | VPF 9 | VPF 14 | | | | | | | Display | Execute work | Display to | Copy data to | | forward | field as a | end of file | Work field | | 1 line | command | | | | | | | | +---------------+---------------+---------------+---------------+ | VPF 4 | VPF 5 | VPF 6 | VPF 15 | | | | | | | Display | Insert work | Display to | Display to | | forward | field at | line 1000 | line 1 | | 10 lines | cursor | | | | | | | | +---------------+---------------+---------------+---------------+ | VPF 1 | VPF 2 | VPF 3 | VPF 16 | | | | | | | Display | Copy data | Display to | Display | | back | to work field | line 1 | forward | | 10 lines | | | 10 lines | | | | | | +---------------+---------------+---------------+ | | VPF 0 | VPF 17 | | | | | | | Update screen with current | Insert work | | | changes | field at | | | | cursor | | | | | | +---------------+---------------+---------------+---------------+ BEACON supports a number of local commands to assist in program configuration. Local commands can be entered in BEACON's Command field (near the bottom of the screen). The MOVE key places the cursor in the Command field which then allows for the entry of local commands. Note that the program is configured for 9600 baud and for serial port A. This baud rate can be changed using the %BAUDRATE and %PORTLETTER local commands. Refer to the BEACON reference manual for a complete list of local commands supported by BEACON. If you have any questions, contact John Parliament of Computing Services. 2 BEACON Installation Guide #Djk#DEFGHIUbcdefghijۉۊ۝ۿ@ &*,@!P<Zx000001,J1h1@!P<Zx@,Jh ,uZ\]xy|}~̣̤89Z̫f̤̥45oṗ̲̳̈̉6789qr̗ 4`̺̉)f~̭ =r̩ < = i j 5 | Q ̘ & m n ́ ̂ H̊P̒X̚`̢&h̪.p̲6x̺ YZ@]y; Z\y@ !, &*, &*, &*,@ @ d   ((()P xxxx Prestige Elite LaserG BQ2 "10.3 BEACON File Transfer Guide Version 0.6 May 15, 1986 Systems & Communications Group Computing Services School of Business Administration University of Michigan The University of Michigan's School of Business Administration has developed "BEACON", a terminal emulation program for the Burroughs B25 workstation. One feature of BEACON is the ability to transfer files over an asynchonous communications line using many file transfer protocols. The file transfer protocols supported are "ASCII" and "BINARY" (the same protocols used in Burrough's ATE), "XMODEM" and "KERMIT". This manual is meant to be an introduction to KERMIT file transfer between the Burroughs B25 and MTS (Michigan Terminal System). Users interested in using any of the other file transfer protocols (other than KERMIT) should refer to Appendix A of this document. Now, a few words about the KERMIT file transfer protocol. The KERMIT file transfer protocol was designed and developed at the Columbia University Center for Computing Activities by Bill Catchings and Frank da Cruz. The initial objective of KERMIT was to provide a facility for archiving mainframe files on microcomputers. KERMIT has quickly been adopted by many computer users because it allows any two computers to exchange files. The KERMIT protocol was named after Kermit the Frog, star of the television series THE MUPPET SHOW. Sending a Text File to MTS First, we must enter MTS's versions of KERMIT. This involves issuing the KERMIT run command. #$RUN *KERMIT #Execution begins KERMIT-UM> MTS KERMIT (UM) Version 1.17 (13:59 Aug 2/85) KERMIT-UM> Next, we must instruct MTS's KERMIT to get ready to accept a file. To do this, we must issue the RECEIVE command. KERMIT-UM>RECEIVE KERMIT-UM>Preparing to receive file. At this point, MTS's KERMIT is ready to receive a file. Now we must instruct BEACON to SEND a file to MTS. For this example, we will send a BTOS file by the name of "message". %SENDFILE message After about 10 seconds, the file transfer should begin. The number of packets correctly transfered will constantly be updated in BEACON's Status Line. The key will interrupt the file transfer at any time. KERMIT-UM>File received successfully. KERMIT-UM> Now the file has been transfered. Note that the KERMIT file transfer protocol sends the name of the file along with the file's contents. This means that MTS's KERMIT uses the BTOS file name as the resulting MTS file name. (The file that was just sent to MTS is in the MTS file "message".) Note that the BEACON command %SENDFILE accepts an optional second parameter which is the desired resulting MTS file name. To exit MTS's KERMIT, issue the following commmand. KERMIT-UM>STOP #Execution terminated # Receiving a Text File to MTS First, we must enter MTS's versions of KERMIT. This involves issuing the KERMIT run command. #$RUN *KERMIT #Execution begins KERMIT-UM> MTS KERMIT (UM) Version 1.17 (13:59 Aug 2/85) KERMIT-UM> Let's assume for this example that we want to transfer the MTS file "SIGFILE" down to the B25. We must instruct MTS's KERMIT to get ready to send the file. To do this, we must issue the SEND command. KERMIT-UM>SEND SIGFILE KERMIT-UM>Preparing to send file 'SIGFILE'. At this point, MTS's KERMIT is ready to send the file. Now we must instruct BEACON to RECEIVE the file from MTS. %RECEIVEFILE After a slight delay (~10 seconds), the file transfer will begin. The user can abort the file transfer at any time by hitting the key. KERMIT-UM>File sent successfully. KERMIT-UM> Now the file has been transfered. Note that the KERMIT file transfer protocol sends the name of the file along with the file's contents. This means that the MTS file name is used as the file name of the new BTOS file. Note that the BEACON command %RECEIVEFILE accepts an optional parameter which is the desired resulting MTS file name. To exit MTS's KERMIT, issue the following commmand. KERMIT-UM>STOP #Execution terminated # Transfering Binary Files First, we must enter MTS's versions of KERMIT. This involves issuing the KERMIT run command. #$RUN *KERMIT #Execution begins KERMIT-UM> MTS KERMIT (UM) Version 1.17 (13:59 Aug 2/85) KERMIT-UM> First, we must specify to MTS's KERMIT that we are transfering binary files. This is needed to inhibit ASCII/EBCDIC translation. KERMIT-UM>SET FILETYPE BINARY KERMIT-UM>Binary filetype set. KERMIT-UM> Next, we need to tell BEACON that we want to transfer binary files. This involves issuing the two BEACON commands BINARYFILETYPE and SETEIGTHBITPREFIX. %BINARYFILETYPE TRUE %SETEIGTHBITPREFIX TRUE Now file transfer can proceed as described in the above sections. From this point onward, all files that are transfered will be binary files. To return to transfering normal text files, the binary file commands must be undone. This is performed as follows. KERMIT-UM>SET FILETYPE TEXT KERMIT-UM>Text filetype set. KERMIT-UM> %BINARYFILETYPE FALSE %SETEIGTHBITPREFIX FALSE Appendix A: File Transfers Using Non-KERMIT Protocols It is also possible to transfer files using the "ASCII", "BINARY", and "XMODEM" file transfer protocols. (Note that "ASCII" and "BINARY" are the file transfer protocols available in Burroughs's Asynchronous Terminal Emulator, and "XMODEM" is a file transfer protocol developed for CP/M and MSDOS based personal computers.) Sending a File Using a non-KERMIT Protocol First, select the file transfer protocol which will be used in file transfer. (In this example, we will use "XMODEM", but "ASCII" and "BINARY" will use the same command sequence.) %SETTRANSFERTYPE "XMODEM" File transfer now procedes with the same command sequence as with the KERMIT file transfer protocol. Next, we must instruct the host to receive the file (using whatever command the host requires for receiving a file). Receive (or whatever the host requires) Now instruct BEACON to send the file. %SENDFILE The file transfer will proceed similar to a KERMIT file transfer. The key can be used to interrupt file transfer at any time. Receiving a File Using a non-KERMIT Protocol First, select the file transfer protocol which will be used in file transfer. (Again, we will use "XMODEM", but "ASCII" and "BINARY" will use the same command sequence.) %SETTRANSFERTYPE "XMODEM" File transfer now procedes with the same command sequence as with the KERMIT file transfer protocol. Next, we must instruct the host to send the file (using whatever command the host requires for receiving a file). Send (or whatever the host requires) Now instruct BEACON to receive the file. %RECEIVEFILE The file transfer will proceed similar to a KERMIT file transfer. The key can be used to interrupt file transfer at any time. Appendix B: BEACON File Transfers Commands Here is an excerpt from the BEACON reference manual which contains a description of all the KERMIT related commands. Most of the BEACON parameters which pertain to KERMIT use the recommended KERMIT default values and should not need to be modified by the user. %BinaryFileType The purpose of this command is to specify that the next file being transferred is a binary file. Specifying a file as type binary will inhibit the mapping of kermit's end-of-record specifier () to BTOS's end-of-record specifier (). This command requires one boolean parameter (either "TRUE" or "FALSE") and the initial value of this parameter is "FALSE". The syntax of this command is as follows: %BinaryFileType <"TRUE"|"FALSE"> %Bye The purpose of this command is to terminate connection between BEACON and a KERMIT server program. This command sends a KERMIT packet to host to instruct the host to disconnect. This command is only useful when connect to a host which is a KERMIT server. The syntax of this command is as follows: %Bye %Finish The purpose of this command is to instruct the host to exit KERMIT server mode but to remain connected. This command sends a KERMIT packet to host to instruct the host to leave KERMIT server mode. This command is only useful when connect to a host which is a KERMIT server. The syntax of this command is as follows: %Finish %Get The purpose of this command is to instruct the host's KERMIT server to send a file from the host to the local B25. This command is only needed when connected to a host which is a KERMIT server. The syntax of this command is as follows: %Get [Local filename] %LogTransactions The purpose of this command is to initiate and terminate the logging of file transfer. Packet content and program status appear in the log file. This command accepts one string parameter which is the name of the log file. Logging is terminated by using this command with no parameters. The syntax of this command is as follows: %LogTransactions [Log file name] %ReceiveFiles The purpose of this command is to place BEACON into receive file mode. An optional string parameter may be specified which will be used as the local file name for the first incoming file. (Note that when in receive file mode, the kermit protocol allows for the reception of more than one file. Filenames are transferred with files.) The syntax of this command is as follows: %ReceiveFiles [BTOS file name] %Remote The purpose of this command is to send executable commands to the host KERMIT server. This command accepts one or two parameters. The first parameter is a valid host command (in proper syntax) and the optional second parameter is the KERMIT packet type used for transmission of the command to the host. (The default value of the second parameter is "K".) This command is only useful when connected to a host KERMIT server. The syntax of this command is as follows: %Remote [KERMIT packet type] %SendFiles The purpose of this command is place BEACON in send file mode. This command requires one string parameter which is used as the name of the BTOS file to send. An optional second string parameter is the desired file name on the host system. If no second parameter is specified, then the BTOS name of the file will be used as the host's file name. The syntax of this command is as follows: %SendFiles [Host file name] %Server The purpose of this command is place BEACON in KERMIT server mode. This will allow the computer at the other end of the connection to send file transfer requests in KERMIT server packets. Currently, KERMIT server mode only supports requests for file transfer and remote specification of BEACON commands. The key can be used to exit KERMIT server mode. The syntax of this command is as follows: %Server %SetEigthBitPrefix The purpose of this command is to enable the Kermit 8th bit prefixing mechanism. This allows for the transmission of 8 bit data through a 7 bit network. This command requires one boolean parameter. Of value of "TRUE" for this parameter enables the request for 8th bit prefixing to be performed. (Note that both computers have to agree to perform 8th bit prefixing.) The initial value for this command is "FALSE". The syntax of this command is as follows: %SetEigthBitPrefix <"TRUE"|"FALSE"> %SetEigthBitPrefixChar The purpose of this command is establish the ASCII character used as the 8th bit prefixing character. The default value for this character is "&". The syntax of this command is as follows: %SetEigthBitPrefixChar %SetReceiveEOLChar The purpose of this command is to establish the End-Of-Line character that BEACON requires with all incoming packets. The default value for this parameter is ASCII 13 (Carriage Return). The syntax of this command is as follows: %SetReceiveEOLChar %SetReceiveEORString The purpose of this command is to establish which End-Of-Record delimiter to expect when receiving text files. Acceptable values for this parameter are "CR" (), "LF" (), or "CRLF" (). The initial value for this parameter is "CRLF". The syntax of this command is as follows: %SetReceiveEORString <"CR"|"LF"|"CRLF"> %SetReceivePacketLength The purpose of this command is to specify the maximum length of BEACON's receive packets. Packet lengths must be between 10 and 94 characters (inclusive). A user might want to specify shorter packets if the connection with the other computer is noisy. The default packet length is 94 characters. The syntax of this command is as follows: %SetReceivePacketLength %SetReceivePadChar The purpose of this command is to specify which character should be sent before receiving packets from the other computer. (The number of times this character is sent is specified by the %SetReceivePadCount command.) The default value for this character is ASCII 0 (NUL). The syntax of this command is as follows: %SetReceivePadChar %SetReceivePadCount The purpose of this command is to specify the number of pad characters that must be sent by the other computer before sending a packet to BEACON. (see %SetReceivePadCount) The default value for this count is zero (which means no padding is performed). The syntax of this command is as follows: %SetReceivePadCount %SetReceiveStartOfPacketChar The purpose of this command is to specify which character to look for which designates the beginning of a receive packet. The default value for this character is ASCII 1 (SOH). The syntax of this command is as follows: %SetReceiveStartOfPacketChar %SetReceiveTimeOut The purpose of this command is specify the amount of time (in seconds) to wait for a packet. The default value for this timeout is 10 seconds. If the program does timeout, appropriate action will be taken. (Either resending the last packet, or aborting the file transfer.) The syntax of this command is as follows: %SetReceiveTimeOut %SetRepeatPrefixChar The purpose of this command is to specify which character will be used as the repeat prefix character. The initial character used is "~" (tilde). The syntax of this command is as follows: %SetRepeatPrefixChar %SetRetryInitialCount The purpose of this command is to specify the number of times to retry the first packet before aborting. The default value for this parameter is 10. The syntax of this command is as follows: %SetRetryInitialCount %SetRetryPacketCount The purpose of this command is to specify the number of times to resend packets which are not received correctly before aborting. The default value for this parameter is 5. The syntax of this command is as follows: %SetRetryPacketCount %SetSendEOLChar The purpose of this command is specify the End-Of-Line character on outgoing packets. This character is usually set by the other computer. The default value for this character is ASCII 13 (Carriage Return). The syntax of this command is as follows: %SetSendEOLChar %SetSendEORString The purpose of this command is to establish which End-Of-Record delimiter to use when sending text files. Acceptable values for this parameter are "CR" (), "LF" (), or "CRLF" (). The initial value for this parameter is "CRLF". The syntax of this command is as follows: %SetReceiveEORString <"CR"|"LF"|"CRLF"> %SetSendPause The purpose of this command is to specify the number of seconds to delay before sending the first packet. The initial value of this parameter is zero (no delay). The syntax of this command is as follows: %SetSendPause %SetSendQuoteChar The purpose of this command is to specify the character that is used for control quoting in outgoing packets. The initial value for this character is "#". The syntax of this command is as follows: %SetSendQuoteChar %SetSendRecordWrap The purpose of this command is to enable line-wrapping of outgoing files. When this function is enabled, an SendEOLString is inserted in the record assuring lines of maximum length specified by SendRecordWrapCount (see the next command). This initial value of this parameter is "FALSE". The syntax of this command is as follows: %SetSendRecordWrap <"TRUE"|"FALSE"> %SetSendRecordWrapCount The purpose of this command is to establish the maximum line length of outgoing files. This parameter is enabled by the SetSendRecordWrap parameter (see the previous command). When SendRecordWrap is enabled, an SendEOLString is inserted in the record assuring lines of maximum length specified by this parameter. This initial value of this parameter is 80. The syntax of this command is as follows: %SetSendRecordWrap Count %SetSendStartOfPacketChar The purpose of this command is specify the first character of a send packet. The initial value for this character is ASCII 01 (SOH). The syntax of this command is as follows: %SetSendStartOfPacketChar %SetServerTimeout The purpose of this command is specify the timeout value (in seconds) when KERMIT is in server mode (see %Server command). The initial value of this parameter is 120. The syntax of this command is as follows: %SetServerTimeout %SetTransferType The purpose of this command is to specify the protocol used for file transfer. BEACON supports "ASCII" and "BINARY" (the two file transfer protocols supported by Burroughs ATE), "KERMIT" and "XMODEM". Note that "ASCII", "BINARY", and "XMODEM" require a serial port configuration of %DATABITS=8, %PARITY=N, and %XONXOFF=FALSE. The initial value for this parameter is "KERMIT". The syntax of this command is as follows: %SetTransferType <"ASCII"|"BINARY"|"KERMIT"|"XMODEM"> %SetXModemBinaryFiletype The purpose of this command is to disable CRLF to LF mapping of files sent using the XModem file transfer protocol. The initial value for this parameter is "TRUE". The syntax of this command is as follows: %SetXModemBinaryFiletype <"TRUE"|"FALSE">2!GH´ !"#$%&2?@ABCDEFGfgzۜųu,@!P<Zx000001,J1h1@!P<Zx@,Jh ,ӧӨK @<Zx@,Jh ,@<Zx@,Jh bwQa:]IVo_`wxՊEFaՆՇ9:\]56\gh =>Vlon~  ,@* X P <Zx@,Jh@$ <Zx@,Jh{{@* X P <Zx@,Jh@<Zx@,Jh  J_Ĭڭo|ĕ+grs=>?_׋׌׭./cd|גו” ,@* X P <Zx@,Jh@$ <Zx@,JhwwJ@* X P <Zx@,Jh@<Zx@,Jh  GH/A[ă+grs<GH/0456[x׃ׄתH,@* X P <Zx@,Jh@$ <Zx@,Jh«7~Ҫt@$ <Zx@,Jh @<Zx@,Jh@<Zx@,Jh ķ-7@ڵھ@AB,@$ <Zx@,Jh@* X P <Zx@,Jh././@$ <Zx@,Jh@<Zx@,Jh @<Zx@,Jh ĭij #-6Ŀګڱ  678ھ¿ , @$ <Zx@,Jh@* X P <Zx@,Jh (folder name) always appears between < > Example: A Directory (folder) contains a group of related documents (files). EVERY USER (or Application) SHOULD HAVE THEIR OWN DIRECTORY. This allows documents (files) to be grouped for quick and easy identification. File specification can be any of the following: source This is the document (file) "source" in the logged in directory and volume (Your Path). data This is the document (file) "data" in the directory "application" on the logged in volume. [f0]test.file This is the document (file) "test.file" in the directory "chas" on the floppy disk volume. Note: If a Volume name is supplied in a file specification the Directory name must also be supplied. CLUSTER CONFIGURATIONS Mini-Cluster (Max. configuration is 5 CWS workstations) B25 ---------------- Note: (max total cable length ! MASTER ! on each Master port is ! WORK STATION ! 1200 feet) ---------------- ! ! -------- --------------------- ! ! ------- ------- ------- ------- ------- ! CWS !---------! CWS ! ! CWS !---------! CWS !---------! CWS ! ------- ------- ------- ------- ------- B25 B25 B25 B25 B25 NOTES: MWS = Master Work Station CWS = Cluster Work Station LFS = A work station with local disk attached (Local File Storage) I/O PORTS (excluding disks) B25 (B26) 2 RS-232 ports (Data comm channel A and B async or sync) 1 RS-422 port (Cluster communications) 1 Centronix port (Parallel printer) 1MB Maximun Memory B27 2 RS-232 ports (Data comm channel A and B async or sync) 1 RS-422 port (Cluster communications) 1 Centronix port (Parallel printer) 1MB Maximun Memory B28 2 RS-232 ports (Data comm channel A and B async or sync) 1 RS-422 port (Cluster communications) 1 Centronix port (Parallel printer) 4MB Maximun Memory B38 2 RS-232 ports (Data comm channel A and B async or sync) 1 RS-422 port (Cluster communications) 1 Centronix port (Parallel printer) 4MB Maximun Memory Q MANAGER and SPOOLER --------------- ! Master ! ------------ ! Workstation !-----------! Printer ! 9253 (SPL) --------------- ------------ --------------! ! ------- ------- ------- ! CWS !-----------! CWS !------------! CWS ! ------- ------- ------- ! ! ----------- ----------- ! Printer ! AP1302 (SPLA) ! Printer ! AP1351 (SPLB) ----------- ----------- NOTES 1) Queue manager must be installed in the Master Workstation. 2) Spooler is installed in each work station that has a printer attached. Splcnfg.Sys file identifies which Queue and Printer this work station serves. 3) Each printer has a configuration file (i.e., splconfig.sys) 4) Queue.index file contains: Spl/[sys]Spl.Queue/1/1 9253Control/[sys]9253Control.Queue/1/1 SplA/[sys]SplA.Queue/1/1 AP1302Control/[sys]AP1302Control.Queue/1/1 SplB/[sys]SplB.Queue/1/1 AP1351Control/[sys]AP1351Control.Queue/1/1 SpoolerStatus/[sys]SpoolerStatus.Queue/1/1 5) Splcnfg.Sys file contains: 0/9253/Spl/[sys]Splconfig.Sys/64/Y 6) SplAcnfg.Sys file contains: B/AP1302/SplA/[sys]SplAconfig.Sys/64/Y 7) SplBcnfg.Sys file contains: 0/AP1351/SplB/[sys]SplBconfig.Sys/64/Y 8) Using the Create Configuration File utility create 3 files: Splconfig.Sys, SplAConfig.Sys and SplBconfig.Sys 9) Consult the Standard Software Operations Guide for more information on configuring the Spooler and Queue Manager. OPERATING SYSTEM TYPES (naming convention) SysImage.Sys The operating system of a work station with local disk storage. (i.e., B26, B27, B28 or a B38) WS252>SysImage.Sys The operating system file name for a B26 CWS without any local disks.(Resides on the MWS's disk) WS251>SysImage.Sys The operating system file name for a B25 CWS with floppy disks.(Resides on the MWS's disk) WS250>SysImage.Sys The operating system file name for a B25 CWS with hard disks.(Resides on the MWS's disk) To force a B25 to BOOT a from the Master Turn power on or press the RESET button at the rear of the CPU while holding the space bar down. Release the space bar when you see the letters separated by commas. The B25 workstation will display B,C,D,L,M,P,T Depress T The B25 workstation will display OS: Depress nnn "nnn" = WS "nnn" >SysImage.Sys * Depress B The workstation will now boot from the Cluster Communications line as long as the MWS has the file WSnnn>SysImage.Sys * nnn is 252 for a B25 with no disk. nnn is 251 for a B25 with floppies and no hard disk. nnn is 252 for a B25 with hard disk. B25 OPERATING SYSTEM TYPES 4.0 or greater (identification) Hardware Type O.S. Type Identification B25 MWS t1MstrSp B25 MWS t1MstrMp B25 SAL t1StndSp B25 SAL t1StndMp B25 CWS t1ClstrSp B25 CWS t1ClstrMp B25 CWS t1ClstrLfsSp B25 CWS t1ClstrLfsMp B27 MWS BawsMstrSp B27 MWS BawsMstrMp B27 SAL BawsStndSp B27 SAL BawsStndMp B27 CWS BawsClstrSp B27 CWS BawsClstrMp B27 CWS BawsClstrLfsSp B27 CWS BawsClstrLfsMp Files in a standard Standalone release (4.0) SysImage.Sys The operating system BawsSys.font The font for a B27 t1Sys.font The font for a B25 t1Diag.font The font for the Check Configuration program Sys.Cmds The commands recognized by the Executive SysInit.run Runs the Sysinit.Jcl file Sys.Keys Keyboard table Sys.Printers Multiplan and WRITEone printer names file Signon.run Executes the statements in the .user file Signon.txt Text displayed at Sign on DtConfig.Sys System date and time configuration file Diag.User Used to allow loading of the diagnostics .User The default ".user" file Bootstrap.Run Run file for the Bootstrap command CheckConfig.Run Run file for Check system configuration Command.run Run file for New Command and Remove Command CreateConfig.Run Run file for Create Configuration File Exec.run Run file for Executive Files.run Run file for Files Command Floppycopy.run Run file for Floppy Copy Command IVArchive.Sub Initialize Archive Volume submit parameters IVolume.run Run file for Initialze Volume Command Restore.run Run file for Restore command MakeTxlFile.Run Run file for Make Printer Translation File SelectiveBackup.run Run file for Selective Backup Command SetDirectoryProt.Run Run file for Set Directory Protection SetTime.run Run file for Set Time Command Sort.run Run file for Sort Command SubCmd.Run Allows submit files to be commands for Exec. Submit.run Run file for Submit Command UserFileEditor.Run Run file for User File Editor VolumeStatus.run Run file for Volume Status Command LptConfig.Sys Parallel printer hardware configuration file PtrBConfig.Sys Serial printer hardware configuration file UserFileTemplate.Sys Template file for the User file editor MULTIPLAN and Printers Multiplan can make use of several types of printers. These printers can be attached directly to your workstation or, in cluster configurations, be located at a different workstation. You can have a letter quality printer which is attached to a serial port, and a fast draft matrix printer attached to a parallel port. You can use direct print, or use spooled print provided by the operating system. In any event you can see the possibilities are many. The following describes how Multiplan knows what printer to use when you use the Print Printer command. Multiplan uses a printer description file which provides it information about the printers which can be used. The Multiplan printer description file is [sys]Sys.Printers. It contains an entry for each printer that you can use. The first entry in the file defines the DEFAULT printer used when you invoke the Print Printer command without changing the Printer Options. You can use a different printer, other than the default printer, by entering a name in the printer field of the Print Options command. Note: This name must exist in the Sys.Printers file and must not cause a conflict with the operation system. (i.e. you can not specify to direct print to a printer that is assigned to the spooler if the spooler is installed. The format of the printer description file (sys.printers) is: PrinterName: Printer Specification: Text Type: Graphics type The PRINTERNAME field is a nickname or alias for the printer. This can be any character string such as Parallel, Printer1, or Draft. This name is used when specifying a printer other than Multiplan's default printer. Type in this name in the Printer field of the Print Options command. The PRINTER SPECIFICATION field is the name which Multiplan provides to the operating system whenever you wish to print a sheet on a printer. Information about printer specifications is provided in the BTOS Operating System Manual. The TEXT TYPE is ignored by Multiplan. The GRAPHICS TYPE is used by Multiplan to determine the type of graphics printer or plotter to be used by the Graph command. Some examples of a printer description file (sys.printers): Example #1 Both printers are Spooled Draft: [Spl]: Draft :Prism Letter: [SplB]: Diablo630 Example #2 One printer is not spooled, one printer is spooled Draft: [Lpt]: Draft: :OkiData Letter: [SplB]: Diablo630 If sys.printers contains the text above , the Print Printer command will default to the printer Draft which is [SplB]. You can, however specify Lpt, PtrB or Letter as different printer names. NOTES If the default printer in sys.printers does not meet your requirements use the text Editor to move or edit the entry that meets your requirements to the first entry in the file. There is a hardware configuration file associated with each printer. It has the file specification format of XXXXconfig.sys, where XXXX usually identifies the printer type. This file defines such things as the maximum print width of the printer and in the case of printers connected to the B20 serial ports what Baud Rate the printer is set at. These configuration files can only be inspected or changed with the Create Configuration File command. Word Processing and Printers This is an example of a Sys.Printers file that the Word Processor (WRITEone) software uses. The top entry in this file is the Default printer for WRITEone. If the top entry in this file does not agree with the printer you have on your system or the way you want to print while in WRITEone (i.e. Spooler or Direct printing) use the Editor and move the correct entry for the way you want to print to the top of the file. Draft: [Spl]: Draft Letter: [SplB]: Diablo630 PTRB: [Ptr]B&[Sys]MpPtrBConfig.Sys,[SplB]: Diablo630 LPT: [Lpt]&[Sys]MpLptConfig.Sys,[Spl]: Draft NOTES Beginning with release 3.0 of WRITEone the default printer configuration file is Sys.Printers. The same default configuration file that MULTIPLAN uses. Prior to WriteOne 3.0 the default is Wp.Printers For WRITEone the third entry on each line is used by the WRITEone software to determine how to format printed information sent to a printer. Multiplan ignores the third entry on each line. WRITEone and Multiplan allow the operator to select any printer defined in their printer file. Therefore it is not mandatory that these files be edited. It does, however, make the software easier to operate if the default printer in these files matches the system configuration and the way the user intends to print from these software programs. POWER ON SEQUENCE OF EVENTS 1) Power on. 2) Bootstrap ROM a) performs system confidence routines b) loads Operating System from disk. 3) Operating System a) performs system confidence routines b) initializes hardware and calls SysInit.Run. 4) SysInit.Run a) displays most recent Crash Status b) displays SysInit.Txt if it exists c) runs Batch stream contained in SysInit.JCL d) calls SignOn.Run 5) SignOn.Run a) displays most recent Crash Status b) displays SignOn.Txt c) displays SignOn form d) checks attempted access to the system by users when they begin operations and accepts the system configuration (User name) each user uses. (the .user file is "User name".user) 6) What happens next is dependent on the contents of the .user file. (SignOnChainFile or SignOnExitFile) CONTENTS OF A .USER FILE REQUIRED ENTRIES This is a sample configuration file. Configuration files and SignOn are described in the System Programmer's Guide. Entries must start with the ":" as the first character of a line. Any other text in the file is ignored by the SignOn program. All user configuration files must contain entries for the path and exit run file as described below. Path The default volume and directory names, the default file prefix, and the default password are required entries (these default entries are used by BTOS whenever a full file specification is not made). The entries may be left blank as in the file prefix and password shown here. :SignOnVolume:Sys :SignOnDirectory:Sys :SignOnFilePrefix: :SignOnPassword: This has the same effect as filling in the Path form of the executive with: Path [Volume] Sys [Directory] Sys [Default file prefix] [Password] Note that if the default volume or directory names are null, the Executive will reinvoke the SignOn program, and the user will be unable to use the Executive. If the password entry is left blank, then SignOn will use any password typed into the SignOn password form as the default password. Exit File The exit file specified is loaded by BTOS whenever a program terminates with an Exit or ErrorExit, or whenever ACTION-FINISH is pressed. :SignOnExitFile:[Sys]Exec.Run CONTENTS OF A .USER FILE (cont.) OPTIONAL ENTRIES Other entries looked for by Signon are the chain file, text file, and Exec command file entries (the following examples are not recognized by Signon because they do not start as the first character of the line). The chain file and text file specifications will use the default path parameters defined above if full file specifications are not made. If any of the optional entries are invalid, the Signon program will ignore them. Chain File The chain file is invoked by Signon before the exit file (required entry described above) is invoked. The following example starts a Submit file named Init.Sub. The parameters passed to the file start on the next line and are terminated by a line starting with a ":". Note the two null parameters: :SignOnChainFile:[Sys]Submit.Run Submit Init.Sub arg0 arg1 : This would be the same as filling out the Submit form from the Executive as: Submit File list Init.Sub [Parameters] arg0 arg1 [Force expansion?] [Show expansion?] Text File The text file is the name of a file or files to be displayed on the video by the SignOn program after logging on. If the file name is blank, then text in the configuration file is used up until the next ":" is encountered. The following three examples show the use of this entry: :SignOnTextFile:System.txt :SignOnTextFile: ### ### The text above is from System.Txt. The text ### below is from Messages.Txt ### :SignOnTextFile:Messages.Txt CONTENTS OF A .USER FILE (cont.) Executive Command File The Executive command file may be different for each user. If the entry is missing or invalid, the Executive uses the file [Sys]Sys.Cmds. This new command file can be generated by copying Sys.Cmds to (i.e.) My.Cmds in the appropriate directory. NOTE, that after you do the copy operation, you must sign on with the "User" name that matches the ".user" file before you can use the new ExecCmdFile. You may then use the Remove Command command to remove the commands that are not required. The following example specifies that the Executive is to use the commands in the command file My.Cmds, in the directory Charlie: :ExecCmdFile:[sys]My.Cmds EXAMPLE of the contents of a .user file: :SignOnVolume:Sys :SignOnDirectory:Charlie :SignOnFilePrefix: :SignOnPassword: :SignOnTextFile:[sys]Messages.Txt :SignOnChainFile:[Sys]Application.Run :SignOnExitFile:[Sys]Exec.Run :ExecCmdFile:[sys]MyCmds In the above example, the default Path is [Sys], the text contained in Messages.Txt will be displayed when the SignOn form is exited. The program that will be executed when the SignOn form is exited is Application.run. When Application.Run terminates the Executive will be executed but only the commands contained in the file MyCmds will be available. CONTENTS OF A .USER FILE (cont.) WRITEone OPTIONAL entries. WRITEone Format Sets If you find you need the Format file(s) ,Prog80.fmt, Prog132.Fmt (B22 only) or the default Wp.Fmt, somewhere other than [sys], you need only put them where you want then and then inform the Word Processor you have done so by adding an entry to your .user file of the form: :WpFormatSet:[d0]Prog80.Fmt WRITEone printer description file The printer description file is used to specify all the printers that are part of the printer configuration for the Word Processor. This entry in the ".user" file allows each User to have a unique Word Processor printer configuration file.(NOTE: this may specify the same file that Multiplan uses. see below) :WpPrinters:[d0]Sys.Printers WRITEone print wheels file This entry in a User file allows you to specify a different print wheel format file for each user. This print wheel file is generated by the Make Wheel Set command. :WpPrintWheels:[d0]Wp.Whl WRITEone Phrase file Phrases are stored in a phrase file specified by an entry in the .user file in the form: :WpPhrases:[d0]phrasefile CONTENTS OF A .USER FILE (cont.) WRITEone Dictionary If you find you need the Dictionary somewhere other than [sys], you need only put them where you want then and then inform the Word Processor you have done so by adding an entry to you .user file of the form: :WpDictionary:[!sys]Wp.Words WRITEone Personal Dictionary When using the spelling checker option of the Word Processor, it is possible to create a personal dictionary of special words you need. The Word Processor will automatically create such a personal dictionary in the form of [Sys]user.words. You can move this personal dictionary by adding an entry to your .user file in the form: :WpPersonalDictionary:[d0]My.dict1 Sorry, no documentation on the following entry :WpStatistics: Multiplan OPTIONAL entries. Multiplan printer description file The printer description file is used to specify all the printers that are part of the printer configuration for Multiplan. This entry in the ".user" file allows each User to have a unique Multiplan printer configuration file. (NOTE: this may specify the same file that the Word Processor uses. see above) :SysPrinters:[d0]My.Printers Passwords Password protection is available at three levels: Volume, Directory, or File. A VOLUME PASSWORD protects a Volume. A DIRECTORY PASSWORD protects a directory on a volume. A FILE PASSWORD protects a file in a directory on a volume. Volume passwords are assigned with the IVolume Command when a disk is initialized, or with the Change Volume Name Command. Directory passwords are assigned with the Create Directory Command. File passwords are specified with the Set Protection utility. Volume, directory and file passwords can consist of all alphanumeric characters, plus the period "." and the hyphen "-". A volume, directory, or file password can have a maximum of 12 characters. A file can be accessed by knowledge of its volume, directory, or file password. Knowledge of a volume password allows access to all the directories and all the files of that volume. Knowledge of a directory password allows access to all the files of that directory. Knowledge of a file password permits access that is dependent on the file protection level. (See "File Protection Level" below.) When a existing file is opened a single password can be supplied with the file specification. This password is compared first against the volume password, then against the directory password, and last against the file password (if one was specified). Access is granted to open the file if any of these comparisons match. When a new file is created a single password may be supplied that authorizes the creation of a file in the specified directory. It is not a password to be assigned to the file being created. This password is compared first against the volume password and then against the directory password. Access is granted to create the file if either of these comparisons match. (The Set Protection utility assigns a password to the file and the Create Directory utility assigns a password to the directory.) A default password can be specified in the Path Command. It is used whenever an explicit password is not specified to an operation. The default password, like an explicit one, is used in a comparison against the volume, directory, and file passwords (in that order). File Protection A file is assigned a FILE PROTECTION LEVEL. A file protection level specifies the access allowed to a file when the accessing program does not present a valid volume or directory password. A default file protection level is specified for the files of a directory when it is created with the Create Directory utility. When a file is created, it is assigned the default file protection level of the directory in which it is created. The file protection level of a file can be changed with the Set Protection Command. The file protection levels are described in Table 1 below. Three levels (unprotected, modify protected, and access protected) ignore file passwords; Six levels (modify password, access password, read password, nondirectory modify password, nondirectory access password, and nondirectory) use file passwords. The unprotected level is used for files that anyone can read or modify. The modify protected, modify password, and nondirectory modify password levels are used for files that anyone can read but for which a password is needed to modify. The access protected, access password, read password, and nondirectory access password levels are used for files that need a password to read or modify. ___________________________________________________________ | | | | ** Protection Level ** | The type Password needed to | | ** of the Directory ** |------------------------------| | ** or the File ** | READ a file | WRITE a file | |-----------------------------------------------------------| | 15 - Unprotected | None | None | |-----------------------------------------------------------| |* 5 - Modify Protected | None | Volume or | | | | Directory | |-----------------------------------------------------------| |* 7 - Modify Password | None | Volume or | | | | Directory or | | | | File | |-----------------------------------------------------------| |* 23 - Nondirectory Modify | None | Volume or | | Password | | File | |-----------------------------------------------------------| |# 0 - Access Protected | Volume or | Volume or | | | Directory | Directory | |-----------------------------------------------------------| |# 1 - Read Password | Volume or | Volume or | | | Directory or | Directory or | | | File | File | |-----------------------------------------------------------| |# 3 - Access Protected | Volume or | Volume or | | | Directory or | Directory or | | | File | File | |-----------------------------------------------------------| |# 19 - Nondirectory Access | Volume or | Volume or | | Password | Directory or | Directory or | | | File | File | |-----------------------------------------------------------| |# 51 - Nondirectory | Volume or | Volume or | | Password | File | File | |____________________________|______________|_______________| Table 1. File Protection Levels * = These levels of protection are used for files that anyone can read but for which a password is needed to modify. # = These levels of protection are used for files that need a password to read or modify. NOTE Protection levels 15, 5 and 0 ignore File passwords. Protection levels 7, 3, 1, 19, 23 and 51 use file passwords. BACKUP PROCEDURES BACKING UP FILES ON THE HARD DISK The SELECTIVE BACKUP command backs up (copies) individual files or directories from the winchester to a floppy, thus allowing archiving of personal files and requiring only read access to the files being archived. You must have the floppy disks already initialized (IVolumed) before you begin the backup. To simplify the Selective Backup procedure, IVolume your floppy disks with a volume name of ARCHIVE or use the IVArchive command to create (initialize ) the floppy disks. Consult the B20 Software Operations Guide for information on how the fill in the Selective Backup command form. NOTE Selective Backup is MUCH FASTER that a normal copy. The Selective Backup command stores the backed up files on the floppy disk(s) in a special way. Backed up floppies CAN NOT be inspected with the Files command to see what is on the floppy because of the special way the files are backed up. RESTORING FILES TO THE HARD DISK The RESTORE command restores files to the winchester disk drive that have been BACKED UP using the Selective Backup command. Consult the B20 Software Operations Guide for information on how the fill in the Restore command form. NOTE The directory information is maintained only on the first volume of the archive file. Thus, when the operation begins from a volume other than the first, Restore creates any required directory 10 sectors in size and unprotected. If 10 sectors are insufficient, create the necessary directory before beginning the Restore operation. Data recovery techniques for 301 and 329 error codes Error Code 301 - I/O Error (Read/Write Error) May be caused by hardware or media fault. Try to read the disk in another drive. If it reads with no errors the original disk drive is bad. If you still get 301 Errors in a different drive the diskette media is bad. Error Code 329 - Floppy disk timeout May be caused by hardware or media fault. Usually caused by defective media. Check to see if the floppy disk will spin freely in it's jacket. If the disk spins freely in it's jacket the cause of the error is probably a defective disk drive. Many 301 errors in the lab have been caused by disks not spinning freely in their jackets. This speed variation during a SAVE can cause a 301 error, if the retries the B25 attempts are not successful. If you continue to use the disk in this situation the 301 errors can progress to 329 errors. For 329 errors caused by the disk not spinning in the jacket try manually rotating the disk several times to see if it will free up. Be very careful not to touch the disk in the cigar shaped cut-out area of the disk jacket. If it frees up, immediately copy the disk to good media. Any time a disk appears to be corrupted or the data not readable you should execute the BACKUP VOLUME command to recover any data on the disk that is recoverable. BACKUP VOLUME should be used even if BTOS does not recognize the disk, as Backup Volume can recover any data that is still readable on a disk. NOTE If you use Backup Volume have some floppy disks available that have been initialized with a Volume Name of ARCHIVE or use the Change Volume Name command and change the Volume Name to ARCHIVE. This is necessary because Backup Volume looks for a floppy disk with this name. If you are trying to recover data from a floppy disk by using Backup Volume it will be easier if you use a Dual-Floppy System. Use the RESTORE Command to retrieve data from the backed up disk. IMPORTANT Make sure your path is set to the Volume where you want the data RESTOREed to, before you execute the Restore command. Also please note, if you press the floppy release door and your disk is not ejected, do not reach in and remove your disk. Close the door and carefully reopen it so that your disk is automatically ejected. Be aware that when you insert your floppy disk in the disk drive, you should watch the red light at the bottom of the floppy drive unit. It should come on twice. Once very fast and the second time there will be a sound coming from the drive associated with the light coming on. If this does not happen remove your floppy disk and insert it again. If you are not successful seek assistance. Failure to observe this sequence can result in the corruption of you disk.2 System Administrator Notes Page #¹۸kǷ- @ ` @ `   `$%<'()<+,@ x 61@ x  , vՃK[’դ uʑ#5ѥnIm@ @  `$%<'()<+,@ `  @ ` @ ` f|'0GP ~6eܷ&7d%6 `$%<'()<+,  @ `  `$%<'()<+,_d%;Uau  Œ $ٍ #   `$%<'()<+, @ `  `$%<'()<+, +•ݵc,ٕdҔc@ `  `$%<'()<+, @ `  `$%<'()<+,.¿/ҽ `$%<'()<+, @ `  @ `  `$%<'()<+, ^ c ¶ 0-̛̺̣J ] d  q I  @ ` @ `  `$%<'()<+, @  @ ` 0  µҺ¢ܣҿx Ґ “ ܣ ¤  ٽٴλيH٣ w ɢv @ $@ $ $(,@  $(, @ 0  @  $(, XxzE e ˜[awxɝը3Wy<Ht՜| Շ D f ~ $VC @ 0  $(,@  @  $(,@ @ $@ x  "%?†Ҧ5=”ܱ. 8 ¦ $VWٷ. Ψٽٱ, . 9 Ʉ- @  $(,  $(,@ x @ x @  @  $(,1A¿pܦ%\əZҙ^/!1B G } l  qҧ~Ʌ0 p@ x  $(,  $(,@   $(,@ @ @ 0  )J27…ݺagS X 0 9 ³ 5)K28ʅ S Y . / :  @ @  @  $(,@ x x  @ 0 @  @ x x £ҥУ@ɣ@ ,@  $(,  ((()P xxxxElite 12GBFOB "1.0.4 #!(5d?OYsRKey words recognized by Make Wheel Set Energy - Requires 256 entries - one for each character (value is 0-7) Fixed - Pitch of the print wheel - (240 divided by the required pitch) (12 Pitch is Fixed 20 ) (240 / 12 = 20 ) HalfBright - Displayed Video attribute for the selected print wheel Mapped - Requires 256 entries - one for each character (value is 00h - FFh) Overstrike - Pitch Proportional * WheelName 2 &@'@m@@@F@@    ()P xxxxElite 12G@ "3.0.7 Courier 10  () ~ ! @ # $ % () & * ( ) _ + ()( )() ^ 1 2 3 4 5 6 7 8 9 0 - = Q W E R T Y U I O P () < > | (\) q w e r t y u i o p () [ ] 7 8 9 A S D F G H J K L : " { } a s d f g h j k l ; ' 4 5 6 - Z X C V B N M , . ? ` z x c v b n m , . / 1 2 3 Those characters enclosed in ( ) are not available on this print wheel.2 oq @ @@U@V@@@@@@6@7@q@@@@%@&@'@o@qoq@ ,  ()P xxxxElite 12G@qo"3.0.7 BEACON Reference Manual Version 0.6 May 15, 1986 Systems & Communications Group Computing Services School of Business Administration University of Michigan Contents Introduction 2 Summary of BEACON Commands 3 Detailed Description of BEACON Commands 6 BEACON Input Editor Key Assignments 28 BEACON Version 0.6 Enhancements 30 Limitations of this version of BEACON 31 APPENDIX A: BTOS Character Codes 32 Introduction This document is a reference manual for BEACON. BEACON is a communications program written by Computing Services in the School of Business Administration at the University of Michigan. BEACON runs on the Burroughs B25 workstations, making the B25 a highly functional terminal that can be used with virtually all host systems. BEACON saves the last 2500 lines (approximately) that appeared on the terminal screen during an host session. Using BEACON, you can store lines from this session in a B25 file or print them on a printer attached to the B25. You can also edit a line from the session and re-submit it to the host. Lines that scroll off the top of the screen during an host session are not lost; you can scroll back and forth freely to view lines in the session, up to the limit of lines saved. This reference manual is intended as a complete technical description of BEACON. You may wish to refer to the BEACON Tutorial for a basic introduction to using BEACON. A Note on Notation In this manual, three kinds of syntax symbols are used to specify notation or syntax of commands, namely: Angle brackets You are required to specify this parameter. Square bracket [parameter] You have the option of specifying this parameter else a default value will be used. Vertical bar parameter|parameter You can choose either of the alternatives separated by |. Do not enclose the value in angle or square brackets. Summary of BEACON Commands The following list summarizes one of the two sets of commands accepted by BEACON. (The other set is accepted by the BEACON Input Editor and is listed in the Input Editor section of this manual). Parameters are omitted from the list. (See detailed descriptions.) While most BEACON commands can be issued by typing the full command or an unambiguous abbreviation, including prefix character (%) from the command line, as given in the list on the next page, many commands are intended to be issued with a single keystroke. If this is the case, the key name is also listed. When issuing a command by typing the full or abbreviated name, the command should be the first entry on the input line, should be followed by its parameters if any are required, and should be terminated by the RETURN key. You may assign any BEACON command to a single key if you wish, using the %DefineKey command. A list and a brief description of all the BEACON local commands is provided on the next page. A detailed description of each of the commands is provided on the following pages. Command Function %AnswerBackMessage Specifies the VT100 answerback message. %AutoExit Returns to BTOS executive when disconnected. %AutoView Enters VIEW mode upon invalid parameter entry. %BackwardScroll Moves back a specific number of lines in the history. %BaudRate Establishes baud rate. %BinaryFileType Sets file transfer file as type BINARY. %Bye Terminates KERMIT while conversing with a server. %ClearAllTabs Removes all tab stops. %ClearTabs Removes tab stops. %Column Sets left margin to a specific column. %Connect Establishes connection with a host. %CTS Specifies the use of CTS line for transmission. %CursorApplicationMode Designates VT100 cursor key behavior. %DataBits Specifies number of data bits for transmission. %DefineKey Defines a string to a key. %Disconnect Terminates connection with host. %Dump Prints a portion of history to output device. %Encipher Enciphers a text file. %EncipheredSubmit Submits a enciphered (%Encipher) file. %Exit Terminates execution and returns to BTOS executive. %Explain Display local command syntax and description. %Finish Instructs host's KERMIT server to exit server mode. %ForwardScroll Moves ahead a specific number of lines in the history. %Get Retrieves a file from a host KERMIT server. %HalfDuplex Enables local echo of keystrokes. %Help Displays a screen of useful information. %HistoryReset Empties the contents of the history. %HistoryRestore Restores history from a file. %HistorySave Saves current history in a file. %KeypadApplicationMode Designates VT100 numeric keypad behavior. %KeyReset Resets all key definitions to default values. %KeyRestore Restore key definitions in a file %KeySave Saves current key definitions in a file. %Line Moves the view to a specific line in the history. %ListKeys Displays all of the current key definitions. %LogTransactions Establishes file transfer logging facility. %LongHistory Verifies all screens get entered into the history. %MacroAssign Assigns a string to a macro variable in macro mode. %MacroBegin Enters the macro mode. %MacroElse Else clause of a macro if statement. %MacroEnd Exits from macro mode. %MacroEndif Specifies the end of an macro if statement. %MacroIf If clause of a macro. %MacroLog Allows tracing of macros to a file. %MacroResponse Reads in a user response for a macro variable. %MacroWrite Prompts the user to enter some input. %MarginBell Enables bell when cursor is close to the end of line. %NewLine Changes CR mapping to CRLF. %NumberDisplay Enables display of history line numbers. %OutputDevice Sets the default printer for %Print and %Dump. %PageSize Defines the number of lines to a page. %ParameterReset Resets all system parameters to default values. %ParameterRestore Restore all systems parameters from a file. %ParameterSave Save all system parameters in a file. %Parity Sets parity type for transmission. %Password Sets the default password for all BTOS file accesses. %PortLetter Selects serial port for transmission. %Prefix Defines the first character of local commands. %Print Prints a file on the output device. %Promptlength Defines the length of the host's prompt. %ReceiveFiles Invokes KERMIT receive file transfer mode. %RecordSession Initiates recording session in a file. %Remote Send commands to host KERMIT server. %Reset Reset to the default environment. %Restore Restores an environment from a file. %Save Saves the current environment in a file. %SendFiles Invokes KERMIT send file transfer mode. %Server Place BEACON into KERMIT server mode. %SetEigthBitPrefix Establishes KERMIT's 8th bit prefix mechanism. %SetEigthBitPrefixChar Establishes KERMIT's 8th bit prefix character. %SetExplainFile Sets the file to be displayed by the %Explain command. %SetHelpFile Sets the file to be displayed by the %Help command. %SetReceiveEOLChar Sets KERMIT's receive end-of-line character. %SetReceiveEORString Sets KERMIT's receive end-of-record string. %SetReceivePacketLength Sets KERMIT's receive packet length. %SetReceivePadChar Sets KERMIT's receive pad character count. %SetReceivePadCount Sets KERMIT's receive pad character. %SetReceiveStartOfPacketChar Sets KERMIT's receive start-of-packet character. %SetReceiveTimeOut Sets KERMIT's receive time-out. %SetRepeatPrefixChar Sets KERMIT's repeat prefix character. %SetRetryInitialCount Sets KERMIT's initial packet retry maximum. %SetRetryPacketCount Sets KERMIT's normal packet retry maximum. %SetSendEOLChar Sets KERMIT's send end-of-line character. %SetSendEORString Sets KERMIT's send end-of-record string. %SetSendPause Sets KERMIT's delay before sending first packet. %SetSendQuoteChar Sets KERMIT's control quote character. %SetSendRecordWrap Enables word-wrap of files in file transfer. %SetSendRecordWrapCount Establishes maximum line length of word-wrap files. %SetSendStartOfPacketChar Sets KERMIT's send start-of-packet character. %SetServerTimeout Timeout interval for BEACON KERMIT server. %SetTabs Sets tab stops. %SetTransferType Establishes protocol used for file transfer. %SetXModemBinaryFileType Enables CRLF/LF mapping in XModem file transfer. %ShiftSize Defines number of columns in horizontal shifting. %StopBits Sets number of stop bits for transmission. %Submit Initiates reading a file for keyboard input. %Suspend Suspends execution for a specified duration. %TypeScript Records all the user generated keystrokes in a file. %View Creates a view screen to modify system parameters. %VT100Mode Selects between VT100 and VT52 emulation mode. %WaitUntil Suspends execution until the specified time. %Width Selects number of characters per line (80/132). %Wraparound Enables auto line wrap of the screen. %XonXoff Enables transmission of XONXOFF. Detailed Description of BEACON Commands %AnswerBackMessage The purpose of this command is to specify the VT100 answerback message. A DEC VT100 terminal sends the host the current answerback message when the terminal receives an ASCII ENQ (Hex 05). BEACON has a default answerback message of the null string (no characters). The syntax of this command is as follows: %AnswerBackMessage [Answerback Message String] %AutoExit The purpose of this command is to automatically return to the BTOS executive upon loss of the communication channel. This command accepts one boolean parameter (either "TRUE" or "FALSE"). The initial value for this command is "FALSE". The syntax of this command is as follows: %AutoExit %AutoView The purpose of this command is to configure BEACON to automatically enter VIEW mode upon the specification of invalid parameters. This allows the user to reenter the parameters for the given command. This command accepts one boolean parameter (either "TRUE" or "FALSE"). The initial value for this command is "FALSE". The syntax of this command is as follows: %AutoView %BackwardScroll The purpose of this command is to shift the view back in the history the specified number of lines. This command is similar to key, but it allows users to move back a specific number of lines. If this parameter is not specified then this command is exactly the same as pressing the key. The syntax of this command is as follows: %BackwardScroll [number of lines to move back] %BaudRate The purpose of this command is to establish the baud rate for communications between host and B25. Valid baud rates are "300", "600", "1200", "2400", "4800", "9600" and "19200". If the baud rate is not specified then the default value of "9600" is used. The syntax of this command is as follows: %BaudRate [300|600|1200|2400|4800|9600|19200] %BinaryFileType The purpose of this command is to specify that the next file being transferred is a binary file. Specifying a file as type binary will inhibit the mapping of kermit's end-of-record specifier () to BTOS's end-of-record specifier (). This command requires one boolean parameter (either "TRUE" or "FALSE") and the initial value of this parameter is "FALSE". The syntax of this command is as follows: %BinaryFileType <"TRUE"|"FALSE"> %Bye The purpose of this command is to terminate connection between BEACON and a KERMIT server program. This command sends a KERMIT packet to host to instruct the host to disconnect. This command is only useful when connect to a host which is a KERMIT server. The syntax of this command is as follows: %Bye %ClearAllTabs The purpose of this command is to remove all active tab stops. Note that the %SetTabs command can be used to set tab stops. The syntax of this command is as follows: %ClearAllTabs %ClearTabs The purpose of this command is to remove tab stops. This command accepts several optional integer parameters to indicate the column numbers at which to remove tabs. If no parameters are specified, then the tab stop at the most recent column of the VT100 screen is removed. Note that the %SetTabs command can be used to set tab stops. The syntax of this command is as follows: %ClearTabs [column[,column[...]]] %Column The purpose of this command is to specify the desired position of the display with respect to the history (VT100 text). This command accepts an integer parameter specifying the start column. If a parameter is not specified then the display is set at the first column. This syntax of this command is as follows: %Column [display start column] %Connect The purpose of this command is to establish a connection between a B25 and the host. Note that users are not required to issue this command because connection is established automatically, if needed. The syntax of this command is as follows: %Connect %CTS The purpose of this command is to instruct the serial port to monitor CTS (Clear To Send) line. This command accepts one boolean parameter (either "TRUE" or "FALSE"). The initial value for this command is "FALSE". Note that most telephone modems do not support CTS. The syntax of this command is as follows: %CTS %CursorApplicationMode The purpose of this command is to enable/disable the DEC VT100 application mode cursor keys. Usually, only the host computer will select which mode the VT100 cursor keys will be in. This command accepts one boolean parameter of which "TRUE" indicates that the cursor keys will generate application mode escape sequences, and "FALSE" indicates that these keys will generate the normal escape sequences. The syntax of this command is as follows: %CursorApplicationMode %DataBits The purpose of this command is to set the number of data bits for serial port transmission. This command accepts an integer parameter with values of either "5", "6", "7", or "8". If a value is not specified then a default value of "7" data bits is used for transmission. The syntax of this command is as follows: %DataBits [5|6|7|8] %DefineKey The purpose of this command is to redefine a key on the keyboard to a specified string. This command accepts two parameters: the first one being the key to be defined and the second to be the defined string. The specification of the first parameter is the integer value corresponding to the BTOS character value for that key. (Refer to Appendix A for the BTOS definitions of the keys.) For the second parameter, if a string is not specified then the key is set to its default definition. The syntax of this command is as follows: %DefineKey [string] %Disconnect The purpose of this command is to terminate the connection between a B25 and the host. This command guarantees that the carrier will be dropped by the B25. Note that the users are not required to issue this command because the line is disconnected automatically with the execution of the %Exit command. The syntax of this command is as follows: %Disconnect %Dump The purpose of this command is to print a portion of the history on the specified device. This command accepts two integer parameters which represent the line numbers of the history range to be printed and a third optional parameter that specifies the output device. If this output device is not specified then the default output device (set by %OutputDevice command) is used. The syntax of this command is as follows: %Dump [printer] %Encipher The purpose of this command is to encipher a file into an unreadable format. Enciphered files may then be used for input to the program with the use of the %EncipheredSubmit command. Note that there is no command to decipher this file once it is enciphered. The syntax of this command is as follows: %Encode %EncipheredSubmit The purpose of this command is read input from a B25 encoded file (enciphered by the %Encipher command) rather than the keyboard. All lines up to end-of-file are read, decoded, and treated as user input lines. The file is closed when an key is pressed. The syntax of this command is as follows: %EncipheredSubmit %Exit The purpose of this command is to exit the BEACON program. This command closes all local files opened during the execution of the BEACON program. This command does not accept any parameters. The syntax of this command is as follows: %Exit The CODE FINISH key combination also generates the %EXIT command. Pressing the FINISH key alone will prompt the user for a confirmation. %Explain The purpose of this command is to display the description and the syntax of all of the available commands. The contents of the file, designated by the %SetExplainFile command, are displayed on the screen. The description displayed by the %Explain command becomes part of the screen history and can then be viewed at any time. This command does not accept any parameters. The syntax of this command is as follows: %Explain The + key combination also generates the %Explain command. The key alone generates the %Help command for a brief description of important key definitions and commands. %Finish The purpose of this command is to instruct the host to exit KERMIT server mode but to remain connected. This command sends a KERMIT packet to host to instruct the host to leave KERMIT server mode. This command is only useful when connect to a host which is a KERMIT server. The syntax of this command is as follows: %Finish %ForwardScroll The purpose of this command is to shift the view forward in the history the specified number of lines. This command is similar to key, but it allows users to move forward a specific number of lines. If a parameter is not specified then this command is exactly the same as pressing the key. The syntax of this command is as follows: %ForwardScroll [number of lines to move forward] %Get The purpose of this command is to instruct the host's KERMIT server to send a file from the host to the local B25. This command is only needed when connected to a host which is a KERMIT server. The syntax of this command is as follows: %Get [Local filename] %HalfDuplex The purpose of this command is to enable the local echo of user input to the screen. This command accepts one boolean parameter (either "TRUE" or "FALSE"). The initial value for this parameter is "FALSE". The syntax of this command is as follows: %HalfDuplex %Help The purpose of this command is to display a brief summary of the useful local commands and function keys. A temporary screen is created and the contents of the file designated by the %SetHelpFile command are displayed on the screen. This screen disappears upon the next user input. This command does not accept any parameters. The syntax of this command is as follows: %Help The key also generates the %Help command for a brief description of BEACON's commands and key definitions. The key combination of + generates the %Explain for a brief description of all BEACON's local commands. %HistoryReset The purpose of this command is to empty the history. The syntax of this command is as follows: %HistoryReset %HistoryRestore The purpose of this command is to empty the history and copy the contents of a specified file into the history. If a file is not specified then the file "BEACONDefault.His" on the current path is used. This command appends ".His" to the specified filename. The syntax of this command is as follows: %HistoryRestore [filename] %HistorySave The purpose of this command is save the current history into a specified local file. If a file is not specified then the file "BEACONDefault.His" on the current path, is used. This command appends ".His" to the specified filename. The syntax of this command is as follows: %HistorySave [filename] %KeypadApplicationMode The purpose of this command is to enable/disable the DEC VT100 application mode of the numeric keypad. Usually, only the host computer will select when the numeric keypad is in application mode. This command accepts one boolean parameter of which "TRUE" indicates that the keypad will generate application mode escape sequences, and "FALSE" indicates that these keys will generate the normal numeric values. The syntax of this command is as follows: %KeypadApplicationMode %KeyReset The purpose of this command is to reset all of the key definitions from the file "[Sys]BEACONDefault". The syntax of this command is as follows: %KeyReset %KeyRestore The purpose of this command is to restore the key definitions from a local B25 key definition file. If a filename is not specified then the file "BEACONDefault.Key" on the current path is used to reinitialize the key definitions. This command appends ".Key" to the specified filename. The syntax of this command is as follows: %KeyRestore [filename] %KeySave The purpose of this command is to save the current key definitions in a B25 file. If a filename is not specified then the file "BEACONDefault.Key" on the current path, is used to save the key definitions. This command appends ".Key" to the specified filename. The syntax of this command is as follows: %KeySave [filename] %Line The purpose of this command is to position the view of the history at a specific line. This is the line number which is displayed on the top frame of the screen. The syntax of this command is as follows: %Line %ListKeys The purpose of this command is to display the current values of all the key definitions. The syntax of this command is as follows: %ListKeys %LogTransactions The purpose of this command is to initiate and terminate the logging of file transfer. Packet content and program status appear in the log file. This command accepts one string parameter which is the name of the log file. Logging is terminated by using this command with no parameters. The syntax of this command is as follows: %LogTransactions [Log file name] %LongHistory The purpose of this command is to enable Long History Mode. With Long History Mode enabled, the contents of the current VT100 screen are copied to the history whenever the host attempts to position the VT100's cursor in the home position. (Home position is ROW=1 and COLUMN=1 or the upper left-most corner of the screen.) With Long History Mode enabled, all screens in menu driven applications should be copied into the history. The syntax of this command is as follows: %LongHistory %MacroAssign The purpose of this command is to define a string to a Macro variable that is active only in the %Macro mode. This command is only acceptable in %Macro mode. This command expects two parameters: the first one being the Macro variable in the range from "0" to "9" and the second to be the defined string. If a string is not specified then the Macro variable is set to null. The use of the Literal function key (F5) may be required to correctly designate the Macro variable. The syntax of this command is as follows: %MacroAssign [string] %MacroBegin The purpose of this command is to enter the %Macro mode in BEACON program. This is a sophisticated mode that allows for conditional execution of commands, prompt the user for various inputs, display status messages etc. All the commands that start with the word "%Macro" are also enabled upon the execution of this command and are disabled at the execution of %MacroEnd command. This command does not accept any parameters. The syntax of this command is as follows: %MacroBegin %MacroElse The purpose of this command is to define the Else part of a conditional execution block. This command is only acceptable in %Macro mode. If the condition specified by the %MacroIf statement is "FALSE" then the instructions starting from the %MacroElse to %MacroEndIf are executed, otherwise this blocked is skipped. The syntax of this command is as follows: %MacroElse %MacroEnd The purpose of this command is to exit the %Macro mode. Once out of the %Macro mode all the Macro variable assignments made are lost and the %Macro commands are no longer accepted. This command is only acceptable in %Macro mode. This command does not accept any parameters. The syntax of this command is as follows: %MacroEnd %MacroEndIf The purpose of this command is to terminate the %MacroIf command. This command does not accept any parameters. This command is only acceptable in %Macro mode. The syntax of this command is as follows: %MacroEndIf %MacroIf The purpose of this command is to allow for conditional execution of commands. This command accepts three string parameters of which the second string is an conditional operator. The first and third parameters are the operands. If the assertion is valid or "TRUE", then all commands following the %MacroIf are executed until a %MacroEndIf, %MacroElse, or %MacroEnd is encountered. If the assertion is false, then all commands following the %MacroIf are skipped until a %MacroEndIf, %MacroElse, or %MacroEnd is encountered. Currently, only the operator "=" is supported. The syntax of this command is as follows: %MacroIf %MacroLog The purpose of this command is to establish a log file for %Macro processing. This is very useful when trying to debug user-written macros. This command accepts optional parameter which is the file name of the log file. Entering this command with no parameters terminates the logging of macro commands. The syntax of this command is as follows: %MacroIf [filename] %MacroResponse The purpose of this commands is to allow for user assignment of Macro variables. This command accepts one integer parameter between "0" and "9" which designates a Macro variable. This command is only acceptable in %Macro mode. The user is then prompted in the command line to input a string value. This value is then assigned to the %Macro variable. The syntax of this command is as follows: %MacroResponse %MacroWrite The purpose of this commands is to write a message in the status line on the screen. This command accepts a string parameter. This command is only acceptable in %Macro mode. This command can be used to prompt for user inputs using %MacroResponse command. The syntax of this command is as follows: %MacroWrite %MarginBell The purpose of this commands is to enable the beep whenever the user is typing beyond the tenth column from the end of the screen. This command accepts a boolean parameter (either "TRUE" or "FALSE"). The initial value for this command is "FALSE". The syntax of this command is as follows: %MarginBell %NewLine The purpose of this commands is to enable the mapping of carriage returns to carriage return and line feeds. This command accepts a boolean parameter (either "TRUE" or "FALSE"). The initial value for this command is "FALSE". The syntax of this command is as follows: %NewLine %NumberDisplay The purpose of this commands is to enable the Number Display Mode. With the Number Display Mode enabled, all line numbers that are associated with lines in the history are displayed on the screen. Having Number Display Mode enabled might be useful when using the %DUMP and %LINE commands. This command accepts a boolean parameter (either "TRUE" or "FALSE"). The initial value for this command is "FALSE". The syntax of this command is as follows: %NumberDisplay %OutputDevice The purpose of this command is specify a default output device for printing purposes. If a printer is not specified then the default printing device "[SPL]" is used. The syntax of this command is as follows: %OUTPUTDEVICE [printer] %PageSize The purpose of this command is to specify the number of lines the screen is to be scrolled when using the and keys. If a number is not specified with this command, the page size is set to the default of 20 lines. The syntax of this command is as follows: %PageSize [# of lines per page] %ParameterReset The purpose of this command is to reset all the system parameters such as communication parameters and editor features to their default values. The syntax of this command is as follows: %ParameterReset %ParameterRestore The purpose of this command is to restore all the system parameters such as communication parameters and editor features from a specified file. If a file is not specified then the file "BEACONDefault.Par" is used. This command appends ".Par" to the specified filename. The syntax of this command is as follows: %ParameterRestore [filename] %ParameterSave The purpose of this command is to save all the system parameters such as communication parameters and editor features into a specified file. If a file is not specified then the file "BEACONDefault.Par" is used. This command appends ".Par" to the specified filename. The syntax of this command is as follows: %ParameterSave [filename] %Parity The purpose of this command is to select the type of parity desired for serial port transmission. This command accepts a character corresponding to parity such as "E" for even parity, "O" for odd parity, "N" for no parity, "0" for zero parity and "1" for one parity. The program is initialized with "0" (zero) parity. The syntax of this command is as follows: %Parity %Password The purpose of this command is to enter a password for the BTOS file system. This password is used to open, read and write files. The initial value for this command is a null string. This value is not saved when doing ParameterSave or global Save. This command accepts one optional parameter. If this parameter is not specified then a null string is used. The syntax of this command is as follows: %Password [password] %PortLetter The purpose of this command is to select a B25 serial port. This command sets the active port to the one specified. Valid ports are either "A" or "B". If a port is not specified then the default port "A" is used. The syntax of this command is as follows: %PortLetter [port char] %Prefix The purpose of this command is to specify a custom command prefix for all local commands. If a character is not specified with this command then it is set to the default prefix of "%". The syntax of this command is specified below: %Prefix [prefix char] %Print The purpose of this command is to print or copy a local file to a local printer. If the printer is not specified then the default output device (set by the %OutputDevice command) is assumed. The syntax of this command is a follows: %Print [printer] Valid printer names are [SPL] for draft (Dot matrix) and [SPLB] for letter quality printer or a filename if output is to be saved in a file. This command can be stopped by the key. %PromptLength This purpose of this command is to specify the length of the host's prompt on a line. This parameter is used during line re-entry feature as to ignore the host prompt characters. This command accepts an integer parameter to specify the prompt length. If this parameter is not specified then the default prompt length of "1" character is used. The syntax of this command is as follows: %PromptLength [length of prompt] %ReceiveFiles The purpose of this command is to place BEACON into receive file mode. An optional string parameter may be specified which will be used as the local file name for the first incoming file. (Note that when in receive file mode, the kermit protocol allows for the reception of more than one file. Filenames are transferred with files.) The syntax of this command is as follows: %ReceiveFiles [BTOS file name] %RecordSession The purpose of this command is to record the terminal session in a local file. If a file is not specified then this command terminates the current recording session (if any). The syntax of this command is as follows: %RecordSession [filename] %Remote The purpose of this command is to send executable commands to the host KERMIT server. This command accepts one or two parameters. The first parameter is a valid host command (in proper syntax) and the optional second parameter is the KERMIT packet type used for transmission of the command to the host. (The default value of the second parameter is "K".) This command is only useful when connected to a host KERMIT server. The syntax of this command is as follows: %Remote [KERMIT packet type] %Reset The purpose of this command is to reset the program environment. This command makes calls to all the Reset commands in order. This command does not accept any parameters. The syntax of this command is as follows: %Reset %Restore The purpose of this command is to restore the program environment from a local file. This command makes calls to all the Restore commands in order with the specified filename. If a filename is not specified then the default filename of "BEACONDefault" is used. Note that all the Restore commands append unique suffixes to filename. The syntax of this command is as follows: %Restore [filename] %Save The purpose of this command is to save the program environment into a local file. This command makes calls to all the Save commands in order with the specified filename. If a filename is not specified then the default filename of "BEACONDefault" is used. Note that all the Save commands append unique suffixes to filename. The syntax of this command is as follows: %Save [filename] %SendFiles The purpose of this command is place BEACON in send file mode. This command requires one string parameter which is used as the name of the BTOS file to send. An optional second string parameter is the desired file name on the host system. If no second parameter is specified, then the BTOS name of the file will be used as the host's file name. The syntax of this command is as follows: %SendFiles [Host file name] %Server The purpose of this command is place BEACON in KERMIT server mode. This will allow the computer at the other end of the connection to send file transfer requests in KERMIT server packets. Currently, KERMIT server mode only supports requests for file transfer and remote specification of BEACON commands. The key can be used to exit KERMIT server mode. The syntax of this command is as follows: %Server %SetEigthBitPrefix The purpose of this command is to enable the Kermit 8th bit prefixing mechanism. This allows for the transmission of 8 bit data through a 7 bit network. This command requires one boolean parameter. Of value of "TRUE" for this parameter enables the request for 8th bit prefixing to be performed. (Note that both computers have to agree to perform 8th bit prefixing.) The initial value for this command is "FALSE". The syntax of this command is as follows: %SetEigthBitPrefix <"TRUE"|"FALSE"> %SetEigthBitPrefixChar The purpose of this command is establish the ASCII character used as the 8th bit prefixing character. The default value for this character is "&". The syntax of this command is as follows: %SetEigthBitPrefixChar %SetExplainFile The purpose of this command is to specify a file that is to be displayed on the screen when the %Explain command is generated. If the filename is not specified then the default value of "[Sys]BEACONExplain" is used. The syntax of this command is as follows: %SetExplainFile [filename] %SetHelpFile The purpose of this command is to specify a file that is to be displayed on the screen when the %Help command is generated. If the filename is not specified then the default value of "[Sys]BEACONHelp" is used. The syntax of this command is as follows: %SetHelpFile [filename] %SetReceiveEOLChar The purpose of this command is to establish the End-Of-Line character that BEACON requires with all incoming packets. The default value for this parameter is ASCII 13 (Carriage Return). The syntax of this command is as follows: %SetReceiveEOLChar %SetReceiveEORString The purpose of this command is to establish which End-Of-Record delimiter to expect when receiving text files. Acceptable values for this parameter are "CR" (), "LF" (), or "CRLF" (). The initial value for this parameter is "CRLF". The syntax of this command is as follows: %SetReceiveEORString <"CR"|"LF"|"CRLF"> %SetReceivePacketLength The purpose of this command is to specify the maximum length of BEACON's receive packets. Packet lengths must be between 10 and 94 characters (inclusive). A user might want to specify shorter packets if the connection with the other computer is noisy. The default packet length is 94 characters. The syntax of this command is as follows: %SetReceivePacketLength %SetReceivePadChar The purpose of this command is to specify which character should be sent before receiving packets from the other computer. (The number of times this character is sent is specified by the %SetReceivePadCount command.) The default value for this character is ASCII 0 (NUL). The syntax of this command is as follows: %SetReceivePadChar %SetReceivePadCount The purpose of this command is to specify the number of pad characters that must be sent by the other computer before sending a packet to BEACON. (see %SetReceivePadCount) The default value for this count is zero (which means no padding is performed). The syntax of this command is as follows: %SetReceivePadCount %SetReceiveStartOfPacketChar The purpose of this command is to specify which character to look for which designates the beginning of a receive packet. The default value for this character is ASCII 1 (SOH). The syntax of this command is as follows: %SetReceiveStartOfPacketChar %SetReceiveTimeOut The purpose of this command is specify the amount of time (in seconds) to wait for a packet. The default value for this timeout is 10 seconds. If the program does timeout, appropriate action will be taken. (Either resending the last packet, or aborting the file transfer.) The syntax of this command is as follows: %SetReceiveTimeOut %SetRepeatPrefixChar The purpose of this command is to specify which character will be used as the repeat prefix character. The initial character used is "~" (tilde). The syntax of this command is as follows: %SetRepeatPrefixChar %SetRetryInitialCount The purpose of this command is to specify the number of times to retry the first packet before aborting. The default value for this parameter is 10. The syntax of this command is as follows: %SetRetryInitialCount %SetRetryPacketCount The purpose of this command is to specify the number of times to resend packets which are not received correctly before aborting. The default value for this parameter is 5. The syntax of this command is as follows: %SetRetryPacketCount %SetSendEOLChar The purpose of this command is specify the End-Of-Line character on outgoing packets. This character is usually set by the other computer. The default value for this character is ASCII 13 (Carriage Return). The syntax of this command is as follows: %SetSendEOLChar %SetSendEORString The purpose of this command is to establish which End-Of-Record delimiter to use when sending text files. Acceptable values for this parameter are "CR" (), "LF" (), or "CRLF" (). The initial value for this parameter is "CRLF". The syntax of this command is as follows: %SetReceiveEORString <"CR"|"LF"|"CRLF"> %SetSendPause The purpose of this command is to specify the number of seconds to delay before sending the first packet. The initial value of this parameter is zero (no delay). The syntax of this command is as follows: %SetSendPause %SetSendQuoteChar The purpose of this command is to specify the character that is used for control quoting in outgoing packets. The initial value for this character is "#". The syntax of this command is as follows: %SetSendQuoteChar %SetSendRecordWrap The purpose of this command is to enable line-wrapping of outgoing files. When this function is enabled, an SendEOLString is inserted in the record assuring lines of maximum length specified by SendRecordWrapCount (see the next command). This initial value of this parameter is "FALSE". The syntax of this command is as follows: %SetSendRecordWrap <"TRUE"|"FALSE"> %SetSendRecordWrapCount The purpose of this command is to establish the maximum line length of outgoing files. This parameter is enabled by the SetSendRecordWrap parameter (see the previous command). When SendRecordWrap is enabled, an SendEOLString is inserted in the record assuring lines of maximum length specified by this parameter. This initial value of this parameter is 80. The syntax of this command is as follows: %SetSendRecordWrap Count %SetSendStartOfPacketChar The purpose of this command is specify the first character of a send packet. The initial value for this character is ASCII 01 (SOH). The syntax of this command is as follows: %SetSendStartOfPacketChar %SetServerTimeout The purpose of this command is specify the timeout value (in seconds) when KERMIT is in server mode (see %Server command). The initial value of this parameter is 120. The syntax of this command is as follows: %SetServerTimeout %SetTabs The purpose of this command is to insert tab stops. This command accepts several optional integer parameters to indicate the column numbers at which to insert tab stops. If no parameters are specified, then the tab stop at the most recent column of the VT100 screen is inserted. Note that the %ClearTabs command can be used to clear tab stops. The syntax of this command is as follows: %SetTabs [column[,column[...]]] %SetTransferType The purpose of this command is to specify the protocol used for file transfer. BEACON supports "ASCII" and "BINARY" (the two file transfer protocols supported by Burroughs ATE), "KERMIT" and "XMODEM". Note that "ASCII", "BINARY", and "XMODEM" require a serial port configuration of %DATABITS=8, %PARITY=N, and %XONXOFF=FALSE. The initial value for this parameter is "KERMIT". The syntax of this command is as follows: %SetTransferType <"ASCII"|"BINARY"|"KERMIT"|"XMODEM"> %SetXModemBinaryFiletype The purpose of this command is to disable CRLF to LF mapping of files sent using the XModem file transfer protocol. The initial value for this parameter is "TRUE". The syntax of this command is as follows: %SetXModemBinaryFiletype <"TRUE"|"FALSE"> %ShiftSize The purpose of this command is to specify the number of columns to shift left or right whenever implicit shift, or key is pressed. If a parameter is not specified then the default shift size of 20 is used. The syntax of this command is as follows: %ShiftSize [# of columns to be shifted] %StopBits The purpose of this command is to set the number of stop bits for serial port transmission. This command accepts an integer parameter with values of either "1", "2". If the number of stopbits is not specified then the default value of "1" stop bits is used. The syntax of this command is as follows: %StopBits [1|2] %Submit The purpose of this command is to redirect the input stream to a local file rather than from the keyboard. All lines up to end-of-file are read and treated as user input lines. The submit file is closed when a key is pressed. The syntax of this command is as follows: %Submit %Suspend The purpose of this command is to pause user input processing for a specified duration of time. The duration is specified in the units of seconds. Valid duration is from "0" to "32767" seconds. The syntax of this command is as follows: %Suspend %TypeScript This command allows the user to record all his keystrokes in a file. This command is very similar to the BTOS Record command. This command differs from the %RecordSession command since %TypeScript command does not record the host output but the %recordSession does. This command is very useful in creating Submit files. This command accepts one string parameter representing a filename. If a file is not specified then the current TypeScript recording session is terminated (if any). The syntax of this command is as follows: %TypeScript [filename] %View This command allows allows the user to alter system parameters in a pull-down menu type fashion. This command accepts any number of parameters which must be names of valid local "%" commands. Upon issuing the %View command with valid parameters, a temporary screen is created with the current values of the parameters to these commands. The user is then allowed to modify these values. Hitting the key updates all of the values of the parameters and terminates the %View command. Hitting just the key updates the values of the parameters of the active command and terminates the %View command. Hitting the key does not update the values of the parameters but does terminate the %View command. The syntax of this command is as follows: %View View also accepts keywords as parameters. Keywords must be spelled correctly (no abbreviations are accepted for keywords). The following is a list of the acceptable keywords and the resulting %View screens generated. %View "ALL" All of the available BEACON commands. %View "KEYDEFS" User string definitions of the keys. %View "CONFIG" Serial port configuration commands. %View "VT100" Dec VT100 Setup mode commands. %View "KERMIT" KERMIT file transfer configuration commands. %View "USER" BEACON user preference commands. Note that the following BEACON local commands are not accessible through %View mode. %Help Disabled in %View mode because %Help and %View both "steal" the screen in a similar manner. %KeypadApplicationMode Disabled in %View mode because %View always sets (and restores) this parameter to distinguish between and . %View Disabled in %View mode to avoid recursive call. %VT100Mode This command allows allows the user to select emulation of either a DEC VT100 or a DEC VT52. This command accepts one boolean parameter of which "TRUE" selects VT100 emulation and "FALSE" selects VT52 emulation. Note that BEACON will switch emulation modes automatically if it receives an escape sequence which is valid only in the mode not currently being emulated. The syntax of this command is as follows: %VT100Mode %WaitUntil This command allows the user to suspend user processing until the specified time. This command is helpful if a user wants to start BEACON at night during off hours. The syntax of this command is as follows: %WaitUntil