Modernization assessment - CARDDEMO

Prepared 19 November 2026 · Selected: job POSTTRAN · 23 reviewed summaries

A sample assessment of AWS CardDemo, an open-source mainframe credit card application (Apache License 2.0, Copyright Amazon.com, Inc. or its affiliates), at commit 59cc6c2 of https://github.com/aws-samples/aws-mainframe-modernization-carddemo. No client code is included.

Executive summary

1
batch jobs
0
transactions / CICS flows
1
programs in scope
697
lines of source
6
datasets
0
findings to resolve

This assessment covers 1 batch job(s) and 0 online transaction(s) or CICS flow(s), 1 application program(s), and 697 lines of source. Approach: 1 refactor (suggested, to confirm).

What they do

Inventory

What the selected jobs and transactions reach: 1 COBOL program(s) and 0 assembler module(s), 5 copybook(s), 1 job(s), 0 PROC(s), 0 CICS transaction(s) or flow(s). Everything loaded holds 44 COBOL program(s), 62 copybook(s), 46 job(s), and 25 CICS transaction(s).

Lines of source by type (excluding comments and blanks)
COBOL: 619COBOL619COPYBOOK: 56COPYBOOK56JOB: 22JOB22
TypeCodeComment
COBOL61959
COPYBOOK5630
JOB2223
COBOL programs by kind
batch: 1batch1

No Db2, IMS, or MQ use.

Largest programs (lines of code)
CBTRN02C: 619CBTRN02C619

Most complex programs

Decision points: IF, WHEN, and UNTIL conditions - roughly the number of paths to test. Depth: the longest chain of PERFORMs from the first paragraph.

ProgramDecision pointsIFEVALUATELoopsPERFORM depthParagraphsGO TO
CBTRN02C4948014260

Jobs and transactions

What each job or transaction reaches - its programs, copybooks, screens, and data - and how much source that is. Shared programs and copybooks count in every scope that uses them.

Lines of source in scope
POSTTRAN: 697POSTTRAN697
NameKindprogramscopybooksscreens (mapsets)datasetsDb2 tablesIMS segmentsLinesApproach
POSTTRANjob156697Refactor suggested

Modernization roadmap

ApproachMeaningCount
RehostMove as is to a mainframe-compatible runtime first; change the code later.0
RefactorRewrite the logic on the target platform (services, SQL, a reporting or ETL tool).1
Expose as APIKeep the business logic, put it behind a service interface, and replace the 3270 screen.0
RetireNot needed on the target platform, or no longer used.0

1 of 1 approach(es) are suggestions from the facts below, to confirm with you before planning.

Refactor (1)

NameWhy
POSTTRAN suggested1 program(s), 697 lines: small enough to rewrite as a batch service, query, or report on the target platform.

Job and transaction details

Job POSTTRAN

Refactor suggested - 1 program(s), 697 lines: small enough to rewrite as a batch service, query, or report on the target platform.

1
jobs
1
steps
1
programs
1
system programs
5
copybooks
6
datasets
12
record layouts
697
lines of source
InputsStepsOutputsupdateupdateupdateupdateAWS.M2.CARDDEMO.CARDXREF.VSAM.KSDSAWS.M2.CARDDEMO.CARDXREF.VSAM.KSDSAWS.M2.CARDDEMO.DALYTRAN.PSAWS.M2.CARDDEMO.DALYTRAN.PSSTEP15: CBTRN02CSTEP15: CBTRN02CAWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDSAWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDSAWS.M2.CARDDEMO.DALYREJSAWS.M2.CARDDEMO.DALYREJSAWS.M2.CARDDEMO.TCATBALF.VSAM.KSDSAWS.M2.CARDDEMO.TCATBALF.VSAM.KSDSAWS.M2.CARDDEMO.TRANSACT.VSAM.KSDSAWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS

What it does

