Leaving a Member Behind on Promotion

APAR OA18614 has introduced new functionality to allow a member to be left behind during promotion. Prior to this APAR being applied, SCLM copies all the required components to the next level.

You can specify whether an EDITABLE member and its accounting record are promoted to the next level or not. During promotion, the outputs (load modules) built using the non-promoted EDITABLE member are either:

Rebuilt at the next level (REBUILD), or
Not rebuilt at the next level

Note: The message FLM53109 "WARNING, PREDECESSOR VERIFICATION FAILED" occurs if the NOPROM member with the authorization code that is not defined to the target group cannot be promoted using one of the authorization codes defined to the from group. If this NOPROM member has an accounting status of NOPROM-R, a manual build must be performed at the target level, as the FLM53109 warning message ends the promote processing and the NOPROM rebuild step following the promote will not run.

Sample scenarios for each of the above are described below.

Load modules rebuilt at the next level (REBUILD): Scenario: There are DB2® table changes in the development group required for the updating of the DB2 DCLGEN copybooks, but these DB2 DCLGEN copybooks are not to be promoted until the DB2 changes are complete. At this stage, you create a fix for a program which uses one of the DB2 DCLGEN copybooks but does not require the other DB2 development changes. This fix needs to be promoted to production.
When building at the development level, the DB2 copybook is used so the program can be tested. But when promoting the program fix, you want the DB2 copybook not to be promoted and the program to be rebuilt at the next level using the version of the DB2 DCLGEN copybook at that level or above.
Load modules not rebuilt at the next level: Scenario: A copybook is being modified in development and a fix for a single program which uses the copybook needs to be promoted to production. However, promoting this copybook would cause problems when building other programs using the copybook after promotion.
You want to build using the development version of the copybook but, when promoting the program fix, wants the copybook not to be promoted and the program source, load and so on, promoted as is.

Note: By promoting everything except the copybook and its accounting record, the build map containing the non-promoted member is in a broken state. This is because the build map date and time for the non-promoted member does not match the member account record and member statistics date and time.