$TXT Created by TRAN,BA at NXT.KERNEL.FO-OAKLAND.MED.VA.GOV (KIDS) on Monday, 10/30/06 at 05:38 ============================================================================= Run Date: JAN 08, 2007 Designation: XU*8*369 Package : XU - KERNEL Priority: Mandatory Version : 8 SEQ #358 Status: Released Compliance Date: FEB 08, 2007 ============================================================================= Associated patches: (v)XU*8*262 <<= must be installed BEFORE `XU*8*369' (v)XU*8*390 <<= must be installed BEFORE `XU*8*369' (v)XU*8*393 <<= must be installed BEFORE `XU*8*369' Subject: Compare local/national checksums Category: - Routine - Enhancement (Mandatory) - Data Dictionary Description: ============ Remedy tickets: - HD0000000162270 - HD0000000140769 Test Sites: - WASHINGTON, DC VAMC - MONTANA HCS - DAYTON, OH VAMC XU*8.0*369 Patch XU*8.0*369 contains two new options that provide the following functionality to sites: 1. Compare local/national checksums report [XU CHECKSUM REPORT]: This option compares national routine checksums to local routine checksums. National checksum information is stored in the ROUTINE file (#9.8). The report contains the following sections and information: a. ROUTINES MARKED FOR LOCAL TRACKING() This section lists all routines that are marked for "Local - report". In order to get a comparison as shown below for the routine ANDAFTP you need manually enter a CHECKSUM VALUE in the ROUTINE file using the output from CHECK1^XTSUMBLD if the CHECKSUM VALUE is Null. Sample output: Routine CHKSUM BASE Our CHKSUM ======= ========== =========== ANDAFTP B6609520 B6609517 || CHECKSUM VALUE ENTERED MANUALLY IN ROUTINE FILE b. ROUTINES WITH THE CHECKSUM OFF() Routine Nat CHKSUM Our CHKSUM Our Patch Loc Mod Patches Needed ===== ========== ========== ======= ====== ========= This section lists Class I routines that are marked for national tracking where the local checksum value differs from the national checksum value. If the option can determine the routine is locally modified it will indicate YES in the Loc Mod column, if it can determine the routine is unmodified but needs patching it will list NO in the Loc Mod column and then display patches needed to bring the routine in compliance. If the routine indicates a patch that hasn't been released, TESTING will appear in the Patches Needed column. When the option can not determine if a routine is locally modified or a TEST patch it will state unknown in appropriate column. The Our Patch column indicates the local patch level of the routine. A count of routines in this section is provided. c. ROUTINES NOT FOUND IN THE SYSTEM() Routine Nat CHKSUM Nat Last Patch ===== ========== ========== This section lists Class I routines that are marked for national tracking that do not exist at the site (local system). Routine name, released checksum, and last patch release are listed. A count of routines in this section is provided. d. ROUTINES NOT MARKED FOR TRACKING () This section provides a count of routines that do not have field #6 of file #9.8 set to National Tracking. e. ROUTINES WITH MATCHING CHECKSUMS () This section provides a count of routines where local checksum matches national checksum f. ROUTINE FILE TOTAL ENTRIES COUNT () This section provides a count of entries in the routine file (#9.8) 2. Load/refresh checksum values into ROUTINE file [XU CHECKSUM LOAD]: This option updates the routine file with the latest checksum values from FORUM via the HL LOGICAL LINK NODE of "XUMF FORUM". NOTE: The routine XU8P369 makes the change that the READ TIMEOUT of the logical link be set to 600 on the "XUMF FORUM" logical link. 3. Data Dictionary (DD) changes to the ROUTINE file (#9.8) are as follows: This patch also updates data dictionary for CHECKSUM REPORT file (#6) of Routine file (#9.8): 9.8,6 CHECKSUM REPORT 6;1 SET '0' FOR Local - don't report; '1' FOR Local - report; '2' FOR National - report; '3' FOR National - Deleted or NOT tracked; LAST EDITED: OCT 17, 2006 DESCRIPTION: Entries flagged with "National - report" should not be changed, with "FOR National - Deleted or NOT tracked" for routines that do not exist in the system. Sites may determine if they want reports on checksum differences for local routines by selecting "Local - report". IMPORTANT INFORMATION NEED TO BE NOTED: ====================================== - Please note that the ROUTINE file on FORUM is not completely up to date. - If you find any problem with the ROUTINE file on FORUM, please report direct to Ba Tran at ba.tran@med.va.gov or Wally Fort at wally.fort@med.va.gov. Please do not log a Remedy ticket. - The report will improve as FORUM is updated. - Users may run the option Load/refresh checksum values into ROUTINE file [XU CHECKSUM LOAD] to update the routine file before running the Compare local/national checksums report [XU CHECKSUM REPORT] - Users may use FileMan to set CHECKSUM REPORT field (#6) for routines: Select OPTION: ENTER OR EDIT FILE ENTRIES INPUT TO WHAT FILE: ROUTINE// EDIT WHICH FIELD: ALL// 6 CHECKSUM REPORT THEN EDIT FIELD: Select ROUTINE NAME: XUGOT1 CHECKSUM REPORT: ? Choose from: 0 Local - don't report 1 Local - report 2 National - report 3 National - Deleted or NOT tracked CHECKSUM REPORT: Blood Bank Team Coordination ============================ Clearance - 1/6/2005 EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch XU*8*369 contains changes to a package referenced in VHA OI SEPG SOP 192-023 Review of VISTA Patches for Effects on VISTA Blood Bank Software. This patch does not alter or modify any VistA Blood Bank software design safeguards or safety critical elements functions. RISK ANALYSIS: Changes made by patch XU*8*369 have no effect on Blood Bank software functionality, therefore RISK is none. Routine Summary ============== The following routines are included in this patch. The second line of each of these routines now looks like: ;;8.0;KERNEL;**[patch list]**;Jul 10, 1995 Checksums ========= Sites should use CHECK^XTSUMBLD to verify checksums. Rtn Nm Chksum Before Chksum After Patch List ====== ============= ============ ========== XU8P369 new 88114 **369** XUGOT new 4554897 **369** XUGOT1 new 21628355 **369** XUMFH 8679369 8933914 **206,209,217,218,262, 335,261,390,369** XUMFI 9849785 8611764 **206,217,218,335,261,369** XUMFI0 new 1874315 **369** XUMFP 2483997 2519138 **206,217,246,262,369** XUMFPMFS 5113686 5750115 **262,369** XUMFPZL7 1318596 2610645 **262,369** Note: XU8P369 will be deleted upon installation. Installation Instructions ========================= 1. Users ARE allowed to be on the system during the installation. However, it is recommended that the patch be installed during non-peak time. It will take about five minutes to install the patch, but you may queue the installation if you wish. 2. You DO NOT need to stop TaskMan or the background filers. 3. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This option will load the KIDS package onto your system. 4. The patch has now been loaded into a Transport global on your system. You now need to use KIDS to install the Transport global. On the KIDS menu, under the 'Installation' menu, use the following options: Verify Checksums in Transport Global Print Transport Global Compare Transport Global to Current System Backup a Transport Global On the KIDS menu, under the 'Installation' menu, use the following option: Install Package(s) Select INSTALL NAME:XU*8.0*369 ========== Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO == Want KIDS to INHIBIT LOGONs during the install? YES// NO == Want to DISABLE Scheduled Options, Menu, Options, and Protocols? NO == Routine Information: ==================== The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: XU8P369 Before: n/a After: B127935 **369** Routine Name: XUGOT Before: n/a After: B14969110 **369** Routine Name: XUGOT1 Before: n/a After: B68922750 **369** Routine Name: XUMFH Before: B77218033 After: B81261510 **206,209,217,218,262,335,261, 390,369** Routine Name: XUMFI Before: B79789892 After: B61663922 **206,217,218,335,261,369** Routine Name: XUMFI0 Before: n/a After: B4427792 **369** Routine Name: XUMFP Before: B22178504 After: B22292581 **206,217,246,262,369** Routine Name: XUMFPMFS Before: B18122564 After: B21142938 **262,369** Routine Name: XUMFPZL7 Before: B2126203 After: B5372481 **262,369** ============================================================================= User Information: Entered By : METCALF,ROGER A Date Entered : OCT 29, 2004 Completed By: SINGH,GURBIR Date Completed: JAN 05, 2007 Released By : TILLIS,LEWIS Date Released : JAN 08, 2007 ============================================================================= Packman Mail Message: ===================== $END TXT