Thanks for the jog to my memory - It is the Open Transport 1.1 release that is
causing the problem with the dropped session, not the Internet Connection as I
errooneously stated in my earlier notes.

Jerry Lawson
________________________Forward Header________________________
Author: INTERNET.OWNERAD
Subject: Re: MacOS 7.5.3 problems
04-30-96 11:50 AM

Rick Tsujimoto <rtsujimoto AT CUSA.CANON DOT COM> said:
> The problem you're experiencing might be due to ADSM client software,
> not the Internet connection software. I'm assuming you're trying to
> backup the MAC to an ADSM MVS server. The MAC could potentially create
> filenames that the ADSM MVS server cannot handle (especially if it's
> V1.1).  If the MAC filenames have nondisplayable characters, e.g. an
> ascii null, as part of the name, then the ADSM V1.1 MVS server could
> have problems, causing the session to be abnormally terminated and
> garbage stored on the MVS data base.

There really do seem to be problems with Open Transport 1.1 vs ADSM,
more than just invalid characters in file names.  Check out the README
file that comes with the PowerMac client for more info.

We've seen the invalid character problem, too, with Mac clients talking
to an AIX server. If you get messages about "active object not found"
during a backup, this is what's going on: there are bad file names
stored in the server database. The really fun part is that the client
mac usually freezes up and has to be rebooted after ADSM unsuccessfully
tries to expire the badly named files/folders from the server database
during an incremental backup.

The problem is halfway fixed by the version 2 client; version 2 won't
back up the badly named files/folders. However, version 1 will, so if
you've got bad names in the server's database already because of the
version 1 client, you can't get them out (expire/delete them) without
deleting the entire filespace and doing a new initial backup of the
client node.

It's really ironic that MacOS can create file names that violate
its own standards but can't detect them. ADSM can detect them.
Maybe IBM should turn the ADSM Mac client into a Mac diagnostic
tool, and fix up our disks while it backs them up.

Wendy Alberg                      Phone:  607/255-2672
Network & Computer Systems        Fax:    607/255-6523
Cornell Information Technologies  E-mail: wa10 AT cornell DOT edu
Cornell University, Ithaca, NY    WWW:    http://dwrgi.cit.cornell.edu/