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

Integration Catalogue

Scope and evidence status

This catalogue records integrations, interfaces, and dependencies explicitly described in the supplied evidence. It covers a partially reconstructed CardDemo mainframe using COBOL, CICS, BMS, VSAM, DB2, IMS, MQ, JCL, REXX, and utilities. The evidence establishes artifacts and intended relationships, but not semantic completeness, successful execution, complete topology, compiler behavior, sequencing, or production behavior. E0001 E0010 E0017 E0020 E0021

Inference: The strongest overall interpretation is a configured, partially reconstructed IBM mainframe architecture expressing intended integration patterns rather than a verified end-to-end runtime model. Execution, deployment, versions, encodings, timing, availability, and complete outcomes remain unresolved. E0023 E0037 E0038 E0041 E0045 E0046

Online transaction integrations

• CICS provides the principal online transaction context. CardDemo is described as deployed within a CICS region, although that deployment is unverified. CICS programs, BMS maps, commareas, and XCTL are identified as interface mechanisms. E0001 E0018 E0034

• The login transaction CC00 invokes COSGN00C. Validated ADMIN credentials are routed through XCTL to COADM01C, while validated non-ADMIN credentials are routed through XCTL to COMEN01C. The evidence does not establish the complete routing table or enforcement behavior. E0034 E0038

• COACTUPC handles the Account Update transaction, CAUP. COACTVWC handles the Account View transaction, CAVW, and retrieves and displays account and customer details. The evidence does not establish all associated maps, commarea layouts, or downstream calls. E0001 E0002

• The security integration includes CardDemo management of USRSEC. COUSR01C writes a user record, COUSR02C reads and rewrites a record, and COUSR03C reads and deletes a record. Authentication, authorization enforcement, auditing, and the relationship to RACF remain unresolved. E0016 E0017 E0032 E0036

Data-store integrations

• VSAM is used through named KSDS and related processing artifacts. CBCUS01C reads AWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDS, and CBACT03C reads AWS.M2.CARDDEMO.CARDXREF.VSAM.KSDS. Index structure, key definitions, deployment location, and consistency guarantees are not established. E0020 E0021

• COACCT01 reads account data from ACCTDAT. COBIL00C also references ACCTDAT for lookup and balance validation. The evidence does not establish whether these references identify the same physical or logical store, nor does it establish balance-update atomicity. E0022 E0029 E0039

• CBSTM03B.CBL performs open, read, and close operations for TRNXFILE. COTRN02C writes validated new transactions to the TRANSACT file, while app/cbl/CBTRN02C.cbl writes failed validations to DALYREJS. File formats, sharing rules, and reconciliation behavior remain unknown. E0007 E0008 E0024

• The Transaction Type Management module is explicitly described as an optional CardDemo extension that maintains data in both DB2 and VSAM. The evidence does not establish synchronization, authority between stores, or whether the extension is deployed. E0010

• IMS artifacts include COPAUS1C.cbl linking to COPAUS2C.cbl and PAUTSUM0 having child segment PAUTDTL1. An unload job, UNLDPADB.JCL, invokes PAUDBUNL, and CBPAUP0J invokes deletion program CBPAUP0C. IMS schema semantics, load ordering, and operational status are not established. E0004 E0005 E0006

Batch, scheduling, and utility integrations

• CORPT00C submits batch jobs through an extra-partition transient data queue by writing JCL records to the TDQ. The receiving reader, submission controls, security boundary, and completion handling are unknown. E0025 E0040

• Control-M is identified in a UNIX environment at MY-HOST. Batch flows include waits, reruns, backups, GDGs, indexing, reporting, and internal-reader submission. Ownership, monitoring, restart behavior, alerting, and completion guarantees are not established. E0026 E0028 E0031 E0044 E0045

• WAITSTEP triggers OPENFIL in a monthly flow. MVSWAIT executes ASMWAIT with BINLBL passed as a control block. These observations show named orchestration or wait relationships, but do not establish their full schedule or runtime sequencing. E0031 E0041

• BATCMP.jcl invokes BUILDBAT, CICCMP.jcl invokes BUILDONL, CICDBCMP.jcl invokes BLDCIDB2, and BMSCMP.jcl invokes BUILDBMS. BMS processing includes NEWCOPY; NEWCOPY for online compilation is disputed. E0026 E0027

• REPRO reads from FILEIN and writes to FILEOUT. TRANREPT.prc invokes REPROC.prc. These are explicit utility and reporting relationships, but input contracts, output semantics, and failure recovery are not established. E0042 E0046

External and platform dependencies

• Named dependencies include CICS, DB2, IMS, MQ, VSAM, RACF, JES/TSO, SDSF, IDCAMS, UNIX, Control-M, FTP, CEEDAYS, and an Ensono-hosted mainframe. Their ownership, availability, network topology, versions, and actual integration are unknown. z/OS and AWS interpretations are inferences rather than confirmed deployment facts. E0003 E0018 E0026 E0035 E0038 E0042

• CSUTLDTC.cbl invokes the CEEDAYS API for date processing. The evidence does not establish date conventions, error handling, or compatibility across environments. E0035

• MQ, FTP, sorting, reporting tools, and DB2 or IMS integrations are described as interfaces or optional capabilities, but queues, endpoints, transformations, keys, credentials, and runtime compatibility are unresolved. E0003 E0039 E0040 E0042 E0046

Integration risks and unknowns

• Potential integration hazards include partial updates, ineffective conditions, malformed input, duplicate identifiers, inconsistent indexes, exposed credentials, FTP failure, critical VSAM errors, abends, destructive replacement or recreation, and uncertain atomicity. No incident or confirmed defect is established by the evidence. E0006 E0014 E0018 E0019 E0026 E0037 E0040 E0042

• Unknown: Complete interface contracts, data transformations, key and index definitions, queue behavior, transaction boundaries, sequencing, deployment topology, ownership, permissions, restart and recovery, retention, version alignment, and production suitability are not established. Conflicts concerning maps, copybooks, deployed artifacts, PF7 behavior, source coverage, and diagram meaning remain unresolved. E0009 E0011 E0014 E0017 E0020 E0021 E0025 E0036 E0039 E0047