Source-derived document; review findings and open questions with the application owner.

Hazards, unknowns and backlog

Hazards

Concurrent updates can be detected when fetched records differ from old commarea values. A failed customer update after a successful account update triggers SYNCPOINT ROLLBACK according to the supplied evidence. E0001

Unknown record types during import are written to an error output file and counted rather than described as successfully imported. E0001

Unknowns

The supplied evidence does not establish the complete interest-rate business rules, state and ZIP validation logic, export-record structure, COBDATFT date-formatting logic, CICS transaction definitions, region configuration, actors, decisions, or security boundaries. E0001

Unresolved relationship

COACTUPC — handles — Account Update transaction (CAUP)

The supplied evidence explicitly identifies COACTUPC as the CICS program for Account Update transaction (CAUP) and describes its input editing, comparison, locking, and update behavior. E0001

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COACTVWC — handles — Account View transaction (CAVW)

The supplied evidence explicitly identifies COACTVWC as the CICS program for Account View transaction (CAVW) and describes its retrieval and display behavior. E0001

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CBEXPORT — creates — multi-record export file

The supplied evidence states that CBEXPORT reads normalized CardDemo files and creates a multi-record export file for branch migration. E0001

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CBIMPORT — splits — multi-record export file

The supplied evidence states that CBIMPORT reads the multi-record export file and splits it into separate normalized target files for customer, account, card, and transaction data. E0001

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

Potential defects include a duplicate paragraph in `COACTVWC.cbl`, a malformed phone blank test, likely reversed EFT and primary-card-holder attributes, ineffective zero-debit substitution, suspicious identifier spelling, compiler-dependent condition syntax, and possibly unset “not found” conditions. E0002

Unknowns

Actors, capabilities, user journeys, state transitions, business decisions, external systems, and confirmed runtime outcomes are not established by the supplied evidence. E0002

Hazards

The apparent `EXPIRAION` spelling may be an established interface name rather than a defect. The discrepancy between ten-character account ZIP storage and five-character screen output may indicate a possible data-loss or validation concern, but impact is unknown. E0002

Unknowns

Unknown: The exact BMS source and version, field-to-record mappings, compile-time numeric encoding, file keys and access methods, CVV protection, spelling consistency, validation behavior, interest calculations, batch behavior, and export/import behavior are not resolved by this source range. E0002

The supplied evidence also contains a contract-gap inconsistency: it says retained coverage omits `COACTVW.CPY` and the three `CVACT` copybooks, although those four artifacts are present in the displayed evidence. Whether “retained source coverage” refers to an external inventory is unknown. E0002

Unresolved relationship

CARD-XREF-RECORD — demonstrates a card-to-customer/account cross-reference layout

`CARD-XREF-RECORD` contains card number, customer ID, and account ID fields. This directly supports the existence of a cross-reference layout, but does not establish file organization, keys, access mode, lookup direction, or error handling. E0002

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

Inference: A failure during coordinated IMS and DB2 authorization work could create consistency risk, which the documented two-phase commit is intended to address. The evidence does not establish the failure modes or recovery guarantees in detail. E0003

The complete handling of all possible IMS and DB2 return codes is not comprehensively documented. E0003

Unknowns

The complete IMS schema and segment relationships, DB2 plan and package names, MQ connection configuration, and fraud rules beyond insufficient funds are not established by the supplied evidence. E0003

Unresolved relationship

COPAUA0C — is triggered by — CP00

README evidence identifies COPAUA0C as the CICS authorization request processor triggered by transaction CP00. E0003

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COPAUS2C — is called from — COPAUS1C

README evidence identifies COPAUS2C as the fraud-marking and DB2-update program called from COPAUS1C. E0003

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COPAUS1C.cbl — links to — COPAUS2C.cbl

Observed: `COPAUS1C.cbl` links to `COPAUS2C.cbl`; the latter performs `AUTHFRDS` inserts and updates and handles duplicate-key processing. E0004

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COPAUA0C.cbl — uses — PAUTSUM0

Observed: `COPAUA0C.cbl`, `COPAUS0C.cbl`, and `COPAUS1C.cbl` use `PAUTSUM0` as the apparent IMS hierarchy root. E0004

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

PAUTSUM0 — has child — PAUTDTL1

Observed: The same programs use `PAUTDTL1` as the apparent child of `PAUTSUM0`. E0004

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

Potential operational hazards include deletion or replacement of output datasets during unload preparation and failure handling requiring system dumps or error capture; these are supported operational configurations, not evidence of actual incidents. E0005

Unknowns

Unknown: The supplied evidence does not establish the COBOL implementation logic, IMS-to-relational mapping, job scheduling, fraud algorithms, complete authorization states, DB2 or MQ integration, or broader security model. E0005

Unresolved relationship

`DLIGSAMP` — defines access to — `DBPAUTP0`

Observed: PSB `DLIGSAMP` defines access to `DBPAUTP0` and GSAM databases for COBOL processing. E0005

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`DBPAUTX0` — provides indexed access to — `DBPAUTP0`

Inferred: The supplied evidence states that `DBPAUTX0` provides indexed access to `DBPAUTP0` through `ACCNTID`; this relationship is explicitly classified as inferred. E0005

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`CBPAUP0J` — executes — `CBPAUP0C`

Observed: Job `CBPAUP0J` executes IMS BMP program `CBPAUP0C` using `PSBPAUTB` to delete expired authorizations. E0005

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`LOADPADB` — executes — `PAUDBLOD`

Observed: Job `LOADPADB` executes IMS BMP program `PAUDBLOD` using `PSBPAUTB` to load input data. E0005

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

The six-byte discrepancy between `PAUTDTL1` and the unload child output is unresolved and could affect format compatibility. Its cause may be framing, metadata, a key, or utility-specific layout, but those possibilities are inference only. E0006

Claims of DB2/MQ integration, verified expiration deletion, useful diagnostic capture, precise IMS option semantics, or a field mapping between `CARDDEMO.AUTHFRDS` and `DBPAUTP0` are unsupported by the supplied evidence. E0006

Unknowns

Unknown: The relationship between `CARDDEMO.AUTHFRDS` and `DBPAUTP0`, exact load/unload transformations, runtime use of the IMS index, scheduling, restart behavior, transaction semantics, and business rules are not established by the supplied evidence. E0006

Unresolved relationship

DBPAUTX0 — declares an LCHILD relationship to — PAUTSUM0

`DBPAUTX0` declares an `LCHILD` relationship to `PAUTSUM0` using `INDEX=ACCNTID`. E0006

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

UNLDPADB.JCL — invokes — PAUDBUNL

`UNLDPADB.JCL` invokes `PAUDBUNL` with `PAUTBUNL` after removing existing flat files. E0006

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COTRN00C.cbl — lists transactions from — TRANSACT file

Observed relationship: The supplied evidence explicitly states that COTRN00C.cbl lists transactions from the TRANSACT file. E0007

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COTRN01C.cbl — views a specific transaction from — TRANSACT file

Observed relationship: The supplied evidence explicitly states that COTRN01C.cbl views a specific transaction from the TRANSACT file using a transaction ID. E0007

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COTRN02C.cbl — adds a new transaction to — TRANSACT file

Observed relationship: The supplied evidence explicitly states that COTRN02C.cbl adds a new transaction to the TRANSACT file after validating input data. E0007

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

In `app/cbl/CBTRN03C.cbl`, the reported EOF test occurs after a date test, and a later EOF branch adds `TRAN-AMT` to totals. Inference: stale prior-record data could be processed at EOF; this is a plausible defect, not a proven output failure. E0008

`app/cbl/CBTRN03C.cbl` also uses `NEXT SENTENCE` in date filtering. Inference: sentence-boundary-dependent control flow creates a maintainability and possible behavior risk. E0008

In `app/cbl/CBTRN01C.cbl`, `9000-DALYTRAN-CLOSE` reportedly checks `DALYTRAN-STATUS` but displays `ERROR CLOSING CUSTOMER FILE` and moves `CUSTFILE-STATUS` to `IO-STATUS`. Inference: a daily-transaction close failure could be misreported. E0008

In `app/cbl/CBTRN02C.cbl`, transaction-category balances are reportedly updated before account rewriting. Inference: an account rewrite failure could leave partial updates because rollback or compensating behavior is not visible; production occurrence is unproven. E0008

`app/cbl/COTRN02C.cbl` reportedly performs nested `EXEC CICS RETURN` operations from validation routines and the main procedure. Inference: this creates non-local control flow whose intended runtime behavior is undocumented. E0008

`app/cbl/CBTRN03C.cbl` contains distinct paragraph names sharing numeric prefixes, including `1110-WRITE-PAGE-TOTALS`, `1110-WRITE-GRAND-TOTALS`, `1120-WRITE-ACCOUNT-TOTALS`, `1120-WRITE-HEADERS`, and `1120-WRITE-DETAIL`. The names are not identical, so a compiler error is not established; compiler and control-flow verification remain warranted. E0008

Unknowns

The supplied evidence reports inconsistencies between contract metadata and displayed source coverage, including files listed as gaps while some are described as visibly present. Referenced copybooks such as `COCOM01Y`, `CSDAT01Y`, `CSMSG01Y`, and account/XREF definitions are not all supplied. E0008

The intended operational purpose of the opened-but-not-visibly-read customer, card, and transaction files in `app/cbl/CBTRN01C.cbl` is unknown. E0008

Unresolved relationship

`app/cbl/CBTRN02C.cbl` — writes rejects to — `DALYREJS`

The supplied evidence states that `app/cbl/CBTRN02C.cbl` writes rejected transactions to `DALYREJS` when validation fails. E0008

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`app/cbl/CBTRN03C.cbl` — writes a report over — transaction records

The supplied evidence states that `app/cbl/CBTRN03C.cbl` reads transaction data, filters it by date range, performs lookups, and writes a report. E0008

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

Unknown: Not established by the supplied evidence. The presence of a password-named field does not establish a security hazard or its mitigation. E0009

Execution and Usage

Unknown: It is unclear how `UNUSED-DATA` is populated, validated, or used by other program units because no calling or usage context is supplied. E0009

Intended Status

Unknown: The evidence does not establish whether `UNUSED-DATA` is currently active, reserved, obsolete, or merely named “unused”; that status is inferred only from the filename and structure name. E0009

Hazards

Referential integrity can prevent deletes, and concurrent updates can encounter deadlocks or lock failures. The evidence does not describe recovery procedures, retry policy, monitoring, or data-loss behavior for these conditions. E0010

Unknowns

Unknown: The exact VSAM synchronization formats, the complete DB2 schema and relationships, detailed CICS region configuration, non-DB2 CICS error behavior, and batch JCL parameters are not established by the supplied evidence. E0010

Unresolved relationship

Transaction Type Management module — is an optional extension for — CardDemo application

The module is described as an optional CardDemo application extension that demonstrates DB2 integration using embedded static SQL. E0010

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

Transaction Type Management module — adds options to — Admin Menu (CA00)

The module integrates with the base application by adding options 5 and 6 to Admin Menu (CA00) for transaction type management. E0010

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

Transaction Type Management module — maintains data in — DB2

The module maintains transaction types in DB2 for administrative functions. E0010

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

Transaction Type Management module — maintains data in — VSAM

The module also maintains transaction types in VSAM for high-performance transaction processing. E0010

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

TRANEXTR job — creates — VSAM-compatible files

TRANEXTR extracts current DB2 transaction type data and creates files compatible with VSAM processing. E0010

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

The CTTU insert path performs the SQL insert but does not visibly copy the resulting `SQLCODE` into `WS-DISP-SQLCODE` before building the error message; the displayed value may therefore be stale. This is a source-level defect indication, not proof of runtime failure. E0011

Paging stability under concurrent DB2 changes, exact delete-failure presentation, and the intended F6/F5 add behavior are not established by the supplied evidence. E0011

Unknowns

The supplied material omits or does not establish job-stream JCL, VSAM layouts, compiler options, DCLGENs, DB2 package bindings, complete copybook context, transaction configuration, and broader CICS runtime configuration. E0011

Unresolved relationship

CTTU — maps to — COTRTUPC

The supplied README and CSD define the online mapping `CTTU → COTRTUPC → COTRTUP`. The screen advertises `F6=Add`, but the visible program logic does not accept `PFK06`; its apparent new-record path uses F5 after a failed lookup. E0011

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CTLI — maps to — COTRTLIC

The supplied README and CSD define the online mapping `CTLI → COTRTLIC → COTRTLI`. `COTRTLIC.cbl` declares forward and backward cursors and performs transaction-type update and delete SQL. E0011

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

TRANSACTION_TYPE_CATEGORY — references — TRANSACTION_TYPE

`TRNTYCAT.ddl` and `DB2CREAT.ctl` show that `TRC_TYPE_CODE` references `TRANSACTION_TYPE.TR_TYPE` with `ON DELETE RESTRICT`. Both online programs visibly account for SQLCODE `-532`, although their state handling differs. E0011

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

The principal documented operational conditions are that missing plans or packages can produce return code 8 during the freeing step, and that extraction backup and cleanup are conditional on earlier-step success. The evidence does not establish recovery behavior for failed maintenance updates, invalid input, incomplete extraction, or dataset loss. E0012

Unknowns

The business logic and validation rules inside COBTUPDT are not visible in the JCL. The schemas and data types of TRANSACTION_TYPE and TRANSACTION_TYPE_CATEGORY are not supplied. The scheduler or trigger for the daily TRANEXTR.jcl run is also unknown. E0012

Unresolved relationship

CREADB21.jcl — initializes — CARDDEMO database

CREADB21.jcl initializes the CARDDEMO database and loads its initial reference data. E0012

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

MNTTRDB2.jcl — executes — COBTUPDT

MNTTRDB2.jcl executes the COBOL program COBTUPDT through the DSN command within an IKJEFT01 step. E0012

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

TRANEXTR.jcl — extracts — transaction type and category data

TRANEXTR.jcl extracts transaction type and category data into sequential datasets for reporting purposes. E0012

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COCRDLIC.cbl — implements — card listing logic

Observed: the source identifies `COCRDLIC.cbl` as the COBOL program implementing filtering, pagination, and selection handling for card listing. E0013

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COCRDLIC.cbl — transfers control with XCTL to — COCRDSLC.cbl

