| DESCRIPTION OF ENHANCEMENTS |
ISL-0598-50691 XUSRB When a GUI-Broker process exited the M system
its context when completing the sign-on.
XQCS These two routines improve the interface between
XQSET the Remote Proceedure Call (RPC) Broker and the
traditional Menu System. With this patch installed
sites will be able to mark Broker-type options
out-of-order, lock them with keys and reverse keys,
and restrict the days and times during which they
are allowed to run.
it failed to clean-up the temp globals
Checksum
Routine Old New 2nd Line
XQCS 9069982 12754137 **15,28,82**
XQSET 11570399 11252847 **28,82**
XUSRB 5125201 5576613 **11,16,28,32,59,70,82**
XUSRB1 9903269 10103967 **28,82**
List of preceding patches: 11, 15, 16, 28, 32, 59, 70
Checksum's calculated by CHECK^XTSUMBLD
as roll and scroll M processes do.
=========================================================================
Installation:
1. DSM sites - Some of these routines may be mapped,
so you will need to disable mapping for the affected routines.
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
Compare Transport Global to Current System
Backup a Transport Global
It was discovered that not all local Broker
4. Stop the Broker server. (If you install when few users are on the
system and the possibility of some CLOBER errors is acceptable,
then users can stay on the system.)
5. On the KIDS menu, under the 'Installation' menu, use the following
option:
Install Package(s) 'XU*8.0*82'
=========
development was making the call to establish
No Options or Protocols need to be placed out-of-order.
Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO
==
6. DSM Sites, after patch has installed, rebuild your map set.
Restart the Broker server.
===========================================================================
an application context. They were just adding
the local RPC to the SIGN-ON context. This
loophole has been fixed by having sign-on remove
|
