Run REORG only for ALTERs that placed in AREOR (exclude AREO*) and needed for newly deployed modules (Bind/Rebind) eg DROP COLUMN

Currently, the RUN_REORG_REBUILD option has the following characteristics

M = Mandatory. Generate REORG utility statements to remove REORG pending conditions. (only Reorg Pending)
A = All relevant. Generate all needed REORG utility statements to fully implement the effects of the changes (AREO* and AREOR) …
N = None. No REORG utility statements are generated.

We need a way to generate a reorg for all necessary pending states (AREOR and REORG PENDING) to materialize the changes for subsequent processes.
Tables with an AREO* state do not prevent any processing and can be cleaned up by the standard operating in our post-process.

Example:
ALTER T1 DROP COL;

Description:
With the ALTER, the table is placed in an advisory REORG-pending (AREOR) state.
A bind for a new Programm can only take place when the pending state has been removed.
The reorg is highly recommended to avoid outage and it is also necessary for the deployment process to be executed.

For this, another option like

D = DEFERED. Generate REORG utility Statements to remove AREOR pending conditions (for necessary deferred changes)

would make sense in order to distinguish between the optional and the required ones when generating reorgs.

With option "A", too many AREO* would be directly remedied, which could better be carried out at low load times.

Alternatively, it would also be possible to adjust the MANDANTORY option so that in future all pending states are considered that prevent further unrestricted processing. (REORG PENDING and AREOR)