RE: another V5R1 upgrade "problem" related to old taatool dltolds plf

["Mark A. Manske" <mmanske@xxxxxxxxxxxxxxxxxx>]

It was not an API, yes I should've seen it coming, but I did not know this
was being
done here (or should I say I never bothered to ask how it was being done
here)

I have been instructing the staff to not use the taatools any longer, as
there are
many better API's, newer functions, and cleaner ways to do things.

It ultimately was my fault for not researching enough, but it always seems
to happen,
some little thing you don't know about sneaks around, lurking from the old
days,
waiting with baited breath to watch you fail.

I plan on changing the whole process to use API's, and am more aggressively
removing
the option to use taatools commands/pgms since we have such an old version
and
there is no hope of allowing us to pay for a newer version.

Mark A. Manske
Fleming CSD - Plymouth Division
Sr. Project Lead
Phone      (763) 545-3700 extension 273
Web Site  http://www.minter-weisman.com
E-Mail      mailto:mmanske@minter-weisman.com





-----Original Message-----
From: midrange-l-admin@midrange.com
[mailto:midrange-l-admin@midrange.com]On Behalf Of R. Bruce Hoffman, Jr.
Sent: Tuesday, February 26, 2002 9:22 AM
To: midrange-l@midrange.com
Subject: Re: another V5R1 upgrade "problem" related to old taatool
dltolds plf


----- Original Message -----
From: <David.X.Kahn@gsk.com>
To: <midrange-l@midrange.com>
Sent: Tuesday, February 26, 2002 4:30 AM
Subject: RE: another V5R1 upgrade "problem" related to old taatool dltolds
plf


> Rod wrote:
>
> > Are you sure this came from TAATOOL? Henrik Krebbs had
> > a command of the same name (library HKTOOL)
>
> Yes, it appears to be a TAATOOL.

fasinating. Yes, it is a very old tool, from the QUSRTOOL libraries, I don't
know if it's still included or offered in the current TAATools. I used it
quite some time ago, but....

I don't recall, but does it use an API or is it spool file output that is
read back in? If (and I think, for some reason, it was) the latter, then you
should have seen it coming, as with almost every release, spooled file
output from commands changes constantly. Outfile support changes
occasionally as well, but API's are not supposed to change in the middle of
the structure, without pointer based and offset references.

If it's an API, and it's not clearly documented in the memo to users as an
API change in the programming section, they you have a legitimate beef with
IBM, regardless of the age of the command. The change should have then been
to add a format or add the field to the end of the output. This is
documented in the API references.

===========================================================