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

Actors and Value Streams

Scope and system position

The supplied evidence describes a partially reconstructed CardDemo mainframe application using online transactions, batch processing, files, databases, messaging, scheduling, and operational utilities. It establishes artifacts and intended behavior, not successful execution, complete topology, compiler semantics, sequencing, or production behavior. Evidence also conflicts about whether all artifacts execute together. E0001 E0010 E0017 E0020 E0021 E0002 E0003 E0005 E0006 E0018

Actors

Observed human and organizational actors include regular users, administrators, and operators. A UNIX-hosted Control-M scheduling environment is also identified. Ownership, role boundaries, permissions, and enforcement are unknown. E0026 E0028 E0035 E0036 E0044 E0047

The online sign-on flow distinguishes administrative credentials from other validated credentials and routes them to different destinations. Inference: this indicates an intended separation between administrative and non-administrative journeys, but it does not establish the responsible actor, authorization policy, or enforcement point. E0034 E0038

External and platform actors include CICS, DB2, IMS, MQ, VSAM, RACF, JES/TSO, SDSF, IDCAMS, UNIX, Control-M, FTP, a date-conversion service, and an Ensono-hosted mainframe. Their ownership, topology, availability, and integration status are unknown; interpretations concerning z/OS and AWS remain inferences. E0003 E0018 E0026 E0038 E0042

Value streams

Inferred value stream — authenticate and route: a user submits credentials through an online login transaction; validated administrative credentials route to an administrative flow, while other validated credentials route to a menu flow. The evidence does not establish session management, authorization enforcement, or successful runtime outcomes. E0034 E0038

Inferred value stream — maintain accounts and customers: online components support account update and account view journeys, including retrieval and display of account and customer details. Account data is also read for payment lookup and balance validation. The complete validation, calculation, persistence, and confirmation behavior is unknown. E0001 E0002 E0029

Inferred value stream — accept payments and post transactions: a payment journey includes lookup, balance validation, confirmation, and submission; validated transaction input is written to a transaction file, while failed validations are written to a rejection file. Whether posting is atomic, when balances change, and how rejected work is recovered are unknown. E0029 E0007 E0008 E0015 E0045

Inferred value stream — administer security records: user-management flows add, update, and delete security records. The application manages the security store, but credential protection, authorization enforcement, audit, and deletion policy are unknown. E0016 E0017 E0032 E0033 E0036

Inferred value stream — produce operational and business outputs: batch reporting, statements, interest, fees, posting, paging, and rejection handling are described. Reporting procedures can invoke subordinate procedures, and a reporting component can submit batch jobs through an extra-partition queue. Output definitions, schedules, ownership, and completeness are unknown. E0002 E0025 E0031 E0042

Inferred value stream — move and prepare data: VSAM loading, indexing, extraction, backup, unload, reload, migration, compilation, and file copy operations are present. Data layouts, encodings, keys, offsets, transformations, restoration behavior, and runtime compatibility remain unresolved. E0022 E0024 E0035 E0041 E0046 E0047

Cross-cutting uncertainty

No supplied evidence establishes a semantically complete actor model or end-to-end value-stream map. Sequencing, external contracts, deployment, monitoring, restart and recovery, retention, security boundaries, and production suitability remain unknown. E0009 E0011 E0014 E0020 E0021 E0025 E0039 E0040 E0045 E0047