$TXT Created by HOLLOWAY,THOMAS J at MNTVBB.FO-ALBANY.MED.VA.GOV (KIDS) on Wednesday, 07/23/03 at 10:32 ============================================================================= Run Date: AUG 29, 2003 Designation: IB*2*226 Package : IB - INTEGRATED BILLING Priority: Mandatory Version : 2 SEQ #205 Status: Released Compliance Date: SEP 29, 2003 ============================================================================= Associated patches: (v)IB*2*161 <<= must be installed BEFORE `IB*2*226' Subject: CLAIMS MANAGER READ ERROR Category: - Routine Description: ============ This patch adds some error trapping code to avoid a problem in the Claims Manager interface that could cause users to be forcibly logged out. ASSOCIATED E3R(s): ================== N/A ASSOCIATED NOIS: ================ 1. PRE-0902-60489 Claims Manager freezing screen Duplicate: DUB-0303-31898 READ+27^IBCIUT3 Duplicate: ASH-0103-30446 ib error when going to claimsmanager NOIS OVERVIEW: ============== 1. PRE-0902-60489 Claims Manager freezing screen Problem: -------- When submitting a bill to the Claims Manager system, the user would occasionally experience a 'frozen screen'. The problem was that a error had occurred and the job had halted. There was no way for the user to know this had happened so they sat waiting for the screen to move on to the next prompt. Eventually they would have to log back in, restart their session and submit the bill again. The errors appear to occur randomly and fairly infrequently. The problem does not appear to be data-related since the same bill transmits just fine when resubmitted. The problem seems to be most prevalent on Cache/NT systems but has occurred at least once on a DSM system (see ASH-0103-30446). Resolution: ----------- This patch corrects part of the issue by adding some error trapping code that returns the user to the menu rather than halting their job when the error occurs. It is not within the scope of this patch to resolve any issues such as network timing, tcp/ip setup, hardware configurations or any other system level communications issues between the host computer and the Claims Manager system which may be the source of the error. TECHNICAL: ========== 1. Changes are made to routines IBCIUT3 and IBCIUT4. IBCIUT3 A new subroutine, ERRTRP, releases the tcp/ip port and creates the message "A SYSTEM ERROR HAS BEEN DETECTED AT THE FOLLOWING LOCATION". A new level is pushed on the error trap stack and the $ETRAP system variable is set to call the new ERRTRP subroutine. IBCIUT4 A new error type, "Fatal System Error" is added to the P1 function. PARTICIPATING TEST SITES: ========================= Asheville, NC Dublin, GA Tomah, WI Prescott, AZ ROUTINE SUMMARY =============== The following is a list of the routines included in this patch. The second line of each of these routines now looks like: ;;2.0;INTEGRATED BILLING;**[PATCH LIST]**;21-MAR-94 CHECK^XTSUMBLD results Routine name Before Patch After Patch Patch List ============ ============ =========== =========== IBCIUT3 18876832 19451135 161,226 IBCIUT4 11525602 11815808 161,226 INSTALLATION INSTRUCTIONS ========================= This patch can be installed at any time. If installed during the normal workday it is recommended that several options, related to the area of change, be temporarily taken out of service (See installation step 5 below). Install time - less than 5 minutes. 1. Choose the PackMan message containing this patch and invoke the INSTALL/CHECK MESSAGE PackMan option. 2. Disable routine mapping on all systems for the routines listed in the routine summary. (DSM for open VMS sites only) NOTE: If the routines included in this patch are not currently in your mapped routine set, please skip this step. 3. Start up the Kernel Installation and Distribution System Menu [XPD MAIN]: Edits and Distribution ... Utilities ... Installation ... Select Kernel Installation & Distribution System Option: INStallation --- 1 Load a Distribution 2 Verify Checksums in Transport Global 3 Print Transport Global 4 Compare Transport Global to Current System 5 Backup a Transport Global 6 Install Package(s) Restart Install of Package(s) Unload a Distribution 4. From this menu, you may elect to use the following options (When prompted for the INSTALL NAME, enter IB*2.0*226): a. Backup a Transport Global - This option will create a backup message of any routines exported with this patch. It will not backup any other changes such as DD's or templates. 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, DD's, 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. 5. Use the Install Package(s) option and select the package IB*2.0*226. a. When prompted 'Want KIDS to INHIBIT LOGONs during the install? YES//', answer NO. b. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES//' answer YES. c. When prompted 'Enter options you wish to mark as 'Out of Order':' Enter the following: Extract Data Files for ClaimsManager [IBCI CLAIMSMANAGER FILE MENU] ClaimsManager Reports Menu [IBCI CLAIMSMANAGER RPT MENU] d. When prompted 'Enter protocols you wish to mark as 'Out of Order': Enter the following: (press return) 6. Optional - Include the routines distributed with this patch in the mapped routine set. (DSM for Open VMS sites only) NOTE: This step is only necessary if you performed step 2 or if you wish to include the routines in your mapped set. INSTALLATION EXAMPLE: --------------------- Select Installation Option: 6 Install Package(s) Select INSTALL NAME: IB*2.0*226 Loaded from Distribution 6/30/03@16:17:17 => IB*2*226 This Distribution was loaded on Jun 30, 2003@16:17:17 with header of IB*2*226 It consisted of the following Install(s): IB*2.0*226 Checking Install for Package IB*2.0*226 Install Questions for IB*2.0*226 Want KIDS to INHIBIT LOGONs during the install? YES// NO Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// Enter options you wish to mark as 'Out Of Order': IBCI CLAIMSMANAGER FILE MENU Extract Data Files for ClaimsManager Enter options you wish to mark as 'Out Of Order': IBCI CLAIMSMANAGER RPT MENU ClaimsManager Reports Menu Enter options you wish to mark as 'Out Of Order': Enter protocols you wish to mark as 'Out Of Order': Delay Install (Minutes): (0-60): 0// 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// IP network IB*2.0*226 ---------------------------------------------------------------------------- Install Started for IB*2.0*226 : Jun 30, 2003@16:19:18 Build Distribution Date: Jun 30, 2003 Installing Routines: Jun 30, 2003@16:19:18 Updating Routine file... Updating KIDS files... IB*2.0*226 Installed. Jun 30, 2003@16:19:19 Install Message sent #2651 ---------------------------------------------------------------------------- +------------------------------------------------------------+ 100% | 25 50 75 | Complete +------------------------------------------------------------+ Install Completed Routine Information: ==================== Routine Name: - IBCIUT3 Routine Checksum: Routine Name: - IBCIUT4 Routine Checksum: ============================================================================= User Information: Entered By : HOLLOWAY,THOMAS J Date Entered : JUN 25, 2003 Completed By: DAWSON,TIM Date Completed: AUG 29, 2003 Released By : BOTTINI,STEVE Date Released : AUG 29, 2003 ============================================================================= Packman Mail Message: ===================== $END TXT