MBF COMPANY CONFIDENTIAL FIELD INFORMATION BULLETIN SERVICE GROUP(S): MINI MFG: BASIC FOUR NACS TYPE(S): N005 MFG. MODEL(S): BOSS BBIV CATEGORY: SOFTWARE DESC: O.S. & UTILITIES *** TABLE OF CONTENTS AS OF 12/21/90 *** FIB 00001.Error 0, Error 47, false "PROCEDURE COMPLETED" - Release 4.208/03/81 FIB 00002.An Error 16 problem exists on BOSS releases 4.2A and 4.2B...09/09/81 FIB 00003.System locks up after power fail on release 4.2.............09/23/81 FIB 00004.Error 26 running file list maintenance on terminals TA thru 02/02/82 FIB 00005.Error 2 or Error 7 can be caused by utilities in 4.2A thru 402/02/82 FIB 00006.Problems with BOSS upgrade from level 3.X to level 4.X......03/15/82 FIB 00007."File Not Found"/no files restored on user defined restore -04/22/82 FIB 00008."Inadequate Disk Space To Restore" message on rel. prior to 05/11/82 FIB 00009.Error 41 using File Copy and Expand utility on releases 4.2 06/03/82 FIB 00010.System.halts while opening files on release 4.3B............08/12/82 FIB 00011.Software patch for Sector Analysis utility..................08/17/82 FIB 00012.Disk Error Analysis/Repair utility reports incorrect cylinde08/17/82 FIB 00013.Error 2 during multiple tape backup on release 4.3B.........09/24/82 FIB 00014.Patch to fix *MTC verify problem on BOSS release 4.3B.......02/07/83 FIB 00015.Data loss using streamer tape on release 4.4A...............04/12/83 FIB 00016.Files may be corrupted by file size increase/decrease utilit06/09/83 FIB 00017.Error 47 during 4.4B UPDATE procedure.......................06/09/83 FIB 00018.Releases 4.4A and 4.4B run slow during *MTC operations......07/19/83 FIB 00019.Cautions on using ctl-S and ctl-Q keys for stopping and star08/24/83 FIB 00020.System halts during initialization on release 4.5A..........09/23/83 FIB 00021.Error 12 instead of following SETERR statement - release 4.511/18/83 FIB 00022.Error 47 while running *MTC on releases prior to 4.5A.......12/01/83 FIB 00023.Early Track Closeout message on MTS utility - release 4.5A..02/27/84 FIB 00024.Long format list data incomplete (records management).......04/06/84 FIB 00025.Error 46 during select code summary or writing to a sort fil04/18/84 FIB 00026.SSBs to be aware of when returning to level 4.4B............04/20/84 FIB 00027.Error 47 after escape key to abort word processing printing.04/25/84 FIB 00028.Error 41 during records management of data file conversion..04/25/84 FIB 00029.Fixed media system hangs on release 4.5A at printer power on05/11/84 FIB 00030.CPU halts, CPU hangs or task hangs after "DELETE" is entered05/23/84 FIB 00031.Cpu halts, CPU hangs or tasks hang on any release prior to 406/04/84 FIB 00032.Causes of file system Error 11's............................07/02/84 FIB 00033.*MTC tape read check may fail to report failure on BOSS 4.4 07/13/84 FIB 00034.Prior to rel 4.5 printers give Error 0 printing EVDT U.C. "607/31/84 FIB 00035.Starting with rel 4.4B defective ports cause port shifting..12/07/84 FIB 00036.Release 4.5B Software Announcement..........................03/18/85 FIB 00037.Release 4.5B UPDATE procedure for removable media disks.....05/20/85 FIB 00038.Procedure to upgrade a Pre-level 4 fixed disk system to leve05/23/85 FIB 00039.Error 17 or Error 27 during MTS tape lable write on release 11/01/85 FIB 00040.Error 43 during 13XX to 2000 software conversion............05/22/86 FIB 00041.Error 47 using *COMM on release 4.5B........................06/16/86 FIB 00042.MPx to 13XX program transfer may cause ERROR 20.............07/07/87 FIB 00043.Date Changes to 01/01/83 after 1989 [ WPSF 599 ]...........02/22/90 SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------Table Of Contents Pg01 of 01 FIB 00001 08/03/81 *** Error 0, Error 47, false "PROCEDURE COMPLETED" - Release 4.2A *** The following are software patches for release 4.2A: 1. ERROR 47 during RESTORE: LOAD "*MTCRB Add the following statement: 0045 IF L$="" THEN READRECORD (1,IND=1)L$; LET L$=L$(7,16) SAVE "*MTCRB" 2. False "PROCEDURE COMPLETE" message on *MTC Restore: LOAD "*MTCRK" LIST 7120 Old: 7120 LET K$(17,3)=BIN(DEC(K$(1,3))+L,3),S$=P$(250,5); GOTO 7470 EDIT 7120 C[(250,5);]D[GOTO 7470][IF K$(1,3)=$000000$ THEN LET K$(1,3)=$ 000001$] New: 7120 LET K(17,3)=BIN(DEC(K$(1,3))+L,3),S$=P$(250,5); IF K$(1,3)=$ 000000$ THEN LET K$(1,3)=$000001$ Add the following statement: 7130 goto 7470 SAVE "*MTCRK" 3. ERROR 0 during backup LOAD "*MTCBA" Enter the following: 1610:;READ(7) (This appends ";READ(7)" to the end of statement 1610) SAVE "*MTCBA" ORIGINATOR: E. LYTE SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB001 Pg001 FIB 00002 09/09/81 *** An Error 16 problem exists on BOSS releases 4.2A and 4.2B *** SYMPTOM: There is an inherent problem in BOSS releases 4.2A and 4.2A. The symp- tom is an ERROR 16 after the systm has been idle for about 30 seconds. The problem is in the CACHE feature and was corrected in release 4.3A. FIX: There is no real "FIX" but here is a workaround: Start a terminal or ghost task with the following problem and let it run at all times. This will prevent the OS from "flushing" the cache. 0010 DIM A$(1024) 0020 FOR D=0 TO 8 0030 GET D,1,ERR=0040,A$ 0040 NEXT D 0050 WAIT 20 0060 GOTO 0020 ORIGINATOR: K. KANNEG SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB002 Pg001 FIB 00003 09/23/81 *** System locks up after power fail on release 4.2 *** After power up or power fail recovery, without re-loding BOSS, a system running release 4.2 will appear to be locked up if you attempt to escape or type on any terminal. After about 70 seconds, operation can commence normally. This is a normal condition with 4.2 BOSS. No system trouble shooting is necessary. ORIGINATOR: D. WEIDEMAN SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB003 Pg001 FIB 00004 02/02/82 *** Error 26 running file list maintenance on terminals TA thru TV *** SYMPTOM: An ERROR 26 occurs when trying to display a filelist using any terminal whose ID is greater than T9. FIX: LOAD "FLIST" LIST 1510 Old: 1510 GOSUB 2000; LET F5$=F4$,F4$(1,4)+STR(NUM(F4$(4,2))+1:"00") EDIT 1510 C[(]C[[$(]R[5] New: 1510 GOSUB 2000; LET F5$=F4$,F4$(1,4)+STR(NUM(F4$(5,2))+1:"00") SAVE "FLIST" ORIGINATOR: D. CHIODA SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB004 Pg001 FIB 00005 02/02/82 *** Error 2 or Error 7 can be caused by utilities in 4.2A thru 4.3A *** SYMPTOM: There exists a problem on levels 4.2A, 4.2B and 4.3A when using the Repair option of the File Analysis/Repair Utility if run on a file with no available records. The next available record pointer contains a record number that does not exist. If there is any activity to the file after using the above utility, ERROR 2 or ERROR 7 could occur. WORKAROUND: 1. Run the Repair utility against the effected file. This will ensure that all record pointers are correct except for the last one. 2. Expand the number of records in the file. 3. Run the Repair utility again. ORIGINATOR: E. OSEBOLD SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB005 Pg001 FIB 00006 03/15/82 *** Problems with BOSS upgrade from level 3.X to level 4.X *** The following is a list of considerations to be made before upgrading a system from any release 3 to any release 4. 1..Greater thn 128K total system memory on level 4 BOSS requires that the system have the "LIGHTNING" (Power Performance Option) feature. The standard speed CPU cannot address above 128K. 2. Fixed media disk drive systems cannot support more than 256K of memory. 3. If the new BOSS is adding DATAWORD II MDT's, one GHOST task must be config- ured for each MDT on the system. 4. Synchronous Communications option on level 4 reuires either on terminal task or one GHOST task. 5. Terminal T0 cannot be an "SPE" device. 6. Terminal T0 cannot be configured with a slave printer. 7. SECTOR CACHE feature requires 32K of system memory and the total system memory must be an increment of 32K. ORIGINATOR: B. GARDNER SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB006 Pg001 FIB 00007 04/22/82 *** "File Not Found"/no files restored on user defined restore - 4.3A *** There is problem with user defined restore procedures under level 4.3A. The symptoms are: 1. The restore procedures SEEM to run correcty and the message "PROCEDURE SUCCESSFULLY COMPLETED" is displayed. Yet, nothing is actually restored. 2. In the case of cataloged files, the catalog shows that the file is present, but *MTC cannot identify the file. The message "FILE NOT FOUND" is dsplayed. To resolve the problem, the "osCRIT" file should ALWAYS be included during the restore process. Releases 4.3 and up have this problem fixed. ORIGINATOR: D. FRATER SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB007 Pg001 FIB 00008 05/11/82 *** "Inadequate Disk Space To Restore" message on rel. prior to 4.3B *** When performing a restore from tape to disk on pre-level 4.3B system with a file that spans two or more tracks and the *MTC software returns the message "INADEQUATE DISK SPACE TO RESTORE THIS FILE", *MTC gives the operator the option to SKIP or ABORT. If the option to skip is taken, the system will encounter an ERROR 14. It is suggested that the restore be aborted and a selective restore of the remaining files be performed instead. Releases 4.3B and above contain the fix this problem. ORIGINATOR: D. FRATER SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB008 Pg001 FIB 00009 06/03/82 *** Error 41 using File Copy and Expand utility on releases 4.2 & 4.3 *** SYMPTOM: Error 41 can occur during the use of the FILE COPY AND EXPAND utility. FIX: LOAD "*XPAND" EDIT 3540C[));]D[DSZ<][IF R>] Line 3540 should now read: 3540 GOSUB 6000; CALL "*SPAC",ERR=9000,F8$,U1,U2,U3,K5; GOSUB 7500; LET R=2*DEC (F$(15,2)); IF R>1024 THEN LET R=1024 SAVE "*XPAND" LOAD "*KXPND" EDIT 3200C[I1=][1]D[4)]C[4]D[1] Line 3200 should now read: 3200 DIM K1$(1024); LET I1=1,U=1024,T1=S1+U1+U2,X=S1+U1-1,J1=1,L3=0,N3=1 SAVE "*KXPND" LOAD "*DXPND" EDIT 2110C[I1=][1]D[I1*][,I=] Line 2110 should now read: 2110 LET J1=0,N3=0,C2=1,C=R1-R,I1=1,I=1024,I2=I,K=1,X=S-I1,T1=DEC(F$(17,3)); SE LECT ASC(F8$(20)); OPEN(2,ISZ=I2)F8$(4,6); SELECT X9; DIM S1$(I2,$00$); L . ET C1=0; IF R>R1 THEN LET C1=R-R1 SAVE "*DXPND" ORIGINATOR: D. FRATER SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB009 Pg001 FIB 00010 08/12/82 *** System halts while opening files on release 4.3B *** SYMPTOM: Red light halt occurs when an attempt to open a file with a single character file name and the BLK= option is done on release 4.3B. Opening of a file without the BLK=option runs without any problems. The following line of code is an illustration of the problem: 0010 OPEN (1,BLK=1024)"A" FIX: No patch available. It is recommended that either single character names not be used or that the BLK= option not be used on single character named files. The problem will be fixed in a future release. ORIGINATOR: D. FRATER SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB010 Pg001 FIB 00011 08/17/82 *** Software patch for Sector Analysis utility *** SUBJECT: Disc error analysis/repair utility - level 4 errors in 'EXAMINE SECTORS' option. A programming error exists on Level 4 Disc Error Analysis by Sector. Due to rounding of the computed cylinder containing a defective sector, the program may cause the cylinder number to be incorrectly reported. Additionally, on fixed disc systems, the number of heads used in the cylinder calculation is incorrect and therefore the reported cylinder will be incorrect. The sector analysis program name is "*SECTA" and should be corrected as indicated: AS IS: 0010 REM "*SECTA""4.3-x"" SECTOR ANALYSIS (mm/dd/yy)JCG ... ... 2032 LET H=H+1; GET D,H*T+T,ERR=9100!B$; IF B$(2,1)>$00$ THEN GOTO 2032 2040 LET X=DSZ-256,N=INT(X/2048) ... ... 4010 LET E=ERR,Y$=BIN(TCB(3),2),X=G+I,M$=STR(X:"B#####0")+" "+STR(G/T:"###0")+ 4010:" "+STR(G/(T*H):"###0")+" "+STR(E:"#0")+" "+HTA(Y$)+" " ... ADD THE FOLLOWING STATEMENT: 2035 LET H=H+1 MODIFY STATEMENT 4010 AS FOLLOWS: EDIT 4010 C[/T]C[STR(][INT(]C[)][)] 4010 LET E=ERR,Y$=BIN(TCB(3),2),X=G+I,M$=STR(X:"B#####0")+" "+STR(G/T:"###0")+ 4010:" "+STR(INT(G/(T*H)):"###0")+" "+STR(E:"#0")+" "+HTA(Y$)+" " ORIGINATOR: J. RIPPL SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB011 Pg001 FIB 00012 08/17/82 *** Disk Error Analysis/Repair utility reports incorrect cylinder *** SYMPTOM: The DISK ERROR ANALYSIS/REPAIR utility can report failing cylinder number incorrectly if a failure occurs during the "EXAMINE SECTORS" option. PROBLEM DETERMINATION:LOAD "*SECTA" and LIST 2035 - If there is no statement 2035 then do the items listed under FIX: below. FIX: Enter: 2035 LET H=H+1 then press CR/ENTER Enter: EDIT 4010 C[/T]C[STR(][INT(]C[)][)] then press CR/ENTER Enter: SAVE "*SECTA" then press CR/ENTER ORIGINATOR: J. RIPPL SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB012 Pg001 FIB 00013 09/24/82 *** Error 2 during multiple tape backup on release 4.3B *** SYMPTOM: Error 2 during multiple tape backup, especially when backing up large files. The error occurs during the catalog procedure after the backup. FIX: LOAD "*MTCBF" DELETE 8200 Enter: 8200 READ(7,END=8205) Enter: 8205 WRITE RECORD (3,KEY=K$,END=1930)A$; LET L7=0 SAVE "*MTCBF" ORIGINATOR: P. SCHWINCK SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB013 Pg001 FIB 00014 02/07/83 *** Patch to fix *MTC verify problem on BOSS release 4.3B *** *** NOTE *** THIS PATCH APPLIES TO BOSS RELEASE 4.3B, PROGRAM *MTCBE ONLY SYMPTOM: Verified backup always fails, non-verified backup does not fail. The verified backup failure occurs only when a file that is being backed up spans two tracks. When a file track-san occurs, the *MTC programs cause the tape to perform a rewind. The problem is the program fails to increment the tape block counter on the special condition of a file continuation occuring at the same time as a track change. To correct the utility, install the following changes and line corrections: FIX: 1. Load program *MTCBE. 2. In statement 1070 change the ERR= clause to read ERR=8790 instead of ERR=8800. 3. Add the following line: 8790 IF ERR=72 THEN LET F1=F1+1 4. Enter SAVE *MTCBE and press CR/RETURN. ORIGINATOR: BASIC FOUR SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB014 Pg001 FIB 00015 04/12/83 *** Data loss using streamer tape on release 4.4A *** SYMPTOM: Data loss/corruption during MTS restore operation. FIX: Make the following changes to the BOSS: LOAD "*DSTPE" Enter: 0327 LET I9=S2-1 then press CR/ENTER Enter: EDIT 0530 C[E*S2-]D[,S2][I9] then press CR/ENTER SAVE "*DSTPE" ORIGINATOR: TIC SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB015 Pg001 FIB 00016 06/09/83 *** Files may be corrupted by file size increase/decrease utilities *** When increasing or decreasind the size of a data file, it is recommended that the "Record-By-Record" option be used on alll applicable level 4 utilities. There have been cases where the utilities have corrupted the keys and/or data records when the "Sector-By Sector" option was selected. ORIGINATOR: DONN CHIODA SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB016 Pg001 FIB 00017 06/09/83 *** Error 47 during 4.4B UPDATE procedure *** SYMPTOM: Error 47 at statement 5000, in program "*DWUD", during UPDATE procedure on release 4.4B. FIX: LOAD "*DWUD" EDIT 5000C[ ][IF LEN(V1$)<>0 AND LEN(V0$)<>0] SAVE "*DWUD" This problem was due to variables being null when DATAWORD II was not currently on the system. The above changes should be made prior to running the BOSS UPDATE utility for removeable disk systems. ORIGINATOR: D. CHIODA SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB017 Pg001 FIB 00018 07/19/83 *** Releases 4.4A and 4.4B run slow during *MTC operations *** The release of the 4.4A operating system includes enhancement to the *MTC utilities set. This allows the user to recover when a tape procedure is aborted or interrupted. This is a safety feature designed to help users expidite their overall system throughput. However, like all safety features, (such as verify), there is a certain degree of system overhead associated with its execution. Some users may have noticed an apparent "slowdown" of the 4.4A and 4.4B *MTC sostware. These observations are directly tied to the overhead of the added safety feature of the abort recovery logic. If the added overhead of the abort recovery logic greatly strains a particular customer, then two minor changes can be made to bypass the logic and increase the *MTC speeds by 15 to 40 percent. The changes are as follows: 1. LOAD "*MTCBE" DELETE 1162 Enter: 1162 WRITE(6,IND=0)P0$,C0$,I6,S,T,V,T9,S9;WRITE(6,IND=1);WRITE(6,IND=2)I$(4, 6);WRITE(6,IND=3)L$;WRITE(6,IND=4)T(0),T(0),T(1),T(2),T(3),T(4),T(5),T( 6),T(7),T(8),F,F1;WRITE(6,IND=5)B$+C4+V$+S$;WRITE(6,IND=6)K9$ SAVE "*MTCBE" 2. LOAD "*MTCEX" Enter: 0015 CALL "*ERAS",ERR=0020,"-MTCRS" SAVE "*MTCEX" The BOSS release 4.5A and those following have a new feature in the *MTC util- ities that allows the user to have the abort recovery active or inactive prior to the execution of any tape procedure. ORIGINATOR: D. FRATER SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB018 Pg001 FIB 00019 08/24/83 *** Cautions on using ctl-S and ctl-Q keys for stopping and starting *** Some Users have come to prefer the use of X-OFF and X-ON characters (CTL-S and CTL-Q respectively) for the purpose of stopping and re-starting a program list in process, and other keyboard or console mode functions. This practice should be discouraged, since the X-OFF/X-ON function is intended for suspeding output to an Asynchronous Communications Device (SPE) while it is being used as the destination of a PRINT or other directive. Use of X-OFF to suspend a LIST function on level 4.3B will suspend operation of the LISTER for all other tasks whether in console or program mode (a terminal being ESCAPEd will hang with no cursor while a task executing the LIST program directive will suspend execution with no apparent indication). Either will give an ERROR 5 when the task that issued the X-OFF issues X-ON. Later levels of BOSS have the X-OFF/X-ON functionality enhanced to lessen the chance of inter-action between tasks, however, it should be remembered that this function was meant for output control protocol rather than task control or console control. ORIGINATOR: J. VANDERHEYDEN SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB019 Pg001 FIB 00020 09/23/83 *** System halts during initialization on release 4.5A *** Certain configurations of BOSS release 4.5A have been found to halt during OS initialization. The problem appears to be releated to the DATAWORD 1 printer driver software, as the halt seems to occur only when a DW i printer is configured and then only when two or more 8-way controllers are installed. The halt occurs after the Proprietary Message is displayed and the reverse-video or lower case '8' appears on the VDT's. This is not a hardware problem. If this symptom occurs another BOSS release is required. ORIGINATOR: J. VANDERHEYDEN SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB020 Pg001 FIB 00021 11/18/83 *** Error 12 instead of following SETERR statement - release 4.5A01 *** The SETERR directive of release 4.5A01 may not execute as expected as it did in previous releases. In releases prior to 4.5A01, the program area of a task was . not cleared until a new program to be run was found in the system directory. In level 4.5A01 however, the RUN statement causes the task memory to be cleared before it attempts to run the requested program. This change can cause a failure of a SETERR branch when a program initiated RUN is defeated by an ERROR 12. This results in the task falling into CONSOLE mode and reporting an ERROR 12 instead of branching to the SETERR directive line. The example below demonstrates what happens if the program "abcdef" does not exist and SETERR is used. 0010 BEGIN; PRINT (0)'CS'; SETERR 9000 0020 RUN "abcdef" 0030 END 9000 PRINT(0)"ERROR! ",ERR,'RB'; INPUT (0)*;END A temporary fix for a system that encounters this problem is to OPEN the file prior to attemting to run it. An ERROR 12 upon an open is honored by the SETERR branch correctly. This would mean modifying user programs to test for the existence of a program prior to attempting a run, but it would correctly trap the error and prevent the task from exiting into CONSOLE mode. ORIGINATOR: D. FRATER SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB021 Pg001 FIB 00022 12/01/83 *** Error 47 while running *MTC on releases prior to 4.5A *** SYMPTOM: On levels prior to 4.A, an ERROR 47 occurs in program *MTCRD at statement 320 when the disk lacks sufficient free sectors. This problem has been fixed in release 4.5A. FIX: The following will fix this problem: LOAD "*MTCRD" EDIT 320C[ELSE][READRECORD(1,IND=12,ERR=9210)P$;] EDIT 330C[ ][GOSUB 8700;] SAVE "*MTCRD" The corrected statements should read as follows: 0320 IF ERR<>15 HEN GOTO 9210 ELSE READ RECORD(1,IND=12,ERR=9210)P$: LET M$="NO SPACE AVAILABLE PAST SECTOR "+STR(NUM(S$))+"TO RESTORE FILE "+A$(4,6),M1$=" RETRY AFTER S E C T O R S A R E M A D E A V A I L A B L E ",M2$=" S K I P FILE",M3$="ABORT",M4$=""; ON POS(P$(255,1)="ASO")-1 GOTO 9240,2080,0330 0330 GOSUB 8700; ON POS(Z$="1223") GOTO 0330,0340,2080,9240 ORIGINATOR: T. TIANGCO SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB022 Pg001 FIB 00023 02/27/84 *** Early Track Closeout message on MTS utility - release 4.5A *** There is a problem ith the 4.5A MTS utility set that can cause a falsely re- ported early track closeout message to appear during a restore of a streamer tape. The problem is with the program logic that checks for the logical end of tape. The following code changes will fix this problem. In progams *FRTPE, *FSTPE and *RSTPE change statement 8500 in all 3 as follows: OLD: 8500 IF T$(1,5)="*eoi*" THEN PRINT IOL=6070; EXITTO ---> etc. NEW: 8500 IF LEN(T$)=5 AND T$(1,5)="*eoi*" THEN PRINT IOL=6070; EXITTO ---> etc. To make this change LOAD each of the three programs and enter: EDIT 8500 C[IF],[LEN(T$)=5 AND] then press CR/ENTER. Now enter: SAVE then press CR/ENTER ............................................................................... THIS REPAIR IS HIGHLY RECOMMENDED FOR ALL 4.4A, 4.4B, AND 4.5A STREAMER TAPE INSTALLATIONS ............................................................................... ORIGINATOR: D. FRATER SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB023 Pg001 FIB 00024 04/06/84 *** Long format list data incomplete (records management) *** The Long Format List in Records Management will not print the title, first name, last name or suffix if the total length of these fields is not greater than 3 characters. The following code changes will fix this problem. LOAD "RMSO40" Change statement 3530: OLD: 3530 IF LEN(I3$)>5 THEN LET I2$(V,36)=I3$,V=V+36 NEW: 3530 IF LEN(I3$)>0 THEN LET I2$(V,36)=I3$,V=V+36 SAVE "RMSO20" LOAD "RMLM11" Change statement 2090: OLD: 2090 IF ABS(IO)<10000 OR IO>99999 THEN GOTO 2020 NEW: 2090 IF ABS(IO)<10001 OR IO>99999 THEN GOTO 2020 SAVE "RMLM11" ORIGINATOR: T. TIANGCO SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB024 Pg001 FIB 00025 04/18/84 *** Error 46 during select code summary or writing to a sort file *** When sort files are defined for 3276 or more records, a error 46 will occur when performing a select code summary or when writing to the file. This is due to an incorrect calculation on the key size. The following changes will correct this problem: LOAD "RMOS20" DELETE LINES 8080 AND 8082 DELETE LINES 8800 THROUGH 8999 Add lines as follows: 8030 LET S=0,S$="" 8040 CALL "MSUT20","SRT",X2$,X1,X0,0,D1,S,S$ 8050 IF S$<>"" THEN LET E$=S$+" (CR) "; GOSUB 9800; EXITTO 9900 SAVE "RMOS20" ORIGINATOR: T. TIANGCO SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB025 Pg001 FIB 00026 04/20/84 *** SSBs to be aware of when returning to level 4.4B *** Due to the recent decision on discontinuing shipment of the Level 4.5A Operating.System on new and add-on orders, several accounts may be dropping back to or installing for the first time, Level 4.4B. The following list of System Software Bulletins should be reviewed and implemented, where applicable, on each newly installed Level 4.4B system. GENERAL SSB 111 File Move and/or Copy Utility SSB 112 Error 47 on BOSS UPDATE SSB 113 Letter Quality Printer Configuration SSB 119 Systems Without a Systems Printer MTC/MTS SSB 101 Streamer Utility Fix SSB 123 *MTC Slowdown SSB 143 Error 47 in *MTCRD SSB 155 MTS End of Tape Problem DATAWORD II SSB 114 Remote Configurator Support SSB 116 Error 169 SSB 117 DataWord II Level 2.3/3.0 SSB 121 Level 3.0 Sheetfeeder Enhancements SSB 136 Update Modifications SSB 141 Printing Conditions 27xx/37xx (TBC) SSB 102 Receive Queue Changes SSB 109 On-Line Spooling Edits If you are missing any of these System Software Bullentins, please contact MSS, (800) 854-1313. ORIGINATOR: LIZ YAMADA SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB026 Pg001 FIB 00027 04/25/84 *** Error 47 after escape key to abort word processing printing *** An ERROR 47 can occur when the escape key is used to abort the printing to a word processing document from Executive Functions. The following code changes will correct this problem: Change the line 1 in thefollowing programs: PSPD10 - LINE PRINTER DRIVER - (PP) PSPD20 - NEC SPINRITER DRIVER - (PP) PSPD30 - STANDARD VDT DRIVER - (PP) PSPD40 - 132 COLUMN ODT DRIVER - (PP) PSPD50 - W/P TEST FILE DRIVER - (PP) PSPD60 - DIABLO PRINTER DRIVER - (PP) OLD: 0001 SETESC 9000; SETERR 9020 NEW: 0001 SETESC 0110; SETERR 9020 ORIGINATOR: T. TIANGCO SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB027 Pg001 FIB 00028 04/25/84 *** Error 41 during records management of data file conversion *** An error 41 can occur when displaying the selectable fields in the Data File Conversion. The following code change will correct this problem: LOAD "RMCV20" OLD: 1470 LET P1=POS(B0$(1,12)=Z0$(16)),Z0$=Z0$(----> NEW: 1470 LET P1=POS(B0$(1,2)=Z0$(16)+B0$(1,12)),Z0$=Z0$(----> SAVE "RMCV20" ORIGINATOR: T. TIANGCO SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB028 Pg001 FIB 00029 05/11/84 *** Fixed media system hangs on release 4.5A at printer power on/off *** A problem which causes the 110/410 system to hang when either a Dataroyal or Tritel serial printer is powered on or off has shown up in several different installations. The customer must reload the system to continue processing. This problem is a fault in the 4.5A operating system, not the CPU, cables or printer. The customer may get around this by first turning on the printer and then loading the BOSS. He must not power the printer off or on during the rest of the day or the system will hang. If this presents a problem to the customer's operating procedure, the the only alternative is to use anothe operating system level. As far as is known, this problem has not shown up on 13XX systems which have removable media disks, but be aware that it might. ORIGINATOR: S. SCHWARTZ SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB029 Pg001 FIB 00030 05/23/84 *** CPU halts, CPU hangs or task hangs after "DELETE" is entered *** A potential halt/hang problem exists on any level 4 system running programs that have been translated from BBI or BBII systems. The problem is rather rare, but can cause system halts, syatem hangs or hung terminals. It is due to a difference between the compiled code of programs compiled under BBII and programs compiled under level 3 or 4, and is apparently limited to programs containing a DEF$ function. If such a program is LOADed into memory and the a console DELETE is executed, a halt or hang can occur. This problem can be corrected by recompilation of the suspect program. Another symptom of the problem is that the system utility for renumbering programs fails on the com- piled code. A method for recompiling BASIC programs is as follows: First define a SERIAL work file for 1000 records and 132 bytes pre record. Name the file "SER001". (1) START a terminal with suficient memory pages to accomodate the program to be re-compiled. (2) LOAD the program. (3) In console mode, execute the following: OPEN(1)"SER001" (4) In console mode, execute the following: LOCK(1) (5) In console mode, LIST the program o "SER001" by typing: LIST(1) (the list make take several seconds - wait for the > ) (6) Close "SER001" by typing: CLOSE(1) (7) Re-START the terminal with the same number of pages used in step (1). (8) OPEN "SER001" again by typing: OPEN "SER001" (9) LOCK "SER001" by typing: LOCK(1) (10) Merge "SER001" into memory by typing: MERGE(1) (the merge may take several seconds and may end with an ERROR 21) (11) Close "SER001" by typing: CLOSE(1) (12) SAVE the program now in memory to it's original name. Repeat the above process for each program that has been translated from a BBI or BBII system AND that contains a DEF$ function. Once recompiled, the newly compiled code will not have the halt/han potential. ORIGINATOR: D.FRATER SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB030 Pg001 FIB 00031 06/04/84 *** Cpu halts, CPU hangs or tasks hang on any release prior to 4.5B *** There exists a problem with level 4 BOSS which causes the above symptoms. It occurs when binary information is passed to a called program via a call list. An example of the type of data that can cause the problem is the FID of a file, which is largely composed of binary data. A simple call, like the example below, that sends the FID of a disk file to a called program can result in a system halt: OPEN (1)"AFILE" CALL "PROG01",FID(1) To avoid encountering this problem, it is recommended that binary data be converted into decimal format before passing the data to the called program. ORIGINATOR: D. FRATER SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB031 Pg001 FIB 00032 07/02/84 *** Causes of file system Error 11's *** The purpose of this document is to explain possible causes for ERROR 11, "missing or duplicate key" as reported by BOSS during application software operation. Although only the error 11 is discussed, try to use this type of logic when troubleshooting problems based solely on customer reported errors. Typically, these types of errors are such that diagnostics indicate no problems and failure duplication is difficult. PROBLEM: Intermittant ERROR 11 while accessing a data file. FACTS: The data file is a direct file. The file is accessed for both reads and writes by the operator. The file may be accessed by more than one operator simultaneously. The file does not appear to be damaged. (no missing or duplicate records) The failures occur only when multiple operators are working. CAUSE: Multiple operators accessing the file at the same time. There are some pitfalls in the BOSS file handlers which, if not taken into account by the applications programmer can cause these types of errors! When diagnostics and duplication efforts fail to isolate a problem, ensure that a hardware problem exists PRIOR to swapping hardware! ORIGINATOR: J. RIPPL SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB032 Pg001 FIB 00033 07/13/84 *** *MTC tape read check may fail to report failure on BOSS 4.4 & 4.5 *** The *MTC tape read check routine (*MTCTR) on all level 4.4 and 4.5 systems contains a logic error that can cause the utility to bypass reporting a tape read error on the screen. The following is a patch to eliminate this problem. 1. LOAD "*MTCTR" and list statement 290. It will be as follows: 0290 PRINT (0,ERR=2900)@(10,21),"TAPE READ ERROR =",ERR," STATUS =",A0$,; INPUT (0,TIM=30,ERR=0300),"ENTER 'CR' TO SKIP FILE, MBIII TO CHANGE TRACKS, MBIV TO ABORT - ",*,@(0,21),'CL',@(0,22),'CL',; ON CTL-2 GOTO 0100,0390,0460 2. Enter the following: EDIT 0290 C[,21),],['RB'],C[TIM=30,ER=],R[0290] then press CR/ENTER 3. The resulting statement 90 will be: 0290 PRINT (0,ERR=2900)@(10,21),'RB',"TAPE READ ERROR =",ERR," STATUS=",A0$,; INPUT (0,TIM=30,ERR=0290),"ENTER 'CR' TO SKIP FILE, MBIII RO CHANGE TRACKS, MBIV TO ABORT - ",*,@(0,21),'CL',@(0,22),; ON CTL-2 GOTO 0100,0390,0460 4. Enter SAVE "*MTCTR" then press CR/ENTER ORIGINATOR: D. FRATER SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB033 Pg001 FIB 00034 07/31/84 *** Prior to rel 4.5 printers give Error 0 printing EVDT U.C. "6" char. *** EVDT terminal keyboards with upper case six (6) indicate either a cent sign or a grave accent mark. The hex code for this keystroke is $E0$. Due to printer drivers in software releases prior to BOSS level 4.5, this code will cause an ERROR 0 during printing. Software releases 4.5A and above correct this problem. ORIGINATOR: J. RIPPL SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB034 Pg001 FIB 00035 12/07/84 *** Starting with rel 4.4B defective ports cause port shifting *** Beginning with BOSS release 4.B, any defective 8-way port causes the OS to shift the port configuration to the next available port during the load. EXAMPLE - System configured for 5 serial ports; 4 terminals and 1 printer: T0 = VDT T1 = VDT T2 = VDT T3 = VDT T4 = PRINTER If T2 on the 8-way becomes defective and the system is loaded - T0 = VDT T1 = VDT T2 = T3 = VDT T4 = VDT T5 = PRINTER The result of this condition is that the VDT's connected to ports 2 and 3 now have FID's of T3 and T4, respectively. Also it is quite likely that the printer if accessed will produce error 5's because of incorrect baud rate and, of course the VDT attached to physical port 2 will not work. ORIGINATOR: S. SCHWARTZ SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB035 Pg001 FIB 00036 03/18/85 *** Release 4.5B Software Announcement *** THIS SOFTWARE ANNOUNCEMENT SUPERCEDES PREVIOUS 4.5B SOFTWARE ANNOUNCEMENT DATED 2/22/85. Level 4.5B is now released and available for distribution. This release is the recommended operating system replacing all prior Level 4 releases. If you wish to order this software level, please use the following software market codes and order the appropriate media separately: Market Code Description WG 013AA O.S. Level 4.5B WG 013AB O.S. Level 4.5B Update This document details the new and enhanced features of Level 4.5B. Installation/Upgrade procedures are fully documented in this announcement. It is strongly recommended that these procedures be read prior to installing any Level 4.5B Operating System. TABLE OF CONTENTS 1.0 OVERVIEW 2.0 LEVEL HISTORY 3.0 ENHANCEMENTS 3.01 NS/FTF ENHANCEMENTS 3.02 13XX INTERSYSTEM TRANSFER PACKAGE 3.03 SUPPORT OF 5 1/4" WDD 4.0 OS/DRIVER CORRECTIONS 4.01 SERIAL PRINTER HANG 4.02 MTC EARLY TRACK CLOSE-OUT 4.03 ISP SLAVE PRINTER HANG 5.0 INSTALLATION AND UPGRADE PROCEDURES FOR LEVEL 4.5B 5.01 FIXED MEDIA PROCEDURES 5.02 REMOVABLE MEDIA PROCEDURES 1.0 OVERVIEW The Level 4.5B Release includes support of the 5 1/4" Winchester disk drives, enhancements to the 13XX Intersystem Transfer package and to diagnostics. In addition to these features this is also a corrective release. Level 4.5B software will contain all the functionality of the 4.5A and 4.5S releases. NOTE: OSBBII has now been renamed on tape to OSBB2, and a new loader new with 4.5B named "(>LDR" has been created to replace any SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB036 Pg001 past loaders. Please read the installation and upgrade procedures carefully to avoid possible problems due to these changes. 2.0 HISTORY OF LEVEL 4 BOSS RELEASES 4.1A Obsolete Enhanced release for removable media systems requiring greater than 18 tasks, 16 terminals, and 256K memory, and were unable to configure under Level 3 due to bank 0 limitations. 4.2A Adequate except This release contained significant Error 16 and enhancements over all previous versions absence of including many new features available to the communications user and various performance improvement. Enhancements include a new loader, sector cache, MDF, auto-save, LIFO removal, and overlaid calls. 4.2B Adequate except Addition of batch communications package plus ERROR 16 various corrections to VDT emulation. 4.3A Adequate except This release contained an enhanced spooler, for support of EASY II, and DataWord\ II. System 310 4.3B Required release Recommended for MTC improved support. for support of System 310 4.3D Adequate release The release contains several DataWord\ II corrections. 4.4A Adequate release This release added MTS (Magnetic Tape Streamer) and *MTCI. It also increased Configurable ghost tasks to 16 and supports up to 8 MDT's. The SPE port configurations option contained a change which allows the configuration to specify if X-ON/X-OFF protocol will be active or inactive for each SPE port. 4.4B Adequate release Carrier for DataWord\ II, 3.0 release, significant enhancements to the Word Processing features of DataWord\ II. 4.5A Recalled for Carrier for DatWord~II, 3.1 release. data corruption Support of ISP as slave printers on S/10's. problems Release problems of 64K IMLC and X.25 communications on the 13XX domestic systems. 4.5S Adequate release Temporary release for 5 1/4" fixed disks. 3.0 ENHANCEMENTS 3.01 NS/FTF ENHANCEMENTS In addition to support of X.25, NS/FTF now supports an SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB036 Pg002 asynchronous transporter. This allows the user to select the data communications medium which best suits his needs. If FTF/B4NET/ASYNC is configured, then an IMLC is not required. It is imperative to note either X.25 or ASYNC, but not both, may be configured. 3.02 13XX INTERSYSTEM TRANSFER PACKAGE The 13XX Intersystem Transfer Package is a software package which is necessary at any 13XX site where Business Basic program and data files are to be exchanged with the 2000 system, or when the 1/4" streamer tape is used for interchange between 13XX, 8000 and 2000 systems. The 13XX Intersystem Transfer Package contains 4 main sections: 1. The Batch Queuer (BQR) provides special file lists and interfaces to standard file list structures. 2. The Schema Generator describes a file's data structure. 3. The transporter provides and defines the transport mechanism via Magnetic Cartridge Streamer (MCS), 27XX/37XX, or asynchronous file transfer (ATP). 4. The ASCII converter converts data to the native ASCII character range of the receiving system, and flags incompatibilities in BASIC programs. 3.02.1 13XX INTERSYSTEM MCS TRANSPORT UTILITY The 13XX Intersystem MCS Transport Utility (BBIICS) is an alternate-loaded operating system that can be used only with the 1/4" magnetic cartridge streamer. 3.02.2 27XX/37XX 27XX/37XX now supports an interface to the 13XX Intersystem Transfer Package. 3.02.3 ASYNCHRONOUS FILE TRANSFER PROGRAM The Asynchronous File Transfer Program (ATP) is easy to use, and provides a means of transmitting all types of files (program files will be transmitted to unlike systems as serial files) to any other Basic Four System, with verification that the file is received accurately. The communications port is an asynchronous terminal port found on all Basic Four Systems. In addition to interfacing with the 13XX Intersystem Transfer Package for data exchange between 13XX and 2000 systems, ATP can be used for file transfers between 13XX, 8000, and S/10 systems. 3.03 SUPPORT OF 5 1/4" WDD Level 4.5B will support the 5 1/4" Winchester disk drives (WDD). For a full description of these drives, please refer to the 4.5S Software Announcement #080884/108. 4.0 OS/DRIVER CORRECTIONS 4.01 SERIAL PRINTER HANG SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB036 Pg003 A problem was found on Level 4.5A, whereby a system hang or an error 5 occurred, if the serial printer was powered on after loading the system. This has been corrected in Level 4.5B. 4.02 MTC EARLY TRACK CLOSE - OUT The MTC DRIVER, (>TC, has been rewritten to allow more retries when encountering errors, thus allowing soft errors to be handled better by the utility. 4.03 ISP SLAVE PRINTER HANG The intermittent hang that occurred due to a buffer overflow of the ISP printer, has been corrected in 4.5B. 5.0 INSTALLATION AND UPGRADE PROCEDURES FOR LEVEL 4.5B _ _ _ ALWAYS PERFORM A COMPLETE VERIFIED BACKUP OF _ _ THE SYSTEM PRIOR TO EVERY SYSTEM UPGRADE _ _ _ 5.01 FIXED MEDIA PROCEDURES 5.01.1 Prelevel 4 to 4.5B Installation/Upgrade - The following procedures should be used to install/upgrade from a prelevel 4 system to Level 4.5B. 1. Set all sense switches on the back of the CPU to the left. The red test light on the front panel should illuminate. 2. Insert the BOSS tape for the system into the tape unit and press the LOAD button on the CPU front panel. 3. Specify the program "FORMP" (or ":FORMS" for 5 1/4" WDD) as the alternate load program. Select Option 6, the Zero Recovery Option, from the format screen. 4. Upon completion of "FORMP" (or ":FORMS" for 5 1/4" WDD), press the load button again. This time enter "*SRCFL" as the alternate load program. 5. Reload the system a third time, specifying "OSBB2" as the alternate load program. 6. After responding to the screen prompts, wait for the system recovery sequence to complete. 7. Reset the sense switches on the back of the CPU card to the right, and perform a system alternate load, by pressing TEST and LOAD buttons on front of CPU. Input OSBB2 as the program name. The screen will then display "Update is Complete. Please re-boot." Reload the system to begin normal processing. 8. Run the *MTC procedure "4.2UPDAT" against the system backup tapes to restore all files not currently residing on the fixed disk. SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB036 Pg004 5.01.2 Level 4 to Level 4.5B Systems Upgrade Procedures - The following procedures should be used to install/upgrade from a previous Level 4 system to a Level 4.5B: 1. Under the existing system level, copy the *MTC procedures file "*MTCPC" and name it "****PC". This is accomplished by typing RUN "*FILE" and selecting Option #4. 2. Define a new temporary procedure that has all of the normal defaults and includes two files; "*MTCPC" and "*MTCRK". 3. Load the 4.5B systems tape and execute the newly defined temporary procedure. This copies the procedure files and restores the new version of "UPDATE", which corrects the "hang" problem associated with level 4.3A. 4. After a successful completion of Step #3, run the *MTC procedure "UPDATE" against the system tape. 5. Reload the system. The screen will display the proprietary message plus the serial number and the old level of O.S. 'RETURN' for next screen (or 'ESCAPE' if SCT=G0). The screen will then display "Update is Complete. Please Re-boot." Re-load the system again to begin normal processing. 6. If the site has custom backup and restore procedures, it will be necessary to reinstate their pre-update version of the procedure file. To do this, erase "*MTCPC" and rename the copy created under Step #1 from "****PC" to "*MTCPC". This is accomplished by typing RUN "*FILE" and selecting Option #1. If it is not necessary to reinstate the procedure file, simply erase the copy made in Step #1, "****PC". 5.02 REMOVABLE MEDIA PROCEDURES 5.02.1 Upgrade of a Level 4 system to Level 4.5B Via Tape - The following procedures should be used to upgrade a previous Level 4 system to Level 4.5B, with 4.5B residing on tape: 1. Under the existing system level, copy the *MTC procedure file, "*MTCPC" and name it "****PC". This is accomplished by typing RUN "*FILE" and selecting Option # 4. 2. Define a new temporary procedure with all the normal defaults and only one file, *MTCPC. 3. Load the 4.5B system tape and execute the newly defined temporary procedure. This copies the procedure file and restores the new version of "UPDATE", which eliminates the "hang" problem associated with 4.3A. 4. After a successful completion of Step # 3, run the *MTC procedure "UPDATE" against the system tape. 5. Reload the system. The screen will display the SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB036 Pg005 proprietary message plus the serial number, and the old level of O.S. 'RETURN' for next screen (or 'ESCAPE' if SCT=g)). The screen will hen display "Update is Complete. Please Re-boot." Reload the system to begin normal processing. 6. If the site has custom backup and restore procedures, it is necessary to reinstate their pre-update version of the procedures file. To do this, erase "*MTCPC" and rename the copy created under Step #1 (from "****PC" to "*MTCPC"). This is accomplished by typing RUN "*FILE" and selecting Option #1. If it is not necessary to reinstate the procedures files, simply erase the copy made in Step #1 "****PC". 5.02.2 Updating A Removable System Not Configured With Tape at a Branch or Dealer (HOST) Location - This procedure should be used for updating a customer removable system, not configured with a tape, at a branch or dealer location. "Host" refers to the branch or dealer system. 1. Erase the two tape drivers "(>TC" & "(>MR" from the customer's pack. Even though the system was not configured for tape, the BOSS pack still contains the drivers. 2. Write a new update procedure called "UPDAT1" as follows: STEP #1 - CATALOG: o Use any tape; do not retension o Catalog label and files (full catalog) - Archive STEP #2 - RESTORE: o Include all files o Include files OSBB2, OSESCP, OSMONR, OSINIT, OSSTRT o Include files *DMPFL, *SRCFL, BBIITC o Exclude files $brief, $conf, $formt, $oper, $queue o Exclude files *MTCFC, *MTCFL, *MTCPC, *MTCTC o Exclude files (>MR, (>TC, *PARM o Use Disk Number: 0 o Use tape from previous step; do not retension o Tape must be fully cataloged o If a selected file is not found, skip the SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB036 Pg006 file o If a file already exists on disk, replace that file o Files are restored at their previous location or at the first available sector o If there is insufficient disk space, the operator may skip the file or abort. o Restore from the first backup on tape STEP #3 - RESTORE o Include files $brief, $conf, $formt, $oper, $queue o Include files (>MR, (>TC, *PARM o Use Disk Number: 0 o Use tape from previous step; do not retension o Tape must be fully cataloged o If a selected file is not found, skip that file o If a file already exists on disk, do not restore the file o Files are restored at their previous location or at the first available sector o If there is insufficient disk space, the operator may skip the file or abort o Restore from the first backup on tape UPDATE PROCEDURES: 1. Load the system under the host pack's operating system. 2. DISABLE O, DISABLE 1; power down drives 0 and 1. 3. Place the customer pack in drive O, the host pack in drive 1; power up drives 0 and 1 and bring on-line. 4. ENABLE O, ENABLE 1. 5. Start 'T0' with 128 pages and RUN "*MTC". 6. Mount the customer's system tape. 7. Execute the newly defined procedure "UPDAT1". 8. After a successful completion of the SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB036 Pg007 "UPDAT1" procedure, load the updated pack. The screen will display the proprietary message plus the serial number, and the old level of O.S. 'RETURN' for the next screen (or 'ESCAPE' if SCT=G0). The screen will then display "Update is Complete. Please Re-boot." Reload the updated pack and follow through to 'T0' initialization. Run "*CONF" to verify that the update performed correctly. 5.02.3 Disk to Disk upgrade to Level 4.5B - The following procedure should be used to perform a disk to disk upgrade from a previous Level 4 release to Level 4.5B: _ _ _ PRIOR TO EVERY SYSTEM UPGRADE, ALWAYS PERFORM _ _ A COMPLETE VERIFIED BACKUP OF THE SYSTEM _ _ _ 1. Place the new BOSS pack in drive O, the old BOSS pack in drive 1, and LOAD the system from the new BOSS pack. 2. After system initialization is complete, run the utility selector "**". 3. Select Option (5) - System. 4. Select Option (5) - BOSS update 5. Respond to the prompts as required, and RUN. ORIGINATOR: MBF SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB036 Pg008 FIB 00037 05/20/85 *** Release 4.5B UPDATE procedure for removable media disks *** The following is the procedure to follow when updatng an initialized customer pack to 4.5B, from tape. 1. Load system with host pack in drive 0 and customer pack in drive 1. 2. Initialize disk 1 (whole disk). Be sure pack is lableb as a master, not a data, pack. 3. Copy *RETUD and *RTUD1 from drive 0 todrive 1. 4. Disable both drives, switch the packs and enable both pdrives. 5. Run *RETUD and put the tape in the tape unit. *RETUD will restore the tape utilities to drive 0, from tape. 6. Run the *MTC procedure UPDATE to restore all system files to drive 0. 7. Flip the CPU sense switches to the left, to alt load from tape. Press the load button and input the program name OSBB2". This will run OSMONR to update the loader and rename OSBB2 to OSBBII. 8. The message "SYSTEM UPDATED. PLEASE RE=BOOT" will display. Re-set the sense switches and load the system normally. ORIGINATOR: BASIC FOUR SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB037 Pg001 FIB 00038 05/23/85 *** Procedure to upgrade a Pre-level 4 fixed disk system to level 4.5B *** SYMPTOM: System loading problems can occur following/during BOSS level 4.5B software installations, where fixed disks have required formatting or when upgrading a pre-level 4 system. FIX: Where disk frmatting or zero recovery is required to install level 4.5B, proceed as follows: 1. Run "FORMP or ":FORMS" if it is a 1600 system 2. Altload from tape "*SRCFL" 3. Altload from tape "OSBB2"; wait for system recovery completion. 4. Altload from disk "OSBB2"; wait for "UPDATE IS COMPLETE" message (this renames "OSBB"" to "OSBBII") 5. Reload from disk normally ORIGINATOR: J. RIPPL SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB038 Pg001 FIB 00039 11/01/85 *** Error 17 or Error 27 during MTS tape lable write on release 4.5 *** Problem: An error 0 during "Now Writing Tape Label" will sometimes display "ERR=17" or "ERR=27". The following changes will correct this problem. Solution: LOAD "*DSTPE" Change statement 8010: . OLD: 8010 PRINT @(10,21), 'RB', "TAPE NOT READY, PLEASE WAIT"; GOSUB 7500; RETRY NEW: 8010 PRINT @(10,21), 'RB', "TAPE NOT READY, PLEASE WAIT"; IF TCB(5)=220 THEN GOTO 220 ELSE IF TCB(5)=7120 GOTO 7120 ELSE IF TCB(5)=310 THEN GOTO 310 ELSE RETRY ORIGINATOR: J. RIPPL SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB039 Pg001 FIB 00040 05/22/86 *** Error 43 during 13XX to 2000 software conversion *** SYMPTOM: The MCS transport conversion program has an edit mask of 5 characters, if the number of records in a file exceeds 99,999 the program will produce an ERROR 43 when the 100,000th record is processed. FIX: To correct this, the following changes need to be entered on the 13XX system while in a standard load: 1. Enter LOAD "*MCS16" then press CR/ENTER 2. Code line 6005 is: 6005 IF R6=1 THEN PRINT @(62,10),'SF',STR(R2: "####0"), Change 6005 to: 6005 IF R6=1 THEN PRINT @(62,10),'SF',STR(R2: "#####0"), To do this, enter: EDIT 6005 C[#][#] then press CR/ENTER 3. Code line 6410 is: 6410 LET A=A+1,N0=0,R6=0; PRINT @(0,10),'CL';PRINT @(60,6),'SF',STR(A:"###0"), Change 6410 to: 6410 LET A=A+1,N0=0,R6=0; PRINT @(0,10),'CL';PRINT @(60,6),'SF',STR(A:"####0"), To do this, enter: EDIT 6410 C[#][#] then press CR/ENTER 4. Code line 8200 is: 8200 IF R1>1000 THEN LET R6=1; PRINT @(34,10),'SB',"RECORDS ",STR(R1:"#0000"), @(50,10),"PROCESSED ",ELSE LET R6=0 Change 8200 to: .8200 IF R1>1000 THEN LET R6=1; PRINT @(34,10),'SB',"RECORDS ",STR(R1:"##0000"), @(50,10),"PROCESSED ",ELSE LET R6=0 To do this, enter: EDIT 8200 C[#][#] then press CR/ENTER 5. Enter SAVE "MCS16" then press CR/ENTER 6. Enter LOAD "MCS19" then press CR/ENTER 7. Code line 485 is: 0485 IF R2>1000 THEN LET R6=1; PRINT @(34,10),'SB',"RECORDS ",STR(R2:"#0000),. @(50,10),"PROCESSED ",ELSE LET R6=0 Change line 485 to: 0485 IF R2>1000 THEN LET R6=1; PRINT @(34,10),'SB',"RECORDS ",STR(R2:"##0000), @(50,10),"PROCESSED ",ELSE LET R6=0 To do this, enter EDIT 0485 C[#][#] then press CR/ENTER 8. Code line 725 is: 0725 IF R6=1 THEN PRINT @(62,10),'SF',STR(R1:"####0"), Change line 725 to: 0725 IF R6=1 THEN PRINT @(62,10),'SF',STR(R1:"#####0"), To do this, enter: EDIT 0725 C[#][#] then press CR/ENTER 9. Enter SAVE "MCS19" then press CR/ENTER SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB040 Pg001 ORIGINATOR: P. THATCHER SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB040 Pg002 FIB 00041 06/16/86 *** Error 47 using *COMM on release 4.5B *** If a system is configured for 19 or more terminals. the *COMM application may display confusing or erratic information. In addition, definition of the TI device may lead to an ERROR 47 when *COMM is run. The following are patches to fix these problems: 1. Load *COMM and add the following line of code: 0055 IF T$(1,1)="T" THEN LET T$=T$(7);GOTO 0055 ELSE GOTO 0070 2. Modify statement 0116 as follows: The original line 0116 will read: 0116 IF T9<>0 THEN LET T$=T$(0,T9-1)+T$(T9+6) Change line 0116 to read: 0116 IF T9<>0 THEN LET T$=T$(1,T9-1)+T$(T9+6) This change may be done by entering the following: EDIT 0116 C[(]R[1] (CR/ENTER) 3. After the changes shown in steps 1 and 2, SAVE the program back to disk. ORIGINATOR: R. HINOJOSA SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB041 Pg001 FIB 00042 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 BBIV-----------------------FIB042 Pg001 FIB 00043 02/22/90 *** Date Changes to 01/01/83 after 1989 [ WPSF 599 ] *** PROBLEM: *BCOM will change the system date to '01/01/83' if the current date is after 1989. Program ",BBF" has to be changed. FIX: Change line 8050 from: 8050 IF M9<1 OR M9>12 OR D9<1 OR Y9<79 OR Y9>89 THEN GOTO 8050:8080 ^^ ^ The line should be: 8050 IF M9<1 OR M9>12 OR D9<1 OR Y9<79 OR Y9>99 THEN GOTO 8050:8080 ^^ ^ ORIGINATOR: Dan Arteritano SOFTWARE-BASIC FOUR-BOSS BBIV-----------------------FIB043 Pg001