$TXT Created by L at KRNIRIS.FO-OAKLAND.DOMAIN.EXT (KIDS) on Wednesday, 02/01/23 at 15:47 ============================================================================= Run Date: MAR 21, 2023 Designation: XU*8*772 Package : XU - KERNEL Priority: Mandatory Version : 8 SEQ #624 Status: Released Compliance Date: APR 21, 2023 ============================================================================= Associated patches: (v)XU*8*662 <<= must be installed BEFORE `XU*8*772' Subject: ALERTS FIXES Category: - Routine Description: ============ This patch fixes three problems: 1) errors; 2) request to prevent accidental purging/deleting of entries in ALERT TRACKING (#8992.1) file; and 3)GETUSER1^XQALDATA returns undefined result. Problem 1: errors in FORWARD^XQALDATA --------- Defect Tracking System Ticket(s): INC22510891 Error Messages with Vista and CPRS INC22364372 XQALDATA subscript error INC21484688 CPRS will not open/broker error : M ERROR = INC23387468 R4 - CPRS Surrogate Issues: $ZE= FORWARD+10^XQALDATA INC23541219 cprs error INC24178711 CPRS-receiving a debugging message INC25021160 CPRS Potential surrogates of deferred alerts are getting two different types errors. In two cases a previous event did not properly delete the processed alerts for the original recipient, leaving bad entries in the list of Alerts in their "XQA" node. In one case, the zero node had no alert data; in the other case, the data in the ALERT TRACKING (#8992.1) file had been previously deleted (not normal) for a TERMINATED user. There is also a third case where there is no bad entries but the logic in the code is incorrect. Resolution: ----------- a) routine XQALDATA was modified to check for null values and prevent these errors b) an incremental LOCK was added to prevent leaving bad "XQA" node when another event is also deleting/modifying the same entry. Problem 2: Prevent purging/deleting of alerts in ALERT TRACKING (#8992.1) file --------- Defect Tracking System Ticket(s): INC24097729 prevent accidental purging/deleting of alerts Request to modify a line of code to remove the comment character to aid in preventing accidental purging of alerts in the ALERT TRACKING (#8992.1) file that need to be retained for litigation hold. NOTE: Entries in the ALERT (#8992) file can still be deleted as before. Resolution: ----------- Line KILLARCH+1^XQALDEL was modified to skip the removal of entries in the ALERT TRACKING (#8992.1) file. Problem 3: GETUSER1^XQALDATA returns undefined result --------- Defect Tracking System Ticket(s): INC25791892 Alerts API GETUSER1^XQALDATA returns undefined result Resolution 1.b triggered another potential bug which returns an undefined result when the user has no alerts Resolution: ----------- The @ROOT reference is properly defined and initialized to 0 Patch Components: ----------------- Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- N/A Forms Associated: Form Name File Number New/Modified/Deleted --------- ----------- -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A Security Keys Associated: Security Key Name ----------------- N/A Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- N/A Remote Procedures Associated: Remote Procedure Name New/Modified/Deleted --------------------- -------------------- N/A Parameter Definitions Associated: Parameter Name New/Modified/Deleted -------------- -------------------- N/A Additional Information: ----------------------- Blood Bank Team Coordination: N/A New Service Requests (NSRs): N/A Patient Safety Issues (PSIs): N/A Test Sites: ---------- Butler Milwaukee Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. Documentation describing the new functionality is included in this release. Documentation can be found on the VA Software Documentation Library at: https://www.domain.ext/vdl/. Documentation can also be obtained at https://download.vista.domain.ext/index.html/SOFTWARE. Documentation Title File Name --------------------------------------------------------------------- Kernel 8.0 & Kernel Toolkit 7.3 Systems Management Guide KRN_8_0_SM.DOCX and KRN_8_0_SM.PDF Patch Installation: ------------------- Pre/Post Installation Overview: Pre-Installation Instructions: This patch may be installed with users on the system although it is recommended that it be installed during non-peak hours to minimize potential disruption to users. This patch should take less than 5 minutes to install. Installation Instructions: 1. Choose the PackMan message containing this build. Then select the INSTALL/CHECK MESSAGE PackMan option to load the build. 2. From the Kernel Installation and Distribution System Menu, select the Installation Menu. From this menu, A. Select the Verify Checksums in Transport Global option to confirm the integrity of the routines that are in the transport global. When prompted for the INSTALL NAME enter the patch or build name. XU*8.0*772 NOTE: Using will not bring up a Multi-Package build even if it was loaded immediately before this step. It will only bring up the last patch in the build. B. Select the Backup a Transport Global option to create a backup message. You must use this option and specify what to backup; the entire Build or just Routines. The backup message can be used to restore the routines and components of the build to the pre-patch condition. i. At the Installation option menu, select Backup a Transport Global ii. At the Select INSTALL NAME prompt, enter your build XU*8.0*772 iii. When prompted for the following, enter R for Routines or B for Build. Select one of the following: B Build R Routines Enter response: Build iv. When prompted Do you wish to secure this message? NO//, press and take the default response of NO. v. When prompted with, Send mail to: Last name, First Name, press to take default recipient. Add any additional recipients. vi. When prompted with Select basket to send to: IN//, press and take the default IN mailbox or select a different mailbox. C. You may also elect to use the following options: i. Print Transport Global - This option will allow you to view the components of the KIDS build. ii. Compare Transport Global to Current System - This option will allow you to view all changes that will be made when this patch is installed. It compares all of the components of this patch, such as routines, DDs, templates, etc. D. Select the Install Package(s) option and choose the patch to install. i. If prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of Install? NO//', press and take the default response of NO. ii. When prompted 'Want KIDS to INHIBIT LOGONs during the install? NO//', press and take the default response of NO. iii. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//', press and take the default response of NO. Post-Installation Instructions: N/A Back-Out/Roll Back Plan: ------------------------ If assistance is needed to rollback/backout the patch please, log a ServiceNow(SNOW) ticket so the development team can assist in this process. Note: During installation, if the option to back-up the routines was executed as directed, "Backup a Transport Global" (Step 2B.), then the routines will have the ability to be restored from the 'backup' MailMan message that was generated. However, the Kernel Installation and Distribution System (KIDS) process does NOT perform a back up of the other VistA software components, such as RPCs. Routine Information: ==================== The second line of each of these routines now looks like: ;;8.0;KERNEL;**[Patch List]**;Jul 10, 1995;Build 5 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: XQALDATA Before:B118403951 After:B123380008 **207,285,443,513,602,653,734, 662,772** Routine Name: XQALDEL Before: B70136763 After: B71202995 **6,24,65,114,174,285,443,602, 653,662,772** Routine list of preceding patches: 662 ============================================================================= User Information: Entered By : Date Entered : MAY 13, 2022 Completed By: Date Completed: MAR 20, 2023 Released By : Date Released : MAR 21, 2023 ============================================================================= Packman Mail Message: ===================== $END TXT