Observed: the evidence states that CICS XCTL transfers control between the list, detail, and update programs, and identifies `COCRDLIC.cbl` and `COCRDSLC.cbl` as the list and detail programs respectively. E0013

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

app/cbl/COCRDSLC.cbl — uses — CCRDSLA

`app/cbl/COCRDSLC.cbl` contains `CCRDSLA` as the value of `LIT-CCLISTMAP`, while `CCRDSLA` is identified as the detail-screen map in `app/bms/COCRDSL.bms` and `app/cpy-bms/COCRDSL.CPY`. E0014

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

app/cbl/COCRDUPC.cbl — rewrites — CARD-UPDATE-RECORD

`app/cbl/COCRDUPC.cbl` moves update values into the update record and then uses `CARD-UPDATE-RECORD` in the rewrite path. E0014

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS — is a VSAM cluster — VSAM cluster

Observed: The catalog identifies AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS as a VSAM cluster with defined key, record-length, and record-count metadata. E0015

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

AIX components — are linked to — KSDS clusters

Observed: The system has AIX components linked to KSDS clusters, indicating alternate key access paths to primary data. E0015

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

TRANSACT.BKUP — retains — historical backup generations

Observed: TRANSACT.BKUP is a GDG base with 76 generations and NOSCRATCH configuration, retaining rolled-off backup generations. E0015

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

Concurrent updates to the same user record are not explicitly addressed. The supplied evidence also does not establish recovery, audit logging, backup, or failure-compensation behavior. E0016

Unknowns

The initial page number and default sort order of the user list are not fully evident. The authentication mechanism for passwords, the underlying USRSEC storage technology, CICS region configuration, transaction definitions, and concurrent-update handling remain unknown. E0016

Unresolved relationship

CardDemo — manages — USRSEC

CardDemo manages user records stored in the USRSEC dataset. E0016

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COUSR00.bms — defines — list users screen

COUSR00.bms defines the mapset for the list users screen, including fields for user selection and details. E0016

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COUSR01.bms — defines — add user screen

COUSR01.bms defines the mapset for the add user screen with input fields for user details. E0016

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COUSR02.bms — defines — update user screen

COUSR02.bms defines the mapset for the update user screen with input fields for user details. E0016

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COUSR03.bms — defines — delete user screen

COUSR03.bms defines the mapset for the delete user screen with fields for user identification and details. E0016

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

Potential hazards include acceptance of user types outside the displayed `A`/`U` domain, apparent clear handling of passwords, ambiguous paging boundary behavior, unresolved update concurrency behavior, and misleading deletion-error text. These are evidence-based concerns, not confirmed runtime failures. E0017

Unknowns

Unknown: Authentication design, secure password storage, concurrency guarantees, lost-update protection, physical PF-key disabling, underlying dataset technology, and CICS region and file configuration are not established by the supplied evidence. E0017

Unresolved relationship

`COUSR01C.cbl` — writes — `USRSEC`

`COUSR01C.cbl` contains the add flow and a CICS `WRITE` operation for the `USRSEC` dataset. E0017

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`COUSR02C.cbl` — rewrites — `USRSEC`

`COUSR02C.cbl` reads a user record for update and later uses `REWRITE` against the `USRSEC` dataset. E0017

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`COUSR03C.cbl` — deletes from — `USRSEC`

`COUSR03C.cbl` contains `DELETE-USER-SEC-FILE`, which issues CICS `DELETE` after the selected record is read. E0017

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

The supplied evidence explicitly identifies risks of semantic incompleteness, incorrectness, and evidence omission during synthesis. It also states that the original fleet status is unchanged, but does not define the operational consequences of that condition. E0017

Unknowns

The supplied evidence does not establish the system’s actors, capabilities, journeys, domain states, interfaces, external dependencies, security model, or operational ownership. It also does not establish whether the recorded metadata is complete or semantically correct. E0017

Hazards

Initialization and maintenance operations delete or replace VSAM structures. Although some missing-file conditions are tolerated, the evidence does not establish safeguards against deleting the wrong dataset, partial replication, inconsistent alternate indexes, or interrupted processing. These are explicitly labeled inferences from the destructive operations and the missing recovery detail. E0018

Unknowns

The supplied evidence does not establish the internal COBOL logic of CBACT01C, CBACT02C, CBSTM03A, or similar programs; the exact interest and fee rules; flat-file layouts; the full CICS configuration; or concurrent-access handling for VSAM files. E0018

Unresolved relationship

CARDDEMO — deployed within — a CICS region

The system overview states that CARDDEMO is deployed within a CICS region and uses a CSD group named CARDDEMO for resource definitions. E0018

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CARDDEMO — manages — AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS

The account-data definition identifies AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS as the VSAM KSDS cluster managed by the system, with 11-byte keys. E0018

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CARDDEMO — manages — AWS.M2.CARDDEMO.CARDDATA.VSAM.KSDS

The card-data definition identifies AWS.M2.CARDDEMO.CARDDATA.VSAM.KSDS as the managed VSAM KSDS cluster, with 16-byte keys and an alternate index. E0018

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

Observed: Material hazards include duplicate CICS definitions, the `CCAD`/`CCDM` mismatch, malformed or inconsistent JCL, exposed credentials, contradictory FTP direction, and comments in `INTRDRJ2.JCL` claiming VSAM/IMS/index creation when only `REPRO IFILE(IN) OFILE(OUT)` is shown. E0019

Unknowns

Unknown: It is unresolved whether duplicate definitions are rejected, replaced, merged, or otherwise handled; whether `AWS.CCDA`, `AWS.M2.CARDEMO`, and `SYSAD` are intentional site-specific values; what record layouts `CBEXPORT` and `CBIMPORT` use; whether `CBIMPORT` performs hidden VSAM operations; and whether the malformed `CREASTMT.JCL` text is repository content or a transcription artifact. E0019

Unresolved relationship

app/jcl/ACCTFILE.jcl — defines — AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS

The source states that `app/jcl/ACCTFILE.jcl` deletes and defines this account KSDS and loads it using `REPRO INFILE(ACCTDATA) OUTFILE(ACCTVSAM)`. E0019

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

app/jcl/CARDFILE.jcl — creates — card alternate index

The source states that `app/jcl/CARDFILE.jcl` defines the card KSDS, creates an alternate index and path, and invokes `BLDINDEX`. E0019

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

app/jcl/CBADMCDJ.jcl — uses — DFHCSDUP

The source states that `app/jcl/CBADMCDJ.jcl` uses `DFHCSDUP` and defines the `CARDDEMO` CICS group, mapsets, programs, and transactions. E0019

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

app/jcl/INTRDRJ1.JCL — submits through — SYSOUT=(A,INTRDR)

The source states that `INTRDRJ1.JCL` submits JCL through the internal reader. This supports “internal reader submission mechanism,” not an intrusion mechanism. E0019

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

READCUST.jcl — executes — CBCUS01C

Observed: The supplied evidence states that `READCUST.jcl` executes program `CBCUS01C`. E0020

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CBCUS01C — reads — AWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDS

Observed: The supplied evidence states that `CBCUS01C` reads the customer master VSAM file `AWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDS`. E0020

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

READXREF.jcl — executes — CBACT03C

Observed: The supplied evidence states that `READXREF.jcl` executes program `CBACT03C`. E0020

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CBACT03C — reads — AWS.M2.CARDDEMO.CARDXREF.VSAM.KSDS

Observed: The supplied evidence states that `CBACT03C` reads the cross-reference master VSAM file `AWS.M2.CARDDEMO.CARDXREF.VSAM.KSDS`. E0020

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

TRANREPT.jcl — executes — CBTRN03C

Observed: The supplied evidence states that `TRANREPT.jcl` executes program `CBTRN03C` to produce a formatted report. E0020

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

Material hazards are the apparent delete-without-recreate path in `app/jcl/TRANBKP.jcl`, duplicate `STEP05R` names, hard-coded report dates, the `SYUID`/`SYSUID` discrepancy, and overlapping transaction setup jobs. E0021

Unknowns

Unknowns include successful processing, hidden unload/repro semantics, business meanings of physical offsets, the role of `DATEPARM`, CICS dataset mappings, accepted JCL syntax in the target environment, GDG lifecycle, and the authoritative execution order of transaction setup and backup jobs. E0021

Unresolved relationship

app/jcl/READCUST.jcl — executes — CBCUS01C

The source explicitly states that `app/jcl/READCUST.jcl` executes `CBCUS01C`. E0021

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

app/jcl/READCUST.jcl — maps DD CUSTFILE to — AWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDS

The source explicitly maps DD `CUSTFILE` to the customer VSAM KSDS. E0021

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

app/jcl/READXREF.jcl — executes — CBACT03C

The source explicitly states that `app/jcl/READXREF.jcl` executes `CBACT03C`. E0021

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

app/jcl/TRANFILE.jcl — defines and loads — the transaction KSDS

The source states that `app/jcl/TRANFILE.jcl` defines and loads the transaction KSDS and performs related alternate-index operations. E0021

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

Account Extractions module — optional extension for — CardDemo application

The supplied README identifies the Account Extractions module as an optional extension for the CardDemo application. E0022

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

Account Extractions module — demonstrates integration between — VSAM

The supplied evidence states that the module demonstrates integration between VSAM and IBM MQ; this relationship names the module and the VSAM side of that integration. E0022

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COACCT01 — associated with transaction — CDRA

The runtime and CICS configuration identify COACCT01 as the program for transaction CDRA. E0022

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CODATE01 — associated with transaction — CDRD

The runtime and CICS configuration identify CODATE01 as the program for transaction CDRD. E0022

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COACCT01 — reads data from — ACCTDAT

The account-inquiry flow states that COACCT01 reads the corresponding account record from the ACCTDAT VSAM dataset. E0022

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CSLKPCDY.cpy — defines — WS-US-PHONE-AREA-CODE-TO-EDIT

Observed relationship: `CSLKPCDY.cpy` defines `WS-US-PHONE-AREA-CODE-TO-EDIT` as a `PIC XXX` field for three-character phone area codes. E0023

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CSLKPCDY.cpy — defines — US-STATE-CODE-TO-EDIT

Observed relationship: `CSLKPCDY.cpy` defines `US-STATE-CODE-TO-EDIT` as a `PIC X(2)` field for two-character United States state codes. E0023

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

Operational hazards include file-processing errors and invalid or null UCB addresses. The documented response to file-processing errors is program abend through CEE3ABD. E0024

Unknowns

Unknown: The supplied evidence does not establish the COPY-book definitions, complete transaction layout, account-selection rules, HTML-selection criteria, complete return-code semantics, human actors, security model, deployment topology, scheduling, monitoring, recovery procedures, or performance characteristics. E0024

Unresolved relationship

CBSTM03A.CBL — communicates with — CBSTM03B.CBL

CBSTM03A.CBL uses the linkage area WS-M03B-AREA to communicate with CBSTM03B.CBL, which performs file operations based on the supplied operation code and file name. E0024

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CBSTM03B.CBL — performs file operations for — TRNXFILE

CBSTM03B.CBL handles opening, reading, and closing operations for TRNXFILE as part of its file-I/O responsibilities. E0024

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Invalid User Input

Invalid, empty, nonnumeric, or out-of-range dates can prevent processing and produce an error message. Invalid confirmation values likewise prevent valid submission. E0025

Queue Write Failure

A failed WRITEQ TD operation prevents the program from writing the batch request to the TDQ and causes an error indication. E0025

Unknowns

The supplied evidence does not establish the TRANREPT implementation, transaction-file reading and date-filtering logic, complete COMMAREA definitions, explicit behavior for a negative confirmation, security controls, or batch-job monitoring and completion behavior. E0025

Unresolved relationship

CORPT00C — submits batch jobs through — extra partition TDQ

CORPT00C is described as submitting batch jobs from an online CICS environment by writing JCL records to an extra partition TDQ for later execution. E0025

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

A failed build could otherwise be deployed or bound, so conditional NEWCOPY and DB2 binding steps provide inferred safeguards against promoting unsuccessful outputs. Temporary intermediate data sets are also explicitly cleaned up in the inferred BMS flow. E0026

Unknown: The evidence does not establish monitoring, alerting, rollback, concurrency controls, capacity limits, or failure recovery beyond these conditional steps. E0026

Unknowns

The exact CARDDEMO business logic and data structures, complete source and copybook inventory, DB2 schemas and SQL, CICS region configuration, transaction definitions, and disaster-recovery procedures remain unknown from the supplied JCL and procedure evidence. E0026

Unresolved relationship

BATCMP.jcl — invokes — BUILDBAT.prc

Inferred relationship: The batch compilation flow in `BATCMP.jcl` invokes the `BUILDBAT` procedure, represented by `BUILDBAT.prc`, with member-name and high-level-qualifier parameters. E0026

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CICCMP.jcl — invokes — BUILDONL.prc

Inferred relationship: The online CICS compilation flow in `CICCMP.jcl` invokes the `BUILDONL` procedure and then performs the documented NEWCOPY step. E0026

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CICDBCMP.jcl — invokes — BLDCIDB2.prc

Inferred relationship: The CICS DB2 compilation flow in `CICDBCMP.jcl` invokes `BLDCIDB2` with SSID, plan, and library parameters for the full build cycle. E0026

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

samples/jcl/BATCMP.jcl — invokes — BUILDBAT

`samples/jcl/BATCMP.jcl` invokes `BUILDBAT` with `MEM=&MEMNAME,HLQ=&HLQ`. E0027

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

samples/jcl/CICCMP.jcl — invokes — BUILDONL

`samples/jcl/CICCMP.jcl` invokes `BUILDONL` and includes an SDSF/CEMT program `NEWCOPY` command. E0027

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

samples/jcl/CICDBCMP.jcl — invokes — BLDCIDB2

`samples/jcl/CICDBCMP.jcl` invokes `BLDCIDB2` with `MEMNAME`, `HLQ`, `SSID`, and `PLAN`. E0027

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

samples/jcl/BMSCMP.jcl — invokes — BUILDBMS

`samples/jcl/BMSCMP.jcl` invokes `BUILDBMS` and then performs a CICS `NEWCOPY` for the generated map. E0027

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

