MAI COMPANY CONFIDENTIAL FIELD INFORMATION BULLETIN SERVICE GROUP(S): MINI MFG: BASIC FOUR NACS TYPE(S): N014 MFG. MODEL(S): BOSS BBV (S80) CATEGORY: SOFTWARE DESC: O.S. & UTILITIES *** TABLE OF CONTENTS AS OF 02/14/95 *** FIB 00001.Error 156'S.................................................12/17/81 FIB 00002.Don't Create Files with "/" OR ":" Characters in File Name..02/02/82 FIB 00003.Explanation of Application Permit Numbers (APNs)............03/08/82 FIB 00004.Error 12 Running EASY at Level 5.3A.........................03/25/82 FIB 00005.Printer Configurations on Level 5.3B........................08/24/82 FIB 00006.Error 92s After Software Upgrade............................11/04/82 FIB 00007.ERR 41s and 2s While Using 27xx/37xx Emulation on Level 5.4A07/01/83 FIB 00008.ERR 2s on 5.4A & B While Running "*RSTOR"...................12/01/83 FIB 00009.Instructions for Use of *FORMP - Disk Formatter Utility.....01/25/95 SOFTWARE-BASIC FOUR-BOSS BBV (S80)------------------Table Of Contents Pg01 of 01 FIB 00001 12/17/81 *** Error 156'S *** SYMPTOM: Error 156s (Data Transmission Error - ICOM) PROBLEM DETERMINATION: There are numerous hardware possibilties for this error: 1. Defective FMM Board 2. Defective CPM/VDM Board 3. ICOM Cables 4. Ground loops (checks are listed in another FIB) 5. Defective backplane in FMC There is also a potential software cause if the O.S. level is lower tha 5.2A.2 FIX: Eliminate potential hardware causes and upgrade the O.S. if lower than 5.2A.2. ORIGINATOR: Prod Support SOFTWARE-BASIC FOUR-BOSS BBV (S80)------------------FIB001 Pg001 FIB 00002 02/02/82 *** Don't Create Files with "/" OR ":" Characters in File Name *** Original Document Name - SYSTEM SOFTWARE BULLETIN 42 DO NOT create Document File names with DATAWORD II using "/" or ":" characters. These characters are RESERVED system characters (used as delimiters). Currently the Dataword II Document file maintenance utility will accept these characters when creating a document file. But once on the DP side they cannot be accessed, erased, expanded, backed-up, restored, moved, renamed, or opened. In order to reuse that section of the disk for other purposes the system must be backed up (with the exception of those document files) and the disk reformatted. Fix is in release 5.3A. ORIGINATOR: S. Muller SOFTWARE-BASIC FOUR-BOSS BBV (S80)------------------FIB002 Pg001 FIB 00003 03/08/82 *** Explanation of Application Permit Numbers (APNs) *** Original Document Name - SOFTWARE ANNOUNCEMENT 030882/81 Application Permit Numbers (APNs) regulate user access to individual data files and BASIC programs. Basic Four uses APNs to secure proprietary software and to ensure that only software current to the present operating system is used. APNs are also used by some Basic Four vendors to secure their own applications software. APNs cannot be changed or assigned by end users. When an operating system is configured, a series of "system APNs" are stored with the operating system information. These APNs match the individual file APNs assigned to the system utilities and any purchased software packages (Dataword II, Easy II, etc.). Depending on how these "system APNs" - which comprise the Application Permit List (APL) - compare to an individual file's APN, user access to that file can be unlimited, limited, or entirely prohibited. The APL of any operating system (O.S.) can be listed using the *Z utility. Individual file APNs can be listed with *A using the complete file description option; limited access BASIC programs are further identified by both *A and F with a "### SECURE PROGRAM ###" comment. APN SECURITY LEVELS AND HOW THEY WORK Four types of system/file APN conditions and security protection exist and are dscussed below in order of increasing security: 1. A file has no APN (the APN is zero). A file with zero APN has no security protection and there are no operational restrictions on its use or access. Files defined with the BASIC . commands PROGRAM, DIRECT, SORT, INDEXED, and SERIAL, the system utility *O, or the O.S. command SAVE (see footnote at the end of this document) will automatically be assigned to an APN of zero. All user defined programs and data files fall into this category. Zero APN programs can be copied freely from one O.S. to another without any security problems. 2. A file with a positive APN matches either a positive or negative system APN in the APL. (For example, a file APN of 100 is matched in the APL by either a 100 or -100). The file has full read/write access on the present O.S. but may not be accessable at all on a later O.S. level due to revision of the system APNs. (See the section entitled "What APNs Are Used For"). 3. A file with a negative APN is matched by either a positive or negative system APN in the APL. (For example, the file APN is -100 and the system APN is 100 or -100). . Negative APNs are assigned to secure programs which the user may only LOAD, RUN, OPEN, ERASE, copy or identify using FID. Attempts by the user to LIST, READ, WRITE, or cross-reference with *X are not allowed and will result in. an Error 91. When a program with a negative APN finishes execution (by reaching the END statement or the user hitting the ESCAPE key), a START will automatically be performed. SOFTWARE-BASIC FOUR-BOSS BBV (S80)------------------FIB003 Pg001 4. The file APN is not matched by any system APN (For example, a file has an APN of 100 or -100 but there is no system APN of 100 or -100 present in the APL). The file cannot be accessed at all aside from copying, ERASE, OPEN, and FID; attemps to LOAD, RUN, READ, WRITE, etc. will result in an Error 92. Files with completely non-matching APNs are useless and typically occur when either there has been a mistake in APN assignment or files from another operating system release (and with different APNs) are being referenced. WHAT APNs ARE USED FOR Basic Four APNs (APN between -999 and 999) Use: System software, utilities, and Basic For applications (Dataword II, Easy II, synchronous and asynchronous communications, etc.) These APNs are used exclusively by Basic Four and are automatically included as needed in the APL by the configurator. Each Basic Four application package has one or more distinct APNs assigned to it, as do the system software and utilities. These APNs cannot be altered using *VEND (see below) except with a configurator. Basic Four APNs are used to ensure that: 1. A user does not use software which is obsolete for his/her O.S. level. For example, if in a new O.S. release the system utilities have been revised, then the utilities' APNs will also have been changed to ensure that the old versions are not run on the new system - that software levels do not become "mixed". This is also true of the Basic Four applications software. 2. Unauthorized use of software does not occur - for example, to prevent a user who has not purchased a Basic Four applications package from obtaining it from another user who has. Negative APNs further secure programs by preventing copying not only from floppy discs but also prohibiting program listings. Vendor APNs (APN between 1000 and 32767 or -1000 and -32767) Use: Vendor applications software packages (CBSIII, Club Management System, etc.) These APNs prevent a user who has not purchased a vendor's software package from obtaining a usable copy from another user who has. Unlike Basic Four APNs (which are automatically included by the configurator in the APL), vendor APNs must be specified in the S80 BOSS Request and are manually entered when the configurator is run. *VEND *VEND is released only to authorized vendors, branches, and dealers and allows a file's APN to be changed from zero to any of the negative APNs contained in the APL, and vice-versa. *VEND cannot alter APNs not contained in the APL, nor can it alter Basic Four APNs unless run on a configurator (only a configurator will contain negative Basic Four APNs in its APL.) It should be added that branches attempting to change a vendor APN erroneously assigned to a user file by using *VEND on the branch configurator will only be sucessful if the branch configurator itself has SOFTWARE-BASIC FOUR-BOSS BBV (S80)------------------FIB003 Pg002 that (negative) vendor APN in is APL; otherwise a "temporary" vendor configuration containing the APN must be made. Vendors must be sure to specify that the vendor APN(s) configured into their vendor system are negative. *VEND does not recognize positive vendor APNs. When it sees a negative APN it allows both negative and positive assignment. SUMMARY The following table summarizes the allowable operations for each file APN condition: ZERO MATCHING SYSTEM APN NO MATCHING OPERATION APN POSITIVE NEGATIVE SYSTEM APN ------------------------------------------------------------- FID...........X..........X..............X............X COPY..........X..........X..............X............X ERASE.........X..........X..............X............X OPEN..........X..........X..............X............X LOAD..........X..........X..............X RUN...........X..........X..............X LIST..........X..........X EDIT..........X..........X SAVE..........X..........X READ..........X..........X WRITE.........X..........X REMOVE........X..........X APN ERROR CODES 91 - Operation not allowed due to negative APN security 92 - Program or file APN does not match any system APN in the APL START - Escape from negative APN program during execution SOME FINAL NOTES - When a file with a negative APN is erased, the file area is filled with hex zeros. - No utility (such as *B, *BAKUP, *C, *D, etc.) will change a file's APN. - BEWARE: If a program with a non-zero APN has been loaded into mmory, SAVEing the program under a different filename will result in the file having the same non-zero APN. In other words, when a BASIC program is loaded into memory, its APN is loaded as well. This potentially could cause the following type of problem: A user defines a program file on disk using *O (which has a positive APN), then types DELETE to clear memory and starts typing in his/her program. Because the DELETE statement clears the *O program text but NOT its APN, the user will ultimately SAVE not only his/her own program but also the non-zero APN. This will have no immediate effect, but since upon O.S. update the system APNs for such utilities as *O may be changed, the user may not be able to access the program when it is copied to the new operating system. The user should type START (which clears the APN) rather than DELETE before typing in a new program. - If a vendor APN has been erroneously assigned to a user file, then either the vendor or the branch can use *VEND to eliminate the APN. If a Basic Four APN has been erroneously assigned to a user file, there is generally no alternative but to delete the file and recopy it or type it in again from scratch. In some cases Basic Four Marketing Systems Support can assist in SOFTWARE-BASIC FOUR-BOSS BBV (S80)------------------FIB003 Pg003 recovery of the file. ORIGINATOR: Prod. Support SOFTWARE-BASIC FOUR-BOSS BBV (S80)------------------FIB003 Pg004 FIB 00004 03/25/82 *** Error 12 Running EASY at Level 5.3A *** Original Document Name - SYSTEM SOFTWARE BULLETIN 53 Level 5.3A has a defective copy of EASY, use EASY from a level 5.2A BOSS or obtain a level 5.3B or later. ORIGINATOR: S. Muller SOFTWARE-BASIC FOUR-BOSS BBV (S80)------------------FIB004 Pg001 FIB 00005 08/24/82 *** Printer Configurations on Level 5.3B *** Original Document Name - SYSTEM SOFTWARE BULLETIN 72 Printers can be connected to the S80 in either (or both) of the following ways: A. Connected to the FMC (File Manager Computer) - a maximum of 1 serial and 1 parallel. The serial can be either a DP or WP type printer. In order to configure Item A, use item 2 on 5.3B BOSS Request Sheet. Item 2 states: 2. Parallel printer (Y or N)___Serial printer (N/D/W)___ If you have a Parallel printer attached to the FMC enter "Y" for YES. If no parallel printer is attached, enter "N" for none. If you have a Serial printer attached to the FMC, enter either "D" for DATA . processing type oe "W" for Word processing type. If no serial printer is attached, enter "N" for none. B. Connected to the MPC (Multifunction Processing Computer - 12" terminal) or MDT (Multifunction Display Terminal - 14" terminal) - a maximum of 1 serial printer can be attached to each unit. Again, this serial printer can be either the DP or the WP type. In order to configure Item B, use Item 5 on the 5.3B BOSS Request Sheet. Item 5 states: Number of MPC's (1-4)___MPC Port Number T0 T1 T2 T3 Shared printer (Y or N) __ __ __ __ Slave printer (Y or N) __ __ __ __ Printer type (DP or WP) __ __ __ __ Async Communications (Y or N) __ __ __ __ Enter number of MPC's (1-4) First, enter number of MPC's (1-4) If there is a printer attached to any of the MPC's, each printer should be identified as either DP or WP type under the corresponding MPC T0 - T3. When a printer is connected to an MPC, that MPC may be configured with either the shared printer option or the slave printer option (or both). When an MPC printer is configured with the shared printer option, and that option is selected at MPC load time, other MPCs may access that printer. (Provided that the ATTACHED MPC is in DP mode, other MPCs may be in either DP or WP mode). When an MPC printer is configured with the slave printer option, and that option is selected at MPC load time, only the attached MPC may access that printer. (MPC printers with the slave printer option are available only in DP mode). SOFTWARE-BASIC FOUR-BOSS BBV (S80)------------------FIB005 Pg001 Any MPC with or without a printer may be configured for Async Communications. For more details on the Slave or Shared printer options see section on Variable Serial Port Utilization and Dynamic Reconfiguration in the 5.3B Software Announcement #062582/87. NOTE: The new Utility *RECON, which resets the default MPC serial option, is not able to reset to an option unless the system was previously configured for that option. ORIGINATOR: S. Muller SOFTWARE-BASIC FOUR-BOSS BBV (S80)------------------FIB005 Pg002 FIB 00006 11/04/82 *** Error 92s After Software Upgrade *** Original Document Name - SYSTEM SOFTWARE BULLETIN 85 This problem occurs when the following specific sequence of events are executed under an earlier os level (prior to upgrade). Sequence of events: A) An S80 System utility e.g. *O is run on an MPC, the utility completes and the task is in console mode. B) In console mode the command DELETE is typed to clear memory. C) A new program is then written and saved. At this point, this new program has been saved with the APN (Applications Permit Number) that was assigned to the Utility e.g. *O. It is Basic Four's policy to change system APN's from one level to another so as to prevent older levels of System programs from running with later OS's. Consequently, when a system is upgraded these programs created by the above sequence of events will cause an Error 92, APN Mismatch. Solution: 1) Obtain a listing of the customer program if possible and retytpe. 2) Copy program to floppy and send to Basic Four Marketing Systems Support, for removal of the old APN. To avoid this bug, always clear memory by using the 'START' command rather than the 'DELETE' command. ORIGINATOR: S. Muller SOFTWARE-BASIC FOUR-BOSS BBV (S80)------------------FIB006 Pg001 FIB 00007 07/01/83 *** ERR 41s and 2s While Using 27xx/37xx Emulation on Level 5.4A *** Original Document Name - SYSTEM SOFTWARE BULLETIN 122 A problem exists in the level 5.4A 27xx/37xx Emulation Package with receiving serial files from the 810 System in File Transfer mode. An Error 41 or Error 2 can be generated on the level 5.4A System during the receipt of a large serial file. The cause of this problem is the difference in the size of the record length indicators on the serial files of each system. To correct this problem, the following edits must be made to line 1065 of the module ",BRCVF": FROM: 1065 IF F4=1 AND LEN(R$)>=22+X8 THEN IF DEC(R$(16+X8,3))<>0 THEN LET N7=DEC(R$(16+X8,3)), W8=DEC(R$(19+X8,3)), R7=INT((W8/N7)+1) TO: 1065 IF F4=1 AND LEN(R$)>=22+X8 THEN IF DEC(R$(16+X8,3))<>0 THEN LET N7=DEC(R$(16+X8,3)), W8=DEC(R$(19+X8,3))+11, T9=N7-MOD(W8,N7); IF (N7<25 OR N7>500) AND N7>T9 THEN W8=W8+T9, R7=(INT(W8/N7)+1) ELSE W8=W8+T9, R7=(INT(W8/N7)) ORIGINATOR: L. Yamada SOFTWARE-BASIC FOUR-BOSS BBV (S80)------------------FIB007 Pg001 FIB 00008 12/01/83 *** ERR 2s on 5.4A & B While Running "*RSTOR" *** Original Document Name - SYSTEM SOFTWARE BULLETIN 145 On S80, levels 5.4A or 5.4B, if a 'FULL' backup of either 'DATA' or 'BOTH' type files are backed-up via the utility "*BAKUP" to floppy, an Error 2 will occur when trying to restore via "*RESTOR", any or all files to the hard disk. In order to avoid this problem, type in the following correction BEFORE running "*BAKUP": LOAD "*BKUP1" ED4210/1$ OR R$/1$ OR R$(1,4)/ SAVE "*BKUP1" Line 4210 should now look like this: 4210 IF R$=$FFFFFFFFFFFF$ THEN GOTO 4500 ELSE IF R$=F3$ OR R$=B1$ OR R$(1,4)=" BCK" THEN GOTO 4190 If you have backed-up in the above manner without this patch and are getting an ERROR 2 during the "COPYING BACKUP DIRECTORY" section of "*RSTOR", it will be necessary for you to reconstruct the " BCDIR" file that is on floppy #1 of your backup set. The following program can be used to repair the " BCDIR": 0010 REM " THIS PROGRAM WILL CORRECT THE BACKUP DIRECTORY FILE ' BCDIR' " 0020 INPUT (0,ERR=0020)'CS',"ENTER SOURCE DRIVE (F0, F1): ",F$:("F0"=0030, "F1"=0030) 0030 OPEN(1,ERR=9000)" BCDIR"+":"+F$ 0040 LET I1=IND(1,END=9000) 0050 READ RECORD(1,IND=I1,END=9000)A$ 0060 LET L=1536; DIM C$(12,$FF$) 0070 DIM B$(L,$FF$); LET B$(1,12)=A$(1,12); LET F$="01"; LET S=1; LET J=13 0080 FOR I=13 TO L STEP 12 0085 IF A$(I,12)=C$ THEN EXITTO 0120 0090 IF NUM(A$(I+9,2))>NUM(F$) THEN LET S=NUM(A$(I+6,3)); LET F$=A$(I+9,2) 0100 IF A$(I,6)=" BCK01" THEN GOTO 0110 ELSE LET B$(J,12)=A$(I,6)+STR(S:"000")+ A$(I+9,3); LET J=J+12; LET S=S+1 0110 NEXT I 0120 WRITE RECORD (1,IND=I1)B$ 0130 GOTO 0040 9000 END SOFTWARE-BASIC FOUR-BOSS BBV (S80)------------------FIB008 Pg001 ORIGINATOR: S. Muller SOFTWARE-BASIC FOUR-BOSS BBV (S80)------------------FIB008 Pg002 FIB 00009 01/25/95 *** Instructions for Use of *FORMP - Disk Formatter Utility *** ORIGINAL DOCUMENT NAME: Mini Alert 64B SUBJECT: *FORMP, /S80 FORMATTER PROGRAM To format a S80 Fixed Disk: 1. Boot from F0 2. Run "*FORMP" 3. Program prints System Serial Number from D0, Sector 0. If required enter new system serial number to match the serial number written on the BOSS diskette to be installed. Example: BOSS diskette = 850-12345 Enter 085012345 ** Do not enter the dash ** System displays 085012345 4. Check again that the system serial number matches BOSS diskette. The correct number is needed to obtain a valid authorization key and to install the Operating System. 5. Ready to format cylinder zero? YES 6. Enter Volume name or CR 7. If program prints CLEAR BAD TRACK TABLE?, answer as follows: a. YES, if you are formatting a new fixed disc. b. NO, if you are re-formatting and want to keep the alternate track map. 8. Enter number of next bad cylinder ? Enter any suspected bad tracks to the table. 9. After formatting is completed, the program will print a LOCK number at the bottom of the screen if the authorization key is required. The LOCK number has the following format: LOCK = XXX-XXX-XXX-X Write down this number which will be needed to obtain a key. If a key is not required, skip to step 8. Run *FORMP again. The program will print: Enter Key X-XXX-XXX-XXX At this point rfer to GENERAL-BASIC FOUR-ADMINISTRATIVE FIB 5 for current procedures to obtain a key. Supply them with the correct system serial number and the lock number printed by the program on the previous run. The system serial number should be supplied as the system displays it. As on example above, the serial is 085012345 ** Dash is not needed ** Enter key given by authorization center. If key is valid, the program will write sector 0 and END normally. If the key is invalid, it is necessary to enter the invalid key 6 times in order to END the program normally. 10. Run "*INSTL" to install the BOSS diskette on the fixed disc. ORIGINATOR: J. Van Oordt MODIFIED by: Norm Jones SOFTWARE-BASIC FOUR-BOSS BBV (S80)------------------FIB009 Pg001 SOFTWARE-BASIC FOUR-BOSS BBV (S80)------------------FIB009 Pg002