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

Deployment and Operations

Scope and operational posture

The supplied evidence describes a partially reconstructed CardDemo mainframe using COBOL, CICS, BMS, VSAM, DB2, IMS, MQ, JCL, REXX, and utilities. It establishes artifacts and intended behavior, but not successful execution, complete topology, compiler semantics, sequencing, or production behavior. Inference: the system should be treated as an expressed operational design rather than a verified end-to-end service. E0001 E0010 E0017 E0020 E0021 E0023 E0045

Deployment context

CARDDEMO is identified as deployed within a CICS region, although that deployment is unverified. The surrounding dependencies include DB2, IMS, MQ, VSAM, RACF, JES/TSO, SDSF, IDCAMS, UNIX, Control-M, FTP, CEEDAYS, and an Ensono-hosted mainframe. An administrative UNIX scheduler environment at `MY-HOST` is also identified. E0018 E0026 E0035 E0038 E0042 E0044

Inference: the evidence most strongly indicates a mainframe-centered architecture with both online CICS processing and external or host-based batch operations. The z/OS and AWS interpretations remain inferences, and the topology, ownership, availability, and integration of the listed dependencies are not established. E0018 E0023 E0026 E0038 E0042

Online deployment and routing

The online surface includes CICS transactions, BMS maps, commareas, VSAM access, and program control through `XCTL`. `CC00` is identified as the login transaction. Validated `ADMIN` credentials route from `COSGN00C` to `COADM01C`; other validated credentials route to `COMEN01C`. Account update and account view are associated with `COACTUPC` and `COACTVWC`, respectively. E0034 E0038 E0001 E0002

Security-related artifacts include `USRSEC`, RACF, and `DUSRSECJ`. The evidence also contains literal or example credentials and sensitive-looking fields. Encryption, masking, authorization enforcement, audit controls, queue permissions, and network boundaries are not established. E0001 E0009 E0016 E0032 E0033 E0036

Build and promotion operations

JCL members identify separate build paths: `BATCMP.jcl` invokes `BUILDBAT`, `CICCMP.jcl` invokes `BUILDONL`, `CICDBCMP.jcl` invokes `BLDCIDB2`, and `BMSCMP.jcl` invokes `BUILDBMS`. BMS processing and `NEWCOPY` are stated for the BMS job, while `NEWCOPY` is disputed for the online compilation job. E0026 E0027

The evidence also describes compilation, migration, backups, GDGs, indexing, reporting, internal-reader submission, and `REPRO`. `REPRO` reads from `FILEIN` and writes to `FILEOUT`; `TRANREPT.prc` invokes `REPROC.prc`. These relationships document intended operational steps, not confirmed successful promotion or execution. E0025 E0039 E0042 E0046

Inference: build and deployment appear to be composed of multiple job-specific procedures rather than one demonstrated release pipeline. Version alignment, generated artifacts, copybook and map compatibility, sequencing, and the identity of deployed artifacts remain unresolved. E0017 E0020 E0021 E0026 E0027

Batch scheduling and processing

The operational evidence identifies a Control-M scheduler environment on UNIX, waits, reruns, batch posting, reporting, migration, statement and interest processing, and internal-reader job submission. The monthly flow states that `WAITSTEP` triggers `OPENFIL`; `CORPT00C` writes JCL records to an extra-partition TDQ. E0026 E0028 E0025 E0031

Batch and file-processing relationships include `CBPAUP0J` executing `CBPAUP0C`, `UNLDPADB.JCL` invoking `PAUDBUNL`, and `CBSTM03B.CBL` opening, reading, and closing `TRNXFILE`. `COTRN02C.cbl` writes validated transactions to `TRANSACT`, while failed validations are reported as written to `DALYREJS`. E0005 E0006 E0007 E0008 E0024

Inference: scheduling and batch execution are intended to coordinate online-adjacent data processing, reporting, and maintenance, but the complete schedule, dependency order, trigger semantics, and rerun behavior are not established. E0025 E0028 E0031 E0039

Data and protection operations

Operational data includes accounts, customers, cards, users, transactions, authorization and fraud records, classifications, cross-references, reports, statements, and imports or exports. Programs are connected to VSAM datasets including customer data and card cross-reference data; other evidence identifies DB2 and IMS artifacts and optional DB2, IMS, and MQ integration. E0004 E0010 E0020 E0021 E0022 E0039

Backup, GDG, indexing, unload, reload, and `REPRO` activities are described. The evidence also records unresolved layout, encoding, timestamp, index-offset, naming, and six-byte unload discrepancies. Destructive replacement or recreation, inconsistent indexes, duplicate identifiers, and partial updates are potential hazards; no incident is established. E0006 E0014 E0037 E0045 E0046

Failure handling and recovery

Observed operational states include validation, confirmation, acceptance, rejection, approval, decline, end-of-file, concurrent update, backup, error, abend, deployment, and generation increments. Operations mention logging, rollback, SQL handling, critical VSAM errors, waits, and reruns. E0015 E0017 E0018 E0031 E0041 E0045

Monitoring, alerting, restart points, disaster recovery, operational ownership, atomicity, completion guarantees, and recovery sequencing are unknown. Two-phase commit is disputed, and complete return-code semantics—including the interpretation of `COND=(4,LT)` under ordinary JCL interpretation—remain unresolved. E0013 E0015 E0028 E0039 E0041 E0044

Operational unknowns

Unknown: Complete deployment topology, environment boundaries, ownership, permissions, runtime availability, production suitability, configuration, version alignment, external contracts, retention, restart and recovery procedures, and end-to-end execution outcomes are not established by the supplied evidence. Conflicts concerning PF7 behavior, maps, copybooks, deployed artifacts, source coverage, and diagram meaning also remain unresolved. E0009 E0011 E0014 E0017 E0020 E0021 E0025 E0036 E0039 E0047