Invalid input, unauthorized menu selection, unavailable target programs, and placeholder target programs interrupt the requested journey and display an error. The full message set and detailed CICS failure behavior remain partly unknown. E0028

Unknowns

The supplied evidence does not establish the contents of `TITLE01` and `TITLE02`, the complete error-message and color logic, the detailed sign-on screen or `COSGN00C` behavior, validation rules for customer, account, and card data, or explicit SEND and RECEIVE handling for CICS error response codes. E0028

Unresolved relationship

COMEN01C.cbl — serves as entry point for — CardDemo

`COMEN01C.cbl` is identified as the entry point for CardDemo’s main menu and handles navigation to sign-on and other application programs. E0028

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COMEN01C.cbl — transfers control to — COSGN00C

On initial entry, and by default after PF3 return handling, `COMEN01C.cbl` transfers control toward `COSGN00C` for the sign-on screen. E0028

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COMEN01C.cbl — uses — CARDDEMO-COMMAREA

`COMEN01C.cbl` maintains and passes `CARDDEMO-COMMAREA` to carry context and user, customer, account, and card information between programs. E0028

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Invalid Payment Conditions

Observed: Blank, unknown, or non-payable accounts and duplicate transaction IDs stop the relevant payment operation and produce an error message. E0029

Incomplete Transaction-ID Evidence

Unknown: The supplied evidence does not fully establish how the next transaction ID is generated or how concurrency is handled. E0029

Unestablished Semantic Categories

Unknown: The supplied evidence does not establish detailed data schemas, CICS environment behavior, authentication or authorization, operational deployment, recovery behavior, or the exact behavior of referenced programs. E0029

Unresolved relationship

CardDemo — includes — COBIL00C.cbl

Observed: The supplied overview names CardDemo as the application and states that it includes COBIL00C, represented in the source as COBIL00C.cbl. E0029

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COBIL00C.cbl — references — TRANSACT

Observed: COBIL00C.cbl references TRANSACT for transaction data. E0029

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COBIL00C.cbl — references — ACCTDAT

Observed: COBIL00C.cbl references ACCTDAT for account data and uses it when locating an account and validating its balance. E0029

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COBIL00C.cbl — references — CXACAIX

Observed: COBIL00C.cbl references CXACAIX for card cross-reference data. E0029

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COADM01C — serves — administrative users

`COADM01C` is explicitly identified as the Admin Menu for administrative users within the CardDemo application. E0030

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COADM01C — returns control to — COSGN00C

The program returns control to `COSGN00C` when no commarea is received and when PF3 is pressed. E0030

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COADM01C — uses — shared commarea structure

The evidence states that the program uses a shared commarea to pass context and data between the admin menu and invoked sub-programs. E0030

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COADM01C — uses — COADM02Y.cpy

The program relies on the menu-options definitions supplied by `COADM02Y.cpy`, which contains the six administrative entries. E0030

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

DAILY-TransactionBackup — starts with — CLOSEFIL

The daily transaction-backup flow starts with CLOSEFIL, then triggers CBPAUP0J, POSTTRAN, WAITSTEP, OPENFIL, and subsequent transaction-processing jobs. E0031

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CLOSEFIL — triggers — CBPAUP0J

The documented daily flow and component reference state that CLOSEFIL triggers CBPAUP0J. E0031

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

WAITSTEP — triggers — OPENFIL

WAITSTEP triggers OPENFIL, and OPENFIL subsequently triggers CLOSEFIL in the documented job cycle. E0031

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

MNTTRDB2 — triggers — TRANEXTR

MNTTRDB2 triggers TRANEXTR in the WEEKLY-TransactionTypesDBRefresh flow. E0031

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

INTCALC — triggers — COMBTRAN

INTCALC triggers COMBTRAN in the MONTHLY-InterestCalculation flow. E0031

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CardDemo — uses — CICS for transaction processing

The evidence states that the runtime environment includes CICS for transaction processing and that online functions are accessed through CICS transactions. E0032

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CardDemo — uses — JCL for batch processing

The evidence states that JCL provides batch processing and that batch jobs execute sequentially for initialization, loading, transaction processing, and file management. E0032

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CardDemo — stores data primarily in — VSAM (KSDS with AIX)

The evidence identifies VSAM, specifically KSDS with AIX, as the primary data-storage technology and identifies VSAM KSDS files for online transactions. E0032

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Documentation Overstatement

The Fleet Document’s “Confirmed” label is too strong when based on README prose. Online behavior, batch sequencing, VSAM lifecycle, MQ behavior, Db2 and IMS operations, and assembler behavior should remain documented claims rather than confirmed implementation facts. E0033

Repository Coverage

Unknown: It is not established whether the README-listed programs, jobs, maps, copybooks, and datasets exist in the repository, whether tests or CI configuration exist outside the supplied range, or whether the documented `main/-/data/EBCDIC/` path is correct. E0033

Unknowns

Unknown: The supplied evidence does not resolve optional-module boundaries, supported product versions, dataset and record definitions, restart procedures, credential restrictions, the authoritative meaning of `TRANBKP`, or the correctness of the competing batch sequences. E0033

Unresolved relationship

README.md — documents — CardDemo

The README documents CardDemo’s purpose, technology profile, online functions, batch guidance, installation material, and optional integrations. E0033

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CardDemo — uses — CICS

The documented technology profile identifies CICS for transaction processing in CardDemo. This relationship is documentation-based and not runtime-verified. E0033

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CardDemo — uses — VSAM KSDS with AIX

The README identifies VSAM KSDS with AIX as part of the documented data technology profile. E0033

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COSGN00C — XCTLs to — COADM01C

When the validated user type is ADMIN, COSGN00C XCTLs to COADM01C and passes CARDDEMO-COMMAREA. E0034

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COSGN00C — XCTLs to — COMEN01C

When the validated user type is not ADMIN, COSGN00C XCTLs to COMEN01C and passes CARDDEMO-COMMAREA. E0034

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

Invalid dates, insufficient data, and bad date values produce distinct validation outcomes and result messages. E0035

Inference: Suppressing return messages through `WS-RETURN-MSG-OFF` could reduce diagnostic detail when enabled, but the supplied evidence does not establish who controls the flag or why it is used. E0035

Unknowns

The complete century-validation rule is not documented beyond the stated acceptance of 19 and 20. E0035

The definitions and ownership of `WS-RETURN-MSG-OFF` and `WS-EDIT-VARIABLE-NAME` are not present in the supplied evidence. E0035

The actors, security boundaries, deployment context, calling applications, transport interfaces, and operational ownership are not established. E0035

Unresolved relationship

CSUTLDPY.cpy — calls — CSUTLDTC.cbl

The `EDIT-DATE-LE` paragraph in `CSUTLDPY.cpy` calls `CSUTLDTC` to validate a CCYYMMDD date using the `YYYYMMDD` format mask. E0035

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CSUTLDTC.cbl — invokes — CEEDAYS API

`CSUTLDTC.cbl` invokes the CEEDAYS API through a COBOL `CALL` statement as part of date validation and date conversion. E0035

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

cardxref.txt — maps — account balances

`cardxref.txt` maps card numbers to account balances, indicating a relationship between card usage and account financial status. The source describes this relationship as inferred rather than confirmed. E0036

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

dailytran.txt — links — merchant names

`dailytran.txt` links specific card numbers to merchant names and transaction amounts in daily transaction records. E0036

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

dailytran.txt — updates — account balances

Inference: Account balances are updated based on transaction activity, because the evidence describes account-balance fields alongside transaction processing. The exact update mechanism is not established. E0036

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

The absence of CICS journaling and automatic VSAM recovery may increase recovery risk after failures; this is an inference from JOURNAL(NO) and RECOVERY(NONE), not an observed incident. E0038

RUNAWAY(SYSTEM) permits the CICS region to terminate tasks exceeding time limits; the operational impact of such termination is not established. E0038

Unknowns

Unknown: The supplied evidence does not establish detailed business logic, calculation rules, user-interface layouts, VSAM record schemas, card-validation rules, credit-limit rules, transaction-authorization rules, JOBS queue integration, or the specific batch jobs submitted. E0038

Unresolved relationship

CARDDEMO — is organized within — CARDDEMO

The application is named CARDDEMO and is organized within a single CICS group also named CARDDEMO. E0038

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CC00 — invokes — COSGN00C

The confirmed login flow specifies transaction CC00 invoking program COSGN00C. E0038

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CAVW — invokes — COACTVWC

The confirmed account-viewing flow specifies transaction CAVW invoking program COACTVWC. E0038

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CAUP — invokes — COACTUPC

The confirmed account-update flow specifies transaction CAUP invoking program COACTUPC. E0038

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CLI — invokes — COCRDLIC

The confirmed card-listing flow specifies transaction CLI invoking program COCRDLIC. E0038

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CDV1 — invokes — COCRDSEC

The confirmed card-search flow specifies transaction CDV1 invoking program COCRDSEC. E0038

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

Observed: Processing cannot proceed when the FTP tunnel is unavailable, and scripts terminate for unsupported file types, missing parameters, missing files, or failed source transformation. E0039

Inference: These conditions create operational failure points for compilation, upload, refresh, and batch execution; recovery procedures and retry behavior are not established. E0039

Unknowns

Unknown: The supplied evidence does not establish human actors, detailed business rules, data schemas, CICS configuration, mainframe version or hardware, security controls, or recovery procedures. E0039

Unresolved relationship

`remote_compile.sh` — communicates with — `mainframe environment hosted by Ensono`

The supplied evidence states that `remote_compile.sh` uses an FTP tunnel to localhost port 2121 and uploads generated JCL to the remote mainframe environment hosted by Ensono. E0039

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`compile_batch.jcl.template` — defines steps for — `COBOL programs`

The supplied evidence states that the JCL template defines IGYCRCTL compilation and HEWL link-edit steps for COBOL programs. E0039

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CBCUS01C.cbl — reads — VSAM indexed file

Observed relationship: `CBCUS01C.cbl` reads customer data from a VSAM indexed file using sequential access. E0040

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CUSTFILE.jcl — manages — AWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDS

Observed relationship: `CUSTFILE.jcl` deletes, defines, and loads the named VSAM KSDS dataset. E0040

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CUSTFILE.jcl — copies data to — VSAM dataset

Observed relationship: `CUSTFILE.jcl` uses an IDCAMS REPRO operation to copy flat-file data into a VSAM dataset. E0040

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Undocumented Date Layout

Hazard: The exact formats of COINPDT and COOUTDT are not defined, limiting verification of the conversion and increasing the risk of incorrect integration assumptions. This is an evidence-based risk, not a demonstrated failure. E0041

Undocumented Wait Contract

Hazard: The behavior of ASMWAIT and the required structure of BINLBL are undocumented in the supplied source, limiting verification of delay semantics. E0041

Unclear Register Instruction

Unknown: The purpose of MVI 12(13),X'FF' in MVSWAIT is unclear; the source contains a comment questioning its removal. E0041

Missing Copybook

Unknown: The content and semantics of the COCDATFT copybook are not visible in the supplied evidence. E0041

Missing Success Semantics

Unknown: The evidence does not specify success indicators, return codes, exact output layouts, or the complete calling conventions for either module. E0041

Unresolved relationship

COBDATFT — references — COINTYPE

COBDATFT references the global field COINTYPE and uses it to select the input-format branch. E0041

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COBDATFT — references — COINPDT

COBDATFT reads COINPDT, validates COINPDT+4 in one branch, and copies and rearranges its fields to format the output date. E0041

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COBDATFT — references — COOUTYPE

COBDATFT checks COOUTYPE against COINTYPE to reject prohibited input/output combinations. E0041

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COBDATFT — sets — COERMSG

COBDATFT sets COERMSG to ‘INVALID INPUT’ in all identified error cases. E0041

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

MVSWAIT — executes — ASMWAIT

MVSWAIT executes ASMWAIT using BINLBL as the control block. E0041

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

Unknown: The supplied evidence does not establish failure modes, data-loss risks, duplicate-processing risks, restart behavior, or operational safeguards. E0042

Unknowns

The supplied evidence leaves error handling, operational behavior, uncertainties, and missing-evidence details unresolved. E0042

Unresolved relationship

TRANREPT.prc — invokes — REPROC.prc

`TRANREPT.prc` calls the reusable `REPROC` procedure as part of its transaction-reporting workflow, and `STEP01R` invokes that procedure for the transaction unload. E0042

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

REPROC.prc — executes — IDCAMS

`REPROC.prc` executes IDCAMS to manage VSAM file operations. E0042

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

TRANREPT.prc — executes — SORT

`TRANREPT.prc` executes SORT to filter and sort transaction records. E0042

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

TRANREPT.prc — executes — CBTRN03C

`TRANREPT.prc` executes `CBTRN03C` to produce formatted reports, using load library `AWS.M2.CARDDEMO.LOADLIB`. E0042

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

Invalid-input handling is a known uncertainty because the evidence does not show validation logic, conversion failures, or the conditions that populate `CODATECN-ERROR-MSG`. E0043

Unknowns

The actual date-conversion processing logic is absent. The calling program and execution context are also absent, so the system’s complete runtime behavior and integration boundaries cannot be determined. E0043

Unresolved relationship

CODATECN-REC — contains — CODATECN-INP-DATE

`CODATECN-REC` is described as containing the input fields used by date conversion, and `CODATECN-INP-DATE` is identified as the input-date field structure. E0043

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CODATECN-IN-REC — specifies — YYYYMMDD

The input record uses type indicators to specify that the input date is in `YYYYMMDD` format. E0043

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CODATECN-IN-REC — specifies — YYYY-MM-DD

The input record uses type indicators to specify that the input date is in `YYYY-MM-DD` format. E0043

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CODATECN-OUT-REC — specifies — YYYY-MM-DD

The output record uses type indicators to specify that the output should be in `YYYY-MM-DD` format. E0043

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CODATECN-OUT-REC — specifies — YYYYMMDD

The output record uses type indicators to specify that the output should be in `YYYYMMDD` format. E0043

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

An invalid key press is an identified user-input condition that produces a specific guidance message. E0044

Abnormal termination is an identified operational hazard for which the application provides structured diagnostic storage. E0044

