$TXT Created by CLN2G2.AAC.DOMAIN.EXT (KIDS) on Thursday, 10/04/18 at 17:32 ============================================================================= Run Date: NOV 01, 2018 Designation: GMRC*3*104 Package : GMRC - CONSULT/REQUEST TRACKING Priority: Mandatory Version : 3 SEQ #93 Status: Released Compliance Date: DEC 02, 2018 ============================================================================= Associated patches: (v)GMRC*3*6 <<= must be installed BEFORE `GMRC*3*104' Subject: DELETING SUB-SERVICES Category: - Data Dictionary - Routine Description: ============ Patch GMRC*3*104 addresses the following issue: 1. Deleting sub-service entries in the REQUEST SERVICES [#123.5] file causes data integrity issues. Patch Components: ----------------- Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- REQUEST SERVICES FILE SERVICE NAME (#.01) Modified (#123.5) The DELETE TEST definition is being modified by this patch. Before patch installation: DELETE TEST: 1,0)= I $P(^GMR(123.5,DA,0),U)="SUICIDE HOTLINE " D EN^DDIOL("...Mandatory Entry. Please see G MRC*3.0*57 for details...") After patch installation: DELETE TEST: 1,0)= S %=$$CHKDEL^GMRCDDX(DA) I $L(%) D EN^DDIOL(%) Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1. Left over "AC" x-ref for Consult Sub-services Problem: -------- ServiceNow ticket INC0069411 reported that the Duplicate Sub-Service Report showed a phantom sub-service relationship caused by orphan "AC" and "APC" index entries in the REQUEST SERVICES [#123.5] file. The exact cause of the orphan entries was not found but it was determined that deleting entries being used as sub-services caused data integrity issues and inadvertent duplicate sub-service entries. According to the ticket, it is a known issue that duplicate sub-services cause crashes when using the Custom Consult view in the CPRS Consults Tab. Resolution: ----------- The data dictionary entry for the REQUEST SERVICES [#123.5] file was modified to stop the deletion of entries that are a sub-service of another entry and show the following message. The modified routine is ^GMRCDDX. This entry cannot be deleted until it is removed as a sub-service of: This is a required response. Enter '^' to exit Test Sites: ----------- Heartland - West Atlanta VA Health Care System Patch Installation Instructions: -------------------------------- This patch can be loaded with users in the system but it is recommended that it be installed when user activity is low. Installation time will be less than 2 minutes. 1. Choose the PackMan message containing this patch 2. Choose the INSTALL/CHECK MESSAGE PackMan option. 3. From the Kernel Installation and Distribution System Menu, select the Installation Menu. 4. From the Installation Menu, select the Backup a Transport Global and when prompted for the INSTALL NAME enter the patch GMRC*3.0*104. This option will create a backup message of the routine(s) exported with this patch. This will be routine GMRCDDX. It will not backup any other changes such as DDs or templates. If for any reason the patch is to be rolled back, this backup will be required to restore the patch's routine(s) to the pre-installation version(s). 5. From the Installation Menu you may elect to use the following options. When prompted for the INSTALL NAME enter the patch GMRC*3.0*104: a. Verify Checksums in Transport Global - This option will allow you to ensure the integrity of the routines that are in the transport global. b. Print Transport Global - This option will allow you to print only a summary of the patch, to print a summary of the patch and the routines in the transport global, or to print only the routines in the transport global. c. 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's routines, DDs, templates, etc.). 6. From the Installation Menu, select the Install Package(s) option and choose the patch to install. 7. When prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of Install? NO//' 8. When prompted 'Want KIDS to INHIBIT LOGONs during the install? NO//' 9. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//' 10. If prompted 'Delay Install (Minutes): (0 - 60): 0//' respond 0. Backout/Rollback Strategy: -------------------------- In the event of a catastrophic failure, the Facility CIO may make the decision to back-out the patch. Because this patch contains data dictionary changes, back-out must be done with the participation of the sustainment team. The back-out plan is to restore the SERVICE NAME field's delete test and can be provided upon request. Please call the national help desk or enter a help desk ticket, if required. No data was modified by this patch installation and, therefore, no data rollback strategy is required. To verify the back-out completed successfully, ensure the SERVICE NAME field's delete test no longer matched the patch version. To restore routine(s) backup from MailMan: ------------------------------------------ 1. Enter the MailMan Menu [XMUSER] 2. At the Select MailMan Menu Option prompt select the Read/Manage Messages Option (RML). 3. At the Read mail in basket prompt: select the basket the routine backup Message is stored in. 4. At the Enter message number or command: prompt select the message which has the routines. 5. At the Type to continue or '^' to exit: prompt enter '^' to skip to the message action prompt. 6. At the Enter message action (in SELECTED basket): prompt type in X for Xtract PackMan. 7. At the Select PackMan function: prompt type in 6 for INSTALL/CHECK MASSAGE. 8. The user will be presented with the following warning and a prompt: Warning: Installing this message will cause a permanent update of globals and routines. Do you really want to do this? NO// At this prompt type in Y for YES to install the backup copies. 9. The user will be presented with the following message and a prompt: Routines are the only parts that are backed up. NO other parts are backed up, not even globals. You may use the 'Summarize Message' option of PackMan to see what parts the message contains. Those parts that are not routines should be backed up separately if they need to be preserved. Shall I preserve the routines on disk in a separate back-up message? YES// Answering yes to this prompt is optional. The site can reinstall the patch. If the user answers YES to this prompt: 9.1 At the Subject: prompt type in a descriptive subject. 9.2 At the Send mail to: prompt select the user to send this message. 9.3 At the Select basket to send to: prompt select the basket to send this message. It will default to the IN basket. 9.4 At the And Send to: prompt select any additional user to send thi Message to or hit enter to continue. A message similar to the following will be presented to the user. Building PackMan backup message with subject backup PackMan backup message [999999999] sent. Line 2 Message #99999999 Unloading Routine GMRCDDX (PACKMAN_BACKUP) If the user answers NO to this prompt, the user will be presented with a message similar to this: Line 2 Message #99999999 Unloading Routine GMRCDDX (PACKMAN_BACKUP) 10. At the Enter message action (in SELECTED basket): prompt accept the default of Ignore. 11. To verify the roll-back completed successfully, ensure the routine TIUCL1 checksum Matches the pre-patch checksum from the patch description. Routine Information: ==================== The second line of each of these routines now looks like: ;;3.0;CONSULT/REQUEST TRACKING;**[Patch List]**;Aug 13, 2018;Build 9 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: GMRC104 Before: n/a After: B1764728 **104** Routine Name: GMRCDDX Before: B1063223 After: B4176613 **1,6,104** Routine list of preceding patches: 6 ============================================================================= User Information: Entered By : Date Entered : APR 24, 2018 Completed By: Date Completed: NOV 01, 2018 Released By : Date Released : NOV 01, 2018 ============================================================================= Packman Mail Message: ===================== $END TXT