verify-cobol-artifacts

COBOL Artifact Verification Recipes

Use these recipes to verify that analysis artifacts accurately reflect the source code. Each recipe specifies what to check, where to check it, and what constitutes a pass or fail.

Verify Transaction IDs (transactions)

Claim: Business-rules frontmatter says transactions: ["XXXX"]

Verification steps:

1. Grep the source for any variable with TRANID or TRANSID in its name:

   Grep pattern: "TRANID|TRANSID" on the program source
   

2. Read the VALUE clause -- it must match the frontmatter value exactly.
3. Cross-check: grep for EXEC CICS RETURN.*TRANSID -- the TRANSID variable should resolve to the same value.
4. Cross-check: if CSD files exist, grep for DEFINE TRANSACTION to confirm the mapping.

Pass: VALUE matches frontmatter. All cross-references agree. Fail: VALUE differs from frontmatter, or no TRANSID found but frontmatter claims one. Log as correction_needed.

Verify Call Relationships (calls, called_by)

Claim: Frontmatter says calls: ["PROGNAME"]

Verification steps:

1. Grep the source for CALL ':

   Grep pattern: "CALL '" on the program source
   

2. Every literal in CALL statements should appear in the calls list.
3. For called_by: check the caller's source for CALL 'THIS-PROGRAM'.

Pass: All CALL targets match. called_by is consistent with callers' calls lists. Fail: Missing CALL target in frontmatter, or called_by references a program that doesn't actually CALL this one. Also check XCTL and LINK.

Verify File I/O (reads, writes)

Claim: Frontmatter says reads: ["ACCTDAT", "CUSTDAT"]

Verification steps:

1. Grep for actual I/O operations:

   Grep pattern: "EXEC CICS.*(READ|WRITE|REWRITE|DELETE)|OPEN.*(INPUT|OUTPUT|I-O|EXTEND)" on the source
   

2. For CICS: extract FILE(x) or DATASET(x) from each match. For batch: extract file names from OPEN statements and cross-reference with SELECT...ASSIGN.
3. Resolve variable names against DATA DIVISION VALUE clauses.
4. Compare resolved names against frontmatter reads and writes.