yes, but this is done inside DSNALI, and to fix it,
I would have to change DSNALI, and I don't (yet) believe that management will
allow me to do so.
In fact, once changed, DSNALI should not be subject of
future changes during new DB2 releases, because it is supposed to be linked
to every batch program, and normally batch programs are not required to be
relinked on DB2 release changes.
This said, I only have the possibiliy to change DSNALI, because my clever
colleagues in 1990 decided NOT to link DSNALI to the batch programs
but to link a little stub called DSNHLI instead which determines the environment
and calls the appropriate interface dynamically. If this was not the case, we
would have to relink all our programs, if we decided to change DSNALI.
> I won't hold my breath for IBM providing a fix. They will probably
> catagorize it as Working As Designed. How about doing a static link
> rather than dynamic one and side stepping the problem ?