$TXT Created by at MPI.DOMAIN.EXT (KIDS) on Wednesday, 04/16/25 at 07:43 ============================================================================= Run Date: JUN 03, 2025 Designation: XU*8*799 Package : XU - KERNEL Priority: Mandatory Version : 8 SEQ #652 Status: Released Compliance Date: JUL 18, 2025 ============================================================================= Associated patches: (v)XU*8*480 <<= must be installed BEFORE `XU*8*799' (v)XU*8*693 <<= must be installed BEFORE `XU*8*799' (v)XU*8*731 <<= must be installed BEFORE `XU*8*799' (v)XU*8*733 <<= must be installed BEFORE `XU*8*799' (v)XU*8*779 <<= must be installed BEFORE `XU*8*799' (v)XU*8*795 <<= must be installed BEFORE `XU*8*799' Subject: KERNEL VISTA ENHANCEMENTS - ENTERPRISE USER SEARCH REBOOT Category: - Routine - Other - Enhancement (Mandatory) - Data Dictionary Description: ============ ************************************************************************** IMPORTANT: SEE THE 'Post-Installation Instructions' SECTION BELOW FOR REQUIRED MANUAL TASK CONFIGURATION STEPS WARNING: To be able to use the enhanced 'Add a New User to the System' [XUSERNEW] menu option, users MUST have previously setup their Personal Identification Verification (PIV) card to login to VistA! See KERNEL Patch XU*8.0*702 for setup instructions. Only Users with a defined Security ID [SECID : field #205.1 in the NEW PERSON (#200) file] in VistA are allowed to perform an Enterprise Search. Obtaining a Security ID can be accomplished by utilizing the 'Link My Account' functionality in the Identity Access Management (IAM) Toolkit. ************************************************************************** XU*8.0*480, XU*8.0*693, XU*8.0*731, XU*8.0*733, XU*8.0*779 and XU*8.0*795 are the required builds for patch XU*8.0*799. The following enhancements/issues exported in this patch are needed to support the Master Veteran Index (MVI) implementation of Enterprise User Identity when adding, editing and/or terminating entries in the NEW PERSON (#200) file in VistA. Enhancement #1 -------------- To support the enterprise provisioning of users and allow for monitoring of user profile changes, the following Data Dictionary (DD) changes have been made: - Enabled auditing on the following fields in the NEW PERSON (#200) file as part of the post-installation process: EMAIL ADDRESS (#.151) NPI ENTRY STATUS (#41.98) NPI (#41.99) SECID (#205.1) SUBJECT ORGANIZATION (#205.2) SUBJECT ORGANIZATION ID (#205.3) UNIQUE USER ID (#205.4) ADUPN (#205.5) NETWORK USERNAME (#501.1) - Created the NEW PERSON FIELD MONITOR (#8933.1) file to serve as a container to track the changes to NEW PERSON (#200) fields that need to be broadcast out to the Person Service Identity Management (PSIM) system via Web Services. *Note: Record level cross-references (X-REFs) indexes "ACXMIT" and "C" were also created for this file. Only a single entry for each modified DUZ will be created per day. The FIELD(S) MODIFIED (#1) will be continuously appended to with the field(s) that were modified for the user that day (See AVIAM* X-REF below), with the exception of LAST SIGN-ON DATE/TIME (#202), which will only be appended to the list once regardless of how many times they sign in/out that day. Due to the possibility that this file was NOT removed during the backout of Entered in Error patch XU*8.0*663 any entries currently existing in this file will be deleted during the post-initialization process in routine XU8P799. - Created the 'AVIAM' new style record X-REF to allow MVI to capture changes on the following fields in the NEW PERSON (#200) file which will add/update entries in the NEW PERSON FIELD MONITOR (#8933.1) file to identify those NEW PERSON (#200) fields that have been changed for the user that day and need to be transmitted/broadcasted out to PSIM: NAME (#.01) EMAIL ADDRESS (#.151) SEX (#4) DOB (#5) DISUSER (#7) SSN (#9) TERMINATION DATE (#9.2) NPI (#41.99) PRIMARY MENU OPTION (#201) LAST SIGN-ON DATE/TIME (#202) SECID (#205.1) SUBJECT ORGANIZATION (#205.2) SUBJECT ORGANIZATION ID (#205.3) UNIQUE USER ID (#205.4) ADUPN (#205.5) NETWORK USERNAME (#501.1) - Created the NEW PERSON FIELD MONITOR PURGE (#875) field in the KERNEL SYSTEM PARAMETERS (#8989.3) file to indicate the number of days that transmitted records in the NEW PERSON FIELD MONITOR (#8933.1) file should be maintained before being purged/deleted. DATA NAME GLOBAL DATA ELEMENT TITLE LOCATION TYPE ----------------------------------------------------------------------- 8989.3,875 NEW PERSON FIELD MONITOR PURGE 875;1 NUMBER INPUT TRANSFORM: K:+X'=X!(X>999)!(X<10)!(X?.E1"."1N.N) X LAST EDITED: JUN 22, 2020 HELP-PROMPT: Enter the number of days (10-999) that NEW PERSON FIELD MONITOR (#8933.1) records should be maintained before being purged. NOTES: - #8933.1 records containing a 'PENDING' transmission value will NOT be purged/deleted from the file. - The post-install routine XU8P799 will initialize this field with a default value of 365 (days) upon installation of this patch (XU*8.0*799). Enhancement #2 -------------- The 'Add a New User to the System' [XUSERNEW] and 'Grant Access by Profile' [XUSERBLK] menu options have been modified to now execute an Enterprise Search, prompting the user for the individual's Veteran Affairs (VA) Email Address, their Network Username or Traits specific to that user to use in the lookup. If searching by Email Address or Network Username and a match is NOT initially found, then additional traits (ie., Name, SSN and optionally their Date of Birth (DOB) and/or Gender) are then prompted for and an additional Enterprise Search is performed. Note: If searching by Traits, then the initial search will be skipped and the user will be immediately prompted for the user's Trait Information that will be used to perform the Enterprise Search. If a user(s) is ultimately found/returned, then their identifying traits from the Enterprise will be displayed for selection. Upon selection of one of these displayed record(s), the Enterprise traits will then be added to the VistA NEW PERSON (#200) file and any traits from VistA not known at the Enterprise (including the Site's Station Number and the user's DUZ) will be filed at the Enterprise. If the user is NOT found at the Enterprise, then a Service Ticket should be logged as all new users being added to VistA should already be known at the Enterprise. Note: The following traits can be added/updated by the Enterprise in VistA's NEW PERSON (#200) file: NAME File 200, Field .01 STREET ADDRESS 1 File 200, Field .111 STREET ADDRESS 2 File 200, Field .112 STREET ADDRESS 3 File 200, Field .113 CITY File 200, Field .114 STATE File 200, Field .115 ZIP CODE File 200, Field .116 EMAIL ADDRESS File 200, Field .151 SEX File 200, Field 4 DOB File 200, Field 5 SSN File 200, Field 9 NPI File 200, Field 41.99 SECID File 200, Field 205.1 SUBJECT ORGANIZATION File 200, Field 205.2 SUBJECT ORGANIZATION ID File 200, Field 205.3 UNIQUE USER ID File 200, Field 205.4 ADUPN File 200, Field 205.5 NETWORK USER NAME File 200, Field 501.1 NOTE: Only Users with a defined Security ID [SECID : field #205.1 in the NEW PERSON (#200) file] in VistA are allowed to perform an Enterprise Search. Obtaining a Security ID can be accomplished by utilizing the 'Link My Account' functionality in the Identity Access Management (IAM) Toolkit. Enhancement #3 -------------- A new option XUS IAM NPFM BATCH UPDATE has been created to monitor the NEW PERSON FIELD MONITOR (#8933.1) file for changes to identified NEW PERSON (#200) fields (See Enhancement #1). This option calls routine EN1^XUIAMNPB which loops through the 'ACXMIT' cross-reference (x-ref) of the NEW PERSON FIELD MONITOR (#8933.1) file, which is created when a specific list of NEW PERSON (#200) fields are modified. This modified data is transmitted to the Identity Access Management (IAM) system via the Service Provisioning Markup Language (SPML) using Web Services. After transmission, the REQUIRES TRANSMISSION (#.03) field is set to 'NO' and the LAST TRANSMITTED DATE/TIME (#.04) field is marked as NOW in the NEW PERSON FIELD MONITOR (#8933.1) file. NOTE: The fields being monitored (See Enhancement #1 above related to the "AVIAM" X-REF) are transmitted up to the IAM system through the MPI_PSIM_NEW EXECUTE web service when they are changed. Any changes to these fields can cause a variety of things to occur on IAM, such as removing the entry for the site/DFN (Data File Number) from the VistA IDs table that is associated with an individuals Personal Identity Verification (PIV) card when the user is terminated or when the DISUSER flag is set to 'Yes'. If the data from the IAM system includes SECID, but it is determined to belong to a record that is different than the one that is being updated in VistA, then the following fields will NOT be updated: o SECID File 200, Field 205.1 o SUBJECT ORGANIZATION File 200, Field 205.2 o SUBJECT ORGANIZTION ID File 200, Field 205.3 o UNIQUE USER ID File 200, Field 205.4 o ADUPN File 200, Field 205.5 o NETWORK USERNAME File 200, Field 501.1 WARNING: If the data on any of the following fields are updated and transmitted but does not match the IAM system, then data from the IAM system will be pushed back down to VistA to update those changed fields to match IAM. IAM is the authoritative source for these data elements and the fields must match the IAM system. EMAIL ADDRESS File 200, Field .151 SECID File 200, Field 205.1 SUBJECT ORGANIZATION File 200, Field 205.2 SUBJECT ORGANIZATION ID File 200, Field 205.3 UNIQUE USER ID File 200, Field 205.4 NETWORK USER NAME File 200, Field 501.1 NOTE: This new option needs to be scheduled in Taskman to run every 600 seconds with SPECIAL QUEUEING defined as STARTUP. Enhancement #4 -------------- A new option XUS IAM NPFM PURGE (which calls routine EN2^XUIAMNPB) has been created to delete all entries from the NEW PERSON FIELD MONITOR (#8933.1) file that are older than the number of days specified in the NEW PERSON FIELD MONITOR PURGE (#875) field in the KERNEL SYSTEM PARAMETERS (#8989.3) file. Deletion of any of these old entries can only occur when the REQUIRES TRANSMISSION (#.03) field in the NEW PERSON FIELD MONITOR (#8933.1) file is NOT equal to 'YES'. NOTE: If the NEW PERSON FIELD MONITOR PURGE (#875) field in the KERNEL SYSTEM PARAMETERS (#8989.3) file is NOT defined, then the number of days will automatically default to 365. NOTE: This new option needs to be scheduled in Taskman to run DAILY after normal business hours with SPECIAL QUEUEING defined as STARTUP. Enhancement #5 -------------- During execution of the option MPI VIEW/EDIT NEW PERSON DATA on the MVI system to delete an individual's National Provider Identifier (NPI) value at a Veterans Affairs Medical Center (VAMC), the remote procedure call (RPC) [XUS MVI NEW PERSON UPDATE] NOT only deletes the NPI (#41.99) value in the NEW PERSON (#200) file, but also, the NPI ENTRY STATUS (#41.98) field value and its corresponding NPI entry in the EFFECTIVE DATE/TIME (#42) field multiple as well. The software assumed that an EFFECTIVE DATE/TIME (#42) field entry would exist (and it was supposed to), but records have been found where that was NOT the case, causing FileMan (FM) to return an error when filing the information (FILE^DIE) as the Internal Entry Number String (IENS) did NOT get defined correctly in the FileMan Data Array (FDA). This error doesn't result in issues with the data since the NPI didn't exist in the multiple, but routine XUMVINPU has been modified to now validate that the NPI entry to be deleted is already populated in the EFFECTIVE DATE/TIME (#42) field multiple before continuing. Enhancement #6 -------------- A new option XUS IAM USER TERMINATE (which calls routine FTOP^XUIAMDD1) has been created and added as an item to the XU USER TERMINATE extended action option to allow the Identity Access Management (IAM) team to know when NEW PERSON (#200) file records that have future termination dates have been subsequently terminated by the background job XUAUTODEACTIVATE so that the SPML message to PSIM can be triggered, as well as executing any other IAM needed down-stream processes. Enhancement #7 -------------- A new option 'Template User Add' [XUSERTEM] has been created and attached to the User Management [XUSER] menu option that will allow for the creation of New "Template" Users in the NEW PERSON (#200) file as previously accomplished prior to these enhancements by bypassing all of the NEW Enterprise features detailed in this patch. These "Template" users are utilized by the Grant Access By Profile [XUSERBLK] option. NOTE: The 'Template User Add' [XUSERTEM] option is basically a copy of the 'Add a New User to the System' [XUSERNEW] option so that when executed it can bypass the Enterprise features, which is determined by the option name passed to the process. Enhancement #8 -------------- A new option 'Template Grant Access by Profile' [XUSERBLK TEMPLATE] has been created and attached to the User Management [XUSER] menu option that will allow for the creation of a new template user profile based on an existing template. This new template user can then be used as a template profile for adding and/or editing users through the Grant Access By Profile [XUSERBLK] option. Issue #1 -------- During initial installation of patch XU*8.0*663 at sites before it was pulled back, it was determined that some sites were having issues with missing NAME COMPONENTS (#10.1) field values in the NEW PERSON (#200) file and/or dangling pointer values to the NAME COMPONENTS (#20) file. This issue may be due to the site NOT completing the 'Name Component' clean-up process that was distributed decades earlier. The post-init routine XU8P799 will queue off a task to loop through all of the NEW PERSON (#200) file records to fix any missing/dangling pointers discovered in the NAME COMPONENTS (#10.1) field in the NEW PERSON (#200) file and/or the NAME COMPONENTS (#20) file. Note: Upon completion of the task, an email will be generated to the installer and the Master Patient Index (MPI) Development team for that site listing the total number of NEW PERSON (#200) file records and the number of records that were updated due to any missing/dangling pointer values indicated above. Issue #2 -------- During unit testing of the XUS IAM USER TERMINATE (Enhancement #6) process above, it was determined that if the 'Purge Flag' which was released in patch XU*8.0*645 is NOT set that the subscribers to the XU USER TERMINATE Protocol event were NOT being notified that users were terminated. After some analysis, it was determined that this was an oversight when it was implemented. Therefore a minor code change was implemented in routine XUSTERM so that if the 'Purge Flag' is NOT set that any subscribers to the XU USER TERMINATE protocol event will still be notified when a user with a future termination date has been terminated. NOTE: If the 'Purge Flag' is set at the site then subscribers were already being notified of the terminations. This subscriber notification issue would ONLY be encountered when the 'Purge Flag' was NOT set at the site. NOTE: During Initial Operating Capability (IOC) testing, it was discovered that: o An increase in daily mailman messages generated may occur from the ENGINEERING IT EQUIPMENT MODULE if the terminated user has active equipment assignments since the subscribers to the XU USER TERMINATE protocol event are being notified of termination events regardless of the 'PURGE' flag setting. o The site may see the following message displayed when the Deactivate a User [XUSERDEACT] option is used to terminate/deactivate a user's account: HMP*2.0*12 - shutdown of the eHMP Project This extraneous message is only displayed as a result of subscribers now being notified of termination events when the "Purge" flag is NOT set and because the ELECTRONIC HEALTH MANAGEMENT PLATFORM (eHMP) did NOT remove their subscriber ("HMP XU EVENTS") to the User terminate event [XU USER TERMINATE] option, but just entered the OUT OF ORDER MESSAGE above when the package was decommissioned in 2017. To prevent this message from displaying the post-init process in routine XU*8.0*799 will clean-up/remove the [HMP XU EVENTS] menu option from the following protocol OPTIONs if it exists: o New User Event [XU USER ADD] o User Change Event [XU USER CHANGE] o User terminate event [XU USER TERMINATE] Patch Components ================ Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- NEW PERSON FIELD MODIFICATION DATE (#.01) *NEW FILE MONITOR (#8933.1) USER (#.02) REQUIRES TRANSMISSION (#.03) LAST TRANSMITTED DATE/TIME (#.04) LAST EDITED BY (#.05) FIELD(S) MODIFIED (#1) KERNEL SYSTEM NEW PERSON FIELD MONITOR MODIFIED (New Field) PARAMETERS (#8989.3) PURGE (#875) Forms Associated: Form Name File # New/Modified/Deleted --------- ------ -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- XU USER TERMINATE EXTENDED ACTION MODIFIED XUS IAM NPFM BATCH RUN ROUTINE NEW UPDATE XUS IAM NPFM PURGE RUN ROUTINE NEW XUS IAM USER TERMINATE ACTION NEW XUSER MENU MODIFIED XUSERBLK TEMPLATE RUN ROUTINE NEW XUSERTEM RUN ROUTINE NEW 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: New Service Requests (NSRs) ---------------------------- N/A Patient Safety Issues (PSIs) ----------------------------- N/A Defect Tracking System Ticket(s) & Overview ------------------------------------------- N/A Test Sites: ---------- Beckley VAMC (WV) Columbus VAMC (OH) Dayton VAMC (OH) Eastern Colorado HCS (CO) SNOW Change Order #: ------------------- Beckley VAMC: CHG0600879 Columbus VAMC: CHG0600036 Dayton VAMC: CHG0600074 Eastern Colorado HCS: CHG0597987 Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. Other Software files: 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 Systems Management: KRN_8_0_SM_SIGNON_SECURITY_UG.PDF Signon/Security User Guide KRN_8_0_SM_SIGNON_SECURITY_UG.DOCX Kernel 8.0 and Kernel Toolkit 7.3 KRN8_0TM.PDF Technical Manual KRN8_0TM.DOCX Note: Direct VA KERNEL Documentation access on the VDL can be found at: http://www.domain.ext/vdl/application.asp?appid=10 Patch Installation: Pre/Post Installation Overview ------------------------------ The post-installation process will: - Create the New-Style record X-REF 'AVIAM' on the NEW PERSON (#200) file - Initialize the NEW PERSON FIELD MONITOR PURGE (#875) field in the KERNEL SYSTEM PARAMETERS (#8989.3) file - Delete any existing entries in the NEW PERSON FIELD MONITOR (#8933.1) file if applicable - Clean-up any missing and/or dangling pointers in the NAME COMPONENTS (#10.1) field in the NEW PERSON (#200) file and/or the NAME COMPONENTS (#20) file Note: An Email message to the installer and MPI Development Team will be generated detailing the total number of NEW PERSON (#200) file records and the number of records requiring an update at the site. - Enable AUDITING on the following fields in the NEW PERSON (#200) file: o EMAIL ADDRESS (#.151) o NP ENTRY STATUS (#41.98) o NPI (#41.99) o SECID (#205.1) o SUBJECT ORGANIZATION (#205.2) o SUBJECT ORGANIZATION ID (#205.3) o UNIQUE USER ID (#205.4) o ADUPN (#205.5) o NETWORK USERNAME (#501.1) - Delete the [HMP XU EVENTS] menu option from the following protocol OPTIONs if it exists: o New User Event [XU USER ADD] o User Change Event [XU USER CHANGE] o User terminate event [XU USER TERMINATE] 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 1 minute to install and may be queued. The following OPTIONs should be disabled during installation: Grant Access by Profile [XUSERBLK] Edit an Existing User [XUSEREDIT] Add a New User to the System [XUSERNEW] Deactivate a User [XUSERDEACT] Reactivate a User [XUSERREACT] 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. (ex. XU*8.0*799) 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*799 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 your build? 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//', answer NO. ii. When prompted 'Want KIDS to INHIBIT LOGONs during the install? NO//', answer NO. iii. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//', answer YES. a. When prompted 'Enter options you wish to mark as 'Out Of Order':', select the following option: Option Name Menu Text ----------- --------- [XUSERBLK] Grant Access by Profile [XUSEREDIT] Edit an Existing User [XUSERNEW] Add a New User to the System [XUSERDEACT] Deactivate a User [XUSERREACT] Reactivate a User Press the Enter key when you are done selecting options. b. When prompted 'Enter protocols you wish to mark as 'Out Of Order':', press the Enter key. c. When prompted 'Delay Install (Minutes): (0 - 60): 0//', answer 15. Post-Installation Instructions ------------------------------ Schedule the following new Tasks using the Schedule/Unschedule Options [XUTM SCHEDULE] option on the TASKMAN MANAGEMENT [XUTM MGR] menu: - OPTION: XUS IAM NPFM BATCH UPDATE QUEUED TO RUN AT WHAT TIME: T@xxx Note: Where xxx is 10min or more from the current time. RESCHEDULING FREQUENCY: 600S SPECIAL QUEUEING: STARTUP - OPTION: XUS IAM NPFM PURGE QUEUED TO RUN AT WHAT TIME: T+1@xxx Note: Where xxx is any time after normal business hours. RESCHEDULING FREQUENCY: 1D SPECIAL QUEUEING: STARTUP Back-Out/Roll Back Plan ----------------------- This patch contains routine, option and file (Including cross-reference) changes. In the event that it is determined that this patch should be backed out, the site should perform a restore using the back up of the BUILD created in Installation Instruction Step 2B. Additional Manual Steps: 1. Delete the new-style index 'AVIAM' from the NEW PERSON (#200) file using the FM Cross-Reference A Field [DIXREF] option on the UTILITY FUNCTIONS menu: What type of cross-reference (Traditional or New)? Traditional// NEW Modify what File: PROTOCOL// NEW PERSON (787 entries) Select Subfile: Current Indexes on file #200: 9 'ADEG' index 10 'ANAME' index 18 'AXUHUI' index 21 'ATR' index 55 'B' index 81 'AUSER' index 170 'AOIUID' index 207 'AVIAM' index Choose E (Edit)/D (Delete)/C (Create): Delete Which Index do you wish to delete? 207 AVIAM Are you sure you want to delete the index definition? NO// YES Index definition deleted. Do you want to execute the old kill logic now? NO 2. UnSchedule/Delete the following Tasks using the Schedule/Unschedule Options [XUTM SCHEDULE] option on the TASKMAN MANAGEMENT [XUTM MGR] menu: - XUS IAM NPFM BATCH UPDATE - XUS IAM NPFM PURGE 3. Ensure the following routines have been deleted: - XU8P799 - XUIAMDD1 - XUIAMNPB - XUIAMPR - XUIAMPR1 4. Using FM, ensure the following options have been deleted: - XUS IAM NPFM BATCH UPDATE - XUS IAM NPFM PURGE - XUS IAM USER TERMINATE - XUSERBLK TEMPLATE - XUSERTEM 5. Using FM, delete the following entries if they exist: a. NEW PERSON FIELD MONITOR (#8933.1) file: VA FileMan Version 22.2 Enter or Edit File Entries Print File Entries Search File Entries Modify File Attributes Inquire to File Entries Utility Functions ... Data Dictionary Utilities ... Transfer Entries Other Options ... Select VA FileMan Option: Utility Functions Verify Fields Cross-Reference A Field Identifier Re-Index File Input Transform (Syntax) Edit File Output Transform Template Edit Uneditable Data Mandatory/Required Field Check Key Definition Select Utility Functions Option: Edit File Modify what File: TASKS// NEW PERSON FIELD MONITOR (524 entries) Do you want to use the screen-mode version? YES// NO NAME: NEW PERSON FIELD MONITOR Replace @ DO YOU WANT JUST TO DELETE THE 524 FILE ENTRIES, & KEEP THE FILE DEFINITION? No// N (No) IS IT OK TO DELETE THE '^XTV(8933.1)' GLOBAL? Yes// Y (Yes) SURE YOU WANT TO DELETE THE ENTIRE 'NEW PERSON FIELD MONITOR' FILE? Y (Yes) Deleting the DATA DICTIONARY... Deleting the INPUT TEMPLATES... Deleting the PRINT TEMPLATES... Deleting the SORT TEMPLATES... Deleting the FORMS... Deleting the BLOCKS... Verify Fields Cross-Reference A Field Identifier Re-Index File Input Transform (Syntax) Edit File Output Transform Template Edit Uneditable Data Mandatory/Required Field Check Key Definition Select Utility Functions Option: b. The NEW PERSON FIELD MONITOR PURGE (#875) field in the KERNEL SYSTEM PARAMETERS (#8989.3) file: Enter or Edit File Entries Print File Entries Search File Entries Modify File Attributes Inquire to File Entries Utility Functions ... Data Dictionary Utilities ... Transfer Entries Other Options ... Select VA FileMan Option: Modify File Attributes Do you want to use the screen-mode version? YES// NO Modify what File: TASKS// KERNEL SYSTEM PARAMETERS (1 entry) Select FIELD: NEW PERSON FIELD MONITOR PURGE LABEL: NEW PERSON FIELD MONITOR PURGE Replace @ SURE YOU WANT TO DELETE THE ENTIRE 'NEW PERSON FIELD MONITOR PURGE' FIELD? Y (Yes) OK TO DELETE 'NEW PERSON FIELD MONITOR PURGE' FIELDS IN THE EXISTING ENTRIES? Yes// Y (Yes). Select FIELD: ^ Note: Most of the components exported in this patch are NEW, so just restoring the original routines will result in a return to normal operations even if the manual clean-up above is NOT executed. This process should only be done with the concurrence and participation of the development team and the appropriate VA Site/Region personnel. If assistance is still required, then submit a ServiceNow (SNOW) ticket so that the development team can evaluate and assist in this restoration process. Routine Information: ==================== The second line of each of these routines now looks like: ;;8.0;KERNEL;**[Patch List]**;Jul 10, 1995;Build 3 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: XU8P799 Before: n/a After: B72250025 **799** Routine Name: XUESSO2 Before:B134263161 After:B156935866 **655,659,630,701,731,771,779,799** Routine Name: XUIAMDD1 Before: n/a After: B20724658 **799** Routine Name: XUIAMNPB Before: n/a After:B108825472 **799** Routine Name: XUIAMPR Before: n/a After:B142252877 **799** Routine Name: XUIAMPR1 Before: n/a After: B56825837 **799** Routine Name: XUIAMXML Before: B85181132 After:B120178978 **731,799** Routine Name: XUIAMXML2 Before: n/a After: B96060099 **799** Routine Name: XUMVINPU Before:B164852419 After:B169761764 **691,711,710,732,733,799** Routine Name: XUS1 Before: B33957171 After: B35222869 **9,59,111,165,150,252,265,419, 469,523,543,638,659,701,795, 799** Routine Name: XUSERNEW Before: B24383535 After: B26785776 **16,49,134,208,157,313,351, 419,467,480,799** Routine Name: XUSTERM Before: B23116686 After: B23416153 **36,73,135,148,169,222,313, 384,489,527,588,645,693,799** Routine list of preceding patches: 480, 693, 733, 779, 795 ============================================================================= User Information: Entered By : Date Entered : DEC 29, 2023 Completed By: Date Completed: JUN 02, 2025 Released By : Date Released : JUN 03, 2025 ============================================================================= Packman Mail Message: ===================== $END TXT