I think there is a AHA Idea for exactly this (see later) . To externalize to the MSTR when a package goes invalid thus giving the chance of looking at it before the autobind. Naturally you can extract from the Db2 log and look for updates to the SYSPACKAGE table. I also do not know of any existing IFCID that returns what you want to know...sounds like an AHA idea to me. IFI pair 108/109 trace any BIND (including Autobind as QW0108T = 'A') so that might help!
The APAR that really helps is PH13550 for Db2 12 where IBM enhanced the DSNT500I message:
Message DSNT500I will be issued to console:
DSNT500I csect-name RESOURCE UNAVAILABLE
when an autobind fails which leads to the
inoperative state being placed on the package.
The following is a description of the tokens in console
reason-code: 00E30305 (existing)
resource-type: 00000804 (new to include the version
identifier in resource-name)
(if there is no version identifier, it will
be COLLECTION.PACKAGE.() )
To facilitate the REBIND command, the
resource-name in DSNT500I will be enclosed
with quotation mark ("):
If the version identifier doesn't exist:
Makes it much easier!
SOFTWARE ENGINEERING GmbH and SEGUS Inc.
Tel. +49 (0)211 96149-675
Fax +49 (0)211 96149-32
Link zur Datenschutzerklärung
Software Engineering GmbH
Amtsgericht Düsseldorf, HRB 37894
Geschäftsführung: Gerhard Schubert, Ulf Heinrich
UPS6756, #1544403 Oleander Drive, Suite CWilmington, NC 28403 Phone: (910) 660-8649Fax: (910) 523-5504