Unknowns

The supplied evidence does not establish the application’s execution flows, invocation sequence, persistence behavior, recovery behavior, monitoring, deployment topology, performance characteristics, or ownership. E0044

The supplied evidence does not establish how predefined messages are displayed, how invalid keys are detected, or how abnormal-termination data is consumed after capture. E0044

Timing misuse

Inference: Incorrect values supplied to ASMWAIT could cause an unintended wait duration or affect coordination between processes. The supplied evidence does not establish parameter validation or safeguards. E0045

Error-message limitation

Inference: The fixed 38-byte COERMSG field may constrain the amount of error information retained. The evidence does not establish whether messages can be truncated, externalized, or supplemented elsewhere. E0045

Unknowns

The supplied evidence does not establish actors, user journeys, state transitions, decision logic, external interfaces, external systems, security boundaries, deployment details, parameter units, error-recovery behavior, or the source of values placed in the COCDATFT fields. E0045

Unresolved relationship

ASMWAIT.mac — defines — ASMWAIT

The supplied evidence explicitly states that ASMWAIT.mac defines a macro named ASMWAIT. E0045

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COCDATFT.mac — defines — COCDATFT

The supplied evidence explicitly states that COCDATFT.mac defines a DSECT named COCDATFT. E0045

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

Unknown: Not established by the supplied evidence. E0046

Unknowns

The business domain or application context is unknown. The exact command dialect, runtime engine, supported parameters, data formats, record structures, encodings, filtering behavior, transformation behavior, conditional processing, and failure handling are not established by the supplied evidence. E0046

Unresolved relationship

REPROCT.ctl — defines — REPRO command

The supplied evidence states that the execution flow is defined by the `REPRO` command in `REPROCT.ctl`. E0046

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

REPRO command — reads from — FILEIN

The supplied evidence states that `INFILE(FILEIN)` directs the reproduction process to read input records from `FILEIN`. E0046

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

REPRO command — writes to — FILEOUT

The supplied evidence states that `OUTFILE(FILEOUT)` directs the reproduction process to write output records to `FILEOUT`. E0046

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

Unknown: Runtime failure modes, operational hazards, and recovery requirements are not established by the supplied evidence. E0047

Unknowns

The specific business domain or application context for the CARDDEMO system is not explicitly defined in the diagram metadata. E0047

The semantic meaning of the “IMS” page structure remains unknown without visual inspection or parsing of the diagram content. E0047

Unresolved relationship

CARDDEMO-DataModel.drawio — contains — ER Diagram

The evidence explicitly states that the source file contains a diagram page named “ER Diagram.” E0047

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CARDDEMO-DataModel.drawio — contains — IMS

The evidence explicitly states that the source file contains a diagram page named “IMS.” E0047

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

Concurrent-update detection and rollback are described operational hazards. Additional potential hazards include ZIP-width mismatch, export/import sequence-width mismatch, file-organization mismatch, unprotected CVV data, and the listed source-code defects; their actual impact is not established. E0001 E0002

Unknowns

Unknown: The evidence does not resolve actors, security controls, decision ownership, complete business rules, validation logic, export structure, field mappings, runtime execution, configuration, file identity and keys, numeric encoding, or whether the separately described program and layout evidence belongs to one executing system. E0001 E0002

Unresolved relationship

COACTUPC — handles — Account Update transaction (CAUP)

COACTUPC is observed as a named component, and Account Update (CAUP) is observed as a named transaction. The supplied evidence explicitly states that COACTUPC handles CAUP and performs input editing, comparison, locking, and updates. E0001 E0002

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COACTVWC — handles — Account View transaction (CAVW)

COACTVWC is observed as a named component, and Account View (CAVW) is observed as a named transaction. The supplied evidence explicitly states that COACTVWC retrieves and displays account and customer details without modification. The copybook evidence confirms an account-view screen structure but not execution. E0001 E0002

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CBEXPORT — creates — multi-record export file

CBEXPORT is observed as an export component, and a multi-record export file is observed as an output artifact. The supplied evidence explicitly states that CBEXPORT reads normalized files and creates formatted export records for branch migration. E0001

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CBIMPORT — splits — multi-record export file

CBIMPORT is observed as an import component, and the multi-record export file is observed as an input artifact. The supplied evidence explicitly states that CBIMPORT reads it and splits records into normalized customer, account, card, and transaction files. E0001

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

Inference: Sending an MQ result before IMS persistence could expose inconsistent externally visible outcomes if the later write fails. The evidence also identifies possible malformed-input and response-length defects, but does not establish actual incidents. E0004

The supplied evidence disagrees on transaction guarantees: one description states two-phase commit across IMS and DB2, while source-focused evidence does not establish genuine two-phase commit or atomicity across MQ, IMS, CICS, and DB2. Failure modes, recovery guarantees, and complete return-code handling remain unknown. E0003 E0004

Unknowns

Unknown: The supplied evidence does not establish complete IMS schemas and mappings, fraud algorithms, authorization transitions, MQ configuration, DB2 plans and packages, scheduling, security architecture, error/re-entry semantics, or whether omitted repository material changes these conclusions. The assessment covers only source bytes `[0, 468762)` without per-file byte offsets. E0004 E0005

Unresolved relationship

COPAUA0C — is triggered by — CP00

`COPAUA0C` is the CICS authorization request processor, and `CP00` is the transaction identified as triggering it. E0003

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COPAUS2C — is called from — COPAUS1C

`COPAUS1C` is the interactive authorization-detail program, and `COPAUS2C` performs fraud marking and DB2 updates when invoked from it. E0003 E0004

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COPAUS1C.cbl — links to — COPAUS2C.cbl

`COPAUS1C.cbl` links to `COPAUS2C.cbl`; the latter inserts or updates `AUTHFRDS` and handles duplicate-key processing. E0004

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COPAUA0C.cbl — uses — PAUTSUM0

`COPAUA0C.cbl` performs IMS operations and uses `PAUTSUM0` as the apparent IMS hierarchy root. E0004

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

PAUTSUM0 — has child — PAUTDTL1

The cited programs use `PAUTDTL1` as the apparent child segment of `PAUTSUM0`. E0004

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

DLIGSAMP — defines access to — DBPAUTP0

`DLIGSAMP` defines COBOL PSB access to `DBPAUTP0`, as well as to the GSAM databases `PADFLDBD` and `PASFLDBD`. E0005

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

DBPAUTX0 — provides indexed access to — DBPAUTP0

Inferred: `DBPAUTX0` is described as providing indexed access to `DBPAUTP0` through `ACCNTID`; the supplied evidence explicitly marks this relationship as inferred. E0005

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CBPAUP0J — executes — CBPAUP0C

`CBPAUP0J` executes IMS BMP program `CBPAUP0C` with `PSBPAUTB` for expired-authorization deletion. E0005

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

LOADPADB — executes — PAUDBLOD

`LOADPADB` executes IMS BMP program `PAUDBLOD` with `PSBPAUTB` to load input data. E0005

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

The unresolved six-byte child-record discrepancy may affect format compatibility; its cause is unknown. Potential risks also include stale-record processing at EOF, `NEXT SENTENCE` control-flow dependence, misreported close failures, partial updates if account rewriting fails, update-intent locking in a lookup, and nested CICS returns. These are inferences or plausible risks, not proven production failures. E0006 E0008

Unknowns

Unknown: The relationship between `CARDDEMO.AUTHFRDS` and `DBPAUTP0`, exact load/unload transformations, runtime index use, expired-authorization deletion, complete business rules, external integrations, security controls, scheduling, restart behavior, and transaction/recovery semantics are not established. The supplied evidence also reports inconsistent source-coverage metadata and unresolved version alignment between CICS and batch components. E0006 E0007 E0008

Unresolved relationship

DBPAUTX0 — declares an LCHILD relationship to — PAUTSUM0

`DBPAUTX0` is an IMS index-database declaration with packed six-byte `INDXSEQ`; `PAUTSUM0` is the declared 100-byte authorization root segment. The supplied DBD explicitly declares an `LCHILD` using `INDEX=ACCNTID`. This establishes a declared relationship, not proven runtime lookup or usage. E0006

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

UNLDPADB.JCL — invokes — PAUDBUNL

`UNLDPADB.JCL` is the unload job, and `PAUDBUNL` is the invoked unload program using `PAUTBUNL`. The job removes existing flat files before allocating replacement outputs. E0006

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COTRN00C.cbl — lists transactions from — TRANSACT file

`COTRN00C.cbl` is the CICS listing program, and `TRANSACT file` is the transaction data source. The evidence explicitly states that the program browses and lists that file. E0007

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COTRN01C.cbl — views a specific transaction from — TRANSACT file

`COTRN01C.cbl` is the CICS lookup program, and `TRANSACT file` is the transaction data source. The evidence states that lookup uses a transaction ID and handles not-found conditions. E0007

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COTRN02C.cbl — adds a new transaction to — TRANSACT file

`COTRN02C.cbl` is the CICS entry program, and `TRANSACT file` is the destination transaction file. The evidence states that validated input is written as a new transaction. E0007

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`app/cbl/CBTRN02C.cbl` — writes rejects to — `DALYREJS`

`app/cbl/CBTRN02C.cbl` is the batch posting program, and `DALYREJS` is the reject file. The evidence states that failed validations are written there. E0008

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`app/cbl/CBTRN03C.cbl` — writes a report over — transaction records

`app/cbl/CBTRN03C.cbl` is the reporting program, and transaction records are its input data. It reads, date-filters, performs lookups, and writes a report. E0008

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

Observed: Referential integrity can block deletes, concurrent updates can encounter deadlocks or lock failures, and the CTTU insert path may display a stale SQLCODE because the resulting code is not visibly copied before error-message construction. The last point is a source-level defect indication, not proof of runtime failure. E0010 E0011

Unknown: Paging stability under concurrent changes, exact delete-failure presentation, recovery, retries, monitoring, and password-field risk or mitigation are not established. E0009 E0010 E0011

Execution and Usage

Unknown: How `UNUSED-DATA` is populated, validated, or used by other program units is not supplied. E0009

Intended Status

Unknown: The evidence does not establish whether `UNUSED-DATA` is active, reserved, obsolete, or merely named “unused.” E0009

Current-System Scope

Unknown: One supplied current-system observation provides detailed DB2/CICS, VSAM, batch, and component behavior, while another marks several corresponding categories as unknown. The supplied evidence does not explain whether this is a scope or evidence-coverage difference, so the disagreement is retained rather than resolved. E0010 E0011

Unresolved relationship

Transaction Type Management module — is an optional extension for — CardDemo application

Observed: The Transaction Type Management module is an optional extension of the CardDemo application and demonstrates DB2 integration using embedded static SQL. The named CardDemo application is the target endpoint. E0010

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

Transaction Type Management module — adds options to — Admin Menu (CA00)

Observed: The Transaction Type Management module is the source module, and Admin Menu (CA00) is the target menu; the module adds options 5 and 6 to that menu. E0010

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

Transaction Type Management module — maintains data in — DB2

Observed: The Transaction Type Management module maintains transaction types in the DB2 system for administrative functions. E0010

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

Transaction Type Management module — maintains data in — VSAM

Observed: The Transaction Type Management module maintains transaction types in the VSAM system for high-performance transaction processing. E0010

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

TRANEXTR job — creates — VSAM-compatible files

Observed: TRANEXTR extracts current DB2 transaction-type data and creates VSAM-compatible files. E0010

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CTTU — maps to — COTRTUPC

Observed: CTTU is the CICS transaction source, and `COTRTUPC` is the mapped online program; the supplied README and CSD define `CTTU → COTRTUPC → COTRTUP`. E0011

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CTLI — maps to — COTRTLIC

Observed: CTLI is the CICS transaction source, and `COTRTLIC` is the mapped online program; `COTRTLIC.cbl` declares forward and backward cursors and performs transaction-type update and delete SQL. E0011

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

TRANSACTION_TYPE_CATEGORY — references — TRANSACTION_TYPE

Observed: `TRANSACTION_TYPE_CATEGORY` is represented by `TRNTYCAT.ddl` and `TRANSACTION_TYPE` by `TRNTYPE.ddl`; `TRC_TYPE_CODE` references `TRANSACTION_TYPE.TR_TYPE` with `ON DELETE RESTRICT`. E0011

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

Documented hazards include return code 8 when nonexistent plans or packages are freed, conditional extraction backup and cleanup, and unknown recovery for invalid maintenance input or failed extraction. E0012

Other observed or inferred hazards include the apparently unreachable PF7 branch, card-number-only reads, possible CVV loss during update, an editable card-number identity during rewrite, the standalone `I`, and inconsistent map naming. E0014

Unknowns

Unknown: COBTUPDT business rules, DB2 schemas and data types, the daily extraction trigger, actual VSAM dataset names, role-determination rules, and the reported contradiction concerning generated copybooks are not resolved by the supplied evidence. E0012 E0013 E0014

Unresolved relationship

CREADB21.jcl — initializes — CARDDEMO database

`CREADB21.jcl` initializes the CARDDEMO database and loads initial reference data. The source endpoint and target database are both identified in the supplied observations. E0012

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

MNTTRDB2.jcl — executes — COBTUPDT

`MNTTRDB2.jcl` executes `COBTUPDT` through a DSN command in an IKJEFT01 step. E0012

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

TRANEXTR.jcl — extracts — transaction type and category data

`TRANEXTR.jcl` extracts transaction type and category data into sequential reporting datasets. E0012

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COCRDLIC.cbl — implements — card listing logic

`COCRDLIC.cbl` implements filtering, pagination, selection handling, and sequential card-file browsing. E0013

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COCRDLIC.cbl — transfers control with XCTL to — COCRDSLC.cbl

The CICS application uses XCTL among listing, detail, and update functions, and identifies `COCRDLIC.cbl` as the listing program and `COCRDSLC.cbl` as the detail program. E0013

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

app/cbl/COCRDSLC.cbl — uses — CCRDSLA

`app/cbl/COCRDSLC.cbl` contains `CCRDSLA` as its map literal, while the supplied BMS and copybook evidence identifies `CCRDSLA` as the detail-screen map. E0014

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

app/cbl/COCRDUPC.cbl — rewrites — CARD-UPDATE-RECORD

