$TXT Created by MONSON,STEVE at DEVCUR.FO-SLC.MED.VA.GOV (KIDS) on Tuesday, 09/09/08 at 13:22 ============================================================================= Run Date: SEP 25, 2008 Designation: WEBV*1*15 Package : WEBV - VISTA WEB Priority: EMERGENCY Version : 1 SEQ #11 Status: Released Compliance Date: OCT 02, 2008 ============================================================================= Subject: VistAWeb Falling Waters Migration Prep Category: - Routine - Other - Data Dictionary - Enhancement () Description: ============ NOTE: The new SACC standard allows for variable lengths longer than 8 characters. However, the TOOLKIT patch (XT*7.3*110) which updates XINDEX to reflect the new standards has not been released yet. Please ignore the following XINDEX warnings: ***** ERRORS & WARNINGS IN WEBVY15 ***** APCONTEXT W - Invalid local variable name. APCONTEXT S - Lower/Mixed case Variable name used. **************************************************************** ** Please Note that this patch is being released with a 7 day ** ** compliance date ** **************************************************************** The primary VistAWeb server will be changing from Silver Spring, MD to Falling Waters, WV. This is currently planned to be sometime after October 1, 2008. As part of the preparation for this move, this patch is being sent out to update the REMOTE APPLICATION file, 8994.5. Please read the DATA DICTIONARY description of this file for more information. This patch contains a single routine, which is a post install routine that is automatically executed after patch installation. This routine simply adds one entry (VISTAWEB-FW) to the REMOTE APPLICATION file, which is the Broker Security Enhancement entry for the new Falling Waters VistAWeb server address. After patch installation, there will be 2 entries for VISTAWEB in this file. Please DO NOT remove the old VISTAWEB entry from this file. This old entry will be dealt with nation-wide by the VistAWeb team following the retirement of the hardware at Silver Spring. Associated Patches: =================== NONE Associated Remedy Ticket(s): ============================ N/A New Service Request (NSR): ========================== N/A Test Sites: =========== TAMPA, FL LOMA LINDA, CA WHITE RIVER JUNCTION, VT EAST ORANGE, NJ (NEW JERSEY) SEATTLE, WA (PUGET SOUND) GRAND JUNCTION, CO Installation Instructions: ========================== This patch can be installed at any time with users on the system. Installation should take less than two minutes. Please also see the MANUAL POST INSTALL instructions below this section. 1. Use the INSTALL/CHECK MESSAGE option on the PackMan menu. (a) If you get a message which states "This patch is for Version 1, you are running Version 0 Want to continue installing this build? NO//" then respond YES. 2. From the Kernel Installation & Distribution System menu, select the Installation menu. 3. From this menu, you may elect to use the following options (when prompted for the INSTALL NAME, enter WEBV*1.0*15): (a) Backup a Transport Global - this option will create a backup message of any routines exported with the patch. It will NOT backup any other changes such as DDs or templates. (b) Compare Transport Global to Current System - this option will allow you to view all changes that will be made when the patch is installed. It compares all components of the 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. (d) Print Transport Global - this option will allow you to view the components of the KIDS build. 4. Use the Install Package(s) option and select the package WEBV*1.0*15. (a) If you get a message which states "This patch is for Version 1, you are running Version 0 Want to continue installing this build? NO//" then respond YES. 5. When prompted "Want KIDS to INHIBIT LOGONs during the install? NO//" respond NO. 6. When prompted "Want to DISABLE Scheduled options, Menu options, and Protocols? NO//" respond NO. Installation Example: ===================== Install Package(s) Select INSTALL NAME: WEBV*1.0*15 Loaded from Distribution Loaded from Distribution 9/17/08@09:38:41 => WEBV*1*15 TEST v5 This Distribution was loaded on Sep 17, 2008@09:38:41 with header of WEBV*1*15 TEST v5 It consisted of the following Install(s): WEBV*1.0*15 Checking Install for Package WEBV*1.0*15 Install Questions for WEBV*1.0*15 Want KIDS to INHIBIT LOGONs during the install? NO// NO Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO// NO Enter the Device you want to print the Install messages. You can queue the install by enter a 'Q' at the device prompt. Enter a '^' to abort the install. DEVICE: HOME// VIRTUAL TELNET Install Started for WEBV*1.0*15 : Sep 17, 2008@09:42:44 Build Distribution Date: Sep 09, 2008 Installing Routines: Sep 17, 2008@09:42:44 Running Post-Install Routine: ^WEBVY15 REMOVING OLD V/W ENTRY FROM 8994.5 WEBV*1.0*15 -------------------------------------------------------------------------------- LOOKING FOR DUPLICATE V/W ENTRY NO OLD V/W ENTRIES FOUND ADDING NEW V/W ENTRY TO 8994.5 LOOKING FOR 'OR CPRS GUI CHART':FOUND OPTION WRITING TO REMOTE APPLICATION FILE (8994.5) VISTAWEB ENTRY SUCCESSFULLY ADDED === POST INSTALL COMPLETED SUCCESSFULLY === Updating Routine file... Updating KIDS files... WEBV*1.0*15 Installed. Sep 17, 2008@09:42:44 Not a production UCI NO Install Message sent -------------------------------------------------------------------------------- +------------------------------------------------------------+ 100% | 25 50 75 | Complete +------------------------------------------------------------+ Install Completed MANUAL POST INSTALL INSTRUCTIONS: ================================= Please perform the following manual step after this patch is installed. This patch also inserts a package entry for VISTA WEB in the PACKAGE file. This manual step is necessary because this is the first time that a VISTA WEB M routine is being sent to the field. Populating the CURRENT VERSION field should avoid warning messages about VISTA WEB version mis- matches in future VISTA WEB releases of M routines. These steps should take less than two minutes. 1. Change the CURRENT VERSION field of the PACKAGE file entry for VISTA WEB to 1 (a) From the Systems Manager Menu, select "FileMan" (FM) (b) From the FileMan menu, select "Enter or Edit" (EN) (c) At the "INPUT TO WHAT FILE" prompt, enter PACKAGE (d) At the "EDIT WHICH FIELD" prompt, enter CURRENT VERSION (e) At the "THEN EDIT FIELD" prompt, press Enter (f) At the "Select PACKAGE NAME" prompt, enter VISTA WEB (you must include the space between the words VISTA and WEB) (g) At the "CURRENT VERSION" prompt, enter 1 (the number "1") 2. Using FileMan "Inquire to File Entries", verify that the PACKAGE file entry for VISTA WEB contains a CURRENT VERSION field with the number 1 You should see something like the following: NAME: VISTA WEB PREFIX: WEBV SHORT DESCRIPTION: VISTA WEB VERSION: 1.0 PATCH APPLICATION HISTORY: 15 DATE APPLIED: SEP 17, 2008@09:42:44 APPLIED BY: HINES,RICK CURRENT VERSION: 1 Routine Information: ==================== The second line of each of these routines now looks like: ;;1.0;VISTAWEB;**[Patch List]**;;Build 3 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: WEBVY15 Before: n/a After: B6829925 **15** ============================================================================= User Information: Entered By : MONSON,STEVEN R Date Entered : JUL 16, 2008 Completed By: MERRILL,DAVID P Date Completed: SEP 25, 2008 Released By : HINES,RICK Date Released : SEP 25, 2008 ============================================================================= Packman Mail Message: ===================== $END TXT