================================================================
===== AdStar Distributed Storage Manager =====
===== Technical Support Team =====
===== =====
===== ******* B U L L E T I N ******* =====
===== =====
================================================================
ABSTRACT
Problem in API restore for rare buffer boundary condition.
DETAIL
IMPORTANT NOTICE FOR ALL ADSM CUSTOMERS
Recently, IBM discovered a rare, but potentially serious problem
with the API on restore/retrieve. The API library will drop data
sent from the server if the dsmGetData buffer exactly fills with
the contents of a Data verb. The object on the server is complete.
It is only on the transfer back to the application that data
can be missed.
This is rare because the boundary condition must match up exactly
to the byte. The buffer sizes that can cause this are difficult
to determine precisely, especially for compressed data because
the expansion of customer data will vary.
Note that this problem is only an issue for API applications,
not the Backup/Archive, HSM, or Admin clients.
PROBLEM RESOLUTION:
The immediate resolution to this problem is to fix the
logic in the API library so that this boundary condition
is checked correctly.
APAR IC13451 was taken to address this problem and the fix
which implements this is included in client PTF 4.
AFFECTED PLATFORMS:
The platforms known to be potentially affected by this problem
are those with an API.
Some of the known API applications are DB2/6000, DB2/2,
Lotus Notes Backup Agent, Personally Safe and Sound,
BACKINT/ADSM, SQL-BackTrack ADSM Module, and
NetSpace/ADSM Virtual Tape Library.
RECOMMENDATION:
Apply client PTF 4. See the list of the numbers below.
If you have not restored any data with your API application,
nothing else is necessary.
If you have restored data, most likely your data is complete.
However, review you data for completeness. In the rare
situation that data was lost, it would have been about
32 kilobytes. If you discover that data is missing, apply
ptf 4 and do another restore using an image that was
backed up before your last restore.
The DB2 applications verify the data on a restore, so
unless they have reported an error, your restored version
is complete.
The IBM ADSTAR Distributed Storage Manager Team
PTFs:
For compid 565511902:
COMP DESCRIPTION RET/REL PTF NUMBER
---------------- ------- ----------
ADSM OS/2 V2 Client(ENG) AC1 IP20801
ADSM OS/2 V2 Client(DBCS) AC2 IP20802
ADSM OS/2 V2 Client(SWE) AC3 IP20803
ADSM OS/2 V2 Client(GER) AC4 IP20804
ADSM OS/2 V2 Client(SPA) AC5 IP20805
ADSM OS/2 V2 Client(ITA) AC6 IP20806
ADSM OS/2 V2 Client(FRE) AC7 IP20807
ADSM OS/2 V2 Client(CHI) AC8 IP20808
ADSM AIX V3 Client Tape ADJ IP20800
ADSM SUNOS Client Diskette AE1 IP20809
ADSM SUNOS Client Tape AEJ IP20810
ADSM NOVELL Client AG1 IP20811
ADSM WINDOWS Client(ENG) AH1 IP20812
ADSM WINDOWS Client(DBCS) AH2 IP20813
ADSM WINDOWS Client(SWE) AH3 IP20814
ADSM WINDOWS Client(GER) AH4 IP20815
ADSM WINDOWS Client(SPA) AH5 IP20816
ADSM WINDOWS Client(ITA) AH6 IP20817
ADSM WINDOWS Client(FRE) AH7 IP20818
ADSM HP-UX Client AI1 IP20819
ADSM ATT Client AL1 IP20820
ADSM Win(32) Client AN1 IP20821
ADSM SINIX RISC Client AP1 IP20822
ADSM SGI Client AQ1 IP20823
ADSM HP10 Client AS1 IP20824
ADSM SINIX (x86) Client AT1 IP20825
ADSM NEC Client AU1 IP20826
ADSM Sequent PTX Client AX1 IP20827
ADSM Digital UNIX Client AY1 IP20828
ADSM Bull Client AZ1 IP20829
For compid 565511904:
ADSM AIX V4 Client AR1 U443912
|