============================================================================= Run Date: MAR 26, 2021 Designation: MAG*3*248 Package : MAG - IMAGING Priority: Mandatory Version : 3 SEQ #200 Status: Released Compliance Date: APR 26, 2021 ============================================================================= Subject: VistA Imaging - Background Processor Defect Patch Category: - Routine Description: ============ Description: This document describes MAG*3.0*248, a patch that provides fixes to the BACKGROUND PROCESSOR (BP). This patch addresses the following issues: 1. BP Verifier blacks out the word "From" in Range box when Range is selected in Scope 2. V12\Milwaukee Access Violation Errors appear regularly in BGP v235 3. BP Purge from P238 release causing Jukebox copies to be queued for no apparent reason 4. Fort Harrison, MT - Size zero JPGs are purging. The process cannot access the file because it is being used by another process. 5. LAS received reports of multiple messages being generated by purge job. Associated Patches: VistA Imaging MAG*3.0*248 must be installed after MAG*3.0*243. 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 Templates Associated: 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 Defect Tracking System Ticket(s) & Overview: 1. Defect 1099283 (Trouble Ticket #INC688805) BP Verifier blacks out word "From:" in Range box, when Range is selected in Scope Problem: -------- When ALL is selected in Scope in the BP Verifier, the word "From" is grey on a black background. When the user selects "Range", the grey characters turn black and cannot be seen. The background needs to be white as it is for "To." Resolution: ----------- Changed the background color to match the other selections (i.e. "Range") when "ALL" is selected. As a result, the background color is now readable when any selection is made. 2. Defect 1106110 (Trouble Ticket #INC7095776) V12\Milwaukee Access Violation Errors appear regularly in BGP v235 Problem: -------- An access violation message is displayed when the user accesses the BP Queue Processor application and clicks the Start button to begin processing. The access violation occurs because the Physical Reference field in the Tier 2 Network Location properties is not populated. A blank Physical Reference field indicates the Network location is not properly configured according to the Background Processor manual. Resolution: ----------- Added conditional check to determines if the value in file 2005.2, '1' is empty. If the value is empty, the application is forced to stop and the message "Network Location missing Physical Reference field. Application has stopped." is presented to the user. At this point, the user will add the Tier 2 network location and start the application. 3. Defect 1222892 (Trouble Ticket INC9443102) BP Purge from the MAG*3.0*238 release is causing Jukebox copies to be queued for no apparent reason. Problem: -------- MAG*3.0*238 added a size comparison before purging Tier 1. If a file is found to be a different size when comparing Tier 1 and Tier 2, it is not purged. An email is sent and an entry is made in the Purge Error log. These do not have Purge Criteria in the form of three numbers. However, there are thousands of entries with Purge Criteria of 1~1~8 or 1~2~8 are not being purged and are creating a new entry into the JUKEBOX queue. This is causing the image to be copied a second time to Tier 2. The files in Tier 1 and Tier 2 are the same size. In a busy site such as Orlando, the Jukebox queue is causing lags with the additional copies being queued. As a result, Orlando has stopped their purge process. The documentation in the User Manual for the BP shows the purge criteria for 1~1~8 or 1~2~8 as available for purge unless there is a size discrepancy. If a discrepancy is discovered, a copy will be queued. Observations: 1. It is not a good idea to copy from Tier 1 to Tier 2 without validating which is the proper file to copy. 2. The issue does not occur when there is a size difference. 3. This is happening for no known reason and seems to be for a large group of images as if a flag was stuck to "no purge". Resolution: ----------- To resolve the "purge action type" issue we added checks for "Tier 1" and "Tier 2" file size zero. If both files on "Tier 1" and "Tier 2" are size zero, we do not queue the copy and we skip to the next record. If both files are reported as zero, there may a problem either with Delphi code or with the Windows file reporting functions for network shares so we log both conditions and report the file sizes for future follow-up. For the situation where there is no "Tier 2" file or if the reported size on "Tier 2" is zero, we log the condition and queue a copy to the JukeBox. We then skip to the next record. Finally, if the file size is zero on "Tier 1", no copy occurs. We log the error condition and we skip to the next record. This reduces the number of JB copies enough the BP won't fall behind. Finally, we produce more detailed logging than with P243T3. To resolve the second and third issues (which involve missing data in the logs), we examined the VI Purge program code and corrected the output so it always includes all four columns in the screen grid/HTML file. This includes both the situation where data is missing from the screen grid/HTML and also for the situation where "Purge Criteria" is missing from "NOT PURGE" conditions on the screen grid/HTML file. 4. Defect IMAG-1717 (Trouble Ticket INC16808095) - Fort Harrison, MT - Size zero JPGs are purging. The process cannot access the file because it is being used by another process. Problem: -------- User experienced an issue when Jukebox and Schd Verifier both attempted to process the same image. The Jukebox log displayed an error reading "Jukebox copy not overwritten." The Verifier log displayed "The process cannot access the file because it is being used by another process." Resolution: ----------- In order to resolve this, we added the "FileInUse" check to the verify process in places where we make a copy of the file. These changes were made in the "Scan", "LocCopy" and "MakeABS" routines, which are the only routines that make a copy of that file. The "FileInUse" check will return "True" if another process has a lock on the file, and as a result, we write this message condition to the log file and skip that file and continue processing on the next file. This way, if the BP processor is in the process of working on a file, and the Verifier tries to access the file while BP is using it, it will issue a "file in use" message and log it and continue processing. 5. Defect 1254848 (Trouble Ticket INC10283143) - LAS received reports of multiple messages being generated by purge job. Problem: -------- LAS- Received reports of multiple messages being generated by a purge job. Why are multiple messages being generated and how can they be prevented? Resolution: ----------- In order to resolve this, we changed the BP Purge server selection code so that when the user makes the selection and clicks "start", the program does not change the default selection back to "ALL" like it was previously doing. This permits the user to keep the same selections and restart the process with the same parameters if desired. Selected/completed purged shares will remain in the list and the program can resume from where the Purge was stopped and those previous selections will not be wiped out until the purge job is completed. Test Sites: ----------- Milwaukee VA Medical Center (Milwaukee, WI) Cleveland VA Medical Center (Cleveland, OH) Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released using a host file. The host file is available at the following location: /srv/vista/patches/SOFTWARE/MAG3_0P248.KID Other Software Files: This release also includes other software files. These files can be obtained by accessing the URL: https://download.vista.domain.ext/index.html/SOFTWARE File Title File Name --------------------------------------------------------------------- Kernel Installation and MAG3_0P248.KID Distribution System (KIDS) build for MAG*3.0*248 Background Processor client MAG3_0P248_Background_Processor_Set up.exe installation file - New Documentation Title File Name --------------------------------------------------------------------- Patch Description for MAG*3.0*248 MAG3_0P248_Patch_Description.pdf Deployment, Installation, Back-Out, MAG3_0P248_DIBORG.pdf and Rollback Guide Patch Installation: ------------------- Supported Client Versions: When MAG*3.0*248 is released, the list of supported versions of Background Processor will change: Client Versions Supported: * 3.0.248 * 3.0.243 * 3.0.238 Client Versions No Longer Supported: * 3.0.235 * 3.0.222 * 3.0.214 Pre/Post Installation Overview: MAG*3.0*248 must be installed on the VistA System prior to running the new executables. This patch must be installed by the compliance date. All sites running VistA Imaging 3.0 must install the KIDS portion of this patch. This patch may be loaded while the VistA Imaging System is active. Installation will take less than one minute. Important: Any BP applications (including Queue Processor, Verifier, and Purge) that are running must be stopped and closed prior to the installation of the KIDS and Client software. Any image capture application (Clinical Capture and DICOM Gateway processing) or display application (Clinical Display and Telereader) can continue to run during the installation. Pre-Installation Instructions: Please refer to the Deployment, Implementation, Back-Out, and Rollback Guide (MAG3_0P248_DIBORG.pdf) for Pre-Installation instructions. Installation Instructions: 1. Use the Load a Distribution option contained on the Kernel Installation and Distribution System Menu to load the Host file. When prompted to "Enter a Host File:" enter /srv/vista/patches/SOFTWARE/MAG3_0P248.KID 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 (ex. MAG*3.0*248). 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 of any routines exported with this patch. It will not backup any other changes such as DDs or templates. 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 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?,' answer NO. ii. When prompted 'Want KIDS to INHIBIT LOGONs during the install?,' answer NO. Post-Installation Instructions: Restart all Background Processor applications that were stopped for installation, provided they are supported versions. Installing the BP Client: Please refer to the Deployment, Implementation, Back-Out and Rollback Guide (MAG3_0P248_DIBORG.pdf) for Client Installation instructions. Back-Out/Roll Back Plan: ------------------------ Please refer to the Deployment, Implementation, Back-Out and Rollback Guide (MAG3_0P248_DIBORG.pdf) for Client Installation instructions. Routine Information: VistA KIDS Checksums This section lists modified routines for the VistA KIDS build. For each routine, the second line will contain the following information: ;;3.0;IMAGING;**[Patch List]**;Mar 19, 2002;Build 7 CHECK1^XTSUMBLD is used to generate the checksums. Routine Checksums Routine Checksum Before Checksum After Patch List MAGQBUT4 97830931 97831735 **7,8,48,20,81,39,121, 135,196,198,214,222,235,238,243,248** MAGIP248 NEW 4110441 **248** Routine MAGIP248 is an installation routine that is automatically deleted after the KIDS installation. Routine Information: ==================== The second line of each of these routines now looks like: ;;3.0;IMAGING;**[Patch List]**;Mar 19, 2002;Build 7 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: MAGIP248 Before: n/a After: B4110441 **248** Routine Name: MAGQBUT4 Before: B97830931 After: B97831735 **7,8,48,20,81,39,121,135,196, 198,214,222,235,238,243,248** Routine list of preceding patches: 243 ============================================================================= User Information: Entered By : Date Entered : SEP 20, 2019 Completed By: Date Completed: MAR 25, 2021 Released By : Date Released : MAR 26, 2021 ============================================================================= Packman Mail Message: ===================== No routines included