_ FCO 11750-I009, REMQUE instr fix & PCS750 kit for VMS V5 installs +-----------------------------------------------------------------------------+ | | | _ _ _ _ _ _ _ Level of Urgency Page 1 | || | | | | | | | +--+ Of 13 | ||d|i|g|i|t|a|l| FCO | I| | ||_|_|_|_|_|_|_| +--+ | |_____________________________________________________________________________| | | | FIELD CHANGE ORDER Number: 11750-I009 | |_____________________________________________________________________________| | Applicability: Retrofit all VAX 11750 systems. Priority for upgrades should | | be: 1) UDA-50 configured systems, 2) VMS V5 systems with batterybackup, 3) | | all other 11750 systems. | |_____________________________________________________________________________| | Problem/Symptom: 1) CMT103 fixes problems with REMQUE Instruction (TU58 tape| | #41). 2) New PCS750 Micropatch kit (TU58 tape #3) required to support VMS V5| | installations. | | | | NOTE 1: Diag. ECKAM has been fixed and is contained on tape #5 (for DEC | | internal use and customers who have purchased a diagnostic license - | | p/n BE-S198R-DE). | | NOTE 2: ULTRIX SYSTEMS DO NOT REQUIRE TAPE #3 (PCS Micropatch). | |_____________________________________________________________________________| | Quick Check:Under VMS:$ SID=f$getsyi("sid), $ Show Symbol SID | | 67 HEX should appear in the second byte of the ID reg. if CMT103 is present | |_____________________________________________________________________________| | Compatibility/Prerequisite FCO: | Est. Time to Install: | | N/A | 1 hr | |___________________________________________________|_________________________| | Special Tools or Test Equipment: | | NONE | |_____________________________________________________________________________| | FCO Parts Information | |_____________________________________________________________________________| | Order by Quantity: Part Number: Description: | | FCO Kit#: | | | | FA-04836-01 1 FA-04836-01 FCO Document | | EQ- N/A | |_____________________________________________________________________________| |EQ Kit Variation System/Option Applic: N/A | |_____________________________________________________________________________| | Approvals | |_____________________________________________________________________________| | CSSE Engineer | F.S. Product Safety | F.S. Logistics | |Ken Jackson | Robert Brister |Willie Ewing | |____________________|__________________________|_____________________________| | CSSE Manager | F.S. Microfiche Libraries| Affected Population: | |Jan Sicard | | 15,000 | |____________________| EP-FSNVX-LB VAX |____________________________ | |MicroMedia Pub | | Initial Kitting: | |Ray LeBlanc | VAXnotes | 15,000 | |____________________| STARS |____________________________ | | Revision: | | Hardcopy Publication: | | A | | 15,000 | |____________________| |_____________________________| | FCO Release Date | | Parts Availability: | | 6-FEB-89 | | N/A | +-----------------------------------------------------------------------------+ _ _ _ _ _ _ _ | FCO 11750-I009 | | | | | | | | | |d|i|g|i|t|a|l| | PAGE 2 OF 13 |_|_|_|_|_|_|_| | | _______________________________|_________________________________________ EQ KIT - N/A ------------ CMT103 and the PCS micropatch WILL NOT be available in EQ kits. This material can be obtained in three ways: 1) Via automatic distribution of diagnostic updates; 2) Purchased from SDC (internally) and through Self-Maintenance Services for Per Call customers; 3) copied over the ENET (for internal field service personnel only). Instructions for copying over the ENET must be obtained through your local FCO coordinator. 1) If you are signed up for a diagnostic update service and receive the following update kits, you will have the required tapes to do the fco installation. UPDATE KITS ----------- ZD201-HG (contains TU58 tapes #3 and #41) for Self-Maintenance Customers. ZD904-HG (contains TU58 tapes #3 and #41) for Field Service personnel. 2) INDIVIDUAL PART NUMBERS TO ORDER FROM SDC IF NOT ON AN AUTOMATIC DISTRIBUTION SERVICE: BE-T538F-ME - Tape #3 !PCS Micropatch Kit BE-T204R-ME - Tape #41 CMT 103 !Console Tape NOTE: the Diagnostic ECKAM was discovered broken when system REV 8 FCO was installed. The diagnostic has been fixed and will be available from the Software Distribution Center (SDC) or from Self-Maintenance Services for self-maintenance customers as of October 17, 1988. BE-S198R-DE (ECKAM diagnostic - for field service personnel and/or customers who have purchased a diagnostic license). 3. To copy over the ENET (internal personnel only) call local FCO coordinator for your area. Determining Update Procedure(s) To Follow: ------------------------------------------- If your system uses the console tape to load microcode you must do the Conscopy procedure to update the microcode. Refer to procedure "A". If your system uses a system disk to load microcode you must do the Disk/PCS update. Refer to procedure "B". If your system uses the console tape to load microcode AND uses battery backup for power fail recovery, you must do both procedures A and B. _ _ _ _ _ _ _ | FCO 11750-I009 | | | | | | | | | |d|i|g|i|t|a|l| | PAGE 3 OF 13 |_|_|_|_|_|_|_| | | _______________________________|_________________________________________ PROCEDURE A (Conscopy Procedure) --------------------------------- This procedure will be accomplished by one of two methods: A-I. You will be using a new console tape that was either ordered through SDC or was obtained through automatic distribution. (OR) A-II. You will be updating your current system console tape with the PCS750.BIN file copied over the ENET. ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- PROCEDURE A-I -------------- Parts Required: --------------- 1. Current "Site Specific" console tape. 2. New console tape BE-T204R-ME. 3. Scratch tape. _ _ _ _ _ _ _ | FCO 11750-I009 | | | | | | | | | |d|i|g|i|t|a|l| | PAGE 4 OF 13 |_|_|_|_|_|_|_| | | _______________________________|_________________________________________ 1. Under VMS run conscopy as follows: ................................................................................ :$ @SYS$UPDATE:CONSCOPY : : : : Save or restore a VMS console medium. : : : : "Which CPU kit do you want to build?" : : : : 78X includes 11/780, 11/782 and 11/785" : : 8600 includes 8650" : : 8200 includes 8300" : : : :[8600, 8200, 78X, 750 or 730, default 750]: : : : : A SAVE operation involves copying the console medium to : : an RT-11 virtual volume, which is a Files-11 file that : : is an image of the RT-11 console volume. : : : : A RESTORE operation involves copying the entire contents : : of a virtual volume to a console medium. : : : :Do you want to SAVE or RESTORE your console TU58? :SAVE : : : :Enter file name of virtual disk [default SYS$DISK:CONSOLE.DSK]: : : : :Do you want log messages as files are copied? [Y/N, default Yes]: : : : :Enter console device drive (DDCU:)CSA1: : : : :Put BE-T204R-ME (new console) TU58 tape into drive CSA1:, : :and type when ready: : : : : The SAVE of your console TU58 is complete. : : : :..............................................................................: 2. Insert old console tape into the the TU58. 3. Save site specific files from the current console tape, to be put on the new console tape, by using the following procedure: EXAMPLE: 3.1 $ EXCHANGE 3.2 EXCHANGE>MOUNT/VIRTUAL SYS$DISK CONSOLE.DSK -------------------- : ----------> File name of virtual disk used in CONSCOPY program. _ _ _ _ _ _ _ | FCO 11750-I009 | | | | | | | | | |d|i|g|i|t|a|l| | PAGE 5 OF 13 |_|_|_|_|_|_|_| | | _______________________________|_________________________________________ 3.3 EXCHANGE>COPY/CONTIG CSA1:DEFBOO.CMD SYS$DISK Continue to copy any other files that are customer-specific onto the virtual disk from the old console tape. 3.4 EXCHANGE>EXIT 4. Produce a new site specific console tape from the CONSOLE.DSK file created above by running CONSCOPY as shown: ................................................................................ :$ @SYS$UPDATE:CONSCOPY : : : : Save or restore a VMS console medium. : : : : "Which CPU kit do you want to build?" : : : : 78X includes 11/780, 11/782 and 11/785" : : 8600 includes 8650" : : 8200 includes 8300" : : : :[8600, 8200, 78X, 750 or 730, default 750]: : : : : A SAVE operation involves copying the console medium to : : an RT-11 virtual volume, which is a Files-11 file that : : is an image of the RT-11 console volume. : : : : A RESTORE operation involves copying the entire contents : : of a virtual volume to a console medium. : : : :Do you want to SAVE or RESTORE your console TU58? :RESTORE : : : :Enter file name of virtual disk [default SYS$DISK:CONSOLE.DSK]: : : : :Do you want log messages as files are copied? [Y/N, default Yes]: : : : :Enter console device drive (DDCU:)CSA1: : : : :Put your "SCRATCH" console TU58 into drive CSA1:, : :and type when ready: : : : : The RESTORE of your console TU58 is complete. : :..............................................................................: 5. If you have battery backup that is being used for power recovery continue with Procedure B (Page 10). If not, procede to step 6. 6. Update complete. Reboot the system to load PCS patches. 7. Fill out a LARS form noting that FCO 11750-I009 has been installed. (See Page 13 for detailed LARS instructions.) _ _ _ _ _ _ _ | FCO 11750-I009 | | | | | | | | | |d|i|g|i|t|a|l| | PAGE 6 OF 13 |_|_|_|_|_|_|_| | | _______________________________|_________________________________________ PROCEDURE A-II --------------- 1. Under VMS run conscopy as follows: ................................................................................ :$ @SYS$UPDATE:CONSCOPY : : : : Save or restore a VMS console medium. : : : : "Which CPU kit do you want to build?" : : : : 78X includes 11/780, 11/782 and 11/785" : : 8600 includes 8650" : : 8200 includes 8300" : : : :[8600, 8200, 78X, 750 or 730, default 750]: : : : : A SAVE operation involves copying the console medium to : : an RT-11 virtual volume, which is a Files-11 file that : : is an image of the RT-11 console volume. : : : : A RESTORE operation involves copying the entire contents : : of a virtual volume to a console medium. : : : :Do you want to SAVE or RESTORE your console TU58? :SAVE : : : :Enter file name of virtual disk [default SYS$DISK:CONSOLE.DSK]: : : : :Do you want log messages as files are copied? [Y/N, default Yes]: : : : :Enter console device drive (DDCU:)CSA1: : : : :Put your "CURRENT" console TU58 into drive CSA1:, : :and type when ready: : : : : The SAVE of your console TU58 is complete. : :..............................................................................: 2. Copy the new PCS750.BIN into the CONSOLE.DSK file that was created by the preceding CONSCOPY routine: Note: The new PCS750.BIN must be loaded into your current login space from a magtape or what ever media your are using to get the PCS750_V5_KIT$ files on to your site. _ _ _ _ _ _ _ | FCO 11750-I009 | | | | | | | | | |d|i|g|i|t|a|l| | PAGE 7 OF 13 |_|_|_|_|_|_|_| | | _______________________________|_________________________________________ Files contained in PCS750_V5_KIT$: KITINSTAL.COM PCS750UTL.OBJ ----->PCS750.BIN PCSV3XDRV.OBJ PCS750.COM PCSV40DRV.OBJ PCS750103.A PCSV50DRV.OBJ PCS750DRV.MAR SUBMIT.DATA PCS750INS.DOC TEMPO.DIR PCS750MSG.OBJ TU583.DCOM PCS750OPR.OPT V5_CHANGES.TXT PCS750UTL.MAR 2.1 $ EXCHANGE 2.2 EXCHANGE>MOUNT/VIRTUAL SYS$DISK CONSOLE.DSK -------------------- : ----------> File name of virtual disk used in CONSCOPY program. 2.3 EXCHANGE>DEL SYS$DISK:PCS750.BIN !Deletes old PCS750.BIN 2.4 EXCHANGE>COPY PCS750.BIN/TRANSFER=BLOCK SYS$DISK !Copies new PCS750.BIN to !CONSOLE.DSK 2.5 EXCHANGE>EXIT _ _ _ _ _ _ _ | FCO 11750-I009 | | | | | | | | | |d|i|g|i|t|a|l| | PAGE 8 OF 13 |_|_|_|_|_|_|_| | | _______________________________|_________________________________________ 3. Run conscopy as follows: ................................................................................ :$ @SYS$UPDATE:CONSCOPY : : : : Save or restore a VMS console medium. : : : : "Which CPU kit do you want to build?" : : : : 78X includes 11/780, 11/782 and 11/785" : : 8600 includes 8650" : : 8200 includes 8300" : : : :[8600, 8200, 78X, 750 or 730, default 750]: : : : : A SAVE operation involves copying the console medium to : : an RT-11 virtual volume, which is a Files-11 file that : : is an image of the RT-11 console volume. : : : : A RESTORE operation involves copying the entire contents : : of a virtual volume to a console medium. : : : :Do you want to SAVE or RESTORE your console TU58? :RESTORE : : : :Enter file name of virtual disk [default SYS$DISK:CONSOLE.DSK]: : : : :Do you want log messages as files are copied? [Y/N, default Yes]: : : : :Enter console device drive (DDCU:)CSA1: : : : :Put your "SCRATCH" console TU58 into drive CSA1:, : :and type when ready: : : : : The RESTORE of your console TU58 is complete. : :..............................................................................: 4. If your system has a battery backup that is being used for power recovery, continue with procedure B (Page 10). If not go to step 5. 5. Update complete. Reboot the system to load PCS patches. 6. Fill out a LARS form noting that FCO 11750-I009 has been installed. (See Page 13 for detailed LARS instructions.) _ _ _ _ _ _ _ | FCO 11750-I009 | | | | | | | | | |d|i|g|i|t|a|l| | PAGE 9 OF 13 |_|_|_|_|_|_|_| | | _______________________________|_________________________________________ PROCEDURE B (DISK/PCS UPDATE PROCEDURE) ---------------------------------------- NOTES:1. To build the tape required in 1.3 below, see attached Appendix A). 2. To help answer question #4 (described in step 1.4.5) in this procedure, you must check the SYSTARTUP.COM file to determine if battery backup is being used for power recovery. o If the command @SYS$MANAGER:PCS750 RECOVER is used in the SYSTARTUP.COM file, battery backup is being used for power recovery. o If the command @SYS$MANAGER:PCS750 is used in the SYSTARTUP.COM file, wheather battery backup is present or not, means power recover is not being used. 3. For version 5.0 VMS, the command file to edit has been changed to SYS$MANAGER:SYSTARTUP_V5.COM PCS750 SOFTWARE UPDATE PROCEDURE: --------------------------------- 1. Under VMS: 1.1 Log in under system manager account. 1.2 Set default to [SYSUPD]. 1.3 Install PCS750KIT TU58 #3 in CSA1: (P/N = BE-T538F-ME) 1.4 Type "@VMSINSTAL PCS750xxx CSA1: Where xxx is the rev of the micropatch kit - eg: PCS750103 which indicates rev 103 of the PCS750.BIN file will be installed. 1.4.1 Questions asked by the update command file. There will be four questions asked: _ _ _ _ _ _ _ | FCO 11750-I009 | | | | | | | | | |d|i|g|i|t|a|l| | PAGE 10 OF 13 |_|_|_|_|_|_|_| | | _______________________________|_________________________________________ 1.4.2 QUESTION #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 (this document) will be printed on SYS$PRINT. 1.4.3 QUESTION #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 then answer YES. 1.4.4 QUESTION #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. 1.4.5 QUESTION #4: "If you have battery backup, do you want powerfail recovery ?" This question decides how a powerfail is handled. If you have a powerfail and you have battery backup, PCS will not be reloaded unless the PCS device driver is included along with the proper command file that defines that device driver. By answering "yes" to this question means the device driver (PCS750DRV) will be included with the PCS loader utility (PCS750UTL). You will be instructed to add a command line to your startup procedure so that if a powerfail occurs with battery backup, the driver will be awakened by the system to reload PCS. If you answer "no", the driver will not be included and PCS will not be reloaded on powerfail recovery. Note:If you have a battery backup option, we recommend a yes answer. 1.5 VMSINSTAL CHECKS After the questions have been answered, the update command file will put the files in the proper locations. When the update command file is complete, do the following checks: _ _ _ _ _ _ _ | FCO 11750-I009 | | | | | | | | | |d|i|g|i|t|a|l| | PAGE 11 OF 13 |_|_|_|_|_|_|_| | | _______________________________|_________________________________________ 1.5.1 The following are in SYS$SYSROOT:[SYSEXE]: PCS750.BIN PCS750UTL.EXE PCS750DRV.EXE (only if answered "yes" to question #4.) 1.5.2 The following are in SYS$SYSROOT:[SYSMGR] PCS750.COM 2.0 Update complete. Reboot the system to load PCS patches. 3.0 Verification of operation. After system re-boot, the system identification register should be checked for the proper Ucode revision level. This can be done by the following method: At the DCL "$" prompt type the following command. $ SID=F$getsyi("sid") $ Show Symbol SID If the proper PCS code has been loaded into PCS, the value 67 HEX should appear in the second byte of the ID register. ------------------------------------------------- | | 6 | 7 | X | X | ------------------------------------------------- If warm restart support was selected then: $ Show Device WDA0: This is the device driver and it should be present and unavailable if warm restart was selected. Device WDA0: will not be present if warm restart was not selected. 5. Fill out a LARS form noting that FCO 11750-I009 has been installed. (See Page 13 for detailed LARS instructions.) _ _ _ _ _ _ _ | FCO 11750-I009 | | | | | | | | | |d|i|g|i|t|a|l| | PAGE 12 OF 13 |_|_|_|_|_|_|_| | | _______________________________|_________________________________________ LARS EXAMPLE ------------ USA GIA EUROPE Activity - Contract and Warranty W U Y Non Contract/Non Warranty F F F DEC Option 11750 11750 11750 Type of Call M M M Action Taken D D I Fail Area-Module-FCO-Comments 11750-I009 11750-I009 11750-I009 Material Used _ _ _ _ _ _ _ | FCO 11750-I009 | | | | | | | | | |d|i|g|i|t|a|l| | PAGE 13 OF 13 |_|_|_|_|_|_|_| | | _______________________________|_________________________________________ APPENDIX A ---------- Creating PCS Micropatch Kit --------------------------- Requirements: 1. SYSTEM privileges. 2. Place all required PCS files in a separate directory. (Internal personnel can obtain files via Enet.) Required PCS files: KITINSTAL.COM PCS750UTL.OBJ PCS750.BIN PCSV3XDRV.OBJ PCS750.COM PCSV40DRV.OBJ PCS750103.A PCSV50DRV.OBJ PCS750DRV.MAR SUBMIT.DATA PCS750INS.DOC TEMPO.DIR PCS750MSG.OBJ TU583.DCOM PCS750OPR.OPT V5_CHANGES.TXT PCS750UTL.MAR (Install a scratch into CSA1:) $ INIT CSA1: PCSKIT $ @PCS_V5_KIT$:TU583 ----------- ----- : : : ------------> Build file. : ---------------------> Name of directory containing TU583.COM and all othe required PCS files. Answer questions as follows: Which kit would you like to build:PCS750103 On which device is the kit to be built:CSA1: \^ 11750 \\11750 \\JACKSON \\1989 \\FEB \\FCO_DOCS