`app/cbl/COCRDUPC.cbl` moves update values into `CARD-UPDATE-RECORD` and uses that record in the rewrite path. E0014

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CardDemo — manages — USRSEC

`CardDemo` is a CICS COBOL program suite supporting user maintenance, and `USRSEC` stores the user records described by the `SEC-USER-DATA` structure. The supplied evidence explicitly states that CardDemo manages those records. E0016

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`COUSR01C.cbl` — writes — `USRSEC`

`COUSR01C.cbl` contains the add-user flow, and `USRSEC` is the dataset receiving the new user record through a CICS `WRITE`. E0017

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`COUSR02C.cbl` — rewrites — `USRSEC`

`COUSR02C.cbl` reads a user record for update and later issues `REWRITE` against `USRSEC`. E0017

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`COUSR03C.cbl` — deletes from — `USRSEC`

`COUSR03C.cbl` contains `DELETE-USER-SEC-FILE`, and `USRSEC` is the dataset from which the selected record is deleted after it is read. E0017

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`COUSR00.bms` — defines — list users screen

`COUSR00.bms` defines the mapset for the list-users screen, and that screen contains user-selection and user-detail fields. E0016

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`COUSR01.bms` — defines — add user screen

`COUSR01.bms` defines the add-user mapset, and the screen contains input fields for user details. E0016

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`COUSR02.bms` — defines — update user screen

`COUSR02.bms` defines the update-user mapset, and the screen contains input fields for user details. E0016

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`COUSR03.bms` — defines — delete user screen

`COUSR03.bms` defines the delete-user mapset, and the screen contains user-identification and detail fields. E0016

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

TRANSACT.BKUP — retains — historical backup generations

`TRANSACT.BKUP` is a GDG base with 76 generations and `NOSCRATCH`; the configuration therefore retains rolled-off backup generations rather than automatically deleting them. E0015

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

AIX components — are linked to — KSDS clusters

The catalog identifies AIX components associated with KSDS clusters, providing alternate-key access paths to primary data. E0015

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS — is a VSAM cluster — VSAM cluster

The catalog identifies `AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS` as a VSAM cluster with defined key, record-length, and record-count metadata; the target is the catalog’s VSAM-cluster classification. E0015

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

Observed: Material hazards include destructive VSAM replacement, possible partial replication, inconsistent alternate indexes, duplicate CICS definitions, the `CCAD`/`CCDM` mismatch, malformed or contradictory JCL, exposed credentials, contradictory FTP direction, and comments claiming operations not shown by the JCL. E0018 E0019

Inference: These conditions create risks of operational failure, data inconsistency, unauthorized access, and mistaken interpretation, but their actual consequences are unknown. E0017 E0018 E0019

Unknowns

Unknown: The supplied evidence does not establish actors, complete domain states, internal COBOL logic, flat-file layouts, business rules, full CICS configuration, concurrent VSAM handling, operational ownership, current execution status, or whether recorded metadata is complete and semantically correct. E0017 E0018 E0019

Unresolved relationship

CARDDEMO — deployed within — a CICS region

CARDDEMO is observed as deployed within a CICS region, with resource definitions managed through a CSD group named `CARDDEMO`; the target is identified only as a CICS region. E0018

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CARDDEMO — manages — AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS

CARDDEMO is the described system, and `AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS` is its 11-byte-key account-data VSAM KSDS cluster. E0018

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CARDDEMO — manages — AWS.M2.CARDDEMO.CARDDATA.VSAM.KSDS

CARDDEMO is the described system, and `AWS.M2.CARDDEMO.CARDDATA.VSAM.KSDS` is its 16-byte-key card-data VSAM KSDS cluster with an alternate index. E0018

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

app/jcl/ACCTFILE.jcl — defines — AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS

`app/jcl/ACCTFILE.jcl` is observed deleting and defining the account KSDS and loading it with `REPRO INFILE(ACCTDATA) OUTFILE(ACCTVSAM)`; the target dataset is the account KSDS described above. E0019

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

app/jcl/CARDFILE.jcl — creates — card alternate index

`app/jcl/CARDFILE.jcl` is observed defining the card KSDS, creating an alternate index and path, and invoking `BLDINDEX`; the target is the card alternate index described above. E0019

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

app/jcl/CBADMCDJ.jcl — uses — DFHCSDUP

`app/jcl/CBADMCDJ.jcl` is observed using `DFHCSDUP` to define the `CARDDEMO` CICS group, mapsets, programs, and transactions; `DFHCSDUP` is the named resource-definition utility. E0019

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

app/jcl/INTRDRJ1.JCL — submits through — SYSOUT=(A,INTRDR)

`app/jcl/INTRDRJ1.JCL` is observed submitting JCL through the internal reader represented by `SYSOUT=(A,INTRDR)`; this is a job-submission mechanism, not an intrusion mechanism. E0019

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

Observed hazards include unavailable queue names, MQ failures, missing account records, transaction backout conditions, duplicate step names, possible symbol errors, hard-coded dates, overlapping setup jobs, and a transaction backup path that visibly deletes resources without showing recreation. E0021 E0022

Unknowns

Unknown: Retry limits, duplicate-message behavior, queue capacity, performance targets, disaster recovery, deployment procedures, monitoring ownership, authentication, and authorization remain unestablished. E0020 E0021 E0022

Unresolved relationship

`READCUST.jcl` — executes — `CBCUS01C`

`READCUST.jcl` is an observed component, and the supplied evidence explicitly states that it executes `CBCUS01C`, which is also an observed component. E0020 E0021

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`CBCUS01C` — reads — `AWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDS`

`CBCUS01C` is an observed component, and `AWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDS` is an observed customer-master dataset; the evidence explicitly states that the program reads it. E0020 E0021

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`READXREF.jcl` — executes — `CBACT03C`

`READXREF.jcl` is an observed component, and the evidence explicitly states that it executes observed component `CBACT03C`. E0020 E0021

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`CBACT03C` — reads — `AWS.M2.CARDDEMO.CARDXREF.VSAM.KSDS`

`CBACT03C` is an observed component, and the named cross-reference KSDS is an observed dataset; the evidence explicitly states that the program reads it. E0020 E0021

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`TRANREPT.jcl` — executes — `CBTRN03C`

`TRANREPT.jcl` and `CBTRN03C` are observed components, and the evidence explicitly states that the job executes the program to produce a formatted processed-transaction report. E0020 E0021

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

Account Extractions module — optional extension for — CardDemo application

The evidence identifies both the Account Extractions module and the CardDemo application and explicitly describes the former as an optional extension of the latter. E0022

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`COACCT01` — associated with transaction — `CDRA`

`COACCT01` and transaction `CDRA` are observed runtime components, and the CICS configuration explicitly associates the program with that transaction. E0022

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`CODATE01` — associated with transaction — `CDRD`

`CODATE01` and transaction `CDRD` are observed runtime components, and the CICS configuration explicitly associates the program with that transaction. E0022

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`COACCT01` — reads data from — `ACCTDAT`

`COACCT01` and `ACCTDAT` are observed components, and the account-inquiry evidence explicitly states that the program reads the corresponding VSAM record. E0022

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unknowns

Unknown: The supplied evidence does not establish human roles, complete copybook and transaction layouts, account-selection logic, full return-code semantics, COMMAREA contents, security controls, deployment details, or batch monitoring and completion behavior. E0024 E0025

Unresolved relationship

CSLKPCDY.cpy — defines — WS-US-PHONE-AREA-CODE-TO-EDIT

`CSLKPCDY.cpy` is observed to define `WS-US-PHONE-AREA-CODE-TO-EDIT` as a `PIC XXX` three-character phone-area-code field. Both the source copybook and target field are declared by that observation. E0023

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CSLKPCDY.cpy — defines — US-STATE-CODE-TO-EDIT

`CSLKPCDY.cpy` is observed to define `US-STATE-CODE-TO-EDIT` as a `PIC X(2)` two-character state-code field. Both endpoints are declared by the supplied evidence. E0023

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CBSTM03A.CBL — communicates with — CBSTM03B.CBL

`CBSTM03A.CBL` communicates with `CBSTM03B.CBL` through `WS-M03B-AREA`, supplying an operation code and file name and receiving `LK-M03B-RC`; `CBSTM03B.CBL` performs the requested file operation. E0024

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CBSTM03B.CBL — performs file operations for — TRNXFILE

`CBSTM03B.CBL` is observed to open, read, and close `TRNXFILE` as part of its file-I/O responsibilities. E0024

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CORPT00C — submits batch jobs through — extra partition TDQ

`CORPT00C` is observed to write JCL records to an extra-partition TDQ for later batch execution. Both the submitting program and queue endpoint are identified in the supplied evidence. E0025

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CORPT00C — relies on — TRANREPT

Inference: The evidence indicates that `CORPT00C` relies on the `TRANREPT` procedure in `AWS.M2.CARDDEMO.PROC` for report generation, but the procedure implementation is unavailable. E0025

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

Potential hazards include deployment or DB2 binding after unsuccessful builds, unexplained JCL conditions, hard-coded library qualifiers, unverified symbol propagation, RACF changes, destructive catalog recreation, and incomplete CICS response handling. Conditional steps and temporary-file cleanup are intended safeguards, but their effectiveness is not established. Monitoring, alerting, rollback, concurrency, capacity, disaster recovery, and failure recovery remain unknown. E0026 E0027 E0028

Unknowns

The supplied evidence does not establish CardDemo’s complete business logic, source inventory, title and message definitions, detailed sign-on behavior, data-validation rules, CICS region and transaction configuration, DB2 schemas and SQL, successful execution, production suitability, or lossless operational correctness. E0026 E0027 E0028

Unresolved relationship

`samples/jcl/BATCMP.jcl` — invokes — `BUILDBAT`

`samples/jcl/BATCMP.jcl` invokes `BUILDBAT` with `MEM=&MEMNAME` and `HLQ=&HLQ`; `BUILDBAT` is the batch COBOL compilation procedure. E0027

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`samples/jcl/CICCMP.jcl` — invokes — `BUILDONL`

`samples/jcl/CICCMP.jcl` invokes `BUILDONL` and includes an SDSF/CICS `NEWCOPY` operation; `BUILDONL` is the online CICS compilation procedure. Whether `NEWCOPY` is correctly gated by `COND=(4,LT)` remains disputed. E0026 E0027

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`samples/jcl/CICDBCMP.jcl` — invokes — `BLDCIDB2`

`samples/jcl/CICDBCMP.jcl` invokes `BLDCIDB2` with member, qualifier, SSID, and plan parameters; `BLDCIDB2` performs the described DB2-oriented build stages. Its internal label discrepancy remains unexplained. E0027

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`samples/jcl/BMSCMP.jcl` — invokes — `BUILDBMS`

`samples/jcl/BMSCMP.jcl` invokes `BUILDBMS` and then performs a CICS `NEWCOPY` for the generated map; `BUILDBMS` uses assembler and binder tooling for BMS map and DSECT generation. E0027

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`COMEN01C.cbl` — serves as entry point for — CardDemo

`COMEN01C.cbl` is identified as CardDemo’s main-menu entry point and handles navigation to sign-on and other application programs. E0028

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`COMEN01C.cbl` — transfers control to — `COSGN00C`

On initial entry, and by default after PF3 handling, `COMEN01C.cbl` transfers control toward `COSGN00C`; the detailed sign-on behavior is unknown. E0028

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`COMEN01C.cbl` — uses — `CARDDEMO-COMMAREA`

`COMEN01C.cbl` passes `CARDDEMO-COMMAREA` to carry context and user, customer, account, and card information between programs. E0028

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Invalid payment and dispatch conditions

Observed: Invalid accounts, non-positive balances, duplicate transaction IDs, invalid menu input, unsupported keys, and unavailable programs stop the relevant operation or dispatch. E0029 E0030

Unestablished system behavior

Unknown: Detailed data schemas, transaction-ID concurrency, authentication, authorization, deployment and recovery behavior, complete job state transitions, CICS environment behavior, and the exact behavior of referenced programs and jobs are not established by the supplied evidence. E0029 E0030 E0031

Unresolved relationship

CardDemo — includes — COBIL00C.cbl

Observed: CardDemo is identified as the application and as including `COBIL00C`, represented here as `COBIL00C.cbl`. E0029

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COBIL00C.cbl — references — TRANSACT

Observed: `COBIL00C.cbl` references `TRANSACT` for transaction data. `COBIL00C.cbl` is a CICS COBOL payment program, while `TRANSACT` is named data storage whose physical organization is unknown. E0029

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COBIL00C.cbl — references — ACCTDAT

Observed: `COBIL00C.cbl` uses `ACCTDAT` to locate accounts and validate balances. E0029

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COBIL00C.cbl — references — CXACAIX

Observed: `COBIL00C.cbl` references `CXACAIX` for card cross-reference data. E0029

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COADM01C — serves — administrative users

Observed: `COADM01C` is the CardDemo administrative menu for administrative users. E0030

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COADM01C — returns control to — COSGN00C

Observed: `COADM01C` returns control to `COSGN00C` when no commarea is received and after PF3. E0030

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COADM01C — uses — shared commarea structure

Observed: `COADM01C` uses shared commarea data to pass context to invoked subprograms; the structure is incomplete. E0030

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COADM01C — uses — COADM02Y.cpy

Observed: `COADM01C` relies on `COADM02Y.cpy` for its six menu entries. E0030

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

DAILY-TransactionBackup — starts with — CLOSEFIL

Observed: The daily backup flow starts with `CLOSEFIL`. `CLOSEFIL` is also documented as triggering `CBPAUP0J`. E0031

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CLOSEFIL — triggers — CBPAUP0J

Observed: The job-chain evidence explicitly states this trigger. E0031

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

WAITSTEP — triggers — OPENFIL

Observed: `WAITSTEP` triggers `OPENFIL`, which subsequently triggers `CLOSEFIL`. E0031

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

MNTTRDB2 — triggers — TRANEXTR

Observed: The weekly transaction-types refresh states this trigger. E0031

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

INTCALC — triggers — COMBTRAN

Observed: The monthly interest flow states this trigger. E0031

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CardDemo — uses — CICS for transaction processing

