With current maintenance a RC/Compare for Db2 for z/OS (RCC) job fails with a S0C4 abend in module RML@BLDC :
SYSTEM COMPLETION CODE=0C4 REASON CODE=00000004
PSW AT TIME OF ERROR 078D0000 9D516D50 ILC 2 INTC 04
ACTIVE MODULE ADDRESS=00000000_1D3EB000 OFFSET
DATA AT PSW 1D516D4A - F004181F 0E0E58E0 40CC58F0
However, using the current @DEFAULT Model ID, that same job works fine.
One of the known problems with user customized models is that the regular maintenance does not touch them, only the @DEFAULT custom subsystem
default is updated. So the older customized models can get out of date. This is because we have no way of parsing what changes the customer has made.
It is a good Best Practice to create new customized models from the @DEFAULT upon each new release or at least do testing to make sure that they still
work after an upgrade to a new release.