IBM Reorg LOG NO AUX YES Should Error with RC 8 and not Just Issues Copy Pending Warnings for LOB Tablespaces due to the Lack of Inline Image Copies

Currently IBM Reorg LOG NO AUX YES On tables With LOB Columns just places LOB tablespaces into copy pending and issues related warning messages in the job output if there was no TEMPLATE (with the &SN. or &TS. parameters) for the COPYDDN to inline copy linked auxiliary LOB tablespaces. This makes IBM Reorg inconsistent, because if there was no inline Image Copy of the base table, then the IBM Reorg would crash with RC 8 (not just place the base tablespace into copy pending). The auxiliary LOB tablespace(s) are integral part(s) of the table with LOB columns, so they should be treated the same way regarding lack of Image Copies as the base tablespace by the IBM Reorg utility. This is a design flaw. Software defects are not only those where a job crashes and produces a dump. This is a Db2 software defect where the IBM Reorg utility succeeds when it shouldn't. I understand that by now there may be many clients & users who don't use TEMPLATEs for these types of IBM Reorgs as they may not update LOB data often, so the best way to fix this design defect is to provide a ZPARM like 'Allow LOG NO Reorg to Succeed Without AUX Copies' and default it to YES. That way existing scheduled IBM Reorg jobs of the type described above would not need to be changed by clients. However, in our case due to the reorg succeeding with placing AUX tablespaces in COPY PENDING the application immediately wanted to update the LOBs and crashed with -904s causing a serious impact.