I would like to add:
- I don't know if the fields BINDDATE and BINDTIME are still populated;
you could find out by simply binding a plan
- there is a column BOUNDTS in SYSPLAN which provides the same
information in more detail ... this column IMO is still populated and used
HTH, regards
Bernd
Am 21.07.2025 um 00:32 schrieb Bernd Oppolzer:
"Not used" IMO could mean: field was used in the past (in prior
versions of DB2), but is now not longer needed.
As for SYSPLAN: I guess, today most people use packages, that is, for
the usability of a package, the BIND timestamps in SYSPACKAGE
may be relevant, otherwise SQLCODE -805. The timestamp provided by the
"user" of a package (that is, the application referring to
the package via the DB2 interface, some sort of DSNHLI) is compared to
the timestamp of the package, AFAIK.
I don't know if at times when there were no packages (must have been
DB2 version 2 or earlier), the timestamps in SYSPLAN were relevant.
We don't do this any more.
HTH, kind regards
Bernd
Am 20.07.2025 um 21:22 schrieb Richard Zierdt:
According to Db2 13 for z/OS: SQL Reference (Last updated:
2024-06-29), there are several fields within various catalog tables
described as "Not used" yet are still populated.
Ex: SYSPLAN, columns BINDDATE, BINDTIME.
"Not used" implies, well, "not used." Is there any wiggle room for
interpretation?
Could it mean "Yes, Db2 will *populate* such columns, but otherwise
not *use* them" ? If so, that interpretation would apply to a
thousand other fields in Db2 and the OS.
Richard Zierdt
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
