*** NETWARE PTF 6 PROBLEM ***

This posting is to make you aware of a problem with the ADSM NetWare client
PTF level 6 (IP20988). After applying PTF 6, the next incremental backup that
is run will result in a full backup (subsequent incremental backups run
correctly). Aside from this nuisance, the code is otherwise okay. (NOTE: I
use the term "nuisance" loosely, as I realize that this may have a major impact
especially on large NetWare installations.)

ADSM development is working on a rebuild of this PTF and will make it available
for download as soon as possible. An *estimated* timeframe is approximately one
week; I can't be more specific than that.

In the mean time, the NetWare client PTF has been pulled from the anonymous
server. If you have already downloaded the code, we recommend that you do *not*
apply it; rather, wait for the corrected PTF 6 to be made available. If you
have already applied this code, you should be alright. But once you apply the
rebuilt PTF 6, the first incremental backup thereafter will be another full.
Unfortunately this can not be helped. Once you're past that full backup,
subsequent backups will run properly.

Appended to the bottom of this note is the text for APAR IC16127, which was
taken to address this problem.

I apologize for any inconvenience that this may have caused.

Andy Raibeck
ADSM Level 2 Support

======== APAR IC16127 text follows ========

ERROR DESCRIPTION:
After upgrading the ADSM Novell NetWare client to PTF level 6,
the next incremental backup will force a full backup of the data
on that client (i.e. all data will be backed up again, regard-
less of whether it has changed). It should be noted that the
code is otherwise okay.

The PTF number is IP20988 and equates to client version 2.1.0.6.
The PTF will be rebuilt with this error corrected. To determine
if you have the erroneous build, check the date on DSMC.NLM. If
the date is 12/19/96 (December 19, 1996) then you have the
erroneous code. The corrected code will have a later date.

NOTE: If you have already run an incremental backup with the
12/19/96 code, then after applying the corrected code, another
full backup will be created when the next incremental backup
runs. Thereafter, incremental backup should behave correctly.