POSTTRAN is the daily posting run. It takes the day's card transactions, rejects the ones that fail basic checks (unknown card, missing account, over the credit limit, account expired), and posts the rest: each is added to the transaction master file, and its amount is added to the account's balance and to the account's running balance for that transaction category. Rejected transactions go to a new rejects file with the reason, for someone to follow up.

Step by step
  1. Post the daily transactions (STEP15, CBTRN02C). Reads the daily transaction file in sequence. For each transaction it looks up the card in the cross-reference to find the account, reads the account, and checks the credit limit and expiration date. Valid transactions update the transaction category balance (creating it for a first transaction in a category), the account's current balance and current-cycle credit or debit total, and are written to the transaction master with the posting time. Invalid ones are written to the rejects file with a reason code (100 unknown card, 101 account not found, 102 over limit, 103 after account expiration). The step ends with return code 4 if anything was rejected.
What it needs
  • The day's transactions in AWS.M2.CARDDEMO.DALYTRAN.PS, delivered by whatever captures card activity upstream (not in the source provided).
  • The card cross-reference (CARDXREF.VSAM.KSDS), the account master (ACCTDATA.VSAM.KSDS), and the category balances (TCATBALF.VSAM.KSDS).
  • The transaction master (TRANSACT.VSAM.KSDS) in a state the program can open for output - it's opened OUTPUT although the JCL allocates the existing file (DISP=SHR), which for a VSAM file works only if it's empty or defined as reusable.
What it produces
  • New records on the transaction master - read later by the transaction report (TRANREPT), the backup and combine jobs, and the statements (CREASTMT).
  • Updated account balances and cycle totals - used by the interest run (INTCALC), the statements, and the online account screens.
  • Updated category balances - the basis of the interest calculation (INTCALC).
  • AWS.M2.CARDDEMO.DALYREJS(+1), a new generation of rejected transactions with reasons, and return code 4 when there are any.
