$TXT Created by at KRNDEV.FO-OAKLAND.DOMAIN.EXT (KIDS) on Thursday, 05/29/25 at 09:07 ============================================================================= Run Date: APR 06, 2026 Designation: XU*8*820 Package : XU - KERNEL Priority: Mandatory Version : 8 SEQ #662 Status: Released Compliance Date: MAY 07, 2026 ============================================================================= Associated patches: (v)XU*8*419 <<= must be installed BEFORE `XU*8*820' Subject: UPDATE TERMINAL TYPE DEFAULT FOR VISTA Category: - Routine Description: ============ Kernel Patch XU*8.0*820 fixes an issue where users' VistA terminal sessions are defaulting to the C-VT100 terminal type. This terminal type can cause issues for users' terminal display and may not fully support extended screen control characters. Kernel uses an interface that probes the terminal emulation software for its Terminal Type ID. If the Terminal Type ID is found to match an existing VistA terminal type, Kernel will set the terminal type to the ID provided by the Terminal Emulation software. If the terminal type cannot be found, Kernel prompts the user for a Terminal Type and defaults to C-VT100. This prompt allows users to enter a possibly erroneous terminal ID. Kernel Patch XU*8.0*820 will now set the terminal type ID default to VT320 when the Kernel probing software cannot identify a user's VistA terminal ID when logging on to the system. This patch also disables the prompt asking for the user to identify a terminal type. The new default C-VT320 terminal ID will allow extended screen control characters. PLEASE NOTE: The interface to probe the terminal emulation is NOT being changed. Applications (Micro Focus Reflection, SecureCRT, etc.) should have the Terminal Emulation set to VT320 as the Terminal Type ID for VistA so that, when probed, VistA Kernel will map to C-VT320 automatically. EHRM Impact Statement: ---------------------- This patch should have no EHRM impact, and can be installed at all sites, including EHRM converted sites. Patch Components: ----------------- 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: ----------------------- New Service Requests (NSRs): N/A Patient Safety Issues (PSIs): N/A Defect Tracking System Ticket(s) & Overview: 1. DMND0011777 - WC20240116 Update Terminal Type Default for VistA (VP-3892) Problem: -------- The problem is that many VistA Applications are defaulting to the C-VT100 terminal that the user is not aware of and do not know how to manipulate. Not using the correct terminal type can cause further issues and can be logged off. Resolution: Kernel Patch XU*8.0*820 will now set the terminal type ID default to VT320 when the Kernel probing software cannot identify a user's VistA terminal ID when logging on to the system. This patch also disables the prompt asking for the user to identify a terminal type. The new default C-VT320 terminal ID will allow extended screen control characters. Test Sites: Change Order #: --------------------------------------- Fort Harrison VAMC CHG0645719 Butler VAMC CHG0645423 Miami VAMC CHG0646519 Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. 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: Device Handler User Guide KRN_8_0_SM_DEVICE_HANDLER_UG.DOCX KRN_8_0_SM_DEVICE_HANDLER_UG.PDF Kernel 8.0 Systems Management: Signon/Security User Guide KRN_8_0_SM_SIGNON_SECURITY_UG.DOCX KRN_8_0_SM_SIGNON_SECURITY_UG.PDF Patch Installation: ------------------- Pre/Post Installation Overview: ------------------------------- There are no Pre/Post installation routine processes. 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 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 XU*8.0*820 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. 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*820 iii. When prompted for the following, enter "R" for Routines or "B" for Build. Select one of the following: B Build (including Routines) R Routines Only Backup Type: B// 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//', press and take the default response of "NO". ii. When prompted 'Want KIDS to INHIBIT LOGONs during the install? NO//', press and take the default response of "NO". iii. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//', press and take the default response of "NO". Post-Installation Instructions: None Back-Out/Roll Back Plan: ------------------------ To rollback/backout this patch, a. Use MailMan menu to locate the PackMan message containing the backup build. The subject of the PackMan message begins with "Backup of XU*8.0*820". Use the PackMan message action XTRACT KIDS. Use the INSTALL/CHECK MESSAGE option to load the backup build. b. Then use KIDS menu to install the backup KIDS distribution using the Install Package(s) [XPD INSTALL BUILD] option. If assistance is needed to rollback/backout the patch, please log a SNOW ticket so the development team can assist. Routine Information: ==================== The second line of each of these routines now looks like: ;;8.0;KERNEL;**[Patch List]**;Jul 10, 1995;Build 1 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: XUS3 Before: B18943733 After: B19200328 **32,149,265,419,820** Routine list of preceding patches: 419 ============================================================================= User Information: Entered By : Date Entered : MAR 28, 2025 Completed By: Date Completed: APR 01, 2026 Released By : Date Released : APR 06, 2026 ============================================================================= Packman Mail Message: ===================== $END TXT