Propose Db2 INSERT response guards

Proprietary

Propose two typed guards before an approved literal success report. Only SQLCODE 0 continues. SQLCODE -803 reaches the approved duplicate exit. Every other result reaches the approved error exit. Require exact caller and schema snapshots and adjacent direct statements in one paragraph. They may share a sentence. Preserve every existing period and add no period inside a shared sentence. Reject a sentence jump that can skip the INSERT and reach the report across a boundary. Accept one explicit row of plain host values supplying every column in a qualified table. Require one ordinary CREATE TABLE with INTEGER or CHAR columns and one nonnullable primary key. The contract establishes that this artifact is the complete enforced schema at this site. Prove diagnostic declarations under the approved STDSQL mode and reject active WHENEVER handlers. Prove both existing jump paths terminate within 64 statements and 16 paragraphs. Preserve SQL, constraints, original statements, comments, periods, messages and existing transaction behavior. Reject aliases, unknown preprocessing, unsupported storage and unproven exits. Require fixed-format UTF-8 with consistent LF or CRLF endings. Report barriers without guessing. This does not prove database type compatibility, row counts, transaction completion or which constraint caused -803. Do not add retries, commits, rollbacks, ABEND or new error routines.

io.moderne.mainframe.security.ProposeDb2InsertResponseGuard

Required

Exact repository-relative source path covered by the approved contract.

Exact program ID. Retain quotes for a literal ID. Literal contents match case exactly.

Lowercase SHA-256 of the complete UTF-8 source text without a byte order mark. The approved contract must cover this exact snapshot. Any source change prevents application.

One-based EXEC SQL INSERT line in the approved source snapshot.

One-based literal DISPLAY line approved as the success report for this INSERT.

Exact unquoted qualified table name in uppercase. The contract must approve the supplied schema as the complete enforced schema at this site.

Exact repository-relative path of the approved standalone DDL member.

Lowercase SHA-256 of the complete approved UTF-8 schema source without a byte order mark.

Approved Db2 SQL processing mode for this exact snapshot. Approve STDSQL(YES) with standalone diagnostics or STDSQL(NO) with an explicit standard SQLCA include. The source must prove the corresponding declarations. The recipe does not infer or change the build mode.

Existing paragraph approved for every result other than 0 and -803 at this exact site. An optional IN or OF section qualifier is supported. The contract must establish that this path preserves required cleanup, messages and transaction behavior.

Existing terminal paragraph approved for every SQLCODE -803 outcome at this site. The contract must preserve required messages, cleanup and transaction behavior.

Provenance of the approved diagnostic mode, response and exit contract. The recipe records this input and does not fetch or infer the contract.

mod run . --recipe=io.moderne.mainframe.security.ProposeDb2InsertResponseGuard \ -P sourcePath=security/cbl/VSIGGOOD.cbl \ -P programName=VSIGGOOD \ -P sourceSha256=0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef \ -P commandLine=15 \ -P successLine=17 \ -P tableName=VTEST.ITEM \ -P schemaSourcePath=security/ddl/VSITEM.ddl \ -P schemaSha256=0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef \ -P diagnosticMode='STDSQL(YES)' \ -P errorExit='SQL-ERROR IN ERROR-HANDLERS' \ -P duplicateExit=DUPLICATE-EXIT \ -P contractSource='mainframe-fixtures/README.md fictional INSERT response contract'

Install it once from Recipe actions, then run it on every repository under the current directory. New to the Moderne CLI? Set it up.