Notes for modernization
  • Posting rules to confirm with the business: the credit-limit check uses the current cycle's credits minus debits plus the new amount, not the account balance; and when a transaction is both over limit and past expiration, only the expiration reason is recorded.
  • Partial updates on failure: an account update that fails is silently ignored after the category balance has been updated and while the transaction is still written; a failure part-way through the run leaves some transactions posted and others not, with no restart point. A modern version would post each transaction atomically (one database transaction) or make the run restartable.
  • Opening the master for output depends on how the VSAM file is defined; confirm the actual run procedure (the scheduler definitions in the source aren't analyzed yet).
  • A natural first candidate for a service: "validate and post a card transaction" is a clear unit of business logic that online and batch could share.
Step-by-step walkthrough from the source
Job POSTTRAN

Step 1 - STEP15: runs CBTRN02C

  • Comment: Process and load daily transaction file and create transaction / category balance and update transaction master vsam
  • What CBTRN02C does: CBTRN02C posts the day's card transactions. It checks each one against the card cross-reference and the account (card known, account found, within the credit limit, account not expired), and for the valid ones adds the amount to the account's balance and cycle totals and to the account's balance for that transaction type and category, and writes the transaction to the transaction master file. Transactions that fail a check are written to a rejects file with the reason.
  • Reads: AWS.M2.CARDDEMO.CARDXREF.VSAM.KSDS (DD XREFFILE), AWS.M2.CARDDEMO.DALYTRAN.PS (DD DALYTRAN)
  • Updates: AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS (DD ACCTFILE), AWS.M2.CARDDEMO.TCATBALF.VSAM.KSDS (DD TCATBALF)
  • Writes: AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS (DD TRANFILE)
  • Creates: AWS.M2.CARDDEMO.DALYREJS (DD DALYREJS)

Inputs from outside the job: AWS.M2.CARDDEMO.CARDXREF.VSAM.KSDS, AWS.M2.CARDDEMO.DALYTRAN.PS Outputs it leaves behind: AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS, AWS.M2.CARDDEMO.DALYREJS, AWS.M2.CARDDEMO.TCATBALF.VSAM.KSDS, AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS

Program CBTRN02C

CBTRN02C posts the day's card transactions. It checks each one against the card cross-reference and the account (card known, account found, within the credit limit, account not expired), and for the valid ones adds the amount to the account's balance and cycle totals and to the account's balance for that transaction type and category, and writes the transaction to the transaction master file. Transactions that fail a check are written to a rejects file with the reason.

Inputs
  • Daily transactions (DD DALYTRAN, AWS.M2.CARDDEMO.DALYTRAN.PS) - read in sequence; layout DALYTRAN-RECORD (CVTRA06Y): ID, type and category codes, source, description, amount, merchant, card number, and origination timestamp.
  • Card cross-reference (DD XREFFILE, VSAM keyed by card number) - gives the account ID for a card (CVACT03Y).
  • Account master (DD ACCTFILE, VSAM keyed by account ID) - credit limit, expiration date, current balance, and current-cycle credit and debit totals (CVACT01Y).
  • Transaction category balances (DD TCATBALF, VSAM keyed by account + type + category) - running balance per account per transaction category (CVTRA01Y).
Outputs
  • Transaction master (DD TRANFILE, AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS) - one record per posted transaction (TRAN-RECORD, CVTRA05Y), with the processing timestamp set to the time of posting.
  • Account master - balances updated in place.
  • Transaction category balances - updated in place, or a new record created for a first transaction in a category.
  • Daily rejects (DD DALYREJS, AWS.M2.CARDDEMO.DALYREJS) - the original 350-byte transaction followed by an 80-byte trailer: a 4-digit reason code and its description.
  • Counts of transactions processed and rejected on SYSOUT; return code 4 when anything was rejected.
Processing
  1. Opens the files: daily transactions and cross-reference for input, account and category balances for update, the transaction master and rejects file for output (0000- to 0500- open paragraphs).
  2. Reads each daily transaction and counts it (1000-DALYTRAN-GET-NEXT, main loop).
  3. Validates it (1500-VALIDATE-TRAN): looks up the card in the cross-reference (1500-A-LOOKUP-XREF), and if found, reads the account and applies the credit-limit and expiration checks (1500-B-LOOKUP-ACCT).
  4. For a valid transaction (2000-POST-TRANSACTION): builds the transaction master record from the daily record, stamps it with the current date and time (Z-GET-DB2-FORMAT-TIMESTAMP), updates the category balance (2700-UPDATE-TCATBAL, creating it if needed in 2700-A-CREATE-TCATBAL-REC), updates the account (2800-UPDATE-ACCOUNT-REC), and writes the transaction (2900-WRITE-TRANSACTION-FILE).
  5. For an invalid one, writes it to the rejects file with the reason (2500-WRITE-REJECT-REC).
  6. Closes the files, displays the counts, and sets return code 4 if there were rejects.
Business rules
  • Reject reasons: 100 "INVALID CARD NUMBER FOUND" (card not in the cross-reference); 101 "ACCOUNT RECORD NOT FOUND"; 102 "OVERLIMIT TRANSACTION"; 103 "TRANSACTION RECEIVED AFTER ACCT EXPIRATION".
  • Credit limit: the transaction is over limit when ACCT-CURR-CYC-CREDIT - ACCT-CURR-CYC-DEBIT + DALYTRAN-AMT exceeds ACCT-CREDIT-LIMIT. The check uses the current cycle's totals, not the account's current balance (ACCT-CURR-BAL).
  • Expiration: rejected when the date part of the origination timestamp (DALYTRAN-ORIG-TS, first 10 characters) is after ACCT-EXPIRAION-DATE.
  • Posting: the amount is added to ACCT-CURR-BAL; a positive or zero amount is added to ACCT-CURR-CYC-CREDIT and a negative one to ACCT-CURR-CYC-DEBIT. The amount is also added to TRAN-CAT-BAL for the account, type, and category.
  • Errors: any open, read, write, or close failure on the files stops the run with an abend (9999-ABEND-PROGRAM, CEE3ABD with code 999); so does writing a transaction ID that's already on the transaction master.
Notes for modernization
  • One reason per reject: when a transaction is both over limit and past expiration, only reason 103 is kept (the second check overwrites the first).
  • A failed account update is silently ignored: if the account rewrite fails, the program sets reason 109 but doesn't reject or stop - by then the category balance has already been updated and the transaction is still written, so the files can disagree.
  • The transaction master is opened for OUTPUT, which for a VSAM KSDS only works when the file is empty or defined as reusable; the scheduling around POSTTRAN has to make sure of that, or the open fails.
  • The over-limit rule uses cycle credits and debits rather than the balance - worth confirming with the business that this is the intended rule before carrying it over.
  • The error message for closing the rejects file shows the cross-reference file's status (copy-and-paste slip in 9300-DALYREJS-CLOSE).
  • Posting is a read-validate-update loop over keyed files with no restart logic: a failure part-way leaves some transactions posted and others not. A modern version would post each transaction in one database transaction, or make the batch restartable.

Data access

Which programs create (C), read (R), update (U), or delete (D) each file, Db2 table, and IMS segment. Batch files are matched to their datasets through the JCL, CICS files through the CSD, so online and batch use of the same file share a row.

DataCBTRN02C
AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS fileRU
AWS.M2.CARDDEMO.CARDXREF.VSAM.KSDS fileR
AWS.M2.CARDDEMO.DALYREJS fileC
AWS.M2.CARDDEMO.DALYTRAN.PS fileR
AWS.M2.CARDDEMO.TCATBALF.VSAM.KSDS fileCRU
AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS fileC

Data dictionary

The records kept in files and Db2 tables: what each field means (from reviewed summaries, where there are any) and, from the source, which programs set each field. A program sets a field when it moves, computes, or accepts a value into it; reading or writing the whole record is under "stored in".

CVACT01Y: ACCOUNT-RECORD

One record per credit card account: its balance, limits, key dates, and current billing-cycle totals. Kept in the account master file (AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS, keyed by account ID), 300 bytes long.

Fields
FieldMeaningNotes
ACCOUNT-RECORDThe whole account recordRead by the account view, update, and bill payment screens and by the batch jobs; rewritten by posting (POSTTRAN), interest (INTCALC), bill payment (CB00), and the account update screen (CAUP)
ACCT-IDAccount number, 11 digitsThe file's key. Other records point to it: the card record (CARD-ACCT-ID) and the card cross-reference (XREF-ACCT-ID)
ACCT-ACTIVE-STATUSWhether the account is active, one characterProbably Y or N; the copybook defines no values. Set by the import job; the account update screen changes it through its own copy of the record (ACCT-UPDATE-RECORD)
ACCT-CURR-BALCurrent balance, signed, two decimals (zoned decimal, not packed)Probably the amount the customer owes. Maintained by three processes: posting adds each posted transaction (POSTTRAN), the monthly interest run adds the interest (INTCALC), and an online bill payment subtracts the payment (CB00)
ACCT-CREDIT-LIMITCredit limit, signed, two decimalsPosting rejects a transaction that would take the account over it (CBTRN02C). Set only by the import job and the account update screen
ACCT-CASH-CREDIT-LIMITCash advance limit, signed, two decimalsUsed online (authorization, account view and update) and printed by the batch account report (CBACT01C) and the export; posting doesn't check it
ACCT-OPEN-DATEDate the account was opened, 10 charactersProbably YYYY-MM-DD, kept as text
ACCT-EXPIRAION-DATEDate the account expires, 10 charactersProbably YYYY-MM-DD, kept as text. Posting rejects transactions after it. The name is misspelled ("EXPIRAION") in the source
ACCT-REISSUE-DATEDate the account (or its cards) was last reissued, 10 charactersProbably YYYY-MM-DD, kept as text. Only displayed and exported
ACCT-CURR-CYC-CREDITTotal credits in the current billing cycle, signed, two decimalsPosting adds credit transactions; the monthly interest run resets it to zero when it closes the cycle
ACCT-CURR-CYC-DEBITTotal debits in the current billing cycle, signed, two decimalsPosting adds debit transactions; the monthly interest run resets it to zero when it closes the cycle
ACCT-ADDR-ZIPZIP code, 10 charactersProbably the billing ZIP code. Set only by the import job and read only by the export job - but see the notes: the account update screen overwrites it
ACCT-GROUP-IDDisclosure group, 10 charactersThe interest run uses it to look up the account's interest rate in the disclosure group file (INTCALC)
Notes for modernization
FieldPICBytesValuesSet by
ACCOUNT-RECORD1‑300
  ACCT-ID9(11)1‑11CBIMPORT (CBIMPORT), CBTRN01C
  ACCT-ACTIVE-STATUSX(01)12‑12CBIMPORT (CBIMPORT)
  ACCT-CURR-BALS9(10)V9913‑24CBACT04C (INTCALC), CBIMPORT (CBIMPORT), CBTRN02C (POSTTRAN), COBIL00C (transaction CB00)
  ACCT-CREDIT-LIMITS9(10)V9925‑36CBIMPORT (CBIMPORT)
  ACCT-CASH-CREDIT-LIMITS9(10)V9937‑48CBIMPORT (CBIMPORT)
  ACCT-OPEN-DATEX(10)49‑58CBIMPORT (CBIMPORT)
  ACCT-EXPIRAION-DATEX(10)59‑68CBIMPORT (CBIMPORT)
  ACCT-REISSUE-DATEX(10)69‑78CBIMPORT (CBIMPORT)
  ACCT-CURR-CYC-CREDITS9(10)V9979‑90CBACT04C (INTCALC), CBIMPORT (CBIMPORT), CBTRN02C (POSTTRAN)
  ACCT-CURR-CYC-DEBITS9(10)V9991‑102CBACT04C (INTCALC), CBIMPORT (CBIMPORT), CBTRN02C (POSTTRAN)
  ACCT-ADDR-ZIPX(10)103‑112CBIMPORT (CBIMPORT)
  ACCT-GROUP-IDX(10)113‑122CBIMPORT (CBIMPORT)

CVACT03Y: CARD-XREF-RECORD

The card cross-reference: one record per card, linking the card number to its customer and account. Kept in AWS.M2.CARDDEMO.CARDXREF.VSAM.KSDS (keyed by card number), 50 bytes long, with an alternate index path (CARDXREF.VSAM.AIX.PATH) that the online screens use to go from an account to its cards.

Fields
FieldMeaningNotes
CARD-XREF-RECORDThe whole cross-reference recordRead by posting (POSTTRAN), interest (INTCALC), the transaction report (TRANREPT), and most online screens; written only by the import job
XREF-CARD-NUMCard number, 16 charactersThe file's key. Several programs move a card number into it only to look the record up (authorization COPAUA0C, the add-transaction screen COTRN02C, and CBTRN01C, a transaction validation program no job in the source runs) - they don't change the file
XREF-CUST-IDCustomer number, 9 digitsPoints to the customer record (CUST-ID)
XREF-ACCT-IDAccount number, 11 digitsPoints to the account record (ACCT-ID). Probably the key of the alternate index, since the account and bill payment screens look cards up by account. The add-transaction screen sets it only to search by account
Notes for modernization
FieldPICBytesValuesSet by
CARD-XREF-RECORD1‑50
  XREF-CARD-NUMX(16)1‑16CBIMPORT (CBIMPORT), CBTRN01C, COPAUA0C (transaction CP00), COTRN02C (transaction CT02)
  XREF-CUST-ID9(09)17‑25CBIMPORT (CBIMPORT)
  XREF-ACCT-ID9(11)26‑36CBIMPORT (CBIMPORT), COTRN02C (transaction CT02)

CVTRA01Y: TRAN-CAT-BAL-RECORD

FieldPICBytesValuesSet by
TRAN-CAT-BAL-RECORD1‑50
  TRAN-CAT-KEY1‑17
    TRANCAT-ACCT-ID9(11)1‑11CBTRN02C (POSTTRAN)
    TRANCAT-TYPE-CDX(02)12‑13CBTRN02C (POSTTRAN)
    TRANCAT-CD9(04)14‑17CBTRN02C (POSTTRAN)
  TRAN-CAT-BALS9(09)V9918‑28CBTRN02C (POSTTRAN)

CVTRA05Y: TRAN-RECORD

One record per card transaction: what kind it is, the amount, the merchant, the card, and when it happened and was processed. Kept in the transaction master file (AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS, keyed by transaction ID), 350 bytes long. The same layout is used for the daily transaction file the report reads (TRANSACT.DALY) and the system transactions the interest run writes (SYSTRAN).

Fields
FieldMeaningNotes
TRAN-RECORDThe whole transaction recordWritten by posting (POSTTRAN), the add-transaction screen (CT02), and bill payment (CB00); the interest run (INTCALC) writes its interest transactions to the separate SYSTRAN file
TRAN-IDTransaction ID, 16 charactersThe master file's key. Posting copies it from the daily transaction; the add-transaction and bill payment screens read the highest ID on file and add 1; the interest run builds one from its run date (PARM) and a counter. The transaction list screen (CT00) sets it only to start browsing
TRAN-TYPE-CDTransaction type, 2 charactersProbably a code from the transaction type file (CVTRA03Y). The interest run writes '01', bill payment writes '02'
TRAN-CAT-CDTransaction category within the type, 4 digitsProbably a code from the transaction category file (CVTRA04Y). The interest run writes 5, bill payment writes 2
TRAN-SOURCEWhere the transaction came from, 10 charactersThe interest run writes 'System', bill payment writes 'POS TERM'
TRAN-DESCDescription, 100 charactersBill payment writes 'BILL PAYMENT - ONLINE'; the interest run builds a description that includes the account
TRAN-AMTAmount, signed, two decimals (zoned decimal)Bill payment records the whole current balance as the payment
TRAN-MERCHANT-IDMerchant number, 9 digits
TRAN-MERCHANT-NAMEMerchant name, 50 characters
TRAN-MERCHANT-CITYMerchant city, 50 characters
TRAN-MERCHANT-ZIPMerchant ZIP code, 10 characters
TRAN-CARD-NUMCard the transaction was made with, 16 charactersPosting uses it to find the account through the card cross-reference
TRAN-ORIG-TSWhen the transaction happened, 26 charactersProbably a Db2-style timestamp, YYYY-MM-DD-HH.MM.SS.nnnnnn
TRAN-PROC-TSWhen it was processed, 26 charactersProbably the same timestamp format; the transaction report (TRANREPT) selects transactions whose first 10 characters (the date) fall in its date range
Notes for modernization
FieldPICBytesValuesSet by
TRAN-RECORD1‑350
  TRAN-IDX(16)1‑16CBACT04C (INTCALC), CBIMPORT (CBIMPORT), CBTRN02C (POSTTRAN), COBIL00C (transaction CB00), COTRN00C (transaction CT00), COTRN02C (transaction CT02)
  TRAN-TYPE-CDX(02)17‑18CBACT04C (INTCALC), CBIMPORT (CBIMPORT), CBTRN02C (POSTTRAN), COBIL00C (transaction CB00)
  TRAN-CAT-CD9(04)19‑22CBACT04C (INTCALC), CBIMPORT (CBIMPORT), CBTRN02C (POSTTRAN), COBIL00C (transaction CB00)
  TRAN-SOURCEX(10)23‑32CBACT04C (INTCALC), CBIMPORT (CBIMPORT), CBTRN02C (POSTTRAN), COBIL00C (transaction CB00)
  TRAN-DESCX(100)33‑132CBACT04C (INTCALC), CBIMPORT (CBIMPORT), CBTRN02C (POSTTRAN), COBIL00C (transaction CB00)
  TRAN-AMTS9(09)V99133‑143CBACT04C (INTCALC), CBIMPORT (CBIMPORT), CBTRN02C (POSTTRAN), COBIL00C (transaction CB00), COTRN02C (transaction CT02)
  TRAN-MERCHANT-ID9(09)144‑152CBACT04C (INTCALC), CBIMPORT (CBIMPORT), CBTRN02C (POSTTRAN), COBIL00C (transaction CB00)
  TRAN-MERCHANT-NAMEX(50)153‑202CBACT04C (INTCALC), CBIMPORT (CBIMPORT), CBTRN02C (POSTTRAN), COBIL00C (transaction CB00)
  TRAN-MERCHANT-CITYX(50)203‑252CBACT04C (INTCALC), CBIMPORT (CBIMPORT), CBTRN02C (POSTTRAN), COBIL00C (transaction CB00)
  TRAN-MERCHANT-ZIPX(10)253‑262CBACT04C (INTCALC), CBIMPORT (CBIMPORT), CBTRN02C (POSTTRAN), COBIL00C (transaction CB00)
  TRAN-CARD-NUMX(16)263‑278CBACT04C (INTCALC), CBIMPORT (CBIMPORT), CBTRN02C (POSTTRAN), COBIL00C (transaction CB00)
  TRAN-ORIG-TSX(26)279‑304CBACT04C (INTCALC), CBIMPORT (CBIMPORT), CBTRN02C (POSTTRAN), COBIL00C (transaction CB00)
  TRAN-PROC-TSX(26)305‑330CBACT04C (INTCALC), CBIMPORT (CBIMPORT), CBTRN02C (POSTTRAN), COBIL00C (transaction CB00)

CVTRA06Y: DALYTRAN-RECORD

FieldPICBytesValuesSet by
DALYTRAN-RECORD1‑350
  DALYTRAN-IDX(16)1‑16
  DALYTRAN-TYPE-CDX(02)17‑18
  DALYTRAN-CAT-CD9(04)19‑22
  DALYTRAN-SOURCEX(10)23‑32
  DALYTRAN-DESCX(100)33‑132
  DALYTRAN-AMTS9(09)V99133‑143
  DALYTRAN-MERCHANT-ID9(09)144‑152
  DALYTRAN-MERCHANT-NAMEX(50)153‑202
  DALYTRAN-MERCHANT-CITYX(50)203‑252
  DALYTRAN-MERCHANT-ZIPX(10)253‑262
  DALYTRAN-CARD-NUMX(16)263‑278
  DALYTRAN-ORIG-TSX(26)279‑304
  DALYTRAN-PROC-TSX(26)305‑330

Findings

Check 2 job(s) the schedule doesn't make wait for the data they read
Compared the client's scheduler definitions with which jobs write and read each dataset and Db2 table.
Check 5 dataset(s) in scope are also used by jobs outside it
Moving these datasets affects the listed jobs too: migrate them together, or keep the data in sync during the transition.
Note 2 job(s) reading data written in another scheduler flow
Compared the client's scheduler definitions with which jobs write and read each dataset and Db2 table.
Note From the review of job POSTTRAN
Note From the review of program CBTRN02C

Appendix: sources and method

About the source

A sample assessment of AWS CardDemo, an open-source mainframe credit card application (Apache License 2.0, Copyright Amazon.com, Inc. or its affiliates), at commit 59cc6c2 of https://github.com/aws-samples/aws-mainframe-modernization-carddemo. No client code is included.

Libraries, in search order

#Library
1APP

How this report was made