CardDemo is documented as a mainframe application whose online functions use CICS transaction processing. CICS is also observed in the runtime and in `COSGN00C` screen and program-control operations. E0032 E0033 E0034

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CardDemo — uses — JCL for batch processing

CardDemo’s documented batch execution uses JCL jobs for initialization, loading, transaction processing, and file management. JCL is therefore an explicitly documented processing technology, although the authoritative job sequence is disputed. E0032 E0033

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CardDemo — stores data primarily in — VSAM (KSDS with AIX)

VSAM KSDS with AIX is identified as CardDemo’s primary data-storage technology, including transaction files and related datasets. The supplied evidence does not provide the underlying definitions. E0032 E0033

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

README.md — documents — CardDemo

The README documents CardDemo’s purpose, technology profile, online functions, batch guidance, installation material, and optional integrations. Its claims are documentation-based and not independently runtime-verified. E0033

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COSGN00C — XCTLs to — COADM01C

After validated credentials identify the user as `ADMIN`, `COSGN00C` XCTLs to `COADM01C` and passes `CARDDEMO-COMMAREA`. The implementation of `COADM01C` is not available in the supplied bundle. E0034

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COSGN00C — XCTLs to — COMEN01C

After validated credentials identify a non-`ADMIN` user, `COSGN00C` XCTLs to `COMEN01C` and passes `CARDDEMO-COMMAREA`. The implementation of `COMEN01C` is not available in the supplied bundle. E0034

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

Invalid dates, insufficient data, and bad date values produce distinct validation outcomes. Inference: suppressing return messages could reduce diagnostic detail, but control and purpose of the flag are unknown. E0035

Potential data hazards include unresolved behavior for missing or inconsistent records, uncertain balance handling, unclear discount semantics, and possible temporal or referential mismatches. These are evidence gaps, not confirmed failure modes. E0036 E0037

Unknowns

The complete century rule, definitions and ownership of referenced date-message variables, actors, security boundaries, deployment context, calling applications, operational ownership, transaction processing, balance updates, discount calculations, and data-field semantics remain undocumented. E0035 E0036 E0037

Unresolved relationship

CSUTLDPY.cpy — calls — CSUTLDTC.cbl

The `EDIT-DATE-LE` paragraph in `CSUTLDPY.cpy` calls `CSUTLDTC` to validate a CCYYMMDD date using the `YYYYMMDD` format mask. `CSUTLDPY.cpy` contains the named reusable validation paragraphs, and `CSUTLDTC.cbl` contains the validation program. E0035

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CSUTLDTC.cbl — invokes — CEEDAYS API

`CSUTLDTC.cbl` invokes the CEEDAYS API through a COBOL `CALL` as part of date validation and date conversion. E0035

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

dailytran.txt — links — merchant names

`dailytran.txt` records contain card numbers, merchant names, transaction amounts, and timestamps, establishing that the transaction records link those fields. E0036

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

Inference: JOURNAL(NO) and RECOVERY(NONE) may increase recovery risk after failures; no incident is observed. RUNAWAY(SYSTEM) may terminate over-time tasks, but its operational impact is unknown. E0038

FTP-tunnel outages, invalid inputs, missing parameters or files, failed transformations, and critical VSAM errors are operational failure points. Recovery procedures, retry behavior, and non-VSAM error handling are not established. E0039 E0040

Unknowns

Unknown: Detailed business logic, security controls, data schemas, user interfaces, external integrations, submitted jobs, CICS configuration, mainframe platform details, and recovery procedures remain incompletely established by the supplied evidence. E0038 E0039 E0040

Unresolved relationship

CARDDEMO — is organized within — CARDDEMO

The application is named CARDDEMO, and the supplied configuration identifies a single CICS group with the same name. E0038

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CC00 — invokes — COSGN00C

CC00 is the login transaction, and the confirmed login flow specifies that it invokes COSGN00C. E0038

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CAVW — invokes — COACTVWC

CAVW is the account-viewing transaction, and the confirmed flow specifies that it invokes COACTVWC. E0038

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CAUP — invokes — COACTUPC

CAUP is the account-update transaction, and the confirmed flow specifies that it invokes COACTUPC. E0038

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CLI — invokes — COCRDLIC

CLI is the card-listing transaction, and the confirmed flow specifies that it invokes COCRDLIC. E0038

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CDV1 — invokes — COCRDSEC

CDV1 is the card-search transaction, and the confirmed flow specifies that it invokes COCRDSEC. E0038

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`remote_compile.sh` — communicates with — `mainframe environment hosted by Ensono`

`remote_compile.sh` uses an FTP tunnel to localhost port 2121 and uploads generated JCL to the Ensono-hosted remote mainframe. E0039

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`compile_batch.jcl.template` — defines steps for — `COBOL programs`

The template defines IGYCRCTL compilation and HEWL link-edit steps for COBOL programs. E0039

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CBCUS01C.cbl — reads — VSAM indexed file

CBCUS01C.cbl is a batch COBOL program that reads customer data sequentially from a VSAM indexed file. E0040

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CUSTFILE.jcl — manages — AWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDS

CUSTFILE.jcl deletes, defines, and loads the named VSAM KSDS dataset. E0040

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CUSTFILE.jcl — copies data to — VSAM dataset

CUSTFILE.jcl uses IDCAMS REPRO to copy flat-file data into a VSAM dataset. E0040

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

Hazards include undocumented date layouts and conversion logic, uncertain invalid-input behavior, and the undocumented ASMWAIT/BINLBL contract. These are evidence-based verification risks, not demonstrated failures. E0041 E0043

Unknown: Transaction failure modes, data-loss or duplicate-processing risks, safeguards, and restart behavior are not established. E0042

Unknowns

Unknown: The evidence does not establish complete success semantics, return codes, calling conventions, output layouts, copybook contents, operational ownership, or security behavior. E0041 E0042 E0043

Unresolved relationship

COBDATFT — references — COINTYPE

COBDATFT references the global field COINTYPE and uses it to select the input-format branch. COINTYPE is identified in the date-field observations. E0041

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COBDATFT — references — COINPDT

COBDATFT reads COINPDT, validates COINPDT+4 in one branch, and rearranges its fields into the output date. COINPDT is identified as a date field, although its complete layout is unknown. E0041

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COBDATFT — references — COOUTYPE

COBDATFT checks COOUTYPE against COINTYPE to reject prohibited combinations. COOUTYPE is identified as the output-type field. E0041

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COBDATFT — sets — COERMSG

COBDATFT sets COERMSG to `INVALID INPUT` for identified validation failures. COERMSG is identified as the associated error field. E0041

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

MVSWAIT — executes — ASMWAIT

MVSWAIT executes ASMWAIT using BINLBL as its control block. ASMWAIT is identified as the wait instruction, while its implementation and contract remain unknown. E0041

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

TRANREPT.prc — invokes — REPROC.prc

TRANREPT.prc invokes REPROC.prc during the transaction-reporting workflow, including the transaction unload step. Both procedures are identified as JCL components. E0042

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

REPROC.prc — executes — IDCAMS

REPROC.prc executes IDCAMS for VSAM file operations. IDCAMS is identified as a runtime utility. E0042

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

TRANREPT.prc — executes — SORT

TRANREPT.prc executes SORT to filter and sort transaction records. SORT is identified as a runtime utility. E0042

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

TRANREPT.prc — executes — CBTRN03C

TRANREPT.prc executes CBTRN03C to produce formatted reports using the stated load library. Both the procedure and program are identified in the supplied evidence. E0042

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CODATECN-REC — contains — CODATECN-INP-DATE

CODATECN-REC is described as containing the input fields used for conversion, and CODATECN-INP-DATE is the input-date structure. E0043

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

Invalid key presses produce specific user guidance, but detection, display, and subsequent handling are unknown. E0044

Abnormal termination is an identified operational hazard with structured diagnostic storage. E0044

Inference: Invalid `ASMWAIT` values could cause unintended wait durations or coordination effects, and the fixed 38-byte error field could constrain retained error information; validation, truncation, and supplementary storage are unknown. E0045

Unknown: Record-reproduction hazards and failure behavior are not established. E0046

Unknowns

The evidence does not establish actors, ownership, invocation sequence, state transitions, persistence, recovery, monitoring, deployment, performance, data semantics, external integrations, security, runtime specifics, parameter units, or error-recovery behavior. E0044 E0045 E0046

The evidence also does not establish how messages are displayed, how invalid keys are detected, how abnormal-termination data is consumed, or how values enter the date-processing layout. E0044 E0045

Unresolved relationship

ASMWAIT.mac — defines — ASMWAIT

`ASMWAIT.mac` is observed to define the `ASMWAIT` macro. E0045

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COCDATFT.mac — defines — COCDATFT

`COCDATFT.mac` is observed to define the `COCDATFT` DSECT. E0045

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

REPROCT.ctl — defines — REPRO command

`REPROCT.ctl` is observed to contain or define the `REPRO` command used by the execution flow. E0046

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

REPRO command — reads from — FILEIN

The `REPRO` command is observed with `INFILE(FILEIN)`, directing input reads from `FILEIN`. E0046

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

REPRO command — writes to — FILEOUT

The `REPRO` command is observed with `OUTFILE(FILEOUT)`, directing output writes to `FILEOUT`. E0046

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

Unknown: Runtime failure modes, operational hazards, and recovery requirements are not established by the supplied evidence. E0047

Unknowns

The specific business domain or application context for the CARDDEMO system is not explicitly defined in the diagram metadata. E0047

The semantic meaning of the “IMS” page structure remains unknown without visual inspection or parsing of the diagram content. E0047

Unresolved relationship

CARDDEMO-DataModel.drawio — contains — ER Diagram

The supplied evidence explicitly states that the source file contains a diagram page named “ER Diagram.” E0047

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CARDDEMO-DataModel.drawio — contains — IMS

The supplied evidence explicitly states that the source file contains a diagram page named “IMS.” E0047

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

Potential hazards include late IMS persistence after an MQ response, concurrent updates and rollback, malformed input, response-length defects, EOF and control-flow errors, partial updates, unprotected CVV data, width and encoding mismatches, file-organization mismatch, sequence truncation, and uncertain atomicity. These are reported or inferred risks, not established incidents. E0001 E0002 E0003 E0004 E0006 E0008

Unknowns

Unknown: Complete schemas and mappings, actors, security, fraud and business rules, lifecycle transitions, runtime execution, configuration, scheduling, keys, transformations, recovery, transaction guarantees, external contracts, version alignment, and whether omitted material changes these conclusions remain unresolved. E0001 E0002 E0003 E0004 E0005 E0006 E0007 E0008

Unresolved relationship

COACTUPC — handles — Account Update transaction (CAUP)

`COACTUPC` and Account Update (CAUP) are observed; the evidence explicitly states that the component handles the transaction. E0001 E0002

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COACTVWC — handles — Account View transaction (CAVW)

`COACTVWC` and Account View (CAVW) are observed; the evidence explicitly states that the component retrieves and displays account and customer details. E0001 E0002

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CBEXPORT — creates — multi-record export file

`CBEXPORT` and a multi-record export file are observed; the evidence states that the component creates formatted branch-migration records. E0001

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CBIMPORT — splits — multi-record export file

`CBIMPORT` and the multi-record export file are observed; the evidence states that it splits input into normalized files. E0001

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COPAUA0C — is triggered by — CP00

`COPAUA0C` and `CP00` are observed; the evidence identifies the transaction as its trigger. E0003

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COPAUS2C — is called from — COPAUS1C

Both programs are observed; the evidence states that the detail program invokes fraud persistence and updates. E0003 E0004

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COPAUS1C.cbl — links to — COPAUS2C.cbl

Both source files are observed; the evidence states that the first links to the second. E0004

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COPAUA0C.cbl — uses — PAUTSUM0

Both the program and IMS root segment are observed; the evidence describes the program as using that root. E0004

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

PAUTSUM0 — has child — PAUTDTL1

Both IMS segments are observed; the evidence describes `PAUTDTL1` as the child. E0004

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

DLIGSAMP — defines access to — DBPAUTP0

Both components are observed; the PSB evidence defines access to the IMS database. E0005

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

DBPAUTX0 — provides indexed access to — DBPAUTP0

Both components are observed; inference from the supplied evidence identifies indexed access through `ACCNTID`, explicitly marked inferred. E0005

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CBPAUP0J — executes — CBPAUP0C

Both job and program are observed; the JCL invokes the IMS BMP for expired-authorization deletion. E0005

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

LOADPADB — executes — PAUDBLOD

Both job and program are observed; the JCL invokes the load program. E0005

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

DBPAUTX0 — declares an LCHILD relationship to — PAUTSUM0

Both database/index declarations are observed; the DBD explicitly declares an `LCHILD` using `ACCNTID`, without proving runtime lookup. E0006

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

UNLDPADB.JCL — invokes — PAUDBUNL

Both job and program are observed; the job invokes the unload program and replaces flat-file outputs. E0006

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COTRN00C.cbl — lists transactions from — TRANSACT file

Both program and file are observed; the evidence states that the program browses and lists the file. E0007

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COTRN01C.cbl — views a specific transaction from — TRANSACT file

Both program and file are observed; the evidence states that lookup uses a transaction ID. E0007

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COTRN02C.cbl — adds a new transaction to — TRANSACT file

Both program and file are observed; the evidence states that validated input is written as a new transaction. E0007

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`app/cbl/CBTRN02C.cbl` — writes rejects to — `DALYREJS`

Both source program and reject file are observed; failed validations are reported as written there. E0008

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`app/cbl/CBTRN03C.cbl` — writes a report over — transaction records

Both reporting program and transaction records are observed; the evidence states that the program reads and reports on them. E0008

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

Referential-integrity deletion failures, deadlocks, unstable paging, possible record-isolation problems, unsupported user types, clear password handling, source-integrity concerns, and incomplete recovery or retry behavior are identified concerns. Their runtime impact and mitigations are not established. E0010 E0011 E0012 E0014 E0016 E0017

Unknowns

