| DESCRIPTION OF ENHANCEMENTS |
This patch to the Laboratory package does not contain any changes to
1. When patch LR*5.2*153 was released it contained changes to the code
LRX 14065673 13923654 65,153,201,217
INSTALLATION INSTRUCTIONS
-------------------------
The install time for this patch is less than 2 minutes. This patch
can be installed when Laboratory users are on the system.
However the following conditions apply:
- Accessioning should not be occurring.
Patch installation needs to be coordinated with the Laboratory
in routine LRX used to create the UID. These changes performed a
Information Manager (LIM/ADPAC).
NOTE: MailMan and KERNEL patches must be current on the target system to
avoid problems loading and/or installing this patch.
1. If any of the above routines are mapped, disable mapping for them.
2. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu. This
check to determine if the UID that was to be created already existed.
option will load the KIDS patch onto your system.
3. The patch has now been loaded into a Transport global on your
system. You now need to use KIDS to install the transport global.
4. On the 'Kernel Installation & Distribution System' Menu (KIDS),
select the 'Installation' menu.
5. Use the 'Verify Checksum in Transport Global' option and verify that
all routines have the correct checksums.
The intent is to prevent the same UID being assigned to two or more
6. If you wish to preserve a copy of the routines exported in this patch
prior to installation, you should use the 'Backup a Transport Global'
option at this time. You may also compare the routine in your
production account to the routine in the patch by using the 'Compare
a Transport Global to Current System' option. These options can
both be found under the 'Installation' menu.
7. Use the 'Install Package(s)' option under the 'Installation' menu
and select the package 'LR*5.2*217'. When prompted 'Want to
accessions. If the UID already existed then routine LRX created an
DISABLE Scheduled Options, Menu Options, and Protocols? YES//',
choose 'NO'.
8. On a mapped system, rebuild your map set.
9. Routine LR217 can be deleted after successful patch installation.
*****************************************************************************
Below is an example of the dialogue seen during the KIDS install:
alternate UID substituting the accession area's numeric identifier
Select Installation Option: 6 Install Package(s)
Select INSTALL NAME: LR*5.2*217 Loaded from Distribution 8/28/98@15:5
7:39
=> LR*5.2*217
This Distribution was loaded on Aug 28, 1998@15:57:39 with header of
LR*5.2*217
It consisted of the following Install(s):
with "00".
LR*5.2*217
LR*5.2*217
Will first run the Environment Check Routine, LR217
--- Environment Check is Ok ---
Install Questions for LR*5.2*217
Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// 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// TELNET VIRTUAL
The code used to produce an alternate UID was setting a lock on
Install Started for LR*5.2*217 :
Aug 28, 1998@15:58:32
Installing Routines:
Aug 28, 1998@15:58:32
Running Pre-Install Routine: PRE^LR217
the global LRO(68,"C",uid) which was not being released.
*** Pre install started ***
--- No actions required for pre install ---
LR*5.2*217
*** Pre install completed ***
Running Post-Install Routine: POST^LR217
the VISTA BLOOD BANK Software as defined by VHA DIRECTIVE 97-033
This caused other lab users to "hang" until the user with the lock
*** Post install started ***
--- No actions required for post install ---
*** Post install completed ***
Updating Routine file...
Updating KIDS files...
logged off and the lock was released. This condition has been found
LR*5.2*217 Installed.
Aug 28, 1998@15:58:34.
Install Message sent #10909944
Install Completed
Select Installation Option:
to occur under three scenarios.
End of example install
*****************************************************************************
The first is when a site switches the numeric identifier for an
accession area and the identifier has been previously used.
The second is when a site has modified the data dictionary for field
NUMERIC IDENTIFIER (#.4) in the ACCESSION file (#68) to allow more
than one accession area to have the same identifier. The third is
explained in #2 below.
titled VISTA BLOOD BANK SOFTWARE VERSION 5.2.
See FileMan's field Description for fields TYPE OF ACCESSION NUMBER
(#.092) and NUMERIC IDENTIFIER (#.4) in the ACCESSION file (#68)
for further information.
Solution: modified code in routine LRX to remove setting lock on
global LRO(68,"C",uid). Since the routine also lock/unlocks
global node LRO(68,"C"), this lock is not neccessary.
NOIS CTX-0798-71641, PAL-0898-60857, PUG-0498-51586, LAS-0798-60721
2. It has been found that under the following conditions the code to
create an accession's UID was being called twice. This resulted in
the UID for the accession being changed to a UID that began with
"00" even if the original UID was unique. This would occur when a
site has accession areas in parallel and the parallel accession
area has a lower internal entry number in the ACCESSION file (#68).
Example: Accession area "B" is in parallel with accession area "A".
Accession area "B" has a lower internal entry number in file
ACCESSION (#68). When building acccessions from an order
the accessions are created based on the internal entry
number in the ACCESSION file (#68). In this example, the
acccession for accession area "B" would be created first.
But since it's in parallel with accession area "A" the
software first creates an accession for accession area "A",
then uses acccession area's "A" accession number for
accession area's "B" accession. Next when the Lab software
attempted to put tests on accession area "A" it detected
that the UID existed and generated the alternate UID using
This patch will address a locking problem concerning the LRO global and
"00" as the NUMERIC IDENTIFIER even though it was the
same accession.
Solution: modified code in routine LRX to only generate an alternate
UID if the UID exists and is not for the same accession.
NOIS PUG-0498-511586
Associated NOIS
--------------
a fix to Laboratory Unique Identifier (UID) creation.
CTX-0798-71641
LAS-0798-60721
PAL-0898-60857
PUG-0498-51586
Test Sites
----------
Central Texas HCS
Las Vegas VAMC
Milwaukee VAMC
Palo Alto VAMC
Puget Sound HCS
----------------------------
ROUTINE SUMMARY
---------------
The following is a list of routines included in this patch. The second
line of each routine now looks like:
<tab>;;5.2;LAB SERVICE;**[patch list]**; Sep 27, 1994
CHECK^XTSUMBLD results
Routine Name Before Patch After Patch Patch List
------------ ------------ ----------- --------------
LR217 N/A 2463818 217
|
