| DESCRIPTION OF ENHANCEMENTS |
It was found that the Broker sign-on were allowed even when Logon were
inhibited.
Both problems fixed by patching XUSRB
SFC-1197-61181 XUSRA The SQLI interface was making use of a call in
XUSRA that called an entry point in XUS that had
chaged with patch 59. This is now fixed.
Checksum
*** Patch XU*8*59 MUST be installed before this patch ***
Routine Old New 2nd Line
XUSRA 1213791 1890066 **70**
XUSRB 4666750 5125201 **11,16,28,32,59,70**
=========================================================================
Installation:
1. DSM sites - One of these routines may by mapped,
so you will need to disable mapping for the effected routine.
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 Checksum's in Transport Global
Print Transport Global
A problem was found when using a Broker v1.0 application on Windows 95
Compare Transport Global to Current System
Backup a Transport Global
4. Users can remain on the system.
Stop the Broker listener to prevent the possibility of some CLOBER
errors.
5. On the KIDS menu, under the 'Installation' menu, use the following
option:
Install Package(s) 'XU*8.0*70'
and server side has Broker v1.1 with Auto sign-on. The 16bit app will
=========
6. MSM Sites - Answer YES to the question 'Want to MOVE routines to
other CPUs?'. Enter the names of your Compute and Print server(s).
7. DSM Sites, after patch has installed, rebuild your map set.
8. All sites, Restart the Broker listener.
=========================================================================
prevent the server from contacting the ClientAgent, this will cause the
16 bit PCMM to time-out and close the sign-on.
The fix is to disable the auto sign-on if the client is Broker v1.0
|