The evidence does not establish complete schemas, VSAM layouts and keys, authentication or authorization, job sequencing, scheduler triggers, recovery, monitoring, retention policy, runtime configuration, copybook usage, or the status and lifecycle of `UNUSED-DATA`. Conflicting observations about scope, PF7 behavior, generated copybooks, map names, and deployed artifacts are retained rather than resolved. E0009 E0010 E0011 E0012 E0013 E0014 E0015 E0016 E0017

Unresolved relationship

Transaction Type Management module — is an optional extension for — CardDemo application

The Transaction Type Management module is described as an optional CardDemo extension providing DB2 integration through embedded static SQL. Both named endpoints are observed. E0010

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

Transaction Type Management module — adds options to — Admin Menu (CA00)

The module adds options 5 and 6 to Admin Menu (CA00). Both the source module and target menu are explicitly identified. E0010

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

Transaction Type Management module — maintains data in — DB2

The module maintains transaction types in DB2 for administrative functions. E0010

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

Transaction Type Management module — maintains data in — VSAM

The module maintains transaction types in VSAM for transaction processing. E0010

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CTTU — maps to — COTRTUPC

CTTU is the CICS transaction and `COTRTUPC` is the mapped online program in the supplied mapping evidence. E0011

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CTLI — maps to — COTRTLIC

CTLI is the CICS transaction and `COTRTLIC` is the mapped online program performing transaction-type update and delete operations. E0011

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

TRANSACTION_TYPE_CATEGORY — references — TRANSACTION_TYPE

`TRANSACTION_TYPE_CATEGORY` and `TRANSACTION_TYPE` are represented by the named DB2 definitions, and `TRC_TYPE_CODE` references `TRANSACTION_TYPE.TR_TYPE` with `ON DELETE RESTRICT`. E0011

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CardDemo — manages — USRSEC

CardDemo is identified as the CICS COBOL suite managing user records stored in `USRSEC`. E0016

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`COUSR01C.cbl` — writes — `USRSEC`

`COUSR01C.cbl` contains the add-user flow and writes a new record to `USRSEC`. E0017

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`COUSR02C.cbl` — rewrites — `USRSEC`

`COUSR02C.cbl` reads a user record for update and issues `REWRITE` against `USRSEC`. E0017

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`COUSR03C.cbl` — deletes from — `USRSEC`

`COUSR03C.cbl` reads the selected record and deletes it from `USRSEC`. E0017

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

TRANEXTR job — creates — VSAM-compatible files

TRANEXTR extracts current DB2 transaction-type data into VSAM-compatible files. E0010

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

TRANSACT.BKUP — retains — historical backup generations

`TRANSACT.BKUP` is configured as a `NOSCRATCH` GDG base and retains rolled-off backup generations. E0015

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

Observed: Specific failure conditions include MQ failure, missing account records, TDQ-write failure, invalid dates or confirmations, file-processing errors, invalid UCB addresses, duplicate steps, symbol errors, and hard-coded report dates. E0021 E0022 E0024 E0025

Unknowns

Unknown: Complete business logic, data layouts, lifecycle models, security controls, deployment and sequencing, monitoring, retry behavior, retention, performance, and current operational status remain unestablished. E0017 E0018 E0019 E0020 E0021 E0022 E0023 E0024 E0025

Unresolved relationship

CARDDEMO — deployed within — a CICS region

Observed: CARDDEMO has CICS resource definitions in group `CARDDEMO`; a CICS region is the stated target context. E0018

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CARDDEMO — manages — AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS

Observed: CARDDEMO is the described system, and the named dataset is its 11-byte-key account KSDS. E0018

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CARDDEMO — manages — AWS.M2.CARDDEMO.CARDDATA.VSAM.KSDS

Observed: CARDDEMO is the described system, and the named dataset is its 16-byte-key card KSDS with an alternate index. E0018

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

app/jcl/ACCTFILE.jcl — defines — AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS

Observed: The JCL deletes, defines, and loads the named account KSDS. E0019

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

app/jcl/CARDFILE.jcl — creates — card alternate index

Observed: The JCL defines the card KSDS, alternate index, and path, then invokes `BLDINDEX`. E0019

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

app/jcl/CBADMCDJ.jcl — uses — DFHCSDUP

Observed: The JCL uses `DFHCSDUP` to define CICS groups, mapsets, programs, and transactions. E0019

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

app/jcl/INTRDRJ1.JCL — submits through — SYSOUT=(A,INTRDR)

Observed: The JCL submits subsequent JCL through the internal reader represented by `SYSOUT=(A,INTRDR)`. E0019

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`READCUST.jcl` — executes — `CBCUS01C`

Observed: `READCUST.jcl` executes the observed program `CBCUS01C`. E0020 E0021

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`CBCUS01C` — reads — `AWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDS`

Observed: `CBCUS01C` reads the observed customer-master KSDS. E0020 E0021

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`READXREF.jcl` — executes — `CBACT03C`

Observed: `READXREF.jcl` executes the observed program `CBACT03C`. E0020 E0021

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`CBACT03C` — reads — `AWS.M2.CARDDEMO.CARDXREF.VSAM.KSDS`

Observed: `CBACT03C` reads the observed cross-reference KSDS. E0020 E0021

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`TRANREPT.jcl` — executes — `CBTRN03C`

Observed: `TRANREPT.jcl` executes `CBTRN03C` for a processed-transaction report. E0020 E0021

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

Account Extractions module — optional extension for — CardDemo application

Observed: The Account Extractions module is explicitly described as an optional CardDemo extension. E0022

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`COACCT01` — associated with transaction — `CDRA`

Observed: CICS configuration associates `COACCT01` with transaction `CDRA`. E0022

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`CODATE01` — associated with transaction — `CDRD`

Observed: CICS configuration associates `CODATE01` with transaction `CDRD`. E0022

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`COACCT01` — reads data from — `ACCTDAT`

Observed: `COACCT01` reads the corresponding `ACCTDAT` VSAM record. E0022

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`CBSTM03A.CBL` — communicates with — `CBSTM03B.CBL`

Observed: The programs communicate through `WS-M03B-AREA`, passing an operation and file name and receiving `LK-M03B-RC`. E0024

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`CBSTM03B.CBL` — performs file operations for — `TRNXFILE`

Observed: `CBSTM03B.CBL` opens, reads, and closes `TRNXFILE`. E0024

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`CORPT00C` — submits batch jobs through — extra partition TDQ

Observed: `CORPT00C` writes JCL records to an extra-partition TDQ. E0025

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`CORPT00C` — relies on — `TRANREPT`

Inference: The evidence indicates reliance on the unavailable `TRANREPT` procedure for report generation. E0025

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

Potential hazards include deployment or binding after unsuccessful builds, ineffective JCL conditions, hard-coded qualifiers, unverified symbols, RACF changes, destructive catalog recreation, incomplete CICS response handling, duplicate transaction IDs, documentation overstatement, exposed example credentials, and uncertain batch sequencing. E0026 E0027 E0030 E0033 E0034

Unknowns

Complete business logic, source and repository inventories, data definitions, sign-on implementation, CICS and Control-M configuration, optional-module boundaries, security enforcement, restart and recovery behavior, authoritative batch procedures, production suitability, and successful execution are not established by the supplied evidence. E0026 E0027 E0028 E0031 E0032 E0033 E0034

Unresolved relationship

`samples/jcl/BATCMP.jcl` — invokes — `BUILDBAT`

The JCL endpoint invokes the batch COBOL compilation procedure with member and qualifier parameters. E0027

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`samples/jcl/CICCMP.jcl` — invokes — `BUILDONL`

The JCL endpoint invokes the online CICS compilation procedure and includes a `NEWCOPY` operation; its condition remains disputed. E0026 E0027

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`samples/jcl/CICDBCMP.jcl` — invokes — `BLDCIDB2`

The JCL endpoint invokes the DB2-oriented build with member, qualifier, SSID, and plan parameters. E0027

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`samples/jcl/BMSCMP.jcl` — invokes — `BUILDBMS`

The JCL endpoint invokes BMS assembler and binder processing and then performs a map `NEWCOPY`. E0027

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`COSGN00C` — XCTLs to — `COADM01C`

Validated `ADMIN` credentials route through CICS `XCTL` and pass `CARDDEMO-COMMAREA`. E0034

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`COSGN00C` — XCTLs to — `COMEN01C`

Validated non-`ADMIN` credentials route through CICS `XCTL` and pass `CARDDEMO-COMMAREA`. E0034

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`COMEN01C.cbl` — transfers control to — `COSGN00C`

The supplied evidence identifies `COSGN00C` as the sign-on target on initial entry or return paths, although detailed sign-on behavior is incomplete. E0028 E0030

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`COBIL00C.cbl` — references — `TRANSACT`

The payment program references transaction data storage whose physical organization is unknown. E0029

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`COBIL00C.cbl` — references — `ACCTDAT`

The payment program uses `ACCTDAT` for account lookup and balance validation. E0029

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`COADM01C` — returns control to — `COSGN00C`

The administrative menu returns control after PF3 or when required context is absent. E0030

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`DAILY-TransactionBackup` — starts with — `CLOSEFIL`

The documented daily backup flow starts with `CLOSEFIL`. E0031

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`CLOSEFIL` — triggers — `CBPAUP0J`

The job-chain evidence explicitly states this trigger. E0031

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`WAITSTEP` — triggers — `OPENFIL`

The monthly flow states that `WAITSTEP` triggers `OPENFIL`, which subsequently triggers `CLOSEFIL`. E0031

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`MNTTRDB2` — triggers — `TRANEXTR`

The weekly transaction-type refresh states this trigger. E0031

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`INTCALC` — triggers — `COMBTRAN`

The monthly interest flow states this trigger. E0031

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

Invalid dates, suppressed diagnostic messages, undocumented layouts and contracts, FTP outages, critical file errors, absent recovery controls, temporal or referential mismatches, uncertain balance handling, and unclear discount semantics are evidence-based risks or gaps, not demonstrated incidents. E0035 E0036 E0037 E0039 E0040 E0041 E0042 E0043

Unknowns

Complete business logic, data schemas, actors, security, deployment, calling contexts, operational ownership, transaction execution, balance updates, interest and discount calculations, recovery, restart behavior, and many field meanings remain unestablished. E0035 E0036 E0037 E0038 E0039 E0040 E0041 E0042 E0043

Unresolved relationship

CSUTLDPY.cpy — calls — CSUTLDTC.cbl

`EDIT-DATE-LE` calls `CSUTLDT​C` for CCYYMMDD validation using `YYYYMMDD`; the reusable paragraph and program are both identified. E0035

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CSUTLDTC.cbl — invokes — CEEDAYS API

`CSUTLDTC.cbl` calls CEEDAYS for date validation and conversion. E0035

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

dailytran.txt — links — merchant names

Transaction records contain card numbers, merchant names, amounts, and timestamps. E0036

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CARDDEMO — is organized within — CARDDEMO

The application and CICS group share the name CARDDEMO. E0038

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CC00 — invokes — COSGN00C

CC00 is the login transaction and invokes COSGN00C. E0038

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CAVW — invokes — COACTVWC

CAVW is the account-viewing transaction and invokes COACTVWC. E0038

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CAUP — invokes — COACTUPC

CAUP is the account-update transaction and invokes COACTUPC. E0038

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CLI — invokes — COCRDLIC

CLI is the card-listing transaction and invokes COCRDLIC. E0038

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CDV1 — invokes — COCRDSEC

CDV1 is the card-search transaction and invokes COCRDSEC. E0038

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`remote_compile.sh` — communicates with — `mainframe environment hosted by Ensono`

The script uses an FTP tunnel and uploads generated JCL to the remote mainframe. E0039

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`compile_batch.jcl.template` — defines steps for — `COBOL programs`

The template defines IGYCRCTL compilation and HEWL link-edit steps. E0039

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CBCUS01C.cbl — reads — VSAM indexed file

The batch program reads customer data sequentially from a VSAM indexed file. E0040

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CUSTFILE.jcl — manages — AWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDS

The JCL deletes, defines, and loads the named KSDS. E0040

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CUSTFILE.jcl — copies data to — VSAM dataset

IDCAMS REPRO copies flat-file data into a VSAM dataset. E0040

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COBDATFT — references — COINTYPE

COBDATFT uses COINTYPE to select the input-format branch. E0041

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COBDATFT — references — COINPDT

COBDATFT validates and rearranges COINPDT. E0041

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COBDATFT — references — COOUTYPE

COBDATFT checks COOUTYPE compatibility. E0041

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COBDATFT — sets — COERMSG

COBDATFT sets COERMSG to `INVALID INPUT` for identified failures. E0041

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

MVSWAIT — executes — ASMWAIT

MVSWAIT passes BINLBL as the ASMWAIT control block. E0041

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

TRANREPT.prc — invokes — REPROC.prc

TRANREPT.prc invokes REPROC.prc during reporting, including unloading. E0042

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

REPROC.prc — executes — IDCAMS

REPROC.prc uses IDCAMS for VSAM operations. E0042

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

TRANREPT.prc — executes — SORT

TRANREPT.prc uses SORT to filter and order transactions. E0042

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

TRANREPT.prc — executes — CBTRN03C

TRANREPT.prc uses CBTRN03C to produce formatted reports. E0042

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CODATECN-REC — contains — CODATECN-INP-DATE

CODATECN-REC contains the input-date structure used for conversion. E0043

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

Invalid key presses produce specific user guidance, but detection, display, and subsequent handling are unknown. Abnormal termination is an identified operational hazard with structured diagnostic storage. E0044

Inference: Invalid `ASMWAIT` values could cause unintended wait durations or coordination effects, and the fixed 38-byte error field could constrain retained error information; validation, truncation, and supplementary storage are unknown. E0045

Unknown: Record-reproduction hazards, runtime failure modes, recovery requirements, and failure behavior are not established. E0046 E0047

Unknowns

The evidence does not establish persistence, monitoring, deployment, performance, data semantics, external integrations, security, runtime specifics, parameter units, error recovery, message display, invalid-key detection, abnormal-termination consumption, or how values enter the date-processing layout. E0044 E0045 E0046

The business domain or application context, semantic meaning of “IMS,” and specific entities, tables, services, modules, interfaces, or data exchanges represented by the diagrams remain unknown without visual inspection or parsing. E0047

Unresolved relationship

ASMWAIT.mac — defines — ASMWAIT

