$TXT Created by at CLN1G1.AAC.DOMAIN.EXT (KIDS) on Wednesday, 03/14/18 at 16:47 ============================================================================= Run Date: APR 13, 2018 Designation: OR*3*443 Package : OR - ORDER ENTRY/RESULTS REPORTING Priority: Mandatory Version : 3 SEQ #398 Status: Released Compliance Date: MAY 14, 2018 ============================================================================= Associated patches: (v)OR*3*350 <<= must be installed BEFORE `OR*3*443' Subject: ORDER DEBUG REPORT Category: - Routine Description: ============ This patch will resolve the following issue: 1. OR DEBUG REPORT - Undefined Error when attempting to print the report New Service Requests (NSRs): ---------------------------- N/A Patient Safety Issues (PSIs): ----------------------------- N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1. I11664086FY17 - OR DEBUG REPORT - Undefined Error Problem: -------- Undefined error (DL+7^ORDEBUG2 ^VA(200,0,0)) encountered when attempting to use RPC DEBUG REPORT [OR DEBUG REPORT] option. This was due to a misfiled entry in XTMP("CPRS DEBUG LOG"). Note: This was previously reported in SDM I11361183FY17, but the cause was not determined at the time and the region OI&T staff resolved the issue by killing off the bad entry in the global. Resolution: ----------- The RPC DEBUG REPORT [OR DEBUG REPORT] option has been modified to handle potentially erroneous entries by simply showing a blank where the name of the user would normally appear. Test Sites: ----------- Puget Sound HCS Software and Documentation Retrieval Instructions: -------------------------------------------------- This patch is being distributed through the National Patch Module, rather than via a host file. 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 patch and invoke the INSTALL/CHECK MESSAGE PackMan option. 2. Start up the Kernel Installation and Distribution System Menu [XPD MAIN]: Edits and Distribution ... Utilities ... Installation ... Select Kernel Installation & Distribution System Option: Installation --- Load a Distribution Verify Checksums in Transport Global Print Transport Global Compare Transport Global to Current System Backup a Transport Global Install Package(s) Restart Install of Package(s) Unload a Distribution 3. From this menu, you may elect to use the following options (When prompted for the INSTALL NAME, enter OR*3.0*443): a. Backup a Transport Global - This option will create a backup message of any routines exported with this patch. It will not backup any other changes such as DD's or templates. b. 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 (routines, DD's, templates, etc.). c. Verify Checksums in Transport Global - This option will allow you to ensure the integrity of the routines that are in the transport global. 4. Use the Install Package(s) option and select the package OR*3.0*443. a. When prompted "Want KIDS to INHIBIT LOGONs during the install? NO//", answer NO. b. When prompted "Want to DISABLE Scheduled Options and Menu Options and Protocols? NO//", answer NO. Post-Installation Instructions: ------------------------------- N/A Back-out/Rollback Strategy: -------------------------- In the event of a catastrophic failure, the Facility CIO may make the decision to back-out the patch. It is imperative that you have performed a backup of the routine included in this patch prior to installation. The back-out plan is to restore the routine from the backup created. No data was modified by this patch installation and, therefore, no rollback strategy is required. To verify the back-out completed successfully, ensure the checksum matches the pre-patch checksum from the patch descriptions. Routine Information: ==================== The second line of each of these routines now looks like: ;;3.0;ORDER ENTRY/RESULTS REPORTING;**[Patch List]**;Dec 17, 1997;Build 5 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: ORDEBUG2 Before: B5203678 After: B5524697 **350,443** Routine list of preceding patches: 350 ============================================================================= User Information: Entered By : Date Entered : NOV 03, 2016 Completed By: Date Completed: APR 11, 2018 Released By : Date Released : APR 13, 2018 ============================================================================= Packman Mail Message: ===================== $END TXT