MAI COMPANY CONFIDENTIAL FIELD INFORMATION BULLETIN SERVICE GROUP(S): MINI MFG: BASIC FOUR NACS TYPE(S): N029 MFG. MODEL(S): BOSS/IX BBVII CATEGORY: SOFTWARE DESC: O.S. & UTILITIES *** TABLE OF CONTENTS AS OF 09/18/92 *** FIB 00001.Release 7.1A Software Announcement..........................02/18/84 FIB 00002.Application Software Security...............................11/21/84 FIB 00003.Level 7.1A MAGNET and Local Area Network....................03/07/85 FIB 00004.Batch Communications Emulator...............................03/07/85 FIB 00005.Asynchronous File Transfer package..........................03/07/85 FIB 00006.BOSS/IX Release 7.1B Software Announcement..................05/15/85 FIB 00007.Error 0 (File System Error -62) on serial printers - release01/30/86 FIB 00008.MCS backups MUST be done in single user mode................03/26/86 FIB 00009.Error -2 and Error -62 during MCS backup/restore - release 704/07/86 FIB 00010.Release 7.2A Software Announcement..........................04/09/86 FIB 00011.COBAL 7.2A Software Announcement............................05/14/86 FIB 00012.Completion code of 77 (Internal FTF Error) - release 7.2A...05/28/86 FIB 00013.MMU errors running ORIGIN R13B on BOSS/IX 7.2A..............06/24/86 FIB 00014.Incorrect files restored using 1/2" MTS on release 7.2A.....07/08/86 FIB 00015.Task(s) drop out of BASIC mode while program is running - re07/08/86 FIB 00016.Error 18 Filesystem Error -48 on 7.2A when adding operator..07/21/86 FIB 00017.System crashs when using the 'BO' and 'EO' mnemonics on rel 09/18/86 FIB 00018.Information on sending dump tapes to BASIC FOUR [WPS # 246].09/25/86 FIB 00019.S10, ODT or other VDTs run slow on release 7.2..............11/13/86 FIB 00020.Error 31 in BASIC on release 7.2 due to variable tables.....11/26/86 FIB 00021.Error 47 while running BQR after file(s) transporting.......11/26/86 FIB 00022.BOSS/IX may return different error codes in BASIC than BOSS/12/11/86 FIB 00023.Release.7.2C Software Announcement..........................05/04/87 FIB 00024.7.2B Software Announcement..................................05/04/87 FIB 00025.COBAL 7.1B for MAI 2000 Series..............................05/04/87 FIB 00026.Rel 7.2C - EIT7217 has the wrong level file.................05/20/87 FIB 00027.2000/3000 Crash/Dump recovery and file repair instructions..05/20/87 FIB 00028.Filelists get corrupted on O.S. Releases 7.2................06/05/87 FIB 00029.Release 7.2D is the available/recommended for the 3000......06/05/87 FIB 00030.Vconf setup parameters for communications software usage....07/07/87 FIB 00031.Release 7.3A Software Announcement [ WPSS 153 ]............12/02/87 FIB 00032.Release of MAI 1800 and 7.2N O.S. [ WPS 408 ]...............12/29/87 FIB 00033.MAI 1800 Software Announcement [ WPSS 152 ].................12/29/87 FIB 00034.7.3A, Different O.S. tape for MAI 2000 and 3000 [ WPS 415 ].12/29/87 FIB 00035.Killed Print Job Still Prints [ WPS 417A ]..................10/24/88 FIB 00036.'EP' functionality change at level 7.3 [ WPS 418 ].........02/12/88 FIB 00037.Remove without key= on MAGNET at 7.3 fails [ WPS 420 ].....02/16/88 FIB 00038.form= option changes on 7.3 OS [ WPS 424 ].................02/16/88 FIB 00039.Release 7.4A Software Announcement [ WPSS 156 ].............03/29/88 FIB 00040.Announcing the 7.2P O.S. for system 1800 [ WPS 408 A ].....04/15/88 FIB 00041.Release Notification and Problems with 7.4A O.S. [ WPSF 44906/27/88 FIB 00042.Err -92 on continuation tape using tsave at level 7.3 [ WPSF04/20/88 FIB 00043.Basic error 65 at level 7.3 OS [ WPSF 455 ]................04/20/88 FIB 00044.Error 31s while upgrading or adding devices [ WPSF 453 ]...04/20/88 FIB 00045.Paradyne 1200/2400 Modems Supported on 7.4A TBC [ WPSF 449-08/16/88 FIB 00046.Rel. 7.2R Available for 1800 Systems - Known Problems [ WPSF12/27/88 FIB 00047.Ports above T9 won't work with auto dialer [ WPSF 449-13 ].10/24/88 FIB 00048.Err 20s in TBC Programs on 7.2R and below (1800s) [ WPSF 4910/24/88 FIB 00049.Release 7.4B Software Announcement [ WPSS 159 ]............12/19/88 FIB 00050.Extra.Files Created - TBC on 7.3A or 7.4A [ WPSF 484 ].....12/19/88 FIB 00051.Incorrect 'errlog' Command in BOSS/IX User Ref Manual [ WPS12/19/88 FIB 00052.ERR 47's using BCOM on 7.4A/B [ WPSF 449-14 ]..............12/20/88 SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------Table Of Contents Pg01 of 02 FIB 00053.Batch.Communications Status Message 483 on 7.4A/B [ WPSF 4412/20/88 FIB 00054.Escape Trapping notes [ WPSF 439 ].........................12/22/88 FIB 00055.Notes on Using the 'KL' Mnemonic [ WPSF 502 ]..............12/28/88 FIB 00056.Release 7.2R Software Announcement for 1800 System [ WPSS 102/08/89 FIB 00057.ERROR 17 on Multi-keyed files [ WPSF 514 ]..................02/08/89 FIB 00058.BASIC programs running slow [ WPSF 512 ]....................02/08/89 FIB 00059.Terminal/System Hangs 7.2 O.S. [ WPSF 435 ]................02/08/89 FIB 00060.Crash Code 21/Bus Errs on 7.3 O.S. [ WPSF 436 ]............02/08/89 FIB 00061.Installing COMM products on SPx systems [WPS 528]...........04/18/89 FIB 00062.PS 3.1A loop in /PS/MSDISPLAY [WPS 527].....................04/18/89 FIB 00063.Error 11's on Multi-Keyed files [ WPSF 522 ]...............04/18/89 FIB 00064.Printer VFU Set by Spooler Even when not Spooled [ WPSF 52404/18/89 FIB 00065.1800 System Error Log information...........................04/27/89 FIB 00066.TBC - ERR 11 Displaying Task Prefixes - 7.4A/B [ WPSF 449-107/27/89 FIB 00067.7.4A Additional Information [ WPSF 449-17 ]................07/27/89 FIB 00068.Err -95 Starting Communications on 7.4A/B [ WPSF 449-19 ]..07/27/89 FIB 00069.Known Dumps and Solutions [ WPSF 557R ]....................08/02/91 FIB 00070.7.4B Warnings & Cautions [ WPSF 573 & -1 ].................02/22/90 FIB 00071.7.5B Software Announcement [ WPSS 167 ]....................11/06/89 FIB 00072.7.5B Warnings and Cautions [ WPSF 597 ]....................02/22/90 FIB 00073.OS.Release 7.5B*17 is Available to Cure Terminal Hangs/Modem05/11/90 FIB 00074.Helpful Software Tools [ WPSF 597 A1 ].....................07/06/90 FIB 00075.Program to Run Unattended Backup on HCC Tape [ WPSF 625 ]..10/11/90 FIB 00076.Performance Problems Related to Serial Printer Use..........10/12/90 FIB 00077.tcompare Reports Erroneous Miscompare [ WPSF 638 ].........11/28/90 FIB 00078.Release 7.5B*20 Differences [ WPSF 167A ]..................01/02/91 FIB 00079.SPx 7.5B*22 Release [ WPSF 703 ]...........................04/16/91 FIB 00080.Power Failure Management (UPS Shutdown) [ WPSF 732 ]........09/17/91 FIB 00081.SPx Data File Integrity Check & File Repair Procedure.......01/02/92 FIB 00082."Invalid Date" message using starting & ending dates in util08/18/92 SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------Table Of Contents Pg02 of 02 FIB 00001 02/18/84 *** Release 7.1A Software Announcement *** 1.0 Introduction Level 7.1A of BOSS/IX~ is now available. This new release consists of the Level 7.1A Operating System and its related software products for the new MAI\ 2000 system. BOSS/IX~ is the first BASIC FOUR\ operating system software release that is not custom configured for each system. The operating system reconfigures with each system boot to adapt to the hardware that is physically connected to the system. Serial and parallel port parameters such as BAUD rate, parity, stop bits etc. are customized on site after the software is installed. BOSS/IX~ contains special security features that govern the use of BASIC FOUR's chargable optional products. A similar security feature is available to vendors and dealers to protect their software from unauthorized use. This security feature and information on operator security are oulined in this document. The MAI\ 2000 system character sets are different from those used on existing BASIC FOUR systems. The MAI\ 2000 system uses industry standard 7-bit (low order) ASCII. The 13XX, MAI\ Series 8000 system, S/10 and the S80 systems all use 8-bit (high order) ASCII. Conversion and transport utilities are available in the Intersystem Transport Product (EIT) to allow program and data interchange between BASIC FOUR systems having unlike character sets. This Software Announcement contains general information about the level 7.1A BOSS/IX~ operating system and its related software products. Also included are the following procedures: installation, upgrade, dump, shutdown, backup and restore. This document contains a section called "For your information", this section contains a list of known system problems and a way, if any, to work around them. TABLE OF CONTENTS 1.0 Introduction 2.0 The Level 7.1A BOSS/IX~ 2.1 Overview 2.2 Base System 2.2.1 Operating System (EOS) 2.2.2 Business BASIC (EBS) 2.2.3 System Utilities (EUT) 2.2.4 Winchester Bootable Diagnostics (WBD) 2.2.5 Hardware Diagnostics (DIA) 2.2.6 EXT (EXT) 2.3 Optional BOSS/IX~ Software Products 2.3.1 Intersystem Transport (EIT) 2.3.2 Informix~ Data Base Management (EDB) 2.3.3 MAGNET (LAN) 2.3.4 27XX/37XX Batch Emulation (EBC) 2.3.5 International Utilities (INT) 3.0 System Start-up and Shutdown 3.1 System Start-up 3.1.1 From Powered Off Condition 3.1.2 From Powered On Condition 3.1.3 Alternate Load From Powered Off Condition 3.1.4 Alternate Load From Powered On Condition SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg001 3.2 How To Start-up Multi-User Mode 3.3 System Shutdown 3.3.1 From Multi-User Mode to Single User Mode 3.3.2 From Single-User Mode to Complete System Shutdown 4.0 Installation and Upgrade 4.1 System Installation 4.2 System Upgrade 5.0 Back-up and Restore 5.1 Via MCS 5.2 VIa Floppy Diskette 5.3 Filesystem to Filesystem 6.0 Customization 6.1 Port Configuration 6.2 System Configuration 7.0 Security 7.1 System Security 7.2 File Security 7.3 Application Security 8.0 Disk Organization 8.1 The Partition 8.2 The Filesystem 9.0 Memory Usage 9.1 Calculating Your System's Memory Requirements 9.1.1 Example 9.2 Exact Method for Calculating BOSS/IX~ Table Space Memory Requirements 10.0 For Your Information 11.0 Helpfull Hints 12.0 Enhancements/Corrections from 7.1A*18 (pre-release) to 7.1A*34 (released version) 13.0 Dump Procedures 14.0 Available Documentation 15.0 Lowest Acceptable Revision Levels (LARL) 2.0 The Level 7.1A BOSS/IX~ 2.1 Overview The MAI\ 2000 BOSS/IX~ is unique in the history of BASIC FOUR\ Operating Systems. BOSS/IX~ is made up of a new powerfull multi-user, UNIX~ - like operating sytem that simultaneously supports both the BASIC FOUR \ Business BASIC environment and the UNIX~ environment. BOSS/IX~ is divided into groupings of programs and files that support different aspects of the total software system. These groupings are known as products. The following is a list of the currently released 7.1A BOSS/IX products and other products available for the MAI\ 2000: MAI\ 2000 Operating system (EOS) MAI\ 2000 Business BASIC (EBS) MAI\ 2000 Utility Set (EUT) MAI\ 2000 Intersystem Transport (EIT)* MAI\ 2000 Customer Diagnostics (DIA) MAI\ 2000 Informix Data Base Management (EDB)* MAI\ 2000 MAGNET (LAN)* MAI\ 2000 27XX/37XX Batch Emulation (EBC)* MAI\ 2000 International Utilities (INT)* MAI\ 2000 Winchester Bootable Diagnostics (WBD)* MAI\ 2000 EXT (EXT) * These products are Optional and may be chargable. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg002 Each product is released and installed independently, with the exception of the base system. The base system consists of the EOS, EBS, EUT, WBD and DIA products. All, but the DIA product, are dependent on the EOS, EBS and EUT products of the base system. The products are available on and can be installed from either floppy diskettes or magnetic cartridge streamer (MCS) tapes. The mediacontains all the files and programs necessary for the execution of the product. It also contains a program that works in conjunction with the installation or upgrade procedure to insure that the product is put on the fixed disk correctly and with the proper security. 2.2 Base System The base system is the nucleus of the BOSS/IX~ software. It consists of a 2 MB image copy of the boot partition, EOS, EBS, EUT, WBD, EXT and the stand alone diagnostic product DIA. If your medium for installation is tape, the boot partition image, the EOS, EUT and EBS will be on one tape, the WBD will be on another tape and the DIA will be on a third tape. Even though the boot partition is separated from the EOS product for both installation and distribution it is still an integral part of the operating system. The '/sys/unos' file, the operating system, resides on and is loaded into memory from the boot partition. Another important system file, the '/etc/conf' file (the system configuration file) also resides on and is loaded into memory from the boot partition. 2.2.1 MAI\ 2000 Operating System EOS The EOS product includes: - The operating system which governs process management, resource management, I/O control and the file sytem. - A powerfull set of system commands, each command contains a '-help' option to display the commands syntax. Most commands are located in the '/bin' directory and can be viewed by typing "ls -l /bin |p" at the command mode prompt 'name>', or from BASIC by using '!' before the command at the BASIC prompt '>'. - 'ved' a text editor used from the command intreperter to create and edit string files. - Macro command definition. - I/O redirection to a device or a file. - Business File System which supports both UNIX\ type files ( string, device, eventcounts and directory ) and the Business BASIC file types (direct, sort, indexed, serial and program ). - Support of multiple languages concurrently; i.e. one terminal process can be running a BASIC program and another can be executing utility programs written in the 'C' language. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg003 - Spooler commands, lpr, lpq, lpmaint and lpstat. These commands together with the '/etc/printers', '/etc/class', '/etc/forms', '/etc/ports' and the printer device files allow you to submit a print job, print it and maintain the print queue. EUT contains a spooling utility that is menu driven for ease of use. Other product dependencies; none. Disk space requirements; 2.66 MB on the root partition. 2 MB on the boot partition and 2 MB swapper for a total of 6.66 MB. 2.2.2 MAI\ 2000 Business BASIC EBS The Level 7.1A BASIC is almost identical to 13XX level 4 BASIC. This allows 13XX application programs to be transported to the MAI\ 2000 with very few changes. MAI\ 2000 BASIC is a subset of the MAI\ 8000 BASIC so that MAI\ 2000 applications will also transport easily to the MAI\ 8000 systems. 7.1A BASIC supports ghost tasks, called programs, public programming and also the execution of 'C' language programs. The following lists summarize the changes made to level 4 basic in adapting it to the MAI\ 2000 hardware and software architectures. NOT SUPPORTED NEW CHANGED ADD ! COMMAND EXECUTE CPL ADDC CLASS= DIRECT ADDL ENCRYPT DISABLE ADDS ERROR ENABLE BLK= LIB \ need C FID BNK= LIB=/ FILE BSZ LVL INDEXED GET OPTS= LOCK HSA PFX LST PUT PNM PREFIX RESERVE RENAME PROGRAM RTY= PUB SEQ= STRING SERIAL SORTSTEP UNT SETDAY SSZ VMERGE SORT TRK= START VOL= TCB TSK ENHANCED MISCELLANEOUS CHANGES EDIT 20 character file names 52 functions Low order ASCII (seven-bit) File allocation parameters Disks are not only logical No filesets (different directory structure) Open channels 0-63 Accepts BASIC statements upper or lower case SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg004 Strings and file/directory names are case sensitive Allowable task names changed somewhat Single line BASIC editor Product dependenices; EOS and EUT. Disk requirements are approximately .8 MB on the root partition. 2.2.3 MAI\ 2000 Utilities EUT EUT can be divided into two sections; the menu system and the utility program set. The menu system consists of a set of predefined menus and a menu edit program '/util/menuedit'. The predefined menus are designed around the current utility set. The '/util/menuedit' program allows you to modify the menu system in order to adapt to the needs of the user. Most of the utility set is written in the "C" language. Most utilities that deal with BASIC programs are written is BASIC. All the utility programs, the menus and the menuedit program reside in the '/util' directory. Each utility or menu can be executed from either the command interpreter or from the BASIC console mode. From BASIC the program names must be preceded by a "!". Product dependencies; EOS and EBS. Disk requirements are approximately 3.6 MB on the root partition. 2.2.4 MAI\ 2000 Winchester Bootable Diagnostics WBD WBD when installed resides on the both the boot partition and a copy on the root partition in the '/sys' directory. The following programs that make-up WBD are based on the MAI\ 2000 DIA product. '/sys/floppy' consisting of: EXEC - a co-resident diagnostic executive. FLOPPY - the set of floppy logic tests '/sys/mcs' consisting of: EXEC - co-resident diagnostic executive. MCS - the set of MCS logic tests. These logic tests are directly bootable to a standalone environment from the BOSS/IX~ loader. To load these tests do an alternate load (see section 3.0). Enter "wd0" and a at the 'boot device:' prompt, then enter "/sys/mcs" or "/sys/floppy" at the 'system file:' prompt. Refer to the diagnostics manual for instructions on the operation of these diagnostics. Product dependencies; EOS. Disk requirements are approximately .13 MB on the boot SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg005 partition and .13 MB on the root partition. 2.2.5 MAI\ 2000 Hardware Diagnostic DIA DIA is a stand alone bootable diagnostic package that contains a set of logic and hardware tests to determine the condition of the MAI\ 2000 system hardware. To load these tests do an alternate load (see section 3.0). Enter either "cs" for Cartridge Streamer or "fd0" for floppy drive 0 and a (DIA is available on either mcs or floppy diskette) at the 'boot device' prompt. Then enter just at the 'system file:' prompt. Refer to the diagnostics manual for instructions on the operation of the diagnostics. Product dependencies; none. Disk requirements; none. 2.2.6 MAI\ 2000 EXT EXT The EXT product currently contains one 'C' program called 'setkeys'. This program was designed to be executed before running 'ved' the system text editor. Setkeys prompts the user for the type of terminal (EVDT's and EDT's only), then loads the functions keys with the 'ved' control key sequences. 'setkeys' is in the '/bin' directory. Product dependencies; EOS. Disk space requirements are approximately 37 blocks ( 512 byte blocks) on the root partition. 2.3 Optional BOSS/IX~ Products 2.3.1 Intersystem Transport EIT The intersystem transport package contains the tools that allow data files and BASIC programs to be transfered between MAI 2000 and 13XX or MAI 8000 systems. It also includes tools that translate the syntax of BASIC programs and convert ASCII data. The transfer medium can be MCS cartridge, asynchronus communications, or synchronous communications. The EIT programs can be accessed from the utilities menu system, under 9. Intersystem transfer, under Utilities. Product dependencies; EOS, EUT and EBS. Disk space requirements are approximately .65 MB on the root partition. 2.3.2 Informix~ Data Base Management EDB Informix~ is a powerful, complete relational data base management system. It includes a database manager, screen and report generator, and a query language. File layouts can be created using the text editor 'ved' (ved is contained in the EOS product). Informix can also interface to existing Business BASIC files provided each record has the same number of fields. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg006 Product dependencies; EOS, EUT and EBS. Disk space requirements are approximately 1.34 MB on the root partition. 2.3.3 MAGNET LAN MAGNET 2000 is the system local area network. LAN provides a means of connecting multiple MAI\ 2000's. All information stored on any disk on the network is accessible by any user on the systems. This eliminates the need for storing redundant data on multiple systems. LAN will support up to 63 MAI\ 2000's cabled together. Standard applications may need minor modifications to accommodate MAI\ 2000's networked using LAN. These modifications to the BASIC application code will include changes to the "OPEN" statements to include the fully qualified pathname of files existing on 'other' systems on the network. Product dependencies; EOS, EBS and EUT. Disk space requirements are approximately; .78 MB on the root partition. 2.3.4 27XX/37XX Batch Emulation EBC The emulator utilities on the MAI\ 2000 system are written in 'C' as opposed to BASIC as on the other BASIC FOUR 13XX, 8000, S80 and S/10 systems. With only a few minor changes the user interface is identical to the 27XX/37XX Batch Emulation utility found on the other BASIC FOUR systems. A user who is familiar with the package on these systems should easily adapt to the emulator utilities on the MAI\ 2000 system. Product dependencies; EOS, EBS and EUT. Disk space requirements are approximately .9 MB on the root partition. 2.3.5 International Utilities INT INT is used to translate all the MAI\ 2000 system utility messages and menu screens into non-English languages. The INT product consists of the following programs: medit - message editor utility. msgcompare - message compare and translate utility. The screens and messages of the system utility set are stored in the utility text and index files: '/util/uthelp.ind', '/util/uthelp.txt', '/util/utmsg.ind' and '/util/utmsg.txt'. 'medit' allows the contents of these files to be changed, added, copied, deleted or verified. 'medit' uses the system editor 'ved' ('ved' is part of EOS). The message compare program 'msgcompare' performs a SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg007 file update and translation of the above utility files. The message compare program is menu driven and prompts the user for all the required information. Product dependencies; EOS and EUT. Disk space requirements are approximately .2 MB on the root partition. 3.0 System Start Up and Shutdown 3.1 System Start-up System start-up is dependant on the set of parameters in the system configuration file that is loaded into memory at boot time. The system will normally use a default system configuration file '/etc/conf' off the boot partition or the system file can be specified at boot time during an alternate load. The following two sections 3.1.1 and 3.1.2, use the standard configuration file that comes with the system software. This configuration file is set up to root to the root partition in a non-secure, single user mode. See section 6.2 on how to customize the system configuration file and change any of the available parameters. 3.1.1 From A Powered Off Condition Step 1. Determine which terminal is the console terminal, all messages during system start-up are displayed on the system console. The system console is normally set up to be either the first port off the CMB (Central Microprocessor Board) or if you have any four ways the first port off the first 4-way. If you don't know which one is the system console, turn both terminals on and which ever displays the self test is the console terminal. (See section 10.0, under Warnings, on system consoles) At the terminal set the system console to 9600 BAUD, x-on/x-off flow control. Step 2. Turn the power on at the back of the CCA (Central Cabinet Assembly). The console terminal will begin to display the system hardware self test. Step 3. After the self test successfully completes, the terminal will display: "Booting from wd0". At this time the operating system file '/sys/unos' and the system configuration file '/etc/conf' are being loaded into memory to begin executing and building the operating system in memory. The operating system then creates process number one '/etc/start', from this point on the '/etc/start' programs monitors the process activity on the system. Step 4. Once step 3 is complete, '/etc/start' displays the BOSS/IX~ system proprietary message. After the proprietary message, '/etc/start' displays the system date and time, you are then asked to enter SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg008 the current date and time: "09:58:35 AM, 08/19/84 Update clock hhmmssxx mmddyy" The cursor will be on the first h after the word clock. Enter a two digit hour, then a two digit minute, then a two digit second, and either an "am" or "pm". Continue typing with a space, then a two digit month, a two digit day, and a two digit year followed by a . Step 5. Once the date is accepted, '/etc/start' will display the entered time and date, the calculated day of the week, and "" message. If a minor error occurred during start-up the error messages are reported in to the '/etc/sys.log' file, '/etc/start' checks this file and if it contains data the following message is displayed; An error has occurred during system startup. File '/etc/sys.log' contains a description of the errors. Press the 'ESC' key to continue. . . If this message occurs simply press the key and the 'ADMIN>' prompt will then be displayed. Once at the 'ADMIN>' prompt, you can print the contents of the '/ets/sys.log' file. If no errors occurred the 'ADMIN>' prompt will display immediately. If a severe error occurs the system will abort the boot process and drop into the system debugger (debug mode). If the '/etc/conf' file was set to "secure mode" a 'Password:' prompt will be displayed before the 'ADMIN>' prompt. If this prompt is diplayed, you must enter the system administrator password followed by a . 3.1.2 From A Powered On Condition Step 1. When the system is properly shutdown from single user mode, the screen will be displaying the reboot prompt: Press 'RETURN' key to reboot (' C'=alt-load,' S'=self-test): At this prompt you can do one of five things; 1. Press to do a normal system load, 2. Press ' C' (a key plus "C") to do an alternate load, 3. Press ' S' (a key plus "S") to do the system self test, which is then followed by a normal load, 4. Press ' Z' (a key plus "Z") to load the kernel debugger. 5. Turn the power off at the CCA. NOTE: This is one of only three prompts where it's appropriate to turn off the power to the CCA. The other prompts SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg009 are 'Boot device:' and 'System file:'. To do a normal load press . The screen will display "Booting from wd0". At this time the operating system file '/sys/unos' and the system configuration file '/etc/conf' are being loaded into memory to begin executing and building the operating system in memory. The operating system then creates process number one '/etc/start', from this point on the '/etc/start' programs monitors the process activity on the system. Step 2. Once step 1 is complete, '/etc/start' displays the BOSS/IX~ system proprietary message. After the proprietary message, '/etc/start' displays the system date and time, you are then asked to enter the current date and time: "09:58:35 AM, 08/19/84 Update clock hhmmssxx mmddyy" The cursor will be on the first h after the word clock. Enter a two digit hour, then a two digit minute, then a two digit second, and either an "am" or "pm". Continue typing with a space, then a two digit month, a two digit day, and a two digit year followed by a . Step 3. Once the date is accepted, '/etc/start' will display the entered time and date, the calculated day of the week, and the "" message. If a minor error occurred during start-up the error messages are reported in the '/etc/sys.log' file, '/etc/start' checks this file and if it contains data the following message is displayed; An error has occurred during system startup File '/etc/sys.log' contains a description of the errors Press the 'ESC' key to continue. . . If this message occurs simply press the key and the 'ADMIN>' prompt will then be displayed. Once at the 'ADMIN>' prompt, you can print the contains of the '/ets/sys.log' file. If no errors occurred the 'ADMIN>' prompt will display immediately. If a severe error occurs the system will abort the boot process and drop into the system debugger (debug mode). If the '/etc/conf' file was set to "secure mode" a 'Password:' prompt will be displayed before the ADMIN>' prompt. If this prompt is diplayed, you must enter the system administrator password followed by a . 3.1.3 Alternate Load From a Powered off Condition Step 1. Determine which terminal is the console SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg010 terminal, all messages during system start-up are displayed on the system console. The system console is normally set up to be either the first port off the CMB (Central Microprocessor Board) or if you have any four ways the first port off the first 4-way. If you don't know which one is the system console, turn both terminals on and which ever displays the self test is the console terminal. At the terminal set the system console to 9600 BAUD, x-on/x-off flow control. Step 2. Turn the power on at the back of the CCA (Central Cabinet Assembly). The console terminal will begin to display the system hardware self test. During the memory portion of the self test the system will seem to stop, at this pause you will have time to press a ' C' ( key plus "C" ). Step 3. Once you have pressed the ' C' the system will complete the memory test then display: Memory [ size=xxxx kbytes] pass c The system will continue with the remainder of the self test. Step 4. After the self test a 'Boot device;' prompt is displayed. At this point you can enter the desired device then a . The current possiblities are: 'fd0', 'cs', 'wd0' or 'wd1'. A key by its self will default to 'wd0'. Step 5. Next is the 'System file:' prompt. The System file has two parts. If one part is omitted the system default is used. The part one of the system file is a loadable operating system file, '/sys/unos' and '/sys/mcs' are examples of loadable operating system files. Part two is a system configuration file, '/etc/conf' and '/etc/boot.conf' are examples of system configuration files. These two parts when entered together are separated by a comma ",". If the first part is entered by its self as in the case of the WBD files '/sys/mcs' no comma is needed and the system will default to the '/etc/conf' file. If the second part is entered by its self, as in the case where you want to root to the boot partition, the comma must precede the file name, example: ',/etc/boot.conf'. In the second case the system will default to the '/sys/unos' operating system file. Step 6. After the information is entered, the terminal will display: "Booting from xxx (requested boot device). At this time the operating system file 'xxxxxxxx' (the requested operating system) and the system requested configuration file 'xxxxxxxxx' are being loaded into memory to begin executing and building the operating system in memory. 3.1.4 Alternate Load From Powered On Condition SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg011 Step 1. When the system is properly shutdown from single user mode, the screen will be displaying the reboot prompt: Press 'RETURN' key to reboot (' C'=alt-load,' S'=self-test): At this prompt you can do one of five things; 1. Press to do a normal system load, 2. Press ' C' (a key plus "C") to do an alternate load, 3. Press ' S' (a key plus "S") to do the system self test, which is then followed by a normal load, 4. Press ' Z' (a key plus "Z") to load the kernel debugger. 5. Turn the power off at the CCA. NOTE: This is one of only three prompts where it's appropriate to turn off the power to the CCA. The other prompts are 'Boot device:' and 'System file:'. Step 2. Press ' C' for alternate load. A 'Boot device;' prompt is displayed. At this point you can enter the desired device then a . The current possiblities are: 'fd0', 'cs', 'wd0' or 'wd1'. A key by its self will default to 'wd0'. Step 3. Next is the 'System file:' prompt. The System file has two parts. If one part is omitted the system default is used. The part one of the system file is a loadable operating system file, '/sys/unos' and '/sys/mcs' are examples of loadable operating system files. Part two is a system configuration file, '/etc/conf' and '/etc/boot.conf' are examples of system configuration files. These two parts when entered together are separated by a comma ",". If the first part is entered by its self as in the case of the WBD files '/sys/mcs' no comma is needed and the system will default to the '/etc/conf' file. If the second part is entered by its self, as in the case where you want to root to the boot partition, the comma must precede the file name, example: ',/etc/boot.conf'. In the second case the system will default to the '/sys/unos' operating system file. Step 4. After the information is entered, the terminal will display: "Booting from xxx (requested boot device). At this time the operating system file 'xxxxxxxx' (the requested operating system) and the system requested configuration file 'xxxxxxxxx' are being loaded into memory to begin executing and building the operating system in memory. 3.2 How to Start-Up Multi-User Mode When you have started the system and entered single user mode, as described above, only the system console, '/dev/tty0' is active and ready for use. To activite SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg012 additional terminals, spooling, system error logger and the LAN remote service manager '/lan/lan rsm' you must enter multi-user mode. Additional terminals and printers must be connected and configured via '/util/configure' utility prior to entering multi-user mode. To enter multi-user mode, type ' D' ('CTRL' plus "D") at the 'ADMIN>' prompt. The system displays, 'single, multi, or shutdown?'. At this point you can do one of three things: 1. Return to single, 2. Go into multi, or 3. Do a complete shutdown. To go into multi-user mode type "multi", then . The '/etc/start' program now begins the multi-user mode start up. '/etc/start' starts all terminals configured, the system spooler, the error logger, clears out the '/tmp' file, the '/lan/lan rsm' program, the '/etc/sinit' file, and the operator 'init' file. The system then begins to display the startup messages indicating its progress. Each terminal is then started with the proper program as indicated in the '/etc/terminals' file. Terminals started with the '/bin/login' program will display the following: The system console displays the MAI\ 2000 message and the 'Account name:' prompt. All other terminals display the MAI\ 2000 message and the following: MAI\ 2000 (Terminal /dev/ttyN) - Press 'CTRL'+'C' or 'ESCAPE' The system is now in multi-user mode. 3.3 System Shutdown It is VERY IMPORTANT that the system be shutdown properly before the power to the CCA is turned off. Failure to follow these procedures may result in damage to the filesystem, and may cause loss of data. The system can only be shutdown by the system administrator. Shutdown can be initiated from any terminal, if the system is in multi-user mode. In single user mode, only the system console is active. A proper system shutdown proceeds in two steps. First, the system is shut down from multi-user mode to single-user mode. This needs to be done only if the system is in multi-user mode at the time you begin to shut down the system. Second, the system is shut down from single user mode to the fully shutdown condition. Only from the fully shut down condition can the power be safely turned off. 3.3.1 Shutdown From Multi-User Mode to Single User Mode To shut down the system from multi-user mode, you must be logged on as the system adminisrator. When SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg013 the system adminisrator prompt 'ADMIN>'is displayed, Type "shutdown x message", and then press , where "x" is the the number of minutes until the shutdown occurs and "message" is a message explaining the reason for the shutdown. The message is optional. For example, to allow 2 minutes before shutting down for the night, type "shutdown 2 For the night", then . Every terminal screen then displays: SYSTEM SHUTTING DOWN IN 2 MINUTES For the night This message is repeated every minute for the remaining number of minutes until shutdown. When the specified number of minutes has expired, the screen displays: LAST WARNING - SYSTEM SHUTTING DOWN IN 15 SECONDS For the night Under this message, the number of seconds is counted down. When the time has expired, the screen displays: SYSTEM SHUTTING DOWN NOW, GOODBYE The system is now back in single user mode. All terminals other than the system console are inactive. The system console remains logged on to the system administrator and is fully functional. NOTE: If the shutdown must be interrupted, you can terminate the process any time up to the last second. To interrupt the shutdown process, press ' C' ('CTRL' plus "C"), at the terminal initiating the process. This terminates the shutdown process, and a message indicating that the shutdown has been aborted is diplayed on all terminals. Multi-user activity can then continue. 3.3.2 Shutdown From Single User Mode to Complete Shutdown When the system is in single user mode, you may shut down the system to its fully shutdown state. To finish the shutdown procedure, at the 'ADMIN>' prompt type ' D' ('CTRL' plus "D"). The system then prompts: 'single, multi, or shutdown?'. AT this point you can do one of three things: 1. Return to single, 2. Go into multi, or 3. Do a complete shutdown. To do the complete shutdown type "shutdown", then . The system then displays the re-boot prompt, and shuts down: Press 'RETURN' key to reboot (' C'=alt-load, ' S'=self-test): The system is now shut down and completely idle. It is now appropriate to turn off the power to the CCA. 4.0 Installation and Upgrade SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg014 4.1 Installation The following steps outline the MAI\ 2000 BOSS/IX~ installation procedures for tape and floppy diskette. Step 1. First step is to install the boot partition. Insert the base tape into the MCS drive. Or, if you are doing floppy installation insert the installation floppy into the floppy drive fd0. Do an alternate load (see section 3 for complete instructions on alternate loads). At the 'boot device:' prompt type "cs" for MCS or "fd0" for floppy diskette, then press , press again at 'System file:' prompt. Step 2. Screen displays loading messages, then the Install Utility Menu. Select option 'A', then . Option 'A' redefines all the wd0 partitions and then copies a new boot partition to disk. After copy is complete, you are instructed to reload. Special note for floppy diskette installations, Make sure your BOOT floppy diskettes are inserted in the correct sequence according to the BOOT number. After one floppy diskette is complete make sure you change floppy diskettes before responding to the prompt on the screen. Step 3. After the boot partition, the EOS product must be installed. Reloading the system at this time automatically reloads and roots to the boot partition. Enter the correct date, the screen will then display the 'ADMIN>' prompt. At the 'ADMIN>' prompt, type "osinstall /dev/cs" for tape and "osinstall /dev/fd0" for floppy diskette. This process uses the parameters in the Super Block to define the root filesystem, then copies the EOS product to the root partition on disk. After the EOS product is installed you are instructed to reload again. Step 4. Reloading of the system at this time automatically reloads and roots to the root partition. Enter either the current date, or a , if the date is correct. At the 'ADMIN>' prompt, type "install /dev/cs EBS EUT", for MCS or "install /dev/fd0 EUT", for floppy diskette. List the products in the order they appear on the tape. If you skip one, go back and retype, do not add it to the end of your list. When working with tapes all products listed on the base tape can be installed with one command line. When working with floppies you must install one product at a time in the following order: EUT, EBS, WBD then the optional products in any order. If you receive more than the base system, each additional product will be on a separate tape or series of floppies. Each additional tape will need a new command line entered. Example: The LAN product is distributed on a separate media. To install it type "install /dev/cs LAN" at the 'ADMIN>' prompt. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg015 Products that are chargeable and not part of the base system will have key codes that you must enter during or after (using '/bin/install key') installation before you can use that product. If the key certificate did not come with the media, contact your customer or service representative in your area to instruct you in where to call for this key code. Step 5. After you have copied all your products to disk your system is ready for use. 4.2 Upgrading The following steps describe the MAI\ 2000 BOSS/IX~ upgrade procedures for MCS tape and floppy diskette. NOTE: Always have a recent back-up before doing any upgrades. Step 1. Using the mcssave command or the floppy diskette save utility, backup the correct configuration and user files of your system. Shutdown system to alternate load prompt. NOTE: If you are upgrading from a pre-release *27 or before it is recommended that you completely replace the boot partition. If you do not want to restore the boot go ahead to step 2. This is done by doing an alternate load, at the reboot prompt: Press key to reboot (' C'=alt load, ' S'=self-test): press the ' C'. At the 'Boot device:' prompt type "cs" for MCS or "fd0" for floppy diskette. At the 'System file:' prompt, press . The system will boot from the tape or floppy and display the loading messages then the Install Menu screen. At this menu select option "B". Option 'B' will only copy the an image copy of the boot partition from tape to disk. This process will insure that your system has all the up to date and proper, MACROs and system files on the boot partition. Once the boot has been copied to disk the '/etc/conf' (system configuration file) will be set to the minimum configuration ( two users and one printer ). If your system is larger than that you will need to modify the '/etc/conf' file. See section 6.0 for instructions. After you have copied the boot partition to disk continue on with step 2. Step 2. Do an alternate load, at 'Boot device:' prompt, enter "wd0", then a . At the 'System File:' prompt, enter ",/etc/boot.conf". Step 3. The above alternate load will automatically reload and root the operating system to the boot partition. Enter the correct date or if the date is correct. Insert SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg016 the base system tape containing EOS, EUT and EBS or the floppy diskette EOS #1. At the 'ADMIN>' prompt type "osupdate cs" for tape and "osupdate rfd0" for floppy diskette. For floppy diskette upgrades the screen will prompt you when to insert the next diskettes. Step 4. After the procedure is complete you have the option of restoring the default system configuration files to the upgraded root then to the boot partition. This is done by typing "/sys/installetc". This procedure allows the operator to select which system files he/she needs to restore. Please note if this is done all system files will be new, the operator file, '/etc/password', '/etc/sinit', etc. All terminals and printers must be redefined, and the '/etc/conf' file will be set to minimum system size (2 terminals, 1 printer). Step 5. Next shutdown system and do a normal reload to the root partition. Enter the correct date or press if the date is correct. If you are upgrading from MCS, at the 'ADMIN>' prompt type "install cs EUT EBS", press . System will automatically install both EUT and EBS. Once EUT and EBS is installed you can then install the rest of the products by typing "install cs XXX" where XXX is the different product codes. If you are upgrading from floppy diskette, insert the first floppy of the EUT set. At the 'ADMIN>' prompt type "install fd0 EUT", for floppy diskette. The system will prompt for additional floppy diskette. Once, EUT is complete use the same routine to install EBS and any other products. Your system is ready for use. 5.0 Backup and Restore The Series MAI\ 2000 System provides three types of backups and restores. The method used is dependent on the hardware configuration. A backup or restore can be performed using a magnetic cartridge streamer (MCS), floppy diskette or from filesystem to filesystem. 5.1 Via MCS There two methods that can be used to backup files via MCS and one way to restore files. The first is the two BOSS/IX~ commands '/bin/mcssave' and '/bin/mcsrestore'. Both commands are included in the EOS software product. Single or multiple files can be saved or restored using the commands. If multiple files are desired a filelist can be used. A filelist is a file containing the full directory pathnames of files that are to be saved or restored separated by a carriage return. A filelist can be created by redirecting the output of the 'ls' command or by using either the command mode text editor (VED) or the system utility 'Filelist maintenance'. At the 'ADMIN>' prompt of the command mode, type "mcssave -h". This will give you the syntax and options of the '/bin/mcssave' SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg017 command. After execution of the '/bin/mcssave' it is recommended that a '/bin/mcscompare' is executed. This will verify that the information on the tape is the same as on disk. The second method is by using the BASIC program '/sys/mcsbackup' (part of EOS) . This program is menu driven and contains the same options as the command '/bin/mcssave'. 5.2 Via Floppy Diskette Backups and restore may be performed by one of two methods when floppy diskettes are used. The first is using the commands, 'mount' and 'copy', included in the software product EOS. The floppy diskette must be mounted onto a directory system contained on the disk and then files or an entire directory can be copied to the floppy diskette. The second method is to use the backup and restore utility. This utility can be accessed directly by executing either '/util/dsave' or '/util/drestore' from the command interperter. Or, by executing the 'menu' from the command interperter. Once in the menu system select option 1. Utility programs. From the Main Utility Menu select option 5. Save & Restore. This will bring you to the Diskette Save & Restore Utilities Menu. Here you can select 1. Save, 2. Restore or 3. Report. Refer to the Systems users guide for more information on both diskette Save & Restore. 5.3 Filesystem to Filesystem If a system has two hard disks configured, backups and restores may be performed from one to the other. To perform a backup or restore disk to disk requires that the secondary drive be mounted on the primary drive using the '/bin/mount' command. Then using the '/bin/copy' to transfer the files from one to the other. An entire directory structure or a individual file can be specified. 6.0 Customization Level 7.1A BOSS/IX~ is unique to MAI BASIC FOUR, INC. There is no BOSS Sheet, this means that all software is standard and the customization is done at the customer site. The BOSS/IX~ Operating System Software, when it comes from MAI BASIC FOUR, INC., does not have an embedded System Serial Number, pre-definded peripherals or pre-set operating system options. All customization including hardware is done at the customer site. The following sections outline the customization that can be done at the customer site. For details please refer to the systems users guide. 6.1 Port Configurations There are three steps to the MAI\ 2000 port configuration: 1. Hardware connection and setup, 2. Software-configure, and 3. Optional mnemonic or translation table definition. Step 1. Hardware connection and setup is dependent on the needs of the customer. After the service representative has SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg018 connected the desired equipment, it is important to acquire the following information from the service representative who connect the equipment; a. Port Number - possible 0-14 b. Device type - the type of device that is connected to each port. Available MAI BASIC FOUR, INC devices: Terminals - vdt7270, edt, evdt and for non- BASIC FOUR terminals there is an "other" type Printers - (serial) lqp, dmp, tp80, Tritel and Whisper. (parallel) dmp, lpm. NOTE: parallel printers can only be on port 2. c. BAUD rate for each terminal, input and output. Step 2. The configure utility '/util/configure' will allow you to software-configure the ports on the system to match the connected hardware. '/util/configure' will allow you to add and remove devices, modify the characteristics of devices already connected, move devices to different ports and report the current configuration of the system. All connected devices, except the system console, must be software configured. The '/util/configure' gets information about the system console from the Non Volatile Random Access Memory (NVRAM) on the CMB. This information can only be changed via the system debugger utility 'config'. (See section 10.0 For Your Information, on how to change the system console information in the NVRAM) '/util/configure' will modify the following system files in order to perform software configurations: '/etc/ports' - contains infromation about each port configured for a device; '/etc/terminals - contains information on each terminal configured on the system; '/etc/printers' - contains information on each printer configured on the system; '/dev' - '/util/configure' will add a device file to this directory for each device configured on the system. '/etc/defaults' - when a printer is configured this file is modified to specify whether there will be spooling for any printer. '/util/configure' should be run in single user mode. '/util/configure' is menu driven and will prompt you for all input. 3. Optional mnemonic and translation tables - If you are connecting non-BASIC FOUR equipment, that supports a different set of mnemonics or requires a translation table. You may need to create a 'ttymntbl' or 'ttyxlate' for each device. See section 11.2 under Helpfull Hints for a brief procedure on the set up of these tables, more information can be found in the systems users guide. 6.2 System Configuration The system hardware configuration is determined at system boot time. Each accessable piece of equipment on the system has an associated '/dev' file. All '/dev' files are either SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg019 defined by the '/util/configure' utility or are part of the EOS product. Besides the hardware, the operating system can be customized for the needs of the each individual site. This is done by the use of the '/bin/vconf' command. '/bin/vconf' is the command that modifies the '/etc/conf' files, the system configuration files. These files tell the operating system at load time how the system is software-configured. The following is a list of the possible software configurable features of the operating system: root=MMmm - This option indicates which filesystem to root to at boot/load time. 'MMmm' is the major and minor numbers for the various partitions/devices on the system. (See Helpfull Hints section 11.20 for a list of major numbers.) System=string - The string contains the information that will be printed at load time specifing the system name. -silent - The load process will execute without sending messages of its progress to the system console. -verbose - The load process will print progress messages to the system console. Opposite of -silent. -debug - With this option set, the system will go into debug if a crash occurs. -single - After a reboot the system will be in single user mode. -multi - After a reboot the system will go into multi user mode automatically bypassing single user mode. -oride - With this option set the system will load to a filesystem that was left mounted (override the mount file). -noride - Opposite of -oride. -secure - After a reboot the system will request a password in order to have access to the system, for single or multi user modes. -nonsecure - After a reboot to single user mode the system will not request a password. -dump - After a system crash the system will perform a dump of memory to the swapper area on the fixed disk. -nodump - After a system crash the system will not perform a dump of memory. printer=# - This number indecates the maximum number of printers on the system. procs=# - This value indicates the maximum number of processes, at one time, on the system. You may need to increase this value if you frequently run out of processes, have many terminals, use LAN or ghost tasks. tseg=# - This value specifies the maximum number of shared text segments (program code segments ) on the system. BASIC SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg020 is a shared text segment, one copy of BASIC is used for all tasks using BASIC. sockets=# - You can set the number of well known LAN sockets on your system. dsockets=# - You can set the number of dynamic LAN sockets on your system. lanbuffers=# - You can set the number of LAN buffers on your system. clist=# - This option sets the number character list buffers for each serial port. The clists are used to buffer the input of characters from a serial port (such as keyboard input from a terminal). mfsys=# - This option sets the maximum number of mounted filesystems. lus=# - This option sets the maximum number of logical units on your system. opens=# - This option sets the maximum number of opens on the system. eventcalls=# - This option sets the maximum number of event calls that can be activiated at a time. Each one of the above options uses memory space. If you use the maximum value for each item you could be taking memory away from your applications, which could also cause unnecessary swapping, and therefore slow down performance. (See section 9.0 for information on memory usage.) The following table contains the recommended values for the configuration files. _SYSTEM _base _add _add _add _maximum_ _DESCRIPTION _system: _for _for _for _system _ _ -------> _ _each _each _each _config-_ _-------------_ _extra _ghost _extra _ urtion_ _"vconf" _2 user _user _task _printer _ _ _BOSS/IX) _1 printer_(above _ _(above _ _ _PARAMTERS _no ghosts_2) _ _1) _ _ _ _ _ _ _ _ _ _buffers= _ 16 _ 4 _ _ _ 64 _ _printers= _ 1 _ _ _ 1 _ 14 _ _procs= _ 20 _ 5 _ 3 _ 1 _ 80 _ _tsegs= _ 16 _ 4 _ _ _ 64 _ _sockets= _ 5 _ _ _ _ 6 _ _dsocket= _ 3 _ _ 4 _ _ 36 _ _lanbuffers= _ 8 _ _ 2 _ _ 16 _ _locks= _ 64 _ 5 _ 5 _ _ 160 _ _clists= _ 8 _ _ _ _ * _ _mfsys= _ 3 _ _ _ _ ## _ _lus= _ 64 _ 10 _ 10 _ 6 _ 254 _ _opens= _ 40 _ 8 _ 10 _ 2 _ 206 _ _eventcalls= _ 64 _ 5 _ 4 _ _ 152 _ * undefined but each buffer takes up 60 bytes of memory per terminal so the memory usage can be great if the number is too large. 8 should be sufficient for most usages with the exception SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg021 of asynchronous serial communications. ## The number of mountable filesystems should be based on the number of mountable disk partitions on your system. 7.0 Security Security on the MAI\ 2000 is optional. There are three levels of security. System security, file security and application security for software packages. 7.1 System Security System security is implemented by terminal logon and passwords. Each operator can be assigned an account name and password. When the system is started each terminal can be automatically started with the '/bin/login' program. This program written in the 'C' language will monitor the access of operators to the system. Once, logged on, the operators can be localized to a specific area of the system. Operator information within the '/etc/passwd' file, states the operators working directory, their password and the program to be run when the operator logs in. Once, the program completes or the operator exits the program they can be sent back to the login prompt, thereby, restricting the user to one area of the system. From logon the operators can be sent to any part of the system, command mode, BASIC, menu system or as discussed a program (BASIC or 'C') 7.2 File Security File security is incorporated in the Business File System portion of the operating system. All files and directories created on the system are assigned access privileges ( read, write and execute ). These privileges are specified for the owner and for others ( all non-owners ), by the file owner ( the person who created the file ) at the time the file is created. Any unauthorized attempt to access the file will result in an error message "access denied". The access modes can be changed at any time by the owner with the '/bin/filemodes' command or the '/util/fsecure' utility.. 7.3 Product Security Product Security allows installation and use of BOSS/IX~ chargable products on an authorized basis. This ensures control of software by MAI BASIC FOUR, Inc. and software vendors for the MAI\ 2000. This authorization is provided through a lock and key process. All products with lock and key protection will be licensed on a per system serial number (SSN) basis. Without the correct key the software will not execute. Purchased MAI\ 2000 products will arrive at the customer site with the key certificate attached to the media. 8.0 Disk Organization Upon installation of BOSS/IX~ 7.1A operating system software the SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg022 disk is automatically mapped out into four partitions. On two of these partitions filesystems are created. The terms partition and filesystem are used extensively on the MAI\ 2000 system to discribe the disk organization and layout. The following sections give a brief description of what a partition and filesystem are, and how they relate to each other on the MAI\ 2000 system. 8.01 The Partition Each fixed disk or floppy diskette on the MAI 2000 can be divided into sections called partitions. There can be from 1-32 partitions on each disk. The number of partitions would depend on application and size of the disk. All information about the number and size of the disk partitions is contained in the super block. The super block is located at the beginning of each disk or floppy diskette. The main fixed disk of a system is pre-defined by the BOSS/IX operating system to have four partitions. The first partition is the entire disk 'wd0' or 'rwd0', the second partition is called the 'boot' (size 2MB). The third is the 'swap' area (size 2MB). The forth is called the 'root', (size of the root depends on the disk size) the root is defined to the end of the disk. Any other disks on the system need only have one partition. The boot and root partitions contain filesystems. The swap area is used when the operating system needs more memory. The operating system swaps out (or copies) sections of memory to the swap partition in order to extend system memory. 8.02 The Filesystems The file system portion of the operating system manages data on the disks. It allocates and defines directories and files. The file system organizes multiple directories and files into a heirarchical inverted tree structure. The tree structure is called a "filesystem" (one word). Filesystems can only be defined on disk partitions, only one filesystem per partition. Each filesystem starts with a single directory called the root directory symbolized by a '/', (not the same as the root partition). The root directory can contain files and other subdirectories, these subdirectories can contain other files and subdirectories ... . The following is a representation of the filesystem that is created on the root partition during installation. / <---root directory _ ---------------------------------------------------------- _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ bin dev include etc mnt lib usr tmp sys util _ _ ----------- _ _ _ bfs sys ut _ SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg023 _ -------- _ _ bfs.h spool.h At system load time (during a normal load) when the operating system is loaded into memory, it will attach or mount the root directory of the filesystem on the root partition to the operating system. This process is called rooting "the system is rooted to the root partition". The operating system only recognizes one root directory (one filesystem). In order to access files or directories on other filesystems, those filesystems must be mounted (logically attached) to the currently rooted filesystem. The operating system provides a special directory "/mnt" for this purpose. But, any directory will do. Note: If you mount over a directory containing files, then those files will be inaccessable to you during the time the other filesystem is mounted (until it is unmounted). 9.0 Memory Usage This section describes how to calculate the optimum memory requirements for your MAI\ 2000 system configuration. Your system's memory requirements are based on the hardware options (such as number of terminals and printers) and software packages (such as BASIC, BASIC applications, utilities, LAN, etc.). You can use your system with less than optimum memory. However, it will run slower because application tasks must be swapped between main memory and disk. This section details the steps used to calulate the amount of memory required to avoid swapping of application tasks. 9.1 Calculating Your System's Memory Requirements This section describes how to calculate the number of memory boards your system requires for optimum performance. Step 1 To compute the memory required, add the following numbers: NOTE: 1 KB = 1024 bytes 225 KB this is the memory required for the base operating system program. 57 KB* This is the memory required by BOSS/IX~ for table space for the base configurations: two users (two terminals), one printer, and no ghost tasks. You will need to allow more memory for table space for each additional user as described later in this formula. How to calculate the exact amount of memory required for table space is explained later in this section. 6.5KB* Add 6.5 KB for BOSS/IX~ table space for each additional user above the two that are allocated in the base system. 1 KB* Add 1 KB for BOSS/IX table space for each additional SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg024 printer above the one that is included in the base system. 30 KB Add 30 KB for each additional printer (above one) that you want to print concurrently. This is a memory allowance for a despooler task. 6.6KB* Add 6.6 KB for BOSS/IX~ table space for each ghost task. 70 KB Add 70KB for memory allowance for swappable system tasks, including the print spooler, the print despooler, the system error log task, the system start process, the command interpreter, etc. These processes can be swapped with each other without affecting the application processes. 160 KB Add 160 KB for each unique non-BASIC tasks that will be executed concurrently on your system. Such tasks include the BASIC interpreter, (you need one BASIC interpreter task to support any number of BASIC programs), the utilities, LAN, Informix, communications, the command interpreter, etc. When computing the memory required for application tasks, you should consider how often each application is used. For example, if you seldom execute the commands or the utilities, you do not need to allocate memory for them. When they are executed, system performance will slow, but this is probably acceptable. 60 KB Add 60 KB for each user that will be executing tasks concurrently. For example, if you have ten operators who are allowed to login but your system only has five terminals, you will have a maximum of five users at any one time. If some of your terminals are infrequently used, you don't need to allocate 60 KB for an operator on that terminal. 60 KB Add 60 KB each ghost or background task that will be executed concurrently. Add 60 KB for each frequently used ghost task server. Each ghost task requires a ghost server, but you only need to allocate memory for a ghost server if the ghost task will frequently communicate with a terminal task or another ghost task. These types of inter-task communications are performed by the ghost server. The resulting number is your system's "memory requirement". (*: the four items marked with an "*" above are the memory required for BOSS/IX operting system table space. These numbers are an approximate allowance for the table space memory. Later in this section, a method is given for computing the exact size of the table space required.) Step 2 Decide how much swapping of application programs you can allow on your system. Swapping slows the speed of execution. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg025 If you want to run without swapping, you must provide the entire memory requirement that you computed in step 1. If the cost of memory is more important than speed, multiply your system's memory requirement by 0.7. (memory requirement x 0.7) This number will result in a system where application programs must be swapped. You can also multiply the memory requirement by some number between 0.7 and 1.0. The closer to the full memory requirement that you provide, the less swapping will be necessary. The result of this calculation is your system's "memory need". Step 3 You can now compute the number of memory boards that your system needs by dividing the memory needed by 256 KB, the amount of memory on a single board (memory needed /256 KB). If a fraction results, you should round the result to the next highest whole number. (However, if your calculation shows that you need 3.1 you can use 3 boards without a performance degradation.) A maximum of six memory boards can be installed in an MAI\ 2000 system, three boards come standard in all MAI 2000 base systems. If your figures show that you need more than six memory boards, even with the 0.7 factor that allows some swapping of appliction tasks, you are overloading your system! 9.1.1 Example Of How To Calculate A System's Memory Requirement This example shows how to compute the memory requirement for a system with 5 terminals and two printers. Four of the terminals are dedicated to running BASIC applications: accounts receivable, accounts payable, payroll, and word processing. The fifth terminal is used to run the utilities, the commands, or the Informix database application (on-line queries). One of the applications uses a ghost task to output reports to a printer. Step 1 Add these numbers to compute "memory required" 225 KB base operating system 57 KB operating system starting table space 6.5 KB x 3 allowance for table space for three additional users (total of 5 users/ terminals) 1 KB Allowance for table space for an additional printer (total of 2 printers) 30 KB allowance for concurrent printing to the second printer. 6.6 KB allowance for table space for one ghost task 70 KB swappable system tasks 160 KB x 2 allowance for the BASIC interpreter and for the utilities/commands/Informix 60 KB x 5 allowance for five opertors executing concurrently 60 KB one ghost task 0 KB no memory is allocated for a ghost server because the ghost task in this example doesn't communicate with other tasks. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg026 TOTAL = 1089.1 KB = memory required NOTE: Total BOSS/IX~ table space allocated for this example: 57 + (6.5 *3) + 1 + 6.6 = 84.1 KB. Step 2 Compute "memory needed" If we don't want to allow swapping of application tasks, memory needed is the same as memory required: Memory needed = 1089.1 KB. If some swapping of applciatin tasks is acceptable: Memory needed = 1089.1 KB * 0.7 = 762.37 KB Step 3 Compute the number of memory baords required No swapping: 1089.1 KB / 256 KB = 4.25 boards Rounded to the next highest whole number, this means that the example system needs five memory boards. Five boards allows extra memory that can be used for additional applications. However, system performance would probably be adequate (little swapping) with four memory boards. Swapping allowed: 762.37 KB / 256 KB = 2.98 boards The example system needs three memory boards to operate with some swapping of application tasks. 9.2 Exact Method For Calculating BOSS/IX~ Table Space Memory Requirement The above method of calculating your system's memory requirements is approximate. It is good for most systems and most situations. However, if you have a large system or a unique configuration such as LAN, you might need to use a more precise method to compute the memory required for the operting system table space. The approximate method described above starts by allocating a fixed 57 KB for operating table space for the base system. Additional space is added for each user, printer, and ghost task. This section describes how to calculate the exact size of the operating system table space needed by any configuration. Table 9A shows the exact amount of memory required for each BOSS/IX~ operating system parameter that adds to the table space. (These parameters can be changed by using "vconf". See section 6.2 of this document.) The exact method computes that the base system required 57.18 KB for table space (look at the totals at the bottom of Table 9A). This is almost identical to the 57 KB allocated for table space by the approximate method. The exact method computes that the five-user example system requires 82.73 KB for table space. The approximate method allocates a slightly larger 84.1 KB. Using either calculation method, the number of memory boards required for the example system is the same. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg027 Table 9A BOSS/IX Operating Parameters and Memory Requirements _ _memory _params.'s_total _param.'s_total _ _BOSS/IX _used for_for base _memory _for _memory _ _PARAMETERS _each _config- _for base_example _for _ _(set by _param. _ uration _system _system *_example_ _"vconf") _(bytes) _system _(bytes) _ _system _ _ _ _ _ _ _(bytes)_ _buffers= _ 566 _ 16 _ 9056 _ 28 _ 15848 _ _printers= _ 204 _ 1 _ 204 _ 2 _ 408 _ _procs= _ 274 _ 20 _ 5480 _ 39 _ 10686 _ _tsegs= _ 20 _ 16 _ 320 _ 28 _ 560 _ _sockets= _ 600 _ 5 _ 3000 _ 5 _ 3000 _ _dsocket= _ 600 _ 8 _ 4800 _ 12 _ 7200 _ _lanbuffers= _ 400 _ 8 _ 3200 _ 10 _ 4000 _ _locks= _ 30 _ 64 _ 1920 _ 84 _ 2520 _ _clists= _ 64 _ 8 _ 512 _ 8 _ 512 _ _mfsys= _ 424 _ 3 _ 1272 _ 3 _ 1272 _ _lus= _ 40 _ 64 _ 2560 _ 110 _ 4400 _ _opens= _ ** _ 40 _ 24944 _ 72 _ 32643 _ _eventcalls= _ 20 _ 64 _ 1280 _ 83 _ 1660 _ ** This formula is used to compute the amount of table space memory required for opens: (214 x #opens) + 16384 = table space memory for opens 10.0 For Your Information The following information is a list of known problems and warnings relating to the MAI\ 2000 WARNINGS o The system console configuration information is resident in the non-volatile RAM (NVRAM) of the CMB (central microprocessor board). This information is preset at the factory. The system console is set to the first port of the first four way. If your system does not have a four way this configuration information must be reset to the first port of the CMB. The following steps are necessary to reset the NVRAM: - Turn on the CCA (central cabinet assembly), during self test the system will look for the system console as defined in the NVRAM. If it does not find the first port off the four way, the first port off the CMB will be utilized. During the memory portion of the self test you will have time to enter a ' Z' ( key plus "Z"). - The system will complete the self test, then enter debug mode. The prompt will be displayed on the screen. - Enter NVRAM configuration mode by typing "config", the prompt will then display. - Read the current NVRAM settings by typing "read" at the prompt. - Display the information you just read by typing "display". - To reconfigure the system console type "console". You will be prompted for the following information, one item at a time. Enter the SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg028 information exactly as listed below: Console dev: sc Console Port: 0 Baud Rate: 9600 Data Bits: 7 Stop Bits: 1 Parity: odd Flow Control: xon - Save the new configuration by entering "write" and responding with a "y", to the Write it (Y/N)? prompt. - Exit the program by typing "debug", at the prompt type "boot wd0", , then again at the 'system file' prompt. - On subsequent system loads, the proper console port will be found. GENERAL WARNINGS o The bytes used column displayed from the '-l' option of the '/bin/ls' command does not reflect the true disk usage of a non-string file. In order to determine exactly how much disk space is being used by a file use the '-blks' option of the '/bin/ls' command. Example: "ADMIN>ls -l -blks /directory name(or filename)". The following will display: Ind 0 < 47> rw. rw. admin Jan 21 11:01:41 testindex The 47 is the blocks used. The 0 indicates the number of data bytes in the file (including duplicate keys for sort and direct files). The file display utility '/util/finfo' will also give you the exact disk usage. o Don't use 19200 Baud rate on the system console. o Under Dump procedure - make sure the tape drive is powered on before executing procedure. o If you run into a condition where you are running out of system resources (values in '/etc/conf' file too low or memory too little for system usage) one of two choices are available. 1. Reconfigure using 'vconf' giving the system more of the resource you need. (See section 6.0) 2. Re-evaluate your memory requirements (See section 9.0 Memory Usage). o Errors may occur when running more than 3 ghosts while running LAN applications. o Any keyed files saved to MCS on or before 7.1A * 27 must be restored using the *27 version of '/bin/mcsrestore' or all keys will be lost. To restore these files, make a copy of *27's '/bin/mcsrestore' and copy it to your 7.1A *34 system. Do not copy it to the '/bin' directory or you'll wipe out the new version of the command. After using the old version of mcsrestore to restore your old backups it is recommended you delete the old version and resave your files to tape under *34 to avoid problems in the future. o If your keyed files restored from *27 were saved, at any time, with no SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg029 records in them then you will not be able to remove keys from these files ever. If you cannot remove keys from a keyed file restored from *27 simply create a new keyed file and transfer the records from the old file to the new using BASIC reads and writes and delete the old file afterwords. o When upgrading your system from *27 or below to *34 via diskette or MCS, the following will occur: - Upon booting *34 an error will occur which will be logged to a file stating the system can't find the mnemonics table "default". This is because the name for non-standard MAI\ 2000 terminals has been changed from "default" to "other". Reconfigure your ports to the new name after upgrade/install. - You may get errors accessing your printers on *34. If this is the case, check your configuration. Some of the printer names have been changed and *34 will not recognize the old names. For example, the parallel printronix in *27 was called "Printronix", in *34 it is called "lpm". To correct the problem either reconfigure the port or install the default configuration parameters while installing *34 as above. o 1.5 MB memory is required for running EBC concurrently with up to 4 othr tasks. 1.25 memory minimum is required for running EBC in stand alone mode. o When running EBC in a multi-user environment, any user logging off will cause the EBC session to abort. If this occurs, simply restart the session. o Errors may occur when running more thatn 14 tasks at 1.5 MB of memory. WORKAROUNDS by PRODUCT PRODUCT: EBS - BASIC 1. PREFIX: ERROR 17 generated adding more than 9 directories to a Prefix list. Workaroung: Maximum number of directories in a Prefix list is 9. 2. Table statement: Error 34 is generated if try to type in a complete table. Workaround: Type table statement in at least 2 parts. 3. ADDE: Rolling error 12's Workaround: Do not erase or rename an ADDE'd file 4. ADDR: System hangs when ADDing several programs. Workaround: Limit the number and size of programs ADDed to memory. BASIC Utilities: 1. Report Files: Not suitable for terminal viewing using '/bin/p' command. Workaround: Send report file to printer. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg030 2. Printers; Selection of printer devices differs from other utilities in bxref, brenumber, bsearch, bcompare. Workaround: Choose option number from menu of upper case device names to correspond with actual printers defined on system. Example: system printer=p0, choose number 2.P0. 3. bencrypt: Fills in erroneous extent sizes after access error message received, then change file name. Workaround: Enter in desired correct values for extents when this happens. PRODUCT: EUT - UTILITIES 1. ddelete: Cannot delete a directory if there are no free file descriptors in the file system. Workaround: Delete the directory using the unos "delete -r" command. 2. fsdbg/fschk: If disk is full, corrupted directory(s) within filesystem cannot be repaired. Workaround: The minimum space required to repair a directory is the sum of the size of the directory in blocks plus an equal number of free blocks. 3. /fschk: No help text is available. Workaround: Refer to the users guide. 4. fmove/fcopy: Report file is incomplete. Workaround: Send output to printer or terminal, not to a file. 5. fsdbg: If "repair = yes", the tool "MODIFY A BLOCK" writes incorrect information to the block. Workaround: None, do not use this tool. 6. fsdbg: If "repair = yes", set type doesn't recognize encrypted basic programs. Automatically changes type to "TYPE UNUSED", string file. Workaround: Reset default back to type = "CONTIGUOUS" and 'encrypted basic program' before exiting this option. PRODUCT: EIT - INTERSYSTEM TRANSPORTER 1. When using ATP to transfer files from MAI\ 2000 to MAI\ 2000, the receiving system will produce an error 41 (Invalid Integer Range) when incoming files are program files. Workaround: To solve this problem the user should avoid sending program files between system's via the ATP package. Instead, use some other means such as magnetic cartridge streamer (MCS) or floppy disk to transport these types of files, or converting program files before ATP transport. PRODUCT: EDB - DATABASE MANAGEMENT SYSTEM 1. Error 4012 is generated using DBSTATUS to 'LOAD' a file which has SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg031 a key or keys which are duplicates of those in the destination file. Workaround: Unless you are sure there are no duplicate keys between the files, you should create a new destination file before 'LOAD'ing. PRODUCT: EBC - BATCH COMMUNICATIONS The following problems deal with a hang or premature termination of a communication session. An operator should be aware that while running a communictions session a hang or premature termination may occur - but only on a very infrequent basis. o During or following text transmission of an indexed file in 2770 expanded buffer, an incident occurred whereby the Local Status Log posted the message "Illegal mnemonic" five hours following the last entry. Apparently BCOM had hung for that period of time before terminating abnormally. o Terminal 0 hung during a communications session. Local Area Network tests were being conducted at this time and consisted of Remote CMD execution tests and point to point functional tests. Only terminal 0 running EBC had a problem. o BCOM process suspended when the attempt was made to change the next entry to transmit while a communication session running. A file write error occurred. This condition only occurs as a very infrequent basis and cannot be predicted. o Premature communication session termination occurred while transmitting in 2780 standard EBCDIC text mode. First record transmitted (minus ETX/CRC/CRC/) was followed by NULL and extraneous characters. The receiving system issued one ENQ, then both system teminated with DLE/EOT. o A "line check" may occur during file transfer (or possibly any other mode) whereby the communication session on the remote system (also a 2000 system) never terminates the session, but when an attempt to restart the session is made an error -534 or -532 (error opening logical port) may occur. This indicated a virtual circuit in congestion or time-out occurred. The next session was successful. Workaround: It may be necessary for an opertor to kill BCOM associated processes if still active, prior to restarting the communications session. PRODUCT: LAN - LOCAL AREA NETWORK 1. Executing '/bin/login' using lan rcx causes '/dev/null' to lose 'rw' permissions. Workaround: Do not try this. 2. Lan rcx gets "time out" error if a command is not specified in the command line. Workaround: Always specify a command when option -C is used. 3. Remotely copy a large direct file gets error -538. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg032 Workaround: None. 4. System hung when running EBC, LAN and cwrite concurrently. Workaround: None. PRODUCT: DIA - DIAGNOSTICS Note: Only the Logic tests and System Interaction Test (SIT) are being released. 1. All Programs: Cannot send output to a printer using BASIC Four protocol. Workaround: Use either terminal display or switch to standard interface for printer output. 2. floppy: Tests listed in documentation do not match what is actually on the system. Workaround: Use 'list-tes' command for list of available test. PRODUCT: WBD-WINCHESTER BOOTABLE DIAGNOSTICS 1. Test listed in documentaiton do not match what is actually on the system. Workaround: Use 'list-tes' command for list of available test. 11.0 Helpfull Hints 11.1 Lost Files When a file system is repaired, files can be lost due to a corrupted directory structure. These files will be placed in the repaired file system's root directory (/) under the name of "lost number" (the number is the inode number of the corrupt file). The procedure might be as follows: 1. Do an alternate load and root to the boot partition system file is ',/etc/boot.conf.'. Then mount '/dev/root' to '/mnt'. 2. Separate the lost files by file type, i.e. BASIC, Key, Serial, String. 3. In the case of an event count file ( a file that ends with ".ec"), there is no way to tell where the file belongs. Delete it. The file may very well be important to the operating system. To be safe you should re-install the operating system. 4. For BASIC program files: A. Start BASIC B. Load the program C. List the program Usually line 10 has a REM statement telling the program's name. If not try to figure out what the program does. Re-save the program with the correct program name. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg033 5. For directories, do an 'ls -l' on them. The contents will usually tell you what they were. Rename the lost directory name to the correct name. 6. All other files, use the "dump" command to examine their contents. From that information you may tell what the file is. Rename the file if you can identify what it is. 7. If possible look at another system of similar arrangement. 11.2 Mnemonic And Translation Table Usage 1. To make a hex code change to an existing mnemonic table: ADMIN>cd /etc/ttymntbl ADMIN>ved 7270.mntbl (to make necessary changes to the file) ADMIN>makettymntbl 7270 Then shutdown and restart the system to use this new table. The table can be loaded immediately for the users terminal with a ttymntbl command. 2. To make a new table: 'ved' the contents of an existing table which is similar and modify it. ADMIN>cd /etc/ttymntbl ADMIN>ved newname.mntbl In 'ved' type ' G' ( a plus "G" ) and enter the name of an existing file such as 'evdt.mntbl'. To generate the new table run the '/bin/makettymntbl' program. ADMIN>makettymntbl newname Then run the configure utility and change or add the terminal type to the type you just created (option 2). Shutdown and restart the system to load the new table. Refer to Systems Users Guide for additional explanation. 3. Translation tables in the directory '/etc/ttyxlt'. Note no translation tables currently exists because they are not necessary to support MAI 2000 peripherals. ADMIN>cd /etc/ttyxlt ADMIN>makettyxlate tablename ADMIN>ttyxlate tablename Then run the configure utility and add the translation table to the input or output translation (options 12 or 13). Refer to the command manual for more information. 11.3 Steps To Edit BASIC Program Using 'ved' ADMIN>basic s=128 Business BASIC level EBS 7105 READY SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg034 >load"basicprogram" >string "filename",0 >open(1) "filename" >list (1) >release ADMIN>ved filename ADMIN>basic s=128 Business BASIC level EBS 7105 READY >vmerge "filename" 11.4 'vconf' Changes To change vconf for the system you must change the conf file contained in boot /etc/conf not root. The root /etc/conf file is a copy. 11.5 Diskette Partitions To make partitions on a floppy disk First, modify super block on '/dev/rfd0' (see 11.9 substituting 'rfd0' for 'rwdx'). ADMIN>makedev /dev/fd1 b 7 2 ADMIN>makedev /dev/fd2 b 7 3 ADMIN>makefs /dev/fd1 1120 ADMIN>makefs /dev/fd2 160 Changing the block size will appear to work but you will not have access to the entire block allocation. 11.6 File System Definitions A filesystem is contained within a partition. All partitions do not contain filesystem. Mounting is done to a filesystem not a partition. Each partition must have a device name (/dev). Raw means unbuffered. 11.7 Help Key On EVDT & 7270 The help key is ' Z' ( a plus " Z") (HEX OX1F). 11.8 Change The Maximum Number Of Mountable Filesystems A. ADMIN>mount /dev/boot /mnt B. ADMIN>cd /mnt/etc C. ADMIN>vconf conf mfsys=# -save (#=number of fs that you want) D. ADMIN>cd / E. ADMIN>unmount /mnt F. ADMIN>reboot the system 11.9 Make A Partition A. get into admin SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg035 B. ADMIN>usb -help C. ADMIN>usb /dev/rwd desc=tmpdsk -get (file tmpdsk now contains info for partitions) D. ADMIN>ved /etc/diskdesc/tmpdsk (change block lengths as needed add a new partition, start of block and number of blocks) E. put edits F. ADMIN>usb -help G. ADMIN>usb /dev/rwd type=tmpdsk -save -set (set puts it into memory) H. now have the new partitions I. makedev for each new partition (14 XX major minor, one buffered one not). Wd0 major number 14 minor numbers 0-31, Wd1 minor numbers 32-63, Fd0 or 1 major number 7. Minor numbers 0-31. J. makefs for each device, if a size is omitted, the partition size will be used Please note adding another partition to the Wd0 is not recommended. If that is done you must recreate a file system for '/dev/root'. 11.10 Instant Shutdown Type 'shutdown -- -1' from admin, to go to single from multi user mode. 11.11 BASIC Language Slow Mode From Execute Execute command in basic will not turn off "fast" flag if you don't access a line number. 11.12 Debug Mode ' Z' ( a plus "Z" ) during initial system test will put you into the debugger (). Type "h" to get a help menu. If you ever get into lower case debug by accident () shutdown the system or hit the reset (DEBUG) button at the back of the MAI 2000 without hitting any keyboard keys. Lower case debug does not have a help menu and executes single character commands. It is very easy to key the wrong single character code in lower case debug (such as "w" for write) and prevent the system from working. 11.13 Diagnostics Test auto= automatic test of system from user diagnostics (DIA) 11.14 Change The System Boot Device a. boot the system, press ' Z' ( a plus "Z" ) during memory test, this will place you into the debugger. b. type "config", this will display the boot configuration menu. c. type "boot", this will prompt you to enter the boot device and boot unit. For a hard disk boot device=wd, boot unit=0. d. type "write" to write the information to the nvram. e. type "read" to read the nvram. f. type "display" to show the last read. g. type "debug" to reenter the debugger. h. type "boot" to reboot the system. 11.15 MACROS For Lan SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg036 o Set Remote control with lan (#b lan /lan/lan rcx -c s=$1 $2) o To log onto other system (#b lanlog /lan/lan rcx s=$1) o To run LAN file copy (#b copy /lan/lan rcopy) 11.16 Making A Boot Floppy The following procedure is setup to be put directly into a command file, if you do not want to use a command file simply omit the 'echo' statements. echo "formatting fd0" devfmt /dev/rfd0 echo "make filesystem on fd0" makefs /dev/rfd0 1280 makedir /mnt2 makedir /mnt1 mount /dev/boot /mnt2 mount /dev/fd0 /mnt1 mount makedir /mnt1/etc makedir /mnt1/bin makedir /mnt1/sys makedir /mnt1/dev makedir /mnt1/mnt makedir /mnt1/tmp makedir /mnt1/etc/ttymntbl copy /mnt2/bin/unmount /mnt1/bin/unmount -v copy /mnt2/bin/mount /mnt1/bin/mount -v copy /mnt2/bin/fschk /mnt1/bin/fschk -v copy /mnt2/bin/date /mnt1/bin/date -v copy /mnt2/bin/command /mnt1/bin/command -v copy /mnt2/bin/admin /mnt1/bin/admin -v copy /mnt2/bin/makefs /mnt1/bin/makefs -v copy /mnt2/bin/mcsrestore /mnt1/bin/mcsrestore copy /mnt2/etc/conf /mnt1/etc/conf -v copy /mnt2/etc/ttymntbl/* /mnt1/etc/ttymntbl -v copy /mnt2/etc/start /mnt1/etc/start -v copy /mnt2/etc/sinit /mnt1/etc/sinit -v copy /mnt2/etc/passwd /mnt1/etc/passwd -v copy /mnt2/etc/mounttab /mnt1/etc/mounttab -v copy /mnt2/sys/unos /mnt1/sys/unos -v copy /mnt2/sys/crashinfo /mnt1/sys/crashinfo -v copy /mnt2/dev/* /mnt1/dev -v copy /mnt2/bin/ls /mnt1/bin/ls -v echo "date" > /mnt1/etc/sinit echo "date > /etc/mounttab">> /mnt1/etc/sinit echo "date > /etc/boot.log">> /mnt1/etc/sinit vconf /mnt1/etc/conf -single size=0 root=700 -nodump -save -oride unmount /mnt1 echo "putting fd loader onto fd0" cd /mnt2/sys putloader fd /dev/fd0 cd unmount /mnt2 echo "complete" 11.17 '/bin/debe' One Hard Disk To Another The following procedure is setup for MACROs but the same lines can be executed in command mode or from a command file, simply remove the "#b label name". SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg037 ADMIN>#b cmic usb /dev/rwd0 desc=mic -get ADMIN>#b cp1 debe if=/dev/rwd0 of=/dev/rwd1 -pg bs=1b count=4 ADMIN>#b cp2 debe if=/dev/rwd0 of=/dev/rwd1 -pg ivskip=5b ovskip=5b bs=102b ADMIN>#b udsb usb /dev/rwd1 type=mic -save -get -set ADMIN>cmic ADMIN>udsb ADMIN>cp1 ADMIN>cp2 use cmic then udsb then cp1 and cp2 assumes all hardware is hooked up and a 43MB disk. 11.18 '/bin/ved' the '/etc/passwd' File A BASIC program can be executed from the log on by editing the account ID file called '/etc/passwd' or using the 'oprinfo' utility. For example, to begin execution of a BASIC program called 'START' under the directory '/usr' for ID's jane and john the '/etc/passwd' file would be changed to read: HOME FIRST PROGRAM ID DIR TO EXECUTE COMMENTS admin::0:::/:/bin/command command language jane::1:::/usr:/bin/basic,s=128, RUN "START" can escape to BASIC john::2:::/usr:/bin/basic,s=128,-nr, RUN "START" can not escape to BASIC immediate mode 11.19 MISCELLANEOUS o 'fschk -f /dev/fd0' on diskette if floppy is removed without unmount command o 'ls >/util/fl/filename.f' and then use ved to create a file list o ved /etc/forms to change the printer form width o install key or ved /etc/level/name for lock and key o MCS backup can be conveniently run with a command file, recommend mcscompare o baud rate of VDTs can be set to 19.2K for faster performance (X-on/X-off and/or DTR should be set all but system console). o S/10's must be set to 7270, 7-bit with X-on/X-off set. 11.20 Device Major and Minor Numbers The device major number designates a particular I/O driver, the minor number of a device refers to the logical device. All accessable devices on the MAI\ 2000 have a major and minor number. These numbers can be viewed by typing 'ls -l /dev | p' at the command mode prompt 'name>'. Major Device Number Description 0 Null device 1-4 Reserved for operating system 5 Parallel Port 6 Cartridge Streamer 7 Floppy Disk 8 Printer Filter 9 CMB 10 Four Way SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg038 11 LAN 12 Synchronous Communication 13 Ram Disk 14 Winchester Disk 12.0 Enhancements/ Corrections from 7.1A*18 (pre-release) to 7.1a*34 (released version) EBS - new option to BASIC '-x' ( cause all control 'c's and escapes to be ignored). EBS - 'sn' and 'sw' mnemonics. Two new fields have been added to the tty table for these mnemonics, all custom tables should be recompiled. EBS - fixed BASIC GOSUBs, they can now execute with less than 600 bytes DSZ. EBS - fix to NUM ("E1") EBS - BASIC fixes - TBL = now compatible with 13XX BEGIN now compatible with 13XX in regard to clearing ENTER'd variables in a called program. EBS - '!menu' can now be executed from BASIC. EIT - new file '/util/BQRLOG' used to keep a log of conversion error messages. EIT - Transporting to 13XX from 2000, make sure to have at least one Ghost and 128 pages of free memory. EIT - Converter can be run concurrently on different filelists on different terminals. EIT - '/util/cread' now converts program files. EIT - Converter handles records of lengths, 8000 bytes without a SKEMA and 5000 bytes with a SKEMA. EOS - You are now able to initialze and start errlog from multi-user. EOS - Auto fschk added '/etc/syschk'. This program does an automatic filesystem check if the rooting filesytem was left mounted due to a system crash or power failrue. EOS - Shutdown from any terminal now available. EOS - '/dev/rcs' device has been removed. EOS - New device types for terminals and printers. Run configure after upgrade to rename terminals and printers. EOS - System configuration file '/etc/conf' on the boot partition is set to the minimun configuration (.75 MB, 2 users and 1 printer). EOS - '/bin/mcscompare' has new option -errors this option will cause mcscompare to only display files that don't compare and the total number of files that didn't compare. Also, the syntax of the command has changed slightly, check the command help (-h) option exact differences. EOS - configure - sets default BAUD rate to 9600 for serial MVP printers. - sets BASIC Four interface parameter ="no" for DMP serial printers EOS - '/bin/vconf' added -debug and -nodebug options, Turns on/off kernel debugger. EOS - 'ps' command now displays the initial program that is executed when the user logs in. EOS - 'ved' The file '.EDTMP' has been changed to to 'EDTMP.n' where 'n' is the operator number. So that each operator can have the last file they edited be saved in their working directory EOS - '/bin/space' has a different now look to its output. EOS - Support of serial MVP printer. EOS - '/bin/ubb' command has been removed. EOS - Performance enhancements added to the ttydriver. EOS - System error logger enhanced to provide more details. EOS - Changes made to floppy driver to flush cashe on close. EOS - '/bin/usb' added parition size in MBs. EOS - Changed 7270 mnemonic table so the 'RT' mnemonic works. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg039 EOS - Changed EVDT mnemonic table to use single character control codes instead of three character escape sequences to move up, down, right and left. Certain mnemonics may execute faster. EOS - ' X' in basic will now return an error on the next input or output. This makes ' X' compatible with the 13XX. EUT - '/util/freespace' followed 'space' with a new look. EUT - The help key ( Z) will accept any prompt. EUT - Utilities no longer search alternate directories. EUT - Alias printer names included in menu of printer devices displayed. LAN - LAN will not communicate with releases prior to *27 (LAN 7114) LAN - LAN install must be done in single user mode. LAN - LAN configuration must be done in multi-user mode. WBD - new WBD must have 'B2.9 kernel PROM or greater. 13.0 Dump Procedures This section describes the enhancements made to the MAI 2000 system crash recovery procedure. The overall objective is to provide a "user friendly" procedure for recovery from any premature system shutdown situation (CRASH). A "premature shutdown" is typically a power loss, inadvertant use of reset button, or fatal operating system error etc...). When the user attempts to reboot, the system should provide the following: Automatic reboot to system boot partition when operator attempts to boot on a "crashed" system. Automatic repair of all damaged filesystems. Handle saving and clearing of system crash dump information stored on system swapper partition. Be able to save dump to floppy disk, save dump to streamer tape, or take no action on dump. The presence of a system dump on swapper partition should not prohibit swapping as in earlier operating system implementations. Minimal amount of user intervention to get system repaired and rebooted. The ability for a sophisticated user to abort auto-check/repair in order to closely analyze the reason for the crash. Repair/check procedures can then be executed manually. Check/repair should be executed any time the system is booted. This ensures that all partitions are useable. 13.1 Implementation The following section describes the implementation of the automated system crash recovery procedure. Changes were made to the Operting System (Kernel) and to the system start command (the first user process after boot.) Also, a new command '/etc/syschk' is added. The 'syschk' command performs a system dump save/clear procedure, if necessary, and a file system check/repair procedure. The syschk command is always initiated by the 'start' command, thus on every boot the 'syschk' command will check/repair any damaged (left-mounted) file systems. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg040 13.2 Command '/etc/syschk' The '/etc/syschk' command contains the file system check/repair and system dump save/clear procedures. It is executed automatically by the system start command, but can also be executed in user mode (for sophisticated users only.) '/etc/syschk' first checks for the existance of system crash dump information on the system swap device. If a crash dump is found, '/etc/syschk' walks the user through the optional crash dump save process. The user may save the crash dump to five floppy diskettes or to one streamer tape. The user is given a chance to format floppies if needed on the chance that the user doesn't have 5 formatted disks. After the format/save procedure is completed, the system swap device is permanently cleared of the dump information by writing over the system dump magic number. Note: Swapping will not be disabled during the 'syschk' process, so it is remotely possible for the dump to be inadvertantly cleared by swapper activity. However, swapping should not occur under normal circumstances. After taking care of the system dump (if any), 'syschk' begins the check/repair file system procedure. By default, 'syschk' scans every hard disk for any 'left mounted' filesystems (see configuration section 13.6 regarding non-default mode.) All 'left mounted' filesystems are checked for errors, then repaired. 'syschk' reports the number of errors repaired to the user. 13.3 Swapping With Crash Dump Swapping is not prohibited if a system crash dump is present on the swap partition. If, during a system boot, the root partition was "left mounted", the Kernel reboots to the system boot partition with "-override" and "-nodump" configuration flags set. The system start command is signaled, via a flag so that the 'start' command may display the appropriate messages. The "File system left mounted" message will be displayed only in verbose mode. 13.4 Command 'start' When '/etc/start' detects a 'root file system left mounted' condition by checking the value of the first argument passed from the Kernel. The user is prompted to continue with auto check/repair process. At this point the user may exit the auto check/repair procedure by pressing the 'ESC' key or continue with the procedure by pressing the key. 'start' also automatically shuts down the system after auto check/repair procedure has completed. 13.5 Files To Change/Delete The following files may be deleted from boot partition: .dump .dump f .dump t SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg041 Remove the following macros from the '.globals' file located on the boot partition: dump f dump t dump clr Delete line containing 'crashinfo' command in the '/etcsinit' file located on the boot partition. The release containing the crash recovery software should require that a new boot partition be installed from scratch. This would ensure that the changes listed above would be made correctly. 13.6 Configuration Requirements By default, the '/etc/syschk' command scans each partition of each hard disk initiating repair operations (fschk -fix -quiet) on each file system 'left mounted' during the crash. In default mode, NO configuration requirements exist. However, if the user desires more control of the check/repair process, a configuration file, '/etc/filesystems', can be installed on every "rootable" filesystem partition. The configuration file should contain a list of device names that correspond to the filesystems partitions that are to be examined during the boot process; only these partitions are examined. The file is to be in BOSS/IX~ filelist format: full path name full path name full path name The boot partition version of the '/etc/filesystems/ file should contain the device names of the root partition and all other user defined file system partitions. Similarily, the root partition version of the file should contain the device names of the boot partition and all other user defined file system partition. 13.7 Saving A System CRASH DUMP In the event of a system crash due to an operating system failure and the system dump flag is set in the system configuration record, filesystem check/repair is preceded by a system crash dump save procedure. First the user is asked to take action regarding the crash dump. - - - - - - - - - - - - - - - - System crash dump (created Mon. Oct. 22, 1984 13:42:48) is available for saving to floppy diskette or streamer tape. NOTE: System crash dump will be lost if not saved at this time. Crash Dump Save Menu (1) Save crash dump to streamer tape. (2) Save crash dump to floppy disks. Continue with system check. Selection: - - - - - - - - - - - - - - - - If the user wished to disregard the crash dump, the key should be pressed. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg042 Save to streamer tape case: The user is prompted to insert a tape and press - - - - - - - - - - - - - - - - Insert cartridge in tape drive. Press key to begin save. Labeling tape... Set: dump Id: dump Created: Oct. 30 Last written: Oct.30, OB:32 Saving system crash dump to tape... System crash dump has been saved to streamer tape. - - - - - - - - - - - - - - - - After the crash dump has been saved to tape, the crash dump menu is displayed again. Floppy diskette crash dump save case: The user should ready 5 floppy diskettes. Each floppy diskette should be previously formatted or formatted by the optional format procedure provided by this crash dump procedure. For example, the following section demonstrate how a user would save a crash dump to floppy with 5 newly unformatted diskettes. - - - - - - - - - - - - - - - - The following procedure requires 5 formatted floppy diskettes. Please label diskettes #0, #1, ... #4). Press key to format all unformatted diskettes, or press key to begin save. Format diskette(s): Insert diskette. Press key to begin format or press key when all diskettes are formatted. format starting track at 0, for entire device. After all diskettes are formatted the process will continue by prompting for the diskette #0 to begin the saving of the swap area to diskette. Insert first diskette (#0) into drive o. Press key. Saving kernel symbol map to first diskette... Insert second diskette (#1) into drive 0. Press key. Saving crash dump to remaining diskettes (#1, #2, #3, #4). System crash dump has been saved to floppy diskettes. - - - - - - - - - - - - - - - - After the crash dump has been saved to tape, the crash dump menu is displayed again. When crash dump has been saved to tape or floppy or both, the user should press . The message "Crash dump save procedure complete" is displayed; the crash dump is cleared; and the procedure continues with the auto check/repair file system procedure. 13.8 File System Check/Repair SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg043 In the event of a system crash (power failure, accidental reset, or fatal operating system error), the user may reboot the system as he/she normally would. During the reboot process the MAI\ 2000 will detect the need to initiate a check and repair on all damaged file systems before attempting a normal reboot. After displaying the MAI\ 2000 proprietary message, the systme will display the following message and prompt on the system console. - - - - - - - - - - - - - - - - * * * * * * * * * * * * * * * * * * Unable to root to desired disk partition. This partition was left mounted, possibly due to premature system shutdown. System has been rooted to boot partition in order to make repairs. Repairs must be made before rebooting system. Press key to begin automatic system check/repair. - - - - - - - - - - - - - - - - If user presses the key, the automatic system check/repair will begin. If user presses the key, the automatic system check/repair will be skipped and the user will be put into single-user mode on the boot partition. Note: The option is not recommended it is very important to always execute the filesystem check/repair. A check and repair will be performed on each file system left mounted when the crash occurred. After each check/repair has completed, the number of errors is displayed. For example... - - - - - - - - - - - - - - - - Repairing filesystem for device (14,3)... 6 errors repaired. Repairing filesystem for device (14,32)... 1 error repaired. - - - - - - - - - - - - - - - - After all of the filesystem have been repaired, the system automatically is 'shutdown'. 14.0 Documentation This documentation will be available to order at the end of March 1985. BFISD 6100 - Becoming Familiar with Your MAI 2000 BFISD 6200 - MAI\ 2000 User Guide BFISD 6250 - BOSS/IX~ Business BASIC Documentation BFISD 6251 - MAI\ 2000 Business BASIC Programming Guide BFISD 6252 - MAI\ 2000 Business BASIC Reference Manual BFISD 6253 - MAI\ 2000 Business BASIC Quick Reference Card BFISD 6255 - MAI\ 2000 Business BASIC Utilites Guide BFISD 6275 - MAI\ 2000 Peripherals BFISD 6353 - MAI\ 2000 Batch Communications User Guide BFISD 6354 - MAI\ 2000 Intersystems Transport Package User Guide BFISD 6351 - MAGNET 2000 Local Area Networking User Guide BFISD 6216 - MAI\ 2000 International Utilities User Guide 15.0 Lowest Acceptable Revision Levels (LARL) The following chart lists the LARL of each PCB on the MAI 2000 system. PCB Part Number LARL SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg044 CMB, Central Microprocessor Board 903441 AD 256K Memory 903368 A 4 - Way controller 903390 P MCS controller 903406 L LAN controller 903405 D WDC Winchester, Adapter Board 903439 B Power Supply Input Module 903443 D Power Supply Control Module 903394 A Power Supply Output Module 903445 F Adaptec Board 907649 C Power Supply Assembly 907472 E Diskette Disk Drive 907584 A Winchester Disk 400549 A * BOSS/IX, and MAGNET are trademarks of MAI Basic Four, Inc. UNIX is a trademark of AT&T Bell Laboratories. INFORMIX is a registered trademark. Copyright^ 1985. MAI and Basic Four are registered trademarks. All specifications are subject to change without notice. BFISD 3196 10/84. ORIGINATOR: MBF SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB001 Pg045 FIB 00002 11/21/84 *** Application Software Security *** A software lock and key feature exists on the 2000 which can be used to control the installation and execution of BASIC software packages. It is used on a per system basis. The "lock and key" feature has seven components: - System Serial Number (SSN) of installation system - Vendor ID (* digits long) - KEYGEN program - Key - Encryption utility or encrypt command - rel program - install program The following procedures are used when implementing the software security procedure: 1. A vendor must assign themselves a Vendor ID. The Vendor ID is an eight character code known only to the vendor. The value or contents of the code is created and maintained by the vendor. The value of the vendor ID must be the same for each application. 2. Create a program (KEYGEN) that generates a "public key" using the System Serial Number (SSN) and the Vendor ID assigned in step 1 above. The key generated from the program must be 8 characters long and only contain the hexadecimal characters 0 - 9 and A - F. This key will be used to install the vendor software in a later step. 3. Select one or more primary programs that are executed by the application. The "primary" programs selected must be executed by the application each time it is run, regardless of options or parameters given by a user. 4. Add a "GOSUB xxxx" in each program selected in step 2. The GOSUB code contains an algorithm using the system serial number and the vendor ID to produce a unique string. The string produced from the algorithm is called the "key". The algorithm used must produce the same key generated in step 2. The GOSUB routine must also compare the key written to disk during the install phase against the key produced from the vendor application. Execution of the vendor application is permitted providing that both keys are identical. 5. Encrypt each program that was selected in step 3. The encryption utility or the encrypt command is used on the programs that contain the added GOSUB routine. The encryption command and utility can only encrypt a program. Once a program is encrypted it cannot be decrypted. It is highly suggested that the vendor save a copy SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB002 Pg001 of the non-encrypted version. 6. The 'rel' command is used to create release diskettes or tapes. After the previous five steps have been completed, and the vendor application is ready to be installed on a customer's system, the 'rel' command is used to copy the files used by the application to tape or diskette for installation purposes. The parameters of the rel command are: Floppy rel/dev/rfdo xxx where: xxx is a unique 3 character product id assigned to the application by the vendor. Examples of BASIC FOUR product ids are EOS, EUT, EBS, etc. Tape rel/dev/rcs/ xxx ... xxxn {tapename=...} {-nappend} where: xxx ... xxxn are product ids tapename is used to label a tape if necessary. -nappend causes a tape to be erased and labeled. (default is to append to the end of the tape without erasing and labeling). The following files are used in conjunction with the 'rel' command. /etc/level/xxx - This file is created by the vendor by executing 'genleve' located in /bin. If security for the product exists the key is placed in the Public id field during the install. The format of the created file is: 1. Creation Date: xx/xx/xx 2. Install Date. xx/xx/xx 3. Release number:xxxxxxx 4. Public id length: 8 5. Public id: xxxxxxx 6. Product Dependencies: 7. Minimum OS level: 8. Short description: 9. Installation procedure file: 10. Ignore path name: /util/fl/xxx.f - A filelist of all the files, with fully qualified pathnames which belong in the xxx product. This list must be created by the vendor. The directory names must also be in the filelist and proceed all the files contained within the specific directories. The 'rel' command verifies that the directories and individual files in the filelist exist. If a directory or file is not found, an error message is issued and the rel command is aborted. The first 3 files in the filelist MUST BE: /etc /etc/level /etc/level/xxx /etc/xxx.I - Installation file procedure. This file is a SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB002 Pg002 optional command file that is executed at installation time. It is used to write the key to disk if security exists for a product. The procedure file must contain the following line if security exists: install key /etc/level/xxx 7. The 'install' command is used to install files from the release tapes or diskette. The 'install' command uses the tape or floppy created in step 6 and transfers the files used by the application to the customer's system. It also updates the /etc/level/xxx file with the public key generated by the KEYGEN program and the system date the application was installed. The parameters for the 'install' command are: Floppy install /dev/rfd0 xxx where xxx is a product id Tape install /dev/rcs xxx ... xxxn where xxx...xxxn are product id(s) The install command first restores all files to the root filesystem and then passes control to the installation procedure, if one exists. The install procedure is the optional command file created prior to executing the 'rel' command ('tmp'xxx.I). If security exists for a product the 'install key' command in the procedure file prompts for an eight character key from the user and writes into the appropriate field in the /etc/level/xxx file. No calculation is made at this point to verify the key created from the KEYGREN program. ORIGINATOR: MBF SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB002 Pg003 FIB 00003 03/07/85 *** Level 7.1A MAGNET and Local Area Network *** This announcement introduces MAGNET 2000 and its Local Area Network capability on Level 7.1A of the MAI^ 2000 System. It is recommended that this document be reviewed prior to the actual installation of the product. The topics covered are as follows: 1.0 Overview 2.0 Requirements 3.0 Installation/Configuration 4.0 Start-up 5.0 Advantages/Limitations 6.0 Files 7.0 Trouble-shooting 8.0 Reference Manual 9.0 For Your Information Please contact Product Support if you have any questions. 1.0 Overview Management Assistance General Network (MAGNET) provides an architecture for the interconnection of MAI systems. MAGNET is initially introduced with its Local Area Network (LAN) capability on the MAI 2000 system. MAGNET 2000 and LAN allows the sharing of information and hardware between multiple 2000 systems in an office, building, or small campus. Although it is in fact a data communications feature it is embedded "transparently" within higher level system services with speeds over 100 times greater than traditional data communications methods. This allows operators and application programs to access remote systems by the same methods and with nearly the same responsiveness as they access their own systems. The local area network concept thus allows the user to expand his configuration and computing services as required, with minimal effect on his existing hardware and applications. LAN on the MAI 2000 allows up to 63 systems (stations) to communicate at speeds up to 1 million bits per second over a low cost, easily installed shared bus wiring system. Use of the bus is negotiated among the stations in microseconds by a Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) method. Each station "listens" for activity on the line before sending data. If a collision should occur, the stations wait a random amount of time before retransmitting. High reliability is assured by automatic error detection and retry, also within microseconds. There are three main functions of MAGNET 2000: Remote SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB003 Pg001 File Access, Remote File Copy, and Remote Command Execution. Record interactive remote file access is provided through the same file management calls used to operate on in-system files. Very little additional overhead is introduced so programs written for single system use can operate on remote files with minimal changes to the application. Bulk copy mode is available through the Remote File Copy Utility. Although its operator interface is nearly identical to that of the standard file copy utility, it is highly optimized for LAN use. The Remote Command Execution utility allows a user at a terminal on a network station to send simple operator commands to another station. The speed of remote execution is nearly the same as in in-system execution of those same commands. All MAGNET 2000 LAN functions are secured in the same manner as the comparable in-system function: by the name of the requesting user, his logon permission, and his file access permissions at the system where the file resides or the command is executed. A remote operation will be permitted if and only if the operation would be permitted to a user of the same name logged on to the remote system directly. 2.0 Requirements Some of the functions of MAGNET 2000 LAN have been incorporated into the 7.1A operating system (i.e. lan remote service manager, /lan/lan rsm). However, in order to have full functionality of the features of MAGNET 2000 and LAN, the LAN product must be installed. The files from this product take up approximately .78 MB on disk. Minimum memory recommended, when running MAGNET 2000 and LAN is 1.25 MB. In addition to the software modules, MAGNET 2000 and LAN require a LAN controller board. This board fits in the enclosure of the 2000 system and handles the lower level control of transmitting and receiving data, including line negotiation, error detection and retransmission. The LAN controller board contains a switch which can be set to control network bias and to set the hardware address of the station. The LAN controller board has a connector which connects a 15' drop cable from the system to the LAN trunk cable. The trunk cable is a twisted pair of wires which maintains the physical connection between the stations on the LAN network. The connection of the drop cable to the trunk cable is made using a tap box. The tap box is a plastic box which contains screws to connect the wires from the drop cable to the trunk cable. The installation of the tap box can occur anywhere along the trunk cable. There is however, a limitation of 4000' total of trunk cable allowed on any one LAN network. A network repeater is required to amplify and carry network signals when the trunk cable is greater than 1000' or when there are more than 32 stations on a 1000' segment. The repeater requires a grounded power outlet. The LAN controller board, drop cable, trunk cable, tap box and repeaters are all available through MAI Basic Four. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB003 Pg002 In order to install a MAGNET 2000 LAN network, the following tools are required by the installer: a wire stripper, 1/8 inch wide flat blade screwdriver, and a knife. A network manager should be assigned to map out a physical layout of the network. A list containing the unique station addresses (01 - 63) for each system must be made available so that the addresses may be set on the LAN controller board. For full installation information, refer to BFISD 6351 titled, "MAGNET 2000 Local Area Networking". 3.0 Installation/Configuration The following procedures must be followed to ensure a proper MAGNET 2000 LAN connection and operation. 3.0.1 Assign one person to act as Network Manager. This person will plan the installation and coordinate all hardware and software installation. He will also assign and keep track of all station addresses and ensure that stations are properly configured, on a ongoing basis as modifications and upgrades to the network are needed. 3.0.2 Plan the physical layout of the network. A map must be drawn denoting the location and address of each station, the locations of tapboxes and repeaters, and the routing of the bus cable. Consideration should be made for possible later expansion, as well as initial installation. Note that repeaters need to be near a power outlet. 3.0.3 Assign unique station addresses, between 01 and 63, to each station. 3.0.4 Have a service representative install the physical components of the network, according to the map. Assure that each LAN controller is set to the correct station address and has correctly set, the switches for network bias and network termination. There are two ways to terminate the network: through the use of a switch on the LAN controller board or through the use of a resister in the terminating tap boxes. There are two sets of dip switches on the LAN controller board, SW1 and SW2. SW2 should already be set, as follows, when the board is shipped to the customer site and should not be touched. SW2 SWITCH SETTINGS 1 - OFF 2 - OFF 3 - OFF 4 - ON 5 - ON 6 - OFF 7 - ON 8 - OFF SW1 is initially set to all OFF when purchased. This is the address switch and must be set at each station with a unique station number between 01 to 63. SW1 also contains switches for the network bias and termination. Position 1 on SW1 is the network bias switch. One and SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB003 Pg003 only one station on the network should have this position set to OFF. All other stations should have this position set to ON. Position 2 on SW1 is the termination switch. If resistors are used in the tap boxes to terminate the trunk cable, then this position should be OFF on all network LAN boards. If the resistors in the tap boxes are not used, then this position on the terminating systems must be set to ON. Position 3 through 8 are used to set the address for the station. Station addresses may range from 01 to 63 but each station on the network must be assigned a unique address. SW1 Positions 3-8 _ _ _0 = off 1 = on _ _ _ _ _ MINISWITCH __ _ MINISWITCH _ _ NETWORK _ POSITION __ NETWORK _ POSITION _ _ ADDRESS _ 3 4 5 6 7 8 __ ADDRESS _ 3 4 5 6 7 8 _ _ _ __ _ _ _ _ __ _ _ _ 00 _ Reserved __ 32 _ 0 1 1 1 1 1 _ _ 01 _1 1 1 1 1 0 __ 33 _ 0 1 1 1 1 0 _ _ 02 _1 1 1 1 0 1 __ 34 _ 0 1 1 1 0 1 _ _ 03 _1 1 1 1 0 0 __ 35 _ 0 1 1 1 0 0 _ _ 04 _1 1 1 0 1 1 __ 36 _ 0 1 1 0 1 1 _ _ 05 _1 1 1 0 1 0 __ 37 _ 0 1 1 0 1 0 _ _ 06 _1 1 1 0 0 1 __ 38 _ 0 1 1 0 0 1 _ _ 07 _1 1 1 0 0 0 __ 39 _ 0 1 1 0 0 0 _ _ 08 _1 1 0 1 1 1 __ 40 _ 0 1 0 1 1 1 _ _ 09 _1 1 0 1 1 0 __ 41 _ 0 1 0 1 1 0 _ _ 10 _1 1 0 1 0 1 __ 42 _ 0 1 0 1 0 1 _ _ 11 _1 1 0 1 0 0 __ 43 _ 0 1 0 1 0 0 _ _ 12 _1 1 0 0 1 1 __ 44 _ 0 1 0 0 1 1 _ _ 13 _1 1 0 0 1 0 __ 45 _ 0 1 0 0 1 0 _ _ 14 _1 1 0 0 0 1 __ 46 _ 0 1 0 0 0 1 _ _ 15 _1 1 0 0 0 0 __ 47 _ 0 1 0 0 0 0 _ _ 16 _1 0 1 1 1 1 __ 48 _ 0 0 1 1 1 1 _ _ 17 _1 0 1 1 1 0 __ 49 _ 0 0 1 1 1 0 _ _ 18 _1 0 1 1 0 1 __ 50 _ 0 0 1 1 0 1 _ _ 19 _1 0 1 1 0 0 __ 51 _ 0 0 1 1 0 0 _ _ 20 _1 0 1 0 1 1 __ 52 _ 0 0 1 0 1 1 _ _ 21 _1 0 1 0 1 0 __ 53 _ 0 0 1 0 1 0 _ _ 22 _1 0 1 0 0 1 __ 54 _ 0 0 1 0 0 1 _ _ 23 _1 0 1 0 0 0 __ 55 _ 0 0 1 0 0 0 _ _ 24 _1 0 0 1 1 1 __ 56 _ 0 0 0 1 1 1 _ _ 25 _1 0 0 1 1 0 __ 57 _ 0 0 0 1 1 0 _ _ 26 _1 0 0 1 0 1 __ 58 _ 0 0 0 1 0 1 _ _ 27 _1 0 0 1 0 0 __ 59 _ 0 0 0 1 0 0 _ _ 28 _1 0 0 0 1 1 __ 60 _ 0 0 0 0 1 1 _ _ 29 _1 0 0 0 1 0 __ 61 _ 0 0 0 0 1 0 _ _ 30 _1 0 0 0 0 1 __ 62 _ 0 0 0 0 0 1 _ _ 31 _1 0 0 0 0 0 __ 63 _ 0 0 0 0 0 0 _ _ _ __ _ _ 3.0.5. Install the Local Area Network (LAN) product on each system. To install from tape: SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB003 Pg004 ADMIN> install cs LAN To install from floppy: ADMIN> install fd LAN 3.0.6 At each station, configure the LAN. The system must be in multi-user mode. Access the LAN configuration utility from either the communications utility menu or by typing in command mode: @>/lan/lan util The LAN configuration utility is used to define the LAN interface for the station and define names and addresses for all other stations it must access in the network. 3.0.7 When all stations are connected and configured, use a utility called "lanpoll" from command mode to assure that its access to each other station is as intended. Lanpoll is also useful in determining if there is a break in the LAN trunk connection. To request a help menu for the lanpoll utility, type in command mode: @>lanpoll -h 3.0.8 At each station, establish operator identifications for each user who must access that station through the network. A user must be identified by the same name at all stations he must access, although his password and privileges may vary from station to station. Conversely, different LAN stations should not use the same operator name for different persons, since LAN assumes the same name implies the same person. 4.0 Startup The LAN communication facilities are started by the LAN configuration utility, and are subsequently restarted automatically whenever a station enters multi-user mode. LAN communication is stopped whenever a station shuts down multi-user mode. LAN features may also be explicitly shut down by the LAN configuration utility. LAN Remote File Access is available at any time from a station with LAN enabled to any station with LAN and Remote File Access enabled. Minor changes to application programs may be necessary to identify fully qualified file names which include the station name on which the remote file resides. For example, to access a file named "sales" on the marketing station, the open statement of a BASIC program may have to be modified to OPEN (1) "/sta/marketing/sales". LAN Remote Command Execution is available at any time from a station with LAN enabled to any station with LAN and Remote Command Execution Enabled. Commands which require operator input, such as ved and menus, are not supported by the Remote Command Execution utility. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB003 Pg005 5.0 Advantages/Limitations The MAGNET 2000 Local Area Networking product allows for the sharing of resources between systems, within limits. The pre-dominant limits are the capacity of an individual station, and the overhead of remote operations. The LAN overhead currently restricts any single system to fewer than about 12 remote access requests per second. The capacity of an individual station may easily become the limiting factor if it is the residence of a data base which is heavily accessed from other stations. The LAN allows more programs to access a shared disk, but it does not make the disk any faster. A LAN is most effectively used by a set of applications which make only light to medium use of a central data base, and can maintain separate copies at each station of any heavily accessed files. Heavier use of shared files can sometimes be tolerated if the shared files are distributed among several stations, rather than concentrated on a single station. Advantages o maximum of 63 stations in a network o shared resources (hardware and software) o remote file copy/access o remote command execution o versatile layout of stations o high speed data exchange rate o inexpensive and easy to install o passive controllers - if system goes down, other network users not affected o file and system access privileges o LAN event reporting and monitoring capabilities Limitations o 4000 feet total network length o 3 repeaters maximum on network o degradation of response time if heavy use of network and/or any single station in network o not all commands are supported by the remote command execution utility (e.g. ved, menus, operations which require operator input) 6.0 Files The following files are required to run Local Area Network: /lan/conf table remote access configuration data base /lan/evtmsg.ind LAN event log text /lan/evtmsg.txt LAN event log text /lan/lan evtmtor event monitor program /lan/lan init LAN initiation program /lan/lan rcmds remote command interpreter program /lan/lan rcopy remote file copy utility program /lan/lan rcs remote command server program /lan/lan rcx remote command utility program /lan/lan rfc remote file copy server program /lan/lan rfs remote file access server program SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB003 Pg006 /lan/lan rsm remote service manager program /lan/lan util LAN configuration utility /lan/lanmsg.ind LAN utilities text /lan/lanmsg.txt LAN utilities text /lan/lanpoll LAN network status report program /lan/sif remote service manger data base 7.0 Trouble-shooting A utility called lanpoll is included with the LAN package to allow a user to monitor the status of systems on the network. Execute lanpoll in command mode. Using the -help option will display an explanation of the options and the interpretation of the status. Lanpoll is an excellent tool to use when there are suspected problems with the network. Another tool which is useful in case of suspected network failures is the LAN Event Log. Since event logging requires some overhead, monitoring of events should be activated only when problems start occurring. 8.0 Reference Manual For detailed information on how to use LAN, please refer to BFISD 6351, "Local Area Networking". 9.0 For Your Information The following list is provided for your information so that any known problem areas of the Local Area Network package can be avoided. These problems are applicable to Level 7.1A and will be addressed in a future release. 9.1 Executing "login" using /lan/lan rcx causes /dev/null on the remote system to lose the Read/Write access permissions. Work-around: Do not attempt "login" with /lan/lan rcx. 9.2 /lan/lan rcx receives a time out error if a command is not specified in the command line. Work-around: Always specify a command when option -c is used. 9.3 A remote copy of a large direct file (over 50,000 bytes) may generate an error -538. Work-around: Attempt the copy again, preferably with a lighter system load. ORIGINATOR: MBF SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB003 Pg007 FIB 00004 03/07/85 *** Batch Communications Emulator *** This announcement introduces the Batch Communications Emulator for the MAI^ 2000 System. It is recommended that this document be reviewed prior to the actual installation of the product. The topics covered are as follows: 1.0 Overview 2.0 Requirements 3.0 Installation/Configuration 4.0 Start-up 5.0 Advantages/Limitations 6.0 Files 7.0 Trouble-shooting 8.0 Reference Manual 9.0 For Your Information Please contact Product Support if you have any questions. 1.0 Overview The Batch Communications Emulator provides an easy to use, menu driven utility to transmit and receive files between Basic Four and non-Basic Four systems which support the IBM 2770/2780/3770/3780 bisynchronous protocol. This package is functionally composed of two components: the emulator utilities and the drivers. The emulator utilities on the MAI 2000 are written in C, as opposed to BASIC on the other Basic Four systems. Functionally, however, the user interface is identical, with a few minor changes, to the Batch Communications Emulator on the Basic Four 8000, 13xx, S/80, and S/10 systems. A user who is familiar with the package on these systems should be able to easily adapt to the emulator utilities on the 2000 system. The drivers utilized by the Batch Communications Emulator consist of a bisynchronous line driver and a 27xx/37xx device driver, both of which are written in C. The line driver is a general purpose driver which can be used in the future for other bisynchronous applications, such as 3270 interactive communications. The device driver controls the characteristics of the various 27xx/37xx terminal types (i.e. buffer size, compression, etc.). 2.0 Requirements Unlike the other Basic Four systems, the MAI 2000 does not require an IMLC communications controller board to run the Batch Communications Emulator. The second serial port on the central microprocessor board (CMB) SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB004 Pg001 can be strapped as a synchronous port. A standard CMB cable is used to connect a modem or a modem eliminator to the port. As with previous systems, the 2000 will expect external clocking to be provided by the modem or the modem eliminator. The Batch Communications Emulator requires a minimum of 1.25 MB of memory on the system to run in stand-alone mode. 1.5 MB of memory is required for the emulator to run concurrently with up to four other tasks. The programs and data files take up approximately 1200 sectors on disk. This package must be run in multi-user mode as it is strongly dependent on the execution of the remote service module, /lan/lan rsm. To ensure that lan/lan rsm is started in multi-user mode, /lan/lan init must be executed as part of the multi-user startup procedure (/etc/startup). 3.0 Installation/Configuration The following procedures must be followed for the Batch Communications Emulator to operate successfully. 3.0.1. Install the EBC package once the 2000 Operating System has been installed. To install from tape, type: ADMIN> install cs EBC To install from floppy, type: ADMIN> install fd EBC During the installation process, a prompt will display requesting a public key for EBC. This key is unique to the system serial number of the system and is written on the product certificate which accopanies the EBC floppy or tape. If a public key does not exist, call an authorized key generation location. It is important to note that EBC requires an operating system called Cunos. During the installation of the product, Cunos is restored to the boot partition, overriding the existing operating system, unos. Cunos is renamed as unos at that time. A copy of Cunos is also resident in the root partition in the /sys directory. If, for any reason, the operating system from the base tape is re-installed, then Cunos must be manually copied and renamed as unos in the boot partition. 3.0.2. On 7.1A, the Batch Communications Emulator may be run only on the second port of the central microprocessor board (CMB). This port must be strapped for synchronous communications. CMB Serial Port 1 (Part # 903441-001) JUMPER SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB004 Pg002 B 1-2 G 15-16 B 3-4 G 17-18 B 7-8 G 19-20 B 9-10 G 23-24 B 13-14 H 1-2 B 15-16 K 1-2 CMB Serial Port 1 (Part # 903441-002) Pin 1 of zero-ohm-pack is in pin 1 of socket B Pin 1 of zero-ohm-pack is in pin 1 of socket K Nothing in sockets G and H 3.0.3. A standard CMB to serial device cable must be connected from port 1 to the synchronous modem or modem eliminator. 3.0.4. The port configuration utility (configure) must be run in single user mode. Port 1 must be "Not Configured" to run synchronous communications. 3.0.5. In order to run the Batch Communications Emulator concurrently with up to four other tasks, the following changes to the system configuration on the boot partition (/etc/conf) are recommended. a. Type "mount /dev/boot /mnt" b. Type "cd /mnt/etc" c. Type "copy conf conf.sav" d. Type "vconf -save conf lanbuffers= 8 procs=48 lus=192 opens=128 buffers=8" e. Type "cd /" f. Type "unmount /mnt" g. Shutdown and re-boot the system. 3.0.6. Multi-user mode must be started so that /lan/lan rsm is executed. 3.0.7. Execute the Batch Communications Emulator from command mode, menu mode, or a user program. 4.0 Startup There are three utilities which comprise the Batch Communications Emulator product - the emulator itself, the Local Status Check utility, and the JCL record generation utility. Each utility may be accessed via the communications submenu from the main utilities menu. In addition, the utilities may be accessed in command/console mode. The Batch Communications Emulator is the user interface to the facility which allows the transfer of files between systems. It is through this utility that the user can customize his sessions by selecting and saving the parameters for a particular session in an autoprompt file. In command mode, this utility is accessed by typing: @>bcom Alternately, the Batch Communications Emulator may be run from a defined BASIC program. Provided that an SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB004 Pg003 autoprompt has been previously saved with the proper options for a given session, the user may insert in his BASIC program an EXEC statement with the following parameters: 1000 PREFIX "/util" 1010 EXEC "!bcom autoprompt N/Y T/G num" where autoprompt = autoprompt name N/Y = N for no operator intervention Y for operator intervention T/G = T for terminal task (foreground) G for ghost task (background) num = "Line Connection Pending" timeout in HHMMSS format The Local Status Check utility allows the user to display a history of status messages that are generated by the Batch Communications Emulator during a communications session. This utility is useful to verify whether a session which may have been run in background or unattended mode, was successful or not. If the session was abnormally terminated, then status messages denoting the problem will also be displayed. To access the Local Status Check utility, select the option from the communications menu or type in command mode: @> lslog The JCL Record generation utility provides an easy method for an operator to create card images of Job Control Language (JCL) required by many mainframes. The utility will allow for the generation of records in EBCDIC or in ASCII. The JCL Record generation utility may be accessed from the communications menu or from console mode in BASIC. @>cd /util @>basic >RUN "UJCL" 5.0 Advantages/Limitations As with many data communication products, the 27XX/37XX Batch Emulation Package on the 2000 system has its advantages and limitations. Listed below are just a few items which should be noted. Items listed under "Limitations" are applicable for release 7.1A and may not necessarily apply on future releases. Advantages o industry standard protocol o support of modem eliminators, switched and leased lines o multi-system hookup to other Basic Four^ and non Basic Four systems o utility set similar to other Basic Four systems (data integrity due to error recovery of the bisynchronous protocol) o transmission of all BASIC file types (Index, Serial, Direct, Sort, Program) between Basic Four systems o interface to the Batch Queuer utility of the Intersystem Transfer Package SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB004 Pg004 o spooling/despooling of received files not necessary Limitations o automatic calling unit (ACU) not supported by hardware or software o second port on the CMB is the only port allowed to run 27XX/37XX o 27XX/37XX through a Local Area Network not supported o most effective throughput at 2400/4800 baud o may notice system degradation running concurrently with more than 4 tasks o 3K record size limit for serial file transmissions, 2K record size limit for all other file types o Transparency and File Transfer modes are not supported with the ASCII line code. 6.0 Files The following files are required to run the Batch Communications Emulator. These files are restored to the hard disk from the EBC product tape during installation. /sys/scs Synchronous Communications Server /sys/b2780 Batch Communications Device Driver /sys/bsci Line Driver Interface /sys/Cunos Communications Operating System /util/bcom Batch Communications Emulator utility /util/lslog Local Status Log utility /util/ebc mess BCOM message file /util/ebc ind BCOM message file /util/UJCL JCL Record Generation utility When the Batch Communications Emulator is initially run, the following files are generated by the emulator. /etc/comm/capfl Autoprompt file /etc/comm/xmtq Transmit Queue file /etc/comm/rcvq Receive Queue file /etc/comm/signfil Signon File /etc/comm/lstat Local Status Log /etc/comm/trncd Translation Table 7.0 Trouble-Shooting Due to the many external interfaces which are involved in a communications session, it is imperative that each separate component be properly checked out. The phone lines should be tested by the phone company at installation and at any time when the quality of the phone lines are in question. Modem vendors should be asked to run self tests and loopback tests on their equipment. Instructions on how to run these tests should also be provided to the customer for future use. The 2000 system should be verified that the software and the hardware are installed and configured correctly. The remote system should also be checked and verified that the communication parameters are compatible to the 2000 system setup of the Batch Communications Emulator. A use of a datascope is always helpful in isolating protocol problems. In addition, the following may help isolate problems SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB004 Pg005 encountered during an attempted communications session. o "ERR -808 Bad Public Key" message displayed when Start Communications option selected. The public key for the system was not input correctly during the installation of the EBC product. Verify that a product certificate containing a public key for EBC was received with the media for the EBC product. If the public key is not documented, then obtain the key from an authorized location. Once the key has been obtained, either re-install the EBC product and input the correct key when prompted, OR, ved the /etc/level/EBC file and edit the public key field with the correct public key for the system. o "ERR -300 Error Starting Server" message displayed when Start Communications option selected. Verify that /lan/lan rsm has been started in multi-user mode. o "ERR -809 Bad Kernal Line Driver" message displayed when Start Communications option selected. Verify that the correct operating system is installed in the boot partition. /sys/unos on the boot partition should be identical in size to the /sys/Cunos in the root partition. If not, re-install the EBC product. o No Data Terminal Ready (DTR) on modem when Start Communications option selected. Verify that the hardware strapping on the CMB is for synchronous communications. Verify also that the CMB cable is functional by testing it out on a terminal on the CMB port 0. Verify that the modem DTR light is not burned out. o "Line Bid Not Acknowledged" message while attempting to transmit file. Verify the line code option on both systems are compatible. Verify the port strapping on the CMB port 1 is for synchronous communications. Verify that both modems are functional by running self/remote loopback tests. o "Receive Timeout" messages continually displays but files in the transmit queue are not transmitted. Verify that the "remote first" option is not selected with the "transmit priority" option under Terminal Definition in the autoprompt file. 8.0 Reference Manual For further information, please refer to BFISD 6353B titled, "Batch Communications User's Guide for the 2000 System." SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB004 Pg006 9.0 For Your Information The following list is provided for your information so that any known problem areas of the Batch Communications Emulator can be avoided. These problems are applicable to Level 7.1A and will be addressed in a future release. 9.1 When running the Batch Communications Emulator concurrently with other tasks, if a user logs off a terminal, the Batch Communications Emulator session will abort. Work-around: Run the Batch Communications Emulator in stand alone mode or alert other users on the system to not log off during a communications session. 9.2 Transmitting string files in File Transfer mode generates Error 17 on the transmitting system. String file transmission in Text or Transparent mode is also not supported. Work-around: Do not attempt to transmit string files via the Batch Communications Emulator. 9.3 The Batch Communications Emulator suspends on the receiving system if the transmitting system sends a File Transfer file and selects to change the name of the file, to be received, without specifying the directory. Work-around:hEither do not rename the transmitting file or always specify the directory and the file name.. 9.4 On a very infrequent basis, the Batch Communications Emulator sessions may encounter premature terminations or session "hangs". The occurrence is rare but can happen under various conditions, such as system load or remote system hangs. Work-around: It may be necessary for the operator to kill any processes associated with the Batch Communications Emulator (bcom). Then, restart the session. ORIGINATOR: MBF SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB004 Pg007 FIB 00005 03/07/85 *** Asynchronous File Transfer package *** This announcement introduces the Asynchronous File Transfer Package on Level 7.1A of the MAI^ 2000 System. It is required that this document be reviewed prior to the sale and installation of the product. The topics covered are as follows: 1.0 Overview 2.0 Requirements 3.0 Installation/Configuration 4.0 Start-up 5.0 Advantages/Limitations 6.0 Files 7.0 Trouble-shooting 8.0 Reference Manual 9.0 For Your Information Please contact Product Support if you have any questions. 1.0 Overview The Asynchronous File Transfer Package (ATP) provides an inexpensive and effective method of transmitting files between the MAI^ Basic Four 8000, 13xx, S/10, and 2000 systems. Since ATP is designed for intersystem use, it is written in BASIC and has the same functionality and user interface on all systems. ATP is easy to use and is capable of transporting all BASIC file types (i.e. index, serial, sort, direct, and program) with verification that the file is received accurately. For transmission to systems with an unlike ASCII character set, ATP can be used in conjunction with the Batch Queuer (BQR) portion of the Intersystem Transfer Package (ITP). 2.0 Requirements ATP allows the transfer of files to local as well as remoted systems through an asynchronous terminal port, available on all MAI^ Basic Four systems. On the 2000 system, this port must be strapped as a standard terminal port, if the connection is local. A standard CMB or 4-Way cable may be used to connect the port to a terminal cable on the other system. In order to connect the two male cable ends, a user supplied female-female connector with pins 2 (transmit) and 3 (receive) crossed is required. Alternately, a single cable with pins 2 and 3 crossed may be used from one system's serial port to the other system's serial port. If the connection is to be remoted through modems, the SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB005 Pg001 2000 terminal port must be strapped as a modem port. A standard CMB or 4-Way cable will then be connected to an asynchronous modem. In addition to the communicating port, a started terminal and operator intervention is required to run the ATP utility. ATP is run in BASIC and should be started with 128 pages on the 2000 and 13xx systems for maximum performance. The files associated with ATP take up approximately 83 sectors on disk. 3.0 Installation/Configuration The following procedures must be followed for ATP to successfully transmit and receive files. 3.0.1. After the Operating System has been installed on the 2000, install the EIT (Intersystem Transfer) product. ATP files will be installed along with the Intersystem Transfer files. To install the EIT product from tape, type: ADMIN> install cs EIT To install the EIT product from floppy, type: ADMIN> install fd EIT 3.0.2. An asynchronous serial port must be strapped as a terminal or modem port, depending on the connection. Ports on the 4-Way are strapped differently than on the CMB. Also, different revision levels of the 4-Way & CMB are strapped differently. CMB Serial Port 0 (Part # 903441-001) Terminal JMP A: 1-3, 2-4, 5-6, 7-9, 8-10, 11-13, 12-14 Modem JMP A: 1-2, 3-4, 7-8, 9-10, 11-12, 13-14 CMB Serial Port 1 (Part # 903441-001) Terminal JMP B: 1-3, 2-4, 5-6, 7-9, 8-10, 13-15, 14-16 JMP G: 15-16, 17-18, 19-20, 23-24 JMP K: 1-2 Modem JMP B: 1-2, 3-4, 7-8, 9-10, 13-14, 15-16 JMP G: 15-16, 17-18, 19-20, 23-24 JMP K: 1-2 CMB Serial Port 0 (Part # 903441-002) Terminal Pin 9 of zero-ohm-pack is in pin 1 of socket A Modem Pin 1 of zero-ohm-pack is in pin 1 of socket A SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB005 Pg002 CMB Serial Port 1 (Part # 903441-002) Terminal Pin 9 of zero-ohm-pack is in pin 1 of socket B Pin 1 of zero-ohm-pack is in pin 1 of socket K Nothing in sockets G and H Modem Pin 1 of zero-ohm-pack is in pin 1 of socket B Pin 1 of zero-ohm-pack is in pin 1 of socket K Nothing in sockets G and H 4-Way Controller Board (Part # 903390-001) Signal Terminal Modem DSR 3-4 3-4 DTR 1-7 1-2 CTS 2-8 7-8 RTS 9-10 9-10 RXD 13-15 13-14 TXD 14-16 15-16 4-Way Controller Board (PCB Detail 904943-001) Signal Terminal Modem DSR 1-3 3-4 DTR 2-4 1-2 CTS 9-11 9-10 RTS 10-12 11-12 RXD 13-15 13-14 TXD 14-16 15-16 3.0.3. If the hook-up is remote, the communicating port must be strapped as a modem port. A standard 2000 CMB or 4-Way cable is connected to an asynchronous modem. 3.0.4. If the hook-up is local, then the communicating port is strapped as a terminal port. A standard 2000 CMB or 4-Way cable may be used with a user-supplied female-female connector to connect to the cable of the other system. If the cable on the other system is a modem cable, then the connector should have the following configuration: _ _ _ 2 ------------- 2 _ _ 3 ------------- 3 _ _ 4 -- -- 4 _ _ _ _ _ _ 5 -- -- 5 _ _ 7 ------------- 7 _ _ _ If the cable on the other system is a terminal cable, then the connector should have pins 2 and 3 crossed. _ _ _ 2 ------------- 3 _ SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB005 Pg003 _ 3 ------------- 2 _ _ 4 -- -- 4 _ _ _ _ _ _ 5 -- -- 5 _ _ 7 ------------- 7 _ _ _ 3.0.5. Run the port configuration utility in single user mode. This utility can either be accessed from the utilities menu or from command mode by typing: ADMIN> configure Configure a port as a terminal (evdt) with no start process defined. To do this, simply select the Start Process option (option 4), type in a blank, and carriage return. The default start process for terminals will be removed. This port will be the "communicating port". Configure also, another terminal port which will be used to run the ATP utility. The characteristics of this port will depend on the terminal used. Save the configuration and reboot the system. 3.0.6. Go into multi-user mode. 3.0.7. Select the Asynchronous File Transfer option from the Intersystem Transfer submenu or in BASIC run ATP and specify the transmitting and receiving stations. 4.0 Start-up ATP can be accessed via the Intersystem Transfer option of the main utilities menu. ATP can also be accessed in command/console mode by typing: @> cd /util @> basic s=128 > RUN "ATP" The ATP program will first prompt the user if this system is to transmit or receive data. Unlike the features of the Batch Communications Emulator, ATP initially requires the operator to specify whether the system will be transmitting files or receiving files. The receiving system will, however, have an opportunity to transmit messages after the receipt of each file through an operator intervention option. The line protocol used by ATP is similar to that of 27xx/37xx in that it includes error detection, retransmission, line-turnaround, breakpoint and restart logic. 5.0 Advantages/Limitations There are advantages of using ATP over some of the other intersystem and intrasystem means of transporting files. Some of the features of ATP are listed below. There are also some limitations to be aware of and those are also listed. Each user must study his requirements and resources to determine which transport mechanism will best suit his application. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB005 Pg004 Advantages o standard protocol and user interface across MAI^ Basic Four, Inc. product line (8000, 13xx, S/10, 2000) o error detection and retransmission o remote and/or local file transfer o baud rates of 1200 - 9600 Bits per Second (BPS) o on-line with multiple users o inexpensive o may send messages or add files during transmission o breakpointing implemented for restart logic o interface to the Batch Queuer utility of the Intersystem Transport Package Limitations o 30% overhead per character (characteristic of async) o time-consuming on large files o requires two ports per system o remote operations usually at 1200 bps (Bell 212A equivalent modems most popular) o cannot use system filelist as transmit queue o supported between Basic Four^ systems only 6.0 Files The following files must reside in /util in order for ATP to operate: ARCV Asynchronous Receive Program ARP Asynchronous Receive Program ATP Asynchronous Transmit Program ATP1 Asynchronous Transmit Program ATRCV Line Receive Program ATXMT Line Transmit Program FILDIR Directory of filelist names 7.0 Trouble-shooting The following areas should be verified if files are not being transmitted/received. o Verify that the terminal port configured as the communicating port does not have a start process defined. o Verify that the terminal port configured as the communicating port has been properly strapped. If the link is local to the 2000, the port should be strapped for a terminal. If the link is remoted through modems, the port must be strapped for a modem. o Verify that if the link is local, the transmit and receive pins (2 and 3) are crossed. o Verify that the baud rates on the communicating ports are compatible. 8.0 Reference Manual For further information, refer to the ATP chapter of SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB005 Pg005 BFISD 6354, titled "Intersystem Transport Package". 9.0 For Your Information The following list is provided for your information so that any known problem areas of the Asynchronous File Transfer package can be avoided. These problems are applicable to Level 7.1A and will be addressed in a future release. 9.1 Program file transfers between 2000 systems may generate an Error 41 on the receiving system. Work-around: When transmitting program files, first convert them to a serial file on the transmitting system. ORIGINATOR: MBF SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB005 Pg006 FIB 00006 05/15/85 *** BOSS/IX Release 7.1B Software Announcement *** 1.0 Introduction Level 7.1B of BOSS/IX~ is now available. 7.1B contains several enhancements and corrections and is the recommended operating system level for the MAI^ 2000 system. 2.0 Installation and Upgrade Procedures The installation and upgrade procedures for the 7.1B software release are the same as mentioned in the 7.1A software announcement. Refer to the 7.1A software announcement for instructions if necessary. See section 4.0, "For Your Information", for warnings on upgrading. 3.0 Corrections to 7.1B o EOS - Fixed problem with rewrites or deletes of duplicate secondary keys used within the COBOL (CBR) and INFORMIX (EDB) packages. - Correction was made to terminal character set to include the support of the business graphics characters. - Corrected problem of numerous extracts on a locked file causing an error 33. o EBS - Corrected problem with MERGE so that now 'END' and 'end' are recognized as terminators. - The variable TCB(7) and the active SETERR statement is reset when going from a CALLed program to the CALLing program. - Corrected error 10 problem on opnes, when using position 35 to end of FID of file to be opened. - Corrected problem of doing a remove on an empty file causing it to be corrupted. o EIT - Fixed cwrite to properly handle large data files and empty program files. - Fixed cread to properly handle a large number of program files. o EBC - The logoff problem has been corrected. 4.0 For Your Information o EOS - If the OS is upgraded using the 'osupdate' command the printers will output garbage. Workaround: After upgrading the OS on the root partition, execute the '/sys/installetc' program and copy the '/tmp/etc/ptrans' file. - Overstrike on the printer, while in output transparency, is causing a premature line feed. Workaround: None. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB006 Pg001 o EBS - Extracting and reading a record within a locked file does not release the lock. Numerous extracts may generate error 33's. Workaround: 1. Do not use EXTRACT within a locked file. 2. Increase the maximum number of locks allowed on the system using the '/bin/vconf' command. - Error 20's are generated on IF statments that have parens "( )" before the equals "=". Example: 20 IF (A+B)=C THEN... Workaround: Move calculation etc. to another statement and assign it to a single variable. Example: 10 X=A+B 20 IF X=C THEN... - Error 20's are generated on IF statments that use an "S" variable name just before the else clause. Example: 10 IF A=B THEN LET B=S ELSE... Workaround: Change the "S" to any other variable name. - Unable to erase or create files from second or third etc. directories of a prefix list. Workaround: In order to create or erase files from the second etc directory use the full path name. Example: 10 PREFIX "/USR/UTIL /SYS" 20 ERASE "/UTIL/FILENAME" 5.0 Enhancements contained 7.1B 5.1 7.1B Sheet Feeder Mnemonics Two new mnemonics have been added. They provide a mechanism to retrieve paper from one of two bins on a BDT cut sheet feeder attached to a Diablo printer. These mnemonics are: 'B1' and 'B2'. The functional characteristics of these mnemonics are as follows: o When an application opens a Diablo printer with a sheet feeder attached, a form feed should be issued to make sure the mechanics of the feeder are in a neutral state. o 'B1' causes the paper to be fed from bin 1 - the bin at the front of the printer. o 'B2' causes the paper to be fed from bin 2 - the bin at the back of the printer. o The application must issue a form feed at the end of every page to cause the paper to feed into the out-tray. o Bin feed is not affected by 6 or 8 lines per inch settings in the '/etc/forms' file or by the '6L' or '8L' mnemonics, as long as lines per inch are not mixed within a single page. Doing so may prevent the paper from feeding completely into the out-tray. If mixed lines per inch is desired, then the application needs SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB006 Pg002 to output two form feeds at the end of every page. o The bin feed mnemonics can be used through the despooler. The despooler will not automatically add bin feed mnemonics to the data at print time. The bin feed mnemonics must already be present in the data. o An application that bypasses the spooling system still has access to the bin feed mnemonics when printing directly to the printer. o The bin feed mnemonics are ignored by all non-Diablo printers, unless the begin error 29 generation mnemonic ('BG') is issued prior to the bin feed mnemonics. o The system will not automatically feed paper from a bin if the application prints beyond the defined length of the page. o The command language will not automatically add bin feed mnemonics to the Diablo printer with a sheet feeder. o Applications that use the sheet feeder functionality and the despooler, should specify a form that has a unique name. That way the user will be reminded by the despooler to change forms as per print job requirements. o The use of the bin feed mnemonics will most likely cause a paper jam on a Diablo with a (continuous form) tractor feed. 5.2 System shutdown The 7.1A and 7.1B software releases contain an undocumented option, "-r", in the '/bin/shutdown' command. This option brings the system directly to the reboot prompt from multi-user mode, Example: ADMIN>shutdown 0 -r 6.0 Lowest Acceptable Revision Levels (LARL) The following chart lists the LARL of each PCB on the MAI 2000. PCB Part Number LARL CMB, Central Microprocessor Board 903441 AF 256K Memory 903368 A 4 - Way Controller 903390 P MCS Controller 903406 L LAN Controller 903405 D WDC WinchesterAdapter Board 903439 B Power Supply Input Module 903443 D Power Supply Control Module 903394 A Power Supply Output Module 903445 F Adaptec Board 907649 C SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB006 Pg003 Power Supply Assembly 907472 E Diskette Disk Drive 907584 A Winchester Disk 50MB 400549 A 1 Board Winchester Disk Controller 903496 D Winchester Disk 140MB 907790 A ORIGINATOR: MBF SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB006 Pg004 FIB 00007 01/30/86 *** Error 0 (File System Error -62) on serial printers - release 7.1 *** SYMPTOM: The problem occurs in multi-user mode when a terminal is running a print job and another terminal signs off. The terminal running the print job gets an ERROR 0. If the directive Error is typed at this point, the system returns File System Error Code: -62. The problem only occurs when the printer is configured as a non-spooled printer. FIX: The following work-around is suggested until Basic Four corrects the problem on the next Operating System release. 1. Use the utilities to configure the printer with spooling. 2. Use the option OPTS="-off" in the OPEN statement on print jobs when spooling is not desired. Example: 0010 OPEN (1,OPTS="-off")"LP" ORIGINATOR: J. VAN OORDT SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB007 Pg001 FIB 00008 03/26/86 *** MCS backups MUST be done in single user mode *** SYMPTOM: Data files restored from backup tapes created in multi-user mode contain corrupted data. PROBLEM DETERMINATION: Files that have been opened and had information in them updated, may be saved to the tape as corrupted files. This is because the header information in the file is not usually updated until that file is closed. FIX: Do all backups in single user mode only. ORIGINATOR: J. VAN OORDT SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB008 Pg001 FIB 00009 04/07/86 *** Error -2 and Error -62 during MCS backup/restore - release 7.1A/B *** SYMPTOM: ERROR -2 and/or ERROR -62 while running MCS backup or restore on OS releases 7.1A or 7.1B. PROBLEM DETERMINATION: Releases 7.1A and 7.1B have several known problems in the MCS tape driver software, mainly because of the constant starting and stopping of the tape motion - ie., not streaming. WORKAROUND: 1. Limit the size of each backup session to less than 300 files. 2. Use the retention option before the compare. 3. Use 3M DC300 XL/P tape cartridges. 4. Do filesystem backups instead of file list backups FIX: Upgrade the software to release 7.2 or higher. ORIGINATOR: S. MULLER SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB009 Pg001 FIB 00010 04/09/86 *** Release 7.2A Software Announcement *** A new release, Level 7.2A, is now available for distribution. This BOSS/IX~ release is the recommended Operating System for the MAI\ 2000 system. If you wish to order this software level, please use the following software market codes: Market Code Description WG032AA Operating System on MCS WG032AB Operating System Update on MCS WG033AA Operating System on Floppy WG033AB Operating System Update on Floppy WG113AA Configuration Record on MCS WG114AA Configuration Record on Floppy This document details the new and enhanced features of Level 7.2A. Installation/upgrade procedures are fully documented in this announcement. It ismandatory that these procedures be read prior to installing any release Level 7.2A Operating System. NOTE: Care should be taken before installing this release as the Operating System and BASIC programs will require more space than on the Level 7.1 Operatin g System. Please see General Warnings (5.1) for more details. TABLE OF CONTENTS 1.0 Overview 2.0 Installation and Upgrade 2.1 Installation 2.2 Upgrading 2.3 Product Installation/Upgrade 2.4 Security Configuration Record Installation/Upgrade 3.0 Level 7.2A BOSS/IX Enhancement/corrections 3.1 Operating System (EOS) 3.2 System Utility Enhancements (EUT) 3.3 BASIC (EBS) 3.4 27XX/37XX Batch Emulation (EBC) 4.0 New Products in Level 7.2A 4.1 Bass (EBA) 4.2 File Transfer Facility (FTF) 4.3 MAGNET (ENT) SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg001 4.4 3270 Binary Synchronous Communications (B32) 5.0 For Your Information 5.1 General Warnings for Level 7.2A 5.2 Workarounds by Products 6.0 Helpful Hints for Level 7.2A 6.1 Saving errors found during conversion from 7.1 BASIC to 7.2A BASIC to a file or printer 6.2 Approximating A System's Memory Requirement 7.0 Memory Usage 7.1 Calculating Your System's Memory Requirements 7.2 Exact Method for Calculating BOSS/IX Table Space and Dynamic Work Space TABLE OF CONTENTS 8.0 Level 7.2A Base Product Usage File Usage Guide 9.0 New and Updated Manuals for Level 7.2A 10.0 Lowest Acceptable Revision Levels (LARL) The Level 7.2A Release contains the following enhancements/features: o Support of a wider range of MAI BASIC FOUR terminals o Slave printers support o Industry Standard Printer Support o MCS driver Enhancements o 1/2 inch MTS supported for BASIC and command operation o Overlapping seeks supported o Utility driven save and restore for MCS o Enhanced filelist maintenance o Enhanced file repair utility o A BASIC compatible to the MPx family type BASIC o Improved performance with 27XX/37XX Batch Comm o Added on line diagnostics (EBA) o File Transfer Facility Added o MAGNET added o 3270 added 2.0 Installation and Upgrade SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg002 2.1 Installation The following steps outline the MAI\ 2000 BOSS/IX~ installation procedures for tape and floppy diskette. Step 1. First step is to install the boot partition. Insert the base tape into the MCS drive. Or, if you are doing floppy installation insert the installation floppy into drive fd0. Do an alternate load. At the 'boot device:' prompt type "cs" for MCS or "fd0" for floppy diskette, then press . Press again at 'System file:' prompt. Step 2. Screen displays loading messages, then the Install Utility Menu. Select Option 'A', then . Option 'A' re-defines all the wd0 partitions and copies a new boot partition to disk. After copy is complete, you are instructed to reload. Special note for floppy diskette installations, make sure your BOOT floppy diskettes are inserted in the correct sequence according to the BOOT number. After one floppy diskette is complete make sure you change floppy diskettes before responding to the prompt on the screen. Step 3. After the boot partition is installed the configuration record must be installed. When the message 'OPTION>' is re-displayed put the configure record tape or floppy in the tape drive or floppy drive. Use option 'D' to install the configuration record. After the configuration record is installed enter ' ^D' and then 'shutdown'. WARNING: If the configuration record for the system is not installed you will be able to access the boot partition only. NOTE: After shutdown and re-boot to the boot partition it is recommended that the configuration record be copied to the boot partition. To do this execute the following with the configuration tape in the tape drive: 'mcsrestore -v name=CONFIG'. Step 4. After the configuration record, the EOS product must be installed. Reloading the system at this time automatically reloads and roots to the boot partition. Enter the correct date, the screen will then display the 'ADMIN>' prompt, type "osinstall cs" for tape and "osinstall fd0" for floppy diskette. This process uses the parameters in the Super Block to define the root filesystem, then copies the EOS product to the root partition on disk. After the EOS product is installed you are instructed to reload again. Step 5. Reloading of the system at this time automatically reloads and roots to the root partition. Enter either the current date, or a , if the date is correct. At the 'ADMIN>' prompt, type "install cs EUT EBS", for SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg003 tape or "install fd0 EUT", for floppy diskette. List the products in the order they appear on the tape. If you skip one, go back and re-type. Do not add it to the end of your list. When working with tapes all products listed on the base tape can be installed with one command line. When working with floppies you must install one product at a time in the following order: EUT, EBS, EXT, EBA then optional products in any order. If you receive more than the base system, each additional product will be on a separate tape or series of floppy diskettes. Each additional tape or floppy will need a new command line entered. Example: The EIT product is distributed on a separate media. To install it type "install cs EIT" or "install fd0 EIT" at the 'ADMIN>' prompt. Products that are chargeable and not part of the base system will have key codes that you must enter during or after (using '/bin/install key') installation before you can use that product. If the key certificate did not come with the media, contact the customer or service representative in your area to instruct you in where to call for this key code. Step 6. The '/etc/conf' file on the boot partition needs to be customized to meet your needs. (See Section 7.0 'Memory Usage' for instruction on how to customize the '/etc/conf' file.) Step 7. After you have copied all your products to disk and have customized the '/etc/conf' file, your system is ready for use. 2.2 Upgrading The following steps describe the MAI 2000 BOSS/IX upgrade procedures for MCS tape and floppy diskette. NOTE: Always have a recent back-up before doing any upgrades. NOTE: The upgrade of the 7.2A Operating System, Utilities and BASIC will require a minimum of 3 MB of free disk space to complete before 'csave' is run. Step 1. Using the MCS command or the floppy diskette save utility, backup the correct configuration and user files of your system. NOTE: If you are upgrading from a pre-release 7.2A*27 or before it is recommended that you completely replace the boot partition. If you do not want to restore the boot go ahead to step 2. Shutdown system to alternate load prompt. Do an alternate load, at the re-boot prompt: Press key to re-boot ('^C'=alt load, '^S'=self-test): Press ' C'. At the 'Boot device:' prompt type "cs" for tape or "fd0" for floppy diskette. At the 'System file:' SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg004 prompt, press . The system will boot from the tape or floppy and display the loading messages then the install Menu screen. At this menu select option "B". Option "B" will only copy an image on the boot partition from tape or floppy to disk. This process will insure that your system has all the up-to-date and proper MACROs and system files on the boot partition. Once the boot has been copied to disk the '/etc/conf' file on the boot will be set to minimum configuration. You will need to customize this file to meet your system's needs. To customize this file see Section 7.0 'Memory Usage'. After you have copied the boot partition to disk continue on with step 2. Step 2. Do an alternate load. At 'Boot device:' prompt, enter ''. At the 'System File:' prompt, enter ",/etc/boot.conf". Warning: If you are updating from a 7.2A*30 and below you must install the configuration record for your system. See section 2.4 for the steps to install a configuration record. Step 3. The above alternate load will automatically reload and root the operating system to the boot partition. Enter the correct date or '' if the date is correct. Insert the base system tape containing EOS, EUT, EBS or the floppy diskette EOS #1. At the 'ADMIN>' prompt type "osupdate cs" for tape or "osupdate fd0" for floppy diskette. For floppy diskette upgrades the screen will prompt you when to insert the next diskettes. Step 4. After the procedure is complete you have the option of restoring the default system configuration files to the upgraded root then to the boot partition. This is done by typing "/sys/installetc". This procedure allows the operator to select which system files he/she needs to restore. Please note if this is done all system files that are restored will be new and will have to be re-updated to reflect the needed system information. Example: If '/etc/passwd' is re-installed the operators will have to be redefined. Following, find a list of the files that can be installed using '/etc/installetc' and the means to modify the file for your system: etc/class, /etc/defaults, /etc/forms: These files are used when printing and can be customized by going to the 'ut.printer' menu and using option 5 'Printer parameters' or using the program 'pparams'. /etc/conf: This file contains your system configuration parameters and is changed by using the '/bin/vconf' command. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg005 /etc/exem, /etc/logm, /etc/motd: These files print to the screen at the time of log in and can be modified by the use of the '/bin/ved' command. /etc/passwd: This file contains your operator information and is updated by going to the 'ut.system' menu and using Option 3, (Operator information) or by using the program 'oprinfo'. /etc/ports, /etc/printers, /etc/terminals: These files contain the terminal and printer configuration parameters and are updated by going to the 'ut.system' menu and using Option 1, (Port configuration) or by using the program 'configure'. /etc/sinit, /etc/startup: These files are used at system load time and can be modified by the use of the '/bin/ved' command. /etc/shtdwn: This file is used when the system is being shutdown and can be modified by the use of the '/bin/ved' command. /etc/ptrans: This file contains the printer translate tables and is modified by the use of the '/bin/pted' command. NOTE: If you are upgrading from a 7.1A release level this file must be restored using '/etc/installetc'. Step 5. Next shutdown the system and do a normal reload to the root partition. Enter the correct date or press '' if the date is correct. If you are upgrading from MCS, at the 'ADMIN>' prompt type "install cs EUT EBS", press ''. The system will automatically install both EUT and EBS. Once EUT and EBS are installed you can then install the rest of the products by typing "install cs XXX" where XXX is the different product names. If you are upgrading from floppy diskette, insert the first floppy of the EUT set. At the 'ADMIN>' prompt type "install fd0 EUT". Once EUT is complete use the same routine to install EBS and any other products. Step 6. There have been some changes in some of the system files between 7.1A/7.1B and 7.2A. For this reason you are required to make some configuration changes to the system. These configuration changes are identified in the following section on a product basis. If you are not installing a particular product then you need not worry about the configuration changes for that product. If you are installing a product then you must follow the steps SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg006 outlined in the following section that covers that product. Once the upgrade and changes have been performed, be especially careful when restoring files back down from a 7.1A/7.1B tape. If you should accidentally restore a changed configuration file it is best to go back and install that product again from the system tape or floppy, being careful to follow the configuration change steps for that product. 2.3 Product Installation/Upgrade EOS - Operating System 1. After upgrading to 7.2A it is recommended that the "/etc/startup" file be edited to delete the following line. If this line is not removed an error will be generated and logged to the "/etc/sys.log" file when booting to multi-user mode. disp -nnl "Starting remote service manager..."; exec i=/dev/null /lan/lan init; disp "" 2. The /lan files are no longer supported and can be deleted: delete /lan -r 3. The following configuration files have changed in format. These files will be automatically converted to the new format by the upgrade process. /etc/forms /etc/printers /etc/terminals 4. The system supported mnemonics files will be restored during the upgrade and all user mnemonics files will be converted. However, if the user wants to add support for the new mnemonics in the user defined mnemonic files, '/bin/ved' can be used to add the following mnemonics. 'PG' dump screen to terminal printer 'KL' keyboard lock 'KU' keyboard unlock 'TS' transmit screen protected to host 'TL' transmit line to host 'TP' transmit line protected to host 'BC' non-destructive backspace cursor (same as 'LT') 5. The configuration files created by the user using '/bin/vconf' have new fields which have been added. (This does not include the standard system 'conf' files.) All configuration files of this type must be modified by the following command: vconf file name -save -dump tbsize=64 ibsize=512 6. The spooling queues ( queues, qtemps) have been moved from the /tmp directory to the /etc directory. This conversion takes place automatically. The user may change the temporary spool file directory with SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg007 the '/bin/ved' by modifying the second field in the '/etc/printers' file. The pathname can be any existing directory the user wants. Special care should be done in changing this default. 7. The /etc/startup file has been changed to delete all files from the /tmp directory every time the system goes into multi-user mode. The conversion of the /etc/startup file takes place automatically. The affected lines are: changed 2 lines from: delete -s /tmp [ ] %%/dev/null>>/dev/null delete -s -r /tmp/etc %%/dev/null to line: delete -s -r /tmp/.*!* %%/dev/null changed line from: exec alias="/* system update program */ /system /update" -d t=/dev/null /sys/update to: exec alias="/* system update program */ /sys/update" -d t=/dev/null floor=1 ceil=4 /sys/update changed line from: exec alias="/* system error logger */ /sys/errlog" -d t=/dev/null /sys/errlog /etc/error.log -quiet to: exec alias = "/*system error logger */ /sys/err log" -d t=/dev/null floor=1 ceil=6 /sys/ errlog /etc/errorlog -quiet EUT - Utilities 1. The following utility file has been obsoleted. This file will be erased from the system automatically. /util/bcreate 2. The utilities depend on the standard configuration files. Some utilities may not work if these configuration files have not been converted as described in the section on EOS. EBS - Business BASIC 1. The BASIC program file format has changed in 7.2A. Programs created under the 7.1A/B environment will be unusable in 7.2A unless converted using one of the ways described below. Converted programs can be expected to grow in size by approximately 20%. It takes approximately 7.5 minutes to convert 100K bytes SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg008 of program. BASIC program files can be converted to the new format in one of two ways. Following, is a description of each of the ways to convert your BASIC program files to 7.2A format: 1. At the end of the installation of the EBS package you will be prompted: 'Do you wish to convert all programs on the disk?' 'Enter 'y' or 'n':' If you enter a 'y' to this prompt the BASIC programs you have on your system will convert to 7.2A format at that time. 2. You can also convert your BASIC programs to 7.2A format at any other time by the use of the 'csave' command. (For the use of 'csave' see M6225A) Warning: The conversion to level 7.2A BASIC format is not backwards compatible. NOTE: After the BASIC program files are converted they will be approximately 20% larger. 2. For other changes to Basic on level 7.2A please see section 3, 'Level 7.2A BOSS.IX Enhancements/corrections'. EBC - 27XX/37XX Batch Communications 1. Cunos (7.1A/B EBC operating system) is now installed as Bbossix. During the installation procedure of EBC, a prompt will display asking the user whether Bbossix is to be installed on the boot or the root partition. A "1" response will install Bbossix on the boot partition and rename it as bossix. Any other response will install Bbossix on the root partition. The user must then copy /sys/Bbossix from the root to the boot partition and do an alternate load of /sys/Bbossix, or rename Bbossix as bossix for a normal load. 2. A public key is required to run EBC. During the installation procedure of EBC, a prompt will display requesting the public key. This key is unique to the system serial number and is written on the product certificate accompanying the EBC tape or floppy. 3. The "configure" utility must be executed to configure Port 1 as a "communications" port to run EBC. Previously, on 7.1A/B, Port 1 had to be "not configured" to run EBC. 4. The bisync line driver interface, /sys/bsci, is no longer required and will be deleted by the SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg009 installation procedure. 5. The 7.1B EBC translation table for the EBCDIC line code contained incorrect translations for lower case j - r. If this is an upgrade of a 7.1A/B system, delete the translation table, /etc/comm/trcnd, so that the 7.2A version of the table will be created when bcom is executed. 6. The 7.2A EBC package has been optimized and now will run with the following approximate configurations: 1 MB Memory - EBC with 2 concurrent tasks 1.25 MB Memory - EBC with 4 concurrent tasks 1.5 MB Memory - EBC with 8 concurrent tasks 7. Baud rates supported are 2400 and 4800. 8. The /etc/startup file has been changed on 7.2A. It can either be installed with the EOS installation or the file can be retained from 7.1A/B and edited using /bin/ved: If the following line exists in /etc/startup, delete it using the ved command. disp -nnl "Starting remote service manager..."; exec i=/dev/null /lan/lan init; disp"" Add the following line right before the line "Multi-user startup completed". disp -nnl "initializing network remote services manager..."; exec -ignore i=/dev/null /net/netinit; disp "" FTF - FILE TRANSFER FACILITY 1. The FTF product installs the operating system containing the LAN drivers, Lbossix, on either the boot or the root partition, depending on the response to the installation prompt in FTF. A "1" response will install Lbossix on the boot partition and rename it as bossix. Any other response will install Lbossix on the root partition. The user must then manually copy /sys/Lbossix from the root to the boot partition and do an alternate load of /sys/Lbossix, or rename /sys/Lbossix as /sys/bossix for a normal load. 2. A public key is required to run FTF. During the installation process, a prompt will display requesting the public key. This key is unique to the system serial number and is written on the product certificate accompanying the FTF product tape or floppy. 3. The 7.1A/B lan files are no longer supported and can be deleted: delete /lan -r delete /sta/* -r delete /bin/lan rcopy SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg010 delete /bin/lan rcx delete /bin/lan util 4. The /etc/startup file has been changed on 7.2A. It can either be installed with the EOS installation or the file can be retained from 7.1A/B and edited using /bin/ved: If the following line exists in /etc/startup, delete it using the ved command. disp -nnl "Starting remote service manager..."; exec i=/dev/null /lan/lan init; disp"" Add the following line right before the line "Multi-user startup completed". disp -nnl "initializing network remote services manager..."; exec -ignore i=/dev/null /net/netinit; disp "" 5. LAN users on 7.1A/B will have to redefine the network configuration for 7.2A. FTF supports remote file copy via the FTF utilities over a local (LAN) or wide (X.25) area network. FTF does NOT support the LAN 7.1A/B features of remote file copy, remote file access, or remote command execution. 6. A new utility, FTFIT, is available on the MAI 2000 System and the MPx 8000 Series Systems to schedule intersystem FTF BQR filelists between the 2000 and 8000 Systems. FTFIT is not available on the 13XX Series Systems, although a workaround method exists for users who wish to send files from the 13XX to the 2000 System via FTF/X.25. This workaround will be available from Product Support on a request basis. ENT - MAGNET 1. The MAGNET (ENT) product installs the operating system containing the LAN drivers, Lbossix, on either the boot or the root partition, depending on the response to the installation prompt in ENT. A "1" response will install Lbossix on the boot partition and rename it as bossix. Any other response will install Lbossix on the root partition. The user must then manually copy /sys/Lbossix from the root to the boot partition and do an alternate load of /sys/Lbossix, or rename /sys/Lbossix as /sys/bossix for a normal load. 2. A public key is required to run ENT. During the installation process, a prompt will display requesting the public key. This key is unique to the system serial number of the system and is written on the product certificate accompanying the ENT product tape or floppy. 3. The 7.1A/B lan files are no longer supported and can be deleted: delete /lan -r delete /sta/* -r SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg011 delete /bin/lan rcopy delete /bin/lan rcx delete /bin/lan util 4. The /etc/startup file has been changed on 7.2A. It can either be installed with the EOS installation or the file can be retained from 7.1A/B and edited using /bin/ved: If the following line exists in /etc/startup, delete it using the ved command. disp -nnl "Starting remote service manager..."; exec i=/dev/null /lan/lan init;disp"" Add the following line right before the line "Multi-user startup completed: disp -nnl "initializing network remote services manager..."; exec -ignore i=/dev/null /net/netinit; disp "" 5. LAN users on 7.1A/B will have to redefine the network configuration for 7.2A. ENT supports remote file access and remote file copy over a local (LAN) or wide (X.25) area network. ENT does NOT support the LAN 7.1A/B feature of remote command execution. X25 - X.25 Drivers 1. The X.25 product is supported through the File Transfer Facility (FTF) for remote file copy, and through MAGNET (ENT) for remote file access/copy over X.25 lines. During the installation procedure of X25, a prompt will display asking the user to select whether the X.25 operating system, Xbossix, is to be installed on the root or boot partition. A "l" response will install Xbossix on the boot partition and rename it to bossix. Any other response will install Xbossix on the root partition. The user must copy /sys/Xbossix to the boot partition and do an alternate load of /sys/Xbossix, or rename Xbossix as bossix for a normal load. Caution must be used so that the FTF or ENT operating system, Lbossix, does not overwrite Xbossix. For this reason, X25 should be installed after FTF or ENT is installed. 2. A public key is required to run X25. During the installation process, a prompt will display requesting the public key. This key is unique to the system serial number and is written on the product certificate accompanying the X25 product tape or floppy. 3. The "configure" utility must be executed to configure port 1 as a "communications" port to run X.25. In addition, CMB port 1 must be strapped for a modem. 4. Since Xbossix contains the LAN drivers in addition to the X.25 drivers, once it is installed on the system, the operating system installed with FTF or ENT, Lbossix, can be deleted to save disk space. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg012 3270 BSC (B32) 1. The B32 product installs the operating system containing the Binary Synchronous Communications (BSC) driver, Bbossix, on either the boot or the root partition, depending on the response to the installation prompt in B32. A '1' response will install Bbossix on the boot partition and rename it as bossix. Any other response will install Bbossix on the root partition. The user must then copy /sys/Bbossix from the root to the boot partition and do an alternate load of /sys/Bbossix, or rename /sys/Bbossix as /sys/bossix for a normal load. note: The B32 product uses the same operating system, Bbossix, as EBC. Therefore, either the EBC or B32 product, but not both concurrently, may be started without re-booting the system. 2. A public key is required to run B32. During the installation process, a prompt will display requesting the public key. This key is unique to the system serial number of the system and is written on the product certificate accompanying the B32 product tape or floppy. 3. The "configure" utility must be executed to configure Port 1 as a "communications" port to run B32. In addition, CMB Port 1 must be strapped for a modem. 4. The /etc/startup file has been changed on 7.2A. It can either be installed with the EOS installation or the file can be retained from 7.1A/B and edited using /bin/ved: If the following line exists in /etc/startup, delete it using the ved command: disp -nnl "Starting remote service manager..."; exec i=/dev/null /lan/lan init; disp"" Add the following line right before the line "Multi-user startup completed". disp -nnl "initializing network remote services manager..."; exec -ignore i=/dev/null /net/netinit; disp "" GKS and GRF - Graphics 1. The devices defined in the /etc/plotters file must be redefined using the configure utility. The best way to accomplish this is to delete the old /etc/plotters file and run configure. 2. The install procedure for both GKS and GRF has been modified to include /etc/gks/devices. This file should not be modified by the user. 3. The install procedure for GKS and GRF now appends the following entry into the /etc/forms file. single:66:80::::::::6:10:S8:y:* SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg013 EDB - Informix 3.3 Database Management 1. No 'ace' report or 'preform' form compiled under Informix 3.1 (7.1A and 7.1B) can be used under Informix 3.3 (7.2A). An attempt to do so will result in the display of a message requesting that the user re-compile with 'aceprep' or 'formbuild'. Unless the new features are to be used, no change is required to the source for the reports or forms. 2. Although no warning messages will appear, it is also recommended that schemas compiled under Informix 3.1 be re-compiled by 'dbbuild' (without the -r rebuild option) under Informix 3.3. The only known problem with not doing so is that, for schemas using BFS compatibility features (marked by use of 'file type' directives), the display of field types by a 'print schema' statement in 'dbstatus' or 'informer' may be incorrect. There are no other changes required for any of the other products. 2.4 Security Configuration Record 2.4.1 Installing/Upgrading a Security Configuration Record on the MAI 2000. When installing 7.2A*30 (or any later 7.2A release) on your system or if you are upgrading/adding to the system's hardware, you must also install/upgrade a security configuration record. Each system needs a unique configuration record based on the system serial number and hardware configuration. Without it, you won't be able to boot the system to the root partition. An attempt to boot to the root partition will cause the system to halt giving an "Illegal Configuration Record" message. This security termination will not damage the root partition. The procedure to install/upgrade a configuration record on the MAI 2000 is outlined below: 1. Boot from the install media. (Base tape or install floppy). 2. Install the boot partition if you need to. 3. Remove the install media and insert the configuration media. 4. Use option "D" to install the configuration record. 5. Shutdown and re-boot the system. 6. OPTIONAL: You can save a copy of the configuration record on the boot partition. To place a copy of the configuration record on the boot partition, after re-booting to the boot partition, use the command: mcsrestore -v name=CONFIG 7. Remove the configuration media and re-insert the install media. 8. Continue with the normal installation procedure. Once you have installed/upgraded the configuration record on your system it will not have to be done again unless a re-format is required or the system's hardware configuration changes. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg014 2.4.2 The 'iconf' command The new program '/bin/iconf' will display the current configuration in force as well as the configuration contained in a configuration record file. The 'iconf' command can also be used to install the configuration record. Format iconf Options -new Display the new system configuration which may be installed -save permanently installs the new configuration record Examples @>iconf Displays the current system configuration @>iconf - new -save Displays the default configuration record and stores it in the system configuration record. Notes: Only the system administrator may display or install the new configuration. The configuration record is always read from, or written to, the Winchester disk from which the system was booted, or from wd0 if the boot device was tape or floppy. Unless explicitly specified, the new configuration record is assumed to be contained in a file under the name '/sys/config.', where is the 10 character system serial number. 2.4.3 Configuration Record Request Sheet On the following page you will find a copy of the 7.2 Configuration Record request sheet. 3.0 LEVEL 7.2A BOSS/IX ENHANCEMENTS/CORRECTIONS 3.1 OPERATING SYSTEM (EOS) 3.1.1 Industry Standard Printer Option Level 7.2A now has an option for Industry Standard Printers (ISP). This option allows the user to configure an ISP that will use a driver that contains only the Industry Standard mnemonic set which includes 'CR', 'LF', 'FF', 'NL', @ positioning and VFU loading. The user is also able to configure the read/status timeout (the time in seconds the system will wait for a response from the printer after a command is issued) and write timeout (the time the system will wait after an x-off is issued or DTR drops before timing out). SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg015 The parallel interface type ISP will now allow interfacing of printers that use the Centronics 351 type interface. 3.1.2 Graphic Printer Option Graphic printers can now be configured through the Port Configuration Utility. There is a 'special' option under the printer options, both parallel and serial, that allows the user to name his/her special printer and set up the plotter parameters along with the other options for ISPs. The serial 'dmp', 'hpplot', parallel 'dmp' and 'lpm' type printers will also allow the user to set graphic parameters. Spooling can be used with the graphic printer. The graphic printer driver will allows untranslated data to pass to the printer for graphic printing. The command 'lpr' has an added option '-ra' that allows the data to be passed to the printer untranslated. The command 'lpq' will show a spool file created in graphics to be shown as "raw". 3.1.3 Slave Printers Supported Slave printers are now supported and are configurable. The 7270 and EVDT will support MAI Basic Four type printers and the EDT will support both MAI Basic Four printers and ISPs. The slave printers are configured using the Port Configuration utility when configuring a terminal. The printers will be 'Lx' (x=terminal port number) and will have the same mnemonic support as the system printers. Note: Slave printers cannot be used with spooling and can only be used by other users if the terminal the printer is connected to is logged off. Slave printers are counted in the printer count in the '/etc/conf' file. 3.1.4 New Terminals Supported The 7250, ODT and S/10 are now supported when configured as 7270 type terminals. There is now an option to allow the user to configure Graphic type terminals in the Port configuration utility. 3.1.5 'vconf' Configuration File Changed The files that are created/modified using the command 'vconf' have had two new parameters added; 'type ahead buffers' allow the operator to type ahead of the input prompts by the amounts specified. 'input buffers' is the amount of characters that the system will buffer during data transfer before an Error 34 (VDT buffer overflow) is produced. The parameter 'clist', which covered the two new 'vconf' parameters, has been removed. 3.1.6 Spooler Changes/Enhancements Turning off automatic spooler-inserted 'form feed' on a printer basis SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg016 The spooler has been changed to allow the user to specify, on a printer basis, whether the spooler should insert a form feed before each print job. The default, in which the user does nothing, is to insert a form feed before each print job. In order to configure the printer spooler for no form feed the user should do 'cat > /etc/.noformfeed' while in single user mode. When he brings the system to multi-user the printer spooler will be started. To re-configure a printer spooler for form feeds one should delete the file while in single user mode and then bring the system back to multi-user. An alternate method to configure the spooler for form feed would be to create/delete the file while in multi-user and then kill the spooler, '/sys/lpd '. It will re-start automatically. Form Feed with Spooling The spooler will not produce a form feed unless there is data in the spool file to be printed. Level 7.1 printed a form feed each time the printer was opened. Spooler Temporary Files Moved The spooler files have been moved from the '/tmp' directory to the '/etc' directory. This will allow for the '/tmp' directory to be erased at the time system is loaded into multi-user. 3.1.7 MCS Driver Enhanced The MCS driver will now allow on-the-fly reads and writes. On-the-fly reads and writes allows the tape drive to read and write end of file marks without stopping. 3.1.8 Printer Testing at Time of Boot All configured printers on the system will be tested at boot time. If a configured printer is offline, not connected or has any other type of problem an error showing the printers condition will be written to the '/etc/sys.log' file. The user will be prompted to enter Escape to continue to warn the user of the error in the '/etc/sys.log' file. 3.1.9 Ghost Support Moved The ghost server has been removed from the 'lan' remote services manager (/lan/lan rsm) and is now an internal part of the operating systems kernel. 3.1.10 MTS Driver Added The driver for the MTS 1/2 inch tape (R0) has been added. This driver will allow the user to write his/her own BASIC applications to do input/output to the MTS 1/2 inch tape using standard BASIC directives. The MTS 1/2 inch tape can also be used for back-up and restore operations. Note: The MTS 1/2 inch tape will not be a bootable device SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg017 on 7.2A, for this reason the MTS 1/2 inch tape can not be used to do Operating System installations. Note: For a complete listing of the new commands for the MTS 1/2 inch tape please see BOSS/IX command changes (3.1.12). 3.1.11 WBD Package Part of EOS The Winchester Bootable Diagnostics (WBD) has now been made a part of the EOS package and is installed at the time EOS is installed. 3.1.12 BOSS/IX Command Changes For more details on these new commands and the changes please see BFISD 6200A - MAI 2000 User Guide. MTS Command The syntax for the MTS commands are the same as their MCS counterparts with the exceptions noted under each command. mtscompare This command will compare the files on the MTS 1/2 inch tape to files on disk. Added option -unload This option specifies that the tape is to be un-loaded (taken off the take-up reel and the drive put offline) upon completion of the command. mtslabel This command will read and write labels to the MTS 1/2 inch tape. mtslist This command lists the files in a saveset or savesets on a MTS 1/2 inch tape. '-tension' to re-tension a tape is not part on the mtslist command. mtsrestore This command allows a user to restore files and file system images from the MTS 1/2 inch tape to disk. The '-tension' option is not part of the mtsrestore command. The '-unload' is included in the mtsrestore command. mtssave This command saves individual files, files found in a filelist, and file systems to the MTS 1/2 inch tape form disk. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg018 the '-tension' option is not part of the mtssave command. The '-unload' is a part of the mtssave command. MCS's commands in general The use of 'dev=/dev/cs' will produce a bad option now as the 'dev=' option has been removed from the commands. 'mcssve' changes The 'mcssave' command has had three options added as follows: -tension - Re-tensions the tape before writing to tape. -stat - Will cause the system to display total number of blocks processed from tape and the number of blocks re-read. -ss - This option will force tape motion to stop when a filemark is written. 'mcsrestore' changes The 'mcsrestore' command has had two options added as follows: ssnum=number - This option specifies the saveset number by position on tape that files are to be restored from. The first saveset is number 1. -stat - Will cause the system to display the number of blocks that were written to tape and the number of blocks that were re-written to tape. 'date' Command Changed The 'date' command now has the option 'timeout=#'. This option will allow a time to be placed in the date command for the command to time out if a date/time is not entered in the time specified. (This can be used in the sinit file at load time.) 'lpr' Command Changed The 'lpr' command has had two options added as follows: - raw - Submits the print job in "raw" mode, suppressing all mnemonics processing. time=date - Delays printing until the specified time and date. Allowed formats are: hhmm, MMDDhhmm and MMDDhhmmYY 'cat' Command Added The 'cat' command has been added. This command opens each of the specified files and reads all the characters found in each. It then writes the characters to standard output. If several files are specified, the output is the concatenation of the files in the specified sequence. 'change' Command Added SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg019 The "change" command substitutes the substitution string for the pattern string in specified files. 'diff' Command Added The "diff" command shows what lines differ between two files. 'match' Command Added The "match" command searches each line of the named files for all occurrences of the given pattern. All lines that match the pattern are output to standard out. 3.1.13 POWER DOWN MESSAGE CHANGED The following message will be displayed when it is safe to power down the system after a shutdown: System Shutdown Complete -- Power Off or Re-boot 3.1.14 Overlapping Seeks Dual hard disk drive systems will now perform overlapping seeks when accessing both drives. Note: For overlapping seeks the single disk controller must be at revision 'D' or higher. The dual disk controller can not be used. 3.2 SYSTEM UTILITIES (EUT) Below is listed the changes and enhancement to the system utilities. For more details please see BFISD 6200A - MAI 2000 User Guide. NOTE: Any utility that allows printing to the printer will now print to a non-spooler printer. 3.2.1 Printer Utility Enhancements 'pparams' Utility The program 'pparams' has been added. This program will allow the user through a menu driven utility to create, modify, delete and report the spooler related files; these include the 'print control defaults file' (/etc/defaults), 'class definition' (/etc/class) and 'form definition' (/etc/forms). This utility can be run directly from console mode or by accessing the printer utility 'menu ut.printer' and selecting option 5 'Printer parameters'. Trial form option An option for trial forms has been added to the change forms utility (pformchg). After a forms changes has been made the user will have the option to print a trial form to ensure that his form is lined up before proceeding. Also, if the 'lpmaint' command is used to change forms the option '-fp' can be used to print a trial form. 3.2.2 Save and Restore Utility using MCS Tape SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg020 The utility 'Save and Restore' now includes the options to save to, restore from, report the contents, compare and label the MCS tape. These utilities can be run from console mode by using 'msave' to save to tape, 'mrestore' to restore from tape, 'mreport' to report tape contents, 'mcompare' to compare tape to disk, or 'mlabel' to label a tape or by accessing the save and restore utility 'menu ut.save'. 3.2.3 Files Utility Enhancements 3.2.3.1 Filelist Enhancements Filelist creation and modification has been expanded to allow the selecting of the different file types to be included in the filelist. This is done by changing the operator's environment by using the 'change environment' option when creating or modifying a filelist. You may get into the 'change environment' by using MBIII at the enter 'file or filelist' prompt or from the filelist menu. 3.2.3.2 'frepair' Utility The utility 'frepair' has been added to allow the operator to analyze and/or repair a data type file. This utility will give the operator the option to just analyze the file or analyze and repair the file (if the file is repairable). The utility can be run from console mode by using 'frepair' or by using option 9 'File repair' from the 'ut.file' menu. The repair option can only be used if the operator is logged in as 'admin'. A file can be analyzed by any operator that has access rights to the file. If repairing a key-type file the utility will attempt to rebuild the file. If the file is any other type and a bad block is found in the file area the block will be removed and the user will be told of the last good record before the bad block and the next good record after the bad block. Repairing a file requires disk space at least equal to the size of the file being repaired. Repairing files could require twice the disk space of the file being repaired if the user chooses to repair the file using a template file. WARNING: Before using this utility a back-up copy of the file should be made. NOTE: A template file is a file that the 'frepair' utility can get the information required such as key size, record length and number of records. This file does not need to contain the same data as the file being repaired, but must have the exact same parameters. 3.2.3.3 Multi-key Type File Support The file utilities now support multi-keyed files for use in Cobol and Informix. 3.3 BASIC (EBS) 3.3.1 BB 7.1 DIRECTIVES THAT ARE NOT SUPPORTED IN BB 7.2A The following is a list of the 7.1 BASIC directive that are no longer supported in 7.2A BASIC and should be removed as SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg021 they will cause error 20 to be produced: DISABLE (Disables a disk drive) ENABLE (Enables a disk drive) SELECT (Selects a logical disk drive) 3.3.2 BB 7.1 SYSTEM VARIABLES THAT ARE NOT SUPPORTED IN BB 7.2A The following is a list of the 7.1 BASIC variables that are no longer supported and will return a value of 0 if used: SEL (Selected logical disk) TCB(9) (Selected logical disk) 3.3.3 OTHER BB 7.1 FEATURES NOT SUPPORTED BY BB 7.2A Logical disk mode. This accounts for the absence of the DISABLE, ENABLE and SELECT directives, as well as the SEL TCB(9) system variables from BB 7.2A. Also, in BB 7.1 byte 20 of the FID gives the logical disk; in BB 7.2A byte 20 of the FID is always 255. BB 7.1 was space insensitive, that is when coding spaces were not required. BB 7.2A does require that spaces are used where required. If spaces are not used when needed an ERROR 20 can be generated or the statement may take on a meaning not intended. (Ex: LETA=B will mean let the variable 'LETA' equal B not A=B). The CPL function takes one or two arguments in BB 7.1 and one or three arguments in BB 7.2A. Also, the format of the second argument to the CPL and LST functions is different between BB 7.1 and BB 7.2 (see BFISD 6252A for more details). The BB7.2A CALL directive returns an ERROR 38 if the same argument is passed twice as a modifiable variable. (Ex: CALL "PGM",A,A). This was allowed in BB7.1. The BB 7.2A SAVE directive no longer requires program size, logical disk, sector or extent parameters; if these are supplied they are ignored. (The exception is when the program size is 1; this instructs the system to create a file which is as contiguous as possible.) In BB 7.2A, if SAVE needs to create a program file, it will be exactly the size of the program to be SAVEd. A BB 7.1 program which used SAVE to create a larger-than-needed program will therefore work differently in BB 7.2A. The pgm= field and the command field on the BOSS/IX command line work together differently between BB 7.1 and BB 7.2A. In BB 7.1 first the command is executed, then the program is run. In BB 7.2A the program is first loaded, then the command is executed, and then the program is run. 3.3.4 NEW DIRECTIVES IN BB 7.2A The following is a list of the new directives that are now supported on BB 7.2A: BEGIN EXCEPT The BEGIN EXCEPT was the same functionality as BEGIN with the exception that variables contained in a variable list SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg022 following the BEGIN EXCEPT will not be cleared. FULLY-NESTED IF BB 7.2A now allows the ELSE clauses in the IF directive to be fully nested. To support multiple ELSE causes, BB 7.2A allows the FI delimiter in the IF directive. ON GOSUB The ON GOSUB directive works like the ON GOTO with the exception that a GOSUB is executed not a GOTO. OPEN INPUT If the keyword INPUT follows the OPEN keyword, the file will be OPENed read-only. A file OPENed read-only may be read from, but an attempt to write to it generates ERROR 18. SYSTEM The SYSTEM directive allows the user to execute a BOSS/IX directive and remain in the BASIC environment. It is similar to the "!" directive, except that "!" is followed by an unquoted literal and SYSTEM is followed by a proper string expression. This difference allows SYSTEM (unlike "!") to appear at the beginning or in the middle of compound statements, because it is clear from the syntax where the BOSS/IX commands ends and the next BASIC directive begins. 3.3.5 TBL FUNCTION The TBL function allows table translation with out the use of an input/output directive. 3.3.6 PRC SYSTEM VARIABLE The PRC system variable returns a numeric value which is the current arithmetic precision of the user's BASIC 3.3.7 NEW CLAUSES IN BB 7.2A IND= (on CLOSE) The IND= on a CLOSE directive when using the 1/2 inch tape will close the tape and also cause an action to be taken depending on the number used for the IND=. SEQ= The SEQ= clauses can be used only when opening the 1/2 inch tape driver R0. When the tape driver is opened with a SEQ= the tape will advance to that sequential file mark. 3.3.8 OTHER NEW FEATURES IN BB 7.2A LONGER VARIABLE NAMES 8 character variable names are now allowed. These names can contain 1 to 8 characters with the first character being a letter. Defined function variables can contain up to 8 characters SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg023 following the 'FN'. MAXIMUM STATEMENT NUMBER The maximum number of statements has been changed from 9999 to 16000. ! DIRECTIVE IN PROGRAM MODE The '!' followed by a command or command level program/utility is now allowed from BASIC. Setting a string variable to equal the system command then executing that string is no longer required. ERRORS RETURNED TO BASIC When the "!" or SYSTEM directive is used and an error occurs in BOSS/IX a BASIC error will be returned to the program. LISTED FORMAT CHANGED The LISTed format of BB 7.2A programs will now have 5-digit statement numbers. OPTIONAL DISK AND SECTOR NUMBER PARAMETERS Disk and sector number parameters in the file-define directive, DIRECT, INDEXED, PROGRAM, SAVE, SERIAL, SORT, and STRING, are not needed. If they are used in the directive they will be ignored. If initial and growth parameters are required then dummy numbers must be used in the disk and sector number parameters. SAVE DIRECTIVE CHANGED If the SAVE directive is used without parameters it will automatically create or re-size a program file to the program file's required size. DIM OF ENTERED VARIABLES BB 7.2A now allows a user to re-DIM a string of numeric array which is passed to a CALLed program. START DIRECTIVE CHANGED the START directive can now be used with zero arguments, which will do a re-START using the start size that the user last used. The maximum number of pages in a START directive has changed from 128 to 65535. MNEMONICS AS STRINGS Mnemonics can now be used as strings. examples: PRINT HTA('CS') will return 1B4353 LET A$='CS'+"THIS IS A TEST!" printing A$ causes a clear screen then the printing of THIS IS A TEST. GHOST TASKS TAKE on STARTING TASKS DIRECTORY ENVIRONMENT When a Ghost task is started, the Ghost will now have the SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg024 same prefix set as the task that started the Ghost. -trans OPTION ADDED IN BOSS/IX COMMAND LINE -trans has been added to the command line options. Its syntax is: basic -trans -trans provides automatic translation as follows: when the user references a file name, if this name appears as a source file name in the translation file, BASIC will obtain the translated file name from the translation file, and will substitute the translated file name for the source file name. If the source file name is not found in the translate file, no translation is done, and the original source file name is used. The following BASIC directives are affected: ADDE, ADDR, CALL, DIRECT, DROP, ENCRYPT, ERASE, FILE, INDEXED, LOAD, OPEN, PROGRAM, RENAME, RUN, SAVE, SERIAL, SORT, START, STRING, VMERGE The translation file is a STRING file with the following format: The first line is the revision level. In this release it is: "EBS001:". Each of the remaining lines has the following format: The delimiter can be any character. Example: SHOW will be a translate file. That looks as follows: EBS001: *test*/usr/ps/test1 *source*/sta/hi/usr/ps/source2 The command 'basic -trans SHOW' is executed. Now each time a BASIC directive listed above uses the file name 'test' the system will translate it to '/usr/ps/test1' like wise the file name 'source' in a program will be translated to '/sta/hi/usr/ps/source2'. 3.4 27XX/37XX BATCH EMULATION (EBC) 3.4.1 Improved Performance The EBC package 7.2A has been optimized and can now run with the following approximate configuration: 1.0 MB memory - EBC with two concurrent tasks 1.25 MB memory - EBC with four concurrent tasks 1.5 MB memory - EBC with eight concurrent tasks 3.4.2 Port Configuration Option for Communications SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg025 A new option, "communications", has been added to the configure utility for configuring EBC on port 1. This allows the operator when configuring new ports to see that the port is already set for communications. NOTE: As with previous releases, the port must be strapped for 'modem operation' when EBC is configured. 4.0 NEW PRODUCTS IN LEVEL 7.2A 4.1 BASS - Basic All-purpose Service System (EBA) 4.1.1 Features BASS is designed to exercise the peripheral hardware through the operating system. It is completely menu driven for ease of use by a customer or operator. The programs are written in BASIC, with the exception of the disk and tape exercisers which use a few command level commands and the LAN exerciser which is written in 'c' language. The package is constructed so that a specific peripheral can be exercised and tested while normal system tasks continue to be executed in parallel. The programs are intended to exercise the peripherals and demonstrate functionality. 4.1.2 Hardware/software Requirements 4.1.2.1 Hardware Requirements o CPU and a minimum of 100 pages of user memory available o A VDT and controller with cable o The EBA package requires .84MB of disk space to be installed 4.1.2.2 Software Requirements o Level 7.2A operating system (EOS) and Business BASIC (EBS) o BASS package (EBA) - Rev. 7201 or greater 4.1.3 Operating Instruction BASS is initiated by entering the directory '/sys/bass' and running BASIC with a start of at least 100 pages of memory. The BASS monitor is then initiated by entering 'RUN"BASS"'. After any test(s) have been executed from either the service system, Inspection Cycle or Burn-In Cycle, the summary screen is displayed. It consists of start time, current time, date, the terminal from which BASS was run from and then it lists each test run along with the numbers of errors detected. This screen will be displayed after each test is run for approximately three seconds. If B/4 Service System or Inspection Cycle were chosen then the summary screen will be re-displayed continuously. If Burn-In Cycle is chosen following the summary screen and return to the main menu press the 'escape' key after the screen has been completely printed. 4.2 File Transfer Facility (FTF) SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg026 4.2.1 Features FTF provides the capability to transfer files between 2000 systems and interconnected 2000/8000 systems. The user interface is similar to the existing B4NET/FTF product on the 8000. In addition to remote file copy, FTF provides the user with the following: o automatic host connection without operator intervention o end to end delivery assurance with automatic re-scheduling and re-start capabilities o concurrent file transfers o remote/local program startup upon file transfer completion o priority transfers o file access security o interface to Intersystem Transfer utilities o 4800 Baud maximum 4.2.2 Media FTF supports two transmission medias; Local Area Networking (LAN) and Wide Area Networking (WAN). A LAN configuration consists of up to 63 2000's connected via LAN controller boards, drop cables, tap boxes, repeaters (optional), and trunk cable up to a maximum distance of 4000 feet. A WAN configuration consists of an X.25 connection to another 2000 or an 8000 through a private or public data network (PDN). X.25 is an international synchronous protocol which uses port 1 on the CMB as the communications port. The FTF network may consist of either a LAN, a WAN, or a combination of the two. 4.2.3 Hardware/Software Requirements 4.2.3.1 Hardware Requirements o CPU with 1.5MB memory recommended o LAN - lan controller, drop cable, trunk cable, tap boxes, repeaters (optional) and/or o WAN - CMB port 1 strapped for modem, synchronous modem or modem eliminator, CMB to modem cable. 4.2.3.2 Software Requirements o Base O.S. o Configuration Product FTF/LAN - install FTF FTF/X.25 - install FTF and X25 FTF/LAN/X25 - install FTF and X25 4.2.4 Operating Procedures SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg027 o Install FTF (X25 - optional) and boot the proper operating system. o Install the hardware for LAN and/or X.25. o Go into multi-user mode and select the communications sub-menu from the main menu. o Select the Network Configurator option to configure the network. o Activate the media via the Media Inventory option in the Network Configurator menu. o Select the File Transfer Facility option from the communications menu to enter the FTF utilities. 4.2.5 Documentation For detailed information, please refer to the "File Transfer Facility (FTF) User Reference Manual", M6352. 4.2.6 Restrictions If using the BASIC callable portion of FTF, BASIC and FTF must be the same release level. 4.3 MAGNET (ENT) 4.3.1 Features ENT allows the sharing of 2000 resources between interconnected 2000 systems by providing remote file access and remote file copy features. These features allow a user to easily develop a distributed system from existing or newly developed applications. Some of the features of ENT are documented below: o Access to files on other 2000's on the network via standard Business Basic file I/O. o "-trans" option of Basic allows for little or no code modification in application when files are moved between systems. o Local Area Network (LAN), Wide Area Network (X.25), or a combination of both supported as data communications media. o File copy between interconnected 2000's available via the same type of utilities used within a local system. 4.3.2 Media ENT supports two transmission medias; Local Area Networking (LAN) and Wide Area Networking (WAN). A LAN configuration consists of up to 63 2000's connected via LAN controller boards, drop cables, tap boxes, repeaters (optional), and trunk cable up to a maximum distance of 4000 feet. A WAN configuration consists of an X.25 connection to SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg028 another 2000 through a private or public data network (PDN). X.25 is an international synchronous protocol which uses port 1 on the CMB as the communications port. The ENT network may consist of either a LAN, a WAN, or a combination of the two. 4.3.3 Hardware/Software Requirements 4.3.3.1 Hardware Requirements o CPU with 1.5MB memory recommended o LAN - lan controller, drop cable, trunk cable, tap box, repeaters (optional) and/or o WAN - CMB port 1 strapped for modem, synchronous modem or modem eliminator, CMB to modem cable 4.3.3.2 Software Requirements o Base O.S. o Configuration Product ENT/LAN - install ENT ENT/X.25 - install ENT and X25 ENT/LAN/X25 - install ENT and X25 4.3.4 Operating Procedures o Install ENT (X25 - optional) and boot the proper operating system. o Install the hardware for LAN and/or X.25. o Go into multi-user mode and select the communications sub-menu from the main menu. o Select the Network Configurator option to configure the network. o Activate the media via the Media Inventory option in the Network Configurator menu. o Select the Remote File Copy option from the communications menu to enter the MAGNET file copy utility. o Applications may be written to open remote files by specifying full path names, including /sta names or by utilizing the -trans option of Basic. 4.3.5 Documentation For detailed information, please refer to the "MAGNET User Reference Manual", M6360. 4.4 3270 Binary Synchronous Communications (B32) 4.4.1 Features SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg029 The B32 product allows emulation of the IBM 3274-51C Binary Synchronous Communications (BSC) cluster controller and its associated display terminals (3278-2) and printers (3287-2). With the B32 product installed, any EDT will appear to the IBM or IBM compatible host as a remote 3278-2 display terminal. Any printer supported by the 2000 operating system will emulate an IBM 3287-2 printer. Listed below are some of the supported features of the B32 product: o 3274-51C compatibility in BSC-3 multi-point protocol mode o Support of up to eight 3278/3287 devices concurrently o Local configuration of devices and cluster addresses o Baud rates of up to 4800 maximum 4.4.2 Hardware/Software Requirements 4.4.2.1 Hardware Requirements o 1.5 MB memory recommended o CPU with 1.5MB memory recommended o CMB port 1 strapped for modem o CMB to modem cable o EDT (4310) for every 3278-2 display terminal emulated o Serial or parallel printer for every 3287-2 printer emulated o 200K bytes of memory for each device emulation object code. 64K bytes for 3274 cluster controller object code. 146K bytes for each 3287 printer emulation object code. 4.4.2.2 Software Requirements o Base O.S. o B32 Product 4.4.3 Operating procedures o Install B32 and boot the Binary Synchronous Communications (BSC) operating system. o Strap CMB port 1 for a modem and connect a CMB cable to a synchronous modem or modem eliminator. o Go into multi-user mode and select the communications sub-menu from the main menu. o Select the 3270 Bisync option to configure the 3270 devices and the 3270 cluster controller addresses. o 3270 Emulation can then be activated by specifying the device address. 4.4.4 Documentation For detailed information, please refer to the "BOSS/IX 3270 BSC Emulation User Reference Manual", M6358. The following information is a list of known problems and warnings SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg030 relating to Level 7.2A*. 5.1 GENERAL WARNINGS o Upgrade installation of the 7.2A Operating System, Utilities and BASIC require a minimum of 3 MB of free disk space to complete before csave conversion have taken place. o The BASIC program file format has changed in 7.2A. Programs created under the 7.1A/B environment will be unusable in 7.2A unless converted using the operating system command 'csave'. Converted programs can be expected to grow in size by 20%. o A memory management error will occur when running 1/2" and 1/4" tape devices at the same time. o You are unable to OPEN the system console 'TO' form BASIC. o Escape during processing of an EXECUTE command can cause the next EXECUTE to abort the program. o BASIC directives using key-FID(0) with an ERR= list incorrectly, i.e. WRITE(1,KEY=FID(0), ERR=10) list as WRITE(1,KEY=FID(0,ERR=10)) o BASIC issues ERROR 26 for "DEF FNA(N) = N" and not for "DEF FNA(N)=N" o BLINK MISMATCH occurs on small start size. o GOTO's /EXITTO's / RETURN's followed by a semicolon, two spaces and REM fail. o 'frepair' - reports an empty program file (no code) as type ENCRYPTED. o 'mcsrestore' - final report lacks message noting files not restored. o 'fcreate' - does a linefeed after each 9 characters of the file name being input. o 'pparams' - if admin modifies a class, previously changed access rights are reset to rw. rw. o BASS - cannot specify slave printer for Burn-in. 5.2 WORKAROUND BY PRODUCTS 5.2.1 OPERATING SYSTEM (EOS) PROBLEM: The busy flag is sent from the Whisper printer if a line is greater than 118 characters. This busy flag could cause the printer to delay at the end of a print line. WORKAROUND: Setting up the Whisper as an ISP will prevent the busy flag from the printer to be sent causing the delay. PROBLEM: The system will slow down after the upgrade if the line in '/etc/startup' that starts the remote service manager '/lan/lan init' is not SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg031 removed. WORKAROUND: If upgrading the system ensure that step 1 under section 2.3 is followed to remove this line. PROBLEM: The parameters set for input buffers and type-ahead buffers in the 'vconf' files might have the numbers in them. WORKAROUND: After the update do a 'vconf' of your 'conf' files. If any of them are incorrect change them using the 'vconf' command. 5.2.2 UTILITIES (EUT) PROBLEM: 'bsearch' will fall out with an error 47 if the program size is at a 512 border. WORKAROUND: If during 'bsearch' you receive an error 47 check the program size. If it is a 512 border add a 'REM' statement and re-save it to enlarge the program off the 512 border. 5.2.3 BASIC (EBS) PROBLEM: BASIC will save a program name with a space but the utilities will not support it. WORKAROUND: Ensure that when you are creating BASIC program files there are no spaces. PROBLEM: System directives can be used as a variable name if a 'LET' is not used. (Ex: "LET PRINT=127" No error, but "PRINT=127" This will produce an error=20) WORKAROUND: System directives should not be used as variable names. 5.2.4 DIAGNOSTIC (DIA) PROBLEM: 'dutil' will destroy the configuration record during a surface analysis. WORKAROUND: After doing a format of the disk re-install the system configuration record. 5.2.5 27XX/37XX BATCH EMULATION (EBC) PROBLEM: Data containing the message 'EOF RECVD' may be routed to a print or punch XXXnnn file. This problem occurs occasionally when a system has just transferred a file in FILE TRANSFER mode and is expecting to receive a file in TEXT or TRANSPARENT mode. WORKAROUND: Delete the incoming file containing 'EOF RECVD'. PROBLEM: If EBC is run without the proper key installed, the error message displays on the screen but is not recorded in the local status log. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg032 WORKAROUND: If problems are occurring with EBC, run in an attended mode and monitor the bcom display status. If the message displays "BAD PUBLIC KEY", install the correct public key. PROBLEM: Files with record lengths greater than 510 bytes may contain corrupted data when received in FILE TRANSFER mode using the EXPANDED TRANSPARENCY terminal options. WORKAROUND: Use any of the other terminal options to send the file in the FILE TRANSFER mode. 5.2.6 FILE TRANSFER FACILITY (FTF) PROBLEM: When there is heavy activity on the system, enough to cause swapping of processes, abort 79's can occur. WORKAROUND: Use the re-scheduling option of FTF or decrease system activity during file transmissions. PROBLEM: If an attempt is made to transfer a locked file, the name of the file is not displayed in the status log and the aborted completion code is incorrect. WORKAROUND: Schedule files when they are not locked. PROBLEM: Files scheduled with the 'high' priority option are sometime scheduled as 'normal' priority. This occurs if there are active transfers in progress when the high priority file was scheduled. WORKAROUND: Reschedule the file with the 'high' priority option. 5.2.7 MAGNET (ENT) PROBLEM: Concurrent FTF and MAGNET activity can cause error -527 conditions for the MAGNET operation. WORKAROUND: Decrease system and transmission load or re-try MAGNET activity. PROBLEM: ESCAPE'S during remote operation can cause BASIC error 95 or 255 conditions. WORKAROUND: ESCAPE processing problems will be addressed in a future release. On 7.2A, refrain from using ESCAPE's during remote operations. PROBLEM: A LAN timeout error, -554, can occur with heavy system activity where processes are being swapped. WORKAROUND: Re-try the operation within the application or decrease system activity. PROBLEM: RCOPY to update a remote file will write over the destination file even if it is locked. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg033 There is no warning message that the destination file will be overwritten as soon as it is unlocked. WORKAROUND: None. Rcopy to replace existing remote files will always overwrite the destination file. 5.2.8 3270 BISYNC (B32) PROBLEM: The word 'SYSTEM' was inadvertently removed from the 3270 Emulator utilities. WORKAROUND: None. Be aware that portions of the utilities may be missing the word 'SYSTEM'. (e.g. in the printer authorization of the local configurator, (0) should read (0)SYSTEM) PROBLEM: The printer emulator cannot accept more than 1 block of data from the host unless an EOT is sent between each block. WORKAROUND: None. This should not be a problem unless large streams of data are sent to the printer. PROBLEM: When using a switched (dial-up) line, the 3270 emulation may appear at times to have stopped. WORKAROUND: When using a switched line, it is the operator's responsibility to monitor the condition of the phone connection. If 3270 activity appears to have stopped, verify the modem connection and re-dial if the line has dropped. PROBLEM: During a 3287 printer operation, the status line may display 'PRTNG' for an extended period of time with no printer activity. WORKAROUND: Error conditions for printers are not tracked at the emulator level. If printer activity is not occurring as expected, check the condition of the printer. This is true for both spooled and non-spooled printers. 6.0 HELPFUL HINTS FOR 7.2A 6.1 Saving errors found during conversion from 7.1 BASIC to 7.2A BASIC to a file. At the end of the installation procedure of the 'EBS' (BASIC) package you will be asked if you wish to convert your BASIC programs at that time. If you answer yes to the question the procedure will go ahead and convert all the BASIC programs on the system to the 7.2A format. This procedure will report the results of the conversion to the terminal. If you wish a copy of the errors found to be written to a file and not to the terminal perform the following procedure: 1. Answer 'n' to the prompt to convert BASIC programs at the end of the installation of the 'EBS' package. 2. Use the command 'csave / -r %% /filename (Where filename is any name you wish.) This command will place a copy of all errors found during the conversion into the file 'filename'. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg034 3. To print this file to a printer use the command 'lpr /filename'. To print this file to a terminal use the command 'p /filename'. Steps 2 and 3 can be used to write errors to a file any time a 'csave' of newly installed 7.1 BASIC programs is required. 6.2 Approximating A System's Memory Requirement This section describes how to approximate the amount of memory a system needs. Table 6A shows four standard system configurations which can be used to approximate the amount of memory a system needs. The number of users (terminals), ghost tasks, and printers differ for each of these standard configurations. First, find the standard configuration that most closely matches the system in question, by scanning down the user/terminals, ghost task, and printers columns. Second, scan across the table to the memory-needed and memory-boards columns; this is the system's memory requirements. Note: Table 6A assumes that the system in question will be executing 60% BASIC and BASIC applications programs, and 40% non-BASIC applications. If the system will be executing a higher percentage of non-BASIC programs, it will need more memory. Table 6B shows how to set up the BOSS/IX configuration ('vconf') parameters for each of the four standard system configurations in table 6A. In other words, if one uses the approximation method to determine a system's memory requirements, table 6B can be used to set up the BOSS/IX configuration parameters. The approximation method is an easy and accurate way to determine a system's memory needs, if its configuration is close to one of the standard configurations. However, if it does not closely fit one of the configurations in table 6A, the calculation method in section 7 should be used. _Standard _ User/ _ Ghost _ Printers _ Memory _ Memory _ _Configuration _ Terminals _ Tasks _ _ Needed _ Boards _ _ _ _ _ _ _ _ _ Number 1 _ 2 _ 0 _ 1 _ .75MB _ 3 _ _ _ _ _ _ _ _ _ Number 2 _ 5 _ 1 _ 2 _ 1.00MB _ 4 _ _ _ _ _ _ _ _ _ Number 3 _ 9 _ 2 _ 2 _ 1.25MB _ 5 _ _ _ _ _ _ _ _ _ Number 4 _ 12 _ 3 _ 3 _ 1.50MB _ 6 _ Note: 1 MB (Megabyte) = 1024 KB (Kilobyte) = 1024 * 1024 bytes Table 6A Approximating the Memory Requirements for an MAI 2000 System _ 'vconf' BOSS/IX _ Standard Configuration (see Table 6A): _ _ Parameter _ _ _ _ _ _ _ _ _ _ number 1 _ number 2 _ number 3 _ number 4 _ _ _ _ _ _ _ _ buffers= _ 20 _ 28 _ 44 _ 56 _ _ _ _ _ _ _ _ printers= _ 1 _ 2 _ 2 _ 3 _ SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg035 _ _ _ _ _ _ _ procs= _ 31 _ 45 _ 72 _ 80 _ _ _ _ _ _ _ _ tsegs= _ 20 _ 28 _ 44 _ 56 _ _ _ _ _ _ _ _ sockets= _ 6 _ 6 _ 6 _ 6 _ _ _ _ _ _ _ _ dsockets= _ 8 _ 14 _ 20 _ 26 _ _ _ _ _ _ _ _ lanbuffers= _ 8 _ 12 _ 16 _ 16 _ _ _ _ _ _ _ _ locks= _ 74 _ 84 _ 109 _ 129 _ _ _ _ _ _ _ _ ibsize= _ 512 _ 512 _ 512 _ 512 _ _ _ _ _ _ _ _ tbsize= _ 64 _ 64 _ 64 _ 64 _ _ _ _ _ _ _ _ mfsys= _ 3 _ 3 _ 3 _ 3 _ _ _ _ _ _ _ _ lus= _ 136 _ 184 _ 286 _ 354 _ _ _ _ _ _ _ _ opens= _ 60 _ 77 _ 120 _ 157 _ _ _ _ _ _ _ _ eventcalls= _ 74 _ 85 _ 111 _ 132 _ 7.0 MEMORY USAGE This section describes how to calculate the optimum memory requirements for your MAI 2000 system configuration. Your system's memory requirements are based on the hardware options (such as number of terminals and printers) and software packages (such as BASIC, BASIC applications, utilities, EBC, etc.). You can use your system with less than optimum memory. However, it will run slower because application tasks must be swapped between main memory and disk. This section details the steps used to calculate the amount of memory required to avoid swapping of application tasks. 7.1 Calculating Your System's Memory Requirements This section describes how to calculate the number of memory boards your system requires for optimum performance. Step 1 To compute the memory required, add the following numbers: 220 KB This is the memory required for the BOSS/IX operating system program. 51 KB* This is the memory required for the operating system's dynamic work space. 30 KB* This is the memory required by BOSS/IX for table space for the base configuration: two users (terminals), one printer, and no ghost tasks. You will need to allow more memory for table space for each additional user as described later in this formula. How to calculate the exact amount of memory required for table space is explained in section 7.2. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg036 7 KB* Add 7 KB for BOSS/IX table space for each ghost task in the system. 1 KB* Add 1 KB for BOSS/IX table space for each additional printer above the one that is included in the base system. 100 KB Add 100 KB for memory allowance for swap-able system tasks including a printer de-spooler process, a system update process, a system error log process and two command interpreters. These processes can be swapped with each other without affecting the application processes. 30 KB Add 30 KB for each additional printer de-spooler above the one that is allocated in the base system. 15 KB Add 15 KB for each user that will be executing tasks concurrently. For example, if you have ten operators who are allowed to login but your system only has five terminals, you will have a maximum of five users at any one time. If some of your terminals are infrequently used, you don't need to allocate 15KB for an operator on that terminal. 160 KB Add 160 KB for each unique non-BASIC tasks that will be executed concurrently on your system. Such tasks include the BASIC interpreter (you need one BASIC interpreter task to support any number of BASIC programs), the utilities, Informix, communications, the command interpreter, etc. When computing the memory required for application tasks, you should consider how often each application is used. For example, if you seldom execute the commands or the utilities, you do not need to allocate memory for them. When they are executed, system performance will slow, but this is probably acceptable. 60 KB Add 60 KB for each BASIC program. This space is the allowance for the data and stack segments for each BASIC program. 64 KB Add 64 KB for each ghost task that will be executed concurrently. The result of the sum is your system's "memory requirement". (* The items marked with an '*' above are memory required for BOSS/IX operating system table space. These numbers are an approximate allowance for table space memory. In section 7.2 a method is given for computing the exact size of the table space required.) Step 2 Decide how much swapping of application programs you can allow on your system. Swapping slows speed of execution. If you want to run without swapping, you must provide the entire memory requirement that you computed in step 1. If cost of memory is more important than speed, multiply your system's memory requirement by 0.7. (Memory requirement x 0.7) This number will result in a system where application programs must be swapped. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg037 You can also multiply the memory requirement by some number between 0.7 and 1.0. The closer to the full memory requirement that you provide, the less swapping will be necessary. The result of this calculation is your system's "memory need". Step 3 You can now compute the number of memory boards required for your system needs by dividing the memory needed by 256KB, the amount of a single board (memory needed/ 256KB). If a fraction results, you should round the result to the next highest whole number. A maximum of six memory boards can be installed in the MAI 2000 system, three boards come standard in all MAI 2000 base systems. If your figures show that you need more than six memory boards, even with the 0.7 factor that allows some swapping of application tasks, you are overloading your system! 7.1.1 Example of How to Calculate a System's Memory Requirement This example shows how to compute the memory requirements for a system with 5 terminals and two printers. Four of the terminals are dedicated to running BASIC applications: accounts receivable, accounts payable, payroll and word processing. The fifth terminal is used to run the utilities, the commands, or the Informix database application. One of the applications uses a ghost task to output reports to a printer. Step 1 Add these numbers to compute "memory required" 220 KB Base operating system 39 KB Table space for base system 51 KB OS dynamic work space for base system 7 KB x 3 Allowance for table space for three additional users (total of 5 users/terminals) 7 KB Allowance for table space for one ghost task 1 KB Allowance for table space for an additional printer (total of two printers) 1.5 KB x 22 Allowance for dynamic work space for three additional users (i.e. 45 "procs", 23+22) 100 KB Allowance for system processes 30 KB Allowance for concurrent printing to the second printer 160 KB x 2 Allowance for the BASIC interpreter and for the utilities/command/Informix 60 KB x 4 Allowance for four concurrent basic applications 64 KB Allowance for one ghost task Total = 1126 KB = "memory required" Step 2 Compute "memory needed" If you don't want to allow swapping of application tasks, memory needed is the same as memory required: Memory needed = 1126 KB If some swapping of application tasks is acceptable: Memory needed = 1126 KB * 0.7 = 788 KB SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg038 Step 3 Compute the number of memory boards required No swapping: 1126 KB /256 KB = 4.3 boards Rounding to the next highest whole number, this means that the example system needs five memory boards. Five memory boards allows for extra memory that can be used for additional applications. However, system performance would probably be adequate (little swapping) with four memory boards. Swapping allowed: 788 KB / 256 KB = 3 boards The system needs three memory boards to operate with some swapping. 7.2 Exact Method for Calculating BOSS/IX Table Space and Dynamic Work Space This section describes how to calculate the size of the operating system table space and size of the operating system dynamic work space needed by any configuration. Table 7A shows the amount of memory allocated for each operating system configuration parameter; it shows the parameters for the base system configuration; it shows how the 39 KB value for table space, used in section 7.1, was calculated; and it shows the parameters and total table space required for the example system depicted in section 7.1.1. To determine the table space for any configuration multiply the value of each configuration parameter by its corresponding memory allowance (see column 1, table 7 A). Next, add the result of these calculations (see column 2). The result is the allowance for table space. To determine the memory allowance for operating system dynamic work space use the following formula: "dynamic memory" (bytes) = (32+("opens"/4) + (("procs" * 2688) / 512 / 2 )) * 512 The variables in the formula from right to left are: 32 - The number of 512 byte pages for miscellaneous operating system space "opens" - The number of open files configured "procs" - The number of processes configured 2688 - The size (bytes) for each process's user area / 512 - For converting into 512 byte pages / 2 - One half the number of pages *512 - For converting pages into bytes For the base configuration the dynamic memory allowance is: "dynamic memory" (bytes) = (32 + (40 /4) + (( 23 * 2688) / 512 / 2)) * 512 = 52416 bytes or 51 KB _ _memory _param.'s_total _param.'s_total _ _BOSS/IX _used for_for base_memory _for _memory _ _PARAMETERS _each _config- _for base_example _for _ _(set by _param. _ uration_system _system *_example_ SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg039 _"vconf") _(bytes) _system _(bytes) _ _system _ _ _ _ _ _ _(bytes)_ _ _ _ _ _ _ _ _buffers= _ 586 _ 16 _ 9376 _ 28 _ 16408 _ _printers= _ 228 _ 1 _ 228 _ 2 _ 465 _ _procs= _ 284 _ 23 _ 6332 _ 45 _ 12780 _ _tsegs= _ 20 _ 16 _ 320 _ 28 _ 560 _ _sockets= _ 600 _ 6 _ 3600 _ 6 _ 3600 _ _dsockets= _ 600 _ 8 _ 4800 _ 12 _ 7200 _ _lanbuffers= _ 400 _ 8 _ 3200 _ 10 _ 4000 _ _locks= _ 30 _ 64 _ 1920 _ 84 _ 2520 _ _ibsize= _ 512 _ _ 1024 _ _ 2560 _ _tbsize= _ 64 _ _ 128 _ _ 320 _ _mfsys= _ 424 _ 3 _ 1272 _ 3 _ 1272 _ _lus= _ 40 _ 96 _ 3840 _ 182 _ 7280 _ _opens= _ 86 _ 40 _ 3440 _ 76 _ 6536 _ _eventcalls= _ 20 _ 64 _ 1280 _ 83 _ 1660 _ _ _ _ _ _ _ _ _TOTALS _ -- _ -- _ 39760 _ -- _ 67161 _ _ _ _ _ 39KB _ _ 65KB _ _ _ _ _ _ _ _ 8.0 Level 7.2A Base Product File Usage Guide This section contains a list of the Level 7.2A base product files with a brief functional description and a list of dependencies for each file. From this a user may determine the usefulness of each file. He/she then may delete files that are not needed for their systems operation. This section is only a quick reference guide to the function and inter-dependencies of Level 7.2A base product set. Be aware that there may exist a program not mentioned in this section that may use a command or utility in one of the base products described in this section. Programs and files should only be removed from a system in special cases. ------- LEGEND ------- DIR..........Directory file. CODE.........68000 code file. Usually a command or utility program. TEXT.........A string or serial file consisting of printable/editable ASCII data. BINARY.......Any file consisting of unprintable ASCII data. KERNAL.......Any stand-alone bootable operating system or diagnostic program for the MAI 2000. BAS..........BASIC program file. SIZE.........Size of the file. File size values are in units of 1024 bytes (1k bytes). ---------------- DEPENDENCY CODES ---------------- (1) REQUIRED.......Absolutely required for system to function. (2) REQUIRED.......Required by another program or sub-system to function, but otherwise not absolutely required by the system. (3) OPTIONAL.......User friendly utility. (4) OPTIONAL.......Novice command. (5) OPTIONAL.......Expert (non-advice) command or utility. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg040 NOTE: (2)-(5) may be removed from the system depending on desired system functionality. NOTE: [see filename] means that some degree of duplicate functionality exists between the command or utility and the command or utility specified by 'filename'. WARNING: Expert and novice commands should be used with care as they may alter the operation of your system. FILENAME TYPE SIZE DESCRIPTION DEPENDENCIES /bin DIR 8k System/user command (1) REQUIRED directory. /bin/addname CODE 19k Add a link to a file. (5) OPTIONAL - Only used to add a link. /bin/admin CODE 25k Changes privilege to those (4) REQUIRED - Required if of the system administrator. '-secure' flag set in sy stem . configuration file and ' admin' user has non-null passwo rd. [see /bin/login]. /bin/advance CODE 21k Advances an eventcount. (5) OPTIONAL /bin/basic CODE 334k BASIC language. (2) REQUIRED - Required to execute system BASIC pro gram. The files /util/bxref, / util /prenumber, /util/bsearc h, /util/bcompare, /util/be ncrypt and /util/bmerge use /bi n /basic. /bin/cat CODE 20k Concatenates files. Often (4) OPTIONAL used to dump the contents of [see /bin/p or /bin/pr] a file to a terminal. /bin/change CODE 23k Substitutes strings in files (4) OPTIONAL (search/replace). /bin/chown CODE 20k Changes the owner of a file. (4) OPTIONAL [see /util/dsecure] /bin/command CODE 46k Command shell. (1) REQUIRED - Used by s ubr fexec(), used by basic,. '/bin/login', etc... /bin/copy CODE 28k Copy a file. (2) REQUIRED - Required by SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg041 /bin/move command and by install procedures. [see /util/fcopy] /bin/cpw CODE 27k Change password. (4) OPTIONAL - Required if system secure or passwor d account protection is de sired. [see /util/oprinfo] /bin/csave CODE 124k Converts 7.1 BASIC programs (5) OPTIONAL - Needed to con- to 7.2A BASIC program format. vert 7.1 programs to usa ble Lists a program in 7.1 7.2A format. format. /bin/csave.cpl CODE 139k csave command compiles (5) OPTIONAL - Required by LISTed 7.1 BASIC programs '/bin/csave'. into 7.2A BASIC programs. [see /bin/csave] /bin/date CODE 25k Set/display system time/date (1) REQUIRED - Date used by /etc/sinit to set time/d ate at system startup. [see /util/sdate] /bin/debe CODE 24k Copies the specified input (2) REQUIRED - Used by E OS to the specified output install procedures (i.e. in- . performing the requested stalls floppy or disk lo aders) conversion. Used to store system dum ps to floppy disk when (boot p arti- tion only). [see /sys/putloader] /bin/delete CODE 22k Deletes files or links to (1) REQUIRED - Used by i nstall a file. 'delete' can be procedures. Also used a t used to delete an empty system startup by comman d file directory. 'etc/startup'. [see /util/fdelete] /bin/devfmt CODE 22k Formats a floppy disk. (5) OPTIONAL - Used only for floppy disk formatting. [see /util/sformat] /bin/diff CODE 26k Displays the difference (4) OPTIONAL between two files. Often used to compare a backup version of a text file to a newer version of the same SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg042 text file. /bin/diskusage CODE 22k Displays number of disk (4) OPTIONAL - 'ls' com mand blocks (512 bytes) used by and 'info' utility can also a directory and it's contents. display number of block s used but only on a file by f ine basis. [see /bin/ls -blks] [see /util/finfo] /bin/dump CODE 21k Provides a hexadecimal/octal/ (5) OPTIONAL ascii dump of a file or input stream. /bin/echo CODE 18k Displays arguments. (1) REQUIRED - Used by i nstall procedures. /bin/exec CODE 27k Execute a program. (1) REQUIRED /bin/filemodes CODE 18k Sets of changes access modes (5) OPTIONAL - for a file. [see /util/fsecure] /bin/fschk CODE 77k Checks or repairs a file (1) REQUIRED system. /bin/install CODE 21k Installs an MAI 2000 product. (1) REQUIRED /bin /install key CODE 18k Changes a install key for a (3) OPTIONAL - User may use MAI 2000 product. 'ved' text editor or 'ch ange' command to change the pr oduct key. [see /bin/change or /bin /ved] /bin/kill. CODE 19k Terminates a process. (1) REQUIRED - If remove d . there is no other way (v ia command or utility) to t ermin- ate a process on the sys tem. /bin/kychk CODE 39k Check or repair a KEYED file (1) REQUIRED either SORT or DIRECT. /bin/login CODE 34k Login command. (1) REQUIRED /bin/lpmaint CODE 43k Maintenace program for (2) REQUIRED - May be re moved printer queues. if no printers desired o n sys- tem. Used at system sta rtup SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg043 time to fix the printer queues. [see /util/pqueue] /bin/lpq CODE 35k Displays a printer queue's (4) OPTIONAL - status. [see /util/pqueue] /bin/lpr CODE 59k Enqueues files for printing. (4) OPTIONAL - [see /util/psubmit] /bin/lpstat CODE 24k Display status of all (4) OPTIONAL - printers. [see /util/pstatus] /bin/ls CODE 32k Display contents of a (4) OPTIONAL directory. [see /util/finfo] /bin/makedev CODE 20k Creates a device file. (5) OPTIONAL - This is t he only way to create a dev ice file. /bin/makedir CODE 19k Creates a directory. (5) OPTIONAL - [see /util/dcreate] /bin/makeec CODE 19k Creates an eventcount file. (5) OPTIONAL - This is t he only way to create a use r eventcount file. /bin/makefs CODE 22k Creates and initializes a (1) REQUIRED file system. /bin/makesta CODE 22k Create a station file. (5) OPTIONAL /bin /makettymntbl CODE 22k Compile a terminal mnemonics (5) OPTIONAL - Needed to table text file. configure a new type ter minal on the system. /bin /makettyxlate CODE 22k Create a terminal translate (5) OPTIONAL - Needed to file. configure a new type ter minal on the system. /bin/match CODE 24k Searches for a pattern in a (4) OPTIONAL file. /bin /mcscompare CODE 42k Compares files on 1/4" (4) OPTIONAL cartridge streamer tape to [see /util/mcscompare] files on disk. /bin/mcslabel CODE 30k Labels a 1/4" cartridge tape. (4) OPTIONAL [see /util/mlabel] /bin/mcslist CODE 38k Displays files on a 1/4" (4) OPTIONAL cartridge tape. [see /util/mcslist] /bin SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg044 /mcsrestore CODE 57k Copies files from a 1/4" (4) OPTIONAL cartridge tape. [see /util/mrestore] /bin/mcssave CODE 55k Copies files to a 1/4" (4) OPTIONAL cartridge tape. [see /util/msave] /bin/mount CODE 22k Mounts a file system. (1) REQUIRED /bin/move CODE 24k Renames a file or moves a (4) OPTIONAL a file across files systems. [see /util/fmove or /bin/frename] [uses /bin/copy] /bin/p CODE 24k Paginates text and filters (4) OPTIONAL non-printable characters. [see /bin/pr or /bin/cat] /bin/pmask CODE 19k Displays default filemodes (5) OPTIONAL mask. /bin/pr CODE 25k Paginates a file. (4) OPTIONAL [see /bin/p or /bin/cat] /bin/ps CODE 27k Displays process status. (5) OPTIONAL /bin/pted CODE 44k Modifies/displays printer (5) OPTIONAL translation tables. /bin/pwd CODE 20k Displays the current working (1) REQUIRED directory. /bin/shutdown CODE 25k Shuts down the system from (1) REQUIRED multi-user mode. /bin/sort CODE 26k Sorts the contents of a file. (2) REQUIRED [used by /util/*] /bin/space CODE 23k Displays amount of free space (5) OPTIONAL on a file system. /bin/suspend CODE 19k Suspends execution of a (5) OPTIONAL process. /bin/sysinfo CODE 22k Display booted OS version, (5) OPTIONAL system serial number and initial system configuration information. /bin /ttymntbl CODE 19k Set terminal mnemonics table. (5) OPTIONAL /bin/ttymodes CODE 23k Displays or sets a terminal's (5) OPTIONAL modes. /bin/ttyxlate CODE 19k Sets terminal translation (5) OPTIONAL tables. /bin/unmount Code 21k Dismounts a previously (1) REQUIRED mounted file system. /bin/usb CODE 25k Displays or sets super block (5) OPTIONAL - Used for alter- SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg045 nate system configuratin g. /bin/vconf CODE 24k Displays or sets the system (5) OPTIONAL - Used for alter- configuration file. nate system configuratin g. /bin/ved CODE 66k Full screen editor for text (5) OPTIONAL files. /bin/who CODE 20k Displays the users currently (5) OPTIONAL logged in. /bin/write CODE 24k Sends a messge to a logged (5) OPTIONAL in user. /dev DIR 4k System device directory. (1) REQUIRED /dev/boot DEV 0 Hard disk 0 boot partition (1) REQUIRED - Used to mount device (buffered). Boot par- the boot partition. tition used for system install and system repair. ('may be mounted') /dev/clock DEV 0 System clock special event (1) REQUIRED count device. /dev/cs DEV 0 Cartridge streamer tape (2) REQUIRED - Required only device. for systems with a cartr idge streamer tape drive. /dev/fd0 DEV 0 Floppy disk device (buffered) (2) REQUIRED - Required only . (may be 'mounted') for systems with floppy disk drives. /dev/kmem DEV 0 Kernel memory device. (1) REQUIRED /dev/null DEV 0 NULL device (1) REQUIRED /dev/rboot DEV 0 Hard disk 0 boot partition (2) REQUIRED - Required only device (unbuffered). Boot for systems with a flopp y disk partition used for system drive. install and system repair. (may NOT be 'mounted') /dev/rfd0 DEV 0 Floppy disk device (2) REQUIRED - Required only (unbuffered). for systems with a flopp y disk drive. /dev/root DEV 0 Hard disk 0 root partition (1) REQUIRED device (buffered). /dev/rroot DEV 0 Hard disk 0 root partition (1) REQUIRED SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg046 device (unbuffered). /dev/rwd0 DEV 0 Hard disk drive 0 (unbuffered). (1) REQUIRED /dev/rwd1 DEV 0 Hard disk drive 1 (unbuffered). (1) REQUIRED /dev/swap DEV 0 Swapper device disk (1) REQUIRED partition (unbuffered). /dev/tty0 DEV 0 Console device file. (1) REQUIRED There will be a device '/dev/ ttyN' for every terminal port on the system. If a slave printer is configured on a particular terminal '/dev/ttyN' then it's corresponding printer device is '/dev/lN'. There may also be devices of the form '/dev/lp', '/dev/pN'... /dev/wd0 DEV 0 Hard disk drive 0 (buffered). (1) REQUIRED /dev/wd1 DEV 0 Hard disk drive 1 (buffered). (1) REQUIRED /doc DEV 1k On-line documentation (2) REQUIRED - Required only directory. if on-line deocumentatio n desired. /doc/cmds TEXT 1k Help text file directory (2) REQUIRED - Required only for commands. if command help text fil es desired. /ved.help. TEXT 30k Help text file for ved (2) REQUIRED - Used by ' ved' command. command. Not required i f no on-line help text is des ired. [see /bin/ved] /etc DIR 2k System/application data (1) REQUIRED and configuration file directory. /etc/ ptemps DIR 2k Default directory for (2) REQUIRED - Only if p rinter printer spool files. despooling is desired. . /etc/ queues DIR 2k Queue file directory for (2) REQUIRED - Only if p rinter spooled printers. despooling is desired. /etc/perrors TEXT 8k Contains basic error text. (2) REQUIRED - May be de leted if detailed basic error message NOT desired. [see /bin/basic] /etc/class. TEXT 2k Class definition file for (2) REQUIRED - May be re SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg047 moved printers. if class option never us ed by the systems applications or if no printers configured o n the system. /etc /comerr.list TEXT 10k Error text for system commands (2) REQUIRED - Only if t he and user programs utilizing user wants descriptive e rror the comerr() subroutines. message for system comma nds '/bin/basic' and the utility and user programs. set each have their own error text files. /etc/conf BINARY 1k Backup copy of the default (1) REQUIRED system configuration record used during system boot is located on the 'boot' partition. /etc/defaults TEXT 1k Printer configuration file. (2) REQUIRED - May be re moved Contains default values for if NO printers desired o n the the system, individual users system. and printers. /etc/diskdesc DIR 1k May contain hard disk super (1) REQUIRED block definition files. /etc/exem TEXT 1k This file is displayed on a (4) OPTIONAL - May be de leted terminal that is not in use. if no message desired. Used by system control program ('etc/start') /etc/forms TEXT 1k Contains form definitions for (2) REQUIRED - May remov e this . printers. file if no printers desi red on the system. /etc/level DIR 1k System software revision /etc/level/EBA TEXT 1k EBA (BASS diagnostic) product (2) REQUIRED - Remove th is software revision level file. file only if entire EBA pro- duct removed from the sy stem. /etc/level/EOS TEXT 1k EOS (operating system base) (1) REQUIRED product software revision level file. /etc/level/EUT TEXT 1k EUT (utilities) product (2) REQUIRED - Remove th is SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg048 . software revision level file. file only if entire EUT pro- duct removed from the sy stem. /etc/logm. TEXT 1k This file is displayed when (4) OPTIONAL - May be de leted user is prompted to login if no login message desi red. by '/bin/login' command. /etc/lpstart TEXT 42k This program (executed only (2) REQUIRED - May be re moved by '/etc/start') initializes only if printers are not de- system printers. sired. [see '/etc/start'] /etc/mailboxes DIR 1k A directory for future inter- (1) REQUIRED active mail sending and receiving program. /etc/maillists DIR 1k Global distribution list (1) REQUIRED - Used by directory. '/bin/write' command and message() subroutine. [see '/bin/write'] /etc/motd TEXT 1k Message of the day file. (4) OPTIONAL - May be d eleted Displayed after a successful if no message of the da y login by command '/bin/login'. display is desired. /etc/passwd TEXT 1k User account file. Contains (1) REQUIRED - Used by list of users for the system. '/bin/login', '/bin/com mand', For each user there exists: and system or user prog ram encrypted password, user id, requiring user account infor- home directory, initial mation. command. /etc/ports TEXT 1k Contains port configuration (1) REQUIRED. for the system. /etc/printers TEXT 1k Contains printer defaults. (1) REQUIRED. /etc/ptrans BINARY 41k Printer translation file. (1) REQUIRED - May be re moved only if printers are not desired. /etc/secure DIR 1k Contains file necessary to (2) REQUIRED - Required i f securing the system. system is ever to be 'sec ured'. /etc/secure /.locals TEXT 1k Local macro file. Contains (1) REQUIRED - Required if secure macro definitions. system is ever to be 'sec ured'. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg049 /etc/secure /EBA.s. TEXT 1k Command file. Secure EBA (2) REQUIRED - Required i f product. system is ever to be 'sec ured'. /etc/secure /EBS.s TEXT 2k Sets filemodes for EBS (2) REQUIRED - Required i f subproduct. system is ever to be 'sec ured'. /etc/secure /EOS.s TEXT 2k Command file. Secure EOS (2) REQUIRED - Required i f product. system is ever to be 'sec ured'. /etc/secure /EUT.s TEXT 2k Command files. Secure EUT (2) REQUIRED - Required i f product. system is ever to be 'sec ured'. /etc/secur /scr CODE 19k System command; executes *.s (2) REQUIRED - Required i f command files to 'secure' system is ever to be 'sec ured'. the system. /etc/sinit. TEXT 1k Command file. Executed at (2) REQUIRED - Needed to set system boot time. Usually system time and date at system used to set system time and boot time. May be remov ed if date and mount extra disk user sets time and date at partitions. some other time. /etc/shtdwn TEXT 1k Command file. Executed at (2) REQUIRED - May be re moved system shutdown. if empty. /etc/start TEXT 39k System control process. (1) REQUIRED Controls system startup and and shutdown as well as controlling user processes in multi-user mode. /etc/startup TEXT 1k System startup command file. (1) REQUIRED Executed when system is moved into multi-user mode. /etc/syschk CODE 28k System program to perform (1) REQUIRED auto file system checks and to handle system crash recovery. /etc/terminals TEXT 1k Terminal configuration file. (1) REQUIRED SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg050 /etc/ttymntbl DIR 1k Terminal mnemonics table file (1) REQUIRED directory. /etc/ttymntbl /vdt7270 BINARY 1k Mnemonics table for 7270 (1) REQUIRED display terminal. /etc/ttymntbl /vdt7270.mntbl TEXT 1k Mnemonics description source (1) REQUIRED - Needed to file for 7270 display create file 'vdt7270'. terminal. /etc/ttymntbl /evdt BINARY 1k Mnemonics table for 'evdt' (1) REQUIRED terminal. /etc/ttymntbl /evdt.mntbl TEXT 1k Mnemonics description source (1) REQUIRED - Needed to file for 'evdt' terminal. create file 'evdt'. /etc/ttymntbl /edt BINARY 1k Mnemonics table for 'edt' (1) REQUIRED terminal. /etc/ttymntbl /edt.mntbl TEXT 1k Mnemonics description source (1) REQUIRED - Needed to file for 'edt' terminal. create file 'evdt'. /etc/ttymntbl /other BINARY 1k Mnemonics table for other (1) REQUIRED type terminal. /etc/ttymntbl /other.mntbl TEXT 1k Mnemonics description source (1) REQUIRED - Needed to file for other type terminal. create file 'other'. /etc/ttyxlt DIR 1k Terminal translation file (1) REQUIRED directory. /mnt DIR 1k Mount point directory. (1) REQUIRED - A standar d mount point. /sys DIR 2k System program directory. (1) REQUIRED /sys/dummy CODE 1k Waits forever. (1) REQUIRED - Used by s ystem control program. [see /bin/start] /sys/errlog CODE 28k Display system device errors. (1) REQUIRED - Needed fo r Also logs system errors to system device diagnostic s disk. record. /sys/genres CODE 83k System program used by (2) REQUIRED - Required only install for floppy version if the floppy drive is u sed of install procedures. to install. [see /bin/install] /sys/lpd CODE 67k System despooler. Despools (2) REQUIRED - May be re moved SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg051 spooled print jobs. if no despooling is desi red. /sys/mcsbackup BAS 12k Basic program. Menu driven (4) OPTIONAL cartridge streamer backup program. /sys/update CODE 1k System program. Update the (1) REQUIRED file system every 30 seconds. Started by system control program to ensure system integrity. /tmp DIR 2k Temporary file directory. (1) REQUIRED /util DIR 2k Utilities/user command (3) OPTIONAL - Required if directory. utility programs are des ired. /util/CLSTBL BAS 2k BASIC utility subprogram (3) OPTIONAL - /util/bse arch which works with variable uses this file. tables. /util/CMPGM BAS 8k BASIC utility subprogram for (3) OPTIONAL - /util/bco mpare comparing BASIC programs. uses this file. /util/COMP BAS 4k BASIC utility subprogram for (3) OPTIONAL - /util/bco mpare comparing BASIC program. uses this file. /util/GRNTBL BAS 3k BASIC utility subprogram. (3) OPTIONAL - /util/bse arch uses this file. /util/HEAD BAS 2k BASIC utility subprogram. (3) OPTIONAL - /util/bxr ef, /util/bsearch, /util/bre number and /util/bcompare use t his file. /util/HERROR BAS 1k BASIC utility subprogram (3) OPTIONAL - /util/ben crypt and /util/bmerge use thi s file. /util/LSTMT BAS 4k BASIC utility subprogram (3) OPTIONAL - /util/bxr ef . which list statements. and /util/brenumber use this file. /util/OPNTBL BAS 3K BASIC utility subprogram (3) OPTIONAL - /util/bxr ef, which opens variable tables. /util/bsearch, /util/bre number and /util/bcompare use t his SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg052 file. /util/OSTMT BAS 3k BASIC utility subprogram. (3) OPTIONAL - /util/bse arch uses this file. /util/PLST BAS 4k BASIC utility subprogram. (3) OPTIONAL - /util/bxr ef uses this file. /util/PLSTO BAS 4k BASIC utility subprogram. (3) OPTIONAL - /util/bsr ef uses this file. /util/PLST1 BAS 8k BASIC utility subprogram. (3) OPTIONAL - /util/bxr ef uses this file. /util/PLST2 BAS 3k BASIC utility subporgram. (3) OPTIONAL - /util/bxr ef uses this file. /util/PLST3 BAS 3k BASIC utility subprogram. (3) OPTIONAL - /util/bxr ef uses this file. /util/PSRCH BAS 5k BASIC utility subprogram. (3) OPTIONAL - /util/bse arch uses this file. /util/RENUM BAS 9k BASIC utility which re- (3) OPTIONAL - /util/bre number numbers basic programs. uses this file. /util/REPL BAS 3k BASIC utility subprogram. (3) OPTIONAL - /util/bse arch uses this file. /util/SREP BAS 7k BASIC utility subprogram. (3) OPTIONAL - /util/bse arch uses this file. /util/bcompare CODE 166k BASIC utility to compare (3) OPTIONAL - /util/bxr ef two BASIC programs. must exist if this progr am is desired. /util/bdisplay CODE 169k BASIC utility to display a (3) OPTIONAL BASIC program. /util/bencrypt CODE 131k BASIC utility to encrypt a (3) OPTIONAL BASIC program. /util/biolib BINARY 16k Subroutines used by BASIC (3) OPTIONAL - used by / util /encrypt and /util/bmerg e. /util/bmerge CODE 166k BASIC utility to merge two (3) OPTIONAL - /util/bxr ef BASIC programs into one. must exist if this progr m is SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg053 desired. /util/brenumber CODE 166k BASIC utility to renumber a (3) OPTIONAL - /util/bxr ef . basic program. must exist if this progr am is desired. /util/bsearch CODE 166k BASIC utility to search or (3) OPTIONAL - /util/bxr ef search and replace strings must exist if this progr am in a BASIC program. is desried. /util/bxref CODE 166k BASIC utility to reformat (3) OPTIONAL - brenumbe r, (spruce) a BASIC program and bsearch, bcompare and b merge to generate a cross reference are 'addname' to this f ile. report of a BASIC program. /util/configure CODE 182k Utility to change usage of (2) REQUIRED - May be re moved systems and parallel ports. if no change in configur ation desired. /util/copydisk CODE 54k Utility to make an exact (3) OPTIONAL copy of a diskette onto another diskette. /util/dcreate CODE 54k Utility to create one or more (3) OPTIONAL sub-directories. [see makedir] /util/delete CODE 55k Utility to delete a directory. (3) OPTIONAL /util/ddisplay CODE 176k Utility to display directory (3) OPTIONAL contents. [see /bin/ls] /util/drestore CODE 177k Utility to copy back to the (3) OPTIONAL file system those files that have been saved to diskette by the "Save" utility. /util/dsave CODE 181k Utility to copy files to (3) OPTIONAL diskette(s). /util/dsaverot CODE 126k Utility to display a report (3) OPTIONAL of the files that were copied on a save set of diskettes. /util/dsecure CODE 61k Utility to change the access (3) OPTIONAL permission flags and/or owner [see /bin/filemodes or of a directory. /bin/chown] /util/fchange CODE 105k Utility to the actual and (3) OPTIONAL maximum size of a file. /util/fcopy CODE 169k Utility to copy files. (3) OPTIONAL [see /bin/copy] /util/fdelete CODE 162k Utility to delete one or (3) OPTIONAL SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg054 more files. [see /bin/delete] /util/filelist CODE 167k Utility to create, modify, (3) OPTIONAL delete and display filelists. /util/finfo CODE 169k Utility to display infor- (3) OPTIONAL mation for a file. [see /bin/ls] /util/fl DIR 1k Utilities file list directory.(3) OPTIONAL - Needed fo r filelist creation. /util/fl/EBA.f TEXT 1k EBA product file list (BASS (3) OPTIONAL - Filelist for diagnostic programs.) package EBA. /util/fl/EBS.f TEXT 1k EBS product file list (basic (3) OPTIONAL - Filelist for language and utilities). package EBS. /util/fl/EOS.f TEXT 1k EOS product file list (3) OPTIONAL - Filelist (base OS). for filelist package EOS /util/fl/EUT.f TEXT 1k EUT product file list (3) OPTIONAL - Filelist for (systems utilities). EOT package. /util/freespace CODE 127k Utility to report the free (3) OPTIONAL space on a file system. [see /bin/space] /util/frename CODE 54k Utility to rename a single (3) OPTIONAL file. [see /bin/move] /util/frepair CODE 182k Utility to repair a corrupted (3) OPTIONAL file. [see /bin/kychk] /util/fsdbg CODE 87k Utility for fixing and main- (3) OPTIONAL taining a file system. [see /bin/fschk] /util/logical. disk BINARY 3k Used before 7.2A*06 to convert (5) OPTIONAL logical disk directives in csave'd programs. /util/mcompare CODE 148k Utility to compare files on (3) OPTIONAL 1/4" cartridge tape to files [see /bin/mcscompare] on the file system. /util/menu CODE 60k Master menu program. (3) OPTIONAL /util/menuedit CODE 155k Utility to edit menus. (3) OPTIONAL /util/mlabel CODE 76k Utility to display or create (3) OPTIONAL a label for a 1/4" cartridge [see /bin/mcslabel] tape. /util/mlist CODE 149k Utility to list files saved (3) OPTIONAL to 1/4" cartridge tape. [see /bin/mcslist] /util/mn DIR 2k Contains tree of different (4) OPTIONAL utility menus. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg055 /util/mn/top BINARY 2k Top of tree for utility menus. (4) OPTIONAL /util/mn/ut BINARY 1k Utility menu set. /util/mn/ut. basic BINARY 4k Basic utility menu. (4) OPTIONAL /util/mn/ut. bcom BINARY 2k Batch Communication utility (4) OPTIONAL menu. /util/mn/ut. cisys BINARY 3k Cartridge inter-system utility (4) OPTIONAL menu. /util/mn/ut. comm BINARY 2k Communication utility menu. (4) OPTIONAL /util/mn/ut. dir BINARY 3k Directory utility menu. (4) OPTIONAL /util/mn/ut. file BINARY 5k File utility menu. (4) OPTIONAL /util/mn/ut. filesys BINARY 3k File system utility menu. (4) OPTIONAL /util/mn/ut. isys BINARY 3k Inter-system transport menu. (4) OPTIONAL /util/mn/ut. main BINARY 3k Main Utility menu. (4) OPTIONAL /util/mn/ut. net BINARY 2k Network utility menu. (4) OPTIONAL /util/mn/ut. printer BINARY 3k Printer utility menu. (4) OPTIONAL /util/mn/ut. save BINARY 4k Save utility menu. (4) OPTIONAL util/mn/ut. system BINARY 3k System operation utility (4) OPTIONAL menu. /util/mrestore CODE 207k Utility to copy files from (3) OPTIONAL 1/4" cartridge tape back to [see /bin/mcsrestore] the file system. /util/msave CODE 214k Utility to save file to (3) OPTIONAL 1/4" cartridge tape. [see /bin/mcssave] /util/oprinfo CODE 139k Utility to add or modify a (3) OPTIONAL system operator or passwords /util/pformchg CODE 129k Utility to change the form (3) OPTIONAL on a printer. /util/pparams CODE 153k Utility to change printer (3) OPTIONAL parameters. /util/pqueue CODE 139k Utility to display the queue (3) OPTIONAL for the specified printer. [see /bin/lpq] SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg056 /util/pstatus CODE 127k Utility to display the status (3) OPTIONAL of all printers on the system.[see /bin/lpstat] /util/psubmit CODE 132k Utility to send a file to the (3) OPTIONAL printer. [see /bin/lpr] /util/sdate CODE 60k Utility to display or change (3) OPTIONAL the time and/or date. [see /bin/date] /util/sformat CODE 55k Utility to format and create (3) OPTIONAL a file system on a diskette. [see /bin/devfmt makefs] /util/smount CODE 75k Utility to mount or unmount (3) OPTIONAL a file system. [see /bin/mount unmount] /util/stderror BINARY 11k Error messages for utility (3) REQUIRED - May be de leted programs. if utility programs are not desired. (i.e. all 'COD E' files in /util). /util/uthelp. ind BINARY 3k Help messages for utility (4) OPTIONAL - If omitte d, no programs. help facility will be av ail- able for utility program s. This file works in comju nc- tion with /util/uthelp.t xt. /util/uthelp. txt BINARY 271k Help messages for utility (4) OPTIONAL - If omitte d, no programs. help facility will be av ail- able for utility program s. This file works in conju nc- tion with /util/uthelp.i nd. /util/utmsg. ind BINARY 8k Messages for utility (3) OPTIONAL - May be de leted programs. if utility programs are not desired. (i.e. all 'COD E' files in /util). This f ile works in conjunction wit h /util/utmsg.txt. /util/utmsg. txt BINARY 71k Messages for utility (3) OPTIONAL - May be de SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg057 leted programs. if utility programs are not desired. (i.e. all 'COD E' files in /util). This f ile works in conjunction wit h /util/utmsg.ind. /util/workdir DIR 53k Utility to change the (3) OPTIONAL current working directory. [see /bin/cwd] ------------------ APPENDIX A ------------------ EXAMPLE USER ENVIRONMENTS: Systems without any floppy drives may have the following files deleted: /dev/fd, /dev/fd0, /dev/floppy, /dev/rfd0 /util/dsave, /util/drestore, /util/dsaverpt, /bin/devfmt, /sys/floppy, /sys/genres Systems without a streamer tape drive may have the following files deleted: /dev/cs, /util,mcompare, /util,mlabel, /util/mlist, /util/mrestore, /util/msave, /bin/mcscompare, /bin/mcslabel, /bin/mcslist, /bin/mcsrestore, /bin/mcssave, /sys/ncs, /sys/mcsbackup Systems without a printer may have the following files deleted: /util/pformschg, /util/pparams, /util/pqueue, /util/pstatus, /util/psubmit, /bin/lpmaint, /bin/lpq, /bin/lpr, /bin/lpstat, /etc/lpstart, /etc/printers, /etc/forms, /etc/defaults, /etc/class, /syste/lpd Systems with no need of diagnostic programs may have the following deleted: /sys/floppy, /sys/mcs, /sys/bass, /sys/bass/.*!* 9.0 NEW AND UPDATED MANUALS FOR LEVEL 7.2A The following is a list of the new and updated manuals for use with the MAI 2000 on Level 7.2A. These manuals and update packages are now available. M 6100A - Becoming Familiar with Your MAI 2000 (New updated manual) BFISD 6200A - MAI 2000 User Guide (Change package for present manual) M 6225A - MAI 2000 Technical Reference Guide (New updated manual) BFISD 6252D - MAI 2000 Business BASIC Reference Manual (Change package for present manual) M 6253A - MAI 2000 Business BASIC Quick Reference Card (New updated card) BFISD 6254A - MAI 2000 Business BASIC Utilities Reference Manual (Change package for present manual) 10.0 Lowest Acceptable Revision Levels (LARL) The following chart lists the LARLs applicable to the 2000 and its SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg058 peripherals. There is also a mention of any specific problems known to effect new functionality in level 7.2A. PCB Part Number LARL New Functionality MAI 2000 CCA and Controllers CMB, Central 903441 AP Microprocessor Board Memory 903368 A 4-Way Controller 903390 P MCS Controller 903406 T LARL required to ensure minimal MCS device problems. LAN Controller 903405 D 2 Board Disk 903439 B Controller Adaptec Board 907649 C 1 Board Disk 903496 D Required to support Controller overlapped seek performance enhance- ment in 7.2 Power Supply Input 903443 D Module Power Supply 903394 A Control Module Power Supply 903445 J Output Module Power Supply 907472 E Assembly Floppy Disk Drive 907584 A 50 MB Winchester 400549 A Disk Drive 140 MB Winchester 907790 A Disk Drive PCB Part Number LARL New Functionality EDT Terminal Logic Board 903462 V Slave Printing requires rev W. Firmware D Power Supply 400449-001 F EVDT Terminal SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg059 Logic Board 903373 AE Firmware F Power Supply 400449-002 F DT 4312 Terminal Logic Board 905323 C Firmware J Power Supply 400449-001 F DMP Printer Vendor Part Number Power Supply 115922 N Parallel Controller 110668 AB Board Mechanism Driver 110239 AD Board ORIGINATOR: MBF SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB010 Pg060 FIB 00011 05/14/86 *** COBAL 7.2A Software Announcement *** The following document details the installation requirements and procedures needed to run COBOL on the MAI\ 2000 system for BOSS/IX\ 7.2A. It is an implementation of RM/COBOL~, a defacto industry standard for small systems. Listed are the marketing codes available. SOFTWARE UPGRADES FROM 7.1 TO 7.2A WC057AB Compiler 1/4 -inch MCS tape WC058AB Runtime 1/4 -inch MCS tape WC061AB Compiler Diskette WC062AB Runtime Diskette COMPLETE SOFTWARE PACKAGE FOR 7.2A WC057AA Compiler 1/4 -inch MCS tape WC058AA Runtime 1/4 -inch MCS tape WC061AA Compiler Diskette WC062AA Runtime Diskette RM/COBOL is a registered trademark of Ryan-McFarland Corp. TABLE OF CONTENTS 1.0 Overview 2.0 Corrections and Enhancements 3.0 Requirements 4.0 Installation 5.0 Start Up 6.0 2000/8000 COBOL Differences 7.0 For Your Information 8.0 Warnings and Cautions 1.0 OVERVIEW COBOL consists of two packages, the COBOL compiler (CBD) and the COBOL runtime system (CBR). These are purchased separately and each requires a public key to execute. The packages contain one program each: CBD - /bin/cobol - COBOL compiler CBR - /bin/runcobol - runtime COBOL The compiler is installed on systems developing COBOL application programs. The runtime package is installed on systems that have applications written in COBOL and have already been compiled. 2.0 CORRECTIONS AND ENHANCEMENTS The 7.2A COBOL addresses the follow items: SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB011 Pg001 o SIZE option used with the DISPLAY directive left-justifies non- numerics. o The POSITION option in both the ACCEPT and DISPLAY directives has been corrected. o The four control bar keys have been mapped into what COBOL calls FUNCTION KEYS. o The COBOL clauses, BLINK, REVERSE, UNDERLINE, and CLEAR FOREGROUND now function as documented. o The default DISPLAY intensity is now compatible with COBOL low density. o The compiler will now accept any string in the SELECT name ASSIGN TO "string" clause. The runtime interpreter will look at the string. If the string appears in the table of synonyms linked into the runtime, then the output is piped to the matching program listed in that table. For example spooling to "LP": SELECT PRINT-LINE ASSIGN TO "PRINTER" The following is the list of synonyms that can be used for spooling. SYNONYM PRINTER PRINTER -----> LP PRINTER0 -----> P1 " " " " PRINTER9 -----> P9 3.0 REQUIREMENTS Disk Space: The COBOL package requires a total of 388 blocks (1.39 MB) on the root partition: 140 blocks (0.07 MB) for CBD and 248 blocks (1.32 MB) for CBR. Memory: COBOL requires a system with a minimum memory configuration of 768 KB. Each COBOL user requires 176 KB. Thus, up to 6 users can execute COBOL without swapping on a 1.5 MB system. Product dependencies: Requires current BOSS/IX~ level 7.2A operating system (EOS). 4.0 INSTALLATION SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB011 Pg002 The installation and upgrade procedures are identical and use the '/bin/ install' and '/bin/install key' programs. Logged on as System Administrator, install the savesets CBD (compiler) and CBR (runtime) from the COBOL tape or diskette using the install command. Example for tape: ADMIN> install cs CBD ADMIN> install cs CBR Example for diskette: ADMIN> install fd0 CBD ADMIN> install fd0 CBR After all the files have been copied to disk, the installation procedure prompts for the public key. Current Public Key: 12345678 Input 8-Character public key (cr=no change) Enter the public key, contained in the appropriate key certificate, and carriage return. The program then prompts for the key a second time. If you did not install your key during the normal installation, you can install it using the install key command. Ex: ADMIN>install key /etc/level/CBD ADMIN>install key /etc/level/CBR 5.0 START-UP The ved text editor is used to create COBOL source programs. Source programs must have the extension ".cbl". When a source program is compiled using the "/bin/cobol" program, the runtime code is placed in a file with the extension ".o", unless the object file is specified otherwise. A compiled COBOL program is executed using the "/bin/runcobol" program. Examples: user>cobol test - Will compile the source ved file "test.cbl" and create the object file "test.o" if no errors are found. user>runcobol test.o - Will execute the object file "test.o". Both the compilier and runtime package can be executed in single or multi-user mode. Further information about the COBOL compiler and runtime package is available in "MAI 2000 COBOL USER & REFERENCE GUIDE", BFISD 6356. 6.0 COBOL DIFFERENCES Reserved Words The following words are reserved in 2000 COBOL but not MPx COBOL. BACKGROUND CONVERT LOW SWITCH-n BEEP ECHO PARAMETERS TAB CLEAR FOREGROUND PRINT USER-LABEL COMP-1 HIGH PROMPT COMPUTATIONAL- 1 INSERT REVERSE SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB011 Pg003 The following words are reserved in MPx COBOL but not in 2000 COBOL. AUTO FULL SPOOL-COPIES TAPE-VOLUME-ID BELL ID SPOOL-JOB-NAME UPDATE COL PRINTER SPOOL-PRIORITY WAIT CONSOLE REQUIRED SWn CSn SCREEN SWITCHn CTP SPOOL-CLASS TAPE-FILE-ID The following words are reserved in 2000 and MPx COBOL but not in ANSI COBOL. BLINK EBCDIC PACK UNPACK COMP-3 ERASE SECURE COMPUTATIONAL-3 ESCAPE UNLOCK ANSI Debugging MPx COBOL supports ANSI debugging. 2000 COBOL does not support ANSI debugging but, it has an extension which allows specified COBOL statements to be compiled only if a debugging switch is specified at compilation time. File Assignments The format of the ASSIGN clause on the 2000 uses the following syntax, ASSIGN TO unit,name where unit is PRINT, INPUT, OUTPUT, INPUT-OUTPUT, or RANDOM to denote the type of operations to be performed, and name is a file or device name which follows BOSS/IX rules. On the MPx, the format is ASSIGN TO name, where name is either an identifier or a literal. The value of name is a file or device name which follows BOSS/VS rules. The MPx system uses 8-bit ASCII (high-order). The 2000 conforms to the system standard of 7-bit ASCII (low-order). Function Keys The 2000 COBOL supports 4 function keys, while RM COBOL supports 9 function keys. 7.0 FOR YOUR INFORMATION o The RERUN verb is treated as a comment. o A sequential file may not be opened with the REVERSED clause. o The ENTER verb is not supported. o Exponential (the "**" operator) is only allowed to integer powers. o The literal form of an alphabet name is not supported. o Multiple results are not permitted in arithmetic statements. o A procedure name is required in GO TO statements. o INSPECT data items are restricted to a single character o Compound TALLYING and REPLACING clauses in the INSPECT statement are SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB011 Pg004 not supported. o When used in the procedure division, the non-numeric literal in the ALL form of a figurative constant may not contain more than one character. o The DATE COMPILED paragraph is treated as a comment, rather than being changed on the listing to show the date compiled. o The FROM option of ACCEPT and DISPLAY statement is limited to 80 characters. o OPTIONAL and RESERVED may not be specified in the SELECT clause. o The MULTIPLE FILE clause is not supported. o LINAGE clauses may not be specified. o The FOR REMOVAL clause of the CLOSE statement is not supported. o The RESERVE clause of the SELECT entry is not supported. o All independent segments must follow the fixed permanent segments in the source program. o A COPY sentence must be the last entry on a source record. o The 2000 does not support reel-to-reel tapes, and thus does not support multi-reel files, or multi-file tapes. 8.0 WARNINGS AND CAUTIONS o COBOL handles INDEXED and DIRECT files differently than BASIC. If the file is accessed by both BASIC and COBOL programs, the manner in which records are processed will have to be changed. 1. When writing to a DIRECT file, COBOL does not append the key to the end of the data record. BASIC appends the key to the end of the data. Workaround - Define the KEY of the DIRECT file in the Working Storage Section, NOT in the FD. 2. COBOL adds an additional two bytes to the beginning of every INDEXED file record to store the length of the record. BASIC does not store the length of each record in the data file. Workaround - Allow for two bytes at the beginning of each record when defining the file layout for an INDEXED file. o COBOL programs can be run in background mode, but the terminal will still be used by the COBOL program. Because of this reason the advantage of running programs in background mode is eliminated. o The input/output redirection (e.g. runcobol pgm.o > log) does not work. o Program and data file names must conform to the rules that apply on the 2000. File names cannot exceed 20 characters in length. Caution should be used when using the following special characters. The character "/" is reserved as a separator for file path names. The characters "*" and "?" are used as wild card characters. o The BACK SPACE key does not work as expected with the ACCEPT SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB011 Pg005 statement. Use the DEL key or load a FUNCTION key with $7F$ for a destructive backspace. o COBOL is internally hard coded to use a 24 x 80 character terminal. ORIGINATOR: MBF SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB011 Pg006 FIB 00012 05/28/86 *** Completion code of 77 (Internal FTF Error) - release 7.2A *** A completion code of 77 (INTERNAL FTF ERROR) can occur intermittantly during serial file transmissions with the 7.2 File Transfer Utility. Please contact Basic Four Product Support for the distribution of the fixes for this problem. ORIGINATOR: L. YAMADA SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB012 Pg001 FIB 00013 06/24/86 *** MMU errors running ORIGIN R13B on BOSS/IX 7.2A *** Memory management errors will occur throughout ORIGIN R13B when running it on a 2000 system with an OS leVel of 7.2A. These errors are caused by a bug in the DIM statement in BASIC level 7223. The following changes will fix the errors in ORIGIN: 1. LOAD "ORICPL" 2. Add statements 0524 and 0526 as follows: 0524 G1$=G$; DIM G2$(255," ") 0526 I=POS(G2$=G1$); IF I<>0 LET G1$=G1$(1,I)+" "+G1$(I+255) 3. Change G$ to G1$ in statement 0530: Old: 0530 X$=CPL(G$,T$,V$,ERR=0550) New: 0530 X$=CPL(G1$,T$,V$,ERR=0550) 4. SAVE "ORICPL" ORIGINATOR: T. TIANGCO SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB013 Pg001 FIB 00014 07/08/86 *** Incorrect files restored using 1/2" MTS on release 7.2A *** A problem has been found with the pattern matching of the 12 inch tape restore. command, "mtsrestore". Following is an example of the problem: A backup tape contains the following files in this order: /ABCD /ABCE /ABC. I wish to restore /ABC, so I use this command: mtsrestore /ABC -v . I will get a . message that /ABC was restored, but what I actually got was a copy of /ABCD into the file /ABC. This is because the pattern matching found the characters /ABC in the field /ABCD. After finding these charactrs, the program stopped and did not. continue to search. The work-around is to use pattern matching to restore files to another direc- tory, then copy the ones you need and delete the others. The problem is fixed in 7.2B. ORIGINATOR: W. MOORE SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB014 Pg001 FIB 00015 07/08/86 *** Task(s) drop out of BASIC mode while program is running - rel 7.2A *** A bug has been found in release 7.2A that will cause BASIC to suspend if the NUM function is used on a string that is greater than 255 characters long. (example: DIM A$(256); PRINT NUM(A$) - BASIC will suspend!) The work-around is to ensure that the string that you are using the NUM func- tion on is less than 256 characters or use a substring when using the NUM func- tion. (example: DIM A$(256); PRINT NUM(A$(200,14))). The substring must contain less than 256 characters, also. This problem will be fixed in release 7.2B. ORIGINATOR: W. MOORE SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB015 Pg001 FIB 00016 07/21/86 *** Error 18 Filesystem Error -48 on 7.2A when adding operator *** If adding an operator whose home directory is an existing diretory the file attributes will be set to Read/Execute for all other users. This will result in a BASIC ERROR 18 Filesystem error -48 when the existing operators try to use the applications residing in that directory. To correct this, the owner needs to be changed back to the original owner and the filemodes need to be changed to allow other users to write to files in that directory. The steps to do this are: 1. Logon to admin 2. ADMIN> chown example: chown name dir_name 3. ADMIN> filemodes rwx rwx example: filemodes rwx rwx dir_name ORIGINATOR: P. THATCHER SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB016 Pg001 FIB 00017 09/18/86 *** System crashs when using the 'BO' and 'EO' mnemonics on rel 7.2 *** When using the Ouptut Transparency mnemonics, 'BO' and 'EO', the 'EO' must be followed by a Carriage Return/Line Feed. Positioning to print after the 'EO' mnemonic without the Carriage Return/Line Feed will cause the system to crash. This will be fixed in 7.2C and 7.3. Examples: Will crash system: 0100 PRINT (1)@(20),'BO',"PRINT STUFF",'EO',@(50),"MORE STUFF", Will work: 0100 PRINT (1)@(20),'BO',"PRINT STUFF",'EO', 0110 PRINT (1)@(50),"MORE STUFF", ORIGINATOR: P. THATCHER SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB017 Pg001 FIB 00018 09/25/86 *** Information on sending dump tapes to BASIC FOUR [WPS # 246] *** To provide the turnaround our customers require and to provide us with the information to return the dump analysis esults to the proper systems person, we release need the folowing data: A. What processes were running on the system when it crashed or dumped? 1. type of programs running 2. number of users on the system 3. was a print job(s) running B. Did the system crash or was the dump forced. 1. if forced, why? a. system slow b. one terminal hung - if so, which one c. some terminals hung - if so which ones d. all terminals hung 2. if not forced (crash), then write down all information from the terminal screen. C. Type and release of Operating System (i.e., boss/ix, Lbossix, Bbossix, etc., 7.1A, 7.1B, 7.2A, 7.2B, etc.) D. Person to contact with dump analysis results. This must be a BASIC FOUR systems person - NOT the customer. To enable us to track and return the customer's tape,please put a label on the. dump tape that includes the following informtion: A. Customer's Name B. System person contact C. Address to send the dump tape back to Send dump tapes to: MAI Basic Four, Inc. 14101 Myford Road Tustin, CA 92680 Attn: Marisa Bell Maildrop 267 Please send dumps ONLY to the address above. Do not send directly to the analyst you've been working with, but please include the Worldwide Product Support analyst name in a note with the other information you are sending. Send- ing a dump to an analyst can cause needless delays in getting the dump results back. ORIGINATOR: W. MOORE SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB018 Pg001 FIB 00019 11/13/86 *** S10, ODT or other VDTs run slow on release 7.2 *** S10, ODT and foreign terminals may run noticeably slower under 7.2 OS as compared to 7.1. The workaround described below will correct this problem. This bulletin also refers to a DS-500 series workstation used on a 2000 ter- minal via PC-LINK on release 7.2. If the PC-link terminal is configured on the 2000 side as an EVDT, the 'CF' mnemonic also clears the background. If the PC- LINK terminal is configured on the 2000 side as a VDT 7270, emulation works properly, but the INSTALLing, SENDing, and RECEIVEing of files fails. *** NOTE *** 7.2 incorporated a device driver to handle a VDT 7270 or a VDT 7250 . The VDT 7250 needed a deley so that when using CRT intensive mnemonics, these mnemonics would e recognized. Using a delay of 01 in the mnemonics table would allow 20 nulls to be sent between escape sequences. The only VDT that needs this type of deley is the VDT 7250. VDT 7270 works with or without the delay, whereas a PC-LINK, S10, ODT or foreign terminal works properly using a delay of 00. WORKAROUND AS FOLLOWS: a) cd /etc/ttymntbl b) copy vdt/7270.mntbl vdt7250.mntbl c) ved vdt7270.mntbl d) change the first line from "DELAY 01" to "DELAY 00" then save the change. (The delay 01 can also be deleted giving the same effect as deley 00) e) makettymntbl vdt7270 f) makettymntbl vdt7250 g) configure (configure as a VDT 7270) h) shutdown and reboot the system ORIGINATOR: D. WENZEL SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB019 Pg001 FIB 00020 11/26/86 *** Error 31 in BASIC on release 7.2 due to variable tables *** To increase the speed of BASIC on the BOSS/IX operating system, variable tables are loaded into the data portion of the user's memory area. These tables are used for faster access of the value of the variable. After a START command is issued, the tables are cleared out of memory. When the first program is loaded, the required tales are defined. During the LOAD or RUN of subsequent programs, these tables are retained, as BASIC has no way to store these tables in case the RUN or LOAD should fail. For this reason the variables from the program being LOADed or RUN are merged into the present tables. If the new program contains variables that are not already present in these tables, these new variables are added. This adding of new variables to the tables will increase the table over-. head, thus, reducing the area available for the program code. Reduced program area can result in ERROR 31's to occur with programs that should have run with the present START size. Table sizes were not a problem in level 7.1 BASIC, since that level of BASIC only allowed two-character variable names. The overhead for the tables was small . With the added functionality of the eight character variable names in level 7.2 BASIC, the overhead for the variable tables is somewhat greater. The following are ways to avoid the ERROR 31's if you are experiencing them with you appication: 1) Increase the initial START size used for running the application. The new START size will depend on the application; the more variable names used, the larger the START size required. 2) Where ever possible, use a START XX,"PROGRAMNAME" in place of the RUN "PROGRAMNAME" statements in the application programs. The START will result in no residual tables in the task's memory. NOTE: The BASIC commands of BEGIN and CLEAR will initialize the tables, but will not remove them. 3) Wherever possible, continue to use the same variable names in all programs in the application software. If the same names are used, the tables will not grow from program-to-programs. In addition, it is recommended that you check your programs to ensure that a re-START command to a lower memory size is not used. There are no plans, at this time, to redesign BASIC on the BOSS/IX operating system, to reduce the area required for variable tables. ORIGINATOR: W. MOORE SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB020 Pg001 FIB 00021 11/26/86 *** Error 47 while running BQR after file(s) transporting *** After files have been transported to the 2000 from another system, an ERROR 47 can occur when running "BQR". This error is caused by converting a file contain- ing a null key. The error will occur at statement 2080 in program /util/CNVTR3. To correct this problem, modify statement 2080 by inserting: IF K8$="" GOTO 2090 ELSE at the beginning of the line. The statement should read as follows: 2080 IF K8$="" GOTO 2090 ELSE FOR J9=1 TO LEN(K8$); LET K8$(J9,1)=A5$(ASC(K8$( J9,1))+1,1); NEXT J9 ORIGINATOR: P. THATCHER SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB021 Pg001 FIB 00022 12/11/86 *** BOSS/IX may return different error codes in BASIC than BOSS/VS *** SYMPTOM: The 2000 release 7.2 OS returns different error codes than the MPx OS on the NUM function when it fails. PROBLEM DETERMINATION: The known differences to date are: 2000 MPx DIM A$(100,"0") A$(1,1)="1" PRINT NUM(A$) !ERROR=40 ERROR=26 DIM A$(500,"0") A$(1,1)="1" PRINT NUM(A$) The value is 0 ERROR=26 A$="00000100000200000300000400000500000600000700000800000900000" PRINT NUM(A$(1,30),ERR=XXX) !ERROR=20 ERROR=26 In future releases the 2000 error codes will be the same as MPx when possible. ORIGINATOR: P. THATCHER SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB022 Pg001 FIB 00023 05/04/87 *** Release 7.2C Software Announcement *** 1.0 INTRODUCTION Level 7.2C of BOSS/IX~ is now available. This new release consists of the level 7.2C Operating System and its related software products for the new MAI^ 3000 system. The 7.2C Operating System release contains the same functionality as the level 7.2B software release for the MAI^ 2000 system. The user will find no difference in the messages and prompts for commands, utilities and BASIC. What has changed is the internal operating system. It has been modified to work with the Motorola^ 68020 processor, the 32 bit microprocessor used in the new MAI 3000. This document contains the information to install and upgrade the 7.2C Operating System and the MAI 3000 hardware. Also, there are sections on customizing the MAI 3000, determining the memory required, system dump procedures, an upgrade questionaire for upgrading to an MAI 3000 from an MAI 2000, a list of new documentation for the MAI 3000, a list of lowest acceptable revision levels for the hardware, and a list of warnings and cautions and a way, if any, to work around them. It is recommended that before installing a MAI 3000, you first read this document. For information on ordering software and hardware and other Marketing related information please see Marketing Announcement 441 for the United States or 295 for International. NOTE: If you are upgrading an MAI 2000 customer running on Operating System level 7.1B or less, it is recommended that you read software announcement number 126, for information on the differences between OS level 7.1 and OS level 7.2. TABLE OF CONTENTS 1.0 INTRODUCTION 2.0 SYSTEM START UP AND SHUTDOWN 2.1 System Start Up 2.2 System Shutdown 3.0 INSTALLATION AND UPGRADE OF THE OPERATING SYSTEM, SOFTWARE AND DIAGNOSTICS 3.1 Installing Diagnostics on the Disk 3.1.1 Introduction 3.1.2 Disk diagnostics installation procedure 3.1.3 Loading Disk Diagnostics 3.2 Installation of the Operating System 3.3 Upgrading Customer Software from an MAI 2000 to an MAI 3000 SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg001 3.4 Upgrading a MAI 3000 3.5 Security Configuration Record 3.5.1 Installing/Upgrading a Security Configuration record on the MAI 3000 3.5.2 The 'iconf' command 3.5.3 Configuration Record Request Sheet 4.0 HARDWARE INFORMATION 4.1 Switch and Jumper Settings 4.1.1 CMB (Central Mother Board) 4.1.2 1 Megabyte Memory Boards 4.1.3 Winchester Disk Controller 4.1.4 4-Way Serial Controller 4.1.5 8-Way Serial Controller 4.1.6 MCS Tape Controller 4.1.7 MTS Tape Controller and Formatter Board 4.1.8 LAN (Local Area Network) Controller 4.2 Cable Diagrams 4.2.1 Parallel Printer Cable (P/N 907455) 4.2.2 CMB to Serial Device Cable (P/N 907753) 4.2.3 4-Way/8-Way "octopus" to Serial Device Cable (P/N 907752) 4.2.4 8-Way "octopus" Cable with 9-pin Connector (P/N 907968) 4.2.5 8-Way "octopus" Cable with 25-pin Connector (P/N 916079) 4.3 Instructions for Upgrading from an MAI 2000 5.0 CUSTOMIZATION 5.1 Operating System Parameters Customization 5.2 Modifying the NVRAM 6.0 MEMORY USAGE 6.1 Approximating a System's Memory Requirement 6.2 Calculating a System's Memory Requirement 6.2.1 Example of How to Calculate a System's Memory Requirement 6.3 Calculating BOSS/IX Table Space and Dynamic Work Space 7.0 UPGRADE FROM THE MAI 3000 CHECKLIST 7.1 Site Survey Checklist 7.2 System Configuration Planning Guide 7.3 Parts Ordering Questionaire 8.0 DUMP PROCEDURE 8.1 Configuring the System To Dump SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg002 8.2 Saving The Dump To Tape Directly 8.3 Forcing A System Dump 9.0 FOR YOUR INFORMATION 10.0 DOCUMENTATION 11.0 LOWEST ACCEPTABLE REVISION LEVELS (LARL) 2.1 System Start Up System start-up is dependent on the set of parameters in the system configuration file that is loaded into memory at boot time. The system will normally use a default system configuration file '/etc/conf' off the boot partition or the system file, O.S. file or boot device can be specified at boot time during an alternate load. First determine which terminal is the console terminal, since all messages during the system start-up are displayed on the system console. The system console is normally set up to be either the first port of the CMB (Central Microprocessor Board) or the first port off of the first serial device controller, whether it be a 4-way or 8-way. If you don't know which one is the system console, turn both terminals on and which ever terminal displays the self test is the console terminal. At the system console, set the terminal attributes to 9600 BAUD, x-on/x-off flow control. Next on the front of the CCA (Central Cabinet Assembly) there is a key switch. This key switch is a three position switch with a locked position; in this position all front panel controls are inoperative, the key should be left in this position during normal operation to prevent an accidental reset. The 'START' position is used to power on the system and initiate a boot load when the 'START' button is pressed. The 'START/RESET/NMI' enables the 'START' button and 'RESET/NMI' button. Turn the key to the middle or 'START' position. On the back of the CCA is a power switch. This switch is a three position switch with an off position, in the middle is the 'neutral' position and a momentary load position. If the switch is in the 'off' position place it into the 'neutral' position and then press the 'START' button on the front panel. If the switch is in the 'neutral' position, then just press the 'START' button on the front panel. (The latter procedure will be the normal start-up process.) NOTE: If the power switch is placed in the momentary position the system will automatically start the load process. After it is released it will return to the 'on' position. During the system start-up process the system will display the systems self test to the console terminal. After the self test successfully completes, the system will automatically complete the boot process, after which the bootstrap menu is displayed: 1) Boot 2) Alt-load SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg003 3) Micro-diagnostics 4) Power Down Enter option (1-4): NOTE: After a proper shutdown the same menu and options will apply. The following describes the different options and the results of each: 1) Boot For a standard load use option 1, , or if no option is entered the system will time-out and default to option 1. If this option is chosen, the standard Operating System and '/etc/conf' configuration file supplied with the software will be loaded. After the load is complete '/etc/start' will be executed. This will display the system proprietary message. After the proprietary message, '/etc/start' displays the system date and time, you are prompted to enter the current date and time. Once the date and time is accepted, '/etc/start' will display the entered time and date, the calculated day of the week, and depending on what is configured in the '/etc/conf' file '' or '' message. If a minor error occurred during start-up, the error messages are reported in the '/etc/sys.log' file; '/etc/start' checks this file and if it contains data the following message is displayed: An error occurred during system startup. File '/etc/sys.log' contains a description of the errors. Press the 'ESC' key to continue. . . If this message occurs simply press the key and the 'ADMIN>' prompt will then be displayed. Once at the 'ADMIN>' prompt, you can print the contents of the '/etc/sys.log' file by using the command, 'p /etc/sys.log'. If no errors occurred the 'ADMIN>' prompt will display immediately. If a severe error occurs the system will abort the boot process and a system crash messsage will be displayed. If the '/etc/conf' file is set to "secure mode" a 'Password:' prompt will be displayed before the 'ADMIN>' prompt. If this prompt is displayed, you must enter the system administrator password followed by a . If the '/etc/conf' file is set to "multi mode", 'etc/startup' will be executed after the date and time is displayed. This program will startup all of the configured terminals on the system. If a minor error occurs anytime during the boot the message telling that the error is in the '/etc/sys.log' file will be displayed after '/etc/startup' is complete. To get to the 'ADMIN>' prompt from multi mode requires that you first enter and admin for operator name. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg004 2) Alt-load For an alternate load use option 2. This option will allow you to load the diagnostics from disk or tape, boot the O.S. installation tape, or boot an alternate O.S. or configuration file. After selection of option 2, the boot device prompt is displayed: Boot device: To boot off of tape, ensure that the proper bootable tape is in the tape drive, enter 'cs' for MCS tape or 'ts' for MTS tape. To boot off the hard disk enter 'wd0' or . After entering your boot device the program will display the file system prompt: System file: If the boot device is 'cs' or 'ts', enter a to this prompt to load from tape. If the boot device is 'wd0', a will cause the default O.S. and configuration file to be loaded; entering 'diag' will cause the diagnostics to be loaded off the hard disk. To load an alternate O.S. or configuration file requires a two part name. If one part is omitted the default is used. Part one of the system file is a loadable O.S. file, '/sys/bossix' and '/sys/Bbossix' are examples of loadable O.S. files. Part two is a system configuration file, '/etc/conf' and '/etc/boot.conf' are examples of system configuration files. These two parts when entered together are seperated by a comma, ",". If the first part is entered by itself no comma is required and the system will default to the '/etc/conf' file, example: '/sys/bossix'. If the second part is entered by itself, for the case where you wish to root to the boot partition, the comma must precede the file name, example: ',/etc/boot.conf'. In the second case the system will default to the default O.S. '/sys/bossix'. After the system file is entered the system will boot off the device specified. If a diagnostic tape is loaded or diagnostics are loaded off the hard disk, the prompt will be displayed after the load is complete. If aninstallation tape is loaded then the installation menu will be displayed after the load is complete. If an O.S. file and/or configuration file is used then the load will proceed as described for option 1. 3) Micro-diagnostics Option 3 will allow you to modify the NVRAM and should only be used by persons who know how to do this, as this can disable your system. For information on modifying the NVRAM see section 5.0. 4) Power down Option 4 will cause the system to be powered down. This is SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg005 all that is required to power down the system, there is no need to turn the power switch on the back of the CCA to the 'off' position. 2.2 System Shutdown It is VERY IMPORTANT that the system be shutdown properly. Failure to follow these procedures may result in damage to the filesystem, and may cause a loss of data. The system can only be shutdown by the system administrator. Shutdown can be initiated from any terminal, if the system is in multi-user mode. In single user mode, only the system console is active. To shutdown a system which automatically boots into multi-user mode, you must be logged in as the system administrator. At the 'ADMIN>' prompt type 'shutdown x -p message ', and press , where 'x' is the number in minutes until the system shutdown occurs, '-p' will cause the system to power down after it is shutdown, and 'message' is any message you wish to display during the shutdown. '-p' and 'message' are both options and need not be entered. If the system boots into single-user mode, and is in single-user mode, enter '^D'. The system then prompts: 'single, multi, shutdown or powerdown?' At this prompt enter 'shutdown' to get back to the bootstrap menu or 'powerdown' to first shutdown the system and then power it down. If the system boots into single-user mode, and is in multi-user mode use the command 'shutdown x message', where 'x' is the number of minutes until shutdown and 'message' is any message you wish to display during the shutdown. The system will then shutdown into single-user mode at which point enter '^D' and follow the prompts described in the above paragraph. 3.0 INSTALLATION AND UPGRADE OF THE OPERATING SYSTEM, SOFTWARE AND DIAGNOSTICS. The following are the steps to install or upgrade the Operating System, customer's software and system diagnostics. Before installing or upgrading the system it is recommended that you read these instructions completely. 3.1 Installing Diagnostics on the Disk 3.1.1 Introduction Diagnostic programs for your system may be contained on the system fixed disk. The installation of all of the diagnostics is optional. Your disk should have diagnostics installed in order to test the tape subsystem included with your system. The purpose of these tape diagnostics is to troubleshoot and test your tape subsystem, when you cannot load diagnostics from the tape subsystem. You may optionally install all of the diagnostics programs on your disk The system diagnostics are contained on a dedicated diagnostic partition. This diagnostic partition is inaccessible to user programs, and is actually beyond SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg006 the reach of the user disk area. For this reason, the diagnostic programs cannot be accessed by the file system, yet they are maintained by a Diagnostic Executive. If your system will not boot diagnostics from disk, and the O.S. is already installed, the file system must first be backed up. Once backed up, a diagnostic partition can be reserved. Once the diagnostic partition is reserved, diagnostics can be installed from the same bootable diagnostic tape. Afterwards the file system must be restored. Use the following procedure to install the diagnostics on your fixed disk. 3.1.2 Disk diagnostic installation procedure Step 1. Backup your disk If your file system is already installed on the disk you must do a complete file by file backup. If your file system has not been installed yet, install your diagnostics first and then install the file system. Step 2. Boot diagnostics from tape Install the diagnostic tape. From the bootstrap menu enter 2 to alt load. For the boot device enter "cs", for MCS or 'ts', for MTS. For the system file enter . Step 3. Enable service mode When the EXEC is loaded, it will auto-size the system and display the program prompt: Any Exec commands can be entered at this time. To begin the installation of diagnostics, you must first enable the service commands. At the Exec prompt, enter: service and a RETURN. This will allow use of the service commands. Exec will then ask for the service password, enter: b4bus and a RETURN after which, the prompt will again be displayed. Step 4. Up date the superblock on the disk. The superblock on the disk must be updated to reserve a section of the disk for the diagnostics. Enter the superblock initialization command: sbinit SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg007 and a RETURN to initialize the superblock for the diagnostic partition. EXEC will ask you if you want to destroy the existing disk partition information and the disk directory name. Any (y/n) responses are single character responses, and do NOT require a . Entry of the "sbinit" command will cause EXEC to ask: Destroy: "volume ID" (y/n)? where "volume ID" is the current volume ID contained in the superblock. A "y" response will allow you to initialize the superblock for the diagnostic partition. A "n", no response will return you to the prompt. Enter: y and EXEC will ask for the number of sectors to reserve on the disk for the diagnostics: Diagnostic Partition size (in sectors)? Enter the number of sectors desired as follows: a) To install all available diagnostics, enter: 1200 b) To install tape diagnostics, enter: 200 EXEC will then ask about the directory: Destroy: "partition name" (y/n)? Enter the character "y" to destroy the current disk directory to have it initialized for a subsequent install, or "n" to retain the current partition name. If you wish to change the name of the disk diagnostic partition, enter: y and EXEC will then ask: Disk name: Enter the new disk name, up to 12 characters in length, and . This new name will be displayed every time you display the directory. EXEC will then display: SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg008 Initializing: "disk name" where "disk name" is the new name you just entered. The diagnostic partition is now defined. Step 5. Copy diagnostics from tape to disk Once the diagnostic partition is defined, diagnostics can be installed on the disk. You now can determine which files to install on the disk by listing the contents of the tape. This is optional if you are going to install all of the diagnostics. To obtain a list of file names on the tape, enter: ltape To install the diagnostics on the fixed disk, enter: install and a RETURN to install ALL of the diagnostics. To install a particular diagnostic enter: install "file" and a RETURN where "file" is the file name to install on the disk. Use the list of files obtained by the "ltape" command to determine which files you want to install. The file EXEC, SIT, MCS and/or MTS are the minimum diagnostic files to install. When you enter the "install" command, to install all of the diagnostics, EXEC will prompt: Destroy: "disk name" (y/n)? where "disk name" is the name of the disk entered during the "sbinit" command sequence. Entry of the character "n" will cause the current directory name to remain and the install process to begin. Entry of a "y" character will cause EXEC to ask you for the new disk name as in the "sbinit" command. Maintain the current directory from the "sbinit" sequence, enter: n and the install procedure will begin. As the diagnostics are installed on the disk, SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg009 EXEC will display the current program being copied from the tape, and the size in sectors. After the sector size display, the file is written to the disk and the directory updated. When all the files are installed, EXEC will again display the prompt: Step 6. After the diagnostics are installed on the disk, you may want to list the diagnostics on the disk enter: ldisk and to obtain the list of the diagnostic files on disk. You should test the bootstrap capability now, to see that you can boot diagnostics from the disk. Enter: shutdown and to obtain the bootstrap menu. Step 7. At the bootstrap menu enter option '2' Alt-load, for the boot device enter: Wdo, for system file enter: diag. Install the file system on the disk. Note that installing diagnostics on the disk HAS TAKEN disk space away from the user available disk space, the device capacity is reduced to provide room for the diagnostics. 3.1.3 Loading Disk Diagnostics When the system is first powered up, or after the system is shutdown, the user must perform an alternate load sequence in order to load diagnostics from disk. The system has the logic to either bootstrap the Operating System or the Diagnostic Executive. The loader programs for each are in different sections of the disk. The diagnostic loader and the associated directory of files for the diagnostics are contained in the diagnostic partition. Thus the diagnostic partition is completely self contained, and separate from the Operating System. The operation of loading diagnostics from the fixed disk and from the MCS tape are similar. The only difference is in the alternate load sequence, as discussed in the following sections. The diagnostics contained on your fixed disk cannot be run while the Operating System is up and running. The diagnostic programs are all off-line programs and require you to first shutdown your system, regardless if you load from MCS tape or from the fixed disk. After running diagnostics, entry of the diagnostic "shutdown" command will allow you to reload the Operating System. The normal indication that diagnostics are not on the SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg010 disk, is the error message "invalid loader detected" when a diagnostic boot is attempted. To access the diagnotics, once they are installed perform an ALT load from the bootstrap menu. For boot device enter 'wd0', for system file enter 'diag'. This will get the '' prompt. Any file name listed by the 'ldisk' command can now be loaded by entry of the command: load file and , where "file" is any file listed. 3.2 Installation of the Operating System The following steps outline the MAI\ 3000 BOSS/IX~ installation procedures. Step 1. First step is to install the boot partition. Insert the base tape into the MCS drive or MTS drive. Do an alternate load. At the 'boot device:' prompt type "cs" for MCS or "ts" for MTS then press . Press again at 'System file:' prompt. Step 2. Screen displays loading messages, then the Installation Menu. Select Option 'A', then . Option 'A' re-defines all the wd0 partitions and copies a new boot partition to disk. After the copy is complete, you are instructed to reload. Note: The diagnostic partition, if defined, is not included in this partition redefinition. Step 3. After the boot partition is installed the configuration record must be installed. When the message 'OPTION>' is re-displayed put the configuration record tape in the tape drive. Use option 'D' to install the configuration record. After the configuration record is installed enter ' D' and then 'shutdown'. WARNING: If the configuration record for the system is not installed you will be able to access the boot partition only. NOTE: After shutdown and re-boot to the boot partition it is recommended that the configuration record be copied to the boot partition. To do this execute the following with the configuration tape in the tape drive: 'mcsrestore -v name=CONFIG' for MCS or 'mtsrestore -v name=CONFIG' for MTS. Step 4. After the configuration record, the EOS product must be installed. Reloading the system at this time automatically reloads and roots to the boot partition. Enter the correct date, the screen will then display the 'ADMIN>' prompt, type "osinstall cs" for MCS and "osinstall ts" for MTS. This command sets up the rest of the partitions on the disk and installs the EOS product. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg011 After the EOS product is installed you are instructed to reload again. Step 5. Reloading of the system at this time automatically reloads and roots to the root partition. Enter either the current date, or a , if the date is correct. At the 'ADMIN>' prompt, type "install cs EUT EBS", for MCS or "install ts EUT EBS", for MTS. All products listed on the base tape can be installed with one command line. If you receive more than the base system, each additional product will be on a separate tape. Each additional tape will need a new command line entered. Example: The EIT product is distributed on a separate media. To install it type "install cs EIT" or "install ts EIT" at the 'ADMIN>' prompt. Products that are chargeable and not part of the base system will have key codes that you must enter during or after (using '/bin/install key') installation before you can use that product. If the key certificate did not come with the media, contact the customer or service representative in your area to instruct you in where to call for this key code. Step 6. The '/etc/conf' file on the boot partition needs to be customized to meet your needs. (See Section 6.0 'Memory Usage' for instruction on how to customize the '/etc/conf' file.) Step 7. After you have copied all your products to disk and have customized the '/etc/conf' file, your system is ready for use. 3.3 Upgrading Customer Software From an MAI 2000 to an MAI 3000 The following steps describe the procedure to upgrade an MAI 2000's software to an MAI 3000. Step 1. Perform a file-by-file backup of the customer's program and data files on the MAI 2000 using the MCS or MTS commands or system utilities. This backup should be a verified backup. NOTE: Be careful not to include any of the system's programs or data files in the user files only. Step 2. If you are not moving the drive(s) from the MAI 2000 go to step 3. If you are moving the drive(s) and are sure you have a verified backup, move the drive(s) to the MAI 3000. Step 3. Refer to section 3.1, 'Installing diagnostics to the disk', and follow the procedure to install the diagnostics. After the diagnostics are installed proceed to step 4. Step 4. Refer to section 3.2, 'Installation of the Operating System', and follow the procedure to install the Operating System, Security Configuration Record, and other products. After the Operating System, Security SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg012 Configuration Record and other products are installed proceed to step 5. Step 5. Use the MCS or MTS commands or system utilities to restore the customer's program and data files to the MAI 3000. Step 6. If the MAI 2000 was at an Operating System level of 7.2A or 7.2B the upgrade is complete. If the MAI 2000 was at an Operating System level of 7.1A or 7.2B, you will need to convert the customer's BASIC programs to the level 7.2 format. To convert level 7.1 BASIC programs to level 7.2 BASIC format use the 'csave' command. NOTE: To convert all the customer's BASIC programs and get a copy of all errors found during the conversion use the following command: csave / -r %% /filename (where filename is any file name that is not presently being used.) To print this file to a printer use the command 'lpr /filename'. To print this file to a terminal use the command 'p /filename'. The above steps can be used to write errors to a file any time a 'csave' of newly installed 7.1 BASIC program(s) is required. After the BASIC programs have been converted to 7.2 format continue with the system customization. 3.4 Upgrading an MAI 3000 The following steps describe the MAI 3000 BOSS/IX upgrade procedures for a system already running as an MAI 3000. WARNING: Always have a current back-up before doing any upgrades. Step 1. Using the MCS command, MTS command or system utility, backup the correct configuration and user files of your system. NOTE: If you do not wish to re-install your boot partition proceed to step 2. Shutdown the system to the point where bootstrap menu is displayed. Do an alternate load, by selecting option '2' from the bootstrap menu. At the 'Boot device:' prompt, type "cs" for MCS tape or "ts" for MTS tape. At the 'System file:' prompt, press . The system will boot from the tape and display the loading messages then the Install Menu screen. At this menu select option "B". Option "B" will only copy an image on the boot partition from tape to disk. This process will ensure that your system has all the up-to-date and proper MACROs and system files on the boot partition. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg013 Once the boot has been copied to disk the '/etc/conf' file on the boot will be set to a minimum configuration. You will need to customize this file to meet your system's needs. To customize this file see Section 5.1. After you have copied the boot partition to disk continue on with step 2. Step 2. Do an alternate load. At 'Boot device:' prompt, enter ''. At the 'System File:' prompt, enter ",/etc/boot.conf". Step 3. The above alternate load will automatically reload and root the operating system to the boot partition. Enter the correct date or '' if the date is correct. Insert the base system tape. At the 'ADMIN>' prompt type "osupdate cs" for MCS or "osupdate ts" for MTS tape. Step 4. After the procedure is complete you have the option of restoring the default system configuration files to the upgraded root then to the boot partition. This is done by typing "/sys/installetc". This procedure allows the operator to select which system files he/she needs to restore. Please note that if this is done all system files that are restored will be new and will have to be re-updated to reflect the needed system information. Example: If '/etc/passwd' is re-installed the operators will have to be redefined. Following, find a list of the files that can be installed using '/sys/installetc' and the means to modify the file for your system: /etc/class, /etc/defaults, /etc/forms: These files are used when printing and can be customized by going to the 'ut.printer' menu and using option 5 'Printer parameters' or using the program 'pparams'. /etc/conf: This file contains your system configuration parameters and is changed by using the '/bin/vconf' command. /etc/exem, /etc/logm, /etc/motd: These files print to the screen at the time of log in and can be modified by the use of the '/bin/ved' command. /etc/passwd: This file contains your operator information and is updated by going to the 'ut.system' menu and using Option 3, (Operator information) or by using the program 'oprinfo'. /etc/ports, /etc/printers, /etc/terminals: These files contain the terminal and printer configuration parameters and are updated by going to the 'ut.system' menu and using Option 1, (Port configuration) or by using the program 'configure'. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg014 /etc/sinit, /etc/startup: These files are used at system load time and can be modified by the use of the '/bin/ved' command. /etc/shtdwn: This file is used when the system is being shutdown and can be modified by the use of the '/bin/ved' command. /etc/ptrans: This file contains the printer translation tables and is modified by the use of the '/bin/pted' command. Step 5. Next shutdown the system and do a normal reload to the root partition. Enter the correct date or press '' if the date is correct. If you are upgrading from MCS, at the 'ADMIN>' prompt type "install cs EUT EBS" or "install ts EUT EBS" for MTS, press ''. The system will automatically install both EUT and EBS. Once EUT and EBS are installed you can then install the rest of the products by typing "install cs XXX" for MCS, or "install ts XXX" for MTS, where XXX is the different product names. 3.5 Security Configuration Record 3.5.1 Installing/Upgrading a Security Configuration Record on the MAI 3000. Each system needs a unique configuration record based on the system serial number and hardware configuration. Without it, you won't be able to boot the system to the root partition. An attempt to boot to the root partition will cause the system to halt giving an "Illegal Configuration Record" message. This security termination will not damage the root partition. The procedure to install/upgrade a configuration record on the MAI 3000 is outlined below: 1. Boot from the Base tape. 2. Install the boot partition if you need to. 3. Remove the Base tape and insert the configuration tape. 4. Use option "D" to install the configuration record. 5. Shutdown and re-boot the system. 6. OPTIONAL: You can save a copy of the configuration record on the boot partition. To place a copy of the configuration record on the boot partition, after re-booting to the boot partition, use the command: "mcsrestore -v name=CONFIG", for MCS or "mtsrestore -v name=CONFIG", for MTS. 7. Remove the configuration tape and re-insert the Base tape. 8. Continue with the normal installation procedure. Once you have installed/upgraded the configuration record on your system it will not have to be done again unless a re-format is required or the system's hardware configuration changes. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg015 3.5.2 The 'iconf' command The program '/bin/iconf' will display the current configuration in force as well as the configuration contained in a configuration record file. The 'iconf' command can also be used to install the configuration record. Format iconf Options -new Display the new system configuration which may be installed -save Permanently installs the new configuration record Examples @>iconf Displays the current system configuration @>iconf - new -save Displays the default configuration record and stores it in the system configuration record. Notes: Only the system administrator may display or install the new configuration. The configuration record is always read from, or written to, the Winchester disk from which the system was booted, or from wd0 if the boot device was tape. Unless explicitly specified, the new configuration record is assumed to be contained in a file under the name '/sys/config.', where is the 10 character system serial number. 3.5.3 Configuration Record Request Sheet On the following page you will find a copy of the MAI 3000 Configuration Record request sheet. This section gives switch settings, cable diagrams and hardware upgrade instructions for the MAI 3000. For more information on the new installation of the system please see the 'MAI 3000 Service Manual', M8108. 4.1 Switch and Jumper Settings This section gives the switch and jumper settings for the different boards that are available for the MAI 3000. 4.1.1 CMB (Central Microprocessor Board) This section gives the switch and jumper settings for the CMB that will most often be changed. For details on other switch and jumper settings for the CMB see M8101, 'MAI 3000 SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg016 Service Manual'. 1. Serial Port Control The serial controller chip has two programmable ports. Each can be configured as RS-232C and support a Modem, Printer or Terminal. In addition, port B supports X.21. NOTE: Only one cable is needed to support printers, terminals and modems. All signal switching is done on the CMB via the jumpers. The RS-232 cable is a pin-for pin connection. No signals or pins are cross connected. Serial Control, Port A - Jumper 29A Jumper 29A is a 'zero-ohm pack', where configuration between a modem or terminal/printer is determined by the orientation of the zero-ohm pack. PORT A: DTE to Modem DCE to Terminal/Printer Pin 1 of a 'zero-ohm pack' Pin 1 of a 'zero-ohm pack' aligned with 29A pin 1. aligned with 29A pin 9. Serial Control, Port B Jumper 29C, 26B and 29B are 'zero-ohm packs', where the orientation of the zero-ohm packs determine the configuration of port B. PORT B RS-232 DTE to Modem DCE to Terminal/Printer Pin 1 of a 'zero-ohm pack' Pin 1 of a 'zero-ohm pack' aligned with 29C pin 1. aligned with 29C pin 9. Pin 1 of a 'zero-ohm pack' Pin 1 of a 'zero-ohm pack' aligned with 26B pin 1. aligned with 26B pin 1. Nothing in 29B. Nothing in 29B PORT B RS-422 (X.21) Pin 1 of a 'zero-ohm pack' aligned with 28C pin 9. Pin 1 of a 'zero-ohm pack' aligned with 29B pin 1. Nothing in 26B. 2. Parallel Port Jumpers These jumpers are used to define the electrical characteristics of the parallel port connector. With the use of shunt blocks the port can be configured to be at TTL levels required for interfacing to a parallel port or the port can be configured with RS-232 levels SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg017 as required for an Auto Dial Modem port (RS-366). Parallel Port (TTL) Auto Dial Port (RS-366) Place shunt blocks at Place shunt blocks at 29E and 29F. 27E and 28F. Nothing in 27E and 28F. Nothing at 29E and 29F. 3. Reset/NMI - JMP 24, JMP 25, JMP 26 These jumpers are used to define the function of NMI/RESET switch on the front panel. In the position with jumper 25 to jumper 26, the switch will cause the system to do a reboot when pushed. In the other position jumper 24 to jumper 25, the switch will cause an Non-Maskable Interrupt. If the software is set to dump pushing the switch will cause a system dump. 4.1.2 1 Megabyte Memory Boards This section gives the switch settings for the 1 megabyte memory boards. ADDRESS RANGE S8 S7 S6 S5 S4 S3 S2 S1 OMB - 1MB ON ON ON ON ON ON ON ON 1MB - 2MB ON ON ON ON ON ON ON OFF 2MB - 3MB ON ON ON ON ON ON OFF ON 3MB - 4MB ON ON ON ON ON ON OFF OFF 4MB - 5MB ON ON ON ON ON OFF ON ON 5MB - 6MB ON ON ON ON ON OFF ON OFF 4.1.3 Winchester Disk Controller This section gives the switch and jumper settings for the Winchester disk controller. Jumper A, WDC BOARD ADDRESS WDC PCBA JUMPER A BOARD ADDRESS PAL & LOCATION 1J 0 903496-001 1-2 CCXXXX Hex 911017-001 1 903496-002 2-3 CDXXXX Hex 911017-007 Jumper B & C, WDC WRITE PRECOMPENSATION Jump B & C (1) DRIVE TYPE 1A - 2A MAXTOR/MICROPOLIS (1300B, 1320) (2) 1B - 2B RODIME (3) 1C - 2C MICROPOLIS (1300A) (4) NOTES: 1. Jump-B controls: drive 0 on the -001 drive 2 on the -002 Jump-C controls: drive 1 on the -001 drive 3 on the -002 2. Write precompensation always off. 3. Write precompensation always on. 4. Write precompensation 'on' at and above the reduced write current cylinder. 4.1.4 4-Way Serial Controller SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg018 This section gives the switch and jumper settings for the 4-way controller. 903390 PCB SW1 (10 position, Location 1A) REV C or D 0 = Switch On 1 = Switch Off DMA ARBITRATION BOARD ADDRESS 1 2 3 4 5 6 7 8 9 10 Board #1 0 1 1 1 1 1 1 0 1 0 Board #2 0 1 1 0 1 1 1 0 1 1 Board #3 0 1 1 0 0 1 1 1 0 0 Board #4 0 1 1 0 0 0 1 1 0 1 PGM #1 - #4 (16 Terminals per PGM set; 4 sets total 904741 PCB TERMINAL PRINTER MODEM 14 - 16 14 - 16 15 - 16 13 - 15 13 - 15 13 - 14 10 - 9 10 - 9 7 - 8 8 - 2 3 - 4 9 - 10 3 - 4 1 - 7 1 - 2 1 - 7 2 - 8 3 - 4 904943 PCB TERMINAL PRINTER MODEM 14 - 16 14 - 16 15 - 16 13 - 15 13 - 15 13 - 14 10 - 12 10 - 12 11 - 12 11 - 9 11 - 9 9 - 10 2 - 4 2 - 4 1 - 2 1 - 3 1 - 3 3 - 4 904943 PCB DCD PULL-UP 7-8 DSR PULL-UP 5-6 4.1.5 8-Way Serial Controller This section gives the switch and jumpers setting for the 8-Way controller. SW1 Settings (10 Position, Location 1G) 0 = Switch On; 1 = Switch Off BOARD ADDR. DMA ARB. BOARD CONFIG. 1 2 3 4 5 6 7 8 9 10 Board #1 0 1 0 1 1 1 1 As Applicable * Board #2 1 1 0 1 1 1 0 " Board #3 0 0 1 1 1 0 1 " Board #4 1 0 1 1 1 0 0 " Board #5 0 1 1 1 0 1 1 " Board #6 1 0 0 1 0 1 0 " * Currently, set these three switches to 111. These switches denote major HW/FW Revisions. 903577 PCB TERMINAL PRINTER MODEM SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg019 PGM #0 14 - 16 14 - 16 15 - 16 PGM #1 13 - 15 13 - 15 13 - 14 PGM #2 10 - 12 10 - 12 11 - 12 PGM #3 11 - 9 11 - 9 9 - 10 PGM #4 2 - 4 2 - 4 1 - 2 PGM #5 1 - 3 1 - 3 3 - 4 PGM #6 5 - 6 (Req'd) 5 - 6 (Req'd) 5 - 6 (Req'd) PGM #7 7 - 8 7 - 8 7 - 8 Jumper Settings From - To Description JMP A 1 - 2 Prom size, 16 KByte (Default) 2 - 3 Prom size, 32 Kbyte JMP B 1 - 2 RAM size, 8 KByte 2 - 3 RAM size, 32 Kbyte (Default) JMP C No Connect 8-Way Configuration (Default) 1 - 2 Reserved for future use JMP D 1 - 2 8 MHz Z80H Clock (Default) 2 - 3 4 MHz Z80H Clock 4.1.6 MCS Tape Controller This section gives the switch settings for the MCS controller. SW1 (8 Position) (0 = Switch On; 1 = Switch Off; X = Do Not Care) 1 2 3 4 5 6 7 8 0 0 0 0 1 1 X M _ _ Mode 8 On (0) for normal operation. 8 Off (1) for drive burn-in mode. 4.1.7 MTS Tape Controller and Formatter Board The 1/2" Tape Controller consists of two assemblies: the SCSI Bus Adapter board and Formatter board. The SCSI Bus Adapter board mounts inside the MAI 3000 CCA. All the switches on this board need to be set to the off(1) position. The formatter board: Dip switch 1, location 7W: all positions On (0) Jumpers W22, 23, 24 Location 6J are open, all others closed. Terminators 6H & 7B should be in place. 4.1.8 LAN (Local Area Network) Controller This section gives the switch settings for the LAN controller. (0 = Switch On; 1 = Switch off; X = Do Not Care) SW1 (8 Position) Address & Interrupt Vector SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg020 1 2 3 4 5 6 7 8 B T A A A A A A _ _ _ _ _ _ _ _ _ Binary coded node address (1 to _ _ 63). Switch 8 is LSB, Switch 3 _ _ is MSB. One unique address per _ _ LAN controller. First unit set _ _ for 000001. Node address 000000 _ _ is illegal. _ _ _ _ _ _ Trunk Cable Terminator Control. _ Switch 2 is closed to connect 100 _ ohm terminator on the trunk; open _ to disconnect. Two and, exactly _ two, controllers (at each end) of _ the network should have switch 2 _ On; all others should have it Off _ _ _ BAIS. Switch 1 set to open on only one LAN controller in the network, all other LAN controllers in the network switch 1 is closed. Two LAN controllers per system is the maximum. SW 2 (8 Position) Bus Arbitration & Address Decode 1 2 3 4 5 6 7 8 Board #1 1 1 1 0 0 1 1 0 Address DFxxxx hex Board #2 1 1 1 0 0 1 0 1 Address DExxxx hex 4.2 Cable Diagrams This section gives the cable diagrams for the peripheral cables that are available for the MAI 3000. 4.2.1 Parallel Printer Cable (Part Number 907455) 4.2.2 CMB to Serial Device Cable (Part Number 907753) 4.2.3 4-Way/ 8-Way "octopus" to Serial Device Cable (Part Number 907752) 4.2.4 8-Way "octopus" Cable With 9-pin Connector (Part Number 907968) 4.2.5 8-Way "octopus" Cable With 25-pin Connector (Part Number 916079) 4.3 Instructions for Upgrading from an MAI 2000 Step 1. Before starting the upgrade verify that the boards that you are carrying over are at minimum revision levels per section 11.0. Step 2. Remove the mounting brackets from the disk or MCS tape drives that are being transferred from the MAI SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg021 2000 system. Mount the drives into the MAI 3000 vertical frame using the same screws removed from the mounting bracket. Note: See cabling diagram in section 4.2. Step 3. Install the disk Radial cable (P/N 916022-001, -002, 916023-001, -002) from the disk drive to the disk controller. Each disk requires a radial cable. Step 4. Install the disk Bus cable (P/N 916021-001, -002) between the disk controller and disk drives. There is Bus cable required to daisy chain up to two drives. A second Bus cable is required for a third disk drive. Step 5. Install the MCS signal cable (P/N 916024-001) from the MCS controller to the tape drive, if there is an internal MCS. Step 6. Install the power cables (P/N 916001-002) to each disk and tape drive that is internal to the MAI 3000 enclosure. One power cable is required for each device. Step 7. Install the boards required for the system, insuring that they are addressed properly. (see 4.1 for details). Step 8. Connect external cables for serial devices, (Serial cables for the 8-way are connected to an "octopus" cable, this cable is then connected to the 8-way. There are four connectors per 8-way "octopus" cable.), parallel printers, LAN, and 1/2" tape drive. Step 9. Attach AC power cord to the rear of the MAI 3000 and plug into the wall power plug. Position the power switch to the NEUTRAL position. WARNING: Because of the added power requirements that the MAI 3000 has the MAI 3000 should not be plugged into the MAI 2000 UPS unit. The system is now ready to be powered on and the software upgrade performed. 5.0 CUSTOMIZATION This section details the information required to customize or change your operating system's parameter file and to modify the NVRAM. 5.1 Operating System Parameters Customization The system hardware configuration is determined at system boot time. Each accessible piece of equipment on the system has an associated '/dev' file. All '/dev' files are either defined by the '/util/configure' utility or are part of the EOS product. Besides the hardware, the operating system can be customized for the needs of each individual site. This is done by the SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg022 use of the '/bin/vconf' command. This command allows you to set some of the parameters that control the BOSS/IX operating system. The values of these parameters are based on your system's software and hardware components, and the environment and performance expected. Section 6.0 of this document describes how to calculate your system's memory requirements. Some of the 'vconf' parameters described in this section affect the amount of memory your system needs. These are the BOSS/IX control parameters that can be changed by the 'vconf' command. root device (root=) This parameter specifies the disk partition that contains the root filesystem. (The default is 1403, "/dev/root") swapper device & size (swap=, size=) This parameter specifies the disk partition that is used for task swapping. If you change the swap device or its size, you must also specify the number of blocks in the swap partition. (The default is 4096: "/dev/swap". The default size is 2 MB.) system ID (system=) You can set the system name that is displayed when the system is booted. mount error override (-oride, -noride) You can specify how the system should handle a filesystem mount error. This error occurs when trying to boot a system that was shutdown without the proper procedures. You can tell the system to ignore the error. A mount error indicates that the root filesystem, and any other filesystems that were mounted when the system was shutdown, are probably damaged. single/multi boot (-single, -multi) You can tell the system to boot into single-user mode or directly into multi-user mode. boot messages (-silent, -verbose) You can tell the system to boot silently or to display boot messages. Once the system has booted, verbose mode remains in affect. Diagnostic messages will continue to be displayed on the system console. Verbose mode is sometimes useful when you are attempting to diagnose a problem. secure boot (-secure, -nonsecure) You can tell the system to require the system administrator ("admin") to enter a password in order to boot. This security feature is active only when the system is booted into single-user mode and a password is present for the "admin" user SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg023 account. crash dump (-dump, -nodump) You can tell the system to generate a dump when the system crashes by using "-dump". The dump might show the cause of the crash. (-nodump) Turns off dump mode. linekill character (linekill=) You can set the keyboard character for the linekill function. The default is the key. The setting of this parameter has no effect on performance or memory usage. erase character (erase=) You can set the keyboard character for the erase function. The default is the key. The setting of this parameter has no effect on performance or memory usage. mountable filesystems (mfsys=) You can specify the maximum number of filesystems that can be mounted on the root filesystem. You will need to increase this number if you define additional filesystems. You will also need to increase this parameter if you add more disk drives. The setting of this parameter has an effect on memory usage. printers (printers=) You can specify the maximum number of printers that can be configured on your system. The number of printers selected has an effect on memory utilization. processes (procs=) You can specify the maximum number of processes that can execute on the system. If you change the number of processes, you should also change these parameters: open files event calls shared text segments logical units file locks All of these require more memory resources. file locks (locks=) You can specify the maximum number of files or portions of files that can be locked at the same time. LAN sockets (sockets=) You can set the number of well-known LAN sockets on your system. dynamic LAN sockets (dsockets=) You can set the number of dynamic LAN sockets on SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg024 your system. LAN buffers (lanbuffers=) You can specify the number of LAN buffers on your system. system buffers (buffers=) You can specify the number of BOSS/IX buffers. The buffers are defined in memory. They are used to cache disk sectors. Each buffer caches 1 512 byte disk sector. open files (opens=) You can specify the number of different files that can be opened on the system at one time. event calls (eventcalls=) You can specify the maximum number of event calls that can be opened at one time. shared text segments (tsegs=) You can set the maximum number of shared text segments (program code segments) on your system. logical units (lus=) You can set the number of logical units on your system. This parameter tells the system the maximum number of pointers to open files the system can have. RAM disk size (ram=) The RAM disk is a feature that is used by the software installation procedures. It can not be changed. debug flag (-debug, -nodebug) "-debug" causes the kernel debugger to be invoked whenever an NMI interrupt is issued or a system crash occurs. NOTE: the debug flag is not available on customer systems. "-nodebug" turns off the debug flag. directory cache (dirc=) The number of directory cache entries is selectable. Directory cache is used to keep in memory information about subpath names, so that path names can be located more quickly than if the directory itself was searched. A larger cache will result in quicker execution of BASIC OPEN's, LOAD's, RUN's, and CALL's, in particular, although other non-BASIC processes may also benefit. terminal input buffer size (ibsize=) Sets the maximum number of characters which may be transferred on a terminal read. This refers to the maximum number of characters that the system can read before seeing a 'CR'. This parameter is for all the terminals on the system and can not be adjusted for only one terminal. terminal type-ahead buffer size (tbsize=) Sets the maximum number of characters which may be queued for a future terminal read. This parameter SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg025 is all the terminals on the system and can not be adjusted for only one terminal. current O.S. parameters (-os) Displays configuration parameters of the currently booted operating system. instruction cache flag (-inca, -noinca) "-inca" enables the on-chip instruction cache. "-noinca disables the on-chip instruction cache. Turning this flag off will cause a serious performance degradation in the operation of your MAI 3000. CMB cache flag (-daca, -nodaca) "-daca" enables the CMB data cache. "-nodaca" disables the CMB data cache. Turning this flag off will cuse a serious performance degradation in the operation of your MAI 3000. To modify the system default configuration file '/etc/conf' from the root partition: perform the following steps: @> mount /dev/boot /mnt @> vconf /mnt/etc/conf -save (options) @> unmount /mnt Recommended Values for "vconf" BOSS/IX Parameters _ SYSTEM _base _add _add _add _maximum _ _ DESCRIPTION _system: _for _for _for _recom- _ _ ----> _ _each _each _each _mended _ _ ---------------_2 user _user _ghost _extra _system _ _ "vconf" _ _1 printer_above _ _printer _values _ _ BOSS/IX _ _ _2 _ _ _(note 1)_ _ PARAMETERS V _ _ _ _ _ _ _ _ _ _ _ _ _ _----------------_---------_-------_------_--------_--------_ _buffers= _ 128 _ 64 _ 64 _ _(note2) _ _----------------_---------_-------_------_--------_--------_ _printers= _ 1 _ _ _ 1 _ 34 _ _----------------_---------_-------_------_--------_--------_ _procs= _ 31 _ 6 _ 1 _ 1 _ 223 _ _----------------_---------_-------_------_--------_--------_ _tsegs= _ 20 _ 4 _ _ _ 148 _ _----------------_---------_-------_------_--------_--------_ _locks= _ 74 _ 5 _ 5 _ _ 234 _ _----------------_---------_-------_------_--------_--------_ _ibsize= _ 512 _ _ _ _ _ _----------------_---------_-------_------_--------_--------_ _tbsize= _ 256 _ _ _ _ _ _----------------_---------_-------_------_--------_--------_ _mfsys= _ 3 _ _ _ _(note 3)_ _----------------_---------_-------_------_--------_--------_ _lus= _ 136 _ 20 _ 20 _ 6 _ 776 _ _----------------_---------_-------_------_--------_--------_ _opens= _ 60 _ 8 _ 10 _ 2 _ 316 _ _----------------_---------_-------_------_--------_--------_ _eventcalls= _ 74 _ 5 _ 5 _ _ 234 _ _----------------_---------_-------_------_--------_--------_ SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg026 _dirc= _ 60 _ 8 _ 10 _ 2 _ 316 _ _ _ _ _ _ _ _ NOTE 1: Values in this column reflect 34 user totals calculated from recommended increments, except for buffers. NOTE 2: Only the size of available memory limits the number of buffers. To many beffers will cause swapping of the user applications. NOTE 3: Allow one mountable file system for each mountable disk partition. A default of 3 allows for a root, boot and 1 other partition. 5.2 Modifing The NVRAM This section describes how you can update the system attributes that are defined in the NVRAM. These attributes are used at boot time to tell the system, which device is the default boot device, which port has the console terminal and its attributes. In addition, the NVRAM contains the down load port and printer port. To change or specify system attributes for the NVRAM, you first need to shutdown the system. At the bootstrap menu, enter 3. At the "" prompt, type "conf" to invoke the NVRAM hardware configurator module. You will be prompted with "". Typing the "lisc" command will display the following command set: disp Display configuration term Specify terminal type boot Specify boot device cons Specify system console down Specify download port prin Specify printer port NOTE: "" is the prompt for the "conf" program module. A list of terms: term definition cs MCS (cartridge streamer) ts MTS (reel-to-reel tape) fw four-way serial controller ew eight-way controller NVRAM Non Volative Random Access Memory. This memory is used to store BOSS/IX parameters. It is not part of main memory. pit parallel interface and timer sc serial communications wd winchester disk (fixed disk) The "disp" command: The display command is used to display the current configuration information found in the NVRAM. The configuration information is displayed in the following SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg027 format: terminal type : evdt boot port : wd0 console port : sc0 baud:9600 data bits:7 stop bits:1 parity:odd flow:xon download port : sc1 baud:9600 data bits:7 stop bits:1 parity:odd flow:xon printer port : pit0 The "boot" command: This command can be used to specify/change the boot device. You will be prompted with: boot dev : (enter 'ts', 'wd', 'cs', 'sc' or 'fw') boot unit : (enter unit number on the device) The "term" command: You can use this command to change the terminal type for the system console. You will be prompted with: term type: (enter 'evdt', 'edt', 'vdt7270', or 'other') The "cons" command: This command allows you to change the console terminals attributes. You will be prompted for console device: (enter 'sc', 'fw' or 'ew') console unit: (enter '0') baud rate: (enter correct baud rate for the term) data bits: (enter correct data bits for the term) stop bits: (enter correct stop bits for the term) parity: (enter correct parity for the term) flow control: (enter correct flow control for the term) The "down" command: The prompts for the "download" port are similar to those for the "console" command. The download port is currently used only for system diagnostics. The "prin" command: The printer can be either the parallel printer or a serial printer. The printer "pit0" is the default (The parallel printer device is "pit" and there is only one unit number: 0). You should enter "pit" to set the printer to the parallel printer. A Normal "conf" Session Each time you update the NVRAM, you should then display the contents (the "disp" command). After determining the characteristics that you want to change, enter one of the change commands ("boot", "term", "cons", "down", or "prin"). To view the changes that you have made use the "disp" command. The "rese" command can be used to make all changes active. Once you have made all the necessary changes, invoke the bootstrap menu, by typing 'shutdown' . SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg028 6.0 Memory Usage This section describes how to determine the memory requirements for the MAI 3000. All BOSS/IX systems have different memory requirements. A system's memory requirement is based on its hardware configuration and software load. Specifically, the number of peripheral devices (i.e. terminals and printers) and software packages (such as BASIC, BASIC applications, utilities, etc.) determine a system's memory needs. This section explains two methods used to determine the amount of memory needed for a system. The first method approximates a systems memory requirements -- and can be used if the system closely fits one of the standard system configurations. The second method calculates the memory requirements for the best system performance -- and is used for non-standard system configurations. 6.1 Approximating A System's Memory Requirement Table 6A shows some standard system configurations which can be used to approximate the amount of memory a system needs. The number of users (terminals), ghost tasks, and printers differ for each of these standard configurations. First, find the standard configuration that most closely matches the system in question, by scanning down the user/terminals, ghost-task, and printers columns. Second, scan across the table to memory-needed column -- this is the system's memory requirements. NOTE: This table 6A assumes that the system in question will be executing 60% BASIC and BASIC applications programs, and 40% non-BASIC applications. If the system will be executing a higher percentage of non-BASIC programs, it will need more memory. Table 6B shows how to set up the BOSS/IX configuration ("vconf") parameters for each of the standard system configurations in table 6A. In other words, if one uses the approximation method to determine a system's memory requirements, table 6B can be used to set up the BOSS/IX configuration parameters. The approximation method is an easy and accurate way to determine a system's memory needs, if its configuration is close to one of the standard configurations. However, if it does not closely fit one of the configurations shown, the calculation method should be used (see section 6.2). _ Standard _ User/ _ Ghost _ Printers _ Memory _ Max. _ _ Config. _ Terminals _ Tasks _ _ Needed (MB) _ Concurrent _ _ _ _ _ _ _ Users _ _ Number 1 _ 2 _ 0 _ 1 _ 1 _ 3 _ _-----------_-----------_-------_----------_-------------_------------_ _ Number 2 _ 9 _ 2 _ 2 _ 2 _ 12 _ _-----------_-----------_-------_----------_-------------_------------_ _ Number 3 _ 16 _ 4 _ 4 _ 3 _ 16 _ _-----------_-----------_-------_----------_-------------_------------_ _ Number 4 _ 22 _ 6 _ 6 _ 4 _ 18 _ _-----------_-----------_-------_----------_-------------_------------_ SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg029 _ Number 5 _ 28 _ 8 _ 9 _ 5 _ 23 _ _-----------_-----------_-------_----------_-------------_------------_ _ Number 6 _ 34 _ 10 _ 10 _ 6 _ 25 _ _ _ _ _ _ _ _ TABLE 6A Approximating the Memory Requirements NOTE: The number of user/terminals shown is approximately the highest number which can be supported in the memory shown. ___________________________________________________________ _ "vconf" BOSS/IX _ Standard Configuration (see Table 6A): _ _ Parameter _ _________________________________________ _ _Number_Number_Number_Number_Number_Number_ _ _ 1 _ 2 _ 3 _ 4 _ 5 _ 6 _ _-----------------_------_------_------_------_------_------_ _buffers= _ 128 _ 704 _ 1280 _ 1792 _ 2304 _ 2816 _ _-----------------_------_------_------_------_------_------_ _printers= _ 1 _ 2 _ 4 _ 6 _ 8 _ 10 _ _-----------------_------_------_------_------_------_------_ _procs= _ 31 _ 76 _ 122 _ 162 _ 203 _ 242 _ _-----------------_------_------_------_------_------_------_ _tsegs= _ 20 _ 48 _ 76 _ 100 _ 124 _ 148 _ _-----------------_------_------_------_------_------_------_ _locks= _ 74 _ 119 _ 164 _ 204 _ 244 _ 284 _ _-----------------_------_------_------_------_------_------_ _ibsize= _ 512 _ 512 _ 512 _ 512 _ 512 _ 512 _ _-----------------_------_------_------_------_------_------_ _tbsize= _ 256 _ 256 _ 256 _ 256 _ 256 _ 256 _ _-----------------_------_------_------_------_------_------_ _mfsys= _ 3 _ 3 _ 4 _ 4 _ 5 _ 5 _ _-----------------_------_------_------_------_------_------_ _lus= _ 136 _ 322 _ 556 _ 656 _ 864 _ 1030 _ _-----------------_------_------_------_------_------_------_ _opens= _ 60 _ 138 _ 218 _ 290 _ 364 _ 434 _ _-----------------_------_------_------_------_------_------_ _eventcalls= _ 74 _ 119 _ 164 _ 204 _ 244 _ 284 _ _-----------------_------_------_------_------_------_------_ _dirc= _ 60 _ 138 _ 218 _ 290 _ 364 _ 434 _ _____________________________________________________________ TABLE 6B "vconf" BOSS/IX Parameters for Standard Configurations ___________________________________________________________________ _BOSS/IX _memory _param.'s_total _ Memory for each _ _Parameters _used for_for base_memory _ additional: _ _(set by _each _config- _for base_-------------------------_ _"vconf") _param. _ uration_system _ USER _ GHOST _ PRINTER _ _ _(bytes) _system _(bytes) _ _ _ _ _--------------_--------_--------_--------_-------_-------_---------_ _buffers= _ 586* _ 128 _ 75008* _37504* _ _ _ _--------------_--------_--------_--------_-------_-------_---------_ _printers= _ 268 _ 1 _ 268 _ _ _ 268 _ _--------------_--------_--------_--------_-------_-------_---------_ _procs= _ 390 _ 31 _ 12090 _ 2340 _ 390 _ 390 _ _------------- _--------_--------_--------_-------_-------_---------_ _tsegs= _ 24 _ 20 _ 480 _ 96 _ _ _ _--------------_--------_--------_--------_-------_-------_---------_ _locks= _ 40 _ 74 _ 2960 _ 200 _ 200 _ _ _--------------_--------_--------_--------_-------_-------_---------_ SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg030 _ibsize= _ 512 _ 2 _ 1024 _ 512 _ _ _ _--------------_--------_--------_--------_-------_-------_---------_ _tbsize= _ 256 _ 2 _ 512 _ 256 _ _ _ _--------------_--------_--------_--------_-------_-------_---------_ _mfsys= _ 424 _ 3 _ 1272 _ _ _ _ _--------------_--------_--------_--------_-------_-------_---------_ _lus= _ 40 _ 136 _ 5440 _ 800 _ 800 _ 240 _ _--------------_--------_--------_--------_-------_-------_---------_ _opens= _ 86 _ 60 _ 5160 _ 688 _ 860 _ 172 _ _--------------_--------_--------_--------_-------_-------_---------_ _eventcalls= _ 20 _ 74 _ 1480 _ 100 _ 100 _ _ _--------------_--------_--------_--------_-------_-------_---------_ _dirc= _ 44* _ 60 _ 2640* _ 352* _ 440* _ _ _--------------_--------_--------_--------_-------_-------_---------_ _Totals _ _ _108334* _42848* _ 2790* _ 1158 _ _ excluding _ _ _ or _ or _ or _ or _ _ hash tables _ _ _106 KB _42 KB *_ 2.7KB*_ 1.1 KB _ _--------------_--------_--------_--------_-------_-------_---------_ _Totals with _ _ _108 KB _ _ _ _ _ hash tables _ _ _ _ _ _ _ _____________________________________________________________________ Table 6C BOSS/IX Operating Parameters and Memory Requirements * Excludes hash table size which must be calculated separately based on the number of entries requested, there added to the total system requirement. ______________________________ _Number of Entries _ Memory _ _Requested _ Required _ ________________________________ _through 63 _ .5 KB _ _ _ _ _64 through 127 _ 1 KB _ _ _ _ _128 through 255 _ 2 KB _ _ _ _ _256 through 511 _ 4 KB _ _ _ _ _512 through 1023 _ 8 KB _ _ _ _ _1024 through 2047 _ 16 KB _ _ _ _ _2048 through 4095 _ 32 KB _ _ _ _ _4096 through 8191 _ 64 KB _ _ _ _ _8192 through 16383 _ 126 KB _ ________________________________ Table 6D Memory Required for Hash Tables This table is used to obtain the amount of memory needed for hash tables for either 'buffers' or directory cache' operating parameters (see table 6C). The per entry charge is not included here and must be added to the value from this table. Users _ Buffers _ Procs _ Tsegs _ Locks _ Lus _ Opens _ ECs _ Dirc ------_---------_-------_-------_-------_-----_-------_-----_----- SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg031 2 _ 128 _ 31 _ 20 _ 74 _ 136 _ 60 _ 74 _ 60 _ _ _ _ _ _ _ _ 6 _ 384 _ 55 _ 36 _ 94 _ 216 _ 92 _ 94 _ 92 _ _ _ _ _ _ _ _ 10 _ 640 _ 79 _ 52 _ 114 _ 296 _ 124 _ 114 _ 124 _ _ _ _ _ _ _ _ 14 _ 896 _ 103 _ 68 _ 134 _ 376 _ 156 _ 134 _ 156 _ _ _ _ _ _ _ _ 18 _ 1152 _ 127 _ 84 _ 154 _ 456 _ 188 _ 154 _ 180 _ _ _ _ _ _ _ _ 22 _ 1408 _ 151 _ 100 _ 174 _ 536 _ 220 _ 174 _ 220 _ _ _ _ _ _ _ _ 26 _ 1664 _ 175 _ 126 _ 194 _ 616 _ 252 _ 194 _ 252 _ _ _ _ _ _ _ _ 30 _ 1920 _ 201 _ 132 _ 214 _ 696 _ 284 _ 214 _ 284 _ _ _ _ _ _ _ _ 34 _ 2176 _ 223 _ 148 _ 234 _ 776 _ 316 _ 234 _ 316 Table 6E Recommended "vconf" Totals by Number of Users Note: Buffers should be allocated freely. Typical MAI Basic Four performance figures are based on 1.5 MB of memory buffers. This column simply represents the value based on the stated recommendation of 64 buffers per task. 6.2 Calculating A System's Memory Requirement This section describes how to calculate the number of memory boards a system requires for adequate performance. The calculations are based on the system's hardware configuration and software load. Software load is defined to be the number and types of processes running on the system. This section steps through an example based on system configuration number 3 in Table 6A; a 16 user system. Step 1 First, add the space required for the operating system, table space, and dynamic space required for the base configuration. NOTE: 1 KB = 1024 bytes 250 KB This is the memory requirement for the BOSS/IX operating system. This includes space for the system's interrupt vectors and operating system's text (code) and data segments. 107 KB** This is the memory requirement for BOSS/IX table space for the base configuration: 2 users (terminals), one printer, and no ghost tasks. Note: additional table space must be added for each additional resource above that in the base configuration (see step 2). Note: this excludes the memory required for hash tables for buffers and directory entries. 65 KB** This is the memory requirement for the operating system's dynamic work space (or unswappable memory) for the base configuration. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg032 Step 2 Next, add in table space needed for resources beyond the ones described in the base configuration. (If the system will be configured like the base configuration skip this step.) Note: the MAI 3000 is a table driven system, and for maximum performance extra memory must be allocated for resources beyond the ones described in the base configuration. 42 KB** This is the memory required as table space for each additional user above the two that are allocated in the base system. 2.7 KB** This is the memory required as table space for each ghost task in the system. 1.1 KB** This is the memory required as table space for each additional printer above the one that is included in the base system. 1.5 KB** This is the memory required for dynamic work space for each additional process (i.e. "proc") above 31 that are included in the base system. ** Memory required for BOSS/IX table space and dynamic work space. These values are the memory allowance assuming that the configuration parameters are set according to table 6B. If the system parameters are set differently, use section 6.3 and table 6C to calculate the memory required for the OS table and OS dynamic work space. Step 3 Add the space needed for system processes for the base system configuration. 100 KB This is the memory allowance for system tasks. System tasks for the base system include: a printer despooler process, a system update process, a system error log process, and two command interpreters. The total memory required to have all system processes in memory at the same time is approximately 200 KB. However, 100 KB should be used in this calculation because system processes wait on system events and it is not likely that all system processes will want to execute at the same time. Furthermore, these processes, when waiting for events, can be swapped to secondary storage, which will have little effect on system performance. Step 4 Add the space needed for any additional system processes beyond the ones specified in the base configuration. This is a memory allowance for data and stack segments for an additional despooler task. An allowance for text (code) space is not necessary, because two despooler tasks will share the same code segments. 30 KB This is the memory needed for each additional printer despooler, above the one that is SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg033 allocated in the base configuration. This is a memory allowance for the data and stack segments for an additional despooler task. An allowance for text (code) space is not necessary, because two despooler tasks will share the same code segments. 15 KB This is the memory required for each user (terminal) that will be executing tasks concurrently. This is the memory allowance for each additional command interpreter. It is space needed for the interpreter's data and stack segments. Note: memory allowance for text (code) space is not necessary, because multiple command interpreters share the same code segments. Note: if the system is configured for ten operators, but the system only has five terminals -- i.e. a maximum of five users logged in at any instant-- then only 75 KB (5x15 KB) need to be allocated. Furthermore, if one of the system terminals is seldom used, then space for that terminal does not have to be allocated. Step 5 Next, add the space needed for applications processes. 160 KB This is space needed for each unique, non-BASIC task that will be executed concurrently on your system. Such tasks include the BASIC interpreter, utility programs, LAN, Informix, communications, BOSS/IX command interpreter, etc. Note: only one BASIC interpreter is needed to support any number of BASIC programs. This value is a rough estimate. All processes require different amounts of memory. When computing the memory required for application tasks, consider how often each application is used. For example, if the system seldom executes BOSS/IX commands or utilities, only a percentage of the total space needed to execute these processes will be required. However, when the system is loaded, and these processes are executed, system response time may increase due to excessive amounts of swapping. 60 KB This is the memory required for each BASIC program. This space is the allowance for the data and stack segments for each BASIC program. Note: all BASIC programs share the same text (code) segment. Furthermore, this value is not exact, for some applications may require more memory and some may require less memory. 64 KB This is the memory for each ghost task that SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg034 will be executed concurrently. This is the space needed for each ghost tasks' stack and data segments. Text space is not allocated because all ghosts share the same BASIC process text segment. The sum of steps 1 thru 5 is the system's "memory requirement" Step 6 Determine the memory/performance trade-offs. The value calculated in steps 1 thru 5 is the "memory required" for good system performance. However, this value is not exact and may be raised or lowered which will increase or decrease performance respectively. By lowering the memory required value one can save the costs of an extra memory board, but at the expense of performance. In other words, systems will run with less memory than required, however, the system overhead for swapping will increase. If the cost of memory is more important than user responsiveness, multiply the system's memory requirement (calculated in steps 1 thru 5) by a value between 0.7 and 1.8. Multiplying the memory required value by 1.0 will cause normal amounts of swapping; multiplying it by 0.7 will cause processes to be swapped to/from memory more frequently. Multiplying the "memory requirement" by some value greater than 1.0 will decrease the OS overhead for swapping. Note: do not run a system with less than 70% of the "memory required" value -- this will cause excessive amounts of swapping. The results of this calculation is your system's "memory need". Step 7 Next compute the number of memory boards that the system needs. Dividing the "memory needed" value, calculated in step 6, by 1024 KB (memory needed /1024 KB). Note: 1024 KB is the amount of memory on a 1 MB board. If a fraction results, round off to the next highest whole number. The value calculated is the "number of boards needed". Note: a maximum of six memory boards can be installed in an MAI 3000 system. If the value calculated in this step is greater than six memory boards, even with the 0.7 degradation factor (see step 6), then you are overloading your system! 6.2.1 Example of How to Calculate a System's Memory Requirement This example shows how to compute the memory requirement for a system with 16 terminals, 4 ghost and 4 printers. Thirteen of the terminals are dedicated to running BASIC applications: accounts receivable, accounts payable, payroll and word processing. The remaining terminals are used to run the utilities, the commands, and the Informix database application. Some of the applications use ghost tasks to output reports to printers. Step 1 thru Step 5 Add these numbers to compute "memory required" SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg035 250 KB Base operating system 106 KB Table space for base system 65 KB OS dynamic work space for base system 2 KB Hash table space for directory cache entries (tables 6C and 6D) 16 KB Hash table space for disk buffers (tables 6C and 6D) 42 KB x 14 Allowance for table space for 14 additional users (total of 16 users terminals) 2.7KB x 4 Allowance for table space for 4 ghost tasks 1.1KB x 3 Allowance for table space for 3 additional printers 1.5KB x 91 Allowance for dynamic work space for 14 additional users ("procs"-base "procs"). 100 KB Allowance for system processes 30 KB x 3 Allowance for concurrent printing to the 3 additional printers. 160 KB x 3 Allowance for the BASIC interpreter and for the utilities/commands/Informix. 15 KB x 3 Allowance for concurrent terminals. 60 KB x 13 Allowance for concurrent basic applications. 64 KB x 4 Allowance for 4 ghost tasks. Total = 2928 KB = "memory required" Step 6 Compute "memory needed" For adequate system performance with frequent swapping of applications tasks and a reduced number of disk buffers: "memory needed" = 2928 * 0.7 = 2048 KB or 2 memory boards For good system performance with very little swapping: "memory needed" = 2928 * 1.0 = 2928 KB or 3 memory boards For best system performance with much caching: "memory needed" = 2928 * 1.3 = 3806 KB or 4 memory boards The approximate method of determining a system's memory requirement (section 6.1, table 6A) shows that a system with 16 users (terminals), 4 printers, and 4 ghost tasks requires 3 MB of memory. The calculation method, described in this section, shows that such a system will have different performance characteristics depending on the number of boards the system has. 6.3 Calculating BOSS/IX Table Space and Dynamic Work Space This section describes how to calculate the size of the operating system table space and the size of the operating SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg036 system dynamic work space needed by any configuration. The calculation method (section 6.2) is accurate if the system's configuration parameters are set according to Table 6B. If the BOSS/IX parameters are not set according to table 6B, use the method described in this section to calculate the amount of memory needed for table space and dynamic work space. Table 6C shows the amount of memory allocated for each operating system configuration parameter; it shows the parameters for the base system configuration; and it shows how the 106 KB value for table space, used in section 6.2, was calculated. To determine the table space for any configuration multiply the value of each configuration parameter by its corresponding memory allowance (see column 1, table 6C). Next, add the result of these calculations (see column 2). The result is the allowance for table space. To determine the memory allowance for the operating system dynamic work space (i.e. unswappable memory) use the following formula: "dynamic memory" (bytes) = (32 + ("opens" /4) +(("procs" * 2704)/512/2)) *512 The variables in this formula from left to right are: 32 - the number of 512 byte pages for miscellaneous operating system space "opens"- the number of open files configured "procs"- the number of processes configured 2704 - size (bytes) for each process's user area / 512 - for converting into 512 byte pages / 2 - one half the number of pages * 512 - for converting pages into bytes For the base configuration the dynamic memory allowance is: "dynamic memory" (bytes) = (32 + (60 /4 ) +((31 * 2704)/ 512 / 2)) * 512 = 65976 bytes or 64.4 KB For the example system (see section 6.2.1) the memory allowance is: "dynamic memory" (bytes)= (32 +(218 /4 ) + (( 122 * 2704) / 512 / 2)) * 512 = 209232 bytes or 204 KB 65 KB (base size) + (91 * 1.5 KB ) (extra procs, 122-31)= 201 KB 7.0 UPGRADE FROM THE MAI 2000 CHECKLIST This section provides a site survey checklist, system configuration planning guide, and parts ordering questionaire. Before ordering an MAI 3000 upgrade, it is recommended that you first read this section, follow the checklists and order the parts required. By doing this you will ensure that you have the correct parts required for the MAI 3000 upgrade. For information on the actual steps required to perform the upgrade see section 4.0. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg037 7.1 SITE SURVEY CHECKLIST Identify which hardware will be used from the MAI 2000 system. 1. Yes No Will disk drives be used from the MAI 2000? Indicate type and number of each: Formatted MAXTOR 120 MAXTOR 71 MICROPOLIS 43 RODIME 44 RODIME 33 MAXTOR 88 NOTE: These are the only disk drives that can be upgraded from an MAI 2000. 2. Yes No Will 1/4" streamer be used from the MAI 2000? Indicate type Streamer is presently in a separate enclosure. Streamer is presently installed internally in the CCA. 3. Yes No Will controllers be used from the MAI 2000? Indicate type Winchester Disk Controller (Part# 903496) 1/4" MCS Controller (Part# 903406) 1/2" MTS Controller (Part# 903528) LAN Controller (Part# 903405) 4-Way Controller (Part# 903390) NOTE: 2-Board Winchester Disk Controller is not allowed. 4. Will 1/2" MTS tape drive be used from the MAI 2000? Yes No 5. Will a Parallel printer be used from the MAI 2000? Yes No 6. Will Serial printer(s) be used from the MAI 2000? Yes No 7. Will VDT(s) be used from the MAI 2000? Yes No 8. Is there sufficient AC power outlets for the CCA and peripherals? SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg038 Yes No If NO, find a place with sufficient outlets or have an electrician install more. Avoid using excessive connections into the same outlet. The use of extension cords should be avoided. 9. Is there sufficient physical space for the new system and associated cables? Yes No The area needed should be 28" high by 10" wide by 25" long, in addition allow for 9" around the system for proper airflow for cooling. If NO, clear an area sufficient to place the system, cables, and peripherals. 7.2 System Configuration Planning Guide 1. Check one of the following DISK/TAPE configurations. Internal 1/4" MCS with a maximum of 3 disk drives. External 1/2" MTS with a maximum of 3 disk drives. External MCS will be mounted inside. The cable included in the upgrade kit is for internal mounting. 2. Configure I/O controllers. Indicate number of controllers to be used. number of 1-Board WDC (2 disk drives supported per controller, 2 Max.) number of 1/4" Tape controllers to be used (1 Max.) number of 1/2" Tape controllers to be used (1 Max.) number of LAN controllers to be used. (1 Max.) number of 4-Way controllers to be used. (4 Max.) number of 8-Way controllers to be used. (4 Max.) NOTE: Total number of controllers allowed is 6. Total number of 4-ways and 8 ways allowed is 4. 3. Pick memory size. Determine the number of memory boards needed. See section 6.0. number of 1MB Memory boards. NOTE: MAI 2000 Memory boards cannot be used on the MAI 3000. A Maximum of 6 memory boards is allowed. The upgrade kit includes 2MB of memory. 7.3 Parts Ordering Questionaire 1. Do you have enough disk drives that you can transfer from the MAI 2000? Yes No If No, order the appropriate number of disk drives that you require. 2. Do you have a 1/4" Streamer drive from your MAI 2000? SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg039 Yes No If you have an MCS or are ordering an MCS, order the upgrade kit which has the front panel with an MCS slot. The MCS will be mounted inside the CCA. All cables are included. If they will only have an MTS, order the upgrade kit with the blank front panel. NOTE: If you presently have a 1/2" MTS tape drive on your MAI 2000 and wish to use it on the MAI 3000, you need not order any parts to move it. 3. Do you have enough I/O controllers? Yes No If YES, order only external cables that are needed. External cables from the MAI 2000 can be used on the MAI 3000. If NO, order controllers and cables needed. The serial cables for the 8-Way are the same as the serial cables for the 4-Way. 4. Configure the base MAI 3000 system that is required (less the parts you already have) and place order. NOTE: The MAI 2000 UPS can not be used with the MAI 3000. 8.0 DUMP PROCEDURE The MAI 3000 provides a 'user friendly' program to recover from any premature system shutdown situation (Crash). A 'premature shutdown' is typically a power loss, inadventant use of the RESET/NMI button, forced dump for troubleshooting, or fatal operating system error. When the user attempts to reboot, the system will check all filesystems to see if any of them were left mounted. If it finds a filesystem that was left mounted it will repair that filesystem. Some data maybe lost, but the filesystem will be restored to a usable condition. This procedure is automatic and only requires that the user enters a , after reading the message that a filesystem was left mounted. In addition to repairing mounted filesystems, the MAI 3000 recovery program will allow the user to save a copy of the system's memory at the time of the crash. This memory information is called a dump. The rest of this section gives the information required to configure your system for it to dump, save the dump to tape and how to force a dump. 8.1 Configuring The System To Dump For the system to produce a dump if it crashes the system configuration file, '/etc/conf' file on the boot partition, has to have dump enabled. The dump enable flag can be set by the use of the '/bin/vconf' command. The use of this command is detailed in section 5. If the system is set for 'nodump', a crash will not produce a dump. Since system dumps help determine the cause of a crash, it is recommended that when a system is setup the dump flag is set on. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg040 8.2. Saving The Dump To Tape When the system crashes, the monitor terminal will display the crash information, and prompt the user with the following message: System dump to 1/4 IN. CARTRIDGE TAPE. Insert CARTRIDGE into drive and press when ready to begin system dump. NOTE: This message and all of the rest in this section is for a system with 1/4 inch tape installed. A system with 1/2 inch tape installed will prompt with similar messages for the 1/2 IN. tape. The user should put a scratch tape in the tape drive and enter to save the dump to tape. If there is no tape in the tape drive or there is a problem writing to the tape, a message explaining the error and the following prompt is displayed: Restart system dump? (y/n) The user should ensure that the problem is solved and then enter 'y'. If the user answers 'n' to this prompt 2MB of the dump will be written to the swapper. See 8.2.2 in this section for saving a dump to tape from the swapper. The system will display the following message during the save to tape. Starting dump to 1/4 IN. CARTRIDGE TAPE (size xxxx Kb).. Where 'xxxx' is the amount of memory on the system. When the dump is complete the system will display: System dump to 1/4 IN. CARTRIDGE TAPE complete. The bootstrap menu will then be displayed. The user is then required to enter an option from that menu. If option 1 is used the system will proceed with the system crash procedure. 8.3 Forcing A System Dump For troubleshooting reasons, a look at the system's memory might be required, for example, if all the terminals on a system are frozen, then a dump of memory will help determine the problem. The following steps outline the steps to force a system dump: 1) Ensure that jumper pin 24 is jumped to jumper pin 25. These jumper pins are on the CMB, and can found by looking at the back of the CCA. Since it is recommended that a service person moves this jumper, the system should be jumped for a dump when it is installed. 2) Turn the front panel key to the 'RESET/NMI/START' position. 3) Press the 'RESET/NMI' button on the front panel. After the 'RESET/NMI' button is pressed the system will SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg041 complete a system crash; and the system dump can then be saved to tapes described above. 9.0 FOR YOUR INFORMATION This section gives the warnings and cautions for the 7.2C Operating System, and a work around if one is available: THIS SECTION WILL BE ENTERED WHEN THE FINAL RELEASE MEMO IS PUBLISHED WITH KNOWN PROBLEMS AND WORKAROUNDS. 9.1 Operating System (EOS) The 'lpr' command displays a confusing error message "Undefined printer '(NULL POINTER)'." when a printer is configured but printer type is missing from the '/etc/defaults' file. Workaround: Ensure that the printer is defined in the '/etc/defaults' file. The 'iconf' command show the same information as it did for the MAI 2000, with no additions. For that reason the floppy disk will still show and the number of eight ways will not show. Workaround: Use the configuration print out that comes with the security configuration record to determine the number of eight ways configured. 9.2 Utilities (EUT) The 'fcreate' will display the file name in multiple line when file name was given. Workaround: None The 'frepair' with the analyze on, the file must have write permission. Workaround: Use the filemodes command to change the filemodes. The 'ddelete' creates a directory when user enter any non-existent directory and hit at error prompt. Workaround: None Cosmetic Error Description: - The 'mrestore', 'mcompare', and 'msave' with the verify on will report key files as deleted in the verify report. - The 'fcopy' gets error message 'Unexpected end of file on "sort".' when user tries to copy a sort file that was expanded using 'fchange'. - The 'msave' displays a list of files saved to tape. In this list it displays the sort file type as a direct file. - The 'frepair' with analyze/repair on, will display debugging statement 'V2 Spawn basic' while working on a basic program. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg042 - The 'fcopy' displays an error message 'Unexpected end of file on "any sortfile"' when user tries to copy any sort file to the same directory with rename option on. - The 'fcreate' displays wrong error message 'File "" already exist' when file name is '/'. It should have the file name in double quotes. - The 'fsdbg' displays wrong error message 'UNKNOWN DEVICES ""' when automatic filesystem analysis was performed on wd1 and the system does not have a second drive. It lacks the device name in quotes. 9.3 BASIC (EBS) In the following basic statement, "PRINT STR(I)", using 'bsearch' to replace the I's with J's, neither of the I's will be replaced because when the I in PRINT is replaced with J it causes a Syntax error and go on to the next statement without replacing I in STR(I). Workaround: Choose scope for literal only. The 'bencrypt' will get an error 12 if entire path name of a program is greater than maximum 40. An error 10 occurs if path name is longer than 40 after ".bak" is added with the creating backup option on, It will create a empty string file with the name of the program that was to be encrypted plus ".bak". Workaround: Use the 'ENCRYPT' directive in basic. The 'brenumber', 'bcompare', 'bxref' when device is file, it will give the same output to the file as it would the printer so file will contain all the mnemonics and it is hard to read and understand the report. Workaround: Do not use file report device. 9.4 MAGNET via LAN and X.25 The following are the notes and cautions for MAGNET via LAN and X.25: - The minimum memory requirement is 2 MBYTES. - RCX (Remote command execution) is still decommitted as on 7.2B and 7.2A. - Concurrent B$NET/FTF and MAGNET activity can cause error -527's for MAGNET activity. - A LAN timeout error -554 can occur with haeavy system activity. This is a retryable error and is caused by the remote file access processes being swapped out. - When 'rcopy' is used to update a remote file (replace existing files) and the destination file is currently locked by another process, the copy will still occur and the data is 'temporarily stored' in the remote system until the file is unlocked. There is no message on the source system stating this is so. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg043 - Using MAGNET with FTF can cause aborts to occur for some file transfers of FTF. Retransmit the file. - 4800 Baud is the maximum speed for X.25. - Do not use the 'lanpoll' command with LAN networks. It can cause the LAN controller to be turned off and task hangs. 9.5 B4NET/FTF via LAN and X.25 The following are the notes and cautions for the B4NET/FTF via LAN and X.25: - The minimum memory requirement is 2 MBYTES. - Reschedule a transfer with the 'high' priority if the transfer gets scheduled with the 'normal' priority. The local file handler will schedule all transfers as 'normal' if it is active (transferring files) when new transfers are scheduled. - If attempting to transfer a locked file, the status file will display the file name. - When there is heavy activity on the system, enough to cause swapping of processes, abort 79's can occur. If this occurs, use the rescheduling option for file transfers. Aborts 149's or 77's can also occur. - Occassional link failures in X.25 can occur depending on system load and link load. Restart the link and reinitiate transfers. - 4800 Baud is maximum speed for X.25. 9.6 27xx/37xx Batch Communications (EBC) Following transmission of a file transfer, if an user transmits in text or transparency, the 'EOF RCVD' message may get 'saved' into an XXXnnn file. Workaround: If this occurs, just delete the file. Records greater than 510 bytes are corrupted in 'Expanded Transparency' mode. Workaround: Use one of the other ten emulator modes to transmit this file. If one attempts to run EBC without having a proper public key installed, the message is output, but not recorded in the local status log. Workaround: None If transmit modes are mixed - i.e. Expanded Buffer with Standard buffers (512 buffer size versus 169 buffer size) - BCOM will suspend. Workaround: Do not mix transmit modes - use 2780 Standard with 2780 Standard, 3780 Standard with 3780 Standard, etc. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg044 4800 Baud is the maximum speed allowed for 27xx/37xx. 9.7 Intersystem Transport Package (EIT) The ATP for this release uses the LEVEL 3 protocol. Ensure that the systems you are communicating with are also at the level 3 ATP. (See software announcement 141) 9.8 Hardware A turned off MAI 3000 power supply causes discharge spikes when removed from the CMB if the line cord is still plugged into the AC. The turned off power supply has capacitors which are charged directly from AC line. The discharge is known to damage MMB piggy-back boards. Workaround: Disconnect AC line cord from power source and wait for one minute before pulling power supply off CMB. Dual disk controller requires a different bus address. Workaround: Get a special PAL for a 2nd disk controller. 9.9 Diagnostics Revision 7.2C*12 (final release for DIAG) The SCC diagnostics cannot be run with CPU instruction cache on, or errors will occur. Workaround: The EXEC command "cache 0" can be entered to turn off the processor cache before entering the "run" command to prevent the errors. the manual intervention tests for external loopback are not included. The DISKFS program produces errors when you attempt to build a test loop, using the 'build' command. Entry of the EXEC 'build' command will produce a bus error. Workaround: Enter the EXEC command 'cmd' and two returns followed by the command 'scmd' and a return. After entry of these commands, the 'build' command can be entered. When the 'install' command is used to install the diagnostics on the disk, from half inch or mcs tape, the error "Disk Error 22" will occur while installing the programs 'SIT' if instruction cache is on. Workaround: Enter the EXEC command 'cache 0' before entering the 'install' command. The 'sbinit' command can only be used for drive 0. Workaround: Configure drive 1 as drive 0, after the install of the diagnostics than reconfigure the drive as the unit you wish it to be. There are some timing problems in the use of the Line Printer option in the diagnostics. The entry of the command "option lp" allows for all console I/O to be printed to the printer attached to the CMB PIT port. Some printers may timeout or not function correctly. Workaround: Enter the 'reset' command after a programs is loaded, followed by the 'option ld' command, and the 'init' SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg045 command for the loaded diagnostic. The 'SIT' program allows testing of all system components. Some errors may occur in the FWAY and LAN controller tasks. The errors are intermittant and should not normally occur. Due to some timing problems, the tasks associated with testing of the LAN and the 4 Way may fail. Workaround: None The loopback tests for the 4 Way and 8 Way controllers in the 'SIT' program is not working correctly and is not supported. Workaround: Remove the loopbacks, if they were installed to run the FWAY and EWAY Logic Test, and these controllers will be tested in the internal loopback mode. When terminals are attached to the ports that are tested by 'SIT', transmit only testing is done. Workaround: None Use of the 'option' command will cause the 4 Way and 8 Way boards to be reinitialized. This will cause errors in some of the Function Select commands, such as the 'baud' commands in FWFS and EWFS. The 'run' command in the PORTS test will also fail. Workaround: Enter the 'init' command after entering an 'option' command. The DISK diagnostic test 25 will intermittantly fail due to the stop and start commands for the disk controller to park the heads. This is most common with the drive under test is a MAXTOR drive. Workaround: Be aware that the error might occur or remove the test by entering the command 'test -25' before the 'run' command to delete the test. 10.0 DOCUMENTATION Following is a list of documentation for the MAI 3000. o MAI 3000 User Guide - M6202 o BOSS/IX 7.2 User Reference Manual - M6210 o BOSS/IX 7.2 Technical Reference Manual - M6224 o MAI 3000 Diagnostics Manual - M6204 o MAI 3000 Service Manual - M8108 The MAI 3000 User Guide, Diagnostics Manual, and Service Manual is specific to the MAI 3000 product. The BOSS/IX 7.2 User Reference Manual and Technical Manual is generic to BOSS/IX 7.2. 11.0 LOWEST ACCEPTABLE REVISION LEVELS (LARL) The following chart lists the LARL of each PCB on the MAI 3000 system. Before installing your system ensure that the boards being used at least at these revision levels. PCB PART NUMBER LARL ------------------------------------------------ 903593 Central Mother Board(CMB) A SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg046 903533 1 MB Memory A 903577 8 Way Controller A 903390 4 Way Controller P 903406 1/4 Inch Tape Controller Y 903528 1/2 Inch Tape Controller A 400591 1/2 Inch Formatter A 907897 Power Supply A 903496 5 1/4 Inch WDD Controller J 903405 LAN Controller D ORIGINATOR: MBF SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB023 Pg047 FIB 00024 05/04/87 *** 7.2B Software Announcement *** Level 7.2B of BOSS/IX is now available. This Software Announcement contains general information about the level 7.2B BOSS/IX operating system. 7.2B contains several enhancements and corrections and is the recommended operating system level for the MAI 2000 system. TABLE OF CONTENTS 1.0 Introduction 2.0 Installation and Upgrade Procedures 3.0 Corrections to 7.2B 4.0 Enhancements contained in 7.2B 5.0 For Your Information 6.0 Lowest Acceptable Revision Levels (LARL) Level 7.2B of BOSS/IX is now available. 7.2B contains enhancements and corrections and is the recommended operating system level for the MAI 2000 system. 2.0 Installation and Upgrade Procedures The installation and upgrade procedures for the 7.2B software release are the same as mentioned in the 7.2A Software Announcement, #126. Refer to the 7.2A Software Announcement for instructions if necessary. See section 5.0, "For Your Information", for warnings on upgrading. 3.0 Corrections to 7.2B o EOS - Correction was made to the printer driver for the Whisper Printer with Basic Four protocol which caused a printer delay if the line was 120 characters or longer. - Fixed the 'requested name logic matching' problem on the 1/2" tape restore which caused the wrong file to be restored. For details see Field Bulletin #215. - Fixed the msave/mcssave continuation tape problem which failed to save a direct file that spanned two tapes resulting in an error -71, bad key. - Fixed the decryption problem in the configuration file installation process which caused failures of certain files during the install. - Fixed the Basic EXTRACT problem which was not locking the record therefore not preventing others from WRITEing the same record. o EBA - Corrected BASS disk test problem which caused an error 12. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB024 Pg001 - Corrected BASS test 6 which caused an error 28. - Corrected the TAB character problem in BASS which caused the text to display at top left corner of the screen each time a TAB character was used. - Corrected BASS printer test problems. The printer names were changed to match those used by the configure utility. Also, tests of unsupported mnemonics were removed. o EBS - Corrected the problem which caused BASIC to suspend if NUM and/or CPL was passed a string greater than 256 characters. - Corrected the problem which caused the process to suspend if an EXECUTE was used to RUN a program. o EUT - Fixed the restore problem which deleted the existing file on disk when the user specified that the utility should skip the restore if the file already existed on disk. 4.0 Enhancements contained in 7.2B o EUT - The Configuration utility has been modified to support a 4th 4-way. Up to 18 ports can be configured. o EBA - The BASS port test now supports 18 ports. - Now tests the EVDT terminals. o EIT - ATP and BQR have been modified to allow Intersystem Transfer with the MAI 1500. 5.0 For Your Information The following is a list of known problems with the 7.2B software release and a work-around, if one exists: EOS - Operating System o The command 'p p' will cause the user to operate under 'p'. It will not give an error message (because of missing arguments) and corrupts ttymodes. Work-around: None. Hit CTRL-C and reset ttymodes to default. o System crashes when using possitioning to print after the transparency mnemonic "EO". Work-around: Do not print anything on the line after the transparent output mnemonic 'EO'. EUT - Utilities o The 'dsave' will abort when a multiple diskette save is performed and one of the continuation diskettes is damaged. It should take the diskette and continue on. Work-around: None. You will have to restart the save operation. o The 'mrestore' reports that 0 blocks were restored for each sort file. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB024 Pg002 Work-around: Use command 'ls -l' to list. o The 'msave' suspends with a memory management error when the system has 3/4 MB memory and the minimum system configuration is configured. Work-around: A minimum of 1 MB of memory is required to perform the 'msave' utility. o The 'mrestore', 'mcompare' and 'msave' with the verify on will report key files as deleted in the verify report. Work-around: None o The 'msave' and 'mcompare' will display a list of files saved to tape. In this list it will display the file type for SORT as a DIRECT. Work-around: None o The 'frepair' with analyzer/repair on, will display debugging statement 'V2 Spawn Basic' when working on a basic program. Work-around: None. Ignored the message. o In the following basic statement, "PRINT STR(I)", using bsearch to replace the I's with J's, neither of the I's will be replaced because when the I in PRINT is replaced with J it causes a Syntax error and will go on to the next statement without replacing the I in STR(I). Work-around: Choose literals only on option #4 "SCOPE". o The 'brenumber', 'bcompare' and 'bxref' will give the same output to a file and a printer. The file will contain all the mnemonics and is difficult to read and understand. Work-around: Do not use a file as the report device. o CTRL-C or ESCAPE should not be used to stop the 'bencrypt' utility when several files have been selected. The 'bencrypt' will stop/start encrypting the next file, briefly go to an ADMIN prompt, continue encrypting the files selected, then, log you off. Work-around: None o The 'bencrypt' will fail if the entire path name of a file exceeds 40 characters. This includes the ".bak" which is added to the file name if the create backup option is on. An error 12 will be generated if the file name exceeds 40 characters. An error 10 will be generated when the length exceeds 40 characters after the ".bak" suffix is added. Work-around: Use the 'ENCRYPT' directive in basic. EBS - BASIC o In BASIC "PRINT NUM(A$)" where A$ is greater than 256 characters, a numeric value of 0 will print on the screen. The system should generate an error 40. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB024 Pg003 Work-around: None o The CPL function does not use the FNx function correctly. It will return a variable name instead of a function label. This will cause an endless loop when the grow table is being updated. Work-around: After the CPL function returns the variable, replace that variable with a known function (FNx) in the table, then re-compile (CPL). This will require that the function label be added to the tables. ITP - INTERSYSTEM TRANSPORT PACKAGE o This version of ITP cannot be used with other systems when using the Asynchronous Transport Package, unless the 'newer' version of ATP is installed on the other systems. Changes to the transporter protocol for enhancement and performance make this version incompatible with the previous version. This ATP also supports the ability to transport intersystem data to the 1500 system in addition to continued support of the 13XX and MPx series systems. o ATP is the only transporter supporting 1500's. Do not transport serial files to the 1500, they are not supported. Indexed files transported to the 1500 can end up with more records allocated because of the method the 1500 uses to allocate files. It is not necessary to serialize program files to or from the 1500. ATP automatically converts and translates program files. o The other software releases which are compatible with 7.2B ITP are 8.5D/8.4E for the MPx, 4.5B with the new ITP for the 13xx, and 6.2A with ITP for the MAI 1500. The older ATP on previous software releases is not compatible with ITP. FTF - FILE TRANSFER FACILITY o Refer to the 7.2A Software Announcement, #126, section 5.2.6 on page 44. ENT - MAGNET o Refer to the 7.2A Software Announcement, #126, section 5.2.7 on page 45. EBC - 27XX/37XX BATCH EMULATION o Refer to the 7.2A Software Announcement, #126, section 5.2.8 on page 56. 6.0 Lowest Acceptable Revision Levels (LARL) Refer to 7.2A Software Announcement #126. ORIGINATOR: MBF SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB024 Pg004 FIB 00025 05/04/87 *** COBAL 7.1B for MAI 2000 Series *** COBOL is now available for the 2000 system. COBOL consists of two packages, the COBOL compiler (CBD) and the COBOL runtime system (CBR). These are each purchased separately and each requires a public key to execute. The packages contain one program each: CBD - /bin/cobol - COBOL compiler. CBR - /bin/runcobol - runtime COBOL. The compiler is installed on systems developing COBOL application programs. The runtime package is installed on systems that have applications written in COBOL and have already been compiled. REQUIREMENTS The CBD package requires 140 blocks and the CBR package requires 248 blocks of disk space on the root partition. Both the COBOL compiler and the runtime package can be executed in single or multi-user mode. COBOL can be executed on a system with the minimum memory configuration of 768 KB. Product dependencies: EOS. INSTALLATION Before installing COBOL, the system must be "rooted" to the root partition. If both packages are going to be installed, the order of installation is unimportant. The installation and upgrade procedures are identical and use the '/bin/install' and '/bin/install key' programs. At the system administrator prompt ( ADMIN> ) enter: install cs CBD (for mcs installation) or install fd0 CBD (for floppy installation). After all the files have been copied to disk, the installation procedure prompts for the public key. Current Public Key: 12345678 Input 8-Character public key (cr=no change) Enter the public key, contained in the CBD key certificate, followed by a carriage return, the program then prompts for the key a second time. If the key is entered the same way twice, the key is written to '/etc/level/CBD' file installed and the package can now be executed. If a mistake is made and the keys do not match, the key must be entered in again. The COBOL runtime package (CBR) is installed by repeating the above process and substituting "CBR" in place of "CBD". START-UP The ved text editor is used to create COBOL source programs. Source programs must have the extension ".cbl". When a source program is compiled SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB025 Pg001 using the '/bin/cobol' program, the runtime code is placed in a file with the extension ".o", unless the object file is specified otherwise. A compiled COBOL program is executed using the '/bin/runcobol' program. Information about the options for the COBOL complier and runtime package is available in "MAI 2000 COBOL USER & REFERENCE GUIDE", BFISD 6356. DIFFERENCE 8000/2000 COBOL The cobol packages on the 2000 system are written in 'C' language, unlike the 8000 which is written in PASCAL. In addition, COBOL on the 2000 conforms to the system standard of 7-bit ASCII (low-order). The 8000 system uses 8-bit ASCII (high-order). Program and data file names must conform to the rules that apply on the 2000. File names cannot exceed 20 characters in length and caution must be used when using special characters. The character "/" is reserved as a separator for filepath names. The characters "*" and "?" are used on the 2000 as wild card operators. The 8000 system has a COBOL mode from which, COBOL programs are compiled. After compiling a COBOL source program, the object code is executed in command mode. On the 2000 system COBOL programs are compiled and executed in command mode. The 2000 COBOL compiler treats the DATE-COMPILED statement in the IDENTIFICATION DIVISION and the FILE CONTAINS integer RECORDS in the FD entry as comments. RESERVED WORD DIFFERENCES The following words are reserved in 2000 COBOL but not in 8000 COBOL. BACKGROUND CONVERT LOW SWITCH-N BEEP ECHO PARAMETERS TAB CLEAR FOREGROUND PRINT USER-LABEL COMP-1 HIGH PROMPT COMPUTATIONAL-1 INSERT REVERSE The following words are reserved in 8000 COBOL but not in 2000 COBOL. AUTO FULL SPOOL-COPIES TAPE-VOLUME-ID BELL ID SPOOL-JOB-NAME UPDATE COL PRINTER SPOOL-PRIORITY WAIT CONSOLE REQUIRED SWn CTP SPOOL-CLASS TAPE-FILE-ID WARNINGS COBOL handles indexed and direct files differently than BASIC. If the file is accessed by both BASIC and COBOL programs, the manner in which records are processed may have to be changed. When writing to a direct file, COBOL does not append the key to the end of the data record. BASIC appends to the end of the data record. COBOL adds an additional two bytes to the beginning of every indexed filed record to store the length of the record. BASIC does not store the length of each record in the data file. COBOL programs can be run in background mode, but the terminal will still be used by the COBOL program. Because of this reason the advantage of running programs in background mode is eliminated. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB025 Pg002 The input/output redirection (e.g. runcobol pgm.o > log) does not work. ORIGINATOR: MBF SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB025 Pg003 FIB 00026 05/20/87 *** Rel 7.2C - EIT7217 has the wrong level file *** The /etc/level/EIT file for the 3000 7.2C version of the EIT7212 product has the wrong level. It has the 7.2B EIT7211 level file. This will be corrected in 7.2D and future releases. The /etc/level/EIT file does not affect the functionality of the product, eventhough the 7.2B and 7.2C versions are NOT interchangeable. The files sizes are different between the 7.2B EIT7211 and the 7.2C EIT7212. To insure that you have the correct version, after you have installed EIT, use the ls command to check the size of the cread and cwrite files. Example: ls -l /util/cread 2000 7.2B 3000 7.2C ----------- ----------- cread 113634 113748 cwrite 106344 106454 ORIGINATOR: P. Thatcher SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB026 Pg001 FIB 00027 05/20/87 *** 2000/3000 Crash/Dump recovery and file repair instructions *** This Field Bulletin details the steps to follow after a system crash/dump, it provides the steps to determine the names for 'lost' files and the steps to verify data files. After a system has crashed or has a forced dumped the following are the recommended steps to follow: o If T0 displays a system crash code, check this number against the listing of crash codes in 4116 FIB group, FIB #4. Follow the recommended work around for the crash code that was displayed. o Copy the dump to tape or floppy media. For information on saving a dump to tape or floppy see the Software Announcement for the release the system is presently on. For the information on sending a dump to Basic Four, see BOSS/IX FIB group, FIB #18. NOTE: With the 7.3 release of the Operating System a new command is added that will allow the viewing of the last 8 errors that occured on the system. This can be done on another system or on the systems that crashed after the repair is complete. This data should be reviewed to help determine the cause of the system crash/dump. See the 7.3 Software Announcement or the 7.3 Technical Reference guide for more information on the command. o After rebooting, the system will prompt for automatic filesystem repair. Answer the prompts for this process to complete. This procedure will check and repair all filesystems that were mounted at the time the system crashed/dumped. It does not check or repair individual files. o After the filesystem check/repair is complete and any corrective steps outlined in BOSS/IX FIB group, FIB #18 are taken, do a standard boot of the system. o From the root partition 'ADMIN>' use the command 'ls /lost* -l' to determine if there are any 'lost' files. These are files that during the filesystem check/repair the system was unable to determine where they should belong in the filesystem. Page 2 of Field Bulletin #334 The 'ls lost* -l' command will display on the left side the file type and on the right side the file name in the form 'lost_number' (where number is the inode number of the file). From this list of 'lost' files try to determine their proper name and then rename the files. Listed below are the file types and the way to rename the file. DIR: This is a directory. Use the 'ls' command to look at the contents of the directory. To rename use the 'move' command. Bas: This is a BASIC program. Go into BASIC, load and list the program. Use the BASIC directive 'RENAME' to rename. Ind,Key,Ser: These are BASIC files. Go into BASIC, OPEN the file and read the file. Use the BASIC directive 'RENAME' to SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB027 Pg001 rename. A blank: This is a string file. Use the 'p' command to look at the file. To rename use the 'move' command. EC: Is an event count. This was left over from the previous session and can be deleted. If you are unable to determine the name of a file, back it up and then delete it from the disk. This will save disk space and avoid confusion. If you find that a file is missing, the backup will allow you to restore the data and look for the file. o For Operating Systems Level 7.2 and above, run the 'frepair' utility. This utility is found in the 'ut.file' utility set. Create a filelist of all data files on the system. Then run the utility against this filelist, doing the analyze only. Output to a file or printer to save having to enter a between each file. Repair any files that are reported bad. After these steps are complete the system should be ready for use. If after these steps the system is still having problems contact your next level of support for assistance. ORIGINATOR: W. Moore SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB027 Pg002 FIB 00028 06/05/87 *** Filelists get corrupted on O.S. Releases 7.2 *** Problem: An existing filelist will become corrupt if it is modified without first being displayed. The problem exists in all levels of 7.2 O.S. but has been corrected in 7.3A. Workaround: After choosing the modify option and entering the filelist name, choose the display option. After the filelist is displayed, the add option can be used to add filenames and/or filelist name to the existing filelist without filelist corruption. ORIGINATOR: D. Wenzel SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB028 Pg001 FIB 00029 06/05/87 *** Release 7.2D is the available/recommended for the 3000 *** Level 7.2D of BOSS/IX is now available for the MAI 3000. It is the recommended Operating System level for the MAI 3000. It contains enhancements and is required for use with the MT-4406 MCS tape drive on the MAI 3000. It also contains corrections for the following problems: o EBC (27xx/37xx) and X25 (FTF/MAGNET WAN) - Logon/logoff a terminal causes the communication session to abort. - Running the command 'ls /dev -l' causes the session to abort. - Running the 'freespace' utility causes the session to abort. - An active communication session prevents access to the parallel printer. o B32 (Bisync 3270) - Logon/logoff a terminal causes the communication session to abort. - Running the command 'ls /dev -l' causes the session to abort. - Running the 'freespace' utility causes the session to abort. - An active communication session prevents access to the parallel printer. - The software does not support any multi-drop link to the host. ORIGINATOR: W. Moore SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB029 Pg001 FIB 00030 07/07/87 *** Vconf setup parameters for communications software usage *** When implementing any data communications software package, such as Batch Communications, MAGNET or FTF on the 2000/3000 systems, the O/S parameters in the vconf file (i.e., Well Known Sockets, Dynamic LAN Sockets and LAN buffers) must be correctly configured for the memory installed in that system. For the 2000 system refer to the 7.2A Software Announcement, page 49. The configuration is valid for the 7.2B O/S release as well. For the 3000 system, incorporate the communication package into the general operating system with the following configuration procedures. 1. Establish the base memory requirements for the user, based on the number of concurrent tasks required. 2. Add 1MB of memory to the base system to support any of the communication packages. 3. Modify the "vconf" parameters to suit the customer's communications environment. BASE MEMORY REQUIREMENTS ignore any communication requirements. The system is sized to accommodate the number of tasks and peripherals required to establish the minimum amount of memory required for acceptable performance. Modify the system "vconf" parameters to reflect the base configuration. This is a normal procedure for system installation. ADD 1MB OF MEMORY to the base memory requirements to support all of the communication requirements. Adding this memory addresses the communication requirements ONLY. The additional memory MUST NOT be allocated for expansion of added user tasks or peripherals over the base allocation performed in step 1 above. This 1MB of memory ALSO covers the TOTAL overhead required for installation of MULTIPLE communication packages in ONE system. MODIFY THE "vconf" parameters, Dynamic Sockets and LAN Buffers, according to the following table. The Well Known Sockets defaults to 5 and remains the default under all system configurations. _____________________ | DYNAMIC | LAN | | LAN | BUFFERS | | SOCKETS | | ----------------------------------- | | | | | DEFAULT | 8 | 8 | | MAXIMUM | 59 | 255 | | | | | | EACH | | | | MAGNET | 2 | 4 | | TASK | | | | | | | | EACH | | | | FTF | 1 | 1 | | TASK | | | SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB030 Pg001 | | | | | X.25 | | | | MEDIA | 1 | 2 | | | | | | 27xx | | | | 37xx | 2 | 1 | ----------------------------------- | | | | | | | BASE | 2 | 2 | | 3 |________|_________|_________| | 2 | | | | | 7 | EACH | | | | 0 | DEVICE | 2 | 2 | | | | | | ----------------------------------- Table definitions are described below. o DEFAULT "vconf" PARAMETERS The "vconf" file defaults to these values when the operating system software is installed. o MAXIMUM "vconf" PARAMETERS The maximum values must not be exceeded when configuring for communications. o EACH MAGNET TASK Every local and remote MAGNET access from/to the system must be accounted for. Add the total number of tasks accessing a remote system AND the total number of remote tasks accessing into the system. This total represents the overhead of the maximum number of simultaneous MAGNET tasks for that system. SYSTEM A SYSTEM B __________________ __________________ | | | | | LOCAL TASK 1 ------------------>>>[SYSTEM TASK] | | LOCAL TASK 2 ------------------>>>[SYSTEM TASK] | | | | | | [SYSTEM TASK]<<<------------------ LOCAL TASK 1 | | [SYSTEM TASK]<<<------------------ LOCAL TASK 2 | | | | | | LOCAL TASK 3 ----------+ ------------------ | | | ------------------ | | | SYSTEM C | __________________ | | | | | [SYSTEM TASK]<<<-------+ | | ------------------ System A contains 5 MAGNET tasks (3 local + 2 remote). System B contains 4 MAGNET tasks (2 local + 2 remote). System C contains 1 MAGNET task (0 local + 1 remote). o EACH FTF TASK SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB030 Pg002 Every local and remote FTF access to the system must be accounted for. Add the total number of tasks accessing a remote system AND the total number of remote tasks accessing into the system. This total represents the overhead of the maximum number of simultaneous FTF tasks for that system. See the example shown under EACH MAGNET TASK. o X.25 MEDIA Set the appropriate parameters if using X.25 media. o 27xx/37xx Set the appropriate parameters if using the Batch Emulator. o 3270 TERMINAL EMULATION The 3270 BASE represents the overhead required to run IBM 3270 cluster controller emulation. Each 3270 device (IBM printer and IBM terminal emulation) configured for that 3270 link requires buffer overhead to be added to the base allocation. ORIGINATOR: R. Hinojosa SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB030 Pg003 FIB 00031 12/02/87 *** Release 7.3A Software Announcement [ WPSS 153 ] *** Level 7.3A of BOSS/IX is now available. It is the recommended Operating System for MAI 2000 and MAI 3000 systems. This Software Announcement contains general information about the Level 7.3A BOSS/IX operating system. Installation and upgrade procedures are fully documented in this announcement. Also, this document has sections on enhancements and corrections to BOSS/IX, approximating memory requirements, memory usage, a list of new documents available for BOSS/IX, a list of the lowest acceptable revision levels for hardware, and a list of warnings and cautions and a way, if any, to work around them. When installing this release on a 3000 system, the system serial number MUST be reinstalled using the new 2000/3000/4000 SSN program. DO NOT attempt to upgrade a 3000 system without reinstalling the system serial number using the new 2000/300/4000 SSN program. It is recommended that you read this document before installing Level 7.3A. For information on how to order Level 7.3A refer to Marketing Announcement 563 for the United States or 368 for International. NOTE: Throughout this document the references to '7.2' include 7.2A/B/C/D/D1. Copyright 1987 MAI Basic Four, Inc. All rights reserved TABLE OF CONTENTS 1.0 Overview 2.0 Installation and Upgrade of the Operating System, Software and Diagnostics 2.1 Installing Diagnostics on the Disk 2.1.1 Introduction 2.1.2 Disk Diagnostic Installation Procedure 2.1.3 Loading Disk Diagnostics 2.2 Installation of the Operating System. 2.3 Upgrading 2.4 Product Installation/Upgrade 2.4.1 EDS - Operating System 2.4.2 ECC "C" Compiler 2.4.3 MAGNET (ENT) and File Transfer Facility (FTF) 2.4.4 27xx/37xx Batch Emulation 2.4.5 Asynchronous Transport Package (ATP) SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg001 2.4.6 3270 Bisynchronous 2.5 Security Configuration Record 2.5.1 7.3A Configuration Record Request Sheet 3.0 Level 7.3A BOSS/IX Enhancements/ Corrections 3.1 Operating System (EOS) 3.1.1 Shared Libraries 3.1.2 Improved 1/2 inch Tape Support 3.1.3 Merged Tape Commands and Utilities 3.1.4 Console Configuration 3.1.5 vconf Configuration File 3.1.6 System Security Configuration Record Format Change 3.1.7 System Dump Changes 3.1.8 Reduced Memory Requirements 3.1.9 Reduced Disk Requirements 3.1.10 New System Error Logger 3.1.11 File Integrity Checking 3.1.12 Configurable Number of Ghost Tasks 3.1.13 Improved BOSS/IX Swapping Performance 3.2 System Utilities/EVT 3.2.1 frepair Utility 3.2.2 Configure Utility 3.2.2.1 Configure the System Console 3.2.2.2 New Terminal Types 3.2.2.3 Configuring Printers 3.2.3 pparams Utility 3.3 Basic (EBS) 3.3.1 Business BASIC 86 3.3.2 BASIC on 7.3 is not backward compatible with 7.2 3.3.3 Changed Functionality 3.3.4 BOSS/VS & BOSS/IX Compatibility Notes 3.3.5 Unsupported Mnemonic on PT-4220 SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg002 4.0 New Products in Level 7.3A 4.1 Universal Printer Driver (UPD) 4.2 PDF (Printer Definition File) 5.0 For Your Information 5.1 Operating System (EOS) 5.2 BASIC (EBS) 5.3 FTF via LAN and X.25 5.4 MAGNET via LAN and X.25 5.5 Intersystem Transport Package (EIT) 5.6 3270 Bisync 5.7 Graphics 6.0 Memory Requirements and Operating Parameters 6.1 Approximating A System's Memory Requirement 6.2 Recommended Values for "vconf" 6.2.1 Recommended Values for "vconf" BOSS/IX Model 2000 Parameters 6.2.2 Recommended Values for "vconf" BOSS/IX Model 3000 Parameters 7.0 Memory Usage 7.1 Calculating A System's Memory Requirements 7.1.1 Model 2000 7.1.1.1 Example of How to Calculate a System's Memory Requirement 7.1.2 Model 3000 7.1.2.1 Second Example of How to Calculate a System's Memory Requirement for Model 3000 7.2 Calculating BOSS/IX Table Space and Dynamic Work Space 7.2.1 Model 2000 7.2.2 Model 3000 8.0 New & Updated Manuals for Level 7.3A 9.0 Lowest Acceptable Revision Levels (LARL) 1.0 Overview SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg003 The level 7.3A Release contains the following enhancements/features: o Shared libraries o Improved 1/2 inch tape support o Merged tape commands and utilities o UPD (Universal Printer Driver) o Changes to console configuration o Changes to vconf file o Changes to system configuration record format o Changes to system dump procedure o Diagnostic Partition o Reduced disk requirements o Reduced memory requirements o New system error logger. o File integrity checking o Bad block retirement o BB86 --- Business BASIC 86 - Multi-key files - Terminal driver enhancements - 4 char BFS device names o Improved BOSS/IX swapping performance o New printers support o New terminals support o Customer configurable number of form feeds before each spooled print job o Enhancements to MAGNET o Enhancements to 2780/3780 o Configurable number of Ghost tasks 2.0 INSTALLATION AND UPGRADE OF THE OPERATING SYSTEM, SOFTWARE AND DIAGNOSTICS The following are the steps to install or upgrade the Operating System, customer's software and system diagnostics. Before installing or upgrading the system it is recommended that you read these instructions completely. NOTE: To do an ALTERNATE LOAD: On a 2000 system, enter ^C at the reboot prompt. On a 3000 system, enter 2 at the bootstrap menu. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg004 2.1 Installing Diagnostics on the Disk 2.1.1 Introduction Diagnostic programs for your system may be contained on the system fixed disk. Your disk should have diagnostics installed in order to test the tape subsystem included with your system. The purpose of these tape diagnostics is to troubleshoot and test your tape subsystem, when you cannot load diagnostics from the tape subsystem. You may optionally install all of the diagnostics programs on your disk. The system diagnostics are contained on a dedicated diagnostic partition. This diagnostic partition is inaccessible to user programs, and is actually beyond the reach of the user disk area. For this reason, the diagnostic programs cannot be accessed by the file system, yet they are maintained by a Diagnostic Executive. If your system will not boot diagnostics from disk, and the O.S. is already installed, the file system must first be backed up. Once backed up, a diagnostic partition can be reserved. Once the diagnostic partition is reserved, diagnostics can be installed from the same bootable diagnostic tape. Afterwards the file system must be restored. Use the following procedure to install the diagnostics on your fixed disk. 2.1.2 Disk diagnostic installation procedure Step 1: Backup your disk If your file system is already installed on the disk you must do a complete file by file backup. If your file system has not been installed yet, install your diagnostics first and then install the file system. Step 2: Boot diagnostics from tape Install the diagnostic tape. Do an alternate load. For the boot device enter "cs", for MCS or 'ts', for MTS. For the system file enter . Step 3: Enable service mode When the EXEC is loaded, it will auto-size the system and display the program prompt: Any Exec commands can be entered at this time. To begin the installation of diagnostics, you must first enable the service commands. At the Exec prompt, enter: service and a RETURN. This will allow use of the service commands. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg005 Exec will then ask for the service password, enter: b4bus and a RETURN after which, the prompt will again be displayed. Step 4: Update the superblock on the disk. The superblock on the disk must be updated to reserve a section of the disk for the diagnostics. Enter the superblock initialization command: sbinit and a RETURN to initialize the superblock for the diagnostic partition. EXEC will ask you if you want to destroy the existing disk partition information and the disk directory name. Any (y/n) responses are single character responses, and do NOT require a . Entry of the "sbinit" command will cause EXEC to ask: Destroy: "volume ID" (y/n)? where "volume ID" is the current volume ID contained in the superblock. A "y" response will allow you to initialize the superblock for the diagnostic partition. A "n", no response will return you to the prompt. Enter: y and EXEC will ask for the number of sectors to reserve on the disk for the diagnostics: Diagnostic Partition size (in sectors)? Enter the number of sectors desired as follows: a) To install all available diagnostics, enter: 1200 b) To install tape diagnostics, enter: 200 EXEC will then ask about the directory: Destroy: "partition name" (y/n)? Enter the character "y" to destroy the current disk directory to have it initialized for a subsequent install, or "n" to retain the current partition name. If you wish to change the name of the disk diagnostic partition, enter: y SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg006 and EXEC will then ask: Disk name: Enter the new disk name, up to 12 characters in length, and . This new name will be displayed every time you display the directory. EXEC will then display: Initializing: "disk name" where "disk name" is the new name you just entered. The diagnostic partition is now defined. Step 5. Copy diagnostics from tape to disk Once the diagnostic partition is defined, diagnostics can be installed on the disk. You now can determine which files to install on the disk by listing the contents of the tape. This is optional if you are going to install all of the diagnostics. To obtain a list of file names on the tape, enter: ltape To install the diagnostics on the fixed disk, enter: install and a RETURN to install ALL of the diagnostics. To install a particular diagnostic enter: install "file" and a RETURN where "file" is the file name to install on the disk. Use the list of files obtained by the "ltape" command to determine which files you want to install. The file EXEC, SIT, MCS and/or MTS are the minimum diagnostic files to install. When you enter the "install" command, to install all of the diagnostics, EXEC will prompt: Destroy: "disk name" (y/n)? where "disk name" is the name of the disk entered during the "sbinit" command sequence. Entry of the character "n" will cause the current directory name to remain and the install process to begin. Entry of a "y" character will cause EXEC to ask you for the new disk name as in the "sbinit" command. Maintain the current directory from the "sbinit" sequence, enter: n and the install procedure will begin. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg007 As the diagnostics are installed on the disk, EXEC will display the current program being copied from the tape, and the size in sectors. After the sector size display, the file is written to the disk and the directory updated. When all the files are installed, EXEC will again display the prompt: Step 6: After the diagnostics are installed on the disk, you may want to list the diagnostics on the disk enter: ldisk and to obtain the list of the diagnostic files on disk. You should test the bootstrap capability now, to see that you can boot diagnostics from the disk. Enter: shut and to obtain the bootstrap menu. Step 7a: 3000 only Do an alternate load, for the boot device enter: wd0, for system file enter: diag Step 7b: 2000 only The EOS product must be installed to boot to the diagnostic partition on the 2000 system. The file /sys/diag exists on the EOS product. this file is required to boot to the diagnostic partition. After you have installed the EOS product: Do an alternate load, for the boot device enter: wd0, for the system file enter: /sys/diag. NOTE: Installing diagnostics on the disk has taken disk space away from the user available disk space, the device capacity is reduced to provide room for the diagnostics. 2.1.3 Loading Disk Diagnostics When the system is first powered up, or after the system is shutdown, the user must perform an alternate load sequence in order to load diagnostics from disk. The system has the logic to either bootstrap the Operating System or the Diagnostic Executive. The loader programs for each are in different sections of the disk. The diagnostic loader and the associated directory of files for the diagnostics are contained in the diagnostic partition. Thus the diagnostic partition is completely self contained, and separate from the Operating System. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg008 The operation of loading diagnostics from the fixed disk and from the MCS/MTS tape are similar. The only difference is in the alternate load sequence, as discussed in the following sections. The diagnostics contained on your fixed disk cannot be run while the Operating System is up and running. The diagnostic programs are all off-line programs and require you to first shutdown your system, regardless if you load from MCS/MTS tape or from the fixed disk. After running diagnostics, entry of the diagnostic "shutdown" command will allow you to reload the Operating System. The normal indication that diagnostics are not on the disk, is the error message "invalid loader detected" when a diagnostic boot is attempted. To access the diagnostics, once they are installed perform an alternate load. For boot device enter 'wd0', for system file enter 'diag' for the 3000 system or '/sys/diag' for the 2000 system. This will get the '' prompt. Any file name listed by the 'ldisk' command can now be loaded by entry of the command: load file and , where "file" is any file listed. 2.2 Installation of the Operating System The following steps outline the 7.3 BOSS/IX installation procedures for tape and floppy diskette. The installation" procedure is to be used when installing a new system, installing the OS after a diagnostic partition has been installed, or when upgrading a 7.1 system to a 7.3A system. NOTE: The 'packaging' of the products has changed. A 'base' tape will no longer be distributed. Instead, you will receive a 'customer' tape. These products are on the 'customer' tape: EOS EUT EBS EBA EXT EDB IDB TBC EIT ENT FTF INT GKS GRF CBR CBD UPD PDF B32 X25 EB2 With this new packaging it is no longer necessary to ship a tape for each product ordered. Instead, a Lock & Key certificate is generated and mailed for each product purchased. WARNING: When installing this release on a 3000 system, the system serial number MUST be reinstalled using the new 2000/3000/4000 SSN program. DO NOT attempt to upgrade a 3000 system without reinstalling the system serial number using the new 2000/3000/4000 SSN program. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg009 Step 1: Using the mcssave/mtssave command or the floppy diskette save utility, do a file by file back up of all user programs and data files. Using the configure utility, print out the port configurations; using the oprinfo utility, print out the operator information report. These will need to be re-entered after the install is complete. Step 2: First step is to install the boot partition. Place the customer tape into the tape drive. Or, if you are doing floppy installation insert the installation floppy into drive fd0. Do an alternate load. At the 'boot device:' prompt type "cs" for MCS, "ts" for MTS or "fd0" for floppy diskette, then press . Press again at 'System file:' prompt. NOTE: MTS requires a 4.2 boot prom on the MAI 2000. Step 3: Screen displays loading messages, then the Install Utility Menu. Select Option 'A', then . Option 'A' re-defines all the wd0 partitions and copies a new boot partition to disk. Special note for floppy diskette installations, make sure your BOOT floppy diskettes are inserted in the correct sequence according to the BOOT number. After one floppy diskette is complete make sure you change floppy diskettes before responding to the prompt on the screen. Step 4: After the boot partition is installed the configuration record must be installed. When the message 'OPTION>' is re-displayed put the configure record tape or floppy in the tape drive or floppy drive. Use option 'D' to install the configuration record. After the configuration record is installed enter ' ^D' and then 'shutdown'. WARNING: If the 7.3 configuration record for the system is not installed you will be able to access the boot partition only. NOTE: After shutdown and re-boot to the boot partition it is recommended that the configuration record be copied to the boot partition. To do this execute the following with the configuration tape in the tape drive: 'trestore dev= -v name=CONFIG' where dev=cs for mcs and dev=ts for mts. For floppies: SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg010 'mount /dev/fd0 /mnt' 'copy /mnt/cofig.* /sys' 'unmount /mnt' Step 5: After the configuration record, the EOS product must be installed. Reloading the system at this time automatically reloads and roots to the boot partition. Enter the correct date; the screen will then display the 'ADMIN>' prompt, type "osinstall cs" for MCS tape, "osinstall ts" for MTS tape and "osinstall fd0" for floppy diskette. This process uses the parameters in the Super Block to define the root filesystem, then copies the EOS product to the root partition on disk. After the EOS product is installed you are instructed to reload again. Step 6: Reloading of the system at this time automatically reloads and roots to the root partition. Enter either the current date, or a , if the date is correct. At the 'ADMIN>' prompt, type "install cs EUT EBS", for MCS tape, "install ts EUT EBS" for MTS tape or "install fd0 EUT", for floppy diskette. NOTE: When working with tapes all products listed on the customer tape can be installed with one command line. When working with floppies you must install one product at a time in the following order: EUT, EBS, EXT, EBA then optional products in any order. Products that are chargeable and not part of the base system will have key codes that you must enter during or after (using '/bin/install key') installation before you can use that product. If the key certificate did not come with the media, contact the customer or service representative in your area for instruction about how to obtain this key code. Step 7: The '/etc/conf' file on the boot partition needs to be customized to meet your needs. (See Section 7.0 'Memory Usage' for instruction on how to customize the '/etc/conf' file.) Step 8: After you have copied all your products to disk and have customized the '/etc/conf' file, your system is ready for use. Step 9: If you have user program and/or data files to be restored, use the 'dups=skip' option of the trestore command or the 'skip' option in the 'duplicates' parameter of the trestore or drestore utility to avoid writing "old" files over your new 7.3A files. If you are restoring 7.1 Basic programs, use SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg011 the csave command to convert them to 7.3A Basic. 2.3 Upgrading The following steps describe the 7.3 BOSS/IX upgrade procedures for tape and floppy diskette. NOTE: This upgrade procedure is for 7.2 only. If you are upgrading a 7.1 OS level system refer to section 2.2 "INSTALLATION OF THE OPERATING SYSTEM". "Upgrade" from 7.1 to 7.3A is not supported this requires an "install" of 7.3A. WARNING: When installing this release on a 3000 system, the system serial number MUST be reinstalled using the new 2000/3000/4000 SSN program. DO NOT attempt to upgrade a 3000 system without reinstalling the system serial number using the new 2000/3000/4000 SSN program. Step 1: Using the mcssave/mtssave command or the floppy diskette save utility, do a file by file back up of all user program and data files. Using the configure utility, print out the port configurations; and, using the oprinfo utility, to print out the operator information report. Step 2: When upgrading from 7.2 to 7.3A you are required to boot off the install media and choose option B to install the boot partition. This means that a default /etc/conf file will be installed on the boot partition. To preserve your config- uration parameters so you don't have to re-assign them with the vconf command after the update is complete copy the /etc/conf file from the boot partition to the root partition: >mount /dev/boot /mnt >copy /mnt/etc/conf /etc -v >unmount /mnt NOTE: This step is optional. If you do not copy etc/conf to the root partition you will have to re-enter the parameters. Be aware that some of the vconf parameters have changed and will need to be re-entered. Refer to table 6C for the 2000 and 6D for the 3000 recommended parameter values. Step 3: Install the boot partition. Insert the customer tape into the tape drive. Or, if you are doing floppy installation insert the installation floppy into drive fd0. Do an alternate load. At the 'boot device:' prompt type "cs" for MCS, "ts" for MTS or "fd0" for floppy diskette, then press . Press again at 'System file:' SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg012 prompt. NOTE: MTS requires a 4.2 boot prom on the MAI 2000. Step 4: Screen displays loading messages, then the Install Utility Menu. Select Option 'B', then . Option 'B' will only copy an image on the boot partition from the tape or floppy to disk. This process will ensure that your system has all the up-to-date and proper MACROs and system files on the boot partition. Special note for floppy diskette installations, make sure your BOOT floppy diskettes are inserted in the correct sequence according to the BOOT number. After one floppy diskette is complete make sure you change floppy diskettes before responding to the prompt on the screen. Step 5: After the boot partition is installed the configuration record must be installed. When the message 'OPTION>' is re-displayed put the configure record tape or floppy in the tape drive or floppy drive. Use option 'D' to install the configuration record. After the configuration record is installed enter '^D' and then 'shutdown'. WARNING: If the 7.3 configuration record for the system is not installed you will be able to access the boot partition only. Step 6: Do an alternate load. At 'Boot device:' prompt, ''. At the 'System File:' prompt, enter ",/etc/boot.conf". Step 7: The above alternate load will re-load and root the operating system to the boot partition. Enter the correct date or '' if the date is correct. Insert the base system tape containing EOS, EUT, EBS or the floppy diskette EOS #1. At the 'ADMIN>' prompt type "osupdate cs" for MCS tape, "osupdate ts" for MTS tape or "osupdate fd0" for floppy diskette. For floppy diskette upgrades the screen will prompt you when to insert the next diskettes. Step 8: After the procedure is complete you have the option of restoring the default system configuration files to the upgraded root then to the boot partition. This is done by typing "/sys/installetc". This procedure allows the operator to select which system files he/she needs to restore. Please note if this is done all system files that are restored will be new and will have to be re-updated to reflect the needed system information. Example: If '/etc/passwd' is re-installed the operators will SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg013 have to be redefined. Following, find a list of the files that can be installed using 'etc/installetc' and the means to modify the files for your system: etc/class, /etc/defaults, /etc/forms: These files are used when printing and can be customized by going to the 'ut.printer' menu and using option 5 'Printer parameters' or using the program 'pparams'. /etc/conf: This file contains your system configuration parameters and is changed by using the '/bin/vconf' command. /etc/exem, /etc/logm, /etc/motd: These files print to the screen at the time of log in and can be modified by the use of the '/bin/ved' command. /etc/passwd: This file contains your operator information and is updated by going to the 'ut.system' menu and using Option 3, (Operator information) or by using the program 'oprinfo'. /etc/ports, /etc/printers, /etc/terminals: These files contain the terminal and printer configuration parameters and are updated by going to the 'ut.system' menu and using Option 1, (Port configuration) or by using the program 'configure'. /etc/sinit, /etc/startup: These files are used at system load time and can be modified by the use of the '/bin/ved' command. /etc/shtdwn: This file is used when the system is being shutdown and can be modified by the use of the '/bin/ved' command. Step 9: If you skipped step 2, then skip this step also. Otherwise, mount the root partition and copy the /etc/conf file back down to the boot. Then run the vconf command on it to convert it to 7.3A format. >mount /dev/root /mnt >copy /mnt/etc/conf /etc -v >vconf -save /etc/conf >unmount /mnt NOTE: This must be done prior to rebooting the system. Now when you reboot your customized /etc/conf file will be used. Beware that some of the vconf parameters have changed and will need to be re-entered. Refer to table 6C for the 2000 SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg014 and table 6D for the 3000 recommended parameter values. Step 10: Next shutdown the system and do a normal reload root partition. Enter the correct date or press '' if the date is correct. If you are upgrading from MCS, at the 'ADMIN>' prompt type "install cs EUT EBS", press ''. If you are upgrading from MTS, at the 'ADMIN>' prompt type "install ts EUT EBS", press ''. The system will automatically install both EUT and EBS. If you are upgrading from floppy diskette, insert the first floppy of the EUT set. At the 'ADMIN>' prompt type "install fd0 EUT". Once EUT is complete use the same routine to install EBS and any other products. NOTE: When working with tapes all products listed on the customer tape can be installed with one command line. Products that are chargeable and not part of the base system will have key codes that you must enter during or after (using '/bin/install key') installation before you can use that product. If the key certificate did not come with the media, contact the customer or service representative in your area to instruct you in where to call for this key code. Step 11: There have been some changes in some of the system files between 7.1, 7.2 and 7.3. For this reason you are required to make some configuration changes to the system. These configuration changes are identified in the following section on a product basis. If you are not installing a particular product you need not worry about the configuration changes for that product. If you are installing a product then you must following the section that covers that product. Once the upgrade has been performed, be especially careful when restoring files back down from a 7.2 tape. If you should accidentally restore a changed configuration file it is best to go back and install that product again from the system tape, being careful to follow the configuration change steps for that product. Step 12: If you have user program and/or data files to be restored, use the 'dups=skip' option of the trestore command or the 'skip' option of the 'duplicates' parameter of the trestore or drestore utility to avoid writing "old" files over your new 7.3A files. NOTE: Restoring customer files on an update procedure should not be required. The procedure should leave all user files intact. 2.4 Product Installation/Upgrade 2.4.1 EOS - Operating System SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg015 1. The configuration files created by "vconf" have new fields and new functionality. Only config- uration files created with a 7.3A vconf command will work on 7.3A operating system. However, the 7.3A vconf command will convert 7.2 configuration files to the 7.3A format. Steps 2 and 9 of the upgrade procedure will accomplish this. 2. The 7.3A user is responsible for configuring the type of the system console terminal after the install procedure is complete. This step cannot be done until the operating system and the utilities product, EUT, have been installed. Then the user should execute the Port Config- uration Utility "configure" and set the system console type. The system console type set by the boot PROM configurator is no longer supported by the operating system. Other system console parameters must still be set through the boot PROM configurator. 3. The format of the print control files has changed. On an osupdate, the existing files will auto- matically be converted to the new format. Backup versions of the old files should not be used or installed. The files are: /etc/forms /etc/ports /etc/printers /etc/defaults /etc/class 4. Automated backup procedures that use "/bin/mcssave", "/bin/mtssave", or related utilities must be changed to use the new tape utilities that are included in the EUT product. See section 3.1.3. 5. Partition files created with 7.2 "/bin/usb", which reside in the "/etc/diskdesc", cannot be used on 7.3A. These files can be recreated using the 7.3A "usb" command. 6. On upgrades from 7.2 to 7.3A the user MUST boot off the customer tape and select the "B" option before doing an "osupdate" from the boot partition. 7. The /etc/error.log file format has changed. Prior to going into multi user mode, use the delete command to delete this file. It will be recreated at the default size of 100 records when the system goes into multi user mode. If you want more than 100 records, use the sys/errlog command specifying the number of records and the initial option to recreate this file. NOTE: All upgrades to 7.3A will create a new boot SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg016 filesystem, thereby destroying all 7.2 files on the boot partition. 2.4.2 ECC "C" Compiler Due to changes to the header files and the new shared libraries in 7.3A all "C" programs should be recompiled on 7.3A to avoid problems executing these programs. 2.4.3 MAGNET (ENT) and File Transfer Facility (FTF) 1. To install ENT, execute the command: admin> install xx ENT To install FTF, execute the command: admin> install xx FTF Where xx is the device of the ENT or FTF media. cs = 1/4" MCS ts = 1/2" MTS fd0 = floppy drive 2. The MAGNET/FTF configuration files have changed format between 7.2 and 7.3. Existing LEGAL network configurations will be converted to the new format by a program which is automatically executed at installation of the 7.3 ENT or FTF product. Configurations which do not conform to documented restrictions (e.g., two LAN boards) may not successfully convert. Though the installation procedure allows the installer to omit calling the configuration conversion program, it is safe to run the conversion program. 3. The old configuration utility, "netutil", has been replaced entirely by the collection of programs known as Network Management Facilities (NMF). Because "netutil" is incompatible with the new configuration file format, it is deleted by the ENT and FTF installation procedures. This is required and automatic. 4. The new NMF event log is different from the old network event log. Old network event logs will become unusable when 7.3 ENT or FTF is installed. If the content is of interest, the logs should be listed using the "netutil" BEFORE installing the new products. 5. The user reference manuals for 7.3A MAGNET and FTF are not available. Refer to the MAGNET BOSS/VS User Reference Manual(M6363) for configuration instructions and to the File Transfer Facility User Reference Manual (M6352) for FTF operations. 6. ENT and FTF uses CMB port 1 when X.25 is installed. This port must be strapped as "modem". The maximum baud rate supported by X.25 on 7.3A is 4800 baud. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg017 2.4.4 27xx/37xx Batch Emulation 1. The 27xx/37xx Batch Emulation package is now written in BASIC and is called TBC (Transportable Batch Communications). The C version of 27xx/37xx Batch Emulation (EBC) is no longer available on the 2000/3000 systems. TBC on 7.3A is compatible to TBC on MPx and 13xx systems, as well as 2000/3000 systems running EBC, since the line protocol has not changed. 2. To install TBC, execute the command: admin> install xx TBC where xx is the device of the TBC media cs = 1/4" MCS ts = 1/2" MTS fd0 = floppy drive 3. Conversion of the transmit queue, receive queue, and autoprompt files is automatically performed when installing TBC on a system previously using the EBC product. The public key for TBC is compatible with the EBC public key. 4. There are no operational changes between TBC and EBC when running BCOM from the Communications menu. However, since the 7.3A version of bcom is written in BASIC, there are changes in accessing BCOM from command mode: user prompt>basic s=128 pgm=/tbc/BCOM/BCOM 5. A new utility, /util/BCOMPFX, allows users to specify which directories the BCOM program files and data files reside in. Previously, EBC required that bcom program files be in /util and data files were created in /etc/comm. With TBC on 7.3A users may copy the BCOM program files from /tbc/BCOM to another node and run BCOMPFX to specify the new node. Data files such as autoprompts, receive queues, transmit queues, will be created in the node specified as the data prefix in BCOMPFX. To access BCOMPFX from command mode, type: user prompt>basic pgm=/util/BCOMPFX 6. TBC on 7.3A supports autodial features which allow BCOM to interface to an automatic calling unit (ACU) to dial the number stored in the BCOM autoprompt file. Two utilities, ACUTD and ACS, have been added to TBC: ACUTD - utility to build scheduler lists of BCOM autoprompts which are designated to be activated at specified date and times. ACUTD can be accessed from the SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg018 communications menu or alternately from command/console mode. user prompt>basic s=128 pgm=/tbc/BCOM/ACUTD ACS - program which activates the scheduler lists specified in ACUTD. ACS can be accessed from the communications menu or alternately from command/console mode. user prompt>basic s=128 pgm=/tbc/BCOM/ACS 7. The 7.3A automatic calling features of TBC have been certified with the following ACU's and modems: o Universal Data Systems 801C ACU with Universal Data Systems 201C synchronous modem - This combination requires a serial asynchronous port be configured as a terminal (EVDT with default parameters) for the 801C ACU and CMB port 1 configured for the synchronous communications port. The UDS 201C is compatible to other vendor's BELL 201C compatible units. o Paradyne FDX 2400 PLUS ACU/modem - This unit also requires a serial port be configured as a terminal (EVDT with default parameters) for the ACU interface and CMB port 1 configured for synchronous communications. This unit is compatible with another Paradyne FDX 2400 Plus, a Bell 212A synchronous modem, and a Universal Data Systems 224 synchronous modem. 8. TBC uses CMB port 1. This port must be strapped as "modem". The maximum baud rate for TBC is 4800 Baud. 9. Details on TBC and modem/ACU strappings are documented in the BOSS/IX Transportable Batch Communications (27xx/37xx) User Guide - M6353C. 2.4.5 Asynchronous Transport Package (ATP) 1. A new level of ATP (4.0) is included with the 7.3 EIT product. ATP 4.0 contains protocol changes for performance enhancements which makes it incompatible with previous releases of ATP. All systems using ATP to communicate to a 7.3A system must also have ATP 4.0 on their systems. 2. In addition to performance enhancements, ATP 4.0 provides the following features: o Line Turnaround - allows transmit and receive functions in a single session o Autodial - supports automatic dialing of Hayes/compatible and UDS 224 A/D modems o Scheduler - provides unattended startup of ATP sessions SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg019 3. To install ATP 4.0, the EIT product must be installed: admin> install xx EIT where xx selects the device of the install media cs = 1/4" MCS ts = 1/2" MTS fd0 = floppy drive 4. To activate the features of Line Turnaround, Autodial, and the Scheduler, a public key must be installed: admin> install_key /etc/level/ATP 5. As with previous levels, BQR must be run to generate an ATP filelist. Note, however, that schema files are no longer supported by BQR for any transport media - transmitted files must either be in TEXT or BINARY format. After BQR filelists are created, RUN "ATP" to set the communications parameters for the session. The parameters may be saved in an autoprompt for future use or use with the Autodial and Scheduler features. RUN "ATPTIM" to set the Scheduler parameters. RUN "ATPSCH" to begin the ATP sessions according to the parameters set in the Scheduler. 6. Automatic file conversion and translation occur during the file transfer. BQR will no longer be required to convert files received via ATP 4.0 from unlike systems. 7. Refer to the ATP 4.0 Software Announcement #150 and the Intersystem Transport Package User Guide (M6354D) for details. 2.4.6 3270 Bisynchronous 1. To install the 3270 Bisynchronous product, execute the command: admin> install xx B32 where xx selects the device of the install media cs = 1/4" MCS ts = 1/2" MTS fd0 = floppy drive 2. B32 uses CMB port 1. This port must be strapped as "modem". The maximum baud rate supported by B32 is 4800 Baud. 3. As with previous releases of B32, the DT-4310 is SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg020 the only terminal which is supported to emulate an IBM 3278 display terminal. 2.5 Security Configuration Record When installing 7.3A on your system or if you are upgrading/adding to the system's hardware, you must also install/upgrade to a 7.3A security configuration record. See step #4 of section 2.2 Installation of the Operating System for instruction. 2.5.1 7.3A Configuration Record Request Sheet On the following page you will find a copy of the 7.3A Configuration Record request sheet. Refer to Software Announcement 153 for Configuration Record Request Sheet. 3.0 LEVEL 7.3 BOSS/IX ENHANCEMENTS/CORRECTIONS 3.1 OPERATING SYSTEM (EOS) 3.1.1 Shared Libraries Instead of each program having a copy of the library, they are shared. This results in less disk space required for the program. 3.1.2 Improved 1/2 inch Tape Support The 1/2 inch tape now supports system boot and software distribution, as well as backup and restore capabilities. 3.1.3 Merged Tape Commands and Utilities The tape commands and utilities have been merged. The tape commands/utilites are now 't' for tape, instead of 'mcs' or 'mts'. When you enter the command/utility name, the 'utility' will be run. To specify the 'command' instead of the utility, enter the device name when you enter the command/utility name, ie: tlabel will execute the tape label utility. tlabel dev=cs {options} will execute the tape label command. 3.1.4 Console Configuration Setting of the system console type is no longer done by the boot PROM configurator. Other system console parameters must still be set through the boot PROM configurator. After the install procedure is complete, the port configuration utility, 'configure', should be used to set the terminal type for for the console. This SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg021 step cannot be done until the operating system and utilities (EUT) have been installed. The console type will be read from the /etc/terminals file. The other console parameters (port number, baud rate, etc) will be read from the NVRAM. 3.1.5 vconf Configuration File The configuration files created by vconf have new fields and functionality. Only configuration files created with a 7.3 vconf command will work on a 7.3 operating system. Do not restore a 7.2 configuration file on a 7.3A operating system. New options: ghosts=# Maximum number of Ghost tasks. dirc=# Number of directory cache entries. fds=# Maximum number of open files on the system. NOTE: opens=# is an obsolete option, it has been replaced by the fds=# option. Also the recommended vconf parameters have changed. See section 6. 3.1.6 System Security Configuration Record format change The System Security Configuration Record format has changed. You must install a 7.3A configuration record on a 7.3A Operating system. Do not attempt to use a 7.2 configuration record on a 7.3A Operating System. 3.1.7 System Dump Changes System dumps now go directly to tape or floppy. Dumps must be written to media before the system is reloaded or the information will be lost. Also, a new command 'dmplog' has been added. This command displays the last 8 entries in the in-memory error log table from a dump. Often times, the cause of the dump can be determined by the information in these entries. This will allow you to evaluate the problem, and often times resolve it, on site at the time it occurred. If necessary, a dump can then be submitted to Product Support for further analysis. Example: dmplog --> /dev/cs, dev/ts, or /dev/fd0 3.1.8 Reduced Memory Requirements The following changes in the operating system have reduced SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg022 the system memory requirements; therefore, the available user memory is increased. 1. Reduced size of unswappable memory. 2. Reduced default configuration parameters. 3.1.9 Reduced Disk Requirements The disk space required for the base product Operating System (ie: EOS, EBS, and EUT) have been reduced accordingly: 7.1B 7448 KB (7.27 MB) 7.2B 9283.5 KB (9.07 MB) 7.2D1 8650 KB (8.45 MB) 7.3A (2000) 4048 KB (3.95 MB) (3000) 3979 KB (3.89 MB) NOTE: These values were calculated using a base configuration on a newly installed Operating System and its commands, BASIC and its utilities, and the system utilities. 3.1.10 New System Error Logger The new system error logger file has a limited number of terminal error entries. This will keep the file from getting filled up with terminal entries which causes other errors to be lost. It is now eaiser to read. The new format allows disk error entires to be interpreted without an Error Logger Specification. The new command options are: -mem display only the errors associated with memory. -tape display only tape errors. -term display only terminal errors. -printer display only printer errors. -comm display only communication errors. -disk display only disk errors. -text used in conjunction with the '-disk' option, means display a description of the disk errors. Example: /sys/errlog Displays the last 8 entries in the error log only. (These are still in memory) /sys/errlog /etc/error.log Displays the error log SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg023 / stored on disk. /sys/errlog /etc/error.log -disk -text Displays the text description of the disk errors. 3.1.11 File Integrity Checking A flag for each file is set when the file is opened, then reset when the file is closed and/or when the buffer is flushed. The command fichk will check a filesystem or directory for files which lack integrity (open when a system crash occurred). This command should be run after a pre-mature shutdown. After the automatic file system check is complete and the system is rebooted normally, use the fichk command with the filelist option to generate a list of corrupt files. Then, run the frepair utility using the file list generated by fichk to repair the file and clear the integrity flag in the file. Format: fichk Options: -clear clears the flag which marks the file as lacking integrity. -filelist generates a filelist file which contains the names of the files found to lack integrity (named "/util/fl/fichk.f"). Example: fichk /dev/root Displays the filenames of files on the /dev/root filesystem which lack integrity. fichk / -filelist -clear Displays filenames of files in the / directory and subdirectories which lack integrity; generates a a filelist named "/util/fl/fichk.f" of the files found; also, clears the integrity flag in the files found. NOTE: The fichk command reports the full path name of the files which lack integrity. It does not repair the file. The frepair utility must be run on the files found. 3.1.12 Configurable Number of Ghost Tasks The maximum number of Ghost Tasks on a system is now a user configurable parameter in vconf. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg024 3.1.13 Improved BOSS/IX Swapping Performance Swapping is now determined by the priority status of the WAIT state. The system now takes less time to determine which process to swap and it makes a better choice. This lessens the system performance degridation due to excessive swapping. 3.2 SYSTEM UTILITIES (EUT) 3.2.1 frepair Utility The frepair utility now has the capibility to retire a a bad block, report which file (if any) the bad block resides in, and gives you the option of repairing the file. You no longer have to re-format the disk each time a bad block is reported in the hardware error logger. NOTE: This will reduce the file system space. 3.2.2 Configure Utility 3.2.2.1 Configure the system console The configure utility has been change to allow the user to set the terminal type for the system console. It now automatically adjusts the /etc/terminlas and /etc/ports entries if the console has been moved since the last time the utility was executed. The system software will ignore the console terminal type in the NVRAM. The console type will be read from the /etc/terminals file. The other console parameters (port number, baud rate, etc.) will be read from the NVRAM. The configure utility and the sysinfo command which reads the /etc/terminals file can report a different console type than the "config" which reads the NVRAM. However, only the values in the /etc/terminals file have any effect on the functionality of the console terminal. 3.2.2.2 New Terminal Types Two new terminal types have been add to the configure utility. The 4313 and 4314 are now available terminal types. 3.2.2.3 Configuring Printers The configure utility has been changed to use marketing numbers instead of names, except for hpplot, isp and spe. The following table shows the relationship between the printer market codes and the actual PDF's used to support them: SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg025 Market Code Actual PDF 4201 dmp 4203 b4whis 4208 isp 4210 oki 4211 diablo 4212 isp 4212B4 oki 4213 whispr 4213B4 b4whis 4214 dmp 4215 fuji 4216 daisy 4217 4218 4218 4218 4220 4220 NOTE: When upgrading from a previous level, printers must be reconfigured using the new market codes. 3.2.3 pparams Utility A field has been added to the /etc/forms file for the number of form feeds to print before each spooled print job. The default value is 1. To change this, use the 'modify' option in the 'maintain form definitions' options. NOTE: A value of 0 (zero) will cause no form feed to be sent from the spooler. 3.3 BASIC (EBS) 3.3.1 BUSINESS BASIC 86 Business Basic 86 or BB86 (TM) is an evolving standard language supported on both BOSS/IX and BOSS/VS. It includes: o Compatibility features o Program generation tools o More system independent features o Multi-key file support For a detailed explanation of BB86 refer to the BUSINESS BASIC 86 REFERENCE MANUAL, M 6262. 3.3.2 BASIC on 7.3 is not backward compatible Some Basic directives on 7.3 generate a different code when compiled than is generated when compiled on prior Basic levels, therefore, 7.3 Basic is not backward compatibily. The following directives and functions are not backward compatible from 7.3A to 7.2 or prior: SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg026 FID, IND, ENCRYPT, RENAME, RELEASE and QUIT. NOTE: This effects only Basic program files, NO other file type is effected by this. 3.3.3 Changed Functionality 1. The RELEASE directive will now log the user off the system. The QUIT directive should be used in place of RELEASE to exit Basic and return to the command interpreter level. 2. The PNM system variable in a CALLed program will return the name of the CALLed program. In 7.2 Basic, PNM in a CALLed program would return the name of the CALLing program. 3. The PNM function returns a fully qualified program name (e.g., "/usr/joe/myprogram" rather than simply "myprogram"). 4. Since 7.3A supports longer device names (e.g., "TA" has become "T10", names which were valid file names in 7.2 and prior releases might be interpreted as device names under 7.3A. For example, suppose that a 7.2 program was using a file named "T10", under 7.3A, if the system had configured that 11th terminal then "T10" would be treated as a device name. This problem may occur with any directive that uses file names (e.g., RUN, OPEN, DIRECT, and INITFILE). 5. The FID directive returns the device value that was opened. Example: OPEN(1) "T10" PRINT FID(1) returns T10 OPEN(1) "TA" PRINT FID(1) returns TA 6. FID (0) returns the 4 character device name. Example: If the terminal ID is T10, the FID (0) will return T10 not TA. 7. The SYS Function returns information formatted in a slightly different way then 7.2 and prior versions of BASIC. It used to return a string such as "EBS7226" and will now return something like "BB86 07.03A*52.01". 8. 7.2 -trans= file's required that the first line in this file begin with "EBS". 7.3A will NOT allow this EBS line and it must be removed. 9. 7.2 and prior versions of the O/S would intercept ctrl-R's. Ctrl - R's may now be read by BASIC programs using INPUT RECORD (0,SIZ=1)A$ commands. 10. Changing the system time will not always affect the TIM function in BASIC programs. The TIM value is SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg027 set the 1st time BASIC uses TIM and will not be reset until BASIC is exited and then re-entered. 11. The echoing of the tab key has changed going from 7.2 to 7.3A. Prior to 7.3A, the tab key would position the cursor to the next tab position on the same line. Beginning with 7.3A, the tab key will now reposition the cursor to the @(0,0) home position. 12. There are quite a few new reserved words that have been introduced in the 7.3A BB86 release of BASIC. These may no longer be used as variables in user programs. The following table lists each new reserved work and gives a thumbnail sketch of each use: ___________________________________________________________________________ | | | ALIAS Part of FIELD ALIAS | | ASCII Compatible ASC function. For example ASC (" ") returns | | 32 | | ATTR Used within OPEN, CREATE and as a funciton for file | | attributes | | CHAR Compatible CHR function. CHAR(65) returns "A" | | CONSOLE Part of CONSOLE LOCK | | CONSOLELOCK Causes prompt for password whenever about to enter | | console-mode | | CREATE Like FILE but has more options and uses a readable string | | CSW Function returning 0 if current program in RUNning, 1 if | | CALLed | | DEVINFO Return information on all devices on system | | ENDFORM Reserved for future use | | ENDIF Terminates a compound IF statment (like FI) | | ENDTRANS Turns off automatic file name translation | | FIELD Part of FIELD ALIAS and SET FIELD | | FIELDALIAS Associates field-variables with different multi-key | | fields | | FMT Used to specify mutli-key format strings | | FMTINFO Returns a multi-key format string | | FORM Reserved for future use | | FORMFILE Reserved for future use | | INIT Part of INIT FILE | | INITFILE Clears out an already existing file | | LISTPROGRAM Converts a program into a ASCII serial file | | MAKE Part of MAKE PROGRAM | | MAKEPROGRAM Converts an ASCII serial file into a program | | MSG Used within CONSOLE LOCK and SET FIELD for messages | | MULTI Creates a multi-key file | | OPENFORM Reserved for future use | | PACK "Writes" to an internal logical unit buffer | | PNM Returns the fully qualified name of the current program | | PSAVE "Protected" program save (like ENCRYPT) | | QUIT Drops from BASIC back to 'shell' (same as 7.2's RELEASE) | | RETAIN Used on I/O to manage an internal logical unit buffer | | SETFIELD Adds or deletes keys in a multi-key file | | SETFORM Reserved for future use | | SETTRANS Specifies how automatic file name translation is to occur | | SYNTAX Checks syntax of a string | | TANS Used with SETTRANS to return translated strings | | TRX Returns the name of the SETTRANS file | | UNPACK "Reads" from an internal logical unit buffer | SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg028 | WHO Returns the name of the current user account | | | |___________________________________________________________________________| Note that 7.2 and earlier programs that use these reserved words will still run as long as lines containing these words are not edited or MERGEd. Once the syntax error is in the program, however, it will probably not run correctly and such variable names must be changed. This situation is normal for any new release of BASIC that supports new features. There is, however, a much longer than normal list of new reserved words for 7.3A and hence a much greater chance of a word being used as a variable. 3.3.4 BOSS/VS & BOSS/IX Compatibility Notes 1. The FID(0) in batch mode returns different results based on the system. In BOSS/VS, FID(0) in batch mode returns the full 80 byte string. In BOSS/IX, FID(0) in batch mode returns Tx. 2. In BOSS/VS, the following statement is accepted: IF A=1 THEN PRINT OK ELSE PRINT NO; ENDIF In BOSS/IX, the semicolon before the ENDIF will generate an error. 3. String functions and string system variables may use an optional '$' in their name on BOSS/VS. For example, the CHR function can be used as C$ = CHR(n) or C$ = CHR$(n). The optional '$' will cause an error on the BOSS/IX system. 4. The keysets are handled differently when two fields occupy the same position in a record of a Multi Key file. BOSS/VS Two fields defined with the same physical start position and length can NOT both be keysets. Example: F1# = S10 Primary Key F2# = S10 ALT Key F3# = F2# Can NOT have keyset BOSS/IX Two fields defined with the same physical start position and length MAY both have keysets defined provided the keysets are of different types. Example: F1# = S10 Primary Key SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg029 F2# = S10 F3# = F2# Then, fields F2# and F3# may have keys defined F2# F3# Error Code (if any) DUP Key ALT Key No Key ALT Key ALT Key ALT Key err 12, -37 NO Key DUP Key NO Key ALT Key NO Key NO Key DUP Key DUP Key err 12, -37 Primary DUP Key Primary NO Key Primary ALT Key err 12, -37 5. BOSS/VS and BOSS/IX will return a different error code when a WRITERECORD with IND= or KEY= option is used on a Multi Key file. BOSS/VS error 13 BOSS/IX error 17 3.3.5 Unsupported Mnemonic on PT4220 On a PT4220 only, output transparency does not work and is not supported. 4.0 NEW PRODUCTS IN LEVEL 7.3A 4.1 Universal Printer Driver (UPD) The UPD is a collection of tools which allow the user to define control and mnemonic support for any printer connected to the MAI system. Although the UPD was conceived with the maximum flexibility in mind, there may be printers which cannot be fully supported through UPD. System Independent Multi Purpose Language (SIMPLE) is one of the UPD tools. It is a "language" used to create a printer definition file (PDF) in which a user defines printer attributes and mnemonic support. The program that the user creates using SIMPLE is compiled and this compiled output is used by a module known as the SIMPLE Executor to drive the printer in question. The UPD product will not reside on the customers system. It is a development tool for creating a PDF. For more information, refer to the Universal Printer Driver Reference Manual, #M0053A. 4.2 PDF (Printer Definition File) The PDF product is required on the customer system to use the SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg030 driver created with the UPD product. It is a security feature. PDF requires a key from Software Distribution. Once the key is entered the driver created with UPD can be used on the customers system. 5.0 FOR YOUR INFORMATION This section gives the warnings and cautions for the 7.3A Operating System and a workaround if one is available. 5.1 Operating System (EOS) 1. SPR 514790: The OS update procedure changes the "spooling" field to "N" instead of "Y" in the SPLON record in the /etc/class file. Workaround: Use the pparams utility to change spooling back to "Y". 2. SPR 514791: A "PRINT" statement in a ghost task will generate an err 0 when you try to read the value if the 10 sec. time out for disk I/O occurs before the read. Workaround: None - if the ghost is being read concurrently you should not see this. 3. SPR 514792: If you change the value of the high bit flag in the /etc/class file, it is ignored. Workaround: None 4. SPR 514793: If you change the value of the pitch and/or lines per inch field in the /etc/forms file, it is ignored on some printers. Workaround: Use the mnemonic or the hex value in the basic program to change lines per inch or pitch. 5. SPR 514847: All of your data will not be sent to the printer if an 'EO' mnemonic, followed by at least one character, is not excuted prior prior to closing the printer. Example 1: 0010 OPEN (1) "P0" 0020 PRINT (1) 'B0", 0030 FOR I=1 TO 60 0040 PRINT (1) "This is a test", I,$0D0A$, 0060 NEXT I 0070 CLOSE (1) 0080 END This program will lose data because there is no 'EO mnemonic before the close statement. Example 2: 0010 OPEN (1) "P0" SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg031 0020 PRINT (1) 'B0", 0030 FOR I=1 TO 60 0040 PRINT (1) "This is a test", I,$0D0A$, 0060 NEXT I 0070 CLOSE (1)'EO', 0080 END This program will also lose data because there is no character following the 'EO' mnemonic. Example 3: 0010 OPEN (1) "P0" 0020 PRINT (1) 'B0", 0030 FOR I=1 TO 60 0040 PRINT (1) "This is a test", I,$0D0A$, 0060 NEXT I 0070 CLOSE (1)'EO' 0080 END This program works because BASIC appends a line feed after the print statement with the 'EO' mnemonic. 5.2 BASIC (EBS) 1. Composite fields whos starting position is not specified and whose length is specified thru ":" are not interpreted correctly, for example "F2#=F1#:8". The work -around is to specify the starting position, for example "F2#=F1#(1):8" or "F2#=F1#(1,8)". 2. If a composite field is defined thru "(s):1" before its component field is defined in the format string, for example "F1#=N10 PRIMARY F2#=F1#(1):12 F3#=N5", then the record size is not computed correctly. The work-around is to use "(s,1)" format instead, for example "F1#=N10 PRIMARY F2#=F1#(1,12) F3#=NS". 3. If a composite field is defined beyond the end of fixed fields, for example "F1#=N10 PRIMARY F2#=N5 F3#=F1*(1,18)", then the size of the record is not extended. This problem might be too unrealistic. But one suggested work-around is to define an additional fixed field, for example: "F1#=N10 PRIMARY F2#=N5 F3#=F1*(1,18) F4#=lN3". All problems above are within the BFS library routine "bfsfmtcpl()" which compiles the format strings. It has been fixed for 7.4A. Here are some examples and work-arounds. 1. "F1#=N10 PRIMARY F2#=F1#:8" is interpreted as "F1#=N10 PRIMARY F2#=N10", but "F1#=N10 PRIMARY F2#=F1#(1):8" works. 2. "F1#=N10 PRIMARY F2#=F1#:12" is interpreted as "F1#=N10 PRIMARY F2#=N10", but "F1#N10 PRIMARY F2#=F1#(1):12" works. 3. "F1#N10 PRIMARY F2#=F1#(1):12 F3#=N5" is interpreted to define a record whose size is 10 instead of l15. But SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg032 "F1#=N10 PRIMARY F2#=F1#(1,12) F3#=N5" works. 4. "F1#=N10 PRIMARY F2#=F1#(1,18)" is interpreted to define a record whose size is 15 instead of 18. 5.3 FTF via LAN and X.25 o Constant full duplex file transfers (simulataneous transfers in both directions) can cause the X.25 link to fail after approximately 30 hours. Workaround: If link failures occur, decrease the amount of full duplex file transfers. o When there is heavy activity on the system, enough to cause swapping of processes, abort 79's can occur. Workaround: Use the rescheduling option of FTF or schedule files during non-peak hours. o File transfers of a file on a remote system (i.e. a system connected via LAN) is not supported and will cause the session to be "In Progress" forever. Workaround: This feature is currently not supported and should not be used. 5.4 MAGNET via LAN and X.25 o When rcopy is used to update a remote file (replace existing files) and the destination file is currently locked by another process, the copy will still occur and the data is 'temporarily stored' in the remote system until the file is unlocked. There is no message on the source systems stating this is so. Workaround: None. This is the same implementation of a local copy command. o LAN timeout errors -554 or -527 occur with moderate to heavy full duplex remote file activity. These errors are caused by the remote file access processes being swapped out. Workaround: Retry operation. Reduce heavy full duplex activity or reduce processing on the remote system. 5.5 Intersystem Transport Package (EIT) o EIT will no longer support mixed format schema files. Only TEXT (convert all data) and BINARY (don't convert all data) are supported. o ATP 4.0 is released with the EIT product. ATP 4.0 is NOT compatible with previous releases of ATP. o Only files which are compatible between unlike systems can be transferred - i.e. string file transmissions can only occur between Boss/IX systems. o ATP 4.0 supports direct connections between 1200 - 9600 SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg033 Baud. ATP 4.0 supports modem connections of 1200 and 2400 Baud using the following modems: UDS 212A UDS 212 A/D UDS 224 A/D UDS FASTTALK "Hayes compatible" HAYES Smartmodems 5.6 3270 Bisync o As with previous releases, the 4310 (EDT) is the only terminal supported as a 3278 display terminal. 5.7 Graphics o When installing Graphics on a floppy diskette you must install 3.1 NOT GRF and GKS. 6.0 Memory Requirements and Operating Parameters 6.1 Approximating A System's Memory Requirement This section describes how to approximate the amount of memory a system needs. Tables 6A and 6B show some standard system configurations which can be used to approximate the amount of memory a system needs. The number of users (terminals), ghost tasks, and printers differ for each of these standard configurations. First, find the standard configuration that most closely matches the system in question, by scanning down the user/terminals, ghost-task, and printers columns. Second, scan across the table to the memory-needed column -- this is the system's memory requirements. NOTE: These tables (6A and 6B) assume that the system in question will be executing 60% BASIC and BASIC application programs, and 40% non-BASIC applications. If the system will be executing a higher percentage of non-BASIC programs, it will need more memory. Tables 6C and 6D show how to set up the BOSS/IX configuration ("vconf") parameters for each of the standard system configurations in tables 6A/B. In other words, if one uses the approximation method to determine a system's memory requirements, tables 6C/D can be used to . set up the BOSS/IX configuration parameters. The approximation method is an easy and accurate way to determine a system's memory needs, if its configuration is close to one of the standard configurations. However, if it does not closely fit one of the configurations shown, the calculation method should be used (see section 7.1). _________________________________________________________________ | | | | | | | Standard | Users/ | Ghost | Printers | Memory | | Configuration | Terminals | Tasks | | Needed | | | | | | | | | | | | | | number 1 | 2 | 0 | 1 | .75 MB | | | | | | | | | | | | | SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg034 | number 2 | 5 | 1 | 2 | 1.00 MB | | | | | | | | | | | | | | number 3 | 9 | 2 | 2 | 1.25 MB | | | | | | | | | | | | | | number 4 | 12 | 3 | 3 | 1.50 MB | | | | | | | _________________________________________________________________ NOTE: 1 MB (Megabyte) = 1024 KB (Kilobyte) = 1024 * 1024 bytes TABLE 6A Approximating the Memory Requirements for an MAI 2000 System ------------------------------------------------------------------------------- _____________________________________________________________________ | | | | | | | Standard | Users/ | Ghost | Printers | Memory | | Configuration | Terminals | Tasks | | Needed (MB) | | | | | | | | | | | | .| number 1 | 2 | 0 | 1 | 1 | | | | | | | | | | | | | | number 2 | 9 | 2 | 2 | 2 | | | | | | | | | | | | | | number 3 | 16 | 4 | 4 | 3 | | | | | | | | | | | | | | number 4 | 22 | 6 | 6 | 4 | | | | | | | | | | | | | | number 5 | 28 | 8 | 9 | 5 | | | | | | | | | | | | | | number 6 | 34 | 10 | 10 | 6 | |_____________________________________________________________________| TABLE 6B Approximating the Memory Requirements for an MAI 3000 System NOTE: The number of users/terminals shown is approximately the highest number which can be supported in the memory shown. ------------------------------------------------------------------------------- _____________________________________________________________ | | | | "vconf" BOSS/IX | Standard Configuration (see Table 6A): | | Parameter |___________________________________________| | | | | | | | | number 1 | number 2 | number 3 | number 4 | |_________________|__________|__________|__________|__________| |buffers=.........|.......20.|.......32*|.......48*|.......60*| SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg035 |printers=........|........1.|........2.|........2.|........3.| |procs=...........|.......16*|.......27*|.......40*|.......51*| |tsegs=...........|.......16*|.......22*|.......30*|.......36*| |locks=...........|.......74.|.......94*|......119*|......139*| |ibsize=..........|......128.|......128.|......128.|......128.| |tbsize=..........|.......64.|.......64.|.......64.|.......64.| |mfsys=...........|........3.|........3.|........3.|........3.| |lus=.............|......136*|......222*|......322*|......408*| |fds=.............|.......60.|.......96*|......138*|......174*| |eventcalls=......|.......16*|.......22*|.......30*|.......36*| |sockets=.........|........6.|........6.|........6.|........6.| |dsockets=........|........8.|.......14.|.......20.|.......26.| |lanbuffers=......|..........|.......12.|.......16.|.......16.| |dirc=............|.......64.|......102.|......144.|......170.| _____________________________________________________________ TABLE 6C "vconf" BOSS/IX Parameters for Standard MAI 2000 NOTE: The "standard" configurations are described in Table 6A. "*" means that this number has changed from 7.2 to 7.3A. "opens" on 7.2 are now called "fds" on 7.3A. "dirc" is a new parameter for the MAI 2000 vconf file. ------------------------------------------------------------------------------- _________________________________________________________________ : : : : "vconf" BOSS/IX : Standard Configuration (see Table 6B) : : parameter :_______________________________________________: : : #1 : #2 : #3 : #4 : #5 : #6 : :_________________:_______:_______:_______:_______:_______:_______: : buffers= : 128 : 704 : 1280 : 1792 : 2304 : 2816 : : : : : : : : : : printers= : 1 : 2 : 4 : 6 : 8 : 10 : : : : : : : : : : procs= : 16* : 40* : 65*: 87*: 110*: 131*: : : : : : : : : : tsegs= : 16* : 30* : 44*: 56*: 68*: 80*: : : : : : : : : : locks= : 74 : 119 : 164 : 204 : 244 : 284 : : : : : : : : : : ibsize= : 128* : 128* : 128* : 128* : 128* : 128* : : : : : : : : : : tbsize= : 64* : 64* : 64* : 64* : 64* : 64* : : : : : : : : : : mfsys= : 3 : 3 : 4 : 4 : 5 : 5 : : : : : : : : : : lus= : 136 : 322 : 556 : 656 : 864 : 1030 : : : : : : : : : : fds= : 60 : 138 : 218 : 290 : 364 : 434 : : : : : : : : : : eventcalls= : 16* : 30* : 44* : 56* : 68* : 80* : : : : : : : : : : dirc= : 64 : 142 : 222 : 294 : 368 : 438 : : : : : : : : : :_________________:_______:_______:_______:_______:_______:_______: SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg036 TABLE 6D "vconf" BOSS/IX Parameters for Standard MAI 3000 Configurations NOTE: The "standard" configurations are described in Table 6B. "*" means that this number has changed from 7.2 to 7.3A. "opens" on 7.2 are now called "fds" on 7.3A. ------------------------------------------------------------------------------- 6.2 Recommended Values for "vconf" The following tables (Table 6E and 6F) show the recommended values for the BOSS/IX "vconf" parameters. 6.2.1 Recommended Values for "vconf" BOSS/IX Model 2000 Parameters __________________________________________________________________________ | | | | | | | | SYSTEM | base | add | add | add | maximum | | DESCRIPTION | system: | for | for | for | recom- | | -----> | | each | each | each | mended | |_______________| 2 user | extra | ghost | extra | system | | | 1 printer | user | task | printer | config- | | "vconf" | | no ghosts | (above 2) | | (above 1) | uration | | BOXX/IX | | | | | | (See | | PARAMETERS | | | | | Note 2) | |---------------|-----------|-----------|-----------|-----------|----------| |buffers=.......|........20.|.........4.|...........|...........|.......64.| |printers=......|.........1.|...........|...........|.........1.|.......14.| |procs=.........|........16.|.........3.|.........1.|.........1.|.......80.| |tsegs=.........|........16.|.........2.|...........|...........|.......64.| |locks=.........|........74.|.........5.|.........5.|...........|......160.| |ibsize=........|.......128.|...........|...........|...........|.....2048.| |tbsize=........|........64.|...........|...........|...........|......512.| |mfsys=.........|.........3.|...........|...........|...........|.......*..| |lus=...........|.......136.|........20.|........20.|.........6.|......254.| |fds=...........|........60.|.........8.|........10.|.........2.|......206.| |eventcalls=....|........16.|.........2.|.........5.|...........|......152.| |dirc=..........|........64.|.........8.|........10.|.........2.|......206.| |ghost=.........|.........0.|.as.needed.|...........|...........|.......99.| |..........................................................................| | * Allow one mountable filesystem slot ("mfsys") for each | | mountable disk partition. The default of three allows | | for a boot partition, a root filesystem partition, and | | a diskette filesystem or 2nd drive. | |__________________________________________________________________________| NOTE 1: The BOSS/IX configuration parameters required for other products are described in their documentation. Specifically, the LAN and 27xx/37xx communications products will require changes to the system parameters. For example, Magnet operating systems require 5 eventcalls per user. NOTE 2: These recommended values are not system limits but provide a guideline to tailoring the system. TABLE 6E SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg037 Recommended Values for Model 2000 Operating Parameters ------------------------------------------------------------------------------- 6.2.2 Recommended Values for "vconf" BOSS/IX Model 3000 Parameters _________________________________________________________________________ | | | | | | | | SYSTEM | base | add | add | add for | maximum | | DESCRIPTION | system: | for | for | each | recom- | | -----> | | each | each | extra | mended | |_______________| 2 user | user | ghost | printer | system | | | 1 printer | (above 2) | | | values | | "vconf" | | | | | | (Note 1) | | BOXX/IX | | | | | | | | PARAMETERS | | | | | | |_______________|___________|___________|___________|__________|__________| |buffers=.......|.......128.|........64.|........64.|..........|.(Note 2).| |printers=......|.........1.|...........|...........|........1.|.......34.| |procs=.........|........16.|.........3.|.........1.|........1.|......223.| |tsegs=.........|........16.|.........2.|...........|..........|......148.| |locks=.........|........74.|.........5.|.........5.|..........|......234.| |ibsize=........|.......128.|...........|...........|..........|..........| |tbsize=........|........64.|...........|...........|..........|..........| |mfsys=.........|.........3.|...........|...........|..........|.(Note 3).| |lus=...........|.......136.|........20.|........20.|........6.|......776.| |fds=...........|........60.|.........8.|........10.|........2.|......316.| |eventcalls=....|........16.|.........2.|.........5.|..........|......234.| |dirc=..........|........64.|.........8.|........10.|........2.|......512.| |ghost=.........|.........0.|.as needed.|...........|..........|.......99.| I_________________________________________________________________________I NOTE 1: Values in this column reflect 34 user totals calculated from recommended increments, except for buffers. NOTE 2: Only memory availability limits buffers. NOTE 3: Allow one mountable file system for each mountable disk partition. A default of 3 allows for a root, boot and 1 other partition. TABLE 6F Recommended Values for Model 3000 Operating Parameters ------------------------------------------------------------------------------- 7.0 Memory Usage This section describes how to determine the memory requirements for any MAI 2000 or MAI 3000 system. All BOSS/IX systems have different memory requirements. A system's memory requirement is based on its hardware configuration and software load. Specifically, the number of peripheral devices (i.e. terminals and printers) and software packages (such as BASIC, BASIC applications, utilities, etc.) determine a system's memory needs. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg038 This section explains two methods used to determine the amount of memory needed for a system. The first method approximates a systems memory requirements -- and can be used if the system closely fits one of the standard system configurations. The second method calculates the memory requirements for best system performance -- and is used for non-standard system configurations. 7.1 Calculating A System's Memory Requirements This section describes how to calculate the number of memory boards a system requires for adequate performance. The calculations are based on the system's hardware configuration and software load. Software load is defined to be the number and types of processes running on the system. 7.1.1 Model 2000 This section steps through an example based on system configuration number 2 in Table 6A, a 5 user system. (See section 7.1.1.1). STEP 1 First, add the space required for the operating system, table space and dynamic space required for the base configuration. NOTE: 1 KB = 1024 bytes 220 KB This is the memory requirement for the base BOSS/IX operating system program. This includes space for the system's interrupt vectors, and operating systems text (code) and data segments. 34 KB** This is the memory requirement for BOSS/IX table space for the base configuation: two users (terminals), one printer, and no ghost task. Note: additional table space must be added for each additional resource above that in the base configuration (see step 2). 37 KB** This is the memory requirement for the operating system's dynamic work space (or unswappable memory). STEP 2 Next, add in table space needed for resources beyond the ones described in the base configuration. (If the system will be configured like the base configuration skip this step). Note: the MAI 2000 is a table driven system, and for maximum performance extra memory must be allocated for resources beyond the ones described in the base configuration. 5 KB** This is the memory needed as table space for SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg039 each additional user above the two that are allocated in the base system. (Refer to Table 7A) 2 KB** This is the memory needed as table space for each ghost task in the system. (Refer to Table 7A) 1.5 KB** This is the memory needed as table space for each additional printer above the one that is included in the base system. (Refer to Table 7A) 1.6 KB** This is the memory needed for dynamic work space for each additional process (i.e. "proc") above the 31 that are included in the base system. (Refer to Section 7.2.1) ** Memory required for BOSS/IX table space and dynamic work space. These values are the memory allowance assuming that the configuration parameters are set according to Table 6A. If the system parameters are set differently, use section 7.2 and Table 7A to calculate the memory required for OS table and OS dynamic work space. STEP 3 Add the space needed for system processes for the base system configuation. 100 KB This is the memory allowance for system tasks. System tasks for the base system include: a printer despooler process, a system update process, a system error log process, and two command intrepreters. The total memory required to have all system processesin memory at the same time is approximately 200 KB. However, 100 KB should be used in this calculation because system processes wait on system events and it is not likely that all system processes will want to execute at the same time. Furthermore, these processes, when waiting for events, can be swapped to secondary storage, which will have little effect on system performance. STEP 4 Add the space needed for any additional system processes beyond the ones specified in the base configuration. (If the system will be configured like the base condiguration skip this step). 30 KB This is the memory needed for each additional printer despooler, above the one that is allocated in the base configuration. This is a memory allowance for the data and stack segments for an additional despooler task. An allowance for text (code) space is not necessary, beacuse two despooler tasks will share the same code segments. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg040 15 KB This is the memory required for each user (terminal) that will be executing tasks concurrently. This is the memory allowance for each additional command interpreter. It is space needed for the interpeters data and stack segments. Note: memory allowance for text (code) space is not necessary, because multiple command interpreters share the same code segments. Note: If the system is configured for ten operators, but the system only has five terminals -- i.e. a maximum of five users logged in at any instant -- then only 75 (5x15KB) need to be allocated. Furthermore, if one of the system terminals is seldom used, then space for that terminal does not have to be allocated. STEP 5 Next, add the space needed for applications processes. 160 KB This is space needed for each unique, non-BASIC task that will be executed concurrently on your system. Such tasks include the BASIC interpreter, utility programs, LAN, Informix, communications, BOXX/IX command interpreter, etc. Note: only one BASIC interpreter is needed to support any number of BASIC programs. This value is a rough estimate, for all processes require different amounts of memory, some more some less. When computing the memory required for application tasks, consider how often each application is used. For example, if the system seldom executes BOXX/IX commands or the utilities, only a percentage of the total space needed to execute these processes will be required. However, when the system is loaded, and these are executed, system response time may increase due to excessive amounts of swapping. 60 KB This is the memory required for each BASIC program. This space is the allowance for the data and stack segments oreach BASIC program. Note: all BASIC programs share the same text (code) segment. Furthermore, this value is not exact, for some applications may require more memory and some may require less memory. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg041 64 KB This is the memory required for each ghost task that will be executed concurently. This is the space needed for each ghost tasks' stack and data segments. Text space is not allocated because all ghost share the basic process text segment. STEP 6 Determine the memory/performance trade-offs. The value calculated in steps 1 thru 5 is the "memory required" for good system performance. However, this value is not exact and may be raised or lowered wich will increase or decrease performance respectively. By lowering the memory required value one can save the costs of an extra memory board, but at the expense of peformance. In other words, systems will run with less memory than required, however, the system overhead for swapping will increase. Process swapping is the action which extends user space to a temporary storage region on disk (i.e. the swap partition) so that, during periods of heavy main memory utilization, processes may be stored on disk to make room in memory for processes waiting to be executed. The advantage of process swapping is that it extends user space to disk (secondary storage); however, it is not without disadvantages. Swaping requires system overhead to read/write processes to/from secondary storage. Furthermore, excessive amounts of swapping will decrease system responsiveness (i.e. decrease performance). If the cost of memory is more important than user responsiveness, multiply the system's memory require- ment (calculated in steps 1 thru 5) by a value between 0.7 and 1.0. Multiplying the memory required value by 1.0 will cause normal amounts of swapping; multiplying it by 0.7 will cause process to be swappd to/from memory more frequently. Multiplying the "memory requirement" by some value greater than 1.0 will decrease the OS overhead for swapping. Note: do not run a system with less than 70% of the "memory required" value -- this will cause excessive amounts of swapping. The result of this calculation is your system's "memory need". STEP 7 Next compute the number of memory boards that the system needs. Dividing the "memory needed" value, calculated in Step 6, by 256 KB (memory needed / 256 KB). Note: 256 KB is the amount of memory on a board. If a fraction results, round off to the next highest whole number. The value calculated is the SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg042 "number of boards needed". Note: A maximum of six memory boards can be installed in an MAI 2000 system. If the value calculated in this step is greater than six memory boards, even with the 0.7 degradation factor (see step 6), you may be overloading your system! 7.1.1.1 Example of How to Calculate a System's Memory Requirement This example shows how to compute the memory requirement for a system with 5 terminals and two printers. Four of the terminals are dedicated to running BASIC applications: accounts receivable, accounts payable, payroll, and word processing. The fifth terminal is used to run the utilities, the commands, or the Informix database application. One of the applications uses a ghost task to output reports to a printer. STEP 1 thru STEP 5: Add these numbers to compute "memory required" 220 KB Base operating sytem 34 KB Table space for base system 37 KB OS dynamic work space for base system 5 KB x 3 Allowance for table space for three additional users (total of 5 users/terminals) 2 KB Allowance for table space for one ghost task 1.5 KB Allowance for table space for an additional printer (total. of 2 printers) 1.6 KB x 11 Allowance for dynamic work space for three additional users ("procs" - 31 in base). 100 KB Allowance for sytem processes 30 KB Allowance for concurrent printer to the second prnter. 160 KB x 2 Allowance for the BASIC interpreter and for the utilities/commands/Informix 60 KB x 4 Allowance for four concurrent basic applications 64 KB Allowance for one ghost task TOTAL = 1080 KB = "memory required" STEP 6: Compute "memory needed" For adequate system performance with frequent . swapping of applications tasks: "memory needed" = 1080 KB * 0.7 = 755 KB For good system performance with normal swapping: SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg043 "memory needed" = 1080 KB * 1.0 = 1080 KB For best system performance with minimal swapping: "memory needed" = 1080 KB * 1.1 = 1187 KB STEP 7: Compute the number of memory boards required For adequate system performance with frequent . swapping: number of boards = 775 KB / 256 KB = 2.9 or 3 boards Rounding to the next highest whole number means that for this hypothethical system, with frequent swapping of applications tasks, the system needs 3 memory boards. For good system performance with normal swapping: number of boards = 1080 KB / 256 KB = 4.2 or 4 boards Rounding down will cause a little more than normal swapping, but this is acceptable if the cost of memory is more important than user responsiveness. With normal swapping 4 boards are required. For best system performance with minimal swapping: number of boards = 1187 KB / 256 KB = 4.6 or 5 boards Rounding to the next highest whole number means that with niminal swapping 5 boards are needed. Furthermore, five boards give the system extra memory, which can be used for additional applications. The approximate method of determining a systems memory requirement (Section 6.1 and Table 6A) . shows that a system with 5 users (terminals), 2 printers, and 1 ghost task needs 4 memory boards. The calculation method, described in this section, shows that such a system will have different performance characteristics depending on the number of boards (i.e. either 3, 4 or 5) the system has. 7.1.2 Model 3000 This section steps through an example based on system configuration number 3 in Table 7B, a 16 user system. (See section 7.1.2.1). SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg044 STEP 1 First, add the space required for the operating system, table space, and dynamic space required for the base configuration. NOTE: 1 KB = 1024 bytes 230 KB This is the memory requirement for the base BOSS/IX operating system program. This includes space for the system's interrupt vectors, and operating systems text (code) and data segments. 98 KB** This is the memory requirement for BOSS/IX table space for the base configuration: 2 users (terminals), one printer, and 0 ghost tasks. NOTE: additional table space must be added for each additional resource above that in the base configuration (see step 2). NOTE: this excludes the memory required for hash tables for buffers and directory entries. 53 KB** This is the memory requirement for the operating system's dynmaic work space (or unswappable memory) for the base configuration (see 7.2.2) STEP 2 Next, add in table space needed for resources beyond the ones described in the base configuration. (If the system will be configured like the base configuration skip this step). NOTE: The MAI 3000 is a table driven system, and for maximum performance extra memory must be allocated for resources beyond the ones described in the base configuration. 41 KB** This is the memory needed as table space for each additional user above the two that are allocated in the base systems. (Refer to Table 7B). 41 KB** This is the memory needed as table space for each ghost task in the system. (Refer to Table 7B) 2 KB** This is the memory needed as table space for each additional printer above the one that is included in the base system. (Refer to Table 7B) 1.7 KB** This is the memory needed for dynamic work space for each additional process (i.e. "proc") above the 16 that are SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg045 included in the base system. (Refer to Section 7.2) ** Memory required for BOSS/IX table space and dynamic work space. These values are the memory allowance assumng that the configuration parameters are set according to Table 6B. If the system parameters are set differently, use section 7.3 and Table 7A to calculate the memory required for O.S. table and O.S. dynamic work space. STEP 3 Add the space need for system processes for the base system configuration. 100 KB This is the memory allowance for system tasks. System tasks for the base system include: a printer despooler process, and two command interpreters. The total memory required to have all system processes in memory at the same time is approximately 2000 KB. However, 100 KB should be used in this calculation because system processes wait on system processes will want to execute at the same time. Furthermore, these processes, when waiting for events, can be swapped to secondary storage, which will have little effect on system performance. STEP 4 Add the space needed for any additional system processes beyond the ones specified in the base configuration. (If the system will be configured like the base configuration skip this step). 30 KB This is the memory needed for each additional printer despooler, above the one that is allocated in the base configuration. This is a memory allowance for the data and stack segments for an additional despooler task. An allowance for test (code) space is not necessary, because two despooler tasks will share the same code segments. 15 KB This is the memory required for each user (terminal) that will be executing tasks concurrently. This is the memory allowance for each additional command interpreter. It is space needed for the interpreter. It is space needed for the interpreter's data and stack segments. NOTE: memory allowance for text (code) space is not necessary, because multiple command interpreters share the same code segments. NOTE: If the system is configured for ten operators, but the system only SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg046 has five terminals-- i.e. a maximum of five users logged in at any instant - - then only 75 KB (5x15KB) need to be allocated. Furthermore, if one of the system terminals is seldom used, then space for that terminal does not have to be allocated. STEP 5 Next, add the space needed for applications processes. 160 KB This is space needed for each unique, non-BASIC task that will be executed concurrently on your system. Such tasks include the BASIC interpreter, utility programs, LAN, Informix, communications, BOSS/IX command interpreter, etc. NOTE: only one BASIC interpreter is needed to support any number of BASIC programs. This value is a rough estimate, for all processes require different amounts of memory, some more some less. When computing the memory required for application tasks, consider how often each application is used. For example, if the system seldom executes BOSS/IX commands or the utilities, only a percentage of the total space needed to execute these processes will be required. However, when the system is loaded, and these processes are executed, system response time may increase due to excessive amounts of swapping. 60 KB This is the memory required for each BASIC program. This space is the allowance for the data and stack segments for each BASIC program. NOTE: all BASIC programs share the same text (code) segment. Furthermore, this value is not exact, for some applications may require more memory and some may require less memory. 64 KB This is the memory required for each ghost task that will be executed concurrently. This is the space needed for each ghost tasks' stack and data segments. Text space is not allocated because all ghost share the basic process text segment. The result of the sum of Steps 1 thru 5 is the system's "memory requirement". SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg047 STEP 6 Determine the memory/performance trade-offs. The value calculated in Steps 1 thru 5 is the "memory required" for good system performance. However, this value is not exact and may be raised or lowered which will increase or decrease performance respectively. By lowering the memory required value one can save the costs of an extra memory board, but at the expense of performance. In other words, systems will run with less memory than required, however, the system overhead for swapping will increase. Process swapping is the action which extends user space to a temporary storage region on disk (i.e.the swap partition) so that during periods of heavy main memory utilization, processes may be stored on disk to make room in memory for processes waiting to execute. The advantage of process swapping is that it extends user space to disk (secondary storage); however, it is not without disadvantages. Swapping requires system overhead to read/write processes to/from secondary storage. Furthermore, excessive amounts of swapping will increase system responsiveness (i.e. decrease performance). If the cost of memory is more important than user responsiveness, multiply the system's memory requirement (calculated in Steps 1 thru 5) by a value between 0.7 and 1.3. Multiplying the memory required value by 1.0 will cause normal amounts of swapping; multiplying it by 0.7 will cause processes to be swapped to/from memory more frequently. Multiplying the "memory requirement" by some value greater than 1.0 will decrease the O.S. overhead for swapping. NOTE: do not run a system with less than 70% of the "memory required" value -- this will cause excessive amounts of swapping. The result of this calculation is your system's "memory need". STEP 7 Next compute the number of memory boards that the system needs. Dividing the "memory needed" value, calculated in Step 6, by 1024 KB (memory needed/1024KB). NOTE: 1024 KB is the amount of memory on a 1 MB board. If a fraction results, round off to the next highest whole number. The value calculated is the "number of boards needed". 7.1.2.1 Second Example of How to Calculate a System's Memory Requirement for Model 3000 This example shows how to compute the memory requirement for a system with 16 terminals, 4 ghosts and 4 printers; or standard configuration number 3 in table 6. Thirteen SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg048 of the terminals are dedicated to running BASIC applications: accounts receivable, accounts payable, payroll, and word processing. The remaining terminals are used to run the utilites, the commands, and the Informix database application. Some of the applications use ghost tasks to output reports to printers. STEP 1 thru STEP 5: Add these numbers to compute "memory required" 230 KB Base operating system 99 KB Table space for base system 53 KB O.S. dynamic work space for base system 2 KB Hash table space for directory cache entries (tables 10G and 10H) 16 KB Hash table space for disk buffers (tables 10G and 10H) 41 KBX14 Allowance for table space for 14 additional users (total of 16 users/terminals) 41 KB*4 Allowance for table space for 4 ghost tasks 2 KB*3 Allowance for table space for additional printers 1.7 KBX49 Allowance for dynamic work space for 14 additional users ("procs" - base "procs") 100 KB Allowance for system processes 30 KB*3 Allowance for concurrent printing to the 3 additional printers 160 KBX3 Allowance for the BASIC interpreter and for the utilities/commands/Informix 15 KB*3 Allowance for concurrent terminals 60 KBX13 Allowance for 13 concurrent basic applications 64 KB*4 Allowance for 4 ghost tasks TOTAL = 2979 KB = "memory required" STEP 6: Compute "memory needed" For adequate system performance with frequent swapping of applications tasks and a reduced number of disk buffers: "memory needed" = 2979 KB * 0.7 = 2085 KB or 2 memory boards For good system performance with very little swapping: "memory needed" - 2979 KB * 1.0 = 2979 KB or 3 memory boards For best system performance with much caching: "memory needed" = 2979 KB * 1.3 = SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg049 3872 KB or 4 memory boards The approximate method of determining a system's memory requirement (section 6.1 and Table 6B) shows that a system with 16 users (terminals), 4 printers, and 4 ghost tasks needs 3 Model 3000 1 MB memory boards. The calculation method, descirbed in this section shows that such a system will have different performance characteristics depending on the number of boards (i.e. either 2,3, or 4) the system has. 7.2 Calculating BOSS/IX Table Space and Dynamic Work Space This section describes how to calculate the size of the operating system dynamic work space needed by any configuration. 7.2.1 Model 2000 The calculation method (section 7.1.1) is accurate if the system's configuration parameters are set according to Table 6E. If the BOSS/IX parameters are not set according to Table 6E, use the method described in this section to calculate the amount of memory needed for table space and dynamic work space. Table 7A shows the amount of memory allocated for each operating system configuration parameter; it shows the parameters for the base system configuration; it shows how the 34 KB value for table space, used in section 7.1.1, was calculated; and it shows the parameters and total table space required for the example system depicted in section 7.1.1. To determine the table space for any configuration multiple the value of each configuration parameter by its corresponding memory allowance (see column 1, table 7A). Next, add the result of these calculations (see column 2). The result is the allowance for table space. To determine the memory allowance for operating system dynamic work space (i.e. unswappable memory) use the following formula: "dynamic memory" (bytes) = (17 + ("opens" / 4) + (("procs" * 2636) /512 / 2)) * 512 The variables in this formula from left to right are: 17 - the number of 512 byte pages for miscellaneous operating system space "fds" - the number of open files configured "procs" - the number of processes configured 2636 - the size (bytes) for each process's user area / 512 - for converting into 512 byte pages / 2 - one-half the number of pages * 512 - for converting pages into bytes For the base configuragion the dynamic memory allowance is: "dynamic memory" (bytes) = 17 + (60/4) + ((16 * 2636 /512/2)) * 512 = 37472 bytes or 37 KB SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg050 For the example system (see section 7.1.1) the memory allolwance is: "dynamic memory" (bytes = 17 + (97/4) + ((27 * 2636) / 512/2)) * 512 = 56706 bytes or 55 KB or 37 KB (base size) + 11 * 1.6 KB (extra procs) = 55 KB NOTE: 1.6 is obtained by (55-37) / 11, based on 11 additional "procs", (27-16). NOTE: The operating system dynamic work space -- nick- named unswappable memory -- is a vital work area for the operating system. Within this work area is the process environments (i.e. user area or "uarea") for all active process in the system. Also within this area is printer input and output buffers, ISAM key and dictionary information, and other operating system structures which get dynamically allocated or de-allocated depending on system load. 7.2.2 Model 3000 The calculation method (section 7.1) is accurate if the system's configuration parameters are set according to Table 6F. If the BOSS/IX parameters are not set according to Table 6F, use the method described in this section to calculate the amount of memory needed for table space and dynamic work space. Table 7B shows the amount of memory allocated for each operating system configuration parameter; it shows the parameters for the base system configuration; it shows how the 98 KB value for table space, used in section 7.1.2, was calculated; and it shows the parameters and total table space required for the example system depicted in section 7.1 To determine the table space for any configuration multiply the value of each configuration parameter by its correspondsing memory allowance (see column 1, table 7B). Next, add the result of these calculations (see column 2). The result is the allowance for table space. To determine the memory allowance for operating system dynamic work space (i.e. unswappable memory) use the following formula: "dynamic memory" (bytes) = (49 + ("fds" / 4) + (("procs" * 2704) / 512 / 2)) * 512 The variables in this formula from left to right are: 49 - the number of 512 byte pages for miscellaneous operating system space "fds" - the number of open files configured "procs" - the number of processes configured SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg051 2704 - the size (bytes) for each process's user area / 512 - for converting into 512 byte pages / 2 - one half the number of pages * 512 - for converting pages into bytes For the base configuration the dynamic memory allowance is: "dynamic memory" (bytes = 49 + (60/4) + ((16 * 2704) / 512 /2)) * 512 = 54400 bytes or 53 KB For the example system (see section 7.1.2) the memory allowance is: "dynamic memory" (bytes) = (49 + (218/4) + ((65 * 2704) / 512 / 2)) * 512 = 140872 bytes or 138 KB or 36.6 LB (base size) + (49 * 1.7 KB) (extra procs, 65-16) = 120 KB NOTE: 1.7 is obtained by 138-53) / 49, the additional "procs" (65-16). NOTE: The operating system dynamic work space -- nick- named unswappable memory -- is a vital work are for the operating system. Within this work area is the process environments (i.e. user area or "uarea") for all active process in the system. Also within this area is printer input and output buffers, ISAM key and dictionary information, and other operating system structures which get dynamically allocated or de-allocated depending on system load. ________________________________________________________________________ :BOSS/IX :mem :param.s : total :param.s : total : Memory for : :PARAMETERS :used :for base: memory :for : memory : each : (set by :for :config- : for base :example : for : additional: : : "vconf") :each :uration : system :system *:example :---------------: : :param.: system : (bytes) : : system :USER:GHOST:PRTR: : :(byts): : : : (bytes): : : : :___________:______:________:__________:________:________:____:_____:____: :buffers=...:..594.:.....20.:....11880.:.....32.:..19008.:2376:.....:....: :printers=..:..906.:......1.:......906.:......2.:...1812.:....:.....:.906: :procs=.....:..324.:.....16.:.....5184.:.....27.:...8748.:.972:..324:.324: :tsegs=.....:...24.:.....16.:......384.:.....22.:....528.:..40:.....:....: :locks=.....:...40.:.....74.:.....2960.:.....94.:...3760.:.200:..200:....: :ibsize=....:..128.:........:......256.:........:....640.:.128:.....:....: :tbsize=....:...64.:........:......128.:........:....320.:..64:.....:....: :mfsys=.....:..424.:......3.:.....1272.:......3.:...1272.:....:.....:....: :lus=.......:...44.:....136.:.....5984.:....224.:...9856.:.800:..880:.264: :fds=.......:...92.:.....60.:.....5520.:.....97.:...8924.:.736:..920:.172: :eventcalls=:...20.:.....16.:......320.:.....95.:...1900.:..32:.....:....: :-----------:------:--------:----------:--------:--------:----:-----:----: :TOTALS : -- : -- : 32388 : -- : 52590 :5148: 2144: 982: : : : : : : 51 KB :5 KB: 2 KB:1 KB: :________________________________________________________________________: SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg052 NOTES: * See section 6.2, Table 6E. It explains how the parameter values (columns 2 and 3) for the base system and example system were derived. Table 7A BOSS/IX Operating Parameters and Memory Requirements (Table Space) for Model 2000 _______________________________________________________________________________ ___________________________________________________________________________ :BOSS/IX :mem :param.s : total :param.s : total : Memory for : :PARAMETERS :used :for base: memory :for : memory : each : : (set by :for :config- : for base :example : for : additional: : : "vconf") :each :uration : system :system *:example :------------------: : :param.: system : (bytes) : : system : USER :GHOST :PRTR: : :(byts): : : : (bytes): : : : :___________:______:________:__________:________:________:______:______:____: ** :buffers=...:..594*:....128.:....76032*:...1280.:.760320*:38016*:38016*:....: :printers=..:..906.:......1.:......906.:......4.:...3624.:..--..:..--..:.268: :procs=.....:..324.:.....16.:.....5184.:.....65.:..21580.:..996.:..332.:.332: :tsegs=.....:...24.:.....16.:......384.:.....44.:...1056.:...48.:......:....: :locks=.....:...40.:.....74.:.....2960.:....164.:...6560.:..200.:..200.:....: :ibsize=....:..128.:......2.:......256.:.....16.:...2048.:..128.:......:....: :tbsize=....:...64.:......2.:......128.:.....16.:...1024.:...64.:......:....: :mfsys=.....:..424.:......3.:.....1272.:......4.:...1696.:......:......:....: :lus=.......:...44.:....136.:.....5984.:....556.:..24464.:..880.:..880.:.264: :fds=.......:...92.:.....60.:.....5520.:....218.:..20056.:..736.:..920.:.172: . :eventcalls=:...20.:.....16.:......320.:.....56.:...1120.:...40.:..100.:....: :dirc=......:...48*:.....64.:.....3027*:....338.:..16224*:..384*:..480*:.96*: :-----------:------:--------:----------:--------:--------:------:------:----: :TOTALS : : : 102018*: : 859792 :41492*:40928*:1132: :excluding : -- : -- : or : -- : or : or : or : or : :hash tables: : : 99 KB : : 839 KB*:40 KB*:40 KB*:1.1K: :___________________________________________________________________________: :TOTALS : : : : : : : : : : : -- : -- : 101 KB : -- : 853 KB :41 KB :41 KB :2 KB: :hash tables: : : : : : : : : :___________________________________________________________________________: Table 7B BOSS/IX Operating Parameters and Memory Requirements (Table Space) for Model 3000 * Excludes hash table size which must be calculated separately based on the number of entires requested, then added to the total system requirement. ** Size, number of calculation differs from Model 2000 _______________________________________________________________________________ __________________________________________ | | | | Number of | | | Entries | Memory | SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg053 | Requested | Required | |_______________________|__________________| | through 63 | .5 KB | | | | | 64 through 127 | 1 KB | | | | | 128 through 255 | 2 KB | | | | | 256 through 255 | 4 KB | | | | | 512 through 1023 | 8 KB | | | | | 1024 through 2047 | 16 KB | | | | | 2048 through 4095 | 32 KB | | | | | 4096 through 8191 | 64 KB | | | | | 8192 through 16383 | 128 KB | |__________________________________________| This table is used to obtain the amount of memory needed for hash tables for either the 'buffers' or 'directory cache' operating parameters (see Table 7B). The per entry charge is not included here and must be added to the value from this table. Table 7C Memory Required for Hash Tables _______________________________________________________________________________ 8.0 New and Updated Manuals for Level 7.3A M6211A BOSS/IX (7.3) User Reference Manual M6227A BOSS/IX (7.3) Technical Reference Manual M6201A MAI 2000 User Guide M6202A MAI 3000 User Guide M0053A Universal Printer Driver Reference Manual M6360A MAGNET BOSS/IX User Reference Manual M6262A BB86 Reference Manual M6353C BOSS/IX TBC (2780/3780) User Reference Manual M6352A FTF Users Reference Manual (updated) M6354D Intersystem Transport Manual (updated) M0053A Universal Printer Driver Reference manual (new) M7510A Business DATA System Support Manual (new) M7511A Business DATA Report Program Generator User Guide (updated) SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg054 M6204A Diagnostics Manual (update) 9.0 Lowest Acceptable Revision Levels (LARL) LOWEST ACCEPTABLE 2000/3000 PCB'S P/N REV. LEVEL --------------- ------- ----------------- CMB, CENTRAL MICROPROCESSOR BOARD, 16 BIT 903441 AU 128K/256K MEMORY 903368 A 4 WAY CONTROLLER 903390 * W MCS STREAMER CONTROLLER 903406 Y LAN, LOCAL AREA NETWORK CONTROLLER 903405 D WDC WINCHESTER, ADAPTER BOARD 903439 B ADAPTEC BOARD 907649 E POWER SUPPLY ASSEMBLY 907472 E 1BOARD WINCH. CONTROLLER 903496 R 3000 POWER SUPPLY 907897 E CMB 32 BIT D.S.C 903593 U 1MB MEMORY 903533 A 8-WAY CONTROLLER 903577 F MMB 400650 L 4MB MEMORY 903575 B ORIGINATOR: Pamela Thatcher SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB031 Pg055 FIB 00032 12/29/87 *** Release of MAI 1800 and 7.2N O.S. [ WPS 408 ] *** Level 7.2N BOSS/IX operating system and its related software products are now available for the new MAI 1800 system. The 7.2N operating system release contains the same functionality as the level 7.2A software release for the MAI 2000 system except for a few minor changes and additions to commands and utilities. There are also differences between the MAI 1800 and MAI 2000 systems in terms of printer support. For details on this release and for installation/upgrade instructions, please refer to the MAI 1800 Software Announcement #152. ORIGINATOR: Dan Wenzel SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB032 Pg001 FIB 00033 12/29/87 *** MAI 1800 Software Announcement [ WPSS 152 ] *** 1.0 INTRODUCTION Level 7.2N BOSS/IX operating system and its related software products are now available for the new MAI 1800 system. The 7.2N operating system release contains the same functionality as the level 7.2A software release for the MAI 2000 system except for a few minor changes and additions to commands and utilities. These changes and additions are outlined in section 1.4. The internal operating system has been modified to work with the Intel 80286 microprocessor. BOSS/IX 7.2N was designed to allow both BOSS/IX and MS-DOS to reside on the MAI 1800 in their respective unique partitions on the hard disk. This arrangement allows the user to operate in either the single-user MS-DOS environment or the multi-user BOSS/IX environment, but not concurrently. The partition sizes are user configurable with an MS-DOS maximum of 32MB. The MAI 1800 is a powerful, IBM PC/XT/AT-compatible, multiuser, business computer based on the 16-bit Intel 80286 microprocessor. The MAI 1800 system uses industry standard 7-bit (low order) ASCII, the same as the MAI 2000. This software announcement contains general and specific information about: o The BOSS/IX 7.2N operating system o System start-up and shutdown o Software installation o System configuration o Hardware considerations o Set-up procedures o Cabling o Back-up & restore techniques o System customization o System security o Helpful hints and useful information o A summary of available documentation For ordering information, refer to the appropriate Marketing Announcement. Copyright 1987 by MAI Basic Four, Inc. All rights reserved. MAI 1800 Software Announcement TABLE OF CONTENTS 1.0 INTRODUCTION 1.1 Primary 7.2N Software Features 1.2 Supported Hardware 1.3 Supported Media 1.4 Differences Between 7.2N and 7.2A SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg001 2.0 SYSTEM START-UP AND SHUTDOWN 2.1 System Start-up 2.1.1 From Floppy Disk Drive 'A' 2.1.2 From Active Partition on Hard Disk Drive 'C' 2.1.2.1 A Standard Load from Active BOSS/IX Partition 2.1.2.2 An Alternate Load from Active BOSS/IX Partition 2.1.2.3 A Standard Load from Active MS-DOS Partition 2.2 System Shutdown 3.0 INSTALLATION 3.1 System Set-Up 3.2 Hard Disk Preparation 3.3 Installation and upgrade procedures for BOSS/IX 3.3.1 Installing BOSS/IX and MS-DOS on the Same Hard Disk 3.3.2 Initial BOSS/IX Installation 3.3.3 Second Hard Disk Preparation 3.3.4 BOSS/IX System Upgrade/Reinstall Procedure 3.3.5 BOSS/IX Configuration Record Installation 3.3.5.1 The 'iconf' Command 3.3.5.2 Configuration Record Request Sheet 3.4 Installing MS-DOS 3.4.1 Create MS-DOS Partition 3.4.2 Formatting and Copying MS-DOS to the Hard Disk 4.0 SYSTEM HARDWARE 4.1 Base Hardware Configuration 4.2 System Hardware Set-Up 4.3 Terminal and Printer Support 4.3.1 Terminal Support 4.3.2 Printer Support 4.3.2.1 Printer Configuration 4.4 Port Configuration 4.5 System Cabling SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg002 5.0 BACK-UP AND RESTORE 5.1 Back-up and Restore under BOSS/IX 5.1.1 Via MCS (1/4" Magnetic Cartridge Streamer Tape) 5.1.2 Via 1.2MB Floppy Diskette 5.1.3 Filesystem to Filesystem 5.2 Back-up and Restore under MS-DOS 6.0 CUSTOMIZATION 6.1 Operating System Parameters Customization 7.0 MEMORY USAGE 7.1 Approximating a System's Memory Requirement 7.2 Calculating a System's Memory Requirement 8.0 SECURITY 8.1 System Security 8.2 File Security 8.3 Product Security 9.0 DUMP PROCEDURE 9.1 Configuring the System To Dump 9.2 Saving The Dump To Floppy Directly 10.0 CAUTIONS AND WARNINGS 11.0 DOCUMENTATION 12.0 27xx/37xx BATCH EMULATION (TBC) 12.1 Hardware/Software Requirements 12.2 Hardware Installation 12.2.1 MBF ICC/186 Communications Controller 12.2.2 Cables 12.2.3 Recommended Modems and Automatic Calling Units 12.3 Software Installation 12.3.1 TBC Installation 12.4 Configuration 12.4.1 System Configuration 12.4.2 Port Configuration SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg003 12.5 Operation 12.5.1 Menu Access 12.5.2 Command/BASIC Access 12.5.3 Program Access 12.6 For Your Information 12.7 Documentation NOTE: Throughout this Software Announcement you will see reference made to and 'RETURN'. These prompts are used interchangeably and refer to the carriage return key. 1.1 Primary 7.2N Software Features o Business BASIC - 7.2A functionality. BASIC supports ghost tasks, called programs and public programs. o Spooler support o Slave printer support o Menu driven utilities o Command language support 1.2 Supported Hardware o CCA - MAI 1800 Intel 80286 Microprocessor with selectable 6Mhz and 10Mhz clock speeds. System Serial Number security device. o Hard Disk support is as follows: Disk Disk Number of Number of Bytes Type Capacity Cylinders Per Cylinder 2 20MB 614 34,816 3 31MB 614 52,224 18 58MB 976 60,928 9 115MB 899 130,560 NOTES: 1. Hard disks used on the 1800 system must have less than 70 defects and cylinder 0 must be error free. 2. The MS-DOS setup and test diskette must be used to store the disk drive parameters (e.g., number of heads, number of cylinders) into battery-backed RAM (a type of non-volatile read/write system memory). This memory contains all of the system parameters (e.g., system date & time, hard disk & floppy disk types, system speed, expansion memory size, and primary display type). System setup is explained in section 3.1. o 1.2MB capacity Floppy Diskette drive o Monochrome or Color monitor (system console) SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg004 o (Optional) 60MB capacity 1/4" tape drive o (Optional) 1 or 2 8-way boards. These multi port boards are only supported while operating under BOSS/IX. o Serial/parallel port boards. One board is required and comes standard with the system. A second board may be added if the system does not have any 8-ways installed. 1 The configuration range of the MAI 1800 is as follows: ________________________________________________________________________ | | | | | |_______________________|_Minimum__|_Maximum_|________Comments_________| | | | | | | Memory | 640KB | 2.6MB | Only 640KB used under | | | | | MS-DOS. | | | | | | | Hard disk drives | 1 | 2 | | | Hard disk capacity | 31MB | 230MB | see notes | | | | | | | | | | | | Floppy disk drive | 1 | 1 | | | Floppy disk capacity | 1.2MB | 1.2MB | see notes | | | | | | | Disk controller | 1 | 1 | Supports 2 hard disks | | | | | & 2 floppy drives. | | | | | | | 1/4" MCS Tape drive | 0 | 1 | Requires controller | | 1/4" tape controller | 0 | 1 | | | 1/4" tape capacity | 60MB | 60MB | | | | | | | | System Monitor | 1 | 1 | Monochrome or color. | | | | | | | Keyboard | 1 | 1 | U.S. (Keycap sets are | | | | | available for inter- | | | | | national languages) | | | | | | | Serial & Parallel | 1 | 2 | Only 1 parallel | | port controller | | | port supported | | | | | | | 8-port controllers | 0 | 2 | 8-way ports not | | | | | accessible from MS-DOS | | | | | | | serial ports | 1 | 17 | | | | | | | | Display Terminals | 0 | 17 | Only BOSS/IX | | | | | applications supported | | | | | | NOTES: Because of power supply restrictions, the disk controller will support a total of 3 disk drives. Any combination of 2 hard disks and 1 floppy disk may be used with the following constraints: a) The 1.2MB high-density floppy drive must be configured as drive A. Maximum of 1-1.2MB floppy drive supported under BOSS/IX. BOSS/IX does not support a 360KB floppy drive. b) There must be at least 1 floppy drive and 1 fixed drive. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg005 c) Maximum of 2 hard disks. Hard disk configurations include 20, 31, 58, and 115MB. The 20MB hard disk is not supported as drive 0. 2 1.3 Supported Media o Floppy (1.2MB high capacity diskettes are required) A 1.2MB floppy diskette drive is required on all systems. A "save/restore" floppy written on a MAI 2000 will not be readable or writeable by the MAI 1800 and vice-versa. o Tape (60MB 1/4" cartridge streamer) MT4406 1/4" streamer tape is supported as a backup/restore media. "save/restore" tapes written on an MAI 2000/3000 will not be readable or writeable on an MAI 1800 and vice-versa. Model MT4403 1/4" streamer tape drive is not supported. 1/4" streamer tape is not supported as a bootable media. 1.4 Differences Between 7.2N and 7.2A 1) The 1800 system swapper space has been reduced from 2MB to 1MB. The boot partition has been reduced from 2MB to 1.5MB. Default partition sizes are: Boot partition 1.5MB Swapper partition 1.0MB Root partition Remainder of disk(minus MS-DOS partition size) 2) The MAI 1800 has a real time clock. The system administrator is not prompted to set the system date or time at boot time. The real time clock can be set with the BOSS/IX 'date' and 'time' commands or the MS-DOS setup program. 3) The MAI 1800 doesn't support a "virtual" console as defined for the MAI 2000/3000 series. On the 2000/3000 series, the console can be on the first serial port or on the CMB. The MAI 1800 console is the "system monitor". The system monitor can be either monochrome or color. The monochrome monitor doesn't support underline and reverse video at the same time. The color monitor doesn't support underline. The system monitor doesn't support a slave printer. 4) The following terminals do not have mnemonic support: VDT7250 S10 ODT *** Refer to Section 4.3.1 for a list of supported terminals. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg006 5) Non-supported printers are as follows: _________________________________________________________ | centronics | | model serial MBF serial parallel | |_______________________________________________________| | PT4201 * | | PT4203 * | | PT4210 * * | | PT4211 * * | | PT4212 * * | | PT4214 * * | | PT4215 * | | PT4216 * | | PT4217 * | | PT4218 * | ________________________________________________________| *** Refer to section 4.3.2 for a list of supported printers 6) The MAI 1800 uses the Intel 80286 microprocessor whereas the 2000/3000 use Motorola microprocessors. The way the Intel 80286 stores word (integer) values in memory is Least Significant Byte (LSB) followed by Most Significant Byte (MSB). This is opposite from the way the Motorola microprocessors write word data to memory. For instance, if the decimal value 18 (hex 12) was stored as a word at memory location 436, it would appear as follows: | memory location micro | 436 437 ---------------------------- Intel | 12 00 Motorola | 00 12 This has an impact in that written "Save/Restore" media (tape and floppy) are not transportable between the 1800 and 2000/3000 series even if the same or a compatible device peripheral is used. The byte sex issue will normally not effect the BASIC programmer using standard ASCII string and numeric variables. 4 ATP 4.0 is available to transport data and BASIC files between the 1800 and the following MBF Systems: o 13xx systems on minimum 4.5B O/S release o 1500 systems on minimum 6.3A O/S release o 2000/3000 systems on minimum 7.3A O/S release o MPx systems on minimum 8.6B O/S release NOTE: ATP 4.0 is not compatible with any other level of ATP (i.e., 1.0, 2.0, or 3.0). Both systems must be on ATP 4.0 to make initial connection. Refer to the ATP 4.0 software announcement for details. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg007 The following section lists differences involving commands, utilities and BASIC: NEW COMMANDS: badtrk - Used to create a bad/alternate track list for hard disks. This command is automatically executed during system installation. fdisk - Used to support co-existence with MS-DOS. NOTE: Rather than using 'fdisk' to change partitions, the BOSS/IX partition can be left active. MS-DOS may be booted from hard disk with the BOSS/IX loader without activating the MS-DOS partition. This can be accomplished by doing an alternate load with the BOSS/IX loader active. When prompted to select boot device and system files enter 'dos', . The loader boots MS-DOS from the first MS-DOS partition found on the hard disk. makeupdxlate - Used to create a new type of printer translation table from a text file. This command replaces the 7.2A pted command. indconvert - (INT product) Indconvert (index convert) will convert the MAI 2000 based index '.ind' files to MAI 1800 format. The text '.txt' files associated with utility support are in ASCII format and do not require any special conversion. 5 The procedure to convert utility support files is as follows: o Be sure the INT product is installed o copy *.ind and *.txt files from the MAI 2000 to MAI 1800 using ATP 4.0. o Enter the command 'indconvert < infile.ind > outfile' DO NOT convert text files as the results are unpredictable. MODIFIED COMMANDS: basic - There is a new limit of 213 on start size. A start size of 200 is the recommended maximum, since any size above 200 leaves very little room for opening files, etc. The basic 'C' library is not supported. lpmaint - New mnemonic processing and character translation functionality has been added. lpr - New mnemonic processing and character translation functionality has been added. lpstat - New mnemonic processing and character translation functionality has been added. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg008 start - The start command initializes serial ports, activates despoolers and activates processes on terminals. This command has been changed to handle the non-support of a "virtual" system console. The system monitor is the only possible system console available on the MAI 1800. sysinfo - Used to display the current hardware configuration contained in system memory. This configuration is initialized and changed using the MS-DOS 'setup and test' diskette. 'sysinfo' also displays the system serial number and the revision level of the booted operating system. usb - This command displays and updates the disk "superblock" and is used to define disk partitions. It will be possible for BOSS/IX and DOS partitions to co-exist on the same disk. However, BOSS/IX must be the first partition on the disk. The 'usb' command has been modified to additionally support non-BOSS/IX partitions. 6 COMMANDS NOT SUPPORTED: kychk - 'frepair' should be used to repair keyed files. makesta - Not needed at this time since magnet is not supported. pted - Replaced by makeupdxlate. MODIFIED UTILITIES: Filesystem and Disk Utilities: Copy Diskette Utility - This utility copies a floppy to a Winchester drive and copies the data contained on the Winchester to a newly inserted floppy. Filesystem Error Analysis Utility - The "fsdbug" utility is an interactive tool used to repair the file system. This utility is not supported under 7.2N. The non-interactive command 'fschk' is invoked automatically after a system crash. 'fschk' handles all BOSS/IX corruption problems. Free Space Analysis Utility - Since it is possible for both BOSS/IX and DOS filesystems to reside on the same disk, it is necessary to point out that this utility will only report free space information pertaining to the BOSS/IX partition. Printer Utilities: Changes have been made to support printer mnemonics and character translation in a manner consistent with 7.3A. Two new directories have been released in 7.2N that are not present on 7.2 A, B, C or D releases. These directories are '/etc/ptrtbl' and '/etc/ptrxlt'. These directories contain the Printer Definition Files (PDF's for mnemonic processing) and the Printer Character Translation Files respectively. Save and Restore Utilities: SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg009 Diskette - the diskette save and restore utilities have been modified to support higher capacity (1.2 meg) diskettes that are supplied with the MAI 1800. These save/restore diskettes cannot be used to transfer information to a MAI 2000 or vice-versa. BASIC Program Utilities: No changes. 7 Communications Utilities: ATP 4.0 is supported on 7.2N. ATP 4.0 is the only released communications product at this time. See section 12 for future support of TBC (27xx/37xx). System Utilities: Port Configuration Utility - Virtual console and split baud rate are not supported. Terminal and printer model numbers are now displayed. Printer types are no longer displayed. 8 2.0 SYSTEM START-UP AND SHUTDOWN 2.1 System Start-up NOTE: Do not cycle A.C. power when the floppy diskette is installed and the disk drive lever is in the locked position. The MAI 1800 can be booted from floppy disk or from hard disk. Booting from 1/4" cartridge tape is not supported. The MAI 1800 can be booted with either the MS-DOS or BOSS/IX Operating System. The system start-up to be used depends on which Operating System you wish to run and the device on which that Operating System is located. It can reside on Floppy disk drive 'A' (the top floppy drive on the system) or the Active partition on Hard disk drive 'C' (the first hard disk drive on the system). When the system is powered up, it will automatically get the Operating System from Floppy drive 'A', if there is a bootable diskette (a diskette that contains a loader and an Operating System) in the drive and the disk drive door is closed. If there is a non-bootable diskette in Floppy drive 'A' at boot time and the disk drive door is closed, an error will be produced and you will be required to re-boot the system. If there is no diskette in Floppy drive 'A' or the floppy drive door is not closed, the system will automatically boot from the active partition on the Hard disk drive 'C'. If there is no active partition on the hard disk or the hard disk partition does not contain an Operating System, an error will be produced or the system may display unreadable characters on the Monitor. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg010 If the system is powered up and already has MS-DOS booted, it can be re-booted by depressing and holding down and , then quickly depressing and releasing all three. The system will then use the steps outlined above to boot the system. If the message "ERROR, (RESUME='F1' KEY)" appears, depress to complete the boot. The following are the steps required to boot the desired Operating System from the correct device. NOTE: If this is a new installation, you will need to first boot your system from Floppy drive 'A' by following the procedure outlined below for System start-up from a floppy. You will need to have the "SETUP and TEST' diskette in Floppy drive 'A' at boot time. 9 2.1.1 From Floppy Disk Drive 'A' To boot the system from Floppy drive 'A', perform the following steps: 1. Hold the diskette you wish to boot from with the label facing up and towards you, and insert it into Floppy drive 'A'. Do not put the disk drive lever in the locked position at this time. 2. If the system is powered off, power on the system. If the system has already been booted, depress and hold and then , and depress and quickly release all three keys. 3. Close the diskette locking lever at this time. The system will now boot from the diskette in Floppy drive 'A'. 2.1.2 From Active Partition on Hard Disk Drive 'C' As mentioned above, if there is a diskette in the floppy drive and the door is closed, the system will attempt to boot off the floppy. To boot from the active partition on the hard disk drive 'C', perform the following steps: 1. Ensure that the floppy drive door is open. 2. Ensure that the partition you wish to boot from is Active. To check which partition is Active or to activate a partition perform the following: A. If you are on the BOSS/IX partition, run 'fdisk'. You MUST be in single user mode. At the ADMIN> prompt type 'fdisk', . This program will allow you to activate the MS-DOS partition. You will be required to re-boot the system after running this program and changing the active partition. B. If you are on the MS-DOS partition, run 'fdisk'. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg011 This program will allow you to activate the BOSS/IX partition. In MS-DOS, the BOSS/IX partition is called non-DOS. 10 3. If the system is powered off, power on the system. If the system is already booted, perform the following: o From the MS-DOS partition, depress and hold and , and depress and quickly release all three keys. OR o From the BOSS/IX partition, perform an orderly shutdown (see section 2.2). After performing the shutdown procedure, press when prompted to press 'RETURN' to reboot. The system will now boot from the active partition on Hard disk 'C'. 2.1.2.1 A Standard Load from Active BOSS/IX Partition This procedure can be performed from a power off or power on condition. o If the system is in a power off condition, power on the system. OR o If the system is in a power on condition(after a proper 'shutdown' is performed and a "Press 'RETURN' key to reboot:" prompt is displayed), press . o When prompted to press 'RETURN' to reboot, press . o When prompted to select boot device and system files, press . The system will now boot from hard disk. The standard Operating System and '/etc/conf' configuration file supplied with the software will now be loaded. After the load is complete '/etc/start' will be executed. This will display the system proprietary message. o When prompted to continue with startup, press . Depending on what is configured in the '/etc/conf' file, the '' or '' message is displayed. 11 If a minor error occurs during start-up, SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg012 the error messages are reported in the '/etc/sys.log' file. '/etc/start' checks this file; and, if it contains data, the following message is displayed: An error occurred during system startup. File '/etc/sys.log' contains a description of the errors. Press the 'ESC' key to continue. . . If this message occurs, simply press the key and the ADMIN> prompt will then be displayed. Once at the ADMIN> prompt, you can print the contents of the '/etc/sys.log' file by using the command, 'p /etc/sys.log'. If no errors occurred, the ADMIN> prompt will display immediately. If a severe error occurs, the system will abort the boot process and a system crash message will be displayed. If the '/etc/conf' file is set to "secure mode", a 'Password:' prompt will be displayed before the ADMIN> prompt. If this prompt is displayed, you must enter the system administrator password followed by an . If the '/etc/conf' file is set to "multi mode", 'etc/startup' will be executed after is pressed. This program will startup all of the configured terminals on the system. If a minor error occurs anytime during the boot, the message telling that the error is in the '/etc/sys.log' file will be displayed after '/etc/startup' is complete. To get to the ADMIN> prompt from multi mode requires that you first enter and admin for operator name. 2.1.2.2 An Alternate Load from the BOSS/IX Partition An alternate load may be performed when the system prompts you to select boot device and system files. This allows you to load an alternate operating system (from floppy or wd0) or configuration file. 12 o From a power off condition, Power on the system. OR o From a power on condition, perform the following if the system is not in a shutdown condition: - Perform an orderly shutdown (see Section 2.2). - When prompted to press 'RETURN' to reboot, SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg013 press . The 'Select boot device and system files:' prompt is displayed. To load an alternate O.S. or configuration file requires a two part name. If one part is omitted, the default is used. Part one of the system file is a loadable O.S. file. '/sys/bossix' and 'dos' are examples of loadable O.S. files. Part two is a system configuration file. '/etc/conf' and '/etc/boot.conf' are examples of system configuration files. These two parts when entered together are separated by a comma, ",". If the first part is entered by itself no comma is required and the system will default to the '/etc/conf' file, example: '/sys/bossix'. If the second part is entered by itself, for the case where you wish to root to the boot partition, the comma must precede the file name, example: ',/etc/boot.conf'. In the second case the system will default to the default O.S. '/sys/bossix'. 2.1.2.3 A Standard Load From Active MS-DOS Partition The system can be booted from either a power off or a power on condition. From a power off condition: 1. Be sure there is no diskette in disk drive A. If there is, remove it. 2. Make sure that power to the system monitor is turned on. 3. Turn the power switch (on the back, right of the CCA) to the on position. 13 From a power on condition (only when the MS-DOS partition is active): 1. Hold down the and keys and press the key. The system begins with a series of self-tests, including a check of the memory and the system setup record. If all goes well and the setup record appears correct, the operating system is loaded and the system boots. NOTE: The MS-DOS startup routine can be changed by creating and modifying the AUTOEXEC.BAT file in the root directory. This is described in the MS-DOS Reference Manual. The default startup routine, described here, is executed in the absence of AUTOEXEC.BAT. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg014 Once the system boots, the current date information and 'ENTER TODAY'S DATE...MMDDYY' prompt is displayed. o If the displayed date is incorrect, enter the correct date and press . If the date is correct press . The current time information and 'ENTER CURRENT TIME...HHMM' prompt is displayed. o If the displayed time is incorrect, enter the correct time and press . If the time is correct press . After the date and time have been entered, the C>prompt is displayed. NOTE: The BOSS/IX partition can be left active. MS-DOS may be booted from hard disk without activating the MS-DOS partition. This can be accomplished by doing an alternate load with the BOSS/IX loader active: o If the system is powered off, power on the system. OR o If the system is powered on, perform an orderly shutdown (see Section 2.2). When prompted to press 'RETURN' to reboot, press . 14 o When prompted to select boot device and system files enter 'dos', . The system will now boot the MS-DOS operating system. MS-DOS will operate as if the MS-DOS partition were active. 2.2 System Shutdown WARNING: When the BOSS/IX partition is active it is very important that the system be shutdown properly. Failure to follow these procedures may result in damage to the filesystem, and may cause a loss of data. The system can only be shutdown by the system administrator. Shutdown can be initiated from any terminal if the system is in multi-user mode. In single user mode only the system console is active. To shutdown a system which automatically boots into multi-user mode, you must be logged in as the system administrator ( ADMIN> ). At the ADMIN> prompt type 'shutdown x message ' and press , where 'x' is the number in minutes until the system shutdown occurs and 'message' is any message you wish to display during the shutdown. The message is optional. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg015 If the system boots into single-user mode and is in single-user mode, enter + 'D'. The system then prompts 'single, multi, or shutdown?' At this prompt enter 'shutdown', . If the system boots into single-user mode and is in multi-user mode, use the command 'shutdown x message', where 'x' is the number of minutes until shutdown and 'message' is any message you wish to display during the shutdown. The system will then shutdown into single-user mode, at which point enter + 'D' and follow the prompts described in the above paragraph. It is now safe to power off or re-boot the system. No special shutdown procedure is required when running under MS-DOS. When running MS-DOS, you can turn off the power whenever any particular program has completed executing. 15 NOTES: 1. Read the 'CAUTIONS AND WARNINGS' in section 10.0 2. BOSS/IX must be installed on the first partition. Before installing or upgrading the system it is recommended that you read these instructions completely. 3. Ensure that you have removed any write-protect tabs from the product diskettes before proceeding with installation. The hard disk on the MAI 1800 can be partitioned and set up so that the system can be booted and run as either a single-user MS-DOS system or a multi-user BOSS/IX system. This section describes the procedure for installing BOSS/IX and MS-DOS on a one or two fixed disk system, beginning with preparing the fixed disk(s). If the system is going to be used only with BOSS/IX, this procedure must still be followed whereas the section on installing MS-DOS may be skipped. Before continuing with this procedure ensure that you have the following diskettes: o MAI Setup and Test Diskette o MS-DOS 3.1 (2 floppies) Required only if MS-DOS is going to be installed. o BOSS/IX BOOT/INSTALL floppy diskette o Configuration record diskette o EOS products o EUT products o EBS products The EOS, EUT, and EBS products and the configuration record may be contained on a single 1/4" cartridge streamer tape. In addition to the above media you will need the bad track information for your hard disk(s). This information is contained on a label attached to the underside of the MAI 1800 CCA and on the disk drive SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg016 case. If for some reason the label on the CCA is missing, you will need to remove the cover and read the list from the disk drive case. The relevant information is the Cylinder and Head number. When you have the proper diskettes and have obtained the bad track information, you are ready to begin the installation. 16 3.1 System Set-up This section describes the procedure to tell the system how many hard disk drives are installed and what type they are. This must be done regardless of the combination of operating systems being installed, whether it be a system partitioned between BOSS/IX and MS-DOS or a system dedicated to BOSS/IX. To start, insert the "Setup and Test" diskette in floppy drive A (if your system has two floppy drives, Drive A is the top drive), and boot the system. When the boot is complete, the system will display the Diagnostics Main Menu. The setup program stores a record of certain configuration information in non-volatile battery-backed RAM. This information is required by the system to function properly, whether it is running under MS-DOS or BOSS/IX. The steps required to set up your system are outlined below: 1. Run the setup program from the Diagnostics menu by selecting Option O, 'Run SETUP'. The Setup menu will be displayed. 2. From the Setup menu select Option 0, 'Set Date and Time'. The current date and then time will be displayed. If they are correct, enter an ; if they are incorrect, enter the correct date and time. When the date and time are correct enter 'Y', , this will return you to the 'Setup menu'. 3. From the Setup menu select Option 1, 'SET DISKETTE DRIVE TYPE'. This option will allow you to set your floppy disk drive types. The system will display the drive type for both the floppy drives 'A' and 'B'. The floppy drive types are shown as follows: (Not installed = no floppy configured at that location) HIGH-DENSITY DISKETTE DRIVE - 1.2MB floppy DOUBLE-DENSITY DISKETTE DRIVE - 360KB floppy NOTE: The 360KB floppy drive and 360KB floppy are NOT supported under BOSS/IX. If the information is correct enter a 'Y', . If the information is incorrect enter a 'N', and enter the correct information for the floppy drives. When the information is correct enter a 'Y', . This will return you to the Setup menu. 4. From the Setup menu select Option 2, 'SET HARD DISK DRIVE TYPE'. This option will allow you to set your hard disk drive types. The system will display the drive types. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg017 17 In addition to these drive types, if no drive is configured at a location, it will display 'not installed'. If the information is correct, enter a 'Y', . If the information is incorrect, enter an 'N', , and follow the system prompts to enter the correct hard disk drive information (see section 1.2 for supported drive type information). When the information is correct enter a 'Y', , and this will return you to the Setup menu. NOTE: When changing the hard disk drive information the system will display the drive types followed by a prompt to 'enter selection'. This prompt is for hard disk 'C'. 5. From the Setup menu, select option 3, 'SET SYSTEM SPEED'. This option will allow you to set your system speed and, in addition, will enable or disable the system speed button located on the control panel. The system will display the current configuration for your system's speed options. If these are correct, enter 'Y', . If they are incorrect enter 'N', , and enter the correct information. When the information is correct, enter 'Y', , and this will return you to the Setup menu. NOTE: BOSS/IX is only certified at 'high' speed (10Mhz). Normal system usage will be to set the system speed to 'high' and to 'disable' the system speed button. Some MS-DOS programs may require the 6Mhz clock speed. If MS-DOS is to be used frequently, choose 'enabled' to allow the user to switch between the 6Mhz and 10Mhz system speeds. 6. From the Setup menu, select Option 4, 'SET EXPANSION MEMORY SIZE'. This option will allow you to set system memory expansion. Currently the MAI 1800 supports 1.6MB or 2.6MB of memory. The memory size must be changed according to the amount of memory installed. If the information is incorrect, enter a 'N', , and follow the system prompts to enter the correct expansion memory size. If you have 1 expansion memory board (standard with each system) select Option 2 for 1024KB (1MB). If you have 2 expansion memory boards, select Option 4 for 2048KB (2MB). NOTE: Do NOT include the 640KB of motherboard memory in your expansion memory setup. 7. From the Setup menu, select Option 5, 'SET PRIMARY DISPLAY TYPE'. This option will allow you to set the type of controller your monitor is connected to. The question 'Is a GDA board installed ?' should be answered with a 'Y'. When the information is correct, enter 'Y', , and this will return you to the Setup menu. 18 8. From the Setup menu, select Option 6, 'REVIEW CURRENT CONFIGURATION'. This option will allow you to review the SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg018 existing system setup. If any of the entries are incorrect, return to the Setup menu by entering an and repeating the appropriate steps. If the entries are correct, enter an to return to the Setup menu. 9. To exit the setup program and save the updated configurations select Option 7, 'EXIT SETUP AND SAVE NEW CONFIGURATION'. The system will display the new configuration and prompt you if the entries are correct. If the settings are correct, enter 'Y', . The system will now automatically REBOOT. NOTE: The 'Setup and Test' diskette must remain in drive 'A'. 3.2 Hard Disk Preparation The following outlines the steps required to prepare the hard disk. These procedures must be followed to allow for operating system installation. If your system has two hard disk drives, follow this procedure twice. The first time using drive 'C' and the second time using drive 'D'. 1. From the 'SETUP and TEST' Menu select Option 4, 'Hard disk preparation'. 2. The system will display the Hard disk preparation menu, with a message that no disk drives are selected. Enter Option 0, 'Select drive', from the menu. The system will prompt for drive 'C' or 'D', enter 'C'. The system will now display 'Hard disk drive C: selected'. 3. From the option menu enter Option 2, 'Initialize hard disk'. WARNING: This will destroy all the data on the disk and should only be run the first time the system is installed. If it is required to run this program again, ensure you have a good back-up of your COMPLETE disk, including MS-DOS and BOSS/IX. You will be prompted twice to ensure this is what you wish to do. Enter 'Y' to the first question and to the second. If you do not wish to initialize your disk, enter . 4. When the initialization program is complete, you will be prompted with a message telling you the program is complete and asking you to enter to continue. Enter , and you will be returned to the Hard Disk Preparation Menu. From this menu, select Option 1, 'Enter bad tracks'. 19 5. This step outlines the procedure to spare the bad tracks from the bad track information gathered earlier from the listing on the bottom of the CCA or from the disk drive. If there are no bad tracks listed then no bad tracks were found. The following prompt appears and allows you to enter the cylinder number and head numbers listed on the Hard Error Map: TYPE CYLINDER NUMBER, COMMA, HEAD NUMBER, AND THEN SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg019 PRESS From the bad track list, enter the cylinder number, followed by a comma, the head number, and press ; for example: 49, 3 . If you enter a nonexistent cylinder or head number, you will be prompted that the wrong head or cylinder has been entered and to press to continue. allows you to go back and re-enter the correct numbers. NOTE: If the hard disk capacity is either 58MB or 115MB the following cylinders can't be entered or used: For the 58MB drive, cylinders 978-1024 are invalid. For the 115MB drive, cylinders 901-918 are invalid. After you press to enter the numbers for a bad cylinder, you will be prompted to answer with a 'Y' if the information is correct or an 'N' to cancel the entry. Entering either choice, Y or N, the entry prompt appears again. Continue to enter the data from the Hard Error Map until all the bad track numbers from the list have been entered. When you have finished entering the bad track numbers, press . The system will display a table of the bad tracks you have just entered. You will then be prompted if you wish to save the list. If this list is incorrect, enter 'N' to re-enter the list. If it is correct, enter 'Y' . A message will be displayed telling you to run 'FDISK AND FORMAT TO SPARE BAD TRACKS'. Enter to return to the Hard disk preparation Menu. After entering the bad tracks listed on the CCA or disk drive, it is recommended that a read/write destructive surface scan test be run. This test should detect any potential bad tracks that weren't listed. The test time depends primarily on the hard disk capacity. 20 The destructive test is included on the "Setup and Test" diskette. o From the main menu, select Option 3, 'Hard disk drive test'. o Select Option 0, 'Select drive'. o Select 'C' or 'D' depending on the drive to be tested. o Select Option 4, 'Select destructive test'. o Select Option 5, 'Start testing'. 3.3 Installation and upgrade procedures for BOSS/IX The following steps outline the MAI 1800 BOSS/IX installation procedures. 3.3.1 Installing BOSS/IX and MS-DOS on the Same Hard Disk If you intend to install both BOSS/IX and MS-DOS on the hard disk: 1. Compute the number of cylinders that will be devoted SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg020 to the BOSS/IX partition (see section 1.2 for cylinder information). BOSS/IX overhead is approximately 9MB. All enough room for BOSS/IX overhead, user programs, and user data. 2. Follow the instructions outlined in section 3.3.2 using option B. 3.3.2 Initial BOSS/IX Installation Step 1: Install the boot partition. o Insert the BOSS/IX boot floppy in the diskette drive and close the latch. o Power on the system using the on/off switch located to the rear of the CCA. o When prompted to select boot device and system files, type 'f', . The system will now boot from floppy. o When prompted to continue with system startup press . The install menu will be displayed. o Select menu option 'A' or 'B' depending on the requirements. Option 'A' will install BOSS/IX on the entire hard disk leaving no partition available for DOS. Option 'B' will install BOSS/IX on the first portion of the hard disk. 21 o Type either 'A', . OR o 'B #', . NOTE: # refers to the number of cylinders dedicated to the BOSS/IX partition(see section 1.2 for hard disk information). The hard disk is now being prepared (BOSS/IX bad tracks table set up, partitions created, etc.) and the boot partition is being installed. o After this procedure is complete, the OPTION> prompt will appear. Press + 'D'. Type 'shutdown', . Step 2: Install the configuration record. WARNING: If the configuration record for the system is not installed, you will be able to access the boot partition only. o Remove the floppy diskette. o When prompted to press 'RETURN' to reboot, SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg021 press . o When prompted to select boot device, press . The system will now boot to the boot partition. o When prompted to continue with startup, press . The system will display the ADMIN> prompt. o Insert the configuration floppy into the respective drive. o Type 'confinstallf', . o The message 'insert CONFIGURATION media into drive' is displayed. Press to proceed with installation. The configuration record is now installed. o Remove the configuration floppy. 22 Step 3: Install the Operating System. NOTE: The following steps will create the filesystem on the root partition and install the operating system files. If EOS is on the floppy disk base set, you must insert the #1 disk first (See step 7 for a breakdown of the BOSS/IX floppy diskette set). You will then be prompted to enter each remaining disk one by one. The EOS floppy disks MUST be inserted in the proper sequence. o Insert the EOS floppy diskette #1 in the drive or insert the MCS cartridge tape into the tape drive. o Type 'osinstall fd0', (for floppy), or type 'osinstall cs', (for 1/4 " streamer tape). o The message 'This procedure will destroy all previous data on the root partition. Press RETURN to continue (Escape to abort)...' is displayed. Press . Step 4: (OPTIONAL) Setup second hard disk This procedure prepares hard disk /dev/wd1 to be used as a single mountable filesystem. Make sure that the hard disk has been properly inititialized and setup. Refer to sections 3.1 & 3.2 for details. o Type 'prepdisk1', . Step 5: Shutdown the System SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg022 o Press + 'D'. o Type 'shutdown', . o Remove any diskette from the floppy drive. Step 6: Boot the system from the hard disk o When prompted to press 'RETURN' to reboot, press . o When prompted to select boot device, press . The system will now boot from hard disk. 23 o When prompted to continue with startup, press . The system will display the ADMIN> prompt. Step 7: Install Desired Software Products NOTE: The MAI 1800 software products base system is contained on either one 1/4" cartridge tape or eleven floppy diskettes. The eleven floppies are labeled as base 1 of 11 ... base 11 of 11. The base system is differentiated as: PRODUCT BASE DISKETTE(S) EOS 1 and 2 (of 11) EUT 3 thru 6 (of 11) EBA 7 (of 11) ITP 8 (of 11) EBS 9 (of 11) INT 10 (of 11) TBC 11 (of 11) The EOS product was already installed thru the 'osinstall' or 'osupdate' command from the boot partition. EUT (BOSS/IX utilities) and EBS (BASIC) should be installed at this time. EBA (BASS diagnostics), ITP (intersystem transport), (INT international tools), and TBC (batch communications) are optional products and should only be installed if they are required. TBC is not released at this time. Read section 12 before installing the TBC product. ITP requires a software key if the expanded features are to be used. Refer to the ATP 4.0 o At the ADMIN> prompt, type 'install fd0 XXX', for each software product to be installed from the floppy diskette where XXX is the product name. o Insert the first XXX product diskette in the drive and press . SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg023 o Insert any additional diskettes as required and press when prompted. OR o At the ADMIN> prompt, type 'install cs XXX YYY ... ZZZ', to install the software products from 1/4" cartridge tape. XXX YYY ... ZZZ indicate the products to be installed. 24 When working with tapes, all products can be installed with one command line. When working with floppies, you must install one product at a time. Products that are chargeable and not part of the base system will have key codes that you must enter during or after (using '/bin/install key') installation before you can use that product. The '/etc/conf' file on the boot partition needs to be customized to meet your needs. (See Section 6.0 'Memory Usage' for instruction on how to customize the '/etc/conf' file.) After you have copied all products to disk and have customized the '/etc/conf' file, your system is ready for use. This completes the O.S. installation procedure. 3.3.3 Second Hard Disk Preparation This procedure prepares hard disk /dev/wd1 (the 2nd hard disk) to be used as a single mountable filesystem under BOSS/IX control. Make sure that the hard disk has been properly initialized and setup (see Sections 3.1 & 3.2). NOTE: 'prepdisk1' is a macro on the BOOT partition. This macro uses the 'fdisk', 'badtrk', and 'makefs' commands to prepare the 2nd hard disk for BOSS/IX. Step 1: Shutdown the System o see section 2.2 for shutdown procedures o Remove any diskette from the floppy drive. Step 2: Boot the System and ROOT to the BOOT Partition o When prompted, press to reboot the system. o When prompted to select boot device and system files, type ',/etc/boot.conf', . o When prompted to continue with startup, press . The system will display the ADMIN> prompt. 25 Step 3: Setting up the Hard Disk SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg024 Ensure that the hard disk has been properly formatted. o Type 'prepdisk1', . Hard disk /dev/wd1 is now prepared and available as a mountable filesystem. Step 4: Install the System Configuration Record NOTE: The configuration record only needs to be installed if the original configuration record specified one hard disk. o Type 'confinstallf', to install the configuration record from floppy diskette. o Insert the floppy diskette labeled 'configuration' into the drive. o Press to proceed with the configuration installation. The configuration record is now installed. o Remove any diskette from the floppy drive. Step 5: Shutdown the System o Press + 'D'. o Type 'shutdown', . o Remove any diskette from the floppy drive Step 6: Boot the system from the hard disk o When prompted to press 'RETURN' to reboot, press . o When prompted to select boot device, press . The system will now boot from hard disk. o When prompted to continue with startup, press . The system will display the ADMIN> prompt. The second hard disk preparation is now complete. 26 3.3.4 BOSS/IX System Upgrade/Reinstall Procedure Perform this procedure on a system already installed with BOSS/IX. The system may be completely reinstalled or just upgraded with this procedure. Step 1: Shutdown the System o See section 2.2 for shutdown procedures. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg025 o Remove any floppy diskette from the drive. Step 2: Boot the System and ROOT to the BOOT Partition o When prompted to press 'RETURN' to reboot, press . o When prompted to select boot device and system files, type ',/etc/boot.conf', . o When prompted to continue with startup, press . The ADMIN> will be displayed. Step 3: Install the System Configuration Record NOTE: Skip Step 3 if the configuration record has not changed from the previous version. o Type 'confinstallf', to install the configuration record from floppy diskette. o Insert the floppy diskette labeled 'configuration' into the drive. . o Press to proceed with the configuration installation. The configuration record is now installed. o Remove any diskette from the floppy drive. Step 4: Update or reinstall Root Partition WARNING: Always have a current back-up before doing any upgrades. 'osupdate' will preserve user files whereas 'osinstall' will destroy all user files. o Insert the first EOS product disk into the floppy drive or insert the install tape containing EOS into the tape drive. 27 o Type 'osupdate fd0', (For floppy update). Insert additional diskettes as required and press when prompted. OR o Type 'osupdate cs', (For 1/4" streamer tape update). OR o Type 'osinstall fd0', (For floppy update). Insert additional diskettes as required and press when prompted. OR o Type 'osinstall cs', (For 1/4" streamer tape update). SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg026 NOTE: Both 'osupdate' and 'osinstall' auto- matically update the BOOT partition. After the procedure ('osupdate' only) is complete you have the option of restoring the default system configuration files to the upgraded root then to the boot partition. This is done by typing "/sys/installetc". This procedure allows you to select which system files you need to restore. Please note that if this is done all system files that are restored will be new and will have to be re-updated to reflect the needed system information. Example: If '/etc/passwd' is re-installed the operators will have to be redefined. Following, find a list of the files that can be installed using '/sys/installetc' and the means to modify the file for your system: /etc/class, /etc/defaults, /etc/forms: These files are used when printing and can be customized by going to the 'ut.printer' menu and using Option 5 'Printer parameters' or using the program 'pparams'. /etc/conf: 28 This file contains the system configuration . parameters and is changed by using the '/bin/vconf' command. /etc/exem, /etc/logm, /etc/motd: These files print to the screen at the time of log in and can be modified by the use of the '/bin/ved' command. /etc/passwd: This file contains your operator information and is updated by going to the 'ut.system' menu and using Option 3, (Operator information) or by using the program 'oprinfo'. /etc/ports, /etc/printers, /etc/terminals: These files contain the terminal and printer configuration parameters and are updated by going to the 'ut.system' menu and using Option 1, (Port configuration) or by using the program 'configure'. /etc/sinit, /etc/startup: These files are used at system load time and can be modified by the use of the '/bin/ved' SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg027 command. /etc/shtdwn: This file is used when the system is being shutdown and can be modified by the use of the '/bin/ved' command. Step 5: Shutdown the System o See section 2.2 for shutdown procedures o Remove any diskette from the floppy drive. Step 6: Boot the System from Hard Disk o When prompted to press 'RETURN' to reboot, press . o When prompted to select a boot device, press . 29 o When prompted to continue with startup, press . The ADMIN> prompt will be displayed. Step 7: Install Desired Software Products o Type 'install /dev/fd0 XXX', for each software product to be installed from the floppy diskette where XXX is the product name.. o Insert the first XXX product diskette in the drive and press . o Insert any additional diskettes as required and press when prompted. OR o Type 'install /dev/cs XXX YYY ... ZZZ', to install the software products from 1/4" cartridge tape. XXX YYY ... ZZZ indicate the products to be installed. The system update/reinstall procedure is now complete. NOTE: In certain cases you may want to upgrade the boot partition without upgrading the root partition operating system files. The following procedure will effect the boot partition only. However, always have a current back-up before doing any upgrade procedure. Install boot partition, while preserving current partitions: o From a powered off condition, insert the BOSS/IX boot floppy in the diskette drive and close the latch. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg028 o Power on the system using the on/off switch located to the rear of the CCA. o When prompted to select boot device and system files, type 'f', . The system will now boot from floppy. o When prompted to continue with system startup press . The install menu will be displayed. 30 o Select menu option 'C' (Preserve current partitions, and install boot partition). o Type 'C', . The boot partition is now being prepared. o After this procedure is complete, the OPTION> prompt will appear. Press + 'D'. Type 'shutdown', . This completes the boot partition upgrade. 3.3.5 BOSS/IX Configuration Record Installation Each system needs a unique configuration record based on the system serial number and hardware configuration. Perform the following procedure to install a different configuration record. For example, a new configuration record would be required to enable the installation of an additional 8-way controller board. Step 1: Shutdown the System o See section 2.2 for shutdown procedures o Remove any diskette from the floppy drive. Step 2: Boot the System and ROOT to the BOOT partition o When prompted to press 'RETURN' to reboot, press . o When prompted to select a boot device and system files, type ',/etc/boot.conf', . o When prompted to continue with startup, press . The ADMIN> prompt will be displayed. Step 3: Install System Configuration Record o Type 'confinstallf', (For floppy install). o Insert configuration floppy into floppy drive. o Press to proceed with configuration installation. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg029 Configuration record is now installed. o Remove configuration floppy. 31 Step 4: Shutdown the System o Press + 'D'. o Type 'shutdown', . o Remove any diskette from the floppy drive. Step 5: Boot the System from Hard Disk o When prompted to press 'RETURN' to reboot, press . o When prompted to select a boot device, press . o When prompted to continue with startup, press . The ADMIN> prompt will be displayed. The configuration record is now installed. Once you have installed/upgraded the configuration record on your system it will not have to be done again unless a hard disk re-initialization is required or the system's hardware configuration changes. 3.3.5.1 The 'iconf' command The program '/bin/iconf' will display the current configuration in force as well as the configuration contained in a configuration record file. The 'iconf' command can also be used to install the configuration record. Format: iconf Options: -new Display the new system configuration which may be installed. -save Permanently installs the new configuration record. 32 Examples: @>iconf Displays the current system configuration. @>iconf - new -save Displays the default configuration record and stores SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg030 it in the system configuration record. NOTES: Only the system administrator may display or install the new configuration. The configuration record is always read from, or written to, the Winchester disk from which the system was booted, or from wd0 if the boot device was tape. Unless explicitly specified, the new configuration record is assumed to be contained in a file under the name '/sys/config.', where is the 10 character system serial number. 3.3.5.2 Configuration Record Request Sheet At the end of this document you will find a copy of the MAI 1800 Configuration Record request sheet. 3.4 Installing MS-DOS 3.4.1 Create MS-DOS Partition This section describes the procedure for creating a MS-DOS partition using MS-DOS FDISK and installing MS-DOS onto the system. NOTES: a. The BOSS/IX partition should already exist before proceeding. The BOSS/IX partition is automatically created during the BOSS/IX installation or upgrade. Option 'B' was used to allow for a coexisting MS-DOS partition (see section 3.3). b. The maximum size for a single MS-DOS partition is 32MB. c. The maximum number of MS-DOS partitions on a disk is 3. If BOSS/IX is to coexist, only 1 MS-DOS partition is allowed. ^ 33 d. If the system contains 2 disk drives, the 2nd disk must be prepared for either BOSS/IX or MS-DOS. e. FDISK will not allow a partition to start in a cylinder where a bad track has been marked. If the cylinder selected as the starting cylinder contains a reserved bad track, FDISK automatically starts the new partition in the next cylinder that does not contain bad tracks. Following are the steps required to create the MS-DOS partition: 1. Insert the MS-DOS diskette (1 of 2) into floppy drive SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg031 'A' and boot the system. After entering the date and time, the system will respond with the MS-DOS prompt A>. 2. Enter 'fdisk', and the system will display the FDISK options menu. The default choice is 1. To select another option, enter the number and press . 3. Select Option 1, 'Create MS-DOS Partition'. The system displays the total disk space, maximum available space, and the following prompt: ENTER PARTITION SIZE........: Press . 4. When prompted to 'ENTER STARTING CYLINDER NUMBER', press . 5. When prompted to 'Press Esc to return to MS-DOS', press . 6. The following message is displayed: 'Please insert MS-DOS diskette into drive A: Press any key when ready...................' "@ 0ress any key. 7. When the system re-boots, enter the date and time. Proceed to the next section. 34 3.4.2 Formatting and Copying MS-DOS to the Hard Disk This section details the procedure used to format the hard disk for MS-DOS and to copy the MS-DOS files to the disk. 1. At the A> prompt, enter 'fdisk', . The FDISK options menu will be displayed. 2. At the 'Enter choice:' prompt, Enter '2', . The system displays a table with the partition information leaving the cursor positioned at the prompt at the bottom of the screen. The column headings are defined as follows: PARTITION - the number of the partition in the order in which it appears on the hard disk. STATUS - Shows wheth%yaa partition is 'A' (for Active, i.e., in control when the system is started from the hard disk) or 'N' (for Non-active). TYPE - shows whether the operating system that occupies the partition is MS-DOS or not MS-DOS. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg032 START - the starting cylinder number for the partition. END - the ending cylinder number for the partition. SIZE - the size of the partition in cylinders. 3. Change the MS-DOS partition status to active. The MS-DOS partition should be partition # 2. If this is the case, when prompted to 'Enter the number of the partition you want to be active.............:', enter '2', . 4. Press . The FDISK Options menu is displayed. Press . the A> prompt is displayed. 5. At the A> prompt, enter 'format c: /s/v', . The system will display a warning message that the program will destroy all the data on the disk and prompt for a 'Y' to continue. NOTE: Only the MS-DOS partition data will be destroyed. The BOSS/IX partition will remain intact. 35 6. Enter 'Y' and the system will again display a warning message that the program will destroy all the data on the disk and prompt for a 'Y' to continue. Enter 'Y', . The system will respond with: Formatting... Verifying... System transferred 7. The last message says that a copy of MS-DOS has been placed on the disk. You are now prompted for a label to identify the disk. The label can be up to 11 characters long or a will equal no label. Enter the label and when complete. The system will next display information about disk space allocation in bytes, used by the system and bytes available on the disk. 8. The system responds with the MS-DOS prompt A>. To copy all files from your MS-DOS diskette onto the hard disk enter 'copy *.* c:', . 9. When the transfer is complete, remove the MS-DOS diskette from the floppy disk drive. 10. Insert the MS-DOS (2 of 2) diskette into the floppy disk drive and enter 'copy *.* c:', . 11. Remove the MS-DOS diskette from the floppy disk drive and set it aside. Your system now has MS-DOS in the MS-DOS partition of the hard disk. 36 4.0 SYSTEM HARDWARE SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg033 This section details information on the 1800 switch settings, board placement, cables and cable connection. 4.1 Base Hardware Configuration The base MAI 1800 system is shipped with the following hardware in the CCA cabinet: o Monochrome/Color Graphic Adapter Card o 640KB of memory on the Mother board o 1024KB expansion memory board o 1.2MB floppy disk drive o 31MB, 58MB or 115MB hard disk drive o Serial/Parallel port controller o Disk Controller (supports 2 hard disks & 2 floppy disk drives.) o Mother Board with 8 card slots o Power Supply for disk drives and boards o Front panel with key lock and two keys o Cables to install a second hard disk drive and a second floppy disk drive 4.2 System Hardware Set-up The following are the installation and set-up instructions for each board in the CCA: o Monochrome/Color Graphics Adapter Card The Monochrome/Color Graphics Adapter Card is shipped in the CCA, in slot location 1, with the switches set for a color monitor. Following are the various switch settings for the adapter card: 37 GRAPHICS DISPLAY ADAPTER _________________________________________________________________________ | | | | | Monitor | Operational | Switch Settings | | Type | Mode | 1 2 3 4 5 | | | | | | | | | | Monochrome | Monochrome or | ON OFF ON OFF Ignored | | | monochrome/Hercules | | | | | | | * Monochrome | Emulation | OFF OFF ON OFF Ignored | | | | | | ** Color | Color/Graphics | OFF ON ON OFF Ignored | | | | | | Color | Color/Graphics | | SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg034 | | (Enhanced Graphics) | OFF ON OFF OFF Ignored | | | | | | Monochrome | | | | Composite | Monochrome | ON OFF ON OFF OFF | | | | | | Color | | | | Composite | Color/Graphics | OFF ON OFF ON ON | | | | | * Switch settings for the Monochrome monitor ** Switch settings for the Color monitor The slide switch on the main PCBA labeled 'COLOR/MONO' near the disk controller connector should be set to the 'COLOR' position for both the standard switch settings (* and **) shown above. o Serial/Parallel port controller One serial/parallel port controller is shipped in the CCA, in slot location 7. The jumper block at location 2E on the board has the two open connections away from the cable connectors to be set for COM1, or the first terminal (This is how the board is shipped.). To set the board for COM2, or the second terminal, remove the jumper block and turn it 180 degrees so that the open connectors are towards the cable connectors. To set the board for LPT1, the jumper block at location 2D will have the two open connectors away from the cable connectors (This is how the board is shipped.). The MAI 1800 will only support one parallel printer. If two serial/parallel port controllers are installed, the second board must be addressed for LPT2, even though this port will not be used. This is done by removing the jumper block at 2D and turning it 180 degrees so that the open connectors are towards the cable connectors. 38 NOTE: The serial/parallel port controller(s) can be located in any open board slot. o Disk Controller The disk controller is shipped in the CCA at board slot location 8. Each cable is stamped with a letter corresponding to the drive it plugs into (A=F0, B=F1, C=H0, D=H1). The floppy drive has one daisy chain cable for both drives. The hard disk drives have one each radial or control cable (the radial controller end is hanging free at the drive end). The hard disk data cable is a daisy chain cable. The disk controller board should have jumper E2 jumped to E3, E5 to E6 and E7 to E8. The first two jumpers are for setting the floppy and hard disk, and need not be changed when adding a second disk of either type. The third jumper is for the data separator and must be in place at all times. NOTE: The jumper block for E1 though E6 is labeled with E1 and across from it is E4. E2 and E3 are on the same side as E1 but are not marked. The jumper for E7 SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg035 and E8 are not at the same location as the E1 though E6 jumpers. o Mother Board The Mother board is located on the bottom of the CCA and contains the board slots. The Mother board, also, contains 640KB of memory and there are no switch settings for memory addressing. In addition, there is a slide switch located just to the left of slot 8, towards slot 7, for setting the system for a color or monochrome monitor(see GRAPHICS DISPLAY ADAPTER settings). o Intelligent 8-way Controller Up to two ISC (intelligent serial controller) boards can be installed for a possibility of 16 serial ports. Along with the standard serial/parallel port card, this yields a maximum of 17 serial ports and 18 users(17 serial ports plus the system monitor). The switch settings are: primary 6, 8 on; the rest off; no jumpers needed (1st 8-way) secondary 6 on; the rest off; no jumpers needed (2nd 8-way) 39 NOTE: The ISC boards must be installed in one of 16 bit CCA expansion slots. Physically, the ports on both boards are from top to bottom (1-8). When configuring the ports using the BOSS/IX 'configure' utility Board #1 will be configured as ports 4-11 whereas board #2 will be ports 12-19. As an example, configured port #4 corresponds to physical port #1 on ISC board #1 and configured port #12 corresponds to physical port #1 on ISC board #2. o 1/4" Tape Controller Board One 1/4" Tape unit may be installed. The switch settings are: 1 thru 5 on; 6 thru 10 off; jumpers required: DA:3 IRQSL:2 DR:3 o Expansion memory 0-1024K SW-1*: all off SW-2: 1,2 off; rest on 1024-2048K SW-1*: all off SW-2: 3,4 off; rest on *Should not need to be changed. o Additional hardware items and switch settings 1. The front panel contains a key lock switch. If the switch is in the locked position, the CCA cover cannot be removed SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg036 and the keyboard is disabled. 2. There is a button on the front panel above the picture of a lightning bolt and a green LED. The LED is lit when the system is operating at 10 MHZ, and it is off when operating at 6 MHZ. This button normally should be disabled by the system setup procedure (see Section 3.1 step 5). WARNING: BOSS/IX is only certified at 10Mhz and should not be used at 6Mhz. 3. The green LED above the picture of a light bulb is the system power on indicator. 4. The green LED above the picture of a drum is lit whenever there is a hard disk access. 40 5. The back panel of the CCA contains the ON/OFF, circuit breaker switch, a 115/220 VAC voltage select switch, a power receptacle for the console monitor, a receptacle for the main A/C power cord, and two different types of jacks for keyboards. 6. The system serial number (SSN) is provided by a device that is installed between the CCA parallel port and the cable end of the parallel printer. The SSN is programmed by manufacturing or the field service organization. This device must be present during boot time or the system will shutdown. Also, the SSN is randomly checked during normal BOSS/IX operation. If the device becomes inoperative or is removed during BOSS/IX operation, the system will shutdown. 4.3 Terminal and Printer Support 4.3.1 Terminal Support The following terminals are supported under 7.2N: Maximum Supported Model # Per System DT4309 17 DT4310 17 DT4312 17 DT4313 17 7270 (limited support) 17 The system console has limited support of the MAI Basic Four international character set that is available on standard serial terminals such as the DT4313 (see the 'CAUTIONS AND WARNINGS' section 10.0). An output translation file has been set up to map the IBM AT compatible console character set into the MAI Basic Four set. However, the IBM set has fewer characters than the MAI BASIC FOUR set. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg037 Mnemonics are supported for the system console; however, special escape sequences used for serial terminals (i.e., function key loads) are not supported. 41 When a color monitor is used in conjunction with the system console, underlining is not supported. The 'BU' and 'EU' mnemonics will display a line in blue (the color monitor hardware doesn't support underlining). Function keys F1, F2, F3, and F4 correspond to Motor Bar keys I, II, III, and IV. Function keys F5 - F10 behave like a 'carriage return'. When the key is held down simultaneously with another key, an 8 bit character will be generated. When the key is held down simultaneously with the key, the screen is cleared. This is similar in function to pressing + on a MBF DT4310 or later terminal. 42 ____________________________________________________________________ | | | O.S. Support_ Interface*2 _ | | Model # MS-DOS BOSS/IX I/S Ser. MBF Ser. Par. | |------------------------------------------------------------------| | | | PT-4223 Yes*6 Yes Yes No Yes*5 | | | | PT-4222 Yes*7 Yes Yes*5 No Yes | | | | PT-4218 Yes*7 Yes No Yes*3 Yes*5 | | | | PT-4217 Yes*7 Yes No Yes*3 Yes*5 | | | | PT-4216 Yes*4 Yes Yes No Yes*5 | | | | PT-4215 Yes*7 Yes Yes No Yes*5 | | | | PT-4214 No Yes No No Yes | | | | PT-4213 No Yes Yes Yes*3 No | | | | PT-4211 Yes*4 Yes Yes No No | | | | PT-4210 No Yes No Yes*3 No | | | NOTES: *1: First printer is typically connected to the parallel port. If MS-DOS mode will be used, only one printer may be selected for use at a time. Serial printers to be accessed via MS-DOS must be attached to the serial port on a single serial/parallel port card, not to an 8-way port. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg038 *2: Indicates which interface standards are supported. I/S ser = industry standard serial, MBF ser = MAI Basic Four serial, Par = Centronics parallel. *3: Printers with MBF serial interface can also be used as slave printers with DT-4313, DT-4312 or DT-4310 terminals. *4: Use of PT-4216 and PT-4211 daisywheel printers under MS-DOS requires a PC application that supports Diablo 630 emulation. *5: Limited mnemonic support. *6: PT-4223 supports IBM PC graphics printer and Diablo 630 emulation under MS-DOS. *7: PT-4222, PT-4218, PT-4217 and PT-4215 support IBM PC graphics printer emulation under MS-DOS. 43 4.3.2.1 Printer Configuration There are two new directories released on the MAI 1800 7.2N release that are not present on 7.2 A, B, or C releases. These directories are: /etc/ptrtbl and /etc/ptrxlt These directories contain the Printer Definition Files (PDF's for mnemomic processing) and the printer character translation files respectively. To inform the system of the type of printer(s) you have connected, run the configure utility. When you select the option to configure a printer, the system will display a list of model numbers for all supported printers. The list is generated from the information contained in the /etc/printdef file. After configuring the printer, you will need to run the 'pparams' utility to define a form for the printer. A form is used to describe the paper margins, the paper length, and the character translation file. 44 There is a set of translation files released with the system in the /etc/ptrxlt directory. These are: ________________________________________________________________ | | | File Model # Comments | |--------------------------------------------------------------| | CI 4217B4 Supports the MBF character set. | | 4218B4 The serial line should be set | | for 8 data bits to utilize | SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg039 | the full character set. | | | | DI 4215 Used for diablo type printers | | 4216 with a standard ASCII 96 | | print wheel. | | | | ES 4215 Used for diablo type printers | | 4216 with a European standard | | print wheel. | | | | WP 4215 Used for diablo type printers | | 4216 with a WP print wheel | | | | MV 4214 Supports the MBF international | | character set. The printer | | requires a special ROM | | (#165047-046) and 8 bit data. | | | | S7 isp 7 bit data. | | | | S8 isp 8 bit data required to utilize | | the full character set. | | | | WI 4213 Supports the MBF international | | 4213B4 character set. The printer | | requires a special ROM | | (#165031-081) and 8 bit data. | | | | 7G For MBF printers with ISO | | German character ROMs. For | | 7 bit data lines. | | | | 8G For MBF printers with ISO | | German character ROMs. For | | 8 bit data lines. | |______________________________________________________________| 45 A user can create a custom translation table with the '/bin/ved' command. A comparable existing translation file (located in the '/etc/ptrxlt' directory) can be used as a template. Follow these guidelines for a new translation table: o Must have a '.tran' suffix. o Must reside in the '/etc/ptrxlt' directory. o After the file is created the '/bin/makupdxlate' command must be executed to compile the source code file. FORMAT: makeupdxlate infile o=outfile o Setup a form that specifies the custom translation file. 4.4 Port Configuration NOTE: 1. The maximum number of printers allowed is defined in SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg040 the system configuration (vconf) file. If a system or slave printer is added to the MAI 1800, the vconf file must be modified to reflect the proper number of configured printers. At the ADMIN> prompt, type "vconf -os" to display the current vconf parameters. If the printer parameter is incorrect, update the "printers=" parameter using the vconf command (see section 6.1). This is a brief overview of the port configuration utility. The configure utility is discussed in detail in the BOSS/IX USER GUIDE (M6210A). All connected devices, except the system console, must be software configured. Port configuration is the process of setting the operational characteristics of the serial and parallel ports on the serial/parallel card and the serial ports 8-way board. These ports may be used to connect terminals and printers. These devices can be connected directly, using appropriate cables, or be remotely located and connected, using modems. Port configuration should be executed in single-user mode to assure system integrity. Modification of ports while they are in use can cause data destruction and operator discomfort. 46 The configure utility '/util/configure' is menu driven and will prompt you for all inputs. At the ADMIN> prompt, type 'configure', . Port 1 is the only parallel port on the MAI 1800 system. All other ports are serial ports. Port configuration allows the following options for all ports with the exception of port 20 which is used for communications: o Add a device o Remove a device o Move a device o Switch two devices o Report port attributes o Modify port attributes '/util/configure' will modify the following system files in order to perform software configurations: '/etc/ports' - contains information about each port configured for a device. '/etc/terminals' - contains information about each terminal configured on the system. '/etc/printers' - contains information about each printer configured on the system. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg041 '/dev' - '/util/configure' will add a device file to this directory for each device configured on the system. '/etc/defaults' - when a printer is configured, this file is modified to specify whether there will or won't be spooling for that printer. Attaching a parallel printer requires the following steps: 1. Connect the printer (with the proper cable) to the parallel port. The cable will attach to the security device which then plugs into the parallel port on the CCA. 2. Configure the printer using the configure utility. 3. Use the "vconf" command to modify the "/etc/conf" file located on the boot partition. 47 Attaching a serial device requires the following steps: 1. Connect the terminal or printer (with the proper cable) to a serial port on the system. 2. Set the terminal's or printer's data transmission characteristics. 3. Configure the port each device is connected to. If the device is a printer and there is already at least one other configured printer, modify the "/etc/conf" file located on the boot partition. 4.5 System Cabling This section gives the cable diagrams for the peripheral cables that are available for the MAI 1800. 906694 Serial Printer to Video Display Terminal Also for Serial Device to 6 ft. 8-way Adapter Cable 907933 Parallel Printer to Port Board 916031 MCS 1/4" Tape Drive to System 916073 Modem to Serial/Parallel Port Board 916074 Serial Device to Serial/Parallel Port Board 916117 8-way Modular (25-100 ft.). Terminal to 8-way Port 916126 8-way Adapter (6 ft. only). Used in conjunction with a 906694 cable. 48 CABLE DRAWINGS PA PB SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg042 2----------------2 brown twisted pair 7----------------7 all whites from pairs 3----------------3 red twisted pair 20--------------20 black twisted pair 4--20 6-8-20 jumpers 4-5 jumper 25 pin connector on both ends Serial Printer to Video Display Terminal or Serial Device to 6 ft. 8-way Adapter Cable P/N - 906694 Parallel Printer to Port Board P/N 907933 (see hardcopy) 49 MCS 1/4" Tape Drive to System P/N 916031 (see hardcopy) 50 Modem to Serial/Parallel Port Board P/N 916073 (see hardcopy) Serial Device to Serial/Parallel Port Board P/N 916074 (see hardcopy) 51 8-way Modular (25-100 ft.). Terminal to 8-way Port P/N 916117 (see hardcopy) 8-way Adapter (6 ft. only). Used in conjunction with a 906694 cable. P/N 916126 (see hardcopy) 52 5.0 BACK-UP AND RESTORE The Series MAI 1800 System provides three types of backups and restores for the BOSS/IX partition and various types of backups and restores for the MS-DOS partition. NOTES: 1. Magnetic Cartridge Streamer is not supported under MS-DOS. 2. Only the BOSS/IX partition can be backed up under BOSS/IX. 3. Only the MS-DOS partition can be backed up under MS-DOS. 5.1 Back-up and Restore under BOSS/IX SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg043 The method used is dependent on the hardware configuration. A backup or restore can be performed using a 1/4" magnetic cartridge streamer (MCS) tape, a 1.2MB floppy diskette, or a filesystem to filesystem transfer. 5.1.1 Via MCS (1/4" Magnetic Cartridge Streamer Tape) There are two methods that can be used to save or restore files via MCS. 1. Use the BOSS/IX commands '/bin/mcssave' and '/bin/mcsrestore'. At the ADMIN> prompt, type 'mcssave -h' or type 'mcsrestore -h'. This will give you the syntax and options required to execute either command. After execution of '/bin/mcssave', it is recommended that a '/bin/mcscompare' is executed. This will verify that the information on the disk and tape are the same. Single or multiple files can be saved or restored using the commands. Create a filelist for multiple file backup/restore. A filelist is a text file containing the full directory pathnames of files that are to saved or restored. Each pathname must be separated by a carriage return. Three methods of filelist creation: o Redirect a directory listing to a file using the 'ls' command and the '>' sign. o Use the text editor (VED) to create a file. o Use the filelist maintanence utility 53 2. Use the save and restore utility o At the ADMIN> prompt, type '/util/ msave', . OR o At the ADMIN> prompt, type '/util/mrestore', . OR o At the ADMIN> prompt, type 'menu', . o choose option 1 (utility programs option). o choose option 5 (save & restore option). o choose the desired save or restore option. 5.1.2 Via 1.2MB Floppy Diskette There are various methods for saving or restoring files via 1.2MB high-density floppy diskettes: SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg044 1. Use the 'mount' and 'copy' commands. Once the floppy is mounted to an empty directory, files can be copied to this diskette. 2. Use the save and restore utility o At the ADMIN> prompt, type '/util/dsave', . OR o At the ADMIN> prompt, type '/util/drestore', . OR o At the ADMIN> prompt, type 'menu', . o choose option 1 (utility programs option). o choose option 5 (save & restore option). o choose the desired save or restore option. 5.1.3 Filesystem to Filesystem Files may be saved to an alternate filesystem or restored from an alternate filesystem. This can be done for example, if a system has two hard disks. The secondary hard disk can be mounted using the '/bin/mount' command. The '/bin/copy' command can then be used to transfer an entire directory structure or a single file from disk to disk. 54 5.2 Back-up and Restore under MS-DOS There are various methods of saving and restoring files on the MS-DOS partition: 1. Use the MS-DOS BACKUP and RESTORE utilities. o Back-up the MS-DOS partition Makes copies of files from one disk to another. Ex. At the C> prompt type "BACKUP C: A: /S" (This will back-up the entire MS-DOS partition located on drive C. You will be prompted to place formatted diskettes in drive A. The amount of formatted diskettes needed for back-up depends on the amount of disk being backed up. 9 1.2MB floppies are required to back-up 10MB. o Restore an MS-DOS Back-up Restores files previously backed up by the MS-DOS BACKUP command. Ex. At the C> prompt type "RESTORE A: C: /S" (If the example above was used to backup the MS-DOS partition, "RESTORE A: C: /S" will restore everything. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg045 2. Use the MS-DOS COPY command Copies one or more files; can also combine files. Ex. At the C> prompt type "COPY *.* A:". All files residing in the current directory path will be copied to a formatted diskette residing in drive A. Refer to the MS-DOS manual for detailed information regarding the MS-DOS BACKUP, RESTORE and COPY commands. 55 6.0 CUSTOMIZATION This section details the information required to customize or change your operating system's parameter file. 6.1 Operating System Parameters Customization The system hardware configuration is determined at system boot time. Each accessible piece of equipment on the system has an associated '/dev' file. All '/dev' files are either defined by the '/util/configure' utility or are part of the EOS product. Besides the hardware, the operating system can be customized for the needs of each individual site. This is done by the use of the '/bin/vconf' command. This command allows you to set some of the parameters that control the BOSS/IX operating system. The values of these parameters are based on your system's software and hardware components, and the environment and performance expected. Section 7.0 of this document describes how to calculate your system's memory requirements. Some of the 'vconf' parameters described in this section affect the amount of memory your system needs. These are the BOSS/IX control parameters that can be changed by the 'vconf' command. root device (root=) This parameter specifies the disk partition that contains the root filesystem. (The default is 1403, "/dev/root") swapper device & size (swap=, size=) These parameters specify the disk partition that is used for task swapping. If you change the swap device or its size, you must also specify the number of blocks in the swap partition. The default is 2048: "/dev/swap". system ID (system=) You can set the system name that is displayed when the system is booted. mount error override (-oride, -noride) You can specify how the system should handle a filesystem mount error. This error occurs when trying to boot a system that was shutdown without the proper procedures. You can tell the system to ignore the error. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg046 A mount error indicates that the root filesystem, and any other filesystems that were mounted when the system was shutdown, are probably damaged. 56 single/multi boot (-single, -multi) You can tell the system to boot into single-user mode or directly into multi-user mode. boot messages (-silent, -verbose) You can tell the system to boot silently or to display boot messages. Once the system has booted, verbose mode remains in affect. Diagnostic messages will continue to be displayed on the system console. Verbose mode is sometimes useful when you are attempting to diagnose hardware problems. secure boot (-secure, -nonsecure) You can tell the system to require the system administrator ( ADMIN ) to enter a password in order to boot. This security feature is active only when the system is booted into single-user mode and a password is present for the "ADMIN" user account. crash dump (-dump, -nodump) You can tell the system to generate a dump when the system crashes by using "-dump". The dump is used by engineering to aid in diagnosing the cause of the crash. (-nodump) Turns off dump mode. linekill character (linekill=) You can set the keyboard character for the linekill function. The default is the key. The setting of this parameter has no effect on performance or memory usage. erase character (erase=) You can set the keyboard character for the erase function. The default is the key. The setting of this parameter has no effect on performance or memory usage. mountable filesystems (mfsys=) You can specify the maximum number of filesystems that can be mounted on the root filesystem. You will need to increase this number if you define additional filesystems. You will also need to increase this parameter if you add more disk drives. The setting of this parameter has an effect on memory usage. printers (printers=) You can specify the maximum number of printers that can be configured on your system. The number of printers selected has an effect on memory utilization. 57 processes (procs=) You can specify the maximum number of processes that can execute on the system. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg047 If you change the number of processes, you should also change these parameters: open files event calls shared text segments logical units file locks All of these require more memory resources. file locks (locks=) You can specify the maximum number of files or portions of files that can be locked at the same time. system buffers (buffers=) You can specify the number of BOSS/IX buffers. The buffers are defined in memory. They are used to cache disk sectors. Each buffer caches a single 512 byte disk sector. open files (opens=) You can specify the number of different files that can be opened on the system at one time. event calls (eventcalls=) You can specify the maximum number of event calls that can be opened at one time. Used mostly by the spooler. shared text segments (tsegs=) You can set the maximum number of shared text segments (program code segments) on your system. logical units (lus=) You can set the number of logical units on your system. This parameter tells the system the maximum number of open channels the system can have at one time. terminal input buffer size (ibsize=) Sets the maximum number of characters which may be transferred on a terminal read. This refers to the maximum number of characters that the system can read before seeing a 'CR'. This parameter is for all the terminals on the system and can not be adjusted for only one terminal. 58 terminal type-ahead buffer size (tbsize=) Sets the maximum number of characters which may be queued for a future terminal read. This parameter includes all the terminals on the system and cannot be adjusted for only one terminal. current O.S. parameters (-os) Displays configuration parameters of the currently booted operating system. To modify the system default configuration file '/etc/conf' from the root partition: perform the following steps: @> mount /dev/boot /mnt SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg048 @> vconf /mnt/etc/conf -save (options) @> unmount /mnt 59 Recommended Values for "vconf" BOSS/IX Parameters ___________________________________________________________________ | | | | | | | | | |add |add |add |maximum | | vconf | base |for |for |for |recommended | | parameter | system |each |each |each |system values | | | |user |ghost |printer | (note 1) | |----------------|---------|-------|------|--------|--------------| |buffers= | 64 | 16 | 16 | | 880 | |----------------|---------|-------|------|--------|--------------| |printers= | 1 | | | 1 | 17 | |----------------|---------|-------|------|--------|--------------| |procs= | 32 | 4 | 1 | 2 | 200 | |----------------|---------|-------|------|--------|--------------| |tsegs= | 32 | 2 | | | 200 | |----------------|---------|-------|------|--------|--------------| |locks= | 74 | 5 | 5 | 1| 172 | |----------------|---------|-------|------|--------|--------------| |ibsize= | 512 | | | | 2048 | |----------------|---------|-------|------|--------|--------------| |tbsize= | 64 | | | | 512 | |----------------|---------|-------|------|--------|--------------| |mfsys= | 3 | | | | (note 2) | |----------------|---------|-------|------|--------|--------------| |lus= | 136 | 20 | 20 | 6 | 1300 | |----------------|---------|-------|------|--------|--------------| |opens= | 86 | 10 | 10 | 4 | 760 | |----------------|---------|-------|------|--------|--------------| |eventcalls= | 32 | 2 | 1|(note 3)| 152 | | | | | | | | NOTES: 1. Values in this column are the maximum values recommended for any given parameter. You can't configure a system with all parameters set to the maximum. This would create a table size greater than 3MB. Refer to tables 7A & 7B for standard configuration recommendations. 2. Allow one mountable file system for each mountable disk partition. A default of 3 allows for a root, boot and 1 other partition. 3. Add 4 for each extra printer (Only to be added if the printer is going to use SPOOLING). 60 7.0 MEMORY USAGE This section describes how to determine the memory requirements for the MAI 1800. All BOSS/IX systems have different memory requirements. The system's memory requirement is based on its hardware configuration and software load. Specifically, the number of peripheral devices (i.e., terminals and printers) and software packages (such as BASIC, BASIC applications, utilities, etc.) determine a system's memory needs. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg049 7.1 Approximating A System's Memory Requirement Table 7A shows some standard system configurations which can be used to approximate the amount of memory a system needs. The number of users (terminals), ghost tasks, and printers differ for each of these standard configurations. First, find the standard configuration that most closely matches the system in question, by scanning down the user/terminals, ghost-tasks, and printers columns. Second, scan across the table to memory-needed column -- this is the system's memory requirements. NOTE: This table 7A assumes that the system in question will be executing 60% BASIC and BASIC applications programs, and 40% non-BASIC applications. If the system will be executing a higher percentage of non-BASIC programs, it will need more memory. Table 7B shows how to set up the BOSS/IX configuration ("vconf") parameters for each of the standard system configurations in table 7A. In other words, if one uses the approximation method to determine a system's memory requirements, table 7B can be used to set up the BOSS/IX configuration parameters. The approximation method is an easy and accurate way to determine a system's memory needs, if its configuration is close to one of the standard configurations. However, if it does not closely fit one of the configurations shown, the calculation method should be used (see section 7.2). 61 _______________________________________________________________________ | | | | | | | | | Standard | User/ | Ghost | Printers | Memory | Memory | Memory | | Config. | Terminals | Tasks | | Needed | used | free | | | | | | | | | | Number 1 | 2 | 0 | 1 | 1664KB | 755KB | 910KB | |-----------|-----------|-------|----------|--------|--------|--------| | Number 2 | 5 | 1 | 1 | 1664KB | 1151KB | 514KB | |-----------|-----------|-------|----------|--------|--------|--------| | Number 3 | 9 | 1 | 2 | 1664KB | 1544KB | 121KB | |-----------|-----------|-------|----------|--------|--------|--------| | Number 4 | 12 | 2 | 3 | 2688KB | 1948KB | 741KB | |-----------|-----------|-------|----------|--------|--------|--------| | Number 5 | 16 | 3 | 3 | 2688KB | 2431KB | 258KB | |___________|___________|_______|__________|________|________|________| TABLE 7A Approximating the Memory Requirements NOTE: The number of user/terminals shown is approximately the highest number which can be supported in the memory shown. 62 ______________________________________________________ | | | | "vconf" BOSS/IX | Standard Configuration | SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg050 | Parameter |----------------------------------| | |Number|Number|Number|Number|Number| | (see table 7A) | 1 | 2 | 3 | 4 | 5 | |-----------------|------|------|------|------|------| |buffers= | 96 | 160 | 224 | 288 | 384 | |-----------------|------|------|------|------|------| |printers= | 1 | 1 | 2 | 3 | 3 | |-----------------|------|------|------|------|------| |procs= | 42 | 55 | 73 | 88 | 149 | |-----------------|------|------|------|------|------| |tsegs= | 36 | 42 | 50 | 56 | 149 | |-----------------|------|------|------|------|------| |locks= | 85 | 105 | 126 | 147 | 182 | |-----------------|------|------|------|------|------| |ibsize= | 512 | 512 | 512 | 512 | 512 | |-----------------|------|------|------|------|------| |tbsize= | 64 | 64 | 64 | 64 | 64 | |-----------------|------|------|------|------|------| |mfsys= | 3 | 3 | 3 | 5 | 5 | |-----------------|------|------|------|------|------| |lus= | 182 | 262 | 348 | 434 | 574 | |-----------------|------|------|------|------|------| |opens= | 110 | 150 | 194 | 238 | 308 | |-----------------|------|------|------|------|------| |eventcalls= | 38 | 45 | 55 | 64 | 73 | | | | | | | | TABLE 7B "vconf" BOSS/IX Parameters for Standard Configurations 63 7.2 Calculating System Memory Requirements This section describes a more careful method to calculate the amount of memory a system requires for adequate performance. The calcultions are based on the hardware configuration and how the system will be used. NOTE: 1KB = 1024 bytes 1MB = 1024KB = 1024 * 1024 = 1,048,576 bytes The amount of memory required can be calculated using the following numbers by totaling the memory required by each parameter. ________________________________________________________ | | | # buffers * 586 | | # procs * 1854 | | # tsegs * 20 | | # eventcalls * 18 | | # locks * 40 | | # lus * 50 | | # opens * 214 | | # printers * 1514 | | # mfsys * 500 | | # serial ports * 1600 | | # hard disks * 340 | | console 1600 | SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg051 | OS 28100 | | basic interpreter 152600 | | # start size * 308 + 40040 | | (for each basic program and/or ghost) | | | | size of addr program(for each addr basic program) | | | | # active despoolers * 64000 | |______________________________________________________| NOTE: Total = memory needed for no swapping to occur. * = multiply by # = number of This calculation doesn't count any utilities or commands active on the system. 64 8.0 SECURITY There are three levels of security for the MAI 1800. System security, file security and application security for software. 8.1 System security System security is implemented by terminal logon and passwords. Each operator can be assigned an account name and password. When the system boots into multi-user mode each terminal is auto- matically started according to the parameters set in the port configuration (start process). If the start process is set to '/bin/login', the system will monitor the access of operators to the system. Once, logged on, the operators can be localized to a specific area of the system. Operator information within the '/etc/passwd' file, states the operators working directory, their password, and the program to be run after a successful login. Once the program completes or the operator exits the program, the operator can be sent back to the login prompt. This action restricts the user to one area of the system. From logon the operators can be sent to any part of the system. This includes command mode, BASIC, menu system, or a BASIC program. 8.2 File security File security is incorporated in the Business File System portion of the operating system. All files and directories created on the system are assigned access privileges (read, write, and execute). These privileges are specified for the owner and for others (all non-owners), by the file owner. Any unautorized attempt to access a file will result in an error message 'access denied'. The access modes can be changed at any time by the file owner. To change file access, use the '/bin/filemodes' command or the '/util/fsecure' utility. 8.3 Product Security Product Security allows installation and use of BOSS/IX SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg052 chargeable products on an authorized basis. This ensures control of software by MAI Basic Four, Inc. and software vendors for the MAI 1800. This authorization is provided through a lock and key process. All products with lock and key protection will be licensed on a per system serial number (SSN) basis. Without the correct key the software will not execute. 65 Purchased MAI 1800 products will arrive at the customer site with the key certificate attached to the media. NOTE: The system serial number (SSN) is provided by a device that is installed between the CCA parallel port and the cable end of the parallel printer. The SSN is programmed by manufacturing or the field service organization. This device must be present during boot time or the system will shutdown. Also, the SSN is randomly checked during normal BOSS/IX operation. If the device becomes inoperative or is removed during BOSS/IX operation, the system will shutdown. 66 9.0 DUMP PROCEDURE The MAI 1800 provides a mechanism to recover from any premature system shutdown situation (Crash). A 'premature shutdown' is typically a power loss or fatal operating system error. When the user attempts to reboot, the system will check all filesystems to see if any of them were left mounted. If it finds a filesystem that was left mounted it will repair that filesystem. Some data may be lost, but the filesystem will be restored to a usable condition. This procedure is automatic and only requires that the user enters an , after reading the message that a filesystem was left mounted. In addition to repairing mounted filesystems, the MAI 1800 recovery program will allow the user to save a copy of the system's memory at the time of the crash. This memory information is called a dump. The rest of this section gives the information required to configure your system for it to dump and save the dump to 1.2MB high-density floppy disks. 9.1 Configuring The System To Dump For the system to produce a dump if it crashes the system configuration file, '/etc/conf' file on the boot partition, has to have dump enabled. The dump enable flag can be set by the use of the '/bin/vconf' command. The use of this command is detailed in section 6. If the system is set for 'nodump', a crash will not produce a dump. Since system dumps help determine the cause of a crash, it is recommended that when a system is setup the dump flag is set on. NOTE: Always have 1.2MB high-density floppy diskettes (they must already be formatted) available for reasons such as a system dump. Two diskettes are required for a system with 1.6MB of memory, whereas three diskettes are required for a system with 2.6MB of memory. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg053 When the system crashes, the monitor terminal will display the crash information, and prompt the user with the following message: Insert diskette number 1 and press when ready. Insert a formatted 1.2MB high-density floppy diskette in drive A. Press to save the dump to floppy. If there is no floppy in the floppy drive or there is a problem writing to the floppy, a message explaining the error and the following prompt is displayed: Restart system dump? (y/n) Ensure that the problem is solved and then enter 'y'. Insert formatted 1.2MB floppies when prompted. NOTE: If is pressed during the dump procedure, the dump is aborted. You are then prompted to "Press 'RETURN' key to reboot:". 67 10.0 CAUTIONS AND WARNINGS The following is a list of problems, warnings, and useful information regarding the MAI 1800 system. Problem: COM1 & COM2 are unsophisticated devices (designed for single user PC environment). Terminals connected to these ports can experience data overruns(BASIC errors 5 and 34) when doing things such as screen transmits or loading function keys with several key codes. COM1 & COM2 should only be used for light-duty terminal use, serial printers (non-MBF protocol) or MODEMS. If COM1 or COM2 is to be used for terminal connectivity, the BAUD rate should be set below 9600. Workaround: Terminals on serial/parallel cards should not be used during periods of heavy system load: o Tape drive operation o Asynchronous communications(ATP) o Heavy usage of the transmit screen 'TR' mnemonic Problem: On a fully configured system (more than 2-3 user) with many processes running, executing the 'TR' mnemonic on COM1 or COM2 could hang the terminal. Most of the time a ctrl + 'c' will terminate the process. However, there is a possibility that the terminal will lock up until the system is rebooted. Workaround: A few suggestions are: 1. Configure the serial port for DTR and XON/XOFF and setup the SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg054 connected terminals in DTR mode. The DTR/CTS method of handshaking is more reliable. 2. In a minimum configured system that only has COM ports, run BASIC applications on the console whenever possible. Also, recommend 8-way cards to customers whenever possible. 3. If the 'TR' is getting alot of parity errors, slowing down the terminal baud rate may help. 4. Run tape operations when the system has the least amount of activity or in single-user mode. 68 Problem: Configuring a 7.2N system using all the maximum numbers (procs, lus, buffers, etc.) in the documentation will cause a crash at a later time. When several of the vconf parameters are set near their maximum, the system requires more memory than is actually available. Workaround: Closely follow the standard configuration chart whenever possible. Problem: Improper use of the MS-DOS 'copy' command will cause corruption of the BOSS/IX partitions. This is possible when a Hard disk is set up solely for BOSS/IX. Example: wd0 was partitioned for BOSS/IX (No MS-DOS partition). wd1 was partitioned for MS-DOS (No BOSS/IX partition). The system is booted from floppy drive A under MS-DOS. At the A> prompt the following is typed: copy *.* c: If this occurs, BOSS/IX will no longer be operable and will need to be re-installed. Workaround: 1. This workaround should be used when the user wants all BOSS/IX on wd0 and all MS-DOS on wd1. Create a small MS-DOS partition on wd0. If MS-DOS files are not going to be stored on wd0, dedicate all but 1 cylinder to BOSS/IX. Example: For a 58MB disk with 976 cylinders, choose option B of the BOSS/IX install menu using 975 for the number of cylinders dedicated to BOSS/IX. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg055 Option B is explained in section 3.3.2 'Initial BOSS/IX Installation' 69 2. This workaround should be used if the user wants MS-DOS coexistent with BOSS/IX on wd0 and BOSS/IX on wd1. Add the statement 'ASSIGN D=C' to an autoexec.bat file. This autoexec.bat file MUST reside on any MS-DOS media from which you wish to boot the system (this includes bootable MS-DOS floppies or the MS-DOS partition on wd0). Refer to the MS-DOS guide for details on the 'ASSIGN' command and autoexec.bat file. If the user wants the same configuration as defined in workaround # 1 but can't afford to give up 1 cylinder, 'ASSIGN C=D' can be used in autoexec.bat files. Problem: A system crash may occur on a 2 hard disk system when the first disk is setup solely for BOSS/IX and the 2nd disk is setup solely for MS-DOS. Workaround: If you plan on using a similar setup, you must setup a small partition on the first drive for MS-DOS. Example: For a 58MB disk with 976 cylinders, choose option B of the BOSS/IX install menu using 975 for the number of cylinders dedicated to BOSS/IX. Option B is explained in section 3.3.2 'Initial BOSS/IX Installation' Problem: When a color monitor is used as the system monitor, the 'BU' and 'EU' (underline mnemonics) will cause the line to be displayed in blue since the hardware for the color monitor doesn't support underline. Workaround: None. 70 Problem: When a monochrome monitor is used as the system console, underline is not supported. Workaround: None. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg056 Problem: SPR #511642 MCS tape commands can cause loss of data for any user running off of the COM1 or COM2 ports. When the MCS tape commands are executed in multi user mode, an error condition occurs for COM1 and COM2. The O.S. reports the error condition back to the port by sending a '!' to the terminal indicating that a parity error has occured. This is a warning to the user that they should stop all processing. At this point there may be a loss of data for the user involved. The '!' will not be sent when BASIC is executing. The ISC 8-way ports are not affected. Workaround: None. It is recommended that backup and restore operations be performed in single user mode. Problem: SPR #511636 SMOUNT returns an incorrect error message. If you select the "mount a filesystem" and don't have a floppy in the drive, the utility returns the error message "Cannot unmount the filesystem. The original floppy is not in the drive." The message should be "Data transfer error or seek error occurred on disk or diskette." Workaround: None. Problem: SPR #511733 Menuedit suspends when trying to modify a non-menu file. Workaround: None. Don't try to edit a non-menu file. 71 Problem: SPR #511838 If a standard serial slave printer is configured but not connected error messages are incorrect. EXAMPLE: 11 is a standard serial slave that is configured but not connected. ADMIN>lpr /.globals l=l1 No error message appears. "The 'l1' printer is offline" message should have been displayed. Workaround: None. Problem: The printer queue can be corrupted as follows: A job listed twice, the second time with an "unknown" state. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg057 Jobs deleted from the queue. Workaround: None. This is an uncommon problem, occuring only as a result of a specific sequence of print commands. Problem: SPR #511882 When running the "msave" utility using the report to file option, it appears that one less file was saved than was listed during the filelist compilation. Actually, the report file is included in the total when the filelist is compiled. However, the report file is not saved. Workaround: None. 72 Problem: SPR #511682 "medit" does not work properly with the text file option. Workaround: None. Users are advised not to use this feature on the 7.2N release. Problem: SPR # 511884 Files that span tapes are not included in file or block totals for the save. No loss of data occurs. Workaround: None. Problem: The 'time of day' is gradually lost when using the MCS unit. Workaround: Reset the time of day after using the MCS. The time of day can be set using the BOSS/IX 'date' command or the MS-DOS 'set date and time' option included on the "Setup and Test" diskette. Problem: The 'System clock rate =' portion of a 'vconf -os' display erroneously shows 16960. No effects will be felt, since this information is not used by the system. Workaround: None. Problem: SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg058 There is a 64KB limit for command line parsing. This limits the number of filenames that utilities can use without resorting to filelists. Workaround: Use a filelist when working with a large number of files. 73 MAI 1800 Software Announcement _ 10.0 (Cont.) Problem: (This problem refers to international character sets on the system console). Under 7.2N pressing the '*', '-', and '+' keys on the U.S. QWERTY system console keyboard generate duplicate codes as when pressing the '*', '-', and '+' keys on the numeric keypad. If any of the 3 keys on the QWERTY portion of the keyboard are changed through translation tables to represent an international character, the corresponding key on the numeric pad will change as well. Workaround: None. Problem: Error=2 trying to save a file under BASIC in certain circumstances. Workaround: The growth factor of a newly created program file must be set to at least 1. Problem: 'msave' utility won't label a new tape. Workaround: Use the 'mcslabel' command to label tapes. Problem: Tape doesn't rewind at proper time when using 'msave'. Workaround: Use the 'mcslabel' command to label tapes. Problem: 'time of day' may drift if the CPU RTC(real time clock) is not accurately adjusted. Workaround: SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg059 Have your service personnel adjust the RTC to 32,76800Khz + or - 0.00006Khz. Also, update the CPU clock via software at least once a week. 74 MAI 1800 Software Announcement _ 11.0 DOCUMENTATION The following manuals are currently available for the MAI 1800 and can be ordered: o MAI 1800 User Guide - M6203A o BOSS/IX 7.2 User Reference - M6210A o BOSS/IX 7.2 Technical Reference - M6224A o MAI 1800 Service Manual - M8112A The MAI 1800 User Guide, and Service Manual are specific to the MAI 1800 product. The BOSS/IX 7.2 User Reference Manual and Technical Reference Manual are generic to BOSS/IX 7.2. 75 MAI 1800 Software Announcement _ 12.0 27XX/37XX BATCH EMULATION (TBC) ************************************************************ * NOTE: TBC is part of the 7.2N Base media but it is not * * a released product at this time. Availability * * of TBC for the 1800 will be announced in a * * General Marketing Announcement. * ************************************************************ The 27xx/37xx Batch Emulation package (TBC) is available on 7.2N. TBC supports transmissions of files between MAI Basic Four (MBF) and non-MBF systems using the IBM binary synchronous protocols of 2770, 2780, 3770, and 3780. TBC on 7.2N is written in Basic and is compatible to TBC on all MBF systems; MPx, 2000/3000, and 13xx. Users familiar with the BCOM application of TBC on other MBF systems will find that the 7.2N version is identical in operation. In addition, 7.2N offers autodial and scheduling features which allow operation of BCOM in unattended mode. Because TBC on the 1800 runs on a separate communications controller board, the maximum baud rate supported is 9600 BPS. TBC on the 2000/ 3000 series, however, supports a maximum baud rate of 4800 BPS since the synchronous port is on the CMB and must share the CPU bandwidth with other tasks. 12.1 Hardware/Software Requirements TBC requirements for hardware and software are as follows: HARDWARE 1800 CCA MBF ICC/186 Communications Controller Cable from communications controller to synchronous modem SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg060 Synchronous modem compatible to modem of remote system Serial port for autodial use (optional) Cable from serial port to autodial unit (optional) Automatic Calling Unit - serial (optional) SOFTWARE Base Operating System (EOS, EUT, EBS) 27xx/37xx Batch Emulation package (TBC) Configuration Record with 1 communications port configured 76 MAI 1800 Software Announcement _ 12.2 Hardware Installation 12.2.1 MBF ICC/186 Communications Controller The communications controller board must be installed for TBC to operate. The board must be configured with the following jumper and switch settings: JB1 - jumper in position 6; all other positions should not contain any jumpers JB2 - jumpers in position 3 and 4; nothing in 1 and 2 JB3 - jumpers in position 1 and 4; nothing in 2 and 3 JB4 - jumper to the right in position 4; jumper to the left in positions 1, 2, 3, 5, 6 JB6 - no jumper JB7 - no jumper J2 - no jumper Switch Setting - positions 2, 3, 5, 6, 7 ON; positions 1, 4, 8, 9, 10 OFF 12.2.2 Cables Cable 916132 is used to connect the communications controller board to an external synchronous modem. If the auto-dialing feature is used, a cable from a serial port must be connected to the serial auto- matic calling unit (ACU). If the serial port is on the serial/parallel board, the serial port to modem cable, 916073, is used. If the serial port is on the 8-way board, an 8-way to modem cable, 916117 with cross pin adapter, must be used. 77 MAI 1800 Software Announcement _ 12.2.3 Recommended Modems and Automatic Calling Units SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg061 The following modems have been tested with the 7.2N TBC product: Universal Data Systems (UDS) 201C - 2400 Baud modem Bell 201C - 2400 Baud modem Paradyne 2400 FDX PLUS standalone unit - 2400 Baud modem with integrated ACU The following ACU has been tested with the autodialing feature of the 7.2N TBC product: UDS 801C ACU in conjunction with the UDS 201C modem Paradyne 2400 FDX PLUS standalone unit (modem/ACU) 12.3 Software Installation 12.3.1 TBC installation o Install the base operating system (EOS, EUT, EBS) following instructions documented in section 3 of this Software Announcement. o Insert the TBC tape cartridge or floppy (labelled BASE 11 of 11) in its appropriate drive and type: admin>install cs TBC (for tape) or admin>install /dev/fd0 TBC (for floppy) o A prompt requesting the TBC public key for this system will display. Type in the public key provided on a certificate with the TBC media. If the certificate is not readily available, the installation process may continue. Press 'CR' at the prompt and the TBC product will be installed. Use of the product will not be allowed, however, until a valid key is input. To input the public key after the product is installed, type: admin>install_key /etc/level/TBC The user will be prompted to enter the TBC public key. 78 MAI 1800 Software Announcement _ 12.3.1 (Cont.) o During the installation of TBC, a prompt will display requiring the user to press '1' to install the TBC operating system on the boot partition, or any other key to install the TBC operating system to the root partition. It is recommended if TBC is to be run on a regular basis, a '1' is selected. This procedure will automatically load the TBC operating system, Cbossix, onto the boot partition and rename it as the SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg062 standard default operating system, bossix. When the user presses 'RETURN' at the boot prompt, the TBC operating system will be loaded. A response other than '1' will install Cbossix onto the root partition as /sys/Cbossix. The user must manually copy /sys/Cbossix from the root to the boot partition and do an alternate load of /sys/Cbossix in order to run TBC. 12.4 Configuration 12.4.1 System Configuration o Set up the system configuration file for the appro- priate hardware/software and number of users for this system. Follow instructions in section 6.0 of this announcement. o Verify that the configuration is set for at least 8 Lanbuffers and 8 dynamic sockets for TBC. 12.4.2 Port Configuration o Run the 'configure' utility to configure port 20 as a 'communications port'. o If the autodialing feature is to be used, configure a serial port as a DT7270 with the default configura- tions. This serial port will be connected to the ACU. 12.5 Operation Reboot the system with the TBC operating system, Cbossix. After a 'CR' is pressed to continue with system startup, the system name and system serial number is displayed and followed by a message identifying the operating system level. If the TBC operating system is loaded, a CB will display next to the level: Operating System: EOS2Nxx CB , BOSS/IX release 7.2N TBC must be run in multi-user mode. Verify that during multi- user start-up, the network service manager is started by the command /net/netinit in the /etc/startup file. Typing 'ps -a' in command mode will display the active processes; verify that /net/rsm is started. 79 MAI 1800 Software Announcement _ 12.5.1 Menu Access o From the System Utilities Menu, select option 7, Communications. o Select the desired TBC operation: 1. Batch Communications Emulator - brings up the BCOM autoprompt utility 2. Local status log SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg063 - displays session logs 3. JCL records - generates/maintains Job Control files 4. BCOM prefix (BCOMPFX) maintenance - sets program and data prefixes for each terminal 5. Auto-dial Scheduler (ACS, ACUTD) - generates scheduler list and sets time and date stamps for execution 12.5.2 Command/Basic Access o From command mode, type: admin>cd /tbc/BCOM admin>basic s=128 >RUN "BCOM" Batch Communications Emulator >RUN "LSLOG" Local Status Log utility >RUN "UJCL" JCL maintenance utility >RUN "BCOMPFX" BCOM prefix utility >RUN "ACUTD" ACU scheduler list utility >RUN "ACS" ACU scheduler list activation utility 12.5.3 Program Access o BCOM can be accessed from a user written BASIC program. The following parameters must be set prior to running BCOM: 100 A$="autoprompt name" 120 P$="program to run after BCOM terminates" 130 O$="Y or N" Y for operator intervention N for no operator intervention 140 Q$="HH:MM" length of time to remain at 'Line Connection Pending' 150 RUN "SBCOM" runs BCOM 80 MAI 1800 Software Announcement _ 12.6 For Your Information The following is a list of problems, warnings and useful information relating to TBC on 7.2N. Where possible, work-around solutions have been provided. Problem: ESCAPE key abort while communications is in progress may cause the next BCOM session to generate a "Con- troller Port Busy" error message. Work-around: Run BCOM again and start communications. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg064 Problem: If the communications controller board is not installed in the 1800, an error message will be posted in the /etc/sys.log file during multiuser startup. In addition, when BCOM starts communications, the error message "BAD KERNEL" is generated and the session is terminated. Work-around: Install the communications controller board. Problem: DSR/CTS drops can be experienced after a "Line Connection Pending" and occasionally during transmitting/receiving a file when Paradyne FDX modems are used. Work-around: Specify at least 5 retries in the Auto-Restart option in BCOM. NOTES: o BCOM has been tested running concurrently with ATP with no problems. o TBC is supported as a medium for the Intersystem Transport package which allows transmission of files between MBF systems with a different ASCII character set. o At least one communications port must be configured in the system's configuration record. o The correct public key for TBC must be installed for TBC to operate. 81 MAI 1800 Software Announcement _ 12.7 Documentation For further information on TBC, refer to the "BOSS/IX Transportable Batch Communications (27xx/37xx) User Guide" (M6353C). For information on the Intersystem Transport Package, refer to the "Intersystem Transport Package User Guide" (M6354D). 82 ORIGINATOR: Dan Wenzel SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB033 Pg065 FIB 00034 12/29/87 *** 7.3A, Different O.S. tape for MAI 2000 and 3000 [ WPS 415 ] *** There are system-specific differences in the 7.3 O.S. tape. Therefore, the tape being used must be for the system type being installed, or the install will fail. If you are upgrading a MAI 2000 system, you must use the 7.3A 2000 O.S. tape, and if you are upgrading a MAI 3000 you must use the 7.3A 3000 O.S. tape. The 2000 and 3000 O.S. tapes are not interchangeable. ORIGINATOR: Julia Shreve SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB034 Pg001 FIB 00035 10/24/88 *** Killed Print Job Still Prints [ WPS 417A ] *** A condition has been reported from the field. When you kill a spooled print job, the job continues to print. This can occur when the print job is killed using either the 'pqueue' utility or the 'lpmaint' command. If the despooler has the file that is being printed open while the print job is being killed, the print job will disappear from the queue and from the '/etc/_queues' directory, but will continue to print. In order to stop the job from printing, the user must do a 'ps -a' in command mode, and 'kill' the PID number of the '/sys/lpd printer_name' process, where 'printer_name' is the name of the printer to be stopped. ORIGINATOR: Julia Shreve SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB035 Pg001 FIB 00036 02/12/88 *** 'EP' functionality change at level 7.3 [ WPS 418 ] *** The Expanded Print mnemonic, 'EP', works differently on the Level 7.3 OS than on prior levels. On 7.3 there are two differences: o The 'EP' must be a the beginning of the print line. o A Line Feed mnemonic, 'LF', in a print statement does not clear the expanded print for the new line. A new print statement does. If you are using a print statement that has an embedded 'EP', the data after the mnemonic in the statement will be expanded instead of the current print line. If a 'LF' occurs after the 'EP' the next printed line will be expanded. This will be fixed in a future release. ORIGINATOR: Pamela Thatcher SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB036 Pg001 FIB 00037 02/16/88 *** Remove without key= on MAGNET at 7.3 fails [ WPS 420 ] *** 'KEY=' is now an option to REMOVE an EXTRACTed record in BASIC on Level 7.3. If you are removing records from a file via MAGNET, the 'KEY=' is not optional. BASIC will suspend if the 'KEY=' is not included in the REMOVE statement, even if the record has been EXTRACTed. However, This should not affect any existing application because until now 'KEY=' was required, not optional. The workaround for REMOVEing records from a file via MAGNET is to save the key and use the KEY= option in the REMOVE statement. ORIGINATOR: Pamela Thatcher SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB037 Pg001 FIB 00038 02/16/88 *** form= option changes on 7.3 OS [ WPS 424 ] *** Problem: Every OPEN of a spooled printer using the 'forms=form_name' option requires a form change. Cause: This is because a 'vfu' load is sent to the printer on every open with a special form. The despooler does not check to see if the specified form is the same as the last form. Workaround: Turn off spooling. Non-spooled pritners receive a 'vfu' load only when specified in the OPEN statement. Future: This will be fixed in a future release. ORIGINATOR: Pamela Thatcher SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB038 Pg001 FIB 00039 03/29/88 *** Release 7.4A Software Announcement [ WPSS 156 ] *** Level 7.4A of BOSS/IX is now available. It is the recommended Operating System for MAI 2000 and MAI 3000 systems, and is the only Operating System for the MAI 4000 system. The 7.4A O.S. is derived from the 7.3A O.S., so the following list of enhancements/corrections are also enhancements on the 7.3A O.S. release. o Shared libraries o 1/2 Inch Tape Boot and Install o Merged tape commands and utilities o UPD (Universal Printer Driver) o Console configuration changes o vconf file changes o System configuration record format changes o System dump changes o BB86 o Diagnostic partition o New user error logger o File integrity flag o Bad block retirement This Software Announcement contains general information about the Level 7.4A BOSS/IX Operating System. Installation and upgrade procedures are fully documented in this announcement. Also, this document has sections on enhancements and corrections to BOSS/IX, approximating memory requirements, memory usage, a list of new documents available for BOSS/IX, a list of the lowes t acceptable revision levels for hardware, and a list of warnings and cautions and a way, if any, to work around them. Warning: When installing this release on a MAI 3000/4000 system, with an O.S. level prior to 7.3, the system serial number MUST be reinstalled using the new 2000/3000/4000 SSN program. DO NOT attempt to upgrade a MAI 3000 system without reinstalling the system serial number using the new MAI 2000/3000/4000 SSN program. Warning: In order to install the systems properly, the 7.4A 2000 O.S. tape must be used to install a MAI 2000 system, and the 7.4A 3000/4000 O.S. tape must be used to install the MAI 3000 and MAI 4000 systems. Warning: With BB86, BASIC programs are not backwards compatible. You must use the conversion facilities to take the programs backwards to a 7.2 or prior release. It is recommended that you read this document before installing Level 7.4A. For information on how to order Level 7.4A refer to Marketing Announcement 578 for the United States or 378 for International. NOTE: Throughout this document the references to '7.2' include 7.2A/B/C/D/D1. Copyright 1988 MAI Basic Four, Inc. All rights reserved TABLE OF CONTENTS 1.0 OVERVIEW 2.0 INSTALLATION AND UPGRADE OF THE OPERATING SYSTEM, SOFTWARE AND DIAGNOSTICS SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg001 2.1 Installing Diagnostics on the Disk 2.1.1 Introduction 2.1.2 Disk Diagnostic Installation Procedure 2.1.3 Loading Disk Diagnostics 2.2 Installation of the Operating System. 2.3 Upgrading 2.4 Product Installation/Upgrade 2.4.1 EOS - Operating System 2.4.2 ECC "C" Compiler 2.4.3 MAGNET (ENT) and File Transfer Facility (FTF) 2.4.4 27xx/37xx Batch Emulation (TBC) 2.4.5 Asynchronous Transport Package (ATP) 2.4.6 3270 Bisynchronous (B32) 2.5 Security Configuration Record 2.5.1 7.4A Configuration Record Request Sheet 3.0 LEVEL 7.4A BOSS/IX ENHANCEMENTS/CORRECTIONS 3.1 Operating System (EOS) 3.1.1 Shared Libraries 3.1.2 1/2 Inch Tape Boot and Install 3.1.3 Merged Tape Commands and Utilities 3.1.4 Console Configuration 3.1.5 vconf Configuration File TABLE OF CONTENTS 3.1.6 System Security Configuration Record Format Change 3.1.7 System Dump Changes 3.1.8 Reduced Disk Requirements 3.1.9 New System Error Logger 3.1.10 File Integrity Checking 3.1.11 Configurable Number of Ghost Tasks 3.1.12 Improved BOSS/IX Swapping Performance 3.2 System Utilities/EUT SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg002 3.2.1 frepair Utility (bad block retirement) 3.2.2 Configure Utility 3.2.2.1 Configure the System Console 3.2.2.2 New Terminal Types 3.2.2.3 Configuring Printers 3.2.3 pparams Utility 3.3 BASIC (EBS) 3.3.1 Business BASIC 86 3.3.2 BASIC on 7.4 is not backward compatible with 7.2 3.3.3 Changed Functionality 3.3.4 BOSS/VS & BOSS/IX Compatibility Notes 3.3.5 Unsupported Mnemonic on PT-4220 3.4 3270 Bisynchronous Product (B32) 4.0 NEW PRODUCTS IN LEVEL 7.4A 4.1 Universal Printer Driver (UPD) 4.2 PDF (Printer Definition File) 5.0 FOR YOUR INFORMATION 5.1 Operating System (EOS) TABLE OF CONTENTS 5.2 BASIC (EBS) 5.3 FTF via LAN and X.25 5.4 MAGNET via LAN and X.25 5.5 Intersystem Transport Package (EIT) 5.6 3270 Bisync 6.0 MEMORY REQUIREMENTS AND OPERATING PARAMETERS 6.1 Approximating A System's Memory Requirement 6.2 Recommended Values for "vconf" 6.2.1 Model 2000 Parameters 6.2.2 Model 3000 Parameters 6.2.3 Model 4000 Parameters 7.0 MEMORY USAGE SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg003 7.1 Calculating A System's Memory Requirements 7.1.1 Model 2000 7.1.1.1 Example of How to Calculate a System's Memory Requirement 7.1.2 Model 3000 and 4000 7.1.2.1 Second Example of How to Calculate a System's Memory Requirement for Model 3000 and 4000. TABLE OF CONTENTS 7.2 Calculating BOSS/IX Table Space and Dynamic Work Space 7.2.1 Model 2000 7.2.2 Model 3000 7.2.3 Model 4000 8.0 NEW & UPDATED MANUALS FOR LEVEL 7.4A 9.0 LOWEST ACCEPTABLE REVISION LEVELS (LARL) 10.0 HELPFUL HINTS 1.0 OVERVIEW The level 7.4A Release contains the following enhancements/features:. o Shared libraries o 1/2 Inch Tape Boot and Install o Merged tape commands and utilities o UPD (Universal Printer Driver) o Changes to console configuration o Changes to vconf file o Changes to system configuration record format o Changes to system dump procedure o Diagnostic Partition o Reduced disk requirements o Reduced memory requirements o New system error logger. o File integrity checking o Bad block retirement SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg004 o BB86 --- Business BASIC 86 - Multi-key files - Terminal driver enhancements - 4 character BFS device names o Improved BOSS/IX swapping performance o New printers supported o New terminals supported o Customer configurable number of form feeds before each spooled print job o Enhancements to 3270 Bisynchronous o Configurable number of Ghost tasks 2.0 INSTALLATION AND UPGRADE OF THE OPERATING SYSTEM, SOFTWARE AND DIAGNOSTICS Following are the steps to install or upgrade the Operating System, customer's software and system diagnostics. Before installing or upgrading the system it is recommended that you read these instructions completely. Warning: When installing this release on the MAI 3000 system, with an O.S. level prior to 7.3, the system serial number MUST be reinstalled using the new 2000/3000/4000 SSN program. DO NOT attempt to upgrade a 3000 system without reinstalling the system serial number using the new 2000/3000/4000 SSN program. NOTE: To do an ALTERNATE LOAD: On a 2000 system, enter ^C at the reboot prompt. On a 3000/4000 system, enter 2 at the bootstrap menu. 2.1 Installing Diagnostics on the Disk 2.1.1 Introduction Diagnostic programs for your system may be contained on the system fixed disk. Your disk should have diagnostics installed in order to test the tape subsystem included with your system. The purpose of these tape diagnostics is to troubleshoot and test your tape subsystem, when you cannot load diagnostics from the tape subsystem. You may optionally install all of the diagnostics programs on your disk. The system diagnostics are contained on a dedicated diagnostic partition. This diagnostic partition is inaccessible to user programs, and is actually beyond the reach of the user disk area. For this reason, the diagnostic programs cannot be accessed by the file system, yet they are maintained by a Diagnostic Executive Program. If your system will not boot diagnostics from disk, and the O.S. is already installed, the file system SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg005 must first be backed up. Once backed up, a diagnostic partition can be reserved. Once the diagnostic partition is reserved, diagnostics can be installed from the same bootable diagnostic tape. Afterwards the file system must be restored. Use the following procedure to install the diagnostics on your fixed disk. 2.1.2 Disk diagnostic installation procedure Step 1: Backup your disk If your file system is already installed on the disk you must do a complete file by file backup. If your file system has not been installed yet, install your diagnostics first and then install the file system. Step 2: Boot diagnostics from tape Install the diagnostic tape. Do an alternate load. For the boot device enter "cs", for MCS or "ts", for MTS. For the system file enter . Step 3: Enable service mode When the 'exec' is loaded, it will auto-size the system and display the program prompt: Any 'exec' commands can be entered at this time. To begin the installation of diagnostics, you must first enable the service commands. At the 'exec' prompt, enter: service and a RETURN. This will allow use of the service commands. 'exec' will then ask for the service password, enter: b4bus (or qwerty if b4bus doesn't work) and a RETURN after which, the prompt will again be displayed. Step 4: Update the superblock on the disk. The superblock on the disk must be updated to reserve a section of the disk for the diagnostics. Enter the superblock initialization command: sbinit and a RETURN to initialize the superblock for the diagnostic partition. EXEC will ask you if you want to destroy the existing disk partition information and the disk directory name. Any (y/n) responses are single character responses, and DO NOT require a . Entry of the "sbinit" command will cause EXEC to ask: Destroy: "volume ID" (y/n)? SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg006 2.1.2 (Cont.) where "volume ID" is the current volume ID contained in the superblock. A "y" response will allow you to initialize the superblock for the diagnostic partition. A "n", no response will return you to the prompt. Enter: y and EXEC will ask for the number of sectors to reserve on the disk for the diagnostics: Diagnostic Partition size (in sectors)? Enter the number of sectors desired as follows: a) To install all available diagnostics, enter: 1300 b) To install tape diagnostics, enter: 200 EXEC will then ask about the directory: Destroy: "partition name" (y/n)? Enter the character "y" to destroy the current disk directory to have it initialized for a subsequent install, or "n" to retain the current partition name. If you wish to change the name of the disk diagnostic partition, enter: y and EXEC will then ask: Disk name: Enter the new disk name, up to 12 characters in length, and . This new name will be displayed every time you display the directory. EXEC will then display: Initializing: "disk name" where "disk name" is the new name you just entered. The diagnostic partition is now defined. 2.1.2 (Cont.) Step 5: Copy diagnostics from tape to disk Once the diagnostic partition is defined, diagnostics can be installed on the disk. You now can determine which files to install on the disk by listing the SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg007 contents of the tape. This is optional if you are going to install all of the diagnostics. To obtain a list of file names on the tape, enter: ltape To install the diagnostics on the fixed disk, enter: install and a RETURN to install ALL of the diagnostics. To install a particular diagnostic enter: install "file" and a RETURN where "file" is the file name to install on the disk. Use the list of files obtained by the "ltape" command to determine which files you want to install. The file EXEC, SIT, MCS and/or MTS are the minimum diagnostic files to install. When you enter the "install" command, to install all of the diagnostics, EXEC will prompt: Destroy: "disk name" (y/n)? where "disk name" is the name of the disk entered during the "sbinit" command sequence. Entry of the character "n" will cause the current directory name to remain and the install process to begin. Entry of a "y" character will cause EXEC to ask you for the new disk name as in the "sbinit" command. Maintain the current directory from the "sbinit" sequence, enter: n and the install procedure will begin. 2.1.2 (Cont.) As the diagnostics are installed on the disk, EXEC will display the current program being copied from the tape, and the size in sectors. After the sector size display, the file is written to the disk and the directory updated. When all the files are installed, EXEC will again display the prompt: Step 6: After the diagnostics are installed on the disk, you may want to list the diagnostics on the disk. Enter: ldisk and to obtain the list of the diagnostic SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg008 files on disk. You should test the bootstrap capability now, to see that you can boot diagnostics from the disk. Enter: shut and to obtain the bootstrap menu. Step 7a: 3000 and 4000 only Do an alternate load, for the boot device enter: wd0, for system file enter: diag Step 7b: 2000 only The EOS product must be installed to boot to the diagnostic partition on the 2000 system. The file /sys/diag exists on the EOS product. This file is required to boot to the diagnostic partition. After you have installed the EOS product: Do an alternate load, for the boot device enter: wd0, for the system file enter: /sys/diag. NOTE: Installing diagnostics on the disk has taken disk space away from the user available disk space. The device capacity is reduced to provide room for the diagnostics. 2.1.3 Loading Disk Diagnostics When the system is first powered up, or after the system is shutdown, the user must perform an alternate load sequence in order to load diagnostics from disk. The system has the logic to either bootstrap the Operating System or the Diagnostic Executive. The loader programs for each are in different sections of the disk. The diagnostic loader and the associated directory of files for the diagnostics are contained in the diagnostic partition. Thus the diagnostic partition is completely self contained, and separate from the Operating System. The operation of loading diagnostics from the fixed disk and from the MCS/MTS tape are similar. The only difference is in the alternate load sequence, as discussed in the following sections. The diagnostics contained on your fixed disk cannot be run while the Operating System is up and running. The diagnostic programs are all off-line programs and require you to first shutdown your system, regardless if you load from MCS/MTS tape or from the fixed disk. After running diagnostics, entry of the diagnostic "shutdown" command will allow you to reload the Operating System. The normal indication that diagnostics are not on the SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg009 disk, is the error message "invalid loader detected" when a diagnostic boot is attempted. To access the diagnostics, once they are installed perform an alternate load. For boot device enter 'wd0', for system file enter 'diag' for the 3000/4000 system or '/sys/diag' for the 2000 system. This will get the '' prompt. Any file name listed by the 'ldisk' command can now be loaded by entry of the command: load file and , where "file" is any file listed. 2.2 Installation of the Operating System The following steps outline the 7.4A BOSS/IX installation procedures for tape and floppy diskette. This "installation" procedure is to be used when installing a new system, or installing the OS after a diagnostic partition has been created, or when upgrading from 7.1. NOTE: The 'packaging' of the products has changed. A 'base' tape will no longer be distributed. Instead, you will receive a 'customer' tape. These products are on the 'customer' tape: EOS EUT EBS EXT EBA IDB TBC EIT ENT FTF INT EB2 CBR CBD UPD PDF B32 X25 EDB With this new packaging it is no longer necessary to ship a tape for each product ordered. Instead, a Public Key certificate is generated for each product purchased. WARNING: When installing this release on the MAI 3000 system, with an O.S. level prior to 7.3, the system serial number MUST be reinstalled using the new MAI 2000/ 3000/4000 SSN program. DO NOT attempt to upgrade a MAI 3000 system without reinstalling the system serial number using the new MAI 2000/3000/4000 SSN program. Step 1: Using the mcssave/mtssave (7.1 & 7.2) or tsave (7.3) command or the floppy diskette save utility, do a file by file back up of all user programs and data files. Using the configure utility, print out the port configurations; using the oprinfo utility, print out the operator information report. These will need to be re-entered after the install is complete. Step 2: First step is to install the boot partition. Place the customer tape into the tape drive. Or, if you are doing floppy installation insert the installation floppy into drive fd0. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg010 NOTE: The 7.4A 2000 O.S. tape must be used to install the MAI 2000, and the 7.4A 3000/4000 tape must be used to install the MAI 3000 and MAI 4000. 2.2 (Cont.) Do an alternate load. At the 'boot device:' prompt type "cs" for MCS, "ts" for MTS or "fd0" for floppy diskette, then press . Press again at 'System file:' prompt. NOTE: MTS requires a 4.2 boot prom on the MAI 2000. Step 3: Screen displays loading messages, then the Install Utility Menu. Select Option 'A', then . Option 'A' re-defines all the wd0 partitions and copies a new boot partition to disk. Special note for floppy diskette installations, make sure your BOOT floppy diskettes are inserted in the correct sequence according to the BOOT number. After one floppy diskette is complete make sure you change floppy diskettes before responding to the prompt on the screen. Step 4: After the boot partition is installed the configuration record must be installed. When the message 'OPTION>' is re-displayed put the configuration record tape or floppy in the tape drive or floppy drive. Use option 'D' to install the configuration record. After the configuration record is installed enter '^D' and then 'shutdown'. Step 5: After the configuration record, the EOS product must be installed. Rebooting the system at this time automatically roots to the boot partition. Enter the correct date; the screen will then display the 'ADMIN>' prompt, type "osinstall cs" for MCS tape, "osinstall ts" for MTS tape and "osinstall fd0" for floppy diskette. This process uses the parameters in the Super Block to define the root filesystem, then copies the EOS product to the root partition on disk. After the EOS product is installed you are instructed to reboot again. 2.2 (Cont.) WARNING: If the 7.4A configuration record for the system is not installed you will be able to access the boot partition only. Step 6: Reloading of the system at this time automatically reloads and roots to the root partition. Enter either the current date, or a , if the date is correct. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg011 At the 'ADMIN>' prompt, type "install cs EUT EBS", for MCS tape, "install ts EUT EBS" for MTS tape or "install fd0 EUT", for floppy diskette. NOTE: When working with tapes all products listed on the customer tape can be installed with one command line. When working with floppies you must install one product at a time in the following order: EUT, EBS, EXT, EBA then optional products in any order. Products that are chargeable and not part of the base system will have key codes that you must enter during or after (using '/bin/install key') installation before you can use that product. If the key certificate did not come with the media, contact the customer or service representative in your area for instruction about how to obtain this key code. NOTE: When upgrading from 7.1 or 7.2, the port configuration utility, 'configure', should be used to set the terminal type for for the console. This step cannot be done until the operating system and utilities (EUT) have been installed. Step 7: The '/etc/conf' file on the boot partition needs to be customized to meet your needs. (See Section 7.0 'Memory Usage' for instruction on how to customize the '/etc/conf' file.) 2.2 (Cont.) Step 8: After you have copied all your products to disk and have customized the '/etc/conf' file, your system is ready for use. Step 9: If you have user program and/or data files to be restored, use the 'dups=skip' option of the trestore command or the 'skip' option in the 'duplicates' parameter of the trestore or drestore utility to avoid writing "old" files over your new 7.4A files. If you are restoring 7.1 Basic programs, use the csave command to convert them to 7.4A Basic. 2.3 Upgrading The following steps describe the 7.4A BOSS/IX upgrade procedures for tape and floppy diskette. NOTE: This upgrade procedure is for 7.2/7.3 only. If you are upgrading a 7.1 OS level system refer to section 2.2 "INSTALLATION OF THE OPERATING SYSTEM". WARNING: When installing this release on a MAI 3000 system, with an O.S. level prior to 7.3, the system serial number MUST be reinstalled using the new MAI 2000/ 3000/4000 SSN program. DO NOT attempt to upgrade a SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg012 MAI 3000 system without reinstalling the system serial number using the new MAI 2000/3000/4000 SSN program. Step 1: Using the mcssave/mtssave command or the floppy diskette save utility, do a file by file back up of all user program and data files. Using the configure utility, print out the port configurations; and, using the oprinfo utility, to print out the operator information report. 2.3 (Cont.) Step 2: When upgrading from 7.2 to or 7.3A, the following should be done. This means that a default /etc/conf file will be installed on the boot partition. To preserve your config- uration parameters so you don't have to re-assign them with the vconf command after the update is complete copy the /etc/conf file from the boot partition to the root partition: >mount /dev/boot /mnt >copy /mnt/etc/conf /etc -v >unmount /mnt NOTE: This step is optional. If you do not copy /etc/conf to the root partition you will have to re-enter the parameters. Warning: Some of the vconf parameters have changed and will need to be re-entered. Refer to table 6C for the 2000 and 6D for the 3000/4000 recommended parameter values. When upgrading from 7.1 to 7.4A, it is recommended to boot off the install media and choose Option 'A' to install the boot and default partitions. NOTE: It is essential that a file by file backup is performed prior to upgrading from 7.1 to 7.4A. The upgrade from 7.1 to 7.4A will destroy all files on the root partition. Step 3: Install the boot partition. Insert the customer tape into the tape drive. Or, if you are doing floppy installation insert the installation floppy into drive fd0. Do an alternate load. At the 'boot device:' prompt type "cs" for MCS, "ts" for MTS or "fd0" for floppy diskette, then press . Press again at 'System file:' prompt. NOTE: MTS requires a 4.2 boot prom on the MAI 2000. 2.3 (Cont.) Step 4: SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg013 Screen displays loading messages, then the Install Utility Menu. When upgrading from 7.2 or 7.3, select Option 'B', then . Option 'B' will only copy an image on the boot partition from the tape or floppy to disk. This process will ensure that your system has all the up-to-date and proper MACROs and system files on the boot partition. Special note for floppy diskette installations, make sure your BOOT floppy diskettes are inserted in the correct sequence according to the BOOT number. After one floppy diskette is complete make sure you change floppy diskettes before responding to the prompt on the screen. Step 5: NOTE: If you are not presently booted off a tape or floppy diskette, refer to step 3 in section 2.3. After the boot partition is installed the configuration record must be installed. When the message 'OPTION>' is re-displayed put the configure record tape or floppy in the tape drive or floppy drive. Use option 'D' to install the configuration record. After the configuration record is installed enter '^D' and then 'shutdown'. WARNING: If the 7.4 configuration record for the system is not installed you will be able to access the boot partition only. Step 6: Do an alternate load. At 'Boot device:' prompt, ''. At the 'System File:' prompt, enter ",/etc/boot.conf". Step 7: The above alternate load will re-load and root the operating system to the boot partition. Enter the correct date or '' if the date is correct. Insert the base system tape containing EOS, EUT, EBS or the floppy diskette EOS #1. When upgrading from 7.2 or 7.3 to 7.4A, at the 'ADMIN>' prompt type "osupdate cs" for MCS tape, "osupdate ts" for MTS tape or "osupdate fd0" for floppy diskette. 2.3 (Cont.) For floppy diskette upgrades the screen will prompt you when to insert the next diskettes. Step 8: After the procedure is complete you have the option of restoring the default system configuration files to the upgraded root then to the boot partition. This is done by typing "/sys/installetc". This procedure allows the operator to select which system files he/she needs to restore. Please note if this is done all system files that are restored will be new and will have to be re-updated to reflect the needed system information. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg014 Example: If an 'sys/installetc' was performed, and '/etc/passwd' is re-installed the operators will have to be redefined. Following, find a list of the files that can be installed using 'etc/installetc' and the means to modify the files for your system: etc/class, /etc/defaults, /etc/forms: These files are used when printing and can be customized by going to the 'ut.printer' menu and using option 5 'Printer parameters' or using the program 'pparams'. /etc/conf: This file contains your system configuration parameters and is changed by using the '/bin/vconf' command. /etc/exem, /etc/logm, /etc/motd: These files print to the screen at the time of log in and can be modified by the use of the '/bin/ved' command. /etc/passwd: This file contains your operator information and is updated by going to the 'ut.system' menu and using Option 3, (Operator information) or by using the program 'oprinfo'. /etc/ports, /etc/printers, /etc/terminals: These files contain the terminal and printer configuration parameters and are updated by going to the 'ut.system' menu and using Option 1, (Port configuration) or by using the program 'configure'. 2.3 (Cont.) /etc/sinit, /etc/startup: These files are executed at system load time and can be modified by the use of the '/bin/ved' command. /etc/shtdwn: This file is executed when the system is being shutdown and can be modified by the use of the '/bin/ved' command. Step 9: If you skipped step 2, then skip this step also. Otherwise, mount the root partition and copy the /etc/conf file back down to the boot. Then run the vconf command on it to convert it to 7.4A format. >mount /dev/root /mnt >copy /mnt/etc/conf /etc -v >vconf -save /etc/conf >unmount /mnt NOTE: This must be done prior to rebooting the system. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg015 Now when you reboot your customized /etc/conf file will be used. Beware that some of the vconf parameters have changed and will need to be re-entered. Refer to table 6C for the 2000 and table 6D for the 3000 recommended parameter values. Step 10: Next shutdown the system and do a normal boot of the system. Enter the correct date or press '' if the date is correct. If you are upgrading from MCS, at the 'ADMIN>' prompt type "install cs EUT EBS", press ''. If you are upgrading from MTS, at the 'ADMIN>' prompt type "install ts EUT EBS", press ''. The system will automatically install both EUT and EBS. If you are upgrading from floppy diskette, insert the first floppy of the EUT set. At the 'ADMIN>' prompt type "install fd0 EUT". Once EUT is complete use the same routine to install EBS and any other products. NOTE: When working with tapes all products listed on the customer tape can be installed with one command line. 2.3 (Cont.) Products that are chargeable and not part of the base system will have key codes that you must enter during or after (using '/bin/install key') installation before you can use that product. If the key certificate did not come with the media, contact the customer or service representative in your area to instruct you in where to call for this key code. NOTE: When upgrading from 7.2, the port configuration utility, 'configure', should be used to set the terminal type for for the console. This step cannot be done until the operating system and utilities (EUT) have been installed. Step 11: There have been some changes in some of the system files between 7.1, 7.2, 7.3 and 7.4. For this reason you are required to make some configuration changes to the system. These changes are identified in the following section on a product basis. If you are not installing a particular product you need not worry about the configuration changes for that product. If you are installing a product then you must following the section that covers that product. Once the upgrade has been performed, be especially careful when restoring files back down from a 7.2 tape. If you should accidentally restore a changed configuration file it is best to go back and install that product again from the system tape, being careful to follow the configuration change steps for that product. Step 12: SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg016 If you have user program and/or data files to be restored, use the 'dups=skip' option of the trestore command or the 'skip' option of the 'duplicates' parameter of the trestore or drestore utility to avoid writing "old" files over your new 7.4A files. NOTE: Restoring customer files on an update procedure should not be required. The procedure should leave all user files intact. 2.4 Product Installation/Upgrade 2.4.1 EOS - Operating System 1. The configuration files created by "vconf" have new fields and new functionality. Only config- uration files created with a 7.3 or 7.4A vconf command will work on 7.4A operating system. However, the 7.4A vconf command will convert 7.2 configuration files to the 7.4A format. 2.4.1 (Cont.) Steps 2 and 9 of the upgrade procedure will accomplish this. 2. The 7.4A user is responsible for configuring the type of the system console terminal after the install procedure is complete. This step cannot be done until the operating system and the utilities product, EUT, have been installed. Then the user should execute the Port Config- uration Utility "configure" and set the system console type. The system console type set by the boot PROM configurator is no longer supported by the operating system. Other system console parameters must still be set through the boot PROM configurator. 3. The format of the print control files has changed. On an osupdate, the existing files will auto- matically be converted to the new format. Backup versions of the old files should not be used or installed. The files are: /etc/forms /etc/ports /etc/printers /etc/defaults /etc/class 4. Automated backup procedures that use "/bin/mcssave", "/bin/mtssave", or related utilities must be changed to use the new tape utilities that are included in the EUT product. See section 3.1.3. 5. Partition files created with 7.1 or 7.2 "/bin/usb", which reside in the "/etc/diskdesc", cannot be used on 7.4A. These files can be recreated using the 7.4A "usb" command. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg017 6. On upgrades from 7.1 to 7.4A the user MUST boot off the customer tape and select the "A" option before doing an "osinstall" from the boot partition. 7. The /etc/error.log file format has changed. Prior to going into multi user mode, use the delete command to delete this file. It will be recreated at the default size of 100 records when the system goes into multi user mode. If you want more than 100 records, use the sys/errlog command specifying the number of records and the initial option to recreate this file. 2.4.2 ECC "C" Compiler Due to changes to the header files and the new shared libraries in 7.4A all "C" programs should be recompiled on 7.4A to avoid problems executing these programs. 2.4.3 MAGNET (ENT) and File Transfer Facility (FTF) 1. To install ENT, execute the command: admin> install xx ENT To install FTF, execute the command: admin> install xx FTF Where xx is the device of the ENT or FTF media. cs = 1/4" MCS ts = 1/2" MTS fd0 = floppy drive 2. The MAGNET/FTF configuration files have changed format between 7.2 and 7.4. Existing LEGAL network configurations will be converted to the new format by a program which is automatically executed at installation of the 7.4 ENT or FTF product. Configurations which do not conform to documented restrictions (e.g., two LAN boards) may not successfully convert. Though the installation procedure allows the installer to omit calling the configuration conversion program, it is safe to run the conversion program. 3. The old 7.2 configuration utility, "netutil", has been replaced entirely by the collection of programs known as Network Management Facilities (NMF). Because "netutil" is incompatible with the new configuration file format, it is deleted by the ENT and FTF installation procedures. This is required and automatic. 4. The new NMF event log is different from the old 7.2 network event log. Old network event logs will become unusable when 7.4 ENT or FTF is installed. If the content is of interest, the logs should be listed using the "netutil" BEFORE installing the new products. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg018 5. The user reference manuals for 7.4A MAGNET and FTF are not available. Refer to the MAGNET BOSS/VS User Reference Manual(M6363) for configuration instructions and to the File Transfer Facility User Reference Manual (M6352) for FTF operations. 2.4.3 (Cont.) 6. ENT and FTF uses CMB port 1 when X.25 is installed. This port must be strapped as "modem". The maximum baud rate supported by X.25 on 7.4A is 4800 baud. 2.4.4 27xx/37xx Batch Emulation 1. The 27xx/37xx Batch Emulation package is now written in BASIC and is called TBC (Transportable Batch Communications). The C version of 27xx/37xx Batch Emulation (EBC) is no longer available on the 2000/3000 systems. TBC on 7.4A is compatible to TBC on MPx and 13xx systems, as well as 2000/3000 systems running EBC, since the line protocol has not changed. 2. To install TBC, execute the command: admin> install xx TBC where xx is the device of the TBC media cs = 1/4" MCS ts = 1/2" MTS fd0 = floppy drive 3. Conversion of the transmit queue, receive queue, and autoprompt files is performed by running/util/ fconvert when installing TBC on a system previously using the EBC product. The public key for TBC is compatible with the EBC public key. 4. There are no operational changes between TBC and EBC when running BCOM from the Communications menu. However, since the 7.4A version of bcom is written in BASIC, there are changes in accessing BCOM from command mode: user prompt>basic s=128 pgm=/tbc/BCOM/BCOM 5. The utility, /util/BCOMPFX, allows users to specify which directories the BCOM program files and data files reside in. Previously, EBC required that bcom program files be in /util and data files were created in /etc/comm. With TBC on 7.4A users may copy the BCOM program files from /tbc/BCOM to another node and run BCOMPFX to specify the new node. Data files such as autoprompts, receive queues, transmit queues, will be created in the node specified as the data prefix in BCOMPFX. To access BCOMPFX from command SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg019 mode, type: user prompt>basic pgm=/util/BCOMPFX 2.4.4 (Cont.) 6. TBC on 7.4A supports autodial features which allow BCOM to interface to an automatic calling unit (ACU) to dial the number stored in the BCOM autoprompt file. Two utilities, ACUTD and ACS, have been added to TBC: ACUTD - utility to build scheduler lists of BCOM autoprompts which are designated to be activated at specified date and times. ACUTD can be accessed from the communications menu or alternately from command/console mode. user prompt>basic s=128 pgm=/tbc/BCOM/ACUTD ACS - program which activates the scheduler lists specified in ACUTD. ACS can be accessed from the communications menu or alternately from command/console mode. user prompt>basic s=128 pgm=/tbc/BCOM/ACS 7. The 7.4A automatic calling features of TBC have been certified with the following ACU's and modems: o Universal Data Systems 801C ACU with Universal Data Systems 201C synchronous modem - This combination requires a serial asynchronous port be configured as a terminal (EVDT with default parameters) for the 801C ACU and CMB port 1 configured for the synchronous communications port. The UDS 201C is compatible to other vendor's BELL 201C compatible units. o Paradyne FDX 2400 PLUS ACU/modem - This unit also requires a serial port be configured as a terminal (EVDT with default parameters) for the ACU interface and CMB port 1 configured for synchronous communications. This unit is compatible with another Paradyne FDX 2400 Plus, a Bell 212A synchronous modem, and a Universal Data Systems 224 synchronous modem. 8. TBC uses CMB port 1. This port must be strapped as "modem". The maximum baud rate for TBC is 4800 Baud. 9. Details on TBC and modem/ACU strappings are documented in the BOSS/IX Transportable Batch Communications (27xx/37xx) User Guide - M6353C. 2.4.5 Asynchronous Transport Package (ATP) 1. ATP 4.0 is included with the 7.4 EIT product. ATP 4.0 contains protocol changes for performance SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg020 enhancements which makes it incompatible with previous releases of ATP. All systems using ATP to communicate to a 7.4A system must also have ATP 4.0 on their systems. 2. In addition to performance enhancements, ATP 4.0 provides the following features: o Line Turnaround - allows transmit and receive functions in a single session o Autodial - supports automatic dialing of Hayes/compatible and UDS 224 A/D modems o Scheduler - provides unattended startup of ATP sessions 3. To install ATP 4.0, the EIT product must be installed: admin> install xx EIT where xx selects the device of the install media cs = 1/4" MCS ts = 1/2" MTS fd0 = floppy drive 4. To activate the features of Line Turnaround, Autodial, and the Scheduler, a public key must be installed: admin> install_key /etc/level/ATP 5. As with previous levels, BQR must be run to generate an ATP filelist. Note, however, that schema files are no longer supported by BQR for any transport media - transmitted files must either be in TEXT or BINARY format. After BQR filelists are created, RUN "ATP" to set the communications parameters for the session. The parameters may be saved in an autoprompt for future use or use with the Autodial and Scheduler features. RUN "ATPTIM" to set the Scheduler parameters. RUN "ATPSCH" to begin the ATP sessions according to the parameters set in the Scheduler. 2.4.5 (Cont.) 6. Automatic file conversion and translation occur during the file transfer. BQR will no longer be required to convert files received via ATP 4.0 from unlike systems. 7. Refer to the ATP 4.0 Software Announcement #150 and the Intersystem Transport Package User Guide (M6354D) for details. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg021 2.4.6 3270 Bisynchronous 1. To install the 3270 Bisynchronous product, execute the command: admin> install xx B32 where xx selects the device of the install media cs = 1/4" MCS ts = 1/2" MTS fd0 = floppy drive 2. B32 uses CMB port 1. This port must be strapped as "modem". The maximum baud rate supported by B32 is 4800 Baud. 3. The DT-4313 is now supported, in addition to the DT-4310 to emulate an IBM 3278 display terminal. 2.5 Security Configuration Record When installing 7.4A on your system or if you are upgrading/adding to the system's hardware, you must also install/upgrade to a 7.4A security configuration record. See step #4 of section 2.2 Installation of the Operating System for instruction. 2.5.1 7.4A Configuration Record Request Sheet On the following page you will find a copy of the 7.4A Configuration Record request sheet. 3.0 LEVEL 7.4 BOSS/IX ENHANCEMENTS/CORRECTIONS 3.1 Operating System (EOS) 3.1.1 Shared Libraries Instead of each program having a copy of the library, they are shared. This results in less disk space required for the program. 3.1.2 1/2 Inch Tape Boot and Install The 1/2 inch tape now supports system boot and software distribution, as well as backup and restore capabilities. 3.1.3 Merged Tape Commands and Utilities The tape commands and utilities have been merged. The tape commands/utilites are now 't' for tape, instead of 'mcs' or 'mts'. When you enter the command/utility name, the 'utility' will be run. To specify the 'command' instead of the utility, enter the device name when you enter the command/utility name, ie: tlabel will execute the tape label utility. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg022 tlabel dev=cs {options} will execute the tape label command on the 1/4" tape cartridge. 3.1.4 Console Configuration Setting of the system console type is no longer done by the boot PROM configurator. Other system console parameters must still be set through the boot PROM configurator. The console type will be read from the /etc/terminals file. The other console parameters (port number, baud rate, etc) will be read from the NVRAM. 3.1.5 vconf Configuration File The configuration files created by vconf have new fields and functionality. Only configuration files created with a 7.3 or 7.4 vconf command will work on a 7.4 operating system. Do not restore a 7.2 configuration file on a 7.4A operating system. New options: ghosts=# Maximum number of Ghost tasks. dirc=# Number of directory cache entries. fds=# Maximum number of open files on the system. NOTE: opens=# is an obsolete option, it has been replaced by the fds=# option. Also the recommended vconf parameters have changed. See section 6. 3.1.6 System Security Configuration Record format change The System Security Configuration Record format has changed. You must install a 7.4A configuration record on a 7.4A Operating system. Do not attempt to use a 7.2 or 7.3 configuration record on a 7.4A Operating System. 3.1.7 System Dump Changes System dumps now go directly to tape or floppy. Dumps must be written to media before the system is reloaded or the information will be lost. Also, a new command 'dmplog' has been added. This command displays the last 8 entries in the in-memory error log table from a dump. Often times, the cause of the dump can be determined by the information in these entries. This will allow you to evaluate the problem, and often times resolve it, on site at the time it SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg023 occurred. If necessary, a dump can then be submitted to Product Support for further analysis. Example: dmplog --> /dev/cs, dev/ts, or /dev/fd0 3.1.8 Reduced Disk Requirements The disk space required for the base product Operating. System (ie: EOS, EBS, and EUT) have been reduced accordingly: 7.1B 7448KB (7.27MB) 7.2B 9283.5KB (9.07MB) 7.2D1 8650KB (8.45MB) 7.3A (2000) 4048KB (3.95MB) (3000) 3979KB (3.89MB) 7.4A (2000) 4621.5KB (4.51MB) (3000) 4688 (4.58MB) (4000) 4688 (4.58MB) NOTE: These values were calculated using a base configuration on a newly installed Operating System and its commands, BASIC and its utilities, and the system utilities. 3.1.9 New System Error Logger The new system error logger file has a limited number of terminal error entries. This will keep the file from getting filled up with terminal entries which causes other errors to be lost. It is now eaiser to read. The new format allows disk error entires to be interpreted without an Error Logger Specification. 3.1.9 (Cont.) The new command options are: -mem display only the errors associated with memory. -tape display only tape errors. -term display only terminal errors. -printer display only printer errors. -comm display only communication errors. -disk display only disk errors. -text used in conjunction with the '-disk' option, means display a description of the disk errors. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg024 Example: /sys/errlog Displays the last 8 entries in the error log only. (These are still in memory) /sys/errlog /etc/error.log Displays the error log stored on disk. /sys/errlog /etc/error.log -disk -text Displays the text description of the disk errors. 3.1.10 File Integrity Checking A flag for each file is set when the file is opened, then reset when the file is closed. The command fichk will check a filesystem or directory for files which lack integrity (open when a system crash occurred). This command should be run after a pre-mature shutdown. After the automatic file system check is complete and the system is rebooted normally, use the fichk command with the filelist option to generate a list of corrupt files. Then, run the frepair utility using the file list generated by fichk to repair the files and clear the integrity flag in the files. Format: fichk 3.1.10 (Cont.) Options: -clear clears the flag which marks the file as lacking integrity. -filelist generates a filelist file which contains the names of the files found to lack integrity (named "/util/fl/fichk.f"). Example: fichk /dev/root Displays the filenames of files on the /dev/root filesystem which lack integrity. fichk / -filelist -clear Displays filenames of files in the / directory and subdirectories which lack integrity; generates a a filelist named "/util/fl/fichk.f" of the files found; also, clears the integrity flag in the files found. NOTE: The fichk command reports the full path name SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg025 of the files which lack integrity. It does not repair the file. The frepair utility must be run on the files found. 3.1.11 Configurable Number of Ghost Tasks The maximum number of Ghost Tasks on a system is now a user configurable parameter in vconf. 3.1.12 Improved BOSS/IX Swapping Performance Swapping is now determined by the priority status of the WAIT state. The system now takes less time to determine which process to swap and it makes a better choice. This lessens the system performance degradation due to excessive swapping. 3.2 SYSTEM UTILITIES (EUT) 3.2.1 frepair Utility The frepair utility now has the capibility to retire a a bad block, report which file (if any) the bad block resides in, and gives you the option of repairing the file. You no longer have to re-format the disk each time a bad block is reported in the hardware error logger. NOTE: This will reduce the file system space. 3.2.2 Configure Utility 3.2.2.1 Configure the system console The configure utility has been change to allow the user to set the terminal type for the system console. It now automatically adjusts the /etc/terminals and /etc/ports entries if the console has been moved since the last time the utility was executed. The system software will ignore the console terminal type in the NVRAM. The console type will be read from the /etc/terminals file. The other console parameters (port number, baud rate, etc.) will be read from the NVRAM. The configure utility and the sysinfo command which reads the /etc/terminals file can report a different console type than the "config" which reads the NVRAM. However, only the values in the /etc/terminals file have any effect on the functionality of the console terminal. 3.2.2.2 New Terminal Types Two new terminal types have been added to the configure utility. The 4313 and 4314 are now available terminal types. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg026 3.2.2.3 Configuring Printers The configure utility has been changed to use. marketing numbers instead of names, except for hpplot, isp and spe. 3.2.2.3 (Cont.) The following table shows the relationship between the printer market codes and the actual PDF's used to support them: Market Code Actual PDF 4201 dmp 4203 b4whis 4208 isp 4210 oki 4211 diablo 4212 isp 4212B4 oki 4213 whispr 4213B4 b4whis 4214 dmp 4215 fuji 4216 daisy 4217 4218 4218 4218 4220 4220 4222 4222 4223 4223 NOTE: When upgrading from a previous level, printer must be reconfigured using the new market codes. 3.2.2.4 Parallel Ports The MAI 4000 allows for two additional parallel ports, making a total of three available. These will appear as the last two ports on the system, no matter how many serial ports are there. 3.2.3 pparams Utility A field has been added to the /etc/forms file for the number of form feeds to print before each spooled print job. The default value is 1. To change this, use the 'modify' option in the 'maintain form definitions' options. NOTE: A value of 0 (zero) will cause no form feed to be sent from the spooler. 3.3 BASIC (EBS) 3.3.1 Business BASIC 86 Business BASIC 86 or BB86 (TM) is an evolving standard language supported on both BOSS/IX and BOSS/VS. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg027 It includes: o Compatibility features o Program generation tools o More system independent features o Multi-key file support For a detailed explanation of BB86 refer to the BUSINESS BASIC 86 REFERENCE MANUAL, M 6262. 3.3.2 BASIC on 7.4 is not backward compatible with 7.2 Some BASIC directives on 7.4 generate a different code when compiled than is generated when compiled on prior BASIC levels, therefore, 7.4 BASIC is not backward compatible. The following directives and functions are not backward compatible from 7.4A to 7.2 or prior releases: FID, IND, ENCRYPT, RENAME, RELEASE and QUIT. NOTE: This effects only BASIC program files, NO other file type is effected by this. 3.3.3 Changed Functionality 1. The RELEASE directive will now log the user off the system. The QUIT directive should be used in place of RELEASE to exit Basic and return to the command interpreter level. 2. The PNM system variable in a CALLed program will return the name of the CALLed program. In 7.2 Basic, PNM in a. CALLed program would return the name of the CALLing program. 3. The PNM function returns a fully qualified program name (e.g., "/usr/joe/myprogram" rather than simply "myprogram"). 3.3.3 (Cont.) 4. Since 7.4A supports longer device names (e.g., "TA" has become "T10"), names which were valid file names in 7.2 and prior releases might be interpreted as device names under 7.4A. For example, suppose that a 7.2 program was using a file named "T10", under 7.4, if the system had configured that 11th terminal then "T10" would be treated as a device name. This problem may occur with any directive that uses file names (e.g., RUN, OPEN, DIRECT, and INITFILE). 5. The FID directive returns the device value that was opened. Example: OPEN(1) "T10" PRINT FID(1) returns T10 OPEN(1) "TA" PRINT FID(1) returns TA SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg028 6. FID (0) returns the 4 character device name. Example: If the terminal ID is T10, the FID (0) will return T10 not TA. 7. The SYS Function returns information formatted in a slightly different way then 7.2 and prior versions. of BASIC. It used to return a string such as "EBS7226" and will now return something like "BB86 07.04A*23.00". 8. 7.2 -trans= file's required that the first line in this file begin with "EBS". 7.4A will NOT allow this EBS line and it must be removed. 9. 7.2 and prior versions of the O/S would intercept ctrl-R's. Ctrl R's may now be read by BASIC programs using INPUT RECORD (0,SIZ=1)A$ commands. 10. The echoing of the tab key has changed going from 7.2 to 7.4A. Prior to 7.4A, the tab key would position the cursor to the next tab position on the same line. Beginning with 7.4A, the tab key will now reposition the cursor to the @(0,0) home position. 3.3.3 (Cont.) 12. There are quite a few new reserved words that have been introduced in the 7.4A BB86 release of BASIC. These may no longer be used as variables in user programs. The following table lists new reserved words and gives a thumbnail sketch of each ones use: ___________________________________________________________________________ | |. | ALIAS Part of FIELD ALIAS | | ASCII Compatible ASC function. For example ASCII (" ") returns | | 32 on either a BOSS/IX or BOSS/VS system. | | ATTR Used within OPEN, CREATE and as a funciton for file | | attributes | | CHAR Compatible CHR function. CHAR(65) returns "A" | | CONSOLE Part of CONSOLE LOCK | | CONSOLELOCK Causes prompt for password whenever about to enter |. | console-mode | | CREATE Like FILE but has more options and uses a readable string | | CSW Function returning 0 if current program in RUNning, 1 if | | CALLed | | DEVINFO Return information on all devices on system | | ENDFORM Reserved for future use | | ENDIF Terminates a compound IF statment (like FI) |. | ENDTRANS Turns off automatic file name translation | | FIELD Part of FIELD ALIAS and SET FIELD | | FIELDALIAS Associates field-variables with different multi-key | | fields | | FMT Used to specify mutli-key format strings | | FMTINFO Returns a multi-key format string | | FORM Reserved for future use | | FORMFILE Reserved for future use | | INIT Part of INIT FILE |. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg029 | INITFILE Clears out an already existing file | | LISTPROGRAM Converts a program into a ASCII serial file | | MAKE Part of MAKE PROGRAM | | MAKEPROGRAM Converts an ASCII serial file into a program | | MSG Used within CONSOLE LOCK and SET FIELD for messages | | MULTI Creates a multi-key file | | OPENFORM Reserved for future use | | PACK "Writes" to an internal logical unit buffer | | PNM Returns the fully qualified name of the current program | | PSAVE "Protected" program save (like ENCRYPT) | | QUIT Drops from BASIC back to 'shell' (same as 7.2's RELEASE) | | RETAIN Used on I/O to manage an internal logical unit buffer | | SETFIELD Adds or deletes keys in a multi-key file | | SETFORM Reserved for future use | | SETTRANS Specifies how automatic file name translation is to occur | | SYNTAX Checks syntax of a string | | TRANS Used with SETTRANS to return translated strings | | TRX Returns the name of the SETTRANS file | | UNPACK "Reads" from an internal logical unit buffer |. | WHO Returns the name of the current user account | | |. |___________________________________________________________________________| 3.3.3 (Cont.) Note that 7.2 and earlier programs that use these reserved words will still run as long as lines containing these words are not edited or MERGEd. Once the syntax error is in the program, however, it will probably not run correctly and such variable names must be changed. This situation is normal for any new release of BASIC that supports new features. There is, however, a much longer than normal list of new reserved words for 7.4A and hence a much greater chance of a word being used as a variable. 13. Programs or files can now be created using unreserved terminal, printer and ghost names, such as 'TA', 'PF', and 'G9'. These names could be used as long as 'tty10' and 'p15' are not configured, and less than eight ghosts are configured in the 'vconf'. However, it is not recommended should the terminals, printers, or ghosts become available, which would cause errors. 14. DEVINFO system variable will now return a device status code in byte 8 of each 10-byte device substring. This code shows the following: BIT Meaning if Bit is set true 0 Escape entered on terminal device 1 Device is open or in use 2-7 undefined (these bits are always zero) 3.3.4 BOSS/VS & BOSS/IX Compatibility Notes 1. The FID(0) in batch mode returns different results SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg030 based on the system. In BOSS/VS, FID(0) in batch mode returns the full 80 byte string. In BOSS/IX, FID(0) in batch mode returns Tx. 2. In BOSS/VS, the following statement is accepted: IF A=1 THEN PRINT OK ELSE PRINT NO; ENDIF In BOSS/IX, the semicolon before the ENDIF will generate an error. 3.3.4 (Cont.) 3. String functions and string system variables may use an optional '$' in their name on BOSS/VS. For example, the CHR function can be used as C$ = CHR(n) or C$ = CHR$(n). The optional '$' will cause an error on the BOSS/IX system. 4. The keysets are handled differently when two fields occupy the same position in a record of a Multi Key file. BOSS/VS Two fields defined with the same physical start position and length can NOT both be keysets. Example: F1# = S10 Primary Key F2# = S10 ALT Key F3# = F2# Can NOT have keyset BOSS/IX Two fields defined with the same physical start position and length MAY both have keysets defined provided the keysets are of different types. Example: F1# = S10 Primary Key F2# = S10 F3# = F2# Then, fields F2# and F3# may have keys defined F2# F3# Error Code (if any) DUP Key ALT Key No Key ALT Key ALT Key ALT Key err 12, -37 NO Key DUP Key NO Key ALT Key NO Key NO Key DUP Key DUP Key err 12, -37 SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg031 Primary DUP Key Primary NO Key Primary ALT Key err 12, -37 3.3.4 (Cont.) 5. BOSS/VS and BOSS/IX will return a different error . code when a WRITERECORD with IND= or KEY= option is. used on a Multi Key file. BOSS/VS error 13 BOSS/IX error 17 3.4.5 Unsupported Mnemonic on PT4220 On a PT-4220 only, output transparency does not work and is not supported. 3.4 3270 Bisynchronous (B32) The DT-4313 terminal is now supported to emulate an IBM 3278 display. terminal. Previous to 7.4A, the DT-4310 was the only terminal supported by B32. 4.0 NEW PRODUCTS IN LEVEL 7.4A 4.1 Universal Printer Driver (UPD) The UPD is a collection of tools which allow the user to define control and mnemonic support for any printer connected to the MAI system. Although the UPD was conceived with the maximum flexibility in mind, there may be printers which cannot be fully supported through UPD. System Independent Multi Purpose Language (SIMPLE) is one of the UPD tools. It is a "language" used to create a printer definition file (PDF) in which a user defines printer attributes and mnemonic support. The program that the user creates using SIMPLE is compiled and this compiled output is used by a module known as the SIMPLE Executor to drive the printer in question. The UPD product will not reside on the customers system. It is a development tool for creating a PDF. For more information, refer to the Universal Printer Driver Reference Manual, #M0053A. 4.2 PDF (Printer Definition File) The PDF product is required on the customer system to use the driver created with the UPD product. It is a security feature. PDF requires a key from Software Distribution. Once the key is entered the driver created with UPD can be used on the customers system. 5.0 FOR YOUR INFORMATION This section gives the warnings and cautions for the 7.4A Operating System and a workaround if one is available. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg032 5.1 Operating System (EOS) 5.2 BASIC (EBS) 1. Composite fields whose starting position is not specified and whose length is specified thru ":" are not interpreted correctly, for example "F2#=F1#:8". The work -around is to specify the starting position, for example "F2#=F1#(1):8" or "F2#=F1#(1,8)". 2. If a composite field is defined thru "(s):1" before its component field is defined in the format string, for example "F1#=N10 PRIMARY F2#=F1#(1):12 F3#=N5", then the record size is not computed correctly. The work-around is to use "(s,1)" format instead, for example "F1#=N10 PRIMARY F2#=F1#(1,12) F3#=NS". 3. If a composite field is defined beyond the end of fixed fields, for example "F1#=N10 PRIMARY F2#=N5 F3#=F1*(1,18)", then the size of the record is not extended. This problem might be too unrealistic. But one suggested work-around is to define an additional fixed field, for example: "F1#=N10 PRIMARY F2#=N5 F3#=F1*(1,18) F4#=lN3". 4. Variable-length fields within multi-keyed files will sometimes be read as empty or zero when they have been written with some other value. There is no work-around. It is recommended to avoid using variable length fields. Here are some examples and workarounds. 1. "F1#=N10 PRIMARY F2#=F1#:8" is interpreted as "F1#=N10 PRIMARY F2#=N10", but "F1#=N10 PRIMARY F2#=F1#(1):8" works. 2. "F1#=N10 PRIMARY F2#=F1#:12" is interpreted as "F1#=N10 PRIMARY F2#=N10", but "F1#N10 PRIMARY F2#=F1#(1):12" works. 3. "F1#N10 PRIMARY F2#=F1#(1):12 F3#=N5" is interpreted to. define a record whose size is 10 instead of l15. But "F1#=N10 PRIMARY F2#=F1#(1,12) F3#=N5" works. 4. "F1#=N10 PRIMARY F2#=F1#(1,18)" is interpreted to define a record whose size is 15 instead of 18. 5.3 FTF via LAN and X.25 o Constant full duplex file transfers (simulataneous transfers in both directions) can cause the X.25 link to fail after approximately 30 hours. Workaround: If link failures occur, decrease the amount of full duplex file transfers. o When there is heavy activity on the system, enough to cause swapping of processes, abort 79's can occur. Workaround: Use the rescheduling option of FTF or schedule files during non-peak hours. o File transfers of a file on a remote system (i.e. a system connected via LAN) is not supported and will cause the SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg033 session to be "In Progress" forever. Workaround: This feature is currently not supported and should not be used. 5.4 MAGNET via LAN and X.25 o When rcopy is used to update a remote file (replace existing files) and the destination file is currently locked by another process, the copy will still occur and the data is 'temporarily stored' in the remote system until the file is unlocked. There is no message on the source systems stating this is so. Workaround: None. This is the same implementation of a local copy command. o When performing an 'EXTRACT' and 'REMOVE' of a keyed record on a remote file, the process will suspend, if the 'KEY=' option is not used. Workaround: Save the 'KEY' from the 'EXTRACT', and use it with the 'REMOVE' directive. o LAN timeout errors -554 or -527 occur with moderate to heavy full duplex remote file activity. These errors are caused by the remote file access processes being swapped out. Workaround: Retry operation. Reduce heavy full duplex activity or reduce processing on the remote system. 5.5 Intersystem Transport Package (EIT) o EIT will no longer support mixed format schema files. Only TEXT (convert all data) and BINARY (don't convert all data) are supported. o ATP 4.0 is released with the EIT product. ATP 4.0 is NOT compatible with previous releases of ATP. o Only files which are compatible between unlike systems can be transferred - i.e. string file transmissions can only occur between Boss/IX systems. o ATP 4.0 supports direct connections between 1200 - 9600 Baud. ATP 4.0 supports modem connections of 1200 and 2400 Baud using the following modems: UDS 212A UDS 212 A/D UDS 224 A/D UDS FASTTALK "Hayes compatible" HAYES Smartmodems 5.6 3270 Bisync o The DT-4310 and the DT-4313 are the only terminals supported as a 3278 display terminal. 6.0 Memory Requirements and Operating Parameters SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg034 6.1 Approximating A System's Memory Requirement This section describes how to approximate the amount of memory a system needs. Tables 6A and 6B show some standard system configurations which can be used to approximate the amount of memory a system needs. The number of users (terminals), ghost tasks, and printers differ for each of these standard configurations. First, find the standard configuration that most closely matches the system in question, by scanning down the user/terminals, ghost-task, and printers columns. Second, scan across the table to the memory-needed column -- this is the system's memory requirements. NOTE: These tables (6A and 6B) assume that the system in question will be executing 60% BASIC and BASIC application programs, and 40% non-BASIC applications. If the system will be executing a higher percentage of non-BASIC programs, it will need more memory. Tables 6C and 6D show how to set up the BOSS/IX configuration ("vconf") parameters for each of the standard system configurations in tables 6A/B. In other words, if one uses the approximation method to determine a system's memory requirements, tables 6C/D can be used to set up the BOSS/IX configuration parameters. The approximation method is an easy and accurate way to determine a system's memory needs, if its configuration is close to one of the standard configurations. However, if it does not closely fit one of the configurations shown, the calculation method should be used (see section 7.1). ___________________________________________________________________ | | | | | | | Standard | Users/ | Ghost | Printers | Memory | | Configuration | Terminals | Tasks | | Needed | | | | | | | | | | | | | | number 1 | 2 | 0 | 1 | .75 MB | | | | | | | | | | | | | | number 2 | 5 | 1 | 2 | 1.00 MB | | | | | | | | | | | | | | number 3 | 9 | 2 | 2 | 1.25 MB | | | | | | | | | | | | | | number 4 | 12 | 3 | 3 | 1.50 MB | | | | | | | NOTE: 1 MB (Megabyte) = 1024 KB (Kilobyte) = 1024 * 1024 bytes TABLE 6A Approximating the Memory Requirements for an MAI 2000 System _____________________________________________________________________ | | | | | | | Standard | Users/ | Ghost | Printers | Memory | SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg035 | Configuration | Terminals | Tasks | | Needed (MB) | | | | | | | | | | | | | | number 1 | 2 | 0 | 1 | 1 | | | | | | | | | | | | | | number 2 | 9 | 2 | 2 | 2 | | | | | | | | | | | | | | number 3 | 16 | 4 | 4 | 3 | | | | | | | | | | | | | | number 4 | 22 | 6 | 6 | 4 | | | | | | | | | | | | | | number 5 | 28 | 8 | 9 | 5 | | | | | | | | | | | | | | number 6 | 34 | 10 | 10 | 6 | | | | | | | TABLE 6B Approximating the Memory Requirements for an MAI 3000 System NOTE: The number of users/terminals shown is approximately the highest number which can be supported in the memory shown. _____________________________________________________________________ | | | | | | | Standard | Users/ | Ghost | Printers | Memory | | Configuration | Terminals | Tasks | | Needed (MB) | | | | | | | | | | | | | | number 1 | 2 | 0 | 1 | 1 | | | | | | | | | | | | | | number 2 | 12 | 4 | 2 | 3 | | | | | | | | | | | | | | number 3 | 27 | 6 | 4 | 6 | | | | | | | | | | | | | | number 4 | 42 | 8 | 6 | 9 | | | | | | | | | | | | | | number 5 | 57 | 10 | 9 | 12 | | | | | | | | | | | | | | number 6 | 74 | 12 | 10 | 16 | | | | | | | TABLE 6C Approximating the Memory Requirements for an MAI 4000 System NOTE: The number of users/terminals shown is approximately the highest number which can be supported in the memory shown. _____________________________________________________________ | | | | "vconf" BOSS/IX | Standard Configuration (see Table 6A): | SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg036 | Parameter | | | | | | | | | | number 1 | number 2 | number 3 | number 4 | | | | | | | |buffers= | 20 | 32*| 48*| 60*| |printers= | 1 | 2 | 2 | 3 | |procs= | 16*| 27*| 40*| 51*| |tsegs= | 16*| 22*| 30*| 36*| |locks= | 74 | 94*| 119*| 139*| |ibsize= | 128 | 128 | 128 | 128 | |tbsize= | 64 | 64 | 64 | 64 | |mfsys= | 3 | 3 | 3 | 3 | |lus= | 136*| 222*| 322*| 408*| |fds= | 60 | 96*| 138*| 174*| |eventcalls= | 16*| 22*| 30*| 36*| |sockets= | 6 | 6 | 6 | 6 | |dsockets= | 8 | 14 | 20 | 26 | |lanbuffers= | | 12 | 16 | 16 | |dirc= | 64 | 102 | 144 | 170 | TABLE 6D "vconf" BOSS/IX Parameters for Standard MAI 2000 NOTE: The "standard" configurations are described in Table 6A. "*" means that this number has changed from 7.2 to 7.4A. "opens" on 7.2 are now called "fds" on 7.4A. "dirc" is a new parameter for the MAI 2000 vconf file. _______________________________________________________________________________ ___ |. | | |. | | | "vconf" BOSS/IX | Standard Configuration (see Table 6B): | | Parameter | | | | | | | | | | | | number 1 | number 2 | number 3 | number 4 | number 5 | numbe r 6 | | | | | | | | | |buffers= | 128 | 704 | 1280 | 1792 | 2304 | 2 816 | |printers= | 1 | 2 | 4 | 6 | 8 | 10 | |procs= | 16 | 40 | 65 | 87 | 110 | 131 | |tsegs= | 16 | 30 | 44 | 56 | 68 | 80 | |locks= | 74 | 119 | 164 | 204 | 244 | 284 | |ibsize= | 128 | 128 | 128 | 128 | 128 | 128 | |tbsize= | 64 | 64 | 64 | 64 | 64 | SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg037 64 | |mfsys= | 3 | 3 | 4 | 4 | 5 | 5 | |lus= | 136 | 322 | 556 | 656 | 864 | 1 030 | |fds=. | 60 | 138 | 218 | 290 | 364 | 434 | |eventcalls= | 16 | 30 | 44 | 56 | 68 | 80 | |dirc= | 64 | 142 | 222 | 294 | 368 | 438 | TABLE 6E "vconf" BOSS/IX Parameters for Standard MAI 3000 Configurations NOTE: The "standard" configurations are described in Table 6B. "opens" on 7.2 are now called "fds" on 7.4A. _______________________________________________________________________________ |. | | | "vconf" BOSS/IX | Standard Configuration (see Table 6C): | | Parameter | | | | | | | | | | | | number 1 | number 2 | number 3 | number 4 | number 5 | numbe r | | | | | | | | | |buffers= | 128 | 768 | 1728 | 3328 | 5248 | 7 936 | |printers= | 1 | 2 | 4 | 6 | 9 | 10 | |procs= | 16 | 47 | 94 | 172 | 265 | 358 | |tsegs=. | 16 | 36 | 96 | 146 | 206 | 290 | |locks= | 74 | 124 | 199 | 324 | 474 | 684 | |ibsize= | 128 | 128 | 128 | 128 | 128 | 128 | |tbsize= | 64 | 64 | 64 | 64 | 64 | 64 | |mfsys=. | 3 | 4 | 5 | 6 | 7 | 8 | |lus= | 136 | 342 | 654 | 1166 | 1784 | 2 630 | |fds= | 60 | 142 | 266 | 470 | 716 | 1 054 | |eventcalls= | 16 | 36 | 96 | 146 | 206 | 290 | |dirc= | 64 | 146 | 270 | 474 | 720 | 1 058 | TABLE 6F "vconf" BOSS/IX Parameters for Standard MAI 4000 Configurations SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg038 NOTE: The "standard" configurations are described in Table 6C. "opens" on 7.2 are now called "fds" on 7.4A. 6.2 Recommended Values for "vconf" The following tables (Table 6G, 6H and 6I) show the recommended values for the BOSS/IX "vconf" parameters. 6.2.1 Recommended Values for "vconf" BOSS/IX Model 2000 Parameters __________________________________________________________________________. | | | | | | | | SYSTEM | base | add | add | add | maximum | | DESCRIPTION | system: | for | for | for | recom- | | -----> | | each | each | each | mended | | | 2 user | extra | ghost | extra | system | | | 1 printer | user | task | printer | config- | | "vconf" | | no ghosts | (above 2) | | (above 1) | uration | | BOXX/IX | | | | | | (See | | PARAMETERS V | | | | | Note 2) | | | | | | | | |buffers= | 20 | 4 | | | 64 | |printers= | 1 | | | 1 | 14 | |procs= | 16 | 3 | 1 | 1 | 80 |. |tsegs= | 16 | 2 | | | 64 |. |locks= | 74 | 5 | 5 | | 160 | |ibsize= | 128 | 1 | | | 2048 | |tbsize= | 64 | 1 | | | 512 | |mfsys= | 3 | | | | * | |lus= | 136 | 20 | 20 | 6 | 254 |. |fds= | 60 | 8 | 10 | 2 | 206 | |eventcalls= | 16 | 2 | 5 | | 152 | |dirc= | 64 | 8 | 10 | 2 | 206 | |ghost= | 0 | as needed | | | 99 | | |. | * Allow one mountable filesystem slot ("mfsys") for each | | mountable disk partition. The default of three allows | | for a boot partition, a root filesystem partition, and | | a diskette filesystem or 2nd drive. | | |. NOTE 1: The BOSS/IX configuration parameters required for other products are described in their documentation. Specifically, the LAN and 27xx/37xx communications products will require changes to the system parameters. For example, Magnet operating systems require 5 eventcalls per user. NOTE 2: These recommended values are not system limits but provide a guideline to tailoring the system. TABLE 6G Recommended Values for Model 2000 Operating Parameters 6.2.2 Recommended Values for "vconf" BOSS/IX Model 3000 Parameters _________________________________________________________________________ | | | | | | | SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg039 | SYSTEM | base | add | add | add for | maximum | | DESCRIPTION | system: | for | for | each | recom- | | -----> | | each | each | extra | mended | | | 2 user | user | ghost | printer | system | | | 1 printer | (above 2) | | | values | | "vconf" | | | | | | (Note 1) | | BOXX/IX | | | | | | | | PARAMETERS V | | | | | | | | | | | | | |buffers= | 128 | 64 | 64 | | (Note 2) | |printers= | 1 | | | 1 | 34 | |procs= | 16 | 3 | 1 | 1 | 223 | |tsegs= | 16 | 2 | | | 148 | |locks= | 74 | 5 | 5 | | 234 | |ibsize= | 128 | 1 | | | | |tbsize= | 64 | 1 | | | | |mfsys= | 3 | | | | (Note 3) | |lus= | 136 | 20 | 20 | 6 | 776 | |fds= | 60 | 8 | 10 | 2 | 316 | |eventcalls= | 16 | 2 | 5 | | 234 | |dirc= | 64 | 8 | 10 | 2 | 512 | |ghost= | 0 | as needed | | | 99 | NOTE 1: Values in this column reflect 34 user totals calculated from recommended increments, except for buffers. NOTE 2: Only memory availability limits buffers. NOTE 3: Allow one mountable file system for each mountable disk partition. A default of 3 allows for a root, boot and 1 other partition. TABLE 6H Recommended Values for Model 3000 Operating Parameters 6.2.3 Recommended Values for "vconf" BOSS/IX Model 4000 Parameters _________________________________________________________________________ | | | | | | | | SYSTEM | base | add | add | add for | maximum | | DESCRIPTION | system: | for | for | each | recom- | | -----> | | each | each | extra | mended | | | 2 user | user | ghost | printer | system | | | 1 printer | (above 2) | | | values | | "vconf" | | | | | | (Note 1) | | BOXX/IX | | | | | | | | PARAMETERS V | | | | | | | | | | | | | |buffers= | 128 | 64 | 64 | | (Note 2) | |printers= | 1 | | | 1 | 76 | |procs= | 16 | 3 | 1 | 1 | 343 | |tsegs= | 16 | 2 | | | 228 |. |locks= | 74 | 5 | 5 | | 434 | |ibsize= | 128 | 1 | | | | |tbsize= | 64 | 1 | | | | |mfsys= | 3 | | | | (Note 3) | |lus= | 136 | 20 | 20 | 6 | 1576 | |fds= | 60 | 8 | 10 | 2 | 636 | |eventcalls= | 16 | 2 | 5 | | 314 | |dirc= | 64 | 8 | 10 | 2 | 1024 | SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg040 |ghost= | 0 | as needed | | | 99 | NOTE 1: Values in this column reflect 74 user totals calculated from recommended increments, except for buffers. NOTE 2: Only memory availability limits buffers. NOTE 3: Allow one mountable file system for each mountable disk partition. A default of 3 allows for a root, boot and 1 other partition. TABLE 6I Recommended Values for Model 4000 Operating Parameters 7.0 Memory Usage This section describes how to determine the memory requirements for any MAI 2000, MAI 3000, or MAI 4000 system. All BOSS/IX systems have different memory requirements. A system's memory requirement is based on its hardware configuration and software load. Specifically, the number of peripheral devices (i.e. terminals and printers) and software packages (such as BASIC, BASIC applications, utilities, etc.) determine a system's memory needs. This section explains two methods used to determine the amount of memory needed for a system. The first method approximates a systems memory requirements -- and can be used if the system closely fits one of the standard system configurations. The second method calculates the memory requirements for best system performance -- and is used for non-standard system configurations. 7.1 Calculating A System's Memory Requirements This section describes how to calculate the number of memory boards a system requires for adequate performance. The calculations are based on the system's hardware configuration and software load. Software load is defined to be the number and types of processes running on the system. 7.1.1 Model 2000 This section steps through an example based on system configuration number 2 in Table 6A, a 5 user system. (See section 7.1.1.1). STEP 1 First, add the space required for the operating system, table space and dynamic space required for the base configuration. NOTE: 1 KB = 1024 bytes 220 KB This is the memory requirement for the base BOSS/IX operating system program. This includes space for the system's interrupt vectors, and operating systems text (code) and data segments. 34 KB** This is the memory requirement for BOSS/IX SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg041 table space for the base configuation: two users (terminals), one printer, and no ghost task. 7.1.1 (Cont.) NOTE: additional table space must be added for each additional resource above that in the base configuration (see step 2). 37 KB** This is the memory requirement for the operating system's dynamic work space (or unswappable memory). STEP 2 Next, add in table space needed for resources beyond the ones described in the base configuration. (If the system will be configured like the base configuration skip this step). NOTE: the MAI 2000 is a table driven system, and for maximum performance extra memory must be allocated for resources beyond the ones described in the base configuration. 5 KB** This is the memory needed as table space for. each additional user above the two that are allocated in the base system. (Refer to Table 7A) 2 KB** This is the memory needed as table space for each ghost task in the system. (Refer to Table 7A) 1.5 KB** This is the memory needed as table space for each additional printer above the one that is included in the base system. (Refer to Table 7A) 1.6 KB** This is the memory needed for dynamic work space for each additional process (i.e. "proc") above the 31 that are included in the. base system. (Refer to Section 7.2.1) ** Memory required for BOSS/IX table space and dynamic work space. These values are the memory allowance assuming that the configuration parameters are set according to Table 6A. If the system parameters are set differently, use section 7.2 and Table 7A to calculate the memory required for OS table and OS dynamic work space. 7.1.1 (Cont.) STEP 3 Add the space needed for system processes for the base system configuation. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg042 100 KB This is the memory allowance for system tasks. System tasks for the base system include: a printer despooler process, a system update process, a system error log process, and two command intrepreters. The total memory required to have all system processesin memory at the same time is approximately 200 KB. However, 100 KB should be used in this calculation because system processes wait on system events and it is not likely that all system processes will want to execute at the same time. Furthermore, these processes, when waiting for events, can be swapped to secondary storage, which will have little effect on system performance. STEP 4 Add the space needed for any additional system processes beyond the ones specified in the base configuration. (If the system will be configured like the base condiguration skip this step). 30 KB This is the memory needed for each additional printer despooler, above the one that is allocated in the base configuration. This is a memory allowance for the data and stack segments for an additional despooler task. An allowance for text (code) space is not necessary, beacuse two despooler tasks will share the same code segments. 15 KB This is the memory required for each user (terminal) that will be executing tasks concurrently. This is the memory allowance for each additional command interpreter. It is space needed for the interpeters data and stack segments. NOTE: memory allowance for text (code) space is not necessary, because multiple command interpreters share the same code segments. 7.1.1 (Cont.) NOTE: If the system is configured for ten operators, but the system only has five terminals -- i.e. a maximum of five users logged in at any instant -- then only 75 (5x15KB) need to be allocated. Furthermore, if one of the system terminals is seldom used, then space for that terminal does not have to be allocated. STEP 5 Next, add the space needed for applications processes. 160 KB This is space needed for each unique, non-BASIC SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg043 task that will be executed concurrently on your system. Such tasks include the BASIC interpreter, utility programs, LAN, Informix, communications, BOSS/IX command interpreter, etc. NOTE: only one BASIC interpreter is needed to support any number of BASIC programs. This value is a rough estimate, for all processes require different amounts of memory, some more some less. When computing the memory required for application tasks, consider how often each application is used. For example, if the system seldom executes BOXX/IX commands or the utilities, only a percentage of the total space needed to execute these processes will be required. However, when the system is loaded, and these are executed, system response time may increase due to excessive amounts of swapping. 60 KB This is the memory required for each BASIC program. This space is the allowance for the data and stack segments oreach BASIC program. NOTE: all BASIC programs share the same text (code) segment. Furthermore, this value is not exact, for some applications may require more memory and some may require less memory. 7.1.1 (Cont.) 64 KB This is the memory required for each ghost task that will be executed concurently. This is the space needed for each ghost tasks' stack and data segments. Text space is not. allocated because all ghost share the basic process text segment. STEP 6 Determine the memory/performance trade-offs. The value calculated in steps 1 thru 5 is the "memory required" for good system performance. However, this value is not exact and may be raised or lowered wich will increase or decrease performance respectively. By lowering the memory required value one can save the costs of an extra memory board, but at the expense of peformance. In other words, systems will run with less memory than required, however, the system overhead for swapping will increase. Process swapping is the action which extends user space to a temporary storage region on disk (i.e. the swap partition) so that, during periods of heavy main memory utilization, processes may be stored on disk to make room in memory for processes waiting to be executed. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg044 The advantage of process swapping is that it extends user space to disk (secondary storage); however, it is not without disadvantages. Swaping requires system overhead to read/write processes to/from secondary storage. Furthermore, excessive amounts of swapping will decrease system responsiveness (i.e. decrease performance). If the cost of memory is more important than user responsiveness, multiply the system's memory require- ment (calculated in steps 1 thru 5) by a value between 0.7 and 1.0. Multiplying the memory required value by 1.0 will cause normal amounts of swapping; multiplying it by 0.7 will cause process to be swappd to/from memory more frequently. Multiplying the "memory requirement" by some value greater than 1.0 will decrease the OS overhead for swapping. NOTE: do not run a system with less than 70% of the "memory required" value -- this will cause excessive amounts of swapping. The result of this calculation is your system's "memory need". 7.1.1 (Cont.) STEP 7 Next compute the number of memory boards that the system needs. Dividing the "memory needed" value, calculated in Step 6, by 256 KB (memory needed / 256 KB). NOTE: 256 KB is the amount of memory on a board. If a fraction results, round off to the next highest whole number. The value calculated is the "number of boards needed". NOTE: A maximum of six memory boards can be installed in an MAI 2000 system. If the value calculated in this step is greater than six memory boards, even with the 0.7 degradation factor (see step 6), you may be overloading your system! 7.1.1.1 Example of How to Calculate a System's Memory Requirement This example shows how to compute the memory requirement for a system with 5 terminals and two printers. Four of the terminals are dedicated to running BASIC applications: accounts receivable, accounts payable, payroll, and word processing. The fifth terminal is used to run the utilities, the commands, or the Informix database application. One of the applications uses a ghost task to output reports to a printer. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg045 7.1.1.1 (Cont.) STEP 1 thru STEP 5: Add these numbers to compute "memory required" 220 KB Base operating sytem 34 KB Table space for base system 37 KB OS dynamic work space for base system 5 KB x 3 Allowance for table space for. three additional users (total of 5 users/terminals) 2 KB Allowance for table space for one ghost task 1.5 KB Allowance for table space for an additional printer (total. of 2 printers) 1.6 KB x 11 Allowance for dynamic work space for three additional users ("procs" - 31 in base). 100 KB Allowance for sytem processes. 30 KB Allowance for concurrent printer to the second printer. 160 KB x 2 Allowance for the BASIC interpreter and for the utilities/commands/Informix 60 KB x 4 Allowance for four concurrent basic applications 64 KB Allowance for one ghost task TOTAL = 1080 KB = "memory required" STEP 6: Compute "memory needed" For adequate system performance with frequent swapping of applications tasks: "memory needed" = 1080 KB * 0.7 = 755 KB For good system performance with normal swapping: "memory needed" = 1080 KB * 1.0 = 1080 KB For best system performance with minimal swapping: "memory needed" = 1080 KB * 1.1 = 1187 KB 7.1.1.1 (Cont.) STEP 7: Compute the number of memory boards required For adequate system performance with frequent. swapping: number of boards = 775 KB / 256 KB = 2.9 or 3 boards Rounding to the next highest whole number means that for this hypothethical system, with frequent swapping of applications tasks, the SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg046 system needs 3 memory boards. For good system performance with normal swapping: number of boards = 1080 KB / 256 KB = 4.2 or 4 boards Rounding down will cause a little more than normal swapping, but this is acceptable if the cost of memory is more important than user responsiveness. With normal swapping 4 boards are required. For best system performance with minimal swapping: number of boards = 1187 KB / 256 KB = 4.6 or 5 boards Rounding to the next highest whole number means that with niminal swapping 5 boards are needed. Furthermore, five boards give the system extra memory, which can be used for additional applications. The approximate method of determining a system's memory requirement (Section 6.1 and Table 6A) shows that a system with 5 users (terminals), 2. printers, and 1 ghost task needs 4 memory boards. The calculation method, described in this section, shows that such a system will have different performance characteristics depending on the number of boards (i.e. either 3, 4 or 5) the system has. 7.1.2 Model 3000 and 4000 This section steps through an example based on system configuration number 3 in Table 6B, a 16 user system for the 3000. The same steps and overhead numbers apply for the Model 4000. (See section 7.1.2.1). 7.1.2 (Cont.) STEP 1 First, add the space required for the operating system, table space, and dynamic space required for the base configuration. NOTE: 1 KB = 1024 bytes 230 KB This is the memory requirement for the base BOSS/IX operating system program. This includes space for the system's interrupt vectors, and operating systems text (code) and data segments. 98 KB** This is the memory requirement for BOSS/IX table space for the base configuration: 2 users (terminals), one printer, and 0 SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg047 gost tasks. NOTE: additional table space must be added for each additional resource above that in the base configuration (see step 2). NOTE: this excludes the memory required for hash tables for buffers and directory entries. 53 KB** This is the memory requirement for the operating system's dynmaic work space (or unswappable memory) for the base configuration (see 7.2.2) STEP 2 Next, add in table space needed for resources beyond the ones described in the base configuration. (If the system will be configured like the base configuration skip this step). NOTE: The MAI 3000 is a table driven system, and for maximum performance extra memory must be allocated for resources beyond the ones described in the base configuration. 41 KB** This is the memory needed as table space for each additional user above the two that are allocated in the base systems. (Refer to Table 7B). 7.1.2 (Cont.) 41 KB** This is the memory needed as table space for each ghost task in the system. (Refer to Table 7B) 2 KB** This is the memory needed as table space for each additional printer above the one that is included in the base system. (Refer to Table 7B) 1.7 KB** This is the memory needed for dynamic work space for each additional process (i.e. "proc") above the 16 that are included in the base system. (Refer to Section 7.2) ** Memory required for BOSS/IX table space and dynamic work space. These values are the memory allowance assumng that the configuration parameters are set according to Table 6B. If the system parameters are set differently, use section 7.4 and Table 7A to calculate the memory required for O.S. table and O.S. dynamic work space. STEP 3 Add the space need for system processes for the base system configuration. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg048 100 KB This is the memory allowance for system tasks. System tasks for the base system include: a printer despooler process, and two command interpreters. The total memory required to have all system processes in memory at the same time is approximately 2000 KB. However, 100 KB should be used in this calculation because system processes wait on system processes will want to execute at the same time. Furthermore, these processes, when waiting for events, can be swapped . to secondary storage, which will have little effect on system performance. STEP 4 Add the space needed for any additional system processes beyond the ones specified in the base configuration. (If the system will be configured like the base configuration skip this step). 7.1.2 (Cont.) 30 KB This is the memory needed for each additional printer despooler, above the one that is allocated in the base configuration. This is a memory allowance for the data and stack segments for an additional despooler task. An allowance for test (code) space is not . necessary, because two despooler tasks will share the same code segments. 15 KB This is the memory required for each user (terminal) that will be executing tasks concurrently. This is the memory allowance for each additional command interpreter. It is space needed for the interpreter. It is space needed for the interpreter's data and stack segments. NOTE: memory allowance for text (code) space is not necessary, because multiple command interpreters share the same code segments. NOTE: If the system is configured for ten operators, but the system only has five terminals-- i.e. a maximum of five users logged in at any instant - - then only 75 KB (5x15KB) need to be allocated. Furthermore, if one of the system terminals is seldom used, then space for that terminal does not have to be allocated. STEP 5 Next, add the space needed for applications processes. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg049 160 KB This is space needed for each unique, non-BASIC task that will be executed concurrently on your system. Such tasks include the BASIC interpreter, utility programs, LAN, Informix, communications, BOSS/IX command interpreter, etc. NOTE: only one BASIC interpreter is needed to support any number of BASIC programs. This value is a rough estimate, for all processes require different amounts of memory, some more some less. 7.1.2 (Cont.) When computing the memory required for application tasks, consider how often each application is used. For example, if the system seldom executes BOSS/IX commands or the utilities, only a percentage of the total space needed to execute these processes will be required. However, when the system is loaded, and these processes are executed, system response time may increase due to excessive amounts of swapping. 60 KB This is the memory required for each BASIC program. This space is the allowance for the data and stack segments for each BASIC program. NOTE: all BASIC programs share the same. text (code) segment. Furthermore, this value is not exact, for some applications may require more memory and some may require less memory. 64 KB This is the memory required for each ghost task that will be executed concurrently. This is the space needed for each ghost tasks' stack and data segments. Text space is not allocated because all ghost share the basic process text segment. The result of the sum of Steps 1 thru 5 is the system's "memory requirement". STEP 6 Determine the memory/performance trade-offs. The value calculated in Steps 1 thru 5 is the "memory required" for good system performance. However, this value is not exact and may be raised or lowered which will increase or decrease performance respectively. By lowering the memory required value one can save the costs of an extra memory board, but at the expense of performance. In other words, systems will run with less memory than required, however, the system overhead for swapping will SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg050 increase. 7.1.2 (Cont.) Process swapping is the action which extends user space to a temporary storage region on disk (i.e. the swap partition) so that during periods of heavy main memory utilization, processes may be stored on disk to make room in memory for processes waiting to execute. The advantage of process swapping is that it extends user space to disk (secondary storage); however, it is not without disadvantages. Swapping requires system overhead to read/write processes to/from secondary storage. Furthermore, excessive amounts of swapping will increase system responsiveness (i.e. decrease performance). If the cost of memory is more important than user responsiveness, multiply the system's memory requirement (calculated in Steps 1 thru 5) by a value between 0.7 and 1.3. Multiplying the memory required value by 1.0 will cause normal amounts of swapping; multiplying it by 0.7 will cause processes to be swapped to/from memory more frequently. Multiplying the "memory requirement" by some value greater than 1.0 will decrease the O.S. overhead for swapping. NOTE: do not run a system with less than 70% of the "memory required" value -- this will cause excessive amounts of swapping. The result of this calculation is your system's "memory need". STEP 7 Next compute the number of memory boards that the system needs. Dividing the "memory needed" value, calculated in Step 6, by 1024 KB (memory needed/1024KB). NOTE: 1024 KB is the amount of memory on a 1 MB board. If a fraction results, round off to the next highest whole number. The value calculated is the "number of boards needed". 7.1.2.1 Second Example of How to Calculate a System's Memory Requirement for Model 3000 and Model 4000 This example shows how to compute the memory requirement for a system with 16 terminals, 4 ghosts and 4 printers; or standard configuration number 3 in table 6. Thirteen of the terminals are dedicated to running BASIC. applications: accounts receivable, accounts payable, payroll, and word processing. The remaining terminals are used to run the utilites, the commands, and the Informix database application. Some of the applications use ghost tasks to output reports to printers. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg051 STEP 1 thru STEP 5: Add these numbers to compute "memory required" 230 KB Base operating system 99 KB Table space for base system 53 KB O.S. dynamic work space for base system 2 KB Hash table space for directory cache entries (tables 10G and 10H) 16 KB Hash table space for disk buffers (tables 10G and 10H) 41 KBX14 Allowance for table space for 14 additional users (total of 16 users/terminals) 41 KB*4 Allowance for table space for 4 ghost tasks 2 KB*3 Allowance for table space for additional printers 1.7 KBX49 Allowance for dynamic work space for 14 additional users ("procs" - base "procs") 100 KB Allowance for system processes 30 KB*3 Allowance for concurrent printing to the 3 additional printers 160 KBX3 Allowance for the BASIC interpreter. and for the utilities/commands/Informix 15 KB*3 Allowance for concurrent terminals 60 KBX13 Allowance for 13 concurrent basic applications 64 KB*4 Allowance for 4 ghost tasks TOTAL = 2979 KB = "memory required" 7.1.2.1 (Cont.) STEP 6: Compute "memory needed" For adequate system performance with frequent swapping of applications tasks and a reduced number of disk buffers: "memory needed" = 2979 KB * 0.7 = 2085 KB or 2 memory boards For good system performance with very little swapping: "memory needed" - 2979 KB * 1.0 = 2979 KB or 3 memory boards For best system performance with much caching: "memory needed" = 2979 KB * 1.3 = 3872 KB or four 1MB memory boards or one 4MB memory boards. The approximate method of determining a system's memory requirement (section 6.1 and Table 6B) SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg052 shows that a system with 16 users (terminals),. 4 printers, and 4 ghost tasks needs 3 Model 3000 1 MB memory boards. The calculation method, descirbed in this section shows that such a system will have different performance characteristics depending on the number of boards (i.e. either 2,3, or 4) the system has. NOTE: In section 7.1.2, all references to memory boards are referring to 1MB memory boards. 7.2 Calculating BOSS/IX Table Space and Dynamic Work Space This section describes how to calculate the size of the operating system dynamic work space needed by any configuration. 7.2.1 Model 2000 The calculation method (section 7.1.1) is accurate if the system's configuration parameters are set according to Table 6E. If the BOSS/IX parameters are not set according to Table 6E, use the method described in this section to calculate the amount of memory needed for table space and dynamic work space. Table 7A shows the amount of memory allocated for each operating system configuration parameter; it shows the parameters for the base system configuration; it shows how the 34 KB value for table space, used in section 7.1.1, was calculated; and it shows the parameters and total table space required for the example system To determine the table space for any configuration multiple the value of each configuration parameter by its corresponding memory allowance (see column 1, table 7A). Next, add the result of these calculations (see column 2). The result is the allowance for table space To determine the memory allowance for operating system dynamic work space (i.e. unswappable memory) use the following formula: "dynamic memory" (bytes) = (17 + ("opens" / 4) + (("procs" * 2636) /512 / 2)) * 512 The variables in this formula from left to right are: 17 - the number of 512 byte pages for miscellaneous operating system space "fds" - the number of open files configured "procs" - the number of processes configured 2636 - the size (bytes) for each process's user area / 512 - for converting into 512 byte pages / 2 - one-half the number of pages * 512 - for converting pages into bytes For the base configuragion the dynamic memory allowance is: "dynamic memory" (bytes) = 17 + (60/4) + ((16 * 2636 /512/2)) * 512 = 37472 bytes or 37 KB SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg053 7.2.1 (Cont.) For the example system (see section 7.1.1) the memory allolwance is: "dynamic memory" (bytes = 17 + (97/4) + ((27 * 2636) / 512/2)) * 512 = 56706 bytes or 55 KB or 37 KB (base size) + 11 * 1.6 KB (extra procs) = 55 KB NOTE: 1.6 is obtained by (55-37) / 11, based on 11 additional "procs", (27-16). NOTE: The operating system dynamic work space -- nick- named unswappable memory -- is a vital work area for the operating system. Within this work area is the process environments (i.e. user area or "uarea") for all active process in the system. Also within this area is printer input and output buffers, ISAM key and dictionary information, and other operating system structures which get dynamically allocated or de-allocated depending on system load. 7.2.2 Model 3000 The calculation method (section 7.1) is accurate if the system's configuration parameters are set according to Table 6F. If the BOSS/IX parameters are not set according to Table 6F, use the method described in this section to calculate the amount of memory needed for table space and dynamic work space. Table 7B shows the amount of memory allocated for each operating system configuration parameter; it shows the parameters for the base system configuration; it shows how the 98 KB value for table space, used in section 7.1.2, was calculated; and it shows the parameters and total table space required for the example system depicted in section 7.1 To determine the table space for any configuration multiply the value of each configuration parameter by. its correspondsing memory allowance (see column 1, table 7B). Next, add the result of these calculations (see column 2). The result is the allowance for table space. 7.2.2 (Cont.) To determine the memory allowance for operating system dynamic work space (i.e. unswappable memory) use the following formula: "dynamic memory" (bytes) = (49 +("fds" / 4) + (("procs" * 2704) / 512 / 2)) * 512 The variables in this formula from left to right are: 49 - the number of 512 byte pages for miscellaneous SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg054 operating system space "fds" - the number of open files configured "procs" - the number of processes configured 2704 - the size (bytes) for each process's user area / 512 - for converting into 512 byte pages / 2 - one half the number of pages * 512 - for converting pages into bytes For the base configuration the dynamic memory allowance is:. "dynamic memory" (bytes = 49 + (60/4) + ((16 * 2704) / 512 /2)) * 512 = 54400 bytes or 53KB For the example system (see section 7.1.2) the memory. allowance is: "dynamic memory" (bytes) = (49 + (218/4) + ((65 * 2704) / 512 / 2)) * 512 = 140872 bytes or 138 KB or 36.6 LB (base size) + (49 * 1.7 KB) (extra procs, 65-16) = 120 KB NOTE: 1.7 is obtained by 138-53) / 49, the additional "procs" (65-16). NOTE: The operating system dynamic work space -- nick- named unswappable memory -- is a vital work are for the operating system. Within this work area is the process environments (i.e. user area or "uarea") for all active process in the system. Also within this area is printer input and output buffers, ISAM key and dictionary information, and other operating system structures which get dynamically allocated or de-allocated depending on system load. _______________________________________________________________________________ ______ | | | | | | | | | BOSS/IX | memory | param.'s | total | param.'s | total | Memory for each | | PARAMETERS | used for | for base | memory | for | memory | additional : | | (set by | each | config- | for base | example | for | | | "vconf") | param. | uration | system | system * | example | | | | | | (bytes) | system | (bytes) | | system | USER|GHOST| PRINTER| | | | | | | (bytes) | | | | |buffers= | 594 | 20 | 11880 | 32 | 19008 | 2376| | | |printers= | 906 | 1 | 906 | 2 | 1812 | | | 906| |procs= | 324 | 16 | 5184 | 27 | 8748 | 972| 324| 324| |tsegs= | 24 | 16 | 384 | 22 | 528 | 40| | SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg055 | |locks= | 40 | 74 | 2960 | 94 | 3760 | 200| 200| | |ibsize= | 128 | | 256 | | 640 | 128| | | |tbsize= | 64 | | 128 | | 320 | 64| | | |mfsys= | 424 | 3 | 1272 | 3 | 1272 | | | | |lus= | 44 | 136 | 5984 | 224 | 9856 | 800| 880| 264| |fds= | 92 | 60 | 5520 | 97 | 8924 | 736| 920| 172| |eventcalls= | 20 | 16 | 320 | 95 | 1900 | 32| | | | | | | | | | | | | |TOTALS | -- | -- | 32388 | -- | 52590 | 5148| 2144| 982| | | | | | | 51 KB | 5 KB| 2 KB| 1 KB| | | | | | | | | | | NOTES: * See section 6.2, Table 6E. It explains how the parameter values (columns 2 and 3) for the base system and example system were derived. Table 7A BOSS/IX Operating Parameters and Memory Requirements (Table Space) for Model 2000 _______________________________________________________________________________ ________ | | | | | | | | | BOSS/IX | memory | param.'s | total | param.'s | total | Memory for each | | PARAMETERS | used for | for base | memory | for | memory | additional : | | (set by | each | config- | for base | example | for | | | "vconf") | param. | uration | system | system * | example | | | | | | (bytes) | system | (bytes) | | system | USER | GHOS T|PRINTER| | | | | | | (bytes) | | | | **|buffers= | 594*| 128 | 76032*| 1280 | 760320*|38016*|380 16*| | |printers= | 906 | 1 | 906 | 4 | 3624 | -- | -- | 268 | |procs= | 324 | 16 | 5184 | 65 | 21580 | 996 | 332 | 332 | |tsegs= | 24 | 16 | 384 | 44 | 1056 | 48 | | | |locks= | 40 | 74 | 2960 | 164 | 6560 | 200 | 200 | | |ibsize= | 128 | 2 | 256 | 16 | 2048 | 128 | SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg056 | | |tbsize= | 64 | 2 | 128 | 16 | 1024 | 64 | | | |mfsys= | 424 | 3 | 1272 | 4 | 1696 | | | | |lus= | 44 | 136 | 5984 | 556 | 24464 | 880 | 880 | 264 | |fds= | 92 | 60 | 5520 | 218 | 20056 | 736 | 920 | 172 | |eventcalls=.| 20 | 16 | 320 | 56 | 1120 | 40 | 100 | | |dirc= | 48*| 64 | 3027*| 338 | 16224*| 384*| 480 *| 96*| |. | | | | | | | | | |TOTALS | | | 102018*| | 859792 |41492*|40928 *| 1132 | | excluding | --- | --- | or | --- | or | or | or | or | | hash tables| | | 99 KB*| | 839 KB*|40 KB*|40 KB *|1.1 KB | |. | | | | | | | | | |TOTALS | | | | | | | | | | hash tables| --- | --- | 101 KB | --- | 853 KB |41 KB |41 KB | 2 KB | |. | | | | | | | | | Table 7B BOSS/IX Operating Parameters and Memory Requirements (Table Space) for Model 3000/4000 * Excludes hash table size which must be calculated separately based on the number of entires requested, then added to the total system requirement. ** Size, number of calculation differs from Model 2000 __________________________________________ | | | | Number of | | | Entries | Memory | | Requested | Required | | | | | through 63 | .5 KB | | | | | 64 through 127 | 1 KB | | | | | 128 through 255 | 2 KB | | | | | 256 through 255 | 4 KB | | | | | 512 through 1023 | 8 KB | | | | | 1024 through 2047 | 16 KB | | | | | 2048 through 4095 | 32 KB | SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg057 | | | | 4096 through 8191 | 64 KB | | | | | 8192 through 16383 | 128 KB | | | | This table is used to obtain the amount of memory needed for hash tables for either the 'buffers' or 'directory cache' operating parameters (see Table 7B). The per entry charge is not included here and must be added to the value from this table. Table 7C Memory Required for Hash Tables 8.0 New and Updated Manuals for Level 7.4A and Related 7.3 Manuals M6211B BOSS/IX (7.4) User Reference Manual M6227B BOSS/IX (7.4) Technical Reference Manual * M6201A MAI 2000 User Guide M6202B MAI 3000/4000 User Guide * M6360A MAGNET BOSS/IX User Reference Manual * M6262A BB86 Reference Manual * M6353C BOSS/IX TBC (2780/3780) User Reference Manual * M6352A FTF Users Reference Manual (updated) * M6354D Intersystem Transport Manual (updated) * M0053A Universal Printer Driver Reference manual (new) * M7510A Business DATA System Support Manual (new) * M7511A Business DATA Report Program Generator User Guide (updated) M6204A MAI 3000/4000 Diagnostic and Error Logging Reference Manual M6358A BOSS/IX 3270 BSC Emulation User Reference Manual * Released for 7.3 9.0 Lowest Acceptable Revision Levels (LARL) DESCRIPTION P/N LARL SYSTEM CMB, CENTRAL MICROPROCESSOR BOARD, 16 BIT 903441 AU 2000 CMB, CENTRAL MICROPROCESSOR BOARD, 16 BIT, with 1/2" Boot Support 903441 * BE 2000 SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg058 128K/256K MEMORY 903368 A 2000 4 WAY CONTROLLER 903390 * W 2000/3000/4000 MCS STREAMER CONTROLLER 903406-001 Y 2000/3000/4000 MCS STREAMER CONTROLLER 903406-002 Y 2000/3000/4000 LAN, LOCAL AREA NETWORK CONTROLLER 903405 D 2000/3000/4000 WDC WINCHESTER, ADAPTER BOARD 903439 B 2000 ADAPTEC BOARD 907649 E 2000 POWER SUPPLY ASSEMBLY 907472 E 2000. 1 BOARD WINCH. CONTROLLER 903496 R 2000/3000/4000 1/2" STREAMER BUS ADAPTER 903528 A 2000/3000/4000 3000 POWER SUPPLY 907897 E 3000/4000 CMB 32 BIT D.S.C 903593 * U 3000 CMB 32 BIT D.S.C 903631-00 * K 3000/4000 1MB MEMORY 903533 * D 3000/4000 8-WAY CONTROLLER 903577 * F 3000/4000 MMB (Used on 903593 or 903631-001 Only) 400650 L 3000 4 MB MEMORY 903575 * D 4000 9.0 (Cont.) DESCRIPTION P/N LARL SYSTEM EXPANSION INTERFACE A 903645-001 * B 4000. EXPANSION INTERFACE B 903643-001 * A 4000 10.0 Helpful Hints This section gives miscellaneous information about the 7.4A O.S. release and the MAI 4000 system. 10.1 Four-way and Eight-way Configuration o A maximum of nine Eight-ways are allowed in the MAI 4000 system. o Four-ways are not allowed in the Expansion Unit. 10.2 Memory Configuration o The MAI 4000 system and 7.4A O.S. only support up to. 16 Mb of RAM. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg059 o The MAI 4000 only supports up to six memory boards. This could include 4 Mb boards and 1 Mb boards. 10.3 Disk Configuration o The MAI 4000 supports up to seven disk drives. They. are installed with three drives in the main unit and four drives in the expansion unit. o The disk drives must be specified by device name according. to the following diagram. ----------- ----------- \ \ \ \ \ 2 \ \ 6 7 \ \ \ \ \ \ \ \ \ \ 0 1 \ \ 4 5 \ \ \ \ \ ----------- ----------- BASE UNIT EXPANSION UNIT There is no Drive 3 as the tape drive goes in that position. To find the Minor number for the drives use the formula: DRIVE # * 32 = DRIVE MINOR NUMBER For example Drive 6 would have minor 192; 6*32=192 ORIGINATOR: Julia Shreve UPDATED BY: JAVIER VAN OORDT SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB039 Pg060 FIB 00040 04/15/88 *** Announcing the 7.2P O.S. for system 1800 [ WPS 408 A ] *** Level 7.2P BOSS/IX operating system and its related software products are now available for the MAI 1800 system. The 7.2P release is the recommended operating system level for the MAI 1800 system. 7.2P corrects a probelm that existed on 7.2N where in certain circumstances string variable corruption under BASIC occurs. The problem occurred due to a memory compaction bug in BASIC. This problem could cause a problem with a file if a field in a record is corrupt before it is written to disk. It is recommended that a printout of all data files used under 7.2N be done to check for any corrupt records. NOTES: 1. 7.2P requires the installation of a 7.2P configuration record. Before installing 7.2P, verify that you have the new 7.2P configuration record. 2. Refer to MAI 1800 Software Announcement #152 for details on installation. If the 7.2N OS is already installed, follow the BOSS/IX System Upgrade/Reinstall Procedures. 3. The Release Level when doing an 'iconf' display will now show 7.2@. ORIGINATOR: Dan Wenzel SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB040 Pg001 FIB 00041 06/27/88 *** Release Notification and Problems with 7.4A O.S. [ WPSF 449 ] *** Level 7.4A of BOSS/IX is now available. It is the recommended Operating System for MAI 2000 and MAI 3000 systems, and is the only Operating System for the MAI 4000 system. The 7.4A O.S. is derived from the 7.3A O.S., so the following list of the enhancements/ corrections are also enhancements on the 7.3A O.S. release. o Shared libraries o Improved 1/2 inch tape support o Merged tape commands and utilities o UPD (Universal Printer Driver) o Console configuration changes o vconf file changes o System configuration record format changes o System dump changes o BB86 o Diagnostic partition o New user error logger o File integrity flag o Bad block retirement This Field Bulletin contains Warnings and Cautions and possible workarounds for Level 7.4A BOSS/IX operating system. Installation and upgrade procedures are fully documented in the 7.4A Software Announcement. Warning: When upgrading from 7.2 to this release on a 3000 system, the system serial number MUST be reinstalled using the new 2000/3000/4000 SSN program. DO NOT attempt to upgrade a 3000 system without reinstalling the system serial number using the new 2000/3000/4000 SSN program. Warning: In order to install the systems properly, the 7.4A 2000 O.S. tape must be used to install a MAI 2000 system, and the 7.4A 3000/4000 O.S. tape must be used to install the MAI 3000 and MAI 4000 systems. Warning: With BB86, BASIC programs are not backward compatible. You must use the conversion facilities to take the programs backward to a 7.2 or prior release. This section gives the warnings and cautions for the 7.4A Operating System and a workaround if one is available. Operating System (EOS) 1. If you change the value of the high bit flag in the /etc/class file, it is ignored. o No workaround is available. 2. When the pitch or the lines per inch field in the /etc/forms file is changed, the value will be ignored. o Use the mnemonic or hex value in the BASIC program to change lines per inch or pitch. 3. When the slew channels are used in the /etc/forms file, the SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB041 Pg001 channels will be ignored. o Set up the slew channels in the BASIC program. 4. An error -92 can occur while running tsave using 1/2 inch tape across multiple tapes. o Split the backup into two filelists, then back them up a tape at a time. BASIC (EBS) 1. Composite fields whose starting position is not specified and whose length is specified thru ":" are not interpreted correctly. Example "F2#=F1#:8" o Specify the starting position. Example: "F2#=F1#(1):8" or "F2#=F1#(1,8)" 2. If a composite field is defined thru "(s):1" before its component field is defined in the format string. Example: "F1#=N10 PRIMARY F2#=F1#(1):12 F3#=N5", then the record size is not computed correctly. o Use "(s,1)" format instead. Example: "F1#=N10 PRIMARY F2#=F1#(1,12) F3#=NS". 3. If a composite field is defined beyond the end of fixed fields. then the size of the record is not extended. Example: "F1#=N10 PRIMARY F2#=N5 F3#=F1*(1,18)", o Define an additional fixed field. Example: "F1#=N10 PRIMARY F2#=N5 F3#=F1*(1,18) F4#=lN3". 4. Variable-length fields within multi-keyed files will sometimes be read as empty or zero when they have been written with some other value. o There is no work-around. It is recommended to avoid using variable length fields. 5. A rolling "Error in for/gosub stack" message may cause a terminal to hang. This occurs if a program is in the middle of a SETESC or SETERR handler, and the program is changed by adding, editting or deleting line(s) of code. o This may be avoided by using END, RESET or EXITTO before the code change, to reset the for/gosub stack. FTF via LAN and X.25 1. Constant full duplex file transfers (simulataneous transfers in both directions) can cause the X.25 link to fail after approximately 30 hours. o If link failures occur, decrease the amount of full duplex file transfers. 2. When there is heavy activity on the system, enough to cause swapping of processes, abort 79's can occur. o Use the rescheduling option of FTF or schedule files during SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB041 Pg002 non-peak hours. 3. File transfers of a file on a remote system (i.e. a system connected via LAN) is not supported and will cause the session to be "In Progress" forever. o This feature is currently not supported and should not be used. MAGNET via LAN and X.25 1. When rcopy is used to update a remote file (replace existing files) and the destination file is currently locked by another process, the copy will still occur and the data is 'temporarily stored' in the remote system until the file is unlocked. There is no message on the source systems stating this is so. o No workaround. This is the same implementation of a local copy command. 2. When performing an 'EXTRACT' and 'REMOVE' of a keyed record on a remote file, the process will suspend, if the 'KEY=' option is not used. o Save the 'KEY' from the 'EXTRACT', and use it with the 'REMOVE' directive. 3. LAN timeout errors -554 or -527 occur with moderate to heavy full duplex remote file activity. These errors are caused by the remote file access processes being swapped out. o Retry operation. Reduce heavy full duplex activity or reduce processing on the remote system. Intersystem Transport Package (EIT) 1. EIT will no longer support mixed format schema files. Only TEXT (convert all data) and BINARY (don't convert all data) are supported. 2. ATP 4.0 is released with the EIT product. ATP 4.0 is NOT compatible with previous releases of ATP. 3. Only files which are compatible between unlike systems can be transferred - i.e. string file transmissions can only occur between BOSS/IX systems. 4. ATP 4.0 supports direct connections between 1200 - 9600 Baud. ATP 4.0 supports modem connections of 1200 and 2400 Baud using the following modems: UDS 212A UDS 212 A/D UDS 224 A/D UDS FASTTALK "Hayes compatible" HAYES Smartmodems 3270 Bisync 1. As with previous releases, the 4310 (EDT) is the only terminal supported as a 3278 display terminal. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB041 Pg003 SSN REINSTALL REQUIREMENTS When upgrading a MAI 3000 from 7.3A to 7.4A or above, the SSN does not need to be re-installed. The SSN only needs to be re-installed if you are upgrading from 7.1 or 7.2 Operating System, to a 7.3A or higher release. NOTE: When upgrading the MAI 2000, the SSN does not need to be re-installed. ............................................................................... TERMINAL/SYSTEM HANGS caused by RELEASEing a BASIC task A problem has been reported from the field, that when you set up the start process for a terminal port through the 'configure' utility to be /bin/basic, everything will appear fine until the terminal tries to logoff using the RELEASE directive. The terminal will hang, and any other terminal that logs off after this or tries to log on will hang because the PID of 1 was killed (on an MAI 2000) or suspended (on an MAI 3000 or 4000). The cause of this problem is related to the change in the RELEASE directive for BB86. There are two workarounds for this. First, set up your terminal ports for /bin/login, and let their user id put them into BASIC. The second workaround is to use the QUIT directive when exiting instead of RELEASE. ............................................................................... The following is a list of system error codes, produced by UPD, and not found in the comerr. list. Error No. Description of Problem -3001 bad opcode passed to evaluater -3002 invalid value passed to the evaluater -3003 not enough operands for the operation -3004 operands left on stack after eval is complete -3005 attempt to divide by zero -3006 evaluation stack overflow -3007 stack start pointer > stack end pointer -3008 starting on an odd memory address -3009 offset does not point to a buffer -3010 offset does not point to a character -3011 offset does not point to an integer -3012 call found nothing in output buffer -3013 no response on printer read -3014 bad value passed -3015 attempt to evaluate invalid function code -3016 the program counter got past the end of PDF -3017 end of PDF section -3018 bad length -3019 bad position -3020 a bad offset into the dsz or var sections -3021 type is not an attribute type -3022 this error is returned by the exit statement -3023 bad PDF -3024 no memory -3025 the SIMPLE buffer is full -3026 a bad mnemonic was found SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB041 Pg004 -3027 there is no PDF section -3028 the PDF tried to access the user buffer in a section that does not allow it -3029 the form length is too long -3030 expected an attribute string -3031 received a bad mnemonic -3032 internal bug -3033 the SIMPLE program requested a mnemonic parameter and there was none -3034 the program requested a mnemonic parameter but the user gave the wrong type ............................................................................... 449 Addendum0-6A When copying or moving a indexed or serial file using the 'fcopy' or 'fmove' utility, the record size may increase to equal the 'number of records maximum' in the file it is copying or moving. For example: Record Size # of Records Before 'fcopy' 400 2000 After 'fcopy' 2000 2000 The workaround for this problem is to use the 'copy' or 'move' command instead of the 'fcopy' or 'fmove' utility. For example: copy /dir1/filename /dir2 -v or move /dir1/filename /dir2 -v ............................................................................... 449 Addendum-7 Parity errors may occur on T0 and additional messages will appear during boot on MAI 2000, MAI 3000 and MAI 4000 systems running 7.4A Operating System. This is caused by the 'verbose' flag being set in the 'vconf' setup. This can be stopped by setting the '-silent' option in the vconf parameters. This is done by doing the following from the ADMIN> prompt: mount /dev/boot /mnt vconf /mnt/etc/conf -silent -save unmount /mnt You must reboot the system before this will go into effect. ............................................................................... 449 Addendum-8 The 'pparams' utility will suspend on 7.3A and 7.4A if the size of the user's '/etc/passwd' file is greater than 256 bytes. Workaround: Move '/etc/passwd' to a temporary file, for example: SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB041 Pg005 move /etc/passwd /etc/orig.passwd -v Then run the 'oprinfo' utility, which will create a new '/etc/passwd' file. Create 'admin' and any other user who will need to access 'pparams'. After the new '/etc/passwd' file has been created, you can run the 'pparams' utility. If you wish to keep a copy of the temporary file, copy it to a temporary name, for example: copy /etc/passwd /etc/temp.passwd -v After you have finished running 'pparams' and you have copied the temporary password file to a temporary name, you must move the original '/etc/passwd' back, for example: move /etc/orig.passwd /etc/passwd -v ............................................................................... 7.4A TBC - Error 12 Occurs Tony Tiangco 6-3-88 449 ADDENDUM-9 Modifying Transmit Queue PROBLEM: An error 12 occurs when modifying a transmit queue that was created on 7.2B EBC and was converted using the 7.4A utility FCONVERT. SOLUTION: 1. Append the underlined portion of the statement below to 1610 in program '/util/FCONVERT'. 1610...R$(9,A9); IF X6$="NONE" THEN X6$="" ___________________________ 2. RUN "util/FCONVERT" to re-convert your 7.2B transmit queue. FUTURE: This problem will be corrected in a future release of TBC. ............................................................................... Larger Partition Size For Carlos Figueroa 6-3-88 449 Addendum-11 7.4A*27 Diagnostics PROBLEM: 7.3A*12 Diag. = 1200 sectors 7.4A*27 Diag. = 1300 sectors Since the new diagnostics require an extra 100 sectors on the diagnostic partition, caution should be taken before installing the 7.4A*27 diagnostics on the hard disk. If an attempt is made to install the 7.4A*27 diagnostics on the disk without increasing the diagnostic partition using the 'sbinit' command, a "BAD DISK FORMAT ERROR" will occur when loading from disk. This error indicates a blown superblock and a disk format will be needed to continue. SOLUTION: o Make sure you have a FULL BACK-UP before increasing the diagnostic partition. o 'sbinit' to destroy all data on disk. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB041 Pg006 o After the completion of the BACK-UP, a new diagnostic partition can be defined. Set up (define) the new partition size to 2000 sectors. Assigning 2000 sectors to the diagnostic partition will allow the installation of any future release without these complications. ORIGINATOR: Julia Shreve SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB041 Pg007 FIB 00042 04/20/88 *** Err -92 on continuation tape using tsave at level 7.3 [ WPSF 451 ] *** Problem: Error -92 when going to the 2nd tape on a 1/2" MTS backup. Cause: The continuation save-set size is greater than the controller buffer size. The save-set is created at the time the tsave is executed. The save-set size is determined by the number of files and length of filenames. When the system attempts to write the continuation saveset to the 2nd tape, the -92 error is generated. Workaround: Change the backup procedure to be two 'smaller' backups, instead of one 'large' backup. Create filelists of the filenames to be backed up and use the filelist options in the tsave command/utility. ORIGINATOR: Pamela Thatcher SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB042 Pg001 FIB 00043 04/20/88 *** Basic error 65 at level 7.3 OS [ WPSF 455 ] *** Problem: The file lacks integrity. Cause: There is a flag in the file header that is set when a file is written to while it is in memory. This flag is reset when the data in memory is written to the disk file by either a 'buffer flush' and/or a file close. If a pre-mature shutdown occurs prior to the time that the changes are written to the disk this flag will show that the file lacks integrity. Workaround: Repair the file using the frepair utility. To avoid this error, before you start processing after recovering from a system crash follow these steps: 1. Use the fichk command with the filelist option to generate a list of all files that lack integrity. The filelist will be '/util/fl/fichk.f'. Example: fichk / -filelist 2. Use the frepair utility, specifying 'fichk.f' as the filelist name, to repair the files which lack integrity. ORIGINATOR: Pamela Thatcher SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB043 Pg001 FIB 00044 04/20/88 *** Error 31s while upgrading or adding devices [ WPSF 453 ] *** A BASIC error 31 can occur when either upgrading a system, or adding devices. This is normally caused by insufficient 'vconf' parameters. If the error 31's occur after either of the above procedures, increase the following 'vconf' parameters by the associated values: procs - 8, tsegs - 4, eventcalls - 4. This might need to be done two times in order to cure the error 31's. If the error 31's still occur after rebooting, and the START sizes for the processes are sufficient, please call Field Product Support. ORIGINATOR: Julia Shreve SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB044 Pg001 FIB 00045 08/16/88 *** Paradyne 1200/2400 Modems Supported on 7.4A TBC [ WPSF 449-12 ] *** The Paradyne 1200 and 2400 FDX Plus modems are supported on 7.4A with TBC. They were inadvertently left out of the 7.4A Software Announcement as supported modems. The switch settings for using the Paradyne modems with TBC are documented in Hardware Announcement #16 on pages 4,5 and 6 and in COMMUNICATIONS-BASIC FOUR-COMMUNICATIONS FIB 30. NOTE - You must have a Paradyne on both the sending and receiving system to use with TBC. ORIGINATOR: Tony Tiangco SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB045 Pg001 FIB 00046 12/27/88 *** Rel. 7.2R Available for 1800 Systems - Known Problems [ WPSF 494A ] *** Level 7.2R BOSS/IX operating system and its related software products are now available for the MAI 1800 system. 7.2R contains several enhancements and corrections. It is recommended that all systems be updated with the 7.2R release. MAI 1800 EIT tape transport tools (xcread, cwrite, etc.) are available for intersystem tape transport between the MAI 1800 system and other MBF systems. The EIT tools are not included with the 7.2R base system. However, these non-supported tools are available as a separate installable product. Please contact your regional office for a copy of the EIT tools diskette and associated documentation. Standard save/restore tapes are not compatible between the MAI 1800 and other BOSS/IX systems (i.e., 2000/2500/3000/4000). Therefore, the EIT tools on ATP must be used to transport programs and data files between systems. The 7.2R Software Announcement #160 contains general information about the 7.2R release. Please read this document before installing any 7.2R systems. For ordering information, refer to the appropriate Marketing Announcement. WARNINGS: An MAI 1800 system running an operating system release prior to 7.2R requires a full installation. Do NOT use the Upgrade/Reinstall procedures unless 7.2R has been previously installed. The 'Hard Disk Preparation' procedure outlined@Mn the 7.2R Software Announcement #160 is different from the procedure outlined in the MAI 1800 Software Announcement #152. Please follow the procedure outlined in the 7.2R announcement. Software Announcement #152 should be used for other helpful information related to the MAI 1800 system. Modifying the vconf parameters in such a way that more memory is needed than is physically installed will cause a system crash (See section 6.1 of the MAI 1800 Software Announcement #152 for details). CORRECTIONS TO 7.2P o EOS - Corrected a problem where the 8-way driver truncated on-going print jobs when a new job was submitted to the same port. - Corrected a problem where a 'drestore' terminated without any error message before restoring the complete backup set. - Fixed the problem where the 'badtrk' command incorrectly handled alternate tracks. - Corrected a UPD problem where random system crashes occurred when trying to free memory that had already been freed. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB046 Pg001 - Corrected a problem where data was lost when printing to a parallel printer while security plug was being checked. - Corrected a problem where a mount form message is issued every time a printer is opened from BASIC. - Corrected a problem where the 'TS' mnemonic used in position 0,0 crashed the system. - Corrected a problem where once a write protect error was detected on a floppy it could not be cleared until the system was booted. - Corrected a problem where data overrun on the COM1 or COM2 ports could cause a system crash. - Corrected a problem where errors in initialization after a dump would cause another crash. Therefore, the data from the first dump would be wiped out. - Fixed a problem where parallel printer interrupts were lost during heavy system activity, causing the print job to start over. - The message requesting a floppy after a system crash was changed to "Insert dump diskette...". - Released new PDF's to solve extra form feed and positioning problems with Letter Quality Printers. - Fixed a problem where a terminal had a slow response time when configured on an 8-way and executing an INPUT with positioning. - Added retry logic for the SSN security device check. This alleviates system crashes with a crash code = 50 which was sometimes caused by a marginal (slightly malfunctioning) security device. Errors caused by a marginal device are now logged in the system error logger with this information: NMI Type: -132 A: 1, 2 or 3 B: 11181 C: hex value D: hex value A = 1 or 2 Used by engineering to determine where in the polling sequence the error occured. A = 3 This failure was caused by a mismatch between the serial number in the plug and the serial number in the configuration record. C: & D: These fields are used only when A = 3. This information is also used by engineering. If the security device fails the retry logic, the system will crash with a crash code = 50. A crash code = 50 indicates a bad or missing SSN device. - Fixed a problem where a terminal had a slow response time when configured on an 8-way and executing an EDIT. - The 4215 PDF was modified to remove an extra form feed. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB046 Pg002 - Error 5 (parity error) was reported every time an error occurred in the tty driver. The proper error is now returned. - Fixed the 'TS' mnemonic on the system console. - Corrected a problem where the system would crash when out of memory on a CALL, ADDR, or ADDE from BASIC. - The 'iconf' command now reports the correct system level for releases above "O". - Two kernel files were modified to enable EIT to process large files created on an MPx system. - Fixed a problem where the current record pointer was incorrectly incremented after an unsuccessful move operation. - Fixed a problem where LQP created a bad temp file when the PID incremented to 6 digits. - Fixed a problem where BASIC was unable to open LP when the PID was 6 digits. o EBS - Corrected a problem where a corrupted program suspended or crashed when loaded. - Corrected a problem where subscripting a nested array doesn't access the correct element. - Corrected a problem where an error 41 was generated when calling a program with an uninitialized variable. - Corrected a problem where an error 41 was generated using the bsearch utility with certain boundary conditions. - Corrected a problem where an error 19 was generated in certain cases running BASIC. - Corrected an error 33 problem under BASIC. - Passing an unitialized variable to a CALLed program now works properly. - A SETESC-RETURN in a CALLed program now works properly. - Corrected a problem where 7.3 keywords were not allowed as variable names. - Corrected a problem where unpredictable results occurred when a data area larger than 32K existed in a RUN program, and an uninitialized string variable was passed to a CALLed program which then attempted to modify that variable. - TSK(0) now reports GA thru GF. - Pressing the escape key during execution of a BASIC directive that was being executed by the EXECUTE directive caused the next EXECUTEd directive to drop SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB046 Pg003 into console mode after completion. This now works properly. - Fixed a problem where BASIC suspended during a particular user application. - Fixed a problem where ON 65536 GOTO xxx,yyy caused BASIC to suspend. - Fixed a problem where 'bencrypt' got an error 19 when processing BASIC programs greater than 32K. o Commands - 'mcssave' with the ip= option nows works properly. - Corrected a problem where the 'move' command would change ownership in certain circumstances. - 'mcssave' and 'mcsrestore' now process files greater than 64K correctly. o EUT - Corrected a problem where an error 0 occurs using 'msave' with BASIC programs greater than 32K bytes in size. - Corrected a problem where using a filelist whose name is 8 characters suspends utilities. - Corrected a problem where removing a slave printer under 'configure' would suspend the 'configure' utility. - Corrected a problem where 'sformat' would not report errors encountered during diskette format verification. - Corrected a problem where 'frepair' suspended when processing large BASIC programs. - Corrected a problem where 'msave' did not log files which could not be saved due to being locked on another terminal. - ddisplay, finfo and fchange now display the correct information for files greater than 32K in size. - Fixed a problem where 'sformat' caused a system crash by not checking for device busy before initializing floppies. - Corrected a problem where 'msave' suspended when MBII was pressed at the 'modify tape label' prompt. - 'msave' and 'mrestore' now process files greater than 64K correctly. ENHANCEMENTS TO 7.2P o EOS - A new PDF was added to allow the configuration of a serial and/or parallel PT-4222. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB046 Pg004 WARNINGS & CAUTIONS Following are some problems and helpful hints related to 7.2N, 7.2P, and 7.2R. 1. Problem: The "." located on the numeric keypad of the MAI 1800 system console will produce a with or without the NUM LOCK active. Workaround: The following can be used if the user doesn't need the : o admin>cd /etc/ttyxlt o admin>copy conout conin o admin>makettyxlate conin _________________________________________________________ | | | | 00 10 20 30 40 50 60 70 80 90 A0 B0 C0 D0 E0 F0 | | ______________________________________________________ | | 00 | 00 10 20 30 40 50 60 70 80 90 A0 B0 C0 D0 E0 F0 | | 01 | 01 11 21 31 41 51 61 71 81 91 A1 B1 C1 D1 E1 F1 | | 02 | 02 12 22 32 42 52 62 72 82 92 A2 B2 C2 D2 E2 F2 | | 03 | 03 13 23 33 43 53 63 73 83 93 A3 B3 C3 D3 E3 F3 | | 04 | 04 14 24 34 44 54 64 74 84 94 A4 B4 C4 D4 E4 F4 | | 05 | 05 15 25 35 45 55 65 75 85 95 A5 B5 C5 D5 E5 F5 | | 06 | 06 16 26 36 46 56 66 76 86 96 A6 B6 C6 D6 E6 F6 | | 07 | 07 17 27 37 47 57 67 77 87 97 A7 B7 C7 D7 E7 F7 | | 08 | 08 18 28 38 48 58 68 78 88 98 A8 B8 C8 D8 E8 F8 | | 09 | 09 19 29 39 49 59 69 79 89 99 A9 B9 C9 D9 E9 F9 | | 0A | 0A 1A 2A 3A 4A 5A 6A 7A 8A 9A AA BA CA DA EA FA | | 0B | 0B 1B 2B 3B 4B 5B 6B 7B 8B 9B AB BB CB DB EB FB | | 0C | 0C 1C 2C 3C 4C 5C 6C 7C 8C 9C AC BC CC DC EC FE | | 0D | 0D 1D 2D 3D 4D 5D 6D 7D 8D 9D AD BD CD DD ED FD | | 0E | 0E 1E 2E 3E 4E 5E 6E 7E 8E 9E AE BE CE DE EE FE | | 0F | 0F 1F 2F 3F 4F 5F 6F 7F 8F 9F AF BF CF DF EF FF | |________________________________________________________| o Replace position 7F with a 2E and save the modified translation table. o Modify T0 using the port configuration utility. Change input translation to 'conin'. o Shutdown the system and reboot. The '.' on the numeric keypad will now be a '.'. 2. Problem: Error 47 using 'bsearch' at statement 640 in program PSRCH. Workaround: Modify line 120 of /util/SREP to look like: 120 LET PTR=PTR+LENG; IF PTR+11>LEN(DATA$) THEN GOSUB 3000 3. Problem: Input translation tables for the system console do not work correctly for non-U.S. keyboards. The keyboard driver assumes a U.S. English layout. The problem is that several keys such as "*" occur twice on the keyboard, one "*" needs to have its ASCII code changed to "(" the other needs to keep the same code. The input translation table is not capable of this. So with these keyboards 2 different characters get SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB046 Pg005 the same code. Workaround: MAI Belgium created a workaround for the French keyboard. There is currently no workaround for other international keyboards. 4. Problem: The system will not recognize any changes to a mnemonics table unless the name of the mnemonics table is changed or the system is rebooted. Workaround: You must either rename the modified mnemonics table or reboot the system for the changes to be recognized by the system. 5. Problem: Configuring a 7.2R system using all the maximum numbers (procs, lus, buffers etc.) in the Technical Reference Manual will cause the system to crash. When the vconf parameters are set to their limits, the configured resources require more memory than the system supports. Workaround: The Technical Reference Manual includes tables which identify the recommended "vconf" parameters according to the number of terminals, printers and Ghost tasks to be used on the system. When configuring "vconf" parameters, the values in these tables should be used. 6. Problem: GHOST tasks will not start up and no error will be generated indicating that the GHOST didn't start up if the vconf parameters are too small. Workaround: Increase the vconf parameters. Unfortunately the minimum parameters needed to start a GHOST task is unknown, so slowly increase all parameters until the task will start. 7. Problem: The system clock loses time during heavy system usage such as during tape I/O. Workaround: None. Set the system clock to the correct time as necessity reqires. 8. Problem: BASIC errors 5 and 34 occur when transferring data throgh the Serial/Parallel card and, at a much lesser frequency, on the 8-way. Workaround: Heavy port usage should be made through the 8-way. 9. Problem: COMx devices configured with DTR will not work properly. Workaround: If you must use DTR, configure those devices on the 8-way. 10. Problem: The BASIC 'TR' mnemonic (Terminal Read) causes terminals attached to the serial port of the serial/parallel controller to hang. The system must be rebooted for the port to come back. Workaround: Run programs which use the 'TR' mnemonic on 8-way terminals only. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB046 Pg006 11. Problem: msave utility allows spaces in saveset names while the mrestore utility does not. mrestore cannot restore a saveset name with spaces in it. Workaround: Specify the saveset number to restore a saveset with spaces in its name. 12. Problem: msave utility 'verify' option fails if the saveset name is generated by the system rather than the user and End of Tape (EOT) is encountered before all the files are saved. Workaround: Specify a saveset name rather than let the system generate one for you. 13. Problem: mcsrestore command 'before' option fails to restrict files whose dates are after the 'before' data from being restored. mcsrestore command 'since' option doesn't allow any files to be restored rather than just those whose dates are after the 'since' date. Workaround: None. 14. Problem: mcsrestore utility restores a different number of files to disk than it reports that it did if the 'sf=' option is used. Workaround: Ignore the numbers reported. All files are correctly restored using the sf= option. 15. Problem: frepair utility hangs if attempting to repair a BASIC program file whose size is greater than 41K bytes. Workaround: Delete the corrupted large program and restore a backup copy of the program. 16. Problem: medit '-i' option will corrupt all messages. Workaround: Select the medit option to rebuild both index and text files together to avoid message corruption. 17. Problem: It is very rare, but entering BASIC has caused an exec error -29184 to occur locking the user out of BASIC. Workaround: The system must be rebooted to recover the terminal. 18. Problem: exec command 'floor=' and 'ceil=' options, when set to greater than 8 are ignored by the system which sets the processes priority to something less than 8. Workaround: None. Don't set 'floor' and 'ceil' priorities to greater than 8. 19. Problem: BASIC suspends attempting to create programs with names that are the same as terminal devices, ie. T0, T1, ..., TH. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB046 Pg007 Workaround: None. Do not name programs "T0" through "TH". 20. Problem: Superscript prints on a separate line for the PT-4210-B4, PT-4213-B4, PT-4217-B4 and PT-4218-B4 printers rather than slightly above the line. Workaround: None. 21. Problem: ESCAPE mnemonic 'ES' doesn't work on the PT-4215 printer. Workaround: None. 22. Problem: 27xx/37xx - Listing autoprompts, receive queues, transmit queues, signon definitions, etc. to a printer, will get a "***10 ERROR 20***" message, and BCOM will abort. Workaround: Perform a global search and replace, changing all occurrences of "ENDIF" with "FI" in the following programs in the /tbc/BCOM directory: BSIGN, BXQF0, BXQF2, BAPFN, BRQF. 23. Problem: DOS 'CHKDSK' command corrupts the DOS partition on a MAXTOR 1140 disk drive if the DOS partition is less than 100 cylinders. Workaround: Make your DOS partition larger than 100 cylinders. 24. Problem: An error 0 won't be returned under BASIC for a non-spooled non-B4 interface printer (This happens only when the printer is configured on the 8-way). The terminal will hang until the printer is put back online or until the user escapes out of the print job. This problem exists in 7.2R. Workarounds: a. Configure the non-B4 interface printer for spooling. b. Configure the non-B4 interface printer on the COMx port. c. Use a B4 interface printer if you choose to use a non-spooled printer. 25. Problem: Marketing Announcement #629 US/C (for the U.S. and Canada), and Marketing Announcement #404 I (for international locations) states that the Intersystem tape Transport Product (ITP) provides the facility on an MAI 1800 system to read and write format-compatible 1/4" MCS tapes. Actually, ITP only contains ATP and BQR facilities. The ITP product is available on the operating system base tape. EIT is the limited-support tool diskette that contains the tape transport tools (xcread, cwrite, clabel, creport). The EIT diskette and a 2 page document is available through the Regional Offices. ORIGINATOR: D. Wenzel SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB046 Pg008 FIB 00047 10/24/88 *** Ports above T9 won't work with auto dialer [ WPSF 449-13 ] *** There is a problem selecting a port to be used with the auto-dialer facility when it is above port number "T9". No error is given when the user selects a port above "T9" but the input is not accepted. To correct this problem the following changes should be made to the program "/tbc/BCOM/BMNU0": 2004 IF PRT9$(1,1)=" " OR LEN(PRT9$)> = 5 THEN GOTO 1996 This problem will be corrected in the next release. ORIGINATOR: D. Jensen SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB047 Pg001 FIB 00048 10/24/88 *** Err 20s in TBC Programs on 7.2R and below (1800s) [ WPSF 494-1 ] *** PROBLEM: Error 20's occur in 5 TBC programs on the 1800 on OS levels 7.2R and below. CAUSE: The 'ENDIF' directive in 7.2 BASIC has been changed to use the BB86 directive 'FI', but the TBC programs didn't contain this change. SOLUTION: Perform a Search and Replace (bsearch) on the following programs: BAPFN - 4030 BRQF - 2240, 2700 BSIGN - 2240, 2670 BXQFO - 7230 BXQF2 - 4730 Search for: 'ENDIF' Replace with: 'FI' FUTURE: This problem will be corrected in a future release of TBC on the 1800. ORIGINATOR: T. Tiangco SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB048 Pg001 FIB 00049 12/19/88 *** Release 7.4B Software Announcement [ WPSS 159 ] *** Level 7.4B of BOSS/IX is now available. It is the recommended Operating System for MAI 2000, MAI 3000 and MAI 4000 systems, and is the only Operating System for the MAI 2500 system. This Software Announcement contains general information about the Level 7.4B BOSS/IX Operating System. Installation and upgrade procedures are fully documented in this announcement. Also, this document has sections on enhancements and corrections to BOSS/IX, approximating memory requirements, memory usage, a list of new documents available for BOSS/IX, and a list of the lowest acceptable revision levels for hardware. WARNING: When installing this release on a 3000 system, the system serial number MUST be reinstalled using the new 2000/2500/ 3000/4000 SSN program. DO NOT attempt to upgrade a 3000 system without reinstalling the system serial number using the new 2000/2500/3000/4000 SSN program. WARNING: In order to install the systems properly, the 7.4B 2000 O.S. tape must be used to install a MAI 2000 system, and the 7.4B 3000/4000 O.S. tape must be used to install the MAI 2500, MAI 3000, and MAI 4000 systems. WARNING: With BB86, BASIC programs are not backwards compatible. You must use the conversion facilities to take the programs backwards to a 7.2 or prior release. It is recommended that you read this document before installing Level 7.4B. For information on how to order Level 7.4B refer to Marketing Announcement 644 for the United States or 413 for International. NOTE: Throughout this document the references to '7.2' include 7.2A/B/C/D/D1. Copyright 1988 MAI Basic Four, Inc. All rights reserved TABLE OF CONTENTS 1.0 OVERVIEW 2.0 INSTALLATION AND UPGRADE OF THE OPERATION SYSTEM, SOFTWARE AND DIAGNOSTICS 2.1 Installing Diagnostics on the Disk 2.1.1 Introduction 2.1.2 Disk Diagnostic Installation Procedure 2.1.3 Loading Disk Diagnostics 2.2 Installation of the Operating System 2.3 Upgrading SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB049 Pg001 2.4 Product Installation/Upgrade - GENERAL 2.4.1 ECC "C" Compiler 2.4.2 MAGNET (ENT) and File Transfer Facility (FTF) 2.4.3 27xx/37xx Batch Emulation 2.4.4 Asynchronous Transport Package (ATP) 2.4.5 3270 Bisynchronous 2.5 Product Installation/Upgrade - from 7.1 or 7.2 2.6 Security Configuration Record 2.6.1 7.4B Configuration Record Request Sheet 3.0 LEVEL 7.4B BOSS/IX ENHANCEMENTS 3.1 Operating System (EOS) 3.2 Utilities (EUT) 3.3 BASIC (EBS) 4.0 MEMORY REQUIREMENTS AND OPERATING PARAMETERS 4.1 Approximating a System's Memory Requirement 4.2 Recommended Values for "vconf" 4.2.1 Recommended Values for "vconf" BOSS/IX Model 2000 Parameters 4.2.2 Recommended Values for "vconf" BOSS/IX Model 2500, 3000 and 4000 Parameters 5.0 MEMORY USAGE 5.1 Calculating a System's Memory Requirement 5.1.1 Example of How to Calculate a System's Memory Requirement for Model 3000 5.2 Calculating BOSS/IX Table Space and Dynamic Work Space 6.0 NEW & UPDATED MANUALS FOR LEVEL 7.4B 7.0 HELPFUL HINTS 7.1 Four-way and Eight-way Configuration 7.2 Memory Configuration 7.3 Disk Configuration 1.0 OVERVIEW SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB049 Pg002 The level 7.4B Release contains the following enhancements/features: o MAI 2500 Support o Operating System Corrections - Memory compaction crash - Sttywrite crash - System stack overflow crash - 1/2 Inch tape error -92 - Offline printer losing data - NAK/ACK on 4213 printer - Two board disk controller with two disk system contention o BB86 --- Business BASIC 86 Corrections - Multi-key file corrections - Infinite 'Error in for/gosub stack' looping error - FPT function not rounding properly - VFU load being sent on open statements o Utility Corrections - frepair show multi-key files with composite fields as corrupted - fcopy changing record size to equal number of records - pparams suspending when the /etc/passwd file has more than 256 bytes 2.0 INSTALLATION AND UPGRADE OF THE OPERATING SYSTEM, SOFTWARE AND DIAGNOSTICS The following are the steps to install or upgrade the Operating System, customer's software and system diagnostics. Before installing or upgrading the system it is recommended that you read these instructions completely. NOTE: To do an ALTERNATE LOAD: On a 2000 system, enter ^C at the reboot prompt. On a 2500/3000/4000 system, enter 2 at the bootstrap menu. 2.1 Installing Diagnostics on the Disk 2.1.1 Introduction Diagnostic programs for your system may be contained on the system fixed disk. Your disk should have diagnostics installed in order to test the tape subsystem included with your system. The purpose of these tape diagnostics is to troubleshoot and test your tape subsystem, when you cannot load diagnostics from the tape subsystem. You may optionally install all of the diagnostics programs on your disk. The system diagnostics are contained on a dedicated diagnostic partition. This diagnostic partition is inaccessible to user programs, and is actually beyond the reach of the user disk area. For this reason, the diagnostic programs cannot be accessed by the file system, yet they are maintained by a Diagnostic SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB049 Pg003 Executive. If your system will not boot diagnostics from disk, and the O.S. is already installed, the file system must first be backed up. Once backed up, a diagnostic partition can be reserved. Once the diagnostic partition is reserved, diagnostics can be installed from the same bootable diagnostic tape. Afterwards the file system must be restored. Use the following procedure to install the diagnostics on your fixed disk. 2.1.2 Disk diagnostic installation procedure Step 1: Backup your disk If your file system is already installed on the disk you must do a complete file by file backup. If your file system has not been installed yet, install your diagnostics first and then install the file system. Step 2: Boot diagnostics from tape Install the diagnostic tape. Do an alternate load. For the boot device enter "cs", for MCS or 'ts', for MTS. For the system file enter . Step 3: Enable service mode When the EXEC is loaded, it will auto-size the system and display the program prompt: Any Exec commands can be entered at this time. To begin the installation of diagnostics, you must first enable the service commands. At the Exec prompt, enter: service and a RETURN. This will allow use of the service commands. Exec will then ask for the service password, enter: b4bus and a RETURN after which, the prompt will again be displayed. Step 4: Update the superblock on the disk. The superblock on the disk must be updated to reserve a section of the disk for the diagnostics. Enter the superblock initialization command: sbinit and a RETURN to initialize the superblock for the diagnostic partition. EXEC will ask you if you want to destroy the existing disk partition information and the disk directory name. Any (y/n) responses are single character responses, and do NOT require a . SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB049 Pg004 Entry of the "sbinit" command will cause EXEC to ask: Destroy: "volume ID" (y/n)? where "volume ID" is the current volume ID contained in the superblock. A "y" response will allow you to initialize the superblock for the diagnostic partition. A "n", no response will return you to the prompt. Enter: y and EXEC will ask for the number of sectors to reserve on the disk for the diagnostics: Diagnostic Partition size (in sectors)? Enter the number of sectors desired as follows: a) To install all available diagnostics, enter: 2000 b) To install tape diagnostics, enter: 200 EXEC will then ask about the directory: Destroy: "partition name" (y/n)? Enter the character "y" to destroy the current disk directory to have it initialized for a subsequent install, or "n" to retain the current partition name. If you wish to change the name of the disk diagnostic partition, enter: y and EXEC will then ask: Disk name: Enter the new disk name, up to 12 characters in length, and . This new name will be displayed every time you display the directory. EXEC will then display: Initializing: "disk name" where "disk name" is the new name you just entered. The diagnostic partition is now defined. Step 5: Copy diagnostics from tape to disk Once the diagnostic partition is defined, diagnostics can be installed on the disk. You now can determine which files to install on the disk by listing the SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB049 Pg005 contents of the tape. This is optional if you are going to install all of the diagnostics. To obtain a list of file names on the tape, enter: ltape To install the diagnostics on the fixed disk, enter: install and a RETURN to install ALL of the diagnostics. To install a particular diagnostic enter: install "file" and a RETURN where "file" is the file name to install on the disk. Use the list of files obtained by the "ltape" command to determine which files you want to install. The file EXEC, SIT, MCS and/or MTS are the minimum diagnostic files to install. When you enter the "install" command, to install all of the diagnostics, EXEC will prompt: Destroy: "disk name" (y/n)? where "disk name" is the name of the disk entered during the "sbinit" command sequence. Entry of the character "n" will cause the current directory name to remain and the install process to begin. Entry of a "y" character will cause EXEC to ask you for the new disk name as in the "sbinit" command. Maintain the current directory from the "sbinit" sequence, enter: n and the install procedure will begin. As the diagnostics are installed on the disk, EXEC will display the current program being copied from the tape, and the size in sectors. After the sector size display, the file is written to the disk and the directory updated. When all the files are installed, EXEC will again display the prompt: Step 6: After the diagnostics are installed on the disk, you may want to list the diagnostics on the disk enter: ldisk and to obtain the list of the diagnostic files on disk. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB049 Pg006 You should test the bootstrap capability now, to see that you can boot diagnostics from the disk. Enter: shut and to obtain the bootstrap menu. Step 7a: 2500, 3000 and 4000 only Do an alternate load, for the boot device enter: wd0, for system file enter: diag Step 7b: 2000 only (2500's boot just like 3000's) The EOS product must be installed to boot to the diagnostic partition on the 2000 system. The file /sys/diag exists on the EOS product. This file is required to boot to the diagnostic partition. After you have installed the EOS product: Do an alternate load, for the boot device enter: wd0, for the system file enter: /sys/diag. NOTE: Installing diagnostics on the disk has taken disk space away from the user available disk space, the device capacity is reduced to provide room for the diagnostics. 2.1.3 Loading Disk Diagnostics When the system is first powered up, or after the system is shutdown, the user must perform an alternate load sequence in order to load diagnostics from disk. The system has the logic to either bootstrap the Operating System or the Diagnostic Executive. The loader programs for each are in different sections of the disk. The diagnostic loader and the associated directory of files for the diagnostics are contained in the diagnostic partition. Thus the diagnostic partition is completely self contained, and separate from the Operating System. The operation of loading diagnostics from the fixed disk and from the MCS/MTS tape are similar. The only difference is in the alternate load sequence, as discussed in the following sections. The diagnostics contained on your fixed disk cannot be run while the Operating System is up and running. The diagnostic programs are all off-line programs and require you to first shutdown your system, regardless if you load from MCS/MTS tape or from the fixed disk. After running diagnostics, entry of the diagnostic "shutdown" command will allow you to reload the Operating System. The normal indication that diagnostics are not on the disk, is the error message "invalid loader detected" when a diagnostic boot is attempted. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB049 Pg007 To access the diagnostics, once they are installed perform an alternate load. For boot device enter 'wd0', for system file enter 'diag' for the 2500/3000/4000 system or '/sys/diag' for the 2000 system. This will get the '' prompt. Any file name listed by the 'ldisk' command can now be loaded by entry of the command: load "file" and , where "file" is any file listed. 2.2 Installation of the Operating System The following steps outline the 7.4B BOSS/IX installation procedures for tape and floppy diskette. The "installation" procedure is to be used when installing a new system, or installing the OS after a diagnostic partition has been installed. NOTE: The 'packaging' of the products has changed. A 'base' tape will no longer be distributed. Instead, you will receive a 'customer' tape. These products are on the 'customer' tape: EOS EUT EBS EXT EBA EDB IDB TBC EIT ENT FTF INT CBR CBD UPD PDF B32 X25 EB2 With this new packaging it is no longer necessary to ship a tape for each product ordered. Instead, a Lock & Key certificate is generated and mailed for each product purchased. WARNING: When installing this release on a 3000 system, the system serial number MUST be reinstalled using the new 2000/3000/4000 SSN program. DO NOT attempt to upgrade a 3000 system without reinstalling the system serial number using the new 2000/3000/4000 SSN program. Step 1: Using the mcssave/mtssave (7.1 & 7.2) or tsave (7.3A & 7.4A) command or the floppy diskette save utility, do a file by file back up of all user programs and data files. Using the configure utility, print out the port configurations; using the oprinfo utility, print out the operator information report. These will need to be re-entered after the install is complete. Step 2: First step is to install the boot partition. Place the customer tape into the tape drive. Or, if you are doing floppy installation insert the installation floppy into drive fd0. NOTE: The 7.4B 2000 O.S. tape must be used to install the SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB049 Pg008 MAI 2000, and the 7.4B 3000/4000 tape must be used to install the MAI 2500, MAI 3000, and MAI 4000. Do an alternate load. At the 'boot device:' prompt type "cs" for MCS, "ts" for MTS, or "fd0" for floppy diskette, then press . Press again at 'System file:' prompt. NOTE: MTS requires a 4.2 boot prom on the MAI 2000. Step 3: Screen displays loading messages, then the 'Install Utility Menu'. Select Option 'A', then . Option 'A' re-defines all the wd0 partitions and copies a new boot partition to disk. Special note for floppy diskette installations, make sure your BOOT floppy diskettes are inserted in the correct sequence according to the BOOT number. After one floppy diskette is complete make sure you change floppy diskettes before responding to the prompt on the screen. Step 4: After the boot partition is installed the configuration record must be installed. When the message 'OPTION>' is re-displayed put the configure record tape or floppy in the tape drive or floppy drive. Use option 'D' to install the configuration record. After the configuration record is installed enter ' ^D' and then 'shutdown'. Step 5: After the configuration record, the EOS product must be installed. Rebooting the system at this time automatically roots to the boot partition. Enter the correct date; the screen will then display the 'ADMIN>' prompt, type "osinstall cs" for MCS tape, "osinstall ts" for MTS tape, and "osinstall fd0" for floppy diskette. This process uses the parameters in the Super Block to define the root filesystem, then copies the EOS product to the root partition on disk. After the EOS product is installed you are instructed to reboot again. WARNING: If the 7.4B configuration record for the system is not installed you will be able to access the boot partition only. NOTE: It is recommended that the configuration record be copied to the boot partition. To do this execute the following with the configuration tape in the tape drive before rebooting: 'trestore dev= -v name=CONFIG' where dev=cs for MCS and dev=ts for MTS. For floppies: SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB049 Pg009 'mount /dev/fd0 /mnt' 'copy /mnt/config.* /sys' 'unmount /mnt' Step 6: Reloading of the system at this time automatically reloads and roots to the root partition. Enter either the current date, or a , if the date is correct. At the 'ADMIN>' prompt, type "install cs EUT EBS EXT", for MCS tape, "install ts EUT EBS EXT" for MTS tape or "install fd0 EUT", for floppy diskette. NOTE: When working with tapes all products listed on the customer tape can be installed with one command line. When working with floppies you must install one product at a time in the following order: EUT, EBS, EXT, EBA then optional products in any order. Products that are chargeable and not part of the base system will have key codes that you must enter during or after (using '/bin/install key') installation before you can use that product. If the key certificate did not come with the media, contact the customer or service representative in your area for instruction about how to obtain this key code. Step 7: The '/etc/conf' file on the boot partition needs to be customized to meet your needs. The '/util/sconf' utility, located in the EXT product, enables you to redefine your '/etc/conf' file. (See Section 5.0 'Memory Usage' for instruction on how to customize the '/etc/conf' file.) Step 8: After you have copied all your products to disk and have customized the '/etc/conf' file, your system is ready for use. Step 9: If you have user program and/or data files to be restored, use the 'dups=skip' option of the trestore command or the 'skip' option in the 'duplicates' parameter of the trestore or drestore utility to avoid writing "old" files over your new 7.4B files. If you are restoring 7.1 BASIC programs, use the csave command to convert them to 7.4B BASIC. 2.3 Upgrading The following steps describe the 7.4B BOSS/IX upgrade procedures for tape and floppy diskette. NOTE: This upgrade procedure is for 7.2/7.3A/7.4A only. If you are upgrading a 7.1 OS level system refer to section 2.2 "INSTALLATION OF THE OPERATING SYSTEM". WARNING: When installing this release on a 3000 system, the system serial number MUST be reinstalled using the new 2000/3000/4000 SSN program. DO NOT attempt to upgrade SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB049 Pg010 a 3000 system without reinstalling the system serial number using the new 2000/3000/4000 SSN program. Step 1: Using the mcssave/mtssave command or the floppy diskette save utility, do a file by file back up of all user program and data files. Using the configure utility, print out the port configurations; and, using the oprinfo utility, to print out the operator information report. When upgrading from 7.3A/7.4A to 7.4B it is recommended to skip to Step 5 at this point, except if your media is floppy diskette. Step 2: Root the system to the Boot Media. Insert the customer tape into the tape drive, or if you are doing floppy installation insert the Boot floppy into drive fd0. NOTE: The floppy diskette requires booting from media. Do an alternate load. At the 'boot device:' prompt type "cs" for MCS, "ts" for MTS or, "fd0" for floppy diskette, then press . Press again at 'System file:' prompt. Step 3: When upgrading from 7.3A or 7.4A to 7.4B it is recommended to skip to Step 4 at this point, except if your media is floppy diskette. Screen displays loading messages, then the Install Utility Menu. When upgrading from 7.2, or using floppy diskettes, select Option 'B', then . Option 'B' will only copy an image on the boot partition from the tape or floppy to disk. This process will ensure that your system has all the up-to-date and proper MACROs and system files on the boot partition. NOTE: For floppy diskette installations, make sure your BOOT floppy diskettes are inserted in the correct sequence according to the BOOT number. After one floppy diskette is complete make sure you change floppy diskettes before responding to the prompt on the screen. Step 4: After the boot partition is installed the configuration record must be installed. When the message 'OPTION>' is re-displayed put the configuration record tape or floppy in the tape drive or floppy drive. Use option 'D' to install the configuration record. After the configuration record is installed enter '^D' and then 'shutdown'. WARNING: If the 7.4B configuration record for the system is not installed, you will be able to access the boot partition only. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB049 Pg011 Step 5: Do an alternate load. At 'Boot device:' prompt, ''. At the 'System File:' prompt, enter ",/etc/boot.conf". Step 6: The above alternate load will re-load and root the operating system to the boot partition. Enter the correct date or '' if the date is correct. Insert the base system tape containing EOS, EUT, EBS or the floppy diskette EOS #1. At the 'ADMIN>' prompt type "osupdate cs" for MCS tape, "osupdate ts" for MTS tape, or "osupdate fd0" for floppy diskette. NOTE: For floppy diskette upgrades the screen will prompt you when to insert the next diskettes. Step 7a: After the procedure is complete you have the option of restoring the default system configuration files to the upgraded root then to the boot partition. This is done by typing "/sys/installetc". This procedure allows the operator to select which system files he/she needs to restore. Please note that if this is done, all system files that are restored will be new and will have to be re-updated to reflect the needed system information. Example: If an 'osupdate' was performed, and '/etc/passwd' is re-installed the operators will have to be redefined. Following, find a list of the files that can be installed using 'etc/installetc' and the means to modify the files for your system: /etc/class, /etc/defaults, /etc/forms: These files are used when printing and can be customized by going to the 'ut.printer' menu and using option 5 'Printer parameters' or using the program 'pparams'. /etc/conf: This file contains your system configuration parameters and is changed by using the '/bin/vconf' command. /etc/exem, /etc/logm, /etc/motd: These files print to the screen at the time of log in and can be modified by the use of the '/bin/ved' command. /etc/passwd: This file contains your operator information and is updated by going to the 'ut.system' menu and using Option 3, (Operator information) or by using the program 'oprinfo'. /etc/ports, /etc/printers, /etc/terminals: SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB049 Pg012 These files contain the terminal and printer configuration parameters and are updated by going to the 'ut.system' menu and using Option 1, (Port configuration) or by using the program 'configure'. /etc/sinit, /etc/startup: These files are used at system load time and can be modified by the use of the '/bin/ved' command. /etc/shtdwn: This file is used when the system is being shutdown and can be modified by the use of the '/bin/ved' command. Step 7b: If you are upgrading from 7.3A/7.4A and you skipped from step 1 to 5 you must install the config record. To do this execute the following commands with the configuration tape in the drive. ADMIN> trestore d=/dev/cs or /dev/ts -v n=CONFIG ADMIN> iconf -new -save Step 8: Next shutdown the system and do a normal boot of the system. Enter the correct date or press '' if the date is correct. If you are upgrading from MCS, at the 'ADMIN>' prompt type "install cs EUT EBS EXT", press ''. If you are upgrading from MTS, at the 'ADMIN>' prompt type "install ts EUT EBS EXT", press ''. The system will automatically install EUT, EBS and EXT. If you are upgrading from floppy diskette, insert the first floppy of the EUT set. At the 'ADMIN>' prompt type "install fd0 EUT". Once EUT is complete use the same routine to install EBS, EXT, and any other products. NOTE: The 'EXT' product must be installed in order to run the 'sconf' utility. The 'sconf' utility is used to set-up the configuration parameters for a system. NOTE: When working with tapes all products listed on the customer tape can be installed with one command line. Products that are chargeable and not part of the base system will have key codes that you must enter during or after (using '/bin/install_key') installation before you can use that product. If the key certificate did not come with the media, contact the service representative in your area to instruct you in where to call for this key code. Step 9: If you are upgrading from 7.2, it is time to verify your port configuration, using the 'configure' utility, and to set-up your configuration parameters, using the 'sconf' utility. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB049 Pg013 To verify your port configuration, run the 'configure' utility to check the current port set-up. As a part of this verification, the printer and terminal model numbers should be accurate for the device in use. Step 10: There have been some changes in some of the system files between 7.1, 7.2 and 7.4B. For this reason you are required to make some configuration changes to the system. These changes are identified in the following two sections. One section covers general changes, the other covers changes specific to 7.1/7.2 upgrades to 7.4B. If you are not installing a particular product you need not worry about the configuration changes for that product. If you are installing a product then you must follow the section that covers that product. Once the upgrade has been performed, be especially careful when restoring files back down from a 7.2 tape. If you should accidentally restore a changed configuration file it is best to go back and install that product again from the system tape, being careful to follow the configuration change steps for that product. Step 11: If you have user program and/or data files to be restored, use the 'dups=skip' option of the trestore command or the 'skip' option of the 'duplicates' parameter of the trestore or drestore utility to avoid writing "old" files over your new 7.4B files. NOTE: Restoring customer files on an update procedure should not be required. The procedure should leave all user files intact. 2.4 Product Installation/Upgrade - GENERAL 2.4.1 ECC 'C' Compiler 1. Due to changes to the header files and new shared libraries in 7.4A AND 7.4B, all 'C' programs compiled previous to 7.4A, should be recompiled on 7.4B to avoid problems executing these programs. 2.4.2 MAGNET (ENT) and File Transfer Facility (FTF) 1. To install ENT, execute the command: admin> install xx ENT 2. To install FTF, execute the command: admin> install xx FTF where xx is the device of the ENT or FTF media. cs = 1/4" MCS ts = 1/2" MTS fd0 = floppy drive 3. ENT and FTF use CMB port 1 when X.25 is installed. This port must be strapped as "modem". The SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB049 Pg014 maximum baud rate supported by X.25 on 7.4B is 4800 baud. 2.4.3 27xx/37xx Batch Emulation 1. The 27xx/37xx Batch Emulation package is written in BASIC since 7.3A and is called TBC (Trans- portable Batch Communications). The C version of 27xx/37xx Batch Emulation (EBC) is no longer available on the 2500/3000 systems. TBC on 7.4B is compatible to TBC on MPx and 13xx systems, as well as 2500/3000 systems running EBC, since the line protocol has not changed. 2. To install TBC, execute the command: admin> install xx TBC where xx is the device of the TBC media cs = 1/4" MCS ts = 1/2" MTS fd0 = floppy drive 3. Conversion of the transmit queue, receive queue, and autoprompt files is automatically performed when installing TBC on a system previously using the EBC product. The public key for TBC is compatible with the EBC public key. 4. There are no operational changes between TBC and EBC when running BCOM from the Communications menu. However, since the 7.4B version of BCOM is written in BASIC, there are changes in accessing BCOM from command mode: user prompt>basic s=128 pgm=/tbc/BCOM/BCOM 5. TBC on 7.4B supports autodial features which allow BCOM to interface to an automatic calling unit (ACU) to dial the number stored in the BCOM autoprompt file. Two utilities, ACUTD and ACS, have been added to TBC: ACUTD - utility to build scheduler lists of BCOM autoprompts which are designated to be activated at specified date and times. ACUTD can be accessed from the communications menu or alternately from command/console mode. user prompt>basic s=128 pgm=/tbc/BCOM/ACUTD ACS - program which activates the scheduler lists specified in ACUTD. ACS can be accessed from the communications menu or alternately from command/console mode. user prompt>basic s=128 pgm=/tbc/BCOM/ACS 6. The 7.4B automatic calling features of TBC have SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB049 Pg015 been certified with the following ACU's and modems: o Universal Data Systems 801C ACU with Universal Data Systems 201C synchronous modem - This combination requires a serial asynchronous port be configured as a terminal (EVDT with default parameters) for the 801C ACU and CMB port 1 configured for the synchronous communications port. The UDS 201C is compatible to other vendor's BELL 201C compatible units. o Paradyne FDX 2400 PLUS ACU/modem - This unit also requires a serial port be configured as a terminal (EVDT with default parameters) for the ACU interface and CMB port 1 configured for synchronous communications. This unit is compatible with another Paradyne FDX 2400 Plus, a Bell 212A synchronous modem, and a Universal Data Systems 224 synchronous modem. 8. TBC uses CMB port 1. This port must be strapped as "modem". The maximum baud rate for TBC is 4800 Baud. 9. Details on TBC and modem/ACU strappings are documented in the BOSS/IX Transportable Batch Communications (27xx/37xx) User Guide - M6353C. 2.4.4 Asynchronous Transport Package (ATP) 1. ATP (4.0) is included with the 7.4B EIT product. ATP 4.0 contains protocol changes for performance enhancements which makes it incompatible with previous releases of ATP. All systems using ATP to communicate to a 7.4B system must also have ATP 4.0 on their systems. 2. In addition to performance enhancements, ATP 4.0 provides the following features: o Line Turnaround - allows transmit and receive functions in a single session o Autodial - supports automatic dialing of Hayes/compatible and UDS 224 A/D modems o Scheduler - provides unattended startup of ATP sessions 3. To install ATP 4.0, the EIT product must be installed: admin> install xx EIT where xx selects the device of the install media cs = 1/4" MCS ts = 1/2" MTS fd0 = floppy drive 4. To activate the features of Line Turnaround, SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB049 Pg016 Autodial, and the Scheduler, a public key must be installed: admin> install_key /etc/level/ATP 5. As with previous levels, BQR must be run to generate an ATP filelist. Note, however, that schema files are no longer supported by BQR for any transport media - transmitted files must either be in TEXT or BINARY format. After BQR filelists are created, RUN "ATP" to set the communications parameters for the session. The parameters may be saved in an autoprompt for future use or use with the Autodial and Scheduler features. RUN "ATPTIM" to set the Scheduler parameters. RUN "ATPSCH" to begin the ATP sessions according to the parameters set in the Scheduler. 6. Automatic file conversion and translation occur during the file transfer. BQR will no longer be required to convert files received via ATP 4.0 from unlike systems. 7. Refer to the ATP 4.0 Software Announcement #150 and the Intersystem Transport Package User Guide (M6354D) for details. 2.4.5 3270 Bisynchronous 1. To install the 3270 Bisynchronous product, execute the command: admin> install xx B32 where xx selects the device of the install media cs = 1/4" MCS ts = 1/2" MTS fd0 = floppy drive 2. B32 uses CMB port 1. This port must be strapped as "modem". The maximum baud rate supported by B32 is 4800 Baud. 3. As with previous releases of B32, the DT-4310 is the only terminal which is supported to emulate an IBM 3278 display terminal. 2.5 Product Installation/Upgrade - From 7.1/7.2 1. The 7.4B user is responsible for configuring the type of system console terminal after the install procedure is complete. This step cannot be done until the operating system and the utilities product, EUT, have been installed. Then the user should execute the Port Configuration Utility "configure" and set the system console type. The SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB049 Pg017 system console type set by the boot PROM configurator is no longer supported by the operating system as of 7.3A. Other system console parameters must still be set through the boot PROM configurator. 2. Partition files created with 7.2 "/bin/usb", which reside in the "/etc/diskdesc", cannot be used on 7.4B. These files can be recreated using the 7.4B "usb" command. 3. On upgrades from 7.1 to 7.4B the user MUST boot off the customer tape and select the "A" option before doing an "osinstall" from the boot. 4. All upgrades to 7.4B will create a new boot partition filesystem, thereby destroying all 7.2 files on the boot partition. 5. The MAGNET/FTF configuration files have changed format between 7.2 and 7.4B. Existing LEGAL network config- urations will be converted to the new format by a program which is automatically executed at installation of the 7.4B ENT or FTF product. Configurations which do not conform to documented restrictions (e.g., two LAN boards) may not successfully convert. Though the installation procedure allows the installer to omit calling the configuration conversion program, it is safe to run the conversion program. 2.6 Security Configuration Record When installing 7.4B on your system or if you are upgrading/adding to the system's hardware, you must also install/upgrade to a 7.4B security configuration record. See step #4 of section 2.2 Installation of the Operating System for instruction. 2.6.1 7.4B Configuration Record Request Sheet On the following page you will find a copy of the 7.4B Configuration Record request sheet. 3.0 LEVEL 7.4 BOSS/IX ENHANCEMENTS AND CORRECTIONS 3.1 Operating System (EOS) o Support for the MAI 2500 o NAK handling on the Whisper printer. o Memory compaction crash correction o Sttywrite crash correction o System stack overflow crash correction o 1/2 Inch tape error -92 correction o Offline printer losing data has been corrected o Two board controller/2 disk system bus contention SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB049 Pg018 3.2 Utilities (EUT) o fcopy changing record size to equal number of records correction o pparams suspending when the /etc/passwd file has more than 256 bytes, correction 3.3 BASIC (EBS) o Multi-key file corrections - Multi-key file writes not advancing record pointer has been corrected - Multi-key file REMOVE reseting to the primary key has been corrected - Loss of Multi-key files variable length fields has been corrected - Multi-key files not supporting IOLIST's has been corrected o Infinite 'Error in for/gosub stack' looping error has been corrected o FPT function not rounding properly has been corrected o VFU load being sent on open statements has been corrected. 4.0 MEMORY REQUIREMENTS AND OPERATING PARAMETERS 4.1 Approximating a System's Memory Requirement This section describes how to approximate the amount of memory a system needs. Tables 4A and 4B show some standard system configurations which can be used to approximate the amount of memory a system needs. The number of users (terminals), ghost tasks, and printers differ for each of these standard config- urations. First, find the standard configuration that most closely matches the system in question, by scanning down the user/terminals, ghost-task, and printers columns. Second, scan across the table to the memory-needed column -- this is the system's memory requirements. NOTE: These tables (4A and 4B) assume that the system in question will be executing 60% BASIC and BASIC application programs, and 40% non-BASIC applications. If the system will be executing a higher percentage of non-BASIC programs, it will need more memory. Memory Requirements Memory requirements for each system will vary depending on the specific software application. "Data Processing Type Users" shows the maximum number of users recommended. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB049 Pg019 MAI 2000 o Data Processing Type Users: Memory: 768KB 1024KB 1280KB 1536KB Max Users: 1 2-4 5-8 9-11 MAI 2500 o Data Processing Type Users: Memory: 1MB 2MB 3MB 4MB Max Users: 3 12 14 14 MAI 3000 o Data Processing Type User: Memory: 1MB 2MB 3MB 4MB 5MB 6MB 8MB 10MB Max Users: 3 12 16 18 23 27 30 31 MAI 4000 o Data Processing Type Users: Memory: 8MB 10MB 12MB 14MB 16MB Max Users: 30 31 33 36 38 NOTE: Users refer to Terminals, Ghosts, and Serial Printers. 4.2 Recommended Values for "vconf" The following tables (Table 4A, 4B) show the recommended values for the BOSS/IX "vconf" parameters. 4.2.1 Recommended Values for "vconf" BOSS/IX Model 2000 Parameters __________________________________________________________________________ | | | | | | | | SYSTEM | base | add | add | add | maximum | | DESCRIPTION | system: | for | for | for | recom- | | -----> | | each | each | each | mended | | | 2 user | extra | ghost | extra | system | | | 1 printer | user | task | printer | config- | | "vconf" | | no ghosts | (above 2) | | (above 1) | uration | | BOSS/IX | | | | | | (See | |_PARAMETERS | | | | | Note 2)_| | | | | | | | |buffers= | 20 | 4 | | | 64 | |printers= | 1 | | | 1 | 14 | |procs= | 14 | 2 | 1 | 1 | 80 | |tsegs= | 12 | 2 | | | 64 | |locks= | 35 | 5 | 5 | | 160 | |ibsize= | 128 | 1 | | | 2048 | |tbsize= | 64 | 1 | | | 512 | |mfsys= | 3 | | | | * | |lus= | 65 | 15 | 15 | 6 | 254 | |fds= | 60 | 12 | 12 | 2 | 206 | |eventcalls= | 16 | 2 | 0 | | 152 | |dirc= | 16 | 5 | 2 | 2 | 206 | |ghosts= | 0 | as needed | | | 99_| | | | * Allow one mountable filesystem slot ("mfsys") for each | | mountable disk partition. The default of three allows | | for a boot partition, a root filesystem partition, and | SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB049 Pg020 | a diskette filesystem or 2nd drive. | |_ _| NOTE 1: The BOSS/IX configuration parameters required for other products are described in their documentation. Specifically, the LAN and 27xx/37xx communications products will require changes to the system parameters. For example, Magnet operating systems require 5 eventcalls per user. NOTE 2: These recommended values are not system limits but provide a guideline to tailoring the system. NOTE 3: vconf numbers for specific applications have been distributed by Field Product Support. The 7.4A values shall apply to 7.4B. TABLE 4A Recommended Values for Model 2000 Operating Parameters 4.2.2 Recommended Values for "vconf" BOSS/IX Model 3000 and 4000 Parameters ____________________________________________________________________________ . .| | | | | | | | | SYSTEM |base |add |add |add for |maximum |maximum | | DESCRIPTION |system: |for |for |each |recom- |recom- | | -----> | |each |each |extra |mended |mended | | |2 user |user |ghost |printer |system |system | | |1 printer |(above 2) | | |values |values | | "vconf" | | | | | |for the |for the | | BOSS/IX | | | | | |MAI 3000 |MAI 4000 | |_PARAMETERS | | | | |(Note 1) |(Note 4)_| .| | | | | | | | |buffers= | 128 | 32 | 0 | |(Note 2) |(Note 2) | |printers= | 1 | | | 1 | 34 | 76 | |procs= | 14 | 3 | 1 | 1 | 223 | 358 | |tsegs= | 12 | 2 | | | 148 | 290 | |locks= | 35 | 5 | 5 | | 284 | 684 | |ibsize= | 128 | 1 | | | | | .|tbsize= | 64 | 1 | | | | | |mfsys= | 3 | | | |(Note 3) |(Note 3) | |lus= | 65 | 15 | 12 | 10 | 1030 | 2630 | |fds= | 60 | 12 | 8 | 2 | 434 | 1054 | |eventcalls= | 16 | 2 | 0 | | 234 | 314 | |dirc= | 64 | 8 | 0 | 0 | 512 | 1058 | |ghosts= | 0 |as needed | | | 99 | 99_| NOTE 1: Values in this column reflect 34 user totals calculated from recommended increments, except for buffers. NOTE 2: Only memory availability limits buffers. NOTE 3: Allow one mountable file system for each mountable disk partition. A default of 3 allows for a root, boot and 1 other partition. NOTE 4: Values in this column reflect 74 user totals calculated from recommended increments, except for buffers. NOTE 5: vconf numbers for specific applications have been distributed by Field Product Support. The 7.4A values still apply to 7.4B. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB049 Pg021 TABLE 4B Recommended Values for Model 2500, 3000 and 4000 Operating Parameters 5.0 MEMORY USAGE This section describes how to determine the memory requirements for any MAI 2000, MAI 2500, MAI 3000, and MAI 4000 system. All BOSS/IX systems have different memory requirements. A system's memory requirement is based on its hardware configuration and software load. Specifically, the number of peripheral devices (i.e. terminals and printers) and software packages (such as BASIC, BASIC applications, utilities, etc.) determine a system's memory needs. This section explains two methods used to determine the amount of memory needed for a system. The first method approximates a systems memory requirements -- and can be used if the system closely fits one of the standard system configurations. The second method calculates the memory requirements for best system performance -- and is used for non-standard system configurations. 5.1 Calculating a System's Memory Requirements This section describes how to calculate the number of memory boards a system requires for adequate performance. The calculations are based on the system's hardware configuration and software load. Software load is defined to be the number and types of processes running on the system. This section steps through an example based on a system consisting of 16 users for the 3000. The same steps and overhead numbers apply for the Model 2500 and 4000. (See section 5.1.1). STEP 1: First, add the space required for the operating system, table space, and dynamic space required for the base configuration. NOTE: 1 KB = 1024 bytes 220 KB This is the memory requirement for the base BOSS/IX operating system program. This includes space for the system's interrupt vectors, and operating systems text (code) and data segments. 34 KB** This is the memory requirement for BOSS/IX table space for the base configuration: (2) users (terminals), (1) printer, and (0) ghost tasks. NOTE: Additional table space must be added for each additional resource above that in the base configuration (see step 2). NOTE: this excludes the memory required for hash tables for buffers and directory entries. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB049 Pg022 36.6 KB** This is the memory requirement for the operating system's dynamic work space (or unswappable memory) for the base configuration. STEP 2: Next, add in table space needed for resources beyond the ones described in the base configuration. (If the system will be configured like the base configuration skip this step). NOTE: The MAI 3000 is a table driven system. For maximum performance extra memory must be allocated for resources beyond the ones described in the base configuration. 10.2 KB** This is the memory needed as table space for each additional user above the two that are allocated in the base systems. 5.0 KB** This is the memory needed as table space for each ghost task in the system. 3.2 KB** This is the memory needed as table space for each additional printer above the one that is included in the base system. 4.8 KB** This is the memory needed for dynamic work space for each additional process (i.e. "proc") above the 16 that are included in the base system. (Refer to Section 5.2) ** Memory required for BOSS/IX table space and dynamic work space. These values are the memory allowances based on a system consisting of 16 users for the 3000. If the system parameters are set differently, use section 5.2 and Table 5B to calculate the memory required for O.S. table and O.S. dynamic work space. STEP 3: Add the space need for system processes for the base system configuration. 106 KB This is the memory allowance for system tasks. System tasks for the base system include: a printer despooler process and two command interpreters. The total memory required to have all system processes in memory at the same time is approximately 2500 KB. However, 106 KB should be used in this calculation because system processes wait on system events and it is not likely that all system processes will want to execute at the same time. Furthermore, these processes, when waiting for events, can be swapped to secondary storage, which will have little effect on system performance. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB049 Pg023 NOTE: There is a one time additional allocation of 83KB for shared libraries. STEP 4: Add the space needed for any additional system processes beyond the ones specified in the base configuration. (If the system will be configured like the base configuration skip this step). 33 KB This is the memory needed for each additional printer despooler, above the one that is allocated in the base configuration. This is a memory allowance for the data and stack segments for an additional despooler task. An allowance for test (code) space is not necessary, because two despooler tasks will share the same code segments. NOTE: A one time shared library allocation of 8KB should be added for the despooler. 11 KB This is the memory required for each user (terminal) that will be executing tasks concurrently. This is the memory allowance for each additional command interpreter. It is space needed for the interpreter's data and stack segments. NOTE: A one time shared library allocation of 8KB should be added for concurrent users. NOTE: memory allowance for text (code) space is not necessary because multiple command interpreters share the same code segments. STEP 5: Next, add the space needed for applications processes. 160 KB This is space needed for each unique, non-BASIC task that will be executed concurrently on your system. Such tasks include the BASIC interpreter, utility programs, LAN, Informix, communications, BOSS/IX command interpreter, etc. NOTE: only one BASIC interpreter is needed to support any number of BASIC programs. This value is a rough estimate, for all processes require different amounts of memory, some more some less. When computing the memory required for SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB049 Pg024 application tasks, consider how often each application is used. For example, if the system seldom executes BOSS/IX commands or the utilities, only a percentage of the total space needed to execute these processes will be required. However, when the system is loaded, and these processes are executed, system response time may increase due to excessive amounts of swapping. 60 KB This is the memory required for each BASIC program. This space is the allowance for the data and stack segments for each BASIC program. NOTE: all BASIC programs share the same text (code) segment. Furthermore, this value is not exact, for some applications may require more memory and some may require less memory. 64 KB This is the memory required for each ghost task that will be executed concurrently. This is the space needed for each ghost tasks' stack and data segments. Text space is not allocated because all ghost share the basic process text segment. The result of the sum of Steps 1 thru 5 is the system's "memory requirement". STEP 6: Determine the memory/performance trade-offs. The value calculated in Steps 1 thru 5 is the "memory required" for good system performance. However, this value is not exact and may be raised or lowered which will increase or decrease performance respectively. By lowering the memory required value, one can save the costs of an extra memory board, but at the expense of performance. In other words, systems will run with less memory than required, however, the system overhead for swapping will increase. Process swapping is the action which extends user space to a temporary storage region on disk (i.e. the swap partition) so that during periods of heavy main memory utilization, processes may be stored on disk to make room in memory for processes waiting to execute. The advantage of process swapping is that it extends user space to disk (secondary storage); however, it is not without disadvantages. Swapping requires system overhead to read/write processes to/from secondary storage. Furthermore, excessive amounts of swapping will increase system responsiveness (i.e. decrease performance). If the cost of memory is more important than user responsiveness, multiply the system's memory requirement (calculated in Steps 1 thru 5) by a value between 0.7 and 1.3. Multiplying the memory required value by 1.0 will cause normal amounts of swapping; multiplying it by 0.7 will cause processes to be swapped to/from memory more frequently. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB049 Pg025 Multiplying the "memory requirement" by some value greater than 1.0 will decrease the O.S. overhead for swapping. NOTE: do not run a system with less than 70% of the "memory required" value -- this will cause excessive amounts of swapping. The result of this calculation is your system's "memory need". STEP 7: Next compute the number of memory boards that the system needs. Dividing the "memory needed" value, calculated in Step 6, by 1024 KB (memory needed/1024KB). NOTE: 1024 KB is the amount of memory on a 1 MB board. If a fraction results, round off to the next highest whole number. The value calculated is the "number of boards needed". 5.1.1 Example of How to Calculate a System's Memory Requirement for Model 3000 This example shows how to compute the memory requirement for a system with 16 terminals, 4 ghosts and 4 printers. Thirteen of the terminals are dedicated to running BASIC applications: accounts receivable, accounts payable, payroll, and word processing. The remaining terminals are used to run utilites, commands, and the Informix database application. Some of the applications use ghost tasks to output reports to printers. STEP 1 thru STEP 5: Add these numbers to compute "memory required" 230 KB Base operating system 99 KB Table space for base system 53 KB O.S. dynamic work space for base system 2 KB Hash table space for directory cache entries (table 5C) 16 KB Hash table space for disk buffers (table 5C) 41 KBX14 Allowance for table space for 14 additional users (total of 16 users/terminals) 41 KB*4 Allowance for table space for 4 ghost tasks 2 KB*3 Allowance for table space for additional printers 1.7 KB*49 Allowance for dynamic work space for 14 additional users ("procs" - base "procs") 100 KB Allowance for system processes 30 KB*3 Allowance for concurrent printing to the 3 additional printers 160 KB*3 Allowance for the BASIC interpreter and for the Utilities/Commands/Informix 15 KB*3 Allowance for concurrent terminals 60 KB*13 Allowance for 13 concurrent BASIC SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB049 Pg026 applications 64 KB*4 Allowance for 4 ghost tasks TOTAL = 2979 KB = "memory required" STEP 6: Compute "memory needed" For adequate system performance with frequent swapping of applications tasks and a reduced number of disk buffers: "memory needed" = 2979 KB * 0.7 = 2085 KB or 2 memory boards For good system performance with very little swapping: "memory needed" - 2979 KB * 1.0 = 2979 KB or 3 memory boards For best system performance with much caching: "memory needed" = 2979 KB * 1.3 = 3872 KB or 4 memory boards The approximate method of determining a system's memory requirement (section 4.1 and Table 4C) shows that a system with 16 users (terminals), 4 printers, and 4 ghost tasks needs 3, Model 3000, 1MB memory boards. The calculation method, described in this section shows that such a system will have different performance characteristics depending on the number of boards (i.e. either 2, 3, or 4) the system has. 5.2 Calculating BOSS/IX Table Space and Dynamic Work Space This section describes how to calculate the size of the operating system dynamic work space needed by any configuration on the MAI 2500, MAI 3000, and the MAI 4000. Table 5B shows the amount of memory allocated for each operating system configuration parameter; it shows the parameters for the base system configuration; for the MAI 2500, 3000, 4000; it shows how the 98 KB value for table space, used in section 5.1.1, was calculated; and it shows the parameters and total table space required for the example system depicted in section 5.1 To determine the table space for any configuration, multiply the value of each configuration parameter by its corresponding memory allowance (see column 1, table 5B). Next, add the result of these calculations (see column 2). The result is the allowance for table space. To determine the memory allowance for operating system dynamic work space (i.e. unswappable memory) use the following formula: " dynamic memory" (bytes) = (49 +("fds" / 4) + (("procs" * 2704) / 512 / 2)) * 512 SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB049 Pg027 The variables in this formula from left to right are: 49 - the number of 512 byte pages for miscellaneous operating system space "fds" - the number of open files configured "procs" - the number of processes configured 2704 - the size (bytes) for each process's user area / 512 - for converting into 512 byte pages / 2 - one half the number of pages * 512 - for converting pages into bytes For the base configuration the dynamic memory allowance is: "dynamic memory" (bytes = 49 + (60/4) + ((16 * 2704) / 512 /2)) * 512 = 54400 bytes or 53KB For the example system (see section 5.1.1) the memory allowance is: "dynamic memory" (bytes) = (49 + (218/4) + ((65 * 2704) / 512 / 2)) * 512 = 140872 bytes or 138KB or 36.6KB (base size) + (49 * 1.7KB) (extra procs, 65-16)=120KB NOTE: 1.7 is obtained by (138-53)/49, the additional "procs" (65-16). NOTE: The operating system dynamic work space -- nicknamed unswappable memory -- is a vital work area for the operating system. Within this work area is the process environments (i.e. user area or "uarea") for all active process in the system. Also within this area is printer input and output buffers, ISAM key and dictionary information, and other operating system structures which get dynamically allocated or de-allocated depending on system load. _______________________________________________________________________ | BOSS/IX | memory |param.'s| total |param.'s|total |memory for ea. | | PARAMETERS|used for|for base| memory | for |memory |additional: | | (set by | each |config- |for base|example |for |---------------| |"vconf" or | param |uration | system |system* |example| | | | | "sconf") | (bytes)|system | (bytes)| |system |USER|GHOST|PTR | | | | | | |(bytes)| | | | |-----------------------------------------------------------------------| |buffers= | 594 | 20 | 11880 | 32 | 19008 |2376| | | |printers= | 906 | 1 | 906 | 4 | 1812 | | | 906| |procs= | 324 | 14 | 5184 | 27 | 8748 | 972| 324 | 324| |tsegs= | 24 | 12 | 384 | 22 | 528 | 40| | | |locks= | 40 | 35 | 2960 | 94 | 3760 | 200| 200 | | |ibsize= | 128 | | 256 | | 640 | 128| | | |tbsize= | 64 | | 128 | 16 | 320 | 64| | | |mfsys= | 424 | 3 | 1272 | 3 | 1272 | | | | |lus= | 44 | 65 | 5984 | 224 | 9856 | 800| 880 | 264| |fds= | 92 | 60 | 5520 | 97 | 8924 | 736| 920 | 172| |eventcalls=| 20 | 16 | 320 | 95 | 1900 | 32| | | | | | | | | | | | | |TOTALS | | | 32388 | | 52590 |5148|2144 | 982| | | --- | --- | | --- | or | or | or | or | | | | | | | 51 KB |5 KB|2 KB |1 KB| SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB049 Pg028 |_______________________________________________________________________| TABLE 5A BOSS/IX Operating Parameters and Memory Requirements (Table Space) for Model 2000 ____________________________________________________________________________ | BOSS/IX | memory |param.'s| total |param.'s|total | memory for each | | PARAMETERS|used for|for base| memory | for |memory | additional: | | (set by | each |config- |for base|example |for |--------------------| |"vconf" or | param |uration | system |system* |example| | | | . | "sconf") | (bytes)|system | (bytes)| |system | USER |GHOST | PTR | | | | | | |(bytes)| | | | |----------------------------------------------------------------------------| . |**buffers= | 594* | 128 | 76032*| 1280 |760320*|38016*|38016 | | |printers= | 906 | 1 | 906 | 4 | 3624 | -- | -- | 268| |procs= | 324 | 16 | 5184 | 65 | 21580 | 996| 332 | 332| |tsegs= | 24 | 16 | 384 | 44 | 1056 | 48| | | |locks= | 40 | 74 | 2960 | 164 | 6560 | 200| 200 | | |ibsize= | 128 | 2 | 256 | 16 | 2048 | 128| | | |tbsize= | 64 | 2 | 128 | 16 | 1024 | 64| | | |mfsys= | 424 | 3 | 1272 | 4 | 1696 | | | | |lus= | 44 | 136 | 5984 | 556 | 24464 | 880| 880 | 264| |fds= | 92 | 60 | 5520 | 218 | 20056 | 736| 920 | 172| |eventcalls=| 20 | 16 | 320 | 56 | 1120 | 40| 100 | | . |dirc= | 48* | 64 3027*| 338 | 16224*| 384*| 480*| 96| | | | | | | | | | | . |TOTALS | | | 102018*| |859792 |41492*|40928*| 1132| |excluding | --- | --- | or | --- | or | or | or | or | |hash tables| | | 99 KB* | |839 KB*|40 KB*|40 KB*|1.1 KB| | | | | | | | | | | . |TOTALS | --- | --- | 101 KB | --- | 853 KB|41 KB |41 KB | 2 KB| |hash tables| | | | | | | | | |____________________________________________________________________________| . TABLE 5B BOSS/IX Operating Parameters and Memory Requirements (Table Space) for Model 2500, 3000, and 4000 * Excludes hash table size which must be calculated separately based on the number of entires requested, then added to the total system requirement. ** Size, number of calculation differs from Model 2000 __________________________________________ | | | | Number of | | | Entries | Memory | | Requested | Required | | | | | through 63 | .5KB | | | | | 64 through 127 | 1KB | | | | SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB049 Pg029 | 128 through 255 | 2KB | | | | | 256 through 255 | 4KB | | | | | 512 through 1023 | 8KB | | | | | 1024 through 2047 | 16KB | | | | | 2048 through 4095 | 32KB | | | | | 4096 through 8191 | 64KB | | | | | 8192 through 16383 | 128KB | | | _| This table is used to obtain the amount of memory needed for hash tables for either the 'buffers' or 'directory cache' operating parameters (see Table 5B). The per entry charge is not included here and must be added to the value from this table. TABLE 5C Memory Required for Hash Tables 6.0 NEW AND UPDATED MANUALS FOR LEVEL 7.4B M6211B BOSS/IX (7.4) User Reference Manual M6227B BOSS/IX (7.4) Technical Reference Manual M6201A MAI 2500 User Guide M6204A MAI 2500/3000/4000 Diagnostic and Error Logging Reference Manual 7.0 HELPFUL HINTS This section gives miscellaneous information about the 7.4B O.S. release and the MAI 4000 system. 7.1 Four-way and Eight-way Configuration o A maximum of nine Eight-ways are allowed in the MAI 4000 system. o Four-ways are not allowed in the Expansion Unit. 7.2 Memory Configuration o The MAI 4000 system and 7.4B O.S. only support up to 16MB of RAM. o The MAI 4000 only suppors up to six memory boards. This could include 4MB boards and 1MB boards. 7.3 Disk Configuration o The MAI 4000 supports up to seven disk drives. They . are installed with three drives in the main unit and four drives in the expansion unit. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB049 Pg030 . o The disk drives must be specified by device name according to the following diagram. ______________________ ______________________ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | WD2 | | WD6 WD5 | | SLOT3 SLOT2 | | SLOT7 SLOT6 | | | | | | | | | | WD1 WD0 | | WD4 WD3 | | SLOT1 SLOT0 | | SLOT5 SLOT4 | | | | | |______________________| |______________________| MAI 4000 DISK CONFIGURATION For minor number, multiply the SLOT number by 32. Example: For WD3 - SLOT (4) x 32 = 128 Major Minor 14 , 128 NOTE: SLOT 3 is reserved for the MCS tape drive. ORIGINATOR: J. Shreve SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB049 Pg031 FIB 00050 12/19/88 *** Extra Files Created - TBC on 7.3A or 7.4A [ WPSF 484 ] *** PROBLEM: Multiple files are created when receiving a single file on a BOSS/IX system on 7.3A or 7.4A using 2780/3780. SOLUTION: Modify program /tbc/BCOM/BRCV. Replace statement 4012: OLD: 4012 LET R8=R8+1; IF R$<>"" THEN LET L8=L8+1 NEW: 4012 IF R$<>"" THEN LET L8=L8+1 Add 5 statements: 1525 IF R$="" THEN LET L8=L8+1 2205 R8=R8+1 2245 R8=R8+1 2455 R8=R8+1 2720 R8=R8+1 ORIGINATOR: T. Tiangco SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB050 Pg001 FIB 00051 12/19/88 *** Incorrect 'errlog' Command in BOSS/IX User Ref Manual [ WPSF 489 ] *** PROBLEM: The example shown in the BOSS/IX User Reference Manual (M6211B) page 5-87 has the incorrect 'errlog' command. Manual Part Number: 006211-002 (January 1988) SOLUTION: Change example on page 5-87 as follows: @> errlog /sys/errlog - initial errors=10 (INCORRECT) @> /sys/errlog /etc/error.log - initial errors=10 (CORRECT) This error will be corrected on the next User Reference Manual release. ORIGINATOR: C. Figueroa SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB051 Pg001 FIB 00052 12/20/88 *** ERR 47's using BCOM on 7.4A/B [ WPSF 449-14 ] *** There are three areas which may cause an error 47 to occur on 7.4A/B when using Batch Communications. The following modifications should be made to correct this problem. Modify the following three programs to correct the problem: 1. Program "/tbc/BCOM/BALOC" 6000 REM "CREATE DIRECTORY" 6010 LET TEMP=0 6020 LET A9$=F7$ 6030 LET A9=POS("/"=A9$) 6040 IF A9<>0 THEN LET A9$=A9$(A9+1),TEMP=TEMP+A9 ELSE GOTO 6100 6050 IF A9=1 THEN GOTO 6030 6060 OPEN(19,ERR=6061) F7$(1,TEMP-1);CLOSE(19);GOTO 6030 6080 SYSTEM "/bin/makedir "+F7$(1,TEMP-1)+" >> /dev/null %% 6080:/etc/comm/systemerr.tbc. "+FID(0) 6090 GOTO 6030 6100 RETURN 2. Program "/tbc/BCOM/BRCVF" 1400 REM "CREATE DIRECTORY" 1410 LET TEMP=0 1420 LET A9$=A1$ 1430 LET A9=POS("/"=A9$) 1440 IF A9<>0 THEN LET A9$=A9$(A9+1),TEMP=TEMP+A9 ELSE GOTO 1480 1450 IF A9=1 THEN GOTO 1430 1460 OPEN(19,ERR=1461) A1$(1,TEMP-1);CLOSE(19);GOTO 1430 1470 SYSTEM "/bin/makedir "+A1$(1,TEMP-1)+" >> /dev/null %% 1470: /etc/comm/systemerr.tbc. "+FID(0) 1475 GOTO 1430 1480 RETURN 3. Program "/tbc/BCOM/BRCV" 15 IF A8>3 THEN LET A8=0 This problem will be fixed in the next release. ORIGINATOR: D. Jensen SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB052 Pg001 FIB 00053 12/20/88 *** Batch Communications Status Message 483 on 7.4A/B [ WPSF 449-15 ] *** The status message 483 with error codes of 47/042 or 26/042 while running Batch Communications may occur on BOSS/IX levels 7.4A/B. This problem occurs when empty records are received on the BOSS/IX system. The following changes should be made to correct the problem: Program "/tbc/BCOM/BRCV" 1470 IF R2>3 THEN GOTO 1501;REM "Bypass ESC 4 routing if protocol greater 1470:than 2780 1501 REM " Operating system allows R$="1" then R$=R$(2) give null string 1501:with no error 1505 IF R$="" THEN LET A9=0;GOTO 1513 1507 LET A9=POS(R$(1,1)=$111213$+")") 1510 IF A9<>0 THEN LET R$=R$(2) 1513 IF A9=0 AND DEVICE$<>"" THEN LET A9=NUM(DEVICE$)+1; REM "Set to last 1513:RCV device encountered if no routing code present 1515 IF R2<=5 AND A9=3 THEN LET A9=2 1518 IF R2<=5 AND A9=4 THEN LET A9=0 1520 IF A9<>0 THEN LET D6=A9-1,DEVICE$=STR(D6) ELSE IF A8>0 THEN LET D6=A8- 1520:1,A8=-1;REM "Set A8 to -1 for breakpoint - DEVICE$ remembers last RCV 1520:device capability set DEVICE$="" instead of DEVICE$=STR(D6) 1525 IF R$="" THEN LET L8=L8+1 This problem will be fixed on the next release. ORIGINATOR: D. Jensen SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB053 Pg001 FIB 00054 12/22/88 *** Escape Trapping notes [ WPSF 439 ] *** When a program begins execution, there is a certain amount of time that the ESCAPE key will be ignored. This "window" was designed to give the application time to set up any ESCAPE handling commands; i.e. SETESC or CONSOLELOCK. On the MPx, this window is 3 executable statements; on the 2000/3000/4000 this window . is one executable statement. An executable statement is any statement which performs one action such as PRINT, INPUT, READ RECORD, etc. Remark (REM) statements affect the statement count. For example, both code fragments below are counted as 3 statements: 10 OPEN(1)"FILE" 20 READ(1)A$ 30 CLOSE(1) and 10 OPEN(1)"FILE";READ(1)A$;CLOSE(1) On the 2000/3000/4000, only one executable statement can be executed before ESCAPE handling is enabled, therefore to totally prevent a user from ESCAPEing, the first statement in the program must be a SETESC or CONSOLELOCK. Many programmers use the beginning lines of a program to comment (using REM statements) the program. These REM statements count as executable statements. It is suggested that any error handling be set-up before these comment lines. ORIGINATOR: R. Case SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB054 Pg001 FIB 00055 12/28/88 *** Notes on Using the 'KL' Mnemonic [ WPSF 502 ] *** PROBLEM: The keyboard mnemonic 'KL' may not work as expected. The 'KL' mnemonic may allow input from the keyboard to be mixed into the terminal I.D. (or with any other information requested from the terminal.) The following are examples of code which could experience this problem: (1) >INPUT(1) 'KL','ES',"d",A$ (2) >INPUT(1) 'CI','KL','ES',"d",A$ (3) >INPUT(1) 'KL','CI','ES',"d",A$ This is because: (1) The system doesn't execute the command fast enough, allowing keyboard input to be placed into the type ahead buffer and sent to the system even after the keyboard is locked. (2) Data can still be input between the 'CI' and 'KL' mnemonics causing data to be mixed with the terminal I.D. (3) This still leaves a window for data to be mixed with the terminal I.D. because 'KL' is sent to the terminal and assumed completed then 'CI' is executed. 'KL' may not be completed immediately, leaving a window open for data to be sent to the system from the keyboard. SOLUTION: Send 'KL' and 'CI'; then wait for all potential data to be soaked up before sending out the command which causes the terminal to transmit the required data. Foe example: >330 PRINT(1) 'KL','CI' >340 READ RECORD (1,SIZ=1,TIM=1,ERR=360)A$ >350 GOTO 340 >360 INPUT(1),'ES',"d",A$ >370 PRINT(1),'KU' Be aware that this method throws away all stray data coming from the terminal. ORIGINATOR: B. Poling SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB055 Pg001 FIB 00056 02/08/89 *** Release 7.2R Software Announcement for 1800 System [ WPSS 160 ] *** Level 7.2R BOSS/IX Operating System and its related software products are now available for the MAI 1800 system. 7.2R contains several enhancements and corrections. It is recommended that all systems be updated with the 7.2R release. This Software Announcement contains general information about the 7.2R release. Please read this document before installing any 7.2R systems. This document should be used in conjunction with the MAI 1800 Software Announcement #152. Software Announcement #152 contains useful information such as operating system parameter customization, memory usage, security, dump procedures, and 27xx/37xx batch emulation (TBC) and this information still applies for 7.2R systems. For ordering information, refer to the appropriate Marketing Announcement. WARNINGS: An MAI 1800 system running an operating system release prior to 7.2R requires a full installation. Do NOT use the Upgrade/Reinstall procedures unless 7.2R has been previously installed. The 'Hard Disk Preparation' procedure outlined in this document is different from the procedure outlined in the MAI 1800 Software Announcement #152. Please follow the procedure outlined in this document. Modifying the vconf parameters in such a way that more memory is needed than is physically installed will cause a system crash (See section 6.1 of the MAI 1800 Software Announcement #152 for details). Copyright 1988 by MAI Basic Four, Inc. All rights reserved. TABLE OF CONTENTS 1.0 INTRODUCTION 2.0 SYSTEM START-UP AND SHUTDOWN 2.1 System Start-up 2.1.1 From Floppy Disk Drive 'A' 2.1.2 From Active Partition on Hard Disk Drive 'C' 2.1.2.1 A Standard Load from Active BOSS/IX Partition 2.1.2.2 An Alternate Load from the BOSS/IX Partition 2.1.2.3 A Standard Load From Active MS-DOS Partition 2.2 System Shutdown 3.0 INSTALLATION 3.1 System Set-up 3.2 Hard Disk Preparation 3.3 Installation and Upgrade Procedures for BOSS/IX 3.3.1 Installing BOSS/IX and MS-DOS on the Same Hard Disk SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB056 Pg001 3.3.2 Initial BOSS/IX Installation 3.3.3 Second Hard Disk Preparation 3.3.4 BOSS/IX System Upgrade/Reinstall Procedure 3.3.5 BOSS/IX Configuration Record Installation 3.4 Installing MS-DOS 3.4.1 Create MS-DOS Partition 3.4.2 Formatting and Copying MS-DOS to the Hard Disk 4.0 PRINTER SUPPORT 5.0 CORRECTIONS TO 7.2P 6.0 ENHANCEMENTS TO 7.2P 7.0 WARNINGS & CAUTIONS 8.0 HELPFUL HINTS 9.0 RELATED DOCUMENTATION 1.0 INTRODUCTION The 7.2R Operating System release contains the same functionality as the level 7.2P software release for the MAI 1800 system except for a few minor changes as outlined in this document. This document contains general information about the 7.2R Operating System on an MAI 1800 system. WARNINGS: It is required that a full installation be done when upgrading a system from 7.2N or 7.2P to 7.2R. This is due to a problem that existed in 7.2N and 7.2P, where alternate bad tracks were incorrectly handled under BOSS/IX. Therefore, back-up data on ALL partitions before proceeding with section 3.2 of this document. Once the 7.2R O.S. has been successfully installed, the BOSS/IX system upgrade procedures may be used for subsequent upgrades of the O.S. The hard disk preparation procedures in section 3.2 of this document are different than the procedures outlined in the MAI 1800 Software Announcement #152. Please follow the new procedures closely when preparing a hard drive. 7.2R also requires installation of a new configuration record. 2.0 SYSTEM START-UP AND SHUTDOWN 2.1 System Start-up NOTE: Do not cycle A.C. power when the floppy diskette is inserted and the disk drive lever is in the locked position. The MAI 1800 can be booted from floppy disk or from hard disk. Booting from 1/4" cartridge tape is not supported. The MAI 1800 can be booted with either the MS-DOS or BOSS/IX SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB056 Pg002 Operating System. The system start-up procedure to be used depends on which Operating System you wish to run and the device on which that Operating System is located. The Operating System can reside on Floppy disk drive 'A' (the top floppy drive on the system) or on the Active partition on Hard disk drive 'C' (the first hard disk drive on the system). When the system is powered up, it will automatically get the Operating System from Floppy drive 'A', if there is a bootable diskette (a diskette that contains a loader and an Operating System) in the drive and the disk drive door is closed. If there is a non-bootable diskette in Floppy drive 'A' at boot time and the disk drive door is closed, an error will be generated and you will be required to re-boot the system. If there is no diskette in Floppy drive 'A' or the floppy drive door is not closed, the system will automatically boot from the active partition on the Hard disk drive 'C'. If there is no active partition on the hard disk or the hard disk partition does not contain an Operating System, an error will be generated or the system may display unreadable characters on the Monitor. If the system is powered up and already has MS-DOS booted, it can be re-booted by depressing and holding down and , then quickly depressing and releasing all three. The system will then use the steps outlined above to boot the system. If the message "ERROR, (RESUME='F1' KEY)" appears, depress to complete the boot. The following are the steps required to boot the desired Operating System from the correct device. NOTE: If this is a new installation, you will first need to boot your system from Floppy drive 'A' by following the procedure outlined below for System start-up from a floppy. You will need to have the "SETUP and TEST' diskette in Floppy drive 'A' at boot time. 2.1.1 From Floppy Disk Drive 'A' To boot the system from Floppy drive 'A', perform the following steps: 1. Hold the diskette you wish to boot from with the label facing up and towards you, and insert it into Floppy drive 'A'. Do not put the disk drive lever in the locked position at this time. 2. If the system is powered off, power on the system. If the system has already been booted, depress and hold and then , and depress and quickly release all three keys. 3. Close the diskette locking lever at this time. The system will now boot from the diskette in Floppy drive 'A'. 2.1.2 From Active Partition on Hard Disk Drive 'C' SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB056 Pg003 As mentioned above, if there is a diskette in the floppy drive and the door is closed, the system will attempt to boot off the floppy. To boot from the active partition on the hard disk drive 'C', perform the following steps: 1. Ensure that the floppy drive door is open. 2. Ensure that the partition you wish to boot from is Active. NOTE: To verify which partition is Active or to activate a partition on a running system, perform the following: A. (Running under BOSS/IX) If you are on the BOSS/IX partition, run 'fdisk'. You MUST be in single user mode. At the ADMIN> prompt type 'fdisk', . This program will allow you to activate the MS-DOS partition. You will be required to re-boot the system after running this program and changing the active partition. B. (Running under MS-DOS) If you are on the MS-DOS partition, run 'fdisk'. This program will allow you to activate the BOSS/IX partition. In MS-DOS, the BOSS/IX partition is called non-DOS. 3. If the system is powered off, power on the system. If the system is already booted, perform the following: o From the MS-DOS partition, depress and hold and , and depress and quickly release all three keys. OR o From the BOSS/IX partition, perform an orderly shutdown (see section 2.2). After performing the shutdown procedure, press when prompted to press 'RETURN' to reboot. The system will now boot from the active partition on Hard disk 'C'. 2.1.2.1 A Standard Load from Active BOSS/IX Partition This procedure can be performed from a power off or power on condition. o If the system is in a power off condition, power on the system. OR o If the system is in a power on condition (after a proper 'shutdown' is performed and a "Press 'RETURN' key to reboot:" prompt is displayed), press . SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB056 Pg004 o When prompted to press 'RETURN' to reboot, press . o When prompted to select boot device and system files, press . The system will now boot from hard disk. The standard Operating System and '/etc/conf' configuration file supplied with the software will now be loaded. After the load is complete '/etc/start' will be executed. This will display the system proprietary message. o When prompted to continue with startup, press . Depending on what is configured in the '/etc/conf' file, the '' or '' message is displayed. If a minor error occurs during start-up, the error messages are reported in the '/etc/sys.log' file. '/etc/start' checks this file; and, if it contains data, the following message is displayed: An error occurred during system startup. File '/etc/sys.log' contains a description of the errors. Press the 'ESC' key to continue. . . If this message occurs, press the key and the ADMIN> prompt will then be displayed. Once at the ADMIN> prompt, you can print the contents of the '/etc/sys.log' file by using the command, 'p /etc/sys.log'. If no errors occurred, the ADMIN> prompt will display immediately. If a severe error occurs, the system will abort the boot process and a system crash message will be displayed. If the '/etc/conf' file is set to "secure mode", a 'Password:' prompt will be displayed before the ADMIN> prompt. If this prompt is displayed, you must enter the system administrator password followed by an . If the '/etc/conf' file is set to "multi mode", 'etc/startup' will be executed after is pressed. This program will startup all of the configured terminals on the system. If a minor error occurs anytime during the boot, the message telling that the error is in the '/etc/sys.log' file will be displayed after '/etc/startup' is complete. To get to the ADMIN> prompt from multi mode requires that you first enter and admin for operator name. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB056 Pg005 2.1.2.2 An Alternate Load from the BOSS/IX Partition An alternate load may be performed when the system prompts you to select boot device and system files. This allows you to load an alternate operating system (from floppy or wd0) or configuration file. o From a power off condition, Power on the system. OR o From a power on condition, perform the following if the system is not in a shutdown condition: - Perform an orderly shutdown (see Section 2.2). - When prompted to press 'RETURN' to reboot, press . The 'Select boot device and system files:' prompt is displayed. To load an alternate O.S. or configuration file requires a two part name. If one part is omitted, the default is used. Part one of the system file is a loadable O.S. file. '/sys/bossix' and 'dos' are examples of loadable O.S. files. Part two is a system configuration file. '/etc/conf' and '/etc/boot.conf' are examples of system configuration files. These two parts when entered together are separated by a comma, ",". If the first part is entered by itself, no comma is required and the system will default to the '/etc/conf' file, example: '/sys/bossix'. If the second part is entered by itself, for the case where you wish to root to the boot partition, the comma must precede the file name, example: ',/etc/boot.conf'. In the second case the system will default to the default O.S. '/sys/bossix'. 2.1.2.3 A Standard Load From Active MS-DOS Partition The system can be booted from either a power off or a power on condition. From a power off condition: 1. Be sure there is no diskette in disk drive A. If there is, remove it. 2. Make sure that power to the system monitor is turned on. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB056 Pg006 3. Turn the power switch (on the back, right of the CCA) to the on position. The system begins with a series of self-tests, including a check of the memory and the system setup record. If all goes well and the setup record appears correct, the operating system is loaded and the system boots. From a power on condition (only when the MS-DOS partition is active): 1. Hold down the and keys and press the key. The system boots at this time without displaying the memory tests. NOTE: The MS-DOS startup routine can be changed by creating and modifying the AUTOEXEC.BAT file in the root directory. This is described in the MS-DOS Reference Manual. The default startup routine, described here, is executed in the absence of AUTOEXEC.BAT. Once the system boots, the current date information and 'ENTER TODAY'S DATE...MMDDYY' prompt is displayed. o If the displayed date is incorrect, enter the correct date and press . If the date is correct press . The current time information and 'ENTER CURRENT TIME...HHMM' prompt is displayed. o If the displayed time is incorrect, enter the correct time and press . If the time is correct press . After the date and time have been entered, the C> prompt is displayed. NOTE: The BOSS/IX partition can be left active. MS-DOS may be booted from hard disk without activating the MS-DOS partition. This can be accomplished by doing an alternate load with the BOSS/IX loader active: o If the system is powered off, power on the system. OR o If the system is powered on, perform an orderly shutdown (see Section 2.2). When prompted to press 'RETURN' to reboot, press . SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB056 Pg007 o When prompted to select boot device and system files, enter 'dos', . The system will now boot the MS-DOS operating system. MS-DOS will operate as if the MS-DOS partition were active. 2.2 System Shutdown WARNING: When the BOSS/IX partition is active, it is very important that the system be shutdown properly. Failure to follow these procedures may result in damage to the filesystem and may cause a loss of data. From BOSS/IX The system can only be shutdown by the system administrator. Shutdown can be initiated from any terminal if the system is in multi-user mode. In single user mode, only the system console is active. To shutdown a system which automatically boots into multi-user mode, you must be logged in as the system administrator (ADMIN>). At the ADMIN> prompt, type 'shutdown x message' and press , where 'x' is the number in minutes until the system shutdown occurs and 'message' is any message you wish to display during the shutdown. The message is optional. If the system is in single-user mode, enter +'d'. The system then prompts 'single, multi, or shutdown?' At this prompt type 'shutdown', . If the system boots into single-user mode and is in multi-user mode, use the command 'shutdown x message', where 'x' is the number of minutes until shutdown and 'message' is any message you wish to display during the shutdown. The system will then shutdown into single-user mode, at which point enter +'d'. The system then prompts 'single, multi, or shutdown?' At this prompt type 'shutdown', . It is now safe to power off or re-boot the system. From MS-DOS No special shutdown procedure is required when running under MS-DOS. When running MS-DOS, you can turn off the power whenever any particular program has completed executing. 3.0 INSTALLATION NOTES: 1. BOSS/IX must be installed on the first partition. BEFORE INSTALLING OR UPGRADING THE SYSTEM IT IS RECOMMENDED THAT YOU READ THESE INSTRUCTIONS COMPLETELY. 2. Ensure that you have removed any write-protect tabs from the product diskettes before proceeding with installation. 3. If this is not the first installation, ensure you have a good back-up of your COMPLETE disk, including MS-DOS SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB056 Pg008 and BOSS/IX. The hard disk on the MAI 1800 can be partitioned and set up so that the system can be booted and run as either a single-user MS-DOS system or a multi-user BOSS/IX system. This section describes the procedure for installing BOSS/IX and MS-DOS on a one or two fixed disk system, beginning with preparing the fixed disk(s). If the system is going to be used only with BOSS/IX, this procedure must still be followed whereas the section on installing MS-DOS may be skipped. Before continuing with this procedure, ensure that you have the following diskettes: o MAI Setup and Test Diskette o MS-DOS 3.1 (2 floppies) Required only if MS-DOS is going to be installed. o BOSS/IX BOOT/INSTALL floppy diskette o Configuration record diskette o EOS product o EUT product o EBS product o Any other products you wish to install such as TBC and ITP. The EOS, EUT, and EBS products and the configuration record may be contained on a single 1/4" cartridge streamer tape. In addition to the above media, you will need the bad track information for your hard disk(s). This information is contained on a label attached to the underside of the MAI 1800 CCA and on the disk drive case. If for some reason the label on the CCA is missing, you will need to remove the cover and read the list from the disk drive case. The relevant information is the Cylinder and Head number. When you have the proper diskettes and have obtained the bad track information, you are ready to begin the installation. 3.1 System Set-up This section describes the procedure to tell the system how many hard disk drives are installed and what type they are. This must be done regardless of the combination of operating systems being installed, whether it be a system partitioned between BOSS/IX and MS-DOS or a system dedicated to BOSS/IX. To start, insert the "Setup and Test" diskette in floppy drive A (if your system has two floppy drives, Drive A is the top drive), and boot the system. When the boot is complete, the system will display the Diagnostics Main Menu. The setup program stores a record of certain configuration information in non-volatile battery-backed RAM. This infor- SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB056 Pg009 mation is required by the system to function properly, whether it is running under MS-DOS or BOSS/IX. The steps required to set up your system are outlined below: 1. Run the setup program from the Diagnostics menu by selecting Option 0, 'Run SETUP'. The Setup Main menu will be displayed. 2. From the SETUP MAIN menu select Option 0, 'Set date and time'. The current date and then time will be displayed. If they are correct, press ; if they are incorrect, type the correct date and time. When the date and time are correct type 'Y', , this will return you to the 'SETUP MAIN menu'. 3. From the SETUP MAIN menu select Option 1, 'Set Diskette drive type'. This option will allow you to set your floppy disk drive types. The system will display the drive type for both the floppy drives 'A' and 'B'. The floppy drive types are shown as follows: (Not installed = no floppy configured at that location) HIGH-DENSITY DISKETTE DRIVE - 1.2MB floppy DOUBLE-DENSITY DISKETTE DRIVE - 360KB floppy NOTE: The 360KB floppy drive and 360KB floppy are NOT supported under BOSS/IX. If the information is correct type a 'Y', . If the information is incorrect type an 'N', and type the correct information for the floppy drives. When the information is correct type a 'Y', . This will return you to the SETUP MAIN menu. 4. From the SETUP MAIN menu select Option 2, 'Set hard disk drive type'. This option will allow you to set your hard disk drive types. The system will display the drive types. In addition to these drive types, if no drive is configured at a location, it will display 'not installed'. If the information is correct, type a 'Y', . If the information is incorrect, type an 'N', , and follow the system prompts to enter the correct hard disk drive information (see section 3.3.1 for supported drive type information). When the information is correct, type a 'Y', , and this will return you to the SETUP MAIN menu. NOTE: When changing the hard disk drive information, the system will display the drive types followed by a prompt to 'enter selection'. This prompt is for hard disk 'C'. 5. From the SETUP MAIN menu, select option 3, 'Set system speed'. This option will allow you to set your system speed and, in addition, will enable or disable the system speed button located on the control panel. The system SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB056 Pg010 will display the current configuration for your system's speed options. If these are correct, type 'Y', . If they are incorrect type 'N', , and type the correct information. When the information is correct, type 'Y', , and this will return you to the SETUP MAIN menu. NOTE: BOSS/IX is only certified at 'high' speed (10Mhz). Normal system usage will be to set the system speed to 'high' and to 'disable' the system speed button. Some MS-DOS programs may require the 6Mhz clock speed. If MS-DOS is to be used frequently, choose 'enabled' to allow the user to switch between the 6Mhz and 10Mhz system speeds. 6. From the SETUP MAIN menu, select Option 4, 'Set expansion memory size'. This option will allow you to set system memory expansion. Currently the MAI 1800 supports 1.6MB or 2.6MB of memory. The memory size must be changed according to the amount of memory installed. If the information is incorrect, type an 'N', , and follow the system prompts to enter the correct expansion memory size. If you have 1 expansion memory board (standard with each system), select Option 2 for 1024KB (1MB). If you have 2 expansion memory boards, select Option 4 for 2048KB (2MB). NOTE: Do NOT include the 640KB of motherboard memory in your expansion memory setup. 7. From the SETUP MAIN menu, select Option 5, 'Set primary display type'. This option will allow you to set the type of controller your monitor is connected to. The question 'Is a GDA board installed ?' should be answered with a 'Y'. When the information is correct, type 'Y', , and this will return you to the SETUP MAIN menu. 8. From the SETUP MAIN menu, select Option 6, 'Review the current configuration'. This option will allow you to review the existing system setup. If any of the entries are incorrect, return to the SETUP MAIN menu by typing an and repeating the appropriate steps. If the entries are correct, enter an to return to the SETUP MAIN menu. 9. To exit the setup program and save the updated configurations, select Option 7, 'Exit setup and save new configuration'. The system will display the new configuration and prompt you if the entries are correct. If the settings are correct, enter 'Y', . The system will now automatically REBOOT. NOTE: The 'Setup and Test' diskette must remain in drive 'A'. 3.2 Hard Disk Preparation The following outlines the steps required to prepare the hard disk. These procedures must be followed to allow for operating system installation. If your system has two hard SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB056 Pg011 disk drives, follow this procedure twice. The first time using drive 'C' and the second time using drive 'D'. The general steps involved in preparing a hard disks are: (A more detailed explanation is given starting at step 1 below) a. Display the DOS bad track list (if one exists) and write down any bad track information that is not listed on the hard error map. The hard error map is located on the bottom of the CCA and on the disk drive. b. Initialize the hard disk. c. Run the destructive surface scan. d. Initialize the hard disk. The disk must be initialized a 2nd time after a destructive surface scan is performed. e. Enter the bad tracks including: - Bad tracks listed on the hard error map. - Any additional bad tracks found during the destructive surface scan. - Any additional bad tracks found in the MS-DOS bad track list (if one existed prior to the first initialization). 1. From the USER DIAGNOSTICS MAIN MENU select Option 4, 'Hard disk preparation'. The system will display the HARD DISK PREPARATION menu, with a message that no disk drives are selected. Enter Option 0, 'Select drive', from the menu. The system will prompt for drive 'C' or 'D', type 'C'. The system will now display 'Hard disk drive C: selected'. NOTE: If the drive has been previously initialized and used for on an MAI 1800 system, you should display the bad track information contained in the MS-DOS bad track list. Enter Option 3, 'Display current bad track list', from the menu. Write down any cylinder and head information that is not already listed on the hard error map. Press , after all information has been written. 2. From the option menu enter Option 2, 'Initialize hard disk'. WARNING: This will destroy all the data on the disk and should only be run the first time the system is installed. If it is required to run this program again, ensure you have a good back-up of your COMPLETE disk, including MS-DOS and BOSS/IX. You will be prompted twice to ensure this is what you wish to do. Answer 'Y' to the first question and to the second. If you do not wish to initialize your disk, enter . SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB056 Pg012 3. When the initialization program is complete, you will be prompted with a message telling you the program is complete and asking you to enter to continue. Enter , and you will be returned to the HARD DISK PREPARATION menu. 4. After the hard disk initialization is performed on the drive, it is recommended that a read/write destructive surface scan test be run. This test should detect any potential bad tracks that weren't listed on the hard error map. The test time depends primarily on the hard disk capacity. Enter , to return to the USER DIAGNOSTICS MAIN menu. From the main menu, select Option 3, 'Hard disk drive test'. Select Option 0, 'Select drive'. Select 'C' or 'D' depending on the drive to be tested. Select Option 4, 'Select destructive test'. Select Option 5, 'Start testing'. Type a 'Y' to start testing. After the test has completed, the display shows the number of bad tracks found. Press , at the prompt 'Do you want to save new bad track list (Y/N)', type 'Y' and press again. Select Option 6, "Display current bad track list'. Write down the cylinder and head information for all bad tracks listed. After all information is written, enter twice. This will return you to the USER DIAGNOSTICS MAIN menu. NOTE: The disk initialization must be performed after a destructive disk test has been performed. 5. From the USER DIAGNOSTICS MAIN menu select Option 4, 'HARD DISK PREPARATION'. The system will display the Hard disk preparation menu, with a message that no disk drives are selected. Enter Option 0, 'Select drive', from the menu. The system will prompt for drive 'C' or 'D', enter 'C'. The system will now display 'Hard disk drive C: selected'. 6. From the option menu enter Option 2, 'Initialize hard disk'. You will be prompted twice to ensure this is what you wish to do. Enter 'Y' to the first question and to the second. 7. When the initialization program is complete, you will be prompted with a message telling you the program is complete and asking you to enter to continue. Enter , and you will be returned to the Hard Disk Preparation Menu. From this menu, select Option 1, 'Enter bad tracks'. 8. This step outlines the procedure to spare the bad tracks. You must enter: - Bad tracks listed on the bottom of the CCA or on the disk drive. - Any additional bad tracks found during the hard disk destructive test. - Any additional bad tracks found in the MS-DOS SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB056 Pg013 bad track list (if one existed prior to the first initialization). The following prompt appears and allows you to enter the cylinder number and head numbers listed on the Hard Error Map: TYPE CYLINDER NUMBER, COMMA, HEAD NUMBER, AND THEN PRESS From the bad track list, enter the cylinder number, followed by a comma, the head number, and press ; for example: 49, 3 . If you enter a nonexistent cylinder or head number, you will be prompted that the wrong head or cylinder has been entered and to press to continue. allows you to go back and re-enter the correct numbers. NOTE: If the hard disk capacity is either 58MB or 115MB the following cylinders can not be entered or used: For the 58MB drive, cylinders 978-1024 are invalid and head 7 is invalid. For the 115MB drive, cylinders 901-918 are invalid. After you press to enter the numbers for a bad cylinder, you will be prompted to answer with a 'Y' if the information is correct or an 'N' to cancel the entry. Entering either choice, Y or N, the entry prompt appears again. Continue to enter the data from the Hard Error Map until all the bad track numbers from the list have been entered. When you have finished entering the bad track numbers, press . The system will display a table of the bad tracks you have just entered. You will then be prompted if you wish to save the list. If this list is incorrect, type 'N' to re-enter the list. If it is correct, type 'Y' . A message will be displayed telling you to 'RUN FDISK and FORMAT to spare bad tracks'. Enter to return to the Hard Disk Preparation Menu. 3.3 Installation and upgrade procedures for BOSS/IX The following steps outline the MAI 1800 BOSS/IX installation procedures. 3.3.1 Installing BOSS/IX and MS-DOS on the Same Hard Disk Disk Disk Number of Number of Bytes Type Capacity Cylinders Per Cylinder 2 20MB 614 34,816 3 31MB 614 52,224 18 58MB 976 60,928 9 115MB 899 130,560 NOTE: This info can be used to compute the size of a BOSS/IX partition. 1MB = 1024 x 1000 = 1024000 bytes. The example shown to the right is for a 58MB drive where the user needs 10MB for an SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB056 Pg014 MS-DOS partition. o Divide 1MB by the number of cylinders for a particular drive to get cylinders per Meg. Ex. 1024000 / 60928 = 16.81 (cylinders per Meg for a 58MB drive) o Multiply cylinders per Meg by the number of Meg required for a non-BOSS/IX partition. Ex. 16.81 * 10 = 168 (# of cylinders for a 10MB partition on a 58MB drive) o Subtract the above result from the number of cylinders for that drive type. This result gives the number of cylinders to use for option B. Option B is explained in section 3.3.2. Ex. 976 - 168 = 808 If you intend to install both BOSS/IX and MS-DOS on the hard disk: 1. Compute the number of cylinders that will be devoted to the BOSS/IX partition (see above chart for cylinder information). BOSS/IX overhead is approximately 9MB. Allow enough room for BOSS/IX overhead, user programs, and user data. 2. Follow the instructions outlined in section 3.3.2 using option B. 3.3.2 Initial BOSS/IX Installation Step 1: Install the boot partition. o Insert the BOSS/IX boot floppy in the diskette drive and close the latch. o Power on the system using the on/off switch located to the rear of the CCA. o When prompted to select boot device and system files, type 'f', . The system will now boot from floppy. o When prompted to continue with system startup press . The install menu will be displayed. o Select menu option 'A' or 'B' depending on the requirements. Option 'A' will install BOSS/IX on the entire hard disk leaving no partition available for DOS. Option 'B' will install BOSS/IX on the first portion of the hard disk. o Type either 'A', . OR SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB056 Pg015 o 'B #', . NOTE: # refers to the number of cylinders dedicated to the BOSS/IX partition (see section 3.3.1 for cylinder information). The hard disk is now being prepared (BOSS/IX bad tracks table set up, partitions created, etc.) and the boot partition is being installed. o After this procedure is complete, the OPTION> prompt will appear. Press +'d'. Type 'shutdown', . Step 2: Install the configuration record. WARNING: If the configuration record for the system is not installed, you will be able to access the boot partition only. o Remove the floppy diskette. o When prompted to press 'RETURN' to reboot, press . o When prompted to select boot device, press . The system will now boot to the boot partition. o When prompted to continue with startup, press . The system will display the ADMIN> prompt. o Insert the configuration floppy into the respective drive. o Type 'confinstallf', . o The message 'insert CONFIGURATION floppy into drive, press ...' is displayed. Press to proceed with installation. The configuration record is now installed. o Remove the configuration floppy. Step 3: Install the Operating System. NOTE: The following steps will create the filesystem on the root partition and install the operating system files. If EOS is on the floppy disk base set, you must insert the #1 disk first (See step 7 for a breakdown of the BOSS/IX floppy diskette set). You will then be prompted to enter each remaining disk one by one. The EOS floppy disks MUST be inserted in the proper sequence. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB056 Pg016 o Insert the EOS floppy diskette #1 in the drive or insert the MCS cartridge tape into the tape drive. o Type 'osinstall fd0', (for floppy), or type 'osinstall cs', (for 1/4 " streamer tape). o The message 'This procedure will destroy all previous data on the root partition. Press RETURN to continue (Escape to abort)...' is displayed. Press . Step 4: (OPTIONAL) Setup second hard disk This procedure prepares hard disk /dev/wd1 to be used as a single mountable filesystem. Make sure that the hard disk has been properly inititialized and setup. Refer to sections 3.1 & 3.2 for details. o Type 'prepdisk1', . Step 5: Shutdown the System o Press +'d'. o Type 'shutdown', . o Remove any diskette from the floppy drive. Step 6: Boot the system from the hard disk o When prompted to press 'RETURN' to reboot, press . o When prompted to select boot device, press . The system will now boot from hard disk. o When prompted to continue with startup, press . The system will display the ADMIN> prompt. Step 7: Install Desired Software Products NOTE: The MAI 1800 software products base system is contained on either one 1/4" cartridge tape or eleven floppy diskettes. The eleven floppies are labeled as base 1 of 11 ... base 11 of 11. The base system is differentiated as: PRODUCT BASE DISKETTE(S) EOS 1 and 2 (of 11) EUT 3 thru 6 (of 11) EBA 7 (of 11) ITP 8 (of 11) EBS 9 (of 11) INT 10 (of 11) TBC 11 (of 11) SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB056 Pg017 The EOS product was already installed thru the 'osinstall' or 'osupdate' command from the boot partition. EUT (BOSS/IX utilities) and EBS (BASIC) should be installed at this time. EBA (BASS diagnostics), ITP (Intersystem Transport), (INT International Tools), and TBC (Batch Communications) are optional products and should only be installed if they are required. ITP requires a software key if the expanded features are to be used. Refer to the ATP 4.0 Software Announcement #150. TBC requires extra hardware as well as a public key. Refer to the MAI 1800 Software Announcement #152. o At the ADMIN> prompt, type 'install fd0 XXX', for each software product to be installed from the floppy diskette where XXX is the product name. o Insert the first XXX product diskette in the drive and press . o Insert any additional diskettes as required and press when prompted. OR o At the ADMIN> prompt, type 'install cs XXX YYY ... ZZZ', to install the software products from 1/4" cartridge tape. XXX YYY ... ZZZ indicate the products to be installed. When working with tapes, all products can be installed with one command line. When working with floppies, you must install one product at a time. Products that are chargeable and not part of the base system will have public key codes that you must enter during or after (using '/bin/install key') installation before you can use that product. After you have copied all products to disk and have customized the '/etc/conf' file, your system is ready for use. This completes the O.S. installation procedure. 3.3.3 Second Hard Disk Preparation This procedure prepares hard disk /dev/wd1 (the 2nd hard disk) to be used as a single mountable filesystem SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB056 Pg018 under BOSS/IX control. Make sure that the hard disk has been properly initialized and setup (see Sections 3.1 & 3.2). NOTE: 'prepdisk1' is a macro on the BOOT partition. This macro uses the 'fdisk', 'badtrk', and 'makefs' commands to prepare the 2nd hard disk for BOSS/IX. Step 1: Shutdown the System o See section 2.2 for shutdown procedures o Assure that no diskettes are installed. Step 2: Boot the System and ROOT to the BOOT Partition o When prompted, press to reboot the system. o When prompted to select boot device and system files, type ',/etc/boot.conf', . o When prompted to continue with startup, press . The system will display the ADMIN> prompt. Step 3: Setting up the Hard Disk Ensure that the hard disk has been properly formatted. o Type 'prepdisk1', . Hard disk /dev/wd1 is now prepared and available as a mountable filesystem. Step 4: Install the System Configuration Record NOTE: The configuration record only needs to be installed if the original configuration record specified one hard disk. o Type 'confinstallf', to install the configuration record from floppy diskette. o Insert the floppy diskette labeled 'configuration' into the drive. o Press to proceed with the configuration installation. The configuration record is now installed. Step 5: Shutdown the System o Press +'d'. o Type 'shutdown', . Step 6: Boot the system from the hard disk o When prompted to press 'RETURN' to reboot, SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB056 Pg019 press . o When prompted to select boot device, press . The system will now boot from hard disk. o When prompted to continue with startup, press . The system will display the ADMIN> prompt. The second hard disk preparation is now complete. 3.3.4 BOSS/IX System Upgrade/Reinstall Procedure Perform this procedure on a system already installed with BOSS/IX. The system may be completely reinstalled or just upgraded with this procedure. WARNING: Always have a current back-up before doing any upgrades. 'osupdate' will preserve user files whereas 'osinstall' will destroy all files. Step 1: Shutdown the System o See section 2.2 for shutdown procedures. o Remove any floppy diskette from the drive. Step 2: Boot the System and ROOT to the BOOT Partition o When prompted to press 'RETURN' to reboot, press . o When prompted to select boot device and system files, type ',/etc/boot.conf', . o When prompted to continue with startup, press . The ADMIN> will be displayed. Step 3: Install the System Configuration Record NOTE: Skip Step 3 if the configuration record has not changed from the previous version. o Type 'confinstallf', to install the configuration record from floppy diskette. o Insert the floppy diskette labeled 'configuration' into the drive. o Press to proceed with the configuration installation. The configuration record is now installed. o Remove any diskette from the floppy drive. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB056 Pg020 Step 4: Update or reinstall Root Partition o Insert the first EOS product disk into the floppy drive or insert the install tape containing EOS into the tape drive. o Type 'osupdate fd0', (For floppy update). Insert additional diskettes as required and press when prompted. OR o Type 'osupdate cs', (For 1/4" streamer tape update). OR o Type 'osinstall fd0', (For floppy install). Insert additional diskettes as required and press when prompted. OR o Type 'osinstall cs', (For 1/4" streamer tape install). NOTE: Both 'osupdate' and 'osinstall' auto- matically update the BOOT partition. After the procedure ('osupdate' only) is complete, you have the option of restoring the default system configuration files to the upgraded root and then to the boot partition. This is done by typing "/sys/installetc". This procedure allows you to select which system files you need to restore. Please note that if this is done, all system files that are restored will be new and will have to be re-updated to reflect the necessary system information. Example: If '/etc/passwd' is re-installed, the operators will have to be redefined. Following, find a list of the files that can be installed using '/sys/installetc' and the means to modify the file for your system: /etc/class, /etc/defaults, /etc/forms: The above files are used when printing and can be customized by going to the 'ut.printer' menu and using Option 5 'Printer parameters' or using the program 'pparams'. /etc/conf: The above file contains the system configuration parameters and is changed by using the '/bin/vconf' command. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB056 Pg021 /etc/exem, /etc/logm, /etc/motd: The above files print to the screen at the time of log in and can be modified by the use of the '/bin/ved' command. /etc/passwd: The above file contains your operator information and is updated by going to the 'ut.system' menu and using Option 3, (Operator information) or by using the program 'oprinfo'. /etc/ports, /etc/printers, /etc/terminals: The above files contain the terminal and printer configuration parameters and are updated by going to the 'ut.system' menu and using Option 1, (Port configuration) or by using the program 'configure'. /etc/sinit, /etc/startup: The above files are used at system load time and can be modified by the use of the '/bin/ved' command. /etc/shtdwn: The above file is used when the system is being shutdown and can be modified by the use of the '/bin/ved' command. Step 5: Shutdown the System o See section 2.2 for shutdown procedures Step 6: Boot the System from Hard Disk o When prompted to press 'RETURN' to reboot, press . o When prompted to select a boot device, press . o When prompted to continue with startup, press . The ADMIN> prompt will be displayed. Step 7: Install Desired Software Products o Type 'install /dev/fd0 XXX', for each software product to be installed from the floppy diskette where XXX is the product name. o Insert the first XXX product diskette in the drive and press . SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB056 Pg022 o Insert any additional diskettes as required and press when prompted. OR o Type 'install /dev/cs XXX YYY ... ZZZ', to install the software products from 1/4" cartridge tape. XXX YYY ... ZZZ indicate the products to be installed. The system update/reinstall procedure is now complete. NOTE: In certain cases you may want to upgrade the boot partition without upgrading the root partition operating system files. The following procedure will affect the boot partition only. However, always have a current back-up before doing any upgrade procedure. Install boot partition, while preserving current partitions: o Power on the system using the on/off switch located to the rear of the CCA. o While the system is displaying the memory selftest, insert the BOSS/IX boot floppy in the diskette drive and close the latch. o When prompted to select boot device and system files, type 'f', . The system will now boot from floppy. o When prompted to continue with system startup press . The install menu will be displayed. o Select menu option 'C' (Preserve current partitions, and install boot partition). o Type 'C', . The boot partition is now being prepared. o After this procedure is complete, the OPTION> prompt will appear. Press +'d'. Type 'shutdown', . This completes the boot partition upgrade. 3.3.5 BOSS/IX Configuration Record Installation Each system needs a unique configuration record based on the system serial number and hardware config- uration. Perform the following procedure to install a different configuration record. For example, a new configuration record would be required to enable the installation of an additional 8-way controller board. Step 1: Shutdown the System o See section 2.2 for shutdown procedures SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB056 Pg023 Step 2: Boot the System to the BOOT partition o When prompted to press 'RETURN' to reboot, press . o When prompted to select a boot device and system files, type ',/etc/boot.conf', . o When prompted to continue with startup, press . The ADMIN> prompt will be displayed. Step 3: Install System Configuration Record o Type 'confinstallf', . o Insert configuration floppy into floppy drive. o Press to proceed with configuration installation. Configuration record is now installed. o Remove configuration floppy. Step 4: Shutdown the System o Press +'d'. o Type 'shutdown', . o Assure that no diskettes are installed. Step 5: Boot the System from Hard Disk o When prompted to press 'RETURN' to reboot, press . o When prompted to select a boot device, press . o When prompted to continue with startup, press . The ADMIN> prompt will be displayed. The configuration record is now installed. Once you have installed/upgraded the configuration record on your system it will not have to be done again unless a hard disk re-initialization is required or the system's hardware configuration changes. 3.4 Installing MS-DOS 3.4.1 Create MS-DOS Partition This section describes the procedure for creating a MS-DOS partition using MS-DOS FDISK and installing MS-DOS onto the system. NOTES: a. The BOSS/IX partition should already exist SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB056 Pg024 before proceeding. The BOSS/IX partition is automatically created during the BOSS/IX installation or upgrade. Option 'B' was used to allow for a coexisting MS-DOS partition (see section 3.3). b. The maximum size for a single MS-DOS partition is 32MB. c. The maximum number of MS-DOS partitions on a disk is 3. If BOSS/IX is to coexist, only 1 MS-DOS partition is allowed. d. If the system contains 2 disk drives, the 2nd disk must be prepared for either BOSS/IX or MS-DOS. e. FDISK will not allow a partition to start in a cylinder where a bad track has been marked. If the cylinder selected as the starting cylinder contains a reserved bad track, FDISK automatically starts the new partition in the next cylinder that does not contain bad tracks. Following are the steps required to create the MS-DOS partition: 1. Insert the MS-DOS diskette (1 of 2) into floppy drive 'A' and boot the system. After entering the date and time, the system will respond with the MS-DOS prompt A>. 2. Enter 'fdisk', and the system will display the FDISK Options menu. The default choice is 1. 3. Select Option 1, 'Create MS-DOS Partition'. The system displays the total disk space, maximum available space, and the following prompt: ENTER PARTITION SIZE........: Press . 4. When prompted to 'ENTER STARTING CYLINDER NUMBER', press . 5. When prompted to 'Press ESC to return to MS-DOS', press . 6. The following message is displayed: 'Please insert MS-DOS diskette into drive A: Press any key when ready...................' Press any key. 7. When the system re-boots, enter the date and time. Proceed to the next section. 3.4.2 Formatting and Copying MS-DOS to the Hard Disk SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB056 Pg025 This section details the procedure used to format the hard disk for MS-DOS and to copy the MS-DOS files to the disk. 1. At the A> prompt, enter 'fdisk', . The FDISK options menu will be displayed. 2. At the 'Enter choice:' prompt, Enter '2', . The system displays a table with the partition information leaving the cursor positioned at the prompt at the bottom of the screen. The column headings are defined as follows: PARTITION - the number of the partition in the order in which it appears on the hard disk. STATUS - shows whether a partition is 'A' (for Active, i.e., in control when the system is started from the hard disk) or 'N' (for Non-active). TYPE - shows whether the operating system that occupies the partition is MS-DOS or not. START - the starting cylinder number for the partition. END - the ending cylinder number for the partition. SIZE - the size of the partition in cylinders. 3. Change the MS-DOS partition status to active. The MS-DOS partition should be partition # 2. If this is the case, when prompted to 'Enter the number of the partition you want to be active..........:', type '2', . 4. Press . The FDISK Options menu is displayed. Press . the A> prompt is displayed. 5. At the A> prompt, enter 'format c: /s/v', . The system will display a warning message that the program will destroy all the data on the disk and prompt for a 'Y' to continue. NOTE: Only the MS-DOS partition data will be destroyed. The BOSS/IX partition will remain intact. 6. Enter 'Y' and the system will again display a warning message that the program will destroy all the data on the disk and prompt for a 'Y' to continue. Enter 'Y', . The system will respond with: Formatting... Verifying... System transferred SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB056 Pg026 7. The last message says that a copy of MS-DOS has been placed on the disk. You are now prompted for a label to identify the disk. The label can be up to 11 characters long or a will equal no label. Enter the label and when complete. The system will next display information about disk space allocation in bytes, used by the system and bytes available on the disk. 8. The system responds with the MS-DOS prompt A>. To copy all files from your MS-DOS diskette onto the hard disk enter 'copy *.* c:', . 9. When the transfer is complete, remove the MS-DOS diskette from the floppy disk drive. 10. Insert the MS-DOS (2 of 2) diskette into the floppy disk drive and enter 'copy *.* c:', . 11. Remove the MS-DOS diskette from the floppy disk drive and set it aside. Your system now has MS-DOS in the MS-DOS partition of the hard disk. 4.0 PRINTER SUPPORT*1 __________________________________________________________________ | | | O.S. Support Interface*2 | | -------------- -------------------------- | | Model # MS-DOS BOSS/IX I/S Ser. MBF Ser. Par. | |..................................................................| | PT-4223 Yes*6 Yes Yes No Yes*5 | |..................................................................| | PT-4222 Yes*7 Yes Yes No Yes | |..................................................................| | PT-4218 Yes*7 Yes Yes*5 Yes*3 Yes*5 | |..................................................................| | PT-4217 Yes*7 Yes Yes*5 Yes*3 Yes*5 | |..................................................................| | PT-4216 Yes*4 Yes Yes Yes*5 Yes*5 | |..................................................................| | PT-4215 Yes*7 Yes Yes Yes*5 Yes*5 | |..................................................................| | PT-4214 No Yes No No Yes | |..................................................................| | PT-4213 No Yes Yes Yes*3 No | |..................................................................| | PT-4211 Yes*4 Yes Yes No No | |..................................................................| | PT-4210 No Yes No Yes*3 No | |..................................................................| NOTES: *1: First printer is typically connected to the parallel port. If MS-DOS mode will be used, only one printer may be selected for use at a time. Serial printers to be accessed via MS-DOS must be attached to the serial port on a single serial/parallel port card, not to an 8-way port. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB056 Pg027 *2: Indicates which interface standards are supported. I/S ser = industry standard serial, MBF ser = MAI Basic Four serial, Par = Centronics parallel. *3: Printers with MBF serial interface can also be used as slave printers with DT-4313, DT-4312 or DT-4310 terminals. *4: Use of PT-4216 and PT-4211 daisywheel printers under MS-DOS requires a PC application that supports Diablo 630 emulation. *5: Limited mnemonic support. These printers must be configured using the isp driver. *6: PT-4223 supports IBM PC graphics printer and Diablo 630 emulation under MS-DOS. *7: PT-4222, PT-4218, PT-4217 and PT-4215 support IBM PC graphics printer emulation under MS-DOS. 4.3.2.1 Printer Configuration There are two new directories released on the MAI 1800 7.2N release that are not present on 7.2 A, B, or C releases. These directories are: /etc/ptrtbl and /etc/ptrxlt These directories contain the Printer Definition Files (PDF's for mnemomic processing) and the printer character translation files respectively. To inform the system of the type of printer(s) you have connected, run the configure utility. When you select the option to configure a printer, the system will display a list of model numbers for all supported printers. The list is generated from the information contained in the /etc/printdef file. After configuring the printer, you will need to run the 'pparams' utility to define a form for the printer. A form is used to describe the paper margins, paper length, and the character translation file. There is a set of translation files released with the system in the /etc/ptrxlt directory. These are: ______________________________________________________________ | | | File Model # Comments | |--------------------------------------------------------------| | CI 4217B4 Supports the MBF character set. | | 4218B4 The serial line should be set | | for 8 data bits to utilize | | the full character set. | SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB056 Pg028 | | | DI 4215 Used for Diablo-compatible | | 4216 printers with a standard ASCII | | 96 print wheel. | | | | ES 4215 Used for Diablo-compatible | | 4216 printers with a European | | standard print wheel. | | | | WP 4215 Used for Diablo-compatible | | 4216 printers with a WP print wheel | | | | MV 4214 Supports the MBF international | | character set. The printer | | requires a special ROM | | (#165047-046) and 8 bit data. | | | | S7 isp 7 bit data. | | | | S8 isp 8 bit data required to utilize | | the full character set. | | | | WI 4213 Supports the MBF international | | 4213B4 character set. The printer | | requires a special ROM | | (#165031-081) and 8 bit data. | | | | 7G For MBF printers with ISO | | German character ROMs. For | | 7 bit data lines. | | | | 8G For MBF printers with ISO | | German character ROMs. For | | 8 bit data lines. | |______________________________________________________________| 5.0 CORRECTIONS TO 7.2P o EOS - Corrected a problem where the 8-way driver truncated on-going print jobs when a new job was submitted to the same port. - Corrected a problem where 'drestore' terminated without any error message before restoring the complete backup set. - Fixed the problem where the 'badtrk' command incorrectly handled alternate tracks. - Corrected a UPD problem where random system crashes when trying to free memory that had already been freed. - Corrected a problem where data was lost when printing to a parallel printer while security plug was being checked. - Corrected a problem where a mount form message is issued every time a printer is opened from BASIC. - Corrected a problem where the 'TS' mnemonic used in position 0,0 crashed the system. - Corrected a problem where once a write protect error was SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB056 Pg029 detected on a floppy it could not be cleared until the system was booted. - Corrected a problem where data overrun on the COM1 or COM2 ports could cause a system crash. - Corrected a problem where errors in initialization after a dump would cause another crash. Therefore, the data from the first dump would be wiped out. - Fixed a problem where parallel printer interrupts were lost during heavy system activity, causing the print job to start over. - The message requesting a floppy after a system crash was changed to "Insert dump diskette...". - Released new PDF's to solve extra form feed and @ positioning problems with Letter Quality Printers. - Fixed a problem where a terminal had a slow response time when configured on an 8-way and executing an INPUT with @ positioning. - Added retry logic for the SSN security device check. This alleviates system crashes with a crash code = 50 that were sometimes caused by a marginal (slightly malfunctioning) security device. Errors caused by a marginal device are now logged in the system error logger with this information: NMI Type: -132 A: 1, 2 or 3 B: 11181 C: hex value D: hex value A = 1 or 2 Used by engineering to determine where in the polling sequence the error occured. A = 3 This failure was caused by a mismatch between the serial number in the plug and the serial number in the configuration record. C: & D: These fields are used only when A = 3. This information is also used by engineering. If the security device fails the retry logic, the system will crash with a crash code = 50. A crash code = 50 indicates a bad or missing SSN device. - Fixed a problem where a terminal had a slow response time when configured on an 8-way and executing an EDIT. - The 4215 PDF was modified to remove an extra form feed. - Error 5 (parity error) was reported every time an error occurred in the tty driver. The proper error is now returned. - Fixed the 'TS' mnemonic on the system console. - Corrected a problem where the system would crash when out of memory on a CALL, ADDR, or ADDE from BASIC. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB056 Pg030 - The 'iconf' command now reports the correct system level for releases above "O". - Two kernel files were modified to enable EIT to process string files created on an MPx system. - Fixed a problem where the current record pointer was incorrectly incremented after an unsuccessful remove operation. - Fixed a problem where lpq created a bad temp file when the PID incremented to 6 digits. - Fixed a problem where BASIC was unable to open LP when the PID was 6 digits. o EBS - Corrected a problem where a corrupted program suspended or crashed when loaded. - Corrected a problem where subscripting a nested array doesn't access the correct element. - Corrected a problem where an error 41 was generated when calling a program with an uninitialized variable. - Corrected a problem where an error 41 was generated using the bsearch utility with certain boundary conditions. - Corrected a problem where an error 19 was generated in certain cases running BASIC. - Corrected an error 33 problem under BASIC. - Passing an unitialized variable to a CALLed program now works properly. - A SETESC-RETURN in a CALLed program now works properly. - Corrected a problem where 7.3 keywords were not allowed as variable names. - Corrected a problem where unpredictable results occurred when a data area larger than 32K existed in a RUN program, and an uninitialized string variable was passed to a CALLed program which then attempted to modify that variable. - TSK(0) now reports GA thru GF. - Pressing the escape key during execution of a BASIC directive that was being executed by the EXECUTE directive caused the next EXECUTEd directive to drop into console mode after completion. This now works properly. - Fixed a problem where BASIC suspended during a particular user application. - Fixed a problem where ON 65536 GOTO xxx,yyy caused BASIC to suspend. - Fixed a problem where 'bencrypt' got an error 19 SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB056 Pg031 when processing BASIC programs greater than 32K. o Commands - 'mcssave' with the ip= option nows works properly. - Corrected a problem where the 'move' command would change ownership in certain circumstances. - 'mcssave' and 'mcsrestore' now process files greater than 64K correctly. o EUT - Corrected a problem where an error 0 occurs using 'msave' with BASIC programs greater than 32K bytes in size. - Corrected a problem where using a filelist whose name is 8 characters suspends utilities. - Corrected a problem where removing a slave printer under 'configure' would suspend the 'configure' utility. - Corrected a problem where 'sformat' would not report errors encountered during diskette format verification. - Corrected a problem where 'frepair' suspended when processing large BASIC programs. - Corrected a problem where 'msave' did not log files which could not be saved due to being locked on another terminal. - ddisplay, finfo and fchange now display the correct information for files greater than 32K in size. - Fixed a problem where 'sformat' caused a system crash by not checking for device busy before initializing floppies. - Corrected a problem where 'msave' suspended when MBII was pressed at the 'modify tape label' prompt. - 'msave' and 'mrestore' now process files greater than 64K correctly. 6.0 ENHANCEMENTS TO 7.2P o EOS - A new PDF was added to allow the configuration of a serial and/or parallel PT-4222. 7.0 WARNINGS & CAUTIONS Following are some problem descriptions and helpful hints related to 7.2N, 7.2P, and 7.2R. 1. Problem: The "." located on the numeric keypad of the MAI 1800 system console will produce a with or without the NUM LOCK active. Workaround: The following can be used if the user doesn't SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB056 Pg032 need the : o admin>cd /etc/ttyxlt o admin>copy conout conin o admin>makettyxlate conin _________________________________________________________ | | | | 00 10 20 30 40 50 60 70 80 90 A0 B0 C0 D0 E0 F0 | | ______________________________________________________ | | 00 | 00 10 20 30 40 50 60 70 80 90 A0 B0 C0 D0 E0 F0 | | 01 | 01 11 21 31 41 51 61 71 81 91 A1 B1 C1 D1 E1 F1 | | 02 | 02 12 22 32 42 52 62 72 82 92 A2 B2 C2 D2 E2 F2 | | 03 | 03 13 23 33 43 53 63 73 83 93 A3 B3 C3 D3 E3 F3 | | 04 | 04 14 24 34 44 54 64 74 84 94 A4 B4 C4 D4 E4 F4 | | 05 | 05 15 25 35 45 55 65 75 85 95 A5 B5 C5 D5 E5 F5 | | 06 | 06 16 26 36 46 56 66 76 86 96 A6 B6 C6 D6 E6 F6 | | 07 | 07 17 27 37 47 57 67 77 87 97 A7 B7 C7 D7 E7 F7 | | 08 | 08 18 28 38 48 58 68 78 88 98 A8 B8 C8 D8 E8 F8 | | 09 | 09 19 29 39 49 59 69 79 89 99 A9 B9 C9 D9 E9 F9 | | 0A | 0A 1A 2A 3A 4A 5A 6A 7A 8A 9A AA BA CA DA EA FA | | 0B | 0B 1B 2B 3B 4B 5B 6B 7B 8B 9B AB BB CB DB EB FB | | 0C | 0C 1C 2C 3C 4C 5C 6C 7C 8C 9C AC BC CC DC EC FE | | 0D | 0D 1D 2D 3D 4D 5D 6D 7D 8D 9D AD BD CD DD ED FD | | 0E | 0E 1E 2E 3E 4E 5E 6E 7E 8E 9E AE BE CE DE EE FE | | 0F | 0F 1F 2F 3F 4F 5F 6F 7F 8F 9F AF BF CF DF EF FF | |________________________________________________________| o Replace position 7F with a 2E and save the modified translation table. o Modify T0 using the port configuration utility. Change input translation to 'conin'. o Shutdown the system and reboot. The '.' on the numeric keypad will now be a '.'. 2. Problem: Error 47 using 'bsearch' at statement 640 in program PSRCH. Workaround: Modify line 120 of /util/SREP to look like: 120 LET PTR=PTR+LENG; IF PTR+11>LEN(DATA$) THEN GOSUB 3000 8.0 HELPFUL HINTS 8.1 MAI 1800 BASIC Program Format The following information may be helpful to vendors or software developers when developing on an MAI 1800 system: The MAI 1800 BASIC program format is identical to that of the 2000/3000/4000, except that several fields are byte- reversed. These fields are byte-reversed to take advantage of the increased speed which the INTEL processor can fetch these fields during execution time. The first 16 bytes are as follows: Bytes Order Meaning ----- ------------- -------------------------------- 1-4 left-to-right This is the ASCII string "EBS1", which identifies the file as a SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB056 Pg033 BASIC program 5-8 native 4-byte field: length of the compiled code 9, 10 unused 11 control flags 12 unused 13-16 native 4-byte field: used by ENCRYPTED programs After the first 16 bytes come the DEF tables. There is a 2-byte field which gives the combined length of the entire DEF area, which is the length of this two-byte field plus the lengths of the two DEF tables. Then comes the first DEF table, which consists of a 2-byte length field, followed by the statement numbers of the program's DEF statements. Then comes the second DEF table, which consists of a 2-byte length field, followed by other information about the user-defined functions. Each of the 3 2-byte length fields mentioned above in connection with DEF tables is stored in native order, which on the MAI 1800, means right-to-left. For example, if the two DEF tables are empty (except for their length fields), the "DEF area" of the program will be 06 00 02 00 02 00. After the DEF area comes the compiled code. As with the MAI 2000, each statement has 2 2-byte fields: first the statement length, then the statement number. On the MAI 1800, as with the MAI 2000, the statement lengths are stored in left-to-right order. The reason is that if it were stored in right-to-left order, the leftmost byte of statements of length 254 or 255 module 256 would be OxFE or OxFF. This would have caused problems for the 1800 while executing the compiled code. The 2-byte statement number field is in native order. The compiled code ends with the usual "65535 END" statement, as it does on the 2000, which compiles on the 1800 as 00 05 FF FF 43. After this is a 6-byte unused field, just like on the 2000. After this begin the variable tables. However, since the variable tables must always begin on an even boundary, there may be an unused byte of "padding" before the variable tables if needed. The variable tables, 8 in all, are identical to those of the 2000, except that wherever there are 2-byte or 4-byte fields, these are in native order, which on the 1800 means left-to right. For example, the length field 00 00 00 06 on the 2000 would be 06 00 00 00 on 1800. PROGRAM FILE FORMAT OVERVIEW Preceding and following each BASIC program is a header that contains information about the program, such as length, DEF tables, Auto-End, flags etc. The following is a description of the SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB056 Pg034 33 bytes that are fixed in the format. FORMAT BYTES CONTENTS 0 - 3 - Business BASIC revision level in 7-bit ASCII 4 - 7 - Length of program compiled code 8 - 11 - Miscellaneous flags 12 - 15 - Miscellaneous for encrypted programs 16 - 17 - 6: length of DEF area 18 - 19 - 2: length of DEF statement number table DEF statement number table goes here 20 - 21 - 2: length of DEF id table DEF id table goes here Compiled code goes here, between the DEF tables and the 65535 END statement. 22 - 23 - 5: length of 65535 END statement 24 - 25 - 65535 26 - hex 43: opcode for END 27 - 28 - 6: length of hash field 29 - 32 - hash field (not used) Variable tables go here There are two DEF tables. The DEF statement number table consists of a two-byte length field followed by two-byte entries which are statement numbers corresponding to the user-defined functions in the program. The DEF id table consists of a two-byte length field followed by id entries which correspond to the user-defined functions in the program. An id entry consists of a one-byte length field, followed by a flag which is 1 if the function has an associated DEF statement, or a flag which is 3 if the function does not, followed by the id (function name) itself. VARIABLE One of the key differences between Level 4 and TABLES Level 7 BASIC is in the use of variables. Level 4 BASIC uses a coding system that identifies the variable precisely. In reading the compiled format, you could interpret the variable labels. For example, a compiled statement that referenced "E101" indicated a numeric variable called "A". Level 7 compiled BASIC uses the same variable labels, but they no longer identify the variable. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB056 Pg035 The label is used only to indicate the variable type and the order in which the variables were created. E0001 is the first numeric variable; EA0001 is the first string/numeric array variable. This enhancement is largely transparent and presents no compatibility problems unless you are using the CPL and LST functions on statements from a program other than the main program you are running. The system has no way of identifying the variable names from the compiled code labels unless you provide the variable table for that program. CPL/LST To allow you to accomplish the task of compiling and listing statments from other program files, the CPL and LST functions may take a second parameter. You may use the functions with only the program statement, but the variables used are from the main program. The second parameter identifies the variables explicitly, and the variables used in the statement being compiled must be in the ID table. Four errors are provided to identify problems: ERROR 68 is issued when the ID table is not in the correct format. ERROR 69 is issued if there is no variable table, or the variables in the statement being compiled are not in the table. Error 70 is issued if the third argument is not an active variable. Error 71 is issued if the third argument is the wrong length. These are explained more fully in Chapter 9. When you want to use the listed form of a compiled statement, the variable name is taken directly from the ID table. How the variable is described in the ID table determines how it is listed. FORMAT FOR There are eight variable tables. The tables VARIABLE TABLES must start on an even boundary, so if the hash field ends on an odd boundary, a 1-byte hole exists between the end of the hash field and the first variable table. Each variable table begins with a 4-byte field which gives the length of the entire table. The variable tables give information about the variables in the current BASIC environment. This information is kept in a form which: 1. Allows fast access to variables when a BASIC program is executing or LISTing. 2. Allows a fast LOAD or RUN of another BASIC program, when the variables in the incoming BASIC program must be merged with the variables in the present environment. The eight variable tables are: SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB056 Pg036 1. Numeric id table: contains the names of numeric variables as entered by the user. There are no delimiters or length fields (except the length field of the entire table). The variable names are stored in ASCII form, one right after another. 2. Numeric sort table: lexicographically sorts the numeric variables. This inforamtion is useful because when a BASIC program is LOADed or RUN, the variables in the incoming program number must be merged with the variables in the current environment. Sorting greatly speeds up LOADs and RUNs. 3. Numberic offset table: contains two-byte fields which are used as offsets into the numeric id table to determine where one variable id ends and the next begins. 4. String id table: similar to numeric id table, used for strings and numeric arrays. 5. String sort table: similar to numeric sort table, used for strings and numeric arrays. 6. String offset table: similar to numeric offset table, used for strings and numeric arrays. 7. Numeric location table: gives location of the data of a numeric BASIC variable. 8. String location table: similar to numeric location table, used for strings and numeric arrays. 9.0 RELATED DOCUMENTATION For more detailed information regarding BOSS/IX and/or the MAI 1800 system, refer to the following documents: o MAI 1800 User Guide - M6203A o BOSS/IX 7.2 User Reference - M6210A o BOSS/IX 7.2 Technical Reference - M6224A o MAI 1800 Service Manual - M8112A o MAI 1800 Software Announcement #152 ORIGINATOR: D. Wenzel SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB056 Pg037 FIB 00057 02/08/89 *** ERROR 17 on Multi-keyed files [ WPSF 514 ] *** Symptom: If you create a composite DUPKEY or ALTKEY using a certain syntax, you will be able to create the multi-keyed file, but you get an error 17 trying to read on the ALTKEY or DUPKEY. Cause 1: Create a multi-keyed file with the following syntax: MULTI "FILE",100,FMT="F1#=S8 F2#=N4 CF1#=F1#:2+F2# ALTKEY(OR DUPKEY)" ^^ || The system accepts this but on a read to the file on KEY=CF1# you will get error 17's (note the arrows point out the problem syntax). Workaround 1: Use the following syntax to create a multi-keyed file: MULTI "FILE",100,FMT="F1#=S8 F2#=N4 CF1#=F1#(1):2+F2# ALTKEY(OR DUPKEY)" ^^^^^ ||||| The arrows point out the syntax that will work on the BOSS/IX (2000/2500/3000/4000) system 7.3A and above. Cause 2: Create a new multi-keyed file using the FMTINFO of an existing multi- keyed file which used the correct syntax from above when it was created, then read on the DUPKEY or ALTKEY and you will get an error 17. This is because the FMTINFO command can return the problem syntax in a multi-keyed file format statement. Workaround 2: Do not use the FMTINFO of an existing file to create new multi-keyed files. Store the correct format information in a direct file with the key as the file name, then when you want to create the new file you can retrieve the correct format information. ORIGINATOR: Bill Poling SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB057 Pg001 FIB 00058 02/08/89 *** BASIC programs running slow [ WPSF 512 ] *** PROBLEM: When you use global search and replace (bsearch) or program renumber (brenumber) on a program the "slow" bit in the program header gets turned on and the program will run slower. CAUSE: The system stores BASIC programs on disk in a format called "quickie code". This code has offsets in it which allow program branches to jump directly to the section of code which is specified by the branch. This is considered "fast" mode and is represented by the 11th bit in the program header being hex 01 ("slow" mode would be hex 00). After a global search and replace or renumber the "quickie code" can no longer rely on the offsets to be correct; therefore, the program runs in "slow" mode meaning on a branch the program must search the statement numbers to find the section of code to branch to. SOLUTION: Make the following changes to bsearch and brenumber: First make backups of the files PSRCH and RENUM: 1. From the ADMIN> prompt type: ADMIN>copy /util/PSRCH /util/PSRCH.old ADMIN>copy /util/RENUM /util/RENUM.old For bsearch: 1. Load "/util/PSRCH" 2. Statement 644 is: >644 IF COUNT>0 THEN RENAME SCRATCH$,FULLNAME$ ELSE ERASE SCRATCH$,ERR=0645; REM "temp becomes real thing Change 644 to: >644 IF COUNT>0 THEN LIST PROGRAM SCRATCH$, SCRATCH$+"s"; MAKE PROGRAM SCRATCH$+"s",FULLNAME$; ERASE SCRATCH$+"s" FI; ERASE SCRATCH$,ERR=0645; REM "temp becomes real thing 3. Save program For brenumber: 1. Load "/util/RENUM" 2. Statement 1388 is: >1388 RENAME SCRATCH$,FILENAME$ Change to: >1388 LIST PROGRAM SCRATCH$,SCRATCH$+"s"; MAKE PROGRAM SCRATCH$+"s",FILENAME$; SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB058 Pg001 ERASE SCRATCH$;ERASE SCRATCH$+"s" 3. Save program CAUTION: These fixes are for 7.3A and above only. These are quick fixes and have not been tested under all circumstances. These changes cause the utilities to load and save the program changed by global search and replace or brenumber. Loading and saving the program resets the 11th bit and allows it to run in "fast" mode. If you are on 7.2 or below you can load any programs altered by the utilities and save them to reset the 11th bit to "fast" mode. Also, it may save you time if you are going to run global search and replace several times on the same prorgrams to not make the fixes mentioned above, but once you have finished running global search and replace load all the programs you have altered and save them. This will reset the 11th bit to fast mode and save the time it would take to save the program multiple times. ORIGINATOR: Bill Poling SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB058 Pg002 FIB 00059 02/08/89 *** Terminal/System Hangs 7.2 O.S. [ WPSF 435 ] *** Problem: A terminal(s) appears to be hung or if no other terminals are logged on, the system appears to be hung. You will most likely find this problem when you log off then cannot log back on again. The terminals which are active will continue working until a logoff takes place at which point the terminal will 'hang'. Cause: The process id 1 is suspended on a 3000 or missing on a 2000. There is a small 'window' in the process handling in which this process suspends. Usually, the suspend is a result of a port that is logged-off flooding the system with escapes. To verify: On an active terminal, do a 'ps -a'. Look for PID 1. On a 2000, it will not exist. On a 3000, the status will be SSPD. Workaround: Upgrade to 7.3 or 7.4. ORIGINATOR: P. Thatcher SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB059 Pg001 FIB 00060 02/08/89 *** Crash Code 21/Bus Errs on 7.3 O.S. [ WPSF 436 ] *** Problem: The system crashes with a crash code 21 or bus error. The first entry in the dump error log is a 0:16 or a 0:0 which can be found using the dmplog command. Usually this will occur just after a print job has finished printing and, to date, on systems that (1) have a maximum configuration with more than one printer or (2) are over configured with one printer for the amount of memory in the system. Here are some examples of configurations on systems that have reported this problem: 3000 -- 2MB Memory, 9 users/terminals, 2 printers 2000 -- 1MB Memory, 7 users/terminals, 1 printer Cause: The memory is corrupted. The system goes to 'free memory' which has already been accidentally freed. Also during memory compaction the system detects 2 adjacent free sections because one of the free sections had already been freed. The bus error is caused by 2 processes accidentally sharing the same memory. Workaround: Upgrade to 7.4 Do NOT configure more user/terminals than the system has the memory to support. (This might only cut down the chances of the crash, but the crash could still occur.) ORIGINATOR: P. Thatcher SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB060 Pg001 FIB 00061 04/18/89 *** Installing COMM products on SPx systems [WPS 528] *** QUESTION: In what order do I install X.25, TBC, B32, ENT and FTF on the 2000, 3000, and the 4000 systems? ANSWER: Install these products in the following order: 1. FTF - Contains Lbossix. 2. ENT - Contains Lbossix and the ENT (LAN) driver. 3. TBC - Contains Bbossix and the drivers for TBC and ENT. 4. X25 - Contains Xbossix and the drivers for X25 and ENT. 5. B32 - Contains Bbossix and the drivers for B32, TBC and ENT. NOTE - Remember to install the new OS of the last product onto the kernel by entering '1' during final install- ation step. You should NOT install the TBC or B32 OS (Bbossix) onto the kernel if you plan to primarily use X25. You should copy Bbossix onto the boot and ATL-LOAD when you want to use it. You are restricted by hardware of executing only 1 of the last 3 products (TBC, X25 and B32) at a time, since they require the same communications port to run. ORIGINATOR: Tony Tiangco SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB061 Pg001 FIB 00062 04/18/89 *** PS 3.1A loop in /PS/MSDISPLAY [WPS 527] *** PROBLEM: The program /PS/MSDISPLAY will go into a loop if the MENU NAME is being displayed in a menu header on the SPx system. The terminal appears to hang, and an ESCAPE must be pressed to continue. SOLUTION: To correct this problem, please make the following code changes to /PS/MSDISPLAY: LOAD "/PS/MSDISPLAY" OLD: 5135 LET OUT$=OUT$+THEMENU$ NEW: 5135 LET OUT$=OUT$+MENUNAME$ OLD: 5138 LET PTR=PTR+LEN(THEMENU$)-1 NEW: 5138 LET PTR=PTR+LEN(MENUNAME$)-1 SAVE "/PS/MSDISPLAY" FIX: This problem will be corrected in the PS 3.3A release. ORIGINATOR: Jackie Shea SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB062 Pg001 FIB 00063 04/18/89 *** Error 11's on Multi-Keyed files [ WPSF 522 ] *** PROBLEM: Error 11's will occur on a write to a record when you have not included all the key field data in a previous write to the record. SOLUTION: Always specify all key fields on a write statement (even though the fields may be zeros, blanks, or nulls). EXAMPLE: For these examples I will create a Multi-keyed file. First showing write statements which will create the error then the way to avoid the error 11's. Create the Multi-keyed file: 100 MULTI "MK1",100,FMT="MAL#=S8 PRIMARY MAL1#=N4 MAL2#=N4 MALC1#=MAL(1):6+MAL1#+MAL2#+MAL#(7) ALTKEY" 110 OPEN(1) "MK1" This code will cause an error 11 on the next write to key "01100001": 120 WRITE(1)"01100001",1250 0R 120 WRITE(1)MAL#="01100001",MAL1#=1250 OR 120 A$="01100001";B=1250;WRITE(1)A$,B To avoid error 11's use this: 120 WRITE(1)"01100001",1250,0 OR 120 WRITE(1)MAL#="01100001",MAL1#=1250,MAL2#=0 OR 120 A$="01100001";B=1250;C$=0;WRITE(1)A$,B,C ORIGINATOR: B. Poling SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB063 Pg001 FIB 00064 04/18/89 *** Printer VFU Set by Spooler Even when not Spooled [ WPSF 524 ] *** DESCRIPTION: If a printer is set to spooling off, it will still set the printer's VFU according to the form defined for that printer in the printer defaults. If no form is specified in printer defaults, it will be set to "stanrd" form. ALTERNATIVE: Open the printers with the "OPTS" option which allows you to set VFU functions as desired. See the Business BASIC Manual #M6262 for appropriate use of the "OPTS" snytax. Or, modify "pparams' to permanently change the form definition. ORIGINATOR: B. Poling SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB064 Pg001 FIB 00065 04/27/89 *** 1800 System Error Log information *** Information for interpretation of the 1800 Syustem Error Log is located in MAI Basic Four publication M6210A, BOSS/IX 7.2 User Reference Manual. The 1800 System info is located in Appendix F. ORIGINATOR: H. Mitchell SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB065 Pg001 FIB 00066 07/27/89 *** TBC - ERR 11 Displaying Task Prefixes - 7.4A/B [ WPSF 449-16 ] *** PROBLEM: An err 11 may occur when displaying/maintaining your task prefix in TBC on 7.4A/B CAUSE: This problem can occur when upgrading from 7.3 to 7.4. The file that contains your task prefix uses the defaults of T0, T1,..., T9, TA, etc. instead of T0, T1,...,T9, T10, etc. SOLUTION: Execute the following steps: 1. Delete the /etc/comm/NODEPREFIX file. 2. Select the 'BCOM prefix (BCOMPFX) maintenance' option from the TBC utility menu. This will recreate the NODEPREFIX file. ORIGINATOR: T. Tiangco SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB066 Pg001 FIB 00067 07/27/89 *** 7.4A Additional Information [ WPSF 449-17 ] *** 1. If you have more memory on your 7.4 system than the Configuration record allows, of if your drive 0 is larger than your Configuration record allows, the system may not boot to the root partition. It may crash, or may not allow you to mount the root partition. 2. If you take your printer offline (and it has XON/XOFF flow control), you will lose data. It will skip either part or all of a page of data. WORKAROUND: Use DTR floe control, or restart the print job at the page before it lost data. 3. When upgrading a 2000 to 7.4 using floppy, you must use either option 'A' or option 'B'. You cannot root directly to the boot partition then upgrade. The floppy diskette upgrade requires booting from the media. NOTE: You should not follow the installation procedures outlined in the Technical Reference Manual, you should follow the 7.4B Installation Instructions. 4. When trying to retire a bad block, through the frepair utility, you can only retire bad blocks of the first four disks. So, if you have a bad block on your fifth drive (logical drive four) you cannot retire the bad block. WORKAROUND: Make 'dummy' areas or reformat the disk. 5. When performing an Intersystem transfer, with BOSS/IX on the receiving system, the growth extents for all the files will be changed to 1. WORKAROUND: Change the fields manually through 'fchange'. A program is available through Field Product Support (FPS) and the regions that will change the growth extents for you. Either call your region for a copy or contact FPS. 6. When running 'frepair' on a multi-key file with composite fields, the file will show an error and will show that it was repaired, but if you re-enter . 'frepair' using the same file it will still show an error. The file is allright, 'frepair' does not recognize the composite field as being correct. 7. When running the 'trestore' utility on multiple 1/2 inch tape backup, the data on the second tape may be inaccessable. This occurrs because the read buffer on the MTS controller is only 32KB, and if the saveset name is larger than 32KB, it cannot read it. It will save the data because the write buffer holds up to 64KB. WORKAROUND: All multiple 1/2 inch tape backups need to be verified using tcompare. If the problem exists, split the backup across multiple tapes. 8. The MAI 4000 may intermittantly crash at power up in the self-test with the message '68020 EIA TRANSMISSION PARITY' failure. Then once it is rebooted it is fine. The system is fine and should run without error. This has been corrected in 7.4B. 9. There is a 132 column limitation on the following printers: PT-4201, PT-4203, PT-4208, PT-4210, PT-4212, PT-4213 (and B4), SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB067 Pg001 PT-4214, PT-4217, PT-4218, PT-4220. WORKAROUND: The regions have a tape of optional PDFs to fix this problem. 10. On the MAI 2000, if you try to use the Dual Board Winchester Disk controller to run more than one drive, the system will hang. WORKAROUND: Upgrade to 7.4B. ORIGINATOR: J. Shreve SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB067 Pg002 FIB 00068 07/27/89 *** Err -95 Starting Communications on 7.4A/B [ WPSF 449-19 ] *** PROBLEM: An error -95 may occur in 27xx/37xx when starting communications on 7.4A/B. CAUSE: The conf settings for lanbuffers, sockets and desockets are below the minimum. The minimum settings are: lanbuffers=10, sockets=5, dsockets=10 SOLUTION: Execute the following steps: 1. Verify that your conf parameters meet the minimum settings by entering 'vconf -os' at the admin prompt. This will display your current boot conf parameters. admin>vconf -os 2. If they don't meet the minimum settings, increase them using the 'vconf' command. admin>mount /dev/boot/mnt admin>vconf /mnt/etc/conf -save -lanbuffers=10 -sockets=5 -dsockets=10 admin>unmount /mnt 3. Re-boot your system to enable the new conf settings. ORIGINATOR: T. Tiangco SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB068 Pg001 FIB 00069 08/02/91 *** Known Dumps and Solutions [ WPSF 557R ] *** Product: MAI 2000/2500/3000/4000 ** PRELIMINARY ** Author: Chuck Zimmerman Issue: Known Dumps and Solutions Type: Informational Purpose: To solve SPx dumps in the field as soon as possible without having to send the dump tape into corporate. This procedure saves valuable time in determining the cause of most SPx system dumps. In order to read an SPx dump tape the operating system level must be 7.3A or greater. In most cases, the system errorlog that resides on tape reveals the reason why the system dumped. The command to print the errorlog is: ADMIN> dmplog /dev/cs > /dev/ The last eight errors recorded are contained in the errorlog report. The errors are listed in order from the most recent error (usually the error that caused the dump) to the oldest. On some dumps, errors that occur prior to the most recent error indicate a pattern that may be developing (ie. parity errors on a specific port, etc). When a dump is caused by Excessive Interrupts, other entries in the log may indicate the port(s) causing the problem. The other entries will have a major number of "10" which indicates a 4/way or 8/way port error. Each entry shows the date and time that the error was logged. When the first entry indicates Excessive Interrupts, look at the date and time that it was recorded and inspect other entries for similiar times. If the entries were logged near the same time, it may indicate the problem port(s). For more information on determining the exact terminal, see note 3. The following are known dumps and solutions. Entries where the SYSTEM field is shown as "3000*", indcates the MAI 2500/3000/4000 systems. (continued on next page) SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB069 Pg001 O/S SYSTEM MAJ:MIN T FIX CAUSE ======================================================================. Any 2000 0:7 See Note 1 Parity Error on Memory Any 3000* 0:23 See Note 2 Parity Error on Memory Any 3000* 0:24 See Note 2 Parity Error on Memory Any 2000 0:18 Diagnostics/CMB Hardware/Illegal Instr. Any 3000* 0:18 Diagnostics/CMB Hardware/Illegal Instr. Any Any 0:0 Diagnostics/CMB Trap/Bus Error Any Any 0:1 Diagnostics/CMB Trap/Illegal Instruct. Any Any 0:4 Not Applicable Trap/Power Failure Any Any 0:5 Diagnostics/CMB Trap/System Call Any Any 0:10 Upgrade OS/CMB Trap/Memory Management Any Any 0:11 Diagnostics/CMB Trap/Odd Address Any Any 0:30 Expansion Unit Trap/Power Failure Any Any 2:0 Not Applicable 1/2 Inch Streamer Any Any 6:0 N/A Applicable Cartridge Tape Any Any 8:-- See Note 3 Printer Filter Any Any 9:-- See Note 4 CMB Any Any 10:-- See Note 5 Parity /DMA Arbitration Any Any 14:-- See Note 6 Disk/Controller Problem 7.2 3000* 0:0 20CFC Change to DTR Flow Control Problem 7.2 3000* 0:16 1C4E8 Upgrade 7.5B*22 Wrting Integer to Short 7.3A 2000 0:16 1CCDC Upgrade 7.5B*22 UPD Free 7.3A 3000* 0:16 1E81A Upgrade 7.5B*22 UPD Free 7.3A 2000* 0:11 35D28 Upgrade 7.5B*22 UPD Free 7.4A 2000 N/A 1D2AA Upgrade 7.5B*22 Stty Write 7.4A 2000 N/A 1E436 Upgrade 7.5B*22 Stty Write 7.4A 3000* N/A 205DA Upgrade 7.5B*22 Stty Write 7.4A 3000* N/A 20642 Upgrade 7.5B*22 Stty Write 7.4A 3000* 0:16 1A894 Upgrade 7.5B*22 Memory Compaction 7.4A 3000* 0:16 1E234 Upgrade 7.5B*22 System Stack Overflow 7.4A 2000 0:16 1BF92 Upgrade 7.5B*22 System Stack Overflow 7.4B 3000* 0:16 1E2B8 Upgrade 7.5B*22 Excessive Interrupts 7.4B 2000 0:16 1C020 Upgrade 7.5B*22 Excessive Interrupts 7.4B 3000* 0:16 7B7A Upgrade 7.5B*22 Excessive Interrupts 7.4B 3000* 0:16 182B8 Upgrade 7.5B*22 Excessive Interrupts 7.5B 3000* 0:16 1E5DO Upgrade 7.5B*22 Excessive Interrupts 7.5B 3000* 0:16 1E608 Upgrade 7.5B*22 Excessive Interrupts Note 1: To determine which memory board had the parity error, use the following chart to find the address range (in hex) in which the 'T' value is located. BOARD refers to 256 KB increments of memory (i.e. 1st addressable board, 2nd addressable, ...). BOARD ADDRESS RANGE BOARD ADDRESS RANGE ============================================================ 1 00000 -> 3FFFF 4 C0000 -> FFFFF 2 40000 -> 7FFFF 5 100000 -> 13FFFF 3 30000 -> BFFFF 6 140000 -> 17FFFF SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB069 Pg002 Note 2: To determine which memory board had the parity error, use the following chart to find the address range (in hex) in which the 'T' value is located. MB refers to the MegaByte of memory in which the parity error occurred. If the system uses 4 MB boards and the error occurred in the third (3rd) MB of memory, the board to replace would be the first (1st) 4 MB board. BOARD ADDRESS RANGE BOARD ADDRESS RANGE =============================================================== 1 00000 -> FFFFF 9 800000 -> 8FFFFF 2 100000 -> 1FFFFF 10 900000 -> 9FFFFF 3 200000 -> 2FFFFF 11 A00000 -> AFFFFF 4 300000 -> 3FFFFF 12 B00000 -> BFFFFF 5 400000 -> 4FFFFF 13 C00000 -> CFFFFF 6 500000 -> 5FFFFF 14 D00000 -> DFFFFF 7 600000 -> 6FFFFF 15 E00000 -> EFFFFF 8 700000 -> 7FFFFF 16 F00000 -> FFFFFF Note 3: The minor number in the error log entry denotes the printer or printer port that is generating errors. To determine the port, use the chart below. MINOR DESCRIPTION MINOR DESCRIPTION ============================================================== . 0 CMB Parallel port 3 1st port on 1st 8/way 1 CMB Serial port A 4 2nd port on 1st 8/way 2 CMB Serial port B 5 and so on . Note 4: The minor number in the error log entry denotes the port on the CMB that is generating the error. To determine the port, use the chart below. MINOR DESCRIPTION MINOR DESCRIPTION =============================================================== 0 CMB Serial port A 2 CMB Parallel port 1 CMB Serial port B Note 5: When entries have a major number of "10", it usually denotes parity, cabling, excessive interrupts and/or framing errors. To determine the actual port/device that is generating the error(s), look at the minor number. The first port on the first 4/way or 8/way is "0", the second is "1" and so on. If the controller is an 8/way, the value of 'A' is 8 in the error log entry. If the value of 'A' is 4, the controller is a 4/way. The table below gives a few examples. MINOR DESCRIPTION MINOR DESCRIPTION =============================================================== 0 Port 1 on 1st 8/way 8 Port 1 on 2nd 8/way 1 Port 2 on 1st 8/way . . 15 Port 8 on 2nd 8/way 7 Port 8 on 1st 8/way 30 Port 7 on 4th 8/way Note 6: When entries have a major number of "14", it denotes disk or controller problems. The 'A' value is the block number on the the disk where the error was received. To find the disk drive or partition that contains the bad block, use the chart below. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB069 Pg003 MINOR DRIVE MINOR DRIVE ============================================================== . 0 - 31 0 128 - 159 4 32 - 63 1 160 - 191 5 64 - 95 2 192 - 223 6 96 - 127 3 224 - 255 7 *** Before sending in a system dump tape, process the dump tape using this field bulletin. If you are unable to determine why the system dumped by reviewing the known system dumps, then send in the dump tape with the error log print out. In addition, a Dump Report Form IS REQUIRED. *** IF THE DUMP REPORT FORM IS NOT COMPLETELY FILLED OUT WITH ALL NECESSARY INFORMATION, THE DUMP TAPE WILL NOT BE PROCESSED AND THE TAPE RETURNED TO THE NEAREST CSM LOCATION. ORIGINATOR: Chuck Zimmerman SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB069 Pg004 FIB 00070 02/22/90 *** 7.4B Warnings & Cautions [ WPSF 573 & -1 ] *** PROBLEM: If a printer is taken off line, it may lose up to a page of data. WORKAROUND: Stop the print job in the queue before taking the printer off-line, then restart it when it is on-line. If the print job cannot be stopped before it goes off-line, restart the print job on the page previous to the last page printed. Fixed in 7.5B. PROBLEM: When starting or restarting a print job on a specified page, the job may start printing on the page after the one indicated. WORKAROUND: Start the print job on the page previous to the one de- sired. Fixed in 7.5B. PROBLEM: When upgrading from 7.4A to 7.4B, the Installation Instructions tell you to first put down the Configuration Record, then perform the 'osupdate', skipping the OPTION A or B when booted from tape. If you follow this procedure, you will not be able to perform the 'osupdate', and it will not allow you to mount the root partition. The proper way to upgrade from 7.4A to 7.4B is to first perform the 'osupdate' then install the Configuration Record. WORKAROUND: This has been re-written in the 7.5B Installation Instructions. PROBLEM: There is a 132 column limitation on the following printers: PT-4201, PT-4203, PT-4208, PT-4210, PT-4212, PT-4213 (and B4), PT-4214, PT-4217, PT-4218, and PT-4220. The patch tape of PDF's is available to fix this problem on 7.4A/B WORKAROUND: This has been fixed in 7.5B. PROBLEM: On a Modem or MUX port, a '%err' can appear in the ps -a and the port may hang. This is a result of the start process checking the port and an error being received or the protocol/set-up on the port/modem/ terminal is incorrect. WORKAROUND: No workaround is available for this issue. The set-up and terminal errors should be checked. PROBLEM: When performing a tape compare using a 120 MB MCS tape drive, the compare may fail with an error, or message 'File does not Compare', but when you restore the file, it restores without incident and is intact. WORKAROUND: Try restoring the file, or a few of the files it failed on, to another directory. Then compare the new and old files. If they compare, the backup is fine. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB070 Pg001 PROBLEM: The message "WINCHESTER DISK ON LOW MEMORY SAVE" will appear on almost any crash dump, but does not in- dicate any specific problem. If this message appears during a crash, nothing can be determined from this message alone, we will need a crash code or a 'dmplog' to analyze the problem without seeing the whole dump. WORKAROUND: None. PROBLEM: 'bmerge' will not work after installing PS 3.3A. An error message will display "malformed libraries". WORKAROUND: Fixed in 7.5B. ORIGINATOR: Julia Shreve/Dan Arteritano SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB070 Pg002 FIB 00071 11/06/89 *** 7.5B Software Announcement [ WPSS 167 ] *** Level 7.5B of BOSS/IX is now available. It is the recommended Operating System for MAI 2000, MAI 2500, MAI 3000 and MAI 4000 systems. This Software Announcement contains general information about the level 7.5B BOSS/IX Operating System. Installation and upgrade procedures are fully documented in this announcement. Also, this document has sections on enhancements and corrections to BOSS/IX, approximating memory requirements, memory usage, and a list of new documents available for BOSS/IX. WARNING: When installing this release on a 3000 system running on a release previous to 7.3, the system serial number MUST be reinstalled using the new 2000/2500/3000/4000 SSN program. DO NOT attempt to upgrade a 3000 system without reinstalling the system serial number using the new 2000/2500/3000/4000 SSN program. WARNING: In order to install the systems properly, the 7.5B 2000 O.S. tape must be used to install a MAI 2000 system, and the 7.5B 2500/3000/4000 O.S. tape must be used to install the MAI 2500, MAI 3000, and MAI 4000 systems. WARNING: With BB86, BASIC programs are not backwards compatible. You must use the conversion facilities to take the programs backwards to a 7.2 or prior release. WARNING: MTS requires a 4.3 boot prom on the MAI 2000, (revision 903441 BE). WARNING: If a SCSI Disk is to be installed, CMB 903631-004 is required. It is recommended that you read this document before installing level 7.5B. For information on how to order level 7.5B refer to Marketing Announcement 757 for the United States or 477 for International. NOTE: Throughout this document the references to '7.2' include 7.2A/B/C/D/D1, and references to '7.4' include 7.4A/B. NOTE: Effective with this release, a Diagnostic Products License Agreement must be signed prior to the installation of diagnostics. See section 2.1 for instructions. Copyright 1989 MAI Basic Four, Inc. All rights reserved. TABLE OF CONTENTS 1.0 OVERVIEW 2.0 INSTALLATION AND UPGRADE OF THE OPERATION SYSTEM, SOFTWARE AND DIAGNOSTICS 2.1 INSTALLING DIAGNOSTICS ON THE DISK 2.1.1 INTRODUCTION 2.1.2 DISK DIAGNOSTIC INSTALLATION PROCEDURE 2.1.3 DELETING DIAGNOSTICS 2.1.4 LOADING DISK DIAGNOSTICS SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB071 Pg001 2.2 INSTALLATION OF THE OPERATING SYSTEM 2.3 UPGRADING 2.4 PRODUCT INSTALLATION/UPGRADE - GENERAL 2.4.1 ECC "C" COMPILER 2.4.2 MAGNET (ENT) AND FILE TRANSFER FACILITY (FTF) 2.4.3 27xx/37xx BATCH EMULATION 2.4.4 ASYNCHRONOUS TRANSPORT PACKAGE (ATP) 2.4.5 3270 BISYNCHRONOUS 2.5 PRODUCT INSTALLATION/UPGRADE - FROM 7.1 or 7.2 2.6 SYSTEM CONFIGURATION RECORD 2.6.1 7.5B CONFIGURATION RECORD REQUEST SHEET 3.0 LEVEL 7.5B BOSS/IX ENHANCEMENTS 3.1 OPERATING SYSTEM (EOS) 3.2 UTILITIES (EUT) 3.3 BASIC (EBS) 3.4 3270 BISYNC SUPPORT 3.5 MAGNET/FTF 3.6 TBC 3.7 ATP 4.0 MEMORY REQUIREMENTS AND OPERATING PARAMETERS 4.1 APPROXIMATING A SYSTEM'S MEMORY REQUIREMENT 4.2 RECOMMENDED VALUES FOR "vconf" 4.2.1 RECOMMENDED VALUES FOR "vconf" BOSS/IX MODEL 2000 PARAMETERS 4.2.2 RECOMMENDED VALUES FOR "vconf" BOSS/IX MODEL 2500, 3000 AND 4000 PARAMETERS 5.0 MEMORY USAGE 5.1 CALCULATING A SYSTEM'S MEMORY REQUIREMENT 5.1.1 EXAMPLE OF HOW TO CALCULATE A SYSTEM'S MEMORY REQUIREMENT FOR MODEL 3000 5.2 CALCULATING BOSS/IX TABLE SPACE AND DYNAMIC WORK SPACE 6.0 NEW AND UPDATED MANUALS FOR LEVEL 7.5B 7.0 HELPFUL HINTS 7.1 FOUR-WAY AND EIGHT-WAY CONFIGURATION 7.2 MEMORY CONFIGURATION 7.3 DISK CONFIGURATION 1.0 OVERVIEW The level 7.5B Release contains the following enhancements/features:. o BB90 Support o GCR 1/2" Tape Drive Support o SCSI Hard Disk Support o Operating System Corrections o Utility Corrections o BASIC Corrections SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB071 Pg002 o 3270 Bisync Support o MAGNET Enhancements o TBC Enhancements o ATP Enhancements 2.0 INSTALLATION AND UPGRADE OF THE OPERATING SYSTEM, SOFTWARE AND DIAGNOSTICS The following are the steps to install or upgrade the Operating System, customer's software and system diagnostics. Before installing or upgrading the system it is recommended that you read these instructions completely. NOTE: To do an ALTERNATE LOAD: On a 2000 system, enter ^C at the reboot prompt. On a 2500/3000/4000 system, enter 2 at the bootstrap menu. 2.1 INSTALLING DIAGNOSTICS ON THE DISK NOTE: If the customer has not signed a Diagnostic Products License Agreement, a file by file back-up must be performed and the diagnostics removed. Please refer to Section 2.1.3. 2.1.1 INTRODUCTION Diagnostic programs for your system may be contained on the system fixed disk. Your disk should have diagnostics installed in order to test the tape subsystem included with your system. The purpose of these tape diagnostics is to troubleshoot and test your tape subsystem when you cannot load diagnostics from the tape subsystem. You may optionally install all of the diagnostics programs on your disk. The system diagnostics are contained on a dedicated diagnostic partition. This diagnostic partition is inaccessible to user programs and is actually beyond the reach of the user disk area. For this reason, the diagnostic programs cannot be accessed by the file system, yet they are maintained by a Diagnostic Executive. If your system will not boot diagnostics from disk, and the O.S. is already installed, the file system must first be backed up. Once backed up, a diagnostic partition can be reserved. Once the diagnostic partition is reserved, diagnostics can be installed from the same bootable diagnostic tape. Afterwards the file system must be restored. Use the following procedure to install the diagnostics on your fixed disk. 2.1.2 DISK DIAGNOSTIC INSTALLATION PROCEDURE STEP 1: Backup your disk If your file system is already installed on the disk you must do a complete file by file backup. If your file system has not been installed yet, install your diagnostics first and then install the file system. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB071 Pg003 STEP 2: Boot diagnostics from tape Install the diagnostic tape. Do an alternate load. For the boot device enter 'cs', for MCS or 'ts', for MTS. For the system file enter . STEP 3: Enable service mode When the EXEC is loaded, it will auto-size the system and display the program prompt: Any Exec commands can be entered at this time. To begin the installation of diagnostics, you must first enable the service commands. At the Exec prompt, enter: service and a . This will allow use of the service commands. Exec will then ask for the service password, enter: b4bus and a after which, the prompt will again be displayed. STEP 4: Update the superblock on the disk. The superblock on the disk must be updated to reserve a section of the disk for the diagnostics. Enter the superblock initialization command: sbinit and a to initialize the superblock for the diagnostic partition. EXEC will ask you if you want to destroy the existing disk partition information and the disk directory name. Any (y/n) responses are single character responses, and do NOT require a . Entry of the "sbinit" command will cause EXEC to ask: Destroy: "volume ID" (y/n)? where "volume ID" is the current volume ID contained in the superblock. A "yes" response will allow you to initialize the superblock for the diagnostic partition. A "n", no response will return you to the prompt. Enter: y and EXEC will ask for the number of sectors to reserve on the disk for the diagnostics: Diagnostic Partition size (in sectors)? Enter the number of sectors desired as follows: SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB071 Pg004 a) To install all available diagnostics, enter: 2000 b) To install tape diagnostics, enter: 200 EXEC will then ask about the directory: Destroy: "partition name" (y/n)? Enter the character "y" to destroy the current disk directory to have it initialized for a subsequent install, or "n" to retain the current partition name. If you wish to change the name of the disk diagnostic partition, enter: y and EXEC will then ask: Disk name: Enter the new disk name, up to 12 characters in length, and . This new name will be displayed every time you display the directory. EXEC will then display: Initializing: "disk name" where "disk name" is the new name you just entered. The diagnostic partition is now defined. STEP 5: Copy diagnostics from tape to disk Once the diagnostic partition is defined, diagnostics can be installed on the disk. You now can determine which files to install on the disk by listing the contents of the tape. This is optional if you are going to install all of the diagnostics. To obtain a list of file names on the tape, enter: ltape To install the diagnostics on the fixed disk, enter: install and a to install ALL of the diagnostics. To install a particular diagnostic enter: install "file" and a where "file" is the file name to install on the disk. Use the list of files obtained by the "ltape" command to determine which files you want to install. The file EXEC, SIT, MCS and/or MTS SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB071 Pg005 are the minimum diagnostic files to install. When you enter the "install" command, to install all of the diagnostics, EXEC will prompt: Destroy: "disk name" (y/n)? where "disk name" is the name of the disk entered during the "sbinit" command sequence. Entry of the character "n" will cause the current directory name to remain and the install process to begin. Entry of a "y" character will cause EXEC to ask you for the new disk name as in the "sbinit" command. Maintain the current directory from the "sbinit" sequence, enter: n and the install procedure will begin. As the diagnostics are installed on the disk, EXEC will display the current program being copied from the tape, and the size in sectors. After the sector size display, the file is written to the disk and the directory updated. When all the files are installed, EXEC will again display the prompt: STEP 6: After the diagnostics are installed on the disk, you may want to list the diagnostics on the disk enter: ldisk and to obtain the list of the diagnostic files on disk. You should test the bootstrap capability now, to see that you can boot diagnostics from the disk. Enter: shut and to obtain the bootstrap menu. STEP 7a: 2500, 3000 and 4000 only Do an alternate load, for the boot device enter: wd0, for system file enter: diag STEP 7b: 2000 only (2500's boot just like 3000's) The EOS product must be installed to boot to the diagnostic partition on the 2000 system. The file /sys/diag exists on the EOS product. This file is required to boot to the diagnostic partition. After you have installed the EOS product: Do an alternate load, for the boot device enter: wd0, SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB071 Pg006 for the system file enter: /sys/diag. NOTE: Installing diagnostics takes disk space away from the user available disk space. The device capacity is reduced to provide room for the diagnostics. 2.1.3. DELETING DIAGNOSTICS To delete the diagnositcs from a customer's hard disk, do a standard boot of the diagnostics from the disk. At the prompt enter 'delete .,; where is the name of the program you wish to delete. Repeat the delete command for all the programs you wish to delete. After you have completed deleting the programs enter the command '1' to get a listing of the programs on disk. The diagnostic programs should be gone. After you have verified that the programs are gone, shut the system down and reboot the diagnostics. The ;system should now dump and display the prompt. The number and names of the diagnostic programs will vary depending which ones were installed. To get a listing of the programs on the disk enter the '1' command. At the minumin the following three programs must be deleted: exec, dutil, sit 2.1.4 LOADING DISK DIAGNOSTICS When the system is first powered up, or after the system is shutdown, the user must perform an alternate load sequence in order to load diagnostics from disk. The system has the logic to either bootstrap the Operating System or the Diagnostic Executive. The loader programs for each are in different sections of the disk. The diagnostic loader and the associated directory of files for the diagnostics are contained in the diagnostic partition. Thus the diagnostic partition is completely self contained, and separate from the Operating System. The operation of loading diagnostics from the fixed disk and from the MCS/MTS tape are similar. The only difference is in the alternate load sequence, as discussed in the following sections. The diagnostics contained on your fixed disk cannot be run while the Operating System is up and running. The diagnostic programs are all off-line programs and require you to first shutdown your system, regardless if you load from MCS/MTS tape or from the fixed disk. After running diagnostics, entry of the diagnostic "shutdown" command will allow you to reload the Operating System. The normal indication that diagnostics are not on the disk, is the error message "invalid loader detected" when a diagnostic boot is attempted. To access the diagnostics, once they are installed perform an alternate load. For boot device enter SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB071 Pg007 'wd0'; for system file enter 'diag' for the 2500/3000/4000 system or '/sys/diag' for the 2000 system. This will get the '' prompt. Any file name listed by the 'ldisk' command can now be loaded by entry of the command: load "file" and , where "file" is any file listed. 2.2 INSTALLATION OF THE OPERATING SYSTEM The following steps outline the 7.5B BOSS/IX installation procedures for tape and floppy diskette. The "installation" procedure is to be used when installing a new system, or installing the OS after a diagnostic partition has been installed. NOTE: The 'packaging' of the products has changed. A 'base' tape will no longer be distributed. Instead, you will receive a 'customer' tape. These products are on the 'customer' tape: EOS EUT EBS EXT EBA EDB IDB TBC EIT ENT FTF INT CBR CBD UPD PDF B32 X25 EB2 With this new packaging it is no longer necessary to ship a tape for each product ordered. Instead, a Lock & Key certificate is generated and mailed for each product purchased. WARNING: When installing this release on a 3000 system from a release previous to 7.3, the system serial number MUST be reinstalled using the new 2000/3000/4000 SSN program. DO NOT attempt to upgrade a 3000 system without reinstalling the system serial number using the new 2000/3000/4000 SSN program. STEP 1: Using the mcssave/mtssave (7.1 & 7.2) or tsave (7.3A, 7.4A, 7.4B) command or the floppy diskette save utility, do a file by file back up of all user programs and data files. Using the configure utility, print out the port configurations; using the oprinfo utility, print out the operator information report. These will need to be re-entered after the install is complete. STEP 2: First step is to install the boot partition. Place the customer tape into the tape drive. Or, if you are doing floppy installation insert the installation floppy into drive fd0. NOTE: The 7.5B 2000 O.S. tape must be used to install the MAI 2000, and the 7.5B 2500/3000/4000 tape must be used to install the MAI 2500, MAI 3000, and MAI 4000. Do an alternate load. At the 'boot device:' prompt type "cs" for MCS, "ts" for MTS, or "fd0" for floppy diskette, then press . Press again at 'System file:' prompt. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB071 Pg008 NOTE: MTS requires a 4.3 boot prom on the MAI 2000. STEP 3: Screen displays loading messages, then the 'Install Utility Menu'. Select Option 'A', then . Option 'A' re-defines all the wd0 partitions and copies a new boot partition to disk. Special note for floppy diskette installations, make sure your BOOT floppy diskettes are inserted in the correct sequence according to the BOOT number. After one floppy diskette is complete make sure you change floppy diskettes before responding to the prompt on the screen. STEP 4: After the boot partition is installed the configuration record must be installed. When the message 'OPTION>' is re-displayed put the configuration record tape or floppy in the tape drive or floppy drive. Use option 'D' to install the configuration record. After the configuration record is installed enter ' ^D' and then 'shutdown'. STEP 5: After the configuration record, the EOS product must be installed. Rebooting the system at this time automatically roots to the boot partition. Enter the correct date; the screen will then display the 'ADMIN>' prompt, type "osinstall cs" for MCS tape, "osinstall ts" for MTS tape, and "osinstall fd0" for floppy diskette. This process uses the parameters in the Super Block to define the root filesystem, then copies the EOS product to the root partition on disk. After the EOS product is installed you are instructed to reboot again. WARNING: If the 7.5B configuration record for the system is not installed you will be able to access the boot partition only. NOTE: It is recommended that the configuration record be copied to the boot partition. To do this, execute the following with the configuration tape in the tape drive before rebooting: 'trestore dev= -v name=CONFIG' where dev=cs for MCS and dev=ts for MTS. For floppies: 'mount /dev/fd0 /mnt' 'copy /mnt/config.* /sys' 'unmount /mnt' STEP 6: Reloading of the system at this time automatically reloads and roots to the root partition. Enter either the current date, or a , if the date is correct. At the 'ADMIN>' prompt, type "install cs EUT EBS EXT", for MCS tape, "install ts EUT EBS EXT" for MTS tape or "install fd0 EUT", for floppy diskette. NOTE: When working with tapes, all products listed on the SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB071 Pg009 customer tape can be installed with one command line. When working with floppies, you must install one product at a time in the following order: EUT, EBS, EXT, EBA then optional products in any order. Products that are chargeable and not part of the base system will have key codes that you must enter during or after (using '/bin/install_key') installation before you can use that product. If the key certificate did not come with the media, contact the customer or service representative in your area for instruction on how to obtain this key code. STEP 7: The '/etc/conf' file on the boot partition needs to be customized to meet your needs. The '/util/sconf' utility, located in the EXT product, enables you to redefine your '/etc/conf' file. (See Section 5.0 'Memory Usage' for instruction on how to customize the '/etc/conf' file.) STEP 8: After you have copied all your products to disk and have customized the '/etc/conf' file, your system is ready for use. STEP 9: If you have user program and/or data files to be restored, use the 'dups=skip' option of the trestore command or the 'skip' option in the 'duplicates' parameter of the trestore or drestore utility to avoid writing "old" files over your new 7.5B files. If you are restoring 7.1 BASIC programs, use the csave command to convert them to 7.5B BASIC. 2.3 UPGRADING The following steps describe the 7.5B BOSS/IX upgrade procedures for tape and floppy diskette. NOTE: This upgrade procedure is for 7.2/7.3A/7.4 only. If you are upgrading a 7.1 OS level system refer to section 2.2 "INSTALLATION OF THE OPERATING SYSTEM". WARNING: When installing this release on a 3000 system from a release previous to 7.3, the system serial number MUST be reinstalled using the new 2000/3000/4000 SSN program. DO NOT attempt to upgrade a 3000 system without reinstalling the system serial number using the new 2000/3000/4000 SSN program. STEP 1: Using the mcssave/mtssave command or the floppy diskette save utility, do a file by file back up of all user program and data files. Using the configure utility, print out the port configurations; and, using the oprinfo utility, print out the operator information report. When upgrading from 7.3A/7.4 to 7.5B it is recommended to skip to Step 5 at this point, except if your media is floppy diskette. STEP 2: Root the system to the Boot Media. Insert the customer tape into the tape drive, or if you are doing floppy installation insert the Boot floppy into drive fd0. NOTE: The floppy diskette requires booting from media. Do an alternate load. At the 'boot device:' prompt type "cs" SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB071 Pg010 for MCS, "ts" for MTS or, "fd0" for floppy diskette, then press . Press again at 'System file:' prompt. STEP 3: When upgrading from 7.3A or 7.4 to 7.5B it is recommended to skip to Step 5 at this point, except if your media is floppy diskette. Screen displays loading messages, then the Install Utility Menu. When upgrading from 7.2, or using floppy diskettes, select Option 'B', then . Option 'B' will only copy an image on the boot partition from the tape or floppy to disk. This process will ensure that your system has all the up-to-date and proper MACROs and system files on the boot partition. NOTE: For floppy diskette installations, make sure your BOOT floppy diskettes are inserted in the correct sequence according to the BOOT number. After one floppy diskette is complete make sure you change floppy diskettes before responding to the prompt on the screen. STEP 4: After the boot partition is installed the configuration record must be installed. When the message 'OPTION>' is re-displayed put the configuration record tape or floppy in the tape drive or floppy drive. Use option 'D' to install the configuration record. After the configuration record is installed enter '^D' and then 'shutdown'. WARNING: If the 7.5B configuration record for the system is not installed, you will be able to access the boot partition only. STEP 5: Do an alternate load. At 'Boot device:' prompt, ''. At the 'System File:' prompt, enter ",/etc/boot.conf". The above alternate load will re-load and root the operating system to the boot partition. Enter the correct date or '' if the date is correct. Insert the base system tape containing EOS, EUT, EBS or the floppy diskette EOS #1. At the 'ADMIN>' prompt type "osupdate cs" for MCS tape, "osupdate ts" for MTS tape, or "osupdate fd0" for floppy diskette. NOTE: For floppy diskette upgrades the screen will prompt you when to insert the next diskettes. STEP 6: If you are upgrading from 7.3A/7.4 and you skipped from step 1 to 5 you must install the config record. To do this execute the following commands with the configuration tape in the drive. ADMIN> trestore d=/dev/cs or /dev/ts -v n=CONFIG ADMIN> iconf -new -save STEP 7: After the procedure is complete you have the option of restoring the default system configuration files to the upgraded root then to the boot partition. This is done by typing "/sys/installetc". This procedure allows the operator SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB071 Pg011 to select which system files he/she needs to restore. Please note that if this is done, all system files that are restored will be new and will have to be re-updated to reflect the needed system information. Example: If an 'osupdate' was performed, and '/etc/passwd' is re-installed the operators will have to be redefined. Following, find a list of the files that can be installed using 'etc/installetc' and the means to modify the files for your system: /etc/class, /etc/defaults, /etc/forms: These files are used when printing and can be customized by going to the 'ut.printer' menu and using option 5 'Printer parameters' or using the program 'pparams'. /etc/conf: This file contains your system configuration parameters and is changed by using the '/bin/vconf' command. /etc/exem, /etc/logm, /etc/motd: These files print to the screen at the time of log in and can be modified by the use of the '/bin/ved' command. /etc/passwd: This file contains your operator information and is updated by going to the 'ut.system' menu and using Option 3, (Operator information) or by using the program 'oprinfo'. /etc/ports, /etc/printers, /etc/terminals: These files contain the terminal and printer configuration parameters and are updated by going to the 'ut.system' menu and using Option 1, (Port configuration) or by using the program 'configure'. /etc/sinit, /etc/startup: These files are used at system load time and can be modified by the use of the '/bin/ved' command. /etc/shtdwn: This file is used when the system is being shutdown and can be modified by the use of the '/bin/ved' command. STEP 8: Next shutdown the system and do a normal boot of the system. Enter the correct date or press '' if the date is correct. If you are upgrading from MCS, at the 'ADMIN>' prompt type "install cs EUT EBS EXT", press ''. If you are upgrading from MTS, at the 'ADMIN>' prompt type "install ts EUT EBS EXT", press ''. The system will automatically install EUT, EBS and EXT. If you are upgrading from floppy diskette, insert the first SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB071 Pg012 floppy of the EUT set. At the 'ADMIN>' prompt type "install fd0 EUT". Once EUT is complete use the same routine to install EBS, EXT, and any other products. NOTE: The 'EXT' product must be installed in order to run the 'sconf' utility. The 'sconf' utility is used to set-up the configuration parameters for a system. NOTE: When working with tapes all products listed on the customer tape can be installed with one command line. Products that are chargeable and not part of the base system will have key codes that you must enter during or after (using '/bin/install_key') installation before you can use that product. If the key certificate did not come with the media, contact the service representative in your area to instruct you where to obtain for this key code. STEP 9: If you are upgrading from 7.2, it is time to verify your port configuration, using the 'configure' utility, and to set-up your configuration parameters, using the 'sconf' utility. To verify your port configuration, run the 'configure' utility to check the current port set-up. As a part of this verification, the printer and terminal model numbers should be accurate for the device in use. STEP 10: There have been some changes in some of the system files between 7.1, 7.2 and 7.5B. For this reason you are required to make some configuration changes to the system. These changes are identified in the following two sections. One section covers general changes, the other covers changes specific to 7.1/7.2 upgrades to 7.5B. If you are installing a particular product, such as TBC, you need not worry about the configuration changes for that product. If you are installing TBC then you must follow the section that covers TBC, and likewise for other products purchased through MBF. Once the upgrade has been performed, be especially careful when restoring files back down from a 7.2 tape. If you should accidentally restore a changed configuration file it is best to go back and install that product again from the system tape, being careful to follow the configuration change steps for that product. STEP 11: If you have user program and/or data files to be restored, use the 'dups=skip' option of the trestore command or the 'skip' option of the 'duplicates' parameter of the trestore or drestore utility to avoid writing "old" files over your new 7.5B files. NOTE: Restoring customer files on an update procedure should not be required. The procedure should leave all user files intact. 2.4 PRODUCT INSTALLATION/UPGRADE - GENERAL 2.4.1 ECC 'C' COMPILER 1. Due to changes to the header files and new shared libraries in 7.4 AND 7.5B, all 'C' programs compiled previous to 7.4, should be recompiled on SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB071 Pg013 7.5B to avoid problems executing these programs. 2.4.2 MAGNET (ENT) AND FILE TRANSFER FACILITY (FTF) 1. To install ENT, execute the command: admin> install xx ENT 2. To install FTF, execute the command: admin> install xx FTF where xx is the device of the ENT or FTF media. cs = 1/4" MCS ts = 1/2" MTS fd0 = floppy drive 3. ENT and FTF use CMB port 1 when X.25 is installed. This port must be strapped as "modem". The maximum baud rate supported by X.25 on 7.5B is 4800 baud. 4. Change your FTF stations to "B4NET" if they are not running MAGNET FTF on 7.5B or on 8/9/10.6G The default station type is set to MAGNET. RUN "/net/B4MAINT" This program displays all of the stations on your system and displays whether they're configured for B4NET or MAGNET FTF. It will also let you change the configurations from MAGNET FTF to B4NET and visa versa. Here is an example of a "B4MAINT" screen: B4NET STATIONS: BFCNY BFCCON BFCCHI MAIFFM MAICDN MAINLS MAGNET FTF STATIONS: BFCFPS BFCMIS BFCENG Enter station to change (*=ALL): After entering a station the following will display: BFCNY is a MAGNET station. Do you wish to change it to B4NET (Y/CR=N)? 5. Delete the RSM server definition file "/net/sif". This file will be recreated when you start up MAGNET. Eg: admin> delete /net/sif 2.4.3 27xx/37xx BATCH EMULATION 1. The 27xx/37xx Batch Emulation package is written in BASIC since 7.3A and is called TBC (Trans- portable Batch Communications). The C version of 27xx/37xx Batch Emulation (EBC) is no longer SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB071 Pg014 available on the 2500/3000 systems. TBC on 7.5B is compatible with TBC on MPx and 13xx systems, as well as 2500/3000 systems running EBC, since the line protocol has not changed. 2. To install TBC, execute the command: admin> install xx TBC where xx is the device of the TBC media cs = 1/4" MCS ts = 1/2" MTS fd0 = floppy drive 3. Conversion of the transmit queue, receive queue, and autoprompt files is automatically performed when installing TBC on a system previously using the EBC product. The public key for TBC is compatible with the EBC public key. 4. There are no operational changes between TBC and EBC when running BCOM from the Communications menu. However, since the 7.5B version of BCOM is written in BASIC, there are changes in accessing BCOM from command mode: user prompt>basic s=128 pgm=/tbc/BCOM/BCOM 5. TBC on 7.5B supports autodial features which allow BCOM to interface to an automatic calling unit (ACU) to dial the number stored in the BCOM autoprompt file. Two utilities, ACUTD and ACS, have been added to TBC: ACUTD - utility to build scheduler lists of BCOM autoprompts which are designated to be activated at specified date and times. ACUTD can be accessed from the communications menu or alternately from command/console mode. user prompt>basic s=128 pgm=/tbc/BCOM/ACUTD ACS - program which activates the scheduler lists specified in ACUTD. ACS can be accessed from the communications menu or alternately from command/console mode. user prompt>basic s=128 pgm=/tbc/BCOM/ACS 6. The 7.5B automatic calling features of TBC have been certified with the following ACU's and modems: o Universal Data Systems 801C ACU with Universal Data Systems 201C synchronous modem - This combination requires a serial asynchronous port be configured as a terminal (EVDT with default parameters) for the 801C ACU and CMB port 1 configured for the synchronous communications SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB071 Pg015 port. The UDS 201C is compatible to other vendor's BELL 201C compatible units. o Paradyne FDX 2400 PLUS ACU/modem - This unit also requires a serial port to be configured as a terminal (EVDT with default parameters) for the ACU interface and CMB port 1 configured for synchronous communications. This unit is compatible with another Paradyne FDX 2400 Plus, a Bell 212A synchronous modem, and a Universal Data Systems 224 synchronous modem. 7. TBC uses CMB port 1. This port must be strapped as "modem". The maximum baud rate for TBC is 4800 Baud. 8. Details on TBC and modem/ACU strappings are documented in the BOSS/IX Transportable Batch Communications (27xx/37xx) User Guide - M6353C. 9. Erase the translation file "TRNCD" and the device file "BWORK". These files are normally located in the BCOM data prefix "/etc/comm". They will be automatically re-created when you run "BCOM". The new translation table has been cleaned up to provide more consistent results between MPx and 2000/2500/3000/4000 systems. Eg: >ERASE "/etc/comm/TRNCD" >ERASE "/etc/comm/BWORK" NOTE 1: You may have to erase these files from more than one directory. The BCOM data prefix can be different for each terminal. To display the data prefix for each terminal, select the 'TASK PREFIX UTILITY' from the 'BATCH COMMUNICATIONS UTILITIES' menu. NOTE 2: If you plan to transfer files with international characters, you MUST modify program "BTRND" prior to running "BCOM" Modify statement 105 and set the variable INTRNATL$ to "INTERNATIONAL". OLD: 105 LET INTRNATL$=""; ... NEW: 105 LET INTRNATL$="INTERNATIONAL"; ... 10. Delete the BCOM node prefix file, "/etc/comm/BCOM.NODEPREFIX". This file will be re-created when you execute the BCOM node prefix utility, "BCOMPFX", from the BCOM main menu. 2.4.4 ASYNCHRONOUS TRANSPORT PACKAGE (ATP) 1. ATP (4.0) is included with the 7.5B EIT product. ATP 4.0 contains protocol changes for performance enhancements which makes it incompatible with SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB071 Pg016 previous releases of ATP. All systems using ATP to communicate to a 7.5B system must also have ATP 4.0 on their systems. 2. In addition to performance enhancements, ATP 4.0 provides the following features: o Line Turnaround - allows transmit and receive functions in a single session o Autodial - supports automatic dialing of Hayes/compatible and UDS 224 A/D modems o Scheduler - provides unattended start-up of ATP sessions 3. To install ATP 4.0, the EIT product must be installed: admin> install xx EIT where xx selects the device of the install media cs = 1/4" MCS ts = 1/2" MTS fd0 = floppy drive 4. To activate the features of Line Turnaround, Autodial, and the Scheduler, a public key must be installed: admin> install_key /etc/level/ATP 5. As with previous levels, BQR must be run to generate an ATP filelist. Note, however, that schema files are no longer supported by BQR for any transport media - transmitted files must either be in TEXT or BINARY format. After BQR filelists are created, RUN "ATP" to set the communications parameters for the session. The parameters may be saved in an autoprompt for future use or use with the Autodial and Scheduler features. RUN "ATPTIM" to set the Scheduler parameters. RUN "ATPSCH" to begin the ATP sessions according to the parameters set in the Scheduler. 6. Automatic file conversion and translation occur during the file transfer. BQR will no longer be required to convert files received via ATP 4.0 from unlike systems. 7. Refer to the ATP 4.0 Software Announcement #150 and the Intersystem Transport Package User Guide (M6354D) for details. 2.4.5 3270 BISYNCHRONOUS 1. To install the 3270 Bisynchronous product, SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB071 Pg017 execute the command: admin> install xx B32 where xx selects the device of the install media cs = 1/4" MCS ts = 1/2" MTS fd0 = floppy drive 2. B32 uses CMB port 1. This port must be strapped as "modem". The maximum baud rate supported by B32 is 4800 Baud. 3. As with previous releases of B32, the DT-4310 is the only terminal which is supported to emulate an IBM 3278 display terminal. 2.5 PRODUCT INSTALLATION/UPGRADE - FROM 7.1/7.2 1. The 7.5B user is responsible for configuring the type of system console terminal after the install procedure is complete. This step cannot be done until the operating system and the utilities product, EUT, have been installed. Then the user should execute the Port Configuration Utility "configure" and set the system console type. The system console type set by the boot PROM configurator is no longer supported by the operating system as of 7.3A. Other system console parameters must still be set through the boot PROM configurator. 2. Partition files created with 7.2 "/bin/usb", which reside in the "/etc/diskdesc", cannot be used on 7.5B. These files can be recreated using the 7.5B "usb" command. 3. On upgrades from 7.1 to 7.5B the user MUST boot off the customer tape and select the "A" option before doing an "osinstall" from the boot. 4. All upgrades to 7.5B will create a new boot partition filesystem, thereby destroying all 7.2 files on the boot partition. 5. The MAGNET/FTF configuration files have changed format between 7.2 and 7.5B. Existing LEGAL network config- urations will be converted to the new format by a program which is automatically executed at installation of the 7.5B ENT or FTF product. Configurations which do not conform to documented restrictions (e.g., two LAN boards) may not successfully convert. Though the installation procedure allows the installer to omit calling the configuration conversion program, it is safer to run the conversion program. 2.6 SYSTEM CONFIGURATION RECORD When installing 7.5B on your system or if you are upgrading/adding to the system's hardware, you must also install/upgrade to a 7.5B system configuration record. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB071 Pg018 See step #4 of section 2.2 Installation of the Operating System for instruction. 2.6.1 7.5B CONFIGURATION RECORD REQUEST SHEET On the following page you will find a copy of the 7.5B Configuration Record request sheet. 3.0 LEVEL 7.4 BOSS/IX ENHANCEMENTS AND CORRECTIONS 3.1 OPERATING SYSTEM (EOS) o SCSI disk support. o Print @(X) resulting in overprint on LQP printers has been corrected. o Spooled printers opened with a form= does a vfu load on OPEN statement with same form has been corrected. o Sttywrite crash correction. o 1/2 Inch tape error -92 correction. o Off-line printer losing data has been corrected. o When start process is /bin/basic and they RELEASE, it kills the pid of one; this has been corrected. o PDF's: LQP Printers send 'FF' when printer is closed; this has been corrected. o The last data line does not get flushed out to printer; corrected. o All PDF's, except LQ-drivers, allow for only 132 column printing - corrected. o When changing devices on a print job spooler loses the job - corrected. o BOSS/IX Xon/Xoff flow CTL spooled printers lose data when taken off-line - corrected. o 4206 printer requires a form change after rebooting the system - corrected. o pwd: suspends in directories with a path name longer than 128 characters - corrected. o 4217 DRIVER:PRINT (1)'SL','EL' will advance the 4217/4218 a 1/2 line - corrected. o sconf gives incorrected defaults for TBC configuration, this has been corrected. o No isp slave printer option - corrected 3.2 UTILITIES (EUT) o GCR support o pqueues: Leap year affects the date set to run print job - corrected. o frepair: retirement of bad block does not work correctly with/multi-key files - corrected. o Invalid pitch error with null pitch when printing through oprinfo - corrected. o bsearch and brenumber leaves program in slowmode - fixed. 3.3 BASIC (EBS) o BB90 Support o Multi-key file - write does not advance record pointer problem - fixed. o LISTPROGRAM and MAKEPROGAM change numeric line values - corrected. o brenumber: renumbering program with IOLIST in it - the SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB071 Pg019 IOLIST does not renumber, this is corrected. o FPT function not rounding properly has been corrected o VFU load being sent on open statements has been corrected. 3.4 MAGNET/FTF There are now two versions of FTF on 7.5B : B4NET/FTF and MAGNET/FTF. B4NET/FTF is the same FTF product as in 7.4B. MAGNET/FTF contains the enhancements listed below: o Performance Enhancements o The transport of multi-keyed files is now supported between 7.5B and 8/9/10.6G systems. o Performance has been enhanced by blocking records within 512 byte MAGNET datagrams instead of 1 record per datagram. o An inter-family text translation option has been added to the FTF transfer options. This enables you to automatically translate the character sets (7/8 bit ascii conversion) when transporting between 7.5B and 8/9/10.6G systems. o Trailing nulls are truncated to reduce transfer overhead. o MAGNET/FTF is automatically started so, you no longer have to start FTF if all systems in your network are using MAGNET/FTF. A MAGNET server is started and release for each file transfer. Both FTF versions can be executed on a system at the same time, but you must specify what version of FTF each system in your network is using by running the new utility "/net/B4MAINT". 3.5 3270 BISYNC SUPPORT FOR DT-4313/DT-4314 The 3270 Bisync package now supports the DT-4313 and DT-4314 terminals in addition to the terminals it already supports. The 3270 status line on these terminal displays on the bottom of the screen instead of the top. 3.6 TBC Here is a list of the new features and enhancements that have been added to TBC for this release: o Multi-key file support o Support of 5 character devices o Improved start-up menu and prompts o BQR file list no longer terminates on last file o Auto-scheduler now accepts international dates o No Chain with EOT Suppression option added to Transmit Queue. 3.7 ATP o Converts String Files to Serial Files o Multi-key file support 4.0 MEMORY REQUIREMENTS AND OPERATING PARAMETERS SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB071 Pg020 4.1 APPROXIMATING A SYSTEM'S MEMORY REQUIREMENT This section describes how to approximate the amount of memory a system needs. Tables 4A and 4B show some standard system configurations which can be used to approximate the amount of memory a system needs. The number of users (terminals), ghost tasks, and printers differ for each of these standard config- urations. First, find the standard configuration that most closely matches the system in question, by scanning down the user/terminals, ghost-task, and printers columns. Second, scan across the table to the memory-needed column -- this is the system's memory requirements. NOTE: These tables (4A and 4B) assume that the system in question will be executing 60% BASIC and BASIC application programs, and 40% non-BASIC applications. If the system will be executing a higher percentage of non-BASIC programs, it will need more memory. Memory Requirements Memory requirements for each system will vary depending on the specific software application. "Data Processing Type Users" shows the maximum number of users recommended. MAI 2000 o Data Processing Type Users: Memory: 768Kb 1024Kb 1280Kb 1536Kb Max Users: 1 2-4 5-8 9-11 MAI 2500 o Data Processing Type Users: Memory: 1Mb 2Mb 3Mb 4Mb Max Users: 3 12 14 14 MAI 3000 o Data Processing Type User: Memory: 1Mb 2Mb 3Mb 4Mb 5Mb 6Mb 8Mb 10MB Max Users: 3 12 16 18 23 27 30 31 MAI 4000 o Data Processing Type Users: Memory: 8Mb 10Mb 12Mb 14Mb 16Mb Max Users: 30 31 33 36 38 NOTE: Users refer to Terminals, Ghosts, and Serial Printers. 4.2 RECOMMENDED VALUES FOR "vconf" The following tables (Table 4A, 4B) show the recommended values for the BOSS/IX "vconf" parameters. 4.2.1 RECOMMENDED VALUES FOR "vconf" BOSS/IX MAI 2000 PARAMETERS SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB071 Pg021 __________________________________________________________________________ . | | | | | | | | SYSTEM | base | add | add | add | maximum | | DESCRIPTION | system: | for | for | for | recom- | | -----> | | each | each | each | mended | | | 2 user | extra | ghost | extra | system | | | 1 printer | user | task | printer | config- | | "vconf" | | no ghosts | (above 2) | | (above 1) | uration | | BOSS/IX | | | | | | (See | | PARAMETERS | | | | | Note 2) | |---------------|-----------|-----------|-----------|-----------|----------| |buffers=.......|........20.|.........4.|...........|...........|.......64 | |printers=......|.........1.|...........|...........|.........1.|.......14 | |procs=.........|........14.|.........2.|.........1.|.........1.|.......80 | |tsegs=.........|........12.|.........2.|...........|...........|.......64 | |locks=.........|........35.|.........5.|.........5.|...........|......160 | |ibsize=........|.......128.|.........1.|...........|...........|.....2048 | |tbsize=........|........64.|.........1.|...........|...........|......512 | |mfsys=.........|.........3.|...........|...........|...........|.......* | |lus=...........|........65.|........15.|........15.|.........6.|......254 | |fds=...........|........60.|........12.|........12.|.........2.|......206 | |eventcalls=....|........16.|.........2.|.........0.|...........|......152 | |dirc=..........|........16.|.........5.|.........2.|.........2.|......206 | |ghosts=........|.........0.|.as needed.|.........1.|...........|.......99 | |--------------------------------------------------------------------------|. | * Allow one mountable filesystem slot ("mfsys") for each | | mountable disk partition. The default of three allows | | for a boot partition, a root filesystem partition, and | | a diskette filesystem or 2nd drive. | |__________________________________________________________________________|. NOTE 1: The BOSS/IX configuration parameters required for other products are described in their documentation. Specifically, the LAN and 27xx/37xx communications products will require changes to the system parameters. For example, Magnet operating systems require 5 eventcalls per user. NOTE 2: These recommended values are not system limits but provide a guideline to tailoring the system. NOTE 3: vconf numbers for specific applications have been distributed by Field Product Support. The 7.4 values shall apply to 7.5B. TABLE 4A Recommended Values for MAI 2000 Operating Parameters SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB071 Pg022 4.2.2 RECOMMENDED VALUES FOR "vconf" BOSS/IX MAI 2500, 3000 AND 4000 PARAMETERS ____________________________________________________________________________ . | | | | | | | |. | SYSTEM |base |add |add |add for |maximum |maximum | | DESCRIPTION |system: |for |for |each |recom- |recom- | | -----> | |each |each |extra |mended |mended | | |2 user |user |ghost |printer |system |system | | |1 printer |(above 2) | | |values |values | | "vconf" | | | | | |for the |for the | | BOSS/IX | | | | | |MAI 3000 |MAI 4000 | | PARAMETERS | | | | |(Note 1) |(Note 4) | |-------------|----------|----------|----------|---------|---------|---------|. |buffers=.....|......128.|.......32.|........0.|.........|(Note 2).|(Note 2) | |printers=....|........1.|..........|..........|.......1.|......34.|......76 | |procs=.......|.......14.|........3.|........1.|.......1.|.....223.|.....358 | |tsegs=.......|.......12.|........2.|..........|.........|.....148.|.....290 | |locks=.......|.......35.|........5.|........5.|.........|.....284.|.....684 | |ibsize=......|......128.|........1.|..........|.........|.........|.........| |tbsize=......|.......64.|........1.|..........|.........|.........|.........| |mfsys=.......|........3.|..........|..........|.........|(Note 3) |(Note 3) | |lus=.........|.......65.|.......15.|.......12.|......10.|....1030.|....2630 | |fds=.........|.......60.|.......12.|........8.|.......2.|.....434.|....1054 | |eventcalls=..|.......16.|........2.|........0.|.........|.....234.|.....314 | |dirc=........|.......64.|........8.|........0.|.......0.|.....512.|....1058 | |ghosts=......|........0.|as needed.|..........|.........|......99.|......99 |. |____________________________________________________________________________|. NOTE 1: Values in this column reflect 34 user totals calculated from recommended increments, except for buffers. NOTE 2: Only memory availability limits buffers. NOTE 3: Allow one mountable file system for each mountable disk partition. A default of 3 allows for a root, boot and 1 other partition. NOTE 4: Values in this column reflect 74 user totals calculated from recommended increments, except for buffers. NOTE 5: vconf numbers for specific applications have been distributed by Field Product Support. The 7.4 values still apply to 7.5B. TABLE 4B Recommended Values for MAI 2500, 3000 and 4000 Operating Parameters 5.0 MEMORY USAGE This section describes how to determine the memory requirements for any MAI 2000, MAI 2500, MAI 3000, and MAI 4000 system. All BOSS/IX systems have different memory requirements. A system's memory requirement is based on its hardware configuration and software load. Specifically, the number of peripheral devices (i.e. terminals and printers) and software packages (such as BASIC, BASIC applications, utilities, etc.) determine a system's memory needs. This section explains two methods used to determine the amount of memory needed for a system. The first method approximates a system's memory requirements -- and can be used if the system closely fits one of the standard system configurations. The second method calculates the memory requirements for best system performance -- and is used for SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB071 Pg023 non-standard system configurations. 5.1 CALCULATING A SYSTEM'S MEMORY REQUIREMENTS This section describes how to calculate the number of memory boards a system requires for adequate performance. The calculations are based on the system's hardware configuration and software load. Software load is defined to be the number and types of processes running on the system. This section steps through an example based on a system consisting of 16 users for the 3000. The same steps and overhead numbers apply for the Model 2500 and 4000. (See section 5.1.1). STEP 1: First, add the space required for the operating system, table space, and dynamic space required for the base configuration. NOTE: 1 Kb = 1024 bytes 220Kb This is the memory requirement for the base BOSS/IX operating system program. This includes space for the system's interrupt vectors, and operating systems text (code) and data segments. 34Kb** This is the memory requirement for BOSS/IX table space for the base configuration: (2) users (terminals), (1) printer, and (0) ghost tasks. NOTE: Additional table space must be added for each additional resource above that in the base configuration (see step 2). NOTE: This excludes the memory required for hash tables for buffers and directory entries. 36.6Kb** This is the memory requirement for the operating system's dynamic work space (or unswappable memory) for the base configuration. STEP 2: Next, add in table space needed for resources beyond the ones described in the base configuration. (If the system will be configured like the base configuration skip this step). NOTE: The MAI 3000 is a table driven system. For maximum performance extra memory must be allocated for resources beyond the ones described in the base configuration. 10.2Kb** This is the memory needed as table space for each additional user above the two that are allocated in the base systems. 5.0Kb** This is the memory needed as table space for each ghost task in the system. 3.2Kb** This is the memory needed as table space for each additional printer above the one that is included in the base system. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB071 Pg024 4.8Kb** This is the memory needed for dynamic work space for each additional process (i.e. "proc") above the 16 that are included in the base system. (Refer to Section 5.2) ** Memory required for BOSS/IX table space and dynamic work space. These values are the memory allowances based on a system consisting of 16 users for the 3000. If the system parameters are set differently, use section 5.2 and Table 5B to calculate the memory required for O.S. table and O.S. dynamic work space. STEP 3: Add the space needed for system processes for the base system configuration. 106Kb This is the memory allowance for system tasks. System tasks for the base system include: a printer despooler process and two command interpreters. The total memory required to have all system processes in memory at the same time is approximately 2500Kb. However, 106Kb should be used in this calculation because system processes wait on system events and it is not likely that all system processes will want to execute at the same time. Furthermore, these processes, when waiting for events, can be swapped to secondary storage, which will have little effect on system performance. NOTE: There is a one time additional allocation of 83Kb for shared libraries. STEP 4: Add the space needed for any additional system processes beyond the ones specified in the base configuration. (If the system will be configured like the base configuration skip this step). 33Kb This is the memory needed for each additional printer despooler, above the one that is allocated in the base configuration. This is a memory allowance for the data and stack segments for an additional despooler task. An allowance for test (code) space is not necessary, because two despooler tasks will share the same code segments. NOTE: A one time shared library allocation of 8Kb should be added for the despooler. 11Kb This is the memory required for each user (terminal) that will be executing tasks concurrently. This is the memory allowance for each additional command interpreter. It is space needed for the interpreter's data and stack segments. NOTE: A one time shared library allocation of 8Kb should be added for all concurrent users. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB071 Pg025 NOTE: Memory allowance for text (code) space is not necessary because multiple command interpreters share the same code segments. STEP 5: Next, add the space needed for applications processes. 160Kb This is the space needed for each unique, non-BASIC task that will be executed concurrently on your system. Such tasks include the BASIC interpreter, utility programs, LAN, Informix, communications, BOSS/IX command interpreter, etc. NOTE: only one BASIC interpreter is needed to support any number of BASIC programs. This value is a rough estimate, for all processes require different amounts of memory, some more some less. When computing the memory required for application tasks, consider how often each application is used. For example, if the system seldom executes BOSS/IX commands or the utilities, only a percentage of the total space needed to execute these processes will be required. However, when the system is loaded, and these processes are executed, system response time may increase due to excessive amounts of swapping. 60Kb This is the memory required for each BASIC program. This space is the allowance for the data and stack segments for each BASIC program. NOTE: All BASIC programs share the same text (code) segment. Furthermore, this value is not exact, for some applications may require more memory and some may require less memory. 64Kb This is the memory required for each ghost task that will be executed concurrently. This is the space needed for each ghost tasks' stack and data segments. Text space is not allocated because all ghost share the BASIC process text segment. The result of the sum of Steps 1 thru 5 is the system's "memory requirement". STEP 6: Determine the memory/performance trade-offs. The value calculated in Steps 1 thru 5 is the "memory required" for good system performance. However, this value is not exact and may be raised or lowered which will increase or decrease performance respectively. By lowering the memory required value, one can save the costs of an extra memory board, but at the expense of performance. In other words, systems will run with less memory than required, however, the system overhead for swapping will increase. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB071 Pg026 Process swapping is the action which extends user space to a temporary storage region on disk (i.e. the swap partition) so that during periods of heavy main memory utilization, processes may be stored on disk to make room in memory for processes waiting to execute. The advantage of process swapping is that it extends user space to disk (secondary storage); however, it is not without disadvantages. Swapping requires system overhead to read/write processes to/from secondary storage. Furthermore, excessive amounts of swapping will increase system responsiveness (i.e. decrease performance). If the cost of memory is more important than user responsiveness, multiply the system's memory requirement (calculated in Steps 1 thru 5) by a value between 0.7 and 1.3. Multiplying the memory required value by 1.0 will cause normal amounts of swapping; multiplying it by 0.7 will cause processes to be swapped to/from memory more frequently. Multiplying the "memory requirement" by some value greater than 1.0 will decrease the O.S. overhead for swapping. NOTE: Do not run a system with less than 70% of the "memory required" value -- this will cause excessive amounts of swapping. The result of this calculation is your system's "memory need". STEP 7: Next compute the number of memory boards that the system needs. Dividing the "memory needed" value, calculated in Step 6, by 1024 d/1024Kb). NOTE: 1024Kb is the amount of memory on a 1Mb board. If a fraction results, round off to the next highest whole number. The value calculated is the "number of boards needed". 5.1.1 EXAMPLE OF HOW TO CALCULATE A SYSTEM'S MEMORY REQUIREMENT FOR MODEL 3000 This example shows how to compute the memory requirement for a system with 16 terminals, 4 ghosts and 4 printers. Thirteen of the terminals are dedicated to running BASIC applications: accounts receivable, accounts payable, payroll, and word processing. The remaining terminals are used to run utilites, commands, and the Informix database application. Some of the applications use ghost tasks to output reports to printers. STEP 1 thru STEP 5: Add these numbers to compute "memory required" 230 Kb Base operating system 99 Kb Table space for base system 53 Kb O.S. dynamic work space for base system 2 Kb Hash table space for directory cache entries (table 5C) 16 Kb Hash table space for disk buffers (table 5C) 41 KbX14 Allowance for table space for 14 additional users (total of 16 users/terminals) 41 Kb*4 Allowance for table space for SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB071 Pg027 4 ghost tasks 2 Kb*3 Allowance for table space for additional printers 1.7 Kb*49 Allowance for dynamic work space for 14 additional users ("procs" - base "procs") 100 Kb Allowance for system processes 30 Kb*3 Allowance for concurrent printing to the 3 additional printers 160 Kb*3 Allowance for the BASIC interpreter and for the Utilities/Commands/Informix 15 Kb*3 Allowance for concurrent terminals 60 Kb*13 Allowance for 13 concurrent BASIC applications 64 Kb*4 Allowance for 4 ghost tasks TOTAL = 2979 Kb = "memory required" STEP 6: Compute "memory needed" For adequate system performance with frequent swapping of applications tasks and a reduced number of disk buffers: "memory needed" = 2979Kb * 0.7 = 2085Kb or 2 memory boards For good system performance with very little swapping: "memory needed" - 2979Kb * 1.0 = 2979Kb or 3 memory boards For best system performance with much caching: "memory needed" = 2979Kb * 1.3 = 3872Kb or 4 memory boards The approximate method of determining a system's memory requirement (section 4.1 and Table 4C) shows that a system with 16 users (terminals), 4 printers, and 4 ghost tasks needs 3, Model 3000, 1Mb memory boards. The calculation method, described in this section shows that such a system will have different performance characteristics depending on the number of boards (i.e. either 2, 3, or 4) the system has. 5.2 CALCULATING BOSS/IX TABLE SPACE AND DYNAMIC WORK SPACE This section describes how to calculate the size of the operating system dynamic work space needed by any configuration on the MAI 2500, MAI 3000, and the MAI 4000. Table 5B shows the amount of memory allocated for each operating system configuration parameter; it shows the parameters for the base system configuration; for the MAI 2500, 3000, 4000; it shows how the 98Kb value for table space, used in section 5.1.1, was calculated; and it shows the parameters and total table space required for the example system depicted in section 5.1 SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB071 Pg028 To determine the table space for any configuration, multiply the value of each configuration parameter by its corresponding memory allowance (see column 1, table 5B). Next, add the result of these calculations (see column 2). The result is the allowance for table space. To determine the memory allowance for operating system dynamic work space (i.e. unswappable memory) use the following formula: " dynamic memory" (bytes) = (49 +("fds" / 4) + (("procs" * 2704) / 512 / 2)) * 512 The variables in this formula from left to right are: 49 - the number of 512 byte pages for miscellaneous operating system space "fds" - the number of open files configured "procs" - the number of processes configured 2704 - the size (bytes) for each process's user area / 512 - for converting into 512 byte pages / 2 - one half the number of pages * 512 - for converting pages into bytes For the base configuration the dynamic memory allowance is: "dynamic memory" (bytes = 49 + (60/4) + ((16 * 2704) / 512 /2)) * 512 = 54400 bytes or 53Kb For the example system (see section 5.1.1) the memory allowance is: "dynamic memory" (bytes) = (49 + (218/4) + ((65 * 2704) / 512 / 2)) * 512 = 140872 bytes or 138Kb or 36.6Kb (base size) + (49 * 1.7Kb) (extra procs, 65-16)=120Kb NOTE: 1.7 is obtained by (138-53)/49, the additional "procs" (65-16). NOTE: The operating system dynamic work space -- also called unswappable memory -- is a vital work area for the operating system. Within this work area is the process environments (i.e. user area or "uarea") for all active process in the system. Also within this area is printer input and output buffers, ISAM key and dictionary information, and other operating system structures which get dynamically allocated or de-allocated depending on system load. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB071 Pg029 ______________________________________________________________________________. |. | | | | | | | |BOSS/IX |memory | param.'s | total | param.'s | total | Memory for each| |PARAMETERS |used for| for base | memory | for | memory | additional: | |(set by |each | config- |for base | example | for |________________| |"vconf" or |param. | uration | system | system * |example | | | | | "sconf") |(bytes) | system | (bytes) | | system |USER |GHOST|PRTR| | | | | | |(bytes) | | | | |-----------|--------|----------|---------|----------|--------|-----|-----|---- |buffers=...|....594.|.......20.|...11880.|.......32.|..19008.|.2376| | | |printers=..|....906.|........1.|.....906.|........4.|...1812.|.....|.....|906 | |procs=.....|....324.|.......14.|....5184.|.......27.|...8748.|..972|..324|324 | |tsegs=.....|.....24.|.......12.|.....384.|.......22.|....528.|...40| | | |locks=.....|.....40.|.......35.|....2960.|.......94.|...3760.|..200|..200| | |ibsize=....|....128.|..........|.....256.|..........|....640.|..128| | | |tbsize=....|.....64.|..........|.....128.|.......16.|....320.|...64| | | |mfsys=.....|....424.|........3.|....1272.|........3.|...1272 | | | | |lus=.......|.....44.|.......65.|....5984.|......224.|...9856.|..800|..880|264 | |fds=.......|.....92.|.......60.|....5520.|.......97.|...8924.|..736|..920|172 | |eventcalls=|.....20.|.......16.|.....320.|.......95.|...1900.|..32 | | | |-----------|--------|----------|---------|----------|--------|-----|-----|---- |TOTALS. | | | 32388 | | 52590 | 5148| 2144|982 | | | --- | --- | | --- | or | or | or |or | | | | | | | 51 Kb | 5 Kb| 2 Kb|1 Kb| |______________________________________________________________________________ TABLE 5A: BOSS/IX Operating Parameters and Memory Requirements (Table Space) for Model 2000 ______________________________________________________________________________. |. | | | | | | | | BOSS/IX | memory| param.'s | total | param.'s| total | Memory for each | |PARAMETERS | used | for base | memory | for | memory | additional: | | (set by | per | config- |for base| example | for |___________________| | "vconf") | param.| uration | system | system *|example | | | | | |(bytes)| system | (bytes)| |system | USER |GHOST |PRTR | | | | | | |(bytes) | | | | |-----------|-------|----------|--------|---------|--------|------|------|----- |**buffers=.|...594*|.....128..|..76032*|....1280.|.760320*|38016*|38016 | | |printers=..|...906.|........1.|....906.|.......4.|...3624.|...--.|...--.|.268 | |procs=.....|...344.|.......16.|...5184.|......65.|..21580.|..996.|..332.|.332 | |tsegs=.....|....24.|.......16.|....384.|......44.|...1056.|...48.| | | |locks=.....|....40.|.......74.|...2960.|.....164.|...6560.|..200.|..200 | | |ibsize=....|...128.|........2.|....256.|......16.|...2048.|..128 | | | |tbsize=....|....64.|........2.|....128.|......16.|...1024.|...64 | | | |mfsys=.....|...424.|........3.|...1272.|.......4.|...1696 | | | | |lus=.......|....44.|......136.|...5984.|.....556.|..24464.|..880.|..880.|.264 | |fds=.......|....92.|.......60.|...5520.|.....218.|..20056.|..736.|..920.|.172 | |eventcalls=|....20.|.......16.|....320.|......56.|...1120.|...40.|..100 | | |dirc=......|....48*|.......64.|...3027*|.....338.|..16224*|..384*|..480*|..96 | |-----------|-------|----------|--------|---------|--------|------|------|----- |TOTALS | | | 102018*| | 859792 |41492*|40928*| 1132| |excluding | --- | --- | or | --- | or | or | or | or | |hash tables| | | 99 Kb*| | 839 Kb*|40 Kb*|40 KB*|1.1KB| |-----------|-------|----------|--------|---------|--------|------|------|----- |TOTAL | | | | | | | | | |hash tables| --- | --- | 101 Kb | --- | 853 Kb |41 Kb |41 KB | 2 KB| |______________________________________________________________________________ TABLE 5B: BOSS/IX Operating Parameters and Memory Requirements (Table Space) for Model 2500, 3000, and 4000 * Excludes hash table size which must be calculated separately based on the number of entires requested, SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB071 Pg030 then added to the total system requirement. ** Size, number of calculation differs from Model 2000 __________________________________________ | | | | Number of | | | Entries | Memory | | Requested | Required | | | | | through 63 | .5Kb | | | | | 64 through 127 | 1Kb | | | | | 128 through 255 | 2Kb | | | | | 256 through 255 | 4Kb | | | | | 512 through 1023 | 8Kb | | | | | 1024 through 2047 | 16Kb | | | | | 2048 through 4095 | 32Kb | | | | | 4096 through 8191 | 64Kb | | | | | 8192 through 16383 | 128Kb | |__________________________________________| This table is used to obtain the amount of memory needed for hash tables for either the 'buffers' or 'directory cache' operating parameters (see Table 5B). The per entry charge is not included here and must be added to the value from this table. TABLE 5C Memory Required for Hash Tables 6.0 NEW AND UPDATED MANUALS FOR LEVEL 7.5B M6211B BOSS/IX (7.5) User Reference Manual M6227B BOSS/IX (7.5) Technical Reference Manual M6204A MAI 2500/3000/4000 Diagnostic and Error Logging Reference Manual M6262-003 BB90 Business BASIC Manual 7.0 HELPFUL HINTS This section gives miscellaneous information about the 7.5B O.S. release and the MAI 4000 system. 7.1 FOUR-WAY AND EIGHT-WAY CONFIGURATION o A maximum of nine Eight-ways are allowed in the MAI 4000 system. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB071 Pg031 o Four-ways are not allowed in the Expansion Unit. 7.2 MEMORY CONFIGURATION o The MAI 4000 system and 7.5B O.S. only support up to 16Mb of RAM. o The MAI 4000 only supports up to six memory boards. This could include 4Mb boards and 1Mb boards. 7.3 DISK CONFIGURATION o The MAI 4000 supports up to seven disk drives. They . are installed with three drives in the main unit and four drives in the expansion unit. o The disk drives must be specified by device name according. to the diagram on the next page. ______________________ ______________________ . | | | |. | | | |. ______________________ ______________________ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | WD2 | | WD6 WD5 | | | SLOT3 SLOT2 | | SLOT7 SLOT6 | | | | | | | | | | | | | WD1 WD0 | | WD4 WD3 |___________| | SLOT1 SLOT0 | | SLOT5 SLOT4 | | | | | |______________________| |______________________| MAI 4000 DISK CONFIGURATION For minor number, multiply the SLOT number by 32. Example: For WD3 - SLOT (4) x 32 = 128 Major Minor 14 , 128 NOTE: SLOT 3 is reserved for the MCS tape drive. ORIGINATOR: Julia Shreve SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB071 Pg032 FIB 00072 02/22/90 *** 7.5B Warnings and Cautions [ WPSF 597 ] *** These problems exist on all levels of BOSS/IX. PROBLEM: bencrypt stops after 5 to 10 programs are encrypted. This is a revision of Field Bulletin #256. WORKAROUND: Create a filelist, using the filelist utility, making sure that the 'EXPANSION' option is set to YES in the utility. 10 rem" ENCRYPT ROUTINE 20 PRINT 'CS';INPUT @ (10,10),"Enter filelist name ",F$ 30 INPUT @(10,12),"Enter the destination directory ",D$ 40 OPEN(1,ERR=20)"/util/fl/"+F$ 50 READ(1,END=120)A$ 60 C$=A$(1,LEN(A$)) 70 IF POS("/"=C$)<>0 THEN LET C$=C$(POS("/"=C$)+1); GOTO 70 80 LET E$=D$+"/"+C$ 90 ENCRYPT A$,E$ 100 PRINT ".", 110 GOTO 50 120 PRINT 'LF',"Program Completed" PROBLEM: Print a job to the spooler with the requeue option on. Change the priority to print the job and only the last page prints. SOLUTION: Using the 'pqueue' utility, re-enter the start page number before restarting the requeued print job. WARNING: When setting-up additional disk drives, always use uppercase letters for the buffered and unbuffered devices. EXAMPLE: Use 'makedev /dev/rdrivel U 14 32'. DO NOT USE 'makedev /dev/rdrivel u 14 32'. WARNING: INDEXED files could have garbage data after being created or initialized. The problem could be noticed if an INDEXED file is initialized and the first record written is not in the first index. If a sequential read is performed, garbage will be read from the initialized records. SOLUTION: After initializing an INDEXED file, write hex zeros to it. PROBLEM: The utility 'brenumber' does not renumber lines of BASIC code with TBL=. SOLUTION: Change line 1180 in util/RENUM. The ^ points to the changes in the line. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB072 Pg001 WARNING: Spool files may be deleted after the system has been re- booted. Because of the naming convention for spool files it is possible that an existing spool file could be over- written. A spool file may have the name /etc/_qtmeps/bfs.0.52. 'bfs' indicates that the file was created by a BASIC process, '0' means that this is the first spool job from this process and '52' is the process id. The process id has the potential for causing the problem. If a spool job is put on hold and the system is rebooted, it is possible that the process '52' (from our example) will recreate a spool file with the same name as the existing spool file thus losing the data from the original print job. WORKAROUND: If it is a common practice to keep spool files on the disk, rename them and resubmit them to the spooler when it is time to print them. WARNING: A data file on tape may be too large to restore to disk. It is possible to not be able to restore a data file to disk it was saved from. 'trestore' tries to create the file at the maximum size, rather than the actual file size which of course may be too large for the disk it was resident on. WORKAROUND: When creating files, make the initial extent and maximum records the same to make sure the file will fit on the disk. If the file is too large, you will receive an error message saying there is not enough room in the file system. After testing to see that the file will fit, you can reduce the initial extent to a smaller size. WARNING: The system will allow a data file to be created which is larger than the disk it will reside on. Attempt to create a huge file with maximum records and initial extent equal. You will get an error stating that there is not enough room in the filesystem. If the initial extent is reduced enough, the file will be created. Eventually the file may fill the filesystem through use. WORKAROUND: Create files with the initial extent and maximum records equal. After the system creates the file, you can reduce the initial extent to make space available on the disk. This problem exists on 7.4B and 7.5B. PROBLEM: The default timeouts for the PT-4217/4218 printers are incorrect. This could prolong system start-up if there are many PT-4217/4218's on a system and they are not on-line. They appear as the following: Read timeout: 20 Write timeout: 45 SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB072 Pg002 WORKAROUND: Should be: Should be: Read timeout: 10 Write timeout: 12 The timeouts can be changed in the port configuration utility when the printer is configured or change the /etc/printdef file. Below are the fields to change: Citizen:PT-4217:4217:2400:2400:2:7:1:0:Y:20:45:1:Y:2:N:3 ^^ ^^ Change 20 and 45 to 10 and 12 so that the defaults in the configure utility are the desired numbers. ............................................................................... These problems exists only on 7.5B. PROBLEM: vconf parameters could be lost. 'sconf' uses 2 files to store its defaults and any changes you make to the vconf parameters. If you execute as 'install cs EUT' the files will be overwritten. The file names are /etc/asg.param and /etc/sconf.param. SOLUTION: Have the files included on the daily backup with the other /etc files and create a copy of the files each time you update the vconf. REVISED: When installing a SCSI disk drive in a 3000/4000, the system must have a CMB level 903631-004 or above to support the drive. A site survey must be performed and a new CMB should be ordered when the SCSI drive is ordered. FACT: The 7.5B Software Announcement #167, states "a Diagnostics Products License Agreement must be signed prior to installation of diagnostics". This applies only to the U.S. and does not apply to International. INFO: CONFIGURATION FOR A PT-4214 w/IGP-CARD ON 7.5B - Protocol: XON-XOFF +DTR to prevent loss of spool jobs when the printer is off-line or paper-out occurs. - Write Timeout set to 55 to prevent intermittent error 244, 283, 285, & 288's. - Initial formfeed set to 1 in the printer form definition. Without the initial formfeed, after paper is reloaded, the printer needs a formfeed to continue to print. FACT: It is NOT possible to transfer encrypted BASIC programs from 7.5B to ANY previous level, as in MAI OFFICE and ORIGIN. The encryption algorithm has changed on 7.5B. Also, any programs being transferred from 7.5B to earlier levels should be transferred using EIT or ATP. INFO: Marketing Announcement #757 states that 7.5B operating system requires 20 MB of disk space. This is true but included in the 20 MB is DSS and PS Forms. If the minimum O/S is installed, EBS, EUT & EIT, the disk usage is 4 MB. In other words, there has been no substantial increase in disk space requirements. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB072 Pg003 WARNING: Error 12 when opening a printer which is configured. 7.5B System 3000/4000 could generate error 12's even though the printer is configured in the 'configure' utility. If the system has more than 22 printers configured, the entries after the 22nd one will be deleted from the /etc/printers file if ANY changes are made using the 'configure' utility. ORIGINATOR: Dan Arteritano SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB072 Pg004 FIB 00073 05/11/90 *** OS Release 7.5B*17 is Available to Cure Terminal Hangs/Modem Probs *** UPDATE SPX, Release of 7.5B*17. Effective Immediately!!!!!!! Purpose of the release: o Fix for the terminal hang and dial-up MODEM access problem. o 'rcopy' will transfer files over LAN without corrupting the files. o The PDF files for the PT-4225, PT-4226, PT-4227, PT-4228 and PT-4229 will be included on the Operating System tape. Procedure to order 7.5B*17 for EXISTING 7.5B*13 and 7.5B*15 customers: o Send a new Sales Order using the existing N/C 7.5B market codes, see page 4, of 11/89 MA 757, of BOSS/IX Software in the Price Book. o Reference the original Sales Order number (ETR) and indicate POLICY REPLACEMENT. o The order will be filled from the factory and sent at N/C to the customer. ORIGINATOR: Dan Arteritano SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB073 Pg001 FIB 00074 07/06/90 *** Helpful Software Tools [ WPSF 597 A1 ] *** TOOL #1: This is a tool to find a file which you know exists but the path name is not known. For ease of use you can create a macro or an executable file to execute the command. THE COMMAND IS: ls -a -l -p -r / | match $1 To create a command, ved a file '/bin/locate' and enter the above line. Exit ved and use the 'filemodes' command to make it executible. Enter: filemodes +x +x /bin/locate Now you can execute the locate command by entering: locate Another option is to create a macro called 'locate'. Enter: #b locate ls -l -a -p -r | match This can also be executed by entering the following: locate This gives 2 ways to find files and their full path names. TOOL #2: This tool is designed to easily find the system error description that may correspond to a BASIC error or a system error. EXAMPLE: Try to open a printer in BASIC and an error 255 occurs, enter "error" and the following is displayed: Basic error code: 255 System error code: -254 Now to find the description of the error -254 the file /etc/comerr.list must be displayed by entering the following: cat /etc/comerr.list |p This will display the file one line at a time. The specific error can be found by entering the following command: match 254 /etc/comerr.list |p This command will display all the lines which have "254" in them. NOTE: Do not use the "-", because the command thinks that anything preceded by a "-" is an argument. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB074 Pg001 The quickest way to find the description of the system error is to create a macro or an executable file. To make an executable file ved /bin/mtch and enter: match $1 /etc/comerr.list |p Exit ved and use filemodes to make the file executable: Enter: filemodes +x +x /bin/mtch You can also create a macro called 'mtch': Enter: #b mtch do 'match $1 /etc/comerr.list |p' This is a second way to quickly find a description of a system error. TOOL #3: This tool is to display the terminal number and operator ID of the terminal which they are currently logged onto. The reason for this tool is that usually when an operator enters "who" in admin all logged on terminals are displayed, this command will ONLY display the operator of the terminal they are on. 1. TO CREATE A MACRO Enter: #b whoami basic 'print fid(0), " ",WHO' 2. CREATE AN EXECUTIBLE FILE Enter: ved /bin/whoami Enter: basic 'print fid(0), " ",WHO' Press: CTRL-C and Enter: Y Enter: filemodes +x +x /bin/whoami Enter: whoami To display your "T" number and operator id. TOOL #4: This is a Helpful Hint to deactivate the key. We all know what a nuisance the key is being so close to the key. There is a way to make the key harmless so that it will not perform a . Here are the 2 methods: o For 7.4 systems and above use the utility 'sconf'. - Select option 3 'Modify OS Parameters': - Change item 18 (it's on the 2nd screen), Select item 18 and the following prompt will appear: Type the Linekill character (key), for no change: Press: CTRL-X (since CTRL-X is not used by the system) CTRL-X will be the character. Press: 3 times and the vconf parameters will be saved. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB074 Pg002 o For 7.2 systems you must use the vconf command. Enter: mount /dev/boot /mnt Enter: vconf /mnt/etc/conf linekill=24 -save Enter: unmount /mnt After the system is rebooted the key will NOT produce a for both of the examples above. The key will produce '^?' when hit, a will delete it and data entry can continue. TOOL #5: This tool is used to send messages to terminals which are not logged on to the system. It is very simple: Enter: echo "Put your message here"|tee /dev/tty* This a good way to send messages to terminals before going into single-user mode to do a backup. TOOL #6: This tool is to display directories and file names across the screen rather than just down the left side of the screen. A macro or executable file can be created to execute the command. o To create a macro: Enter: #b lc ls | pr l=1 w=80 -5 -nh o To create an executable file: Enter: ved /bin/lc Enter: ls | pr l=1 w=80 -5 -nh Press: CTRL-C Press: Y Enter: filemodes +x +x /bin/lc The command is now executable and will display the directories and file names in columns. ORIGINATOR: Dan Arteritano SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB074 Pg003 FIB 00075 10/11/90 *** Program to Run Unattended Backup on HCC Tape [ WPSF 625 ] *** TYPE: Informational PURPOSE: The enclosed program is a working example that may be used to run an unattended backup. PROCEDURE: To get the program started put the following line in the /etc/startup file. exec o=BACKUP.LOG e=BACKUP.LOG -a -c -d /bin/basic s=128 -nr pgm=AUTOBAK BACKUP.LOG will contain the messages that normally print on the screen. HCC.LOG will contain the status of your backups. This program will start each time the system is loaded. If you want to stop it, just kill the PID for this task. Most parameters such as backup time, weekend backup, user messages may be changed to meet individual user needs. 0010 REM AUTOBAK IS A PGM TO DO A UNATTENDED BACKUP ON SPX 0020 LET A=TIM 0025 REM GET SYSTEM TIME MUST BE SET FOR 24 HR CLOCK 0030 IF A=23 OF A>23 AND A<23.2 THEN GOTO 0040 ELSE GOTO 0150 0035 REM IF ITS BETWEEN 11.00PM AND 11.06PM WE DO A BACKUP 0040 LET Z$="date >HCCDATE" 0041 GOSUB 0500 0045 OPEN (1)"HCCDATE" 0050 READ RECORD(1)B$ 0060 IF B$(1,3)="Sat" OR B$(1,3)="Sun" THEN CLOSE (1); WAIT 360; 0060: GOTO 0150 0062 REM IF TODAY IS SATURDAY OR SUNDAY SKIP THE BACKUP 0065 CLOSE (1,ERR=0070) 0070 !write -all -n "WE WILL START A COMPLETE BACKUP IN 3 MINUTES 0070: PLEASE SIGN OFF" 0072 WAIT 180 0075 REM NOTIFY ANY USERS ON THE SYSTEM 0080 LET Z$="tsave dev=ts -i -r -stat /* >>HCC.LOG" 0085 GOSUB 0500 0090 REM DO A COMPLETE BACKUP ANY VALID TAPE COMMAND MAY GO 0090: BETWEEN THE QUOTES 0100 LET Z$="tcompare dev=ts -e >HCC.LOG" 0105 GOSUB 0500 0110 REM DO A TAPE TO DISK COMPARE 0150 WAIT 300 0155 REM WAIT 5 MINUTES BETWEEN LOOPS 0160 GOTO 0020 0500 SYSTEM Z$ 0510 RETURN ORIGINATOR: Steve Binderup SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB075 Pg001 FIB 00076 10/12/90 *** Performance Problems Related to Serial Printer Use *** SYMPTOM: System degradation when a serial printer configured for XON/XOFF flow control is in use. PROBLEM DETERMINATION: Check the port configuration for the printer and the rated printer speed in characters per second (CPS). The baud rate should be set to keep the printer busy but not too fast or the XON/XOFF activity will be excessive and slow the system down. FIX: Set the baud rate (or bits per second) for optimum value based on the printer speed. This can be calculated as follows: Normal character setup is 7 data bits, odd parity, and 1 stop bit which translates to (in bits): 1 - start bit (not configurable but always there) 7 - data bits 1 - parity bit 1 - stop bit -- 10 - total data bits per character The exact baud rate to match the printer's speed is: CPS * 10 The optimum baud rate is the next higher configurable baud rate. example - 45 CPS daisy wheel printer 45 * 10 = 450 baud next higher configurable baud rate = 600 baud ORIGINATOR: Norm Jones SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB076 Pg001 FIB 00077 11/28/90 *** tcompare Reports Erroneous Miscompare [ WPSF 638 ] *** Problem: Occasionally tcompare reports an erroneous miscompare. SYMPTOM: tcompare will report error -98's and cannot find /usr/file on 60 and 120 MB MCS tape drives even though the data on the tape is correct. SOLUTION: Patch 14 can be ordered for tcompare, from Product Support. The versions available are: SYSTEM OS Level ------ -------- 2500/3000/4000 7.4B 2000 7.5B 2500,3000,4000 7.7B The fix is currently available as a patch only because the it . increases the overall time to do a backup and compare. ORIGINATOR: Dan Arteritano SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB077 Pg001 FIB 00078 01/02/91 *** Release 7.5B*20 Differences [ WPSF 167A ] *** BOSS/IX 7.5B*20 STEVE BINDERUP 12/90 167-ADDENDUM BOSS/IX 7.5B*20 is now available for release. This release has three main enhancements: o Power failure management. o PDF Version stamping. o Presentation Services 3.3B There are many error/bug corrections in this release. Refer to Software Announcement 167 for installation and configuration information. This addendum will only cover differences between *17 and *20 T A B L E O F C O N T E N T S 1.0 POWER FAILURE MANAGEMENT. . . . . . . . . . . . . . . . . . .1 1.1 HOW IT WORKS . . . . . . . . . . . . . . . . . . . . . .1 2.0 PDF VERSION STAMPING. . . . . . . . . . . . . . . . . . . . .1 3.0 SUPPORT FOR PRESENTATION SERVICES 3.3B. . . . . . . . . . . .2 4.0 BUG FIXES . . . . . . . . . . . . . . . . . . . . . . . . . .2 1.0 POWER FAILURE MANAGEMENT This section describes the method used to handle power failure conditions on SPx 3000/4000 systems. The goal of this feature is to provide the means for a orderly shutdown to preserve data integrity in the event of a power failure. This new feature is supported with the Topaz and Exide power protection products. 1.1 HOW IT WORKS At the time of a power failure, a signal is sent to the system by the UPS and a child task of process 1 is started up. This process will read an optional user-created file (/etc/pftime) where the site may specify the expected reserve power of the UPS unit. If this file is not present, the process will delay shutdown by 15 minutes. If the file is present the powerfail process will display the line of text on each logged on terminal and the shutdown will be delayed by the numeric value in this line of text. If power is restored before the shutdown is invoked, the power fail process will abort the shutdown countdown. The /etc/pfttime file is simply one line (up to 80 characters) of free form ascii data, which contains a numeric value anywhere on the line. The remainder of the line may contain any non-numeric data of your choice such as "Reserve time on UPS is 60 minutes". SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB078 Pg001 The system will also keep track of UPS time during the last 24 hours. If your site has had multiple blackouts in the day, the system will have a record of how long the UPS was in use. If you have used your UPS for 10 minutes during the last 24 hours and your shutdown time is 15 minutes, if you have a power failure, the system will shutdown in 5 minutes. 2.0 PDF VERSION STAMPING Introduced with *20 a version stamp will be on each printer definition file. To display the PDF version number, create the following program: 1. ADMIN> cd /etc/ptrtbl 2. ADMIN> basic s=100 3. 10 BEGIN 20 INPUT (0) 'CS',"ENTER PDF NAME: ",NAME$ 30 OPEN (1,ERR=20)NAME$ 40 READ RECORD (1,IND=0,SIZ=8)SIMPLE$ 50 IF SIMPLE$<>".SIMPLE." THEN CLOSE(1);PRINT "NON MAI BASIC FOUR 50: PDF";STOP 60 READ RECORD (1,IND=140,SIZ=24)REC$ 70 LET VERSION$=REC(1,5),PDFNAME$=REC$(6) 80 PRINT "PDF VERSION NUMBER IS: ",VERSION$," NAME: "PDFNAME$ 90 END 4. SAVE "PDFVERSION" 5. RUN NOTE: PDF's created by the user or previously released will not have version numbers and therefore, will not display. 3.0 PRESENTATION SERVICES 3.3B SUPPORT Some of the highlights of PS 3.3B are: * Allow gradual conversion of applications to forms. * Modified refresh mnemonic. * 'START' at last field in IOLIST. * 'RB' on message menemonic. * Multiple configuration files. * Modified required field validation. * Addition of color. * Increased Performance in menus and repeating groups. * More than 999 help ID's. Detailed descriptions may be found in Software Announcement 177. 4.0 BUG FIXES The following is a list of bug fixes for 7.5B*20 * Slave printer output transparency. * PT-4218 Printer without spooling ignores ESC sequences. * Configuring more than 22 printers on reboot will ignore above 22. * Ports configured for 2 stop bits only uses 1. * Ghost tasks fail to recognize 'lf'. * Multi-key retain buffer option loses data. * Read after extract causes an error 0. * Composite field is not created on multi-key files * PT-4217/4218 timeout is too long at boot. SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB078 Pg002 * trestore defined files for their maximum size when restoring them to disk. * "fchange" can modify a file to be larger than the disk it resides on. * PT-4223 printer offered twice in configuration utility. * Error 2 is generated instead of an Error 1 after a READ of IND=0 of an INDEXed file that was written with a Error 1. * "brenumber" utility does not renumber TBL= statements. * who -1 does not show ports past tt34 * Spool files overwritten at boot time. * A printer that had the vfu programatically loaded would have the default vfu loaded after printer is off line and times out. ORIGINATOR: Steve Binderup SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB078 Pg003 FIB 00079 04/16/91 *** SPx 7.5B*22 Release [ WPSF 703 ] *** SPx 7.5B*22 Release Dan Arteritano Type: Information Purpose: Announce the Release of 7.5B*22 for SPx. 7.5B*22 has been released for the MAI 2000, MAI 2500, MAI 3000 and MAI 4000. It was derived from 7.5B*20 and contains enhancements and corrections to the 7.5B*20 Operating System. There are NO installation procedure changes for this release. The fixes in this level are: INDEXed files with more the 32,000 records would be empty after 'frepair' was run on them. The chance for system crash with a Crash Code 30 or Excessive Interupts has been further reduced on this level. ATP, Async Transfer would not work on 7.5B*20 because of a problem in the 8-way driver. ORIGINATOR: D. Arteritano SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB079 Pg001 FIB 00080 09/17/91 *** Power Failure Management (UPS Shutdown) *** SUBJECT: SPx 3000/4000 Power Failure Management TYPE: Informational PURPOSE: To provide clarification for Power Failure Management. o MARKETING ANNOUNCEMENT # 1019 12/90 MAI SYSTEMS offers two versions of UPS's, a 1kVA and 3kVA, that match the power requirements for the SPx 3000 and 4000. UPS MKT SYS SYS POWER UPS POWER REMAINING BATTERY CABLE CODE TYPE REQUIRED DELIVERED POWER BACKUP ------------------------------------------------------------------ ZS002AA 3000 .6kVA 1.0kVA .4kVA 10 MIN. UR011AA ZA056AA 4000 1.1kVA 3.0kVA 1.9kVA 13 MIN. UR012AA UR011AA (1kVA) or UR012AA (3kVA/5kVA) UPS Interface Cable should also be ordered to take advantage of the Power Failure feature. Remaining Power is the power that can still be provided by the UPS, outside the system requirement, that may be used by other peripherals. The peripherals that would use this remaining power would be those required during a power outage condition; e.g. console terminal and printer. o SOFTWARE ANNOUNCEMENT # 167 ADDENDUM 12/90 The Power Failure Management software was first announced in the BOSS/IX 7.5B*20 addendum. This feature is supported with the Exide power protection products. When the system detects a power failure, it will read the user-created file '/etc/pftime' and use the numeric value for the minutes to delay shutdown. Depending on which unit you have, this value must be adjusted according to the grid above. For example, you have the UPS on a 3000 and the Battery Backup Time is 10 minutes. Enter the following: ved /etc/pftime (to create the file) System to shutdown in 5 minutes. (to set time to 5) ** CTRL+C (to exit 'ved') Y (to write the information to '/etc/pftime') If you do not create this file, the system will default to 15 minutes, which is longer than the battery backup time and you will not receive a proper shutdown. ** Choose your time carefully! The ratings on the Backup units are based on being fully charged over a 24 hour period. If a power outage occurs, the unit needs time to recharge. In other words, if the battery is in use for 5 minutes, as in the example above, the next time the system goes down only 5 minutes are available. (Rated time - time used, i.e. 10 - 5 = 5) SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB080 Pg001 ORIGINATOR: MBF SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB080 Pg002 FIB 00081 01/02/92 *** SPx Data File Integrity Check & File Repair Procedure *** The following step-by-step procedure should be performed anytime a non-standard system shutdown has occurred (power failure, system crash, system hang, etc.) and is based on the system having successfully completed an automatic filesystem repair. This procedure is recommended for use by the system administrator. A qualified system's administrator should have completed MAI's "Managing Your BOSS/IX System", taught at MAI education centers. PLEASE MAKE SURE YOU HAVE A CURRENT COMPLETE BACKUP. If you do not have a current backup, please do one before executing this procedure. You may need to restore your backup if the file repair utility is not able to fix all the data files. NOTE: Use a different set of tapes from your previous backup! 1. Login as "admin" on the system console (T0). 2. Have all users completely log off the system prior to repairing the data files. You can check which users are still logged on the system by using the "who" command at the system prompt. ADMIN> who 3. After all users have logged off the system, shut the system down into single-user mode by entering the following command: ADMIN> shutdown 0 -s It takes several minutes for the system to completely shutdown into single-user mode. Enter the following command: ADMIN> fichk / -f After the command is entered, a filelist of the files that need to be repaired is created. It may take several minutes for the list to be created. After the list is created, the following message is displayed: ______________________________________________________________________ |Filelist '/util/fl/fichk.f' contains filenames that lack integrity. | |______________________________________________________________________| 4. Run the file repair utility by entering: ADMIN> frepair 5. The utility begins with a multiple choice menu containing the parameters for the utility to use during the analyze and repair process. To change the selection of an item, type the item number (without RETURN). An asterisk next to an item, indicates that the item has been selected. Please select the following items: (continued on next page) SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB081 Pg001 ______________________________________________________________________ | File Analysis and Repair Utility | |______________________________________________________________________| | 1. REPAIR MODE 2. FILE SELECTION | | analyze single file | | *analyze & repair *selected files | | retire bad block | | | | 3. REPORT DEVICE | | terminal | | printer | | *file | | | | Type number to change selection, when all are correct: | |______________________________________________________________________| 6. A warning message is displayed on the screen: ______________________________________________________________________ | WARNING: Files or data might be lost, Proceed? (yes/no): yes | |______________________________________________________________________| Type in 'yes' 7. The screen is cleared and you are prompted to enter the report file name. Enter the name in the following format: repair.MMDDYY where: MM=month DD=day YY=year ______________________________________________________________________ | Working directory: / | | | | Type report file name: repair.MMDDYY | |______________________________________________________________________| 8. The screen is cleared and you are prompted to enter the filelist name that contains the file or files to be repaired. ______________________________________________________________________ | Working directory: / | | | | Type a file or filelist name to add, when done: fichk.f | |______________________________________________________________________| 9. Files that need repair will be listed on the screen and a total of file names added appears at the bottom. You are done, so press . The screen is then cleared and you are prompted to edit the list of filenames. At this point, press . ______________________________________________________________________ | Edit list of names | | 1. Add | | 2. Delete | | 3. Display | | 4. Sort | | 5. Change environment | | 6. Save | | Type number of selection, to end: | |______________________________________________________________________| 10. The system will ask if you want to specify template files, answer no. _____________________________________________________________________ | Do you want to specify template files for keyed files? no | |_____________________________________________________________________| SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB081 Pg002 11. When completed, the screen will flash "PROGRAM IS DONE" and take you back to the ADMIN> prompt. Type in 'ls -l /lost*' and check out the lost files. You may need to contact your application software vendor for file identification. ADMIN> ls -l /lost* 12. To bring the system back into multi-user mode, hold down the CTRL key and the letter 'd'. The system will prompt: _____________________________________________________________________ | single, multi, shutdown or powerdown | |_____________________________________________________________________| 13. Type in the entire word: shutdown. Reboot (start up) the system as you would normally. !@$! ORIGINATOR: NSC SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB081 Pg003 FIB 00082 MAI COMPANY CONFIDENTIAL 08/18/92 *** "Invalid Date" message using starting & ending dates in utilities *** NOTE: I found the following bug on 3000 systems running 7.5B*17 & *22. BUG: When you enter a utility (ex: finfo and tsave) there is an option to select a files or files. If you select files you either enter a filelist name or a group of files. After completion the next screen has an option #5,Change Environment. On entering this option you have options 2 and 3 which give you the opportunity to change the starting and ending dates. If you enter a date in a leap year (ex: 1988,1992) starting with the month of February and till December and the day is either the 30 or 31 of that month you will get a message saying you entered an invalid date. For the month of February that is obviously true but the utility also sees as invalid all the 30 and 31 of every month in the leap year (except January). WORKAROUND: In tsave I used the command line with the -since option and it worked fine with any date. ORIGINATOR: Kim Yaworsky SOFTWARE-BASIC FOUR-BOSS/IX BBVII-------------------FIB082 Pg001