MAI COMPANY CONFIDENTIAL FIELD INFORMATION BULLETIN SERVICE GROUP(S): MINI MFG: BASIC FOUR NACS TYPE(S): N001 MFG. MODEL(S): BOSS/VS BBVIII & BBIX CATEGORY: SOFTWARE DESC: O.S. & UTILITIES *** TABLE OF CONTENTS AS OF 08/19/94 *** FIB 00001.Starting with Rel 8.2A*34 "CRASHINFO" is avilable...........03/22/90 FIB 00002.BOSS/VS security file information...........................11/22/83 FIB 00003.Prior to Rel 8.2C disk HD/CYL errors can cause system dumps.12/16/83 FIB 00004.Lost Space message in directory list - release 8.2C.........03/06/84 FIB 00005.Direct file pointer problems using IND= with EXTRACT - prior08/21/84 FIB 00006.BASIC Problem on O.S. releases prior to 8.5.................02/20/85 FIB 00007.Incorrect program results due to PRECISION handling - 8.4B/C05/20/85 FIB 00008.Release.8.4C Software Announcement..........................05/31/85 FIB 00009.Incorrect Status/Sector displayed on disk to disk backup - R06/17/85 FIB 00010.Release 8.4D Software Announcement..........................06/18/85 FIB 00011.Release 8.5A initial information............................10/23/85 FIB 00012.BOSS/VS release 8.5B information............................01/03/86 FIB 00013."Rule of thumb" Memory requirements with 8.4E/8.5 releases..04/07/86 FIB 00014.Message "SPACE MAP IS xx, SHOULD BE xx" on DISKANALYZER.....04/10/86 FIB 00015.Display differences with INSTALL.CONFIG on 8.5C/9.5C........04/23/86 FIB 00016.Potential Keyed file corruption - release 8.5B/C............06/16/86 FIB 00017.Write-through default on File Create does not work - Rel 8.507/03/86 FIB 00018.Information for computing the Dump Area size................07/03/86 FIB 00019.Error 47 in startup of Auto Dial utility - 8.4E/8.5C/9.5C...10/23/86 FIB 00020.Differences with CONFIG.MGR utility (replaces INSTALL.CONFIG11/13/86 FIB 00021.Rel 8.4E has problem if disk errors occur during SAVERESTORE03/24/87 FIB 00022.Release 8.6A/9.6A Software Announcement.....................04/28/87 FIB 00023.MPx to 13XX program transfer may cause ERROR 20.............07/07/87 FIB 00024.Down.Load Utility Option to Display Device ISDC/Line Numbers08/04/87 FIB 00025.Release 9.6A/8.6A is now available..........................08/11/87 FIB 00026.Character position and overprinting with OS 9.6/8.6.........08/11/87 FIB 00027.Use.EXTTAPE Utility to restore Configuration records on 8.4 08/24/87 FIB 00028.Warnings and Cautions for Release 9.6A/8.6A.................09/17/87 FIB 00029.Release 8.4E Software Announcement..........................10/01/87 FIB 00030.Release 8.5D/9.5D Software Announcement.....................10/01/87 FIB 00031.Release 8.5E/9.5E Software Announcement.....................10/01/87 FIB 00032.Release 9.6/8.6B is now available...........................10/12/87 FIB 00033.The Use of EXTTAPE with MPx 8.4 Configuration Records.......10/30/87 FIB 00034.Warning During System Configuration Record Install - 8/96A..10/30/87 FIB 00035.Bootable O.S. & Diagnostic Tape Information.................11/02/87 FIB 00036.8.5-9.5 Spooler class definitions are not converted on 8.6-912/02/87 FIB 00037.Terminal model numbers are used in TERM.CONFIG on 9.6A and u12/02/87 FIB 00038.Release 9.6B/8.6B Software Announcement [ WPSS 151 ].......12/02/87 FIB 00039.Wrong message for Key Too Long on release 9/8.E.............12/02/87 FIB 00040.Incorrect spec. char. file names returned on DIR function - 12/02/87 FIB 00041.Operator Flags on BOSS/VS 9/8.6 [ WPS 411 ].................12/29/87 FIB 00042.8-bit mode doesn't work on letter quality printers [ WPS 39902/12/88 FIB 00043.MPX Spooler change in pitch support on 8/9.6C OS [ WPS 425 02/16/88 FIB 00044."NOT CONVERTED" message in !CONVERT/!CONVERTSP - 8/9.5 [ WP02/16/88 FIB 00045.Spooler Error Codes returned to BASIC on 9/8.6 [ WPSF 428 ].03/28/88 FIB 00046.Use caution when selecting drive #s on tape update [ WPSF 4404/20/88 FIB 00047.Install new Configuration Record before adding fixed disk...05/20/88 FIB 00048.Helpful Programs to Spot Files Almost Full ( ERR 2s) [ WPS 406/01/88 FIB 00049.Printers lose Top of Forms - affects 8/9.6A [ WPS 462 ]....06/01/88 FIB 00050.Automatic Start-up for FTF after Type 1 Load [ WPSF 468 ]..06/23/88 FIB 00051.BQR ERRs 10/14 on Files Transported from an SPX.............06/23/88 FIB 00052.Release 9.6C/8.6C Software Announcement [ WPSS 157 ]........08/16/88 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------Table Of Contents Pg01 of 02 FIB 00053.Enhancements/Considerations with Release 8.6C/9.6C [ WPSF 4708/16/88 FIB 00054.RECONSTRUCT at 8.6/9.6 MUST have Sufficient Disk Space [ WPS08/16/88 FIB 00055.ASG Software Requires Installation of Key after Upgrade [ WP08/16/88 FIB 00056.Restricting Log-on on 8/9/10.6 Level Systems [ WPSF 501-1 ].10/24/88 FIB 00057.8/9/10.6E Release Announcement [ WPSF 501 ].................10/24/88 FIB 00058.CONFIG.DISPLAY & CONFIG.TAPE Utilities on 8/9.6C [ WPSF 47210/24/88 FIB 00059.Warnings & Special Considerations for Rel. 8/9.6C [ WPSF 47212/19/88 FIB 00060.Ghost Task not Released - BCOM at n.6B/C [ WPSF 483 ]......12/19/88 FIB 00061.Escape Trapping notes [ WPSF 439 ].........................12/22/88 FIB 00062.9xxx System Hangs While Running DOWN.LOAD - 9.6A/B [ WPSF 412/22/88 FIB 00063.Notes on Using the 'KL' Mnemonic [ WPSF 502 ]..............12/28/88 FIB 00064.Use EXTTAPE for Config Records below 8/9.6A [ WPSF 505 ]...12/28/88 FIB 00065.System Hang/Dump Recovery Procedures [ WPSF 506 ]..........12/28/88 FIB 00066.Release 10.6E/9.6E/8.6E Software Announcement [ WPSS 161 ].02/08/89 FIB 00067.DOWN.LOAD occurs during execution of BCOM [ WPSF 511 ]......02/08/89 FIB 00068.MPx Memory Sizing [ WPSF 433 ].............................02/08/89 FIB 00069.ERR variable changed on Rel 10/0/8.6E PS 526]...............04/18/89 FIB 00070.Warnings & Special Considerations for 8/9/10.6E [ WPSF 523 04/18/89 FIB 00071.Dumps 2,6,1,10 Caused by User Defined Function [ WPSF 536 ]05/12/89 FIB 00072.MVP Bar Code Problems when upgrading from 8/9.4 & 8/9.5 to 808/17/89 FIB 00073.Explanation of Disk Fragmentation [ WPSF 552 ].............08/31/89 FIB 00074.Warnings/Special.Considerations for BOSS/VS n.6G [ WPSF 5510/27/89 FIB 00075.Unexpected Error 12 Message in "COMM" on OS n.6G [ WPSF 56010/27/89 FIB 00076.Possible Data Loss using !RECONSTRUCT 8.5 & Higher [ WPSF 5710/27/89 FIB 00077.MAGNET/FTF Completion code 1 on BOSS/VS n.6G [ WPSF 565 ]..11/22/89 FIB 00078.Software Announcement 8/9/10.6G.............................11/22/89 FIB 00079.Each Disk Set-up as Separate Family when Shipped [ WPSF 57901/17/90 FIB 00080.8/9/10.6G*45 has been released [ WPSF 589 ]................01/17/90 FIB 00081.Form Feed not Generated on Stopped or Cancelled Jobs [ WPSF 01/17/90 FIB 00082.Possible Data Loss during Directory Reconstruct [ WPSF 591 01/17/90 FIB 00083.DATAWORD II VDT Emulation Causes Dumps on n.6G OS [ WPSF 6003/05/90 FIB 00084.Diskanalyzer Reconstruct VS Reconstruct [ WPSF 608 ]........03/22/90 FIB 00085.Software Announcement 8/9/10.6H.............................05/16/90 FIB 00086.IMLC Won't Work After Upgrading to 10/9/8.6H O.S............05/21/90 FIB 00087.!PHOTO & 'TR' Lose Screen Data (Garbled Data Received)......08/17/90 FIB 00088.Release 8/9/10.6H*41 Available to Fix These Problems........10/10/90 FIB 00089.Upgrade Procedure for TBC & MAGNET for M.6H Reguired [ WPSF11/27/90 FIB 00090.Notes & Special Considerations for BOSS/VS M6H [ WPSF 634 &01/07/91 FIB 00091.System Slowdown with Serial 4220 on Single Processor System.12/31/91 FIB 00092.Release 8/9/10.7A Software Announcement.....................01/24/92 FIB 00093.HCC On-Line Backup Utility..................................01/27/92 FIB 00094.Patch 55-Spooler/Enhancer Patches available for R7A [WPSF 7806/17/92 FIB 00095.Error 503's on Advanced Series Systems [WPSF 796]...........09/11/92 FIB 00096.Release N.7 BROADCAST and read timeout problem [ WPSF 799M 07/19/94 FIB 00097.Program to convert ERRLOG dump numbers to four-tuple on 8.4 01/15/93 FIB 00098.Installing keys for ALB (Auditor's LogBook) & OLB (OnLine Ba01/26/93 FIB 00099.Release 8/9/10.7B Software Announcement.....................10/29/93 FIB 00100.BASIC writes to tape in lengths that are multiples of 4.....05/12/94 FIB 00101.Using "unattended backup" with 1.2GB 1/4" MCS...............08/18/94 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------Table Of Contents Pg02 of 02 FIB 00001 03/22/90 *** Starting with Rel 8.2A*34 "CRASHINFO" is avilable *** A new feature in the program DUMPTOFILE is the display of crash information which caused the system to dump. This new feature is available on software release 8.2A*34 and above. This information is displayed on the screen of the terminal running the DUMPTOFILE program and a prompt is provided for a hard copy output. It would be extremely useful to keep a hard copy output for trouble- shooting intermittent problems. The CRASH INFO contains the following information: a. PCB number is the Process Control Block number which called for the system dump. Each terminal has its own PCB number, which is assigned by the system at the time an escape is detected from the terminal at log-on time. b. NAME displays the name of the process which caused the dump. It can be a terminal I.D., ghost I.D. or a system process. A system process is proceeded by a * such as *SHADOW MANAGER process, and is part of the operating system. This is useful in determining who or what caused the dump, is it the same terminal calling the dump or maybe the same system process. c. CPU # is the number of the CPU which was processing the data which called for the system dump. Several dumps all having the same CPU # might indicate a hardware problem with that CPU set. d. STKSEG is the stack segment number. This is used to find the segment table entry. The entry gives the information needed to find data in memory for a detailed analysis and is used by Engineering. e. SYSTEM ERROR NUMBER is the four-tuple of the dump. This should be the same number which flashed on the HVDT screens and/or T0 while the system was processing the dump. f. SYSDUMP MSG is the four-tuple error text. g. TIME OF SYSTEM DUMP is the time at which the dump occurred. h. DATE OF SYSTEM DUMP is the date on which the dump occurred. i. DISK IOCBs WITH ERRORS displays the information needed if the dump was caused by a disk abort error. If the dump was caused by a disk or if a disk had an error at the time of a dump the IOCB number, disk address, status, cylinder, head and sector information is displayed. This is extremely useful information if the dump numbers are 28, 2, 1, 25 or 28, 8, 1, 25. ORIGINATOR: J. KANZLER SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB001 Pg001 FIB 00002 11/22/83 *** BOSS/VS security file information *** There are two areas in the security file that contain the user level of an account. The first area is the creation level and is determined when the account is created. The second level is the active level. It contains the current user level of the account. The the security system allows allows any user to change his user level to a lower level, i.e. a user with Level 3 status can change his status down to level 0. The system checks the active user level befor allowing the user to run specific utilities such as GENSSN and CONFIG.MGR. Not all utilities check the the active user level before allowing the user access, i.e. SECURITY will check the priviledges of the original user level. The original user level and active user level are stored in the security file. In the event that an account is to be permanently changed to a user level lower then originally created, it is recommended that the user account be deleted and re-entered. ORIGINATOR: K. SHON SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB002 Pg001 FIB 00003 12/16/83 *** Prior to Rel 8.2C disk HD/CYL errors can cause system dumps *** Software release 8.2C and above now has I/O command change in it that does a rezero and fault clear after a disk HD/CYL error occurs. Previous to this release, if a HD/CYL error was encountered during a critical disk operation, the system would dump. The most common dumps that this error caused were 28,2,1,25 and 28,8,1,25. To determine if a system has this problem run the program called 'DUMPTOFILE' after the dump. If a disk error caused the dump this program will return disk IOCBS with status information. A HD/CYL error would be Hex status 80040000. If system is not at software level 8.2 the dump will have to be sent to BFISD for interpretation. It is suggested that a customer be asked to upgrade to software release 8.2C if they do not want these dumps to occur. It should also be noted that if the HD/CYL errors are excessive you probably have a disk problem and these errors will be recorded in the ERRORLOG with too high a frequency rate. ORIGINATOR: J. KANZLER SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB003 Pg001 FIB 00004 03/06/84 *** Lost Space message in directory list - release 8.2C *** When doing a directory with attributes on the 8.2C release, the message THIS FILE MAY HAVE LOST AVAILABLE SPACE displays on files that are OPEN and have been modified. Log all terminals off and run a directory list on the individual file again, if the message persists reconstruct with DISKNALYZER. ORIGINATOR: S. BROWN SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB004 Pg001 FIB 00005 08/21/84 *** Direct file pointer problems using IND= with EXTRACT - prior to 8.4B *** Releases prior to 8.4B have a DIRECT file pointer problem if EXTRACT is used with IND=. The pointer will be positioned incorrectly. ORIGINATOR: P. ROBERTSON SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB005 Pg001 FIB 00006 02/20/85 *** BASIC Problem on O.S. releases prior to 8.5 *** Certain BASIC programs have been found to produce peculiar errors and/or dumps. These problems arise from a problem in the BASIC run-time system. The BASIC programs share two common traits for this condition. The first trait is that the program must have deleted or edited compound statements (i.e. statements with semicolons, FORs, and GOSUB). As more compound statements are deleted or edited, the chances of this problem occurring increases. The second trait is that the program or the user must retry a statement which has recently had a "normal" error. This usually entails using RETRY logic from the program or the RUN command from console mode. The current solution for level 8.4B or below is to recompile the BASIC program using CONVERT or EDIT. In level 8.4C, this problem will be partially fixed. Programs will not have to be recompiled. However, any BASIC programs, from previous releases which have problems, will still have to be recompiled. In level 8.5A, BASIC will fix any program loaded into memory. ORIGINATOR: MBF SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB006 Pg001 FIB 00007 05/20/85 *** Incorrect program results due to PRECISION handling - 8.4B/C *** Releases 8.4B/C do not pass the PRECISION level to a called program. Prior releases (and later ones) passed the PRECISION level on a call. This may cause unexplained answers from working software. PRECISION can be set within the called program if this is a problem, or upgrade. to a later level. ORIGINATOR: P. SUPPORT SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB007 Pg001 FIB 00008 05/31/85 *** Release 8.4C Software Announcement *** 1.0 INTRODUCTION MAI Basic Four, Inc. is pleased to announce that a new software release, 8.4C, is now available. This is the recommended software release for all Basic Four\ System 810 and MAI\ 8000 Series systems. The following summarizes the new features contained in the Level 8.4C release: o BOSS/VS COBOL o Buffered Magnetic Tape Controller 1/2-inch tape support o DEDICATE with expanded error reporting o Enhanced ISDC OS for 4-way, 8-way and 16-way o FILE SIZE Utility o New File SystemF o Changes to Saverestore utility o New terminal Errorlog utility It is mandatory that the MCS and ACS PCBAs be updated to revision level L. If a BMTC is in use on the system the ACS PCBA must be updated to revision level T. Without the proper revision levels, the system will not load. It is also mandatory that the ISDC subtype be adjusted on all ISDCs to the correct setting before installation. The ISDC (8-way) subtype, switch SW2 (location 1A), should be set to 0. A new configuration record is not required unless this release coincides with the purchase of new hardware or chargeable software. Installation and upgrade procedures are fully documented in this announcement. Please read the upgrade section (4.01) prior to installing any new operating system. 8.4C BOSS/VS Software Announcement Table of Contents 1.0 Introduction 2.0 History 3.0 New & Enhanced BOSS/VS Features 3.01 Configurations 3.01.1 8000 Series 3.01.2 System 810 3.02 Languages 3.02.1 BOSS/VS COBOL 3.03 Utilities 3.03.1 DEDICATE Utility 3.03.2 GLOBAL SEARCH AND REPLACE (GSR) Utility 3.03.3 FILESIZE 3.03.4 FIND LOST SPACE SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB008 Pg001 3.04 Hardware 3.04.1 Buffered Magnetic Tape Controller 3.04.2 Printer Support 3.05 Operating System 3.05.1 Intelligent Serial Device Controller 4.0 Installation Procedures 4.01 Upgrade Procedures for 8.4B to 8.4C 5.0 Related Documentation 2.0 HISTORY Release Current Status Description 8.1A Obsolete Introduction of the System 810 hardware and BOSS/VS software. 8.1B Obsolete Enhanced features include: 31 logical units in BASIC, increase in file system cache from 208 to 225 unique files, MULTIREELSR, family image backups, SAVERESTORE backup files having the Lack-of-Integrity bit set. Bugs were fixed in DISKANALYZER, SAVERESTORE and many of the system dumps. 8.2A Obsolete This release contained significant enhancements providing NO EXTEND BASIC, 68 serial devices, math functions, X.25 Communications, DataWord 3.0. File System write through and BULLETIN board availability. 8.2B Obsolete This release contained all of the above features but was required for the 8000 Series systems due to a change in the WCS image for that hardware. 8.2C Obsolete This release contained a WCS fix to support rezero fault clear, disk error recovery and a fix to the IMLC. 8.4A Acceptable This release contained significant enhancements including 6 megabytes of main system memory, 96 devices, 84 total serial devices, disk to disk sequential family backup, enhanced hardware error log, system load progress monitor, and fast reconstruct utility. 8.4B Obsolete Enhanced features include: 8 megabytes of main system memory, 16-port Asynchronous Controller, point-to-point file specification, QUIET mode for utilities, BASIC statement numbers up to 16000, Buffered Magnetic Tape Controller (BMTC) 1/4" tape support, S/10 Industry Standard Printer as slave printer. 3.O NEW AND ENHANCED BOSS/VS FEATURES 3.01 CONFIGURATIONS SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB008 Pg002 3.01.1 8000 Series The maximum configuration for the MAI 8000 Series is as follows: 96 Devices - A combination of 8-ways, 16-ways, the 4 ports on the MCS PCBA, MDTs and HVDTs up to a total of 96 devices are supported. The following is a list of the maximum ISDCs that are supported. 10 ISDCs (8-way) 6 ISDCs (16-way) 32 Ghost tasks 64 Concurrent tasks recommended (high activity) 24 High speed videos (HVDT) 8 Disk drives 4 Parallel printers 8 Megabytes of memory 2 Magnetic tape drives (MTR, MTS and/or MCS) 2 Intelligent Multi-Line Controllers (IMLC) 8 Dataword II\ terminals 4 TBC lines 64 3270 terminals 8 X.25 lines 2 Auto-Call Units (ACU) 1 1/4 inch MCS for intersystem transport 24 System printers (spooler) NOTE There is a maximum of 9 memory assembly boards in any combination of 1/2 Mb, 1 Mb, 2 Mb, 4 Mb and BMTCs (a maximum of 3 boards per chassis). The above limits apply to the Basic Four\ 8030 Series system only. The Basic Four\ 8010 and 8020 have the configuration limits described below: 8010 8020 1-4 Mb memory 1-6 Mb memory 20 devices 52 devices 12 concurrent tasks 30 concurrent tasks recommended (high recommended (high activity) activity) 19 system printers 24 system printers 3.01.2 System 810 The maximum configuration for the 810 System is as follows: 64 Devices - 7 ISDCs and up to 24 high speed videos (the total not to exceed 64 devices including serial printers) 24 System printers (parallel and non-slave serial) 24 High speed videos (HVDT) 8 Disk drives 4 Parallel printers 6 Megabytes of memory (maximum of 8 boards in any combination; 1/2 Mb, 1 Mb) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB008 Pg003 2 Magnetic tape drives (MTR and/or MTS) 2 Intelligent Multi-Line Controllers (IMLC) 8 Dataword II terminals 4 TBC lines 64 3270 terminals 8 X.25 lines 2 Auto-Call Units (ACU) 32 Ghost tasks 3.02 LANGUAGES 3.02.1 BOSS/VS COBOL BOSS/VS COBOL is a complete package that enables the user to compile and execute COBOL source programs. It conforms in a majority of areas to the 1974 ANSI standard (ANSI X3.23-1974) with the Federal Information Processing Standard (FIPS PUB 21-1) validation. BOSS/VS COBOL also includes an enhanced run-time debugging utility and a Report Writer module. NOTE This is a software controlled feature and must be configured on an 8.4 configuration record. The following is a list of the files and modules used by BOSS/VS COBOL with a brief description of each: .R4C50.SYS.COBOL Interface to the COBOL compiler .R4C50.SYS.COBOL.CPL Compile interpreter of the MOM code. .R4C50.SYS.COBOL.CTBL Message file for the compiler .R4C50.SYS.COBOL.HELPER Manager of workspace for COBOL .R4C50.SYS.COBOL.MOM Macro Operational Module (low level language of the compiler) .R4C50.SYS.COBOL.RD Run-time of object code with BOSS/VS Symbolic Debugging .R4C50.SYS.COBOL.RT Run-time of object code .R4C50.SYS.COBOL.XTBL Message file for Run-time and Run-time Debugging 3.02.1.1 Using the COBOL System There are three basic steps performed with BOSS/VS COBOL programs. They are: 1. Transport/Create the COBOL Source 2. Compile 3. Execute the COBOL Program file (Run-Time) 3.02.1.2 Transport/Create the COBOL Source A COBOL program can be created or modified on the BOSS/VS system using EDIT. With EDIT a serial file is created, then compiled creating the object code. Each source line must be no more than 80 characters in length, conforming to the standard COBOL input format. With EDIT each line conforms to a standard COBOL source line, beginning at column 8 as the A section and not SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB008 Pg004 exceeding column 73. If data exceeds column 72 on a source line an error will not always be generated, but the data is lost. NOTE Columns 1-6 are used for source statement numbers. A '*' in column 7 indicates the statement is a comment; "/" in column 7 indicates a comment that begins a new page in the source listing. Column 73-80 are, by 80-column card convention, reserved for file identification. When a COBOL program is modified with the EDIT Utility it must then be recompiled to generate the new object code. Tape transport of COBOL programs can be handled with a BASIC program. BOSS/VS COBOL supports ANSI standard tape labels, including multi-file reels and multi-reel files. The source tape preference is high bit ASCII with 80 byte records. 3.02.1.3 Compile The Basic Four COBOL Compiler interpreter is written in Pascal and is an interpretive compiler that interprets Macro Operation Module (MOM) code, which is an assembly like language. The BOSS/VS COBOL has a complete implementation. The compiler compiles about 200 lines per minute and consists of six phases that are executed in two passes. Pass one does a scan of the four divisions; IDENTIFICATION, ENVIRONMENT, DATA and PROCEDURE. After this pass all encoded information is output to disk work files, and forward data references are resolved. Pass two consists of forward procedure references resolution, data code and procedure code generation. PASS 1 - phase 1 - Scans the source code - namely, the IDENTIFICATION, ENVIRONMENT, and DATA divisions and tokenizes the codes. phase 2 - Scans the screen section and report generator. phase 3 - Scans the PROCEDURE division. PASS 2 - phase 4 - Code generation for three divisions, IDENTIFICATION, ENVIRONMENT and DATA. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB008 Pg005 phase 5 - Code generation of the PROCEDURE division. phase 6 - Generates the listing for diagnostics, errors and cross-reference. The COBOL compiler is accessed by entering: !COBOL The screen then displays the 15 compiler options. The following is a short description of the function of each: 1. LS - Source listing output requested. 2. LO - Object listing output requested. 3. DM - Data map listing requested. 4. PM - Procedure map listing requested. 5. XR - Cross reference procedure and data names requested. 6. SY - Syntax check only compilation. 7. SN - Sequence field check requested. 8. SB - Subprogram compilation. This option is no longer needed and will be removed in subsequent versions of the compiler. 9. SG - Object program must be segmented. If this is not specified, the program is generated without segmentation. (i.e., the segment numbers on section headings are ignored) 10. DB - ANSI Debugging requested. If this is not specified, all ANSI debugging operations are ignored. 11. ID - Symbolic debug file output is requested. BOSS/VS COBOL debugger is automatically invoked when a program compiled with this option is executed. 12. F1 - Low Level. 13. F2 - Low-Intermediate Level. 14. F3 - High-Intermediate Level. 15. F4 - High Level (flags BOSS/VS COBOL extensions). Options 12-15, are for use with the different FIPS level variations of COBOL implementation and can be used to perform a check of compatibility for COBOL programs being transferred to or from other equipment. 3.02.1.4 Execution (Run-Time) When a program is compiled, the object program is created. The object shows the file type of "COB" for COBOL when displaying the file through the DIRectory list utility (with attributes). To execute a COBOL object program the compiled SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB008 Pg006 program name is entered in Command Mode. EXAMPLE: !objectfilename If the ANSI debugging code is to be activated 'DBG' is passed as a parameter to the program name. EXAMPLE: !objectfilename DBG NOTE COBOL accepts the same file name for the source program, object file and output device without giving a warning that the file exists. It overwrites the source or other files on disk that have the same name. 3.02.1.5 Debugging/Diagnostics BOSS/VS COBOL has an enhanced, interactive debugging capability. When the option "ID" is requested through the compiler and the COBOL program is executed, an interactive debug file (object.IDF) is created. This file allows the user to debug during execution. The object.IDF file contains procedure and variable tables that allow the user to examine procedures and data values when debugging. This file is used only when debugging and can be deleted when the process is no longer needed. In order for the BOSS/VS COBOL interactive debugging to be used, option 11 of the compiler menu must be selected. The table below summarizes the commands available through the debugger option: SB Set break point DB Display break point CB Clear break point AD Alter contents of data item AI Alter contents of index item AW Alter contents of individual words in the data division * DDP Display data item * DIP Display index item * DWP Display word(s) * ACP Display contents of arithmetic accumulator * DMP Show data map * PMP Show procedure map * TWP Trace a word on value change * TRP Trace library names executed. QU Terminate (QUit) program execution SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB008 Pg007 NOTE * P is optional and, if entered sends the debug information to a printer. 3.02.1.6 Input/Output Status Key If there is a FILE STATUS data-name associated with a file, the status of any Input/Output statement causes the data-name to be updated as follows: Key Value Description 00 Successful completion 02 Successful, duplicate key 10 End of file 21 Key sequence error 22 Invalid duplicate key 23 No record found 24 Invalid key - boundary violation 30 Permanent error 34 Boundary violation 90 Invalid operation. A READ, WRITE, REWRITE, START or DELETE was attempted which conflicts with the current OPEN mode or access. 91 File not opened. A READ, WRITE, REWRITE, START, DELETE, LOCK UNLOCK, or CLOSE was attempted on a file that is not open. 92 File not closed. An OPEN was attempted on a file that is open. 93 File not available. An OPEN was attempted on a file previously CLOSED WITH LOCK. 94 Invalid open. An OPEN was attempted with either invalid parameters for a VALUE OF clause or an OPEN INPUT, I-O or EXTEND was attempted to a non-existent file or device. 95 Invalid device. An OPEN was attempted to a device which does not support the open mode (e.g., OPEN INPUT of a line-printer). 96 Undefined current record. A sequential access READ was attempted after an unsuccessful random access READ or START. 97 Invalid record length. An OPEN was attempted on a RELATIVE or INDEXED organization file, and the lengths of the record as defined within the program's FD do not match those of the file. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB008 Pg008 Key Value Description 99 Record or file locked. An OPEN, READ, REWRITE, DELETE, LOCK or UNLOCk was attempted on either a record or file which has been locked by another task on the system. 9A Memory exceeded. An I/O operation was attempted but failed because of insufficient memory (e.g., work-space overflow, no more segment table entries, etc.). 9B Other I/O error. (e.g., insufficient privilege). If this or any error occurs and more precise information is needed, run the COBOL program with the "ERR" option to display the BOSS/VS error for ALL I/O errors. Example: !ABC ERR (where ABC is the name of a COBOL program). 3.02.1.7 COBOL Interaction With Business BASIC BASIC and COBOL programs can share access to data files with the following restraints: BASIC 1. Use fixed length fields. Generally this requires the use of READ RECORDs/WRITE RECORDs as opposed to simple READs/WRITEs. 2. Numeric items must appear with leading zeros and no decimal point. 3. Signed numeric items should have a leading sign character. 4. A Direct file (COBOL Indexed) must hold the key within the record at the same fixed location within each record. COBOL 1. Embedded or trailing signs should be avoided. If a sign must be used, make it a LEADING SEPARATE sign. 2. Comp-3 should be avoided as BASIC finds it difficult to handle. 3. BASIC considers the following hexadecimal bytes as field terminator codes, $00$, $8A$, $8D$, $96$, $97$, $98$, $99$, $9C$, $9D$, $9E$ and $9F$. These should be avoided within records that BASIC reads without the RECORD modifier. NOTE SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB008 Pg009 COBOL cannot CALL subprograms in any other language but COBOL. BASIC and CLI (Command Language Interface) can start COBOL programs but there is no support given to passing parameters to or from the programs. 3.02.1.8 File Structure Since the COBOL system's files and I/O records are constructed to meet the requirements of ANSI Standard COBOL, not all files generated by Business BASIC can be correctly interpreted by the COBOL system. COBOL always performs fixed length I/O. The length is taken from the longest record associated with the file that is described in the FD definition of the Data Division. All reads, writes and rewrites use that length. Physical records longer than this are truncated on the right causing loss of information. COBOL programs use three file types: 1. Sequential-access (BOSS/VS Serial). COBOL automatically locks this file when it is OPENed for either I-O, output or extend. 2. Relative (BOSS/VS Indexed). The first byte of each record in this file is used to indicate if the record is available (unused or a deleted record). This is indicated with a hexadecimal $FF$. The CIRRF utility is available to create these files. Use this utility as follows (no screen): !CIRRF file.name, # RECORDS, RECORD SIZE CIRRF places a hexidecimal $FF$ in the first byte of each record. If CIRRF is not used to create the file and there are characters other than $FF$ in the first byte of a record, COBOL looks at it as data (which could result in garbage or file full). NOTE The BOSS/VS Release 8.5A File System will support deleted records in a manner which is transparent to application programs. 3. Indexed (BOSS/VS Direct) COBOL has the same maximum key size (56 bytes) but requires the primary key to appear within the data record at the same fixed position in each record. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB008 Pg010 BOSS/VS COBOL can use only the primary key, the Alternate key is not recognized. 3.02.1.9 Deviations from the ANSI Standard 1. The RERUN clause is not supported. It is treated as a comment. 2. In Sequential files (BOSS/VS Serial) the REVERSED verb is not supported. 3. With an INDEXED file (BOSS/VS Direct) the I/Os can use only the primary key. ALTERNATE KEY is not supported. 4. BOSS/VS Spooler support. Three clauses can be added to a file description (FD section) in the following format: VALUE OF SPOOL-CLASS IS SPOOL-COPIES IS SPOOL-PRIORITY IS Both alphanumeric and integer values can be either a variable or literal of the appropriate type and the same or fewer characters as specified in the implied picture. Any combination of these clauses can be entered for any FD in any order, but a clause can not be repeated. 5. The WAIT verb allows a delay to processing for a specified amount of time. EXAMPLE: WAIT Where "numeric" can be either a variable or a literal and indicates the 100ths of a second to wait. 6. File/record level locking is provided in the following format: LOCK UNLOCK RECORD READ [NEXT] RECORD [WITH LOCK] [INTO ] LOCK causes the file to become inaccessible to other files. The status of is updated to indicate either '00' for a successful lock or a 90-series error if the lock failed. UNLOCK cancels either a file or a record level lock. An error 91 is returned if the file is not opened, otherwise an error status of '00' is returned. READ WITH LOCK locks only the 'read' record and remains in effect until the next I/O operation or UNLOCK on this particular file. Normal error handling takes place SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB008 Pg011 with this operation. 7. Communications module entries are not supported. 8. With the COMPUTE verb, exponentiation to a non-integral power is not allowed. 3.03 UTILITIES 3.03.1 DEDICATE UTILITY The DEDICATE utility has enhanced error status messages for its new capabilities (i.e., PENDING DISCONNECT). The following is a list of the additional errors returned from the DEDICATE utility: Description BASIC Error Printer is not present 12 Pending disconnection 13 Pending dedication 13 Dedicated-Disconnect pending 13 Printer is not dedicated or disconnected 14 Printer is dedicated from another process 14 Request rejected-pending state 14 Already disconnected and in use 14 Invalid printer name 17 The following DEDICATEs a printer with a quiet display: >! QUIETON;DEDICATE D,LP;QUIETOFF (in BASIC) 3.03.2 GLOBAL SEARCH AND REPLACE (GSR) The GSR utility now operates on Index and Direct files in addition to the previous support of Serial files and BASIC programs. This provides a method of editing Index files and the data portion (not the keys) of Direct files. NOTE When specifying a node in GSR, all file types (including Direct and Index) are included in the Search and/or Replace. 3.03.3 FILESIZE This utility is used to find how much space will be taken by files in BOSS/VS release 8.5A. This utility is to be used when upgrading from 8.4C to 8.5A to estimate disk space requirements. When FILESIZE is used, the following menu appears: NODE OR FILE NAME: FILE TYPE : RECORDS DECLARED : ACTUAL RECORDS : SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB008 Pg012 KEY SIZE : OUTPUT DEVICE : ENTRIES CORRECT (Y/N): At the NODE OR FILE NAME prompt, enter a node or filename to calculate space on. To calculate space for a file that doesn't exist, press RETURN. If a node or filename is entered, then the cursor will go to the OUTPUT DEVICE prompt. Enter the output device desired. If a RETURN was pressed in response to the NODE OR FILE NAME prompt, the program will prompt for file type. Next the total number of declared records will be entered. At the ACTUAL RECORDS prompt, the number of declared records that are actually being used is entered. To calculate the largest space allocated by the file under the new file system, make actual records equal to the number of declared records. The record size will then be prompted for. If a Direct or Sort file was chosen, the enter the key size at the KEY SIZE prompt. The utility will then prompt for correct entries. The utility will then display the filename, attributes, and space taken by the file(s) on the new file system. The last two columns represent how much space is taken by the file. The column labeled USED SECS represents how much disk space is taken by the file with the current data content. The column MAX SECS represents how much disk space will be taken by the file when filled to its maximum capacity. After all files have been displayed,the utility will show the total number of required sectors for the file(s) under the new file system. Also, the total number of required sectors when all files are filled to capacity will be displayed. 3.03.4 FIND LOST SPACE (FINDLOSTSPACE) This utility will display all files in the given family that have the LOST SPACE flag set. Also files which have the BAD INTEGRITY flag set are reported. The report is automatically sent to LP. 3.04 HARDWARE 3.04.1 Buffered Magnetic Tape Controller (BMTC) Use of a BMTC requires that the ACS PCBA be updated to revision level T. A combination of an MCS and MTS or a combination of an MCS and an MTR can be used. A combination of an MTR and an MTS cannot be connected to the same BMTC. A combination of two MTS's is possible and are daisy chained together. However, when more than one tape drive is present on the BMTC, there are some restrictions on simultaneous access due to the fact that there are effectively two buffers on the BMTC which are managed by the software. SAVERESTORE uses both buffers, so no other tasks may access BMTC SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB008 Pg013 drives while SAVERESTORE is in control of one or two drives connected to it (two drives might be used in a reel switch operation). Application programs access to a BMTC drive uses just one buffer, so two drives on a BMTC may be accessed simultaneously by one or more application programs. The BMTC provides full tape support including ODD BYTE READS and WRITES (through BASIC), and 800 bpi (through BASIC and COBOL). The MTR can be used for 800 bpi reads and writes from BASIC only. The MTS is limited to 1600 bpi density, due to hardware restrictions. SAVERESTORE reads and writes only 1600 bpi density tapes on all drives. NOTE On 8.4C, a Type 2 SAVERESTORE backup is slower when the MTS is connected to the BMTC than when connected to the TDP. This is due to 8.4C not using the full buffering capability of the BMTC. This is fixed in 8.5A 3.04.2 Printer Support The following printers can be used as slave devices with an S/10 on level 8.4C: o Okidata 82A standard interface (Model 4208) o Diablo 630 ISP standard interface (Model 4211) o Whisper standard interface (Model 4213) 3.05 OPERATING SYSTEM 3.05.1 Intelligent Serial Device Controller (ISDC) The 8.4C release features an enhanced ISDC OS for the 4-way, 8-way and 16-way. The ISDC was enhanced to prevent serial printers from losing print lines when used through a statistical multiplexor. 4.0 INSTALLATION PROCEDURES If upgrading from a release prior to 8.4B, please refer to the 8.4B BOSS/VS Release Software Announcement 011185/110 section 4.0 for instructions. The only change will be to substitute the 8.4C file names for the 8.4B versions. 8.4C Release Files .R4C50.BURN. Burn in programs. .R4C50.INST. System installation files. .R4C50.INTL. International translation files. .R4C50.SYS. Operating system files. .DWPGM. DataWord II (3.1) program files. .DW.V23. DataWord II(2.3) program files. .CONX. DataWord II(3.1) for first time installation. .DWII. DataWord II conversion programs (2.3 to 3.1) .PGMPASC. Pascal communication files (all packages). .PGM3270. 3270 communication program files. .COM3270. 3270 communication data files. .PGMTBC. TBC communication program files. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB008 Pg014 .COMTBC. TBC communication data files. .NSDATA. X.25 data files. .NSPGM. X.25 program files. .PGMEZ2. Easy II program files. 4.01 UPGRADE PROCEDURES FOR 8.4B to 8.4C Please read the following section carefully before beginning installation. NOTE BEFORE UPDATING TO ANY NEW BOSS/VS LEVEL, CREATE A FULL BACKUP AND COMPARE ALL FILES. 8.4C SAVERESTORE TAPES CANNOT BE READ BY A BOSS/VS RELEASE PRIOR TO 8.4B. PROGRAMS COMPILED UNDER 8.4C DO NOT RUN UNDER A BOSS/VS RELEASE PRIOR TO 8.4B. I. BACKUP Be sure to backup the following files in addition to application files: .SYSDATA. .SYSTEM.CONFIG. Make an archive copy of program files in the event that they need to be run on a release prior to 8.4B. The OLDTAPE utility can be used to back up programs on 8.4C and restore them on 8.4A. OLDTAPE recompiles the programs on 8.4A during the restore. II. INSTALL THE 8.4C RELEASE TAPE A. ALT LOAD 1. Mount the new release tape into the tape drive. 2. Press the "ALT LOAD" button on the front panel. a. Enter the appropriate system disk (0 or 1) or if drives 0 and 1 are system disks, enter "2" to update both disks. b. Enter a "0" to update WCS slot 0. c. Enter "Y" to the prompt "Are you SURE you want to overwrite this WCS? (Y/)" The system automatically updates OS and WCS slot 0 on both disks, if selected. When this is done the system prompts "DONE - READY FOR NORMAL DISK LOAD". RELOAD by pressing the LOAD button. B. ENTER A TYPE 3 LOAD - SPECIAL FUNCTIONS 1. Select #2 - CHANGE INSTALLATION PARAMETERS SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB008 Pg015 SYSTEM DISKS: (displayed) DRIVE NUMBER: You have the ability to update a second disk without the requirement of loading from that drive prior to the update. PRIMARY PREFIX? Enter (family).R4C50.SYS. Where (family) is the family where the operating system files reside. SECONDARY PREFIX? Enter (family).R4C50.SYS. Where (family) is the family where the alternate operating system files reside. DEFAULT USER FAMILY NAME?: (Example: DISK) SECURITY (E=ENABLED, D=DISABLED): FILE SYSTEM WRITE THROUGH? (E=ENABLED, D=DISABLED): Having this feature enabled causes immediate writes to the disk during all write operations. UPDATE DISK WITH INSTALLATION PARAMETERS? (Y/N) Display: PARAMETERS SUCCESSFULLY WRITTEN TO DISK. 2. Enter a CTL-IV to return to the SPECIAL FUNCTIONS menu. Reload the system by pressing the LOAD button. C. TYPE 2 LOAD - Select #1 SAVERESTORE UTILITY 1. Select "RESTORE FILES FROM TAPE" - the following screen appears: RESTORE FILES TAPE SET.ID: DRIVE-NUM: 00 REEL-NUM:01 PRIMARY PREFIX: (FAMILY).NODE. FILE TYPE (D/P/CR=ALL) COMPARE (CR=Y/N) DATE (MM/DD/YY) TIME (HH:MM) OUTPUT DEVICE (CR=VDT) DELETE EXISTING FILES (CR=Y) VERIFY (Y/CR=N) ENTRIES CORRECT (Y/N) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB008 Pg016 At each prompt, enter a . At the prompt, "FILE SPECIFIERS" enter ".". Enter to all other questions. All system files will be restored to disk. Please note that once all files are restored to disk, the message "AUTOMATIC COMPARE, CR TO CONTINUE" appears. This automatically rewinds the tape and begins the compare. This occurs only when the automatic compare option is selected. 2. When the compare is completed, enter a CTL-IV to return to the "SAVERESTORE UTILITY" menu. Reload the system by pressing the LOAD button. D. TYPE 1 LOAD - NORMAL EXECUTION The names of modules are displayed as they are initialized. Enter the DATE and TIME. 1. Go to command mode where the system prompt is the exclamation mark (!) and enter: a. PREFIX .R4C50.INST. This sets the prefix to .R4C50.INST. in order to update the remaining OS and WCS slots. Slot 0 was updated in the ALT LOAD procedure. b. OSINFO This displays the updated OS and WCS slot 0 with the 8.4C release level, the 8.4B level in slot 1, 8.4B REMIDI in slot 2 and 8.4B DEMON in slot 3. c. UPDATE.OS NAME OF IMAGE FILE: .R4C50.INST.OS1.UV040350001 IMAGE FILE NAME: .R4C50.INST.OS1.UV040350001 OS SLOT: (displayed) OS VERSION: (displayed) IMAGE FORMAT: (displayed) NEW WCS SLOT: 1 UPDATE WHICH DISK: (0=nn/1=nn/B=BOTH/Q=QUIT) Display: DONE! UPDATE COMPLETE d. UPDATE.WCS ENTER WCS SLOT [0...3]: 1 AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : 0 WCS IMAGE FILE: .R4C50.INST.WCS.xxxxxx Ex: System 810 hardware = .R4C50.INST.WCS.A426 8000 Series hardware= .R4C50.INST.WCS.B426 Display: WCS LEVEL OF WCS IMAGE FILE: (version above) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB008 Pg017 UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETED! ** Repeat this step to update WCS slot 1 on drive 1 if drive 1 is a system disk. e. UPDATE.WCS ENTER WCS SLOT [0...3] 2 AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : 0 WCS IMAGE FILE: .R4C50.INST.REMIDI.xxxxxx Ex: System 810 hardware = .R4C50.INST.REMIDI.AV422 8000 Series hardware= .R4C50.INST.REMIDI.BV427 Display: WCS LEVEL OF WCS IMAGE FILE: (Version above) UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETED! ** Repeat this step to update WCS slot 2 on drive 1 if drive 1 is a system disk. f. UPDATE.OS NAME OF IMAGE FILE: .R4C50.INST.OS3.UV040234011 OS SLOT: (displayed) OS VERSION: (displayed) IMAGE FORMAT: (displayed) NEW WCS SLOT: 3 UPDATE WHICH DISK (0=nn/1=nn/B=BOTH/Q=QUIT) Display: UPDATING DISK DONE! UPDATE IS NOW COMPLETE g. UPDATE.WCS ENTER WCS SLOT [0...3]: 3 DISK TO UPDATE: 0 WCS IMAGE FILE: .R4C50.INST.WCS.xxxxxx Ex: System 810 hardware = .R4C50.INST.WCS.A426 8000 Series hardware= .R4C50.INST.WCS.B426 Display: WCS LEVEL OF WCS IMAGE FILE: (Version above) UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETED! ** Repeat this step to update WCS slot 3 on drive 1 if drive 1 is a system disk. h. OSINFO This displays all Load Directories updated with the 8.4C release. 5.0 RELATED DOCUMENTATION 2770/2780/3770/3780 Batch Emulator User's Guide BFISD 5080B SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB008 Pg018 3270 Pass-Through Reference Manual BFISD 5091A BOSS/VS Business BASIC Reference Manual BFISD 5092B MAI 8000 User's Guide BFISD 5098C BOSS/VS Utilities User's Guide BFISD 5102B Level 3/4 to MAI 8000 Series Conversion Guide BFISD 5105B MAI 8000 Series Operator's Guide BFISD 5115A 3270 Emulation Package Operator's Guide for MAI 8000 Series BFISD 5129 MAI 8000 Terminal Asynchronous Communication Facility Reference Manual BFISD 5130A Network Communications Interface Reference Manual BFISD 5131P BOSS/VS Installation Guide BFISD 5138A MAI 8000 Series Installation Planning Guide BFISD 5146C BOSS/VS Special Purpose Utilities User Guide BFISD 5151 BOSS/VS System Support Manual BFISD 5152 BOSS/VS System Management Utilities User Guide BFISD 5154A Intersystem Transfer (13XX/8000/2000) BFISD 6354 MAI 8000 Series COBOL Reference Manual BFISD 5174 MAI 8000 Series COBOL User Guide BFISD 5175 BOSS/VS Business BASIC Reference Manual Section 8 (Mnemonics) Change Notice BFISD 5092B ORIGINATOR: MBF SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB008 Pg019 FIB 00009 06/17/85 *** Incorrect Status/Sector displayed on disk to disk backup - Rel 8.4B *** Problem: When a disk I/O error is encountered on level 8.4B in the TYPE III load COPY FAMILY FROM DISK TO DISK, the error status bits are displayed on the screen. However, a bug in this level causes the display to always show the same error. Example: DISK ERROR STATUS = 000003F8 (DEV) DRIVE HARDWARE ERROR, STARTING SCTOR = NNNN TO CONTINUE Where (DEV) is either SOURCE or DESTINATION and NNNN is the sector number. Solution: This incorrect status, 000003F8, is corrected in the 8.4C release. Note that the sector number shown is a sector within a 64K block. The exact sector number can be found by doing a DISKREAD of the pack, which will show up as a single sector error in the ERRORLOG. ORIGINATOR: J. RIPPL SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB009 Pg001 FIB 00010 06/18/85 *** Release 8.4D Software Announcement *** 1.0 INTRODUCTION MAI Basic Four, Inc. is pleased to announce that a new software release, 8.4D, is now available. This is the recommended software release for all System 810~ and MAI\ 8000 Series systems. The following summarizes the features contained in the Level 8.4D release: o BOSS/VS BASIC execution change for CALLed program transfer of PRECISION level. o BOSS/VS COBOL execution change of the ACCEPT FROM TERMINAL-ID clause. o EXTTAPE can now accept 13XX files with greater than 64,000 records. o Numerous enhancements to the FILESIZE utility. A new configuration record is not required unless this release coincides with the purchase of new hardware or chargeable software. Installation and upgrade procedures are fully documented in this announcement. Please read the upgrade section (4.01) prior to installing any new operating system. NOTE BOSS/VS Level 8.4D is the last BOSS/VS release to support 810 System hardware. Also, BOSS/VS Level 8.4D will the last release of EASY II. 8.4D BOSS/VS Software Announcement Table of Contents 1.0 Introduction 2.0 History 3.0 Enhanced BOSS/VS Features 3.01 BOSS/VS BASIC Execution Change 3.02 BOSS/VS COBOL Execution Change 3.03 EXTTAPE Utility Enhancement 3.04 FILESIZE Utility Repairs 4.0 Installation Procedures 4.01 Upgrade Procedures for 8.4C to 8.4D 5.0 Related Documentation 2.0 HISTORY Release Current Status Description 8.1A Obsolete Introduction of the System 810 hardware and BOSS/VS software. 8.1B Obsolete Enhanced features include: 31 logical units in BASIC, increase in file system cache from 208 to 225 unique files, MULTIREELSR, family image SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB010 Pg001 backups, SAVERESTORE backup files having the Lack-of-Integrity bit set. Bugs were fixed in DISKANALYZER, SAVERESTORE and many of the system dumps. 8.2A Obsolete This release contained significant enhancements providing NO EXTEND BASIC, 68 serial devices, math functions, X.25 Communications, DataWord 3.0. File System write through and BULLETIN board availability. 8.2B Obsolete This release contained all of the above features but was required for the 8000 Series systems due to a change in the WCS image for that hardware. 8.2C Obsolete This release contained a WCS fix to support rezero fault clear, disk error recovery and a fix to the IMLC. 8.4A Acceptable This release contained significant enhancements including 6 megabytes of main system memory, 96 devices, 84 total serial devices, disk to disk sequential family backup, enhanced hardware error log, system load progress monitor, and fast reconstruct utility. 8.4B Obsolete Enhanced features include: 8 megabytes of main system memory, 16-port Asynchronous Controller, point-to-point file specification, QUIET mode for utilities, BASIC statement numbers up to 16000, Buffered Magnetic Tape Controller (BMTC) 1/4" tape support, S/10 Industry Standard Printer as slave printer, new ISDC OS for 4-way. 8-way and 16-way. 8.4C Obsolete Enhanced features include: Buffered Magnetic Tape Controller, 1/2" tape support (BMTC), DEDICATE with expanded error reporting, and the release of the new FILESIZE utility. 3.0 ENHANCED BOSS/VS FEATURES 3.01 BOSS/VS BASIC EXECUTION CHANGE The 8.4D BOSS/VS BASIC run-time execution module, BASIC.RT, has been changed with this release to be more compatible with the execution characteristics of BASIC Levels 3, 4, 7 and pre-level 8.4B BOSS/VS releases. In other Business BASIC levels the PRECISION level is passed from the CALLing program to the CALLed program automatically. BOSS/VS releases 8.4B and 8.4C altered this practice so that the CALLed program will come up in the default PRECISION level of PRECISION 2, regardless of the CALLing programs set PRECISION. The 8.4D BOSS/VS BASIC release reinstates the previous practice of passing the PRECISION level onto a CALLed program. 3.02 BOSS/VS COBOL EXECUTION CHANGE This release of BOSS/VS COBOL changes the ACCEPT FROM TERMINAL-ID clause to act like the Business BASIC FID(0) function, returning the task I.D. to the task executing COBOL. Previous releases of BOSS/VS COBOL used the ACCEPT FROM TERMINAL-ID clause to re-direct terminal I/O to alternate terminals. This feature, SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB010 Pg002 however, was not clearly understood and if not programmed correctly could result in system dumps. It is now changed to return the task I.D. instead of re-directing output. 3.03 EXTTAPE UTILITY ENHANCEMENT The previous EXTTAPE utility releases were not able to accept a file with greater than 64,000 records. This new release corrects that deficiency. 3.04 FILESIZE UTILITY REPAIRS Numerous screen handling, masking, and error reporting enhancements have been incorporated into the new FILESIZE utility contained on this release. 4.0 INSTALLATION PROCEDURES If upgrading from a release prior to 8.4B, please refer to the 8.4B BOSS/VS Release Software Announcement 011185/110 section 4.0 for instructions. The only change will be to substitute the 8.4D file names for the 8.4B versions. 8.4D Release Files .R4D51.BURN. Burn in programs. .R4D51.INST. System installation files. .R4D51.INTL. International translation files. .R4D51.SYS. Operating system files. .DWPGM. DataWord II (3.1) program files. .DW.V23. DataWord II(2.3) program files. .CONX. DataWord II(3.1) for first time installation. .DWII. DataWord II conversion programs (2.3 to 3.1) .PGMPASC. Pascal communication files (all packages). .PGM3270. 3270 communication program files. .COM3270. 3270 communication data files. .PGMTBC. TBC communication program files. .COMTBC. TBC communication data files. .NSDATA. X.25 data files. .NSPGM. X.25 program files. .PGMEZ2. Easy II program files. 4.01 UPGRADE PROCEDURES FOR 8.4C to 8.4D Please read the following section carefully before beginning installation. NOTE BEFORE UPDATING TO ANY NEW BOSS/VS LEVEL, CREATE A FULL BACKUP AND COMPARE ALL FILES. 8.4D SAVERESTORE TAPES CANNOT BE READ BY A BOSS/VS RELEASE PRIOR TO 8.4B. PROGRAMS COMPILED UNDER 8.4D DO NOT RUN UNDER A BOSS/VS RELEASE PRIOR TO 8.4B. I. BACKUP Be sure to backup the following files in addition to application files: .SYSDATA. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB010 Pg003 .SYSTEM.CONFIG. Make an archive copy of program files in the event that they need to be run on a release prior to 8.4B. The OLDTAPE utility can be used to back up programs on 8.4D and restore them on 8.4A. The TAPE utility recompiles the programs on 8.4A during the restore. II. INSTALL THE 8.4D RELEASE TAPE A. ALT LOAD 1. Mount the new release tape into the tape drive. 2. Press the "ALT LOAD" button on the front panel. a. Enter the appropriate system disk (0 or 1) or if drives 0 and 1 are system disks, enter "2" to update both disks. b. Enter a "0" to update WCS slot 0. c. Enter "Y" to the prompt "Are you SURE you want to overwrite this WCS? (Y/)" The system automatically updates OS and WCS slot 0 on both disks, if selected. When this is done the system prompts "DONE - READY FOR NORMAL DISK LOAD". RELOAD by pressing the LOAD button. B. ENTER A TYPE 3 LOAD - SPECIAL FUNCTIONS 1. Select #2 - CHANGE INSTALLATION PARAMETERS SYSTEM DISKS: (displayed) DRIVE NUMBER: You have the ability to update a second disk without the requirement of loading from that drive prior to the update. PRIMARY PREFIX? Enter (family).R4D51.SYS. Where (family) is the family where the operating system files reside. SECONDARY PREFIX? Enter (family).R4D51.SYS. Where (family) is the family where the alternate operating system files reside. DEFAULT USER FAMILY NAME?: (Example: DISK) SECURITY (E=ENABLED, D=DISABLED): FILE SYSTEM WRITE THROUGH? (E=ENABLED, D=DISABLED): SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB010 Pg004 Having this feature enabled causes immediate writes to the disk during all write operations. UPDATE DISK WITH INSTALLATION PARAMETERS? (Y/N) Display: PARAMETERS SUCCESSFULLY WRITTEN TO DISK. 2. Enter a CTL-IV to return to the SPECIAL FUNCTIONS menu. Reload the system by pressing the LOAD button. C. TYPE 2 LOAD - Select #1 SAVERESTORE UTILITY 1. Select "RESTORE FILES FROM TAPE" - the following screen appears: RESTORE FILES TAPE SET.ID: DRIVE-NUM: 00 REEL-NUM:01 PRIMARY PREFIX: (FAMILY).NODE. FILE TYPE (D/P/CR=ALL) COMPARE (CR=Y/N) DATE (MM/DD/YY) TIME (HH:MM) OUTPUT DEVICE (CR=VDT) DELETE EXISTING FILES (CR=Y) VERIFY (Y/CR=N) ENTRIES CORRECT (Y/N) At each prompt, enter a . At the prompt, "FILE SPECIFIERS" enter ".". Enter to all other questions. All system files will be restored to disk. Please note that once all files are restored to disk, the message "AUTOMATIC COMPARE, CR TO CONTINUE" appears. This automatically rewinds the tape and begins the compare. This occurs only when the automatic compare option is selected. 2. When the compare is completed, enter a CTL-IV to return to the "SAVERESTORE UTILITY" menu. Reload the system by pressing the LOAD button. D. TYPE 1 LOAD - NORMAL EXECUTION The names of modules are displayed as they are initialized. Enter the DATE and TIME. 1. Go to command mode where the system prompt is the exclamation mark (!) and enter: a. PREFIX .R4D51.INST. This sets the prefix to .R4D51.INST. in order to update the remaining OS and WCS slots. Slot 0 was updated in the ALT LOAD procedure. b. OSINFO This displays the updated OS and WCS slot 0 with the 8.4D release level, the 8.4D level in slot 1, 8.4D REMIDI in slot 2 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB010 Pg005 and 8.4D DEMON in slot 3. c. UPDATE.OS NAME OF IMAGE FILE: .R4D51.INST.OS1.UV040451000 IMAGE FILE NAME: .R4D51.INST.OS1.UV040451000 OS SLOT: (displayed) OS VERSION: (displayed) IMAGE FORMAT: (displayed) NEW WCS SLOT: 1 UPDATE WHICH DISK: (0=nn/1=nn/B=BOTH/Q=QUIT) Display: DONE! UPDATE COMPLETE d. UPDATE.WCS ENTER WCS SLOT [0...3]: 1 AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : 0 WCS IMAGE FILE: .R4D51.INST.WCS.xxxxxx Ex: System 810 hardware = .R4D51.INST.WCS.A426 8000 Series hardware= .R4D51.INST.WCS.B426 Display: WCS LEVEL OF WCS IMAGE FILE: (version above) UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETED! ** Repeat this step to update WCS slot 1 on drive 1 if drive 1 is a system disk. e. UPDATE.WCS ENTER WCS SLOT [0...3] 2 AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : 0 WCS IMAGE FILE: .R4D51.INST.REMIDI.xxxxxx Ex: System 810 hardware = .R4D51.INST.REMIDI.AV422 8000 Series hardware= .R4D51.INST.REMIDI.BV427 Display: WCS LEVEL OF WCS IMAGE FILE: (Version above) UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETED! ** Repeat this step to update WCS slot 2 on drive 1 if drive 1 is a system disk. f. UPDATE.OS NAME OF IMAGE FILE: .R4D51.INST.OS3.UV040234011 OS SLOT: (displayed) OS VERSION: (displayed) IMAGE FORMAT: (displayed) NEW WCS SLOT: 3 UPDATE WHICH DISK (0=nn/1=nn/B=BOTH/Q=QUIT) Display: UPDATING DISK DONE! UPDATE IS NOW COMPLETE g. UPDATE.WCS SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB010 Pg006 ENTER WCS SLOT [0...3]: 3 DISK TO UPDATE: 0 WCS IMAGE FILE: .R4D51.INST.WCS.xxxxxx Ex: System 810 hardware = .R4D51.INST.WCS.A426 8000 Series hardware= .R4D51.INST.WCS.B426 Display: WCS LEVEL OF WCS IMAGE FILE: (Version above) UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETED! ** Repeat this step to update WCS slot 3 on drive 1 if drive 1 is a system disk. h. OSINFO This displays all Load Directories updated with the 8.4D release. 5.0 RELATED DOCUMENTATION 2770/2780/3770/3780 Batch Emulator User's Guide BFISD 5080B 3270 Pass-Through Reference Manual BFISD 5091A BOSS/VS Business BASIC Reference Manual BFISD 5092B MAI 8000 User's Guide BFISD 5098C BOSS/VS Utilities User's Guide BFISD 5102B Level 3/4 to MAI 8000 Series Conversion Guide BFISD 5105B MAI 8000 Series Operator's Guide BFISD 5115A 3270 Emulation Package Operator's Guide for MAI 8000 Series BFISD 5129 MAI 8000 Terminal Asynchronous Communication Facility Reference Manual BFISD 5130A Network Communications Interface Reference Manual BFISD 5131P BOSS/VS Installation Guide BFISD 5138A MAI 8000 Series Installation Planning Guide BFISD 5146C BOSS/VS Special Purpose Utilities User Guide BFISD 5151 BOSS/VS System Support Manual BFISD 5152 BOSS/VS System Management Utilities User Guide BFISD 5154A Intersystem Transfer (13XX/8000/2000) BFISD 6354 MAI 8000 Series COBOL Reference Manual BFISD 5174 MAI 8000 Series COBOL User Guide BFISD 5175 BOSS/VS Business BASIC Reference Manual SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB010 Pg007 Section 8 (Mnemonics) Change Notice BFISD 5092B ORIGINATOR: MBF SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB010 Pg008 FIB 00011 10/23/85 *** Release 8.5A initial information *** 1. INTRODUCTION MAI Basic Four, Inc. is pleased to announce that the new software release, 8.5A, is now available. This release is the recommended software release for all 8000 and 7000 series systems. The following is a summary of enhancements contained in the Level 8.5A release: o Increased concurrency on disk file open, close, read and write operations for greater throughput on systems with multiple tasks online. o Support for the MAI 7000 Series systems. o True proportional growth for DIRECT and SORT files. o Maximum number of different files open system-wide increased from 224 to 512. o Maximum number of tasks sharing the same file increased from 64 to 256. o Write-through selectable on an individual file basis. o DISKANALYZER is available in stand-alone mode as well as online mode. o DISKANALYZER can reconstruct directory and available space files. o Maximum number of system printers increased to 99. o System dumps can be dumped directly to tape. o System support for the DMP serial printer. o New terminal services error utility. o DataWord printer queue enhancements. o Enhanced SAVERESTORE utility. It is mandatory that all PCBA revision levels are updated to proper levels (see section 4.2). Any three CE system must have an IMLC at revision level K or higher to insure proper operation of DataWord and communications. A new configuration record is not required unless this release coincides with the purchase of new hardware or chargeable software. Installation and upgrade procedures are fully documented in this announcement. ******************************** * * * PLEASE READ THE INSTALLATION * * INSTRUCTIONS BEFORE ATTEMPT- * * ING INSTALLATION OR UPGRADE. * * THIS RELEASE USES NEW * * PROCEDURES. * * * ******************************** Copyright 1985 by MAI Basic Four Inc. All rights reserved. ORIGINATOR: MBF SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB011 Pg001 FIB 00012 01/03/86 *** BOSS/VS release 8.5B information *** Basic Four has introduced a new level of operating system for 7000 and 8000 series, Level 8.5B. This level must be used by all customers presently on 8.5A level, as 8.5A has a "timebomb" installed into it that will not allow its use after the first of May, 1986. 8.5A was not an official release. Do not relay this information to customers, as this is the responsibility of Basic Four and their dealers. Repeating, all customers using 8.5A level software will not be able to use that operating system as of May 1, 1986. They must make provisions with Basic Four support personnel to be converted to 8.5B by that date! A few of the differences between level 8.5 and any version of 8.4 that may have some affect on hardware are listed below: - 7000 (MPC) support added. - New 8" disks supported, types P-207, P-314 and P-303 - Up to 12 disks allowed with TDP controllers, still 8 with MPC controllers. - Better error retries on hi-speed disks. - T-303 Firmware reduces some I/O errors. - New daisywheel printer supported. - Support for direct connection of serial MVP (no converter box required). - New streamer tape type added. - Some printer drivers speeded up. - 810 system hardware no longer supported. - M-160 and M-315 disk types dropped. ORIGINATOR: C. GAHAN SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB012 Pg001 FIB 00013 04/07/86 *** "Rule of thumb" Memory requirements with 8.4E/8.5 releases *** The redesign of the file system and other BOSS/VS enhancements have increased the required system memory overhead for the operating system. Because an additional 1/4 MB is required the total system memory overhead is now 3/4 MB (or 750 K). The "rule of thumb" for task memory is now: tasks 1 - 20 = 100K per task tasks 21 - 164 = 70K per task * * NOTE: Because memory allocation per task is very application dependent this figure may need to be higher. BOSS/VS being a virtual memory system also means that memory calculations are not hard fast rules. Example: A system with 24 terminals and 2 ghost tasks would be configured as follows: O.S. overhead.....................= 750K First 20 tasks (terminals) @ 100K = 2000K Next 4 tasks (terminals) @ 70K....= 280K 2 ghost tasks @ 70K...............= 140K ______ 3170K or 3.5 MB Always round up to the nearest 1/2 MB. Please use this information when upgrading your customers to the new File System to prevent performance problem complaints. ORIGINATOR: S. BROWN SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB013 Pg001 FIB 00014 04/10/86 *** Message "SPACE MAP IS xx, SHOULD BE xx" on DISKANALYZER *** On 8.5 OS levels when the DISKANALYZER utility is run, in many cases a message appears reporting that the Space Map size is not correct. There is a field that is not being updated but the field is not used by anything, except referenced by DISKANALYZER. This message is harmless and there is no action required. This problem will be corrected in a future release. ORIGINATOR: D. JENSEN SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB014 Pg001 FIB 00015 04/23/86 *** Display differences with INSTALL.CONFIG on 8.5C/9.5C *** New utilities used to generate configuration records cause the following changes in the INSTALL.CONFIG utility display: RELEASE LEVEL 9.5C ONLY: The configuration record now recognizes two MPX mpdel types that run on 9.5: the 9000 and the 9500. MPX 9000 and 9500 Series Systems both have RSTACK Cache available. In addition the MPX 9500 offers DATA and CODE Caches. The model number is used to designate which caches are available. However, the model number ("System Type") of MPX 9500 Series Systems will display as "90xx" instead of "95xx" in the INSTALL.CONFIG utility. The number of CPUs will display accurately.) The 8.6 INSTALL.CONFIG will display the correct model number for the MPX 9500. In order to verify that you have a 9500, run the DEVICES utility. The top line in DEVICES displays the CPU number and the letters "RDC". If all three letters are capitalized, all the caches for the 9500 are enabled. If these letters appear as "Rdc", the DATA and CODE Caches (a 9500 feature) are not enabled. (These caches can also be enabled/disabled by switches on the 9500 CPU or by the boot loader if failures occur at load time.) The letter "R" represents RSTACK Cache. RELEASE LEVELS 8.5C AND 9.5C ONLY: "Main Memory Size" will now be displayed in Megabytes instead of 128K Units. ALL RELEASE LEVELS ON MPX SERIES SYSTEMS: The number displayed in INSTALL.CONFIG for "MAI Async Terminals" now includes the total number of all MAI terminals, MAI non-slave printers, and non-MAI async devices. A "0" will appear for "Non-slave Printers" and "Non-MAI Async Devices". This does not represent any new restriction on the number of allowed devices. It only means that one total number is being displayed forthe whole group. This display will be reworded in the 8.6 INSTALL.CONFIG utility. ORIGINATOR: N. PRENTISS SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB015 Pg001 FIB 00016 06/16/86 *** Potential Keyed file corruption - release 8.5B/C *** On Operating System levels 8.5B/C there is the possibility of the incorrect placement of a pointer in direct and sort files when accessing by "key". The problem can exist when at least two channels are opened to the same file. The problem only occurs when one channel writes a record to the file which upon the write becomes the immediate logical predecessor to the key to which another channel(s) is pointing. In this case the second channel's key pointer is repositioned to point to the newly created record, rather than remaining in place. In the following example, assume that a sort file ("MRFILE") contains three records with keys of "A", "D", and "E". If the following program is run on OS 8.5B or 8.5C the output will be "AADDB", rather than the correct output of "AADDD". 10 OPEN (1)"MRFILE";OPEN (2)"MRFILE" 20 PRINT KEY (1), KEY(2), 30 READ (1); PRINT KEY(1), 40 WRITE (2,KEY="B") 50 PRINT KEY (2), KEY (1), 60 END In the above example one program has two channels open to a file. However, the . channels need not be opened by the same task. A program running on one terminal may affect the current record position of those running on another terminal or . terminals. For this problem to occur requires the uncommon coincidence of one key pointer being established at a key and a write occurring from another channel which upon the write becomes the immediate logical predecessor (among keys that actually exist in the file) to the first key. The first key pointer is then displaced and points to the newly written record. This problem will be corrected in the 8.5D release. ORIGINATOR: L. VERTAL SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB016 Pg001 FIB 00017 07/03/86 *** Write-through default on File Create does not work - Rel 8.5 *** Option 2 in a TYPE 3 LOAD (change installation parameters) contains the prompt, "WRITE THROUGH DEFAULT ON FILE CREATE (E=ENABLED, D=DISABLED):". This is intended to allow the user to specfy what default value should be used for the write through paremeter of the CREATE utility when an explicit value for write through is not specified. The problem is that the default value will remain "DISABLED" even if an "E" for "ENABLED" is entered in responce to the above Installation Parameter prompt. Thus if the user does not specify a write through parameter on a CREATE, (in either the parameter line or through the extendd options on the CREATE menu) write through will always default to "DISABLED". If the user answers "Y" to "Write Through" on the CREATE utility extended options menu, or specifies "WRITE THROUGH = TRUE" on the CREATE utility parameter line, write through will be "ENABLED". The write through option on files may be changed by using the UPDATE utility. This problem does not exist with files created in BASIC, and it will be fixed in release 8.6A. ORIGINATOR: N. PRENTISS SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB017 Pg001 FIB 00018 07/03/86 *** Information for computing the Dump Area size *** Presently on all MPX release levels, the operating system computes the size of the Dump Area using information derived from the currently installed configuration record in conjunction with a survey of the installed hardware at the time of the last system load. This method has two major disadvantages: 1. If a disk has no installed configuration record, the Dump Area Size is computed on a minimum configuration, regardless of what hardware is installed in the system. 2. If additional main memory and shared memory controllers are installed in the system, and this exceeds the limits set by the currently installed configuration record, this new hardware will not be included when computing the size of the dump area. The solution to this problem is for the operating system to actually check the installed hardware when computing the size of the Dump Area, and this will be done in releases 8.6A/9.6A. In the meantime, if either one of the above two situations apply to your system, it will be necessary to compute the size of the Dump Area by determining exactly what main memory and shared memory controllers. are installed in the system, and adding up the area required for each. The total should be input in Option 1 (Change Volume Information) of a TYPE 3 LOAD after the prompt "SIZE OF DUMP AREA (FOR SYSTEM DISK ONLY):". All other numbers on the Option 1 screen that refer to the size of the Dump Area should be ignored. Listed below are the main memory and shared memory controllers and the values to be used when computing the size of the Dump Area: 1. Each megabyte of main memory (903349, 903516)..1024 (x 1024 bytes) 2. Each 4-Way controller (903374)...................64 (x 1024 bytes) 3. Each 8-Way controller (903383)...................64 (x 1024 bytes) 4. Each 16-Way controller (903437).................128 (x 1024 bytes) 5. Each IMLC controller (903381, 903534)............64 (x 1024 bytes) 6. Each LAN controller..............................64 (x 1024 bytes) 7. Each BMTC controller (903413)...................128 (x 1024 bytes) EXAMPLE: A system has 8 MB of main memory, 1 4-Way controller, 2 16-Way controllers, 1 IMLC, and 1 BMTC. Compute the size of the Dump Area as follows: 8 MB main memory (8 x 1024)....= 8192 (x 1024 bytes) 1 4-Way controller.............= 64 (x 1024 bytes) 2 16-Way controllers (2 x 128) = 256 (x 1024 bytes) 1 IMLC.........................= 64 (x 1024 bytes) 1 BMTC.........................= 128 (x 1024 bytes) _____ TOTAL 8704 (x 1024 bytes) "SIZE OF DUMP AREA (FOR SYSTEM DISKS ONLY):" 8704 (x 1024 bytes). Correct sizing of the Dump Area is especially critical on MPX 9000 and 9500 systems, because dumps to tape are not possible on these systems. This is because the BMTC, which is required to control tape operations on MPX 9000 and 9500 systems, is a shared memory controller. If it becomes necessary to enlarge the Dump Area, you must back up and reinitialize the system disks (options 1-4 in a TYPE 3 LOAD). When sizing the Dump Area, you may want to round up to the next megabyte or add an extra SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB018 Pg001 megabyte or two for future expansion. ORIGINATOR: N. PRENTISS SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB018 Pg002 FIB 00019 10/23/86 *** Error 47 in startup of Auto Dial utility - 8.4E/8.5C/9.5C *** Starting up the auto dial utility will cause an ERROR 47 in program ACS2 line 8010 after the first communication session terminates. The program generates this error because it is not passed any prefix information required to open the file "ADAPQ". The following patch addresses the problem in ACS2: >LOAD "BCOM" modify line 0305 from: 0305 BEGIN EXCEPT P$, C5$; REM "FIX EXTRACT IND 0 OF LSLOG BUG to the following: 0305 BEGIN EXCEPT P$, C5$, P4$, P7$, P8$; REM "FIX EXTRACT IND 0 OF LSLOG BUG (P$,C5$) REM "FIX AUTODIAL ERR 47 IN ACS2 (P4$, P7$, P8$) >SAVE ORIGINATOR: R. HINOJOSA SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB019 Pg001 FIB 00020 11/13/86 *** Differences with CONFIG.MGR utility (replaces INSTALL.CONFIG) *** As of releases 8.5D/9.5D, the INSTALL.CONFIG utility has been replaced by the CONFIG.MGR utility for the display and installation of configuration records. The 8.5D/9.5D Software Announcement #139 (which may now be printed out by Docwriter) documents how to use CONFIG.MGR. New utilities used to generate and display configuration records cause some configuration parameters to be displayed in a different format. The following is a summary of these differences: SYSTEM TYPE System Type for the 9500 is diplayed as "9000" on 9.5C. It is displayed as "9500" on 9.5D. (See Field Bulletin #174 for further pertinant information.) RELEASE LEVEL Configuration records generated for 8.4B/C/D/E are interchangeable in regard to release level. For example, a configuration record generated for release 8.4E can be installed on an 8.4B system and visa versa. Configuration records generated for 8.5B/C/D are interchangeable. Configuration records generated for 9.5C/D are also interchangeable in regard to release level. MAIN MEMORY SIZE Memory size is displayed in 128K units on release levels 8.5B and below. Memory is displayed in MB units on release levels 8.5C/9.5C and above. FILE SYSTEM SPACE File system space is displayed in 45 MB units on release levels 8.5C and below. It is displayed in MB units on 9.5C, 8.5D/9.5D and above. To convert 45 MB units to MB units for the BOSS SHEET for release levels 8.5C/9.5C and below, multiply. the number of 45 MB units by 45 and use that calculated number for File System Space. For releases 8.5D/9.5D and above, the total formatted capacities of the disks.should be entered on the BOSS SHEET as the MB units for File System Space. (The reason forthe two methods of calculating File System Space has to do with differences in the rounding procedures in the configuration utilities.) ISDC (SERIAL) PORTS ISDC Ports will display in one of the three different formats below: (The actual numbers used here are just examples.) a) MAI Async Terminals: 20 Non-slave Printers: 20 Non-MAI Async Devices: 20 b) MAI Async Terminals: 20 Non-slave Printers: 0 Non-MAI Async Devices: 0 c) MAI Async Terminals: 10 Non-slave Printers: 5 Non-MAI Async Devices: 5 All three formats indicate a maximum of 20 ISDC Ports. In addition, regardless of the format of the display, ISDC Ports may be configured in any combination SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB020 Pg001 of the three categories, (MAI Async Terminals, Non-slave Printers, and Non-MAI Async Devices), as long as the total ISDC ports configured does not exceed 20, (in this example). On release levels 8.5D/9.5D, CONFIG.MGR adds up the ISDC Ports in example a) above, and displays the number of MAXIMUM ISDC PORTS as 60. This is a bug in the display in CONFIG.MGR, as the actual number of MAXIMUM ISDC PORTS is 20 (in this example). This bug will be fixed in 8.6A/9.6A. CONFIGURATION RECORD WARNINGS AND CAUTIONS In addition to the bug mentioned under ISDC PORTS, the following configuration record bugs exist. All of these bugs will be fixed in 8.5E/9.5E and 8.6A/9.6A. None of these bugs affect the integrity of the configuration record. 1. Printouts of configuration records created for 7000 Series Systems will show. "7.5" for the release level instead of "8.5". However, the release level will display as "8.5" after the configuration record has been installed. 2. A few configuration records have some garbage characters appended to the right of the USER NAME. 3. After installation of the configuration record the following will be displayed: "Installation Complete (16,50,0,3)" The fourtuple is merely the number of the "Installation Complete" message and should be ignored. ORIGINATOR: N. PRENTISS SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB020 Pg002 FIB 00021 03/24/87 *** Rel 8.4E has problem if disk errors occur during SAVERESTORE *** If a disk error occurs during a disk node backup on OS release 8.4E, the utility may skip the rest of that node. For example, if a disk error occurs during the backup of the third file of a node containing 100 files, the utility has a problem which can cause the remaining 97 files to NOT be saved to tape; furthermore, the utility will not notify the user of the fact! Therefore, prior to doing any work on a customer's disk (on release 8.4E) which may destroy disk data, be certain the customer has verified that the disk is truly completely, backed up. The only work-around for this problem is to do a file list backup. ORIGINATOR: B. BERARD SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB021 Pg001 FIB 00022 04/28/87 *** Release 8.6A/9.6A Software Announcement *** MAI Basic Four, Inc. is pleased to announce that the new software release, 9.6A/8.6A, is now available. The 8.6A release is the recommended release for MPx 7000, 7100, and 8000 Series Systems. The 9.6A release is the recommended release for MPx 9000, 9100, and 9500 Series Systems. **************************************************** * * * PLEASE READ THE INSTALLATION INSTRUCTIONS BEFORE * * ATTEMPTING INSTALLATION OR UPGRADE. * * * * UPGRADES FROM RELEASE LEVELS 8.4D AND BELOW * * REQUIRE A CONVERSION TO THE NEW FILE SYSTEM. * * THIS ANNOUNCEMENT DOES NOT CONTAIN INSTRUCTIONS * * FOR THIS CONVERSION. THESE INSTRUCTIONS APPEAR * * IN THE SOFTWARE ANNOUNCEMENTS FOR RELEASES 8.4E * * AND 8.5A/B/C/D/E, AS WELL AS IN THE "BOSS/VS * * FILE CONVERSION USER GUIDE" M 5185A. THE * * CONVERSION CANNOT BE PERFORMED WITHOUT THESE * * INSTRUCTIONS. * * * * THIS ANNOUNCEMENT CONTAINS AN OVERVIEW OF THE * * NEW FEATURES OF 9.6A/8.6A. FOR A DETAILED * * EXPLANATION OF THESE FEATURES AND HOW TO USE * * THEM, YOU MUST HAVE THE FOLLOWING MANUALS: * * * * BUSINESS BASIC 86 REFERENCE MANAUAL M 6262 * * BOSS/VS USER GUIDE M 5098F * * BOSS/VS UTILITIES USER GUIDE M 5102E * * BOSS/VS INSTALLATION GUIDE M 5138D * * MAGNET/VS USER REFERENCE MANUAL M 6363 * * * * A NEW CONFIGURATION RECORD IS REQUIRED WHEN * * UPGRADING TO 8.6A AND 9.6A. * * * * PROGRAMS WRITTEN OR MODIFIED ON 9.6A/8.6A WILL * * NOT RUN ON PRIOR RELEASES. * * * * 9.6A/8.6A FEATURES NEW SYSTEM STARTUP PROCEDURES * * FOR MAGNET, SPOOLER, AND JOB MANAGER. IT IS * * ESSENTIAL TO REVIEW THE SYSTEM STARTUP SECTION * * BEFORE ATTEMPTING INSTALLATION OR UPGRADE. * * * **************************************************** Copyright 1987 by MAI Basic Four, Inc. All rights reserved. C O N T E N T S _ _ _ _ _ _ _ _ 1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . 2 2 HISTORY . . . . . . . . . . . . . . . . . . . . . . . . 4 3 BOSS/VS . . . . . . . . . . . . . . . . . . . . . . . . 7 3.1 GENERAL INFORMATION . . . . . . . . . . . . . . . . . 7 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg001 3.1.1 Software Announcement . . . . . . . . . . . . . . . 7 3.1.2 New file node . . . . . . . . . . . . . . . . . . . 7 3.2 CONFIGURATIONS . . . . . . . . . . . . . . . . . . . . 7 3.2.1 Configurations for the MPx 7000, 7100, and 8000 . . 7 3.2.2 Configurations for MPx 9000 and 9100 Series Systems 8 3.2.3 Configurations for MPx 9500 Series Systems . . . . . 9 3.3 UTILITIES . . . . . . . . . . . . . . . . . . . . . . 10 3.3.1 JOB MANAGER . . . . . . . . . . . . . . . . . . . . 10 3.3.1.1 Overview . . . . . . . . . . . . . . . . . . . . . 10 3.3.1.2 Jobs and Job Groups . . . . . . . . . . . . . . . 10 3.3.1.3 Job Names . . . . . . . . . . . . . . . . . . . . 11 3.3.1.4 System Resource Use Limits . . . . . . . . . . . . 12 3.3.1.5 Resource Use Statistics . . . . . . . . . . . . . 12 3.3.1.6 Utility Displays . . . . . . . . . . . . . . . . . 13 3.3.1.7 Job Group Activity Log . . . . . . . . . . . . . . 13 3.3.1.8 Running the JOB and GROUP Utilities . . . . . . . 13 3.3.1.9 JOB ACCOUNTING . . . . . . . . . . . . . . . . . . 14 3.3.1.9.1 Account Resource Use . . . . . . . . . . . . . . 14 3.3.1.9.2 Account Resource Limits . . . . . . . . . . . . 15 3.3.2 GETDEVINFO Utility . . . . . . . . . . . . . . . . . 17 3.3.2.1 Shared Memory Controller ID Code (Byte 6) . . . . 17 3.3.2.2 Device Type Codes (Byte 7) . . . . . . . . . . . . 18 3.3.2.2.1 Device Status Codes (Byte 8) . . . . . . . . . . 18 3.3.2.2.2 ISDC Line Number (Byte 9) . . . . . . . . . . . 19 3.3.3 SECURITY MANAGER Utility . . . . . . . . . . . . . . 19 3.3.4 INTRODUCTION TO THE SPOOLER . . . . . . . . . . . . 19 3.4 CLI BATCH SUBSYSTEM . . . . . . . . . . . . . . . . . 23 3.4.1 Purpose . . . . . . . . . . . . . . . . . . . . . . 23 3.4.2 Introduction . . . . . . . . . . . . . . . . . . . . 23 3.4.3 Creating a BATCH Job . . . . . . . . . . . . . . . . 24 3.4.4 INPUT Handling . . . . . . . . . . . . . . . . . . . 26 3.4.5 CLI in BATCH . . . . . . . . . . . . . . . . . . . . 26 3.4.6 Utilities in BATCH . . . . . . . . . . . . . . . . . 27 3.5 NEW LOAD SCREEN . . . . . . . . . . . . . . . . . . . 29 3.6 COMMUNICATIONS . . . . . . . . . . . . . . . . . . . . 31 3.6.1 19.2K BPS SUPPORT . . . . . . . . . . . . . . . . . 31 3.6.1.1 Introduction . . . . . . . . . . . . . . . . . . . 31 3.6.1.2 Notes . . . . . . . . . . . . . . . . . . . . . . 32 3.6.2 ENHANCED SERIAL PORT AVAILABILITY AFTER BOOT . . . . 32 3.6.3 MAGNET . . . . . . . . . . . . . . . . . . . . . . . 33 3.6.3.1 OVERVIEW . . . . . . . . . . . . . . . . . . . . . 33 3.6.3.2 FEATURES . . . . . . . . . . . . . . . . . . . . . 33 3.6.3.3 LIMITATIONS . . . . . . . . . . . . . . . . . . . 34 3.6.3.4 MEDIA SELECTION . . . . . . . . . . . . . . . . . 35 3.6.3.4.1 MAGNET LAN . . . . . . . . . . . . . . . . . . . 35 3.6.3.4.2 MAGNET WAN . . . . . . . . . . . . . . . . . . . 36 3.6.3.4.2.1 MAGNET WAN Connection Options . . . . . . . . 36 3.6.3.4.2.1.1 Public Packet Data Network . . . . . . . . . 36 3.6.3.4.2.1.2 Private Packet Data Network . . . . . . . . 37 3.6.3.4.2.1.3 Basic Four Point to Point . . . . . . . . . 37 3.6.3.5 REQUIREMENTS . . . . . . . . . . . . . . . . . . . 37 3.6.3.5.1 HARDWARE REQUIREMENTS . . . . . . . . . . . . . 37 3.6.3.5.1.1 LAN Hardware . . . . . . . . . . . . . . . . . 38 3.6.3.5.1.2 WAN Hardware . . . . . . . . . . . . . . . . . 38 3.6.3.5.2 SOFTWARE . . . . . . . . . . . . . . . . . . . . 38 3.6.3.5.2.1 LAN Software . . . . . . . . . . . . . . . . . 39 3.6.3.5.2.2 WAN Software . . . . . . . . . . . . . . . . . 39 3.6.3.6 INSTALLATION . . . . . . . . . . . . . . . . . . . 39 3.6.3.6.1 HARDWARE INSTALLATION . . . . . . . . . . . . . 39 3.6.3.6.1.1 LAN Subnetwork . . . . . . . . . . . . . . . . 40 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg002 3.6.3.6.1.2 WAN Subnetwork . . . . . . . . . . . . . . . . 40 3.6.3.6.2 SOFTWARE INSTALLATION . . . . . . . . . . . . . 40 3.6.3.7 CONFIGURATION . . . . . . . . . . . . . . . . . . 41 3.6.3.7.1 EZCONFIG . . . . . . . . . . . . . . . . . . . . 41 3.6.3.7.2 NETWORK MANAGEMENT FACILITIES . . . . . . . . . 42 3.6.3.8 STARTUP . . . . . . . . . . . . . . . . . . . . . 44 3.6.3.9 OPERATION . . . . . . . . . . . . . . . . . . . . 45 3.6.3.9.1 APPLICATIONS . . . . . . . . . . . . . . . . . . 45 3.6.3.9.2 UTILITIES . . . . . . . . . . . . . . . . . . . 47 3.6.3.10 TROUBLE-SHOOTING . . . . . . . . . . . . . . . . 47 3.6.3.11 LAN CONTROLLER . . . . . . . . . . . . . . . . . 49 3.6.3.11.1 7000/7100/8000 MMC Addressing . . . . . . . . . 49 3.6.3.11.2 9000 MMC Addressing . . . . . . . . . . . . . . 50 3.6.3.11.3 Station Addressing . . . . . . . . . . . . . . 51 3.6.3.11.4 Board Sub-type . . . . . . . . . . . . . . . . 51 3.6.3.12 DOCUMENTATION . . . . . . . . . . . . . . . . . . 52 3.6.4 FILE TRANSFER FACILITY . . . . . . . . . . . . . . . 52 3.6.4.1 INSTALLATION . . . . . . . . . . . . . . . . . . . 52 3.6.4.1.1 SOFTWARE INSTALLATION . . . . . . . . . . . . . 52 3.6.4.1.2 HARDWARE INSTALLATION . . . . . . . . . . . . . 52 3.6.4.2 CONFIGURATION . . . . . . . . . . . . . . . . . . 52 3.6.4.3 COMPATIBILITY . . . . . . . . . . . . . . . . . . 53 3.6.4.4 ITEMS TO NOTE . . . . . . . . . . . . . . . . . . 53 3.6.4.5 DOCUMENTATION . . . . . . . . . . . . . . . . . . 53 3.7 BUSINESS BASIC 86 . . . . . . . . . . . . . . . . . . 54 3.7.1 BUSINESS BASIC 7.3A AND 8.6A . . . . . . . . . . . . 54 3.7.2 COMPATIBILITY ENHANCEMENTS . . . . . . . . . . . . . 54 3.7.3 BB86 ENHANCEMENTS . . . . . . . . . . . . . . . . . 55 3.7.4 SPOOLER CONTROL . . . . . . . . . . . . . . . . . . 55 3.7.5 SYSTEM INDEPENDENT ENHANCEMENTS . . . . . . . . . . 57 3.7.5.1 CREATE: System Independent File Creation . . . . . 58 3.7.5.1.1 ATTR: System Independent File Information . . . 58 3.7.6 SYSTEM DEPENDENT IN BB86 . . . . . . . . . . . . . . 60 3.7.7 FILE NAME TRANSLATION - MAGNET SUPPORT . . . . . . . 60 3.7.8 PROGRAM GENERATION ENHANCEMENTS . . . . . . . . . . 62 3.7.9 MULTI-KEY FILES . . . . . . . . . . . . . . . . . . 62 3.7.9.1 Introduction . . . . . . . . . . . . . . . . . . . 62 3.7.9.2 Possible Applications . . . . . . . . . . . . . . 63 3.7.9.2.1 Existing Applications That Use Sets of Files . . 63 3.7.9.2.2 Existing Applications That Use the Sort Utility 63 3.7.9.2.3 Enhancement of Existing Applications . . . . . . 63 3.7.9.2.4 Rewriting Applications or Writing New Applicatio 63 3.7.9.3 Benefits of Using Multi-Keyed Files . . . . . . . 64 3.7.9.3.1 Reduced File Maintenance . . . . . . . . . . . . 64 3.7.9.3.2 Improved Data Integrity . . . . . . . . . . . . 64 3.7.9.3.3 Improved Performance . . . . . . . . . . . . . . 65 3.7.9.3.4 Reduced Disk Space Requirements . . . . . . . . 65 3.7.9.3.5 Reduced Complexity of Applications . . . . . . . 65 3.7.9.4 Syntax For Multi-Keyed Files . . . . . . . . . . . 66 3.7.9.4.1 Creating a Multi-Keyed File . . . . . . . . . . 66 3.7.9.4.1.1 Format String Overview . . . . . . . . . . . . 67 3.7.9.4.1.2 Field Information . . . . . . . . . . . . . . 69 3.7.9.4.1.2.1 Fixed-length String Fields . . . . . . . . . 69 3.7.9.4.1.2.2 Fixed-length Numeric Fields . . . . . . . . 70 3.7.9.4.1.2.3 Variable-length Fields . . . . . . . . . . . 71 3.7.9.4.1.2.4 Composite Fields . . . . . . . . . . . . . . 72 3.7.9.4.1.2.5 When Fields Don't Directly Follow Each Other 75 3.7.9.4.1.2.6 Gaps In The Record . . . . . . . . . . . . . 78 3.7.9.4.2 Reading Records From a Multi-Keyed File . . . . 78 3.7.9.4.2.1 Introductory Examples . . . . . . . . . . . . 78 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg003 3.7.9.4.2.2 Expanded KEY= Capabilities . . . . . . . . . . 79 3.7.9.4.2.3 Reading Using FIELD ALIAS . . . . . . . . . . 80 3.7.9.4.2.4 RETAIN and UNPACK . . . . . . . . . . . . . . 81 3.7.9.4.2.5 Other Variants On the READ Statement . . . . . 82 3.7.9.4.3 Writing Records To a Multi-Keyed File . . . . . 82 3.7.9.4.4 Removing Records From a Multi-Keyed File . . . . 85 3.7.9.4.5 The KEY Function . . . . . . . . . . . . . . . . 86 3.7.9.4.6 The FID Function . . . . . . . . . . . . . . . . 86 3.7.9.4.7 The FMTINFO Function . . . . . . . . . . . . . . 86 3.7.9.4.8 INITFILE . . . . . . . . . . . . . . . . . . . . 89 3.7.9.4.9 SETFIELD . . . . . . . . . . . . . . . . . . . . 89 3.7.9.4.10 FIELD ALIAS . . . . . . . . . . . . . . . . . . 90 3.7.9.4.11 Miscellany . . . . . . . . . . . . . . . . . . 91 3.7.9.5 Sample Programs . . . . . . . . . . . . . . . . . 92 3.7.9.5.1 Printing a Multi-Keyed File . . . . . . . . . . 94 3.7.9.5.2 Updating a Multi-Keyed File . . . . . . . . . . 95 3.7.9.5.3 Loading Data Into a Multi-Keyed File . . . . . . 96 3.7.9.6 Conversion of Existing Applications . . . . . . . 97 3.7.9.6.1 Selection of Appropriate Candidate . . . . . . . 97 3.7.9.6.2 Conversion Approaches . . . . . . . . . . . . . 97 3.7.9.6.3 Selection of Keysets . . . . . . . . . . . . . . 97 3.7.9.6.3.1 Selection of Fields Which Should Not Be Perman 98 3.7.9.6.3.2 Selecting Records Based on Non-Keyed Fields . 98 3.7.9.6.4 Suggestions for Conversion . . . . . . . . . . . 99 3.7.9.6.4.1 Data Layout Diagrams . . . . . . . . . . . . . 99 3.7.9.6.4.2 Field Separator Characters . . . . . . . . . . 99 3.7.9.6.4.3 Subfields . . . . . . . . . . . . . . . . . 100 3.7.9.6.4.4 The WriteThru File Attribute on BOSS/VS . . 101 3.7.9.6.4.5 Definition of Keysets for Conversion . . . . 101 3.7.9.7 Recovery of Multi-Keyed Files on BOSS/VS . . . . 101 3.7.9.7.1 Ways to repair Multi-Key Files . . . . . . . . 101 3.7.9.7.2 File Recovery Sequence . . . . . . . . . . . . 102 3.7.9.8 Multi-Key Transport . . . . . . . . . . . . . . 103 3.7.9.9 Performance Characteristics . . . . . . . . . . 107 3.7.9.9.1 File Conversion . . . . . . . . . . . . . . . 107 3.7.9.9.2 Addition of a Keyset . . . . . . . . . . . . . 108 3.7.9.9.3 Deletion of a Keyset . . . . . . . . . . . . . 108 3.7.9.9.4 Reconstruct Utility on BOSS/VS . . . . . . . . 108 3.7.9.9.5 Record Access . . . . . . . . . . . . . . . . 108 3.8 TYPE 3 LOAD . . . . . . . . . . . . . . . . . . . . 110 3.8.1 MAIN MENU . . . . . . . . . . . . . . . . . . . . 110 3.8.2 DISPLAY VOLUME AND FAMILY INFORMATION . . . . . . 111 3.8.3 INITIALIZATION OPTIONS. . . . . . . . . . . . . . 112 3.8.3.1 Change Volume Label Information . . . . . . . . 112 3.8.3.1.1 Initialization . . . . . . . . . . . . . . . . 112 3.8.3.1.2 Update Family Information . . . . . . . . . . 113 3.8.3.1.2.1 Initialization . . . . . . . . . . . . . . . 113 3.8.3.1.3 Initialize Family Directory . . . . . . . . . 113 3.8.3.1.4 Change Installation Parameters . . . . . . . . 113 3.8.3.1.5 Check File System Tag . . . . . . . . . . . . 114 3.8.3.2 Mount/Dismount Disk . . . . . . . . . . . . . . 115 3.8.3.3 Change Master/Backup Status . . . . . . . . . . 115 3.8.3.4 Copy Options . . . . . . . . . . . . . . . . . . 115 3.8.3.4.1 Disk to Tape Family Backup . . . . . . . . . . 116 3.8.3.4.1.1 Introduction . . . . . . . . . . . . . . . . 116 3.8.3.4.1.2 Save Operational Characteristics . . . . . . 116 3.8.3.4.2 Restore Family . . . . . . . . . . . . . . . . 117 3.8.3.4.2.1 Restore Initial Display . . . . . . . . . . 117 3.8.3.4.2.2 Restore Operational Characteristics . . . . 118 3.8.3.5 Disk to Disk Sequential Family Backup . . . . . 120 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg004 3.8.3.5.1 Introduction . . . . . . . . . . . . . . . . . 120 3.8.3.6 Copy Family From Disk to Disk . . . . . . . . . 120 3.8.3.6.1 Introduction . . . . . . . . . . . . . . . . . 120 3.8.3.6.2 Copy Family Display . . . . . . . . . . . . . 120 3.8.3.6.3 Requirements for Copying . . . . . . . . . . . 121 3.8.3.6.4 Copy 300 Mb 8" to 285 Mb Disk Drives . . . . . 121 3.8.3.6.5 Copy Process . . . . . . . . . . . . . . . . . 122 3.8.3.6.6 Error Handling . . . . . . . . . . . . . . . . 122 4 DIAGNOSTICS . . . . . . . . . . . . . . . . . . . . . 124 5 HARDWARE . . . . . . . . . . . . . . . . . . . . . . . 125 5.1 LARLS FOR PCBAS FOR THE MPX 7000, 7100, AND 8000 . . 125 5.2 LARLS FOR PCBAS FOR MPX 9000, 9100, AND 9500 SERIES 125 5.3 LOCAL AREA NETWORK CONTROLLER (LAN) . . . . . . . . 127 6 INSTALLATION . . . . . . . . . . . . . . . . . . . . . 128 6.1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . 128 6.2 NEW INSTALLATION . . . . . . . . . . . . . . . . . . 128 6.2.1 Installing the O.S. . . . . . . . . . . . . . . . 128 6.2.1.1 ALT LOAD . . . . . . . . . . . . . . . . . . . . 128 6.2.1.2 ENTER A TYPE 3 LOAD (SPECIAL FUNCTIONS) . . . . 129 6.2.1.2.1 OPTION 1 (CHANGE VOLUME LABEL INFORMATION) . . 129 6.2.1.2.2 OPTION 2 (UPDATE FAMILY INFORMATION) . . . . . 130 6.2.1.2.3 OPTION 3 (INITIALIZE FAMILY DIRECTORY) . . . . 130 6.2.1.2.4 OPTION 4 (CHANGE INSTALLATION PARAMETERS) . . 130 6.2.1.3 Restoring the O.S. . . . . . . . . . . . . . . . 131 6.3 8000 UPGRADE FROM RELEASE LEVELS ABOVE 8.4D . . . . 133 6.3.1 Saving Files to Tape . . . . . . . . . . . . . . . 133 6.3.2 Operating System Update . . . . . . . . . . . . . 133 6.3.2.1 Installing the O.S. . . . . . . . . . . . . . . 133 6.3.2.1.1 ALT LOAD . . . . . . . . . . . . . . . . . . . 133 6.3.2.1.2 CHANGE INSTALLATION PARAMETERS . . . . . . . . 133 6.3.2.2 Restoring the O.S. . . . . . . . . . . . . . . . 134 6.3.2.3 Installing the Configuration Record . . . . . . 135 6.3.3 UPDATING OTHER O.S. SLOTS . . . . . . . . . . . . 136 6.3.3.1 UPDATING SLOT ONE (1) . . . . . . . . . . . . . 136 6.3.3.2 UPDATING WCS SLOT TWO (2) . . . . . . . . . . . 137 6.3.3.3 UPDATING SLOT THREE (3) . . . . . . . . . . . . 137 6.3.3.3.1 Updating O.S. Slot Three (3) . . . . . . . . . 137 6.3.3.4 Updating WCS Slot Three (3) . . . . . . . . . . 138 6.3.3.4.1 WCS Slot Three on 7000/7100 Series Systems . . 138 6.3.3.4.2 WCS Slot Three on 8000 Series Systems . . . . 138 6.3.4 SLOT INFORMATION . . . . . . . . . . . . . . . . . 138 6.4 UPGRADING TO 9.6A AND THE MPX 9000, 9100, AND 9500 . 140 6.4.1 SPECIAL CONSIDERATIONS . . . . . . . . . . . . . . 140 6.4.2 PRINTING OUT THE TERMINAL CONFIGURATION RECORD . . 140 6.4.3 SAVING FILES TO TAPE . . . . . . . . . . . . . . . 140 6.4.4 OPERATING SYSTEM UPDATE . . . . . . . . . . . . . 141 6.4.4.1 ALT LOAD . . . . . . . . . . . . . . . . . . . . 141 6.4.4.2 TYPE 3 LOAD (SPECIAL FUNCTIONS) . . . . . . . . 141 6.4.4.2.1 Updating Installation Parameters . . . . . . . 141 6.4.4.2.1.1 OPTION 4 (CHANGE INSTALLATION PARAMETERS) . 141 6.4.4.2.1.2 Sizing the Dump Area . . . . . . . . . . . . 142 6.4.4.2.2 Restoring the O.S. Files . . . . . . . . . . . 142 6.4.4.2.3 Installing the Configuration Record . . . . . 143 6.4.4.3 UPDATING OTHER O.S. SLOTS . . . . . . . . . . . 144 6.4.4.3.1 Updating Slot One (1) . . . . . . . . . . . . 144 6.4.4.3.2 Updating WCS Slot Two (2) . . . . . . . . . . 145 6.4.4.3.3 Updating Slot Three (3) . . . . . . . . . . . 145 6.4.4.3.3.1 Updating O.S. Slot Three (3) . . . . . . . . 145 6.4.4.3.3.2 Changing the Load Sector for Slot Three (3) 146 6.4.4.3.3.3 Updating WCS Slot Three (3) . . . . . . . . 146 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg005 6.4.5 Slot Information . . . . . . . . . . . . . . . . . 146 6.5 SYSTEM STARTUP . . . . . . . . . . . . . . . . . . . 148 6.5.1 Standard Startup Command File on 8.6A/9.6A BOSS/VS 148 6.5.1.1 Command File Definitions . . . . . . . . . . . . 148 6.5.2 Implications . . . . . . . . . . . . . . . . . . . 149 7 RELATED DOCUMENTATION . . . . . . . . . . . . . . . . 152 INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . 153 T A B L E S and F I G U R E S _ _ _ _ _ _ ___ _ _ _ _ _ _ _ Table 3-1. DEVICE TYPE CODES . . . . . . . . . . . . . . . 18 Table 3-2. Utilities and Commands in BATCH . . . . . . . . 28 Figure 6-1. Restore Screen . . . . . . . . . . . . . . . 132 Figure 6-2. Restore Screen . . . . . . . . . . . . . . . 135 Figure 6-3. Operating System Information . . . . . . . . 139 Figure 6-4. Restore Screen . . . . . . . . . . . . . . . 143 Figure 6-5. Operating System Information . . . . . . . . 147 1. INTRODUCTION ____________ The following enhancements are contained in the 9.6A/8.6A release: o A new and enhanced SPOOLER. o New JOB MANAGER utilities, which provide control over user processes and collect and display system resource use statistics. o JOB ACCOUNTING, an optional, chargeable feature of JOB MANAGER, which sets account resource limits and displays system resource use statistics for user accounts. o MAGNET, an optional, chargeable feature, which includes a Local Area Network and a Wide Area Network. o BUSINESS BASIC 86, which includes intersystem compatibility features, program generation tools, more system independent features, file name translation (primarily for MAGNET support), and MULTI-KEY FILES. o Support for 19.2K bps asynchronous communications. o SECURITY utility enhancements. o A Command Language BATCH SUBSYSTEM facility, which allows tasks to run in background mode. o Support for 24 megabytes of main memory on MPx 9500 Series Systems. o Support for 255 devices on the Mpx 9530. As of the 8.5D/9.5D releases, the INSTALL.CONFIG utility has been replaced by the CONFIG.MGR utility. A new configuraion record is required when upgrading to 9.6A/8.6A from an 8.4 or 8.5 release. A new configuration record is also required when upgrading from 7000/7100/8000 Series Systems to 9000/9100/9500 Series Systems. It is required that 8000 systems being upgraded to 9.6A run on release 8.4E or an 8.5 release for a minimum of one week prior to upgrade. It is recommended that 8000 systems being upgraded to 9.6A run on 8.6A prior to upgrade. 9.5 systems should upgrade directly to 9.6A. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg006 A presite survey is required before upgrading to the MPx 9000, 9100, or 9500. (See Field Bulletin 161A). When upgrading to 9.6A/8.6A from releases prior to 8.5C/9.5C, an ALT LOAD must be done before the O.S. files are restored. this is because certain files will not restore (including the drivers for the ISDC controllers) when on releases prior to 8.5C/9.5C. Sections documented in this 9.6A/8.6A announcement supersede those sections in previous announcements. Copyright 1987 by MAI Basic Four, Inc. All rights reserved. History 2. HISTORY _______ 8.5E/9.5E Acceptable This release provided improvements to the COPY, SAVERESTORE, and UPDATE.RIGHTS utilities, BASIC, the File System, and Type 3 Load Backup. 8.5D/9.5D Acceptable Enhancements include: A new CONFIG.MGR utility for displaying and installing configuration records; Four Spooler fixes; DISKANALYZER reconstruction of serial files; Manual selection of different print modes on DMP printers; an optional enhanced ATP package. 8.5C/9.5C Obsolete Enhancements include: Expanded ERRORLOG reporting; Optimization of DataWord files; Number of logical channels increased to 64; Support for 8 bit character sets; DISKANALYZER reporting of required disk space for reconstruction. Mpx 9000 and 9500 systems only: 32 bit CPU; increased main memory; number of maximum devices increased to 164; new DMA controller for increased performance; enhanced CPU processing for faster arithmetic and logical operations; RSTACK cache; overall performance increase which is 2-3 times that of 7000/7100/8000 systems; support for the faster 8-inch fixed disk. Mpx 9500 only: DATA and CODE caches for additional increased performance. 8.5B Obsolete In this release the system model number has been included in the configuration record, the COMPARE utility has been fixed so that it completely compares BASIC program files, and a new TBC AUTODIAL feature allows for definition and retrieval of multiple station lists. 8.5A Obsolete Enhancements include: Increased file system concurrency for greater throughput, support for 7000/7100 series systems, proportional growth for DIRECT and SORT files, maximum number SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg007 of open files increased to 512, maximum number of tasks sharing same file increased to 512, file selectable write-through, DISKANALYZER also available in stand-alone mode, DISKANALYZER reconstruct of directory and available space files, maximum number of system printers increased to 99, system dumps written directly to tape, system support for the DMP serial printer, new terminal services error utility, DataWord printer queue enhancements, enhanced SAVERESTORE History utility. 8.4E Acceptable This release contains all the features of the 8.5A/B/C/D releases, with the exception of the 8.5 performance enhancements. 8.4D Obsolete Contained fixes for BASIC PRECISION, EXTTAPE, COBOL, and FILESIZE. 8.4C Obsolete Enhanced features included: Buffered Magnetic Tape Controller, 1/2" tape support, DEDICATE with expanded error reporting, new ISDC OS for 4-way, 8-way and 16-way, FILESIZE utility. 8.4B Obsolete Enhanced features include: 8 megabytes of main system memory, 16-port Asynchronous Controller, point-to-point file specification, QUIET mode for utilities, BASIC statement numbers up to 16000, Buffered Magnetic Tape Controller (BMTC) 1/4" tape support, S/10 Industry Standard Printer as slave printer. 8.4A Obsolete This release contained significant enhancements including 6 megabytes of main system memory, 96 devices, 84 total serial devices, disk to disk sequential family backup, enhanced hardware error log, system load progress monitor, and fast reconstruct utility. 8.2C Obsolete This release contained a WCS fix to support rezero fault clear, disk error recovery and a fix to the IMLC. 8.2B Obsolete This release contained all of the above features but was required for the 8000 Series systems due to a change in the WCS image for that hardware. 8.2A Obsolete This release contained significant enhancements providing NO EXTEND BASIC, 68 serial devices, math functions, X.25 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg008 Communications, DataWord 3.0. File System write through and History BULLETIN board availability. 8.1B Obsolete Enhanced features include: 31 logical units in BASIC, increase in file system cache from 208 to 225 unique files, MULTIREELSR, family image backups, SAVERESTORE backup files having the Lack-of-Integrity bit set. Bugs were fixed in DISKANALYZER, SAVERESTORE and many of the system dumps. 8.1A Obsolete Introduction of the System 810 hardware and BOSS/VS software. 3. BOSS/VS _______ 3.1. GENERAL INFORMATION _______ ___________ 3.1.1. Software Announcement ________ ____________ With this release, a copy of this software announcement exists as a serial file on the system, which allows the user to print a copy, if needed. This file can be submitted to a printer using the SUBMIT utility. The document file is named: (family).R6AXX.INST.DOC.SA6A.TEXT 3.1.2. New file node ___ ____ ____ Beginning with the 9.6A/8.6A release, a new node is provided on the Operating System tape called ".R6Axx.UNSPRTD." ("UNSPRTD" stands for "Unsupported".). This node contains one file ("MIRTH", see the section on Multikeyed files) on this release. This node has been created to provide useful shell programs that the user can later modify for their own purposes. Programs provided in this node are unsupported and should be regarded as examples. 3.2. CONFIGURATIONS ______________ NOTE 1: The number of "High Activity Tasks" is approximate and largely dependent on the application. The relative relationship of the numbers between configurations is more important than the actual numbers themselves. NOTE 2: System configurations of the MPx 9000 and 9500 Series Systems are based on the use of the LS-700 power supply mainframes. Original 810 systems will not meet all defined maximum configurations listed. 3.2.1. Configurations for the MPx 7000, 7100, and 8000 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg009 ______________ ___ ___ ___ _____ _____ ___ ____ The maximum configuration for MPx 7000, 7100, and 8000 Series Systems, Models 7030, 7130, and 8030, is as follows: 116 Devices - A combination of 8-ways, 16-ways, the 4 ports on the MCS PCBA, MDTs and HVDTs up to a total of 116 devices are supported. 3 CPU sets 10 ISDCs: 16-ways (7 maximum) and/or 8-ways 32 Ghost tasks 24 High speed videos (HVDT) 8 Disk drives 4 Parallel printers 8 Megabytes of memory 2 Magnetic tape drives (MTR, MTS and/or MCS) Configurations 4 Intelligent Multi-Line Controllers (IMLC) 8 DataWord II terminals 4 TBC lines 64 3270 terminals 8 X.25 lines 2 Auto-Call Units (ACU) 99 Serial printers 99 System printers (total serial and parallel not to exceed 99) 2 Buffered Magnetic Tape Controllers 27 High activity concurrent tasks 1 LAN controller Note: There is a maximum of 9 memory assembly boards in any combination of 1/2 Mb, 1 Mb, 2 Mb, 4 Mb and BMTCs (a maximum of 3 boards per chassis). Models 7010/7110/8010 and 7020/7120/8020 have the same configuration limits as Models 7030 and 8030 above, with the following limitations: 7010/7110/8010 7020/7120/8020 1 CPU set 2 CPU sets 2-4 Mb memory 2-6 Mb memory 20 Devices 52 Devices 12 Concurrent tasks 20 Concurrent tasks (high activity) (high activity) 19 System printers 51 System printers 3.2.2. Configurations for MPx 9000 and 9100 Series Systems ______________ ___ ___ ____ ___ ____ ______ _______ The maximum configuration for MPx 9000 and 9100 Series Systems, Model 9020 and model 9120 is as follows: 116 Devices - A combination of 8-ways, 16-ways, the 4 ports on the MCS PCBA, MDTs and HVDTs up to a total of 116 devices are supported. 2 CPU sets with Evaluation Stack and Rstack Cache 10 ISDCs: 16-ways (6 maximum) and/or 8-ways (10 maximum) 32 Ghost tasks 24 High speed videos (HVDT) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg010 12 8-inch fixed or 8 14-inch disk drives 8 Parallel printers 12 Megabytes of memory 2 Magnetic tape drives including MTR, MTS and/or MCS (1 maximum) 4 Intelligent Multi-Line Controllers (IMLC) 8 Dataword II terminals 4 TBC lines 64 3270 terminals 8 X.25 lines 2 Auto-Call Units (ACU) Configurations 99 Serial printers 99 System printers (total serial and parallel not to exceed 99) 4 DMA controllers 2 Buffered Magnetic Tape Controllers 43 High activity concurrent tasks 1 LAN controller Model 9010 and 9110 has the same configuration limits as the 9020 and 9120 above, with the following exceptions: 1 CPU set with Evaluation Stack and Rstack Cache 68 Devices 10 ISDCs: 16-ways (4 maximum) and/or 8-ways (8 maximum) 67 Serial printers 75 System printers (total serial and parallel not to exceed 75) 26 High activity concurrent tasks 3.2.3. Configurations for MPx 9500 Series Systems ______________ ___ ___ ____ ______ _______ The maximum configuration for MPx 9500 Series Systems, Model 9530, is the same as the maximum configuration for the MPx 9000 and 9100 Series Systems, Models 9020 and 9120 with the following exceptions: 3 CPU sets with Evaluation Stack Rstack Cache Code Cache Data Cache 255 Devices 16 ISDCs: 16-ways (16 maximum) and/or 8-ways (16 maximum) 24 Megabytes of memory (see Hardware section for mandatory revision levels for main memory support above 12 megabytes) 16 8-inch fixed or 8 14-inch disk drives 73 High activity concurrent tasks Models 9510 and 9520 have the same configuration limits as Model 9530 with the following exceptions: 9510 9520 1 CPU set 2 CPU sets (same caches as the 9530) (same caches as the 9530) 10 ISDCs: 16-way (4 maximum) 10 ISDCs: 16-way (6 maximum) 8-way (8 maximum) 8-way (10 maximum) 84 Devices 132 Devices 83 Serial printers 53 Concurrent tasks 91 System printers (high activity) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg011 (total serial and parallel) 32 Concurrent tasks (high activity) 3.3. UTILITIES _________ 3.3.1. JOB MANAGER ___ _______ 3.3.1.1. Overview ________ The Job Manager feature gives the user more effective control of jobs that are running on the system. This new feature is in addition to the existing operator control features, which work the same as on previous releases. Job Management provides added levels of control over user processes, and allows the system operator to control and observe job and job group activity. The Job Manager consists of two utilities: Group Control (GROUP) and Job Control (JOB). Group Control is used by the system operator to display, modify, create, and delete job groups, to record job group activity, and also to set system resource use limits. Job Control is available for any user to create, display, modify, and delete jobs. It can also be used to send and receive messages, and to set system resource use limits on the user jobs. The Job Manager treats system processes and user processes as jobs attached to job groups. System processes run independently of any user activity, and are controlled by BOSS/VS. They are attached to a built in system group (SYSGROUP). User jobs are controlled by the user. Job groups can only be controlled by the system operator. 3.3.1.2. Jobs and Job Groups ____ ___ ___ ______ A job consists of a program and its associated process(es), and files, as well as control information that identifies the job and sets parameters for its execution and use of system resources. Each job is associated with a user account and is identified by a job name or job number. Using the Job Control utility, users can start jobs that run on job groups. Each job is attached to a job group. A job may also be attached to a terminal for interactive communication with users (interactive mode), or it may run independently (batch mode). The method used to start a job determines its job type: a terminal job is started by a user from a terminal or the START command; a batch job is started by the JOB.CREATE command; and a system job is started automatically by BOSS/VS. A job group is a BOSS/VS system structure that allows a specified number of jobs to run on the system, and accepts SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg012 Job Manager more jobs for later execution. Using the Group Control utility, the system operator can define and control the number and type of user job groups on the system. Each group may have various job parameters associated with it, i.e., number of jobs that may run concurrently, priority, limits on system resource use, etc. When a job is entered into the system, it is attached to a job group. There are three job types: terminal, batch, and system. A terminal job is started when a user signs on at a terminal device and runs in interactive mode. A batch job can only be started by the JOB.CREATE command and runs in batch mode. Input and output activity is performed on disk files, though programs may be open and use other devices as well. A system job can be started by BOSS/VS. It allows a log of system activity and accounting of system resources not used directly by user programs. 3.3.1.3. Job Names ___ _____ Each job is identified by a unique job name and job number that is assigned to it when the job is created. Terminal job names are assigned when the user signs on. Batch job names may be assigned by the user, or the job may be assigned a default job name. The job number is assigned to the job and can be used by most commands instead of the job name. The Job Manager uses a default 'user base name' when it assigns names to terminal, batch, and system jobs. The name consists of (up to) the first four characters of the major account name, a period (.), and (up to) the first four characters of the minor account name of the user who starts the job. For example, the user base name 'PAYROLL.BARBARA' is PAYR.BARB. The user base name of 'PR.BAR' is 'PR.BAR' because it is short. A device or process name suffix is added. Terminal device names are 'T' followed by the device number. Process names are defined by the job type. For terminal jobs, the name is the device name. For batch jobs, the name is 'B' followed by the job number. For system jobs, the name is 'S' followed by the job number. A terminal job name is assigned when a user signs on at a Job Manager terminal. It consists of the 'user base name', a period (.), and the process name. For example, 'PR.BAR.T15'. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg013 A batch job name is assigned when the batch job is created, if a name has not been specified by the job creator. It consists of the 'user base name', a period (.), and the process name. For example, 'PR.BAR.B123'. A system job name is assigned when the system job is created. It consists of the 'user base name', a period (.), and the process name. For example, 'SYS.MGR.S41'. 3.3.1.4. System Resource Use Limits ______ ________ ___ ______ The system operator may set limits on the system resources that a job may use, and the system operator or the user can specify that a batch job is to be terminated if resource use limits are exceeded. (The total resources that a user account ____ _______ may use is controlled by the Job Accounting utility, which is discussed in the section on JOB ACCOUNTING in this announcement.) After a job has been started, it is terminated only by the specification of the user. Each job has a set of resource use statistics and a set of resource limit parameters. Each job also has a "limits" flag that controls how the limits affect the job. When a job is created it gets the set of resource limits from its associated group. The job limits flag is specified by the user. The user or system operator may change the job limits or the limits flag at any time with the commands of the Job Control utility. The system operator may change the set of limit parameters of any group with the commands of the Group Control utility. The statistics of each job are checked by the Job Manager every ten minutes. The counts for each resource are accumulated and compared to the corresponding job limit. If any of the job limits are exceeded, the job limit error flag is set, and action is taken depending on the job limits flag. If the limits flag is false, no action is taken, and the job continues to run normally, with the limit error flag set. If the limits flag is true, a message is sent to the terminal of an interactive job; this will be repeated every ten minutes. For batch jobs, the job is terminated when a limit error occurs, and the limits flag is true. 3.3.1.5. Resource Use Statistics ________ ___ __________ Resource use statistics are the number of accesses that a process makes on a resource, or the number of units of a resource that the job consumes. The Job Manager accumulates Job Manager resource use statistics for each job and group. The resource use statistics are not accumulated continuously, but only when certain key events take place, e.g, a file being closed, the job being rescheduled, Job Manager checking job limits, or the job terminating. As a result, a display of current Job or Group statistics may be somewhat behind the SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg014 actual current state of the job or group, and a job is not terminated the instant it exceeds a resource limit. The total job statistics are complete after the job terminates. Partial job statistics are not maintained for jobs interrupted by a system reload. When a job terminates, the total job statistics are added to the group statistics. The group statistics reflect the total resource use of all jobs that have run and terminated on the group; they are not the limits for all jobs that run on the group. 3.3.1.6. Utility Displays _______ ________ The JOB and GROUP utilities provide a summary and detail display of the current status of jobs and job groups. For most functions, it also provides a Function Report containing a list of the names of the jobs or groups that the function operated on and the results of the operation. The Function Report can be listed on the terminal or sent to another file or device. 3.3.1.7. Job Group Activity Log ___ _____ ________ ___ The Job Manager maintains a Job Group Activity Log that is separate from the current status display for jobs and job groups. Each job group has its own associated log which records the history of activity on the group. The log may be set to direct output to a terminal, a printer, or a disk file. Events such as accept job, run job, and terminate job are automatically recorded in this log. Jobs within the group may also record text as entries in the log. 3.3.1.8. Running the JOB and GROUP Utilities _______ ___ ___ ___ _____ _________ The JOB and GROUP utilities can be run in interactive mode or command mode. Instructions for running the utilites in can be found in the Help Screens for the JOB and GROUP utilities. Further information on Job Manager and the JOB and GROUP utilities can be found in the BOSS/VS Utilities User Guide, M _______ _________ ____ _____ 5102E. Job Manager 3.3.1.9. JOB ACCOUNTING ___ __________ Job Accounting is a chargeable option of Job Management. The system operator can use the Job Accounting utility to display the accumulated system resource use statistics for each user account, to specify the collection of accounting statistics for user accounts, and to set resource use limits for any user account. The use of Job Accounting requires that the option be turned on in the System Configuration Record. The Job Accounting utility also provides an output list of account names when a range of user account names is entered SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg015 for a function. The list contains the names of the user accounts that the function is operating on and the results of the operation. The report is displayed when the function begins to execute. When the function is run in interactive mode or when the QUIET parameter is FALSE in command mode, the output list is displayed on the terminal. It can also be sent to a file or device by the OUTPUT DEVICE parameter. The VERIFY parameter and the PAUSE ON ERRORS parameter provide the user with a means of selectively processing the names in the list. The initial default for both parameters is TRUE. The current default is the last entered selection. 3.3.1.9.1. Account Resource Use _______ ________ ___ The functions of the Job Accounting utility can assist the system operator in controlling the amount of system resources that each user may use. If an account has used more of any resource than the corresponding account limit, that account may not be used to sign onto the system, create new batch jobs, or use the system Spooler to output print jobs. The account limits are never used to terminate a job once the job has started. Job limit termination is controlled by the Job Control utility, which is described in section 3.3.1 in this announcement. The recording of account resource statistics and checking of account limits is done only when Job Accounting is 'ON'. If Job Accounting is 'OFF', resource use statistics are not recorded, and account limits are not checked. The Job Accounting utility maintains a record of account information for each account. The record contains a set of account resource statistics, a set of account resource limits, a limit error flag, and a 'limited' flag. The resource use statistics are the number of accesses that a job makes on a resource, or the number of units of a resource that a job consumes. Job Manager When Job Accounting is 'ON', the total job resource use statistics are added to the user account when a job terminates. The account resource statistics are only updated when a job terminates; they do not reflect the resources used by jobs that are currently running for the user account. Partial job statistics are not maintained for user accounts of jobs that are interrupted by a system reload. The account resource use statistics include counts of interactive terminal jobs (users signed on to the system), batch jobs, and print jobs (files printed by the system Spooler). When the job statistics are added to the account, the limit error flag is set if any of the limits are exceeded. 3.3.1.9.2. Account Resource Limits _______ ________ ______ If Job Accounting is 'ON', the account limits ae checked each SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg016 time the user attempts to sign on to the system, create a batch job, or submit a file to be printed by the system Spooler. If Job Accounting is 'OFF', this limit checking is not performed. If the 'limited' flag of the user account if 'OFF', the account is not limited and may proceed, regardless of the account limits. If the 'limited' flag of the user account is 'ON', the limits are checked. The limits are used to prevent a user from starting a job if the limits are exceeded. The account limits are not used to terminate a job once it has started. The account limits also prevent a user from starting a job if the job request is greater than the remaining account limits. The remaining account limits are the difference between the account statistics and the account limits. If the limit error flag is 'ON', the account limits have been exceeded, and the job is not accepted. If the limit error flag is 'OFF', the resource requests are compared to the remaining account limits. If any account limit is exceeded, the job request is not accepted. For print job requests for the system Spooler, the resource request is an estimated number of pages to be printed. For terminal sign on requests and batch job create requests, the resource requests are the group limits of the group that the job is starting on. To run Job Accounting by menu, select Job Utilities from the Main Utilities Menu and then select Job Accounting from the Job Manager Job Utilities Menu, or enter 'ACCOUNTS' without parameters in console mode. For further information on Job Accounting, see the HELP screens for ACCOUNTS and the BOSS/VS Utilities User _______ _________ ____ Guide, M 5102E. _____ 3.3.2. GETDEVINFO Utility __________ _______ The GETDEVINFO utility is a procedure callable through BASIC in the following format: CALL "GETDEVINFO", A$. It returns the device names and types on the system. For each device on the system, 10 bytes of information are returned. Bytes 1-5 contain the device name padded with trailing blanks. Byte 6 contains the shared memory controller number and the IMLC line number. Byte 7 is the device type code. Byte 8 is the device status code. Byte 9 contains the ISDC line number. Byte 10 is reserved and is always zero. 3.3.2.1. Shared Memory Controller ID Code (Byte 6) ______ ______ __________ __ ____ _____ __ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg017 Bit Meaning ___ _______ 0 Line number - A is 0 and B is 1 on IMLC 1-6 Shared memory controller number - range 0-63 7 Not used If the device is on an ISDC controller, the shared memory controller field is valid, and the line number is zero. If the device is neither an IMLC nor an ISDC, the entire SMC ID code (byte 6) is zero. GETDEVINFO Utility 3.3.2.2. Device Type Codes (Byte 7) ______ ____ _____ _____ __ Table 3-1 shows all the possible device codes available. An '*' by the code indicates that it is new for 8.6A/9.6A. Table 3-1. DEVICE TYPE CODES _____ ____ ______ ____ _____ Code Description ____ ___________ 00 No device 01 High speed VDT 02 DataWord II MDT in WP mode 03 DataWord II MDT in VDT emulation 04 Ghost terminal 05 7250 terminal 06 Transportable Batch Communications (TBC) 07 TBC Autodial unit 08 3270 running on IMLC 09 X.25 running on IMLC 0A Basic Four interface system serial printer 0B Async driver 0C Async modem driver 0D 7270 terminal w/o slave option 0E 4309 or 4312 (EVDT) terminal 10 Basic Four slave printer 11 Parallel matrix printer 12 Parallel band printer 13 MTR 1/2" reel-to-reel tape drive 14 MTS 1/2" streamer tape drive 15 4308 (ODT) terminal 16 4105 (S/10) terminal 17 SPEcial VDT device (4300) 18 Letter quality system serial printer 1A DMP serial system printer 1B DMP parallel printer 1C Industry standard slave printer 20 MCS 1/4" cartridge streamer tape drive 2D* 4310 (EDT) terminal 30* MAGNET socket 31* 4313 VDTB (intelligent) terminal 34 Available Hex codes not listed are unused or reserved for future devices. 3.3.2.2.1. Device Status Codes (Byte 8) ______ ______ _____ _____ __ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg018 In the device status field, each bit has one meaning. More than one bit may be set in this field. For each bit in the field that is set, that condition is true. GETDEVINFO Utility Bit Meaning (If bit is set) ___ _______ ___ ___ __ ____ 0 Escape entered on terminal device 1 Device is open or in use 2 Device is not configured 3 Printer is dedicated 4 Terminal has a slave printer 5-7 Not used 3.3.2.2.2. ISDC Line Number (Byte 9) ____ ____ ______ _____ __ The lower three bits of the byte contain the line number (0-7) of the device if the device resides on an ISDC. The 16-way ISDC is treated as two consecutively addressed 8-way ISDCs. On a 4-way ISDC (MCS), the lower 2 bits will be the line number, and bit 3 will be zero. for any other type of device, this field is zero. The other 5 bits are reserved for future expansion. 3.3.3. SECURITY MANAGER Utility ________ _______ _______ In the Security Manager Utility, the Operator Flag has been changed from one field to three fields. The three fields are now refered to as: 1) System Operator 2) Spooler Operator 3) Tape Operator The System Operator flag allows the user access to certain system programs that require the Operator flag to be set to TRUE in order to execute. These programs are: BULLETIN INSTALL.PARAMS TERM.CONFIG RESERVE DISCONNECT TRANSLATE CONFIG.MGR SAVERESTORE If the System Operator flag is TRUE, then the operator will have the Spooler Operator and the Tape Operator flags also set to TRUE. The Tape Operator and the Spooler Operator flags are a subset of the System Operator flag. The Spooler Operator flag allows the account access to privileged spooler functions and the Tape Operator flag allows the account access to system backup functions. 3.3.4. INTRODUCTION TO THE SPOOLER ____________ __ ___ _______ The BOSS/VS 8.6/9.6 Spooler gives the user much greater flexibility with expanded functionality, increased ability to control printing on system printers, and control of the execution of print jobs. The purpose of this section is to give an overview of the 8.6/9.6 Spooler. For those familiar SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg019 with the old Spooler, this section will explain terms which SPOOLER were associated with old Spooler, and guide you through new terms and use of the 8.6/9.6 Spooler. To bring the system printers into spooled mode, the following must be done: COPY .R6A39.SYS.START.CMD, which is provided on the release tape, to (system-default-family).SYSDATA.START.CMD. The previous Spooler's CLASS is now divided into a new CLASS and FORM. The new CLASS defines how to print the request (number of copies, starting and ending pages, automatic paging, etc.), while FORM specifies what sort of print medium to use (paper dimensions, VFU information, lines and characters per inch, etc.) If the system is being upgraded from an earlier MPx release, it will automatically convert the old CLASS definitions into their equivalent new CLASS and FORM definitions at the time of the first 8.6 Type I boot. The name of the new CLASS will be identical to the old CLASS and the new FORM will be called 'FORMx', where 'x' is the CLASS letter of the old definition. The following basic concepts need to be understood: o SPOOLER OPERATOR - A user whose account has been set up with the SPOOLER operator flag equal to TRUE by the Security Manager utility. The user need not have system operator status to have spooler operator status. The spooler operator has operator privileges within the spooler utilities. o SPOOLed MODE - Jobs are sent to the printer via the Spooler subsystem. o RESERVEd MODE - The printer is reserved by a process, and that process has complete control over that printer until either the process gives it back to the SPOOLer subsystem, or the process goes away. In the latter case the printer is given back to the Spooler subsystem. While in RESERVED mode, the Spooler subsystem does not have control of the printer, and spooling is off. The process that executed the RESERVE command may open the printer or may submit jobs with spooling off. (RESERVE is roughly equivalent to DEDICATE in the old Spooler). o DISCONNECTed MODE - The printer is disconnected from the SPOOLER subsystem but is not RESERVED by any process. Spooling is off. If the printer is IDLE, a process can open the printer and use it until the process 'closes' the printer. If the printer is PRINTING (busy) , any other process is denied access to the printer. Any process with spooler operator status can give a DISCONNECTed (spooling SPOOLER allowed) printer back to the SPOOLER subsystem. A user can submit a job to a disconnected printer that is idle with spooling off. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg020 o SUSPENDED - The printer is stopped from doing any work. It is not available for use. Jobs may be enqueued to the printer but will not print until printing is resumed. This mode is used as a software printer offline. The user can suspend printing to do printer maintenance, to modify the print queue, or modify print jobs within the queue. The Spooler utility is divided into five options: Printer Control, Job Control, Form Control, Class, and Spooler Status. The Printer Control utility provides the user with a way to control the printers on the system. The user can "SUSPEND" printing,"DISCONNECT" a device,"RESERVE" a device,"SPOOL" a device,"SETFORMs" on a device and display device status. The Job Control utility allows the user to SUBMIT, STOP, RESTART, MODIFY, CANCEL or display a print job. The SUBMIT parameters are as follows: CLASS NAME PRINTER NAME FORM NAME NUMBER OF COPIES STARTING PAGE ENDING PAGE DATE TO PRINT TIME TO PRINT PRIORITY DELETE DISK FILE LOAD FORMS REQUEST NOTIFY USER REQUEUE JOB FORMFEED AT START PRINT LINES PAGING GENERATED PAGE HEADINGS PAGE NUMBERS SEPARATOR PAGES RAW MODES SPOOLING ON HIGH BIT ON JOB ALIAS VERIFY PAUSE ON ERRORS OUTPUT DEVICE With 8.6/9.6 Spooler, the user has a much greater control over what happens to his print job. The user can control the disposition of a print job - when and where it prints. Form feed between print jobs and mnemonic interpretaion by the system is now optional. The user can be notified when a print job is done. The Form Control Utility gives the user the ability to control forms defined on the system. In Form Control you can create, modify, delete and display a form. In creating a form, you having the following options: Form Name - The name can be up six characters. SPOOLER Character per Line - The number of characters can be from 1 to 511 per line. Lines per Page - The lines per page is 1 to 255. Lines per Inch - The lines per inch can be 6 or 8. Channel Slew - The slew channels used are 2 through 8. Loadforms Message - The form mounting message can contain up SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg021 to 40 characters. Pitch - The pitch can be 10 or 16 characters per inch. Another option in the 8.6/9.6 Spooler is the Class Utility. In the Class Utility you have the following parameters: CLASS NAME: PRINTER NAME FORM NAME NUMBER OF COPIES PRIORITY STARTING PAGE ENDING PAGE DATE TO PRINT TIME TO PRINT DELETE DISK FILE LOAD FORMS REQUEST NOTIFY USER REQUEUE JOB FORMFEED AT START PRINT LINES PAGING GENERATED PAGE HEADINGS PAGE NUMBERS SEPARATOR PAGES RAW MODE HIGH BIT ON PRINTER DEF FILE JOB ALIAS SPOOL FILENAME DELETE DEFINITION As you can see, most of these parameters are the same as those in the submit utility. A class is assigned to a form and together they control a printing job. The last utility in the spooler is STATUS. In the Status utility the user has the following options: 1. Display Printer Status 2. Display Job Status 3. Display Form Status 4. Display Class Status All Spooler functions are accessible through the BASIC OPEN statement. This must be specified in the ATTR clause on the OPEN: OPEN(1,ATTR="KEYWORD=VALUE, KEYWORD=VALUE")"LP". If the user specifies a class name, the class defaults are read, and they will set any values that are not not SPOOLER specified. The keywords are: CLASS LOADFORMS PAGING PRIORITY FORM NUMBER COPIES SPOOLON HEADINGS START NOTIFY LINES END REQUEUE WAIT DATE FORMFEED SEPPAGES TIME RAWMODE PRINTDEF DELETE HIBIT ALIAS SPOOLNAME There are several Spooler information programs available from BASIC. These programs return information to a BASIC program in a set format. The Spooler information programs that are available are: GETFORMINFO, GETFORMS, GETCLASSINFO, GETCLASS, GETPRINTINFO, GETJOBINFO, and GETJOBS. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg022 For example: 10 A$="FORMA" 20 CALL "GETFORMS",A$,B$ B$ will be returned with the definition for the form specified in A$. The information format returned will be in ASCII. The character fields are left justified and filled out with nulls. Numeric fields are right justified and filled with zeros. For more detailed information on the Spooler, refer to the BOSS/VS User Guide, M 5098F, and the Business BASIC 86 _______ ____ _____ ________ _____ __ Reference Manual, M 6262. _________ ______ 3.4. CLI BATCH SUBSYSTEM ___ _____ _________ 3.4.1. Purpose _______ The batch facility provides the user with the means to run tasks in background mode, that is, without a terminal attached to the process. 3.4.2. Introduction ____________ It is assumed that the reader of this document is familiar with the Job Manager on the BOSS/VS. The Job Manager is described in the Job Manager Section of this document. It is through the Job Manager that the operator creates, deletes, and modifies a job in a batch group. The Job Manager provides utilities to create and modify groups and jobs, and set access privileges. It is with these utilities that batch groups are created. Once the batch group is created, batch jobs may be submitted to them. CLI Batch Subsystem The system provides standard input and output ports. These ports are used by the utilities for reading input and writing output to the terminals. When a terminal starts up, the ports are both open to the user's terminal. The input port is the port all utilities, programs, and CLI (Command Language Interpreter) use to read input from the user. This may be responses to prompts for data, or 'CR' to continue. The output port is the port the utilities, programs and CLI use to write the output. This includes data entry screens, display screens, and messages. All utilities use these ports and they do not modify them during execution. When a batch job (background task) starts up, the input and output ports are open to files that the user specifies. The utility or program may then read input from a user specified file and write output to another user specified file. This way, the utility or program does not require any changes to run in Batch mode. The user may wish to not specify these files and then the input and output ports would be opened by the batch executive. All attempts to read input by a utility SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg023 or program will get an error (End of file) and all outputs are sent to a default file. The command language prompts the user for input (commands and prompts) using the input port. All messages and command echoing are sent out using the output port. When the command language encounters a command procedure file, it must begin to read commands from there and not from the terminal. To do this, CLI uses a local port to read the command file. The input port is not used or modified. This is done so that command input and data input is kept separate. If the user has a program that reads input, the program name would be in the command procedure file and the input to read would be in a user specified input file. The input data is not stored in the command procedure file. 3.4.3. Creating a BATCH Job ________ _ _____ ___ Once a Batch Group has been created by the Job Manager, a user can create jobs on that group. To create a batch job the user must use the Job.Create command. Job.Create , {,JOBOUTPUT=} {,JOBOUTACTION=} {,JOBINPUT=} {,ACCOUNT=} The parameters listed here are only a partial list of parameters available for this command. Please see the Job Manager Section of this announcement for more information on the Job Manager Utilities. CLI Batch Subsystem The is required. This is the command to execute in batch. It may be the name of a program, a Command Language command, the name of a command procedure, or any other valid command or program name. If it is a command procedure name or program name, the file name, if not fully qualified already, will be fully qualified when it comes time to execute the command. So, you must remember that the prefix will be the prefix set up from the userid specified account. Also, remember if a command is specified that is from a special command definition file, that command definition file must be set up first. (DEFAULT command.) The initail command should be enclosed in single quotes if it is to include spaces or punctuation. Multiple CLI commands are separated by semicolons. For example, the following command could be used to set the job prefix and then run a program. JOB.CREATE 'PREFIX .USER1.;userprog parm1 parm2', usergroup This command creates a job on the group 'usergroup', under the current user account, that will run the CLI command: PREFIX .USER1.;userprog parm1 parm2 When the job executes, this initial command will first set the SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg024 prefix of the job to '.USER1.', then run the BASIC program 'userprog', passing in the two param- eters 'parm1', and 'parm2'. This assumes that the BASIC program expects two parameters (via the BASIC ENTER statement). The is also required. This is the name of the batch job group to use. The file is the file where the output is to be written. The output port will be opened to this file. This is the file that would get all output that would normally go to the VDT. If this file is not specified, a new file will be created for the user with the name JOBNAME.OUT under the user's primary prefix. The JOBNAME is generated by the Job Manager and is a unique name for this job. The is the action on the user specified output file. The outaction may be 'No' - do not delete the file if it exists (generate an error if it exists), 'Delete'- delete the file if it exists, 'Append' - append to the file if it exists. Note: if 'Append' is specified, the file must be a serial file. The file is where the program or utility can go to get input whenever a read is encountered. The input port is opened to this file and becomes the FID(0) for the batch job. CLI Batch Subsystem This file must contain all inputs required by the batch job. If no input file is specified, the batch job creates a temporary null file. The file will have no records so that any reads that are attempted will get an End of File error. This file will then be deleted when the batch job is complete. NOTE: If the user specifies names for the input or output file that are not fully specified, the names will be fully specified when the batch job is run. This is with the prefix set from the userid account specified. The is the account name associated with the batch job. If none is specified the account of the user who is submitting the job is used. A user must be a user level 3 to start anyone elses batch jobs. A user with a level of 2 can start any batch job for anyone with the same major account, and a user level 1 can only start his own batch jobs. A user with a level of 0 cannot run batch jobs. Note: To start a job running on another terminal, the user must use the START command. To start a batch job the JOB.CREATE command is used. 3.4.4. INPUT Handling _____ ________ The input file is a file that contains all of the users' data input. This is different from the CLI Command input. The input file contains one record for each read that will occur. This way a user can write an application program that reads from the input port and as long as the data is available in the input file, the application will run in Batch mode. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg025 3.4.5. CLI in BATCH ___ __ _____ When CLI is run in Batch Mode, the user is not prompted for 'CR' to Continue: at errors. Also, the user is not prompted for more information about an error. The entire error is written to the output file. Other than these minor changes, CLI runs the same as in console mode. Any command procedure that is run in Batch will run the same in console mode. When a $ACCEPT is done in Batch mode the Command Language reads from the Input file instead of from the terminal. Note: The DISPLAY command allows the user to write mnemonics to the output file (VDT in console mode). This will still be allowed in Batch mode. The user must be aware that these mnemonics may cause the output file to not be readable by the editor. Also, if the output is sent to the printer the mnemonics may not be recognized by certain printers. CLI Batch Subsystem 3.4.6. Utilities in BATCH _________ __ _____ The utilities will run in Batch mode and send the output to the output file. Screens and prompts are not written to the file. If the user wants the complete output, output can be sent to a file using the OUTPUT parameter for the particular utility. In Batch mode the user will not be prompted with 'CR' to Continue:. If a utility does not have an OUTPUT parameter, the utility will output to the output file specified in the Job.Create command. Utilities will not be allowed to run in interactive mode as a batch job. The following list indicates the utilities that are available in batch mode. After each new feature name appears a code showing the extent that the command, function or program supports with this feature. Codes: YES - the feature is fully supported by the Utility or Command. NO - the feature is NOT supported by the Utility or Command. N/A - the Utility or Command is unaffected by the new feature. YES indicates that the utility operates correctly in non-interactive or 'batch' mode; with disk files connected to the INPUT and OUTPUT ports. All functions work in BATCH mode. An '*' following a YES means that all options of that menu utility are available in BATCH mode. An '*' following a NO means that none of the options are available in BATCH mode. CLI Batch Subsystem Table 3-2. Utilities and Commands in BATCH _____ ____ _________ ___ ________ __ _____ Utility Name Batch Utility Name Batch ------------------------------ ------------------------------ ACCOUNT :YES ACCOUNTS :YES * BAND.TABLE :NO BBXREF :YES BULLETIN :NO BULLETIN.UPDATE :YES CMDCONVERT :NO * CMDVERSION :YES SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg026 COMPACT :YES COMPARE :YES CONFIG.MGR :NO CONVERT :YES CONVERTSP :YES COPY :YES CREATE :YES DATE :YES DEFAULT :YES DELETE :YES DEVICES :NO DIR :YES DISCONNECT :YES DISKANALYZER :NO DISPLAY :YES DOWN.LOAD :NO DUMPTOFILE :NO EDIT :NO EDIT.RECOVER :NO ERR :NO ERRNUM :YES ERRORLOG :YES EXAMINE :NO EXIT :YES EXTTAPE :NO FAMILY :NO * FILESIZE :NO FILESYSORIDE :YES FORM :YES * GENSSN :NO GETVERSION :YES GROUP :YES * GSR :YES HELLO :NO HELP :YES HERMIT :NO IF :YES IMAGER :NO INSTALL.PARAMS :NO * JOB :YES * LEVEL :YES LOG :YES LOGEND :YES MAGNET :NO MAJOR :YES MCSI :NO MINOR :YES NETCONFIG :NO * NETLOG :NO * NETSTATUS :NO * NFSCONVERT :NO OLDDIR :NO OLDTAPE :NO OPERATOR :YES OSINFO :NO PHOTO :NO PPARMS :YES * PPOP :YES PPUSH :YES PREFIX :YES PROCESSID :YES QUIETOFF :YES QUIETON :YES RECONSTRUCT :NO RELEASE :YES REM :YES RENAME :YES RENUMBER :YES RESERVED :YES RESET :YES SAVERESTORE :NO SCANERRORS :NO SDFAMILY :YES SECURITY :YES * SETFORM :YES SKEY :NO * SORT :YES SPDEV :NO SPDEV.DISPLAY :YES SPJOB :YES * SPLOPR :YES SPOOLED :YES SPOOLER :NO SPSTATUS :NO START :YES SUBMIT :YES SUSPEND :YES SYSFAMILY :YES CLI Batch Subsystem SYSINFO :NO SYSPREFIX :YES TAPEOPR :YES TASKS :NO TERM.CONFIG :NO TERM.ERRORS :YES * TERM.TABLE :NO TIME :YES UDFAMILY :YES UPDATE :YES UPDATE.LD :NO UPDATE.OS :NO UPDATE.WCS :NO UPDATE.RIGHTS :YES UTILITY :NO WHO :YES 3.5. NEW LOAD SCREEN ___ ____ ______ The BOSS/VS "Load Screen" has been changed to display additional information. Below is a sample display of the new load screen. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg027 --------------------------------------------------------------------- Load PROM Version: 2.0.0.5 SYSTEM SERIAL NUMBER : 810-66666 Load Drive 1 Unit 37 Sector 0 SERIAL NUMBER CREATOR: TB0-30026 WCS 0 Version: 5.3.9 CONFIGURATION CREATOR: TB0-30026 OS 0 Version: 6.1.30.1 LOAD TYPE OPTIONS: CPUs On-Line: 0 1 Memory (Mb) : 2.0 1) COMMENCE NORMAL EXECUTION Disk Drives : 2 2) STANDALONE FILE FUNCTIONS Tape Drives : 1 3) SPECIAL FUNCTIONS Printers : 1 HVDTs : 0 ENTER OPTION NUMBER: IMLCs : 1 Serial Ports: 2 Date Format MM/DD/YY BMTCs : 0/0 LAN Cntrlrs : 0 SYSTEM PREFIX: (DISK).R6A30.SYS.,.R6A30.INST. System Default Family: DISK File System Write Thru: TRUE User Default Family : DISK Per-File Write Through: FALSE Insatallation Name : HQA File System Security : FALSE --------------------------------------------------------------------- The field screen positions and a description for each field are given below. Field (0,0) : Load PROM Version #.#.#.# - This field contains the four-tuple version number assigned to the load PROM's current revision. Field (0,1) : Load Drive # Unit # Sector # - This field contains the relative drive index of the load disk, its unit number, and the sector from which the load directory was read. Field (0,2) : WCS # Version #.#.# - This field contains the slot New Load Screen number of the Writable Control Store (WCS) contents and its version number three-tuple. Field (0,3) : OS # Version #.#.#.# - This field contains the BOSS/VS Operating System load slot number and the four-tuple version number assigned thereto. Field (40,0) : SYSTEM SERIAL NUMBER : ###-##### - This field contains the current system serial number assigned to the load machine. Field (40,1) : SERIAL NUMBER CREATOR: ###-##### - This field contains the system serial number of the BOSS/VS system which generated or authorized the generation of the current system's SSN. Field (40,2) : CONFIGURATION CREATOR: ###-##### - This field contains the system serial number of the BOSS/VS system which generated the current system's system configuration record. Field (10,5) : CPU Id #s: - This field displays the identification numbers of all of the machine CPUs which are currently on-line. Note that this display occurs before the system configuration of the CPUs takes place. DEVICES should be used to display on-line CPUs once the system has been initialized. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg028 Field (10,6) : Memory (Mb) : - This field shows the number of main memory megabytes, rounded to the nearest .01Mb. Note that this reflect the configuration of main memory after the system configuration has taken effect. Field (10,7) : Disk Drives: - This field displays the number of disk drives recognized by the system after the enforcement of the system configuration record. Field (10,8) : Tape Drives: - This field displays the number of tape drives connected to the IO bus on the 7000, 7100, and 8000. It does not include tape drives attached to the BMTC. Field (10,9) : Printers : - This field displays the number of parallel printers recognized by the system after the enforcement of the system configuration record. Field (10,10): HVDTs: - This field displays the number of High Speed Video Display Terminals recognized by the system. Field (10,11): IMLCs : - This field displays the number of Intelligent Multi-line Controllers (WAN/X.25, DWII, TBC, SNA/3270) recognized by the system. Field (10,12): Serial Ports : - This field displays the total number of serial ports on all 4-way, 8-way and 16-way Intelligent Serial Device Controllers that are recognized by the system. Field (10,13): BMTCs : - This field displays the number of tape drives which are attached to any BMTCs recognized by the system. This is displayed as two numbers in foreground mode separated by a virjule ("/") in background mode; the first number is the number of New Load Screen 1/2" tape drives attached to all BMTCs in the system and the second number gives the number of 1/4" cartridge drives attached to BMTCs in the system. Field (10,14): LAN Cntrlrs : - This field displays the number of LAN Controllers recognized by the system. Field (40,4), (42,6),(42,7), (42,8) and (40,10): These are the option prompts which require operator input to determine which type of load is to be performed. Field (40,12): Date Format: - This field displays the currently defined system format for the date using standard abbreviations for the month, day and year parts of the date. Field (40,13) and (40,14) : - These are the date and time input prompts. These are the same as previous load screen options display except for their position on the screen and their new availability in Type 2 and 3 Loads. Field (0,16) : SYSTEM PREFIX : - This field displays the currently set system prefix list. Field (0,18) : System Default Family : - This field displays the name of the currently defined system default family. Field (0,19) : User Default Family: - This field displays the name of the currently defined user default family. Field (0,20) : Installation Name : - This field displays the name of the system's default installation name. Field (40,18): File System Write Thru: - This field displays the current setting of the BOSS/VS File System's system-wide file write-through option. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg029 Field (40,19): Per-File Write Through: - This field displays the current setting of the BOSS/VS File System's per-file basis write-through option. Field (40,20): File System Security : - This field displays the current setting of the BOSS/VS File System security-enabled switch. Field (10,22): INITIALIZING : - This field displays the name of the current stage of BOSS/VS Initialization Phase II. During the input of the date and time fields, this field is blank and is used for error message displays related to date/time input errors. 3.6. COMMUNICATIONS ______________ 3.6.1. 19.2K BPS SUPPORT _____ ___ _______ 3.6.1.1. Introduction ____________ Asynchronous communications has been enhanced with the 9.6A/8.6A release to support 19,200 bits/sec./line data rates on the 8way and 16way ISDC controllers. "LINE SPEED" may be 19.2K BPS set to 19,200 in the ISDC UPDATE OPTION of the Terminal Configuration Utility (!TERM.CONFIG). The DT-4313 terminal wil display data a nearly twice the speed previously possible when configured at 19,200 bits/sec. This feature is intended for use in an interactive environment and not for the bulk transfer of data asynchronously. 3.6.1.2. Notes _____ In order to make the best use of this feature and optimize overall aysnchronous throughput the user should spread his 19.2K bps devices over various controllers, rather than concentrating them on specific ISDC's. When multiple 19,200 bps terminals on the same 8way or 16way simultaneously update their screens, some drop in screen display speed may be noted due to the overall data throughput capacity of the 8way/16way being reached. However, experience so far indicates that in most applications, customers will rarely notice any speed reduction. The following guidelines should aid the user in the implementation of this feature: 1) 4-way: - 19.2K bps is NOT supported on the 4way. 2) 8-way: - Four 19.2K terminals with four 9.6K or below devices would be optimal. The concentration of a greater number of 19.2K bps terminals on an 8-way should be done incrementally. The total number of 19.2K bps terminals that can supported on an individiual ISDC will be highly dependent on the specific applications being run and the level of concurrent terminal use. - No block input or file transfer 19.2K bps support. 3) 16-way:- Ports 0-7 same guidelines as an 8-way. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg030 - Ports 8-15 same guidelines as an 8-way. By exceeding the above guidelines the following consequences may occur: 1) Terminal throughput on an ISDC exceeding the above limitations may actually decline and/or give the appearance of random hesitation of terminal response. 2) Block I/O or file transfer at 19.2K bps can produce UART errors or buffer overflows (eg. error 5's and error 34's). 3.6.2. ENHANCED SERIAL PORT AVAILABILITY AFTER BOOT ________ ______ ____ ____________ _____ ____ Beginning with the 9.6A/8.6A release, there is now improved serial port availability after booting the system into a type-1 load. On levels prior to 9/8.6, to have a serial port "available" in a type-1 load it was neccessary that at the time of booting that there existed an ISDC (4-way, 8-way, 16-way) controller with the correct address, that the port be defined in TERM.CONFIG, and that there be a serial cable attached to the controller's port to give "cable presence" at boot. This "availability" is seen by running "SYSINFO", "DEVICES", or by attempting an OPEN in BASIC to that port. On 9.6A/8.6A it is NOT required to have "cable presence" to have the port available at the time of boot. If there is an ISDC controller with the correct address and a corresponding port definition in TERM.CONFIG at the time of boot, then the port is available. These ports will be "seen" in "SYSINFO" as "Available" and will be included in the totals found in running "DEVICES". This enhancement results in a change in BASIC. Since "cable presence" at boot is no longer required to make a port available, a port can be OPENed in BASIC without a cable being attached. On levels prior to 9/8.6A, if a cable was not present a boot, then an error 12 would be returned on an attempt to OPEN the port in BASIC. This is no longer the case. 3.6.3. MAGNET ______ 3.6.3.1. OVERVIEW ________ MAGNET is the MAI Basic Four General Purpose Network which __ _ ___ allows the sharing of files between multiple MPx systems. Users on one MPx system can access files on another MPx system in a real-time environment, using standard BASIC input/output directives, such as READ's and WRITE's. Access of another MPx system's database can occur whether the system is in the same room or across continents. The distance between the MPx systems determines the best media to use to connect the systems. Local Area Network (LAN) connections would be most efficient for systems which are within 4000 feet of each other. Systems which are further than 4000 feet apart will be SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg031 connected via a Wide Area Network (WAN). On 8.6A, the WAN media is the internationally recognized X.25 protocol. 3.6.3.2. FEATURES ________ MAGNET is ideal for a user who has outgrown his single MPx system and wishes to add additional MPx systems, or for a user who has multiple sites with independent processing needs and yet requires the ability to share common information stored on these different MPx systems. Previous to MAGNET, the most common method of sharing information between MAI Basic Four systems was to transmit the whole file to the local system, update the information, then transmit the updated file back. With the introduction of MAGNET, this is no longer necessary. MAGNET allows application programs running on a local system MAGNET to access any data file, given the proper security, on any other MPx connected to the user's MAGNET network. This is accomplished with minimal or no changes to the user's application that was originally written to access files on a single system. Features of MAGNET include: o MAGNET is integrated into the Business File System and BASIC language and therefore transparent to the user. o Minimal or no application code changes are required for existing programs when used in a MAGNET network. o MAGNET supports remote file access on a record interactive basis. o MAGNET supports of a subset of MPx commands and utilities, such as COPY, DIR. A list of these commands is in section 3.3. o MAGNET observes system and file security rules of a single system. o MAGNET LAN provides access between a maximum of 63 MPx systems on a single subnetwork. o MAGNET WAN and internetworking provide access to a maximum of 100 subnetworks. o MAGNET WAN using X.25 provides access to MPx's on a worldwide scale through Public Packet Data Networks (PDN) which have certified Basic Four's X.25 product. In addition, MAGNET WAN is supported on private packet switching networks and point to point configurations between two MPx systems. o MAGNET internetworking allows LAN and WAN connections on a single MAGNET network. o MAGNET Network Management Facilities (NMF) provides utilities to configure a network, log events, and check media status. o MAGNET EZCONFIG provides a very simple network configuration utility typical for "simple" networks. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg032 o Network errors, such as link failures, are reported by the same BASIC error numbers as single-system errors with similiar programmed recovery. 3.6.3.3. LIMITATIONS ___________ MAGNET on 8.6A is restricted for use between MPx systems only. Although MAGNET on an MPx can co-exist on the same LAN or WAN network as a 2000 MAGNET network, interfacing between the two MAGNET systems will not be possible until a future release. Although the MAGNET network is intended to be transparent to the user, a slight response delay is unavoidable. On MPx systems connected via a LAN, this response delay is approximately 30 ms per BASIC language Read or Write statement. When connected via a WAN, the response delay is approximately 1-2 seconds. Timing will vary according to the system type (i.e. MPx 80x0, 90x0, or 95x0), baud rate, X.25 parameters, network congestion and system load. MAGNET on 8.6A supports access to remote data files (except for Multi-Key files) only. Access of remote devices such as printers and tape drives and executing of remote programs are not supported on 8.6A. Care should be taken regarding the number of remote tasks per system (the number or remote tasks should not exceed 20% of allowable tasks/system), the distribution of files within the network, and the frequency of remote accesses to those files. Failure to adopt proper network planning could result in performance degradation of given applications on the network. The 8.6A release of MAGNET will support a maximum of 100 subnetworks. Subnetworks are either single X.25 systems or a number of systems connected by LAN with one or more systems using X.25 to connect to the rest of the MAGNET network. Any task will have a maximum of 10 remote systems it may access simultaneously. This may be further limited by the X.25 parameters specified for the system (LCN's) and by the remote activity of other tasks on the system. 3.6.3.4. MEDIA SELECTION _____ _________ MAGNET will support either a LAN or a WAN media on an MPx system. Which media to use will depend on the location of the MPx systems in the MAGNET network. 3.6.3.4.1. MAGNET LAN ______ ___ MPx systems which are located within a single building or a group of buildings will benefit from using the LAN media. MAGNET LAN provides an inexpensive, yet highly reliable high speed connection between up to 63 MPx systems which are within 4000' of each other. The connection is made through a single twisted pair wire called a trunk cable, with a data transfer SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg033 rate of 1 Megabits per second. A LAN repeater is required to amplify and carry network signals when the trunk cable is greater than 1000' or when there are more than 32 MPx systems on a 1000' trunk segment. MAGNET LAN on the MPx uses the same OMNINET* protocol as on the 2000 MAGNET LAN product. Except MAGNET for the LAN controller board, LAN hardware from the 2000 system may be used on the MPx. * OMNINET is a registered mark of Corvus Systems Incorporated and is used under license from that company. 3.6.3.4.2. MAGNET WAN ______ ___ MAGNET WAN uses the X.25 protocol to connect MPx systems where LAN is not appropriate due to distance or cabling restrictions. X.25 is a full duplex synchronous protocol which is gaining popularity around the world as a "standard" interface for computers and networks. There are many options available for X.25 connections. MAGNET WAN in general supports the following options: o X.21 bis physical interface with standard IMLC and cable o X.21 physical interface with standard IMLC and modified cable o HDLC link level protocol o LAPB link level procedure o Switched virtual circuits o 1 - 8 logical channels (8 recommended) o Packet size configurable (128/256) o Link level window configurable (default=7) o Packet level window configurable (default=2) 3.6.3.4.2.1. MAGNET WAN Connection Options ______ ___ __________ _______ There are three MAGNET WAN connections available: Public Packet Data Network (Public PDN) , Private Packet Data Network (Private PDN), and Point to Point. 3.6.3.4.2.1.1. Public Packet Data Network ______ ______ ____ _______ Access to Public PDN's are available in most technically advanced countries at reasonable rates. A connection to a Public PDN will allow an MPx to communicate to any number of MPx's connected to the same PDN. In addition, many Public PDN's offer interconnections to other Public PDN's domestically and internationally. Certification of MAI's X.25 product is required before a MAGNET WAN connection will be allowed on a Public PDN. Currently MAI's X.25 product has been certified with the following Public PDN's: United States TELENET TYMNET UNINET ACCUNET Australia AUSPAC SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg034 Belgium DCS MAGNET Canada DATAPAC Chile TELENET France TRANSPAC Netherlands DATANET-1 Norway TELEVERKET Sweden DATAPAK Switzerland TELEPAC United Kingdom PSS West Germany DATEX-P A MAGNET WAN network requiring international connections will be most efficient in a Public Packet Data Network environment. 3.6.3.4.2.1.2. Private Packet Data Network _______ ______ ____ _______ When security and control are issues to consider, a Private PDN may be better suited than a Public PDN. Private PDN's also require connections from each MPx, but instead of to a Public PDN, the connection will be to a "black box" which provides data packet delivery and supports the necessary X.25 interfaces. The "black box", commonly referred to as an X.25 switch, will allow multiple MPX systems to be connected to the switch via private or leased lines and synchronous modems. Besides providing a Private PDN, the X.25 switch can act as a line sharing device. One port of the X.25 switch can be used to interface to a Public PDN. This configuration will then allow all MPx systems connected to the X.25 switch to have access to the Public PDN through the single port, at a fraction of the cost of using a Public PDN port per system. 3.6.3.4.2.1.3. Basic Four Point to Point _____ ____ _____ __ _____ When only two MPx systems are in a MAGNET WAN network, a point to point configuration will eliminate Public PDN or Private PDN costs. This configuration is also somewhat faster than a PDN. A point to point network consists of two MPx systems connected via a leased or private line and synchronous full duplex modems. One MPx will be configured via the MAGNET configuration utilities to be a "DCE" while the other will be configured as a "DTE". By configuring one MPx as a "DCE", that MPx will emulate a PDN and interface properly to the "DTE" MPx. 3.6.3.5. REQUIREMENTS ____________ 3.6.3.5.1. HARDWARE REQUIREMENTS ________ ____________ MAGNET 3.6.3.5.1.1. LAN Hardware ___ ________ Hardware requirements for each MPx requiring a LAN connection SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg035 are as follows: LAN Controller Board LAN Trunk Cable - up to 4000' of twisted pair wire which connects the MPx systems in a MAGNET network LAN Drop Cable - 15' cable which connects the LAN controller to the LAN trunk cable LAN Tap Box - a plastic box containing screws to connect the wires from the drop cable to the trunk cable LAN Repeater Box - a box requiring a grounded power outlet to amplify signals over the trunk cable when distances between systems exceed 1000' 3.6.3.5.1.2. WAN Hardware ___ ________ Hardware requirements for each MPx system requiring a MAGNET WAN (X.25) connection are as follows: IMLC - a maximum of 4 IMLC's are allowed on the MPx. For maximum performance, when line speeds greater than 4800 BPS are used, an IMLC with X.25 configured on port A and nothing on port B is recommended The maximum line speed the IMLC supports is 19.2K BPS. IMLC to Modem Cable - XCOM cable connecting the IMLC port configured to run X.25 to a synchronous full duplex modem Synchronous Modem - modem which is compatible to the PDN's modem. In a point to point MAGNET WAN connection, or a private data network connection, each MPx and each X.25 switch port must be equipped with compatible modems. Dedicated Phone Line - a leased or private line to the PDN, private data network switch, or to another MPx system in a point to point connection. X.25 Switch - A "black box" providing data packet routing and X.25 interfaces, used in Private PDN environments. Basic Four has tested the Dynapac X.25 switch. 3.6.3.5.2. SOFTWARE ________ The use of MAGNET is controlled by the system Configuration Record. Either or both of the following options must be configured for a successful MAGNET connection in the MAGNET CONFIG.MGR utility. 3.6.3.5.2.1. LAN Software ___ ________ disk space (approx) MAGNET 115 sectors NETWORK MANAGEMENT FACILITIES 570 sectors* SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg036 LAN 23 sectors 3.6.3.5.2.2. WAN Software ___ ________ disk space (approx) MAGNET 115 sectors NETWORK MANAGEMENT FACILITIES 570 sectors* X.25 (# LINES=2 per IMLC port) 58 sectors * an additional 493 sectors are required if eventlog recording is activated 3.6.3.6. INSTALLATION ____________ 3.6.3.6.1. HARDWARE INSTALLATION ________ ____________ A. Assign one person as the Network Manager. This person will plan the installation and coordinate all hardware and software installation. He will also assign and keep track of system (aka station) and media addresses and ensure that the MPx systems in the network are properly configured, as modifications and upgrades to the network are required. This individual may also monitor the status of network hardware and phone lines and coordinate teh solutions to problems. B. Plan the physical layout of the MAGNET network. A map must be drawn denoting the location, system serial number, system name (maximum of eight characters), station address, MMC address of the IMLC and/or LAN controller. The map should include the media (LAN or X.25) to use to access all systems on the MAGNET network. Denote on the map all subnetworks on the MAGNET network. The subnetworks are each group of systems connected on a LAN and each single system with an X.25 access to the network. Assign to each subnetwork a unique identifying number in the range 1 - 32767. Ensuring that the network map is as complete as possible will enable the MAGNET soft ware configuration to be completed smoothly. C. On a LAN subnetwork, each station must be assigned a unique station address, between 01 and 63. The station address is assigned on the LAN controller. In addition to the station address, the LAN controller must be set for an MMC number. The switch settings for both the MMC MAGNET and address settings are documented in section 3.6.3.11 titled "LAN CONTROLLER". D. Have a service representative install the physical components of the subnetwork. This will include hardware for each system on a LAN or a single system with an X.25 connection. 3.6.3.6.1.1. LAN Subnetwork ___ __________ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg037 Each MPx on a LAN subnetwork will have a LAN controller installed. Note the switch settings for the MMC ad dress and the station address before installing the board. These addresses are required during MAGNET configuration. The 15' drop cable has a connector on one end which fits into the connector on the LAN controller. The opposite end of the 15' drop cable is a bare wire with a black and red wire exposed. The Tap Box is used to connect the black and red wires of the drop cable to the black and red wires of the trunk cable. Any trunk segment over 1000' or any segment which has more than 32 systems connected to it requires a repeater box. Note that the repeater box requires a power outlet. Each end of the trunk cable must be terminated with a single 100 ohm resister in the terminating Tap Boxes. 3.6.3.6.1.2. WAN Subnetwork ___ __________ An IMLC is required on any MPx which will be using X.25 to communicate on the MAGNET network. The IMLC must be strapped for XCOM/RS-232 (or X.21 - available in Europe) on either port, A or B, which will be configured to run X.25. Note the MMC number for the IMLC as it will be required when configuring the MAGNET network. An IMLC to modem cable must be connected from the proper IMLC port to a full duplex synchronous modem. IMLC switch settings for the MMC and XCOM/RS-232C settings for IMLC part number 903381 are documented in the service manual M8101. IMLC switch settings for part number 903534-001 are documented in Field Bulletin 149A or Mini-Systems Alert 461A. 3.6.3.6.2. SOFTWARE INSTALLATION ________ ____________ A. Install the 8.6A operating system, following the instructions in section 1 of this Software Announcement. B. Verify by running !CONFIG.MGR that MAGNET, Network Management Facilities, and the appropriate media (LAN or X.25) for this system are allowed in the configuration record. C. Execute !TERM.CONFIG to configure the IMLC port(s) for MAGNET X.25. D. Execute !DEVICES to verify that the LAN and/or IMLC controllers are recognized by the operating system. E. Verify that the startup command file contains the MAGNET startup command, MAGNET.STARTUP. This will ensure that MAGNET is started at boot time. Refer to section 1.6, System Startup, for details. F. At this point, the MAGNET network is ready to be configured. 3.6.3.7. CONFIGURATION _____________ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg038 There are two configuration utilities available to configure an MPx in a MAGNET network. Networks which use only one media type, either LAN or X.25 but not a combination of both, are called "simple" networks. Simple network configurations are ac- complished through a configuration utility called EZCONFIG. If the MAGNET network is a LAN/WAN combination, or modifica- tions to the default parameters of X.25 must be made, then the Network Management Facilities utility must be used to configure the network. Network configurations must always start with a complete network map. 3.6.3.7.1. EZCONFIG ________ Networks configured using EZCONFIG are limited to those which utilize a single media, either LAN or X.25. EZCONFIG is run on one MPx to create a global configuration file which des- cribes the MAGNET network layout. This configuration file is then moved to all other MPx systems on the network and installed using the installation utility, EZINSTALL. Control of the configuration process can be limited to one location, thus eliminating the need for a network manager at each MPx location. A. Have a copy of the network map available. This map should designate the location, system serial number, system name, and network address (X.25) or station address (LAN) of each MPx in the MAGNET network. B. Execute the EZCONFIG utility by typing !EZCONFIG. C. Specify a file name for the configuration. D. Enter the desired network communications media - LAN, X.25 Network, or X.25 Direct (Point to Point). MAGNET E. Enter the desired access security for MAGNET users. The security can be by user name, requesting system name, or none. Access security by "user name" means that the remote user who logs on to this local system will be assigned the same log on name that he used on the remote system. If "requesting system name" is selected, the remote user will be logged under an account "REMOTE.station name". If "none" is selected, there will be no remote access allowed on the local files. "None" can also be selected if the security access is complicated enough that it must be customized later through the Network Management Facilities utilities. F. Once the security prompts are input, the network definition screen displays with options to add, delete, modify stations, delete configuration, and modify access security. G. On a new configuration, select the Add Stations option. Input the station name, system serial number, and network address of each MPx on the MAGNET simple network. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg039 H. Once all MPx systems in the MAGNET network have been defined, exit the utility by pressing "CR". A message will display informing the operator that the file ().SYSDATA.EZCONFIG.name must be moved to each configured MPx in the network and installed by running EZINSTALL. A "CR" at this point will allow the operator to either save the configuration or exit the utility. I. The configuration file must be moved to each system on the network by existing communications media or by tape. J. !EZINSTALL must be executed on every MPx which has a copy of the EZCONFIG file. This procedure will install the proper network configuration parameters on the system. K. A "?" followed by a "CR" at any prompt in the EZCONFIG utility will provide a help text. 3.6.3.7.2. NETWORK MANAGEMENT FACILITIES _______ __________ __________ The Network Management Facilities (NMF) are used to configure more complex MAGNET networks which utilize a combination LAN/ WAN media, require customized user access security, or require modifications to the default X.25 parameters. A. Have available the MAGNET network map which was drawn by the network manager denoting location, system serial number, station name, station address, MMC addresses of the LAN and IMLC controllers, and the media used by each system to communicate within the network. Specify each MAGNET subnetwork in the network and assign a unique subnetwork number. B. To enter the NMF utilities, type !MAGNET. Three options will display on the screen; Network Configuration, Network Status, and Network Event Log. C. Select option 1, Network Configuration. This option will allow the network manager to define to the MAGNET software, the topology and routing for each station in the network. Since a correctly configured network is essential for a successful MAGNET connection, the steps involved in this option must be carefully followed. Refer to the network map to enter the network parameters. D. Select "Home Station Definition" to enter the information pertinent to the local system. The utility will prompt the network manager for: o Station Name - a descriptive name of the MPx. Up to a maximum of 8 characters are allowed. When this name is modified, the utility will change the installation name of the MPx. o Station Address - the address assigned to this MPx on the LAN controller board. If this MPx has only an X.25 media, the station address should be set to "1". SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg040 o System Serial Number - the system serial number of the MPx. o Subnetwork Number - A unique number from 1 to 32767 assigned to a group of stations on a LAN and to a single station with only X.25. o Subnetwork Description - a comment field for a general description of the subnetwork. Once the entries are specified by the network manager as being correct, the next screen will display, requesting media information. Beginning with media number 1, the network manager must specify any LAN and/or WAN X.25 media used on this MPx. Included in this option are prompts requesting the MMC number of the LAN and IMLC controllers, the subnetwork number, the station number, and media parameters, such as X.25 subscription options obtained through the PDN. E. Option 3, Station Configuration, must be selected now if there are any other stations in the same subnetwork as the home station. For each station which is added, the utility prompts for station name, subnetwork number, MAGNET station address, and system serial number. F. Once the home subnetwork has been configured, select option 2, Subnetwork Configuration. Enter all other subnetworks in the MAGNET network the home station will be communicating to. Each subnetwork definition requires that a "gateway" station for the local subnetwork be defined. The gateway station is the station on the local subnetwork which will route the data through its X.25 media to and from the rest of the network. If the local station is the gateway, then the user is prompted for the X.25 media number for this station. Refer to the MAGNET BOSS/VS User Reference Manual, Appendix C, for recommended X.25 parameters. G. Option 3, Station Configuration, must be selected after all subnetworks have been defined. This utility allows the network manager to specify the names of the stations in all subnetworks which the home station will be accessing through MAGNET. For each station which is added, the utility prompts for station name, subnetwork number, station address and system serial number. Once the subnetwork number is entered, the subnetwork description field will be automatically updated. H. The last option in the Network Configuration menu is option 4, User Configuration. Remote user security is defined by this option. Remote users are mapped to a local user account and can be as unrestrictive or as restrictive as the network manager desires it to be. I. At this point the MAGNET network configuration for the home station is complete. The changes do not take affect until the MPx is rebooted. THIS PROCESS MUST BE DUPLICATED ON EVERY STATION IN THE MAGNET NETWORK. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg041 3.6.3.8. STARTUP _______ The MAGNET software is automatically started at system boot time, if the system startup file, .SYSDATA.START.CMD, contains the command, MAGNET.STARTUP. Alternatively, MAGNET may be started from the Network Status utility, option 2 when !MAGNET is executed. The Network Status utility has 3 options, the third one being MAGNET Start and Stop. In addition to starting MAGNET, each media on the station must be activated before MAGNET transactions can take place between systems on a particular media. Option 2, Medium Status and Control, of the Network Status utility will allow a user to start, terminate immediately or stop the media when inactive. Once each media is in an active state, option 1, Station MAGNET Status, of the Network Status menu should be selected. This utility allows the network manager to send polls to any station in the network to determine if the link between the systems is there. 3.6.3.9. OPERATION _________ Once MAGNET hardware and software have been installed and configured properly, the operation of MAGNET should be trans- parent to the user. Existing applications written for single systems may be easily adapted to run on a MAGNET network using the SETTRANS command. Many BASIC directives now support fully qualified file names, including the MPx installation name, to further enhance the interface to a MAGNET network. Also, many 8.6A utilities may also be run on a MAGNET network. 3.6.3.9.1. APPLICATIONS ____________ A. SETTRANS is an 8.6A feature which allows the user to set up a translation list for file names. The translation is typically to a file name on a remote system but may even be to a different file name on the local system. The proper syntax for SETTRANS is: >0010 SETTRANS "file.TEXT" The file used by SETTRANS is created using the MPx editor. The file format must be as follows: * - a single character on the first line which defines the wild card - defines one translation rule; several may be defined in one file :NAME:NAME1 - the first character defines the delimiter (in this example a ":") - a delimiter is required between file names but not at the end - NAME is the matched name - NAME1 is the target name SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg042 - NAME or NAME1 may contain one wild card at the begin- ning, end or middle of the name - the wild card, if used in NAME, will match 0-x bytes - the wild card, if used in NAME1, will reproduce the characters it matched in NAME (if any) ;; COMMENT - any two leading characters which are identical define a comment line An example of a SETTRANS file for a MAGNET environment is: * :.SALES.*: [REMOTE]().SALES.* MAGNET In this example, any references in the application to files in the .SALES. node will be translated to go over MAGNET to the system called REMOTE and access the files in REMOTE's SALES. node. () is the default disk name. ENDTRANS will deactivate the translation list specified by the previous SETTRANS. An "END" in BASIC will not reset SETTRANS. However, "RELEASE" will reset SETTRANS. Further information on SETTRANS can be found in section 3.7.7. NOTE: Translation also affects the file names in CALL, RUN, and SETTRANS itself, the directive in EXECUTE and the command in SYSTEM. Be careful not to translate more than you intend. B. MAGNET remote file access supports the following Business BASIC features: OPEN READ{RECORD} LOCK DIRECT WRITE{RECORD} UNLOCK SORT EXTRACT{RECORD} LIST SERIAL PRINT{RECORD} MERGE INDEXED FIND{RECORD} KEY CLOSE INPUT{RECORD} IND ERASE REMOVE FID C. Although applications need not be modified to run on a MAGNET network, some users may find that fine-tuning their applications for MAGNET will provide performance improvements. Some programming hints are listed below. o Limit the number of remote OPEN's and CLOSE's. OPEN's and CLOSE's take the most time in establishing a logical connection between the local and remote systems. o Do OPEN's of frequently accessed files at the beginning of the program, and leave them open. The initial OPEN has the largest amount of overhead when establishing a logical link between a local and a remote system. o When accessing multiple files on one remote system, keep at least one remote file open to that system to avoid overhead in re-establishing a link. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg043 o Use large records for large collection of data instead of many small records. o Use SETTRANS instead of PREFIX to qualify file names. PREFIX will not allow remote access, and SETTRANS is faster. MAGNET o Organize files so they are distributed between systems on the network. Avoid using a single MAGNET system as a file server. Place each file on the system which most often needs to access it. o Remote file access in applications should not exceed 20 - 30% of the recommended system load. Keep in mind that 1 remote access equals "2" system tasks - 1 on the local system and 1 on the remote system. o Incorporate MAGNET errors in error processing. 3.6.3.9.2. UTILITIES _________ 8.6A utilities supported by MAGNET are: COPY DIR CREATE NOTE: SETTRANS is not in effect for Pascal programs such as these utilities. Therefore, when using utilities over MAGNET, fully qualified remote names must be specified. 3.6.3.10. TROUBLE-SHOOTING ________________ Errors generated during a MAGNET transaction fall usually in one or more of the following categories: o Network Configuration (e.g. Error 60) o Naming and Translation (e.g. Error 12, 17) o Security (e.g. Error 13) o Hardware Failures (e.g. Error 95) o Communication Failures (e.g. Error 0, 5) o Communication Errors (e.g. Error 59) o System Load (e.g. Error 0, 33, 62) A. Error Processing Determining the cause of an error can sometimes become a tedious process in any networking environment. MAGNET has attempted to provide error codes which are identical to the normal file access errors, such as error 0, 5, 12. Recovery of these errors should be identical in a MAGNET environment as in a non-MAGNET environment. For applications which desire more descriptive network errors, a four-tuple error can be derived from the TCB(12). A complete listing of these error codes and recommended recovery process is documented in the MAGNET User Reference Manual (M 6363). SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg044 MAGNET B. Event Logging In addition to the descriptive four-tuple error codes, MAGNET has an event log capability which allows network transactions to be recorded for the whole subnetwork on any system in the subnetwork. The event log can log network errors, information, and statistics of all systems on the subnetwork which have their network reporting option activated. To access the Event Log utility, type !MAGNET and select option 3, Network Event Log. Two items will display, Event Log Control and Event Log Display. Select option 1, Event Log Control to configure the network logging facilities of this system. In the Event Log Control utility, the user is given the option to report its network events to the system on the subnetwork which is recording. The user may also specify that this system be the recording system on the subnetwork. The recording system can record errors, information, statistics or any combination of the three. Due to the overhead involved in keeping an active event log running, the recording system should be limited to a single, less heavily used, system on the subnetwork. In heavily used systems, event log recording/reporting should be activated only when problems are suspected on the network. Select option 2, Event Log Display, to display the contents of the log. As the Event Log Display utility is an ORIGIN DSS application, the event log output can be formatted according to the users specifications. C. Hardware Failures It is not uncommon for hardware failures to occur in any networking environment. Due to the many vendors involved, i.e. modems, PDN's, switches, phone lines, etc., it is difficult to isolate the cause of the problem. It is imperative, therefore, to ensure that on each MPx system on the MAGNET network, the hardware and software were installed and configured correctly. In addition, check the following: o loose cable connections - Is the IMLC to modem cable connected at both ends? Are the LAN drop cable and trunk cable secured at each tap box/repeater? Is the drop cable plugged in to the LAN controller? o LAN terminators - Are the LAN terminators properly placed in the tap boxes which terminate the LAN network? MAGNET Are all other tap boxes in between free of terminators? o IMLC/LAN diagnostics - Have a service representative run the IMLC and LAN diagnostics to assure the SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg045 controllers are not defective. Have him verify that the switch settings on the controllers are set properly. What does the MAGNET Eventlog Statistics and Errors indicate? o modem tests - Have end to end tests been run on the modems to detect any defects? o phone line - Has the phone company been called to check the phone lines for quality? o Public PDN problems - Has the Public PDN been called to determine if they are having network problems? o Private PDN problems - Have all diagnostic tests been run on the X.25 switch? Is it properly configured? 3.6.3.11. LAN CONTROLLER ___ __________ The LAN controller must be configured for an MMC address and a station address when used in a MAGNET network. The MMC addressing differs depending on whether the MPx is a 7000/7100/8000 or a 9000/9100/9500 series. The station address and the terminator and bias switches are the same on the 7000, 8000 and 9000 series. 3.6.3.11.1. 7000/7100/8000 MMC Addressing ______________ ___ __________ Switch S1, location 2T sets the MMC address. 1 = OPEN or OFF 0 = CLOSED or ON 7 6 5 4 3 2 1 Board No. 7 6 5 4 3 2 1 Board No. 1 0 0 1 1 1 0 1 0 1 0 1 1 1 0 33 1 0 0 1 1 0 1 2 0 1 0 1 1 0 1 34 1 0 0 1 1 0 0 3 0 1 0 1 1 0 0 35 1 0 0 1 0 1 1 4 0 1 0 1 0 1 1 36 1 0 0 1 0 1 0 5 0 1 0 1 0 1 0 37 1 0 0 1 0 0 1 6 0 1 0 1 0 0 1 38 1 0 0 1 0 0 0 7 0 1 0 1 0 0 0 39 1 0 0 0 1 1 1 8 0 1 0 0 1 1 1 40 1 0 0 0 1 1 0 9 0 1 0 0 1 1 0 41 1 0 0 0 1 0 1 10 0 1 0 0 1 0 1 42 1 0 0 0 1 0 0 11 0 1 0 0 1 0 0 43 1 0 0 0 0 1 1 12 0 1 0 0 0 1 1 44 1 0 0 0 0 1 0 13 0 1 0 0 0 1 0 45 1 0 0 0 0 0 1 14 0 1 0 0 0 0 1 46 1 0 0 0 0 0 0 15 0 1 0 0 0 0 0 47 MAGNET 0 1 1 1 1 1 1 16 0 0 1 1 1 1 1 48 0 1 1 1 1 1 0 17 0 0 1 1 1 1 0 49 0 1 1 1 1 0 1 18 0 0 1 1 1 0 1 50 0 1 1 1 1 0 0 19 0 0 1 1 1 0 0 51 0 1 1 1 0 1 1 20 0 0 1 1 0 1 1 52 0 1 1 1 0 1 0 21 0 0 1 1 0 1 0 53 0 1 1 1 0 0 1 22 0 0 1 1 0 0 1 54 0 1 1 1 0 0 0 23 0 0 1 1 0 0 0 55 0 1 1 0 1 1 1 24 0 0 1 0 1 1 1 56 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg046 0 1 1 0 1 1 0 25 0 0 1 0 1 1 0 57 0 1 1 0 1 0 1 26 0 0 1 0 1 0 1 58 0 1 1 0 1 0 0 27 0 0 1 0 1 0 0 59 0 1 1 0 0 1 1 28 0 0 1 0 0 1 1 60 0 1 1 0 0 1 0 29 0 0 1 0 0 1 0 61 0 1 1 0 0 0 1 30 0 0 1 0 0 0 1 62 0 1 1 0 0 0 0 31 0 0 1 0 0 0 0 63 0 1 0 1 1 1 1 32 NOTE: MMC address 0 is reserved for the 4 WAY MCS board. 3.6.3.11.2. 9000 MMC Addressing ____ ___ __________ Switch S1, location 2T sets the MMC address. 1 = OPEN or OFF 0 = CLOSED or ON 7 6 5 4 3 2 1 Board No. 7 6 5 4 3 2 1 Board No. 1 0 0 1 1 1 0 1 1 1 0 0 1 1 0 41 1 0 0 1 1 0 1 2 1 1 0 0 1 0 1 42 1 0 0 1 1 0 0 3 1 1 0 0 1 0 0 43 1 0 0 1 0 1 1 4 1 1 0 0 0 1 1 44 1 0 0 1 0 1 0 5 1 1 0 0 0 1 0 45 1 0 0 1 0 0 1 6 1 1 0 0 0 0 1 46 1 0 0 1 0 0 0 7 1 1 0 0 0 0 0 47 1 0 0 0 1 1 1 8 1 0 1 1 1 1 1 48 1 0 0 0 1 1 0 9 1 0 1 1 1 1 0 49 1 0 0 0 1 0 1 10 1 0 1 1 1 0 1 50 1 0 0 0 1 0 0 11 1 0 1 1 1 0 0 51 1 0 0 0 0 1 1 12 1 0 1 1 0 1 1 52 1 0 0 0 0 1 0 13 1 0 1 1 0 1 0 53 1 0 0 0 0 0 1 14 1 0 1 1 0 0 1 54 1 0 0 0 0 0 0 15 1 0 1 1 0 0 0 55 1 1 0 1 1 1 1 32 1 0 1 0 1 1 1 56 1 1 0 1 1 1 0 33 1 0 1 0 1 1 0 57 1 1 0 1 1 0 1 34 1 0 1 0 1 0 1 58 1 1 0 1 1 0 0 35 1 0 1 0 1 0 0 59 1 1 0 1 0 1 1 36 1 0 1 0 0 1 1 60 1 1 0 1 0 1 0 37 1 0 1 0 0 1 0 61 1 1 0 1 0 0 1 38 1 0 1 0 0 0 1 62 1 1 0 1 0 0 0 39 1 0 1 0 0 0 0 63 MAGNET 1 1 0 0 1 1 1 40 NOTE: MMC address 0 is reserved for the MCS board. MMC address 16 - 31 may not be used for LANC on the 9000. 3.6.3.11.3. Station Addressing _______ __________ Switch S4 sets the address of the system, the bias switch, and the termination switch. Each system on the LAN subnetwork must have a unique station address from 01 to 63. One and only one system on the subnetwork should have the bias switch set to OPEN; all others must have the bias switch set to CLOSED. All systems on the subnetwork should set the terminating switch to OPEN and use 100 ohm resisters in the terminating tap boxes instead. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg047 Switch S4 - 1 OPEN = Bias supplied to cable CLOSED = No bias supplied to cable Switch S4 - 2 OPEN = No terminator CLOSED = Terminator in circuit Switch S4 - 3 to S4 - 8 1 = OPEN 0 = CLOSED 3 4 5 6 7 8 Station Address 0 0 0 0 0 1 1 0 0 0 0 1 0 2 0 0 0 0 1 1 3 0 0 0 1 0 0 4 0 0 0 1 0 1 5 0 0 0 1 1 0 6 Although the station address 0 0 0 1 1 1 7 is set hexadecimally on the 0 0 1 0 0 0 8 LAN controller, the MAGNET 0 0 1 0 0 1 9 LAN software will look at the 0 0 1 0 1 0 10 station address decimally. 0 0 1 0 1 1 11 . . . . 1 1 1 1 1 0 62 1 1 1 1 1 1 63 3.6.3.11.4. Board Sub-type _____ ________ Switch S2 sets the board sub-type for the 7000/7100/8000 and 9000/9100/9500. S2 - 1 OPEN (OMNINET) MAGNET S2 - 2 CLOSED S2 - 3 CLOSED S2 - 4 through S2 - 7 CLOSED 3.6.3.12. DOCUMENTATION _____________ Further information on MAGNET can be obtained from the MAGNET User Reference Manual (M 6363). 3.6.4. FILE TRANSFER FACILITY ____ ________ ________ File Transfer Facility (FTF) on 8.6A has been enhanced to support a Local Area Network (LAN) media as well as continue to support the Wide Area Network (WAN) through the X.25 protocol. In additon, FTF is now configured using the same configuration utility, Network Management Facilities, as MAGNET. A FTF network can easily co-exist with a MAGNET network without duplicating the network configuration efforts. 3.6.4.1. INSTALLATION ____________ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg048 3.6.4.1.1. SOFTWARE INSTALLATION ________ ____________ Follow the installation instructions in this Software Announcement. The configuration record must have the following options selected for FTF to function. File Transfer Facility Network Management Facilities LAN (for LAN networks) X.25 (for WAN/X.25 networks; # of X.25 lines = 2/IMLC port) 3.6.4.1.2. HARDWARE INSTALLATION ________ ____________ The hardware installation and requirements for FTF are identical to those of MAGNET. FTF can either run on a LAN network, or an X.25 network. Refer to the MAGNET section in this Software Announcement for details on hardware installation. 3.6.4.2. CONFIGURATION _____________ Current FTF users will have to redefine their networks by using the new 8.6A configuration utilities, EZCONFIG or Network Management Facilities (NMF). EZCONFIG may be used to configure networks with a single media type, such as X.25 or LAN. NMF is used to configure more complex networks which use both X.25 and LAN as medias. NMF must also be run to make any modifications to the default X.25 parameters. Details on how to run EZCONFIG and NMF are documented in the MAGNET Configuration section of this Software Announcement. FILE TRANSFER FACILITY 3.6.4.3. COMPATIBILITY _____________ Although MAGNET networks can only communicate between MPx systems, FTF remains compatible to the FTF products on the 13xx and 2000 series when using the X.25 media. Thus, MPx systems which are on existing FTF X.25 networks with 13xx and 2000 systems can continue to transfer data between these systems. MPx systems using LAN as the FTF media are restricted to transmitting files between MPx systems only. 8.6A FTF also continues to support the interface to MAI MAIL which allows out-tray messages to be transmitted remotely. On previous levels, MAI Office (OMS) programs which were to be started by FTF were listed in the Network Services (NS) Topology File. On 8.6A, the NS Topology File utilities have been replaced with Network Management Facilities. Therefore, on 8.6A, in order to have FTF start MAI Office programs, the OMS directory must be entered in the FTF Security Access utility with the EXECUTE option enabled: (family).OMS. EXECUTE The OMS node must be on the same family as the NSPGM node. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg049 Previous releases of FTF started ghost tasks for FTF servers. !TASKS on 8.6A will now display a task called "FTF" instead of "Gx". 3.6.4.4. ITEMS TO NOTE _____ __ ____ FTF and MAGNET can be configured to run concurrently on the same system. However, since both products share common re- sources, such as X.25 logical channels, the performance of either products may be impacted when there is a high demand for these resources. FTF on 8.6A does not support transmissions of remote file names. In other words, FTF between two systems will not support transmissions of files which reside on a third system in a MAGNET network. To specify concurrent outgoing FTF transfers, add in the FTF Security Access utility, either *FTF2 or *FTF3 with the EXECUTE option. *FTF2 will allow 2 concurrent outgoing transfers, *FTF3 will allow 3 concurrent outgoing transfers. 3.6.4.5. DOCUMENTATION _____________ Further information on FTF can be found in the MAGNET/VS User Reference Manual (M 6363) and the File Transfer Facility User Reference Manual (M 6352A). Business BASIC 86 3.7. 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 "Core" Business BASIC features o Useful BOSS/IX features added to BOSS/VS o Useful BOSS/VS features added to BOSS/IX o Program generation tools o More system independent features o File name translation (primarily for MAGNET support) o Multi-key file support There are still language features on both systems which are NOT part of BB86! To support existing older code, not everything could be made common to both systems. New programs should use BB86. ______ ___ 3.7.1. BUSINESS BASIC 7.3A AND 8.6A ________ _____ ____ ___ ____ 7.3A_BOSS/IX_Business_BASIC ___________________________ o All BB86 features SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg050 o All 7.2 (and prior) BASIC features 8.6A_BOSS/VS_Business_BASIC ___________________________ o All BB86 features o All 8.5 (and prior) BASIC features o 8.6A Spooler support 3.7.2. COMPATIBILITY ENHANCEMENTS _____________ ____________ Most of the features that are in both BOSS/IX and BOSS/VS Business BASIC ("core" features) are carried over into BB86. BOSS/IX_Features_Added_to_BOSS/VS _________________________________ o RENAME "FROM" , "TO" [, ERR=stmtno ] Changes the name of the "FROM" file to "TO" o ENCRYPT "FROM" , "TO" [, ERR=stmtno ] Works like PSAVE "TO" except the program to be "protected" resides on disk rather than in BASIC's program buffer. o TCB (task control block function) has two added functions TCB (10) returns a 0 if in EXTEND and a 1 if in NOEXTEND mode. TCB (12) returns the last error 4-tuple. o SERIAL files may now be accessed with a lower IND= value Business BASIC 86 than the previous read. BOSS/VS_Features_Added_to_BOSS/IX _________________________________ o The CSW, PNM and WHO system variables added. o INITFILE "NAME" [, ERR=stmtno ] initializes/clears a file. o PSAVE "PGMNAME" [, ERR=stmtno ] does a "protected" save. o QUIT now stops BASIC and drops back to 'shell' o RELEASE now stops BASIC and logs off the terminal. o Double quotes (") may now appear within string constants by entering them twice. o LIST and SETTRACE now pause after listing a full page. 3.7.3. BB86 ENHANCEMENTS ____ ____________ Additional_Enhancements_Added_to_BB86 _____________________________________ o CONSOLE LOCK [ "PASSWORD" [, MSG=PROMPT$ ] ] This either locks out BASIC's console mode or re-enables it. CONSOLE LOCK with the "password" parameter and optional MSG= clause will stop the program from dropping into console mode for ANY reason (which includes end-of-program, uncaught escape key or uncaught error) unless the user types in the correct password. If the MSG= clause is given it will be used as a prompt each time the password is requested. If there is no MSG= clause SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg051 then no prompt will be given. Once the CONSOLE LOCK is given it will remain in affect until it's turned off (which is dome by entering CONSOLE LOCK without the password parameter), a START command is encountered or BASIC is exited. CONSOLE LOCK "password", MSG=(0,23)+'CL'+" ENTER PASSWORD? " o ENDIF ENDIF is used to terminate the closest unterminated IF statement. NOTE: This works exactly like FI and is meant to (someday) replace it. o END= clause now allowed within the IND function. 0100 I=IND(4,END=200, ERR=120) o OPEN with the new ATTR= clause controls spooling. NOT part of BB86 but introduced in 8.6A. 3.7.4. SPOOLER CONTROL _______ _______ OPEN with ATTR= OPEN (lun, ATTR=attributes$ [, ERR=stmtno ] ) printer$ The string that ATTR= takes (attributes$) may specify a Business BASIC 86 series of spooler attribute assignments which are each composed of: 1) Spooler attribute name 2) Equals sign (=) 3) The value of that attribute which may be either alphanumeric, numeric, true-or-false or a file name (depending on that attribute). Either uppercase or lowercase letters may be used and are not significant except within file names. Spaces may also be used freely except that they may not appear in the middle of a name or value. Examples of spooler attribute assignments: CLASS=Big date = 07/23/86 loadforms = f LINES=51 SPOOLER ATTRIBUTES, VALUES AND DESCRIPTIONS Attribute Value's Name_____ Type___ Description _________ _______ ___________ ALIAS = alphanumeric Used to notify user that spool job complete AUTOFF = true/false Automatic formfeed CLASS = alphanumeric Spooler class (up to 6 characters) COPIES = numeric Number of copies to print DATE = alphanumeric Date to begin printing DELETE = true/false Delete disk file after printing SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg052 END = numeric Ending page FORM = alphanumeric Form name FORMFEED = true/false Formfeed before job HEADINGS = true/false Add headings HIBIT = true/false High bit on LINES = numeric Lines per page LOADFORMS = true/false Require a load forms when beginning NOTIFY = true/false Notify the logon account when done NUMBERS = true/false Add page numbers PAGES = numeric Number of seperator pages PAGING = true/false Automatic paging PRINTDEF = file name Printer definition file PRIORITY = numeric Job priority RAWMODE = true/false Set rawmode REQUEUE = true/false Requeue job SPOOLNAME = file name Set the spooler file name SPOOLON = true/false Spooling on or off for this job START = numeric Starting page TIME = alphanumeric Time to begin printing WAIT = true/false Wait on close Business BASIC 86 If more than one spooler attribute is being assigned in the string then each assignment must be seperated from the others by at least one space. Examples of OPEN ATTR= : OPEN (1, ATTR= " TIME=03:03 DATE=07/24/86 CLASS=MINE ") "LP" OPEN (LPU, ATTR= "alias=WAKEUP notify=t") L$ OPEN (2, ERR=100, ATTR= "CLASS=CLASS1 spoolname=report.no1")"P*" A$="form=big hibit=t; OPEN (3, ATTR=A$) "PO" NOTE: 1) True/false must be in T/F or t/f format. 2) Commas given up because of BOSS/IX shell - spaces work on both BOSS/IX and BOSS/VS. 3) Commands are not case dependent. 3.7.5. SYSTEM INDEPENDENT ENHANCEMENTS ______ ___________ ____________ o The SYS system variable now returns the system level in the form: BB86 aa.bbC*dd.ee (or eee) Example: >print sys BB86 08.06A*30.100 o The ASCII and CHAR functions provide character set independence. 1) ASCII (string) works like ASC only the value returned is the standard ASCII numeric code of the first character. Example: A=ACSII("A"), B=ASC("A") would set A to 65 on both systems but would set B to 193 on BOSS/VS or 65 on a BOSS/IX. 2) CHAR (number) works like CHR only 'number' is assumed to be the standard ASCII numeric code and not a system dependent "actual" ASCII code. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg053 Example: LF$=CHAR(10) would set LF$ to $0A$ on a BOSS/IX and $8A$ on a BOSS/VS. o DEVINFO: function returning device information. Corresponds to BOSS/IX's TSK(0) function and BOSS/VS's CALL "GETDEVINFO". o CREATE: system independent file creation (like FILE). o ATTR function: system independent file information (replaces FID). Business BASIC 86 3.7.5.1. CREATE: System Independent File Creation _______ ______ ___________ ____ ________ CREATE ATTR=attributes$ [, FMT=format$ ] [, ERR=stmtno ] The CREATE directive will create any file type and is a system independent version of the FILE directive. This string that the ATTR= clause takes is very similar in general format to the OPEN's ATTR= string. The difference between the two is the attributes which are allowed within the string. The FMT= clause creates multi-key files. Attribute Value Default Description _________ _____ _______ ___________ GROWTH = numeric sys. dep. Additional records allocated INITIAL = numeric sys. dep. Initial records allocated NAME = file name no default File's name ORGANIZATION = alphanumeric IND File Type - DIR - DIRECT IND - INDEXED MUL - MULTI-KEYED SER - SERIAL STR - STRING (BOSS/IX) OWNER = alphanumeric sys. dep. File owner RECORD_SIZE = numeric 80 Bytes per record RECORDS_ALLOWED = numeric 1000 Maximum records in file KEY_SIZE = numeric no default Key size for DIRECT files USAGE_RIGHTS = alphanumeric sys. dep. Usage rights When attributes (except NAME and, for DIRECT files, KEY_SIZE) are omitted, then the default is used. If the same attribute is given more than once, then the LAST assignment is the one which takes affect. Examples of CREATE: CREATE ATTR= "name=my.file organization=ind record_size=120 "+ "records_allowed= 1000" INDEXED "my.file",1000,120 CREATE ATTR= "name=PAYROLL organization=DIR usage_rights=w(pay.roll) "+ "records_allowed=2000 initial=2000 record_size=250" 3.7.5.1.1. ATTR: System Independent File Information _____ ______ ___________ ____ ___________ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg054 A$ = ATTR (lun, attrstr$) The ATTR function is the system independent replacement for the FID function. It returns selected attributes from an open file. The 'attrstr$' string is made up of a list, seperated by spaces, of attribute names or control verbs. All of CREATE's attribute names are supported with a few additions. Business BASIC 86 Value Attribute Returned Description _________ ________ ___________ ALL = control Specifies ALL attributes are to be returned in long form. This must be the only thing in attrstr$ if used. GROWTH = numeric Number of additional records. INITIAL = numeric Number of initial records allocated. KEY_SIZE = numeric Key size for DIRECT files (0 for others) LONG = control Specifies all of following attributes are to be returned in the name=value form. NAME = file name Name of file. ORGANIZATION = alphanumeric Returns a 3 byte ASCII code: BAS - BASIC code file COB - COBOL code file (BOSS/VS) DEV - Device (not a file) DIR - DIRECT or SORT IND - INDEXED MUL - MULTI-KEYED PAS - Pascal code file (BOSS/VS) SER - SERIAL STR - STRING (BOSS/IX) OWNER = alphanumeric Owner of file. RECORD_SIZE = numeric Bytes per record. RECORDS_ALLOWED = numeric Maximum number of records allowed. RECORDS_USED = numeric Records used so far (0 if device). SHORT = control Specifies all of following attributes are to be returned as values only. This is the default. USAGE_RIGHTS = alphanumeric Usage rights of the file. If more than one attribute is requested, then the values or name=value pairs will be seperated by two spaces. POS(" "=A$) will work to pull apart the returned values. NOTE: NAME, OWNER, and USAGE_RIGHTS values are system dependent. Examples: in +2 NAME = (DISK).ABC.MYFILE ORGANIZATION = IND RECORD_SIZE = 120 RECORDS_ALLOWED = 1000 RECORDS_USED = 352 KEY_SIZE = 0 INITIAL = 334 GROWTH = 150 OWNER = MY.ACCT USAGE_RIGHTS = W(SR.*);R(*.*) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg055 This is an example file on a BOSS/VS system only. A BOSS/IX system would have different looking NAME, OWNER and USAGE_RIGHTS values. Business BASIC 86 Function Returned_String ________ _______________ ATTR(1,"Organization") "IND" ATTR(1,"LONG KEY_SIZE") "KEY_SIZE=0" ATTR(1,"initial growth") "334 150" ATTR(1,"all") "NAME=(DISK).ABC.MYFILE ORGANIZATION=IND "+ "RECORD_SIZE=120 RECORDS_ALLOWED=1000 "+ "RECORDS_USED=352 KEY_SIZE=0 INITIAL=334 "+ "GROWTH=150 OWNER=MY.ACCT "+ "USAGE_RIGHTS=W(SR.*);R(*.*)" 3.7.6. SYSTEM DEPENDENT IN BB86 ______ _________ __ ____ o ASCII character set o String values o Hex strings o Values returned from ASC and CHR o File names o Usage rights string (ATTR) o Logon account (ATTR and WHO) o SYSTEM and ! commands 3.7.7. FILE NAME TRANSLATION - MAGNET SUPPORT ____ ____ ___________ _ ______ _______ o SET TRANS "file" Turns on translation. o END TRANS Turn off translation. o B$ = TRANS( A$ ) String function returning the translation of A$. If A$'s value is not found in the translation file or translation is not in affect, then A$ is returned unchanged. o T$ = TRX Task variable returning the name of the translation file currently in affect. If translation is not in affect then an empty string is returned. NOTE: This function is system dependent. Business BASIC 86 When translation is turned on, it automatically translates: o File names (accepted as an argument) CALL, DIRECT, ENCRYPT, ERASE, INDEXED, INITFILE, LISTPROGRAM, MAKEPROGRAM, MULTI, OPEN, PSAVE, RENAME, RUN, SAVE, SERIAL, SETTRANS, SORT and START. NOTE: File names embedded within other information are not translated (FILE and file names within ATTR=, SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg056 ! or SYSTEM) nor are returned file names (ATTR, FID, PNM AND TRX). o Ghost task names RELEASE and START o The entire string of an ATTR= clause ______ CREATE and OPEN o An entire system command ______ SYSTEM and ! It also explicitly translates strings passed to the TRANS function. Examples: _________ These examples use the following EDIT created translation file, MYTRANS.TEXT :MYFILE:MYFILE86 :MYFILE2:(DISK).MYNODE.MYFILE2 :system:BOSS/VS :attr 1:class=x spoolon=f form=ck :copy a,b delexist:copy a,b delexist newrights=f :/user/jon/doe/data:(DISK).JON.DOE.DATA :a*:(DISK2).abc.a* Once translation is enabled by a SETTRANS "MYTRANS.TEXT" then: Command Result _______ ______ OPEN(1) "MYFILE" OPEN(1) "MYFILE86" SAVE "MYFILE2" SAVE "(DISK).MYNODE.MYFILE2" A$=TRANS("system") A$="BOSS/VS" A$=TRANS("config") A$="config" EXECUTE "OPEN(1)""system""" EXECUTE "OPEN(1)""BOSS/VS""" EXECUTE "system" EXECUTE "system" !ERROR OPEN(1,ATTR="attr 1")"LP" OPEN(1,ATTR="class=x spoolon=f form=ck)"LP" OPEN(1,ATTR="ATTR 1")"LP" OPEN(1,ATTR="ATTR 1")"LP" !ERROR !copy a,b delexist !copy a,b delexist newrights=f OPEN(1)"/user/jon/doe/data" OPEN(1)"(DISK).JON.DOE.DATA" SERIAL "abc",10,10 SERIAL "(DISK).abc.abc",10,10 Business BASIC 86 3.7.8. PROGRAM GENERATION ENHANCEMENTS _______ __________ ____________ Enhancements to make it easier for a BASIC program to create or manipulate another BASIC program: o LIST PROGRAM "FROM.PGM", "TO.SERIAL" [, ERR=stmtno ] This lists the file "FROM.PGM" into a serial file "TO.SERIAL". "TO.SERIAL" will be created if it's not already present on the disk and may be a printer. o MAKE PROGRAM "FROM.SERIAL", "TO.PGM" [, ERR=stmtno ] This converts the serial file "FROM.SERIAL into its BASIC program equivalent file, "TO.PGM". "TO.PGM" SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg057 will be created if necessary. o SYNTAX "line to check" [, ERR=stmtno ] SYNTAX checks the BASIC syntax of its string argument and will generate an error (usually an ERROR 20) if there's something wrong. This would normally be used by a program generator before writing a user specified line to a serial "program". Syntax is not very fast on BOSS/VS. For further information on BB86 see the Business BASIC 86 ________ _____ __ Reference Manual, M 6262. _________ ______ 3.7.9. MULTI-KEY FILES _________ _____ 3.7.9.1. Introduction ____________ Multi-Keyed files offer the capability to reference a set of records (a file) by a number of different access paths (keysets). This capability has been possible in the past only through the use of combinations of files. For example, an employee data base might be implemented by storing all of the employee data records in a Direct file with the employee number being the key. Random access to the data records based on other sorts (e.g. employee name or department number) could be implemented by creating one Sort file for each required access path. The keys for these Sort files would contain the information needed (like employee name) as well as some unique identifier that would allow reference to the Direct "master" file. This unique identifier should be the key value associated with the record. With the use of Multi-Keyed files, it is possible to maintain multiple access paths in a single file. Each access path provides a means to reference the data records both randomly and sequentially according to the order of the alternate key values. Following are some examples of specific cases where the use of Multi-Keyed files would be recommended. Multi-key Files 3.7.9.2. Possible Applications ________ ____________ 3.7.9.2.1. Existing Applications That Use Sets of Files ________ ____________ ____ ___ ____ __ _____ Existing applications that use "sets" of Direct and Sort files to emulate the behavior of Multi-Keyed files may be modified to use the Multi-Keyed file type. The key of the Direct file becomes the primary key of the new Multi-Keyed file. Each Sort file becomes an alternate (or duplicate) keyset on the Multi-Keyed file. See section 3.7.9.6 below on conversion of applications for more information. 3.7.9.2.2. Existing Applications That Use the Sort Utility ________ ____________ ____ ___ ___ ____ _______ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg058 Some applications do not need an alternate access path to be maintained during normal operations, but only on special occasions such as end-of-month processing. In the past, this requirement might be met by using the Sort utility to generate a new file by sorting the Direct file on the desired field. With the advent of Multi-Keyed files, this requirement can be satisfied by using SETFIELD statements in the BASIC program that requires the alternate access path. The SETFIELD directive can be used to generate a new keyset (access path) on a defined field. The same SETFIELD directive can be used the remove the keyset when there is no further need for that access path. 3.7.9.2.3. Enhancement of Existing Applications ___________ __ ________ ____________ Existing applications may be enhanced by the use of multiple access paths available with Multi-Keyed files. The easy-to-use nature of the Multi-Keyed syntax will make development of these enhancements to programs much simpler and will reduce development time. 3.7.9.2.4. Rewriting Applications or Writing New Applications _________ ____________ __ _______ ___ ____________ When applications need to be rewritten for other reasons (for example, for improved maintainability or added functionality) or when new applications are planned, the added functionality of Multi-Keyed files and the improved readability of syntax should certainly be considered. Multi-key Files 3.7.9.3. Benefits of Using Multi-Keyed Files ________ __ _____ ___________ _____ When a single Multi-Keyed file is used in place of the techniques previously available, such as using sets of Direct and Sort files, system administrators and operators will be able to take advantage of several benefits. These benefits will take the form of reduced complexity and improved productivity, both in program development and in day-to-day operations. 3.7.9.3.1. Reduced File Maintenance _______ ____ ___________ One of the benefits that system administrators and operators will receive is a reduction in file maintenance tasks. When a set of files is used, care must be taken to save or restore the entire set when making or using backup copies. Obviously, with a single file, there are no concerns about missing part of the data base on a backup. 3.7.9.3.2. Improved Data Integrity ________ ____ _________ Another advantage to using Multi-Keyed files is that it is much easier to maintain data integrity within the data base. One reason for this is related to the fact that there is reduced file maintenance. If an error is made saving or restoring or copying a set of files the result may be a SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg059 mismatched set. Problems of this sort would result in unpredictable results in running the application which would be very difficult to diagnose. Using a single Multi-Keyed file would eliminate these problems. Another reason Multi-Keyed files result in better data integrity has to do with the problems of maintaining correct programs. When a record is added to a set of files, it is implemented as a WRITE to the Direct file and a WRITE of the corresponding key to each of the related Sort files. If this "logical write" operation takes place in more than one place in the application, care must be taken to make sure that all files are correctly updated. When operations for rewriting or deleting records are taken into account, it becomes apparent that there is significant potential for programming errors. The central problem is that the set of files is not "self-describing". The correct updating sequence is "hidden" in the application program itself. The problem of maintaining correct record updates is compounded when a new access path (and Sort file) is to be maintained. None of these problems exists with Multi-Keyed files because the file system is responsible for maintaining all keysets and because Multi-Keyed files are self-describing. Another potential cause for data integrity problems can occur Multi-key Files after a system failure. While each file in a set of files may be separately recovered using the appropriate utility (see section 3.7.9.7) problems may still exist because an update operation was in progress at the time of the system failure. For example, if a record was being rewritten, it might require updates to several of the associated Sort files. If the system failed between two of the Sort file updates, the set of files would contain inconsistent information. This kind of error is undetectable by the file repair utilities. Multi-Keyed files, on the other hand, do not have this problem because the file repair utilities will correct any inconsistencies in keysets. 3.7.9.3.3. Improved Performance ________ ___________ There are several areas where the use of Multi-Keyed files will provide better performance than an equivalent implementation using a set of files. One area of particular interest is the reading of a record based on an alternate keyset. When accessing a set of files, this function requires a READ of the appropriate Sort file, extraction of the Direct file key from the Sort file key, then a READ of the Direct file. The corresponding operation on a Multi-Keyed file requires only a single READ. The READ of the Multi-Keyed file is significantly faster than the sequence required on a set of files. More information on performance is contained in section 3.7.9.9. 3.7.9.3.4. Reduced Disk Space Requirements _______ ____ _____ ____________ Multi-Keyed files use disk space more efficiently than do sets of Direct and Sort files. The actual amount of savings SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg060 depends on how many Sort files are involved and the relative sizes of the keys versus the data records. As the number of Sort files that are replaced increases and as the key size increases, the percentage of saved disk space will increase. In a typical application with 4 keysets and keys that are approximately one fifth the size of the data records, a savings of 10 to 20% would be realized. In addition, on BOSS/VS, some applications can make use of the variable length record feature of Multi-Keyed files for additional disk space savings. 3.7.9.3.5. Reduced Complexity of Applications _______ __________ __ ____________ As mentioned previously, the use of Multi-Keyed files and the new syntax available will simplify record access to the user data base. This will lead to fewer programming errors that result in inconsistencies in the user data base. In addition, Multi-key Files it will reduce program development and maintenance time and costs. 3.7.9.4. Syntax For Multi-Keyed Files ______ ___ ___________ _____ This section introduces the syntax for operations on Multi-Keyed files. It conveys the more important aspects of most operations by use of examples. There are a few more complex, less frequently used aspects which the reader may at first skip. 3.7.9.4.1. Creating a Multi-Keyed File ________ _ ___________ ____ Creation of Multi-Keyed files is like the creation of other file types, except with the addition of the required FMT= clause: 0300 MULTI FILENAME$,NUMRECS,RECSIZE,FMT=FORMAT$,ERR=0320 RECSIZE and ERR= are optional. In this example, FILENAME$ has been previously set to the name of the file to be created. NUMRECS has been previously set to the maximum number of records to be allowed in the file. The "number of records" has the intuitively obvious meaning: If one writes a record which doesn't replace a record that was there previously, this increases the number of records used in the file by one. If one writes a record which replaces a previously-existing record, this has no effect on the record count. If one removes a record, this decreases the number of records used in the file by one. If one attempts to add a record so that the number of records exceeds NUMRECS, then an error 2 occurs. RECSIZE (optional) has been previously set to the maximum number of bytes allowed in each record. If this value is SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg061 omitted, BASIC will calculate the value as the smallest number of bytes which allows all the fields in the format string to be present. If a record which is to be written to the file contains more bytes than specified by the explicit or implicit RECSIZE, error 1 will occur. FMT=FORMAT$ is described by section 3.7.9.4.1.1. ERR=xxxx (optional) shows the number of the statement to be executed next if the system was unable to create this Multi-Keyed file. This overrides any SETERR statement which Multi-key Files may have been executed but does not override SETESC if the error is that was pressed. 3.7.9.4.1.1. Format String Overview ______ ______ ________ FMT=FORMAT$ shows how each record in the file is divided into fields, via (in this example) FORMAT$. FORMAT$ has been previously assigned something which we will call the "format string". Generally, all records in the same file will be divided into fields in the same way; just how that division is performed is described in the format string. The format string describes each field in the record layout. We show here a sample format string. For purposes of clarity we show each field on a separate line; in practice, they're typically all part of the same string, and are separated from each other by a space: EMPLNUM# = N5 PRIMARY SOCIALSN# = N9 ALTKEY FRSTNAME# = S16 LASTNAME# = S20 FULLNAME# = LASTNAME# + FRSTNAME# DUPKEY DEPTNUM# = N4 DUPKEY COMMENT# = S*200 The first part of each field description is a field name ending with #, followed by =. The part of the field name before the # is subject to the same restrictions as BASIC numeric variable names (begins with a letter, etc.). After the = comes field information, followed by optional keyset information. Field information is described in section 3.7.9.4.1.2. Multi-Keyed files, as the name implies, can have more than one key per record. The keys are derived from the values in the fields of each record. The above example would have a keyset based on each of these fields: EMPLNUM#, SOCIALSN#, FULLNAME#, and DEPTNUM#. Each record would have a key in each of these keysets. The keys for a given record would be equal to the value of each of these four fields in the record. The keyset information shows whether a given field is represented by a keyset, and what kind of keyset that is. The keyset information may be changed after the file has been in SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg062 use (see section 3.7.9.4.9); the field names and field information are not allowed to change for the life of the file; nor can new fields be added once the file has been created. Multi-key Files Keyset information, if present, is either PRIMARY, ALTKEY, DUPKEY, or NOKEY. If no keyset information is present, then NOKEY is implied. -- PRIMARY means that this field forms the primary keyset of the file. Every Multi-Keyed file must have one and only one PRIMARY keyset. The primary keyset may not be deleted, and does not allow duplicate values. Other special properties of the primary keyset are mentioned in this document at the appropriate places. Suppose a record is written to a Multi-Keyed file, and the PRIMARY key for that record matches the PRIMARY key for another record that is already in the file. That earlier record will be automatically removed from the file at the same time that the new record is written, unless DOM= is specified in the WRITE statement; in that case, the earlier record will stay, the new record won't be written at all, and the DOM branch will be taken. -- ALTKEY means that this field forms a keyset, and no two records in the file may have the same value for this field; this insures that all keys in the keyset are different. The keyset may be deleted, and there may be more than one of them, or none at all. Suppose a record is written to a Multi-Keyed file, and an ALTKEY-type key for that record matches the corresponding key for another record that is already in the file. That earlier record will stay in the file; an error 11 has occurred. -- DUPKEY means that this field forms a keyset, and it is permitted for several records in the file to have the same value for this field; this implies that several keys in the keyset may have the same value also. The keyset may be deleted, and there may be more than one of them, or none at all. Suppose a record is written to a Multi-Keyed file, and a DUPKEY-type key for that record matches the corresponding key for another record that is already in the file. That earlier record will stay in the file, and the new record will also get written; the records will coexist with duplicate keys in the same keyset. -- NOKEY means that this field is not represented by a keyset at all. If this field is either fixed-length or composite, a keyset (either ALTKEY or DUPKEY) may be added for this field at a later time. Even if it Multi-key Files SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg063 is not represented by a keyset, it may be part of a composite field which is represented by a keyset. In the above example, LASTNAME is not represented by a keyset, but FULLNAME is, and LASTNAME is part of FULLNAME. An ALTKEY or DUPKEY field may not be longer than 80 bytes. This limit does not apply to a NOKEY field. 3.7.9.4.1.2. Field Information _____ ___________ Field information in a format string shows (or implies) where the field starts, how large the field is, and what kind of information is in the field. Where the field starts in the record usually follows the simple rule: "Each field begins just after the end of the field defined just before it in the format string." Exceptions to this rule are discussed in section 3.7.9.4.1.2.5. When choosing how large the field is, and what kind of information is in the field, one can choose from five general categories: -- a fixed-length string field; -- a variable-length string field; -- a fixed-length numeric field; -- a variable-length numeric field; or -- a composite field. 3.7.9.4.1.2.1. Fixed-length String Fields ____________ ______ ______ There are three fixed-length string types, 'S', 'C', and 'X'. The 'S' type specifies that this field will be a string with null bytes appended to it, if necessary, when writing and all appended nulls removed when the field is read ( perhaps even null data bytes that the user wrote out as binary data). The type 'C' is exactly the same as 'S' except spaces are used rather than null characters. The 'X' type implies that trailing nulls will be added when writing, but that these nulls will not be removed when reading the field. Following the field type is the field size. For these types of fields, the field size is simply an integer indicating the size of the string. A field size specification must follow the field type. String type fields, by default, are left-justified. This means as fields are written to the file, they will have trailing characters appended to the right if they are too short or truncated from the right if they are too long. The character used for padding depends on the type of string used Multi-key Files as described above. As left-justified fields are read, trailing pad characters are removed (unless this is an 'X' type field). The fields can also be right-justified by adding the keyword RIGHT before the field type declaration. Right-justified fields simply add and remove leading rather SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg064 then trailing characters. Left-justified fields can also be defined by adding the keyword LEFT before the field type declaration. Examples: S10 a 10-byte string, padded with trailing null bytes which will be removed when the field is read back in LEFT S10 same RIGHT S10 a 10-byte string, padded with leading null bytes which will be removed when the field is read back in RIGHT X10 the same, except that the null bytes will be retained when the field is read back in RIGHT C20 a 20-byte string, padded with leading spaces which will be removed when the field is read back in 3.7.9.4.1.2.2. Fixed-length Numeric Fields ____________ _______ ______ The numeric field type allows a numeric field of fixed size to be defined. This type is designated by the character 'N'. The numeric field type consists of a optional sign, whole digits, and fractional digits. This annotated by: (+,-)N whole digits [. [fractional digits]] [] means optional The whole digits specify how many places to the left of the decimal point the number will contain. The fractional digits will specify how many places to the right of the decimal point the number will have. The '+' and '-' as well as the keywords SIGNED and UNSIGNED may be used to specify whether or not the field is signed. This method of defining a numeric field implies a "virtual" BASIC format mask. Some examples are shown below: 'N'_Specifier Implied_mask _____________ ____________ N5 "00000" ( 5 digit integer) N5.2 "00000.00" +N5.2 "+00000.00" Multi-key Files +N3 "+000" N.3 ".000" N2. "00." -N2 "+00" -N5.2 "+00000.00" UNSIGNED N5.2 "00000.00" ( same as N5.2) SIGNED N5.2 "+00000.00" SIGNED N2 "+00" Note that the period (".") will always be a period even if the user's system has the European format mask option in effect. Also note that '+', '-' and SIGNED may be used interchangeably SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg065 and any one of these produces implied masks with '+'s. 3.7.9.4.1.2.3. Variable-length Fields _______________ ______ A variable-length string is a linefeed terminated string (exactly like the field produced by the statement WRITE A$). The type is of the form 'S*n' where n is the estimated width the string and is used in calculation of the maximum record size. Some variable-length field's data could be shorter and some longer than their estimated width, as long as the total length of all these fields does not produce a record length which is greater than the maximum record size. A variable-length string may not be used as a keyset. A variable-length numeric is a free-form ASCII number terminated by a linefeed. This field is created by converting the number into its ASCII representation. This type is of the form 'N*n' where n is the estimated width. The same restrictions apply to n as with the variable-length string type. The length specified for a variable-length field is not enforced when writing that field; but it is used for calculating the maximum record length when creating a file. This means that if the format string describes each record as containing two variable-length fields, and one of the variable-length fields in a particular record is longer than specified in the format string, then the other variable-length field must be shorter, so that the overall record length does not exceed the maximum specified for the file. In general, variable-length fields must follow all fixed-length fields in the record; in other words, all fields which follow a variable-length field must be variable-length fields as well. For exceptions, see section 3.7.9.4.1.2.5. Variable-length fields may not be keysets; that is, they may not be declared to be PRIMARY, ALTKEY, or DUPKEY. It is possible for the first variable-length field to contribute to a composite field (see section 3.7.9.4.1.2.4). However, the Multi-key Files composite field cannot be used as a key definition. If any field overlaps a variable-length field, even by one byte (see section 3.7.9.4.1.2.5), then that field may not be PRIMARY, ALTKEY, or DUPKEY either. A variable-length field may only make up part of a composite field under the following conditions: -- only a specified number of bytes in the variable-length field is used, thus forcing the number of bytes in this component of the composite field to be fixed also (see section 3.7.9.4.1.2.4); and -- it is the first variable-length field in the record, thus forcing the position within the record as a whole to be fixed. There are also restrictions on the use of a variable-length using the "starting-position clause". See section SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg066 3.7.9.4.1.2.5 for details. 3.7.9.4.1.2.4. Composite Fields _________ ______ One might assume that a composite field simply consists of two or more other fields. This assumption is logical, but not quite complete. A composite field may consist also of parts of other fields, or one part of one field. A composite field may not be used to place data into a record (via, for example, WRITE, PRINT, or PACK); it is primarily intended for getting data from a record (via, for example, READ, INPUT, or UNPACK), and can be used as a key. A composite field is specified by specifying one or more components separated by "+". Suppose a format string specifies a fixed-length field called FIXEDFLD#. Suppose also that the first variable-length field in the format string is called FIRSTVAR#. In that situation, here are examples of variations allowed in a component of a composite field. The first variant is usually used only to combine two or more fields into one. Variants 2, 3, and 4 are normally used to specify part of a field, although it is permissible to "spill over" into the next field. Variant 5 (not highly recommended) is used to specify part of a record without referring to a particular field at all. Each of these five variants will be discussed in more detail later. Multi-key Files 1) FIXEDFLD# 2) FIXEDFLD# (7) 3) FIXEDFLD# (7) : 5 4) FIRSTVAR# (3) : 5 5) 39 : 6 It is best to view these variants not as complete specifications of composite fields, but as specifications of components of composite fields. To illustrate: 0030 LET FORMAT$="FIELD1# = N5 PRIMARY" 0030: +" FIELD2# = S15" 0030: +" FIELD3# = S10" 0030: +" FIELD4# = FIELD1# + FIELD2# (7)" 0030: +" + FIELD3# (2) : 5" 0030: +" FIELD5# = S12" In this example, FIELD5# will physically follow FIELD3# in each record. FIELD4# does not define a new area in the record; being a composite field, it "composes" its data from other fields or from unnamed regions of the record. Note that in a composite field declaration, a component may not name any variable-length field after the first one. It's easy for the system to compute where the first variable-length field begins, and that location is the same for every record in the file. For other variable-length fields, the location is dependent on the lengths of previous variable-length fields, and so can vary from record to record. Note that there is no indication in these specifications SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg067 whether the component of the composite field is N-, S-, X-, or C-type; all that appears after the colon or the comma is an integer. In practice, all components of a composite field are of type "LEFT S". Using composite fields as components of other composite fields is not permitted. How is an excessively long component (one which overflows into the next field) handled? In most of these examples, there is no verification that the component actually fits in the named field, or even that it fits in the whole record. If the component spills over into the next field, then it is useful to keep in mind how the component will be built. To do so, remember that: -- if the component spills over the end of a fixed-length field, the next byte in the component will normally be the first byte of the next field; -- if the component spills over the end of a variable-length field, the next byte in the component Multi-key Files will normally be a line feed, which will be followed by the first byte of the next field; -- if the component spills over the end of the record (which will end with a line feed if the last field was variable-length), then the remaining bytes of the component will be null (all bits off). Keeping those things in mind, here's a discussion of the above examples: 1) FIXEDFLD# In this example, the component is simply some other field. This is the usual way to combine two fields as the components for a composite field. An example of such a combination is shown in section 3.7.9.4.1.1. 2) FIXEDFLD# (7) In this example the component doesn't consist of all of FIXEDFLD#, but only of that part of it which starts at byte 7. This is similar to the BASIC substring notation in which one can refer to all the bytes after byte 6 of a string by saying STRING$ (7). An error occurs in this example if FIXEDFLD# is fewer than 7 bytes long. 3) FIXEDFLD# (7) : 5 In this example the component doesn't consist of all of FIXEDFLD#, but only of the five bytes beginning at byte 7. There is no requirement that FIXEDFLD# be 11 bytes long, or even 7 bytes long. If it isn't 11 bytes long, then this subfield will extend beyond the end of FIXEDFLD#; if it isn't even 7 bytes long, then this subfield will actually begin beyond FIXEDFLD#. 4) FIRSTVAR# (3) : 5 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg068 This example works the same way as FIXEDFLD# (7) : 5. There is no requirement that FIRSTVAR# be 7 bytes long, or even 3 bytes long. Each component of a composite field must be of fixed length; therefore, FIRSTVAR# (3) won't work, because the length depends on how long FIRSTVAR# itself is. 5) 39 : 6 Suppose the whole record as it is stored on disk were accessible as a BASIC variable called RECORD$. Then this example would define the component as RECORD$ (39,6). There is no requirement that the record be 45 bytes long, or even 39 Multi-key Files bytes long. 3.7.9.4.1.2.5. When Fields Don't Directly Follow Each Other ____ ______ _____ ________ ______ ____ _____ There are two situations in which the actual order of fields in the data record is different from the order in which the fields were specified in the format string. The first situation is the use of a composite field. If a format string contains (perhaps among other items) the following adjacent items: -- a non-composite field -- a composite field -- a non-composite field then the second non-composite field shown above will normally follow the first non-composite field. The second situation is a sort of "multiple viewpoint" of the record. In some contexts it is referred to as "multiple logical record types", and it works as follows: Suppose sometimes the record could be divided into certain fields, but in other situations it would be more appropriate to divide it into different fields, with different names and at different locations in the record. Or suppose that part of the record should always have the same layout but the rest of the record could have one of several layouts depending on what's found in the first part of the record. We might have a record, for example, which looks like this: +---------------+------+-+---+------+ | account # |expire|?| feedback + +---------------+------+-+---+------+ ^| | | |+---+------+ | ^ ^ | | | | | premium | number of copies individual or institution? In this partial example of a record layout for a file of subscribers to a magazine, there is a field which identifies whether the subscriber is an individual or an institution. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg069 Based on that field, either the next field shows details of whether the individual subscriber has sent letters to the editor of the magazine, or the next two fields show how many copies are to be delivered to the institution and what premium to the normal subscription price must be paid by that institution. Multi-key Files There is a way to use the format string to specify this sharing of space in the record. One does this by using an explicit "starting position" on one of the fields, in this case COPIES#. The above (simplified) example might be expressed as follows: 0100 FORMAT$ = "ACCOUNT# = N8 PRIMARY" 0100: +" EXPIRE# = N6 DUPKEY" 0100: +" ACCTTYPE# = C1 DUPKEY" 0100: +" FEEDBACK# = S8" 0100: +" COPIES# = FEEDBACK# : N3" 0100: +" PREMIUM# = +N1.2" What happens in the above format string is that COPIES# does not come after FEEDBACK# in the normal manner; rather, it starts where FEEDBACK# starts. PREMIUM# continues right after COPIES#, following the normal each-field-follows-the- previous-one rule. There are two variations on the previous example. Variation one: COPIES# = FEEDBACK# ( 3 ) : N3 This makes the first byte of COPIES# coincide with the third byte of FEEDBACK#. Variation two: COPIES# = 17 : N3 This makes the first byte of COPIES# coincide with the 17th byte of the whole record. This sort of dead reckoning without using field names is harder to do correctly, and is not recommended. Actually, it is recommended that the practice of overlaying field definitions (as shown in this section) be avoided because it is easier to reorganize a file to change (typically lengthen) fields which have not been overlaid than it is to change fields which share space with other fields. For applications where starting positions are needed, though, there are three additional points to keep in mind. The first point is a minor restriction. If two fields are defined to occupy exactly the same space in each record (whether they are composite or not), they may not ever be both DUPKEY, or both ALTKEY. One of them may be DUPKEY and the other ALTKEY, or both may be NOKEY; all other combinations are valid except for both being ALTKEY or both being DUPKEY. This restriction encourages organization of the file so that writes occur faster, because there are fewer keysets. Multi-key Files SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg070 Also, a field which occupies exactly the same space in each record as the PRIMARY keyset may not be defined to be an ALTKEY keyset. The second point is to differentiate between two kinds of field specification. Suppose we have the above example of a format string, but with one minor change: 0100 FORMAT$ = "ACCOUNT# = N8 PRIMARY" 0100: +" EXPIRE# = N6 DUPKEY" 0100: +" ACCTTYPE# = C1 DUPKEY" 0100: +" FEEDBACK# = S8" 0100: +" COPIES# = FEEDBACK# : 3" 0100: +" PREMIUM# = +N1.2" The difference is that COPIES# is now defined as FEEDBACK# : 3, not FEEDBACK# : N3. If the part of the specification after the ":" is an integer, as it is here, then the field is a composite field (as described in section 3.7.9.4.1.2.4); but if the part after the ":" is an N-, S-, X-, or C-type specification, then the field is not a composite field. In the above example, since COPIES# is a composite field, PREMIUM# is located immediately after FEEDBACK#, and would not be a correct implementation of the diagrammed record layout; but if COPIES# is not a composite field, as in the previous example, then PREMIUM# is located immediately after COPIES#. The third point to keep in mind when using starting positions is the effect that this has on rules concerning variable-length fields. When using a starting position, one usually starts at a fixed point in the record, by using either an integer, a fixed field, or the first variable-length field; if this is so, then even if prior fields in the format string are variable-length, one may now revert to using fixed fields again. When the starting position is fixed like this, then the first variable-length field declared at or after the starting position has a fixed beginning point within the record; so this variable-length field enjoys the same distinctions accorded to the "first variable-length field" as described elsewhere in this document. Suppose, on the other hand, that the starting position is not at a fixed point in the record; that is, it is described in terms of a "non-first" variable-length record. In that case, fields declared at or after the starting position must be variable-length fields, and none of them qualifies as the "first variable-length field". This restriction applies only until a subsequent starting position is specified which refers to a fixed point in the record. Multi-key Files 3.7.9.4.1.2.6. Gaps In The Record ____ __ ___ ______ It is possible to describe areas of the record which are to contain no information whatsoever. It is difficult to describe a situation in which one might want to do such a thing, but for purposes of completeness, we offer the following summary of the syntax of such an unused field: SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg071 FILLER = 39 : 6 FILLER = FIXEDFLD# : 5 FILLER = FIRSTVAR# : 5 FILLER = FIXEDFLD# (7) : 5 FILLER = FIRSTVAR# (3) : 5 Note that "FILLER" is not followed by #. Also note the similarity between these examples and some of the examples in section 3.7.9.4.1.2.4. 3.7.9.4.2. Reading Records From a Multi-Keyed File _______ _______ ____ _ ___________ ____ First we give a few simple examples. Then we go into significant new capabilities such as expanded KEY=, FIELD ALIAS, RETAIN, and UNPACK. 3.7.9.4.2.1. Introductory Examples ____________ ________ Suppose a file has the following format string: F1#=S10 PRIMARY F2#=S5 F3#=S8 F4#=S15 F5#=+N5.2 F6#=S3 F7#=S3 F8#=N3 F9#=S3 ... and suppose that the following READ operation is performed on the file: READ (5) A$, B$, F4#=C$, D, E$, #F8, Q$, #=F3$ Then the following variables receive values from the corresponding fields in the record: Multi-key Files A$ gets its value from F1# B$ gets its value from F2# C$ gets its value from F4# D gets its value from F5# E$ gets its value from F6# F8 gets its value from F8# Q$ gets its value from F9# F3$ gets its value from F3# Note that the fields do not need to be read in the order in which they appear in the record; indeed, not all of the fields need be read. If the IO list contains a variable but does not associate a field name with that variable, this implies that the field to be used is the one that follows (in the format string) the field used for the previous variable in the IO list. If a field name is explicitly shown in an item in the IO list, it causes a new "current field" to be defined, and may alter the field-to-variable correspondences of later items in the IO list. The explicit reference may be in the long SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg072 form (e.g., F4#=C$) or in the short form (e.g., #F8). In the example above, variable D gets its value from field F5# because the previous item in the IO list explicitly named field F4#. Similarly, Q$ gets its value from F9# because the previous item referenced field F8#. Also note that numeric variables must correspond to N-type fields, and string variables must correspond to S-, C-, and X-type fields; an error 17 will result if this correspondence is not maintained. Three equivalent forms of the above READ statement are: READ(5)F1#=A$,F2#=B$,F4#=C$,F5#=D,F6#=E$,F8#=F8,F9#=Q$,F3#=F3$ READ(5) A$, B$,F4#=C$, D, E$, #=F8, Q$, #=F3$ READ(5) A$, B$,F4#=C$, D, E$, #F8, Q$, #F3$ One may place everything after the "READ (5)" in the above READ statement into an IOLIST statement, and instead say: READ (5) IOL=1230 3.7.9.4.2.2. Expanded KEY= Capabilities ________ ____ ____________ When reading using the KEY= clause, one may specify the searching of any field which is either PRIMARY, ALTKEY, or DUPKEY (that is, anything but NOKEY). For example, one may say, "read the record whose key in keyset F1# is 'Jones'" by using the following clause: KEY=F1#="Jones" Multi-key Files Of course, it is also permissible to have the key value in a string variable and use this clause: KEY=F1#=STRING$ If the variable name matches the field name (except for the # at the end of the field name), certain short cuts may be taken. The following examples are equivalent: KEY=F1#=F1$ KEY=#=F1$ KEY=#F1$ These five examples will only work if field F1# is of type S, C, or X, but not N (numeric). If the field is of type N, then the following examples will work, with the last three being identical in effect: KEY=F1#=-987.33 KEY=F1#=PAYMENT KEY=F1#=F1 KEY=#=F1 KEY=#F1 It is also acceptable not to specify the keyset, in which case the PRIMARY keyset is used. Here are two examples: SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg073 KEY="Jones" KEY=-987.33 If one does not use the KEY= clause, then the "next" record is read. Since different keysets place different ordering on the records, the keyset which is used to find the "next" record is the last keyset which was previously used in a KEY= clause, whether that previous KEY= clause was in a REMOVE statement or in a READ statement (or variant such as EXTRACT or READ RECORD). If no KEY= clause has been used for this logical unit since it was opened, then the PRIMARY keyset is used for ordering purposes on sequential reads. 3.7.9.4.2.3. Reading Using FIELD ALIAS _______ _____ _____ _____ Note that field names are hard coded into a BASIC program; that is, there is no way (without using an EXECUTE statement) to input from the user (or compute from scratch) a field name, place it into a string variable, and use that string variable in place of the usual field name. There is, however, a way around this: the FIELD ALIAS statement: 0530 FIELD ALIAS (1,ERR=650) X#=F$, Y#=G$, Z#=H$ ... Multi-key Files If this statement is in the program, one can then have READ statements containing field names X#, Y#, Z#, etc. The actual fields read from the record, however, are not X#, Y#, and Z#; the actual fields have the names which were in F$, G$, and H$ at the time statement 530 was executed. Assuming that the contents of F$, G$, and H$ have not changed since the execution of the FIELD ALIAS statement, the following two statements perform the same action: 8720 READ (1,KEY=X#=A$) Y#=B$, Z#=C$ 8720 EXECUTE "READ (1,KEY="+F$+"=A$) " 8720: +G$+"=B$, " 8720: +H$+"=C$" Note that this example only specifies aliases for unit 1; a READ statement for unit 2 can also refer to field X#, but this will actually pull field X# from the record that's read from unit 2 (if there is such a field), unless a FIELD ALIAS statement naming #X has also been executed for unit 2. A statement such as statement 0530 above can be executed more than once; each time there can be different values in F$, G$, and H$, and each time a subsequent read referring to fields X#, G#, and H# will actually read different fields. An error 17 occurs if any of the following happens: -- reading a numeric field into a string -- reading a field string into a numeric -- performing a FIELD ALIAS where the field name specified in the string doesn't exist in the file to which the specified unit number is open -- performing a FIELD ALIAS where the field name specified in the string isn't even a valid field name SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg074 (including the "#") A more general discussion of the FIELD ALIAS statement is in section 3.7.9.4.10. 3.7.9.4.2.4. RETAIN and UNPACK ______ ___ ______ For every logical unit which is open to a Multi-Keyed file there is a RETAIN buffer. When reading data from fields into BASIC variables, it is possible at the same time (that is, in the same READ statement) to copy the whole record from which those fields come into the RETAIN buffer. Suppose one reads a record into the RETAIN buffer, and then reads one or more records from the same unit without specifying RETAIN for these later read operations. If this is Multi-key Files done, the RETAIN buffer will continue to hold the data from the prior read which specifies RETAIN; the later reads don't change the buffer at all. The RETAIN option is used like this: READ (1,KEY=NEWKEY$,RETAIN) F1#=A$,F2#=X It isn't necessary to use the KEY= clause just because one wants to use the RETAIN clause; they are independent features. Just use each one when it's helpful. After placing the data into the RETAIN buffer, one can pull additional data out of it with the UNPACK statement, which works just like READ except that it pulls the data out of the RETAIN buffer, not out of the file. (Since the system already knows which record is desired, the KEY= clause is not used here.) Example: UNPACK (1,ERR=0970) F3#=B$,F4#=Y 3.7.9.4.2.5. Other Variants On the READ Statement _____ ________ __ ___ ____ _________ READ RECORD works as READ does, except that no fields are specified (except optionally in the KEY= clause), and that the destination is simply a string variable. This reads the record as it's stored on disk, and is of limited usefulness. EXTRACT works just like READ, with two differences: (a) The record will be locked until the next operation on the same logical unit. (b) If the next operation on the same logical unit is a REMOVE, no key is required. See section 3.7.9.4.4 for removing a record. See also section 3.7.9.4.3 for what happens when rewriting an EXTRACTed record in which the PRIMARY key has just been changed. If a DOM= clause is in a READ or READ RECORD statement, it works the same as for DIRECT files; if the specified key is not found, the error branch is taken. If there is no DOM= clause, then an error 11 is generated. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg075 INPUT and INPUT RECORD work exactly the same as READ and READ RECORD do, respectively. 3.7.9.4.3. Writing Records To a Multi-Keyed File _______ _______ __ _ ___________ ____ Most of the discussion here is about differences (syntactically and otherwise) between reading and writing. Multi-key Files In general, the syntax for a WRITE statement is the same as that for a READ. One difference is the same for Multi-Keyed files as it is for other file types: one may write string expressions and numeric expressions, but one may not read into them. The first two items after the ")" in the following example may appear in a READ statement, but not the last four; but all six may appear in a WRITE statement: WRITE (5) F1#=A$,F2#=A,F3#=B$+"123",F4#=3*X,F5#="Now",F6#=98.6 (In this example, the odd-named fields are of type S, C, or X; the even-named fields are of type N.) An IOL= clause, with a corresponding IOLIST statement, may be used here, just as with the READ statement. Do not use a KEY= clause in a WRITE statement to a Multi-Keyed file; the key(s) is (are) generated directly from the record, according to the format string for the file. If a DOM= clause appears in the WRITE statement, then that branch is taken if either the PRIMARY key for the new record matches an already existing PRIMARY key, or an ALTKEY-type key for the new record matches an already existing key in the corresponding keyset. Note that this prevents a record from overwriting a previously existing one with the same PRIMARY key; without the DOM= statement, the overwriting would take place. In order to rewrite a record, it is necessary to execute a WRITE statement without the DOM= clause. The PRIMARY key value of the record being written must match the PRIMARY key value of the record in the file which is to be overwritten. It is not necessary to execute an EXTRACT statement (on the record which is to be overwritten) prior to the WRITE, but the EXTRACT ... WRITE sequence is highly recommended in any case where the file is shared. If, during an EXTRACT ... WRITE sequence, the PRIMARY key value changes before the WRITE, then effectively a brand new record is being written, and the ordinary rules for writing a brand new record will apply. Note that in this situation the record lock will be removed from the old record when the WRITE takes place. When a record is written or rewritten, it may cause duplicate key values to be created in those fields which are defined to be DUPKEY. These duplicate key values are stored in the corresponding keyset along with the other keys with identical values. Further, all of these key entries with the same value are stored chronologically, based on the order in which the SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg076 KEY was added to the file. For example, if a record is Multi-key Files rewritten so that a field to be DUPKEY is changed, the old key value of that field will be removed from the corresponding keyset and the new value will be inserted at the end of all other key sequences with that same value. Therefore, when reading sequentially through that keyset, within a given set of duplicate key values, records will be returned in the order in which the keys were added to the keyset. Note that certain operations do not preserve the chronological ordering of duplicate key values. These operations would include file utilites that alter the number of records in the file (UPDATE on BOSS/VS and fchange on BOSS/IX), reconstruction utilities (DISKANALYZER or RECONSTRUCT on BOSS/VS and frepair on BOSS/IX) and utilites that copy files one record at a time. If the chronological ordering of duplicate key values is to be preserved despite the use of the above-mentioned utilities, or if other orderings are preferred, it is necessary to append a sequencing field to the end of the main field being defined. When this is done, the field need not be defined as DUPKEY and should properly be addressed ALTKEY, because the addition of the sequencing field will cause all key values of the composite to be unique. A FIELD ALIAS statement works for subsequent WRITE statements, just as it does for READ statements. See section 3.7.9.4.2.3. PACK may be used to modify the RETAIN buffer for a logical unit, just as UNPACK may be used to copy fields in the retain buffer into variables. See section 3.7.9.4.2.4. BEWARE, though: a PACK without the RETAIN clause will reinitialize the RETAIN buffer. The following erroneous example will leave just E$ in the buffer: 0530 PACK (1) F1#=A$ 0540 PACK (1) F2#=B$; REM WRONG! 0550 PACK (1) F3#=C$; REM WRONG! 0560 PACK (1) F4#=D$; REM WRONG! 0570 PACK (1) F5#=E$; REM WRONG! Each of the following examples will place all five values into the RETAIN buffer. The one on the left will leave ONLY those values in the buffer; the one on the right will also leave untouched any other fields in the buffer which had values before this example ran: Multi-key Files 0530 PACK(1 )F1#=A$ 0530 PACK(1,RETAIN)F1#=A$ 0540 PACK(1,RETAIN)F2#=B$ 0540 PACK(1,RETAIN)F2#=B$ 0550 PACK(1,RETAIN)F3#=C$ 0550 PACK(1,RETAIN)F3#=C$ 0560 PACK(1,RETAIN)F4#=D$ 0560 PACK(1,RETAIN)F4#=D$ 0570 PACK(1,RETAIN)F5#=E$ 0570 PACK(1,RETAIN)F5#=E$ The example on the left above may be replaced by the first of these two statements, and the example on the right above may be replaced by the second: SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg077 0530 PACK (1 ) F1#=A$,F2#=B$,F3#=C$,F4#=D$,F5#=E$ 0530 PACK (1,RETAIN) F1#=A$,F2#=B$,F3#=C$,F4#=D$,F5#=E$ When the retain buffer contains the record just the way one wants it, one may WRITE using the RETAIN clause: WRITE (1,RETAIN) If the retain buffer contains the record almost the way one wants it, one may modify any desired fields to produce the desired record at the same time one writes the record: WRITE (1,RETAIN) F7#=98.6, #F8$ WRITE RECORD works as WRITE does, except that no fields are specified, and that the source data is simply a string variable. The contents of the string variable are used as the exact contents of the record; the string is considered to be divided into fields as specified in the format string. This feature is of limited usefulness. The RETAIN clause is not allowed on WRITE RECORD. PRINT and PRINT RECORD work exactly the same as WRITE and WRITE RECORD do, respectively. 3.7.9.4.4. Removing Records From a Multi-Keyed File ________ _______ ____ _ ___________ ____ One can remove the record which has a given PRIMARY key like this: REMOVE (1,KEY=A$) Since one cannot remove a record by knowing just the value of a non-PRIMARY key for the record, one should not specify a field name in the REMOVE statement: REMOVE (1,KEY=F1#=A$); REM WRONG! One can remove a record which has been EXTRACTed without specifying the key at all: Multi-key Files REMOVE (1) If the previous operation to this logical unit was not EXTRACT, an error will result and no record will be removed from the file. 3.7.9.4.5. The KEY Function ___ ___ ________ The KEY function will return the next key in the current keyset (that is, the keyset which was last specified in a KEY= clause for this logical unit). The field will be treated as type "S", with trailing nulls removed. This means, for example, that if the current keyset is of type N5.2, and the next value in that keyset is 3.5, then KEY(that unit) is "00003.5". SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg078 3.7.9.4.6. The FID Function ___ ___ ________ The FID function returns a string which contains information exactly like that for a DIRECT file, with two exceptions: (a) The file type is $03$. (b) The key size is the size of the primary key. For information about each field, one must use the FMTINFO function; see section 3.7.9.4.7. 3.7.9.4.7. The FMTINFO Function ___ _______ ________ Suppose a BASIC program is to function as a sort of utility to work with files whose format string is unknown. It uses the FMTINFO function to become acquainted with such a format string. The FMTINFO function takes 1, 2, or 3 parameters. The first parameter is the number of the logical unit which has been opened to the Multi-Keyed file; this parameter is required. The second parameter is optional and is used to specify individual fields or information for all fields if desired. The third parameter, also optional, shows the form in which the program wants the information returned. Suppose we have a file whose format string which was originally formed as follows. (Normally it would not be split into many lines like this, but this arrangement makes it easier to read each field definition). Multi-key Files 0530 FORMAT$ = "F1#=S5 PRIMARY " 0530: + "F2#=N5 ALTKEY " 0530: + "F3#=X5 DUPKEY " 0530: + "F4#=C5 NOKEY " 0530: + "F5#=S5 " 0530: + "G5#=F1#+F2# " 0530: + "F6#=N*10 " 0530: + "F7#=S*20" Suppose further that this file is open on unit 7 and we perform one of the following operations (they're all equivalent): A$ = FMTINFO ( 7 ) A$ = FMTINFO ( 7, 0 ) A$ = FMTINFO ( 7, 0, 0 ) Then A$ will contain the format string in much the same format as it was originally defined (and as it may have been altered by the SETFIELD operation as described in section 3.7.9.4.9). A$ will all be one string, but for purposes of easy reading, we break it up into several pieces, as follows: "F1#=S5 PRIMARY " "F2#=N5 ALTKEY " "F3#=X5 DUPKEY " "F4#=C5 " "F5#=S5 " "G5#=F1#+F2# " "F6#=N*10 " "F7#=S*20" SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg079 Note that two spaces separate each adjacent field description, and that there are no other occurrences of two adjacent spaces in the format string. Also note that the specification of "NOKEY" for F4# has disappeared; the meaning, however, is the same. Suppose that we change the call to FMTINFO as follows: A$ = FMTINFO ( 7, 0, 1 ) Then A$ will contain the format string in a form which is much easier for a BASIC program to read. In hex, the contents of A$ are as follows: 2010 1020 2230 2100 2000 F000 5000 6000 Each field is described by two bytes. In the following discussion of the contents of these two bytes, "x" means four bits which may contain anything, and are not guaranteed to contain zero. Multi-key Files The first byte shows what the field type is. The allowable values are: $1x$ "N" (fixed length) $20$ "S" (fixed length) $21$ "C" (fixed length) $22$ "X" (fixed length) $5x$ "N*" (variable length) $6x$ "S*" (variable length) $Fx$ a composite field The second byte shows what the key type is. The allowable values are: $0x$ NOKEY (not a key) $1x$ PRIMARY $2x$ ALTKEY $3x$ DUPKEY The most convenient formula for the number of fields defined in the file is the following: 3280 A$ = FMTINFO ( 7, 0, 1 ) 3290 NUMFLDS = LEN(A$)/2 The remaining variations simply allow one to access individual field definitions. The following code: 5500 FOR I = 3 TO 4 5510 A$ = FMTINFO ( 7, I, 0 ) 5520 B$ = FMTINFO ( 7, I, 1 ) 5530 PRINT "'",A$,"'" 5540 PRINT HTA(B$) 5550 NEXT I will produce the following output (keeping in mind that in each case the last four bits of B$ are not guaranteed): SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg080 'F3#=X5 DUPKEY' 2230 'F4#=C5' 2100 If the third argument to FMTINFO is 0, it may be omitted. The following variations are identical: A$ = FMTINFO ( 7, 3, 0 ) A$ = FMTINFO ( 7, 3 ) The following forms are also allowed, and identical: Multi-key Files A$ = FMTINFO ( 7, SOCIALSN#, 0 ) A$ = FMTINFO ( 7, SOCIALSN# ) If a BASIC program is reading field names from a terminal, FMTINFO can be used in combination with FIELD ALIAS to obtain information (for example, is this field numeric? does it have a keyset?) about the field whose name has just been typed: 0040 INPUT "Enter the field name: ", F$ 0050 IF F$ = "" GOTO 40 ELSE IF F$(LEN(F$)) <> "#" 0050: THEN F$=F$+"#" 0060 FIELD ALIAS (5,ERR=80) X#=F$ 0070 GOTO 100 0080 PRINT "No such field" 0090 GOTO 40 0100 INFO$ = FMTINFO (5,X#,1); (now look at INFO$ for the information) A more general discussion of the FIELD ALIAS statement is in section 3.7.9.4.10. 3.7.9.4.8. INITFILE ________ The following statement, when used for a Multi-Keyed file, removes all the records from the file, but keeps the format string unchanged; even though SETFIELD operations may have been performed on the file since it was first created, these operations are not undone by the INITFILE statement. 0730 INITFILE "FILE",ERR=0900 The ERR= clause is optional. 3.7.9.4.9. SETFIELD ________ It is possible to change a fixed-length or composite field from one to another of these key types: NOKEY, ALTKEY, DUPKEY. The statement looks like this: SETFIELD "FILE",FMT="FIELD3#=DUPKEY",MSG="Progress: " ,ERR=1230 The MSG= and ERR= clauses are optional. The file must not currently be open by anyone. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg081 The PRIMARY field may not be changed to any other keyset type; no other field may be declared as PRIMARY. An error will occur if changing a field from NOKEY or DUPKEY Multi-key Files to ALTKEY if two or more records have the same data in the specified field; this would generate duplicate keys. The MSG= clause, if present, specifies that a message should be displayed on the terminal, followed by a running percentage-complete tally. At the end of the operation, this tally will show 100%. If the clause is omitted, the percentage-complete tally will not show. The message will be displayed at the screen's current cursor position, unless a new one is specified as in this example: MSG=@(65,20)+"Progress: " It is permissible (but not terribly useful, except in a situation where generality is desired) to change a field from ALTKEY to ALTKEY, from DUPKEY to DUPKEY, and from NOKEY to NOKEY. 3.7.9.4.10. FIELD ALIAS _____ _____ Suppose that a BASIC programmer is working with a multikeyed file and doesn't want to hard code the field names into his program. This might happen if the end user of the program will be typing field names at the terminal, or if the program computes the field names (F001#, F002#, etc.). How can the BASIC programmer deal with this situation? Here are two solutions, which are not recommended, followed by the one that is. Solution number one: The BASIC programmer writes a separate BASIC statement for each field name which might be used there. Example: 0550 IF F$ = "APPLES#" THEN 0550: READ ( 1, KEY=APPLES#=G$ ) A$, B$, C$ ELSE 0550: IF F$ = "ORANGES#" THEN 0550: READ ( 1, KEY=ORANGES#=G$ ) A$, B$, C$ ELSE 0550: IF F$ = "BLUES#" THEN 0550: READ ( 1, KEY=BLUES#=G$ ) A$, B$, C$ ELSE ... That solution would be cumbersome and hard to maintain. Solution number two: 0550 EXECUTE "READ ( 1, KEY="+F$+"=G$ ) A$, B$, C$" That solution is far less cumbersome, but runs too slowly. The penalty is high enough for the EXECUTE statement, but is even greater on BOSS/IX systems than on BOSS/VS: In BOSS/IX systems, as soon as a BASIC program performs its first EXECUTE Multi-key Files SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg082 statement, the whole program from then on slows down significantly. This brings us to the real solution: 0210 FIELD ALIAS ( 1, X#=F$) 0550 READ ( 1, KEY=X#=G$ ) A$, B$, C$ Statement 210 says the following: From this point on, whenever performing operations on unit 1, which is opened to a multikeyed file, if field X# is specified, the field actually desired is the field in F$ as of the time this statement (statement 210) is executed. This is to be effective until (a) some other FIELD ALIAS on the same unit number (1 in this case) and the same alias name (X# in this example, not the contents of F$) is performed, or (b) the unit (unit 1 in this example) is CLOSEd. It is important to remember that the FIELD ALIAS is performed on whatever expression is on the righthand side of the equals sign as of the time of execution of the FIELD ALIAS statement. For example: 7700 A$ = "BROWN#" 7710 FIELD ALIAS ( 1, J# = A$ ) 7720 A$ = "GREEN#" 7730 READ ( 1, KEY=J#=B$) X$, Y$, Z$ ... will read using field BROWN#, not field GREEN#. FIELD ALIAS can be used for more than READ statements; in fact, it can be used effectively in any statement containing a field name, except (of course) another FIELD ALIAS statement. For examples of FIELD ALIAS usage, see the following sections: 3.7.9.4.2.3 3.7.9.4.7 (near the end) 3.7.9.5 3.7.9.4.11. Miscellany __________ The syntax for the OPEN and CLOSE statements is the same for Multi-Keyed files as it is for other file types. Neither the IND function nor the IND= clause is allowed in Multi-key Files operations on Multi-Keyed files. If an error occurs while defining a Multi-Key file due to format string errors, the function TCB(14) can be used to get the approximate position of where in the format string the error occurred. This is an approximate position and the error SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg083 will be close by. 3.7.9.5. Sample Programs ______ ________ The following three programs illustrate the sort of use to which Multi-Keyed files can be put. They don't use all the facilities; if they did, they would be less readable and more contrived. They do use a fair number of the facilities, however, and give a good flavor for the flexibility of Multi-Keyed files. All programs work with the same file. The record layout is as follows: +-----+--------+----------------+------------------+----+ | N5 | N9 | S16 | S20 | N4 | +-----+--------+----------------+------------------+----+ ^ ^ ^ ^ ^ | | | | | | | first name last name | | social security number department number employee number +----------------------------------+ ^ | full name (last name first) Within each box in this diagram, "N" means "numeric", "S" means "string", and the number shows how many bytes are reserved for the field. For more information, see section 3.7.9.4.1.2. The layout of the record is described by the format string shown in this statement: 0030 LET FORMAT$="EMPLNUM# = N5 PRIMARY" 0030: +" SOCIALSN# = N9 ALTKEY" 0030: +" FRSTNAME# = S16" 0030: +" LASTNAME# = S20" 0030: +" FULLNAME# = LASTNAME#+FRSTNAME# DUPKEY" 0030: +" DEPTNUM# = N4 DUPKEY" EMPLNUM# is the employee number. It is a numeric field, and has been designated the PRIMARY key because the employee Multi-key Files number is the principal means of identifying each record in the file (that is, identifying each employee in the company). When a record is deleted, for example, it is the employee number which will be used to identify the record, not the social security number or the last name of the employee. Note that the PRIMARY keyset of a file may never have duplicate values; in this case, no two employees will have the same employee number. SOCIALSN# is the social security number. It is a numeric field, and has been declared to be ALTKEY; a keyset will be maintained using this field, so that employee records may be accessed directly by social security number. Should the need arise, the keyset may also be used to print the records so SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg084 that the social security numbers are in order. Since this field is ALTKEY, not DUPKEY, duplicate values are not allowed in this field; no two employees are allowed to have the same social security number. FRSTNAME# is the employee's first name. It is a string (non-numeric) field. It has not been declared to be PRIMARY, ALTKEY, or DUPKEY; therefore this field is of type NOKEY, and as it exists can never be used to access records directly by employee's first name ("give me Fred's record") or list the records in order of first name. LASTNAME# is the employee's last name; like FRSTNAME#, it is a string field, and is of type NOKEY. FULLNAME# is a combination of FRSTNAME# and LASTNAME#, and is therefore called a "composite" field. It has been declared to be DUPKEY; a keyset will be maintained using this field, so that employee records may be accessed directly using first and last name. ("Get me the records for all Fred Smiths in this company.") Should the need arise, the keyset may also be used to print the records in alphabetical order, last name first. "Last name first" means that Fred Smith comes after Jim Jones, but if the record is printed as it appears in the file, the first name will appear before the last name on the listing. Since this field is DUPKEY, not ALTKEY, duplicate values are allowed in this field; there may be two Fred Smiths working for the company. DEPTNUM# is the number of the department to which the employee belongs. It is a numeric field, and has been declared to be DUPKEY; a keyset will be maintained using this field, so that employee records may be accessed directly using the department number. ("Get me the records for all employees in department 1099.") Should the need arise, the keyset may also be used to print the records of all employees, ordered by department number. This field is DUPKEY, not ALTKEY; otherwise, it would not be possible to have any department contain more than one Multi-key Files employee, which causes more than one record to contain the same department number. The three programs which follow are designed more for easy reading than for user friendliness. The first one prints a report showing all the records in the file, ordering them by any field, even if that field is currently declared NOKEY. The second one allows a user to update records which are already in the file. The third one shows how to create the file in the first place, converting from a DIRECT or SERIAL file. 3.7.9.5.1. Printing a Multi-Keyed File ________ _ ___________ ____ This program lists the whole file, in order by any field in the file. If there is no keyset for the field yet, it produces one, lists the file, and then deletes the keyset. (Note that in real life no new keyset could be added if anyone had the file open.) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg085 Lines 0120, 0130, 0140, 0170, and 0180 show how FMTINFO can be used to find out information about an otherwise unfamiliar field. To see how these statements do what they do, see section 3.7.9.4.7. 0010 REM "PRINT THE FILE IN A SPECIFIED ORDER" 0020 BEGIN 0030 OPEN (1)"EMPLOYEES" 0040 INPUT "On which field should we sort the file? ", F$ 0050 IF F$ = "" GOTO 40 ELSE IF F$(LEN(F$)) <> "#" 0050: THEN F$=F$+"#" 0060 FIELD ALIAS (1,ERR=80) X#=F$ 0070 GOTO 100 0080 PRINT "No such field" 0090 GOTO 40 0100 REM "Position at the beginning of 0100: the requested keyset" 0110 REM "First we must ask: is there a keyset already? 0120 INFO$ = FMTINFO (1,X#,1) 0130 FLDINFO = INT(ASC(INFO$(1,1))/16) 0140 KEYINFO = INT(ASC(INFO$(2,1))/16) 0150 IF KEYINFO <> 0 GOTO 270 0160 FLDNAME$ = FMTINFO (1,X#,0) 0170 FLDNAME$ = FLDNAME$ (1,POS("#"=FLDNAME$)) 0180 CLOSE (1) 0190 SETERR 220 0195 PRINT "Please wait for keyset generation.", 0200 SETFIELD "EMPLOYEES",FMT=FLDNAME$+"=DUPKEY",MSG=" " 0205 PRINT 'LF',"Generation complete." 0210 GOTO 240 0220 PRINT 'LF',"Couldn't create a keyset for this field" 0230 SETERR 0; GOTO 30; REM "We must reopen the file" Multi-key Files 0240 SETERR 0; REM "We didn't catch an error from line 0240: 0190 onward." 0250 OPEN (1)"EMPLOYEES"; 0260 FIELD ALIAS (1,ERR=80) X#=F$ 0270 REM "This field has a keyset; is this field numeric 0270: or string?" 0280 IF FLDINFO <> 1 GOTO 320 0290 REM "Position at beginning of numeric keyset" 0300 EXTRACT (1,KEY=X#=0) 0310 GOTO 330 0320 REM "Position at beginning of string keyset" 0325 EXTRACT (1,KEY=X#="") 0330 OPEN (2)"P*" 0340 PRINT (2)"EMPLNUM#", 0340: (11),"SOCIALSN#", 0340: (21),"FRSTNAME#", 0340: (41),"LASTNAME#", 0340: (62),"DEPTNUM#" 0350 PRINT (2)"" 0360 READ (1,END=390) #EMPLNUM, #SOCIALSN, #FRSTNAME$, 0360: #LASTNAME$, #DEPTNUM 0370 PRINT (2) EMPLNUM:"00000", 0370: (11), SOCIALSN:"000000000", 0370: (21), FRSTNAME$, 0370: (41), LASTNAME$, 0370: (62), DEPTNUM:"0000" 0380 GOTO 360 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg086 0390 CLOSE (1) 0400 CLOSE (2) 0410 IF KEYINFO = 0 THEN SETFIELD "EMPLOYEES", 0410: FMT=FLDNAME$+"=NOKEY" 0420 END 3.7.9.5.2. Updating a Multi-Keyed File ________ _ ___________ ____ This program updates a Multi-Keyed file, field by field. As with the other sample programs, most of the human engineering aspects have been grossly neglected, so that the essentials of handling Multi-Keyed files could be seen as plainly as possible. 0010 REM "UPDATE A SINGLE FIELD" 0020 BEGIN 0030 OPEN (1)"EMPLOYEES" 0040 INPUT "Employee number: ",EMPLOYEE 0050 IF EMPLOYEE = 0 THEN END 0060 EXTRACT (1,KEY=EMPLOYEE,RETAIN,DOM=80) 0070 GOTO 100 0080 PRINT "No such employee number" 0090 GOTO 40 0100 INPUT "Field name: ",FLDNAME$ Multi-key Files 0105 REM " means no more field changes; 0105: rewrite record" 0110 IF FLDNAME$="" THEN WRITE (1,RETAIN); GOTO 40 0120 IF FLDNAME$(LEN(FLDNAME$))<>"#" THEN 0120: FLDNAME$=FLDNAME$+"#" 0125 IF FLDNAME$ = "EMPLNUM#" THEN 0125: PRINT "Can't change employee number"; GOTO 100 0130 FIELD ALIAS (1,ERR=150) X#=FLDNAME$ 0140 GOTO 170 0150 PRINT "No such field" 0160 GOTO 40 0170 INFO$=FMTINFO(1,X#,1) 0180 FLDINFO = INT(ASC(INFO$(1,1))/16) 0190 IF FLDINFO = 1 GOTO 270 0200 UNPACK (1) X#=VALUE$; REM "from the RETAIN buffer" 0210 PRINT "Current value: ",VALUE$ 0220 IF FLDINFO = 15 GOTO 100; 0220: REM "Can't rewrite composite fields" 0230 INPUT "New value: ",VALUE$ 0240 IF VALUE$="" GOTO 100; 0240: REM "Doesn't want to change the field" 0250 PACK (1,RETAIN) X#=VALUE$ 0260 GOTO 100 0270 REM "Numeric value" 0280 UNPACK (1) X#=VALUE; REM "from the RETAIN buffer" 0290 PRINT "Current value: ",STR(VALUE) 0300 INPUT "New value: ",VALUE$ 0310 IF VALUE$="" GOTO 100; 0310: REM "Doesn't want to change the field" 0320 PACK (1,RETAIN) X#=NUM(VALUE$,ERR=340) 0330 GOTO 100 0340 PRINT "Invalid numeric value" 0350 GOTO 290 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg087 3.7.9.5.3. Loading Data Into a Multi-Keyed File _______ ____ ____ _ ___________ ____ This program is fairly straightforward; it initializes the file and does a record-by-record transfer into it. 0010 REM "CONVERT TO MULTIKEYED FILE" 0020 BEGIN 0030 LET FORMAT$="EMPLNUM# = N5 PRIMARY" 0030: +" SOCIALSN# = N9 ALTKEY" 0030: +" FRSTNAME# = S16" 0030: +" LASTNAME# = S20" 0030: +" FULLNAME# = LASTNAME#+FRSTNAME# DUPKEY" 0030: +" DEPTNUM# = N4 DUPKEY" 0040 MULTI "EMPLOYEES",200,FMT=FORMAT$ 0050 OPEN (1)"OLDDATA" 0060 OPEN (2)"EMPLOYEES" 0070 READ (1,END=0100) EMPLNUM,SOCIALSN, FRSTNAME$, Multi-key Files 0070: LASTNAME$, DEPTNUM 0080 WRITE (2) #EMPLNUM,#SOCIALSN,#FRSTNAME$,#LASTNAME$, 0080: #DEPTNUM 0090 GOTO 70 0100 CLOSE (1) 0110 CLOSE (2) 0120 END 3.7.9.6. Conversion of Existing Applications __________ __ ________ ____________ The following points should be considered when planning a conversion of an existing application program from using Direct and Sort files to the use of Multi-Keyed files. 3.7.9.6.1. Selection of Appropriate Candidate _________ __ ___________ _________ Some applications will benefit greatly from conversion to Multi-Keyed file use. The most obvious candidates are those that currently emulate Multi-Keyed file functionality. Other types of applications would benefit less or not at all and would not warrant changing. 3.7.9.6.2. Conversion Approaches __________ __________ When considering the modification of an existing application program to the use of Multi-Keyed files, the first decision that must be made is how much modification will be required. For some programs, a straight-forward substitution approach may be taken. For others, modification may be impractical and redesigning and rewriting the application or portions of it may be required. To make this determination, the application programmer would have to analyze the complexity of the existing application and the difficulty in isolating the references to the individual files that make up the user data base. 3.7.9.6.3. Selection of Keysets _________ __ _______ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg088 When designing the characteristics of a Multi-Keyed file, one of the most important decisions to be made is the selection of which fields will become keysets. A good starting point is to define the primary key of the Multi-Keyed file to be the same field as was used to reference the Direct file and define alternate keysets (either ALTKEY or DUPKEY) for each of the Sort files. During the conversion design process, it may be determined that there are other fields that should also be keyed to allow access to the data in ways that were not possible before. At the same time, it must be remembered that Multi-key Files each keyset that is maintained as a permanent part of the file will increase the overhead required for modifications to the file. Therefore, a subset of the keysets defined as useful may be designated as temporary keysets that will be added to the file only when necessary. 3.7.9.6.3.1. Selection of Fields Which Should Not Be Permanent Keysets _________ __ ______ _____ ______ ___ __ _________ _______ Not all fields which would be useful to have as keysets should be made into "permanent" keysets. If a field is used as a means of locating records very infrequently, it is usually inappropriate to include it as one of the standard keysets. For example, suppose a monthly report is required that selects records from an Employee file based on a field (EXEMPT#) which indicates whether or not the employee is salaried. If the EXEMPT# field were keyed, then it could be used to facilitate the selection of records. However, the fact that the report is required only monthly, presuming the field is not used as a key for other purposes, would argue against defining this field as a keyed field for the entire month. 3.7.9.6.3.2. Selecting Records Based on Non-Keyed Fields _________ _______ _____ __ _________ ______ If a field is required as an access path only infrequently, several options are available for handling such cases. The easiest solution is to make the field into a keyed field when necessary with the use of the SETFIELD directive. Once the field is a keyed field, it may be used normally to select records. Sometimes, however, it is impractical to perform the SETFIELD operation because that operation requires that the file be unused at the time. In this case, it may be necessary to process all of the records in the file, selecting only those records that satisfy the selection criteria. If the output is to be in order by a non-keyed field, an intermediate file should be created with all of the selected records and then that file, on BOSS/VS, could be sorted using the Sort utility. On BOSS/VS, the Sort utility could be used to sort the entire Multi-Keyed file on the contents of a non-keyed field. This technique would be appropriate if the character positions being sorted on had not been defined as a field within the Multi-Keyed file format. The Sort utility has the same restriction as the SETFIELD operation, in that the file must not be used by others at the time of the sort. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg089 Multi-key Files 3.7.9.6.4. Suggestions for Conversion ___________ ___ __________ 3.7.9.6.4.1. Data Layout Diagrams ____ ______ ________ A pictorial representation of the fields within the data record will facilitate the design of the data records within a Multi-Keyed file. It is useful to have a picture of the layout of the data records within the Direct file as well as the layout of the new record(s). This is especially helpful if the record design contains more than one logical record (record type). It is important to define as fields any combination of character positions that might at some point be used as a keyset. Fields that are not initially defined to be keyed may be converted into keyed fields (either ALTKEY or DUPKEY) by using the SETFIELD directive. However, new fields may not be added to a format once the file has been created, making it important to anticipate future needs. When planning the field layout for the Multi-Keyed file, the field for the primary key must be defined. This is important because the field may not have been part of the data record of the Direct file. Similarly, Sort file key values may not have been part of the Direct data record, but must be included in the Multi-Keyed file key. Having a pictorial representation will make it easier to deal with some of the special considerations described below. 3.7.9.6.4.2. Field Separator Characters _____ _________ __________ It is important to remember the field separator characters. These will be present between fields of the Direct file record. Because the logical structure of the records within a Multi-Keyed file is described in the Format string, field separator characters are not required and are not included in the physical data records. In order to eliminate field separator characters when converting a Direct file to a Multi-Keyed file, a BASIC program should be written that READs records from the Direct file using the standard IOLIST and WRITEs each record to the Multi-Keyed file also using an IOLIST. An example of such a program is shown in section 3.7.9.5.3. The IOLIST used for output might be slightly different from the IOLIST used for input (see the next section for one example). The field separator characters in the input data record will be used to assign data to BASIC variables, but will not be included in the output data record. Multi-key Files 3.7.9.6.4.3. Subfields _________ Subfields, for the purpose of this discussion, are sequences of characters that are defined as substrings of other fields. For example, if field 'PHONUM' (phone number) is a 10 character string, it might consist of two subfields: PHONUM SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg090 (1,3) (area code) and PHONUM (4,7) (local number). In order to use the subfields, the characters must be extracted by substring reference from the larger field. Subfields are allowed on either Direct or Multi-Keyed files. If subfields are present in the Direct file and they are to be eliminated in the Multi-Keyed file (so that each subfield becomes a field that can be referenced explicitly without a substring reference to another field), there are two possible approaches. The first (and preferred) solution is to READ the input record into an IOLIST which specifies a variable for the larger field; then extract the subfields into other variables; finally to WRITE the subfield variables to the Multi-Keyed file as part of the IOLIST. To clarify this using the example above, first READ the record specifying a variable, PHONUM$ to hold the entire 10 digit number. Then separate the parts into individual variables. Finally, write the record to the Multi-Keyed file specifying both AREA$ and PHONE$ in the IOLIST: READ (1) A, B, ..., PHONUM$, ... AREA$ = PHONUM$ (1,3) PHONE$ = PHONUM$ (4,7) WRITE (2) A, B, ..., AREA$, PHONE$, ... The second approach would be to define a new field in the Multi-Keyed file format string which overlaid all of the subfields (which had been described as separate fields in the new record). For example: MKFORM$ = "... AREA# = S3 PHONE# = S7 PHONUM# = AREA#: S10" Here, the field PHONUM# overlays the previous two fields. To convert a record using this technique, the data would be READ the same way as in the first approach, but the subfields would not be extracted. Instead, the larger field would be written to the Multi-Keyed file specifying the redefined field name: READ (1) A, B, ..., PHONUM$, ... WRITE (2) A, B, ..., PHONUM#=PHONUM$, ... After writing the record this way, the parts of the phone Multi-key Files number may be referenced by name (AREA# and PHONE#) or the whole field may be referenced by the name of the redefined field (PHONUM#). The ability to reference a combination of fields by a single name can be desirable, but the addition of overlaid fields implies a more complicated record structure than really exists. Note that the use of a composite field instead of an overlay field would not work because of the restriction that composite fields may not be included in the IOLIST for a WRITE. The use of overlaid fields is not recommended. 3.7.9.6.4.4. The WriteThru File Attribute on BOSS/VS ___ _________ ____ _________ __ _______ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg091 To speed up the conversion of a Direct file into a Multi-Keyed file, it is important to set the WriteThru attribute for the Multi-Keyed file to False. This will have no effect if the system-wide WriteThru parameter is set to True, so it may be necessary to change the system-wide parameter also. Once the conversion is complete, the WriteThru attribute on the Multi-Keyed file should be reset to True to improve recoverability of the file when it is in use. 3.7.9.6.4.5. Definition of Keysets for Conversion __________ __ _______ ___ __________ Another technique for speeding up the conversion of a Direct file is to set up the format string for the Multi-Keyed file to define all of the fields but only one keyset (the primary keyset is required). This will accelerate the WRITEs to the new file. After all records have been converted (written to the new file) the other keysets should be added using the SETFIELD directive. This operation uses a more efficient technique to build the other keyset structures. 3.7.9.7. Recovery of Multi-Keyed Files on BOSS/VS ________ __ ___________ _____ __ _______ This section deals with issues that arise when a system failure causes a Multi-Keyed file to "lack integrity". Because the internal structure of Multi-Keyed files are more complicated than those of other file types, some of the integrity characteristics and recovery techniques are different and require special attention. 3.7.9.7.1. Ways to repair Multi-Key Files ____ __ ______ _________ _____ After a system crash or other problem that leads to a re-loading of the system, the system administrator is concerned with providing access to the system data base as Multi-key Files quickly as possible, while guaranteeing the integrity of that data base. The sequence of steps covered in the following section describes the quickest way to reestablish the integrity of the user data base. The major steps involve repairing or reconstructing files. There are two tools available to reconstruct files: Diskanalyzer and the Reconstruct utility (not to be confused with the Validation/Reconstruction option within Diskanalyzer). Both will reconstruct a keyed file that lacks integrity, but they each use different techniques and have different limitations and applications. Specifically, the Reconstruct utility operates much more quickly than does Diskanalyzer, but its limitations are that it may require more disk space than Diskanalyzer and it may not be able to recover all files that Diskanalyzer can recover. 3.7.9.7.2. File Recovery Sequence ____ ________ ________ The recommended sequence of operations for recovery of user files is: SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg092 1) On the system load immediately following a system failure, the system operator should select type 2 load. This provides a single-user environment in which to verify and correct certain problems. The Diskanalyzer option 5, "DISK SPACE USAGE", should then be selected and run on each family to verify that the system files are intact. If this operation reports any errors, the user must immediately take steps to correct the errors. There steps are as follows: a) Reconstruct the Directory of the family(ies) that received errors using the Diskanalyzer option "Reconstruct Directory File" (option 10). b) Reconstruct the available space file for each member of the family(ies) affected using the option "Reconstruct Available Space Files" (option 9). c) Select and run option 5 again to verify that the problems detected have been corrected. 2) Run Diskanalyzer option 1, "Find All Files That Lack Integrity". The list of files that this option generates will be used in subsequent steps. This procedure can be run while still under type 2 load. 3) At this point it will be necessary to re-load the system under type 1 load in order to use the Reconstruct utility. If normal access to files must be avoided because there are files that lack integrity, steps must be taken to inform or prevent users from Multi-key Files restarting their work. With the new 8.6 release, this can be accomplished with the job manager GROUP enable initial command. Suggestions on how to control access to the system through the startup procedures are contained in the System Startup Overview document. 4) Run the Reconstruct utility to reconstruct all keyed files that lack integrity - using the output of step 2 to select the files. 5) Use the Diskanalyzer Validate/Reconstruct option to reconstruct those files which either are not keyed files (e.g. Serial or Indexed files) or are damaged in such a way that the Reconstruct utility fails to recover them. 6) Finally, if after steps 1 through 5 have been performed and there are problems with starting up the application that seem to be attributable to file corruption problems, the customer may be advised to take other, more time consuming steps such as running the Diskanalyzer option "Validate All Files", validation of specific files or, depending on the circumstances, restoration of files from the most current backup. 7) When recovery of all files is complete, including any renaming that must be done following the use of the Diskanalyzer reconstruction option, access to the SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg093 system by others can be allowed. If access to the system was prevented by not enabling the terminal groups (using the Job Manager) it can be restored by enabling them at this time. As can be seen from the sequence above, the reconstruction of a Multi-Keyed file using the Diskanalyzer option is not recommended until after the Reconstruction utility has been tried and has failed. The validation of all files or the validation of a specific file is recommended only in the unusual circumstance that the other recovery mechanisms fail. 3.7.9.8. Multi-Key Transport _________ _________ Multi-Key files are fully transportable between like systems, which contain operating system which support Multi-Key files, using standard tape utilities. However, standard tape utilities do not support transportation between BOSS/VS and BOXX/IX. There some methods that can be used to transport multi-keyed files between BOSS/VS and BOSS/IX. One method is to convert the multi-key file to another file format which is transportable and then convert it back to a multi-key file Multi-key Files once it has been transported. This method is very easy to implement but also requires disk space to hold the converted file. Another method is to write to directly to tape. Since the MCS cartridge cannot be accessed from BASIC, the MTS must be used on both systems. This method is a little more complicated to code and will result is a slower transfer but it doesn't require the disk space that the first method does. Below is a listing of a program that will convert a multi-key file to a serial file and vice-versa. This program is presented as an example on how to convert multi-keyed files to another file type. The program is fairly self-documenting. The program determines from the type of the specified source file which direction the file will be converted (serial to multi-key or vice-versa). The file can be found under the node ".R6Axxx.UNSPRTD.". ___________________________________________________________________________ 0010 REM " M I R T H " 0020 REM "This program will convert multi-key to serial and vice-versa" 0030 REM "to allow transportation between BOSS/VS and BOSS/IX. " 0040 REM 0050 PRINT 'CS',(35,0),'BR'," MIRTH ",'ER', 0060 SETESC 09900;SETERR 07000 0070 REM 0080 REM "Get filenames and file statistics" 0090 REM 0100 GOSUB 04000 0110 IF TY$="" THEN GOTO 09900 0120 IF TY$="SER" THEN GOTO 01000 0130 REM 0140 REM "*************************************************************" 0150 REM "* *" SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg094 0160 REM "* Multi-key to serial conversion *" 0170 REM "* *" 0180 REM "*************************************************************" 0190 REM 0200 REM "Convert multi-key file to serial file. " 0210 REM "First, lets define the serial file (erase any existing " 0220 REM "serial file). " 0230 REM 0240 ERASE DFN$,ERR=00250 0250 SERIAL DFN$,NUMREC,RECSIZE,ERR=00260;GOTO 00290 0260 E$="ERROR: Error "+STR(ERR)+" occured while defining serial 0260: file '"+SFN$+"'";GOSUB 06000;GOTO 00070 0270 REM 0280 REM "Now, lets do the copy from the multi-key to the serial " 0290 REM 0300 OPEN (2)DFN$;LOCK(2) Multi-key Files 0310 REM 0320 REM "Format the screen for copy." 0330 REM 0340 GOSUB 05000 0350 REM 0360 REM "The first record written to the serial file will be the format" 0370 REM "string of the multi-key file. " 0380 REM 0390 FORMAT$=FMTINFO(1,0) 0400 WRITE RECORD(2)FORMAT$ 0410 REM 0420 REM "Lets now copy the records from the multi-key to the serial " 0430 REM 0440 READ RECORD (1,END=00480)REC$ 0450 WRITE RECORD(2)REC$ 0460 PRINT (37,10),INT((CURREC/NUMREC)*100)," ", 0470 CURREC=CURREC+1;GOTO 00440 0480 REM 0490 REM "End of copy,prompt for CR and return to main menu." 0500 REM 0510 CLOSE (1);CLOSE(2);E$="Copy complete ";GOSUB 06000;GOTO 00070 1000 REM 1000 1010 REM "**************************************************************" 1020 REM "* *" 1030 REM "* Serial to multi-key conversion *" 1040 REM "* *" 1050 REM "**************************************************************" 1060 REM 1070 REM 1080 REM "Create multi-key file. To do this, we need the format string. " 1090 REM "We get the format string from the first record in the serial " 1100 REM "file." 1110 REM 1120 READ RECORD (1,ERR=01130)FORMAT$;GOTO 01150 1130 E$="Error "+STR(ERR)+" in reading format string";GOSUB 06000 1140 GOTO 09900 1150 ERASE DFN$,ERR=01160 1160 MULTI DFN$,NUMREC,FMT=FORMAT$,ERR=01170;GOTO 01190 1170 E$="ERROR: Error "+STR(ERR)+" in defining multi-key file";GOSUB 1170:06000 1180 GOTO 09900 1190 REM 1200 REM "Multi-key has been defined, just copy the records to the file." SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg095 1210 REM 1220 OPEN (2)DFN$ 1230 REM 1240 REM "Format the screen for the copy. " 1250 REM 1260 GOSUB 05000 1270 REM 1280 REM " Do the copy from serial to mulit-key. " 1290 REM Multi-key Files 1300 READ RECORD (1,END=01350)REC$ 1310 WRITE RECORD(2)REC$ 1320 CURREC=CURREC+1 1330 PRINT (37,10),INT((CURREC/NUMREC)*100)," ", 1340 GOTO 01300 1350 REM 1360 REM "End of serial to multi-key copy. Prompt user for CR and return " 1370 REM "to main menu. " 1380 REM 1390 E$="Copy complete ";CLOSE(1);CLOSE(2);GOSUB 06000;GOTO 00070 4000 REM 4000 4010 REM "This subroutine prompts the user for the source file name and " 4020 REM "destination file name. The destination file opened, it type " 4030 REM "is checked for the proper types (SERIAL or MULTI) and the " 4040 REM "necessary file attributes are retreived. " 4050 REM 4060 PRINT (0,1),'CE', 4070 INPUT (0,ERR=04070) (20,5),'CL',"Source file name: ",SFN$ 4080 IF SFN$="" THEN TY$="";RETURN 4090 INPUT (0,ERR=04090)(20,7),'CL',"Destination file name: ",DFN$ 4100 OPEN (1,ERR=04110)SFN$;LOCK(1);GOTO 04130 4110 E$="ERROR: Error "+STR(ERR)+" on opening '"+SFN$+"'";GOSUB 06000 4120 GOTO 04060 4130 REM 4140 REM "The file attributes (record size and records used) are retrieved " 4150 REM "and the copy direction is determined. " 4160 REM 4170 CURREC=1 4180 AT$=ATTR(1,"SHORT ORGANIZATION RECORD_SIZE RECORDS_USED") 4190 TY$=AT$(1,3);AT$=AT$(6);P=POS(" "=AT$);RECSIZE=NUM(AT$(1,P)); 4190:NUMREC=NUM(AT$(P)) 4200 IF TY$<>"MUL" THEN IF TY$<>"SER" THEN E$="ERROR: Source file type 4210:not MULTI or SERIAL";GOSUB 06000;TY$="";GOTO 04070 4210 RETURN 5000 REM 5000 5010 REM "This subroutine formats the screen for the copy. It displays " 5020 REM "the direction of the copy and the name of the files involved. " 5030 REM 5040 PRINT (0,1),'CE', 5050 IF TY$="MUL" THEN T$="Multi-key to serial" ELSE T$="Serial to 5050:multi-key" 5060 PRINT (20,6),'CL','SB',T$, 5070 PRINT (20,8),'CL','SB',"Copying ",'SF',SFN$,'SB'," to ",'SF',DFN$ 5080 PRINT (20,10),'CL','SB',"Percent complete:",'SF',;RETURN 6000 REM 6000 6010 REM "This subroutine will display any error message at the bottom " 6020 REM "at the bottom of the screen and will prompt the user for a " 6030 REM "for a CR. " 6040 REM 6050 PRINT (0,21),'CL','RB',E$,'RB',; PRINT (0,22),'CL',"Press SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg096 6050:to continue ",;INPUT (0,ERR=06060)* 6060 PRINT (0,21),'CL',(0,22),'CL',;RETURN Multi-key Files 7000 REM 7000 7010 REM "An error occured; report it and abort " 7020 REM 7030 E$="ERROR: Error "+STR(ERR)+" occurred at line "+STR(TCB(5)) 7040 GOSUB 06000 9900 REM 9900 9910 REM "Exit user." 9920 REM 9930 CLOSE(1);CLOSE(2) 9940 END _________________________________________________________________________ 3.7.9.9. Performance Characteristics ___________ _______________ The information contained in this section reflects measurements made on a sample data base that consists of 33,000 records that are 100 bytes long and keys that are 15 bytes long. The timings were performed on an MPx 8000 system and an MAI 2000 system. The timing measurements should be regarded as only rough estimates to assist in planning such operations as conversion of Direct files into Multi-Keyed files and the reconstruction of files that lack integrity. 3.7.9.9.1. File Conversion ____ __________ The timings referenced in this section, except where noted, were performed on an 8000. The conversion of a Direct file with 33,000 records to a Multi-Keyed file with 2 fields and 1 keyset required 80 minutes. The identical conversion on a 2000 required approximately the same amount of time. The conversion was done with a small BASIC program (for more details, see section 3.7.9.6). Conversion time increases as more fields and more keysets are added. To convert a Direct file with 67,000 records of 256 bytes each into a Multi-Keyed file with 38 fields and 2 keysets took 18 hours. The primary reason for the greatly increased time for conversion was the necessity for random insertion of each alternate key value. An alternate approach, described in section 3.7.9.6.4.5, is to convert the file with only a primary key defined and to add the other keysets later using SETFIELD. Using this approach, the conversion with one keyset took only 2 hours and 50 minutes. The SETFIELD operation took 9 minutes, for a total of 3 hours. The above timings were performed with WriteThru Enabled. When the conversion was performed with WriteThru Disabled, the conversion, including the SETFIELD, took about 1 hour. Multi-key Files 3.7.9.9.2. Addition of a Keyset ________ __ _ ______ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg097 Addition of a keyset is performed by executing a SETFIELD directive on an existing Multi-Keyed file. This statement will automatically invoke a special sorting program which is a very efficient way to generate the information required for the new keyset. To add one keyset to the 33,000 record file required only 3 and 1/2 minutes on BOSS/VS. On the 2000 this operation requires approximately 30 minutes. On BOSS/VS only, when many keysets which allow duplicates are added, occasionally the addition of a keyset will require more time because the record structures must be modified. 3.7.9.9.3. Deletion of a Keyset ________ __ _ ______ Deletion of a keyset is also performed by executing a SETFIELD directive on an existing Multi-Keyed file. Deletion of a keyset is a simpler operation than addition. To delete a keyset from a file with 33,000 requires only 4 seconds on the 8000. On the 2000 this operation takes approximately 90 seconds. 3.7.9.9.4. Reconstruct Utility on BOSS/VS ___________ _______ __ _______ The recommended method of reconstructing a Multi-Keyed file is to use the Reconstruct utility. More information on the sequence of operations to perform when recovering files after a system failure is contained in section 3.7.9.7. The time required to reconstruct a file varies with the number of keysets in the file. The following measurements were performed with the same 33,000 record file to which additional keysets were added. 1 keyset - 3.2 minutes 2 keysets - 6.7 minutes 3 keysets - 9.2 minutes 4 keysets - 16.3 minutes 3.7.9.9.5. Record Access ______ ______ Because the access method support for Multi-Keyed files is very similar to the access method support for Direct files, there is little difference in performance of READs and WRITEs when a Multi-Keyed file with a single keyset is compared to a Direct file. For the same reason, READs to the primary keyset of a Multi-Keyed file are equivalent to READs to the Direct file, no matter how many keysets or auxiliary Sort files there Multi-key Files are. When WRITEs to a Multi-Keyed file with multiple keysets are compared to WRITEs to a Direct file with an equivalent number of Sort files, the WRITEs to the Multi-Keyed file are faster, and the improvement increases as the number of keysets increases. WRITEs to a Multi-Keyed file with 10 keysets are approximately 20% faster than the sum of the time to WRITE to a Direct file and 9 related Sort files. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg098 Although WRITEs to Multi-Keyed files are faster than WRITEs to sets of Direct and Sort files, there is a performance cost for each additional keyset when writing to a Multi-Keyed file. A number of various factors affect the time required to write a record to record to a Multi-Keyed file, such as the length of the keys and records and the number of records currently in the file. In general, however, it is true that the time required for modifications to the keysets is a large percentage of the total write time. For smaller files, the time to modify each keyset is approximately the same as the time required to modify the data record area. For larger files, the keyset structures become more involved and the time required to modify them increases, so that a keyset modification might take 3 times as long as the record area modification. Access to records within a Multi-Keyed file via an alternate access path is much faster than the corresponding access from a Sort file into a Direct file. In order to access records sequentially, based on an alternate access path requires two READ operations when performed on a set of files. First a sequential READ is performed on the appropriate Sort file, then a random READ is performed on the Direct file, based on the key value which is extracted from the Sort file key. The corresponding operation on a Multi-Keyed file requires only one READ operation and is 2 to 3 times faster. To access records randomly based on an alternate access path requires three file operations when performed on a set of files. First a random READ is performed on the appropriate Sort file, using a partial key value. The key is partial because only the alternate key value is known and the entire key includes the Direct file key which is not known. This operation fails to find an exact match, so another operation, this one a KEY function must be performed to retrieve the entire key of the Sort file. The Direct file key is then extracted from the Sort file key. Finally, the Direct file key is used to READ the Direct file. The corresponding operation on a Multi-Keyed file requires just one READ operation and is approximately twice as fast. For further information of Multi-Key Files, see the Business ________ Multi-key Files BASIC 86 Reference Manual, M 6262. _____ __ _________ ______ 3.8. TYPE 3 LOAD ____ _ ____ TYPE 3 LOAD is known as "Special Load". This section describes the enhancements and changes that will be found in the 8.6 OS Special Load utility over the 8.5 OS. For information on how to run these options please refer to the BOSS/VS Installation Guide M 5138D, section 4, "Type 3 Load _______ ____________ _____ _ _____ Procedures". SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg099 3.8.1. MAIN MENU ____ ____ The main menu gives the operator the following options: 1. DISPLAY VOLUME AND FAMILY INFORMATION 2. INITIALIZATION OPTIONS 3. MOUNT/DISMOUNT DISK 4. CHANGE MASTER/BACKUP STATUS (8.6 NEW) 5. COPY OPTIONS Briefly, these five options are as follows: Display Volume and Family Information - This option gives system volume information and family status information. Initialization Options - All options for initializing volumes, families and installation parameters are included under this option. 1. CHANGE VOLUNE LABEL INFORMATION 2. UPDATE FAMILY INFORMATION 3. INITIALIZE FAMILY DIRECTORY 4. CHANGE INSTALLATION PARAMETERS 5. CHECK FILE SYSTEM TAG (8.6 NEW) Mount/Dismount Disk - An option for IO enabling and disabling disks. Change Master/Backup Status - An option for designating a drive as either MASTER (read only, write protected) or BACKUP (read/write) under Type 3 Load only. Copy Options - The three main types of copy are included under this screen. 1. DISK TO TAPE FAMILY BACKUP 2. DISK TO DISK SEQUENTIAL FAMILY BACKUP 3. COPY FAMILY FROM DISK TO DISK TYPE 3 LOAD Changes to these options are explained in subsequent sections. Though the final action of most the options are the same, the menu screen displays have changed. Menu screens were changed to give clear system information in all options, reduces the need to go between options to get information and to take away potentially dangerous options from the first level. 3.8.2. DISPLAY VOLUME AND FAMILY INFORMATION _______ ______ ___ ______ ___________ This option will display all volume and family information. It will provide information on all the disks on the system and information on any selected families. It will give the drive number, the volume serial number of the drive, whether the drive is fixed or removable, whether the drive is a system or data or backup disk, the name of the family the drive is in, its index within the family, the size in sectors of its file system space, whether the drive is mounted or not, and whether the drive is designated master or SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg100 backup. This screen also gives the option of asking for further information on a given disk and its family. If this option is chosen another screen will come up. If the volume label of the drive is not readable then an error status wil be displayed at the bottom of the screen, otherwise the screen will give the drive number, the status of the family that the drive belongs to, a map of the start locations, end locations, and sizes of all the spaces on the disk, and the general disk information as in the previous screen for all the drives in the family of the requested disk. DRIVE NUMBER : START END SIZE SEGMGR: (used by OS for swapping various segments of OS) TOTAL FS SPACE: DUMP AREA: RELTRKSUM: RELTRACKS: DR# SERIAL# TYPE CONFIG FAMNAME FAM# #SECTORS MOUNTED MASTER (A message appears at the bottom of the screen as to whether or not there are any conflicts between this and any other mounted family members. The disk must be mounted.) Please refer to the "BOSS/VS INSTALLATION GUIDE" manual M5138D for further information in the "Type 3 Load Procedure" section. TYPE 3 LOAD 3.8.3. INITIALIZATION OPTIONS. ______________ ________ The initialization options are as follows: 1. CHANGE VOLUME LABEL INFORMATION 2. UPDATE FAMILY INFORMATION 3. INITIALIZE FAMILY DIRECTORY 4. CHANGE INSTALLATION PARAMETERS 5. CHECK FILE SYSTEM TAG (8.6 NEW) The change volume information and update family information options will both begin by displaying information about all available disk drives. The initialize family directory option begins by displaying information about all available family base drives on the system. An "available" drive is any drive which is cabled into the system, regardless of whether it is enabled, disabled, powered on or off. The operator will then be requested to select one of the listed drives. If the drive is not accessible, an appropriate error message is given. If any of the requested drives have a master status an update will not be allowed. Just prior to the final prompt the update family information option will display all requested drives and the initialize family directory screen will display all the drives in the requested family. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg101 All options of Type 3 Load have a common question as the last prompt on the menu. This question asks whether the disk should be updated or not. No information is ever written on a disk until this question is answered with a "Y" and even then no information is written to drives or families with drives having a master status. 3.8.3.1. Change Volume Label Information ______ ______ _____ ___________ 3.8.3.1.1. Initialization ______________ The first prompt of this menu is for a drive number. The drive must be mounted and with a non-master status. After the drive has been selected, Type 3 Load checks the disk model type (Priam 154, Trident 83, etc). If the model is not recognized, the disk is rejected and a new disk is asked for. The only instance when disks will not be recognized is when a hardware/software configuration mismatch occurs. If the disk is recognized, Type 3 Load then reads the information in the disk volume label. If there is an error in getting this information Type 3 Load posts the error message, and then allows the operator to continue. TYPE 3 LOAD 3.8.3.1.2. Update Family Information ______ ______ ___________ This menu allows disk families to be created or modified. 3.8.3.1.2.1. Initialization ______________ When the menu is initially entered, the program displays information from all available drives. If any requested drive cannot be read, an error message is posted giving the read error along with a comment that the volume serial number cannot be determined. Note that all affected disks must be "mounted" in order for the initialization of this option to be successful. They also cannot be initialized if they have a master status. If an error occurs for one of these two reasons then the operator should exit the update family menu, select the "mount/dismount" and/or "master/backup" option, and change the appropriate disks. After the system has been booted, all disks on the system which have valid non-duplicate serial numbers will be "mounted", regardless of the state of their family configuration. If families of the same name or disks with the same serial number are present on the system, the mount/dismount option can be used to control which disks the system will recognize for the execution of "update family information". 3.8.3.1.3. Initialize Family Directory __________ ______ _________ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg102 The Initialize Family Directory first displays all base drives on the system. It will then prompt the user for the drive number of the base drive of a disk family. Next, it will display all the drives in the requested family. Finally, it prompts "INITIALIZE FAMILY? (Y/N):". If yes is answered to this prompt, all files on the family are deleted, and the entire file system area of the disk becomes available space. 3.8.3.1.4. Change Installation Parameters ______ ____________ __________ The prompts for this menu are: 1. Drive Number 2. Primary Prefix 3. Secondary Prefix 4. System Installation Name 5. Default User Family Name 6. Security Enabled Indicator 7. Write-Through Enabled Indicator 8. Write-Through Default on File Create Indicator. 9. Update Disk TYPE 3 LOAD In addition to the prompt fields, a display only field is present on the top of the screen which indicates which disk drives can be selected. These drives are the identifiable disks on the system which are online, mounted, and configured as system disks. The parameters set by this option are the same as those set by the INSTALL.PARAMS utility. 3.8.3.1.5. Check File System Tag _____ ____ ______ ___ (8.6 NEW) This option allows the viewing of the file system root sector tag which gives the state of the family on system and data disks. Sequential family backup disks do not use this option. The possible values are INIT, Init, ZERO, Zero, T3AB, and T3ER. INIT, Init, ZERO, and Zero are normal values. If the tag is displayed in capitals the disk was set-up on a 8/9.5 OS system. There is no harm with these values. If displayed in lower case the disk was set-up on a 8/9.6 OS system. The value of 'ZERO', 'Zero' indicates that the disk family directory has been zeroed and never enabled (initialized). The value of 'INIT', 'Init', indicates that the disk has been enabled once in a TYPE 1 LOAD. T3AB is a tag value used only on the 8/9.6 OS systems. T3AB is a value that is given to the destination disk tag in a TYPE 3 disk to disk copy if the copy did not go to completion and was aborted. A disk with this value cannot be used in TYPE 1 or TYPE 2 LOAD. To make the disk usable you must either 'INITIALIZE FAMILY DIRECTORY' or run 'COPY FAMILY FROM DISK TO DISK' to completion. T3ER is a tag value used only on the 8/9.6 and later OS systems. T3ER is a value that is given to the destination disk tag, in a TYPE 3 disk to disk copy, if the copy went to completion but there was a error and 'CONTINUE' was input. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg103 T3ER prevents the disk from being'ENABLED' in a TYPE 1 or TYPE 2 LOAD but may be changed if the pack is needed in an emergency. This value is used to flag the user that the data on the disk needs to be checked. The user should always note the locations that were skipped from a 'CONTINUE' and verify the data at those locations. A prompt of "WOULD YOU LIKE TO MAKE THIS PACK VALID ?" appears with a value of T3ER. A "Y" will change the 'TAG' to 'Init' and the pack can then be used in TYPE 1 or TYPE 2 LOAD. Please refer to the "BOSS/VS INSTALLATION GUIDE" manual M5138D for further information in the "Initialization Options" section. TYPE 3 LOAD 3.8.3.2. Mount/Dismount Disk ______________ ____ The mount/dismount disk option allows the operator to change the mounted or dismounted state of the disk. It will first produce a system display screen. It will then ask the drive number of the drive to mount or dismount. After entering a valid drive number it will attempt to mount or dismount the disk, again displaying the drive information. If it is successful the display will reflect the change of status, otherwise the error will be displayed on the screen. Please refer to the "BOSS/VS INSTALLATION GUIDE" manual M5138D for further information in the "Mount/Dismount Disk" section. 3.8.3.3. Change Master/Backup Status ______ _____________ ______ (8.6 NEW) A disk drive can have either a master or a backup status assigned to it. This is essentially a write protect bit in the volume label of the disk. Having a backup status is not to be confused with a pack being a backup pack. Its main purpose is to prevent the easy and possibly accidental destruction of critical disk data. This status field is changed through the use of this option. A copy will be allowed from any 'SOURCE' family regardless of the status of its member drives but no copy will be allowed onto a 'DESTINATION' family containing a drive with master status. This should eliminate the vast majority of wrong way backups and unintended disk and family initializations. The procedure to change the master/backup status will be almost identical to the option to mount or dismount disk; displaying all the drives, requesting a drive for status change, redisplaying the drives, and display an error message in case of failure. Please refer to the "BOSS/VS INSTALLATION GUIDE" manual M5138D for further information in the "Change Master/Backup Status" section. 3.8.3.4. Copy Options ____ _______ Upon selection of the copy options of the main screen a screen will come up giving you a choice among the three copy options. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg104 The three options are disk to tape family backup, disk to disk sequential family backup, and copy family from disk to disk. These will be explained below. Please refer to the "BOSS/VS INSTALLATION GUIDE" manual M5138D for further information in the "Copy Options" section. TYPE 3 LOAD 3.8.3.4.1. Disk to Tape Family Backup ____ __ ____ ______ ______ 3.8.3.4.1.1. Introduction ____________ The disk to tape family backup utility allows disk families to be saved/restored via either 1/2 inch magnetic tape reels, or 1/4 inch magnetic tape cartridges. There have been no major changes to this option. The added capability to retry, continue or to abort has been added in case of a disk read error. Please refer to the BOSS/VS INSTALLATION GUIDE M5138D for use of these options. This backup utility is used to save or restore entire disk families. It does not save/restore individual files. The restore option of this utility does a replace of an existing family's files and file structures with the data from the tape. The restore does not "add" to files already existing on a family, and any previously existing files on a family which is restored over are lost. An automatic compare option is also offered by this utility. This option allows a compare of disk and tape to be made in order to absolutely insure the integrity of both media. This program cannot be used to save, reconfigure, and then restore a disk family, because certain changes will disallow the restore. 3.8.3.4.1.2. Save Operational Characteristics ____ ___________ _______________ The save operation does an image copy of all data in the family. It saves the data without inspection of the file structures or directory format. If a compare option is selected, tapes still only need to be mounted one time. In the simplest case, each reel is compared immediately after it's saved, and before the next reel is saved. In the more complex case using two tape drives, two reels are saved before the first one is compared, because this allows the program to avoid waiting for a tape to rewind. The tape (tape errors only, not disk) error recovery during the save is on a reel by reel basis. This type of recovery allows the operator to rewrite any reel which fails to be written correctly. Therefore if an error occurs on the fifth reel being written, the save only needs to go back and restart at the beginning of the fifth reel. The save does NOT need to restart from reel number one. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg105 Examples of errors which will allow the operator to restart TYPE 3 LOAD the save of the current reel are: 1. The compare option is selected, and the compare fails. 2. The tape turns out to not be readable during the compare. 3. During the save, a large bad spot exists on tape, which causes the write to fail. 4. The tape drive is set offline while the save or compare is in progress. 5. The tape drive malfunctions (loses vacuum, for instance) Note if an error requires that a reel be rewritten and the tape itself is suspected of being bad, a new tape may be mounted before the save is resumed. If an error occurs while reading from disk, a sector by sector retry of the operation is attempted. If it successfully reads the sectors, it will continue. If the error recurs then a message is written to the screen indicating the type of error and its exact location. A carriage return will be requested to continue and the operator will be given the option to retry, continue, or to abort. An abort will cause the entire save to be aborted and a continue will continue past the error. If an error is continued through, it will probably be caught again during the compare. If any disk error occurs, the operator should note the location of the error, because it can be used to determine what track needs to be relocated to correct the problem. Disk maintenance programs (not part of TYPE 3 LOAD) can then be run to determine which files are affected and to perform the track relocation. 3.8.3.4.2. Restore Family _______ ______ There have been no major changes to this option. The added capability to retry, continue or abort has been added in case a disk write error occured and was caught during the verify of the data. 3.8.3.4.2.1. Restore Initial Display _______ _______ _______ The initial display put up by the restore function is: RESTORE FAMILY FROM TAPE INPUT TAPE DRIVE NUMBER(S)? xxxxxxxx DISK FAMILY TO BE RESTORED? xxxxxxxx AUTOMATIC COMPARE (Y/N)? xx TYPE 3 LOAD BEGIN RESTORE (Y/N)? xx In response to the tape drive prompt, the operator should SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg106 mount the first tape to restore, and then enter one or two tape drive numbers in the same manner as for save. Please refer to the BOSS/VS INSTALLATION GUIDE M5138D for use of these options. 3.8.3.4.2.2. Restore Operational Characteristics _______ ___________ _______________ The restore process essentially deletes all files on the family to be restored, and replaces them with the data from the tape. The restore process begins execution by checking the family to be restored with the family saved on tape. In order for the restore to be allowed, both families must have the same number of members, and both must have the same starting location for the file space area. In order for the file space start to be the same, the corresponding disks must both have the same volume label "configuration", which is either system disk or data disk. Disks do not need to be the same model. For example, data saved from a Priam disk can be restored to a Trident disk provided that the two disks are similar in capacity. The families are also compared member by member to insure that the maximum potential file space on each member is big enough to hold the corresponding data from tape. If a member is absolutely not big enough, the program displays an error message indicating the disk family which is too small, and terminates. If a member is big enough, but the configuration of the file space differs between disk and tape, a message describing the discrepancy is displayed, and the operator is allowed to change the disk family member and continue. Note: When changing disk families, only the end of the file space will be changed. The dump area size will not be reduced to allow for a bigger file space. If the operator wishes to adjust the dump area, it must be done via the TYPE 3 LOAD option which performs that function. If the data to be restored is on several reels of tape, the tapes must be mounted in proper sequence for the restore. An attempt to mount a tape out of sequence will be rejected by the program with the message "WRONG SEQUENCE NUMBER. WANTED REEL #n, BUT REEL MOUNTED WAS m". In this message, "n" is the reel number of the tape wanted, and "m" is the number of the tape found. Both numbers refer to the order in which the tapes were written during the save. When restoring data from multi-reel saves, the operator is TYPE 3 LOAD protected from incorrectly restoring a family by mounting the wrong tape. The types of errors checked for are explained in detail in the section "TAPE LABEL INFORMATION AND USE". Briefly, these errors are: 1). Mounting a tape with the wrong family name. 2). Mounting a tape not created in the same save. 3). Mounting a tape not created via the family backup program. The restore of the data is done in a special order to prevent a partial restore from looking like a good family. If the SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg107 restore is terminated prior to the copy of the last block from the last reel of tape, the family being restored will look as if it has never been initialized (e.g. no files on disk can be accessed). Disk writes performed by a restore are always followed by a disk verify operation. This verify will be done in addition to a compare (if selected). The verify consists of reading the data back from disk, and comparing it to the copy already in memory. If an error is detected during the read or verify then a sector by sector retry of the operation is attempted. If the read is successful then the program continues. If the error recurs then a message is written to the screen indicating the type of error and its exact location. At this point a carriage return will be requested to continue and the operator will be given the option to retry, continue, or to abort. An abort will cause the restore to be aborted and will leave the destination disk in an invalid state. A continue will continue past the error. If an error is continued then it will probably be caught during the compare operation. Whenever a disk error occurs during restore, the location of the error should be noted, even if a retry corrected the problem. The disk error indicates that the media or drive is marginal, and may develop problems in the future. Disk diagnostics may then be run on the affected area of the disk to see if a track needs to be relocated, or if disk hardware needs to be fixed. Note that most disk writes done by a TYPE 1 LOAD of the system are not followed by a verify, so marginal media or drives would not be detected until later when the consequences are potentially severe (loss of files or system dump). The error recovery of tape errors in restore works on a reel by reel basis in the same way as save, and all tape error recovery options of save apply to restore. TYPE 3 LOAD 3.8.3.5. Disk to Disk Sequential Family Backup ____ __ ____ __________ ______ ______ 3.8.3.5.1. Introduction ____________ The Disk to Disk Sequential Family Backup utility allows disk families to be either saved or restored from other disks. Any group of system or data disk families may be saved to a sequence of one or more "backup" disks in the same manner as files are saved to a sequence of tape volumes via SAVERESTORE or DISK TO TAPE FAMILY BACKUP. The same restrictions apply to the sequence of backup disks as applied to a sequence of tape volumes, except that families on backup disks may be re-saved (updated) without destroying adjacent families on the backup media. A disk which is initialized as a "Backup" disk, is essentially a data disk without the filesystem overhead. This utility is designed only for high speed backup of entire families. Entire families may be saved or restored, but individual files on the backup medium created by a save may SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg108 not be read or written with normal file system access methods. To access any file on a pack created by a save, the entire family must be restored, then the file may be accessed. 3.8.3.6. Copy Family From Disk to Disk ____ ______ ____ ____ __ ____ 3.8.3.6.1. Introduction ____________ The copy family utility is designed to duplicate entire families in the fastest way possible. It performs this operation by using almost all of the available memory and doing direct reads and writes at disk speed. Only the file system boundaries are heeded. Hence, the destination disk file space is a bit for bit image of the source disk. This is done at the expense of using one or more entire disk packs as backup media. Both the source and destination families must simultaneously be on line and enabled. This utility runs only as one of the TYPE 3 LOAD options. This insures that no other disk accesses are possible while the program is running and that almost all of the main memory is available for buffer space. 3.8.3.6.2. Copy Family Display ____ ______ _______ When the Disk to Disk copy first comes up, it will display the base volumes only of all families on the system. The display ____ _______ ____ will contain the same information as the disk information display option. After displaying the family root volumes the program will TYPE 3 LOAD request a source and a destination drive number. A display will then be made of all the members of the source and destination families. 3.8.3.6.3. Requirements for Copying ____________ ___ _______ In the event only a single family exists, no copy is possible and the user will be so notified. If more than one family exists, copying may be possible. After selection of the source and destination, a consistency check is made by the program to insure the two families have an equal number of members and have the same disk configurations and that each destination member has sufficient space for receiving the source. If they do not, the user is notified of the problem and the copy will not continue. If the source and destination file system spaces have an exact match both in size and position, then the copy process is ready to begin. If the destination file space is large enough then the program will alert the user that it must "force a match" before continuing and give the operator a chance to abort. If the force-match option has been chosen, then on starting the copy the destination directory will be cleared (returned to an un-initialized state) and a new volume label will be written. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg109 The copy operation starts after the "BEGIN COPY" prompt is answered with "Y". 3.8.3.6.4. Copy 300 Mb 8" to 285 Mb Disk Drives ____ ___ __ __ __ ___ __ ____ ______ For systems that have an existing 285 Mb disk drive and the 300 Mb 8" drives, the 8" drive can be made to look like the 285 Mb drive for copy family disk to disk. The benefit of this allows for DISK TO DISK backups of the 300 Mb to a 285 Mb removable media instead of having to use tape media. This can be done by fooling the system into thinking that it has the same filesystem space as the 285 Mb removable. To accomplish this the 300 Mb drive needs to be set up and initialized in the TYPE 3 LOAD to reflect the 285 Mb that it will in effect become. In other words , the disk type, SYSTEM or DATA, the correct size DUMP AREA, etc must be the same. Once the setup is complete, a DISK TO DISK FAMILY COPY may be done from the 285 Mb to the 300 Mb or vice versa. The first time this copy is done the operator will be prompted that there is a filesystem space mis-match, "FORCE MATCH" Y/N ?. A yes response will make the 300 Mb look identical to the 285 Mb in terms of filesystem space. CAUTION_: If the 300 Mb is ever re-initialized, then the above _________ process will have to be performed in order to make the 300 Mb look like the 285 Mb again. TYPE 3 LOAD 3.8.3.6.5. Copy Process ____ _______ To maximize copy speed, all other IO is minimized including VDT IO. Thus, very little activity will be discernible on the system. After each completed cycle consisting of a read/write/verify, the percent complete will be updated at the bottom of the screen. If no errors have occurred while copying, the message "D O N E - TYPE " will signify that the copy was successfully completed. 3.8.3.6.6. Error Handling _____ ________ At the beginning of the copy process the file system start space of the destination family is invalidated by writing over it. The purpose of this is to guarantee that if we abort out of an error condition we will not be able to use the destination family as valid. This space is restored at the end of the copy process in all copies in which an abort is not invoked. If an error occurs during the copy, a sector by sector retry of the attempted IO operation is done. This allows one automatic software retry and in the case of a hard error it gives the exact sector of the error. If the error does not occur on the retry the copy will continue without notifying the operator. If the error happened again on the retry a message will be sent to on the screen indicating the status, SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg110 whether it was a soft or a hard error, and whether it was a source or a destination error. In the case of a hard error the exact cylinder, sector, and head are written to the screen. At this point a carriage return is requested to continue. After a carriage return is received, the program will display a message asking if you want to abort, retry, or continue. If you abort, the copy is aborted, leaving the file system space corrupt. If you retry, the program tries the operation on the sector of the error. If successful it continues on the sector past that in which the error occurred, otherwise it goes through the previous error sequence again. If you request to continue it will continue on the sector past that in which the error happened. If you continue through all the errors without aborting, the message "DONE - ERRORS OCCURRED" is displayed on the screen. The root sector tag will contain the value T3ER and is unusable until this tag value is changed. This will allow the use of any files which did copy correctly onto the destination family. The user, however, should be cautious in the use of these packs. TYPE 3 LOAD If you do abort out of an error situation rather than retry or continue then the file system start space will remain corrupted, causing the destination family to appear invalid to the file system. The root sector tag will contain the value T3AB. This, in turn, will cause the disk to remain disabled until a zero directory is performed or until the copy process is run to completion. Refer to section 1.3.5 "Check File System Tag. 4. DIAGNOSTICS ___________ | REMIDI (MPx 7000/7100/8000) | LAN Controller support has been added for off-line testing. | REMIDI (MPx 9000/9100/9500) | LAN Controller support has been added for off-line testing. | New CPU Tests: Write to opcode cache when disabled test, ___ ___ _____ | Forced parity test, Cache error reporting test, Backplane | update using partial words test, ESTK up/down counter test. | (ESTK up/down counter test is in the IDC test selection.) | Screen Display Changes: I/O CPU identified, Memory and ______ _______ _______ | Controller tests numbers cleared. | DEMON | LAN Controller support has been added for off-line testing. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg111 | The extended memory test "Test Address Lines" had been | replaced with a much faster (5 min/MB) and improved test | algorithm. This improved algorithm has also been added to | the "Shared Memory Test" for the 4/8/16-Way, IMLC, BMTC, | and LAN. | Random data pattern test has been added to the "Buffer | Memory Test" for the DMA and MPC controllers. | Disk drive testing "SET DEFAULTS" menu now prompts for | controller type (TDP, MPC or DMA). | NEWX | LAN Controller support has been added for on-line testing. | DCL | The Common I/O procedure has been modified to handle TR, | TL, TP, and TS Read commands of VDT and HVDT tests | correctly. | For further information on these diagnostics and how to run | them, refer to the Diagnostic User's Manual Document Writer, | which is accessed by entering !DOCWRITER in command mode. Hardware 5. HARDWARE ________ 5.1. LARLS FOR PCBAS FOR THE MPX 7000, 7100, AND 8000 _____ ___ _____ ___ ___ ___ _____ _____ ___ ____ | The Lowest Acceptable Revision Levels for 7000, 7100, and 8000 | PCBAS are identical to those for 8.4B/C/D/E with the following | exceptions: | 1) MPC 903500 PCBA-Revision H | (If used in the MPx 7100 system, remove JMP3 if | present and set SW2-1 OFF | and SW2-4 OFF) | 2) MPC 903549 PCBA-Revision B | (If used in the MPx 7100 system, remove JMP3 if | present and set SW2-1 OFF | and SW2-2 OFF) | 3) BMTC 903413 PCBA-Revision R | Revision T is required for full MTCS support. | Revision U is required for support of the GCR 1/2" (model | 4405) tape drive. | 4) ACS 903379-001/-002 = 7000 systems require "Y" or higher. | = 8000 systems require "L" or higher, | (T if BMTC). | 903379-003 = 7100 systems require "AD" or higher, | (can also be used in 7000/7100/8000 systems). | Revision AA and above supports either 7000 or 8000 Series | Systems and is required for the 8" 300 MB fix disk. | Revision levels V-Y cannot be used on 8000 systems. | Revision level Z cannot be used on 7000/7100 systems. | 5) MCS 903374 PCBA-Revision L | Revision S is switch selectable between MPx | 7000/7100/8000 Series Systems or MPx 9000/9100/9500 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg112 | Series Systems via SW1 on the MCS PCBA. If the MCS PCBA, | at revision S, is switch selected for MPx 9000/9500 | Series Systems and installed into an MPx 7000/7100/8000 | Series System, it will not load. | 6) LAN 903595 PCBA-Revision F 5.2. LARLS FOR PCBAS FOR MPX 9000, 9100, AND 9500 SERIES _____ ___ _____ ___ ___ _____ _____ ___ ____ ______ | The Lowest Acceptable Revision Levels for PCBAs for MPx 9000, | 9100, and 9500 Series Systems are: | 1) MCS 903374 PCBA-Revision L | Revision S is switch selectable between MPx | 7000/7100/8000 Series Systems or MPx 9000/9100/9500 | Series Systems via SW1 on the MCS PCBA. If the MCS PCBA | is switch selected for MPx 7000/7100/8000 systems and | installed into an MPx 9000/9100/9500 system, board | addresses 32 thru 47 are reserved for the IMLC PCB only. | Revision "T" is required for main memory support above 12 | megabytes. Hardware | 2) AMS 903548 PCBA-Revision F Revision "N" (-002) is | required for main memory support above 12 megabytes. | 3) ESTK 903552 PCBA-Revision G Revision "J" is required for | main memory support above 12 megabytes. | 4) IDC 903550-001 PCBA-Revision P (with cache) | IDC 903550-002 PCBA-Revision P (without cache) | Revision J addresses cache timing problems on selected | systems. Do not replace the IDC PCBA on an error free | system to meet this LARL requirement. | 5) IDC64 903597-001 PCBA-Revision E (with cache) | IDC64 903597-002 PCBA-Revision E (without cache) | IDC64 PCBA is required for support of main memory above | 12 megabytes. | 6) DMA 903554 PCBA-Revision H Revision "G" is required for | support of main memory above 12 megabytes. Revision "G" | is also required for support of the 600 LPM band printer | model 4220. Do not replace revision "G" DMA on an error | free system to meet this LARL. | 7) IMLC 903381 PCBA-Revision K | IMLC 903534 PCBA-Revision D | 8) BMTC 903413 PCBA-Revision R | Revision "U" is required for support of the GCR tape | drive model 4405. | 9) GCR Minimum Revision Levels | It is possible for a hang condition to occur in | SAVERSTORE, if the GCR tape drive does not have the | following minimum revision levels: | IF CARD 403923205 (BEFORE THE LARL WAS 403923202) | CP CARD 403864305 (BEFORE THE LARL WAS 403864303) | 10) Memory (1/2 and 1 MB) 903349 PCBA-Revision V | (Not to be used with greater than 12 megabyte support; | must use standard trade-in policies.) | 11) Memory (2 and 4 MB) 903516-001,-002, PCBA-Revision E | Revision "J" is required for support of main memory above | 12 megabytes. Support of main memory above 12 megabytes | is supported on the MPx 9500 Series Systems only. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg113 | 12) Hi-speed video controller 903377 PCBA-Revision C | 13) 8-Way 903383 PCBA-Revision A | 14) 16-Way 903437 PCBA-Revision J | 15) LAN 903595 PCBA-Revision F | The following boards are NOT supported on MPx 9000, 9100, and | 9500 Series Systems: | 1) 7000/7100/8000 CPU set | 2) TDP (Must be replaced by the BMTC for tape support) | 3) MPC Hardware 5.3. LOCAL AREA NETWORK CONTROLLER (LAN) _____ ____ _______ __________ _____ | With the release of the 8.6A/9.6A O.S., a new controller is | supported: The Local Area Network controller. The LAN PCBA PN | 903595 provides the ability to tie like systems together (MPx | to MPx) in a local environment not more than 4000 feet apart. | Each system requires one LAN controller and both systems must | be on the same O.S. level. The LAN may be installed either | to the right of the CPU set(s) after the BMTC PCBA or to the | left of the MCS PCBA. Refer to MAGNET section in this | document for further information on the Local Area Network. 6. INSTALLATION ____________ 6.1. INTRODUCTION ____________ There are two ways to install 8.6A/9.6A: 1) Install a new system 2) Update a system If you are installing a new system go to section 6.2. If you are upgrading from a level above 8.4D, go to section 6.3. If you are upgrading to 9.6A, go to section 6.4. Upgrades from release levels 8.4D and below require a conversion to the new file system. This document does not contain instructions for this conversion. These conversion instructions appear in the Software Announcements for release levels 8.4E and 8.5A/B/C/D/E, as well as in the "BOSS/VS FILE CONVERSION USERS GUIDE" M 5185A. The conversion cannot be performed without these instructions. Starting with 8.6A/9.6A there is a change in the way terminals are enabled for user logon at system load time. The enable of the TERMINALS group, that allows users to logon, is now under user control, in the startup command file, if the file exists. If the file does not exist, the TERMINALS group is enabled automatically. Refer to the section on System Startup for information on Job Manager, MAGNET and Spooler startup procedures. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg114 For further information on System Startup see Section 6.5. 6.2. NEW INSTALLATION ___ ____________ The loading of 8.6A is done the same as any other BOSS/VS release. Since the operating system can be released on 1/2" (reel) or 1/4" (cartridge) tape, the word "tape" means either media form. 6.2.1. Installing the O.S. __________ ___ ____ 6.2.1.1. ALT LOAD ___ ____ A) Mount the new release tape in the tape drive. B) Press the "ALTLOAD" button on the front panel. C) Enter the appropriate system disk (0 or 1) or if drives 0 and 1 are both system disks, enter "2" to update both disks. D) Enter a "0" to update WCS slot 0. E) Enter a "Y" to the prompt "Are you SURE you want to overwrite this WCS ? (Y/)". New Installation The system automatically updates the OS and WCS slot 0 on both disks, if selected. When this is complete, the system prompts "DONE - READY FOR NORMAL LOAD". Reload by pressing the LOAD button. 6.2.1.2. ENTER A TYPE 3 LOAD (SPECIAL FUNCTIONS) _____ _ ____ _ ____ ________ __________ OPTION 2 (INITIALIZATION OPTIONS) Initialization options 1-4 must be done to insure proper operation. 6.2.1.2.1. OPTION 1 (CHANGE VOLUME LABEL INFORMATION) ______ _ _______ ______ _____ ____________ All available disk drives will be displayed. An 'available' drive is any drive cabled to the system, whether enabled, disabled, powered ON or OFF. If any drive has a 'MASTER' status, an update will not be allowed. To change a 'MASTER' status, go to the main menu in TYPE 3 LOAD. Choose option 4 (CHANGE MASTER/BACKUP STATUS). ENTER DRIVE NUMBER OF VOLUME LABEL TO CHANGE:__ ( Enter volume label to change. ) The screen will change to display the information for only the drive whose volume label you choose. SERIAL NUMBER _________ ( Enter CR to accept current serial number. ) DISK CONFIGURATION (1=SYSTEM, 2=DATA, 3=BACKUP) ____ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg115 ( Enter the appropriate disk type. ) SIZE OF DUMP AREA.....______ x 1024 BYTES ( For system disks only, enter the size of the dump area given by the line below this prompt as the area needed for both main memory and shared memory controllers. ) FILE SYSTEM SPACE ______ x 1000 SECTORS ( Enter the number displayed at the bottom of the screen for this prompt. The display will appear as "CR=X" where X is the maximum space allowed. ) UPDATE DISK VOLUME LABEL (Y/N) __ ( Enter "Y" if above information is correct) New Installation 6.2.1.2.2. OPTION 2 (UPDATE FAMILY INFORMATION) ______ _ _______ ______ ____________ The disk information for all drives on the system is displayed and the cursor is positioned at 'FAMILY BASE DRIVE NUMBER'. FAMILY BASE DRIVE NUMBER ___ FAMILY NAME ______ ( CR for default family name ) DRIVE NUMBERS OF OTHER DISKS IN FAMILY? (TYPE SPACES FOR NO OTHER DRIVES) Enter all other drive numbers for this family or spaces if none. The drives must be fixed media drives and in 8.6 format. UPDATE DISK (Y/N)? 6.2.1.2.3. OPTION 3 (INITIALIZE FAMILY DIRECTORY) ______ _ ___________ ______ __________ This option displays all root drives on the system. FAMILY BASE DRIVE NUMBER ______ ( Enter drive number to be initialized. ) INITIALIZE FAMILY? (Y/N) __ 6.2.1.2.4. OPTION 4 (CHANGE INSTALLATION PARAMETERS) ______ _ _______ ____________ ___________ Only system disks will be displayed. DRIVE NUMBER _______ PRIMARY PREFIX __________________ ( Enter (family).R6A49.SYS. ) Where (family) is the family where the operating system files will reside. SECONDARY PREFIX _______________ ( Enter (family).R6A49.SYS. ) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg116 Where (family) is the family where the alternate operating system files will reside. SYSTEM INSTALLATION NAME ________________ Sets the default installation name for a specified system disk. DEFAULT USER FAMILY NAME _____________ ( Enter default user family ) New Installation SECURITY (E=ENABLED, D=DISABLED) ___ FILE SYSTEM WRITE THROUGH? (E=ENABLED, D=DISABLED) ___ WRITE THROUGH DEFAULT ON FILE CREATE (E=ENABLED, D=DISABLED):__ This parameter specifies what the default write through will be on a file created through a BASIC file create or through the CREATE utility. UPDATE DISK WITH INSTALLATION PARAMETERS? (Y/N) __ Display: INSTALLATION PARAMETERS SUCCESSFULLY WRITTEN TO DISK. (CR) TO CONTINUE: Option 1 must be done on all disks. Options 2 and 3 must be done for each family. Option 4 must be done on system disks only. 6.2.1.3. Restoring the O.S. _________ ___ ____ Enter SAVERESTORE in a TYPE 2 LOAD and choose OPTION 2 RESTORE FILES FROM TAPE. The screen appears as in figure 6-1. At the prompt for output device, enter a parallel printer so that a listing of the restore operation is produced. This listing can be used to make sure all files were restored correctly. At the prompt, "FILE SPECIFIERS", enter ".". Enter to all other questions. All system files will be restored to disk. Once all files are restored to disk, the message "AUTOMATIC COMPARE, CR TO CONTINUE" appears. This automatically rewinds the tape and begins the compare operation. This only occurs when the compare option is selected. When the compare is completed, enter a CTL-IV to return to the "SAVERESTORE" menu. Reload the system and enter a TYPE 1 LOAD. Now go to section 6.3.3 to continue updating the O.S. slots. New Installation Figure 6-1. Restore Screen ______ ____ _______ ______ -------------------------------------------------------- SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg117 RESTORE FILES TAPE SET.ID: DRIVE-NUM: REEL-NUM: PRIMARY PREFIX: (FAMILY).NODE. FILE TYPE (D/P/CR=ALL) COMPARE (CR=Y/N) DATE (MM/DD/YY) TIME (HH:MM) OUTPUT DEVICE (CR=VDT) DELETE EXISTING FILES (CR=Y) VERIFY (Y/CR=N) ENTRIES CORRECT (Y/N) -------------------------------------------------------- 8.6A Installation Procedure for Upgrade from Releases Above 8.4D 6.3. 8000 UPGRADE FROM RELEASE LEVELS ABOVE 8.4D ____ _______ ____ _______ ______ _____ ____ If you are upgrading to 9.6A, go to section 6.4. 6.3.1. Saving Files to Tape ______ _____ __ ____ Current files must first be backed up to tape, using the standard tape utility, SAVERESTORE. When saving files to tape, send the output from the save process to the printer. These will provide a record of backup for each file. Also it is recommended that all files on tape be compared to the files on the disk. 6.3.2. Operating System Update _________ ______ ______ 6.3.2.1. Installing the O.S. __________ ___ ____ 6.3.2.1.1. ALT LOAD ___ ____ A) Mount the new release tape in the tape drive. B) Press the "ALTLOAD" button on the front panel. C) Enter the appropriate system disk (0 or 1) or if drives 0 and 1 are both system disks, enter "2" to update both disks. D) Enter a "0" to update WCS slot 0. E) Enter a "Y" to the prompt "Are you SURE you want to overwrite this WCS ? (Y/)". The system automatically updates the OS and WCS slot 0 on both disks, if selected. When this is complete, the system prompts "DONE - READY FOR NORMAL LOAD". Reload by pressing the LOAD button. 6.3.2.1.2. CHANGE INSTALLATION PARAMETERS ______ ____________ __________ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg118 Enter a TYPE 3 LOAD (SPECIAL FUNCTIONS) and select OPTION 2 (INITIALIZATION OPTIONS). OPTION 2 (INITIALIZATION OPTIONS) OPTION 4 CHANGE INSTALLATION PARAMETERS Only system disks will be displayed. DRIVE NUMBER _______ PRIMARY PREFIX _______________________ ( Enter (family).R6A49.SYS. ) Where (family) is the family where the operating system files reside. 8.6A Installation Procedure for Upgrade from Releases Above 8.4D SECONDARY PREFIX _____________________ ( Enter (family).R6A49.SYS. ) Where (family) is the family where the alternate operating system files reside. SYSTEM INSTALLATION NAME _________________________ Sets the default installation name for a specified system disk. DEFAULT USER FAMILY NAME ________ ( Enter default user family ) SECURITY (E=ENABLED, D=DISABLED) ___ FILE SYSTEM WRITE THROUGH? (E=ENABLED, D=DISABLED) ___ WRITE THROUGH DEFAULT ON FILE CREATE (E=ENABLED, D=DISABLED) __ This parameter specifies what the default write through will be on a file created through a BASIC file create or through the CREATE utility. UPDATE DISK WITH INSTALLATION PARAMETERS? (Y/N)__ Display: INSTALLATION PARAMETERS SUCCESSFULLY WRITTEN TO DISK (CR) TO CONTINUE: Reload the system by pressing the LOAD button and enter a TYPE 2 LOAD. 6.3.2.2. Restoring the O.S. _________ ___ ____ Enter SAVERESTORE in a TYPE 2 LOAD and choose OPTION 2 RESTORE FILES FROM TAPE. The screen appears as in figure 6-2. At the prompt, "FILE SPECIFIERS", enter ".". Enter to all other questions. All system files will be restored to disk. Please note that once all files are restored to disk, the message "AUTOMATIC COMPARE, CR TO CONTINUE" appears. This SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg119 automatically rewinds the tape and begins the compare operation. This only occurs when the compare option is selected. When the compare is completed, enter a CTL-IV to return to the "SAVERESTORE" menu. 8.6A Installation Procedure for Upgrade from Releases Above 8.4D Figure 6-2. Restore Screen ______ ____ _______ ______ -------------------------------------------------------- RESTORE FILES TAPE SET.ID: DRIVE-NUM: REEL-NUM: PRIMARY PREFIX: (FAMILY).NODE. FILE TYPE (D/P/CR=ALL) COMPARE (CR=Y/N) DATE (MM/DD/YY) TIME (HH:MM) OUTPUT DEVICE (CR=VDT) DELETE EXISTING FILES (CR=Y) VERIFY (Y/CR=N) ENTRIES CORRECT (Y/N) -------------------------------------------------------- At each prompt, enter a . 6.3.2.3. Installing the Configuration Record __________ ___ _____________ ______ It is necessary to install a new configuration record when upgrading to 8.6A from a previous level. Until the following procedure is completed, the system will have a minimum configuration. Enter a TYPE 1 LOAD. Set your prefix to .SYSTEM.CONFIG. Before you load the new configuration record, rename the current configuration record on your system, using the RENAME utility, to temporarily preserve it for fall back purposes. (e.g. Add "OLD" in front of the name.) Using the SAVERESTORE utility, restore the new configuration record on tape onto your system. Execute the CONFIG.MGR utility. The CONFIG.MGR utility allows the user to update the system configuration record by installing a new configuration file. This utility displays the current and new configuration record. When "Y" is answered to the prompt "Install Configuration:", the new configuration is copied from the file ".SYSTEM.CONFIG.I(serial number)", to the special system area on disk. The new configuration takes effect at the next system load. For further details on the use of the CONFIG.MGR utility, see the 8.5D/9.5D Software Announcement #139. The configuration record file name is derived from the system SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg120 8.6A Installation Procedure for Upgrade from Releases Above 8.4D serial number by changing the leading "8" to an "I" and adding the prefix ".SYSTEM.CONFIG.". EXAMPLE: .SYSTEM.CONFIG.I1030114 for SSN 810-30114 This file should be backed up by the user, in case reinstallation should become necessary. Before going to the next step, LOAD the system so the new ____ configuration record will take affect. If you do not load the system, you will have a minimum configuration and the system will be very slow. 6.3.3. UPDATING OTHER O.S. SLOTS ________ _____ ____ _____ The slots 1, 2, and 3 need to be updated. Set the prefix to the .INST. node by keying in the following in command mode: !PREFIX .R6A49.INST. With the inclusion of support for 7000/7100 Series Systems, there is an additional version of REMIDI for the MPC controller. Version BVM6A0803 now contains micro-diagnostics for the LAN and MPC controller, and is placed in WCS slot 3 on 7000/7100 Series Systems. Version BV5C0101 includes all the micro-diagnostics except MPC controller micro-diagnostics. It is placed in WCS slot 2 and is used for testing on both the 7000/7100 and 8000 Series Systems. 6.3.3.1. UPDATING SLOT ONE (1) ________ ____ ___ ___ A copy of the primary operating system will be put in slot 1. !UPDATE.OS IMAGE FILE NAME: .R6A49.INST.OS1.UV060149003 OS SLOT: (displayed) OS VERSION: (displayed) IMAGE FORMAT: (displayed) NEW WCS SLOT: 1 UPDATE WHICH DISK: (0=nn/1=nn/B=BOTH/Q=QUIT)___ DONE ! UPDATE COMPLETE Next, WCS slot 1 is updated with a copy of the same WCS that was installed in slot 0. !UPDATE.WCS ENTER WCS SLOT [0..3]: Enter '1' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) 8.6A Installation Procedure for Upgrade from Releases Above 8.4D WCS IMAGE FILE: .R6A49.INST.WCS.B5311 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg121 WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 6.3.3.2. UPDATING WCS SLOT TWO (2) ________ ___ ____ ___ ___ REMIDI version BV5C0101 will reside in this slot. !UPDATE.WCS ENTER WCS SLOT [0..3]: Enter '2' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE: (choose disk) WCS IMAGE FILE: .R6A49.INST.REMIDI.BV5C0101 WCS LEVEL OF WCS IMAGE FILE: (level displayed) UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETED! 6.3.3.3. UPDATING SLOT THREE (3) ________ ____ _____ ___ 6.3.3.3.1. Updating O.S. Slot Three (3) ________ ____ ____ _____ ___ The O.S. slot 3 will contain the O.S. for DEMON on both 7000/7100 and 8000 Series Systems. !UPDATE.OS IMAGE FILE NAME: .R6A49.INST.OS3.UV060139011 OS SLOT: (displayed) OS VERSION: (displayed) IMAGE FORMAT: (displayed) NEW WCS SLOT: Enter '0' or '1' on 7000/7100 Series Systems to associate the WCS in either slot with load sector 3. Enter '3' on 8000 Series Systems. UPDATE WHICH DISK (0=nn/1=nn/B=BOTH/Q=QUIT):____ UPDATING DISK DONE! UPDATE IS NOW COMPLETE NOTE: On MPx 7000/7100 Series Systems, the UPDATE.LD utility needs to be run to update the Load Directory. For further information on the use of UPDATE.LD, see the Diagnostic section in the 8.5D/9.5D Software Announcement #139. 8.6A Installation Procedure for Upgrade from Releases Above 8.4D 6.3.3.4. Updating WCS Slot Three (3) ________ ___ ____ _____ ___ 6.3.3.4.1. WCS Slot Three on 7000/7100 Series Systems ___ ____ _____ __ _________ ______ _______ This slot will contain the micro-diagnostics for the MPC and LAN controller, REMIDI version BVM6A0803. After this slot has been updated, it will be necessary to change the Load SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg122 Directory by running the utility UPDATE.LD. See the Diagnostic section of the 8.5D/9.5D Software Announcement #139, for further information on REMIDI and running UPDATE.LD. !UPDATE.WCS ENTER WCS SLOT [0..3]: Enter '3' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R6A49.INST.REMIDI.BVM6A0803 WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 6.3.3.4.2. WCS Slot Three on 8000 Series Systems ___ ____ _____ __ ____ ______ _______ This slot will contain system WCS which is common to both the O.S. and DEMON. !UPDATE.WCS ENTER WCS SLOT [0..3]: Enter '3' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R6A49.INST.WCS.B5311 WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 6.3.4. SLOT INFORMATION ____ ___________ Once all slots have been updated, use the utility OSINFO to display the slot information. The information should be similar to figure 6-3. If disk 1 is a system disk also, repeat these steps beginning with the first step in section 6.3.3 8.6A Installation Procedure for Upgrade from Releases Above 8.4D Figure 6-3. Operating System Information ______ ____ _________ ______ ___________ OPERATING SYSTEM INFORMATION ------------------------------------------------------------------ BOOT LEVEL : X.X.X.X LOAD SECTOR: 0 1 2 3 DISK 0 : 0/0 1/1 0/2 3/3 SERIAL # : XXX-XXXXX ------------------------------------------------------------------ OS NAME OS LEVEL DISK:SLOT WCS LEVEL ------------------------------------------------------------------ R 6A*49 870415 6.1.49.3 0:0 B 5.3.11 R 6A*49 870415 6.1.49.3 0:1 B 5.3.11 N/A 0:2 REMIDI B 5.1.1 DEMON 2/23/87 6.1.39.11 0:3 B 5.3.11 ------------------------------------------------------------------ NOTE: OSINFO on 7000/7100 Series Systems will show the additional SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg123 version of REMIDI IN WCS slot 3. The load sector 3 should be 3/0 on the 7000/7100 Series. Installation Procedure for Upgrade to the MPx 9000, 9100, and 9500 6.4. UPGRADING TO 9.6A AND THE MPX 9000, 9100, AND 9500 _________ __ ____ ___ ___ ___ _____ _____ ___ ____ 6.4.1. SPECIAL CONSIDERATIONS _______ ______________ A presite survey is required before upgrading to an MPx 9000, 9100, or 9500. (See Field Bulletin #161A). A new configuration record is required when upgrading to a 9000, 9100, or 9500. A new configuration record is also necessary when upgrading to 9.6A from 9.5. It is required that systems being upgraded to 9.6A run on a release level that supports the new File System (any level above 8.4D) for at least one week prior to upgrade. When it is established that the system is running smoothly on the software at the end of this period, upgrade to 9.6A may then proceed. 6.4.2. PRINTING OUT THE TERMINAL CONFIGURATION RECORD ________ ___ ___ ________ _____________ ______ Skip this section if you are upgrading to 9.6 from 9.5. When upgrading from the MPx 8000 to the MPx 9000, 9100 or 9500, it is necessary to reference the 8.5 terminal configuration in order to properly re-address the 9000, 9100 and 9500 controllers. Therefore, it is necessary to print out a copy of the terminal configuration record before upgrading. 1. Enter the TERM.CONFIG utility. 2. Select OPTION 2 DISPLAY A CONFIGURATION FILE. 3. When the following screen is displayed, enter these responses to the prompts: CONFIGURATION FILE: P OUTPUT DEVICE: DETAILED REPORT: Y ENTRIES CORRECT: Y The terminal configuration record should now be printed. 6.4.3. SAVING FILES TO TAPE ______ _____ __ ____ Current files must first be backed up to tape, using the standard tape utility, SAVERESTORE. When saving files to tape, send the output from the save process to the printer. This will provide a record of backup for each file. Also it is recommended that all tapes be compared to the files on the disk. Installation Procedure for Upgrade to the MPx 9000, 9100, and 9500 6.4.4. OPERATING SYSTEM UPDATE _________ ______ ______ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg124 6.4.4.1. ALT LOAD ___ ____ A) Mount the new release tape in the tape drive. B) Press the "ALTLOAD" button on the front panel. C) Enter the appropriate system disk (0 or 1) or if drives 0 and 1 are both system disks, enter "2" to update both disks. D) Enter a "0" to update WCS slot 0. E) Enter a "Y" to the prompt "Are you SURE you want to overwrite this WCS ? (Y/)". The system automatically updates the OS and WCS slot 0 on both disks, if selected. When this is complete, the system prompts "DONE - READY FOR NORMAL LOAD". Load the 9.6A O.S. from slot 0 by setting switch 3 to 'off' and pressing the LOAD switch. 6.4.4.2. TYPE 3 LOAD (SPECIAL FUNCTIONS) ____ _ ____ ________ __________ 6.4.4.2.1. Updating Installation Parameters ________ ____________ __________ Enter a TYPE 3 LOAD (SPECIAL FUNCTIONS) OPTION 2 (INITIALIZATION OPTIONS) 6.4.4.2.1.1. OPTION 4 (CHANGE INSTALLATION PARAMETERS) ______ _ _______ ____________ ___________ Only system disks will be displayed. DRIVE NUMBER _______ PRIMARY PREFIX ________________________________ ( Enter (family).R6A49.SYS. ) Where (family) is the family where the operating system files will reside. SECONDARY PREFIX ________________________________ ( Enter (family).R6A49.SYS. ) Where (family) is the family where the alternate operating system files will reside. SYSTEM INSTALLATION NAME ___________________________ Sets the default installation name for a specified system disk. DEFAULT USER FAMILY NAME ________ Installation Procedure for Upgrade to the MPx 9000, 9100, and 9500 ( Enter default user family ) SECURITY (E=ENABLED, D=DISABLED) ___ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg125 FILE SYSTEM WRITE THROUGH? (E=ENABLED, D=DISABLED) ___ WRITE THROUGH DEFAULT ON FILE CREATE (E=ENABLED, D=DISABLED) __ This parameter specifies what the default write through will be on a file created through a BASIC file create or through the CREATE utility. (Please see Field Bulletin #212.) UPDATE DISK WITH INSTALLATION PARAMETERS? (Y/N)__ Display: INSTALLATION PARAMETERS SUCCESSFULLY WRITTEN TO DISK (CR) TO CONTINUE: Reload the system by pressing the LOAD button and enter a TYPE II load. 6.4.4.2.1.2. Sizing the Dump Area ______ ___ ____ ____ At this point it is necessary to enter a TYPE 3 LOAD (SPECIAL FUNCTIONS), choose OPTION 2 (INITIALIZATION OPTIONS), then go to OPTION 1 CHANGE VOLUME LABEL INFORMATION to determine whether the Dump Area is large enough. Correct sizing of the Dump Area is especially critical on MPx 9000, 9100 and 9500 systems, because dumps to tape are not possible on these systems. This is because the BMTC, which is required to control tape operations on MPx 9000, 9100 and 9500 systems, is a shared memory controller. When sizing the Dump Area, you may want to round up to the next megabyte or add an extra megabyte or two for future expansion. If it becomes necessary to enlarge the Dump Area, you must do a complete back up (which you already should have), reinitialize the system disks (OPTION 2, 1 through 4, in a TYPE 3 LOAD), and do a restore from the back up in a TYPE 2 LOAD. 6.4.4.2.2. Restoring the O.S. Files _________ ___ ____ _____ Enter SAVERESTORE in a TYPE 2 LOAD and choose OPTION 2 RESTORE FILES FROM TAPE. The screen appears as in figure 6-2. At the prompt, "FILE SPECIFIERS", enter ".". Enter to all other questions. This will restore all files from the release tape to disk. Please note that once all files are restored to disk, the Installation Procedure for Upgrade to the MPx 9000, 9100, and 9500 Figure 6-4. Restore Screen ______ ____ _______ ______ -------------------------------------------------------- RESTORE FILES TAPE SET.ID: DRIVE-NUM: REEL-NUM: PRIMARY PREFIX: (FAMILY).NODE. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg126 FILE TYPE (D/P/CR=ALL) COMPARE (CR=Y/N) DATE (MM/DD/YY) TIME (HH:MM) OUTPUT DEVICE (CR=VDT) DELETE EXISTING FILES (CR=Y) VERIFY (Y/CR=N) ENTRIES CORRECT (Y/N) -------------------------------------------------------- At each prompt, enter a . message "AUTOMATIC COMPARE, CR TO CONTINUE" appears. This automatically rewinds the tape and begins the compare operation. This only occurs when the compare option is selected. When the compare is completed, enter a CTL-IV to return to the "SAVERESTORE" menu. 6.4.4.2.3. Installing the Configuration Record __________ ___ _____________ ______ It is necessary to install a new configuration record when upgrading to 9.6A from 8.4, 8.5 and 9.5 release levels. Until the following procedure is completed, the system will have a minimum configuration. Enter a TYPE 1 LOAD. Set your prefix to .SYSTEM.CONFIG. Before you load the new configuration record, rename the current configuration record on your system, using the RENAME utility, to temporarily preserve it for fall back purposes. (e.g. ".OLDCONFIG.") Using the SAVERESTORE utility, restore the new configuration record on tape onto your system. Execute the CONFIG.MGR utility. The CONFIG.MGR utility allows the user to update the system configuration record by installing a new configuration file. This utility displays the current and new configuration record. When "Y" is Installation Procedure for Upgrade to the MPx 9000, 9100, and 9500 answered to the prompt "Install Configuration:", the new configuration is copied from the file ".SYSTEM.CONFIG.I(serial number)", to the special system area on disk. The new configuration takes effect at the next system load. For further details on the use of the CONFIG.MGR utility, see the 8.5D/9.5D Software Announcement #139. The configuration record file name is derived from the system serial number by changing the leading "8" to an "I" and adding the prefix ".SYSTEM.CONFIG.". EXAMPLE: .SYSTEM.CONFIG.I1030114 for SSN 810-30114 This file should be backed up by the user, in case reinstallation should become necessary. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg127 After installing the new configuration record, LOAD the system. Otherwise your system will be at minimum configuration and will be extremely slow. 6.4.4.3. UPDATING OTHER O.S. SLOTS ________ _____ ____ _____ The slots 1, 2, and 3 need to be updated. Set the prefix to the .INST. node by keying in the following in command mode: !PREFIX .R6A49.INST. 6.4.4.3.1. Updating Slot One (1) ________ ____ ___ ___ A copy of the 9.6A operating system will be put in O.S. slot 1. !UPDATE.OS IMAGE FILE NAME: .R6A49.INST.OS1.UV060149003 OS SLOT: (displayed) OS VERSION: (displayed) IMAGE FORMAT: (displayed) NEW WCS SLOT: 1 UPDATE WHICH DISK: (0=nn/1=nn/B=BOTH/Q=QUIT)___ DONE ! UPDATE COMPLETE Next, WCS slot 1 is updated with a copy of the 9.6A WCS. !UPDATE.WCS ENTER WCS SLOT [0..3]: Enter '1' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R6A49.INST.WCS.A641 WCS LEVEL OF WCS IMAGE FILE: (level displayed) Installation Procedure for Upgrade to the MPx 9000, 9100, and 9500 Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 6.4.4.3.2. Updating WCS Slot Two (2) ________ ___ ____ ___ ___ The first section of the 9000/9100/9500 version of REMIDI will reside in this slot. NOTE: Running UPDATE.OS automatically updates the load sectors for the disk. However, running UPDATE.WCS does not. (The Load Sectors are displayed at the top of the OSINFO screen.) It is therefore necessary to run UPDATE.LD for REMIDI on newly initialized systems packs, or whenever question marks ("?/?") appear in Load Sector 2 on the OSINFO screen. See the Diagnostic section in the 8.5D/9.5D Software Announcement, #139, for further information on REMIDI and running UPDATE.LD. !UPDATE.WCS SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg128 ENTER WCS SLOT [0..3]: Enter '2' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE: (choose disk) WCS IMAGE FILE: .R6A49.INST.REMIDI.AVA6A0104 WCS LEVEL OF WCS IMAGE FILE: (level displayed) UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETED! 6.4.4.3.3. Updating Slot Three (3) ________ ____ _____ ___ 6.4.4.3.3.1. Updating O.S. Slot Three (3) ________ ____ ____ _____ ___ O.S. slot 3 will contain the O.S. for DEMON. !UPDATE.OS IMAGE FILE NAME: .R6A49.INST.OS3.UV060139011 OS SLOT: (displayed) OS VERSION: (displayed) IMAGE FORMAT: (displayed) NEW WCS SLOT: Enter '0' to associate DEMON's O.S. with the WCS in slot 0. (DEMON and the 9.6A O.S. share the same WCS. UPDATE WHICH DISK (0=nn/1=nn/B=BOTH/Q=QUIT):____ UPDATING DISK DONE! UPDATE IS NOW COMPLETE Installation Procedure for Upgrade to the MPx 9000, 9100, and 9500 6.4.4.3.3.2. Changing the Load Sector for Slot Three (3) ________ ___ ____ ______ ___ ____ _____ ___ Because the second section of the 9000/9100/9500 version of REMIDI is in WCS slot 3, the Load Directory must be changed to point to another WCS slot for DEMON. The 9.6A O.S. and DEMON share the same WCS code, therefore, we can point to the WCS slot used by the 9.6A O.S. Update the Load Directory for DEMON by using the UPDATE.LD utility. See the Diagnostic section in the 8.5D/9.5D Software Announcement, #139 for information on how to run UPDATE.LD. 6.4.4.3.3.3. Updating WCS Slot Three (3) ________ ___ ____ _____ ___ This slot will contain the second section of the 9000/9500 version of REMIDI. !UPDATE.WCS ENTER WCS SLOT [0..3]: Enter '3' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R6A49.INST.REMIDI.AVC6A0104 WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg129 WCS UPDATE COMPLETE 6.4.5. Slot Information ____ ___________ Once all slots have been updated, use the utility OSINFO to display the slot information. The information should be similar to figure 6-3. Installation Procedure for Upgrade to the MPx 9000, 9100, and 9500 Figure 6-5. Operating System Information ______ ____ _________ ______ ___________ OPERATING SYSTEM INFORMATION ------------------------------------------------------------------ BOOT LEVEL : X.X.X.X LOAD SECTOR: 0 1 2 3 DISK 0 : 0/0 1/1 0/2 3/1 SERIAL # : XXX-XXXXX ------------------------------------------------------------------ OS NAME OS LEVEL DISK:SLOT WCS LEVEL ------------------------------------------------------------------ R 6A*49 870415 6.1.49.3 0:0 A 6.4.1 R 6A*49 870415 6.1.49.3 0:1 A 6.4.1 N/A 0:2 REMIDI A 6.1.4 DEMON 2/23/87 6.1.39.11 0:3 REMIDI A 6.1.5 ------------------------------------------------------------------ The O.S. and WCS slots on all other system disks on the system must also be updated. Installation is now complete. System Startup 6.5. SYSTEM STARTUP ______ _______ 6.5.1. Standard Startup Command File on 8.6A/9.6A BOSS/VS ________ _______ _______ ____ __ _________ _______ The commands for the standard System Startup Command File are released in the file: .R6A39.SYS.START.CMD The standard commands are: !MAGNET.STARTUP !GROUP.CREATE SPOOLER,TYPE=SYSTEM !SPOOL P*,VERIFY=F,PAUSE=F !GROUP.ENABLE TERMINALS,VERIFY=F,PAUSE=F The name of the System Startup Command File actually used for startup is: (system-default-family).SYSDATA.START.CMD Part of 8.6A/9.6A BOSS/VS system installation is to copy the released file to the .SYSDATA. node and make changes and additions as necessary. Note that the commands and parameters in this file must match the commands and parameters defined in SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg130 the CLI command and function definition files for the individual system being installed. If the System Startup Command File is not found after a system load, then a default initialization is performed. This puts all printers into spooled mode and enables terminals. The following outlines the commands, some of the implications and details of the System Startup Command File method of system configuration. 6.5.1.1. Command File Definitions _______ ____ ___________ MAGNET.STARTUP ______________ This command runs a released MAGNET program that does all of the startup operations required by the MAGNET subsystem. This command should be deleted if MAGNET is not part of the system configuration. GROUP.CREATE_SPOOLER,TYPE=SYSTEM ________________________________ This command creates the Spooler Group that maintains the activity log files and Group statistics for the spooler subsystem. This command should come before the 'SPOOL P*' command. System Startup SPOOL_P*,VERIFY=F,PAUSE=F _________________________ This command puts all of the printers into spooled mode, and causes any eligible requests on the spooled printers to start printing. GROUP.ENABLE_TERMINALS,VERIFY=F,PAUSE=F _______________________________________ This command enables the 'built-in' TERMINALS Group, and allows all users to logon to any terminals. This command is provided to allow the terminals to be enabled under user control. See below. NOTE: IF A SYSTEM STARTUP COMMAND FILE EXISTS, THIS COMMAND, OR SOME OTHER COMMAND TO ENABLE TERMINAL GROUPS, MUST BE IN THE SYSTEM STARTUP COMMAND FILE FOR USERS TO LOGON TO THE SYSTEM. In case the TERMINALS Group is disabled, a user with 'system operator' status can enable this group when attempting to logon to the system. This allows an operator to logon to the system in case the Startup Command File did not enable the TERMINALS Group, or the TERMINALS Group was left disabled by accident and all operators signed off the system. To enable the TERMINALS Group during logon the operator attempts to logon and ignores the 'Logon disabled' error messages and enters a 'CR' to continue. A prompt is displayed asking the operator if he wants to enable the TERMINALS Group. NOTE: THIS OPTION IS NOT AVAILABLE IF SOME OTHER TERMINAL SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg131 TYPE GROUP IS ENABLED. ALSO, ONLY THE TERMINALS GROUP IS ENABLED, AND IT IS NOT CREATED IF IT DOES NOT EXIST. 6.5.2. Implications ____________ 1). Normal system startup is automatic. The system ______ ______ _______ __ _________ configuration options defined when the system was installed (placed into the System Startup Command File) are put into effect each time the system is loaded, with no further action by the user. These startup options may be modified by the user at any time, by editing the System Startup Command File. 2). Startup sequence is under user control. Users now have _______ ________ __ _____ ____ _______ the ability to control the sequence of events at startup, after the internal startup sequence is complete. Users that do not need this level of control may ignore this feature. Some users may wish to run specific programs, and do recovery operations, before MAGNET and/or the Spooler are System Startup started up. This ability would be impossible if these subsystems were always started by the internal system initialization. 3). System recovery is possible before all users logon. This ______ ________ __ ________ ______ ___ _____ _____ approach allows the operator to allow only specified terminals/users to logon after a system load. The System Startup Command File containing the single command: GROUP.CREATE , TYPE=TERMINAL, USERS=SYS.MGR, DEVICES=T0 would allow only the user 'SYS.MGR' to logon to terminal 'T0' after the system load. No other users could logon, and no other activity would start. In this case the printers will be in suspended mode and MAGNET will not be initialized. When the system operator is finished with the recovery operations the 'normal' system configuration command file may be run by the operator to begin normal system processing. Again, users who do not need this level of control may ignore this feature. 4). Default startup with no System Startup Command File. When _______ _______ ____ __ ______ _______ _______ ____ the TYPE 1 LOAD is complete, if the System Startup Command File is not found then 'default' startup conditions are in effect. In this case the system is available for any use. This mode is intended to support systems that want only these default startup options. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg132 The 'built-in' TERMINALS Group is enabled and allows all users to logon to any terminal. A system group named SPOOLER is created and the printers are put into spooled mode. The MAGNET subsystem is not activated. ___ The following is a description of the details of the System Startup Job: When a TYPE 1 LOAD is performed, the last module to be initialized is the Job Manager (JMM). The final act of JMM is to run a batch job with a CLI command file. The files involved are: (system-default-family).SYSDATA.START.CMD (system-default-family).SYSDATA.START.IN (system-default-family).SYSDATA.START.OUT SYSDATA.START.CMD is a sequential file that contains all of System Startup the startup commands; this is the System Startup Command File. The Job Manager looks in the system default family (only) for this file. SYSDATA.START.IN is a sequential file that contains any data that may be input by commands and programs in the above startup file. A read from standard INPUT will read records from this file. The Job Manager looks in the system default family (only) for this file. SYSDATA.START.OUT is a sequential file that contains the results of the startup command file. A write to standard OUTPUT by commands and programs will be placed into this file. The Job Manager deletes this file in the system family if it exists, prior to running the startup command file. If the startup file (system-default-family).SYSDATA.START.CMD - or - (system-default-family).SYSDATA.START.CMD.TEXT is not found, the Job Manager will perform a default startup described above. If the startup file (system-default-family).SYSDATA.START.IN - or - (system-default-family).SYSDATA.START.IN.TEXT is not found, the Job Manager will attach a null file to startup INPUT; an End-Of-File will be returned for each read from standard INPUT. NOTE: THE SYSTEM STARTUP COMMAND FILE CONTAINS (ONLY) STANDARD CLI COMMANDS. A CLI command may be: SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg133 1. A CLI Command or Function (START, PREFIX, $WHERE, etc.) 2. A system utility (DIR, COPY, etc.) 3. The name of a program to run. 4. The name of another CLI command file. 7. RELATED DOCUMENTATION _______ _____________ 2770/2780/3770/3780 Batch Emulator User Guide M 5080C 3270 Pass-Through Reference Manual M 5091A BOSS/VS Business BASIC 86 Reference Manual M 6262 * BOSS/VS User Guide M 5098F * BOSS/VS Utilities User Guide M 5102E * 3270 Emulation Package Operator Guide for MAI 8000 Series M 5129 MAI 8000 Terminal Asynchronous Communication Facility Reference Manual M 5130A File Transfer Facility User Reference Manual M 6352A BOSS/VS Installation Guide M 5138D * MPx System Installation Planning Guide M 5146F * BOSS/VS Special Purpose Utilities User Guide M 5151 BOSS/VS System Support Manual M 5152 Intersystem Transport Package User Guide M 6354D MAI 8000 Series COBOL Reference Manual M 5174 MAI 8000 Series COBOL User Guide M 5175 BOSS/VS File Conversion User Guide M 5185A MAGNET/VS User Reference Manual M 6363 * * These manuals have been revised for 8.6A/9.6A. INDEX _____ DISCONNECTed Mode: 20 RESERVEd Mode: 20 SPOOLed Mode: 20 Spooler Operator Definition: 20 SUSPENDed Mode: 21 ORIGINATOR: MBF SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB022 Pg134 FIB 00023 07/07/87 *** MPx to 13XX program transfer may cause ERROR 20 *** Transferring programs from an MPx system to a 13xx system may cause error 20's on the 13xx system. A source program on the MPx system is converted to a serial file using the program BPGM before transferring to the 13xx system via TBC. Once on the 13xx system, a conversion from serial file format to program is accomplished through the program *BPGM. Error 20's may occur during this last conversion process. WORKAROUND - The following patch addresses the problem. Modify the program, *CL5L4, on the 13xx system. 0740 READRECORD (4,END=1000,ERR=0750,IND=J) I$ 0742 LET A9=POS($8A$=I$) 0744 IF A9<>0 THEN I$=I$(1,A9-1) 0746 GOTO 0790 SAVE "*CL5L4". The problem occurs on any version of the MPx but particularly on the 4.5B release of 13xx. A BEGIN or a CLEAR directive within the converted program initiates the problem. ORIGINATOR: R. Hinojosa SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB023 Pg001 FIB 00024 08/04/87 *** Down.Load Utility Option to Display Device ISDC/Line Numbers *** There is an option in the Down.Load utility that will display devices with ISDC numbers and the line numbers on the ISDC. This option is undocumented, use as follows: In command mode (at !) enter DOWN.LOAD At prompt 'Enter device number to down load (0 - 63)' enter ? and CR. A screen of help information will be displayed. At prompt 'press CR for next screen' enter * and CR. Device ID, device type, ISDC.line number and status will be displayed for all devices (except disk) on the system. ex. DEVICE TYPE LINE STATUS TT15 7270/sl 2.1 Open Device = T - Terminal G - Ghost L - Slave R - Tape LP - Line Printer P - Serial Printer (NOTE: line number for serial printers may display incorrectly - always line 0 but the ISDC number will be correct) Type = Any device type (/sl = slave) Line = ISDC number.line number on this ISDC Status = Available - configured, cable present, not in-use Open - in-use No cable ORIGINATOR: N. Jones SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB024 Pg001 FIB 00025 08/11/87 *** Release 9.6A/8.6A is now available *** MAI Basic Four, Inc. is pleased to announce that the new software release, 9.6A /8.6A, is now available. The 9.6A release is the recommended release for MPx 9000, 9100, and 9500 Series Systems. The 8.6A release is the recommended release for MPx 7000, 7100,and 8000 Series Systems. A. ENHANCEMENTS o A new and enhanced SPOOLER. o New JOB MANAGER utilities, which provide control over user processes and collect and display system resource use statistics. o JOB ACCOUNTING, an optional, chargeable feature of JOB MANAGER, which sets account resource limits and displays system resource use statistics for user accounts. o MAGNET, an optional, chargeable feature, which includes a Local Area Network and a Wide Area Network. o BUSINESS BASIC 86, which includes intersystem compatibility features, program generation tools, more system independent features, file name translation (primarily for MAGNET support), and MULTI-KEY FILES. o Support for 19.2K bps asynchronous communications. o SECURITY utility enhancements. o A Command Language BATCH SUBSYSTEM facility, which allows tasks to run in background mode. o Support for 24 megabytes of main memory and greater than 164 device connectivity on MPx 9500 Series Systems. B. IMPORTANT NEW CONSIDERATIONS FOR 9.6A/8.6A o 9.6A/8.6A features new System Startup procedures for MAGNET, SPOOLER, and JOB MANAGER. These procedures are documented in the System Startup section of the 9.6A/8.6A Software Announcement. o BASIC programs written or modified on 9.6A/8.6A will not run on prior releases without recompilation. If you wish to move BASIC programs from 9.6A/8.6A to prior releases, these programs should not contain any of the new features offered on 9.6A/8.6A, and they will need to be recompiled on the prior release. o A new configuration record is required when upgrading to 9.6A/8.6A from an 8.4 or 8.5 release. A new configuration record is also required when upgrading to 9000/9100/9500 Series Systems. C. ADDITIONAL IMPORTANT CONSIDERATIONS o Upgrades from release levels 8.4D and below require a conversion to the new File System. These instructions appear in the software announcements for releases 8.4E and 8.5A/B/C/D/E, SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB025 Pg001 as well as in the "BOSS/VS FILE CONVERSION USER GUIDE" M 5185A. These conversion instructions do not appear in the 9.6A/8.6A Software Announcement. o It is recommended that 8000 Series Systems be upgraded to 9000 or 9500 Series Systems run on the new File System (O.S. releases 8.4E and above) for a minimum of one week prior to the hardware upgrade. 9.5 systems should upgrade directly to 9.6A. o A presite survey is required before installing or upgrading to an MPx 9000, 9100, or 9500 (See Field Bulletin 161A). o When upgrading to 9.6A/8.6A from releases prior to 9.5C/8.5C, an ALT LOAD must be done before the O.S. files are restored. This is because certain files will not restore (including the drivers for the ISDC controllers) when on releases prior to 9.5C/8.5C. D. RELATED DOCUMENTATION A detailed explanation of the new features of 9.6A/8.6A and how to use them, can be found in the following manuals: BUSINESS BASIC 86 REFERENCE MANUAL M 6262 BOSS/VS USER GUIDE M 5098F BOSS/VS UTILITIES USER GUIDE M 5102E BOSS/VS INSTALLATION GUIDE M 5138D MAGNET/VS USER REFERENCE MANUAL M 6363 ORIGINATOR: N. Prentiss SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB025 Pg002 FIB 00026 08/11/87 *** Character position and overprinting with OS 9.6/8.6 *** The purpose of this Field Bulletin is to make clear the definition and use of character positioning and overprinting on operating system levels BOSS/VS 9.6/8.6 and later. Character positioning is through the use of the @(x) mnemonic in Business Basic, which designates where the next character is to appear in the output line. Character positioning never implies overprinting. If output is repositioned to a point where output data is already in place, the resulting output, including spaces, replaces what was put there earlier. Example: 100 PRINT(1)@(10), "XXXXXXXXXXXXXXXXXXXX",@(15),"YYY 000" Results: (starting at position 10) XXXXXYYY 000XXXXXX This example holds true for all printers in all modes on MPx systems using BOSS/VS 9.6/8.6. Overprinting is any operation which causes more than one non blank character to be printed in the same position on a line. Overprinting can be done through the use of the 'CR' mnemonic. The effect of 'CR' is to print characters without advancing the paper. The resulting output is superimposed characters on an "already" printed line. Matrix printers cannot perform overprinting. Underlining is a special case of overprinting. Underlining using the 'CR' mnemonic is supported, even on Matrix printers. Also, uderlining can be performed by using 'BU' (begin underline) and 'EU' (end underline) mnemonics. Example: PRINT(1)"XXXXXXXXXXXXXXXXXXXX",'CR',"YYY 000" Results: Matrix Printers: "---XXX---XXXXXXXXXXX" Band and Serial Printers: "***XXX***XXXXXXXXXX" (* in the above line indicates an "X" with a "-" overprinted) This example holds true for all modes. ORIGINATOR: L. Sanders SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB026 Pg001 FIB 00027 08/24/87 *** Use EXTTAPE Utility to restore Configuration records on 8.4 OS *** The EXTTAPE utility should be used to restore newly created Configuration record tapes on systems which are running 8.4x releases. The tapes are created on systems at Basic Four which are using the 'new' file system and SAVERESTORE is incompatible with 8.4. SAVERESTORE should be used to restore Configuration record tapes on systems at 8.5x and later release levels. There have been some instances where the tapes were created by Basic Four using. the wrong utility (i.e. SAVERESTORE for an 8.4x system) and the only work-around was to take the tape to an 8.6/9.6 system, restore using SAVERESTORE, backup using EXTTAPE then the tape was usable on the 8.4 system. NOTE: If an incorrectly generated Configuration tape is received a new one should be ordered, however this work-around might be required in some circumstances. If SAVERESTORE recognizes the format of the tape but indicates an incorrect FILE SYSTEM, the tape was generated with SAVERESTORE on a different level of FILE SYSTEM and the above work-around is the only way the tape can be used. ORIGINATOR: N. Jones SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB027 Pg001 FIB 00028 09/17/87 *** Warnings and Cautions for Release 9.6A/8.6A *** These Warnings and Cautions apply to release level 9.6A/8.6A. Where applicable, the SPR (System Problem Report) or RSC (Request for Software Change) number is listed. The following Warnings and Cautions apply to all MPx systems. I. BOSS/VS A. UTILITIES 1. CONFIG.MGR a) A configuration record can only be installed from an account with a USER LEVEL of 3. b) Printer output cannot be directed to a specific printer. c) The LEGAL option of DataWord will always display "YES" when using the "Install" option. However, if the configuration record was created with LEGAL=NO, LEGAL will not be enabled. This is a problem in the "Install" display only. d) Configuration records created for 9100 Series Systems on O.S. levels 8.5/9.5 will display as System Type "9000", even though the printout of the configuration record shows "9100". Configuration records created for 9100 Series Systems on O.S. levels 8.6/9.6 will display as System Type "9100". 2. FAMILY a) SPR #507152 - Disk numbers of the first multi-volume family created are used as defaults for subsequent families, if the subsequent families are created without exiting the FAMILY utility. The workaround for this problem is to exit the FAMILY utility after each multi-volume family is created. b) SPR #507151 - When creating volume labels using the FAMILY utility (Option 4), the volume type (System or Data) of the first disk is retained as a default when creating volume labels for subsequent disks. However, if this default value is used (by pressing ), the volume label will not be updated with this default value for volume type, even though it displays this way on the screen. The workaround for this problem is to always key in "S" for System disk and "D" for Data disk, and never take the default for volume type. 3. GETDEVINFO GETDEVINFO does not return information on Batch jobs. 4. JOB MANAGER a) Defined GROUPS are deleted at system reload. Job GROUPS to be kept on a more or less permanent basis should be created via commands entered in the System Startup command file, .SYSDATA.START.CMD. b) JOB.CREATE does not allow the PAUSE=TRUE parameter to be passed. If the command is embedded in a program, all errors must be handled by the application. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB028 Pg001 c) BATCH jobs require an output device file which is not automatically deleted. The user may need to delete these files on a regular basis to keep disk space available. d) The FID (0) is a file for a BATCH job. This is done by design so that a BASIC program can be run in BATCH mode. e) SPR 510275 - The JOB DISPLAY detail screen can erroneously show negative workspace usage. This problem will be fixed in 9.6B/ 8.6B. f) Quotes must be used around the user accounts when specifying more than one user account in the GROUP.CREATE and GROUP.MODIFY parameter lines. Example: GROUP.CREATE MYGROUP, TYPE=TERMINAL, PRIORITY=3, USERS="GROUP1.*, GROUP2.*" g) RSC 511490 - If PRIORITY is not specified for TERMINAL and BATCH type jobs, the PRIORITY will default to 1. This default, although proper for BATCH type jobs, is normally too low for TERMINAL type jobs. It is recommended that a PRIORITY of 3 be specified for TERMINAL type jobs during GROUP.CREATE. (See example in item f.) h) RSC 511491 - The priority of SYSTEM type jobs cannot be changed, even though GROUP.MODIFY appears to allow the user to do this. i) RSC 511491 - SYSTEM type jobs cannot be deleted, nor can they be modified. GROUP.MODIFY appears to allow the user to modify SYSTEM type jobs, but such modifications are not enforced. j) SPR 512155 - JOB.MODIFY hangs a terminal when the Operator Flag = FALSE and. QUIET = TRUE. The workaround for this is to have QUIET = FALSE (the default) when using JOB.MODIFY. 5. MOUNT MOUNT is not used with the new Spooler introduced in 8.6A/9.6A. 6. SAVERESTORE a) Restoring ISDC Code Files and Remidi On 8.5C/9.5C the three ISDC code files (ETWYOS, FOWYOS, SXTNOS) and the REMIDI files were changed to be unorganized file types. This was done so DISKANALYZER would no longer flag these files as having an internal file problem. Files that are typed as unorganized were not supported by SAVERESTORE and the File System in releases prior to 8.5C/9.5C, so these files are rejected when an attempt is made to restore them on prior O.S. levels. This is why an ALT LOAD from tape must be done before the O.S. files are restored when upgrading a system that is currently on a release prior to 8.5C/9.5C. (The only exception to this is an upgrade from 8.4E. The same changes to the above 8.5C/9.5C files were also made to the 8.4E files.) b) SPR 509944 - The rename delimiter ("^") does not work with SAVERESTORE on a restore. The file specifier, "^&,(family).node.^" will not rename the family as the files are restored. The workaround for this is to restore the files as they are and then rename them after the restore. This problem will be fixed in release 9.6B/8.6B. 7. TERM.TABLE SPR #502408 - When using the copy option of TERM.TABLE (Option #4) to copy the Primary file to the Secondary file, the copy is not successful. The workaround SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB028 Pg002 is to copy the Primary to the Secondary again without exiting the TERM.TABLE utility. The COPY will be successful the second time. 8. UPDATE a) SPR #505144 - When expanding a file, the screen display exceeds 100%. b) SPR #505145 - When expanding a file, the number of "records used" is changed to the number that was in "max records" before the expand. 9. UPDATE.OS SPR #502348 - UPDATE.OS returns an error when trying to update the O.S. before the WCS on a newly formatted disk. The workarounds for this problem include updating the WCS before the O.S., or doing an ALT LOAD to update slot 0. 10. LOGON RSC #507496 - The message "Logon disabled at this terminal, 'CR' to continue:" is displayed after a system load, if a the logon is attempted when the System Startup command file has not completed execution. Ignore this message and enter 'CR'. 11. MCSI All filelist access must be made by a user with File Security Override set to true. 12. SPOOLER a) SPR 510916 - OPENing a serial printer in BASIC that is offline and in either RESERVEd or DISCONNECTed mode causes the terminal to hang. To keep this situation from occurring, the following steps should be observed: o Serial printers being used in RESERVEd or DISCONNECTed modes should be monitored to prevent any extended periods of being offline or unplugged. o Serial printers that have been unplugged should be SUSPENDed to prevent unwanted polling. o Serial printers that may be offline for extended periods should either be SUSPENDed or placed in SPOOLed mode. This problem will be fixed in release 9.6B/8.6B. b) SPR 509923 - The FORM utility does not allow over 14 individual printers to be entered for a specific form. c) The Spooler NOTIFY function, which broadcasts a message to the top of a terminal screen when a print job has finished, will cause the screen to scroll if the cursor is on the last line of the screen. d) SPR 511331 - In RESERVE mode, @ positioning is offset to the left by one character position. This problem has been addressed by engineering and will be fixed on an upcoming release. e) SPR 510332 - It may take a few minutes to print a spooler job if the system is heavily loaded. f) BADREQUESTS File - The REQUESTS file contains names of Spooler files that have been submitted to the printer. This REQUESTS file can become corrupted when there is a fatal system error. When the REQUESTS file is observed SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB028 Pg003 to lack integrity at system load time, it is renamed to BADREQUESTS. Then a new, empty REQUESTS file is created. To re-establish Spooler access to the files named in BADREQUESTS, it is necessary to reconstruct the BADREQUESTS file with the following steps: o Boot the system into a Type 2 Load. o Reconstruct the BADREQUESTS file using DISKANALYZER. o RENAME it to REQUESTS, deleting the source file. o Reboot the system into a Type 1 Load. h) SPR 512485 - When a printer is deconfigured in TERM.CONFIG, the STNDRD form is assigned to all other printers when the system is rebooted. The forms previously assigned to these printers must then be reassigned. i) When a form is modified, all assignments for that form are withdrawn. 13. EXTTAPE EXTTAPE does not support PSAVEd programs. However, it gives an erroreous "End of Tape" message when it encounters a PSAVEd program (SPR 509607). 14. TERM.CONFIG a) The DT-4312 terminal must be configured as a DT-4309. b) SPR 511815 - The HELP screens for terminal types contain model numbers as of release 9.5E/8.5E. They have not been updated for 9.6A/8.6A, and therefore. do not contain the necessary information for configuring terminals at this level. B. BASIC 1. Running SORT from BASIC If the SORT utility has been executed from BASIC, and it encounters an error, BASIC will always return an error 0. 2. MTCS Tape Drive An MTCS tape drive cannot be accessed through BASIC. This was done by design. . 3. Program File Compatibility The significant enhancements of Business BASIC 86 introduced in 9.6A/8.6A will restrict backward compatibility. Programs written or modified on 9.6B/8.6B will. not run on releases prior to 9.6A/8.6A without recompilation. In addition, new Business BASIC 86 features introduced in 9.6A/8.6A cannot be used in programs which will be run on 9.5/8.5 or 8.4 release levels. Intersystem transport packages or the CONVERTSP utility can be used to recompile programs written or modified on 9.6/8.6, provided the new BB86 features have not been used. In most cases, where you used SAVERESTORE for tape transfer of programs to an 8.5 system, you would use EXTTAPE instead. EXTTAPE will recompile the programs as they are being transported. (All tape transfers from the new file system to the old file system require EXTTAPE.) 4. Multi-Key Files a) The following utilities will not operate on Multi-Key files: BCOM, BQR, COMP ARE, CREATE, EDIT, EXTTAPE, FILESIZE, FTF, GSR, MCSI, NFSCONVERT, OLDDIR, SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB028 Pg004 OLDTAPE. b) Two fields occupying the same space in a data record cannot both be keysets. 5. CONSOLELOCK The system will log you off while in BASIC CONSOLELOCK if both of the following 2 conditions are met: a) An END, STOP, or ESCAPE directive has just been executed in the BASIC program, and b) You enter carriage return or an invalid password 3 times. This is according to design. 6. SPR 511723 - The following code, when executed on a high speed terminal, will hang the terminal: 10 INPUT 'KL','TR',A$ 20 PRINT 'KU' Serial terminals are not affected. This problem will be fixed in release 9.6B/8.6B. C. CLI Batch Subsystem For a list of the utilities not supported by BATCH, please see the CLI Batch Subsystem section in the 9.6A/8.6A Software Announcement. D. Communications 1. MAGNET and File Transfer Facility (FTF) a) There is no automatic conversion of topology configuration files to the new Network Management Facility (NMF) configuration files when 8.6A is installed on an MPx system previously configured for B4NET/FTF. The user is responsible for printing the previous configuration information before re-configuring the MAGNET and/or FTF network with NMF or EZCONFIG. b) A reboot is necessary after the initial configuration of each system in the. MAGNET/FTF network. Any subsequent modifications to the home station parameters or subnetwork numbers also require a reboot to activate the changes. c) Care must be taken to configure enough SVC's to support all remote concurrent activities; the number of remote X.25 sites accessed at any time cannot exceed the number of SVC's configured for the X.25 link; each FTF file transfer will require its own SVC. d) FTF file transfers may experience Completion Code 149's (Network Services Timer Expired) when the system or network load is heavy, or when communicating over a LAN/WAN internetwork. e) FTF file transfers via LAN are only allowed between MPx systems. 2000/3000 systems may not co-exist on the same LAN network as MPx systems. FTF file transfers are allowed to unlike systems (MPx, 2000/3000, 13xx) over X.25 links; however, automatic data conversion for unlike character sets is NOT performed. The Intersystem Transport program, FTFIT, must be used for data conversion of FTF file transfers between unlike systems. f) Three types of X.25 packet data switches were used during the test cycle: SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB028 Pg005 o Memotec 8500 o Dynapac Model 8 o Dynapac Model 12 & Model 12A Results of the testing showed that the Memotec 8500 should only be used for networks which have a low load or when performance is not a factor. The Dynapac Model 8 can handle heavier network load but the baud rate is limited to 9600 BPS. The Dynapac Model 12 is recommended for networks with heavy loads - up to 7 MPx systems at 19.2K BPS using 128 byte packets. A problem where the Dynapac Model 12 went into a 'lockup' mode was found when running 5 or more systems at 19.2K BPS and using 256 byte packets. To prevent this problem, the packet size should be reduced to 128 bytes. (The Dynapac Model 12A is recommended over the Dynapac Model 12 to avoid MAGNET errors due to "restarts") g) To optimize throughput of X.25 communications, it is recommended that the IMLC be configured with X.25 on port A and nothing on Port B. This configuration will allow running at baud rates of 9600 BPS and above, and configuring more SVC's and larger data packet sizes. Other IMLC products such as 27xx/37xx, 3270, and Dataword should be configured on another IMLC. 9/8.6A supports up to 4 IMLC boards. h) Gateway systems in an LAN/WAN internetwork environment can pass MAGNET accesses to other systems in its subnetwork even if the gateway is configured for FTF and not MAGNET (must also be configured for X.25, LAN, and NMF). However, the reverse is not true - gateway systems configured for X.25, LAN, NMF, and MAGNET cannot pass FTF file transfers through to other systems in the subnetwork. FTF requires that gateway systems be configured for FTF in its configuration record. i) LAN/WAN internetworking has a significant impact on the gateway system. For this reason, the largest and/or least busy system on the subnetwork should be configured as the gateway system. The minimum system type for a gateway should be an 8030 if possible. j) A maximum of 63 systems may exist on a MAGNET LAN network. However, performance degradation will occur when more than 8 systems are actively transmitting data, especially during file copies. k) MAGNET event logs are initially set in the GROUP utility to LOGFILES=10 and LOGRECS=100. Although these parameters are normally sufficient, depending on network activity the event log sizes may have to be increased. To increase the size, modify the .SYSDATA.START.CMD file to include the command: GROUP.SETLOG MAGNET,LOGFILES=n,LOGRECS=n,VERIFY=FALSE where 'n' is the number desired; recommended values are LOGFILES=25 and LOGRECS=200. The logfiles will be increased with the next reboot of the system. If you wish to increase the logfiles on a temporary basis, the logfile parameters can be modified through the JOB MANAGER utility. The modifications will take effect immediately but will stay in effect only until the system is rebooted. l) If MAGNET is installed on a system already running in production mode, some degradation may be experienced. If this occurs, the system should be upgraded in terms of memory and/or cpu. 2. Asynchronous Transport Package (ATP) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB028 Pg006 ATP 4.0 will be the ATP release available on 9/8.6A. ATP 4.0 provides new features such as autodial, scheduler, line turn-around, and performance enhancements. ATP 4.0 is NOT compatible with previous releases of ATP; all systems communicating with ATP 4.0 systems must also upgrade to 4.0. ATP 4.0 is currently in beta test. Users on 9/8.6A who require ATP should contact Product Marketing on being an ATP 4.0 beta site. 3. 19.2K BPS Support TERM.CONFIG permits configuration of 8-Way and 16-Way ports with a baud rate of 19.2K. However, each 8-Way (1/2 16-Way) has an aggregate throughput of about 46K BPS and MBF terminals have an effective rate (using flow control) of, at most, 10.7K BPS. II. Hardware A. Terminals Very fast typing may cause DT-4312 terminals to drop characters. This occurence is rare. B. MCS Board 1. When Upgrading from 8.4D and Below When upgrading from 8.4D or below to 8.6/9.6, it is essential that the 4-Way (MCS board) be enabled (SW1 position 3). Not doing so will result in a dump with the fourtuple 11,13,0,0 occurring when attempting to enter a TYPE 3 LOAD after the update of slot 0. 2. MCS Revision "S" MCS PCBA PN 903374-001 at revision "S" now has the ability to be switch selectable (SW1-4) to match the different address schemes between MPx 7000/8000 Series Systems and MPx 9000, 9100, and 9500 Series Systems. The "S" revision level is not mandatory for the function of either system. a) MCS revision "S", when used in MPx 7000/8000 Series Systems, must be set for MPx 7000/8000 systems. Failure to do so will cause the system load to abort with BOOT STRAP ERROR "FFFF". b) MCS revision "S" used in MPx 9000/9100/9500 systems, (when switch selected for MPx 9000/9100/9500 systems), will allow any controller to be board addressed from the range of 1 to 63 (the board address of 16 through 31 are not valid in the MPx 9xxx system, do not address pcb's in these ranges). If set for MPx 7000/8000 systems and used in MPx 9000/9500 systems the board addresses of 32 thru 47 may only be used for the IMLC PCB. There will also be no support for memory above 12 megabytes. Revisions "T" is required for support of more than 12 megabytes of memory. The following are the switch settings for revision "S" or above MCS board: Switch SW1-4 open: MPx 7000/8000 Switch SW1-4 closed: MPx 9000/9100/9500 The following Warnings and Cautions apply to MPx 9000, 9100 and 9500 Series Systems only: I. BOSS/VS A. Dumps SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB028 Pg007 Because the BMTC is a shared memory controller, dumps to tape are not possible on the 9000 and 9500. Therefore, it is essential that the dump area on disk be large enough. See Field Bulletin #211, "Computing the Dump Area Size on MPx Systems", for further information. II. HARDWARE A. IMLC 1. The Memory Map Controller board numbers of the IMLC's must be in the range 32-47. If Revision level "S" or above of the MCS board is used and set for the model MPx 9000/9100/9500 Series Systems then this restriction is removed. 2. The "JMP C" self test jumper should be installed on the IMLC PCBA's. This is a hardware requirement for 9xxx systems only, and it is not related to the 9.6/8.6 O.S. level. For further information on this jumper, see the field bulletin titled "MPx 8xxx to 9xxx Upgrade IMLC NOT RECOGNIZED". ORIGINATOR: Nancy Prentiss SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB028 Pg008 FIB 00029 10/01/87 *** Release 8.4E Software Announcement *** 8.4E Software Announcement MAI Basic Four, Inc. is pleased to announce that the new software release, 8.4E, is now available. This is the recommended release for MPx 8000 Series Systems on 8.4. ************************************************************************* * * * PLEASE READ THE INSTALLATION INSTRUCTIONS BEFORE ATTEMPTING UPGRADE * * OR INSTALLATION. * * * * A NEW CONFIGURATION RECORD IS NOT REQUIRED WHEN UPGRADING TO 8.4E, * * UNLESS INSTALLATION OF THIS RELEASE COINCIDES WITH THE PURCHASE OF * * NEW HARDWARE OR CHARGEABLE SOFTWARE. * * * * UPGRADING TO 8.4E REQUIRES CONVERTING FILES TO A NEW FILE FORMAT, * * WHICH MAY TAKE APPROXIMATELY A DAY, DEPENDING ON SYSTEM SIZE. * * * * RELEASE 8.4E IS DESIGNED FOR USE ON MPx 8000 SERIES SYSTEMS ONLY. * * 8.4E IS NOT SUPPORTED ON THE SYSTEM 810 OR MPx 7000 SERIES SYSTEMS. * * * * WHEN UPGRADING TO 8.4E, AN ALT LOAD MUST BE DONE BEFORE THE O.S. * * FILES ARE RESTORED. THIS IS BECAUSE CERTAIN FILES WILL NOT RESTORE, * * (INCLUDING THE DRIVERS FOR THE ISDC CONTROLLERS), WHEN ON A PRIOR * * RELEASE. * * * * THE NEXT AVAILABLE UPGRADE FOR SYSTEMS ON 8.4E IS RELEASE LEVEL 8.5D. * * * ************************************************************************* Copyright 1986 by MAI Basic Four, Inc. All rights reserved. C O N T E N T S _ _ _ _ _ _ _ _ 1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . 2 2 HISTORY . . . . . . . . . . . . . . . . . . . . . . . . 3 3 BOSS/VS . . . . . . . . . . . . . . . . . . . . . . . . 4 3.1 CONFIGURATIONS . . . . . . . . . . . . . . . . . . . . 4 3.2 FILE SYSTEM . . . . . . . . . . . . . . . . . . . . . 5 3.2.1 Direct and Sort Proportional Growth . . . . . . . . 5 3.2.2 Write-through on Individual Files . . . . . . . . . 5 3.2.3 System Dumps . . . . . . . . . . . . . . . . . . . . 6 3.2.4 System Dumps-Dump to Tape . . . . . . . . . . . . . 6 3.2.5 TYPE III Load-Change Installation Parameters . . . . 7 3.2.6 Disk Errors During Power Failure Recovery . . . . . 8 3.3 UTILITIES . . . . . . . . . . . . . . . . . . . . . . 9 3.3.1 COMPARE Utility . . . . . . . . . . . . . . . . . . 9 3.3.2 DISKANALYZER Utility . . . . . . . . . . . . . . . . 9 3.3.2.1 Introduction . . . . . . . . . . . . . . . . . . . 9 3.3.2.2 Error Messages . . . . . . . . . . . . . . . . . . 9 3.3.2.3 Options . . . . . . . . . . . . . . . . . . . . . 10 3.3.2.3.1 Main Screen . . . . . . . . . . . . . . . . . . 11 3.3.2.3.2 Options Taken From Main Screen . . . . . . . . . 11 3.3.2.3.2.1 Option 1, FIND ALL FILES THAT LACK INTEGRITY. 12 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg001 3.3.2.3.2.2 Option 2, VALIDATE/RECONSTRUCT A FILE . . . . 13 3.3.2.3.2.2.1 Validation Errors by File Type . . . . . . . 14 3.3.2.3.2.2.1.1 Serial Files . . . . . . . . . . . . . . . 14 3.3.2.3.2.2.1.2 Indexed Files . . . . . . . . . . . . . . 15 3.3.2.3.2.2.1.3 Direct Files . . . . . . . . . . . . . . . 16 3.3.2.3.2.2.1.4 Code Files . . . . . . . . . . . . . . . . 18 3.3.2.3.2.2.2 Other Validation Errors . . . . . . . . . . 19 3.3.2.3.2.3 Option 3, VALIDATE ALL FILES . . . . . . . . . 21 3.3.2.3.2.4 Option 4, LOCATION OF A FILE . . . . . . . . . 21 3.3.2.3.2.5 Option 5, DISK SPACE USAGE . . . . . . . . . . 23 3.3.2.3.2.6 Option 6, CHECK DIRECTORY AND AVAILABLE SPACE 25 3.3.2.3.2.7 Option 7, LIST FILES IN A SECTOR RANGE . . . . 26 3.3.2.3.2.8 Option 8, DISKREAD (FOR HARDWARE ERRORS) . . . 27 3.3.2.3.2.9 Option 9, RECONSTRUCT AVAILABLE SPACE FILE . . 29 3.3.2.3.2.10 Option 10, RECONSTRUCT DIRECTORY FILE . . . . 30 3.3.2.4 Reconstruction of Serial Files . . . . . . . . . . 30 3.3.3 ERRORLOG Utility . . . . . . . . . . . . . . . . . . 32 3.3.3.1 By Menu or Command Without Parameters . . . . . . 32 3.3.3.2 By Command With Parameters . . . . . . . . . . . . 33 3.3.3.3 Output From the Utility . . . . . . . . . . . . . 36 3.3.3.3.1 Boot History . . . . . . . . . . . . . . . . . . 36 3.3.3.3.2 Dump History . . . . . . . . . . . . . . . . . . 37 3.3.3.3.3 Memory Errors . . . . . . . . . . . . . . . . . 39 3.3.3.3.4 Download History . . . . . . . . . . . . . . . . 41 3.3.3.3.5 Totals Summary . . . . . . . . . . . . . . . . . 42 3.3.3.3.6 Unit Error Reports . . . . . . . . . . . . . . . 43 3.3.3.3.7 Map/Analysis (for Disks) . . . . . . . . . . . . 46 3.3.4 FILESIZE Utility . . . . . . . . . . . . . . . . . . 49 3.3.4.1 Introduction . . . . . . . . . . . . . . . . . . . 49 3.3.4.2 Description of the Program . . . . . . . . . . . . 49 3.3.4.2.1 Main Screen . . . . . . . . . . . . . . . . . . 49 3.3.4.2.2 Field Descriptions . . . . . . . . . . . . . . . 50 3.3.4.3 Examples . . . . . . . . . . . . . . . . . . . . . 54 3.3.4.3.1 Node Space Calculation . . . . . . . . . . . . . 54 3.3.4.3.2 Single File Space Calculation . . . . . . . . . 56 3.3.4.3.3 Non-Existing File Space Calculation . . . . . . 56 3.3.5 GETDEVINFO Utility . . . . . . . . . . . . . . . . . 57 3.3.5.1 Shared Memory Controller ID Code (Byte 6) . . . . 57 3.3.5.2 Device Type Codes (Byte 7) . . . . . . . . . . . . 57 3.3.5.2.1 Device Status Code (Byte 8) . . . . . . . . . . 58 3.3.5.2.2 ISDC Line Number (Byte 9) . . . . . . . . . . . 58 3.3.6 OLDDIR-Old Directory List Utility . . . . . . . . . 59 3.3.6.1 Introduction . . . . . . . . . . . . . . . . . . . 59 3.3.6.2 Procedures for Using Utility . . . . . . . . . . . 59 3.3.6.2.1 By Command with Parameters . . . . . . . . . . . 60 3.3.6.2.2 By Menu or Command Without Parameters . . . . . 61 3.3.6.2.2.1 Field Descriptions . . . . . . . . . . . . . . 61 3.3.6.3 Printed Results and Displays . . . . . . . . . . . 65 3.3.6.3.1 The Display . . . . . . . . . . . . . . . . . . 65 3.3.6.3.1.1 Files with Attributes . . . . . . . . . . . . 65 3.3.6.3.2 Exiting the Utility . . . . . . . . . . . . . . 66 3.3.7 NFSCONVERT Utility . . . . . . . . . . . . . . . . . 67 3.3.7.1 Introduction . . . . . . . . . . . . . . . . . . . 67 3.3.7.2 Workspace Required for Keyed Files . . . . . . . . 67 3.3.7.3 Procedures for Using Utility . . . . . . . . . . . 68 3.3.7.3.1 By Command with Parameters . . . . . . . . . . . 68 3.3.7.3.2 By Menu or Command Without Parameters . . . . . 70 3.3.7.3.2.1 Field Descriptions . . . . . . . . . . . . . . 70 3.3.7.4 Functions Performed . . . . . . . . . . . . . . . 76 3.3.8 SAVERESTORE Utility . . . . . . . . . . . . . . . . 81 3.3.8.1 File Specifier Editing . . . . . . . . . . . . . . 81 3.3.8.2 Point-to-Point Specifiers . . . . . . . . . . . . 82 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg002 3.3.9 TERM.CONFIG Utility . . . . . . . . . . . . . . . . 82 3.3.9.1 EDT Terminal . . . . . . . . . . . . . . . . . . . 82 3.3.9.2 Serial DMP . . . . . . . . . . . . . . . . . . . . 83 3.3.10 TERM.ERRORS Utility . . . . . . . . . . . . . . . . 85 3.3.10.1 Introduction . . . . . . . . . . . . . . . . . . 85 3.3.10.1.1 Definitions . . . . . . . . . . . . . . . . . . 85 3.3.10.1.2 Information Entered . . . . . . . . . . . . . . 86 3.3.10.1.3 Information Returned . . . . . . . . . . . . . 86 3.3.10.1.4 Procedures For Using Utility . . . . . . . . . 87 3.3.10.1.4.1 By Command With Parameters . . . . . . . . . 87 3.3.10.1.4.2 By Menu Or Command Without Parameters . . . . 89 3.3.10.1.4.2.1 Option 1, DISPLAY TERMINAL ERRORS . . . . . 91 3.3.10.1.4.2.1.1 Field Descriptions . . . . . . . . . . . 91 3.3.10.1.4.2.1.2 Functions Performed . . . . . . . . . . . 95 3.3.10.1.4.2.1.3 Display Termination . . . . . . . . . . . 98 3.3.10.1.4.2.2 Option 2, START ERROR RECORDING . . . . . . 98 3.3.10.1.4.2.3 Option 3, STOP ERROR RECORDING . . . . . . 99 3.3.10.1.4.2.4 Option 4, SELECT RECORDING OPTIONS . . . . 99 3.3.10.1.4.2.4.1 Field Descriptions . . . . . . . . . . 100 3.3.10.1.4.2.4.2 Functions Performed . . . . . . . . . . 102 3.3.10.1.4.2.5 Option 5, RESET ERROR RECORDING . . . . . 103 3.3.10.1.5 Terminal Errors Utility Error Reporting . . . 104 3.4 LANGUAGES . . . . . . . . . . . . . . . . . . . . . 106 3.4.1 BASIC . . . . . . . . . . . . . . . . . . . . . . 106 3.4.1.1 Additional Logical Units . . . . . . . . . . . . 106 3.4.1.2 PRC Function . . . . . . . . . . . . . . . . . . 106 3.4.1.3 DMP Printer Mnemonics . . . . . . . . . . . . . 106 3.5 COMMUNICATIONS . . . . . . . . . . . . . . . . . . . 108 3.5.1 Asynchronous STATUS Command . . . . . . . . . . . 108 3.5.2 Asynchronous STAT Command . . . . . . . . . . . . 108 3.5.3 TBC AUTODIAL Utility . . . . . . . . . . . . . . . 109 3.5.3.1 Operational Differences . . . . . . . . . . . . 109 3.6 DIAGNOSTICS . . . . . . . . . . . . . . . . . . . . 111 3.6.1 DEMON . . . . . . . . . . . . . . . . . . . . . . 111 3.6.2 DCL and NEWX . . . . . . . . . . . . . . . . . . . 111 3.6.3 HEADS . . . . . . . . . . . . . . . . . . . . . . 111 3.7 APPLICATION SOFTWARE . . . . . . . . . . . . . . . . 112 3.7.1 DataWord . . . . . . . . . . . . . . . . . . . . . 112 3.7.1.1 Merged DataWord II . . . . . . . . . . . . . . . 112 3.7.1.2 DataWord Printer Queue Speed Enhancement . . . . 113 3.8 GENERAL INFORMATION . . . . . . . . . . . . . . . . 114 3.8.1 Software Announcement . . . . . . . . . . . . . . 114 3.8.2 Four-Tuple Messages . . . . . . . . . . . . . . . 114 3.8.3 DISKREAD Function . . . . . . . . . . . . . . . . 114 3.8.4 Disk to Disk Image Copy . . . . . . . . . . . . . 114 4 HARDWARE . . . . . . . . . . . . . . . . . . . . . . . 116 4.1 LOWEST ACCEPTABLE REVISION LEVELS FOR PCBAS . . . . 116 4.2 PARALLEL DMP DEVICE VARIANCE CONFIGURATION . . . . . 116 5 INSTALLATION . . . . . . . . . . . . . . . . . . . . . 118 5.1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . 118 5.2 NEW INSTALLATION . . . . . . . . . . . . . . . . . . 118 5.2.1 Installing the O.S. . . . . . . . . . . . . . . . 118 5.2.1.1 ALT LOAD . . . . . . . . . . . . . . . . . . . . 118 5.2.1.2 ENTER A TYPE 3 LOAD (SPECIAL FUNCTIONS) . . . . 118 5.2.1.2.1 Sizing the Dump Area (Change Volume Information 118 5.2.1.2.2 Option 1, CHANGE VOLUME INFORMATION . . . . . 120 5.2.1.2.3 Option 2, CHANGE INSTALLATION PARAMETERS . . . 120 5.2.1.2.4 Option 3, UPDATE FAMILY INFORMATION . . . . . 121 5.2.1.2.5 Option 4, INITIALIZE FAMILY DIRECTORY . . . . 122 5.2.1.3 Restoring the O.S. . . . . . . . . . . . . . . . 122 5.3 8000 UPGRADE . . . . . . . . . . . . . . . . . . . . 124 5.3.1 Introduction . . . . . . . . . . . . . . . . . . . 124 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg003 5.3.2 Preliminary Evaluation . . . . . . . . . . . . . . 125 5.3.2.1 Hardware Evaluation . . . . . . . . . . . . . . 125 5.3.2.2 File Preparation . . . . . . . . . . . . . . . . 125 5.3.2.3 8.4E Space Requirements . . . . . . . . . . . . 126 5.3.2.4 Saving Files to Tape . . . . . . . . . . . . . . 126 5.3.3 Operating System Update and File Conversion . . . 127 5.3.3.1 Installing the O.S. . . . . . . . . . . . . . . 127 5.3.3.1.1 ALT LOAD . . . . . . . . . . . . . . . . . . . 127 5.3.3.1.2 ENTER A TYPE 3 LOAD (SPECIAL FUNCTIONS) . . . 127 5.3.3.1.2.1 Option 1, CHANGE VOLUME INFORMATION . . . . 128 5.3.3.1.2.2 Option 2, CHANGE INSTALLATION PARAMETERS . . 128 5.3.3.1.2.3 Option 3, UPDATE FAMILY INFORMATION . . . . 129 5.3.3.1.2.4 Option 4, INITIALIZE FAMILY DIRECTORY . . . 129 5.3.3.2 Restoring the O.S. . . . . . . . . . . . . . . . 130 5.3.3.3 Conversion of Files . . . . . . . . . . . . . . 131 5.3.3.3.1 Tape to Disk Conversion . . . . . . . . . . . 131 5.3.3.3.2 Disk to Disk Conversion . . . . . . . . . . . 131 5.3.3.3.3 Check Files . . . . . . . . . . . . . . . . . 132 5.4 UPDATING OTHER SLOTS . . . . . . . . . . . . . . . . 133 5.4.1 Updating Slot One (1) . . . . . . . . . . . . . . 133 5.4.2 Updating WCS Slot Two (2) . . . . . . . . . . . . 133 5.4.2.1 Updating the Load Sector for REMIDI . . . . . . 134 5.4.3 Updating Slot Three (3) . . . . . . . . . . . . . 134 5.4.4 Slot Information . . . . . . . . . . . . . . . . . 135 5.4.5 Update Terminal Configuration File . . . . . . . . 135 6 RELATED DOCUMENTATION . . . . . . . . . . . . . . . . 137 INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . 138 T A B L E S and F I G U R E S _ _ _ _ _ _ ___ _ _ _ _ _ _ _ Table 3-1. File Write-through Relationships . . . . . . . 5 Figure 3-1. ERRORLOG Data Entry Screen . . . . . . . . . . 32 Table 3-2. ERRORLOG Screen Fields & Command Parameters (I) 34 Table 3-3. ERRORLOG Screen Fields & Command Parameters (II 35 Figure 3-2. Boot Load Summary Report . . . . . . . . . . . 36 Figure 3-3. Dump Summary Report . . . . . . . . . . . . . 37 Figure 3-4. Dump Detail Report . . . . . . . . . . . . . . 38 Figure 3-5. Memory Error Summary Report . . . . . . . . . 39 Figure 3-6. DOWNLOAD Summary Report . . . . . . . . . . . 41 Figure 3-7. Totals Summary Report . . . . . . . . . . . . 42 Figure 3-8. Unit Error Summary Report . . . . . . . . . . 43 Figure 3-9. Unit Error Detail Report . . . . . . . . . . . 45 Figure 3-10. Fault Map for the Volume . . . . . . . . . . 46 Figure 3-11. Error Counts for the Volume . . . . . . . . . 48 Figure 3-12. File Space Calculation Screen . . . . . . . . 50 Table 3-4. Possible Errors for NODE OR FILE NAME Field . . 51 Table 3-5. Possible Errors for RECORDS DECLARED Field . . 52 Table 3-6. Possible Errors for ACTUAL RECORDS Field . . . 52 Table 3-7. Possible Errors for RECORD SIZE Field . . . . . 53 Table 3-8. Possible Errors for KEY SIZE Field . . . . . . 53 Table 3-9. Possible Errors for OUTPUT DEVICE Field . . . . 54 Figure 3-13. Sample Output, Node Space Calculation . . . . 55 Table 3-10. DEVICE TYPE CODES . . . . . . . . . . . . . . 58 Table 3-11. Parameters of the Old Directory List Command . 60 Figure 3-14. Old Directory List Utility Data Entry Screen 61 Table 3-12. Possible Errors for Start Specifier Field . . 62 Table 3-13. Possible Errors with Point to Point Specifiers 63 Table 3-14. Possible Errors for File Type Field . . . . . 63 Table 3-15. Possible Errors for Output Device Field . . . 64 Figure 3-15. Output to VDT, Multiple Files, with Attribute 66 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg004 Table 3-16. Parameters for NFSCONVERT . . . . . . . . . . 69 Figure 3-16. NFSCONVERT Data Entry Screen . . . . . . . . 70 Table 3-17. Possible Errors for Start Specifier, not Point 72 Table 3-18. Possible Errors for Destination Field . . . . 73 Table 3-19. Possible Errors for OUTPUT DEVICE Field . . . 76 Figure 3-17. NFSCONVERT Display on the VDT . . . . . . . . 77 Figure 3-18. NFSCONVERT Output to a Printer or File . . . 79 Figure 3-19. NFSCONVERT Display with Parameters . . . . . 80 Table 3-20. EDT Defaults . . . . . . . . . . . . . . . . . 83 Table 3-21. Serial DMP Defaults . . . . . . . . . . . . . 84 Figure 3-20. Main Option Screen . . . . . . . . . . . . . 90 Figure 3-21. Display Errors Option Screen . . . . . . . . 91 Table 3-22. Possible Errors for OUTPUT DEVICE Field. . . . 95 Figure 3-22. Terminal Errors Display Screen . . . . . . . 96 Figure 3-23. Terminal Errors Summary Display Screen . . . 97 Figure 3-24. Select Recording Options Screen . . . . . . 100 Figure 5-1. Restore Screen . . . . . . . . . . . . . . . 123 Figure 5-2. Restore Screen . . . . . . . . . . . . . . . 130 Figure 5-3. Operating System Information . . . . . . . . 135 1. INTRODUCTION ____________ The following enhancements are contained in the 8.4E release: o True proportional growth for Direct and Sort files. o Write-through selectable on an individual file basis. o DISKANALYZER available in standalone as well as online mode. o DISKANALYZER reconstruction of directory and available space files. o DISKANALYZER reporting of current disk space available and disk space required for file reconstruction. o Maximum number of system printers increased to 99. o System dumps optionally dumped to tape. o System support for the DMP serial printer, including manual selection of different print modes. o System support for the EDT terminal. o New TERMINAL SERVICES ERROR utility. o Enhanced SAVERESTORE utility. o Maximum number of different files open system-wide increased from 224 to 512. o Maximum number of tasks sharing the same file increased from 64 to 256. o Improved COMPARE utility which now successfully compares BASIC program files. o A new TBC AUTODIAL feature which allows the definition and retrieval of multiple Station Lists. o Expanded ERRORLOG reporting. o Optimization of DataWord files for improved response time. o DataWord printer queue enhancements. o Number of logical channels available in BASIC increased from 32 to 64 (0-63). o Support for 8-bit character sets on all BASIC FOUR terminals. o Support for the faster 8-inch fixed disk. o An optional enhanced ATP package now available at nominal cost. Sections documented in this 8.4E announcement supersede those sections in the 8.4D announcement. It is mandatory that all PCBA revision levels are updated to proper levels (see section 4.1). Any three CPU system must have an IMLC at revision level K or higher to insure proper operation of DataWord and communications. Installation and upgrade procedures are fully documented in this announcement. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg005 Copyright 1986 by MAI Basic Four, Inc. All rights reserved. 2. HISTORY _______ Release Current Status Description _______ _______ ______ ___________ 8.1A Obsolete Introduction of the System 810 hardware and BOSS/VS software. 8.1B Obsolete Enhanced features include: 31 logical units in BASIC, increase in file system cache from 208 to 225 unique files, MULTIREELSR, family image backups, SAVERESTORE backup files having the Lack-of-Integrity bit set. Bugs were fixed in DISKANALYZER, SAVERESTORE and many of the system dumps. 8.2A Obsolete This release contained significant enhancements providing NO EXTEND BASIC, 68 serial devices, math functions, X.25 Communications, DataWord 3.0. File System write through and BULLETIN board availability. 8.2B Obsolete This release contained all of the above features but was required for the 8000 Series systems due to a change in the WCS image for that hardware. 8.2C Obsolete This release contained a WCS fix to support rezero fault clear, disk error recovery and a fix to the IMLC. 8.4A Obsolete This release contained significant enhancements including 6 megabytes of main system memory, 96 devices, 84 total serial devices, disk to disk sequential family backup, enhanced hardware error log, system load progress monitor, and fast reconstruct utility. 8.4B Obsolete Enhanced features include: 8 megabytes of main system memory, 16-port Asynchronous Controller, point-to-point file specification, QUIET mode for utilities, BASIC statement numbers up to 16000, Buffered Magnetic Tape Controller (BMTC) 1/4" tape support, S/10 Industry Standard Printer as slave printer. 8.4C Obsolete Enhanced features included: Buffered Magnetic Tape Controller, 1/2" tape support, DEDICATE with expanded error reporting, new ISDC OS for 4-way, 8-way and 16-way, FILESIZE utility. 8.4D Acceptable Contained fixes for BASIC PRECISION, 810 Only EXTTAPE, COBOL, and FILESIZE. 8.4D is the last release supported on the System 810. 3. BOSS/VS _______ 3.1. CONFIGURATIONS ______________ NOTE: Systems on software release level 8.4E will require an extra 1/4 MB of. memory for File System data structures, increasing the amount of memory required for system overhead from 1/2 MB on 8.4D to 3/4 MB on 8.4E. The maximum configuration for the MPx 8000 Series Systems, Model 8030, is as follows: 116 Devices - A combination of 8-ways, 16-ways, the 4 ports on the MCS PCBA, MDTs and HVDTs up to a total of 116 devices are supported. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg006 3 CPU sets 10 ISDCs: 16-ways (7 maximum) and/or 8-ways 32 Ghost tasks 24 High speed videos (HVDT) 8 Disk drives 4 Parallel printers 8 Megabytes of memory 2 Magnetic tape drives (MTR, MTS and/or MCS) 2 Intelligent Multi-Line Controllers (IMLC) 8 DataWord II terminals 4 TBC lines 64 3270 terminals 8 X.25 lines 2 Auto-Call Units (ACU) 99 Serial printers 99 System printers (spooler) 2 Buffered Magnetic Tape Controllers NOTE: There is a maximum of 9 memory assembly boards in any combination of 1/2 Mb, 1 Mb, 2 Mb, 4 Mb and BMTCs (a maximum of 3 boards per chassis). Models 8010 and 8020 have the same configuration limits as Model 8030 above, with the following limitations: 8010 8020 1 CPU set 2 CPU sets 2-4 Mb memory 2-6 Mb memory 20 Devices 52 Devices 19 System printers 51 System printers 3.2. FILE SYSTEM ____ ______ 3.2.1. Direct and Sort Proportional Growth ______ ___ ____ ____________ ______ Both DIRECT and SORT files grow proportionally, as the space is needed. In pre-8.4E releases, DIRECT and SORT files would expand to fill their allocated space on the disk when the first key was written. In 8.4E, DIRECT and SORT files will grow to the allocated space as the file is filled. 3.2.2. Write-through on Individual Files _____________ __ __________ _____ Before 8.4E, file write-through could only be specified for the entire system. On 8.4E, file write-through can be specified for all data files . on an individual basis. File write-through, when enabled, causes each update to a file to be written immediately to the disk or, when disabled, writes the data to the disk . when the internal buffer is full or when the file is closed. The advantage of having file write-through disabled is that accesses to the file are faster. The disadvantage to having file write-through disabled is that if the system dumps or loses power, some of the updated data may not have been written to the disk. The system wide write-through option still exists. Table 3-1 shows the SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg007 relationship between the system wide write-through and individual file write- through. Table 3-1. File Write-through Relationships _____ ____ ____ _____________ _____________ Individual file On Off ___________________ S | | | y W On | On | On | s i |-------------------| t d | | | e e Off | On | Off | m |___________________| If system wide write-through is selected, then all files will be written to disk immediately regardless of the individual write-through setting. If the system wide write-through is disabled, then only updates to those individual files that have write-through enabled will immediately be written to. disk. The utilities CREATE and UPDATE have been modified to include Kthe individual write-through option. In CREATE, an extended create will allow the user to specify write-through for that file. In UPDATE, an added prompt allows the user to change the individual write-through for that file. Files created from the BASIC directives DIRECT, SORT, SERIAL, and INDEXED (also the CREATE UTILITY default) will be set according to the write-through parameter CHANGE INSTALLATION PARAMETERS in a TYPE III load (see section 3.2.5). One exception to this rule is the creation of SERIAL files. Due to their structure, the write-through parameter is always set to disabled (false). The user may change this parameter through UPDATE. 3.2.3. System Dumps ______ _____ In the 8.4E release, when a system dump occurs, extended information is given in the form of a second four-tuple. When a system dump occurs, all terminals will display the following message: SYSTEM DUMP xxxxxxxx zzzzzzzz IN PROGRESS: PLEASE STAND BY The first field of xxxxxxxx is a four-tuple that represents the module reporting the error and the specific nature of the error. This is the same as pre-8.4E releases. The second field of zzzzzzzz is an extended or auxiliary status that gives more detail on the nature of the error. If this field appears as a four-tuple, it then represents the root software error which caused the failure. If this field is a block of eight hexdecimal digits, then the field represents the hardware status that caused the failure. This field may not be displayed at all, indicating that there is no extended status connected with the failure. Diagnostic dumps follow the same format. 3.2.4. System Dumps-Dump to Tape ______ __________ __ ____ Another new feature in 8.4E is the ability to dump the system to tape when the disk has no space available for dumps. This feature is automatically invoked by the operating system when no dump area on the disk can be located or if the dump area is too small to contain the dump. When a system dump occurs and disk SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg008 space is not available, the OS will attempt to send the dump to a tape unit. Tape drives on a BMTC cannot be used. The main reason for not using the BMTC is that there is no guarantee that the BMTC itself hasn't crashed. Also, the BMTC, being a shared memory controller that will be dumped, would have to be dumped to disk before being used. However, there is no disk dump area (if there was, we would never get here). Note: Any time Sense Switch 0 (SSW0- the bottom switch on the MCS board, leftmost on the soft control panel) is up/on before certain messages, a message to reset SSW0 is displayed until the switch is reset. The message appears as: SYSTEM DUMP xxxxxxxx zzzzzzzzz RESET SENSE SWITCH 0 (SSW0) When a system dump occurs and space is not available on disk, the system will display a message that prompts the user to select the tape drive and to set SSW0 to continue. The message appears as: SYSTEM DUMP xxxxxxxx zzzzzzzzz TAPE DRIVE # = SSW1; SSW0=CONTINUE The position of sense switch 1 indicates which drive to use: off/down means tape drive 0, on/up means tape drive 1. The system then verifies the selected unit as a tape drive and displays a message to set SSW0 when the tape is ready for the dump. The message appears as: SYSTEM DUMP xxxxxxxx zzzzzzzz SET SSW0 WHEN TAPE IS READY The tape must be properly mounted and the tape drive must be on-line. If the tape is too short or if it is not completely ready to recieve the dump, the dump will NOT complete. The dump will be lost. When SSW0 has been set, the system will display the normal IN PROGRESS dump message (see section 3.2.3). It then rewinds the tape and the cartridge is erased (this takes about two minutes). The system is then dumped directly to tape. This tape can be directly sent to MAI Basic Four, Inc. or it may be read in to a file using the DUMPTOFILE utility. The DUMPTOFILE utility has been changed to allow the user to read a dump from a tape. When sending the dump into MAI Basic Four, Inc., please label the tape on the outside as to whether the dump was directly to tape or from the DUMPTOFILE utility. 3.2.5. TYPE III Load-Change Installation Parameters ____ ___ ___________ ____________ __________ Under a TYPE III load, the Change Installation Parameters have been modified to allow the setting of the default write-through for files. The prompt will appear as: WRITE THROUGH DEFAULT ON FILE CREATE (E=ENABLED, D=DISABLED): This parameter specifies what default will be used for individual files created through BASIC file directives or through the CREATE utility (see section 3.2.2). 3.2.6. Disk Errors During Power Failure Recovery ____ ______ ______ _____ _______ ________ During a power failure recovery, if a disk error occurs, the message displayed is: SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg009 POWER FAILURE RECOVERY DISK DRIVE x: ERROR xxxxxxxxx-PLEASE FIX instead of the message POWER FAILURE RECOVERY UNSUCCESSFUL: PLEASE RELOAD SYSTEM This message will continue to be displayed until the error has been corrected or until the system is reloaded. The system will attempt to read the volume label at least once every 50 seconds, so this difficulty (if it occurs) may take some time to correct. 3.3. UTILITIES _________ 3.3.1. COMPARE Utility _______ _______ The previous COMPARE utility release was not able to compare BASIC program files completely. This new release corrects that deficiency. 3.3.2. DISKANALYZER Utility ____________ _______ 3.3.2.1. Introduction ____________ DISKANALYZER is a program designed to locate and identify problems with a. file which may hinder use of the file. Under certain conditions, damaged files may be repaired by DISKANALYZER. The directory and available space files are special system files which may also be validated and/or reconstructed by DISKANALYZER. DISKANALYZER was designed so that, if necessary, it can be run from the Type II load option. This was done so that it can analyze, and fix, problem files which may prohibit a normal load. In addition, this provides an environment wherein DISKANALYZER has sole use of the system and its resources. Thus, other tasks are prevented from modifying system data structures which must remain static for DISKANALYZER. This environment is essential for repairing either the directory file or the available space files. 3.3.2.2. Error Messages _____ ________ Error messages and warnings may appear in virtually any operation. The error codes are divided into five categories. These are: 1) disk hardware 2) logical disk structure including space management 3) file control structure 4) file data structure 5) record structure These codes are not exclusive and a given problem may "cascade" into other categories. For example, an upset in logical disk structure could create a problem in the record structure of some files. Conversely, if a record in one of the system files is corrupted, the result could be a bad disk structure. Thus, when discussing error codes for a particular operation, only the most pertinent will be mentioned although it must be remembered that other relevant messages could appear. This is particularly true in the case of disk hardware errors. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg010 DISKANALYZER Utility In the file structure area and particularly in the record structure area, there are groups of messages that apply only to a specific file type. These will be discussed along with their ramifications and possible solutions. Any abnormal condition detected by DISKANALYZER will be reported by some text message that will be preceded by a number enclosed in square brackets. These numbers are strictly internal DISKANALYZER numbers and bear no relationship to BASIC error numbers or to system four-tuples. They are included primarily as an aid in the communications that occur between the field and system support personnel. In addition to these numbered error codes, there may appear "informative messages". These do not have a condition code number and are displayed to include more detail on an already reported problem or to call a user's attention to something that may require further investigation. DISKANALYZER may receive errors that are reported by other system components. Some examples would include printer errors or running out of disk space while reconstructing a file. In the case of system errors returned to DISKANALYZER, DISKANALYZER will make no attempt to look up the text portion of the error since this will involve file I/O. Only the four-tuple will be displayed. 3.3.2.3. Options _______ DISKANALYZER receives user inputs via option screens. Other utilities make heavy use of files for screen displays and screen manipulation. DISKANALYZER, on the other hand, was designed with the ability to run without relying on the presence or good integrity of any file on the system. That is, the program and all its screens exist solely in the image part of the system and are outside the domain of the file system. For this reason, DISKANALYZER does not have access to the pool of common software used by the utilities. Hence, there may be some instances where DISKANALYZER screens and screen handling may be slightly different from those used by the utilities. Any differences that do exist are minor and should not present any ambiguities or confusion to the user. The functions of the motor bar (CTL) keys are identical. The one exception to the above is the HELP screen. This has been left as a file since accidental corruption would not hinder the operation of DISKANALYZER. The help screens are available by entering DISKANALYZER.HELP from the ! sign. Help is not availble via the normal mode of entering a '?' in a data entry field. Also, Help is not available from the type II load. DISKANALYZER Utility For some operations, the creation of files (e.g. SPOOL files) by DISKANALYZER is forbidden. If output to a printer is selected, a dedicated printer may be mandatory as this is a guarantee that a file will not be created. If a dedicated printer is required, DISKANALYZER will issue a message that the user must run the DEDICATE utility before proceeding. There are two levels of DISKANALYZER screens consisting of the main menu screen and ten subordinate data entry screens. Subsequent sections will discuss the options presented by each screen. 3.3.2.3.1. Main Screen ____ ______ Execution of DISKANALYZER can be initiated in three ways. One way is by SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg011 entering DISKANALYZER at the command level (i.e. "!DISKANALYZER"). Another is by entering "!UTILITY" and selecting "SYSTEM UTILITIES" from the first menu and then "DISKANALYZER" from the System Utilities menu. A third way is by performing a type II load and choosing option 3 (DISKANALYZER) from the load menu. In all the above cases, the main screen for DISKANALYZER will appear. This screen permits the user to select one of the ten DISKANALYZER operations. The main screen appears as follows: MAI BASIC FOUR, INC. DISK ANALYZER OPTIONS: 1. FIND ALL FILES THAT LACK INTEGRITY 2. VALIDATE/RECONSTRUCT A FILE 3. VALIDATE ALL FILES 4. LOCATION OF A FILE 5. DISK SPACE USAGE (MISSING/OVERLAPPING) 6. CHECK DIRECTORY AND AVAILABLE SPACE FILES 7. LIST FILES IN A SECTOR RANGE 8. DISKREAD (FOR HARDWARE ERRORS) 9. RECONSTRUCT AVAILABLE SPACE FILES (TYPE II LOAD) 10. RECONSTRUCT DIRECTORY FILE (TYPE II LOAD) ENTER OPTION NUMBER: xxx 'CTL-IV' TO EXIT Note that the last two options involve reconstruction of system files and require the type II load environment. Any attempt to execute them from a normal load will be disallowed and an appropriate error message will be issued. 3.3.2.3.2. Options Taken From Main Screen _______ _____ ____ ____ ______ The following subsections will describe the purpose and intent of each of the individual options. DISKANALYZER Utility 3.3.2.3.2.1. Option 1, FIND ALL FILES THAT LACK INTEGRITY. ______ __ ____ ___ _____ ____ ____ __________ This screen will appear if option 1 is selected. MAI BASIC FOUR, INC. DISK ANALYZER FIND ALL FILES THAT LACK INTEGRITY FAMILY NAME: xxxxxxxx OUTPUT DEVICE: xxxxxx PAUSE ON FULL SCREEN (Y/N): xxx ENTRIES CORRECT (Y/N): xxx First, the family name is entered. The user default family will be displayed at the bottom of the screen and will be the DISKANALYZER default if only a carriage return is entered. Next, an output device is selected. This can be a standard printer mnemonic such as LP, P*, P1, P2, (etc.) or a VDT. The default is VDT. Output will always go to the VDT even if a printer is selected. Output to a file is not allowed by this option. If Pause On Full Screen is true (the default), DISKANALYZER will stop and request input with each full screen SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg012 of output. DISKANALYZER can be made to switch to a non-pause mode by pressing CTL II whenever input is requested. The "entries correct" field is the only field that has no default. The Lack-Of-Integrity stamp is a flag kept in the control segment of all files on the system. This flag is set whenever file updates have not been written to disk and reset when they have. Thus, "permanent" lack of integrity exists when. the flag is set and no processes have the file opened. This error condition is more likely to occur on systems that do frequent updates to files with Write-through disabled. Writing files back to disk on these systems are more infrequent and therefore the files become more vulnerable to unexpected system halts (long term power outages, dumps, hangs, etc.). This particular option tests only the Lack-Of-Integrity flag and not the actual state of the file. (The validate option should be used if complete file validation is desired.) It tests all files and lists the name of each file as it examines it. There is only one message that applies directly to the bad integrity situation and it is: DISKANALYZER Utility [31] FILE LACKS INTEGRITY Files that lack integrity are not usable (cannot be opened) and must be reconstructed (see Option 2 below). Reconstruction will usually make the file usable again although one or more of the most recent updates may be lost. 3.3.2.3.2.2. Option 2, VALIDATE/RECONSTRUCT A FILE ______ __ ____________________ _ ____ This screen will appear if Option 2 is selected. MAI BASIC FOUR, INC. DISK ANALYZER VALIDATE/RECONSTRUCT A FILE PRIMARY PREFIX: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx FILE NAME: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx NEW FILE NAME: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx OUTPUT DEVICE: xxxx PAUSE ON FULL SCREEN (Y/N): xxx ENTRIES CORRECT (Y/N): xxx The top line (Primary Prefix) is filled in by DISKANALYZER and is the first node within the user's prefix. It is the node that DISKANALYZER will search if a fully qualified name is not specified. DISKANALYZER will ignore the primary prefix shown on the top line if a fully qualified name is given on the next line. (A fully qualified name starts with a '.' or with a family specification). The "New File Name" on the third line is optional. If given, a "new file name" which is not fully qualified will have the primary prefix from the top line appended to the front of this name. Any legal file name in this field is both a flag that reconstruction is to be performed and that the new file is to have this as its file name. The absence of any name signifies a validation pass only. The reconstruct and validate passes are identical operations except that reconstruction involves writing each record to the new SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg013 file as it is encountered. This is the primary entry point for checking a user's file for consistency and reconstructing it if necessary. Reconstruction is performed only when a new file name is given. If a new name is given and there is nothing wrong with the old file (it validates successfully), the new file will still be generated. Validation of a file should be performed whenever a file is suspect. The reconstruct phase is not normally performed until after a validation pass has indicated the file needs reconstruction. Sequential, Indexed, Direct, Sort, and Code files can be validated. Code files are the only type which cannot be reconstructed but they are tested for valid control segments and for hardware readability. DISKANALYZER will check for numerous anomalies and report any it finds during a validate or reconstruct phase. The actual conditions reported are addressed in a subsequent subsection. When Direct files are reconstructed, the new file will be written in ascending sequential key order. This usually results in a change in the file's structure. The relation between key and index (relative record position) will be lost. System files may be validated (but not reconstructed) from this option by specifying a colon as the first character of the name. The system files which may be validated are: :AVSPxx, :DIR, and :OVERLAY. The :AVSPxx file is a special disk space management file. Since there is one of these files for each member in the family, the member number is included as part of the name. That is, the 'xx' in :AVSPxx represents the member index in the specified family. i.e. xx = 01, 02, ..NN for members 01, 02, .. NN respectively. The directory file (:DIR) is also a special file. This file contains information to use all files that exist for the given family. The :OVERLAY file is simply a chunk of disk space allocated as a memory extension and never contains any permanent data. Validation of this file consists only of reading for hardware errors. 3.3.2.3.2.2.1. Validation Errors by File Type __________ ______ __ ____ ____ There is wide a assortment of condition reports that could appear using this option so they will be categorized according to file type. 3.3.2.3.2.2.1.1. Serial Files ______ _____ Serial files are divided into fixed size blocks, each of which typically is in the range of 4K to 16K (8K is the default). Problems which may be deteced by DISKANALYZER usually involve problems with record headers or block headers. [72] LOST SERIAL FILE RECORD # This error is caused by an illegal record length being encountered. The remainder of this block will be skipped. Streams of 'Lost Record' messages will be emitted until the record count is one less than the record index of the first record in the next block. These records will be lost during reconstruction also. [73] SKIPPING SERIAL BLOCK WITH FIRST INDEX # LOOKING FOR INDEX # The current sequential record count (index) is greater than the value in the SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg014 next block to be processed. Blocks are skipped until an index is found with a value greater than the current one. Any skipped blocks will result in the loss of all records within the block. [74] INVALID SERIAL BLOCK #. SKIP AND ADVANCE TO NEXT DISKANALYZER is at the proper block boundary but the following block is not a valid one. The only recourse is to skip to the next block. Any records within the block will not be reconstructed. [47] FILE CLAIMS # RECORDS. # ACTUALLY FOUND At the end of reading the file, the record count is compared with the value in the control segment and this message is displayed if they are different. If previous lost record (or block) messages have appeared, this would be indicative of the number of records lost. A file that lacks integrity might be expected to. display this also. These lost records are not recoverable by reconstruction. 3.3.2.3.2.2.1.2. Indexed Files _______ _____ Indexed files are fairly simple structures consisting of fixed size blocks. Problems generally involve the block headers. [71] RR RECORD IS LARGER THAN 32K SYSTEM LIMIT There is a 32K upper limit on the record size of these files. An illegal value here means the entire file is probably bad and no records are recoverable. Nevertheless, DISKANALYZER will continue with the operation since there are additional checks on record validity. [70] RR HEADER INDICATES NEITHER INUSE NOR VACANT, INDEX = #, COUNT = # Each header has a byte with a unique value indicating "inuse" (record has been written and has not been deleted) or "vacant" (record has been deleted or was never written). Anything other than these two unique values is considered invalid. The index and a running total of bad indices are displayed. Only valid "inuse" records will be reconstructed. [47] FILE CLAIMS # RECORDS. # ACTUALLY FOUND The final (valid) record count is compared against the value in the control segment and the above message will be displayed if they are different. This message could also appear as a result of the file lacking integrity. Assuming the value in the control sector is valid, this is indicative of the number of records lost (or gained) while reconstructing. 3.3.2.3.2.2.1.3. Direct Files ______ _____ Keyed (Direct) files have the largest collection of problem codes. [27] INVALID LEVEL NUMBER IN B-TREE The cause of this error is usually a previous catastrophic system failure at the time a record was being written. DISKANALYZER can recreate the key from the data record and, hence, can write the record by key. No record will be constructed more than once. [29] UNACCOUNTED FOR SPACE WITHIN FILE If a record has no corresponding key, and is not in the free record chain, then SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg015 it is unaccounted for. The record address (block number and record number within block) of this record will be displayed. If the control byte indicates that the record was not deleted, then it will be picked up if the file is being reconstructed. [30] RECORD ACCOUNTED FOR MORE THAN ONCE This.problem is simliar to unaccounted for space in reverse. It has a key and is probably in the deleted record chain. If it is in the deleted record chain then this message will be accompanied by the message "B-Tree path led to a deleted record". Such a record will be reconstructed (only once) if the control byte within the record indicates it is in use. [31] FILE LACKS INTEGRITY The file was being written to and the updates did not get written to disk. (Probably because of a system dump.) This message was more thoroughly explained in the section on integrity checking. The file must be reconstructed before it can be used. [32] REQUESTED SECTOR # IS BEYOND LAST FILE EXTENT Something caused DISKANALYZER to read beyond the area allocated for the file. This could be caused by corrupted data within the file resulting in an improper sector number calculation or by the physical space allocation being incorrect. This is a serious error and could be catastrophic to the operation depending upon the actual values encountered. In some situations, DISKANALYZER will be able to recover all records by reading in index order. [33] PREVIOUS ERRORS TOO SEVERE TO CONTINUE Some errors (which have just been previously reported) are too severe even for DISKANALYZER to overcome. This typically is caused by a primary control structure being totally unorganized. [34] B-TREE PATH LED TO A DELETED RECORD The control byte of a record indicates the record has been deleted. The "deleted byte" takes precedence when reconstructing the file. That is, the deleted records will not be restored. [42] B-TREE SECTOR EXPECTED. NOT FOUND. HEADER WORD = There is a special tag in B-Tree sectors such that DISKANALYZER (and the file system for that matter) will know if it has encountered bad B-Tree data. The 4-byte data that it did find is displayed (in hex) along with this message. A bad B-Tree usually does not mean the file data records are bad and reconstruction quite often recovers 100 percent of the records. [43] READNEXT KEY: KEY IN B-TREE DOES NOT MATCH KEY IN DATA RECORD The hidden key in the data record did not match the B-Tree value. Both keys will be displayed in the lines that follow. For purposes of reconstruction, the hidden key within the data record is assumed to be the valid one. [44] UNABLE TO OPEN NEW FILE FOR OUTPUT When reconstructing a file, DISKANALYZER opens a new file for output as any other program would and is a candidate for the same types of failure. If the open fails, the file system reports the reason for the failure as a four tuple. This four tuple will echoed by DISKANALYZER along with the above message. No attempt will be made to display the associated text message. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg016 [45] FS ERROR WRITING NEW FILE The file system had an error while in the process of writing out the new (reconstructed) file. The error four tuple will also be displayed. The state of the file being reconstructed will not be the cause of this error. That is, this error is usually caused by a bad system directory or a full disk problem. [46] FREE (DELETED) RECORD CHAIN IS BROKEN The deleted record chain has been broken. If this is the only problem detected, the consequence will not be too severe. 100 percent of the records can be reconstructed. However, corrective action should be taken immediately since continued writing to this file can result in further damage. [47] FILE CLAIMS # RECORDS. # ACTUALLY FOUND The number of records found does not equal the number declared in the control sector. This is normally the result of a file lacking integrity. Only those records actually found will be reconstructed. [48] RECORD NUMBER # IN SHORT RECORD BLOCK NUMBER # IS TOO LARGE The record number referred to is the record number within a block. There is an upper limit of this number equal to the blocking factor of the file. If this limit is exceeded, both the record number and block number will be displayed. 3.3.2.3.2.2.1.4. Code Files ____ _____ Code files are checked for control sector errors and disk errors only. They cannot be reconstructed. (Note, however, that they can be recreated by recompilation.) These errors are discussed in the following section. 3.3.2.3.2.2.2. Other Validation Errors _____ __________ ______ A number of errors apply across all file types. These generally involve disk errors and control sector incongruities. Before validating any file, the control sector values are checked to make sure they have a sensible range. This check is performed to make sure that the control sector is reasonably intact. A demolished control sector (or sectors) generally means the file is unrecoverable. The following list of messages pertain to control sector range checking: [6] - WRONG FILE FORMAT LEVEL (CREATED UNDER ANOTHER FILE SYSTEM) [7] - BAD VALUE FOR FILE TYPE [8] - NEITHER A CODE FILE NOR A DATA FILE [9] - VALUE FOR HIGH WATER MARK IS INVALID [10] - BAD BLOCKING FACTOR [11] - FAMILY MEMBER FOR FIRST EXTENT IS OUT OF RANGE [12] - FAMILY MEMBER FOR ADDITIONAL EXTENTS IS OUT OF RANGE [13] - INDICATED RECORD SIZE IS INVALID SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg017 [14] - ACTUAL NUMBER OF RECORDS DECLARED IS NOT WITHIN A LEGAL RANGE [15] - RECORDED MAXIMUM RECORD LENGTH IS CORRUPTED [16] - FREE HEAD POINTER CORRUPTED [17] - B-TREE COUNT IS CORRUPTED [18] - POINTER TO USAGE RIGHTS IS CORRUPTED [19] - USAGE RIGHTS STRING EXTENDS PAST INDICATED SIZE OF CONTROL SEGMENT [20] - PARTITION MAP LOCATION IS LOST [21] - B-TREE LOCATION (WITHIN FILE) IS LOST [22] - CORRUPTED CONTROL SEGMENT If the last error - 'corrupted control segment' - appears, the file is considered to be hopelessly damaged and further validation or reconstruction is inhibited. If a hardware error occurs while the disk is being read, the hardware status bits will be fully expanded to text messages along with the disk and precise sector number. The complete set of messages is: [23] HARDWARE (DISK) ERROR DISK UNIT #, STARTING SECTOR # - UNSOLICITED SEEK ERROR - DATA VERIFY ERROR - SEEK ERROR - INVALID DISK COMMAND - DATA SYNC ERROR - ID SYNC ERROR - ID CRC ERROR - SECTOR NUMBER ERROR - ALTERNATE CYLINDER ERROR - DRIVE FAULT ERROR - DATA CRC ERROR - HEAD/CYLINDER ERROR - DISK NOT READY - DISK OFF LINE - DIAGNOSTIC CYLINDER ERROR - SERVO ERROR AND NOT SEEK ERROR - GUARD BAND ERROR - UP SPEED ERROR - TIME OUT ERROR - NOT ON CYLINDER ERROR - WRITE AND READ GATE FAULT - MULTI TAG FAULT - POWER LOSS - READ DATA FAULT - PLOLOCK ERROR - READ ONLY AND WRITE - WRITE OFFTRACK INOPERATIVE - WRITE FAIL INOPERATIVE - AC WRITE INOPERATIVE - MULTI HEAD INOPERATIVE SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg018 3.3.2.3.2.3. Option 3, VALIDATE ALL FILES ______ __ ________ ___ _____ This screen will appear if Option 3 is selected. MAI BASIC FOUR, INC. DISK ANALYZER VALIDATE ALL FILES FAMILY NAME: xxxxxxxx OUTPUT DEVICE: xxxx PAUSE ON FULL SCREEN (Y/N): xxx ENTRIES CORRECT (Y/N): xxx This option validates a file just as in Option 2, but the names are automatically retrieved in name (key) order from the directory file. Each name is printed on the screen as it is being validated. Any problems which DISK ANALYZER detects will be listed out after the file name. The possible problem areas and associated messages are exactly the same ones which may appear in Option 2. System files (:DIR, :AVSPxx, and :OVERLAY) are not validated when using this option. 3.3.2.3.2.4. Option 4, LOCATION OF A FILE ______ __ ________ __ _ ____ This screen will appear if Option 4 is selected. MAI BASIC FOUR, INC. DISK ANALYZER LOCATION OF A FILE PRIMARY PREFIX: xxxxxxxxxxxxxxxxxxxxxxxxxx FILE NAME: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx OUTPUT DEVICE: xxxx PAUSE ON FULL SCREEN (Y/N): xxx ENTRIES CORRECT (Y/N): xxx The purpose of this option is to find the physical location of a file, including all its extents, on a disk (or disks). With this option, it is permissible to specify either a full file name, just the beginning characters of a file name, or just a single dot ('.') character. If the file name does not begin with a dot or a family specification, the primary prefix from the first line will be appended to the front. DISKANALYZER will find the first file with a name greater than or equal to the input string and continue until the end-of-directory or until CTL-IV is entered. The output consists of the size and location of each file extent as shown in the following example: FILENAME : .EXAMPLE.FOR.DOC EXT MEM FRelStrt Length $FRelStrt$ $Length$ Vol Start $Vol Start$ 0 1 0 642 $000000$ $000282$ 33701 $0083A5$ 1 1 642 320 $000282$ $000140$ 34343 $008627$ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg019 2 1 962 320 $0003C2$ $000140$ 34663 $008767$ EXT is the extent index and MEM is the family member index on which the extent resides. FRelStrt is the file relative starting sector number of the extent. This will always be zero for the first extent. Length is the size of the extent in sectors. Both FRelStrt and Length are repeated in hex notation as a convenience for the user. Vol Start is the (disk) volume relative sector number where the extent starts. This is repeated in hex notation. Note that FRelStrt + Length should equal FRelStrt of the next extent. The Volume starting sector for a given extent can be anywhere within the domain of the family space managed by the file system. This option will also display the location of a system file when a colon is entered followed by a full system file name. These names are :DIR, :OVERLAY, and :AVSP01, :AVSP02,.. :AVSPxx where xx is the highest member number in the specified family. DISKANALYZER Utility 3.3.2.3.2.5. Option 5, DISK SPACE USAGE ______ __ ____ _____ _____ This screen will appear if Option 5 is selected. MAI BASIC FOUR, INC. DISK ANALYZER DISK SPACE USAGE (MISSING/OVERLAPPING) FAMILY NAME: xxxxxxxx OUTPUT DEVICE: xxxx PAUSE ON FULL SCREEN (Y/N): xxx ENTRIES CORRECT (Y/N): xxx The file system uses an internal (system) file to keep track of what space is free and available for use. The sum of the available and inuse space should account for all sectors within the domain of a particular file system family. While creating a file, available space is taken from the AVSPxx file(s) and recorded in the directory file. The converse of this occurs on a delete. Space formerly occupied by the deleted file is recorded in the AVSPxx files. If the system encounters an unexpected halt during this type of process, the transaction may not complete and some space will remain in limbo (neither in use nor available). DISKANALYZER will locate and report this space by "summing" the AVSPxx and directory file records and then looking for "holes". It is conceivable that files may overlap each other (share disk space) or be accounted for as both in use AND available. Such a situation is very rare and should not occur even after a system dump. This is guarded against by the order in which system files are updated. Nevertheless, DISKANALYZER checks for this condition. If it occurs, DISKANALYZER will print out the names and locations of the files (and/or available spaces) that are sharing sectors. An example of both lost and shared SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg020 space follows: ******** FOUND UNACCOUNTED FOR SECTORS ON MEMBER NO. 1 UNACCOUNTED FOR SECTORS = 37216 -> 37221, SIZE 6, SUM 6 UNACCOUNTED FOR SECTORS = 41337 -> 41339, SIZE 3, SUM 9 UNACCOUNTED FOR SECTORS = 57679 -> 57716, SIZE 38, SUM 47 ******** OVERLAPPING FILE SPACE DETECTED ON MEMBER NO. 1 SHARED FILE SECTORS = 64302 -> 64308 AFFECTED FILE : .FILENAME1 AFFECTED FILE : .FILENAME2 DISKANALYZER Utility AFFECTED FILE : (AVAILABLE SPACE) In the part of the example showing the shared (overlapping) space, the same area is accounted for three times. Two files are sharing space which indicates that the directory contains bad data. In addition, this space is also marked as available which means that the :AVSP01 file has a record with invalid (or at least inconsistent) data. It is possible to recover from this situation by applying the DISKANALYZER options that reconstruct system files. This process is somewhat risky so it should be attempted only after backing up the family (if possible). The order of the steps outlined below is extremely important. 1) Backup the family to tape (file by file) 2) Run the Diskread option (option 8) and check for disk errors. 3) At least one of the two files must be deleted. It would be prudent to delete both. If this is undesirable, determine if either FILENAME1 or FILENAME2 is bad by a file validation process. It is possible that neither is bad and both can be saved by copying one of the files to a new location (another disk or a tape) and deleting its source. 4) Re-execute this option (5) to make sure two file names do not share the same space. Overlaps involving available space is the expected result at this point. (Perhaps also involving one file.) 5) Reconstruct the :AVSP01 file. This should correct missing and overlapping space. 6) Run the DISKANALYZER option (6) to check the Directory and Available Space files. Files sharing space are not necessarily the result of Directory/AVSPxx file format problems. 7) If step 6 detects problems in the directory, the :DIR file should be reconstructed (option 7) at this point. If step 6 does not indicate any problem, :DIR should not be reconstructed. 8) Steps 4) through 7) should be repeated until there are no more problems with space or directory records. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg021 DISKANALYZER Utility 3.3.2.3.2.6. Option 6, CHECK DIRECTORY AND AVAILABLE SPACE FILES ______ __ _____ _________ ___ _________ _____ _____ This screen will appear if Option 6 is selected. MAI BASIC FOUR, INC. DISK ANALYZER CHECK DIRECTORY AND AVAILABLE SPACE FILES FAMILY NAME: xxxxxxxx OUTPUT DEVICE: xxxx PAUSE ON FULL SCREEN (Y/N): xxx ENTRIES CORRECT (Y/N): xxx This option works very much like the Validate All Files option. First, it validates the system directory file (:DIR) and then the available space files (:AVSPxx files for xx = 1,2..Members-In-Family). The names are displayed per the convention of using colons while being validated. Both the :DIR and :AVSPxx are special files. For these, several distinct validation steps are taken. A check is made to ensure the space within the file is being properly managed. All keysets are checked for correct order and that they point to the correct data blocks. Finally, the file is read in index order, a key is built from the data using the key definition tables. Any errors or discrepancies uncovered by these tests usually call for rebuilding the affected system file or the entire family. However, before doing this, it is best first to check for overlapping space. The sequence of events to perform this operation is discussed under Option 5 - "Disk Space Usage (Missing/Overlapping)". DISKANALYZER Utility 3.3.2.3.2.7. Option 7, LIST FILES IN A SECTOR RANGE ______ __ ____ _____ __ _ ______ _____ This screen will appear if Option 7 is selected. MAI BASIC FOUR, INC. DISK ANALYZER LIST FILES IN A SECTOR RANGE DRIVE NUMBER: xxx FAMILY NAME: xxxxxxxx FAMILY INDEX: xxx START SECTOR: xxxxxxx SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg022 END SECTOR: xxxxxxx OUTPUT DEVICE: xxxx PAUSE ON FULL SCREEN (Y/N): xxx ENTRIES CORRECT (Y/N): xxx This option does the inverse of listing the location of a file. That is, given a sector, it finds the file that occupies it. When the start sector number is entered, its value will become the default value for the end sector, ( i.e., the default range of sectors is one). The option also works for a range of sectors by specifying an end sector greater than the start sector. In this case, there may be many files that occupy a given range. The following is an example of the output after a request for the names of the files occupying sectors 9000 to 10000. FILENAME EXTENT STRTSCT - ENDSCT $STRTSCT - $ENDSCT .THIS.ONE 0 8317 9984 $00207D - $002700 .THIS.ONE.ALSO 0 9985 11588 $002701 - $002D44 Note that the full extent of the file is displayed. That is, extents are not truncated at the requested boundaries (9000 to 10000 in this example). This is one of the few options that requires the drive number as input. The family name and family index will be displayed after the drive number is entered. (The Family utility option 1 will display the correlation between drive number and Family Name/Family Index). DISKANALYZER Utility DISKANALYZER begins by searching directory records for all files with extents in the given range and listing the qualifying extents. If the entire directory is searched and all the space has not been accounted for, DISKANALYZER will continue with the available space file and other areas that are reserved for the system. Sectors of available space that fall within the specified range will be listed out in parentheses as (AVAILABLE SPACE). System file names and other system sectors will be listed out with a preceeding colon (:DIR for example). If by chance some of the space is not accounted for, it will be obvious only by the absence of some sector ranges in this list. Option 5 should be used as the check for lost space. The task will terminate as soon as all the requested area has been accounted for. Because of this, this option may or may not detect files that share space. Option 5 should be used as the check for shared space. 3.3.2.3.2.8. Option 8, DISKREAD (FOR HARDWARE ERRORS) ______ __ ________ ____ ________ _______ This screen will appear if Option 8 is selected. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg023 MAI BASIC FOUR, INC. DISK ANALYZER DISKREAD (FOR HARDWARE ERRORS) DRIVE NUMBER: xxx FAMILY NAME: xxxxxxxx FAMILY INDEX: xxx START SECTOR: xxxxxxx END SECTOR: xxxxxxx OUTPUT DEVICE: xxxx PAUSE ON FULL SCREEN (Y/N): xxx ENTRIES CORRECT (Y/N): xxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx HIGHEST DRIVE NUMBER = Since disk hardware errors are intimately related to loss of file data, this option is provided to search out hardware errors as fast as possible. On a given disk, it will locate DISKANALYZER Utility an error down to the sector level and give a precise report of the hardware status. Disk status is returned as a 32 bit word with 30 of these bits representing a particular drive condition. If set, a drive error has occurred. The text corresponding to these bits was previously presented under Validate a File option and are repeated here for convenience. - UNSOLICITED SEEK ERROR - DATA VERIFY ERROR - SEEK ERROR - INVALID DISK COMMAND - DATA SYNC ERROR - ID SYNC ERROR - ID CRC ERROR - SECTOR NUMBER ERROR - ALTERNATE CYLINDER ERROR - DRIVE FAULT ERROR - DATA CRC ERROR - HEAD/CYLINDER ERROR - DISK NOT READY - DISK OFF LINE - DIAGNOSTIC CYLINDER ERROR - SERVO ERROR AND NOT SEEK ERROR - GUARD BAND ERROR - UP SPEED ERROR - TIME OUT ERROR - NOT ON CYLINDER ERROR - WRITE AND READ GATE FAULT SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg024 - MULTI TAG FAULT - POWER LOSS - READ DATA FAULT - PLOLOCK ERROR - READ ONLY AND WRITE - WRITE OFFTRACK INOPERATIVE - WRITE FAIL INOPERATIVE - AC WRITE INOPERATIVE - MULTI HEAD INOPERATIVE When used in conjunction with Option 7 - LIST FILES IN A SECTOR RANGE, exactly what file is affected and what sectors in the file can be determined. If the file is not a code file, the reconstruct option should be able to recover all but the data in the block containing the bad sector. This assumes the block is not needed in order to access other file blocks. To aid in selecting beginning and ending sector numbers, the file system start and end sectors are displayed at the bottom. No value is enforced on the selection except that the end sector be greater than or equal to the start sector. DISKANALYZER Utility Since the drive number is input, the highest drive number on the system is displayed and any attempt to input a value above this will be refused. The Family utility is helpful for displaying the correlation between drive numbers and family names/indices. 3.3.2.3.2.9. Option 9, RECONSTRUCT AVAILABLE SPACE FILE ______ __ ___________ _________ _____ ____ This screen will appear if Option 9 is selected. MAI BASIC FOUR, INC. DISK ANALYZER RECONSTRUCT AVAILABLE SPACE FILE FAMILY NAME: xxxxxxxx OUTPUT DEVICE: xxxx PAUSE ON FULL SCREEN (Y/N): xxx ENTRIES CORRECT (Y/N): xxx This option is one of the special ones that must be run from a type II load. The program will insist that this be the case before allowing this option to run. Normally, this option is invoked to regain lost space which is indicated by Option 5 - DISK SPACE USAGE (MISSING/OVERLAPPING). The available space file is rebuilt from scratch by finding all sectors not being occupied by files in the directory or by a few file system reserved sectors. These new "records of empty sectors" are written out via special file system entry points and then the system is automatically switched over to using the new available space file. If some unexpected problem is encountered, the system will not SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg025 be instructed to switch over to the new AVSPxx file and it will remain as though this option had never been run. DISKANALYZER Utility 3.3.2.3.2.10. Option 10, RECONSTRUCT DIRECTORY FILE ______ ___ ___________ _________ ____ This screen will appear if Option 10 is selected. MAI BASIC FOUR, INC. DISK ANALYZER RECONSTRUCT DIRECTORY FILE FAMILY NAME: xxxxxxxx OUTPUT DEVICE: xxxx PAUSE ON FULL SCREEN (Y/N): xxx ENTRIES CORRECT (Y/N): xxx This is another option that must be run from a type II load since the present directory must remain static while performing this operation. DISKANALYZER uses its ability to read records in index order from the available space area. It then writes these records to a new file through a special entry point in the file system. If nothing catastrophic happens, two disk parameters will be switched so the file system will begin using the new directory file the next time the system is loaded. If a serious, unforeseen error does occur, the disk parameters will not be switched and the system will behave as though this option had never been run. 3.3.2.4. Reconstruction of Serial Files ______________ __ ______ _____ The following procedure should be followed for the reconstuction of Serial files through DISKANALYZER: 1) Reconstruct the file with DISKANALYZER. If no error messages are displayed, no further work is required - the file can be used as is. 2) If DISKANALYZER displays messages indicating a break in the record sequence, (error message numbers 78 and 79 stating: "SYNC ERROR AT RECORD n", where "n" is the record index of the first record beyond the break sequence), then further work is required: a) If ERROR 78 is displayed, the records that follow probably do not belong in the file, and a new record should be written at the indicated index, or the record at the previous index should be read and rewritten. This DISKANALYZER Utility will get rid of the subsequent records that do not belong in the file. It should not be necessary to read through SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg026 the file. b) If ERROR 79 is displayed, it is possible that one or more blocks of data were not recovered, but that records beyond the break were recovered successfully. In this case, it is necessary to inspect the records after the indicated break in sequence and determine if the records should be removed as in 2(a) above, or left in the file, with the knowledge that the intervening records were lost. 3) If error messages other than 78 and 79 are displayed during the reconstruction, it is advisable to examine the last few records of the reconstructed file. In many cases, the last record will be corrupt. In this case, the next to last record in the reconstructed Serial file should be read and rewritten, causing the last record to be dropped. NOTE: File Write Through affects the recoverability of Serial files. System wide Write Through is not sufficient to assure that all Serial file records are promptly written to disk. To get full Write Through, the file-specific Write Through must be set. This will have a noticeable impact on performance, but, without it, up to 8 K bytes of data may be lost. ERRORLOG Utility 3.3.3. ERRORLOG Utility ________ _______ The ERRORLOG utility allows you to generate a report that lists errors/events recorded in the ERRORLOG file(s). The data in the ERRORLOG file(s) can either be errors or events recorded for reference purposes, e.g., bootload and download events. Records can be selected for inclusion in the report based upon the type of error/event or the time of occurrence. All reports can be produced in SUMMARY format and some can be produced in DETAILED format. 3.3.3.1. By Menu or Command Without Parameters __ ____ __ _______ _______ __________ To run the ERRORLOG utility, enter "7" from the System Utilities Menu, or enter the command "ERRORLOG" without parameters in console mode. The utility displays the screen shown in Figure 3-1. Figure 3-1. ERRORLOG Data Entry Screen ______ ____ ________ ____ _____ ______ __________________________________________________________________ | | | MM/DD/YY MAI BASIC FOUR, INC. HH:MM | | ERROR LOG UTILITY | | | | | | | | ERROR FILE SPECIFIER : | | STARTING RECORD NO. : 1 | | ERROR REPORT GROUP : U | | UNIT LIST : D*,P*,R* | | ERROR REPORT TYPE : S | SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg027 | START DATE : 00/00/00 | | START TIME : 00:00:00 | | END DATE : 12/31/59 | | END TIME : 23:59:59 | | OUTPUT DEVICE : VDT | | | | | | ENTRIES CORRECT (Y/N): | | | |________________________________________________________________| Use the following steps to enter the data. Prompts for each field are provided at the bottom of the screen as the cursor moves from field to field. Refer to Tables 3-2 and 3-3 for a detailed description of each field. To enter the default value for any field, press RETURN. 1. Enter the ERROR FILE SPECIFIER. 2. If the error file specifier is an individual file, enter ERRORLOG Utility the number of the first record to be read. 3. Enter the letter for the ERROR REPORT GROUP to be listed in the report. 4. If the ERROR REPORT GROUP is "U", enter the UNIT LIST to be included in the report. 5. Enter the ERROR REPORT TYPE to specify the report format. 6. Enter the earliest error date. 7. Enter the time on the earliest date. 8. Enter the latest error date. 9. Enter the time on the latest date. 10. Enter the OUTPUT DEVICE where the report is to be sent. If the OUTPUT DEVICE is a file which already exists, the following prompt appears: FILE ALREADY EXISTS, DO YOU WISH TO DELETE OR APPEND TO THE FILE (D/A/N): Enter "D" to delete the existing file. Enter "A" to append this report to the existing file. Enter "N" to enter a different OUTPUT DEVICE. 11. Enter "N" to return to the ERROR FILE SPECIFIER field. Enter "Y" to generate the report. 3.3.3.2. By Command With Parameters __ _______ ____ __________ The ERRORLOG utility can also be accessed by entering the command ERRORLOG with parameters in console mode, or as a program directive from BASIC. The format is: ERRORLOG FileSpecifier [ {,RECNO=<1>} {,GROUP=} {,LIST=} {,TYPE=} {,BDATE=<00/00/00>} {,BTIME=<00:00:00>} {,EDATE=<12/31/59>} {,ETIME=<23:59:59>} SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg028 {,OUTPUT=} {,OUTACTION=} {,QUIET=} ] The parameters used with the ERRORLOG command in console mode and the corresponding ERRORLOG screen fields are described in Tables 3-2 and 3-3. ERRORLOG Utility Table 3-2. ERRORLOG Screen Fields & Command Parameters (I) _____ ____ ________ ______ ______ _ _______ __________ ___ _____________________________________________________________________________ | SCREEN FIELD | PARAMETER | DESCRIPTION | |_______________|___________|_______________________________________________| | | | | | ERROR FILE | File | The name of an individual file or a node | | SPECIFIER | Specifier | composed of one or more files containing the | | | | error/event records to be used to produce | | | | the report. There are no restrictions on the | | | | names used for these files because ERRORLOG | | | | looks at the file's attributes to determine | | | | its eligibility for use in generating the | | | | report. (Default = .ERRORLOG.) | | | | | | STARTING | RECNO | The record number of the first record to be | | RECORD NO. | | read from an individual file only. The | | | | range is 1 to 799. (Default = 1) | | | | | | ERROR REPORT | GROUP | Specifies the kind of error/event records | | GROUP | | that will be selected for the report. The | | | | records are classified according to the kind | | | | of error or event that caused them to be | | | | entered into the file. The report groups are:| | | | | | | | B = type 1 boot history | | | | D = system dump history | | | | E = memory errors | | | | L = down load history | | | | T = totals for each kind of error/event | | | | U = disk, tape, and printer errors | | | | | | | | (Default = U) | | | | | | UNIT LIST | LIST | The UNIT type records to be listed in the | | | | report. UNIT LIST can only be used with | | | | report group "U". The UNIT LIST can be: | | | | | | | | o an individual unit specified by device | | | | letter and number, e.g., D0, R2, P1 | | | | (for Disk 0, Tape 2, and Printer 1) | | | | | | | | o all units belonging to a device group | | | | specified by the device letter and an | | | | asterisk (*), e.g., D*, R*, P* | | | | | | | | o any combination of the two previous | | | | categories separated by commas, e.g., | | | | D*,R0,R1,P*. | | | | | | | | (Default = D*,R*,P*) | SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg029 |___________________________________________________________________________| ERRORLOG Utility Table 3-3. ERRORLOG Screen Fields & Command Parameters (II) _____ ____ ________ ______ ______ _ _______ __________ ____ _____________________________________________________________________________ | SCREEN FIELD | PARAMETER | DESCRIPTION | |_______________|___________|_______________________________________________| | | | | | ERROR REPORT | TYPE | Specifies one of the following format types: | | TYPE | | | | | | S = SUMMARY - used for all report groups | | | | | | | | D = DETAILED - used for DUMP and UNIT | | | | report groups only | | | | | | | | M = MAP/ANALYSIS - used for the UNIT report | | | | group with disks only (UNIT LIST = D*) | | | | | | | | (Default = S) | | | | | | START DATE | BDATE | START DATE and START TIME define the earliest | | | | time-stamp on an ERRORLOG record that can be | | START TIME | BTIME | accepted for the report. The default START | | | | DATE, 00/00/00, corresponds to January 1, 1960| | | | the earliest date recognized by BOSS/VS. | | | | | | END DATE | EDATE | END DATE and END TIME define the latest | | | | time-stamp on an ERRORLOG record that can be | | END TIME | ETIME | accepted for the report. | | | | The default END DATE, 12/31/59, corresponds | | | | to December 31, 2059, the latest date | | | | recognized by BOSS/VS. The END DATE and | | | | END TIME combination must be later than the | | | | START DATE and START TIME combination. | | | | | | OUTPUT DEVICE | OUTPUT | Specifies the device or file where the report | | | | output is to be sent. If output to the VDT | | | | is selected, output pauses when the screen | | | | is full and waits for an operator input to | | | | continue. If output to a file or printer is | | | | selected, output is duplicated on the VDT | | | | without a pause for an operator input when | | | | the screen is full. | | | | | | | | If output to an existing file is selected on | | | | the ERRORLOG screen, the file can be appended,| | | | deleted and then recreated, or the output | | | | device can be respecified. ERRORLOG displays | | | | screen prompts for this purpose. | | | | For the command parameter, OUTACTION, use "A" | | | | to append, "D" to delete and then recreate | | | | the file, or "N" for no action. If you use | | | | "N" and the file exists, ERRORLOG aborts. | |___________________________________________________________________________| ERRORLOG Utility 3.3.3.3. Output From the Utility ______ ____ ___ _______ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg030 The first line of all reports contains the name of the report and the Selection (date/time) Interval used as part of the record selection criteria. The second line contains the name of the errorlog file from which the data was read. With the exception of the MAP report and the MEMORY ERROR Summary, the next four lines contain the column headings for the fields in the report. Examples of each report type are shown in the following figures. 3.3.3.3.1. Boot History ____ _______ The BOOT LOAD SUMMARY Report provides a history of all System Loads which occurred during the Selection Interval. Figure 3-2. Boot Load Summary Report ______ ____ ____ ____ _______ ______ _____________________________________________________________________________ | | | MM/DD/YY MAI BASIC FOUR, INC. HH:MM | | ERROR LOG UTILITY | | | | BOOT LOAD SUMMARY: 11/15/85-08:00:00 TO 12/31/59-23:59:59 | | LOG FILE: (P807).ERRLOG.D851115T02010861 | |---------------------------------------------------------------------------| | Rec Load Load Memory Boot WCS | | # Date Time CPUs Bit Vector Version Version | |---------------------------------------------------------------------------| | 1 11/16/85 16:01 2 FFFFFF0000000000 2.0.0.4 5.3.2 | | 5 11/19/85 08:19 2 FFFFFF0000000000 2.0.0.4 5.3.2 | | 22 11/20/85 16:30 3 FFFFFF0000000000 2.0.0.4 5.3.2 | | 27 11/21/85 07:39 3 FFFFFF0000000000 2.0.0.4 5.3.2 | | 36 11/22/85 07:27 3 FFFFFF0000000000 2.0.0.4 5.3.2 | |___________________________________________________________________________| Rec # - The relative index of the ERRORLOG record. Load Date - The date when the System Load was initiated. Load Time - The time when the System Load was initiated. CPUs - The number of CPUs on-line after System Load. Memory Bit - The amount of memory that was enabled after the Vector System Laod was complete. Each bit represents 128K bytes or 256K bytes, depending upon the kind of memory board installed. The example in Figure 3-2 was run with 128K byte memory boards,and shows 3 megabytes of memory enabled. ERRORLOG Utility Boot - The release level of the System Loader that executed Version the load operation. WCS - The release level of the firmware that was installed at System Load time. 3.3.3.3.2. Dump History ____ _______ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg031 The DUMP SUMMARY Report and the DUMP DETAIL Report provide a history of all System Dumps which occurred during the Selection Interval. Figure 3-3. Dump Summary Report ______ ____ ____ _______ ______ _____________________________________________________________________________ | | | MM/DD/YY MAI BASIC FOUR, INC. HH:MM | | | ERROR LOG UTILITY | | | | | | DUMP SUMMARY: 11/15/85-08:00:00 TO 12/31/59-23:59:59 | | LOG FILE: (P807).ERRLOG.D851115T02010861 | |---------------------------------------------------------------------------| | Rec Dump Dump Process Prs CPU Main Auxiliary | | # Date Time Name # # Error Code Error Code | |---------------------------------------------------------------------------| | 3 11/16/85 16:02 *INIT 7 2 8,234,11,4 8,234,59,124 | | 24 11/20/85 16:37 T16 22 0 2,10,18,25 1,20,0,25 | | 38 11/21/85 18:42 T4 29 2 2,0,8,10 | | 50 11/22/85 10:34 T3 29 1 28,254,0,255 | | 61 11/25/85 11:45 *IDLE0 3 2 2,0,4,10 | |___________________________________________________________________________| Rec # - The relative index of the ERRORLOG record. Dump Date - The date when the System Dump was initiated. Dump Time - The time when the System Dump was initiated. Process - The name of the process that was running when Name the System Dump occurred. In most non-forced dumps, this is also the process that caused the dump. In forced-dumps, this is the process that was executing when the dump started, and whose system resources were used for completing the dump. If an asterisk (*) precedes the Process Name, it is the name of a System Process. Prs # - The number of the process that was running at the time the System Dump occurred. ERRORLOG Utility CPU # - The CPU on which the process was executing when the System Dump occurred. Main Error - This four-tuple identifies the area of the system Code that was executing when the System Dump occurred. In most cases, this also identifies the cause of the dump. Auxiliary - This four-tuple identifies the specific cause of Error Code the dump when the Main Error Code only identifies the area of system failure. This field is blank if no Auxiliary Error Code is present. The DUMP DETAIL Report includes all the information provided in the DUMP SUMMARY Report and also the text associated with SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg032 the Main Error Code. Figure 3-4. Dump Detail Report ______ ____ ____ ______ ______ _____________________________________________________________________________ | MM/DD/YY MAI BASIC FOUR, INC. HH:MM | | ERROR LOG UTILITY | | | | | | DUMP DETAIL: 11/15/85-08:00:00 TO 12/31/59-23:59:59 | | LOG FILE: (P807).ERRLOG.D851115T02010861 | |---------------------------------------------------------------------------| | Rec Dump Dump Process Prs CPU Main Auxiliary | | # Date Time Name # # Error Code Error Code | |---------------------------------------------------------------------------| | 3 11/16/85 16:02 *INIT 7 2 8,234,11,4 8,234,59,124 | | Dump Msg: FamAVS: FAMenableFam: ReadRootSector #2 failed | | 24 11/20/85 16:37 T16 22 0 2,10,18,25 1,20,0,25 | | Dump Msg: Instruction Fault in Connector Module | | 38 11/21/85 18:42 T4 29 2 2,0,8,10 | | Dump Msg: Block Exit found locked PIB in frame mark workspace list | | 50 11/22/85 10:34 T3 29 1 28,254,0,255 | | Dump Msg: Non-fatal dump invoked for testing purposes | | 61 11/25/85 11:45 *IDLE0 3 2 2,0,4,10 | | Dump Msg: Diagnostic dump forced in time slicer handler | |___________________________________________________________________________| Dump Msg - The text associated with the Main Error Code. If no text can be found, the following substitute message appears in the report: <<<<< NO TEXT AVAILABLE . . . >>>>> ERRORLOG Utility 3.3.3.3.3. Memory Errors ______ ______ The MEMORY ERROR SUMMARY Report provides a count of the number of memory errors that occurred during the Selection Interval, he addresses of the most recent 24 (32) errors, and the version of the Kernel that was executing during data collection. Figure 3-5. Memory Error Summary Report ______ ____ ______ _____ _______ ______ _______________________________________________________________________________ | MM/DD/YY MAI BASIC FOUR, INC. HH:MM | | ERROR LOG UTILITY | |. | |. | | MEMORY ERROR SUMMARY: 08/01/85-08:00:00 TO 08/31/85-23:59:59 | | LOG FILE: (P807).ERRLOG.D850815T11511705 | |------------------------------------------------------------------------------ | ADDRESSES OF 24 MOST RECENT ERRORS | |. | | 100000 100000 200000 100000 100000 100000 200000 000000 | |. 000000 000000 000000 000000 000000 000000 000000 000000 | |. 000000 000000 000000 000000 000000 000000 000000 000000 | |. | SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg033 |. | | ERROR COUNTS BY ADDRESS RANGE | |. | |000000 - 080000 - 100000 - 180000 - 200000 - 280000 - 300000 - 380000 - 400000| | 0 0 5 0 1 1 0 0 | |400000 - 480000 - 500000 - 580000 - 600000 - 680000 - 700000 - 780000 - 800000| |. 0 0 0 0 0 0 0 0 | |800000 - 880000 - 900000 - 980000 - A00000 - A80000 - B00000 - B80000 - C00000| |. 0 0 0 0 0 0 0 0 | |. | |. | |Kernel Version: 5.3.7.0 | |______________________________________________________________________________ Addresses of the 24 (32) Most Recent Errors This is a display of the most significant byte of each of the 24 (32) addresses that most recently reported parity errors. The newest entry in the list is in the upper left corner; the oldest is in the lower right corner. New values are entered into the list at the upper left corner, forcing the oldest entries to "fall off" at the lower right corner. For ECC errors reported by system release levels of 8.4D or earlier, the 32 most recent error addresses are reported. Later releases report the 24 most recent error addresses only. ERRORLOG Utility In Figure 3-5, the most recent error occurred somewhere within the address range of 100000 and 1FFFFF. The same is also true of the second most recent error, although there is no way of knowing whether the second error was caused by the same memory address as the first. Since the list is not yet full, the oldest error occurred somewhere within the address range of 200000 and 2FFFFF. Error Counts By Address Range This is a display of the number of errors recorded within the range of addresses that surround the count from above. The count indicates how many errors have been recorded within the address range bounded below by the left hand address, and above by the right hand address. In Figure 3-5, there were 5 memory errors detected in addresses that were greater than or equal to 100000 and less than 180000. By comparing this to the addresses of the most recent errors above, it can be seen that there were 5 errors detected in the address range 100000 through 1FFFFF. However, the two errors occurring in the address range 200000 through 2FFFFF are seen to have been caused by one error in the range 200000 through 280000 and one in the range 280000 through 300000. This correlation between the two sections of the report is only possible when fewer than 24 (32) errors have been recorded, since only then do the counts in the two sections agree. Once the first address is "pushed off" the bottom of the recent history list, establishing this correspondence is no longer possible. The version of the kernel that reported the errors is also SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg034 included in the report. ERRORLOG Utility 3.3.3.3.4. Download History ________ _______ The DOWNLOAD SUMMARY Report provides a chronological history of all Serial Controller Down-Load events occurring during the Selection Interval. Down Loading of a controller can be initiated in response to an operator request or as a result of an initialization request occurring during System Load. Figure 3-6. DOWNLOAD Summary Report ______ ____ ________ _______ ______ _____________________________________________________________________________ | MM/DD/YY MAI BASIC FOUR, INC. HH:MM | | ERROR LOG UTILITY | | | | | | DOWNLOAD SUMMARY: 11/15/85-08:00:00 TO 12/31/59-23:59:59 | | LOG FILE: (P807).ERRLOG.D851115T02010861 | |---------------------------------------------------------------------------| | Rec D/L D/L Process Ctlr Ctlr | | # Date Time Name # Type Completion status | |---------------------------------------------------------------------------| | 26 11/20/85 16:32 T3 63 IMLC Normal Completion | | 47 11/22/85 14:13 T16 32 8way Normal Completion | | 55 11/22/85 15:02 *INIT2 6 16way File not found | | 82 11/25/85 07:38 T03 0 4way 4way Normal Completion | |101 11/27/85 06:44 *MIDNITE 4 8way 8way Normal Completion | |___________________________________________________________________________| Rec # - The relative index of the ERRORLOG record. D/L Date - The date when the Down Load was initiated. D/L Time - The time when the Down Load was initiated. Process - The name of the process that was running when Name the Down Load was initiated. If an asterisk (*) precedes the Process Name, it is the name of a System Process and the associated Down Load event was not initiated by operator request. Two such processes are: *MIDNITE and *INIT2. *MIDNITE reinitializes the controllers during power-fail recovery and during normal power-up. *INIT2 is responsible for initialization of controllers during System Load. It only records attempts to Down Load that fail. Ctlr # - The number of the downloaded controller. Ctlr Type - The type of controller that was downloaded. ERRORLOG Utility Status - Indicates the success or failure of the Down Load. If the Down Load failed, the reason for SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg035 the failure is stated in this field. 3.3.3.3.5. Totals Summary ______ _______ The TOTALS SUMMARY Report provides a count of all errors/events by group that were recorded in a specific LOG FILE during the Selection Interval. By selecting this report and designating a START DATE several days earlier than the current date, it is possible to determine what the most prevalent errors were during recent days. Then the specific area can be explored in more detail using one of the other reports. Figure 3-7. Totals Summary Report ______ ____ ______ _______ ______ _______________________________________________________________________________ | MM/DD/YY MAI BASIC FOUR, INC. HH:MM | | ERROR LOG UTILITY | | |. | |. | TOTALS SUMMARY: 08/05/85-08:00:00 TO 12/31/59-23:59:59 | | LOG FILES PREFIX: (P807).ERRLOG. | |-----------------------------------------------------------------------------| | Boot- Down- --Mem-- Disk Tape Prtr Un- | | LOG FILE Loads MMC Dumps Loads ECC ECX Errs Errs Errs known Total| |-----------------------------------------------------------------------------| | D850815T11511705 107 214 34 37 0 2 124 124 155 0 797 | | D850927T09050940 111 219 60 50 0 0 175 77 105 0 797 | | D851118T16010861 25 50 20 6 0 0 15 10 27 0 153 | |_____________________________________________________________________________| LOG FILE - The name of the file from which the totals were obtained. The LOG FILE name preceded by the LOG FILES PREFIX is the fully qualified file name. Boot Loads - The number of Boot Load events recorded. MMC - The number of times a census of all Memory Mapped Controllers was recorded. Dumps - The number of System Dumps recorded. Down Loads - The number of Down Load events recorded. --Mem-- - The number of single bit parity errors in main ECC ECX memory recorded. ECC errors are recorded exclu- sively by BOSS/VS releases 8.4D and earlier. ECX errors are recorded exclusively by BOSS/VS releases 8.4E, 8.5C and later. ERRORLOG Utility Disk Errs - The number of disk errors recorded. Tape Errs - The number of tape errors recorded. Prtr Errs - The number of printer errors recorded. Unknown - The number of errors recorded that do not belong to one of the other error groups. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg036 This column should always be 0. 3.3.3.3.6. Unit Error Reports ____ _____ _______ The UNIT ERROR SUMMARY Report and the UNIT ERROR DETAIL Report provide a list of all errors that occurred during the Selection Interval on the devices specified in the UNIT LIST. Figure 3-8. Unit Error Summary Report ______ ____ ____ _____ _______ ______ _______________________________________________________________________________ | MM/DD/YY MAI BASIC FOUR, INC. HH:MM | | ERROR LOG UTILITY | |. | |. | | UNIT ERROR SUMMARY: 11/15/85-08:00:00 TO 12/31/59-23:59:59 | | LOG FILE: (P807).ERRLOG.D851115T02010861 | |------------------------------------------------------------------------------ | Rec Err Err Unit Dev I/O Volume Disk| | # Date Time # Name Status Operation Ser # Hd Cyl Sc Area| |------------------------------------------------------------------------------ | 8 11/19/85 09:51 48 D3 80080000 Normal Read 3016297 2 184 1 FS | | 20 11/20/85 10:19 18 R0 81800000 Read Ignore FM | | 46 11/22/85 13:34 64 D5 88021000 Retry Read 3000022 2 725 16 FS | | 63 11/25/85 13:14 18 R0 81840000 Read Ignore FM | | 85 11/26/85 10:20 33 D2 80080000 Normal Read 1050 7 0 9 FS | |______________________________________________________________________________ Rec # - The relative index of the ERRORLOG record. Err Date - The date when the error occurred. Err Time - The time when the error occurred. Unit # - The address of the unit where the error occurred. Dev Name - The device name, computed from the unit address and based upon the devices present at the most recent system load. ERRORLOG Utility NOTE: Device numbering is established at run-time and is based upon the devices present. Unit errors are recorded by Unit Address and the same Unit Address may correspond to different device numbers at different times based upon system configuration at the time the system is brought up. This may result in a device number that is not the one where the error actually occurred. For UNIT ERROR Reports, device numbers are derived from the Unit Address by calculation on the basis of the current configuration. Status - The status word returned by the controller, and indicating the nature of the error. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg037 I/O - The operation in the command list that was Operation executing at the time the error occurred. Volume - The volume serial number of the disk reporting Ser # the error. For tape and printer errors, this field is blank. Hd - The disk head where the error occurred. For tape and printer errors, this field is blank. Cyl - The disk cylinder where the error occurred. For tape and printer errors, this field is blank. Sc - The disk sector where the error occurred. For tape and printer errors, this field is blank. Disk Area - The area on the disk where the error occurred. For tape and printer errors, or errors occurring on disk volumes not currently mounted on the system, this field is blank. The areas are: FS = File System Area TS = Relocation Track Summary Area RT = Relocation Track Area SM = Segment Manager Shadow Area DA = Dump Area ERRORLOG Utility The UNIT ERROR DETAIL Report includes all the information provided in the UNIT ERROR SUMMARY Report and also the fields described after Figure 3-9. Figure 3-9. Unit Error Detail Report ______ ____ ____ _____ ______ ______ _______________________________________________________________________________ | MM/DD/YY MAI BASIC FOUR, INC. HH:MM | | ERROR LOG UTILITY | |. | |. | | UNIT ERROR DETAIL: 11/15/85-08:00:00 TO 12/31/59-23:59:59 | | LOG FILE: (P807).ERRLOG.D851115T02010861 | |------------------------------------------------------------------------------ | Rec Err Err Unit Dev I/O Volume Disk| | # Date Time # Name Status Operation Ser # Hd Cyl Sc Area| |------------------------------------------------------------------------------ | 8 11/19/85 09:51 48 D3 80080000 Normal Read 3016297 2 184 1 FS | |Retries=2 Retry Count=2 Device Type=Disk F P154 144Mb Sector: 23221 | |STATUS: Abort flag, Data CRC/ECC Err | |. | |IOCB: 00300001 10B80001 00C44FB8 00000900 80080000 02020000 00000000 00050C48| | 00000004 00080000 00D28000 00010900 000000B1 002E0669 04800068 00000000| |------------------------------------------------------------------------------ | 20 11/20/85 10:19 18 R0 81800000 Read Ignore FM | |Retries=10 Retry Count=0 Device Type=Tape MTR 1/2" TDP | |STATUS: Abort flag, Short Record, Hard Error | |. | |IOCB: 2012002E 00001000 000531EC 00001000 81800000 0A008000 00000000 08B50000| | 00000000 00800000 08DD0017 162C1752 00000082 08B50018 048005A8 00000554| |______________________________________________________________________________ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg038 Retries - The maximum number of retries specified for the device. Retry - The number of retries attempted before the error Count was reported. Device - A full description of the device based upon the Type device name. Since this may not be the actual device that produced the error, caution is advised before associating the error with the device description given in this field. Refer to the "Dev Name" field described previously. Sector - The absolute sector number that corresponds to the head, cylinder, and sector appearing above. For tape and printer errors, this field is blank. STATUS - The meaning of each bit in the Status word. ERRORLOG Utility IOCB - A hexidecimal display of the contents of the IOCB at the time the error occurred. The complete description can be found in the IO Private module interface. 3.3.3.3.7. Map/Analysis (for Disks) ____________ ____ ______ The MAP/ANALYSIS report may be requested for DISK units only. It provides a count of specific errors by volume that occurred during the Selection Interval, and a track map for that volume showing where the errors occurred. The MAP/ANALYSIS consists of two reports, MAP and COUNT ANALYSIS, but is considered to be a single report TYPE. For the MAP/ANALYSIS reports, ERRORLOG gathers data from all the specified files and prints or displays a list of the files used. This list is followed by the reports on a per-volume basis. Figure 3-10. Fault Map for the Volume ______ _____ _____ ___ ___ ___ ______ _____________________________________________________________________________ | MM/DD/YY MAI BASIC FOUR, INC. HH:MM | | ERROR LOG UTILITY | | | | | | MAP AND ANALYSIS: 11/15/85-08:00:00 TO 12/31/59-23:59:59 | | FAULT MAP FOR VOLUME 3000022 DISK TYPE: P144 | |---------------------------------------------------------------------------| | | | Cylinder/100 | | | | Head 0---1---2---3---4---5---6---7---8---9---0---1--- | | | | 0 ................................................ | | 1 ................................................ | | 2 ..........2...................................*. | | 3 .........3...................................... | | 4 ................................................ | SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg039 | 5 ................................................ | | 6 ................................................ | | 7 ................................................ | |___________________________________________________________________________| Fault Map - The volume serial number of the disk on which the for Volume errors are being reported. Disk Type - The MAI Basic Four designation of the type of disk on which the errors are being reported. ERRORLOG Utility Head - Each vertical unit of the track map corresponds to one head position. As many rows are provided as are required by the size of the disk. Cylinder - Each horizontal unit of the track map /100 corresponds to 25 cylinders. The first column represents cylinders 0 through 24, the second represents 25 through 49, and so on. As many columns are provided as are required by the size of the disk. For each head position and cylinder range, the symbols and decimal digits used for the MAP mean the following: o A dot (.) indicates no errors reported. o A single decimal digit (1 through 9)indicates the number of errors specified. NOTE: Errors in adjacent columns should not be read as one number. For example, 3 errors on head 4, cylinders 300 through 324, and 5 errors on head 4, cylinders 325 through 349, will appear next to each other on the map. This should be read as two pieces of data (3 and 5) and NOT as 35 errors. o An asterisk (*) indicates more than 9 errors reported. ERRORLOG Utility The Error Counts for Volume counts the type of errors found on the disk and summarizes them in tabular form. Figure 3-11. Error Counts for the Volume ______ _____ _____ ______ ___ ___ ______ _____________________________________________________________________________ | MM/DD/YY MAI BASIC FOUR, INC. HH:MM | | ERROR LOG UTILITY | | | | | | MAP AND ANALYSIS: 11/15/85-08:00:00 TO 12/31/59-23:59:59 | | ERROR COUNTS FOR VOLUME 3000022 DISK TYPE: P144 | |---------------------------------------------------------------------------| | Hard Soft | | Error Errors Errors Totals | SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg040 |---------------------------------------------------------------------------| | Drive Faults 0 0 0 | | ID Sync Errors 0 0 0 | | Sector Number Errors 0 0 0 | | ID CRC Errors 0 0 0 | | Data Sync Errors 0 11 11 | | Data CRC Errors 0 5 5 | | Other Errors (except Alt Trk) 0 0 0 | |---------------------------------------------------------------------------| | Totals: 0 16 16 | |___________________________________________________________________________| FILESIZE Utility 3.3.4. FILESIZE Utility ________ _______ 3.3.4.1. Introduction ____________ FILESIZE is a program which calculates the amount of disk space files will require on the 8.4E New File System. It works for existing files, as well as non-existing files (where calculations are based on user-input file attributes). It may be run on a pre-8.4E system to estimate disk requirements for conversion to 8.4E. For files on a 13XX system the user will need to run *SIZE to get the estimated space the file would need on an 8.4E system. For existing files, a user may specify a family, node, or individual file name(s). The calculations are based on the default growth parameters of the existing file(s). For non-existing files, the user enters filetype, declared number of records, actual number of records, record size and key size (if applicable), and the program bases its calculations on default growth parameters. The figures provided by this program should be used as estimations only, because actual disk requirements are affected by indeterminable factors such as disk fragmentation and file usage. A summary of FILESIZE's capabilities is shown below: 1. Calculates the total file space taken under one entire family or one specific node. 2. Calculates the space taken for one single file specified by the user. 3. Calculates the space taken for a non-existing file based upon the attributes provided by the user. 3.3.4.2. Description of the Program ___________ __ ___ _______ 3.3.4.2.1. Main Screen ____ ______ FILESIZE Utility SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg041 Figure 3-12. File Space Calculation Screen ______ _____ ____ _____ ___________ ______ FILE SPACE CALCULATION NODE OR FILE NAME: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX FILE TYPE : XXXXXXX RECORDS DECLARED : XXXXXXX ACTUAL RECORDS : XXXXXXX RECORD SIZE : XXXXX KEY SIZE : XX OUTPUT DEVICE : XXXXXXXXXXXXXXX ENTRIES CORRECT (Y/N) : XXX 3.3.4.2.2. Field Descriptions _____ ____________ The fields in the FILESIZE Data Entry Screen (figure 3-12) are as follows: 1. NODE OR FILE NAME The NODE OR FILE NAME field is the name of a node or a file. The message appears on line 22 and line 23: ENTER NODE OR FILE NAME IF USER INTENDS TO CALCULATE ALL FILE SPACE IN A NODE OR A SPECIFIC FILE. Enter the name of a node or a file. If the name is not fully specified, e.g., .ABC. or ABC.TEXT then the default family name is added to the node or file name e.g., (DISK).ABC. or (DISK).ABC.TEXT. If the user enters a node, 'CR', 'CTL-I', or 'CTL-III' moves the cursor to the OUTPUT DEVICE field. If the user enters an existing file name, the program retrieves all required attributes of that file and displays them at the corresponding fields on the screen. The cursor finally stops at the OUTPUT DEVICE field. If the user wants to do a non-existing file space estimation, CTL-I or 'CR' will move the cursor to the FILE TYPE field and leave the NODE OR FILE NAME field blank. FILESIZE Utility Table 3-4. Possible Errors for NODE OR FILE NAME Field _____ ____ ________ ______ ___ ____ __ ____ ____ _____ ----------------------------------------------------------- | ERROR MESSAGE | REASON FOR ERROR | ----------------------------------------------------------- | BAD FILE NAME | File name is invalid. | ----------------------------------------------------------- SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg042 | FILE DOES NOT EXIST | File does not exist | ----------------------------------------------------------- | NODE DOES NOT EXIST | The node does not exist. | ----------------------------------------------------------- | FILE IS LOCKED | File is locked and cannot be | | | opened. | ----------------------------------------------------------- | DISK VOLUME NOT MOUNTED| File specified is not located | | | on a volume that is not mounted| ----------------------------------------------------------- | INVALID FAMILY NAME | Family name has more than 8 | | | characters. | ----------------------------------------------------------- Please note that the above error messages and all other messages specified for the FILESIZE utility, are those found on the 8.4D system. The error messages may be slightly different on an 8.4E system. 2. FILE TYPE This field is the type of a file which can be specified by the user or retrieved from an existing user-specified file. The message appears on line 22: ENTER FILE TYPE - INDEXED, SERIAL, DIRECT, SORT (I/SE/D/S) The user may enter the file type by typing in I/i, S/s, SE/se, or D/d, then the full name of the file type will be displayed, i.e., INDEXED, SORT, SERIAL, DIRECT. However, if the user has entered a file name at the NODE OR FILE NAME field, the program will immediately retrieve the file type attribute and display the full name on the screen. 3. RECORDS DECLARED This field is the declared number of records which is either requested by the user or retrieved from an existing user-specified file. The message appears on line 22: ENTER NO OF RECORDS DECLARED. RANGE 1..8388607 FILESIZE Utility The user enters the number, or the program provides the information if the file exists. Table 3-5. Possible Errors for RECORDS DECLARED Field _____ ____ ________ ______ ___ _______ ________ _____ ---------------------------------------------------------- | ERRROR MESSAGE | REASON FOR ERROR | ---------------------------------------------------------- | Number of records | Number is not in the range. | | declared must be | | | between 1..8388607 | | ---------------------------------------------------------- 4. ACTUAL RECORDS SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg043 This field is the number of records actually being used by an existing file or hypothetically 'in-use' by a non-existing file. It can be specified by the user or retrieved from the file if the user has specified the file at the NODE OR FILE NAME field. The message appears on line 22: ENTER ACTUAL NO. OF RECORDS The user enters the number of records hypothetically 'in-use' by the non-existing file. If the file type is Indexed, Sort, or Direct, this number must be less than or equal to the declared number of records. Table 3-6. Possible Errors for ACTUAL RECORDS Field _____ ____ ________ ______ ___ ______ _______ _____ ----------------------------------------------------------- | ERROR MESSAGE | REASON FOR ERRORS | ----------------------------------------------------------- | Actual records must be | User-specified actual number | | <= declared # records | of records is not in the range | | for Indexed and Direct | | | file. | | ----------------------------------------------------------- 5. RECORD SIZE The RECORD SIZE field is the size of the record in bytes. It can be either user-specified or program-provided. The message appears on line 22: ENTER THE SIZE OF THE RECORD. RANGE 1..16384. FILESIZE Utility Table 3-7. Possible Errors for RECORD SIZE Field _____ ____ ________ ______ ___ ______ ____ _____ ----------------------------------------------------------- | ERROR MESSAGE | REASON FOR ERROR | ----------------------------------------------------------- | Record size is between | Record size is not in the range| | 1..16384. | | ----------------------------------------------------------- 6. KEY SIZE This field is the size of the key in bytes. This field applies only when the user specifies an existing or a non-existing Single-keyed (Direct or Sort) file. If the file is Sequential (Serial) or Relative record (Indexed), the program will skip the KEY SIZE field and stop at the OUTPUT DEVICE field. The message appears on line 22: ENTER THE SIZE OF THE KEY. RANGE 1..56. Table 3-8. Possible Errors for KEY SIZE Field _____ ____ ________ ______ ___ ___ ____ _____ ---------------------------------------------------------- SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg044 | ERROR MESSAGE | REASON FOR ERROR | ---------------------------------------------------------- | Key size is between | Key size is not in the range. | | 1..56. | | ---------------------------------------------------------- 7. OUTPUT DEVICE This field allows the user to specify where to list the output produced by the program. The user can select VDT, T*, T0-T99, or 'CR' if he prefers the output on a terminal. He may also enter a file name. This file subsequently may be viewed or submitted to a printer. The message appears on line 22: ENTER DEVICE OR FILE NAME. 'CR' = ___ where ___ is the current default of this field. The initial default is 'VDT'. FILESIZE Utility Table 3-9. Possible Errors for OUTPUT DEVICE Field _____ ____ ________ ______ ___ ______ ______ _____ ---------------------------------------------------------- | ERROR MESSAGE | REASON FOR ERROR | ---------------------------------------------------------- | BAD FILE NAME | File name is invalid. | ---------------------------------------------------------- | TERMINAL IS ALREADY | The terminal specified by the | | OPEN | user is not free. | ---------------------------------------------------------- | File already exists, do| The user-specified output file| | you want to delete it, | already exists. | | (Y/N) | | ---------------------------------------------------------- | INVALID OUTPUT DEVICE | Not a valid name of printer or| | | file, e.g. Family not mounted.| ---------------------------------------------------------- 8. ENTRIES CORRECT The last field is the ENTRIES CORRECT field. If all the entries are correct, entering a 'Y'/'y' causes the file space calculation to begin. If the user enters a 'N'/'n', the cursor will move back to the NODE OR FILE NAME field and the entry for that field is erased. 3.3.4.3. Examples ________ 3.3.4.3.1. Node Space Calculation ____ _____ ___________ The user enters the node name, '.ABC.', then hits a 'CR' or 'CTL-IV' which moves the cursor to the OUTPUT DEVICE field. He enters 'VDT' followed by a 'CR'. The cursor stops at the last field, ENTRIES CORRECT, and he then types in 'Y' since all the entries are correct. The calculation immediately begins and the formatted output is displayed: SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg045 FILESIZE Utility Figure 3-13. Sample Output, Node Space Calculation ______ _____ ______ _______ ____ _____ ___________ File File Max Used Rec Key Used Max Name Type Recs Recs Siz Siz Secs Secs (XYZ) .ABC.XXXXXXXXXXX XX XXXXX XXXXX XXX XX XXXX XXXX .ABC.XXXXXXXX XX XXXXX XXXXX XXX XX XXXX XXXX Total sectors for files under .ABC. after conversion: XXXXXXXXX Total sectors for files under .ABC. when files are full: XXXXXXXXX Output description: File Type: Possible file types are 'IND' for Indexed, 'DIR' for Direct, 'SER' for Serial, 'SRT' for Sort, 'SYS' for System PASCAL, 'BB' for Business BASIC, and 'COB' for Business COBOL. Max Recs: Maximum number of records for a file. Used Recs: Number of records actually used by a file. Rec Siz: Record size in bytes. Key Size: Key size in bytes. This column only applies to Direct and Sort files. Used Secs: Number of sectors that will actually be allocated after converting to 8.4E. The amount of space taken up by a file immediately after conversion depends on the file type, but is the same whether one does disk-to-disk conversion or SAVERESTORE-type conversion. Indexed files are compacted back to occupy just enough space to include the block containing the highest-positioned record in the file. This is the same as what happens using SAVERESTORE without conversion, or using the COMPACT utility on an 8.4E Indexed file. Serial files are handled exactly the same way as indexed files. Direct and Sort files are handled a little differently, to be compatible with the file system's attempt to partially "tune" the performance of these files. They will contain enough sectors to hold the greatest of these: (a) the number of records already in the file; FILESIZE Utility (b) 40% of the declared maximum number of records for the file (rounded down); (c) one record (this case is rare). However, a 'create' of Indexed and/or Serial files on 8.4E will require a different number of sectors as opposed to SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg046 conversion. It will allocate enough sectors to hold 40% of the declared maximum number of records. Therefore, the number of sectors required to allocate an initially created file very possibly may be greater than the number of sectors required during conversion. Max Secs: Maximum number of sectors needed assuming this file is full. A file is full when 'Used Recs' = 'Max Recs' Total sectors for files under .ABC. after conversion: Sum of 'Used Secs'. Total sectors for files under .ABC. when files are full: Sum of 'Max Secs'. 3.3.4.3.2. Single File Space Calculation ______ ____ _____ ___________ The user enters the file name '.ABC.testfile.text'. The screen immediately responds with each attribute shown at its corresponding field and the cursor stops at the OUTPUT DEVICE field. The user chooses the '.XYZ.outfile' as the output device and 'Y' for ENTRIES CORRECT field. The output goes to both the file '(DISK).XYZ.outfile' and the screen with the same format as in 3.3.4.3.1 except that there is no line that says 'Total sectors for files under XXX are : ' since there is only one file. 3.3.4.3.3. Non-Existing File Space Calculation ____________ ____ _____ ___________ The user skips the NODE OR FILE NAME field by pressing 'CR'. He then enters 'D' for FILE TYPE, '10000' for RECORDS DECLARED, '300' for ACTUAL RECORDS, '80' for RECORD SIZE, '20' for KEY SIZE, 'T*' for OUTPUT DEVICE and 'Y' for ENTRIES CORRECT. The output shows on the terminal with the same format as in 3.3.4.3.1, but the 'File Name' field is left blank because it is a non-existing file. GETDEVINFO Utility 3.3.5. GETDEVINFO Utility __________ _______ The GETDEVINFO utility is a procedure callable by any process on the system, and which returns the device names and types on the system. For each device on the system, 10 bytes of information are returned. Bytes 1-5 contain the device name padded with blanks. Byte 6 contains the shared memory controller number and the IMLC line number. Byte 7 is the device type code. Byte 8 is the device status code. Byte 9 contains the ISDC line number. Byte 10 is reserved and is always zero. 3.3.5.1. Shared Memory Controller ID Code (Byte 6) ______ ______ __________ __ ____ _____ __ Bit Meaning ___ _______ 0 Line number - A is 0 and B is 1 on IMLC 1-6 Shared memory controller number - range 0-63 7 Not used SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg047 If the device is on an ISCD, the shared memory controller field is valid, and the line number is zero. 3.3.5.2. Device Type Codes (Byte 7) ______ ____ _____ _____ __ Table 3-10 shows all the possible device codes available. An '*' by the code indicates that it is new for 8.4E. GETDEVINFO Utility Table 3-10. DEVICE TYPE CODES _____ _____ ______ ____ _____ Code Description ____ ___________ 00 No device 01 High speed VDT 02 DataWord II MDT in WP mode 03 DataWord II MDT in VDT emulation 04 Ghost terminal 05 7250 terminal 06 Transportable Batch Communications (TBC) 07 TBC Autodial unit 08 3270 running on IMLC 09 X.25 running on IMLC 0A Basic Four serial printer 0B Async driver 0C Async modem driver 0D 7270 terminal w/o slave option 0E 7270 terminal with slave option 10 Basic Four slave printer 11 Parallel matrix printer 12 Parallel band printer 13 MTR 1/2" reel-to-reel tape drive 14 MTS 1/2" streamer tape drive 18* Letter quality system serial printer 1A* DMP serial system printer 1B* DMP parallel printer 1C* Industry standard slave printer 20 MCS 1/4" cartridge streamer tape drive 21-FF Unused 3.3.5.2.1. Device Status Code (Byte 8) ______ ______ ____ _____ __ In the device status field, each bit has one meaning. More than one bit may be set in this field. For each bit in the field that is set, that condition is true. Bit Meaning (If bit is set) ___ _______ ___ ___ __ ____ 0 Escape entered on terminal device 1 Device is open or in use 2 Device is not configured 3 Printer is dedicated 4 Terminal has a slave printer 5-7 Not used 3.3.5.2.2. ISDC Line Number (Byte 9) ____ ____ ______ _____ __ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg048 The lower three bits of the byte contain the line number (0-7) of the device if the device resides on an ISDC. The 16-way ISDC is treated as two consecutively addressed 8-way ISDCs. On a 4-way ISDC (MCS), the lower 2 bits will be the line number, and bit 3 will be zero. OLDDIR Utility 3.3.6. OLDDIR-Old Directory List Utility __________ _________ ____ _______ 3.3.6.1. Introduction ____________ The Old_Directory_List_Utility provides the user a printed or __________________________ displayed list of files on an pre-8.4E format family. The files to be listed may be specified by single file names, mask name, or node name. If the user tries to use this utility to list a new file format family an error will be returned telling the user that the family is not in the old-style format. The old-style format drive is disabled when the utility is called. The utility will handle enabling it for read purposes and then returning it to the disabled state. The information required to run the Old_Directory_List_Utility __________________________ includes: 1. The name(s) of the file(s) to be listed. 2. The type(s) of files to be listed. The user has the choice of listing all files, only program files, or only data files. 3. The output device of the listing. The options include displaying the listing at the VDT, also printing the listing at a line printer, or sending the listing to a specified file as well as to the VDT. 4. Whether or not output to the VDT should be suppressed. An output device must be specified. The information returned by the Old_Directory_List_Utility __________________________ includes a listing or display of the following: 1. File name 2. The type of file. Single-Keyed files will be listed as DIR (Direct), Serial files will be listed as SER, Indexed files will be listed as IND, Program files will be listed as CODE. Unrecognized data files will be listed as UNO (unorganized; for example terminal configuration files), and unrecognized program files will be listed as ACF (Alien code file; for example, OS image files). All program messages and errors are output to the VDT unless the user specified that the utility run in quiet mode. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg049 3.3.6.2. Procedures for Using Utility __________ ___ _____ _______ OLDDIR Utility 3.3.6.2.1. By Command with Parameters __ _______ ____ __________ The Old_Directory_List_Utility can be run by entering a __________________________ command with parameters in console mode or as a program directive. The format is as follows: OLDDIR filename {,OUTPUT= } {,TYPE= } {,OUTACTION= } {,QUIET= } Table 3-11 explains each of the parameters. Table 3-11. Parameters of the Old Directory List Command _____ _____ __________ __ ___ ___ _________ ____ _______ ------------------------------------------------------------------------ | Requried Parameters (positional) | | | | Parameter | | --------- | | 1. filename = Name of file(s) to be listed. | | May be an individual filename, | | node name, or mask name. | | | |----------------------------------------------------------------------| | Optional Parameters (Keyword) | | | | Parameter Keyword Values and Effects | | --------- ------- ------------------ | | | | 1. Output device OUTPUT= LP ,P1, etc = line printer | | for listing filename = selected file | | ** VDT = VDT only | | | | 2. Types of files TYPE= ** A = all file types | | to be listed. P = program files only | | D = data files only | | | | 3. Whether output device OUTACTION= A = Append to file if it | | should be deleted if exists | | it exists, or appended D = Delete file if it exists| | to if it exists. ** N = Do not Delete or append | | | | 4. Whether output to the QUIET= T = Suppress all output to | | terminal should be VDT. (An output device | | suppressed. must be specified.) | | ** F = Normal output. | ------------------------------------------------------------------------ ** = Defaults OLDDIR Utility 3.3.6.2.2. By Menu or Command Without Parameters __ ____ __ _______ _______ __________ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg050 The Old_Directory_List_Utility by the command 'OLDDIR' in __________________________ console mode. The program returns the screen shown in Figure 3-14. Figure 3-14. Old Directory List Utility Data Entry Screen ______ _____ ___ _________ ____ _______ ____ _____ ______ MAI BASIC FOUR, INC. OLD DIRECTORY LIST UTILITY PRIMARY PREFIX : XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX START SPECIFIER: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX END SPECIFIER : XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX FILE TYPE : XXXXXXXXX OUTPUT DEVICE : XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX ENTRIES CORRECT (Y/N): XXXXXXXXX 3.3.6.2.2.1. Field Descriptions _____ ____________ The fields on the Old_Directory_List_Utility data entry screen __________________________ are as follows: 1. The PRIMARY PREFIX field is a display-only field listing the user's primary prefix. The primary prefix is displayed as soon as the screen comes up. 2. The File Name consists of two fields, the START SPECIFIER and the END SPECIFIER. Because of the possible length of the file name, the interactive utility must use two fields. a) The START SPECIFIER is used for all types of files to be listed. If the user wants a specific range of files he may use point to point syntax. In the START SPECIFIER field the user must enter the starting point of the range. The last character of this specifier must be a '/' to specify point to point masking. When the utility sees the '/', the user will then be prompted for the END SPECIFIER. If the user did not specify point to point masking, the END SPECIFIER field will not be used. When the cursor reaches this field the prompt displayed on line 23 on the screen: OLDDIR Utility ENTER INDIVIDUAL FILE NAME, NODE, OR MASK NAME To list selected files, enter the individual file name, the node, or a mask name. The default for this field is to list the users Primary Prefix. The default is entered by entering a or at the beginning of the field. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg051 Entering a '?' causes the help screen to be displayed. Possible errors for the start specifier field if the file name specified does not have point to point syntax, are shown in Table 3-12. Table 3-12. Possible Errors for Start Specifier Field _____ _____ ________ ______ ___ _____ _________ _____ -------------------------------------------------------------------------- | ERROR MESSAGE | REASON FOR ERROR | -------------------------------------------------------------------------- | Invalid file name | The utility does not recognize the | | | entry as a valid file name. | | Invalid family name | The utility does not recognize the | | | entry as having a valid family name | | File does not exist | Individual file name entered and | | | file does not exist. | | VOLUME NOT MOUNTED | File(s) specified are located on | | | a volume that is not mounted. | -------------------------------------------------------------------------- b) The END SPECIFIER field is where the user enters the ending file name in point to point masking. This field will only be used if point to point masking was specified in the START SPECIFIER field. When the cursor reaches this field the prompt: ENTER INDIVIDUAL FILE NAME, NODE, OR MASK NAME is displayed on line 23. The default for this field is '.': list all files to the end of the directory. Note: Errors for the START SPECIFIER field and END SPECIFIER field, if point to point, will not be detected until this field is entered. The error message will be displayed for both fields, as if they were one. Possible errors with point to point syntax in addition to start specifier errors, are shown in table 3-13. OLDDIR Utility Table 3-13. Possible Errors with Point to Point Specifiers _____ _____ ________ ______ ____ _____ __ _____ __________ -------------------------------------------------------------------------- | ERROR MESSAGE | REASON FOR ERROR | -------------------------------------------------------------------------- | INVALID PT2PT RANGE | The start and end file specifiers | | | must be in the same range | | NO FILE FOUND IN RANGE | There was no file(s) found in the | | OF PT2PT SPECIFIER | specified range of the start and | | | end file specifiers | -------------------------------------------------------------------------- 3. The FILE TYPE field allows the user to specify whether SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg052 all files, only program files, or only data files are to be listed. When the cursor reaches this field the prompt appears on line 23: FILES TO BE LISTED, ALL, DATA, OR PROGRAM, (A/D/P), 'CR' = ___ The ___ is the current default for this field, the initial default is to list all files. To list program files only enter 'P', to list data files only enter 'D'. The possible errors for this field are shown in Table 3-14. Table 3-14. Possible Errors for File Type Field _____ _____ ________ ______ ___ ____ ____ _____ -------------------------------------------------------------------------- | ERROR MESSAGE | REASON FOR ERROR | -------------------------------------------------------------------------- | Invalid entry | File type must be A, P, D, or some | | | part of the words ALL, PROGRAM, or DATA| | | Example: AL, ALL, PRO, PROG, DAT. | -------------------------------------------------------------------------- 4. Under OUTPUT DEVICE the user can choose whether to have the listing sent only to the VDT, or also to a line printer or to a specified file. The prompt displayed on line 23 when the cursor reaches this field is: ENTER DEVICE OR FILE NAME, 'CR'= ___ Where ___ is the current default for the field. The Initial default is 'VDT'. If the file name entered exists then the utility will delete the existing file with the user's permission. The error and prompt displayed on line 23 is: OLDDIR Utility FILE ALREADY EXISTS, DO YOU WISH TO DELETE OR APPEND TO THE FILE (D/A/N): XX An answer of 'D' will delete the existing file and send the output to the file. An answer of 'A' will append the listing to the existing file. The original information in the file will remain. An answer of 'N' will not delete the file and will prompt the user again for an output device. If the user has entered the command from the console with parameters the user is not prompted for this. It is passed in as a parameter OUTACTION to the utility. If the user passed a 'N' and the file exists an error is generated. The possible errors for this field are shown in Table 3-15. Table 3-15. Possible Errors for Output Device Field _____ _____ ________ ______ ___ ______ ______ _____ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg053 -------------------------------------------------------------------------- | ERROR MESSAGE | REASON FOR ERROR | -------------------------------------------------------------------------- | PRIVILEGE INSUFFICIENT | Do not have enough access rights to | | | delete existing file. | | TERMINAL ALREADY OPEN | Terminal specified is already open | | INVALID OUTPUT DEVICE | Entry is not recognized as an | | | individual file name, a terminal | | | name or a printer name. | | PRINTER DOES NOT EXIST | Printer specified does not exist. | | File already exists | User passed in a 'N' for OUTACTION | | | and the file already exists. | -------------------------------------------------------------------------- 5. For ENTRIES CORRECT, there are no prompts. If the entries are all correct, entering 'Y' causes the utility to begin. If the user enters 'N', the cursor goes back to the START SPECIFIER field and the entry for that field is erased. All entries are remembered and used as defaults. If the user enters , the cursor goes back to the START SPECIFIER field, erasing all entries. All entries are not remembered. The old defaults are reset. The only possible error is if the user enters something that is not YES or NO or any logical part or those words, (i.e. Y,YE,N ). The error displayed is: INVALID ENTRY OLDDIR Utility 3.3.6.3. Printed Results and Displays _______ _______ ___ ________ 3.3.6.3.1. The Display ___ _______ When the Old_Directory_List_Utility is run the program __________________________ produces a list of the results of the utility. Whenever results are sent to a printer or a file they are also displayed at the VDT. The results sent to a file and then spooled to a printer look identical to results sent directly to a printer. If the user specified quiet mode (QUIET=TRUE) then the listing will only go to the output device specified. If an output device was not specified then the error INCONSISTENT PARAMETERS PASSED is generated. The utility will stop and prompt the user every 17 file names. The user is prompted with 'CR' TO CONTINUE: on line 23. At this point the user may type in to exit back to the data entry screen, or may enter or to continue to the next page. If the user entered or the file names on the screen are scrolled up one line for each new file name listed. After another 17 files are listed, the prompt appears again. After all file names have been displayed and the utility was entered through SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg054 the interactive screen, the utility prompts the user with 'CR' TO CONTINUE, 'CTL-IV' TO EXIT UTILITY: If the user enters or to the above prompt the utility will redisplay the data entry screen and then prompt the user for a new file specifier. If the user enters then the cursor is positioned at line 23, column 0 and the utility exits. 3.3.6.3.1.1. Files with Attributes _____ ____ __________ If the user specified partial attributes, results displayed at the VDT are shown in Figure 3-15. The results are the same whether the utility was entered through a command with or without parameters. The totals for the files listed are displayed on the last page of the listing and to a printer or file if it was specified. The totals listed are: total number of files listed and total number of each type of file. OLDDIR Utility Figure 3-15. Output to VDT, Multiple Files, with Attributes ______ _____ ______ __ ____ ________ ______ ____ __________ MAI BASIC FOUR, INC. OLD DIRECTORY LIST UTILITY FILE NAME TYPE (family name) .AAA.BBB.CCC.DDD.EEE.FFF.GGG.HHH DIR .AAA.BBB.CCC.DDD.EEE.FFF.GGG.HHI CODE .AAA.BB.FILE SER .AAA.CC.FILE CODE .AAA.DD.FILE.TEXT SER .AAA.EE.FILE IND .AAA.FF.FILE CODE .AAA.GFILE CODE .AAA.H.FILE.TEXT DIR .AAA.COBOL CODE TOTALS: FILES LISTED: 10 DIR: 2 IND: 1 SER: 2 UNO: 0 CODE: 5 ACF: 0 'CR' TO CONTINUE: XX The information listed under the column headings is as follows: 1. FILE NAME: The name of the file (32 character field) 2. TYPE: The type of the file. For data files the possible types are DIR for direct or sort files, IND for indexed files, and SER for serial files. For program files all types are CODE. 3.3.6.3.2. Exiting the Utility _______ ___ _______ To exit the utility enter 'CTL-IV' in the first position of the START SPECIFIER field or enter 'CTL-IV' at the prompt SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg055 'CR' TO CONTINUE, 'CTL-IV' TO EXIT UTILTIY: NFSCONVERT Utility 3.3.7. NFSCONVERT Utility __________ _______ 3.3.7.1. Introduction ____________ The Disk to Disk Conversion Utility provides the user with a ____ __ ____ __________ _______ method for converting files with an old file format (release 8.4D and earlier) to the new file format. The user may convert a single file or a group of files. The files to be converted can be specified by individual file name, node name or by masking. No more than one terminal may be converting a given family on the system. You can convert more than one family at a time, using different terminals for each family. 3.3.7.2. Workspace Required for Keyed Files _________ ________ ___ _____ _____ NFSCONVERT uses a sizable amount of workspace when converting keyed (Direct and Sort) files. Therefore, it is strongly recommended that all keyed files in a family be converted first. NFSCONVERT first looks for workspace on the User Default Family. If it cannot find enough workspace there, it looks for space on the System Default Family. ("!UDFAMILY" will display the name of the User Default Family, and "!SDFAMILY" will display the name of the System Default Family.) If NFSCONVERT still cannot locate enough workspace, a message will display that it is out of usable disk space. If this occurs, and there is an extra disk drive on your system for a removable pack, you may mount an 8.4E formatted scratch pack on that drive. You must then run INSTALL.PARAMS, option 4, (TYPE 1 LOAD) to temporarily change the name of the User Default Family to the family name on the scratch pack. This will cause NFSCONVERT to use the scratch pack for the workspace needed to convert the keyed files. (Remember to change the User Default Family back to its original name when the conversion is complete.) If NFSCONVERT runs out of disk space, and you do not have an extra drive on your system, you must do the conversion to tape using SAVERESTORE. If you would like to estimate the amount of workspace NFSCONVERT will require for your keyed files, you can apply this formula: Add 5 to the declared keysize for the file, and multiply the result by the number of records written to in the file. Then multiply this number by 7. Divide the result by 1024, and you will have the approximate number of workspace sectors NFSCONVERT will require for the file. NFSCONVERT Utility 3.3.7.3. Procedures for Using Utility __________ ___ _____ _______ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg056 3.3.7.3.1. By Command with Parameters __ _______ ____ __________ The Disk to Disk Conversion Utility can be run by entering a ____ __ ____ __________ _______ command with parameters in console mode or as a program directive. The format is as follows: NFSCONVERT filename1, filename2 {,OUTPUT= } {,VERIFY= } {,PAUSE= } {,DELEXIST= } {,OUTACTION= } {,TYPE= } {,QUIET= } Each of the parameters is explained in Table 3-16. NFSCONVERT Utility Table 3-16. Parameters for NFSCONVERT _____ _____ __________ ___ __________ -------------------------------------------------------------------------- | Requried Parameters (Positional) | | Parameter Values and Effects | | --------- ------------------ | | 1. filename1= Name of file(s) to be converted. String | | May be an individual file name, | | a node, or mask. The file(s) may | | be specified using point-to-point | | syntax in the mask. | | | | 2. filename2= Name of destination file(s). String | | May be an individual file name, | | a node, or mask. | |------------------------------------------------------------------------| | Optional Parameters (Keyword) | | Parameter Keyword Values and Effects | | --------- ------- ------------------ | | 1. Output device OUTPUT= LP ,P1, etc = line printer | | for listing filename = selected file | | ** VDT = VDT only | | | | 2. Verify Conversion VERIFY= ** T = Verify | | F = do not Verify | | | | 3. Whether program should PAUSE= ** T = Pause on errors | | pause on errors F = Do not pause on errors | | | | 4. Whether file existing DELEXIST= T = Delete existing files | | under destination name ** F = Do not delete existing | | is to be deleted. files | | | | 5. Whether output file OUTACTION= A = Append to file if it | | should be deleted if it exists | | exists, appended to if D = Delete file if it | | exists, or tell user that exists | | it exists. ** N = Do not delete or append | | | | 6. What type of files should TYPE= ** A = All files found in | SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg057 | be converted. group specified. | | K = Only KEYED files found | | in group specified. | | O = Only NON-KEYED files | | found in group. | | | | 9. Whether output to the QUIET= T = No output to the VDT. | | terminal should be Verify and Pause must | | suppressed. be false. | | ** F = Normal output. | | ** Defaults | -------------------------------------------------------------------------- NFSCONVERT Utility Help for the Disk to Disk Conversion Utility can be displayed ____ __ ____ __________ _______ to the console with the following command: NFSCONVERT.HELP [] The printer name is optional. If it is specified then the help screens will be sent to the printer. If a printer name is not specified then the screens will be displayed at the console and the user is prompted at the end of each page with a: 'CR' TO CONTINUE:. 3.3.7.3.2. By Menu or Command Without Parameters __ ____ __ _______ _______ __________ The user can run this utility by keying the command 'NFSCONVERT with no parameters in console mode. The program responds by displaying the screen shown in Figure 3-16. Figure 3-16. NFSCONVERT Data Entry Screen ______ _____ __________ ____ _____ ______ MAI BASIC FOUR, INC. DISK TO DISK CONVERSION UTILITY PRIMARY PREFIX : XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX START SPECIFIER: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX END SPECIFIER : XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX DESTINATION : XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX DELETE EXISTING DESTINATION FILE : XXXXXXXXX VERIFY : XXXXXXXXX PAUSE ON ERRORS : XXXXXXXXX TYPE: XXXXXXXXXX OUTPUT DEVICE : XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX ENTRIES CORRECT (Y/N): XXXXXXXXX 3.3.7.3.2.1. Field Descriptions _____ ____________ The purpose for each field in the Data Entry Screen is as follows: SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg058 1. The PRIMARY PREFIX field is a display-only field listing the user's primary prefix. If the source file or destination file does not exist in this prefix, a fully-specified file name must be specified. 2. The File Name consists of two fields: The START SPECIFIER and the END SPECIFIER. Because of the NFSCONVERT Utility possible length of the file name, the interactive utility must use two fields. For normal file masking, only the '&' and the '^' masking characters can be used. The '&' can only be used as the last character. a) The START SPECIFIER is used for all types of files to be converted. If the user wants a specific range of files he may use point to point syntax. In the START SPECIFIER field the user must enter the starting point of the range. The last character of this specifier must be a '/' to specify point to point masking. When the utility sees the '/', the user will then be prompted for the END SPECIFIER. If the user did not specify point to point masking, the END SPECIFIER field will not be used. When the cursor reaches this field the prompt displayed on line 23 is: ENTER INDIVIDUAL FILE NAME, NODE, OR MASK NAME To convert selected files, enter the individual file name, node or mask. Entering a '?' causes the help screens to be displayed. The user should be aware that he is specifying files on an Old File System format family at this point. That family must be present, of course, but cannot and need not be enabled. Two families with the same name can be on the same system at the same time, provided that one of them has Old File System format, and the other has New File System format. Possible errors for the Start Specifier field, if the file name specified does not have point to point syntax, are shown in Table 3-17. NFSCONVERT Utility Table 3-17. Possible Errors for Start Specifier, not Point-to-Point _____ _____ ________ ______ ___ _____ __________ ___ ______________ ------------------------------------------------------------------------- | ERROR MESSAGE | REASON FOR ERROR | ------------------------------------------------------------------------- | INVALID FILE NAME | The utility does not recognize the | | | entry as an individual file name, | | | mask, or node. | | FILE DOES NOT EXIST | Individual file name entered and | | | file does not exist. | | NODE DOES NOT EXIST | Node does not exist. | ------------------------------------------------------------------------- SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg059 b) The END SPECIFIER is the ending file name in point to point masking. This field will only be used if point to point masking was specified in the START SPECIFIER field. When the cursor reaches this field the prompt: ENTER INDIVIDUAL FILE NAME, NODE, OR MASK NAME is displayed on line 23. The default for this field is '.': convert all files to the end of the directory. Note: Errors for the START SPECIFIER field and END SPECIFIER field, if point to point, will not be detected until after the destination field is entered. The error message will be displayed for all three fields, as if they were one. 3. DESTINATION is used to enter the names of the files to be converted to by this utility. For masking, only the '&' and the '^' can be used. The '&' can only be used as the last character. When the cursor reaches this field the prompt appears on line 23 of the screen: ENTER INDIVIDUAL FILE NAME, NODE, OR MASK NAME Enter the individual file name, node or mask of the destination file(s). Errors for the START SPECIFIER field and END SPECIFIER field, if point to point, will not be detected until this field is entered. The error message will be displayed for all three fields, as if they were one. Possible errors for the Destination field are shown in Table 3-18. NFSCONVERT Utility Table 3-18. Possible Errors for Destination Field _____ _____ ________ ______ ___ ___________ _____ ------------------------------------------------------------------------- | ERROR MESSAGE | REASON FOR ERROR | ------------------------------------------------------------------------- | INVALID FILE NAME | The utility does not recognize the | | | entry as an individual file name, | | | mask, or node. | | 'SOURCE' AND 'DESTINATION' | The start and destination file | | MUST BE OF SAME TYPE | specifiers must be of same type, | | | i.e. both individual file names, | | | mask, nodes or point-to-point. | | INVALID PT2PT RANGE | The start and end file specifiers | | | must be in the same range | | NO FILE FOUND IN RANGE OF | There was no file(s) found in the | | PT2PT SPECIFIER | specified range of the start and | | | end specifier. | | FILE DOES NOT EXIST | Individual file name entered and | | | file does not exist. | | NODE DOES NOT EXIST | Individual node name entered and | | | node does not exist. | ------------------------------------------------------------------------- Note: If a 'CTL-II' is entered from the destination _____ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg060 field the cursor will be moved to the start specifier field. 4. DELETE EXISTING DESTINATION FILE is used to specify whether a file already existing under the destination file name is to be deleted. If you elect not to have an existing file deleted, and the program encounters a file under the destination file name, the program will not convert the source file to that destination file name. When the cursor arrives at this field, the prompt DELETE EXISTING DESTINATION FILE, (Y/N), 'CR'=___ is displayed on line 23. ___ is the current default for this field. The initial default is <'N'>. If the user does not respond with 'YES', 'NO', or any subset of these ('Y','YE','N'), the program outputs INVALID ENTRY on line 23. 5. VERIFY is used to designate whether or not the user wishes to authorize conversion of each file before doing so. When the cursor arrives at this field, the NFSCONVERT Utility prompt VERIFY EACH CONVERSION, (Y/N), 'CR'=___ is displayed on line 23. ___ is the current default; the initial default is <'Y'>. If the user does not respond with 'YES', 'NO', or any subset of these ('Y','YE','N'), the program outputs INVALID ENTRY on line 23. 6. PAUSE ON ERRORS is used to direct the utility to stop and inform the user when an error occurs while attempting to convert the primary file. When the cursor arrives at the field, the prompt PAUSE ON ALL ERRORS, (Y/N), 'CR'=___ is displayed on line 23. ___ is the current default; the initial default is <'Y'>. If the user has already specified VERIFY=TRUE the response to this field is ignored and the utility will pause before every file whether there is an error or not. However, if the user responds to the VERIFY prompt with 'CTL-II' while the utility is executing, the PAUSE ON ERRORS will remain enabled even after the VERIFY has been turned off. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg061 If the user does not respond with 'YES', 'NO', or any subset of these ('Y','YE','N'), the program outputs INVALID ENTRY on line 23. 7. TYPE is used to designate the type of files to convert. The user may convert all file types, only keyed files, or only non-keyed files. If a disk is close to being full and the user converts all files, the user may run out of space, even though there is enough room for the files. There may not be enough room to work through the conversion. In this case the user will want to convert KEYED files first. These files take more work area to convert. Then he will want to convert all other non-keyed files. When the cursor arrives at this field, the prompt NFSCONVERT Utility TYPE OF FILES TO CONVERT, ALL, KEYED, NON KEYED (OTHER), (A/K/O), 'CR' = ___ where ___ is the current default for this field. The initial default is to convert all files (A). When something other than A, K, or O is entered, the error: INVALID ENTRY is displayed on line 23. 8. OUTPUT DEVICE is used to designate a device or file where a summary status of the activity will be reported. The report may be written to the VDT only, to the VDT and a line printer, or to the VDT and a specified file. When the cursor arrives at this field, the prompt ENTER DEVICE OR FILE NAME, 'CR'=___ is displayed on line 23. ___ is the current default; the initial default is 'VDT'. If the user enters the name of a file that already exists, the utility will delete the existing file, but only at the user's direction. To determine what action to take, the program prompts with FILE ALREADY EXISTS, DO YOU WISH TO DELETE OR APPEND TO THE FILE (D/A/N): XX on line 23. If the response is 'D', the utility will delete the existing file and write its report to a new file having the same name. If the response is 'A', the utility will append its report to the end of the existing file without altering the original data in the file. If the response is 'N', no action will be taken, the file will not be deleted, and the utility will prompt again for the OUTPUT DEVICE. NOTE! When the Append option is requested, the file to ____ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg062 which the appending takes place must be a SERIAL file. Possible errors for this field are shown in Table 3-19. NFSCONVERT Utility Table 3-19. Possible Errors for OUTPUT DEVICE Field _____ _____ ________ ______ ___ ______ ______ _____ ------------------------------------------------------------------------- | ERROR MESSAGE | REASON FOR ERROR | ------------------------------------------------------------------------- | INVALID OUTPUT DEVICE | Entry is not a valid name of file, | | | printer, or terminal. | | PRINTER DOES NOT EXIST | Entry is valid printer name but not | | | currently on the system. | | TERMINAL ALREADY OPEN | Entry is name of a terminal that is | | | already open by another user. | | PRIVILEGE INSUFFICIENT | User's account lacks the privilege to | | | delete or write to the existing | | | OUTPUT file. | | FILE ALREADY EXISTS | OUTPUT file exists and user passed | | | OUTACTION=N from command line. | | FILE MUST BE SERIAL TO APPEND | User is attempting to Append to a | | | non-SERIAL OUTPUT file. | ------------------------------------------------------------------------- 9. ENTRIES CORRECT is used to retain the request parameters on the screen long enough to allow the user to verify their correctness and make any desired changes. There is no prompt for this field. If the user enters 'Y', the conversion operation begins. If the user enters 'N', the cursor returns to the first input field and the earlier entry for the field is erased. All entries are retained for use as current default values. If the user enters 'CTL-IV', the cursor returns to the first input field, all field entries are erased, and the utility reverts to the initial defaults. If the user does not respond with 'YES', 'NO', or any subset of these ('Y','YE','N'), the program outputs INVALID ENTRY on line 23. 3.3.7.4. Functions Performed _________ _________ When the Disk to Disk Converstion Utility is run, the program ____ __ ____ ___________ _______ produces a display or a printing of the results of the utility. Whenever results are sent to a printer or to a specified file, they are also displayed at the VDT. When the results which have been sent to a specified file are spooled to a line printer, they look identical to the results sent directly to the printer. Figure 3-17 shows the results at the VDT. NFSCONVERT Utility If the user set the parameter QUIET as TRUE then output to the SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg063 VDT is suppressed. The user will see no output, not even errors. If the parameter PAUSE or VERIFY was passed in as TRUE as well as QUIET then the error INCONSISTENT PARAMETERS PASSED is generated. You can't run quietly and still prompt the user. If an output device was specified then output will go there as usual. Figure 3-17. NFSCONVERT Display on the VDT ______ _____ __________ _______ __ ___ ___ MAI BASIC FOUR, INC. DISK TO DISK CONVERSION UTILITY SOURCE FILE NAME DESTINATION FILE NAME ACTION (family name) (family name) .AAA.AFILE.TEXT .XXX.AFILE.TEXT CONVERTED .AAA.BFILE.TEXT .XXX.BFILE.TEXT SKIPPED .AAA.CFILE.TEXT .XXX.CFILE.TEXT CONVERTED .AAA.CFILE .XXX.CFILE CONVERTED .AAA.DFILE .XXX.DFILE CONVERTED .AAA.EFILE.TEXT .XXX.EFILE.TEXT CONVERTED .AAA.FFILE .XXX.FFILE CONVERTED .AAA.GFILE.TEXT .XXX.GFILE.TEXT CONVERTED .AAA.HFILE .XXX.HFILE CONVERTED For each file that was selected for conversion, the program displays the source and destination file name. If the user specified verification the prompt 'CR','CTL-I' TO CONVERT, 'CTL-II'=VERIFY OFF, 'CTL-III'=SKIP, 'CTL-IV'= EXIT: XX is displayed on line 23. The user must respond to the prompt before the file can be converted. If the user responds with or the utility tries to convert the file. If it is successful then the message CONVERTED is displayed on the same line as the file names and the next file name is displayed on the next line. (If we are at the bottom line, line 21, then the list of files scrolls up one file.) If the utility could not convert the file the message ERROR is displayed on the same line as the file names. If we are verifying or if pause on errors is TRUE, the error message is displayed on line 23. If we are not verifying and pause on errors is not true the error message is not displayed. If the user responds to the prompt with a the message NFSCONVERT Utility CONVERTED is displayed on the same line as the file names, and the file is converted. The verification prompt is then no longer displayed and no verification takes place. If the user responds to the prompt with a the message SKIPPED is displayed on the same line as the file names, and the file is not converted. The next file is then displayed on the next line. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg064 When a is selected the conversion process quits and will return to the calling program. If the program was interactive then the copy files data entry screen is displayed with the cursor at the START SPECIFIER field and the user may specify the name of another file to be converted, otherwise the user is returned to the command line prompt. When all files selected have been processed the prompt 'CR' TO CONTINUE, 'CTL-IV' TO EXIT UTILITY: is displayed on line 23. When the user enters a the utility returns to the interactive screen or the command language. If the program was run through the interactive utility then the data entry screen is redisplayed and the cursor is placed at the START SPECIFIER field and the user may specify the name of another file to be copied. Otherwise the user is returned to the command line prompt. If the user enters a from the prompt, the utility will exit to the program that called the utility, either the command language, BASIC, or a program. This feature allows the user to bypass the interactive data screen when exiting. If the verify option was not selected the utility will try to convert all files specified. If an error occurs and pause on errors is set, the error message is displayed on line 23. In addition to the displays and/or printed reports, all program and system errors are displayed on the OUTPUT DEVICE. The output listing to a file or printer looks like the VDT display except the actual error encountered is printed under the file name. Figure 3-18 shows output to a file or printer. This conversion would have been invoked by the command: NFSCONVERT (FamilyA).AAA.,(FamilyB).XXX.,OUTPUT=LP NFSCONVERT Utility Figure 3-18. NFSCONVERT Output to a Printer or File ______ _____ __________ ______ __ _ _______ __ ____ MAI BASIC FOUR, INC. DISK TO DISK CONVERSION UTILITY SOURCE FILE NAME DESTINATION FILE NAME ACTION (family name) (family name) .AAA.AFILE.TEXT .XXX.AFILE.TEXT CONVERTED .AAA.BFILE.TEXT .XXX.BFILE.TEXT ERROR FILE LOCKED .AAA.CFILE.TEXT .XXX.CFILE.TEXT CONVERTED .AAA.CFILE .XXX.CFILE CONVERTED .AAA.DFILE .XXX.DFILE CONVERTED .AAA.EFILE.TEXT .XXX.EFILE.TEXT ERROR PRIVILEGE INSUFFICIENT .AAA.FFILE .XXX.FFILE CONVERTED .AAA.GFILE.TEXT .XXX.GFILE.TEXT CONVERTED .AAA.HFILE .XXX.HFILE CONVERTED Output to the terminal when the utility is called from console mode with parameters is shown in Figure 3-19. The first file SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg065 name is displayed on the line following the command. If the verify parameter was set to TRUE, the user is prompted for verification. The prompt: CONVERT? ('CTL-I' = Y /'CTL-III' = N/'CTL-II'=VERIFY OFF) is displayed on the line following the file name. The messages CONVERTED, and SKIPPED are displayed on the same line as the file names. If the copy encountered an error, it is displayed under the file name. If pause on errors is TRUE the user is prompted for 'CR' TO CONTINUE. NFSCONVERT Utility Figure 3-19. NFSCONVERT Display with Parameters ______ _____ __________ _______ ____ __________ SOURCE FILE NAME DESTINATION FILE NAME ACTION (family name) (family name) .AAA.AFILE.TEXT .XXX.AFILE.TEXT CONVERTED .AAA.BFILE.TEXT .XXX.BFILE.TEXT ERROR FILE LOCKED .AAA.CFILE.TEXT .XXX.CFILE.TEXT CONVERTED .AAA.CFILE .XXX.CFILE CONVERTED .AAA.DFILE .XXX.DFILE CONVERTED .AAA.EFILE.TEXT .XXX.EFILE.TEXT ERROR PRIVILEGE INSUFFICIENT .AAA.FFILE .XXX.FFILE CONVERTED .AAA.GFILE.TEXT .XXX.GFILE.TEXT CONVERTED .AAA.HFILE .XXX.HFILE CONVERTED 3.3.8. SAVERESTORE Utility ___________ _______ NOTE: The message displayed when reaching the end of a reel on a Save has changed from 8.4D to 8.4E, and requires the opposite answer to the prompt. On 8.4D the prompt is, "End of this reel, do you want to continue (CR=N/Y)?", which requires a "Y" response if you want to continue. On 8.4E the prompt is, "End of this reel, exit save operation (CR=N/Y)?", which requires a "N" or "CR" response if you want to continue. The file specifiers on the Save, Restore, and Compare options can now be edited by using certain control keys. In addition, SAVERESTORE now supports point-to-point file specifiers. Compare for Save, using point- to-point specifiers, is also supported. SAVERESTORE also performs automatic conversion of pre-8.4E files to the new file format. This allows any archived files to be brought forward to the new File System. 3.3.8.1. File Specifier Editing ____ _________ _______ This feature allows a user to edit the file specifiers for the Save, Restore, and Compare operations. Any character except those described below are considered to be valid file specifiers. Any valid character typed in is always inserted SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg066 to the left of the cursor. The following keys are used to more the cursor around: CR (CARRIAGE RETURN) - This key has two functions. One is to exit the screen edit mode. The other is to move the cursor to the next line. CTL-I - Same as "CR". CTL-II - This key has two functions. One is to move the cursor to the beginning of the line. The other is to move the cursor to the beginning of the previous line, if the cursor is at the beginning of the current line. CTL-III - This key deletes the character at the cursor position. CTL-IV - This key has two functions. One is to exit the file specifier screen, if the cursor is at the first character of the first line on the screen. The other is to clear all inputs and position the cursor at the first position on the first line. Left Arrow (CTL-N) - This key moves the cursor one character to the left. Right Arrow (CTL-L) - This key moves the cursor one character to the right. 3.3.8.2. Point-to-Point Specifiers ______________ __________ A point-to-point specifier is a file specifier in the format of: source-begin-file-specifier/end-file-specifier,destination-file-specifier Both the "/end-file-specifier" and ",destination-file- specifier" are optional. The point-to-point specifier allows the user who knows the sequence of files to start restoring and comparing in a particular range. The "source-begin-file-specifier" designates the file where the operation is to begin. The "end-file-specifier" designates where the operation terminates. If no "end-file-specifier" exists, the operation continues until the end of a given node and/or disk. For example, the file specifier "ABC/ZZZ" will perform the operation for all the files between the files ABC and ZZZ, as they appear in the directory listing. The example, ".BIGNODE.BIGFILE/.BIGNODE.SMALLFILE" will do the chosen operation for the files between BIGFILE and SMALLFILE in the node BIGNODE. 3.3.9. TERM.CONFIG Utility ___________ _______ With this release there is now support for the EDT terminal (model 4310) and the DMP serial printer (model 4214). SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg067 3.3.9.1. EDT Terminal ___ ________ There is now an option when configuring terminals to configure an EDT terminal. This is Option 8 from the subtype options. Table 3-20 shows the defaults when the EDT subtype is chosen. Table 3-20. EDT Defaults _____ _____ ___ ________ Option Default ______ _______ Bits/char 8 Parity Odd Line speed 9600 Inhibit welcome No Multiplexor support No Duplex Full Stop bits 1 Line length 80 Delay type Time Delay length 0 ticks Attached printer No X-on/X-off flow control Yes Inhibit translate No Echo suppression No Auto CR on LF No Input transparency No Output transparency No 3.3.9.2. Serial DMP ______ ___ When choosing the printer option, there is now a DMP serial printer type. The option number is three from the subtype options. The DMP printer is a standard RS-232C printer that will operate from the ISDC. Table 3-21 shows the DMP defaults when the option is chosen. Table 3-21. Serial DMP Defaults _____ _____ ______ ___ ________ Option Default ______ _______ Bits/char 7 Parity Odd Line speed 2400 Inhibit welcome Yes Multiplexor support No Duplex Full Stop bits 1 Line length 132 Delay type Time Delay length 0 ticks Attached printer No X-on/X-off flow control No Echo Suppression Yes Auto CR on LF No SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg068 Input transparency Yes Output transparency Yes TERM.ERRORS Utility 3.3.10. TERM.ERRORS Utility ___________ _______ 3.3.10.1. Introduction ____________ This section describes the Terminal Errors Utility for the BOSS/VS. This utility allows the user to record and report errors on terminals connected to an Intelligent Serial Device Controller (ISDC). The operator may Start, Stop, Display, Select options and Reset the terminal error recording at any time. This utility allows the user to select the types of errors to record and set the maximum number of errors to record. The Terminal Errors File can hold up to the user specified number of terminal error event records. When this limit is reached the oldest terminal error events are deleted and new errors are recorded in their place. This utility will only record and report errors that happen on ISDC controllers, and only when devices on these controllers are accessed through Terminal Services. 3.3.10.1.1. Definitions ___________ The following are conditions on an ISDC device referenced by Terminal Services: 1. UART overrun error. Data was presented to the ISDC faster than it could be processed. Some data was probably lost. For this type of error, the line number in the error event record detected the error, but may or may not be the line causing the overrun. 2. UART framing error. This indicates a data error on the line number in the error event record. 3. UART break error. This indicates a data error on the line number in the error event record. This may be caused by a terminal power off, and may be reported as an 'Unknown' transmission error. 4. UART parity error. This indicates a data error on the line number in the error event record. 5. 'Unknown' transmission error. This indicates a data error on the line of one of the above three types, but the error type can not be determined. 6. Type ahead buffer overflow. This occurs when the line buffer is not being emptied fast enough to keep up with the characters being input. Some input data has been lost. TERM.ERRORS Utility SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg069 7. I/O abort error. This indicates that the ISDC was not able to process data properly. 3.3.10.1.2. Information Entered ___________ _______ The information required to run the Terminal Errors Utility includes: 1. The operator command for the utility; Start, Stop, Display, Select options and Reset the terminal error recording. Some of these commands also require options to be entered by the operator; refer to the section for each command. 2. The information recorded in the Terminal Errors File about terminal error events is input by the utility for user display. 3.3.10.1.3. Information Returned ___________ ________ This utility records information about terminal errors in the Terminal Errors File. This information is returned to the operator by the Display errors function of this utility. The information for each error includes: 1. Terminal error event sequence number. Consecutive error sequence number, since reset, of the error; whether or not the error event is recorded. 2. Date of error, in system date format when error occurred. 3. Time of error. 4. Controller number that had the error; 0..63. 5. Line number that had the error; 0..8. 6. Terminal number that had the error; Tn. 7. Error four-tuple of error code for the error. 8. Error type; one of the seven types listed in Section 3.3.10.1.1. Text for the recorded error four-tuple is displayed. The terminal error display may be directed to any utility output device by the OUTPUT DEVICE option of the Display function. TERM.ERRORS Utility 3.3.10.1.4. Procedures For Using Utility __________ ___ _____ _______ The Terminal Errors Utility may be run from the BOSS/VS system console mode or from a command file. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg070 Since all of the options may be specified from a command file this utility may be used as part of an automated procedure to report errors and reset the terminal errors file. The options for any function may be specified by parameters on the command line, as shown with each command. All of the defaults of each function are specified in the system command file entry for the function. These may be changed in the user command file by the CMDCONVERT utility. If no parameters are specified on the command line then the utility is in interactive mode and the function parameters, if any, will be prompted for by the selected function, on data entry screens. If any of the parameters are specified on the command line then the utility is not in interactive mode, and no function's parameters will be prompted for. In this case, the function parameters will be the command file defaults and the parameters specified on the command line. 3.3.10.1.4.1. By Command With Parameters __ _______ ____ __________ The Terminal Errors Utility may be run as a command with parameters by the following commands. 1. DISPLAY - Terminal errors are displayed. The operator is prompted for the display options if they are not entered with the command, as shown below. See section 3.3.10.1.4.2.1 for more information on this function and its options. If ALLCTRLS is YES then CTRL is ignored. If ALLERRORS is YES then the individual error type parameters is set to YES. TERM.ERRORS.DISPLAY {ALLCTRLS = } {CTRL = <0>} {ALLERRORS = } {OVERRUN = } {FRAMING = } {BREAK = } {PARITY = } {UNKNOWN = } {OVERFLOWS = } {ABORT = } {BDATE = <00/00/00>} {EDATE = } {OUTPUT = } {OUTACTION = } TERM.ERRORS Utility {QUIET = } The OUTACTION option specifies the action (D/A/N) to be performed when the output device is a file and the file exists. Refer to the description of the OUTPUT DEVICE option in section 3.3.10.1.4.2.1. Note: The following parameters are not available as command parameters due to CMDCONVERT limitations. {BTIME = <00:00:00>} {ETIME = <23:59:59>} SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg071 2. START - Terminal error recording is started. See section 3.3.10.1.4.2.2 for for more information on this option. TERM.ERRORS.START {QUIET = } When the start terminal error recording command is initiated it displays: Starting Terminal Error Recording When the command is complete it displays the state of the error recording: Terminal error recording is or 3. STOP - Terminal error recording is stopped. See section 3.3.10.1.4.2.3 for for more information on this option. TERM.ERRORS.STOP {QUIET = } When the stop terminal error recording command is initiated it displays: Stopping Terminal Error Recording When the command is complete it displays the state of the error recording: Terminal error recording is or 4. SELECT - Terminal error recording selection options are set. The operator is prompted for the SELECTION options if they are not entered with the command, as shown below. See section 3.3.10.1.4.2.4 for for more information on this function and its options. If ALLCTRLS is YES then CTRL is ignored. If ALLERRORS is YES then the individual error type parameters set to YES. TERM.ERRORS.SELECT {ALLCTRLS = } {CTRL = <0>} {ALLERRORS = } TERM.ERRORS Utility {OVERRUN = } {FRAMING = } {BREAK = } {PARITY = } {UNKNOWN = } {OVERFLOWS = } {ABORT = } {ERRORS = <100>} {QUIET = } When the select terminal error recording options command is initiated in non-interactive mode, it displays: Setting Terminal Error Recording When the command is complete, it displays the state of the error recording: SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg072 Terminal error recording options set Terminal error recording is or 5. RESET - Terminal error recording is reset. See section 3.3.10.1.4.2.5 for more information on this option. TERM.ERRORS.RESET {QUIET = } When the reset terminal error recording command is initiated, it displays: Resetting Terminal Error Recording When the command is complete, it displays the state of the error recording: Terminal error data is reset Terminal error recording is or 6. HELP - Help information is displayed for the Terminal Errors Utility. TERM.ERRORS.HELP {PRINTER = } {QUIET = } 3.3.10.1.4.2. By Menu Or Command Without Parameters __ ____ __ _______ _______ __________ The Terminal Errors Utility is run by entering TERM.ERRORS as a command. No command line parameters are allowed. The operator is first prompted for the function to perform on the main option menu, as shown in Figure 3-20. The Terminal Errors Utility can be selected from the System TERM.ERRORS Utility Utilities Menu. If there is an error condition in the Terminal Error Log then the error status is displayed before the user selection is requested. See Section 3.3.10.1.5. If a '?' is entered at the first field, help information is displayed to the user. If an escape key is detected, it will interrupt the current function and display: Terminal Errors Utility, user escape detected, 'CR' to continue: on line 23. If it is detected during one of the Terminal Error Log functions, the interactive function screen will be redisplayed, if any. Otherwise main option (Figure 3-20) screen will be redisplayed. Figure 3-20. Main Option Screen ______ _____ ____ ______ ______ MAI BASIC FOUR, INC. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg073 TERMINAL ERRORS UTILITY MAIN OPTIONS ------------------------------------------------------------------------------- OPTIONS: 1. DISPLAY TERMINAL ERRORS 2. START ERROR RECORDING 3. STOP ERROR RECORDING 4. SELECT RECORDING OPTIONS 5. RESET ERROR RECORDING ENTER OPTION NUMBER: XX 'CTL-IV' TO EXIT Terminal error recording is or _______________________________________________________________________________ _______________________________________________________________________________ TERM.ERRORS Utility 3.3.10.1.4.2.1. Option 1, DISPLAY TERMINAL ERRORS ______ __ _______ ________ ______ The display errors function allows the user to display the terminal errors that have been recorded in the Terminal Errors File. If in interactive mode, the screen shown in Figure 3-21 is displayed to allow the user to select the error display options. Figure 3-21. Display Errors Option Screen ______ _____ _______ ______ ______ ______ MAI BASIC FOUR, INC. TERMINAL ERRORS UTILITY DISPLAY OPTIONS ------------------------------------------------------------------------------- ALL CONTROLLERS : XXXXXXXXX CONTROLLER NUMBER : XXXXXXXXX ALL ERROR TYPES : XXXXXXXXX UART OVERRUN ERRORS : XXXXXXXXX UART FRAMING ERRORS : XXXXXXXXX UART BREAK ERRORS : XXXXXXXXX UART PARITY ERRORS : XXXXXXXXX UNKNOWN TRANSMIT ERRORS : XXXXXXXXX INPUT BUFFER OVERFLOWS : XXXXXXXXX I/O ABORT ERRORS : XXXXXXXXX BEGINNING DATE : XXXXXXXXX ENDING DATE : XXXXXXXXX BEGINNING TIME : XXXXXXXXX ENDING TIME : XXXXXXXXX OUTPUT DEVICE : XXXXXXXXXXXXXXXXXXX ENTRIES CORRECT (Y/N): XXXXXXXX _______________________________________________________________________________ _______________________________________________________________________________ 3.3.10.1.4.2.1.1. Field Descriptions _____ ____________ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg074 The display errors option screen allows the user to select for display a subset of the total terminal errors that are recorded. The errors that will be displayed are those that meet all of the criteria selected, as follows: 1. ALL CONTROLLERS: This is used to specify if errors are to be displayed for all ISDCs or for only one ISDC. When the cursor reaches this field the prompt: Select errors on all controllers (Y/N) TERM.ERRORS Utility is displayed on line 23. The initial default is 'YES'. If a 'YES' answer is given then errors on all controllers will be displayed and the cursor moves to the 'ALL ERROR TYPES' field; the next field is skipped and blanked. If a 'NO' answer is given then errors will be displayed for one ISDC only and the cursor moves to the next field. 2. CONTROLLER NUMBER: This is used to specify the controller number when errors for only one controller are to be displayed. When the cursor reaches this field the prompt: Enter controller number for errors display (0..63) is displayed on line 23. The initial default is 0. The user may enter 0 to 63 to select an ISDC number. Any other entry will generate the error: Invalid INTEGER parameter, 'CR' to continue: on line 23. 3. ALL ERROR TYPES: This is used to specify if errors are to be displayed for all error types or for only selected error types. When the cursor reaches this field the prompt: Select all error types (Y/N) is displayed on line 23. The initial default is 'YES'. If a 'YES' answer is given then all error types will be displayed and the cursor moves to the 'BEGINNING DATE' field; the next seven fields are skipped and set to 'YES'. If a 'NO' answer is given then any combination of error types may be selected for display and the cursor moves to the next field. Note: if one of the following error types is 'optional set' to 'NO' in the command file then this field has no effect on it; it will be used as 'NO'. 4. UART OVERRUN ERRORS: This field is used to specify if UART overrun errors are to be displayed. The user may enter 'YES' to select this error type or 'NO' to deselect this error type. The initial default is 'YES'. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg075 5. UART FRAMING ERRORS: This field is used to specify if UART framing errors are to be displayed. The user may enter 'YES' to select this error type or 'NO' to deselect this error type. The initial default is 'YES'. TERM.ERRORS Utility 6. UART BREAK ERRORS: This field is used to specify if UART break errors are to be displayed. The user may enter 'YES' to select this error type or 'NO' to deselect this error type. The initial default is 'YES'. 7. UART PARITY ERRORS: This field is used to specify if UART PARITY errors are to be displayed. The user may enter 'YES' to select this error type or 'NO' to deselect this error type. The initial default is 'YES'. 8. UNKNOWN TRANSMIT ERRORS: This field is used to specify if 'unknown' transmit errors are to be displayed. The user may enter 'YES' to select this error type or 'NO' to deselect this error type. The initial default is 'YES'. 9. INPUT BUFFER OVERFLOWS: This field is used to specify if input buffer overflow errors are to be displayed. The user may enter 'YES' to select this error type or 'NO' to deselect this error type. The initial default is 'YES'. 10. I/O ABORT ERRORS: This field is used to specify if I/O abort errors are to be displayed. The user may enter 'YES' to select this error type or 'NO' to deselect this error type. The initial default is 'YES'. 11. BEGINNING DATE: This field is used to specify a beginning date for errors to be displayed. The user may enter a date in the form of nn/nn/nn. The nn's refer to months, days and years in the current system date format. This entry will be compared to the dates recorded in the terminal error event record. The initial default is the 'minimum starting date' value, which is entered as 00/00/00 or 0/0/0. This value is defined to be less than any valid date, in any date format. An entry not in a valid date format will generate the error: Invalid DATE parameter, 'CR' to continue: on line 23. 12. ENDING DATE: This field is used to specify an ending date for errors to be displayed. The user may enter a date in the form of nn/nn/nn. The nn's refer to months, days and years in the current system date format. This entry will be compared to the dates recorded in the terminal error event record. The initial default is the current date. An entry not in a valid date format will generate the error: TERM.ERRORS Utility Invalid DATE parameter, 'CR' to continue: SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg076 on line 23. 13. BEGINNING TIME: This field is used to specify a beginning time for errors to be displayed. The user may enter a time in the form of nn:nn:nn. The nn's refer to hours, minutes and seconds. This entry will be compared to the times recorded in the terminal error event record. The user need not enter the seconds; if only hours and minutes are entered then zero seconds are used. The initial default is the starting time (00:00:00). An entry not in a valid time format will generate the error: Invalid TIME parameter, 'CR' to continue: on line 23. 14. ENDING TIME: This field is used to specify an ending time for errors to be displayed. The user may enter a time in the form of nn:nn:nn. The nn's refer to hours, minutes and seconds. This entry will be compared to the times recorded in the terminal error event record. The initial default is the the ending time (23:59:59). An entry not in a valid time format will generate the error: Invalid TIME parameter, 'CR' to continue: on line 23. 15. OUTPUT DEVICE: This field allows the user to choose whether to have the display function output only to the VDT, or also to a line printer or to a specified file. When the cursor reaches this field, the following prompt appears on line 23 of the screen: ENTER DEVICE OR FILE NAME, 'CR' = ___ where ___ is the current default. The initial default is VDT. If a file name exists, the utility will delete the existing file with the user's permission. The error and prompt on line 23 is: File already exists, do you wish to delete or append to the file, (D/A/N): An answer of 'D' will delete the existing file. An answer of 'A' will append the display to the existing file; the TERM.ERRORS Utility original information in the file will remain. An answer of 'N' will not delete the file and will prompt the user again for an output device. If a printer is selected the output will be spooled to the printer. Possible errors for this field are shown in Table 3-22. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg077 All errors are displayed on line 23. Table 3-22. Possible Errors for OUTPUT DEVICE Field. _____ _____ ________ ______ ___ ______ ______ ______ -------------------------------------------------------------- ERROR MESSAGE | REASON FOR ERROR -------------------------------------------------------------- Privilege insufficient | Do not have enough access rights to | delete existing file. Terminal already open | Terminal specified is already open. Invalid output device | Entry is not recognized as an | individual file name, a terminal | name or a printer name. Printer does not exist | Printer specified does not exist. -------------------------------------------------------------- 16. ENTRIES CORRECT (Y/N): The user must enter 'YES' answer to display the selected terminal errors. If 'NO' answer is entered the cursor will move to the 'ALL CONTROLLERS' field and the current selections are displayed as defaults. If is entered the cursor moves to the 'OUTPUT DEVICE' field. If is entered the cursor moves to the 'ALL CONTROLLERS' field and the initial defaults are displayed. 3.3.10.1.4.2.1.2. Functions Performed _________ _________ After the user has entered the display selection options, the selected terminal errors are displayed to the user. The errors displayed are those that meet all of the specified display selection options. The errors are displayed as shown in Figure 3-22. If the VDT screen becomes full and there are more errors to display the message: ('CTL-II'=no pause/'CTL-III'=no VDT/'CTL-IV'=quit), 'CR' to continue: is displayed on line 23 and the utility waits for the user response. A or will display the next page, will display all subsequent pages without pausing for TERM.ERRORS Utility user input, a will display Reading Terminal Errors File... on line 23, read the rest of the terminal error event records with no VDT display, then display the summary shown in Figure 3-23. Figure 3-22. Terminal Errors Display Screen ______ _____ ________ ______ _______ ______ MAI BASIC FOUR, INC. TERMINAL ERRORS UTILITY ERROR DISPLAY ------------------------------------------------------------------------------- SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg078 Number Date Time ISDC Line Name Error Description XXXXXX XX/XX/XX XX:XX:XX XX XX XXXXXXXX XXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXX XXXXXX XX/XX/XX XX:XX:XX XX XX XXXXXXXX XXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXX XXXXXX XX/XX/XX XX:XX:XX XX XX XXXXXXXX XXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXX XXXXXX XX/XX/XX XX:XX:XX XX XX XXXXXXXX XXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXX XXXXXX XX/XX/XX XX:XX:XX XX XX XXXXXXXX XXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXX XXXXXX XX/XX/XX XX:XX:XX XX XX XXXXXXXX XXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXX XXXXXX XX/XX/XX XX:XX:XX XX XX XXXXXXXX XXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXX XXXXXX XX/XX/XX XX:XX:XX XX XX XXXXXXXX XXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXX XXXXXX XX/XX/XX XX:XX:XX XX XX XXXXXXXX XXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXX XXXXXX XX/XX/XX XX:XX:XX XX XX XXXXXXXX XXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXX XXXXXX XX/XX/XX XX:XX:XX XX XX XXXXXXXX XXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXX XXXXXX XX/XX/XX XX:XX:XX XX XX XXXXXXXX XXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXX XXXXXX XX/XX/XX XX:XX:XX XX XX XXXXXXXX XXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXX XXXXXX XX/XX/XX XX:XX:XX XX XX XXXXXXXX XXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXX XXXXXX XX/XX/XX XX:XX:XX XX XX XXXXXXXX XXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXX XXXXXX XX/XX/XX XX:XX:XX XX XX XXXXXXXX XXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXX XXXXXX XX/XX/XX XX:XX:XX XX XX XXXXXXXX XXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXX XXXXXX XX/XX/XX XX:XX:XX XX XX XXXXXXXX XXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXX ('CTL-II'=no pause/'CTL-III'=no VDT/'CTL-IV'=quit), 'CR' to continue: _______________________________________________________________________________ _______________________________________________________________________________ The number displayed at the left is the terminal error event sequence number. This number is recorded with the terminal error event record. Gaps in the number sequence reflect errors that were not recorded, or not selected for display. If an output device other than the VDT is selected a title will be output: MAI BASIC FOUR, INC. TERMINAL ERROR LOG UTILITY When the error display is complete the total number of recorded errors is displayed, along with the 'ON' or 'OFF' state of the terminal error recording when the error display was started. Then the message: TERM.ERRORS Utility 'CR' to continue: is displayed on line 23 and the utility waits for the user to enter a . Then an error summary is displayed as shown in Figure 3-23. The total error counts for each ISDC are displayed, regardless of the error display selection options. Only ISDC controller numbers with nonzero error counts are displayed. If there are no ISDC errors recorded the error summary is not displayed, instead the message: No ISDC errors recorded, Terminal error recording is or is displayed, then the display function terminates, as described in Section 3.3.10.1.4.2.1.3. Figure 3-23. Terminal Errors Summary Display Screen ______ _____ ________ ______ _______ _______ ______ MAI BASIC FOUR, INC. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg079 TERMINAL ERRORS UTILITY ERROR SUMMARY ------------------------------------------------------------------------------- ISDC - ERRORS ISDC - ERRORS ISDC - ERRORS ISDC - ERRORS 0 XXXXX 16 XXXXX 32 XXXXX 48 XXXXX 1 XXXXX 17 XXXXX 33 XXXXX 49 XXXXX 2 XXXXX 18 XXXXX 34 XXXXX 50 XXXXX 3 XXXXX 19 XXXXX 35 XXXXX 51 XXXXX 4 XXXXX 20 XXXXX 36 XXXXX 52 XXXXX 5 XXXXX 21 XXXXX 37 XXXXX 53 XXXXX 6 XXXXX 22 XXXXX 38 XXXXX 54 XXXXX 7 XXXXX 23 XXXXX 39 XXXXX 55 XXXXX 8 XXXXX 24 XXXXX 40 XXXXX 56 XXXXX 9 XXXXX 25 XXXXX 41 XXXXX 57 XXXXX 10 XXXXX 26 XXXXX 42 XXXXX 58 XXXXX 11 XXXXX 27 XXXXX 43 XXXXX 59 XXXXX 12 XXXXX 28 XXXXX 44 XXXXX 60 XXXXX 13 XXXXX 29 XXXXX 45 XXXXX 61 XXXXX 14 XXXXX 30 XXXXX 46 XXXXX 62 XXXXX 15 XXXXX 31 XXXXX 47 XXXXX 63 XXXXX XXX ISDC Errors, Terminal error recording is or 'CR' to continue, 'CTL-IV' to exit this function: _______________________________________________________________________________ _______________________________________________________________________________ After the error summary is displayed, the display function terminates as described in Section 3.3.10.1.4.2.1.3. TERM.ERRORS Utility 3.3.10.1.4.2.1.3. Display Termination _______ ___________ When the display function terminates the message: 'CR' to continue, 'CTL-IV' to exit this function: is displayed on line 23 and the utility waits for the user response. If or is entered, in interactive mode (command parameters not entered on the command line), the error display option screen is redisplayed, as in Figure 3-21. If is entered, and this function was selected from the main option menu, then that menu is redisplayed, as in Figure 3-20, otherwise control returns to the command mode that called this function. 3.3.10.1.4.2.2. Option 2, START ERROR RECORDING ______ __ _____ _____ _________ This function allows the user to start the recording of terminal error events. When this function is performed the terminal event recording is turned on. If the event recording was already on, it remains on. When this function begins, it displays the message: Starting Terminal Error Recording SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg080 When this function is complete, if there was an error condition in the Terminal Error Log then the error status is displayed as shown in Section 3.3.10.1.5. Finally, the running status of terminal error recording is displayed by the message: Terminal error recording is or Then, if this function is in interactive mode the message: 'CR' to continue is displayed on line 23 and the utility waits for the user response. If this function was selected from the main option menu then that menu is redisplayed, as in Figure 3-20. Otherwise control returns to the command mode that called this function. TERM.ERRORS Utility 3.3.10.1.4.2.3. Option 3, STOP ERROR RECORDING ______ __ ____ _____ _________ This function allows the user to stop the recording of terminal error events. When this function is performed the terminal event recording is turned off. If the event recording was already off, it remains off. When this function begins, it displays the message: Stopping Terminal Error Recording When this function is complete, if there was an error condition in the Terminal Error Log then the error status is displayed as shown in Section 3.3.10.1.5. Finally, the running status of terminal error recording is displayed by the message: Terminal error recording is or Then, if this function is in interactive mode the message: 'CR' to continue is displayed on line 23 and the utility waits for the user response. If this function was selected from the main option menu then that menu is redisplayed, as in Figure 3-20. Otherwise control returns to the command mode that called this function. 3.3.10.1.4.2.4. Option 4, SELECT RECORDING OPTIONS ______ __ ______ _________ _______ This function allows the user to select the type and number of errors to be recorded. If in interactive mode, the screen shown in Figure 3-24 is displayed to allow the user to select the error recording SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg081 options. The first default values on the screen are the current values in effect for terminal error recording. If the user wishes to use the defaults from the command file, a may be entered, on any field but the first. If not in interactive mode, only the command line parameters and command file defaults are used for this function and the message: Setting Terminal Error Recording is displayed. TERM.ERRORS Utility Figure 3-24. Select Recording Options Screen ______ _____ ______ _________ _______ ______ MAI BASIC FOUR, INC. TERMINAL ERRORS UTILITY RECORDING OPTIONS ------------------------------------------------------------------------------- ALL CONTROLLERS : XXXXXXXX CONTROLLER NUMBER : XXXXXXXX ALL ERROR TYPES : XXXXXXXX UART OVERRUN ERRORS : XXXXXXXX UART FRAMING ERRORS : XXXXXXXX UART BREAK ERRORS : XXXXXXXX UART PARITY ERRORS : XXXXXXXX UNKNOWN TRANSMIT ERRORS : XXXXXXXX INPUT BUFFER OVERFLOWS : XXXXXXXX I/O ABORT ERRORS : XXXXXXXX NUMBER OF ERRORS : XXXXXXXX ENTRIES CORRECT (Y/N): XXXXXXXX _______________________________________________________________________________ _______________________________________________________________________________ 3.3.10.1.4.2.4.1. Field Descriptions _____ ____________ The select errors option screen allows the user to select a subset of terminal errors that are to be recorded. The errors that will be recorded are those that meet all of the criteria selected, as follows: 1. ALL CONTROLLERS: This is used to specify if errors are to be recorded for all ISDCs or for only one ISDC. When the cursor reaches this field the prompt: Select errors on all controllers (Y/N) is displayed on line 23. The initial default is 'YES'. If a 'YES' answer is given then errors on all controllers will be recorded and the cursor moves to the 'ALL ERROR TYPES' field; the next field is skipped and blanked. If a 'NO' answer is given then errors will be SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg082 recorded for one ISDC only and the cursor moves to the next field. 2. CONTROLLER NUMBER: This is used to specify the controller number when errors for only one controller are to be TERM.ERRORS Utility recorded. When the cursor reaches this field the prompt: Enter controller number for error recording (0..63) is displayed on line 23. The initial default is 0. The user may enter 0 to 63 to select an ISDC number. Any other entry will generate the error: Invalid INTEGER parameter, 'CR' to continue: on line 23. 3. ALL ERROR TYPES: This is used to specify if errors are to be recordeded for all error types or for only selected error types. When the cursor reaches this field the prompt: Select all error types (Y/N) is displayed on line 23. The initial default is 'YES'. If a 'YES' answer is given then all error types will be recorded and the cursor moves to the 'NUMBER OF ERRORS' field; the next seven fields are skipped and set to 'YES'. If a 'NO' answer is given then any combination of error types may be selected for recording and the cursor moves to the next field. Note: if one of the following error types is 'optional set' to 'NO' in the command file then this field has no effect on it; it will be used as 'NO'. 4. UART OVERRUN ERRORS: This field is used to specify if UART overrun errors are to be recorded. The user may enter 'YES' to select this error type or 'NO' to deselect this error type. The initial default is 'YES'. 5. UART FRAMING ERRORS: This field is used to specify if UART framing errors are to be recorded. The user may enter 'YES' to select this error type or 'NO' to deselect this error type. The initial default is 'YES'. 6. UART BREAK ERRORS: This field is used to specify if UART break errors are to be recorded. The user may enter 'YES' to select this error type or 'NO' to deselect this error type. The initial default is 'YES'. 7. UART PARITY ERRORS: This field is used to specify if UART PARITY errors are to be recorded. The user may enter 'YES' to select this error type or 'NO' to deselect this error type. The initial default is 'YES'. TERM.ERRORS Utility SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg083 8. UNKNOWN TRANSMIT ERRORS: This field is used to specify if 'unknown' transmit errors are to be recorded. The user may enter 'YES' to select this error type or 'NO' to deselect this error type. The initial default is 'YES'. 9. INPUT BUFFER OVERFLOWS: This field is used to specify if input buffer overflow errors are to be recorded. The user may enter 'YES' to select this error type or 'NO' to deselect this error type. The initial default is 'YES'. 10. I/O ABORT ERRORS: This field is used to specify if I/O abort errors are to be recorded. The user may enter 'YES' to select this error type or 'NO' to deselect this error type. The initial default is 'YES'. 11. NUMBER OF ERRORS: This field is used to specify the maximum number of terminal error event records that may be recorded in the Terminal Errors File. When the cursor reaches this field the prompt: Enter maximum number of terminal errors to record, 'CR' = ___ is displayed on line 23, where ___ is the current default. The initial default is the current maximum. The user may enter 1 to 99999. Any other entry will generate the error: Invalid INTEGER parameter, 'CR' to continue: on line 23. 12. ENTRIES CORRECT (Y/N): The user must enter 'YES' answer to put the error selections into effect. If 'NO' answer is entered the cursor will move to the 'ALL CONTROLLERS' field and the current selections are displayed as defaults. If is entered the cursor moves to the 'NUMBER OF ERRORS' field. If is entered the cursor moves to the 'ALL CONTROLLERS' field and the initial defaults are displayed. 3.3.10.1.4.2.4.2. Functions Performed _________ _________ The recording selection options are set and in effect after the user responds with a 'YES' answer to the 'ENTRIES CORRECT' prompt, in interactive mode. If the event recording was off it remains off. If the event recording was on it remains on. After the selection options have been set the message: TERM.ERRORS Utility Terminal error recording options set is displayed. If there was an error condition in the Terminal Error Log then the error status is displayed as shown in Section 3.3.10.1.5. Finally, the running status of terminal error recording is SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg084 displayed by the message: Terminal error recording is or Then, if this function is in interactive mode the message: 'CR' to continue is displayed on line 23 and the utility waits for the user response. If this function was selected from the main option menu then that menu is redisplayed, as in Figure 3-20. Otherwise control returns to the command mode that called this function. 3.3.10.1.4.2.5. Option 5, RESET ERROR RECORDING ______ __ _____ _____ _________ This function allows the user to reset the Terminal Errors File data. When this function is performed the number of terminal error events recorded is set to zero. Previous error records can no longer be displayed. This also sets the terminal error event sequence number to 1. If the event recording was off, it remains off. If the event recording was on, it remains on. When this function begins it displays the message: Resetting Terminal Error Recording After the Terminal Errors File data has been reset, it displays the message: Terminal error data is reset If there was an error condition in the Terminal Error Log then the error status is displayed as shown in Section 3.3.10.1.5. Finally, the running status of terminal error recording is displayed by the message: Terminal error recording is or Then, if this function is in interactive mode the message: TERM.ERRORS Utility 'CR' to continue is displayed on line 23 and the utility waits for the user response. If this function was selected from the main option menu then that menu is redisplayed, as in Figure 3-20. Otherwise control returns to the command mode that called this function. If there was a problem accessing the Terminal Error Log control variables, the error message: Terminal Error Recording Control File Error SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg085 is displayed. If there was a problem during initialization of the Terminal Error Log, the error message: Terminal Error Recording Initialization Failed is displayed. In either of these cases, a second reset command will attempt to re-initialize the Terminal Error Log, with default parameters. If this is successful the message: Terminal Error Recording Reinitialized is displayed and error recording will proceed. In this case, any error event records will be preserved, if possible. If the Terminal Errors File becomes unuseable, it may be deleted; the reset function will create a new one if it does not exist. To re-initialize the Terminal Error Log at any time, the user may delete the Terminal Errors Options File (see Section 3.3.10.1.1 for the file name) and then issue two reset commands. 3.3.10.1.5. Terminal Errors Utility Error Reporting ________ ______ _______ _____ _________ The Terminal Errors Utility reports any error condition to the user (unless in quiet mode). The error four-tuple and the operation or file that caused the error are displayed on line 21: Error n,n,n,n on : xxxxxxxxxxxxxxxxxxxxxxxxxxxxx; The n,n,n,n represent the error four-tuple and the xxx's represent the operation or file name. For example, if there was a problem with accessing the Terminal Errors File, the xxx's are: 'Terminal Error Log Access'. If a file was not found, the xxx's are the file name. TERM.ERRORS Utility The text of the error message for the error four-tuple is displayed on line 22. The message: TERMINAL ERRORS UTILITY ERROR, 'CTL-IV' to exit, 'CR' to continue is displayed on line 23, and the utility waits for the user response. A or will continue, a will exit the utility. After the problem causing the error is corrected, the Reset function can be used to reset the error condition in the utility. See section 3.3.10.1.4.2.5. 3.4. LANGUAGES _________ 3.4.1. BASIC SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg086 _____ 3.4.1.1. Additional Logical Units __________ _______ _____ The number of logical channels available in BASIC has been increased to 64 (0-63). 3.4.1.2. PRC Function ___ ________ In BASIC, there now is a function which allows you to find the current precision in effect. This function has the syntax of =PRC The variable will be assigned the current precision in affect. This value will be carried over to CALLed programs also. Therefore a CALLed program may find out the precision of the calling program. If FLOATINGPOINT is in effect, PRC will return -1. For example the following program demonstrates the PRC function. >10 PRECISION 5 set precision to 5 >20 PRINT PRC print current precision >30 PRECISION 7 >40 PRINT PRC >50 PRECISION 14 >60 A=PRC >70 PRINT A >80 FLOATINGPOINT >90 PRINT PRC >RUN 5 7 14 -1 >READY 3.4.1.3. DMP Printer Mnemonics ___ _______ _________ In this release, are new mnemonics for parallel and serial DMP. The mnemonics and their function are shown below. Mnemonic Description ________ ___________ DACS De-select alternate character set EPM Even dot plot mode SACS Select alternate character set SPM1 Set printer to mode 1 SPM2 Set printer to mode 2 SPM3 Set printer to mode 3 SPM4 Set printer to mode 4 SPM5 Set printer to mode 5 3.5. COMMUNICATIONS ______________ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg087 3.5.1. Asynchronous STATUS Command ____________ ______ _______ The asynchronous driver now implements a new status command to enhance the old status command. This command is used as follows: READRECORD(chanl,KEY="STATUS",SIZ=1)string variable This command will return a one character status to the string specified. This character will indicate the status of the modem control signals CLEAR-TO-SEND (CTS) and DATA-SET-READY (DSR). If no error occurs, then these signals are set. If an error 5 occurs, then one of these bits have changed. The bits (in order 7-6-5-4-3-2-1-0) are: Signal Bit ______ ___ DSR 5 CTS 4 If an error 5 has occurred, there are alternate statuses: Error Bit _____ ___ UART Break error 4 UART Framing error 3 UART Parity error 2 UART Overrun error 1 3.5.2. Asynchronous STAT Command ____________ ____ _______ This command also returns status information. The format of the status byte changes in this release. The command is used as follows: READRECORD(chanl,KEY="STAT",SIZ=1)string variable The status meanings are listed below: Value Meaning _____ _______ 00 No problem indicated 01 UART Overrun error 02 UART Parity error 03 UART Framing error 04 UART Break error 05 DATA-SET-READY (DSR) dropped 06 CLEAR-TO-SEND (CTS) dropped 3.5.3. TBC AUTODIAL Utility ___ ________ _______ The 8.4E BOSS/VS release contains a very useful new feature in the TBC AUTODIAL facility. This new feature allows the SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg088 definition and retrieval of multiple Station Lists. In previous BOSS/VS releases, only one Station List was available to the AUTODIAL utility. If a user needed multiple Station Lists, he either had to erase the current list and input the new information, or keep multiple copies of the AUTODIAL file, "BADFL", in separate nodes. Then the various copies would be selectively renamed into the .PGMTBC. node to access the alternate versions. This release builds a multiple Station List feature into the TBC utility system. 3.5.3.1. Operational Differences ___________ ___________ There are two major operational differences between the new 8.4E AUTODIAL utility and previous releases. The first difference is that upon entry into "ACS", the new version now prompts the user to enter the name of the ACU Station List that is to be used with the session with the following INPUT statement. ENTER NAME OF ACU STATION LIST FILE TO USE (INCLUDING PREFIX): _ The full path name of the ACU Station List must be entered correctly or the utility will repeat the prompt. If only the default ACU Station List is desired, then the operator need only enter "BADFL". Once a correct ACU Station List name has been entered, the utility proceeds as it has in previous releases. The second, and most important, change is in the functioning of the ACU Station List maintenance utility, "ACUTD". The first prompt to the utility now asks for operator input of the Station List file name: ENTER PREFIX WHERE ACU STATION LIST RESIDES: _ (CR = USER PREFIX, MB-I = DISPLAY NAMES, MB-IV = EXIT) Once an acceptable ACU Station List prefix has been entered, another new prompt appears: ENTER NAME OF ACU STATION LIST: _ 'CR' = ACU DEFAULT STATION LIST 'MB-IV' = DELETE AN ACU STATION LIST 'MB-II or MB-III' = RETURN TO PREVIOUS MENU 'MB-I' = LIST NAMES OF ACU STATION LISTS If the user enters a Station List name that does not exist, the utility will offer to define a new list with the following prompt: CAN NOT FIND .XXX.XXX ACU STATION LIST DO YOU WANT TO DEFINE IT? (Y='CR'/N): _ If an 'N' is input, the "ENTER NAME OF ACU STATION LIST" prompt is repeated. If the user inputs a 'Y', a new ACU Station List is defined and the "ACU STATION UTILITY MENU" is run. A 'CR' will result in the use of the default ACU Station List SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg089 of "BADFL". "BADFL" is the only ACU Station List provided automatically with the TBC utilities set. All additional ACU Station Lists must be user input. 3.6. DIAGNOSTICS ___________ 3.6.1. DEMON _____ DEMON has been enhanced to allow testing of the 7000 system and related peripherals. On tape tests, DEMON allows the option of rewinding the tape prior to each test or continue testing at the current tape position. This will allow test personnel to test all of the tape instead of just the beginning (option #25 on the tape test menu). Another option on the tape tests is the WRITE TAPE ONLY (option #22). This test writes 10 records of 16,384 bytes each of different patterns. Option #23 allows you to do option #22 with a read verification. Some new tape tests have been added. These new tests appear as options #8-17. These options will not run unless the diagnostic switch is set or the disk is labeled as a scratch pack. Tests #8 and #9 are tests to check the CRC error logic of the controller. These tests will not work on the 7000 series. Tests #10 and #11 are tests to check the ECC error logic of the controller. Tests #12 and #13 write a data pattern to disk, change memory and then issue a verify command expecting the controller to return verify errors. Tests #14 and #15 check to see if the controller performs an alternate cylinder read and write correctly. Test #16 writes and reads 1 to 64 sectors. Test #17 is used to exercise the controller. It randomly selects a read, write or seek. Also randomly chosen are record size and disk address. 3.6.2. DCL and NEWX ___ ___ ____ Both of these on-line diagnostics have been modified to test the 7000 Systems and its related peripherals. 3.6.3. HEADS _____ The program HEADS is a useful program that allows logical sectors to be mapped into head, cylinder and sector number and vice-versa. The program will ask you to select the type of disk you want. It then gives you the choice to convert logical sector to physical attributes or physical attributes to logical sector. The program is under the INST node: (family).R4E56.INST.HEADS 3.7. APPLICATION SOFTWARE SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg090 ___________ ________ 3.7.1. DataWord ________ 3.7.1.1. Merged DataWord II ______ ________ __ MAI Basic Four is pleased to announce the release of Merged DataWord II for MPx 7000, 8000, 9000, and 9500 Series Systems on release levels 8.4E and 8.5C/9.5C and above. Instead of opening each DataWord II file individually, reading it, and closing it, as the procedure was previously done, all files are merged into two DataWord files, DWPGMS and DMDIR. Merged DataWord will speed up the response time of DataWord up to 20%. This improvement is most apparent when selecting screens (menus, options, etc.). Merged DataWord also saves disk space. The process for merging DataWord II is as follows: 1) Unbundle DataWord and obtain individual DataWord programs. 2) Customize (for international use only). 3) Merge the individual DataWord programs, and obtain Merged DataWo2d' PROCEDURES You can unbundle and merge DataWord into any node. THE UNBUNDLING PROCEDURE In command mode type: !UNBUNDLE The screen will display: INITIALIZING. . . . . . . . . . . . . . . The system is checking 'DMDIR' to make sure DataWord files do not exist. If they do, an error will appear stating the files already exist, and the process will be aborted. CREATING DWPGM'S (family).NODE.DataWord file . . .. . . . . . . etc. The unbundling process has begun. VERIFY (family).NODE.DataWord file . . . . . . . . . . etc. The system is comparing each record in the unbundled version against the merged version. DWPGM will be deleted but will be recreated when DataWord is merged. MERGING DATAWORD SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg091 In command mode type: !MERGE The screen will display: INITIALIZING CHECK OUT PARAMETERS . . . . . . . . . . MERGING (family).NODE.DataWord file . . . . . etc. The system is merging the DataWord files. VERIFY (family).NODE.DataWord file . . . . . etc. The system is comparing each record in the individual DataWord programs against the merged version. DELETING INDIVIDUAL FILES (family).NODE.DataWord file IS DELETED etc. The verify is complete. The system is deleting the individual DataWord files since they are no longer needed. DataWord is now merged. 3.7.1.2. DataWord Printer Queue Speed Enhancement ________ _______ _____ _____ ___________ In this release, the time from when a document is submitted to the queue and the time when the document starts printing has been decreased. Documents now submitted to the print queue will be ready to print in less time than on previous releases. 3.8. GENERAL INFORMATION _______ ___________ 3.8.1. Software Announcement ________ ____________ With this release, a copy of this software announcement exists as a serial file on the system. This allows the user to get copies of this announcement if needed. This file can be submitted to a printer using the SUBMIT utility. The document file is named: (family).R4E56.INST.DOC.SA84E 3.8.2. Four-Tuple Messages __________ ________ In this release, some four-tuple messages have been modified to provide enhanced error reporting capabilities. When determining the text associated with a four-tuple on an 8.4E SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg092 system, use the ERR function to ensure the correct error text is displayed. There is a serial file on the system that contains all possible four-tuples and their meanings. The name of the file is: (family).R4E56.SYS.ERRORS.LIST This file can be submitted to the printer using the SUBMIT utility. The listing requires 132 column paper. 3.8.3. DISKREAD Function ________ ________ The DISKREAD function, which reads the disk for errors, no longer exists as a separate function. DISKREAD has been implemented as Option number 8 in DISKANALYZER (see the section on DISKANALYZER). 3.8.4. Disk to Disk Image Copy ____ __ ____ _____ ____ The Disk to Disk Image Copy in a TYPE 3 LOAD now contains expanded error reporting. During the beginning of the actual copy process, the option will destroy the files system space of the destination pack. This is to guarantee that improperly copied packs will not be used as valid packs. If the copy of the entire family completes without error, the file system is restored on the destination pack. On 8.4D, when an error occurred during a copy, an error message was displayed indicating the beginning sector of the track that had the error. The option would then abort, leaving the destination pack unusable. Beginning in 8.4E, when an error occurs, the option will attempt a sector by sector copy on the track on which the error occurred. If no errors are encountered on the sector by sector copy for that track, the option continues the copy on a track by track basis again. If an error does occur on the sector by sector copy, an error message is displayed giving the exact sector number of the error. Also displayed is the head, cylinder, and sector number within the track. The user is then prompted to abort, retry, or continue. If the user aborts, the option will abort and leave the destination pack unusable. If the retry option is chosen, the option will retry the operation for that sector. If it is successful, the copy will continue, or you will get the same abort, retry, or continue message. If you continue, the option will continue on the next sector after the error. If the user continues through all the errors to the end of the copy, the file system of the destination pack will be restored. This will allow the user to have access to portions of the family which copied correctly. 4. HARDWARE ________ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg093 4.1. LOWEST ACCEPTABLE REVISION LEVELS FOR PCBAS ______ __________ ________ ______ ___ _____ The Lowest Acceptable Revision Levels for PCBAs for systems on 8.4E are identical to those for 8.4B/C/D with the following exceptions: 1) BMTC 903413 PCBAs: Revision R Revision T (For MCS support) 2) ACS 903379 PCBAs: Revision Boot Prom ________ ____ ____ L 2.0.0.1 T,Z 2.0.0.2 (Required for BMTC) Y 2.0.0.3 AA 2.0.0.5 NOTES: ACS Revision W is obsolete and should not be used. The Boot Prom level can be found in the OSINFO display. 4.2. PARALLEL DMP DEVICE VARIANCE CONFIGURATION ________ ___ ______ ________ _____________ With the 8.4E release, the parallel DMP device variance code needs to be changed. Previously, the DMP printer had the same code as a matrix printer. Changing the DMP printer to a new device variance is done by changing the switch settings on the appropriate controller board. The new DMP printer switch settings are: TDP CONTROLLER BOARD 903217 OR 903453 ___ __________ _____ ______ __ ______ Switch 4C Position # 8 7 6 _ _ _ O O C MPC CONTROLLER BOARD 903500 OR 903546 ___ __________ _____ ______ __ ______ 903500 ______ Switch 2A (SW2) PRINTER 0 S2-2 S2-5 S2-8 PRINTER 1 S2-3 S2-6 S2-7 ____ ____ ____ C O O 903546 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg094 ______ Switch 2A (SW2) Switch 9F (SW5) * Position # Position # (Strobe) Printer 0 S2-3 S2-4 S2-5 Printer 0 S5-1 Printer 1 S2-6 S2-7 S2-8 Printer 1 S5-2 ____ ____ ____ ____ O C O O * NOTE: Switch SW5, location 9F, selects whether a printer will receive a "normal" or inverted data strobe. O-Open or Off C-Closed or On 5. INSTALLATION ____________ 5.1. INTRODUCTION ____________ There are two ways to install 8.4E: 1) Install a new system 2) Update a system If you are installing a new system go to section 5.2. If you are upgrading a system go to section 5.3. 5.2. NEW INSTALLATION ___ ____________ The loading of 8.4E is done the same as any other BOSS/VS release. 5.2.1. Installing the O.S. __________ ___ ____ 5.2.1.1. ALT LOAD ___ ____ A) Insert the new release tape into the tape drive. B) Press the "ALTLOAD" button on the front panel. C) Enter the appropriate system disk (0 or 1) or if drives 0 and 1 are both system disks, enter "2" to update both disks. D) Enter a "0" to update WCS slot 0. E) Enter a "Y" to the prompt "Are you SURE you want to overwrite this WCS ? (Y/)". The system automatically updates the OS and WCS slot 0 on both disks, if selected. When this is complete, the system prompts "DONE - READY FOR NORMAL LOAD". SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg095 Reload by pressing the LOAD button. 5.2.1.2. ENTER A TYPE 3 LOAD (SPECIAL FUNCTIONS) _____ _ ____ _ ____ ________ __________ Options 1-4 must be done to insure proper operation. 5.2.1.2.1. Sizing the Dump Area (Change Volume Information) ______ ___ ____ ____ _______ ______ ____________ Presently, on all MPx release levels, the operating system computes the size of the Dump Area using information derived from the currently installed configuration record in conjunction with a survey of the installed hardware at the Installation Procedures - New Installation time of the last system load. This method has two major disadvantages: 1. If a disk has no installed configuration record, the Dump Area size is computed on a minimum configuration, regardless of what hardware is installed in the system. 2. If additional main memory and shared memory controllers are installed in the system, and this exceeds the limits set by the currently installed configuration record, this new hardware will not be included when computing the size of the Dump Area. The solution to this problem is for the operating system to actually check the installed hardware when computing the size of the Dump Area, and this will be done in releases 8.6A/9.6A. In the meantime, if either one of the above two situations apply to your system, it will be necessary to compute the size of the Dump Area by determining exactly what main memory and shared memory controllers are installed in the system, and adding up the area required for each. The total should be input in Option 1 (Change Volume Information) of a TYPE 3 LOAD after the prompt "SIZE OF DUMP AREA (FOR SYSTEM DISK ONLY):". All other numbers on the Option 1 screen that refer to the size of the Dump Area should be ignored. Listed below are the main memory and shared memory controllers and the values to be used when computing the size of the Dump Area: 1. Each megabyte of main memory (903349, 903516)...1024 (x 1024 bytes) 2. Each 4-Way controller (903374).................. 64 (x 1024 bytes) 3. Each 8-Way controller (903383).................. 64 (x 1024 bytes) 4. Each 16-Way controller (903437.................. 128 (x 1024 bytes) 5. Each IMLC controller (903381, 903534)........... 64 (x 1024 bytes) 6. Each BMTC controller (903413)................... 128 (x 1024 bytes) EXAMPLE: A system has 8 MB of main memory, 1 4-Way controller, 2 16-Way controllers, 1 IMLC, and 1 BMTC. Compute the size of the Dump Area as follows: 8 MB main memory (8 x 1024) = 8192 (x 1024 bytes) 1 4-Way controller = 64 (x 1024 bytes) 2 16-Way controllers (2 x 128) = 256 (x 1024 bytes) 1 IMLC = 64 (x 1024 bytes) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg096 1 BMTC = +128 (x 1024 bytes) ---- Total 8704 (x 1024 bytes) "SIZE OF DUMP AREA (FOR SYSTEM DISKS ONLY):" 8704 (x 1024 bytes) When sizing the Dump Area, you may want to round up to the Installation Procedures - New Installation next megabyte or add an extra megabyte or two for future expansion. If it becomes necessary to enlarge the Dump Area, you must do a complete back up, reinitialize the system disks (options 1-4 in a TYPE 3 LOAD), and do a restore from the back up in a TYPE 2 LOAD. 5.2.1.2.2. Option 1, CHANGE VOLUME INFORMATION ______ __ ______ ______ ___________ SYSTEM DISKS: (displayed) DRIVE NUMBER:__________ Enter the disk to update. SERIAL NUMBER:_________ Enter CR to accept current serial number. DISK CONFIGURATION (1=SYSTEM, 2=DATA, 3=BACKUP):____ Enter the appropriate disk type. SIZE OF DUMP AREA....:______ Enter the size of the dump area given by the line below this prompt as the area needed for both main memory and shared memory controllers. FILE SYSTEM SPACE:______ Enter the number displayed at the bottom of the screen for this prompt. The display will appear as "CR=X" where X is the maximum space allowed. UPDATE DISK (Y/N): Enter "Y" 5.2.1.2.3. Option 2, CHANGE INSTALLATION PARAMETERS ______ __ ______ ____________ __________ SYSTEM DISKS: (displayed) DRIVE NUMBER:_______ PRIMARY PREFIX ? Enter (family).R4E56.SYS. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg097 Installation Procedures - New Installation Where (family) is the family where the operating system files reside. SECONDARY PREFIX ? Enter (family).R4E56.SYS. Where (family) is the family where the alternate operating system files reside. DEFAULT USER FAMILY NAME ?:________ Enter default user family SECURITY (E=ENABLED, D=DISABLED):___ FILE SYSTEM WRITE THROUGH? (E=ENABLED, D=DISABLED):___ For conversion purposes, set this option to D (disabled). This will speed up the conversion process. It can be changed later if desired. WRITE THROUGH DEFAULT ON FILE CREATE (E=ENABLED, D=DISABLED):__ This parameter specifies what the default write through will be on a file created through a BASIC file create or through the CREATE utility. UPDATE DISK WITH INSTALLATION PARAMETERS? (Y/N)__ Display: PARAMETERS SUCCESSFULLY WRITTEN TO DISK 5.2.1.2.4. Option 3, UPDATE FAMILY INFORMATION ______ __ ______ ______ ___________ AVAILABLE DRIVES: (displayed) FAMILY BASE DRIVE NUMBER:___ DRIVE NUMBERS OF OTHER DISKS IN FAMILY? (TYPE SPACES FOR NO OTHER DRIVES): Enter all other drive numbers for this family or spaces if none. The drives must be fixed media drives and in 8.4E format. UPDATE DISK (Y/N) ? Installation Procedures - New Installation 5.2.1.2.5. Option 4, INITIALIZE FAMILY DIRECTORY ______ __ __________ ______ _________ FAMILY NAME:______ Enter family name. INITIALIZE FAMILY (Y/N)?__ Option 1 must be done on all disks. Option 2 must be done to SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg098 system disks only. Options 3 and 4 must be done for all families. 5.2.1.3. Restoring the O.S. _________ ___ ____ Enter SAVERESTORE in a TYPE II load and choose option #2 "RESTORE FILES FROM TAPE". The screen appears as in figure 5-1. At the prompt for output device, enter a parallel printer so that a listing of the restore operation is produced. This listing can be used to make sure all files were restored correctly. At the prompt, "FILE SPECIFIERS", enter ".". Enter to all other questions. All system files will be restored to disk. Please note that once all files are restored to disk, the message "AUTOMATIC COMPARE, CR TO CONTINUE" appears. This automatically rewinds the tape and begins the compare operation. This only occurs when the compare option is selected. When the compare is completed, enter a CTL-IV to return to the "SAVERESTORE" menu. Reload the system and enter a TYPE I load. Now go to section 5.4 to complete the installation. Figure 5-1. Restore Screen ______ ____ _______ ______ -------------------------------------------------------- RESTORE FILES TAPE SET.ID: DRIVE-NUM: REEL-NUM: PRIMARY PREFIX: (FAMILY).NODE. FILETYPE (D/P/CR=ALL) COMPARE (CR=Y/N) DATE (MM/DD/YY) TIME (HH:MM) OUTPUT DEVICE (CR=VDT) DELETE EXISTING FILES (CR=Y) VERIFY (Y/CR=N) ENTRIES CORRECT (Y/N) -------------------------------------------------------- Installation Procedures - System Upgrade 5.3. 8000 UPGRADE ____ _______ 5.3.1. Introduction ____________ Since 8.4E contains new file formats and a new file system, conversion of files is required to make files compatible with the new file system. The file conversion can be done in two ways: SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg099 A) From tape to disk B) From disk to disk Which method is used depends on the configuration of the system. The disk to disk method is preferable for a system with removable disks. The disk to disk method involves upgrading the system disk with the new O.S.. Then the system disk can be used to convert other disks by using the NFSCONVERT utility to convert one file from one disk to another. This also moves the data from one disk to another. If this method is used on fixed disks, the files may not reside on the family intended unless copied back later. This should be considered when using the disk to disk conversion. The tape conversion uses the utility SAVERESTORE. The conversion process is invisible to the user with the exception of a status message that may be displayed during conversion. All one needs to do to convert is use SAVERESTORE in a normal manner. The tape conversion requires about 4 minutes per megabyte of data. The installation procedure is broken into two parts: A) Preliminary evaluation B) Operating System upgrade and file conversion The preliminary evaluation is required to ensure that proper hardware and file preparation is done. An O.S. upgrade from releases of 8.4D and below entails loading of the 8.4E system and converting files to their new format. The conversion process, in large configurations, will take more than one day. At the end of this section is an upgrade and conversion checklist that should be used to track progress through the upgrade procedure. Installation Procedures - System Upgrade 5.3.2. Preliminary Evaluation ___________ __________ The preliminary section deals with revision levels and file preparation. 5.3.2.1. Hardware Evaluation ________ __________ All hardware must be checked for proper operation. All boards must be at proper revision levels. Ensure that all tape units are operating correctly. Also, make sure that all memory boards are set for 160 ns operation. Also note that any 3 CE systems must have a revision K or higher on the IMLC board (if present). 5.3.2.2. File Preparation ____ ___________ Obtain a directory listing with partial attributes for each family in the system. This listing will help you to find SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg100 files, if any, that need repair before conversion. Next, using DISKANALYZER, validate all files in the system. Now determine which files need repair. Files which have the following attributes MUST be repaired before they are saved to tape: A) Files which lack integrity. B) Files which have lost space. C) Non-serial files in which records used is greater than records defined. D) Files that have invalid format. These files can be located in several ways: A) Scan the directory listing noting any files flagged. B) Use the report generated by DISKANALYZER as a guide. C) Use the utility FINDLOSTSPACE (8.4C/D only). All of the above methods should be used to find files that lack integrity and that have lost space. However, the directory listing must be scanned to find files that have a greater number of records used then defined as maximum records. This is a very important step. Any file possessing any of these attributes WILL NOT convert properly. They have to be repaired on a previous release before conversion. Any EDITOR recovery files must be recovered or deleted before Installation Procedures - System Upgrade conversion. The recovery files are identified by the node ED.REC.. After the node, there will be a series of digits. These files can be found by scanning the directory listing. These files must be recovered by using EDIT.RECOVER or deleted by using the DELETE utility. ***************************************** * * * ALL FILES MUST BE FREE FROM LACK OF * * INTEGRITY, LOST SPACE, AND MAX * * RECORDS GREATER THAN DEFINED RECORDS. * * FILES WILL NOT BE CONVERTED IF THEY * * POSSESS ANY ONE OF THESE ATTRIBUTES * * * ***************************************** 5.3.2.3. 8.4E Space Requirements ____ _____ ____________ The space required for files under the new file system are about the same as under 8.4D/C/B/A levels. However, it is recommended that a listing be obtained which displays the files and their new sizes. On the 8.4D release, the program FILESIZE is used to produce this listing. The program FILESIZE will display the new file size under the 8.4E system SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg101 for each file in a given family. It will also display the total number of sectors required by the entire family under the new file system. Please see section 3.3.4 for FILESIZE usage. 5.3.2.4. Saving Files to Tape ______ _____ __ ____ Files must now be backed up to tape. If you are using disk to disk conversion, it is STRONGLY recommended that all files be saved to tape. This will allow recovery of files in case of problems with the disk to disk conversion. The files are saved using the standard tape utility, SAVERESTORE. When saving files to tape, send the output from the save process to the printer. These will provide a record of backup for each file. Also it is recommended that all tapes be compared to the files on the disk. When using the tape or disk conversion, the conversion requires temporary disk space to sort keyed (direct and sort) files. The space required varies with the number of records and the size of the key. To insure proper space is available, the following steps should be observed: A) Do not restore the user default family until last. B) Convert large keyed files first. Installation Procedures - System Upgrade Step A insures that the default user disk has a large amount of free space since this is where the tape and disk conversion utility defines the temporary files. Step B allows the files that require the most amount of temporary space to be converted first. To convert large keyed files first, they must be saved to tape first. The large keyed files can be identified by scanning the directory listing obtained in section 5.3.2.2. If using disk to disk conversion, the NFSCONVERT utility allows you to convert keyed files first (section 3.3.7). 5.3.3. Operating System Update and File Conversion _________ ______ ______ ___ ____ __________ The loading of 8.4E is done the same as any other BOSS/VS release. However, there are some extra steps that are required to bring the disks into proper format. 5.3.3.1. Installing the O.S. __________ ___ ____ 5.3.3.1.1. ALT LOAD ___ ____ A) Insert the new release tape into the tape drive. B) Press the "ALTLOAD" button on the front panel. C) Enter the appropriate system disk (0 or 1) or if SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg102 drives 0 and 1 are both system disks, enter "2" to update both disks. D) Enter a "0" to update WCS slot 0. E) Enter a "Y" to the prompt "Are you SURE you want to overwrite this WCS ? (Y/)". The system automatically updates the OS and WCS slot 0 on both disks, if selected. When this is complete, the system prompts "DONE - READY FOR NORMAL LOAD". Reload by pressing the LOAD button. 5.3.3.1.2. ENTER A TYPE 3 LOAD (SPECIAL FUNCTIONS) _____ _ ____ _ ____ ________ __________ This step is VERY important. Options 1-4 MUST be done for a 8.4E disk to be used on the system. These options MUST NOT be done for any disk that has not been converted from pre-8.4E. If a tape conversion is being done, then initialize all disks at this time. If a disk to disk conversion is being done, then just initialize one scratch (8.4E) pack that the converted files are going to reside on. In both cases the system disk(s) must be initialized. Installation Procedures - System Upgrade 5.3.3.1.2.1. Option 1, CHANGE VOLUME INFORMATION ______ __ ______ ______ ___________ SYSTEM DISKS: (displayed) DRIVE NUMBER:__________ Enter the disk to update. SERIAL NUMBER:_________ Enter CR to accept current serial number. DISK CONFIGURATION (1=SYSTEM, 2=DATA, 3=BACKUP):____ Enter the appropriate disk type. SIZE OF DUMP AREA....:______ Enter the size of the dump area given by the line below this prompt as the area needed for both main memory and shared memory controllers. FILE SYSTEM SPACE:______ Enter the number displayed at the bottom of the screen for this prompt. The display will appear as "CR=X" where X is the maximum space allowed. UPDATE DISK (Y/N): Enter "Y" 5.3.3.1.2.2. Option 2, CHANGE INSTALLATION PARAMETERS SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg103 ______ __ ______ ____________ __________ SYSTEM DISKS: (displayed) DRIVE NUMBER:_______ PRIMARY PREFIX ? Enter (family).R4E56.SYS. Where (family) is the family where the operating system files reside. SECONDARY PREFIX ? Enter (family).R4E56.SYS. Where (family) is the family where the alternate Installation Procedures - System Upgrade operating system files reside. DEFAULT USER FAMILY NAME ?:________ Enter default user family SECURITY (E=ENABLED, D=DISABLED):___ FILE SYSTEM WRITE THROUGH? (E=ENABLED, D=DISABLED):___ For conversion purposes, set this option to D (disabled). This will speed up the conversion process. It can be changed later if needed. WRITE THROUGH DEFAULT ON FILE CREATE (E=ENABLED, D=DISABLED):__ This parameter specifies what the default write through will be on a file created through a BASIC file create or through the CREATE utility. UPDATE DISK WITH INSTALLATION PARAMETERS? (Y/N)__ Display: PARAMETERS SUCCESSFULLY WRITTEN TO DISK 5.3.3.1.2.3. Option 3, UPDATE FAMILY INFORMATION ______ __ ______ ______ ___________ AVAILABLE DRIVES: (displayed) FAMILY BASE DRIVE NUMBER:___ DRIVE NUMBERS OF OTHER DISKS IN FAMILY? (TYPE SPACES FOR NO OTHER DRIVES): Enter all other drive numbers for this family or spaces if none. The drives must be in 8.4E format. UPDATE DISK (Y/N) ? 5.3.3.1.2.4. Option 4, INITIALIZE FAMILY DIRECTORY ______ __ __________ ______ _________ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg104 FAMILY NAME:______ Enter family name. INITIALIZE FAMILY (Y/N)?__ Option 1 must be done to all disks. Option 2 must be done to the system disk. Options 3 and 4 must be done for all families. Installation Procedures - System Upgrade Reload the system by pressing the LOAD button and enter a TYPE II load. 5.3.3.2. Restoring the O.S. _________ ___ ____ Enter SAVERESTORE in a TYPE II load and choose option #2 "RESTORE FILES FROM TAPE". The screen appears as in figure 5-2. Figure 5-2. Restore Screen ______ ____ _______ ______ -------------------------------------------------------- RESTORE FILES TAPE SET.ID: DRIVE-NUM: REEL-NUM: PRIMARY PREFIX: (FAMILY).NODE. FILETYPE (D/P/CR=ALL) COMPARE (CR=Y/N) DATE (MM/DD/YY) TIME (HH:MM) OUTPUT DEVICE (CR=VDT) DELETE EXISTING FILES (CR=Y) VERIFY (Y/CR=N) ENTRIES CORRECT (Y/N) -------------------------------------------------------- At each prompt, enter a . At the prompt, "FILE SPECIFIERS", enter ".". Enter to all other questions. All system files will be restored to disk. Please note that once all files are restored to disk, the message "AUTOMATIC COMPARE, CR TO CONTINUE" appears. This automatically rewinds the tape and begins the compare operation. This only occurs when the compare option is selected. When the compare is completed, enter a CTL-IV to return to the "SAVERESTORE" menu. Installation Procedures - System Upgrade SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg105 5.3.3.3. Conversion of Files __________ __ _____ If doing tape to disk conversion see section 5.3.3.3.1. If doing disk to disk conversion see section 5.3.3.3.2. 5.3.3.3.1. Tape to Disk Conversion ____ __ ____ __________ Mount the first tape to restore and enter Option #2. A screen as in figure 5-2 will appear. Answer all prompts as in the figure. Make sure that you direct the output to a printer. This will provide you with a "history" of the restore operation. Each file is converted to the new file format as it is restored. The conversion to the new file format will be entirely invisible except for a pause at the completion of restoring a file. This pause, which can last a few seconds to a few hours depending on file size, indicates the file is being converted to the new file format. Occasionally the message "...CONVERTING FILE TO NFS..." will appear as a visual indicator of file conversion. System files from the previous release need not be restored. However, to preserve all system parameters and configurations, the 'SYSDATA' and '.SYSTEM.CONFIG.' node must be restored from the backup tapes. Tapes made on a release prior to 8.4E cannot be compared when restored to the new file system. After all files have been restored, go to section 5.3.3.3.3. 5.3.3.3.2. Disk to Disk Conversion ____ __ ____ __________ The utility NFSCONVERT is used to convert files from the old format to the new file format. The destination disk must be in 8.4E format as described in section 5.3.3.1.2. The source disk must be in pre-8.4E format. When using disk to disk conversion, only one family may be converted per terminal. You cannot start NFSCONVERT on two terminals converting different parts of the same family. You can convert different families at the same time. As in the tape to disk conversion, the node '.SYSDATA.' and '.SYSTEM.CONFIG.' must be converted to preserve system parameters and configurations. See section 3.3.7 for operation of the NFSCONVERT utility. Installation Procedures - System Upgrade 5.3.3.3.3. Check Files _____ _____ Once all files have been converted, DISKANALYZER should be used to validate all files for each family. DISKANALYZER can be used in a TYPE II load or a TYPE I load. See the section on DISKANALYZER. Once all files have been validated, enter a TYPE I load, (if you have not already done so). Installation Procedures - Updating Slots 1, 2, and 3 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg106 5.4. UPDATING OTHER SLOTS ________ _____ _____ The slots 1, 2, and 3 need to be updated. Set the prefix to the .INST. node by keying in the following in command mode: !PREFIX .R4E56.INST. 5.4.1. Updating Slot One (1) ________ ____ ___ ___ A copy of the primary operating system will be put in slot 1. UPDATE.OS IMAGE FILE NAME: .R4E56.INST.OS1.UV040556000 OS SLOT: (displayed) OS VERSION: (displayed) IMAGE FORMAT: (displayed) NEW WCS SLOT: 1 UPDATE WHICH DISK: (0=nn/1=nn/B=BOTH/Q=QUIT)___ DONE ! UPDATE COMPLETE Next, WCS slot 1 is updated with a copy of the slot 0 WCS. UPDATE.WCS ENTER WCS SLOT [0..3]: Enter '1' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R4E56.INST.WCS.B536 WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 5.4.2. Updating WCS Slot Two (2) ________ ___ ____ ___ ___ REMIDI will reside in this slot. UPDATE.WCS ENTER WCS SLOT [0..3]: Enter '2' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE: (choose disk) WCS IMAGE FILE: .R4E56.INST.REMIDI.BV5C0101 WCS LEVEL OF WCS IMAGE FILE: (level displayed) UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETED! Installation Procedures - Updating Slots 1, 2, and 3 5.4.2.1. Updating the Load Sector for REMIDI ________ ___ ____ ______ ___ ______ Running UPDATE.OS automatically updates the Load Sectors for the disk. However, running UPDATE.WCS does not. (The Load Sectors are displayed at the top of the OSINFO screen.) It is therefore necessary to run UPDATE.LD for REMIDI on newly SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg107 initialized system packs, or whenever question marks ("?/?") appear in Load Sector 2 on the OSINFO screen. Update the Load Directory for REMIDI by using the UPDATE.LD utility: * Input in command mode !UPDATE.LD Update Load Directory Utility Disks (Unit number) on line : 0(16),1(17) Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 4.5.56.0 R 4E*56 860808 B 5.3.6 1 1/1 | 4.5.56.0 R 4E*56 860808 B 5.3.6 2 ?/? | B 5.1.1 3 3/3 | 5.3.12.17 DEMON 2/26/86 B 5.3.6 * New OS slot (0,1,3): 0 * New WCS slot (0..3): 2 * Load sector (0..3) : 2 Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 4.5.56.0 R 4E*56 860808 B 5.3.6 1 1/1 | 4.5.56.0 R 4E*56 860808 B 5.3.6 2 0/2 | B 5.1.1 3 3/3 | 5.3.12.17 DEMON 2/26/86 B 5.3.6 Notice that load sector 2 is now pointing to WCS slot 2. 5.4.3. Updating Slot Three (3) ________ ____ _____ ___ Operating system slot 3 will contain the O.S. for DEMON. UPDATE.OS IMAGE FILE NAME: .R4E56.INST.OS3.UV050312017 OS SLOT: (displayed) OS VERSION: (displayed) IMAGE FORMAT: (displayed) NEW WCS SLOT: Enter '3' UPDATE WHICH DISK (0=nn/1=nn/B=BOTH/Q=QUIT):____ UPDATING DISK DONE! UPDATE IS NOW COMPLETE Now, the WCS for DEMON is updated. Installation Procedures - Updating Slots 1, 2, and 3 UPDATE.WCS ENTER WCS SLOT [0..3]: Enter '3' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R4E56.INST.WCS.B536 WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 5.4.4. Slot Information SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg108 ____ ___________ Once all slots have been updated, use the utility OSINFO to display the slot information. The information should be simliar to figure 5-3. If disk 1 is a system disk also, repeat these steps beginning with section 5.4 Figure 5-3. Operating System Information ______ ____ _________ ______ ___________ OPERATING SYSTEM INFORMATION ------------------------------------------------------------------ BOOT LEVEL : X.X.X.X LOAD SECTOR: 0 1 2 3 DISK 0 : 0/0 1/1 0/2 3/3 SERIAL # : XXX-XXXXX ------------------------------------------------------------------ OS NAME OS LEVEL DISK:SLOT WCS LEVEL ------------------------------------------------------------------ R 4E*56 860808 4.5.56.0 0:0 B 5.3.6 R 4E*56 860808 4.5.56.0 0:1 B 5.3.6 N/A 0:2 REMIDI B 5.1.1 DEMON 2/26/86 5.3.12.17 0:3 B 5.3.6 ------------------------------------------------------------------ 5.4.5. Update Terminal Configuration File ______ ________ _____________ ____ The terminal configuration file must be updated to the new 8.4E format. This update will allow all other devices to become accessible. The file is updated by entering TERM.CONFIG and choosing the update option. Enter PRIMARY as the file to change. Enter an existing ISDC and display one of the ISDC ports. Enter a MB-IV to exit the update without changing anything. The utility will say that the file has been modified and do you want to save it. Respond with YES. Now reload the system to allow the devices to become active. Installation is now complete. 8.4E 8000 UPGRADE AND CONVERSION CHECKLIST ____ ____ _______ ___ __________ _________ 1) Hardware levels => section 4 2) Validate files => section 5.3.2.2 A) DIR listings B) FINDLOSTSPACE Utility C) Delete unwanted EDITOR,SPOOL, and TEMP files 3) New file sizes => section 5.3.2.3 A) FILESIZE utility 4) Save files to tape => section 5.3.2.4 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg109 A) Large keyed files first 5) Update operating system => section 5.3.3.1 A) ALT-LOAD B) Options 1-4 C) Restore operating system files 6) File conversion A) Tape-to-disk => section 5.3.3.3.1 B) Disk-to-disk => section 5.3.3.3.2 7) Check file integrity => section 5.3.3.3.3 8) Complete installation A) Update slots => section 5.4 B) Update terminal configuration file => section 5.4.5 6. RELATED DOCUMENTATION _______ _____________ 2770/2780/3770/3780 Batch Emulator User Guide M 5080C 3270 Pass-Through Reference Manual M 5091A BOSS/VS Business BASIC Reference Manual M 5092C BOSS/VS User Guide M 5098E BOSS/VS Utilities User Guide M 5102D 3270 Emulation Package Operator Guide for MAI 8000 Series M 5129 MAI 8000 Terminal Asynchronous Communication Facility Reference Manual M 5130A File Transfer Facility User Reference Manual M 6352 BOSS/VS Installation Guide M 5138C MPx System Installation Planning Guide M 5146E BOSS/VS Special Purpose Utilities User Guide M 5151 BOSS/VS System Support Manual M 5152 Intersystem Transport Package User Guide M 6354D MAI 8000 Series COBOL Reference Manual M 5174 MAI 8000 Series COBOL User Guide M 5175 BOSS/VS File Conversion User Guide M 5185A SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg110 Note: BOSS/VS User Guide (M 5098E) includes the MAI 8000 Series Operator Guide. BOSS/VS Utilities User Guide (M 5102D) includes the BOSS/VS System Management Utilities User Guide. INDEX _____ NFSCONVERT DELEXIST: 73 NFSCONVERT Destination: 72 NFSCONVERT End Specifier: 72 NFSCONVERT ENTRIES CORRECT: 76 NFSCONVERT OUTPUT DEVICE: 75 NFSCONVERT PAUSE ON ERRORS: 74 NFSCONVERT Primary Prefix: 70 NFSCONVERT Start Specifier: 71 NFSCONVERT TYPE: 74 NFSCONVERT VERIFY: 73 NFSDir END SPECIFIER: 62 NFSDir START SPECIFIER: 61 OldDir ENTRIES CORRECT: 64 OldDir FILE TYPE: 63 OldDir OUTPUT DEVICE: 63 OldDir TYPE: 66 ORIGINATOR: MBF SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB029 Pg111 FIB 00030 10/01/87 *** Release 8.5D/9.5D Software Announcement *** 8.5D/9.5D Software Announcement MAI Basic Four, Inc. is pleased to announce that the new software releases, 8.5D and 9.5D, are now available. The 8.5D release is the required release for MPx 7000 and 8000 Series Systems on 8.5. The 9.5D release is the required release for MPx 9000 and 9500 Series Systems. ************************************************** * * * PLEASE READ THE INSTALLATION INSTRUCTIONS * * BEFORE ATTEMPTING INSTALLATION OR UPGRADE. * * * * A NEW CONFIGURATION RECORD IS NOT REQUIRED * * WHEN UPGRADING TO 8.5D FROM LEVEL 8.5B AND * * ABOVE. A NEW CONFIGURATION RECORD IS REQUIRED * * WHEN UPGRADING TO 8.5D FROM LEVELS BELOW 8.5B. * * * * A NEW CONFIGURATION RECORD IS NOT REQUIRED * * WHEN UPGRADING TO 9.5D FROM 9.5C. A NEW CONFIG-* * URATION RECORD IS REQUIRED WHEN UPGRADING TO A * * MPX 9000 OR 9500 FROM AN MPX 8000. * * * * IT IS REQUIRED THAT 8000 SYSTEMS BEING * * UPGRADED TO 9.5D RUN ON RELEASE 8.4E OR AN 8.5 * * RELEASE FOR A MINIMUM OF ONE WEEK PRIOR TO * * UPGRADE. IT IS RECOMMENDED THAT 8000 SYSTEMS * * BEING UPGRADED TO 9.5D RUN ON 8.5D PRIOR TO * * UPGRADE. 9.5C SYSTEMS SHOULD UPGRADE DIRECTLY * * TO 9.5D. * * * * A PRESITE SURVEY IS REQUIRED BEFORE UPGRADING * * TO A 9000 OR 9500. (SEE FIELD BULLETIN #161A.) * * * * WHEN UPGRADING TO 8.5D/9.5D FROM RELEASES * * PRIOR TO 8.5C/9.5C, AN ALT LOAD MUST BE DONE * * BEFORE THE O.S. FILES ARE RESTORED. THIS IS * * BECAUSE CERTAIN FILES WILL NOT RESTORE * * (INCLUDING THE DRIVERS FOR THE ISDC * * CONTROLLERS) WHEN ON RELEASES PRIOR TO * * 8.5C/9.5C. * * * * AS OF THIS RELEASE, THE "INSTALL.CONFIG" * * UTILITY NO LONGER EXISTS. IT HAS BEEN REPLACED * * BY THE "CONFIG.MGR" UTILITY. * * * ************************************************** Copyright 1986 by MAI Basic Four, Inc. All rights reserved. C O N T E N T S _ _ _ _ _ _ _ _ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg001 1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . 2 2 HISTORY . . . . . . . . . . . . . . . . . . . . . . . . 3 3 BOSS/VS . . . . . . . . . . . . . . . . . . . . . . . . 5 3.1 CONFIGURATIONS . . . . . . . . . . . . . . . . . . . . 5 3.1.1 Configurations for MPx 7000 and 8000 Series Systems 5 3.1.2 Configurations for MPx 9000 and 9500 Series Systems 6 3.1.2.1 Configurations for MPx 9000 Series Systems . . . . 6 3.1.2.2 Configurations for MPx 9500 Series Systems . . . . 7 3.2 UTILITIES . . . . . . . . . . . . . . . . . . . . . . 8 3.2.1 CONFIGURATION MANAGER UTILITY . . . . . . . . . . . 8 3.2.1.1 Introduction . . . . . . . . . . . . . . . . . . . 8 3.2.1.2 Using the CONFIGURATION MANAGER . . . . . . . . . 8 3.2.1.2.1 The Installation Process . . . . . . . . . . . . 9 3.2.1.2.2 The Display Process . . . . . . . . . . . . . . 13 3.2.1.3 Possible Errors . . . . . . . . . . . . . . . . . 16 3.2.2 DISKANALYZER Utility . . . . . . . . . . . . . . . . 16 3.2.2.1 Reconstruction of Serial Files . . . . . . . . . . 16 3.2.3 FILESIZE Utility . . . . . . . . . . . . . . . . . . 17 3.2.3.1 Introduction . . . . . . . . . . . . . . . . . . . 17 3.2.3.2 Description of the Program . . . . . . . . . . . . 18 3.2.3.2.1 Main Screen . . . . . . . . . . . . . . . . . . 18 3.2.3.2.2 Field Descriptions . . . . . . . . . . . . . . . 18 3.2.3.3 Examples . . . . . . . . . . . . . . . . . . . . . 23 3.2.3.3.1 Node Space Calculation . . . . . . . . . . . . . 23 3.2.3.3.2 Single File Space Calculation . . . . . . . . . 24 3.2.3.3.3 Non-Existing File Space Calculation . . . . . . 24 3.2.4 NFSCONVERT Utility . . . . . . . . . . . . . . . . . 25 3.2.4.1 Introduction . . . . . . . . . . . . . . . . . . . 25 3.2.4.2 Workspace Required for Keyed Files . . . . . . . . 25 3.2.4.3 Procedures for Using Utility . . . . . . . . . . . 26 3.2.4.3.1 By Command with Parameters . . . . . . . . . . . 26 3.2.4.3.2 By Menu or Command without Parameters . . . . . 28 3.2.4.3.2.1 Field Descriptions . . . . . . . . . . . . . . 28 3.2.4.4 Functions Performed . . . . . . . . . . . . . . . 34 3.3 GENERAL INFORMATION . . . . . . . . . . . . . . . . . 39 3.3.1 Software Announcement . . . . . . . . . . . . . . . 39 3.4 DIAGNOSTICS . . . . . . . . . . . . . . . . . . . . . 40 3.4.1 REMIDI . . . . . . . . . . . . . . . . . . . . . . . 40 3.4.1.1 REMIDI for MPx 7000 and 8000 Series Systems . . . 40 3.4.1.1.1 Using REMIDI on 7000 Series Systems . . . . . . 40 3.4.1.2 REMIDI for MPx 9000 and 9500 Series Systems . . . 42 3.4.1.2.1 Changing the Load Sector for Slot Three . . . . 42 4 HARDWARE . . . . . . . . . . . . . . . . . . . . . . . . 43 4.1 LARLS FOR PCBAS FOR MPX 7000 AND 8000 SERIES SYSTEMS . 43 4.2 LARLS FOR PCBAS FOR MPX 9000 AND 9500 SERIES SYSTEMS . 43 4.3 PARALLEL DMP DEVICE VARIANCE CONFIGURATION . . . . . . 44 4.3.1 MPx 7000 and 8000 Series Systems . . . . . . . . . . 44 4.3.2 MPx 9000 and 9500 Series Systems . . . . . . . . . . 44 5 INSTALLATION . . . . . . . . . . . . . . . . . . . . . . 46 5.1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . 46 5.2 NEW INSTALLATION . . . . . . . . . . . . . . . . . . . 46 5.2.1 Installing the O.S. . . . . . . . . . . . . . . . . 46 5.2.1.1 ALT LOAD . . . . . . . . . . . . . . . . . . . . . 46 5.2.1.2 ENTER A TYPE 3 LOAD (SPECIAL FUNCTIONS) . . . . . 46 5.2.1.2.1 OPTION 1 (CHANGE VOLUME INFORMATION) . . . . . . 47 5.2.1.2.2 OPTION 2 (CHANGE INSTALLATION PARAMETERS) . . . 47 5.2.1.2.3 OPTION 3 (UPDATE FAMILY INFORMATION) . . . . . . 48 5.2.1.2.4 OPTION 4 (INITIALIZE FAMILY DIRECTORY) . . . . . 48 5.2.1.3 Restoring the O.S. . . . . . . . . . . . . . . . . 49 5.2.2 UPDATING OTHER O.S. SLOTS . . . . . . . . . . . . . 50 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg002 5.2.2.1 UPDATING SLOT ONE (1) . . . . . . . . . . . . . . 50 5.2.2.2 UPDATING WCS SLOT TWO (2) . . . . . . . . . . . . 50 5.2.2.3 UPDATING SLOT THREE (3) . . . . . . . . . . . . . 51 5.2.2.3.1 Updating O.S. Slot Three . . . . . . . . . . . . 51 5.2.2.3.2 Updating WCS Slot Three (3) . . . . . . . . . . 51 5.2.2.3.2.1 WCS Slot Three on 7000 Series Systems . . . . 51 5.2.2.3.2.2 WCS Slot Three on 8000 Series Systems . . . . 52 5.2.2.4 SLOT INFORMATION . . . . . . . . . . . . . . . . . 52 5.3 8000 UPGRADE FROM RELEASE LEVELS OF 8.4D AND BELOW . . 54 5.3.1 Introduction . . . . . . . . . . . . . . . . . . . . 54 5.3.2 Preliminary Evaluation . . . . . . . . . . . . . . . 55 5.3.2.1 Hardware Evaluation . . . . . . . . . . . . . . . 55 5.3.2.2 File Preparation . . . . . . . . . . . . . . . . . 55 5.3.2.3 8.5D Space Requirements . . . . . . . . . . . . . 56 5.3.2.4 Saving Files to Tape . . . . . . . . . . . . . . . 56 5.3.3 Operating System Update and File Conversion . . . . 57 5.3.3.1 Installing the O.S. . . . . . . . . . . . . . . . 57 5.3.3.1.1 ALT LOAD . . . . . . . . . . . . . . . . . . . . 57 5.3.3.1.2 ENTER A TYPE 3 LOAD (SPECIAL FUNCTIONS) . . . . 58 5.3.3.1.2.1 OPTION 1 (CHANGE VOLUME INFORMATION) . . . . . 58 5.3.3.1.2.2 OPTION 2 (CHANGE INSTALLATION PARAMETERS) . . 58 5.3.3.1.2.3 OPTION 3 (UPDATE FAMILY INFORMATION) . . . . . 59 5.3.3.1.2.4 OPTION 4 (INITIALIZE FAMILY DIRECTORY) . . . . 60 5.3.3.2 Restoring the O.S. . . . . . . . . . . . . . . . . 60 5.3.3.3 Installing the Configuration Record . . . . . . . 61 5.3.3.4 Conversion of Files . . . . . . . . . . . . . . . 61 5.3.3.4.1 Tape to Disk Conversion . . . . . . . . . . . . 62 5.3.3.4.2 Disk to Disk Conversion . . . . . . . . . . . . 62 5.3.3.4.3 Check Files . . . . . . . . . . . . . . . . . . 62 5.3.4 UPDATING OTHER O.S. SLOTS . . . . . . . . . . . . . 63 5.3.4.1 UPDATING SLOT ONE (1) . . . . . . . . . . . . . . 63 5.3.4.2 UPDATING WCS SLOT TWO (2) . . . . . . . . . . . . 63 5.3.4.3 UPDATING SLOT THREE (3) . . . . . . . . . . . . . 64 5.3.4.3.1 Updating O.S. Slot Three . . . . . . . . . . . . 64 5.3.4.3.2 Updating WCS Slot Three (3) . . . . . . . . . . 64 5.3.4.3.2.1 WCS Slot Three on 7000 Series Systems . . . . 64 5.3.4.3.2.2 WCS Slot Three on 8000 Series Systems . . . . 65 5.3.4.4 SLOT INFORMATION . . . . . . . . . . . . . . . . . 65 5.3.5 Update Terminal Configuration File . . . . . . . . . 65 5.4 8000 UPGRADE FROM RELEASE LEVELS ABOVE 8.4D . . . . . 68 5.4.1 Saving Files to Tape . . . . . . . . . . . . . . . . 68 5.4.2 Operating System Update . . . . . . . . . . . . . . 68 5.4.2.1 Installing the O.S. . . . . . . . . . . . . . . . 68 5.4.2.1.1 ALT LOAD . . . . . . . . . . . . . . . . . . . . 68 5.4.2.1.2 CHANGE INSTALLATION PARAMETERS . . . . . . . . . 68 5.4.2.2 Restoring the O.S. . . . . . . . . . . . . . . . . 69 5.4.2.3 Installing the Configuration Record . . . . . . . 70 5.4.3 UPDATING OTHER O.S. SLOTS . . . . . . . . . . . . . 71 5.4.3.1 UPDATING SLOT ONE (1) . . . . . . . . . . . . . . 71 5.4.3.2 UPDATING WCS SLOT TWO (2) . . . . . . . . . . . . 72 5.4.3.3 UPDATING SLOT THREE (3) . . . . . . . . . . . . . 72 5.4.3.3.1 Updating O.S. Slot Three . . . . . . . . . . . . 72 5.4.3.3.2 Updating WCS Slot Three (3) . . . . . . . . . . 73 5.4.3.3.2.1 WCS Slot Three on 7000 Series Systems . . . . 73 5.4.3.3.2.2 WCS Slot Three on 8000 Series Systems . . . . 73 5.4.3.4 SLOT INFORMATION . . . . . . . . . . . . . . . . . 73 5.5 UPGRADING TO 9.5D AND THE MPX 9000 AND 9500 SERIES . . 75 5.5.1 SPECIAL CONSIDERATIONS . . . . . . . . . . . . . . . 75 5.5.2 PRINTING OUT THE TERMINAL CONFIGURATION RECORD . . . 75 5.5.3 SAVING FILES TO TAPE . . . . . . . . . . . . . . . . 75 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg003 5.5.4 OPERATING SYSTEM UPDATE . . . . . . . . . . . . . . 76 5.5.4.1 ALT LOAD . . . . . . . . . . . . . . . . . . . . . 76 5.5.4.2 TYPE 3 LOAD (SPECIAL FUNCTIONS) . . . . . . . . . 76 5.5.4.2.1 Updating Installation Parameters . . . . . . . . 76 5.5.4.2.2 Sizing the Dump Area (Change Volume Information) 77 5.5.4.3 Restoring the O.S. Files . . . . . . . . . . . . . 78 5.5.4.4 Installing the Configuration Record . . . . . . . 79 5.5.5 UPDATING OTHER O.S. SLOTS . . . . . . . . . . . . . 80 5.5.5.1 Updating Slot One (1) . . . . . . . . . . . . . . 80 5.5.5.2 Updating WCS Slot Two (2) . . . . . . . . . . . . 81 5.5.5.3 Updating Slot Three (3) . . . . . . . . . . . . . 81 5.5.5.3.1 Updating O.S. Slot Three (3) . . . . . . . . . . 81 5.5.5.3.2 Changing the Load Sector for Slot Three (3) . . 82 5.5.5.3.3 Updating WCS Slot Three (3) . . . . . . . . . . 82 5.5.5.4 Slot Information . . . . . . . . . . . . . . . . . 82 6 RELATED DOCUMENTATION . . . . . . . . . . . . . . . . . 84 INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 T A B L E S and F I G U R E S _ _ _ _ _ _ ___ _ _ _ _ _ _ _ Figure 3-1. Options Available for Mpx Systems . . . . . . 9 Figure 3-2. Install System Configuration, Screen 1 . . . . 11 Figure 3-3. Install System Configuration, Screen 2 . . . . 12 Figure 3-4. Chargeable Software Options . . . . . . . . . 12 Figure 3-5. Display System Configuration, Screen 1 . . . . 13 Figure 3-6. Display System Configuration, Screen 2 . . . . 14 Table 3-1. Possible Errors for the USER SSN field . . . . 16 Figure 3-7. File Space Calculation Screen . . . . . . . . 18 Table 3-2. Possible Errors for NODE OR FILE NAME Field . . 19 Table 3-3. Possible Errors for RECORDS DECLARED Field . . 20 Table 3-4. Possible Errors for ACTUAL RECORDS Field . . . 21 Table 3-5. Possible Errors for RECORD SIZE Field . . . . . 21 Table 3-6. Possible Errors for KEY SIZE Field . . . . . . 22 Table 3-7. Possible Errors for OUTPUT DEVICE Field . . . . 22 Figure 3-8. Sample Output, Node Space Calculation . . . . 23 Table 3-8. Parameters for NFSCONVERT . . . . . . . . . . . 27 Figure 3-9. NFSCONVERT Data Entry Screen . . . . . . . . . 28 Table 3-9. Possible Errors for Start Specifier, not Point- 30 Table 3-10. Possible Errors for Destination Field . . . . 31 Table 3-11. Possible Errors for OUTPUT DEVICE Field . . . 34 Figure 3-10. NFSCONVERT Display on the VDT . . . . . . . . 35 Figure 3-11. NFSCONVERT Output to a Printer or File . . . 37 Figure 3-12. NFSCONVERT Display with Parameters . . . . . 38 Figure 5-1. Restore Screen . . . . . . . . . . . . . . . . 49 Figure 5-2. Operating System Information . . . . . . . . . 53 Figure 5-3. Restore Screen . . . . . . . . . . . . . . . . 60 Figure 5-4. Operating System Information . . . . . . . . . 66 Figure 5-5. Restore Screen . . . . . . . . . . . . . . . . 70 Figure 5-6. Operating System Information . . . . . . . . . 74 Figure 5-7. Restore Screen . . . . . . . . . . . . . . . . 79 Figure 5-8. Operating System Information . . . . . . . . . 83 1. INTRODUCTION ____________ The following enhancements are contained in the 8.5D/9.5D releases: o A new CONFIGURATION MANAGER utility. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg004 o Four spooler fixes. o DISKANALYZER reconstruction of serial files. o Support for the faster 8-inch fixed disk. (Support for this product actually began in 8.5C/9.5C) o Manual selection of different print modes on DMP printers. o An optional enhanced ATP package now available at nominal cost. As of the 8.5D/9.5D releases, the INSTALL.CONFIG utility has been replaced by the CONFIG.MGR utility. A new configuration record is not required when upgrading to 8.5D from level 8.5B and above, but one is required for upgrades from software levels below 8.5B. A new configuration record is not required when upgrading to 9.5D from level 9.5C, but one is required when upgrading to MPx 9000 or 9500 Series Systems from MPx 8000 Series Systems. A presite survey is required before upgrading to the MPx 9000 or 9500. (See Field Bulletin 161A). Sections documented in this 8.5D/9.5D announcement supersede those sections in previous announcements. Installation and upgrade procedures are fully documented in this announcement. Copyright 1986 by MAI Basic Four, Inc. All rights reserved. 2. HISTORY _______ Release Current Status Description _______ _______ ______ ___________ 8.5A Obsolete Enhancements include: Increased file system concurrency for greater throughput, support for 7000 series systems, proportional growth for DIRECT and SORT files, maximum number of open files increased to 512, maximum number of tasks sharing same file increased to 512, file selectable write-through, DISKANALYZER also available in stand-alone mode, DISKANALYZER reconstruct of directory and available space files, maximum number of system printers increased to 99, system dumps written directly to tape, system support for the DMP serial printer, new terminal services error utility, DataWord printer queue enhancements, enhanced SAVERESTORE utility. 8.5B Obsolete In this release the system model number has been included in the configuration record, the COMPARE utility has been fixed so that it completely compares BASIC program files, and a new TBC AUTODIAL feature allows for definition and retrieval of multiple station lists. 8.5C/ Obsolete Enhancements include: Expanded ERRORLOG 9.5C reporting; Optimization of DataWord files; Number of logical channels increased to 64; Support for 8 bit character sets; DISKANALYZER reporting of required disk space for recon- SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg005 struction. Mpx 9000 and 9500 systems only: 32 bit CPU; increased main memory; number of maximum devices increased to 164; new DMA controller for increased performance; enhanced CPU processing for faster arithmetic and logical operations; RSTACK cache; overall performance increase which is 2-3 times that of 7000/8000 systems. Mpx 9500 only: DATA and CODE caches for additional increased perfor- mance. Release Current Status Description _______ _______ ______ ___________ 8.1A Obsolete Introduction of the System 810 hardware and BOSS/VS software. 8.1B Obsolete Enhanced features include: 31 logical units in BASIC, increase in file system cache from 208 to 225 unique files, MULTIREELSR, family image backups, SAVERESTORE backup files having the Lack-of-Integrity bit set. Bugs were fixed in DISKANALYZER, SAVERESTORE and many of the system dumps. 8.2A Obsolete This release contained significant enhancements providing NO EXTEND BASIC, 68 serial devices, math functions, X.25 Communications, DataWord 3.0. File System write through and BULLETIN board availability. 8.2B Obsolete This release contained all of the above features but was required for the 8000 Series systems due to a change in the WCS image for that hardware. 8.2C Obsolete This release contained a WCS fix to support rezero fault clear, disk error recovery and a fix to the IMLC. 8.4A Obsolete This release contained significant enhancements including 6 megabytes of main system memory, 96 devices, 84 total serial devices, disk to disk sequential family backup, enhanced hardware error log, system load progress monitor, and fast reconstruct utility. 8.4B Obsolete Enhanced features include: 8 megabytes of main system memory, 16-port Asynchronous Controller, point-to-point file specification, QUIET mode for utilities, BASIC statement numbers up to 16000, Buffered Magnetic Tape Controller (BMTC) 1/4" tape support, S/10 Industry Standard Printer as slave printer. 8.4C Obsolete Enhanced features included: Buffered Magnetic Tape Controller, 1/2" tape support, DEDICATE with expanded error reporting, new ISDC OS for 4-way, 8-way and 16-way, FILESIZE utility. 8.4D Acceptable Contained fixes for BASIC PRECISION, 810/8000 Only EXTTAPE, COBOL, and FILESIZE. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg006 3. BOSS/VS _______ 3.1. CONFIGURATIONS ______________ NOTE 1: Systems on software release levels 8.5 and 9.5 will require an extra 1/4 MB of memory for File System data structures, increasing the amount of memory required for system overhead from 1/2 MB on 8.4D to 3/4 MB on 8.5 and 9.5. NOTE 2: The number of "High Activity Tasks" is approximate and largely dependent on the application. The relative relationship of the numbers between configurations is more important than the actual numbers themselves. 3.1.1. Configurations for MPx 7000 and 8000 Series Systems ______________ ___ ___ ____ ___ ____ ______ _______ The maximum configuration for the MPx 8000 Series Systems, Model 8030, is as follows: 116 Devices - A combination of 8-ways, 16-ways, the 4 ports on the MCS PCBA, MDTs and HVDTs up to a total of 116 devices are supported. 3 CPU sets 10 ISDCs: 16-ways (7 maximum) and/or 8-ways 32 Ghost tasks 24 High speed videos (HVDT) 8 Disk drives 4 Parallel printers 8 Megabytes of memory 2 Magnetic tape drives (MTR, MTS and/or MCS) 2 Intelligent Multi-Line Controllers (IMLC) 8 DataWord II terminals 4 TBC lines 64 3270 terminals 8 X.25 lines 2 Auto-Call Units (ACU) 99 Serial printers 99 System printers (spooler) 2 Buffered Magnetic Tape Controllers 27 High activity concurrent tasks Note: There is a maximum of 9 memory assembly boards in any combination of 1/2 Mb, 1 Mb, 2 Mb, 4 Mb and BMTCs (a maximum of 3 boards per chassis). Models 7010/8010 and 7020/8020 have the same configuration limits as Model 8030 above, with the following limitations: 7010/8010 7020/8020 1 CPU set 2 CPU sets 2-4 Mb memory 2-6 Mb memory 20 Devices 52 Devices 12 Concurrent tasks 20 Concurrent tasks SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg007 (high activity) (high activity) 19 System printers 51 System printers 3.1.2. Configurations for MPx 9000 and 9500 Series Systems ______________ ___ ___ ____ ___ ____ ______ _______ 3.1.2.1. Configurations for MPx 9000 Series Systems ______________ ___ ___ ____ ______ _______ The maximum configuration for MPx 9000 Series Systems, Model 9020, is as follows: 116 Devices - A combination of 8-ways, 16-ways, the 4 ports on the MCS PCBA, MDTs and HVDTs up to a total of 116 devices are supported. 2 CPU sets with Evaluation Stack and Rstack Cache 10 ISDCs: 16-ways (6 maximum) and/or 8-ways (10 maximum) 32 Ghost tasks 24 High speed videos (HVDT) 12 8-inch fixed or 8 14-inch disk drives 8 Parallel printers 12 Megabytes of memory 2 Magnetic tape drives including MTR, MTS and/or MCS (1 maximum) 2 Intelligent Multi-Line Controllers (IMLC) 8 Dataword II terminals 4 TBC lines 64 3270 terminals 8 X.25 lines 2 Auto-Call Units (ACU) 99 Serial printers 99 System printers (spooler) 4 DMA controllers 2 Buffered Magnetic Tape Controllers 43 High activity concurrent tasks Model 9010 has the same configuration limits as the 9020 above, with the following exceptions: 1 CPU set with Evaluation Stack and Rstack Cache 68 Devices 10 ISDCs: 16-ways (4 maximum) and/or 8-ways (8 maximum) 67 Serial printers 75 System printers 26 High activity concurrent tasks 3.1.2.2. Configurations for MPx 9500 Series Systems ______________ ___ ___ ____ ______ _______ The maximum configuration for MPx 9500 Series Systems, Model 9530, is the same as the maximum configuration for the MPx 9000 Series Systems, Model 9020, with the following exceptions: 3 CPU sets with Evaluation Stack Rstack Cache Code Cache Data Cache 164 Devices SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg008 10 ISDCs: 16-ways (10 maximum) and/or 8-ways (10 maximum) 16 8-inch fixed or 8 14-inch disk drives 73 High activity concurrent tasks Models 9510 and 9520 have the same configuration limits as Model 9530 with the following exceptions: 9510 9520 1 CPU set 2 CPU sets (same caches as the 9530) (same caches as the 9530) 10 ISDCs: 16-way (4 maximum) 10 ISDCs: 16-way (6 maximum) 8-way (8 maximum) 8-way (10 maximum) 84 Devices 132 Devices 83 Serial printers 53 Concurrent tasks 91 System printers (high activity) 32 Concurrent tasks (high activity) 3.2. UTILITIES _________ 3.2.1. CONFIGURATION MANAGER UTILITY _____________ _______ _______ 3.2.1.1. Introduction ____________ This section describes the CONFIGURATION MANAGER utility for MPx Series Systems. This utility replaces the INSTALL.CONFIG utility for releases levels 8.5D/9.5D and above. The CONFIGURATION MANAGER utility allows the user to install or display the fields of a system configuration record. The configuration record contains information describing the system hardware configuration. 3.2.1.2. Using the CONFIGURATION MANAGER _____ ___ _____________ _______ The CONFIGURATION MANAGER utility can be run by simply keying the command 'CONFIG.MGR' in console mode. It cannot be run as a command with parameters. Help for the CONFIGURATION MANAGER utility can be displayed to the console with the following command : CFGMGR.HELP [] The printer name is optional. If it is specified, then the help screens will be sent to the printer; otherwise, the screens will be displayed at the console and the user is prompted at the end of each page with the prompt, 'CR' TO CONTINUE. The CONFIGURATION MANAGER utility will display a menu-driven screen, requiring the user to select the system for which the configuration record is to be displayed or installed. After the desired system has been selected, a prompt will be displayed at the bottom of the screen showing the options available to the user. The options for MPx Series Systems SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg009 are: 'D' to Display and 'I' to Install. See Figure 3-1. CONFIG.MGR Utility Figure 3-1. Options Available for Mpx Systems ______ ____ _______ _________ ___ ___ _______ ____________________________________________________________________________ |MM/DD/YY MAI BASIC FOUR, INC. HH:MM | | CONFIGURATION MANAGER UTILITY | | | | | | OPTIONS: 1. MPx SYSTEM | | 2. 2000 SYSTEM | | 3. 3000 SYSTEM | | | | ENTER OPTION NUMBER: 1 | | 'CTL-IV' TO EXIT | | | | | | | | | | OPTIONS : 'D' to Display or 'I' to Install : XX | |__________________________________________________________________________| 3.2.1.2.1. The Installation Process ___ ____________ _______ The following is an outline of the installation process involved with the selection of an 'I' : 1. A screen such as in Figure 3-2 is displayed. 2. The GENERATOR SSN field is predisplayed in foreground. 3. The utility will prompt the user for the USER SSN field. If a '?' is entered at this field, the utility will display a set of help screens and at the end of the help screens display, the previous screen will be redisplayed and the cursor will be repositioned at the USER SSN field. 4. After the user enters a valid value, the utility will attempt to retrieve a configuration record that matches the USER SSN entered. Note that the USER SSN entered must match the system serial number (i.e. the GENERATOR SSN) for successful installation of the configuration record. 5. If a configuration record is found, then all of its fields for both the current and new configuration records will be displayed. Otherwise, only the current configuration record is displayed. CONFIG.MGR Utility 6. The utility will display the prompt, 'VIEW ISDC PORTS (Y/N) :' If 'YES' is entered at this field, then another screen will be displayed showing the distribution of the ISDC ports. 7. The user will be prompted for the 'CR' TO CONTINUE prompt SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg010 at the bottom of the first screen. Then, another screen such as in Figure 3-3 is displayed showing the rest of the fields of the configuration record. 8. The user will be prompted at the VIEW SOFTWARE OPTIONS field. If the user enters 'YES' at this field, then the utility will display another screen similar to the one in Figure 3-4. This screen will show the software options that had been specified during the generation of this configuration record. At the bottom of the screen, the user is prompted with a message, 'CR' TO CONTINUE. Entering a 'CR' will cause the previous screen to be redisplayed, with the cursor positioned at the next field. 9. The user must now enter a value for the NUMBER OF COPIES TO PRINT field. 10. After a value is entered for this field, the user will be asked if the configuration is to be installed. If 'YES' is entered at this prompt, the user will be asked to enter the disk drive number on which the configuration is to be installed. If 'NO' is specified at the INSTALL CONFIGURATION prompt, then the cursor is repositioned at the USER SSN field. 11. After the user enters a valid value for the disk drive number prompt, the utility will confirm whether the user wishes to continue the installation process. If the user enters 'YES', the installation process begins. Otherwise, the cursor is repositioned at the USER SSN field. 12. After the installation process is complete, the utility will display a message, indicating that the installation of the configuration record has been completed. The user now has the option to enter 'CR' to continue or 'MB-IV' to exit. CONFIG.MGR Utility Figure 3-2. Install System Configuration, Screen 1 ______ ____ _______ ______ ______________ ______ _ ___________________________________________________________________________ 0 MM/DD/YY MAI BASIC FOUR, INC. HH:MM | 1 MPx INSTALL CONFIGURATION | 2 | 3 GENERATOR SSN : XXXXXXXXX | 4 USER SSN : XXXXXXXXXX FOR RELEASE : XXXXX | 5 USER NAME : XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX | 6 | 7 CURRENT NEW | 8 SYSTEM TYPE : XXXXX XXXXX | 9 CPUS : XX XX | 0 MAIN MEMORY SIZE (MB UNITS) : XXXXXX XXXXXX | 1 DISK DRIVES : XXX XXX | 2 FILE SYSTEM SPACE (MB UNITS) : XXXXX XXXXX | 3 TAPE DRIVES : XXX XXX | 4 PARALLEL PRINTERS : XXX XXX | 5 BAND PRINTERS : XXX XXX | 6 MAXIMUM ISDC PORTS : XXXX XXXX | SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg011 7 | 8 | 9 | 0 | 1 | 2 | 3 'CR' TO CONTINUE : XX | ___________________________________________________________________________| CONFIG.MGR Utility Figure 3-3. Install System Configuration, Screen 2 ______ ____ _______ ______ ______________ ______ _ ___________________________________________________________________________ 0 MM/DD/YY MAI BASIC FOUR, INC. HH:MM | 1 MPx INSTALL CONFIGURATION | 2 | 3 GENERATOR SSN : XXXXXXXXX | 4 USER SSN : XXXXXXXXXX FOR RELEASE : XXXXX | 5 USER NAME : XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX | 6 | 7 CURRENT NEW | 8 TBC LINES : XXXX XXXX | 9 3270 TERMINALS : XXXX XXXX | 0 X25 LINES : XXXX XXXX | 1 FUTURE FEATURE : XXXX XXXX | 2 VIEW SOFTWARE OPTIONS : XXXXXXXXX XXXXXXXXX | 3 NUMBER OF COPIES TO PRINT : XXX | 4 | ___________________________________________________________________________| Figure 3-4. Chargeable Software Options ______ ____ __________ ________ _______ ___________________________________________________________________________ 0 MM/DD/YY MAI BASIC FOUR, INC. HH:MM | 1 MPx INSTALL CONFIGURATION | 2 SOFTWARE OPTIONS | 3 | 4 GENERATOR SSN : XXXXXXXXX | 5 USER SSN : XXXXXXXXX FOR RELEASE : XXXXX | 6 | 7 | 8 DATAWORD FEATURES : XXXXXXXXX | 9 LEGAL PACKAGE : XXXXXXXXX | 0 PASCAL PACKAGE : XXXXXXXXX | 1 COBOL PACKAGE : XXXXXXXXX | 2 FUTURE FEATURE : XXXXXXXXX | 3 FUTURE FEATURE : XXXXXXXXX | 4 FUTURE FEATURE : XXXXXXXXX | 5 FUTURE FEATURE : XXXXXXXXX | 6 | 7 | 8 | 9 | 0 ENTRIES CORRECT : XXXXXXXXX | 1 | ___________________________________________________________________________| CONFIG.MGR Utility SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg012 3.2.1.2.2. The Display Process ___ _______ _______ A procedure similar to the installation process is involved if 'D' is selected, except that only if a configuration record that matches the USER SSN entered can be found is it displayed. Furthermore, there is no current configuration displayed and no installation of the configuration is performed. Note that if a '?' is entered at the USER SSN field, the utility will display a set of help screens and at the end of the help screens display, the previous screen will be redisplayed and the cursor will be repositioned at the USER SSN field. See Figures 3-5 and 3-6 for the layouts of the screens. Figure 3-5. Display System Configuration, Screen 1 ______ ____ _______ ______ ______________ ______ _ ___________________________________________________________________________ 0 MM/DD/YY MAI BASIC FOUR, INC. HH:MM | 1 MPx DISPLAY CONFIGURATION | 2 | 3 GENERATOR SSN : XXXXXXXXX | 4 USER SSN : XXXXXXXXXX FOR RELEASE : XXXXX | 5 USER NAME : XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX | 6 | 7 SYSTEM TYPE : XXXXX | 8 CPUS : XX | 9 MAIN MEMORY SIZE (MB UNITS) : XXXXXX | 0 DISK DRIVES : XXX | 2 FILE SYSTEM SPACE (MB UNITS) : XXXXX | 3 TAPE DRIVES : XXX | 4 PARALLEL PRINTERS : XXX | 5 BAND PRINTERS : XXX | 6 MAXIMUM ISDC PORTS : XXXX | 7 | 8 | 9 | 0 | 1 | 2 | 3 'CR' TO CONTINUE : XX | ___________________________________________________________________________| CONFIG.MGR Utility Figure 3-6. Display System Configuration, Screen 2 ______ ____ _______ ______ ______________ ______ _ ___________________________________________________________________________ 0 MM/DD/YY MAI BASIC FOUR, INC. HH:MM | 1 MPx DISPLAY CONFIGURATION | 2 | 3 GENERATOR SSN : XXXXXXXXX | 4 USER SSN : XXXXXXXXXX FOR RELEASE : XXXXX | 5 USER NAME : XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX | 6 | 7 | 8 TBC LINES : XXXX | 9 3270 TERMINALS : XXXX | SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg013 0 X25 LINES : XXXX | 1 FUTURE FEATURE : XXXX | 2 VIEW SOFTWARE OPTIONS : XXXXXXXXX | 3 NUMBER OF COPIES TO PRINT : XXX | 4 | 5 | 6 | 7 | 8 | 9 | 0 | 1 | 2 | 3 'CR' TO CONTINUE : XX | ___________________________________________________________________________| The following describes the fields for the screens in Figures 3-2, 3-3, 3-5, and 3-6 : 1. GENERATOR SSN is a display only field, which shows the serial number for the system that is running this utility. 2. USER SSN is used to enter the serial number for which the configuration record is to be installed or displayed. The format for this field is aan-nnnnn, where 'a' represents an alphanumeric character and n is a number between 0 and 9, inclusive. 3. FOR RELEASE shows the release level of the configuration record that matches the User SSN entered. NOTE: When the 'I' option is selected for installation, the value displayed at this field reflects the release level for the new configuration record. If ___ a new configuration does not exist, this field remains blank. CONFIG.MGR Utility 4. USER NAME shows the system user name. NOTE: When the 'I' option is selected for installation, the value displayed at this field reflects the user name for the new configuration record. If a new ___ configuration does not exist, this field remains blank. 5. SYSTEM TYPE shows the type of system for which the configuration record has been defined. 6. CPUs shows the maximum number of CPUs defined within the configuration record. 7. MAIN MEMORY SIZE shows the maximum number of system memory bytes in MB units. 8. DISK DRIVES shows the maximum number of disk drives defined within the configuration record. 9. FILE SYSTEM SPACE shows disk space allocated for file system usage in MB units. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg014 10. TAPE DRIVES shows the maximum number of tape drives defined within the configuration record. 11. PARALLEL PRINTERS shows the maximum number of parallel printers defined within the configuration record. 12. BAND PRINTERS shows the maximum number of band printers defined within the configuration record. 13. MAXIMUM ISDC PORTS shows the total number of terminals, printers, and async devices defined within the configuration record. 14. TBC LINES shows the maximum number of TBC lines defined within the configuration record. 15. 3270 TERMINALS shows the maximum number of 3270 terminals defined within the configuration record. 16. X25 LINES shows the maximum number of X25 lines defined within the configuration record. 18. VIEW SOFTWARE OPTIONS allows the user to view software options if desired. 19. NUMBER OF COPIES TO PRINT is used to specify if a hard copy listing of the configuration is desired, and if so, the number of copies to be output. CONFIG.MGR Utility 3.2.1.3. Possible Errors ________ ______ The possible errors for the USER SSN field are shown in Table 3-1. Table 3-1. Possible Errors for the USER SSN field _____ ____ ________ ______ ___ ___ ____ ___ _____ +-----------------------------------------------------------------------+ | Error Message | Reason for Error | +-----------------------------+-----------------------------------------+ | Invalid User SSN | The user SSN entered is not in the | | | format, 'aan-nnnnn', where a is an | | | alphanumeric character and n is a digit | | | between 0 and 9. | | | | | The user SSN entered is not | The user SSN entered is for a system | | compatible with the system | other than the one currently being | | being used. | used. | | | | | The user SSN entered must | The user SSN entered does not match the | | match the system SSN during | GENERATOR SSN. | | installation of the | | | configuration record. | | +-----------------------------+-----------------------------------------+ 3.2.2. DISKANALYZER Utility ____________ _______ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg015 3.2.2.1. Reconstruction of Serial Files ______________ __ ______ _____ The following procedure should be followed for the reconstuction of Serial files through DISKANALYZER: 1) Reconstruct the file with DISKANALYZER. If no error messages are displayed, no further work is required - the file can be used as is. 2) If DISKANALYZER displays messages indicating a break in the record sequence, (error message numbers 78 and 79 stating: "SYNC ERROR AT RECORD n", where "n" is the record index of the first record beyond the break sequence), then further work is required: a) If ERROR 78 is displayed, the records that follow probably do not belong in the file, and a new record should be written at the indicated index, or the record at the previous index should be read and rewritten. This will get rid of the subsequent records that do not belong in the file. It should not be necessary to read through the file. b) If ERROR 79 is displayed, it is possible that one or more blocks of data were not recovered, but that records beyond the break were recovered successfully. In this case, it is necessary to inspect the records after the indicated break in sequence and determine if the records should be removed as in 2(a) above, or left in the file, with the knowledge that the intervening records were lost. 3) If error messages other than 78 and 79 are displayed during the reconstruction, it is advisable to examine the last few records of the reconstructed file. In many cases, the last record will be corrupt. In this case, the next to last record in the reconstructed Serial file should be read and rewritten, causing the last record to be dropped. NOTE: File Write Through affects the recoverability of Serial files. System wide Write Through is not sufficient to assure that all Serial file records are promptly written to disk. To get full Write Through, the file-specific Write Through must be set. This will have a noticeable impact on performance, but, without it, up to 8 K bytes of data may be lost. 3.2.3. FILESIZE Utility ________ _______ 3.2.3.1. Introduction ____________ This utility is also documented in previous software announcements. It is included here for easier reference when converting to the new File System. FILESIZE is a program which calculates the amount of disk space files will require on the 8.5 new file system. It works SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg016 for existing files, as well as non-existing files (where calculations are based on user-input file attributes). It may be run on an 8.4 system to estimate disk requirements for conversion to 8.5 file format. For files on a 13XX system the user will need to run *SIZE to get the estimated space the file would need on an 8.5 file format system. For existing files, a user may specify a family, node, or individual file name(s). The calculations are based on the default growth parameters of the existing file(s). For non-existing files, the user enters filetype, declared number of records, actual number of records, record size and key size (if applicable), and the program bases its calculations on default growth parameters. FILESIZE Utility The figures provided by this program should be used as estimations only, because actual disk requirements are affected by indeterminable factors such as disk fragmentation and file usage. A summary of FILESIZE's capabilities is shown below: 1. Calculates the total file space taken under one entire family or one specific node. 2. Calculates the space taken for one single file specified by the user. 3. Calculates the space taken for a non-existing file based upon the attributes provided by the user. 3.2.3.2. Description of the Program ___________ __ ___ _______ 3.2.3.2.1. Main Screen ____ ______ Figure 3-7. File Space Calculation Screen ______ ____ ____ _____ ___________ ______ FILE SPACE CALCULATION NODE OR FILE NAME: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX FILE TYPE : XXXXXXX RECORDS DECLARED : XXXXXXX ACTUAL RECORDS : XXXXXXX RECORD SIZE : XXXXX KEY SIZE : XX OUTPUT DEVICE : XXXXXXXXXXXXXXX ENTRIES CORRECT (Y/N) : XXX SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg017 3.2.3.2.2. Field Descriptions _____ ____________ The fields in the FILESIZE Data Entry Screen (figure 3-7) are as follows: 1. NODE OR FILE NAME The NODE OR FILE NAME field is the name of a node or a file. The message appears on line 22 and line 23: FILESIZE Utility ENTER NODE OR FILE NAME IF USER INTENDS TO CALCULATE ALL FILE SPACE IN A NODE OR A SPECIFIC FILE. Enter the name of a node or a file. If the name is not fully specified, e.g., .ABC. or ABC.TEXT then the default family name is added to the node or file name e.g., (DISK).ABC. or (DISK).ABC.TEXT. If the user enters a node, 'CR', 'CTL-I', or 'CTL-III' moves the cursor to the OUTPUT DEVICE field. If the user enters an existing file name, the program retrieves all required attributes of that file and displays them at the corresponding fields on the screen. The cursor finally stops at the OUTPUT DEVICE field. If the user wants to do a non-existing file space estimation, CTL-I or 'CR' will move the cursor to the FILE TYPE field and leave the NODE OR FILE NAME field blank. Table 3-2. Possible Errors for NODE OR FILE NAME Field _____ ____ ________ ______ ___ ____ __ ____ ____ _____ ----------------------------------------------------------- | ERROR MESSAGE | REASON FOR ERROR | ----------------------------------------------------------- | BAD FILE NAME | File name is invalid. | ----------------------------------------------------------- | FILE DOES NOT EXIST | File does not exist | ----------------------------------------------------------- | NODE DOES NOT EXIST | The node does not exist. | ----------------------------------------------------------- | FILE IS LOCKED | File is locked and cannot be | | | opened. | ----------------------------------------------------------- | DISK VOLUME NOT MOUNTED| File specified is not located | | | on a volume that is not mounted| ----------------------------------------------------------- | INVALID FAMILY NAME | Family name has more than 8 | | | characters. | ----------------------------------------------------------- Please note that the above error messages and all other messages specified for the FILESIZE utility, are those found on the 8.4D system. The error messages may be slightly different on an 8.5 system. 2. FILE TYPE SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg018 This field is the type of a file which can be specified by the user or retrieved from an existing user-specified file. The message appears on line 22: FILESIZE Utility ENTER FILE TYPE - INDEXED, SERIAL, DIRECT, SORT (I/SE/D/S) The user may enter the file type by typing in I/i, S/s, SE/se, or D/d, then the full name of the file type will be displayed, i.e., INDEXED, SORT, SERIAL, DIRECT. However, if the user has entered a file name at the NODE OR FILE NAME field, the program will immediately retrieve the file type attribute and display the full name on the screen. 3. RECORDS DECLARED This field is the declared number of records which is either requested by the user or retrieved from an existing user-specified file. The message appears on line 22: ENTER NO OF RECORDS DECLARED. RANGE 1..8388607 The user enters the number, or the program provides the information if the file exists. Table 3-3. Possible Errors for RECORDS DECLARED Field _____ ____ ________ ______ ___ _______ ________ _____ ---------------------------------------------------------- | ERRROR MESSAGE | REASON FOR ERROR | ---------------------------------------------------------- | Number of records | Number is not in the range. | | declared must be | | | between 1..8388607 | | ---------------------------------------------------------- 4. ACTUAL RECORDS This field is the number of records actually being used by an existing file or hypothetically 'in-use' by a non-existing file. It can be specified by the user or retrieved from the file if the user has specified the file at the NODE OR FILE NAME field. The message appears on line 22: ENTER ACTUAL NO OF RECORDS The user enters the number of records hypothetically 'in-use' by the non-existing file. If the file type is Indexed, Sort, or Direct, this number must be less than or equal to the declared number of records. FILESIZE Utility Table 3-4. Possible Errors for ACTUAL RECORDS Field _____ ____ ________ ______ ___ ______ _______ _____ ----------------------------------------------------------- SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg019 | ERROR MESSAGE | REASON FOR ERRORS | ----------------------------------------------------------- | Actual records must be | User-specified actual number | | <= declared # records | of records is not in the range | | for Indexed and Direct | | | file. | | ----------------------------------------------------------- 5. RECORD SIZE The RECORD SIZE field is the size of the record in bytes. It can be either user-specified or program-provided. The message appears on line 22: ENTER THE SIZE OF THE RECORD. RANGE 1..16384. Table 3-5. Possible Errors for RECORD SIZE Field _____ ____ ________ ______ ___ ______ ____ _____ ----------------------------------------------------------- | ERROR MESSAGE | REASON FOR ERROR | ----------------------------------------------------------- | Record size is between | Record size is not in the range| | 1..16384. | | ----------------------------------------------------------- 6. KEY SIZE This field is the size of the key in bytes. This field applies only when the user specifies an existing or a non-existing Single-keyed (Direct or Sort) file. If the file is Sequential (Serial) or Relative record (Indexed), the program will skip the KEY SIZE field and stop at the OUTPUT DEVICE field. The message appears on line 22: ENTER THE SIZE OF THE KEY. RANGE 1..56. FILESIZE Utility Table 3-6. Possible Errors for KEY SIZE Field _____ ____ ________ ______ ___ ___ ____ _____ ---------------------------------------------------------- | ERROR MESSAGE | REASON FOR ERROR | ---------------------------------------------------------- | Key size is between | Key size is not in the range. | | 1..56. | | ---------------------------------------------------------- 7. OUTPUT DEVICE This field allows the user to specify where to list the output produced by the program. The user can select VDT, T*, T0-T99, or 'CR' if he prefers the output on a terminal. He may also enter a file name. This file subsequently may be viewed or submitted to a printer. The message appears on line 22: ENTER DEVICE OR FILE NAME. 'CR' = ___ where ___ is the current default of this field. The initial default is 'VDT'. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg020 Table 3-7. Possible Errors for OUTPUT DEVICE Field _____ ____ ________ ______ ___ ______ ______ _____ ---------------------------------------------------------- | ERROR MESSAGE | REASON FOR ERROR | ---------------------------------------------------------- | BAD FILE NAME | File name is invalid. | ---------------------------------------------------------- | TERMINAL IS ALREADY | The terminal specified by the | | OPEN | user is not free. | ---------------------------------------------------------- | File already exists, do| The user-specified output file| | you want to delete it, | already exists. | | (Y/N) | | ---------------------------------------------------------- | INVALID OUTPUT DEVICE | Not a valid name of printer or| | | file, e.g. Family not mounted.| ---------------------------------------------------------- 8. ENTRIES CORRECT The last field is the ENTRIES CORRECT field. If all the entries are correct, entering a 'Y'/'y' causes the file space calculation to begin. If the user enters a 'N'/'n', the cursor will move back to the NODE OR FILE NAME field and the entry for that field is erased. FILESIZE Utility 3.2.3.3. Examples ________ 3.2.3.3.1. Node Space Calculation ____ _____ ___________ The user enters the node name, '.ABC.', then hits a 'CR' or 'CTL-IV' which moves the cursor to the OUTPUT DEVICE field. He enters 'VDT' followed by a 'CR'. The cursor stops at the last field, ENTRIES CORRECT, and he then types in 'Y' since all the entries are correct. The calculation immediately begins and the formatted output is displayed: Figure 3-8. Sample Output, Node Space Calculation ______ ____ ______ _______ ____ _____ ___________ File File Max Used Rec Key Used Max Name Type Recs Recs Siz Siz Secs Secs (XYZ) .ABC.XXXXXXXXXXX XX XXXXX XXXXX XXX XX XXXX XXXX .ABC.XXXXXXXX XX XXXXX XXXXX XXX XX XXXX XXXX Total sectors for files under .ABC. after conversion: XXXXXXXXX Total sectors for files under .ABC. when files are full: XXXXXXXXX Output description: File Type: Possible file types are 'IND' for Indexed, 'DIR' for Direct, 'SER' for Serial, 'SRT' for Sort, 'SYS' for System SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg021 PASCAL, 'BB' for Business BASIC, and 'COB' for Business COBOL. Max Recs: Maximum number of records for a file. Used Recs: Number of records actually used by a file. Rec Siz: Record size in bytes. Key Size: Key size in bytes. This column only applies to Direct and Sort files. Used Secs: Number of sectors that will actually be allocated after converting to 8.5 file format. The amount of space taken up by a file immediately after conversion depends on the file type, but is the same whether one does disk-to-disk conversion or SAVERESTORE-type conversion. Indexed files are compacted back to occupy just enough space to include the block containing the highest-positioned record in the file. This is the same as what happens using SAVERESTORE without conversion, or using the COMPACT utility FILESIZE Utility on an 8.5 Indexed file. Serial files are handled exactly the same way as indexed files. Direct and Sort files are handled a little differently, to be compatible with the file system's attempt to partially "tune" the performance of these files. They will contain enough sectors to hold the greatest of these: (a) the number of records already in the file; (b) 40% of the declared maximum number of records for the file (rounded down); (c) one record (this case is rare). However, a 'create' of Indexed and/or Serial files on a system using 8.5 file format will require a different number of sectors as opposed to conversion. It will allocate enough sectors to hold 40% of the declared maximum number of records. Therefore, the number of sectors required to allocate an initially created file very possibly may be greater than the number of sectors required during conversion. Max Secs: Maximum number of sectors needed assuming this file is full. A file is full when 'Used Recs' = 'Max Recs' Total sectors for files under .ABC. after conversion: Sum of 'Used Secs'. Total sectors for files under .ABC. when files are full: Sum of 'Max Secs'. 3.2.3.3.2. Single File Space Calculation ______ ____ _____ ___________ The user enters the file name '.ABC.testfile.text'. The screen immediately responds with each attribute shown at its corresponding field and the cursor stops at the OUTPUT DEVICE SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg022 field. The user chooses the '.XYZ.outfile' as the output device and 'Y' for ENTRIES CORRECT field. The output goes to both the file '(DISK).XYZ.outfile' and the screen with the same format as in 3.2.3.3.1 except that there is no line that says 'Total sectors for files under XXX are : ' since there is only one file. 3.2.3.3.3. Non-Existing File Space Calculation ____________ ____ _____ ___________ The user skips the NODE OR FILE NAME field by pressing 'CR'. He then enters 'D' for FILE TYPE, '10000' for RECORDS DECLARED, '300' for ACTUAL RECORDS, '80' for RECORD SIZE, '20' for KEY SIZE, 'T*' for OUTPUT DEVICE and 'Y' for ENTRIES CORRECT. The output shows on the terminal with the same format as in 3.2.3.3.1, but the 'File Name' field is left FILESIZE Utility blank because it is a non-existing file. 3.2.4. NFSCONVERT Utility __________ _______ 3.2.4.1. Introduction ____________ This utility is also documented in previous software announcements. It is included here for easier reference when converting to the new File System. The Disk to Disk Conversion Utility provides the user with a ____ __ ____ __________ _______ method for converting files with an old file format (Release 8.4D and earlier) to the new file format. The user may convert a single file or a group of files. The files to be converted can be specified by individual file name, node name or by masking. No more than one terminal may be converting a given family on the system. You can convert more than one family at a time, using different terminals for each family. 3.2.4.2. Workspace Required for Keyed Files _________ ________ ___ _____ _____ NFSCONVERT uses a sizable amount of workspace when converting keyed (Direct and Sort) files. Therefore, it is strongly recommended that all keyed files in a family be converted first. NFSCONVERT first looks for workspace on the User Default Family. If it cannot find enough workspace there, it looks for space on the System Default Family. ("!UDFAMILY" will display the name of the User Default Family, and "!SDFAMILY" will display the name of the System Default Family.) If NFSCONVERT still cannot locate enough workspace, a message will display that it is out of usable disk space. If this occurs, and there is an extra disk drive on your system for a removable pack, you may mount an 8.5 formatted scratch pack on that drive. You must then run INSTALL.PARAMS, option 4, (TYPE 1 LOAD) to temporarily change the name of the User Default SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg023 Family to the family name on the scratch pack. This will cause NFSCONVERT to use the scratch pack for the workspace needed to convert the keyed files. (Remember to change the User Default Family back to its original name when the conversion is complete.) If NFSCONVERT runs out of disk space, and you do not have an extra drive on your system, you must do the conversion to tape using SAVERESTORE. If you would like to estimate the amount of workspace NFSCONVERT will require for your keyed files, you can apply this formula: Add 5 to the declared keysize for the file, and multiply the result by the number of records written to in the file. Then multiply this number by 7. Divide the result by NFSCONVERT Utility 1024, and you will have the approximate number of workspace sectors NFSCONVERT will require for the file. 3.2.4.3. Procedures for Using Utility __________ ___ _____ _______ 3.2.4.3.1. By Command with Parameters __ _______ ____ __________ The Disk to Disk Conversion Utility can be run by entering a ____ __ ____ __________ _______ command with parameters in console mode or as a program directive. The format is as follows: NFSCONVERT filename1, filename2 {,OUTPUT= } {,VERIFY= } {,PAUSE= } {,DELEXIST= } {,OUTACTION= } {,TYPE= } {,QUIET= } Each of the parameters is explained in Table 3-8. NFSCONVERT Utility Table 3-8. Parameters for NFSCONVERT _____ ____ __________ ___ __________ -------------------------------------------------------------------------- | Requried Parameters (Positional) | | Parameter Values and Effects | | --------- ------------------ | | 1. filename1= Name of file(s) to be converted. String | | May be an individual file name, | | a node, or mask. The file(s) may | | be specified using point-to-point | | syntax in the mask. | | | | 2. filename2= Name of destination file(s). String | | May be an individual file name, | | a node, or mask. | |------------------------------------------------------------------------| | Optional Parameters (Keyword) | | Parameter Keyword Values and Effects | | --------- ------- ------------------ | SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg024 | 1. Output device OUTPUT= LP ,P1, etc = line printer | | for listing filename = selected file | | ** VDT = VDT only | | | | 2. Verify Conversion VERIFY= ** T = Verify | | F = do not Verify | | | | 3. Whether program should PAUSE= ** T = Pause on errors | | pause on errors F = Do not pause on errors | | | | 4. Whether file existing DELEXIST= T = Delete existing files | | under destination name ** F = Do not delete existing | | is to be deleted. files | | | | 5. Whether output file OUTACTION= A = Append to file if it | | should be deleted if it exists | | exists, appended to if D = Delete file if it | | exists, or tell user that exists | | it exists. ** N = Do not delete or append | | | | 6. What type of files should TYPE= ** A = All files found in | | be converted. group specified. | | K = Only KEYED files found | | in group specified. | | O = Only NON-KEYED files | | found in group. | | | | 9. Whether output to the QUIET= T = No output to the VDT. | | terminal should be Verify and Pause must | | suppressed. be false. | | ** F = Normal output. | | ** Defaults | -------------------------------------------------------------------------- NFSCONVERT Utility Help for the Disk to Disk Conversion Utility can be displayed ____ __ ____ __________ _______ to the console with the following command: NFSCONVERT.HELP [] The printer name is optional. If it is specified then the help screens will be sent to the printer. If a printer name is not specified then the screens will be displayed at the console and the user is prompted at the end of each page with a: 'CR' TO CONTINUE:. 3.2.4.3.2. By Menu or Command without Parameters __ ____ __ _______ _______ __________ The user can run this utility by keying the command 'NFSCONVERT with no parameters in console mode. The program responds by displaying the screen shown in Figure 3-9. Figure 3-9. NFSCONVERT Data Entry Screen ______ ____ __________ ____ _____ ______ MAI BASIC FOUR, INC. DISK TO DISK CONVERSION UTILITY PRIMARY PREFIX : XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg025 START SPECIFIER: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX END SPECIFIER : XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX DESTINATION : XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX DELETE EXISTING DESTINATION FILE : XXXXXXXXX VERIFY : XXXXXXXXX PAUSE ON ERRORS : XXXXXXXXX TYPE: XXXXXXXXXX OUTPUT DEVICE : XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX ENTRIES CORRECT (Y/N): XXXXXXXXX 3.2.4.3.2.1. Field Descriptions _____ ____________ The purpose for each field in the Data Entry Screen is as follows: 1. The PRIMARY PREFIX field is a display-only field listing the user's primary prefix. If the source file or destination file does not exist in this prefix, a fully-specified file name must be specified. 2. The File Name consists of two fields: The START SPECIFIER and the END SPECIFIER. Because of the NFSCONVERT Utility possible length of the file name, the interactive utility must use two fields. For normal file masking, only the '&' and the '^' masking characters can be used. The '&' can only be used as the last character. a) The START SPECIFIER is used for all types of files to be converted. If the user wants a specific range of files he may use point to point syntax. In the START SPECIFIER field the user must enter the starting point of the range. The last character of this specifier must be a '/' to specify point to point masking. When the utility sees the '/', the user will then be prompted for the END SPECIFIER. If the user did not specify point to point masking, the END SPECIFIER field will not be used. When the cursor reaches this field the prompt displayed on line 24 is: ENTER INDIVIDUAL FILE NAME, NODE, OR MASK NAME To convert selected files, enter the individual file name, node or mask. Entering a '?' causes the help screens to be displayed. The user should be aware that he is specifying files on an Old File System format family at this point. That family must be present, of course, but cannot and need not be enabled. Two families with the same name can be on the same system at the same time, provided that one of them has Old File System format, and the other has New File System format. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg026 Possible errors for the Start Specifier field, if the file name specified does not have point to point syntax, are shown in Table 3-9. NFSCONVERT Utility Table 3-9. Possible Errors for Start Specifier, not Point-to-Point _____ ____ ________ ______ ___ _____ __________ ___ ______________ ------------------------------------------------------------------------- | ERROR MESSAGE | REASON FOR ERROR | ------------------------------------------------------------------------- | INVALID FILE NAME | The utility does not recognize the | | | entry as an individual file name, | | | mask, or node. | | FILE DOES NOT EXIST | Individual file name entered and | | | file does not exist. | | NODE DOES NOT EXIST | Node does not exist. | ------------------------------------------------------------------------- b) The END SPECIFIER is the ending file name in point to point masking. This field will only be used if point to point masking was specified in the START SPECIFIER field. When the cursor reaches this field the prompt: ENTER INDIVIDUAL FILE NAME, NODE, OR MASK NAME is displayed on line 23. The default for this field is '.': convert all files to the end of the directory. Note: Errors for the START SPECIFIER field and END SPECIFIER field, if point to point, will not be detected until after the destination field is entered. The error message will be displayed for all three fields, as if they were one. 3. DESTINATION is used to enter the names of the files to be converted to by this utility. For masking, only the '&' and the '^' can be used. The '&' can only be used as the last character. When the cursor reaches this field the prompt appears on line 23 of the screen: ENTER INDIVIDUAL FILE NAME, NODE, OR MASK NAME Enter the individual file name, node or mask of the destination file(s). Errors for the START SPECIFIER field and END SPECIFIER field, if point to point, will not be detected until this field is entered. The error message will be displayed for all three fields, as if they were one. Possible errors for the Destination field are shown in Table 3-10. NFSCONVERT Utility Table 3-10. Possible Errors for Destination Field _____ _____ ________ ______ ___ ___________ _____ ------------------------------------------------------------------------- | ERROR MESSAGE | REASON FOR ERROR | SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg027 ------------------------------------------------------------------------- | INVALID FILE NAME | The utility does not recognize the | | | entry as an individual file name, | | | mask, or node. | | 'SOURCE' AND 'DESTINATION' | The start and destination file | | MUST BE OF SAME TYPE | specifiers must be of same type, | | | i.e. both individual file names, | | | mask, nodes or point-to-point. | | INVALID PT2PT RANGE | The start and end file specifiers | | | must be in the same range | | NO FILE FOUND IN RANGE OF | There was no file(s) found in the | | PT2PT SPECIFIER | specified range of the start and | | | end specifier. | | FILE DOES NOT EXIST | Individual file name entered and | | | file does not exist. | | NODE DOES NOT EXIST | Individual node name entered and | | | node does not exist. | ------------------------------------------------------------------------- Note: If a 'CTL-II' is entered from the destination _____ field the cursor will be moved to the start specifier field. 4. DELETE EXISTING DESTINATION FILE is used to specify whether a file already existing under the destination file name is to be deleted. If you elect not to have an existing file deleted, and the program encounters a file under the destination file name, the program will not convert the source file to that destination file name. When the cursor arrives at this field, the prompt DELETE EXISTING DESTINATION FILE, (Y/N), 'CR'=___ is displayed on line 23. ___ is the current default for this field. The initial default is <'N'>. If the user does not respond with 'YES', 'NO', or any subset of these ('Y','YE','N'), the program outputs INVALID ENTRY on line 23. 5. VERIFY is used to designate whether or not the user wishes to authorize conversion of each file before doing so. When the cursor arrives at this field, the NFSCONVERT Utility prompt VERIFY EACH CONVERSION, (Y/N), 'CR'=___ is displayed on line 23. ___ is the current default; the initial default is <'Y'>. If the user does not respond with 'YES', 'NO', or any subset of these ('Y','YE','N'), the program outputs INVALID ENTRY on line 23. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg028 6. PAUSE ON ERRORS is used to direct the utility to stop and inform the user when an error occurs while attempting to convert the primary file. When the cursor arrives at the field, the prompt PAUSE ON ALL ERRORS, (Y/N), 'CR'=___ is displayed on line 23. ___ is the current default; the initial default is <'Y'>. If the user has already specified VERIFY=TRUE the response to this field is ignored and the utility will pause before every file whether there is an error or not. However, if the user responds to the VERIFY prompt with 'CTL-II' while the utility is executing, the PAUSE ON ERRORS will remain enabled even after the VERIFY has been turned off. If the user does not respond with 'YES', 'NO', or any subset of these ('Y','YE','N'), the program outputs INVALID ENTRY on line 23. 7. TYPE is used to designate the type of files to convert. The user may convert all file types, only keyed files, or only non-keyed files. If a disk is close to being full and the user converts all files, the user may run out of space, even though there is enough room for the files. There may not be enough room to work through the conversion. In this case the user will want to convert KEYED files first. These files take more work area to convert. Then he will want to convert all other non-keyed files. When the cursor arrives at this field, the prompt NFSCONVERT Utility TYPE OF FILES TO CONVERT, ALL, KEYED, NON KEYED (OTHER), (A/K/O), 'CR' = ___ where ___ is the current default for this field. The initial default is to convert all files (A). When something other than A, K, or O is entered, the error: INVALID ENTRY is displayed on line 23. 8. OUTPUT DEVICE is used to designate a device or file where a summary status of the activity will be reported. The report may be written to the VDT only, to the VDT and a line printer, or to the VDT and a specified file. When the cursor arrives at this field, the prompt ENTER DEVICE OR FILE NAME, 'CR'=___ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg029 is displayed on line 23. ___ is the current default; the initial default is 'VDT'. If the user enters the name of a file that already exists, the utility will delete the existing file, but only at the user's direction. To determine what action to take, the program prompts with FILE ALREADY EXISTS, DO YOU WISH TO DELETE OR APPEND TO THE FILE (D/A/N): XX on line 23. If the response is 'D', the utility will delete the existing file and write its report to a new file having the same name. If the response is 'A', the utility will append its report to the end of the existing file without altering the original data in the file. If the response is 'N', no action will be taken, the file will not be deleted, and the utility will prompt again for the OUTPUT DEVICE. NOTE! When the Append option is requested, the file to ____ which the appending takes place must be a SERIAL file. Possible errors for this field are shown in Table 3-11. NFSCONVERT Utility Table 3-11. Possible Errors for OUTPUT DEVICE Field _____ _____ ________ ______ ___ ______ ______ _____ ------------------------------------------------------------------------- | ERROR MESSAGE | REASON FOR ERROR | ------------------------------------------------------------------------- | INVALID OUTPUT DEVICE | Entry is not a valid name of file, | | | printer, or terminal. | | PRINTER DOES NOT EXIST | Entry is valid printer name but not | | | currently on the system. | | TERMINAL ALREADY OPEN | Entry is name of a terminal that is | | | already open by another user. | | PRIVILEGE INSUFFICIENT | User's account lacks the privilege to | | | delete or write to the existing | | | OUTPUT file. | | FILE ALREADY EXISTS | OUTPUT file exists and user passed | | | OUTACTION=N from command line. | | FILE MUST BE SERIAL TO APPEND | User is attempting to Append to a | | | non-SERIAL OUTPUT file. | ------------------------------------------------------------------------- 9. ENTRIES CORRECT is used to retain the request parameters on the screen long enough to allow the user to verify their correctness and make any desired changes. There is no prompt for this field. If the user enters 'Y', the conversion operation begins. If the user enters 'N', the cursor returns to the first input field and the earlier entry for the field is erased. All entries are retained for use as current default values. If the user enters 'CTL-IV', the cursor returns to the first input field, all field entries are erased, and the utility reverts to the initial defaults. If the user does not respond with 'YES', 'NO', or any subset of these ('Y','YE','N'), the program outputs SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg030 INVALID ENTRY on line 23. 3.2.4.4. Functions Performed _________ _________ When the Disk to Disk Converstion Utility is run, the program ____ __ ____ ___________ _______ produces a display or a printing of the results of the utility. Whenever results are sent to a printer or to a specified file, they are also displayed at the VDT. When the results which have been sent to a specified file are spooled to a line printer, they look identical to the results sent directly to the printer. Figure 3-10 shows the results at the VDT. NFSCONVERT Utility If the user set the parameter QUIET as TRUE then output to the VDT is suppressed. The user will see no output, not even errors. If the parameter PAUSE or VERIFY was passed in as TRUE as well as QUIET then the error INCONSISTENT PARAMETERS PASSED is generated. You can't run quietly and still prompt the user. If an output device was specified then output will go there as usual. Figure 3-10. NFSCONVERT Display on the VDT ______ _____ __________ _______ __ ___ ___ MAI BASIC FOUR, INC. DISK TO DISK CONVERSION UTILITY SOURCE FILE NAME DESTINATION FILE NAME ACTION (family name) (family name) .AAA.AFILE.TEXT .XXX.AFILE.TEXT CONVERTED .AAA.BFILE.TEXT .XXX.BFILE.TEXT SKIPPED .AAA.CFILE.TEXT .XXX.CFILE.TEXT CONVERTED .AAA.CFILE .XXX.CFILE CONVERTED .AAA.DFILE .XXX.DFILE CONVERTED .AAA.EFILE.TEXT .XXX.EFILE.TEXT CONVERTED .AAA.FFILE .XXX.FFILE CONVERTED .AAA.GFILE.TEXT .XXX.GFILE.TEXT CONVERTED .AAA.HFILE .XXX.HFILE CONVERTED For each file that was selected for conversion, the program displays the source and destination file name. If the user specified verification the prompt 'CR','CTL-I' TO CONVERT, 'CTL-II'=VERIFY OFF, 'CTL-III'=SKIP, 'CTL-IV'= EXIT: XX is displayed on line 23. The user must respond to the prompt before the file can be converted. If the user responds with or the utility tries to convert the file. If it is successful then the message CONVERTED is displayed on the same line as the file names and the next file name is SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg031 displayed on the next line. (If we are at the bottom line, line 21, then the list of files scrolls up one file.) If the utility could not convert the file the message ERROR is displayed on the same line as the file names. If we are verifying or if pause on errors is TRUE, the error message is displayed on line 23. If we are not verifying and pause on errors is not true the error message is not displayed. If the user responds to the prompt with a the message NFSCONVERT Utility CONVERTED is displayed on the same line as the file names, and the file is converted. The verification prompt is then no longer displayed and no verification takes place. If the user responds to the prompt with a the message SKIPPED is displayed on the same line as the file names, and the file is not converted. The next file is then displayed on the next line. When a is selected the conversion process quits and will return to the calling program. If the program was interactive then the copy files data entry screen is displayed with the cursor at the START SPECIFIER field and the user may specify the name of another file to be converted, otherwise the user is returned to the command line prompt. When all files selected have been processed the prompt 'CR' TO CONTINUE, 'CTL-IV' TO EXIT UTILITY: is displayed on line 23. When the user enters a the utility returns to the interactive screen or the command language. If the program was run through the interactive utility then the data entry screen is redisplayed and the cursor is placed at the START SPECIFIER field and the user may specify the name of another file to be copied. Otherwise the user is returned to the command line prompt. If the user enters a from the prompt, the utility will exit to the program that called the utility, either the command language, BASIC, or a program. This feature allows the user to bypass the interactive data screen when exiting. If the verify option was not selected the utility will try to convert all files specified. If an error occurs and pause on errors is set, the error message is displayed on line 23. In addition to the displays and/or printed reports, all program and system errors are displayed on the OUTPUT DEVICE. The output listing to a file or printer looks like the VDT display except the actual error encountered is printed under the file name. Figure 3-11 shows output to a file or printer. This conversion would have been invoked by the command: NFSCONVERT (FamilyA).AAA.,(FamilyB).XXX.,OUTPUT=LP NFSCONVERT Utility Figure 3-11. NFSCONVERT Output to a Printer or File SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg032 ______ _____ __________ ______ __ _ _______ __ ____ MAI BASIC FOUR, INC. DISK TO DISK CONVERSION UTILITY SOURCE FILE NAME DESTINATION FILE NAME ACTION (family name) (family name) .AAA.AFILE.TEXT .XXX.AFILE.TEXT CONVERTED .AAA.BFILE.TEXT .XXX.BFILE.TEXT ERROR FILE LOCKED .AAA.CFILE.TEXT .XXX.CFILE.TEXT CONVERTED .AAA.CFILE .XXX.CFILE CONVERTED .AAA.DFILE .XXX.DFILE CONVERTED .AAA.EFILE.TEXT .XXX.EFILE.TEXT ERROR PRIVILEGE INSUFFICIENT .AAA.FFILE .XXX.FFILE CONVERTED .AAA.GFILE.TEXT .XXX.GFILE.TEXT CONVERTED .AAA.HFILE .XXX.HFILE CONVERTED Output to the terminal when the utility is called from console mode with parameters is shown in Figure 3-12. The first file name is displayed on the line following the command. If the verify parameter was set to TRUE, the user is prompted for verification. The prompt: CONVERT? ('CTL-I' = Y /'CTL-III' = N/'CTL-II'=VERIFY OFF) is displayed on the line following the file name. The messages CONVERTED, and SKIPPED are displayed on the same line as the file names. If the copy encountered an error, it is displayed under the file name. If pause on errors is TRUE the user is prompted for 'CR' TO CONTINUE. NFSCONVERT Utility Figure 3-12. NFSCONVERT Display with Parameters ______ _____ __________ _______ ____ __________ SOURCE FILE NAME DESTINATION FILE NAME ACTION (family name) (family name) .AAA.AFILE.TEXT .XXX.AFILE.TEXT CONVERTED .AAA.BFILE.TEXT .XXX.BFILE.TEXT ERROR FILE LOCKED .AAA.CFILE.TEXT .XXX.CFILE.TEXT CONVERTED .AAA.CFILE .XXX.CFILE CONVERTED .AAA.DFILE .XXX.DFILE CONVERTED .AAA.EFILE.TEXT .XXX.EFILE.TEXT ERROR PRIVILEGE INSUFFICIENT .AAA.FFILE .XXX.FFILE CONVERTED .AAA.GFILE.TEXT .XXX.GFILE.TEXT CONVERTED .AAA.HFILE .XXX.HFILE CONVERTED 3.3. GENERAL INFORMATION _______ ___________ 3.3.1. Software Announcement ________ ____________ With this release, a copy of this software announcement exists SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg033 as a serial file on the system, which allows the user to print a copy, if needed. This file can be submitted to a printer using the SUBMIT utility. The document file is named: (family).R5D24.INST.DOC.SA5D Diagnostics 3.4. DIAGNOSTICS ___________ Please see the installation sections of this announcement for instructions on how to install DEMON and REMIDI. Further information on these diagnostics can be found in DOCWRITER, which is located in the .R5D24.INST. node. 3.4.1. REMIDI ______ NOTE: Running UPDATE.OS automatically updates the load sectors for the disk. However, running UPDATE.WCS does not. (The Load Sectors are displayed at the top of the OSINFO screen.) It is therefore necessary to run UPDATE.LD for REMIDI on newly initialized systems packs, or whenever question marks ("?/?") appear in Load Sector 2 on the OSINFO screen. 3.4.1.1. REMIDI for MPx 7000 and 8000 Series Systems ______ ___ ___ ____ ___ ____ ______ _______ REMIDI version BV5C0101 includes all micro-diagnostics except those for the MPC controller. It is loaded into WCS slot 2 and is used on both MPx 7000 and 8000 Series Systems. REMIDI version BVM5C0101 contains micro-diagnostics for the MPC controller only, is loaded into WCS slot 3, and is used only on MPx 7000 Series Systems. The Load Directory controls which version of REMIDI will be executed on MPx 7000 Series Systems. The UPDATE.LD utility is used to update the Load Directory. 3.4.1.1.1. Using REMIDI on 7000 Series Systems _____ ______ __ ____ ______ _______ Since REMIDI is a WCS Image, and the 7000 requires the additional REMIDI image for MPC controller testing, two WCS slots will be required for the two versions. The extra slot will be provided by the DEMON WCS slot. It is necessary to update the load directory, using the UPDATE.LD utility, to have DEMON use OS slot 3 and WCS slot 0. (DEMON and the BOSS/VS Operating System both use the same WCS image). UPDATE.LD will also be required to toggle between the two versions of REMIDI, since only one version can run at a time. If you have an MPx 7000 Series System, the following steps must be taken: NOTE: LINES PRECEDED BY AN "*" REQUIRE OPERATOR INPUT. 1) Install the REMIDI version BVM5C0101 WCS in slot 3 with UPDATE.WCS: * Input in command mode !UPDATE.WCS. Update.WCS 8.5xx.x * ENTER WCS Slot (0..3) :3 Available disk units are :0,1 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg034 * Disk to update :0 * WCS image file (=first found :.R5xxx.INST.REMIDI.BVM5C0101 Diagnostics Updating Disk Unit 16 sector 415 WCS update completed ! NOTE: THE LEVEL OF THE WCS IMAGE FILE MUST BE KNOWN. THIS LEVEL IS ALSO THE OPERATING SOFTWARE LEVEL, (i.e. .R5D24.). 2) Update the Load Directory for DEMON by using UPDATE.LD: * Input in command mode !UPDATE.LD Update Load Directory Utility Disks (Unit number) on line : 0(16),1(17) Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 5.4.24.1 R 5D*24 860821 B 5.3.7 1 1/1 | 5.4.24.1 R 5D*24 860821 B 5.3.7 2 0/2 | B 5.x.x R 3 3/3 | 5.4.0.0 DEMON 6/30/86 B 5.x.x R * New OS slot (0,1,3): 3 * New WCS slot (0..3): 0 or 1 (Slot booted from) * Load sector (0..3) : 3 Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 5.4.24.1 R 5D*24 860821 B 5.3.7 1 1/1 | 5.4.24.1 R 5D*24 860821 B 5.3.7 2 0/2 | B 5.x.x R 3 3/0 | 5.4.0.0 DEMON 6/30/86 B 5.x.x R NOTE: NOTICE THE CHANGE IN LOAD 3. IT WENT FROM 3/3 TO 3/0. IT WAS USING WCS SLOT 3; IT IS NOW USING WCS SLOT 0. Only one version of REMIDI will run at a time. The version that will run is dependent on how the Load Directory for REMIDI (load sector 2) is set up. The standard version, BV5C0101, which resides in WCS slot 2, has an OS/WCS of 0/2. The MPC version, BVM5C0101, which resides in WCS slot 3, has an OS/WCS of 0/3. Use UPDATE.LD to update the load directory to designate which version to run. To test the MPC controller with REMIDI version BVM5C0101, execute UPDATE.LD, as in step 2 above, using the following: * New OS slot (0,1,3): 0 * New WCS slot (0..3): 3 * Load sector (0..3) : 2 To go back to the standard REMIDI version, BV5C0101, which tests the CPU and main memory, use the following in UPDATE.LD: * New OS slot (0,1,3): 0 * New WCS slot (0..3): 2 * Load sector (0..3) : 2 Diagnostics 3.4.1.2. REMIDI for MPx 9000 and 9500 Series Systems ______ ___ ___ ____ ___ ____ ______ _______ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg035 Another version of REMIDI contains micro-diagnostics for the MPx 9000 and 9500 Series Systems. It consists of two sections, AVA5C0901, which is loaded into WCS slot 2, and AVC5C0901, which is loaded into WCS slot 3. 3.4.1.2.1. Changing the Load Sector for Slot Three ________ ___ ____ ______ ___ ____ _____ Because the second section of the 9000/9500 version of REMIDI is in WCS slot 3, the load directory must be changed to point to another WCS slot for DEMON. The 9.5D O.S. and DEMON share the same WCS code, therefore, we can point to the WCS slot used by the 9.5D O.S. Update the Load Directory for DEMON by using the UPDATE.LD utility: * Input in command mode !UPDATE.LD Update Load Directory Utility 9.5xxx.xx Disks (Unit number) on line : 0(16),1(17) Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 5.4.24.1 R 5D*24 860821 A 5.7.0 1 1/1 | 5.4.24.1 R 5D*24 860821 A 5.7.0 2 0/2 | A 5.14.1 R 3 3/3 | 5.4.0.0 DEMON 6/30/86 A 5.14.1 R * New OS slot (0,1,3): 3 * New WCS slot (0..3): 1 (May be changed to 0 after upgrade.) * Load sector (0..3) : 3 Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 5.4.24.1 R 5D*24 860821 A 5.7.0 1 1/1 | 5.4.24.1 R 5D*24 860821 A 5.7.0 2 0/2 | A 5.14.1 R 3 3/1 | 5.4.0.0 DEMON 6/30/86 A 5.14.1 R Notice that load sector 3 is now pointing to WCS slot 1. Hardware 4. HARDWARE ________ 4.1. LARLS FOR PCBAS FOR MPX 7000 AND 8000 SERIES SYSTEMS _____ ___ _____ ___ ___ ____ ___ ____ ______ _______ The Lowest Acceptable Revision Levels for 7000 and 8000 PCBAS are identical to those for 8.4B/C/D with the following exceptions: 1) MPC 903500 PCBA-Revision H 2) MPC 903549 PCBA-Revision B 3) BMTC 903413 PCBA-Revision R 4) ACS PCBA - 7000 systems only=> Y 8000 systems only=> L (T if BMTC) ** NOTE: Revision AA supports either the 7000 or 8000 series systems. Revision levels V-Y cannot be used on 8000 systems. Revision level Z cannot be used on 7000 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg036 systems. ** 5) 1/4" Micro Cartridge Streamer (No change from 8.5A) Revision 5 for main PWB Revision 9 for formatter PWB 4.2. LARLS FOR PCBAS FOR MPX 9000 AND 9500 SERIES SYSTEMS _____ ___ _____ ___ ___ ____ ___ ____ ______ _______ The Lowest Acceptable Revision Levels for PCBAs for MPx 9000 and 9500 Series Systems are: 1) MCS 903374 PCBA-Revision L 2) AMS 903548 PCBA-Revision F 3) ESTK 903552 PCBA-Revision D 4) IDC 903550 PCBA-Revision J 5) DMA 903554 PCBA-Revision E 6) IMLC 903381 PCBA-Revision K IMLC 903534 PCBA-Revision D 7) BMTC 903413 PCBA-Revision R 8) Memory (1/2 and 1 MB) 903349 PCBA-Revision V 9) Memory (2 and 4 MB) 903516 PCBA-Revision E 10) Hi-speed video controller 903377 PCBA-Revision C 11) 8-Way 903383 PCBA-Revision A 12) 16-Way 903437 PCBA-Revision J 13) PPS II (Protected Power Supply) 907251 PCBA-Rev. E 14) PPS II 906418 PCBA-Revision D The following boards are NOT supported on the MPx 9000 and 9500 Series Systems: 1) 7000/8000 CPU set 2) TDP (Must be replaced by the BMTC for tape support) 3) MPC Hardware 4.3. PARALLEL DMP DEVICE VARIANCE CONFIGURATION ________ ___ ______ ________ _____________ With the 8.5 releases, the parallel DMP device variance code needs to be changed. Previously, the DMP printer had the same code as a matrix printer. Changing the DMP printer to a new device variance is done by changing the switch settings on the appropriate controller board. 4.3.1. MPx 7000 and 8000 Series Systems ___ ____ ___ ____ ______ _______ The new DMP printer switch settings are: TDP CONTROLLER BOARD 903217 OR 903453 ___ __________ _____ ______ __ ______ Switch 4C Position # 8 7 6 _ _ _ O O C MPC CONTROLLER BOARD 903500 OR 903546 ___ __________ _____ ______ __ ______ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg037 903500 ______ Switch 2A (SW2) PRINTER 0 S2-2 S2-5 S2-8 PRINTER 1 S2-3 S2-6 S2-7 ____ ____ ____ C O O 903546 ______ Switch 2A (SW2) Switch 9F (SW5) * Position # Position # (Strobe) Printer 0 S2-3 S2-4 S2-5 Printer 0 S5-1 Printer 1 S2-6 S2-7 S2-8 Printer 1 S5-2 ____ ____ ____ ____ O C O O * NOTE: Switch SW5, location 9F, selects whether a printer will receive a "normal" or inverted data strobe. 4.3.2. MPx 9000 and 9500 Series Systems ___ ____ ___ ____ ______ _______ The new DMP printer switch settings are: DMA CONTROLLER BOARD 903554 ___ __________ _____ ______ Switch 6J (SW2) PRINTER 0 S2-1 S2-2 S2-3 S2-4 PRINTER 1 S2-5 S2-6 S2-7 S2-8 ____ ____ ____ ____ C C O C Hardware O-Open or Off C-Closed or On 5. INSTALLATION ____________ 5.1. INTRODUCTION ____________ There are two ways to install 8.5D: 1) Install a new system 2) Update a system If you are installing a new system go to section 5.2. If you are upgrading a system from 8.4D or below go to section 5.3. If you are upgrading a system from a level above 8.4D, go to section 5.4. If you are upgrading to 9.5D, go to section 5.5. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg038 5.2. NEW INSTALLATION ___ ____________ The loading of 8.5D is done the same as any other BOSS/VS release. Since the operating system can be released on 1/2" (reel) or 1/4" (cartridge) tape, the word "tape" means either media form. 5.2.1. Installing the O.S. __________ ___ ____ 5.2.1.1. ALT LOAD ___ ____ A) Insert the new release tape into the tape drive. B) Press the "ALTLOAD" button on the front panel. C) Enter the appropriate system disk (0 or 1) or if drives 0 and 1 are both system disks, enter "2" to update both disks. D) Enter a "0" to update WCS slot 0. E) Enter a "Y" to the prompt "Are you SURE you want to overwrite this WCS ? (Y/)". The system automatically updates the OS and WCS slot 0 on both disks, if selected. When this is complete, the system prompts "DONE - READY FOR NORMAL LOAD". Reload by pressing the LOAD button. 5.2.1.2. ENTER A TYPE 3 LOAD (SPECIAL FUNCTIONS) _____ _ ____ _ ____ ________ __________ Options 1-4 must be done to insure proper operation. New Installation 5.2.1.2.1. OPTION 1 (CHANGE VOLUME INFORMATION) ______ _ _______ ______ ____________ SYSTEM DISKS: (displayed) DRIVE NUMBER:__________ Enter the disk to update. SERIAL NUMBER:_________ Enter CR to accept current serial number. DISK CONFIGURATION (1=SYSTEM, 2=DATA, 3=BACKUP):____ Enter the appropriate disk type. SIZE OF DUMP AREA....:______ Enter the size of the dump area given by the line below this prompt as the area needed for both main memory and SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg039 shared memory controllers. FILE SYSTEM SPACE:______ Enter the number displayed at the bottom of the screen for this prompt. The display will appear as "CR=X" where X is the maximum space allowed. UPDATE DISK (Y/N): Enter "Y" 5.2.1.2.2. OPTION 2 (CHANGE INSTALLATION PARAMETERS) ______ _ _______ ____________ ___________ SYSTEM DISKS: (displayed) DRIVE NUMBER:_______ PRIMARY PREFIX ? Enter (family).R5D24.SYS. Where (family) is the family where the operating system files reside. SECONDARY PREFIX ? Enter (family).R5D24.SYS. New Installation Where (family) is the family where the alternate operating system files reside. DEFAULT USER FAMILY NAME ?:________ Enter default user family SECURITY (E=ENABLED, D=DISABLED):___ FILE SYSTEM WRITE THROUGH? (E=ENABLED, D=DISABLED):___ For conversion purposes, set this option to D (disabled). This will speed up the conversion process. It can be changed later if desired. WRITE THROUGH DEFAULT ON FILE CREATE (E=ENABLED, D=DISABLED):__ This parameter specifies what the default write through will be on a file created through a BASIC file create or through the CREATE utility. UPDATE DISK WITH INSTALLATION PARAMETERS? (Y/N)__ Display: PARAMETERS SUCCESSFULLY WRITTEN TO DISK 5.2.1.2.3. OPTION 3 (UPDATE FAMILY INFORMATION) ______ _ _______ ______ ____________ AVAILABLE DRIVES: (displayed) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg040 FAMILY BASE DRIVE NUMBER:___ DRIVE NUMBERS OF OTHER DISKS IN FAMILY? (TYPE SPACES FOR NO OTHER DRIVES): Enter all other drive numbers for this family or spaces if none. The drives must be fixed media drives and in 8.5 format. UPDATE DISK (Y/N) ? 5.2.1.2.4. OPTION 4 (INITIALIZE FAMILY DIRECTORY) ______ _ ___________ ______ __________ FAMILY NAME:______ Enter family name. INITIALIZE FAMILY (Y/N)?__ Option 1 must be done on all disks. Option 2 must be done to system disks only. Options 3 and 4 must be done for all New Installation families. 5.2.1.3. Restoring the O.S. _________ ___ ____ Enter SAVERESTORE in a TYPE II load and choose option #2 "RESTORE FILES FROM TAPE". The screen appears as in figure 5-1. At the prompt for output device, enter a parallel printer so that a listing of the restore operation is produced. This listing can be used to make sure all files were restored correctly. At the prompt, "FILE SPECIFIERS", enter ".". Enter to all other questions. All system files will be restored to disk. Please note that once all files are restored to disk, the message "AUTOMATIC COMPARE, CR TO CONTINUE" appears. This automatically rewinds the tape and begins the compare operation. This only occurs when the compare option is selected. When the compare is completed, enter a CTL-IV to return to the "SAVERESTORE" menu. Reload the system and enter a TYPE I load. Figure 5-1. Restore Screen ______ ____ _______ ______ -------------------------------------------------------- RESTORE FILES TAPE SET.ID: DRIVE-NUM: REEL-NUM: PRIMARY PREFIX: (FAMILY).NODE. FILETYPE (D/P/CR=ALL) COMPARE (CR=Y/N) DATE (MM/DD/YY) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg041 TIME (HH:MM) OUTPUT DEVICE (CR=VDT) DELETE EXISTING FILES (CR=Y) VERIFY (Y/CR=N) ENTRIES CORRECT (Y/N) -------------------------------------------------------- New Installation 5.2.2. UPDATING OTHER O.S. SLOTS ________ _____ ____ _____ The slots 1, 2, and 3 need to be updated. Set the prefix to the .INST. node by keying in the following in command mode: !PREFIX .R5D24.INST. With the inclusion of support for 7000 Series Systems, there are two versions of REMIDI, BV5C0101 and BVM5C0101. Version BV5C0101 includes all the micro-diagnostics except MPC controller micro-diagnostics. It is placed in WCS slot 2 and is used for testing on both the 7000 and 8000 Series Systems. Version BVM5C0101 consists of micro-diagnostics for the MPC controller only, and is placed in WCS slot 3 on 7000 Series Systems. 5.2.2.1. UPDATING SLOT ONE (1) ________ ____ ___ ___ A copy of the primary operating system will be put in slot 1. UPDATE.OS IMAGE FILE NAME: .R5D24.INST.OS1.UV050424001 OS SLOT: (displayed) OS VERSION: (displayed) IMAGE FORMAT: (displayed) NEW WCS SLOT: 1 UPDATE WHICH DISK: (0=nn/1=nn/B=BOTH/Q=QUIT)___ DONE ! UPDATE COMPLETE Next, WCS slot 1 is updated with a copy of the same WCS that was installed in slot 0. UPDATE.WCS ENTER WCS SLOT [0..3]: Enter '1' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R5D24.INST.WCS.B537 WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 5.2.2.2. UPDATING WCS SLOT TWO (2) ________ ___ ____ ___ ___ REMIDI version BV5C0101 will reside in this slot. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg042 New Installation UPDATE.WCS ENTER WCS SLOT [0..3]: Enter '2' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE: (choose disk) WCS IMAGE FILE: .R5D24.INST.REMIDI.BV5C0101 WCS LEVEL OF WCS IMAGE FILE: (level displayed) UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETED! 5.2.2.3. UPDATING SLOT THREE (3) ________ ____ _____ ___ 5.2.2.3.1. Updating O.S. Slot Three ________ ____ ____ _____ The O.S. slot 3 will contain the O.S. for DEMON on both 7000 and 8000 Series Systems. UPDATE.OS IMAGE FILE NAME: .R5D24.INST.OS3.UV050400000 OS SLOT: (displayed) OS VERSION: (displayed) IMAGE FORMAT: (displayed) NEW WCS SLOT: Enter '0' or '1' on 7000 Series Systems to associate the WCS in either slot with load sector 3. Enter '3' on 8000 Series Systems. UPDATE WHICH DISK (0=nn/1=nn/B=BOTH/Q=QUIT):____ UPDATING DISK DONE! UPDATE IS NOW COMPLETE NOTE: On MPx 7000 Series Systems, the UPDATE.LD utility needs to be run to update the Load Directory. For further information on the use of UPDATE.LD, see section 3.4. 5.2.2.3.2. Updating WCS Slot Three (3) ________ ___ ____ _____ ___ 5.2.2.3.2.1. WCS Slot Three on 7000 Series Systems ___ ____ _____ __ ____ ______ _______ This slot will contain the micro-diagnostics for the MPC controller, REMIDI version BVM5C0101. After this slot has been updated, it will be necessary to change the Load Directory by running the utility UPDATE.LD. See section 3.4 for further information on REMIDI and running UPDATE.LD. UPDATE.WCS ENTER WCS SLOT [0..3]: Enter '3' AVAILABLE DISK UNITS ARE: (displayed) New Installation SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg043 DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R5D24.INST.REMIDI.BVM5C0101 WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 5.2.2.3.2.2. WCS Slot Three on 8000 Series Systems ___ ____ _____ __ ____ ______ _______ This slot will contain system WCS which is common to both the O.S. and DEMON. UPDATE.WCS ENTER WCS SLOT [0..3]: Enter '3' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R5D24.INST.WCS.B537 WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 5.2.2.4. SLOT INFORMATION ____ ___________ Once all slots have been updated, use the utility OSINFO to display the slot information. The information should be simliar to figure 5-2. If disk 1 is a system disk also, repeat these steps beginning with step 5.2.2 Installation is now complete. Figure 5-2. Operating System Information ______ ____ _________ ______ ___________ OPERATING SYSTEM INFORMATION ------------------------------------------------------------------ BOOT LEVEL : X.X.X.X LOAD SECTOR: 0 1 2 3 DISK 0 : 0/0 1/1 0/2 3/3 SERIAL # : XXX-XXXXX ------------------------------------------------------------------ OS NAME OS LEVEL DISK:SLOT WCS LEVEL ------------------------------------------------------------------ R 85D*24 860821 5.4.24.1 0:0 B 5.3.7 R 85D*24 860821 5.4.24.1 0:1 B 5.3.7 N/A 0:2 REMIDI B 5.1.1 DEMON 6/30/86 5.4.0.0 0:3 B 5.3.7 ------------------------------------------------------------------ NOTE: OSINFO on 7000 Series Systems will show the additional version of REMIDI IN WCS slot 3. 8.5D Installation Procedure for Upgrade from 8.4D and Below 5.3. 8000 UPGRADE FROM RELEASE LEVELS OF 8.4D AND BELOW ____ _______ ____ _______ ______ __ ____ ___ _____ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg044 5.3.1. Introduction ____________ Since 8.5 contains new file formats and a new file system, conversion of files is required to make files compatible with the new file system, if you are upgrading from a software release level of 8.4D or below. If you are upgrading from a release level above 8.4D, skip to section 5.4. The file conversion can be done in two ways: A) From tape to disk B) From disk to disk Which method is used depends on the configuration of the system. The disk to disk method is preferable for a system with removable disks. The disk to disk method involves upgrading the system disk with the new O.S.. Then the system disk can be used to convert other disks by using the NFSCONVERT utility to convert one file from one disk to another. This also moves the data from one disk to another. If this method is used on fixed disks, the files may not reside on the family intended unless copied back later. This should be considered when using the disk to disk conversion. The tape conversion uses the utility SAVERESTORE. The conversion process is invisible to the user with the exception of a status message that may be displayed during conversion. All one needs to do to convert is use SAVERESTORE in a normal manner. The tape conversion requires about 4 minutes per megabyte of data. The installation procedure is broken into two parts: A) Preliminary evaluation B) Operating System upgrade and file conversion The preliminary evaluation is required to ensure that proper hardware and file preparation is done. An O.S. upgrade from releases of 8.4D and below entails loading of the 8.5D system and converting files to their new format The conversion process, in large configurations, will take more than one day. The BOSS/VS release 8.5A began support for the MAI 7000 Series System. The BOSS/VS tape for the 7000 Series System resides on a 1/4" magnetic cartridge streamer (MCS) tape. At the end of this section is an upgrade and conversion 8.5D Installation Procedure for Upgrade from 8.4D and Below checklist that should be used to track progress through the upgrade procedure. 5.3.2. Preliminary Evaluation ___________ __________ The preliminary section deals with revision levels and file preparation. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg045 5.3.2.1. Hardware Evaluation ________ __________ All hardware must be checked for proper operation. All boards must be at proper revision levels (see the section "HARDWARE"). Ensure that all tape units are operating correctly. Also, make sure that all memory boards are set for 160 ns operation. Also note that any 3 CE systems must have a revision K or higher on the IMLC board (if present). 5.3.2.2. File Preparation ____ ___________ Obtain a directory listing with partial attributes for each family in the system. This listing will help you to find files, if any, that need repair before conversion. Next, using DISKANALYZER, validate all files in the system. Now determine which files need repair. Files which have the following attributes MUST be repaired before they are saved to tape: A) Files which lack integrity. B) Files which have lost space. C) Non-serial files in which records used is greater than records defined. D) Files that have invalid format. These files can be located in several ways: A) Scan the directory listing noting any files flagged. B) Use the report generated by DISKANALYZER as a guide. C) Use the utility FINDLOSTSPACE (8.4C/D only). All of the above methods should be used to find files that lack integrity and that have lost space. However, the directory listing must be scanned to find files that have a greater number of records used then defined as maximum records. This is a very important step. Any file possessing any of these attributes WILL NOT convert properly. They have 8.5D Installation Procedure for Upgrade from 8.4D and Below to be repaired on a previous release before conversion. Any EDITOR recovery files must be recovered or deleted before conversion. The recovery files are identified by the node ED.REC.. After the node, there will be a series of digits. These files can be found by scanning the directory listing. These files must be recovered by using EDIT.RECOVER or deleted by using the DELETE utility. ***************************************** * * * ALL FILES MUST BE FREE FROM LACK OF * SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg046 * INTEGRITY, LOST SPACE, AND MAX * * RECORDS GREATER THAN DEFINED RECORDS. * * FILES WILL NOT BE CONVERTED IF THEY * * POSSESS ANY ONE OF THESE ATTRIBUTES * * * ***************************************** 5.3.2.3. 8.5D Space Requirements ____ _____ ____________ The space required for files under the new file system are about the same as under 8.4D/C/B/A levels. However, it is recommended that a listing be obtained which displays the files and their new sizes. On the 8.4D release, the program FILESIZE is used to produce this listing. The program FILESIZE will display the new file size under the 8.5 file system for each file in a given family. It will also display the total number of sectors required by the entire family under the new file system. For further information on this utility, see the section 3.2.3. 5.3.2.4. Saving Files to Tape ______ _____ __ ____ Files must now be backed up to tape. If you are using disk to disk conversion, it is STRONGLY recommended that all files be saved to tape. This will allow recovery of files in case of problems with the disk to disk conversion. The files are saved using the standard tape utility, SAVERESTORE. When saving files to tape, send the output from the save process to the printer. These will provide a record of backup for each file. Also it is recommended that all tapes be compared to the files on the disk. When using the tape or disk conversion, the conversion requires temporary disk space to sort keyed (direct and sort) files. The space required varies with the number of records and the size of the key. To insure proper space is available, the following steps should be observed: A) Do not restore the user default family 8.5D Installation Procedure for Upgrade from 8.4D and Below until last. B) Convert large keyed files first. Step A insures that the default user disk has a large amount of free space since this is where the tape and disk conversion utility defines the temporary files. Step B allows the files that require the most amount of temporary space to be converted first. To convert large keyed files first, they must be saved to tape first. The large keyed files can be identified by scanning the directory listing obtained in section 5.3.2.2. If using disk to disk conversion, the NFSCONVERT utility allows you to convert keyed files first. (See the section 3.2.4 for further information on this utility.) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg047 5.3.3. Operating System Update and File Conversion _________ ______ ______ ___ ____ __________ The loading of 8.5D is done the same as any other BOSS/VS release. However, there are some extra steps that are required to bring the disks into proper format. Since the operating system can be released on 1/2" (reel) or 1/4" (cartridge) tape, the word "tape" means either media form. 5.3.3.1. Installing the O.S. __________ ___ ____ 5.3.3.1.1. ALT LOAD ___ ____ A) Insert the new release tape into the tape drive. B) Press the "ALTLOAD" button on the front panel. C) Enter the appropriate system disk (0 or 1) or if drives 0 and 1 are both system disks, enter "2" to update both disks. D) Enter a "0" to update WCS slot 0. E) Enter a "Y" to the prompt "Are you SURE you want to overwrite this WCS ? (Y/)". The system automatically updates the OS and WCS slot 0 on both disks, if selected. When this is complete, the system prompts "DONE - READY FOR NORMAL LOAD". Reload by pressing the LOAD button. 8.5D Installation Procedure for Upgrade from 8.4D and Below 5.3.3.1.2. ENTER A TYPE 3 LOAD (SPECIAL FUNCTIONS) _____ _ ____ _ ____ ________ __________ This step is VERY important. Options 1-4 MUST be done for a 8.5D disk to be used on the system. These options MUST NOT be done for any disk that has not been converted to 8.5 format. If a tape conversion is being done, then initialize all disks at this time. If a disk to disk conversion is being done, then just initialize one scratch (8.5 format) pack that the converted files are going to reside on. In both cases the system disk(s) must be initialized. 5.3.3.1.2.1. OPTION 1 (CHANGE VOLUME INFORMATION) ______ _ _______ ______ ____________ SYSTEM DISKS: (displayed) DRIVE NUMBER:__________ Enter the disk to update. SERIAL NUMBER:_________ Enter CR to accept current serial number. DISK CONFIGURATION (1=SYSTEM, 2=DATA, 3=BACKUP):____ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg048 Enter the appropriate disk type. SIZE OF DUMP AREA....:______ Enter the size of the dump area given by the line below this prompt as the area needed for both main memory and shared memory controllers. FILE SYSTEM SPACE:______ Enter the number displayed at the bottom of the screen for this prompt. The display will appear as "CR=X" where X is the maximum space allowed. UPDATE DISK (Y/N): Enter "Y" 5.3.3.1.2.2. OPTION 2 (CHANGE INSTALLATION PARAMETERS) ______ _ _______ ____________ ___________ SYSTEM DISKS: (displayed) DRIVE NUMBER:_______ PRIMARY PREFIX ? 8.5D Installation Procedure for Upgrade from 8.4D and Below Enter (family).R5D24.SYS. Where (family) is the family where the operating system files reside. SECONDARY PREFIX ? Enter (family).R5D24.SYS. Where (family) is the family where the alternate operating system files reside. DEFAULT USER FAMILY NAME ?:________ Enter default user family SECURITY (E=ENABLED, D=DISABLED):___ FILE SYSTEM WRITE THROUGH? (E=ENABLED, D=DISABLED):___ For conversion purposes, set this option to D (disabled). This will speed up the conversion process. It can be changed later if needed. WRITE THROUGH DEFAULT ON FILE CREATE (E=ENABLED, D=DISABLED):__ This parameter specifies what the default write through will be on a file created through a BASIC file create or through the CREATE utility. UPDATE DISK WITH INSTALLATION PARAMETERS? (Y/N)__ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg049 Display: PARAMETERS SUCCESSFULLY WRITTEN TO DISK 5.3.3.1.2.3. OPTION 3 (UPDATE FAMILY INFORMATION) ______ _ _______ ______ ____________ AVAILABLE DRIVES: (displayed) FAMILY BASE DRIVE NUMBER:___ DRIVE NUMBERS OF OTHER DISKS IN FAMILY? (TYPE SPACES FOR NO OTHER DRIVES): Enter all other drive numbers for this family or spaces if none. The drives must be in 8.5 format. UPDATE DISK (Y/N) ? 8.5D Installation Procedure for Upgrade from 8.4D and Below 5.3.3.1.2.4. OPTION 4 (INITIALIZE FAMILY DIRECTORY) ______ _ ___________ ______ __________ FAMILY NAME:______ Enter family name. INITIALIZE FAMILY (Y/N)?__ Option 1 must be done to all disks. Option 2 must be done to the system disk. Options 3 and 4 must be done for all families. Reload the system by pressing the LOAD button and enter a TYPE II load. 5.3.3.2. Restoring the O.S. _________ ___ ____ Enter SAVERESTORE in a TYPE II load and choose option #2 "RESTORE FILES FROM TAPE". The screen appears as in figure 5-3. Figure 5-3. Restore Screen ______ ____ _______ ______ -------------------------------------------------------- RESTORE FILES TAPE SET.ID: DRIVE-NUM: REEL-NUM: PRIMARY PREFIX: (FAMILY).NODE. FILETYPE (D/P/CR=ALL) COMPARE (CR=Y/N) DATE (MM/DD/YY) TIME (HH:MM) OUTPUT DEVICE (CR=VDT) DELETE EXISTING FILES (CR=Y) VERIFY (Y/CR=N) ENTRIES CORRECT (Y/N) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg050 -------------------------------------------------------- At each prompt, enter a . At the prompt, "FILE SPECIFIERS", enter ".". Enter to all other questions. All system files will be restored to disk. Please note that once all files are restored to disk, the 8.5D Installation Procedure for Upgrade from 8.4D and Below message "AUTOMATIC COMPARE, CR TO CONTINUE" appears. This automatically rewinds the tape and begins the compare operation. This only occurs when the compare option is selected. When the compare is completed, enter a CTL-IV to return to the "SAVERESTORE" menu. 5.3.3.3. Installing the Configuration Record __________ ___ _____________ ______ The system model number has been included in the configuration record since release 8.5B. Therefore, it is necessary to install a new configuration record if you upgrade to 8.5D from a level below 8.5B. Until the following procedure is completed, the system will have a minimum configuration. Enter a TYPE I LOAD. Set your prefix to .SYSTEM.CONFIG. Before you load the new configuration record, rename the current configuration record on your system, using the RENAME utility, to temporarily preserve it for fall back purposes. (e.g. Add "OLD" in front of the name.) Using the SAVERESTORE utility, restore the new configuration record on tape onto your system. Execute the CONFIG.MGR utility. The CONFIG.MGR utility allows the user to update the system configuration record by installing a new configuration file. This utility displays the current and new configuration record. When "Y" is answered to the prompt "Install Configuration:", the new configuration is copied from the file ".SYSTEM.CONFIG.I(serial number)", to the special system area on disk. The new configuration takes effect at the next system load. For further details on the use of the CONFIG.MGR utility, see section 3.2.1. The configuration record file name is derived from the system serial number by changing the leading "8" to an "I" and adding the prefix ".SYSTEM.CONFIG.". EXAMPLE: .SYSTEM.CONFIG.I1030114 for SSN 810-30114 This file should be backed up by the user, in case reinstallation should become necessary. 5.3.3.4. Conversion of Files __________ __ _____ If doing tape to disk conversion see section 5.3.3.4.1. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg051 If doing disk to disk conversion see section 5.3.3.4.2. 8.5D Installation Procedure for Upgrade from 8.4D and Below 5.3.3.4.1. Tape to Disk Conversion ____ __ ____ __________ Mount the first tape to restore, enter the SAVERESTORE utility, and select option #2. A screen as in figure 5-3 will appear. Answer all prompts as in the figure. Make sure that you direct the output to a printer. This will provide you with a "history" of the restore operation. Each file is converted to the new file format as it is restored. The conversion to the new file format will be entirely invisible except for a pause at the completion of restoring a file. This pause, which can last a few seconds to a few hours depending on file size, indicates the file is being converted to the new file format. Occasionally the message "...CONVERTING FILE TO NFS..." will appear as a visual indicator of file conversion. System files from the previous release need not be restored. However, to preserve all system parameters and configurations, the 'SYSDATA' and '.SYSTEM.CONFIG.' node must be restored from the backup tapes. Tapes made on a releases of 8.4D and below cannot be compared when restored to the new file system. After all files have been restored, go to section 5.3.3.4.3. 5.3.3.4.2. Disk to Disk Conversion ____ __ ____ __________ The utility NFSCONVERT is used to convert files from the old format to the new file format. The destination disk must be in 8.5 format as described in section 5.3.3.1.2. The source disk must be in 8.4D format. When using disk to disk conversion, only one family may be converted per terminal. You cannot start NFSCONVERT on two terminals converting different parts of the same family. You can convert different families at the same time. As in the tape to disk conversion, the node '.SYSDATA.' and '.SYSTEM.CONFIG.' must be converted to preserve system parameters and configurations. See section 3.2.4 for operation of the NFSCONVERT utility. 5.3.3.4.3. Check Files _____ _____ Once all files have been converted, DISKANALYZER should be used to validate all files for each family. DISKANALYZER can be used in a TYPE II load or a TYPE I load. See the section on DISKANALYZER in the 8.5A software announcement for details of operation. Once all files have been validated, enter a TYPE I load, (if you have not already done so). 8.5D Installation Procedure for Upgrade from 8.4D and Below 5.3.4. UPDATING OTHER O.S. SLOTS ________ _____ ____ _____ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg052 The slots 1, 2, and 3 need to be updated. Set the prefix to the .INST. node by keying in the following in command mode: !PREFIX .R5D24.INST. With the inclusion of support for 7000 Series Systems, there are two versions of REMIDI, BV5C0101 and BVM5C0101. Version BV5C0101 includes all the micro-diagnostics except MPC controller micro-diagnostics. It is placed in WCS slot 2 and is used for testing on both the 7000 and 8000 Series Systems. Version BVM5C0101 consists of micro-diagnostics for the MPC controller only, and is placed in WCS slot 3 on 7000 Series Systems. 5.3.4.1. UPDATING SLOT ONE (1) ________ ____ ___ ___ A copy of the primary operating system will be put in slot 1. UPDATE.OS IMAGE FILE NAME: .R5D24.INST.OS1.UV050424001 OS SLOT: (displayed) OS VERSION: (displayed) IMAGE FORMAT: (displayed) NEW WCS SLOT: 1 UPDATE WHICH DISK: (0=nn/1=nn/B=BOTH/Q=QUIT)___ DONE ! UPDATE COMPLETE Next, WCS slot 1 is updated with a copy of the same WCS that was installed in slot 0. UPDATE.WCS ENTER WCS SLOT [0..3]: Enter '1' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R5D24.INST.WCS.B537 WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 5.3.4.2. UPDATING WCS SLOT TWO (2) ________ ___ ____ ___ ___ REMIDI version BV5C0101 will reside in this slot. 8.5D Installation Procedure for Upgrade from 8.4D and Below UPDATE.WCS ENTER WCS SLOT [0..3]: Enter '2' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE: (choose disk) WCS IMAGE FILE: .R5D24.INST.REMIDI.BV5C0101 WCS LEVEL OF WCS IMAGE FILE: (level displayed) UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETED! SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg053 5.3.4.3. UPDATING SLOT THREE (3) ________ ____ _____ ___ 5.3.4.3.1. Updating O.S. Slot Three ________ ____ ____ _____ The O.S. slot 3 will contain the O.S. for DEMON on both 7000 and 8000 Series Systems. UPDATE.OS IMAGE FILE NAME: .R5D24.INST.OS3.UV050400000 OS SLOT: (displayed) OS VERSION: (displayed) IMAGE FORMAT: (displayed) NEW WCS SLOT: Enter '0' or '1' on 7000 Series Systems to associate the WCS in either slot with load sector 3. Enter '3' on 8000 Series Systems. UPDATE WHICH DISK (0=nn/1=nn/B=BOTH/Q=QUIT):____ UPDATING DISK DONE! UPDATE IS NOW COMPLETE NOTE: On MPx 7000 Series Systems, the UPDATE.LD utility needs to be run to update the Load Directory. For further information on the use of UPDATE.LD, see section 3.4. 5.3.4.3.2. Updating WCS Slot Three (3) ________ ___ ____ _____ ___ 5.3.4.3.2.1. WCS Slot Three on 7000 Series Systems ___ ____ _____ __ ____ ______ _______ This slot will contain the micro-diagnostics for the MPC controller, REMIDI version BVM5C0101. After this slot has been updated, it will be necessary to change the Load Directory by running the utility UPDATE.LD. See section 3.4 for further information on REMIDI and running UPDATE.LD. UPDATE.WCS ENTER WCS SLOT [0..3]: Enter '3' AVAILABLE DISK UNITS ARE: (displayed) 8.5D Installation Procedure for Upgrade from 8.4D and Below DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R5D24.INST.REMIDI.BVM5C0101 WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 5.3.4.3.2.2. WCS Slot Three on 8000 Series Systems ___ ____ _____ __ ____ ______ _______ This slot will contain system WCS which is common to both the O.S. and DEMON. UPDATE.WCS SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg054 ENTER WCS SLOT [0..3]: Enter '3' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R5D24.INST.WCS.B537 WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 5.3.4.4. SLOT INFORMATION ____ ___________ Once all slots have been updated, use the utility OSINFO to display the slot information. The information should be simliar to figure 5-2. If disk 1 is a system disk also, repeat these steps beginning with step 5.2.2 Installation is now complete. 5.3.5. Update Terminal Configuration File ______ ________ _____________ ____ The terminal configuration file must be updated to the new 8.5 format. This update will allow all other devices to become accessible. The file is updated by entering TERM.CONFIG and choosing the update option. Enter PRIMARY as the file to change. Enter an existing ISDC and display one of the ISDC ports. Enter a MB-IV to exit the update without changing anything. The utility will say that the file has been modified and do you want to save it. Respond with YES. Now reload the system to allow the devices to become active. Installation is now complete. Figure 5-4. Operating System Information ______ ____ _________ ______ ___________ OPERATING SYSTEM INFORMATION ------------------------------------------------------------------ BOOT LEVEL : X.X.X.X LOAD SECTOR: 0 1 2 3 DISK 0 : 0/0 1/1 0/2 3/3 SERIAL # : XXX-XXXXX ------------------------------------------------------------------ OS NAME OS LEVEL DISK:SLOT WCS LEVEL ------------------------------------------------------------------ R 85D*24 860821 5.4.24.1 0:0 B 5.3.7 R 85D*24 860821 5.4.24.1 0:1 B 5.3.7 N/A 0:2 REMIDI B 5.1.1 DEMON 6/30/86 5.4.0.0 0:3 B 5.3.7 ------------------------------------------------------------------ NOTE: OSINFO on 7000 Series Systems will show the additional version of REMIDI IN WCS slot 3. 8.5D 8000 UPGRADE AND CONVERSION CHECKLIST SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg055 ____ ____ _______ ___ __________ _________ 1) Hardware levels => section 4 2) Validate files => section 5.3.2.2 A) DIR listings B) FINDLOSTSPACE Utility C) Delete unwanted EDITOR,SPOOL, and TEMP files 3) New file sizes => section 5.3.2.3 A) FILESIZE utility 4) Save files to tape => section 5.3.2.4 A) Large keyed files first 5) Update operating system => section 5.3.3.1 A) ALT-LOAD B) Options 1-4 C) Restore operating system files 6) File conversion A) Tape-to-disk => section 5.3.3.4.1 B) Disk-to-disk => section 5.3.3.4.2 7) Check file integrity => section 5.3.3.4.3 8) Complete installation A) Update slots => section 5.2.2 B) Update terminal configuration file => section 5.3.5 8.5D Installation Procedure for Upgrade from Releases Above 8.4D 5.4. 8000 UPGRADE FROM RELEASE LEVELS ABOVE 8.4D ____ _______ ____ _______ ______ _____ ____ If you are upgrading to 8.5D from release level 8.4D or below, go to section 5.3. If you are upgrading to 9.5D, go to section 5.5. 5.4.1. Saving Files to Tape ______ _____ __ ____ Current files must first be backed up to tape, using the standard tape utility, SAVERESTORE. When saving files to tape, send the output from the save process to the printer. These will provide a record of backup for each file. Also it is recommended that all tapes be compared to the files on the disk. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg056 5.4.2. Operating System Update _________ ______ ______ 5.4.2.1. Installing the O.S. __________ ___ ____ 5.4.2.1.1. ALT LOAD ___ ____ A) Insert the new release tape into the tape drive. B) Press the "ALTLOAD" button on the front panel. C) Enter the appropriate system disk (0 or 1) or if drives 0 and 1 are both system disks, enter "2" to update both disks. D) Enter a "0" to update WCS slot 0. E) Enter a "Y" to the prompt "Are you SURE you want to overwrite this WCS ? (Y/)". The system automatically updates the OS and WCS slot 0 on both disks, if selected. When this is complete, the system prompts "DONE - READY FOR NORMAL LOAD". Reload by pressing the LOAD button. 5.4.2.1.2. CHANGE INSTALLATION PARAMETERS ______ ____________ __________ Enter a TYPE 3 LOAD (Special Functions) and select option 2, "Change Installation Parameters". The following will be displayed: SYSTEM DISKS: (displayed) DRIVE NUMBER:_______ 8.5D Installation Procedure for Upgrade from Releases Above 8.4D PRIMARY PREFIX ? Enter (family).R5D24.SYS. Where (family) is the family where the operating system files reside. SECONDARY PREFIX ? Enter (family).R5D24.SYS. Where (family) is the family where the alternate operating system files reside. DEFAULT USER FAMILY NAME ?:________ Enter default user family SECURITY (E=ENABLED, D=DISABLED):___ FILE SYSTEM WRITE THROUGH? (E=ENABLED, D=DISABLED):___ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg057 WRITE THROUGH DEFAULT ON FILE CREATE (E=ENABLED, D=DISABLED):__ This parameter specifies what the default write through will be on a file created through a BASIC file create or through the CREATE utility. UPDATE DISK WITH INSTALLATION PARAMETERS? (Y/N)__ Display: PARAMETERS SUCCESSFULLY WRITTEN TO DISK Reload the system by pressing the LOAD button and enter a TYPE II load. 5.4.2.2. Restoring the O.S. _________ ___ ____ Enter SAVERESTORE in a TYPE II load and choose option #2 "RESTORE FILES FROM TAPE". The screen appears as in figure 5-3. At the prompt, "FILE SPECIFIERS", enter ".". Enter to all other questions. All system files will be restored to disk. Please note that once all files are restored to disk, the message "AUTOMATIC COMPARE, CR TO CONTINUE" appears. This automatically rewinds the tape and begins the compare operation. This only occurs when the compare option is 8.5D Installation Procedure for Upgrade from Releases Above 8.4D Figure 5-5. Restore Screen ______ ____ _______ ______ -------------------------------------------------------- RESTORE FILES TAPE SET.ID: DRIVE-NUM: REEL-NUM: PRIMARY PREFIX: (FAMILY).NODE. FILETYPE (D/P/CR=ALL) COMPARE (CR=Y/N) DATE (MM/DD/YY) TIME (HH:MM) OUTPUT DEVICE (CR=VDT) DELETE EXISTING FILES (CR=Y) VERIFY (Y/CR=N) ENTRIES CORRECT (Y/N) -------------------------------------------------------- At each prompt, enter a . selected. When the compare is completed, enter a CTL-IV to return to the "SAVERESTORE" menu. 5.4.2.3. Installing the Configuration Record SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg058 __________ ___ _____________ ______ The system model number has been included in the configuration record since release 8.5B. Therefore, it is necessary to install a new configuration record if you upgrade to 8.5D from a level below 8.5B. Until the following procedure is completed, the system will have a minimum configuration. Enter a TYPE I LOAD. Set your prefix to .SYSTEM.CONFIG. Before you load the new configuration record, rename the current configuration record on your system, using the RENAME utility, to temporarily preserve it for fall back purposes. (e.g. Add "OLD" in front of the name.) Using the SAVERESTORE utility, restore the new configuration record on tape onto your system. Execute the CONFIG.MGR utility. The CONFIG.MGR utility allows the user to update the system configuration record by installing a new configuration file. This utility displays the current and new configuration record. When "Y" is answered to the prompt "Install Configuration:", the new configuration is copied from the file ".SYSTEM.CONFIG.I(serial 8.5D Installation Procedure for Upgrade from Releases Above 8.4D number)", to the special system area on disk. The new configuration takes effect at the next system load. For further details on the use of the CONFIG.MGR utility, see section 3.2.1. The configuration record file name is derived from the system serial number by changing the leading "8" to an "I" and adding the prefix ".SYSTEM.CONFIG.". EXAMPLE: .SYSTEM.CONFIG.I1030114 for SSN 810-30114 This file should be backed up by the user, in case reinstallation should become necessary. 5.4.3. UPDATING OTHER O.S. SLOTS ________ _____ ____ _____ The slots 1, 2, and 3 need to be updated. Set the prefix to the .INST. node by keying in the following in command mode: !PREFIX .R5D24.INST. With the inclusion of support for 7000 Series Systems, there are two versions of REMIDI, BV5C0101 and BVM5C0101. Version BV5C0101 includes all the micro-diagnostics except MPC controller micro-diagnostics. It is placed in WCS slot 2 and is used for testing on both the 7000 and 8000 Series Systems. Version BVM5C0101 consists of micro-diagnostics for the MPC controller only, and is placed in WCS slot 3 on 7000 Series Systems. 5.4.3.1. UPDATING SLOT ONE (1) ________ ____ ___ ___ A copy of the primary operating system will be put in slot 1. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg059 UPDATE.OS IMAGE FILE NAME: .R5D24.INST.OS1.UV050424001 OS SLOT: (displayed) OS VERSION: (displayed) IMAGE FORMAT: (displayed) NEW WCS SLOT: 1 UPDATE WHICH DISK: (0=nn/1=nn/B=BOTH/Q=QUIT)___ DONE ! UPDATE COMPLETE Next, WCS slot 1 is updated with a copy of the same WCS that was installed in slot 0. UPDATE.WCS 8.5D Installation Procedure for Upgrade from Releases Above 8.4D ENTER WCS SLOT [0..3]: Enter '1' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R5D24.INST.WCS.B537 WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 5.4.3.2. UPDATING WCS SLOT TWO (2) ________ ___ ____ ___ ___ REMIDI version BV5C0101 will reside in this slot. UPDATE.WCS ENTER WCS SLOT [0..3]: Enter '2' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE: (choose disk) WCS IMAGE FILE: .R5D24.INST.REMIDI.BV5C0101 WCS LEVEL OF WCS IMAGE FILE: (level displayed) UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETED! 5.4.3.3. UPDATING SLOT THREE (3) ________ ____ _____ ___ 5.4.3.3.1. Updating O.S. Slot Three ________ ____ ____ _____ The O.S. slot 3 will contain the O.S. for DEMON on both 7000 and 8000 Series Systems. UPDATE.OS IMAGE FILE NAME: .R5D24.INST.OS3.UV050400000 OS SLOT: (displayed) OS VERSION: (displayed) IMAGE FORMAT: (displayed) NEW WCS SLOT: Enter '0' or '1' on 7000 Series Systems to associate the WCS in either slot with load sector 3. Enter '3' on 8000 Series Systems. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg060 UPDATE WHICH DISK (0=nn/1=nn/B=BOTH/Q=QUIT):____ UPDATING DISK DONE! UPDATE IS NOW COMPLETE NOTE: On MPx 7000 Series Systems, the UPDATE.LD utility needs to be run to update the Load Directory. For further information on the use of UPDATE.LD, see section 3.4. 8.5D Installation Procedure for Upgrade from Releases Above 8.4D 5.4.3.3.2. Updating WCS Slot Three (3) ________ ___ ____ _____ ___ 5.4.3.3.2.1. WCS Slot Three on 7000 Series Systems ___ ____ _____ __ ____ ______ _______ This slot will contain the micro-diagnostics for the MPC controller, REMIDI version BVM5C0101. After this slot has been updated, it will be necessary to change the Load Directory by running the utility UPDATE.LD. See section 3.4 for further information on REMIDI and running UPDATE.LD. UPDATE.WCS ENTER WCS SLOT [0..3]: Enter '3' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R5D24.INST.REMIDI.BVM5C0101 WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 5.4.3.3.2.2. WCS Slot Three on 8000 Series Systems ___ ____ _____ __ ____ ______ _______ This slot will contain system WCS which is common to both the O.S. and DEMON. UPDATE.WCS ENTER WCS SLOT [0..3]: Enter '3' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R5D24.INST.WCS.B537 WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 5.4.3.4. SLOT INFORMATION ____ ___________ Once all slots have been updated, use the utility OSINFO to display the slot information. The information should be simliar to figure 5-2. If disk 1 is a system disk also, repeat these steps beginning with step 5.2.2 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg061 Installation is now complete. Figure 5-6. Operating System Information ______ ____ _________ ______ ___________ OPERATING SYSTEM INFORMATION ------------------------------------------------------------------ BOOT LEVEL : X.X.X.X LOAD SECTOR: 0 1 2 3 DISK 0 : 0/0 1/1 0/2 3/3 SERIAL # : XXX-XXXXX ------------------------------------------------------------------ OS NAME OS LEVEL DISK:SLOT WCS LEVEL ------------------------------------------------------------------ R 85D*24 860821 5.4.24.1 0:0 B 5.3.7 R 85D*24 860821 5.4.24.1 0:1 B 5.3.7 N/A 0:2 REMIDI B 5.1.1 DEMON 6/30/86 5.4.0.0 0:3 B 5.3.7 ------------------------------------------------------------------ NOTE: OSINFO on 7000 Series Systems will show the additional version of REMIDI IN WCS slot 3. Installation Procedure for Upgrade to MPx 9000 and 9500 Series Systems 5.5. UPGRADING TO 9.5D AND THE MPX 9000 AND 9500 SERIES _________ __ ____ ___ ___ ___ ____ ___ ____ ______ 5.5.1. SPECIAL CONSIDERATIONS _______ ______________ A presite survey is required before upgrading to an MPx 9000 or 9500. (See Field Bulletin #161A). A new configuration record is required when upgrading to a 9000 or 9500. A new configuration record is not necessary when upgrading to 9.5D from 9.5C. It is required that systems being upgraded to 9.5D run on a release level that supports the new File System (any level above 8.4D) for at least one week prior to upgrade. It is recommended that systems being upgraded to 9.5D run on 8.5D prior to upgrade. When it is established that the system is running smoothly on the software at the end of this period, upgrade to 9.5D may then proceed. 5.5.2. PRINTING OUT THE TERMINAL CONFIGURATION RECORD ________ ___ ___ ________ _____________ ______ Skip this section if your are upgrading to 9.5D from 9.5C. When upgrading from the MPx 8000 to the MPx 9000 or 9500, It is necessary to reference the 8.5 terminal configuration in order to properly re-address the 9000 and 9500 controllers. Therefore, it is necessary to print out a copy of the terminal configuration record before upgrading. 1. Enter the TERM.CONFIG utility. 2. Select option 2, "DISPLAY A CONFIGURATION FILE" SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg062 3. When the following screen is displayed, enter these responses to the prompts: CONFIGURATION FILE: P OUTPUT DEVICE: DETAILED REPORT: Y ENTRIES CORRECT: Y The terminal configuration record should now be printed. 5.5.3. SAVING FILES TO TAPE ______ _____ __ ____ Current files must first be backed up to tape, using the standard tape utility, SAVERESTORE. When saving files to tape, send the output from the save process to the printer. This will provide a record of backup for each file. Also it is recommended that all tapes be compared to the files on the disk. Installation Procedure for Upgrade to MPx 9000 and 9500 Series Systems 5.5.4. OPERATING SYSTEM UPDATE _________ ______ ______ 5.5.4.1. ALT LOAD ___ ____ A) Insert the new release tape into the tape drive. B) Press the "ALTLOAD" button on the front panel. C) Enter the appropriate system disk (0 or 1) or if drives 0 and 1 are both system disks, enter "2" to update both disks. D) Enter a "0" to update WCS slot 0. E) Enter a "Y" to the prompt "Are you SURE you want to overwrite this WCS ? (Y/)". The system automatically updates the OS and WCS slot 0 on both disks, if selected. When this is complete, the system prompts "DONE - READY FOR NORMAL LOAD". Load the 9.5D O.S. from slot 0 by setting switch 3 to 'off' and pressing the LOAD switch. 5.5.4.2. TYPE 3 LOAD (SPECIAL FUNCTIONS) ____ _ ____ ________ __________ 5.5.4.2.1. Updating Installation Parameters ________ ____________ __________ Enter a TYPE 3 LOAD (Special Functions) and select option 2, "Update Installation Parameters". The following will be displayed: SYSTEM DISKS: (displayed) DRIVE NUMBER:_______ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg063 PRIMARY PREFIX ? Enter (family).R5D24.SYS. Where (family) is the family where the operating system files reside. SECONDARY PREFIX ? Enter (family).R5D24.SYS. Where (family) is the family where the alternate operating system files reside. Installation Procedure for Upgrade to MPx 9000 and 9500 Series Systems DEFAULT USER FAMILY NAME ?:________ Enter default user family SECURITY (E=ENABLED, D=DISABLED):___ FILE SYSTEM WRITE THROUGH? (E=ENABLED, D=DISABLED):___ WRITE THROUGH DEFAULT ON FILE CREATE (E=ENABLED, D=DISABLED):__ This parameter specifies what the default write through will be on a file created through a BASIC file create or through the CREATE utility. (Please see Field Bulletin #212.) UPDATE DISK WITH INSTALLATION PARAMETERS? (Y/N)__ Display: PARAMETERS SUCCESSFULLY WRITTEN TO DISK Reload the system by pressing the LOAD button and enter a TYPE II load. 5.5.4.2.2. Sizing the Dump Area (Change Volume Information) ______ ___ ____ ____ _______ ______ ____________ At this point it is necessary to enter a TYPE 3 LOAD, Option 1, "Change Volume Information" to determine whether the Dump Area is large enough. Presently, on all MPx release levels, the operating system computes the size of the Dump Area using information derived from the currently installed configuration record in conjunction with a survey of the installed hardware at the time of the last system load. This method has two major disadvantages: 1. If a disk has no installed configuration record, the Dump Area size is computed on a minimum configuration, regardless of what hardware is installed in the system. 2. If additional main memory and qHBred memory controllers are installed in the system, and this exceeds the limits set by the currently installed configuration record, this new hardware will not be included when computing the size of the Dump Area. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg064 The solution to this problem is for the operating system to actually check the installed hardware when computing the size of the Dump Area, and this will be done in releases 8.6A/9.6A. In the meantime, if either one of the above two situations apply to your system, it will be necessary to compute the size of the Dump Area by determining exactly what main memory and Installation Procedure for Upgrade to MPx 9000 and 9500 Series Systems shared memory controllers are installed in the system, and adding up the area required for each. The total should be input in Option 1 (Change Volume Information) of a TYPE 3 LOAD after the prompt "SIZE OF DUMP AREA (FOR SYSTEM DISK ONLY):". All other numbers on the Option 1 screen that refer to the size of the Dump Area should be ignored. Listed below are the main memory and shared memory controllers and the values to be used when computing the size of the Dump Area: 1. Each megabyte of main memory (903349, 903516)...1024 (x 1024 bytes) 2. Each 4-Way controller (903374).................. 64 (x 1024 bytes) 3. Each 8-Way controller (903383).................. 64 (x 1024 bytes) 4. Each 16-Way controller (903437.................. 128 (x 1024 bytes) 5. Each IMLC controller (903381, 903534)........... 64 (x 1024 bytes) 6. Each LAN controller............................. 64 (x 1024 bytes) 7. Each BMTC controller (903413)................... 128 (x 1024 bytes) EXAMPLE: A system has 8 MB of main memory, 1 4-Way controller, 2 16-Way controllers, 1 IMLC, and 1 BMTC. Compute the size of the Dump Area as follows: 8 MB main memory (8 x 1024) = 8192 (x 1024 bytes) 1 4-Way controller = 64 (x 1024 bytes) 2 16-Way controllers (2 x 128) = 256 (x 1024 bytes) 1 IMLC = 64 (x 1024 bytes) 1 BMTC = +128 (x 1024 bytes) ---- Total 8704 (x 1024 bytes) "SIZE OF DUMP AREA (FOR SYSTEM DISKS ONLY):" 8704 (x 1024 bytes) Correct sizing of the Dump Area is especially critical on MPx 9000 and 9500 systems, because dumps to tape are not possible on these systems. This is because the BMTC, which is required to control tape operations on MPx 9000 and 9500 systems, is a shared memory controller. When sizing the Dump Area, you may want to round up to the next megabyte or add an extra megabyte or two for future expansion. If it becomes necessary to enlarge the Dump Area, you must do a complete back up (which you already should have), reinitialize the system disks (options 1-4 in a TYPE 3 LOAD), and do a restore from the back up in a TYPE 2 LOAD. 5.5.4.3. Restoring the O.S. Files _________ ___ ____ _____ Enter SAVERESTORE in a TYPE II load and choose option #2 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg065 Installation Procedure for Upgrade to MPx 9000 and 9500 Series Systems "RESTORE FILES FROM TAPE". The screen appears as in figure 5-3. Figure 5-7. Restore Screen ______ ____ _______ ______ -------------------------------------------------------- RESTORE FILES TAPE SET.ID: DRIVE-NUM: REEL-NUM: PRIMARY PREFIX: (FAMILY).NODE. FILETYPE (D/P/CR=ALL) COMPARE (CR=Y/N) DATE (MM/DD/YY) TIME (HH:MM) OUTPUT DEVICE (CR=VDT) DELETE EXISTING FILES (CR=Y) VERIFY (Y/CR=N) ENTRIES CORRECT (Y/N) -------------------------------------------------------- At each prompt, enter a . At the prompt, "FILE SPECIFIERS", enter ".". Enter to all other questions. This will restore all files from the release tape to disk. Please note that once all files are restored to disk, the message "AUTOMATIC COMPARE, CR TO CONTINUE" appears. This automatically rewinds the tape and begins the compare operation. This only occurs when the compare option is selected. When the compare is completed, enter a CTL-IV to return to the "SAVERESTORE" menu. 5.5.4.4. Installing the Configuration Record __________ ___ _____________ ______ It is necessary to install a new configuration record when upgrading to 9.5D from 8.4 and 8.5 release levels. Skip this section if you are upgrading from release level 9.5C. Until the following procedure is completed, the system will have a minimum configuration. Enter a TYPE I LOAD. Set your prefix to .SYSTEM.CONFIG. Before you load the new configuration record, rename the current configuration record on your system, using the RENAME Installation Procedure for Upgrade to MPx 9000 and 9500 Series Systems utility, to temporarily preserve it for fall back purposes. (e.g. ".OLDCONFIG.") Using the SAVERESTORE utility, restore the new configuration record on tape onto your system. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg066 Execute the INSTALL.CONFIG utility. The INSTALL.CONFIG utility allows the user to update the system configuration record by installing a new configuration file. This utility displays the current and new configuration record. When "Y" is answered to the prompt "Install Configuration:", the new configuration is copied from the file ".SYSTEM.CONFIG.I(serial number)", to the special system area on disk. The new configuration takes effect at the next system load. The configuration record file name is derived from the system serial number by changing the leading "8" to an "I" and adding the prefix ".SYSTEM.CONFIG.". EXAMPLE: .SYSTEM.CONFIG.I1030114 for SSN 810-30114 This file should be backed up by the user, in case reinstallation should become necessary. 5.5.5. UPDATING OTHER O.S. SLOTS ________ _____ ____ _____ The slots 1, 2, and 3 need to be updated. Set the prefix to the .INST. node by keying in the following in command mode: !PREFIX .R5D24.INST. 5.5.5.1. Updating Slot One (1) ________ ____ ___ ___ A copy of the 9.5D operating system will be put in O.S. slot 1. UPDATE.OS IMAGE FILE NAME: .R5D24.INST.OS1.UV050424001 OS SLOT: (displayed) OS VERSION: (displayed) IMAGE FORMAT: (displayed) NEW WCS SLOT: 1 UPDATE WHICH DISK: (0=nn/1=nn/B=BOTH/Q=QUIT)___ DONE ! UPDATE COMPLETE Next, WCS slot 1 is updated with a copy of the 9.5D WCS. UPDATE.WCS Installation Procedure for Upgrade to MPx 9000 and 9500 Series Systems ENTER WCS SLOT [0..3]: Enter '1' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R5D24.INST.WCS.A570 WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 5.5.5.2. Updating WCS Slot Two (2) ________ ___ ____ ___ ___ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg067 The first section of the 9000/9500 version of REMIDI will reside in this slot. NOTE: Running UPDATE.OS automatically updates the load sectors for the disk. However, running UPDATE.WCS does not. (The Load Sectors are displayed at the top of the OSINFO screen.) It is therefore necessary to run UPDATE.LD for REMIDI on newly initialized systems packs, or whenever question marks ("?/?") appear in Load Sector 2 on the OSINFO screen. See section 3.4.1.2 for further information on REMIDI and running UPDATE.LD. UPDATE.WCS ENTER WCS SLOT [0..3]: Enter '2' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE: (choose disk) WCS IMAGE FILE: .R5D24.INST.REMIDI.AVA5C1401 WCS LEVEL OF WCS IMAGE FILE: (level displayed) UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETED! 5.5.5.3. Updating Slot Three (3) ________ ____ _____ ___ 5.5.5.3.1. Updating O.S. Slot Three (3) ________ ____ ____ _____ ___ O.S. slot 3 will contain the O.S. for DEMON. UPDATE.OS IMAGE FILE NAME: .R5D24.INST.OS3.UV050400000 OS SLOT: (displayed) OS VERSION: (displayed) IMAGE FORMAT: (displayed) NEW WCS SLOT: Enter '0' to associate DEMON's O.S. with the WCS in slot 0. (DEMON and the 9.5D O.S. share the same WCS. Installation Procedure for Upgrade to MPx 9000 and 9500 Series Systems UPDATE WHICH DISK (0=nn/1=nn/B=BOTH/Q=QUIT):____ UPDATING DISK DONE! UPDATE IS NOW COMPLETE 5.5.5.3.2. Changing the Load Sector for Slot Three (3) ________ ___ ____ ______ ___ ____ _____ ___ Because the second section of the 9000/9500 version of REMIDI is in WCS slot 3, the Load Directory must be changed to point to another WCS slot for DEMON. The 9.5D O.S. and DEMON share the same WCS code, therefore, we can point to the WCS slot used by the 9.5D O.S. Update the Load Directory for DEMON by using the UPDATE.LD utility. See section 3.4.1.2 for information on how to run UPDATE.LD. 5.5.5.3.3. Updating WCS Slot Three (3) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg068 ________ ___ ____ _____ ___ This slot will contain the second section of the 9000/9500 version of REMIDI. UPDATE.WCS ENTER WCS SLOT [0..3]: Enter '3' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R5D24.INST.REMIDI.AVC5C1401 WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 5.5.5.4. Slot Information ____ ___________ Once all slots have been updated, use the utility OSINFO to display the slot information. The information should be simliar to figure 5-2. Installation Procedure for Upgrade to MPx 9000 and 9500 Series Systems Figure 5-8. Operating System Information ______ ____ _________ ______ ___________ OPERATING SYSTEM INFORMATION ------------------------------------------------------------------ BOOT LEVEL : X.X.X.X LOAD SECTOR: 0 1 2 3 DISK 0 : 0/0 1/1 0/2 3/1 SERIAL # : XXX-XXXXX ------------------------------------------------------------------ OS NAME OS LEVEL DISK:SLOT WCS LEVEL ------------------------------------------------------------------ R 5D*24 860821 5.4.24.1 0:0 A 5.7.0 R 5D*24 860821 5.4.24.1 0:1 A 5.7.0 N/A 0:2 REMIDI A 5.14.1 DEMON 6/30/86 5.4.0.0 0:3 REMIDI A 5.14.1 ------------------------------------------------------------------ The O.S. and WCS slots on all other system disks on the system must also be updated. Installation is now complete. 6. RELATED DOCUMENTATION _______ _____________ 2770/2780/3770/3780 Batch Emulator User Guide M 5080C 3270 Pass-Through Reference Manual M 5091A BOSS/VS Business BASIC Reference Manual M 5092C BOSS/VS User Guide M 5098E BOSS/VS Utilities User Guide M 5102D SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg069 3270 Emulation Package Operator Guide for MAI 8000 Series M 5129 MAI 8000 Terminal Asynchronous Communication Facility Reference Manual M 5130A File Transfer Facility User Reference Manual M 6352 BOSS/VS Installation Guide M 5138C MPx System Installation Planning Guide M 5146E BOSS/VS Special Purpose Utilities User Guide M 5151 BOSS/VS System Support Manual M 5152 Intersystem Transport Package User Guide M 6354D MAI 8000 Series COBOL Reference Manual M 5174 MAI 8000 Series COBOL User Guide M 5175 BOSS/VS File Conversion User Guide M 5185A Note: BOSS/VS User Guide (M 5098E) includes the MAI 8000 Series Operator Guide. BOSS/VS Utilities User Guide (M 5102D) includes the BOSS/VS System Management Utilities User Guide. INDEX _____ NFSCONVERT DELEXIST: 31 NFSCONVERT Destination: 30 NFSCONVERT End Specifier: 30 NFSCONVERT ENTRIES CORRECT: 34 NFSCONVERT OUTPUT DEVICE: 33 NFSCONVERT PAUSE ON ERRORS: 32 NFSCONVERT Primary Prefix: 28 NFSCONVERT Start Specifier: 29 NFSCONVERT TYPE: 32 NFSCONVERT VERIFY: 31 ORIGINATOR: MBF SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB030 Pg070 FIB 00031 10/01/87 *** Release 8.5E/9.5E Software Announcement *** 8.5E/9.5E Software Announcement MAI Basic Four, Inc. is pleased to announce that the new software release, 8.5E/9.5E, is now available. The 8.5E release is the required release for MPx 7000 and 8000 Series Systems on 8.5. The 9.5E release is the required release for MPx 9000, 9100, and 9500 Series Systems. ************************************************** * * * PLEASE READ THE INSTALLATION INSTRUCTIONS * * BEFORE ATTEMPTING INSTALLATION OR UPGRADE. * * * * A NEW CONFIGURATION RECORD IS NOT REQUIRED * * WHEN UPGRADING TO 8.5E FROM LEVEL 8.5B AND * * ABOVE. A NEW CONFIGURATION RECORD IS REQUIRED * * WHEN UPGRADING TO 8.5E FROM LEVELS BELOW 8.5B. * * * * A NEW CONFIGURATION RECORD IS NOT REQUIRED * * WHEN UPGRADING TO 9.5E FROM A PRIOR 9.5 * * RELEASE. A NEW CONFIGURATION RECORD IS * * REQUIRED WHEN UPGRADING TO AN MPX 9000, 9100, * * OR 9500 FROM AN MPX 8000. * * * * IT IS REQUIRED THAT 8000 SYSTEMS BEING * * UPGRADED TO 9.5E RUN ON RELEASE 8.4E OR AN 8.5 * * RELEASE FOR A MINIMUM OF ONE WEEK PRIOR TO * * UPGRADE. IT IS RECOMMENDED THAT 8000 SYSTEMS * * BEING UPGRADED TO 9.5E RUN ON 8.5E PRIOR TO * * UPGRADE. 9.5 SYSTEMS SHOULD UPGRADE DIRECTLY * * TO 9.5E. * * * * WHEN UPGRADING TO 8.5E/9.5E FROM RELEASES * * PRIOR TO 8.5C/9.5C, AN ALT LOAD MUST BE DONE * * BEFORE THE O.S. FILES ARE RESTORED. THIS IS * * BECAUSE CERTAIN FILES WILL NOT RESTORE * * (INCLUDING THE DRIVERS FOR THE ISDC * * CONTROLLERS) WHEN ON RELEASES PRIOR TO * * 8.5C/9.5C. * * * * AS OF RELEASE 8.5D/9.5D, THE "INSTALL.CONFIG" * * UTILITY NO LONGER EXISTS. IT HAS BEEN REPLACED * * BY THE "CONFIG.MGR" UTILITY. * * * ************************************************** Copyright 1986 by MAI Basic Four, Inc. All rights reserved. C O N T E N T S _ _ _ _ _ _ _ _ 1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . 2 2 HISTORY . . . . . . . . . . . . . . . . . . . . . . . . 4 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg001 3 CONFIGURATIONS . . . . . . . . . . . . . . . . . . . . . 7 3.1 CONFIGURATIONS FOR MPX 7000 AND 8000 SERIES SYSTEMS . 7 3.2 CONFIGURATIONS FOR MPX 9000, 9100, 9500 SERIES SYSTEMS 8 3.2.1 Configurations for MPx 9000 and 9100 Series Systems 8 3.2.2 Configurations for MPx 9500 Series Systems . . . . . 9 4 GENERAL INFORMATION . . . . . . . . . . . . . . . . . . 10 4.1 SOFTWARE ANNOUNCEMENT . . . . . . . . . . . . . . . . 10 5 DIAGNOSTICS . . . . . . . . . . . . . . . . . . . . . . 11 6 HARDWARE . . . . . . . . . . . . . . . . . . . . . . . . 12 6.1 LARLS FOR PCBAS FOR MPX 7000 AND 8000 SERIES SYSTEMS . 12 6.2 LARLS FOR PCBAS FOR MPX 9000, 9100 AND 9500 SERIES SYS 12 6.3 PARALLEL DMP DEVICE VARIANCE CONFIGURATION . . . . . . 13 6.3.1 MPx 7000 and 8000 Series Systems . . . . . . . . . . 13 6.3.2 MPx 9000 and 9500 Series Systems . . . . . . . . . . 13 7 INSTALLATION . . . . . . . . . . . . . . . . . . . . . . 15 7.1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . 15 7.2 NEW INSTALLATION . . . . . . . . . . . . . . . . . . . 15 7.2.1 Installing the O.S. . . . . . . . . . . . . . . . . 15 7.2.1.1 ALT LOAD . . . . . . . . . . . . . . . . . . . . . 15 7.2.1.2 ENTER A TYPE 3 LOAD (SPECIAL FUNCTIONS) . . . . . 15 7.2.1.2.1 OPTION 1 (CHANGE VOLUME INFORMATION) . . . . . . 16 7.2.1.2.2 OPTION 2 (CHANGE INSTALLATION PARAMETERS) . . . 16 7.2.1.2.3 OPTION 3 (UPDATE FAMILY INFORMATION) . . . . . . 17 7.2.1.2.4 OPTION 4 (INITIALIZE FAMILY DIRECTORY) . . . . . 17 7.2.1.3 Restoring the O.S. . . . . . . . . . . . . . . . . 18 7.2.2 UPDATING OTHER O.S. SLOTS . . . . . . . . . . . . . 19 7.2.2.1 UPDATING SLOT ONE (1) . . . . . . . . . . . . . . 19 7.2.2.2 UPDATING WCS SLOT TWO (2) . . . . . . . . . . . . 19 7.2.2.3 UPDATING SLOT THREE (3) . . . . . . . . . . . . . 20 7.2.2.3.1 Updating O.S. Slot Three . . . . . . . . . . . . 20 7.2.2.3.2 Updating WCS Slot Three (3) . . . . . . . . . . 20 7.2.2.3.2.1 WCS Slot Three on 7000 Series Systems . . . . 20 7.2.2.3.2.2 WCS Slot Three on 8000 Series Systems . . . . 21 7.2.2.4 SLOT INFORMATION . . . . . . . . . . . . . . . . . 21 7.3 8000 UPGRADE FROM RELEASE LEVELS OF 8.4D AND BELOW . . 23 7.3.1 Introduction . . . . . . . . . . . . . . . . . . . . 23 7.3.2 Preliminary Evaluation . . . . . . . . . . . . . . . 24 7.3.2.1 Hardware Evaluation . . . . . . . . . . . . . . . 24 7.3.2.2 File Preparation . . . . . . . . . . . . . . . . . 24 7.3.2.3 8.5E Space Requirements . . . . . . . . . . . . . 25 7.3.2.4 Saving Files to Tape . . . . . . . . . . . . . . . 25 7.3.3 Operating System Update and File Conversion . . . . 26 7.3.3.1 Installing the O.S. . . . . . . . . . . . . . . . 26 7.3.3.1.1 ALT LOAD . . . . . . . . . . . . . . . . . . . . 26 7.3.3.1.2 ENTER A TYPE 3 LOAD (SPECIAL FUNCTIONS) . . . . 27 7.3.3.1.2.1 OPTION 1 (CHANGE VOLUME INFORMATION) . . . . . 27 7.3.3.1.2.2 OPTION 2 (CHANGE INSTALLATION PARAMETERS) . . 27 7.3.3.1.2.3 OPTION 3 (UPDATE FAMILY INFORMATION) . . . . . 28 7.3.3.1.2.4 OPTION 4 (INITIALIZE FAMILY DIRECTORY) . . . . 29 7.3.3.2 Restoring the O.S. . . . . . . . . . . . . . . . . 29 7.3.3.3 Installing the Configuration Record . . . . . . . 30 7.3.3.4 Conversion of Files . . . . . . . . . . . . . . . 30 7.3.3.4.1 Tape to Disk Conversion . . . . . . . . . . . . 31 7.3.3.4.2 Disk to Disk Conversion . . . . . . . . . . . . 31 7.3.3.4.3 Check Files . . . . . . . . . . . . . . . . . . 31 7.3.4 UPDATING OTHER O.S. SLOTS . . . . . . . . . . . . . 32 7.3.4.1 UPDATING SLOT ONE (1) . . . . . . . . . . . . . . 32 7.3.4.2 UPDATING WCS SLOT TWO (2) . . . . . . . . . . . . 32 7.3.4.3 UPDATING SLOT THREE (3) . . . . . . . . . . . . . 33 7.3.4.3.1 Updating O.S. Slot Three . . . . . . . . . . . . 33 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg002 7.3.4.3.2 Updating WCS Slot Three (3) . . . . . . . . . . 33 7.3.4.3.2.1 WCS Slot Three on 7000 Series Systems . . . . 33 7.3.4.3.2.2 WCS Slot Three on 8000 Series Systems . . . . 34 7.3.4.4 SLOT INFORMATION . . . . . . . . . . . . . . . . . 34 7.3.5 Update Terminal Configuration File . . . . . . . . . 34 7.4 8000 UPGRADE FROM RELEASE LEVELS ABOVE 8.4D . . . . . 37 7.4.1 Saving Files to Tape . . . . . . . . . . . . . . . . 37 7.4.2 Operating System Update . . . . . . . . . . . . . . 37 7.4.2.1 Installing the O.S. . . . . . . . . . . . . . . . 37 7.4.2.1.1 ALT LOAD . . . . . . . . . . . . . . . . . . . . 37 7.4.2.1.2 CHANGE INSTALLATION PARAMETERS . . . . . . . . . 37 7.4.2.2 Restoring the O.S. . . . . . . . . . . . . . . . . 38 7.4.2.3 Installing the Configuration Record . . . . . . . 39 7.4.3 UPDATING OTHER O.S. SLOTS . . . . . . . . . . . . . 40 7.4.3.1 UPDATING SLOT ONE (1) . . . . . . . . . . . . . . 40 7.4.3.2 UPDATING WCS SLOT TWO (2) . . . . . . . . . . . . 41 7.4.3.3 UPDATING SLOT THREE (3) . . . . . . . . . . . . . 41 7.4.3.3.1 Updating O.S. Slot Three . . . . . . . . . . . . 41 7.4.3.3.2 Updating WCS Slot Three (3) . . . . . . . . . . 42 7.4.3.3.2.1 WCS Slot Three on 7000 Series Systems . . . . 42 7.4.3.3.2.2 WCS Slot Three on 8000 Series Systems . . . . 42 7.4.3.4 SLOT INFORMATION . . . . . . . . . . . . . . . . . 42 7.5 UPGRADING TO 9.5E AND THE MPX 9000, 9100, AND 9500 . . 44 7.5.1 SPECIAL CONSIDERATIONS . . . . . . . . . . . . . . . 44 7.5.2 PRINTING OUT THE TERMINAL CONFIGURATION RECORD . . . 44 7.5.3 SAVING FILES TO TAPE . . . . . . . . . . . . . . . . 44 7.5.4 OPERATING SYSTEM UPDATE . . . . . . . . . . . . . . 45 7.5.4.1 ALT LOAD . . . . . . . . . . . . . . . . . . . . . 45 7.5.4.2 TYPE 3 LOAD (SPECIAL FUNCTIONS) . . . . . . . . . 45 7.5.4.2.1 Updating Installation Parameters . . . . . . . . 45 7.5.4.2.2 Sizing the Dump Area (Change Volume Information) 46 7.5.4.3 Restoring the O.S. Files . . . . . . . . . . . . . 47 7.5.4.4 Installing the Configuration Record . . . . . . . 48 7.5.5 UPDATING OTHER O.S. SLOTS . . . . . . . . . . . . . 49 7.5.5.1 Updating Slot One (1) . . . . . . . . . . . . . . 49 7.5.5.2 Updating WCS Slot Two (2) . . . . . . . . . . . . 50 7.5.5.3 Updating Slot Three (3) . . . . . . . . . . . . . 50 7.5.5.3.1 Updating O.S. Slot Three (3) . . . . . . . . . . 50 7.5.5.3.2 Changing the Load Sector for Slot Three (3) . . 51 7.5.5.3.3 Updating WCS Slot Three (3) . . . . . . . . . . 51 7.5.6 SLOT INFORMATION . . . . . . . . . . . . . . . . . . 51 8 RELATED DOCUMENTATION . . . . . . . . . . . . . . . . . 53 F I G U R E S _ _ _ _ _ _ _ Figure 7-1. Restore Screen . . . . . . . . . . . . . . . . 18 Figure 7-2. Operating System Information . . . . . . . . . 22 Figure 7-3. Restore Screen . . . . . . . . . . . . . . . . 29 Figure 7-4. Operating System Information . . . . . . . . . 35 Figure 7-5. Restore Screen . . . . . . . . . . . . . . . . 39 Figure 7-6. Operating System Information . . . . . . . . . 43 Figure 7-7. Restore Screen . . . . . . . . . . . . . . . . 48 Figure 7-8. Operating System Information . . . . . . . . . 52 1. INTRODUCTION ____________ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg003 The 8.5E/9.5E release contains all the features and enhancements of release 8.5D/9.5D, which are documented in the 8.5D/9.5D Software Announcement, #139. The 8.5E/9.5E release also contains fixes for the following system problems: UTILITIES COPY Utility The following problems only occurred when system security checking was ENABLED and File System Security Override was set to FALSE. 1. A diagnostic dump occurred when a non-owner of a file (who had READ-only access to the file) attempted to copy the file, specifying New Usage Rights (the default). The copy completed successfully, and then the system dumped with the fourtuple 28,255,0,0. This problem was introduced in 8.5D/9.5D. 2. If a user who had READ-only access to a file copied that file, the OWNER was not updated. 3. If a user who had READ-only access to a file specified to Delete Existing Destination File, the destination file was deleted. SAVERESTORE Utility Soft tape errors sometimes lead to incorrect sector calculation and returned a "Sector Count Mismatch" error. This problem occurred in both TYPE 1 and TYPE 2 Loads. UPDATE.RIGHTS Utility The following problems only occurred when system security checking was ENABLED and File System Security Override was set to FALSE. 1. A diagnostic dump occurred when a non-owner of a file attempted to change the Usage Rights of the file using the UPDATE.RIGHTS utility. The following messages were displayed: "Privilege insufficient" and "File rights not updated - ERROR". Then the system dumped with the fourtuple 28,255,0,0. This problem was introduced in 8.5D/9.5D. 2. A non-owner of a file was allowed to change the Usage Rights of a file. PAGE 2 BASIC 1. A user was allowed to REMOVE records from a direct file when he did not have WRITE access to the file. 2. When an attempt was made to READ or WRITE using a KEY that was longer than the defined key length, an ERROR 65 ("File Lacks Integrity") resulted. The fix for this problem is to return an ERROR 46 ("Invalid String Size") when a KEY is used which is longer than the key length specified for the file. The KEY that is too long will be truncated so that subsequent KEY or sequential READ operations will not fail with an ERROR SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg004 46, but will advance from the position defined by the truncated version of the KEY. 3. An attempt to WRITE with a DOM branch to a record that already existed on a keyed file bumped the key pointer to the next highest logical record. The fix is to not advance the current record pointer beyond the KEY value that was used on the WRITE that fails because of a duplicate KEY. FILE SYSTEM Direct file records could occupy record index positions beyond the maximum number of records minus 1. TYPE 3 LOAD Improper end-of-reel handling in a Type 3 Load Disk to Tape Image Copy sometimes caused incorrect sector calculation and returned the error "Sector Count Mismatch". PAGE 3 2. HISTORY _______ 8.5D/9.5D Obsolete Enhancements include: A new CONFIG.MGR utility for displaying and installing configuration records; Four Spooler fixes; DISKANALYZER reconstruction of serial files; Manual selection of different print modes on DMP printers; an optional enhanced ATP package. 8.5C/9.5C Obsolete Enhancements include: Expanded ERRORLOG reporting; Optimization of DataWord files; Number of logical channels increased to 64; Support for 8 bit character sets; DISKANALYZER reporting of required disk space for reconstruction. Mpx 9000 and 9500 systems only: 32 bit CPU; increased main memory; number of maximum devices increased to 164; new DMA controller for increased performance; enhanced CPU processing for faster arithmetic and logical operations; RSTACK cache; overall performance increase which is 2-3 times that of 7000/8000 systems; support for the faster 8-inch fixed disk. Mpx 9500 only: DATA and CODE caches for additional increased performance. 8.5B Obsolete In this release the system model number has been included in the configuration record, the COMPARE utility has been fixed so that it completely compares BASIC program files, and a new TBC AUTODIAL feature allows for definition and retrieval of multiple station lists. 8.5A Obsolete Enhancements include: Increased file system concurrency for greater throughput, support for 7000 series systems, proportional growth for DIRECT and SORT files, maximum number of open files increased to 512, maximum number of tasks SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg005 sharing same file increased to 512, file selectable write-through, DISKANALYZER also available in stand-alone mode, DISKANALYZER reconstruct of directory and available space files, maximum number of system printers increased to 99, system dumps written directly to tape, system support for the DMP serial printer, new terminal services error utility, DataWord printer queue enhancements, enhanced SAVERESTORE utility. 8.4E Acceptable This release contains all the features of the 8.5A/B/C/D releases, with the exception of the 8.5 performance PAGE 4 enhancements. 8.4D Obsolete Contained fixes for BASIC PRECISION, EXTTAPE, COBOL, and FILESIZE. 8.4C Obsolete Enhanced features included: Buffered Magnetic Tape Controller, 1/2" tape support, DEDICATE with expanded error reporting, new ISDC OS for 4-way, 8-way and 16-way, FILESIZE utility. 8.4B Obsolete Enhanced features include: 8 megabytes of main system memory, 16-port Asynchronous Controller, point-to-point file specification, QUIET mode for utilities, BASIC statement numbers up to 16000, Buffered Magnetic Tape Controller (BMTC) 1/4" tape support, S/10 Industry Standard Printer as slave printer. 8.4A Obsolete This release contained significant enhancements including 6 megabytes of main system memory, 96 devices, 84 total serial devices, disk to disk sequential family backup, enhanced hardware error log, system load progress monitor, and fast reconstruct utility. 8.2C Obsolete This release contained a WCS fix to support rezero fault clear, disk error recovery and a fix to the IMLC. 8.2B Obsolete This release contained all of the above features but was required for the 8000 Series systems due to a change in the WCS image for that hardware. 8.2A Obsolete This release contained significant enhancements providing NO EXTEND BASIC, 68 serial devices, math functions, X.25 Communications, DataWord 3.0. File System write through and SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg006 BULLETIN board availability. 8.1B Obsolete Enhanced features include: 31 logical units in BASIC, increase in file system cache from 208 to 225 unique files, PAGE 5 MULTIREELSR, family image backups, SAVERESTORE backup files having the Lack-of-Integrity bit set. Bugs were fixed in DISKANALYZER, SAVERESTORE and many of the system dumps. 8.1A Obsolete Introduction of the System 810 hardware and BOSS/VS software. PAGE 6 3. CONFIGURATIONS ______________ NOTE 1: Systems on software release levels 8.5 and 9.5 will require an extra 1/4 MB of memory for File System data structures, increasing the amount of memory required for system overhead from 1/2 MB on 8.4D to 3/4 MB on 8.5 and 9.5. NOTE 2: The number of "High Activity Tasks" is approximate and largely dependent on the application. The relative relationship of the numbers between configurations is more important than the actual numbers themselves. 3.1. CONFIGURATIONS FOR MPX 7000 AND 8000 SERIES SYSTEMS ______________ ___ ___ ____ ___ ____ ______ _______ The maximum configuration for the MPx 8000 Series Systems, Model 8030, is as follows: 116 Devices - A combination of 8-ways, 16-ways, the 4 ports on the MCS PCBA, MDTs and HVDTs up to a total of 116 devices are supported. 3 CPU sets 10 ISDCs: 16-ways (7 maximum) and/or 8-ways 32 Ghost tasks 24 High speed videos (HVDT) 8 Disk drives 4 Parallel printers 8 Megabytes of memory 2 Magnetic tape drives (MTR, MTS and/or MCS) 2 Intelligent Multi-Line Controllers (IMLC) 8 DataWord II terminals 4 TBC lines 64 3270 terminals 8 X.25 lines 2 Auto-Call Units (ACU) 99 Serial printers 99 System printers (spooler) 2 Buffered Magnetic Tape Controllers 27 High activity concurrent tasks Note: SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg007 There is a maximum of 9 memory assembly boards in any combination of 1/2 Mb, 1 Mb, 2 Mb, 4 Mb and BMTCs (a maximum of 3 boards per chassis). PAGE 7 Models 7010/8010 and 7020/8020 have the same configuration limits as Model 8030 above, with the following limitations: 7010/8010 7020/8020 1 CPU set 2 CPU sets 2-4 Mb memory 2-6 Mb memory 20 Devices 52 Devices 12 Concurrent tasks 20 Concurrent tasks (high activity) (high activity) 19 System printers 51 System printers 3.2. CONFIGURATIONS FOR MPX 9000, 9100, 9500 SERIES SYSTEMS ______________ ___ ___ _____ _____ ____ ______ _______ 3.2.1. Configurations for MPx 9000 and 9100 Series Systems ______________ ___ ___ ____ ___ ____ ______ _______ The maximum configuration for MPx 9000 and 9100 Series Systems, Models 9020 and 9120, is as follows: 116 Devices - A combination of 8-ways, 16-ways, the 4 ports on the MCS PCBA, MDTs and HVDTs up to a total of 116 devices are supported. 2 CPU sets with Evaluation Stack and Rstack Cache 10 ISDCs: 16-ways (6 maximum) and/or 8-ways (10 maximum) 32 Ghost tasks 24 High speed videos (HVDT) 12 8-inch fixed or 8 14-inch disk drives 8 Parallel printers 12 Megabytes of memory 2 Magnetic tape drives including MTR, MTS and/or MCS (1 maximum) 2 Intelligent Multi-Line Controllers (IMLC) 8 Dataword II terminals 4 TBC lines 64 3270 terminals 8 X.25 lines 2 Auto-Call Units (ACU) 99 Serial printers 99 System printers (spooler) 4 DMA controllers 2 Buffered Magnetic Tape Controllers 43 High activity concurrent tasks Models 9010 and 9110 have the same configuration limits as the 9020 and 9120 above, with the following exceptions: 1 CPU set with Evaluation Stack and Rstack Cache 68 Devices 10 ISDCs: 16-ways (4 maximum) and/or 8-ways (8 maximum) 67 Serial printers PAGE 8 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg008 75 System printers 26 High activity concurrent tasks 3.2.2. Configurations for MPx 9500 Series Systems ______________ ___ ___ ____ ______ _______ The maximum configuration for MPx 9500 Series Systems, Model 9530, is the same as the maximum configuration for the MPx 9000 Series Systems, Model 9020, with the following exceptions: 3 CPU sets with Evaluation Stack Rstack Cache Code Cache Data Cache 164 Devices 10 ISDCs: 16-ways (10 maximum) and/or 8-ways (10 maximum) 16 8-inch fixed or 8 14-inch disk drives 73 High activity concurrent tasks Models 9510 and 9520 have the same configuration limits as Model 9530 with the following exceptions: 9510 9520 1 CPU set 2 CPU sets (same caches as the 9530) (same caches as the 9530) 10 ISDCs: 16-way (4 maximum) 10 ISDCs: 16-way (6 maximum) 8-way (8 maximum) 8-way (10 maximum) 84 Devices 132 Devices 83 Serial printers 53 Concurrent tasks 91 System printers (high activity) 32 Concurrent tasks (high activity) PAGE 9 4. GENERAL INFORMATION _______ ___________ 4.1. SOFTWARE ANNOUNCEMENT ________ ____________ With this release, a copy of this software announcement exists as a serial file on the system, which allows the user to print a copy, if needed. This file can be submitted to a printer using the SUBMIT utility. The document file is named: (family).R5E25.INST.DOC.SA5E.TEXT PAGE 10 5. DIAGNOSTICS ___________ REMIDI (MPx 9000/9100/9500) New CPU Tests: Write to opcode cache when disabled test, ___ ___ _____ Forced parity test, Cache error reporting test, Backplane update using partial words test, ESTK up/down counter test. (ESTK up/down counter test is in the IDC test selection.) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg009 Screen Display Changes: I/O CPU identified, Memory and ______ _______ _______ Controller tests numbers cleared. DEMON (All Systems) The extended memory test "Test Address Lines" had been replaced with a much faster (5 min/MB) and improved test algorithm. This improved algorithm has also been added to the "Shared Memory Test" for the 4/8/16-Way, IMLC, BMTC, and LAN. Random data pattern test has been added to the "Buffer Memory Test" for the DMA and MPC controllers. Disk drive testing "SET DEFAULTS" menu now prompts for controller type (TDP, MPC or DMA). DCL (All systems) The Common I/O procedure has been modified to handle TR, TL, TP, and TS Read commands of VDT and HVDT tests correctly. For further information on these diagnostics and how to run them, refer to the Diagnostic User's Manual Document Writer, which is accessed by entering !DOCWRITER in command mode. PAGE 11 Hardware 6. HARDWARE ________ 6.1. LARLS FOR PCBAS FOR MPX 7000 AND 8000 SERIES SYSTEMS _____ ___ _____ ___ ___ ____ ___ ____ ______ _______ The Lowest Acceptable Revision Levels for 7000 and 8000 PCBAS are identical to those for 8.4B/C/D with the following exceptions: 1) MPC 903500 PCBA-Revision H 2) MPC 903549 PCBA-Revision B 3) BMTC 903413 PCBA-Revision R 4) ACS PCBA - 7000 systems only=> Y 8000 systems only=> L (T if BMTC) ** NOTE: Revision AA supports either the 7000 or 8000 series systems. Revision levels V-Y cannot be used on 8000 systems. Revision level Z cannot be used on 7000 systems. ** 5) 1/4" Micro Cartridge Streamer (No change from 8.5A) Revision 5 for main PWB Revision 9 for formatter PWB 6.2. LARLS FOR PCBAS FOR MPX 9000, 9100 AND 9500 SERIES SYSTEMS _____ ___ _____ ___ ___ _____ ____ ___ ____ ______ _______ The Lowest Acceptable Revision Levels for PCBAs for MPx 9000 and 9500 Series Systems are: SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg010 1) MCS 903374 PCBA-Revision L 2) AMS 903548 PCBA-Revision F 3) ESTK 903552 PCBA-Revision D 4) IDC 903550 PCBA-Revision J 5) DMA 903554 PCBA-Revision E 6) IMLC 903381 PCBA-Revision K IMLC 903534 PCBA-Revision D 7) BMTC 903413 PCBA-Revision R 8) Memory (1/2 and 1 MB) 903349 PCBA-Revision V 9) Memory (2 and 4 MB) 903516 PCBA-Revision E 10) Hi-speed video controller 903377 PCBA-Revision C 11) 8-Way 903383 PCBA-Revision A 12) 16-Way 903437 PCBA-Revision J 13) PPS II (Protected Power Supply) 907251 PCBA-Rev. E 14) PPS II 906418 PCBA-Revision D The following boards are NOT supported on the MPx 9000 and 9500 Series Systems: 1) 7000/8000 CPU set 2) TDP (Must be replaced by the BMTC for tape support) 3) MPC PAGE 12 Hardware 6.3. PARALLEL DMP DEVICE VARIANCE CONFIGURATION ________ ___ ______ ________ _____________ With the 8.5 releases, the parallel DMP device variance code needs to be changed. Previously, the DMP printer had the same code as a matrix printer. Changing the DMP printer to a new device variance is done by changing the switch settings on the appropriate controller board. 6.3.1. MPx 7000 and 8000 Series Systems ___ ____ ___ ____ ______ _______ The new DMP printer switch settings are: TDP CONTROLLER BOARD 903217 OR 903453 ___ __________ _____ ______ __ ______ Switch 4C Position # 8 7 6 _ _ _ O O C MPC CONTROLLER BOARD 903500 OR 903546 ___ __________ _____ ______ __ ______ 903500 ______ Switch 2A (SW2) PRINTER 0 S2-2 S2-5 S2-8 PRINTER 1 S2-3 S2-6 S2-7 ____ ____ ____ C O O SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg011 903546 ______ Switch 2A (SW2) Switch 9F (SW5) * Position # Position # (Strobe) Printer 0 S2-3 S2-4 S2-5 Printer 0 S5-1 Printer 1 S2-6 S2-7 S2-8 Printer 1 S5-2 ____ ____ ____ ____ O C O O * NOTE: Switch SW5, location 9F, selects whether a printer will receive a "normal" or inverted data strobe. 6.3.2. MPx 9000 and 9500 Series Systems ___ ____ ___ ____ ______ _______ The new DMP printer switch settings are: DMA CONTROLLER BOARD 903554 ___ __________ _____ ______ Switch 6J (SW2) PRINTER 0 S2-1 S2-2 S2-3 S2-4 PRINTER 1 S2-5 S2-6 S2-7 S2-8 ____ ____ ____ ____ C C O C PAGE 13 Hardware O-Open or Off C-Closed or On PAGE 14 7. INSTALLATION ____________ 7.1. INTRODUCTION ____________ There are two ways to install 8.5E: 1) Install a new system 2) Update a system If you are installing a new system go to section 7.2. If you are upgrading a system from 8.4D or below go to section 7.3. If you are upgrading a system from a level above 8.4D, go to section 7.4. If you are upgrading to 9.5E, go to section 7.5. 7.2. NEW INSTALLATION ___ ____________ The loading of 8.5E is done the same as any other BOSS/VS release. Since the operating system can be released on 1/2" (reel) or 1/4" (cartridge) tape, the word "tape" means either media form. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg012 7.2.1. Installing the O.S. __________ ___ ____ 7.2.1.1. ALT LOAD ___ ____ A) Insert the new release tape into the tape drive. B) Press the "ALTLOAD" button on the front panel. C) Enter the appropriate system disk (0 or 1) or if drives 0 and 1 are both system disks, enter "2" to update both disks. D) Enter a "0" to update WCS slot 0. E) Enter a "Y" to the prompt "Are you SURE you want to overwrite this WCS ? (Y/)". The system automatically updates the OS and WCS slot 0 on both disks, if selected. When this is complete, the system prompts "DONE - READY FOR NORMAL LOAD". Reload by pressing the LOAD button. 7.2.1.2. ENTER A TYPE 3 LOAD (SPECIAL FUNCTIONS) _____ _ ____ _ ____ ________ __________ Options 1-4 must be done to insure proper operation. PAGE 15 New Installation 7.2.1.2.1. OPTION 1 (CHANGE VOLUME INFORMATION) ______ _ _______ ______ ____________ SYSTEM DISKS: (displayed) DRIVE NUMBER:__________ Enter the disk to update. SERIAL NUMBER:_________ Enter CR to accept current serial number. DISK CONFIGURATION (1=SYSTEM, 2=DATA, 3=BACKUP):____ Enter the appropriate disk type. SIZE OF DUMP AREA....:______ Enter the size of the dump area given by the line below this prompt as the area needed for both main memory and shared memory controllers. FILE SYSTEM SPACE:______ Enter the number displayed at the bottom of the screen for this prompt. The display will appear as "CR=X" where X is the maximum space allowed. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg013 UPDATE DISK (Y/N): Enter "Y" 7.2.1.2.2. OPTION 2 (CHANGE INSTALLATION PARAMETERS) ______ _ _______ ____________ ___________ SYSTEM DISKS: (displayed) DRIVE NUMBER:_______ PRIMARY PREFIX ? Enter (family).R5E25.SYS. Where (family) is the family where the operating system files reside. SECONDARY PREFIX ? Enter (family).R5E25.SYS. PAGE 16 New Installation Where (family) is the family where the alternate operating system files reside. DEFAULT USER FAMILY NAME ?:________ Enter default user family SECURITY (E=ENABLED, D=DISABLED):___ FILE SYSTEM WRITE THROUGH? (E=ENABLED, D=DISABLED):___ For conversion purposes, set this option to D (disabled). This will speed up the conversion process. It can be changed later if desired. WRITE THROUGH DEFAULT ON FILE CREATE (E=ENABLED, D=DISABLED):__ This parameter specifies what the default write through will be on a file created through a BASIC file create or through the CREATE utility. UPDATE DISK WITH INSTALLATION PARAMETERS? (Y/N)__ Display: PARAMETERS SUCCESSFULLY WRITTEN TO DISK 7.2.1.2.3. OPTION 3 (UPDATE FAMILY INFORMATION) ______ _ _______ ______ ____________ AVAILABLE DRIVES: (displayed) FAMILY BASE DRIVE NUMBER:___ DRIVE NUMBERS OF OTHER DISKS IN FAMILY? (TYPE SPACES FOR NO OTHER DRIVES): Enter all other drive numbers for this family or spaces if none. The drives must be fixed media drives and in SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg014 8.5 format. UPDATE DISK (Y/N) ? 7.2.1.2.4. OPTION 4 (INITIALIZE FAMILY DIRECTORY) ______ _ ___________ ______ __________ FAMILY NAME:______ Enter family name. INITIALIZE FAMILY (Y/N)?__ Option 1 must be done on all disks. Option 2 must be done to system disks only. Options 3 and 4 must be done for all PAGE 17 New Installation families. 7.2.1.3. Restoring the O.S. _________ ___ ____ Enter SAVERESTORE in a TYPE II load and choose option #2 "RESTORE FILES FROM TAPE". The screen appears as in figure 7-1. At the prompt for output device, enter a parallel printer so that a listing of the restore operation is produced. This listing can be used to make sure all files were restored correctly. At the prompt, "FILE SPECIFIERS", enter ".". Enter to all other questions. All system files will be restored to disk. Please note that once all files are restored to disk, the message "AUTOMATIC COMPARE, CR TO CONTINUE" appears. This automatically rewinds the tape and begins the compare operation. This only occurs when the compare option is selected. When the compare is completed, enter a CTL-IV to return to the "SAVERESTORE" menu. Reload the system and enter a TYPE I load. Figure 7-1. Restore Screen ______ ____ _______ ______ -------------------------------------------------------- RESTORE FILES TAPE SET.ID: DRIVE-NUM: REEL-NUM: PRIMARY PREFIX: (FAMILY).NODE. FILETYPE (D/P/CR=ALL) COMPARE (CR=Y/N) DATE (MM/DD/YY) TIME (HH:MM) OUTPUT DEVICE (CR=VDT) DELETE EXISTING FILES (CR=Y) VERIFY (Y/CR=N) ENTRIES CORRECT (Y/N) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg015 -------------------------------------------------------- PAGE 18 New Installation 7.2.2. UPDATING OTHER O.S. SLOTS ________ _____ ____ _____ The slots 1, 2, and 3 need to be updated. Set the prefix to the .INST. node by keying in the following in command mode: !PREFIX .R5E25.INST. With the inclusion of support for 7000 Series Systems, there are two versions of REMIDI, BV5C0101 and BVM5C0101. Version BV5C0101 includes all the micro-diagnostics except MPC controller micro-diagnostics. It is placed in WCS slot 2 and is used for testing on both the 7000 and 8000 Series Systems. Version BVM5C0101 consists of micro-diagnostics for the MPC controller only, and is placed in WCS slot 3 on 7000 Series Systems. 7.2.2.1. UPDATING SLOT ONE (1) ________ ____ ___ ___ A copy of the primary operating system will be put in slot 1. UPDATE.OS IMAGE FILE NAME: .R5E25.INST.OS1.UV050525003 OS SLOT: (displayed) OS VERSION: (displayed) IMAGE FORMAT: (displayed) NEW WCS SLOT: 1 UPDATE WHICH DISK: (0=nn/1=nn/B=BOTH/Q=QUIT)___ DONE ! UPDATE COMPLETE Next, WCS slot 1 is updated with a copy of the same WCS that was installed in slot 0. UPDATE.WCS ENTER WCS SLOT [0..3]: Enter '1' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R5E25.INST.WCS.B537 WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 7.2.2.2. UPDATING WCS SLOT TWO (2) ________ ___ ____ ___ ___ REMIDI version BV5C0101 will reside in this slot. PAGE 19 New Installation UPDATE.WCS SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg016 ENTER WCS SLOT [0..3]: Enter '2' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE: (choose disk) WCS IMAGE FILE: .R5E25.INST.REMIDI.BV5C0101 WCS LEVEL OF WCS IMAGE FILE: (level displayed) UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETED! 7.2.2.3. UPDATING SLOT THREE (3) ________ ____ _____ ___ 7.2.2.3.1. Updating O.S. Slot Three ________ ____ ____ _____ The O.S. slot 3 will contain the O.S. for DEMON on both 7000 and 8000 Series Systems. UPDATE.OS IMAGE FILE NAME: .R5E25.INST.OS3.UV050400000 OS SLOT: (displayed) OS VERSION: (displayed) IMAGE FORMAT: (displayed) NEW WCS SLOT: Enter '0' or '1' on 7000 Series Systems to associate the WCS in either slot with load sector 3. Enter '3' on 8000 Series Systems. UPDATE WHICH DISK (0=nn/1=nn/B=BOTH/Q=QUIT):____ UPDATING DISK DONE! UPDATE IS NOW COMPLETE NOTE: On MPx 7000 Series Systems, the UPDATE.LD utility needs to be run to update the Load Directory. For further information on the use of UPDATE.LD, see the Diagnostics section in the 8.5D/9.5D Software Announcement. 7.2.2.3.2. Updating WCS Slot Three (3) ________ ___ ____ _____ ___ 7.2.2.3.2.1. WCS Slot Three on 7000 Series Systems ___ ____ _____ __ ____ ______ _______ This slot will contain the micro-diagnostics for the MPC controller, REMIDI version BVM5C0101. After this slot has been updated, it will be necessary to change the Load Directory by running the utility UPDATE.LD. See the Diagnostics section in the 8.5D/9.5D Software Announcement for further information on REMIDI and running UPDATE.LD. UPDATE.WCS PAGE 20 New Installation ENTER WCS SLOT [0..3]: Enter '3' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R5E25.INST.REMIDI.BVM5C0101 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg017 WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 7.2.2.3.2.2. WCS Slot Three on 8000 Series Systems ___ ____ _____ __ ____ ______ _______ This slot will contain system WCS which is common to both the O.S. and DEMON. UPDATE.WCS ENTER WCS SLOT [0..3]: Enter '3' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R5E25.INST.WCS.B537 WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 7.2.2.4. SLOT INFORMATION ____ ___________ Once all slots have been updated, use the utility OSINFO to display the slot information. The information should be simliar to figure 7-2. If disk 1 is a system disk also, repeat these steps beginning with step 7.2.2 Installation is now complete. PAGE 21 Figure 7-2. Operating System Information ______ ____ _________ ______ ___________ OPERATING SYSTEM INFORMATION ------------------------------------------------------------------ BOOT LEVEL : X.X.X.X LOAD SECTOR: 0 1 2 3 DISK 0 : 0/0 1/1 0/2 3/3 SERIAL # : XXX-XXXXX ------------------------------------------------------------------ OS NAME OS LEVEL DISK:SLOT WCS LEVEL ------------------------------------------------------------------ R 85E*25 861210 5.5.25.3 0:0 B 5.3.7 R 85E*25 861210 5.5.25.3 0:1 B 5.3.7 N/A 0:2 REMIDI B 5.1.1 DEMON 6/30/86 5.4.0.0 0:3 B 5.3.7 ------------------------------------------------------------------ NOTE: OSINFO on 7000 Series Systems will show the additional version of REMIDI IN WCS slot 3. PAGE 22 8.5E Installation Procedure for Upgrade from 8.4D and Below 7.3. 8000 UPGRADE FROM RELEASE LEVELS OF 8.4D AND BELOW ____ _______ ____ _______ ______ __ ____ ___ _____ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg018 7.3.1. Introduction ____________ Since 8.5 contains new file formats and a new file system, conversion of files is required to make files compatible with the new file system, if you are upgrading from a software release level of 8.4D or below. If you are upgrading from a release level above 8.4D, skip to section 7.4. The file conversion can be done in two ways: A) From tape to disk B) From disk to disk Which method is used depends on the configuration of the system. The disk to disk method is preferable for a system with removable disks. The disk to disk method involves upgrading the system disk with the new O.S.. Then the system disk can be used to convert other disks by using the NFSCONVERT utility to convert one file from one disk to another. This also moves the data from one disk to another. If this method is used on fixed disks, the files may not reside on the family intended unless copied back later. This should be considered when using the disk to disk conversion. The tape conversion uses the utility SAVERESTORE. The conversion process is invisible to the user with the exception of a status message that may be displayed during conversion. All one needs to do to convert is use SAVERESTORE in a normal manner. The tape conversion requires about 4 minutes per megabyte of data. The installation procedure is broken into two parts: A) Preliminary evaluation B) Operating System upgrade and file conversion The preliminary evaluation is required to ensure that proper hardware and file preparation is done. An O.S. upgrade from releases of 8.4D and below entails loading of the 8.5E system and converting files to their new format The conversion process, in large configurations, will take more than one day. The BOSS/VS release 8.5A began support for the MAI 7000 Series System. The BOSS/VS tape for the 7000 Series System resides on a 1/4" magnetic cartridge streamer (MCS) tape. At the end of this section is an upgrade and conversion PAGE 23 8.5E Installation Procedure for Upgrade from 8.4D and Below checklist that should be used to track progress through the upgrade procedure. 7.3.2. Preliminary Evaluation ___________ __________ The preliminary section deals with revision levels and file SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg019 preparation. 7.3.2.1. Hardware Evaluation ________ __________ All hardware must be checked for proper operation. All boards must be at proper revision levels (see the section "HARDWARE"). Ensure that all tape units are operating correctly. Also, make sure that all memory boards are set for 160 ns operation. Also note that any 3 CE systems must have a revision K or higher on the IMLC board (if present). 7.3.2.2. File Preparation ____ ___________ Obtain a directory listing with partial attributes for each family in the system. This listing will help you to find files, if any, that need repair before conversion. Next, using DISKANALYZER, validate all files in the system. Now determine which files need repair. Files which have the following attributes MUST be repaired before they are saved to tape: A) Files which lack integrity. B) Files which have lost space. C) Non-serial files in which records used is greater than records defined. D) Files that have invalid format. These files can be located in several ways: A) Scan the directory listing noting any files flagged. B) Use the report generated by DISKANALYZER as a guide. C) Use the utility FINDLOSTSPACE (8.4C/D only). All of the above methods should be used to find files that lack integrity and that have lost space. However, the directory listing must be scanned to find files that have a greater number of records used then defined as maximum records. This is a very important step. Any file possessing any of these attributes WILL NOT convert properly. They have PAGE 24 8.5E Installation Procedure for Upgrade from 8.4D and Below to be repaired on a previous release before conversion. Any EDITOR recovery files must be recovered or deleted before conversion. The recovery files are identified by the node ED.REC.. After the node, there will be a series of digits. These files can be found by scanning the directory listing. These files must be recovered by using EDIT.RECOVER or deleted by using the DELETE utility. ***************************************** SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg020 * * * ALL FILES MUST BE FREE FROM LACK OF * * INTEGRITY, LOST SPACE, AND MAX * * RECORDS GREATER THAN DEFINED RECORDS. * * FILES WILL NOT BE CONVERTED IF THEY * * POSSESS ANY ONE OF THESE ATTRIBUTES * * * ***************************************** 7.3.2.3. 8.5E Space Requirements ____ _____ ____________ The space required for files under the new file system are about the same as under 8.4D/C/B/A levels. However, it is recommended that a listing be obtained which displays the files and their new sizes. On the 8.4D release, the program FILESIZE is used to produce this listing. The program FILESIZE will display the new file size under the 8.5 file system for each file in a given family. It will also display the total number of sectors required by the entire family under the new file system. For further information on this utility, see the section on the Filesize utility in the 8.5D/9.5D Software Announcement. 7.3.2.4. Saving Files to Tape ______ _____ __ ____ Files must now be backed up to tape. If you are using disk to disk conversion, it is STRONGLY recommended that all files be saved to tape. This will allow recovery of files in case of problems with the disk to disk conversion. The files are saved using the standard tape utility, SAVERESTORE. When saving files to tape, send the output from the save process to the printer. These will provide a record of backup for each file. Also it is recommended that all tapes be compared to the files on the disk. When using the tape or disk conversion, the conversion requires temporary disk space to sort keyed (direct and sort) files. The space required varies with the number of records and the size of the key. To insure proper space is available, the following steps should be observed: PAGE 25 8.5E Installation Procedure for Upgrade from 8.4D and Below A) Do not restore the user default family until last. B) Convert large keyed files first. Step A insures that the default user disk has a large amount of free space since this is where the tape and disk conversion utility defines the temporary files. Step B allows the files that require the most amount of temporary space to be converted first. To convert large keyed files first, they must be saved to tape first. The large keyed files can be identified by scanning the directory listing obtained in section 7.3.2.2. If using disk to disk conversion, the NFSCONVERT utility allows you to SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg021 convert keyed files first. (See the section on the NFSCONVERT utility in the 8.5D/9.5D Software Announcement for further information.) 7.3.3. Operating System Update and File Conversion _________ ______ ______ ___ ____ __________ The loading of 8.5E is done the same as any other BOSS/VS release. However, there are some extra steps that are required to bring the disks into proper format. Since the operating system can be released on 1/2" (reel) or 1/4" (cartridge) tape, the word "tape" means either media form. 7.3.3.1. Installing the O.S. __________ ___ ____ 7.3.3.1.1. ALT LOAD ___ ____ A) Insert the new release tape into the tape drive. B) Press the "ALTLOAD" button on the front panel. C) Enter the appropriate system disk (0 or 1) or if drives 0 and 1 are both system disks, enter "2" to update both disks. D) Enter a "0" to update WCS slot 0. E) Enter a "Y" to the prompt "Are you SURE you want to overwrite this WCS ? (Y/)". The system automatically updates the OS and WCS slot 0 on both disks, if selected. When this is complete, the system prompts "DONE - READY FOR NORMAL LOAD". Reload by pressing the LOAD button. PAGE 26 8.5E Installation Procedure for Upgrade from 8.4D and Below 7.3.3.1.2. ENTER A TYPE 3 LOAD (SPECIAL FUNCTIONS) _____ _ ____ _ ____ ________ __________ This step is VERY important. Options 1-4 MUST be done for a 8.5E disk to be used on the system. These options MUST NOT be done for any disk that has not been converted to 8.5 format. If a tape conversion is being done, then initialize all disks at this time. If a disk to disk conversion is being done, then just initialize one scratch (8.5 format) pack that the converted files are going to reside on. In both cases the system disk(s) must be initialized. 7.3.3.1.2.1. OPTION 1 (CHANGE VOLUME INFORMATION) ______ _ _______ ______ ____________ SYSTEM DISKS: (displayed) DRIVE NUMBER:__________ Enter the disk to update. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg022 SERIAL NUMBER:_________ Enter CR to accept current serial number. DISK CONFIGURATION (1=SYSTEM, 2=DATA, 3=BACKUP):____ Enter the appropriate disk type. SIZE OF DUMP AREA....:______ Enter the size of the dump area given by the line below this prompt as the area needed for both main memory and shared memory controllers. FILE SYSTEM SPACE:______ Enter the number displayed at the bottom of the screen for this prompt. The display will appear as "CR=X" where X is the maximum space allowed. UPDATE DISK (Y/N): Enter "Y" 7.3.3.1.2.2. OPTION 2 (CHANGE INSTALLATION PARAMETERS) ______ _ _______ ____________ ___________ SYSTEM DISKS: (displayed) DRIVE NUMBER:_______ PRIMARY PREFIX ? PAGE 27 8.5E Installation Procedure for Upgrade from 8.4D and Below Enter (family).R5E25.SYS. Where (family) is the family where the operating system files reside. SECONDARY PREFIX ? Enter (family).R5E25.SYS. Where (family) is the family where the alternate operating system files reside. DEFAULT USER FAMILY NAME ?:________ Enter default user family SECURITY (E=ENABLED, D=DISABLED):___ FILE SYSTEM WRITE THROUGH? (E=ENABLED, D=DISABLED):___ For conversion purposes, set this option to D (disabled). This will speed up the conversion process. It can be changed later if needed. WRITE THROUGH DEFAULT ON FILE CREATE (E=ENABLED, D=DISABLED):__ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg023 This parameter specifies what the default write through will be on a file created through a BASIC file create or through the CREATE utility. UPDATE DISK WITH INSTALLATION PARAMETERS? (Y/N)__ Display: PARAMETERS SUCCESSFULLY WRITTEN TO DISK 7.3.3.1.2.3. OPTION 3 (UPDATE FAMILY INFORMATION) ______ _ _______ ______ ____________ AVAILABLE DRIVES: (displayed) FAMILY BASE DRIVE NUMBER:___ DRIVE NUMBERS OF OTHER DISKS IN FAMILY? (TYPE SPACES FOR NO OTHER DRIVES): Enter all other drive numbers for this family or spaces if none. The drives must be in 8.5 format. UPDATE DISK (Y/N) ? PAGE 28 8.5E Installation Procedure for Upgrade from 8.4D and Below 7.3.3.1.2.4. OPTION 4 (INITIALIZE FAMILY DIRECTORY) ______ _ ___________ ______ __________ FAMILY NAME:______ Enter family name. INITIALIZE FAMILY (Y/N)?__ Option 1 must be done to all disks. Option 2 must be done to the system disk. Options 3 and 4 must be done for all families. Reload the system by pressing the LOAD button and enter a TYPE II load. 7.3.3.2. Restoring the O.S. _________ ___ ____ Enter SAVERESTORE in a TYPE II load and choose option #2 "RESTORE FILES FROM TAPE". The screen appears as in figure 7-3. Figure 7-3. Restore Screen ______ ____ _______ ______ -------------------------------------------------------- RESTORE FILES TAPE SET.ID: DRIVE-NUM: REEL-NUM: PRIMARY PREFIX: (FAMILY).NODE. FILETYPE (D/P/CR=ALL) COMPARE (CR=Y/N) DATE (MM/DD/YY) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg024 TIME (HH:MM) OUTPUT DEVICE (CR=VDT) DELETE EXISTING FILES (CR=Y) VERIFY (Y/CR=N) ENTRIES CORRECT (Y/N) -------------------------------------------------------- At each prompt, enter a . At the prompt, "FILE SPECIFIERS", enter ".". Enter to all other questions. All system files will be restored to disk. Please note that once all files are restored to disk, the PAGE 29 8.5E Installation Procedure for Upgrade from 8.4D and Below message "AUTOMATIC COMPARE, CR TO CONTINUE" appears. This automatically rewinds the tape and begins the compare operation. This only occurs when the compare option is selected. When the compare is completed, enter a CTL-IV to return to the "SAVERESTORE" menu. 7.3.3.3. Installing the Configuration Record __________ ___ _____________ ______ The system model number has been included in the configuration record since release 8.5B. Therefore, it is necessary to install a new configuration record if you upgrade to 8.5D from a level below 8.5B. Until the following procedure is completed, the system will have a minimum configuration. Enter a TYPE I LOAD. Set your prefix to .SYSTEM.CONFIG. Before you load the new configuration record, rename the current configuration record on your system, using the RENAME utility, to temporarily preserve it for fall back purposes. (e.g. Add "OLD" in front of the name.) Using the SAVERESTORE utility, restore the new configuration record on tape onto your system. Execute the CONFIG.MGR utility. The CONFIG.MGR utility allows the user to update the system configuration record by installing a new configuration file. This utility displays the current and new configuration record. When "Y" is answered to the prompt "Install Configuration:", the new configuration is copied from the file ".SYSTEM.CONFIG.I(serial number)", to the special system area on disk. The new configuration takes effect at the next system load. For further details on the use of the CONFIG.MGR utility, see section on CONFIG.MGR in the 8.5D/ 9.5D Software Announcement. The configuration record file name is derived from the system serial number by changing the leading "8" to an "I" and adding the prefix ".SYSTEM.CONFIG.". EXAMPLE: .SYSTEM.CONFIG.I1030114 for SSN 810-30114 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg025 This file should be backed up by the user, in case reinstallation should become necessary. 7.3.3.4. Conversion of Files __________ __ _____ If doing tape to disk conversion see section 7.3.3.4.1. If doing disk to disk conversion see section 7.3.3.4.2. PAGE 30 8.5E Installation Procedure for Upgrade from 8.4D and Below 7.3.3.4.1. Tape to Disk Conversion ____ __ ____ __________ Mount the first tape to restore, enter the SAVERESTORE utility, and select option #2. A screen as in figure 7-3 will appear. Answer all prompts as in the figure. Make sure that you direct the output to a printer. This will provide you with a "history" of the restore operation. Each file is converted to the new file format as it is restored. The conversion to the new file format will be entirely invisible except for a pause at the completion of restoring a file. This pause, which can last a few seconds to a few hours depending on file size, indicates the file is being converted to the new file format. Occasionally the message "...CONVERTING FILE TO NFS..." will appear as a visual indicator of file conversion. System files from the previous release need not be restored. However, to preserve all system parameters and configurations, the 'SYSDATA' and '.SYSTEM.CONFIG.' node must be restored from the backup tapes. Tapes made on a releases of 8.4D and below cannot be compared when restored to the new file system. After all files have been restored, go to section 7.3.3.4.3. 7.3.3.4.2. Disk to Disk Conversion ____ __ ____ __________ The utility NFSCONVERT is used to convert files from the old format to the new file format. The destination disk must be in 8.5 format as described in section 7.3.3.1.2. The source disk must be in 8.4D format. When using disk to disk conversion, only one family may be converted per terminal. You cannot start NFSCONVERT on two terminals converting different parts of the same family. You can convert different families at the same time. As in the tape to disk conversion, the node '.SYSDATA.' and '.SYSTEM.CONFIG.' must be converted to preserve system parameters and configurations. See section on the NFSCONVERT utility in the 8.5D/9.5D Software Announcement for further information. 7.3.3.4.3. Check Files _____ _____ Once all files have been converted, DISKANALYZER should be used to validate all files for each family. DISKANALYZER can SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg026 be used in a TYPE II load or a TYPE I load. See the section on DISKANALYZER in the 8.5A software announcement for details of operation. Once all files have been validated, enter a TYPE I load, (if you have not already done so). PAGE 31 8.5E Installation Procedure for Upgrade from 8.4D and Below 7.3.4. UPDATING OTHER O.S. SLOTS ________ _____ ____ _____ The slots 1, 2, and 3 need to be updated. Set the prefix to the .INST. node by keying in the following in command mode: !PREFIX .R5E25.INST. With the inclusion of support for 7000 Series Systems, there are two versions of REMIDI, BV5C0101 and BVM5C0101. Version BV5C0101 includes all the micro-diagnostics except MPC controller micro-diagnostics. It is placed in WCS slot 2 and is used for testing on both the 7000 and 8000 Series Systems. Version BVM5C0101 consists of micro-diagnostics for the MPC controller only, and is placed in WCS slot 3 on 7000 Series Systems. 7.3.4.1. UPDATING SLOT ONE (1) ________ ____ ___ ___ A copy of the primary operating system will be put in slot 1. UPDATE.OS IMAGE FILE NAME: .R5E25.INST.OS1.UV050525003 OS SLOT: (displayed) OS VERSION: (displayed) IMAGE FORMAT: (displayed) NEW WCS SLOT: 1 UPDATE WHICH DISK: (0=nn/1=nn/B=BOTH/Q=QUIT)___ DONE ! UPDATE COMPLETE Next, WCS slot 1 is updated with a copy of the same WCS that was installed in slot 0. UPDATE.WCS ENTER WCS SLOT [0..3]: Enter '1' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R5E25.INST.WCS.B537 WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 7.3.4.2. UPDATING WCS SLOT TWO (2) ________ ___ ____ ___ ___ REMIDI version BV5C0101 will reside in this slot. PAGE 32 8.5E Installation Procedure for Upgrade from 8.4D and Below SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg027 UPDATE.WCS ENTER WCS SLOT [0..3]: Enter '2' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE: (choose disk) WCS IMAGE FILE: .R5E25.INST.REMIDI.BV5C0101 WCS LEVEL OF WCS IMAGE FILE: (level displayed) UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETED! 7.3.4.3. UPDATING SLOT THREE (3) ________ ____ _____ ___ 7.3.4.3.1. Updating O.S. Slot Three ________ ____ ____ _____ The O.S. slot 3 will contain the O.S. for DEMON on both 7000 and 8000 Series Systems. UPDATE.OS IMAGE FILE NAME: .R5E25.INST.OS3.UV050400000 OS SLOT: (displayed) OS VERSION: (displayed) IMAGE FORMAT: (displayed) NEW WCS SLOT: Enter '0' or '1' on 7000 Series Systems to associate the WCS in either slot with load sector 3. Enter '3' on 8000 Series Systems. UPDATE WHICH DISK (0=nn/1=nn/B=BOTH/Q=QUIT):____ UPDATING DISK DONE! UPDATE IS NOW COMPLETE NOTE: On MPx 7000 Series Systems, the UPDATE.LD utility needs to be run to update the Load Directory. For further information on the use of UPDATE.LD, see the Diagnostics section in the 8.5D/9.5D Software Announcement. 7.3.4.3.2. Updating WCS Slot Three (3) ________ ___ ____ _____ ___ 7.3.4.3.2.1. WCS Slot Three on 7000 Series Systems ___ ____ _____ __ ____ ______ _______ This slot will contain the micro-diagnostics for the MPC controller, REMIDI version BVM5C0101. After this slot has been updated, it will be necessary to change the Load Directory by running the utility UPDATE.LD. See the Diagnostics section in the 8.5D/9.5D Software Announcement for further information on REMIDI and running UPDATE.LD. UPDATE.WCS PAGE 33 8.5E Installation Procedure for Upgrade from 8.4D and Below ENTER WCS SLOT [0..3]: Enter '3' AVAILABLE DISK UNITS ARE: (displayed) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg028 DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R5E25.INST.REMIDI.BVM5C0101 WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 7.3.4.3.2.2. WCS Slot Three on 8000 Series Systems ___ ____ _____ __ ____ ______ _______ This slot will contain system WCS which is common to both the O.S. and DEMON. UPDATE.WCS ENTER WCS SLOT [0..3]: Enter '3' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R5E25.INST.WCS.B537 WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 7.3.4.4. SLOT INFORMATION ____ ___________ Once all slots have been updated, use the utility OSINFO to display the slot information. The information should be simliar to figure 7-2. If disk 1 is a system disk also, repeat these steps beginning with step 7.2.2 Installation is now complete. 7.3.5. Update Terminal Configuration File ______ ________ _____________ ____ The terminal configuration file must be updated to the new 8.5 format. This update will allow all other devices to become accessible. The file is updated by entering TERM.CONFIG and choosing the update option. Enter PRIMARY as the file to change. Enter an existing ISDC and display one of the ISDC ports. Enter a MB-IV to exit the update without changing anything. The utility will say that the file has been modified and do you want to save it. Respond with YES. Now reload the system to allow the devices to become active. Installation is now complete. PAGE 34 Figure 7-4. Operating System Information ______ ____ _________ ______ ___________ OPERATING SYSTEM INFORMATION ------------------------------------------------------------------ BOOT LEVEL : X.X.X.X LOAD SECTOR: 0 1 2 3 DISK 0 : 0/0 1/1 0/2 3/3 SERIAL # : XXX-XXXXX SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg029 ------------------------------------------------------------------ OS NAME OS LEVEL DISK:SLOT WCS LEVEL ------------------------------------------------------------------ R 85E*25 861210 5.5.25.3 0:0 B 5.3.7 R 85E*25 861210 5.5.25.3 0:1 B 5.3.7 N/A 0:2 REMIDI B 5.1.1 DEMON 6/30/86 5.4.0.0 0:3 B 5.3.7 ------------------------------------------------------------------ NOTE: OSINFO on 7000 Series Systems will show the additional version of REMIDI IN WCS slot 3. PAGE 35 8.5E 8000 UPGRADE AND CONVERSION CHECKLIST ____ ____ _______ ___ __________ _________ 1) Hardware levels => section 6 2) Validate files => section 7.3.2.2 A) DIR listings B) FINDLOSTSPACE Utility C) Delete unwanted EDITOR,SPOOL, and TEMP files 3) New file sizes => section 7.3.2.3 A) FILESIZE utility 4) Save files to tape => section 7.3.2.4 A) Large keyed files first 5) Update operating system => section 7.3.3.1 A) ALT-LOAD B) Options 1-4 C) Restore operating system files 6) File conversion A) Tape-to-disk => section 7.3.3.4.1 B) Disk-to-disk => section 7.3.3.4.2 7) Check file integrity => section 7.3.3.4.3 8) Complete installation A) Update slots => section 7.2.2 B) Update terminal configuration file => section 7.3.5 PAGE 36 8.5E Installation Procedure for Upgrade from Releases Above 8.4D 7.4. 8000 UPGRADE FROM RELEASE LEVELS ABOVE 8.4D SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg030 ____ _______ ____ _______ ______ _____ ____ If you are upgrading to 8.5E from release level 8.4D or below, go to section 7.3. If you are upgrading to 9.5E, go to section 7.5. 7.4.1. Saving Files to Tape ______ _____ __ ____ Current files must first be backed up to tape, using the standard tape utility, SAVERESTORE. When saving files to tape, send the output from the save process to the printer. These will provide a record of backup for each file. Also it is recommended that all tapes be compared to the files on the disk. 7.4.2. Operating System Update _________ ______ ______ 7.4.2.1. Installing the O.S. __________ ___ ____ 7.4.2.1.1. ALT LOAD ___ ____ A) Insert the new release tape into the tape drive. B) Press the "ALTLOAD" button on the front panel. C) Enter the appropriate system disk (0 or 1) or if drives 0 and 1 are both system disks, enter "2" to update both disks. D) Enter a "0" to update WCS slot 0. E) Enter a "Y" to the prompt "Are you SURE you want to overwrite this WCS ? (Y/)". The system automatically updates the OS and WCS slot 0 on both disks, if selected. When this is complete, the system prompts "DONE - READY FOR NORMAL LOAD". Reload by pressing the LOAD button. 7.4.2.1.2. CHANGE INSTALLATION PARAMETERS ______ ____________ __________ Enter a TYPE 3 LOAD (Special Functions) and select option 2, "Change Installation Parameters". The following will be displayed: SYSTEM DISKS: (displayed) DRIVE NUMBER:_______ PAGE 37 8.5E Installation Procedure for Upgrade from Releases Above 8.4D PRIMARY PREFIX ? Enter (family).R5E25.SYS. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg031 Where (family) is the family where the operating system files reside. SECONDARY PREFIX ? Enter (family).R5E25.SYS. Where (family) is the family where the alternate operating system files reside. DEFAULT USER FAMILY NAME ?:________ Enter default user family SECURITY (E=ENABLED, D=DISABLED):___ FILE SYSTEM WRITE THROUGH? (E=ENABLED, D=DISABLED):___ WRITE THROUGH DEFAULT ON FILE CREATE (E=ENABLED, D=DISABLED):__ This parameter specifies what the default write through will be on a file created through a BASIC file create or through the CREATE utility. UPDATE DISK WITH INSTALLATION PARAMETERS? (Y/N)__ Display: PARAMETERS SUCCESSFULLY WRITTEN TO DISK Reload the system by pressing the LOAD button and enter a TYPE II load. 7.4.2.2. Restoring the O.S. _________ ___ ____ Enter SAVERESTORE in a TYPE II load and choose option #2 "RESTORE FILES FROM TAPE". The screen appears as in figure 7-3. At the prompt, "FILE SPECIFIERS", enter ".". Enter to all other questions. All system files will be restored to disk. Please note that once all files are restored to disk, the message "AUTOMATIC COMPARE, CR TO CONTINUE" appears. This automatically rewinds the tape and begins the compare operation. This only occurs when the compare option is PAGE 38 8.5E Installation Procedure for Upgrade from Releases Above 8.4D Figure 7-5. Restore Screen ______ ____ _______ ______ -------------------------------------------------------- RESTORE FILES TAPE SET.ID: DRIVE-NUM: REEL-NUM: PRIMARY PREFIX: (FAMILY).NODE. FILETYPE (D/P/CR=ALL) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg032 COMPARE (CR=Y/N) DATE (MM/DD/YY) TIME (HH:MM) OUTPUT DEVICE (CR=VDT) DELETE EXISTING FILES (CR=Y) VERIFY (Y/CR=N) ENTRIES CORRECT (Y/N) -------------------------------------------------------- At each prompt, enter a . selected. When the compare is completed, enter a CTL-IV to return to the "SAVERESTORE" menu. 7.4.2.3. Installing the Configuration Record __________ ___ _____________ ______ The system model number has been included in the configuration record since release 8.5B. Therefore, it is necessary to install a new configuration record if you upgrade to 8.5D from a level below 8.5B. Until the following procedure is completed, the system will have a minimum configuration. Enter a TYPE I LOAD. Set your prefix to .SYSTEM.CONFIG. Before you load the new configuration record, rename the current configuration record on your system, using the RENAME utility, to temporarily preserve it for fall back purposes. (e.g. Add "OLD" in front of the name.) Using the SAVERESTORE utility, restore the new configuration record on tape onto your system. Execute the CONFIG.MGR utility. The CONFIG.MGR utility allows the user to update the system configuration record by installing a new configuration file. This utility displays the current and new configuration record. When "Y" is answered to the prompt "Install Configuration:", the new configuration is copied from the file ".SYSTEM.CONFIG.I(serial PAGE 39 8.5E Installation Procedure for Upgrade from Releases Above 8.4D number)", to the special system area on disk. The new configuration takes effect at the next system load. For further details on the use of the CONFIG.MGR utility, see section on CONFIG.MGR in the 8.5D/ 9.5D Software Announcement. The configuration record file name is derived from the system serial number by changing the leading "8" to an "I" and adding the prefix ".SYSTEM.CONFIG.". EXAMPLE: .SYSTEM.CONFIG.I1030114 for SSN 810-30114 This file should be backed up by the user, in case reinstallation should become necessary. 7.4.3. UPDATING OTHER O.S. SLOTS ________ _____ ____ _____ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg033 The slots 1, 2, and 3 need to be updated. Set the prefix to the .INST. node by keying in the following in command mode: !PREFIX .R5E25.INST. With the inclusion of support for 7000 Series Systems, there are two versions of REMIDI, BV5C0101 and BVM5C0101. Version BV5C0101 includes all the micro-diagnostics except MPC controller micro-diagnostics. It is placed in WCS slot 2 and is used for testing on both the 7000 and 8000 Series Systems. Version BVM5C0101 consists of micro-diagnostics for the MPC controller only, and is placed in WCS slot 3 on 7000 Series Systems. 7.4.3.1. UPDATING SLOT ONE (1) ________ ____ ___ ___ A copy of the primary operating system will be put in slot 1. UPDATE.OS IMAGE FILE NAME: .R5E25.INST.OS1.UV050525003 OS SLOT: (displayed) OS VERSION: (displayed) IMAGE FORMAT: (displayed) NEW WCS SLOT: 1 UPDATE WHICH DISK: (0=nn/1=nn/B=BOTH/Q=QUIT)___ DONE ! UPDATE COMPLETE Next, WCS slot 1 is updated with a copy of the same WCS that was installed in slot 0. UPDATE.WCS PAGE 40 8.5E Installation Procedure for Upgrade from Releases Above 8.4D ENTER WCS SLOT [0..3]: Enter '1' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R5E25.INST.WCS.B537 WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 7.4.3.2. UPDATING WCS SLOT TWO (2) ________ ___ ____ ___ ___ REMIDI version BV5C0101 will reside in this slot. UPDATE.WCS ENTER WCS SLOT [0..3]: Enter '2' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE: (choose disk) WCS IMAGE FILE: .R5E25.INST.REMIDI.BV5C0101 WCS LEVEL OF WCS IMAGE FILE: (level displayed) UPDATING DISK UNIT nn SECTOR xx SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg034 WCS UPDATE COMPLETED! 7.4.3.3. UPDATING SLOT THREE (3) ________ ____ _____ ___ 7.4.3.3.1. Updating O.S. Slot Three ________ ____ ____ _____ The O.S. slot 3 will contain the O.S. for DEMON on both 7000 and 8000 Series Systems. UPDATE.OS IMAGE FILE NAME: .R5E25.INST.OS3.UV050400000 OS SLOT: (displayed) OS VERSION: (displayed) IMAGE FORMAT: (displayed) NEW WCS SLOT: Enter '0' or '1' on 7000 Series Systems to associate the WCS in either slot with load sector 3. Enter '3' on 8000 Series Systems. UPDATE WHICH DISK (0=nn/1=nn/B=BOTH/Q=QUIT):____ UPDATING DISK DONE! UPDATE IS NOW COMPLETE NOTE: On MPx 7000 Series Systems, the UPDATE.LD utility needs to be run to update the Load Directory. For further information on the use of UPDATE.LD, see the Diagnostics section in the 8.5D/9.5D Software Announcement. PAGE 41 8.5E Installation Procedure for Upgrade from Releases Above 8.4D 7.4.3.3.2. Updating WCS Slot Three (3) ________ ___ ____ _____ ___ 7.4.3.3.2.1. WCS Slot Three on 7000 Series Systems ___ ____ _____ __ ____ ______ _______ This slot will contain the micro-diagnostics for the MPC controller, REMIDI version BVM5C0101. After this slot has been updated, it will be necessary to change the Load Directory by running the utility UPDATE.LD. See the Diagnostics section in the 8.5D/9.5D Software Announcement for further information on REMIDI and running UPDATE.LD. UPDATE.WCS ENTER WCS SLOT [0..3]: Enter '3' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R5E25.INST.REMIDI.BVM5C0101 WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 7.4.3.3.2.2. WCS Slot Three on 8000 Series Systems ___ ____ _____ __ ____ ______ _______ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg035 This slot will contain system WCS which is common to both the O.S. and DEMON. UPDATE.WCS ENTER WCS SLOT [0..3]: Enter '3' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R5E25.INST.WCS.B537 WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 7.4.3.4. SLOT INFORMATION ____ ___________ Once all slots have been updated, use the utility OSINFO to display the slot information. The information should be simliar to figure 7-2. If disk 1 is a system disk also, repeat these steps beginning with step 7.2.2 Installation is now complete. PAGE 42 Figure 7-6. Operating System Information ______ ____ _________ ______ ___________ OPERATING SYSTEM INFORMATION ------------------------------------------------------------------ BOOT LEVEL : X.X.X.X LOAD SECTOR: 0 1 2 3 DISK 0 : 0/0 1/1 0/2 3/3 SERIAL # : XXX-XXXXX ------------------------------------------------------------------ OS NAME OS LEVEL DISK:SLOT WCS LEVEL ------------------------------------------------------------------ R 85E*25 861210 5.5.25.3 0:0 B 5.3.7 R 85E*25 861210 5.5.25.3 0:1 B 5.3.7 N/A 0:2 REMIDI B 5.1.1 DEMON 6/30/86 5.4.0.0 0:3 B 5.3.7 ------------------------------------------------------------------ NOTE: OSINFO on 7000 Series Systems will show the additional version of REMIDI IN WCS slot 3. PAGE 43 Upgrading to MPx 9000, 9100, and 9500 Series Systems 7.5. UPGRADING TO 9.5E AND THE MPX 9000, 9100, AND 9500 _________ __ ____ ___ ___ ___ _____ _____ ___ ____ 7.5.1. SPECIAL CONSIDERATIONS _______ ______________ A presite survey is required before upgrading to an MPx 9000, 9100 or 9500. (See Field Bulletin #161A). It is required that systems being upgraded to 9.5E run on a SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg036 release level that supports the new File System (any level above 8.4D) for at least one week prior to upgrade. It is recommended that systems being upgraded to 9.5E run on 8.5E prior to upgrade. When it is established that the system is running smoothly on the software at the end of this period, upgrade to 9.5E may then proceed. 7.5.2. PRINTING OUT THE TERMINAL CONFIGURATION RECORD ________ ___ ___ ________ _____________ ______ Skip this section if your are upgrading to 9.5E from a previous 9.5 release. When upgrading from the MPx 8000 to the MPx 9000, 9100 or 9500, It is necessary to reference the 8.5 terminal configuration in order to properly re-address the 9000, 9100, and 9500 controllers. Therefore, it is necessary to print out a copy of the terminal configuration record before upgrading. 1. Enter the TERM.CONFIG utility. 2. Select option 2, "DISPLAY A CONFIGURATION FILE" 3. When the following screen is displayed, enter these responses to the prompts: CONFIGURATION FILE: P OUTPUT DEVICE: DETAILED REPORT: Y ENTRIES CORRECT: Y The terminal configuration record should now be printed. 7.5.3. SAVING FILES TO TAPE ______ _____ __ ____ Current files must first be backed up to tape, using the standard tape utility, SAVERESTORE. When saving files to tape, send the output from the save process to the printer. This will provide a record of backup for each file. Also it is recommended that all tapes be compared to the files on the disk. PAGE 44 Upgrading to MPx 9000, 9100, and 9500 Series Systems 7.5.4. OPERATING SYSTEM UPDATE _________ ______ ______ 7.5.4.1. ALT LOAD ___ ____ A) Insert the new release tape into the tape drive. B) Press the "ALTLOAD" button on the front panel. C) Enter the appropriate system disk (0 or 1) or if drives 0 and 1 are both system disks, enter "2" to update both disks. D) Enter a "0" to update WCS slot 0. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg037 E) Enter a "Y" to the prompt "Are you SURE you want to overwrite this WCS ? (Y/)". The system automatically updates the OS and WCS slot 0 on both disks, if selected. When this is complete, the system prompts "DONE - READY FOR NORMAL LOAD". Load the 9.5E O.S. from slot 0 by setting switch 3 to 'off' and pressing the LOAD switch. 7.5.4.2. TYPE 3 LOAD (SPECIAL FUNCTIONS) ____ _ ____ ________ __________ 7.5.4.2.1. Updating Installation Parameters ________ ____________ __________ Enter a TYPE 3 LOAD (Special Functions) and select option 2, "Update Installation Parameters". The following will be displayed: SYSTEM DISKS: (displayed) DRIVE NUMBER:_______ PRIMARY PREFIX ? Enter (family).R5E25.SYS. Where (family) is the family where the operating system files reside. SECONDARY PREFIX ? Enter (family).R5E25.SYS. Where (family) is the family where the alternate operating system files reside. PAGE 45 Upgrading to MPx 9000, 9100, and 9500 Series Systems DEFAULT USER FAMILY NAME ?:________ Enter default user family SECURITY (E=ENABLED, D=DISABLED):___ FILE SYSTEM WRITE THROUGH? (E=ENABLED, D=DISABLED):___ WRITE THROUGH DEFAULT ON FILE CREATE (E=ENABLED, D=DISABLED):__ This parameter specifies what the default write through will be on a file created through a BASIC file create or through the CREATE utility. (Please see Field Bulletin #212.) UPDATE DISK WITH INSTALLATION PARAMETERS? (Y/N)__ Display: PARAMETERS SUCCESSFULLY WRITTEN TO DISK Reload the system by pressing the LOAD button and enter a TYPE II load. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg038 7.5.4.2.2. Sizing the Dump Area (Change Volume Information) ______ ___ ____ ____ _______ ______ ____________ At this point it is necessary to enter a TYPE 3 LOAD, Option 1, "Change Volume Information" to determine whether the Dump Area is large enough. Presently, on all MPx release levels, the operating system computes the size of the Dump Area using information derived from the currently installed configuration record in conjunction with a survey of the installed hardware at the time of the last system load. This method has two major disadvantages: 1. If a disk has no installed configuration record, the Dump Area size is computed on a minimum configuration, regardless of what hardware is installed in the system. 2. If additional main memory and shared memory controllers are installed in the system, and this exceeds the limits set by the currently installed configuration record, this new hardware will not be included when computing the size of the Dump Area. The solution to this problem is for the operating system to actually check the installed hardware when computing the size of the Dump Area, and this will be done in releases 8.6A/9.6A. In the meantime, if either one of the above two situations apply to your system, it will be necessary to compute the size of the Dump Area by determining exactly what main memory and PAGE 46 Upgrading to MPx 9000, 9100, and 9500 Series Systems shared memory controllers are installed in the system, and adding up the area required for each. The total should be input in Option 1 (Change Volume Information) of a TYPE 3 LOAD after the prompt "SIZE OF DUMP AREA (FOR SYSTEM DISK ONLY):". All other numbers on the Option 1 screen that refer to the size of the Dump Area should be ignored. Listed below are the main memory and shared memory controllers and the values to be used when computing the size of the Dump Area: 1. Each megabyte of main memory (903349, 903516)...1024 (x 1024 bytes) 2. Each 4-Way controller (903374).................. 64 (x 1024 bytes) 3. Each 8-Way controller (903383).................. 64 (x 1024 bytes) 4. Each 16-Way controller (903437.................. 128 (x 1024 bytes) 5. Each IMLC controller (903381, 903534)........... 64 (x 1024 bytes) 6. Each LAN controller............................. 64 (x 1024 bytes) 7. Each BMTC controller (903413)................... 128 (x 1024 bytes) EXAMPLE: A system has 8 MB of main memory, 1 4-Way controller, 2 16-Way controllers, 1 IMLC, and 1 BMTC. Compute the size of the Dump Area as follows: 8 MB main memory (8 x 1024) = 8192 (x 1024 bytes) 1 4-Way controller = 64 (x 1024 bytes) 2 16-Way controllers (2 x 128) = 256 (x 1024 bytes) 1 IMLC = 64 (x 1024 bytes) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg039 1 BMTC = +128 (x 1024 bytes) ---- Total 8704 (x 1024 bytes) "SIZE OF DUMP AREA (FOR SYSTEM DISKS ONLY):" 8704 (x 1024 bytes) Correct sizing of the Dump Area is especially critical on MPx 9000, 9100, and 9500 systems, because dumps to tape are not possible on these systems. This is because the BMTC, which is required to control tape operations on MPx 9000, 9100, and 9500 systems, is a shared memory controller. When sizing the Dump Area, you may want to round up to the next megabyte or add an extra megabyte or two for future expansion. If it becomes necessary to enlarge the Dump Area, you must do a complete back up (which you already should have), reinitialize the system disks (options 1-4 in a TYPE 3 LOAD), and do a restore from the back up in a TYPE 2 LOAD. 7.5.4.3. Restoring the O.S. Files _________ ___ ____ _____ Enter SAVERESTORE in a TYPE II load and choose option #2 PAGE 47 Upgrading to MPx 9000, 9100, and 9500 Series Systems "RESTORE FILES FROM TAPE". The screen appears as in figure 7-3. Figure 7-7. Restore Screen ______ ____ _______ ______ -------------------------------------------------------- RESTORE FILES TAPE SET.ID: DRIVE-NUM: REEL-NUM: PRIMARY PREFIX: (FAMILY).NODE. FILETYPE (D/P/CR=ALL) COMPARE (CR=Y/N) DATE (MM/DD/YY) TIME (HH:MM) OUTPUT DEVICE (CR=VDT) DELETE EXISTING FILES (CR=Y) VERIFY (Y/CR=N) ENTRIES CORRECT (Y/N) -------------------------------------------------------- At each prompt, enter a . At the prompt, "FILE SPECIFIERS", enter ".". Enter to all other questions. This will restore all files from the release tape to disk. Please note that once all files are restored to disk, the message "AUTOMATIC COMPARE, CR TO CONTINUE" appears. This SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg040 automatically rewinds the tape and begins the compare operation. This only occurs when the compare option is selected. When the compare is completed, enter a CTL-IV to return to the "SAVERESTORE" menu. 7.5.4.4. Installing the Configuration Record __________ ___ _____________ ______ It is necessary to install a new configuration record when upgrading to 9.5E from 8.4 and 8.5 release levels. Skip this section if you are upgrading from A previous 9.5 release. Until the following procedure is completed, the system will have a minimum configuration. Enter a TYPE I LOAD. Set your prefix to .SYSTEM.CONFIG. Before you load the new configuration record, rename the current configuration record on your system, using the RENAME PAGE 48 Upgrading to MPx 9000, 9100, and 9500 Series Systems utility, to temporarily preserve it for fall back purposes. (e.g. ".OLDCONFIG.") Using the SAVERESTORE utility, restore the new configuration record on tape onto your system. Execute the CONFIG.MGR utility. The CONFIG.MGR utility allows the user to update the system configuration record by installing a new configuration file. This utility displays the current and new configuration record. When "Y" is answered to the prompt "Install Configuration:", the new configuration is copied from the file ".SYSTEM.CONFIG.I(serial number)", to the special system area on disk. The new configuration takes effect at the next system load. For further details on the use of the CONFIG.MGR utility, see section on CONFIG.MGR in the 8.5D/ 9.5D Software Announcement. The configuration record file name is derived from the system serial number by changing the leading "8" to an "I" and adding the prefix ".SYSTEM.CONFIG.". EXAMPLE: .SYSTEM.CONFIG.I1030114 for SSN 810-30114 This file should be backed up by the user, in case reinstallation should become necessary. 7.5.5. UPDATING OTHER O.S. SLOTS ________ _____ ____ _____ The slots 1, 2, and 3 need to be updated. Set the prefix to the .INST. node by keying in the following in command mode: !PREFIX .R5E25.INST. 7.5.5.1. Updating Slot One (1) ________ ____ ___ ___ A copy of the 9.5E operating system will be put in O.S. slot 1. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg041 UPDATE.OS IMAGE FILE NAME: .R5E25.INST.OS1.UV050525003 OS SLOT: (displayed) OS VERSION: (displayed) IMAGE FORMAT: (displayed) NEW WCS SLOT: 1 UPDATE WHICH DISK: (0=nn/1=nn/B=BOTH/Q=QUIT)___ DONE ! UPDATE COMPLETE Next, WCS slot 1 is updated with a copy of the 9.5E WCS. PAGE 49 Upgrading to MPx 9000, 9100, and 9500 Series Systems UPDATE.WCS ENTER WCS SLOT [0..3]: Enter '1' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R5E25.INST.WCS.A571 WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 7.5.5.2. Updating WCS Slot Two (2) ________ ___ ____ ___ ___ The first section of the 9000/9100/9500 version of REMIDI will reside in this slot. NOTE: Running UPDATE.OS automatically updates the load sectors for the disk. However, running UPDATE.WCS does not. (The Load Sectors are displayed at the top of the OSINFO screen.) It is therefore necessary to run UPDATE.LD for REMIDI on newly initialized systems packs, or whenever question marks ("?/?") appear in Load Sector 2 on the OSINFO screen. See the Diagnostics section in the 8.5D/9.5D Software Announcement for further information on REMIDI and running UPDATE.LD. UPDATE.WCS ENTER WCS SLOT [0..3]: Enter '2' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE: (choose disk) WCS IMAGE FILE: .R5E25.INST.REMIDI.AVA6A0104 WCS LEVEL OF WCS IMAGE FILE: (level displayed) UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETED! 7.5.5.3. Updating Slot Three (3) ________ ____ _____ ___ 7.5.5.3.1. Updating O.S. Slot Three (3) ________ ____ ____ _____ ___ O.S. slot 3 will contain the O.S. for DEMON. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg042 UPDATE.OS IMAGE FILE NAME: .R5E25.INST.OS3.UV050400000 OS SLOT: (displayed) OS VERSION: (displayed) IMAGE FORMAT: (displayed) NEW WCS SLOT: Enter '0' to associate DEMON's O.S. with the PAGE 50 Upgrading to MPx 9000, 9100, and 9500 Series Systems WCS in slot 0. (DEMON and the 9.5E O.S. share the same WCS. UPDATE WHICH DISK (0=nn/1=nn/B=BOTH/Q=QUIT):____ UPDATING DISK DONE! UPDATE IS NOW COMPLETE 7.5.5.3.2. Changing the Load Sector for Slot Three (3) ________ ___ ____ ______ ___ ____ _____ ___ Because the second section of the 9000/9100/9500 version of REMIDI is in WCS slot 3, the Load Directory must be changed to point to another WCS slot for DEMON. The 9.5E O.S. and DEMON share the same WCS code, therefore, we can point to the WCS slot used by the 9.5E O.S. Update the Load Directory for DEMON by using the UPDATE.LD utility. See the the Diagnostics section in the 8.5D/9.5D Software Announcement for information on how to run UPDATE.LD. 7.5.5.3.3. Updating WCS Slot Three (3) ________ ___ ____ _____ ___ This slot will contain the second section of the 9000/9100/9500 version of REMIDI. UPDATE.WCS ENTER WCS SLOT [0..3]: Enter '3' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R5E25.INST.REMIDI.AVC6A0104 WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 7.5.6. SLOT INFORMATION ____ ___________ Once all slots have been updated, use the utility OSINFO to display the slot information. The information should be simliar to figure 7-2. PAGE 51 Upgrading to MPx 9000, 9100, and 9500 Series Systems Figure 7-8. Operating System Information ______ ____ _________ ______ ___________ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg043 OPERATING SYSTEM INFORMATION ------------------------------------------------------------------ BOOT LEVEL : X.X.X.X LOAD SECTOR: 0 1 2 3 DISK 0 : 0/0 1/1 0/2 3/1 SERIAL # : XXX-XXXXX ------------------------------------------------------------------ OS NAME OS LEVEL DISK:SLOT WCS LEVEL ------------------------------------------------------------------ R 5E*25 861210 5.5.25.3 0:0 A 5.7.1 R 5E*25 861210 5.5.25.3 0:1 A 5.7.1 N/A 0:2 REMIDI A 6.1.4 DEMON 6/30/86 5.4.0.0 0:3 REMIDI A 6.1.5 ------------------------------------------------------------------ The O.S. and WCS slots on all other system disks on the system must also be updated. Installation is now complete. PAGE 52 8. RELATED DOCUMENTATION _______ _____________ 2770/2780/3770/3780 Batch Emulator User Guide M 5080C 3270 Pass-Through Reference Manual M 5091A BOSS/VS Business BASIC Reference Manual M 5092C BOSS/VS User Guide M 5098E BOSS/VS Utilities User Guide M 5102D 3270 Emulation Package Operator Guide for MAI 8000 Series M 5129 MAI 8000 Terminal Asynchronous Communication Facility Reference Manual M 5130A File Transfer Facility User Reference Manual M 6352 BOSS/VS Installation Guide M 5138C MPx System Installation Planning Guide M 5146E BOSS/VS Special Purpose Utilities User Guide M 5151 BOSS/VS System Support Manual M 5152 Intersystem Transport Package User Guide M 6354D MAI 8000 Series COBOL Reference Manual M 5174 MAI 8000 Series COBOL User Guide M 5175 BOSS/VS File Conversion User Guide M 5185A PAGE 53 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg044 ORIGINATOR: MBF SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB031 Pg045 FIB 00032 10/12/87 *** Release 9.6/8.6B is now available *** MAI Basic Four, Inc. is pleased to announce that the new software release, 9.6B/8.6B, is now available. The 9.6B release is the recommended release for MPx 9000, 9100, and 9500 Series Systems. The 8.6B release is the recommended release for MPx 7000, 7100, and 8000 Series Systems. A. ENHANCEMENTS The 9.6B/8.6B release contains the following enhancements: o Support for the new 4314 terminal, which features: - dual serial ports - 132-character screen o Automatic type conversion of numeric/string fields in Multi-key files. For further information on this new feature, see the section on Multi-key files in the 9.6/8.6 Software Announcement. o VFU load is no longer done by the system when a printer is in RESERVE or DISCONNECT mode. This allows the operator to control VFU in the application program. The change makes VFU handling consistent with the 8.4 and 9.5/8.5 operating system releases. In addition, the 9.6B/8.6B release contains fixes for problems in the JOB MANAGER, SAVERESTORE, UPDATE, and SPOOLER utilities, BASIC, FTF, and TBC. See the section "Fixes in this Release" in the 9.6B/8.6B Software Announcement for specific fixes. B. IMPORTANT CONSIDERATIONS FOR 9.6B/8.6B AND 9.6A/8.6A o 9.6/8.6 features new System Startup procedures for MAGNET, SPOOLER, and JOB MANAGER. These procedures are documented in the System Startup section of the 9.6/8.6 Software Announcements. o BASIC programs written or modified on release levels 9.6A/8.6A and above will not run on prior releases without recompilation. If you wish to move BASIC programs from 9.6/8.6 to 9.5/8.5 or 8.4, these programs should not contain any of the new features offered on 9.6/8.6, and they will need to be recompiled on the prior release. o A new configuration record is not required when upgrading from release 9.6A to 9.6B or from release 8.6A to 8.6B. A new configuration record is required , however, when upgrading from 9.5/8.5 and 8.4 releases to 9.6/8.6 releases. A new configuration record is also required when an upgrade includes new hardware (such as a upgrade from an 8000 Series System to a 9000/9100/9500 Series System). C. ADDITIONAL IMPORTANT CONSIDERATIONS o Upgrades from release levels 8.4D and below require a conversion to the new File System. These instructions appear in the software announcements for releases 8.4E and 8.5A/B/C/D/E, as well as in the "BOSS/VS FILE CONVERSION USER GUIDE" M5185A. These conversion instructions do not appear in the 9.6/8.6 Software Announcements. o It is recommended that 8000 Series Systems being upgraded to 9000 or 9500 Series Systems run on the new File System (O.S. releases 8.4E and above) for. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB032 Pg001 a minimum of one week prior to the hardware upgrade. 9.5 systems should upgrade directly to 9.6B. o A presite survey is required before installing or upgrading to an MPx 9000, 9100, or 9500. (See Field Bulletin 161A). o When upgrading to 9.6/8.6 from releases prior to 9.5C/8.5C, an ALT LOAD must be done before the O.S. files are restored. This is because certain files will not restore (including the drivers for the ISDC controllers) when on releases prior to 9.5C/8.5C. D. RELATED DOCUMENTATION A detailed explanation of the new features of 9.6/8.6 and how to use them, can be found in the following manuals. These manuals were updated for 9/8.6A. An update for 9/8.6B was not necessary. BUSINESS BASIC 86 REFERENCE MANUAL M6262 BOSS/VS USER GUIDE M5098F BOSS/VS UTILITIES USER GUIDE M5102E BOSS/VS INSTALLATION GUIDE M5138D MAGNET/VS USER REFERENCE MANUAL M6363 ORIGINATOR: N. Prentiss SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB032 Pg002 FIB 00033 10/30/87 *** The Use of EXTTAPE with MPx 8.4 Configuration Records *** When MPx configuration records are created, the release level they display will be the latest official level for a given major release at the time of creation. For example, recently created 8.4 configuration records display 8.4E as the release level, 9.5/8.5 configuration records display 9.5E/8.5E as the release level, and 9.6/8.6 configuration records display 9.6B/8.6B as the release level (until there is another release of 9.6/8.6). Although recently created 8.4 configuration records display 8.4E, they can be used on any 8.4 O.S. level. (The same logic applies to allmajor release levels. See Field Bulletin #363, "MPx Configuration Records".) EXTTAPE is used to save all 8.4 configuration records, and EXTTAPE must be used to restore 8.4 configuration records. In addition, configuration records for 8.4 O.S. levels that are currently transmitted from Software Distribution must be saved on the destination system with EXTTAPE and restored with EXTTAPE before they can be used. ORIGINATOR: Nancy Prentiss SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB033 Pg001 FIB 00034 10/30/87 **** Warning During System Configuration Record Install - 8/96A *** BOSS/VS Levels 8/9.6A and B Upon attempt to install a new system configuration record on an MPx system, the following message may occur: "WARNING: Stack approaching maximum size, (2,1,32,1) If you find yourself getting logged off without warning, your stack probably needed to exceed the maximum size allowed for a segment. 'CR' to continue:" This will occur only when the MPx INSTALL CONFIGURATION utility is executed through the UTILITY menus, and a number other than zero is entered for "NUMBER OF COPIES TO PRINT". After the warning message, just enter a carriage return and continue with the installation. If the users stack is large prior to going into the UTILITY menus, the user may actually be logged off. A work-around to avoid this problem is to call the configuration installation utility directly from command mode. The utility name is CONFIG.MGR. This problem is scheduled to be fixed in 9/8.7. ORIGINATOR: Dale Jensen SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB034 Pg001 FIB 00035 11/02/87 *** Bootable O.S. & Diagnostic Tape Information *** 810 and 9xxx systems boot from tape using the first file on tape, 7xxx and 8xxx systems boot from tape using the second file on tape. Therefore the files must be placed on tape in the proper order to make the tape bootable. The file order (if any additional files are on the tape) after the first two files is not relevant to the tape boot process. This allows a tape to be used for more than one system type on the same O.S. release (810/8xxx, 8xxx/9xxx). Since the software support for the 810 ended at release 8.4D and the first 9xxx release was 9.5C, there is no problem with utilization of the first file. Use the SAVERESTORE utility, save files to tape option, to create bootable tapes. __________________________O.S. TAPE BOOT INFORMATION____________________________ O.S. image files are identified as follows: (DISK).Rxxx.INST.OSN.ATxxxxxxxxx : :: : :* - T=1/2" tape; C=1/4" tape (7xxx); V=disk : : : * - A=9xxx (or 810) tape; B=7xxx/8xxx tape; U=disk : * - releases prior to 9.6C will display OS0, 9.6C & later releases will display OSN * To make a bootable 8xxx/9xxx 1/2" O.S. tape place files on tape as follows: 1. .Rxxx.INST.OSN.ATxxxxxxxxx (9xxx 1/2" tape image file) 2. .Rxxx.INST.OSN.BTxxxxxxxxx (7xxx/8xxx 1/2" tape image file) 3. No other files are required but any number may be added after the second file * To make a bootable 7xxx 1/4" O.S. tape place files on tape as follows: 1. .Rxxx.INST.OSN.ATxxxxxxxxx (any file will work as the first file) 2. .Rxxx.INST.OSN.BCxxxxxxxxx (7xxx 1/4" tape image file) 3. No other files are required but any number may be added after the second file. __________________________DEMON TAPE BOOT INFORMATION___________________________ DEMON tape images are identified as follows: (DISK).Rxxx.INST.OS3.ADxxxxxxxxx :: :* - C=1/4" tape; D=1/2" tape; V=disk : * - A=9xxx (or 810) tape; B=7xxx/8xxx tape; U=disk * To make a bootable 8xxx/9xxx 1/2" DEMON tape place files on tape as follows: 1. .Rxxx.INST.OS3.ADxxxxxxxxx (9xxx DEMON 1/2" tape image file) 2. .Rxxx.INST.OS3.BDxxxxxxxxx (7xxx/8xxx 1/2" tape image file) 3. All of the files in the OS3 node should be placed after the second file. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB035 Pg001 * To make a bootable 7xxx 1/4" DEMON tape place files on tape as follows: 1. .Rxxx.INST.OS3.ADxxxxxxxxx (any file will work as the first file) 2. .Rxxx.INST.OS3.BCxxxxxxxxx (7xxx 1/4" DEMON tape image file) 3. All of the files in the OS3 node should be placed after the second file. __________________________REMIDI TAPE BOOT INFORMATION__________________________ Remidi requires various image files depending on system type. 810 systems require only one image file for disk and one for tape (requires one boot tape, one file as the first file on the tape). 7xxx systems require two image files for disk and two for tape (requires two boot tapes, one file as the second file on each tape). 8xxx systems require only one image file for disk and one for tape (requires one boot tape, one file as the second file on the tape). 9xxx systems require two image files for disk and four for tape (requires four boot tapes, one file as the first file on each tape). REMIDI image files are identified as follows: (DISK).Rxxx.INST.REMIDI.ADAxxxxxx (9xxx 1/2" tape image A) ::: ::* - A=tape image A or disk image A;B=tape image B; :: C=tape image C or disk image C;D=tape image D;. :: M=MPC tests;number= part of revision level :: (7xxx/8xxx only) :: :* - C=1/4" tape ;D=1/2" tape ;V=disk : * - A=9xxx (or 810) ;B=7xxx/8xxx * To make bootable 1/4" 7xxx REMIDI tapes, two tapes are required, place files as follows: I. Tape 1: 1. .Rxxx.INST.REMIDI.BDMxxxxxx (any file will work as the first file) 2. .Rxxx.INST.REMIDI.BC#xxxxxx (7xxx 1/4" REMIDI - the # will be some numeric revision number) II. Tape 2: 1. .Rxxx.INST.REMIDI.BDMxxxxxx (any file will work as the first file) 2. .Rxxx.INST.REMIDI.BCMxxxxxx (7xxx 1/4" REMIDI MPC tests) * To make a bootable 8xxx REMIDI tape place files as follows: 1. .Rxxx.INST.REMIDI.BDMxxxxxx (any file will work as the first file) 2. .Rxxx.INST.REMIDI.BD#xxxxxx (8xxx 1/2" REMIDI - the # will be some numeric revision number) * To make bootable 9xxx REMIDI tapes, four tapes are required, place files as follows: I. Tape 1: 1. .Rxxx.INST.REMIDI.ADAxxxxxx (9xxx REMIDI image A) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB035 Pg002 II. Tape 2: 1. .Rxxx.INST.REMIDI.ADBxxxxxx (9xxx REMIDI image B) III. Tape 3: 1. .Rxxx.INST.REMIDI.ADCxxxxxx (9xxx REMIDI image C) IV. Tape 4: 1. .Rxxx.INST.REMIDI.ADDxxxxxx (9xxx REMIDI image D) ORIGINATOR: N. Jones SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB035 Pg003 FIB 00036 12/02/87 *** 8.5-9.5 Spooler class definitions are not converted on 8.6-9.6A/B *** When a system is upgraded from 9/8.5 or below, the spooler class definitions are not converted automatically. This is a bug on 9/8.6A/B and will be fixed on 9/8.6C. The workaround is to copy the .SYSDATA.SSM.MOUNTMSG.TEXT file to .SYSDATA.SSM.MOUNT before the upgrade. After the file is copied, the system can be reloaded and the class definition file is converted. ORIGINATOR: Leo Sanders SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB036 Pg001 FIB 00037 12/02/87 *** Terminal model numbers are used in TERM.CONFIG on 9.6A and up *** On 9/8.6A and higher, model numbers will be used to select the necessary terminal. A description of the terminals and model numbers are shown below: MODEL NUMBER DESCRIPTION ------------ ----------- 4300 7250 4301 7270 4105 S/10 4308 ODT 4309 EVDT 4310 EDT 4313 DT-4313 4314 DT-4314 The DT-4312 terminals are configured as a 4309. ORIGINATOR: Leo Sanders SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB037 Pg001 FIB 00038 12/02/87 *** Release 9.6B/8.6B Software Announcement [ WPSS 151 ] *** MAI Basic Four, Inc. is pleased to announce that the new system software revisions 9.6B/8.6B, are now available. The 9.6B revision is the recommended revision for MPx 9000, 9100, and 9500 Series Systems. The 8.6B revision is the recommended revision for MPx 7000, 7100, and 8000 Series Systems. *************************************************************** * * * PLEASE READ THE INSTALLATION INSTRUCTIONS BEFORE ATTEMPTING * * INSTALLATION OR UPGRADE. * * * * RELEASE 9.6B/8.6B CONTAINS ALL THE NEW FEATURES AND ENHANCE-* * MENTS OF RELEASE 9.6A/8.6A, WHICH ARE DOCUMENTED IN THE * * 9.6A/8.6A SOFTWARE ANNOUNCEMENT, #148. BOTH THE 9.6A/8.6A * * AND 9.6B/8.6B SOFTWARE ANNOUNCEMENTS EXIST AS SERIAL FILES * * ON THE OFFICIAL 9.6B/8.6B RELEASE TAPE. THESE DOCUMENTS CAN * * BE PRINTED BY SUBMITTING THE FILES TO THE PRINTER. SEE THE * * SECTION ON "GENERAL INFORMATION" FOR THE FILE NAMES. * * * * UPGRADES FROM RELEASE LEVELS 8.4D AND BELOW REQUIRE A CON- * * VERSION TO THE NEW FILE SYSTEM. THIS ANNOUNCEMENT DOES NOT * * CONTAIN INSTRUCTIONS FOR THIS CONVERSION. THESE INSTRUCTIONS* * APPEAR IN THE SOFTWARE ANNOUNCEMENTS FOR RELEASES 8.4E AND * * 8.5A/B/C/D/E, AS WELL AS IN THE "BOSS/VS FILE CONVERSION * * USER GUIDE" M 5185A. THE CONVERSION CANNOT BE PERFORMED * * WITHOUT THESE INSTRUCTIONS. * * * * PROGRAMS WRITTEN OR MODIFIED ON 9.6B/8.6B WILL NOT RUN ON * * RELEASES PRIOR TO 9.6A/8.6A WITHOUT RECOMPILATION. NEW * * BUSINESS BASIC 86 FEATURES INTRODUCED IN 9.6A/8.6A CANNOT * * BE USED IN PROGRAMS WHICH ARE GOING TO BE RUN ON 9.5/8.5 OR * * 8.4 O.S. LEVELS. * * * * 9.6A/8.6A INTRODUCED NEW SYSTEM STARTUP PROCEDURES FOR * * MAGNET, SPOOLER, AND JOB MANAGER. IT IS ESSENTIAL TO REVIEW * * THE SYSTEM STARTUP SECTION BEFORE ATTEMPTING INSTALLATION * * OR UPGRADE. * * * *************************************************************** Copyright 1987, Rev. 1987, MAI Basic Four, Inc. All rights reserved. C O N T E N T S _ _ _ _ _ _ _ _ 1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . 2 2 FIXES IN THIS RELEASE . . . . . . . . . . . . . . . . . 3 2.1 UTILITIES . . . . . . . . . . . . . . . . . . . . . . 3 2.1.1 JOB MANAGER Utilities . . . . . . . . . . . . . . . 3 2.1.2 SAVERESTORE Utility . . . . . . . . . . . . . . . . 3 2.1.3 SPOOLER Utilities . . . . . . . . . . . . . . . . . 3 2.1.4 UPDATE Utility . . . . . . . . . . . . . . . . . . . 4 2.2 BASIC . . . . . . . . . . . . . . . . . . . . . . . . 4 2.3 COMMUNICATIONS . . . . . . . . . . . . . . . . . . . . 4 2.3.1 File Transfer Facility (FTF) . . . . . . . . . . . . 4 2.3.2 Transportable Batch Communications (TBC) . . . . . . 4 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg001 2.3.2.1 UJCL . . . . . . . . . . . . . . . . . . . . . . . 4 3 HISTORY . . . . . . . . . . . . . . . . . . . . . . . . 6 4 BOSS/VS . . . . . . . . . . . . . . . . . . . . . . . . 9 4.1 GENERAL INFORMATION . . . . . . . . . . . . . . . . . 9 4.1.1 Software Announcement . . . . . . . . . . . . . . . 9 4.2 DIAGNOSTICS . . . . . . . . . . . . . . . . . . . . . 10 4.2.1 REMIDI . . . . . . . . . . . . . . . . . . . . . . . 10 4.2.1.1 REMIDI for MPx 7000, 7100, and 8000 Series Systems 10 4.2.1.1.1 Using REMIDI on 7000, 7100, and 8000 Systems . . 10 4.2.1.2 REMIDI for MPx 9000, 9100, and 9500 Series Systems 12 4.2.1.2.1 Changing the Load Sector for Slot Three . . . . 12 4.3 CONFIGURATIONS . . . . . . . . . . . . . . . . . . . . 14 4.3.1 Configurations for the MPx 7000, 7100, and 8000 . . 14 4.3.2 Configurations for MPx 9000 and 9100 Series Systems 15 4.3.3 Configurations for MPx 9500 Series Systems . . . . . 16 4.4 BASIC . . . . . . . . . . . . . . . . . . . . . . . . 17 4.4.1 Multi-key Field Types . . . . . . . . . . . . . . . 17 5 HARDWARE . . . . . . . . . . . . . . . . . . . . . . . . 18 5.1 LARLS FOR PCBAS FOR THE MPX 7000, 7100, AND 8000 . . . 18 5.2 LARLS FOR PCBAS FOR THE MPX 9000, 9100, AND 9500 . . . 19 5.3 LOCAL AREA NETWORK CONTROLLER (LAN) . . . . . . . . . 21 6 INSTALLATION . . . . . . . . . . . . . . . . . . . . . . 22 6.1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . 22 6.2 NEW INSTALLATION . . . . . . . . . . . . . . . . . . . 22 6.2.1 Installing the O.S. . . . . . . . . . . . . . . . . 22 6.2.1.1 ALT LOAD . . . . . . . . . . . . . . . . . . . . . 23 6.2.1.2 ENTER A TYPE 3 LOAD (SPECIAL FUNCTIONS) . . . . . 23 6.2.1.2.1 OPTION 1 (CHANGE VOLUME LABEL INFORMATION) . . . 23 6.2.1.2.2 OPTION 2 (UPDATE FAMILY INFORMATION) . . . . . . 24 6.2.1.2.3 OPTION 3 (INITIALIZE FAMILY DIRECTORY) . . . . . 24 6.2.1.2.4 OPTION 4 (CHANGE INSTALLATION PARAMETERS) . . . 24 6.2.1.3 Restoring the O.S. . . . . . . . . . . . . . . . . 25 6.3 8000 UPGRADE FROM RELEASE LEVELS ABOVE 8.4D . . . . . 27 6.3.1 Saving Files to Tape . . . . . . . . . . . . . . . . 27 6.3.2 Operating System Update . . . . . . . . . . . . . . 27 6.3.2.1 Installing the O.S. . . . . . . . . . . . . . . . 27 6.3.2.1.1 ALT LOAD . . . . . . . . . . . . . . . . . . . . 27 6.3.2.1.2 CHANGE INSTALLATION PARAMETERS . . . . . . . . . 27 6.3.2.2 Restoring the O.S. . . . . . . . . . . . . . . . . 28 6.3.2.3 Installing the Configuration Record . . . . . . . 29 6.3.3 UPDATING OTHER O.S. SLOTS . . . . . . . . . . . . . 30 6.3.3.1 UPDATING SLOT ONE (1) . . . . . . . . . . . . . . 30 6.3.3.2 UPDATING WCS SLOT TWO (2) . . . . . . . . . . . . 31 6.3.3.3 UPDATING SLOT THREE (3) . . . . . . . . . . . . . 31 6.3.3.3.1 Updating O.S. Slot Three (3) . . . . . . . . . . 31 6.3.3.4 Updating WCS Slot Three (3) . . . . . . . . . . . 32 6.3.3.4.1 On 7000/7100 Systems and 8000 Systems with LAN . 32 6.3.3.4.2 On 8000 Systems Without LAN . . . . . . . . . . 33 6.3.4 SLOT INFORMATION . . . . . . . . . . . . . . . . . . 33 6.4 UPGRADING TO 9.6B AND THE MPX 9000, 9100, AND 9500 . . 35 6.4.1 SPECIAL CONSIDERATIONS . . . . . . . . . . . . . . . 35 6.4.2 PRINTING OUT THE TERMINAL CONFIGURATION RECORD . . . 35 6.4.3 SAVING FILES TO TAPE . . . . . . . . . . . . . . . . 35 6.4.4 OPERATING SYSTEM UPDATE . . . . . . . . . . . . . . 36 6.4.4.1 ALT LOAD . . . . . . . . . . . . . . . . . . . . . 36 6.4.4.2 TYPE 3 LOAD (SPECIAL FUNCTIONS) . . . . . . . . . 36 6.4.4.2.1 Updating Installation Parameters . . . . . . . . 36 6.4.4.2.1.1 OPTION 4 (CHANGE INSTALLATION PARAMETERS) . . 36 6.4.4.2.1.2 Sizing the Dump Area . . . . . . . . . . . . . 37 6.4.4.2.2 Restoring the O.S. Files . . . . . . . . . . . . 38 6.4.4.2.3 Installing the Configuration Record . . . . . . 38 6.4.4.3 UPDATING OTHER O.S. SLOTS . . . . . . . . . . . . 39 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg002 6.4.4.3.1 Updating Slot One (1) . . . . . . . . . . . . . 39 6.4.4.3.2 Updating WCS Slot Two (2) . . . . . . . . . . . 40 6.4.4.3.3 Updating Slot Three (3) . . . . . . . . . . . . 41 6.4.4.3.3.1 Updating O.S. Slot Three (3) . . . . . . . . . 41 6.4.4.3.3.2 Changing the Load Sector for Slot Three (3) . 41 6.4.4.3.3.3 Updating WCS Slot Three (3) . . . . . . . . . 41 6.4.5 Slot Information . . . . . . . . . . . . . . . . . . 42 6.5 SYSTEM STARTUP . . . . . . . . . . . . . . . . . . . . 43 6.5.1 Standard Startup Command File on 9.6B/8.6B BOSS/VS . 43 6.5.1.1 Command File Definitions . . . . . . . . . . . . . 43 6.5.2 Implications . . . . . . . . . . . . . . . . . . . . 44 7 WARNINGS AND CAUTIONS . . . . . . . . . . . . . . . . . 48 7.1 MPX 7000, 7100, 8000, 9000, 9100 & 9500 SERIES SYSTEMS 48 7.1.1 BOSS/VS . . . . . . . . . . . . . . . . . . . . . . 48 7.1.1.1 UTILITIES . . . . . . . . . . . . . . . . . . . . 48 7.1.1.1.1 CONFIG.MGR . . . . . . . . . . . . . . . . . . . 48 7.1.1.1.2 FAMILY . . . . . . . . . . . . . . . . . . . . . 48 7.1.1.1.3 GETDEVINFO . . . . . . . . . . . . . . . . . . . 49 7.1.1.1.4 JOB MANAGER . . . . . . . . . . . . . . . . . . 49 7.1.1.1.5 MOUNT . . . . . . . . . . . . . . . . . . . . . 50 7.1.1.1.6 SAVERESTORE . . . . . . . . . . . . . . . . . . 50 7.1.1.1.6.1 Restoring ISDC Code Files and REMIDI . . . . . 50 7.1.1.1.7 SPOOLER . . . . . . . . . . . . . . . . . . . . 50 7.1.1.1.8 EXTTAPE . . . . . . . . . . . . . . . . . . . . 51 7.1.1.1.9 TERM.CONFIG . . . . . . . . . . . . . . . . . . 51 7.1.1.1.10 TERM.TABLE . . . . . . . . . . . . . . . . . . 51 7.1.1.1.11 UPDATE . . . . . . . . . . . . . . . . . . . . 51 7.1.1.1.12 UPDATE.OS . . . . . . . . . . . . . . . . . . . 51 7.1.1.1.13 MCSI . . . . . . . . . . . . . . . . . . . . . 52 7.1.1.2 LOGON . . . . . . . . . . . . . . . . . . . . . . 52 7.1.1.3 BASIC . . . . . . . . . . . . . . . . . . . . . . 52 7.1.1.3.1 Running SORT from BASIC . . . . . . . . . . . . 52 7.1.1.3.2 MTCS (MCS) Tape Drive . . . . . . . . . . . . . 52 7.1.1.3.3 Program File Compatibility . . . . . . . . . . . 52 7.1.1.3.4 CONSOLELOCK . . . . . . . . . . . . . . . . . . 53 7.1.1.3.5 Multi-Key Files . . . . . . . . . . . . . . . . 53 7.1.1.4 CLI Batch Subsystem . . . . . . . . . . . . . . . 53 7.1.1.5 Communications . . . . . . . . . . . . . . . . . . 53 7.1.1.5.1 MAGNET and File Transfer Facility (FTF) . . . . 53 7.1.1.5.2 Asynchronous Transport Package (ATP) . . . . . . 56 7.1.1.5.3 19.2K BPS Support . . . . . . . . . . . . . . . 56 7.1.2 Hardware . . . . . . . . . . . . . . . . . . . . . . 56 7.1.2.1 Terminals . . . . . . . . . . . . . . . . . . . . 56 7.1.2.2 MCS Board . . . . . . . . . . . . . . . . . . . . 56 7.1.2.2.1 When Upgrading from 8.4D and Below . . . . . . . 56 7.1.2.2.2 MCS Revision "S" . . . . . . . . . . . . . . . . 56 7.2 MPX 9000, 9100 AND 9500 SERIES SYSTEMS ONLY . . . . . 57 7.2.1 BOSS/VS . . . . . . . . . . . . . . . . . . . . . . 57 7.2.1.1 Dumps . . . . . . . . . . . . . . . . . . . . . . 57 7.2.2 HARDWARE . . . . . . . . . . . . . . . . . . . . . . 57 7.2.2.1 IMLC in MPx 9000/9100/9500 Systems . . . . . . . . 57 8 RELATED DOCUMENTATION . . . . . . . . . . . . . . . . . 58 F I G U R E S _ _ _ _ _ _ _ Figure 6-1. Restore Screen . . . . . . . . . . . . . . . . 26 Figure 6-2. Restore Screen . . . . . . . . . . . . . . . . 29 Figure 6-3. Operating System Information . . . . . . . . . 34 Figure 6-4. Restore Screen . . . . . . . . . . . . . . . . 38 Figure 6-5. Operating System Information . . . . . . . . . 42 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg003 1. INTRODUCTION ____________ The 9.6B/8.6B release contains the following enhancements: o Support for the new 4314 terminal, which features: - dual serial ports - 132-character screen o Automatic type conversion of numeric/string fields in Multi-key files. For further information on this new feature, see section 4.4.1. o VFU load is no longer done by the system when a printer is in RESERVE or DISCONNECT mode. This allows the operator to control VFU in the application program. The change makes VFU handling consistent with the 8.4 and 9.5/8.5 Operating System releases. In addition, the 9.6B/8.6B release contains fixes for problems in the JOB MANAGER, SAVERESTORE, UPDATE, and SPOOLER utilities, BASIC, FTF, and TBC. See section 2 for specific fixes. A new configuration record is not required when upgrading from release 9.6A to 9.6B or from release 8.6A to 8.6B. A new configuration record is required, however, when upgrading from 8.4 and 9.5/8.5 releases to 9.6B/8.6B releases. A new configuration record is also required when an upgrade includes new hardware. 2. FIXES IN THIS RELEASE _____ __ ____ _______ 2.1. UTILITIES _________ 2.1.1. JOB MANAGER Utilities ___ _______ _________ 1. SPR 510275 - The JOB DISPLAY detail screen would erroreously show negative workspace usage. 2. SPR 512155 - JOB.MODIFY would hang a terminal when the Operator Flag = FALSE and QUIET = TRUE. 2.1.2. SAVERESTORE Utility ___________ _______ 1. SPR 509944 - The rename delimiter ("^") would not work with SAVERESTORE on a restore. The file specifier, "^&,(family).node.^" would not rename the family as the files were being restored. 2. SPR 506808 - The RENAME option did not check for invalid family name. 2.1.3. SPOOLER Utilities SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg004 _______ _________ 1. SPR 510916 - The following set of circumstances would cause a terminal to hang: a) A serial printer was either offline or its cable had been unplugged. b) The printer was in either RESERVEd or DISCONNECTed mode. c) One user was attempting to OPEN a file to the printer, AND d) One or more other users were attempting to display the status of the printer. 2. SPR 511331 - In RESERVE mode, print positioning was offset to the left by one character position. 3. SPR 510999 - SUSPENDing then DISCONNECTing a printer caused an ERROR 0 to be returned when it was subsequently OPENed in BASIC. 4. SPR 511400 - Stopping a print job at the end of the job sometimes caused a diagnostic dump with the fourtuple 2,0,8,10. 5. SPR 511560 - A Diagnostic dump with the fourtuple 2,0,8,10 would occur when opening a DISCONNECTed printer when the printer was already open. 2.1.4. UPDATE Utility ______ _______ SPR 511907 - UPDATE did a full copy of a Multi-keyed file when only the WRITETHROUGH parameter was being modified. 2.2. BASIC _____ 1. SPR 511723 - The following code, when executed on a high speed terminal, would hang the terminal: 10 INPUT 'KL','TR',A$ 20 PRINT 'KU' Serial terminals were not affected. 2. SPR 510662 - A multi-key file READ with a KEY= clause would sometimes return a false ERROR 11 (Duplicate or Missing Key), even though the record actually existed. This problem occurred when either RIGHT justified string fields or "C" type (space padded) string fields were referenced with a KEY= clause, using a KEY value that was shorter than the width of the field. 3. SPR 513044 - On 9xxx systems only, a READ with the IND option to the end of file would sometimes cause an ERROR 32. 2.3. COMMUNICATIONS ______________ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg005 2.3.1. File Transfer Facility (FTF) ____ ________ ________ _____ 1. SPR 508911 - Transmitting a program with statement sizes greater than 1024 bytes caused transfer aborts with a Completion Code of 75. The new limit is 2048 bytes, the maximum size of a BASIC statement. 2.3.2. Transportable Batch Communications (TBC) _____________ _____ ______________ _____ 2.3.2.1. UJCL ____ 1. SPR 508910 - If multiple nodes were in the user's prefix, a "Disk Error" message was generated when defining a JCL file name. Now UJCL allows the user prefix to have multiple nodes, and the first node is used to generate the JCL file. 3. HISTORY _______ 8.6A/9.6A Acceptable This release contains the following enhancements: A new and enhanced SPOOLER; new JOB MANAGER utilities, including JOB ACCOUNTING; MAGNET, which includes a Local Area Network and a Wide Area Network; Business BASIC 86, which offers several new BASIC features, including Multi-key Files; 19.2K BPS asyncronous communications; SECURITY utility enhancements; CLI Batch Subsystem; Support for 24 megabytes of main memory and 255 devices on MPx 9500 Series Systems. 8.5E/9.5E Acceptable This release provided improvements to the COPY, SAVERESTORE, and UPDATE.RIGHTS utilities, BASIC, the File System, and Type 3 Load Backup. 8.5D/9.5D Obsolete Enhancements include: A new CONFIG.MGR utility for displaying and installing configuration records; Four Spooler fixes; DISKANALYZER reconstruction of serial files; Manual selection of different print modes on DMP printers; an optional enhanced ATP package. 8.5C/9.5C Obsolete Enhancements include: Expanded ERRORLOG reporting; Optimization of DataWord files; Number of logical channels increased to 64; Support for 8 bit character sets; DISKANALYZER reporting of required disk space for reconstruction. Mpx 9000 and 9500 systems only: 32 bit CPU; increased main memory; number of maximum devices increased to 164; new DMA controller for increased performance; enhanced CPU processing for faster arithmetic and logical operations; RSTACK cache; overall performance increase which is 2-3 times that of 7000/7100/8000 systems; support for the faster 8-inch fixed disk. Mpx 9500 only: DATA and CODE caches for additional increased performance. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg006 8.5B Obsolete In this release the system model number has been included in the configuration record, the COMPARE utility has been fixed so that it completely compares BASIC program files, and a new TBC AUTODIAL feature allows for definition and retrieval of multiple station lists. 8.5A Obsolete Enhancements include: Increased file system concurrency for greater throughput, support for 7000/7100 series systems, proportional growth for DIRECT and SORT files, maximum number of open files increased to 512, maximum number of tasks sharing same file increased to 512, file selectable write-through, DISKANALYZER also available in stand-alone mode, DISKANALYZER reconstruct of directory and available space files, maximum number of system printers increased to 99, system dumps written directly to tape, system support for the DMP serial printer, new terminal services error utility, DataWord printer queue enhancements, enhanced SAVERESTORE utility. 8.4E Acceptable This release contains all the features of the 8.5A/B/C/D releases, with the exception of the 8.5 performance enhancements. 8.4D Obsolete Contained fixes for BASIC PRECISION, EXTTAPE, COBOL, and FILESIZE. 8.4C Obsolete Enhanced features included: Buffered Magnetic Tape Controller, 1/2" tape support, DEDICATE with expanded error reporting, new ISDC OS for 4-way, 8-way and 16-way, FILESIZE utility. 8.4B Obsolete Enhanced features include: 8 megabytes of main system memory, 16-port Asynchronous Controller, point-to-point file specification, QUIET mode for utilities, BASIC statement numbers up to 16000, Buffered Magnetic Tape Controller (BMTC) 1/4" tape support, S/10 Industry Standard Printer as slave printer. 8.4A Obsolete This release contained significant enhancements including 6 megabytes of main system memory, 96 devices, 84 total serial devices, disk to disk sequential family backup, enhanced hardware error log, system load progress monitor, and fast reconstruct utility. 8.2C Obsolete This release contained a WCS fix to support rezero fault clear, disk error recovery and a fix to the IMLC. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg007 8.2B Obsolete This release contained all of the above features but was required for the 8000 Series systems due to a change in the WCS image for that hardware. 8.2A Obsolete This release contained significant enhancements providing NO EXTEND BASIC, 68 serial devices, math functions, X.25 Communications, DataWord 3.0. File System write through and BULLETIN board availability. 8.1B Obsolete Enhanced features include: 31 logical units in BASIC, increase in file system cache from 208 to 225 unique files, MULTIREELSR, family image backups, SAVERESTORE backup files having the Lack-of-Integrity bit set. Bugs were fixed in DISKANALYZER, SAVERESTORE and many of the system dumps. 8.1A Obsolete Introduction of the System 810 hardware and BOSS/VS software. 4. BOSS/VS _______ 4.1. GENERAL INFORMATION _______ ___________ 4.1.1. Software Announcement ________ ____________ The 9.6A/8.6A and 9.6B/8.6B Software Announcements exists as serial files on the official 9.6B/8.6B O.S. release tape, which allows the user to print copies, if needed. To print these documents, SUBMIT the following files to the printer: (family).R6BXX.INST.DOC.SA6A.TEXT 9.6A/8.6A (family).R6BXX.INST.DOC.SA6B.TEXT 9.6B/8.6B 4.2. DIAGNOSTICS ___________ Please see the installation sections of this announcement for instructions on how to install DEMON and REMIDI. Further information on these diagnostics can be found in DOCWRITER, which can be accessed by entering !DOCWRITER in command mode. 4.2.1. REMIDI ______ NOTE: Running UPDATE.OS automatically updates the Load Sectors for the disk. However, running UPDATE.WCS does not. (The Load Sectors are displayed at the top of the OSINFO screen.) It is therefore necessary to run UPDATE.LD for REMIDI on newly initialized systems packs, or whenever question marks ("?/?") appear in Load Sector 2 on the OSINFO screen. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg008 4.2.1.1. REMIDI for MPx 7000, 7100, and 8000 Series Systems ______ ___ ___ _____ _____ ___ ____ ______ _______ REMIDI version BV5C0101 includes all micro-diagnostics except those for the MPC and LAN controllers. It is loaded into WCS slot 2 and is used on MPx 7000, 7100, and 8000 Series Systems. REMIDI version BVM6A0803 contains micro-diagnostics for the MPC and LAN controllers. It is loaded into WCS slot 3 on all 7000/7100 Series Systems and on 8000 Series Systems with LAN controllers. This version of REMIDI is used on MPx 7000/7100 Series Systems for the MPC and LAN controllers, and on 8000 Series Systems for LAN controllers only. If a LAN controller is not present on an 8000 Series System, the BVM6A0803 version of REMIDI is not needed. The Load Directory controls which version of REMIDI will be executed. The UPDATE.LD utility is used to update the Load Directory. See the following section for instructions on running UPDATE.LD. 4.2.1.1.1. Using REMIDI on 7000, 7100, and 8000 Systems _____ ______ __ _____ _____ ___ ____ _______ Disregard this section if your 8000 Series System does not have a LAN controller. (In this case only REMIDI version BV5C0101 is used, and it is not necessary to update the Load Directory.) Since REMIDI is a WCS Image, two WCS slots will be required for the two REMIDI versions. The extra slot will be provided by the DEMON WCS slot. It is necessary to update the Load Directory, using the UPDATE.LD utility, to have DEMON use OS slot 3 and WCS slot 0. (DEMON and the BOSS/VS Operating System both use the same WCS image). UPDATE.LD will also be required to toggle between the two versions of REMIDI, since only one version can run at a time. For MPx 7000/7100 Series Systems and 8000 Series Systems with LAN controllers, the following steps must be taken: NOTE: Lines preceded by an "*" require operator input. 1) Install the REMIDI version BVM6A0803 WCS in slot 3 with UPDATE.WCS: * Input in command mode !UPDATE.WCS. Update.WCS 8.6xx.x * ENTER WCS Slot (0..3) :3 Available disk units are :0,1 * Disk to update :0 * WCS image file (=first found :.R6xxx.INST.REMIDI.BVM6A0803 Updating Disk Unit 16 sector 415 WCS update completed ! NOTE: The level of the WCS image file must be known. This level is also the operating system software level, (i.e. .R6Bxx.). 2) Update the Load Directory for DEMON by using UPDATE.LD: * Input in command mode !UPDATE.LD Update Load Directory Utility SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg009 Disks (Unit number) on line : 0(16),1(17) Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 6.2.x.x R 6B*xx (date) B 5.3.11 1 1/1 | 6.2.x.x R 6B*xx (date) B 5.3.11 2 0/2 | B 5.1.4 R 3 3/3 | 6.1.39.11 DEMON 02/23/87 B 6.1.5 R * New OS slot (0,1,3): 3 * New WCS slot (0..3): 0 or 1 (Slot booted from) * Load sector (0..3) : 3 Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 6.2.x.x R 6B*xx (date) B 5.3.11 1 1/1 | 6.2.x.x R 6B*xx (date) B 5.3.11 2 0/2 | B 5.1.4 R 3 3/0 | 6.1.39.11 DEMON 02/23/87 B 6.1.5 R NOTE: Notice the change in Load Sector 3. It went from 3/3 to 3/0. DEMON was using WCS slot 3; it is now using WCS slot 0. Only one version of REMIDI will run at a time. The version that will run is dependent on how the Load Directory for REMIDI (load sector 2) is set up. The standard version, BV5C0101, which resides in WCS slot 2, has an OS/WCS of 0/2. The MPC/LAN version, BVM6A0803, which resides in WCS slot 3, has an OS/WCS of 0/3. Use UPDATE.LD to update the Load Directory to designate which version to run. To test the MPC and LAN controllers with REMIDI version BVM6A0803, execute UPDATE.LD, as in step 2 above, using the following: * New OS slot (0,1,3): 0 * New WCS slot (0..3): 3 * Load sector (0..3) : 2 To go back to the standard REMIDI version, BV5C0101, which tests the CPU and main memory, use the following in UPDATE.LD: * New OS slot (0,1,3): 0 * New WCS slot (0..3): 2 * Load sector (0..3) : 2 NOTE: The Load Directory should stay in the above setup in case the system CPU needs to be tested in a down condition. 4.2.1.2. REMIDI for MPx 9000, 9100, and 9500 Series Systems ______ ___ ___ _____ _____ ___ ____ ______ _______ Another version of REMIDI contains micro-diagnostics for MPx 9000, 9100, and 9500 Series Systems. It consists of two sections, AVA6A0104, which is loaded into WCS slot 2, and AVC6A0104, which is loaded into WCS slot 3. 4.2.1.2.1. Changing the Load Sector for Slot Three ________ ___ ____ ______ ___ ____ _____ Because the second section of the 9xxx version of REMIDI is in WCS slot 3, the Load Directory must be changed to point to another WCS slot for DEMON. The 9.6B O.S. and DEMON share SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg010 the same WCS code, therefore, we can point to the WCS slot used by the 9.6B O.S. Update the Load Directory for DEMON by using the UPDATE.LD utility: * Input in command mode !UPDATE.LD Update Load Directory Utility 9.6xx.xx Disks (Unit number) on line : 0(16),1(17) Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 6.2.x.x R 6B*xx (date) A 6.4.20 1 1/1 | 6.2.x.x R 6B*xx (date) A 6.4.20 2 0/2 | A 6.1.4 R 3 3/3 | 6.1.39.11 DEMON 02/23/87 A 6.1.5 R * New OS slot (0,1,3): 3 * New WCS slot (0..3): 1 (Slot booted from) * Load sector (0..3) : 3 Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 6.2.x.x R 6B*xx (date) A 6.4.20 1 1/1 | 6.2.x.x R 6B*xx (date) A 6.4.20 2 0/2 | A 6.1.4 R 3 3/1 | 6.1.39.11 DEMON 02/23/87 A 6.1.5 R Notice that Load Sector 3 is now pointing to WCS slot 1. 4.3. CONFIGURATIONS ______________ NOTE 1: The number of "High Activity Tasks" is approximate and largely dependent on the application. The relative relationship of the numbers between configurations is more important than the actual numbers themselves. NOTE 2: System configurations of the MPx 9000, 9100, and 9500 Series Systems are based on the use of the LS-700 power supply mainframes. Original 810 systems will not meet all defined maximum configurations listed. 4.3.1. Configurations for the MPx 7000, 7100, and 8000 ______________ ___ ___ ___ _____ _____ ___ ____ The maximum configuration for MPx 7000, 7100, and 8000 Series Systems, Models 7030, 7130, and 8030, is as follows: 116 Devices - A combination of 8-ways, 16-ways, the 4 ports on the MCS PCBA, MDTs and HVDTs up to a total of 116 devices are supported. 3 CPU sets 10 ISDCs: 16-ways (7 maximum) and/or 8-ways 32 Ghost tasks 24 High speed videos (HVDT) 8 Disk drives 4 Parallel printers 2-8 Megabytes of memory 2 Magnetic tape drives (MTR, MTS and/or MCS) 4 Intelligent Multi-Line Controllers (IMLC) 8 DataWord II terminals SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg011 4 TBC lines 64 3270 terminals 8 X.25 lines 2 Auto-Call Units (ACU) 99 Serial printers 99 System printers (total serial and parallel not to exceed 99) 2 Buffered Magnetic Tape Controllers 27 High activity concurrent tasks 1 LAN controller NOTE: There is a maximum of 9 memory assembly boards in any combination of 1/2 Mb, 1 Mb, 2 Mb, 4 Mb and BMTCs (a maximum of 3 boards per chassis). Models 7010/7110/8010 and 7020/7120/8020 have the same configuration limits as Models 7030 and 8030 above, with the following limitations: 7010/7110/8010 7020/7120/8020 1 CPU set 2 CPU sets 2-4 Mb memory 2-6 Mb memory 20 Devices 52 Devices 12 Concurrent tasks 20 Concurrent tasks (high activity) (high activity) 19 System printers 51 System printers 4.3.2. Configurations for MPx 9000 and 9100 Series Systems ______________ ___ ___ ____ ___ ____ ______ _______ The maximum configuration for MPx 9000 and 9100 Series Systems, Model 9020 and model 9120 is as follows: 116 Devices - A combination of 8-ways, 16-ways, the 4 ports on the MCS PCBA, MDTs and HVDTs up to a total of 116 devices are supported. 2 CPU sets with Evaluation Stack and Rstack Cache 10 ISDCs: 16-ways (6 maximum) and/or 8-ways (10 maximum) 32 Ghost tasks 24 High speed videos (HVDT) 12 8-inch fixed or 8 14-inch disk drives 8 Parallel printers 4-12 Megabytes of memory 2 Magnetic tape drives including MTR, MTS and/or MCS (1 maximum) 4 Intelligent Multi-Line Controllers (IMLC) 8 Dataword II terminals 4 TBC lines 64 3270 terminals 8 X.25 lines 2 Auto-Call Units (ACU) 99 Serial printers 99 System printers (total serial and parallel not to exceed 99) 4 DMA controllers 2 Buffered Magnetic Tape Controllers 43 High activity concurrent tasks 1 LAN controller Model 9010 and 9110 has the same configuration limits as the 9020 and 9120 above, with the following exceptions: 1 CPU set with Evaluation Stack and SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg012 Rstack Cache 68 Devices 10 ISDCs: 16-ways (4 maximum) and/or 8-ways (8 maximum) 67 Serial printers 75 System printers (total serial and parallel not to exceed 75) 26 High activity concurrent tasks 4.3.3. Configurations for MPx 9500 Series Systems ______________ ___ ___ ____ ______ _______ The maximum configuration for MPx 9500 Series Systems, Model 9530, is the same as the maximum configuration for the MPx 9000 and 9100 Series Systems, Models 9020 and 9120 with the following exceptions: 3 CPU sets with Evaluation Stack Rstack Cache Code Cache Data Cache 255 Devices 16 ISDCs: 16-ways (16 maximum) and/or 8-ways (16 maximum) 24 Maximum megabytes of main memory (see Hardware section for mandatory revision levels for main memory support above 12 megabytes) 16 8-inch fixed or 8 14-inch fixed disk drives 73 High activity concurrent tasks Models 9510 and 9520 have the same configuration limits as Model 9530 with the following exceptions: 9510 9520 1 CPU set 2 CPU sets (same caches as the 9530) (same caches as the 9530) 10 ISDCs: 16-way (4 maximum) 10 ISDCs: 16-way (6 maximum) 8-way (8 maximum) 8-way (10 maximum) 84 Devices 132 Devices 83 Serial printers 53 Concurrent tasks 91 System printers (high activity) (total serial and parallel) 32 Concurrent tasks (high activity) 4.4. BASIC _____ 4.4.1. Multi-key Field Types _________ _____ _____ This release of BASIC removes the restriction that the "type" of Multi-key fields must match that of the associated variable or value. The removal of this "type checking" allows a user to do things like write a string into a numeric field or pull a numeric value out of a string field. 5. HARDWARE ________ 5.1. LARLS FOR PCBAS FOR THE MPX 7000, 7100, AND 8000 _____ ___ _____ ___ ___ ___ _____ _____ ___ ____ The Lowest Acceptable Revision Levels for 7000, 7100, and 8000 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg013 PCBAs are as follows: 1) MPC 903500 PCBA-Revision H If used in the MPx 7100 system, remove JMP3 if present and set SW2-1 OFF and SW2-4 OFF MPC 903546 PCBA-Revision B If used in the MPx 7100 system, remove JMP3 if present and set SW2-1 OFF and SW2-2 OFF 2) BMTC 903413 PCBA-Revision R Revision T is required for full MTCS support. Revision U is required for support of the GCR 1/2" (model 4405) tape drive. 3) ACS 903379-001/-002 PCBAs 7000 systems require "Y" or higher. 8000 systems require "L" or higher (T if BMTC). ACS 903379-003 PCBA-Revision AD 7100 systems require "AD" or higher (can also be used in 7000/7100/8000 systems). Board versions -002 or -003 are mandatory for 3 CPU systems. Revision AA and above supports either 7000 or 8000 Series Systems and is required for the 8" 300 MB fix disk. Revision levels V-Y cannot be used on 8000 systems. Revision level Z cannot be used on 7000/7100 systems. 4) MCS 903374 PCBA-Revision L Revision S is switch selectable between MPx 7000/7100/8000 Series Systems or MPx 9000/9100/9500 Series Systems via SW1 on the MCS PCBA. If the MCS PCBA, at revision S, is switch selected for MPx 9xxx Series Systems and installed into an MPx 7000/7100/8000 Series System, it will not load. 5) LAN 903595 PCBA-Revision F 6) Memory (1/2 and 4 MB) 903516 PCBA-Revision A Revision E is required for the 9xxx CPU set. 7) Memory (1 MB) 903349-Revision J Revision V is required for the 9xxx CPU set. 8) MDI 903361 PCBA-Revision L MDI 903408 PCBA-Revision K 9) TDP Controller 903217 PCBA-Revision J Revision K eliminates excessive sector number errors written to the ERROR LOG. TDP Controller 903453 PCBA-Revision A 10) NIMLC Controller 903381 PCBA-Revision E Revision K is mandatory for all (3) mainframe systems and all 9xxx systems. Revision N is intended for international X.25 use only - this revision is not to be installed domestically. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg014 NIMLC Controller 903534 PCBA-Revision D 11) HVDT Controller 903377 PCBA-Revision C 12) 8-Way Controller 903383 PCBA-Revision A 13) Terminator 903199 PCBA-Revision D Revision H creates -004 Assembly. 14) 16-Way Controller 903437 PCBA-Revision J 5.2. LARLS FOR PCBAS FOR THE MPX 9000, 9100, AND 9500 _____ ___ _____ ___ ___ ___ _____ _____ ___ ____ NOTE: An asterisk (*) appears in front of revision levels that are mandatory for main memory support above 12 megabytes. The Lowest Acceptable Revision Levels for PCBAs for MPx 9000, 9100, and 9500 Series Systems are: 1) MCS 903374 PCBA-Revision L Revision S is switch selectable between MPx 7000/7100/8000 Series Systems or MPx 9000/9100/9500 Series Systems via SW1 on the MCS PCBA. If the MCS PCBA is switch selected for MPx 7000/7100/8000 systems and installed into an MPx 9000/9100/9500 system, board addresses 32 thru 47 are reserved for the IMLC PCB only. * Revision "T" is required for main memory support above 12 megabytes. 2) AMS 903548 PCBA-Revision F * Revision "N" (-002) is required for main memory support above 12 megabytes. 3) ESTK 903552 PCBA-Revision G * Revision "J" is required for main memory support above 12 megabytes. 4) IDC 903550-001 PCBA-Revision P (with cache) IDC 903550-002 PCBA-Revision P (without cache) Revision J addresses cache timing problems on selected systems. Do not replace the IDC PCBA on an error free system to meet this LARL requirement. However, boards with revision levels below "H" should not be used. 5) IDC64 903597-001 PCBA-Revision E (with cache) IDC64 903597-002 PCBA-Revision E (without cache) * IDC64 PCBA is required for support of main memory above 12 megabytes. 6) DMA 903554 PCBA-Revision H * Revision "G" is required for support of main memory above 12 megabytes. Revision "G" is also required for support of the 600 LPM band printer model 4220. Do not replace revision "G" DMA on an error free system to meet this LARL. 7) IMLC 903381 PCBA-Revision K IMLC 903534 PCBA-Revision D 8) BMTC 903413 PCBA-Revision R Revision "U" is required for support of the GCR tape SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg015 drive model 4405. 9) GCR Minimum Revision Levels It is possible for a hang condition to occur in SAVERSTORE, if the GCR tape drive does not have the following minimum revision levels: IF CARD 403923205 (BEFORE THE LARL WAS 403923202) CP CARD 403864305 (BEFORE THE LARL WAS 403864303) 10) Memory (1/2 and 1 MB) 903349 PCBA-Revision V (Not to be used with greater than 12 megabyte support; must use standard trade-in policies.) 11) Memory (2 and 4 MB) 903516-001,-002, PCBA-Revision E * Revision "J" is required for support of main memory above 12 megabytes. Support of main memory above 12 megabytes is supported on the MPx 9500 Series Systems only. 12) Hi-speed video controller 903377 PCBA-Revision C 13) 8-Way 903383 PCBA-Revision A 14) 16-Way 903437 PCBA-Revision J 15) LAN 903595 PCBA-Revision F The following boards are NOT supported on MPx 9000, 9100, and 9500 Series Systems: 1) 7000/7100/8000 CPU set 2) TDP (Must be replaced by the BMTC for tape support) 3) MPC 5.3. LOCAL AREA NETWORK CONTROLLER (LAN) _____ ____ _______ __________ _____ With the release of the 9.6A/8.6A O.S., a new controller is supported: The Local Area Network controller. The LAN PCBA PN 903595 provides the ability to tie like systems together (MPx to MPx) in a local environment not more than 4000 feet apart. Each system requires one LAN controller and both systems must be on the same O.S. level. The LAN may be installed either to the right of the CPU set(s) after the BMTC PCBA or to the left of the MCS PCBA. Refer to MAGNET section in this document for further information on the Local Area Network. 6. INSTALLATION ____________ 6.1. INTRODUCTION ____________ There are two ways to install 9.6B/8.6B: 1) Install a new system 2) Update a system If you are installing a new system go to section 6.2. If you are upgrading from a level above 8.4D, go to section 6.3. If you are upgrading to 9.6B, go to section 6.4. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg016 Upgrades from release levels 8.4D and below require a conversion to the new file system. This document does not contain instructions for this conversion. These conversion instructions appear in the Software Announcements for release levels 8.4E and 8.5A/B/C/D/E, as well as in the "BOSS/VS FILE CONVERSION USERS GUIDE" M 5185A. The conversion cannot be performed without these instructions. After files have been converted to the new file system, go to section 6.3 in this announcement to complete the installation. Starting with 9.6A/8.6A there is a change in the way terminals are enabled for user logon at system load time. The enable of the TERMINALS group, that allows users to logon, is now under user control, in the startup command file, if the file exists. If the file does not exist, the TERMINALS group is enabled automatically. Refer to the section on System Startup for information on JOB MANAGER, MAGNET and SPOOLER startup procedures. For further information on System Startup see Section 6.5. 6.2. NEW INSTALLATION ___ ____________ The loading of 8.6B is done the same as any other BOSS/VS release. Since the operating system can be released on 1/2" (reel) or 1/4" (cartridge) tape, the word "tape" means either media form. 6.2.1. Installing the O.S. __________ ___ ____ 6.2.1.1. ALT LOAD ___ ____ A) Mount the new release tape in the tape drive. B) Press the "ALTLOAD" button on the front panel. C) Enter the appropriate system disk (0 or 1) or if drives 0 and 1 are both system disks, enter "2" to update both disks. D) Enter a "0" to update WCS slot 0. E) Enter a "Y" to the prompt "Are you SURE you want to overwrite this WCS ? (Y/)". The system automatically updates the OS and WCS slot 0 on both disks, if selected. When this is complete, the system prompts "DONE - READY FOR NORMAL LOAD". Reload by pressing the LOAD button. 6.2.1.2. ENTER A TYPE 3 LOAD (SPECIAL FUNCTIONS) _____ _ ____ _ ____ ________ __________ OPTION 2 (INITIALIZATION OPTIONS) Initialization options 1-4 must be done to insure proper operation. 6.2.1.2.1. OPTION 1 (CHANGE VOLUME LABEL INFORMATION) ______ _ _______ ______ _____ ____________ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg017 All available disk drives will be displayed. An 'available' drive is any drive cabled to the system, whether enabled, disabled, powered ON or OFF. If any drive has a 'MASTER' status, an update will not be allowed. To change a 'MASTER' status, go to the main menu in TYPE 3 LOAD. Choose option 4 (CHANGE MASTER/BACKUP STATUS). ENTER DRIVE NUMBER OF VOLUME LABEL TO CHANGE:__ ( Enter volume label to change. ) The screen will change to display the information for only the drive whose volume label you choose. SERIAL NUMBER _________ ( Enter CR to accept current serial number. ) DISK CONFIGURATION (1=SYSTEM, 2=DATA, 3=BACKUP) ____ ( Enter the appropriate disk type. ) SIZE OF DUMP AREA.....______ x 1024 BYTES ( For system disks only, enter the size of the dump area given by the line below this prompt as the area needed for both main memory and shared memory controllers. ) FILE SYSTEM SPACE ______ x 1000 SECTORS ( Enter the number displayed at the bottom of the screen for this prompt. The display will appear as "CR=X" where X is the maximum space allowed. ) UPDATE DISK VOLUME LABEL (Y/N) __ ( Enter "Y" if above information is correct) 6.2.1.2.2. OPTION 2 (UPDATE FAMILY INFORMATION) ______ _ _______ ______ ____________ The disk information for all drives on the system is displayed and the cursor is positioned at 'FAMILY BASE DRIVE NUMBER'. FAMILY BASE DRIVE NUMBER ___ FAMILY NAME ______ ( CR for default family name ) DRIVE NUMBERS OF OTHER DISKS IN FAMILY? (TYPE SPACES FOR NO OTHER DRIVES) Enter all other drive numbers for this family or spaces if none. The drives must be fixed media drives and in 8.6 format. UPDATE DISK (Y/N)? 6.2.1.2.3. OPTION 3 (INITIALIZE FAMILY DIRECTORY) ______ _ ___________ ______ __________ This option displays all root drives on the system. FAMILY BASE DRIVE NUMBER ______ ( Enter drive number to be initialized. ) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg018 INITIALIZE FAMILY? (Y/N) __ 6.2.1.2.4. OPTION 4 (CHANGE INSTALLATION PARAMETERS) ______ _ _______ ____________ ___________ Only system disks will be displayed. DRIVE NUMBER _______ PRIMARY PREFIX __________________ ( Enter (family).R6B54.SYS. ) Where (family) is the family where the operating system files will reside. SECONDARY PREFIX _______________ ( Enter (family).R6B54.SYS. ) Where (family) is the family where the alternate operating system files will reside. SYSTEM INSTALLATION NAME ________________ Sets the default installation name for a specified system disk. DEFAULT USER FAMILY NAME _____________ ( Enter default user family ) SECURITY (E=ENABLED, D=DISABLED) ___ FILE SYSTEM WRITE THROUGH? (E=ENABLED, D=DISABLED) ___ WRITE THROUGH DEFAULT ON FILE CREATE (E=ENABLED, D=DISABLED):__ This parameter specifies what the default write through will be on a file created through a BASIC file create or through the CREATE utility. UPDATE DISK WITH INSTALLATION PARAMETERS? (Y/N) __ Display: INSTALLATION PARAMETERS SUCCESSFULLY WRITTEN TO DISK. (CR) TO CONTINUE: Option 1 must be done on all disks. Options 2 and 3 must be done for each family. Option 4 must be done on system disks only. 6.2.1.3. Restoring the O.S. _________ ___ ____ Enter SAVERESTORE in a TYPE 2 LOAD and choose OPTION 2 RESTORE FILES FROM TAPE. The screen appears as in figure 6-1. At the prompt for output device, enter a parallel printer so that a listing of the restore operation is produced. This listing can be used to make sure all files were restored correctly. At the prompt, "FILE SPECIFIERS", enter ".". Enter to all other questions. All system files will be restored to disk. Once all files are restored to disk, the message "AUTOMATIC COMPARE, CR TO CONTINUE" appears. This automatically rewinds SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg019 the tape and begins the compare operation. This only occurs when the compare option is selected. When the compare is completed, enter a CTL-IV to return to the "SAVERESTORE" menu. Reload the system and enter a TYPE 1 LOAD. Figure 6-1. Restore Screen ______ ____ _______ ______ ------------------------------------------------------- RESTORE FILES TAPE SET.ID: DRIVE-NUM: REEL-NUM: PRIMARY PREFIX: (FAMILY).NODE. FILE TYPE (D/P/CR=ALL) COMPARE (CR=Y/N) DATE (MM/DD/YY) TIME (HH:MM) OUTPUT DEVICE (CR=VDT) DELETE EXISTING FILES (CR=Y) VERIFY (Y/CR=N) ENTRIES CORRECT (Y/N) -------------------------------------------------------- Now go to section 6.3.3 to continue updating the O.S. slots. 6.3. 8000 UPGRADE FROM RELEASE LEVELS ABOVE 8.4D ____ _______ ____ _______ ______ _____ ____ If you are upgrading to 9.6B, go to section 6.4. 6.3.1. Saving Files to Tape ______ _____ __ ____ Current files must first be backed up to tape, using the standard tape utility, SAVERESTORE. When saving files to tape, send the output from the save process to the printer. These will provide a record of backup for each file. Also it is recommended that all files on tape be compared to the files on the disk. 6.3.2. Operating System Update _________ ______ ______ 6.3.2.1. Installing the O.S. __________ ___ ____ 6.3.2.1.1. ALT LOAD ___ ____ A) Mount the new release tape in the tape drive. B) Press the "ALTLOAD" button on the front panel. C) Enter the appropriate system disk (0 or 1) or if drives 0 and 1 are both system disks, enter "2" to update both disks. D) Enter a "0" to update WCS slot 0. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg020 E) Enter a "Y" to the prompt "Are you SURE you want to overwrite this WCS ? (Y/)". The system automatically updates the OS and WCS slot 0 on both disks, if selected. When this is complete, the system prompts "DONE - READY FOR NORMAL LOAD". Reload by pressing the LOAD button. 6.3.2.1.2. CHANGE INSTALLATION PARAMETERS ______ ____________ __________ Enter a TYPE 3 LOAD (SPECIAL FUNCTIONS) and select OPTION 2 (INITIALIZATION OPTIONS). OPTION 2 (INITIALIZATION OPTIONS) OPTION 4 CHANGE INSTALLATION PARAMETERS Only system disks will be displayed. DRIVE NUMBER _______ PRIMARY PREFIX _______________________ ( Enter (family).R6B54.SYS. ) Where (family) is the family where the operating system files reside. SECONDARY PREFIX _____________________ ( Enter (family).R6B54.SYS. ) Where (family) is the family where the alternate operating system files reside. SYSTEM INSTALLATION NAME _________________________ Sets the default installation name for a specified system disk. DEFAULT USER FAMILY NAME ________ ( Enter default user family ) SECURITY (E=ENABLED, D=DISABLED) ___ FILE SYSTEM WRITE THROUGH? (E=ENABLED, D=DISABLED) ___ WRITE THROUGH DEFAULT ON FILE CREATE (E=ENABLED, D=DISABLED) __ This parameter specifies what the default write through will be on a file created through a BASIC file create or through the CREATE utility. UPDATE DISK WITH INSTALLATION PARAMETERS? (Y/N)__ Display: INSTALLATION PARAMETERS SUCCESSFULLY WRITTEN TO DISK (CR) TO CONTINUE: Reload the system by pressing the LOAD button and enter a TYPE 2 LOAD. 6.3.2.2. Restoring the O.S. _________ ___ ____ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg021 Enter SAVERESTORE in a TYPE 2 LOAD and choose OPTION 2 RESTORE FILES FROM TAPE. The screen appears as in figure 6-2. Figure 6-2. Restore Screen ______ ____ _______ ______ -------------------------------------------------------- RESTORE FILES TAPE SET.ID: DRIVE-NUM: REEL-NUM: PRIMARY PREFIX: (FAMILY).NODE. FILE TYPE (D/P/CR=ALL) COMPARE (CR=Y/N) DATE (MM/DD/YY) TIME (HH:MM) OUTPUT DEVICE (CR=VDT) DELETE EXISTING FILES (CR=Y) VERIFY (Y/CR=N) ENTRIES CORRECT (Y/N) -------------------------------------------------------- At each prompt, enter a . At the prompt, "FILE SPECIFIERS", enter ".". Enter to all other questions. All system files will be restored to disk. Please note that once all files are restored to disk, the message "AUTOMATIC COMPARE, CR TO CONTINUE" appears. This automatically rewinds the tape and begins the compare operation. This only occurs when the compare option is selected. When the compare is completed, enter a CTL-IV to return to the "SAVERESTORE" menu. 6.3.2.3. Installing the Configuration Record __________ ___ _____________ ______ It is necessary to install a new configuration record when upgrading to 8.6B from 8.4 and 8.5 O.S. levels. Until the following procedure is completed, the system will have a minimum configuration. Enter a TYPE 1 LOAD. Set your prefix to .SYSTEM.CONFIG. Before you load the new configuration record, rename the current configuration record on your system, using the RENAME utility, to temporarily preserve it for fall back purposes. (e.g. Add "OLD" in front of the name.) Using the SAVERESTORE utility, restore the new configuration record on tape onto your system. Execute the CONFIG.MGR utility. The CONFIG.MGR utility allows the user to update the system configuration record by installing a new configuration file. This utility displays the current and new configuration record. When "Y" is SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg022 answered to the prompt "Install Configuration:", the new configuration is copied from the file ".SYSTEM.CONFIG.I(serial number)", to the special system area on disk. The new configuration takes effect at the next system load. For further details on the use of the CONFIG.MGR utility, see the 8.5D/9.5D Software Announcement #139. The configuration record file name is derived from the system serial number by changing the leading "8" to an "I" and adding the prefix ".SYSTEM.CONFIG.". EXAMPLE: .SYSTEM.CONFIG.I1030114 for SSN 810-30114 This file should be backed up by the user, in case reinstallation should become necessary. Before going to the next step, LOAD the system so the new configuration record will take affect. If you do not load the system, you will have a minimum configuration and the system will be very slow. 6.3.3. UPDATING OTHER O.S. SLOTS ________ _____ ____ _____ The slots 1, 2, and 3 need to be updated. Set the prefix to the .INST. node by keying in the following in command mode: !PREFIX .R6B54.INST. 6.3.3.1. UPDATING SLOT ONE (1) ________ ____ ___ ___ A copy of the primary operating system will be put in slot 1. !UPDATE.OS IMAGE FILE NAME: .R6B54.INST.OS1.UV060254000 OS SLOT: (displayed) OS VERSION: (displayed) IMAGE FORMAT: (displayed) NEW WCS SLOT: 1 UPDATE WHICH DISK: (0=nn/1=nn/B=BOTH/Q=QUIT)___ DONE ! UPDATE COMPLETE Next, WCS slot 1 is updated with a copy of the same WCS that was installed in slot 0. !UPDATE.WCS ENTER WCS SLOT [0..3]: Enter '1' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R6B54.INST.WCS.B5311 WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 6.3.3.2. UPDATING WCS SLOT TWO (2) ________ ___ ____ ___ ___ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg023 REMIDI version BV5C0101 includes all the micro-diagnostics except MPC and LAN controller micro-diagnostics. It is placed in WCS slot 2 and is used for testing on all 7000/7100 and 8000 Series Systems. !UPDATE.WCS ENTER WCS SLOT [0..3]: Enter '2' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE: (choose disk) WCS IMAGE FILE: .R6B54.INST.REMIDI.BV5C0101 WCS LEVEL OF WCS IMAGE FILE: (level displayed) UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETED! 6.3.3.3. UPDATING SLOT THREE (3) ________ ____ _____ ___ 6.3.3.3.1. Updating O.S. Slot Three (3) ________ ____ ____ _____ ___ The O.S. slot 3 will contain the O.S. for DEMON on both 7000/7100 and 8000 Series Systems. !UPDATE.OS IMAGE FILE NAME: .R6B54.INST.OS3.UV060139011 OS SLOT: `U!Rsplayed) OS VERSION: (displayed) IMAGE FORMAT: (displayed) NEW WCS SLOT: Enter '0' or '1' on 7000/7100 Series Systems and 8000 Series Systems with LAN to associate the WCS in either slot with load sector 3. Enter '3' on 8000 Series Systems without LAN. UPDATE WHICH DISK (0=nn/1=nn/B=BOTH/Q=QUIT):____ UPDATING DISK DONE! UPDATE IS NOW COMPLETE NOTE: On MPx 7000/7100 Series Systems and 8000 Series Systems with LAN, the UPDATE.LD utility needs to be run to update the Load Directory. For further information on the use of UPDATE.LD, see the Diagnostics section in this announcement. 6.3.3.4. Updating WCS Slot Three (3) ________ ___ ____ _____ ___ 6.3.3.4.1. On 7000/7100 Systems and 8000 Systems with LAN __ _________ _______ ___ ____ _______ ____ ___ REMIDI version BVM6A0803 contains micro-diagnostics for the LAN and MPC controllers. It is placed in WCS slot 3 on 7000/7100 Series Systems and on 8000 Series Systems with LAN controllers. After this slot has been updated, it will be necessary to change the Load Directory by running the utility UPDATE.LD. See the Diagnostics section in this announcement for further information on REMIDI and UPDATE.LD. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg024 !UPDATE.WCS ENTER WCS SLOT [0..3]: Enter '3' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R6B54.INST.REMIDI.BVM6A0803 WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 6.3.3.4.2. On 8000 Systems Without LAN __ ____ _______ _______ ___ This slot will contain system WCS which is common to both the O.S. and DEMON. !UPDATE.WCS ENTER WCS SLOT [0..3]: Enter '3' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R6B54.INST.WCS.B5311 WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 6.3.4. SLOT INFORMATION ____ ___________ Once all slots have been updated, use the utility OSINFO to display the slot information. The information should be similar to figure 6-3. If disk 1 is a system disk also, repeat these steps beginning with the first step in section 6.3.3. Figure 6-3. Operating System Information ______ ____ _________ ______ ___________ OPERATING SYSTEM INFORMATION ------------------------------------------------------------------ BOOT LEVEL : X.X.X.X LOAD SECTOR: 0 1 2 3 DISK 0 : 0/0 1/1 0/2 3/3 SERIAL # : XXX-XXXXX ------------------------------------------------------------------ OS NAME OS LEVEL DISK:SLOT WCS LEVEL ------------------------------------------------------------------ R 6B*54 870910 6.2.54.0 0:0 B 5.3.11 R 6B*54 870910 6.2.54.0 0:1 B 5.3.11 N/A 0:2 REMIDI B 5.1.1 DEMON 2/23/87 6.1.39.11 0:3 B 5.3.11 ------------------------------------------------------------------ NOTE: OSINFO on 7000/7100 Series Systems and 8000 Series Systems with LAN will show the additional version of REMIDI IN WCS slot 3. The load sector 3 should be 3/0 on these systems. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg025 6.4. UPGRADING TO 9.6B AND THE MPX 9000, 9100, AND 9500 _________ __ ____ ___ ___ ___ _____ _____ ___ ____ 6.4.1. SPECIAL CONSIDERATIONS _______ ______________ A new configuration record is required when upgrading to 9.6B from 9.5 O.S. levels. A new configuration record is also required when an upgrade includes new hardware. It is recommended that systems being upgraded to 9.6B run on a release level that supports the new File System (any level above 8.4D) for at least one week prior to upgrade. When it is established that the system is running smoothly on the software at the end of this period, upgrade to 9.6B may then proceed. 6.4.2. PRINTING OUT THE TERMINAL CONFIGURATION RECORD ________ ___ ___ ________ _____________ ______ Skip this section if you are upgrading to 9.6B from 9.6A or 9.5. When upgrading from MPx 7000/7100/8000 Series Systems to the MPx 9000/9100/9500 Series Systems it is necessary to reference the terminal configuration in order to properly re-address the 9000, 9100, and 9500 controllers. Therefore, you must print out a copy of the terminal configuration record before upgrading. 1. Enter the TERM.CONFIG utility. 2. Select OPTION 2 DISPLAY A CONFIGURATION FILE. 3. When the following screen is displayed, enter these responses to the prompts: CONFIGURATION FILE: P OUTPUT DEVICE: DETAILED REPORT: Y ENTRIES CORRECT: Y The terminal configuration record should now be printed. 6.4.3. SAVING FILES TO TAPE ______ _____ __ ____ Current files must first be backed up to tape, using the standard tape utility, SAVERESTORE. When saving files to tape, send the output from the save process to the printer. This will provide a record of backup for each file. Also it is recommended that all tapes be compared to the files on the disk. Installation Procedure for Upgrade to the MPx 9000, 9100, and 9500 6.4.4. OPERATING SYSTEM UPDATE _________ ______ ______ 6.4.4.1. ALT LOAD ___ ____ A) Mount the new release tape in the tape drive. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg026 B) Press the "ALTLOAD" button on the front panel. C) Enter the appropriate system disk (0 or 1) or if drives 0 and 1 are both system disks, enter "2" to update both disks. D) Enter a "0" to update WCS slot 0. E) Enter a "Y" to the prompt "Are you SURE you want to overwrite this WCS ? (Y/)". The system automatically updates the OS and WCS slot 0 on both disks, if selected. When this is complete, the system prompts "DONE - READY FOR NORMAL LOAD". 6.4.4.2. TYPE 3 LOAD (SPECIAL FUNCTIONS) ____ _ ____ ________ __________ 6.4.4.2.1. Updating Installation Parameters ________ ____________ __________ Enter a TYPE 3 LOAD (SPECIAL FUNCTIONS) OPTION 2 (INITIALIZATION OPTIONS) 6.4.4.2.1.1. OPTION 4 (CHANGE INSTALLATION PARAMETERS) ______ _ _______ ____________ ___________ Only system disks will be displayed. DRIVE NUMBER _______ PRIMARY PREFIX ________________________________ ( Enter (family).R6B54.SYS. ) Where (family) is the family where the operating system files will reside. SECONDARY PREFIX ________________________________ ( Enter (family).R6B54.SYS. ) Where (family) is the family where the alternate operating system files will reside. SYSTEM INSTALLATION NAME ___________________________ Installation Procedure for Upgrade to the MPx 9000, 9100, and 9500 Sets the default installation name for a specified system disk. DEFAULT USER FAMILY NAME ________ ( Enter default user family ) SECURITY (E=ENABLED, D=DISABLED) ___ FILE SYSTEM WRITE THROUGH? (E=ENABLED, D=DISABLED) ___ WRITE THROUGH DEFAULT ON FILE CREATE (E=ENABLED, D=DISABLED) __ This parameter specifies what the default write through will be on a file created through a BASIC file create or through the CREATE utility. (Please see Field Bulletin #212.) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg027 UPDATE DISK WITH INSTALLATION PARAMETERS? (Y/N)__ Display: INSTALLATION PARAMETERS SUCCESSFULLY WRITTEN TO DISK (CR) TO CONTINUE: 6.4.4.2.1.2. Sizing the Dump Area ______ ___ ____ ____ At this point it is necessary to enter a TYPE 3 LOAD (SPECIAL FUNCTIONS), choose OPTION 2 (INITIALIZATION OPTIONS), then go to OPTION 1 CHANGE VOLUME LABEL INFORMATION to determine whether the Dump Area is large enough. Correct sizing of the Dump Area is especially critical on MPx 9000, 9100 and 9500 systems, because dumps to tape are not possible on these systems. This is because the BMTC, which is required to control tape operations on MPx 9000, 9100 and 9500 systems, is a shared memory controller. When sizing the Dump Area, you may want to round up to the next megabyte or add an extra megabyte or two for future expansion. If it becomes necessary to enlarge the Dump Area, you must do a complete back up (which you already should have), reinitialize the system disks (OPTION 2, 1 through 4, in a TYPE 3 LOAD), and do a restore from the back up in a TYPE 2 LOAD. Installation Procedure for Upgrade to the MPx 9000, 9100, and 9500 6.4.4.2.2. Restoring the O.S. Files _________ ___ ____ _____ Enter SAVERESTORE in a TYPE 2 LOAD and choose OPTION 2 RESTORE FILES FROM TAPE. The screen appears as in figure 6-4. Figure 6-4. Restore Screen ______ ____ _______ ______ -------------------------------------------------------- RESTORE FILES TAPE SET.ID: DRIVE-NUM: REEL-NUM: PRIMARY PREFIX: (FAMILY).NODE. FILE TYPE (D/P/CR=ALL) COMPARE (CR=Y/N) DATE (MM/DD/YY) TIME (HH:MM) OUTPUT DEVICE (CR=VDT) DELETE EXISTING FILES (CR=Y) VERIFY (Y/CR=N) ENTRIES CORRECT (Y/N) -------------------------------------------------------- At each prompt, enter a . SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg028 At the prompt, "FILE SPECIFIERS", enter ".". Enter to all other questions. This will restore all files from the release tape to disk. Please note that once all files are restored to disk, the message "AUTOMATIC COMPARE, CR TO CONTINUE" appears. This automatically rewinds the tape and begins the compare operation. This only occurs when the compare option is selected. When the compare is completed, enter a CTL-IV to return to the "SAVERESTORE" menu. 6.4.4.2.3. Installing the Configuration Record __________ ___ _____________ ______ It is necessary to install a new configuration record when upgrading to 9.6B from 8.4, 8.5 and 9.5 release levels. Until the following procedure is completed, the system will have a Installation Procedure for Upgrade to the MPx 9000, 9100, and 9500 minimum configuration. Enter a TYPE 1 LOAD. Set your prefix to .SYSTEM.CONFIG. Before you load the new configuration record, rename the current configuration record on your system, using the RENAME utility, to temporarily preserve it for fall back purposes. (e.g. ".OLDCONFIG.") Using the SAVERESTORE utility, restore the new configuration record on tape onto your system. Execute the CONFIG.MGR utility. The CONFIG.MGR utility allows the user to update the system configuration record by installing a new configuration file. This utility displays the current and new configuration record. When "Y" is answered to the prompt "Install Configuration:", the new configuration is copied from the file ".SYSTEM.CONFIG.I(serial number)", to the special system area on disk. The new configuration takes effect at the next system load. For further details on the use of the CONFIG.MGR utility, see the 8.5D/9.5D Software Announcement #139. The configuration record file name is derived from the system serial number by changing the leading "8" to an "I" and adding the prefix ".SYSTEM.CONFIG.". EXAMPLE: .SYSTEM.CONFIG.I1030114 for SSN 810-30114 This file should be backed up by the user, in case reinstallation should become necessary. After installing the new configuration record, LOAD the system. Otherwise your system will be at minimum configuration and will be extremely slow. 6.4.4.3. UPDATING OTHER O.S. SLOTS ________ _____ ____ _____ The slots 1, 2, and 3 need to be updated. Set the prefix to SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg029 the .INST. node by keying in the following in command mode: !PREFIX .R6B54.INST. 6.4.4.3.1. Updating Slot One (1) ________ ____ ___ ___ A copy of the 9.6B operating system will be put in O.S. slot 1. Installation Procedure for Upgrade to the MPx 9000, 9100, and 9500 !UPDATE.OS IMAGE FILE NAME: .R6B54.INST.OS1.UV060254000 OS SLOT: (displayed) OS VERSION: (displayed) IMAGE FORMAT: (displayed) NEW WCS SLOT: 1 UPDATE WHICH DISK: (0=nn/1=nn/B=BOTH/Q=QUIT)___ DONE ! UPDATE COMPLETE Next, WCS slot 1 is updated with a copy of the 9.6B WCS. !UPDATE.WCS ENTER WCS SLOT [0..3]: Enter '1' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R6B54.INST.WCS.A6420 WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 6.4.4.3.2. Updating WCS Slot Two (2) ________ ___ ____ ___ ___ The first section of the 9000/9100/9500 version of REMIDI will reside in this slot. NOTE: Running UPDATE.OS automatically updates the load sectors for the disk. However, running UPDATE.WCS does not. (The Load Sectors are displayed at the top of the OSINFO screen.) It is therefore necessary to run UPDATE.LD for REMIDI on newly initialized systems packs, or whenever question marks ("?/?") appear in Load Sector 2 on the OSINFO screen. See the Diagnostics section in this announcement for further information on REMIDI and UPDATE.LD. !UPDATE.WCS ENTER WCS SLOT [0..3]: Enter '2' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE: (choose disk) WCS IMAGE FILE: .R6B54.INST.REMIDI.AVA6A0104 WCS LEVEL OF WCS IMAGE FILE: (level displayed) UPDATING DISK UNIT nn SECTOR xx SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg030 Installation Procedure for Upgrade to the MPx 9000, 9100, and 9500 WCS UPDATE COMPLETED! 6.4.4.3.3. Updating Slot Three (3) ________ ____ _____ ___ 6.4.4.3.3.1. Updating O.S. Slot Three (3) ________ ____ ____ _____ ___ O.S. slot 3 will contain the O.S. for DEMON. !UPDATE.OS IMAGE FILE NAME: .R6B54.INST.OS3.UV060139011 OS SLOT: (displayed) OS VERSION: (displayed) IMAGE FORMAT: (displayed) NEW WCS SLOT: Enter '0' to associate DEMON's O.S. with the WCS in slot 0. (DEMON and the 9.6B O.S. share the same WCS.) UPDATE WHICH DISK (0=nn/1=nn/B=BOTH/Q=QUIT):____ UPDATING DISK DONE! UPDATE IS NOW COMPLETE 6.4.4.3.3.2. Changing the Load Sector for Slot Three (3) ________ ___ ____ ______ ___ ____ _____ ___ Because the second section of the 9000/9100/9500 version of REMIDI is in WCS slot 3, the Load Directory must be changed to point to another WCS slot for DEMON. The 9.6B O.S. and DEMON share the same WCS code, therefore, we can point to the WCS slot used by the 9.6B O.S. Update the Load Directory for DEMON by using the UPDATE.LD utility. See the Diagnostics section in this announcement for information on how to run UPDATE.LD. 6.4.4.3.3.3. Updating WCS Slot Three (3) ________ ___ ____ _____ ___ This slot will contain the second section of the 9000/9100/9500 version of REMIDI. !UPDATE.WCS ENTER WCS SLOT [0..3]: Enter '3' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R6B54.INST.REMIDI.AVC6A0104 WCS LEVEL OF WCS IMAGE FILE: (level displayed) Installation Procedure for Upgrade to the MPx 9000, 9100, and 9500 Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 6.4.5. Slot Information SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg031 ____ ___________ Once all slots have been updated, use the utility OSINFO to display the slot information. The information should be similar to figure 6-5. Figure 6-5. Operating System Information ______ ____ _________ ______ ___________ OPERATING SYSTEM INFORMATION ------------------------------------------------------------------ BOOT LEVEL : X.X.X.X LOAD SECTOR: 0 1 2 3 DISK 0 : 0/0 1/1 0/2 3/1 SERIAL # : XXX-XXXXX ------------------------------------------------------------------ OS NAME OS LEVEL DISK:SLOT WCS LEVEL ------------------------------------------------------------------ R 6B*54 870910 6.2.54.0 0:0 A 6.4.20 R 6B*54 870910 6.2.54.0 0:1 A 6.4.20 N/A 0:2 REMIDI A 6.1.4 DEMON 02/23/87 6.1.39.11 0:3 REMIDI A 6.1.5 ------------------------------------------------------------------ The O.S. and WCS slots on all other system disks on the system must also be updated. Installation is now complete. System Startup 6.5. SYSTEM STARTUP ______ _______ 6.5.1. Standard Startup Command File on 9.6B/8.6B BOSS/VS ________ _______ _______ ____ __ _________ _______ The commands for the standard System Startup Command File are released in the file: .R6B54.SYS.START.CMD The standard commands are: !MAGNET.STARTUP !GROUP.CREATE SPOOLER,TYPE=SYSTEM !SPOOL P*,VERIFY=F,PAUSE=F !GROUP.ENABLE TERMINALS,VERIFY=F,PAUSE=F The name of the System Startup Command File actually used for startup is: (system-default-family).SYSDATA.START.CMD Part of 9.6B/8.6B BOSS/VS system installation is to copy the released file to the .SYSDATA. node and make changes and additions as necessary. Note that the commands and parameters in this file must match the commands and parameters defined in the CLI command and function definition files for the individual system being installed. If the System Startup Command File is not found after a system SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg032 load, then a default initialization is performed. This puts all printers into spooled mode and enables terminals. The following outlines the commands, some of the implications and details of the System Startup Command File method of system configuration. 6.5.1.1. Command File Definitions _______ ____ ___________ MAGNET.STARTUP ______________ This command runs a released MAGNET program that does all of the startup operations required by the MAGNET subsystem. This command should be deleted if MAGNET is not part of the system configuration. GROUP.CREATE_SPOOLER,TYPE=SYSTEM ________________________________ System Startup This command creates the Spooler Group that maintains the activity log files and Group statistics for the spooler subsystem. This command should come before the 'SPOOL P*' command. SPOOL_P*,VERIFY=F,PAUSE=F _________________________ This command puts all of the printers into spooled mode, and causes any eligible requests on the spooled printers to start printing. GROUP.ENABLE_TERMINALS,VERIFY=F,PAUSE=F _______________________________________ This command enables the 'built-in' TERMINALS Group, and allows all users to logon to any terminals. This command is provided to allow the terminals to be enabled under user control. See below. NOTE: IF A SYSTEM STARTUP COMMAND FILE EXISTS, THIS COMMAND, OR SOME OTHER COMMAND TO ENABLE TERMINAL GROUPS, MUST BE IN THE SYSTEM STARTUP COMMAND FILE FOR USERS TO LOGON TO THE SYSTEM. In case the TERMINALS Group is disabled, a user with 'system operator' status can enable this group when attempting to logon to the system. This allows an operator to logon to the system in case the Startup Command File did not enable the TERMINALS Group, or the TERMINALS Group was left disabled by accident and all operators signed off the system. To enable the TERMINALS Group during logon the operator attempts to logon and ignores the 'Logon disabled' error messages and enters a 'CR' to continue. A prompt is displayed asking the operator if he wants to enable the TERMINALS Group. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg033 NOTE: THIS OPTION IS NOT AVAILABLE IF SOME OTHER TERMINAL TYPE GROUP IS ENABLED. ALSO, ONLY THE TERMINALS GROUP IS ENABLED, AND IT IS NOT CREATED IF IT DOES NOT EXIST. 6.5.2. Implications ____________ 1) Normal system startup is automatic. The system ______ ______ _______ __ _________ configuration options defined when the system was installed (placed into the System Startup Command File) are put into effect each time the system is loaded, with no further action by the user. System Startup These startup options may be modified by the user at any time, by editing the System Startup Command File. 2) Startup sequence is under user control. Users now have _______ ________ __ _____ ____ _______ the ability to control the sequence of events at startup, after the internal startup sequence is complete. Users that do not need this level of control may ignore this feature. Some users may wish to run specific programs, and do recovery operations, before MAGNET and/or the Spooler are started up. This ability would be impossible if these subsystems were always started by the internal system initialization. 3) System recovery is possible before all users logon. This ______ ________ __ ________ ______ ___ _____ _____ approach allows the operator to allow only specified terminals/users to logon after a system load. The System Startup Command File containing the single command: GROUP.CREATE , TYPE=TERMINAL, USERS=SYS.MGR, DEVICES=T0 would allow only the user 'SYS.MGR' to logon to terminal 'T0' after the system load. No other users could logon, and no other activity would start. In this case the printers will be in suspended mode and MAGNET will not be initialized. When the system operator is finished with the recovery operations the 'normal' system configuration command file may be run by the operator to begin normal system processing. Again, users who do not need this level of control may ignore this feature. 4) Default startup with no System Startup Command File. When _______ _______ ____ __ ______ _______ _______ ____ the TYPE 1 LOAD is complete, if the System Startup Command File is not found then 'default' startup conditions are in effect. In this case the system is available for any use. This mode is intended to support systems that want only these default startup options. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg034 The 'built-in' TERMINALS Group is enabled and allows all users to logon to any terminal. A system group named SPOOLER is created and the printers System Startup are put into spooled mode. The MAGNET subsystem is not activated. ___ The following is a description of the details of the System Startup Job: When a TYPE 1 LOAD is performed, the last module to be initialized is the Job Manager (JMM). The final act of JMM is to run a batch job with a CLI command file. The files involved are: (system-default-family).SYSDATA.START.CMD (system-default-family).SYSDATA.START.IN (system-default-family).SYSDATA.START.OUT SYSDATA.START.CMD is a sequential file that contains all of the startup commands; this is the System Startup Command File. The Job Manager looks in the system default family (only) for this file. SYSDATA.START.IN is a sequential file that contains any data that may be input by commands and programs in the above startup file. A read from standard INPUT will read records from this file. The Job Manager looks in the system default family (only) for this file. SYSDATA.START.OUT is a sequential file that contains the results of the startup command file. A write to standard OUTPUT by commands and programs will be placed into this file. The Job Manager deletes this file in the system family if it exists, prior to running the startup command file. If the startup file (system-default-family).SYSDATA.START.CMD - or - (system-default-family).SYSDATA.START.CMD.TEXT is not found, the Job Manager will perform a default startup described above. If the startup file (system-default-family).SYSDATA.START.IN - or - (system-default-family).SYSDATA.START.IN.TEXT is not found, the Job Manager will attach a null file to System Startup startup INPUT; an End-Of-File will be returned for each read SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg035 from standard INPUT. NOTE: THE SYSTEM STARTUP COMMAND FILE CONTAINS (ONLY) STANDARD CLI COMMANDS. A CLI command may be: 1) A CLI Command or Function (START, PREFIX, $WHERE, etc.) 2) A system utility (DIR, COPY, etc.) 3) The name of a program to run. 4) The name of another CLI command file. Warnings and Cautions 7. WARNINGS AND CAUTIONS ________ ___ ________ These Warnings and Cautions are applicable to release levels 9.6B and 8.6B. Where applicable, the SPR (System Problem Report) or RSC (Request for Software Change) number is listed. 7.1. MPX 7000, 7100, 8000, 9000, 9100 & 9500 SERIES SYSTEMS ___ _____ _____ _____ _____ ____ _ ____ ______ _______ 7.1.1. BOSS/VS _______ 7.1.1.1. UTILITIES _________ 7.1.1.1.1. CONFIG.MGR __________ 1) A configuration record can only be installed from an account with a USER LEVEL of 3. 2) Printer output cannot be directed to a specific printer. 3) The LEGAL option of DataWord will always display "YES" when using the "Install" option. However, if the configuration record was created with LEGAL=NO, LEGAL will not be enabled. This is a problem in the "Install" display only. This problem has been addressed by engineering and will be fixed in an upcoming release. 4) Configuration records created for 9100 Series Systems on O.S. levels 8.5/9.5 will display as System Type "9000", even though the printout of the configuration record shows "9100". Configuration records created for 9100 Series Systems on O.S. levels 8.6/9.6 will display as System Type "9100". 5) As of the 9.5D/8.5D release, the CONFIG.MGR utility replaces the INSTALL.CONFIG utility. 7.1.1.1.2. FAMILY ______ 1) SPR 507152 - Disk numbers of the first multi-volume family created are used as defaults for subsequent families, if the subsequent families are created without exiting the FAMILY SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg036 utility. The workaround for this problem is to exit the FAMILY utility after each multi-volume family is created. 2) SPR 507151 - When creating volume labels using the FAMILY utility (Option 4), the volume type (System or Data) of the first disk is retained as a default when creating volume Warnings and Cautions labels for subsequent disks. However, if this default value is used (by pressing ), the volume label will not be updated with this default value for volume type, even though it displays this way on the screen. The workaround for this problem is to always key in "S" for System disk and "D" for Data disk, and never take the default for volume type. 7.1.1.1.3. GETDEVINFO __________ GETDEVINFO does not return information on Batch jobs. 7.1.1.1.4. JOB MANAGER ___ _______ 1) Defined GROUPS are deleted at system reload. Job Groups to be kept on a more or less permanent basis should be created via commands entered in the System Startup command file, .SYSDATA.START.CMD. 2) JOB.CREATE does not allow the PAUSE=TRUE parameter to be passed. If the command is embedded in a program, all errors must be handled by the application. 3) BATCH jobs require an output file which is not automatically deleted. The user may need to delete these files on a regular basis to keep disk space available. 4) The FID (0) is a file for a BATCH job. This is done by design so that a BASIC program can be run in BATCH mode. 5) Quotes must be used around the user accounts when specifiying more than one user account in the GROUP.CREATE and GROUP.MODIFY parameter lines. (Example: GROUP.CREATE MYGROUP, TYPE=TERMINAL, PRIORITY=3, USERS="GROUP1.*, GROUP2.*") 6) RSC 511490 - If PRIORITY is not specified for TERMINAL and BATCH type jobs, the PRIORITY will default to 1. This default, although proper for BATCH type jobs, is normally too low for TERMINAL type jobs. It is recommended that a PRIORITY of 3 be specified for TERMINAL type jobs during GROUP.CREATE. (See example in item 6.) 7) RSC 511491 - The PRIORITY of SYSTEM type jobs cannot be changed, even though GROUP.MODIFY appears to allow the user to do this. 8) RSC 511491 - SYSTEM type jobs cannot be deleted, nor can Warnings and Cautions SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg037 they be modified. GROUP.MODIFY appears to allow the user to modify SYSTEM type jobs, but such modifications are not enforced. 7.1.1.1.5. MOUNT _____ MOUNT is not used with the new Spooler introduced in 9.6A/8.6A. 7.1.1.1.6. SAVERESTORE ___________ 7.1.1.1.6.1. Restoring ISDC Code Files and REMIDI _________ ____ ____ _____ ___ ______ On 8.5C/9.5C the three ISDC code files (ETWYOS, FOWYOS, SXTNOS) and the REMIDI files were changed to be unorganized file types. This was done so DISKANALYZER would no longer flag these files as having an internal file problem. Files that are typed as unorganized were not supported by SAVERESTORE and the File System in releases prior to 8.5C/9.5C, so these files are rejected when an attempt is made to restore them on prior O.S. levels. This is why an ALT LOAD from tape must be done before the O.S. files are restored when upgrading a system that is currently on a release prior to 8.5C/9.5C. (The only exception to this is an upgrade from 8.4E. The same changes to the above 8.5C/9.5C files were also made to the 8.4E files.) 7.1.1.1.7. SPOOLER _______ 1) SPR 509923 - The FORM utility does not allow over 14 individual printers to be entered for a specific form. 2) The Spooler NOTIFY function, which broadcasts a message to the top of a terminal screen when a print job has finished, will cause the screen to scroll if the cursor is on the last line of the screen. 3) SPR 510332 - It may take a few minutes to print a spooler job if the system is heavily loaded. 4) BADREQUESTS File The REQUESTS file contains names of Spooler files that have been submitted to the printer. This REQUESTS file can become corrupted when there is a fatal system error. When the REQUESTS file is observed to lack integrity at system load time, it is renamed to BADREQUESTS. Then a new, empty Warnings and Cautions REQUESTS file is created. To reestablish Spooler access to the files named in BADREQUESTS, it is necessary to reconstruct the BADREQUESTS file with the following steps: o Boot the system into a Type 2 Load. o Reconstruct the BADREQUESTS file using DISKANALYZER. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg038 o RENAME it to REQUESTS, deleting the source file. o Reboot the system into a Type 1 Load. 7.1.1.1.8. EXTTAPE _______ EXTTAPE does not support PSAVEd programs. However, it gives an erroreous "End of Tape" message when it encounters a PSAVEd program (SPR 509607). 7.1.1.1.9. TERM.CONFIG ___________ 1) The DT-4312 terminal must be configured as a DT-4309. 2) SPR 511815 - The HELP screens for terminal types contain model numbers used on release 9.5E/8.5E. They have not been updated for 9.6/8.6, and, therefore, do not contain the necessary information for configuring terminals at this level. 7.1.1.1.10. TERM.TABLE __________ SPR 502408 - When using the copy option of TERM.TABLE (Option #4) to copy the Primary file to the Secondary file, the copy is not successful. The workaround is to copy the Primary to the Secondary again without exiting the TERM.TABLE utility. The COPY will be successful the second time. 7.1.1.1.11. UPDATE ______ 1) SPR 505144 - When expanding a file, the screen display exceeds 100%. 2) SPR 505145 - When expanding a file, the number of "records used" is changed to the number that was in "max records" before the expand. 7.1.1.1.12. UPDATE.OS _________ SPR 502348 - UPDATE.OS returns an error when trying to update the O.S. before the WCS on a newly formatted disk. The workarounds for this problem include updating the WCS before Warnings and Cautions the O.S., or doing an ALT LOAD to update slot 0. 7.1.1.1.13. MCSI ____ All filelist access must be made by a user with File Security Override set to true. 7.1.1.2. LOGON _____ RSC 507496 - The message "Logon disabled at this terminal, SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg039 'CR' to continue:" is displayed after a system load, if a the logon is attempted when the System Startup command file has not completed execution. Enter 'CR' and the Logon should then be enabled. 7.1.1.3. BASIC _____ 7.1.1.3.1. Running SORT from BASIC _______ ____ ____ _____ If the SORT utility has been executed from BASIC, and it encounters an error, BASIC will always return an error 0. 7.1.1.3.2. MTCS (MCS) Tape Drive ____ _____ ____ _____ An MTCS (MCS) tape drive cannot be accessed through BASIC. This is done by design. 7.1.1.3.3. Program File Compatibility _______ ____ _____________ The significant enhancements of Business BASIC 86 introduced in 9.6A/8.6A will restrict backward compatibility. Programs written or modified on 9.6B/8.6B will not run on releases prior to 9.6A/8.6A without recompilation. In addition, new Business BASIC 86 features introduced in 9.6A/8.6A cannot be used in programs which will be run on 9.5/8.5 or 8.4 release levels. Intersystem transport packages or the CONVERTSP utility can be used to recompile programs written or modified on 9.6/8.6, provided the new BB86 features have not been used. In most cases, where you used SAVERESTORE for tape transfer of programs to an 8.5 system, you would use EXTTAPE instead. EXTTAPE will recompile the programs as they are being transported. (All tape transfers from the new file system to the old file system require EXTTAPE.) Warnings and Cautions 7.1.1.3.4. CONSOLELOCK ___________ The system will log off while in BASIC CONSOLELOCK if both of the following 2 conditions are met: a) An END, STOP, or ESCAPE directive has just been executed in the BASIC program, and b) You enter carriage return or an invalid password 3 times. This is according to design. 7.1.1.3.5. Multi-Key Files _________ _____ 1) The following utilities will not operate on Multi-Key files: BCOM, BQR, CREATE, EDIT, EXTTAPE, FILESIZE, FTF, GSR, MCSI, NFSCONVERT, OLDDIR, OLDTAPE. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg040 2) SPR 507831 - Two fields occupying the same space in a data record cannot both be keysets. 7.1.1.4. CLI Batch Subsystem ___ _____ _________ For a list of the utilities not supported by BATCH, please see the CLI Batch Subsystem section in this announcement. 7.1.1.5. Communications ______________ 7.1.1.5.1. MAGNET and File Transfer Facility (FTF) ______ ___ ____ ________ ________ _____ 1) There is no automatic conversion of topology configuration files to the new Network Management Facility (NMF) configuration files when 8.6A is installed on an MPx system previously configured for B4NET/FTF. The user is responsible for printing the previous configuration information before re-configuring the MAGNET and/or FTF network with NMF or EZCONFIG. 2) A reboot is necessary after the initial configuration of each system in the MAGNET/FTF network. Any subsequent modifications to the home station parameters or subnetwork numbers also require a reboot to activate the changes. 3) Care must be taken to configure enough SVC's to support all remote concurrent activities; the number of remote X.25 sites accessed at any time cannot exceed the number of SVC's Warnings and Cautions configured for the X.25 link; each FTF file transfer will require its own SVC. 4) FTF file transfers may experience Completion Code 149's (Network Services Timer Expired) when the system or network load is heavy, or when communicating over a LAN/WAN internetwork. 5) FTF file transfers via LAN are only allowed between MPx systems. 2000/3000 systems may not co-exist on the same LAN network as MPx systems. FTF file transfers are allowed to unlike systems (MPx, 2000/3000, 13xx) over X.25 links; however, automatic data conversion for unlike character sets is NOT performed. The Intersystem Transport program, FTFIT, must be used for data conversion of FTF file transfers between unlike systems. 6) Three types of X.25 packet data switches were used during the test cycle: o Memotec 8500 o Dynapac Model 8 o Dynapac Model 12 Results of the testing showed that the Memotec 8500 should only be used for networks which have a low load or when performance is not a factor. The Dynapac Model 8 can handle SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg041 heavier network load but the baud rate is limited to 9600 BPS. The Dynapac Model 12 is recommended for networks with heavy loads - up to 7 MPx systems at 19.2K BPS using 128 byte packets. A problem where the Dynapac Model 12 went into a 'lockup' mode was found when running 5 or more systems at 19.2K BPS and using 256 byte packets. To prevent this problem, the packet size should be reduced to 128 bytes. (The Dynapac Model 12A is recommended over the Dynapac Model 12 to avoid MAGNET errors due to "restarts") 7) To optimize throughput of X.25 communications, it is recommended that the IMLC be configured with X.25 on port A and nothing on Port B. This configuration will allow running at baud rates of 9600 BPS and above, and configuring more SVC's and larger data packet sizes. Other IMLC products such as 27xx/37xx, 3270, and Dataword should be configured on another IMLC. 9/8.6A supports up to 4 IMLC boards. 8) Gateway systems in an LAN/WAN internetwork environment can Warnings and Cautions pass MAGNET accesses to other systems in its subnetwork even if the gateway is configured for FTF and not MAGNET (must also be configured for X.25, LAN, and NMF). However, the reverse is not true - gateway systems configured for X.25, LAN, NMF, and MAGNET cannot pass FTF file transfers through to other systems in the subnetwork. FTF requires that gateway systems be configured for FTF in its configuration record. 9) LAN/WAN internetworking has a significant impact on the gateway system. For this reason, the largest and/or least busy system on the subnetwork should be configured as the gateway system. The minimum system type for a gateway should be an 8030 if possible. 10) A maximum of 63 systems may exist on a MAGNET LAN network. However, performance degradation will occur when more than 8 systems are actively transmitting data, especially during file copies. 11) MAGNET event logs are initially set in the GROUP utility to LOGFILES=10 and LOGRECS=100. Although these parameters are normally sufficient, depending on network activity the event log sizes may have to be increased. To increase the size, modify the .SYSDATA.START.CMD file to include the command: GROUP.SETLOG MAGNET,LOGFILES=n,LOGRECS=n,VERIFY=FALSE where 'n' is the number desired; recommended values are LOGFILES=25 and LOGRECS=200. The logfiles will be increased with the next reboot of the system. If you wish to increase the logfiles on a temporary basis, the logfile parameters can be modified through the JOB MANAGER utility. The modifications will take effect immediately but will stay in effect only until the system is SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg042 rebooted. 12) If MAGNET is installed on a system already running in production mode, some degradation may be experienced. If this occurs, the system should be upgraded in terms of memory and/or CPU. Warnings and Cautions 7.1.1.5.2. Asynchronous Transport Package (ATP) ____________ _________ _______ _____ ATP 4.0 will be the ATP release available for 9/8.6A. ATP 4.0 provides new features such as autodial, scheduler, line turn-around, and performance enhancements. ATP 4.0 is NOT compatible with previous releases of ATP; all systems communicating with ATP 4.0 systems must also upgrade to 4.0. ATP 4.0 is currently in beta test. Users on 9/8.6A who require ATP should contact Product Marketing on being an ATP 4.0 beta site. 7.1.1.5.3. 19.2K BPS Support _____ ___ _______ TERM.CONFIG permits configuration of 8-Way and 16-Way ports with a BPS of 19.2K. See the section on 19.2K BPS in the 9.6A/8.6A Software Announcement for guidelines on configuration cautions in regard to aggregate ISDC throughput. 7.1.2. Hardware ________ 7.1.2.1. Terminals _________ Very fast typing may cause DT-4312 terminals to drop characters. This occurence is rare. 7.1.2.2. MCS Board ___ _____ 7.1.2.2.1. When Upgrading from 8.4D and Below ____ _________ ____ ____ ___ _____ When upgrading from 8.4D or below to 8.6/9.6, it is essential that the 4-Way (MCS board) be enabled (SW1 position 3). Not doing so will result in a dump with the fourtuple 11,13,0,0 occurring when attempting to enter a TYPE 3 LOAD after the update of slot 0. 7.1.2.2.2. MCS Revision "S" ___ ________ ___ MCS PCBA PN 903374-001 at revision "S" now has the ability to be switch selectable (SW1-4) to match the different address schemes between MPx 7000/8000 Series Systems and MPx 9000, 9100, and 9500 Series Systems. The "S" revision level is not mandatory for the function of either system. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg043 MCS revision "S", when used in MPx 7000/8000 Series Systems, Warnings and Cautions must be set for MPx 7000/8000 systems. Failure to do so will cause the system load to abort with BOOT STRAP ERROR "FFFF". MCS revision "S" used in MPx 9000/9100/9500 systems, (when switch selected for MPx 9000/9100/9500 systems), will allow any controller to be board addressed from the range of 1 to 63 (the board address of 16 through 31 are not valid in the MPx 9xxx system, do not address pcb's in these ranges). If set for MPx 7000/8000 systems and used in MPx 9000/9500 systems the board addresses of 32 thru 47 may only be used for the IMLC PCB. There will also be no support for memory above 12 megabytes. Revisions "T" is required for support of more than 12 megabytes of memory. The following are the switch settings for revision "S" or above MCS board: Switch SW1-4 open: MPx 7000/8000 Switch SW1-4 closed: MPx 9000/9100/9500 7.2. MPX 9000, 9100 AND 9500 SERIES SYSTEMS ONLY ___ _____ ____ ___ ____ ______ _______ ____ 7.2.1. BOSS/VS _______ 7.2.1.1. Dumps _____ Because the BMTC is a shared memory controller, dumps to tape are not possible on the 9000 and 9500. Therefore, it is essential that the dump area on disk be large enough. See Field Bulletin #211, "Computing the Dump Area Size on MPx Systems", for further information. 7.2.2. HARDWARE ________ 7.2.2.1. IMLC in MPx 9000/9100/9500 Systems ____ __ ___ ______________ _______ 1) The Memory Map Controller board numbers of the IMLC's must be in the range 32-47. If Revision level "S" or above of the MCS board is used and set for the model MPx 9000/9100/9500 Series Systems then this restriction is removed. See MCS BOARD in Warnings and Cautions. 2) The "JMP C" self test jumper should be installed on the IMLC PCBA's. This is a hardware requirement for 9xxx systems only, and it is not related to the 9.6/8.6 O.S. level. For further information on this jumper, see the field bulletin titled "MPx 8xxx to 9xxx Upgrade IMLC NOT RECOGNIZED". Warnings and Cautions 8. RELATED DOCUMENTATION _______ _____________ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg044 2770/2780/3770/3780 Batch Emulator User Guide M 5080C 3270 Pass-Through Reference Manual M 5091A BOSS/VS Business BASIC 86 Reference Manual M 6262 * BOSS/VS User Guide M 5098F * BOSS/VS Utilities User Guide M 5102E * 3270 Emulation Package Operator Guide for MAI 8000 Series M 5129 MAI 8000 Terminal Asynchronous Communication Facility Reference Manual M 5130A File Transfer Facility User Reference Manual M 6352A BOSS/VS Installation Guide M 5138D * MPx System Installation Planning Guide M 5146F * BOSS/VS Special Purpose Utilities User Guide M 5151 BOSS/VS System Support Manual M 5152 Intersystem Transport Package User Guide M 6354D MAI 8000 Series COBOL Reference Manual M 5174 MAI 8000 Series COBOL User Guide M 5175 BOSS/VS File Conversion User Guide M 5185A MAGNET/VS User Reference Manual M 6363 * * These manuals were revised for 9.6A/8.6A. No manuals have been revised for 9.6B/8.6B. ORIGINATOR: Nancy Prentiss SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB038 Pg045 FIB 00039 12/02/87 *** Wrong message for Key Too Long on release 9/8.E *** In WPS Field Bulletin #312, "Software Releases 8.5E/9.5E Now Available", the following File System problem was listed as fixed. The fix was actually incorporated into the 9/8.6A release, not the 9/8.5E release. Problem: When an attempt is made to READ or WRITE using a KEY that is longer than the defined key length, an ERROR 65 ("File Lacks Integrity") results. The correct result is to return an ERROR 46 ("Invalid String Size"). ORIGINATOR: Nancy Prentiss SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB039 Pg001 FIB 00040 12/02/87 *** Incorrect spec. char. file names returned on DIR function - 9/8.5 *** A potential problem for users on 9/8.5 exists. BASIC and DISKANALYZER will allow the user to create files which have illegal file names. These files can not be deleted using the standard utilities DELETE, RENAME, or COPY. The main problem that these files cause is that DIR, SAVERESTORE, and DISKANALYZER do not work correctly when these file names are in a directory and a node name search is done. The way an illegal file name is created is through a file create in BASIC (DIRECT, SERIAL, INDEXED, SORT) or in DISKANALYZER for the output file when validating a file. Example: .NODE.%6!@!@!@! The key is that the %6 indicates 6 characters will follow and 6 is the maximum number.allowed for special character file names. However, 7 characters actually follow the %6. When one does a DIR the file is displayed as %7!@!@!@!. Any file with a special name which follows this file in the same node may be "lost" to DIR, SAVERESTORE, or DISKANALYZER. The user can still OPEN the "lost" files, but access of the files from the directory does not show them unless they are fully specified or a filelist is used. The way to remove these illegal name files is to do the following: From BASIC >ERASE ".NODE.%6!@!@!@!" Note that %6 was used and not %7. If you do not specify the prefix of the file, you will get an illegal file name error. Once the file is erased, all of the utilities start finding all file names again. This problem has been corrected on release levels 9/8.6A and above, by not allowing the creation of illegal file names. ORIGINATOR: Dale Jensen SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB040 Pg001 FIB 00041 12/29/87 *** Operator Flags on BOSS/VS 9/8.6 [ WPS 411 ] *** Operator flags are set on an account through the use of the SECURITY utility. The three operator flags are: Spooler Operator, Tape Operator, and System Operator. If the Spooler Operator flag is set to "F", the user will not be able to do the following: 1. Move a printer to or from SUSPEND mode. 2. Move a printer to or from DISCONNECT mode. 3. STOP, CANCEL, RESTART, or MODIFY another user's job. 4. Stop another user's printing job by moving the printer from SPOOL to RESERVE mode. If the Tape Operator flag is set to "F", the user will not be able to use any of the tape utilities. If the System Operator flag is set to "T", the user on that account will be able to do all Spooler and tape operations, regardless of how the Spooler and Tape Operator flags are set. If the System Operator flag is set to "F", the Spooler and Tape Operator flags will be looked at individually. ORIGINATOR: Nancy Prentiss SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB041 Pg001 FIB 00042 02/12/88 *** 8-bit mode doesn't work on letter quality printers [ WPS 399 ] *** 8-bit word length does not work correctly on any BOSS/VS OS releases prior to 8/9.6C when using the Letter Quality Printer driver. This affects the following printers 4206, 4211, 4215, 4216, and 4223. This problem is not significant when the LQP driver is used with the 4206, 4211 or 4216 daisy wheel-type printers since these printers don't support 8-bit character sets. The problem is significant when using the 4215 and 4223 printers that do have 8-bit character sets. In order to use 8-bit word length with the LQP driver, BOSS/VS must be at 8/9.6C or higher. Details of 2 of the problems are as follows: 1. 8.6A had a problem loading the VFU on 8-bit letter quality printers. The ISDCOS was sending out ESC SUB 1 to set up the printer with the high bit on. This will be fixed in 8/9.6C. 2. There were some problems with 8-bit mode using the SER and PAR DMP printers. These were fixed on 8/9.6B. NOTE: As long as the printers are configured for 7-bit word length, on releases prior to 8/9.6C, the problems do not occur. ORIGINATOR: Tom Sears SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB042 Pg001 FIB 00043 02/16/88 *** MPX Spooler change in pitch support on 8/9.6C OS [ WPS 425 ] *** The 8/9.5 Spooler had no support for pitch in its FORMS definition, making it necessary for the user to set pitch by either using '10' or '16' mnemonics for 10 and 16 pitch, or by directly sending the hex code to set pitch to the printer. The 8/9.5 Spooler did not intervene in any way, but allowed the user total control over the pitch setting. The 8/9.6A Spooler introduced support for 10 and 16 pitch in its FORMS definition. This support involves setting the pitch at the beginning of every line of output to a printer. This has the effect of removing control over pitch from the application and placing it in the Spooler's hands. 8/9.5 applications which previously could set a printer at 12 pitch by sending the appropriate hex code directly to the printer, now have the pitch overridden on the next line by the Spooler. This has had the effect of requiring an application to set the pitch on every line output, rather than once at the beginning of a job. In order to correct this problem, the Spooler is being changed (8/9.6C) so that it only sets the pitch specified in the FORMS definition at the beginning of each job. This will allow the user to exert the same level and type of control over pitch as they could in 8/9.5. Another effect of the change is to remove Spooler support for setting the pitch in "reserved" and "disconnected" modes. Control over pitch in these modes is now the user's responsibility, as it was in 8/9.5. This is made necessary because there is no "beginning of job" in these modes at which the VFU may be loaded and the pitch can be set. In addition, this will achieve 8/9.5 compatibility in Spooler operation in these non-spooled modes. ORIGINATOR: Joe Melendez SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB043 Pg001 FIB 00044 02/16/88 *** "NOT CONVERTED" message in !CONVERT/!CONVERTSP - 8/9.5 [ WPS 426 ] *** In some cases when using !CONVERTSP or !CONVERT you will get under STATUS the message "NOT CONVERTED" and at the bottom of the screen you will have this message: "Cannot convert restricted-access program, 'CR' to continue:" This will happen when you have the following: a. statement that has only a ? 0050 ? (will not convert and give you the message) 0050 ? A$ (will convert) b. statement that has only a !. 0050 ! (will not convert and give you the message) 0050 ! UTILITY (will convert) This is fixed in 8/9.6. ORIGINATOR: Joe Melendez SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB044 Pg001 FIB 00045 03/28/88 *** Spooler Error Codes returned to BASIC on 9/8.6 [ WPSF 428 ] *** The new 9/8.6 spooler contains some changes from the 9/8.5 spooler error codes returned to the user throught BASIUC. For example, on 9/8.5 a "PRINTER NOT PRESENT" condition will return an error 12. On 9/8.6, this same condition will result in an error 17. When a spooler error is received through BASIC, its fourtuple may be obtained by typing the "ERROR" command. For example, if a user tries to reserve a printer that is already reserved from BASIC. the following error is received: !ERROR=18 >0290 !RESERVE LP In order to obtain the full spooler fourtuple and description of the error, the user should type the following: !ERROR=18 >0290 !RESERVE LP >ERROR ----Type in "ERROR" !ERROR=18 (40,0,18,5) ----Status returned PRINTER IS ALREADY RESERVED In order to help identify and interpret the 9/8.6 spooler error codes, attached is a list of "Fourtuple Error Codes" and a description of their meanings. ORIGINATOR: Leo Sanders SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB045 Pg001 FIB 00046 04/20/88 *** Use caution when selecting drive #s on tape update [ WPSF 445 ] *** On Operating System updates, caution must be taken when updating the image slot area using a tape load. It is very important to note how the disks are labeled, whether they are a "SYSTEM" disk or a "DATA" disk. The update, when done from a tape load, will allow the user to select a disk to update a disk labeled as a "DATA" disk. If a "DATA" disk is selected, a warning message is displayed such as: WARNING !!! DISK # x - IMPROPER VOLUME LABEL DETECTED- FS START SECTOR IN O.S. AREA SM START SECTOR IN O.S. AREA SM END SECTOR <= SM START AREA MEMORY DUMP AREA TOO SMALL FOR TOTAL MEMORY If the user selects "YES" to proceed, the O.S. and WCS images will be restored over the user's file system area on that disk. The disk will not be usable until the FAMILY is initialized using the Type 3 Load options. The important point is, when updating the Operating System, check to see how the disks are labeled and ensure there is a current backup of all files before the update is started. Do not install the images on a "DATA" disk unless you intend on making it a "SYSTEM" disk. ORIGINATOR: Dale Jensen SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB046 Pg001 FIB 00047 05/20/88 *** Install new Configuration Record before adding fixed disk *** If a fixed disk drive is being added to a system and will become part of the system disk family the new Configuration Record must be installed on the existing system disk family before proceeding with the VOL label updates. If the new configuration record is not installed before initializing the existing system disk family, the system will not recognize the new disk drive even in a Type 3 (special functions) load. To get around the problem if it has already occurred, install the OS, install the new configuration record, then go back to the special functions load and proceed with the VOL label updates. ORIGINATOR: N. Jones SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB047 Pg001 FIB 00048 06/01/88 *** Helpful Programs to Spot Files Almost Full ( ERR 2s) [ WPS 431 ] *** During a recent USERS GROUP meeting the following suggestions were made: QUESTIONS & SUGGESTIONS 1. Many times files get full without anyone realizing it until an error 2 condition is reach. Can a utility be written where an operator is able to input a percent and the system will search for all files that are over that percent and print them out? 2. If during processing an error 2 is about to happen, can a utility somehow flag this and let the operator know that they can not add more records to that file? ANSWERS 1. There is no utility to do this but the following BASIC programs will do this for you. There are two examples for doing this. o Using FID (all BOSS/VS levels) o Using ATTR (8/9.6 and up) First create a FILELIST using the utility !DIR with no attributes and data only. A. PROGRAM TO FIND PERCENT FULL USING FID. 10 BEGIN 20 PRINT 'CS' 30 REM "ENTER PERCENT WITH DECIMAL POINT EG: .50" 40 INPUT "PERCENT ",D 50 REM "CREATE FILELIST USING !DIR WITH NO ATTRIBUTES AND DATA ONLY" 60 OPEN(1)"filelist" 70 READ(1,END=9999)A$ 80 OPEN(2)A$ 90 B$=FID(2) 100 REM "LOOK FOR INDEXED OR DIRECT FILES" 110 IF DEC(B$(10,1))=2 OR DEC(B$(10,1))=0 GOTO 120 ELSE CLOSE(2);GOTO 70 120 A=DEC (B$(25,4)),B=DEC(B$(12,3)) 130 REM "A=RECORDS USED,B=RECORDS DEFINED" 140 IF A/B => D PRINT A$ 150 CLOSE(2);GOTO 70 9999 END B. PROGRAM TO FIND PERCENT FULL USING ATTR. 10 BEGIN 20 PRINT 'CS' 30 REM "ENTER PERCENT WITH DECIMAL POINT EG: .50" 40 INPUT "ENTER PERCENT ",D 50 REM "FILELIST CREATE BY !DIR WITH NO ATTRIBUTES AND DATA ONLY" 60 OPEN(1)"filelist" SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB048 Pg001 65 READ(1,END=9999)A$ 70 OPEN(2) A$ 80 B1$=ATTR(2,"ORGANIZATION") 90 REM "LOOK FOR ONLY INDEXED AND DIRECT FILES" 100 IF B1$="DIR" OR B1$="IND" GOTO 110 ELSE CLOSE(2);GOTO 65 110 B$=ATTR(2,"RECORDS_USED");C1$=ATTR(2,"RECORDS_ALLOWED") 120 A=NUM(B$),B=NUM(C1$) 130 REM "A=RECORDS USED,B=RECORDS DEFINED" 140 IF A/B => D PRINT A$ 150 GOTO 65 9999 END NOTES: A. For more information on how to use FID refer to the BB86 reference manual (M6262A) pages 10-16, 10-17. B. For more information on how to use ATTR refer to the BB86 reference manual (M6262A) pages 5-7 to 5-10. C. This example will only work for indexed and direct files, for any other files please see note A and B. 2. How to prevent an ERROR 2 during process? In your applications you will have to use the FID or ATTR to find out how many records are left in the file. (see examples above) We apreciate the suggestions from this USERS GROUP and if your next USERS GROUP has any questions or suggestions please let us know. ORIGINATOR: Joe Melendez SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB048 Pg002 FIB 00049 06/01/88 *** Printers lose Top of Forms - affects 8/9.6A [ WPS 462 ] *** PROBLEM: On levels 8/9.6A print jobs lose TOP OF FORM on all printers. This can happen if the printer is in DISCONNECT, RESERVED or SPOOLED mode. CAUSE: Whenever the printer is accessed from BASIC through an OPEN statement, the VFU is loaded which sets TOP OF FORM. For example, the first job prints correctly and the job ends in the middle of the page. The next job will start in the middle of the page and now the job has lost the correct position for TOP OF FORM. WORKAROUND: On 8/9.6A there is not a workaround for this problem. This has been changed in 8/9.6B to cause the VFU not to load at the OPEN of a printer. ORIGINATOR: L. Sanders SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB049 Pg001 FIB 00050 06/23/88 *** Automatic Start-up for FTF after Type 1 Load [ WPSF 468 ] *** The following are the steps that you must do in order to start FTF automatically after a type 1 LOAD. 1. LOAD ".NSPGM.B4NET" 2. Modify the following lines: DELETE 210 DELETE 265 DELETE 230 Add Statement 230 : 230 GOTO 262 DELETE 263 Add Statement 263 : 263 RELEASE 3. Save this program to another node. Example: SAVE "(DISK).USER.STARTFTF" 4. Create a user account. Example: ! SECURITY.CREATE MAJOR ACCOUNT : MAJOR MINOR ACCOUNT : MINOR INIT CMD : BASIC STARTFTF ACCOUNT LEVEL : F 2 T T T T PREFIX LIST : (DISK).USER. 5. Edit the .SYSDATA.START.CMD and add the following: ! START Tx (Tx = Your terminal),USERID=MAJOR.MINOR,GROUP=TERMINALS 6. SAVE .SYSDATA.START.CMD 7. Do a type 1 LOAD and RUN "B4NET" then choose option 2. The FTF will now be in startup mode. ORIGINATOR: J. Melendez SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB050 Pg001 FIB 00051 06/23/88 *** BQR ERRs 10/14 on Files Transported from an SPX [ WPSF 470 ] *** After restoring files from a BOSS/IX system to a BOSS/VS system using !MCSI, you must run "BQR" to convert these files. "BQR" will not convert files that have special characters (-,=,+,etc). You will get an ERROR 10 or 14. The following patch will allow you to convert these files without problems. Please make the following changes on the BOSS/VS side: 1. Load "BQR3" 2. Add The Following Statements: 1115 A=POS (")" = D1$);NFAMD1$=D1$(A+1) 2066 T1$=PFX + FID (0) + "TYU"; GOTO 2069 2069 CLOSE (D) 2071 IF HTA (H3$(69,1))="00" GOTO 2075 ELSE GOTO 1900 3. SAVE "BQR3" BOSS/VS Notes: A) If file names are greater than 6 characters and contain special characters, MCSI will create new file names using the last 6 characters of the original file name. Example: If you have a file name as "+ABCDEFG" this file will be renamed as "BCDEFG". Therefore, it is important to make sure that there is not a file already named "BCDEFG". MCSI will erase the existing file if the option "Delete Existing files" = "y". Otherwise MCSI will skip this file. B) Composite prefix list will not work. Example: "().USER.,.SYSMGR.". Use a single prefix list. Example: "().USER." C) This patch will not convert files that have lower case characters. The recommendation is to rename there files to upper case prior to the conversion. BOSS/IX Notes: "cwrite" will abort with the message "AN ILLEGAL INSTRUCTION OR DIVIDE BY ZERO HAPPENED. ENTER ANY CHARACTER TO ABORT" if the file has zero records used. Files with zero records can be found by printing a directory listing with attributes. These files should not be converted but can be recreated on the BOSS/VS system. Conversion of special character file names will be fixed in a future BOSS/VS release. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB051 Pg001 ORIGINATOR: J. Melendez SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB051 Pg002 FIB 00052 08/16/88 *** Release 9.6C/8.6C Software Announcement [ WPSS 157 ] *** MAI Basic Four, Inc. is pleased to announce that the new system software revisions, 9.6C/8.6C, are now available. The 9.6C revision is the recommended revision for MPx 9xxx Series Systems. The 8.6C release is the recommended revision for MPx 7xxx and 8xxx Series Systems. **************************************************************** * * * o Installation procedures have been revised for 9.6C/8.6C. * * Please read the installation instructions before * * attempting installation or upgrade. These instructions * * assume the reader is familiar with BOSS/VS O.S. * * installation and TYPE 3 LOAD Special Functions. * * * * o In preparation for future MPx enhancements, positioning of * * the image slots has been adjusted slightly. Therefore, * * previous O.S./WCS levels cannot reside in slots on the * * same disk with release levels 9.6C/8.6C. In addition, ALL * * slots must be updated when upgrading 9.6C/8.6C. * * * * o As of this release, T0 must be a model 4309 or later * * terminal or an HVDT. Terminal models 7250 and 7270 are no * * longer supported as T0. This change was made to improve * * backup times in TYPE 2 and TYPE 3 LOADS. * * * * o The .SYSDATA.SECURITY.DATA file should be saved before * * upgrading to 9.6C/8.6C. For details, see the section on * * the new SECURITY.DATA file in this announcement. * * * * o The 9.6C/8.6C Software Announcement exists as a serial * * file on the official release tape. To print a copy, submit * * the following file to the printer: * * * * .R6C11.INST.DOC.ANNOUNCE6C * * * **************************************************************** Copyright 1988, Rev. 1988, MAI Basic Four, Inc. All rights reserved. C O N T E N T S _ _ _ _ _ _ _ _ 1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . 2 1.1 ENHANCEMENTS IN THIS RELEASE . . . . . . . . . . . . . 2 1.2 CONFIGURATION RECORD CONSIDERATIONS . . . . . . . . . 3 1.3 SOFTWARE ANNOUNCEMENT . . . . . . . . . . . . . . . . 3 2 FIXES IN THIS RELEASE . . . . . . . . . . . . . . . . . 4 2.1 UTILITIES . . . . . . . . . . . . . . . . . . . . . . 4 2.1.1 GSR . . . . . . . . . . . . . . . . . . . . . . . . 4 2.1.2 ERRORLOG . . . . . . . . . . . . . . . . . . . . . . 4 2.1.3 SPOOLER/PRINTERS . . . . . . . . . . . . . . . . . . 4 2.1.4 TERM.CONFIG . . . . . . . . . . . . . . . . . . . . 6 2.2 BASIC . . . . . . . . . . . . . . . . . . . . . . . . 6 2.3 FILE SYSTEM . . . . . . . . . . . . . . . . . . . . . 6 2.4 TYPE 3 LOAD . . . . . . . . . . . . . . . . . . . . . 7 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg001 2.5 ISDC OPERATING SYSTEMS . . . . . . . . . . . . . . . . 7 2.6 COMMUNICATIONS . . . . . . . . . . . . . . . . . . . . 7 2.6.1 MAGNET . . . . . . . . . . . . . . . . . . . . . . . 7 2.6.2 TBC . . . . . . . . . . . . . . . . . . . . . . . . 7 2.7 OPERATING SYSTEM . . . . . . . . . . . . . . . . . . . 8 3 HISTORY . . . . . . . . . . . . . . . . . . . . . . . . 9 4 BOSS/VS . . . . . . . . . . . . . . . . . . . . . . . . 12 4.1 UTILITIES . . . . . . . . . . . . . . . . . . . . . . 12 4.1.1 SECURITY . . . . . . . . . . . . . . . . . . . . . . 12 4.1.1.1 The New SECURITY.DATA File . . . . . . . . . . . . 12 4.1.2 SPOOLER . . . . . . . . . . . . . . . . . . . . . . 14 4.1.2.1 Trial Forms Using Live Data . . . . . . . . . . . 14 4.1.2.2 SPOOLER REQUESTS File . . . . . . . . . . . . . . 16 4.1.3 TERM.CONFIG . . . . . . . . . . . . . . . . . . . . 17 4.1.3.1 Async Enhancements . . . . . . . . . . . . . . . . 17 4.1.3.1.1 TERM.CONFIG Update . . . . . . . . . . . . . . . 17 4.1.3.1.2 XON/XOFF Options . . . . . . . . . . . . . . . . 19 4.1.3.1.3 Drop DTR Option . . . . . . . . . . . . . . . . 19 4.1.3.2 Additional TERM.CONFIG Changes . . . . . . . . . . 20 4.2 FILE SYSTEM . . . . . . . . . . . . . . . . . . . . . 21 4.2.1 Increased Buffer Cache . . . . . . . . . . . . . . . 21 4.3 BROADCAST . . . . . . . . . . . . . . . . . . . . . . 22 4.4 DIAGNOSTICS . . . . . . . . . . . . . . . . . . . . . 24 4.4.1 REMIDI . . . . . . . . . . . . . . . . . . . . . . . 24 4.4.1.1 REMIDI on MPx 7000, 7100, and 8000 Series Systems 24 4.4.1.1.1 Updating the Load Directory for REMIDI . . . . . 24 4.4.1.2 REMIDI on MPx 9xxx Series Systems . . . . . . . . 26 4.4.1.2.1 Updating the Load Directory for REMIDI . . . . . 26 4.4.2 Updating the Load Directory for DEMON . . . . . . . 27 4.5 CONFIGURATIONS . . . . . . . . . . . . . . . . . . . . 29 4.5.1 Configurations for MPx 7000/7100/8000 Series Systems 29 4.5.2 Configurations for MPx 9000/9100/9400 Series Systems 30 4.5.3 Configurations for MPx 9500/9600 Series Systems . . 31 5 HARDWARE . . . . . . . . . . . . . . . . . . . . . . . . 33 5.1 MPX 7000, 7100, AND 8000 PCBA NOTES . . . . . . . . . 33 5.2 MPX 9XXX SERIES SYSTEM PCBA NOTES . . . . . . . . . . 35 5.3 PCBA'S FOR ALL SYSTEM TYPES . . . . . . . . . . . . . 38 6 INSTALLATION . . . . . . . . . . . . . . . . . . . . . . 40 6.1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . 40 6.2 NEW INSTALLATION . . . . . . . . . . . . . . . . . . . 42 6.2.1 INSTALLING THE OPERATING SYSTEM . . . . . . . . . . 42 6.2.1.1 Loading Slots 0 and 1 Using ALT LOAD . . . . . . . 42 6.2.1.2 TYPE 3 LOAD (Special Functions) . . . . . . . . . 44 6.2.1.2.1 OPTION 1 (CHANGE VOLUME LABEL INFORMATION) . . . 45 6.2.1.2.2 OPTION 2 (UPDATE FAMILY INFORMATION) . . . . . . 45 6.2.1.2.3 OPTION 3 (INITIALIZE FAMILY DIRECTORY) . . . . . 46 6.2.1.2.4 OPTION 4 (CHANGE INSTALLATION PARAMETERS) . . . 46 6.2.1.3 Restoring the O.S. . . . . . . . . . . . . . . . . 47 6.2.2 INSTALLING THE CONFIGURATION RECORD . . . . . . . . 48 6.3 UPGRADING TO 8.6C FROM RELEASE LEVELS 8.4D AND BELOW . 50 6.3.1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . 50 6.3.2 PRELIMINARY EVALUATION . . . . . . . . . . . . . . . 51 6.3.2.1 Hardware Evaluation . . . . . . . . . . . . . . . 51 6.3.2.2 File Preparation . . . . . . . . . . . . . . . . . 51 6.3.2.3 New File System Space Requirements . . . . . . . . 52 6.3.2.4 Saving Files to Tape . . . . . . . . . . . . . . . 53 6.3.3 OPERATING SYSTEM UPDATE and FILE CONVERSION . . . . 54 6.3.3.1 Installing the O.S. . . . . . . . . . . . . . . . 54 6.3.3.1.1 Loading Slots 0 and 1 Using ALT LOAD . . . . . . 54 6.3.3.1.2 TYPE 3 LOAD (SPECIAL FUNCTIONS) . . . . . . . . 56 6.3.3.1.2.1 OPTION 1 (CHANGE VOLUME LABEL INFORMATION) . . 57 6.3.3.1.2.2 OPTION 2 (UPDATE FAMILY INFORMATION) . . . . . 57 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg002 6.3.3.1.2.3 OPTION 3 (INITIALIZE FAMILY DIRECTORY) . . . . 58 6.3.3.1.2.4 OPTION 4 (CHANGE INSTALLATION PARAMETERS) . . 58 6.3.3.1.3 Restoring the O.S. . . . . . . . . . . . . . . . 59 6.3.3.2 INSTALLING THE CONFIGURATION RECORD . . . . . . . 60 6.3.3.3 CONVERTING FILES . . . . . . . . . . . . . . . . . 61 6.3.3.3.1 Tape to Disk Conversion . . . . . . . . . . . . 61 6.3.3.3.2 Disk to Disk Conversion . . . . . . . . . . . . 61 6.3.3.3.3 Check Files . . . . . . . . . . . . . . . . . . 62 6.3.4 UPDATING THE TERMINAL CONFIGURATION FILE . . . . . . 62 6.4 UPGRADING TO 8.6C FROM RELEASE LEVELS 8.4E AND ABOVE . 64 6.4.1 SAVING FILES TO TAPE . . . . . . . . . . . . . . . . 64 6.4.2 OPERATING SYSTEM UPDATE . . . . . . . . . . . . . . 64 6.4.2.1 Loading Slots 0 and 1 Using ALT LOAD . . . . . . . 64 6.4.2.2 Changing Installation Parameters . . . . . . . . . 66 6.4.2.3 Restoring the O.S. . . . . . . . . . . . . . . . . 68 6.4.3 INSTALLING THE CONFIGURATION RECORD . . . . . . . . 68 6.4.4 UPDATING SLOTS 2 AND 3 ON 7xxx and 8xxx SYSTEMS . . 69 6.4.4.1 Updating WCS Slot Two (2) . . . . . . . . . . . . 70 6.4.4.2 Updating Slot Three (3) . . . . . . . . . . . . . 70 6.4.4.2.1 Updating WCS Slot Three (3) . . . . . . . . . . 70 6.4.4.2.1.1 On 7000/7100 Systems and 8000 Systems with LAN 70 6.4.4.2.1.2 On 8000 Systems Without LAN . . . . . . . . . 71 6.4.4.2.2 Updating O.S. Slot Three (3) . . . . . . . . . . 71 6.4.5 SLOT INFORMATION . . . . . . . . . . . . . . . . . . 72 6.5 UPGRADING TO 9.6C . . . . . . . . . . . . . . . . . . 73 6.5.1 SPECIAL CONSIDERATIONS . . . . . . . . . . . . . . . 73 6.5.2 PRINTING OUT THE TERMINAL CONFIGURATION INFORMATION 73 6.5.3 SAVING FILES TO TAPE . . . . . . . . . . . . . . . . 73 6.5.4 OPERATING SYSTEM UPDATE . . . . . . . . . . . . . . 74 6.5.4.1 Loading Slots 0 and 1 Using ALT LOAD . . . . . . . 74 6.5.4.2 Changing Installation Parameters . . . . . . . . . 76 6.5.4.3 Restoring the O.S. Files . . . . . . . . . . . . . 77 6.5.5 INSTALLING THE CONFIGURATION RECORD . . . . . . . . 78 6.5.6 UPDATING SLOTS 2 AND 3 ON MPx 9xxx SERIES SYSTEMS . 79 6.5.6.1 Updating WCS Slot Two (2) . . . . . . . . . . . . 79 6.5.6.2 Updating WCS Slot Three (3) . . . . . . . . . . . 80 6.5.6.3 Updating the Load Directory for REMIDI . . . . . . 80 6.5.6.4 Updating O.S. Slot Three (3) . . . . . . . . . . . 81 6.5.7 SLOT INFORMATION . . . . . . . . . . . . . . . . . . 81 6.6 UPDATING SLOTS 0 AND 1 USING UPDATE.OS AND UPDATE.WCS 83 6.6.1 Updating O.S. Slots 0 and 1 . . . . . . . . . . . . 83 6.6.2 Updating WCS Slots 0 and 1 . . . . . . . . . . . . . 84 6.7 SYSTEM STARTUP . . . . . . . . . . . . . . . . . . . . 85 6.7.1 STANDARD STARTUP COMMAND FILE . . . . . . . . . . . 85 6.7.1.1 Command File Definitions . . . . . . . . . . . . . 85 6.7.2 IMPLICATIONS . . . . . . . . . . . . . . . . . . . . 86 7 RELATED DOCUMENTATION . . . . . . . . . . . . . . . . . 90 F I G U R E S _ _ _ _ _ _ _ Figure 6-1. Restore Screen . . . . . . . . . . . . . . . . 48 Figure 6-2. Restore Screen . . . . . . . . . . . . . . . . 59 Figure 6-3. Restore Screen . . . . . . . . . . . . . . . . 68 Figure 6-4. Operating System Information . . . . . . . . . 72 Figure 6-5. Restore Screen . . . . . . . . . . . . . . . . 78 Figure 6-6. Operating System Information . . . . . . . . . 82 1. INTRODUCTION ____________ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg003 1.1. ENHANCEMENTS IN THIS RELEASE ____________ __ ____ _______ The 9.6C/8.6C release contains the following enhancements: o Support for the new MPx 9400 Series Systems, which feature the new DMA-II controller for SCSI ("Small Computer System Interface") disk and tape devices. o Support for the new, more compact MPx 9600 Series Systems, which provide the same computing power as MPx 9500 Series Systems. o Support for the new, higher density, 250 MB, 5 1/4-inch SCSI disk drive for MPx 9400 Series Systems, via the new DMA-II controller. o Support for the new 120 MB, 1/4-inch, embedded SCSI MCS tape unit, via the new DMA-II controller. o A new SPOOLER TESTPRINT option, which allows printing of trial forms with live data. o A new TERM.CONFIG option for bidirectional XON/XOFF flow control. o A new TERM.CONFIG option for dropping DTR on process release. o A new ALT LOAD from tape, which loads both O.S. slots 0 and 1. (Previously, only O.S. slot 0 could be loaded with ALT LOAD.) o Automatic reconstruction of the SPOOLER REQUESTS file at load time after a system dump. Previously, this file had to be reconstructed by the user. o Increased buffer cache for high use data files to decrease disk input/output operations and increase system performance on large, heavily loaded systems. o Improved logon account security. o A BROADCAST facility, which provides for inter-terminal message sending. o TYPE 2 and TYPE 3 LOAD standalone functions now have enhanced performance on systems with a serial terminal as T0. As a result, T0 must be a model 4309 (EVDT) or later terminal (or an HVDT). Terminal models 7250 and 7270 are no longer supported as T0. o An enhancement to the DIR utility, which allows the first line of a BASIC program to be printed or displayed on a terminal when ATTRIBUTES = ALL is selected. 1.2. CONFIGURATION RECORD CONSIDERATIONS _____________ ______ ______________ A new configuration record is not required when upgrading from release 9.6A/B to 9.6C or from release 8.6A/B to 8.6C. A new SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg004 configuration record is required, however, when upgrading from 8.4 and 9.5/8.5 releases to 9.6C/8.6C releases. A new configuration record is also required when an upgrade includes new hardware. 1.3. SOFTWARE ANNOUNCEMENT ________ ____________ The 9.6A/8.6A and 9.6C/8.6C Software Announcements exist as serial files on the official 9.6C/8.6C O.S. release tape, which allows the user to print copies, if needed. To print these documents, SUBMIT the following files to the printer: (family).R6Cxx.INST.DOC.ANNOUNCE6A 9.6A/8.6A (family).R6Cxx.INST.DOC.ANNOUNCE6C 9.6C/8.6C Fixes in this Release 2. FIXES IN THIS RELEASE _____ __ ____ _______ The 9/8.6C releases contain fixes for the following system problems: 2.1. UTILITIES _________ 2.1.1. GSR ___ SPR 510110 - The GSR replace option took a long time to complete when used on BASIC programs. 2.1.2. ERRORLOG ________ 1) SPR 514096 - ERRORLOG displayed total ECC errors in the ECX column of the "Totals Summary" display. The ECC and ECX counts have now been consolidated into a single column with the heading "Memory Errors". 2) SPR 514558 - The ERRORLOG display for memory errors would only go up to 12 megabytes. ERRORLOG nows displays errors for up to 24 megabytes. The screen display will change to the 24 megabyte format when an error above 12 megabytes occurs. 2.1.3. SPOOLER/PRINTERS ________________ 1) SPR 512810 - Powering model 4217/4218 printers off then on caused a 2 minute delay before a printer status was returned. This timeout has been reduced to 35 seconds. 2) SPR 513028 - THE SPOOLER CLASS definitions were not converted on an upgrade from 9/8.5. 3) SPR 513687 - If a family was full, the system would dump at system load during initialization of the SPOOLER with the fourtuples 40,x,x,x and 8,x,15,13. Now the following message is displayed: SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg005 "(Family Name) Family full - out of usable disk space. Use TYPE 2 LOAD to delete files. Please reboot." The system will then hang but will not dump. Unnecessary files should then be deleted in a TYPE 2 LOAD to free disk space. 4) SPR 514199 - Taking a printer offline during a BASIC print program would sometimes cause the terminal to hang and print lines to be lost. 5) SPR 514220 - When a printer was despooling a job, and a user RESERVEd this printer with the option "WHEN=J", (meaning RESERVE the printer after the current job is complete), the spool job stopped at 96% complete. 6) SPR 514389 - The length for a spool file extent on 9/8.6 releases was much shorter than on 9/8.5 releases, causing excessive extents to be created. This sometimes resulted in a delay while creating and deleting spool files. The length for a spool file extent has now been increased to match the extent length on 9/8.5 releases. 7) SPR 514475 - The SPOOLER would automatically reset the lines per inch to 10 at the beginning of each print line. Therefore, if the user programmatically selected a line pitch other than 10, his specified print mode would not be used. The SPOOLER now resets the print mode only at the beginning of each copy of a job, so the print mode can be changed programmatically thereafter. 8) SPR 514583 - Under certain circumstances, multiple users could RESERVE the same printer. 9) SPR 514659 - "Time to Print" did not work when defined in a class that was specified in BASIC. 10) SPR 514972 - If printers using the Diablo driver (models 4211, 4215, 4216, 4223) were taken offline during the printer status display, all other spooled printing would stop, and terminals would hang for 20-30 seconds, until the printer status was updated. Now only the printers using Diablo drivers will be delayed when taken offline. Other printers will not be affected. 11) SPR 514974 - Print data was lost when printing spool jobs on XON/XOFF printers configured as system printers. 12) SPR 515189 - Printer models 4105 and 4308 were assigned the wrong type of slave printers. Model 4105 was assigned a "MAI Basic Four" slave printer, and model 4308 was assigned an "IS" slave printer. The correct slave printers now assigned are "Industry Standard" for model 4105 and "Basic Four" for model 4308. 13) SPR 515291 - Printer model 4200 printed a '?' at the end of every line. 14) SPR 515900 - Vertical tab ('VT') and slewing did not reset expanded print ('EP'). SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg006 15) SPR 516357 - Print data was lost when a job was modified to another printer while the last block of data was being transferred (near the end of the job). 16) SPR 516562 - The first line of print data was lost when printer models 4217/4218 were powered off then on. 17) SPR 516700 - A system dump with the fourtuples 2,10,33,34 and 1,16,0,34 was caused when the Spooler encountered an invalid status on a laser or letter quality printer. An I/O error is now returned. 18) Fix Without SPR - Serial printers in RESERVE mode that were being polled by PRSTATUS from another terminal would hang. 2.1.4. TERM.CONFIG ___________ SPR 511815 - The HELP screens for terminal types have now been updated for 9/8.6. 2.2. BASIC _____ 1) SPR 514745 - BASIC DEVINFO would not return the proper status bits for DISCONNECTED/OPENED printers. 2) SPR 515230 - START from a called BASIC program would get a fatal error when the program being STARTed did not exist and an error catcher (SETERR or ERR=) was specified. When executed from CLI, the program returned an ERR 525, and when executed from BASIC, the fourtuple 1,142,0,25 was returned. 3) SPR 515919 - Only 32736 bytes were allowed as the maximum size for the DIM of a string, when it should have been 32767. 2.3. FILE SYSTEM ____ ______ 1) SPR 507692 - A system dump with the fourtuples 2,10,6,3 and 1,133,0,3 occurred when an attempt was made to DELETE a file with a corrupted control segment (file format error). 2) SPR 514338 - "End of File" (ERROR 2) was returned to BASIC when a user attempted to read the last record in a serial file by index. 3) SPR 516076 - A system dump with the fourtuples 6,1,72,1 and 2,10,34,43 occurred because the system had insufficient special shadow. The File System now uses less space in the special shadow area. 2.4. TYPE 3 LOAD ____ _ ____ SPR 513898 - TYPE 3 LOAD did not return the Dump Area to the File System when changing a disk from a System to a Data pack. 2.5. ISDC OPERATING SYSTEMS ____ _________ _______ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg007 1) SPR 514394 - A port hang was caused by a print buffer being full at the time an XOFF was received. 2) SPR 514395 - DOWN.LOAD caused a system hang. 2.6. COMMUNICATIONS ______________ 2.6.1. MAGNET ______ 1) SPR 513846 - System dump 2,7,3,10 caused by GATEWAY workspace corruption. 2) SPR 515056 - An ERROR 33 would occur when MAGNET ran out of "sockets". (A socket is a mailbox which allows users to transmit and receive messages via MAGNET.) System management of sockets is now more efficient. 3) SPR 515846 - A remote user was allowed access to a file for which he did not have usage rights. An ERROR 13 (Improper file/device access) is now returned. 2.6.2. TBC ___ 1) SPR 512861 - The TBC "no spooling" option did not route data to a punch device. 2) SPR 514425 - The ACS timer activated BCOM at midnight instead of the specified time. 2.7. OPERATING SYSTEM _________ ______ 1) RSC 516290 - A meaningful warning message is now displayed when an attempt is made to do an O.S. update on a data disk using tape load. 2) SPR 516368 - A system dump with the fourtuples 3,4,1,19 and 6,0,17,3 was caused by an uninitialized I/O module variable. 3. HISTORY _______ 8.6B/9.6B Acceptable This release contains the following enhancements: Support for the 4314 terminal, which features dual serial ports and 132 character screen; Automatic type conversion of numeric/string fields in Multi-key files; VFU load no longer done when a printer is in RESERVE or DISCONNECT mode. 8.6A/9.6A Acceptable This release contains the following enhancements: A new and enhanced SPOOLER; new JOB MANAGER utilities, including JOB ACCOUNTING; MAGNET, which includes a Local Area Network and a Wide Area Network; Business BASIC 86, which offers several new BASIC features, including Multi-key Files; 19.2K BPS asyncronous communications; SECURITY utility enhancements; CLI SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg008 Batch Subsystem; Support for 24 megabytes of main memory and 255 devices on MPx 9500 Series Systems. 8.5E/9.5E Acceptable This release provided improvements to the COPY, SAVERESTORE, and UPDATE.RIGHTS utilities, BASIC, the File System, and Type 3 Load Backup. 8.5D/9.5D Obsolete Enhancements include: A new CONFIG.MGR utility for displaying and installing configuration records; Four SPOOLER fixes; DISKANALYZER reconstruction of serial files; Manual selection of different print modes on DMP printers; an optional enhanced ATP package. 8.5C/9.5C Obsolete Enhancements include: Expanded ERRORLOG reporting; Optimization of DataWord files; Number of logical channels increased to 64; Support for 8 bit character sets; DISKANALYZER reporting of required disk space for reconstruction. Mpx 9000 and 9500 systems only: 32 bit CPU; increased main memory; number of maximum devices increased to 164; new DMA controller for increased performance; enhanced CPU processing for faster arithmetic and logical operations; RSTACK cache; overall performance increase which is 2-3 times that of 7000/7100/8000 systems; support for the faster 8-inch fixed disk. Mpx 9500 only: DATA and CODE caches for additional increased performance. 8.5B Obsolete In this release the system model number has been included in the configuration record, the COMPARE utility has been fixed so that it completely compares BASIC program files, and a new TBC AUTODIAL feature allows for definition and retrieval of multiple station lists. 8.5A Obsolete Enhancements include: Increased file system concurrency for greater throughput, support for 7000/7100 series systems, proportional growth for DIRECT and SORT files, maximum number of open files increased to 512, maximum number of tasks sharing same file increased to 512, file selectable write-through, DISKANALYZER also available in stand-alone mode, DISKANALYZER reconstruct of directory and available space files, maximum number of system printers increased to 99, system dumps written directly to tape, system support for the DMP serial printer, new terminal services error utility, DataWord printer queue enhancements, enhanced SAVERESTORE utility. 8.4E Acceptable This release contains all the features of the 8.5A/B/C/D releases, with the exception of the 8.5 performance enhancements. 8.4D Obsolete SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg009 Contained fixes for BASIC PRECISION, EXTTAPE, COBOL, and FILESIZE. 8.4C Obsolete Enhanced features included: Buffered Magnetic Tape Controller, 1/2" tape support, DEDICATE with expanded error reporting, new ISDC OS for 4-way, 8-way and 16-way, FILESIZE utility. 8.4B Obsolete Enhanced features include: 8 megabytes of main system memory, 16-port Asynchronous Controller, point-to-point file specification, QUIET mode for utilities, BASIC statement numbers up to 16000, Buffered Magnetic Tape Controller (BMTC) 1/4" tape support, S/10 Industry Standard Printer as slave printer. 8.4A Obsolete This release contained significant enhancements including 6 megabytes of main system memory, 96 devices, 84 total serial devices, disk to disk sequential family backup, enhanced hardware error log, system load progress monitor, and fast reconstruct utility. 8.2C Obsolete This release contained a WCS fix to support rezero fault clear, disk error recovery and a fix to the IMLC. 8.2B Obsolete This release contained all of the above features but was required for the 8000 Series systems due to a change in the WCS image for that hardware. 8.2A Obsolete This release contained significant enhancements providing NO EXTEND BASIC, 68 serial devices, math functions, X.25 Communications, DataWord 3.0. File System write through and BULLETIN board availability. 8.1B Obsolete Enhanced features include: 31 logical units in BASIC, increase in file system cache from 208 to 225 unique files, MULTIREELSR, family image backups, SAVERESTORE backup files having the Lack-of-Integrity bit set. Bugs were fixed in DISKANALYZER, SAVERESTORE and many of the system dumps. 8.1A Obsolete Introduction of the System 810 hardware and BOSS/VS software. 4. BOSS/VS _______ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg010 4.1. UTILITIES _________ 4.1.1. SECURITY ________ 4.1.1.1. The New SECURITY.DATA File ___ ___ _____________ ____ A new SECURITY.DATA file format is being released to 9/8.6C. The change is being made in order to improve access security to MPx. This section provides the general features of the change. 1. The major and minor accounts have been removed from the account profile so that "viewing" a record in SECURITY.DATA is no longer sufficient to know to whom the profile belongs. 2. The password is now encrypted using a better algorithm that will eliminate the ability to log on successfully using any one of several "equivalent" passwords. 3. The sequence of fields in an account profile has been ordered differently. 4. The entire profile record is now encrypted before being written to the SECURITY.DATA file. Even if one were able to "view" a record, it would not be possible to comprehend its contents without decryption. 5. The key used to read, write, modify, or delete an account in SECURITY.DATA, i.e., ., is now scrambled in order to prevent associating a record with a specific account. The conversion of SECURITY.DATA from the old format to the new is accomplished in two steps, both automatic: 1. During system load time, any record in SECURITY.DATA that has not already been converted is changed to the new format with the exception of the password field. The code that affects this conversion is resident at load time only, and no operator action is necessary to initiate or control the activity. 2. Whenever an account successfully logs onto the system using the old form of the password, the value of the password used to gain entry to the system is encrypted using the new algorithm, and the entire account profile is rewritten to the disk. Installations that have a large number of accounts in their security file (e.g., several hundred) will experience an additional one to two minutes of running time during system load during which this conversion activity takes place. Once a SECURITY.DATA file has been converted, no further load-time work will be required to support the conversion, and loading time will revert to its usual duration. Customers who install 9/8.6C should be advised in advance that SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg011 their SECURITY.DATA files will be modified the first time the new release is loaded. 9/8.6C SECURITY.DATA files cannot be used on previous releases. Therefore, the .SYSDATA.SECURITY.DATA file should be backed up on the old release prior to upgrade, in the event of an O.S. downgrade. Finally, all interfaces to SECURITY.DATA remain unchanged as a result of this conversion. As long as customers are doing all their maintenance of the file through the SECURITY utility, no difficulty will be experienced in making changes to the file. However, any attempt to open the file through BASIC and to work with its contents using READRECORD and WRITERECORD, will no longer work correctly. (Such access of the SECURITY.DATA file is not supported by MAI Basic Four, Inc.) 4.1.2. SPOOLER _______ 4.1.2.1. Trial Forms Using Live Data _____ _____ _____ ____ ____ On release levels 9/8.6A and 9/8.6B the SPOOLER forms alignment using the TRIAL FORM feature of SETFORM is carried out by showing the dimensions of the FORM definition, and the positions of the slew channels defined therein. This description is called the Box representation of the FORM definition. While such a technique is suitable for ensuring that the paper is entirely contained by the FORM definition, some have expressed a preference for using actual print data to guarantee a more precise alignment. Accordingly, the 9/8.6C version of the SPOOLER will also support the use of a Live-Data representation of the FORM definition for paper positioning. The choice of which representation to be used is made at the time SETFORM is called up for execution. The parameter indicating which representation to use is called LIVEDATA and its default value is FALSE (use the Box representation). One possible use of SETFORM might look like this: !SETFORM LP,FORM=SPEC,LIVEDATA=T,START=3,NUMPAGES=2 Then, when CTL-I is entered at the ACTION prompt, the Live-Data will be printed provided there is a job waiting that satisfies the eligibility requirements in all other respects. If no such job exists, the Box representation will be generated instead. The Live-Data representation is formed by reading from the file to be printed and converting all alphabetic characters to upper case X, and all numeric digits to 9. The revised syntax of the new SETFORM command is as follows: !SETFORM [{,FORM = } {,LIVEDATA = } {,START = <1> } {,NUMPAGES = <1> } {,VERIFY = } {,PAUSE = } SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg012 {,OUTPUT = } {,OUTACTION = } Trial Forms {,QUIET = }] Of course, SETFORM may also be run from the Utility menu or in command mode without parameters. The START parameter is the page number of the spool job where the Trial Form is to begin printing. The NUMPAGES parameter is the number of pages of Trial Forms to print. SPECIAL CONSIDERATIONS 1. If the spool job begins with a form feed, the START parameter must be at least "2". If the START parameter is "1", the SPOOLER will count the form feed as one page, and no trial forms will be printed. 2. Printing of Trial Forms will abort if the printer is taken offline or if an error occurs while they are printing. 3. If there are jobs in the spool queue for the same FORM and PRINTER that are ahead of the job for which you wish to print Trial Forms, there are two ways to assure that the Trial Forms are printed for the correct job: a) The jobs that are ahead can be stopped to allow printing of Trial Forms for the desired job. b) When the job you wish the Trial Forms printed for is SUBMITted, specify the parameter LOADFORMS=T. This will cause that job to stop and wait for a SETFORM when it comes up in the queue. 4.1.2.2. SPOOLER REQUESTS File _______ ________ ____ The SPOOLER REQUESTS file contains names of SPOOLER files that have been submitted to the printer. The REQUESTS file can become corrupted when there is a fatal system error (i.e., a system dump). Prior to the 9/8.6C releases, when the REQUESTS file was observed to lack integrity at system load time, it was renamed to BADREQUESTS. To reestablish SPOOLER access to the files named in BADREQUESTS, it was necessary to reconstruct the BADREQUESTS file with DISKANALYZER. Beginning with the 9/8.6C releases, the system automatically reconstructs the REQUESTS file at load time, if it is observed to lack integrity. TERM.CONFIG/Async Enhancements 4.1.3. TERM.CONFIG ___________ 4.1.3.1. Async Enhancements _____ ____________ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg013 The 9/8.6C O.S. release adds two major new asynchronous features. These are Bidirectional XON/XOFF flow control and _____________ ________ ____ _______ Dropping DTR signal on terminal release. These features are ________ ___ ______ __ ________ _______ configurable on a line-by-line basis using the TERM.CONFIG utility. Both of these features are effective for all terminal types and the Bidirectional XON/XOFF feature is also usable on Async devices. There are some minor changes to the TERM.CONFIG utility to implement these new features. 4.1.3.1.1. TERM.CONFIG Update ___________ ______ These enhancements are defined in the TERM.CONFIG utility on the extended screen. (To access the extended screen, key in an 'X' at the 'ENTRIES CORRECT' prompt on the main screen.) The extended screen and the defaults are displayed below: 10/05/87 MAI BASIC FOUR, INC. 09:40 TERMINAL CONFIGURATION UTILITY ISDC UPDATE OPTION SHARED MEMORY CONTROLLER NUMBER : 0 SLAVE PRINTER : NO PRINTER TYPE : None LINE LENGTH : 80 CR ON LF : NO CHARACTER DELAY : NO DELAY LENGTH : 1 SUPRESS ECHO : NO XON/XOFF : YES MUX DEVICE : NO DELIMITER : I/O TRANSLATE : YES PRINT MESSAGES : YES INPUT TRANSPARENCY : NO OUTPUT TRANSPARENCY: NO RELEASE DETACH : NO ENTRIES CORRECT (Y/N) : The changes to this screen are: 1. XON/XOFF field allows a new option 'X' meaning ________ bi-directional XON/XOFF flow control. 2. RELEASE DETACH field has been added. This is a new _______ ______ TERM.CONFIG/Async Enhancements option. 3. I/O TRANSLATE field was called 'NO TRANSLATE'. This ___ _________ change makes this field much easier to understand. 4. PRINT MESSAGES field was called 'NO MESSAGES'. This _____ ________ change makes this field much easier to understand. 5. DELIMITER field does not display except on ASYNC _________ configurations. TERM.CONFIG DISPLAY SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg014 ___________ _______ The TERM.CONFIG detailed display has been modified to display the new configurable options. An example of the new display follows: 10/05/87 MAI BASIC FOUR, INC. 09:40 TERMINAL CONFIGURATION UTILITY DISPLAY OPTION Primary File Shared Memory Controller number 1 Type is ISDC 0: SPE W/Slv Ptr 9600 Baud, Odd Parity, 7 bits/char, 1.0 Stop Bits 80 Char Line, 0 mS Delay, B4 Printer, Translation, Echo, Print Banner 1: 4313 Terminal 9600 Baud, Odd Parity, 7 bits/char, 1.0 Stop Bits 80 Char Line, 0 mS Delay, Translation, Echo, XON/XOFF Bidirectional Print Banner, Drop DTR on Release 2: 4314 Terminal 19200 Baud, Odd Parity, 7 bits/char, 1.0 Stop Bits 80 Char Line, 0 mS Delay, Translation, Echo, XON/XOFF Flow Control Print Banner, Drop DTR on Release 3: 4105 w/Slv Ptr 9600 Baud, Odd Parity, 7 bits/char, 1.0 Stop Bits 80 Char Line, 5 Char Delay, IS Printer, Translation, Echo, XON/XOFF Flow Control, Print Banner 4: 4309 W/Slv Ptr 9600 Baud, Odd Parity, 7 bits/char, 1.0 Stop Bits 80 Char Line, 0 mS Delay, B4 Printer, Translation, Echo, XON/XOFF Bidirectional, Print Banner 'CR' to continue: Note the 'XON/XOFF Bidirectional' option set on lines 1 and 4 and the 'Drop DTR on Release' option set on lines 1 and 2. TERM.CONFIG/Async Enhancements 4.1.3.1.2. XON/XOFF Options ________ _______ The XON/XOFF field now prompts with the message: Enter XON/XOFF flow controls: Yes, No or X for bi-directional. When the answer to this prompt is 'No', then the system will provide no flow control using the XON and XOFF chatacters. If the system receives either of these characters, they will simply be passes through to any application program as data. If the answer to this prompt is 'Yes', then the driver system will recognize and act on receiving these. When the system receives an XOFF character, it will stop transmitting characters until such time as an XON character is received. When the answer to the XON/XOFF field is 'X', the system will ________ both recognize and act on receiving XON and XOFF characters and will transmit XON and XOFF characters to stop a remote device from transmitting. The system will recognize on input the XON and XOFF characters the same as if this option was specified as 'Yes'. Also when a device is sending data to the system and the internal 256-character type-ahead buffer is greater than 90% full, the system will transmit an XOFF character. When the type-ahead buffer gets less than 50% SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg015 full, the system will send an XON character to start the device transmitting again. The value of the XON character is $11$ and the value of the XOFF character is $13$. 4.1.3.1.3. Drop DTR Option ____ ___ ______ The prompt for the new RELEASE DETACH field is: _______ ______ Enter: 'Y' to drop DTR on terminal Release. When this option is specified as 'No' then the DTR signal from the controller will remain asserted (high) while the system is running. That is, it is set high when the system is booted and never is dropped. When this is specified as 'Yes' then the system will drop this signal when the terminal is released. The DTR signal will also be dropped when a terminal is closed that was opened from another terminal. This is also true for a slave printer opened from another terminal. 4.1.3.2. Additional TERM.CONFIG Changes __________ ___________ _______ I/O TRANSLATE Option ___ _________ ______ The new prompt for the I/O TRANSLATE field is: ___ _________ Enter: 'Y' for input and output translation. This inversion of the former option is much easier to understand. The former option was NO TRANSLATE. __ _________ PRINT MESSAGES OPTION _____ ________ ______ For the PRINT MESSAGES field the new prompt is: _____ ________ Enter: 'Y' to print welcome banner and messages. This inversion of the former option is much easier to understand. The former option was NO MESSAGES. __ ________ NOTE: After O.S. upgrade, the information previously stored in older terminal definition files will be interpreted in such a way as to preserve the user's previous setting. e.g., If a user had keyed in "NO" to NO MESSAGES, the new display will be __ ________ PRINT MESSAGES = "YES". _____ ________ 4.2. FILE SYSTEM ____ ______ 4.2.1. Increased Buffer Cache SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg016 _________ ______ _____ With the 9/8.6C release, the system will dynamically "tune" the number of data buffers allowed for data files. This will result in a performance enhancement when accessing high use data files by reducing disk I/O requirements. This improved performance will mainly be observable on systems with large configurations and high activity. Up to 10% performance improvement of overall system capacity may be expected, although results will be dependent upon applications. On previous releases, the data buffers for a file was a fixed number. The number of buffers is now dynamically changed according to the system resources available. The operating system will monitor file and memory usage and then determine the optimum number of file buffers allowed for each data file, respectively. This is a more efficient use of memory. Because the system needs to monitor usage for a certain period of time before adjustments to the buffers can be done, performance improvements will not be seen right away for a system new to 9/8.6C. As time goes on, the system will "tune" the data buffers, and system performance will improve. Each time the system is loaded, a new monitoring period begins. The system will dynamically save the new buffer parameters on disk, so an initial adjustment period is not required every time the system is loaded. The "tuning" of the data buffers is based on the number of times a file is OPENed at a given time. Therefore, files that don't have many concurrent OPEN's will not benefit greatly from this "tuning". 4.3. BROADCAST _________ A BROADCAST facility is now available on MPx systems, which provides the ability to send a message from one terminal to one or more other terminals. To achieve this, a new command at Command Language Interface (CLI) has been implemented. The MPx BROADCAST facility was formerly a part of the BOSS/VS ENHANCER PACKAGE. BROADCAST can be run interactively in command mode. You may also pass parameters to this program either from BASIC or command mode. To use this facility interactively, enter BROADCAST in command mode. The screen will display the prompt "Type Message:" along with the time, the terminal number, and the user's major.minor account. The message being sent should be entered here. The message can be up to 126 characters long, including the characters used for the time, terminal number, and account name of the sender. A carriage return will end the input of the message. The user will then be prompted with "Send Where:" Here specific terminal numbers or user account names are entered. Terminal numbers in a list are separated by commas. Masking is allowed for the user account names. The masking character is an asterisk (*). Some valid inputs to the "Send Where:" prompt are: "T1,T7" or "PAYROLL.JIM" or "ACCT.*". To send the SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg017 message to all logged on terminals, input "*.*" at this prompt. To send the message to all terminals, whether they are logged on or not, input *ALL*. When a carriage return is entered after specifying the terminals to receive the message, the message is immediately displayed on those terminals. In addition to the message, the time the message was sent, the terminal number from which the message was sent, and the user I.D. of the person sending the message will be displayed. Any message being sent will overlay a previous message up to the length of the new message. The message display begins on line 0. Screen positioning is also allowed (at the beginning of the message only). To position messages, enter the x,y coordinates as shown in the following example: Send What: (10,10) Test positioning Messages may also be cleared as follows: Send What: (10,10)*CLEAR* Parameters may be passed to BROADCAST from command mode as in the following example: BROADCAST "(10,10) This is a test","T5,T7" Parameters may be passed to BROADCAST from BASIC as in the following example: A$ = "BROADCAST '(10,10) Test','T5, T1'"; SYSTEM A$ BROADCAST resides in the .R6CXX.UNSPRTD. node. It may be copied to the .R6CXX.SYS. node, if access to this program by all users is desired. BROADCAST is an unsupported tool. 4.4. DIAGNOSTICS ___________ NOTE: To access all the software documented in this section, the prefix must be set to the .R6C11.INST. node. Please see the installation sections in this announcement for instructions on how to install DEMON and REMIDI. Further information on these diagnostics can be found in DOCWRITER, which can be accessed by entering !DOCWRITER in command mode. 4.4.1. REMIDI ______ NOTE: Running UPDATE.OS automatically updates the Load Sectors for the disk. However, running UPDATE.WCS does not. (The Load Sectors are displayed at the top of the OSINFO screen.) It is therefore necessary to run UPDATE.LD for REMIDI on 7xxx/8xxx systems on newly initialized systems packs, or whenever question marks ("?/?") appear in Load Sector 2 on the OSINFO screen. UPDATE.LD must ALWAYS be run to update Load ______ Sector 2 for REMIDI on 9xxx systems. 4.4.1.1. REMIDI on MPx 7000, 7100, and 8000 Series Systems SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg018 ______ __ ___ _____ _____ ___ ____ ______ _______ REMIDI version BV5C0101 includes all micro-diagnostics except those for the MPC and LAN controllers. It is loaded into WCS slot 2 and is used on MPx 7000, 7100, and 8000 Series Systems. REMIDI version BVM6A0803 contains micro-diagnostics for the MPC and LAN controllers. It is loaded into WCS slot 3 on all 7000/7100 Series Systems and on 8000 Series Systems with LAN controllers. This version of REMIDI is used on MPx 7000/7100 Series Systems for the MPC and LAN controllers, and on 8000 Series Systems for LAN controllers only. If a LAN controller is not present on an 8000 Series System, the BVM6A0803 version of REMIDI is not needed. The Load Directory controls which version of REMIDI will be executed. The UPDATE.LD utility is used to update the Load Directory. See the following section for instructions on running UPDATE.LD. 4.4.1.1.1. Updating the Load Directory for REMIDI ________ ___ ____ _________ ___ ______ Disregard this section if your 8000 Series System does not have a LAN controller. (In this case only REMIDI version BV5C0101 is used, and it is not necessary to update the Load Directory.) Since REMIDI is a WCS Image, two WCS slots, slot 2 and slot 3, will be required for the two REMIDI versions. The extra slot is provided by the DEMON WCS slot. Because DEMON and the BOSS/VS O.S. share the same WCS, Load Sector 3 should display 3/0 or 3/1, indicating that the WCS for DEMON is in either WCS slot 0 or WCS slot 1. This leaves WCS slot 3 free for REMIDI. Only one version of REMIDI will run at a time. The version that will run is dependent on how the Load Directory for REMIDI (Load Sector 2) is set up. The standard version, BV5C0101, which resides in WCS slot 2, has an OS/WCS of 0/2. The MPC/LAN version, BVM6A0803, which resides in WCS slot 3, has an OS/WCS of 0/3. Use UPDATE.LD to update the Load Directory to designate which version to run. To test the MPC and LAN controllers with REMIDI version BVM6A0803, execute UPDATE.LD, using the inputs below: NOTE: Lines preceded by an "*" require operator input. * Input in command mode !UPDATE.LD Update Load Directory Utility Disks (Unit number) on line : 0(16),1(17) Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 6.3.x.x R 6C*xx (date) B 6.1.x.x 1 1/1 | 6.3.x.x R 6C*xx (date) B 6.1.x.x 2 0/2 | B 5.x.x R 3 3/0 | 6.3.x.x DEMON (date) B 6.x.x R * New OS slot (0,1,3): 0 * New WCS slot (0..3): 3 * Load sector (0..3) : 2 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg019 In this case, UPDATE.LD will then display the new Load Directory as follows: Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 6.3.x.x R 6C*xx (date) B 6.1.x.x 1 1/1 | 6.3.x.x R 6C*xx (date) B 6.1.x.x 2 0/3 | B 5.x.x R 3 3/0 | 6.3.x.x DEMON (date) B 6.x.x R Notice the change in Load Sector 2. To go back to the standard REMIDI version, BV5C0101, which tests the CPU and main memory, use the following in UPDATE.LD: * New OS slot (0,1,3): 0 * New WCS slot (0..3): 2 * Load sector (0..3) : 2 In this case, UPDATE.LD will then display the new Load Directory as follows: Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 6.3.x.x R 6C*xx (date) B 6.1.x.x 1 1/1 | 6.3.x.x R 6C*xx (date) B 6.1.x.x 2 0/2 | B 5.x.x R 3 3/0 | 6.3.x.x DEMON (date) B 6.x.x R NOTE: The Load Directory should stay in the above setup in case the system CPU needs to be tested in a down condition. Always use Load Sector 2 for REMIDI. 4.4.1.2. REMIDI on MPx 9xxx Series Systems ______ __ ___ ____ ______ _______ REMIDI for MPx 9xxx Series Systems consists of two sections, AVA6C0003, which is loaded into WCS slot 2, and AVC6C0003, which is loaded into WCS slot 3. Unlike the REMIDI versions on 7xxx/8xxx systems, the 9xxx versions of REMIDI are not used independently. The version of REMIDI in WCS slot 2 calls the version of REMIDI in WCS slot 3. Load Sector 2 contains the OS/WCS pointers for REMIDI. 4.4.1.2.1. Updating the Load Directory for REMIDI ________ ___ ____ _________ ___ ______ The Load Directory must ALWAYS be updated for Load Sector 2 on ______ 9xxx systems after the installation of REMIDI with UPDATE.WCS, even if the OSINFO screen already shows the correct pointers for Load Sector 2 (0/2). Update the Load Directory by using the UPDATE.LD utility: NOTE: Lines preceded by an "*" require operator input. * Input in command mode !UPDATE.LD Update Load Directory Utility x.6xx.xx Disks (Unit number) on line : 0(16),1(17) Load OS/WCS | OS-Level Name WCS-Level SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg020 0 0/0 | 6.3.x.x R 6C*xx (date) x 6.x.x 1 1/1 | 6.3.x.x R 6C*xx (date) x 6.x.x 2 ?/? | R x 6.x.x 3 3/0 | 6.3.x.x DEMON (date) R x 6.x.x * New OS slot (0,1,3): 0 * New WCS slot (0..3): 2 * Load sector (0..3) : 2 UPDATE.LD will then display the new Load Directory as follows: Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 6.3.x.x R 6C*xx (date) x 6.x.x 1 1/1 | 6.3.x.x R 6C*xx (date) x 6.x.x 2 0/2 | R x 6.x.x 3 3/3 | 6.3.x.x DEMON (date) R x 6.x.x Notice the change in Load Sector 2. 4.4.2. Updating the Load Directory for DEMON ________ ___ ____ _________ ___ _____ Because REMIDI resides in WCS slot 3 on 7xxx and 9xxx systems and 8xxx systems with LAN, the Load Directory must point to another WCS slot for DEMON on these systems. The O.S. and DEMON share the same WCS code, therefore, Load Sector 3 should point to the WCS slot used by the O.S. Normally, this is set up by the operating system when DEMON is installed, providing that the correct answers are entered at the UPDATE.OS prompts during installation. If, for any reason, Load Sector 3 does not reflect OS/WCS as 3/0 or 3/1, you may use UPDATE.LD to change it, using the following inputs: NOTE: Lines preceded by an "*" require operator input: * Input in command mode !UPDATE.LD Update Load Directory Utility x.6xx.xx Disks (Unit number) on line : 0(16),1(17) Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 6.3.x.x R 6C*xx (date) x 6.x.x 1 1/1 | 6.3.x.x R 6C*xx (date) x 6.x.x 2 0/2 | R x 6.x.x 3 3/3 | 6.3.x.x DEMON (date) R x 6.x.x * New OS slot (0,1,3): 3 * New WCS slot (0..3): 0 (or 1) * Load sector (0..3) : 3 UPDATE.LD will then display the new Load Directory as follows: Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 6.3.x.x R 6C*xx (date) x 6.x.x 1 1/1 | 6.3.x.x R 6C*xx (date) x 6.x.x 2 0/2 | R x 6.x.x 3 3/0 | 6.3.x.x DEMON (date) R x 6.x.x Notice that Load Sector 3 is now pointing to WCS slot 0. 4.5. CONFIGURATIONS ______________ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg021 NOTE 1: The number of "High Activity Tasks" is approximate and largely dependent on the application. The relative relationship of the numbers between configurations is more important than the actual numbers themselves. NOTE 2: System configurations of MPx 9xxx Series Systems are based on the use of the LS-700 power supply mainframes. Original 810 systems do not support the LS-700 power supply and, therefore, will not meet all defined maximum configurations listed. NOTE 3: The following configurations are based on performance testing, and are subject to change as newer performance testing data becomes available. The configurations listed in the marketing announcements override those listed here. 4.5.1. Configurations for MPx 7000/7100/8000 Series Systems ______________ ___ ___ ______________ ______ _______ The maximum configuration for MPx 7000, 7100, and 8000 Series Systems, models 7030, 7130, and 8030, is as follows: 116 Devices - A combination of 8-ways, 16-ways, the 4 ports on the MCS PCBA, MDTs and HVDTs up to a total of 116 devices are supported. 3 CPU sets 10 ISDCs: 16-ways (7 maximum) and/or 8-ways 32 Ghost tasks 24 High speed videos (HVDT) 8 Disk drives 4 Parallel printers 2-8 Megabytes of memory (6 MB maximum on 7000/7100 systems) 2 Magnetic tape drives - MTR, MTS, and/or GCR (2 Maximum), and/or MCS (1 maximum) 4 Intelligent Multi-Line Controllers (IMLC) 8 DataWord II terminals 4 TBC lines 64 3270 terminals 8 X.25 lines 2 Auto-Call Units (ACU) 99 Serial printers 99 System printers (total serial and parallel not to exceed 99) 2 Buffered Magnetic Tape Controllers 27 High activity concurrent tasks 1 LAN controller NOTE: There is a maximum of 9 memory assembly boards in any combination of 1/2 Mb, 1 Mb, 2 Mb, 4 Mb and BMTCs (a maximum of 3 boards per chassis). Models 7010/7110/8010 and 7020/7120/8020 have the same configuration limits as models 7030 and 8030 above, with the following limitations: 7010/7110/8010 7020/7120/8020 1 CPU set 2 CPU sets 2-4 Mb memory 2-6 Mb memory 20 Devices 52 Devices 12 Concurrent tasks 20 Concurrent tasks (high activity) (high activity) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg022 19 System printers 51 System printers 4.5.2. Configurations for MPx 9000/9100/9400 Series Systems ______________ ___ ___ ______________ ______ _______ The maximum configuration for MPx 9000, 9100, and 9400 Series Systems, models 9020, 9120, and 9420 is as follows: 116 Devices - A combination of 8-ways, 16-ways, the 4 ports on the MCS PCBA, MDTs and HVDTs up to a total of 116 devices are supported. 2 CPU sets with Evaluation Stack and Rstack Cache 10 ISDCs: 16-ways (6 maximum) and/or 8-ways (10 maximum) 32 Ghost tasks 24 High speed videos (HVDT) 12 Disk drives on models 9020 and 9120, 8 disk drives on model 9420 (2.4 GB maximum), with no more than 8 14-inch fixed drives on any of the 3 models 8 Parallel printers 4-12 Megabytes of memory 2 Magnetic tape drives - MTR, MTS, and/or GCR (2 maximum), and/or MCS (1 maximum) 4 Intelligent Multi-Line Controllers (IMLC) 8 Dataword II terminals 4 TBC lines 64 3270 terminals 8 X.25 lines 2 Auto-Call Units (ACU) 99 Serial printers 99 System printers (total serial and parallel not to exceed 99) 4 DMA-I controllers on models 9020 and 9120, and 4 (total) DMA-I/DMA-II controllers on model 9420 * 2 Buffered Magnetic Tape Controllers 42 High activity concurrent tasks 1 LAN controller * It is recommended that, for maximum performance, no more than two disks be configured per DMA-II, and that the number of DMA-II's equal or exceed the number of CPU's. Models 9010, 9110, and 9410 have the same configuration limits as the 9020, 9120, and 9420 above, with the following exceptions: 1 CPU set with Evaluation Stack and Rstack Cache 68 Devices 10 ISDCs: 16-ways (4 maximum) and/or 8-ways (8 maximum) 67 Serial printers 75 System printers (total serial and parallel not to exceed 75) 27 High activity concurrent tasks 4.5.3. Configurations for MPx 9500/9600 Series Systems ______________ ___ ___ _________ ______ _______ The maximum configuration for MPx 9500 and 9600 Series Systems, models 9530 and 9630, is the same as the maximum configuration for the MPx 9000, 9100 and 9400 Series Systems, models 9020, 9120, and 9420 with the following exceptions: 3 CPU sets with Evaluation Stack SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg023 Rstack Cache Code Cache Data Cache 255 Devices 16 ISDCs: 16-ways (16 maximum) and/or 8-ways (16 maximum) 4-24 Maximum megabytes of main memory (see Hardware section for mandatory revision levels for main memory support above 12 megabytes) 16 Disk drives on model 9530, 12 disk drives on model 9630 (3.6 GB maximum), with no more than 8 14-inch fixed drives on either model 4 DMA-I controllers (may also include DMA-II controllers if system is an upgrade from a 9400) 73 High activity concurrent tasks Models 9510/9520 and 9610/9620 have the same configuration limits as models 9530/9630 with the following exceptions: 9510/9610 9520/9620 1 CPU set 2 CPU sets (same caches as the 9530) (same caches as the 9530) 10 ISDCs: 16-way (4 maximum) 10 ISDCs: 16-way (6 maximum) 8-way (8 maximum) 8-way (10 maximum) 84 Devices 132 Devices 83 Serial printers 53 Concurrent tasks 91 System printers (high activity) (total serial and parallel) 32 Concurrent tasks (high activity) 5. HARDWARE ________ NOTE: The 9.6C/8.6C operating systems do not necessarily require changes in hardware when upgrading from previous O.S. levels. The following information pertains to PCBA revisions that change/add functions to specific MPx Series Systems, and/or PCBA revisions that require certain operating systems levels. 5.1. MPX 7000, 7100, AND 8000 PCBA NOTES ___ _____ _____ ___ ____ ____ _____ 1) MCS 903374-001 PCBA Revision S adds another option to the switch setting of SW1. SW1 position 4 (SW1-4) is switch selectable between MPx 7000/7100/8000 (SW1-4, OPEN) Series Systems or MPx 9xxx Series Systems (SW1-4, CLOSED). If the MCS PCBA, at revision S, is switch selected for MPx 9xxx Series Systems and installed into an MPx 7000/7100/8000 Series System, it will not load. MCS 903374-002 PCBA-Revision V Revision V creates the -002 assembly. This assembly can be used on all MPx systems. 2) MDI 903361-001 PCBA Revision L prevents the MDI/ACS clocks from drifting and getting out of phase thus causing "INVOP" and "NILPTR" dumps. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg024 MDI 903408-001 PCBA Revision K prevents the MDI/ACS clocks from drifting and getting out of phase thus causing "INVOP" and "NILPTR" dumps. 3) ACS 903379-001/-002 PCBAs 7000 systems require revision Y or above, boot prom version 2.0.0.4 or higher (MPC support). Revision level Z cannot be used on 7000 systems, boot prom version 2.0.0.2 (No MPC support). 8000 systems on OS 8.4B or above require revision L, boot prom version 2.0.0.1 or higher. Revision levels V and W, boot prom version 2.0.0.3, is obsolete do not use. Tape load support from a BMTC requires revision T, boot prom version 2.0.0.2 or higher. Systems with 8-inch fixed drives require revision AA, boot prom version 2.0.0.5 or higher. ACS 903379-003 PCBA Revision AD creates the -003 assembly. This version of the ACS PCBA can also be used in 7000/8000 systems. 7100 systems require AD or higher and this revision level is also required for support of the 120 MB MTCS tape. Board versions -002 or -003 are mandatory for 3 CPU systems, MPx 7x/8xxx. 4) MPC 903500 PCBA If used in the MPx 7100 system, remove JMP3, if present, and set SW2-1 OFF and SW2-4 OFF. MPC 903546 PCBA If used in the MPx 7100 system, remove JMP3 if present and set SW2-1 OFF and SW2-2 OFF. 5) TDP Controller 903217-001 PCBA Revision K eliminates excessive sector number errors written to the ERROR LOG. TDP Controller 903453-001 PCBA New build TDP Controller, replaces TDP controller 903217-001. 6) NIMLC Controller 903381-001 PCBA This IMLC must be located to the right of the CPU set. Revision G provides correct line status for Data Set Ready (DSR) when no device is attached. Revision K is mandatory for all three (3) mainframe systems. NIMLC Controller 903381-002 Revision N creates this version of NIMLC for International use. It provides RS-232-C interface on Port B using standard 1488/1489 IC's to support cabling longer than 50 feet (provides higher input impedance interface required for use on various Wide-Area SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg025 Networks.) NIMLC Controller 903534-001 PCBA Provides the same interface as the 903381-002 PCBA on ports A and B. This NIMLC can be located on the left or right of the CPU. NIMLC Controller 903251-001 PCBA This NIMLC was used with the 810 system and will not operate on the MPx series systems. 7) Memory (1 MB, 2 MB, 4 MB) 903516-00x PCBA Memory 903516-001 PCBA is the 2MB version. Memory 903516-002 PCBA is the 4MB version. Memory 903516-003 PCBA is the 1MB version. 8) Terminator 903199 PCBA-Revision D Revision H creates the -004 assembly. Revision H can be used on all MPx systems. 5.2. MPX 9XXX SERIES SYSTEM PCBA NOTES ___ ____ ______ ______ ____ _____ NOTE: An asterisk (*) appears in front of revision levels that are mandatory for main memory support above 12 megabytes. 1) MCS 903374 PCBA Revision L and above is required for the operation of the MPx 9xxx system. Revision S adds another option to the switch setting of SW1. SW1 position 4 (SW1-4) is switch selectable between the addressing schemes of the MPx 7000/7100/8000 (SW1-4, OPEN) Series Systems or the MPx 9xxx Series Systems (SW1-4, CLOSED). If the MCS PCBA is switch selected for MPx 7000/7100/8000 systems and installed into an MPx 9xxx Series System, board addresses 32 thru 47 are reserved for the IMLC PCB only. If the MPx 9xxx scheme is used then there are no address restrictions. * Revision T is required for main memory support above 12 megabytes. Set SW1-4 to CLOSE for the 9xxx addressing scheme. * Revision V creates the -002 MCS. This revision is mandatory for support of the 16 MB memory board (P/N 903621) on 9xxx systems. It also can be used for main memory support above 12 MB. 2) AMS 903548 PCBA Revision F released the 4K boot proms version 3.1.0.4. This revision, or above, is required for operation. * Revision N creates the -002 PCBA and is required for main memory support above 12 megabytes. Revision P creates the -003 PCBA and is required for MPx 94xx systems. The -003 PCBA can be used in all MPx systems. 3) ESTK 903552 PCBA * Revision J, or above, is required for main memory SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg026 support above 12 megabytes. 4) IDC 903550-001 PCBA (with cache) IDC 903550-002 PCBA(without cache) Revision J addresses cache timing problems on selected systems. Do not replace the IDC PCBA on an error free system. 5) IDC64 903597-001 PCBA (with cache) IDC64 903597-002 PCBA (without cache) * IDC64 PCBA is required for support of main memory above 12 megabytes. Strap E6 to E7 must be out. 6) DMA-I 903554 PCBA * Revision G or above is required for support of main memory above 12 MB and the 600 LPM band printer, model 4220. Revision H is required if 300 MB 8-inch drives log excessive errors in the ERRORLOG. Revision N is required when used with the DMA-II. Revision R is required for use with the 16 MB memory board for full power fail recovery. 7) DMA-II (SCSI) 903599 PCBA Required for MPx 94xx SCSI disk drive support; requires 9.6C or later O.S. Revision K is required if there is also a DMA-I in the system. Revision L contains a fix for excessive soft errors logged in the ERRORLOG when both DMA-I's and DMA-II's are in the same system. 8) NIMLC 903381-001 PCBA This NIMLC must be located to the right of the CPU set. Revision K or above is mandatory for all MPx 9xxx systems. NIMLC 903381-002 PCBA Revison N creates this version of NIMLC for International use. It provides RS-232-C interface on Port B using standard 1488/1489 IC's to support cabling longer than 50 feet (provides the higher input impedance interface required for use on various Wide-Area Networks). NIMLC 903534 PCBA Provides the same interface as the 903381-002 PCBA on ports A and B. This NIMLC can be located on the left or right of the CPU set. NIMLC 903251 is OBSOLETE This NIMLC was used with the 810 system and will not operate on the MPx series systems. 9) Memory (1/2 MB and 1 MB) 903349 PCBA Revision V or above required for MPx 9xxx series systems. Not to be used with greater than 12 megabyte support; must use standard trade-in policies. 10) Memory (2 and 4 MB) 903516-00x PCBA Memory 903516-001 PCBA is the 2MB version. Revision E or above required for MPx 9xxx series systems. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg027 Memory 903516-002 PCBA is the 4MB version. * Revision J is required for support of main memory above 12 megabytes. Support of main memory above 12 megabytes is supported on MPx 9500 and 9600 Series Systems only. JMP 5 at location 1E = 1 to 2, and IC pad location 1A = 8 to 9. 11) Memory (4 MB, 8 MB, 16 MB) 903621-00x PCBA Memory 903621-001 is the 16 MB version. Memory 903621-003 is the 8 MB version. Memory 903621-004 is the 4 MB version. Requires MCS -002, Terminator -004, and DMA-I at revision R or above. 12) Terminator 903199 PCBA Revision H creates the -004 assembly, the -004 assembly is mandatory for support of the 16 MB memory board (P/N 903621). The following boards are NOT supported on MPx 9xxx Series Systems: 1) 7000/7100/8000 CPU set 2) TDP (Must be replaced by the BMTC for tape support) 3) MPC 5.3. PCBA'S FOR ALL SYSTEM TYPES ______ ___ ___ ______ _____ The following are PCBA'S common to all MPx systems without system model dependencies: 1) BMTC 903413 PCBA Revision T is required for full MTCS support. Revision U is required for support of the GCR 1/2" tape drive model 4405. It is possible for a hang condition to occur in SAVERESTORE, if the GCR tape drive does not have the following minimum revision levels: IF CARD 403923205 (Previously, the LARL was 403923202) CP CARD 403864305 (Previously, the LARL was 403864303) Revision Z allows the BMTC to operate on the Left or Right side of the CPU set. 2) Local Area Network Controller (LAN) 903595 PCBA With the release of the 9.6A/8.6A O.S., a new controller is supported: The Local Area Network controller. The LAN PCBA provides the ability to tie like systems together (MPx to MPx) in a local environment not more than 4000 feet apart. Each system requires one LAN controller and both systems must be on the same O.S. level. The LAN may be installed either to the Right of the CPU set(s) after the BMTC PCBA or to the Left of the MCS PCBA. Refer to MAGNET section in this document for further information on the Local Area Network. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg028 3) 16-Way Controller 903437 PCBA 16-Way controllers require the use of an I/O panel. The I/O panel is supplied with the purchase of the PCBA. 4) 8-Way Controller 903383 PCBA 5) HVDT Controller 903377 PCBA 6. INSTALLATION ____________ 6.1. INTRODUCTION ____________ IMPORTANT NOTE 1: IN PREPARATION FOR FUTURE MPx ENHANCEMENTS, POSITIONING OF THE O.S. AND WCS SLOTS HAS BEEN ADJUSTED SLIGHTLY. THEREFORE, PREVIOUS O.S./WCS LEVELS CANNOT RESIDE IN SLOTS ON THE SAME DISK WITH RELEASE LEVELS 9/8.6C. IMPORTANT NOTE 2: THE .SYSDATA.SECURITY.DATA FILE SHOULD BE SAVED BEFORE UPGRADING TO 9.6C/8.6C (FOR FALL BACK PURPOSES ONLY). FOR DETAILS, SEE THE SECTION ON THE NEW SECURITY.DATA FILE IN THIS ANNOUNCEMENT. For further information on BOSS/VS O.S. installation and TYPE 3 LOAD Special Functions, see the BOSS/VS INSTALLATION GUIDE, M 5138D. There are two ways to install 9.6C/8.6C: 1) Install a new system 2) Update a system If you are installing a new 7xxx, 8xxx, or 9xxx Series System, go to section 6.2. If you are upgrading a 8xxx Series System to 8.6C from level 8.4D or below, go to section 6.3. If you are upgrading a 7xxx or 8xxx Series System to 8.6C from level 8.4E or above, go to section 6.4. If you are upgrading a 9xxx Series System to 9.6C, go to section 6.5. If you are upgrading a 7xxx or 8xxx Series System to a 9xxx Series System, you must first run for a minimum of one week on O.S. 8.6A or above before the hardware upgrade. Beginning with release 9.6A/8.6A there is a change in the way terminals are enabled for user logon at system load time. Initial enabling of the TERMINALS group, which allows users to logon, is now under user control through the use of the Startup Command File. If the file does not exist, the TERMINALS group is enabled automatically. Refer to section 6.7 for further information on the startup command file and startup procedures for JOB MANAGER, MAGNET, and the SPOOLER. Since the operating system can be released on 1/2" (reel) or SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg029 1/4" (cartridge) tape, the word "tape" means either media form. 6.2. NEW INSTALLATION ___ ____________ 6.2.1. INSTALLING THE OPERATING SYSTEM __________ ___ _________ ______ Most new systems are shipped with the operating system already installed on the disk. This section is for those new systems that do not have the operating system installed. 6.2.1.1. Loading Slots 0 and 1 Using ALT LOAD _______ _____ _ ___ _ _____ ___ ____ NOTE: Positioning of the O.S./WCS slots has been adjusted slightly on O.S. levels 9/8.6C. Therefore, previous O.S. levels cannot reside in slots on the same disk with O.S. levels 9/8.6C. For this reason, ALT LOAD has been enhanced so that it will automatically load both slots 0 and 1. To perform an ALT LOAD from tape follow these steps: A) Mount the new release tape in the tape drive. (All front panel switches should be OFF if using tape drive 0. Switch 1 should be ON if using tape drive 1.) B) Press the "ALT LOAD" button on the front panel. First, a proprietary message will be displayed, and then the following load screen: ____________________________________________________________________ Load PROM Version: x.x.x.x SYSTEM SERIAL NUMBER : 000-00000 Load Drive n SERIAL NUMBER CREATOR: 000-00000 WCS 0 Version: x.x.x CONFIGURATION CREATOR: 000-00000 OS 0 Version: 6.3.x.x CPUs ID #s : n Memory (Mb) : n.0 Disk Drives : n BOSS/VS LOAD FROM TAPE Tape Drives : n Printers : n HVDTs : n IMLCs : n Serial Ports: n Date Format MM/DD/YY: BMTCs : n DATE = MM/DD/YY: LAN Cntrlrs : n TIME = HH:MM:SS: SYSTEM PREFIX: (family).Rxxxx.SYS.,.Rxxxx.INST. System Default Family: (family) File System Write Thru: T/F User Default Family : (family) Per-File Write Through: T/F Installation Name : (name) File System Security : T/F ____________________________________________________________________ Key in the current DATE and TIME at the above prompts. The screen will then display: ____________________________________________________________________ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg030 L O A D I N G . . . BOSS/VS Operating System Image Update Utility [version 6.3.x.x] OS/WCS information for drive n (nn): 0: ?????????????? ??????? | x x.x.x 1: ?????????????? ??.??.??.??? | ? ??.??.?? 2: -------------- -- -- -- --- | ????????? 3: ?????????????? ??????? | ????????? BOSS/VS Image File Name: (displays one of the following): OSN.AT060311000 (9xxx systems - 1/2-inch) OSN.AC060311000 (9400 systems - 1/4-inch) OSN.BT060311000 (8xxx systems) OSN.BC060311000 (7xxx systems) Target OS Slot (0/1/3) : '0' Target WCS Slot (0-3) : '0' NOTE: Even though only slot 0 is selected, both slots 0 and 1 will be updated. Target Drives (0/1/All/Quit): (choose drive) ____________________________________________________________________ C) The Image File Name will be displayed by the system. Enter '0' at the slot prompts to load O.S. and WCS slots 0 and 1. Enter '0', '1', or 'All' at the drive prompt to update the appropriate drives. The system will now display: ___________________________________________________________________ Now updating WCS slot # n Update in progress: nn% Now updating BOSS/VS Image (displays one of the following): OSN.AT060311000 (9xxx systems - 1/2-inch) OSN.AC060311000 (9400 systems - 1/4-inch) OSN.BT060311000 (8xxx systems) OSN.BC060311000 (7xxx systems) Update in progress: nn% Image slot directory n/n:n Updates all complete. D O N E - R E A D Y F O R N O R M A L D I S K L O A D ___________________________________________________________________ When O.S. and WCS slots 0 and 1 have been updated, reload the system by pressing the LOAD switch. 6.2.1.2. TYPE 3 LOAD (Special Functions) ____ _ ____ ________ __________ NOTE: If any disk has a 'MASTER' status, no update to the disk will be allowed. You must change the disk to a 'BACKUP' status in order to perform the TYPE 3 LOAD SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg031 functions. To do this, select OPTION 4 (CHANGE MASTER/BACKUP STATUS) from the TYPE 3 LOAD main menu. Be sure to change the disk back to a 'MASTER' status after the TYPE 3 LOAD functions are completed (if this status is desired). This MASTER/BACKUP status is simply a flag which makes it possible to write-protect a disk. It is not to be confused with the disk configuration (e.g., SYSTEM, DATA, BACKUP) specified in Option 1 (Change Volume Label Information) of INITIALIZATION OPTIONS (OPTION 2 on the TYPE 3 LOAD main menu). OPTION 2 - INITIALIZATION OPTIONS Option 1 must be done on all disks. Options 2 and 3 must be done for each family. Option 4 must be done on system disks only. 6.2.1.2.1. OPTION 1 (CHANGE VOLUME LABEL INFORMATION) ______ _ _______ ______ _____ ____________ All available disk drives will be displayed. An 'available' drive is any drive cabled to the system, whether enabled, disabled, powered ON or OFF. ENTER DRIVE NUMBER OF VOLUME LABEL TO CHANGE:__ (Enter volume label to change. The screen will change to display the information for only the drive whose volume label you choose. Selected drive must be online and ready.) SERIAL NUMBER _________ (Enter CR to accept current serial number.) DISK CONFIGURATION (1=SYSTEM, 2=DATA, 3=BACKUP) ____ (Enter the appropriate disk type.) SIZE OF DUMP AREA.....______ x 1024 BYTES (For system disks only, enter the size of the dump area displayed on the line below this prompt as the area needed for both main memory and shared memory controllers.) FILE SYSTEM SPACE ______ x 1000 SECTORS (Enter the number displayed at the bottom of the screen for this prompt. The display will appear as "CR=X" where X is the maximum space allowed.) UPDATE DISK VOLUME LABEL (Y/N) __ (Enter "Y" if above information is correct.) Repeat the steps in 6.2.1.2.1 for all remaining disk drives. 6.2.1.2.2. OPTION 2 (UPDATE FAMILY INFORMATION) ______ _ _______ ______ ____________ NOTE: Removable drives can only have one member per family. Fixed drives can be combined to create a larger capacity disk family. The disk information for all drives on the system is displayed SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg032 and the cursor is positioned at 'FAMILY BASE DRIVE NUMBER'. FAMILY BASE DRIVE NUMBER ___ FAMILY NAME ______ (CR for default family name.) DRIVE NUMBERS OF OTHER DISKS IN FAMILY? (TYPE SPACES FOR NO OTHER DRIVES) (Enter all other drive numbers for this family or spaces if none. The drives must be fixed media drives.) UPDATE DISK (Y/N)? Repeat the steps in 6.2.1.2.2 until all drives are identified in a family. 6.2.1.2.3. OPTION 3 (INITIALIZE FAMILY DIRECTORY) ______ _ ___________ ______ __________ This option displays all base drives on the system. FAMILY BASE DRIVE NUMBER ______ (Enter drive number to be initialized.) INITIALIZE FAMILY? (Y/N) __ Repeat the steps in 6.2.1.2.3 for all defined families. 6.2.1.2.4. OPTION 4 (CHANGE INSTALLATION PARAMETERS) ______ _ _______ ____________ ___________ Only SYSTEM disks will be displayed. DRIVE NUMBER _______ PRIMARY PREFIX __________________ (Enter (family).R6C11.SYS. (Family) is the family name where the operating system files will reside.) SECONDARY PREFIX _______________ (Enter (family).R6C11.SYS. (Family) is the family where the alternate operating system files will reside.) SYSTEM INSTALLATION NAME ________________ (Sets the default installation name for a specified system disk. Used only with MAGNET. Enter for default.) DEFAULT USER FAMILY NAME _____________ (Enter default user family.) SECURITY (E=ENABLED, D=DISABLED) ___ FILE SYSTEM WRITE THROUGH? (E=ENABLED, D=DISABLED) ___ WRITE THROUGH DEFAULT ON FILE CREATE (E=ENABLED, D=DISABLED):__ (This parameter specifies what the default write through will be on a file created through a BASIC SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg033 file create or through the CREATE utility.) UPDATE DISK WITH INSTALLATION PARAMETERS? (Y/N) __ Display: INSTALLATION PARAMETERS SUCCESSFULLY WRITTEN TO DISK. (CR) TO CONTINUE: Repeat the steps in 6.2.1.2.4 for any additional system disks. If you changed your disk from a 'MASTER' status to a 'BACKUP' status to do the TYPE 3 LOAD functions, change it back to a 'MASTER' status at this point. Reload the system by pressing the LOAD switch. 6.2.1.3. Restoring the O.S. _________ ___ ____ Enter SAVERESTORE in a TYPE 2 LOAD and choose OPTION 2 RESTORE FILES FROM TAPE. The screen appears as in figure 6-1. At the prompt for output device, enter a parallel printer so that a listing of the restore operation is produced. This listing can be used to make sure all files were restored correctly. On the next screen, at the prompt, "FILE SPECIFIERS", enter ".". Enter to all other questions. All system files will be restored to disk. Once all files are restored to disk, the message "AUTOMATIC COMPARE, CR TO CONTINUE" appears. This automatically rewinds the tape and begins the compare operation. This only occurs when the compare option is selected. When the compare is completed, enter a CTL-IV to return to the "SAVERESTORE" menu. Reload the system and enter a TYPE 1 LOAD. Figure 6-1. Restore Screen ______ ____ _______ ______ -------------------------------------------------------- RESTORE FILES TAPE SET.ID: DRIVE-NUM: REEL-NUM: PRIMARY PREFIX: (FAMILY).NODE. FILE TYPE (D/P/CR=ALL) COMPARE (CR=Y/N) DATE (MM/DD/YY) TIME (HH:MM) OUTPUT DEVICE (CR=VDT) DELETE EXISTING FILES (CR=Y) VERIFY (Y/CR=N) ENTRIES CORRECT (Y/N) -------------------------------------------------------- 6.2.2. INSTALLING THE CONFIGURATION RECORD __________ ___ _____________ ______ It is necessary to install a new configuration record when SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg034 installing a new system and when upgrading to 8.6C from 8.4 and 8.5 O.S. levels. Until the following procedure is completed, the system will have a minimum configuration. New systems normally already have a configuration record installed. If you have a new system, and you want to verify that the configuration record has been installed, run the CONFIG.MGR utility in a TYPE 1 LOAD. If the configuration record has already been installed, you may skip this section. Enter a TYPE 1 LOAD. Set your prefix to .SYSTEM.CONFIG. Using the SAVERESTORE utility, restore the new configuration record on tape onto your system. Execute the CONFIG.MGR utility. The CONFIG.MGR utility allows the user to update the system configuration record by installing a new configuration file. This utility displays the current and new configuration record. When "Y" is answered to the prompt "Install Configuration:", the new configuration is copied from the file ".SYSTEM.CONFIG.I(serial number)", to the special system area on disk. The new configuration takes effect at the next system load. For further details on the use of the CONFIG.MGR utility, see the 8.5D/9.5D Software Announcement #139, or the BOSS/VS Utility User Guide, M5102. The configuration record file name is derived from the system serial number by changing the leading "8" to an "I" and adding the prefix ".SYSTEM.CONFIG.". EXAMPLE: .SYSTEM.CONFIG.I1030114 for SSN 810-30114 This configuration record tape should be saved, in case reinstallation should become necessary. Before going to the next step, LOAD the system so the new ____ configuration record will take effect. If you do not load the system, you will have a minimum configuration and the system will be very slow. If you are installing a 7xxx/8xxx system, go to section 6.4.4 to load the remaining slots. If you are installing a 9xxx system, go to section 6.5.6 to load the remaining slots. 6.3. UPGRADING TO 8.6C FROM RELEASE LEVELS 8.4D AND BELOW _________ __ ____ ____ _______ ______ ____ ___ _____ 6.3.1. INTRODUCTION ____________ NOTE: This section contains references to the FILESIZE, NFSCONVERT, and DISKANALYZER utilities. Further information on these utilities and their use during file conversion can be found in the following sources: - BOSS/VS FILE CONVERSION GUIDE, M5185 - BOSS/VS UTILITY USER GUIDE, M5102 - Software Announcements for release levels 8.4E and 8.5A/B/C/D - HELP SCREENS accessed by keying in UTILITYNAME.HELP in SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg035 command mode Since release levels 8.4E and above contain new file formats and a new file system, conversion of files is required to make files compatible with the new file system, if you are upgrading from a software release level of 8.4D or below. The file conversion can be done in two ways: A) From tape to disk B) From disk to disk Which method used depends on the configuration of the system. The disk to disk method is preferable for a system with removable disks. The disk to disk method involves upgrading the system disk with the new O.S. Then the system disk can be used to convert other disks by using the NFSCONVERT utility to convert one file from one disk to another. If the disk to disk method is used on fixed disks, any user files must be copied from the fixed system disk to another disk or to tape for conversion. This is because the system disk must be initialized and updated to the new O.S. to do the conversion. To do a tape conversion, a save and restore is performed with the SAVERESTORE utility in the normal manner. The conversion process is invisible to the user with the exception of the following status message that is displayed during conversion: "Now converting to NFS format...." The tape conversion requires about 4 minutes per megabyte of data. The installation procedure is broken into two parts: A) Preliminary evaluation B) Operating System upgrade and file conversion The preliminary evaluation is required to ensure that proper hardware and file preparation is done. An O.S. upgrade from releases of 8.4D and below entails loading of the 8.6C O.S. and converting files to their new format. The conversion process, in large configurations, will take more than one day. At the end of this section is an upgrade and conversion checklist that should be used to track progress through the upgrade procedure. 6.3.2. PRELIMINARY EVALUATION ___________ __________ The preliminary section deals with revision levels and file preparation. 6.3.2.1. Hardware Evaluation ________ __________ All hardware must be checked for proper operation. All boards SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg036 must be at proper revision levels (see the HARDWARE section in this announcement.) Ensure that all tape units are operating correctly. Also, make sure that all memory boards are set for 160 ns operation. Also note that any 3 CE systems must have a revision K or higher on the IMLC board (if present). 6.3.2.2. File Preparation ____ ___________ Obtain a directory listing with partial attributes for each family in the system. This listing will help you to find files, if any, that need repair before conversion. Next, using DISKANALYZER, select the option "VALIDATE ALL FILES" to determine which files need repair. Files which have the following attributes MUST be repaired before they are saved to tape: A) Files which lack integrity. B) Files which have lost space. C) Non-serial files in which records used is greater than records defined. D) Files that have invalid format. These files can be located in several ways: A) Scan the directory listing noting any files flagged. B) Use the report generated by the DISKANALYZER "VALIDATE ALL FILES" option. C) Use the utility FINDLOSTSPACE (8.4C/D only). All of the above methods should be used to find files that lack integrity and that have lost space. However, the directory listing must be scanned to find files that have a greater number of records used then defined as maximum records. This is a very important step. Any file possessing any of these attributes WILL NOT convert properly. They have to be repaired on a previous release before conversion. Any EDITOR recovery files must be recovered or deleted before conversion. The recovery files are identified by the node ED.REC. After the node, there will be a series of digits. These files can be found by scanning the directory listing. These files must be recovered by using EDIT.RECOVER or deleted by using the DELETE utility. ***************************************** * * * ALL FILES MUST BE FREE FROM LACK OF * * INTEGRITY, LOST SPACE, AND MAX * * RECORDS GREATER THAN DEFINED RECORDS. * * FILES WILL NOT BE CONVERTED IF THEY * * POSSESS ANY ONE OF THESE ATTRIBUTES. * * * ***************************************** 6.3.2.3. New File System Space Requirements SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg037 ___ ____ ______ _____ ____________ The space required for files under the new file system are about the same as under 8.4D/C/B/A levels. However, it is recommended that a listing be obtained which displays the files and their new sizes. On the 8.4D release, the program FILESIZE is used to produce this listing. The program FILESIZE will display the file size under the new file system for each file in a given family. It will also display the total number of sectors required by the entire family under the new file system. 6.3.2.4. Saving Files to Tape ______ _____ __ ____ User files and the .SYSDATA. node must now be backed up to tape. It is STRONGLY recommended that these files be saved to tape even if disk to disk conversion is being used. This will allow recovery of files in case of problems with the disk to disk conversion. It is necessary to save the .SYSDATA. node to preserve all system parameters. This node must be restored on the new file system along with the user files. It is essential that the .SYSDATA.SECURITY.DATA file be backed up before upgrading to 8.6C and saved for a period of time on tape. This SECURITY.DATA file will go through a conversion during the upgrade, and the converted file cannot be used on previous O.S. levels. The old version of SECURITY.DATA should be kept in the event of an O.S. downgrade. The files are saved using the standard tape utility, SAVERESTORE. When saving files to tape, send the output from the save process to the printer. These will provide a record of backup for each file. Also it is recommended that all tapes be compared to the files on the disk. When using the tape or disk conversion, the conversion requires temporary disk space to sort keyed (direct and sort) files. The space required varies with the number of records and the size of the key. To insure proper space is available, the following steps should be observed: A) Do not restore the user default family until last. B) Convert large keyed files first. Step A insures that the default user disk has a large amount of free space since this is where the tape and disk conversion utility defines the temporary files. Step B allows the files that require the most amount of temporary space to be converted first. To convert large keyed files first, they must be saved to tape first. The large keyed files can be identified by scanning the directory listing obtained in section 6.3.2.2. If using disk to disk conversion, the NFSCONVERT utility allows you to convert keyed files first. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg038 6.3.3. OPERATING SYSTEM UPDATE and FILE CONVERSION _________ ______ ______ ___ ____ __________ 6.3.3.1. Installing the O.S. __________ ___ ____ 6.3.3.1.1. Loading Slots 0 and 1 Using ALT LOAD _______ _____ _ ___ _ _____ ___ ____ NOTE: Positioning of the O.S./WCS slots has been adjusted slightly on O.S. levels 9/8.6C. Therefore, previous O.S. levels cannot reside in slots on the same disk with O.S. levels 9/8.6C. For this reason, ALT LOAD has been enhanced so that it will automatically load both slots 0 and 1. To perform an ALT LOAD from tape follow these steps: A) Mount the new release tape in the tape drive. (All front panel switches should be OFF if using tape drive 0. Switch 1 should be ON if using tape drive 1.) B) Press the "ALT LOAD" button on the front panel. First, a proprietary message will be displayed, and then the following load screen: ____________________________________________________________________ Load PROM Version: x.x.x.x SYSTEM SERIAL NUMBER : 000-00000 Load Drive n SERIAL NUMBER CREATOR: 000-00000 WCS 0 Version: x.x.x CONFIGURATION CREATOR: 000-00000 OS 0 Version: 6.3.x.x CPUs ID #s : n Memory (Mb) : n.0 Disk Drives : n BOSS/VS LOAD FROM TAPE Tape Drives : n Printers : n HVDTs : n IMLCs : n Serial Ports: n Date Format MM/DD/YY: BMTCs : n DATE = MM/DD/YY: LAN Cntrlrs : n TIME = HH:MM:SS: SYSTEM PREFIX: (family).Rxxxx.SYS.,.Rxxxx.INST. System Default Family: (family) File System Write Thru: T/F User Default Family : (family) Per-File Write Through: T/F Installation Name : (name) File System Security : T/F ____________________________________________________________________ Key in the current DATE and TIME at the above prompts. The screen will then display: ____________________________________________________________________ L O A D I N G . . . BOSS/VS Operating System Image Update Utility [version 6.3.x.x] OS/WCS information for drive n (nn): 0: ?????????????? ??????? | x x.x.x SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg039 1: ?????????????? ??.??.??.??? | ? ??.??.?? 2: -------------- -- -- -- --- | ????????? 3: ?????????????? ??????? | ????????? BOSS/VS Image File Name: (displays one of the following): OSN.AT060311000 (9xxx systems - 1/2-inch) OSN.AC060311000 (9400 systems - 1/4-inch) OSN.BT060311000 (8xxx systems) OSN.BC060311000 (7xxx systems) Target OS Slot (0/1/3) : '0' Target WCS Slot (0-3) : '0' NOTE: Even though only slot 0 is selected, both slots 0 and 1 will be updated. Target Drives (0/1/All/Quit): (choose drive) ____________________________________________________________________ C) The Image File Name will be displayed by the system. Enter '0' at the slot prompts to load O.S. and WCS slots 0 and 1. Enter '0', '1', or 'All' at the drive prompt to update the appropriate drives. The system will now display: ___________________________________________________________________ Now updating WCS slot # n Update in progress: nn% Now updating BOSS/VS Image (displays one of the following): OSN.AT060311000 (9xxx systems - 1/2-inch) OSN.AC060311000 (9400 systems - 1/4-inch) OSN.BT060311000 (8xxx systems) OSN.BC060311000 (7xxx systems) Update in progress: nn% Image slot directory n/n:n Updates all complete. D O N E - R E A D Y F O R N O R M A L D I S K L O A D ___________________________________________________________________ When O.S. and WCS slots 0 and 1 have been updated, reload the system by pressing the LOAD switch. 6.3.3.1.2. TYPE 3 LOAD (SPECIAL FUNCTIONS) ____ _ ____ ________ __________ NOTE 1: When using NFSCONVERT, the following steps should only be performed on the destination disk (which will be in new File System format). NOTE 2: If any disk has a 'MASTER' status, no update to the disk will be allowed. You must change the disk to a 'BACKUP' status in order to perform the TYPE 3 LOAD functions. To do this, select OPTION 4 (CHANGE MASTER/BACKUP STATUS) from the TYPE 3 LOAD main menu. Be sure to change the disk back to a SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg040 'MASTER' status after the TYPE 3 LOAD functions are completed (if this status is desired). This MASTER/BACKUP status is simply a flag which makes it possible to write-protect a disk. It is not to be confused with the disk configuration (e.g., SYSTEM, DATA, BACKUP) specified in Option 1 (Change Volume Label Information) of INITIALIZATION OPTIONS (OPTION 2 on the TYPE 3 LOAD main menu). OPTION 2 - INITIALIZATION OPTIONS INITIALIZATION OPTIONS 1-4 must be done to insure proper operation. Option 1 must be done for all disks. Option 2 must be done for the system disk. Options 3 and 4 must be done for all families. 6.3.3.1.2.1. OPTION 1 (CHANGE VOLUME LABEL INFORMATION) ______ _ _______ ______ _____ ____________ All available disk drives will be displayed. An 'available' drive is any drive cabled to the system, whether enabled, disabled, powered ON or OFF. ENTER DRIVE NUMBER OF VOLUME LABEL TO CHANGE:__ (Enter volume label to change. The screen will change to display the information for only the drive whose volume label you choose.) SERIAL NUMBER _________ (Enter CR to accept current serial number.) DISK CONFIGURATION (1=SYSTEM, 2=DATA, 3=BACKUP) ____ (Enter the appropriate disk type.) SIZE OF DUMP AREA.....______ x 1024 BYTES (For system disks only, enter the size of the dump area given by the line below this prompt as the area needed for both main memory and shared memory controllers.) FILE SYSTEM SPACE ______ x 1000 SECTORS (Enter the number displayed at the bottom of the screen for this prompt. The display will appear as "CR=X" where X is the maximum space allowed.) UPDATE DISK VOLUME LABEL (Y/N) __ (Enter "Y" if above information is correct.) 6.3.3.1.2.2. OPTION 2 (UPDATE FAMILY INFORMATION) ______ _ _______ ______ ____________ The disk information for all drives on the system is displayed and the cursor is positioned at 'FAMILY BASE DRIVE NUMBER'. FAMILY BASE DRIVE NUMBER ___ FAMILY NAME ______ (CR for default family name.) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg041 DRIVE NUMBERS OF OTHER DISKS IN FAMILY? (TYPE SPACES FOR NO OTHER DRIVES) (Enter all other drive numbers for this family or spaces if none. The drives must be fixed media drives and in new file system format.) UPDATE DISK (Y/N)? 6.3.3.1.2.3. OPTION 3 (INITIALIZE FAMILY DIRECTORY) ______ _ ___________ ______ __________ This option displays all root drives on the system. FAMILY BASE DRIVE NUMBER ______ (Enter drive number to be initialized.) INITIALIZE FAMILY? (Y/N) __ 6.3.3.1.2.4. OPTION 4 (CHANGE INSTALLATION PARAMETERS) ______ _ _______ ____________ ___________ Only system disks will be displayed. DRIVE NUMBER _______ PRIMARY PREFIX __________________ (Enter (family).R6C11.SYS. (Family) is the family where the operating system files will reside.) SECONDARY PREFIX _______________ (Enter (family).R6C11.SYS. (Family) is the family where the alternate operating system files will reside.) SYSTEM INSTALLATION NAME ________________ (Sets the default installation name for a specified system disk.) DEFAULT USER FAMILY NAME _____________ (Enter default user family.) SECURITY (E=ENABLED, D=DISABLED) ___ FILE SYSTEM WRITE THROUGH? (E=ENABLED, D=DISABLED) ___ (For conversion purposes, set this option to 'D' for DISABLED. This will speed up the conversion process and can be changed later if needed.) WRITE THROUGH DEFAULT ON FILE CREATE (E=ENABLED, D=DISABLED):__ (This parameter specifies what the default write through will be on a file created through a BASIC file create or through the CREATE utility.) UPDATE DISK WITH INSTALLATION PARAMETERS? (Y/N) __ Display: INSTALLATION PARAMETERS SUCCESSFULLY WRITTEN TO DISK. (CR) TO CONTINUE: Reload the system by pressing the LOAD switch. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg042 6.3.3.1.3. Restoring the O.S. _________ ___ ____ Enter SAVERESTORE in a TYPE II load and choose option #2 "RESTORE FILES FROM TAPE". The screen appears as in figure 6-2. Figure 6-2. Restore Screen ______ ____ _______ ______ -------------------------------------------------------- RESTORE FILES TAPE SET.ID: DRIVE-NUM: REEL-NUM: PRIMARY PREFIX: (FAMILY).NODE. FILETYPE (D/P/CR=ALL) COMPARE (CR=Y/N) DATE (MM/DD/YY) TIME (HH:MM) OUTPUT DEVICE (CR=VDT) DELETE EXISTING FILES (CR=Y) VERIFY (Y/CR=N) ENTRIES CORRECT (Y/N) -------------------------------------------------------- At each prompt, enter a . At the prompt, "FILE SPECIFIERS", enter ".". Then enter twice. This will restore all the files on the release tape to disk. Please note that once all files are restored to disk, the message "AUTOMATIC COMPARE, CR TO CONTINUE" appears. This automatically rewinds the tape and begins the compare operation. This only occurs when the compare option is selected. When the compare is completed, enter a CTL-IV to return to the "SAVERESTORE" menu. 6.3.3.2. INSTALLING THE CONFIGURATION RECORD __________ ___ _____________ ______ It is necessary to install a new configuration record when installing a new system and when upgrading to 8.6C from 8.4 and 8.5 O.S. levels. Until the following procedure is completed, the system will have a minimum configuration. Enter a TYPE 1 LOAD. Set your prefix to .SYSTEM.CONFIG. Before you load the new configuration record, rename the current configuration record on your system, using the RENAME utility, to temporarily preserve it for fall back purposes. (e.g. Add "OLD" in front of the name.) Using the SAVERESTORE utility, restore the new configuration record on tape onto your system. Execute the CONFIG.MGR utility. The CONFIG.MGR utility allows SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg043 the user to update the system configuration record by installing a new configuration file. This utility displays the current and new configuration record. When "Y" is answered to the prompt "Install Configuration:", the new configuration is copied from the file ".SYSTEM.CONFIG.I(serial number)", to the special system area on disk. The new configuration takes effect at the next system load. For further details on the use of the CONFIG.MGR utility, see the 9.5D/8.5D Software Announcement #139, or the BOSS/VS UTILITY USER GUIDE, M5102. The configuration record file name is derived from the system serial number by changing the leading "8" to an "I" and adding the prefix ".SYSTEM.CONFIG.". EXAMPLE: .SYSTEM.CONFIG.I1030114 for SSN 810-30114 This configuration record tape should be saved, in case reinstallation should become necessary. Before going to the next step, LOAD the system so the new ____ configuration record will take affect. If you do not load the Upgrading to 8.6C from Release Levels 8.4D and Below system, you will have a minimum configuration and the system will be very slow. 6.3.3.3. CONVERTING FILES __________ _____ If doing tape to disk conversion see section 6.3.3.3.1. If doing disk to disk conversion see section 6.3.3.3.2. 6.3.3.3.1. Tape to Disk Conversion ____ __ ____ __________ Mount the first tape to restore, enter the SAVERESTORE utility, and select option #2. A screen as in figure 6-2 will appear. Answer all prompts as in the figure. Make sure that you direct the output to a printer. This will provide you with a "history" of the restore operation. Each file is converted to the new file format as it is restored. The conversion to the new file format will be entirely invisible except for a pause at the completion of restoring a file. This pause, which can last a few seconds to a few hours depending on file size, indicates the file is being converted to the new file format. Occasionally the message "...CONVERTING FILE TO NFS..." will appear as a visual indicator of file conversion. System files from the previous release need not be restored. However, to preserve all system parameters, the .SYSDATA. node must be restored from the backup tapes. Tapes made on a releases of 8.4D and below cannot be compared when restored to the new file system. After all files have been restored, reload the system so the SECURITY.DATA file will be converted to the new 9/8.6C format and the terminal definition files will take effect. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg044 Now go to section 6.3.3.3.3. 6.3.3.3.2. Disk to Disk Conversion ____ __ ____ __________ The utility NFSCONVERT is used to convert files from the old format to the new file format. The destination disk must be in new file system format as described in section 6.3.3.1.2. The source disk must be in old file system format. When using disk to disk conversion, only one family may be converted per terminal. You cannot start NFSCONVERT on two terminals converting different parts of the same family. You can convert different families at the same time. As in the tape to disk conversion, the .SYSDATA. node must be converted to preserve system parameters and configurations. 6.3.3.3.3. Check Files _____ _____ Once all files have been converted, the DISKANALYZER "VALIDATE ALL FILES" option should be used on each family. DISKANALYZER can be used in a TYPE II load or a TYPE I load. Once all files have been validated, enter a TYPE I load, (if you have not already done so). 6.3.4. UPDATING THE TERMINAL CONFIGURATION FILE ________ ___ ________ _____________ ____ The terminal configuration file must be updated to the new file system format. This update will allow all other devices to become accessible. The file is updated by entering TERM.CONFIG and choosing the update option. Enter PRIMARY as the file to change. Enter an existing ISDC and display one of the ISDC ports. Enter a MB-IV to exit the update without changing anything. The utility will say that the file has been modified and do you want to save it. Respond with YES. Now reload the system to allow the devices to become active. Now go to section 6.4.4 to complete the last step of the installation. 7xxx/8xxx UPGRADE AND CONVERSION CHECKLIST _________ _______ ___ __________ _________ 1) Hardware levels => section 5 2) Validate files => section 6.3.2.2 A) DISKANALYZER option "VALIDATE ALL FILES" B) DIR listings C) FINDLOSTSPACE Utility D) Delete unwanted EDITOR,SPOOL, and TEMP files 3) New file sizes => section 6.3.2.3 A) FILESIZE utility 4) Save files to tape => section 6.3.2.4 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg045 A) Large keyed files first 5) Update operating system => section 6.3.3.1 A) ALT-LOAD B) Options 1-4 C) Restore operating system files 6) File conversion A) Tape-to-disk => section 6.3.3.3.1 B) Disk-to-disk => section 6.3.3.3.2 7) Check file integrity => section 6.3.3.3.3 8) Complete installation A) Update terminal configuration file => section 6.3.4 B) Update slots 2 and 3 => section 6.4.4 6.4. UPGRADING TO 8.6C FROM RELEASE LEVELS 8.4E AND ABOVE _________ __ ____ ____ _______ ______ ____ ___ _____ If you are upgrading to 9.6C, go to section 6.5. 6.4.1. SAVING FILES TO TAPE ______ _____ __ ____ Current files must first be backed up to tape, using the standard tape utility, SAVERESTORE. When saving files to tape, send the output from the save process to the printer. These will provide a record of backup for each file. Also it is recommended that all files on tape be compared to the files on the disk. NOTE: It is essential that the .SYSDATA.SECURITY.DATA file be backed up before upgrading to 8.6C. This SECURITY.DATA file will go through a conversion during the upgrade, and the converted file cannot be used on previous O.S. levels. The old version of SECURITY.DATA should be saved in case an O.S. downgrade is ever needed. 6.4.2. OPERATING SYSTEM UPDATE _________ ______ ______ 6.4.2.1. Loading Slots 0 and 1 Using ALT LOAD _______ _____ _ ___ _ _____ ___ ____ NOTE: Positioning of the O.S./WCS slots has been adjusted slightly on O.S. levels 9/8.6C. Therefore, previous O.S. levels cannot reside in slots on the same disk with O.S. levels 9/8.6C. For this reason, ALT LOAD has been enhanced so that it will automatically load both slots 0 and 1. To perform an ALT LOAD from tape follow these steps: A) Mount the new release tape in the tape drive. (All front panel switches should be OFF if using tape drive 0. Switch 1 should be ON if using tape drive 1.) B) Press the "ALT LOAD" button on the front panel. First, a SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg046 proprietary message will be displayed, and then the following load screen: ____________________________________________________________________ Load PROM Version: x.x.x.x SYSTEM SERIAL NUMBER : 000-00000 Load Drive n SERIAL NUMBER CREATOR: 000-00000 WCS 0 Version: x.x.x CONFIGURATION CREATOR: 000-00000 OS 0 Version: 6.3.x.x CPUs ID #s : n Memory (Mb) : n.0 Disk Drives : n BOSS/VS LOAD FROM TAPE Tape Drives : n Printers : n HVDTs : n IMLCs : n Serial Ports: n Date Format MM/DD/YY: BMTCs : n DATE = MM/DD/YY: LAN Cntrlrs : n TIME = HH:MM:SS: SYSTEM PREFIX: (family).Rxxxx.SYS.,.Rxxxx.INST. System Default Family: (family) File System Write Thru: T/F User Default Family : (family) Per-File Write Through: T/F Installation Name : (name) File System Security : T/F ____________________________________________________________________ Key in the current DATE and TIME at the above prompts. The screen will then display: ____________________________________________________________________ L O A D I N G . . . BOSS/VS Operating System Image Update Utility [version 6.3.x.x] OS/WCS information for drive n (nn): 0: ?????????????? ??????? | x x.x.x 1: ?????????????? ??.??.??.??? | ? ??.??.?? 2: -------------- -- -- -- --- | ????????? 3: ?????????????? ??????? | ????????? BOSS/VS Image File Name: (displays one of the following): OSN.AT060311000 (9xxx systems - 1/2-inch) OSN.AC060311000 (9400 systems - 1/4-inch) OSN.BT060311000 (8xxx systems) OSN.BC060311000 (7xxx systems) Target OS Slot (0/1/3) : '0' Target WCS Slot (0-3) : '0' NOTE: Even though only slot 0 is selected, both slots 0 and 1 will be updated. Target Drives (0/1/All/Quit): (choose drive) ____________________________________________________________________ C) The Image File Name will be displayed by the system. Enter '0' at the slot prompts to load O.S. and WCS slots 0 and 1. Enter '0', '1', or 'All' at the drive prompt to update SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg047 the appropriate drives. The system will now display: ___________________________________________________________________ Now updating WCS slot # n Update in progress: nn% Now updating BOSS/VS Image (displays one of the following): OSN.AT060311000 (9xxx systems - 1/2-inch) OSN.AC060311000 (9400 systems - 1/4-inch) OSN.BT060311000 (8xxx systems) OSN.BC060311000 (7xxx systems) Update in progress: nn% Image slot directory n/n:n Updates all complete. D O N E - R E A D Y F O R N O R M A L D I S K L O A D ___________________________________________________________________ When O.S. and WCS slots 0 and 1 have been updated, reload the system by pressing the LOAD switch. 6.4.2.2. Changing Installation Parameters ________ ____________ __________ NOTE: If any disk has a 'MASTER' status, no update to the disk will be allowed. You must change the disk to a 'BACKUP' status in order to perform the TYPE 3 LOAD functions. To do this, select OPTION 4 (CHANGE MASTER/BACKUP STATUS) from the TYPE 3 LOAD main menu. Be sure to change the disk back to a 'MASTER' status after the TYPE 3 LOAD functions are completed (if this status is desired). This MASTER/BACKUP status is simply a flag which makes it possible to write-protect a disk. It is not to be confused with the disk configuration (e.g., SYSTEM, DATA, BACKUP) specified in Option 1 (Change Volume Label Information) of INITIALIZATION OPTIONS (OPTION 2 on the TYPE 3 LOAD main menu). Enter a TYPE 3 LOAD (SPECIAL FUNCTIONS) and select OPTION 2 (INITIALIZATION OPTIONS). OPTION 2 - INITIALIZATION OPTIONS Option 4 - CHANGE INSTALLATION PARAMETERS Only system disks will be displayed. DRIVE NUMBER _______ PRIMARY PREFIX _______________________ (Enter (family).R6C11.SYS. (Family) is the family where the operating system files reside.) SECONDARY PREFIX _____________________ (Enter (family).R6C11.SYS. (Family) is the family SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg048 where the alternate operating system files reside.) SYSTEM INSTALLATION NAME _________________________ (Sets the default installation name for a specified system disk.) DEFAULT USER FAMILY NAME ________ (Enter default user family.) SECURITY (E=ENABLED, D=DISABLED) ___ FILE SYSTEM WRITE THROUGH? (E=ENABLED, D=DISABLED) ___ WRITE THROUGH DEFAULT ON FILE CREATE (E=ENABLED, D=DISABLED) __ (This parameter specifies what the default write through will be on a file created through a BASIC file create or through the CREATE utility.) UPDATE DISK WITH INSTALLATION PARAMETERS? (Y/N)__ Display: INSTALLATION PARAMETERS SUCCESSFULLY WRITTEN TO DISK (CR) TO CONTINUE: Reload the system by pressing the LOAD switch. 6.4.2.3. Restoring the O.S. _________ ___ ____ Enter SAVERESTORE in a TYPE 2 LOAD and choose OPTION 2 RESTORE FILES FROM TAPE. The screen appears as in figure 6-2. Figure 6-3. Restore Screen ______ ____ _______ ______ -------------------------------------------------------- RESTORE FILES TAPE SET.ID: DRIVE-NUM: REEL-NUM: PRIMARY PREFIX: (FAMILY).NODE. FILE TYPE (D/P/CR=ALL) COMPARE (CR=Y/N) DATE (MM/DD/YY) TIME (HH:MM) OUTPUT DEVICE (CR=VDT) DELETE EXISTING FILES (CR=Y) VERIFY (Y/CR=N) ENTRIES CORRECT (Y/N) -------------------------------------------------------- At each prompt, enter a . At the prompt, "FILE SPECIFIERS", enter ".". Then enter twice. This will restore all files on the release tape to disk. Please note that once all files are restored to disk, the message "AUTOMATIC COMPARE, CR TO CONTINUE" appears. This automatically rewinds the tape and begins the compare SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg049 operation. This only occurs when the compare option is selected. When the compare is completed, enter a CTL-IV to return to the "SAVERESTORE" menu. 6.4.3. INSTALLING THE CONFIGURATION RECORD __________ ___ _____________ ______ It is necessary to install a new configuration record when installing a new system and when upgrading to 8.6C from 8.4 and 8.5 O.S. levels. Until the following procedure is completed, the system will have a minimum configuration. Enter a TYPE 1 LOAD. Set your prefix to .SYSTEM.CONFIG. Before you load the new configuration record, rename the current configuration record on your system, using the RENAME utility, to temporarily preserve it for fall back purposes. (e.g. Add "OLD" in front of the name.) Using the SAVERESTORE utility, restore the new configuration record on tape onto your system. Execute the CONFIG.MGR utility. The CONFIG.MGR utility allows the user to update the system configuration record by installing a new configuration file. This utility displays the current and new configuration record. When "Y" is answered to the prompt "Install Configuration:", the new configuration is copied from the file ".SYSTEM.CONFIG.I(serial number)", to the special system area on disk. The new configuration takes effect at the next system load. For further details on the use of the CONFIG.MGR utility, see the 9.5D/8.5D Software Announcement #139, or the BOSS/VS UTILITY USER GUIDE, M5102. The configuration record file name is derived from the system serial number by changing the leading "8" to an "I" and adding the prefix ".SYSTEM.CONFIG.". EXAMPLE: .SYSTEM.CONFIG.I1030114 for SSN 810-30114 This configuration record tape should be saved, in case reinstallation should become necessary. Before going to the next step, LOAD the system so the new ____ configuration record will take affect. If you do not load the system, you will have a minimum configuration and the system will be very slow. 6.4.4. UPDATING SLOTS 2 AND 3 ON 7xxx and 8xxx SYSTEMS ________ _____ _ ___ _ __ ____ ___ ____ _______ WARNING: Because of the changes in slots sizes on 9/8.6C, ALL SLOTS MUST BE UPDATED. NOTE: Running UPDATE.OS automatically updates the Load Sectors for the disk. However, running UPDATE.WCS does not. It is therefore necessary to run UPDATE.LD for REMIDI on 7xxx/8xxx systems on newly initialized systems packs, or whenever question marks ("?/?") appear in Load Sector 2 on the OSINFO screen. See section 4.4.1 for further information on REMIDI SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg050 and UPDATE.LD. O.S. and WCS slots 2 and 3 are updated by using the UPDATE.OS and UPDATE.WCS utilities in a TYPE 1 LOAD. To run these utilities, you must set your prefix to the .R6C11.INST. node. 6.4.4.1. Updating WCS Slot Two (2) ________ ___ ____ ___ ___ REMIDI version BV5C0101 includes all the micro-diagnostics except MPC and LAN controller micro-diagnostics. It is placed in WCS slot 2 and is used for testing on all 7000/7100 and 8000 Series Systems. !UPDATE.WCS ENTER WCS SLOT [0..3]: '2' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE: (choose disk) WCS IMAGE FILE: .R6C11.INST.REMIDI.BV5C0101 WCS LEVEL OF WCS IMAGE FILE: (level displayed) UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETED! 6.4.4.2. Updating Slot Three (3) ________ ____ _____ ___ 6.4.4.2.1. Updating WCS Slot Three (3) ________ ___ ____ _____ ___ 6.4.4.2.1.1. On 7000/7100 Systems and 8000 Systems with LAN __ _________ _______ ___ ____ _______ ____ ___ REMIDI version BVM6A0803 contains micro-diagnostics for the LAN and MPC controllers. It is placed in WCS slot 3 on 7000/7100 Series Systems and on 8000 Series Systems with LAN controllers. The utility UPDATE.LD is used to update the Load Directory for Load Sector 2 to toggle between the two versions of REMIDI in WCS slots 2 and 3. The pointers in Load Sector 2 (displayed on the OSINFO screen) determine which diagnostics will run. See section 4.4.1 for further information on REMIDI and UPDATE.LD. !UPDATE.WCS ENTER WCS SLOT [0..3]: '3' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R6C11.INST.REMIDI.BVM6A0803 WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 6.4.4.2.1.2. On 8000 Systems Without LAN __ ____ _______ _______ ___ This slot will contain system WCS which is common to both the O.S. and DEMON. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg051 !UPDATE.WCS ENTER WCS SLOT [0..3]: '3' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R6C11.INST.WCS.B610 WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 6.4.4.2.2. Updating O.S. Slot Three (3) ________ ____ ____ _____ ___ The O.S. slot 3 will contain the O.S. for DEMON on both 7000/7100 and 8000 Series Systems. !UPDATE.OS BOSS/VS Image File Name: .R6C11.INST.OS3.UV060310016 Target OS Slot (0/1/3) : '3' Target WCS Slot (0-3) : '0' Target Drives (0/1/All/Quit): (choose drive) NOTE: A '0' is entered for the WCS slot to associate DEMON's O.S. with the WCS in slot 0. DEMON and the 8.6C O.S. share the same WCS. The system will now display: Update in progress: nn% Image slot directory n/n:n Updates all complete. 6.4.5. SLOT INFORMATION ____ ___________ Once all slots have been updated, use the utility OSINFO to display the slot information. The information should be similar to figure 6-4. This operating system installation procedure must be performed on all system disks. If disk 1 is a system disk also, repeat the operating system installation procedure for this disk. Figure 6-4. Operating System Information ______ ____ _________ ______ ___________ OPERATING SYSTEM INFORMATION ------------------------------------------------------------------ BOOT LEVEL : X.X.X.X LOAD SECTOR: 0 1 2 3 DISK 0 : 0/0 1/1 0/2 3/3 SERIAL # : XXX-XXXXX ------------------------------------------------------------------ OS NAME OS LEVEL DISK:SLOT WCS LEVEL ------------------------------------------------------------------ R 6C*11 880511 6.3.11.0 0:0 B 6.1.0 R 6C*11 880511 6.3.11.0 0:1 B 6.1.0 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg052 N/A 0:2 REMIDI B 5.1.1 DEMON 6.3.10.16 0:3 B 6.1.0 ------------------------------------------------------------------ NOTE: OSINFO on 7000/7100 Series Systems and 8000 Series Systems with LAN will show the additional version of REMIDI in WCS slot 3. The load sector 3 should be 3/0 on these systems. 6.5. UPGRADING TO 9.6C _________ __ ____ 6.5.1. SPECIAL CONSIDERATIONS _______ ______________ If you are installing a new 9xxx system, go to section 6.2. A new configuration record is required when upgrading to 9.6C from 9.5 O.S. levels. A new configuration record is also required when an upgrade includes new hardware. It is required that systems being upgraded to 9.6C run on a release level that supports the new File System (any level above 8.4D) for at least one week prior to upgrade. When it is established that the system is running smoothly on the software at the end of this period, upgrade to 9.6C may then proceed. 6.5.2. PRINTING OUT THE TERMINAL CONFIGURATION INFORMATION ________ ___ ___ ________ _____________ ___________ Skip this section if you are upgrading to 9.6C from 9.6A/B or 9.5. When upgrading from MPx 7xxx/8xxx Series Systems to the MPx 9xxx Series Systems, it is necessary to reference the terminal configuration in order to properly re-address the 9xxx controllers. Therefore, you must print out a copy of the terminal configuration information before upgrading. 1. Enter the TERM.CONFIG utility. 2. Select OPTION 2 DISPLAY A CONFIGURATION FILE. 3. When the following screen is displayed, enter these responses to the prompts: CONFIGURATION FILE: P OUTPUT DEVICE: DETAILED REPORT: Y ENTRIES CORRECT: Y The terminal configuration information should now be printed. 6.5.3. SAVING FILES TO TAPE ______ _____ __ ____ Current files must first be backed up to tape, using the standard tape utility, SAVERESTORE. When saving files to tape, send the output from the save process to the printer. This will provide a record of backup for each file. Also it is recommended that all tapes be compared to the files on the disk. NOTE: It is essential that the .SYSDATA.SECURITY.DATA file be SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg053 backed up before upgrading to 9.6C. This SECURITY.DATA file will go through a conversion during the upgrade, and the converted file cannot be used on previous O.S. levels. The old version of SECURITY.DATA should be saved in case an O.S. downgrade is ever needed. 6.5.4. OPERATING SYSTEM UPDATE _________ ______ ______ 6.5.4.1. Loading Slots 0 and 1 Using ALT LOAD _______ _____ _ ___ _ _____ ___ ____ NOTE: Positioning of the O.S./WCS slots has been adjusted slightly on O.S. levels 9/8.6C. Therefore, previous O.S. levels cannot reside in slots on the same disk with O.S. levels 9/8.6C. For this reason, ALT LOAD has been enhanced so that it will automatically load both slots 0 and 1. To perform an ALT LOAD from tape follow these steps: A) Mount the new release tape in the tape drive. (All front panel switches should be OFF if using tape drive 0. Switch 1 should be ON if using tape drive 1.) B) Press the "ALT LOAD" button on the front panel. First, a proprietary message will be displayed, and then the following load screen: ____________________________________________________________________ Load PROM Version: x.x.x.x SYSTEM SERIAL NUMBER : 000-00000 Load Drive n SERIAL NUMBER CREATOR: 000-00000 WCS 0 Version: x.x.x CONFIGURATION CREATOR: 000-00000 OS 0 Version: 6.3.x.x CPUs ID #s : n Memory (Mb) : n.0 Disk Drives : n BOSS/VS LOAD FROM TAPE Tape Drives : n Printers : n HVDTs : n IMLCs : n Serial Ports: n Date Format MM/DD/YY: BMTCs : n DATE = MM/DD/YY: LAN Cntrlrs : n TIME = HH:MM:SS: SYSTEM PREFIX: (family).Rxxxx.SYS.,.Rxxxx.INST. System Default Family: (family) File System Write Thru: T/F User Default Family : (family) Per-File Write Through: T/F Installation Name : (name) File System Security : T/F ____________________________________________________________________ Key in the current DATE and TIME at the above prompts. The screen will then display: ____________________________________________________________________ L O A D I N G . . . BOSS/VS Operating System Image Update Utility [version 6.3.x.x] SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg054 OS/WCS information for drive n (nn): 0: ?????????????? ??????? | x x.x.x 1: ?????????????? ??.??.??.??? | ? ??.??.?? 2: -------------- -- -- -- --- | ????????? 3: ?????????????? ??????? | ????????? BOSS/VS Image File Name: (displays one of the following): OSN.AT060311000 (9xxx systems - 1/2-inch) OSN.AC060311000 (9400 systems - 1/4-inch) OSN.BT060311000 (8xxx systems) OSN.BC060311000 (7xxx systems) Target OS Slot (0/1/3) : '0' Target WCS Slot (0-3) : '0' NOTE: Even though only slot 0 is selected, both slots 0 and 1 will be updated. Target Drives (0/1/All/Quit): (choose drive) ____________________________________________________________________ C) The Image File Name will be displayed by the system. Enter '0' at the slot prompts to load O.S. and WCS slots 0 and 1. Enter '0', '1', or 'All' at the drive prompt to update the appropriate drives. The system will now display: ___________________________________________________________________ Now updating WCS slot # n Update in progress: nn% Now updating BOSS/VS Image (displays one of the following): OSN.AT060311000 (9xxx systems - 1/2-inch) OSN.AC060311000 (9400 systems - 1/4-inch) OSN.BT060311000 (8xxx systems) OSN.BC060311000 (7xxx systems) Update in progress: nn% Image slot directory n/n:n Updates all complete. D O N E - R E A D Y F O R N O R M A L D I S K L O A D ___________________________________________________________________ When O.S. and WCS slots 0 and 1 have been updated, reload the system by pressing the LOAD switch. 6.5.4.2. Changing Installation Parameters ________ ____________ __________ NOTE: If any disk has a 'MASTER' status, no update to the disk will be allowed. You must change the disk to a 'BACKUP' status in order to perform the TYPE 3 LOAD functions. To do this, select OPTION 4 (CHANGE MASTER/BACKUP STATUS) from the TYPE 3 LOAD main menu. Be sure to change the disk back to a 'MASTER' status after the TYPE 3 LOAD functions are completed (if this status is SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg055 desired). This MASTER/BACKUP status is simply a flag which makes it possible to write-protect a disk. It is not to be confused with the disk configuration (e.g., SYSTEM, DATA, BACKUP) specified in Option 1 (Change Volume Label Information) of INITIALIZATION OPTIONS (OPTION 2 on the TYPE 3 LOAD main menu). Enter a TYPE 3 LOAD (SPECIAL FUNCTIONS) and select OPTION 2 (INITIALIZATION OPTIONS). OPTION 2 - INITIALIZATION OPTIONS Option 4 - CHANGE INSTALLATION PARAMETERS Only system disks will be displayed. DRIVE NUMBER _______ PRIMARY PREFIX _______________________ (Enter (family).R6C11.SYS. (Family) is the family where the operating system files reside.) SECONDARY PREFIX _____________________ (Enter (family).R6C11.SYS. (Family) is the family where the alternate operating system files reside.) SYSTEM INSTALLATION NAME _________________________ (Sets the default installation name for a specified system disk.) DEFAULT USER FAMILY NAME ________ (Enter default user family.) SECURITY (E=ENABLED, D=DISABLED) ___ FILE SYSTEM WRITE THROUGH? (E=ENABLED, D=DISABLED) ___ WRITE THROUGH DEFAULT ON FILE CREATE (E=ENABLED, D=DISABLED) __ (This parameter specifies what the default write through will be on a file created through a BASIC file create or through the CREATE utility.) UPDATE DISK WITH INSTALLATION PARAMETERS? (Y/N)__ Display: INSTALLATION PARAMETERS SUCCESSFULLY WRITTEN TO DISK (CR) TO CONTINUE: Reload the system by pressing the LOAD switch. 6.5.4.3. Restoring the O.S. Files _________ ___ ____ _____ Enter SAVERESTORE in a TYPE 2 LOAD and choose OPTION 2 RESTORE FILES FROM TAPE. The screen appears as in figure 6-2. Figure 6-5. Restore Screen ______ ____ _______ ______ -------------------------------------------------------- RESTORE FILES SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg056 TAPE SET.ID: DRIVE-NUM: REEL-NUM: PRIMARY PREFIX: (FAMILY).NODE. FILE TYPE (D/P/CR=ALL) COMPARE (CR=Y/N) DATE (MM/DD/YY) TIME (HH:MM) OUTPUT DEVICE (CR=VDT) DELETE EXISTING FILES (CR=Y) VERIFY (Y/CR=N) ENTRIES CORRECT (Y/N) -------------------------------------------------------- At each prompt, enter a . At the prompt, "FILE SPECIFIERS", enter ".". Then enter twice. This will restore all files on the release tape to disk. Please note that once all files are restored to disk, the message "AUTOMATIC COMPARE, CR TO CONTINUE" appears. This automatically rewinds the tape and begins the compare operation. This only occurs when the compare option is selected. When the compare is completed, enter a CTL-IV to return to the "SAVERESTORE" menu. 6.5.5. INSTALLING THE CONFIGURATION RECORD __________ ___ _____________ ______ It is necessary to install a new configuration record when upgrading to 9.6C from 8.4, 8.5 and 9.5 release levels. Until the following procedure is completed, the system will have a minimum configuration. Enter a TYPE 1 LOAD. Set your prefix to .SYSTEM.CONFIG. Before you load the new configuration record, rename the current configuration record on your system, using the RENAME utility, to temporarily preserve it for fall back purposes. (e.g. ".OLDCONFIG.") Using the SAVERESTORE utility, restore the new configuration record on tape onto your system. Execute the CONFIG.MGR utility. The CONFIG.MGR utility allows the user to update the system configuration record by installing a new configuration file. This utility displays the current and new configuration record. When "Y" is answered to the prompt "Install Configuration:", the new configuration is copied from the file ".SYSTEM.CONFIG.I(serial number)", to the special system area on disk. The new configuration takes effect at the next system load. For further details on the use of the CONFIG.MGR utility, see the 8.5D/9.5D Software Announcement #139, or the BOSS/VS UTILITY USER GUIDE, M5102. The configuration record file name is derived from the system serial number by changing the leading "8" to an "I" and adding SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg057 the prefix ".SYSTEM.CONFIG.". EXAMPLE: .SYSTEM.CONFIG.I1030114 for SSN 810-30114 This configuration record tape should be saved, in case reinstallation should become necessary. After installing the new configuration record, LOAD the system. Otherwise your system will be at minimum configuration and will be extremely slow. 6.5.6. UPDATING SLOTS 2 AND 3 ON MPx 9xxx SERIES SYSTEMS ________ _____ _ ___ _ __ ___ ____ ______ _______ O.S. and WCS slots 2 and 3 are updated by using the UPDATE.OS and UPDATE.WCS utilities in a TYPE 1 LOAD. To run these utilities, you must set your prefix to the .R6C11.INST. node. 6.5.6.1. Updating WCS Slot Two (2) ________ ___ ____ ___ ___ The first section of the 9xxx version of REMIDI will reside in this slot. !UPDATE.WCS ENTER WCS SLOT [0..3]: '2' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE: (choose disk) WCS IMAGE FILE: .R6C11.INST.REMIDI.AVA6C0004 WCS LEVEL OF WCS IMAGE FILE: (level displayed) UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETED! 6.5.6.2. Updating WCS Slot Three (3) ________ ___ ____ _____ ___ The second section of the 9xxx version of REMIDI will reside in this slot. !UPDATE.WCS ENTER WCS SLOT [0..3]: '3' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R6C11.INST.REMIDI.AVC6C0004 WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 6.5.6.3. Updating the Load Directory for REMIDI ________ ___ ____ _________ ___ ______ The Load Directory must ALWAYS be updated for Load Sector 2 on ______ 9xxx systems after the installation of REMIDI with UPDATE.WCS, even if the OSINFO screen already shows ther correct pointers for Load Sector 2 (0/2). Update the Load Directory by using the UPDATE.LD utility: SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg058 NOTE: Lines preceded by an "*" require operator input. * Input in command mode !UPDATE.LD Update Load Directory Utility x.6xx.xx Disks (Unit number) on line : 0(16),1(17) Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 6.3.x.x R 6C*xx (date) x 6.x.x 1 1/1 | 6.3.x.x R 6C*xx (date) x 6.x.x 2 ?/? | R x 6.x.x 3 3/0 | 6.3.x.x DEMON (date) R x 6.x.x * New OS slot (0,1,3): 0 * New WCS slot (0..3): 2 * Load sector (0..3) : 2 UPDATE.LD will then display the new Load Directory as follows: Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 6.3.x.x R 6C*xx (date) x 6.x.x 1 1/1 | 6.3.x.x R 6C*xx (date) x 6.x.x 2 0/2 | R x 6.x.x 3 3/3 | 6.3.x.x DEMON (date) R x 6.x.x Notice the change in Load Sector 2. 6.5.6.4. Updating O.S. Slot Three (3) ________ ____ ____ _____ ___ O.S. slot 3 will contain the O.S. for DEMON. !UPDATE.OS BOSS/VS Image File Name: .R6C11.INST.OS3.UV060310016 Target OS Slot (0/1/3) : '3' Target WCS Slot (0-3) : '0' Target Drives (0/1/All/Quit): (choose drive) NOTE: A '0' is entered for the WCS slot to associate DEMON's O.S. with the WCS in slot 0. DEMON and the 8.6C O.S. share the same WCS. The system will now display: Update in progress: nn% Image slot directory n/n:n Updates all complete. If drive 1 is a system disk also, the operating system installation procedure must be repeated for this disk. 6.5.7. SLOT INFORMATION ____ ___________ Once all slots have been updated, use the utility OSINFO to display the slot information. The information should be similar to figure 6-6. Figure 6-6. Operating System Information ______ ____ _________ ______ ___________ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg059 OPERATING SYSTEM INFORMATION ------------------------------------------------------------------ BOOT LEVEL : X.X.X.X LOAD SECTOR: 0 1 2 3 DISK 0 : 0/0 1/1 0/2 3/0 SERIAL # : XXX-XXXXX ------------------------------------------------------------------ OS NAME OS LEVEL DISK:SLOT WCS LEVEL ------------------------------------------------------------------ R 6C*11 880511 6.3.11.0 0:0 A 6.5.4 R 6C*11 880511 6.3.11.0 0:1 A 6.5.4 N/A 0:2 REMIDI A 6.3.4 DEMON 6.3.10.16 0:3 REMIDI A 6.3.5 ------------------------------------------------------------------ Installation is now complete. 6.6. UPDATING SLOTS 0 AND 1 USING UPDATE.OS AND UPDATE.WCS ________ _____ _ ___ _ _____ _________ ___ __________ Because the new ALT LOAD from tape loads O.S. and WCS slots 0 and 1, it is no longer necessary to use UPDATE.OS and UPDATE.WCS to update these slots during a normal installation. However, these slots can be loaded at any time using these utilities, provided the O.S. and WCS files are resident on disk and you are not booted from the slot you wish to update. The following is the procedure to accomplish this. 6.6.1. Updating O.S. Slots 0 and 1 ________ ____ _____ _ ___ _ Set the prefix to the .INST. node by keying in the following in command mode: !PREFIX .R6C11.INST. !UPDATE.OS BOSS/VS Operating System Image Update Utility [Version 6.3.x.x] OS/WCS information for drive n (nn) 0: R 6C*xx (date) 6.3.x.x | X 6.x.x 1: ?????????????? ??.??.??.??? | ? ??.??.?? 2: -------------- -- -- -- --- | R X 6.x.x 3: DEMON 6.3.x.x | R X 6.x.x The following prompts will then be displayed, one at a time: BOSS/VS Image File Name: .R6C11.INST.OSN.UV060311000 Target OS Slot (0/1/3) : '0' or '1' Target WCS Slot (0-3) : '0' or '1' Target Drives (0/1/All/Quit): (choose drive) The system will now display: Update in progress: nn% Image slot directory n/n:n Updates all complete. 6.6.2. Updating WCS Slots 0 and 1 ________ ___ _____ _ ___ _ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg060 Set the prefix to the .INST. node by keying in the following in command mode: !PREFIX .R6C11.INST. !UPDATE.WCS ENTER WCS SLOT [0..3]: '0' or '1' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R6C11.INST.WCS.B610 (7xxx/8xxx) .R6C11.INST.WCS.A6504 (9xxx) WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 6.7. SYSTEM STARTUP ______ _______ 6.7.1. STANDARD STARTUP COMMAND FILE ________ _______ _______ ____ The commands for the standard System Startup Command File are released in the file: .R6C11.SYS.START.CMD The standard commands are: h .. !MAGNET.STARTUP !GROUP.CREATE SPOOLER,TYPE=SYSTEM !SPOOL P*,VERIFY=F,PAUSE=F !GROUP.ENABLE TERMINALS,VERIFY=F,PAUSE=F The name of the System Startup Command File actually used for startup is: (system-default-family).SYSDATA.START.CMD Part of 9.6C/8.6C BOSS/VS system installation is to copy the released file to the .SYSDATA. node and make changes and additions as necessary. Note that the commands and parameters in this file must match the commands and parameters defined in the CLI command and function definition files for the individual system being installed. If the System Startup Command File is not found after a system load, then a default initialization is performed. This puts all printers into spooled mode and enables terminals. The following outlines the commands, some of the implications and details of the System Startup Command File method of system configuration. 6.7.1.1. Command File Definitions _______ ____ ___________ MAGNET.STARTUP ______________ SOFTWARE-BASIC FOTB-BOSS/VS BBVIII & BBIX-----------FIB052 Pg061 This command runs a released MAGNET program that does all of the startup operations required by the MAGNET subsystem. This command should be deleted if MAGNET is not part of the system configuration. GROUP.CREATE_SPOOLER,TYPE=SYSTEM ________________________________ This command creates the SPOOLER Group that maintains the activity log files and Group statistics for the spooler subsystem. This command should come before the 'SPOOL P*' command. SPOOL_P*,VERIFY=F,PAUSE=F _________________________ This command puts all of the printers into spooled mode, and causes any eligible requests on the spooled printers to start printing. GROUP.ENABLE_TERMINALS,VERIFY=F,PAUSE=F _______________________________________ This command enables the 'built-in' TERMINALS Group, and allows all users to logon to any terminals. This command is provided to allow the terminals to be enabled under user control. See below. NOTE: IF A SYSTEM STARTUP COMMAND FILE EXISTS, THIS COMMAND, OR SOME OTHER COMMAND TO ENABLE TERMINAL GROUPS, MUST BE IN THE SYSTEM STARTUP COMMAND FILE FOR USERS TO LOGON TO THE SYSTEM. In case the TERMINALS Group is disabled, a user with 'system operator' status can enable this group when attempting to logon to the system. This allows an operator to logon to the system in case the Startup Command File did not enable the TERMINALS Group, or the TERMINALS Group was left disabled by accident and all operators signed off the system. To enable the TERMINALS Group during logon the operator attempts to logon and ignores the 'Logon disabled' error messages and enters a 'CR' to continue. A prompt is displayed asking the operator if he wants to enable the TERMINALS Group. NOTE: THIS OPTION IS NOT AVAILABLE IF SOME OTHER TERMINAL TYPE GROUP IS ENABLED. ALSO, ONLY THE TERMINALS GROUP IS ENABLED, AND IT IS NOT CREATED IF IT DOES NOT EXIST. 6.7.2. IMPLICATIONS ____________ 1) Normal system startup is automatic. The system ______ ______ _______ __ _________ configuration options defined when the system was installed (placed into the System Startup Command File) are put into effect each time the system is loaded, with no further action by the user. These startup options may be modified by the user at any time, by editing the System Startup Command File. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg062 2) Startup sequence is under user control. Users now have _______ ________ __ _____ ____ _______ the ability to control the sequence of events at startup, after the internal startup sequence is complete. Users that do not need this level of control may ignore this feature. Some users may wish to run specific programs, and do recovery operations, before MAGNET and/or the SPOOLER are started up. This ability would be impossible if these subsystems were always started by the internal system initialization. 3) System recovery is possible before all users logon. This ______ ________ __ ________ ______ ___ _____ _____ approach allows the operator to allow only specified terminals/users to logon after a system load. The System Startup Command File containing the single command: GROUP.CREATE , TYPE=TERMINAL, USERS=SYS.MGR, DEVICES=T0 would allow only the user 'SYS.MGR' to logon to terminal 'T0' after the system load. No other users could logon, and no other activity would start. In this case the printers will be in suspended mode and MAGNET will not be initialized. When the system operator is finished with the recovery operations the 'normal' system configuration command file may be run by the operator to begin normal system processing. Again, users who do not need this level of control may ignore this feature. 4) Default startup with no System Startup Command File. When _______ _______ ____ __ ______ _______ _______ ____ the TYPE 1 LOAD is complete, if the System Startup Command File is not found then 'default' startup conditions are in effect. In this case the system is available for any use. This mode is intended to support systems that want only these default startup options. The 'built-in' TERMINALS Group is enabled and allows all users to logon to any terminal. A system group named SPOOLER is created and the printers are put into spooled mode. The MAGNET subsystem is not activated. ___ The following is a description of the details of the System Startup Job: When a TYPE 1 LOAD is performed, the last module to be initialized is the Job Manager (JMM). The final act of JMM is to run a batch job with a CLI command file. The files involved are: (system-default-family).SYSDATA.START.CMD SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg063 (system-default-family).SYSDATA.START.IN (system-default-family).SYSDATA.START.OUT SYSDATA.START.CMD is a sequential file that contains all of the startup commands; this is the System Startup Command File. The Job Manager looks in the system default family (only) for this file. SYSDATA.START.IN is a sequential file that contains any data that may be input by commands and programs in the above startup file. A read from standard INPUT will read records from this file. The Job Manager looks in the system default family (only) for this file. SYSDATA.START.OUT is a sequential file that contains the results of the startup command file. A write to standard OUTPUT by commands and programs will be placed into this file. The Job Manager deletes this file in the system family if it exists, prior to running the startup command file. If the startup file (system-default-family).SYSDATA.START.CMD - or - (system-default-family).SYSDATA.START.CMD.TEXT is not found, the Job Manager will perform a default startup described above. If the startup file (system-default-family).SYSDATA.START.IN - or - (system-default-family).SYSDATA.START.IN.TEXT is not found, the Job Manager will attach a null file to startup INPUT; an End-Of-File will be returned for each read from standard INPUT. NOTE: THE SYSTEM STARTUP COMMAND FILE CONTAINS (ONLY) STANDARD CLI COMMANDS. A CLI command may be: 1) A CLI Command or Function (START, PREFIX, $WHERE, etc.) 2) A system utility (DIR, COPY, etc.) 3) The name of a program to run. 4) The name of another CLI command file. 7. RELATED DOCUMENTATION _______ _____________ 2770/2780/3770/3780 Batch Emulator User Guide M 5080C 3270 Pass-Through Reference Manual M 5091A BOSS/VS Business BASIC 86 Reference Manual M 6262A * BOSS/VS User Guide M 5098F * BOSS/VS Utilities User Guide M 5102E * BOSS/VS Utilities User Guide Change Package M 5102F ** SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg064 3270 Emulation Package Operator Guide for MAI 8000 Series M 5129 File Transfer Facility User Reference Manual M 6352A BOSS/VS Installation Guide M 5138D * BOSS/VS Installation Guide Change Package M 5138E ** MPx System Installation Planning Guide M 5146F * BOSS/VS Special Purpose Utilities User Guide M 5151 BOSS/VS System Support Manual M 5152 Intersystem Transport Package User Guide M 6354D MAI 8000 Series COBOL Reference Manual M 5174 MAI 8000 Series COBOL User Guide M 5175 BOSS/VS File Conversion User Guide M 5185A MAGNET/VS User Reference Manual M 6363 * * These manuals were revised for 9.6A/8.6A. ** These change packages were created for 9/8.6C and must be used with the corresponding manuals. ORIGINATOR: MBF SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB052 Pg065 FIB 00053 08/16/88 *** Enhancements/Considerations with Release 8.6C/9.6C [ WPSF 472 ] *** MAI Basic Four, Inc. is pleased to announce that the new system software revisions, 9.6C/8.6C, are now available. The 9.6C revision is the recommended revision for MPx 9xxx Series Systems. The 8.6C revision is the recommended revision for MPx 7xxx and 8xxx Series Systems. The 9.6C/8.6C revision contains the following enhancements: o Support for the new MPx 9400 Series Systems, which feature the new DMA-II controller for SCSI ("Small Computer System Interface") disk and tape devices. o Support for the new, more compact MPx 9600 Series Systems, which provide the same computing power as MPx 9500 Series Systems. o Support for the new, higher density, 250MB, 5 1/4-inch SCSI disk drive for MPx 9400 Series Systems, via the new DMA-II controller. o Support for the new 120MB, 1/4-inch, embedded SCSI MCS tape unit, via the new DMA-II controller. o A new SPOOLER TESTPRINT option, which allows printing of trial forms with live data. o A new TERM.CONFIG option for bidirectional XON/XOFF flow control. o A new TERM.CONFIG option for dropping DTR on process release. o A new ALT LOAD from tape, which loads both O.S. slots 0 and 1. (Previously, only O.S. slot 0 could be loaded with ALT LOAD.) o Automatic reconstruction of the SPOOLER REQUESTS file at load time after a system dump. Previously, this file had to be reconstructed by the user. o Increased buffer cache for high use data files to decrease disk input/output operations and increase system performance on large, heavily loaded systems. o Improved logon account security. o A BROADCAST facility, which provides for inter-terminal message sending. o TYPE 2 and TYPE 3 LOAD standalone functions now have enhanced performance on systems with a serial terminal as T0. As a result, T0 must be a model 4309 (EVDT) or later terminal (or an HVDT). Terminal models 7250 and 7270 are no longer supported as T0. o An enhancement to the DIR utility, which allows the first line of a BASIC program to be printed or displayed on a terminal when ATTRIBUTES = ALL is selected. Configuration Record Considerations A new configuration record is not required when upgrading from release 9.6A/B to 9.6C or from release 8.6A/B to 8.6C. A new configuration SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB053 Pg001 record is required, however, when upgrading from 8.4 and 9.5/8.5 releases to 9.6C/8.6C releases. A new configuration record is also required when an upgrade includes new hardware. Software Announcement The 9.6A/8.6A and 9.6C/8.6C Software Announcements exist as serial files on the official 9.6C/8.6C O.S. release tape, which allows the user to print copies, if needed. To print these documents, SUBMIT the following files to the printer: (family).R6Cxx.INST.DOC.ANNOUNCE6A 9.6A/8.6A (family).R6Cxx.INST.DOC.ANNOUNCE6C 9.6C/8.6C Special Considerations 1. Installation procedures have been revised for 9.6C/8.6C. Please read the installation instructions before attempting installation or upgrade. 2. In preparation for future MPx enhancements, positioning of the image slots has been adjusted slightly. Therefore, previous O.S./WCS levels cannot reside in slots on the same disk with release levels 9.6C/8.6C. In addition, ALL slots must be updated when upgrading 9.6C/8.6C. 3. As of this release, T0 must be a model 4309 or later terminal or an HVDT. Terminal models 7250 and 7270 are no longer supported as T0. This change was made to improve backup times in TYPE 2 and TYPE 3 LOADS. 4. The .SYSDATA.SECURITY.DATA file should be saved before upgrading to 9.6C/8.6C (for fall back purposes only). The 9/8.6C SECURITY.DATA file is not transportable to previous release levels. 5. It is not expected that a downgrade from release levels 9.6C/8.6C will be necessary. However, in the event of an O.S. downgrade from these levels, a special procedure must be followed. See the upcoming field bulletin "9.6C/8.6C Warnings and Special Considerations" for this procedure. ORIGINATOR: Nancy Prentiss SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB053 Pg002 FIB 00054 08/16/88 *** RECONSTRUCT at 8.6/9.6 MUST have Sufficient Disk Space [ WPSF 473 ] *** On 8.6/9.6A through 8.6/9.6C, when using the RECONSTRUCT utility to repair a Multi-Keyed or Direct file and there is insufficient disk space to complete the repair, the file will be left in a corrupted state. An error message will be displayed and the integrity flag is reset but the file may possibly be corrupt. NOTE: DON'T USE DISKANALYZER TO RECONSTRUCT THE FILE. IT WILL CAUSE A SYSTEM DUMP. Use the following procedure when reconstructing Multi-Keyed or Direct files: 1. Before using the RECONSTRUCT utility, make sure that there is sufficient disk space available. RECONSTRUCT estimates the amount of space needed and also allows the specification of a family to use for scratch files. NOTE: WHEN A FILE LACKS INTEGRITY, RECONSTRUCT WILL NOT ESTIMATE THE SPACE NEEDED PROPERLY. TO ESTIMATE THE SPACE NEEDED: NUMBER OF SECTORS REQUIRED=(NUMBER OF RECS USED*(LARGEST KEY +8)*7)/1024. FOR EXAMPLE: DIRECT FILE WITH 100,000 RECORD USED WITH A KEYSIZE OF 11 WOULD REQUIRE: SECTORS: 12989=(100000(11+8)*7)/1024 A MULTI-KEY FILE WITH 50,000 RECORDS USED WITH KEYSET SIZES 11,10,20 BYTES. THE SPACE REQUIRED WOULD BE: SECTORS: 9570=(50000(20+8)*7)/1024 (REMEMBER TO USE LARGEST KEYSET FOR MULTI-KEYED FILES) The operator should choose a family that has ample space. 2. If an out-of-disk-space error is returned, the operator should do a DIR on the file immediately. If the file lacks integrity, as it should, then the only action required is to make more space available and to restart the RECONSTRUCT. If the file shows good integrity, the file MUST NOT be used because any use will cause a system dump. The file can be renamed so that it may not be accessed by the application. Only RECONSTRUCT can repair the file so, space must be freed up by deleting files or moving them to another family. Then RECONSTRUCT can be started again. Once the reconstruction is complete, the file can be renamed back to the original name. This problem will be fixed in 8.6/9.6E. ORIGINATOR: Randy Case SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB054 Pg001 FIB 00055 08/16/88 *** ASG Software Requires Installation of Key after Upgrade [ WPSF 474 ] *** Due to changes in the 8.6/9.6 OS, ASG Applications may require re-installation. of the security key. After an OS Upgrade, the following message may appear when the application software is executed: ______________________________________________________________________________. |. | | THIS SOFTWARE IS NOT CONFIGURED TO RUN ON THIS SYSTEM. | |. | | CONTACT YOUR APPLICATIONS SOFTWARE SUPPORT REPRESENTATIVE FOR ASSISTANCE. | |. | |______________________________________________________________________________ If this message appears, please refer to the application installation instructions to reinstall the same key. ORIGINATOR: Randy Case SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB055 Pg001 FIB 00056 10/24/88 *** Restricting Log-on on 8/9/10.6 Level Systems [ WPSF 501-1 ] *** It is possible to allow only specified terminals/users to log on to the system in a TYPE 1 LOAD. This is especially useful after a fatal system error, making system recovery possible before all users log on. Typically, the system operator would be validating and reconstructing files at this time. To achieve this, the first step is to disable all groups with TYPE = TERMINAL, using GROUP.DISABLE. (This will not cause users who logged on before the disable to be logged off. To eliminate any users who might have already logged onto the system, BROADCAST a logoff message and then release them. They will then be prevented from logging back on.) The next step is to shutdown MAGNET, if it is used on the system. To do this, execute NETSSTART in command mode, and answer 'Y' to the question "Do you want to stop MAGNET?". The third step is to create one special TERMINAL type group by executing a statement similar to the following in command mode: !GROUP.CREATE , TYPE=TERMINAL, USERS=SYS.MGR, DEVICES=T0 This will allow only the user 'SYS.MGR' to log on to terminal 'T0'. (One or more other users or terminals could be substituted for 'SYS.MGR' and 'T0'.) When the system operator is finished with the recovery operations, he can then disable his special TERMINAL group. He then needs to enable all other TERMINAL type groups and start MAGNET by executing the .SYSDATA.START.CMD file in command mode. Normal system processing can then continue. ORIGINATOR: N. Prentiss SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB056 Pg001 FIB 00057 10/24/88 *** 8/9/10.6E Release Announcement [ WPSF 501 ] *** MAI Basic Four, Inc. is pleased to announce that the new system software revisions, 10.6E/9.6E/8.6E, are now available. The 10.6E revision is the required revision for the ADVANCED SERIES family. The 9.6E revision is the recommended revision for MPx 9xxx Series Systems. The 8.6E revision is the recommended revision for MPx 7xxx and 8xxx Series Systems. There were no 9.6D/8.6D system software revisions. C O N T E N T S 1 THE 10/9/8.6E RELEASE . . . . . . . . . . . . . . . . . 2 1.1 ENHANCEMENTS IN THIS RELEASE . . . . . . . . . . . . . 2 1.2 CONFIGURATION RECORD CONSIDERATIONS . . . . . . . . . 3 1.3 SOFTWARE ANNOUNCEMENT . . . . . . . . . . . . . . . . 3 1.4 FIXES IN THIS RELEASE . . . . . . . . . . . . . . . . 3 1.4.1 OPERATING SYSTEM . . . . . . . . . . . . . . . . . . 3 1.4.2 COMMAND LANGUAGE . . . . . . . . . . . . . . . . . . 3 1.4.2.1 START Command . . . . . . . . . . . . . . . . . . 3 1.4.3 UTILITIES . . . . . . . . . . . . . . . . . . . . . 4 1.4.3.1 DISKANALYZER . . . . . . . . . . . . . . . . . . . 4 1.4.3.2 JOB MANAGER . . . . . . . . . . . . . . . . . . . 4 1.4.3.3 RECONSTRUCT . . . . . . . . . . . . . . . . . . . 4 1.4.3.4 SAVERESTORE . . . . . . . . . . . . . . . . . . . 4 1.4.3.5 SECURITY . . . . . . . . . . . . . . . . . . . . . 4 1.4.3.6 SPOOLER . . . . . . . . . . . . . . . . . . . . . 5 1.4.3.7 UPDATE.WCS . . . . . . . . . . . . . . . . . . . . 5 1.4.4 BASIC . . . . . . . . . . . . . . . . . . . . . . . 6 1.4.5 FILE SYSTEM . . . . . . . . . . . . . . . . . . . . 6 1.5 SPECIAL CONSIDERATIONS . . . . . . . . . . . . . . . . 6 1. THE 10/9/8.6E RELEASE 1.1. ENHANCEMENTS IN THIS RELEASE The 10.6E/9.6E/8.6E release contains the following enhancements: o Support for the new, high performance ADVANCED SERIES family. o Support for the new, high capacity, high performance 621MB fixed disk and its associated DMA-III controller. o An AUDITOR'S LOGBOOK, which allows for an optional, automatic record of updates to a file. AUDITOR'S LOGBOOK is a chargeable feature controlled by software key. o Enhancements to the hardware ERRORLOG, including: 1) a summary option added to the DOWNLOAD group; 2) the drive number added to I/O error data; 3) expanded cache error reporting to include the ADVANCED SERIES; and 4) clarification of the memory error report. o Full 7-bit/8-bit support for T0 when this release is used in conjunction with the new MCS/M board on the ADVANCED SERIES. o An enhanced UPDATE utility, which now expands files in a SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB057 Pg001 fraction of the time required previously. UPDATE no longer makes a copy of the entire file, but merely adds extents when an expand is specified. o High frequency margin testing for use with hardware diagnostics on the ADVANCED SERIES family. o A new INITFILE utility, which initializes a file, retaining either the same disk allocation or the primary extent only. o An enhanced BASIC EDIT directive, which allows editing of the last statement typed without specifying a statement number. o A new OS/WCS file naming convention, which uses shortened file names to simplify installation procedures. o An enhanced TASKS utility, which now refreshes the TASKS screen only when the screen changes, instead of every 2.5 seconds. This makes the screen more readable on terminals running at 1200 and 2400 baud. o An enhanced SECURITY.UPDATE utility, which allows any user to change his own password. (This enhancement was actually implemented as of 9/8.6C.) o An enhanced ALT LOAD on the ADVANCED SERIES, which allows REMIDI and DEMON to be loaded into memory and executed. 1.2. CONFIGURATION RECORD CONSIDERATIONS In general, a new configuration record is required when upgrading to a new system type (e.g., from an 8xxx to a 9xxx system), when adding new hardware, and when upgrading to a new major release level (e.g., 8.5 to 8.6). A new configuration record is not required when upgrading from releases 9.6A/B/C to 9.6E or from releases 8.6A/B/C to 8.6E. A new configuration record is required, however, when upgrading to 10.6E. A new configuration record is also required when upgrading from 8.4 and 9.5/8.5 releases to 10.6E/9.6E/8.6E releases. 1.3. SOFTWARE ANNOUNCEMENT The 10.6E/9.6E/8.6E Software Announcement exists as a serial file on the official 10/9/8.6E O.S. release tape, which allows the user to print copies, if needed. To print this document, SUBMIT the following file to the printer: (family).R6E14.INST.DOC.ANNOUNCE6E 1.4. FIXES IN THIS RELEASE The 10/9/8.6E releases contain fixes for the following system problems: 1.4.1. OPERATING SYSTEM 1) SPR 518490 - The 'AC' tape loader for 9400 systems would display 'AT' on the terminal screen during an ALT LOAD. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB057 Pg002 2) SPR 518642 - Certain very large MPx configurations sometimes experienced an "Insufficient Special Shadow" system dump. 1.4.2. COMMAND LANGUAGE 1.4.2.1. START Command SPR 514159 - One account was able to START an account on another terminal with higher privileges than itself, as long as the accounts had the same User Level. 1.4.3. UTILITIES 1.4.3.1. DISKANALYZER 1) A "File not lockable - opened by others" message was returned by DISKANALYZER when the file was not open if the following 3 conditions were true: a) the file was a Multi-key file, AND b) the file name contains a "%", AND c) the user was running DISKANALYZER Option 3, "Validate Files". 2) SPR 517795 - DISKANALYZER would sometimes corrupt a Multi-key file in such a way as to prevent BASIC SETFIELD from working. 1.4.3.2. JOB MANAGER SPR 518491 - If a user renamed a .SYSLOG. file, changing the string length, and left the file in the .SYSLOG. node, the system would dump with the fourtuples 2,10,20,11 (Instruction Fault in Job Manager Module) and 1,146,0,11 while initializing Job Manager when entering a TYPE 1 LOAD. SPR 516691 - JOB.CREATE commands that were incorporated into the .SYSDATA.START.CMD file would not execute if the SYSTEM.MANAGER account was not present on the system. 1.4.3.3. RECONSTRUCT SPR 517822 - Direct and Multi-key files could be corrupted if the RECONSTRUCT utility ran out of disk space. In this case, the DIR utility would show good integrity for the file, but any access of the file (including DISKANALYZER) would cause an Instruction Fault/Nil Pointer system dump. 1.4.3.4. SAVERESTORE SPR 517308 - On 1/2-inch tape drives, if a user did a SAVERESTORE restore or compare, and he mounted a new reel to start or continue the restore/compare, a "Tape drive offline" message was displayed on the mount menu. 1.4.3.5. SECURITY 1) SPR 517425 - When the System Prefix was included in an account's prefix list (using the SECURITY utility), a PPUSH or PPOP would cause extra System Prefixes to be appended on the end of the account's prefix list. Eventually, this caused the system dump 2,10,5,32, with SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB057 Pg003 the secondary fourtuple 1,240,0,32, due to the prefix list being too long. 2) SPR 518786 - The message "Record not found" was returned by the SECURITY utility when using the LIST ACCOUNTS option, if the following steps were performed in sequence: a) The LIST ACCOUNTS option was selected specifying all MINOR ACCOUNTs under a specific MAJOR ACCOUNT name (using '*' for MINOR ACCOUNT) and ATTRIBUTES = YES. b) After the above accounts were listed, the LIST ACCOUNTS option were selected again, and one particular MINOR ACCOUNT name was specified from the group of accounts that was listed in a). "Record not found" was then displayed. 3) SPR 518812 - SECURITY.UPDATE allowed a user with no password to be updated to any user level (0-3). 1.4.3.6. SPOOLER 1) SPR 517645 - Serial printers configured as DMP serials sometimes hung while printing long print jobs. The Spooler status would show "PRINTING", but the number of pages and percent done never changed. 2) SPR 518108 - Cancelled spool jobs created from BASIC were removed from the queue, but the spool files remained on disk in the .SPL. node. (This was a problem on 9/8.6C only.) 3) SPR 518186 - If a major or minor account name exceeded 15 characters, and a spool job was submitted from that account, the system would dump with the fourtuples 2,10,33,11 (Instruction Fault in Spooler Module) and 1,242,0,11 when the spool job was accessed. 4) SPR 518994 - Restarting a spool job on a spool record that was greater than 247 bytes caused system dump 2,10,33,32 (Instruction Fault in Spooler Module) and 1,242,0,32 (String Limit Exceeded). 5) SPR 518718 - Restarting a print job after the TIME option had been modified sometimes caused the job to have a "Deferred" status, even after the time to print had passed. 6) SPR 519093 - If the system is reloaded when there are P* requests in the REQUESTS file (spool queue), and PRSTATUS is executed after the reload, the system will dump with the fourtuples 2,10,33,11 (Instruction Fault in Spooler Module) and 1,146,0,11 (Range Violation). The workaround is either to route all print requests to a specific printer, or be sure there are no P* requests in the REQUESTS file when the system is taken down. If the dump occurs, the REQUESTS file should be deleted and the system reloaded. Any jobs that were left in the spool queue should be printed using the SUBMIT utility. 1.4.3.7. UPDATE.WCS SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB057 Pg004 SPR 517589 - UPDATE.WCS did not update the Load Directory for REMIDI on 9xxx systems. 1.4.4. BASIC 1) Changes to the BASIC TIM= function caused MAI OFFICE to log the user off the system after 4 1/2 minutes, even if TIM= was set for a longer period of time. The fix in Presentation Services allows for a timeout value of up to 512 seconds (about 8 1/2 minutes). If the timeout value specified is over 512 seconds is the system will never timeout. 2) SPR 518169 - If the ESCAPE key was pressed while reading a file with a duplicate key, dropping the terminal into console mode (no ESCAPE handling), typing RUN at this point to continue the program caused a record in the file to be skipped. 1.4.5. FILE SYSTEM SPR 517631 - Sometimes a hang condition would occur when accessing a Multi-Key file. Subsequent accesses of this file by other processes would result in hanging of those processes also. 1.5. SPECIAL CONSIDERATIONS 1) As of release 9/8.6C, positioning of the image slots has been adjusted slightly. Therefore, O.S./WCS levels previous to 9/8.6C cannot reside in slots on the same disk with release levels 9/8.6C and above. 2) As of release 9/8.6C, T0 must be a model 4309 or later terminal on all systems, or an HVDT on 7xxx/8xxx/9xxx systems. Terminal models 7250 and 7270 are no longer supported as T0. 3) High Speed terminals (and the VCON controller board) are not supported on ADVANCED SERIES. 4) As of release 9/8.6C, the .SYSDATA.SECURITY.DATA file is not transportable to previous release levels. Therefore, if you are upgrading to 10/9/8.6E from a release prior to 9/8.6C, this file should be saved before the upgrade, for fall-back purposes. 5) Files transferred from 10/9/8.6E to O.S. levels below 9/8.6A must be transported with EXTTAPE, MCSI, FTF, TBC, or ATP. If a downgrade is performed from 10/9/8.6E to a release prior to 9/8.6A, the user's files must be transported to the older O.S. level with one of the above utilities. ORIGINATOR: N. Prentiss SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB057 Pg005 FIB 00058 10/24/88 *** CONFIG.DISPLAY & CONFIG.TAPE Utilities on 8/9.6C [ WPSF 472-2 ] *** As of releases 9/8.6C, the CONFIG.DISPLAY and CONFIG.TAPE utilities are included on the BOSS/VS O.S. tape under the .INST. node. These utilities are only used on BOSS/IX configuration records that reside on BOSS/VS systems. Typically, these BOSS/IX configuration records have been transmitted to the BOSS/VS systems from Software Distribution. CONFIG.DISPLAY allows BOSS/IX configuration records to be displayed on BOSS/VS systems. CONFIG.TAPE allows BOSS/IX configuration records to be saved to 1/2-inch or 1/4-inch tape from BOSS/VS systems in the format necessary for installation on BOSS/IX systems. The System Serial Number ranges for the different BOSS/IX system types are as follows: 1800 53000 - 59999 2000 90000 - 99999 2500/3000/4000 81000 - 89999 When prompted for the System Serial Number in either utility, enter the system type, a dash, and the SSN. For example: 2000-90001. The file names for 1800 configuration records begin with 'C00'. The file names for 2000, 2500, 3000, and 4000 configuration records created on releases 9/8.6C and later begin with 'A00'. The file names for configuration records created on releases prior to 9/8.6C for system types 3000 and 4000 began with a different letter: 3000 configuration record file names began with 'B00', and 4000 configuration record file names began with 'D00'. THE 9/8.6C VERSIONS OF CONFIG.DISPLAY AND CONFIG.TAPE WILL NOT WORK WITH 3000 AND 4000 CONFIGURATION RECORD FILES THAT DO NOT BEGIN WITH 'A00'. If you are using the 9/8.6C versions of these utilities, you must RENAME any configuration record files that begin with 'B00' and 'D00' to begin with 'A00'. The System Serial Number should remain the same. (DO NOT RENAME configuration record files that begin with 'C00'. These are 1800 configuration record files, and their names have not changed.) As a precaution, save the .SYSTEM.CONFIG. node on tape before renaming any configuration record files. The 3000 configuration record files ('B00') should be renamed before the 4000 configuration record files ('D00'). this is to assure that configuration records for the same SSN (because of an upgrade from a 3000 to a 4000 system) will reflect the 4000 system. It is recommended that BOSS/IX configuration records be examined with the CONFIG.DISPLAY utility for accuracy before saving them to tape with CONFIG.TAPE. ORIGINATOR: N. Prentiss SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB058 Pg001 FIB 00059 12/19/88 *** Warnings & Special Considerations for Rel. 8/9.6C [ WPSF 472-1 ] *** These Warnings and Special Considerations are applicable to release levels 9.6C and 8.6C. This Field Bulletin is part of an effort to expand the reporting of known problems and special considerations to the field. C O N T E N T S 1 WARNINGS AND SPECIAL CONSIDERATIONS . . . . . . . . . . 2 1.1 FOR ALL MPX SERIES SYSTEMS . . . . . . . . . . . . . . 2 1.1.1 OPERATING SYSTEM . . . . . . . . . . . . . . . . . . 2 1.1.1.1 Different O.S. Levels in Adjacent Slots . . . . . 2 1.1.1.2 SECURITY.DATA File . . . . . . . . . . . . . . . . 2 1.1.1.3 Operating System Downgrade . . . . . . . . . . . . 2 1.1.2 COMMAND LANGUAGE . . . . . . . . . . . . . . . . . . 3 1.1.2.1 START Command . . . . . . . . . . . . . . . . . . 3 1.1.3 UTILITIES . . . . . . . . . . . . . . . . . . . . . 3 1.1.3.1 CONFIG.MGR . . . . . . . . . . . . . . . . . . . . 3 1.1.3.2 DELETE, CREATE, RENAME . . . . . . . . . . . . . . 4 1.1.3.3 DISKANALYZER . . . . . . . . . . . . . . . . . . . 4 1.1.3.4 FAMILY . . . . . . . . . . . . . . . . . . . . . . 4 1.1.3.5 GETDEVINFO . . . . . . . . . . . . . . . . . . . . 5 1.1.3.6 JOB MANAGER . . . . . . . . . . . . . . . . . . . 5 1.1.3.7 RECONSTRUCT . . . . . . . . . . . . . . . . . . . 6 1.1.3.8 SAVERESTORE . . . . . . . . . . . . . . . . . . . 6 1.1.3.8.1 Restoring ISDC Code Files and REMIDI . . . . . . 6 1.1.3.9 SECURITY . . . . . . . . . . . . . . . . . . . . . 7 1.1.3.10 SPOOLER . . . . . . . . . . . . . . . . . . . . . 7 1.1.3.11 EXTTAPE . . . . . . . . . . . . . . . . . . . . . 9 1.1.3.12 TERM.TABLE . . . . . . . . . . . . . . . . . . . 9 1.1.3.13 UPDATE . . . . . . . . . . . . . . . . . . . . . 9 1.1.3.14 MCSI . . . . . . . . . . . . . . . . . . . . . . 9 1.1.4 LOGON . . . . . . . . . . . . . . . . . . . . . . . 9 1.1.5 BASIC . . . . . . . . . . . . . . . . . . . . . . . 10 1.1.5.1 STATUS . . . . . . . . . . . . . . . . . . . . . . 10 1.1.5.2 Running SORT from BASIC . . . . . . . . . . . . . 10 1.1.5.3 Terminal Echo . . . . . . . . . . . . . . . . . . 10 1.1.5.4 MTCS (MCS) Tape Drive . . . . . . . . . . . . . . 10 1.1.5.5 Program File Compatibility . . . . . . . . . . . . 10 1.1.5.6 CONSOLELOCK . . . . . . . . . . . . . . . . . . . 10 1.1.5.7 MAI OFFICE Time-Out . . . . . . . . . . . . . . . 11 1.1.6 FILE SYSTEM . . . . . . . . . . . . . . . . . . . . 11 1.1.6.1 Multi-Key Files . . . . . . . . . . . . . . . . . 11 1.1.7 COMMUNICATIONS . . . . . . . . . . . . . . . . . . . 11 1.1.7.1 MAGNET and File Transfer Facility (FTF) . . . . . 11 1.1.7.2 Asynchronous Transport Package (ATP) . . . . . . . 13 1.1.7.3 19.2K BPS Support . . . . . . . . . . . . . . . . 13 1.1.8 HARDWARE . . . . . . . . . . . . . . . . . . . . . . 13 1.1.8.1 Terminals . . . . . . . . . . . . . . . . . . . . 13 1.1.8.2 MCS Board . . . . . . . . . . . . . . . . . . . . 14 1.1.8.2.1 When Upgrading from 8.4D and Below . . . . . . . 14 1.1.8.2.2 MCS Revision "S" . . . . . . . . . . . . . . . . 14 1.1.9 Miscellaneous . . . . . . . . . . . . . . . . . . . 14 1.2 FOR MPX 9XXX SERIES SYSTEMS ONLY . . . . . . . . . . . 15 1.2.1 UTILITIES . . . . . . . . . . . . . . . . . . . . . 15 1.2.1.1 UPDATE.WCS . . . . . . . . . . . . . . . . . . . . 15 1.2.2 DUMPS . . . . . . . . . . . . . . . . . . . . . . . 15 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB059 Pg001 1.2.3 HARDWARE . . . . . . . . . . . . . . . . . . . . . . 15 1.2.3.1 IMLC in MPx 9xxx Series Systems . . . . . . . . . 15 1.2.3.2 Excessive Cache Errors . . . . . . . . . . . . . . 15 1. WARNINGS AND SPECIAL CONSIDERATIONS 1.1. FOR ALL MPX SERIES SYSTEMS 1.1.1. OPERATING SYSTEM {PJON} 1) SPR 518490 - The 'AC' tape loader for 9400 systems displays 'AT' on the terminal screen during an ALT LOAD. This problem will be fixed in the next BOSS/VS release. 2) SPR 518642 - Certain large MPx configurations may experience an "Insufficient Special Shadow" system dump. This problem will be fixed in the next BOSS/VS release. A 9/8.6C patch for this problem is available upon request from Field Product Support. 1.1.1.1. Different O.S. Levels in Adjacent Slots Positioning of the O.S./WCS slots has been adjusted slightly on O.S. levels 9/8.6C in preparation for future MPx enhancements. Therefore, previous O.S. levels cannot reside in slots on the same disk with O.S. levels 9/8.6C. 1.1.1.2. SECURITY.DATA File The SECURITY.DATA file is converted to a new format during an upgrade to 9/8.6C. This converted SECURITY.DATA file cannot be used on previous O.S. levels. Therefore, the SECURITY.DATA file should be saved on the previous release before upgrading. In the event of an O.S. downgrade, this old SECURITY.DATA file must be restored on the previous O.S. level. 1.1.1.3. Operating System Downgrade Although it is not expected that downgrades from 9/8.6C will be necessary, the following downgrade procedure is documented because it differs from downgrades on previous release levels. Because of changes in the slot sizes and the new format of the SECURITY.DATA file on 9/8.6C, the following special steps must be taken in the event of a downgrade from this release: 1. Do an ALT LOAD from the release tape of the older O.S. 2. Rewrite the volume label in a TYPE 3 LOAD (Option 1 of INITIALIZATION OPTIONS). The defaults may be used, if applicable. NOTE: If the pack has a "Master" status, it must be changed to a "Backup" status to rewrite the volume label (Option 4 on the TYPE 3 LOAD main menu). The pack should be changed back to reflect a "Master" status after the volume label is written. Failure to rewrite the volume label will result in a dump on a system load. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB059 Pg002 3. Change the System Prefixes to reflect the older O.S. (CHANGE INSTALLATION PARAMETERS, Option 4 of INITIALIZATION OPTIONS.) 4. Restore the O.S. from the release tape of the previous release. 5. The 9/8.6C SECURITY.DATA file is not transportable to previous releases. Therefore, you must restore the .SYSDATA.SECURITY.DATA file used on the previous O.S. level. (This file should have been saved prior to the upgrade to 9/8.6C. If this file was not saved on the previous release, enter a TYPE 2 LOAD, DELETE the .SYSDATA.SECURITY.DATA file, enter a TYPE 1 LOAD, and recreate all accounts used on the system.) 6. Update the remaining O.S. and WCS slots with the files from the previous release, using UPDATE.OS and UPDATE.WCS. Processing can now continue. NOTE: The location of the File System start sector has not been changed. Therefore, it is not necessary to initialize the directory and restore the user's files from a backup (unless you are downgrading to 8.4D or below, in which case you must tranfer the user's files with EXTTAPE). A backup is recommended prior to the downgrade, however, as a precaution. 1.1.2. COMMAND LANGUAGE 1.1.2.1. START Command SPR 514159 - One account is able to START an account on another terminal with higher privileges than itself, as long as the accounts have the same User Level. 1.1.3. UTILITIES SPR 515010 - When QUIET=T (or QUIETON) and an output file are specified in a utility command, and the utility encounters an error, the error will not be written to the output file. 1.1.3.1. CONFIG.MGR 1) A configuration record can only be installed from an account with a USER LEVEL of 3. 2) Printer output cannot be directed to a specific printer. All output goes to P*. 1.1.3.2. DELETE, CREATE, RENAME RSC 516539 - A user is allowed to delete a file that is opened by others through the use of the DELETE, CREATE, and RENAME utilities. The RSC requests that users be notified if they are about to delete an "in use" file and be given the option of cancelling the delete. 1.1.3.3. DISKANALYZER SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB059 Pg003 1) A "File not lockable - opened by others" message will be returned by DISKANALYZER when the file is not open if the following 3 conditions are true: a) the file is a Multi-key file, AND b) the file name contains a "%", AND c) the user is running DISKANALYZER Option 3, "Validate Files". The best workaround for this problem is to run DISKANALYZER Option 2, "Validate/Reconstruct a File" on the files that return the "File Open" error. This problem does not exist when a file is validated separately. If Option 2 returns the "File open" error, then the file is truly open. This problem will be fixed in the next BOSS/VS release. 2) SPR 517795 - DISKANALYZER will sometimes corrupt a Multi- key file in such a way as to prevent BASIC SETFIELD from working. The only workaround is to restore the file from a backup. This problem will be fixed in the next BOSS/VS release. 1.1.3.4. FAMILY 1) SPR 507152 - Disk numbers of the first multi-volume family created are used as defaults for subsequent families, if the subsequent families are created without exiting the FAMILY utility. The workaround for this problem is to exit the FAMILY utility after each multi-volume family is created. 2) SPR 507151 - When creating volume labels using the FAMILY utility (Option 4), the volume type (System or Data) of the first disk is retained as a default when creating volume labels for subsequent disks. However, if this default value is used (by pressing ), the volume label will not be updated with this default value for volume type, even though it displays this way on the screen. The workaround for this problem is to always key in "S" for System disk and "D" for Data disk, and never take the default for volume type. 1.1.3.5. GETDEVINFO GETDEVINFO does not return information on Batch jobs. 1.1.3.6. JOB MANAGER 1) Defined GROUPS are deleted at system reload. Job Groups to be kept on a more or less permanent basis should be created via commands entered in the System Startup command file, .SYSDATA.START.CMD. 2) JOB.CREATE does not allow the PAUSE=TRUE parameter to be passed. If the command is embedded in a program, all errors must be handled by the application. 3) BATCH jobs require an output file which is not automatically deleted. The user may need to delete these files on a regular basis to keep disk space available. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB059 Pg004 4) The FID (0) is a file for a BATCH job. This is done by design so that a BASIC program can be run in BATCH mode. 5) Quotes must be used around the user accounts when specifiying more than one user account in the GROUP.CREATE and GROUP.MODIFY parameter lines. (Example: GROUP.CREATE MYGROUP, TYPE=TERMINAL, PRIORITY=3, USERS="GROUP1.*, GROUP2.*") 6) RSC 511490 - If PRIORITY is not specified for TERMINAL and BATCH type jobs, the PRIORITY will default to 1. This default, although proper for BATCH type jobs, is normally too low for TERMINAL type jobs. It is recommended that a PRIORITY of 3 be specified for TERMINAL type jobs during GROUP.CREATE. (See example in item 5.) 7) RSC 511491 - The PRIORITY of SYSTEM type jobs cannot be changed, even though GROUP.MODIFY appears to allow the user to do this. 8) RSC 511491 - SYSTEM type jobs cannot be deleted, nor can they be modified. GROUP.MODIFY appears to allow the user to modify SYSTEM type jobs, but such modifications are not enforced. 9) SPR 518491 - If a user renames a .SYSLOG. file, changing the string length, and leaves the file in the .SYSLOG. node, the system will dump with the fourtuples 2,10,20,11 (Instruction Fault in Job Manager Module) and 1,146,0,11 while initializing Job Manager when entering a TYPE 1 LOAD. If a user encounters this problem, he should enter a TYPE 2 LOAD and delete the .SYSLOG. files. (These files will be recreated on a TYPE 1 LOAD.) Users should be advised not to rename .SYSLOG. files, or, if they do, to rename them back before they load the system. This problem will be fixed in the next BOSS/VS release. 1.1.3.7. RECONSTRUCT SPR 517822 - Direct and Multi-key files can be corrupted if the RECONSTRUCT utility runs out of disk space. In this case, the DIR utility will show good integrity for the file, but any access of the file (including DISKANALYZER) will cause an Instruction Fault/Nil Pointer system dump. Before using the RECONSTRUCT utility, make sure there is sufficient disk space available. Please see Field Bulletin #473 for further information. This problem will be fixed in the next BOSS/VS release. 1.1.3.8. SAVERESTORE 1.1.3.8.1. Restoring ISDC Code Files and REMIDI 1) On 8.5C/9.5C the three ISDC code files (ETWYOS, FOWYOS, SXTNOS) and the REMIDI files were changed to be unorganized (UNO) file types. This was done so DISKANALYZER would no longer flag these files as having an internal file problem. Files that are typed as unorganized were not supported by SAVERESTORE and the File System in releases prior to 8.5C/9.5C, so these files are rejected when an attempt is made to restore SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB059 Pg005 them on prior O.S. levels. This is why an ALT LOAD from tape must be done before the O.S. files are restored when upgrading a system that is currently on a release prior to 8.5C/9.5C. (The only exception to this is an upgrade from 8.4E. The same changes to the above 8.5C/9.5C files were also made to the 8.4E files.) 2) SPR 517308 - On 1/2-inch tape drives, if a user does a SAVERESTORE restore or compare, and he must mount a new reel to start or continue the restore/compare, a "Tape drive offline" message is displayed on the mount menu. The workaround is to just enter a when the message occurs and continue. This problem will be fixed in the next BOSS/VS release. 3) SPR 519167 - If the VERIFY option is on, and MBIII is pressed to skip a file that spans 2 tapes, SAVERESTORE returns the message 'SECTOR COUNT MISMATCH, CANNOT RESTORE'. The workaround is to ignore the message, press , and select option 9 to mount the next tape. This will be fixed in a future BOSS/VS release. 1.1.3.9. SECURITY 1) SPR 517425 - When the System Prefix is included in an account's prefix list (using the SECURITY utility), a PPUSH or PPOP will cause extra System Prefixes to be appended on the end of the account's prefix list. Eventually, this causes the system dump 2,10,5,32, with the secondary fourtuple 1,240,0,32, due to the prefix list being too long. This problem will be fixed in the next BOSS/VS release. 2) SPR 518786 - The message "Record not found" will be returned by the SECURITY utility when using the LIST ACCOUNTS option, if the following steps are performed in sequence: a) The LIST ACCOUNTS option is selected specifying all MINOR ACCOUNTs under a specific MAJOR ACCOUNT name (using '*' for MINOR ACCOUNT) and ATTRIBUTES = YES. b) After the above accounts are listed, the LIST ACCOUNTS option is selected again, and one particular MINOR ACCOUNT name is specified from the group of accounts that was listed in a). "Record not found" will now be displayed. The workaround is to exit and re-enter the SECURITY utility after step a). This problem will be fixed in the next BOSS/VS release. 3) SPR 518812 - SECURITY.UPDATE allows a user with no password to be updated to any user level (0-3). This problem will be fixed in the next BOSS/VS release. 1.1.3.10. SPOOLER 1) SPR 509923 - The FORM utility does not allow over 14 individual printers to be entered for a specific form. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB059 Pg006 2) The SPOOLER NOTIFY function, which broadcasts a message to the top of a terminal screen when a print job has finished, will cause the screen to scroll if the cursor is on the last line of the screen. 3) SPR 514941 - Although SPOOLON appears on the SUBMIT screen and is documented in the user manuals, it does not RESERVE a printer on MPx 9/8.6 systems. The RESERVE command should be used instead. References to SPOOLON for MPx systems will be removed from the manuals in the next revisions. 4) SPR 517645 - Serial printers configured as DMP serials may hang while printing long print jobs. The Spooler status will show "PRINTING", but the number of pages and percent done never change. The printer will remain in a hung state until the user does one of the following: a) Perform a DOWN.LOAD. The job will then continue to print, but the buffered data will be lost (up to 132 lines). b) Reload the system. The print job will then continue without loss of data. An ISDC O.S. patch is available for this problem from Field Product Support upon request. This problem will be fixed in the next BOSS/VS release. 5) SPR 518108 - Cancelled spool jobs created from BASIC are removed from the queue, but the spool file remains on disk. It is, therefore, necessary to periodically delete the .SPL. node after the user has verified that all desired print jobs have completed. This problem only occurs on 9/8.6C. It will be fixed in the next BOSS/VS release. 6) SPR 518186 - If a major or minor account name exceeds 15 characters, and a spool job is submitted from that account, the system will dump with the fourtuples 2,10,33,11 (Instruction Fault in Spooler Module) and 1,242,0,11 when the spool job is accessed. To avoid the problem, do not have a major or minor account name with more than 15 characters. This problem will be fixed in the next BOSS/VS release. 7) SPR 518994 - Restarting a spool job on a spool record that is greater than 247 bytes causes system dump 2,10,33,32 (Instruction Fault in Spooler Module) and 1,242,0,32 (String Limit Exceeded). The workaround is to start the spool job at the beginning, not from where it left off. If this dump occurs on a TYPE 1 system load, the REQUESTS file should be deleted in a TYPE 2 LOAD, and the system reloaded again. (Any spool jobs that were in the deleted REQUESTS file need to then be SUBMITted manually.) This problem will be fixed in the next BOSS/VS release. 8) SPR 518718 - Restarting a print job after the TIME option has been modified may cause the job to have a "Deferred" status, even after the time to print has passed. The workaround is to cancel the job and resubmit it. This SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB059 Pg007 problem will be fixed in the next BOSS/VS release. 9) SPR 519093 - If the system is reloaded when there are P* requests in the REQUESTS file (spool queue), and PRSTATUS is executed after the reload, the system will dump with the fourtuples 2,10,33,11 (Instruction Fault in Spooler Module) and 1,146,0,11 (Range Violation). The workaround is either to route all print requests to a specific printer, or be sure there are no P* requests in the REQUESTS file when the system is taken down. If the dump occurs, the REQUESTS file should be deleted and the system reloaded. Any jobs that were left in the spool queue should be printed using the SUBMIT utility. This problem will be fixed in the 10.6E. 1.1.3.11. EXTTAPE EXTTAPE does not support PSAVEd programs. However, it gives an erroreous "End of Tape" message when it encounters a PSAVEd program (SPR 509607). 1.1.3.12. TERM.TABLE SPR 502408 - When using the copy option of TERM.TABLE (Option #4) to copy the Primary file to the Secondary file, the copy is not successful. The workaround is to copy the Primary to the Secondary again without exiting the TERM.TABLE utility. The COPY will be successful the second time. 1.1.3.13. UPDATE SPR 505144 - When expanding a file, the screen display exceeds 100%. 1.1.3.14. MCSI All filelist access must be made by a user with File Security Override set to TRUE. 1.1.4. LOGON RSC 507496 - The message "Logon disabled at this terminal, 'CR' to continue:" is displayed after a system load, if a the logon is attempted when the System Startup command file has not completed execution. Enter 'CR' and the Logon should then be enabled. 1.1.5. BASIC 1.1.5.1. STATUS SPR 511886 - The use of "STATUS" to report DSR and CTS to BASIC does not work. This problem will be fixed in an upcoming release. 1.1.5.2. Running SORT from BASIC If the SORT utility has been executed from BASIC, and it encounters an error, BASIC will always return an error 0. 1.1.5.3. Terminal Echo SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB059 Pg008 SPR 513998 - Terminal echo is lost when some unsupported utilities (e.g. HEADS) are called from BASIC. 1.1.5.4. MTCS (MCS) Tape Drive An MTCS (MCS) tape drive cannot be accessed through BASIC. This was done by design, due to considerable differences in programming such devices verses 1/2-inch tape devices. 1.1.5.5. Program File Compatibility The significant enhancements of Business BASIC 86 introduced in 9.6/8.6 will restrict backward compatibility. Programs written or modified on 9.6/8.6 will not run on prior releases without recompilation. In addition, new Business BASIC 86 features introduced in 9.6/8.6 cannot be used in programs which will be run on 9.5/8.5 or 8.4 release levels. Intersystem transport packages or the CONVERTSP utility can be used to recompile programs written or modified on 9.6/8.6, provided the new BB86 features have not been used. In most cases, where you used SAVERESTORE for tape transfer of programs to an 8.5 system, you would use EXTTAPE instead. EXTTAPE will recompile the programs as they are being transported. (All tape transfers from the new file system to the old file system require EXTTAPE.) 1.1.5.6. CONSOLELOCK The system will log a user off while in BASIC CONSOLELOCK if both of the following 2 conditions are met: a) An END, STOP, or ESCAPE directive has just been executed in the BASIC program, and b) You enter carriage return or an invalid password 3 times. This is according to design. 1.1.5.7. MAI OFFICE Time-Out Changes to the BASIC TIM= function cause MAI OFFICE to log the user off the system after 4 1/2 minutes, even if TIM= is set for a longer period of time. This occurs on 9/8.6C only. An ISDC O.S. patch is available for this problem from Field Product Support upon request. This problem will be fixed in Presentation Services in the next BOSS/VS release. 1.1.6. FILE SYSTEM 1.1.6.1. Multi-Key Files 1) The following utilities will not operate on Multi-Key files: BCOM, BQR, CREATE, EDIT, EXTTAPE, FILESIZE, FTF, GSR, MCSI, NFSCONVERT, OLDDIR, OLDTAPE. 2) SPR 507831 - Two fields occupying the same space in a data record cannot both be keysets. 3) SPR 517631 - Sometimes a hang condition may occur when accessing a Multi-Key file. Subsequent accesses of that file by other processes will result in hanging of those processes also. A system load is necessary to release SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB059 Pg009 the hung processes. This problem will be fixed in the next BOSS/VS release. 1.1.7. COMMUNICATIONS 1.1.7.1. MAGNET and File Transfer Facility (FTF) 1) There is no automatic conversion of topology config- uration files to the new Network Management Facility (NMF) configuration files when 9.6/8.6 is installed on an MPx system previously configured for B4NET/FTF. The user is responsible for printing the previous configuration information before re-configuring the MAGNET and/or FTF network with NMF or EZCONFIG. 2) A reboot is necessary after the initial configuration of each system in the MAGNET/FTF network. Any subsequent modifications to the home station parameters or subnetwork numbers also require a reboot to activate the changes. 3) Care must be taken to configure enough SVC's to support all remote concurrent activities; the number of remote X.25 sites accessed at any time cannot exceed the number of SVC's configured for the X.25 link; each FTF file transfer will require its own SVC. 4) FTF file transfers may experience Completion Code 149's (Network Services Timer Expired) when the system or network load is heavy, or when communicating over a LAN/WAN internetwork. 5) FTF file transfers via LAN are only allowed between MPx systems. 2000/3000 systems may not co-exist on the same LAN network as MPx systems. FTF file transfers are allowed to unlike systems (MPx, 2000/3000, 13xx) over X.25 links; however, automatic data conversion for unlike character sets is NOT performed. The Intersystem Transport program, FTFIT, must be used for data conversion of FTF file transfers between unlike systems. 6) Three types of X.25 packet data switches were used during the test cycle: o Memotec 8500 o Dynapac Model 8 o Dynapac Model 12 Results of the testing showed that the Memotec 8500 should only be used for networks which have a low load or when performance is not a factor. The Dynapac Model 8 can handle heavier network load but the baud rate is limited to 9600 BPS. The Dynapac Model 12 is recommended for networks with heavy loads - up to 7 MPx systems at 19.2K BPS using 128 byte packets. A problem where the Dynapac Model 12 went into a 'lockup' mode was found when running 5 or more systems at 19.2K BPS and using 256 byte packets. To prevent this problem, the packet size should be reduced to 128 bytes. (The Dynapac Model 12A is recommended over the Dynapac Model 12 to avoid MAGNET errors due to "restarts") SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB059 Pg010 7) To optimize throughput of X.25 communications, it is recommended that the IMLC be configured with X.25 on port A and nothing on Port B. This configuration will allow running at baud rates of 9600 BPS and above, and configuring more SVC's and larger data packet sizes. Other IMLC products such as 27xx/37xx, 3270, and Dataword should be configured on another IMLC. 9/8.6 supports up to 4 IMLC boards. 8) LAN/WAN internetworking has a significant impact on the gateway system. For this reason, the largest and/or least busy system on the subnetwork should be configured as the gateway system. The minimum system type for a gateway should be an 8030 if possible. 9) A maximum of 63 systems may exist on a MAGNET LAN network. However, performance degradation will occur when more than 8 systems are actively transmitting data, especially during file copies. 10) MAGNET event logs are initially set in the GROUP utility to LOGFILES=10 and LOGRECS=100. Although these parameters are normally sufficient, depending on network activity the event log sizes may have to be increased. To increase the size, modify the .SYSDATA.START.CMD file to include the command: GROUP.SETLOG MAGNET,LOGFILES=n,LOGRECS=n,VERIFY=FALSE where 'n' is the number desired; recommended values are LOGFILES=25 and LOGRECS=200. The logfiles will be increased with the next reboot of the system. If you wish to increase the logfiles on a temporary basis, the logfile parameters can be modified through the JOB MANAGER utility. The modifications will take effect immediately but will stay in effect only until the system is rebooted. 11) If MAGNET is installed on a system already running in production mode, some degradation may be experienced. If this occurs, the system should be upgraded in terms of memory and/or CPU. 1.1.7.2. Asynchronous Transport Package (ATP) ATP 4.0 will be the ATP release available for 9/8.6. ATP 4.0 provides new features such as autodial, scheduler, line turn-around, and performance enhancements. ATP 4.0 is NOT compatible with previous releases of ATP; all systems communicating with ATP 4.0 systems must also upgrade to 4.0. 1.1.7.3. 19.2K BPS Support TERM.CONFIG permits configuration of 8-Way and 16-Way ports with a BPS of 19.2K. See the section on 19.2K BPS in the 9.6A/8.6A Software Announcement for guidelines on configuration cautions in regard to aggregate ISDC throughput. 1.1.8. HARDWARE SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB059 Pg011 1.1.8.1. Terminals 1) Very fast typing may cause DT-4312 terminals to drop characters. This occurence is rare. 2) In order to use a standard MBF printer as a slave off a DT-4313 terminal, the terminal must have REV E firmware. If the DT-4313 terminal does not have REV E firmware, only screen dumps can be printed. 1.1.8.2. MCS Board 1.1.8.2.1. When Upgrading from 8.4D and Below When upgrading from 8.4D or below to 8.6/9.6, it is essential that the 4-Way (MCS board) be enabled (SW1 position 3). Not doing so will result in a dump with the fourtuple 11,13,0,0 occurring when attempting to enter a TYPE 3 LOAD after the update of slot 0. 1.1.8.2.2. MCS Revision "S" MCS PCBA PN 903374-001 at revision "S" now has the ability to be switch selectable (SW1-4) to match the different address schemes between MPx 7xxx/8xxx Series Systems and MPx 9xxx Series Systems. The "S" revision level is not mandatory for the function of either system. MCS revision "S", when used in MPx 7xxx/8xxx Series Systems, must be set for MPx 7xxx/8xxx systems. Failure to do so will cause the system load to abort with BOOT STRAP ERROR "FFFF". MCS revision "S" used in MPx 9xxx Series Systems, (when switch selected for MPx 9xxx systems), will allow any controller to be board addressed from the range of 1 to 63 (the board address of 16 through 31 are not valid on MPx 9xxx Series Systems; do not address PCB's in these ranges). If set for MPx 7xxx/8xxx Series Systems and used in MPx 9xxx Series Systems, the board addresses of 32 thru 47 may only be used for the IMLC PCB. There will also be no support for memory above 12 megabytes. (Revision "T" is required for support of more than 12 megabytes of memory.) The following are the switch settings for revision "S" or above MCS board: Switch SW1-4 open: MPx 7xxx/8xxx Series Systems Switch SW1-4 closed: MPx 9xxx Series Systems 1.1.9. Miscellaneous MAI BUSINESS GRAPH: A range violation (1,228,0,11) will occur if an attempt is made to print Pies and Stack Bars with MAI BUSINESS GRAPH version 3.1A on 9/8.6C. This problem will be fixed in MAI Business Graph 3.2B. 1.2. FOR MPX 9XXX SERIES SYSTEMS ONLY 1.2.1. UTILITIES 1.2.1.1. UPDATE.WCS SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB059 Pg012 SPR 517589 - UPDATE.WCS does not update the Load Directory on 9xxx systems. The workaround is to run UPDATE.LD to update the Load Directory after running UPDATE.WCS. This problem will be fixed in the next BOSS/VS release. 1.2.2. DUMPS Because the BMTC is a shared memory controller, it is not possible to direct a dump to a tape drive connected to a BMTC. On systems where a BMTC is the only tape controller, it is essential that the dump area on disk be large enough. See Field Bulletin #211, "Computing the Dump Area Size on MPx Systems", for further information. 1.2.3. HARDWARE 1.2.3.1. IMLC in MPx 9xxx Series Systems 1) The Memory Map Controller board numbers of the IMLC's must be in the range 32-47. If Revision level "S" or above of the MCS board is used and set for MPx 9xxx Series Systems, this restriction is removed. See the information on the MCS board in this section. 2) The "JMP C" self test jumper should be installed on the IMLC PCBA's. This is a hardware requirement for 9xxx systems only, and it is not related to the 9.6/8.6 O.S. level. For . further information on this jumper, see the Field Bulletin titled "MPx 8xxx to 9xxx Upgrade IMLC NOT RECOGNIZED". 1.2.3.2. Excessive Cache Errors SPR 517452 - Excessive cache errors are logged in the ERRORLOG at load time for the non-I/O CPU if its AMS board P/N 903548 is not -003. Any cache parity errors on the non-I/O CPU during system load should be ignored. This problem is fixed in the Advanced Series. The fix for 9xxx systems is upcoming, and will most likely be an ECN to the IDC-64 board. Please see the Field Bulletin titled "MPx Cache Errors with 9.6C and -001/-002 AMS PCBA" for additional information. ORIGINATOR: N. Prentiss SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB059 Pg013 FIB 00060 12/19/88 *** Ghost Task not Released - BCOM at n.6B/C [ WPSF 483 ] *** PROBLEM: When BCOM is run in a ghost task on levels 8/9.6B or 8/9.9C, the ghost is not released when the session is complete. SOLUTION: Modify statements 240, 305, and 311 in program BCOM. Add the underlined portions. 240 READ(2,ERR=260,KEY=FID(0))T$,*,P$ 305 BEGIN EXCEPT P$, C5$, G$, T$; REM ... 311 IF G$="G" THEN RELEASE T$ ORIGINATOR: T. Tiangco SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB060 Pg001 FIB 00061 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/VS BBVIII & BBIX-----------FIB061 Pg001 FIB 00062 12/22/88 *** 9xxx System Hangs While Running DOWN.LOAD - 9.6A/B [ WPSF 443 ] *** A problem has been discovered which may cause an MPx system to hang when running the DOWN.LOAD utility. This problem has only been seen on the MPx 9000 and 9500 series systems with Operating System levels 9.6A and 9.6B. This problem is fixed in 9.6C. There are two things that may be tried as a workaround if running DOWN.LOAD has been required and system hangs have resulted. The first thing to try is to set the priority of the task running DOWN.LOAD to high (6) by using !JOB MODIFY. Another workaround is to keep track of how long the down load is in progress. If the down load is taking more than 30 seconds, then abort the process by depressing the escape key several times. A second attempt to down load the controller should complete successfully. NOTE: Frequent down loads to the same controller may indicate a "hardware problem" with that controller or a device connected to it. ORIGINATOR: D. Jensen SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB062 Pg001 FIB 00063 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/VS BBVIII & BBIX-----------FIB063 Pg001 FIB 00064 12/28/88 *** Use EXTTAPE for Config Records below 8/9.6A [ WPSF 505 ] *** Because of recent changes in the File System, configuration records created on releases 10/9/8.6E and above for releases below 9/8.6A must be transported with EXTTAPE. Configuration records created for 10/9/8.6 levels may still be transported with SAVERESTORE. Tapes containing configuration records saved with EXTTAPE will be labeled "Restore with EXTTAPE". If you receive transmitted 9/8.5 & 8.4E configuration records that are created . on O.S. levels 10/9/8.6E and above they must be transported with EXTTAPE. There may be a few 9/8.5 & 8.4E configuration records sent out that were created on 9.6E and saved with SAVERESTORE. These config records cannot be used. SAVERESTORE will return the following message at the end of the restore of such configuration records: "FILE HAS INVALID FORMAT. USE DISKANALYZER TO RECONSTRUCT." The file will be restored, but any access of the file will return the same message. DISKANALYZER will not correct the problem. A new configuration record must be ordered from Software Distribution. ORIGINATOR: N. Prentiss SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB064 Pg001 FIB 00065 12/28/88 *** System Hang/Dump Recovery Procedures [ WPSF 506 ] *** This procedure should be followed after a system dump or a system load due to a system hang. Step 1) After the dump is completed, reload system and enter a Type II load. Choose the option DISKANALYZER. The DISKANALYZER main menu will appear. Step 2) First check the directory and the available space. Choose option 6 "CHECK DIRECTORY AND AVAILABLE SPACE FILES". Each family needs to be checked. If errors are reported, that directory and available space will need to be reconstructed (this operation is explained in step 4). Step 3) Check for overlapping or missing space by choosing option 5 "DISK SPACE USAGE" (SPACE MISSING/OVERLAPPING)". If the option reports that space is missing, then the available space file must be reconstructed to reclaim. that space. If 2 or more files are overlapping, then certain actions must be taken to resolve the conflict. To fix this, do the following steps: A) Make a backup of the system (just in case). B) Only one of the overlapping files can exist in that filespace. First you have to determine which files are not the proper owner. Use option 2 "VALIDATE/RECONSTRUCT A FILE". It is possible that the files are not bad and can be saved by copying the files to a new location (another disk or tape) and deleting its source. If not, then delete the files that do not own the filespace. C) The available space file will have to be reconstructed. (This is explained in step 4). D) After reconstruction, recheck the directory and available space files using options 5 and 6. Repeat steps B, C, D as necessary. Step 4) Steps 2 and 3 will identify any problems with the directory and the available space files. If the files are reported to have problems, they must be reconstructed before processing can continue. If both the directory and the available space must be reconstructed, the available space file MUST be reconstructed first. To reconstruct the available space file, choose option 9 "RECONSTRUCT AVAILABLE SPACE FILES (TYPE II LOAD)". To reconstruct the directory, choose option 10 "RECONSTRUCT DIRECTORY FILE (TYPE II LOAD)". Step 5) Next, the files must be validated. To do this use option 1 "FIND FILES THAT LACK INTEGRITY". This option will find any files that have the integrity flag set. This option does not check the file structure, only the integrity flag. If persistant problems with file corruption occur, then use option 3 "VALIDATE FILES". This option provides a very thorough check of each file's internal structure. Step 6) The files found to have problems from step 5 must be fixed. Files critical to the operation of the system and the application should be fixed using option 2 "VALIDATE/RECONSTRUCT A FILE". Files that are not critical should be reconstructed in a Type I load. This will allow you to start reconstruction on multiple terminals. Step 7) Enter a Type I load. Reconstruct the files not reconstructed in step 6. Keyed (DIRECT, SORT, MULTIKEY) files should be reconstructed FIRST using SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB065 Pg001 the RECONSTRUCT utility. This utility is faster than DISKANALYZER. If RECONSTRUCT cannot fix the file, then DISKANALYZER option 2 must be used to repair the file. Serial and indexed files are repaired using DISKANALYZER. ORIGINATOR: R. Case SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB065 Pg002 FIB 00066 02/08/89 *** Release 10.6E/9.6E/8.6E Software Announcement [ WPSS 161 ] *** MAI Basic Four, Inc. is pleased to announce that the new system software revisions, 10.6E/9.6E/8.6E, are now available. The 10.6E revision is the required revision for the ADVANCED SERIES family. The 9.6E revision is the recommended revision for MPx 9xxx Series Systems. The 8.6E revision is the recommended revision for MPx 7xxx and 8xxx Series Systems. There were no 9.6D/8.6D system software revisions. **************************************************************** * * * o As of release 9/8.6C, positioning of the image slots has * * been adjusted slightly. Therefore, O.S./WCS levels * * previous to 9/8.6C cannot reside in slots on the same disk * * with release levels 9/8.6C and above. * * * * o As of release 9/8.6C, T0 must be a model 4309 or later * * terminal on all systems, or an HVDT on 7xxx/8xxx/9xxx * * systems. * * * * o High Speed terminals (and the VCON controller board) are * * not supported on ADVANCED SERIES. * * * * o As of release 9/8.6C, the .SYSDATA.SECURITY.DATA file is * * not transportable to previous release levels. Therefore, * * if you are upgrading to 10/9/8.6E from a release prior to * * 9/8.6C, this file should be saved before the upgrade, for * * fall-back purposes. * * * * o Files transferred from 10/9/8.6E to O.S. levels below * * 9/8.6A must be transported with EXTTAPE, MCSI, FTF, TBC, * * or ATP. If a downgrade is performed from 10/9/8.6E to a * * release prior to 9/8.6A, the user's files must be * * transported to the older O.S. level with one of the above * * utilities. * * * * o Horizontal software such as PRESENTATION SERVICES, GRAPH, * * and ORIGIN typically have files that reside in the .SYS. * * node. These files need to be transferred to the new .SYS. * * node on an O.S. upgrade, either by using the COPY utility * * or by reinstalling the software. * * * * o The 10/9/8.6E Software Announcement exists as a serial * * file on the O.S. release tape. To print a copy on 10/9/8.6 * * systems, submit the following file to the printer: * * * * .R6E15.INST.DOC.ANNOUNCE6E * * * **************************************************************** Copyright 1988, Rev. 1988, MAI Basic Four, Inc. All rights reserved. C O N T E N T S _ _ _ _ _ _ _ _ 1 IMPORTANT NOTE ON THE *15 RELEASE . . . . . . . . . . . 2 2 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . 3 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg001 2.1 ENHANCEMENTS IN THIS RELEASE . . . . . . . . . . . . . 3 2.2 CONFIGURATION RECORD CONSIDERATIONS . . . . . . . . . 4 2.3 SOFTWARE ANNOUNCEMENT . . . . . . . . . . . . . . . . 4 3 FIXES IN THIS RELEASE . . . . . . . . . . . . . . . . . 5 3.1 BOSS/VS . . . . . . . . . . . . . . . . . . . . . . . 5 3.1.1 OPERATING SYSTEM . . . . . . . . . . . . . . . . . . 5 3.1.2 COMMAND LANGUAGE . . . . . . . . . . . . . . . . . . 5 3.1.2.1 START Command . . . . . . . . . . . . . . . . . . 5 3.1.3 UTILITIES . . . . . . . . . . . . . . . . . . . . . 5 3.1.3.1 DISKANALYZER . . . . . . . . . . . . . . . . . . . 5 3.1.3.2 JOB MANAGER . . . . . . . . . . . . . . . . . . . 5 3.1.3.3 RECONSTRUCT . . . . . . . . . . . . . . . . . . . 6 3.1.3.4 SAVERESTORE . . . . . . . . . . . . . . . . . . . 6 3.1.3.5 SECURITY . . . . . . . . . . . . . . . . . . . . . 6 3.1.3.6 SPOOLER . . . . . . . . . . . . . . . . . . . . . 6 3.1.3.7 UPDATE.WCS . . . . . . . . . . . . . . . . . . . . 7 3.1.4 BASIC . . . . . . . . . . . . . . . . . . . . . . . 7 3.1.5 FILE SYSTEM . . . . . . . . . . . . . . . . . . . . 8 4 BOSS/VS . . . . . . . . . . . . . . . . . . . . . . . . 9 4.1 UTILITIES . . . . . . . . . . . . . . . . . . . . . . 9 4.1.1 ERRORLOG Utility Enhancements . . . . . . . . . . . 9 4.2 AUDITOR'S LOGBOOK . . . . . . . . . . . . . . . . . . 14 4.2.1 General Information . . . . . . . . . . . . . . . . 14 4.2.2 Disk Space Usage . . . . . . . . . . . . . . . . . . 16 4.2.3 System Performance . . . . . . . . . . . . . . . . . 16 4.2.4 DISKANALYZER Considerations . . . . . . . . . . . . 17 4.2.5 Installing the AUDITOR'S LOGBOOK Key . . . . . . . . 17 4.3 DIAGNOSTICS . . . . . . . . . . . . . . . . . . . . . 19 4.3.1 REMIDI . . . . . . . . . . . . . . . . . . . . . . . 19 4.3.1.1 On MPx 7000, 7100, and 8000 Series Systems . . . . 19 4.3.1.1.1 Updating the Load Directory for REMIDI . . . . . 19 4.3.1.2 On MPx 9xxx and the ADVANCED SERIES . . . . . . . 21 4.3.1.2.1 Updating the Load Directory for REMIDI . . . . . 21 4.3.2 DEMON - Updating the Load Directory . . . . . . . . 22 4.3.3 ADVANCED SERIES Only . . . . . . . . . . . . . . . . 22 4.3.3.1 High Frequency Margins on the ADVANCED SERIES . . 22 4.3.3.2 Using ALT LOAD for REMIDI and DEMON . . . . . . . 23 4.4 CONFIGURATIONS . . . . . . . . . . . . . . . . . . . . 24 4.4.1 Configurations for MPx 7000/7100/8000 Series Systems 24 4.4.2 Configurations for MPx 9000/9100/9400 Series Systems 25 4.4.3 Configurations for MPx 9500/9600 Series Systems . . 26 4.4.4 Configurations for the ADVANCED SERIES Family . . . 27 4.5 BASIC . . . . . . . . . . . . . . . . . . . . . . . . 29 4.5.1 Key Words . . . . . . . . . . . . . . . . . . . . . 29 4.5.2 Easy EDIT . . . . . . . . . . . . . . . . . . . . . 29 5 HARDWARE . . . . . . . . . . . . . . . . . . . . . . . . 30 5.1 MPX 7000, 7100, AND 8000 PCBA NOTES . . . . . . . . . 30 5.2 MPX 9XXX SERIES SYSTEM PCBA NOTES . . . . . . . . . . 33 5.3 PCBA'S FOR ALL MPX SERIES SYSTEMS . . . . . . . . . . 37 5.4 ADVANCED SERIES PCBA NOTES . . . . . . . . . . . . . . 38 5.4.1 PCBA's Not Supported on the ADVANCED SERIES . . . . 40 5.5 PERIPHERAL DEPENDENCIES . . . . . . . . . . . . . . . 40 5.5.1 Tape Drives . . . . . . . . . . . . . . . . . . . . 40 5.5.1.1 GCR Tape Drive . . . . . . . . . . . . . . . . . . 40 5.5.1.2 SCSI MTCS Tape Drive . . . . . . . . . . . . . . . 40 5.5.2 Terminals . . . . . . . . . . . . . . . . . . . . . 40 5.5.3 Disk Drives . . . . . . . . . . . . . . . . . . . . 41 6 INSTALLATION . . . . . . . . . . . . . . . . . . . . . . 42 6.1 NEW FILE NAMING CONVENTION . . . . . . . . . . . . . . 42 6.1.1 File Names . . . . . . . . . . . . . . . . . . . . . 42 6.2 GENERAL INFORMATION . . . . . . . . . . . . . . . . . 44 6.3 NEW OPERATING SYSTEM INSTALLATION . . . . . . . . . . 46 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg002 6.3.1 INSTALLING THE OPERATING SYSTEM . . . . . . . . . . 46 6.3.1.1 Loading Slots 0 and 1 Using ALT LOAD . . . . . . . 46 6.3.1.2 TYPE 3 LOAD (Special Functions) . . . . . . . . . 48 6.3.1.2.1 OPTION 1 (CHANGE VOLUME LABEL INFORMATION) . . . 48 6.3.1.2.2 OPTION 2 (UPDATE FAMILY INFORMATION) . . . . . . 49 6.3.1.2.3 OPTION 3 (INITIALIZE FAMILY DIRECTORY) . . . . . 50 6.3.1.2.4 OPTION 4 (CHANGE INSTALLATION PARAMETERS) . . . 50 6.3.1.3 Restoring the O.S. . . . . . . . . . . . . . . . . 51 6.3.2 INSTALLING THE CONFIGURATION RECORD . . . . . . . . 52 6.4 UPGRADING TO 8.6E FROM RELEASE LEVELS 8.4D AND BELOW . 54 6.4.1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . 54 6.4.2 PRELIMINARY EVALUATION . . . . . . . . . . . . . . . 55 6.4.2.1 Hardware Evaluation . . . . . . . . . . . . . . . 55 6.4.2.2 File Preparation . . . . . . . . . . . . . . . . . 55 6.4.2.3 New File System Space Requirements . . . . . . . . 56 6.4.2.4 Saving Files to Tape . . . . . . . . . . . . . . . 56 6.4.3 OPERATING SYSTEM UPDATE and FILE CONVERSION . . . . 57 6.4.3.1 Installing the O.S. . . . . . . . . . . . . . . . 57 6.4.3.1.1 Loading Slots 0 and 1 Using ALT LOAD . . . . . . 57 6.4.3.1.2 TYPE 3 LOAD (SPECIAL FUNCTIONS) . . . . . . . . 60 6.4.3.1.2.1 OPTION 1 (CHANGE VOLUME LABEL INFORMATION) . . 60 6.4.3.1.2.2 OPTION 2 (UPDATE FAMILY INFORMATION) . . . . . 61 6.4.3.1.2.3 OPTION 3 (INITIALIZE FAMILY DIRECTORY) . . . . 61 6.4.3.1.2.4 OPTION 4 (CHANGE INSTALLATION PARAMETERS) . . 62 6.4.3.1.3 Restoring the O.S. . . . . . . . . . . . . . . . 62 6.4.3.2 INSTALLING THE CONFIGURATION RECORD . . . . . . . 63 6.4.3.3 CONVERTING FILES . . . . . . . . . . . . . . . . . 64 6.4.3.3.1 Tape to Disk Conversion . . . . . . . . . . . . 64 6.4.3.3.2 Disk to Disk Conversion . . . . . . . . . . . . 65 6.4.3.3.3 Check Files . . . . . . . . . . . . . . . . . . 65 6.4.4 UPDATING THE TERMINAL CONFIGURATION FILE . . . . . . 65 6.5 UPGRADING TO 8.6E FROM RELEASE LEVELS 8.4E AND ABOVE . 67 6.5.1 SAVING FILES TO TAPE . . . . . . . . . . . . . . . . 67 6.5.2 OPERATING SYSTEM UPDATE . . . . . . . . . . . . . . 67 6.5.2.1 Loading Slots 0 and 1 Using ALT LOAD . . . . . . . 67 6.5.2.2 Changing Installation Parameters . . . . . . . . . 70 6.5.2.3 Restoring the O.S. . . . . . . . . . . . . . . . . 70 6.5.3 INSTALLING THE CONFIGURATION RECORD . . . . . . . . 71 6.5.4 UPDATING SLOTS 2 AND 3 ON 7xxx and 8xxx SYSTEMS . . 72 6.5.4.1 Updating WCS Slot Two (2) . . . . . . . . . . . . 72 6.5.4.2 Updating Slot Three (3) . . . . . . . . . . . . . 73 6.5.4.2.1 Updating WCS Slot Three (3) . . . . . . . . . . 73 6.5.4.2.1.1 On 7000/7100 Systems and 8000 Systems with LAN 73 6.5.4.2.1.2 On 8000 Systems Without LAN . . . . . . . . . 73 6.5.4.2.2 Updating O.S. Slot Three (3) . . . . . . . . . . 73 6.5.5 SLOT INFORMATION . . . . . . . . . . . . . . . . . . 74 6.6 UPGRADING TO 9.6E . . . . . . . . . . . . . . . . . . 75 6.6.1 SPECIAL CONSIDERATIONS . . . . . . . . . . . . . . . 75 6.6.2 PRINTING OUT THE TERMINAL CONFIGURATION INFORMATION 75 6.6.3 SAVING FILES TO TAPE . . . . . . . . . . . . . . . . 75 6.6.4 OPERATING SYSTEM UPDATE . . . . . . . . . . . . . . 76 6.6.4.1 Loading Slots 0 and 1 Using ALT LOAD . . . . . . . 76 6.6.4.2 Changing Installation Parameters . . . . . . . . . 78 6.6.4.3 Restoring the O.S. Files . . . . . . . . . . . . . 79 6.6.5 INSTALLING THE CONFIGURATION RECORD . . . . . . . . 80 6.6.6 UPDATING SLOTS 2 AND 3 ON MPx 9xxx SERIES SYSTEMS . 81 6.6.6.1 Updating WCS Slot Two (2) . . . . . . . . . . . . 81 6.6.6.2 Updating WCS Slot Three (3) . . . . . . . . . . . 82 6.6.6.3 Updating O.S. Slot Three (3) . . . . . . . . . . . 82 6.6.7 SLOT INFORMATION . . . . . . . . . . . . . . . . . . 83 6.7 UPGRADING TO 10.6E AND THE ADVANCED SERIES . . . . . . 84 6.7.1 SPECIAL CONSIDERATIONS . . . . . . . . . . . . . . . 84 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg003 6.7.2 SAVING FILES TO TAPE . . . . . . . . . . . . . . . . 84 6.7.3 OPERATING SYSTEM UPDATE . . . . . . . . . . . . . . 84 6.7.3.1 Loading Slots 0 and 1 Using ALT LOAD . . . . . . . 84 6.7.3.2 Changing Installation Parameters . . . . . . . . . 87 6.7.3.3 Restoring the O.S. Files . . . . . . . . . . . . . 88 6.7.4 INSTALLING THE CONFIGURATION RECORD . . . . . . . . 88 6.7.5 Updating Slots 2 and 3 on ADVANCED SERIES Systems . 89 6.7.5.1 Updating WCS Slot Two (2) . . . . . . . . . . . . 89 6.7.5.2 Updating WCS Slot Three (3) . . . . . . . . . . . 90 6.7.5.3 Updating O.S. Slot Three (3) . . . . . . . . . . . 90 6.7.6 SLOT INFORMATION . . . . . . . . . . . . . . . . . . 91 6.8 UPDATING SLOTS 0 AND 1 USING UPDATE.OS AND UPDATE.WCS 92 6.8.1 Updating O.S. Slots 0 and 1 . . . . . . . . . . . . 92 6.8.2 Updating WCS Slots 0 and 1 . . . . . . . . . . . . . 92 6.9 SYSTEM STARTUP . . . . . . . . . . . . . . . . . . . . 94 6.9.1 STANDARD STARTUP COMMAND FILE . . . . . . . . . . . 94 6.9.1.1 Command File Definitions . . . . . . . . . . . . . 94 6.9.2 IMPLICATIONS . . . . . . . . . . . . . . . . . . . . 95 7 RELATED DOCUMENTATION . . . . . . . . . . . . . . . . . 98 F I G U R E S _ _ _ _ _ _ _ Figure 4-1. DOWNLOAD Detail Screen . . . . . . . . . . . . 9 Figure 4-2. New DOWNLOAD Summary Screen . . . . . . . . . 10 Figure 4-3. Fault Map Screen . . . . . . . . . . . . . . . 11 Figure 4-4. Cache Parity Errors on ADVANCED SERIES . . . . 12 Figure 4-5. Memory Error Summary . . . . . . . . . . . . . 13 Figure 4-6. Totals Summary . . . . . . . . . . . . . . . . 13 Figure 6-1. Restore Screen . . . . . . . . . . . . . . . . 52 Figure 6-2. Restore Screen . . . . . . . . . . . . . . . . 63 Figure 6-3. Restore Screen . . . . . . . . . . . . . . . . 71 Figure 6-4. Operating System Information . . . . . . . . . 74 Figure 6-5. Restore Screen . . . . . . . . . . . . . . . . 80 Figure 6-6. Operating System Information . . . . . . . . . 83 Figure 6-7. Restore Screen . . . . . . . . . . . . . . . . 88 Figure 6-8. Operating System Information . . . . . . . . . 91 1. IMPORTANT NOTE ON THE *15 RELEASE _________ ____ __ ___ ___ _______ Three problems were discovered on the ADVANCED SERIES after 10/9/8.6E *14 was officially released. These problems are now fixed in the firmware (WCS) for the ADVANCED SERIES on *15. If you are running the *14 release, and you do not have an ADVANCED SERIES, you do not need to upgrade to *15. If you do have an ADVANCED SERIES, and you are on the 10.6E *14 release, you should upgrade to 10.6E *15. If you are using this *15 Software Announcement to install the *14 release, please remember that the system prefix will be .R6E14. instead of .R6E15. In addition, the OSINFO screens documented in this *15 announcement will differ slighty from those on *14. The file names used to install the O.S./WCS slots will be the same. The three problems fixed in the WCS for the ADVANCED SERIES are: 1) A CPU would sometimes go offline during the initialization SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg004 phase of a system load. 2) A hang would sometimes occur on a heavily loaded system with multiple CPU's. 3) A certain invalid opcode instruction was not properly handled by the WCS, leaving the system in an unknown state. 2. INTRODUCTION ____________ 2.1. ENHANCEMENTS IN THIS RELEASE ____________ __ ____ _______ The 10.6E/9.6E/8.6E release contains the following enhancements: o Support for the new, high performance ADVANCED SERIES family. o Support for the new, high capacity, high performance 621MB fixed disk and its associated DMA-III controller. o An AUDITOR'S LOGBOOK, which allows for an optional, automatic record of updates to a file. AUDITOR'S LOGBOOK is a chargeable feature controlled by software key. o Enhancements to the hardware ERRORLOG, including: 1) a summary option added to the DOWNLOAD group; 2) the drive number added to I/O error data; 3) expanded cache error reporting to include the ADVANCED SERIES; and 4) clarification of the memory error report. o Full 7-bit/8-bit support for T0 when this release is used in conjunction with the new MCS/M board on the ADVANCED SERIES. o An enhanced UPDATE utility, which now expands files in a fraction of the time required previously. UPDATE no longer makes a copy of the entire file, but merely adds extents when an expand is specified. o High frequency margin testing for use with hardware diagnostics on the ADVANCED SERIES family. o A new INITFILE utility, which initializes a file, retaining either the same disk allocation or the primary extent only. o An enhanced BASIC EDIT directive, which allows editing of the last statement typed without specifying a statement number. o A new OS/WCS file naming convention, which uses shortened file names to simplify installation procedures. o An enhanced TASKS utility, which now refreshes the TASKS screen only when the screen changes, instead of every 2.5 seconds. This makes the screen more readable on terminals running at 1200 and 2400 baud. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg005 o An enhanced SECURITY.UPDATE utility, which allows any user to change his own password. (This enhancement was actually implemented as of 9/8.6C.) o An enhanced ALT LOAD on the ADVANCED SERIES, which allows REMIDI and DEMON to be loaded into memory from the O.S. tape and executed (1/2-inch tape only). 2.2. CONFIGURATION RECORD CONSIDERATIONS _____________ ______ ______________ In general, a new configuration record is required when upgrading to a new system type (e.g., from an 8xxx to a 9xxx system), when adding new hardware, and when upgrading to a new major release level (e.g., 8.5 to 8.6). A new configuration record is not required when upgrading from releases 9.6A/B/C to 9.6E or from releases 8.6A/B/C to 8.6E. A new configuration record is required, however, when upgrading to 10.6E. A new configuration record is also required when upgrading from 8.4 and 9.5/8.5 releases to 10.6E/9.6E/8.6E releases. 2.3. SOFTWARE ANNOUNCEMENT ________ ____________ The 10.6E/9.6E/8.6E Software Announcement exists as a serial file on the official 10/9/8.6E O.S. release tape, which allows the user to print copies, if needed. To print this document, SUBMIT the following file to the printer: (family).R6E15.INST.DOC.ANNOUNCE6E 3. FIXES IN THIS RELEASE _____ __ ____ _______ The 10/9/8.6E releases contain fixes for the following system problems: 3.1. BOSS/VS _______ 3.1.1. OPERATING SYSTEM _________ ______ 1) SPR 518490 - The 'AC' tape loader for 9400 systems would display 'AT' on the terminal screen during an ALT LOAD. 2) SPR 518642 - Certain very large MPx configurations sometimes experienced an "Insufficient Special Shadow" system dump. 3) SPR 519471 - System dump 3,12,1,11 (Chained HVDT IOCB's) would occur if the ESCAPE key was pressed on a High Speed terminal other than T0 while in a TYPE 2 LOAD. 3.1.2. COMMAND LANGUAGE _______ ________ 3.1.2.1. START Command _____ _______ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg006 SPR 514159 - One account was able to START an account on another terminal with higher privileges than itself, as long as the accounts had the same User Level. 3.1.3. UTILITIES _________ 3.1.3.1. DISKANALYZER ____________ 1) A "File not lockable - opened by others" message was returned by DISKANALYZER when the file was not open if the following 3 conditions were true: a) the file was a Multi-key file, AND b) the file name contains a "%", AND c) the user was running DISKANALYZER Option 3, "Validate Files". 2) SPR 517795 - DISKANALYZER would sometimes corrupt a Multi-key file in such a way as to prevent BASIC SETFIELD from working. 3.1.3.2. JOB MANAGER ___ _______ SPR 518491 - If a user renamed a .SYSLOG. file, changing the string length, and left the file in the .SYSLOG. node, the system would dump with the fourtuples 2,10,20,11 (Instruction Fault in Job Manager Module) and 1,146,0,11 while initializing Job Manager when entering a TYPE 1 LOAD. SPR 516691 - JOB.CREATE commands that were incorporated into the .SYSDATA.START.CMD file would not execute if the SYSTEM.MANAGER account was not present on the system. 3.1.3.3. RECONSTRUCT ___________ SPR 517822 - Direct and Multi-key files could be corrupted if the RECONSTRUCT utility ran out of disk space. In this case, the DIR utility would show good integrity for the file, but any access of the file (including DISKANALYZER) would cause an Instruction Fault/Nil Pointer system dump. 3.1.3.4. SAVERESTORE ___________ SPR 517308 - On 1/2-inch tape drives, if a user did a SAVERESTORE restore or compare, and he mounted a new reel to start or continue the restore/compare, a "Tape drive offline" message was displayed on the mount menu. 3.1.3.5. SECURITY ________ 1) SPR 517425 - When the System Prefix was included in an account's prefix list (using the SECURITY utility), a PPUSH or PPOP would cause extra System Prefixes to be appended on the end of the account's prefix list. Eventually, this caused the system dump 2,10,5,32, with the secondary fourtuple SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg007 1,240,0,32, due to the prefix list being too long. 2) SPR 518786 - The message "Record not found" was returned by the SECURITY utility when using the LIST ACCOUNTS option, if the following steps were performed in sequence: a) The LIST ACCOUNTS option was selected specifying all MINOR ACCOUNTs under a specific MAJOR ACCOUNT name (using '*' for MINOR ACCOUNT) and ATTRIBUTES = YES. b) After the above accounts were listed, the LIST ACCOUNTS option was selected again, and one particular MINOR ACCOUNT name was specified from the group of accounts that was listed in a). "Record not found" was then displayed. 3) SPR 518812 - SECURITY.UPDATE allowed a user with no password to be updated to any user level (0-3). 3.1.3.6. SPOOLER _______ 1) SPR 517645 - Serial printers configured as DMP serials sometimes hung while printing long print jobs. The Spooler status would show "PRINTING", but the number of pages and percent done never changed. 2) SPR 518108 - Cancelled spool jobs created from BASIC were removed from the queue, but the spool files remained on disk in the .SPL. node. (This was a problem on 9/8.6C only.) 3) SPR 518186 - If a major or minor account name exceeded 15 characters, and a spool job was submitted from that account, the system would dump with the fourtuples 2,10,33,11 (Instruction Fault in Spooler Module) and 1,242,0,11 when the spool job was accessed. 4) SPR 518994 - Restarting a spool job on a spool record that was greater than 247 bytes caused system dump 2,10,33,32 (Instruction Fault in Spooler Module) and 1,242,0,32 (String Limit Exceeded). 5) SPR 518718 - Restarting a print job after the TIME option had been modified sometimes caused the job to have a "Deferred" status, even after the time to print had passed. 6) SPR 519093 - If the system is reloaded when there are P* requests in the REQUESTS file (spool queue), and PRSTATUS is executed after the reload, the system will dump with the fourtuples 2,10,33,11 (Instruction Fault in Spooler Module) and 1,146,0,11 (Range Violation). The workaround is either to route all print requests to a specific printer, or be sure there are no P* requests in the REQUESTS file when the system is taken down. If the dump occurs, the REQUESTS file should be deleted and the system reloaded. Any jobs that were left in the spool queue should be printed using the SUBMIT utility. 3.1.3.7. UPDATE.WCS __________ SPR 517589 - UPDATE.WCS did not update the Load Directory for SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg008 REMIDI on 9xxx systems. 3.1.4. BASIC _____ 1) Changes to the BASIC TIM= function caused MAI OFFICE to log the user off the system after 4 1/2 minutes, even if TIM= was set for a longer period of time. The fix in Presentation Services allows for a timeout value of up to 512 seconds (about 8 1/2 minutes). If the timeout value specified is over 512 seconds is the system will never timeout. 2) SPR 518169 - If the ESCAPE key was pressed while reading a file with a duplicate key, dropping the terminal into console mode (no ESCAPE handling), typing RUN at this point to continue the program caused a record in the file to be skipped. 3.1.5. FILE SYSTEM ____ ______ SPR 517631 - Sometimes a hang condition would occur when accessing a Multi-Key file. Subsequent accesses of this file by other processes would result in hanging of those processes also. 4. BOSS/VS _______ 4.1. UTILITIES _________ 4.1.1. ERRORLOG Utility Enhancements ________ _______ ____________ The 10/9/8.6E releases offer several enhancements to the hardware ERRORLOG. One enhancement is the addition of a Summary option to the DOWNLOAD group. Figure 4-1 shows the current DOWNLOAD Detail screen (which is still an option). Figure 4-2 shows the new Summary screen. Figure 4-1. DOWNLOAD Detail Screen ______ ____ ________ ______ ______ MM/DD/YY MAI BASIC FOUR, INC. ERROR LOG UTILITY DOWNLOAD DETAIL: 02/01/88-00:00:00 TO 02/29/88-23:59:59 LOG FILE: (SYSDISK).ERRLOG.D880119T11511705 ---------------------------------------------------------------- Rec D/L D/L Process Ctlr Ctlr # Date Time Name # Type Completion status ---------------------------------------------------------------- 26 02/01/88 16:32 T3 63 IMLC Normal Completion 47 02/03/88 14:13 T16 32 8way Normal Completion 55 02/03/88 15:02 *INIT2 6 16way File not found 56 02/03/88 15:03 *INIT2 7 16way File not found 82 02/05/88 07:38 T0 0 4way Normal Completion 101 02/06/88 05:44 *MIDNITE 4 8way Normal Completion SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg009 Figure 4-2. New DOWNLOAD Summary Screen ______ ____ ___ ________ _______ ______ MM/DD/YY MAI BASIC FOUR, INC. ERROR LOG UTILITY DOWNLOAD SUMMARY: 02/01/88-00:00:00 TO 02/29/88-23:59:59 LOG FILE: (SYSDISK).ERRLOG.D880119T11511705 ---------------------------------------------------------------- Ctlr Ctlr D/L D/L # Type Total Errors ---------------------------------------------------------------- 0 4way 7 0 4 8way 11 0 6 8way 11 0 12 16way 12 1 13 16way 11 0 14 LANC 9 0 15 LANC 7 0 32 8way 13 2 62 IMLC 7 0 63 IMLC 7 0 Another enhancement is the addition of the drive number to I/O error data on the Fault Map screen. This is the "DRIVE = D3" information in the second text line of Figure 4-3. Figure 4-3. Fault Map Screen ______ ____ _____ ___ ______ MM/DD/YY MAI BASIC FOUR, INC. ERROR LOG UTILITY MAP AND ANALYSIS: 02/01/88-00:00:00 TO 02/29/88-23:59:59 FAULT MAP FOR VOLUME 3000022; DRIVE = D3; TYPE = P143 ------------------------------------------------------------ Cylinder/100 Head 0---1---2---3---4---5---6---7---8---9---0---1--- 0 ................................................ 1 ................................................ 2 ..........2..................................... 3 .........3...................................*.. 4 ................................................ 5 ..........................................1..... 6 ................................................ 7 ................................................ Cache error reporting has now been expanded to include ADVANCED SERIES family. The screen in Figure 4-4 shows cache error summary information for the ADVANCED SERIES only. The standard cache error reporting is still used for MPx 9xxx Series Systems. Figure 4-4. Cache Parity Errors on ADVANCED SERIES ______ ____ _____ ______ ______ __ ________ ______ MM/DD/YY MAI BASIC FOUR, INC. HH:MM ERROR LOG UTILITY SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg010 MEMORY ERROR SUMMARY: 02/01/88-00:00:00 TO 02/29/88-23:59:59 LOG FILE: (SYSDISK).ERRLOG.D880119T11511705 .------------------------------------------------------------------------------ Data Cache Parity Errors .------------------------------------------------------------------------------ CPU # Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0 .------------------------------------------------------------------------------ CPU0 0 0 0 0 CPU1 0 0 0 0 CPU2 0 0 0 0 Code Cache Parity Errors .------------------------------------------------------------------------------ CPU # Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0 .------------------------------------------------------------------------------ CPU0 0 0 0 0 CPU1 0 4 0 0 CPU2 0 0 0 0 Bits 0-31 indicate a 32-bit word. The cache error is broken down to the byte level for Data/Code cache on ADVANCED SERIES Systems, which will help in depot repair. A cache error will be reported on the Totals Summary report, regardless of the bit location. (An example of the Totals Summary report appears in Figure 4-6.) Memory error reporting has also been clarified. Memory error totals are now displayed on one screen as in Figure 4-5. The user no longer needs to add up memory errors from several screens to get the total. Actual running totals for memory errors and cache errors are also now displayed on the Total Summary screen as in Figure 4-6. Figure 4-5. Memory Error Summary ______ ____ ______ _____ _______ MM/DD/YY MAI BASIC FOUR, INC. HH:MM ERROR LOG UTILITY MEMORY ERROR SUMMARY: 02/01/88-00:00:00 TO 02/29/88-23:59:59 LOG FILE: (SYSDISK).ERRLOG.D880119T11511705 .------------------------------------------------------------------------------ ADDRESSES OF 24 MOST RECENT ERRORS 100000 100000 200000 100000 100000 100000 200000 000000 000000 000000 000000 000000 000000 000000 000000 000000 000000 000000 000000 000000 000000 000000 000000 000000 ERROR COUNTS BY ADDRESS RANGE 0000000-0080000-0100000-0180000-0200000-0280000-0300000-0380000-0400000 0 0 5 0 1 1 0 0 0400000-0480000-0500000-0580000-0600000-0680000-0700000-0780000-0800000 0 0 0 0 0 0 0 0 0800000-0880000-0900000-0980000-0A00000-0A80000-0B00000-0B80000-0C00000 0 0 0 0 0 0 0 0 CPU No: 0 1 2 3 Cache Parity Errs: 0 4 0 0 Figure 4-6. Totals Summary ______ ____ ______ _______ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg011 MM/DD/YY MAI BASIC FOUR, INC. HH:MM ERROR LOG UTILITY TOTALS SUMMARY: 01/01/88-00:00:00 TO 02/29/88-23:59:59 LOG FILES PREFIX: (SYSDISK).ERRLOG. .------------------------------------------------------------------------------ Boot- Down- Mem Cache Disk Tape Prtr Un- LOGFILE Loads Dumps Loads Errs Errs Errs Errs Errs known Total .------------------------------------------------------------------------------ D880107T11511705 107 34 37 0 4 124 124 155 0 797 D880119T09050940 111 60 50 0 0 175 77 105 0 797 D880201T16010861 25 20 6 7 0 15 10 27 0 153 4.2. AUDITOR'S LOGBOOK _________ _______ 4.2.1. General Information _______ ___________ The AUDITOR'S LOGBOOK provides automatic logging of the access history for selected files. You can use it to determine which records in a file have been created, modified, or deleted, at which time, and by whom. At the file level, you can determine who accessed the file and when any of the following events took place: o audit logging was turned ON or OFF; o audit writethru was turned ON or OFF; o the source file was deleted or renamed. The audit log information includes the user I.D., process I.D., date, time, operation performed, (i.e., write, delete, rewrite), plus a copy of the record written, deleted, or rewritten. Audit logging may be used for all file types except Serial. AUDITOR'S LOGBOOK provides for a permanent record of updates to a file, which can be invaluable when used for file recovery after a fatal system error. The existence of an audit log file allows you to: o examine any modifications that were made to data in the source files. o write other applications to read the audit log file and examine file activity; o reconstruct all activities on the file being audited; o recover data from the audit log file if the source file is damaged; You can request audit logging through the CREATE utility and the UPDATE utility. When you turn audit logging ON through either utility, the file system creates two indexed audit log files: a primary and a backup. The default file names are: .AUD for the primary and .AUDBAK for the backup. The system automatically appends the ".AUD" and ".AUDBAK" to the source file name. Audit logging is not supported on files with SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg012 special character file names. When a record in the data file is modified, the following information is recorded in the primary audit log file: o format level o type of operation o user I.D. o process I.D. o data o time o record image The audit information is recorded in chronological order. The backup audit log file holds the data from the previous primary audit log file. You may backup or initialize the backup audit log file without interfering with current operations on the primary audit log file and the data file. The backup file is initialized with the INITFILE utility. When the primary file is full, you must switch it with the backup file. The files are switched with the UPDATE utility. The backup audit log file must either be empty or non-existent before you try to switch the files. If neither case is true, the UPDATE utility displays an error message asking you to backup and initialize the backup file before the switch can proceed. IF THE PRIMARY LOG FILE BECOMES FULL, UPDATES TO THE SOURCE DATA FILE WILL BE HALTED UNTIL THE PRIMARY LOG FILE IS SWITCHED WITH THE BACKUP LOG FILE, OR UNTIL THE LOG FILES ARE EXPANDED. For this reason, it is important that the log files be sized as accurately as possible, and that the primary and backup log files be "switched" when the primary log file is close to reaching its capacity. The UPDATE utility is used for reducing and expanding the log files, as well as switching the primary log file with the backup log file. The log files may be reduced to the size required to hold the last record used. Because the log files must be the same size, the highest record used between the two files will determine the minimum size of the files. When the log files are expanded, both the primary and backup log files are expanded at the same time to keep them the same size. UPDATE requires exclusive access of the file. It is, therefore, necessary to exit the application to do the switch or the expand. In a future BOSS/VS release, the log files may be switched automatically, allowing the user to remain in his application and continue from where he left off after the switch. For further information on how to use the AUDITOR'S LOGBOOK, see the BOSS/VS UTILITY USER GUIDE, M5102J. 4.2.2. Disk Space Usage ____ _____ _____ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg013 Necessary space for the primary and backup log files should be taken into account when planning disk space usage. The primary and backup log files must reside on the same family as the source file. Although defaults are provided for the size and growth parameters of the log files, the user is encouraged to monitor file activity and use this as a basis for estimating the size of his log files. How often the user wishes to "switch" his primary and backup log files is also a factor in determining the size of these files. File activity includes the number of records added to and deleted from the file, as well as the number of records that are modified. Remember that any change to a record in a file creates a record in the log file. 4.2.3. System Performance ______ ___________ Using AUDITOR'S LOGBOOK does affect performance to a certain degree. However, this is dependent upon user applications, some of which may show no noticible performance degradation. When turning logging on, the user may select whether or not each new record written to the log file will be written immediately to disk. The state of the Writethru options for the data file and the log files will significantly affect the resultant performance. The following table demonstrates variations in performance based upon the use of file WRITE THRU in a WORST CASE scenerio. The file used in this example was a Direct file with a size of 10,000 records, 300 bytes per record, and a key size of 17. The timings reflect how long it took to write 10,000 records to this file. This test was run on an 8020 system. (Keep in mind that timings would be much faster on 9xxx and Advanced Series Systems.) ----------------------------------------------------------------------- File Audit Time Taken Write Thru Audit Log Write Thru 10,000 Recs % Increase ----------------------------------------------------------------------- a) FALSE FALSE N/A 684 secs N/A b) FALSE TRUE FALSE 790 secs 15% as compared to a) c) FALSE TRUE TRUE 1591 secs 133% as compared to a) d) TRUE FALSE N/A 1243 secs 82% as compared to a) e) TRUE TRUE FALSE 1451 secs 17% as compared to d) f) TRUE TRUE TRUE 2269 secs 83% as compared to d) ----------------------------------------------------------------------- File Write Thru: The Write Thru option on the source data file. Audit Log: The flag that indicates whether record updates to the source file are logged to the file. Audit Write Thru: The Write Thru option on the log file. Time: The time it took to perform the operation, using the given parameters. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg014 % Increase: Comparison of results based upon total time to fill up the 10,000 record file. --------------------------------------------------------------------- 4.2.4. DISKANALYZER Considerations ____________ ______________ 1) If the user reconstructs a file with logging enabled via DISKANALYZER, the new file will have two empty log files attached to it. Renaming the reconstructed file back to the old name will automatically delete the original log files, because the DELEXIST parameter in the RENAME utility refers to all three files: the source data file and its associated log files. The workaround for this problem is to rename the log files to a temporary name before the reconstruct, and rename them back to the original log names after the reconstructed source data file has been renamed back to its original name. This problem will be corrected in a future release. 2) Log files may be reconstructed, but after the reconstruction, they will not appear to the system to be "official" log files. They will still contain the log data, and they may be used for tracing an audit trail, but they may not be used to continue logging. If a log file is reconstructed and renamed back to its original name, the associated data file will not be accessible, because the file system will complain about the presence of a "non-official" log file. Software Engineering is investigating a solution to this problem. 4.2.5. Installing the AUDITOR'S LOGBOOK Key __________ ___ _________ _______ ___ AUDITOR'S LOGBOOK is an optional, chargeable feature, controlled by public key. This key is ordered through normal channels. To install the key, set your prefix to: .ETC.LEVEL. Enter the following in command mode: !INSTALLKEY ALB You will be prompted to enter the 8-character public key. Then you will be prompted to enter it again for verification. If the key installation is successful, the following will display: This key written to file. 4.3. DIAGNOSTICS ___________ NOTE: To access all the software documented in this section, the prefix must be set to the .R6E15.INST. node. Please see the installation sections in this announcement for SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg015 instructions on how to install DEMON and REMIDI. Further information on these diagnostics can be found in DOCWRITER, which can be accessed by entering !DOCWRITER in command mode. 4.3.1. REMIDI ______ NOTE: UPDATE.LD needs to be run for REMIDI whenever question marks (?/?) appear in Load Sector 2 at the top of the OSINFO screen. 4.3.1.1. On MPx 7000, 7100, and 8000 Series Systems __ ___ _____ _____ ___ ____ ______ _______ REMIDI version BV includes all micro-diagnostics except those for the MPC and LAN controllers. It is loaded into WCS slot 2 and is used on MPx 7000, 7100, and 8000 Series Systems. REMIDI version BVM contains micro-diagnostics for the MPC and LAN controllers. It is loaded into WCS slot 3 on all 7000/7100 Series Systems and on 8000 Series Systems with LAN controllers. This version of REMIDI is used on MPx 7000/7100 Series Systems for the MPC and LAN controllers, and on 8000 Series Systems for LAN controllers only. If a LAN controller is not present on an 8000 Series System, the BVM version of REMIDI is not needed. The Load Directory controls which version of REMIDI will be executed. The UPDATE.LD utility is used to update the Load Directory. See the following section for instructions on running UPDATE.LD. 4.3.1.1.1. Updating the Load Directory for REMIDI ________ ___ ____ _________ ___ ______ Disregard this section if your 8000 Series System does not have a LAN controller. (In this case only REMIDI version BV is used, and it is not necessary to update the Load Directory.) Since REMIDI is a WCS Image, two WCS slots, slot 2 and slot 3, will be required for the two REMIDI versions. The extra slot is provided by the DEMON WCS slot. Because DEMON and the BOSS/VS O.S. share the same WCS, Load Sector 3 should display 3/0 or 3/1, indicating that the WCS for DEMON is in either WCS slot 0 or WCS slot 1. This leaves WCS slot 3 free for REMIDI. Only one version of REMIDI will run at a time. The version that will run is dependent on how the Load Directory for REMIDI (Load Sector 2) is set up. The standard version, BV, which resides in WCS slot 2, has an OS/WCS of 0/2. The MPC/LAN version, BVM, which resides in WCS slot 3, has an OS/WCS of 0/3. Use UPDATE.LD to update the Load Directory to designate which version to run. To test the MPC and LAN controllers with REMIDI version BVM, execute UPDATE.LD, using the inputs below: NOTE: Lines preceded by an "*" require operator input. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg016 * Input in command mode !UPDATE.LD Update Load Directory Utility Disks (Unit number) on line : 0(16),1(17) Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 6.5.x.x R 6E*xx (date) B 6.1.x.x 1 1/1 | 6.5.x.x R 6E*xx (date) B 6.1.x.x 2 0/2 | B 5.x.x R 3 3/0 | 6.5.x.x DEMON (date) B 6.x.x R * New OS slot (0,1,3): 0 * New WCS slot (0..3): 3 * Load sector (0..3) : 2 In this case, UPDATE.LD will then display the new Load Directory as follows: Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 6.5.x.x R 6E*xx (date) B 6.1.x.x 1 1/1 | 6.5.x.x R 6E*xx (date) B 6.1.x.x 2 0/3 | B 5.x.x R 3 3/0 | 6.5.x.x DEMON (date) B 6.x.x R Notice the change in Load Sector 2. To go back to the standard REMIDI version, BV, which tests the CPU and main memory, use the following in UPDATE.LD: * New OS slot (0,1,3): 0 * New WCS slot (0..3): 2 * Load sector (0..3) : 2 In this case, UPDATE.LD will then display the new Load Directory as follows: Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 6.5.x.x R 6E*xx (date) B 6.1.x.x 1 1/1 | 6.5.x.x R 6E*xx (date) B 6.1.x.x 2 0/2 | B 5.x.x R 3 3/0 | 6.5.x.x DEMON (date) B 6.x.x R NOTE: The Load Directory should stay in the above setup in case the system CPU needs to be tested in a down condition. Always use Load Sector 2 for REMIDI. 4.3.1.2. On MPx 9xxx and the ADVANCED SERIES __ ___ ____ ___ ___ ________ ______ REMIDI for MPx 9xxx Series Systems consists of two sections, AVA, which is loaded into WCS slot 2, and AVC, which is loaded into WCS slot 3. REMIDI for the ADVANCED SERIES family also consists of two sections, CVA, which is loaded into WCS slot 2, and CVC, which is loaded into WCS slot 3. Unlike the REMIDI versions on 7xxx/8xxx systems, the REMIDI versions on 9xxx and ADVANCED SERIES Systems, respectively, are not used independently by slot. In other words, the version of REMIDI in WCS slot 2 calls the version of REMIDI in SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg017 WCS slot 3 on 9xxx and ADVANCED SERIES Systems. Load Sector 2 contains the OS/WCS pointers for REMIDI. 4.3.1.2.1. Updating the Load Directory for REMIDI ________ ___ ____ _________ ___ ______ Normally, the Load Directory is updated by the operating system when REMIDI is installed with UPDATE.WCS. However, if Load Sector 2 does not reflect an O.S./WCS of 0/2, the UPDATE.LD utility can be run to update the Load Directory: NOTE: Lines preceded by an "*" require operator input. * Input in command mode !UPDATE.LD Update Load Directory Utility x.6xx.xx Disks (Unit number) on line : 0(16),1(17) Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 6.5.x.x R 6E*xx (date) x 6.x.x 1 1/1 | 6.5.x.x R 6E*xx (date) x 6.x.x 2 ?/? | R x 6.x.x 3 3/0 | 6.5.x.x DEMON (date) R x 6.x.x * New OS slot (0,1,3): 0 * New WCS slot (0..3): 2 * Load sector (0..3) : 2 UPDATE.LD will then display the new Load Directory as follows: Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 6.5.x.x R 6E*xx (date) x 6.x.x 1 1/1 | 6.5.x.x R 6E*xx (date) x 6.x.x 2 0/2 | R x 6.x.x 3 3/0 | 6.5.x.x DEMON (date) R x 6.x.x Notice the change in Load Sector 2. 4.3.2. DEMON - Updating the Load Directory _____ _ ________ ___ ____ _________ Because REMIDI resides in WCS slot 3 on 7xxx and 9xxx systems and 8xxx systems with LAN, the Load Directory must point to another WCS slot for DEMON on these systems. The O.S. and DEMON share the same WCS code, therefore, Load Sector 3 should point to the WCS slot used by the O.S. Normally, this is set up by the operating system when DEMON is installed, providing that the correct answers are entered at the UPDATE.OS prompts during installation. If, for any reason, Load Sector 3 does not reflect OS/WCS as 3/0 or 3/1, you may use UPDATE.LD to change it, using the following inputs: NOTE: Lines preceded by an "*" require operator input: * Input in command mode !UPDATE.LD Update Load Directory Utility x.6xx.xx Disks (Unit number) on line : 0(16),1(17) Load OS/WCS | OS-Level Name WCS-Level SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg018 0 0/0 | 6.5.x.x R 6E*xx (date) x 6.x.x 1 1/1 | 6.5.x.x R 6E*xx (date) x 6.x.x 2 0/2 | R x 6.x.x 3 3/3 | 6.5.x.x DEMON (date) R x 6.x.x * New OS slot (0,1,3): 3 * New WCS slot (0..3): 0 (or 1) * Load sector (0..3) : 3 UPDATE.LD will then display the new Load Directory as follows: Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 6.5.x.x R 6E*xx (date) x 6.x.x 1 1/1 | 6.5.x.x R 6E*xx (date) x 6.x.x 2 0/2 | R x 6.x.x 3 3/0 | 6.5.x.x DEMON (date) R x 6.x.x Notice that Load Sector 3 is now pointing to WCS slot 0. 4.3.3. ADVANCED SERIES Only ________ ______ ____ 4.3.3.1. High Frequency Margins on the ADVANCED SERIES ____ _________ _______ __ ___ ________ ______ The ADVANCED SERIES processor has the capability to run at a faster clock rate for diagnostic purposes. This capability is intended for diagnostic testing of the CPUs ONLY. The system should never be used at the higher clock rate except for diagnostic purposes. 4.3.3.2. Using ALT LOAD for REMIDI and DEMON _____ ___ ____ ___ ______ ___ _____ On the ADVANCED SERIES, REMIDI and DEMON can be loaded into memory from the O.S. tape via ALT LOAD and executed (1/2-inch tape only). To load REMIDI, load switch 2 should be on. To load DEMON, load switches 2 and 3 should be on. Pressing the ALT LOAD switch will then load the selected diagnostic into memory for execution. 4.4. CONFIGURATIONS ______________ NOTE 1: The number of "High Activity Tasks" is approximate and largely dependent on the application. The relative relationship of the numbers between configurations is more important than the actual numbers themselves. NOTE 2: System configurations of MPx 9xxx Series Systems are based on the use of the LS-700 power supply mainframes. Original 810 systems do not support the LS-700 power supply and, therefore, will not meet all defined maximum configurations listed. NOTE 3: The following configurations are based on performance testing, and are subject to change as newer performance testing data becomes available. The configurations listed in the marketing announcements override those listed here. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg019 4.4.1. Configurations for MPx 7000/7100/8000 Series Systems ______________ ___ ___ ______________ ______ _______ The maximum configuration for MPx 7000, 7100, and 8000 Series Systems, models 7030, 7130, and 8030, is as follows: 116 Devices - A combination of 8-ways, 16-ways, the 4 ports on the MCS PCBA, MDTs and HVDTs up to a total of 116 devices are supported. 3 CPU sets 10 ISDCs: 16-ways (7 maximum) and/or 8-ways 32 Ghost tasks 24 High speed videos (HVDT) 8 Disk drives 4 Parallel printers 2-8 Megabytes of memory (6 MB maximum on 7000/7100 systems) 2 Magnetic tape drives - MTR, MTS, and/or GCR (2 Maximum), and/or MCS (1 maximum) 4 Intelligent Multi-Line Controllers (IMLC) 8 DataWord II terminals 4 TBC lines 64 3270 terminals 8 X.25 lines 2 Auto-Call Units (ACU) 99 Serial printers 99 System printers (total serial and parallel not to exceed 99) 2 Buffered Magnetic Tape Controllers 27 High activity concurrent tasks 1 LAN controller NOTE: There is a maximum of 9 memory assembly boards in any combination of 1/2 Mb, 1 Mb, 2 Mb, 4 Mb and BMTCs (a maximum of 3 boards per chassis). Models 7010/7110/8010 and 7020/7120/8020 have the same configuration limits as models 7030 and 8030 above, with the following limitations: 7010/7110/8010 7020/7120/8020 1 CPU set 2 CPU sets 2-4 Mb memory 2-6 Mb memory 20 Devices 52 Devices 12 Concurrent tasks 20 Concurrent tasks (high activity) (high activity) 19 System printers 51 System printers 4.4.2. Configurations for MPx 9000/9100/9400 Series Systems ______________ ___ ___ ______________ ______ _______ The maximum configuration for MPx 9000, 9100, and 9400 Series Systems, models 9020, 9120, and 9420 is as follows: 116 Devices - A combination of 8-ways, 16-ways, the 4 ports on the MCS PCBA, MDTs and HVDTs up to a total of 116 devices are supported. 2 CPU sets with Evaluation Stack and Rstack Cache 10 ISDCs: 16-ways (6 maximum) and/or 8-ways (10 maximum) 32 Ghost tasks SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg020 24 High speed videos (HVDT) 12 Disk drives on models 9020 and 9120, 8 disk drives on model 9420 (2.4 GB maximum), with no more than 8 14-inch fixed drives on any of the 3 models 8 Parallel printers 4-12 Megabytes of memory 2 Magnetic tape drives - MTR, MTS, and/or GCR (2 maximum), and/or MCS (1 maximum) 4 Intelligent Multi-Line Controllers (IMLC) 8 Dataword II terminals 4 TBC lines 64 3270 terminals 8 X.25 lines 2 Auto-Call Units (ACU) 99 Serial printers 99 System printers (total serial and parallel not to exceed 99) 4 DMA-I controllers on models 9020 and 9120, and 4 (total) DMA-I/DMA-II controllers on model 9420 * 2 Buffered Magnetic Tape Controllers 42 High activity concurrent tasks 1 LAN controller * It is recommended that, for maximum performance, no more than two disks be configured per DMA-II, and that the number of DMA-II's equal or exceed the number of CPU's. Models 9010, 9110, and 9410 have the same configuration limits as the 9020, 9120, and 9420 above, with the following exceptions: 1 CPU set with Evaluation Stack and Rstack Cache 68 Devices 10 ISDCs: 16-ways (4 maximum) and/or 8-ways (8 maximum) 67 Serial printers 75 System printers (total serial and parallel not to exceed 75) 27 High activity concurrent tasks 4.4.3. Configurations for MPx 9500/9600 Series Systems ______________ ___ ___ _________ ______ _______ The maximum configuration for MPx 9500 and 9600 Series Systems, models 9530 and 9630, is the same as the maximum configuration for the MPx 9000, 9100 and 9400 Series Systems, models 9020, 9120, and 9420 with the following exceptions: 3 CPU sets with Evaluation Stack Rstack Cache Code Cache Data Cache 255 Devices 16 ISDCs: 16-ways (16 maximum) and/or 8-ways (16 maximum) 4-24 Maximum megabytes of main memory (see Hardware section for mandatory revision levels for main memory support above 12 megabytes) 16 Disk drives on model 9530, 12 disk drives on model 9630 (3.6 GB maximum), with no more than 8 14-inch fixed drives on either model 4 DMA-I controllers (may also include DMA-II controllers if system is an upgrade from a 9400) 73 High activity concurrent tasks SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg021 Models 9510/9520 and 9610/9620 have the same configuration limits as models 9530/9630 with the following exceptions: 9510/9610 9520/9620 1 CPU set 2 CPU sets (same caches as the 9530) (same caches as the 9530) 10 ISDCs: 16-way (4 maximum) 10 ISDCs: 16-way (6 maximum) 8-way (8 maximum) 8-way (10 maximum) 84 Devices 132 Devices 83 Serial printers 53 Concurrent tasks 91 System printers (high activity) (total serial and parallel) 32 Concurrent tasks (high activity) 4.4.4. Configurations for the ADVANCED SERIES Family ______________ ___ ___ ________ ______ ______ The maximum number of high activity concurrent tasks is 146 on the Advanced Series Model 63 and 84 on the ADVANCED SERIES Model 42. The maximum configuration for ADVANCED SERIES model 63 is as follows: 255 Devices - A combination of 8-ways, 16-ways, and the 4 ports on the MCS/M PCBA, and MDT's up to a total of 255 devices are supported. 3 CPU's (with cache boards) 16 ISDCs: 16-ways (16 maximum) and/or 8-ways (16 maximum) 4-24 Maximum megabytes of main memory (See Hardware section for mandatory revision levels for main memory support above 12 megabytes.) 16 Disk drives (may be 300MB and 621MB fixed disks, and 285 removables up to 9.9GB maximum) 4 DMA controllers (may be DMA-I disk controllers for support of 285MB removable disks and/or DMA-III disk and parallel printer controllers for support of 300MB and 621MB fixed disks and parallel printers) * 32 Ghost tasks 8 Parallel printers 2 Magnetic tape drives - MTR, MTS, and/or GCR (2 maximum), and/or MCS (1 maximum) 4 Intelligent Multi-Line Controllers (IMLC) 8 Dataword II terminals 4 TBC lines 64 3270 terminals 8 X.25 lines 2 Auto-Call Units (ACU) 99 Serial printers 99 System printers (total serial and parallel not to exceed 99) 2 Buffered Magnetic Tape Controllers 1 LAN controller The maximum configuration for ADVANCED SERIES model 62 is the same as for model 63, with the following exceptions: SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg022 196 Devices 2 CPU's (with cache boards) 4-20 maximum megabytes of main memory The maximum configuration for ADVANCED SERIES model 61 is the same as for model 63, with the following exceptions: 148 Devices 1 CPU (with cache board) 4-16 maximum megabytes of main memory The maximum configuration for ADVANCED SERIES model 42 is the same as for model 63, with the following exceptions: 132 Devices 2 CPU's (without cache) 4-16 maximum megabytes of main memory The maximum configuration for ADVANCED SERIES model 41 is the same as for model 63, with the following exceptions: 100 Devices 1 CPU (without cache) 4-12 maximum megabytes of main memory * For maximum performance, it is recommended that no more than 2 disks be configured per DMA. 4.5. BASIC _____ 4.5.1. Key Words ___ _____ New key words were added to MBF BUSINESS BASIC as of release 9/8.6A. For a complete list of BASIC key words, see Appendix E of the BUSINESS BASIC 86 REFERENCE MANUAL, M6262A. 4.5.2. Easy EDIT ____ ____ The BASIC EDIT directive has been enhanced to allow editing of the last statement you typed without specifying the statement number. For example, if the last statement you typed was: >1030 PRINT "HI" and you type: >EDIT the statement appears with the cursor positioned at the beginning of the line. If you edit the statement and press RETURN, the new statement replaces the original statement and also becomes the last statement typed. If you remove the line number and press RETURN, the console command in the statement is executed. If you change the line number only and press RETURN, the new line number is added to the program or replaces the line with SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg023 that new number if it already exists in the program. The original line number and statement are not changed. If you end the edited statement with ESCAPE, the unedited statement is remembered as the last statememt typed. If the line is blank, the previously remembered statement remains. An easy EDIT statement, i.e., one which does not specify a statement number, is not remembered as the last statement typed. If you type an "EDIT X" statement, where X is not a valid statement number, the EDIT statement itself is remembered. If you extend a statement by typing a colon after the statement number, e.g., "2500: ELSE GOTO 1710", the whole statement is remembered as the last statement typed. 5. HARDWARE ________ When upgrading to O.S. levels 9/8.6E, hardware changes, per se, are not required. (Upgrading to 10.6E requires ADVANCED SERIES hardware - see section 5.4.) However, the following list of PCBA revision levels indicates the MANDATORY and RECOMMENDED revision levels of MPx and ADVANCED SERIES PCBA's. MANDATORY means that the specified revision level is needed for system operation. This level provides minimum assurance that your customer's system will operate in a stable manner. RECOMMENDED means that the specified revision level ensures the reliable operation of your customer's system. The RECOMMENDED (or higher) revision levels help to assure reliability and stability. If your customers' system PCBA's are at MANADATORY levels or below, careful plans should be made to replace the PCBA's with the RECOMMENDED (or higher) revisions. This should be done on a once per visit basis, such as one board per PM visit. DO NOT replace all PCBA's simultaneously. Some RECOMMENDED revision levels may vary based on specific system configurations, as detailed below. For example, the 16 MB High Speed Memory PCBA requires specific MCS and Terminator PCBA's. 5.1. MPX 7000, 7100, AND 8000 PCBA NOTES ___ _____ _____ ___ ____ ____ _____ 1) MCS 903374-001 PCBA Revision L is the mandatory and recommended level. Revision S adds another option to the switch setting of SW1. SW1 position 4 (SW1-4) is switch selectable between MPx 7000/7100/8000 Series Systems (SW1-4, OPEN) or MPx 9xxx Series Systems (SW1-4, CLOSED). If the MCS PCBA, at revision S, is switch selected for MPx 9xxx Series Systems and installed into an MPx 7000/7100/8000 Series SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg024 System, it will not load. - MCS 903374-002 PCBA-Revision V Revision V creates the -002 assembly. This assembly can be used on all MPx systems. 2) MDI 903361-001 PCBA Revision L is the mandatory and recommended level. This level prevents the MDI/ACS clocks from drifting and getting out of phase, which causes "INVOP" and "NILPTR" dumps. - MDI 903408-001 PCBA Revision K is the mandatory and recommended level. This level prevents the MDI/ACS clocks from drifting and getting out of phase, which causes "INVOP" and "NILPTR" dumps. 3) ACS 903379-001/-002 PCBA's Revision L is the mandatory and recommended level. 8000 systems on OS 8.4B or above require revision L, boot prom version 2.0.0.1 or higher. 7000 systems require revision Y or above, boot prom version 2.0.0.4 or higher (MPC support). Revision level Z, boot prom version 2.0.0.2, cannot be used on 7000 systems (no MPC support). Revision levels V and W, boot prom version 2.0.0.3, is obsolete; do not use. Tape load support from a BMTC requires revision T, boot prom version 2.0.0.2 or higher. Systems with 8-inch fixed drives require revision AA, boot prom version 2.0.0.5 or higher. - ACS 903379-003 PCBA Revision AD creates the -003 assembly. This version of the ACS PCBA can also be used in 7000/8000 systems. 7100 systems require AD or higher and this revision level is also required for support of the 120 MB MTCS tape. Board versions -002 or -003 are mandatory for 3 CPU systems, MPx 7xxx/8xxx Series Systems. 4) MPC 903500 PCBA Revision H is the mandatory and recommended level. If used in the MPx 7100 system, remove JMP3, if present, and set SW2-1 and SW2-4 OFF. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg025 - MPC 903546 PCBA Revision B is the mandatory level; revision H is the recommended level. If used in the MPx 7100 system, remove JMP3 if present and set SW2-1 and SW2-2 OFF. 5) TDP Controller 903217-001 PCBA Revision K is the mandatory recommended level. Revision K eliminates excessive sector number errors written to the ERROR LOG. - TDP Controller 903453-001 PCBA New build TDP controller, which replaces TDP controller 903217-001. Revision K is the mandatory and recommended level. 6) NIMLC Controller 903381-001 PCBA Revision E is the mandatory level; revision K is the recommended level. This IMLC must be located to the right of the CPU set. Revision G provides correct line status for Data Set Ready (DSR), when no device is attached. Revision K is mandatory for all three (3) mainframe systems. - NIMLC Controller 903381-002 Revision N creates this version of NIMLC for international use. It provides RS-232-C interface on Port B, using standard 1488/1489 IC's to support cabling longer than 50 feet (provides higher input impedance interface required for use on various Wide-Area Networks). - NIMLC Controller 903534-001 PCBA Revision D is the mandatory and recommended level. Provides the same interface as the 903381-002 PCBA on ports A and B. This NIMLC can be located on the left or right of the CPU. - NIMLC Controller 903251-001 PCBA This NIMLC was used with the 810 system and will not operate on the MPx series systems. 7) Memory (1 MB, 2 MB, 4 MB) 903516-00x PCBA Revision A is the mandatory level; revision E is the recommended level. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg026 Memory 903516-001 PCBA is the 2MB version. Memory 903516-002 PCBA is the 4MB version. Memory 903516-003 PCBA is the 1MB version. 8) Terminator 903199 PCBA Revision D is the mandatory and recommended level. Revision H creates the -004 assembly. Revision H can be used on all MPx systems. 5.2. MPX 9XXX SERIES SYSTEM PCBA NOTES ___ ____ ______ ______ ____ _____ NOTE: An asterisk (*) appears in front of revision levels that are mandatory for main memory support above 12 megabytes. 1) MCS 903374 PCBA Revision L is the mandatory level; revision S is the recommended level. Revision S, or above, is required for reliable system operation. Revision S adds another option to the switch setting of SW1. SW1 position 4 (SW1-4) is switch selectable between the addressing schemes of the MPx 7000/7100/8000 (SW1-4, OPEN) Series Systems or the MPx 9xxx Series Systems (SW1-4, CLOSED). If the MCS PCBA is switch selected for MPx 7000/7100/8000 systems and installed into an MPx 9xxx Series System, board addresses 32 thru 47 are reserved for the IMLC PCB only. If the MPx 9xxx scheme is used then there are no address restrictions. * Revision T is required for main memory support above 12 megabytes. Set SW1-4 to CLOSE for the 9xxx addressing scheme. * Revision V creates the -002 MCS. This revision is mandatory for support of the 16 MB memory board (P/N 903621) on 9xxx systems. It also can be used for main memory support above 12 MB. 2) AMS 903548 PCBA Revision F is the mandatory level, revision L is the recommended level. Revision F released the 4K boot proms version 3.1.0.4. This revision, or above, is required for operation. * Revision N creates the -002 PCBA and is required for main memory support above 12 megabytes. Revision P creates the -003 PCBA and is required for MPx 94xx systems. The -003 PCBA can be used in all MPx systems. Revision P is required for support of the 621 MB fixed disk drive. 3) ESTK 903552 PCBA SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg027 Revision G is the mandatory and recommended level. * Revision J, or above, is required for main memory support above 12 megabytes. 4) IDC 903550-001 PCBA (with cache) IDC 903550-002 PCBA(without cache) Revision H is the mandatory level; revision P is the recommended level. Revision J addresses cache timing problems on selected systems. Do not replace the IDC PCBA on an error free system. 5) IDC64 903597-001 PCBA (with cache) IDC64 903597-002 PCBA (without cache) Revision E is the mandatory level; revision H is the recommended level. * IDC64 PCBA is required for support of main memory above 12 megabytes. Strap E6 to E7 must be out. 6) DMA-I 903554 PCBA * Revision H is the mandatory level; revision P is the recommended level. Revision H is required for the 600 LPM band printer, model 4220. It is also required if 300 MB 8-inch drives log excessive errors in the ERRORLOG. Revision N is required when used with the DMA-II. Revision P, or above, is required for reliable system operation. Revision R is required for use with the 16 MB memory board for full power fail recovery. 7) DMA-II (SCSI) 903599 PCBA Revision K is the mandatory and recommended level. This revision is required for MPx 94xx SCSI disk drive support; requires 9.6E or later O.S. Revision L contains a fix for excessive soft errors logged in the ERRORLOG when both DMA-I's and DMA-II's are in the same system. - DMA-II (SCSI) 903741 PCBA This is the new version of DMA-II due to artwork changes. It may be use in place of 903599 PCBA and visa versa. 8) DMA-III (SMD) 903679-001 PCBA Revison C is the mandatory and recommended level. The DMA-III is required for support of the 621 MB fixed disk drive. (The 621 MB disk also requires the 903548 -003 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg028 AMS board.) The DMA-III revision C controller also supports the 300 MB disk drive without the use of the SMD-I/II PCBA. This controller has the SMD logic on board. 9) NIMLC 903381-001 PCBA Revision K is the mandatory and recommended level. This NIMLC must be located to the right of the CPU set. - NIMLC 903381-002 PCBA Revison N creates this version of NIMLC for International use. It provides RS-232-C interface on Port B using standard 1488/1489 IC's to support cabling longer than 50 feet (provides the higher input impedance interface required for use on various Wide-Area Networks). - NIMLC 903534 PCBA Revision D is the mandatory and recommended level. This revision provides the same interface as the 903381-002 PCBA on ports A and B. This NIMLC can be located on the left or right of the CPU set. - NIMLC 903251 is OBSOLETE This NIMLC was used with the 810 system and will not operate on the MPx Series Systems. NOTES: There have been a few instances when a known good IMLC is installed into the MPx 9xxx system, the RED LED (Parity error) comes on during load (903534/903381). In this case, install JMP C on the PCBA. When the JMP C option is used on the MPx 9xxx system and "T0" is a serial terminal, the system will hang in the TYPE II/III load. This side effect only occurs with the 9.6A OS and is fixed in 9.6B OS and above. Refer to Field Bulletin #375. 10) Memory (1/2 MB and 1 MB) 903349 PCBA Revision V is the mandatory and recommended level. This revision is not to be used with greater than 12 megabyte support. 11) Memory (2 and 4 MB) 903516-00x PCBA Revision E is the mandatory and recommended level. Memory 903516-001 PCBA is the 2MB version. Memory 903516-002 PCBA is the 4MB version. * Revision J is required for support of main memory above 12 megabytes. Support of main memory above 12 megabytes is supported on MPx 9500 and 9600 Series Systems only. JMP 5 at location 1E = 1 to 2, and IC pad location 1A = 8 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg029 to 9. 12) 16/8/4MB High Speed ECC Memory 903621-00x PCBA High Speed ECC Memory 903621-001 (16MB), -003 (8MB), -004 (4MB) version are supported on the MPx 9xxx Series Systems. Requires MCS -002, Terminator -004, and DMA-I at revision R or above for MPx Series Systems. Revision C is the mandatory level; revision F is the recommended level. Revision G creates the 903621-005 (16MB), -007 (8MB), -008 (4MB) versions. 13) Terminator 903199 PCBA Revision D is the mandatory and recommended level. Revision H creates the -004 assembly, which is mandatory for support of the 16 MB, High Speed ECC memory board versions (P/N 903621). The following boards are NOT supported on MPx 9xxx Series Systems: 1) 7000/7100/8000 CPU set 2) TDP (Must be replaced by the BMTC for tape support) 3) MPC 5.3. PCBA'S FOR ALL MPX SERIES SYSTEMS ______ ___ ___ ___ ______ _______ The following are PCBA'S common to all MPx Series Systems without system model dependencies: 1) BMTC 903413 PCBA Revision R is required for full MTCS support. Revision U is required for support of the GCR 1/2" tape drive model 4405. Revision Z allows the BMTC to operate on the left or right side of the CPU set. 2) Local Area Network Controller (LAN) 903595 PCBA Revision E in the mandatory level; revision F is the recommended level. With the release of the 9.6A/8.6A O.S., a new controller is supported: The Local Area Network controller. The LAN PCBA provides the ability to tie like systems together (MPx to MPx) in a local environment not more than 4000 feet apart. Each system requires one LAN controller, and both systems must be on the same O.S. level. The LAN may be installed either to the right of the CPU set(s) after the BMTC PCBA or to the left of the MCS PCBA. Refer to the MAGNET section in this document for further information on the Local Area Network. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg030 Revision H creates the -002 version. This version can be used on all MPx series systems. 3) 16-Way Controller 903437 PCBA Revision J is the mandatory and recommended level. 16-Way controllers require the use of an I/O panel. The I/O panel is supplied with the purchase of the PCBA. 4) 8-Way Controller 903383 PCBA Revision A is the mandatory and recommended level. 5) VCON Controller 903377 PCBA Revision C is the mandatory and recommended level. 5.4. ADVANCED SERIES PCBA NOTES ________ ______ ____ _____ The following are PCBA's that are supported on the ADVANCED SERIES and their revision levels. 1) MCS/M 903718 PCBA Revision G is the released level of this PCBA. The MCS/M (Memory Communication Support with Memory) PCBA provides boot load function/clocks/4way and 4MB of main memory. 2) NEP II 903705 PCBA Revision E is the released level of this PCBA. The NEP II (N-Code Execution Process) PCBA is the main processer. 3) STACHE II 903707 PCBA Revision C is the released level of this PCBA. The STACHE II PCBA is an optional PCBA that makes up the ADVANCED SERIES Model 60. It contains the Rstack, Code Cache, and Data Cache. 4) MBA 903617 PCBA Revision D is the released level of this PCBA. The MBA (Memory Bus Adapter) PCBA is required to support the shared memory controllers developed for the MPx 8/9xxx systems (160ns clock) on the ADVANCED SERIES Models 40/60 (80ns clock). 5) BMTC 903413 PCBA Revision Z is mandatory for support of the ADVANCED SERIES systems. 6) LAN 903595-002 PCBA Revision H creates the -002 version, this version is mandatory for support of the ADVANCED SERIES systems. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg031 7) DMA-I 903554 PCBA Revision R is mandatory for support on the ADVANCED SERIES, due to the 1Mbit rams used for main memory (MCS/M and 16MB PCBA's) and full power fail recovery. REV T corrects a problem in REV R firmware which caused the timeout LED (DS2) to turn on during REMIDI testing in the ADVANCED SERIES family only. 8) DMA-III (SMD) 903679-001 PCBA Revision C is the mandatory and recommended level. The DMA-III is required for support of the F621 (600MB) disk drive. It also supports the P314 (300MB) disk drive without the use of the SMD-I/II PCBA. This controller has the SMD logic on board. 9) IMLC 903534 PCBA Revision D is mandatory for support of the ADVANCED SERIES. This version of IMLC, at the indicated revision level, is required to function on the left side of the CPU set. Remove JMP C if installed. 10) 16/8/4MB High Speed ECC Memory 903621-00x PCBA Revision G creates the -005 (16MB), -007 (8MB), -008 (4MB) versions. Revision K is the mandatory and recommended level. 11) 8-WAY 903383 PCBA There is no mandatory revision level required for support of this PCBA on the ADVANCED SERIES. 12) 16-Way 903437 PCBA Revision J is LARL for support on the MPx and ADVANCED SERIES. 13) Terminator 903199-004 PCBA Revision H is the mandatory level, and it creates the -004 version. 14) LS-700 Power Supply Assembly 907295-001 If any MPx 8000 system is being upgraded to the ADVANCED SERIES family, the LS-700 assembly 907295-001 must be at revision AA. (PCBA 903386-001, inside the LS-700 assy, will be at revision AB or above.) If any MPx 9xxx system is being upgraded to the ADVANCED SERIES family, the LS-700 power supply does not need to be replaced. The load sustained by this power supply under the 9xxx configuration gives sufficient evidence that the existing revision level is adequate for the ADVANCED SERIES. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg032 5.4.1. PCBA's Not Supported on the ADVANCED SERIES ______ ___ _________ __ ___ ________ ______ The following boards are NOT supported on the ADVANCED SERIES family: 1) 7x00/8000/9x00 CPU sets. (Use ADVANCED SERIES 40/60 CPU's) 2) MCS PCBA. (Use MCS/M) 3) MPC/TDP and DMA-II PCBA's. (Use DMA-I and DMA-III) 4) Memory 903349 (1MB assembly), 903516 (4MB assembly), 903621-001/-003/004. (Use 16MB: -005, 8MB: -007, 4MB: -008) 5) VCON PCBA and HVDT's 6) Terminators -001 (Below revision H). (Use -004) 5.5. PERIPHERAL DEPENDENCIES __________ ____________ 5.5.1. Tape Drives ____ ______ 5.5.1.1. GCR Tape Drive ___ ____ _____ It is possible for a hang condition to occur in SAVERESTORE, if the GCR tape drive does not have the following minimum revision levels: IF CARD 403923205 (Previously, the LARL was 403923202) CP CARD 403864305 (Previously, the LARL was 403864303) 5.5.1.2. SCSI MTCS Tape Drive ____ ____ ____ _____ On the SCSI MTCS 1/4-inch tape drive (4406), the E-PROM (OEM PN 966039; MBF PN 400716-103) at location 'U6' should be 3X10. This tape drive is used on MPx 94xx systems only. 5.5.2. Terminals _________ 1) The DT-4313 terminal must have REV E firmware to support Industry Standard slave printers. 2) T0 MUST be a model 4309 or later model VDT. VDT's 7250 and 7270 (4301) are not supported as T0 on release levels 9/8.6C and above due to default terminal driver change. This change corrected the time differences seen in Saverestore Type I vs Type II load. 5.5.3. Disk Drives ____ ______ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg033 1) The 621 MB fixed disk requires the -003 version of AMS PCBA P/N 903548 when used in 9xxx systems. The 621 MB disk is supported by the DMA-III controller, P/N 903679. 2) The 300 MB fixed disk requires revision AA of ACS PCBA P/N 903379 when installed on MPx 7xx/8xxx systems. TDP (PDC) controller P/N's 903217 and 903453 require IC's OTHER THAN Signetics (indicated by a bold 'S') at locations 9E and 10K (74S240). 6. INSTALLATION ____________ 6.1. NEW FILE NAMING CONVENTION ___ ____ ______ __________ As of releases 10/9/8.6E, the names of the files that are loaded into the OS/WCS slots have been shortened and made generic in order to simplify installation procedures. The first letter of the name will designate the machine type as follows: A - MPx 9xxx Machine Type B - MPx 8xxx/7xxx Machine Type C - ADVANCED SERIES Machine Type U - Universal Disk Image Format The second letter of the name will be used to designate the boot image type as follows: C - 1/4 inch Cartridge Tape Boot Image D - 1/2 inch Diagnostic Tape Boot Image Load & Execute T - 1/2 inch Tape Boot Image Load & Copy V - Universal Disk Image Format The third letter, if present, will be used to designate the Micro Peripheral Controller WCS images and the four REMIDI image formats, as follows: A - First REMIDI Module B - Second REMIDI Module C - Third REMIDI Module D - Fourth REMIDI Module M - Micro Peripheral Controller 6.1.1. File Names ____ _____ BOSS/VS IMAGES .R6Exx.INST.OS.CT 1/2 Inch Tape Boot, ADVANCED SERIES .R6Exx.INST.OS.CC 1/4 Inch Tape Boot, ADVANCED SERIES .R6Exx.INST.OS.AT 1/2 Inch Tape Boot, MPx 9xxx .R6Exx.INST.OS.AC 1/4 Inch Tape Boot, MPx 9xxx .R6Exx.INST.OS.BT 1/2 Inch Tape Boot, MPx 8xxx .R6Exx.INST.OS.BC 1/4 Inch Tape Boot, MPx 7xxx .R6Exx.INST.OS.UV Universal Disk Boot Image, MPx/ADVANCED SERIES DEMON IMAGES SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg034 .R6Exx.INST.DEMON.CD 1/2 Inch Tape Boot, ADVANCED SERIES .R6Exx.INST.DEMON.CC 1/4 Inch Tape Boot, ADVANCED SERIES .R6Exx.INST.DEMON.AD 1/2 Inch Tape Boot, MPx 9xxx .R6Exx.INST.DEMON.AC 1/4 Inch Tape Boot, MPx 9xxx .R6Exx.INST.DEMON.BD 1/2 Inch Tape Boot, MPx 8xxx .R6Exx.INST.DEMON.BC 1/4 Inch Tape Boot, MPx 7xxx .R6Exx.INST.DEMON.UV Universal Disk Boot Image, MPx/ADVANCED SERIES REMIDI MPx 7xxx/8xxx IMAGES .R6Exx.INST.REMIDI.BDM 1/2 Inch Tape Boot, MPC/LAN .R6Exx.INST.REMIDI.BCM 1/4 Inch Tape Boot, MPC/LAN .R6Exx.INST.REMIDI.BVM Disk Boot Image, MPC/LAN .R6Exx.INST.REMIDI.BD 1/2 Inch Tape Boot, CPU .R6Exx.INST.REMIDI.BC 1/4 Inch Tape Boot, CPU .R6Exx.INST.REMIDI.BV Disk Boot Image, CPU REMIDI MPx 9xxx IMAGES .R6Exx.INST.REMIDI.ADA 1/2 Inch Tape Boot Module 1 .R6Exx.INST.REMIDI.ADB 1/2 Inch Tape Boot Module 2 .R6Exx.INST.REMIDI.ADC 1/2 Inch Tape Boot Module 3 .R6Exx.INST.REMIDI.ADD 1/2 Inch Tape Boot Module 4 .R6Exx.INST.REMIDI.ACA 1/4 Inch Tape Boot Module 1 .R6Exx.INST.REMIDI.ACB 1/4 Inch Tape Boot Module 2 .R6Exx.INST.REMIDI.ACC 1/4 Inch Tape Boot Module 3 .R6Exx.INST.REMIDI.ACD 1/4 Inch Tape Boot Module 4 .R6Exx.INST.REMIDI.AVA Disk Boot Image for Module 1 & 2 .R6Exx.INST.REMIDI.AVC Disk Boot Image for Module 3 & 4 REMIDI ADVANCED SERIES IMAGES .R6Exx.INST.REMIDI.CD 1/2 Inch Tape Boot Module 1 through 4 .R6Exx.INST.REMIDI.CC 1/4 Inch Tape Boot Module 1 through 4 .R6Exx.INST.REMIDI.CVA Disk Boot Image Module 1 & 2 .R6Exx.INST.REMIDI.CVC Disk Boot Image Module 3 & 4 WCS FILES .R6Exx.INST.WCS.C WCS for ADVANCED SERIES .R6Exx.INST.WCS.A WCS for MPx 9xxx .R6Exx.INST.WCS.B WCS for MPx 8xxx/7xxx 6.2. GENERAL INFORMATION _______ ___________ IMPORTANT NOTE 1: AS OF RELEASES 9/8.6C, POSITIONING OF THE O.S. AND WCS SLOTS HAS BEEN ADJUSTED SLIGHTLY. THEREFORE, O.S./WCS LEVELS PRIOR TO 9/8.6C CANNOT RESIDE IN SLOTS ON THE SAME DISK WITH RELEASE LEVELS 10/9/8.6E. IMPORTANT NOTE 2: THE .SYSDATA.SECURITY.DATA FILE SHOULD BE SAVED BEFORE UPGRADING TO 10.6E/9.6E/8.6E IF YOUR CURRENT RELEASE IS BELOW 9/8.6C. AS OF RELEASES 9/8.6C, THE SECURITY.DATA FILE HAS A NEW FORMAT AND IS NOT TRANSPORTABLE TO RELEASES PRIOR TO 9/8.6C. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg035 IMPORTANT NOTE 3: IT IS NOT EXPECTED THAT A DOWNGRADE FROM 10/9/8.6E WILL BE NECESSARY. HOWEVER, IF A DOWNGRADE IS PERFORMED TO A RELEASE PRIOR TO 9/8.6C *11, THE USER'S FILES MUST BE TRANSPORTED TO THE OLDER O.S. LEVEL VIA EXTTAPE, MCSI, FTF, TBC, or ATP. FAILURE TO DO SO WILL RESULT IN INCOMPATIBLE FILE CONTROL SEGMENTS. THE VOLUME LABEL MUST ALSO BE REWRITTEN ON THE OLDER O.S. LEVEL. THERE ARE NO RESTRICTIONS ON A DOWNGRADE TO 9/8.6C *11. These Installation Instructions assume that the reader is familiar with BOSS/VS installation procedures and TYPE 3 LOAD Special Functions. For further information, see the BOSS/VS INSTALLATION GUIDE, M5138D. If you are installing the O.S. on a newly formatted System disk or changing a Data disk to a System disk on any system, go to section 6.3. If you are upgrading a 8xxx Series System to 8.6E from level 8.4D or below, go to section 6.4. If you are upgrading a 7xxx or 8xxx Series System to 8.6E from level 8.4E or above, go to section 6.5. If you are upgrading a 9xxx Series System to 9.6E, go to section 6.6. If you are upgrading an ADVANCED SERIES to 10.6E, go to section 6.7. If you have just received a new system, please note the following: New systems are shipped with the operating system installed on the disk, and the TYPE 3 LOAD (Special Functions) parameters already set up. If you wish to change the disk/family information on your new system, you must run Option 2 (Update Family Information) of INITIALIZATION OPTIONS (OPTION 2 on the main menu) in a TYPE 3 LOAD. (See section 6.3.1.2.2). For further information on setting up families on your system, see the BOSS/VS INSTALLATION GUIDE, M5138. After the families are set up to your satisfaction, go to section 6.3.1.3. Beginning with release 9.6A/8.6A there is a change in the way terminals are enabled for user logon at system load time. Initial enabling of the TERMINALS group, which allows users to logon, is now under user control through the use of the Startup Command File. If the file does not exist, the TERMINALS group is enabled automatically. Refer to section 6.9 for further information on the startup command file and startup procedures for JOB MANAGER, MAGNET, and the SPOOLER. Since the operating system can be released on 1/2" (reel) or 1/4" (cartridge) tape, the word "tape" means either media form. 6.3. NEW OPERATING SYSTEM INSTALLATION SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg036 ___ _________ ______ ____________ 6.3.1. INSTALLING THE OPERATING SYSTEM __________ ___ _________ ______ Follow the instructions in this section if you are creating a SYSTEM disk on a newly formatted disk, or if you are changing a DATA disk to a SYSTEM disk. 6.3.1.1. Loading Slots 0 and 1 Using ALT LOAD _______ _____ _ ___ _ _____ ___ ____ NOTE: ALT LOAD has been enhanced so that it will automatically load both slots 0 and 1 on a new installation. (WCS slots 2 and 3 are also loaded with the BOSS/VS WCS for formatting purposes only. The user needs to reload these slots with the REMIDI WCS files, using UPDATE.WCS. See the sections on updating slots 2 and 3 in this announcement.) To perform an ALT LOAD from tape follow these steps: A) Mount the new release tape in the tape drive. (All front panel load select switches should be OFF if using tape drive 0. Switch 1 should be ON if using tape drive 1.) B) Press the "ALT LOAD" button on the front panel. First, a proprietary message will be displayed, and then the following load screen: ____________________________________________________________________ Load PROM Version: x.x.x.x SYSTEM SERIAL NUMBER : 000-00000 Load Drive n SERIAL NUMBER CREATOR: 000-00000 WCS 0 Version: x.x.x CONFIGURATION CREATOR: 000-00000 OS 0 Version: 6.5.x.x CPUs ID #s : n Memory (Mb) : n.0 Disk Drives : n BOSS/VS LOAD FROM TAPE Tape Drives : n Printers : n HVDTs : n IMLCs : n Serial Ports: n Date Format MM/DD/YY: BMTCs : n/n DATE = MM/DD/YY: LAN Cntrlrs : n TIME = HH:MM:SS: SYSTEM PREFIX: (family).R6E15.SYS.,.R6E15.INST. System Default Family: (family) File System Write Thru: T/F User Default Family : (family) Per-File Write Through: T/F Installation Name : (name) File System Security : T/F ____________________________________________________________________ Key in the current DATE and TIME at the above prompts. The screen will then display: ____________________________________________________________________ L O A D I N G . . . SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg037 BOSS/VS Operating System Image Update Utility [version 6.5.x.x] OS/WCS information for drive n (nn): 0: ?????????????? ??????? | x x.x.x 1: ?????????????? ??.??.??.??? | ? ??.??.?? 2: -------------- -- -- -- --- | ????????? 3: ?????????????? ??????? | ????????? BOSS/VS Image File Name: (displays one of the following): OSN.CT0605xxxxx (ADVANCED SERIES) OSN.AT0605xxxxx (9x00 systems - 1/2-inch) OSN.AC0605xxxxx (9400 systems - 1/4-inch) OSN.BT0605xxxxx (8000 systems - 1/2-inch) OSN.BC0605xxxxx (7x00 systems - 1/4-inch) Target OS Slot (0/1/3) : '0' (or 1) Target WCS Slot (0-3) : '0' (or 1) Target Drives (0/1/All/Quit): (choose drive) ____________________________________________________________________ C) The Image File Name will be displayed by the system. Enter '0' or '1' at the slot prompts to load O.S. and WCS slots 0 and 1. Enter '0', '1', or 'All' at the drive prompt to update the appropriate drives. NOTE: Do not update drive 1 if it is a DATA disk and is to remain so. The system will now display: ___________________________________________________________________ Now updating WCS slot # n Update in progress: nn% Now updating BOSS/VS Image (displays one of the following): OSN.CT0605xxxxx (ADVANCED SERIES) OSN.AT0605xxxxx (9x00 systems - 1/2-inch) OSN.AC0605xxxxx (9400 systems - 1/4-inch) OSN.BT0605xxxxx (8000 systems - 1/2-inch) OSN.BC0605xxxxx (7x00 systems - 1/4-inch) Update in progress: nn% Image slot directory n/n:n Updates all complete. D O N E - R E A D Y F O R N O R M A L D I S K L O A D ___________________________________________________________________ When O.S. and WCS slots 0 and 1 have been updated, reload the system by pressing the LOAD switch. 6.3.1.2. TYPE 3 LOAD (Special Functions) ____ _ ____ ________ __________ NOTE: If any disk has a 'MASTER' status, no update to the SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg038 disk will be allowed. You must change the disk to a 'BACKUP' status in order to perform the TYPE 3 LOAD functions. To do this, select OPTION 4 (CHANGE MASTER/BACKUP STATUS) from the TYPE 3 LOAD main menu. Be sure to change the disk back to a 'MASTER' status after the TYPE 3 LOAD functions are completed (if this status is desired). This MASTER/BACKUP status is simply a flag which makes it possible to write-protect a disk. It is not to be confused with the disk configuration (e.g., SYSTEM, DATA, BACKUP) specified in Option 1 (Change Volume Label Information) of INITIALIZATION OPTIONS (OPTION 2 on the TYPE 3 LOAD main menu). Select OPTION 2 - INITIALIZATION OPTIONS Option 1 (Change Volume Label Information) must be done on all disks. Options 2 (Update Family Information) and 3 (Initialize Family Directory) must be done for each family. Option 4 (Change Installation Parameters) must be done on system disks only. 6.3.1.2.1. OPTION 1 (CHANGE VOLUME LABEL INFORMATION) ______ _ _______ ______ _____ ____________ All available disk drives will be displayed. An 'available' drive is any drive cabled to the system, whether enabled, disabled, powered ON or OFF. The selected drive entered in response to the Option 1 prompts must be online and ready. ENTER DRIVE NUMBER OF VOLUME LABEL TO CHANGE:__ (Enter volume label to change. The screen will change to display the information for only the drive whose volume label you choose.) SERIAL NUMBER _________ (Enter CR to accept current serial number.) DISK CONFIGURATION (1=SYSTEM, 2=DATA, 3=BACKUP) ____ (Enter the appropriate disk type.) SIZE OF DUMP AREA.....______ x 1024 BYTES (For system disks only, enter the size of the dump area displayed on the line below this prompt as the area needed for both main memory and shared memory controllers. If installation of additional memory and/or shared memory controllers is planned, increase the dump area size to accommodate them. See Field Bulletin # 211, "Computing Dump Area Size".) FILE SYSTEM SPACE ______ x 1000 SECTORS (Enter the number displayed at the bottom of the screen for this prompt. The display will appear as "CR=X" where X is the maximum space allowed.) UPDATE DISK VOLUME LABEL (Y/N) __ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg039 (Enter "Y" if above information is correct.) Repeat the steps in 6.3.1.2.1 for all remaining disk drives. 6.3.1.2.2. OPTION 2 (UPDATE FAMILY INFORMATION) ______ _ _______ ______ ____________ NOTE: Removable drives can only have one member per family. Fixed drives can be combined to create a larger capacity disk family. The disk information for all drives on the system is displayed and the cursor is positioned at 'FAMILY BASE DRIVE NUMBER'. FAMILY BASE DRIVE NUMBER ___ FAMILY NAME ______ (CR for default family name.) DRIVE NUMBERS OF OTHER DISKS IN FAMILY? (TYPE SPACES FOR NO OTHER DRIVES) (Enter all other drive numbers for this family or spaces if none. The drives must be fixed media drives.) UPDATE DISK (Y/N)? Repeat the steps in 6.3.1.2.2 until all drives are identified in a family. 6.3.1.2.3. OPTION 3 (INITIALIZE FAMILY DIRECTORY) ______ _ ___________ ______ __________ This option displays all base drives on the system. FAMILY BASE DRIVE NUMBER ______ (Enter drive number to be initialized.) INITIALIZE FAMILY? (Y/N) __ (CAUTION: Insure that all data you want is backed up. This step will delete all data on the disk.) Repeat the steps in 6.3.1.2.3 for all defined families. 6.3.1.2.4. OPTION 4 (CHANGE INSTALLATION PARAMETERS) ______ _ _______ ____________ ___________ NOTE: On newly formatted disks, the following message will be displayed: "CAN'T READ INITIALIZATION PARAMETERS FROM DISK. STATUS = [3,7,30,1], TO CONTINUE:" Just press and continue. Only SYSTEM disks will be displayed. DRIVE NUMBER _______ PRIMARY PREFIX __________________ (Enter (family).R6E15.SYS. (Family) is the primary family name on which the OS/WCS image files reside SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg040 for slot 0.) SECONDARY PREFIX _______________ (Enter (family).R6E15.SYS. (Family) is the family where the alternate OS/WCS image files reside for slot 1.) SYSTEM INSTALLATION NAME ________________ (Sets the default installation name for a specified system disk. Used only with MAGNET. Enter for default.) DEFAULT USER FAMILY NAME _____________ (Enter default user family.) SECURITY (E=ENABLED, D=DISABLED) ___ FILE SYSTEM WRITE THROUGH? (E=ENABLED, D=DISABLED) ___ WRITE THROUGH DEFAULT ON FILE CREATE (E=ENABLED, D=DISABLED):__ (This parameter specifies what the default write through will be on a file created through a BASIC file create or through the CREATE utility.) UPDATE DISK WITH INSTALLATION PARAMETERS? (Y/N) __ Display: INSTALLATION PARAMETERS SUCCESSFULLY WRITTEN TO DISK. (CR) TO CONTINUE: Repeat the steps in 6.3.1.2.4 for any additional system disks. If you changed your disk from a 'MASTER' status to a 'BACKUP' status to do the TYPE 3 LOAD functions, change it back to a 'MASTER' status at this point. Reload the system by pressing the LOAD switch. Be sure you are loading from the drive where you wish to restore the operating system files. 6.3.1.3. Restoring the O.S. _________ ___ ____ Enter SAVERESTORE in a TYPE 2 LOAD and choose OPTION 2 RESTORE FILES FROM TAPE. The screen appears as in figure 6-1. At the prompt for output device, enter a parallel printer so that a listing of the restore operation is produced. This listing can be used to make sure all files were restored correctly. On the next screen, at the prompt, "FILE SPECIFIERS", enter ".". Then enter twice. All system files will be restored to disk. Once all files are restored to disk, the message "AUTOMATIC COMPARE, CR TO CONTINUE" appears. This automatically rewinds the tape and begins the compare operation. This only occurs when the compare option is selected. When the compare is completed, enter a CTL-IV to return to the "SAVERESTORE" menu. Reload the system and enter a TYPE 1 LOAD. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg041 Figure 6-1. Restore Screen ______ ____ _______ ______ -------------------------------------------------------- RESTORE FILES TAPE SET.ID: DRIVE-NUM: REEL-NUM: PRIMARY PREFIX: (FAMILY).NODE. FILE TYPE (D/P/CR=ALL) COMPARE (CR=Y/N) DATE (MM/DD/YY) TIME (HH:MM) OUTPUT DEVICE (CR=VDT) DELETE EXISTING FILES (CR=Y) VERIFY (Y/CR=N) ENTRIES CORRECT (Y/N) -------------------------------------------------------- At this point it is necessary to install the System Serial Number (using GENSSN) on newly formatted disks and DATA disks that you are changing to SYSTEM disks. 6.3.2. INSTALLING THE CONFIGURATION RECORD __________ ___ _____________ ______ It is necessary to install a new configuration record when installing a new system and when upgrading to 8.6E from 8.4 and 8.5 O.S. levels. Until the following procedure is completed, the system will have a minimum configuration. New systems normally already have a configuration record installed. If you have a new system, and you want to verify that the configuration record has been installed, run the CONFIG.MGR utility in a TYPE 1 LOAD. If the configuration record has already been installed, you may skip this section. Enter a TYPE 1 LOAD. Set your prefix to .SYSTEM.CONFIG. Using the SAVERESTORE utility, restore the new configuration record on tape onto your system. Execute the CONFIG.MGR utility. The CONFIG.MGR utility allows the user to update the system configuration record by installing a new configuration file. This utility displays the current and new configuration record. When "Y" is answered to the prompt "Install Configuration:", the new configuration is copied from the file ".SYSTEM.CONFIG.I(serial number)", to the special system area on disk. The new configuration takes effect at the next system load. For further details on the use of the CONFIG.MGR utility, see the 8.5D/9.5D Software Announcement #139, or the BOSS/VS Utility User Guide, M5102. The configuration record file name is derived from the system serial number by changing the leading "8" to an "I" and adding the prefix ".SYSTEM.CONFIG.". SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg042 EXAMPLE: .SYSTEM.CONFIG.I1030114 for SSN 810-30114 This configuration record tape should be saved, in case reinstallation should become necessary. Before going to the next step, LOAD the system so the new ____ configuration record will take effect. If you do not load the system, you will have a minimum configuration and the system will be very slow. If you are installing a 7xxx/8xxx system, go to section 6.5.4 to load the remaining slots. If you are installing a 9xxx system, go to section 6.6.6 to load the remaining slots. 6.4. UPGRADING TO 8.6E FROM RELEASE LEVELS 8.4D AND BELOW _________ __ ____ ____ _______ ______ ____ ___ _____ 6.4.1. INTRODUCTION ____________ NOTE: This section contains references to the FILESIZE, NFSCONVERT, and DISKANALYZER utilities. Further information on these utilities and their use during file conversion can be found in the following sources: - BOSS/VS FILE CONVERSION GUIDE, M5185 - BOSS/VS UTILITY USER GUIDE, M5102 - Software Announcements for release levels 8.4E and 8.5A/B/C/D - HELP SCREENS accessed by keying in UTILITYNAME.HELP in command mode Since release levels 8.4E and above contain new file formats and a new file system, conversion of files is required to make files compatible with the new file system, if you are upgrading from a software release level of 8.4D or below. The file conversion can be done in two ways: A) From tape to disk B) From disk to disk Which method used depends on the configuration of the system. The disk to disk method is preferable for a system with removable disks. The disk to disk method involves upgrading the system disk with the new O.S. Then the system disk can be used to convert other disks by using the NFSCONVERT utility to convert one file from one disk to another. If the disk to disk method is used on fixed disks, any user files must be copied from the fixed system disk to another disk or to tape for conversion. This is because the system disk must be initialized and updated to the new O.S. to do the conversion. To do a tape conversion, a save and restore is performed with the SAVERESTORE utility in the normal manner. The conversion process is invisible to the user with the exception of the SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg043 following status message that is displayed during conversion: "Now converting to NFS format...." The tape conversion requires about 4 minutes per megabyte of data. The installation procedure is broken into two parts: A) Preliminary evaluation B) Operating System upgrade and file conversion The preliminary evaluation is required to ensure that proper hardware and file preparation is done. An O.S. upgrade from releases of 8.4D and below entails loading of the 8.6E O.S. and converting files to their new format. The conversion process, in large configurations, will take more than one day. At the end of this section is an upgrade and conversion checklist that should be used to track progress through the upgrade procedure. 6.4.2. PRELIMINARY EVALUATION ___________ __________ The preliminary section deals with revision levels and file preparation. 6.4.2.1. Hardware Evaluation ________ __________ All hardware must be checked for proper operation. All boards must be at proper revision levels (see the HARDWARE section in this announcement.) Ensure that all tape units are operating correctly. 6.4.2.2. File Preparation ____ ___________ Obtain a directory listing with partial attributes for each family in the system. This listing will help you to find files, if any, that need repair before conversion. Next, using DISKANALYZER, select the option "VALIDATE ALL FILES" to determine which files need repair. Files which have the following attributes MUST be repaired before they are saved to tape: A) Files which lack integrity. B) Files which have lost space. C) Non-serial files in which records used is greater than records defined. D) Files that have invalid format. These files can be located in several ways: A) Scan the directory listing noting any files SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg044 flagged as lacking integrity. B) Use the report generated by the DISKANALYZER "VALIDATE ALL FILES" option. (Preferred method) C) Use the utility FINDLOSTSPACE (8.4C/D only). All of the above methods should be used to find files that lack integrity and that have lost space. However, the directory listing must be scanned to find files that have a greater number of records used then defined as maximum records. This is a very important step. Any file possessing any of these attributes WILL NOT convert properly. They have to be repaired on a previous release before conversion. Any EDITOR recovery files must be recovered or deleted before conversion. The recovery files are identified by the node ED.REC. After the node, there will be a series of digits. These files can be found by scanning the directory listing. These files must be recovered by using EDIT.RECOVER or deleted by using the DELETE utility. ***************************************** * * * ALL FILES MUST BE FREE FROM LACK OF * * INTEGRITY, LOST SPACE, AND MAX * * RECORDS GREATER THAN DEFINED RECORDS. * * FILES WILL NOT BE CONVERTED IF THEY * * POSSESS ANY ONE OF THESE ATTRIBUTES. * * * ***************************************** 6.4.2.3. New File System Space Requirements ___ ____ ______ _____ ____________ The space required for files under the new file system are about the same as under 8.4D/C/B/A levels. However, it is recommended that a listing be obtained which displays the files and their new sizes. On the 8.4D release, the program FILESIZE is used to produce this listing. The program FILESIZE will display the file size under the new file system for each file in a given family. It will also display the total number of sectors required by the entire family under the new file system. 6.4.2.4. Saving Files to Tape ______ _____ __ ____ User files and the .SYSDATA. node must now be backed up to tape. It is STRONGLY recommended that these files be saved to tape even if disk to disk conversion is being used. This will allow recovery of files in case of problems with the disk to disk conversion. It is necessary to save the .SYSDATA. node to preserve all system parameters. This node must be restored on the new file system along with the user files. It is essential that the .SYSDATA.SECURITY.DATA file be backed SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg045 up before upgrading to 8.6E and saved for a period of time on tape. This SECURITY.DATA file will go through a conversion during the upgrade, and the converted file cannot be used on previous O.S. levels. The old version of SECURITY.DATA should be kept in the event of an O.S. downgrade. The files are saved using the standard tape utility, SAVERESTORE. When saving files to tape, send the output from the save process to the printer. These will provide a record of backup for each file. Also it is recommended that all tapes be compared to the files on the disk. When using the tape or disk conversion, the conversion requires temporary disk space to sort keyed (direct and sort) files. The space required varies with the number of records and the size of the key. To insure proper space is available, the following steps should be observed: A) Do not restore the user default family until last. B) Convert large keyed files first. Step A insures that the default user disk has a large amount of free space since this is where the tape and disk conversion utility defines the temporary files. Step B allows the files that require the most amount of temporary space to be converted first. To convert large keyed files first, they must be saved to tape first. The large keyed files can be identified by scanning the directory listing obtained in section 6.4.2.2. If using disk to disk conversion, the NFSCONVERT utility allows you to convert keyed files first. 6.4.3. OPERATING SYSTEM UPDATE and FILE CONVERSION _________ ______ ______ ___ ____ __________ 6.4.3.1. Installing the O.S. __________ ___ ____ 6.4.3.1.1. Loading Slots 0 and 1 Using ALT LOAD _______ _____ _ ___ _ _____ ___ ____ NOTE: As of releases 9/8.6C, positioning of the O.S./WCS slots has been adjusted slightly. Therefore, O.S. levels previous to 9/8.6C cannot reside in slots on the same disk with O.S. levels 9/8.6C and above. For this reason, ALT LOAD has been enhanced so that it will automatically load both slots 0 and 1 if one of the following three conditions is true: 1) You are upgrading from a release prior to 9/8.6C. 2) You are updating a newly formatted disk. 3) You are changing a DATA disk to a SYSTEM disk. If any of the above three conditions are true, WCS slots 2 and 3 are also loaded with the BOSS/VS WCS for formatting purposes only. The user needs to reload these slots with SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg046 the REMIDI WCS files, using UPDATE.WCS. See the sections on updating slots 2 and 3 in this announcement. If you are upgrading to 10/9/8.6E from 9/8.6C, or if you are reinstalling 10/9/8.6E (over itself), the ALT LOAD procedure must be run twice - once to load O.S. and WCS slots 0, and once to load O.S. and WCS slots 1. To perform an ALT LOAD from tape follow these steps: A) Mount the new release tape in the tape drive. (All front panel load select switches should be OFF if using tape drive 0. Switch 1 should be ON if using tape drive 1.) B) Press the "ALT LOAD" button on the front panel. First, a proprietary message will be displayed, and then the following load screen: ____________________________________________________________________ Load PROM Version: x.x.x.x SYSTEM SERIAL NUMBER : 000-00000 Load Drive n SERIAL NUMBER CREATOR: 000-00000 WCS 0 Version: x.x.x CONFIGURATION CREATOR: 000-00000 OS 0 Version: 6.5.x.x CPUs ID #s : n Memory (Mb) : n.0 Disk Drives : n BOSS/VS LOAD FROM TAPE Tape Drives : n Printers : n HVDTs : n IMLCs : n Serial Ports: n Date Format MM/DD/YY: BMTCs : n/n DATE = MM/DD/YY: LAN Cntrlrs : n TIME = HH:MM:SS: SYSTEM PREFIX: (family).R6E15.SYS.,.R6E15.INST. System Default Family: (family) File System Write Thru: T/F User Default Family : (family) Per-File Write Through: T/F Installation Name : (name) File System Security : T/F ____________________________________________________________________ Key in the current DATE and TIME at the above prompts. The screen will then display: ____________________________________________________________________ L O A D I N G . . . BOSS/VS Operating System Image Update Utility [version 6.5.x.x] OS/WCS information for drive n (nn): 0: ?????????????? ??????? | x x.x.x 1: ?????????????? ??.??.??.??? | ? ??.??.?? 2: -------------- -- -- -- --- | ????????? 3: ?????????????? ??????? | ????????? BOSS/VS Image File Name: (displays one of the following): OSN.CT0605xxxxx (ADVANCED SERIES) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg047 OSN.AT0605xxxxx (9x00 systems - 1/2-inch) OSN.AC0605xxxxx (9400 systems - 1/4-inch) OSN.BT0605xxxxx (8000 systems - 1/2-inch) OSN.BC0605xxxxx (7x00 systems - 1/4-inch) Target OS Slot (0/1/3) : '0' (or 1) Target WCS Slot (0-3) : '0' (or 1) Target Drives (0/1/All/Quit): (choose drive) ____________________________________________________________________ C) The Image File Name will be displayed by the system. Enter '0' or '1' at the slot prompts to load O.S. and WCS slots 0 and 1. Enter '0', '1', or 'All' at the drive prompt to update the appropriate drives. NOTE: Do not update drive 1 if it is a DATA disk and is to remain so. The system will now display: ___________________________________________________________________ Now updating WCS slot # n Update in progress: nn% Now updating BOSS/VS Image (displays one of the following): OSN.CT0605xxxxx (ADVANCED SERIES) OSN.AT0605xxxxx (9x00 systems - 1/2-inch) OSN.AC0605xxxxx (9400 systems - 1/4-inch) OSN.BT0605xxxxx (8000 systems - 1/2-inch) OSN.BC0605xxxxx (7x00 systems - 1/4-inch) Update in progress: nn% Image slot directory n/n:n Updates all complete. D O N E - R E A D Y F O R N O R M A L D I S K L O A D ___________________________________________________________________ If you are upgrading to 10/9/8.6E from 9/8.6C or from another star ("*") level of 10/9/8.6E, repeat this procedure for O.S. and WCS slots 1. When O.S. and WCS slots 0 and 1 have been updated, reload the system by pressing the LOAD switch. 6.4.3.1.2. TYPE 3 LOAD (SPECIAL FUNCTIONS) ____ _ ____ ________ __________ NOTE 1: When using NFSCONVERT, the following steps should only be performed on the destination disk (which will be in new File System format). NOTE 2: If any disk has a 'MASTER' status, no update to the disk will be allowed. You must change the disk to a 'BACKUP' status in order to perform the TYPE 3 LOAD functions. To do this, select OPTION 4 (CHANGE MASTER/BACKUP STATUS) from the TYPE 3 LOAD main menu. Be sure to change the disk back to a SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg048 'MASTER' status after the TYPE 3 LOAD functions are completed (if this status is desired). This MASTER/BACKUP status is simply a flag which makes it possible to write-protect a disk. It is not to be confused with the disk configuration (e.g., SYSTEM, DATA, BACKUP) specified in Option 1 (Change Volume Label Information) of INITIALIZATION OPTIONS (OPTION 2 on the TYPE 3 LOAD main menu). OPTION 2 - INITIALIZATION OPTIONS INITIALIZATION OPTIONS 1-4 must be done to insure proper operation. Option 1 must be done for all disks. Option 2 must be done for the system disk. Options 3 and 4 must be done for all families. 6.4.3.1.2.1. OPTION 1 (CHANGE VOLUME LABEL INFORMATION) ______ _ _______ ______ _____ ____________ All available disk drives will be displayed. An 'available' drive is any drive cabled to the system, whether enabled, disabled, powered ON or OFF. The selected drive entered in response to the Option 1 prompts must be online and ready. ENTER DRIVE NUMBER OF VOLUME LABEL TO CHANGE:__ (The screen will change to display the information for only the drive whose volume label you choose.) SERIAL NUMBER _________ (Enter CR to accept current serial number.) DISK CONFIGURATION (1=SYSTEM, 2=DATA, 3=BACKUP) ____ (Enter the appropriate disk type.) SIZE OF DUMP AREA.....______ x 1024 BYTES (For system disks only, enter the size of the dump area displayed on the line below this prompt as the area needed for both main memory and shared memory controllers. If installation of additional memory and/or shared memory controllers is planned, increase the dump area size to accommodate them. See Field Bulletin # 211, "Computing Dump Area Size".) FILE SYSTEM SPACE ______ x 1000 SECTORS (Enter the number displayed at the bottom of the screen for this prompt. The display will appear as "CR=X" where X is the maximum space allowed.) UPDATE DISK VOLUME LABEL (Y/N) __ (Enter "Y" if above information is correct.) 6.4.3.1.2.2. OPTION 2 (UPDATE FAMILY INFORMATION) ______ _ _______ ______ ____________ The disk information for all drives on the system is displayed and the cursor is positioned at 'FAMILY BASE DRIVE NUMBER'. FAMILY BASE DRIVE NUMBER ___ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg049 FAMILY NAME ______ (CR for default family name.) DRIVE NUMBERS OF OTHER DISKS IN FAMILY? (TYPE SPACES FOR NO OTHER DRIVES) (Enter all other drive numbers for this family or spaces if none. The drives must be fixed media drives and in new file system format.) UPDATE DISK (Y/N)? 6.4.3.1.2.3. OPTION 3 (INITIALIZE FAMILY DIRECTORY) ______ _ ___________ ______ __________ This option displays all family base drives on the system. FAMILY BASE DRIVE NUMBER ______ (Enter drive number to be initialized.) INITIALIZE FAMILY? (Y/N) __ 6.4.3.1.2.4. OPTION 4 (CHANGE INSTALLATION PARAMETERS) ______ _ _______ ____________ ___________ Only system disks will be displayed. DRIVE NUMBER _______ PRIMARY PREFIX __________________ (Enter (family).R6E15.SYS. (Family) is the family where the operating system files will reside.) SECONDARY PREFIX _______________ (Enter (family).R6E15.SYS. (Family) is the family where the alternate operating system files will reside.) SYSTEM INSTALLATION NAME ________________ (Sets the default installation name for a specified system disk.) DEFAULT USER FAMILY NAME _____________ (Enter default user family.) SECURITY (E=ENABLED, D=DISABLED) ___ FILE SYSTEM WRITE THROUGH? (E=ENABLED, D=DISABLED) ___ (For conversion purposes, set this option to 'D' for DISABLED. This will speed up the conversion process and can be changed later if needed.) WRITE THROUGH DEFAULT ON FILE CREATE (E=ENABLED, D=DISABLED):__ (This parameter specifies what the default write through will be on a file created through a BASIC file create or through the CREATE utility.) UPDATE DISK WITH INSTALLATION PARAMETERS? (Y/N) __ Display: INSTALLATION PARAMETERS SUCCESSFULLY WRITTEN TO DISK. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg050 (CR) TO CONTINUE: Reload the system by pressing the LOAD switch. 6.4.3.1.3. Restoring the O.S. _________ ___ ____ Enter SAVERESTORE in a TYPE II load and choose option #2 "RESTORE FILES FROM TAPE". The screen appears as in figure 6-2. Figure 6-2. Restore Screen ______ ____ _______ ______ -------------------------------------------------------- RESTORE FILES TAPE SET.ID: DRIVE-NUM: REEL-NUM: PRIMARY PREFIX: (FAMILY).NODE. FILETYPE (D/P/CR=ALL) COMPARE (CR=Y/N) DATE (MM/DD/YY) TIME (HH:MM) OUTPUT DEVICE (CR=VDT) DELETE EXISTING FILES (CR=Y) VERIFY (Y/CR=N) ENTRIES CORRECT (Y/N) -------------------------------------------------------- At each prompt, enter a . At the prompt, "FILE SPECIFIERS", enter ".". Then enter twice. This will restore all the files on the release tape to disk. Please note that once all files are restored to disk, the message "AUTOMATIC COMPARE, CR TO CONTINUE" appears. This automatically rewinds the tape and begins the compare operation. This only occurs when the compare option is selected. When the compare is completed, enter a CTL-IV to return to the "SAVERESTORE" menu. 6.4.3.2. INSTALLING THE CONFIGURATION RECORD __________ ___ _____________ ______ It is necessary to install a new configuration record when installing a new system disk and when upgrading to 10/9/8.6E from 8.4 and 8.5 O.S. levels. Until the following procedure is completed, the system will have a minimum configuration. Enter a TYPE 1 LOAD. Set your prefix to .SYSTEM.CONFIG. Before you load the new configuration record, rename the current configuration record on your system, using the RENAME utility, to temporarily preserve it for fall back purposes. (e.g. Add "OLD" in front of the name.) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg051 Using the SAVERESTORE utility, restore the new configuration record on tape onto your system. Execute the CONFIG.MGR utility. The CONFIG.MGR utility allows the user to update the system configuration record by installing a new configuration file. This utility displays the current and new configuration record. When "Y" is answered to the prompt "Install Configuration:", the new configuration is copied from the file ".SYSTEM.CONFIG.I(serial number)", to the special system area on disk. The new configuration takes effect at the next system load. For further details on the use of the CONFIG.MGR utility, see the 9.5D/8.5D Software Announcement #139, or the BOSS/VS UTILITY USER GUIDE, M5102. The configuration record file name is derived from the system serial number by changing the leading "8" to an "I" and adding the prefix ".SYSTEM.CONFIG.". EXAMPLE: .SYSTEM.CONFIG.I1030114 for SSN 810-30114 This configuration record tape should be saved, in case reinstallation should become necessary. Before going to the next step, LOAD the system so the new ____ configuration record will take affect. If you do not load the system, you will have a minimum configuration and the system will be very slow. 6.4.3.3. CONVERTING FILES __________ _____ If doing tape to disk conversion see section 6.4.3.3.1. If doing disk to disk conversion see section 6.4.3.3.2. 6.4.3.3.1. Tape to Disk Conversion ____ __ ____ __________ Mount the first tape to restore, enter the SAVERESTORE utility, and select option #2. A screen as in figure 6-2 will appear. Answer all prompts as in the figure. Make sure that you direct the output to a printer. This will provide you with a "history" of the restore operation. Each file is converted to the new file format as it is restored. The conversion to the new file format will be entirely invisible except for a pause at the completion of restoring a file. This pause, which can last a few seconds to a few hours depending on file size, indicates the file is being converted to the new file format. Occasionally the message "...CONVERTING FILE TO NFS..." will appear as a visual indicator of file conversion. System files from the previous release need not be restored. However, to preserve all system parameters, the .SYSDATA. node must be restored from the backup tapes. Tapes made on a releases of 8.4D and below cannot be compared when restored to the new file system. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg052 After all files have been restored, reload the system so the SECURITY.DATA file will be converted to the new 9/8.6E format and the terminal definition files will take effect. Now go to section 6.4.3.3.3. 6.4.3.3.2. Disk to Disk Conversion ____ __ ____ __________ The utility NFSCONVERT is used to convert files from the old format to the new file format. The destination disk must be in new file system format as described in section 6.4.3.1.2. The source disk must be in old file system format. When using disk to disk conversion, only one family may be converted per terminal. You cannot start NFSCONVERT on two terminals converting different parts of the same family. You can convert different families at the same time. As in the tape to disk conversion, the .SYSDATA. node must be converted to preserve system parameters and configurations. 6.4.3.3.3. Check Files _____ _____ Once all files have been converted, the DISKANALYZER "VALIDATE ALL FILES" option should be used on each family. DISKANALYZER can be used in a TYPE II load or a TYPE I load. Once all files have been validated, enter a TYPE I load, (if you have not already done so). 6.4.4. UPDATING THE TERMINAL CONFIGURATION FILE ________ ___ ________ _____________ ____ The terminal configuration file must be updated to the new file system format. This update will allow all other devices to become accessible. The file is updated by entering TERM.CONFIG and choosing the update option. Enter PRIMARY as the file to change. Enter an existing ISDC and display one of the ISDC ports. Enter a MB-IV to exit the update without changing anything. The utility will say that the file has been modified and do you want to save it. Respond with YES. Now reload the system to allow the devices to become active. Now go to section 6.5.4 to complete the last step of the installation. 7xxx/8xxx UPGRADE AND CONVERSION CHECKLIST _________ _______ ___ __________ _________ 1) Hardware levels => section 5 2) Validate files => section 6.4.2.2 A) DISKANALYZER option "VALIDATE ALL FILES" B) DIR listings C) FINDLOSTSPACE Utility D) Delete unwanted EDITOR,SPOOL, and TEMP files SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg053 3) New file sizes => section 6.4.2.3 A) FILESIZE utility 4) Save files to tape => section 6.4.2.4 A) Large keyed files first 5) Update operating system => section 6.4.3.1 A) ALT-LOAD B) Options 1-4 C) Restore operating system files 6) File conversion A) Tape-to-disk => section 6.4.3.3.1 B) Disk-to-disk => section 6.4.3.3.2 7) Check file integrity => section 6.4.3.3.3 8) Complete installation A) Update terminal configuration file => section 6.4.4 B) Update slots 2 and 3 => section 6.5.4 6.5. UPGRADING TO 8.6E FROM RELEASE LEVELS 8.4E AND ABOVE _________ __ ____ ____ _______ ______ ____ ___ _____ If you are installing the 8.6E O.S. on a newly formatted System disk or changing a Data disk to a System disk, go to section 6.3. 6.5.1. SAVING FILES TO TAPE ______ _____ __ ____ Current files must first be backed up to tape, using the standard tape utility, SAVERESTORE. When saving files to tape, send the output from the save process to the printer. This will provide a record of backup for each file. Also, it is recommended that all files on tape be compared to the files on the disk. NOTE: It is essential that the .SYSDATA.SECURITY.DATA file be backed up before upgrading to 8.6E, if your current O.S. level is below 8.6C. This SECURITY.DATA file will go through a conversion during the upgrade, and the converted file cannot be used on previous O.S. levels. The old version of SECURITY.DATA should be saved in case an O.S. downgrade is ever necessary. 6.5.2. OPERATING SYSTEM UPDATE _________ ______ ______ 6.5.2.1. Loading Slots 0 and 1 Using ALT LOAD _______ _____ _ ___ _ _____ ___ ____ NOTE: As of releases 9/8.6C, positioning of the O.S./WCS slots has been adjusted slightly. Therefore, O.S. levels previous to 9/8.6C cannot reside in slots on the same disk SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg054 with O.S. levels 9/8.6C and above. For this reason, ALT LOAD has been enhanced so that it will automatically load both slots 0 and 1 if one of the following three conditions is true: 1) You are upgrading from a release prior to 9/8.6C. 2) You are updating a newly formatted disk. 3) You are changing a DATA disk to a SYSTEM disk. If any of the above three conditions are true, WCS slots 2 and 3 are also loaded with the BOSS/VS WCS for formatting purposes only. The user needs to reload these slots with the REMIDI WCS files, using UPDATE.WCS. See the sections on updating slots 2 and 3 in this announcement. If you are upgrading to 10/9/8.6E from 9/8.6C, or if you are reinstalling 10/9/8.6E (over itself), the ALT LOAD procedure must be run twice - once to load O.S. and WCS slots 0, and once to load O.S. and WCS slots 1. To perform an ALT LOAD from tape follow these steps: A) Mount the new release tape in the tape drive. (All front panel load select switches should be OFF if using tape drive 0. Switch 1 should be ON if using tape drive 1.) B) Press the "ALT LOAD" button on the front panel. First, a proprietary message will be displayed, and then the following load screen: ____________________________________________________________________ Load PROM Version: x.x.x.x SYSTEM SERIAL NUMBER : 000-00000 Load Drive n SERIAL NUMBER CREATOR: 000-00000 WCS 0 Version: x.x.x CONFIGURATION CREATOR: 000-00000 OS 0 Version: 6.5.x.x `"A Drives : n Printers : n HVDTs : n IMLCs : n Serial Ports: n Date Format MM/DD/YY: BMTCs : n/n DATE = MM/DD/YY: LAN Cntrlrs : n TIME = HH:MM:SS: SYSTEM PREFIX: (family).R6E15.SYS.,.R6E15.INST. System Default Family: (family) File System Write Thru: T/F User Default Family : (family) Per-File Write Through: T/F Installation Name : (name) File System Security : T/F ____________________________________________________________________ Key in the current DATE and TIME at the above prompts. The screen will then display: ____________________________________________________________________ L O A D I N G . . . SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg055 BOSS/VS Operating System Image Update Utility [version 6.5.x.x] OS/WCS information for drive n (nn): 0: ?????????????? ??????? | x x.x.x 1: ?????????????? ??.??.??.??? | ? ??.??.?? 2: -------------- -- -- -- --- | ????????? 3: ?????????????? ??????? | ????????? BOSS/VS Image File Name: (displays one of the following): OSN.CT0605xxxxx (ADVANCED SERIES) OSN.AT0605xxxxx (9x00 systems - 1/2-inch) OSN.AC0605xxxxx (9400 systems - 1/4-inch) OSN.BT0605xxxxx (8000 systems - 1/2-inch) OSN.BC0605xxxxx (7x00 systems - 1/4-inch) Target OS Slot (0/1/3) : '0' (or 1) Target WCS Slot (0-3) : '0' (or 1) Target Drives (0/1/All/Quit): (choose drive) ____________________________________________________________________ C) The Image File Name will be displayed by the system. Enter '0' or '1' at the slot prompts to load O.S. and WCS slots 0 and 1. Enter '0', '1', or 'All' at the drive prompt to update the appropriate drives. NOTE: Do not update drive 1 if it is a DATA disk and is to remain so. The system will now display: ___________________________________________________________________ Now updating WCS slot # n Update in progress: nn% Now updating BOSS/VS Image (displays one of the following): OSN.CT0605xxxxx (ADVANCED SERIES) OSN.AT0605xxxxx (9x00 systems - 1/2-inch) OSN.AC0605xxxxx (9400 systems - 1/4-inch) OSN.BT0605xxxxx (8000 systems - 1/2-inch) OSN.BC0605xxxxx (7x00 systems - 1/4-inch) Update in progress: nn% Image slot directory n/n:n Updates all complete. D O N E - R E A D Y F O R N O R M A L D I S K L O A D ___________________________________________________________________ If you are upgrading to 10/9/8.6E from 9/8.6C or from another star ("*") level of 10/9/8.6E, repeat this procedure for O.S. and WCS slots 1. When O.S. and WCS slots 0 and 1 have been updated, reload the system by pressing the LOAD switch. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg056 6.5.2.2. Changing Installation Parameters ________ ____________ __________ Enter a TYPE 3 LOAD (SPECIAL FUNCTIONS) and select OPTION 2 (INITIALIZATION OPTIONS). OPTION 2 - INITIALIZATION OPTIONS Option 4 - CHANGE INSTALLATION PARAMETERS Only system disks will be displayed. DRIVE NUMBER _______ PRIMARY PREFIX _______________________ (Enter (family).R6E15.SYS. (Family) is the family where the operating system files reside.) SECONDARY PREFIX _____________________ (Enter (family).R6E15.SYS. (Family) is the family where the alternate operating system files reside.) SYSTEM INSTALLATION NAME _________________________ (Sets the default installation name for a specified system disk.) DEFAULT USER FAMILY NAME ________ (Enter default user family.) SECURITY (E=ENABLED, D=DISABLED) ___ FILE SYSTEM WRITE THROUGH? (E=ENABLED, D=DISABLED) ___ WRITE THROUGH DEFAULT ON FILE CREATE (E=ENABLED, D=DISABLED) __ (This parameter specifies what the default write through will be on a file created through a BASIC file create or through the CREATE utility.) UPDATE DISK WITH INSTALLATION PARAMETERS? (Y/N)__ Display: INSTALLATION PARAMETERS SUCCESSFULLY WRITTEN TO DISK (CR) TO CONTINUE: Reload the system by pressing the LOAD switch. 6.5.2.3. Restoring the O.S. _________ ___ ____ Enter SAVERESTORE in a TYPE 2 LOAD and choose OPTION 2 RESTORE FILES FROM TAPE. The screen appears as in figure 6-2. At the prompt, "FILE SPECIFIERS", enter ".". Then enter twice. This will restore all files on the release tape to disk. Figure 6-3. Restore Screen ______ ____ _______ ______ -------------------------------------------------------- RESTORE FILES SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg057 TAPE SET.ID: DRIVE-NUM: REEL-NUM: PRIMARY PREFIX: (FAMILY).NODE. FILE TYPE (D/P/CR=ALL) COMPARE (CR=Y/N) DATE (MM/DD/YY) TIME (HH:MM) OUTPUT DEVICE (CR=VDT) DELETE EXISTING FILES (CR=Y) VERIFY (Y/CR=N) ENTRIES CORRECT (Y/N) -------------------------------------------------------- At each prompt, enter a . Please note that once all files are restored to disk, the message "AUTOMATIC COMPARE, CR TO CONTINUE" appears. This automatically rewinds the tape and begins the compare operation. This only occurs when the compare option is selected. When the compare is completed, enter a CTL-IV to return to the "SAVERESTORE" menu. 6.5.3. INSTALLING THE CONFIGURATION RECORD __________ ___ _____________ ______ It is necessary to install a new configuration record when installing a new system disk and when upgrading to 10/9/8.6E from 8.4 and 8.5 O.S. levels. Until the following procedure is completed, the system will have a minimum configuration. Enter a TYPE 1 LOAD. Set your prefix to .SYSTEM.CONFIG. Before you load the new configuration record, rename the current configuration record on your system, using the RENAME utility, to temporarily preserve it for fall back purposes. (e.g. Add "OLD" in front of the name.) Using the SAVERESTORE utility, restore the new configuration record on tape onto your system. Execute the CONFIG.MGR utility. The CONFIG.MGR utility allows the user to update the system configuration record by installing a new configuration file. This utility displays the current and new configuration record. When "Y" is answered to the prompt "Install Configuration:", the new configuration is copied from the file ".SYSTEM.CONFIG.I(serial number)", to the special system area on disk. The new configuration takes effect at the next system load. For further details on the use of the CONFIG.MGR utility, see the 9.5D/8.5D Software Announcement #139, or the BOSS/VS UTILITY USER GUIDE, M5102. The configuration record file name is derived from the system serial number by changing the leading "8" to an "I" and adding the prefix ".SYSTEM.CONFIG.". SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg058 EXAMPLE: .SYSTEM.CONFIG.I1030114 for SSN 810-30114 This configuration record tape should be saved, in case reinstallation should become necessary. Before going to the next step, LOAD the system so the new ____ configuration record will take affect. If you do not load the system, you will have a minimum configuration and the system will be very slow. 6.5.4. UPDATING SLOTS 2 AND 3 ON 7xxx and 8xxx SYSTEMS ________ _____ _ ___ _ __ ____ ___ ____ _______ NOTE: If question marks (?/?) ever appear for Load Sector 2 at the top of the OSINFO screen, it is necessary to run UPDATE.LD for REMIDI. See section 4.3.1 for further information on REMIDI and UPDATE.LD. O.S. and WCS slots 2 and 3 are updated by using the UPDATE.OS and UPDATE.WCS utilities in a TYPE 1 LOAD. To run these utilities, you must set your prefix to the .R6E15.INST. node. 6.5.4.1. Updating WCS Slot Two (2) ________ ___ ____ ___ ___ REMIDI version BV includes all the micro-diagnostics except MPC and LAN controller micro-diagnostics. It is placed in WCS slot 2 and is used for testing on all 7000/7100 and 8000 Series Systems. !UPDATE.WCS ENTER WCS SLOT (0..3): '2' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE: (choose disk) WCS IMAGE FILE: .R6E15.INST.REMIDI.BV WCS LEVEL OF WCS IMAGE FILE: (level displayed) UPDATING DISK UNIT nn SECTOR xxx WCS UPDATE COMPLETED! 6.5.4.2. Updating Slot Three (3) ________ ____ _____ ___ 6.5.4.2.1. Updating WCS Slot Three (3) ________ ___ ____ _____ ___ 6.5.4.2.1.1. On 7000/7100 Systems and 8000 Systems with LAN __ _________ _______ ___ ____ _______ ____ ___ REMIDI version BVM contains micro-diagnostics for the LAN and MPC controllers. It is placed in WCS slot 3 on 7000/7100 Series Systems and on 8000 Series Systems with LAN controllers. The utility UPDATE.LD is used to update the Load Directory for Load Sector 2 to toggle between the two versions of REMIDI in WCS slots 2 and 3. The pointers in Load Sector 2 (displayed on the OSINFO screen) determine which diagnostics will run. See section 4.3.1 for further information on REMIDI and SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg059 UPDATE.LD. !UPDATE.WCS ENTER WCS SLOT (0..3): '3' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R6E15.INST.REMIDI.BVM WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE! 6.5.4.2.1.2. On 8000 Systems Without LAN __ ____ _______ _______ ___ This slot will contain system WCS which is common to both the O.S. and DEMON. !UPDATE.WCS ENTER WCS SLOT [0..3]: '3' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R6E15.INST.WCS WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 6.5.4.2.2. Updating O.S. Slot Three (3) ________ ____ ____ _____ ___ The O.S. slot 3 will contain the O.S. for DEMON on both 7000/7100 and 8000 Series Systems. !UPDATE.OS BOSS/VS Image File Name: .R6E15.INST.DEMON.UV Target OS Slot (0/1/3) : '3' Target WCS Slot (0-3) : '0' Target Drives (0/1/All/Quit): (choose drive) NOTE: A '0' is entered for the WCS slot to associate DEMON's O.S. with the WCS in slot 0. DEMON and the 8.6E O.S. share the same WCS. The system will now display: Update in progress: nn% Image slot directory n/n:n Updates all complete. 6.5.5. SLOT INFORMATION ____ ___________ Once all slots have been updated, use the utility OSINFO to display the slot information. The information should be similar to figure 6-4. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg060 This operating system installation procedure must be performed on all system disks. If disk 1 is a system disk also, repeat the operating system installation procedure for this disk. Figure 6-4. Operating System Information ______ ____ _________ ______ ___________ OPERATING SYSTEM INFORMATION ------------------------------------------------------------------ BOOT LEVEL : X.X.X.X LOAD SECTOR: 0 1 2 3 DISK 0 : 0/0 1/1 0/2 3/3 SERIAL # : XXX-XXXXX ------------------------------------------------------------------ OS NAME OS LEVEL DISK:SLOT WCS LEVEL ------------------------------------------------------------------ R 6E*15 881017 6.5.15.0 0:0 B 6.1.0 R 6E*15 881017 6.5.15.0 0:1 B 6.1.0 N/A 0:2 REMIDI B 5.1.1 DEMON 6.5.7.11 0:3 B 6.1.0 ------------------------------------------------------------------ NOTE: OSINFO on 7000/7100 Series Systems and 8000 Series Systems with LAN will show the additional version of REMIDI in WCS slot 3. The load sector 3 should be 3/0 on these systems. 6.6. UPGRADING TO 9.6E _________ __ ____ 6.6.1. SPECIAL CONSIDERATIONS _______ ______________ If you are installing the 9.6E O.S. on a newly formatted System disk or changing a Data disk to a System disk, go to section 6.3. If you are upgrading a 7xxx or 8xxx Series System to a 9xxx Series System, you must first run for a minimum of one week on O.S. 8.6A or above before the hardware upgrade. A new configuration record is required when upgrading to 9.6E from 9.5 O.S. levels. A new configuration record is also required when an upgrade includes new hardware. 6.6.2. PRINTING OUT THE TERMINAL CONFIGURATION INFORMATION ________ ___ ___ ________ _____________ ___________ Skip this section if you are upgrading to 9.6E from 9.6A/B/C or 9.5. When upgrading from MPx 7xxx/8xxx Series Systems to the MPx 9xxx Series Systems, it is necessary to reference the terminal configuration in order to properly re-address the 9xxx controllers. Therefore, you must print out a copy of the terminal configuration information before upgrading. 1. Enter the TERM.CONFIG utility. 2. Select OPTION 2 DISPLAY A CONFIGURATION FILE. 3. When the following screen is displayed, enter these responses to the prompts: SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg061 CONFIGURATION FILE: P OUTPUT DEVICE: DETAILED REPORT: Y ENTRIES CORRECT: Y The terminal configuration information should now be printed. 6.6.3. SAVING FILES TO TAPE ______ _____ __ ____ Current files must first be backed up to tape, using the standard tape utility, SAVERESTORE. When saving files to tape, send the output from the save process to the printer. This will provide a record of backup for each file. Also it is recommended that all tapes be compared to the files on the disk. NOTE: It is essential that the .SYSDATA.SECURITY.DATA file be backed up before upgrading to 9.6E, if your current O.S. level is below 9.6C. This SECURITY.DATA file will go through a conversion during the upgrade, and the converted file cannot be used on previous O.S. levels. The old version of SECURITY.DATA should be saved in case an O.S. downgrade is ever necessary. 6.6.4. OPERATING SYSTEM UPDATE _________ ______ ______ 6.6.4.1. Loading Slots 0 and 1 Using ALT LOAD _______ _____ _ ___ _ _____ ___ ____ NOTE: As of releases 9/8.6C, positioning of the O.S./WCS slots has been adjusted slightly. Therefore, O.S. levels previous to 9/8.6C cannot reside in slots on the same disk with O.S. levels 9/8.6C and above. For this reason, ALT LOAD has been enhanced so that it will automatically load both slots 0 and 1 if one of the following three conditions is true: 1) You are upgrading from a release prior to 9/8.6C. 2) You are updating a newly formatted disk. 3) You are changing a DATA disk to a SYSTEM disk. If any of the above three conditions are true, WCS slots 2 and 3 are also loaded with the BOSS/VS WCS for formatting purposes only. The user needs to reload these slots with the REMIDI WCS files, using UPDATE.WCS. See the sections on updating slots 2 and 3 in this announcement. If you are upgrading to 10/9/8.6E from 9/8.6C, or if you are reinstalling 10/9/8.6E (over itself), the ALT LOAD procedure must be run twice - once to load O.S. and WCS slots 0, and once to load O.S. and WCS slots 1. To perform an ALT LOAD from tape follow these steps: A) Mount the new release tape in the tape drive. (All front panel load select switches should be OFF if using tape drive 0. Switch 1 should be ON if using tape drive 1.) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg062 B) Press the "ALT LOAD" button on the front panel. First, a proprietary message will be displayed, and then the following load screen: ____________________________________________________________________ Load PROM Version: x.x.x.x SYSTEM SERIAL NUMBER : 000-00000 Load Drive n SERIAL NUMBER CREATOR: 000-00000 WCS 0 Version: x.x.x CONFIGURATION CREATOR: 000-00000 OS 0 Version: 6.5.x.x CPUs ID #s : n Memory (Mb) : n.0 Disk Drives : n BOSS/VS LOAD FROM TAPE Tape Drives : n Printers : n HVDTs : n IMLCs : n Serial Ports: n Date Format MM/DD/YY: BMTCs : n/n DATE = MM/DD/YY: LAN Cntrlrs : n TIME = HH:MM:SS: SYSTEM PREFIX: (family).R6E15.SYS.,.R6E15.INST. System Default Family: (family) File System Write Thru: T/F User Default Family : (family) Per-File Write Through: T/F Installation Name : (name) File System Security : T/F ____________________________________________________________________ Key in the current DATE and TIME at the above prompts. The screen will then display: ____________________________________________________________________ L O A D I N G . . . BOSS/VS Operating System Image Update Utility [version 6.5.x.x] OS/WCS information for drive n (nn): 0: ?????????????? ??????? | x x.x.x 1: ?????????????? ??.??.??.??? | ? ??.??.?? 2: -------------- -- -- -- --- | ????????? 3: ?????????????? ??????? | ????????? BOSS/VS Image File Name: (displays one of the following): OSN.CT0605xxxxx (ADVANCED SERIES) OSN.AT0605xxxxx (9x00 systems - 1/2-inch) OSN.AC0605xxxxx (9400 systems - 1/4-inch) OSN.BT0605xxxxx (8000 systems - 1/2-inch) OSN.BC0605xxxxx (7x00 systems - 1/4-inch) Target OS Slot (0/1/3) : '0' (or 1) Target WCS Slot (0-3) : '0' (or 1) Target Drives (0/1/All/Quit): (choose drive) ____________________________________________________________________ C) The Image File Name will be displayed by the system. Enter '0' or '1' at the slot prompts to load O.S. and WCS slots SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg063 0 and 1. Enter '0', '1', or 'All' at the drive prompt to update the appropriate drives. NOTE: Do not update drive 1 if it is a DATA disk and is to remain so. The system will now display: ___________________________________________________________________ Now updating WCS slot # n Update in progress: nn% Now updating BOSS/VS Image (displays one of the following): OSN.CT0605xxxxx (ADVANCED SERIES) OSN.AT0605xxxxx (9x00 systems - 1/2-inch) OSN.AC0605xxxxx (9400 systems - 1/4-inch) OSN.BT0605xxxxx (8000 systems - 1/2-inch) OSN.BC0605xxxxx (7x00 systems - 1/4-inch) Update in progress: nn% Image slot directory n/n:n Updates all complete. D O N E - R E A D Y F O R N O R M A L D I S K L O A D ___________________________________________________________________ If you are upgrading to 10/9/8.6E from 9/8.6C or from another star ("*") level of 10/9/8.6E, repeat this procedure for O.S. and WCS slots 1. When O.S. and WCS slots 0 and 1 have been updated, reload the system by pressing the LOAD switch. 6.6.4.2. Changing Installation Parameters ________ ____________ __________ Enter a TYPE 3 LOAD (SPECIAL FUNCTIONS) and select OPTION 2 (INITIALIZATION OPTIONS). OPTION 2 - INITIALIZATION OPTIONS Option 4 - CHANGE INSTALLATION PARAMETERS Only system disks will be displayed. DRIVE NUMBER _______ PRIMARY PREFIX _______________________ (Enter (family).R6E15.SYS. (Family) is the family where the operating system files reside.) SECONDARY PREFIX _____________________ (Enter (family).R6E15.SYS. (Family) is the family where the alternate operating system files reside.) SYSTEM INSTALLATION NAME _________________________ (Sets the default installation name for a specified SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg064 system disk.) DEFAULT USER FAMILY NAME ________ (Enter default user family.) SECURITY (E=ENABLED, D=DISABLED) ___ FILE SYSTEM WRITE THROUGH? (E=ENABLED, D=DISABLED) ___ WRITE THROUGH DEFAULT ON FILE CREATE (E=ENABLED, D=DISABLED) __ (This parameter specifies what the default write through will be on a file created through a BASIC file create or through the CREATE utility.) UPDATE DISK WITH INSTALLATION PARAMETERS? (Y/N)__ Display: INSTALLATION PARAMETERS SUCCESSFULLY WRITTEN TO DISK (CR) TO CONTINUE: Reload the system by pressing the LOAD switch. Be sure to load the system from the disk where you wish to restore the operating system files. 6.6.4.3. Restoring the O.S. Files _________ ___ ____ _____ Enter SAVERESTORE in a TYPE 2 LOAD and choose OPTION 2 RESTORE FILES FROM TAPE. The screen appears as in figure 6-5. Figure 6-5. Restore Screen ______ ____ _______ ______ -------------------------------------------------------- RESTORE FILES TAPE SET.ID: DRIVE-NUM: REEL-NUM: PRIMARY PREFIX: (FAMILY).NODE. FILE TYPE (D/P/CR=ALL) COMPARE (CR=Y/N) DATE (MM/DD/YY) TIME (HH:MM) OUTPUT DEVICE (CR=VDT) DELETE EXISTING FILES (CR=Y) VERIFY (Y/CR=N) ENTRIES CORRECT (Y/N) -------------------------------------------------------- At each prompt, enter a . At the prompt, "FILE SPECIFIERS", enter ".". Then enter twice. This will restore all files on the release tape to disk. Please note that once all files are restored to disk, the message "AUTOMATIC COMPARE, CR TO CONTINUE" appears. This automatically rewinds the tape and begins the compare operation. This only occurs when the compare option is SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg065 selected. When the compare is completed, enter a CTL-IV to return to the "SAVERESTORE" menu. 6.6.5. INSTALLING THE CONFIGURATION RECORD __________ ___ _____________ ______ It is necessary to install a new configuration record when upgrading to 9.6E from 8.4, 8.5 and 9.5 release levels. Until the following procedure is completed, the system will have a minimum configuration. Enter a TYPE 1 LOAD. Set your prefix to .SYSTEM.CONFIG. Before you load the new configuration record, rename the current configuration record on your system, using the RENAME utility, to temporarily preserve it for fall back purposes. (e.g. ".OLDCONFIG.") Using the SAVERESTORE utility, restore the new configuration record on tape onto your system. Execute the CONFIG.MGR utility. The CONFIG.MGR utility allows the user to update the system configuration record by installing a new configuration file. This utility displays the current and new configuration record. When "Y" is answered to the prompt "Install Configuration:", the new configuration is copied from the file ".SYSTEM.CONFIG.I(serial number)", to the special system area on disk. The new configuration takes effect at the next system load. For further details on the use of the CONFIG.MGR utility, see the 8.5D/9.5D Software Announcement #139, or the BOSS/VS UTILITY USER GUIDE, M5102. The configuration record file name is derived from the system serial number by changing the leading "8" to an "I" and adding the prefix ".SYSTEM.CONFIG.". EXAMPLE: .SYSTEM.CONFIG.I1030114 for SSN 810-30114 This configuration record tape should be saved, in case reinstallation should become necessary. After installing the new configuration record, LOAD the system. Otherwise your system will be at minimum configuration and will be extremely slow. 6.6.6. UPDATING SLOTS 2 AND 3 ON MPx 9xxx SERIES SYSTEMS ________ _____ _ ___ _ __ ___ ____ ______ _______ O.S. and WCS slots 2 and 3 are updated by using the UPDATE.OS and UPDATE.WCS utilities in a TYPE 1 LOAD. To run these utilities, you must set your prefix to the .R6E15.INST. node. 6.6.6.1. Updating WCS Slot Two (2) ________ ___ ____ ___ ___ The first section of the 9xxx version of REMIDI will reside in this slot. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg066 !UPDATE.WCS ENTER WCS SLOT (0..3): '2' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE: (choose disk) WCS IMAGE FILE: .R6E15.INST.REMIDI.AVA WCS LEVEL OF WCS IMAGE FILE: (level displayed) UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETED! 6.6.6.2. Updating WCS Slot Three (3) ________ ___ ____ _____ ___ The second section of the 9xxx version of REMIDI will reside in this slot. !UPDATE.WCS ENTER WCS SLOT (0..3): '3' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R6E15.INST.REMIDI.AVC WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE! NOTE: After REMIDI has been installed, Load Sector 2 at the top of the OSINFO screen should reflect an O.S./WCS of 0/2. If 0/2 is not displayed for Load Sector 2, UPDATE.LD must be run to update the Load Directory. See section 4.3.1.2 for instructions on how to do this. 6.6.6.3. Updating O.S. Slot Three (3) ________ ____ ____ _____ ___ O.S. slot 3 will contain the O.S. for DEMON. !UPDATE.OS BOSS/VS Image File Name: .R6E15.INST.DEMON.UV Target OS Slot (0/1/3) : '3' Target WCS Slot (0-3) : '0' Target Drives (0/1/All/Quit): (choose drive) NOTE: A '0' is entered for the WCS slot to associate DEMON's O.S. with the WCS in slot 0. DEMON and the 10/9/8.6E O.S. share the same WCS. The system will now display: Update in progress: nn% Image slot directory n/n:n Updates all complete. If drive 1 is a system disk also, the operating system installation procedure must be repeated for this disk. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg067 6.6.7. SLOT INFORMATION ____ ___________ Once all slots have been updated, use the utility OSINFO to display the slot information. The information should be similar to figure 6-6. Figure 6-6. Operating System Information ______ ____ _________ ______ ___________ OPERATING SYSTEM INFORMATION ------------------------------------------------------------------ BOOT LEVEL : X.X.X.X LOAD SECTOR: 0 1 2 3 DISK 0 : 0/0 1/1 0/2 3/0 SERIAL # : XXX-XXXXX ------------------------------------------------------------------ OS NAME OS LEVEL DISK:SLOT WCS LEVEL ------------------------------------------------------------------ R 6E*15 881017 6.5.15.0 0:0 A 6.5.4 R 6E*15 881017 6.5.15.0 0:1 A 6.5.4 N/A 0:2 REMIDI A 6.5.1 DEMON 6.5.7.11 0:3 REMIDI A 6.5.2 ------------------------------------------------------------------ Installation is now complete. 6.7. UPGRADING TO 10.6E AND THE ADVANCED SERIES _________ __ _____ ___ ___ ________ ______ 6.7.1. SPECIAL CONSIDERATIONS _______ ______________ If you are installing the 10.6E O.S. on a newly formatted System disk or changing a Data disk to a System disk, go to section 6.3. A new configuration record is required when upgrading to 10.6E. It is required that systems being upgraded to 10.6E run on any 9/8.6 release prior to upgrade. When it is established that the system is running smoothly on 9/8.6, upgrade to 10.6E may then proceed. 6.7.2. SAVING FILES TO TAPE ______ _____ __ ____ Current files must first be backed up to tape, using the standard tape utility, SAVERESTORE. When saving files to tape, send the output from the save process to the printer. This will provide a record of backup for each file. Also it is recommended that all tapes be compared to the files on the disk. NOTE: It is essential that the .SYSDATA.SECURITY.DATA file be backed up before upgrading to 10.6E, if your current O.S. level is below 9.6C. This SECURITY.DATA file will go through a conversion during the upgrade, and the converted file cannot be used on previous O.S. levels. The old version of SECURITY.DATA should be saved in case an O.S. downgrade is ever necessary. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg068 6.7.3. OPERATING SYSTEM UPDATE _________ ______ ______ 6.7.3.1. Loading Slots 0 and 1 Using ALT LOAD _______ _____ _ ___ _ _____ ___ ____ NOTE: As of releases 9/8.6C, positioning of the O.S./WCS slots has been adjusted slightly. Therefore, O.S. levels previous to 9/8.6C cannot reside in slots on the same disk with O.S. levels 9/8.6C and above. For this reason, ALT LOAD has been enhanced so that it will automatically load both slots 0 and 1 if one of the following three conditions is true: 1) You are upgrading from a release prior to 9/8.6C. 2) You are updating a newly formatted disk. 3) You are changing a DATA disk to a SYSTEM disk. If any of the above three conditions are true, WCS slots 2 and 3 are also loaded with the BOSS/VS WCS for formatting purposes only. The user needs to reload these slots with the REMIDI WCS files, using UPDATE.WCS. See the sections on updating slots 2 and 3 in this announcement. If you are upgrading to 10/9/8.6E from 9/8.6C, or if you are reinstalling 10/9/8.6E (over itself), the ALT LOAD procedure must be run twice - once to load O.S. and WCS slots 0, and once to load O.S. and WCS slots 1. To perform an ALT LOAD from tape follow these steps: A) Mount the new release tape in the tape drive. (All front panel load select switches should be OFF if using tape drive 0. Switch 1 should be ON if using tape drive 1.) B) Press the "ALT LOAD" button on the front panel. First, a proprietary message will be displayed, and then the following load screen: ____________________________________________________________________ Load PROM Version: x.x.x.x SYSTEM SERIAL NUMBER : 000-00000 Load Drive n SERIAL NUMBER CREATOR: 000-00000 WCS 0 Version: x.x.x CONFIGURATION CREATOR: 000-00000 OS 0 Version: 6.5.x.x CPUs ID #s : n Memory (Mb) : n.0 Disk Drives : n BOSS/VS LOAD FROM TAPE Tape Drives : n Printers : n HVDTs : n IMLCs : n Serial Ports: n Date Format MM/DD/YY: BMTCs : n/n DATE = MM/DD/YY: LAN Cntrlrs : n TIME = HH:MM:SS: SYSTEM PREFIX: (family).R6E15.SYS.,.R6E15.INST. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg069 System Default Family: (family) File System Write Thru: T/F User Default Family : (family) Per-File Write Through: T/F Installation Name : (name) File System Security : T/F ____________________________________________________________________ Key in the current DATE and TIME at the above prompts. The screen will then display: ____________________________________________________________________ L O A D I N G . . . BOSS/VS Operating System Image Update Utility [version 6.5.x.x] OS/WCS information for drive n (nn): 0: ?????????????? ??????? | x x.x.x 1: ?????????????? ??.??.??.??? | ? ??.??.?? 2: -------------- -- -- -- --- | ????????? 3: ?????????????? ??????? | ????????? BOSS/VS Image File Name: (displays one of the following): OSN.CT0605xxxxx (ADVANCED SERIES) OSN.AT0605xxxxx (9x00 systems - 1/2-inch) OSN.AC0605xxxxx (9400 systems - 1/4-inch) OSN.BT0605xxxxx (8000 systems - 1/2-inch) OSN.BC0605xxxxx (7x00 systems - 1/4-inch) Target OS Slot (0/1/3) : '0' (or 1) Target WCS Slot (0-3) : '0' (or 1) Target Drives (0/1/All/Quit): (choose drive) ____________________________________________________________________ C) The Image File Name will be displayed by the system. Enter '0' or '1' at the slot prompts to load O.S. and WCS slots 0 and 1. Enter '0', '1', or 'All' at the drive prompt to update the appropriate drives. NOTE: Do not update drive 1 if it is a DATA disk and is to remain so. The system will now display: ___________________________________________________________________ Now updating WCS slot # n Update in progress: nn% Now updating BOSS/VS Image (displays one of the following): OSN.CT0605xxxxx (ADVANCED SERIES) OSN.AT0605xxxxx (9x00 systems - 1/2-inch) OSN.AC0605xxxxx (9400 systems - 1/4-inch) OSN.BT0605xxxxx (8000 systems - 1/2-inch) OSN.BC0605xxxxx (7x00 systems - 1/4-inch) Update in progress: nn% Image slot directory n/n:n Updates all complete. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg070 D O N E - R E A D Y F O R N O R M A L D I S K L O A D ___________________________________________________________________ If you are upgrading to 10/9/8.6E from 9/8.6C or from another star ("*") level of 10/9/8.6E, repeat this procedure for O.S. and WCS slots 1. When O.S. and WCS slots 0 and 1 have been updated, reload the system by pressing the LOAD switch. 6.7.3.2. Changing Installation Parameters ________ ____________ __________ Enter a TYPE 3 LOAD (SPECIAL FUNCTIONS) and select OPTION 2 (INITIALIZATION OPTIONS). OPTION 2 - INITIALIZATION OPTIONS Option 4 - CHANGE INSTALLATION PARAMETERS Only system disks will be displayed. DRIVE NUMBER _______ PRIMARY PREFIX _______________________ (Enter (family).R6E15.SYS. (Family) is the family where the operating system files reside.) SECONDARY PREFIX _____________________ (Enter (family).R6E15.SYS. (Family) is the family where the alternate operating system files reside.) SYSTEM INSTALLATION NAME _________________________ (Sets the default installation name for a specified system disk.) DEFAULT USER FAMILY NAME ________ (Enter default user family.) SECURITY (E=ENABLED, D=DISABLED) ___ FILE SYSTEM WRITE THROUGH? (E=ENABLED, D=DISABLED) ___ WRITE THROUGH DEFAULT"o FILE CREATE (E=ENABLED, D=DISABLED) __ (This parameter specifies what the default write through will be on a file created through a BASIC file create or through the CREATE utility.) UPDATE DISK WITH INSTALLATION PARAMETERS? (Y/N)__ Display: INSTALLATION PARAMETERS SUCCESSFULLY WRITTEN TO DISK (CR) TO CONTINUE: Reload the system by pressing the LOAD switch. Be sure you are loading the system from the disk where you wish to restore the operating system files. 6.7.3.3. Restoring the O.S. Files SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg071 _________ ___ ____ _____ Enter SAVERESTORE in a TYPE 2 LOAD and choose OPTION 2 RESTORE FILES FROM TAPE. The screen appears as in figure 6-2. Figure 6-7. Restore Screen ______ ____ _______ ______ -------------------------------------------------------- RESTORE FILES TAPE SET.ID: DRIVE-NUM: REEL-NUM: PRIMARY PREFIX: (FAMILY).NODE. FILE TYPE (D/P/CR=ALL) COMPARE (CR=Y/N) DATE (MM/DD/YY) TIME (HH:MM) OUTPUT DEVICE (CR=VDT) DELETE EXISTING FILES (CR=Y) VERIFY (Y/CR=N) ENTRIES CORRECT (Y/N) -------------------------------------------------------- At each prompt, enter a . At the prompt, "FILE SPECIFIERS", enter ".". Then enter twice. This will restore all files on the release tape to disk. Please note that once all files are restored to disk, the message "AUTOMATIC COMPARE, CR TO CONTINUE" appears. This automatically rewinds the tape and begins the compare operation. This only occurs when the compare option is selected. When the compare is completed, enter a CTL-IV to return to the "SAVERESTORE" menu. 6.7.4. INSTALLING THE CONFIGURATION RECORD __________ ___ _____________ ______ It is necessary to install a new configuration record when upgrading to 10.6E. Until the following procedure is completed, the system will have a minimum configuration. Enter a TYPE 1 LOAD. Set your prefix to .SYSTEM.CONFIG. Before you load the new configuration record, rename the current configuration record on your system, using the RENAME utility, to temporarily preserve it for fall back purposes. (e.g. ".OLDCONFIG.") Using the SAVERESTORE utility, restore the new configuration record on tape onto your system. Execute the CONFIG.MGR utility. The CONFIG.MGR utility allows the user to update the system configuration record by installing a new configuration file. This utility displays SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg072 the current and new configuration record. When "Y" is answered to the prompt "Install Configuration:", the new configuration is copied from the file ".SYSTEM.CONFIG.I(serial number)", to the special system area on disk. The new configuration takes effect at the next system load. For further details on the use of the CONFIG.MGR utility, see the 8.5D/9.5D Software Announcement #139, or the BOSS/VS UTILITY USER GUIDE, M5102. The configuration record file name is derived from the system serial number by changing the leading "8" to an "I" and adding the prefix ".SYSTEM.CONFIG.". EXAMPLE: .SYSTEM.CONFIG.I1030114 for SSN 810-30114 This configuration record tape should be saved, in case reinstallation should become necessary. After installing the new configuration record, LOAD the system. Otherwise your system will be at minimum configuration and will be extremely slow. 6.7.5. Updating Slots 2 and 3 on ADVANCED SERIES Systems ________ _____ _ ___ _ __ ________ ______ _______ O.S. and WCS slots 2 and 3 are updated by using the UPDATE.OS and UPDATE.WCS utilities in a TYPE 1 LOAD. To run these utilities, you must set your prefix to the .R6E15.INST. node. 6.7.5.1. Updating WCS Slot Two (2) ________ ___ ____ ___ ___ The first section of REMIDI will reside in this slot. !UPDATE.WCS ENTER WCS SLOT [0..3]: '2' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE: (choose disk) WCS IMAGE FILE: .R6E15.INST.REMIDI.CVA WCS LEVEL OF WCS IMAGE FILE: (level displayed) UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETED! NOTE: After REMIDI has been installed, Load Sector 2 at the top of the OSINFO screen should reflect an O.S./WCS of 0/2. If 0/2 is not displayed for Load Sector 2, UPDATE.LD must be run to update the Load Directory. See section 4.3.1.2 for instructions on how to do this. 6.7.5.2. Updating WCS Slot Three (3) ________ ___ ____ _____ ___ The second section of the ADVANCED SERIES version of REMIDI will reside in this slot. !UPDATE.WCS ENTER WCS SLOT [0..3]: '3' AVAILABLE DISK UNITS ARE: (displayed) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg073 DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R6E15.INST.REMIDI.CVC WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 6.7.5.3. Updating O.S. Slot Three (3) ________ ____ ____ _____ ___ O.S. slot 3 will contain the O.S. for DEMON. !UPDATE.OS BOSS/VS Image File Name: .R6E15.INST.DEMON.UV Target OS Slot (0/1/3) : '3' Target WCS Slot (0-3) : '0' Target Drives (0/1/All/Quit): (choose drive) NOTE: A '0' is entered for the WCS slot to associate DEMON's O.S. with the WCS in slot 0. DEMON and the 10/9/8.6E O.S. share the same WCS. The system will now display: Update in progress: nn% Image slot directory n/n:n Updates all complete. If drive 1 is a system disk also, the operating system installation procedure must be repeated for this disk. 6.7.6. SLOT INFORMATION ____ ___________ Once all slots have been updated, use the utility OSINFO to display the slot information. The information should be similar to figure 6-6. Figure 6-8. Operating System Information ______ ____ _________ ______ ___________ OPERATING SYSTEM INFORMATION ------------------------------------------------------------------ BOOT LEVEL : X.X.X.X LOAD SECTOR: 0 1 2 3 DISK 0 : 0/0 1/1 0/2 3/0 SERIAL # : XXX-XXXXX ------------------------------------------------------------------ OS NAME OS LEVEL DISK:SLOT WCS LEVEL ------------------------------------------------------------------ R 6E*15 881017 6.5.15.0 0:0 C 6.5.14 R 6E*15 881017 6.5.15.0 0:1 C 6.5.14 N/A 0:2 REMIDI C 6.5.6 DEMON 6.5.7.11 0:3 REMIDI C 6.5.7 ------------------------------------------------------------------ Installation is now complete. 6.8. UPDATING SLOTS 0 AND 1 USING UPDATE.OS AND UPDATE.WCS SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg074 ________ _____ _ ___ _ _____ _________ ___ __________ Because the new ALT LOAD from tape loads O.S. and WCS slots 0 and 1, it is no longer necessary to use UPDATE.OS and UPDATE.WCS to update these slots during a normal installation. However, these slots can be loaded at any time using these utilities, provided the O.S. and WCS files are resident on disk and you are not booted from the slot you wish to update. The following is the procedure to accomplish this. 6.8.1. Updating O.S. Slots 0 and 1 ________ ____ _____ _ ___ _ Set the prefix to the .INST. node by keying in the following in command mode: !PREFIX .R6E15.INST. !UPDATE.OS BOSS/VS Operating System Image Update Utility [Version 6.3.x.x] OS/WCS information for drive n (nn) 0: R 6C*xx (date) 6.3.x.x | X 6.x.x 1: ?????????????? ??.??.??.??? | ? ??.??.?? 2: -------------- -- -- -- --- | R X 6.x.x 3: DEMON 6.3.x.x | R X 6.x.x The following prompts will then be displayed, one at a time: BOSS/VS Image File Name: .R6E15.INST.OSN.UV Target OS Slot (0/1/3) : '0' or '1' Target WCS Slot (0-3) : '0' or '1' Target Drives (0/1/All/Quit): (choose drive) The system will now display: Update in progress: nn% Image slot directory n/n:n Updates all complete. 6.8.2. Updating WCS Slots 0 and 1 ________ ___ _____ _ ___ _ Set the prefix to the .INST. node by keying in the following in command mode: !PREFIX .R6E15.INST. !UPDATE.WCS ENTER WCS SLOT [0..3]: '0' or '1' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R6E15.INST.WCS.A (for 9xxx systems) WCS.B (for 7xxx/8xxx systems) WCS.C (for ADVANCED SERIES) WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg075 WCS UPDATE COMPLETE 6.9. SYSTEM STARTUP ______ _______ 6.9.1. STANDARD STARTUP COMMAND FILE ________ _______ _______ ____ The commands for the standard System Startup Command File are released in the file: .R6E15.SYS.START.CMD The standard commands are: !MAGNET.STARTUP !GROUP.CREATE SPOOLER,TYPE=SYSTEM !SPOOL P*,VERIFY=F,PAUSE=F !GROUP.ENABLE TERMINALS,VERIFY=F,PAUSE=F The name of the System Startup Command File actually used for startup is: (system-default-family).SYSDATA.START.CMD Part of 10/9/8.6E BOSS/VS system installation is to copy the released file to the .SYSDATA. node and make changes and additions as necessary. Note that the commands and parameters in this file must match the commands and parameters defined in the CLI command and function definition files for the individual system being installed. If the System Startup Command File is not found after a system load, then a default initialization is performed. This puts all printers into spooled mode and enables terminals. The following outlines the commands, some of the implications and details of the System Startup Command File method of system configuration. 6.9.1.1. Command File Definitions _______ ____ ___________ MAGNET.STARTUP ______________ This command runs a released MAGNET program that does all of the startup operations required by the MAGNET subsystem. This command should be deleted if MAGNET is not part of the system configuration. GROUP.CREATE_SPOOLER,TYPE=SYSTEM ________________________________ This command creates the SPOOLER Group that maintains the activity log files and Group statistics for the spooler subsystem. This command should come before the 'SPOOL P*' command. SPOOL_P*,VERIFY=F,PAUSE=F SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg076 _________________________ This command puts all of the printers into spooled mode, and causes any eligible requests on the spooled printers to start printing. GROUP.ENABLE_TERMINALS,VERIFY=F,PAUSE=F _______________________________________ This command enables the 'built-in' TERMINALS Group, and allows all users to logon to any terminals. This command is provided to allow the terminals to be enabled under user control. See below. NOTE: IF A SYSTEM STARTUP COMMAND FILE EXISTS, THIS COMMAND, OR SOME OTHER COMMAND TO ENABLE TERMINAL GROUPS, MUST BE IN THE SYSTEM STARTUP COMMAND FILE FOR USERS TO LOGON TO THE SYSTEM. In case the TERMINALS Group is disabled, a user with 'system operator' status can enable this group when attempting to logon to the system. This allows an operator to logon to the system in case the Startup Command File did not enable the TERMINALS Group, or the TERMINALS Group was left disabled by accident and all operators signed off the system. To enable the TERMINALS Group during logon the operator attempts to logon and ignores the 'Logon disabled' error messages and enters a 'CR' to continue. A prompt is displayed asking the operator if he wants to enable the TERMINALS Group. NOTE: THIS OPTION IS NOT AVAILABLE IF SOME OTHER TERMINAL TYPE GROUP IS ENABLED. ALSO, ONLY THE TERMINALS GROUP IS ENABLED, AND IT IS NOT CREATED IF IT DOES NOT EXIST. 6.9.2. IMPLICATIONS ____________ 1) Normal system startup is automatic. The system ______ ______ _______ __ _________ configuration options defined when the system was installed (placed into the System Startup Command File) are put into effect each time the system is loaded, with no further action by the user. These startup options may be modified by the user at any time, by editing the System Startup Command File. 2) Startup sequence is under user control. Users now have _______ ________ __ _____ ____ _______ the ability to control the sequence of events at startup, after the internal startup sequence is complete. Users that do not need this level of control may ignore this feature. Some users may wish to run specific programs, and do recovery operations, before MAGNET and/or the SPOOLER are started up. This ability would be impossible if these subsystems were always started by the internal system initialization. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg077 3) System recovery is possible before all users logon. This ______ ________ __ ________ ______ ___ _____ _____ approach allows the operator to allow only specified terminals/users to logon after a system load. The System Startup Command File containing the single command: GROUP.CREATE , TYPE=TERMINAL, USERS=SYS.MGR, DEVICES=T0 would allow only the user 'SYS.MGR' to logon to terminal 'T0' after the system load. No other users could logon, and no other activity would start. In this case the printers will be in suspended mode and MAGNET will not be initialized. When the system operator is finished with the recovery operations the 'normal' system configuration command file may be run by the operator to begin normal system processing. Again, users who do not need this level of control may ignore this feature. 4) Default startup with no System Startup Command File. When _______ _______ ____ __ ______ _______ _______ ____ the TYPE 1 LOAD is complete, if the System Startup Command File is not found then 'default' startup conditions are in effect. In this case the system is available for any use. This mode is intended to support systems that want only these default startup options. The 'built-in' TERMINALS Group is enabled and allows all users to logon to any terminal. A system group named SPOOLER is created and the printers are put into spooled mode. The MAGNET subsystem is not activated. ___ The following is a description of the details of the System Startup Job: When a TYPE 1 LOAD is performed, the last module to be initialized is the Job Manager (JMM). The final act of JMM is to run a batch job with a CLI command file. The files involved are: (system-default-family).SYSDATA.START.CMD (system-default-family).SYSDATA.START.IN (system-default-family).SYSDATA.START.OUT SYSDATA.START.CMD is a sequential file that contains all of the startup commands; this is the System Startup Command File. The Job Manager looks in the system default family (only) for this file. SYSDATA.START.IN is a sequential file that contains any data that may be input by commands and programs in the above startup file. A read from standard INPUT will read records SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg078 from this file. The Job Manager looks in the system default family (only) for this file. SYSDATA.START.OUT is a sequential file that contains the results of the startup command file. A write to standard OUTPUT by commands and programs will be placed into this file. The Job Manager deletes this file in the system family if it exists, prior to running the startup command file. If the startup file (system-default-family).SYSDATA.START.CMD - or - (system-default-family).SYSDATA.START.CMD.TEXT is not found, the Job Manager will perform a default startup described above. If the startup file (system-default-family).SYSDATA.START.IN - or - (system-default-family).SYSDATA.START.IN.TEXT is not found, the Job Manager will attach a null file to startup INPUT; an End-Of-File will be returned for each read from standard INPUT. NOTE: THE SYSTEM STARTUP COMMAND FILE CONTAINS (ONLY) STANDARD CLI COMMANDS. A CLI command may be: 1) A CLI Command or Function (START, PREFIX, $WHERE, etc.) 2) A system utility (DIR, COPY, etc.) 3) The name of a program to run. 4) The name of another CLI command file. 7. RELATED DOCUMENTATION _______ _____________ 2770/2780/3770/3780 Batch Emulator User Guide M5080C 3270 Pass-Through Reference Manual M5091A BOSS/VS Business BASIC 86 Reference Manual M6262A * BOSS/VS Business BASIC 86 Addendum M6262B * BOSS/VS User Guide M5098G ** BOSS/VS Utilities User Guide M5102J ** 3270 Emulation Package Operator Guide for MAI 8000 Series M5129 File Transfer Facility User Reference Manual M6352A BOSS/VS Installation Guide M5138H ** MPx System Installation Planning Guide M5146G ** BOSS/VS Special Purpose Utilities User Guide M5151 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg079 BOSS/VS System Support Manual M5152 Intersystem Transport Package User Guide M6354D MAI 8000 Series COBOL Reference Manual M5174 MAI 8000 Series COBOL User Guide M5175 BOSS/VS File Conversion User Guide M5185A MAGNET/VS User Reference Manual M6363 * * These manuals were revised for 9.6A/8.6A. ** These manuals were revised for 10/9/8.6E. ORIGINATOR: N. Prentiss SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB066 Pg080 FIB 00067 02/08/89 *** DOWN.LOAD occurs during execution of BCOM [ WPSF 511 ] *** PROBLEM: A DOWN.LOAD occurs on the IMLC each time you start communications in BCOM on the MPx or Advanced Series. This problem can occur on all OS levels. CAUSE: An invalid controller port is specified in the Terminal Definition option of the BCOM mode menu. The default controller port is 0A on a new installation of BCOM. SOLUTION: Modify your Controller Port in the Terminal Definition menu to a valid port - eg: 32A, 63A. CTL-I at the controller port input will display your available ports. ORIGINATOR: T. Tiangco SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB067 Pg001 FIB 00068 02/08/89 *** MPx Memory Sizing [ WPSF 433 ] *** The rule of thumb formula for memory sizing on the MPx series systems now includes an additional rule for more optimum system performance. The MPx rule of thumb for memory sizing has not changed. It is not dependent upon any version of BOSS/VS, but rather, the site's system load. MINIMUM: 750K OS plus 100K per task for the first 20 tasks and 70K per task above 20 plus 1MB additional for MAGNET. This is a minimum baseline rule of thumb that ensures the system will run. For most sites, this has proven to be sufficient, but depending on the application, the performance may or may not be acceptable to the user. If system performance is an issue, the performance monitor tools should be run to determine if lack of memory, CPU power or disk I/O is the problem. If the system is found to need additional memory, this is empirical evidence that the site's particular load or the specific application being run requires more than the minimum amount for optimal performance. In these cases, a general rule of thumb for memory sizing would be: OPTIMUM: 2MB for the OS plus 100K per task for the first 20 tasks and 70K per task above 20 plus 1MB additional for MAGNET. This formula estimates the additional amount of memory which may be allocated for workspace segments for the system basis and for general system buffers. This formula is based on field information collected from sites that were experiencing performance problems. ORIGINATOR: D. Jensen SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB068 Pg001 FIB 00069 04/18/89 *** ERR variable changed on Rel 10/0/8.6E PS 526] *** Prior to BOSS/VS 10/9/8.6E, exiting a CALLed program restored the old state of the ERR variable (last error) in the calling program, even if the CALLed program had changed it. This is not compatible with the way the 13xx and BOSS/IX work (they both pass back the ERR to the CALLing programs). EXAMPLE: CALLer Program: 100 SETERR 1000 ; A= 1/0 ; REM "will generate an error = 40" 1000 CALL "CALLee" 1100 PRINT "Returned Error", ERR CALLed Program: 100 SETERR 1000 ; A$=A$(5) ; REM " this generates an error = 47" 1000 EXIT On BOSS/VS releases prior to 10/9/8.6E the CALLer program on statement 1100 will print: Returned Error 40, but the same program on 13xx and BOSS/IX will print: Returned Error 47. On BOSS/VS 10/9/8.6E and above it will now print 47: Returned Error 47. ORIGINATOR: Joe Melendez SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB069 Pg001 FIB 00070 04/18/89 *** Warnings & Special Considerations for 8/9/10.6E [ WPSF 523 ] *** These Warnings and Special Considerations are applicable to release levels 10.6E, 9.6E, and 8.6E. This Field Bulletin is part of an effort to expand the reporting of known problems and special considerations to the field. C O N T E N T S 1 WARNINGS AND SPECIAL CONSIDERATIONS . . . . . . . . . . 1.1 FOR ALL ADVANCED SERIES AND MPX SERIES SYSTEMS . . . . 1.1.1 OPERATING SYSTEM . . . . . . . . . . . . . . . . . . 1.1.1.1 Different O.S. Levels in Adjacent Slots . . . . . 1.1.1.2 SECURITY.DATA File . . . . . . . . . . . . . . . . 1.1.1.3 Downgrading from 10/9/8.6E Releases . . . . . . . 1.1.1.4 Software Announcement on Tape . . . . . . . . . . 1.1.1.5 Dumps to Tape . . . . . . . . . . . . . . . . . . 1.1.2 AUDITOR'S LOGBOOK . . . . . . . . . . . . . . . . . 1.1.3 BROADCAST . . . . . . . . . . . . . . . . . . . . . 1.1.4 UTILITIES . . . . . . . . . . . . . . . . . . . . . 1.1.4.1 CONFIG.MGR . . . . . . . . . . . . . . . . . . . . 1.1.4.2 DELETE, CREATE, RENAME . . . . . . . . . . . . . . 1.1.4.3 EXTTAPE . . . . . . . . . . . . . . . . . . . . . 1.1.4.4 FAMILY . . . . . . . . . . . . . . . . . . . . . . 1.1.4.5 GETDEVINFO . . . . . . . . . . . . . . . . . . . . 1.1.4.6 JOB MANAGER . . . . . . . . . . . . . . . . . . . 1.1.4.7 MCSI . . . . . . . . . . . . . . . . . . . . . . . 1.1.4.8 SAVERESTORE . . . . . . . . . . . . . . . . . . . 1.1.4.9 SPOOLER . . . . . . . . . . . . . . . . . . . . . 1.1.4.10 TERM.TABLE . . . . . . . . . . . . . . . . . . . 1.1.4.11 UPDATE . . . . . . . . . . . . . . . . . . . . . 1.1.4.12 UTILITY . . . . . . . . . . . . . . . . . . . . . 1.1.5 LOGON . . . . . . . . . . . . . . . . . . . . . . . 1.1.6 BASIC . . . . . . . . . . . . . . . . . . . . . . . 1.1.7 FILE SYSTEM . . . . . . . . . . . . . . . . . . . . 1.1.7.1 Multi-Key Files . . . . . . . . . . . . . . . . . 1.1.8 HORIZONTAL SOFTWARE . . . . . . . . . . . . . . . . 1.1.9 COMMUNICATIONS . . . . . . . . . . . . . . . . . . . 1.1.9.1 MAGNET and File Transfer Facility (FTF) . . . . . 1.1.9.2 Asynchronous Transport Package (ATP) . . . . . . . 1.1.9.3 19.2K BPS Support . . . . . . . . . . . . . . . . 1.1.10 HARDWARE . . . . . . . . . . . . . . . . . . . . . 1.1.10.1 Terminals . . . . . . . . . . . . . . . . . . . . 1.1.10.2 MCS Board . . . . . . . . . . . . . . . . . . . . 1.1.10.2.1 When Upgrading from 8.4D and Below . . . . . . 1.1.10.2.2 MCS Revision "S" . . . . . . . . . . . . . . . 1.1.10.3 BMTC . . . . . . . . . . . . . . . . . . . . . . 1.2 FOR MPX 9XXX SERIES SYSTEMS ONLY . . . . . . . . . . . 1.2.1 HARDWARE . . . . . . . . . . . . . . . . . . . . . . 1.2.1.1 IMLC . . . . . . . . . . . . . . . . . . . . . . . 1.3 FOR THE ADVANCED SERIES ONLY . . . . . . . . . . . . . 1.3.1 POWER FAIL . . . . . . . . . . . . . . . . . . . . . 1.3.2 DIAGNOSTICS . . . . . . . . . . . . . . . . . . . . 1.3.2.1 High Frequency Margins on the ADVANCED SERIES . . 1.3.2.2 DMA 1 "Timeout" LED Running REMIDI . . . . . . . . 1.3.2.3 REMIDI ERROR 2701 on NEP Board . . . . . . . . . . 1.3.3 TERMINALS . . . . . . . . . . . . . . . . . . . . . SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB070 Pg001 1. WARNINGS AND SPECIAL CONSIDERATIONS 1.1. FOR ALL ADVANCED SERIES AND MPx SERIES SYSTEMS 1.1.1. OPERATING SYSTEM 1.1.1.1. Different O.S. Levels in Adjacent Slots As of release 9/8.6C, positioning of the image slots has been adjusted slightly. Therefore, OS/WCS levels previous to 9/8.6C cannot reside in slots on the same disk with release levels 9/8.6C and above. 1.1.1.2. SECURITY.DATA File The SYSDATA.SECURITY.DATA file is converted to a new format during an upgrade to O.S. levels 9/8.6C and above. This converted SECURITY.DATA file cannot be used on O.S. levels previous to 9/8.6C. Therefore, if you are upgrading to 10/9/8.6E from a release prior to 9/8.6C, the SECURITY.DATA file should be saved on the previous release before the upgrade. In the event of a downgrade, this old SECURITY.DATA file must be restored on the previous O.S. level. 1.1.1.3. Downgrading from 10/9/8.6E Releases The only acceptable downgrades from 10/9/8.6E releases are to 9/8.6C *11 releases. Downgrades to releases prior to 9/8.6C *11 may potentially cause control segment corruption. 1.1.1.4. Software Announcement on Tape The 10/9/8.6E Software Announcement exists as a serial file on the O.S. release tape. The name of this file is: .R6E15.INST.DOC.ANNOUNCE6E. This file can be restored and SUBMITted to a printer on 10/9/8.6 systems. Because of changes in the File System on 10/9/8.6E, this file cannot be restored on 9/8.5 systems. Files tranferred from 10/9/8.6E to release levels below 9/8.6A must be transported with EXTTAPE. Because the 10/9/8.6E release tape is created with SAVERESTORE, the Software Announcement file cannot be restored on release levels below 9/8.6A. 1.1.1.5. Dumps to Tape 1) SPR 519356 - Dumps to tape do not work on 1/4-inch tape drives connected to an MPC controller. This will be fixed in the next BOSS/VS release. 2) SPR 519358 - Diagnostic dumps to tape are sometimes followed by a fatal dump in systems with a TDP (PDC) controller. This will be fixed in the next BOSS/VS release. 3) SPR 519365 - Dumps to tape do not work with SCSI tape drives. This will be fixed in the next BOSS/VS release. 1.1.2. AUDITOR'S LOGBOOK 1) The source data file and its associated log files must be on the same family. In the next BOSS/VS release, the user SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB070 Pg002 will be able to specify a different family for the log files. 2) Audit logging is not supported on files with special character file names. 3) SPR 518831 - If the user reconstructs a file with logging enabled via DISKANALYZER, the new file will have two empty log files attached to it. Renaming the reconstructed file back to the old name will automatically delete the original log files, because the DELEXIST parameter in the RENAME utility refers to all three files: the source data file and its associated log files. The workaround for this problem is to rename the log files to a temporary name before the reconstruct, and rename them back to the original log names after the reconstructed source data file has been renamed back to its original name. This problem will be corrected in the next BOSS/VS release. 4) Log files may be reconstructed, but after the reconstruction, they will not appear to the system to be "official" log files. They will still contain the log data, and they may be used for tracing an audit trail, but they may not be used to continue logging. If a log file is reconstructed and renamed back to its original name, the associated data file will not be accessible, because the file system will complain about the presence of a "non- official" log file. Software Engineering is investigating a solution to this problem. 5) SPR 519433 - If the AUDITOR'S LOGBOOK key has already been installed on a system, and the O.S. is restored again from the release tape, the key file will be overwritten, making it necessary to reinstall the key. This is because the LOGBOOK key file, .ETC.LEVEL.ALB, is on the release tape. (The key is installed in this file after the file is restored.) The workaround is to use COPY or RENAME to save the .ETC.LEVEL.ALB file on disk under a different name before the O.S. restore, and renaming or copying it back after the O.S. restore. This problem will be remedied in the next BOSS/VS release. 6) SPR 519165 - When specifying Usage Rights on a file CREATE that are different from the default Usage Rights, the log files inherit the default Usage Rights instead of the Usage Rights specified. In the next BOSS/VS release, the log files will inherit the Usage Rights specified on a file CREATE. 7) If a user downgrades from 10/9/8.6E to a previous release of 9/8.6, and then goes back to 10/9.8.6E again, the audit logging attributes for files are lost. 8) When using CREATE to create a file that already exists and has assocaiated log files, DELEXIST = TRUE returns an ERROR 12 (Undefined or duplicate file name), because the CREATE DELEXIST parameter does not work with log files. The workaround is to DELETE the file and its associated log files before the CREATE. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB070 Pg003 9) SPR - 519267 - Users with Operator status are not allowed to COPY log files with DELEXIST = TRUE or DELSOURCE = TRUE if these users are not incorporated into the file's Usage Rights. In the next BOSS/VS release, users with Tape or System Operator status will be able to COPY log files with DELEXIST = TRUE or DELSOURCE = TRUE, even though they are not listed in the Usage Rights. 10) SPR 519493 - When doing a COPY of a file that has associated log files, with NEWRIGHTS = TRUE (the default), destination log files are automatically created. (If NEWRIGHTS = FALSE is specified, the destination log files will not be created.) In the next BOSS/VS release, COPY with NEWRIGHTS = TRUE will not create destination log files. 11) SPR 519494 - If a file is set for AUDIT LOGGING = TRUE, and it has no log files attached (they have been DELETEd or RENAMEd), DELETEing that file will create associated log files. This takes up much unnecessary disk space. In the next BOSS/VS release, a file DELETE in this case will still create the log files, but they will only be one record long, so that the DELETE may be recorded. 12) SPR 519766 - If the BASIC INITFILE directive is used on a file that has audit log files attached, the main source file will be deleted. The workaround is to use !INITFILE in command mode, which does not delete the file. 1.1.3. BROADCAST In order to send messages to all terminals, whether they are logged on or not, with the *ALL* command, the user must be logged on to a level 3 account. 1.1.4. UTILITIES SPR 515010 - When QUIET=T (or QUIETON) and an output file are specified in a utility command, and the utility encounters an error, the error will not be written to the output file. 1.1.4.1. CONFIG.MGR 1) A configuration record can only be installed from an account with a USER LEVEL of 3. 2) Printer output cannot be directed to a specific printer. All output goes to P*. 3) Configuration records on *.6E release levels will display *.6G in the CONFIG.MGR 'FOR RELEASE' field. Configuration records on systems with release levels other than *.6E will display the release level of the system they RESIDE on. For example, if a configuration record for 8.6C is transmitted to an 8.6B system, it will display 8.6B in the CONFIG.MGR 'FOR RELEASE' field when it is on the 8.6B system. It will display 8.6C when it is installed on the 8.6C system. 1.1.4.2. DELETE, CREATE, RENAME 1) RSC 516539 - A user is allowed to delete a file that is SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB070 Pg004 opened by others through the use of the DELETE, CREATE, and RENAME utilities. This was done by design; the operating system has always worked this way. The RSC requests that the users be notified if they are about to delete an "in use" file and be given the option of cancelling the delete. 2) SPR 517570 - The ADDGROWTH parameter of CREATE was not required on 9/8.5 releases, and ADDGROWTH = 0 returned an error. On 10/9/8.6 releases, the ADDGROWTH parameter IS required, and ADDGROWTH = 0 is accepted. Users upgrading to 10/9/8.6 from 9/8.5 releases need to add the ADDGROWTH parameter to CREATE parameter lines. In the next BOSS/VS release, ADDGROWTH will not be required, and ADDGROWTH = 0 will be accepted, thus making any further program changes unnecessary. 1.1.4.3. EXTTAPE EXTTAPE does not support PSAVEd programs. However, it gives an erroreous "End of Tape" message when it encounters a PSAVEd program (SPR 509607). 1.1.4.4. FAMILY 1) SPR 507152 - Disk numbers of the first multi-volume family created are used as defaults for subsequent families, if the subsequent families are created without exiting the FAMILY utility. The workaround for this problem is to exit the FAMILY utility after each multi-volume family is created. This will be fixed in the next BOSS/VS release. 2) SPR 507151 - When creating volume labels using the FAMILY utility (Option 4), the volume type (System or Data) of the first disk is retained as a default when creating volume labels for subsequent disks. However, if this default value is used (by pressing ), the volume label will not be updated with this default value for volume type, even though it displays this way on the screen. The workaround for this problem is to always key in "S" for System disk and "D" for Data disk, and never take the default for volume type. This will be fixed in the next BOSS/VS release. 1.1.4.5. GETDEVINFO GETDEVINFO does not return information on Batch jobs. 1.1.4.6. JOB MANAGER 1) Defined GROUPS are deleted at system reload. Job Groups to be kept on a more or less permanent basis should be created via commands entered in the System Startup command file, .SYSDATA.START.CMD. 2) JOB.CREATE does not allow the PAUSE=TRUE parameter to be passed. If the command is embedded in a program, all errors must be handled by the application. 3) BATCH jobs require an output file which is not auto- matically deleted. The user may need to delete these SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB070 Pg005 files on a regular basis to keep disk space available. 4) BASIC's FID (0) is a file for a BATCH job. This will be changed in an upcoming release so that FID (0) is the batch ID. 5) Quotes must be used around the user accounts when specifiying more than one user account in the GROUP.CREATE and GROUP.MODIFY parameter lines. (Example: GROUP.CREATE MYGROUP, TYPE=TERMINAL, PRIORITY=3, USERS="GROUP1.*, GROUP2.*") 6) RSC 511490 - If PRIORITY is not specified for TERMINAL and BATCH type jobs, the PRIORITY will default to 1. This default, although proper for BATCH type jobs, is normally too low for TERMINAL type jobs. It is recom- mended that a PRIORITY of 3 be specified for TERMINAL type jobs during GROUP.CREATE. (See example in item 5.) 7) RSC 511491 - The PRIORITY of SYSTEM type jobs cannot be changed, even though GROUP.MODIFY appears to allow the user to do this. 8) RSC 511491 - SYSTEM type jobs cannot be deleted, nor can they be modified. GROUP.MODIFY appears to allow the user to modify SYSTEM type jobs, but such modifications are not enforced. 1.1.4.7. MCSI All filelist access must be made by a user with File Security Override set to TRUE. 1.1.4.8. SAVERESTORE 1) On 8.5C/9.5C the three ISDC code files (ETWYOS, FOWYOS, SXTNOS) and the REMIDI files were changed to be un- organized (UNO) file types. This was done so DISKANALYZER would no longer flag these files as having an internal file problem. Files that are typed as unorganized were not supported by SAVERESTORE and the File System in releases prior to 8.5C/9.5C, so these files are rejected when an attempt is made to restore them on prior O.S. levels. This is why an ALT LOAD from tape must be done before the O.S. files are restored when upgrading a system that is currently on a release prior to 8.5C/9.5C. (The only exception to this is an upgrade from 8.4E. The same changes to the above 8.5C/9.5C files were also made to the 8.4E files.) 2) SPR 519167 - If the VERIFY option is on, and MBIII is pressed to skip a file that spans 2 tapes, SAVERESTORE returns the message 'SECTOR COUNT MISMATCH, CANNOT RESTORE'. The workaround is to ignore the message, press , and select option 9 to mount the next tape. This will be fixed in the next BOSS/VS release. 3) SPR 519427 - A system dump with the fourtuple 25,0,17,27 (Program error detected by mag-tape services module) can occur (rarely) during SAVERESTORE. The exact cause of this dump is still under investigation. If you experience this dump, please send it to Field Product SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB070 Pg006 Support along with a description of the steps taken in SAVERESTORE. This problem has been observed in other levels of 9/8.6 and 9/8.5E. 4) The following problems exist when using SAVERESTORE to convert old File System files (pre-8.4E) to O.S. levels 10/9/8.6E: a) SPR 519790 - Data files: Data files restored will receive an error "ERROR WHILE CALLING CONV85: I'M TOO OLD FOR THIS FILE SYSTEM!". The files will actually be restored and converted to the new file format. However, the following file attributes may change: - Owner - Last modified date - Last modified time The file will be accessible and no data corruption or loss will occur. b) SPR 519934 - Programs files:: Programs will restore properly, and no message will be issued from SAVERESTORE. However, the programs will be corrupted. These programs can be executed but cannot be LISTed or recompiled. Any attempt to do so will result in an ERR 137 from BASIC or "GETID: Invalid ID Address (15,1,137,0)" from the utilities. PSAVEd programs will probably not execute properly. The error "Byte offset field of pointer exceeds segment size, (1,159,52,3)" will appear when trying to execute PSAVEd programs. It is recommended that programs be moved using EXTTAPE. PSAVEd programs cannot be moved via EXTTAPE. Therefore the source will need to be moved to the new level and PSAVEd again. This problem ONLY EXISTS in 10/9/8.6E. It will be fixed in the next BOSS/VS release. 1.1.4.9. SPOOLER 1) SPR 509923 - The FORM utility does not allow over 14 individual printers to be entered for a specific form. 2) The SPOOLER NOTIFY function, which broadcasts a message to the top of a terminal screen when a print job has finished, will cause the screen to scroll if the cursor is on the last line of the screen. 3) SPR 514941 - Although SPOOLON appears on the SUBMIT and CLASS screens and is documented in the user manuals, assigning 'F' to this option does not RESERVE a printer on MPx 9/8.6 systems. SPOOLON is always 'T' (TRUE), meaning spooling is on. The RESERVE command should be used in place of SPOOLON = F. 4) RSC 512943 - Spool jobs sometimes print on the wrong form SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB070 Pg007 before SETFORM can be run. One workaround is to RESERVE the printer. Another workaround is as follows: a) When the Spool job (i.e. for payroll) is created, specify LOADFORMS = YES. This can be done on the SUBMIT screen or the "ATTR =" parameter on the BASIC OPEN statement. (The LOADFORMS option on a job can also be modified through Job Maintenance or SPJOB.MODIFY after the Spool job has been created.) This will cause the job to wait for a SETFORM before printing. The Spooler status will display "WAIT FORMS" when the job comes up in the queue. b) When it is time to print the job on a special form (i.e. paychecks), SUSPEND the printer at the end of the current job (WHEN = J). c) Mount the special forms in the printer (i.e. paychecks). d) Run SETFORM (with the Trial Form option, if desired). e) Move the printer to Spool mode. 5) SPR 519424 - A system dump with the fourtuples 2,10,33,11 (Instruction Fault in Spooler Module) and 1,146,0,11 (Range Violation) will occur if the printer name in a spool request is modified to a value greater than P99. This will be fixed in the next BOSS/VS release. 6) SPR 519554 - In certain rare circumstances, the control segment of a file becomes so corrupted that it cannot be repaired with DISKANALYZER. If this happens to the control segment of the Spooler REQUESTS file, the system will dump with the fourtuple 4,0,13,4 (Error trying to open or create .SYSDATA.SPL.REQUESTS) when trying to enter a TYPE 1 LOAD. The REQUESTS file cannot be accessed in any way, and the system cannot enter a TYPE 1 LOAD. The only solution is to do a complete backup of the family with SAVERESTORE in a TYPE 2 LOAD, initialize the Directory, and restore the backup. 7) SPR 518930 - Doing a DOWN.LOAD on an ISDC controller causes any spooled print jobs that are currently printing on serial printers attached to that controller to stop. The Spooler will show a "Stopped" status for these jobs, along with the fourtuple 31,0,9,2 (Power Failure Error). These print jobs must be restarted in the Spooler after the DOWN.LOAD. This is according to the design of the 9/8.6 Spooler. 8) SPR 519428 - Under certain circumstances spooled print jobs that are stopped while printing will sometimes remain in a "Stopping" status in the Spooler. This makes the printer unaccessible, even though that particular job is no longer printing. The only workaround is to reload the system, which will bring the job to a "Stopped" status and free the printer. This problem is under investigation by Software Engineering. 9) SPR 519697 - Using the 'EP' mnemonic on 4213 printers can cause unnecessary form feeds. The workaround is to SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB070 Pg008 use "'LF'," (line feed comma) at the end of the print statement (e.g., PRINT (x) 'EP',"TEST",'LF',). 1.1.4.10. TERM.TABLE SPR 502408 - When using the copy option of TERM.TABLE (Option #4) to copy the Primary file to the Secondary file, the copy is not successful. The workaround is to copy the Primary to the Secondary again without exiting the TERM.TABLE utility. The COPY will be successful the second time. 1.1.4.11. UPDATE SPR 505144 - When expanding a file, the screen display exceeds 100%. 1.1.4.12. UTILITY SPR 519642 - When accessing the Configuration Utilities through the UTILITY menu, option 3 is "Set Printer Band Table", which is !SETBAND in command mode (a Spooler utility). Option 3 of Configuration Utilities should be "Printer Band Translation Table", which is !BAND.TABLE in command mode. This problem will be fixed in the next BOSS/VS release. 1.1.5. LOGON RSC 507496 - The message "Logon disabled at this terminal, 'CR' to continue:" is displayed after a system load, if a logon is attempted when the System Startup command file has not completed execution. Enter 'CR' and the Logon should then be enabled. 1.1.6. BASIC 1) SPR 511886 - The use of "STATUS" to report DSR and CTS to BASIC does not work. This problem will be fixed in an upcoming release. 2) If the SORT utility has been executed from BASIC, and it encounters an error, BASIC will always return an error 0. 3) SPR 513998 - Terminal echo is lost when some unsupported utilities (e.g. HEADS) are called from BASIC. 4) An MTCS (MCS) tape drive cannot be accessed through BASIC. This was done by design, due to considerable differences in programming such devices verses 1/2-inch tape devices. 5) The significant enhancements of Business BASIC 86 introduced in 9.6/8.6 will restrict backward compatibility. Programs written or modified on 9.6/8.6 will not run on prior releases without recompilation. In addition, new Business BASIC 86 features introduced in 9.6/8.6 cannot be used in programs which will be run on 9.5/8.5 or 8.4 release levels. Intersystem transport packages or the CONVERTSP utility can be used to recompile programs written or modified on 9.6/8.6, provided the new BB86 features have not been used. EXTTAPE should be used to transport programs from 10/9/8.6 release levels to 9/8.5 and 8.4 release levels. EXTTAPE will recompile the programs as SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB070 Pg009 they are being transported. (ALL program and data files transferred from 10/9/8.6E release levels to 9/8.5 and 8.4 release levels must be transported with EXTTAPE.) 6) The system will log a user off while in BASIC CONSOLELOCK if both of the following 2 conditions are met: a) An END, STOP, or ESCAPE directive has just been executed in the BASIC program, and b) You enter carriage return or an invalid password 3 times. This is according to design. 1.1.7. FILE SYSTEM 1.1.7.1. Multi-Key Files 1) The following utilities will not operate on Multi-Key files: BCOM, BQR, CREATE, EDIT, EXTTAPE, FILESIZE, FTF, GSR, MCSI, NFSCONVERT, OLDDIR, OLDTAPE. 2) SPR 507831 - Two fields occupying the same space in a data record cannot both be keysets. 3) SPR 519377 - System ERROR 8,255,15,125 (Resource Error) or BASIC ERROR 15 can occur while adding records to an extremely large Multi-key file on release levels 10/9/8.6. In order for a Multi-key file to be large enough to possibly experience this problem, the sum of the sizes of the keys multiplied by the number of records in the file must be greater than 200 million. For example: Primary key: 15 bytes Number of records in the file: 100,000 1st secondary key: 25 bytes Sum of key sizes: x 50 2nd seconary key: 10 bytes Sum of key sizes: 50 bytes 5,000,000 As you can see, the above file does not qualify for the problem. The workaround for the problem is to drop a keyset and use a Sort file for that keyset instead. This problem will be fixed in the next BOSS/VS release. A special image may be available for earlier releases, if there is a need. If you experience this problem, please contact Field Product Support. 4) SPR 519633 - If an attempt is made to REMOVE a record from a Multi-key file in read-only mode, the system will dump with the fourtuples 2,10,38,25 (Instruction Fault in File System Multi-key Module) and 1,139,0,25 (Nil Pointer). The read-only mode is established by definition in the file's Usage Rights or by using OPEN INPUT. This problem occurs only if File System Security checking is enabled and only on 10/9/8.6E. It will be fixed in the next BOSS/VS release. 1.1.8. HORIZONTAL SOFTWARE SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB070 Pg010 The horizontal software packages of PRESENTATION SERVICES, GRAPH, and ORIGIN 2.0 and above typically have files that reside in the .SYS. node. If this is the case, these files need to be reinstalled in the .SYS. node after an O.S. upgrade. This can be accomplished by one of the following methods: a) Retain a copy of the .SYS. node used by the older O.S. and, after the O.S. upgrade, copy the old .SYS. node to the new .SYS. node with DELETE EXISTING DESTINATION FILE = NO. b) For PRESENTATION SERVICES, run the PS.INSTALL program, which will copy all the necessary PS files to the .SYS. node. For ORIGIN, copy the node .ORIGIN.R2xx.RT. to the new .SYS. node. If the users' prefixes include this ORIGIN runtime node, the ORIGIN files do not need to be in the .SYS. node. For GRAPH, copy the files .GRAF.GRAPH and .GRAF.GRAPHMAKER to the new .SYS. node. 1.1.9. COMMUNICATIONS 1.1.9.1. MAGNET and File Transfer Facility (FTF) 1) There is no automatic conversion of topology configuration files to the new Network Management Facility (NMF) configuration files when 9.6/8.6 is installed on an MPx system previously configured for B4NET/FTF (9.5 and earlier). The user is responsible for printing the previous configuration information before re-configuring the MAGNET and/or FTF network with NMF or EZCONFIG. 2) A reboot is necessary after the initial configuration of each system in the MAGNET/FTF network. Any subsequent modifications to the home station parameters or sub- network numbers also require a reboot to activate the changes. 3) Care must be taken to configure enough SVC's to support all remote concurrent activities; the number of remote X.25 sites accessed at any time cannot exceed the number of SVC's configured for the X.25 link; each FTF file transfer will require its own SVC. 4) FTF file transfers may experience Completion Code 149's (Network Services Timer Expired) when the system or network load is heavy, or when communicating over a LAN/WAN internetwork. 5) FTF file transfers via LAN are only allowed between MPx systems. 2000/3000 systems may not co-exist on the same LAN network as MPx systems. FTF file transfers are allowed to unlike systems (MPx, 2000/3000, 13xx) over X.25 links; however, automatic data conversion for unlike character sets is NOT performed. The Intersystem Transport program, FTFIT, must be used for data conversion of FTF file transfers between unlike systems. 6) Three types of X.25 packet data switches were used during the test cycle: SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB070 Pg011 o Memotec 8500 o Dynapac Model 8 o Dynapac Model 12 Results of the testing showed that the Memotec 8500 should only be used for networks which have a low load or when performance is not a factor. The Dynapac Model 8 can handle heavier network load but the baud rate is limited to 9600 BPS. The Dynapac Model 12 is recommended for networks with heavy loads - up to 7 MPx systems at 19.2K BPS using 128 byte packets. A problem where the Dynapac Model 12 went into a 'lockup' mode was found when running 5 or more systems at 19.2K BPS and using 256 byte packets. To prevent this problem, the packet size should be reduced to 128 bytes. (The Dynapac Model 12A is recommended over the Dynapac Model 12 to avoid MAGNET errors due to "restarts") 7) To optimize throughput of X.25 communications, it is recommended that the IMLC be configured with X.25 on port A and nothing on Port B. This configuration will allow running at baud rates of 9600 BPS and above, and configuring more SVC's and larger data packet sizes. Other IMLC products such as 27xx/37xx, 3270, and Dataword should be configured on another IMLC. 9/8.6 supports up to 4 IMLC boards. 8) LAN/WAN internetworking has a significant impact on the gateway system. For this reason, the largest and/or least busy system on the subnetwork should be configured as the gateway system. The minimum system type for a gateway should be an 8030 if possible. 9) A maximum of 63 systems may exist on a MAGNET LAN network. However, performance degradation will occur when more than 8 systems are actively transmitting data, especially during file copies. 10) MAGNET event logs are initially set in the GROUP utility to LOGFILES=10 and LOGRECS=100. Although these para- meters are normally sufficient, depending on network activity the event log sizes may have to be increased. To increase the size, modify the .SYSDATA.START.CMD file to include the command: GROUP.SETLOG MAGNET,LOGFILES=n,LOGRECS=n,VERIFY=FALSE where 'n' is the number desired; recommended values are LOGFILES=25 and LOGRECS=200. The logfiles will be increased with the next reboot of the system. If you wish to increase the logfiles on a temporary basis, the logfile parameters can be modified through the JOB MANAGER utility. The modifications will take effect immediately but will stay in effect only until the system is rebooted. 11) If MAGNET is installed on a system already running in production mode, some degradation may be experienced. If SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB070 Pg012 this occurs, the system should be upgraded in terms of memory and/or CPU. 1.1.9.2. Asynchronous Transport Package (ATP) ATP 4.0 will be the ATP release available for 9/8.6. ATP 4.0 provides new features such as autodial, scheduler, line turn-around, and performance enhancements. ATP 4.0 is NOT compatible with previous releases of ATP; all systems communicating with ATP 4.0 systems must also upgrade to 4.0. 1.1.9.3. 19.2K BPS Support TERM.CONFIG permits configuration of 8-Way and 16-Way ports with a BPS of 19.2K. See the section on 19.2K BPS in the 9.6A/8.6A Software Announcement for guidelines on configuration cautions in regard to aggregate ISDC throughput. 19.2K BPS is not supported on the 4-way ports on releases 10/9/8.6E. 19.2K BPS will be supported on the MCS/M, the 4-way for the ADVANCED SERIES, beginning with the next BOSS/VS release. 1.1.10. HARDWARE 1.1.10.1. Terminals 1) Very fast typing may cause DT-4312 terminals to drop characters. This occurence is rare. 2) In order to use an industry standard printer as a slave off a DT-4313 terminal, the terminal must have REV E firmware. If the DT-4313 terminal does not have REV E firmware, only screen dumps can be printed. 3) As of release 9/8.6C, T0 must be a model 4309 or later terminal on all systems, or an HVDT on 7xxx/8xxx/9xxx systems. Terminal models 7250 and 7270 are no longer supported as T0. 1.1.10.2. MCS Board 1.1.10.2.1. When Upgrading from 8.4D and Below When upgrading from 8.4D or below to 8.6/9.6, it is es- sential that the 4-Way (MCS board) be enabled (SW1 position 3). Not doing so will result in a dump with the fourtuple 11,13,0,0 occurring when attempting to enter a TYPE 3 LOAD after the update of slot 0. 1.1.10.2.2. MCS Revision "S" MCS PCBA P/N 903374-001 at revision "S" now has the ability to be switch selectable (SW1-4) to match the different address schemes between MPx 7xxx/8xxx Series Systems and MPx 9xxx Series Systems. The "S" revision level is not mandatory for the function of either system. MCS revision "S", when used in MPx 7xxx/8xxx Series Systems, must be set for MPx 7xxx/8xxx systems. Failure to do so will cause the system load to abort with BOOT STRAP ERROR "FFFF". SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB070 Pg013 MCS revision "S" used in MPx 9xxx Series Systems, (when switch selected for MPx 9xxx systems), will allow any controller to be board addressed from the range of 1 to 63 with the exception of board addresses of 16 through 31 which are not valid on MPx 9xxx Series Systems and should never be used. If set for MPx 7xxx/8xxx Series Systems and used in MPx 9xxx Series Systems, the board addresses of 32 thru 47 may only be used for the IMLC PCB. There will also be no support for memory above 12 megabytes. (Revision "T" is required for support of more than 12 megabytes of memory.) The following are the switch settings for revision "S" or above MCS board: Switch SW1-4 open: MPx 7xxx/8xxx Series Systems Switch SW1-4 closed: MPx 9xxx Series Systems 1.1.10.3. BMTC Because the BMTC is a shared memory controller, it is not possible to direct a dump to a tape drive connected to a BMTC. On systems where a BMTC is the only tape controller (as is the case with the ADVANCED SERIES and 9xxx Series Systems) it is essential that the dump area on disk be large enough. See Field Bulletin #211, "Computing the Dump Area Size on MPx Systems", for further information. 1.2. FOR MPX 9XXX SERIES SYSTEMS ONLY 1.2.1. HARDWARE 1.2.1.1. IMLC 1) The Memory Map Controller board numbers of the IMLC's must be in the range 32-47. If Revision level "S" or above of the MCS board is used and set for MPx 9xxx Series Systems, this restriction is removed. See the information on the MCS board in this section. 2) The "JMP C" self test jumper should be installed on the IMLC PCBA's. This is a hardware requirement for 9xxx systems only, and it is not related to the 9.6/8.6 O.S. level. For further information on this jumper, see the field bulletin titled "MPx 8xxx to 9xxx Upgrade IMLC NOT RECOGNIZED". 1.3. FOR THE ADVANCED SERIES ONLY 1.3.1. POWER FAIL SPR 518907 - A "DRIVE OFFLINE" message appears briefly during a power fail recovery. This message should be ignored. This problem will be fixed in the next BOSS/VS release. 1.3.2. DIAGNOSTICS 1.3.2.1. High Frequency Margins on the ADVANCED SERIES The ADVANCED SERIES processor has the capability to run at a faster clock rate for diagnostic purposes. This capability is intended for diagnostic testing of the CPUs ONLY. The SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB070 Pg014 system should never be used at the higher clock rate except for diagnostic purposes. When the system is running at high frequency margins, the following message appears on the load screen "WARNING: SYSTEM IS RUNNING AT CLOCK MARGIN". DO NOT RUN NORMAL PROCESSING WHEN THIS MESSAGE IS DISPLAYED. (MCS/M boards at REV D and below cause this message to be displayed, even though high frequency clock margining has not been set on the MCS/M board.) The following warnings should be observed when using high frequency margins. The boards mentioned below should not be considered faulty and replaced. a) THE SYSTEM WILL NOT FUNCTION RELIABILY AT HIGH CLOCK MARGINS PLUS VOLTAGE MARGINS! This will result in failures which are not due to bad hardware. The system can, for diagnostic purposes only, be run at clock margins or voltage margins but never both at the same time. b) The LAN self-test will fail at high clock margins. This will result in a failure to checkin with the operating system at boot time. The operating system will boot and not see the LAN board since it fails the self-test initiated by terminal services during O.S. initialization. DEMON will still see the LAN board. This LAN self-test would also fail when run by DEMON. This is prevented by having DEMON check for the clock rate and not run the tests which will fail at the higher clock rate. The tests affected are the UART counter/timer tests which used the system clock to time operations to a specific tolerances. c) The DEMON 16-way controller local loopback tests fail at high clock margins. These tests are only run by DEMON and will be omitted when DEMON detects the higher clock rate. 1.3.2.2. DMA 1 "Timeout" LED Running REMIDI The ADVANCED SERIES REMIDI "NEP" tests force a "bus error". This results in a "timeout" error indication by the DMA 1 board (amber LED comes on). This is due to a bug in the DMA 1 firmware (board revision R). This will be corrected in revision T of the DMA 1. Until then this condition can be expected on all the DMA 1 boards when REMIDI is run. The LEDs should be manually reset when REMIDI testing has been completed. 1.3.2.3. REMIDI ERROR 2701 on NEP Board When running the REMIDI 2700 test, an ERROR 2701 may be returned on the NEP board on rare occasions. Ignore this message. This problem will be fixed in the next BOSS/VS release. 1.3.3. TERMINALS High Speed terminals (and the VCON controller board) are not SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB070 Pg015 supported on the ADVANCED SERIES. ORIGINATOR: J. Melendez SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB070 Pg016 FIB 00071 05/12/89 *** Dumps 2,6,1,10 Caused by User Defined Function [ WPSF 536 ] *** In BOSS/VS BASIC, a condition has been found that when user defined functions are used under certain conditions, it may cause a system dump 2,6,1,10. This dump may occur when the formal parameters in a function (i.e. those in the parenthesis) are used on the left hand side of an assignment statement that also contains that function. For example: 10 DEF FNAB$(E$)=E$+"XXXX" . ^ . | . ----------- <== CANNOT BE THE SAME VARIABLES !!!! . | . v 100 E$=FNAB$("KK") Do not construct code in the above fashion. It may not always dump the system but it could. This applies to string and numeric user defined functions and applies to all variables in the parameter list of the function. There are no plans to fix this in a future release. The workaround is to use different variables on the left hand side of the assignment statement. ORIGINATOR: R. Case SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB071 Pg001 FIB 00072 08/17/89 *** MVP Bar Code Problems when upgrading from 8/9.4 & 8/9.5 to 8/9.6 *** There is a problem with Bar Code software when a customer upgrades from 8/9.4 or 8/9.5 to 8/9.6 ( on any MPX system). A customer printing Bar Code on a 4214/4219 printer after an upgrade might experience their Bar Code software not printing bar codes. Before level 8.6 it was not necessary to have an 'EO' command at the end of a line that began with 'BO' and contained the mnemonic $07$. On level 8.6 this is necessary. An example of this can be found in Worldwide product Support Hardware Bulletin number 10 (BAR CODE PRINTERS), section 11.0 UPC-A Bar Code. The identical example can also be found on page 4-40 of the MBF PT-4214/PT-4219 Bar Code Printer User Reference Manual (M5177C). If you attempt to run this program on a 4214 or 4219 printer on OS level 8/9.6 it will not print the test bar code. If you add an 'EO' at the end of statement 40 the program should work correctly. It will not because there is one other bug in the program. This bug is in statement 110. In this statement the data field should be surrounded by apostrophes as in statement 70. With these two changes the program should now work correctly and the Bar Codes will print out as they appear in the manual. Here are the two statements as they appear in the manual: NOTE: C$=$07$ (statement 30) 40 PRINT(1) 'BO',C$,"CREATE;UPCA" 110 PRINT(1) "12345678876" Here is how the statements should read: 40 PRINT(1) 'BO',C$,"CREATE;UPCA",'EO' 110 PRINT(1) "'12345678876'" It would be helpful BEFORE an upgrade occurs to warn a customer that they might have to change some lines of code to have their Bar Code printers work properly after the upgrade ! ORIGINATOR: Kim Yaworsky SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB072 Pg001 FIB 00073 08/31/89 *** Explanation of Disk Fragmentation [ WPSF 552 ] *** This field bulletin will explain about disk fragmentation, why it occurs, why it can slow down a system, and how to "de-fragment" a family. WHAT IS DISK FRAGMENTATION ??? Disk fragmentation occurs when different parts of a file do not reside contiguously on disk, that is, they are spread out all over the disk MBF files use proportional growth. This means that a file only occupies the disk space needed to accommodate the current number of records in the file. For efficiency, the file system will allocate some extra records to cut down on the number of times space allocation occurs. Files are allocated in blocks of sectors called extents. Every file is made up of one or more extents. The size of each extent is controlled by the growth parameters of a file. A file exists as: _____________ | | | | | EXTENT 1 | | | |_____________| | | | EXTENT 2 | |_____________| | | | EXTENT 3 | |_____________| ____________ | | | EXTENT N | |____________| The size of EXTENT 1 is controlled by the "INITIAL GROWTH" parameter. The size of EXTENT 2 through EXTENT N is controlled by the "ADD GROWTH" parameter. These parameters are defined when the file is created and the values specified are the number of records to allocate and to grow by. For example, if the INITIAL GROWTH=100, ADD GROWTH=50, then the first extent will contain enough sectors for 100 records. Each additional extent will contain enough sectors for 50 records. These extents continue until the file reaches maximum size. Ideally, the extents of a given file should exist side by side on the disks to ensure maximum performance. This way the disk heads don't have to seek all over on the disk; the seeks are concentrated in one area. When a file becomes fragmented, the extents of the file are not side by side on the disk but scattered throughout the family. This can cause a performance degradation, especially, if the fragmented files are heavily used. Usually a file with 8 or more extents is considered to be a poor performance candidate. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB073 Pg001 HOW TO FIND FRAGMENTED FILES There is an utility called FINDEXTENTS located under the .Rxxxx.INST. node. This utility will prompt you for an output filename, a family name, a starting node, and extent threshold. You may specify an entire family or just a specific node. The threshold should be set to 8. This means any file with 8 or more extents will be displayed. The DIR utility will also flag any file that has more than 20 extents. This is noted by an asterisk (*) appearing next to the number of sectors that a file occupies when doing a full attribute listing of a file or files. HOW TO "DE-FRAGMENT" A FILE OR FILES To fully de-fragment a file or files, you must make a file by file copy of the of the family by using SAVERESTORE or COPY utility initialize the family, and restore the files. When files are restored from tape to a newly initialized family, an attempt is made to collapse the current file into one extent which will then grow by the number of records specified in the ADDGROWTH parameter. It is important to note that IMAGE backup utilities cannot be used for the backup. The backup up method must be a file by file method. Only this method ensures that all files will contain just 1 extent after file restoration. A short term solution is to copy the file to another name on the same family delete the old file and rename the one just created. This operation will usually reduce the number of extents that a file has but may not reduce it to a satisfactory level. This method is a short term solution until a file by file backup, initialization, and restore can be done. PREVENTION OF FRAGMENTATION Certain steps can be taken to minimize file fragmentation: A) When the file is first created, make the size of the initial extent the same as the maximum number of records. This will ensure that the file will contain one extent. The drawback to this is that the file will be at its full size when created and may waste some disk space until the file is full. This is ideal for files, which it is known before hand, that will remain full or nearly full or will be filled quite quickly. It is done by setting the "INITIAL" GROWTH field in the CREATE utility to the maximum number of records in the file. B) Don't use extreme values for INITIAL GROWTH and ADD GROWTH parameters. The default on creation for INITIAL GROWTH is 60% of the maximum number of records and the default for the ADD GROWTH is 40% of the maximum number of records. If the ADD GROWTH is made too small, this will cause the file to become fragmented. The ADD GROWTH should be at least 15% or higher of the maximum number of records. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB073 Pg002 C) The COMPACT utility returns sectors that have been physically allocated to a file but are not in use by the file currently. The extents are returned to free space starting from the end of the file, and continuing until in-use extent is encountered. The file is now considered "compacted". While this returns space to file system, it could eventually promote file fragmentation. If two extents are side by side and COMPACT returns one of them to free space, there is no guarantee when another extent needs to be allocated for that file, that it will be adjacent to the last extent of the file. Therefore, the COMPACT utility should be used sparingly. ORIGINATOR: Randy Case SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB073 Pg003 FIB 00074 10/27/89 *** Warnings/Special Considerations for BOSS/VS n.6G [ WPSF 559 ] *** These Warnings and Special Considerations are applicable to release levels 10/9/8/6G. This Field Bulletin is part of an effort to expand the reporting of known problems and special considerations to the field. C O N T E N T S 1 Warnings and Special Considerations 1.1 For the 10/9/8.6G O/S release and below 1.1.2 Different O.S. Levels in Adjacent Slots 1.1.3 SECURITY.DATA file 1.1.4 Downgrading from 10/9/8.6G Releases 1.1.5 Software Announcement on Tape 1.2 Diagnostics Removal 1.3 UTILITY 1.3.1 DIR 1.3.2 ALB (Auditor Log Book) 1.3.3 COMPARE 1.3.4 ERRORLOG 1.3.5 EXAMINE 1.3.6 FINDEXTENTS 1.3.7 GSR ( Global Search and Replace) 1.3.8 SAVERESTORE 1.3.9 SPOOLER/PRINTER 1.3.10 RENAME 1.3.11 UPDATE 1.3.12 UPDATE.RIGHTS 1.3.13 DISKANALYZER 1.3.14 TERM.CONFIG 1.3.15 EXTTAPE 1.3.16 CONFIG.MGR 1.3.17 MCSI 1.3.18 DEVICE ERROR 1.4 BASIC 1.5 CLI (Command Language Interpreter) 1.6 TBC COMMUNICATIONS 1.7 FILE SYSTEM 1.8 JOB MANAGER 1.9 FTF (File Transfer Facility) 1.10 SCSI (Small Computer System Interface) 1.11 MAGNET 1.12 TERMINALS SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB074 Pg001 1.13 ATP (Asynchronous Transport Package) 1.14 HORIZONTAL SOFTWARE 1 WARNINGS AND SPECIAL CONSIDERATIONS 1.1 FOR THE 10/9/8.6G O/S RELEASE AND BELOW 1.1.2 Different O.S. Levels in Adjacent Slots As of release 9/8.6C, positioning of the image slots has been adjusted slightly. Therefore, OS/WCS levels previous to 9/8.6C cannot reside in slots on the same disk with released levels 9/8.6C and above. 1.1.3 SECURITY.DATA File The SYSDATA.SECURITY.DATA file is converted to a new format during an upgrade to O.S. levels 9/8.6C and above. This converted SECURITY.DATA file cannot be used on O.S. levels previous to 9/8.6C. Therefore, if you are upgrading to 10/9/8.6C from a release prior to 9/8.6C, the SECURITY.DATA file should be saved on the previous release before the upgrade. In the event of a downgrade, this old SECURITY.DATA file must be restored on the previous O.S. level. 1.1.4 Downgrading from 10/9/8.6G Releases The only acceptable downgrades from 10/9/8.6G releases are to 10/9/8.6E or 9/8.6C releases. Downgrades to releases prior to 9/8.6C *11 may potentially cause control segment corruption. 1.1.5 Software Announcement on Tape The 10/9/8.6G Software Announcement exists as a serial file on the O/S release tape. The name of this file is : .R6Gxx.INST.DOC.ANNOUNCE6G. This file can be restored and SUBMITted to a printer. When upgrading or installing a system with this release please refer to this Software Announcement. 1.2 Diagnostics Removal Starting with the 10/9/8.6G O/S release, customers that have not signed a Diagnostic Product License Agreement will receive a O/S tape that does not contain the DEMON, REMIDI or Enhancer/ Tracker tools. (Enhancer/Tracker are now included as part of the Diagnostic tools and released accordingly). These tools must be removed from the system. This is a U.S./Canadian policy only. Please refer to the 10/9/8.6G Software Announcement for the Diagnostic Removal Procedure. 1.3 UTILITY 1.3.1 DIR SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB074 Pg002 1. SPR 521415 - !DIR (FAMILYNAME).*! will display no file found even if FAMILYNAME is not enabled. 2. SPR 522725 - !DIR does not accept a MB IV to exit at the " 'CR' to continue " if files have ALB turned on. 3. SPR 520549 - Display a Multi-key file and chose the option "'F' = Format String" might give you a "String Limit Exceeded" error. (1,233,0,32) 1.3.2 ALB (Auditor Log Book) 1. SPR 521840 - "MAGNET SHUTDOWN COMPLETE" error might occur if you try to delete a file that has ALB turned on and: A) Change the System name. B) Take a removable pack that has this file to another system. C) Reboot the system with another BOSS pack and it has a different System name. The file has the full file name (including the installation name) and when trying to delete this file the system tries to access the installation name. 2. SPR 521248 - You will get an error 32,116,59,3 (Invalid Software Key for ALB), if you copy a file that has ALB turned on to a system that does not have ALB installed and try to delete this file on the system that does not have ALB installed. The file will be deleted so you should just ignore the error. 3. SPR 522668 - Dump 2,10,6,32 (Instruction Fault File System Module) and 1,241,0,32 (String Limit Exceeded) will occur when you try to copy a file with ALB turned on and the log file is on a different family and the length of the file name is greater than 25 characters (does not include Installation name, Family name, or "()[]"). 4. SPR 521712 - You will get a "LOG File not found" error if you do the following: A) Set your prefix to a Family that is not enabled. B) Create a file using the !CREATE utility and specify AUDIT LOGGING ="Y". The AUDIT FAMILY NAME will de- fault to the Family that is not enabled. C) After "ENTRIES CORRECT " ="Y" you will get the error. 5. SPR 523210 - Using COPY or SAVERESTORE, the Logfile family name is changed to the default family on the system instead of the family that contains the source file. 6. SPR 523051 - Automatic switch with Indexed files while open will corrupt the Indexed file. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB074 Pg003 7. SPR 523325 - Under certain conditions (Please call FPS for details) using ! UPDATE from the command line mode and using ALB may cause an error 16,37,17,47 (Invalid number of Log records parameter). 8. SPR 523804 - DUMP 2,10,38,25 (Instruction Fault in File System Multi-Keyed Files Module) and 1,157,34,25 (Nil Pointer) will occur if you COPY/SAVERESTORE a MK-File that has ALB turned on to a system that does not have ALB and you try to write to this MK-file. WORKAROUND: Is to turn ALB off for the file before the COPY/SAVERESTORE. 9. Audit logging is not supported on files with special character file names. 1.3.3 COMPARE 1. SPR 520420 - Comparing files with only one record will always compare even if the records are different. 2. SPR 518626 - Indexed and Direct files will not display the first byte. Example : Write to the Indexed and Direct file a record "ABCDEF", compare these files and it will display "BCDEF" it will not display "A". 1.3.4 ERRORLOG 1. SPR 522220 - When listing tape unit errors, the unit numbers will change but the device name will remain the same. When you list the errorlog you will see that the unit number will change. (Example: 624 to 632, but the device name will always be R0.) 1.3.5 EXAMINE 1. SPR 516693 - Using Quiet =T will hang a terminal. EXAMPLE: !EXAMINE DIRECTFILE, FORMAT=KEY, OUTPUT=LP, QUIET=TRUE. The same example with QUIET=FALSE will work without problems. 1.3.6 FINDEXTENTS 1. SPR 521274 - If you output to a file that exists, it will overwrite the file and you will lose whatever information the old file had. 1.3.7 GSR (Global Search and Replace) 1. SPR 522527 - Will not always replace the search pattern when token characters are used. Example: 10 B$=B$(X+2) 20 BB$=B$(X+2) Enter "R" to search and replace, enter %B as the start specifier and enter BF$ as the replace pattern. The result will be that: SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB074 Pg004 10 BF$=BF$(X+2) (Correct) 20 BB$=B$(X+2) (Incorrect, should have been BB$=BF$(X+2) ) 2. SPR 520970 - Will not lock file while running GSR. This can be a problem if someone else is using this file (data can be lost). 1.3.8 SAVERESTORE 1. SPR 518915 - Masking capabilities do not work the same as with other utilities. Some masking capabilities that can be used in the COPY utility will not work in the SAVERESTORE utility. A number of masking problems have been reported by the field: A) SPR 514224 - Doing a compare with MASKING will not compare all files correctly. B) SPR 521707 - Restoring using RENAME delimiter will restore the file with an incorrect destination name. EXAMPLE: .^R6G43.BURN.,(DISK).^ should restore the files as (DISK).R6G43.BURN.AUTO but the files are restored as (DISK).AUTO. 2. On 8.5C/9.5C the three ISDC code files (ETWYOS, FOWYOS, SXTNOS) and the REMIDI files were changed to be unorganized (UNO) file types. This was done so DISKANALYZER would no longer flag these files as having as internal file problem. Files that are typed as unorganized were not supported by SAVERESTORE and the File System in releases prior to 8.5C/9.5C, so these files are rejected when an attempt is made to restore them on prior O.S. levels. This is why an ALT LOAD from tape must be done before the O.S. files are restored when upgrading a system that is currently on a release prior to 8.5C/9.5C. (The only exception to this is an upgrade from 8.4E. The same changes to the above 8.5C/9.5C files were also made to the 8.4E files.) 1.3.9 SPOOLER/PRINTER 1. SPR 522529 - If you have Serial printers on-line and you look at the "DISPLAY PRINTER STATUS" utility it will show the printer status as IDLE. Take the printer off-line and the status field continues to display IDLE until you submit a job to this printer, then the the status will change to OFF-LINE or I/O error. 2. SPR 522539 - On serial printers that are OFF-LINE you can set a FORM and print a trial form without getting a error. MBF DMP serial printers will get the following error message: " Trial Form Printing Error. Load Forms xxxx may be used on Idle Printers only ". 3. SPR 521588 - Printing a job that has greater number of characters than what a printer can support will cause that printer to hang. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB074 Pg005 EXAMPLE: Set a form that has 511 CPL to a whisper printer and send a line with 256 characters in compress print ('16') to this printer, the Printer/Job will hang. 4. SPR 521299 - Using 'SPMx' will cause positioning of data to be incorrect on a 4214 printer. EXAMPLE: PRINT (X) 'SPM2',@(15),"TEST" will result TEST being printed out at position 11 instead of position 15. WORKAROUND: Add a 'CR' after the 'SPM2': PRINT (X) 'SPM2','CR',@(15),"TEST". 5. SPR 521326 - Class defined with Page Numbers and Page Headings = "Y" will print the page numbers and page headings on alternate pages only. This will occur if the Form was defined as 110 CPL but the job had 132 CPL. 6. SPR 515285 - On a T2LD an attempt to print out to a printer that was OFF-LINE will hang the system. Putting the printer On-LINE will unhang the system. 7. SPR 521669 - Powering serial printers OFF and ON will produce a error=0 when trying to print to these printers. Please refer to Field Bulletin 343A for more information regarding problems when powering serial printers OFF/ON. 8. SPR 522343 - Error=0 (Slave Printer Off-line) will occur after you 'ESCAPE' from a program that is printing to a slave printer. 9. SPR 521170 - Using 'PG' will result in a timeout error (err=0) with a PT-4224 slaved to a DT-4314 10. SPR 523362 - An extra line feed will be inserted after loading the VFU. WORKAROUND: Add a comma after the VFU command. EXAMPLE: PRINT (X) 'SL',"10002",'EL' (Will produce a 'LF') PRINT (X) 'SL',"10002",'EL', (no extra line feed) 11. The Spooler does a automatic form feed at the start of a print job after rebooting a system, even if the CLASS is set for "No form feed at start." This will only happen to the first job sent to the printer after rebooting a system. 12. Spooled jobs queued to serial printers might hang. In the Spooler Job Maintenance Utility the job will display the status of "PRINTING" but percent done will be zero and nothing is being printed. Also, a job will say "STOPPING" but will never stop. You will have to reboot the system in order to unhang the printer. 13. SPR 509923 - The FORM utility does not allow over 14 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB074 Pg006 individual printers to be entered for a specific form. 14. The SPOOLER NOTIFY function, which broadcasts a message to the top of a terminal screen when a print job has finished, will cause the screen to scroll if the cursor is on the last line of the screen. 15. SPR 514941 - Although SPOOLON appears on the SUBMIT and CLASS screens and is documented in the User Manual, assigning 'F' to this option does not RESERVE a printer on MPx 9/8.6 systems. SPOOLON is always 'T' (TRUE) meaning spooling is on. The RESERVE command should be used in place of SPOOLON = F. 16. RSC 512943 - Spool jobs sometimes print on the wrong form before SETFORM can be run. WORKAROUND #1: RESERVE the printer. WORKAROUND #2: As follows: a) When the spool job (i.e. for payroll) is created, specify LOADFORMS = YES. This can be done on the SUBMIT screen or the "ATTR=" parameter on the BASIC OPEN statement. (The LOADFORMS option on a job can also be modified through Job Maintenance or SPJOB.MODIFY after the Spool job has been created.) This will cause the job to wait for a SETFORM before printing. The Spooler status will display "WAIT FORMS" when the job comes up in the status queue. b) When it is time to print the job on a special form (i.e. paychecks), SUSPEND the printer at the end of the current job (WHEN = J). c) Mount the special forms in the printer (i.e. paychecks). d) Run SETFORM (with the Trial Form Option, if desired). e) Move the printer to Spool mode. 17. SPR 518930 - Doing a DOWN.LOAD on an ISDC controller causes any spooled print jobs that are currently printing on serial printers attached to that controller to stop. The Spooler will show a "Stopped" status for these jobs, along with the fourtuple 31,0,9,2 (Power Failure Error). These print jobs must be restarted in the Spooler after the DOWN.LOAD. This is according to the design of the 9/8.6 spooler 1.3.10 RENAME 1. SPR 522457 - After getting a valid "Insufficient Priviledge " error any subsequent attempt to use this utility will result in the following message: "Port must be closed for current operation and is open". After getting the "Insufficient Priviledge", you must first exit completly out of SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB074 Pg007 the utility and then you can re-enter it without problems. 1.3.11 UPDATE 1. SPR 521592 - After using this utility to add more records to a file, if you use DISKANALYZER on this file it will report ERR=29 (Unaccounted Space for this file). 2. SPR 522830 - If you use this utility more than once to add records to a file (same file used twice in UPDATE), when trying to add a new record after the second time that this file has been thru the UPDATE utility you will get a ERROR=2 and DISKANALYZER will give you ERR=29 (Unaccounted Space for this file). You must RECONSTRUCT this file in order to correct the errors. EXAMPLE: A) Create a Sort file with 100 records and Key size of 16. B) Write a program to fill this file and get an error=2. C) Run !UPDATE and add 15 records (After this if you check this file with DISKANALYZER it will report the error=29, but the file is not yet corrupted). D) Write 15 more records to the file and you will get an error =2. E) Run !UPDATE again to add 15 more records. F) Try writing a new record and you will get a false error=2. The file is now corrupted and you must RECONSTRUCT this file. WORKAROUND: Add enough records to the file the first time you use !UPDATE or after using !UPDATE, reconstruct the file. 1.3.12 UPDATE.RIGHTS 1. SPR 520159 - You will get a "User's Rights Specification" error when a file has more than one line of User's Rights. 1.3.13 DISKANALYZER 1. SPR 520888 - Will show files with 0 records but !DIR will show that these files do have records. 2. SPR 521404 - Option 1 (Find files that lack integrity) will find files with problems (Invalid Format) but, option 3 (Validate and Reconstruct) will not show any problems with this file. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB074 Pg008 1.3.14 TERM.CONFIG 1. RSC 522966 - I/O translate is only supported on devices configured as TERMINAL. It is not supported when configuring ASYNC devices. 1.3.15 EXTTAPE 1. SPR 509607 - EXTTAPE does not support PSAVEd programs. However, it gives an erronreous "End of Tape" message when it encounters a PSAVEd program. 1.3.16 CONFIG.MGR 1. A configuration record can only be installed from an account with a USER LEVEL of 3. 2. Printer output cannot be directed to a specific printer. All output goes to P*. 1.3.17 MCSI 1. All filelist access must be made by a user with File Security Override set to TRUE. 1.3.18 DEVICE ERROR An error 2,6,17,2 (String may not be resized unless flexible), will occur in the following utilities: SECURITY, DEVICES, DOWN.LOAD and NEWX, if the number of DEVICES configured on the system exceeds 409. DEVICES include all terminals, all printers (serial, parallel and slave), all tape drives, all I devices (DATAWORD, TBC, 3270, X.25, all sockets) and all ghost tasks. To find out how many DEVICES are configured on a system, type the following in BASIC: CALL "GETDEVINFO",A$ PRINT LEN (A$)/10 The print statement will give you the number of devices. WORKAROUND: Reduce the number of devices configured on the system to 409 or less. EXAMPLE: Reduce the number of slave printers. 1.4 BASIC 1. SPR 516420 - You will get an ERROR=24 (Function name definition error) when trying to MERGE files that have the same DEF xx functions. EXAMPLE: PROGRAM 1, Statement 100 DEF FNABC (D,E)= PROGRAM 1: D-E PROGRAM 2, Statement 500 DEF FNABC (A,B)= PROGRAM 2: A+B When trying to do a MERGE you will get the error=24. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB074 Pg009 2. If a BASIC program RUNs another BASIC program which itself RUNs the first program, (This is known as the RUN/RUN problem in FPS) there is a chance that this process will never time-out and allow any other processes to run (in other words hang the system). 3. If the SORT utility has been executed from BASIC, and it encounters an error, BASIC will always return an error 0. 4. An MTCS (MCS) tape drive cannot be accessed through BASIC. This was done by design, due to considerable differences in programming such devices versus 1/2-inch tape devices. 5. The significant enhancements of Business BASIC 86 introduced in 9/8.6 will restrict backward compatibility. Programs written or modified on 9/8.6 will not run on prior releases without recompilation. In addition, new Business BASIC 86 features introduced in 9/8.6 cannot be used in programs which will be run on 9/8.5 or 8.4 release levels. Intersystem transport packages or the CONVERTSP utility can be used to recompile programs written or modified on 9/8.6, provided the new BB86 features have not been used. EXTTAPE should be used to transport programs from 10/9/8.6 release levels to 9/8.5 and 8.4 release levels. EXTTAPE will recompile the programs as they are being transported. (ALL programs and data files transferred from 10/9/8.6G release levels to 9/8.5 and 8.4 release levels must be transported with EXTTAPE.) 6. SPR 511886 - The use of "STATUS" to report DSR and CTS to BASIC is not supported. This will be fixed in an upcoming release. 7. GETDEVINFO does not return information on Batch jobs. 1.5 CLI (Command Language Interpreter) RELEASE 1. SPR 522476 - Doing a !RELEASE * will not release Batch Jobs or Magnet Servers. 1.6 TBC Communications 1. SPR 520796 - TBC protocols using SPOOLing may cause DATA corruption. It is recomended to always define the receive queue with spooling turned off. 1.7 File System 1. SPR 520660 - Indexed files created with maximum record size (32768) will get an error 47 when trying to read records. 2. SPR 521857 - Dump 2,10,37,65 (Instruction Fault SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB074 Pg010 File System Single Keyed Module) and 1,238,0,65 (Invalid Instruction) will occur if you try to remove records from a direct/sort file without using the KEY= option ( REMOVE (x)) and the files have greater than 50 records. If less than 50 records, the system will return an error 8,4,13,68 (Invalid Current record Position). 3. SPR 515010 - When QUIET=T (or QUIETON) and an output file are specified in a utility command, and the utility encounters an error, the error will not be written to the output file. 4. RSC 516539 - A user is allowed to delete a file that is opened by others through the use of the DELETE, CREATE, and RENAME utilities. This was done by design; the operating system has always worked this way. The RSC requests that the user be notified if they are about to delete an "in use" file and be given the option of cancelling the delete. 1.8 JOB MANAGER 1. Defined GROUPS are deleted at system reload. Job Groups to be kept on a more or less permanent basis should be created via commands entered in the System Startup command file, .SYSDATA.START.CMD. 2. JOB.CREATE does not allow the PAUSE.TRUE parameter to be passed. If the command is embedded in a program, all errors must be handled by the application. 3. BATCH jobs require an output file which is not automatically deleted. The user may need to delete these files on a regular basis to keep disk space available. 4. Quotes must be used around the user accounts when specifying more than one user account in the GROUP.CREATE and GROUP.MODIFY parameter lines. EXAMPLE: (GROUP.CREATE MYGROUP, TYPE=TERMINAL, PRIORITY=3, USERS="GROUP1.*, GROUP.*"). 5. RSC 511490 - If PRIORITY is not specified for TERMINAL and BATCH type jobs, the PRIORITY will default to 1. This default, although proper for BATCH type jobs, is normally too low for TERMINAL type jobs. It is recommended that a PRIORITY of 3 be specified for TERMINAL type jobs during GROUP. CREATE. (See example in item 4) 6. RSC 511491 - The PRIORITY of SYSTEM type jobs cannot be changed, even though GROUP.MODIFY appears to allow the user to do this. 7. RSC 511491 - SYSTEM type jobs cannot be deleted, nor can they be modified. GROUP.MODIFY appears to allow the user to modify SYSTEM tape jobs, but such modifications are not enforced. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB074 Pg011 1.9 FTF (File Tranfer Facility) If you plan to use MAI MAIL (Electronic Mail) or if you plan to start remote programs via FTF, you must ADD the name of the directory in which your remote programs resides to programs "FTF" and "FTFRTHINT". EXAMPLE: If your MAI OFFICE directory is "(TEST).OMS.", add it to statement 52 in program "FTF" and to statement 50 in program "FTFRTHINT". Add the underline portions shown below. LOAD ".NSPGM.FTF" 0052 P$=P8$+."NUPDATA.,.NUPPGM.,.NSPGM., 0052: (TEST).OMS." LOAD ".NSPGM.FTFRTHINT" 0050 P$=P8$+".NUPDATA.,.NUPPGM.,.NSPGM., 0050: (TEST).OMS." 1.10 SCSI (Small Computer System Interface) 1. SPR 523353 - SCSI retry : After a power failure, ECC for SCSI drives are not being reset (will log more soft errors in the errorlog, No ECC correction being done). WORKAROUND: Is to disable and enable the SCSI drives. If SCSI is a BOOT disk you must reboot the system. 1.11 MAGNET A USER level of 3 should be the only user to START/STOP MAGNET. If a USER of less than 3 START's MAGNET, you will get a "Insufficient Privileged" error when trying to access files via LAN/WAN. WORKAROUNDS: 1) Create a new account with the following characteristics: MAJOR ACCOUNT: MAGNET MINOR ACCOUNT: STARTUP PASSWORD: (anything) INITIAL COMMAND: MAGNET.STARTUP; RELEASE ABORT FLAG: T USER LEVEL: 3 FILE SEC OVERRIDE: T SYS OPR: T SPOOL OPR: T TAPE OPR: T DEFAULT PREFIX LIST: (anything) No other system operations can take place with this account as it would release after starting MAGNET. If MAGNET is already started when this is run, this would have no adverse effect. 2) Instead of shutting down MAGNET, just stop the media. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB074 Pg012 That is, in the MAGNET 'Network Status' menu, option 3 shuts down all of MAGNET but option 2 allows an operator to just shut down the LAN. This is just as effective as shutting down MAGNET to stop remote accessing but the MAGNET system tasks are not terminated so that when the media is restarted they all have their original characteristics. 1.12 Terminals 1. In order to use an industry standard printer as a slave off a DT-4313 terminal, the terminal must have REV E or above firmware. If the DT-4313 terminal does not have REV E firmware, only screen dumps can be printed. 2. As of release 9/8.6C, T0 must be a model 4309 or later terminal on all systems, or an HVDT on 7xxx/8xxx/9xxx systems. Terminal models 7250 and 7270 are no longer supported as T0. 1.13 ASYNCHRONOUS TRANSPORT PACKAGE (ATP) ATP 4.0 is the ATP release available for 9/8.6. ATP 4.0 provides new features such as autodial, scheduler, line turnaround, and performance enhancements. ATP 4.0 is NOT compatible with previous releases of ATP; all systems communicating with ATP 4.0 systems must also upgrade to 4.0. 1.14 HORIZONTAL SOFTWARE 1.14.1 The horizontal software packages of PRESENTATION SERVICES, GRAPH, and ORIGIN 2.0 and above typically have files that reside in the .SYS.node. If this is the case, these files need to be reinstalled in the SYS.node after an O.S. upgrade. This can be accomplished by one of the following methods: a) Retain a copy of the .SYS.node used by the older O.S. and, after the O.S. upgrade, copy the old .SYS. node to the new .SYS. node with DELETE EXISTING DESTINATION FILE = NO. b) For PRESENTAION SERVICES, run the PS.INSTALL program, which will copy all the necessary PS files to the .SYS. node. 1.14.2 For ORIGIN, copy the node .ORIGIN.R2xx.RT. to the new .SYS. node. If the users' prefixes include this ORIGIN runtime node, the ORIGIN files do not need to be in the .SYS. node. For GRAPH, copy the files .GRAF.GRAPH and .GRAF. GRAPHMAKER to the new .SYS. node. 1.14.3 MAGNET AND FILE TRANSFER FACILITY (FTF) 1. There is no automatic conversion of topology configuration files to the new Network Management Facility (NMF) configuration files when 9.6/8.6 is installed on an MPx system previously configured for B4NET/FTF (9.5 and earlier). The user is responsible for printing the previous configuration information SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB074 Pg013 before re-configuring the MAGNET and/or FTF network with NMF or EZCONFIG. 2. A reboot is necessary after the initial configuration of each system in the MAGNET/FTF network. Any subsequent modifications to the home station parameters or sub-network numbers also require a reboot to activate the changes. ORIGINATOR: Joe Melendez SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB074 Pg014 FIB 00075 10/27/89 *** Unexpected Error 12 Message in "COMM" on OS n.6G [ WPSF 560 ] *** It is possible to receive an error message "UNEXPECTED ERROR 12" when attempting to run the program "COMM". This error occurs at statement 5055 of that program when it does a CALL to ".NSPGM.CHKFTF". The .NSPGM. node contains files used with MAGNET and FTF but not Batch Communications. If the customer only uses Batch Communications, the .NSPGM. node is sometimes deleted from the disk to free up additional space. When this node is deleted, the error will occur. To correct this problem, add an ERR=5056 branch to statement 5055. 5055 CALL ".NSPGM.CHKFTF",ERR=5056,STAT; IF STAT=0 THEN A(3)=1 ELSE A(3)=0 .... This problem will be corrected on a later release. ORIGINATOR: Dale Jensen SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB075 Pg001 FIB 00076 10/27/89 *** Possible Data Loss using !RECONSTRUCT 8.5 & Higher [ WPSF 572 ] *** With BOSS/VS releases 8.5 and higher, using the RECONSTRUCT utility with certain parameters can cause data corruption in the future usage of a file. The potential problem is caused by entering a number greater than one in the field SECTORS/BTREE NODE in the RECONSTRUCT utility. Any file which has the number of sectors per btree node greater than one may have problems. To detect files which may this have a problem, a tool is available, called CHKBTREES, which will scan a given family and identify those files that could have this problem. The instructions to use CHKBTREES appears below: 1) At the "!" prompt, enter "CHKBTREES". An informational screen will appear. Press any character to continue or 'E' to exit the tool. 2) The prompt "ENTER OUTPUT FILENAME [='P*'] : " will appear. Any printer name or filename can be entered. If RETURN is entered without any other input, the P* will be chosen. The full output file name will be displayed. If a printer is chosen, then the spool file name will be displayed. 3) The next prompt "ENTER FAMILY NAME ['()',, or RETURN= '()']:" will appear. The name of the family (or the family portion of the filename to be searched) is entered here. Any family name can be entered. The entries '()' or RETURN will choose the system default family. 4) Next "ENTER STARTING NODE [RETURN=<.>]: " is displayed. There are three options that can be entered: A) Enter a "." or press RETURN. This will scan the entire family beginning at the first file and continuing until the last file. B) Enter a specific node (without the family name) to search. Only that node will be searched (i.e. .SYSDATA.). C) Enter a specific filename (with the family name) to check. Only that file will be checked (i.e. .SYSDATA.FILE). 5) The next prompt "ENTER IF THE UTILITY SHOULD PAUSE ON ERRORS ['Y'/(anything)]: " will appear. Any error that occurs while CHKBTREES is scanning the disk will be displayed. If this option is set to YES, then the utility will pause and require the user to press RETURN to continue the scan. If this option is answered NO, then when an error occurs, the error will be displayed but the user will not be required to press RETURN. The tool will continue automatically. All errors are also sent to the output device or file. 6) The utility will now scan the disk, node or file. The number of files found and the current file that it is working on will be displayed. 7) When the scan is complete, the prompt "CONTINUE ('N'/ANYTHING)" will appear. If you press "N" (or "n"), the tool will go back SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB076 Pg001 to step 3 and allow the user to enter more families or files to check. 8) The printout will contain the name of the file, its type (DIRECT or SORT) and the number of sectors per btree. To repair files that have this problem, use RECONSTRUCT with SECTORS/BTREE node equal to 1. To prevent users from possibly causing this problem, the RECON- STRUCT utility has been changed in 8/9/10.6G. The field "SECTORS/BTREE NODE" will be a display only field and will display the value "0". The user will not be allowed to change this value. The utility will use the value of one when rebuilding the file. To obtain the program "CHKTREES", please contact Field Product Support. This problem will be fixed in a future release. ORIGINATOR: Randy Case SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB076 Pg002 FIB 00077 11/22/89 *** MAGNET/FTF Completion code 1 on BOSS/VS n.6G [ WPSF 565 ] *** PROBLEM: A completion code of 1 is reported upon scheduling an FTF transfer that starts a remote program. Sending Electronic Mail via MAI Mail is an example of such an FTF transfer. CAUSE: The remote program cannot be started because it is not defined in the default FTF prefix list. There is a basic assumption that .OMS. resides in the same family disk as FTF. SOLUTION: The following modifications must be made to properly define the FTF prefix list on the receiving end. For MAI MAIL, the correct family name and directory in which the remote programs reside i.e. (family).OMS. must be included as follows: Add the underlined portions to the statements shown below. 1. LOAD ".NSPGM.FTF" 0052 P$=P8$+".NUPDATA.,.NUPPGM.,.NSPGM.,(family). 0052:OMS." SAVE 2. LOAD ".NSPGM.FTFRTHINT" 0050 P$=P8$+".NUPDATA.,.NUPPGM.,.NSPGM.,(family). 0050:OMS." SAVE ORIGINATOR: Frank Csete SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB077 Pg001 FIB 00078 11/22/89 *** Software Announcement 8/9/10.6G *** MAI Basic Four, Inc. is pleased to announce that the new system software revisions, 10.6G/9.6G/8.6G, are now available. The 9.6G revision is the recommended revision for MPx 9xxx Series Systems. The 8.6G revision is the recommended revision for MPx 7xxx and 8xxx Series Systems. The 10.6G revision is the recommended revision for Advanced Series Systems. There were no 9.6F/8.6F system software revisions. ****************************************************************** * * * o If this release is installed on MPx 9x00 system containing * * DMA-II controllers, then version -002 of the DMA-II * * boards must be used. If the system contains -001 boards, * * please contact your hardware support for local board * * replacement procedures. Please refer to the HARDWARE * * section #4. * * * * o As of release 9/8.6C, the .SYSDATA.SECURITY.DATA file is * * not transportable to previous release levels. Therefore, * * if you are upgrading to 10/9/8.6G from a release prior to * * 9/8.6C, this file should be saved before the upgrade, for * * fall-back purposes. * * * * o Files transferred from 10/9/8.6G to O.S. levels below * * 9/8.6A must be transported with EXTTAPE, MCSI, FTF, TBC, * * or ATP. If a downgrade is performed from 10/9/8.6G to a * * release prior to 9/8.6C, the user's files must be * * transported to the older O.S. level with one of the above * * utilities. * * * * o Horizontal software such as PRESENTATION SERVICES, GRAPH, * * and ORIGIN typically have files that reside in the .SYS. * * node. These files need to be transferred to the new .SYS. * * node on an O.S. upgrade, either by using the COPY utility * * or by reinstalling the software. * * * * o The 10/9/8.6G Software Announcement exists as a serial * * file on the official release tape. To print a copy, submit * * the following file to the printer: * * * * .R6Gxx.INST.DOC.ANNOUNCE6G * * * ****************************************************************** Copyright 1989, Rev. 1989, MAI Basic Four, Inc. All rights reserved. C O N T E N T S 1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . 1.1 ENHANCEMENTS IN THIS RELEASE . . . . . . . . . . . . . 1.2 CONFIGURATION RECORD CONSIDERATIONS . . . . . . . . . 1.3 SOFTWARE ANNOUNCEMENT. . . . . . . . . . . . . . . . . 2 FIXES IN THIS RELEASE. . . . . . . . . . . . . . . . . 2.1 SPOOLER. . . . . . . . . . . . . . . . . . . . . . . . 2.2 JOB MANAGER. . . . . . . . . . . . . . . . . . . . . . SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg001 2.3 TERMINALS. . . . . . . . . . . . . . . . . . . . . . . 2.4 FILESYSTEM . . . . . . . . . . . . . . . . . . . . . . 2.5 SAVERESTORE. . . . . . . . . . . . . . . . . . . . . . 2.6 CREATE UTILITY . . . . . . . . . . . . . . . . . . . . 2.7 BASIC. . . . . . . . . . . . . . . . . . . . . . . . . 2.8 GLOBAL SEARCH AND REPLACE. . . . . . . . . . . . . . . 2.9 BUSINESS BASIC CROSS REFERENCE (BBXREF). . . . . . . . 2.10 CONVERTSP. . . . . . . . . . . . . . . . . . . . . . . 2.11 BQR. . . . . . . . . . . . . . . . . . . . . . . . . . 2.12 TBC. . . . . . . . . . . . . . . . . . . . . . . . . . 3 BOSS/VS . . . . . . . . . . . . . . . . . . . . . . . 3.1 UTILITIES . . . . . . . . . . . . . . . . . . . . . . 3.1.1 ERRORLOG UTILITY ENHANCEMENTS . . . . . . . . . . . . 3.1.2 COPY UTILITY - TYPE II LOAD. . . . . . . . . . . . . . 3.2 AUDITOR'S LOGBOOK . . . . . . . . . . . . . . . . . . 3.3 MULTI-FAMILY BACKUP. . . . . . . . . . . . . . . . . . 3.4 CONFIGURATIONS . . . . . . . . . . . . . . . . . . . . 3.4.1 CONFIGURATIONS FOR MPx 7000/7100/8000 SERIES SYSTEMS . 3.4.2 CONFIGURATIONS FOR MPx 9000/9100/9400 SERIES SYSTEMS . 3.4.3 CONFIGURATIONS FOR MPx 9500/9600 SERIES SYSTEMS . . . 3.4.4 CONFIGURATIONS FOR THE ADVANCED SERIES FAMILY . . . . 3.5 FILE BUFFER FLUSH. . . . . . . . . . . . . . . . . . . 3.6 ALTERNATE FORCED DUMP ON ADVANCED SERIES SYSTEMS . . . 3.7 ELIMINATION OF DISK OFF-LINE MESSAGES. . . . . . . . . 3.8 COMMUNICATIONS - NEW FEATURES AND ENHANCEMENTS . . . . 3.8.1 MULTI-KEY FILE SUPPORT . . . . . . . . . . . . . . . . 3.8.2 MAGNET PERFORMANCE ENHANCEMENTS. . . . . . . . . . . . 3.8.3 FTF NETWORK QUALITY AND PERFORMANCE ENHANCEMENTS . . . 3.8.4 3270 BISYNC SUPPORT FOR DT-4313/DT4314 . . . . . . . . 3.8.5 TBC. . . . . . . . . . . . . . . . . . . . . . . . . . 3.8.5.1 BCOM MENU ENHANCEMENTS . . . . . . . . . . . . . . . . 3.8.5.2 BQR FILE LIST. . . . . . . . . . . . . . . . . . . . . 3.8.5.3 AUTO-SCHEDULER ACCEPTS INTERNATIONAL DATE. . . . . . . 3.8.6 ATP CONVERTS STRING FILES TO SERIAL FILES. . . . . . . 3.8.7 UPGRADING TBC. . . . . . . . . . . . . . . . . . . . . 3.8.8 UPGRADING MAGNET . . . . . . . . . . . . . . . . . . . 3.8.9 UPGRADING FTF. . . . . . . . . . . . . . . . . . . . . 3.9 DIAGNOSTICS. . . . . . . . . . . . . . . . . . . . . . 3.9.1 REMIDI . . . . . . . . . . . . . . . . . . . . . . . . 3.9.1.1 ON MPx 7000/7100 AND 8000 SERIES SYSTEMS . . . . . . . 3.9.1.1.1 UPDATING THE LOAD DIRECTORY FOR REMIDI . . . . . . . . 3.9.1.2 ON MPx 9xxx AND THE ADVANCED SERIES. . . . . . . . . . 3.9.1.2.1 UPDATING THE LOAD DIRECTORY FOR REMIDI . . . . . . . . 3.9.2 DEMON - UPDATING THE LOAD DIRECTORY. . . . . . . . . . 3.9.3 ADVANCED SERIES ONLY . . . . . . . . . . . . . . . . . 3.9.3.1 HIGH FREQUENCY MARGINS ON THE ADVANCED SERIES. . . . . 3.9.3.2 USING ALT LOAD FOR REMIDI AND DEMON. . . . . . . . . . 3.9.4 DIAGNOSTIC REMOVAL . . . . . . . . . . . . . . . . . . 3.10 BASIC. . . . . . . . . . . . . . . . . . . . . . . . . 4 HARDWARE . . . . . . . . . . . . . . . . . . . . . . . 4.1 MPX 7000, 7100, AND 8000 PCBA NOTES . . . . . . . . . 4.2 MPX 9XXX SERIES SYSTEM PCBA NOTES . . . . . . . . . . 4.3 PCBA'S FOR ALL MPX SERIES SYSTEMS . . . . . . . . . . 4.4 ADVANCED SERIES PCBA NOTES . . . . . . . . . . . . . . 4.4.1 PCBA's NOT SUPPORTED ON ADVANCED SERIES . . . . . . . 4.5 PERIPHERAL DEPENDENCIES . . . . . . . . . . . . . . . 4.5.1 TAPE DRIVES . . . . . . . . . . . . . . . . . . . . . 4.5.1.1 GCR TAPE DRIVE . . . . . . . . . . . . . . . . . . . . 4.5.1.2 SCSI MTCS TAPE DRIVE . . . . . . . . . . . . . . . . . 4.5.2 TERMINALS . . . . . . . . . . . . . . . . . . . . . . 4.5.3 DISK DRIVES . . . . . . . . . . . . . . . . . . . . . SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg002 5 INSTALLATION . . . . . . . . . . . . . . . . . . . . . 5.1 NEW FILE NAMING CONVENTION . . . . . . . . . . . . . . 5.1.1 FILE NAMES . . . . . . . . . . . . . . . . . . . . . . 5.2 GENERAL INFORMATION . . . . . . . . . . . . . . . . . 5.3 NEW OPERATING SYSTEM INSTALLATION . . . . . . . . . . 5.3.1 INSTALLING THE OPERATING SYSTEM . . . . . . . . . . . 5.3.1.1 LOADING SLOTS 0 AND 1 USING ALT LOAD . . . . . . . . . 5.3.1.2 TYPE 3 LOAD (Special Functions) . . . . . . . . . . . 5.3.1.2.1 OPTION 1 (CHANGE VOLUME LABEL INFORMATION) . . . . . . 5.3.1.2.2 OPTION 2 (UPDATE FAMILY INFORMATION) . . . . . . . . . 5.3.1.2.3 OPTION 3 (INITIALIZE FAMILY DIRECTORY) . . . . . . . . 5.3.1.2.4 OPTION 4 (CHANGE INSTALLATION PARAMETERS) . . . . . . 5.3.1.3 RESTORING THE O.S. . . . . . . . . . . . . . . . . . . 5.3.2 INSTALLING THE CONFIGURATION RECORD . . . . . . . . . 5.4 UPGRADING TO 8.6E FROM RELEASE LEVELS 8.4D AND BELOW . 5.4.1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . 5.4.2 PRELIMINARY EVALUATION . . . . . . . . . . . . . . . . 5.4.2.1 HARDWARE EVALUATION . . . . . . . . . . . . . . . . . 5.4.2.2 FILE PREPARATION . . . . . . . . . . . . . . . . . . . 5.4.2.3 NEW FILE SYSTEM SPACE REQUIREMENTS . . . . . . . . . . 5.4.2.4 SAVING FILES TO TAPE . . . . . . . . . . . . . . . . . 5.4.3 OPERATING SYSTEM UPDATE AND FILE CONVERSION . . . . . 5.4.3.1 INSTALLING THE O.S. . . . . . . . . . . . . . . . . . 5.4.3.1.1 LOADING SLOTS 0 AND 1 USING ALT LOAD . . . . . . . . . 5.4.3.1.2 TYPE 3 LOAD (SPECIAL FUNCTIONS) . . . . . . . . . . . 5.4.3.1.2.1 OPTION 1 (CHANGE VOLUME LABEL INFORMATION) . . . . . . 5.4.3.1.2.2 OPTION 2 (UPDATE FAMILY INFORMATION) . . . . . . . . . 5.4.3.1.2.3 OPTION 3 (INITIALIZE FAMILY DIRECTORY) . . . . . . . . 5.4.3.1.2.4 OPTION 4 (CHANGE INSTALLATION PARAMETERS) . . . . . . 5.4.3.1.3 RESTORING THE O.S. . . . . . . . . . . . . . . . . . . 5.4.3.2 INSTALLING THE CONFIGURATION RECORD . . . . . . . . . 5.4.3.3 CONVERTING FILES . . . . . . . . . . . . . . . . . . . 5.4.3.3.1 TAPE TO DISK CONVERSION . . . . . . . . . . . . . . . 5.4.3.3.2 DISK TO DISK CONVERSION . . . . . . . . . . . . . . . 5.4.3.3.3 CHECK FILES . . . . . . . . . . . . . . . . . . . . . 5.4.4 UPDATING THE TERMINAL CONFIGURATION FILE . . . . . . . 5.5 UPGRADING TO 8.6E FROM RELEASE LEVELS 8.4E AND ABOVE . 5.5.1 SAVING FILES TO TAPE . . . . . . . . . . . . . . . . . 5.5.2 OPERATING SYSTEM UPDATE . . . . . . . . . . . . . . . 5.5.2.1 LOADING SLOTS 0 AND 1 USING ALT LOAD . . . . . . . . . 5.5.2.2 CHANGING INSTALLATION PARAMETERS . . . . . . . . . . . 5.5.2.3 RESTORING THE O.S. . . . . . . . . . . . . . . . . . . 5.5.3 INSTALLING THE CONFIGURATION RECORD . . . . . . . . . 5.5.4 UPDATING SLOTS 2 AND 3 ON 7xxx AND 8xxx SYSTEMS . . . 5.5.4.1 UPDATING WCS SLOT TWO (2) . . . . . . . . . . . . . . 5.5.4.2 UPDATING SLOT THREE (3) . . . . . . . . . . . . . . . 5.5.4.2.1 UPDATING WCS SLOT THREE (3) . . . . . . . . . . . . . 5.5.4.2.1.1 ON 7000/7100 SYSTEMS AND 8000 SYSTEMS WITH LAN . . . . 5.5.4.2.1.2 ON 8000 SYSTEMS WITHOUT LAN . . . . . . . . . . . . . 5.5.4.2.2 UPDATING O.S. SLOT THREE (3) . . . . . . . . . . . . . 5.5.5 SLOT INFORMATION . . . . . . . . . . . . . . . . . . . 5.6 UPGRADING TO 9.6E . . . . . . . . . . . . . . . . . . 5.6.1 SPECIAL CONSIDERATIONS . . . . . . . . . . . . . . . . 5.6.2 PRINTING OUT THE TERMINAL CONFIGURATION INFORMATION. . 5.6.3 SAVING FILES TO TAPE . . . . . . . . . . . . . . . . . 5.6.4 OPERATING SYSTEM UPDATE . . . . . . . . . . . . . . . 5.6.4.1 LOADING SLOTS 0 AND 1 USING ALT LOAD . . . . . . . . . 5.6.4.2 CHANGING INSTALLATION PARAMETERS . . . . . . . . . . . 5.6.4.3 RESTORING THE O.S. FILES . . . . . . . . . . . . . . . 5.6.5 INSTALLING THE CONFIGURATION RECORD . . . . . . . . . 5.6.6 UPDATING SLOTS 2 AND 3 ON MPx 9xxx SERIES SYSTEMS. . . SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg003 5.6.6.1 UPDATING WCS SLOT TWO (2) . . . . . . . . . . . . . . 5.6.6.2 UPDATING WCS SLOT THREE (3) . . . . . . . . . . . . . 5.6.6.3 UPDATING O.S. SLOT THREE (3) . . . . . . . . . . . . . 5.6.7 SLOT INFORMATION . . . . . . . . . . . . . . . . . . . 5.7 UPGRADING TO 10.6E AND THE ADVANCED SERIES . . . . . . 5.7.1 SPECIAL CONSIDERATIONS . . . . . . . . . . . . . . . . 5.7.2 SAVING FILES TO TAPE . . . . . . . . . . . . . . . . . 5.7.3 OPERATING SYSTEM UPDATE . . . . . . . . . . . . . . . 5.7.3.1 LOADING SLOTS 0 AND 1 USING ALT LOAD . . . . . . . . . 5.7.3.2 CHANGING INSTALLATION PARAMETERS . . . . . . . . . . . 5.7.3.3 RESTORING THE O.S. FILES . . . . . . . . . . . . . . . 5.7.4 INSTALLING THE CONFIGURATION RECORD . . . . . . . . . 5.7.5 UPDATING SLOTS 2 AND 3 ON ADVANCED SERIES SYSTEMS. . . 5.7.5.1 UPDATING WCS SLOT TWO (2) . . . . . . . . . . . . . . 5.7.5.2 UPDATING WCS SLOT THREE (3) . . . . . . . . . . . . . 5.7.5.3 UPDATING O.S. SLOT THREE (3) . . . . . . . . . . . . . 5.7.6 SLOT INFORMATION . . . . . . . . . . . . . . . . . . . 5.8 UPDATING SLOTS 0 AND 1 USING UPDATE.OS AND UPDATE.WCS. 5.8.1 UPDATING O.S. SLOTS 0 AND 1 . . . . . . . . . . . . . 5.8.2 UPDATING WCS SLOTS 0 AND 1 . . . . . . . . . . . . . . 5.9 SYSTEM STARTUP . . . . . . . . . . . . . . . . . . . . 5.9.1 STANDARD STARTUP COMMAND FILE . . . . . . . . . . . . 5.9.1.1 COMMAND FILE DEFINITIONS . . . . . . . . . . . . . . . 5.9.2 IMPLICATIONS . . . . . . . . . . . . . . . . . . . . . 5.10 DE-INSTALLING DIAGNOSTICS. . . . . . . . . . . . . . . 6 RELATED DOCUMENTATION . . . . . . . . . . . . . . . . 1. INTRODUCTION 1. ENHANCEMENTS IN THIS RELEASE The 10.6G/9.6G/8.6G release contains the following enhancements: o COPY utility now in a TYPE - II load. Allows offline mode of copying files. o File buffer flush - The feature forces the file buffers to the disk in the event of a system dump. Reduces the number of files lacking integrity after a dump. o New features for Auditor's log book including automatic log file switch, selectable family name for log files, and improved SAVERESTORE and COPY support. o Alternate force dump method when diagnostic dumps won't occur on the Advanced System. o Logging of incomplete dumps and disk offline errors to the ERRORLOG. o Support for Multi-key files in communications: MAGNET, MCSI, ATP, and Batch communications. o MAGNET performance enhancements. o Support for the 250Mb and M364Mb SCSI disk drive for 9xxx and Advanced Series machines. 1.2. CONFIGURATION RECORD CONSIDERATIONS In general, a new configuration record is required when upgrading to a new system type (e.g., from an 8xxx to a 9xxx system), when SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg004 adding new hardware, or when upgrading to a new major release level (e.g., 8.5 to 8.6). A new configuration record is not required when upgrading from releases 9.6A/B/C/E to 9.6G or from releases 8.6A/B/C/E to 8.6G. A new configuration record is required, however, when upgrading to 10.6G. A new configuration record is also required when upgrading from 8.4 and 9.5/8.5 releases to 10.6G/9.6G/8.6G releases. 1.3. SOFTWARE ANNOUNCEMENT The 10.6G/9.6G/8.6G Software Announcement exists as a serial file on the official 10/9/8.6G O.S. release tape, which allows the user to print copies, if needed. To print this document, SUBMIT the following file to the printer: (family).R6Gxx.INST.DOC.ANNOUNCE6G 2 FIXES IN THIS RELEASE 2.1 SPOOLER 1) Using a printer number greater than 99 in some printer utilities caused a system dump of 2,10,33,11 - 1,146,0,11 2) Eight-bit now works correctly when using 'SL' and 'EL' when using a PT-4214 printer. 3) A print job that was stopped on the second copy would not restart properly. The job can now be restarted. 4) When spools jobs were cancelled, the spool files were not being deleted. Spool files are now deleted. 5) The PT-4213/PT-4217/PT-4218 drivers have been enhanced to allow 512 characters per line. 2.2 JOB MANAGER 1) If account exists in the SECURITY file, previous releases wouldn't allow the account to be LIMITed by the Job Manager until the account was first logged onto. 2) GROUP.LOGCOPY with QUIET=T will not position the cursor, allowing the utility to be called from a ghost. 2.3 TERMINALS 1) Closing a terminal port from inside a batch process will not produce an error 0. 2.4 FILESYSTEM 1) Fixed a problem with receiving ERR 15's "Resource Error" when writing to very large Multi-key files. 2) Removing a record for a Multi-key file without locking the record or specifying the KEY= option would cause a system dump 2,10,38,25 - 1,139,0,25. It now returns an error. 3) A concurrency problem with Multi-key files that caused a dump 8,240,1,44. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg005 4) Using INITFILE utility on a file and then using RECONSTRUCT on the same file used to produce a dump 8,240,1,44. 5) Opening and closing a file multiple times with Audit logging on caused a system dump 7,5,1,20 - 35,0,0,2. 6) Fixed a problem with conversion of data files from *.6C to *.6E. DKA would display an error "USAGE RIGHTS OVERLAPPING WITH FORMAT STRING". This has been fixed in *.6G. Also DKA is been enhanced to fix these errors. 2.5 SAVERESTORE 1) If the verify option is on and MB-III is pressed to skip a file that spans 2 tapes, SAVERESTORE used to return the error message "SECTOR COUNT MISMATCH". The file is now properly skipped. 2) In a type II load, SAVERESTORE would dump the system (2,10,33, 11 - 1,146,0,11) during a save operation where the output device was a printer that was offline. 3) Restoring programs from the old filesystem (pre-*.4E) would cause the programs to be corrupted although no error message was given on the restore operation. 4) Restoring data files from the old filesystem (pre-*.4E) would cause an error message "ERROR WHILE CALLING CONV85:I'M TOO OLD FOR THIS FILESYSTEM". In actuality the files would convert normally. 2.6 CREATE UTILITY 1) When calling the CREATE utility with initial records equal to max records, you no longer have to specify the ADDGROWTH=0. 2.7 BASIC 1) An END before an ENDIF was ignored on previous versions. Now "IF xxx THEN zzz;END ENDIF ;vvvvv" will now end properly when the condition is true. 2) When using INITFILE from BASIC on a file that had audit logging turned on would delete the source file. This has been fixed. 2.8 GLOBAL SEARCH AND REPLACE 1) When suppressing the output of GSR, the utility would display the search data as it found it. Now it will not display the output when quiet mode is in effect. 2.9 BUSINESS BASIC CROSS REFERENCE (BBXREF) 1) When cross-referencing multiple programs, and the reserved word option was used, the reserved word "SETFIELD" would appear even though it was not used in the program. This has been fixed. 2.10 CONVERTSP 1) When specifying .NODE.& as your source node and .NODE1.& as your destination node, the files in the destination node will SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg006 be missing the first character (i.e. .NODE.FILE1 will be .NODE1.ILE1). This has been fixed in this release. 2.11 BQR 1) BQR will now properly handle special character file names less than 6 characters. Previous releases returned ERROR 10 and ERROR 14. 2.12 TBC 1) You are now able to run TBC in a ghost when autoprompt has set transmit priority to secondary. 2) Serial files, with record lengths greater than 132 characters, will not split up when transmitted using 3780 text mode. 3. BOSS/VS 3.1. UTILITIES 1.1. ERRORLOG UTILITY ENHANCEMENTS The error log utility has been enhanced such that dumps will be logged to the error log file prior to beginning the dump. This will log the dump regardless of whether or not the dump completes. 1.2. COPY UTILITY - TYPE II LOAD The COPY utility is now available in a standalone TYPE II load. Upon entering a TYPE II load, the following screen will appear: 1. SAVERESTORE UTILITY 2. DISK FILES UTILITY 3. DISKANALYZER UTILITY Choosing option 2 will display the file functions menu: 1. DELETE FILES 2. RENAME FILES 3. LIST FILES 4. COPY FILES Choose option #4 to access the copy utility. The COPY screen will appear: CURRENT FAMILY : (display field only) SOURCE FILE SPECIFIER : DESTINATION FILE SPECIFIER : OUTPUT DEVICE (CR=VDT) : VERIFY (N/CR=Y) : DELEXIST (Y/CR=N) : ENTRIES CORRECT (Y/N) : SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg007 Each of the prompts are answered as they would be for the TYPE I COPY utility. Note however, the following differences between the TYPE I COPY and the TYPE II COPY: 1) The following fields from the TYPE I COPY are not implemented: START and END SPECIFIER DELETE SOURCE IF COPY SUCCESSFUL FROM DATE and FROM TIME NEW USAGE RIGHTS PAUSE ON ERRORS 2) The TYPE II COPY utility will not allow masking in the filename. This is similar to all other file functions in the TYPE II load. 3.2. AUDITOR'S LOGBOOK There have been three enhancements to the Auditor's log book in this release: 1) Automatic Switch When the primary log file becomes full, the OS will perform an automatic switch to the backup log file. The user no longer needs to perform a manual file switch operation. However, if the backup log file is not empty when the switch is attempted, the switch will not occur and an error will be returned to the application. 2) Selectable log family Users can determine which disk family is used to hold the log files. Both log files (primary and backup) must reside on the same family, but that family can be different from that of the source. When using the CREATE or UPDATE utility to turn on audit logging, an additional prompt will appear: AUDIT FAMILY NAME: Enter the name of the family where the audit files will reside. Note that the prefix of the logfiles will the same as the source file. For example, if the source file is named (DISK).APPL.FILE and you specify the log family as MYDISK, then the log files will be named (MYDISK).APPL.FILE.AUD and (MYDISK).APPL.FILE.AUDBAK. 3) Improved SAVERESTORE and COPY support It is now possible to move sets of files (a data file plus its log files) from one node to another or from one family to another with the SAVERESTORE and COPY utilities without losing the ability to access the data file. NOTE: When installing Auditor's logbook for the first time, the key file must be copied from .R6Gxx.INST.ETC.LEVEL.ALB to ().ETC.LEVEL.ALB. 3.3 MULTI-FAMILY BACKUP NOTE: Multi-Family back-up is only supported for future tape products. Single Family back-up is supported for current and future tape products. As of this release, the TYPE III DISK TO TAPE FAMILY BACKUP utility will support multiple family backup and restore. More SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg008 than one family can be specified for the save operation and the restore operation will allow the user to select one or more families to be restored to disk. This is all done without user intervention once the operation begins. Choosing option #1 "SAVE FAMILY TO TAPE" will allow you to save one or more families to tape. At the prompt "DISK FAMILY TO BE SAVED?", the user can enter one or more family names (to a maximum of 16 families). Once all the prompts are answered, the backup will begin. The utility will save the first family to tape, then the second family, and so on until all families specified have been saved. The utility will prompt the user for tapes as needed. If a fatal tape error occurs and if the user aborts the copy due to an error, an attempt will be made to terminate the save operation at the end of the last good family backup or beginning of the tape. When more than one family has been saved successfully prior to the tape/disk error, the utility will set the logical end of tape at the end of the last good family backup. When option #2 "RESTORE FAMILY FROM TAPE", the user will be allowed to restore multiple families from tape. At the prompt "DISK FAMILY TO BE RESTORED?", the user may enter up to 16 families to be restored. The family names may be entered in any order and do not have to match the order in which they are saved. The families will be restored in the order in which they will appear on the tape. The restore will require all tapes to be processed in a sequential order starting with the first tape. When performing a multi-family restore operation, if the current family being restored cannot be done due to incompatible file space area, then an attempt will be made to restore the next family. At the end of a save or restore session, a summary screen will be displayed to inform the user of the results. The screen will be as follows: TAPE BACKUP STATUS DISPLAY FAMNAME OPERATION STATUS ERROR xxxxxxxx xxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxx xxxxxxxx xxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxx . . . . . . . . The OPERATION field may have the values "SAVE" or "RESTORE" depending on the operation being done. The STATUS field will contain the status of the operation and can have the possible values: o FILE SYSTEM SIZE ERROR - Indicates that the restore operation tried to restore to a family whose file system area is incompatible. o NO BACKUP OPERATION - The backup operation did not occur for this family. This can be caused by specifying a family to restore that doesn't exist on tape. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg009 o TAPE ERROR - A fatal tape error has occurred and the tape backup couldn't continue. o DISK FAILURE - A Hardware disk error has occured and the tape backup did not complete successfully. o DONE - The operation completed successfully for this family. The ERROR field, if the message "TAPE ERROR" appears, may display an error 4-tuple (xx,xx,xx,xx). If the status field displayed "DISK FAILURE", the last hardware status would be displayed in this field. If the image back was successful, the ERROR field will display "NONE" 3.4. CONFIGURATIONS NOTE 1: The number of "High Activity Tasks" is approximate and largely dependent on the application. The relative relationship of the numbers between configurations is more important than the actual numbers themselves. NOTE 2: System configurations of MPx 9xxx Series Systems are based on the use of the LS-700 power supply mainframes. Original 810 systems do not support the LS-700 power supply and, therefore, will not meet all defined maximum configurations listed. NOTE 3: The following configurations are based on performance testing, and are subject to change as newer performance testing data becomes available. The configurations listed in the marketing announcements override those listed here. 4.1. CONFIGURATIONS FOR MPx 7000/7100/8000 SERIES SYSTEMS The maximum configuration for MPx 7000, 7100, and 8000 Series Systems, models 7030, 7130, and 8030, is as follows: 116 Devices - A combination of 8-ways, 16-ways, the 4 ports on the MCS PCBA, MDTs and HVDTs up to a total of 116 devices are supported. 3 CPU sets 10 ISDCs: 16-ways (7 maximum) and/or 8-ways 32 Ghost tasks 24 High speed videos (HVDT) 8 Disk drives 4 Parallel printers 2-8 Megabytes of memory (6 Mb maximum on 7000/7100 systems) 2 Magnetic tape drives - MTR, MTS, and/or GCR (2 Maximum), and/or MCS (1 maximum) 4 Intelligent Multi-Line Controllers (IMLC) 8 DataWord II terminals 4 TBC lines 64 3270 terminals 8 X.25 lines 2 Auto-Call Units (ACU) 99 Serial printers 99 System printers (total serial and parallel not to exceed 99) 2 Buffered Magnetic Tape Controllers 27 High activity concurrent tasks 1 LAN controller SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg010 NOTE: There is a maximum of 9 memory assembly boards in any combination of 1/2 Mb, 1 Mb, 2 Mb, 4 Mb and BMTCs (a maximum of 3 boards per chassis). Models 7010/7110/8010 and 7020/7120/8020 have the same configuration limits as models 7030 and 8030 above, with the following limitations: 7010/7110/8010 7020/7120/8020 1 CPU set 2 CPU sets 2-4 Mb memory 2-6 Mb memory 20 Devices 52 Devices 12 Concurrent tasks 20 Concurrent tasks (high activity) (high activity) 19 System printers 51 System printers 3.4.2. CONFIGURATIONS FOR MPx 9000/9100/9400 SERIES SYSTEMS The maximum configuration for MPx 9000, 9100, and 9400 Series Systems, models 9020, 9120, and 9420 is as follows: 116 Devices - A combination of 8-ways, 16-ways, the 4 ports on the MCS PCBA, MDTs and HVDTs up to a total of 116 devices are supported. 2 CPU sets with Evaluation Stack and Rstack Cache 10 ISDCs: 16-ways (6 maximum) and/or 8-ways (10 maximum) 32 Ghost tasks 24 High speed videos (HVDT) 12 Disk drives on models 9020 and 9120, 8 disk drives on model 9420 (2.4 GB maximum), with no more than 8 14-inch fixed drives on any of the 3 models 8 Parallel printers 4-12 Megabytes of memory 2 Magnetic tape drives - MTR, MTS, and/or GCR (2 maximum), and/or MCS (1 maximum) 4 Intelligent Multi-Line Controllers (IMLC) 8 8 DataWord II terminals 4 TBC lines 64 3270 terminals 8 X.25 lines 2 Auto-Call Units (ACU) 99 Serial printers 99 System printers (total serial and parallel not to exceed 99) 4 DMA-I controllers on models 9020 and 9120, and 4 (total) DMA-I/DMA-II controllers on model 9420 * 2 Buffered Magnetic Tape Controllers 42 High activity concurrent tasks 1 LAN controller * It is recommended that, for maximum performance, no more than two disks be configured per DMA-II, and that the number of DMA-II's equal or exceed the number of CPU's. Models 9010, 9110, and 9410 have the same configuration limits as the 9020, 9120, and 9420 above, with the following exceptions: 1 CPU set with Evaluation Stack and Rstack Cache 68 Devices 10 ISDCs: 16-ways (4 maximum) and/or 8-ways (8 maximum) 67 Serial printers SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg011 75 System printers (total serial and parallel not to exceed 75) 27 High activity concurrent tasks .4.3. CONFIGURATIONS FOR MPx 9500/9600 SERIES SYSTEMS The maximum configuration for MPx 9500 and 9600 Series Systems, models 9530 and 9630, is the same as the maximum configuration for the MPx 9000, 9100 and 9400 Series Systems, models 9020, 9120, and 9420 with the following exceptions: 3 CPU sets with Evaluation Stack Rstack Cache Code Cache Data Cache 255 Devices 16 ISDCs: 16-ways (16 maximum) and/or 8-ways (16 maximum) 4-24 Maximum megabytes of main memory (see Hardware section for mandatory revision levels for main memory support above 12 megabytes) 16 Disk drives on model 9530, 12 disk drives on model 9630 (3.6 GB maximum), with no more than 8 14-inch fixed drives on either model 4 DMA-I controllers (may also include DMA-II controllers if system is an upgrade from a 9400) 73 High activity concurrent tasks Models 9510/9520 and 9610/9620 have the same configuration limits as models 9530/9630 with the following exceptions: 9510/9610 9520/9620 1 CPU set 2 CPU sets (same caches as the 9530) (same caches as the 9530) 10 ISDCs: 16-way (4 maximum) 10 ISDCs: 16-way (6 maximum) 8-way (8 maximum) 8-way (10 maximum) 84 Devices 132 Devices 83 Serial printers 53 Concurrent tasks 91 System printers (high activity) (total serial and parallel) 32 Concurrent tasks (high activity) 3.4.4. CONFIGURATIONS FOR THE ADVANCED SERIES FAMILY The maximum number of high activity concurrent tasks is 146 on the Advanced Series Model 63 and 84 on the ADVANCED SERIES Model 42. The maximum configuration for ADVANCED SERIES model 63 is as follows: 255 Devices - A combination of 8-ways, 16-ways, and the 4 ports on the MCS/M PCBA, and MDT's up to a total of 255 devices are supported. 3 CPU's (with cache boards) 16 ISDCs: 16-ways (16 maximum) and/or 8-ways (16 maximum) 4-24 Maximum megabytes of main memory (See Hardware section for mandatory revision levels for main memory support above 12 megabytes.) 16 Disk drives (may be 300Mb and 621Mb fixed disks, and 285 removables up to 9.9GB maximum) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg012 4 DMA controllers (may be DMA-I disk controllers for support of 285Mb removable disks and/or DMA-III disk and parallel printer controllers for support of 300Mb and 621Mb fixed disks and parallel printers) * 32 Ghost tasks 8 Parallel printers 2 Magnetic tape drives - MTR, MTS, and/or GCR (2 maximum), and/or MCS (1 maximum) 4 Intelligent Multi-Line Controllers (IMLC) 8 DataWord II terminals 4 TBC lines 64 3270 terminals 8 X.25 lines 2 Auto-Call Units (ACU) 99 Serial printers 99 System printers (total serial and parallel not to exceed 99) 2 Buffered Magnetic Tape Controllers 1 LAN controller The maximum configuration for ADVANCED SERIES model 62 is the same as for model 63, with the following exceptions: 196 Devices 2 CPU's (with cache boards) 4-20 maximum megabytes of main memory The maximum configuration for ADVANCED SERIES model 61 is the same as for model 63, with the following exceptions: 148 Devices 1 CPU (with cache board) 4-16 maximum megabytes of main memory The maximum configuration for ADVANCED SERIES model 42 is the same as for model 63, with the following exceptions: 132 Devices 2 CPU's (without cache) 4-16 maximum megabytes of main memory The maximum configuration for ADVANCED SERIES model 41 is the same as for model 63, with the following exceptions: 100 Devices 1 CPU (without cache) 4-12 maximum megabytes of main memory * For maximum performance, it is recommended that no more than 2 disks be configured per DMA. 3.5 FILE BUFFER FLUSH This new feature has been added to reduce file recovery time by minimizing the number of files that need reconstruction after a fatal dump. When a fatal dump (not diagnostic or power failure) occurs, the system will attempt to write all buffered data in memory to their respective files on the disk. If the data is written successfully, files will no longer lack integrity and will not require reconstruction. Under certain circumstances, the buffers may not be successfully SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg013 written to disk because of some other failure (for example DMA failure). If not, then files may need to be reconstructed upon reboot. When a fatal dump occurs, the dump will begin to the dump area on the disk. After main memory and shared memory controllers have been dumped to disk, a message will appear stating the file buffer flush is in progress: SYSTEM DUMP: FILE BUFFERS BEING FORCED TO DISK FOR FAMILY: xxxxxxxx Each family name will be displayed as its buffers are flushed to disk. If the buffer flush is successful, then the following message will appear: SYSTEM DUMP nn,nn,nn,nn FBF COMPLETE: PLEASE RELOAD 00000003 The system may now be reloaded. You MUST still follow standard dump recovery procedures for finding and repairing corrupt files. 3.6. ALTERNATE FORCED DUMP ON ADVANCED SYSTEMS When a diagnostic dump cannot be forced through the sense switches, a low level diagnostic dump can be forced. The alternate dump is invoked by using the sense switches in the following manner: 1. All switches "off" 2. Switch zero (leftmost) "on" <== Begin normal diagnostic dump, if diagnostic dump 3. Switch zero "off" 4. Switch one "on" 5. Switch one "off" 6. Switch zero "on" <== Begin alternate dump In some situations, it may be required to enter this sequence twice. So, if an alternate dump is required enter the above sequence once, if system doesn't dump, then enter the sequence again. NOTE: This alternate dump should only be done when a normal diagnostic dump cannot be done. An alternate dump is always fatal dump is done, the system may not recover and may require re-booting. 3.7. ELIMINATION OF DISK OFFLINE MESSAGES Under certain infrequent circumstances, momentary "offline" messages would flash on the screen. In many cases, the reason cannot be determined since no error log entry would be made. This release adds two things: 1) Eliminates the disk offline messages where the condition is momentary and not because of a drive malfunction. 2) Any offline condition that needs to be reported will be recorded in the error log. 3.8 COMMUNICATIONS - NEW FEATURES AND ENHANCEMENTS 1. Multi-Key file support over MAGNET, FTF, ATP, TBC and MCSI 2. MAGNET Performance Enhancements 3. FTF Network Quality and Performance Enhancements SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg014 4. 3270 Bisync support for DT-4313/DT-4314 5. TBC Enhancements 6. ATP converts string files to serial files .8.1 MULTI-KEY FILE SUPPORT The inter-system transport of Multi-key files is now allowed over MAGNET, FTF, ATP, TBC and MCSI between MPx and Advanced Series systems, and over FTF, ATP, TBC and MCSI between MPx/Advanced Series systems and 2000/2500/3000/4000 systems. Dependencies: To transport Multi-keyed files, both the sending and receiving systems must be on M.6G or above for MPx and Advanced Series systems, and on 7.5B or above for 2000/2500/3000/4000 systems. NOTE - B4NET/FTF does NOT support Multi-key transport, you must use MAGNET/FTF. .8.2 MAGNET PERFORMANCE ENHANCEMENTS MAGNET's transfer rate has been increased over both LAN and WAN by reducing system overhead through CPU reduction and buffer usage, and by reducing process dispatching, reducing communications traffic, and by reducing traffic to the IMLC. These performance enhancements should reduce the frequency of timeouts on busy networks. Dependencies: To take advantage of these enhancements, both the receiving and sending systems must be on M.6G or higher. Backwards Compatibility: To transport NON-Multi-key files (Direct, Sort, Serial, Index), the minimum OS level for the other system is *.6E for MPx and Advanced Series systems. .8.3 FTF NETWORK QUALITY AND PERFORMANCE ENHANCEMENTS There are now two versions of FTF on *.6G - MAGNET/FTF and B4NET/FTF. MAGNET/FTF contains the new enhancements, B4NET/FTF uses the same protocol as in M.6E. Here's an overview of the MAGNET/FTF enhancements: o Multi-key Support between other *.6G and 7.5B systems. o Record Blocking - sends data in 482 byte datagrams instead of by record. (B4NET uses 4 bytes per record overhead.) o Inter-family text translation - will automatically translate text when going between *.6G and 7.4B systems. o Trailing Null suppression - reduces transfer overhead. o Automatic MAGNET/FTF startup - You no longer have to start B4NET if all systems in your network are using MAGNET/FTF. A MAGNET server is started and release for each file transfer. A new program has been added to FTF, "().NSPGM.B4MAINT", so that you can specify which systems in your network are using MAGNET/FTF and which are using B4NET/FTF. (Please see section SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg015 3.6.3 UPGRADING FTF for more information on this program.) Dependencies: To take advantage of these enhancements, both the sending and receiving systems must be using MAGNET/FTF. This means that both systems must be on *.6G for MPx and Advanced Series systems and on 7.5B for 2000/2500/3000/4000 systems. Backwards Compatibility: FTF on *.6G can communicate with MPx and Advanced Series systems on *.6E or above, and with 2000/2500/3000/4000 systems on 7.4A or above, and with 1800 systems on 7.2R, and with 13xx systems on 4.5B. .8.4 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. .8.5 TBC Here is a list of the new features and enhancements that have been made to TBC for this release: o Multi-key file support o Auto-Dial utility now functions like the BOSS/IX utility o Printer mnemonics support o Serial files are no longer truncated at 131 characters o BCOM Menu enhancements o BQR file list no longer terminates on last file o Auto-scheduler now accepts international dates Multi-keyed File Support Please see 3.6.1 Multi-Keyed File Support for information on this new feature. Auto-Dial Utility The auto-dial utility has been changed to function and look like the BOSS/IX auto-dial utility. Please refer to the BOSS/IX Transportable Batch Communications (27xx/37xx) User Guide, M6353, for information on this utility. Printer Mnemonics Support Printer mnemonics are now supported when transmitting serial files. To enable this feature, you must enter a SERIAL file name in your TRANSMIT queue and using the transfer type TEXT. The following prompt will then display: SPECIFY TYPE OF SERIAL FILE: (CR=STANDARD FILE S=STANDARD P=TRANSLATION OF MBF PRINT FILE MB-IV=EXIT) Enter a 'P' to specify TRANSLATION OF MBF PRINT FILE. Serial Files are No Longer Truncated at 131 Characters SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg016 Serial files are now sent in records sizes up to the maximum block size of the protocol you're using. Records larger than than maximum block size will be wrapped to the next record. NOTE - If the serial files are transmitted using the TRANSLATION OF MBF PRINT FILE option, the records will be truncated at 131 characters. .8.5.1 BCOM MENU ENHANCEMENTS The BCOM entry screen has been made easier to use by giving the user more descriptive displays and options that allow the user to move between the prompts and select debugging features. Here is a sample entry screen and a description of its options. ___________________________________________________________________ ENTER AUTO-PROMPT NAME: =DEFAULT MB-I=DISPLAY MB-IV=EXIT) CR = will use your default auto-prompt. MB-I = will display your saved auto-prompts MB-IV = will exit you from the BCOM utility. __________________________________________________________________ ENTER TASK TO BE USED FOR COMMUNICATIONS: CR = will use your terminal to execute the session. G* = will use your specified ghost. MB-II or MB-III = will display the addition options below MB-IV = will exit you from the BCOM utility. __________________________________________________________________ ENTER TASK TO BE USED FOR COMMUNICATIONS: * (MB-I=BEGINNING MB-II=DISPLAY PGM MB-III=ENABLE ESCAPE MB-IV=ENABLE DEBUG) MB-I = will return you to ENTER AUTO-PROMPT NAME: MB-II = will display the TBC program name in the upper left hand corner of the screen during a session. MB-III = will also display the TBC program name but, will also enable you to escape during a session MB-IV = will function the same as MB-III. NOTE 1 - Using the de-bug options (MB-II, MB-III, MB-IV) will slow down the performance of BCOM. Use them only when needed. NOTE 2 - DO NOT 'END' if you escape in a BCOM program. You must enter 'RUN' and exit the program and BCOM normally. ________________________________________________________________ DO YOU DESIRE OPERATOR INTERVENTION? (CR=NO Y=INTERVENTION MB-I=PREVIOUS PROMPT MB-IV=EXIT) CR = will start communications. Y = will bring to the main BCOM menu. MB-I = will return you to ENTER TASK TO BE USED FOR COMMUNICATIONS. MB-IV = will exit you from the BCOM utility. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg017 ________________________________________________________________ .8.5.2 BQR FILE LIST Two changes have been made to BQR utilities to make them easier to use with TBC. 1. When you define a BQR filelist as a 27xx/37xx transfer, the BQR filelist name is automatically added to the TBC transmit queue. So, when you CTL-IV to list names of transmit queues in the TBC utility, your BQR filelists will display. 2. The last file in a BQR filelist will no longer terminate the TBC session. Instead, the option for NO CHAINING will be used. .8.5.3 AUTO-SCHEDULER ACCEPTS INTERNATIONAL DATE The auto-scheduler now accepts 3 date formats: MMDDYY DDMMYY YYMMDD 3.8.6 ATP CONVERTS STRING FILES TO SERIAL FILES ATP 4.0 has been enhanced. It can now receive string files from 2000/2500/3000/4000 and 1800 systems. It converts them to serial files as it receives them. 3.8.7 UPGRADING TBC 1. Bug fixes have been made to the TBC translation file "TRNCD", therefore, you must erase it. This file will automatically be created when you run "BCOM" and can be found in the BCOM data prefix. Eg: >ERASE "TRNCD" >RUN "BCOM" NOTE: You may have to erase the 'TRNCD' file 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. 2. If you have over 99 terminals on your system, delete the 'BWORK' file in your BCOM data prefix. This file will be re-created when you run "BCOM". (You can display your data prefix by selecting option 7, 'TASK PREFIX UTILITY', from BCOM main menu.) Eg: !DELETE BWORK 3.8.8 UPGRADING MAGNET 1. Add the following command to the ".SYSDATA.START.CMD" file. Eg: !GROUP.CREATE REMOTE TYPE=SYSTEM PRIORITY=3 RUNJOBS=99 MAXJOBS=99 DEVICES="" SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg018 2. Delete the RSM server definition file "DEFNS". This file will be recreated when you startup MAGNET. Eg: !DELETE .SYSDATA.SERVERS.DEFNS 3.8.9 UPGRADING FTF Change your FTF stations to "B4NET" if they are not running MAGNET FTF on 9/10.6G or on 7.5B. The default station type is set to MAGNET. RUN ".NSPGM.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 vice 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: BFCFPS is a MAGNET station. Do you wish to change it to B4NET (Y/CR=N)? 3.9. DIAGNOSTICS NOTE: To access all of the software documented in this section, the prefix must be set to the .R6Gxx.DIAG.,.R6Gxx.INST. node. Please see the installation sections in this announcement for instructions on how to install DEMON and REMIDI. Further information on these diagnostics can be found in DOCWRITER, which can be accessed by entering !DOCWRITER in command mode. 3.9.1. REMIDI NOTE: UPDATE.LD needs to be run for REMIDI whenever question marks (?/?) appear in Load Sector 2 at the top of the OSINFO screen. 3.9.1.1. ON MPx 7000, 7100, AND 8000 SERIES SYSTEMS REMIDI version BV includes all micro-diagnostics except those for the MPC and LAN controllers. It is loaded into WCS slot 2 and is used on MPx 7000, 7100, and 8000 Series Systems. REMIDI version BVM contains micro-diagnostics for the MPC and LAN controllers. It is loaded into WCS slot 3 on all 7000/7100 Series Systems and on 8000 Series Systems with LAN controllers. This version of REMIDI is used on MPx 7000/7100 Series Systems for the MPC and LAN controllers, and on 8000 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg019 Series Systems for LAN controllers only. If a LAN controller is not present on an 8000 Series System, the BVM version of REMIDI is not needed. The Load Directory controls which version of REMIDI will be executed. The UPDATE.LD utility is used to update the Load Directory. See the following section for instructions on running UPDATE.LD. .9.1.1.1. UPDATING THE LOAD DIRECTORY FOR REMIDI Disregard this section if your 8000 Series System does not have a LAN controller. (In this case only REMIDI version BV is used, and it is not necessary to update the Load Directory.) Since REMIDI is a WCS Image, two WCS slots, slot 2 and slot 3, will be required for the two REMIDI versions. The extra slot is provided by the DEMON WCS slot. Because DEMON and the BOSS/VS O.S. share the same WCS, Load Sector 3 should display 3/0 or 3/1, indicating that the WCS for DEMON is in either WCS slot 0 or WCS slot 1. This leaves WCS slot 3 free for REMIDI. Only one version of REMIDI will run at a time. The version that will run is dependent on how the Load Directory for REMIDI (Load Sector 2) is set up. The standard version, BV, which resides in WCS slot 2, has an OS/WCS of 0/2. The MPC/LAN version, BVM, which resides in WCS slot 3, has an OS/WCS of 0/3. Use UPDATE.LD to update the Load Directory to designate which version to run. To test the MPC and LAN controllers with REMIDI version BVM, execute UPDATE.LD, using the inputs below: NOTE: Lines preceded by an "*" require operator input. * Input in command mode !UPDATE.LD Update Load Directory Utility (Version 6.5.5.0) Disks (Unit number) on line : 0(16),1(17) Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 6.7.x.x R 6G*xx (date) B 6.1.x.x 1 1/1 | 6.7.x.x R 6G*xx (date) B 6.1.x.x 2 0/2 | B 5.x.x R 3 3/0 | 6.7.x.x DEMON (date) B 6.x.x R * New OS slot (0,1,3): 0 * New WCS slot (0..3): 3 * Load sector (0..3) : 2 In this case, UPDATE.LD will then display the new Load Directory as follows: Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 6.7.x.x R 6G*xx (date) B 6.1.x.x 1 1/1 | 6.7.x.x R 6G*xx (date) B 6.1.x.x 2 0/3 | B 5.x.x R 3 3/0 | 6.7.x.x DEMON (date) B 6.x.x R Notice the change in Load Sector 2. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg020 To go back to the standard REMIDI version, BV, which tests the CPU and main memory, use the following in UPDATE.LD: * New OS slot (0,1,3): 0 * New WCS slot (0..3): 2 * Load sector (0..3) : 2 In this case, UPDATE.LD will then display the new Load Directory as follows: Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 6.7.x.x R 6G*xx (date) B 6.1.x.x 1 1/1 | 6.7.x.x R 6G*xx (date) B 6.1.x.x 2 0/2 | B 5.x.x R 3 3/0 | 6.7.x.x DEMON (date) B 6.x.x R NOTE: The Load Directory should stay in the above setup in case the system CPU needs to be tested in a down condition. Always use Load Sector 2 for REMIDI. .9.1.2. ON MPx 9xxx AND THE ADVANCED SERIES REMIDI for MPx 9xxx Series Systems consists of two sections, AVA, which is loaded into WCS slot 2, and AVC, which is loaded into WCS slot 3. REMIDI for the ADVANCED SERIES family also consists of two sections, CVA, which is loaded into WCS slot 2, and CVC, which is loaded into WCS slot 3. Unlike the REMIDI versions on 7xxx/8xxx systems, the REMIDI versions on 9xxx and ADVANCED SERIES Systems, are not used independently by slot. In other words, the version of REMIDI in WCS slot 2 calls the version of REMIDI in WCS slot 3 on 9xxx and ADVANCED SERIES Systems. Load Sector 2 contains the OS/WCS pointers for REMIDI. .9.1.2.1. UPDATING THE LOAD DIRECTORY FOR REMIDI Normally, the Load Directory is updated by the operating system when REMIDI is installed with UPDATE.WCS. However, if Load Sector 2 does not reflect an O.S./WCS of 0/2, the UPDATE.LD utility can be run to update the Load Directory: NOTE: Lines preceded by an "*" require operator input. * Input in command mode !UPDATE.LD Update Load Directory Utility (Version 6.5.5.0) Disks (Unit number) on line : 0(16),1(17) Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 6.7.x.x R 6G*xx (date) x 6.x.x 1 1/1 | 6.7.x.x R 6G*xx (date) x 6.x.x 2 ?/? | R x 6.x.x 3 3/0 | 6.7.x.x DEMON (date) R x 6.x.x * New OS slot (0,1,3): 0 * New WCS slot (0..3): 2 * Load sector (0..3) : 2 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg021 UPDATE.LD will then display the new Load Directory as follows: Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 6.7.x.x R 6G*xx (date) x 6.x.x 1 1/1 | 6.7.x.x R 6G*xx (date) x 6.x.x 2 0/2 | R x 6.x.x 3 3/0 | 6.7.x.x DEMON (date) R x 6.x.x Notice the change in Load Sector 2. 3.9.2. DEMON - UPDATING THE LOAD DIRECTORY Because REMIDI resides in WCS slot 3 on 7xxx and 9xxx systems and 8xxx systems with LAN, the Load Directory must point to another WCS slot for DEMON on these systems. The O.S. and DEMON share the same WCS code, therefore, Load Sector 3 should point to the WCS slot used by the O.S. Normally, this is set up by the operating system when DEMON is installed, providing that the correct answers are entered at the UPDATE.OS prompts during installation. If, for any reason, Load Sector 3 does not reflect OS/WCS as 3/0 or 3/1, you may use UPDATE.LD to change it, using the following inputs: NOTE: Lines preceded by an "*" require operator input: * Input in command mode !UPDATE.LD Update Load Directory Utility (Version 6.5.5.0) Disks (Unit number) on line : 0(16),1(17) Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 6.7.x.x R 6G*xx (date) x 6.x.x 1 1/1 | 6.7.x.x R 6G*xx (date) x 6.x.x 2 0/2 | R x 6.x.x 3 3/3 | 6.7.x.x DEMON (date) R x 6.x.x * New OS slot (0,1,3): 3 * New WCS slot (0..3): 0 (or 1) * Load sector (0..3) : 3 UPDATE.LD will then display the new Load Directory as follows: Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 6.7.x.x R 6G*xx (date) x 6.x.x 1 1/1 | 6.7.x.x R 6G*xx (date) x 6.x.x 2 0/2 | R x 6.x.x 3 3/0 | 6.7.x.x DEMON (date) R x 6.x.x Notice that Load Sector 3 is now pointing to WCS slot 0. 3.9.3. ADVANCED SERIES ONLY 3.9.3.1. HIGH FREQUENCY MARGINS ON THE ADVANCED SERIES The ADVANCED SERIES processor has the capability to run at a faster clock rate for diagnostic purposes. This capability is intended for diagnostic testing of the CPUs ONLY. The system should never be used at the higher clock rate except for diagnostic purposes. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg022 3.9.3.2. USING ALT LOAD FOR REMIDI AND DEMON On the ADVANCED SERIES, REMIDI and DEMON can be loaded into memory from the O.S. tape via ALT LOAD and executed. To load REMIDI, load switch 2 should be on. To load DEMON, load switches 2 and 3 should be on. Pressing the ALT LOAD switch will then load the selected diagnostic into memory for execution. 3.9.4 DIAGNOSTIC REMOVAL This section describes the removal of diagnostic programs from a system. The diagnostics reside in the file system and several bootable disk slots. They are removed from the file system with the 'delete' utility. They are removed from the bootable slots by overwriting the images. The procedure follows. 1. Removing REMIDI The removal of REMIDI is accomplished by overwriting the two bootable REMIDI slots with the WCS image. 2. Update WCS Slot 2 Execute the UPDATE.WCS utility and respond to the prompts as shown below. ENTER WCS SLOT (0..3): - 2 AVAILABLE DISK UNITS ARE: - (displayed) DISK TO UPDATE : - Enter the disk number. WCS IMAGE FILE: - .R6Gxx.INST.WCS.X (where X = A,B,C) X = A for MPx 9xxx X = B for MPx 7xxx, 8xxx X = C for Advanced Series WCS LEVEL OF WCS IMAGE FILE: - (displayed) During the update process, the following message appears: UPDATING DISK UNIT nn SECTOR xx When the update is complete, the following message appears: WCS UPDATE COMPLETED! The preceding should be performed on all system disks. 3. Update WCS Slot 3 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg023 Execute the UPDATE.WCS utility and respond to the prompts as shown below. ENTER WCS SLOT (0..3): - 3 AVAILABLE DISK UNITS ARE: - (displayed) DISK TO UPDATE : - Enter the disk number. WCS IMAGE FILE: - .R6Gxx.INST.WCS.X (where X = A,B,C) X = A for MPx 9xxx X = B for MPx 7xxx, 8xxx X = C for Advanced Series WCS LEVEL OF WCS IMAGE FILE: - (displayed) During the update process, the following message appears: UPDATING DISK UNIT nn SECTOR xx When the update is complete, the following message appears: WCS UPDATE COMPLETED! The preceding should be performed on all system disks. 4. Removing DEMON The removal of DEMON is accomplished by overwriting the bootable DEMON slot with DEMON.UX. 5. Update OS Slot 3 Execute the UPDATE.OS utility and respond to the prompts as shown below. BOSS/VS Image File Name: - DEMON.UX Target OS Slot (0/1/3): - 3 Target WCS Slot (0-3): - 0 Target Drives (0/1/All/Quit): - Enter the disk number During the update process, the following message appears: Update in progress : x/y : zz% When the update is complete, the following message appears: Updates all complete. The preceding should be performed on all system disks. 6. Removing diagnostics from the file system The diagnostics are removed from the file system using the 'delete' utility. The diagnostics are found in the system node .R6Gxx.DIAG. The files in the following nodes should be deleted from the file system. .R6Gxx.DIAG. .ENHANCER6G. .TRACKER. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg024 The following files should be deleted: .AC (MPX 9000 Series 1/4" tape boot OS image with DIVE) .AT (MPx 9000 Series 1/2" tape boot OS image with DIVE) .BC (MPx 7000 Series 1/4" tape boot OS image with DIVE) .BT (MPx 8000 Series 1/2" tape boot OS image with DIVE) .CC (Advanced Series 1/4" tape boot OS image with DIVE) .CT (Advanced Series 1/2" tape boot OS image with DIVE) The following file(s) should be added as a replacement for the file(s) deleted above. .ACX (MPx 9000 Series 1/4" tape boot OS image without DIVE) .ATX (MPx 9000 Series 1/2" tape boot OS image without DIVE) .BCX (MPx 7000 Series 1/4" tape boot OS image without DIVE) .BTX (MPx 8000 Series 1/2" tape boot OS image without DIVE) .CCX (Advanced Series 1/4" tape boot OS image without DIVE) .CTX (Advanced Series 1/2" tape boot OS image without DIVE) This completes the diagnostic removal procedure! 3.10 BASIC 1) Protected BASIC programs can be identified by the FID function. Byte 10 of the FID returns the file type. BASIC (unprotected) programs will return a $04$ and protected BASIC programs (PSAVED) will return a $14$. 2) The FID(0), while running as a batch job, will return the batch name instead of the input filename. The batch name consists of the letter "B" followed by a number (e.g. B2,B67). 4. HARDWARE When upgrading to O.S. levels 9/8.6G, hardware changes, per se, are not required EXCEPT if your system contains a DMAII. (See section 4.2-7) However, the following list of PCBA revision levels indicates the MANDATORY and RECOMMENDED revision levels of MPx and ADVANCED SERIES PCBA's. MANDATORY means that the specified revision level is needed for system operation. This level provides minimum assurance that your customer's system will operate in a stable manner. RECOMMENDED means that the specified revision level ensures the reliable operation of your customer's system. The RECOMMENDED (or higher) revision levels help to assure reliability and stability. If your customers' system PCBA's are at MANDATORY levels or below, careful plans should be made to replace the PCBA's with the RECOMMENDED (or higher) revisions. This should be done on a one per visit basis, such as one board per PM visit. DO NOT replace all PCBA's simultaneously. Some RECOMMENDED revision levels may vary based on specific system conffigurations, as detailed below. For example, the 16Mb High Speed Memory PCBA requires specific MCS and Terminator PCBA's. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg025 4.1. MPX 7000, 7100, AND 8000 PCBA NOTES 1) MCS 903374-001 PCBA Revision L is the mandatory and recommended level. Revision S adds another option to the switch setting of SW1. SW1 position 4 (SW1-4) is switch selectable between MPx 7000/7100/8000 Series Systems (SW1-4, OPEN) or MPx 9xxx Series Systems (SW1-4, CLOSED). If the MCS PCBA, at revision S, is switch selected for MPx 9xxx Series Systems and installed into an MPx 7000/7100/8000 Series System, it will not load. - MCS 903374-002 PCBA-Revision V Revision V creates the -002 assembly. This assembly can be used on all MPx systems. 2) MDI 903361-001 PCBA Revision L is the mandatory and recommended level. This level prevents the MDI/ACS clocks from drifting and getting out of phase, which causes "INVOP" and "NILPTR" dumps. - MDI 903408-001 PCBA Revision K is the mandatory and recommended level. This level prevents the MDI/ACS clocks from drifting and getting out of phase, which causes "INVOP" and "NILPTR" dumps. 3) ACS 903379-001/-002 PCBA's Revision L is the mandatory and recommended level. 8000 systems on OS 8.4B or above require revision L, boot prom version 2.0.0.1 or higher. 7000 systems require revision Y or above, boot prom version 2.0.0.4 or higher (MPC support). Revision level Z, boot prom version 2.0.0.2, cannot be used on 7000 systems (no MPC support). Revision levels V and W, boot prom version 2.0.0.3, is obsolete; do not use. Tape load support from a BMTC requires revision T, boot prom version 2.0.0.2 or higher. Systems with 8-inch fixed drives require revision AA, boot prom version 2.0.0.5 or higher. - ACS 903379-003 PCBA Revision AD creates the -003 assembly. This version of the ACS PCBA can also be used in 7000/8000 systems. 7100 systems require AD or higher and this revision level is also quired for support of the 120Mb MTCS tape. Board versions -002 or -003 are mandatory for 3 CPU systems, MPx 7xxx/8xxx Series Systems. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg026 4) MPC 903500 PCBA Revision H is the mandatory and recommended level. If used in the MPx 7100 system, remove JMP3, if present, and set SW2-1 and SW2-4 OFF. - MPC 903546 PCBA Revision B is the mandatory level; revision H is the recommended level. If used in the MPx 7100 system, remove JMP3 if present and set SW2-1 and SW2-2 OFF. 5) TDP Controller 903217-001 PCBA Revision K is the mandatory level. Revision K eliminates excessive sector number errors written to the ERROR LOG. Revision W is the recommended level. This revision checks for Signetic IC's at locations 9E and 10K, if the IC's at these two locations are something other than Signetics, then this revision level is not required. Issue with 8" drives only. - TDP Controller 903453-001 PCBA New build TDP controller, which replaces TDP controller 903217-001. Revision A is the mandatory level. Revision J is the recommended level. This revision checks for Signetic IC's at locations 9E and 10K, if the IC's at these two locations are something other than Signetics, then this revision level is not required. Issue with 8" drives only. 6) NIMLC Controller 903381-001 PCBA Revision E is the mandatory level; revision K is the recommended level. This IMLC must be located to the right of the CPU set. Revision G provides correct line status for Data Set Ready (DSR), when no device is attached. Revision K is mandatory for all three (3) mainframe systems. - NIMLC Controller 903381-002 Revision N creates this version of NIMLC for international use. It provides RS-232-C interface on Port B, using standard 1488/1489 IC's to support cabling longer than 50 feet (provides higher input impedance interface required for use on various Wide-Area Networks). - NIMLC Controller 903534-001 PCBA Revision D is the mandatory and recommended level. Provides the same interface as the 903381-002 PCBA on ports A and B. This NIMLC can be located on the left or right of the CPU. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg027 - NIMLC Controller 903251-001 PCBA This NIMLC was used with the 810 system and will not operate on the MPx series systems. 7) Memory (1Mb, 2Mb, 4Mb) 903516-00x PCBA Revision A is the mandatory level; revision E is the recommended level. Memory 903516-001 PCBA is the 2Mb version. Memory 903516-002 PCBA is the 4Mb version. Memory 903516-003 PCBA is the 1Mb version. 8) Terminator 903199 PCBA Revision D is the mandatory and recommended level. Revision H creates the -004 assembly. Revision H can be used on all MPx systems. 4.2. MPX 9XXX SERIES SYSTEM PCBA NOTES NOTE: An asterisk (*) appears in front of revision levels that are mandatory for main memory support above 12 megabytes. 1) MCS 903374 PCBA Revision L is the mandatory level; revision S is the recommended level. Revision S, or above, is required for reliable system operation. Revision S adds another option to the switch setting of SW1. SW1 position 4 (SW1-4) is switch selectable between the addressing schemes of the MPx 7000/7100/8000 (SW1-4, OPEN) Series Systems or the MPx 9xxx Series Systems (SW1-4, CLOSED). If the MCS PCBA is switch selected for MPx 7000/7100/8000 systems and installed into an MPx 9xxx Series System, board addresses 32 thru 47 are reserved for the IMLC PCB only. If the MPx 9xxx scheme is used then there are no address restrictions. * Revision T is required for main memory support above 12 megabytes. Set SW1-4 to CLOSE for the 9xxx addressing scheme. * Revision V creates the -002 MCS. This revision is mandatory for support of the 16Mb memory board (P/N 903621) on 9xxx systems. It also can be used for main memory support above 12Mb. 2) AMS 903548 PCBA Revision F is the mandatory level, revision L is the recommended level. Revision F released the 4K boot proms version 3.1.0.4. This revision, or above, is required for operation. * Revision N creates the -002 PCBA and is required for main memory support above 12 megabytes. Revision P creates the -003 PCBA and is required for MPx 94xx systems. The -003 PCBA can be used in all MPx systems. Revision is required for support of the 621Mb fixed disk drive. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg028 3) ESTK 903552 PCBA Revision G is the mandatory and recommended level. * Revision J, or above, is required for main memory support above 12 megabytes. 4) IDC 903550-001 PCBA (with cache) IDC 903550-002 PCBA (without cache) Revision H is the mandatory level; revision P is the recommended level. Revision J addresses cache timing problems on selected systems. Do not replace the IDC PCBA on an error free system. 5) IDC64 903597-001 PCBA (with cache) IDC64 903597-002 PCBA (without cache) Revision E is the mandatory level; revision H is the recommended level. * IDC64 PCBA is required for support of main memory above 12 megabytes. Strap E6 to E7 must be out. 6) DMA-I 903554 PCBA * Revision H is the mandatory level; revision AA is the recommended level. Revision H is required for the 600 LPM band printer, model 20. It is also required if 300Mb 8-inch drives log excessive errors in the ERRORLOG. Revision N is required when used with the DMA-II. Revision P, or above, is required for reliable system operation, also if the DMA-III is in the system. vision R is required for use with the 16Mb m mory board for full power fail recovery. Revision Z is required for systems that have more than 2 DMA's installed for performance. Revision AA is recommended when system also contains DMA-II. This revision eliminates soft Head/Cyl (8004) errors reported against the dirves supported on the DMA-I when DMA-II installed. This revision also reports 8001 'Offline status' instead of 8002 'Not ready' when taking disk packs out of removable drives. 7) DMA-II (SCSI) 903599 PCBA Revision K required for MPx 94xx SCSI disk drive support; requires 9.6C or later O.S. Revision L contains a fix for excessive soft errors logged in the ERRORLOG when both DMA-I's and DMA-II's are in the same system. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg029 Revision M Creates the DMAII-002 version. This revision has become the mandatory and recomended level. This is the mandatory level for support of the 364Mb (M380) SCSI disk drive. NOTE: This level of DMAII is mandatory if 9.6G O.S. is installed on the system. (It is also a replacement for the -001 and does not require the 9.6G O.S.) - DMA-II (SCSI) 903741 PCBA This is the new version of DMA-II due to artwork changes. It may be used in place of 903599 PCBA and visa versa. Revision E has become the mandatory and recomended revision level. This revision is mandatory for support of the 364Mb (M380) SCSI disk drive. This creates the -002 version. NOTE: This level of DMAII is mandatory if 9.6G O.S. is installed on the system. 8) DMA-III (SMD) 903679-001 PCBA Revison C is the mandatory and revision D is the recommended vel. The DMA-III is required for support of the 621Mb fixed sk drive. (The 621Mb disk also requires the 903548 -03 AMS board.) The DMA-III revision C controller also supports the 300Mb disk drive without the use of the SMD-I/II PCBA. This controller has the SMD logic on board. Revision E is required for DMAI/II/III to reside in the same system. Revision G is required for systems that have more than 2 DMA's installed for performance. 9) NIMLC 903381-001 PCBA Revision K is the mandatory and recommended level. This NIMLC must be located to the right of the CPU set. - NIMLC 903381-002 PCBA Revision N creates this version of NIMLC for International use. It provides RS-232-C interface on Port B using standard 1488/1489 IC's to support cabling longer than 50 feet (provides the higher input impedance interface required for use on various Wide-Area Networks). - NIMLC 903534 PCBA Revision D is the mandatory and recommended level. This revision provides the same interface as the 903381-002 PCBA on ports A and B. This NIMLC can be located on the left or right of the CPU set. - NIMLC 903251 is OBSOLETE This NIMLC was used with the 810 system and will not operate on the MPx Series Systems. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg030 NOTES: There have been a few instances when a known good IMLC is installed into the MPx 9xxx system, the RED LED (Parity error) comes on during load (903534/903381). In this case, install JMP C on the PCBA. When the JMP C option is used on the MPx 9xxx system and "T0" is a serial terminal, the system will hang in the TYPE II/III load. This side effect only occurs with the 9.6A OS and is fixed in 9.6B OS and above. Refer to Field Bulletin #375. 10) Memory (1/2Mb and 1Mb) 903349 PCBA Revision V is the mandatory and recommended level. This revision is not to be used with greater than 12 megabyte support. 11) Memory (2 and 4 MB) 903516-00x PCBA Revision E is the mandatory and recommended level. Memory 903516-001 PCBA is the 2Mb version, 903516-002 PCBA is the 4Mb version. * Revision J is required for support of main memory above 12 megabytes. Support of main memory above 12 megabytes is supported on MPx 9500 and 9600 Series Systems only. JMP 5 at location 1E = 1 to 2, and IC pad location 1A = 8 to 9. 12) 16/8/4Mb High Speed ECC Memory 903621-00x PCBA High Speed ECC Memory 903621-001 (16Mb), -003 (8Mb), -004 (4Mb) version are supported on the MPx 9xxx Series Systems. Requires MCS -002, Terminator -004, DMA-I at revision R or above for MPx Series Systems. Revision C is the mandatory level; revision F is the recommended level. Revision G creates the 903621-005 (16Mb), -007 (8Mb), -008 (4Mb) versions. Revision N if 30 or more slots are used in 9530. 13) Terminator 903199 PCBA Revision D is the mandatory and recommended level. Revision H creates the -004 assembly, which is mandatory for support of the 16Mb, High Speed ECC memory board versions (P/N 903621). The following boards are NOT supported on MPx 9xxx Series Systems: 1) 7000/7100/8000 CPU set 2) TDP (Must be replaced by the BMTC for tape support) 3) MPC 4.3. PCBA'S FOR ALL MPX 7/8/9xx SERIES SYSTEMS The following are PCBA'S common to all MPx Series Systems without system model dependencies: SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg031 1) BMTC 903413 PCBA Revision R is required for full MTCS support. Revision U is required for support of the GCR 1/2" tape drive model 4405. Revision Z allows the BMTC to operate on the left or right side of the CPU set. 2) Local Area Network Controller (LAN) 903595 PCBA Revision E is the mandatory level; revision F is the recommended level. With the release of the 9.6A/8.6A O.S., a new controller is supported: The Local Area Network controller. The LAN PCBA provides the ability to tie like systems together (MPx to MPx) in a local environment not more than 4000 feet apart. Each system requires one LAN controller, and both systems must be on the same O.S. level. The LAN may be installed either to the right of the CPU set(s) after the BMTC PCBA or to the left of the MCS PCBA. Refer to the MAGNET section in this document for further information on the Local Area Network. Revision H creates the -002 version. This version can be used on all MPx series systems and ASxx systems. 3) 16-Way Controller 903437 PCBA Revision J is the mandatory and recommended level. 16-Way controllers require the use of an I/O panel. The I/O panel is supplied with the purchase of the PCBA. 4) 8-Way Controller 903383 PCBA Revision A is the mandatory and recommended level. 5) VCON Controller 903377 PCBA Revision C is the mandatory and recommended level. 4.4. ADVANCED SERIES PCBA NOTES The following are PCBA's that are supported on the ADVANCED SERIES and their revision levels. NOTE: An asterisk (*) appears in front of revision levels that are MANDATORY for the Doublewide backplane chassis. A pound sign (#) appears in front of revision levels that differ form the minumum revision levels of the Advanced Series systems. These revision levels are MANDATORY for the Advanced Series model 21 system. 1) MCS/M 903718 PCBA Revision G is the released level of this PCBA. The MCS/M (Memory Communication Support with Memory) PCBA provides boot load function/clocks/4way and 4Mb of main memory. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg032 # Revision H (-002) is the mandatory level for support of the DMA-II PCBA and the 364Mb (M380) SCSI disk drive on the Advanced Series system. Revision J required for 19.2 KBaud and 7/8 bit data support for T0. 2) NEP II 903705 PCBA Revision G is the mandatory level; heat-sink added. Revision J recommended. * Revison K is the mandatory level when used in the Doublewide backplane chassis. This is also the recomended level for the model 21 system. 3) STACHE II 903707 PCBA Revision D is the released level of this PCBA. The STACHE II PCBA is an optional PCBA that makes up the ADVANCED SERIES Model 6x. It contains the Rstack, Code Cache, and Data Cache. * Revision F is mandatory for Doublewide backplane chassis. 4) MBA 903617 PCBA Revision D is the released level of this PCBA. The MBA (Memory Bus Adapter) PCBA is required to support the shared memory controllers developed for the MPx 8/9xxx systems (160ns clock) on the ADVANCED SERIES Models 40/60 (80ns clock). Revision E is mandatory for support of the Advanced Series system. # * Revision H is mandatory for the Doublewide backplane chassis. This is also the recomended revision level for ALL Advanced Series systems. 5) BMTC 903413 PCBA Revision Z is mandatory for support of the ADVANCED SERIES systems. 6) LAN 903595-002 PCBA Revision H creates the -002 version, this version is mandatory for support of the ADVANCED SERIES systems. 7) DMA-I 903554 PCBA Revision R is mandatory for support on the ADVANCED SERIES, due to the 1Mbit rams used for main memory (MCS/M and 16Mb PCBA's) and full power fail recovery. REV T corrects a problem in REV R firmware which caused the timeout LED (DS2) to turn on during REMIDI testing in the ADVANCED SERIES family only. Revision Z is required for systems that have more than 2 DMA's installed for performance. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg033 Revision AA is recomended when system also contains DMA-II. This revision eliminates soft Head/Cyl (8004) errors reported against the drives supported on the DMA-I when DMA-II installed. This revision also reports 8001 'Offline status' instead of 8002 'Not ready' when taking disk packs out of removable drives. 8) DMA-II (SCSI) 903599-002 PCBA # Revision M is mandatory for support of the 364Mb (M380) SCSI 5-1/4 inch disk drive. This revision creates the -002 version. Revision N is the mandatory revision level if the Advanced Series system contains more than 4MB of main memory using the 903621-00x High Speed ECC memory. - DMA-II (SCSI) 903741-002 PCBA # Revision E is mandatory for support of the 364Mb (M380) SCSI 5-1/4 inch disk drive. This revision creates the -002 version. Revision F is the mandatory revision level if the Advanced series system contains more than 4MB of main memory using the 903621-00x High Speed ECC memory. 9) DMA-III (SMD) 903679-001 PCBA Revision C is the mandatory and recommended level. The DMA-III is required for support of the F621 (600Mb) disk drive. It also supports the P314 (300Mb) disk drive without the use of the SMD-I/II PCBA. This controller has the SMD logic on board. Revision E is only mandatory if the DMA-I and DMA-II is also in the system. Revision G is required for systems that have more than 2 DMA's installed for performance. 10) IMLC 903534 PCBA Revision D is mandatory for support of the ADVANCED SERIES. This version of IMLC, at the indicated revision level, is required to function on the left side of the CPU set. Remove JMP C if installed. 11) 16/8/4Mb High Speed ECC Memory 903621-00x PCBA Revision G creates the -005 (16Mb), -007 (8Mb), -008 (4Mb) versions. Refer to DMAII, section 8, for other concerns if DMAII is in the system. # * Revision N is the mandatory level. This revision helps prevent the possibility of parity errors during Nibble Mode cycles (Code Cache). 12) 8-WAY 903383 PCBA There is no mandatory revision level required for support of this PCBA on the ADVANCED SERIES. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg034 13) 16-Way 903437 PCBA Revision J is LARL for support on the MPx and ADVANCED SERIES. 14) Terminator 903199-004 PCBA Revision H is the mandatory level, and it creates the -004 version. 15) Terminator, High Speed 903769 PCBA * Revision A releases the High Speed Terminator, mandatory in Doublewide chassis. 16) LS-700 Power Supply Assembly 907295-001 If any MPx 8000 system is being upgraded to the ADVANCED SERIES family, the LS-700 assembly 907295-001 must be at revision AA. (PCBA 903386-001, inside the LS-700 assembly, will be at revision AB or above.) If any MPx 9xxx system is being upgraded to the ADVANCED SERIES family, the LS-700 power supply does not need to be replaced. The load sustained by this power supply under the 9xxx configuration gives sufficient evidence that the existing revision level is adequate for the ADVANCED SERIES. 4.4.1. PCBA's NOT SUPPORTED ON ADVANCED SERIES The following boards are NOT supported on the ADVANCED SERIES family: 1) 7x00/8000/9x00 CPU sets. (Use ADVANCED SERIES 40/60 CPU's) 2) MCS PCBA. (Use MCS/M) 3) MPC and TDP's. (Use DMA-I, DMA-II, and DMA-III) 4) Memory 903349 (1Mb assembly), 903516 (4Mb assembly), 903621-001/-003/004. (Use 16Mb: -005, 8Mb: -007, 4Mb: -008) 5) VCON PCBA and HVDT's 6) Terminators -001 (Below revision H). (Use -004) 4.5. PERIPHERAL DEPENDENCIES 4.5.1. TAPE DRIVES .5.1.1. GCR TAPE DRIVE It is possible for a hang condition to occur in SAVERESTORE, if the GCR tape drive does not have the following minimum revision levels: IF CARD 403923205 (Previously, the LARL was 403923202) CP CARD 403864305 (Previously, the LARL was 403864303) .5.1.2. SCSI MTCS TAPE DRIVE On the SCSI MTCS 1/4-inch tape drive (4406), the E-PROM (OEM PN 966039; MBF PN 400716-103) at location 'U6' should be 3X10. This tape drive is used on MPx 94xx systems only. Requires the DMA-II for support. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg035 4.5.2. TERMINALS 1) The DT-4313 terminal must have REV E firmware to support Industry Standard slave printers. 2) T0 MUST be a model 4309 or later model VDT. VDT's 7250 and 7270 (4301) are not supported as T0 on release levels 9/8.6C and above due to default terminal driver change. This change corrected the time differences seen in Saverestore Type I vs Type II load. 3) OS level N.6E and above loads T0 with defaults when going into a Type 2 or 3 load. After reloading the system, these settings remain loaded in the terminal. If T0 is configured to settings other then the default values, the terminal will need to be reset. Defaults = EVDT, 9600, 7-bit, ODD Parity. 4.5.3. DISK DRIVES 1) The 590Mb (F621 aka 600Mb) fixed disk requires the -003 version of AMS PCBA P/N 903548 when used in 9xxx systems. The F621Mb disk is supported by the DMA-III controller, P/N 903679. 2) The 300Mb (P314) fixed disk requires revision AA of ACS PCBA P/N 903379 when installed on MPx 7xxx/8xxx systems. TDP (PDC) controller P/N's 903217 and 903453 require IC's OTHER THAN Signetics (indicated by a bold 'S') at locations 9E and 10K (74S240). 3) The 364Mb (M380) SCSI 5-1/5 inch disk drive requires *.6G OS or above and the -002 version of the DMA-II. See MCS/M and DMA-II for other requirements for the system that it will be installed on. 5. INSTALLATION 5.1. FILE NAMING CONVENTION The names of the files that are loaded into the OS/WCS slots are generic in order to simplify installation procedures. **************************************************************** * * * IN THE FOLLOWING INSTALLATION INSTRUCTIONS, THE * * REFERENCES TO ".R6Gxx" SHOULD BE REPLACED BY THE ACTUAL * * RELEASE LEVEL THAT IS FOUND ON THE LABEL OF THE OS TAPE. * * * **************************************************************** The first letter of the name will designate the machine type as follows: A - MPx 9xxx Machine Type B - MPx 8xxx/7xxx Machine Type C - ADVANCED SERIES Machine Type U - Universal Disk Image Format SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg036 The second letter of the name will be used to designate the boot image type as follows: C - 1/4 inch Cartridge Tape Boot Image D - 1/2 inch Diagnostic Tape Boot Image Load & Execute T - 1/2 inch Tape Boot Image Load & Copy V - Universal Disk Image Format The third letter, if present, will be used to designate the Micro Peripheral Controller WCS images and the four REMIDI image formats, as follows: A - First REMIDI Module B - Second REMIDI Module C - Third REMIDI Module D - Fourth REMIDI Module M - Micro Peripheral Controller .1.1. FILE NAMES BOSS/VS IMAGES .R6Gxx.INST.OS.CT 1/2 Inch Tape Boot, ADVANCED SERIES .R6Gxx.INST.OS.CC 1/4 Inch Tape Boot, ADVANCED SERIES .R6Gxx.INST.OS.AT 1/2 Inch Tape Boot, MPx 9xxx .R6Gxx.INST.OS.AC 1/4 Inch Tape Boot, MPx 9xxx .R6Gxx.INST.OS.BT 1/2 Inch Tape Boot, MPx 8xxx .R6Gxx.INST.OS.BC 1/4 Inch Tape Boot, MPx 7xxx .R6Gxx.INST.OS.UV Universal Disk Boot Image, MPx/ADVANCED SERIES DEMON IMAGES .R6Gxx.DIAG.DEMON.CC 1/4 Inch Tape Boot, ADVANCED SERIES .R6Gxx.DIAG.DEMON.CD 1/2 Inch Tape Boot, ADVANCED SERIES .R6Gxx.DIAG.DEMON.AD 1/2 Inch Tape Boot, MPx 9xxx .R6Gxx.DIAG.DEMON.AC 1/4 Inch Tape Boot, MPx 9xxx .R6Gxx.DIAG.DEMON.BD 1/2 Inch Tape Boot, MPx 8xxx .R6Gxx.DIAG.DEMON.BC 1/4 Inch Tape Boot, MPx 7xxx .R6Gxx.DIAG.DEMON.UV Universal Disk Boot Image, MPx/ADVANCED SERIES REMIDI MPx 7xxx/8xxx IMAGES .R6Gxx.DIAG.REMIDI.BDM 1/2 Inch Tape Boot, MPC/LAN .R6Gxx.DIAG.REMIDI.BCM 1/4 Inch Tape Boot, MPC/LAN .R6Gxx.DIAG.REMIDI.BVM Disk Boot Image, MPC/LAN .R6Gxx.DIAG.REMIDI.BD 1/2 Inch Tape Boot, CPU .R6Gxx.DIAG.REMIDI.BC 1/4 Inch Tape Boot, CPU .R6Gxx.DIAG.REMIDI.BV Disk Boot Image, CPU REMIDI MPx 9xxx IMAGES .R6Gxx.DIAG.REMIDI.ADA 1/2 Inch Tape Boot Module 1 .R6Gxx.DIAG.REMIDI.ADB 1/2 Inch Tape Boot Module 2 .R6Gxx.DIAG.REMIDI.ADC 1/2 Inch Tape Boot Module 3 .R6Gxx.DIAG.REMIDI.ADD 1/2 Inch Tape Boot Module 4 .R6Gxx.DIAG.REMIDI.ACA 1/4 Inch Tape Boot Module 1 .R6Gxx.DIAG.REMIDI.ACB 1/4 Inch Tape Boot Module 2 .R6Gxx.DIAG.REMIDI.ACC 1/4 Inch Tape Boot Module 3 .R6Gxx.DIAG.REMIDI.ACD 1/4 Inch Tape Boot Module 4 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg037 .R6Gxx.DIAG.REMIDI.AVA Disk Boot Image for Module 1 & 2 .R6Gxx.DIAG.REMIDI.AVC Disk Boot Image for Module 3 & 4 REMIDI ADVANCED SERIES IMAGES .R6Gxx.DIAG.REMIDI.CD 1/2 Inch Tape Boot Module 1 through 4 .R6Gxx.DIAG.REMIDI.CC 1/4 Inch Tape Boot Module 1 through 4 .R6Gxx.DIAG.REMIDI.CVA Disk Boot Image Module 1 & 2 .R6Gxx.DIAG.REMIDI.CVC Disk Boot Image Module 3 & 4 WCS FILES .R6Gxx.INST.WCS.C WCS for ADVANCED SERIES .R6Gxx.INST.WCS.A WCS for MPx 9xxx .R6Gxx.INST.WCS.B WCS for MPx 8xxx/7xxx 5.2. GENERAL INFORMATION IMPORTANT NOTE 1: AS OF RELEASES 9/8.6C, POSITIONING OF THE O.S. AND WCS SLOTS HAS BEEN ADJUSTED SLIGHTLY. THEREFORE, O.S./WCS LEVELS PRIOR TO 9/8.6C CANNOT RESIDE IN SLOTS ON THE SAME DISK WITH RELEASE LEVELS 10/9/8.6G. IMPORTANT NOTE 2: THE .SYSDATA.SECURITY.DATA FILE SHOULD BE SAVED BEFORE UPGRADING TO 10.6G/9.6G/8.6G IF YOUR CURRENT RELEASE IS BELOW 9/8.6C. AS OF RELEASES 9/8.6C, THE SECURITY.DATA FILE HAS A NEW FORMAT AND IS NOT TRANSPORTABLE TO RELEASES PRIOR TO 9/8.6C. IMPORTANT NOTE 3: IT IS NOT EXPECTED THAT A DOWNGRADE FROM 10/9/8.6G WILL BE NECESSARY. HOWEVER, IF A DOWNGRADE IS PERFORMED TO A RELEASE PRIOR TO 9/8.6C *11, THE USER'S FILES MUST BE TRANSPORTED TO THE OLDER O.S. LEVEL VIA EXTTAPE, MCSI, FTF, TBC, or ATP. FAILURE TO DO SO WILL RESULT IN INCOMPATIBLE FILE CONTROL SEGMENTS. THE VOLUME LABEL MUST ALSO BE REWRITTEN ON THE OLDER O.S. LEVEL. THERE ARE NO RESTRICTIONS ON A DOWNGRADE TO 9/8.6C *11. These Installation Instructions assume that the reader is familiar with BOSS/VS installation procedures and TYPE 3 LOAD Special Functions. For further information, see the BOSS/VS INSTALLATION GUIDE, M5138D. If you are installing the O.S. on a newly formatted System disk or changing a Data disk to a System disk on any system, go to section 5.3. If you are upgrading a 8xxx Series System to 8.6G from level 8.4D or below, go to section 5.4. If you are upgrading a 7xxx or 8xxx Series System to 8.6G from level 8.4E or above, go to section 5.5. If you are upgrading a 9xxx Series System to 9.6G, go to section 5.6. If you are upgrading an ADVANCED SERIES to 10.6G, go to section 5.7. If you have just received a new system, please note the following: new systems are shipped with the operating system installed on the disk, and the TYPE 3 LOAD (Special Functions) parameters already SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg038 set up. If you wish to change the disk/family information on your new system, you must run Option 2 (Update Family Information) of INITIALIZATION OPTIONS (OPTION 2 on the main menu) in a TYPE 3 LOAD. (See section 5.3.1.2.2). For further information on setting up families on your system, see the BOSS/VS INSTALLATION GUIDE, M5138. After the families are set up to your satisfaction, go to section 5.3.1.3. Beginning with release 9.6A/8.6A there is a change in the way terminals are enabled for user log-on at system load time. Initial enabling of the TERMINALS group, which allows users to log-on, is now under user control through the use of the Startup Command File. If the file does not exist, the TERMINALS group is enabled automatically. Refer to section 5.9 for further information on the startup command file and startup procedures for JOB MANAGER, MAGNET, and the SPOOLER. Since the operating system can be released on 1/2" (reel) or 1/4" (cartridge) tape, the word "tape" means either media form. 5.3. NEW OPERATING SYSTEM INSTALLATION 5.3.1. INSTALLING THE OPERATING SYSTEM Follow the instructions in this section if you are creating a SYSTEM disk on a newly formatted disk, or if you are changing a DATA disk to a SYSTEM disk. .3.1.1. LOADING SLOTS 0 AND 1 USING ALT LOAD NOTE: ALT LOAD has been enhanced so that it will automatically load both slots 0 and 1 on a new installation. (WCS slots 2 and 3 are also loaded with the BOSS/VS WCS for formatting purposes only. The user needs to reload these slots with the REMIDI WCS files, using UPDATE.WCS. See the sections on updating slots 2 and 3 in this announcement.) To perform an ALT LOAD from tape follow these steps: A) Mount the new release tape in the tape drive. (All front panel load select switches should be OFF if using tape drive 0. Switch 1 should be ON if using tape drive 1.) B) Press the "ALT LOAD" button on the front panel. First, a proprietary message will be displayed, and then the following load screen: ____________________________________________________________________ Load PROM Version: x.x.x.x SYSTEM SERIAL NUMBER : 000-00000 Load Drive n SERIAL NUMBER CREATOR: 000-00000 WCS 0 Version: x.x.x CONFIGURATION CREATOR: 000-00000 OS 0 Version: 6.7.x.x SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg039 CPUs ID #s : n Memory (Mb) : n.0 Disk Drives : n BOSS/VS LOAD FROM TAPE Tape Drives : n Printers : n HVDTs : n IMLCs : n Serial Ports: n Date Format MM/DD/YY: BMTCs : n/n DATE = MM/DD/YY: LAN Cntrlrs : n TIME = HH:MM:SS: SYSTEM PREFIX: (family).R6Gxx.SYS. System Default Family: (family) File System Write Through : T/F User Default Family : (family) Per-File Write Through : T/F Installation Name : (name) File System Security : T/F ____________________________________________________________________ Key in the current DATE and TIME at the above prompts. The screen will then display: ____________________________________________________________________ L O A D I N G . . . BOSS/VS Operating System Image Update Utility [version 6.5.x.x] OS/WCS information for drive n (nn): 0: ?????????????? ??????? | x x.x.x 1: ?????????????? ??.??.??.??? | ? ?.??.?? 2: -------------- -- -- -- --- | ????????? 3: ?????????????? ??????? | ????????? BOSS/VS Image File Name: (displays one of the following): OSN.CT0607xxxxx (ADVANCED SERIES) OSN.AT0607xxxxx (9x00 systems - 1/2-inch) OSN.AC0607xxxxx (9400 systems - 1/4-inch) OSN.BT0607xxxxx (8000 systems - 1/2-inch) OSN.BC0607xxxxx (7x00 systems - 1/4-inch) Target OS Slot (0/1/3) : '0' (or 1) Target WCS Slot (0-3) : '0' (or 1) Target Drives (0/1/All/Quit): (choose drive) ____________________________________________________________________ C) The Image File Name will be displayed by the system. Enter '0' or '1' at the slot prompts to load O.S. and WCS slots 0 and 1. Enter '0', '1', or 'All' at the drive prompt to update the appropriate drives. NOTE: Do not update drive 1 if it is a DATA disk and is to remain so. The system will now display: ___________________________________________________________________ Now updating WCS slot # n Update in progress: nn% SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg040 Now updating BOSS/VS Image (displays one of the following): OSN.CT0607xxxxx (ADVANCED SERIES) OSN.AT0607xxxxx (9x00 systems - 1/2-inch) OSN.AC0607xxxxx (9400 systems - 1/4-inch) OSN.BT0607xxxxx (8000 systems - 1/2-inch) OSN.BC0607xxxxx (7x00 systems - 1/4-inch) Update in progress: nn% Image slot directory n/n:n Updates all complete. D O N E - R E A D Y F O R N O R M A L D I S K L O A D ___________________________________________________________________ When O.S. and WCS slots 0 and 1 have been updated, reload the system by pressing the LOAD switch. .3.1.2. TYPE 3 LOAD (Special Functions) NOTE: If any disk has a 'MASTER' status, no update to the disk will be allowed. You must change the disk to a 'BACKUP' status in order to perform the TYPE 3 LOAD functions. To do this, select OPTION 4 (CHANGE MASTER/BACKUP STATUS) from the TYPE 3 LOAD main menu. Be sure to change the disk back to a 'MASTER' status after the TYPE 3 LOAD functions are completed (if this status is desired). This MASTER/BACKUP status is simply a flag which makes it possible to write-protect a disk. It is not to be confused with the disk configuration (e.g., SYSTEM, DATA, BACKUP) specified in Option 1 (Change Volume Label Information) of INITIALIZATION OPTIONS (OPTION 2 on the TYPE 3 LOAD main menu). Select OPTION 2 - INITIALIZATION OPTIONS Option 1 (Change Volume Label Information) must be done on all disks. Options 2 (Update Family Information) and 3 (Initialize Family Directory) must be done for each family. Option 4 (Change Installation Parameters) must be done on system disks only. .3.1.2.1. OPTION 1 (CHANGE VOLUME LABEL INFORMATION) All available disk drives will be displayed. An 'available' drive is any drive cabled to the system, whether enabled, disabled, powered ON or OFF. The selected drive entered in response to the Option 1 prompt must be online and ready. ENTER DRIVE NUMBER OF VOLUME LABEL TO CHANGE:______ (Enter volume label to change. The screen will change to display the information for only the drive whose volume label you choose.) SERIAL NUMBER _________ (Enter CR to accept current serial number.) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg041 DISK CONFIGURATION (1=SYSTEM, 2=DATA, 3=BACKUP) ____ (Enter the appropriate disk type.) SIZE OF DUMP AREA.....______ x 1024 BYTES (For system disks only, enter the size of the dump area displayed on the line below this prompt as the area needed for both main memory and shared memory controllers. If installation of additional memory and/or shared memory controllers is planned, increase the dump area size to accommodate them. See Field Bulletin # 211, "Computing Dump Area Size".) FILE SYSTEM SPACE ______ x 1000 SECTORS (Enter the number displayed at the bottom of the screen for this prompt. The display will appear as "CR=X" where X is the maximum space allowed.) UPDATE DISK VOLUME LABEL (Y/N) __ (Enter "Y" if above information is correct.) Repeat the steps in 5.3.1.2.1 for all remaining disk drives. .3.1.2.2. OPTION 2 (UPDATE FAMILY INFORMATION) NOTE: Removable drives can only have one member per family. Fixed drives can be combined to create a larger capacity disk family. The disk information for all drives on the system is displayed and the cursor is positioned at 'FAMILY BASE DRIVE NUMBER'. FAMILY BASE DRIVE NUMBER ___ FAMILY NAME ______ (CR for default family name.) DRIVE NUMBERS OF OTHER DISKS IN FAMILY? (TYPE SPACES FOR NO OTHER DRIVES) (Enter all other drive numbers for this family or spaces if none. The drives must be fixed media drives.) UPDATE DISK (Y/N)? Repeat the steps in 5.3.1.2.2 until all drives are identified in a family. .3.1.2.3. OPTION 3 (INITIALIZE FAMILY DIRECTORY) This option displays all base drives on the system. FAMILY BASE DRIVE NUMBER ______ (Enter drive number to be initialized.) INITIALIZE FAMILY? (Y/N) __ (CAUTION: Ensure that all data you want is backed up. This step will delete all data on the disk.) Repeat the steps in 5.3.1.2.3 for all defined families. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg042 .3.1.2.4. OPTION 4 (CHANGE INSTALLATION PARAMETERS) NOTE: On newly formatted disks, the following message will be displayed: "CAN'T READ INITIALIZATION PARAMETERS FROM DISK. STATUS = (3,7,30,1), TO CONTINUE:" Just press and continue. Only SYSTEM disks will be displayed. DRIVE NUMBER _______ PRIMARY PREFIX __________________ (Enter (family).R6Gxx.SYS. (Family) is the family where the operating system files will reside.) SECONDARY PREFIX _______________ (Enter (family).R6Gxx.SYS. (Family) is the family where the alternate OS/WCS image files reside for slot 1.) SYSTEM INSTALLATION NAME ________________ (Sets the default installation name for a specified system disk. Used only with MAGNET. Enter for default.) DEFAULT USER FAMILY NAME _____________ (Enter default user family.) SECURITY (E=ENABLED, D=DISABLED) ___ FILE SYSTEM WRITE THROUGH? (E=ENABLED, D=DISABLED) ___ WRITE THROUGH DEFAULT ON FILE CREATE (E=ENABLED, D=DISABLED):__ (This parameter specifies what the default write through will be on a file created through a BASIC file create or through the CREATE utility.) UPDATE DISK WITH INSTALLATION PARAMETERS? (Y/N) __ Display: INSTALLATION PARAMETERS SUCCESSFULLY WRITTEN TO DISK. (CR) TO CONTINUE: Repeat the steps in 5.3.1.2.4 for any additional system disks. If you changed your disk from a 'MASTER' status to a 'BACKUP' status to do the TYPE 3 LOAD functions, change it back to a 'MASTER' status at this point. Reload the system by pressing the LOAD switch. Be sure you are loading from the drive where you wish to restore the operating system files. 5.3.1.3. RESTORING THE O.S. Enter SAVERESTORE in a TYPE 2 LOAD and choose OPTION 2 RESTORE FILES FROM TAPE. The screen appears as in figure 5-1. At the prompt for output device, enter a parallel printer so that a listing of the restore operation is produced. This listing can be used to make sure all files were restored correctly. On the next screen, at the prompt, "FILE SPECIFIERS", enter ".". Then enter twice. All system files will be restored to disk. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg043 Once all files are restored to disk, the message "AUTOMATIC COMPARE, CR TO CONTINUE" appears. This automatically rewinds the tape and begins the compare operation. This only occurs when the compare option is selected. When the compare is completed, enter a CTL-IV to return to the "SAVERESTORE" menu. Reload the system and enter a TYPE 1 LOAD. Figure 5-1. Restore Screen -------------------------------------------------------- RESTORE FILES TAPE SET.ID: DRIVE-NUM: REEL-NUM: PRIMARY PREFIX: (FAMILY).NODE. FILE TYPE (D/P/CR=ALL) COMPARE (CR=Y/N) DATE (MM/DD/YY) TIME (HH:MM) OUTPUT DEVICE (CR=VDT) DELETE EXISTING FILES (CR=Y) VERIFY (Y/CR=N) ENTRIES CORRECT (Y/N) -------------------------------------------------------- At this point it is necessary to install the System Serial Number (using GENSSN) on newly formatted disks and DATA disks that you are changing to SYSTEM disks. 5.3.2. INSTALLING THE CONFIGURATION RECORD It is necessary to install a new configuration record when installing a new system or when upgrading to 8.6G from 8.4 and 8.5 O.S. levels or when changing systems. Until the following procedure is completed, the system will have a minimum configuration. New systems normally already have a configuration record installed. If you have a new system, and you want to verify that the configuration record has been installed, run the CONFIG.MGR utility in a TYPE 1 LOAD. If the configuration record has already been installed, you may skip this section. Enter a TYPE 1 LOAD. Set your prefix to .SYSTEM.CONFIG. Using the SAVERESTORE utility, restore the new configuration record on tape onto your system. Execute the CONFIG.MGR utility. The CONFIG.MGR utility allows the user to update the system configuration record by installing a new configuration file. This utility displays the current and new configuration record. When "Y" is answered to the prompt "Install Configuration:", the new configuration is copied from the file ".SYSTEM.CONFIG.I(serial number)", to the special system area on disk. The new configuration takes effect at the next system load. For further details on the use of the CONFIG.MGR utility, see the 8.5D/9.5D Software Announcement #139, or the BOSS/VS Utility User Guide, M5102. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg044 The configuration record file name is derived from the system serial number by changing the leading "8" to an "I" and adding the prefix ".SYSTEM.CONFIG.". EXAMPLE: .SYSTEM.CONFIG.I1030114 for SSN 810-30114 This configuration record tape should be saved, in case re-installation should become necessary. Before going to the next step, LOAD the system so the new configuration record will take effect. If you do not load the system, you will have a minimum configuration and the system will be very slow. If you are installing a 7xxx/8xxx system, go to section 5.5.4 to load the remaining slots. If you are installing a 9xxx system, go to section 5.6.6 to load the remaining slots. 5.4. UPGRADING TO 8.6G FROM RELEASE LEVELS 8.4D AND BELOW 5.4.1. INTRODUCTION NOTE: This section contains references to the FILESIZE, NFSCONVERT, and DISKANALYZER utilities. Further information on these utilities and their use during file conversion can be found in the following sources: - BOSS/VS FILE CONVERSION GUIDE, M5185 - BOSS/VS UTILITY USER GUIDE, M5102 - Software Announcements for release levels 8.4E and 8.5A/B/C/D - HELP SCREENS accessed by keying in UTILITYNAME.HELP in command mode If you are upgrading from a software release level of 8.4D or below. Since release levels 8.4E and above contain new file formats and a new file system, conversion of files is required to make files compatible with the new file system, if you are upgrading from a software release level of 8.4D or below. The file conversion can be done in two ways: A) From tape to disk B) From disk to disk Which method used depends on the configuration of the system. The disk to disk method is preferable for a system with removable disks. The disk to disk method involves upgrading the system disk with the new O.S. Then the system disk can be used to convert other disks by using the NFSCONVERT utility to convert one file from one disk to another. If the disk to disk method is used on fixed disks, any user files must be copied from the fixed system disk to another disk or to tape for conversion. This is because the system disk must be initialized and updated to the new O.S. to do the conversion. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg045 To do a tape conversion, a save and restore is performed with the SAVERESTORE utility in the normal manner. The conversion process is invisible to the user with the exception of the following status message that is displayed during conversion: "Now converting to NFS format...." The tape conversion requires about 4 minutes per megabyte of data. The installation procedure is broken into two parts: A) Preliminary evaluation B) Operating System upgrade and file conversion The preliminary evaluation is required to ensure that proper hardware and file preparation is done. An O.S. upgrade from releases of 8.4D and below entails loading of the 8.6G O.S. and converting files to their new format. In large configurations, the conversion process will take more than one day. At the end of this section is an upgrade and conversion checklist that should be used to track progress through the upgrade procedure. 5.4.2. PRELIMINARY EVALUATION The preliminary section deals with revision levels and file preparation. .4.2.1. HARDWARE EVALUATION All hardware must be checked for proper operation. All boards must be at proper revision levels (see the HARDWARE section in this announcement.) Ensure that all tape units are operating correctly. .4.2.2. FILE PREPARATION Obtain a directory listing with partial attributes for each family in the system. This listing will help you to find files, if any, that need repair before conversion. Next, using DISKANALYZER, select the option "VALIDATE ALL FILES" to determine which files need repair. Files which have the following attributes MUST be repaired before they are saved to tape: A) Files which lack integrity. B) Files which have lost space. C) Non-serial files in which records used is greater than records defined. D) Files that have invalid format. These files can be located in several ways: A) Scan the directory listing noting any files flagged as lacking integrity. B) Use the report generated by the DISKANALYZER "VALIDATE ALL FILES" option. (Preferred method) C) Use the utility FINDLOSTSPACE (8.4C/D only). SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg046 All of the above methods should be used to find files that lack integrity and that have lost space. However, the directory listing must be scanned to find files that have a greater number of records used than defined as maximum records. This is a very ant step. Any file possessingg any f these attributes WILLs WILL NOT convert properly. They have to be repaired on a previous release before conversion. Any EDITOR recovery files must be recovered or deleted before conversion. The recovery files are identified by the node ED.REC. After the node, there will be a series of digits. These files can be found by scanning the directory listing. These files must be recovered by using EDIT.RECOVER or deleted by using the DELETE utility. ***************************************** * * * ALL FILES MUST BE FREE FROM LACK OF * * INTEGRITY, LOST SPACE, AND MAX * * RECORDS GREATER THAN DEFINED RECORDS. * * FILES WILL NOT BE CONVERTED IF THEY * * POSSESS ANY ONE OF THESE ATTRIBUTES. * * * ***************************************** .4.2.3. NEW FILE SYSTEM SPACE REQUIREMENTS The space required for files under the new file system is about the same as under 8.4D/C/B/A levels. However, it is recommended that a listing be obtained which displays the files and their new sizes. On the 8.4D release, the program FILESIZE is used to produce this listing. The program FILESIZE will display the file size under the new file system for each file in a given family. It will also display the total number of sectors required by the entire family under the new file system. .4.2.4. SAVING FILES TO TAPE User files and the .SYSDATA. node must now be backed up to tape. It is STRONGLY recommended that these files be saved to tape even if disk to disk conversion is being used. This will allow recovery of files in case there are problems with the disk to disk conversion. It is necessary to save the .SYSDATA. node to preserve all system parameters. This node must be restored on the new file system along with the user files. It is essential that the .SYSDATA.SECURITY.DATA file be backed up before upgrading to 8.6G and saved for a period of time on tape. This SECURITY.DATA file will go through a conversion during the upgrade, and the converted file cannot be used on previous O.S. levels. The old version of SECURITY.DATA should be kept in case you need to perform an O.S. downgrade. The files are saved using the standard tape utility, SAVERESTORE. When saving files to tape, send the output from the save process to the printer. These will provide a record of backup for each file. Also it is recommended that all tapes be SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg047 compared to the files on the disk. When using the tape or disk conversion, the conversion requires temporary disk space to sort keyed (direct and sort) files. The space required varies with the number of records and the size of the key. To ensure proper space is available, the following steps should be observed: A) Do not restore the user default family until last. B) Convert large keyed files first. Step A ensures that the default user disk has a large amount of free space since this is where the tape and disk conversion utility defines the temporary files. Step B allows the files that require the most amount of temporary space to be converted first. To convert large keyed files first, they must be saved to tape first. The large keyed files can be identified by scanning the directory listing obtained in section 5.4.2.2. If using disk to disk conversion, the NFSCONVERT utility allows you to convert keyed files first. 5.4.3. OPERATING SYSTEM UPDATE and FILE CONVERSION 5.4.3.1. INSTALLING THE O.S. .4.3.1.1. LOADING SLOTS 0 AND 1 USING ALT LOAD NOTE: As of releases 9/8.6C, positioning of the O.S./WCS slots has been adjusted slightly. Therefore, O.S. levels previous to 9/8.6C cannot reside in slots on the same disk with O.S. levels 9/8.6C and above. For this reason, ALT LOAD has been enhanced so that it will automatically load both slots 0 and 1 if one of the following three conditions is true: 1) You are upgrading from a release prior to 9/8.6C. 2) You are changing a DATA disk to a SYSTEM disk. If any of the above three conditions are true, WCS slots 2 and 3 are also loaded with the BOSS/VS WCS for formatting purposes only. The user needs to reload these slots with the REMIDI WCS files, using UPDATE.WCS. See the sections on updating slots 2 and 3 in this announcement. If you are upgrading to 10/9/8.6G from 9/8.6E, or if you are reinstalling 10/9/8.6G (over itself), the ALT LOAD procedure must be run twice - once to load O.S. and WCS slots 0, and once to load O.S. and WCS slots 1. To perform an ALT LOAD from tape follow these steps: A) Mount the new release tape in the tape drive. (All front panel load select switches should be OFF if using tape drive 0. Switch 1 should be ON if using tape drive 1.) B) Press the "ALT LOAD" button on the front panel. First, a proprietary message will be displayed, and then the following load screen: SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg048 ____________________________________________________________________ Load PROM Version: x.x.x.x SYSTEM SERIAL NUMBER : 000-00000 Load Drive n SERIAL NUMBER CREATOR: 000-00000 WCS 0 Version: x.x.x CONFIGURATION CREATOR: 000-00000 OS 0 Version: 6.7.x.x CPUs ID #s : n Memory (Mb) : n.0 Disk Drives : n BOSS/VS LOAD FROM TAPE Tape Drives : n Printers : n HVDTs : n IMLCs : n Serial Ports: n Date Format MM/DD/YY: BMTCs : n/n DATE = MM/DD/YY: LAN Cntrlrs : n TIME = HH:MM:SS: SYSTEM PREFIX: (family).R6Gxx.SYS. System Default Family: (family) File System Write Thru: T/F User Default Family : (family) Per-File Write Through: T/F Installation Name : (name) File System Security : T/F ____________________________________________________________________ Key in the current DATE and TIME at the above prompts. The screen will then display: ____________________________________________________________________ L O A D I N G . . . BOSS/VS Operating System Image Update Utility [version 6.5.x.x] OS/WCS information for drive n (nn): 0: ?????????????? ??????? | x x.x.x 1: ?????????????? ??.??.??.??? | ? ??.??.?? 2: -------------- -- -- -- --- | ????????? 3: ?????????????? ??????? | ????????? BOSS/VS Image File Name: (displays one of the following): OSN.CT0607xxxxx (ADVANCED SERIES) OSN.AT0607xxxxx (9x00 systems - 1/2-inch) OSN.AC0607xxxxx (9400 systems - 1/4-inch) OSN.BT0607xxxxx (8000 systems - 1/2-inch) OSN.BC0607xxxxx (7x00 systems - 1/4-inch) Target OS Slot (0/1/3) : '0' (or 1) Target WCS Slot (0-3) : '0' (or 1) Target Drives (0/1/All/Quit): (choose drive) ____________________________________________________________________ C) The Image File Name will be displayed by the system. Enter '0' or '1' at the slot prompts to load O.S. and WCS slots 0 and 1. Enter '0', '1', or 'All' at the drive prompt to update the appropriate drives. NOTE: Do not update drive 1 if it is a DATA disk and is to remain so. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg049 The system will now display: ___________________________________________________________________ Now updating WCS slot # n Update in progress: nn% Now updating BOSS/VS Image (displays one of the following): OSN.CT0607xxxxx (ADVANCED SERIES) OSN.AT0607xxxxx (9x00 systems - 1/2-inch) OSN.AC0607xxxxx (9400 systems - 1/4-inch) OSN.BT0607xxxxx (8000 systems - 1/2-inch) OSN.BC0607xxxxx (7x00 systems - 1/4-inch) Update in progress: nn% Image slot directory n/n:n Updates all complete. D O N E - R E A D Y F O R N O R M A L D I S K L O A D _______________________________________________________________ If you are upgrading to 10/9/8.6G from 9/8.6E or from another star ("*") level of 10/9/8.6G, repeat this procedure for O.S. and WCS slots 1. When O.S. and WCS slots 0 and 1 have been updated, reload the system by pressing the LOAD switch. 5.4.3.1.2. TYPE 3 LOAD (SPECIAL FUNCTIONS) NOTE 1: When using NFSCONVERT, the following steps should only be performed on the destination disk (which will be in the new File System format). NOTE 2: If any disk has a 'MASTER' status, no update to the disk will be allowed. You must change the disk to a 'BACKUP' status in order to perform the TYPE 3 LOAD functions. To do this, select OPTION 4 (CHANGE MASTER/BACKUP STATUS) from the TYPE 3 LOAD main menu. Be sure to change the disk back to a 'MASTER' status after the TYPE 3 LOAD functions are completed (if this status is desired). This MASTER/BACKUP status is simply a flag which makes it possible to write-protect a disk. It is not to be confused with the disk configuration (e.g., SYSTEM, DATA, BACKUP) specified in Option 1 (Change Volume Label Information) of INITIALIZATION OPTIONS (OPTION 2 on the TYPE 3 LOAD main menu). OPTION 2 - INITIALIZATION OPTIONS INITIALIZATION OPTIONS 1-4 must be done to insure proper operation. Option 1 must be done for all disks. Options 2 and 3 must be done for all disks. Option 4 must be done for system disk. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg050 .4.3.1.2.1. OPTION 1 (CHANGE VOLUME LABEL INFORMATION) All available disk drives will be displayed. An 'available' drive is any drive cabled to the system, whether enabled, disabled, in powered ON or OFF. The selected drive entered in response to the Option 1 prompts must be online and ready. ENTER DRIVE NUMBER OF VOLUME LABEL TO CHANGE:__ (The screen will change to display the information for only the drive whose volume label you choose.) SERIAL NUMBER _________ (Enter CR to accept current serial number.) DISK CONFIGURATION (1=SYSTEM, 2=DATA, 3=BACKUP) ____ (Enter the appropriate disk type.) SIZE OF DUMP AREA.....______ x 1024 BYTES (For system disks only, enter the size of the dump area displayed on the line below this prompt as the area needed for both main memory and shared memory controllers. If installation of additional memory and/or shared memory controllers is planned, increase the dump area size to accommodate them. See Field Bulletin # 211, "Computing Dump Area Size".) FILE SYSTEM SPACE ______ x 1000 SECTORS (Enter the number displayed at the bottom of the screen for this prompt. The display will appear as "CR=X" where X is the maximum space allowed.) UPDATE DISK VOLUME LABEL (Y/N) __ (Enter "Y" if above information is correct.) .4.3.1.2.2. OPTION 2 (UPDATE FAMILY INFORMATION) The disk information for all drives on the system is displayed and the cursor is positioned at 'FAMILY BASE DRIVE NUMBER'. FAMILY BASE DRIVE NUMBER ___ FAMILY NAME ______ (CR for default family name.) DRIVE NUMBERS OF OTHER DISKS IN FAMILY? (TYPE SPACES FOR NO OTHER DRIVES) (Enter all other drive numbers for this family or spaces if none. The drives must be fixed media drives and in new file system format.) UPDATE DISK (Y/N)? .4.3.1.2.3. OPTION 3 (INITIALIZE FAMILY DIRECTORY) This option displays all family base drives on the system. FAMILY BASE DRIVE NUMBER ______ (Enter drive number to be initialized.) INITIALIZE FAMILY? (Y/N) __ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg051 .4.3.1.2.4. OPTION 4 (CHANGE INSTALLATION PARAMETERS) Only system disks will be displayed. DRIVE NUMBER _______ PRIMARY PREFIX __________________ (Enter (family).R6Gxx.SYS. (Family) is the family where the operating system files will reside.) SECONDARY PREFIX _______________ (Enter (family).R6Gxx.SYS. (Family) is the family where the alternate operating system files will reside.) SYSTEM INSTALLATION NAME ________________ (Sets the default installation name for a specified system disk.) DEFAULT USER FAMILY NAME _____________ (Enter default user family.) SECURITY (E=ENABLED, D=DISABLED) ___ FILE SYSTEM WRITE THROUGH? (E=ENABLED, D=DISABLED) ___ (For conversion purposes, set this option to 'D' for DISABLED. This will speed up the conversion process and can be changed later if needed.) WRITE THROUGH DEFAULT ON FILE CREATE (E=ENABLED, D=DISABLED):__ (This parameter specifies what the default write through will be on a file created through a BASIC file create or through the CREATE utility.) UPDATE DISK WITH INSTALLATION PARAMETERS? (Y/N) __ Display: INSTALLATION PARAMETERS SUCCESSFULLY WRITTEN TO DISK. (CR) TO CONTINUE: Reload the system by pressing the LOAD switch. 5.4.3.1.3. RESTORING THE O.S. Enter SAVERESTORE in a TYPE II load and choose option #2 "RESTORE FILES FROM TAPE". The screen appears as in Figure 5-2. (continued on next page) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg052 Figure 5-2. Restore Screen -------------------------------------------------------- RESTORE FILES TAPE SET.ID: DRIVE-NUM: REEL-NUM: PRIMARY PREFIX: (FAMILY).NODE. FILETYPE (D/P/CR=ALL) COMPARE (CR=Y/N) DATE (MM/DD/YY) TIME (HH:MM) OUTPUT DEVICE (CR=VDT) DELETE EXISTING FILES (CR=Y) VERIFY (Y/CR=N) ENTRIES CORRECT (Y/N) -------------------------------------------------------- At each prompt, enter a . At the prompt, "FILE SPECIFIERS", enter ".". Then enter twice. This will restore all the files on the release tape to disk. Please note that once all files are restored to disk, the message "AUTOMATIC COMPARE, CR TO CONTINUE" appears. This automatically rewinds the tape and begins the compare operation. This only occurs when the compare option is selected. When the compare is completed, enter a CTL-IV to return to the "SAVERESTORE" menu. 5.4.3.2. INSTALLING THE CONFIGURATION RECORD It is necessary to install a new configuration record when installing a new system disk and when upgrading to 10/9/8.6G from 8.4 and 8.5 O.S. levels or when changing system types. Until the following procedure is completed, the system will have a minimum configuration. Enter a TYPE 1 LOAD. Set your prefix to .SYSTEM.CONFIG. Before you load the new configuration record, rename the current configuration record on your system, using the RENAME utility, to temporarily preserve it for fall back purposes. (e.g. Add "OLD" in front of the name.) Using the SAVERESTORE utility, restore the new configuration record from tape onto your system. Execute the CONFIG.MGR utility. The CONFIG.MGR utility allows the user to update the system configuration record by installing a new configuration file. This utility displays the current and new configuration record. When "Y" is answered to the prompt "Install Configuration:", the new configuration is copied from the file ".SYSTEM.CONFIG.I (serial number)", to the special system area on disk. The new configuration takes effect at the next system load. For further details on the use of the CONFIG.MGR utility, see the SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg053 9.5D/8.5D Software Announcement #139, or the BOSS/VS UTILITY USER GUIDE, M5102. The configuration record file name is derived from the system serial number by changing the leading "8" to an "I" and adding the prefix ".SYSTEM.CONFIG.". EXAMPLE: .SYSTEM.CONFIG.I1030114 for SSN 810-30114 This configuration record tape should be saved, in case reinstallation should become necessary. Before going to the next step, LOAD the system so the new configuration record will take affect. If you do not load the system, you will have a minimum configuration and the system will be very slow. 5.4.3.3. CONVERTING FILES If doing tape to disk conversion see section 5.4.3.3.1. If doing disk to disk conversion see section 5.4.3.3.2. 5.4.3.3.1. TAPE TO DISK CONVERSION Mount the first tape to restore, enter the SAVERESTORE utility, and select option #2. A screen as in figure 5-2 will appear. Answer all prompts as in the figure. Make sure that you direct the output to a printer. This will provide you with a "history" of the restore operation. Each file is converted to the new file format as it is restored. The conversion to the new file format will be entirely invisible except for a pause at the completion of restoring a file. This pause, which can last a few seconds to a few hours depending on file size, indicates the file is being converted to the new file format. Occasionally the message "...CONVERTING FILE TO NFS..." will appear as a visual indicator of file conversion. System files from the previous release need not be restored. However, to preserve all system parameters, the .SYSDATA. node must be restored from the back- up tapes. Tapes made on releases of 8.4D and below cannot be compared when restored to the new file system. After all files have been restored, reload the system so the SECURITY.DATA file will be converted to the new 9/8.6G format and the terminal definition files will take effect. Now go to section 5.4.3.3.3. .4.3.3.2. DISK TO DISK CONVERSION The utility NFSCONVERT is used to convert files from the old format to the new file format. The destination disk must be in new file system format as described in section 5.4.3.1.2. The source disk must be in the old file system format. When using disk to disk conversion, only one family may be converted per terminal. You cannot start NFSCONVERT on two terminals converting different parts of the same family, however you can convert different families at the same time. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg054 As in the tape to disk conversion, the .SYSDATA. node must be converted to preserve system parameters and configurations. .4.3.3.3. CHECK FILES Once all files have been converted, the DISKANALYZER "VALIDATE ALL FILES" option should be performed on each family. DISKANALYZER can be used in a TYPE II load or a TYPE I load. Once all files have been validated, enter a TYPE I load, (if you have not already done so). 5.4.4. UPDATING THE TERMINAL CONFIGURATION FILE The terminal configuration file must be updated to the new file system format. This update will allow all other devices to become accessible. The file is updated by entering TERM.CONFIG and choosing the update option. Enter PRIMARY as the file to change. Enter an existing ISDC and display one of the ISDC ports. Enter a MB-IV to exit the update without changing anything. The utility will say that the file has been modified and ask if you want to save it. Respond with YES. Now reload the system to allow the devices to become active. Now go to section 5.5.4 to complete the last step of the installation. 7xxx/8xxx UPGRADE AND CONVERSION CHECKLIST 1) Hardware levels => section 4 2) Validate files => section 5.4.2.2 A) DISKANALYZER option "VALIDATE ALL FILES" B) DIR listings C) FINDLOSTSPACE Utility D) Delete unwanted EDITOR, SPOOL, and TEMP files 3) New file sizes => section 5.4.2.3 A) FILESIZE utility 4) Save files to tape => section 5.4.2.4 A) Large keyed files first 5) Update operating system => section 5.4.3.1 A) ALT-LOAD B) Options 1-4 C) Restore operating system files 6) File conversion A) Tape-to-disk => section 5.4.3.3.1 B) Disk-to-disk => section 5.4.3.3.2 7) Check file integrity => section 5.4.3.3.3 8) Complete installation SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg055 A) Update terminal configuration file => section 5.4.4 B) Update slots 2 and 3 => section 5.5.4 5.5. UPGRADING TO 8.6G FROM RELEASE LEVELS 8.4E AND ABOVE If you are installing the 8.6G O.S. on a newly formatted System disk or changing a Data disk to a System disk, go to section 5.3. .5.1. SAVING FILES TO TAPE Current files must first be backed up to tape, using the standard tape utility, SAVERESTORE. When saving files to tape, send the output from the save process to the printer. This will provide a record of backup for each file. Also, it is recommended that all files on tape be compared to the files on the disk. NOTE: It is essential that the .SYSDATA.SECURITY.DATA file be backed up before upgrading to 8.6G, if your current O.S. level is below 8.6C. This SECURITY.DATA file will go through a conversion during the upgrade, and the converted file cannot be used on previous O.S. levels. The old version of SECURITY.DATA should be saved in case an O.S. downgrade is ever necessary. 5.5.2. OPERATING SYSTEM UPDATE 5.5.2.1. LOADING SLOTS 0 AND 1 USING ALT LOAD NOTE: As of releases 9/8.6C, positioning of the O.S./WCS slots has been adjusted slightly. Therefore, O.S. levels previous to 9/8.6C cannot reside in slots on the same disk with O.S. levels 9/8.6C and above. For this reason, ALT LOAD has been enhanced so that it will automatically load both slots 0 and 1 if one of the following three conditions are true: 1) You are upgrading from a release prior to 9/8.6C 2) You are changing a DATA disk to a SYSTEM disk If any of the above three conditions are true, WCS slots 2 and 3 are also loaded with the BOSS/VS WCS for formatting purposes ly. The user needs to reload these slots with the REMIDI WCS S files, using UPDATE.WCS. See the sections on updating slots 2 and 3 in this announcement. If you are upgrading to 10/9/8.6G from 9/8.6C, or if you are reinstalling 10/9/8.6G (over itself), the ALT LOAD procedure must be run twice - once to load O.S. and WCS slots 0, and once to load O.S. and WCS slots 1. To perform an ALT LOAD from tape; follow these steps: A) Mount the new release tape in the tape drive. (All front panel load select switches should be OFF if using tape drive 0. Switch 1 should be ON if using tape drive 1.) B) Prs the "ALT LOAD" button on the front panel. First, a proprietary message will be displayed, and then the following load screen: (continued on next page) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg056 ____________________________________________________________________ Load PROM Version: x.x.x.x SYSTEM SERIAL NUMBER : 000-00000 Load Drive n SERIAL NUMBER CREATOR: 000-00000 WCS 0 Version: x.x.x CONFIGURATION CREATOR: 000-00000 OS 0 Version: 6.7.x.x CPUs ID #s : n Memory (Mb) : n.0 Disk Drives : n BOSS/VS LOAD FROM TAPE Tape Drives : n Printers : n HVDTs : n IMLCs : n Serial Ports: n Date Format MM/DD/YY: BMTCs : n/n DATE = MM/DD/YY: LAN Cntrlrs : n TIME = HH:MM:SS: SYSTEM PREFIX: (family).R6Gxx.SYS. System Default Family: (family) File System Write Thru: T/F User Default Family : (family) Per-File Write Through: T/F Installation Name : (name) File System Security : T/F Key in the current DATE and TIME at the above prompts. The screen will then display: ____________________________________________________________________ L O A D I N G . . . BOSS/VS Operating System Image Update Utility [version 6.5.x.x] OS/WCS information for drive n (nn): 0: ?????????????? ??????? |x x.x.x 1: ?????????????? ??.??.??.??? |? ??.??.?? 2: -------------- -- -- -- --- | ????????? 3: ?????????????? ??????? | ????????? BOSS/VS Image File Name: (displays one of the following): OSN.CT0607xxxxx (ADVANCED SERIES) OSN.AT0607xxxxx (9x00 systems - 1/2-inch) OSN.AC0607xxxxx (9400 systems - 1/4-inch) OSN.BT0607xxxxx (8000 systems - 1/2-inch) OSN.BC0607xxxxx (7x00 systems - 1/4-inch) Target OS Slot (0/1/3) : '0' (or 1) Target WCS Slot (0-3) : '0' (or 1) Target Drives (0/1/All/Quit): (choose drive) ____________________________________________________________________ C) The Image File Name will be displayed by the system. Enter '0' or '1' at the slot prompts to load O.S. and WCS slots 0 and 1. Enter '0', '1', or 'All' at the drive prompt to update the appropriate drives. NOTE: Do not update drive 1 if it is a DATA disk and is to remain so. The system will now display: SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg057 ___________________________________________________________________ Now updating WCS slot # n Update in progress: nn% Now updating BOSS/VS Image (displays one of the following): OSN.CT0607xxxxx (ADVANCED SERIES) OSN.AT0607xxxxx (9x00 systems - 1/2-inch) OSN.AC0607xxxxx (9400 systems - 1/4-inch) OSN.BT0607xxxxx (8000 systems - 1/2-inch) OSN.BC0607xxxxx (7x00 systems - 1/4-inch) Update in progress: nn% Image slot directory n/n:n Updates all complete. D O N E - R E A D Y F O R N O R M A L D I S K L O A D ___________________________________________________________________ If you are upgrading to 10/9/8.6G from 9/8.6E or from another star ("*") level of 10/9/8.6G, repeat this procedure for O.S. and WCS slots 1. .5.2.2. CHANGING INSTALLATION PARAMETERS Enter a TYPE 3 LOAD (SPECIAL FUNCTIONS) and select OPTION 2 (INITIALIZATION OPTIONS). OPTION 2 - INITIALIZATION OPTIONS Option 4 - CHANGE INSTALLATION PARAMETERS Only system disks will be displayed. DRIVE NUMBER _______ PRIMARY PREFIX _______________________ (Enter (family).R6Gxx.SYS. (Family) is the family where the operating system files reside.) SECONDARY PREFIX _____________________ (Enter (family).R6Gxx.SYS. (Family) is the family where the alternate operating system files reside.) SYSTEM INSTALLATION NAME _________________________ (Sets the default installation name for a specified system disk.) DEFAULT USER FAMILY NAME ________ (Enter default user family.) SECURITY (E=ENABLED, D=DISABLED) ___ FILE SYSTEM WRITE THROUGH? (E=ENABLED, D=DISABLED) ___ WRITE THROUGH DEFAULT ON FILE CREATE (E=ENABLED, D=DISABLED) __ (This parameter specifies what the default write through will be on a file created through a BASIC file create or through the CREATE utility.) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg058 UPDATE DISK WITH INSTALLATION PARAMETERS? (Y/N)__ Display: INSTALLATION PARAMETERS SUCCESSFULLY WRITTEN TO DISK (CR) TO CONTINUE: Reload the system by pressing the LOAD switch. 5.5.2.3. RESTORING THE O.S. Enter SAVERESTORE in a TYPE 2 LOAD and choose OPTION 2 RESTORE FILES FROM TAPE. The screen appears as in figure 5-3. At the prompt, "FILE SPECIFIERS", enter ".". Then enter twice. This will restore all files on the release tape to disk. Figure 5-3. Restore Screen -------------------------------------------------------- RESTORE FILES TAPE SET.ID: DRIVE-NUM: REEL-NUM: PRIMARY PREFIX: (FAMILY).NODE. FILE TYPE (D/P/CR=ALL) COMPARE (CR=Y/N) DATE (MM/DD/YY) TIME (HH:MM) OUTPUT DEVICE (CR=VDT) DELETE EXISTING FILES (CR=Y) VERIFY (Y/CR=N) ENTRIES CORRECT (Y/N) -------------------------------------------------------- At each prompt, enter a . Please note that once all files are restored to disk, the message "AUTOMATIC COMPARE, CR TO CONTINUE" appears. This automatically rewinds the tape and begins the compare operation. This only occurs when the compare option is selected. When the compare is completed, enter a CTL-IV to return to the "SAVERESTORE" menu. 5.5.3. INSTALLING THE CONFIGURATION RECORD It is necessary to install a new configuration record when installing a new system disk and when upgrading to 10/9/8.6G from 8.4 and 8.5 O.S. levels. Until the following procedure is completed, the system will have a minimum configuration. Enter a TYPE 1 LOAD. Set your prefix to .SYSTEM.CONFIG. Before you load the new configuration record, rename the current configuration record on your system, using the RENAME utility, to temporarily preserve it for fall back purposes. (e.g. Add "OLD" in front of the name.) Using the SAVERESTORE utility, restore the new configuration record from tape onto your system. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg059 Execute the CONFIG.MGR utility. The CONFIG.MGR utility allows the user to update the system configuration record by installing a new configuration file. This utility displays the current and new configuration record. When "Y" is answered to the prompt "Install Configuration:", the new configuration is copied from the file ".SYSTEM.CONFIG.I(serial number)", to the special system area on disk. The new configuration takes effect at the next system load. For further details on the use of the CONFIG.MGR utility, see the 9.5D/8.5D Software Announcement #139, or the BOSS/VS UTILITY USER GUIDE, M5102. The configuration record file name is derived from the system serial number by changing the leading "8" to an "I" and adding the prefix ".SYSTEM.CONFIG.". EXAMPLE: .SYSTEM.CONFIG.I1030114 for SSN 810-30114 This configuration record tape should be saved, in case reinstallation should become necessary. Before going to the next step, LOAD the system so the new configuration record will take affect. If you do not load the system, you will have a minimum configuration and the system will be very slow. 5.5.4. UPDATING SLOTS 2 AND 3 ON 7xxx and 8xxx SYSTEMS NOTE: If question marks (?/?) ever appear for Load Sector 2 at the top of the OSINFO screen, it is necessary to run UPDATE.LD for REMIDI. See section 3.3.1 for further information on REMIDI and UPDATE.LD. O.S. and WCS slots 2 and 3 are updated by using the UPDATE.OS and UPDATE.WCS utilities in a TYPE 1 LOAD. To run these utilities, you must set your prefix to the .R6Gxx.DIAG. node. 5.5.4.1. UPDATING WCS SLOT TWO (2) REMIDI version BV includes all the micro-diagnostics except MPC and LAN controller micro-diagnostics. It is placed in WCS slot 2 and is used for testing on all 7000/7100 and 8000 Series Systems. !UPDATE.WCS ENTER WCS SLOT (0..3): '2' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE: (choose disk) WCS IMAGE FILE: .R6Gxx.DIAG.REMIDI.BV WCS LEVEL OF WCS IMAGE FILE: (level displayed) UPDATING DISK UNIT nn SECTOR xxx WCS UPDATE COMPLETED! 5.5.4.2. UPDATING SLOT THREE (3) 5.5.4.2.1. UPDATING WCS SLOT THREE (3) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg060 .5.4.2.1.1. ON 7000/7100 SYSTEMS AND 8000 SYSTEMS WITH LAN REMIDI version BVM contains micro-diagnostics for the LAN and MPC controllers. It is placed in WCS slot 3 on 7000/7100 Series Systems and on 8000 Series Systems with LAN controllers. The utility UPDATE.LD is used to update the Load Directory for Load Sector 2 to toggle between the two versions of REMIDI in WCS slots 2 and 3. The pointers in Load Sector 2 (displayed on the OSINFO screen) determine which diagnostics will run. See section 3.3.1 for further information on REMIDI and UPDATE.LD. !UPDATE.WCS ENTER WCS SLOT (0..3): '3' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R6Gxx.DIAG.REMIDI.BVM WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE! .5.4.2.1.2. ON 8000 SYSTEMS WITHOUT LAN This slot will contain system WCS which is common to both the O.S. and DEMON. !UPDATE.WCS ENTER WCS SLOT (0..3): '3' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R6Gxx.DIAG.WCS.B WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 5.5.4.2.2. UPDATING O.S. SLOT THREE (3) The O.S. slot 3 will contain the O.S. for DEMON on both 7000/7100 and 8000 Series Systems. !UPDATE.OS BOSS/VS Image File Name: .R6Gxx.DIAG.DEMON.UV Target OS Slot (0/1/3) : '3' Target WCS Slot (0-3) : '0' Target Drives (0/1/All/Quit): (choose drive) NOTE: A '0' is entered for the WCS slot to associate DEMON's O.S. with the WCS in slot 0. DEMON and the 8.6G O.S. share the same WCS. The system will now display: Update in progress: nn% Image slot directory n/n:n SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg061 Updates all complete. 5.5.5. SLOT INFORMATION Once all slots have been updated, use the utility OSINFO to display the slot information. The information should be similar to figure 5-4. This operating system installation procedure must be performed on all system disks. If disk 1 is a system disk also, repeat the operating system installation procedure for this disk. Figure 5-4. Operating System Information OPERATING SYSTEM INFORMATION ------------------------------------------------------------------ BOOT LEVEL : X.X.X.X LOAD SECTOR: 0 1 2 3 DISK 0 : 0/0 1/1 0/2 3/3 SERIAL # : XXX-XXXXX ------------------------------------------------------------------ OS NAME OS LEVEL DISK:SLOT WCS LEVEL ------------------------------------------------------------------ R 6G*xx xxxxxx 6.7.x.x 0:0 B x.x.x R 6G*xx xxxxxx 6.7.x.x 0:1 B x.x.x N/A 0:2 REMIDI B x.x.x DEMON 6.7.x.x 0:3 B x.x.x ------------------------------------------------------------------ NOTE: OSINFO on 7000/7100 Series Systems and 8000 Series Systems with LAN will show the additional version of REMIDI in WCS slot 3. The load sector 3 should be 3/0 on these systems. 5.6. UPGRADING TO 9.6G .6.1. SPECIAL CONSIDERATIONS If you are installing the 9.6G O.S. on a newly formatted System disk or changing a Data disk to a System disk, go to section 5.3. If you are upgrading a 7xxx or 8xxx Series System to a 9xxx Series System, you must first run for a minimum of one week on O.S. 8.6A or above before the hardware upgrade. A new configuration record is required when upgrading to 9.6G from 9.5 O.S. levels. A new configuration record is also required when an upgrade includes new hardware. .6.2. PRINTING OUT THE TERMINAL CONFIGURATION INFORMATION Skip this section if you are upgrading to 9.6G from 9.6A/B/C/E or 9.5. When upgrading from MPx 7xxx/8xxx Series Systems to the MPx 9xxx Series Systems, it is necessary to reference the terminal configuration in order to properly re-address the 9xxx controllers. Therefore, you must print out a copy of the terminal configuration information before upgrading. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg062 1. Enter the TERM.CONFIG utility. 2. Select OPTION 2 DISPLAY A CONFIGURATION FILE. 3. When the following screen is displayed, enter these responses to the prompts: CONFIGURATION FILE: P OUTPUT DEVICE: DETAILED REPORT: Y ENTRIES CORRECT: Y The terminal configuration information should now be printed. 5.6.3. SAVING FILES TO TAPE Current files must first be backed up to tape, using the standard tape utility, SAVERESTORE. When saving files to tape, send the output from the save process to the printer. This will provide a record of backup for each file. Also it is recommended that all tapes be compared to the files on the disk. NOTE: It is essential that the .SYSDATA.SECURITY.DATA file be backed up before upgrading to 9.6G, if your current O.S. level is below 9.6C. This SECURITY.DATA file will go through a conversion during the upgrade, and the converted file cannot be used on previous O.S. levels. The old version of SECURITY.DATA should be saved in case an O.S. downgrade is ever necessary. 5.6.4. OPERATING SYSTEM UPDATE 5.6.4.1. LOADING SLOTS 0 AND 1 USING ALT LOAD NOTE: As of releases 9/8.6C, positioning of the O.S./WCS slots has been adjusted slightly. Therefore, O.S. levels previous to 9/8.6C cannot reside in slots on the same disk with O.S. levels 9/8.6C and above. For this reason, ALT LOAD has been enhanced so that it will automatically load both slots 0 and 1 if one of the following three conditions is true: 1) You are upgrading from a release prior to 9/8.6C. 2) You are changing a DATA disk to a SYSTEM disk. If any of the above three conditions are true, WCS slots 2 and 3 are also loaded with the BOSS/VS WCS for formatting purposes only. The user needs to reload these slots with the REMIDI WCS files, using UPDATE.WCS. See the sections on updating slots 2 and 3 in this announcement. If you are upgrading to 10/9/8.6G from 9/8.6E, or if you are reinstalling 10/9/8.6G (over itself), the ALT LOAD procedure must be run twice - once to load O.S. and WCS slots 0, and once to load O.S. and WCS slots 1. To perform an ALT LOAD from tape, follow these steps: A) Mount the new release tape in the tape drive. (All front panel load select switches should be OFF if using tape drive 0. Switch 1 should be ON if using tape drive 1.) B) Press the "ALT LOAD" button on the front panel. First, a proprietary message will be displayed, and then the following load screen: SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg063 ____________________________________________________________________ Load PROM Version: x.x.x.x SYSTEM SERIAL NUMBER : 000-00000 Load Drive n SERIAL NUMBER CREATOR: 000-00000 WCS 0 Version: x.x.x CONFIGURATION CREATOR: 000-00000 OS 0 Version: 6.5.x.x CPUs ID #s : n Memory (Mb) : n.0 Disk Drives : n BOSS/VS LOAD FROM TAPE Tape Drives : n Printers : n HVDTs : n IMLCs : n Serial Ports: n Date Format MM/DD/YY: BMTCs : n/n DATE = MM/DD/YY: LAN Cntrlrs : n TIME = HH:MM:SS: SYSTEM PREFIX: (family).R6Gxx.SYS.,.R6Gxx.INST. System Default Family: (family) File System Write Thru: T/F User Default Family : (family) Per-File Write Through: T/F Installation Name : (name) File System Security : T/F ____________________________________________________________________ Key in the current DATE and TIME at the above prompts. The screen will then display: ____________________________________________________________________ L O A D I N G . . . BOSS/VS Operating System Image Update Utility [version 6.5.x.x] OS/WCS information for drive n (nn): 0: ?????????????? ??????? | x x.x.x 1: ?????????????? ??.??.??.??? | ? ??.??.?? 2: -------------- -- -- -- --- | ????????? 3: ?????????????? ??????? | ????????? BOSS/VS Image File Name: (displays one of the following): OSN.CT0607xxxxx (ADVANCED SERIES) OSN.AT0607xxxxx (9x00 systems - 1/2-inch) OSN.AC0607xxxxx (9400 systems - 1/4-inch) OSN.BT0607xxxxx (8000 systems - 1/2-inch) OSN.BC0607xxxxx (7x00 systems - 1/4-inch) Target OS Slot (0/1/3) : '0' (or 1) Target WCS Slot (0-3) : '0' (or 1) Target Drives (0/1/All/Quit): (choose drive) ____________________________________________________________________ C) The Image File Name will be displayed by the system. Enter '0' or '1' at the slot prompts to load O.S. and WCS slots 0 and 1. Enter '0', '1', or 'All' at the drive prompt to update the appropriate drives. NOTE: Do not update drive 1 if it is a DATA disk and is to remain so. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg064 The system will now display: ________________________________________________________________ Now updating WCS slot # n Update in progress: nn% Now updating BOSS/VS Image (displays one of the following): OSN.CT0607xxxxx (ADVANCED SERIES) OSN.AT0607xxxxx (9x00 systems - 1/2-inch) OSN.AC0607xxxxx (9400 systems - 1/4-inch) OSN.BT0607xxxxx (8000 systems - 1/2-inch) OSN.BC0607xxxxx (7x00 systems - 1/4-inch) Update in progress: nn% Image slot directory n/n:n Updates all complete. D O N E - R E A D Y F O R N O R M A L D I S K L O A D _______________________________________________________________ If you are upgrading to 10/9/8.6G from 9/8.6E or from another star ("*") level of 10/9/8.6G, repeat this procedure for O.S. and WCS slots 1. When O.S. and WCS slots 0 and 1 have been updated, reload the system by pressing the LOAD switch. 5.6.4.2. CHANGING INSTALLATION PARAMETERS Enter a TYPE 3 LOAD (SPECIAL FUNCTIONS) and select OPTION 2 (INITIALIZATION OPTIONS). OPTION 2 - INITIALIZATION OPTIONS Option 4 - CHANGE INSTALLATION PARAMETERS Only system disks will be displayed. DRIVE NUMBER _______ PRIMARY PREFIX _______________________ (Enter (family).R6Gxx.SYS. (Family) is the family where the operating system files reside.) SECONDARY PREFIX _____________________ (Enter (family).R6Gxx.SYS. (Family) is the family where the alternate operating system files reside.) SYSTEM INSTALLATION NAME _________________________ (Sets the default installation name for a specified system disk.) DEFAULT USER FAMILY NAME ________ (Enter default user family.) SECURITY (E=ENABLED, D=DISABLED) ___ FILE SYSTEM WRITE THROUGH? (E=ENABLED, D=DISABLED) ___ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg065 WRITE THROUGH DEFAULT ON FILE CREATE (E=ENABLED, D=DISABLED) __ (This parameter specifies what the default write through will be on a file created through a BASIC file create or through the CREATE utility.) UPDATE DISK WITH INSTALLATION PARAMETERS? (Y/N)__ Display: INSTALLATION PARAMETERS SUCCESSFULLY WRITTEN TO DISK (CR) TO CONTINUE: Reload the system by pressing the LOAD switch. Be sure to load the system from the disk where you wish to restore the operating system files. 5.6.4.3. RESTORING THE O.S. FILES Enter SAVERESTORE in a TYPE 2 LOAD and choose OPTION 2 RESTORE FILES FROM TAPE. The screen appears as in figure 5-5. Figure 5-5. Restore Screen -------------------------------------------------------- RESTORE FILES TAPE SET.ID: DRIVE-NUM: REEL-NUM: PRIMARY PREFIX: (FAMILY).NODE. FILE TYPE (D/P/CR=ALL) COMPARE (CR=Y/N) DATE (MM/DD/YY) TIME (HH:MM) OUTPUT DEVICE (CR=VDT) DELETE EXISTING FILES (CR=Y) VERIFY (Y/CR=N) ENTRIES CORRECT (Y/N) -------------------------------------------------------- At each prompt, enter a . At the prompt, "FILE SPECIFIERS", enter ".". Then enter twice. This will restore all files on the release tape to disk. Please note that once all files are restored to disk, the message "AUTOMATIC COMPARE, CR TO CONTINUE" appears. This automatically rewinds the tape and begins the compare operation. This only occurs when the compare option is selected. When the compare is completed, enter a CTL-IV to return to the "SAVERESTORE" menu. 5.6.5. INSTALLING THE CONFIGURATION RECORD It is necessary to install a new configuration record when upgrading to 9.6G from 8.4, 8.5 and 9.5 release levels. Until the following procedure is completed, the system will have a minimum configuration. Enter a TYPE 1 LOAD. Set your prefix to .SYSTEM.CONFIG. Before you load the new configuration record, rename the current SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg066 configuration record on your system, using the RENAME utility, to temporarily preserve it for fall back purposes. (e.g. ".OLDCONFIG.") Using the SAVERESTORE utility, restore the new configuration record from tape onto your system. Execute the CONFIG.MGR utility. The CONFIG.MGR utility allows the user to update the system configuration record by installing a new configuration file. This utility displays the current and new configuration record. When "Y" is answered to the prompt "Install Configuration:", the new configuration is copied from the file ".SYSTEM.CONFIG.I(serial number)", to the special system area on disk. The new configuration takes effect at the next system load. For further details on the use of the CONFIG.MGR utility, see the 8.5D/9.5D Software Announcement #139, or the BOSS/VS UTILITY USER GUIDE, M5102. The configuration record file name is derived from the system serial number by changing the leading "8" to an "I" and adding the prefix ".SYSTEM.CONFIG.". EXAMPLE: .SYSTEM.CONFIG.I1030114 for SSN 810-30114 This configuration record tape should be saved, in case reinstallation should become necessary. After installing the new configuration record, LOAD the system. Otherwise your system will be at minimum configuration and will be extremely slow. 5.6.6. UPDATING SLOTS 2 AND 3 ON MPx 9xxx SERIES SYSTEMS O.S. and WCS slots 2 and 3 are updated by using the UPDATE.OS' and UPDATE.WCS utilities in a TYPE 1 LOAD. To run these utilities, you must set your prefix to the .R6Gxx.DIAG. node. 5.6.6.1. UPDATING WCS SLOT TWO (2) The first section of the 9xxx version of REMIDI will reside in this slot. !UPDATE.WCS ENTER WCS SLOT (0..3): '2' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE: (choose disk) WCS IMAGE FILE: .R6Gxx.DIAG.REMIDI.AVA WCS LEVEL OF WCS IMAGE FILE: (level displayed) UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETED! 5.6.6.2. UPDATING WCS SLOT THREE (3) The second section of the 9xxx version of REMIDI will reside in this slot. !UPDATE.WCS SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg067 ENTER WCS SLOT (0..3): '3' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R6Gxx.DIAG.REMIDI.AVC WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE! NOTE: After REMIDI has been installed, Load Sector 2 at the top of the OSINFO screen should reflect an O.S./WCS of 0/2. If 0/2 is not displayed for Load Sector 2, UPDATE.LD must be run to update the Load Directory. See section 3.3.1.2 for instructions on how to do this. 5.6.6.3. UPDATING O.S. SLOT THREE (3) O.S. slot 3 will contain the O.S. for DEMON. !UPDATE.OS BOSS/VS Image File Name: .R6Gxx.DIAG.DEMON.UV Target OS Slot (0/1/3) : '3' Target WCS Slot (0-3) : '0' Target Drives (0/1/All/Quit): (choose drive) NOTE: A '0' is entered for the WCS slot to associate DEMON's O.S. with the WCS in slot 0. DEMON and the 10/9/8.6G O.S. share the same WCS. The system will now display: Update in progress: nn% Image slot directory n/n:n Updates all complete. If drive 1 is a system disk also, the operating system installation procedure must be repeated for this disk. 5.6.7. SLOT INFORMATION Once all slots have been updated, use the utility OSINFO to display the slot information. The information should be similar to figure 5-6. Figure 5-6. Operating System Information OPERATING SYSTEM INFORMATION --------------------------------------------------------------- BOOT LEVEL : X.X.X.X LOAD SECTOR: 0 1 2 3 DISK 0 : 0/0 1/1 0/2 3/0 SERIAL # : XXX-XXXXX --------------------------------------------------------------- OS NAME OS LEVEL DISK:SLOT WCS LEVEL --------------------------------------------------------------- R 6G*xx xxxxxx 6.7.x.x 0:0 A x.x.x R 6G*xx xxxxxx 6.7.x.x 0:1 A x.x.x N/A 0:2 REMIDI A x.x.x DEMON 6.7.x.x 0:3 REMIDI A x.x.x --------------------------------------------------------------- Installation is now complete. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg068 5.7. UPGRADING TO 10.6G AND THE ADVANCED SERIES 5.7.1. SPECIAL CONSIDERATIONS If you are installing the 10.6G O.S. on a newly formatted System disk or changing a Data disk to a System disk, go to section 5.3. 5.7.2. SAVING FILES TO TAPE Current files must first be backed up to tape, using the standard tape utility, SAVERESTORE. When saving files to tape, send the output from the save process to the printer. This will provide a record of backup for each file. Also it is recommended that all tapes be compared to the files on the disk. NOTE: It is essential that the .SYSDATA.SECURITY.DATA file be backed up before upgrading to 10.6G, if your current O.S. level is below 9.6C. This SECURITY.DATA file will go through a conversion during the upgrade, and the converted file cannot be used on previous O.S. levels. The old version of SECURITY.DATA should be saved in case an O.S. downgrade is ever necessary. 5.7.3. OPERATING SYSTEM UPDATE .7.3.1. LOADING SLOTS 0 AND 1 USING ALT LOAD NOTE: As of releases 9/8.6C, positioning of the O.S./WCS slots has been adjusted slightly. Therefore, O.S. levels previous to 9/8.6C cannot reside in slots on the same disk with O.S. levels 9/8.6C and above. For this reason, ALT LOAD has been enhanced so that it will automatically load both slots 0 and 1 if one of the folwing twoee conditions is true: 1) You are upgrading from a release prior to 9/8.6C. 2) You are changing a DATA disk to a SYSTEM disk. If any of the above three conditions are true, WCS slots 2 and 3 are also loaded with the BOSS/VS WCS for formatting purposes only. The user needs to reload these slots with the REMIDI WCS files, using UPDATE.WCS. See the sections on updating slots 2 and 3 in this announcement. If you are upgrading to 10/9/8.6G from 9/8.6E, or if you are reinstalling 10/9/8.6G (over itself), the ALT LOAD procedure must be run twice - once to load O.S. and WCS slots 0, and once to load O.S. and WCS slots 1. To perform an ALT LOAD from tape follow these steps: A) Mount the new release tape in the tape drive. (All front panel load select switches should be OFF if using tape drive 0. Switch 1 should be ON if using tape drive 1.) B) Press the "ALT LOAD" button on the front panel. First, a proprietary message will be displayed, and then the following load screen: SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg069 ___________________________________________________________________ Load PROM Version: x.x.x.x SYSTEM SERIAL NUMBER : 000-00000 Load Drive n SERIAL NUMBER CREATOR: 000-00000 WCS 0 Version: x.x.x CONFIGURATION CREATOR: 000-00000 OS 0 Version: 6.7.x.x CPUs ID #s : n Memory (Mb) : n.0 Disk Drives : n BOSS/VS LOAD FROM TAPE Tape Drives : n Printers : n HVDTs : n IMLCs : n Serial Ports: n Date Format MM/DD/YY: BMTCs : n/n DATE = MM/DD/YY: LAN Cntrlrs : n TIME = HH:MM:SS: SYSTEM PREFIX: (family).R6Gxx.SYS. System Default Family: (family) File System Write Thru: T/F User Default Family : (family) Per-File Write Through: T/F Installation Name : (name) File System Security : T/F ____________________________________________________________________ Key in the current DATE and TIME at the above prompts. The screen will then display: ____________________________________________________________________ L O A D I N G . . . BOSS/VS Operating System Image Update Utility [version 6.7.x.x] OS/WCS information for drive n (nn): 0: ?????????????? ??????? | x x.x.x 1: ?????????????? ??.??.??.??? | ????????? 2: -------------- -- -- -- --- | ????????? 3: ?????????????? ??????? | ????????? BOSS/VS Image File Name: (displays one of the following): OSN.CT0607xxxxx (ADVANCED SERIES) OSN.AT0607xxxxx (9x00 systems - 1/2-inch) OSN.AC0607xxxxx (9400 systems - 1/4-inch) OSN.BT0607xxxxx (8000 systems - 1/2-inch) OSN.BC0607xxxxx (7x00 systems - 1/4-inch) Target OS Slot (0/1/3) : '0' (or 1) Target WCS Slot (0-3) : '0' (or 1) Target Drives (0/1/All/Quit): (choose drive) ____________________________________________________________________ C) The Image File Name will be displayed by the system. Enter '0' or '1' at the slot prompts to load O.S. and WCS slots 0 and 1. Enter '0', '1', or 'All' at the drive prompt to update the appropriate drives. NOTE: Do not update drive 1 if it is a DATA disk and is to remain so. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg070 The system will now display: ___________________________________________________________________ Now updating WCS slot # n Update in progress: nn% Now updating BOSS/VS Image (displays one of the following): OSN.CT0607xxxxx (ADVANCED SERIES) OSN.AT0607xxxxx (9x00 systems - 1/2-inch) OSN.AC0607xxxxx (9400 systems - 1/4-inch) OSN.BT0607xxxxx (8000 systems - 1/2-inch) OSN.BC0607xxxxx (7x00 systems - 1/4-inch) Update in progress: nn% Image slot directory n/n:n Updates all complete. D O N E - R E A D Y F O R N O R M A L D I S K L O A D ___________________________________________________________________ If you are upgrading to 10/9/8.6G from 9/8.6G or from another star ("*") level of 10/9/8.6G, repeat this procedure for O.S. and WCS slots 1. When O.S. and WCS slots 0 and 1 have been updated, reload the system by pressing the LOAD switch. 5.7.3.2. CHANGING INSTALLATION PARAMETERS Enter a TYPE 3 LOAD (SPECIAL FUNCTIONS) and select OPTION 2 (INITIALIZATION OPTIONS). OPTION 2 - INITIALIZATION OPTIONS Option 4 - CHANGE INSTALLATION PARAMETERS Only system disks will be displayed. DRIVE NUMBER _______ PRIMARY PREFIX _______________________ (Enter (family).R6Gxx.SYS. (Family) is the family where the operating system files reside.) SECONDARY PREFIX _____________________ (Enter (family).R6Gxx.SYS. (Family) is the family where the alternate operating system files reside.) SYSTEM INSTALLATION NAME _________________________ (Sets the default installation name for a specified system disk.) DEFAULT USER FAMILY NAME ________ (Enter default user family.) SECURITY (E=ENABLED, D=DISABLED) ___ FILE SYSTEM WRITE THROUGH? (E=ENABLED, D=DISABLED) ___ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg071 WRITE THROUGH DEFAULT ON FILE CREATE (E=ENABLED, D=DISABLED) __ (This parameter specifies what the default write through will be on a file created through a BASIC file create or through the CREATE utility.) UPDATE DISK WITH INSTALLATION PARAMETERS? (Y/N)__ Display: INSTALLATION PARAMETERS SUCCESSFULLY WRITTEN TO DISK (CR) TO CONTINUE: Reload the system by pressing the LOAD switch. Be sure you are loading the system from the disk where you wish to restore the operating system files. 5.7.3.3. RESTORING THE O.S. FILES Enter SAVERESTORE in a TYPE 2 LOAD and choose OPTION 2 RESTORE FILES FROM TAPE. The screen appears as in figure 5-2. Figure 5-7. Restore Screen -------------------------------------------------------- RESTORE FILES TAPE SET.ID: DRIVE-NUM: REEL-NUM: PRIMARY PREFIX: (FAMILY).NODE. FILE TYPE (D/P/CR=ALL) COMPARE (CR=Y/N) DATE (MM/DD/YY) TIME (HH:MM) OUTPUT DEVICE (CR=VDT) DELETE EXISTING FILES (CR=Y) VERIFY (Y/CR=N) ENTRIES CORRECT (Y/N) -------------------------------------------------------- At each prompt, enter a . At the prompt, "FILE SPECIFIERS", enter ".". Then enter twice. This will restore all files on the release tape to disk. Please note that once all files are restored to disk, the message "AUTOMATIC COMPARE, CR TO CONTINUE" appears. This automatically rewinds the tape and begins the compare operation. This only occurs when the compare option is selected. When the compare is completed, enter a CTL-IV to return to the "SAVERESTORE" menu. 5.7.4. INSTALLING THE CONFIGURATION RECORD It is necessary to install a new configuration record when installing a new system or when upgrading to 10.6G from 8.4 and 8.5 O.S. levels or when changing systems. Until the following procedure is completed, the system will have a minimum configuration. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg072 Enter a TYPE 1 LOAD. Set your prefix to .SYSTEM.CONFIG. fore you load the new configuration ecord, rename the current configuration record on your system, using the RENAME utility, to temporarily preserve it for fall back purposes. (e.g. ".OLDCONFIG.") Using the SAVERESTORE utility, restore the new configuration record on tape onto your system. Execute the CONFIG.MGR utility. The CONFIG.MGR utility allows the user to update the system configuration record by installing a new configuration file. This utility displays the current and new configuration record. When "Y" is answered to the prompt "Install Configuration:", the new configuration is copied from the file ".SYSTEM.CONFIG.I(serial number)", to the special system area on disk. The new configuration takes effect at the next system load. For further details on the use of the CONFIG.MGR utility, see the 8.5D/9.5D Software Announcement #139, or the BOSS/VS UTILITY USER GUIDE, M5102. The configuration record file name is derived from the system serial number by changing the leading "8" to an "I" and adding the prefix ".SYSTEM.CONFIG.". EXAMPLE: .SYSTEM.CONFIG.I1030114 for SSN 810-30114 This configuration record tape should be saved, in case reinstallation should become necessary. After installing the new configuration record, LOAD the system. Otherwise your system will be at minimum configuration and will be extremely slow. 5.7.5. UPDATING SLOTS 2 AND 3 ON ADVANCED SERIES SYSTEMS O.S. and WCS slots 2 and 3 are updated by using the UPDATE.OS and UPDATE.WCS utilities in a TYPE 1 LOAD. To run these utilities, you must set your prefix to the .R6Gxx.DIAG. node. 5.7.5.1. UPDATING WCS SLOT TWO (2) The first section of REMIDI will reside in this slot. !UPDATE.WCS ENTER WCS SLOT (0..3): '2' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE: (choose disk) WCS IMAGE FILE: .R6Gxx.DIAG.REMIDI.CVA WCS LEVEL OF WCS IMAGE FILE: (level displayed) UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETED! NOTE: After REMIDI has been installed, Load Sector 2 at the top of the OSINFO screen should reflect an O.S./WCS of 0/2. If 0/2 is not displayed for Load Sector 2, UPDATE.LD must be run to update the Load Directory. See section 3.9.1.2 for instructions on how to do this. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg073 5.7.5.2. UPDATING WCS SLOT THREE (3) The second section of the ADVANCED SERIES version of REMIDI will reside in this slot. !UPDATE.WCS ENTER WCS SLOT (0..3): '3' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R6Gxx.DIAG.REMIDI.CVC WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 5.7.5.3. UPDATING O.S. SLOT THREE (3) O.S. slot 3 will contain the O.S. for DEMON. !UPDATE.OS BOSS/VS Image File Name: .R6Gxx.DIAG.DEMON.UV Target OS Slot (0/1/3) : '3' Target WCS Slot (0-3) : '0' Target Drives (0/1/All/Quit): (choose drive) NOTE: A '0' is entered for the WCS slot to associate DEMON's O.S. with the WCS in slot 0. DEMON and the 10/9/8.6G O.S. share the same WCS. The system will now display: Update in progress: nn% Image slot directory n/n:n Updates all complete. If drive 1 is a system disk also, the operating system installation procedure must be repeated for this disk. 5.7.6. SLOT INFORMATION Once all slots have been updated, use the utility OSINFO to display the slot information. The information should be similar to figure 5-6. Figure 5-8. Operating System Information OPERATING SYSTEM INFORMATION ---------------------------------------------------------------- BOOT LEVEL : X.X.X.X LOAD SECTOR: 0 1 2 3 DISK 0 : 0/0 1/1 0/2 3/0 SERIAL # : XXX-XXXXX ----------------------------------------------------------------- OS NAME OS LEVEL DISK:SLOT WCS LEVEL ----------------------------------------------------------------- R 6G*xx xxxxxx 6.7.x.x 0:0 C x.x.x R 6G*xx xxxxxx 6.7.x.x 0:1 C x.x.x N/A 0:2 REMIDI C x.x.x DEMON 6.7.x.x 0:3 REMIDI C x.x.x ----------------------------------------------------------------- SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg074 Installation is now complete. 5.8. UPDATING SLOTS 0 AND 1 USING UPDATE.OS AND UPDATE.WCS Because the new ALT LOAD from tape loads O.S. and WCS slots 0 and 1, it is no longer necessary to use UPDATE.OS and UPDATE.WCS to update these slots during a normal installation. However, these slots can be loaded at any time using these utilities, provided the O.S. and WCS files are resident on disk and you are not booted from the slot you wish to update. The following is the procedure to accomplish this. 5.8.1. UPDATING O.S. SLOTS 0 AND 1 Set the prefix to the .INST. node by keying in the following in command mode: !PREFIX .R6Gxx.INST. !UPDATE.OS BOSS/VS Operating System Image Update Utility (Version 6.5.5.0) OS/WCS information for drive n (nn) 0: R 6G*xx (date) 6.7.x.x | X 6.x.x 1: ?????????????? ??.??.??.??? | ? ??.??.?? 2: -------------- -- -- -- --- | R X 6.x.x 3: DEMON 6.7.x.x | R X 6.x.x The following prompts will then be displayed, one at a time: BOSS/VS Image File Name: .R6Gxx.INST.OSN.UV Target OS Slot (0/1/3) : '0' or '1' Target WCS Slot (0-3) : '0' or '1' Target Drives (0/1/All/Quit): (choose drive) The system will now display: Update in progress: nn% Image slot directory n/n:n Updates all complete. 5.8.2. UPDATING WCS SLOTS 0 AND 1 Set the prefix to the .INST. node by keying in the following in command mode: !PREFIX .R6Gxx.INST. !UPDATE.WCS ENTER WCS SLOT (0..3): '0' or '1' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R6Gxx.INST.WCS.A (for 9xxx systems) WCS.B (for 7xxx/8xxx systems) WCS.C (for ADVANCED SERIES) WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg075 5.9. SYSTEM STARTUP 5.9.1. STANDARD STARTUP COMMAND FILE The commands for the standard System Startup Command File are released in the file: .R6Gxx.SYS.START.CMD The standard commands are: !MAGNET.STARTUP !GROUP.CREATE SPOOLER,TYPE=SYSTEM !SPOOL P*,VERIFY=F,PAUSE=F !GROUP.ENABLE TERMINALS,VERIFY=F,PAUSE=F The name of the System Startup Command File actually used for startup is: (system-default-family).SYSDATA.START.CMD Part of 10/9/8.6G BOSS/VS system installation is to copy the released file to the .SYSDATA. node and make changes and additions as necessary. Note that the commands and parameters in this file must match the commands and parameters defined in the CLI command and function definition files for the individual system being installed. If the System Startup Command File is not found after a system load, then a default initialization is performed. This puts all printers into spooled mode and enables terminals. The following outlines the commands, some of the implications and details of the System Startup Command File method of system configuration. .9.1.1. COMMAND FILE DEFINITIONS MAGNET.STARTUP This command runs a released MAGNET program that does all of the startup operations required by the MAGNET subsystem. This command should be deleted if MAGNET is not part of the system configuration. GROUP.CREATE SPOOLER,TYPE=SYSTEM This command creates the SPOOLER Group that maintains the activity log files and Group statistics for the spooler subsystem. This command should come before the 'SPOOL P*' command. SPOOL P*,VERIFY=F,PAUSE=F This command puts all of the printers into spooled mode, and causes any eligible requests on the spooled printers to start printing. GROUP.ENABLE TERMINALS,VERIFY=F,PAUSE=F This command enables the 'built-in' TERMINALS Group, and allows all users to logon to any terminals. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg076 This command is provided to allow the terminals to be enabled under user control. See below. NOTE: IF A SYSTEM STARTUP COMMAND FILE EXISTS, THIS COMMAND, OR SOME OTHER COMMAND TO ENABLE TERMINAL GROUPS, MUST BE IN THE SYSTEM STARTUP COMMAND FILE FOR USERS TO LOGON TO THE SYSTEM. In case the TERMINALS Group is disabled, a user with 'system operator' status can enable this group when attempting to logon to the system. This allows an operator to logon to the system in case the Startup Command File did not enable the TERMINALS Group, or the TERMINALS Group was left disabled by accident and all operators signed off the system. To enable the TERMINALS Group during logon the operator attempts to logon and ignores the 'Logon disabled' error messages and enters a 'CR' to continue. A prompt is displayed asking the operator if he wants to enable the TERMINALS Group. NOTE: THIS OPTION IS NOT AVAILABLE IF SOME OTHER TERMINAL TYPE GROUP IS ENABLED. ALSO, ONLY THE TERMINALS GROUP IS ENABLED, AND IT IS NOT CREATED IF IT DOES NOT EXIST. 5.9.2. IMPLICATIONS 1) Normal system startup is automatic. The system configuration options defined when the system was installed (placed into the System Startup Command File) are put into effect each time the system is loaded, with no further action by the user. These startup options may be modified by the user at any time, by editing the System Startup Command File. 2) Startup sequence is under user control. Users now have the ability to control the sequence of events at startup, after the internal startup sequence is complete. Users that do not need this level of control may ignore this feature. Some users may wish to run specific programs, and do recovery operations, before MAGNET and/or the SPOOLER are started up. This ability would be impossible if these subsystems were always started by the internal system initialization. 3) System recovery is possible before all users logon. This approach allows the operator to allow only specified terminals/users to logon after a system load. The System Startup Command File containing the single command: GROUP.CREATE , TYPE=TERMINAL, USERS=SYS.MGR, DEVICES=T0 would allow only the user 'SYS.MGR' to logon to terminal 'T0' after the system load. No other users could logon, and no other activity would start. In this case the printers will be in suspended mode and MAGNET will not be initialized. When the system operator is finished with the recovery operations the 'normal' system configuration command file may be run by the operator to begin normal system processing. Again, users who do not need this level of control may ignore this feature. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg077 4) Default startup with no System Startup Command File. When the TYPE 1 LOAD is complete, if the System Startup Command File is not found then 'default' startup conditions are in effect. In this case the system is available for any use. This mode is intended to support systems that want only these default startup options. The 'built-in' TERMINALS Group is enabled and allows all users to logon to any terminal. A system group named SPOOLER is created and the printers are put into spooled mode. The MAGNET subsystem is not activated. The following is a description of the details of the System Startup Job: When a TYPE 1 LOAD is performed, the last module to be initialized is the Job Manager (JMM). The final act of JMM is to run a batch job with a CLI command file. The files involved are: (system-default-family).SYSDATA.START.CMD (system-default-family).SYSDATA.START.IN (system-default-family).SYSDATA.START.OUT SYSDATA.START.CMD is a sequential file that contains all of the startup commands; this is the System Startup Command File. The Job Manager looks in the system default family (only) for this file. SYSDATA.START.IN is a sequential file that contains any data that may be input by commands and programs in the above startup file. A read from standard INPUT will read records from this file. The Job Manager looks in the system default family (only) for this file. SYSDATA.START.OUT is a sequential file that contains the results of the startup command file. A write to standard OUTPUT by commands and programs will be placed into this file. The Job Manager deletes this file in the system family if it exists, prior to running the startup command file. If the startup file (system-default-family).SYSDATA.START.CMD - or - (system-default-family).SYSDATA.START.CMD.TEXT is not found, the Job Manager will perform a default startup described above. If the startup file (system-default-family).SYSDATA.START.IN - or - (system-default-family).SYSDATA.START.IN.TEXT is not found, the Job Manager will attach a null file to startup INPUT; an End-Of-File will be returned for each read from standard INPUT. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg078 NOTE: THE SYSTEM STARTUP COMMAND FILE CONTAINS (ONLY) STANDARD CLI COMMANDS. A CLI command may be: 1) A CLI Command or Function (START, PREFIX, $WHERE, etc.) 2) A system utility (DIR, COPY, etc.) 3) The name of a program to run. 4) The name of another CLI command file. 5.10 DIAGNOSTIC REMOVAL This section describes the removal of diagnostic programs from a system. The diagnostics reside in the file system and several bootable disk slots. They are removed from the file system with the 'delete' utility. They are removed from the bootable slots by overwriting the images. The procedure follows. 1. Removing REMIDI The removal of REMIDI is accomplished by overwriting the two bootable REMIDI slots with the WCS image. 2. Update WCS Slot 2 Execute the UPDATE.WCS utility and respond to the prompts as shown below. ENTER WCS SLOT (0..3): - 2 AVAILABLE DISK UNITS ARE: - (displayed) DISK TO UPDATE : - Enter the disk number. WCS IMAGE FILE: - .R6Gxx.INST.WCS.X (where X = A,B,C) X = A for MPx 9xxx X = B for MPx 7xxx, 8xxx X = C for Advanced Series WCS LEVEL OF WCS IMAGE FILE: - (displayed) During the update process, the following message appears: UPDATING DISK UNIT nn SECTOR xx When the update is complete, the following message appears: WCS UPDATE COMPLETED! The preceding should be performed on all system disks. 3. Update WCS Slot 3 Execute the UPDATE.WCS utility and respond to the prompts as shown below. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg079 ENTER WCS SLOT (0..3): - 3 AVAILABLE DISK UNITS ARE: - (displayed) DISK TO UPDATE : - Enter the disk number. WCS IMAGE FILE: - .R6Gxx.INST.WCS.X (where X = A,B,C) X = A for MPx 9xxx X = B for MPx 7xxx, 8xxx X = C for Advanced Series WCS LEVEL OF WCS IMAGE FILE: - (displayed) During the update process, the following message appears: UPDATING DISK UNIT nn SECTOR xx When the update is complete, the following message appears: WCS UPDATE COMPLETED! The preceding should be performed on all system disks. 4. Removing DEMON The removal of DEMON is accomplished by overwriting the bootable DEMON slot with DEMON.UX. 5. Update OS Slot 3 Execute the UPDATE.OS utility and respond to the prompts as shown below. BOSS/VS Image File Name: - DEMON.UX Target OS Slot (0/1/3): - 3 Target WCS Slot (0-3): - 0 Target Drives (0/1/All/Quit): - Enter the disk number During the update process, the following message appears: Update in progress : x/y : zz% When the update is complete, the following message appears: Updates all complete. The preceding should be performed on all system disks. 6. Removing diagnostics from the file system The diagnostics are removed from the file system using the 'delete' utility. The diagnostics are found in the system node .R6Gxx.DIAG. The files in the following nodes should be deleted from the file system. .R6Gxx.DIAG. .ENHANCER6G. .TRACKER. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg080 The following files should be deleted: .AC (MPX 9000 series 1/4" tape boot OS image with DIVE) .AT (MPx 9000 series 1/2" tape boot OS image with DIVE) .BC (MPx 7000 series 1/4" tape boot OS image with DIVE) .BT (MPx 8000 series 1/2" tape boot OS image with DIVE) .CC (Advanced Sereis 1/4" tape boot OS image with DIVE) .CT (Advanced Series 1/2" tape boot OS image with DIVE) The following file(s) should be added as a replacement for the file(s) deleted above. .ACX (MPx 9000 series 1/4" tape boot OS image without DIVE) .ATX (MPx 9000 series 1/2" tape boot OS image without DIVE) .BCX (MPx 7000 series 1/4" tape boot OS image without DIVE) .BTX (MPx 8000 series 1/2" tape boot OS image without DIVE) .CCX (Advanced Series 1/4" tape boot OS image without DIVE) .CTX (Advanced Series 1/2" tape boot OS image without DIVE) This completes the diagnostic removal procedure! 6. RELATED DOCUMENTATION 2770/2780/3770/3780 Batch Emulator User Guide M5080C 3270 Pass-Through Reference Manual M5091A Business BASIC 90 Reference Manual M6262C * BOSS/VS User Guide M5098G BOSS/VS Utilities User Guide M5102K * 3270 Emulation Package Operator Guide for MAI 8000 Series M5129 File Transfer Facility User Reference Manual M6352A * BOSS/VS Installation Guide M5138J * MPx System Installation Planning Guide M5146G BOSS/VS Special Purpose Utilities User Guide M5151 BOSS/VS System Support Manual M5152 Intersystem Transport Package User Guide M6354D MAI 8000 Series COBOL Reference Manual M5174 MAI 8000 Series COBOL User Guide M5175 BOSS/VS File Conversion User Guide M5185A MAGNET/VS User Reference Manual M6363 * These manuals were revised for 10.6G/9.6G/8.6G. ORIGINATOR: MBF SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB078 Pg081 FIB 00079 01/17/90 *** Each Disk Set-up as Separate Family when Shipped [ WPSF 579 ] *** Beginning on December 1, 1989, all multi-disk MPx and Advanced Series Systems will be shipped with each drive setup as a separate family. In the past, multiple drive systems were setup as a single family. The majority of the time the field personnel needed to reconfigure the drives as single families so the new procedure should save a considerable amount of time. ORIGINATOR: Kevin Liebl SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB079 Pg001 FIB 00080 01/17/90 *** 8/9/10.6G*45 has been released [ WPSF 589 ] *** M6G*45 has been released. It contains the following fixes for problems that were reported on M6G*43: 1. Spooled jobs queued to serial printers might hang. In the Spooler Job Maintenance Utility the job will display the status of "PRINTING" but percent done will be zero and nothing is being printed. Also a job will display "STOPPING" but will never stop. 2. ERRORLOG will display the wrong memory board location for ECC errors. Erroneous locations were being reported in the ERRORLOG. 3. ALB (Auditors Log Book) a) Automatic switch with Indexed files while open will corrupt the file. b) Unable to turn off logging, if files are disabled. You can order this new release from Software Distribution. New M6G*43 orders will receive the M6G*45 release. ORIGINATOR: Joe Melendez SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB080 Pg001 FIB 00081 01/17/90 *** Form Feed not Generated on Stopped or Cancelled Jobs [ WPSF 590 ] *** PROBLEM: When a spooler job is 'Stopped' and/or 'Cancelled' from the spooler, a form-feed is not generated on 8/9/10.6G. Therefore, the next job submitted begins printing directly after the stopped job, not at the Top of Form. This was a regression from 8/9/10.6E. SOLUTION: This has been fixed on 8/9/10.6H. ORIGINATOR: Kevin Liebl SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB081 Pg001 FIB 00082 01/17/90 *** Possible Data Loss during Directory Reconstruct [ WPSF 591 ] *** PROBLEM: On releases 8/9/10.6E and below, when using DISKANALYZER to reconstruct a directory and enough disk space is not available, the reconstruct will stop. An error message will be issued at the point where the reconstruct stopped and all files after this point will be lost. SOLUTION: When reconstructing a directory, make sure there is enough free disk space to do the recontruction. To determine how many sectors are required, use DISKANALYZER, option #4 "LOCATION OF A FILE". At the filename prompt, enter "(family):DIR" where "family" is the name of the family to be reconstructed. DISKANALYZER will show all the extents for the directory. The fourth column labeled "Length" contains the size, in sectors, of each of the extents. The sum of this column is the total number of sectors needed in that family to recontruct the directory. Ensure that the family has enough free space to accomodate the new directory that will be established by the directory re- construct option. FIX: This problem is fixed in 8/9/10.6G. ORIGINATOR: Randy Case SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB082 Pg001 FIB 00083 03/05/90 *** DATAWORD II VDT Emulation Causes Dumps on n.6G OS [ WPSF 605 ] *** PROBLEM: After upgrading to n.6G OS, the following four tuples have occurred when trying to use an MDT in BASIC emulation: 2,10,3,3 (Instruction Fault in IO Module) with a 1,238,0,3 (Byte offset field of pointer exceeds segment size) or 3,4,1,19 (Error unlocking segment for main memory I/O request (ioctrap)) with a 6,0,17,3 (Usage error). WORKAROUND: At this time do not use the MDT in BASIC emulation (works fine in DATAWORD). This problem is fixed in the n.6H OS level. ORIGINATOR: Don Luque SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB083 Pg001 FIB 00084 03/22/90 *** Diskanalyzer Reconstruct VS Reconstruct [ WPSF 608 ] *** When a file needs to be reconstructed, there is often confusion as to which utility should be used. The following is a comparison between !Diskanalyzer and !Reconstruct which may help to alleviate some of this confusion. DKA (RECONTRUCT) RECONSTRUCT SPEED SLOWER FASTER EXTENT OF VERY THOROUGH NOT AS THOROUGH REPAIR ESTIMATED SIZE DEPENDS ON DATA RECORD REQUIRES APPROXIMATELY DISK SPACE SIZE. (EG. USING A MK FILE 6 TO 7 TIMES THE REQUIREMENTS WITH KEYSIZES OF 8,12,21,& SPACE OCCUPIED BY THE 14 AND 10K RECORDS, EACH WITH LARGEST KEYSET IN FILE 1K BYTES, THE REQUIRED DISK (EG. USING A MK FILE SPACE WOULD BE APPROXIMATELY WITH KEYSIZES OF 10K(# RECORDS) * 1100 (BYTES 8,12,21 & 14 AND 10K PER RECORD + TOTAL KEYSIZES + RECORDS, EACH 1K 4 BYTES PER KEYSET FOR OVER BYTES, THE REQUIRED HEAD ROUNDED UPWARD) = 11,000K DISK SPACE WOULD BE BYTES OR 11,000 SECTORS) APPROXIMATELY 25(21+4 OVERHEAD) * 10K(# RE- CORDS)* 7= 1,750K BYTES OR 1,750 SECTORS) THE ABOVE CALCULATIONS ARE APPROXIMATIONS AND SHOULD THEREFORE ONLY BE USED TO CALCULATE "ESTIMATED" DISK REQUIREMENTS. WHICH UTILITY WILL USE MORE SPACE DEPENDS ON RATIO BETWEEN RECORD SIZE AND LARGEST KEYSIZE. FOR EXAMPLE, THE ABOVE SITUATION WOULD BE REVERSED WITH LARGE KEYS AND SMALL RECORDS. TYPE OF FILES ALL TYPES (EXCEPT SYSTEM) KEYED FILES ONLY (NOT SUPPORTED SERIAL OR INDEXED) WORK AREA USES A USER SPECIFIED REBUILDS IN PLACE NEW FILE (USER CAN SELECT WITH TEMPORARY FILES FAMILY) FOR B-TREES (USER CAN SELECT FAMILY) DKA (RECONTRUCT) RECONSTRUCT METHOD USED SINGLE-KEYED FILES: USES THE SINGLE-KEYED FILES: "HIDDEN KEY" IN THE DATA AREA USES THE "HIDDEN KEY" TO BUILD KEYS OF THE NEW FILE IN THE DATA AREA TO IN A TEMPORARY FILE. BUILD KEYS OF THE EXISTING FILE IN PLACE. MULTI-KEYED FILES: USES THE MULTI-KEYED FILES: INTERNAL FORMAT STRING (IFS) USES THE INTERNAL IN THE CONTROL SEGMENT OF FORMAT STRING (IFS) THE FILE, PLUS THE DATA AREA IN THE CONTROL TO BUILD THE KEYS OF THE NEW SEGMENT OF THE FILE, SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB084 Pg001 FILE IN A TEMPORARY FILE. PLUS THE DATA AREA TO BUILD THE KEYS OF THE EXISTING FILE IN PLACE. READS DATA AREA, CREATES AND USES THE SORT UTILITY. COPIES TO A WHOLE NEW FILE, IT ISSUES THE PROMPT RECONSTRUCTING B-TREE KEYS "ARE YOU IN STAND-ALONE IN NEW KEY AREA ONE RECORD AT MODE?" IF SO, IT USES A TIME FROM THE DATA WITHIN LARGE FIXED SEGMENTS. THE FILE AND (FOR MULTI-KEYED THESE ARE LARGE CHUNKS OF FILES) THE IFS. MEMORY WHICH CANNOT BE SWAPPED. THIS MAY IMPACT PERFORMANCE. IF THE SYSTEM IS NOT REALLY IN STAND-ALONE MODE WHEN STAND-ALONE MODE IS RE- QUESTED AND IF THE UTILITY CANNOT FIND A PLACE TO PUT THE DATA, IT COULD DUMP OR HANG. UPDATES RECORD COUNT IN CONTROL BREAKS THE VOLUME OF SEGMENT. IF FILE DATA AND IFS DATA INTO SEVERAL ARE DAMAGED, MAY NOT BE ABLE TO DIFFERENT PIECES AND FIND ALL RECORDS; FINDS WHAT IT THEN MERGES THEM. THE CAN, CHECKS NUMBER OF RECORDS KEYS ARE REWRITTEN TO IN CONTROL SEGMENT (WHICH IS NOT THE SAME AREA ON DISK. UPDATED IN ALL CASES DURING FILE UPDATES RECORD COUNT IN WRITE THROUGH). CONTROL SEGMENT. WHEN "REPAIRING" MULTI-KEYED THE NEW B-TREES ARE FILES (COPYING TO ANOTHER DISK FILLED TO A USER DE- AREA), INDIRECT RECORDS IN LONG FINED PERCENTAGE (67% RECORD BLOCKS (LRBS) ARE IN- IS DEFAULT) FULL, CORPORATED IN SEQUENCE INTO LEAVING ROOM TO GROW SHORT RECORD BLOCKS (SRBS) WITHOUT SPLITTING, THEREBY CONSOLIDATING THE SINCE SPLITTING OF A FILE, LEAVING ALL RECORDS IN B-TREE SLOWS PERFORMANCE. SRBS AND NONE IN LRBS. THIS WILL INCREASE PERFORMANCE. DKA (RECONTRUCT) RECONSTRUCT METHOD USED THE NEW B-TREES ARE FILLED TO THE NUMBER OF SECTORS CON'T 67% FULL, LEAVING ROOM TO GROW PER B-TREE NODE IS SET WITHOUT SPLITTING, SINCE THE TO A USER DEFINED SPLITTING OF A B-TREE SLOWS NUMBER BETWEEN 1 AND 4. PERFORMANCE. (SEE "WARNINGS AND RELATED FIELD BULLETINS" BELOW FOR MORE INFO.) THIS IS A GOOD IDEA IF THE FILE IS LARGE AND PERFORMANCE ON THIS FILE NEEDS TO BE IMPROVED AND IF ADDITIONAL MEMORY IS AVAILABLE. PERFORMANCE ON THE OTHER FILES MAY SUFFER. ERROR IF SOME DATA IS BAD (HARD DISK RELIES ON THE INTEGRITY CORRECTION/ ERROR), IT REPORTS THE AREA OF THE DATA. IF DATA IS SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB084 Pg002 REPORTING THEN GIVES OPTION TO ABORT OR BAD (HARD DISK ERRORS), CONTINUE, SO ALTHOUGH SOME DATA IT ABORTS THE PROCESS. MAY BE LOST, MUCH CAN BE IT DOES NOT REPORT ERRORS RECOVERED. IT FINDS (EG. RECORD COUNT). WARNINGS WHEN RECONSTRUCTING A DIRECTORY ON RELEASES 8.5 AND USING DKA, MAKE SURE THERE IS HIGHER, USING RECONSTRUCT ENOUGH FREE DISK SPACE. IF WITH A VALUE GREATER THAN THERE IS NOT ENOUGH DISK SPACE, 1 IN THE "SECTORS/B-TREE THE RECONSTRUCT WILL FAIL AND NODE" MAY CAUSE DATA DATA FILES WILL BE LOST. THIS CORRUPTION. A UTILITY IS FIXED IN *.6G. SEE FB591 CALLED "CHKBTREES" IS FOR MORE INFORMATION. AVAILABLE TO FIND FILES WHICH MAY HAVE THIS PROBLEM. SEE FB572 FOR MORE INFORMATION. RELATED FIELD FB473 - USING RECONSTRUCT TO REPAIR MULTIKEYED AND DIRECT BULLETINS FILES. FB572 - POSSIBLE DATA LOSS WITH RECONSTRUCTED FILES. FB591 - POSSIBLE DATA LOSS WHILE RECONSTRUCTING THE DIRECTORY. ORIGINATOR: Kevin Liebl SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB084 Pg003 FIB 00085 05/16/90 *** Software Announcement 8/9/10.6H *** MAI Basic Four, Inc. is pleased to announce that the new system software revisions, 10.6H/9.6H/8.6H, are now available. The 9.6H revision is the recommended revision for MPx 9xxx Series Systems. The 8.6H revision is the recommended revision for MPx 7xxx and 8xxx Series Systems. The 10.6H revision is the recommended revision for Advanced Series Systems. ****************************************************************** * * * o If this release is installed on MPx 9x00 system containing * * DMA-II controllers, then version -002 of the DMA-II * * boards must be used. If the system contains -001 boards, * * please contact your hardware support for local board * * replacement procedures. Please refer to the HARDWARE * * section #4. * * * * o As of release 9/8.6C, the .SYSDATA.SECURITY.DATA file is * * not transportable to previous release levels. Therefore, * * if you are upgrading to 10/9/8.6H from a release prior to * * 9/8.6C, this file should be saved before the upgrade, for * * fall-back purposes. * * * * o Files transferred from 10/9/8.6H to O.S. levels below * * 9/8.6A must be transported with EXTTAPE, MCSI, FTF, TBC, * * or ATP. If a downgrade is performed from 10/9/8.6H to a * * release prior to 9/8.6C, the user's files must be * * transported to the older O.S. level with one of the above * * utilities. * * * * o Horizontal software such as PRESENTATION SERVICES, GRAPH, * * and ORIGIN typically have files that reside in the .SYS. * * node. These files need to be transferred to the new .SYS. * * node on an O.S. upgrade, either by using the COPY utility * * or by re-installing the software. * * * * o The 10/9/8.6H Software Announcement exists as a serial * * file on the official release tape. To print a copy, submit * * the following file to the printer: * * * * .R6Hxx.INST.DOC.ANNOUNCE6H * * * ****************************************************************** Copyright 1989, Rev. 1989, MAI Basic Four, Inc. All rights reserved. TABLE OF CONTENTS _____ __ ________ 1.0 INTRODUCTION 2 1.1 ENHANCEMENTS IN THIS RELEASE 2 1.1.1 Support for new printers 2 1.1.2 Hardware flow control 2 1.1.3 Online Backup (Future enhancement) 3 1.2 NEW MNEMONIC FOR SUPERSCRIPT AND SUBSCRIPT 3 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB085 Pg001 1.3 NEW UTILITY FOR PRINTER CHARACTER TRANSLATION - XLTGEN 3 1.4 CONFIGURATION RECORD CONSIDERATIONS 4 1.5 SOFTWARE ANNOUNCEMENT 4 2.0 FIXES IN THIS RELEASE 5 2.1 SPOOLER 5 2.2 BOSS/VS 5 2.2.1 Utilities 5 2.2.2 Auditor's Logbook (ALB) 5 3.0 CONFIGURATIONS 6 3.1 CONFIGURATIONS FOR MPX 7000/7100/8000 SERIES SYSTEMS 6 3.2 CONFIGURATIONS FOR MPX 9000/9100/9400 SERIES SYSTEMS 7 3.3 CONFIGURATIONS FOR MPX 9500/9600 SERIES SYSTEMS 8 3.4 CONFIGURATIONS FOR THE ADVANCED SERIES FAMILY 9 4.0 DIAGNOSTICS 11 4.1 REMIDI 11 4.1.1 ON MPx 7000, 7100, AND 8000 SERIES SYSTEMS 11 4.2 DEMON - UPDATING THE LOAD DIRECTORY 14 4.3 ADVANCED SERIES ONLY 15 4.3.1 HIGH FREQUENCY MARGINS ON THE ADVANCED SERIES 15 4.3.2 USING ALT LOAD FOR REMIDI AND DEMON 15 4.4 DIAGNOSTIC REMOVAL 15 5.0 HARDWARE 18 5.1 MPX 7000, 7100, AND 8000 PCBA NOTES 18 5.2 MPX 9XXX SERIES SYSTEM PCBA NOTES 21 5.3 PCBA'S FOR ALL MPX 7/8/9XXX SERIES SYSTEMS 25 5.4 ADVANCED SERIES PCBA NOTES 27 5.5 PCBA'S NOT SUPPORTED ON ADVANCED SERIES 30 5.6 PERIPHERAL DEPENDENCIES 30 5.6.1 GCR TAPE DRIVE 30 5.6.2 SCSI MTCS TAPE DRIVE 31 5.6.3 HIGH CAPACITY CARTRIDGE (HCC) TAPE DRIVE 31 5.6.4 TERMINALS 31 5.6.5 DISK DRIVES 31 5.7 HARDWARE FLOW CONTROL - NEW FEATURE 32 1.0 INTRODUCTION ____________ 1.1 ENHANCEMENTS IN THIS RELEASE ____________ __ ____ _______ The 10.6H/9.6H/8.6H release contains the following enhancements: 1.1.1 Support for new printers _______ ___ ___ ________ This release provides support for new printers. The PT-422X Workstation Printers are a family of rugged desktop printers designed for low to moderate-duty applications. Intended applications include invoice/folio printer, terminal/PC printer or low-end system printer. The family includes four members: PT-4225 -- 80-column/9-wire PT-4226 -- 132-column/9-wire PT-4227 -- 80-column/24-wire SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB085 Pg002 PT-4228 -- 132-column/24 wire The 9 wire products offer Near Letter Quality printing at 63 cps, and draft mode printing at 250 cps. The 24-wire products offer Letter Quality printing at 75 cps, and draft mode printing at 225 cps. All products support up to 4-part forms, both rear and bottom feed, and demand-document/tear bar. This release implements Universal Printer Driver (UPD) for these printers. Please see section **UPD** for information on configuring these printers. 1.1.2 Hardware flow control ________ ____ _______ With this release the 16-way will support uni-directional hardware flow control. The 16-way that supports this feature is PN 903437-002, revision R or above. A new I/O cable will also be required for support of this feature, PN 916509, revision B. The device will be able to throttle the host, but the host will not throttle the device. (This will cure the 'Data Loss' problem that occurs with ISP printers when they are turned off.) When ordering this new revision PCBA, it is only necessary to replace 16-ways that will be using hardware flow control. Please DO NOT replace every 16-way in every system with this new revision. This will ensure that there will be enough PCBA's to go around upon release of 8/9/10.6H. Flow control is implemented by monitoring the CTS signal of the interface. If CTS drops, the host will cease transmitting until CTS is detected or until a specified timeout has occurred. If the timeout occurs, a "timeout" error will be returned to the user. The timeout value is reset for each character transmitted. This means that if CTS drops multiple times during a transmission, 5 seconds (for example) will be allowed for each detection of CTS dropping. Hardware flow control is available for any serial device except for SPE.MODEM. Hardware flow control must be configured in TERM.CONFIG for it to be operational. Enter the extended options menu from the port main menu and the option will appear: USE CTS FLOW CTL (Y/N) Enter a 'Y' to have the system recognize CTS flow control for this device. Hardware flow control requires a new cable; 916509 at revisionB. This cable comes with a 15 pin connector designed to be attached to the backpanel serial connector. 1.1.3 Online Backup (Future enhancement) ______ ______ _______ ____________ In the COPY and SAVERESTORE utilities, there is a new prompt for online backup. In SAVERESTORE and COPY, the prompt: ONLINE BACKUP (Y/CR=N) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB085 Pg003 will appear. Online backup is a new feature that will be released in the future and IS NOT available currently. This field will be skipped when entering the options for the SAVE and COPY operations. 1.2 NEW MNEMONIC FOR SUPERSCRIPT AND SUBSCRIPT ___ ________ ___ ___________ ___ _________ When using the mnemonics 'SUPER' and 'SUB' to preform superscripting and subscripting, the mnemonic 'ESS' is use to end the attributes. For example, 10 PRINT (1) "HELLO",'SUPER',"SUPER",'ESS' 1.3 NEW UTILITY FOR PRINTER CHARACTER TRANSLATION - XLTGEN ___ _______ ___ _______ _________ ___________ _ ______ The utility XLTGEN is used to build a character translation file to be used in the Universal Printer Driver (UPD) subsystem. This utility replaces the BAND.TABLE utility. Please refer to the BOSS/VS Utilities User's Guide (M5102L) for more information. 1.4 CONFIGURATION RECORD CONSIDERATIONS _____________ ______ ______________ In general, a new configuration record is required when upgrading to a new system type (e.g., from an 8xxx to a 9xxx system), when adding new hardware, or when upgrading to a new major release level (e.g., 8.5 to 8.6). A new configuration record is NOT required when upgrading from releases 9.6A/B/C/E to 9.6H, from releases 8.6A/B/C/E to 8.6H and from release 10.6A/B/C/E to 10.6H. A new configuration record is also required when upgrading from 8.4 and 9.5/8.5 releases to 10.6H/9.6H/8.6H releases. 1.5 SOFTWARE ANNOUNCEMENT ________ ____________ The 10.6H/9.6H/8.6H Software Announcement exists as a serial file on the official 10/9/8.6H O.S. release tape, which allows the user to print copies, if needed. To print this document, SUBMIT the following file to the printer: (family).R6Hxx.INST.DOC.ANNOUNCE6H 2.0 FIXES IN THIS RELEASE _____ __ ____ _______ 2.1 SPOOLER _______ 1) A problem with some printers when stooping never make the transition from STOPPING to STOPPED. This has been fixed.(519428) 2) Using the 'SPMx' mnemonics on PT-4214 or PT-4219 printers would cause a positioning mnemonics to work SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB085 Pg004 incorrectly.(521299) 3) With an MBF serial printer connected and online, an offline transition will be detected as soon as the printer goes off-line instead of when the next spool job begins on that printer.(522529) 4) You may not set a trial form on a MBF serial printer that is off-line. (522539) 5) With a printer in reserved mode, a linefeed will no longer be inserted after a VFU load.(523362) 6) Using 4217 as a slave printer, screen dumps and printing from BASIC can be done without having to invert the 8th bit.(524323) 2.2 BOSS/VS _______ 2.2.1 Utilities _________ 1) A problem with SECURITY, DOWN.LOAD, NEWX, and DEVICES where an ERR 2,6,17,2 would occur when more than 409 devices were configured on the system. 2) The ERRORLOG was not reporting memory errors at the right location. This has been fixed.(524376) 2.2.2 Auditor's Logbook (ALB) _________ _______ _____ 1) When auto-switching of logfiles occur on an indexed file, the current position of the source file is maintained and is not lost.(523051) 2) A problem with ALB using excessive semaphores and causing a system dump 7,5,1,20-35,0,0,2 has been fixed.(523354) 3) Logging can now be disabled if the logfiles exists on a family or installation that is disabled or non-existent.(524064) 3.0 CONFIGURATIONS NOTE 1: The number of "High Activity Tasks" is approximate and largely dependent on the application. The relative relationship of the numbers between configurations is more important than the actual numbers themselves. NOTE 2: System configurations of MPx 9xxx Series Systems are based on the use of the LS-700 power supply mainframes. Original 810 systems do not support the LS-700 power supply and, therefore, will not meet all defined maximum configurations listed. NOTE 3: The following configurations are based on performance testing, and are subject to change as newer performance testing data becomes available. The configurations listed in the marketing announcements override those listed here. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB085 Pg005 3.1 CONFIGURATIONS FOR MPX 7000/7100/8000 SERIES SYSTEMS ______________ ___ ___ ______________ ______ _______ The maximum configuration for MPx 7000, 7100, and 8000 Series Systems, models 7030, 7130, and 8030, is as follows: 116 Devices - A combination of 8-ways, 16-ways, the 4 ports on the MCS PCBA, MDTs and HVDTs up to a total of 116 devices are supported. 3 CPU sets 10 ISDCs: 16-ways (7 maximum) and/or 8-ways 32 Ghost tasks 24 High speed videos (HVDT) 8 Disk drives 4 Parallel printers 2-8 Megabytes of memory 2 Magnetic tape drives - MTR, MTS, and/or GCR (2 Maximum), and/or MCS (1 maximum) 4 Intelligent Multi-Line Controllers (IMLC) 8 DataWord II terminals 4 TBC lines 64 3270 terminals 8 X.25 lines 2 Auto-Call Units (ACU) 99 Serial Printers 99 System printers (total serial and parallel not to exceed 99) 2 Buffered Magnetic Tape Controllers 27 High activity concurrent tasks 1 LAN controller NOTE: There is a maximum of 9 memory assembly boards in any combination of 1/2 Mb, 1 Mb, 2 Mb, 4 Mb and BMTCs (a maximum of 3 boards per chassis). Models 7010/7110/8010 and 7020/7120/8020 have the same configuration limits as models 7030 and 8030 above, with the following limitations: 7010/7110/8010 7020/7120/8020 1 CPU set 2 CPU sets 2-4 Mb memory 2-8 Mb memory 20 Devices 52 Devices 12 Concurrent tasks 20 Concurrent tasks (high activity) (high activity) 23 System printers 51 System printers 3.2 CONFIGURATIONS FOR MPX 9000/9100/9400 SERIES SYSTEMS ______________ ___ ___ ______________ ______ _______ The maximum configuration for MPx 9000, 9100, and 9400 Series Systems, models 9020, 9120, and 9420 is as follows: 116 Devices - A combination of 8-ways, 16-ways, the 4 ports on the MCS PCBA, MDTs and HVDTs up to a total of 116 devices are supported. 2 CPU sets with Evaluation Stack and Rstack Cache SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB085 Pg006 10 ISDCs: 16-ways (7 maximum) and/or 8-ways (10 maximum) 32 Ghost tasks 24 High speed videos (HVDT) 16 Disk drives on models 9020 and 9120, 8 disk drives on model 9420(5.1 GB maximum), with no more than 8 14-inch fixed drives on any of the 3 models 8 Parallel printers 4-12 Megabytes of memory 2 Magnetic tape drives - MTR, MTS, and/or GCR (2 maximum), and/or MCS,HCC (1 maximum) 4 Intelligent Multi-Line Controllers (IMLC) 8 DataWord II terminals 6 TBC lines 64 3270 terminals 8 X.25 lines 2 Auto-Call Units (ACU) 99 Serial printers 99 System printers (total serial and parallel not to exceed 99) 4 DMA controllers (including DMA-I, DMA-II and DMA-III's in any combination)* 2 Buffered Magnetic Tape Controllers 42 High activity concurrent tasks 1 LAN controller * It is recommended that, for maximum performance, no more than two 250MB disks be configured per DMA-II, and that the number of DMA-II's equals or exceeds the number of CPU's. Models 9010, 9110, and 9410 have the same configuration limits as the 9020, 9120, and 9420 above, with the following exceptions: 1 CPU set with Evaluation Stack and Rstack Cache 68 Devices 10 ISDCs: 16-ways (4 maximum) and/or 8-ways (8 maximum) 67 Serial printers 75 System printers (total serial and parallel not to exceed 75) 27 High activity concurrent tasks 3.3 CONFIGURATIONS FOR MPX 9500/9600 SERIES SYSTEMS ______________ ___ ___ _________ ______ _______ The maximum configuration for MPx 9500 and 9600 Series Systems, models 9530 and 9630, is the same as the maximum configuration for the MPx 9000, 9100 and 9400 Series Systems, models 9020, 9120, and 9420 with the following exceptions: 3 CPU sets with Evaluation Stack Rstack Cache Code Cache Data Cache 255 Devices 16 ISDCs: 16-ways (16 maximum) and/or 8-ways (16 maximum) 4-24 Maximum megabytes of main memory (see Hardware section for mandatory revision levels for main memory support above 12 megabytes) 16 Disk drives on model 9530, 12 disk drives on model 9630 (7.9 GB maximum), with no more than 8 14-inch fixed drives on either model 4 DMA controllers (including DMA-I, DMA-II, and DMA-III's SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB085 Pg007 in any combination.) 82 High activity concurrent tasks Models 9510/9520 and 9610/9620 have the same configuration limits as models 9530/9630 with the following exceptions: 9510/9610 9520/9620 1 CPU set 2 CPU sets (same caches as the 9530) (same caches as the 9530) 16 disk drives (9610) 16 disk drives (9620) 10 ISDCs: 16-way (5 maximum) 10 ISDCs: 16-way (8 maximum) 8-way (8 maximum) 8-way (10 maximum) 84 Devices 132 Devices 83 Serial printers 63 Concurrent tasks 91 System printers (high activity) (total serial and parallel) 52 Concurrent tasks (high activity) 3.4 CONFIGURATIONS FOR THE ADVANCED SERIES FAMILY ______________ ___ ___ ________ ______ ______ The maximum number of high activity concurrent tasks is 140 on the Advanced Series Model 63, 65 on the ADVANCED SERIES Model 42 and 40 on the ADVANCED SERIES model 20. The maximum configuration for ADVANCED SERIES model 63 is as follows: 255 Devices - A combination of 8-ways, 16-ways, and the 4 ports on the MCS/M PCBA, and MDT's up to a total of 255 devices are supported. 3 CPU's (with cache boards) 16 ISDCs: 16-ways (16 maximum) and/or 8-ways (16 maximum) 4-48 Maximum megabytes of main memory (See Hardware section for mandatory revision levels for main memory support above 12 megabytes.) 16 Disk drives (may be 300MB and 590MB fixed disks, 285 removables, or 364MB,250MB, 690MB on DMA-II for up to 11 GB maximum) 4 DMA controllers with standard backplane. Double wide backplane allows 6 DMA controllers. (The controllers may be DMA-I disk controllers for support of 285Mb removable disks and/or DMA-III disk and parallel printer controllers for support of 300Mb and 590Mb fixed disks and parallel printers) * 32 Ghost tasks 8 Parallel printers 2 Magnetic tape drives - MTR, MTS, and/or GCR (2 maximum), and/or MCS (1 maximum) 4 Intelligent Multi-Line Controllers (IMLC) 8 DataWord II terminals 4 TBC lines 64 3270 terminals 8 X.25 lines 2 Auto-Call Units (ACU) 99 Serial printers 99 System printers (total serial and parallel not to exceed 99) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB085 Pg008 2 Buffered Magnetic Tape Controllers 1 LAN controller The maximum configuration for ADVANCED SERIES model 62 is the same as for model 63, with the following exceptions: 196 Devices 2 CPU's (with cache boards) 4-36 maximum megabytes of main memory 12 16-ways; 12 8-ways The maximum configuration for ADVANCED SERIES model 61 is the same as for model 63, with the following exceptions: 148 Devices 1 CPU (with cache board) 4-28 maximum megabytes of main memory 9 16-ways; 9 8-ways The maximum configuration for ADVANCED SERIES model 42 is the same as for model 63, with the following exceptions: 132 Devices 2 CPU's (without cache) 4-24 maximum megabytes of main memory 8 16-ways; 8 8-ways The maximum configuration for ADVANCED SERIES model 41 is the same as for model 63, with the following exceptions: 100 Devices 1 CPU (without cache) 4-20 maximum megabytes of main memory 6 16-way; 6 8-ways The maximum configuration for ADVANCED SERIES model 20 is the same as for model 63, with the following exceptions: 1 chassis 52 Devices 1 CPU (without cache) 4-12 maximum megabytes of main memory 2 disks maximum; 250MB, 364MB, 690MB disks (up to 1.4GB) 2 parallel ports 3 ISDCs: 16-ways maximum 51 serial printers 53 system printers 1 BMTC 2 IMLC * For maximum performance, it is recommended that no more than 2 disks be configured per DMA. 4.0 DIAGNOSTICS ___________ NOTE: To access all of the software documented in this section, the prefix must be set to the .R6Hxx.DIAG.,.R6Hxx.INST. node. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB085 Pg009 Please see the installation sections in this announcement for instructions on how to install DEMON and REMIDI. Further information on these diagnostics can be found in DOCWRITER, which can be accessed by entering !DOCWRITER in command mode. 4.1 REMIDI ______ NOTE: UPDATE.LD needs to be run for REMIDI whenever question marks (?/?) appear in Load Sector 2 at the top of the OSINFO screen. 4.1.1 ON MPx 7000, 7100, AND 8000 SERIES SYSTEMS __ ___ _____ _____ ___ ____ ______ _______ REMIDI version BV includes all micro-diagnostics except those for the MPC and LAN controllers. It is loaded into WCS slot 2 and is used on MPx 7000, 7100, and 8000 Series Systems. REMIDI version BVM contains micro-diagnostics for the MPC and LAN controllers. It is loaded into WCS slot 3 on all 7000/7100 Series Systems and on 8000 Series Systems with LAN controllers. This version of REMIDI is used on MPx 7000/7100 Series Systems for the MPC and LAN controllers, and on 8000 Series Systems for LAN controllers only. If a LAN controller is not present on an 8000 Series System, the BVM version of REMIDI is not needed. The Load Directory controls which version of REMIDI will be executed. The UPDATE.LD utility is used to update the Load Directory. See the following section for instructions on running UPDATE.LD. UPDATING THE LOAD DIRECTORY FOR REMIDI Disregard this section if your 8000 Series System does not have a LAN controller. (In this case only REMIDI version BV is used, and it is not necessary to update the Load Directory.) Since REMIDI is a WCS Image, two WCS slots, slot 2 and slot 3, will be required for the two REMIDI versions. The extra slot is provided by the DEMON WCS slot. Because DEMON and the BOSS/VS O.S. share the same WCS, Load Sector 3 should display 3/0 or 3/1, indicating that the WCS for DEMON is in either WCS slot 0 or WCS slot 1. This leaves WCS slot 3 free for REMIDI. Only one version of REMIDI will run at a time. The version that will run is dependent on how the Load Directory for REMIDI (Load Sector 2) is set up. The standard version, BV, which resides in WCS slot 2, has an OS/WCS of 0/2. The MPC/LAN version, BVM, which resides in WCS slot 3, has an OS/WCS of 0/3. Use UPDATE.LD to update the Load Directory to designate which version to run. To test the MPC and LAN controllers with REMIDI version BVM, execute UPDATE.LD, using the inputs below: NOTE: Lines preceded by an "*" require operator input. * Input in command mode !UPDATE.LD SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB085 Pg010 Update Load Directory Utility (Version 6.5.5.0) Disks (Unit number) on line : 0(16),1(17) Enter disk number: Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 6.8.x.x R 6H*xx (date) B 6.1.x.x 1 1/1 | 6.8.x.x R 6H*xx (date) B 6.1.x.x 2 0/2 | B 6.1.x R 3 3/0 | 6.8.x.x DEMON B 6.x.x R * New OS slot (0,1,3): 0 * New WCS slot (0..3): 3 * Load sector (0..3) : 2 In this case, UPDATE.LD will then display the new Load Directory as follows: Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 6.8.x.x R 6H*xx (date) B 6.1.x.x 1 1/1 | 6.8.x.x R 6H*xx (date) B 6.1.x.x 2 0/3 | B 6.x.x R 3 3/0 | 6.8.x.x DEMON B 6.x.x R Notice the change in Load Sector 2. To go back to the standard REMIDI version, BV, which tests the CPU and main memory, use the following in UPDATE.LD: * New OS slot (0,1,3): 0 * New WCS slot (0..3): 2 * Load sector (0..3) : 2 In this case, UPDATE.LD will then display the new Load Directory as follows: Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 6.8.x.x R 6H*xx (date) B 6.1.x.x 1 1/1 | 6.8.x.x R 6H*xx (date) B 6.1.x.x 2 0/2 | B 6.x.x R 3 3/0 | 6.8.x.x DEMON B 6.x.x R NOTE: The Load Directory should stay in the above setup in case the system CPU needs to be tested in a down condition. Always use Load Sector 2 for REMIDI. ON MPx 9xxx AND THE ADVANCED SERIES REMIDI for MPx 9xxx Series Systems consists of two sections, AVA, which is loaded into WCS slot 2, and AVC, which is loaded into WCS slot 3. REMIDI for the ADVANCED SERIES family also consists of two sections, CVA, which is loaded into WCS slot 2, and CVC, which is loaded into WCS slot 3. Unlike the REMIDI versions on 7xxx/8xxx systems, the REMIDI versions on 9xxx and ADVANCED SERIES Systems, are not used independently by slot. In other words, the version of REMIDI in WCS slot 2 calls the version of REMIDI in WCS slot 3 on 9xxx and ADVANCED SERIES Systems. Load Sector 2 contains the OS/WCS pointers for REMIDI. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB085 Pg011 UPDATING THE LOAD DIRECTORY FOR REMIDI Normally, the Load Directory is updated by the operating system when REMIDI is installed with UPDATE.WCS. However, if Load Sector 2 does not reflect an O.S./WCS of 0/2, the UPDATE.LD utility can be run to update the Load Directory: NOTE: Lines preceded by an "*" require operator input. * Input in command mode !UPDATE.LD Update Load Directory Utility (Version 6.5.5.0) Disks (Unit number) on line : 0(16) 1(17) ENTER DISK NUMBER: Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 6.8.x.x R 6H*xx (date) x 6.x.x 1 1/1 | 6.8.x.x R 6H*xx (date) x 6.x.x 2 ?/? | x 6.x.x R 3 3/0 | 6.8.x.x DEMON x 6.x.x R * New OS slot (0,1,3): 0 * New WCS slot (0..3): 2 * Load sector (0..3) : 2 UPDATE.LD will then display the new Load Directory as follows: Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 6.8.x.x R 6H*xx (date) x 6.x.x 1 1/1 | 6.8.x.x R 6H*xx (date) x 6.x.x 2 0/2 | x 6.x.x R 3 3/0 | 6.8.x.x DEMON x 6.x.x R Notice the change in Load Sector 2. 4.2 DEMON - UPDATING THE LOAD DIRECTORY _____ _ ________ ___ ____ _________ Because REMIDI resides in WCS slot 3 on 7xxx and 9xxx systems and 8xxx systems with LAN, the Load Directory must point to another WCS slot for DEMON on these systems. The O.S. and DEMON share the same WCS code, therefore, Load Sector 3 should point to the WCS slot used by the O.S. Normally, this is set up by the operating system when DEMON is installed, providing that the correct answers are entered at the UPDATE.OS prompts during installation. If, for any reason, Load Sector 3 does not reflect OS/WCS as 3/0 or 3/1, you may use UPDATE.LD to change it, using the following inputs: NOTE: Lines preceded by an "*" require operator input: * Input in command mode !UPDATE.LD Update Load Directory Utility (Version 6.5.5.0) Disks (Unit number) on line : 0(16),1(17) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB085 Pg012 Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 6.7.x.x R 6H*xx (date) x 6.x.x 1 1/1 | 6.7.x.x R 6H*xx (date) x 6.x.x 2 0/2 | x 6.x.x R 3 3/3 | 6.7.x.x DEMON x 6.x.x R * New OS slot (0,1,3): 3 * New WCS slot (0..3): 0 (or 1) * Load sector (0..3) : 3 UPDATE.LD will then display the new Load Directory as follows: Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 6.7.x.x R 6H*xx (date) x 6.x.x 1 1/1 | 6.7.x.x R 6H*xx (date) x 6.x.x 2 0/2 | x 6.x.x R 3 3/0 | 6.7.x.x DEMON x 6.x.x R Notice that Load Sector 3 is now pointing to WCS slot 0. 4.3 ADVANCED SERIES ONLY ________ ______ ____ 4.3.1 HIGH FREQUENCY MARGINS ON THE ADVANCED SERIES ____ _________ _______ __ ___ ________ ______ The ADVANCED SERIES processor has the capability to run at a faster clock rate for diagnostic purposes. This capability is intended for diagnostic testing of the CPUs ONLY. The system should never be used at the higher clock rate except for diagnostic purposes. 4.3.2 USING ALT LOAD FOR REMIDI AND DEMON _____ ___ ____ _________ ___ _____ On the ADVANCED SERIES, REMIDI and DEMON can be loaded into memory from the O.S. tape via ALT LOAD and executed. To load REMIDI, load switch 2 should be on. To load DEMON, load switches 2 and 3 should be on. Pressing the ALT LOAD switch will then load the selected diagnostic into memory for execution. 4.4 DIAGNOSTIC REMOVAL __________ _______ This section describes the removal of diagnostic programs from a system. The diagnostics reside in the file system and several bootable disk slots. They are removed from the file system with the 'delete' utility. They are removed from the bootable slots by overwriting the images. The procedure follows. 1. Removing REMIDI The removal of REMIDI is accomplished by overwriting the two bootable REMIDI slots with the WCS image. 2. Update WCS Slot 2 Execute the UPDATE.WCS utility and respond to the prompts as SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB085 Pg013 shown below. ENTER WCS SLOT (0..3): - 2 AVAILABLE DISK UNITS ARE: - (displayed) DISK TO UPDATE : - Enter the disk number. WCS IMAGE FILE: - .R6Hxx.INST.WCS.X (where X = A,B,C) X = A for MPx 9xxx X = B for MPx 7xxx, 8xxx X = C for Advanced Series WCS LEVEL OF WCS IMAGE FILE: - (displayed) During the update process, the following message appears: UPDATING DISK UNIT nn SECTOR xx When the update is complete, the following message appears: WCS UPDATE COMPLETED! The preceding should be performed on all system disks. 3. Update WCS Slot 3 Execute the UPDATE.WCS utility and respond to the prompts as shown below. ENTER WCS SLOT (0..3): - 3 AVAILABLE DISK UNITS ARE: - (displayed) DISK TO UPDATE : - Enter the disk number. WCS IMAGE FILE: - .R6Hxx.INST.WCS.X (where X = A,B,C) X = A for MPx 9xxx X = B for MPx 7xxx, 8xxx X = C for Advanced Series WCS LEVEL OF WCS IMAGE FILE: - (displayed) During the update process, the following message appears: UPDATING DISK UNIT nn SECTOR xx When the update is complete, the following message appears: WCS UPDATE COMPLETED! The preceding should be performed on all system disks. 4. Removing DEMON The removal of DEMON is accomplished by overwriting the bootable DEMON slot with DEMON.UX. 5. Update OS Slot 3 Execute the UPDATE.OS utility and respond to the prompts as shown below. BOSS/VS Image File Name: - DEMON.UX SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB085 Pg014 Target OS Slot (0/1/3): - 3 Target WCS Slot (0-3): - 0 Target Drives (0/1/All/Quit): - Enter the disk number During the update process, the following message appears: Update in progress : x/y : zz% When the update is complete, the following message appears: Updates all complete. The preceding should be performed on all system disks. 6. Removing diagnostics from the file system The diagnostics are removed from the file system using the 'delete' utility. The diagnostics are found in the system node .R6Hxx.DIAG. The files in the following nodes should be deleted from the file system. .R6Hxx.DIAG. .ENHANCER6H. .TRACKER. The following files should be deleted: .AC (MPX 9000 Series 1/4" tape boot OS image with DIVE) .AT (MPx 9000 Series 1/2" tape boot OS image with DIVE) .BC (MPx 7000 Series 1/4" tape boot OS image with DIVE) .BT (MPx 8000 Series 1/2" tape boot OS image with DIVE) .CC (Advanced Series 1/4" tape boot OS image with DIVE) .CT (Advanced Series 1/2" tape boot OS image with DIVE) The following file(s) should be added as a replacement for the file(s) deleted above. .ACX (MPx 9000 Series 1/4" tape boot OS image without DIVE) .ATX (MPx 9000 Series 1/2" tape boot OS image without DIVE) .BCX (MPx 7000 Series 1/4" tape boot OS image without DIVE) .BTX (MPx 8000 Series 1/2" tape boot OS image without DIVE) .CCX (Advanced Series 1/4" tape boot OS image without DIVE) .CTX (Advanced Series 1/2" tape boot OS image without DIVE) This completes the diagnostic removal procedure! 5.0 HARDWARE ________ When upgrading to O.S. levels 9/8.6H, hardware changes, per se, are not required EXCEPT if your system contains a DMA-II. However, the following list of PCBA revision levels indicates the MANDATORY and RECOMMENDED revision levels of MPx and ADVANCED SERIES PCBA's. MANDATORY means that the specified revision level is needed for system operation. This level provides minimum assurance that your customer's system will operate in a stable manner. RECOMMENDED means that the specified revision level ensures the reliable operation of your customer's system. The RECOMMENDED (or higher) revision levels help to assure SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB085 Pg015 reliability and stability. If your customers' system PCBA's are at MANDATORY levels or below, careful plans should be made to replace the PCBA's with the RECOMMENDED (or higher) revisions. This should be done on a one per visit basis, such as one board per PM visit. DO NOT replace all PCBA's simultaneously. Some RECOMMENDED revision levels may vary based on specific system configurations, as detailed below. For example, the 16Mb High Speed Memory PCBA requires specific MCS and Terminator PCBA's. 5.1 MPX 7000, 7100, AND 8000 PCBA NOTES ___ _____ _____ ___ ____ ____ _____ 1) MCS 903374-001 PCBA Revision L is the mandatory and recommended level. Revision S adds another option to the switch setting of SW-1. SW-1 position 4 (SW1-4) is switch selectable between MPx 7000/7100/8000 Series Systems (SW1-4, OPEN) or MPx 9xxx Series Systems (SW1-4, CLOSED). If the MCS PCBA, at revision S, is switch selected for MPx 9xxx Series Systems and installed into an MPx 7000/7100/8000 Series System, it will not load. - MCS 903374-002 PCBA-Revision V Revision V creates the -002 assembly. This assembly can be used on all MPx systems. 2) MDI 903361-001 PCBA Revision L is the mandatory and recommended level. This level prevents the MDI/ACS clocks from drifting and getting out of phase, which causes "INVOP" and "NILPTR" dumps. - MDI 903408-001 PCBA Revision K is the mandatory and recommended level. This level prevents the MDI/ACS clocks from drifting and getting out of phase, which causes "INVOP" and "NILPTR" dumps. 3) ACS 903379-001/-002 PCBA's Revision L is the mandatory and recommended level. 8000 systems on OS 8.4B or above require revision L, boot prom version 2.0.0.1 or higher. 7000 systems require revision Y or above, boot prom version 2.0.0.4 or higher (MPC support). Revision level Z, boot prom version 2.0.0.2, cannot be used on 7000 systems (no MPC support). Revision levels V and W, boot prom version 2.0.0.3, is obsolete; do not use. Tape load support from a BMTC requires revision T, boot prom version 2.0.0.5 or higher. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB085 Pg016 Systems with 8-inch fixed drives require revision AA, boot prom version 2.0.0.5 or higher. - ACS 903379-003 PCBA Revision AD creates the -003 assembly. This version of the ACS PCBA can also be used in 7000/8000 systems. 7100 systems require AD or higher and this revision level is also required for support of the 120Mb MTCS tape. Board versions -002 or -003 are mandatory for 3 CPU systems, MPx 7xxx/8xxx Series Systems. 4) MPC 903500 PCBA Revision H is the mandatory and recommended level. If used in the MPx 7100 system, remove JMP3, if present, and set SW2-1 and SW2-4 OFF. - MPC 903546 PCBA Revision B is the mandatory level; revision H is the recommended level. If used in the MPx 7100 system, remove JMP3 if present and set SW2-1 and SW2-2 OFF. 5) TDP Controller 903217-001 PCBA Revision K is the mandatory level. Revision K eliminates excessive sector number errors written to the ERRORLOG. Revision W is the recommended level. This revision checks for Signetic IC's at locations 9E and 10K, if the IC's at these two locations are something other than Signetics, then this revision level is not required. Issue with 8" drives only. - TDP Controller 903453-001 PCBA New build TDP controller, which replaces TDP controller 903217-001. Revision A is the mandatory level. Revision J is the recommended level. This revision checks for Signetic IC's at locations 9E and 10K, if the IC's at these two locations are something other than Signetics, then this revision level is not required. Issue with 8" drives only. 6) NIMLC Controller 903381-001 PCBA Revision E is the mandatory level; revision K is the recommended level. This IMLC must be located to the right of the CPU set. Revision G provides correct line status for Data Set Ready (DSR), when no device is attached. Revision K is mandatory for all three (3) mainframe systems. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB085 Pg017 - NIMLC Controller 903381-002 Revision N creates this version of NIMLC for international use. It provides RS-232-C interface on Port B, using standard 1488/1489 IC's to support cabling longer than 50 feet (provides higher input impedance interface required for use on various Wide-Area Networks). - NIMLC Controller 903534-001 PCBA Revision D is the mandatory and recommended level. Provides the same interface as the 903381-002 PCBA on ports A and B. This NIMLC can be located on the left or right of the CPU. - NIMLC Controller 903251-001 PCBA This NIMLC was used with the 810 system and will not operate on the MPx series systems. 7) Memory (1Mb, 2Mb, 4Mb) 903516-00x PCBA Revision A is the mandatory level; revision E is the recommended level. Memory 903516-001 PCBA is the 2Mb version. Memory 903516-002 PCBA is the 4Mb version. Memory 903516-003 PCBA is the 1Mb version. 8) Terminator 903199 PCBA Revision D is the mandatory and recommended level. Revision H creates the -004 assembly. Revision H can be used on all MPx systems. 5.2 MPX 9XXX SERIES SYSTEM PCBA NOTES ___ ____ ______ ______ ____ _____ NOTE: An asterisk (*) appears in front of revision levels that are mandatory for main memory support above 12 megabytes. Higher revision levels may be used too. 1) MCS 903374 PCBA Revision L is the mandatory level; revision S is the recommended level. Revision S, or above, is required for reliable system operation. Revision S adds another option to the switch setting of SW1. SW1 position 4 (SW1-4) is switch selectable between the addressing schemes of the MPx 7000/7100/8000 (SW1-4, OPEN) Series Systems or the MPx 9xxx Series Systems (SW1-4, CLOSED). If the MCS PCBA is switch selected for MPx 7000/7100/8000 systems and installed into an MPx 9xxx Series System, board addresses 32 thru 47 are reserved for the IMLC PCB only. If the MPx 9xxx scheme is used then there are no address restrictions. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB085 Pg018 * Revision T is required for main memory support above 12 megabytes. Set SW1-4 to CLOSE for the 9xxx addressing scheme. * Revision V creates the -002 MCS. This revision is mandatory for support of the 16Mb memory board (P/N 903621) on 9xxx systems. It also can be used for main memory support above 12Mb. 2) AMS 903548 PCBA Revision F is the mandatory level, revision L is the recommended level. Revision F released the 4K boot proms version 3.1.0.4. This revision, or above, is required for operation. * Revision N creates the -002 PCBA and is required for main memory support above 12 megabytes. Revision P creates the -003 PCBA and is required for MPx 94xx (SCSI) systems. The -003 PCBA can be used in all MPx systems. Revision P is required for support of the 621Mb fixed disk drive and the DMA-III PCBA. 3) ESTK 903552 PCBA Revision G is the mandatory and recommended level. * Revision J, or above, is required for main memory support above 12 megabytes. 4) IDC 903550-001 PCBA (with cache) IDC 903550-002 PCBA (without cache) Revision H is the mandatory level; revision P is the recommended level. Revision J addresses cache timing problems on selected systems. Do not replace the IDC PCBA on an error free system. 5) IDC64 903597-001 PCBA (with cache) IDC64 903597-002 PCBA (without cache) Revision E is the mandatory level; revision H is the recommended level. * IDC64 PCBA is required for support of main memory above 12 megabytes. Strap E6 to E7 must be out to configure PCB for use above 12MB. 6) DMA-I 903554 PCBA * Revision H is the mandatory level; revision AA is the recommended level. Revision H is required for the 600 LPM band printer, model 20. It is also required if 300Mb 8-inch drives log excessive errors in the ERRORLOG. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB085 Pg019 Revision N is required when used with the DMA-II. Revision P, or above, is required for reliable system operation, also if the DMA-III is in the system. Revision R is required for use with the 16Mb memory board for full power fail recovery. Revision Z is required for systems that have more than 2 DMA's installed for performance. Revision AA is recommended when system also contains DMA-II. This revision eliminates soft Head/Cyl (8004) errors reported against the drives supported on the DMA-I when DMA-II installed. This revision also reports 8001 'Offline status' instead of 8002 'Not ready' when taking disk packs out of removable drives. 7) DMA-II (SCSI) 903599 PCBA Revision K required for MPx 94xx SCSI disk drive support; requires 9.6C or later O.S. and the AMS -003 version. Revision L contains a fix for excessive soft errors logged in the ERRORLOG when both DMA-I's and DMA-II's are in the same system. Revision M Creates the DMA-II -002 version. This revision has become the mandatory and recommended level. This is the mandatory level for support of the 364Mb (M380) and 690Mb (M760) SCSI disk drive. NOTE: This level of DMA-II is mandatory if n.6G OS, or above, is installed on the system. (It is also a replacement for the -001 and does not require the n.6G OS or above.) - DMA-II (SCSI) 903741 PCBA This is the new version of DMA-II due to artwork changes. It may be used in place of 903599 PCBA and visa versa. Revision E has become the mandatory and recommended revision level. This revision is mandatory for support of the 364Mb (M380) and 690Mb (M760) SCSI disk drive. This creates the -002 version. NOTE: This level of DMA-II is mandatory if n.6G OS, or above, is installed on the system. 8) DMA-III (SMD) 903679-001 PCBA The DMA-III is required for support of the F621Mb fixed disk drive. (The F621Mb disk also requires the 903548-003 AMS board.) The DMA-III revision C controller also supports the 300Mb disk drive without the use of the SMD-I/II PCBA. This controller has the SMD logic embedded. Revision E is required for DMA-I/II/III to reside in the same system. Revision G is required for systems that have more than 2 DMA's installed for performance. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB085 Pg020 Revision J is now the recommended/mandatory revision level. This level prevents possible data corruption. When a DMA-III is replaced, this level should be used. 9) NIMLC 903381-001 PCBA Revision K is the mandatory and recommended level. This NIMLC must be located to the right of the CPU set. - NIMLC 903381-002 PCBA Revision N creates this version of NIMLC for International use. It provides RS-232-C interface on Port B using standard 1488/1489 IC's to support cabling longer than 50 feet (provides the higher input impedance interface required for use on various Wide-Area Networks). - NIMLC 903534 PCBA Revision D is the mandatory and recommended level. This revision provides the same interface as the 903381-002 PCBA on ports A and B. This NIMLC can be located on the left or right of the CPU set. - NIMLC 903251 is OBSOLETE This NIMLC was used with the 810 system and will not operate on the MPx Series Systems. NOTES: There have been a few instances when a known good IMLC is installed into the MPx 9xxx system, the RED LED (Parity error) comes on during load (903534/903381). In this case, install JMP C on the PCBA. When the JMP C option is used on the MPx 9xxx system and "T0" is a serial terminal, the system will hang in the TYPE II/III load. This side effect only occurs with the 9.6A OS and is fixed in 9.6B OS and above. Refer to Field Bulletin #375. 10) Memory (1/2Mb and 1Mb) 903349 PCBA Revision V is the mandatory and recommended level. This revision is not to be used with greater than 12 megabyte support. 11) Memory (2 and 4 MB) 903516-00x PCBA Revision E is the mandatory and recommended level. Memory 903516-001 PCBA is the 2Mb version, 903516-002 PCBA is the 4Mb version. * Revision J is required for support of main memory above 12 megabytes. Support of main memory above 12 megabytes is supported on MPx 9500 and 9600 Series Systems only. JMP 5 at location 1E = 1 to 2, and IC pad location 1A = 8 to 9. 12) 16/8/4Mb High Speed ECC Memory 903621-00x PCBA SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB085 Pg021 High Speed ECC Memory 903621-001 (16Mb), -003 (8Mb), -004 (4Mb) version are supported on the MPx 9xxx Series Systems. Requires MCS -002, Terminator -004, DMA-I at revision R or above for MPx Series Systems. Revision C is the mandatory level; revision F is the recommended level. Revision G creates the 903621-005 (16Mb), -007 (8Mb), -008 (4Mb) versions. Revision N if 30 or more slots are used in 9530. 13) Terminator 903199 PCBA Revision D is the mandatory and recommended level. Revision H creates the -004 assembly, which is mandatory for support of the 16Mb, High Speed ECC memory board versions (P/N 903621). 14) Non Supported PCBA's on MPx 9xxx Series System The following boards are NOT supported on MPx 9xxx Series Systems: 1) 7000/7100/8000 CPU set. 2) TDP (Must be replaced by the BMTC for tape support). 3) MPC. 5.3 PCBA'S FOR ALL MPX 7/8/9XXX SERIES SYSTEMS ______ ___ ______ ________ ______ _______ The following are PCBA'S common to all MPx Series Systems without system model dependencies: 1) BMTC 903413 PCBA Revision R is required for full MTCS support. This is the minimum revision for support of the HCC tape unit. NOTE: The HCC is supported on the MPx 9xxx and Advanced Series systems only. Revision U is required for support of the GCR 1/2" tape drive model 4405. Revision Z allows the BMTC to operate on the left or right side of the CPU set. 2) Local Area Network Controller (LAN) 903595 PCBA Revision E is the mandatory level; revision F is the recommended level. With the release of the 9.6A/8.6A O.S., a new controller is supported: The Local Area Network controller. The LAN PCBA provides the ability to tie like systems together (MPx to MPx) in a local environment not more than 4000 feet apart. Each system requires one LAN controller, and both systems must be on the same O.S. level. The LAN may be installed SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB085 Pg022 either to the right of the CPU set(s) after the BMTC PCBA or to the left of the MCS PCBA. Refer to the MAGNET section in this document for further information on the Local Area Network. Revision H creates the -002 version. This version can be used on all MPx series systems and ASxx systems. 3) 16-Way Controller 903437 PCBA 16-Way controllers require the use of an I/O panel. The I/O panel is supplied with the purchase of the PCBA. Revision J is the mandatory and recommended level. Revision R creates the -002 version that supports hardware flow control with the n.6H, or above release of software. Cable PN 916509, revision B, must also be used for this feature. 4) 8-Way Controller 903383 PCBA Revision A is the mandatory and recommended level. 5) VCON Controller 903377 PCBA Revision C is the mandatory and recommended level. 5.4 ADVANCED SERIES PCBA NOTES ________ ______ ____ _____ The following are PCBA's that are supported on the ADVANCED SERIES and their revision levels. NOTE: An asterisk (*) appears in front of revision levels that are MANDATORY for the Doublewide backplane chassis. A pound sign (#) appears in front of revision levels that differ form the minimum revision levels of the Advanced Series systems. These revision levels are MANDATORY for the Advanced Series model 21 system. 1) MCS/M 903718 PCBA Revision G is the released level of this PCBA. The MCS/M (Memory Communication Support with Memory) PCBA provides boot load function/clocks/4-way and 4Mb of main memory. # Revision H (-002) is the mandatory level for support of the DMA-II PCBA and the SCSI disk drives on the Advanced Series system. Revision J required for 19.2K Baud and 7/8 bit data support for T0. 2) NEP II 903705 PCBA Revision G is the mandatory level; heat-sink added. Revision J recommended. * Revision K is the mandatory level when used in the Doublewide backplane chassis. This is also the recommended level for the model 21 system. 3) STACHE II 903707 PCBA SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB085 Pg023 Revision D is the released level of this PCBA. The STACHE II PCBA is an optional PCBA that makes up the Advanced Series Model 6x. It contains the Rstack, Code Cache, and Data Cache. * Revision F is mandatory for Doublewide backplane chassis. 4) MBA 903617 PCBA Revision D is the released level of this PCBA. The MBA (Memory Bus Adapter) PCBA is required to support the shared memory controllers developed for the MPx 8/9xxx systems (160ns clock) on the Advanced Series Models 40/60 (80ns clock). Revision E is mandatory for support of the Advanced Series system. # * Revision H is mandatory for the Doublewide backplane chassis. This is also the recommended revision level for ALL Advanced Series systems. 5) BMTC 903413 PCBA Revision Z is mandatory for support of the Advanced Series systems. 6) LAN 903595-002 PCBA Revision H creates the -002 version, this version is mandatory for support of the Advanced Series systems. 7) DMA-I 903554 PCBA Revision R is mandatory for support on the Advanced Series, due to the 1Mbit rams used for main memory (MCS/M and 16Mb PCBA's) and full power fail recovery. Revision T corrects a problem in Revision R firmware which caused the timeout LED (DS2) to turn on during REMIDI testing in the Advanced Series family only. Revision Z is required for systems that have more than 2 DMA's installed for performance. Revision AA is recommended when system also contains DMA-II. This revision eliminates soft Head/Cyl (8004) errors reported against the drives supported on the DMA-I when DMA-II installed. This revision also reports 8001 'Offline status' instead of 8002 'Not ready' when taking disk packs out of removable drives. 8) DMA-II (SCSI) 903599-002 PCBA The DMA-II requires the MCS/M -002 for support. Revision M is mandatory for support of the 364Mb (M380) and SCSI 5-1/4 inch disk drive. This revision creates the -002 version. Revision N is the mandatory revision level if the Advanced SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB085 Pg024 Series system contains more than 4MB of main memory using the 903621-00x High Speed ECC memory. - DMA-II (SCSI) 903741-002 PCBA The DMA-II requires the MCS/M -002 for support. Revision E is mandatory for support of the 364Mb (M380) and 690Mb (M760) SCSI 5-1/4 inch disk drive. This revision creates the -002 version. Revision F is the mandatory revision level if the Advanced series system contains more than 4MB of main memory using the 903621-00x High Speed ECC memory. 9) DMA-III (SMD) 903679-001 PCBA The DMA-III is required for support of the F621 (600Mb) disk drive. It also supports the (300Mb) disk drive without the use of the SMD-I/II PCBA. This controller has the SMD logic on board. Revision E supports the DMA-I and DMA-II is also in the system. Revision G is required for systems that have more than 2 DMA's installed for performance. Revision J is now the recommended/mandatory revision level. This level prevents possible data corruption. When a DMA-III is replaced, this level should be used. 10) IMLC 903534 PCBA Revision D is mandatory for support of the Advanced Series. This version of IMLC, at the indicated revision level, is required to function on the left side of the CPU set. Remove JMP C if installed. 11) 16/8/4Mb High Speed ECC Memory 903621-00x PCBA Revision G creates the -005 (16Mb), -007 (8Mb), -008 (4Mb) versions. Refer to DMA-II section for other concerns if DMA-II is in the system. # * Revision N is the mandatory level. This revision helps prevent the possibility of parity errors during Nibble Mode cycles (Code Cache). 12) 8-WAY 903383 PCBA There is no mandatory revision level required for support of this PCBA on the Advanced Series. 13) 16-Way 903437 PCBA Revision J is LARL for support on the MPx and Advanced Series. Revision R creates the -002 version that supports hardware flow control with the n.6H, or above release of software. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB085 Pg025 Cable PN 916509, revision B, must also be used for this feature. 14) Terminator 903199-004 PCBA Revision H is the mandatory level, and it creates the -004 version. 15) Terminator, High Speed 903769 PCBA * Revision A releases the High Speed Terminator, mandatory in Doublewide chassis. 16) LS-700 Power Supply Assembly 907295-001 If any MPx 8000 system is being upgraded to the Advanced Series family, the LS-700 assembly 907295-001 must be at revision AA. (PCBA 903386-001, inside the LS-700 assembly, will be at revision AB or above.) If any MPx 9xxx system is being upgraded to the Advanced Series family, the LS-700 power supply does not need to be replaced. The load sustained by this power supply under the 9xxx configuration gives sufficient evidence that the existing revision level is adequate for the Advanced Series. 5.5 PCBA'S NOT SUPPORTED ON ADVANCED SERIES ______ ___ _________ __ ________ ______ The following boards are NOT supported on the Advanced Series family: 1) 7x00/8000/9x00 CPU sets. (Use Advanced Series 40/60 CPU's) 2) MCS PCBA. (Use MCS/M) 3) MPC, TDP and DMA-II-001. (Use DMA-I, DMA-II-002, and DMA-III) 4) Memory 903349 (1Mb assembly), 903516 (4Mb assembly), 903621-001/-003/004. (Use 16Mb: -005, 8Mb: -007, 4Mb: -008) 5) VCON PCBA and HVDT's 6) Terminators -001 (Below revision H). (Use -004) 5.6 PERIPHERAL DEPENDENCIES __________ ____________ 5.6.1 GCR TAPE DRIVE ___ ____ _____ It is possible for a hang condition to occur in SAVERESTORE, if the GCR tape drive does not have the following minimum revision levels: IF CARD 403923205 (Previously, the LARL was 403923202) CP CARD 403864305 (Previously, the LARL was 403864303) 5.6.2 SCSI MTCS TAPE DRIVE ____ ____ ____ _____ On the SCSI MTCS 1/4-inch tape drive (4406), the E-PROM (OEM PN 966039; MBF PN 400716-103) at location 'U6' should be 3X10. This tape drive is used on MPx 94xx systems only. Requires the DMA-II for support. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB085 Pg026 5.6.3 HIGH CAPACITY CARTRIDGE (HCC) TAPE DRIVE ____ _________________ _____ ____ _____ The HCC tape drive is supported on the MPx 9xxx and Advanced Series only. It requires the n.6G OS, or above, and the BMTC controller. The BMTC must at least be revision R or higher. The revision is dependent on other tape devices that may be attached to the same BMTC. Refer to the BMTC sections, under your system model. 5.6.4 TERMINALS _________ 1) The DT-4313 terminal must have REV E firmware to support Industry Standard slave printers. 2) T0 MUST be a model 4309 or later model VDT. VDT's 7250 and 7270 (4301) are not supported as T0 on release levels n.6C and above due to default terminal driver change. This change corrected the time differences seen in Saverestore Type I vs Type II load. 3) OS level n.6E and above loads T0 with defaults when going into a Type 2 or 3 load. After reloading the system, these settings remain loaded in the terminal. If T0 is configured to settings other then the default values, the terminal will need to be reset. Defaults = EVDT, 9600, 7-bit, ODD Parity. The MCS/M at revision J, used on the Advanced Series systems, allows T0 to use 19.2K baud. 5.6.5 DISK DRIVES ____ ______ 1) The 590Mb (aka F621/600Mb) fixed disk requires the -003 version of AMS PCBA P/N 903548 when used in 9xxx systems. The F621Mb disk is supported by the DMA-III controller, P/N 903679. Supported on n.6E OS or above. 2) The 300Mb (aka P314) fixed disk requires revision AA of ACS PCBA P/N 903379 when installed on MPx 7xxx/8xxx systems. TDP (PDC) controller P/N's 903217 and 903453 require IC's OTHER THAN Signetics (indicated by a bold 'S') at locations 9E and 10K (74S240). 3) The 364Mb (aka M380) SCSI 5-1/5 inch disk drive requires n.6G OS or above and the -002 version of the DMA-II. See MCS/M and DMA-II for other requirements on the system that it will be installed on. 4) The 690Mb (aka M760) SCSI 5-1/4 inch disk drive requires n.6G OS or above and the -002 version of the DMA-II. See MCS/M and DMA-II for other requirements on the system that it will be installed on. 5.7 HARDWARE FLOW CONTROL - NEW FEATURE ________ ____ ________ ___ _______ With this release the 16-way will support uni-directional hardware flow control. The 16-way that supports this feature is PN 903437-002, revision R or above. A new I/O cable will SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB085 Pg027 also be required for support of this feature, PN 916509, revision B. The device will be able to throttle the host, but the host will not throttle the device. (This will cure the 'Data Loss' problem that occurs with ISP printers when they are turned off.) Flow control is implemented by monitoring the CTS signal of the interface. If CTS drops, the host will cease transmitting until CTS is detected or until a specified timeout has occurred. If the timeout occurs, a "timeout" error will be returned to the user. The timeout value is reset for each character transmitted. This means that if CTS drops multiple times during a transmission, 5 seconds (for example) will be allowed for each detection of CTS dropping. Hardware flow control is available for any serial device except for SPE.MODEM. Hardware flow control must be configured in TERM.CONFIG for it to be operational. Enter the extended options menu from the port main menu and the option will appear: USE CTS FLOW CTL (Y/N) Enter a 'Y' to have the system recognize CTS flow control for this device. Hardware flow control requires a new cable; 916509-xxx. This cable comes with a 15 pin connector designed to be attached to the backpanel serial connector. ORIGINATOR: MBF SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB085 Pg028 FIB 00086 05/21/90 *** IMLC Won't Work After Upgrading to 10/9/8.6H O.S. *** SYMPTOM: After upgrading the OS to 9.6H the IMLC won't work.It goes through all the motions (gives start time,# of polls, down.load was successful) but the modem won't answer and no link is established. FIX: The TBC translation file "TRNCD" must be erased.This file will automatically be created when you run "BCOM" and can be found in the BCOM data prefix. Eg: >ERASE "TRNCD" >RUN "BCOM" NOTE:You may have to erase the "TRNCD" file from more than one directory. SEE SOFTWARE ANNOUNCEMENT 10/9/8.6G FOR MORE INFORMATION (3.8.7 upgrading TBC) ORIGINATOR: Bob Berard SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB086 Pg001 FIB 00087 08/17/90 *** !PHOTO & 'TR' Lose Screen Data (Garbled Data Received) *** SYMPTOM: !PHOTO and the 'TR' (read screen) mnemonic lose characters from the terminal screen. !PHOTO loses about four characters in the 12TH line, the 'TR' mnemonic loses 3-4 characters from the home position as well as losing 3-4 characters in the 12TH line. No errors are posted to the terminal errorlog. FIX: There was an 'ET' mnemonic (end type ahead buffer) inadvertantly inserted in a common program accessed by all users, this disabled the type ahead buffer (and buffer overflow checking) throughout the current sign-on. There should be a corresponding 'BT' mnemonic (begin type ahead buffer) for each 'ET'. NOTE: Once 'ET' is in effect the input buffer is disabled until the user signs off or a 'BT' mnemonic is executed. ORIGINATOR: Norm Jones SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB087 Pg001 FIB 00088 10/10/90 *** Release 8/9/10.6H*41 Available to Fix These Problems *** M6H*41 is now available. This release fixes the following problems that were reported on M6H*34/36. 1. After upgrading to M6H the system will dump in a T1LD if the spooler had jobs in the queue from the previous release. 2. Printer will pause when printing 5 to 15 lines. 3. !BROADCAST causes data to dump to a Terminal that is connected to a MUX/MODEM or a A/B Switch box. 4. Spooler dump when stopping a job that is defined for '8L' and you turn the printer offline and try to stop the job using the "IMMEDIATE" mode. 5. PT-4220 loses 'VT' after each job. You have to do a !SETFORM after every job. 6. PT-4224 loses data while slewing. 7. Stopping a job using "CURRENT PAGE" option will not stop the job or it will take a long time to stop. 8. If you have a Job printing to a BAND printer and this job is using 'VT' you will lose the 'VT' if you a open this printer using a different form. 9. Printer will lose Top of Form (slewing or 'VT') if you stop and restart the job thru the Spooler Job Maintenance Utility. 10. We will include the source translation tables for all released tables. 11. 'PM' mnemonic does not work the same as on M6G. 12. PT-4217/18 will change from 10 CPI to 17 CPI after sending a from feed when the printer is using a form defined for 8 lines per inch. You can order this release thru Software Distribution, new orders for M6H will receive the M6H*41 release. ORIGINATOR: Joe Melendez SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB088 Pg001 FIB 00089 11/27/90 *** Upgrade Procedure for TBC & MAGNET for M.6H Reguired [ WPSF 644 ] *** TYPE: Problem PURPOSE This Field Bulletin was released due to the number of calls requesting the procedure to upgrade TBC and MAGNET to M.6H. Since no enhancements were made to any communication products from M.6G to M.6H, the communications upgrade procedure was excluded from the M.6H software announcement. SYMPTOM If upgrading from a release prior to M.6H an upgrade procedure must be performed. A DOWN.LOAD will occur when starting BCOM if the upgrade procedure was not performed. SOLUTION Upgrading TBC: 1. Bug fixes have been made to the TBC translation file "TRNCD" therefore, you must erase it. This file will automatically be recreated when you run "BCOM" and can be found in the BCOM data prefix. Eg: >ERASE "TRNCD" >RUN "BCOM" NOTE: You may have to erase the "TRNCD" file from more than one directory. Since 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. 2. If you work with over 99 terminals on your system, delete the "BWORK" file in your BCOM data prefix. This file will be recreated when you run "BCOM". You can display your data prefix by selecting option 7, 'TASK PREFIX UTILITY', from the BCOM main menu. Upgrading MAGNET: 1. Add the following command to the ".SYSDATA.START.CMD" file. !GROUP.CREATE REMOTE TYPE=SYSTEM PRIORITY=3 RUNJOBS=99 MAXJOBS=99 DEVICES=" " 2. Delete the RSM server definition file "DEFNS". This will be recreated when you startup MAGNET. !DELETE .SYSDATA.SERVERS.DEFNS RELATED DOCUMENTATION M.6H Software Announcement Number 166. ORIGINATOR: Frank Csete SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB089 Pg001 FIB 00090 01/07/91 *** Notes & Special Considerations for BOSS/VS M6H [ WPSF 634 & A ] *** LEVELS 10/9/8.6H TYPE: Informational These Warnings and Special Considerations are applicable to release levels 10/9/8/6H. This Field Bulletin is part of an effort to expand the reporting of known problems and special considerations to the field. C O N T E N T S 1 Notes and Special Considerations 1.1. Different O.S. Levels in Adjacent Slots 1.1.2 SECURITY.DATA file 1.1.3 Downgrading from 10/9/8.6H Releases 1.1.4 Software Announcement on Tape 1.2 Diagnostics Removal 1.3 UTILITY 1.3.1 DIR 1.3.2 ALB (Auditor Log Book) 1.3.3 COMMAND DEFINITIONS MANAGER 1.3.4 COMPARE 1.3.5 ERRORLOG 1.3.6 EXAMINE 1.3.7 FINDEXTENTS 1.3.8 GSR ( Global Search and Replace) 1.3.9 SAVERESTORE 1.3.10 SPOOLER/PRINTER 1.3.11 RENAME 1.3.12 UPDATE 1.3.13 UPDATE.RIGHTS 1.3.14 DISKANALYZER 1.3.15 TERM.CONFIG 1.3.16 EXTTAPE 1.3.17 CONFIG.MGR 1.3.18 MCSI 1.3.19 PHOTO 1.4 BASIC 1.5 CLI (Command Language Interpreter) 1.6 TBC COMMUNICATIONS 1.7 FILE SYSTEM 1.8 JOB MANAGER 1.9 FTF (File Transfer Facility) 1.10 ENHANCER TOOLS 1.11 MAGNET SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB090 Pg001 1.12 TERMINALS 1.13 ATP (Asynchronous Transport Package) 1.14 HORIZONTAL SOFTWARE 1.0 NOTES AND SPECIAL CONSIDERATIONS The following problems are reported for the M6H*37 or higher release. For Spooler problems reported on M6H*34/36 please refer to Field Bulletin #635. After upgrading to this release, the utility TERM.CONFIG must be executed to convert the TERMINALS DEFINITION files to the new format. For systems that have MAGNET and/or TBC and are upgrading to M6H from a O/S release prior to M6G, please refer to the M6G Software Announcement on how to do the MAGNET and/or TBC upgrade. If upgrading from M6H*34/36 to M6H*41 you should check PRCONFIG to make sure that your printers are set up correctly. The PRCONFIG utility is used to update the printer configuration on M6H. At boot time, the SPOOLER will look at the .SYSDATA.PRINERS.CONF file to configure the printers. If this file does not exist at boot time, the SPOOLER will create one, and on M6H*37 it has been changed to default ALL parallel printers to be multi-buffered. If the configuration file already exists, then the SPOOLER will use the default defined in the file. To clarify this further, upgrading from M6G to M6H will bring all parallel printers up in multi-buffered mode since the configuration file does not exist on M6G. On the other hand, upgrading from M6H*34 to M6H*36 or above, will not change the configuration unless one has either deleted or updated the PRINTERS.CONF file. At any rate, PRCONFIG allows the user to switch the buffering mode, and a system boot is required for the mode change to take place. 1.1 Different O.S. Levels in Adjacent Slots As of release 9/8.6C, positioning of the image slots has been adjusted slightly. Therefore, OS/WCS levels previous to 9/8.6C cannot reside in slots on the same disk with released levels 9/8.6C and above. 1.1.2 SECURITY.DATA File The SYSDATA.SECURITY.DATA file is converted to a new format during an upgrade to O.S. levels 9/8.6C and above. This converted SECURITY.DATA file cannot be used on O.S. levels previous to 9/8.6C. Therefore, if you are upgrading to 10/9/8.6C or above from a release prior to 9/8.6C, the SECURITY.DATA file should be saved on the previous release before the upgrade. In the event of a downgrade, this old SECURITY.DATA file must be restored on the previous O.S. level. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB090 Pg002 1.1.3 Downgrading from 10/9/8.6H Releases The only acceptable downgrades from 10/9/8.6H releases are to 10/9/8.6G, 10/9/8.6E or 9/8.6C releases. Downgrades to releases prior to 9/8.6C *11 may potentially cause control segment corruption. If a downgrade is performed to a release prior to 9/8/6C, the user's files must be transported to the older O.S. level via EXTTAPE, MCSI, FTF, TBC or ATP. The volume label on the system disk must also be rewritten on the older O.S. level. The format of the .SYSDATA.TERMINALS.DEFN1 and .SYSDATA.TERMINALS.DEFN2 have been changed on this release (M6H). Please save these files on the previous release before upgrading to the M6H release. You must restore these files if a downgrade is necessary. The format of the .SYSDATA.SPL.FORMS, .SYSDATA.SPL.REQUESTS and .SYSDATA.SPL.JOBIDS have been changed on this release. Please save these files in case a downgrade is necessary. Also due to these changes, it is not recommended that previous O.S. releases reside on the same system disk with the M6H release. (If you try to reboot from a previous O.S. release, the system will dump. You will have to delete the .SYSDATA. TERMINALS.DEFN1 and DEFN2, .SYSDATA.SPL.FORMS, REQUESTS and JOBIDS and restore these from a backup of the previous release or after deleting these files and rebooting the previous release, re-enter the TERM.DEFN1 and DEFN2 (TERM.CONFIG) and all forms defined for spooling). 1.1.4 Software Announcement on Tape The 10/9/8.6H Software Announcement exists as a serial file on the O/S release tape. The name of the file is: .R6Hxx.INST.DOC.ANNOUNCE6H (xx=release level). This file can be restored and SUBMITTed to a printer. When upgrading or installing a system, please refer to this Software Announcement. 1.2 Diagnostics Removal Starting with the 10/9.86G O/S release, customers that have not signed a Diagnostic Product License Agreement will receive a O/S tape that does not contain the DEMON, REMIDI or Enhancer/Tracker tools. (Enhancer/Tracker are now included as part of the Diagnostics tools and released accordingly). These tools must be removed from the system. (Please refer to the M6H Software Announcement for removal procedures). This is a U.S./Canadian policy only. 1.3 UTILITY 1.3.1 DIR 1. SPR 521415 - !DIR (FAMILYNAME).*! will display no file found even if FAMILYNAME is not enabled. 2. SPR 522725 - !DIR does not accept a MB IV to exit at the " 'CR' to continue " prompt, if files have ALB turned on. 3. SPR 520549 - Display a Multi-key file and chose the option "'F' = Format String" might give you a "String Limit SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB090 Pg003 Exceeded" error. (1,233,0,32) 1.3.2 ALB (Auditor Log Book) 1. SPR 521840 - "MAGNET SHUTDOWN COMPLETE" error might occur if you try to delete a file that has ALB turned on and you: A) Change the System name. B) Take a removable pack that has this file to another system. C) Reboot the system with another BOSS pack and it has a different System name. The file has the full file name (including the installation name) and when trying to delete this file the system tries to access the installation name. 2. SPR 521248 - You will get an error 32,116,59,3 (Invalid Software Key for ALB), if you copy a file that has ALB turned on to a system that does not have ALB installed and try to delete this file on the system that does not have ALB installed. The file will be deleted so you should just ignore the error. 3. SPR 522668 - Dump 2,10,6,32 (Instruction Fault File System Module) and 1,241,0,32 (String Limit Exceeded) will occur when you try to copy a file with ALB turned on and the log file is on a different family and the length of the file name is greater than 25 characters (does not include Installation name, Family name, or "()[]"). 4. SPR 521712 - You will get a "LOG File not found" error if you do the following: A) Set your prefix to a Family that is not enabled. B) Create a file using the !CREATE utility and specify AUDIT LOGGING ="Y". The AUDIT FAMILY NAME will de- fault to the Family that is not enabled. C) After "ENTRIES CORRECT " ="Y" you will get the error. 5. SPR 523325 - Under certain conditions (Please call FPS for details) using ! UPDATE from the command line mode and using ALB may cause an error 16,37,17,47 (Invalid number of Log records parameter). 6. SPR 523804 - DUMP 2,10,38,25 (Instruction Fault in File System Multi-Keyed Files Module) and 1,157,34,25 (Nil Pointer) will occur if you COPY/SAVERESTORE a MK-File that has ALB turned on to a system that does not have ALB and you try to write to this MK-file. WORKAROUND: Is to turn ALB off for the file before the COPY/SAVERESTORE. 7. Audit logging is not supported on files with special character file names. 1.3.3 COMMAND DEFINITIONS MANAGER SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB090 Pg004 1. SPR 524938 - Change the CMDDEF.DATA for the BBXREF utility from Formated to Unformated but using BBXREF to list programs will always list these formated. 1.3.4 COMPARE 1. SPR 520420 - Comparing files with only one record will always compare even if the records are different. 2. SPR 518626 - Indexed and Direct files will not display the first byte. EXAMPLE: Write to the Indexed and Direct file a record "ABCDEF", compare these files and it will display "BCDEF"; it will not display the "A". 1.3.5 ERRORLOG 1. SPR 522220 - When listing tape unit errors, the unit numbers will change but the device name will remain the same. When you list the errorlog, you will see that the unit number will change. (EXAMPLE: 624 to 632, but the device name will always be R0.) 1.3.6 EXAMINE 1. SPR 516693 - Using Quiet =T will hang a terminal. EXAMPLE: !EXAMINE DIRECTFILE, FORMAT=KEY, OUTPUT=LP, QUIET=TRUE. The same example with QUIET=FALSE will work without problems. 1.3.7 FINDEXTENTS 1. SPR 521274 - If you output to a file that exists, it will overwrite the file and you will lose whatever information the old file had. 1.3.8 GSR (Global Search and Replace) 1. SPR 522527 - Will not always replace the search pattern when token characters are used. EXAMPLE: 10 B$=B$(X+2) 20 BB$=B$(X+2) Enter "R" to search and replace, enter %B as the start specifier and enter BF$ as the replace pattern. The result will be that: 10 BF$=BF$(X+2) (Correct) 20 BB$=B$(X+2) (Incorrect, should have been BB$=BF$(X+2) ) 2. SPR 520970 - Files are not locked while running GSR. This can be a problem if someone else is using this file (data can be lost). 1.3.9 SAVERESTORE SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB090 Pg005 1. SPR 525594 - Invalid file name message when trying to backup a single file with special characters . Eg : %5#GHIS 2. SPR 526770 - If you save files which have a "]" in the filename, SAVERESTORE will save them and compare them without problems but if you try to list the tape directory (Option 4) you will get a four tuple of (1,20,0,32 - Insert or Concatenate into a string which is not long enough). 3. SPR 522724 - Saverestore only supports filelist of about 1100 entries which is not enough for large systems. 4. SPR 518915 - Masking capabilities do not work the same as with other utilities. Some masking capabilities that can be used in the COPY utility will not work in the SAVERESTORE utility. A number of masking problems have been reported by the field: A) SPR 514224 - Doing a compare with MASKING will not compare all files correctly. B) SPR 521707 - Restoring using RENAME delimiter will restore the file with an incorrect destination name. EXAMPLE: .^R6G43.BURN.,(DISK).^ should restore the files as (DISK).R6G43.BURN.AUTO but the files are restored as (DISK).AUTO. 5. On 8.5C/9.5C the three ISDC code files (ETWYOS, FOWYOS, SXTNOS) and the REMIDI files were changed to be unorganized (UNO) file types. This was done so DISKANALYZER would no longer flag these files as having as internal file problem. Files that are typed as unorganized were not supported by SAVERESTORE and the File System in releases prior to 8.5C/9.5C, so these files are rejected when an attempt is made to restore them on prior O.S. levels. This is why an ALT LOAD from tape must be done before the O.S. files are restored when upgrading a system that is currently on a release prior to 8.5C/9.5C. (The only exception to this is an upgrade from 8.4E. The same changes to the above 8.5C/9.5C files were also made to the 8.4E files.) 1.3.10 SPOOLER/PRINTER 1. SPR 525264 - Hitting 'ESCAPE' on a terminal that has a PT-4225 slave printer printing might cause the terminal and slave printer to hang. You will have to turn OFF/ON both the terminal and the slave printer in order to unhang these devices. 2. SPR 527049 - MBF serial printers might lose DATA after an ERROR=0 if the print job is not being spooled. This is because the print information has been sent to the printer buffer and when an ERR=0 occurs (Paper out, Printer Off-line, etc) you can lose what is in the buffer. The system does not know that this information was not printed and will continue with the next line/lines of data. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB090 Pg006 EXAMPLE: 80 FOR X =225 TO 250 90 PRINT (1,ERR=200)CHR(X), 100 NEXT X 110 PRINT (1,ERR=200)'LF' 120 END 200 PRINT "ERR=",ERR, "ON PRINTER"; WAIT 2 ;RETRY Data is kept in the printer buffer until the 'LF', if a error 0 occurs in the FOR/NEXT loop all data in the printer buffer will be lost. WORKAROUND: Spool all print jobs. 3. SPR 521588 - Printing a job that has a greater number of characters than what a printer can support will cause that printer to hang. EXAMPLE: Set a form that has 511 CPL to a Whisper printer and send a line with 256 characters in compress print ('16') to this printer, the Printer/Job will hang. 4. SPR 521669 - Powering serial printers OFF and ON will produce an error=0 when trying to print to these printers. Please refer to Field Bulletin 343A for more information regarding problems when powering serial printers OFF/ON. 5. SPR 522343 - Error=0 (Slave Printer Off-line) will occur after you 'ESCAPE' from a program that is printing to a slave printer. 6. SPR 521170 - Using 'PG' will result in a timeout error (err=0) with a PT-4224 slaved to a DT-4314. 7. The Spooler does a automatic form feed at the start of a print job after rebooting a system, even if the CLASS is set for "No form feed at start". This will happen to the first job sent to the printer after rebooting a system. 8. SPR 509923 - The FORM utility does not allow over 14 individual printers to be entered for a specific form. 9. The SPOOLER NOTIFY function, which broadcasts a message to the top of a terminal screen when a print job has finished, will cause the screen to scroll if the cursor is on the last line of the screen. 10. SPR 514941 - Although SPOOLON appears on the SUBMIT and CLASS screens and is documented in the User Manual, assigning 'F' to this option does not RESERVE a printer on MPx 9/8.6 systems. SPOOLON is always 'T' (TRUE) meaning spooling is on. The RESERVE command should be used in place of SPOOLON = F. 11. RSC 512943 - Spool jobs sometimes print on the wrong form before SETFORM can be run. WORKAROUND #1: RESERVE the printer. WORKAROUND #2: As follows: SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB090 Pg007 a) When the spool job (i.e. for payroll) is created, specify LOADFORMS = YES. This can be done on the SUBMIT screen or the "ATTR=" parameter on the BASIC OPEN statement. (The LOADFORMS option on a job can also be modified through Job Maintenance or SPJOB.MODIFY after the Spool job has been created.) This will cause the job to wait for a SETFORM before printing. The Spooler status will display "WAIT FORMS" when the job comes up in the status queue. b) When it is time to print the job on a special form (i.e. paychecks), SUSPEND the printer at the end of the current job (WHEN = J). c) Mount the special forms in the printer (i.e. paychecks). d) Run SETFORM (with the Trial Form Option, if desired). e) Move the printer to Spool mode. 12. SPR 518930 - Doing a DOWN.LOAD on an ISDC controller causes any spooled print jobs that are currently printing on serial printers attached to that controller to stop. The Spooler will show a "Stopped" status for these jobs, along with the fourtuple 31,0,9,2 (Power Failure Error). These print jobs must be restarted in the Spooler after the DOWN.LOAD. This is according to the design of the 9/8.6 spooler. 13. SPR 528669 - Hardware Flow Control does not work at 19200 baud rate. 14. SPR 528617 - UPD printers do not update % complete in PRSTATUS if print jobs are using 'VT' or slew controls. UPD printers can not stop at end of current page, if you stop this job using the "immediate" option you cannot restart this print job (using restart). It will always start at the beginning of the job. 15. SPR 529654 - Printers configured with CTS Flow Control will produce an I/O ERROR if the printer was turned off when the system was rebooted. WORKAROUND : Perform a !DOWN.LOAD on the controller that has this printer configured. 16. SPR 529596 - Print (x)@(15),'PM',A$ - will produced 15 dots instead of 15 spaces on PT-4201 printers. 17. SPR 529518 - Printers will hang if you use 'BU' after certain print positions. Example : PRINT (x)@(109),'BU',"THIS IS A TEST" 18. SPR 529494 - PT-4213 printers will print in compressed mode after doing a 'SL',A$,'EL', Example : 10 OPEN(1)"P1" 20 DIM A$(66,"0");A$(1,1)="1" 30 PRINT (1),'SL',A$,'EL', SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB090 Pg008 40 PRINT (1)"THIS IS THE FIRST LINE"; REM " WILL BE IN COMPRESSED PRINT" 50 END 19. SPR 529273 - Spooler dump 2,10,33,25 - 1,230,0,25 with UPD printers if you you do not have these printers configured in PRCONFIG. 20. SPR 528198 - Spooler dump 2,10,33,25 - 1,146,0,11. 21. SPR 529642 - Printing multi copies when in BC/FO mode when the printer is RESERVE will fail after a number of copies. Also if a form is set for 8LPI you will not be able to print in BC/FO. 22. SPR 529691 - The following program will shift 1 line between page 1 and page 4 on PT 4217/18 printers : 10 BEGIN 20 FOR X = 1 TO 4 30 OPEN(1)"P1" 40 DIM A$(66,"0"); A$(1,1)="1" 50 PRINT (1)'SL',A$,'EL', 60 PRINT (1)"----------------" 70 CLOSE (1) 80 NEXT X 23. SPR 528318 - Spooler dump 2,10,33,25 - 1,80,0,25. 1.3.11 RENAME 1. SPR 522457 - After getting a valid "Insufficient Priviledge " error any subsequent attempt to use this utility will result in the following message: "Port must be closed for current operation and is open". After getting the "Insufficient Priviledge" message, you must first exit completly out of the utility and then you can re-enter it without problems. 1.3.12 UPDATE 1. SPR 521592 - After using this utility to add more records to a file, if you use DISKANALYZER on this file it will report ERR=29 (Unaccounted Space for this file). 2. SPR 522830 - If you use this utility more than once to add records to a file (same file used twice in UPDATE), when trying to add a new record after the second time that this file has been thru the UPDATE utility you will get an ERROR=2 and DISKANALYZER will give you ERR=29 (Unaccounted Space for this file). You must RECONSTRUCT this file in order to correct the errors. EXAMPLE: A) Create a Sort file with 100 records and Key size of 16. B) Write a program to fill this file and get an error=2. C) Run !UPDATE and add 15 records (After this if you check this file with DISKANALYZER it will report the error=29, but the file is not yet corrupted). SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB090 Pg009 D) Write 15 more records to the file and you will get an error =2. E) Run !UPDATE again to add 15 more records. F) Try writing a new record and you will get a false error=2. The file is now corrupted and you must RECONSTRUCT this file. WORKAROUND: Add enough records to the file the first time you use !UPDATE or after using !UPDATE, reconstruct the file. 1.3.13 UPDATE.RIGHTS 1. SPR 520159 - You will get a "User's Rights Specification" error when a file has more than one line of User's Rights. 1.3.14 DISKANALYZER 1. SPR 523806 - While running option 5 (DISK SPACE USAGE) you might get LOGGED-OFF the system if the Available Space file (AVSP) is very fragmented (close to 2000 extents). This problem will occur more often on large capacity disk drives. 2. SPR 520888 - Will show files with 0 records but !DIR will show that these files do have records. 3. SPR 521404 - Option 1 (Find files that lack integrity) will find files with problems (Invalid Format) but, option 3 (Validate and Reconstruct) will not show any problems with this file. 1.3.15 TERM.CONFIG 1. RSC 522966 - I/O translate is only supported on devices configured as TERMINAL. It is not supported when configuring ASYNC devices. 1.3.16 EXTTAPE 1. SPR 509607 - EXTTAPE does not support PSAVEd programs. However, it gives an erronreous "End of Tape" message when it encounters a PSAVEd program. 1.3.17 CONFIG.MGR 1. A configuration record can only be installed from an account with a USER LEVEL of 3. 2. Printer output cannot be directed to a specific printer. All output goes to P*. 1.3.18 MCSI 1. All filelist access must be made by a user with File Security Override set to TRUE. 1.3.19 PHOTO SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB090 Pg010 1. SPR 526530 - Loses the top line and the line numbers are off by one on the printed lines. Eg : What prints on the screen @ 15,20 will say it's printed @ 14,20. This will occur if the screen has 22 lines to be printed. 1.4 BASIC 1. SPR 527061 - Program with execute rights can not be started in a ghost task. Have File Security Enable, create a program that only has execute rights, create a USER as : AF=T, UL=0, SYS=T, TPE=T, SPL=T, FSO=F. Log-on as USER defined above and in BASIC : START 30,"G0" =======> works START 30,"PGM"=======> works (PGM is program you created with execute rights only) START 30,"PGM","G1"==> will give an ERROR=13. 2. SPR 516420 - You will get an ERROR=24 (Function name definition error) when trying to MERGE files that have the same DEF xx functions. EXAMPLE: PROGRAM 1, Statement 100 DEF FNABC (D,E)= PROGRAM 1: D-E PROGRAM 2, Statement 500 DEF FNABC (A,B)= PROGRAM 2: A+B When trying to do a MERGE you will get the error=24. 3. If a BASIC program RUNs another BASIC program which itself RUNs the first program, (This is known as the RUN/RUN problem in FPS) there is a chance that this process will never time-out and allow any other processes to run (in other words hang the system). 4. If the SORT utility has been executed from BASIC, and it encounters an error, BASIC will always return an error 0. 5. An MTCS (MCS) tape drive cannot be accessed through BASIC. This was done by design, due to considerable differences in programming such devices versus 1/2-inch tape devices. 6. The significant enhancements of Business BASIC 86 introduced in 9/8.6 will restrict backward compatibility. Programs written or modified on 9/8.6 will not run on prior releases without recompilation. In addition, new Business BASIC 86 features introduced in 9/8.6 cannot be used in programs which will be run on 9/8.5 or 8.4 release levels. Intersystem transport packages or the CONVERTSP utility can be used to recompile programs written or modified on 9/8.6, provided the new BB86 features have not been used. EXTTAPE should be used to transport programs from 10/9/8.6 release levels to 9/8.5 and 8.4 release levels. EXTTAPE will recompile the programs as they are being transported. (ALL programs and data files transferred from 10/9/8.6G release levels to 9/8.5 and 8.4 release levels must be transported with EXTTAPE.) 7. GETDEVINFO does not return information on Batch jobs. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB090 Pg011 8. SPR 527864 - CALLED program that uses the CLEAR directive will not return values correctly. EXAMPLE: PGM 1 : 10 BEGIN 20 CALL "PGM2",A$ 30 PRINT A$ PGM2 : 10 ENTER A$ 20 B$="HELLO" 30 A$=B$ 40 CLEAR A$ 50 A$="ABC" 60 EXIT When PGM2 exits, PGM 1 print A$ and A$ is "HELLO" when it should be "ABC" 1.5 CLI (Command Language Interpreter) RELEASE 1. SPR 522476 - Doing a !RELEASE * will not release Batch Jobs or Magnet Servers. 1.6 TBC Communications 1. SPR 520796 - TBC protocols using SPOOLing may cause DATA corruption. It is recommended to always define the receive queue with spooling turned off. 1.7 File System 1. SPR 524576 - MK file loses pointer when reading and removing records. EXAMPLE: a) Create a MK file that has keys that begin the same on the primary keyset (10 keys that start with an "A", 10 that start with a "B" and so on through "G") b) Open the file and start reading the file from records that start with a "B" (READ(1,KEY="B",DOM=xx) c) Now begin a sequential read of this file. At one point remove a record. On the next sequential read, the record that is read is the one that was read at the beginning of the read (Record found on step 2) instead of the next sequential record. 2. SPR 524684 - Taking a DOM= or a ERR= branch on a read from a MK file will reset the current keyset to the primary keyset instead of staying with the chosen keyset. 3. SPR 525127 - When a MK file is full and you write a duplicate record with a DOM= branch, you will get an error 2 file full instead of an error 11 duplicate key (primary keys). If you don't specify the DOM, it will work as it should (error=11). SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB090 Pg012 4. SPR 520660 - Indexed files created with maximum record size (32768) will get an error 47 when trying to read records. 5. SPR 521857 - Dump 2,10,37,65 (Instruction Fault File System Single Keyed Module) and 1,238,0,65 (Invalid Instruction) will occur if you try to remove records from a direct/sort file without using the KEY= option (REMOVE (x)) and the files have greater than 50 records. If less than 50 records, the system will return an error 8,4,13,68 (Invalid Current record Position). 6. SPR 515010 - When QUIET=T (or QUIETON) and an output file are specified in a utility command, and the utility encounters an error, the error will not be written to the output file. 7. RSC 516539 - A user is allowed to delete a file that is opened by others through the use of the DELETE, CREATE, and RENAME utilities. This was done by design; the operating system has always worked this way. The RSC requests that the user be notified if they are about to delete an "in use" file and be given the option of cancelling the delete. 1.8 JOB MANAGER 1. Defined GROUPS are deleted at system reload. Job Groups to be kept on a more or less permanent basis should be created via commands entered in the System Startup command file, .SYSDATA.START.CMD. 2. JOB.CREATE does not allow the PAUSE.TRUE parameter to be passed. If the command is embedded in a program, all errors must be handled by the application. 3. BATCH jobs require an output file which is not automatically deleted. The user may need to delete these files on a regular basis to keep disk space available. 4. Quotes must be used around the user accounts when specifying more than one user account in the GROUP.CREATE and GROUP.MODIFY parameter lines. EXAMPLE: (GROUP.CREATE MYGROUP, TYPE=TERMINAL, PRIORITY=3, USERS="GROUP1.*, GROUP.*"). 5. RSC 511490 - If PRIORITY is not specified for TERMINAL and BATCH type jobs, the PRIORITY will default to 1. This default, although proper for BATCH type jobs, is normally too low for TERMINAL type jobs. It is recommended that a PRIORITY of 3 be specified for TERMINAL type jobs during GROUP. CREATE. (See example in item 4) 6. RSC 511491 - The PRIORITY of SYSTEM type jobs cannot be changed, even though GROUP.MODIFY appears to allow the user to do this. 7. RSC 511491 - SYSTEM type jobs cannot be deleted, nor can they be modified. GROUP.MODIFY appears to allow the user to modify SYSTEM tape jobs, but such modifications are not enforced. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB090 Pg013 8. SPR 526067 - If the log file for a certain group is opened, the log record will not get written to this file because JOB MANAGER requires this file to be locked before writing to the file. In some cases, the system will not return an error if the information could not get logged. 1.9 FTF (File Transfer Facility) If you plan to use MAI MAIL (Electronic Mail) or if you plan to start remote programs via FTF, you must ADD the name of the directory in which your remote programs resides to programs "FTF" and "FTFRTHINT". EXAMPLE: If your MAI OFFICE directory is "(TEST).OMS.", add it to statement 52 in program "FTF" and to statement 50 in program "FTFRTHINT". Add the underline portions shown below. LOAD ".NSPGM.FTF" 0052 P$=P8$+."NUPDATA.,.NUPPGM.,.NSPGM., 0052: (TEST).OMS." LOAD ".NSPGM.FTFRTHINT" 0050 P$=P8$+".NUPDATA.,.NUPPGM.,.NSPGM., 0050: (TEST).OMS." 1.10 ENHANCER TOOLS 1. SPR 520015 - PCBMONITOR: The Semaphore display is shifted to the right by one column starting after the SEGSEM field. 2. SPR 523596 - ROT: Relocating track zero (0) on a non SCSI drive that is still FileSystem enabled (on-line), will cause track zero to be relocated nine (9) times. This is not a problem with the tape load version of ROT. Relocating sectors (blocks) 0 thru 15 on a SCSI drive that is still FileSystem enabled (on-line), will give a Four-tuple 3,21,17,101 (Invalid Disk Sector Number). There is a possibility that the System Serial Number will be destroyed and a GENSSN will be needed. 1.11 MAGNET A USER level of 3 should be the only user to START/STOP MAGNET. If a USER of less than 3 START's MAGNET, you will get an "Insufficient Privileged" error when trying to access files via LAN/WAN. WORKAROUNDS: 1. Create a new account with the following characteristics: MAJOR ACCOUNT: MAGNET MINOR ACCOUNT: STARTUP PASSWORD: (anything) WORKAROUNDS: (CON'T) 1. Create a new account with the following characteristics: INITIAL COMMAND: MAGNET.STARTUP; RELEASE SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB090 Pg014 ABORT FLAG: T USER LEVEL: 3 FILE SEC OVERRIDE: T SYS OPR: T SPOOL OPR: T TAPE OPR: T DEFAULT PREFIX LIST: (anything) No other system operations can take place with this account as it would release after starting MAGNET. If MAGNET is already started when this is run, this would have no adverse effect. 2. Instead of shutting down MAGNET, just stop the media. That is, in the MAGNET 'Network Status' menu, option 3 shuts down all of MAGNET but option 2 allows an operator to just shut down the LAN. This is just as effective as shutting down MAGNET to stop remote accessing but the MAGNET system tasks are not terminated so that when the media is restarted they all have their original characteristics. 1.12 Terminals 1. In order to use an industry standard printer as a slave off a DT-4313 terminal, the terminal must have REV. E or above firmware. If the DT-4313 terminal does not have REV E firmware, only screen dumps can be printed. 2. As of release 9/8.6C, T0 must be a model 4309 or later terminal on all systems, or an HVDT on 7xxx/8xxx/9xxx systems. Terminal models 7250 and 7270 are no longer supported as T0. 3. SPR 527864 - When a 132 col. report is printed to a DT-4314 terminal (REV C and L) in condensed mode, the tabing does not work properly. EXAMPLE: Use the following code to duplicate problem: 10 BEGIN 20 PRINT @(10),"10",@(20),"20"...(until) 20:@(130),"130" 30 END This will print fine until position 80, after this you will see that it will not print properly. 1.13 ASYNCHRONOUS TRANSPORT PACKAGE (ATP) ATP 4.0 is the ATP release available for 9/8.6. ATP 4.0 provides new features such as autodial, scheduler, line turnaround, and performance enhancements. ATP 4.0 is NOT compatible with previous releases of ATP; all systems communicating with ATP 4.0 systems must also upgrade to 4.0. 1.14 HORIZONTAL SOFTWARE 1.14.1 The horizontal software packages of PRESENTATION SERVICES, GRAPH, and ORIGIN 2.0 and above typically have files that reside in the .SYS. node. If this is the case, these files need to be reinstalled in the SYS. node after an O.S. upgrade. This can be accomplished by one of the following methods: SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB090 Pg015 a) Retain a copy of the .SYS. node used by the older O.S. and, after the O.S. upgrade, copy the old .SYS. node to the new .SYS. node with DELETE EXISTING DESTINATION FILE = NO. b) For PRESENTAION SERVICES, run the PS.INSTALL program, which will copy all the necessary PS files to the .SYS. node. 1.14.2 For ORIGIN, copy the node .ORIGIN.R2xx.RT. to the new .SYS. node. If the users' prefixes include this ORIGIN runtime node, the ORIGIN files do not need to be in the .SYS. node. For GRAPH, copy the files .GRAF.GRAPH and .GRAF. GRAPHMAKER to the new .SYS. node. 1.14.3 MAGNET AND FILE TRANSFER FACILITY (FTF) 1. There is no automatic conversion of topology configuration files to the new Network Management Facility (NMF) configuration files when 9.6/8.6 is installed on an MPx system previously configured for B4NET/FTF (9.5 and earlier). The user is responsible for printing the previous configuration information before reconfiguring the MAGNET and/or FTF network with NMF or EZCONFIG. 2. A reboot is necessary after the initial configuration of each system in the MAGNET/FTF network. Any subsequent modifications to the home station parameters or sub-network numbers also require a reboot to activate the changes. ORIGINATOR: Joe Melendez SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB090 Pg016 FIB 00091 12/31/91 *** System Slowdown with Serial 4220 on Single Processor System *** If a PT-4220 600 LPM SERIAL printer is attached to a SINGLE ENGINE MPx or Advanced Series system, there may be unacceptable system and printer performance degradation. This is due to the way the Universal Printer Driver (UPD) interacts with CPU scheduling. The PT-4220 serial printer does not cause degradation on systems with more than one CPU. There is not a performance limitation with the PT-4220 parallel printers on a single or multiple CPU systems, since the parallel interface is controlled by the Standard Printer Driver (SPD) rather than the UPD. Furthermore, the PT-4221 1200LPM printer is not affected by this because it is only available in a parallel/SPD configuration. There are two approaches to eliminating performance degradation when using the PT-4220 on MPx/Advanced Series systems: 1. Keep the serial printer and add another CPU to the system. 2. Keep the system at one CPU and upgrade the printer to a parallel interface using Market Code NE010AA. ORIGINATOR: Norm Jones SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB091 Pg001 FIB 00092 01/24/92 *** Release 8/9/10.7A Software Announcement *** MAI Basic Four, Inc. is pleased to announce that the new system software revisions, 8/9/10.7A, are now available. The 9.7A revision is the recommended revision for MPx 9xxx Series Systems. The 8.7A revision is the recommended revision for MPx 7xxx and 8xxx Series Systems. The 10.7A revision is the recommended revision for Advanced Series Systems. ****************************************************************** * * * o A new configuration record is required when upgrading to * * 8/9/10.7A. * * * * o If this release is installed on MPx 9x00 system containing * * DMA-II controllers, then version -002 of the DMA-II * * boards must be used. If the system contains -001 boards, * * please contact your hardware support for local board * * replacement procedures. Please refer to the HARDWARE * * section #6. * * * * o As of release 8/9.6C, the .SYSDATA.SECURITY.DATA file is * * not transportable to previous release levels. Therefore, * * if you are upgrading to 8/9/10.7A from a release prior to * * 8/9.6C, this file should be saved before the upgrade, for * * fall-back purposes. * * * * o Files transferred from 8/9/10.7A to O.S. levels below * * 8/9.6A must be transported with EXTTAPE, MCSI, FTF, TBC, * * or ATP. If a downgrade is performed from 10/9/8.7A to a * * release prior to 8/9.6C, the user's files must be * * transported to the older O.S. level with one of the above * * utilities. * * * * o Programs written or modified on 8/9/10.7A which are * * transferred to a prior release must be transported with * * EXTTAPE, MCSI, FTF, TBC, or ATP. An alternate method * * would be to convert the basic program to a serial file on * * 8/9/10.7A and then transfer it to a prior release. * * * * o Horizontal software such as PRESENTATION SERVICES, GRAPH, * * and ORIGIN typically have files that reside in the .SYS. * * node. These files need to be transferred to the new .SYS. * * node on an O.S. upgrade, either by using the COPY utility * * or by re-installing the software. * * * * o The 8/9/10.7A Software Announcement exists as a serial * * file on the official release tape. To print a copy, submit * * the following file to the printer: * * * * .R7Axx.INST.DOC.ANNOUNCE7A * * * ****************************************************************** Copyright 1990, Rev. 1990, MAI Basic Four, Inc. All rights reserved. C O N T E N T S _ _ _ _ _ _ _ _ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg001 1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . 3 1.1 ENHANCEMENTS IN THIS RELEASE . . . . . . . . . . . . . 3 1.1.1 Image File Restore (IFR) . . . . . . . . . . . . . . 3 1.1.2 Multi-Key File Repair (MKR) . . . . . . . . . . . . 3 1.1.3 Online Backup (OLB) . . . . . . . . . . . . . . . . 3 1.1.4 System Dump to BMTC . . . . . . . . . . . . . . . . 4 1.1.5 Additional Tape Drive Support . . . . . . . . . . . 4 1.1.6 Auditor's Logbook enhancements . . . . . . . . . . . 4 1.1.7 DSR Disconnect . . . . . . . . . . . . . . . . . . . 4 1.1.8 Type 3 Load "Unattended" HCC Backup . . . . . . . . 6 1.2 CONFIGURATION RECORD CONSIDERATIONS . . . . . . . . . 6 1.3 SOFTWARE ANNOUNCEMENT . . . . . . . . . . . . . . . . 6 2 FIXES IN THIS RELEASE . . . . . . . . . . . . . . . . . 7 2.1 SPOOLER . . . . . . . . . . . . . . . . . . . . . . . 7 2.2 BOSS/VS . . . . . . . . . . . . . . . . . . . . . . . 7 2.2.1 Utilities . . . . . . . . . . . . . . . . . . . . . 7 3 CONFIGURATIONS . . . . . . . . . . . . . . . . . . . . . 8 3.1 CONFIGURATIONS FOR MPX 7000/7100/8000 SERIES SYSTEMS . 8 3.2 CONFIGURATIONS FOR MPX 9000/9100/9400 SERIES SYSTEMS . 9 3.3 CONFIGURATIONS FOR MPX 9500/9600 SERIES SYSTEMS . . . 10 3.4 CONFIGURATIONS FOR THE ADVANCED SERIES FAMILY . . . . 11 4 UTILITIES . . . . . . . . . . . . . . . . . . . . . . . 13 4.1 IMAGE FILE RESTORE (IFR) . . . . . . . . . . . . . . . 13 4.2 MULTI-KEY FILE REPAIR (MKR) . . . . . . . . . . . . . 14 4.3 ONLINE BACKUP (OLB) . . . . . . . . . . . . . . . . . 15 4.4 HCC UNATTENDED BACKUP UTILITY . . . . . . . . . . . . 17 5 DIAGNOSTICS . . . . . . . . . . . . . . . . . . . . . . 22 5.1 REMIDI . . . . . . . . . . . . . . . . . . . . . . . . 22 5.1.1 ON MPx 7000, 7100, AND 8000 SERIES SYSTEMS . . . . . 22 5.2 DEMON - UPDATING THE LOAD DIRECTORY . . . . . . . . . 25 5.3 ADVANCED SERIES ONLY . . . . . . . . . . . . . . . . . 26 5.3.1 HIGH FREQUENCY MARGINS ON THE ADVANCED SERIES . . . 26 5.3.2 USING ALT LOAD FOR REMIDI AND DEMON . . . . . . . . 26 5.4 DIAGNOSTIC REMOVAL . . . . . . . . . . . . . . . . . . 26 6 HARDWARE . . . . . . . . . . . . . . . . . . . . . . . . 29 6.1 MPX 7000, 7100, AND 8000 PCBA NOTES . . . . . . . . . 29 6.2 MPX 9XXX SERIES SYSTEM PCBA NOTES . . . . . . . . . . 32 6.3 PCBA'S FOR ALL MPX 7/8/9XXX SERIES SYSTEMS . . . . . . 37 6.4 ADVANCED SERIES PCBA NOTES . . . . . . . . . . . . . . 38 6.5 PCBA'S NOT SUPPORTED ON ADVANCED SERIES . . . . . . . 42 6.6 PERIPHERAL DEPENDENCIES . . . . . . . . . . . . . . . 42 6.6.1 GCR TAPE DRIVE . . . . . . . . . . . . . . . . . . . 42 6.6.2 SCSI MTCS TAPE DRIVE . . . . . . . . . . . . . . . . 42 6.6.3 HIGH CAPACITY CARTRIDGE (HCC) TAPE DRIVE . . . . . . 42 6.6.4 TERMINALS . . . . . . . . . . . . . . . . . . . . . 43 6.6.5 DISK DRIVES . . . . . . . . . . . . . . . . . . . . 43 6.7 HARDWARE FLOW CONTROL - NEW FEATURE . . . . . . . . . 43 7 INSTALLATION . . . . . . . . . . . . . . . . . . . . . . 45 7.1 GENERAL INFORMATION . . . . . . . . . . . . . . . . . 45 7.2 NEW OPERATING SYSTEM INSTALLATION . . . . . . . . . . 50 7.3 UPGRADING TO 9.7A . . . . . . . . . . . . . . . . . . 50 7.3.1 PRINTING OUT THE TERMINAL CONFIGURATION INFORMATION 51 7.3.2 SAVING FILES TO TAPE . . . . . . . . . . . . . . . . 51 7.4 UPGRADING FROM RELEASE LEVELS 8.4D AND BELOW . . . . . 52 7.4.1 HARDWARE EVALUATION . . . . . . . . . . . . . . . . 53 7.4.2 FILE PREPARATION . . . . . . . . . . . . . . . . . . 53 7.4.3 NEW FILE SYSTEM SPACE REQUIREMENTS . . . . . . . . . 54 7.4.4 SAVING FILES TO TAPE . . . . . . . . . . . . . . . . 54 7.5 INSTALLING THE OS - LOADING SLOTS 0 AND 1 USING ALT LO 56 7.6 TYPE 3 LOAD (SPECIAL FUNCTIONS) . . . . . . . . . . . 58 7.6.1 OPTION 1 (CHANGE VOLUME LABEL INFORMATION) . . . . . 59 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg002 7.6.2 OPTION 2 (UPDATE FAMILY INFORMATION) . . . . . . . . 60 7.6.3 OPTION 3 (INITIALIZE FAMILY DIRECTORY) . . . . . . . 60 7.6.4 OPTION 4 (CHANGE INSTALLATION PARAMETERS) . . . . . 60 7.6.5 RESTORING THE O.S. . . . . . . . . . . . . . . . . . 61 7.6.6 INSTALLING THE CONFIGURATION RECORD . . . . . . . . 62 7.7 CONVERTING FILES . . . . . . . . . . . . . . . . . . . 63 7.7.1 TAPE TO DISK CONVERSION . . . . . . . . . . . . . . 63 7.7.2 DISK TO DISK CONVERSION . . . . . . . . . . . . . . 64 7.7.3 CHECK FILES . . . . . . . . . . . . . . . . . . . . 64 7.7.4 UPDATING THE TERMINAL CONFIGURATION FILE . . . . . . 64 7.8 UPDATING THE OTHER SLOTS . . . . . . . . . . . . . . . 65 7.8.1 UPDATING SLOTS 2 AND 3 ON 7xxx and 8xxx SYSTEMS . . 65 7.8.1.1 UPDATING WCS SLOT TWO (2) . . . . . . . . . . . . 65 7.8.1.2 UPDATING WCS SLOT THREE (3) . . . . . . . . . . . 66 7.8.1.2.1 ON 7000/7100 SYSTEMS AND 8000 SYSTEMS WITH LAN . 66 7.8.1.2.2 ON 8000 SYSTEMS WITHOUT LAN . . . . . . . . . . 66 7.8.1.3 UPDATING O.S. SLOT THREE (3) . . . . . . . . . . . 66 7.8.2 UPDATING SLOTS 2 AND 3 ON MPx 9xxx SERIES SYSTEMS . 67 7.8.2.1 UPDATING WCS SLOT TWO (2) . . . . . . . . . . . . 67 7.8.2.2 UPDATING WCS SLOT THREE (3) . . . . . . . . . . . 68 7.8.2.3 UPDATING O.S. SLOT THREE (3) . . . . . . . . . . . 68 7.8.3 UPDATING SLOTS 2 AND 3 ON ADVANCED SERIES SYSTEMS . 69 7.8.3.1 UPDATING WCS SLOT TWO (2) . . . . . . . . . . . . 69 7.8.3.2 UPDATING WCS SLOT THREE (3) . . . . . . . . . . . 70 7.8.3.3 UPDATING O.S. SLOT THREE (3) . . . . . . . . . . . 70 7.9 CONFIGURING UPD . . . . . . . . . . . . . . . . . . . 70 7.9.1 Comments on UPD . . . . . . . . . . . . . . . . . . 72 7.10 SYSTEM STARTUP . . . . . . . . . . . . . . . . . . . 73 7.10.1 STANDARD STARTUP COMMAND FILE . . . . . . . . . . . 73 7.10.2 COMMAND FILE DEFINITIONS . . . . . . . . . . . . . 74 7.10.3 IMPLICATIONS . . . . . . . . . . . . . . . . . . . 75 7.11 DIAGNOSTIC REMOVAL . . . . . . . . . . . . . . . . . 77 8 RELATED DOCUMENTATION . . . . . . . . . . . . . . . . . 80 T A B L E S , F I G U R E S and G R A P H S _ _ _ _ _ _ _ _ _ _ _ _ _ _ ___ _ _ _ _ _ _ Figure 7-1. SAVERESTORE Screen . . . . . . . . . . . . . . 62 Figure 7-2. OPERATING SYSTEM INFORMATION . . . . . . . . . 67 Figure 7-3. OPERATING SYSTEM INFORMATION . . . . . . . . . 69 Figure 7-4. OPERATING SYSTEM INFORMATION . . . . . . . . . 71 1. INTRODUCTION ____________ 1.1. ENHANCEMENTS IN THIS RELEASE ____________ __ ____ _______ The 10.7A/9.7A/8.7A release contains the following enhancements: 1.1.1. Image File Restore (IFR) _____ ____ _______ _____ The Disk Image backup has become very popular because it is much faster than file-by-file backups. The main disadvantage is that when a single file needed to be restored, the entire image needed to be restored on a temporary drive and then the single file backed up from this temporary source. This was both time consuming and required large amounts of temporary disk space. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg003 The Image File Restore (IFR) utility allows individual files to be restored from disk image tape backups. IFR is supported on all tape drives, however for best performance, the large capacity tape drives such as the 8mm HCC tape (which is limited to disk image backups only) is recommended. See the Utilities section for more information. 1.1.2. Multi-Key File Repair (MKR) _________ ____ ______ _____ When a system has a fatal crash, it is possible that files will lack integrity. Prior to 8/9/10.7A the tools available to correct this condition were DiskAnalyzer and Reconstruct. When restoring integrity to extremely large Multi-Keyed files, these tools proved to be very slow. As a response to this problem, the 8/9/10.7A release is providing the Multi-Key File Repair (MKR) utility. The MKR utility will allow the user to "repair" only those records that were in use at the time of the corruption, rather than "reconstructing" every record in the file. The advantage is that MKR will repair a file in minutes rather than hours or days irregardless of the file size. See the Utilities section for more information. 1.1.3. Online Backup (OLB) ______ ______ _____ The new Online Backup (OLB) utility is a selectable feature available in both the interactive (menu) mode and in the command-line mode (where parameters are passed in on the command line). In the menu mode, both SaveRestore and Copy prompt the operator for the new Online Backup option. This option was added with 8/9/10.6H, however it was not activated until the 8/9/10.7A release. If the Online Backup option is chosen, files may be saved or copied even though they are in use by other tasks running application programs that are actively modifying the file. The copy of the file that is saved to tape or copied to disk represents the state of the file as it existed at the beginning of the save or copy of that file. See the Utilities section for more information. 1.1.4. System Dump to BMTC ______ ____ __ ____ In the past, the MPx has not supported system dumps directly to BMTC. The disadvantage has been that if the dump area was too small on a system with a BMTC, there was no way to save the dump to tape. Now, with the release of 8/9/10.7A, systems with BMTC controllers will be able to dump directly to tape. Note: There will be no error checking within this feature, therefore care should be taken when using the utility. For example, if the utility is instructed to dump directly to a drive but a tape is not loaded on that drive, or the drive is not on line, or a write ring is not on the tape, the utility will dump the contents of memory to the BMTC without writing to tape and the dump will be lost. 1.1.5. Additional Tape Drive Support __________ ____ _____ _______ The MPx 9xxx and Advanced Series 40 and 60 systems can now have up to four tape drives. This is accomplished by allowing SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg004 four BMTCs in these systems. This allows customers to have a variety of tape devices to meet their needs. 1.1.6. Auditor's Logbook enhancements _________ _______ ____________ There were two enhancements made to the Auditor's Logbook for the 8/9/10.7A operating system release: o Non-owners of data files may now switch log files for the data file. In previous releases, only the owner of a data file may switch its log files. This new capability allows system operatiors to manage the files without having the capability to view the file contents. o Log files may be manually switched while the data file is opened. Previous releases required the main data file to be closed before performing a manual log switch. 1.1.7. DSR Disconnect ___ __________ The DSR Disconnect enhancement will allow the RS-232 hardware flow control to process the DSR (Data Set Ready) signal as a disconnect command. This feature will be available on any serial port. The DSR signal is a pin in the RS-232 port which is controlled by the serial device and is used to indicate that the device is ready to accept data. When the DSR goes from ON to OFF (indicating that the device is not ready to receive data) a signal will be sent to the operating system to signify the change. The operating system will do one of the following three things, depending on how the port is configured in TERM.CONFIG. o ERR ON DISCONNECT: If 'YES', the ISDCOS will return an error 86 upon receiving the disconnect condition on the communication port. The default is 'NO'. If this field is set to 'NO', then DSR will be ignored. o RELEASE DISCONNECT: This option provides security for a disconnected communication port, and it depends on the 'ERR ON DISCONNECT' field. If 'ERR ON DISCONNECT' is 'NO', then there is no security and this field will be skipped and set to 'NO'. If 'ERR ON DISCONNECT' is 'YES', then there are 2 security measures to consider: 1) If 'RELEASE DISCONNECT' IS 'NO': this selection indicates that on recognizing the line disconnect condition, the OS will report an error one time and it is up to the application to recognize this condition and release itself from the system. 2) If 'RELEASE DISCONNECT' is 'YES': this selection indicates that when the OS detects the line disconnect condition, the process will automatically be released from the system without any notification to the application. By using the TERM.CONFIG fields outlined above, the following options are available: o Ignore the disconnect signal o Return error 86 and then ignore the signal o Release the task immediately on disconnect signal SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg005 This feature is most useful in a system configuration which has modem access. On previous versions of BOSS/VS, if a modem was "disconnected" prematurely (ie. if the modem hung up), the BASIC application that was running had no way of knowing that the modem had disconnected. As a result, the next person that dialed into the port would "fall into" the application that was running. This presented a serious security violation. DSR disconnect prevents this by offering two options: o Returning an error to the application so that the program can perform any clean up chores and return the system to the state needed for the next caller. o Immediately release the task that was associated with that port to prevent the next remote user from "falling into" the application. NOTE: It should be noted that if the ERR ON DISCONNECT option is used, and the user is not in a BASIC application which will respond to the ERR 86 (ie. BOSS/VS Utilities, Console Mode, etc.) then the error will be returned, however the port will remain open. The table below lists the cables needed to use the DSR disconnect feature: Market Code Description --------------------------------------------------------------------------- QB003AA Cable, RS-232 device to CCA (8-Way) 25 ft. (Part #907115) QB005AA Cable, RS-232 device to Back Panel 25 ft. (Part #907646) SJ015AA Cable, Modem to CCA (8-Way) 25 ft. (Part #907117) SJ016AA Cable, Modem to CCA (8-Way) 50 ft. (Part #907117) SJ017AA Cable, Modem to Back Panel 25 ft. (Part #907648) SJ018AA Cable, Modem to Back Panel 50 ft. (Part #907648) 1.1.8. Type 3 Load "Unattended" HCC Backup ____ _ ____ ____________ ___ ______ This utility will allow you to use the HCC tape drive to perform a Type 3 Load Image Backup when the user is in a Type 1 Load. The software will be unprotected (will not need a password). The HCC utility will allow you to select the families to be backed up, as well as the date and time to start the backup process. The utility will also produce a report of any problems (ie. miscompares or disk errors). 1.2. CONFIGURATION RECORD CONSIDERATIONS _____________ ______ ______________ In general, a new configuration record is required when upgrading to a new system type (e.g., from an 8xxx to a 9xxx system), when adding new hardware, or when upgrading to a new major release level (e.g., 8.6 to 8.7). A new configuration record WILL BE required when upgrading from any prior release (ie. 8/9/10.6H or below). 1.3. SOFTWARE ANNOUNCEMENT ________ ____________ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg006 The 8/9/10.7A Software Announcement exists as a serial file on the official 8/9/10.7A O.S. release tape, which allows the user to print copies, if needed. To print this document, SUBMIT the following file to the printer: (family).R7Axx.INST.DOC.ANNOUNCE7A 2. FIXES IN THIS RELEASE _____ __ ____ _______ 2.1. SPOOLER _______ 1) This is item 1. 2.2. BOSS/VS _______ 2.2.1. Utilities _________ 1) This is item 1. 3. CONFIGURATIONS ______________ NOTE 1: The number of "High Activity Tasks" is approximate and largely dependent on the application. The relative relationship of the numbers between configurations is more important than the actual numbers themselves. NOTE 2: System configurations of MPx 9xxx Series Systems are based on the use of the LS-700 power supply mainframes. Original 810 systems do not support the LS-700 power supply and, therefore, will not meet all defined maximum configurations listed. NOTE 3: The following configurations are based on performance testing, and are subject to change as newer performance testing data becomes available. The configurations listed in the marketing announcements override those listed here. 3.1. CONFIGURATIONS FOR MPX 7000/7100/8000 SERIES SYSTEMS ______________ ___ ___ ______________ ______ _______ The maximum configuration for MPx 7000, 7100, and 8000 Series Systems, models 7030, 7130, and 8030, is as follows: 116 Devices - A combination of 8-ways, 16-ways, the 4 ports on the MCS PCBA, MDTs and HVDTs up to a total of 116 devices are supported. 3 CPU sets 10 ISDCs: 16-ways (7 maximum) and/or 8-ways 32 Ghost tasks 24 High speed videos (HVDT) 8 Disk drives 4 Parallel printers SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg007 2-8 Megabytes of memory 2 Magnetic tape drives - MTR, MTS, and/or GCR (2 Maximum), and/or MCS (1 maximum) 4 Intelligent Multi-Line Controllers (IMLC) 8 DataWord II terminals 4 TBC lines 64 3270 terminals 8 X.25 lines 2 Auto-Call Units (ACU) 99 Serial Printers 99 System printers (total serial and parallel not to exceed 99) 2 Buffered Magnetic Tape Controllers 27 High activity concurrent tasks 1 LAN controller NOTE: There is a maximum of 9 memory assembly boards in any combination of 1/2 Mb, 1 Mb, 2 Mb, 4 Mb and BMTCs (a maximum of 3 boards per chassis). Models 7010/7110/8010 and 7020/7120/8020 have the same configuration limits as models 7030 and 8030 above, with the following limitations: 7010/7110/8010 7020/7120/8020 1 CPU set 2 CPU sets 2-4 Mb memory 2-8 Mb memory 20 Devices 52 Devices 12 Concurrent tasks 20 Concurrent tasks (high activity) (high activity) 23 System printers 51 System printers 3.2. CONFIGURATIONS FOR MPX 9000/9100/9400 SERIES SYSTEMS ______________ ___ ___ ______________ ______ _______ The maximum configuration for MPx 9000, 9100, and 9400 Series Systems, models 9020, 9120, and 9420 is as follows: 116 Devices - A combination of 8-ways, 16-ways, the 4 ports on the MCS PCBA, MDTs and HVDTs up to a total of 116 devices are supported. 2 CPU sets with Evaluation Stack and Rstack Cache 10 ISDCs: 16-ways (7 maximum) and/or 8-ways (10 maximum) 32 Ghost tasks 24 High speed videos (HVDT) 16 Disk drives on models 9020 and 9120, 8 disk drives on model 9420(5.1 GB maximum), with no more than 8 14-inch fixed drives on any of the 3 models 8 Parallel printers 4-12 Megabytes of memory 2 Magnetic tape drives - MTR, MTS, and/or GCR (2 maximum), and/or MCS,HCC (1 maximum) 4 Intelligent Multi-Line Controllers (IMLC) 8 DataWord II terminals 6 TBC lines 64 3270 terminals 8 X.25 lines 2 Auto-Call Units (ACU) 99 Serial printers 99 System printers (total serial and parallel not to exceed 99) 4 DMA controllers (including DMA-I, DMA-II and DMA-III's in any SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg008 combination)* 2 Buffered Magnetic Tape Controllers 42 High activity concurrent tasks 1 LAN controller * It is recommended that, for maximum performance, no more than two 250MB disks be configured per DMA-II, and that the number of DMA-II's equals or exceeds the number of CPU's. Models 9010, 9110, and 9410 have the same configuration limits as the 9020, 9120, and 9420 above, with the following exceptions: 1 CPU set with Evaluation Stack and Rstack Cache 68 Devices 10 ISDCs: 16-ways (4 maximum) and/or 8-ways (8 maximum) 67 Serial printers 75 System printers (total serial and parallel not to exceed 75) 27 High activity concurrent tasks 3.3. CONFIGURATIONS FOR MPX 9500/9600 SERIES SYSTEMS ______________ ___ ___ _________ ______ _______ The maximum configuration for MPx 9500 and 9600 Series Systems, models 9530 and 9630, is the same as the maximum configuration for the MPx 9000, 9100 and 9400 Series Systems, models 9020, 9120, and 9420 with the following exceptions: 3 CPU sets with Evaluation Stack Rstack Cache Code Cache Data Cache 255 Devices 16 ISDCs: 16-ways (16 maximum) and/or 8-ways (16 maximum) 4-24 Maximum megabytes of main memory (see Hardware section for mandatory revision levels for main memory support above 12 megabytes) 16 Disk drives on model 9530, 12 disk drives on model 9630 (7.9 GB maximum), with no more than 8 14-inch fixed drives on either model 4 DMA controllers (including DMA-I, DMA-II, and DMA-III's in any combination.) 82 High activity concurrent tasks Models 9510/9520 and 9610/9620 have the same configuration limits as models 9530/9630 with the following exceptions: 9510/9610 9520/9620 1 CPU set 2 CPU sets (same caches as the 9530) (same caches as the 9530) 16 disk drives (9610) 16 disk drives (9620) 10 ISDCs: 16-way (5 maximum) 10 ISDCs: 16-way (8 maximum) 8-way (8 maximum) 8-way (10 maximum) 84 Devices 132 Devices 83 Serial printers 63 Concurrent tasks 91 System printers (high activity) (total serial and parallel) 52 Concurrent tasks SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg009 (high activity) 3.4. CONFIGURATIONS FOR THE ADVANCED SERIES FAMILY ______________ ___ ___ ________ ______ ______ The maximum number of high activity concurrent tasks is 140 on the Advanced Series Model 63, 65 on the ADVANCED SERIES Model 42 and 40 on the ADVANCED SERIES model 20. The maximum configuration for ADVANCED SERIES model 63 is as follows: 255 Devices - A combination of 8-ways, 16-ways, and the 4 ports on the MCS/M PCBA, and MDT's up to a total of 255 devices are supported. 3 CPU's (with cache boards) 16 ISDCs: 16-ways (16 maximum) and/or 8-ways (16 maximum) 4-48 Maximum megabytes of main memory (See Hardware section for mandatory revision levels for main memory support above 12 megabytes.) 16 Disk drives (may be 300MB and 590MB fixed disks, 285 removables, or 364MB,250MB, 690MB on DMA-II for up to 11 GB maximum) 4 DMA controllers with standard backplane. Double wide backplane allows 6 DMA controllers. (The controllers may be DMA-I disk controllers for support of 285Mb removable disks and/or DMA-III disk and parallel printer controllers for support of 300Mb and 590Mb fixed disks and parallel printers) * 32 Ghost tasks 8 Parallel printers 2 Magnetic tape drives - MTR, MTS, and/or GCR (2 maximum), and/or MCS (1 maximum) 4 Intelligent Multi-Line Controllers (IMLC) 8 DataWord II terminals 4 TBC lines 64 3270 terminals 8 X.25 lines 2 Auto-Call Units (ACU) 99 Serial printers 99 System printers (total serial and parallel not to exceed 99) 2 Buffered Magnetic Tape Controllers 1 LAN controller The maximum configuration for ADVANCED SERIES model 62 is the same as for model 63, with the following exceptions: 196 Devices 2 CPU's (with cache boards) 4-36 maximum megabytes of main memory 12 16-ways; 12 8-ways The maximum configuration for ADVANCED SERIES model 61 is the same as for model 63, with the following exceptions: 148 Devices 1 CPU (with cache board) 4-28 maximum megabytes of main memory 9 16-ways; 9 8-ways SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg010 The maximum configuration for ADVANCED SERIES model 42 is the same as for model 63, with the following exceptions: 132 Devices 2 CPU's (without cache) 4-24 maximum megabytes of main memory 8 16-ways; 8 8-ways The maximum configuration for ADVANCED SERIES model 41 is the same as for model 63, with the following exceptions: 100 Devices 1 CPU (without cache) 4-20 maximum megabytes of main memory 6 16-way; 6 8-ways The maximum configuration for ADVANCED SERIES model 20 is the same as for model 63, with the following exceptions: 1 chassis 52 Devices 1 CPU (without cache) 4-12 maximum megabytes of main memory 2 disks maximum; 250MB, 364MB, 690MB disks (up to 1.4GB) 2 parallel ports 3 ISDCs: 16-ways maximum 51 serial printers 53 system printers 1 BMTC 2 IMLC * For maximum performance, it is recommended that no more than 2 disks be configured per DMA. 4. UTILITIES _________ There are several utility enhancements and additions with the 8/9/10.7A release. These features were introduced in the ENHANCEMENTS section and are described in more detail in the following sections. 4.1. IMAGE FILE RESTORE (IFR) _____ ____ _______ _____ The Image File Restore (IFR) utility will provide the user the ability to process the retrieval of file(s) from single or multi-volume image (family) backup tape(s). This utility will be available in both interactive (menu) an command-line mode (where parameters are passed from the command line). If more than one file per session is needed, a filelist must be created with the editor or !DIR and submitted to the utility. It may be passed into the program from either the menu or the command line. In both cases, the filelist name entered must be prefixed with the '@' sign. To support the quicker retrieval of important control structures from tape, image backup has been modified to write the necessary control structures at the start of the tape. These structures are currently written at the end of the tape. This new format will be transparent to older SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg011 versions of utilities which deal with the image tape format. In other words, an image backup from an operating system level of 8/9/10.7A or above will be able to be restored on a previous level. The impact however is that the IFR utility requires the new format and therefore IFR will only work on image backups made on O.S. level 8/9/10.7A and above. IFR will support all tape drive types, however IFR works best with large capacity tape drives such as the 8mm HCC tape (which is limited to disk image backups only). The IFR utility will also support multiple tape reals. As many as four passes through the tape may be required to restore a single file. Two tape passes may be required to restore the working directory and two passes to restore each user input file. The performance will depend upon the tape device, the system configuration, and the number and location of extents in the restored file. The best case scenario will be a file with only one extent, or where the control segment precedes the location of all other extents of that file on the image backup. This scenario will require only one pass through the tape. Due to the fact that the utility is restoring raw data, there is a class of errors that are not detectable until the file is opened for access. For this reason, it is recommended that the user run DKA option VALIDATE/RECONSTRUCT A FILE on the restored files at the completion of the run. NOTE: File names that start with special characters (Ex. ,!#$%^&*[]) cannot be restored from a filelist. They must be restored file by file. 4.2. MULTI-KEY FILE REPAIR (MKR) _________ ____ ______ _____ The MKR Utility will allow a user to repair a Multi-Keyed file, by reading the record information stored in the control segment. File Buffer Flush (FBF) has been enhanced to copy relevant information to the control segment, in preparation for the repair process. This information consists of record addresses of records which are being accessed and the current state of the file (ie. Add, Delete, Rewrite). All records which have modifications in progress during the time of the system crash will be purged. A report file is generated to provide the user with information regarding all records that were being modified but did not complete their transaction. The three different types of record transactions are Add, Delete, and Rewrite (modify). Notice that Read operations are not necessary to reconstruct since the read operation does not modify any structures of the file. The user can then look at the report and decide what to do with the incomplete transactions. There will be a status line associated with each transaction on the report. For a record that was being Deleted, the status will show "deleted", and no additional information will be kept. The delete will be completed by the repair. For records that are being Added, the record will be saved in a log file if the repair was successful SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg012 and the status will show "recovered". The user will be able to recover the record from the log file. For records which are being rewrote, the record will also be deleted and depending on the state of the rewrite operation, either the old or new record will be saved to the log file. The status will show either "old record recovered" or "new record recovered". The information in the log file can be used for data recovery. The DiskAnalyzer (DKA) and Reconstruct programs will be enhanced to detect when a "repair" operation is possible, and recommend the user to use MKR for faster recovery. In the event that MKR cannot repair a MK file due to one of the conditions stated in the limitations section below, the MKR utility will report back to the user that DKA or Reconstruct must be used. LIMITATIONS There are a few limitations to the MKR Utility and they are specified below: 1) The MKR utility will be able to repair up to eight transactions which are considered incomplete. This includes add, delete, or rewrite operations during the time of the crash. Initial research showed this is more than needed on nearly all files. 2) The MKR utility may not be able to complete if certain file structures are swapped out to disk (Control Segment, Current Record Table, etc.). The utility also may not be able to complete if a B-Tree split was in process during the time of the crash. 3) The MKR utility is supported for systems with System Write-Through enabled and File Write-Through enabled, however it is recommended that users turn Write-Through OFF on those MK files which are most frequently used. This is due to the increase in number of I/Os on file which have write-through enabled. The higher number of I/Os tend to work against the MKR mechanism. 4) The MKR utility will only work on files which were corrupted under 8/9/10.7A. This is because the file must have record data saved at the time of the crash to be "repairable". In other words, you cannot take a file which was corrupted on a previous release and try to repair it on an M7A system. 5) The FBF feature must be completed after a system crash for MKR to be able to repair a file. 4.3. ONLINE BACKUP (OLB) ______ ______ _____ Online backup is a selectable feature available in both the SaveRestore and the Copy utilities. In Copy, this feature is available in both the interactive (menu) mode and in the command-line mode (where parameters are passed in on the command line). In the menu mode, both SaveRestore and Copy prompt the operator for the new Online Backup option. This prompt was introduced in 8/9/10.6H, however, it was not SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg013 activated until 8/9/10.7A. The default for this option is false, so it will not be enabled unless specifically requested. When copying files with parameters from the command line, the keyword for the new feature is ONLINEBACKUP and the values it can take are TRUE and FALSE (the default). Help screens are available for both Copy and SaveRestore. In the Online Backup mode, files may be saved or copied even though they are in use by other tasks running application programs that are actively modifying the file. The benefit to the user is that the system does not have to be brought "down" for backups. The resultant copy of the file that is saved to tape or copied to disk represents the state of the file as it existed at the beginning of the save or copy of that file. A "checkpoint" is forced when initiating this mode to ensure that no modifications are in progress when the mode is established. During the Online backup, the operating system maintains a static version of the file to be used by SaveRestore or Copy and a dynamic version for normal data access. If parts of the file are modified while the save or copy is in progress, the original versions of those parts are recorded in a temporary file known as the before-image-journal file. This file is allocated on the disk family which has the most available space and is automatically deallocated when the save or copy is complete. If any errors occur during the recording of the before-images, the error will be reported by SaveRestore or Copy the next time it reads data from the data file. One possible error is "Family Full (out of usable disk space)." The response to this error should be to make additional space available on some family (presumably the one that had the most available space already) and retry the operation. Alternatively, the save or copy can be retried at a time when the data file is undergoing fewer modifications. When the Online Backup mode is selected from the first SaveRestore or Copy input screen, that mode will be applied to all files saved or copied in that session, regardless of whether or not the files are opened by others at the beginning of the save or copy. NOTE: It is important to note that NO synchronization is performed between the files being backed up to guarantee that all files being backed up represent the same point in time. NOTE: If files are modified while they are being backed up, a subsequent compare operation will result in mismatches. The same situation occurs if a file is modified between the time of the save or copy and the compare. Normally, the automatic compare option should not be selected when files are backed up in Online Backup mode. NOTE: The utilities cannot save or copy files that are locked, even if the Online Backup mode is selected. 4.4. HCC UNATTENDED BACKUP UTILITY ___ __________ ______ _______ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg014 NOTE: THIS UNSUPPORTED SOFTWARE CANNOT PROTECT AGAINST ITS SOURCE DISK FROM BEING MODIFIED AS IT IS BEING BACKED UP. UPDATES TO FILES CAN OCCUR FROM NORMAL USER TASKS WHILE THE IMAGE COPY IS IN PROGRESS. IT IS UP TO THE USER TO INSURE THAT THIS DOES NOT HAPPEN. MBF DOES NOT GUARANTEE FILE INTEGRITY IF FILES ARE BEING MODIFIED AT THE SAME TIME THAT THE FAMILY IS BEING BACKED UP. THIS UNSUPPORTED SOFTWARE HAS NOT BEEN CERTIFIED ON ALL HARDWARE CONFIGURATIONS. IF YOU HAVE PROBLEMS WHILE USING THIS SOFTWARE IT WILL BE THE USER'S RESPONSIBILITY TO MODIFY THESE PROGRAMS. THIS UNSUPPORTED SOFTWARE MUST BE RUN ON A VDT 4309 OR HIGHER. The following is documentation for the HCC backup processing. It is suggested to create a separate operator logon that sets the prefix and automatically runs the HCC menu program (PSMU01). Before performing the HCC backup process, it is recommended to always verify that the HCC tape unit has been turned on and is on-line and that the specified printer (if any) has been turned on and is on-line. Also if File Security is set to true system wide, then to run this unsupported software the user must have File Security Override set to true. The HCC backup processing menu has three options. They are as follows: 1) HCC Backup Data Entry and Processing 2) HCC Backup Processing (Do Not Use) 3) HCC Backup Processing Serial File Hardcopy The first option is a data entry screen (PSDE01) which is required to be completed before the backup processing can take place. The information needed to be input and the descriptions of the items are as follows: 1) Tape Unit Number - This is the tape drive number that the backup processing will open to the HCC tape drive. It MUST be the correct tape unit drive number. 2) Tape Set Name - This is the set name which will be written to the label of the HCC tape before the actual backup processing begins. 3) Tape ID Name - This is the identification name which will be written to the label of the HCC tape before the actual backup processing begins. 4) Compare Y/N - This field, if 'Y' is entered, will allow an automatic compare to take place after the backup processing is completed. If 'N' is entered, no compare will take place. It is recommended to always set this parameter to 'Y'. 5) Password - This is where the system password is entered. This will be checked before beginning the backup processing. The backup processing will not begin without a correct password. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg015 6) Family Name - The terminal will display the families to be to be backed up . Enter a M.B. IV to modify this display or enter 'CR' to accept this display. While modifying families you can add 16 families but it will be up to the user to make sure that the total capacity (MBYT) does not exceed the capacity of the HCC tape. Also when entering families the system will check to see if this family is mounted on the system. It also will not accept duplicate families to be backed up (Enter a family more than once). You can use CTRL C to help you modify a family name. NOTE: The Family Name fields must be used in order. (ie. If three families are to be backed up, then these family names would be entered in the family name 1,2 and 3 fields, and Family Name 4 would be left blank after this blank field the system will ignore the rest of the family fields. 10) Start Date - This is the date that will be compared to the system date to determine when the backup will automatically begin. The system date will be displayed while accessing this field for your convenience. This date will be in MM/DD/YYYY format. Entry of the century is not necessary. If the date entered in this field is equal or prior to the the system date, the backup processing will wait until the Start Time parameter (covered in the following paragraph) is met. If the date entered in this field is in the future, the system will wait until this date is met. 11) Start Time - This is the time that will be compared to the system time to determine when the backup will automatically begin. The system time will be displayed while accessing this field for your convenience. This field can be entered in 24 hour format and will be converted and displayed in standard time. It can also be entered in standard time format. If 'A' for 'AM' or 'P' for 'PM' is not specified, 'AM' will be defaulted. The system will NOT begin checking the time parameter against the system time until the Start Date parameter has been met. The time parameter must match the system time exactly before the backup processing will begin. NOTE: Due to rounding in the calculation process of time, the time entered may lose or gain one minute. It is recommended to enter a start time on either an hour or half an hour. 12) Printer Name - This is the printer where the output of the backup will be sent. This MUST be a valid printer and this printer MUST be on-line. The backup processing will automatically RESERVE this device so it will not create a spool file and miscompare. The backup processing will automatically update the printer back to SPOOL mode during the completion of the backup processing. 13) Output File Name - This is a serial file where the output of the backup will be sent. This field will override the Printer Name field above. If this field is used, then output will be sent to the file name specified. If this field is left blank, then output will be sent to the printer name specified, described above. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg016 NOTE: This file most likely will be miscompared (If compare option is used) due to live procesing. This will also cause the :DIR and AVSP files to also miscompare. 14) Ghost ID - This is the name of the ghost task that will be automatically started during the backup processing. It MUST be in Gnn format. 15) Stand Alone Mode - This field, if 'Y' is entered, will automatically release all terminals that are logged on to the system before starting the backup processing. Also, the group TERMINALS will be disabled to prevent users from logging into the system during the backup processing. If 'N' is entered, any users logged onto the system will not be released. After filling out the above information, a prompt 'IS THE ABOVE DATA CORRECT (Y-N-END):' is displayed. If 'Y' is entered, the above information is saved and the HCC backup processing program (PSBU01) is run. This program takes the information entered in the data entry program and performs the actual backup. ERROR REPORTING 1) Soft errors are not reported to the HCC routine but are reported in the ERRORLOG. A soft error will be the one that is displayed in the ERRORLOG as NORMAL Read. A NORMAL read error is one that failed the MULTI sector read (first pass), then dropped into the 'Single Sector' read but did not have any errors for the sectors that were in the Normal Read. 2) Hard errors are reported to the HCC routine (Software will do two retries and skip the sector and continue) and are also in the ERRORLOG. They will be the ones that are reported as Normal Read, Retry Read, Retry Read. It failed the Normal Read (multi sectors) then dropped into the single sector read (Retry Read), then hit a sector that was bad and failed (Retry Read). 3) You will have compare errors if files were being modified at the time the system was backing up these files (Compare errors will only be displayed if you select the option of COMPARE="Y"). It will be up to the user to determine what files have been modified (By using the information provided by the HCC routine you can go into the !DKA utility and select option 7 ( LIST FILES IN A SECTOR RANGE). Some files that might show up as being miscompared are : DIR, AVSP, OVERLAY and ERRORLOG (if you had soft/hard errors). Also if you select a file for output this might show up as being miscompared. You can ignore these files since you are backing up a "LIVE" system and this utility was originally made for a T3LD. Anything else that shows up as being miscompared (user's files) is up to the user to determine if he has a valid backup. In case of a power failure the HCC routine is not guaranteed because the BMTC does not have the power fail capability as does memory. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg017 You will know if you have a GOOD backup if at the end of the HCC routine your final page (printout/file) has a box that displays all families backup. It should display the following : ------------------------------------------------------------------------- FAMNAME OPERATION STATUS TOTAL INCIDENTS ------------------------------------------------------------------------- FAMNAME = Families backed up OPERATION = Should always say BACKUP STATUS = DONE means backup completed (but you might have had a soft/ hard or a miscompare error). If TOTAL INCIDENTS is 0 there were no problems encountered during this backup. = DISK ERROR means HARD/SOFT error encountered. *NOTE* If you have any HARD errors reported by the HCC routine you should have a Customer Service representative check the family and ROT (if necessary) the sectors that have these HARD errors. TOTAL INCIDENTS = should match the number of HARD/SOFT and COMPARE errors that is in the printout/file. Reported by the HCC routine. At the end of this box it should display the START TIME and END TIME of the BACKUP. If you do not get this box or if this box is incomplete (missing families) you do not have a GOOD backup. 5. DIAGNOSTICS ___________ NOTE: To access all of the software documented in this section, the prefix must be set to the .R7Axx.DIAG.,.R7Axx.INST. node. Please see the installation sections in this announcement for instructions on how to install DEMON and REMIDI. Further information on these diagnostics can be found in DOCWRITER, which can be accessed by entering !DOCWRITER in command mode. 5.1. REMIDI ______ NOTE: UPDATE.LD needs to be run for REMIDI whenever question marks (?/?) appear in Load Sector 2 at the top of the OSINFO screen. 5.1.1. ON MPx 7000, 7100, AND 8000 SERIES SYSTEMS __ ___ _____ _____ ___ ____ ______ _______ REMIDI version BV includes all micro-diagnostics except those for the MPC and LAN controllers. It is loaded into WCS slot 2 and is used on MPx 7000, 7100, and 8000 Series Systems. REMIDI version BVM contains micro-diagnostics for the MPC and LAN controllers. It is loaded into WCS slot 3 on all 7000/7100 Series Systems and on 8000 Series Systems with SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg018 LAN controllers. This version of REMIDI is used on MPx 7000/7100 Series Systems for the MPC and LAN controllers, and on 8000 Series Systems for LAN controllers only. If a LAN controller is not present on an 8000 Series System, the BVM version of REMIDI is not needed. The Load Directory controls which version of REMIDI will be executed. The UPDATE.LD utility is used to update the Load Directory. See the following section for instructions on running UPDATE.LD. UPDATING THE LOAD DIRECTORY FOR REMIDI Disregard this section if your 8000 Series System does not have a LAN controller. (In this case only REMIDI version BV is used, and it is not necessary to update the Load Directory.) Since REMIDI is a WCS Image, two WCS slots, slot 2 and slot 3, will be required for the two REMIDI versions. The extra slot is provided by the DEMON WCS slot. Because DEMON and the BOSS/VS O.S. share the same WCS, Load Sector 3 should display 3/0 or 3/1, indicating that the WCS for DEMON is in either WCS slot 0 or WCS slot 1. This leaves WCS slot 3 free for REMIDI. Only one version of REMIDI will run at a time. The version that will run is dependent on how the Load Directory for REMIDI (Load Sector 2) is set up. The standard version, BV, which resides in WCS slot 2, has an OS/WCS of 0/2. The MPC/LAN version, BVM, which resides in WCS slot 3, has an OS/WCS of 0/3. Use UPDATE.LD to update the Load Directory to designate which version to run. To test the MPC and LAN controllers with REMIDI version BVM, execute UPDATE.LD, using the inputs below: NOTE: Lines preceded by an "*" require operator input. * Input in command mode !UPDATE.LD Update Load Directory Utility (Version 6.5.5.0) Disks (Unit number) on line : 0(16),1(17) Enter disk number: Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 7.1.x.x R 7A*xx (date) B 6.1.x.x 1 1/1 | 7.1.x.x R 7A*xx (date) B 6.1.x.x 2 0/2 | B 6.1.x R 3 3/0 | 7.1.x.x DEMON B 6.x.x R * New OS slot (0,1,3): 0 * New WCS slot (0..3): 3 * Load sector (0..3) : 2 In this case, UPDATE.LD will then display the new Load Directory as follows: SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg019 Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 7.1.x.x R 7A*xx (date) B 6.1.x.x 1 1/1 | 7.1.x.x R 7A*xx (date) B 6.1.x.x 2 0/3 | B 6.x.x R 3 3/0 | 7.1.x.x DEMON B 6.x.x R Notice the change in Load Sector 2. To go back to the standard REMIDI version, BV, which tests the CPU and main memory, use the following in UPDATE.LD: * New OS slot (0,1,3): 0 * New WCS slot (0..3): 2 * Load sector (0..3) : 2 In this case, UPDATE.LD will then display the new Load Directory as follows: Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 7.1.x.x R 7A*xx (date) B 6.1.x.x 1 1/1 | 7.1.x.x R 7A*xx (date) B 6.1.x.x 2 0/2 | B 6.x.x R 3 3/0 | 7.1.x.x DEMON B 6.x.x R NOTE: The Load Directory should stay in the above setup in case the system CPU needs to be tested in a down condition. Always use Load Sector 2 for REMIDI. ON MPx 9xxx AND THE ADVANCED SERIES REMIDI for MPx 9xxx Series Systems consists of two sections, AVA, which is loaded into WCS slot 2, and AVC, which is loaded into WCS slot 3. REMIDI for the ADVANCED SERIES family also consists of two sections, CVA, which is loaded into WCS slot 2, and CVC, which is loaded into WCS slot 3. Unlike the REMIDI versions on 7xxx/8xxx systems, the REMIDI versions on 9xxx and ADVANCED SERIES Systems, are not used independently by slot. In other words, the version of REMIDI in WCS slot 2 calls the version of REMIDI in WCS slot 3 on 9xxx and ADVANCED SERIES Systems. Load Sector 2 contains the OS/WCS pointers for REMIDI. UPDATING THE LOAD DIRECTORY FOR REMIDI Normally, the Load Directory is updated by the operating system when REMIDI is installed with UPDATE.WCS. However, if Load Sector 2 does not reflect an O.S./WCS of 0/2, the UPDATE.LD utility can be run to update the Load Directory: NOTE: Lines preceded by an "*" require operator input. * Input in command mode !UPDATE.LD Update Load Directory Utility (Version 6.5.5.0) Disks (Unit number) on line : 0(16) 1(17) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg020 ENTER DISK NUMBER: Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 7.1.x.x R 7A*xx (date) x 6.x.x 1 1/1 | 7.1.x.x R 7A*xx (date) x 6.x.x 2 ?/? | x 6.x.x R 3 3/0 | 7.1.x.x DEMON x 6.x.x R * New OS slot (0,1,3): 0 * New WCS slot (0..3): 2 * Load sector (0..3) : 2 UPDATE.LD will then display the new Load Directory as follows: Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 7.1.x.x R 7A*xx (date) x 6.x.x 1 1/1 | 7.1.x.x R 7A*xx (date) x 6.x.x 2 0/2 | x 6.x.x R 3 3/0 | 7.1.x.x DEMON x 6.x.x R Notice the change in Load Sector 2. 5.2. DEMON - UPDATING THE LOAD DIRECTORY _____ _ ________ ___ ____ _________ Because REMIDI resides in WCS slot 3 on 7xxx and 9xxx systems and 8xxx systems with LAN, the Load Directory must point to another WCS slot for DEMON on these systems. The O.S. and DEMON share the same WCS code, therefore, Load Sector 3 should point to the WCS slot used by the O.S. Normally, this is set up by the operating system when DEMON is installed, providing that the correct answers are entered at the UPDATE.OS prompts during installation. If, for any reason, Load Sector 3 does not reflect OS/WCS as 3/0 or 3/1, you may use UPDATE.LD to change it, using the following inputs: NOTE: Lines preceded by an "*" require operator input: * Input in command mode !UPDATE.LD Update Load Directory Utility (Version 6.5.5.0) Disks (Unit number) on line : 0(16),1(17) Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 6.7.x.x R 7A*xx (date) x 6.x.x 1 1/1 | 6.7.x.x R 7A*xx (date) x 6.x.x 2 0/2 | x 6.x.x R 3 3/3 | 6.7.x.x DEMON x 6.x.x R * New OS slot (0,1,3): 3 * New WCS slot (0..3): 0 (or 1) * Load sector (0..3) : 3 UPDATE.LD will then display the new Load Directory as follows: SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg021 Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 6.7.x.x R 7A*xx (date) x 6.x.x 1 1/1 | 6.7.x.x R 7A*xx (date) x 6.x.x 2 0/2 | x 6.x.x R 3 3/0 | 6.7.x.x DEMON x 6.x.x R Notice that Load Sector 3 is now pointing to WCS slot 0. 5.3. ADVANCED SERIES ONLY ________ ______ ____ 5.3.1. HIGH FREQUENCY MARGINS ON THE ADVANCED SERIES ____ _________ _______ __ ___ ________ ______ The ADVANCED SERIES processor has the capability to run at a faster clock rate for diagnostic purposes. This capability is intended for diagnostic testing of the CPUs ONLY. The system should never be used at the higher clock rate except for diagnostic purposes. 5.3.2. USING ALT LOAD FOR REMIDI AND DEMON _____ ___ ____ ___ ______ ___ _____ On the ADVANCED SERIES, REMIDI and DEMON can be loaded into memory from the O.S. tape via ALT LOAD and executed. To load REMIDI, load switch 2 should be on. To load DEMON, load switches 2 and 3 should be on. Pressing the ALT LOAD switch will then load the selected diagnostic into memory for execution. 5.4. DIAGNOSTIC REMOVAL __________ _______ This section describes the removal of diagnostic programs from a system. The diagnostics reside in the file system and several bootable disk slots. They are removed from the file system with the 'delete' utility. They are removed from the bootable slots by overwriting the images. The procedure follows. 1. Removing REMIDI The removal of REMIDI is accomplished by overwriting the two bootable REMIDI slots with the WCS image. 2. Update WCS Slot 2 Execute the UPDATE.WCS utility and respond to the prompts as shown below. ENTER WCS SLOT (0..3): - 2 AVAILABLE DISK UNITS ARE: - (displayed) DISK TO UPDATE : - Enter the disk number. WCS IMAGE FILE: - .R7Axx.INST.WCS.X (where X = A,B,C) X = A for MPx 9xxx X = B for MPx 7xxx, 8xxx X = C for Advanced Series WCS LEVEL OF WCS IMAGE FILE: - (displayed) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg022 During the update process, the following message appears: UPDATING DISK UNIT nn SECTOR xx When the update is complete, the following message appears: WCS UPDATE COMPLETED! The preceding should be performed on all system disks. 3. Update WCS Slot 3 Execute the UPDATE.WCS utility and respond to the prompts as shown below. ENTER WCS SLOT (0..3): - 3 AVAILABLE DISK UNITS ARE: - (displayed) DISK TO UPDATE : - Enter the disk number. WCS IMAGE FILE: - .R7Axx.INST.WCS.X (where X = A,B,C) X = A for MPx 9xxx X = B for MPx 7xxx, 8xxx X = C for Advanced Series WCS LEVEL OF WCS IMAGE FILE: - (displayed) During the update process, the following message appears: UPDATING DISK UNIT nn SECTOR xx When the update is complete, the following message appears: WCS UPDATE COMPLETED! The preceding should be performed on all system disks. 4. Removing DEMON The removal of DEMON is accomplished by overwriting the bootable DEMON slot with DEMON.UX. 5. Update OS Slot 3 Execute the UPDATE.OS utility and respond to the prompts as shown below. BOSS/VS Image File Name: - DEMON.UX Target OS Slot (0/1/3): - 3 Target WCS Slot (0-3): - 0 Target Drives (0/1/All/Quit): - Enter the disk number During the update process, the following message appears: Update in progress : x/y : zz% When the update is complete, the following message appears: Updates all complete. The preceding should be performed on all system disks. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg023 6. Removing diagnostics from the file system The diagnostics are removed from the file system using the 'delete' utility. The diagnostics are found in the system node .R7Axx.DIAG. The files in the following nodes should be deleted from the file system. .R7Axx.DIAG. .ENHANCER7A. .TRACKER. The following files should be deleted: .AC (MPX 9000 Series 1/4" tape boot OS image with DIVE) .AT (MPx 9000 Series 1/2" tape boot OS image with DIVE) .BC (MPx 7000 Series 1/4" tape boot OS image with DIVE) .BT (MPx 8000 Series 1/2" tape boot OS image with DIVE) .CC (Advanced Series 1/4" tape boot OS image with DIVE) .CT (Advanced Series 1/2" tape boot OS image with DIVE) The following file(s) should be added as a replacement for the file(s) deleted above. .ACX (MPx 9000 Series 1/4" tape boot OS image without DIVE) .ATX (MPx 9000 Series 1/2" tape boot OS image without DIVE) .BCX (MPx 7000 Series 1/4" tape boot OS image without DIVE) .BTX (MPx 8000 Series 1/2" tape boot OS image without DIVE) .CCX (Advanced Series 1/4" tape boot OS image without DIVE) .CTX (Advanced Series 1/2" tape boot OS image without DIVE) This completes the diagnostic removal procedure! 6. HARDWARE ________ When upgrading to O.S. levels 9/8.7A, hardware changes, per se, are not required EXCEPT if your system contains a DMA-II. However, the following list of PCBA revision levels indicates the MANDATORY and RECOMMENDED revision levels of MPx and ADVANCED SERIES PCBA's. MANDATORY means that the specified revision level is needed for system operation. This level provides minimum assurance that your customer's system will operate in a stable manner. RECOMMENDED means that the specified revision level ensures the reliable operation of your customer's system. The RECOMMENDED (or higher) revision levels help to assure reliability and stability. If your customers' system PCBA's are at MANDATORY levels or below, careful plans should be made to replace the PCBA's with the RECOMMENDED (or higher) revisions. This should be done on a one per visit basis, such as one board per PM visit. DO NOT replace all PCBA's simultaneously. Some RECOMMENDED revision levels may vary based on specific system configurations, as detailed below. For example, the 16Mb High Speed Memory PCBA requires specific MCS and Terminator PCBA's. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg024 6.1. MPX 7000, 7100, AND 8000 PCBA NOTES ___ _____ _____ ___ ____ ____ _____ 1) MCS 903374-001 PCBA Revision L is the mandatory and recommended level. Revision S adds another option to the switch setting of SW-1. SW-1 position 4 (SW1-4) is switch selectable between MPx 7000/7100/8000 Series Systems (SW1-4, OPEN) or MPx 9xxx Series Systems (SW1-4, CLOSED). If the MCS PCBA, at revision S, is switch selected for MPx 9xxx Series Systems and installed into an MPx 7000/7100/8000 Series System, it will not load. - MCS 903374-002 PCBA-Revision V Revision V creates the -002 assembly. This assembly can be used on all MPx systems. 2) MDI 903361-001 PCBA Revision L is the mandatory and recommended level. This level prevents the MDI/ACS clocks from drifting and getting out of phase, which causes "INVOP" and "NILPTR" dumps. - MDI 903408-001 PCBA Revision K is the mandatory and recommended level. This level prevents the MDI/ACS clocks from drifting and getting out of phase, which causes "INVOP" and "NILPTR" dumps. 3) ACS 903379-001/-002 PCBA's Revision L is the mandatory and recommended level. 8000 systems on OS 8.4B or above require revision L, boot prom version 2.0.0.1 or higher. 7000 systems require revision Y or above, boot prom version 2.0.0.4 or higher (MPC support). Revision level Z, boot prom version 2.0.0.2, cannot be used on 7000 systems (no MPC support). Revision levels V and W, boot prom version 2.0.0.3, is obsolete; do not use. Tape load support from a BMTC requires revision T, boot prom version 2.0.0.5 or higher. Systems with 8-inch fixed drives require revision AA, boot prom version 2.0.0.5 or higher. - ACS 903379-003 PCBA Revision AD creates the -003 assembly. This version of the ACS PCBA can also be used in 7000/8000 systems. 7100 systems require AD or higher and this revision level is also required for support of the 120Mb MTCS tape. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg025 Board versions -002 or -003 are mandatory for 3 CPU systems, MPx 7xxx/8xxx Series Systems. 4) MPC 903500 PCBA Revision H is the mandatory and recommended level. If used in the MPx 7100 system, remove JMP3, if present, and set SW2-1 and SW2-4 OFF. - MPC 903546 PCBA Revision B is the mandatory level; revision H is the recommended level. If used in the MPx 7100 system, remove JMP3 if present and set SW2-1 and SW2-2 OFF. 5) TDP Controller 903217-001 PCBA Revision K is the mandatory level. Revision K eliminates excessive sector number errors written to the ERRORLOG. Revision W is the recommended level. This revision checks for Signetic IC's at locations 9E and 10K, if the IC's at these two locations are something other than Signetics, then this revision level is not required. Issue with 8" drives only. - TDP Controller 903453-001 PCBA New build TDP controller, which replaces TDP controller 903217-001. Revision A is the mandatory level. Revision J is the recommended level. This revision checks for Signetic IC's at locations 9E and 10K, if the IC's at these two locations are something other than Signetics, then this revision level is not required. Issue with 8" drives only. 6) NIMLC Controller 903381-001 PCBA Revision E is the mandatory level; revision K is the recommended level. This IMLC must be located to the right of the CPU set. Revision G provides correct line status for Data Set Ready (DSR), when no device is attached. Revision K is mandatory for all three (3) mainframe systems. - NIMLC Controller 903381-002 Revision N creates this version of NIMLC for international use. It provides RS-232-C interface on Port B, using standard 1488/1489 IC's to support cabling longer than 50 feet (provides higher input impedance interface required for use on various Wide-Area Networks). SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg026 - NIMLC Controller 903534-001 PCBA Revision D is the mandatory and recommended level. Provides the same interface as the 903381-002 PCBA on ports A and B. This NIMLC can be located on the left or right of the CPU. - NIMLC Controller 903251-001 PCBA This NIMLC was used with the 810 system and will not operate on the MPx series systems. 7) Memory (1Mb, 2Mb, 4Mb) 903516-00x PCBA Revision A is the mandatory level; revision E is the recommended level. Memory 903516-001 PCBA is the 2Mb version. Memory 903516-002 PCBA is the 4Mb version. Memory 903516-003 PCBA is the 1Mb version. 8) Terminator 903199 PCBA Revision D is the mandatory and recommended level. Revision H creates the -004 assembly. Revision H can be used on all MPx systems. 6.2. MPX 9XXX SERIES SYSTEM PCBA NOTES ___ ____ ______ ______ ____ _____ NOTE: An asterisk (*) appears in front of revision levels that are mandatory for main memory support above 12 megabytes. Higher revision levels may be used too. 1) MCS 903374 PCBA Revision L is the mandatory level; revision S is the recommended level. Revision S, or above, is required for reliable system operation. Revision S adds another option to the switch setting of SW1. SW1 position 4 (SW1-4) is switch selectable between the addressing schemes of the MPx 7000/7100/8000 (SW1-4, OPEN) Series Systems or the MPx 9xxx Series Systems (SW1-4, CLOSED). If the MCS PCBA is switch selected for MPx 7000/7100/8000 systems and installed into an MPx 9xxx Series System, board addresses 32 thru 47 are reserved for the IMLC PCB only. If the MPx 9xxx scheme is used then there are no address restrictions. * Revision T is required for main memory support above 12 megabytes. Set SW1-4 to CLOSE for the 9xxx addressing scheme. * Revision V creates the -002 MCS. This revision is mandatory for support of the 16Mb memory board (P/N 903621) on 9xxx systems. It also can be used for main SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg027 memory support above 12Mb. 2) AMS 903548 PCBA Revision F is the mandatory level, revision L is the recommended level. Revision F released the 4K boot proms version 3.1.0.4. This revision, or above, is required for operation. * Revision N creates the -002 PCBA and is required for main memory support above 12 megabytes. Revision P creates the -003 PCBA and is required for MPx 94xx (SCSI) systems. The -003 PCBA can be used in all MPx systems. Revision P is required for support of the 621Mb fixed disk drive and the DMA-III PCBA. 3) ESTK 903552 PCBA Revision G is the mandatory and recommended level. * Revision J, or above, is required for main memory support above 12 megabytes. 4) IDC 903550-001 PCBA (with cache) IDC 903550-002 PCBA (without cache) Revision H is the mandatory level; revision P is the recommended level. Revision J addresses cache timing problems on selected systems. Do not replace the IDC PCBA on an error free system. 5) IDC64 903597-001 PCBA (with cache) IDC64 903597-002 PCBA (without cache) Revision E is the mandatory level; revision H is the recommended level. * IDC64 PCBA is required for support of main memory above 12 megabytes. Strap E6 to E7 must be out to configure PCB for use above 12MB. 6) DMA-I 903554 PCBA * Revision H is the mandatory level; revision AA is the recommended level. Revision H is required for the 600 LPM band printer, model 20. It is also required if 300Mb 8-inch drives log excessive errors in the ERRORLOG. Revision N is required when used with the DMA-II. Revision P, or above, is required for reliable system operation, also if the DMA-III is in the system. Revision R is required for use with the 16Mb memory board for full power fail recovery. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg028 Revision Z is required for systems that have more than 2 DMA's installed for performance. Revision AA is recommended when system also contains DMA-II. This revision eliminates soft Head/Cyl (8004) errors reported against the drives supported on the DMA-I when DMA-II installed. This revision also reports 8001 'Offline status' instead of 8002 'Not ready' when taking disk packs out of removable drives. 7) DMA-II (SCSI) 903599 PCBA Revision K required for MPx 94xx SCSI disk drive support; requires 9.6C or later O.S. and the AMS -003 version. Revision L contains a fix for excessive soft errors logged in the ERRORLOG when both DMA-I's and DMA-II's are in the same system. Revision M Creates the DMA-II -002 version. This revision has become the mandatory and recommended level. This is the mandatory level for support of the 364Mb (M380) and 690Mb (M760) SCSI disk drive. NOTE: This level of DMA-II is mandatory if n.6G OS, or above, is installed on the system. (It is also a replacement for the -001 and does not require the n.6G OS or above.) - DMA-II (SCSI) 903741 PCBA This is the new version of DMA-II due to artwork changes. It may be used in place of 903599 PCBA and visa versa. Revision E has become the mandatory and recommended revision level. This revision is mandatory for support of the 364Mb (M380) and 690Mb (M760) SCSI disk drive. This creates the -002 version. NOTE: This level of DMA-II is mandatory if n.6G OS, or above, is installed on the system. 8) DMA-III (SMD) 903679-001 PCBA The DMA-III is required for support of the F621Mb fixed disk drive. (The F621Mb disk also requires the 903548-003 AMS board.) The DMA-III revision C controller also supports the 300Mb disk drive without the use of the SMD-I/II PCBA. This controller has the SMD logic embedded. Revision E is required for DMA-I/II/III to reside in the same system. Revision G is required for systems that have more than 2 DMA's installed for performance. Revision J is now the recommended/mandatory revision level. This level prevents possible data corruption. When a DMA-III is replaced, this level should be used. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg029 9) NIMLC 903381-001 PCBA Revision K is the mandatory and recommended level. This NIMLC must be located to the right of the CPU set. - NIMLC 903381-002 PCBA Revision N creates this version of NIMLC for International use. It provides RS-232-C interface on Port B using standard 1488/1489 IC's to support cabling longer than 50 feet (provides the higher input impedance interface required for use on various Wide-Area Networks). - NIMLC 903534 PCBA Revision D is the mandatory and recommended level. This revision provides the same interface as the 903381-002 PCBA on ports A and B. This NIMLC can be located on the left or right of the CPU set. - NIMLC 903251 is OBSOLETE This NIMLC was used with the 810 system and will not operate on the MPx Series Systems. NOTES: There have been a few instances when a known good IMLC is installed into the MPx 9xxx system, the RED LED (Parity error) comes on during load (903534/903381). In this case, install JMP C on the PCBA. When the JMP C option is used on the MPx 9xxx system and "T0" is a serial terminal, the system will hang in the TYPE II/III load. This side effect only occurs with the 9.6A OS and is fixed in 9.6B OS and above. Refer to Field Bulletin #375. 10) Memory (1/2Mb and 1Mb) 903349 PCBA Revision V is the mandatory and recommended level. This revision is not to be used with greater than 12 megabyte support. 11) Memory (2 and 4 MB) 903516-00x PCBA Revision E is the mandatory and recommended level. Memory 903516-001 PCBA is the 2Mb version, 903516-002 PCBA is the 4Mb version. * Revision J is required for support of main memory above 12 megabytes. Support of main memory above 12 megabytes is supported on MPx 9500 and 9600 Series Systems only. JMP 5 at location 1E = 1 to 2, and IC pad location 1A = 8 to 9. 12) 16/8/4Mb High Speed ECC Memory 903621-00x PCBA High Speed ECC Memory 903621-001 (16Mb), -003 (8Mb), -004 (4Mb) version are supported on the MPx 9xxx Series Systems. Requires MCS -002, Terminator -004, DMA-I at revision R or above for MPx Series Systems. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg030 Revision C is the mandatory level; revision F is the recommended level. Revision G creates the 903621-005 (16Mb), -007 (8Mb), -008 (4Mb) versions. Revision N if 30 or more slots are used in 9530. 13) Terminator 903199 PCBA Revision D is the mandatory and recommended level. Revision H creates the -004 assembly, which is mandatory for support of the 16Mb, High Speed ECC memory board versions (P/N 903621). 14) Non Supported PCBA's on MPx 9xxx Series System The following boards are NOT supported on MPx 9xxx Series Systems: 1) 7000/7100/8000 CPU set. 2) TDP (Must be replaced by the BMTC for tape support). 3) MPC. 6.3. PCBA'S FOR ALL MPX 7/8/9XXX SERIES SYSTEMS ______ ___ ___ ___ ________ ______ _______ The following are PCBA'S common to all MPx Series Systems without system model dependencies: 1) BMTC 903413 PCBA Revision R is required for full MTCS support. This is the minimum revision for support of the HCC tape unit. NOTE: The HCC is supported on the MPx 9xxx and Advanced Series systems only. Revision U is required for support of the GCR 1/2" tape drive model 4405. Revision Z allows the BMTC to operate on the left or right side of the CPU set. Revision AD is the mandatory and recommended level. This revision level will insure that a 'hard' error is posted, during restore of data, when using the GCR tape unit. This level aslo cures a problem where the BMTC goes 'offline' when using SAVERESTORE. 2) Local Area Network Controller (LAN) 903595 PCBA Revision E is the mandatory level; revision F is the recommended level. With the release of the 9.6A/8.6A O.S., a new controller is supported: The Local Area Network controller. The LAN PCBA provides the ability to tie like systems together (MPx to MPx) in a local environment not more than 4000 feet apart. Each system requires one LAN SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg031 controller, and both systems must be on the same O.S. level. The LAN may be installed either to the right of the CPU set(s) after the BMTC PCBA or to the left of the MCS PCBA. Refer to the MAGNET section in this document for further information on the Local Area Network. Revision H creates the -002 version. This version can be used on all MPx series systems and ASxx systems. 3) 16-Way Controller 903437 PCBA 16-Way controllers require the use of an I/O panel. The I/O panel is supplied with the purchase of the PCBA. Revision J is the mandatory and recommended level. Revision R creates the -002 version that supports hardware flow control with the n.7A, or above release of software. Cable PN 916509, revision B, must also be used for this feature. 4) 8-Way Controller 903383 PCBA Revision A is the mandatory and recommended level. 5) VCON Controller 903377 PCBA Revision C is the mandatory and recommended level. 6.4. ADVANCED SERIES PCBA NOTES ________ ______ ____ _____ The following are PCBA's that are supported on the ADVANCED SERIES and their revision levels. NOTE: An asterisk (*) appears in front of revision levels that are MANDATORY for the Doublewide backplane chassis. A pound sign (#) appears in front of revision levels that differ form the minimum revision levels of the Advanced Series systems. These revision levels are MANDATORY for the Advanced Series model 21 system. 1) MCS/M 903718 PCBA Revision G is the released level of this PCBA. The MCS/M (Memory Communication Support with Memory) PCBA provides boot load function/clocks/4-way and 4Mb of main memory. # Revision H (-002) is the mandatory level for support of the DMA-II PCBA and the SCSI disk drives on the Advanced Series system. Revision J required for 19.2K Baud and 7/8 bit data support for T0. 2) NEP II 903705 PCBA Revision G is the mandatory level; heat-sink added. Revision J recommended. * Revision K is the mandatory level when used in the Doublewide backplane chassis. This is also the SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg032 recommended level for the model 21 system. 3) STACHE II 903707 PCBA Revision D is the released level of this PCBA. The STACHE II PCBA is an optional PCBA that makes up the Advanced Series Model 6x. It contains the Rstack, Code Cache, and Data Cache. * Revision F is mandatory for Doublewide backplane chassis. 4) MBA 903617 PCBA Revision D is the released level of this PCBA. The MBA (Memory Bus Adapter) PCBA is required to support the shared memory controllers developed for the MPx 8/9xxx systems (160ns clock) on the Advanced Series Models 40/60 (80ns clock). Revision E is mandatory for support of the Advanced Series system. # * Revision H is mandatory for the Doublewide backplane chassis. This is also the recommended revision level for ALL Advanced Series systems. 5) BMTC 903413 PCBA Revision Z is mandatory for support of the Advanced Series systems. 6) LAN 903595-002 PCBA Revision H creates the -002 version, this version is mandatory for support of the Advanced Series systems. 7) DMA-I 903554 PCBA Revision R is mandatory for support on the Advanced Series, due to the 1Mbit rams used for main memory (MCS/M and 16Mb PCBA's) and full power fail recovery. Revision T corrects a problem in Revision R firmware which caused the timeout LED (DS2) to turn on during REMIDI testing in the Advanced Series family only. Revision Z is required for systems that have more than 2 DMA's installed for performance. Revision AA is recommended when system also contains DMA-II. This revision eliminates soft Head/Cyl (8004) errors reported against the drives supported on the DMA-I when DMA-II installed. This revision also reports 8001 'Offline status' instead of 8002 'Not ready' when taking disk packs out of removable drives. 8) DMA-II (SCSI) 903599-002 PCBA The DMA-II requires the MCS/M -002 for support. Revision M is mandatory for support of the 364Mb (M380) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg033 and SCSI 5-1/4 inch disk drive. This revision creates the -002 version. Revision N is the mandatory revision level if the Advanced Series system contains more than 4MB of main memory using the 903621-00x High Speed ECC memory. - DMA-II (SCSI) 903741-002 PCBA The DMA-II requires the MCS/M -002 for support. Revision E is mandatory for support of the 364Mb (M380) and 690Mb (M760) SCSI 5-1/4 inch disk drive. This revision creates the -002 version. Revision F is the mandatory revision level if the Advanced series system contains more than 4MB of main memory using the 903621-00x High Speed ECC memory. 9) DMA-III (SMD) 903679-001 PCBA The DMA-III is required for support of the F621 (600Mb) disk drive. It also supports the (300Mb) disk drive without the use of the SMD-I/II PCBA. This controller has the SMD logic on board. Revision E supports the DMA-I and DMA-II is also in the system. Revision G is required for systems that have more than 2 DMA's installed for performance. Revision J is now the recommended/mandatory revision level. This level prevents possible data corruption. When a DMA-III is replaced, this level should be used. 10) IMLC 903534 PCBA Revision D is mandatory for support of the Advanced Series. This version of IMLC, at the indicated revision level, is required to function on the left side of the CPU set. Remove JMP C if installed. 11) 16/8/4Mb High Speed ECC Memory 903621-00x PCBA Revision G creates the -005 (16Mb), -007 (8Mb), -008 (4Mb) versions. Refer to DMA-II section for other concerns if DMA-II is in the system. # * Revision N is the mandatory level. This revision helps prevent the possibility of parity errors during Nibble Mode cycles (Code Cache). 12) 8-WAY 903383 PCBA There is no mandatory revision level required for support of this PCBA on the Advanced Series. 13) 16-Way 903437 PCBA Revision J is LARL for support on the MPx and Advanced SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg034 Series. Revision R creates the -002 version that supports hardware flow control with the n.7A, or above release of software. Cable PN 916509, revision B, must also be used for this feature. 14) Terminator 903199-004 PCBA Revision H is the mandatory level, and it creates the -004 version. 15) Terminator, High Speed 903769 PCBA * Revision A releases the High Speed Terminator, mandatory in Doublewide chassis. 16) LS-700 Power Supply Assembly 907295-001 If any MPx 8000 system is being upgraded to the Advanced Series family, the LS-700 assembly 907295-001 must be at revision AA. (PCBA 903386-001, inside the LS-700 assembly, will be at revision AB or above.) If any MPx 9xxx system is being upgraded to the Advanced Series family, the LS-700 power supply does not need to be replaced. The load sustained by this power supply under the 9xxx configuration gives sufficient evidence that the existing revision level is adequate for the Advanced Series. 6.5. PCBA'S NOT SUPPORTED ON ADVANCED SERIES ______ ___ _________ __ ________ ______ The following boards are NOT supported on the Advanced Series family: 1) 7x00/8000/9x00 CPU sets. (Use Advanced Series 40/60 CPU's) 2) MCS PCBA. (Use MCS/M) 3) MPC, TDP and DMA-II-001. (Use DMA-I, DMA-II-002, and DMA-III) 4) Memory 903349 (1Mb assembly), 903516 (4Mb assembly), 903621-001/-003/004. (Use 16Mb: -005, 8Mb: -007, 4Mb: -008) 5) VCON PCBA and HVDT's 6) Terminators -001 (Below revision H). (Use -004) 6.6. PERIPHERAL DEPENDENCIES __________ ____________ 6.6.1. GCR TAPE DRIVE ___ ____ _____ It is possible for a hang condition to occur in SAVERESTORE, if the GCR tape drive does not have the following minimum revision levels: IF CARD 403923205 (Previously, the LARL was 403923202) CP CARD 403864305 (Previously, the LARL was 403864303) BMTC PCBA revision AD is mandatory for support of the GCR due to a buffer transfer issue. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg035 6.6.2. SCSI MTCS TAPE DRIVE ____ ____ ____ _____ On the 120MB SCSI MTCS 1/4-inch tape drive (4406), the E-PROM (OEM PN 966039; MBF PN 400716-103) at location 'U6' should be 3X10. This tape drive is used on MPx 94xx systems only. Requires the DMA-II for support. The 525MB SCSI MTCS 1/4-inch tape drive can replace the 120MB SCSI MTCS without any other hardware changes. You must insure that the proper 1/4-inch tape cartridge is used to achieve proper data density storage. 6.6.3. HIGH CAPACITY CARTRIDGE (HCC) TAPE DRIVE ____ ________ _________ _____ ____ _____ The HCC tape drive is supported on the MPx 9xxx and Advanced Series only. It requires the n.6G OS, or above, and the BMTC controller. The BMTC must at least be revision R or higher. The revision is dependent on other tape devices that may be attached to the same BMTC. Refer to the BMTC sections, under your system model. 6.6.4. TERMINALS _________ 1) The DT-4313 terminal must have REV E firmware to support Industry Standard slave printers. 2) T0 MUST be a model 4309 or later model VDT. VDT's 7250 and 7270 (4301) are not supported as T0 on release levels n.6C and above due to default terminal driver change. This change corrected the time differences seen in Saverestore Type I vs Type II load. 3) OS level n.6E and above loads T0 with defaults when going into a Type 2 or 3 load. After reloading the system, these settings remain loaded in the terminal. If T0 is configured to settings other then the default values, the terminal will need to be reset. Defaults = EVDT, 9600, 7-bit, ODD Parity. The MCS/M at revision J, used on the Advanced Series systems, allows T0 to use 19.2K baud. 6.6.5. DISK DRIVES ____ ______ 1) The 590MB (aka F621/600Mb) fixed disk requires the -003 version of AMS PCBA P/N 903548 when used in 9xxx systems. The F621Mb disk is supported by the DMA-III controller, P/N 903679. Supported on n.6E OS or above. 2) The 300MB (aka P314) fixed disk requires revision AA of ACS PCBA P/N 903379 when installed on MPx 7xxx/8xxx systems. TDP (PDC) controller P/N's 903217 and 903453 require IC's OTHER THAN Signetics (indicated by a bold 'S') at locations 9E and 10K (74S240). 3) The 250MB (aka M280) SCSI 5-1/4 inch disk drive requires n.6C OS or above and the -002 (mandatory revision) DMA-II. 4) The 364Mb (aka M380) SCSI 5-1/4 inch disk drive requires SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg036 n.6G OS or above and the -002 version of the DMA-II. See MCS/M and DMA-II for other requirements on the system that it will be installed on. 5) The 690MB (aka M760) SCSI 5-1/4 inch disk drive requires n.6G OS or above and the -002 version of the DMA-II. See MCS/M and DMA-II for other requirements on the system that it will be installed on. 6.7. HARDWARE FLOW CONTROL - NEW FEATURE ________ ____ _______ _ ___ _______ With this release the 16-way will support uni-directional hardware flow control. The 16-way that supports this feature is PN 903437-002, revision R or above. A new I/O cable will also be required for support of this feature, PN 916509, revision B. The device will be able to throttle the host, but the host will not throttle the device. (This will cure the 'Data Loss' problem that occurs with ISP printers when they are turned off.) Flow control is implemented by monitoring the CTS signal of the interface. If CTS drops, the host will cease transmitting until CTS is detected or until a specified timeout has occurred. If the timeout occurs, a "timeout" error will be returned to the user. The timeout value is reset for each character transmitted. This means that if CTS drops multiple times during a transmission, 5 seconds (for example) will be allowed for each detection of CTS dropping. Hardware flow control is available for any serial device except for SPE.MODEM. Hardware flow control must be configured in TERM.CONFIG for it to be operational. Enter the extended options menu from the port main menu and the option will appear: USE CTS FLOW CTL (Y/N) Enter a 'Y' to have the system recognize CTS flow control for this device. Hardware flow control requires a new cable; 916509-xxx. This cable comes with a 15 pin connector designed to be attached to the backpanel serial connector. 7. INSTALLATION ____________ 7.1. GENERAL INFORMATION _______ ___________ IMPORTANT NOTE 1: AS OF RELEASES 9/8.6C, POSITIONING OF THE O.S. AND WCS SLOTS HAS BEEN ADJUSTED SLIGHTLY. THEREFORE, O.S./WCS LEVELS PRIOR TO 9/8.6C CANNOT RESIDE IN SLOTS ON THE SAME DISK WITH RELEASE LEVELS 10/9/8.7A. IMPORTANT NOTE 2: THE .SYSDATA.SECURITY.DATA FILE SHOULD BE SAVED BEFORE UPGRADING TO 10.7A/9.7A/8.7A IF YOUR CURRENT RELEASE IS BELOW 9/8.6C. AS OF RELEASES 9/8.6C, THE SECURITY.DATA FILE HAS A NEW FORMAT AND IS NOT TRANSPORTABLE TO RELEASES PRIOR TO 9/8.6C. IMPORTANT NOTE 3: IT IS NOT EXPECTED THAT A DOWNGRADE FROM SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg037 10/9/8.7A WILL BE NECESSARY. HOWEVER, IF A DOWNGRADE IS PERFORMED TO A RELEASE PRIOR TO 9/8.6C *11, THE USER'S FILES MUST BE TRANSPORTED TO THE OLDER O.S. LEVEL VIA EXTTAPE, MCSI, FTF, TBC, or ATP. FAILURE TO DO SO WILL RESULT IN INCOMPATIBLE FILE CONTROL SEGMENTS. THE VOLUME LABEL MUST ALSO BE REWRITTEN ON THE OLDER O.S. LEVEL. THERE ARE NO RESTRICTIONS ON A DOWNGRADE TO 9/8.6C *11. IMPORTANT NOTE 4: THE FORMAT OF THE .SYSDATA.TERMINALS.DEF1 AND .SYSDATA.TERMINALS.DEFN2 FILES WERE CHANGED ON 8/9/10.6H. IF YOUR CURRENT RELEASE IS PRIOR TO 8/9/10.6H THEN THESE FILES SHOULD BE SAVED IN CASE A DOWNGRADE IS NECESSARY. IMPORTANT NOTE 5: THE FORMAT OF SOME OF THE .SYSDATA.SPL. FILES WERE CHANGED ON 8/9/10.6H. IF YOUR CURRENT RELEASE IS PRIOR TO 8/9/10.6H THEN THESE FILES SHOULD BE SAVED IN CASE A DOWNGRADE IS NECESSARY. ALSO, DUE TO THESE CHANGES, 8/9/10.6H AND ABOVE MAY NOT RESIDE ON THE SYSTEM WITH PREVIOUS OS LEVELS. ################################################################ # # # IF UPGRADING A SYSTEM TO *.7A FROM A RELEASE, PRIOR TO # # 8/9/10.6H. THE UTILITY TERM.CONFIG MUST BE EXECUTED TO # # CONVERT THE TERMINAL DEFINITION FILES TO THEIR NEW FORMAT. # # PLEASE SEE THE UPGRADE SECTION FOR DETAILS. # # # ################################################################ **************************************************************** * * * IN THE FOLLOWING INSTALLATION INSTRUCTIONS, THE * * REFERENCES TO ".R7Axx" SHOULD BE REPLACED BY THE ACTUAL * * RELEASE LEVEL THAT IS FOUND ON THE LABEL OF THE OS TAPE. * * * **************************************************************** The upgrade can be done in one of three ways depending on how the system is configured now: 1) A new system 2) Upgrade from 8.4D and below 3) Upgrade from 8.4E and above to *.7A Each of these methods share common steps in the upgrade. Below is a chart showing the flow of steps from each upgrade: (continued on next page) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg038 ============================================================================= INSTALLATION FLOW CHART ____________ ____ _____ --------- --------- --------- | | | | | | | NEW | | UPGRADE | |UPGRADE84| | | | | | | --------- --------- --------- | | | | | PRELIMINARY PREPARATION |<----------------------|<---------------------| | ALT LOAD | |------------------------------ CHANGE VOLUME LABEL | | | | | UPDATE FAMILY INFORMATION | | |UPGRADE | | INITIALIZE FAMILY | | | |<----------------------------| CHANGE INSTALLATION PARAMETERS | | RESTORE OS | | UPGRADE84 INSTALL CONFIG RECORD |------> NEW FILESYSTEM CONVERSION - |--------------------| | |<-------------------------------------------------------| UPDATE REMAINING SLOTS | | UPDATE COMPLETE ============================================================================= Using this chart, any upgrade can be accomplished quickly and easily. In each section, watch for underlined text as these will be special instructions for a particular upgrade method. These Installation Instructions assume that the reader is familiar with BOSS/VS installation procedures and TYPE 3 LOAD Special Functions. For further information, see the BOSS/VS INSTALLATION GUIDE, M5138. If you have just received a new system, please note the following: new systems are shipped with the operating system installed on the disk, and the TYPE 3 LOAD (Special Functions) parameters already set up. If you wish to change the disk/family information on your new system, you must run Option 2 (Update Family Information) of INITIALIZATION OPTIONS (OPTION 2 on the main menu) in a TYPE 3 LOAD. For further information on setting up families on your system, see the BOSS/VS INSTALLATION GUIDE, M5138. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg039 Beginning with release 9.6A/8.6A there is a change in the way terminals are enabled for user log-on at system load time. Initial enabling of the TERMINALS group, which allows users to log-on, is now under user control through the use of the Startup Command File. If the file does not exist, the TERMINALS group is enabled automatically. Refer to section 7.10 for further information on the startup command file and startup procedures for JOB MANAGER, MAGNET, and the SPOOLER. Since the operating system can be released on 1/2" (reel) or 1/4" (cartridge) tape, the word "tape" means either media form. The names of the files that are loaded into the OS/WCS slots are generic in order to simplify installation procedures. The first letter of the name will designate the machine type as follows: A - MPx 9xxx Machine Type B - MPx 8xxx/7xxx Machine Type C - ADVANCED SERIES Machine Type U - Universal Disk Image Format The second letter of the name will be used to designate the boot image type as follows: C - 1/4 inch Cartridge Tape Boot Image D - 1/2 inch Diagnostic Tape Boot Image Load & Execute T - 1/2 inch Tape Boot Image Load & Copy V - Universal Disk Image Format The third letter, if present, will be used to designate the Micro Peripheral Controller WCS images and the four REMIDI image formats, as follows: A - First REMIDI Module B - Second REMIDI Module C - Third REMIDI Module D - Fourth REMIDI Module M - Micro Peripheral Controller FILE_NAMES __________ BOSS/VS IMAGES .R7Axx.INST.OS.CT 1/2 Inch Tape Boot, ADVANCED SERIES .R7Axx.INST.OS.CC 1/4 Inch Tape Boot, ADVANCED SERIES .R7Axx.INST.OS.AT 1/2 Inch Tape Boot, MPx 9xxx .R7Axx.INST.OS.AC 1/4 Inch Tape Boot, MPx 9xxx .R7Axx.INST.OS.BT 1/2 Inch Tape Boot, MPx 8xxx .R7Axx.INST.OS.BC 1/4 Inch Tape Boot, MPx 7xxx .R7Axx.INST.OS.UV Universal Disk Boot Image, MPx/ADVANCED SERIES DEMON IMAGES .R7Axx.DIAG.DEMON.CC 1/4 Inch Tape Boot, ADVANCED SERIES SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg040 .R7Axx.DIAG.DEMON.CD 1/2 Inch Tape Boot, ADVANCED SERIES .R7Axx.DIAG.DEMON.AD 1/2 Inch Tape Boot, MPx 9xxx .R7Axx.DIAG.DEMON.AC 1/4 Inch Tape Boot, MPx 9xxx .R7Axx.DIAG.DEMON.BD 1/2 Inch Tape Boot, MPx 8xxx .R7Axx.DIAG.DEMON.BC 1/4 Inch Tape Boot, MPx 7xxx .R7Axx.DIAG.DEMON.UV Universal Disk Boot Image, MPx/ADVANCED SERIES REMIDI MPx 7xxx/8xxx IMAGES .R7Axx.DIAG.REMIDI.BDM 1/2 Inch Tape Boot, MPC/LAN .R7Axx.DIAG.REMIDI.BCM 1/4 Inch Tape Boot, MPC/LAN .R7Axx.DIAG.REMIDI.BVM Disk Boot Image, MPC/LAN .R7Axx.DIAG.REMIDI.BD 1/2 Inch Tape Boot, CPU .R7Axx.DIAG.REMIDI.BC 1/4 Inch Tape Boot, CPU .R7Axx.DIAG.REMIDI.BV Disk Boot Image, CPU REMIDI MPx 9xxx IMAGES .R7Axx.DIAG.REMIDI.ADA 1/2 Inch Tape Boot Module 1 .R7Axx.DIAG.REMIDI.ADB 1/2 Inch Tape Boot Module 2 .R7Axx.DIAG.REMIDI.ADC 1/2 Inch Tape Boot Module 3 .R7Axx.DIAG.REMIDI.ADD 1/2 Inch Tape Boot Module 4 .R7Axx.DIAG.REMIDI.ACA 1/4 Inch Tape Boot Module 1 .R7Axx.DIAG.REMIDI.ACB 1/4 Inch Tape Boot Module 2 .R7Axx.DIAG.REMIDI.ACC 1/4 Inch Tape Boot Module 3 .R7Axx.DIAG.REMIDI.ACD 1/4 Inch Tape Boot Module 4 .R7Axx.DIAG.REMIDI.AVA Disk Boot Image for Module 1 & 2 .R7Axx.DIAG.REMIDI.AVC Disk Boot Image for Module 3 & 4 REMIDI ADVANCED SERIES IMAGES .R7Axx.DIAG.REMIDI.CD 1/2 Inch Tape Boot Module 1 through 4 .R7Axx.DIAG.REMIDI.CC 1/4 Inch Tape Boot Module 1 through 4 .R7Axx.DIAG.REMIDI.CVA Disk Boot Image Module 1 & 2 .R7Axx.DIAG.REMIDI.CVC Disk Boot Image Module 3 & 4 WCS FILES .R7Axx.INST.WCS.C WCS for ADVANCED SERIES .R7Axx.INST.WCS.A WCS for MPx 9xxx .R7Axx.INST.WCS.B WCS for MPx 8xxx/7xxx 7.2. NEW OPERATING SYSTEM INSTALLATION ___ _________ ______ ____________ Follow the instructions in this section if you are creating a SYSTEM disk on a newly formatted disk, or if you are changing a DATA disk to a SYSTEM disk. GO TO SECTION 7.5 TO BEGIN NEW OS INSTALLATION __ __ _______ ___ __ _____ ___ __ ____________ 7.3. UPGRADING TO 9.7A _________ __ ____ If you are installing the 9.7A O.S. on a newly formatted System disk or changing a Data disk to a System disk, go to the section above. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg041 If you are upgrading a 7xxx or 8xxx Series System to a 9xxx Series System, you must first run for a minimum of one week on O.S. 8.6A or above before the hardware upgrade. A new configuration record is required when upgrading to 9.7A from 9.6 O.S. levels. A new configuration record is also required when an upgrade includes new hardware. NOTE: If upgrading from 8/9/10.6H, then you may skip this ____ paragraph. The terminal configuration files changed with 8/9/10.6H. If upgrading from a release prior to 8/9/10.6H then these files must be converted. To convert the terminal configuration files, when the system is reloaded, enter the terminal configuration utility TERM.CONFIG. A message will be displayed that the terminal files are being converted. When this is complete the system needs to be reloaded for the configuration to take effect. UNTIL THIS CONVERSION AND REBOOT IS DONE, TERMINALS AND PRINTERS WILL NOT BE ACTIVE. NOTE: It is essential that the .SYSDATA.SECURITY.DATA file be backed up before upgrading to *.7A, if your current O.S. level is below *.6C. This SECURITY.DATA file will go through a conversion during the upgrade, and the converted file cannot be used on previous O.S. levels. The old version of SECURITY.DATA should be saved in case an O.S. downgrade is ever necessary. NOTE: The format of the .SYSDATA.TERMINALS.DEFN1 and .SYSDATA.TERMINALS.DEFN2 was changed on 8/9/10.6H. If the current release is below 8/9/10.6H, then please save these files in case a downgrade is necessary. NOTE: The format of some of the .SYSDATA.SPL. files was changed on release 8/9/10.6H. If the current release is below 8/9/10.6H, then please save these files in case a downgrade is necessary. Also, due to these changes, 8/9/10.6H and above may not reside on the same system with previous OS levels. 7.3.1. PRINTING OUT THE TERMINAL CONFIGURATION INFORMATION ________ ___ ___ ________ _____________ ___________ When upgrading from MPx 7xxx/8xxx Series Systems to the MPx 9xxx Series Systems, it is necessary to reference the terminal configuration in order to properly re-address the 9xxx controllers. Therefore, you must print out a copy of the terminal configuration information before upgrading. 1. Enter the TERM.CONFIG utility. 2. Select OPTION 2 DISPLAY A CONFIGURATION FILE. 3. When the following screen is displayed, enter these responses to the prompts: CONFIGURATION FILE: P OUTPUT DEVICE: DETAILED REPORT: Y ENTRIES CORRECT: Y The terminal configuration information should now be SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg042 printed. 7.3.2. SAVING FILES TO TAPE ______ _____ __ ____ Current files must first be backed up to tape, using the standard tape utility, SAVERESTORE. When saving files to tape, send the output from the save process to the printer. This will provide a record of backup for each file. Also it is recommended that all tapes be compared to the files on the disk. NOTE: It is essential that the .SYSDATA.SECURITY.DATA file be backed up before upgrading to 9.7A, if your current O.S. level is below 9.6C. This SECURITY.DATA file will go through a conversion during the upgrade, and the converted file cannot be used on previous O.S. levels. The old version of SECURITY.DATA should be saved in case an O.S. downgrade is ever necessary. GO TO SECTION 7.5 TO BEGIN UPGRADE TO 9.7A __ __ _______ ___ __ _____ _______ __ ____ 7.4. UPGRADING FROM RELEASE LEVELS 8.4D AND BELOW _________ ____ _______ ______ ____ ___ _____ NOTE: This section contains references to the FILESIZE, NFSCONVERT, and DISKANALYZER utilities. Further information on these utilities and their use during file conversion can be found in the following sources: - BOSS/VS FILE CONVERSION GUIDE, M5185 - BOSS/VS UTILITY USER GUIDE, M5102 - Software Announcements for release levels 8.4E and 8.5A/B/C/D - HELP SCREENS accessed by keying in UTILITYNAME.HELP in command mode Since release levels 8.4E and above contain new file formats and a new file system, conversion of files is required to make files compatible with the new file system if you are upgrading from a software release level of 8.4D or below. The file conversion can be done in two ways: A) From tape to disk B) From disk to disk Which method used depends on the configuration of the system. The disk to disk method is preferable for a system with removable disks. The disk to disk method involves upgrading the system disk with the new O.S. Then the system disk can be used to convert other disks by using the NFSCONVERT utility to convert one file from one disk to another. If the disk to disk method is used on fixed disks, any user files must be copied from the fixed system disk to another disk or to tape for conversion. This is because the system disk must be initialized and updated to the new O.S. to do the conversion. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg043 To do a tape conversion, a save and restore is performed with the SAVERESTORE utility in the normal manner. The conversion process is invisible to the user with the exception of the following status message that is displayed during conversion: "Now converting to NFS format...." The tape conversion requires about 4 minutes per megabyte of data. The installation procedure is broken into two parts: A) Preliminary evaluation B) Operating System upgrade and file conversion The preliminary evaluation is required to ensure that proper hardware and file preparation is done. An O.S. upgrade from releases of 8.4D and below entails loading of the 8.7A O.S. and converting files to their new format. In large configurations, the conversion process will take more than one day. At the end of this section is an upgrade and conversion checklist that should be used to track progress through the upgrade procedure. 7.4.1. HARDWARE EVALUATION ________ __________ All hardware must be checked for proper operation. All boards must be at proper revision levels (see the HARDWARE section 6 in this announcement). Ensure that all tape units are operating correctly. 7.4.2. FILE PREPARATION ____ ___________ Obtain a directory listing with partial attributes for each family in the system. This listing will help you to find files, if any, that need repair before conversion. Next, using DISKANALYZER, select the option "VALIDATE ALL FILES" to determine which files need repair. Files which have the following attributes MUST be repaired before they are saved to tape: A) Files which lack integrity. B) Files which have lost space. C) Non-serial files in which records used is greater than records defined. D) Files that have invalid format. These files can be located in several ways: A) Scan the directory listing noting any files flagged as lacking integrity. B) Use the report generated by the DISKANALYZER "VALIDATE ALL FILES" option. (Preferred method) C) Use the utility FINDLOSTSPACE (8.4C/D only). SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg044 All of the above methods should be used to find files that lack integrity and that have lost space. However, the directory listing must be scanned to find files that have a greater number of records used than defined as maximum records. This is a very important step. Any file possessing any of these attributes WILL NOT convert properly. They have to be repaired on a previous release before conversion. Any EDITOR recovery files must be recovered or deleted before conversion. The recovery files are identified by the node ED.REC. After the node, there will be a series of digits. These files can be found by scanning the directory listing. These files must be recovered by using EDIT.RECOVER or deleted by using the DELETE utility. ***************************************** * * * ALL FILES MUST BE FREE FROM LACK OF * * INTEGRITY, LOST SPACE, AND MAX * * RECORDS GREATER THAN DEFINED RECORDS. * * FILES WILL NOT BE CONVERTED IF THEY * * POSSESS ANY ONE OF THESE ATTRIBUTES. * * * ***************************************** 7.4.3. NEW FILE SYSTEM SPACE REQUIREMENTS ___ ____ ______ _____ ____________ The space required for files under the new file system is about the same as under 8.4D/C/B/A levels. However, it is recommended that a listing be obtained which displays the files and their new sizes. On the 8.4D release, the program FILESIZE is used to produce this listing. The program FILESIZE will display the file size under the new file system for each file in a given family. It will also display the total number of sectors required by the entire family under the new file system. 7.4.4. SAVING FILES TO TAPE ______ _____ __ ____ User files and the .SYSDATA. node must now be backed up to tape. It is STRONGLY recommended that these files be saved to tape even if disk to disk conversion is being used. This will allow recovery of files in case there are problems with the disk to disk conversion. It is necessary to save the .SYSDATA. node to preserve all system parameters. This node must be restored on the new file system along with the user files. It is essential that the .SYSDATA.SECURITY.DATA file be backed up before upgrading to 8.7A and saved for a period of time on tape. This SECURITY.DATA file will go through a conversion during the upgrade, and the converted file cannot be used on previous O.S. levels. The old version of SECURITY.DATA should be kept in case you need to perform an O.S. downgrade. The files are saved using the standard tape utility, SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg045 SAVERESTORE. When saving files to tape, send the output from the save process to the printer. These will provide a record of backup for each file. Also it is recommended that all tapes be compared to the files on the disk. When using the tape or disk conversion, the conversion requires temporary disk space to sort keyed (direct and sort) files. The space required varies with the number of records and the size of the key. To ensure proper space is available, the following steps should be observed: A) Do not restore the user default family until last. B) Convert large keyed files first. Step A ensures that the default user disk has a large amount of free space since this is where the tape and disk conversion utility defines the temporary files. Step B allows the files that require the most amount of temporary space to be converted first. To convert large keyed files first, they must be saved to tape first. The large keyed files can be identified by scanning the directory listing obtained in section 7.4.2. If using disk to disk conversion, the NFSCONVERT utility allows you to convert keyed files first. 7xxx/8xxx UPGRADE AND CONVERSION CHECKLIST 1) Hardware levels => section 6 2) Validate files => section 7.4.2 A) DISKANALYZER option "VALIDATE ALL FILES" B) DIR listings C) FINDLOSTSPACE Utility D) Delete unwanted EDITOR, SPOOL, and TEMP files 3) New file sizes => section 7.4.3 A) FILESIZE utility 4) Save files to tape => section 7.4.4 A) Large keyed files first 5) Update operating system => section 7.5 A) ALT-LOAD B) TYPE III - Options 1-4 C) Restore operating system files 6) File conversion A) Tape-to-disk => section 7.7.1 B) Disk-to-disk => section 7.7.2 7) Check file integrity 8) Complete installation SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg046 A) Update terminal configuration file 7.5. INSTALLING THE OS - LOADING SLOTS 0 AND 1 USING ALT LOAD __________ ___ __ _ _______ _____ _ ___ _ _____ ___ ____ NOTE: ALT LOAD has been enhanced so that it will automatically load both slots 0 and 1 on a new installation. (WCS slots 2 and 3 are also loaded with the BOSS/VS WCS for formatting purposes only. The user needs to reload these slots with the REMIDI WCS files, using UPDATE.WCS. See the sections on updating slots 2 and 3 in this announcement.) To perform an ALT LOAD from tape follow these steps: A) Mount the new release tape in the tape drive. (All front panel load select switches should be OFF if using tape drive 0. Switch 1 should be ON if using tape drive 1.) B) Press the "ALT LOAD" button on the front panel. First, a proprietary message will be displayed, and then the following load screen: ______________________________________________________________________ Load PROM Version: x.x.x.x SYSTEM SERIAL NUMBER : 000-00000 Load Drive n SERIAL NUMBER CREATOR: 000-00000 WCS 0 Version: x.x.x CONFIGURATION CREATOR: 000-00000 OS 0 Version: 7.1.x.x CPUs ID #s : n Memory (Mb) : n.0 Disk Drives : n BOSS/VS LOAD FROM TAPE Tape Drives : n Printers : n HVDTs : n IMLCs : n Serial Ports: n Date Format MM/DD/YY: BMTCs : n/n DATE = MM/DD/YY: LAN Cntrlrs : n TIME = HH:MM:SS: SYSTEM PREFIX: (family).R7Axx.SYS. System Default Family: (family) File System Write Through : T/F User Default Family : (family) Per-File Write Through : T/F Installation Name : (name) File System Security : T/F ____________________________________________________________________ Key in the current DATE and TIME at the above prompts. The screen will then display: ____________________________________________________________________ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg047 L O A D I N G . . . BOSS/VS Operating System Image Update Utility [version 7.1.x.x] OS/WCS information for drive n (nn): 0: ?????????????? ??????? | x x.x.x 1: ?????????????? ??.??.??.??? | ? ?.??.?? 2: -------------- -- -- -- --- | ????????? 3: ?????????????? ??????? | ????????? BOSS/VS Image File Name: (displays one of the following): OSN.CT0708xxxxx (ADVANCED SERIES) OSN.AT0708xxxxx (9x00 systems - 1/2-inch) OSN.AC0708xxxxx (9400 systems - 1/4-inch) OSN.BT0708xxxxx (8000 systems - 1/2-inch) OSN.BC0608xxxxx (7x00 systems - 1/4-inch) Target OS Slot (0/1/3) : '0' (or 1) Target WCS Slot (0-3) : '0' (or 1) Target Drives (0/1/All/Quit): (choose drive) ____________________________________________________________________ C) The Image File Name will be displayed by the system. Enter '0' or '1' at the slot prompts to load O.S. and WCS slots 0 and 1. Enter '0', '1', or 'All' at the drive prompt to update the appropriate drives. NOTE: Do not update drive 1 if it is a DATA disk and is to remain so. The system will now display: ___________________________________________________________________ Now updating WCS slot # n Update in progress: nn% Now updating BOSS/VS Image (displays one of the following): OSN.CT0608xxxxx (ADVANCED SERIES) OSN.AT0608xxxxx (9x00 systems - 1/2-inch) OSN.AC0608xxxxx (9400 systems - 1/4-inch) OSN.BT0608xxxxx (8000 systems - 1/2-inch) OSN.BC0608xxxxx (7x00 systems - 1/4-inch) Update in progress: nn% Image slot directory n/n:n Updates all complete. D O N E - R E A D Y F O R N O R M A L D I S K L O A D ___________________________________________________________________ When O.S. and WCS slots 0 and 1 have been updated, reload the system by pressing the LOAD switch. IF UPGRADING FROM 8.4E AND ABOVE, THEN GO TO SECTION 7.6.4. __ _________ ____ ____ ___ ______ ____ __ __ _______ ______ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg048 7.6. TYPE 3 LOAD (SPECIAL FUNCTIONS) ____ _ ____ ________ __________ NOTE: If any disk has a 'MASTER' status, no update to the disk will be allowed. You must change the disk to a 'BACKUP' status in order to perform the TYPE 3 LOAD functions. To do this, select OPTION 4 (CHANGE MASTER/BACKUP STATUS) from the TYPE 3 LOAD main menu. Be sure to change the disk back to a 'MASTER' status after the TYPE 3 LOAD functions are completed (if this status is desired). This MASTER/BACKUP status is simply a flag which makes it possible to write-protect a disk. It is not to be confused with the disk configuration (e.g., SYSTEM, DATA, BACKUP) specified in Option 1 (Change Volume Label Information) of INITIALIZATION OPTIONS (OPTION 2 on the TYPE 3 LOAD main menu). Note 1: When using NFSCONVERT, the following steps should ____ __ ____ _____ ___________ ___ _________ _____ ______ only be performed on the destination disk (which will be in ____ __ _________ __ ___ ___________ ____ ______ ____ __ __ the new filesystem format) ___ ___ __________ _______ Select OPTION 2 - INITIALIZATION OPTIONS Option 1 (Change Volume Label Information) must be done on all disks. Options 2 (Update Family Information) and 3 (Initialize Family Directory) must be done for each family. Option 4 (Change Installation Parameters) must be done on system disks only. 7.6.1. OPTION 1 (CHANGE VOLUME LABEL INFORMATION) ______ _ _______ ______ _____ ____________ All available disk drives will be displayed. An 'available' drive is any drive cabled to the system, whether enabled, disabled, powered ON or OFF. The selected drive entered in response to the Option 1 prompt must be online and ready. ENTER DRIVE NUMBER OF VOLUME LABEL TO CHANGE:______ (Enter volume label to change. The screen will change to display the information for only the drive whose volume label you choose.) SERIAL NUMBER _________ (Enter CR to accept current serial number.) DISK CONFIGURATION (1=SYSTEM, 2=DATA, 3=BACKUP) ____ (Enter the appropriate disk type.) SIZE OF DUMP AREA.....______ x 1024 BYTES (For system disks only, enter the size of the dump area SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg049 displayed on the line below this prompt as the area needed for both main memory and shared memory controllers. If installation of additional memory and/or shared memory controllers is planned, increase the dump area size to accommodate them. See Field Bulletin # 211, "Computing Dump Area Size".) FILE SYSTEM SPACE ______ x 1000 SECTORS (Enter the number displayed at the bottom of the screen for this prompt. The display will appear as "CR=X" where X is the maximum space allowed.) UPDATE DISK VOLUME LABEL (Y/N) __ (Enter "Y" if above information is correct.) Repeat the steps in option #1 for all remaining disk drives. 7.6.2. OPTION 2 (UPDATE FAMILY INFORMATION) ______ _ _______ ______ ____________ NOTE: Removable drives can only have one member per family. Fixed drives can be combined to create a larger capacity disk family. The disk information for all drives on the system is displayed and the cursor is positioned at 'FAMILY BASE DRIVE NUMBER'. FAMILY BASE DRIVE NUMBER ___ FAMILY NAME ______ (CR for default family name.) DRIVE NUMBERS OF OTHER DISKS IN FAMILY? (TYPE SPACES FOR NO OTHER DRIVES) (Enter all other drive numbers for this family or spaces if none. The drives must be fixed media drives.) UPDATE DISK (Y/N)? Repeat the steps in option #2 until all drives are identified in a family. 7.6.3. OPTION 3 (INITIALIZE FAMILY DIRECTORY) ______ _ ___________ ______ __________ This option displays all base drives on the system. FAMILY BASE DRIVE NUMBER ______ (Enter drive number to be initialized.) INITIALIZE FAMILY? (Y/N) __ (CAUTION: Ensure that all data you want is backed up. This step will delete all data on the disk.) Repeat the steps in option #3 for all defined families. 7.6.4. OPTION 4 (CHANGE INSTALLATION PARAMETERS) ______ _ _______ ____________ ___________ NOTE: On newly formatted disks, the following message will SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg050 be displayed: "CAN'T READ INITIALIZATION PARAMETERS FROM DISK. STATUS = (3,7,30,1), TO CONTINUE:" Just press and continue. Only SYSTEM disks will be displayed. DRIVE NUMBER _______ PRIMARY PREFIX __________________ (Enter (family).R7Axx.SYS. '(Family)' is the family where the operating system files will reside.) SECONDARY PREFIX _______________ (Enter (family).R7Axx.SYS. '(Family)' is the family where the alternate OS/WCS image files reside for slot 1.) SYSTEM INSTALLATION NAME ________________ (Sets the default installation name for a specified system disk. Used only with MAGNET. Enter for default.) DEFAULT USER FAMILY NAME _____________ (Enter default user family.) SECURITY (E=ENABLED, D=DISABLED) ___ FILE SYSTEM WRITE THROUGH? (E=ENABLED, D=DISABLED) ___ WRITE THROUGH DEFAULT ON FILE CREATE (E=ENABLED, D=DISABLED):__ (This parameter specifies what the default write through will be on a file created through a BASIC file create or through the CREATE utility.) UPDATE DISK WITH INSTALLATION PARAMETERS? (Y/N) __ Display: INSTALLATION PARAMETERS SUCCESSFULLY WRITTEN TO DISK. (CR) TO CONTINUE: Repeat the steps in option #4 for any additional system disks. If you changed your disk from a 'MASTER' status to a 'BACKUP' status to do the TYPE 3 LOAD functions, change it back to a 'MASTER' status at this point. Reload the system by pressing the LOAD switch. Be sure you are loading from the drive where you wish to restore the operating system files. 7.6.5. RESTORING THE O.S. _________ ___ ____ From a TYPE 2 LOAD, select the SAVERESTORE option. Once in SAVERESTORE, choose OPTION 2 RESTORE FILES FROM TAPE. The screen appears as in figure 7-1. At the prompt for output device, enter a parallel printer So that a listing of the restore operation is produced. This listing can be used to make sure all files were restored correctly. On the next screen, at the prompt, "FILE SPECIFIERS", enter ".". Then enter twice. All system files will be restored to disk. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg051 Once all files are restored to disk, the message "AUTOMATIC COMPARE, CR TO CONTINUE" appears. This automatically rewinds the tape and begins the compare operation. This only occurs when the compare option is selected. When the compare is completed, enter a CTL-IV to return to the "SAVERESTORE" menu. Reload the system and enter a TYPE 1 LOAD. Figure 7-1. SAVERESTORE Screen ______ ____ ___________ ______ -------------------------------------------------------- RESTORE FILES TAPE SET.ID: DRIVE-NUM: REEL-NUM: PRIMARY PREFIX: (FAMILY).NODE. FILE TYPE (D/P/CR=ALL) COMPARE (CR=Y/N) DATE (MM/DD/YY) TIME (HH:MM) OUTPUT DEVICE (CR=VDT) DELETE EXISTING FILES (CR=Y) VERIFY (Y/CR=N) ENTRIES CORRECT (Y/N) -------------------------------------------------------- At this point it is necessary to install the System Serial Number (using GENSSN) on newly formatted disks and DATA disks that you are changing to SYSTEM disks. 7.6.6. INSTALLING THE CONFIGURATION RECORD __________ ___ _____________ ______ It is necessary to install a new configuration record when installing a new system or when upgrading to 8.7A from 8.6 and lower O.S. levels or when changing systems. Until the following procedure is completed, the system will have a minimum configuration. New systems normally already have a configuration record installed. If you have a new system, and you want to verify that the configuration record has been installed, run the CONFIG.MGR utility in a TYPE 1 LOAD. If the configuration record has already been installed, you may skip this section. Enter a TYPE 1 LOAD. Set your prefix to .SYSTEM.CONFIG. Using the SAVERESTORE utility, restore the new configuration record on tape onto your system. Execute the CONFIG.MGR utility. The CONFIG.MGR utility allows the user to update the system configuration record by installing a new configuration file. This utility displays the current and new configuration record. When "Y" is answered to the prompt "Install Configuration:", the new configuration is copied from the file ".SYSTEM.CONFIG.I(serial number)", to the special system SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg052 area on disk. The new configuration takes effect at the next system load. For further details on the use of the CONFIG.MGR utility, see the 8.5D/9.5D Software Announcement #139, or the BOSS/VS Utility User Guide, M5102. The configuration record file name is derived from the system serial number by changing the leading "8" to an "I" and adding the prefix ".SYSTEM.CONFIG.". EXAMPLE: .SYSTEM.CONFIG.I1030114 for SSN 810-30114 This configuration record tape should be saved, in case re-installation should become necessary. Before going to the next step, LOAD the system so the new configuration record will take effect. If you do not load the system, you will have a minimum configuration and the system will be very slow. IF UPGRADE FROM 8.4E OR ABOVE OR A NEW INSTALLATION THEN GO __ _______ ____ ____ __ _____ __ _ ___ ____________ ____ __ TO SECTION 7.8. __ _______ ____ 7.7. CONVERTING FILES __________ _____ If doing tape to disk conversion see section 7.7.1. 7.7.1. TAPE TO DISK CONVERSION ____ __ ____ __________ Mount the first tape to restore, enter the SAVERESTORE utility, and select option #2. A screen as in figure 7-1 will appear. Answer all prompts as in the figure. Make sure that you direct the output to a printer. This will provide you with a "history" of the restore operation. Each file is converted to the new file format as it is restored. The conversion to the new file format will be entirely invisible except for a pause at the completion of restoring a file. This pause, which can last a few seconds to a few hours depending on file size, indicates the file is being converted to the new file format. Occasionally the message "...CONVERTING FILE TO NFS..." will appear as a visual indicator of file conversion. System files from the previous release need not be restored. However, to preserve all system parameters, the .SYSDATA. node must be restored from the backup tapes. Tapes made on releases of 8.4D and below cannot be compared when restored to the new file system. After all files have been restored, reload the system so the SECURITY.DATA file will be converted to the new 9/8.7A format and the terminal definition files will take effect. 7.7.2. DISK TO DISK CONVERSION ____ __ ____ __________ The utility NFSCONVERT is used to convert files from the SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg053 old format to the new file format. The destination disk must be in new file system format as described in section "TYPE3" The source disk must be in the old file system format. When using disk to disk conversion, only one family may be converted per terminal. You cannot start NFSCONVERT on two terminals converting different parts of the same family, however you can convert different families at the same time. As in the tape to disk conversion, the .SYSDATA. node must be converted to preserve system parameters and configurations. 7.7.3. CHECK FILES _____ _____ Once all files have been converted, the DISKANALYZER "VALIDATE ALL FILES" option should be performed on each family. DISKANALYZER can be used in a TYPE II load or a TYPE I load. Once all files have been validated, enter a TYPE I load, (if you have not already done so). 7.7.4. UPDATING THE TERMINAL CONFIGURATION FILE ________ ___ ________ _____________ ____ The terminal configuration file must be updated to the new file system format. This update will allow all other devices to become accessible. The file is updated by entering TERM.CONFIG and choosing the update option. Enter PRIMARY as the file to change. Enter an existing ISDC and display one of the ISDC ports. Enter a MB-IV to exit the update without changing anything. The utility will say that the file has been modified and ask if you want to save it. Respond with YES. Now reload the system to allow the devices to become active. 7.8. UPDATING THE OTHER SLOTS ________ ___ _____ _____ This section will describe how to update the other slots on the disk. Instructions are different for each system type. Using the chart below, you can find the section needed to install the other slots: SYSTEM SECTION ______ _______ 7xxx and 8xxx 7.8.1 9xxx 7.8.2 ADVANCED SERIES 7.8.3 7.8.1. UPDATING SLOTS 2 AND 3 ON 7xxx and 8xxx SYSTEMS ________ _____ _ ___ _ __ ____ ___ ____ _______ NOTE: If question marks (?/?) ever appear for Load Sector 2 at the top of the OSINFO screen, it is necessary to run SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg054 UPDATE.LD for REMIDI. O.S. and WCS slots 2 and 3 are updated by using the UPDATE.OS and UPDATE.WCS utilities in a TYPE 1 LOAD. To run these utilities, you must set your prefix to the .R7Axx.INST. node. 7.8.1.1. UPDATING WCS SLOT TWO (2) ________ ___ ____ ___ ___ REMIDI version BV includes all the micro-diagnostics except MPC and LAN controller micro-diagnostics. It is placed in WCS slot 2 and is used for testing on all 7000/7100 and 8000 Series Systems. !UPDATE.WCS ENTER WCS SLOT (0..3): '2' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE: (choose disk) WCS IMAGE FILE: .R7Axx.DIAG.REMIDI.BV WCS LEVEL OF WCS IMAGE FILE: (level displayed) UPDATING DISK UNIT nn SECTOR xxx WCS UPDATE COMPLETED! 7.8.1.2. UPDATING WCS SLOT THREE (3) ________ ___ ____ _____ ___ 7.8.1.2.1. ON 7000/7100 SYSTEMS AND 8000 SYSTEMS WITH LAN __ _________ _______ ___ ____ _______ ____ ___ REMIDI version BVM contains micro-diagnostics for the LAN and MPC controllers. It is placed in WCS slot 3 on 7000/7100 Series Systems and on 8000 Series Systems with LAN controllers. The utility UPDATE.LD is used to update the Load Directory for Load Sector 2 to toggle between the two versions of REMIDI in WCS slots 2 and 3. The pointers in Load Sector 2 (displayed on the OSINFO screen) determine which diagnostics will run. !UPDATE.WCS ENTER WCS SLOT (0..3): '3' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R7Axx.DIAG.REMIDI.BVM WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE! 7.8.1.2.2. ON 8000 SYSTEMS WITHOUT LAN __ ____ _______ _______ ___ This slot will contain system WCS which is common to both the O.S. and DEMON. !UPDATE.WCS SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg055 ENTER WCS SLOT (0..3): '3' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R7Axx.INST.WCS.B WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 7.8.1.3. UPDATING O.S. SLOT THREE (3) ________ ____ ____ _____ ___ The O.S. slot 3 will contain the O.S. for DEMON on both 7000/7100 and 8000 Series Systems. !UPDATE.OS BOSS/VS Image File Name: .R7Axx.DIAG.DEMON.UV Target OS Slot (0/1/3) : '3' Target WCS Slot (0-3) : '0' Target Drives (0/1/All/Quit): (choose drive) NOTE: A '0' is entered for the WCS slot to associate DEMON's O.S. with the WCS in slot 0. DEMON and the 8.7A O.S. share the same WCS. The system will now display: Update in progress: nn% Image slot directory n/n:n Updates all complete. Using the utility OSINFO, the slots information can be displayed. It should appear as in figure 7-2. Figure 7-2. OPERATING SYSTEM INFORMATION ______ ____ _________ ______ ___________ OPERATING SYSTEM INFORMATION ------------------------------------------------------------------ BOOT LEVEL : X.X.X.X LOAD SECTOR: 0 1 2 3 DISK 0 : 0/0 1/1 0/2 3/3 SERIAL # : XXX-XXXXX ------------------------------------------------------------------ OS NAME OS LEVEL DISK:SLOT WCS LEVEL ------------------------------------------------------------------ R 7A*xx xxxxxx 7.1.x.x 0:0 B x.x.x R 7A*xx xxxxxx 7.1.x.x 0:1 B x.x.x N/A 0:2 REMIDI B x.x.x DEMON 7.1.x.x 0:3 B x.x.x ------------------------------------------------------------------ NOTE: OSINFO on 7000/7100 Series Systems and 8000 Series Systems with LAN will show the additional version of REMIDI in WCS slot 3. The load sector 3 should be 3/0 on these systems. 7.8.2. UPDATING SLOTS 2 AND 3 ON MPx 9xxx SERIES SYSTEMS ________ _____ _ ___ _ __ ___ ____ ______ _______ O.S. and WCS slots 2 and 3 are updated by using the SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg056 UPDATE.OS' and UPDATE.WCS utilities in a TYPE 1 LOAD. To run these utilities, you must set your prefix to the .R7Axx.INST. node. 7.8.2.1. UPDATING WCS SLOT TWO (2) ________ ___ ____ ___ ___ The first section of the 9xxx version of REMIDI will reside in this slot. !UPDATE.WCS ENTER WCS SLOT (0..3): '2' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE: (choose disk) WCS IMAGE FILE: .R7Axx.DIAG.REMIDI.AVA WCS LEVEL OF WCS IMAGE FILE: (level displayed) UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETED! 7.8.2.2. UPDATING WCS SLOT THREE (3) ________ ___ ____ _____ ___ The second section of the 9xxx version of REMIDI will reside in this slot. !UPDATE.WCS ENTER WCS SLOT (0..3): '3' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R7Axx.DIAG.REMIDI.AVC WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE! NOTE: After REMIDI has been installed, Load Sector 2 at the top of the OSINFO screen should reflect an O.S./WCS of 0/2. If 0/2 is not displayed for Load Sector 2, UPDATE.LD must be run to update the Load Directory. 7.8.2.3. UPDATING O.S. SLOT THREE (3) ________ ____ ____ _____ ___ O.S. slot 3 will contain the O.S. for DEMON. !UPDATE.OS BOSS/VS Image File Name: .R7Axx.DIAG.DEMON.UV Target OS Slot (0/1/3) : '3' Target WCS Slot (0-3) : '0' Target Drives (0/1/All/Quit): (choose drive) NOTE: A '0' is entered for the WCS slot to associate DEMON's O.S. with the WCS in slot 0. DEMON and the 10/9/8.7A O.S. share the same WCS. The system will now display: SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg057 Update in progress: nn% Image slot directory n/n:n Updates all complete. If drive 1 is a system disk also, the operating system installation procedure must be repeated for this disk. Using the utility OSINFO, the slots information can be displayed. It should appear as in figure 7-3. Figure 7-3. OPERATING SYSTEM INFORMATION ______ ____ _________ ______ ___________ OPERATING SYSTEM INFORMATION --------------------------------------------------------------- BOOT LEVEL : X.X.X.X LOAD SECTOR: 0 1 2 3 DISK 0 : 0/0 1/1 0/2 3/0 SERIAL # : XXX-XXXXX --------------------------------------------------------------- OS NAME OS LEVEL DISK:SLOT WCS LEVEL --------------------------------------------------------------- R 7A*xx xxxxxx 7.1.x.x 0:0 A x.x.x R 7A*xx xxxxxx 7.1.x.x 0:1 A x.x.x N/A 0:2 REMIDI A x.x.x DEMON 7.1.x.x 0:3 REMIDI A x.x.x --------------------------------------------------------------- 7.8.3. UPDATING SLOTS 2 AND 3 ON ADVANCED SERIES SYSTEMS ________ _____ _ ___ _ __ ________ ______ _______ O.S. and WCS slots 2 and 3 are updated by using the UPDATE.OS and UPDATE.WCS utilities in a TYPE 1 LOAD. To run these utilities, you must set your prefix to the .R7Axx.INST. node. 7.8.3.1. UPDATING WCS SLOT TWO (2) ________ ___ ____ ___ ___ The first section of REMIDI will reside in this slot. !UPDATE.WCS ENTER WCS SLOT (0..3): '2' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE: (choose disk) WCS IMAGE FILE: .R7Axx.DIAG.REMIDI.CVA WCS LEVEL OF WCS IMAGE FILE: (level displayed) UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETED! NOTE: After REMIDI has been installed, Load Sector 2 at the top of the OSINFO screen should reflect an O.S./WCS of 0/2. If 0/2 is not displayed for Load Sector 2, UPDATE.LD must be run to update the Load Directory. 7.8.3.2. UPDATING WCS SLOT THREE (3) ________ ___ ____ _____ ___ The second section of the ADVANCED SERIES version of REMIDI will reside in this slot. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg058 !UPDATE.WCS ENTER WCS SLOT (0..3): '3' AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R7Axx.DIAG.REMIDI.CVC WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 7.8.3.3. UPDATING O.S. SLOT THREE (3) ________ ____ ____ _____ ___ O.S. slot 3 will contain the O.S. for DEMON. !UPDATE.OS BOSS/VS Image File Name: .R7Axx.DIAG.DEMON.UV Target OS Slot (0/1/3) : '3' Target WCS Slot (0-3) : '0' Target Drives (0/1/All/Quit): (choose drive) NOTE: A '0' is entered for the WCS slot to associate DEMON's O.S. with the WCS in slot 0. DEMON and the 10/9/8.7A O.S. share the same WCS. The system will now display: Update in progress: nn% Image slot directory n/n:n Updates all complete. If drive 1 is a system disk also, the operating system installation procedure must be repeated for this disk. Using the utility OSINFO, the slots information can be displayed. It should appear as in figure 7-4. 7.9. CONFIGURING UPD ___________ ___ This section describes how to configure the new (available with 8/9/10.6H) printers: 4225, 4226, 4227 and 4228 printers for system use. Each of of these printers must have a PDF assigned to them to be used on the system. Figure 7-4. OPERATING SYSTEM INFORMATION ______ ____ _________ ______ ___________ OPERATING SYSTEM INFORMATION ---------------------------------------------------------------- BOOT LEVEL : X.X.X.X LOAD SECTOR: 0 1 2 3 DISK 0 : 0/0 1/1 0/2 3/0 SERIAL # : XXX-XXXXX ----------------------------------------------------------------- SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg059 OS NAME OS LEVEL DISK:SLOT WCS LEVEL ----------------------------------------------------------------- R 7A*xx xxxxxx 7.1.x.x 0:0 C x.x.x R 7A*xx xxxxxx 7.1.x.x 0:1 C x.x.x N/A 0:2 REMIDI C x.x.x DEMON 7.1.x.x 0:3 REMIDI C x.x.x ----------------------------------------------------------------- Below are the steps to assigned these PDF's: Step 1) The PDF's and the translation files must be copied into the SYSDATA node. The PDF's are located in the INST node. These files can be copied using the copy command: COPY ().R7Axx.INST.PDF.P42&,().SYSDATA.PDF.P42& COPY ().R7Axx.INST.XLT.X42&,().SYSDATA.XLT.X42& Step 2) Next the printers must be configured to run under UPD. To do this, the utility TERM.CONFIG and the new utility PRCONFIG will be used, in that order. To do this: A) Determine the controller and the line that your printer is connected to. If unknown, then SYSINFO may be used to determine the controller and line number. B) Execute TERM.CONFIG, select the controller and line corresponding to the printer and configure the printer as UPD SERIAL. Set all other parameters as they would normally be set. C) Repeat step 2 for every UPD printer to be configured. The system must now be rebooted for the changes to take effect. Step 3) Execute the PRCONFIG utility, select the printer to be configured and fill in the remaining parameters: 1) The PDF name will usually be the letter "P" followed by the model number, e.g. P4225. Currently only two PDFS exist; use P4225 for the PT-4225 and PT-4226 printers. Use the P4227 for the PT-4227 and the PT-4228 printers. 2) The translation name will usually be the letter "X" followed by the model number, e.g. X4225. Currently there is only one translation file, X4225. This translation file is used for all UPD printers. 3) Multi-buffering should be selected for printers running 600 LPM or faster. Multi-buffering consumes extra memory and will not boost performance of slower printers. 4) Enter 30 seconds for the read and write timeouts values. These values can be changed later if SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg060 necessary. 5) The model number field is for informational purposes only and doesn't effect the functionality or usage of printer. Enter YES to the entries correct prompt if all entries are correct. Repeat step 3 for all UPD printers to be configured. (4225, 4226, 4227 and 4228 ) 7.9.1. Comments on UPD ________ __ ___ The PRCONFIG utility will build a file called PRINTERS.CONF in the SYSDATA node. It is built using the device name (e.g. P2) and the unit address (e.g. 2.4). The data in the PRINTERS.CONF file must agree with the data in the terminal definition files TERMINALS.DEFNx (maintained by TERM.CONFIG). At system load, one of four conditions can occur: 1) No entry for a particular unit address exists in PRINTERS.CONF but one does exist in TERMINALS.DEFNx. One is therefore created with standard printer driver defaults and entered into PRINTERS.CONF. 2) An entry for a particular unit address does exist in PRINTERS.CONF but one does not exist in TERMINALS.DEFNx. The entry in PRINTERS.CONF is removed. 3) An entry for a particular unit address exists in both PRINTERS.CONF and TERMINALS.DEFNx, but the device name differs, i.e. PRINTERS.CONF believes unit 4.3 corresponds to device P3, but TERMINALS.DEFNx has determined that it is really P2. The entry in PRINTERS.CONF is changed to P2, but all other configuration data remains unchanged. 4) An entry for a particular unit address exists in both PRINTERS.CONF and TERMINALS.DEFNx and the device names agree. In this case, everything is configured properly. A user built PDF requires a software key be installed for proper operation. 7.10. SYSTEM STARTUP ______ _______ 7.10.1. STANDARD STARTUP COMMAND FILE ________ _______ _______ ____ The commands for the standard System Startup Command File are released in the file: .R7Axx.SYS.START.CMD The standard commands are: SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg061 !MAGNET.STARTUP !GROUP.CREATE SPOOLER,TYPE=SYSTEM !SPOOL P*,VERIFY=F,PAUSE=F !GROUP.ENABLE TERMINALS,VERIFY=F,PAUSE=F The name of the System Startup Command File actually used for startup is: (system-default-family).SYSDATA.START.CMD Part of 10/9/8.7A BOSS/VS system installation is to copy the released file to the .SYSDATA. node and make changes and additions as necessary. Note that the commands and parameters in this file must match the commands and parameters defined in the CLI command and function definition files for the individual system being installed. If the System Startup Command File is not found after a system load, then a default initialization is performed. This puts all printers into spooled mode and enables terminals. The following outlines the commands, some of the implications and details of the System Startup Command File method of system configuration. 7.10.2. COMMAND FILE DEFINITIONS _______ ____ ___________ MAGNET.STARTUP This command runs a released MAGNET program that does all of the startup operations required by the MAGNET subsystem. This command should be deleted if MAGNET is not part of the system configuration. GROUP.CREATE SPOOLER,TYPE=SYSTEM This command creates the SPOOLER Group that maintains the activity log files and Group statistics for the spooler subsystem. This command should come before the 'SPOOL P*' command. SPOOL P*,VERIFY=F,PAUSE=F This command puts all of the printers into spooled mode, and causes any eligible requests on the spooled printers to start printing. GROUP.ENABLE TERMINALS,VERIFY=F,PAUSE=F This command enables the 'built-in' TERMINALS Group, and allows all users to logon to any terminals. This command is provided to allow the terminals to be enabled under user control. See below. NOTE: IF A SYSTEM STARTUP COMMAND FILE EXISTS, THIS COMMAND, OR SOME OTHER COMMAND TO ENABLE TERMINAL GROUPS, MUST BE IN THE SYSTEM STARTUP COMMAND FILE FOR USERS TO LOGON TO THE SYSTEM. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg062 In case the TERMINALS Group is disabled, a user with 'system operator' status can enable this group when attempting to logon to the system. This allows an operator to logon to the system in case the Startup Command File did not enable the TERMINALS Group, or the TERMINALS Group was left disabled by accident and all operators signed off the system. To enable the TERMINALS Group during logon the operator attempts to logon and ignores the 'Logon disabled' error messages and enters a 'CR' to continue. A prompt is displayed asking the operator if he wants to enable the TERMINALS Group. NOTE: THIS OPTION IS NOT AVAILABLE IF SOME OTHER TERMINAL TYPE GROUP IS ENABLED. ALSO, ONLY THE TERMINALS GROUP IS ENABLED, AND IT IS NOT CREATED IF IT DOES NOT EXIST. 7.10.3. IMPLICATIONS ____________ 1) Normal system startup is automatic. The system configuration options defined when the system was installed (placed into the System Startup Command File) are put into effect each time the system is loaded, with no further action by the user. These startup options may be modified by the user at any time, by editing the System Startup Command File. 2) Startup sequence is under user control. Users now have the ability to control the sequence of events at startup, after the internal startup sequence is complete. Users that do not need this level of control may ignore this feature. Some users may wish to run specific programs, and do recovery operations, before MAGNET and/or the SPOOLER are started up. This ability would be impossible if these subsystems were always started by the internal system initialization. 3) System recovery is possible before all users logon. This approach allows the operator to allow only specified terminals/users to logon after a system load. The System Startup Command File containing the single command: GROUP.CREATE , TYPE=TERMINAL, USERS=SYS.MGR, DEVICES=T0 would allow only the user 'SYS.MGR' to logon to terminal 'T0' after the system load. No other users could logon, and no other activity would start. In this case the printers will be in suspended mode and MAGNET will not be initialized. When the system operator is finished with the recovery operations the 'normal' system configuration command file may be run by the operator to begin normal system processing. Again, users who do not need this level of control may ignore this feature. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg063 4) Default startup with no System Startup Command File. When the TYPE 1 LOAD is complete, if the System Startup Command File is not found then 'default' startup conditions are in effect. In this case the system is available for any use. This mode is intended to support systems that want only these default startup options. The 'built-in' TERMINALS Group is enabled and allows all users to logon to any terminal. A system group named SPOOLER is created and the printers are put into spooled mode. The MAGNET subsystem is not activated. The following is a description of the details of the System Startup Job: When a TYPE 1 LOAD is performed, the last module to be initialized is the Job Manager (JMM). The final act of JMM is to run a batch job with a CLI command file. The files involved are: (system-default-family).SYSDATA.START.CMD (system-default- family).SYSDATA.START.IN (system-default- family).SYSDATA.START.OUT SYSDATA.START.CMD is a sequential file that contains all of the startup commands; this is the System Startup Command File. The Job Manager looks in the system default family (only) for this file. SYSDATA.START.IN is a sequential file that contains any data that may be input by commands and programs in the above startup file. A read from standard INPUT will read records from this file. The Job Manager looks in the system default family (only) for this file. SYSDATA.START.OUT is a sequential file that contains the results of the startup command file. A write to standard OUTPUT by commands and programs will be placed into this file. The Job Manager deletes this file in the system family if it exists, prior to running the startup command file. If the startup file (system-default-family).SYSDATA.START.CMD - or - (system-default-family).SYSDATA.START.CMD.TEXT is not found, the Job Manager will perform a default startup described above. If the startup file (system-default-family).SYSDATA.START.IN - or - (system-default-family).SYSDATA.START.IN.TEXT is not found, the Job Manager will attach a null file to SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg064 startup INPUT; an End-Of-File will be returned for each read from standard INPUT. NOTE: THE SYSTEM STARTUP COMMAND FILE CONTAINS (ONLY) STANDARD CLI COMMANDS. A CLI command may be: 1) A CLI Command or Function (START, PREFIX, $WHERE, etc.) 2) A system utility (DIR, COPY, etc.) 3) The name of a program to run. 4) The name of another CLI command file. 7.11. DIAGNOSTIC REMOVAL __________ _______ This section describes the removal of diagnostic programs from a system. The diagnostics reside in the file system and several bootable disk slots. They are removed from the file system with the 'delete' utility. They are removed from the bootable slots by overwriting the images. The procedure follows. 1. Removing REMIDI The removal of REMIDI is accomplished by overwriting the two bootable REMIDI slots with the WCS image. 2. Update WCS Slot 2 Execute the UPDATE.WCS utility and respond to the prompts as shown below. ENTER WCS SLOT (0..3): - 2 AVAILABLE DISK UNITS ARE: - (displayed) DISK TO UPDATE : - Enter the disk number. WCS IMAGE FILE: - .R7Axx.INST.WCS.X (where X = A,B,C) X = A for MPx 9xxx X = B for MPx 7xxx, 8xxx X = C for Advanced Series WCS LEVEL OF WCS IMAGE FILE: - (displayed) During the update process, the following message appears: UPDATING DISK UNIT nn SECTOR xx When the update is complete, the following message appears: WCS UPDATE COMPLETED! The preceding should be performed on all system disks. 3. Update WCS Slot 3 Execute the UPDATE.WCS utility and respond to the prompts as shown below. ENTER WCS SLOT (0..3): - 3 AVAILABLE DISK UNITS ARE: - (displayed) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg065 DISK TO UPDATE : - Enter the disk number. WCS IMAGE FILE: - .R7Axx.INST.WCS.X (where X = A,B,C) X = A for MPx 9xxx X = B for MPx 7xxx, 8xxx X = C for Advanced Series WCS LEVEL OF WCS IMAGE FILE: - (displayed) During the update process, the following message appears: UPDATING DISK UNIT nn SECTOR xx When the update is complete, the following message appears: WCS UPDATE COMPLETED! The preceding should be performed on all system disks. 4. Removing DEMON The removal of DEMON is accomplished by overwriting the bootable DEMON slot with DEMON.UX. 5. Update OS Slot 3 Execute the UPDATE.OS utility and respond to the prompts as shown below. BOSS/VS Image File Name: - DEMON.UX Target OS Slot (0/1/3): - 3 Target WCS Slot (0-3): - 0 Target Drives (0/1/All/Quit): - Enter the disk number During the update process, the following message appears: Update in progress : x/y : zz% When the update is complete, the following message appears: Updates all complete. The preceding should be performed on all system disks. 6. Removing diagnostics from the file system The diagnostics are removed from the file system using the 'delete' utility. The diagnostics are found in the system node .R7Axx.DIAG. The files in the following nodes should be deleted from the file system. .R7Axx.DIAG. .ENHANCER7A. .TRACKER. The following files should be deleted: .AC (MPX 9000 series 1/4" tape boot OS image with DIVE) .AT (MPx 9000 series 1/2" tape boot OS image with DIVE) .BC (MPx 7000 series 1/4" tape boot OS image with DIVE) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg066 .BT (MPx 8000 series 1/2" tape boot OS image with DIVE) .CC (Advanced Series 1/4" tape boot OS image with DIVE) .CT (Advanced Series 1/2" tape boot OS image with DIVE) The following file(s) should be added as a replacement for the file(s) deleted above. .ACX (MPx 9000 series 1/4" tape boot OS image without DIVE) .ATX (MPx 9000 series 1/2" tape boot OS image without DIVE) .BCX (MPx 7000 series 1/4" tape boot OS image without DIVE) .BTX (MPx 8000 series 1/2" tape boot OS image without DIVE) .CCX (Advanced Series 1/4" tape boot OS image without DIVE) .CTX (Advanced Series 1/2" tape boot OS image without DIVE) This completes the diagnostic removal procedure! 8. RELATED DOCUMENTATION _______ _____________ 2770/2780/3770/3780 Batch Emulator User Guide M5080C 3270 Pass-Through Reference Manual M5091A Business BASIC 90 Reference Manual M6262D BOSS/VS User Guide M5098H BOSS/VS Utilities User Guide M5102M 3270 Emulation Package Operator Guide for MAI 8000 Series M5129 File Transfer Facility User Reference Manual M6352A BOSS/VS Installation Guide M5138L System Site Planning Guide M0174A BOSS/VS Special Purpose Utilities User Guide M5151 BOSS/VS System Support Manual M5152 Intersystem Transport Package User Guide M6354F MAI 8000 Series COBOL Reference Manual M5174 MAI 8000 Series COBOL User Guide M5175 BOSS/VS File Conversion User Guide M5185A MAGNET/VS User Reference Manual M6363 BOSS/VS 3270 BSC Emulation User Reference Manual M0170A ORIGINATOR: MBF SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB092 Pg067 FIB 00093 01/27/92 *** HCC On-Line Backup Utility *** On Line HCC Backup Processing Documentation THIS UNSUPORTED SOFTWARE CANNOT PROTECT AGAINST ITS SOURCE DISK FROM BEING MODIFIED AS IT IS BEING BACKED UP. UPDATES TO FILES CAN OCCUR FROM NORMAL USER TASKS WHILE THE IMAGE COPY IS IN PROGRESS. IT IS UP TO THE USER TO INSURE THAT THIS DOES NOT HAPPEN. MBF DOES NOT GARANTEE FILE INTEGRITY IF FILES ARE BEING MODIFIED AT THE SAME TIME THAT THE FAMILY IS BEING BACKED UP. THIS UNSUPPORTED SOFTWARE HAS NOT BEEN CERTIFIED ON ALL HARDWARE CONFIGURATIONS. IF YOU HAVE PROBLEMS WHILE USING THIS SOFTWARE IT WILL BE THE USER'S RESPONSIBILITY TO MODIFY THESE PROGRAMS. THIS UNSUPPORTED SOFTWARE MUST BE RUN ON A VDT 4309 OR HIGHER. =============================================================================== The following is documentation for the HCC backup processing. It is suggested to create a seperate operator logon that sets the prefix and automatically runs the HCC menu program (PSMU01). Before performing the HCC backup process, it is recommended to always verify that the HCC tape unit has been turned on and is on-line and that the specified printer (if any) has been turned on and is on-line. Also if File Security is set to true system wide, then to run this unsupported software the user must have File Security Override set to true. The HCC backup processing menu has three options. They are as follows: 1) HCC Backup Data Entry and Processing 2) HCC Backup Processing (Do Not Use) 3) HCC Backup Processing Serial File Hardcopy The first option is a data entry screen (PSDE01) which is required to be completed before the backup processing can take place. The information needed to be input and the descriptions of the items are as follows: 1) Tape Unit Number - This is the tape drive number that the backup processing will open to the HCC tape drive. It MUST be the correct tape unit drive number. 2) Tape Set Name - This is the set name which will be written to the label of the HCC tape before the actual backup processing begins. 3) Tape ID Name - This is the identification name which will be written to the label of the HCC tape before the actual backup processing begins. 4) Compare Y/N - This field, if 'Y' is entered, will allow an automatic compare to take place after the backup processing is completed. If 'N' is entered, no compare will take place. It is recommended to always set this parameter to 'Y'. 5) Password - This is where the system password is SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB093 Pg001 entered. This will be checked before beginning the backup processing. The backup processing will not begin without a correct password. 6) Family Name - The terminal will display the families to be to be backed up . Enter a M.B. IV to modify this display or enter 'CR' to accept this display. While modifying families you can add 16 families but it will be up to the user to make sure that the total capacity (MBYT) does not exceed the capacity of the HCC tape. Also when entering families the system will check to see if this family is mounted on the system. It also will not accept duplicate families to be backed up (Enter a family more than once). You can use CTRL C to help you modify a family name. ** Note : The Family Name fields must be used in order. (ie. If three families are to be backed up, then these family names would be entered in the family name 1,2 and 3 fields, and Family Name 4 would be left blank after this blank field the system will ignore the rest of the family fields. 10) Start Date - This is the date that will be compared to the system date to determine when the backup will automatically begin. The system date will be displayed while accessing this field for your convenience. This date will be in MM/DD/YYYY format. Entry of the century is not necessary. If the date entered in this field is equal or prior to the the system date, the backup processing will wait until the Start Time parameter (covered in the following paragraph) is met. If the date entered in this field is in the future, the system will wait until this date is met. 11) Start Time - This is the time that will be compared to the system time to determine when the backup will automatically begin. The system time will be displayed while accessing this field for your convenience. This field can be entered in 24 hour format and will be converted and displayed in standard time. It can also be entered in standard time format. If 'A' for 'AM' or 'P' for 'PM' is not specified, 'AM' will be defaulted. The system will NOT begin checking the time parameter against the system time until the Start Date parameter has been met. The time parameter must match the system time exactly before the backup processing will begin. ** Note : Do to rounding in the calculation process of time, the time entered may lose or gain one minute. It is recommended to enter a start time on either an hour or half an hour. 12) Printer Name - This is the printer where the output of the backup will be sent. This MUST be a valid printer and this printer MUST be on-line. The backup processing will automatically RESERVE this device so it will not create a spool file and miss compare. The backup processing will automatically update the printer back to SPOOL mode during the completion of the backup processing. 13) Output File Name - This is a serial file where the output of the backup will be sent. This field will override the Printer Name field above. If this field is used, then output will be sent to the file name specified. If this field is left blank, then output will be sent to the printer name specified, described above. ** Note : This file most likely will be miscompared (If compare option is used) due to live procesing. This will also cause the :DIR and AVSP files to also miscompare. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB093 Pg002 14) Ghost ID - This is the name of the ghost task that will be automatically started during the backup processing. It MUST be in Gnn format. 15) Stand Alone Mode - This field, if 'Y' is entered, will automatically release all terminals that are logged on to the system before starting the backup processing. Also, the group TERMINALS will be disabled to prevent users from logging into the system during the backup processing. If 'N' is entered, any users logged onto the system will not be released. After filling out the above information, a prompt 'IS THE ABOVE DATA CORRECT (Y-N-END):' is displayed. If 'Y' is entered, the above information is saved and the HCC backup processing program (PSBU01) is run. This program take the information entered in the data entry program and performs the actual backup. ERROR REPORTING 1. Soft errors are not reported to the HCC routine but are reported in the ERRORLOG. A soft error will be the one that is displayed in the ERRORLOG as NORMAL Read. A NORMAL read error is one that failed the MULTI sector read (first pass), then dropped into the 'Single Sector' read but did not have any errors for the sectors that were in the Normal Read. 2. Hard errors are reported to the HCC routine (Software will do two retries and skip the sector and continue) and are also in the ERRORLOG. They will be the ones that are reported as Normal Read, Retry Read, Retry Read. It failed the Normal Read (multi sectors) then dropped into the single sector read (Retry Read), then hit a sector that was bad and failed (Retry Read). 3. You will have compare errors if files where being modified at the time the system was backing up these files (Compare errors will only be displayed if you select the option of COMPARE="Y"). It will be up to the user to determind what files have been modified (By using the information provided by the HCC routine you can go into the !DKA utility and select option 7 ( LIST FILES IN A SECTOR RANGE). Some files that might show up as being miscompared are : DIR, AVSP, OVERLAY and ERRORLOG (if you had soft/hard errors). Also if you select a file for output this might show up as being miscompared. You can ignore these files since you are backing up a "LIVE" system and this utility was originally made for a T3LD. Anything else that shows up as being miscompared (user's files) is up to the user to determind if he has a valid backup. In case of a power failure the HCC routine is not garanteed because the BMTC does not have the power fail capability as does memory. You will know if you have a GOOD backup if at the end of the HCC routine your final page (printout/file) has a box that displays all families backup. It should display the following : ------------------------------------------------------------------------- FAMNAME OPERATION STATUS TOTAL INCIDENTS ------------------------------------------------------------------------- FAMNAME = Families backed up OPERATION = Should always say BACKUP STATUS = DONE means backup completed (but you might have had a soft/ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB093 Pg003 hard or a miscompare error). If TOTAL INCIDENTS is 0 there were no problems encountered during this backup. = DISK ERROR means HARD/SOFT error encountered. *NOTE* If you have any HARD errors reported by the HCC routine you should have Customer Service representative check the family and ROT (if necessary) the sectors that have these HARD errors. TOTAL INCIDENTS = should match the number of HARD/SOFT and COMPARE errors that is in the printout/file. Reported by the HCC routine. At the end of this box it should display the START TIME and END TIME of the BACKUP. If you do not get this box or if this box is incomplete (missing families) you do not have a GOOD backup. ORIGINATOR: MBF SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB093 Pg004 FIB 00094 MAI COMPANY CONFIDENTIAL 06/17/92 *** Patch 55 - Spooler/Enhancer Patches available for R7A *** *************************PRELIMINARY FIELD BULLETIN********************** Subject: MPx - Patch 55 Author Date Combines Patches & Fixes Spooler Bugs Jean Keller 5/29/92 Type: Problem Purpose: This field bulletin is to inform the field about the availability of Patch 55. Symptom: Several patches needed to be combined for distribution and some SPOOLER bugs needed fixing. Solution: Patch 55 has been released and should be installed on all systems as required. The following patches are included. Patch 50 SECURITY The utility will run correctly when there are more than 409 devices configured on the system. Patch 51 DISKMONITOR .ENHANCER7A. program. Recompiled for M7A release. Now will execute. Patch 54 TERM .ENHANCER7A. program. Recompiled for M7A release. Now will execute. Requires a security key. The following new .ENHANCER7A. tools are included: RSMMON Captures magnet traffic between systems and logs it to a user-specified output file. RSMCLOSEMON Terminates magnet traffic logging to a file. RSMTERM Captures magnet traffic between systems and logs it to a user-specified terminal. RSMCLOSETERM Terminates magnet traffic logging to a terminal. The following fixes are included: IFR fix Multiple files from a user-specified file list may now be restored from a tape image backup. HCC fix program .ENHANCER7A.PSBU01. Accessed from HCC unattended backup program menu .ENHANCER7A.PSMU01. Fixed "Aborted backup due to invalid ghost communications" problem. SPOOLER fixes. Requires a revised OS. 1) VFU was not loaded correctly if jobs were queued up before a SETFORM was done. (EX: A form specifying 33 lines would print 33 lines of a file per page, but the page would be the length of the previous form, for example 66 lines.) 2) Slewing in 8 lpi mode caused printing to be 1/2 line off. Documentation: A description of the fixes and the installation instructions are included on hard copy with the tape. They are also on .PATCH55.README file on the tape. Installation: Provided with the patch tape and README file as follows: The tape containes files which will restore/replace programs in the node .ENHANCER7A. and .R7A42. The new OS will restore as .PATCH55.OSN.UV and the READEME file as .PATCH55.README. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB094 Pg001 Execute !SYSPREFIX to determine the default system family name. Restore the tape using !SAVERESTORE, Option 2, specifying: Delete existing files = Y file specifiers: >.,(xxx). where xxx is the system family name. To install and use the updated version of the OS: Execute !OSINFO to display the current settings of the system disks. Execute !UPDATE.OS, specifying the image file name .PATCH55.OSN.UV and the OS and WCS slots and the disk(s) you wish to update. Note: Remember, you cannot update the OS slot from which the system was loaded (indicated in OSINFO by highlighted text.) Execute !OSINFO to display the current settings of the system disks. The new OS will display as: SPOOLER PATCHER 7.1.42.2 Reboot the system, setting the load and devices switches as necessary to load the new OS. Execute !OSINFO to verify the system has been loaded from the new OS (It should be highlighted on the display). Patch 55 should be ordered through software distribution. ORIGINATOR: Jean Keller SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB094 Pg002 FIB 00095 MAI COMPANY CONFIDENTIAL 09/11/92 *** Error 503's on Advanced Series Systems *** TYPE : Problem PURPOSE: This field bulletin is to inform the field of a problem found on Advanced Series systems while running a BASIC application. SYMPTOM: An ERROR 503 with an 'INTERNAL BASIC ERROR -- ENTER PCDUMP OR PRESS RETURN' error is generated when accessing a element in a numeric array that does not exist. after this error, the task will drop out of BASIC and into command mode or the task will be released. If 'PCDUMP' is entered at the prompt, the top of the output will look similar to the following : PC SEGMENT NAME PROC NAME OFFSET == ======= ==== ==== ==== ====== -1 * KERNEL [1] ( 73) PEINSTRF 240 -2 BB EDIT CODE ( 2) 107 -3 (DISK).R7B02.SYS.BASIC.RT ( 11) RUN 80 -4 (DISK).R7B02.SYS.BASIC.RT ( 4) DISPATCH 285 -5 (DISK).R7B02.SYS.BASIC.RT ( 1) BASIC 23 A very simple example program to generate this problem would be : >DIM A(1) >X=A(36) CAUSE: This is a problem with WCS (firmware) for the Advanced Series Systems. An ERROR 42 should be returned but it is not. This problem is only seen on the Advanced Series. SOLUTION: The solution is to modify applications so that they do not reference a non-existent element of a dimensioned numeric array. There are no plans to make any changes to the firmware for the Advanced Series Systems. ORIGINATOR: Dale Jensen SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB095 Pg001 FIB 00096 MAI COMPANY CONFIDENTIAL 07/19/94 *** Release N.7 BROADCAST and read timeout problem [ WPSF 799M ] *** PURPOSE: To inform the field on how to correct a problem on the BOSS/VS 8/9/10.7 A and B release when using the BROADCAST utility. This also corrects a problem where spurious ERROR 0 READ TIMEOUTs occur. SYMPTOM: Terminals will not display BROADCASTed messages and will display garbage characters on the terminal. BASIC tasks give spurious ERROR 0 READ TIMEOUTs. SOLUTION: The attached program will automatically modify all terminal ports on the MPx/AS system. After running the program you MUST reboot the system for the changes to take effect. Enter the following program: 10 REM "To correct BOSS/VS 8/9/10.7 0/5 BROADCAST problems" 20 BEGIN; PRINT `CS' 30 OPEN(l) ".SYSDATA.TERMINALS.DEFN1";LOCK(1) 40 FORI=0 TO 64 50 READRECORD (1,IND=I)A$ 60 FOR Z=l TO LEN (A$) STEP 32 70 IF HTA(A$(Z,1))="05" GOTO 80 ELSE GOTO 130 80 L1=Z+l6 90 PRINT "CURRENT TIME VALUE IS:",DEC(A$(L1,1)) 100 V=80 110 A$(L1,1)=BIN(V,l) 120 WRITERECORD (1,IND=I)A$ 130 NEXT Z 140 NEXT I 150 END After running the above program you MUST reboot the system for the changes to take effect. This Field Bulletin supersedes the information that is in Field Bulletin 764, Pages 16 and 17 (BROADCAST problems on BOSS/VS 8/9/10.7 O/S release). This program will have to be rerun if ports are added or if major changes are made to a port configuration (terminal-to-printer, printer-to-terminal). ORIGINATOR: Joe Melendez MODIFIED by: Norm Jones SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB096 Pg001 FIB 00097 MAI COMPANY CONFIDENTIAL 01/15/93 *** Program to convert ERRLOG dump numbers to four-tuple on 8.4 OS *** This FIB is being issued since there are still MPx systems running on 8.4 OS levels. On 8.4 levels the ERRORLOG dump option displays a nine digit number for. the dump rather than the four-tuple, the following program will convert this number to the four-tuple. 0005 REM "CONVERT ERRLOG DUMP NUMBER TO FOUR-TUPLE FOR 8.4 OS" 0010 INPUT "ENTER DUMP NUMBER FROM ERRORLOG - ",X 0020 X$=BIN(X,4) 0030 X1$=$00$+X$(1,1) 0040 X2$=$00$+X$(2,1) 0050 X3$=$00$+X$(3,1) 0060 X4$=$00$+X$(4,1) 0065 PRINT "THE FOUR-TUPLE ERR NUMBER FOR - ",X," IS - ", 0070 PRINT DEC(X1$),",",DEC(X2$),",",DEC(X3$),",",DEC(X4$) 0080 GOTO 10 ORIGINATOR: Norm Jones SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB097 Pg001 FIB 00098 MAI COMPANY CONFIDENTIAL 01/26/93 *** Installing keys for ALB (Auditor's LogBook) & OLB (OnLine Backup) *** Online Backup is available with n.7A OS. It is implemented in SAVERESTORE as interactive (menu) and in COPY as either interactive or command-line mode. In interactive mode (menu) there is a prompt for ONLINE BACKUP. When copying files. in command-line mode the keyword is ONLINEBACKUP (=TRUE or =FALSE). The AUDITOR'S LOGBOOK provides automatic logging of the access history for selected files. The procedure to install the public keys for Auditor's Logbook or Online Backup is as follows: 1) Copy the product file from the .INST. node to ().ETC.LEVEL. ex. for Online Backup: !COPY (DISK).R7B01.INST.ETC.LEVEL.OLB (DISK).ETC.LEVEL.OLB 2) Edit the product file and enter your key after the colon on the line listed as Public id: ex. for Online Backup: !EDIT (DISK).ETC.LEVEL.OLB SAMPLE OLB FILE 1. Creation date:08/25/89 2. Install date: 3. Release number:1.0 4. Public id length:8 5. Public id:12345678 6. Product dependencies: none 7. Minimum OS level:6.7.43.0 8. Short description: Online Backup 9. Installation procedure file: 10. Ignore path name: 3) Reboot the system ORIGINATOR: Norm Jones SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB098 Pg001 FIB 00099 MAI COMPANY CONFIDENTIAL 10/29/93 *** Release 8/9/10.7B Software Announcement *** MAI Systems Corporation is pleased to announce that the new system software revisions, 8/9/10.7B, are now available. The 9.7B revision is the recommended revision for MPx 9xxx Series Systems. The 8.7B revision is the recommended revision for MPx 7xxx and 8xxx Series Systems. The 10.7B revision is the recommended revision for Advanced Series Systems. This release adds support for the 1.6GB disk drives. o This release includes the fixes in Patch 55. Note: Patch 55 combined Patch 50, 51, and 54, and contained fixes to the some of the problems described in Notes and Special Considerations for BOSS/VS Levels 10/9/8.7A. Specifics are noted in the section describing the Fixes in this document. Please be aware that the problems described in Notes and Special Considerations apply to M7B. If you made any program modifications to .R7Axx. system files to work-around a problem, you must make those same modifications to the .R7Bxx. system files. A new configuration record is required when upgrading to 8/9/10.7B from levels BELOW 8/9/10.7A but not from level 8/9/10.7A. If this release is installed on MPx 9x00 systems containing DMA-II controllers, then version -002 of the DMA-II boards must be used. If the system contains - 001 boards, please contact your hardware support for local board replacement procedures. Please refer to the HARDWARE Section #6. o As of release 8/9.6C, the .SYSDATA.SECURITY.DATA file is not transportable to previous release levels. Therefore, if you are upgrading to 8/9/10.7B from a release prior to 8/9.6C, this file should be saved before the upgrade, for fall-back purposes. o Files transferred from 8/9/10.7B to O.S. levels below 8/9.6A must be transported with EXTTAPE, MCSI, FTF, TBC, or ATP. If a downgrade is performed from 10/9/8.7B to a release prior to 8/9.6C, the user's files must be transported to the older O.S. level with one of the above utilities. o Programs written or modified on 8/9/10.7B which are transferred to a release prior to 8/9/10.7A must be transported with EXTTAPE, MCSI, FTF, TBC, or ATP. An alternate method would be to convert the basic program to a serial file on 8/9/10.7B and then transfer it to a prior release. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg001 o Horizontal software such as PRESENTATION SERVICES, GRAPH, and ORIGIN typically have files that reside in the .SYS. node. These files need to be transferred to the new .SYS. node on an O.S. upgrade, either by using the COPY utility or by re-installing the software. o The 8/9/10.7B Software Announcement exists as a serial file on the official release tape. To print a copy, submit the following file to the printer: .R7Bxx.INST.DOC.ANNOUNCE7B. CONTENTS 1 INTRODUCTION ..........................................7 1.1 ENHANCEMENTS IN THIS RELEASE ...................7 1.1.1 Support for the 1.6GB disk drive .........7 1.1.1.1 FAMILY UTILITY ....................7 1.1.1.2 Type 3 Load .......................7 1.1.1.3 HCC Unattended Backup .............7 1.1.2 Thumbprint check for all SCSI disks removed. .......................................7 1.1.3 Diagnostics ..............................7 1.1.3.1 DEMON .............................7 1.1.3.2 DIVE ..............................7 1.1.4 Networks/Gateway .........................7 1.1.4.1 Standard gateway ..................8 2 FIXES IN THIS RELEASE .................................8 2.1 SECURITY Utility ...............................8 2.2 DISKMONITOR (ENHANCER7B.) .....................8 2.3 TERM (.ENHANCER7B.) ...........................8 2.4 MAGNET LOGGING (.ENHANCER7B.) .................8 2.4.1 RSMON ....................................8 2.4.2 RSMCLOSEMON ..............................8 2.4.3 RSMTERM ..................................9 2.4.4 RSMCLOSETERM .............................9 2.5 RFS Remote prefix (System Command) ..............9 2.6 IFR Utility .....................................9 2.7 Unattended Image T3LD On-line Backup (HCC) .....9 2.8 Spooler/Printer Fixes (OS) ......................10 2.8.1 VFU Load Fix .............................10 2.8.2 Will slew correctly in 8 lpi mode. .......10 3 CONFIGURATIONS .........................................10 3.1 CONFIGURATIONS FOR MPX 7000/7100/8000 SERIES SYSTEMS .............................................10 3.2 CONFIGURATIONS FOR MPX 9000/9100/9400 SERIES SYSTEMS .............................................11 3.3 CONFIGURATIONS FOR MPX 9500/9600 SERIES SYSTEMS .............................................12 3.4 CONFIGURATIONS FOR THE ADVANCED SERIES FAMILY ...13 4 DIAGNOSTICS ............................................15 4.1 REMIDI ..........................................15 4.1.1 ON MPx 7000, 7100, AND 8000 SERIES SYSTEMS ........................................15 4.2 DEMON - UPDATING THE LOAD DIRECTORY .............18 4.3 ADVANCED SERIES ONLY ............................19 4.3.1 HIGH FREQUENCY MARGINS ON THE ADVANCED SERIES .........................................19 4.3.2 USING ALT LOAD FOR REMIDI AND DEMON ......19 4.4 DIAGNOSTIC REMOVAL ..............................20 5 HARDWARE ...............................................22 5.1 MPX 7000, 7100, AND 8000 PCBA NOTES .............22 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg002 5.2 MPX 9XXX SERIES SYSTEM PCBA NOTES ...............25 5.3 PCBA'S FOR ALL MPX 7/8/9XXX SERIES SYSTEMS ......30 5.4 ADVANCED SERIES PCBA NOTES ......................31 5.5 PCBA'S NOT SUPPORTED ON ADVANCED SERIES .........35 5.6 PERIPHERAL DEPENDENCIES .........................35 5.6.1 GCR TAPE DRIVE ...........................35 5.6.2 SCSI MTCS TAPE DRIVE .....................35 5.6.3 HIGH CAPACITY CARTRIDGE (HCC) TAPE DRIVE ..........................................36 5.6.4 TERMINALS ................................36 5.6.5 DISK DRIVES ..............................36 5.7 HARDWARE FLOW CONTROL ...........................37 6 INSTALLATION ...........................................38 6.1 GENERAL INFORMATION .............................38 6.2 NEW OPERATING SYSTEM INSTALLATION ...............43 6.3 UPGRADING TO 9.7B ...............................43 6.3.1 PRINTING OUT THE TERMINAL CONFIGURATION INFORMATION ....................................44 6.3.2 SAVING FILES TO TAPE .....................44 6.4 UPGRADING FROM RELEASE LEVELS 8.4D AND BELOW ....45 6.4.1 HARDWARE EVALUATION ......................46 6.4.2 FILE PREPARATION .........................46 6.4.3 NEW FILE SYSTEM SPACE REQUIREMENTS .......47 6.4.4 SAVING FILES TO TAPE .....................47 6.5 INSTALLING THE OS - LOADING SLOTS 0 AND 1 USING ALT LOAD ......................................49 6.6 TYPE 3 LOAD (SPECIAL FUNCTIONS) .................51 6.6.1 OPTION 1 (CHANGE VOLUME LABEL INFORMATION) ...................................52 6.6.2 OPTION 2 (UPDATE FAMILY INFORMATION) .....52 6.6.3 OPTION 3 (INITIALIZE FAMILY DIRECTORY) ...53 6.6.4 OPTION 4 (CHANGE INSTALLATION PARAMETERS) ....................................53 6.6.5 RESTORING THE O.S. .......................54 6.6.6 INSTALLING THE CONFIGURATION RECORD ......55 6.7 CONVERTING FILES ................................56 6.7.1 TAPE TO DISK CONVERSION ..................56 6.7.2 DISK TO DISK CONVERSION ..................57 6.7.3 CHECK FILES ..............................57 6.7.4 UPDATING THE TERMINAL CONFIGURATION FILE ...........................................57 6.8 UPDATING THE OTHER SLOTS ........................57 6.8.1 UPDATING SLOTS 2 AND 3 ON 7xxx and 8xxx SYSTEMS ........................................58 6.8.1.1 UPDATING WCS SLOT TWO (2) .........58 6.8.1.2 UPDATING WCS SLOT THREE (3) .......58 6.8.1.2.1 ON 7000/7100 SYSTEMS AND 8000 SYSTEMS WITH LAN ................58 6.8.1.2.2 ON 8000 SYSTEMS WITHOUT LAN ..................................59 6.8.1.3 UPDATING O.S. SLOT THREE (3) ......59 6.8.2 UPDATING SLOTS 2 AND 3 ON MPx 9xxx SERIES SYSTEMS .................................60 6.8.2.1 UPDATING WCS SLOT TWO (2) .........60 6.8.2.2 UPDATING WCS SLOT THREE (3) .......60 6.8.2.3 UPDATING O.S. SLOT THREE (3) ......61 6.8.3 UPDATING SLOTS 2 AND 3 ON ADVANCED SERIES SYSTEMS .................................61 6.8.3.1 UPDATING WCS SLOT TWO (2) .........62 6.8.3.2. UPDATING WCS SLOT THREE (3) .....62 6.8.3.3 UPDATING O.S. SLOT THREE (3) ......63 6.9 CONFIGURING UPD .................................63 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg003 6.9.1 Comments on UPD ..........................65 6.10 SYSTEM STARTUP .................................65 6.10.1 STANDARD STARTUP COMMAND FILE ...........65 6.10.2 COMMAND FILE DEFINITIONS ................66 6.10.3 IMPLICATIONS ............................67 6.11 DIAGNOSTIC REMOVAL .............................69 7 RELATED DOCUMENTATION ..................................72 T A B L E S , F I G U R E S and G R A P H S Figure 7-1. SAVERESTORE Screen . . . . . . . . . . . . . 55 Figure 7-2. OPERATING SYSTEM INFORMATION . . . . . . . . 60 Figure 7-3. OPERATING SYSTEM INFORMATION . . . . . . . . 62 Figure 7-4. OPERATING SYSTEM INFORMATION . . . . . . . . 63 1.1 ENHANCEMENTS IN THIS RELEASE The 10.7B/9.7B/8.7B release contains the following enhancements: 1.1.1 Support for the 1.6GB disk drive 1.1.1.1 FAMILY UTILITY Support for the 1.6GB Disk drive has been added. The utilities will display the drive showing the correct number of sectors used and available. 1.1.1.2 Type 3 Load Support for the 1.6GB disk drive has been added. The display for the drive will reflect the characteristics and size. Copy features for Disk to disk and disk to tape now include provisions for the 1.6GB disk drives. 1.1.1.3 HCC Unattended Backup Support for the 1.6MB disk drive has been added. The utility that is called by the modules through the menu program PSMU01 now includes the provision for the 1.6MB disk drive. 1.1.2 Thumpprint check for all SCSI disks removed The thumbprint check for all SCSI disks has been removed. Now non-thumbprinted drives will not be prohibited. Thumbprinted drives will still be acceptable. 1.1.3 Diagnostics 1.1.3.1 DEMON Some variable and print formats have been expanded to support the 1.6GB drive. 1.1.3.2 DIVE An Appendix to the DIVE User Guide has been added to support the 1.6GB disk drive. Some internal modifications have been made concerning SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg004 invocation of cylinder based on read capacity on certain products, and write size. 1.1.4 Networks/Gateway 1.1.4.1 Standard Gateway The standard gateway process was changed to suppress checking for duplicate X.25 connections. This version of the gateway will only be used in customer sites connected to UNIX hosts via OpenMagnet Gateway and using X.25 to gateway to other subnetworks. 2.1 SECURITY Utility The utility will run correctly when there are more than 409 devices configured on the system. (See Notes & Special Considerations, 1.3.11.1; Patch 50, 55) 2.2 DISKMONITOR (ENHANCER7B.) Recompiled for M7B. Will run correctly, and not release your terminal. (See Notes & Special Considerations, 1.10.3; Patch 51,55). 2.3 TERM (ENHANCER7B.) Recompiled for M7B. Terminal Emulator; requires a securitiy key. (See Notes & Special Considerations, 1.3.20; Patch 54, 55) 2.4 MAGNET LOGGING (ENHANCER7B.) 2.4.1 RSMON New tool on M7A omitted from M7A release.. Captures the MAGNET traffic between systems and logs it to a user- specified output file. (On Patch 55) 2.4.2 RSMCLOSEMON New tool on M7A omitted from M7A release. Terminates the MAGNET traffic logging started by RSMMON. (On Patch 55). 2.4.3 RSMTERM New tool on M7A omitted from M7A release. Captures the MAGNET traffic between systems and logs it to a user- specified terminal. Note: MAGNET performance is significantly degraded when logging is on.) (On Patch 55). SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg005 2.4.4 RSMCLOSETERM New tool on M7A omitted from M7A release. Terminates the MAGNET traffic logging started by RSMTERM. (On Patch 55). 2.5 RFS Remote prefix (System Command) Remote prefix functionality. The server will interpret the use of a new special file name to indicate that the local server's prefix list should be used. When a file is specified as "[INST](:PFX).FILE.NAME", where 'INST' is the remote installation and 'FILE.NAME' is any file name, the server will recognize the special family designation. '(:PFX)' to mean th remove the family and the leading '.' in the specified file name. Since the resluting file name will begin with neither a '(' nore a '.', the server prefix list will be used to open the file. FOr example, for file name "[SYSTEM2](:PFX).DATA.FILE", the server on system 'SYSTEM2' will attempt to access file "DATA.FILE" in the user's current prefix. (On Patch 55). 2.6 IFR Utility IFR will now allow restoring multiple files via a file list. (See Notes & Special Considerations, 1.3.12; Patch 55) 2.7 Unattended Image T3LD On-Line backup (HCC) From the menu program "PSMU01", "PSBU01" will no longer report "ABORTED BACKUP DUE TO INVALID GHOST COMMUNICATIONS" during HCC Unattended Image Backup. (See Notes & Special Considerations, 1.3.14; Patch 55) Note: Please keep in mind this disclaimer (also included in the M7A Release Notes): THIS UNSUPPORTED SOFTWARE CANNOT PROTECT AGAINST ITS SOURCE DISK FROM BEING MODIFIED AS IT IT BEING BACKED UP. UPDATES TO FILES CAN OCCUR DURING THE PROCESS. IT IS UP TO THE USER TO INSURE THAT THIS DOES NOT HAPPEN. MBF DOES NOT GUARANTEE FILE INTEGRITY IF FILES ARE BEING MODIFIED DURING BACKUP. THE SOFTWARE IS UNSUPPORTED AND HAS NOT BEEN CERTIFIED ON ALL CONFIGURATIONS. 2.8 Spooler/Printer Fixes (OS) 2.8.1 VFU Load Fix Print job will no longer print with attributes from a previous form that was mounted. The VFU will now load correctly when a SETFORM is done to print jobs queued up waiting for the SETFORM to be done. (Notes & Special Considerations, 1.3.10.9; Patch 55) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg006 2.8.2 Will slew correctly in 8 lpi mode. Slewing in 8 lpi mode will no longer cause printing to be a half a line off. (European Support Center reported problem) NOTE 1: The number of "High Activity Tasks" is approximate and largely dependent on the application. The relative relationship of the numbers between configurations is more important than the actual numbers themselves. NOTE 2: System configurations of MPx 9xxx Series Systems are based on the use of the LS-700 power supply mainframes. Original 810 systems do not support the LS-700 power supply and, therefore, will not meet all defined maximum configurations listed. NOTE 3: The following configurations are based on performance testing, and are subject to change as newer performance testing data becomes available. The configurations listed in the marketing announcements override those listed here. 3.1 CONFIGURATIONS FOR MPX 7000/7100/8000 SERIES SYSTEMS The maximum configuration for MPx 7000, 7100, and 8000 Series Systems, models 7030, 7130, and 8030, is as follows: 116 Devices - A combination of 8-ways, 16-ways, the 4 ports on the MCS PCBA, MDTs and HVDTs up to a total of 116 devices are supported. 3 CPU sets 10 ISDCs: 16-ways (7 maximum) and/or 8-ways 32 Ghost tasks 24 High speed videos (HVDT) 8 Disk drives 4 Parallel printers 2-8 Megabytes of memory 2 Magnetic tape drives - MTR, MTS, and/or GCR (2 Maximum), and/or MCS (1 maximum) 4 Intelligent Multi-Line Controllers (IMLC) 8 DataWord II terminals 4 TBC lines 64 3270 terminals 8 X.25 lines 2 Auto-Call Units (ACU) 99 Serial Printers 99 System printers (total serial and parallel not to exceed 99) 2 Buffered Magnetic Tape Controllers 27 High activity concurrent tasks 1 LAN controller NOTE: There is a maximum of 9 memory assembly boards in any combination of 1/2 Mb, 1 Mb, 2 Mb, 4 Mb and BMTCs (a maximum of 3 boards per chassis). Models 7010/7110/8010 and 7020/7120/8020 have the same configuration limits as models 7030 and 8030 above, with the SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg007 following limitations: 7010/7110/8010 7020/7120/8020 1 CPU set 2 CPU sets 2-4 Mb memory 2-8 Mb memory 20 Devices 52 Devices 12 Concurrent tasks 20 Concurrent tasks (high activity) (high activity) 23 System printers 51 System printers 3.2 CONFIGURATIONS FOR MPX 9000/9100/9400 SERIES SYSTEMS The maximum configuration for MPx 9000, 9100, and 9400 Series Systems, models 9020, 9120, and 9420 is as follows: 116 Devices - A combination of 8-ways, 16-ways, the 4 ports on the MCS PCBA, MDTs and HVDTs up to a total of 116 devices are supported. 2 CPU sets with Evaluation Stack and Rstack Cache 10 ISDCs: 16-ways (7 maximum) and/or 8-ways (10 maximum) 32 Ghost tasks 24 High speed videos (HVDT) 16 Disk drives on models 9020 and 9120, 8 disk drives on model 9420(5.1 GB maximum), with no more than 8 14-inch fixed drives on any of the 3 models 8 Parallel printers 4-12 Megabytes of memory 4 Magnetic tape drives - MTR, MTS, and/or GCR (2 maximum), and/or MCS,HCC (1 maximum) 4 Intelligent Multi-Line Controllers (IMLC) 8 DataWord II terminals 6 TBC lines 64 3270 terminals 8 X.25 lines 2 Auto-Call Units (ACU) 99 Serial printers 99 System printers (total serial and parallel not to exceed 99) 4 DMA controllers (including DMA-I, DMA-II and DMA-III's in any combination)* 4 Buffered Magnetic Tape Controllers 42 High activity concurrent tasks 1 LAN controller * It is recommended that, for maximum performance, no more than two 250MB disks be configured per DMA-II, and that the number of DMA-II's equals or exceeds the number of CPU's. Models 9010, 9110, and 9410 have the same configuration limits as the 9020, 9120, and 9420 above, with the following exceptions: 1 CPU set with Evaluation Stack and Rstack Cache 68 Devices 10 ISDCs: 16-ways (4 maximum) and/or 8-ways (8 maximum) 67 Serial printers 75 System printers (total serial and parallel not to exceed 75) 27 High activity concurrent tasks SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg008 3.3 CONFIGURATIONS FOR MPX 9500/9600 SERIES SYSTEMS The maximum configuration for MPx 9500 and 9600 Series Systems, models 9530 and 9630, is the same as the maximum configuration for the MPx 9000, 9100 and 9400 Series Systems, models 9020, 9120, and 9420 with the following exceptions: 3 CPU sets with Evaluation Stack Rstack Cache Code Cache Data Cache 255 Devices 16 ISDCs: 16-ways (16 maximum) and/or 8-ways (16 maximum) 4-24 Maximum megabytes of main memory (see Hardware section for mandatory revision levels for main memory support above 12 megabytes) 16 Disk drives on model 9530, 12 disk drives on model 9630 (7.9 GB maximum), with no more than 8 14-inch fixed drives on either model 4 DMA controllers (including DMA-I, DMA-II, and DMA-III's in any combination.) 82 High activity concurrent tasks Models 9510/9520 and 9610/9620 have the same configuration limits as models 9530/9630 with the following exceptions: 9510/9610 9520/9620 1 CPU set 2 CPU sets (same caches as the 9530) (same caches as the 9530) 16 disk drives (9610) 16 disk drives (9620) 10 ISDCs: 16-way (5 maximum) 10 ISDCs: 16-way (8 maximum) 8-way (8 maximum) 8-way (10 maximum) 84 Devices 132 Devices 83 Serial printers 63 Concurrent tasks 91 System printers (high activity) (total serial and parallel) 52 Concurrent tasks (high activity) 3.4 CONFIGURATIONS FOR THE ADVANCED SERIES FAMILY The maximum number of high activity concurrent tasks is 140 on the Advanced Series Model 63, 65 on the ADVANCED SERIES Model 42 and 40 on the ADVANCED SERIES model 20. The maximum configuration for ADVANCED SERIES model 63 is as follows: 255 Devices - A combination of 8-ways, 16-ways, and the 4 ports on the MCS/M PCBA, and MDT's up to a total of 255 devices are supported. 3 CPU's (with cache boards) 16 ISDCs: 16-ways (16 maximum) and/or 8-ways (16 maximum) 4-48 Maximum megabytes of main memory (See Hardware section for mandatory revision levels for main memory support above 12 megabytes.) 16 Disk drives (may be 300MB and 590MB fixed disks, 285 removables, or 364MB,250MB, 690MB on DMA-II for up to 11 GB SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg009 maximum) 4 DMA controllers with standard backplane. Double wide backplane allows 6 DMA controllers. (The controllers may be DMA-I disk controllers for support of 285Mb removable disks and/or DMA-III disk and parallel printer controllers for support of 300Mb and 590Mb fixed disks and parallel printers) * 32 Ghost tasks 8 Parallel printers 4 Magnetic tape drives - MTR, MTS, and/or GCR (2 maximum), and/or MCS (1 maximum) 4 Intelligent Multi-Line Controllers (IMLC) 8 DataWord II terminals 4 TBC lines 64 3270 terminals 8 X.25 lines 2 Auto-Call Units (ACU) 99 Serial printers 99 System printers (total serial and parallel not to exceed 99) 4 Buffered Magnetic Tape Controllers 1 LAN controller The maximum configuration for ADVANCED SERIES model 62 is the same as for model 63, with the following exceptions: 196 Devices 2 CPU's (with cache boards) 4-36 maximum megabytes of main memory 12 16-ways; 12 8-ways The maximum configuration for ADVANCED SERIES model 61 is the same as for model 63, with the following exceptions: 148 Devices 1 CPU (with cache board) 4-28 maximum megabytes of main memory 9 16-ways; 9 8-ways The maximum configuration for ADVANCED SERIES model 42 is the same as for model 63, with the following exceptions: 132 Devices 2 CPU's (without cache) 4-24 maximum megabytes of main memory 8 16-ways; 8 8-ways The maximum configuration for ADVANCED SERIES model 41 is the same as for model 63, with the following exceptions: 100 Devices 1 CPU (without cache) 4-20 maximum megabytes of main memory 6 16-way; 6 8-ways The maximum configuration for ADVANCED SERIES model 20 is the same as for model 63, with the following exceptions: 1 chassis 52 Devices SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg010 1 CPU (without cache) 4-12 maximum megabytes of main memory 2 disks maximum; 250MB, 364MB, 690MB disks (up to 1.4GB) 2 parallel ports 3 ISDCs: 16-ways maximum 51 serial printers 53 system printers 1 BMTC 2 IMLC * For maximum performance, it is recommended that no more than 2 disks be configured per DMA. NOTE: To access all of the software documented in this section, the prefix must be set to the .R7Bxx.DIAG.,.R7Bxx.INST. node. Please see the installation sections in this announcement for instructions on how to install DEMON and REMIDI. Further information on these diagnostics can be found in DOCWRITER, which can be accessed by entering !DOCWRITER in command mode. 4.1 REMIDI NOTE: UPDATE.LD needs to be run for REMIDI whenever question marks (?/?) appear in Load Sector 2 at the top of the OSINFO screen. 4.1.1 ON MPx 7000,7100, AND 8000 SERIES SYSTEMS REMIDI version BV includes all micro-diagnostics except those for the MPC and LAN controllers. It is loaded into WCS slot 2 and is used on MPx 7000, 7100, and 8000 Series Systems. REMIDI version BVM contains micro-diagnostics for the MPC and LAN controllers. It is loaded into WCS slot 3 on all 7000/7100 Series Systems and on 8000 Series Systems with LAN controllers. This version of REMIDI is used on MPx 7000/7100 Series Systems for the MPC and LAN controllers, and on 8000 Series Systems for LAN controllers only. If a LAN controller is not present on an 8000 Series System, the BVM version of REMIDI is not needed. The Load Directory controls which version of REMIDI will be executed. The UPDATE.LD utility is used to update the Load Directory. See the following section for instructions on running UPDATE.LD. UPDATING THE LOAD DIRECTORY FOR REMIDI Disregard this section if your 8000 Series System does not have a LAN controller. (In this case only REMIDI version BV is used, and it is not necessary to update the Load Directory.) Since REMIDI is a WCS Image, two WCS slots, slot 2 and slot 3, will be required for the two REMIDI versions. The extra slot is provided by the DEMON WCS slot. Because DEMON and the BOSS/VS O.S. share the same WCS, Load Sector 3 should display 3/0 or 3/1, indicating that the WCS for DEMON is in SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg011 either WCS slot 0 or WCS slot 1. This leaves WCS slot 3 free for REMIDI. Only one version of REMIDI will run at a time. The version that will run is dependent on how the Load Directory for REMIDI (Load Sector 2) is set up. The standard version, BV, which resides in WCS slot 2, has an OS/WCS of 0/2. The MPC/LAN version, BVM, which resides in WCS slot 3, has an OS/WCS of 0/3. Use UPDATE.LD to update the Load Directory to designate which version to run. To test the MPC and LAN controllers with REMIDI version BVM, execute UPDATE.LD, using the inputs below: NOTE: Lines preceded by an "*" require operator input. * Input in command mode !UPDATE.LD Update Load Directory Utility (Version 6.5.5.0) Disks (Unit number) on line : 0(16),1(17) Enter disk number: Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 7.1.x.x R 7B*xx (date) B 6.1.x.x 1 1/1 | 7.1.x.x R 7B*xx (date) B 6.1.x.x 2 0/2 | B 6.1.x R 3 3/0 | 7.1.x.x DEMON B 6.x.x R * New OS slot (0,1,3): 0 * New WCS slot (0..3): 3 * Load sector (0..3) : 2 In this case, UPDATE.LD will then display the new Load Directory as follows: Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 7.1.x.x R 7B*xx (date) B 6.1.x.x 1 1/1 | 7.1.x.x R 7B*xx (date) B 6.1.x.x 2 0/3 | B 6.x.x R 3 3/0 | 7.1.x.x DEMON B 6.x.x R Notice the change in Load Sector 2. To go back to the standard REMIDI version, BV, which tests the CPU and main memory, use the following in UPDATE.LD: * New OS slot (0,1,3): 0 * New WCS slot (0..3): 2 * Load sector (0..3) : 2 In this case, UPDATE.LD will then display the new Load Directory as follows: Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 7.1.x.x R 7B*xx (date) B 6.1.x.x 1 1/1 | 7.1.x.x R 7B*xx (date) B 6.1.x.x 2 0/2 | B 6.x.x R 3 3/0 | 7.1.x.x DEMON B 6.x.x R NOTE: The Load Directory should stay in the above setup in case the system CPU needs to be tested in a down condition. Always use Load Sector 2 for REMIDI. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg012 ON MPx 9xxx AND THE ADVANCED SERIES REMIDI for MPx 9xxx Series Systems consists of two sections, AVA, which is loaded into WCS slot 2, and AVC, which is loaded into WCS slot 3. REMIDI for the ADVANCED SERIES family also consists of two sections, CVA, which is loaded into WCS slot 2, and CVC, which is loaded into WCS slot 3. Unlike the REMIDI versions on 7xxx/8xxx systems, the REMIDI versions on 9xxx and ADVANCED SERIES Systems, are not used independently by slot. In other words, the version of REMIDI in WCS slot 2 calls the version of REMIDI in WCS slot 3 on 9xxx and ADVANCED SERIES Systems. Load Sector 2 contains the OS/WCS pointers for REMIDI. UPDATING THE LOAD DIRECTORY FOR REMIDI Normally, the Load Directory is updated by the operating system when REMIDI is installed with UPDATE.WCS. However, if Load Sector 2 does not reflect an O.S./WCS of 0/2, the UPDATE.LD utility can be run to update the Load Directory: NOTE: Lines preceded by an "*" require operator input. Update Load Directory Utility (Version 6.5.5.0) Disks (Unit number) on line : 0(16) 1(17) ENTER DISK NUMBER: Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 7.1.x.x R 7B*xx (date) x 6.x.x 1 1/1 | 7.1.x.x R 7B*xx (date) x 6.x.x 2 ?/? | x 6.x.x R 3 3/0 | 7.1.x.x DEMON x 6.x.x R * New OS slot (0,1,3): 0 * New WCS slot (0..3): 2 * Load sector (0..3 : 2 UPDATE.LD will then display the new Load Directory as follows: Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 7.1.x.x R 7B*xx (date) x 6.x.x 1 1/1 | 7.1.x.x R 7B*xx (date) x 6.x.x 2 0/2 | x 6.x.x R 3 3/0 | 7.1.x.x DEMON x 6.x.x R Notice the change in Load Sector 2. 4.2 DEMON - UPDATING THE LOAD DIRECTORY Because REMIDI resides in WCS slot 3 on 7xxx and 9xxx systems and 8xxx systems with LAN, the Load Directory must point to another WCS slot for DEMON on these systems. The O.S. and DEMON share the same WCS code, therefore, Load Sector 3 should point to the WCS slot used by the O.S. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg013 Normally, this is set up by the operating system when DEMON is installed, providing that the correct answers are entered at the UPDATE.OS prompts during installation. If, for any reason, Load Sector 3 does not reflect OS/WCS as 3/0 or 3/1, you may use UPDATE.LD to change it, using the following inputs: NOTE: Lines preceded by an "*" require operator input: Update Load Directory Utility (Version 6.5.5.0) Disks (Unit number) on line : 0(16),1(17) Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 6.7.x.x R 7B*xx (date) x 6.x.x 1 1/1 | 6.7.x.x R 7B*xx (date) x 6.x.x 2 0/2 | x 6.x.x R 3 3/3 | 6.7.x.x DEMON x 6.x.x R * New OS slot (0,1,3): 3 * NEW WCS SLOT (0..3): 0 * LOAD SECTOR (0..3) : 3 UPDATE.LD will then display the new Load Directory as follows: Load OS/WCS | OS-Level Name WCS-Level 0 0/0 | 6.7.x.x R 7B*xx (date) x 6.x.x 1 1/1 | 6.7.x.x R 7B*xx (date) x 6.x.x 2 0/2 | x 6.x.x R 3 3/0 | 6.7.x.x DEMON x 6.x.x R Notice that Load Sector 3 is now pointing to WCS slot 0. 4.3 ADVANCED SERIES ONLY 4.3.1 HIGH FREQUENCY MARGINS ON ADVANCED SERIES The ADVANCED SERIES processor has the capability to run at a faster clock rate for diagnostic purposes. This capability is intended for diagnostic testing of the CPUs ONLY. The system should never be used at the higher clock rate except for diagnostic purposes. 4.3.2 USING ALT LOAD FOR REMIDI AND DEMON On the ADVANCED SERIES, REMIDI and DEMON can be loaded to memory from the O.S. tape via ALT LOAD and executed. To load REMIDI, load switch 2 should be on. To load DEMON, load switches 2 and 3 should be on. Pressing the ALT LOAD switch will then load the selected diagnostic into memory for execution. 4.4 DIAGNOSTIC REMOVAL This section describes the removal of diagnostic programs from a system. The diagnostics reside in the file system and several bootable disk slots. They are removed from the file system with the 'delete' utility. They are removed from the bootable slots by overwriting the images. The procedure follows. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg014 1. Removing REMIDI The removal of REMIDI is accomplished by overwriting the two bootable REMIDI slots with the WCS image. 2. Update WCS Slot 2 Execute the UPDATE.WCS utility and respond to the prompts as shown below. ENTER WCS SLOT (0..3): - 2 AVAILABLE DISK UNITS ARE: - (displayed) DISK TO UPDATE : - Enter the disk number. WCS IMAGE FILE: (where X = A,B,C) X = A for MPx 9xxx X = B for MPx 7xxx, 8xxx X = C for Advanced Series WCS LEVEL OF WCS IMAGE FILE: - (displayed) During the update process, the following message appears: UPDATING DISK UNIT nn SECTOR xx When the update is complete, the following message appears: WCS UPDATE COMPLETED! The preceding should be performed on all system disks. 3. Update WCS Slot 3 Execute the UPDATE.WCS utility and respond to the prompts as shown below. ENTER WCS SLOT (0..3): - 3 AVAILABLE DISK UNITS ARE: - (displayed) DISK TO UPDATE : - Enter the disk number. WCS IMAGE FILE: - .R7Bxx.INST.WCS.X (where X = A,B,C) X = A for MPx 9xxx X = B for MPx 7xxx, 8xxx X = C for Advanced Series WCS LEVEL OF WCS IMAGE FILE: - (displayed) During the update process, the following message appears: UPDATING DISK UNIT nn SECTOR xx When the update is complete, the following message appears: WCS UPDATE COMPLETED! The preceding should be performed on all system disks. 4. Removing DEMON The removal of DEMON is accomplished by overwriting the SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg015 bootable DEMON slot with DEMON.UX. 5. Update OS Slot 3 Execute the UPDATE.OS utility and respond to the prompts as shown below. BOSS/VS Image File Name: - DEMON.UX Target OS Slot (0/1/3): - 3 Target WCS Slot (0-3): - 0 Target Drives (0/1/All/Quit): - Enter the disk number During the update process, the following message appears: Updates all complete. The preceding should be performed on all system disks. 6. Removing diagnostics from the file system The diagnostics are removed from the file system using the 'delete' utility. The diagnostics are found in the system node .R7Bxx.DIAG. The files in the following nodes should be deleted from the file system. .R7Bxx.DIAG. .ENHANCER7B. .TRACKER. The following files should be deleted: .AC (MPX 9000 Series 1/4" tape boot OS image with DIVE) .AT (MPx 9000 Series 1/2" tape boot OS image with DIVE) .BC (MPx 7000 Series 1/4" tape boot OS image with DIVE) .BT (MPx 8000 Series 1/2" tape boot OS image with DIVE) .CC (Advanced Series 1/4" tape boot OS image with DIVE) .CT (Advanced Series 1/2" tape boot OS image with DIVE) The following file(s) should be added as a replacement for the file(s) deleted above. .ACX (MPx 9000 Series 1/4" tape boot OS image without DIVE) .ATX (MPx 9000 Series 1/2" tape boot OS image without DIVE) .BCX (MPx 7000 Series 1/4" tape boot OS image without DIVE) .BTX (MPx 8000 Series 1/2" tape boot OS image without DIVE) .CCX (Advanced Series 1/4" tape boot OS image without DIVE) .CTX (Advanced Series 1/2" tape boot OS image without DIVE) This completes the diagnostic removal procedure! When upgrading to O.S. levels 9/8.7B, hardware changes, per se, are not required EXCEPT if your system contains a DMA- II. However, the following list of PCBA revision levels indicates the MANDATORY and RECOMMENDED revision levels of MPx and ADVANCED SERIES PCBA's. MANDATORY means that the specified revision level is needed for system operation. This level provides minimum assurance that your customer's system will operate in a stable manner. RECOMMENDED means that the specified revision level ensures the reliable operation of your customer's system. The SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg016 RECOMMENDED (or higher) revision levels help to assure reliability and stability. If your customers' system PCBA's are at MANDATORY levels or below, careful plans should be made to replace the PCBA's with the RECOMMENDED (or higher) revisions. This should be done on a one per visit basis, such as one board per PM visit. DO NOT replace all PCBA's simultaneously. Some RECOMMENDED revision levels may vary based on specific system configurations, as detailed below. For example, the 16Mb High Speed Memory PCBA requires specific MCS and Terminator PCBA's. 5.1 MPX 7000, 7100, AND 8000 PCBA NOTES 1) MCS 903374-001 PCBA Revision L is the mandatory and recommended level. Revision S adds another option to the switch setting of SW- 1. SW-1 position 4 (SW1-4) is switch selectable between MPx 7000/7100/8000 Series Systems (SW1-4, OPEN) or MPx 9xxx Series Systems (SW1-4, CLOSED). If the MCS PCBA, at revision S, is switch selected for MPx 9xxx Series Systems and installed into an MPx 7000/7100/8000 Series System, it will not load. - MCS 903374-002 PCBA-Revision V Revision V creates the -002 assembly. This assembly can be used on all MPx systems. 2) MDI 903361-001 PCBA Revision L is the mandatory and recommended level. This level prevents the MDI/ACS clocks from drifting and getting out of phase, which causes "INVOP" and "NILPTR" dumps. - MDI 903408-001 PCBA Revision K is the mandatory and recommended level. This level prevents the MDI/ACS clocks from drifting and getting out of phase, which causes "INVOP" and "NILPTR" dumps. 3) ACS 903379-001/-002 PCBA's Revision L is the mandatory and recommended level. 8000 systems on OS 8.4B or above require revision L, boot prom version 2.0.0.1 or higher. 7000 systems require revision Y or above, boot prom version 2.0.0.4 or higher (MPC support). Revision level Z, boot prom version 2.0.0.2, cannot be used on 7000 systems (no MPC support). Revision levels V and W, boot prom version 2.0.0.3, is obsolete; do not use. Tape load support from a BMTC requires revision T, boot prom version 2.0.0.5 or higher. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg017 Systems with 8-inch fixed drives require revision AA, boot prom version 2.0.0.5 or higher. - ACS 903379-003 PCBA Revision AD creates the -003 assembly. This version of the ACS PCBA can also be used in 7000/8000 systems. 7100 systems require AD or higher and this revision level is also required for support of the 120Mb MTCS tape. Board versions -002 or -003 are mandatory for 3 CPU systems, MPx 7xxx/8xxx Series Systems. 4) MPC 903500 PCBA Revision H is the mandatory and recommended level. If used in the MPx 7100 system, remove JMP3, if present, and set SW2-1 and SW2-4 OFF. - MPC 903546 PCBA Revision B is the mandatory level; revision H is the recommended level. If used in the MPx 7100 system, remove JMP3 if present and set SW2-1 and SW2-2 OFF. 5) TDP Controller 903217-001 PCBA Revision K is the mandatory level. Revision K eliminates excessive sector number errors written to the ERRORLOG. Revision W is the recommended level. This revision checks for Signetic IC's at locations 9E and 10K, if the IC's at these two locations are something other than Signetics, then this revision level is not required. Issue with 8" drives only. - TDP Controller 903453-001 PCBA New build TDP controller, which replaces TDP controller 903217-001. Revision A is the mandatory level. Revision J is the recommended level. This revision checks for Signetic IC's at locations 9E and 10K, if the IC's at these two locations are something other than Signetics, then this revision level is not required. Issue with 8" drives only. 6) NIMLC Controller 903381-001 PCBA Revision E is the mandatory level; revision K is the recommended level. This IMLC must be located to the right of the CPU set. Revision G provides correct line status for Data Set Ready (DSR), when no device is attached. Revision K is mandatory or all three (3) mainframe systems. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg018 - NIMLC Controller 903381-002 Revision N creates this version of NIMLC for international use. It provides RS-232-C interface on Port B, using standard 1488/1489 IC's to support cabling longer than 50 feet (provides higher input impedance interface required for use on various Wide-Area Networks). - NIMLC Controller 903534-001 PCBA Revision D is the mandatory and recommended level. Provides the same interface as the 903381-002 PCBA on ports A and B. This NIMLC can be located on the left or right of the CPU. - NIMLC Controller 903251-001 PCBA This NIMLC was used with the 810 system and will not operate on the MPx series systems. 7) Memory (1Mb, 2Mb, 4Mb) 903516-00x PCBA Revision A is the mandatory level; evision E is the recommended level. Memory 903516-001 PCBA is the 2Mb version. Memory 903516- 002 PCBA is the 4Mb version. Memory 903516-003 PCBA is the 1Mb version. 8) Terminator 903199 PCBA Revision D is the mandatory and recommended level. Revision H creates the -004 assembly. Revision H can be used on all MPx systems. 5.2 MPX 9XXX SERIES SYSTEM PCBA NOTES NOTE: An asterisk (*) appears in front of revision levels that are mandatory for main memory support above 12 megabytes. Higher revision levels may be used too. 1) MCS 903374 PCBA Revision L is the mandatory level; revision S is the recommended level. Revision S, or above, is required for reliable system operation. Revision S adds another option to the switch setting of SW1. SW1 position 4 (SW1-4) is switch selectable between the addressing schemes of the MPx 7000/7100/8000 (SW1-4, OPEN) Series Systems or the MPx 9xxx Series Systems (SW1-4, CLOSED). If the MCS PCBA is switch selected for MPx 7000/7100/8000 systems and installed into an MPx 9xxx Series System, board addresses 32 thru 47 are reserved for the IMLC PCB only. If the MPx 9xxx scheme is used then there are no address restrictions. * Revision T is required for main memory support above 12 megabytes. Set SW1-4 to CLOSE for the 9xxx addressing scheme. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg019 * Revision V creates the -002 MCS. This revision s mandatory for support of the 16Mb memory board (P/N 903621) on 9xxx systems. It also can be used for main memory support above 12Mb. 2) AMS 903548 PCBA Revision F is the mandatory level, revision L is the recommended level. Revision F released the 4K boot proms version 3.1.0.4. This revision, or above, is required for operation. * Revision N creates the -002 PCBA and is required for main memory support above 12 megabytes. Revision P creates the -003 PCBA and is required for MPx 94xx (SCSI) systems. The -003 PCBA can be used in all MPx systems. Revision P is required for support of the 621Mb fixed disk drive and the DMA-III PCBA. 3) ESTK 903552 PCBA Revision G is the mandatory and recommended level. * Revision J, or above, is required for main memory support above 12 megabytes. 4) IDC 903550-001 PCBA (with cache) IDC 903550-002 PCBA (without cache) Revision H is the mandatory level; revision P is the recommended level. Revision J addresses cache timing roblems on selected systems. Do not replace the IDC PCBA on an error free system. 5) IDC64 903597-001 PCBA (with cache) IDC64 903597-002 PCBA (without cache) Revision E is the mandatory level; revision H is the recommended level. * IDC64 PCBA is required for support of main memory above 12 megabytes. Strap E6 to E7 must be out to configure PCB for use above 12MB. 6) DMA-I 903554 PCBA * Revision H is the mandatory level; revision AA is the recommended level especially if there is a DMAII in the system. Revision H is required for the 600 LPM band printer, model 20. It is also required if 300Mb 8-inch drives log excessive errors in the ERRORLOG. Revision N is required when used with the DMA-II. Revision P, or above, is required for reliable system operation, also if the DMA-III is in the system. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg020 Revision R is required for use with the 16Mb memory board for full power fail recovery. Revision Z is required for systems that have more than 2 DMA's installed for performance. Revision AA is recommended when system also contains DMA-II. This revision eliminates soft Head/Cyl (8004) errors reported against the drives supported on the DMA-I when DMA- II is installed. This revision also reports 8001 'Offline status' instead of 8002 'Not ready' when taking disk packs out of removable drives. 7) DMA-II (SCSI) 903599 PCBA Revision K required for MPx 94xx SCSI disk drive support; requires 9.6C or later O.S. and the AMS -003 version. Revision L contains a fix for excessive soft errors logged in the ERRORLOG when both DMA-I's and DMA-II's are in the same system. Revision M Creates the DMA-II -002 version. This revision has become the mandatory and recommended level. This is the mandatory level for support of the 364Mb (M380), 690Mb(M760) and 1.6GByte (P1-17S) SCSI disk drive. NOTE: This level of DMA-II is mandatory if n.6G OS, or above, is installed on the system. (It is also a replacement for the -001 and does not require the n.6G OS or above.) Revision P prevents hang conditions in multi-CPU ASxx systems and corrects Disk Errorlog status '00000000' entries. - DMA-II (SCSI) 903741 PCBA This is the new version of DMA-II due to artwork changes. It may be used in place of 903599 PCBA and visa versa. Revision E has become the mandatory and recommended revision level. This revision is mandatory for support of the 364Mb (M380) and 690Mb (M760) SCSI disk drive. This creates the - 002 version. NOTE: This level of DMA-II is mandatory if n.6G OS, or above, is installed on the system. Revision K prevents hang conditions in multi-CPU ASxx systems and corrects Disk Errorlog status '00000000' entries. 8) DMA-III (SMD) 903679-001 PCBA The DMA-III is required for support of the F621Mb fixed disk drive. (The F621Mb disk also requires the 903548-003 AMS board.) The DMA-III revision C controller also supports the 300Mb disk drive without the use of the SMD-I/II PCBA. This controller has the SMD logic embedded. Revision E is required for DMA-I/II/III to reside in the same system. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg021 Revision G is required for systems that have more than 2 DMA's installed for performance. Revision J is now the recommended/mandatory revision level. This level prevents possible data corruption. When a DMA- III is replaced, this level should be used. 9) NIMLC 903381-001 PCBA Revision K is the mandatory and recommended level. This NIMLC must be located to the right of the CPU set. - NIMLC 903381-002 PCBA Revision N creates this version of NIMLC for International use. It provides RS-232-C interface on Port B using standard 1488/1489 IC's to support cabling longer than 50 feet (provides the higher input impedance interface required for use on various Wide-Area Networks). - NIMLC 903534 PCBA Revision D is the mandatory and recommended level. This revision provides the same interface as the 903381-002 PCBA on ports A and B. This NIMLC can be located on the left or right of the CPU set. - NIMLC 903251 is OBSOLETE This NIMLC was used with the 810 system and will not operate on the MPx Series Systems. NOTES: There have been a few instances when a known good IMLC is installed into the MPx 9xxx system, the RED LED (Parity error) comes on during load (903534/903381). In this case, install JMP C on the PCBA. When the JMP C option is used on the MPx 9xxx system and "T0" is a serial terminal, the system will hang in the TYPE II/III load. This side effect only occurs with the 9.6A OS and is fixed in 9.6B OS and above. Refer to Field Bulletin #375. 10) Memory (1/2Mb and 1Mb) 903349 PCBA Revision V is the mandatory and recommended level. This revision is not to be used with greater than 12 megabyte support. 11) Memory (2 and 4 MB) 903516-00x PCBA Revision E is the mandatory and recommended level. Memory 903516-001 PCBA is the 2Mb version, 903516-002 PCBA is the 4Mb version. * Revision J is required for support of main memory above 12 megabytes. Support of main memory above 12 megabytes is supported on MPx 9500 and 9600 Series Systems only. JMP 5 at location 1E = 1 to 2, and IC pad location 1A = 8 to 9. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg022 12) 16/8/4Mb High Speed ECC Memory 903621-00x PCBA High Speed ECC Memory 903621-001 (16Mb), -003 (8Mb), -004 (4Mb) version are supported on the MPx 9xxx Series Systems. Requires MCS -002, Terminator -004, DMA-I at revision R or above for MPx Series Systems. Revision C is the mandatory level; revision F is the recommended level. Revision G creates the 903621-005 (16Mb), -007 (8Mb), -008 (4Mb) versions. Revision N if 30 or more slots are used in 9530. 13) Terminator 903199 PCBA Revision D is the mandatory and recommended level. Revision H creates the -004 assembly, which is mandatory for support of the 16b, High Speed ECC memory board versions (P/N 903621). 14) Non Supported PCBA's on MPx 9xxx Series System The following boards are NOT supported on MPx 9xxx Series Systems: 1) 7000/7100/8000 CPU set. 2) TDP (Must be replaced by the BMTC for tape support). 3) MPC. 5.3 PCBA'S FOR ALL MPX 7/8/9XXX SERIES SYSTEMS The following are PCBA'S common to all MPx Series Systems without system model dependencies: 1) BMTC 903413 PCBA Revision R is required for full MTCS support. This is the minimum revision for support of the HCC tape unit. NOTE: The HCC is supported on the MPx 9xxx and Advanced Series systems only. Revision U is required for support of the GCR 1/2" tape drive model 4405. Revision Z allows the BMTC to operate on the left or right side of the CPU set. Revision AD is the mandatory and recommended level. This revision level will insure that a 'hard' error is posted, during restore of data, when using the GCR tape unit. This level also cures a problem where the BMTC goes 'offline' when using SAVERESTORE. 2) Local Area Network Controller (LAN) 903595 PCBA Revision E is the mandatory level; revision F is the recommended level. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg023 With the release of the 9.6A/8.6A O.S., a new controller is supported: The Local Area Network controller. The LAN PCBA provides the ability to tie like systems together (MPx to MPx) in a local environment not more than 4000 feet apart. Each system requires one LAN controller, and both systems must be on the same O.S. level. The LAN may be installed either to the right of the CPU set(s) after the BMTC PCBA or to the left of the MCS PCBA. Refer to the MAGNET section in this document for further information on the Local Area Network. Revision H creates the -002 version. This version can be used on all MPx series systems and ASxx systems. 3) 16-Way Controller 903437 PCBA 16-Way controllers require the use of an I/O panel. The I/O panel is supplied with the purchase of the PCBA. Revision J is the mandatory and recommended level. Revision R creates the -002 version that supports hardware flow control with the n.7A, or above release of software. Cable PN 916509, revision B, must also be used for this feature and 'CTS' Flow Control='Y' in TERM.CONFIG. 4) 8-Way Controller 903383 PCBA Revision A is the mandatory and recommended level. 5) VCON Controller 903377 PCBA Revision C is the mandatory and recommended level. The following are PCBA's that are supported on the ADVANCED SERIES and their revision levels. NOTE: An asterisk (*) appears in front of revision levels that are MANDATORY for the Doublewide backplane chassis. A pound sign (#) appears in front of revision levels that differ from the minimum revision levels of the Advanced Series systems. These revision levels are MANDATORY for the Advanced Series model 21 system. 1) MCS/M 903718 PCBA Revision G is the released level of this PCBA. The MCS/M (Memory Communication Support with Memory) PCBA provides boot load function/clocks/4-way and 4Mb of main memory. # Revision H (-002) is the mandatory level for support of the DMA-II PCBA and the SCSI disk drives on the Advanced Series system. Revision J required for 19.2K Baud and 7/8 bit data support for T0. 2) NEP II 903705 PCBA Revision G is the mandatory level; heat-sink added. Revision J recommended. * Revision K is the mandatory level when used in the SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg024 Doublewide backplane chassis. This is also the recommended level for the model 21 system. 3) STACHE II 903707 PCBA Revision D is the released level of this PCBA. The STACHE II PCBA is an optional PCBA that makes up the Advanced Series Model 6x. It contains the Rstack, Code Cache, and Data Cache. * Revision F is mandatory for Doublewide backplane chassis. 4) MBA 903617 PCBA Revision D is the released level of this PCBA. The MBA (Memory Bus Adapter) PCBA is required to support the shared memory controllers developed for the MPx 8/9xxx systems (160ns clock) on the Advanced Series Models 40/60 (80ns clock). Revision E is mandatory for support of the Advanced Series system. # * Revision H is mandatory for the Doublewide backplane chassis. This is also the recommended revision level for ALL Advanced Series systems. 5) BMTC 903413 PCBA Revision Z is required for support of the Advanced Series systems. Revision AD is the mandatory and recommended level. This revision level will insure that a 'hard' error is posted, during restore of data, when using the GCR tape unit. This level also cures a problem where the BMTC goes 'offline' when using SAVERESTORE. 6) LAN 903595-002 PCBA Revision H creates the -002 version, this version is mandatory for support of the Advanced Series systems. 7) DMA-I 903554 PCBA Revision R is mandatory for support on the Advanced Series, due to the 1Mbit rams used for main memory (MCS/M and 16Mb PCBA's) and full power fail recovery. Revision T corrects a problem in Revision R firmware which caused the timeout LED (DS2) to turn on during REMIDI testing in the Advanced Series family only. Revision Z is required for systems that have more than 2 DMA's installed for performance. Revision AA is recommended when system also contains DMA-II. This revision eliminates soft Head/Cyl (8004) errors reported against the drives supported on the DMA-I when DMA- II installed. This revision also reports 8001 'Offline status' instead of 8002 'Not ready' when taking disk packs SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg025 out of removable drives. 8) DMA-II (SCSI) 903599-002 PCBA The DMA-II requires the MCS/M -002 for support. Revision M is mandatory for support of the 364Mb (M380), 690Mb (M760) and 1.6Gbyte (P1-17S) SCSI 5-1/4 inch disk drive. This revision creates the -002 version. NOTE: This level of DMA-II is mandatory if n.6G OS, or above, is installed on the system. (It is also a replacement for the -001 and does not require the n.6G OS or above.) Revision N is the mandatory revision level if the Advanced Series system contains more than 4MB of main memory using the 903621-00x High Speed ECC memory. Revision P prevents hang conditions in multi-CPU ASxx systems and corrects Disk Errorlog status '00000000' entries. - DMA-II (SCSI) 903741-002 PCBA The DMA-II requires the MCS/M -002 for support. Revision E is mandatory for support of the 364Mb (M380) and 690Mb (M760) SCSI 5-1/4 inch disk drive. This revision creates the -002 version. Revision F is the mandatory revision level if the Advanced series system contains more than 4MB of main memory using the 903621-00x High Speed ECC memory. Revision K prevents hang conditions in multi-CPU ASxx systems and corrects Disk Errorlog status '00000000' entries. 9) DMA-III (SMD) 903679-001 PCBA The DMA-III is required for support of the F621 (600Mb) disk drive. It also supports the (300Mb) disk drive without the use of the SMD-I/II PCBA. This controller has the SMD logic on board. Revision E supports the DMA-I and DMA-II is also in the system. Revision G is required for systems that have more than 2 DMA's installed for performance. Revision J is now the recommended/mandatory revision level. This level prevents possible data corruption. When a DMA- III is replaced, this level should be used. 10) IMLC 903534 PCBA (903381 Not Supported on ASxx Series) Revision D is mandatory for support of the Advanced Series. This version of IMLC, at the indicated revision level, is required to function on the left side of the CPU set. Remove JMP C if installed. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg026 11) 16/8/4Mb High Speed ECC Memory 903621-00x PCBA Revision G creates the -005 (16Mb), -007 (8Mb), -008 (4Mb) versions. Refer to DMA-II section for other concerns if DMA-II is in the system. # * Revision N is the mandatory level. This revision helps prevent the possibility of parity errors during Nibble Mode cycles (Code Cache). 12) 8-WAY 903383 PCBA There is no mandatory revision level required for support of this PCBA on the Advanced Series. 13) 16-Way 903437 PCBA Revision J is LARL for support on the MPx and Advanced Series. Revision R creates the -002 version that supports hardware flow control with the n.7A, or above release of software. Cable PN 916509, revision B, must also be used for this feature and 'CTS' Flow Control='Y' in TERM.CONFIG. 14) Terminator 903199-004 PCBA Revision H is the mandatory level, and it creates the -004 version. 15) Terminator, High Speed 903769 PCBA * Revision A releases the High Speed Terminator, mandatory in Doublewide chassis. 16) LS-700 Power Supply Assembly 907295-001 If any MPx 8000 system is being upgraded to the Advanced Series family, the LS-700 assembly 907295-001 must be at revision AA. (PCBA 903386-001, inside the LS-700 assembly, will be at revision AB or above.) If any MPx 9xxx system is being upgraded to the Advanced Series family, the LS-700 power supply does not need to be replaced. The load sustained by this power supply under the 9xxx configuration gives sufficient evidence that the existing revision level is adequate for the Advanced Series. 5.5 PCBA'S NOT SUPPORTED ON ADVANCED SERIES The following boards are NOT supported on the Advanced Series family: 1) 7x00/8000/9x00 CPU sets. (Use Advanced Series 40/60 CPU's) 2) MCS PCBA. (Use MCS/M) 3) MPC, TDP and DMA-II-001. (Use DMA-I, DMA-II-002, and DMA-III) 4) Memory 903349 (1Mb assembly), 903516 (4Mb assembly), 903621-001/-003/004. (Use 16Mb: -005, 8Mb: -007, 4Mb: -008) 5) VCON PCBA and HVDT's 6) Terminators -001 (Below revision H). (Use -004) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg027 7) IMLC 903381 5.6 PERIPHERAL DEPENDENCIES 5.6.1 GCR TAPE DRIVE It is possible for a hang condition to occur in SAVERESTORE, if the GCR tape drive does not have the following minimum revision levels: IF CARD 403923205 (Previously, the LARL was 403923202) CP CARD 403864305 (Previously, the LARL was 403864303) BMTC PCBA revision AD is mandatory for support of the GCR due to a buffer transfer issue. 5.6.2 SCSI MTCS TAPE DRIVE On the 120MB SCSI MTCS 1/4-inch tape drive (4406), the E- PROM (OEM PN 966039; MBF PN 400716-103) at location 'U6' should be 3X10. This tape drive is used on MPx 94xx systems only. Requires the DMA-II for support. FUTURE PRODUCT: The 525MB SCSI MTCS 1/4-inch tape drive can replace the internal 120MB SCSI MTCS or the external 1/4-inch on the AS-21 without any other hardware changes. You must insure that the proper 1/4-inch tape cartridge is used to achieve proper data density storage. This requires the DMA-II and operating system level M.6G. 5.6.3 HIGH CAPACITY CARTRIDGE (HCC) TAPE DRIVE The HCC tape drive is supported on the MPx 9xxx and Advanced Series only. It requires the n.6G OS, or above, and the BMTC controller. The BMTC must at least be revision R or higher. The revision is dependent on other tape devices that may be attached to the same BMTC. Refer to the BMTC sections, under your system model. If you are using IFR and backing up multiple families with HCC, then it is recommended that the HCC firmware be updated to revision 'D'. This will achieve faster positioning to families on the tape. On the HCC unit, Switch 2, position 7 must be set to ON along with the revision 'D' firmware. The update will be done by the FE through the normal field upgrade procedures. 5.6.4 TERMINALS 1) The DT-4313 terminal must have REV E firmware to support Industry Standard slave printers. 2) T0 MUST be a model 4309 or later model VDT. VDT's 7250 and 7270 (4301) are not supported as T0 on release levels n.6C and above due to default terminal driver change. This change corrected the time differences seen in Saverestore Type I vs Type II load. 3) OS level n.6E and above loads T0 with defaults when going into a Type 2 or 3 load. After reloading the system, these settings remain loaded in the terminal. If SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg028 T0 is configured to settings other then the default values, the terminal will need to be reset. Defaults = EVDT, 9600, 7-bit, ODD Parity. The MCS/M at revision J, used on the Advanced Series systems, allows T0 to use 19.2K baud. 5.6.5 DISK DRIVES 1) The 590MB (aka F621/600Mb) fixed disk requires the -003 version of AMS PCBA P/N 903548 when used in 9xxx systems. The F621Mb disk is supported by the DMA-III controller, P/N 903679. Supported on n.6E OS or above. 2) The 300MB (aka P314) fixed disk requires revision AA of ACS PCBA P/N 903379 when installed on MPx 7xxx/8xxx systems. TDP (PDC) controller P/N's 903217 and 903453 require IC's OTHER THAN Signetics (indicated by a bold 'S') at locations 9E and 10K (74S240). 3) The 250MB (aka M280) SCSI 5-1/4 inch disk drive requires n.6C OS or above and the -002 (mandatory revision) DMA-II. 4) The 364Mb (aka M380) SCSI 5-1/4 inch disk drive requires n.6G OS or above and the -002 version of the DMA-II. See MCS/M and DMA-II for other requirements on the system that it will be installed on. 5) The 690MB (aka M760) SCSI 5-1/4 inch disk drive requires n.6G OS or above and the -002 version of the DMA-II. See MCS/M and DMA-II for other requirements on the system that it will be installed on. 6) The 1.6GB (aka P1-17S) SCSI 5-1/4 inch disk drive requires n.7B OS or above and the -002 version of the DMA-II. See MCS/M and DMA-II for other requirements on the system that it will be installed on. 5.7 HARDWARE FLOW CONTROL With the M6H and above releases, the 16-way will support uni-directional hardware flow control. The 16-way that supports this feature is PN 903437-002, revision R or above. A new I/O cable will also be required for support of this feature, PN 916509, revision B. The device will be able to throttle the host, but the host will not throttle the evice. (This will cure the 'Data Loss' problem that occurs with ISP printers when they are turned off.) Flow control is implemented by monitoring the CTS signal of the interface. If CTS drops, the host will cease transmitting until CTS is detected or until a specified timeout has occurred. If the timeout occurs, a "timeout" error will be returned to the user. The timeout value is reset for each character transmitted. This means that if CTS drops multiple times during a transmission, 5 seconds (for example) will be allowed for each detection of CTS dropping. Hardware flow control is available for any serial device except for SPE.MODEM. Hardware flow control must be configured in TERM.CONFIG for it to be operational. Enter the extended options menu from the port main menu and the SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg029 option will appear: USE CTS FLOW CTL (Y/N) Enter a 'Y' to have the system recognize CTS flow control for this device. Hardware flow control requires a new cable; 916509-xxx (Rev. B). This cable comes with a 15 pin connector designed to be attached to the backpanel serial connector. 6.1 GENERAL INFORMATION IMPORTANT NOTE 1: AS OF RELEASES 9/8.6C, POSITIONING OF THE O.S. AND WCS SLOTS HAVE BEEN ADJUSTED SLIGHTLY. THEREFORE, O.S./WCS LEVELS PRIOR TO 9/8.6C CANNOT RESIDE IN SLOTS ON THE SAME DISK WITH RELEASE LEVELS 10/9/8.7B. IMPORTANT NOTE 2: THE .SYSDATA.SECURITY.DATA FILE SHOULD BE SAVED BEFORE UPGRADING TO 10.7B/9.7B/8.7B IF YOUR CURRENT RELEASE IS BELOW 9/8.6C. AS OF RELEASES 9/8.6C, THE SECURITY.DATA FILE HAS A NEW FORMAT AND IS NOT TRANSPORTABLE TO RELEASES PRIOR TO 9/8.6C. IMPORTANT NOTE 3: IT IS NOT EXPECTED THAT A DOWNGRADE FROM 10/9/8.7B WILL BE NECESSARY. HOWEVER, IF A DOWNGRADE IS PERFORMED TO A RELEASE PRIOR TO 9/8.6C *11, THE USER'S FILES MUST BE TRANSPORTED TO THE OLDER O.S. LEVEL VIA EXTTAPE, MCSI, FTF, TBC, or ATP. FAILURE TO DO SO WILL RESULT IN INCOMPATIBLE FILE CONTROL SEGMENTS. THE VOLUME LABEL MUST ALSO BE REWRITTEN ON THE OLDER O.S. LEVEL. THERE ARE NO RESTRICTIONS ON A DOWNGRADE TO 9/8.6C *11. IMPORTANT NOTE 4: THE FORMAT OF THE .SYSDATA.TERMINALS.DEF1 AND .SYSDATA.TERMINALS.DEFN2 FILES WERE CHANGED ON 8/9/10.6H. IF YOUR CURRENT RELEASE IS PRIOR TO 8/9/10.6H THEN THESE FILES SHOULD BE SAVED IN CASE A DOWNGRADE IS NECESSARY. IMPORTANT NOTE 5: THE FORMAT OF SOME OF THE .SYSDATA.SPL. FILES WERE CHANGED ON 8/9/10.6H. IF YOUR CURRENT RELEASE IS PRIOR TO 8/9/10.6H THEN THESE FILES SHOULD BE SAVED IN CASE A DOWNGRADE IS NECESSARY. ALSO, DUE TO THESE CHANGES, 8/9/10.6H AND ABOVE MAY NOT RESIDE ON THE SYSTEM WITH PREVIOUS OS LEVELS. ############################################################ # # # IF UPGRADING A SYSTEM TO *.7B FROM A RELEASE, PRIOR TO # # 8/9/10.6H. THE UTILITY TERM.CONFIG MUST BE EXECUTED TO # # CONVERT THE TERMINAL DEFINITION FILES TO THEIR NEW # # FORMAT. PLEASE SEE THE UPGRADE SECTION FOR DETAILS. # # # ############################################################ ************************************************************ * * * IN THE FOLLOWING INSTALLATION INSTRUCTIONS, THE * * REFERENCES TO ".R7Bxx" SHOULD BE REPLACED BY THE ACTUAL * * RELEASE LEVEL THAT IS FOUND ON THE LABEL OF THE OS TAPE.* * * ************************************************************ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg030 The upgrade can be done in one of three ways depending on how the system is configured now: 1) A new system 2) Upgrade from 8.4D and below 3) Upgrade from 8.4E and above to *.7B Each of these methods share common steps in the upgrade. Below is a chart showing the flow of steps from each upgrade: ============================================================ INSTALLATION FLOW CHART --------- --------- --------- | | | | | | | NEW | | UPGRADE | |UPGRADE84| | | | | | | --------- --------- --------- | | | | | PRELIMINARY PREPARATION |<----------------------|<---------------------| | ALT LOAD | |------------------------------ CHANGE VOLUME LABEL | | | | | UPDATE FAMILY INFORMATION | | |UPGRADE | | INITIALIZE FAMILY | | | |<----------------------------| CHANGE INSTALLATION PARAMETERS | | RESTORE OS | | UPGRADE84 INSTALL CONFIG RECORD |----> NEW FILESYSTEM CONVERSION | |------------------->| | |<---------------------------------------------------<| UPDATE REMAINING SLOTS | | UPDATE COMPLETE ============================================================ Using this chart, any upgrade can be accomplished quickly and easily. In each section, watch for underlined text as these will be special instructions for a particular upgrade method. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg031 These Installation Instructions assume that the reader is familiar with BOSS/VS installation procedures and TYPE 3 LOAD Special Functions. For further information, see the BOSS/VS INSTALLATION GUIDE, M5138. If you have just received a new system, please note the following: new systems are shipped with the operating system installed on the disk, and the TYPE 3 LOAD (Special Functions) parameters already set up. If you wish to change the disk/family information on your new system, you must run Option 2 (Update Family Information) of INITIALIZATION OPTIONS (OPTION 2 on the main menu) in a TYPE 3 LOAD. For further information on setting up families on your system, see the BOSS/VS INSTALLATION GUIDE, M5138. Beginning with release 9.6A/8.6A there is a change in the way terminals are enabled for user log-on at system load time. Initial enabling of the TERMINALS group, which allows users to log-on, is now under user control through the use of the Startup Command File. If the file does not exist, the TERMINALS group is enabled automatically. Refer to Section 6.10 for further information on the startup command file and startup procedures for JOB MANAGER, MAGNET, and the SPOOLER. Since the operating system can be released on 1/2" (reel) or 1/4" (cartridge) tape, the word "tape" means either media form. The names of the files that are loaded into the OS/WCS slots are generic in order to simplify installation procedures. The first letter of the name will designate the machine type as follows: A - MPx 9xxx Machine Type B - MPx 8xxx/7xxx Machine Type C - ADVANCED SERIES Machine Type U - Universal Disk Image Format The second letter of the name will be used to designate the boot image type as follows: C - 1/4 inch Cartridge Tape Boot Image D - 1/2 inch Diagnostic Tape Boot Image Load f Execute T - 1/2 inch Tape Boot Image Load f Copy V - Universal Disk Image Format The third letter, if present, will be used to designate the Micro Peripheral Controller WCS images and the four REMIDI image formats, as follows: A - First REMIDI Module B - Second REMIDI Module C - Third REMIDI Module D - Fourth REMIDI Module M - Micro Peripheral Controller SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg032 FILE_NAMES BOSS/VS IMAGES .R7Bxx.INST.OS.CT 1/2 Inch Tape Boot, ADVANCED SERIES .R7Bxx.INST.OS.CC 1/4 Inch Tape Boot, ADVANCED SERIES .R7Bxx.INST.OS.AT 1/2 Inch Tape Boot, MPx 9xxx .R7Bxx.INST.OS.AC 1/4 Inch Tape Boot, MPx 9xxx .R7Bxx.INST.OS.BT 1/2 Inch Tape Boot, MPx 8xxx .R7Bxx.INST.OS.BC 1/4 Inch Tape Boot, MPx 7xxx .R7Bxx.INST.OS.UV Universal Disk Boot Image, MPx/ADVANCED SERIES DEMON IMAGES .R7Bxx.DIAG.DEMON.CC 1/4 Inch Tape Boot, ADVANCED SERIES .R7Bxx.DIAG.DEMON.CD 1/2 Inch Tape Boot, ADVANCED SERIES .R7Bxx.DIAG.DEMON.AD 1/2 Inch Tape Boot, MPx 9xxx .R7Bxx.DIAG.DEMON.AC 1/4 Inch Tape Boot, MPx 9xxx .R7Bxx.DIAG.DEMON.BD 1/2 Inch Tape Boot, MPx 8xxx .R7Bxx.DIAG.DEMON.BC 1/4 Inch Tape Boot, MPx 7xxx .R7Bxx.DIAG.DEMON.UV Universal Disk Boot Image, MPx/ADVANCED SERIES REMIDI MPx 7xxx/8xxx IMAGES .R7Bxx.DIAG.REMIDI.BDM 1/2 Inch Tape Boot, MPC/LAN .R7Bxx.DIAG.REMIDI.BCM 1/4 Inch Tape Boot, MPC/LAN .R7Bxx.DIAG.REMIDI.BVM Disk Boot Image, MPC/LAN .R7Bxx.DIAG.REMIDI.BD 1/2 Inch Tape Boot, CPU .R7Bxx.DIAG.REMIDI.BC 1/4 Inch Tape Boot, CPU .R7Bxx.DIAG.REMIDI.BV Disk Boot Image, CPU REMIDI MPx 9xxx IMAGES .R7Bxx.DIAG.REMIDI.ADA 1/2 Inch Tape Boot Module 1 .R7Bxx.DIAG.REMIDI.ADB 1/2 Inch Tape Boot Module 2 .R7Bxx.DIAG.REMIDI.ADC 1/2 Inch Tape Boot Module 3 .R7Bxx.DIAG.REMIDI.ADD 1/2 Inch Tape Boot Module 4 .R7Bxx.DIAG.REMIDI.ACA 1/4 Inch Tape Boot Module 1 .R7Bxx.DIAG.REMIDI.ACB 1/4 Inch Tape Boot Module 2 .R7Bxx.DIAG.REMIDI.ACC 1/4 Inch Tape Boot Module 3 .R7Bxx.DIAG.REMIDI.ACD 1/4 Inch Tape Boot Module 4 .R7Bxx.DIAG.REMIDI.AVA Disk Boot Image for Module 1 f 2 .R7Bxx.DIAG.REMIDI.AVC Disk Boot Image for Module 3 f 4 REMIDI ADVANCED SERIES IMAGES .R7Bxx.DIAG.REMIDI.CD 1/2 Inch Tape Boot Module 1 through 4 .R7Bxx.DIAG.REMIDI.CC 1/4 Inch Tape Boot Module 1 through 4 .R7Bxx.DIAG.REMIDI.CVA Disk Boot Image Module 1 f 2 .R7Bxx.DIAG.REMIDI.CVC Disk Boot Image Module 3 f 4 WCS FILES .R7Bxx.INST.WCS.C WCS for ADVANCED SERIES .R7Bxx.INST.WCS.A WCS for MPx 9xxx .R7Bxx.INST.WCS.B WCS for MPx 8xxx/7xxx SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg033 6.2 NEW OPERATING SYSTEM INSTALLATION Follow the instructions in this section if you are creating a SYSTEM disk on a newly formatted disk, or if you are changing a DATA disk to a SYSTEM disk. GO TO SECTION 6.5 TO BEGIN NEW OS INSTALLATION 6.3 UPGRADING TO 9.7B If you are installing the 9.7B O.S. on a newly formatted System disk or changing a Data disk to a System disk, go to the section above. If you are upgrading a 7xxx or 8xxx Series System to a 9xxx Series System, you must first run for a minimum of one week on O.S. 8.6A or above before the hardware upgrade. A new configuration record is required when upgrading to 9.7B from 9.6 O.S. levels. A new configuration record is also required when an upgrade includes new hardware. NOTE: If upgrading from 8/9/10.6H, then you may skip this paragraph. The terminal configuration files changed with 8/9/10.6H. If upgrading from a release prior to 8/9/10.6H then these files must be converted. To convert the terminal configuration files, when the system is reloaded, enter the terminal configuration utility TERM.CONFIG. A message will be displayed that the terminal files are being converted. When this is complete the system needs to be reloaded for the configuration to take effect. UNTIL THIS CONVERSION AND REBOOT IS DONE, TERMINALS AND PRINTERS WILL NOT BE ACTIVE. NOTE: It is essential that the .SYSDATA.SECURITY.DATA file be backed up before upgrading to *.7B, if your current O.S. level is below *.6C. This SECURITY.DATA file will go through a conversion during the upgrade, and the converted file cannot be used on previous O.S. levels. The old version of SECURITY.DATA should be saved in case an O.S. downgrade is ever necessary. NOTE: The format of he .SYSDATA.TERMINALS.DEFN1 and .SYSDATA.TERMINALS.DEFN2 was changed on 8/9/10.6H. If the current release is below 8/9/10.6H, then please save these files in case a downgrade is necessary. NOTE: The format of some of the .SYSDATA.SPL. files was changed on release 8/9/10.6H. If the current release is below 8/9/10.6H, then please save these files in case a downgrade is necessary. Also, due to these changes, 8/9/10.6H and above may not reside on the same system with previous OS levels. 6.3.1 PRINTING OUT THE TERMINAL CONFIGURATION INFORMATION When upgrading from MPx 7xxx/8xxx Series Systems to the MPx 9xxx Series Systems, it is necessary to reference the terminal configuration in order to properly re-address the 9xxx controllers. Therefore, you must print out a SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg034 copy of the terminal configuration information before upgrading. 1. Enter the TERM.CONFIG utility. 2. Select OPTION 2 DISPLAY A CONFIGURATION FILE. 3. When the following screen is displayed, enter these responses to the prompts: CONFIGURATION FILE: P OUTPUT DEVICE: DETAILED REPORT: Y ENTRIES CORRECT: Y The terminal configuration information should now be printed. 6.3.2 SAVING FILES TO TAPE Current files must first be backed up to tape, using the standard tape utility, SAVERESTORE. When saving files to tape, send the output from the save process to the printer. This will provide a record of backup for each file. Also it is recommended that all tapes be compared to the files on the disk. NOTE: It is essential that the .SYSDATA.SECURITY.DATA file be backed up before upgrading to 9.7B, if your current O.S. level is below 9.6C. This SECURITY.DATA file will go through a conversion during the upgrade, and the converted file cannot be used on previous O.S. levels. The old version of SECURITY.DATA should be saved in case an O.S. downgrade is ever necessary. GO TO SECTION 6.5 TO BEGIN UPGRADE TO 9.7B 6.4 UPGRADING FROM RELEASE LEVELS 8.4D AND BELOW NOTE: This section contains references to the FILESIZE, NFSCONVERT, and DISKANALYZER utilities. Further information on these utilities and their use during file conversion can be found in the following sources: - BOSS/VS FILE CONVERSION GUIDE, M5185 - BOSS/VS UTILITY USER GUIDE, M5102 - Software Announcements for release levels 8.4E and 8.5A/B/C/D - HELP SCREENS accessed by keying in UTILITYNAME.HELP in command mode Since release levels 8.4E and above contain new file formats and a new file system, conversion of files is required to make files compatible with the new file system if you are upgrading from a software release level of 8.4D or below. The file conversion can be done in two ways: A) From tape to disk B) From disk to disk Which method used depends on the configuration of the system. The disk to disk method is preferable for a system SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg035 with removable disks. The disk to disk method involves upgrading the system disk with the new O.S. Then the system disk can be used to convert other disks by using the NFSCONVERT utility to convert one file from one disk to another. If the disk to disk method is used on fixed disks, any user files must be copied from the fixed system disk to another disk or to tape for conversion. This is because the system disk must be initialized and updated to the new O.S. to do the conversion. To do a tape conversion, a save and restore is performed with the SAVERESTORE utility in the normal manner. The conversion process is invisible to the user with the exception of the following status message that is displayed during conversion: "Now converting to NFS format...." The tape conversion requires about 4 minutes per megabyte of data. The installation procedure is broken into two parts: A) Preliminary evaluation B) Operating System upgrade and file conversion The preliminary evaluation is required to ensure that proper hardware and file preparation is done. An O.S. upgrade from releases of 8.4D and below entails loading of the 8.7B O.S. and converting files to their new format. In large configurations, the conversion process will take more than one day. At the end of this section is an upgrade and conversion checklist that should be used to track progress through the upgrade procedure. 6.4.1 HARDWARE EVALUATION All hardware must be checked for proper operation. All boards must be at proper revision levels (see the HARDWARE Section 6 in this announcement). Ensure that all tape units are operating correctly. 6.4.2 FILE PREPARATION Obtain a directory listing with partial attributes for each family in the system. This listing will help you to find files, if any, that need repair before conversion. Next, using DISKANALYZER, select the option "VALIDATE ALL FILES" to determine which files need repair. Files which have the following attributes MUST be repaired before they are saved to tape: A) Files which lack integrity. B) Files which have lost space. C) Non-serial files in which records used is greater than records defined. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg036 D) Files that have invalid format. These files can be located in several ways: A) Scan the directory listing noting any files flagged as lacking integrity. B) Use the report generated by the DISKANALYZER "VALIDATE ALL FILES" option. (Preferred method) C) Use the utility FINDLOSTSPACE (8.4C/D only). All of the above methods should be used to find files that lack integrity and that have lost space. However, the directory listing must be scanned to find files that have a greater number of records used than defined as maximum records. This is a very important step. Any file possesing any of these attributes WILL NOT convert. properly. They have to be repaired on a previous release before conversion. Any EDITOR recovery files must be recovered or deleted before conversion. The recovery files are identified by the node ED.REC. After the node, there will be a series of digits. These files can be found by scanning the directory listing. These files must be recovered by using EDIT.RECOVER or deleted by using the DELETE utility. ***************************************** * * * ALL FILES MUST BE FREE FROM LACK OF * * INTEGRITY, LOST SPACE, AND MAX * * RECORDS GREATER THAN DEFINED RECORDS. * * FILES WILL NOT BE CONVERTED IF THEY * * POSSESS ANY ONE OF THESE ATTRIBUTES. * * * ***************************************** 6.4.3 NEW FILE SYSTEM SPACE REQUIREMENTS The space required for files under the new file system is about the same as under 8.4D/C/B/A levels. However, it is recommended that a listing be obtained which displays the files and their new sizes. On the 8.4D release, the program FILESIZE is used to produce this listing. The program FILESIZE will display the file size under the new file system for each file in a given family. It will also display the total number of sectors required by the entire family under the new file system. 6.4.4 SAVING FILES TO TAPE User files and the .SYSDATA. node must now be backed up to tape. It is STRONGLY recommended that these files be saved to tape even if disk to disk conversion is being used. This will allow recovery of files in case there are problems with the disk to disk conversion. It is necessary to save the .SYSDATA. node to preserve all system parameters. This node must be restored on the new file system along with the user files. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg037 It is essential that the .SYSDATA.SECURITY.DATA file be backed up before upgrading to 8.7B and saved for a period of time on tape. This SECURITY.DATA file will go through a conversion during the upgrade, and the converted file cannot be used on previous O.S. levels. The old version of SECURITY.DATA should be kept in case you need to perform an O.S. downgrade. The files are saved using the standard tape utility, SAVERESTORE. When saving files to tape, send the output from the save process to the printer. These will provide a record of backup for each file. Also it is recommended that all tapes be compared to the files on the disk. When using the tape or disk conversion, the conversion requires temporary disk space to sort keyed (direct and sort) files. The space required varies with the number of records and the size of the key. To ensure proper space is available, the following steps should be observed: A) Do not restore the user default family until last. B) Convert large keyed files first. Step A ensures that the default user disk has a large amount of free space since this is where the tape and disk conversion utility efines the temporary files. Step B allows the files that require the most amount of temporary space to be converted first. To convert large keyed files first, they must be saved to tape first. The large keyed files can be identified by scanning the directory listing obtained in Section 6.4.2. If using disk to disk conversion, the NFSCONVERT utility allows you to convert keyed files first. 7xxx/8xxx UPGRADE AND CONVERSION CHECKLIST 1) Hardware levels => Section 6 2) Validate files => Section 6.4.2 A) DISKANALYZER option "VALIDATE ALL FILES" B) DIR listings C) FINDLOSTSPACE Utility D) Delete unwanted EDITOR, SPOOL, and TEMP files 3) New file sizes => Section 6.4.3 A) FILESIZE utility 4) Save files to tape => Section 6.4.4 A) Large keyed files first 5) Update operating system => Section 6.5 A) ALT-LOAD B) TYPE III - Options 1-4 C) Restore operating system files SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg038 6) File conversion A) Tape-to-disk => Section 6.7.1 B) Disk-to-disk => Section 6.7.2 7) Check file integrity 8) Complete installation A) Update terminal configuration file 6.5 INSTALLING THE OS - LOADING SLOTS 0 AND 1 USING ALT LOAD NOTE: ALT LOAD has been enhanced so that it will automatically load both slots 0 and 1 on a new installation. (WCS slots 2 and 3 are also loaded with the BOSS/VS WCS for formatting purposes only. The user needs to reload these slots with the REMIDI WCS files, using UPDATE.WCS sections on updating slots 2 and 3 in this announcement.) To perform an ALT LOAD from tape follow these steps: A) Mount the new release tape in the tape drive. (All front panel load select switches should be OFF if using tape drive 0. Switch 1 should be ON if using tape drive 1.) B) Press the "ALT LOAD" button on the front panel. First, a proprietary message will be displayed, and then the following load screen: ____________________________________________________________ Load PROM Version: x.x.x.x SYSTEM SERIAL NUMBER : 000-00000 Load Drive n SERIAL NUMBER CREATOR: 000-00000 WCS 0 Version: x.x.x CONFIGURATION CREATOR: 000-00000 OS 0 Version: 7.1.x.x CPUs ID #s : n Memory (Mb) : n.0 Disk Drives : n BOSS/VS LOAD FROM TAPE Tape Drives : n Printers : n HVDTs : n IMLCs : n Serial Ports: n Date Format MM/DD/YY: BMTCs : n/n DATE = MM/DD/YY: LAN Cntrlrs : n TIME = HH:MM:SS: SYSTEM PREFIX: (family).R7Bxx.SYS. System Default Family: (family) File System Write Through: T/F User Default Family : (family) Per-File Write Through : T/F Installation Name : (name) File System Security : T/F ____________________________________________________________ Key in the current DATE and TIME at the above prompts. The screen will then display: ____________________________________________________________ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg039 L O A D I N G . . . BOSS/VS Operating System Image Update Utility [version 7.1.x.x] OS/WCS information for drive n (nn): 0: ?????????????? ??????? | x x.x.x 1: ?????????????? ??.??.??.??? | ? ?.??.?? 2: -------------- -- -- -- --- | ????????? 3: ?????????????? ??????? | ????????? BOSS/VS Image File Name: (displays one of the following): OSN.CT0708xxxxx (ADVANCED SERIES) OSN.AT0708xxxxx (9x00 systems - 1/2-inch) OSN.AC0708xxxxx (9400 systems - 1/4-inch) OSN.BT0708xxxxx (8000 systems - 1/2-inch) OSN.BC0608xxxxx (7x00 systems - 1/4-inch) Target OS Slot (0/1/3) : '0' (or 1) Target WCS Slot (0-3) : '0' (or 1) Target Drives (0/1/All/Quit): (choose drive) ____________________________________________________________ C) The Image File Name will be displayed by the system. Enter '0' or '1' at the slot prompts to load O.S. and WCS slots 0 and 1. Enter '0', '1', or 'All' at the drive prompt to update the appropriate drives. NOTE: Do not update drive 1 if it is a DATA disk and is to remain so. The system will now display: ____________________________________________________________ Now updating WCS slot # n Update in progress: nn% Now updating BOSS/VS Image (displays one of the following): OSN.CT0608xxxxx (ADVANCED SERIES) OSN.AT0608xxxxx (9x00 systems - 1/2-inch) OSN.AC0608xxxxx (9400 systems - 1/4-inch) OSN.BT0608xxxxx (8000 systems - 1/2-inch) OSN.BC0608xxxxx (7x00 systems - 1/4-inch) Update in progress: nn% Image slot directory n/n:n Updates all complete. D O N E - R E A D Y F O R N O R M A L D I S K L O A D ____________________________________________________________ When O.S. and WCS slots 0 and 1 have been updated, reload the system by pressing the LOAD switch. IF UPGRADING FROM 8.4E AND ABOVE, THEN GO TO SECTION 6.6.4. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg040 6.6 TYPE 3 LOAD (SPECIAL FUNCTIONS) NOTE: If any disk has a 'MASTER' status, no update to the disk will be allowed. You must change the disk to a 'BACKUP' status in order to perform the TYPE 3 LOAD functions. To do this, select OPTION 4 (CHANGE MASTER/BACKUP STATUS) from the TYPE 3 LOAD main menu. Be sure to change the disk back to a 'MASTER' status after the TYPE 3 LOAD functions are completed (if this status is desired). This MASTER/BACKUP status is simply a flag which makes it possible to write-protect a disk. It is not to be confused with the disk configuration (e.g., SYSTEM, DATA, BACKUP) specified in Option 1 (Change Volume Label Information) of INITIALIZATION OPTIONS (OPTION 2 on the TYPE 3 LOAD main menu). Select OPTION 2 - INITIALIZATION OPTIONS Option 1 (Change Volume Label Information) must be done on all disks. Options 2 (Update Family Information) and 3 (Initialize Family Directory) must be done for each family. Option 4 (Change Installation Parameters) must be done on system disks only. 6.6.1 OPTION 1 (CHANGE VOLUME LABEL INFORMATION) All available disk drives will be displayed. An 'available' drive is any drive cabled to the system, whether enabled, disabled, powered ON or OFF. The selected drive entered in response to the Option 1 prompt must be online and ready. ENTER DRIVE NUMBER OF VOLUME LABEL TO CHANGE:______ (Enter volume label to change. The screen will change to display the information for only the drive whose volume label you choose.) SERIAL NUMBER (Enter CR to accept current serial number.) DISK CONFIGURATION (1=SYSTEM, 2=DATA, 3=BACKUP) ____ (Enter the appropriate disk type.) SIZE OF DUMP AREA.....______ x 1024 BYTES (For system disks only, enter the size of the dump area displayed on the line below this prompt as the area needed for both main memory and shared memory controllers. If installation of additional memory and/or shared memory controllers is planned, increase the dump area size to accommodate them. See Field Bulletin # 211, "Computing Dump Area Size".) FILE SYSTEM SPACE ______ x 1000 SECTORS (Enter the number displayed at the bottom of the screen for this prompt. The display will appear as SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg041 "CR=X" where X is the maximum space allowed.) UPDATE DISK VOLUME LABEL (Y/N) __ (Enter "Y" if above information is correct.) Repeat the steps in option #1 for all remaining disk drives. 6.6.2 OPTION 2 (UPDATE FAMILY INFORMATION) NOTE: Removable drives can only have one member per family. Fixed drives can be combined to create a larger capacity disk family. The disk information for all drives on the system is displayed and the cursor is positioned at 'FAMILY BASE DRIVE NUMBER'. FAMILY BASE DRIVE NUMBER ___ FAMILY NAME ______ (CR for default family name.) DRIVE NUMBERS OF OTHER DISKS IN FAMILY? (TYPE SPACES FOR NO OTHER DRIVES) (Enter all other drive numbers for this family or spaces if none. The drives must be fixed media drives.) UPDATE DISK (Y/N)? Repeat the steps in option #2 until all drives are identified in a family. 6.6.3 OPTION 3 (INITIALIZE FAMILY DIRECTORY) This option displays all base drives on the system. FAMILY BASE DRIVE NUMBER ______ (Enter drive number to be initialized.) INITIALIZE FAMILY? (Y/N) __ (CAUTION: Ensure that all data you want is backed up. This step will delete all data on the disk.) Repeat the steps in option #3 for all defined families. 6.6.4 OPTION 4 (CHANGE INSTALLATION PARAMETERS) NOTE: On newly formatted disks, the following message will be displayed: "CAN'T READ INITIALIZATION PARAMETERS FROM DISK. STATUS = (3,7,30,1), TO CONTINUE:" Just press and continue. Only SYSTEM disks will be displayed. DRIVE NUMBER _______ PRIMARY PREFIX __________________ (Enter (family).R7Bxx.SYS. '(Family)' is the family where the operating system files will reside.) SECONDARY PREFIX _______________ SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg042 (Enter (family).R7Bxx.SYS. '(Family)' is the family where the alternate OS/WCS image files reside for slot 1.) SYSTEM INSTALLATION NAME ________________ (Sets the default installation name for a specified system disk. Used only with MAGNET. Enter for default.) DEFAULT USER FAMILY NAME _____________ (Enter default user family.) SECURITY (E=ENABLED, D=DISABLED) ___ FILE SYSTEM WRITE THROUGH? (E=ENABLED, D=DISABLED) ___ WRITE THROUGH DEFAULT ON FILE CREATE (E=ENABLED, D=DISABLED):__ (This parameter specifies what the default write through will be on a file created through a BASIC file create or through the CREATE utility.) UPDATE DISK WITH INSTALLATION PARAMETERS? (Y/N) __ Display: INSTALLATION PARAMETERS SUCCESSFULLY WRITTEN TO DISK. (CR) TO CONTINUE: Repeat the steps in option #4 for any additional system disks. If you changed your disk from a 'MASTER' status to a 'BACKUP' status to do the TYPE 3 LOAD functions, change it back to a 'MASTER' status at this point. Reload the system by pressing the LOAD switch. Be sure you are loading from the drive where you wish to restore the operating system files. 6.6.5 RESTORING THE O.S. From a TYPE 2 LOAD, select the SAVERESTORE option. Once in SAVERESTORE, choose OPTION 2 RESTORE FILES FROM TAPE. The screen appears as in Figure 7-1. At the prompt for output device, enter a parallel printer so that a listing of the restore operation is produced. This listing can be used to make sure all files were restored correctly. On the next screen, at the prompt, "FILE SPECIFIERS", enter ".". Then enter twice. All system files will be restored to disk. Once all files are restored to disk, the message "AUTOMATIC COMPARE, CR TO CONTINUE" appears. This automatically rewinds the tape and begins the compare operation. This only occurs when the compare option is selected. When the compare is completed, enter a CTL-IV to return to the "SAVERESTORE" menu. Reload the system and enter a TYPE 1 LOAD. At this point it is necessary to install the System Serial Number (using GENSSN) on newly formatted disks and SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg043 DATA disks that you are changing to SYSTEM disks. You will need to call the Software Distribution Center for a key to enter during this process. After the SSN has been installed on system disks, reboot the system. Figure 7-1. SAVERESTORE Screen -------------------------------------------------------- RESTORE FILES TAPE SET.ID: DRIVE-NUM: REEL-NUM: PRIMARY PREFIX: (FAMILY).NODE. FILE TYPE (D/P/CR=ALL) COMPARE (CR=Y/N) DATE (MM/DD/YY) TIME (HH:MM) OUTPUT DEVICE (CR=VDT) DELETE EXISTING FILES (CR=Y) VERIFY (Y/CR=N) ENTRIES CORRECT (Y/N) -------------------------------------------------------- 6.6.6 INSTALLING THE CONFIGURATION RECORD It is necessary to install a new configuration record when installing a new system or when upgrading to 8.7B from 8.6 and lower O.S. levels or when changing systems. Until the following procedure is completed, the system will have a minimum configuration. New systems normally already have a configuration record installed. If you have a new system, and you want to verify that the configuration record has been installed, run the CONFIG.MGR utility in a TYPE 1 LOAD. If the configuration record has already been installed, you may skip this section. Enter a TYPE 1 LOAD. Set your prefix to .SYSTEM.CONFIG. Using the SAVERESTORE utility, restore the new configuration record on tape onto your system. Execute the CONFIG.MGR utility. The CONFIG.MGR utility allows the user to update the system configuration record by installing a new configuration file. This utility displays the current and new configuration record. When "Y" is answered to the prompt "Install Configuration:", the new configuration is copied from the file ".SYSTEM.CONFIG.I(serial number)", to the special system area on disk. The new configuration takes effect at the next system load. For further details on the use of the CONFIG.MGR utility, see the 8.5D/9.5D Software Announcement #139, or the BOSS/VS Utility User Guide, M5102. The configuration record file name is derived from the SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg044 system serial number by changing the leading "8" to an "I" and adding the prefix ".SYSTEM.CONFIG.". EXAMPLE: .SYSTEM.CONFIG.I1030114 for SSN 810-30114 This configuration record tape should be saved, in case re-installation should become necessary. Before going to the next step, LOAD the system so the new configuration record will take effect. If you do not load the system, you will have a minimum configuration and the system will be very slow. IF UPGRADING FROM 8.4E OR ABOVE OR A NEW INSTALLATION THEN GO TO SECTION 6.8. 6.7 CONVERTING FILES If doing tape to disk conversion see Section 6.7.1. If doing disk to disk conversion see Section 6.7.2. 6.7.1 TAPE TO DISK CONVERSION Mount the first tape to restore, enter the SAVERESTORE utility, and select option #2. A screen as in Figure 7-1 will appear. Answer all prompts as in the figure. Make sure that you direct the output to a printer. This will provide you with a "history" of the restore operation. Each file is converted to the new file format as it is restored. The conversion to the new file format will be entirely invisible except for a pause at the completion of restoring a file. This pause, which can last a few seconds to a few hours depending on file size, indicates the file is being converted to the new file format. Occasionally the message "...CONVERTING FILE TO NFS..." will appear as a visual indicator of file conversion. System files from the previous release need not be restored. However, to preserve all system parameters, the .SYSDATA. node must be restored from the backup tapes. Tapes made on releases of 8.4D and below cannot be compared when restored to the new file system. After all files have been restored, reload the system so the SECURITY.DATA file will be converted to the new 9/8.7B format and the terminal definition files will take effect. 6.7.2 DISK TO DISK CONVERSION The utility NFSCONVERT is used to convert files from the old format to the new file format. The destination disk must be in new file system format as described in section "TYPE3". The source disk must be in the old file system format. When using disk to disk conversion, only one family may be converted per terminal. You cannot start NFSCONVERT on two terminals converting different parts of the same family, however you can convert different families at SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg045 the same time. As in the tape to disk conversion, the .SYSDATA. node must be converted to preserve system parameters and configurations. 6.7.3 CHECK FILES Once all files have been converted, the DISKANALYZER "VALIDATE ALL FILES" option should be performed on each family. DISKANALYZER can be used in a TYPE II load or a TYPE I load. Once all files have been validated, enter a TYPE I load, (if you have not already done so). 6.7.4 UPDATING THE TERMINAL CONFIGURATION FILE The terminal configuration file must be updated to the new file system format. This update will allow all other devices to become accessible. The file is updated by entering TERM.CONFIG and choosing the update option. Enter PRIMARY ISDC exit the update without changing anything. The utility will say that the file has been modified and ask if you system to allow the devices to become active. 6.8 UPDATING THE OTHER SLOTS This section will describe how to update the other slots on the disk. Instructions are different for each system type. Using the chart below, you can find the section needed to install the other slots: 7xxx and 8xxx 6.8.1 9xxx 6.8.2 ADVANCED SERIES 6.8.3 6.8.1 UPDATING SLOTS 2 & 3 ON 7XXX AND 8XXX SYSTEMS NOTE: If question marks (?/?) ever appear for Load Sector 2 at the top of the OSINFO screen, it is necessary to run UPDATE.LD for REMIDI. O.S. and WCS slots 2 and 3 are updated by using the UPDATE.OS and UPDATE.WCS utilities in a TYPE 1 LOAD. To run these utilities, you must set your prefix to the .R7Bxx.INST. 6.8.1.1 UPDATING WCS SLOT 2 REMIDI version BV includes all the micro-diagnostics except MPC and LAN controller micro-diagnostics. It is placed in WCS slot 2 and is used for testing on all 7000/7100 and 8000 Series Systems. !UPDATE WCS ENTER WCS SLOT (0..3: 2 AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE: (choose disk) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg046 WCS IMAGE FILE: .R7Bxx.DIAG.REMIDI.BV WCS LEVEL OF WCS IMAGE FILE: (level displayed) UPDATING DISK UNIT nn SECTOR xxx WCS UPDATE COMPLETED! 6.8.1.2 UPDATING WCS SLOT THREE (3) 6.8.1.2.1 ON 7000/7100 SYSTEMS AND 8000 SYSTEMS WITH LAN REMIDI version BVM contains micro-diagnostics for the LAN and MPC controllers. It is placed in WCS slot 3 on 7000/7100 Series Systems and on 8000 Series Systems with LAN controllers. The utility UPDATE.LD is used to update the Load Directory for Load Sector 2 to toggle between the two versions of REMIDI in WCS slots 2 and 3. The pointers in Load Sector 2 (displayed on the OSINFO screen) determine which diagnostics will run. !UPDATE.WCS ENTER WCS SLOT (0..3): 3 AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R7Bxx.DIAG.REMIDI.BVM WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE! 6.8.1.2.2 ON 8000 SYSTEMS WITHOUT LAN This slot will contain system WCS which is common to both the O.S. and DEMON. !UPDATE.WCS ENTER WCS SLOT (0..3): 3 AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE : .R7Bxx.INST.WCS.B WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 6.8.1.3 UPDATING O.S. SLOT THREE (3) The O.S. slot 3 will contain the O.S. for DEMON on both 7000/7100 and 8000 Series Systems. !UPDATE.OS BOSS/VS Image File Name: .R7Bxx.DIAG.DEMON.UV Target OS Slot (0/1/3) : 3 Target WCS Slot (0-3) : 0 Target Drives (0/1/All/Quit): (choose drive) NOTE: DEMON's O.S. with the WCS in slot 0. DEMON and the 8.7B O.S. share the same WCS. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg047 The system will now display: Update in progress: nn% Image slot directory n/n:n Updates all complete. Using the utility OSINFO, the slots information can be displayed. It should appear as in Figure 7-2. 6.8.2 UPDATING SLOTS 2 AND 3 ON MPX 9XXX SERIES SYSTEMS O.S. and WCS slots 2 and 3 are updated by using the UPDATE.OS' and UPDATE.WCS utilities in a TYPE 1 LOAD. To run these utilities, you must set your prefix to the .R7Bxx.INST. Figure 7-2. OPERATING SYSTEM INFORMATION OPERATING SYSTEM INFORMATION ------------------------------------------------------------ BOOT LEVEL : X.X.X.X LOAD SECTOR: 0 1 2 3 DISK 0 : 0/0 1/1 0/2 3/3 SERIAL # : XXX-XXXXX ------------------------------------------------------------ OS NAME OS LEVEL DISK:SLOT WCS LEVEL ------------------------------------------------------------ R 7B*xx xxxxxx 7.2.x.x 0:0 B x.x.x R 7B*xx xxxxxx 7.2.x.x 0:1 B x.x.x N/A 0:2 REMIDI B x.x.x DEMON 7.1.x.x 0:3 B x.x.x ------------------------------------------------------------ NOTE: OSINFO on 7000/7100 Series Systems and 8000 Series Systems with LAN will show the additional version of REMIDI in WCS slot 3. The load sector 3 should be 3/0 on these systems. 6.8.2.1 UPDATING WCS SLOT TWO (2) The first section of the 9xxx version of REMIDI will reside in this slot. !UPDATE.WCS ENTER WCS SLOT (0..3): 2 AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE: (choose disk) WCS IMAGE FILE: .R7Bxx.DIAG.REMIDI.AVA WCS LEVEL OF WCS IMAGE FILE: (level displayed) UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETED! 6.8.2.2 UPDATING WCS SLOT THREE (3) The second section of the 9xxx version of REMIDI will reside in this slot. !UPDATE.WCS ENTER WCS SLOT (0..3): 3 AVAILABLE DISK UNITS ARE: (displayed) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg048 DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R7Bxx.DIAG.REMIDI.AVC WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE! NOTE: After REMIDI has been installed, Load Sector 2 at the top of the OSINFO screen should reflect an O.S./WCS of 0/2. If 0/2 is not displayed for Load Sector 2, UPDATE.LD must be run to update the Load Directory. 6.8.2.3 UPDATING OS SLOT THREE (3) O.S. slot 3 will contain the O.S. for DEMON. !UPDATE.OS BOSS/VS Image File Name: .R7Bxx.DIAG.DEMON.UV Target OS Slot (0/1/3) : 3 Targer WCS Slot (0-3) : 0 Target Drives (0/1/All/Quit): (choose drive) NOTE: DEMON's O.S. with the WCS in slot 0. DEMON and the 10/9/8.7B O.S. share the same WCS. The system will now display: Update in progress: nn% Image slot directory n/n:n Updates all complete. If drive 1 is a system disk also, the operating system installation procedure must be repeated for this disk. Using the utility OSINFO, the slots information can be displayed. It should appear as in Figure 7-3. 6.8.3 UPDATING SLOTS 2 AND 3 ON ADVANCED SERIES SYSTEMS O.S. and WCS slots 2 and 3 are updated by using the UPDATE.OS and UPDATE.WCS utilities in a TYPE 1 LOAD. To run these utilities, you must set your prefix to the .R7Bxx.INST. 6.8.3.1 UPDATING WCS SLOT TWO (2) The first section of REMIDI will reside in this slot. !UPDATE.WCS ENTER WCS SLOT (0..3): 2 AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE: (choose disk) WCS IMAGE FILE: .R7Bxx.DIAG.REMIDI.CVA WCS LEVEL OF WCS IMAGE FILE: (level displayed) SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg049 Figure 7-3. OPERATING SYSTEM INFORMATION OPERATING SYSTEM INFORMATION ------------------------------------------------------------ BOOT LEVEL : X.X.X.X LOAD SECTOR: 0 1 2 3 DISK 0 : 0/0 1/1 0/2 3/0 SERIAL # : XXX-XXXXX ------------------------------------------------------------ OS NAME OS LEVEL DISK:SLOT WCS LEVEL ------------------------------------------------------------ R 7B*xx xxxxxx 7.2.x.x 0:0 A x.x.x R 7B*xx xxxxxx 7.2.x.x 0:1 A x.x.x N/A 0:2 REMIDI A x.x.x DEMON 7.1.x.x 0:3 REMIDI A x.x.x ------------------------------------------------------------ UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETED! NOTE: After REMIDI has been installed, Load Sector 2 at the top of the OSINFO screen should reflect an O.S./WCS of 0/2. If 0/2 is not displayed for Load Sector 2, UPDATE.LD must be run to update the Load Directory. 6.8.3.2 UPDATING WCS SLOT THREE (3) The second section of the ADVANCED SERIES version of REMIDI will reside in this slot. !UPDATE.WCS ENTER WCS SLOT (0..3): 3 AVAILABLE DISK UNITS ARE: (displayed) DISK TO UPDATE : (choose disk) WCS IMAGE FILE: .R7Bxx.DIAG.REMIDI.CVC WCS LEVEL OF WCS IMAGE FILE: (level displayed) Display: UPDATING DISK UNIT nn SECTOR xx WCS UPDATE COMPLETE 6.8.3.3 UPDATING O.S. SLOT THREE (3) O.S. slot 3 will contain the O.S. for DEMON. !UPDATE.OS BOSS/VS Image File Name: .R7Bxx.DIAG.DEMON.UV Target OS Slot (0/1/3) : 3 Target WCS Slot (0..3) : 0 Target Drives (0/1/All/Quit): (choose drive) NOTE: A '0' is entered for the WCS slot to associate DEMON's O.S. with the WCS in slot 0. DEMON and the 10/9/8.7B O.S. share the same WCS. The system will now display: Update in progress: nn% Image slot directory n/n:n SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg050 Updates all complete. If drive 1 is a system disk also, the operating system installation procedure must be repeated for this disk. Using the utility OSINFO, the slots information can be displayed. It should appear as in Figure 7-4. Figure 7-4. OPERATING SYSTEM INFORMATION OPERATING SYSTEM INFORMATION ------------------------------------------------------------ BOOT LEVEL : X.X.X.X LOAD SECTOR: 0 1 2 3 DISK 0 : 0/0 1/1 0/2 3/0 SERIAL # : XXX-XXXXX ------------------------------------------------------------ OS NAME OS LEVEL DISK:SLOT WCS LEVEL ------------------------------------------------------------ R 7B*xx xxxxxx 7.1.x.x 0:0 C x.x.x R 7B*xx xxxxxx 7.1.x.x 0:1 C x.x.x N/A 0:2 REMIDI C x.x.x DEMON 7.1.x.x 0:3 REMIDI C x.x.x ------------------------------------------------------------ 6.9 CONFIGURING UPD This section describes how to configure the new (available with 8/9/10.6H) printers: 4225, 4226, 4227 and 4228 printers for system use. Each of of these printers must have a PDF assigned to them to be used on the system. Below are the steps to assign these PDF's: Step 1) The PDF's and the translation files must be copied into the SYSDATA node. The PDF's are located in the INST node. These files can be copied using the copy command: COPY ().R7Bxx.INST.PDF.P42f,().SYSDATA.PDF.P42f COPY ().R7Bxx.INST.XLT.X42f,().SYSDATA.XLT.X42f Step 2) Next the printers must be configured to run under UPD. To do this, the utility TERM.CONFIG and the new utility PRCONFIG will be used, in that order. To do this: A) Determine the controller and the line that your printer is connected to. If unknown, then SYSINFO may be used to determine the controller and line number. B) Execute TERM.CONFIG, select the controller and line corresponding to the printer and configure the printer as UPD SERIAL. Set all other parameters as they would normally be set. C) Repeat step 2 for every UPD printer to be configured. The system must now be rebooted for the changes to take effect. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg051 Step 3) Execute the PRCONFIG utility, select the printer to be configured and fill in the remaining parameters: 1) The PDF name will usually be the letter "P" followed by the model number, e.g. P4225. Currently only two PDFS exist; use P4225 for the PT-4225 and PT-4226 printers. Use the P4227 forthe PT-4227 and the PT-4228 printers. 2) The translation name will usually be the letter "X" followed by the model number, e.g. X4225. Currently there is only one translation file, X4225. This translation file is used for all UPD printers. 3) Multi-buffering should be selected for printers running 600 LPM or faster. Multi-buffering consumes extra memory and will not boost performance of slower printers. 4) Enter 30 seconds for the read and write timeouts values. These values can be changed later if necessary. 5) The model number field is for informational purposes only and doesn't effect the functionality or usage of printer. Enter YES to the entries correct prompt if all entries are correct. Repeat step 3 for all UPD printers to be configured. (4225, 4226, 4227 and 4228 ) 6.9.1 Comments on UPD The PRCONFIG utility will build a file called PRINTERS.CONF in the SYSDATA node. It is built using the device name (e.g., P2) and the unit address (e.g., 2.4). The data in the PRINTERS.CONF file must agree with the data in the terminal definition files TERMINALS.DEFNx (maintained by TERM.CONFIG). At system load, one of four conditions can occur: 1) No entry for a particular unit address exists in PRINTERS.CONF but one does exist in TERMINALS.DEFNx. One is therefore created with standard printer driver defaults and entered into PRINTERS.CONF. 2) An entry for a particular unit address does exist in PRINTERS.CONF but one does not exist in TERMINALS.DEFNx. The entry in PRINTERS.CONF is removed. 3) An entry for a particular unit address exists in both PRINTERS.CONF and TERMINALS.DEFNx, but the device name differs, i.e., PRINTERS.CONF believes unit 4.3 corresponds to device P3, but TERMINALS.DEFNx has determined that it is really P2. The entry in PRINTERS.CONF is changed to P2, but all other configuration data remains unchanged. 4) An entry for a particular unit address exists in both PRINTERS.CONF and TERMINALS.DEFNx and the device names agree. In this case, everything is configured properly. A user built PDF requires a software key be installed for proper operation. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg052 6.10 SYSTEM STARTUP 6.10.1 STANDARD STARTUP COMMAND FILE The commands for the standard System Startup Command File are released in the file: .R7Bxx.SYS.START.CMD The standard commands are: !MAGNET.STARTUP !GROUP.CREATE SPOOLER,TYPE=SYSTEM !SPOOL P*,VERIFY=F,PAUSE=F !GROUP.ENABLE TERMINALS,VERIFY=F,PAUSE=F The name of the System Startup Command File actually used for startup is: (system-default-family).SYSDATA.START.CMD Part of 10/9/8.7B BOSS/VS system installation is to copy the released file to the .SYSDATA. node and make changes and additions as necessary. Note that the commands and parameters in this file must match the commands and parameters defined in the CLI command and function definition files for the individual system being installed. If the System Startup Command File is not found after a system load, then a default initialization is performed. This puts all printers into spooled mode and enables terminals. The following outlines the commands, some of the implications and details of the System Startup Command File method of system configuration. 6.10.2 COMMAND FILE DEFINITIONS MAGNET.STARTUP This command runs a released MAGNET program that does all of the startup operations required by the MAGNET subsystem. This command should be deleted if MAGNET is not part of the system configuration. GROUP.CREATE SPOOLER,TYPE=SYSTEM This command creates the SPOOLER Group that maintains the activity log files and Group statistics for the spooler subsystem. This command should come before the 'SPOOL P*' command. SPOOL P*,VERIFY=F,PAUSE=F This command puts all of the printers into spooled mode, and causes any eligible requests on the spooled printers to start printing. GROUP.ENABLE TERMINALS,VERIFY=F,PAUSE=F SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg053 This command enables the 'built-in' TERMINALS Group, and allows all users to logon to any terminals. This command is provided to allow the terminals to be enabled under user control. See below. NOTE: IF A SYSTEM STARTUP COMMAND FILE EXISTS, THIS COMMAND, OR SOME OTHER COMMAND TO ENABLE TERMINAL GROUPS, MUST BE IN THE SYSTEM STARTUP COMMAND FILE FOR USERS TO LOGON TO THE SYSTEM. In case he TERMINALS Group is disabled, a user with 'system operator' status can enable this group when attempting to logon to the system. This allows an operator to logon to the system in case the Startup Command File did not enable the TERMINALS Group, or the TERMINALS Group was left disabled by accident and all operators signed off the system. To enable the TERMINALS Group during logon the operator attempts to logon and ignores the 'Logon disabled' error messages and enters a 'CR' to continue. A prompt is displayed asking the operator if he wants to enable the TERMINALS Group. NOTE: THIS OPTION IS NOT AVAILABLE IF SOME OTHER TERMINAL TYPE GROUP IS ENABLED. ALSO, ONLY THE TERMINALS GROUP IS ENABLED, AND IT IS NOT CREATED IF IT DOES NOT EXIST. 6.10.3 IMPLICATIONS 1)Normal system startup is automatic. The system configuration options defined when the system was installed (placed into the System Startup Command File) are put into effect each time the system is loaded, with no further action by the user. These startup options may be modified by the user at any time, by editing the System Startup Command File. 2) Startup sequence is under user control. Users now have the ability to control the sequence of events at startup, after the internal startup sequence is complete. Users that do not need this level of control may ignore this feature. Some users may wish to run specific programs, and do recovery operations, before MAGNET and/or the SPOOLER are started up. This ability would be impossible if these subsystems were always started by the internal system initialization. 3) System recovery is possible before all users logon. This approach allows the operator to allow only specified terminals/users to logon after a system load. The System Startup Command File containing the single command: GROUP.CREATE , TYPE=TERMINAL, USERS=SYS.MGR, DEVICES=T0 would allow only the user 'SYS.MGR' to logon to terminal 'T0' after the system load. No other users could logon, SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg054 and no other activity would start. In this case the printers will be in suspended mode and MAGNET will not be initialized. When the system operator is finished with the recovery operations the 'normal' system configuration command file may be run by the operator to begin normal system processing. Again, users who do not need this level of control may ignore this feature. 4) Default startup with no System Startup Command File. When the TYPE 1 LOAD is complete, if the System Startup Command File is not found then 'default' startup conditions are in effect. In this case the system is available for any use. This mode is intended to support systems that want only these default startup options. The 'built-in' TERMINALS Group is enabled and allows all users to logon to any terminal. A system group named SPOOLER is created and the printers are put into spooled mode. The MAGNET subsystem is not activated. The following is a description of the details of the System Startup Job: When a TYPE 1 LOAD is performed, the last module to be initialized is the Job Manager (JMM). The final act of JMM is to run a batch job with a CLI command file. The files involved are: (system-default-family).SYSDATA.START.CMD (system-default-family).SYSDATA.START.IN (system-default-(family).SYSDATA.START.OUT SYSDATA.START.CMD is a sequential file that contains all of the startup commands; this is the System Startup Command File. The Job Manager looks in the system default family (only) for this file. SYSDATA.START.IN is a sequential file that contains any data that may be input by commands and programs in the above startup file. A read from standard INPUT will read records from this file. The Job Manager looks in the system default family (only) for this file. SYSDATA.START.OUT is a sequential file that contains the results of the startup command file. A write to standard OUTPUT by commands and programs will be placed into this file. The Job Manager deletes this file in the system family if it exists, prior to running the startup command file. If the startup file SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg055 (system-default-family).SYSDATA.START.CMD - or - (system-default-family).SYSDATA.START.CMD.TEXT is not found, the Job Manager will perform a default startup described above. If the startup file (system-default-family).SYSDATA.START.IN - or - (system-default-family).SYSDATA.START.IN.TEXT is not found, the Job Manager will attach a null file to startup INPUT; an End-Of-File will be returned for each read from standard INPUT. NOTE: THE SYSTEM STARTUP COMMAND FILE CONTAINS (ONLY) STANDARD CLI COMMANDS. A CLI command may be: 1) A CLI Command or Function (START, PREFIX, $WHERE,etc.) 2) A system utility (DIR, COPY, etc.) 3) The name of a program torun. 4) The name of another CLI command file. 6.11 DIAGNOSTIC REMOVAL This section describes the removal of diagnostic programs from a system. The diagnostics reside in the file system and several bootable disk slots. They are removed from the file system with the 'delete' utility. They are removed from the bootable slots by overwriting the images. The procedure follows. 1. Removing REMIDI The removal of REMIDI is accomplished by overwriting the two bootable REMIDI slots with the WCS image. 2. Update WCS Slot 2 Execute the UPDATE.WCS utility and respond to the prompts as shown below. ENTER WCS SLOT (0..3): - 2 AVAILABLE DISK UNITS ARE: - (displayed) DISK TO UPDATE : - Enter the disk number. WCS IMAGE FILE: - R7Bxx.INST.WCS.X (where X = A,B,C) X = A for MPx 9xxx X = B for MPx 7xxx, 8xxx X = C for Advanced Series WCS LEVEL OF WCS IMAGE FILE: - (displayed) During the update process, the following message appears: UPDATING DISK UNIT nn SECTOR xx SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg056 When the update is complete, the following message appears: WCS UPDATE COMPLETED! The preceding should be performed on all system disks. 3. Update WCS Slot 3 Execute the UPDATE.WCS utility and respond to the prompts as shown below. ENTER WCS SLOT (0..3): - 3 AVAILABLE DISK UNITS ARE: - (displayed) DISK TO UPDATE : - Enter the disk number. WCS IMAGE FILE: - .R7Bxx.INST.WCS.X (where X = A,B,C) X = A for MPx 9xxx X = B for MPx 7xxx, 8xxx X = C for Advanced Series WCS LEVEL OF WCS IMAGE FILE: - (displayed) During the update process, the following message appears: UPDATING DISK UNIT nn SECTOR xx When the update is complete, the following message appears: WCS UPDATE COMPLETED! The preceding should be performed on all system disks. 4. Removing DEMON The removal of DEMON is accomplished by overwriting the bootable DEMON slot with DEMON.UX. 5. Update OS Slot 3 Execute the UPDATE.OS utility and respond to the prompts as shown below. BOSS/VS Image File Name: - DEMON.UX Target OS Slot (0/1/3): - 3 Target WCS Slot (0-3) : 0 Target Drives (0/1/All/Quit): - Enter the disk number During the update process, the following message appears: Update in progress : x/y : zz% When the update is complete, the following message appears: Updates all complete. The preceding should be performed on all system disks. 6. Removing diagnostics from the file system The diagnostics are removed from the file system using the SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg057 'delete' utility. The diagnostics are found in the system node .R7Bxx.DIAG. The files in the following nodes should be deleted from the file system. .R7Bxx.DIAG. .ENHANCER7B. .TRACKER. The following files should be deleted: .AC (MPx 9000 series 1/4" tape boot OS image with DIVE) .AT (MPx 9000 series 1/2" tape boot OS image with DIVE) .BC (MPx 7000 series 1/4" tape boot OS image with DIVE) .BT (MPx 8000 series 1/2" tape boot OS image with DIVE) .CC (Advanced Series 1/4" tape boot OS image with DIVE) .CT (Advanced Series 1/2" tape boot OS image with DIVE) The following file(s) should be added as a replacement for the file(s) deleted above. .ACX (MPx 9000 series 1/4" tape boot OS image without DIVE) .ATX (MPx 9000 series 1/2" tape boot OS image without DIVE) .BCX (MPx 7000 series 1/4" tape boot OS image without DIVE) .BTX (MPx 8000 series 1/2" tape boot OS image without DIVE) .CCX (Advanced Series 1/4" tape boot OS image without DIVE) .CTX (Advanced Series 1/2" tape boot OS image without DIVE) This completes the diagnostic removal procedure! Software Announcement #193, dated 4/91 8/9/10.7A REVISION on MPx (Author: Kevin Liebl) Notes and Special Considerations for BOSS/VS Levels 10/9/8.7A dated 4/92 (Author: Joe Melendez) Install Instructions Patch 55 MPx, Document 916968, Section 2.1, The Patches. 2770/2780/3770/3780 Batch Emulator User Guide M5080C 3270 Pass-Through Reference Manual M5091A Business BASIC 90 Reference Manual M6262D BOSS/VS User Guide M5098H BOSS/VS Utilities User Guide M5102M 3270 Emulation Package Operator Guide for MAI 8000 Series M5129 File Transfer Facility User Reference Manual M6352A BOSS/VS Installation Guide M5138L System Site Planning Guide M0174A BOSS/VS Special Purpose Utilities User Guide M5151 BOSS/VS System Support Manual M5152 SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg058 Intersystem Transport Package User Guide M6354F MAI 8000 Series COBOL Reference Manual M5174 MAI 8000 Series COBOL User Guide M5175 BOSS/VS File Conversion User Guide M5185A MAGNET/VS User Reference Manual M6363 BOSS/VS 3270 BSC Emulation User Reference Manual M0170A ORIGINATOR: Joe Melendez SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB099 Pg059 FIB 00100 MAI COMPANY CONFIDENTIAL 05/12/94 *** BASIC writes to tape in lengths that are multiples of 4 *** BASIC writes to tape in lengths that are a multiple of 4, if the defined length is not a multiple of 4, nulls ($00$) are padded to the string to make it a multiple of 4. ex. 10 OPEN(1,SEQ=0)"R0" 20 DIM A$(1,$55$) 30 WRITERECORD(1)A$ 40 CLOSE(1) 50 OPEN(1,SEQ=0)"R0" 60 DIM B$(1024) 70 READRECORD(1)B$ B$ will now be a length of 4 and will = $55000000$ ORIGINATOR: Norm Jones SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB100 Pg001 FIB 00101 MAI COMPANY CONFIDENTIAL 08/18/94 *** Using "unattended backup" with 1.2GB 1/4" MCS *** Subject : Using "unatended backup" with new 1.2GB 1/4 MCS tape drive on MPX. Type : Informational Purpose : Inform the field of support of this tape drive using the "Unatended T3LD Online backup" for MPX systems. The "Unatended T3LD Online Backup" was supported only with the HCC tape drive on release M7B on MPX systems. MAI just announced a new 1.2GB 1/4 MCS tape drive and a customer wanted to use this tape drive in the "unatended" mode. The following information will provide how to make this new tape drive work on M7B release of MPX. These changes MUST be made if the MCS tape drive is the only tape drive on the system. If the system has more then one tape drive then the standard "Unatended T3LD Online Backup" programs will work without modification (for info on these programs please refer to the M7A software announcement). Make the following modifications to : ().ENHANCER7B.PSBU01 REM STATEMENTS 2520, 2540, 2550 ADD STATEMENTS : 2700 REM " ENTER VOL ID TO INITIALIZE (FOR SINGLE TAPE DRIVE ON SYSTEM)" 2720 GOSUB 6500 2740 WRITE(GHOST,ERR=2750)SETID$;GOTO 2800 2750 IF ERR<>13 GOTO 9000 2800 REM" ENTER "Y" TO INITIALIZE VOL ID" 2820 GOSUB 6500 2840 WRITE(GHOST,ERR=2850)"Y";GOTO 2900 2850 IF ERR<>13 GOTO 9000 Save these modifications. We did a test using the "Uantended T3LD Online Backup" between the HCC and the MCS tape drives. We backed up three 300 MBYT drives (COMPARE option set to NO) on our MPX 9000 system and we got the following timings : HCC backup took 1:20 to b/up these drives VS 1:53 for the MCS tape drive. IFR (Image File Recovery) took :57 minutes on the HCC VS 2:30 for the MCS tape drive (This was a worst case scenario, file was a MK file with 11 keysets, 11536 records used, 1101 bytes/record using 19407 total sectors with 5 extents, located on the third disk drive). NOTE : we will report the performance difference between these two tape drives to Engineering and to Marketing. Helpfull hints when using the "Unatended T3LD On-line backup" programs : 1. When using this software we suggest that you select "RESULT" as the output file and do not use the printer as the output device. If you have any problems with the backup you can run a program called DISPLAY which will read the RESULT file and show you all input/output of what the utility is doing and you can see where this is failing. 2. If you have a customer using this software we suggest that they write down all the disk setup information (like is it a SYSTEM or DATA disk, System dump area, File system size) so that if a disk drive has to be replaced you can setup the new drive with the correct information so that you do not have any problems trying to restore the backup. SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB101 Pg001 3. If you get rewind error or tape error we suggest that you first check the errorlog to see if it's reporting hard disk errors, next clean the tape heads, try with a new tape media and finally replace tape drive. 4. To restore a list of files from the backup you must first create a filelist using the !EDIT utility. This filelist must contain the full file name of the file on tape and the full file name of where you want this file to be restored. (Example : (DISK).JOE.FILE,(USER).JOSE.NEWFILE (The utility would look for the file on tape called (DISK).JOE.FILE and restore it to (USER).JOSE.NEWFILE)). You must do this for each file (specify SOURCE FILE & DESTINATION FILE) you want to restore in this filelist. To restore a full backup you must reboot the system in a T3LD. If you have any questions on using the "Unatended T3LD On-line backup" please call the MAI NSC. ORIGINATOR: Joe Melendez SOFTWARE-BASIC FOUR-BOSS/VS BBVIII & BBIX-----------FIB101 Pg002