Analyze current Db2 UPDATE results

Prove existing immediate checks that permit continuation only for SQLCODE zero and SQLERRD(3) one. Require a complete supported direct UPDATE, one SQL island and source-proven system SQLCA storage under an approved STDSQL(NO) contract. Accept one structure qualifier in SQL hosts. This result-domain analysis does not establish host bindings or SQL type compatibility. Reject active WHENEVER handlers and unresolved source. Evaluate up to eight adjacent checks using terminal IF rejection gates or ordered EVALUATE SQLCODE selection. Use complete SQLCODE comparisons against integer literals with AND, OR and NOT. Affected-count comparisons remain limited to one. Support up to 32 WHEN groups, 64 numeric literal labels and 64 branch statements per EVALUATE. Preserve first-match behavior and the implicit no-match path when OTHER is absent. Require supported rejection checks, no-ops or terminal exits in each reachable branch. Do not skip a report or unknown effect on a continuing branch. Each reported other-value case represents integers outside the required value. Internally preserve selected SQLCODE literals, their exact complement and affected-count correlations across successive checks. Project onto the four reported combinations only after the modeled sequence. Empty continuing domains do not establish success. Intervening effects and unsupported checks stop the proof. Report evidence without changing source or producing vulnerability findings. This proves result handling on the path following the UPDATE. It does not prove execution, key uniqueness, prior-version provenance, concurrency protection, authorization or transaction completion. 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.