_ FCO KU750-R002, Old loaders & drvrs do not work with VMS V5.0 +-----------------------------------------------------------------------------+ | | | _ _ _ _ _ _ _ Level of Urgency Page 1 | || | | | | | | | +--+ Of 6 | ||d|i|g|i|t|a|l| FCO | R| | ||_|_|_|_|_|_|_| +--+ | |_____________________________________________________________________________| | | | FIELD CHANGE ORDER Number: KU750-R002 | |_____________________________________________________________________________| | Applicability: Retrofit all KU750 options with new G&H microcode before | | installing VMS V5.0. | | | | This brings the rev of the KU750 to 02. | | | |_____________________________________________________________________________| | Problem/Symptom: Old loaders and drivers do not work with VMS V5.0 | | | |_____________________________________________________________________________| | Quick Check: N/A | | | | | |_____________________________________________________________________________| | Compatibility/Prerequisite FCO: | Est. Time to Install: | | N/A | 1 hour | |___________________________________________________|_________________________| | Special Tools or Test Equipment: | | NONE | |_____________________________________________________________________________| | FCO Parts Information | |_____________________________________________________________________________| | Order by Quantity: Part Number: Description: | | FCO Kit#: | | EQ-01533-01 1 BE-T909C-ME TU58 tape containing | | KU750-YG G&H ucode & loader| | FA-04835-01 1 FA-04835-01 FCO Document | |_____________________________________________________________________________| |EQ Kit Variation System/Option Applic: N/A | |_____________________________________________________________________________| | Approvals | |_____________________________________________________________________________| | CSSE Engineer | F.S. Product Safety | F.S. Logistics | |Ken Jackson | Robert Brister |Ed Duggan | |____________________|__________________________|_____________________________| | CSSE Manager | F.S. Microfiche Libraries| Affected Population: | |Jan Sicard | | 500 | |____________________| EP-FSNVX-LB VAX |____________________________ | | MicroMedia Pub | | Initial Kitting: | |Ray LeBlanc | VAXnotes | 500 | |____________________| STARS |____________________________ | | Revision: | | Hardcopy Publication: | | A | | 600 | |____________________| |_____________________________| | FCO Release Date | | Parts Availability: | | 23-NOV-88 | | November 1988 | +-----------------------------------------------------------------------------+ _ _ _ _ _ _ _ | FCO KU750-R002 | | | | | | | | | |d|i|g|i|t|a|l| | PAGE 2 OF 6 |_|_|_|_|_|_|_| | | _______________________________|_________________________________________ UPGRADE PROCEDURE FOR INSTALLATION OF G&H MICROCODE (to support VMS V5) --------------------------------------------------- The KU750 option supports microcode execution of Grand and Huge (G&H) floating point VAX instructions by the VAX 11/750. The CPU hardware must include WCS (Writeable Control Store) prior to installing this software. WCS is written (loaded) with microcode to support the G & H floating point operations. This is the KU750 VMS Update kit for adding KU750 Load (and disable) command Procedures, Load Utility, KU750 Driver (if Battery Backup present and reload on powerfail recovery selected), KU750 microcode load verfication, and G+H Floating Microcode binary file (and G+H Floating Microcode OFF binary file) to a VMS 4.x or 5.x system disk. The Site Specific system startup command procedure must be modified by the System Manager to include KU750 startup procedures. You will be instructed, at the end of this installation, which line to add. VAX-11/750's with H7112 Battery Backup Unit allow VMS to recover from short power failures, without the need for rebooting the system disk, or re-running the system startup command procedures. This is known as WARM-RESTART. KU750 microcode will be destroyed after a power failure, and requires a special WARM-RESTART driver for its reloading. If you desire WARM-RESTART capability, this KU750 Driver and the G+H Microcode image must be memory resident, occupying about 14 kilobytes permanently. If Battery Backup is present and answers to subsequent questions asked in this procedure indicate that powerfail recovery is desired, KU750.COM will be used to SYSGEN/CONNECT the KU750 driver, and call the KU750 load utility for loading the GHFLOAT.BIN ucode. 1. Power Up The System. 2. To Update VMS In Order To Load GHFLOAT.BIN, Perform The Following Steps: A) Boot Up VMS. B) Log In Under The System Manager Account. C) Set Default To SYS$UPDATE: D) Install KU750KIT TU58 #4 (P/N BE-T909*-ME) In CSA1: E) Type "@VMSINSTAL KU750020 CSA1:" _ _ _ _ _ _ _ | FCO KU750-R002 | | | | | | | | | |d|i|g|i|t|a|l| | PAGE 3 OF 6 |_|_|_|_|_|_|_| | | _______________________________|_________________________________________ The update command file will ask four questions: 1) "Do you want to print a copy of the Installation Notes [YES]?" If you answer YES, or just type carriage return, then the installation notes will be printed on SYS$PRINT. 2) "Do you want a copy of the Installation Notes in SYS$MANAGER [NO]?" If you would like to save a copy of the installation notes in SYS$MANAGER answer YES. 3) "Do you want files replaced by this installation purged [YES]?" If you answer YES, or just type carriage return, then any files replaced by this installation will be purged. 4) "If you have battery backup, do you want powerfail recovery?" This question decides how a powerfail is handled. If a powerfail occurs and you have battery backup, WCS will not be reloaded unless the KU750 device driver is included with the command file that defines that device driver. If you answer "yes" to this question, the device driver (KU750DRV) will be included with the KU loader utility (KU750UTL). If you answer "no," the driver will not be included with the utility. F) VMSINSTAL CHECK After you have answered the questions, the update command file will put the files in the proper locations. When the update command file is complete, do the following checks: 1) Ensure the following files are in SYS$SYSROOT:[SYSEXE]: GHFLOAT.BIN GHOFF.BIN KU750UTL.EXE KU750TST.EXE KU750DRV.EXE (only if answered "yes" to question #4.) _ _ _ _ _ _ _ | FCO KU750-R002 | | | | | | | | | |d|i|g|i|t|a|l| | PAGE 4 OF 6 |_|_|_|_|_|_|_| | | _______________________________|_________________________________________ 2) Ensure the following files are in SYS$SYSROOT:[SYSMGR]: KU750.COM KU750OFF.COM KU750INS.MEM (only if answered "yes" to question #2.) 3) Ensure the following is in SYS$SYSROOT:[SYSTEST]: KU750IPC.COM EMUL_Flag_Clear.EXE EMUL_Flag_Set.EXE 3. MODIFICATIONS TO SITE SPECIFIC STARTUP PROCEDURE. Your site-specific startup procedure needs to be edited to include one of the following commands. Place the appropriate command as close as possible to the beginning of the startup procedure. SYSTARTUP NAME CHANGE Site specific startup procedure for VMS V4.x systems is normally named SYS$MANAGER:SYSTARTUP.COM. For version 5.0 VMS, the normal site specific startup procedure filename has been changed to SYS$MANAGER:SYSTARTUP_V5.COM . If you answered "YES" to the question on Battery Backup and Power Fail Recovery, include this line: $ @SYS$MANAGER:KU750 RECOVER If you answered NO to the question on Battery Backup and Power Fail Recovery, include this line: $ @SYS$MANAGER:KU750 _ _ _ _ _ _ _ | FCO KU750-R002 | | | | | | | | | |d|i|g|i|t|a|l| | PAGE 5 OF 6 |_|_|_|_|_|_|_| | | _______________________________|_________________________________________ For either cases the following message will output to the installation terminal screen: "%WCSMSG-I--MICVER, GH microcode version 2 loaded successfully" VMS says this machine is running with G+H Floating Point instructions in microcode. KU750 ucode has been loaded. G_FLOAT_EMULATED = CLEAR Please note that the second command should always be included for systems without battery backup. Note also that the first command should be included for systems equipped with battery backup; if this command is missing, G+H Floating microcode will not be reloaded on recovery from a powerfail condition. 4. Installation is complete. Reboot the system to load KU750 with G+H microcode. 5. OPERATION VERIFICATION To verify that G+H microcode has been successfully loaded, run the testing procedure ( which tests all G+H Floating instructions ) by typing: @SYS$TEST:KU750IPC If the G+H microcode has been loaded, the following message will be output to the installation terminal screen: "%WCSMSG-I--MICVER, GH microcode version 2 loaded successfully" VMS says this machine is running with G+H Floating Point instructions in microcode. KU750 ucode has been loaded. G_FLOAT_EMULATED = CLEAR If the G+H microcode has NOT been loaded, the following message will be output to the installation terminal screen: "%WCSMSG-E-INSTERR, GH instruction errors detected" "%NONAME-W-NOMSG, message number 00000000" VMS says this machine is emulating GH floating point instructions G_FLOAT_EMULATED = SET _ _ _ _ _ _ _ | FCO KU750-R002 | | | | | | | | | |d|i|g|i|t|a|l| | PAGE 6 OF 6 |_|_|_|_|_|_|_| | | _______________________________|_________________________________________ 6. DISABLING G+H FLOATING POINT MICROCODE If for some reason it is desired to disable G+H Floating operation in microcode, then use following command procedure: @SYS$MANAGER:KU750OFF After successful completion of the KU750OFF procedure, G and H floating point instructions will be emulated by the VMS operating system. 7. Complete LARS form using the example below. ------------------------------------------------------------------------------- LARS EXAMPLE ------------ USA GIA EUROPE --- --- ------ Activity - Contract and Warranty W U Y Non Contract/Non Warranty F U F DEC Option KU750 KU750 KU750 Type of Call M M M Action Taken D D I Fail Area-Module-FCO-Comments KU750-R002 KU750-R002 KU750-R002 Material Used EQ-01533-01 EQ-01533-01 EQ-01533-01 \^ KU750 \\KU750 \\JACKSON \\1988 \\NOV \\FCO_DOCS