Propose Db2 SELECT output guards

Guard a full copy of one SELECT output under an explicit approved result policy. Require SQLCODE zero and the exact output indicator zero. Require exact caller and ordinary COPY snapshots, one plain selected column, resolved ordinary hosts, matching approved diagnostics and inactive WHENEVER handlers. Require a PIC X output and its signed two-byte binary indicator. Keep input hosts and the copy destination separate from output, indicator and diagnostic storage. Accept one structure qualifier. Reject input indicators, multiple outputs, expressions, aliases and incomplete source. Insert a typed IF before the full equal-width MOVE. Support shared sentences and preserve every original byte and period. Reject every other result through the approved existing terminal exit. Independently prove the changed tree requires both zero values before the exact original copy. Existing complete checks remain unchanged. Support up to seven adjacent IF or EVALUATE checks when their complete result domain still permits a rejected outcome before the exact copy. EVALUATE selects bounded SQLCODE literals with ordered first-match behavior. Preserve exact values and indicator correlations across successive selections. Support complete SQLCODE comparisons with integer literals, AND, OR and NOT. Unknown conditions and intervening effects remain unresolved without findings. Eight incomplete checks can establish a finding but leave no room for a proposed guard within the eight-check proof. Existing checks that exclude every approved outcome also prevent a proposal. Report conditional CWE-252 only when a proven continuation to the output copy still permits a result rejected by the approved policy. An unproven exit or insertion leaves a finding without an edit. Application-team review remains required. The approved contract supplies the null and truncation policy. No universal null rejection, warning handling or not-found behavior is inferred. This does not establish SQL execution, database type compatibility, business validity, authorization, later use or transaction completion. Do not add retries, commits, rollbacks, ABEND or new error routines. Limit each condition to 64 atomic comparisons and the sequence to 1024 distinct nonzero SQLCODE literals. Ordered comparisons preserve exact integer intervals. They require every SQLCODE boundary in the sequence to have an absolute value no greater than 999999998. Unsupported expressions remain unresolved.