MVSFORUMS.com

[jctgf]

[dbzTHEdinosauer]

did you CALL this module from 2 different modules?

if you look at the compile listing, you will see inserted code (by db2) between your Procedure Division Using statement and
your exec sql set timestamp.

this code is executed once - by the first call to this module (notice SQL-INIT-END logic).

this code sets up the addressing for db2 for your host variables.

1st call, the linkage section comes from program A working storage. sql-init section addresses the host variable to program A.

2nd call, the linkage section comes from program B working storage, yet db2 has the host variable addressed to program A.
you will find when program B calls the db2 module,
the set timestamp will populate program A working storage.

that is why it works sometimes.

would suggest that you use linkage for host variables only if the db2 program is only called from one module and the linkage is to that one modules working storage.

if your db2 timestamp program is called from more than one module, you need to use working storage of the db2 program as the host variable - as you had to do to get everything to work.

you can also solve the problem by reseting the sql-init-flag each time you exit the db2 module, but I would not recommend this solution

I made the same mistake about 15 years ago.
_________________
Dick Brenholtz
American living in Varel, Germany

[jctgf]

thank you a lot, sir!
thank you very much indeed!