`ASMWAIT.mac` and `ASMWAIT` are both observed: the former defines the latter. E0045

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COCDATFT.mac — defines — COCDATFT

`COCDATFT.mac` and the `COCDATFT` DSECT are both observed: the former defines the latter. E0045

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

REPROCT.ctl — defines — REPRO command

`REPROCT.ctl` and the `REPRO` command are both observed: the control file contains or defines the command. E0046

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

REPRO command — reads from — FILEIN

The `REPRO` command and `FILEIN` are both observed, with `INFILE(FILEIN)` directing input reads from `FILEIN`. E0046

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

REPRO command — writes to — FILEOUT

The `REPRO` command and `FILEOUT` are both observed, with `OUTFILE(FILEOUT)` directing output writes to `FILEOUT`. E0046

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CARDDEMO-DataModel.drawio — contains — ER Diagram

`CARDDEMO-DataModel.drawio` and the “ER Diagram” page are both observed, and the source file explicitly contains that page. E0047

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CARDDEMO-DataModel.drawio — contains — IMS

`CARDDEMO-DataModel.drawio` and the “IMS” page are both observed, and the source file explicitly contains that page. E0047

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

Potential hazards include destructive replacement, partial updates, late IMS persistence, malformed input, unstable paging, concurrency conflicts, inconsistent indexes, file-organization and width mismatches, sequence truncation, exposed credentials, unprotected sensitive fields, duplicate definitions, missing recreation, abends, and uncertain atomicity. These are reported or inferred risks, not established incidents. E0001 E0006 E0014 E0018 E0019 E0021 E0025

Unknowns

Complete schemas and mappings, actors, security controls, business rules, lifecycle transitions, runtime execution, configuration, sequencing, keys, transformations, scheduling, monitoring, recovery, retention, transaction guarantees, external contracts, version alignment, and the status of `UNUSED-DATA` remain unresolved. Conflicts about PF7 behavior, map names, generated copybooks, deployed artifacts, and source coverage are retained rather than resolved. E0009 E0011 E0014 E0017 E0020 E0021 E0023 E0025

Unresolved relationship

Transaction Type Management module — is an optional extension for — CardDemo application

Both endpoints and the optional-extension relationship are explicitly described. E0010

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

Transaction Type Management module — maintains data in — DB2

The module is described as maintaining administrative transaction-type data in DB2. E0010

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

Transaction Type Management module — maintains data in — VSAM

The module is described as maintaining transaction-type data in VSAM for processing. E0010

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CTTU — maps to — COTRTUPC

The mapping evidence identifies CTTU and `COTRTUPC`. E0011

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CTLI — maps to — COTRTLIC

The mapping evidence identifies CTLI and `COTRTLIC`. E0011

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

TRANSACTION_TYPE_CATEGORY — references — TRANSACTION_TYPE

`TRC_TYPE_CODE` references `TRANSACTION_TYPE.TR_TYPE` with `ON DELETE RESTRICT`. E0011

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CardDemo — manages — USRSEC

CardDemo is identified as managing `USRSEC` user records. E0016

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`COUSR01C.cbl` — writes — `USRSEC`

The add-user flow writes a new `USRSEC` record. E0017

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`COUSR02C.cbl` — rewrites — `USRSEC`

The update flow reads and rewrites `USRSEC`. E0017

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`COUSR03C.cbl` — deletes from — `USRSEC`

The delete flow reads and deletes the selected `USRSEC` record. E0017

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CARDDEMO — deployed within — a CICS region

CICS resource definitions place CARDDEMO in a stated CICS-region context; deployment remains unverified. E0018

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`CBCUS01C` — reads — `AWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDS`

The program and customer KSDS are explicitly connected by the supplied JCL and source evidence. E0020 E0021

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`CBACT03C` — reads — `AWS.M2.CARDDEMO.CARDXREF.VSAM.KSDS`

The program reads the named cross-reference KSDS. E0020 E0021

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`COACCT01` — reads data from — `ACCTDAT`

The account-extraction program reads the corresponding VSAM record. E0022

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`CBSTM03B.CBL` — performs file operations for — `TRNXFILE`

The program opens, reads, and closes `TRNXFILE`. E0024

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`CORPT00C` — submits batch jobs through — extra partition TDQ

The report program writes JCL records to the TDQ. E0025

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`COACTUPC` — handles — Account Update transaction (CAUP)

The evidence explicitly identifies this component as handling CAUP. E0001 E0002

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`COACTVWC` — handles — Account View transaction (CAVW)

The evidence identifies this component as retrieving and displaying account and customer details. E0001 E0002

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`COPAUS1C.cbl` — links to — `COPAUS2C.cbl`

The first source file is stated to link to the second. E0004

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`PAUTSUM0` — has child — `PAUTDTL1`

The IMS evidence identifies `PAUTDTL1` as the child segment. E0004

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`CBPAUP0J` — executes — `CBPAUP0C`

The JCL invokes the expired-authorization deletion program. E0005

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`UNLDPADB.JCL` — invokes — `PAUDBUNL`

The unload job invokes the named program. E0006

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`COTRN02C.cbl` — adds a new transaction to — `TRANSACT` file

The evidence states that validated input is written as a new transaction. E0007

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`app/cbl/CBTRN02C.cbl` — writes rejects to — `DALYREJS`

Failed validations are reported as written to the reject file. E0008

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

Potential risks include ineffective JCL conditions, unsuccessful builds followed by binding or deployment, hard-coded qualifiers, unverified symbols, RACF changes, destructive catalog recreation, incomplete response handling, duplicate transaction IDs, exposed credentials, FTP outages, critical VSAM errors, uncertain batch sequencing, temporal mismatches, and undocumented recovery. These are risks or gaps, not demonstrated incidents. E0026 E0027 E0037 E0039 E0040 E0041 E0042 E0045

Unknowns

Complete business logic, source inventory, data semantics, actors, ownership, security enforcement, deployment topology, CICS and Control-M configuration, optional-module boundaries, authoritative batch ordering, balance updates, interest and discount calculations, transaction execution, restart and recovery, and production suitability are not established. The diagrams’ entities and the meaning of “IMS” are also unknown because their visual content was not parsed. E0026 E0035 E0036 E0038 E0039 E0042 E0044 E0046 E0047

Unresolved relationship

samples/jcl/BATCMP.jcl — invokes — BUILDBAT

The JCL invokes batch COBOL compilation with member and qualifier parameters; both endpoints are observed. E0027

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

samples/jcl/CICCMP.jcl — invokes — BUILDONL

The JCL invokes online CICS compilation and includes a disputed `NEWCOPY` condition; both endpoints are observed. E0026 E0027

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

samples/jcl/CICDBCMP.jcl — invokes — BLDCIDB2

The JCL invokes the DB2-oriented build with member, qualifier, SSID, and plan parameters. E0027

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

samples/jcl/BMSCMP.jcl — invokes — BUILDBMS

The JCL invokes BMS assembler and binder processing and performs map `NEWCOPY`. E0027

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COSGN00C — XCTLs to — COADM01C

Validated `ADMIN` credentials route through CICS `XCTL` and pass `CARDDEMO-COMMAREA`. E0034

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COSGN00C — XCTLs to — COMEN01C

Validated non-`ADMIN` credentials route through CICS `XCTL` and pass `CARDDEMO-COMMAREA`. E0034

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CC00 — invokes — COSGN00C

`CC00` is identified as the login transaction invoking `COSGN00C`. E0038

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COBIL00C.cbl — references — ACCTDAT

The payment program uses `ACCTDAT` for account lookup and balance validation. E0029

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

WAITSTEP — triggers — OPENFIL

The monthly flow states that `WAITSTEP` triggers `OPENFIL`, which subsequently triggers `CLOSEFIL`. E0031

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CSUTLDTC.cbl — invokes — CEEDAYS API

The date-validation program calls CEEDAYS for conversion and validation. E0035

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

MVSWAIT — executes — ASMWAIT

`MVSWAIT` passes `BINLBL` as the `ASMWAIT` control block. E0041

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

REPRO command — reads from — FILEIN

`INFILE(FILEIN)` directs the `REPRO` operation to read from `FILEIN`. E0046

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

REPRO command — writes to — FILEOUT

`OUTFILE(FILEOUT)` directs the `REPRO` operation to write to `FILEOUT`. E0046

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

TRANREPT.prc — invokes — REPROC.prc

The reporting procedure invokes `REPROC.prc` for unloading and related VSAM operations. E0042

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CARDDEMO-DataModel.drawio — contains — ER Diagram

The draw.io file explicitly contains a page named “ER Diagram”; its encoded visual content was not parsed. E0047

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CARDDEMO-DataModel.drawio — contains — IMS

The draw.io file explicitly contains a page named “IMS”; its architectural meaning is unknown. E0047

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Hazards

Potential hazards include destructive replacement or recreation, partial updates, ineffective conditions, malformed input, unstable paging, duplicate IDs, inconsistent indexes, exposed credentials, FTP failure, critical VSAM errors, abends, and uncertain atomicity. No incident is established. E0001 E0006 E0014 E0018 E0019 E0026 E0037 E0040 E0042

Unknowns

Complete schemas, mappings, actors, ownership, security controls, deployment topology, sequencing, business rules, balances, calculations, configuration, restart and recovery, retention, external contracts, version alignment, and production suitability are unknown. Conflicts over PF7, maps, copybooks, deployed artifacts, source coverage, and diagram meaning remain unresolved. E0009 E0011 E0014 E0017 E0020 E0021 E0025 E0036 E0039 E0047

Unresolved relationship

Transaction Type Management module — is an optional extension for — CardDemo application

Both endpoints and the optional-extension relationship are explicit. E0010

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

Transaction Type Management module — maintains data in — DB2

Both endpoints and the maintenance relationship are explicit. E0010

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

Transaction Type Management module — maintains data in — VSAM

Both endpoints and the maintenance relationship are explicit. E0010

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CTTU — maps to — COTRTUPC

Both names and the mapping are identified. E0011

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CTLI — maps to — COTRTLIC

Both names and the mapping are identified. E0011

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

TRANSACTION_TYPE_CATEGORY — references — TRANSACTION_TYPE

The foreign-key reference and `ON DELETE RESTRICT` are stated. E0011

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CardDemo — manages — USRSEC

Both endpoints and management are identified. E0016

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`COUSR01C.cbl` — writes — `USRSEC`

The add-user flow writes a record. E0017

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`COUSR02C.cbl` — rewrites — `USRSEC`

The update flow reads and rewrites a record. E0017

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`COUSR03C.cbl` — deletes from — `USRSEC`

The delete flow reads and deletes a record. E0017

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CARDDEMO — deployed within — a CICS region

The resource context is stated; deployment is unverified. E0018

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`CBCUS01C` — reads — `AWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDS`

The program and dataset are connected by supplied evidence. E0020 E0021

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`CBACT03C` — reads — `AWS.M2.CARDDEMO.CARDXREF.VSAM.KSDS`

The named read relationship is explicit. E0020 E0021

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`COACCT01` — reads data from — `ACCTDAT`

The extraction program reads the record. E0022

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`CBSTM03B.CBL` — performs file operations for — `TRNXFILE`

Open, read, and close operations are stated. E0024

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`CORPT00C` — submits batch jobs through — extra partition TDQ

The program writes JCL records to the TDQ. E0025

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`COACTUPC` — handles — Account Update transaction (CAUP)

The component and transaction are explicitly associated. E0001 E0002

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`COACTVWC` — handles — Account View transaction (CAVW)

The component retrieves and displays account and customer details. E0001 E0002

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`COPAUS1C.cbl` — links to — `COPAUS2C.cbl`

The source states this link. E0004

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`PAUTSUM0` — has child — `PAUTDTL1`

The IMS evidence identifies the child segment. E0004

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`CBPAUP0J` — executes — `CBPAUP0C`

The JCL invokes the deletion program. E0005

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`UNLDPADB.JCL` — invokes — `PAUDBUNL`

The unload job invokes the program. E0006

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`COTRN02C.cbl` — adds a new transaction to — `TRANSACT` file

Validated input is stated to be written. E0007

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`app/cbl/CBTRN02C.cbl` — writes rejects to — `DALYREJS`

Failed validations are reported as written there. E0008

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`samples/jcl/BATCMP.jcl` — invokes — BUILDBAT

The JCL invokes batch compilation. E0027

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`samples/jcl/CICCMP.jcl` — invokes — BUILDONL

The JCL invokes online compilation; `NEWCOPY` is disputed. E0026 E0027

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`samples/jcl/CICDBCMP.jcl` — invokes — BLDCIDB2

The JCL invokes DB2-oriented building. E0027

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

`samples/jcl/BMSCMP.jcl` — invokes — BUILDBMS

The JCL invokes BMS processing and `NEWCOPY`. E0027

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COSGN00C — XCTLs to — COADM01C

Validated `ADMIN` credentials route through `XCTL`. E0034

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COSGN00C — XCTLs to — COMEN01C

Validated non-`ADMIN` credentials route through `XCTL`. E0034

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CC00 — invokes — COSGN00C

`CC00` is identified as the login transaction. E0038

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

COBIL00C.cbl — references — ACCTDAT

The payment program uses it for lookup and balance validation. E0029

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

WAITSTEP — triggers — OPENFIL

The monthly flow states this trigger. E0031

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CSUTLDTC.cbl — invokes — CEEDAYS API

The date program calls CEEDAYS. E0035

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

MVSWAIT — executes — ASMWAIT

`BINLBL` is passed as the control block. E0041

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

REPRO command — reads from — FILEIN

`INFILE(FILEIN)` directs the read. E0046

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

REPRO command — writes to — FILEOUT

`OUTFILE(FILEOUT)` directs the write. E0046

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

TRANREPT.prc — invokes — REPROC.prc

The reporting procedure invokes `REPROC.prc`. E0042

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CARDDEMO-DataModel.drawio — contains — ER Diagram

The file contains a page with that name; visuals were not parsed. E0047

Exact, unambiguous named endpoints were not supplied together; no edge was created.

Unresolved relationship

CARDDEMO-DataModel.drawio — contains — IMS

The file contains a page with that name; meaning is unknown. E0047

Exact, unambiguous named endpoints were not supplied together; no edge was created.