| DESCRIPTION OF ENHANCEMENTS |
HIN-1298-40427 XUSRB A convoluted link with patch XU*8*69 is causing
Routine Summary
The following routines are included in this patch. The second line of each
of these routines now looks like:
;;8.0;KERNEL;<patchlist>;Jul 05, 1995
Checksum
Routine Old New 2nd Line
XUSRB 5576613 5738122 **11,16,28,32,59,70,82,109**
problems in CPRS at DSM sites. The error is
List of preceding patches: 11, 16, 28, 32, 59, 70, 82
Sites should use CHECK^XTSUMBLD to verify checksums
=========================================================================
Installation:
1. DSM sites - This routines is usually mapped,
so you will need to disable mapping for the affected routines.
%DSM-E-DEVNOTOPN at QUIT^%ZIS6 with IO(0) null.
2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This
option will load the KIDS package 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.
On the KIDS menu, under the 'Installation' menu, use the following
options:
Verify Checksums in Transport Global
Print Transport Global
This only happens at DSM sites that do not have
Compare Transport Global to Current System
Backup a Transport Global
4. Users can remain on the system.
Stop the Broker server(s).
"DO STOP^XWBTCP(<socket>)" on each node that has Broker running.
(If you install when few users are on the system and the possibility
of some CLOBER/NOSOURCE errors is acceptable, Leave the Broker
running and queue the install for after hours.)
auto sign-on disabled. The code that calls the
5. On the KIDS menu, under the 'Installation' menu, use the following
option:
Install Package(s) 'XU*8.0*109'
=========
No Options or Protocols need to be placed out-of-order.
Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO
==
client agent mades a call to HOME^%ZIS and TCP
6. DSM Sites, after patch has installed, rebuild your map set.
If the Broker was stopped, Remember to restart it.
"DO STRT^XWBTCP(<socket>)" on each Broker node.
=========================================================================
connection don't work as a home device. The fix
is to have the XUSRB save the NULL device as the
HOME device before the call to Client agent.
|