$TXT Created by G at CHY0034.FO-BAYPINES.DOMAIN.EXT (KIDS) on Wednesday, 01/10/24 at 12:39 ============================================================================= Run Date: JAN 24, 2024 Designation: SD*5.3*866 Package : SD - SCHEDULING Priority: Mandatory Version : 5.3 SEQ #717 Status: Released Compliance Date: FEB 06, 2024 ============================================================================= Associated patches: (v)SD*5.3*694 <<= must be installed BEFORE `SD*5.3*866' (v)SD*5.3*818 <<= must be installed BEFORE `SD*5.3*866' (v)SD*5.3*846 <<= must be installed BEFORE `SD*5.3*866' (v)SD*5.3*861 <<= must be installed BEFORE `SD*5.3*866' (v)SD*5.3*864 <<= must be installed BEFORE `SD*5.3*866' Subject: VS GUI VERSION 1.7.52.0 Category: - Routine - Enhancement (Mandatory) - Data Dictionary Description: ============ VistA Scheduling (VS) Graphical User Interface (GUI) Release 1.7.52.0 and patch SD*5.3*866 includes several defect corrections and enhancements including: The new SDES GET CLINIC INFO3 RPC was created to file Special Instructions in the order in which they were entered when additional Special Instructions are entered. The VS GUI was updated so if the patient has a home phone stored in the database, this phone number will be displayed when the contact attempts information is viewed. The returned JSON object for the SDES BLOCK AND MOVE RPC was updated to conform to the established JSON formatting. The SDES SEARCH CLINIC ATTRIBUTES RPC was updated to accept an optional Length of appointment input parameter. When the optional length of appointment input parameter is sent in, the RPC will screen out clinics that don't have a matching length of appointment field (#1912). The new SDES2 CREATE RECALL REQUEST RPC was created and will contain the USER DUZ in the SDCONTEXT array. The USER DUZ will be stored on any new Recall Request that is created. The new SDES2 EDIT RECALL REQUEST RPC was created and will contain the USER DUZ in the SDCONTEXT array. The USER DUZ will be stored when editing and existing recall request. The new SDES2 DISPOSITION APPT REQ RPC was created and will contain the USER DUZ in the SDCONTEXT array. The USER DUZ will be used when dispositioning any appointment request. The new SDES2 DISPOSITION RECALL REQ RPC was created and will contain the USER DUZ in the SDCONTEXT array. The USER DUZ will be used when dispositioning any recall request. The new SDES2 CREATE APPOINTMENT RPC was created and will contain the USER DUZ in the SDCONTEXT array. The USER DUZ will be used when creating new appointment requests. The new SDES2 CHECKIN RPC was created and will contain the USER DUZ in the SDCONTEXT array. The USER DUZ will be used when checking in a patient. The VS GUI was updated so that when a user navigates away from the currently Selected request, the clinic drop down list for the calendar will clear so that appointments won't accidentally be booked into an incorrect clinic. The SDES READ CLINIC GROUP RPC was updated to return the CLINIC IEN or PROVIDER IEN based on the RESOURCE TYPE. The return JSON object description was also updated to document all the fields. The VS GUI was updated so that each time a new patient is selected, the clinic field for the old patient is cleared out and refreshed based on the newly selected patient. The new SDES2 GET PATIENT INFO RPC was created and will return assorted patient information based on the DFN. The SDES CREATE WALKIN APPT RPC was updated to utilize the latest SDES CHECKIN Code and it will utilize the time zone associated with the clinic to populate the CHECKIN field (#.03). The new SDES2 CHECK CLIN AVAIL DEFINED RPC was created and will return a flag of 1 if availability has been defined in the past for a given clinic and a 0 if availability has never been defined. If a clinic currently doesn't have availability, but availability has been defined in the past, the result is 1. The SDES2 EDIT CLINIC was updated to allow for the editing of the SCHEDULE ON HOLIDAYS? (#1918.5) field. The VS GUI was updated to default to the patient when only one patient is returned from a patient search. The VS GUI was updated so that correctly disposition and appointment when cancelling an appointment in Pending Appointments using a reason that will return the Appointment Request to the RM Grid. The SDES2 GET LAST SELECTED PAT RPC was updated to use the USER DUZ from the SDCONTEXT Input array to prevent the issue where the user is marked as sensitive when coming from "Load Last Selected" button. The VS GUI was updated to automatically close the eligibility window when the user performs a patient search and then selects a patient. The new SDES2 GET CANCELLED SLOTS RPC was created and will return cancelled slots within a given timeframe for a given clinic in JSON format. The SDES2 EDIT CLINIC logic was updated to allow the removal of the 'default' designation from both provider and diagnosis code. The validation logic for the Service field was updated to save the correct code for Neurology. This update applies to both the SDES2 CREATE CLINIC and SDES2 EDIT CLINIC RPCs. ************************************************************************** * GUI UPDATE NOTICE * * ---------------------------------------------------------------------- * * This patch MUST be installed before the GUI update for release * * 1.7.52.0 of VS is installed. * * * * * * The previous version of the VS GUI will not operate after this * * patch is installed. Therefore, VS GUI V1.7.52.0 and VistA patch * * SD*5.3*866 must be coordinated and installed during the same * * maintenance window. * * * * * ************************************************************************** Patch Components: ----------------- Files & Fields Associated: New/Modified/Deleted -------------------------- -------------------- SDES ERROR CODES New errors being Modified (#409.93) deployed File Name (Number) Field Name New/Modified/Deleted ------------------ ---------- -------------------- 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 ----------- ---- -------------------- SDESRPC Broker Modified 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 --------------------- -------------------- SDES BLOCK AND MOVE Modified SDES GET CLINIC INFO3 New SDES2 CHECK CLIN AVAIL DEFINED New SDES2 CHECKIN New SDES2 CREATE APPOINTMENT New SDES2 CREATE RECALL REQUEST New SDES2 DISPOSITION APPT REQ New SDES2 DISPOSITION RECALL REQ New SDES2 EDIT CLINIC Modified SDES2 EDIT RECALL REQUEST New SDES2 GET CANCELLED SLOTS New SDES2 GET LAST SELECTED PAT Modified SDES2 GET PATIENT INFO New SDES2 GET RESOURCE GROUP New SDES2 PATIENT SEARCH Modified SDES2 SEARCH CLINIC ATTRIBUTES Modified Parameter Definitions Associated: --------------------------------- N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- JIRA tasks: =========== 1) VSE-6406: Clinic Special Instructions are alphabetized, rather than being saved sequentially. Problem: IVC Testers have reported that Special Instructions entered for Clinics appear to be filed in alphabetical order, rather than preserving the sequence of lines as entered by the user. Moreover, when retrieved as detailed in our discovery ticket VAS-1345, this appears to result from using each instruction as a subscript of the SPECIALINSTRUCT array in the VALIDATESI^SDESCLINICSET2 subroutine. The result is that special instructions are presented to the end user in the wrong sequence in a persistent manner. This is occurring in the SDES code. SDES2 does not do this so they are in the correct order. Resolution: The new SDES GET CLINIC INFO3 RPC was created to file Special Instructions in the order in which they were entered when additional Special Instructions are entered. 2) VSE-6444: VS GUI: Home phone number does not appear in Contact Attempts. Problem: A patient's home phone number is not displaying in the Contact Attempts. If the patient has a cell phone number, that number populates as both the cell phone number as well as the home phone number. Resolution: The VS GUI was updated so if the patient has a home phone stored in the database, this phone number will be displayed when the contact attempts information is viewed. 3) VSE-6456: VistA: Modify SDES BLOCK AND MOVE to send output as properly formatted JSON. Problem: As an Acheron developer I would like to receive properly formatted JSON return from the SDES BLOCK AND MOVE RPC so that I can parse it correctly. Resolution: The returned JSON object for the SDES BLOCK AND MOVE RPC was updated to conform to the established JSON formatting. 4) VSE-6457: VistA: Modify SDES SEARCH CLINIC ATTRIBUTES to have an optional input parameter. Problem: As a VSA developer I want SDES SEARCH CLINIC ATTRIBUTES to have an optional input parameter (Length of appointment) which would only select clinics within the search with the matching clinic appointment length. I also want to add the clinic appointment length to the output object. Resolution: The SDES SEARCH CLINIC ATTRIBUTES RPC was updated to accept an optional Length of appointment input parameter. When the optional length of appointment input parameter is sent in, the RPC will screen out clinics that don't have a matching length of appointment field (#1912). 5) VSE-6470: SDES2 Priority 2: Rewrite SDES CREATE RECALL REQ 2 in the SDES2 Namespace. Problem: As a Mumps developer I want to rewrite SDES CREATE RECALL REQ 2 in the SDES2 namespace so that I receive the originating requestor's USER DUZ in the SDCONTEXT array so that I can store the correct user in the database. Resolution: The new SDES2 CREATE RECALL REQUEST RPC was created and will contain the USER DUZ in the SDCONTEXT array. The USER DUZ will be stored on any new Recall Request that is created. 6) VSE-6474: SDES2 Priority 4: Rewrite SDES EDIT RECALL REQ 2 in the SDES2 Namespace. Problem: As a Mumps developer I want to rewrite the SDES EDIT RECALL REQ 2 in the SDES2 namespace so that I have the USER DUZ in the SDCONTEXT array to store the correct requesting user in the database. Resolution: The new SDES2 EDIT RECALL REQUEST RPC was created and will contain the USER DUZ in the SDCONTEXT array. The USER DUZ will be stored when editing and existing recall request. 7) VSE-6475: SDES2 Priority 5: Rewrite SDES DISPOSITION APPT REQ in the SDES2 Namespace. Problem: As a Mumps developer I want to rewrite the SDES DISPOSITION APPT REQ in the SDES2 namespace so that I have the USER DUZ in the SDCONTEXT array to store the correct requesting user in the database. Resolution: The new SDES2 DISPOSITION APPT REQ RPC was created and will contain the USER DUZ in the SDCONTEXT array. The USER DUZ will be used when dispositioning any appointment request. 8) VSE-6479: SDES2 Priority 6: Rewrite SDES DISPOSITION RECALL REQ in the SDES2 namespace. Problem: As a Mumps developer I want to rewrite the SDES DISPOSITION RECALL REQ in the SDES2 namespace so that I have the USER DUZ in the SDCONTEXT array to store the correct requesting user in the database. Resolution: The new SDES2 DISPOSITION RECALL REQ RPC was created and will contain the USER DUZ in the SDCONTEXT array. The USER DUZ will be used when dispositioning any recall request. 9) VSE-6484: SDES2 Priority 10: Rewrite SDES CREATE APPOINTMENTS in the SDES2 namespace. Problem: As a Mumps developer I want to rewrite the SDES CREATE APPOINTMENTS in the SDES2 namespace so that I have the USER DUZ in the SDCONTEXT array to store the correct requesting user in the database. Resolution: The new SDES2 CREATE APPOINTMENT RPC was created and will contain the USER DUZ in the SDCONTEXT array. The USER DUZ will be used when creating new appointment requests. 10) VSE-6485: SDES2 Priority 11: Rewrite SDES CHECKIN in the SDES2 namespace. Problem: As a Mumps developer I want to rewrite the SDES CHECKIN in the SDES2 namespace so that I have the USER DUZ in the SDCONTEXT array to store the correct requesting user in the database. Resolution: The new SDES2 CHECKIN RPC was created and will contain the USER DUZ in the SDCONTEXT array. The USER DUZ will be used when checking in a patient. 11) VSE-6533: VS GUI: Navigating away from a Consult Request for a service/specialty does not clear the service/specialty. Problem: When a user selects a Consult or Procedure Request in the RM Grid the specialty procedure is selected in the clinic drop down list for the calendar. When the user navigates away from the request to a different request the clinic drop down list for the calendar does not clear. The user could book an appointment in an incorrect clinic if they do not notice that the clinic did not clear. Resolution: The VS GUI was updated so that when a user navigates away from the currently Selected request, the clinic drop down list for the calendar will clear so that appointments won't accidentally be booked into an incorrect clinic. 12) VSE-6552: VistA: Modify SDES READ CLINIC GROUP to return CLINIC IEN or PROVIDER IEN based on the RESOURCE TYPE. Problem: As a VSA developer I want SDES READ CLINIC GROUP RPC to return the CLINIC IEN or PROVIDER IEN based on the RESOURCE TYPE. Need to update SDES READ CLINIC GROUP RPC documentation to include all the fields in the return object. Resolution: The SDES READ CLINIC GROUP RPC was updated to return the CLINIC IEN or PROVIDER IEN based on the RESOURCE TYPE. The return JSON object description was also updated to document all the fields. 13) VSE-6554: VS GUI: Clinic not been updated. Problem: The clinic appears immediately when a user brings up any request type. However, if the user changes to a different patient, information is supposed to be updated (clinic, appointment, or request screen), but the clinic is not being updated and remains a carryover from the previous patient session. Resolution: The VS GUI was updated so that each time a new patient is selected, the clinic field for the old patient is cleared out and refreshed based on the newly selected patient. 14) VSE-6589: VistA: Create SDES2 RPC for Patient Information. Problem: Create new SDES2 RPC to take DFN as an input parameter and update SDES2 PATIENT SEARCH to have GAF value, Priority Group, and Enrollment Subgroup. Correct RPC description documentation for SDES2 PATIENT SEARCH RPC. Resolution: The new SDES2 GET PATIENT INFO RPC was created and will return assorted patient information based on the DFN. 15) VSE-6591: VistA: Modify SDES CREATE WALKIN APPT to call new check in routine. Problem: As a Mumps developer I would like to modify SDES CREATE WALKIN APPT to call the new check in routine so that I am calling latest SDES CHECKIN code. If system is in eastern time and clinic is in Mountain, then the time populated in CHECKIN will be converted to the mountain time. Example: if walk-in is entered at 12:00 system time, but the clinic is 10:00, then the stored value in the CHECK-IN file will be stored as 10:00. Check in entered will continue to be system time. Resolution: The SDES CREATE WALKIN APPT RPC was updated to utilize the latest SDES CHECKIN Code and it will utilize the time zone associated with the clinic to populate the CHECKIN field (#.03). 16) VSE-6593: VistA: New SDES2 RPC return back - has the given clinic ever had any availability defined? Problem: Create a new RPC that returns back a flag of whether or not a clinic has had availability. Logic is already in SDEC NOAVAIL. Needs to be brought into SDES2 code and brought up to standards. Resolution: The new SDES2 CHECK CLIN AVAIL DEFINED RPC was created and will return a flag of 1 if availability has been defined in the past for a given clinic and a 0 if availability has never been defined. If a clinic currently doesn't have availability, but availability has been defined in the past, the result is 1. 17) VSE-6606: VistA: Update SDES2 EDIT CLINIC to allow for the editing of the holiday field. Problem: Modify SDES2 EDIT CLINIC to allow the user to edit the SCHEDULE ON HOLIDAYS? (#1918.5) field. Resolution: The SDES2 EDIT CLINIC was updated to allow for the editing of the SCHEDULE ON HOLIDAYS? (#1918.5) field. 18) VSE-6611: VS GUI defect around the patient search/selection. Problem: If I do a search and 1 result is back, i.e. Test,Chad, and I hit Enter it just closes the search modal instead of selecting that patient. Resolution: The VS GUI was updated to default to the patient when only one patient is returned from a patient search. 19) VSE-6641: VS GUI: Appt Request Disposition issue after Cancelling Appt. Problem: After cancelling an appointment in Pending Appointments, using a reason that will return the Appointment Request to the RM Grid, user has to Disposition the Request twice in order for the Request to fall off the RM grid. Resolution: The VS GUI was updated so that correctly disposition and appointment when cancelling an appointment in Pending Appointments using a reason that will return the Appointment Request to the RM Grid. 20) VSE-6673: VistA: Modify SDES2 GET LAST SELECTED PAT to use SDCONTEXT USER DUZ. Problem: As an VSS developer, I want to modify SDES2 GET LAST SELECTED PAT to use SDCONTEXT USER DUZ and remove the input parameter so that the correct user DUZ is stored in the database. Code also needs to be updated to calls POPULATES^SDES2PATSEARCH and passing in DUZ of user. This will correct issue with patient being marked as sensitive when coming from "Load Last Selected" button. Resolution: The SDES2 GET LAST SELECTED PAT RPC was updated to use the USER DUZ from the SDCONTEXT Input array to prevent the issue where the user is marked as sensitive when coming from "Load Last Selected" button. 21) VSE-6693: VS GUI: While in Windowed mode VS GUI will move to a right justified position on the screen when a new patient is searched. Problem: If a user is in windowed mode in VS GUI and they perform a patient search, once a patient is selected, the window moves and the search dialog stays open with the eligibility window. To proceed the eligibility window then needs to be closed. Resolution: The VS GUI was updated to automatically close the eligibility window when the user performs a patient search and then selects a patient. 22) VSE-6906: VistA: Create a new SDES2 RPC to return all future canceled slots given a clinic ID. Problem: As a CCM developer I want to call an RPC where I can pass in the clinic ID so that the object returned contains all future canceled slots and is the same format as SDES GET CLIN AVAILABILITY. The RPC can accept a Start Date and an End Date but must be able to return all future canceled slots without any limitations. Resolution: The new SDES2 GET CANCELLED SLOTS RPC was created and will return cancelled slots within a given timeframe for a given clinic in JSON format. 23) VSE-7001: VistA: Update SDES2 EDIT CLINIC to allow removal of default designation from both provider and diagnosis Problem: Update SDES2 EDIT CLINIC to allow removal of the 'default' designation from both provider and diagnosis. Related to VAS-1703. Resolution: The SDES2 EDIT CLINIC logic was updated to allow the removal of the 'default' designation from both provider and diagnosis code. 24) VSE-7021: VistA: Correct issue with neurology service not saving on creation or edit. Problem: Need to correct issue in the SDES2 CREATE CLINIC and SDES2 EDIT CLINIC RPCs where the Service of Neurology is not being saved correctly. Resolution: The validation logic for the Service field was updated to save the correct code for Neurology. This update applies to both the SDES2 CREATE CLINIC and SDES2 EDIT CLINIC RPCs. Test Sites: ----------- El Paso, TX (ELP) San Diego, CA (SDC) Software and Documentation Retrieval Instructions: ---------------------------------------------------- Software is distributed by PackMan message and MSI software. NOTE: There are two installation files. The file titled VISTASCHEDULINGGUIINSTALLER_1_7_52_0_P.MSI is the production VS GUI installation file. The file titled VISTASCHEDULINGGUIINSTALLER_1_7_52_0_T.MSI is the preproduction VS GUI file. Other Software Files: This release also includes documentation and other software files. They can be obtained at: https://download.vista.domain.ext/index.html/SOFTWARE/ Documentation Title File Name FTP Mode -------------------------------------------------------------------------- VS GUI R1.7.52.0 INSTALLER VISTASCHEDULINGGUIINSTALLER_1_7_52_0_P.MSI Binary VS GUI R1.7.52.0 INSTALLER VISTASCHEDULINGGUIINSTALLER_1_7_52_0_T.MSI Binary VS GUI R1.7.52.0 VDD VS_GUI_1_7_52_0 VDD Binary VS GUI R1.7.52.0 DIBR VS_GUI_1_7_52_0 DIBR Binary VS GUI R1.7.52.0 Release Notes VS_GUI_1_7_52_0 RN Binary VS GUI R1.7.52.0 Technical Manual VS_GUI_1_7_52_0 TM Binary PIMS Technical Manual PIMS_TM Binary 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/ Patch Installation: ------------------- GUI Installation Instructions: ------------------------- Sites that employ the VistA Consolidated Server (VACS) installation process will be alerted to the new GUI via an action item from Office of Information and Technology (OIT) Software Product Management (SPM) Services. Follow the detailed instructions in the Action Item email for VistA Consolidated Server (VACS) installation. The Information Operations (IO) HBMC Field Operations (FO) Application Division will lead and coordinate deployment activities with EUO, Client Technology, Citrix Back Office, and Area Managers, and other OIT and business partners as required. The released software package is available at: https://download.vista.domain.ext/index.html/SOFTWARE Release Manager Point of Contact: Name: Stevens Jack Email: jack.stevens1@domain.ext Pre/Post Installation Overview: ------------------------------- Routine SDES866P will update SDEC SETTINGS (#409.98) file. Routine will run at the end of patch installation process. Pre-Installation Instructions: ------------------------------ N/A Setup/Configuration 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. 1. Choose the PackMan message containing this patch. 2. Choose the INSTALL/CHECK MESSAGE PackMan option. 3. From the KIDS Menu, select the Installation Menu. From this menu, you may elect to use the following options. When prompted for the INSTALL NAME, enter SD*5.3*866. a. Backup a Transport Global - This option will create a backup message of any components exported with this patch. You are prompted to select "R" for Routines or "B" for Build. For this patch, backing up the "B"uild is suggested. Select one of the following: B Build R Routines Enter response: Build 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, DDs, 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. From the Installation Menu, select the Install Package(s) option and when prompted for the INSTALL NAME, enter SD*5.3*866. 5. If prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of Install? NO//' respond NO. 6. When prompted "Want KIDS to INHIBIT LOGONs during the install? NO//" respond NO. 7. If prompted "Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//" respond NO. 8. If prompted "Delay Install (Minutes): (0 - 60): 0//" respond 0. Post-Installation Instructions: ------------------------------- Post install routine SDES866P will automatically run at the end of the installation process. After the post install has finished running, sites can delete the SDES866P routine using the Delete Routines [XTRDEL] if they wish. Back-Out Plan/Roll Back Plan: ----------------------------- 1. Load the Backup MailMan Message a. Go into MailMan and find the backup message created in step 3a of the installation process and read that message. b. At the "Type to continue or '^' to exit:" prompt enter ^ to get to the command prompt. c. At the command prompt enter X for eXtract and press enter. d. At the "Select PackMan function:" prompt enter 6 for INSTALL/CHECK MESSAGE and press enter. e. At the "OK to Continue with Load? NO//" prompt, type YES and press enter. f. At the "Want to Continue with Load? YES//" prompt, press enter. g. Exit MailMan. 2. Go Into the Kernel Installation & Distribution System (KIDS) and load and install the backup like you would a regular patch. a. Enter D ^XUP at the command prompt. b. At the "Select OPTION NAME:" prompt, enter Kernel Installation & Distribution System" and press enter. c. From the main KIDS menu, select the Installation ... option. d. From the Installation ... option, select 6 Install Package(s). e. At the "Select INSTALL NAME:" prompt enter SD*5.3*866b. f. If prompted for "Want KIDS to INHIBIT LOGONs during the install? NO//" take the default by pressing enter. g. If prompted for "Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//" take the default by pressing enter. h. At the DEVICE: prompt, enter the output device of your choice. i. Verify that the SD*5.3*866b backup installs without any issues. The VS GUI NATIONAL and VS GUI LOCAL entries in the SDEC SETTINGS (#409.98) file needs to be reverted to 1.7.51. If 1.7.52.0 VS GUI was installed, it will need to be reverted to VS GUI 1.7.51.1. Routine Information: ==================== The second line of each of these routines now looks like: ;;5.3;Scheduling;**[Patch List]**;Aug 13, 1993;Build 22 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: SDECAPI Before: B60666254 After: B62126868 **627,694,866** Routine Name: SDES2APPTUTIL Before: n/a After: B92055567 **866** Routine Name: SDES2ARCLOSE Before: n/a After: B16284167 **866** Routine Name: SDES2CHECKIN Before: n/a After: B35666783 **866** Routine Name: SDES2CHKCAVAIL Before: n/a After: B1636441 **866** Routine Name: SDES2CLINUT Before:B133417975 After:B142875568 **853,857,866** Routine Name: SDES2CREATEAPPT Before: n/a After:B132627097 **866** Routine Name: SDES2DISPRECALL Before: n/a After: B13404674 **866** Routine Name: SDES2EDITCLIN Before:B128879224 After:B133392069 **853,857,864,866** Routine Name: SDES2GETCANSLOTS Before: n/a After: B26843982 **866** Routine Name: SDES2GETPATINFO Before: n/a After: B1333340 **866** Routine Name: SDES2GETRESGROUP Before: n/a After: B7959402 **866** Routine Name: SDES2GETSTORDPAT Before: B1802809 After: B2021826 **861,866** Routine Name: SDES2PATSEARCH Before:B104992811 After:B101627108 **864,866** Routine Name: SDES2RECLLREQ Before: n/a After: B81047809 **866** Routine Name: SDES2SEARCHCLNAT Before: n/a After: B31106538 **866** Routine Name: SDES2VAL44 Before:B184764058 After:B180410212 **853,857,864,866** Routine Name: SDES2VALISODTTM Before: B4545555 After: B6284142 **853,866** Routine Name: SDES2VALUTIL Before: B28961790 After: B36207318 **853,861,866** Routine Name: SDES866P Before: n/a After: B2544222 **866** Routine Name: SDESBLOCKANDMOVE Before: B51880301 After: B51481870 **853,866** Routine Name: SDESCRTWALKIN Before: B48197639 After: B47234575 **823,846,866** Routine Name: SDESRTVCLN3 Before: n/a After:B135198869 **866** Routine Name: SDRRISRU Before: B21237844 After: B21748366 **536,627,648,799,818,866** Routine list of preceding patches: 694, 818, 846, 861, 864 ============================================================================= User Information: Entered By : Date Entered : OCT 19, 2023 Completed By: Date Completed: JAN 24, 2024 Released By : Date Released : JAN 24, 2024 ============================================================================= Packman Mail Message: ===================== $END TXT