When executing a DB2 program it abended with an SQL error code of - 805 . This usually means that the DB2 timestamp within the executed load module is different from the timestamp found in the DB2 catalog as a result of a bind of the DBRM.
Prior to ZMF 5.5.3, SER messages contained the subsys id in the fourth position (ex: SERx 805 I). In v5.5.3, SER messages contain a 0 (zero) in place of subsys ID and/or the message number has changed (ex: SERx805I is now SER0801I).
Customer has an intermittent problem where the bind job counters in the ISIT record are set incorrectly to zero. This results in no CMN32 job submitted during the install, leading to a production outage the next time the newly installed load module is executed (SQLCODE=- 805 or -818).
However the CMN20 jobs were submitted. This caused - 805 DB2 errors in the customer's PROD environment. In non ERO packages, the CMN21 and CMN20 jobs are both being submitted in the correct order.
In the output records in the SYSOUT of the RARTM step, the release and area were not displayed. This problem was the result of an SQLCODE= - 805 on CMNDB2SQ. However, the error condition was not indicated within the ERO area audit.
