Modernization assessment - CARDDEMO

Prepared 19 November 2026 · All members of the libraries provided · 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

46
batch jobs
25
transactions / CICS flows
45
programs in scope
41,347
lines of source
71
datasets
3
findings to resolve

This assessment covers 46 batch job(s) and 25 online transaction(s) or CICS flow(s), 45 application program(s), and 41,347 lines of source. Approach: 42 refactor, 17 expose as API, 7 rehost, 5 retire (suggested, to confirm). 3 finding(s) should be resolved before estimating: 1 member(s) referenced but not in the source; 1 program(s) use ALTER; 1 file(s) a program uses that its job doesn't define.

What they do

Inventory

Everything loaded: 44 COBOL program(s) and 2 assembler module(s), 62 copybook(s), 46 job(s), 2 PROC(s), 25 CICS transaction(s) defined.

Lines of source by type (excluding comments and blanks)
COBOL: 22,904COBOL22,904COPYBOOK: 9,573COPYBOOK9,573BMS: 5,324BMS5,324JOB: 1,601JOB1,601CSD: 685CSD685CA7: 425CA7425CONTROLM: 280CONTROLM280PARM: 217PARM217DCLGEN: 85DCLGEN85ASM: 75ASM75PROC: 60PROC60DDL: 53DDL53DBD: 41DBD41PSB: 24PSB24
TypeCodeComment
COBOL22,9043,906
COPYBOOK9,573989
BMS5,324430
JOB1,6011,304
CSD6850
CA74250
CONTROLM2800
PARM2170
DCLGEN85106
ASM7539
PROC6054
DDL530
DBD4194
PSB2464
COBOL programs by kind
cics: 25cics25batch: 12batch12subprogram: 7subprogram7
COBOL programs using
IMS: 7IMS7DB2: 4DB24MQ: 3MQ3
Largest programs (lines of code)
COACTUPC: 3,368COACTUPC3,368COTRTLIC: 1,597COTRTLIC1,597COTRTUPC: 1,241COTRTUPC1,241COCRDUPC: 1,194COCRDUPC1,194COCRDLIC: 1,093COCRDLIC1,093COPAUS0C: 792COPAUS0C792CBSTM03A: 784CBSTM03A784COPAUA0C: 771COPAUA0C771COACTVWC: 703COACTVWC703COCRDSLC: 642COCRDSLC642

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
COACTUPC420274110410166
COTRTUPC1745114046523
COTRTLIC1688617655828
COCRDUPC152729034721
COCRDLIC1245910334116
COCRDSLC7333503369
COUSR00C7325845160
COTRN00C7226845160
COACTVWC6728603379
COTRN02C64141306180

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
CAUP: 6,518CAUP6,518CTLI: 2,674CTLI2,674CPVS: 2,218CPVS2,218CCLI: 2,149CCLI2,149CTTU: 1,851CTTU1,851CT00: 1,775CT001,775CCUP: 1,771CCUP1,771CU00: 1,769CU001,769CAVW: 1,745CAVW1,745CPVD: 1,461CPVD1,461CT02: 1,381CT021,381CCDL: 1,180CCDL1,180CR00: 1,122CR001,122CREASTMT: 1,070CREASTMT1,070CP00: 905CP00905
NameKindprogramscopybooksscreens (mapsets)datasetsDb2 tablesIMS segmentsLinesApproach
CAUPtransaction216136,518Expose as API suggested
CTLItransaction111112,674Expose as API suggested
CPVStransaction1121322,218Rehost suggested
CCLItransaction19112,149Expose as API suggested
CTTUtransaction111111,851Expose as API suggested
CT00transaction16111,775Expose as API suggested
CCUPtransaction111111,771Expose as API suggested
CU00transaction16111,769Expose as API suggested
CAVWtransaction113131,745Expose as API suggested
CPVDtransaction281121,461Rehost suggested
CT02transaction28131,381Expose as API suggested
CCDLtransaction111121,180Expose as API suggested
CR00transaction2611,122Refactor suggested
CREASTMTjob2481,070Refactor suggested
CP00transaction1832905Rehost suggested
CT01transaction1611831Expose as API suggested
CB00transaction1813774Expose as API suggested
CM00transaction171751Refactor suggested
TRANREPTjob158708Refactor suggested
POSTTRANjob156697Refactor suggested
CA00transaction171695Refactor suggested
CU02transaction1611683Expose as API suggested
INTCALCjob156622Refactor suggested
CU03transaction1611603Expose as API suggested
CC00transaction1611581Expose as API suggested
CU01transaction1611573Expose as API suggested
CBEXPORTjob166564Refactor suggested
CDRAtransaction111514Expose as API suggested
CBIMPORTjob166505Refactor suggested
READACCTjob224497Refactor suggested
CDRDtransaction1409Refactor suggested
LOADPADBjob1422340Rehost suggested
CBPAUP0Jjob122337Rehost suggested
UNLDPADBjob1442312Rehost suggested
UNLDGSAMjob1644311Rehost suggested
CREADB21job242Refactor suggested
MNTTRDB2job111200Refactor suggested
READCUSTjob111159Refactor suggested
READCARDjob111146Refactor suggested
READXREFjob111144Refactor suggested
CBADMCDJjob1121Refactor suggested
TRANEXTRjob4283Refactor suggested
CARDFILEjob481Refactor suggested
TRANFILEjob481Refactor suggested
ESDSRRDSjob368Refactor suggested
XREFFILEjob468Refactor suggested
TRANBKPjob365Refactor suggested
PRTCATBLjob363Refactor suggested
DEFGDGDjob652Refactor suggested
CUSTFILEjob248Refactor suggested
DUSRSECJjob248Refactor suggested
DEFGDGBjob641Retire suggested
ACCTFILEjob236Refactor suggested
DISCGRPjob236Refactor suggested
TCATBALFjob236Refactor suggested
TRANCATGjob236Refactor suggested
TRANTYPEjob236Refactor suggested
WAITSTEPjob235Refactor suggested
DBPAUTP0job332Refactor suggested
TRANIDXjob330Refactor suggested
COMBTRANjob427Refactor suggested
DEFCUSTjob224Retire suggested
INTRDRJ1job314Refactor suggested
TXT2PDF1job214Refactor suggested
FTPJCLjob13Refactor suggested
CLOSEFILjob12Refactor suggested
OPENFILjob12Refactor suggested
DALYREJSjob110Retire suggested
REPTFILEjob110Retire suggested
INTRDRJ2job29Refactor suggested
CDV1transaction0Retire suggested

Modernization roadmap

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

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

Rehost (7)

NameWhy
CBPAUP0J suggestedUses IMS databases; rehost first and plan the data migration separately.
CP00 suggested905 lines with IMS or heavy logic: rehost, then expose services.
CPVD suggested1,461 lines with IMS or heavy logic: rehost, then expose services.
CPVS suggested2,218 lines with IMS or heavy logic: rehost, then expose services.
LOADPADB suggestedUses IMS databases; rehost first and plan the data migration separately.
UNLDGSAM suggestedUses IMS databases; rehost first and plan the data migration separately.
UNLDPADB suggestedUses IMS databases; rehost first and plan the data migration separately.

Refactor (42)

NameWhy
ACCTFILE suggestedOnly IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.
CA00 suggestedScreen and navigation only (no data access): rebuild in the new user interface.
CARDFILE suggestedOnly IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.
CBADMCDJ suggestedOnly IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.
CBEXPORT suggested1 program(s), 564 lines: small enough to rewrite as a batch service, query, or report on the target platform.
CBIMPORT suggested1 program(s), 505 lines: small enough to rewrite as a batch service, query, or report on the target platform.
CDRD suggestedScreen and navigation only (no data access): rebuild in the new user interface.
CLOSEFIL suggestedOnly IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.
CM00 suggestedScreen and navigation only (no data access): rebuild in the new user interface.
COMBTRAN suggestedOnly IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.
CR00 suggestedScreen and navigation only (no data access): rebuild in the new user interface.
CREADB21 suggestedOnly IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.
CREASTMT suggested2 program(s), 1,070 lines: small enough to rewrite as a batch service, query, or report on the target platform.
CUSTFILE suggestedOnly IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.
DBPAUTP0 suggestedOnly IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.
DEFGDGD suggestedOnly IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.
DISCGRP suggestedOnly IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.
DUSRSECJ suggestedOnly IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.
ESDSRRDS suggestedOnly IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.
FTPJCL suggestedOnly IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.
INTCALC suggested1 program(s), 622 lines: small enough to rewrite as a batch service, query, or report on the target platform.
INTRDRJ1 suggestedOnly IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.
INTRDRJ2 suggestedOnly IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.
MNTTRDB2 suggested1 program(s), 200 lines: small enough to rewrite as a batch service, query, or report on the target platform.
OPENFIL suggestedOnly IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.
POSTTRAN suggested1 program(s), 697 lines: small enough to rewrite as a batch service, query, or report on the target platform.
PRTCATBL suggestedOnly IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.
READACCT suggested2 program(s), 497 lines: small enough to rewrite as a batch service, query, or report on the target platform.
READCARD suggested1 program(s), 146 lines: small enough to rewrite as a batch service, query, or report on the target platform.
READCUST suggested1 program(s), 159 lines: small enough to rewrite as a batch service, query, or report on the target platform.
READXREF suggested1 program(s), 144 lines: small enough to rewrite as a batch service, query, or report on the target platform.
TCATBALF suggestedOnly IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.
TRANBKP suggestedOnly IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.
TRANCATG suggestedOnly IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.
TRANEXTR suggestedOnly IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.
TRANFILE suggestedOnly IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.
TRANIDX suggestedOnly IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.
TRANREPT suggested1 program(s), 708 lines: small enough to rewrite as a batch service, query, or report on the target platform.
TRANTYPE suggestedOnly IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.
TXT2PDF1 suggestedOnly IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.
WAITSTEP suggested2 program(s), 35 lines: small enough to rewrite as a batch service, query, or report on the target platform.
XREFFILE suggestedOnly IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.

Expose as API (17)

NameWhy
CAUP suggestedReads or updates business data behind a 3270 screen: keep the logic as a service (API) and replace the screen with a web interface.
CAVW suggestedReads or updates business data behind a 3270 screen: keep the logic as a service (API) and replace the screen with a web interface.
CB00 suggestedReads or updates business data behind a 3270 screen: keep the logic as a service (API) and replace the screen with a web interface.
CC00 suggestedReads or updates business data behind a 3270 screen: keep the logic as a service (API) and replace the screen with a web interface.
CCDL suggestedReads or updates business data behind a 3270 screen: keep the logic as a service (API) and replace the screen with a web interface.
CCLI suggestedReads or updates business data behind a 3270 screen: keep the logic as a service (API) and replace the screen with a web interface.
CCUP suggestedReads or updates business data behind a 3270 screen: keep the logic as a service (API) and replace the screen with a web interface.
CDRA suggestedReads or updates business data behind a 3270 screen: keep the logic as a service (API) and replace the screen with a web interface.
CT00 suggestedReads or updates business data behind a 3270 screen: keep the logic as a service (API) and replace the screen with a web interface.
CT01 suggestedReads or updates business data behind a 3270 screen: keep the logic as a service (API) and replace the screen with a web interface.
CT02 suggestedReads or updates business data behind a 3270 screen: keep the logic as a service (API) and replace the screen with a web interface.
CTLI suggestedReads or updates business data behind a 3270 screen: keep the logic as a service (API) and replace the screen with a web interface.
CTTU suggestedReads or updates business data behind a 3270 screen: keep the logic as a service (API) and replace the screen with a web interface.
CU00 suggestedReads or updates business data behind a 3270 screen: keep the logic as a service (API) and replace the screen with a web interface.
CU01 suggestedReads or updates business data behind a 3270 screen: keep the logic as a service (API) and replace the screen with a web interface.
CU02 suggestedReads or updates business data behind a 3270 screen: keep the logic as a service (API) and replace the screen with a web interface.
CU03 suggestedReads or updates business data behind a 3270 screen: keep the logic as a service (API) and replace the screen with a web interface.

Retire (5)

NameWhy
CDV1 suggestedPROGRAM COCRDSEC isn't in the source: confirm with the client whether it's still used, and retire it if not.
DALYREJS suggestedOnly IBM utilities that define and delete data sets - housekeeping a database-backed platform doesn't need.
DEFCUST suggestedOnly IBM utilities that define and delete data sets - housekeeping a database-backed platform doesn't need.
DEFGDGB suggestedOnly IBM utilities that define and delete data sets - housekeeping a database-backed platform doesn't need.
REPTFILE suggestedOnly IBM utilities that define and delete data sets - housekeeping a database-backed platform doesn't need.

Job and transaction details

Job ACCTFILE

Refactor suggested - Only IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.

1
jobs
3
steps
1
system programs
2
datasets
36
lines of source
InputsStepsOutputsdeletedeletedefinedefineAWS.M2.CARDDEMO.ACCTDATA.PSAWS.M2.CARDDEMO.ACCTDATA.PSSTEP05: IDCAMSSTEP05: IDCAMSSTEP10: IDCAMSSTEP10: IDCAMSSTEP15: IDCAMSSTEP15: IDCAMSAWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDSAWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Job ACCTFILE

Step 1 - STEP05: runs IDCAMS (IBM utility)

  • Comment: DELETE ACCOUNT VSAM FILE IF ONE ALREADY EXISTS
  • Deletes: AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS
  • Control statements: DELETE AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS CLUSTER IF MAXCC LE 08 THEN SET MAXCC = 0

Step 2 - STEP10: runs IDCAMS (IBM utility)

  • Comment: DEFINE ACCOUNT VSAM FILE
  • Defines: AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS
  • Control statements: DEFINE CLUSTER (NAME(AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS) CYLINDERS(1 5) VOLUMES(AWSHJ1 ) KEYS(11 0) RECORDSIZE(300 300) SHAREOPTIONS(2 3) ERASE

Step 3 - STEP15: runs IDCAMS (IBM utility)

  • Comment: COPY DATA FROM FLAT FILE TO VSAM FILE
  • Copies AWS.M2.CARDDEMO.ACCTDATA.PS into AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS
  • Reads: AWS.M2.CARDDEMO.ACCTDATA.PS (DD ACCTDATA)
  • Writes: AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS (DD ACCTVSAM)
  • Control statements: REPRO INFILE(ACCTDATA) OUTFILE(ACCTVSAM)

Inputs from outside the job: AWS.M2.CARDDEMO.ACCTDATA.PS Outputs it leaves behind: AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS

Job CARDFILE

Refactor suggested - Only IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.

1
jobs
8
steps
2
system programs
4
datasets
81
lines of source
InputsStepsOutputsdeletedeletedeletedeletedefinedefinedefinedefinedefinedefineAWS.M2.CARDDEMO.CARDDATA.PSAWS.M2.CARDDEMO.CARDDATA.PSAWS.M2.CARDDEMO.CARDDATA.VSAM.KSDSAWS.M2.CARDDEMO.CARDDATA.VSAM.KSDSCLCIFIL: SDSFCLCIFIL: SDSFSTEP05: IDCAMSSTEP05: IDCAMSSTEP10: IDCAMSSTEP10: IDCAMSSTEP15: IDCAMSSTEP15: IDCAMSSTEP40: IDCAMSSTEP40: IDCAMSSTEP50: IDCAMSSTEP50: IDCAMSSTEP60: IDCAMSSTEP60: IDCAMSOPCIFIL: SDSFOPCIFIL: SDSFAWS.M2.CARDDEMO.CARDDATA.VSAM.AIXAWS.M2.CARDDEMO.CARDDATA.VSAM.AIXAWS.M2.CARDDEMO.CARDDATA.VSAM.KSDSAWS.M2.CARDDEMO.CARDDATA.VSAM.KSDSAWS.M2.CARDDEMO.CARDDATA.VSAM.AIX.PATHAWS.M2.CARDDEMO.CARDDATA.VSAM.AIX.PATH

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Job CARDFILE

Step 1 - CLCIFIL: runs SDSF (IBM utility)

  • Comment: Close files in CICS region

Step 2 - STEP05: runs IDCAMS (IBM utility)

  • Comment: DELETE CARD DATA VSAM FILE IF ONE ALREADY EXISTS
  • Deletes: AWS.M2.CARDDEMO.CARDDATA.VSAM.AIX, AWS.M2.CARDDEMO.CARDDATA.VSAM.KSDS
  • Control statements: DELETE AWS.M2.CARDDEMO.CARDDATA.VSAM.KSDS CLUSTER IF MAXCC LE 08 THEN SET MAXCC = 0 DELETE AWS.M2.CARDDEMO.CARDDATA.VSAM.AIX ALTERNATEINDEX IF MAXCC LE 08 THEN SET MAXCC = 0

Step 3 - STEP10: runs IDCAMS (IBM utility)

  • Comment: DEFINE CARD DATA VSAM FILE
  • Defines: AWS.M2.CARDDEMO.CARDDATA.VSAM.KSDS
  • Control statements: DEFINE CLUSTER (NAME(AWS.M2.CARDDEMO.CARDDATA.VSAM.KSDS) CYLINDERS(1 5) VOLUMES(AWSHJ1 ) KEYS(16 0) RECORDSIZE(150 150) SHAREOPTIONS(2 3) ERASE

Step 4 - STEP15: runs IDCAMS (IBM utility)

  • Comment: COPY DATA FROM FLAT FILE TO VSAM FILE
  • Copies AWS.M2.CARDDEMO.CARDDATA.PS into AWS.M2.CARDDEMO.CARDDATA.VSAM.KSDS
  • Reads: AWS.M2.CARDDEMO.CARDDATA.PS (DD CARDDATA)
  • Writes: AWS.M2.CARDDEMO.CARDDATA.VSAM.KSDS (DD CARDVSAM)
  • Control statements: REPRO INFILE(CARDDATA) OUTFILE(CARDVSAM)

Step 5 - STEP40: runs IDCAMS (IBM utility)

  • Comment: CREATE ALTERNATE INDEX ON ACCT ID
  • Defines: AWS.M2.CARDDEMO.CARDDATA.VSAM.AIX
  • Control statements: DEFINE ALTERNATEINDEX (NAME(AWS.M2.CARDDEMO.CARDDATA.VSAM.AIX)- RELATE(AWS.M2.CARDDEMO.CARDDATA.VSAM.KSDS) KEYS(11 16) NONUNIQUEKEY UPGRADE RECORDSIZE(150,150) VOLUMES(AWSHJ1) CYLINDERS(5,1))

Step 6 - STEP50: runs IDCAMS (IBM utility)

  • Comment: DEFINE PATH IS USED TO RELATE THE ALTERNATE INDEX TO BASE CLUSTER
  • Defines: AWS.M2.CARDDEMO.CARDDATA.VSAM.AIX.PATH
  • Control statements: DEFINE PATH (NAME(AWS.M2.CARDDEMO.CARDDATA.VSAM.AIX.PATH) PATHENTRY(AWS.M2.CARDDEMO.CARDDATA.VSAM.AIX))

Step 7 - STEP60: runs IDCAMS (IBM utility)

  • Comment: BUILD ALTERNATE INDEX CLUSTER
  • BLDINDEX AWS.M2.CARDDEMO.CARDDATA.VSAM.KSDS into AWS.M2.CARDDEMO.CARDDATA.VSAM.AIX
  • Reads: AWS.M2.CARDDEMO.CARDDATA.VSAM.KSDS
  • Writes: AWS.M2.CARDDEMO.CARDDATA.VSAM.AIX
  • Control statements: BLDINDEX INDATASET(AWS.M2.CARDDEMO.CARDDATA.VSAM.KSDS) OUTDATASET(AWS.M2.CARDDEMO.CARDDATA.VSAM.AIX)

Step 8 - OPCIFIL: runs SDSF (IBM utility)

  • Comment: Open files in CICS region

Inputs from outside the job: AWS.M2.CARDDEMO.CARDDATA.PS Outputs it leaves behind: AWS.M2.CARDDEMO.CARDDATA.VSAM.AIX

Job CBADMCDJ

Refactor suggested - Only IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.

1
jobs
1
steps
1
system programs
1
datasets
121
lines of source
InputsStepsOutputsOEM.CICSTS.DFHCSDOEM.CICSTS.DFHCSDSTEP1: DFHCSDUPSTEP1: DFHCSDUP

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Job CBADMCDJ

Step 1 - STEP1: runs DFHCSDUP (IBM utility)

  • Comment: Create Resources for Card Demo application / SET PARMS FOR THIS JOB:
  • Uses: OEM.CICSTS.DFHCSD (DD DFHCSD)

Inputs from outside the job: none Outputs it leaves behind: none

Job CBEXPORT

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

1
jobs
2
steps
1
programs
2
system programs
6
copybooks
6
datasets
6
record layouts
564
lines of source
InputsStepsOutputsdeletedeletedefinedefineAWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDSAWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDSAWS.M2.CARDDEMO.CARDDATA.VSAM.KSDSAWS.M2.CARDDEMO.CARDDATA.VSAM.KSDSAWS.M2.CARDDEMO.CARDXREF.VSAM.KSDSAWS.M2.CARDDEMO.CARDXREF.VSAM.KSDSAWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDSAWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDSAWS.M2.CARDDEMO.TRANSACT.VSAM.KSDSAWS.M2.CARDDEMO.TRANSACT.VSAM.KSDSSTEP01: IDCAMSSTEP01: IDCAMSSTEP02: CBEXPORTSTEP02: CBEXPORTAWS.M2.CARDDEMO.EXPORT.DATAAWS.M2.CARDDEMO.EXPORT.DATA

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Job CBEXPORT

Step 1 - STEP01: runs IDCAMS (IBM utility)

  • Comment: EXPORT CUSTOMER DATA FROM VSAM FILES TO MULTI-RECORD EXPORT FILE / FOR BRANCH MIGRATION OR DATA TRANSFER PURPOSES / STEP 1: DEFINE VSAM CLUSTER FOR EXPORT FILE
  • Defines: AWS.M2.CARDDEMO.EXPORT.DATA
  • Deletes: AWS.M2.CARDDEMO.EXPORT.DATA
  • Control statements: DELETE AWS.M2.CARDDEMO.EXPORT.DATA CLUSTER PURGE SET MAXCC = 0 DEFINE CLUSTER (NAME(AWS.M2.CARDDEMO.EXPORT.DATA) INDEXED KEYS(4 28) RECORDSIZE(500 500) CYLINDERS(10 5) FREESPACE(10 10)

Step 2 - STEP02: runs CBEXPORT

  • Comment: STEP 2: RUN EXPORT PROGRAM
  • CBEXPORT's comments: Program : CBEXPORT.CBL / Application : CardDemo / Type : BATCH COBOL Program / Function : Export Customer Data for Branch Migration
  • Reads: AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS (DD ACCTFILE), AWS.M2.CARDDEMO.CARDDATA.VSAM.KSDS (DD CARDFILE), AWS.M2.CARDDEMO.CARDXREF.VSAM.KSDS (DD XREFFILE), AWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDS (DD CUSTFILE), AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS (DD TRANSACT)
  • Writes: AWS.M2.CARDDEMO.EXPORT.DATA (DD EXPFILE)

Inputs from outside the job: AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS, AWS.M2.CARDDEMO.CARDDATA.VSAM.KSDS, AWS.M2.CARDDEMO.CARDXREF.VSAM.KSDS, AWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDS, AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS Outputs it leaves behind: AWS.M2.CARDDEMO.EXPORT.DATA

Job CBIMPORT

Refactor suggested - 1 program(s), 505 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
6
copybooks
6
datasets
6
record layouts
505
lines of source
InputsStepsOutputsAWS.M2.CARDDEMO.EXPORT.DATAAWS.M2.CARDDEMO.EXPORT.DATASTEP01: CBIMPORTSTEP01: CBIMPORTAWS.M2.CARDDEMO.ACCTDATA.IMPORTAWS.M2.CARDDEMO.ACCTDATA.IMPORTAWS.M2.CARDDEMO.CARDXREF.IMPORTAWS.M2.CARDDEMO.CARDXREF.IMPORTAWS.M2.CARDDEMO.CUSTDATA.IMPORTAWS.M2.CARDDEMO.CUSTDATA.IMPORTAWS.M2.CARDDEMO.IMPORT.ERRORSAWS.M2.CARDDEMO.IMPORT.ERRORSAWS.M2.CARDDEMO.TRANSACT.IMPORTAWS.M2.CARDDEMO.TRANSACT.IMPORT

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Job CBIMPORT

Step 1 - STEP01: runs CBIMPORT

  • Comment: IMPORT CUSTOMER DATA FROM MULTI-RECORD EXPORT FILE AND SPLIT / INTO SEPARATE NORMALIZED FILES FOR TARGET SYSTEM
  • CBIMPORT's comments: Program : CBIMPORT.CBL / Application : CardDemo / Type : BATCH COBOL Program / Function : Import Customer Data from Branch Migration Export
  • Reads: AWS.M2.CARDDEMO.EXPORT.DATA (DD EXPFILE)
  • Creates: AWS.M2.CARDDEMO.ACCTDATA.IMPORT (DD ACCTOUT), AWS.M2.CARDDEMO.CARDXREF.IMPORT (DD XREFOUT), AWS.M2.CARDDEMO.CUSTDATA.IMPORT (DD CUSTOUT), AWS.M2.CARDDEMO.IMPORT.ERRORS (DD ERROUT), AWS.M2.CARDDEMO.TRANSACT.IMPORT (DD TRNXOUT)

Inputs from outside the job: AWS.M2.CARDDEMO.EXPORT.DATA Outputs it leaves behind: AWS.M2.CARDDEMO.ACCTDATA.IMPORT, AWS.M2.CARDDEMO.CARDXREF.IMPORT, AWS.M2.CARDDEMO.CUSTDATA.IMPORT, AWS.M2.CARDDEMO.IMPORT.ERRORS, AWS.M2.CARDDEMO.TRANSACT.IMPORT

Job CBPAUP0J

Rehost suggested - Uses IMS databases; rehost first and plan the data migration separately.

1
jobs
1
steps
1
programs
2
copybooks
2
IMS segments
337
lines of source
InputsStepsOutputsSTEP01: CBPAUP0CSTEP01: CBPAUP0C

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Job CBPAUP0J

Step 1 - STEP01: runs CBPAUP0C, through DFSRRC00

  • Comment: EXECUTE IMS PROGRAM TO DELETE EXPIRED AUTHORIZATIONS
  • CBPAUP0C's comments: Program : CBPAUP0C.CBL / Application : CardDemo - Authorization Module / Type : BATCH COBOL IMS Program / Function : Delete Expired Pending Authoriation Messages
  • Reads and deletes from IMS segment PAUTDTL1
  • Reads and deletes from IMS segment PAUTSUM0

Inputs from outside the job: none Outputs it leaves behind: none

Job CLOSEFIL

Refactor suggested - Only IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.

1
jobs
1
steps
1
system programs
12
lines of source
InputsStepsOutputsCLCIFIL: SDSFCLCIFIL: SDSF

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Job CLOSEFIL

Step 1 - CLCIFIL: runs SDSF (IBM utility)

  • Comment: Close files in CICS region

Inputs from outside the job: none Outputs it leaves behind: none

Job COMBTRAN

Refactor suggested - Only IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.

1
jobs
2
steps
2
system programs
4
datasets
27
lines of source
InputsStepsOutputsAWS.M2.CARDDEMO.SYSTRANAWS.M2.CARDDEMO.SYSTRANAWS.M2.CARDDEMO.TRANSACT.BKUPAWS.M2.CARDDEMO.TRANSACT.BKUPAWS.M2.CARDDEMO.TRANSACT.COMBINEDAWS.M2.CARDDEMO.TRANSACT.COMBINEDSTEP05R: SORTSTEP05R: SORTSTEP10: IDCAMSSTEP10: IDCAMSAWS.M2.CARDDEMO.TRANSACT.COMBINEDAWS.M2.CARDDEMO.TRANSACT.COMBINEDAWS.M2.CARDDEMO.TRANSACT.VSAM.KSDSAWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Job COMBTRAN

Step 1 - STEP05R: runs SORT (IBM utility)

  • Comment: Sort current transaction file and system generated transactions
  • Sorts AWS.M2.CARDDEMO.TRANSACT.BKUP into AWS.M2.CARDDEMO.TRANSACT.COMBINED
  • Sorts AWS.M2.CARDDEMO.SYSTRAN into AWS.M2.CARDDEMO.TRANSACT.COMBINED
  • Reads: AWS.M2.CARDDEMO.SYSTRAN (DD SORTIN), AWS.M2.CARDDEMO.TRANSACT.BKUP (DD SORTIN)
  • Creates: AWS.M2.CARDDEMO.TRANSACT.COMBINED (DD SORTOUT)
  • Sort keys: TRAN-ID (ascending, positions 1-16).
  • Control statements: SORT FIELDS=(TRAN-ID,A)

Step 2 - STEP10: runs IDCAMS (IBM utility)

  • Comment: Load combined file to transaction master
  • Copies AWS.M2.CARDDEMO.TRANSACT.COMBINED into AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS
  • Reads: AWS.M2.CARDDEMO.TRANSACT.COMBINED (DD TRANSACT)
  • Writes: AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS (DD TRANVSAM)
  • Control statements: REPRO INFILE(TRANSACT) OUTFILE(TRANVSAM)

Inputs from outside the job: AWS.M2.CARDDEMO.SYSTRAN, AWS.M2.CARDDEMO.TRANSACT.BKUP Outputs it leaves behind: AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS

Job CREADB21

Refactor suggested - Only IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.

1
jobs
5
steps
2
system programs
6
control cards
242
lines of source
InputsStepsOutputsFREEPLN: IKJEFT01FREEPLN: IKJEFT01CRCRDDB: IKJEFT01CRCRDDB: IKJEFT01LDTTYPE: IEFBR14LDTTYPE: IEFBR14RUNTEP2: IKJEFT01RUNTEP2: IKJEFT01LDTCCAT: IKJEFT01LDTCCAT: IKJEFT01

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Job CREADB21

From the job's comments: Create CARDDEMO Database in DAZ1 subsystem (SSID=DAZ1) / You can run the SQLs linked here through SPUFI / If you prefer JCL, you can run them from this job / You may need to bind the utilities used first though / See AWS.M2.CARDDEMO.JCL.UTIL(BINDTIAD) to see how / SET PARMS FOR THIS JOB: / STEP 00 : Free existing plans and packages / : It ends with RC 8 if not existing.

Step 1 - FREEPLN: runs IKJEFT01

  • Comment: STEP 00 : Free existing plans and packages / : It ends with RC 8 if not existing. / : So dont run it if creating new database
  • Reads control card DB2FREE (DD SYSTSIN)

Step 2 - CRCRDDB: runs IKJEFT01

  • Comment: STEP 10 : Use Utility DSNTIAD to create the database / This uses an existing STOGROUP AWST1STG / You would have to create it if not available
  • Reads control card DB2TIAD1 (DD SYSTSIN)
  • Reads control card DB2CREAT (DD SYSIN)

Step 3 - LDTTYPE: runs IEFBR14 (IBM utility)

  • Comment: STEP 20 : Load the transaction Type table / using DSNTEP4 utility

Step 4 - RUNTEP2: runs IKJEFT01

  • Reads control card DB2TEP41 (DD SYSTSIN)
  • Reads control card DB2LTTYP (DD SYSIN)

Step 5 - LDTCCAT: runs IKJEFT01

  • Comment: STEP 30 : Load Transaction Type Category table / using DSNTEP4 utility
  • Reads control card DB2TEP41 (DD SYSTSIN)
  • Reads control card DB2LTCAT (DD SYSIN)

Inputs from outside the job: none Outputs it leaves behind: none

Job CREASTMT

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

1
jobs
5
steps
2
programs
4
system programs
4
copybooks
8
datasets
23
record layouts
1,070
lines of source
InputsStepsOutputsdeletedeletedeletedeletedefinedefinedeletedeletedeletedeleteAWS.M2.CARDDEMO.TRANSACT.VSAM.KSDSAWS.M2.CARDDEMO.TRANSACT.VSAM.KSDSAWS.M2.CARDDEMO.TRXFL.SEQAWS.M2.CARDDEMO.TRXFL.SEQAWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDSAWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDSAWS.M2.CARDDEMO.CARDXREF.VSAM.KSDSAWS.M2.CARDDEMO.CARDXREF.VSAM.KSDSAWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDSAWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDSAWS.M2.CARDDEMO.TRXFL.VSAM.KSDSAWS.M2.CARDDEMO.TRXFL.VSAM.KSDSDELDEF01: IDCAMSDELDEF01: IDCAMSSTEP010: SORTSTEP010: SORTSTEP020: IDCAMSSTEP020: IDCAMSSTEP030: IEFBR14STEP030: IEFBR14STEP040: CBSTM03ASTEP040: CBSTM03AAWS.M2.CARDDEMO.TRXFL.SEQAWS.M2.CARDDEMO.TRXFL.SEQAWS.M2.CARDDEMO.TRXFL.VSAM.KSDSAWS.M2.CARDDEMO.TRXFL.VSAM.KSDSAWS.M2.CARDDEMO.STATEMNT.HTMLAWS.M2.CARDDEMO.STATEMNT.HTMLAWS.M2.CARDDEMO.STATEMNT.PSAWS.M2.CARDDEMO.STATEMNT.PS

What it does

CREASTMT produces the customer statements. It rebuilds a copy of the transaction master keyed by card number, clears out the previous run's statements, and then prints a statement for every card - customer name and address, account ID, current balance, FICO score, and the card's transactions with a total - as both a plain-text file and an HTML file.

Step by step
  1. Clear the work files (DELDEF01, IDCAMS). Deletes the previous card-keyed transaction files (TRXFL.SEQ and TRXFL.VSAM.KSDS) and defines a new, empty VSAM file keyed by card number and transaction ID (32-byte key, 350-byte records).
  2. Re-key the transactions by card (STEP010, SORT). Sorts the whole transaction master by card number (TRAN-CARD-NUM) then transaction ID (TRAN-ID), and moves the card number to the front of each record so it becomes part of the key, writing TRXFL.SEQ.
  3. Load the card-keyed file (STEP020, IDCAMS REPRO). Copies the sorted file into the new VSAM file TRXFL.VSAM.KSDS.
  4. Remove last run's statements (STEP030, IEFBR14). Deletes the previous text and HTML statement files.
  5. Print the statements (STEP040, CBSTM03A with its file-access subroutine CBSTM03B). For each card in the cross-reference, reads the customer and account and writes a statement with the card's transactions and their total, in text (STATEMNT.PS) and HTML (STATEMNT.HTML).
What it needs
  • The transaction master (TRANSACT.VSAM.KSDS) after posting and the interest load, the card cross-reference, the customer file (CUSTDATA.VSAM.KSDS), and the account master.
  • To run after the cycle's posting (POSTTRAN), interest (INTCALC), and combine (COMBTRAN) jobs, so balances and transactions are complete.
What it produces
  • AWS.M2.CARDDEMO.STATEMNT.PS - text statements, one per card.
  • AWS.M2.CARDDEMO.STATEMNT.HTML - the same statements as HTML.
  • TRXFL.SEQ and TRXFL.VSAM.KSDS - work files, rebuilt each run.
Notes for modernization
  • Only works for demo-sized data: the statement program loads every transaction into a table of 51 cards x 10 transactions per card with no overflow check, so a realistic number of cards or transactions corrupts memory rather than failing cleanly.
  • No statement period: every transaction ever posted to the master appears on the statement; there's no cycle start and end date. Real statements need one - confirm the intended cycle with the business.
  • One statement per card, not per account: a customer with two cards on one account gets two statements, each showing the full account balance.
  • The re-keying steps (delete, define, sort, load) exist only to read transactions in card order; with a database, a query ordered by card replaces steps 1-3.
  • The statement program uses z/OS-specific control-block access and ALTER/GO TO (deliberately, to exercise modernization tools); both are removed in a rewrite. Statement layout and HTML generation map naturally to a templating or document-generation tool.
Step-by-step walkthrough from the source
Job CREASTMT

Step 1 - DELDEF01: runs IDCAMS (IBM utility)

  • Comment: This JCL will create statement for each CARD present in the XREF / file
  • Defines: AWS.M2.CARDDEMO.TRXFL.VSAM.KSDS
  • Deletes: AWS.M2.CARDDEMO.TRXFL.SEQ, AWS.M2.CARDDEMO.TRXFL.VSAM.KSDS
  • Control statements: DELETE AWS.M2.CARDDEMO.TRXFL.SEQ DELETE AWS.M2.CARDDEMO.TRXFL.VSAM.KSDS CLUSTER SET MAXCC = 0 DEFINE CLUSTER (NAME(AWS.M2.CARDDEMO.TRXFL.VSAM.KSDS) KEYS(32 0) VOLUMES(TSU023) RECORDSIZE(350 350)

Step 2 - STEP010: runs SORT (IBM utility)

  • Comment: CREATE COPY OF TRANSACT FILE WITH CARD NUMBER AND TRAN ID AS KEY
  • Sorts AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS into AWS.M2.CARDDEMO.TRXFL.SEQ
  • Reads: AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS (DD SORTIN)
  • Creates: AWS.M2.CARDDEMO.TRXFL.SEQ (DD SORTOUT)
  • Sort keys: TRAN-CARD-NUM (ascending, positions 263-278), TRAN-ID (ascending, positions 1-16).
  • Reformats the records (INREC/OUTREC) - see the control statements.
  • Control statements: SORT FIELDS=(263,16,CH,A,1,16,CH,A) OUTREC FIELDS=(1:263,16,17:1,262,279:279,50)

Step 3 - STEP020: runs IDCAMS (IBM utility)

  • Copies AWS.M2.CARDDEMO.TRXFL.SEQ into AWS.M2.CARDDEMO.TRXFL.VSAM.KSDS
  • Reads: AWS.M2.CARDDEMO.TRXFL.SEQ (DD INFILE)
  • Writes: AWS.M2.CARDDEMO.TRXFL.VSAM.KSDS (DD OUTFILE)
  • Control statements: REPRO INFILE(INFILE) OUTFILE(OUTFILE)

Step 4 - STEP030: runs IEFBR14 (IBM utility)

  • Comment: DELETE TRANSACTION REPORTS FROM PREVIOUS RUN
  • Deletes: AWS.M2.CARDDEMO.STATEMNT.HTML (DD HTMLFILE), AWS.M2.CARDDEMO.STATEMNT.PS (DD STMTFILE)

Step 5 - STEP040: runs CBSTM03A

  • Comment: PRODUCING REPORT IN TEXT AND HTML - DEMONSTRATES CALLED SUBROUTINE
  • What CBSTM03A does: CBSTM03A prints the customer statements: for every card in the cross-reference it writes a statement with the customer's name and address, the account ID, current balance, and FICO score, followed by the card's transactions and their total - once as an 80-column text file and once as HTML. It reads its input files through the CBSTM03B subroutine. By its own comments, it was also written to exercise modernization tooling: it reads z/OS control blocks, uses ALTER and GO TO, COMP and COMP-3 fields, a two-dimensional table, and a subroutine call.
  • Reads: AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS (DD ACCTFILE), AWS.M2.CARDDEMO.CARDXREF.VSAM.KSDS (DD XREFFILE), AWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDS (DD CUSTFILE), AWS.M2.CARDDEMO.TRXFL.VSAM.KSDS (DD TRNXFILE)
  • Creates: AWS.M2.CARDDEMO.STATEMNT.HTML (DD HTMLFILE), AWS.M2.CARDDEMO.STATEMNT.PS (DD STMTFILE)

Inputs from outside the job: AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS, AWS.M2.CARDDEMO.CARDXREF.VSAM.KSDS, AWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDS, AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS Outputs it leaves behind: AWS.M2.CARDDEMO.STATEMNT.HTML, AWS.M2.CARDDEMO.STATEMNT.PS

Program CBSTM03A

CBSTM03A prints the customer statements: for every card in the cross-reference it writes a statement with the customer's name and address, the account ID, current balance, and FICO score, followed by the card's transactions and their total - once as an 80-column text file and once as HTML. It reads its input files through the CBSTM03B subroutine. By its own comments, it was also written to exercise modernization tooling: it reads z/OS control blocks, uses ALTER and GO TO, COMP and COMP-3 fields, a two-dimensional table, and a subroutine call.

Inputs
  • Transactions sorted by card (DD TRNXFILE, AWS.M2.CARDDEMO.TRXFL.VSAM.KSDS, layout TRNX-RECORD in COSTM01: card number + transaction ID as the key, then the transaction details) - read once, entirely into memory.
  • Card cross-reference (DD XREFFILE) - read in card-number order; drives one statement per card.
  • Customers (DD CUSTFILE, CUSTREC) - name, address, FICO score, read by the customer ID on the cross-reference.
  • Accounts (DD ACCTFILE, CVACT01Y) - account ID and current balance, read by the account ID on the cross-reference.
Outputs
  • Text statements (DD STMTFILE, AWS.M2.CARDDEMO.STATEMNT.PS, 80-byte lines): "START OF STATEMENT", name and three address lines, Basic Details (account ID, current balance, FICO score), a Transaction Summary with one line per transaction (ID, description, amount), "Total EXP", and "END OF STATEMENT".
  • HTML statements (DD HTMLFILE, AWS.M2.CARDDEMO.STATEMNT.HTML, 100-byte lines) - the same content as HTML.
  • SYSOUT: the job and step name and the DD names allocated to the step, read from z/OS control blocks.
Processing
  1. Displays the running job, step, and the DD names allocated to it by walking the z/OS control blocks (PSA, TCB, TIOT) through pointers (start of the procedure division).
  2. Opens the two output files and, through a chain of ALTERed GO TOs, opens each input file in turn via CBSTM03B (0000-START, 8100-FILE-OPEN to 8400-ACCTFILE-OPEN).
  3. Reads the whole sorted transaction file into a table of up to 51 cards x 10 transactions per card (8500-READTRNX-READ, 8599-EXIT).
  4. For each cross-reference record (1000-MAINLINE, 1000-XREFFILE-GET-NEXT): reads the customer and account (2000-CUSTFILE-GET, 3000-ACCTFILE-GET), writes the statement header in both formats (5000-CREATE-STATEMENT, 5100-WRITE-HTML-HEADER, 5200-WRITE-HTML-NMADBS), then finds the card in the table and writes each of its transactions, adding up the total (4000-TRNXFILE-GET, 6000-WRITE-TRANS), and writes the total and the statement trailer.
  5. Closes all files at the end of the cross-reference (9100- to 9400- close paragraphs).
Business rules
  • One statement per card, not per account or customer: a customer with two cards gets two statements, each showing the same account balance.
  • Statement total ("Total EXP") = the sum of TRNX-AMT for the card's transactions.
  • Which transactions: every transaction for the card in the input file - there's no statement period or date selection in the program.
  • Name and address: first, middle, and last name joined with single spaces; address line 3, state, country, and ZIP joined on one line.
  • Errors: any file error, a customer or account record that can't be found, or an empty transaction file stops the run with an abend (9999-ABEND-PROGRAM, CEE3ABD).
Notes for modernization
  • Fixed in-memory limits with no checks: the transaction table holds 51 cards and 10 transactions per card. More cards or transactions than that overwrite other storage instead of failing cleanly - the program only works for demo-sized data. A modern version would read transactions per card on demand (a query by card) instead of loading them all.
  • z/OS-only code: reading the PSA, TCB, and TIOT control blocks to list DD names has no equivalent off the mainframe; it's diagnostic only and can be dropped.
  • ALTER and GO TO: the file-opening sequence is a self-modifying jump chain; rewrite it as straight-line opens.
  • No statement period: statements list all transactions on file. Real statements need a cycle (from-to dates), which the job and program don't have - a gap to raise with the business.
  • The HTML is assembled line by line from fixed text; a templating tool replaces most of this program.
  • Depends on the cross-reference and the transaction file both being in card-number order; the matching stops looking once the table passes the current card.
Program CBSTM03B

CBSTM03B is a file-access subroutine for the statement program (CBSTM03A): it opens, reads, and closes the four files the statements are built from - the card-sorted transaction file, the card cross-reference, customers, and accounts - on request, and hands back the record and the file status. It holds no business logic.

Inputs
  • Request area from the caller (LK-M03B-AREA): which file (the DD name), the operation (O open, C close, R read next, K read by key), and for keyed reads the key and its length.
  • Transaction file sorted by card (DD TRNXFILE, AWS.M2.CARDDEMO.TRXFL.VSAM.KSDS) - read in key order (card number, then transaction ID).
  • Card cross-reference (DD XREFFILE) - read in key order.
  • Customers (DD CUSTFILE) and accounts (DD ACCTFILE) - read by key.
Outputs
  • The record read, returned in LK-M03B-FLDT (up to 1,000 bytes), and the two-character file status in LK-M03B-RC.
Processing
  1. Routes the request by DD name to the paragraph for that file (0000-START); an unknown DD name returns without doing anything.
  2. For the transaction and cross-reference files: open for input, read the next record, or close (1000-TRNXFILE-PROC, 2000-XREFFILE-PROC).
  3. For the customer and account files: open for input, read the record with the given key, or close (3000-CUSTFILE-PROC, 4000-ACCTFILE-PROC).
  4. Returns the file status to the caller, which decides what to do with it.
Business rules
  • None - error handling is left to the caller: the subroutine reports the file status and never stops the run itself.
  • Write (W) and rewrite (Z) operations are defined in the request area but not implemented for any file.
Notes for modernization
  • A hand-written data-access layer: on a modern platform this becomes ordinary database queries or a repository class, and the subroutine goes away.
  • Unsupported combinations (for example a keyed read on the transaction file, or any write) silently do nothing and return the previous status - callers must not rely on them.
  • Uses GO TO between paragraphs for control flow; straightforward to restructure.

Job CUSTFILE

Refactor suggested - Only IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.

1
jobs
5
steps
2
system programs
2
datasets
48
lines of source
InputsStepsOutputsdeletedeletedefinedefineAWS.M2.CARDDEMO.CUSTDATA.PSAWS.M2.CARDDEMO.CUSTDATA.PSCLCIFIL: SDSFCLCIFIL: SDSFSTEP05: IDCAMSSTEP05: IDCAMSSTEP10: IDCAMSSTEP10: IDCAMSSTEP15: IDCAMSSTEP15: IDCAMSOPCIFIL: SDSFOPCIFIL: SDSFAWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDSAWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDS

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Job CUSTFILE

Step 1 - CLCIFIL: runs SDSF (IBM utility)

  • Comment: Close files in CICS region

Step 2 - STEP05: runs IDCAMS (IBM utility)

  • Comment: DELETE CUSTOMER VSAM FILE IF ONE ALREADY EXISTS
  • Deletes: AWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDS
  • Control statements: DELETE AWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDS CLUSTER IF MAXCC LE 08 THEN SET MAXCC = 0

Step 3 - STEP10: runs IDCAMS (IBM utility)

  • Comment: DEFINE CUSTOMER VSAM FILE
  • Defines: AWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDS
  • Control statements: DEFINE CLUSTER (NAME(AWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDS) CYLINDERS(1 5) VOLUMES(AWSHJ1 ) KEYS(9 0) RECORDSIZE(500 500) SHAREOPTIONS(2 3) ERASE

Step 4 - STEP15: runs IDCAMS (IBM utility)

  • Comment: COPY DATA FROM FLAT FILE TO VSAM FILE
  • Copies AWS.M2.CARDDEMO.CUSTDATA.PS into AWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDS
  • Reads: AWS.M2.CARDDEMO.CUSTDATA.PS (DD CUSTDATA)
  • Writes: AWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDS (DD CUSTVSAM)
  • Control statements: REPRO INFILE(CUSTDATA) OUTFILE(CUSTVSAM)

Step 5 - OPCIFIL: runs SDSF (IBM utility)

  • Comment: Open files in CICS region

Inputs from outside the job: AWS.M2.CARDDEMO.CUSTDATA.PS Outputs it leaves behind: AWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDS

Job DALYREJS

Retire suggested - Only IBM utilities that define and delete data sets - housekeeping a database-backed platform doesn't need.

1
jobs
1
steps
1
system programs
1
datasets
10
lines of source
InputsStepsOutputsdefinedefineSTEP05: IDCAMSSTEP05: IDCAMSAWS.M2.CARDDEMO.DALYREJSAWS.M2.CARDDEMO.DALYREJS

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Job DALYREJS

Step 1 - STEP05: runs IDCAMS (IBM utility)

  • Comment: DELETE TRANSACATION MASTER VSAM FILE IF ONE ALREADY EXISTS
  • Defines: AWS.M2.CARDDEMO.DALYREJS
  • Control statements: DEFINE GENERATIONDATAGROUP (NAME(AWS.M2.CARDDEMO.DALYREJS) LIMIT(5) SCRATCH )

Inputs from outside the job: none Outputs it leaves behind: none

Job DBPAUTP0

Refactor suggested - Only IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.

1
jobs
2
steps
2
system programs
3
datasets
32
lines of source
InputsStepsOutputsdeletedeletedeletedeleteOEM.IMS.IMSP.PAUTHDBOEM.IMS.IMSP.PAUTHDBOEM.IMS.IMSP.PAUTHDBXOEM.IMS.IMSP.PAUTHDBXSTEPDEL: IEFBR14STEPDEL: IEFBR14UNLOAD: DFSRRC00UNLOAD: DFSRRC00AWS.M2.CARDDEMO.IMSDATA.DBPAUTP0AWS.M2.CARDDEMO.IMSDATA.DBPAUTP0

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Job DBPAUTP0

Step 1 - STEPDEL: runs IEFBR14 (IBM utility)

  • Comment: DELETE OUTPUT DATASET
  • Deletes: AWS.M2.CARDDEMO.IMSDATA.DBPAUTP0 (DD SYSUT1)

Step 2 - UNLOAD: runs DFSRRC00

  • Comment: DOWNLOAD DBD DBPAUTP0
  • Deletes: AWS.M2.CARDDEMO.IMSDATA.DBPAUTP0 (DD DFSURGU1)
  • Uses: OEM.IMS.IMSP.PAUTHDB (DD DDPAUTP0), OEM.IMS.IMSP.PAUTHDBX (DD DDPAUTX0)

Inputs from outside the job: none Outputs it leaves behind: none

Job DEFCUST

Retire suggested - Only IBM utilities that define and delete data sets - housekeeping a database-backed platform doesn't need.

1
jobs
1
steps
1
system programs
2
datasets
24
lines of source
InputsStepsOutputsdeletedeletedefinedefinedeletedeletedefinedefineSTEP05: IDCAMSSTEP05: IDCAMSAWS.CCDA.CUSTDATA.CLUSTERAWS.CCDA.CUSTDATA.CLUSTERAWS.CUSTDATA.CLUSTERAWS.CUSTDATA.CLUSTER

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Job DEFCUST

Step 1 - STEP05: runs IDCAMS (IBM utility)

  • Comment: DELETE CUSTOMER VSAM FILE IF ONE ALREADY EXISTS
  • Defines: AWS.CUSTDATA.CLUSTER
  • Deletes: AWS.CCDA.CUSTDATA.CLUSTER
  • Control statements: DELETE AWS.CCDA.CUSTDATA.CLUSTER CLUSTER

Step 2 - STEP05: runs IDCAMS (IBM utility)

  • Comment: DELETE CUSTOMER VSAM FILE IF ONE ALREADY EXISTS
  • Defines: AWS.CUSTDATA.CLUSTER
  • Deletes: AWS.CCDA.CUSTDATA.CLUSTER
  • Control statements: DEFINE CLUSTER (NAME(AWS.CUSTDATA.CLUSTER) CYLINDERS(1 5) KEYS(10 0) RECORDSIZE(500 500) SHAREOPTIONS(1 4) ERASE INDEXED )

Inputs from outside the job: none Outputs it leaves behind: none

Job DEFGDGB

Retire suggested - Only IBM utilities that define and delete data sets - housekeeping a database-backed platform doesn't need.

1
jobs
1
steps
1
system programs
6
datasets
41
lines of source
InputsStepsOutputsdefinedefinedefinedefinedefinedefinedefinedefinedefinedefinedefinedefineSTEP05: IDCAMSSTEP05: IDCAMSAWS.M2.CARDDEMO.SYSTRANAWS.M2.CARDDEMO.SYSTRANAWS.M2.CARDDEMO.TCATBALF.BKUPAWS.M2.CARDDEMO.TCATBALF.BKUPAWS.M2.CARDDEMO.TRANREPTAWS.M2.CARDDEMO.TRANREPTAWS.M2.CARDDEMO.TRANSACT.BKUPAWS.M2.CARDDEMO.TRANSACT.BKUPAWS.M2.CARDDEMO.TRANSACT.COMBINEDAWS.M2.CARDDEMO.TRANSACT.COMBINEDAWS.M2.CARDDEMO.TRANSACT.DALYAWS.M2.CARDDEMO.TRANSACT.DALY

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Job DEFGDGB

Step 1 - STEP05: runs IDCAMS (IBM utility)

  • Comment: DEFINE GDG BASES NEEDED BY CARDDEMO PROJECT
  • Defines: AWS.M2.CARDDEMO.SYSTRAN, AWS.M2.CARDDEMO.TCATBALF.BKUP, AWS.M2.CARDDEMO.TRANREPT, AWS.M2.CARDDEMO.TRANSACT.BKUP, AWS.M2.CARDDEMO.TRANSACT.COMBINED, AWS.M2.CARDDEMO.TRANSACT.DALY
  • Control statements: DEFINE GENERATIONDATAGROUP (NAME(AWS.M2.CARDDEMO.TRANSACT.BKUP) LIMIT(5) SCRATCH ) IF LASTCC=12 THEN SET MAXCC=0 DEFINE GENERATIONDATAGROUP (NAME(AWS.M2.CARDDEMO.TRANSACT.DALY)

Inputs from outside the job: none Outputs it leaves behind: none

Job DEFGDGD

Refactor suggested - Only IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.

1
jobs
6
steps
2
system programs
6
datasets
52
lines of source
InputsStepsOutputsdefinedefinedefinedefinedefinedefineAWS.M2.CARDDEMO.TRANTYPE.PSAWS.M2.CARDDEMO.TRANTYPE.PSAWS.M2.CARDDEMO.TRANCATG.PSAWS.M2.CARDDEMO.TRANCATG.PSAWS.M2.CARDDEMO.DISCGRP.PSAWS.M2.CARDDEMO.DISCGRP.PSSTEP10: IDCAMSSTEP10: IDCAMSSTEP20: IEBGENERSTEP20: IEBGENERSTEP30: IDCAMSSTEP30: IDCAMSSTEP40: IEBGENERSTEP40: IEBGENERSTEP50: IDCAMSSTEP50: IDCAMSSTEP60: IEBGENERSTEP60: IEBGENERAWS.M2.CARDDEMO.TRANTYPE.BKUPAWS.M2.CARDDEMO.TRANTYPE.BKUPAWS.M2.CARDDEMO.TRANCATG.PS.BKUPAWS.M2.CARDDEMO.TRANCATG.PS.BKUPAWS.M2.CARDDEMO.DISCGRP.BKUPAWS.M2.CARDDEMO.DISCGRP.BKUP

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Job DEFGDGD

Step 1 - STEP10: runs IDCAMS (IBM utility)

  • Comment: RESTART=STEP30 / This jcl will create GDGs and load first generation for / Transaction reference data / Define GDG for Transaction Type
  • Defines: AWS.M2.CARDDEMO.TRANTYPE.BKUP
  • Control statements: DEFINE GENERATIONDATAGROUP (NAME(AWS.M2.CARDDEMO.TRANTYPE.BKUP) LIMIT(5) SCRATCH )

Step 2 - STEP20: runs IEBGENER (IBM utility)

  • Comment: Create the first generation of GDG Transaction Type
  • Copies AWS.M2.CARDDEMO.TRANTYPE.PS into AWS.M2.CARDDEMO.TRANTYPE.BKUP
  • Reads: AWS.M2.CARDDEMO.TRANTYPE.PS (DD SYSUT1)
  • Creates: AWS.M2.CARDDEMO.TRANTYPE.BKUP (DD SYSUT2)

Step 3 - STEP30: runs IDCAMS (IBM utility)

  • Comment: Transaction Category type
  • Defines: AWS.M2.CARDDEMO.TRANCATG.PS.BKUP
  • Control statements: DEFINE GENERATIONDATAGROUP (NAME(AWS.M2.CARDDEMO.TRANCATG.PS.BKUP) LIMIT(5) SCRATCH )

Step 4 - STEP40: runs IEBGENER (IBM utility)

  • Comment: Create the first generation of GDG Transaction Category Type
  • Copies AWS.M2.CARDDEMO.TRANCATG.PS into AWS.M2.CARDDEMO.TRANCATG.PS.BKUP
  • Reads: AWS.M2.CARDDEMO.TRANCATG.PS (DD SYSUT1)
  • Creates: AWS.M2.CARDDEMO.TRANCATG.PS.BKUP (DD SYSUT2)

Step 5 - STEP50: runs IDCAMS (IBM utility)

  • Comment: Disclosure Group
  • Defines: AWS.M2.CARDDEMO.DISCGRP.BKUP
  • Control statements: DEFINE GENERATIONDATAGROUP (NAME(AWS.M2.CARDDEMO.DISCGRP.BKUP) LIMIT(5) SCRATCH )

Step 6 - STEP60: runs IEBGENER (IBM utility)

  • Comment: Create the first generation of GDG disclosure group
  • Copies AWS.M2.CARDDEMO.DISCGRP.PS into AWS.M2.CARDDEMO.DISCGRP.BKUP
  • Reads: AWS.M2.CARDDEMO.DISCGRP.PS (DD SYSUT1)
  • Creates: AWS.M2.CARDDEMO.DISCGRP.BKUP (DD SYSUT2)

Inputs from outside the job: AWS.M2.CARDDEMO.DISCGRP.PS, AWS.M2.CARDDEMO.TRANCATG.PS, AWS.M2.CARDDEMO.TRANTYPE.PS Outputs it leaves behind: AWS.M2.CARDDEMO.DISCGRP.BKUP, AWS.M2.CARDDEMO.TRANCATG.PS.BKUP, AWS.M2.CARDDEMO.TRANTYPE.BKUP

Job DISCGRP

Refactor suggested - Only IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.

1
jobs
3
steps
1
system programs
2
datasets
36
lines of source
InputsStepsOutputsdeletedeletedefinedefineAWS.M2.CARDDEMO.DISCGRP.PSAWS.M2.CARDDEMO.DISCGRP.PSSTEP05: IDCAMSSTEP05: IDCAMSSTEP10: IDCAMSSTEP10: IDCAMSSTEP15: IDCAMSSTEP15: IDCAMSAWS.M2.CARDDEMO.DISCGRP.VSAM.KSDSAWS.M2.CARDDEMO.DISCGRP.VSAM.KSDS

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Job DISCGRP

Step 1 - STEP05: runs IDCAMS (IBM utility)

  • Comment: DELETE DISCLOSURE GROUP VSAM FILE IF ONE ALREADY EXISTS
  • Deletes: AWS.M2.CARDDEMO.DISCGRP.VSAM.KSDS
  • Control statements: DELETE AWS.M2.CARDDEMO.DISCGRP.VSAM.KSDS CLUSTER SET MAXCC = 0

Step 2 - STEP10: runs IDCAMS (IBM utility)

  • Comment: DEFINE DISCLOSURE GROUP VSAM FILE
  • Defines: AWS.M2.CARDDEMO.DISCGRP.VSAM.KSDS
  • Control statements: DEFINE CLUSTER (NAME(AWS.M2.CARDDEMO.DISCGRP.VSAM.KSDS) CYLINDERS(1 5) VOLUMES(AWSHJ1 ) KEYS(16 0) RECORDSIZE(50 50) SHAREOPTIONS(2 3) ERASE

Step 3 - STEP15: runs IDCAMS (IBM utility)

  • Comment: COPY DATA FROM FLAT FILE TO VSAM FILE
  • Copies AWS.M2.CARDDEMO.DISCGRP.PS into AWS.M2.CARDDEMO.DISCGRP.VSAM.KSDS
  • Reads: AWS.M2.CARDDEMO.DISCGRP.PS (DD DISCGRP)
  • Writes: AWS.M2.CARDDEMO.DISCGRP.VSAM.KSDS (DD DISCVSAM)
  • Control statements: REPRO INFILE(DISCGRP) OUTFILE(DISCVSAM)

Inputs from outside the job: AWS.M2.CARDDEMO.DISCGRP.PS Outputs it leaves behind: AWS.M2.CARDDEMO.DISCGRP.VSAM.KSDS

Job DUSRSECJ

Refactor suggested - Only IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.

1
jobs
4
steps
3
system programs
2
datasets
48
lines of source
InputsStepsOutputsdeletedeletedeletedeletedefinedefineAWS.M2.CARDDEMO.USRSEC.PSAWS.M2.CARDDEMO.USRSEC.PSPREDEL: IEFBR14PREDEL: IEFBR14STEP01: IEBGENERSTEP01: IEBGENERSTEP02: IDCAMSSTEP02: IDCAMSSTEP03: IDCAMSSTEP03: IDCAMSAWS.M2.CARDDEMO.USRSEC.PSAWS.M2.CARDDEMO.USRSEC.PSAWS.M2.CARDDEMO.USRSEC.VSAM.KSDSAWS.M2.CARDDEMO.USRSEC.VSAM.KSDS

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Job DUSRSECJ

Step 1 - PREDEL: runs IEFBR14 (IBM utility)

  • Comment: PRE DELETE STEP
  • Deletes: AWS.M2.CARDDEMO.USRSEC.PS (DD DD01)

Step 2 - STEP01: runs IEBGENER (IBM utility)

  • Comment: CREATE USER SECURITY FILE (PS) FROM IN-STREAM DATA
  • Copies (in-stream SYSUT1) into AWS.M2.CARDDEMO.USRSEC.PS
  • Creates: AWS.M2.CARDDEMO.USRSEC.PS (DD SYSUT2)

Step 3 - STEP02: runs IDCAMS (IBM utility)

  • Comment: DEFINE VSAM FILE FOR USER SECURITY
  • Defines: AWS.M2.CARDDEMO.USRSEC.VSAM.KSDS
  • Deletes: AWS.M2.CARDDEMO.USRSEC.VSAM.KSDS
  • Control statements: DELETE AWS.M2.CARDDEMO.USRSEC.VSAM.KSDS SET MAXCC = 0 DEFINE CLUSTER (NAME(AWS.M2.CARDDEMO.USRSEC.VSAM.KSDS) KEYS(8,0) RECORDSIZE(80,80) REUSE INDEXED TRACKS(45,15)

Step 4 - STEP03: runs IDCAMS (IBM utility)

  • Comment: COPY USER SECURITY DATA FROM PS TO VSAM FILE
  • Copies AWS.M2.CARDDEMO.USRSEC.PS into AWS.M2.CARDDEMO.USRSEC.VSAM.KSDS
  • Reads: AWS.M2.CARDDEMO.USRSEC.PS (DD IN)
  • Writes: AWS.M2.CARDDEMO.USRSEC.VSAM.KSDS (DD OUT)
  • Control statements: REPRO INFILE(IN) OUTFILE(OUT)

Inputs from outside the job: none Outputs it leaves behind: AWS.M2.CARDDEMO.USRSEC.VSAM.KSDS

Job ESDSRRDS

Refactor suggested - Only IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.

1
jobs
6
steps
3
system programs
3
datasets
68
lines of source
InputsStepsOutputsdeletedeletedeletedeletedefinedefinedeletedeletedefinedefineAWS.M2.CARDDEMO.ESDSRRDS.PSAWS.M2.CARDDEMO.ESDSRRDS.PSPREDEL: IEFBR14PREDEL: IEFBR14STEP01: IEBGENERSTEP01: IEBGENERSTEP02: IDCAMSSTEP02: IDCAMSSTEP03: IDCAMSSTEP03: IDCAMSSTEP04: IDCAMSSTEP04: IDCAMSSTEP05: IDCAMSSTEP05: IDCAMSAWS.M2.CARDDEMO.ESDSRRDS.PSAWS.M2.CARDDEMO.ESDSRRDS.PSAWS.M2.CARDDEMO.USRSEC.VSAM.ESDSAWS.M2.CARDDEMO.USRSEC.VSAM.ESDSAWS.M2.CARDDEMO.USRSEC.VSAM.RRDSAWS.M2.CARDDEMO.USRSEC.VSAM.RRDS

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Job ESDSRRDS

Step 1 - PREDEL: runs IEFBR14 (IBM utility)

  • Comment: PRE DELETE STEP
  • Deletes: AWS.M2.CARDDEMO.ESDSRRDS.PS (DD DD01)

Step 2 - STEP01: runs IEBGENER (IBM utility)

  • Comment: CREATE USER SECURITY FILE (PS) FROM IN-STREAM DATA
  • Copies (in-stream SYSUT1) into AWS.M2.CARDDEMO.ESDSRRDS.PS
  • Creates: AWS.M2.CARDDEMO.ESDSRRDS.PS (DD SYSUT2)

Step 3 - STEP02: runs IDCAMS (IBM utility)

  • Comment: DEFINE VSAM FILE FOR USER SECURITY (ESDS)
  • Defines: AWS.M2.CARDDEMO.USRSEC.VSAM.ESDS
  • Deletes: AWS.M2.CARDDEMO.USRSEC.VSAM.ESDS
  • Control statements: DELETE AWS.M2.CARDDEMO.USRSEC.VSAM.ESDS SET MAXCC = 0 DEFINE CLUSTER (NAME(AWS.M2.CARDDEMO.USRSEC.VSAM.ESDS) RECORDSIZE(80,80) REUSE NONINDEXED TRACKS(45,15) FREESPACE(10,15)

Step 4 - STEP03: runs IDCAMS (IBM utility)

  • Comment: COPY USER SECURITY DATA FROM PS TO VSAM FILE(ESDS)
  • Copies AWS.M2.CARDDEMO.ESDSRRDS.PS into AWS.M2.CARDDEMO.USRSEC.VSAM.ESDS
  • Reads: AWS.M2.CARDDEMO.ESDSRRDS.PS (DD IN)
  • Writes: AWS.M2.CARDDEMO.USRSEC.VSAM.ESDS (DD OUT)
  • Control statements: REPRO INFILE(IN) OUTFILE(OUT)

Step 5 - STEP04: runs IDCAMS (IBM utility)

  • Comment: DEFINE VSAM FILE FOR USER SECURITY (RRDS)
  • Defines: AWS.M2.CARDDEMO.USRSEC.VSAM.RRDS
  • Deletes: AWS.M2.CARDDEMO.USRSEC.VSAM.RRDS
  • Control statements: DELETE AWS.M2.CARDDEMO.USRSEC.VSAM.RRDS SET MAXCC = 0 DEFINE CLUSTER (NAME(AWS.M2.CARDDEMO.USRSEC.VSAM.RRDS) RECORDSIZE(80,80) REUSE NUMBERED TRACKS(45,15) FREESPACE(10,15)

Step 6 - STEP05: runs IDCAMS (IBM utility)

  • Comment: COPY USER SECURITY DATA FROM PS TO VSAM FILE(ESDS)
  • Copies AWS.M2.CARDDEMO.ESDSRRDS.PS into AWS.M2.CARDDEMO.USRSEC.VSAM.RRDS
  • Reads: AWS.M2.CARDDEMO.ESDSRRDS.PS (DD IN)
  • Writes: AWS.M2.CARDDEMO.USRSEC.VSAM.RRDS (DD OUT)
  • Control statements: REPRO INFILE(IN) OUTFILE(OUT)

Inputs from outside the job: none Outputs it leaves behind: AWS.M2.CARDDEMO.USRSEC.VSAM.ESDS, AWS.M2.CARDDEMO.USRSEC.VSAM.RRDS

Job FTPJCL

Refactor suggested - Only IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.

1
jobs
1
steps
1
system programs
13
lines of source
InputsStepsOutputsSTEP1: FTPSTEP1: FTP

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Job FTPJCL

Step 1 - STEP1: runs FTP (IBM utility)

  • Comment: FTP JOB TO RECEIVE A FILE / MY.FTP.SERVER.COM IS THE FTP SERVER NAME(SUBJECT TO CHANGE FOR SITE) / USER ID - EITHER SCHEDULER ID OR TSO USER ID / PASSWORD OF THE USER / FOLDER TO FTP THE MAINFRAME FILE / PUT COMMAND FOR SENDING MAINFRAME FILE TO TXT / CHANGE THE PUT COMMAND TO GET TO RECEIVE FILE INTO MAINFRAME

Inputs from outside the job: none Outputs it leaves behind: none

Job INTCALC

Refactor suggested - 1 program(s), 622 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
10
record layouts
622
lines of source
InputsStepsOutputsupdateupdateAWS.M2.CARDDEMO.CARDXREF.VSAM.AIX.PATHAWS.M2.CARDDEMO.CARDXREF.VSAM.AIX.PATHAWS.M2.CARDDEMO.CARDXREF.VSAM.KSDSAWS.M2.CARDDEMO.CARDXREF.VSAM.KSDSAWS.M2.CARDDEMO.DISCGRP.VSAM.KSDSAWS.M2.CARDDEMO.DISCGRP.VSAM.KSDSAWS.M2.CARDDEMO.TCATBALF.VSAM.KSDSAWS.M2.CARDDEMO.TCATBALF.VSAM.KSDSSTEP15: CBACT04CSTEP15: CBACT04CAWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDSAWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDSAWS.M2.CARDDEMO.SYSTRANAWS.M2.CARDDEMO.SYSTRAN

What it does

INTCALC is the monthly interest run. For every account it charges interest on the account's balance in each transaction category, at the annual rate set for the account's disclosure group (or the default group), and writes each charge as a system-generated interest transaction. It adds the account's total interest to its current balance and resets the account's current-cycle credit and debit totals, closing the billing cycle. The interest transactions go to a new file; a later job (COMBTRAN) loads them into the transaction master.

Step by step
  1. Calculate interest (STEP15, CBACT04C, with the run date as its PARM). Reads the category balances in account order. For each account it reads the account and a card number from the cross-reference; for each of the account's categories it looks up the annual rate for the account's group, transaction type, and category (falling back to the DEFAULT group) and, if the rate isn't zero, computes a month's interest (balance x rate / 1200) and writes an interest transaction - type 01, category 05, source "System", ID made of the run date and a sequence number. When it moves on to the next account, it adds the interest total to the previous account's current balance and sets its cycle credit and debit totals to zero.
What it needs
  • The category balances built up by daily posting (POSTTRAN, TCATBALF.VSAM.KSDS), the account master, the card cross-reference, and the disclosure group rates (DISCGRP.VSAM.KSDS), including DEFAULT group rates.
  • The run date, coded in the JCL as PARM='2022071800' - it has to be changed for every run, or every month's interest transactions get IDs starting with the same date.
  • To run after the month's posting is complete.
What it produces
  • AWS.M2.CARDDEMO.SYSTRAN(+1), a new generation of interest transactions, which COMBTRAN sorts together with the transaction master's backup and loads into the master.
  • Updated account balances (interest added) and reset cycle totals - seen by the next statements (CREASTMT) and the online account screens.
Notes for modernization
  • The last account in the file is never updated: its interest transactions are written but the interest isn't added to its balance and its cycle isn't reset (a loop branch the program can't reach) - the transactions and balances disagree for that account every month.
  • Interest is charged on running totals that nothing resets: the category balances are only ever added to by posting; neither this job nor the posting job clears them after interest is charged, so each month's interest is calculated on all activity to date, not the month's balance. Confirm with the business how the balance subject to interest should be defined - this is a likely defect, not just a modernization detail.
  • Hard-coded run date in the JCL; on a modern scheduler this is the business date passed in automatically.
  • Fees are a placeholder in the program (not implemented).
  • Interest posting is split across three jobs (INTCALC writes, COMBTRAN merges and reloads the master); a modern design would post the interest directly, in the same database transaction as the balance update.
Step-by-step walkthrough from the source
Job INTCALC

Step 1 - STEP15: runs CBACT04C

  • Comment: Process transaction balance file and compute interest and fees.
  • What CBACT04C does: CBACT04C calculates the monthly interest on every account. For each account's balance in each transaction category it looks up the annual interest rate for the account's disclosure group, works out a month's interest, writes it as a system-generated interest transaction, adds the account's total interest to its current balance, and resets the account's current-cycle credit and debit totals to zero - closing the billing cycle.
  • Reads: AWS.M2.CARDDEMO.CARDXREF.VSAM.KSDS (DD XREFFILE), AWS.M2.CARDDEMO.DISCGRP.VSAM.KSDS (DD DISCGRP), AWS.M2.CARDDEMO.TCATBALF.VSAM.KSDS (DD TCATBALF)
  • Updates: AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS (DD ACCTFILE)
  • Creates: AWS.M2.CARDDEMO.SYSTRAN (DD TRANSACT)
  • Uses: AWS.M2.CARDDEMO.CARDXREF.VSAM.AIX.PATH (DD XREFFIL1)

Inputs from outside the job: AWS.M2.CARDDEMO.CARDXREF.VSAM.KSDS, AWS.M2.CARDDEMO.DISCGRP.VSAM.KSDS, AWS.M2.CARDDEMO.TCATBALF.VSAM.KSDS Outputs it leaves behind: AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS, AWS.M2.CARDDEMO.SYSTRAN

Program CBACT04C

CBACT04C calculates the monthly interest on every account. For each account's balance in each transaction category it looks up the annual interest rate for the account's disclosure group, works out a month's interest, writes it as a system-generated interest transaction, adds the account's total interest to its current balance, and resets the account's current-cycle credit and debit totals to zero - closing the billing cycle.

Inputs
  • Transaction category balances (DD TCATBALF, VSAM, read in key order: account, type, category) - TRAN-CAT-BAL per account and category (CVTRA01Y), as built up by the posting job.
  • Account master (DD ACCTFILE, VSAM keyed by account ID) - the account's disclosure group (ACCT-GROUP-ID) and balances (CVACT01Y).
  • Card cross-reference (DD XREFFILE, VSAM, read by its alternate key, account ID) - a card number for the account (CVACT03Y).
  • Disclosure groups (DD DISCGRP, VSAM keyed by group + transaction type + category) - the annual interest rate DIS-INT-RATE (CVTRA02Y).
  • Run date - the PARM on the job step (PARM-DATE, 10 characters), used to number the interest transactions.
Outputs
  • Interest transactions (DD TRANSACT, AWS.M2.CARDDEMO.SYSTRAN, a new sequential file) - one TRAN-RECORD (CVTRA05Y) per account and category that earns interest: type 01, category 05, source "System", description "Int. for a/c <account>", amount = the month's interest, card number from the cross-reference, and both timestamps set to the time of the run.
  • Account master - updated in place: interest added to the current balance, cycle totals reset.
  • Every category balance record is DISPLAYed to SYSOUT.
Processing
  1. Opens the category balances, cross-reference, and disclosure groups for input, the account master for update, and the interest transaction file for output (0000- to 0400- open paragraphs).
  2. Reads the category balances in key order (1000-TCATBALF-GET-NEXT), so all of one account's categories come together.
  3. When the account changes, updates the previous account (1050-UPDATE-ACCOUNT), resets the interest total, and reads the new account and its cross-reference (1100-GET-ACCT-DATA, 1110-GET-XREF-DATA).
  4. For each category, looks up the interest rate for the account's group, transaction type, and category, falling back to the DEFAULT group when there's no specific rate (1200-GET-INTEREST-RATE, 1200-A-GET-DEFAULT-INT-RATE).
  5. If the rate isn't zero, computes the month's interest, adds it to the account's total, and writes an interest transaction (1300-COMPUTE-INTEREST, 1300-B-WRITE-TX). Fees are a placeholder (1400-COMPUTE-FEES, "To be implemented").
  6. Closes the files at end of file.
Business rules
  • Monthly interest = TRAN-CAT-BAL x DIS-INT-RATE / 1200 - the category balance times the annual percentage rate, divided by 12 months and 100.
  • Rate lookup: by account group (ACCT-GROUP-ID), transaction type, and category; if that combination isn't in the disclosure group file, the DEFAULT group's rate for the same type and category is used. A missing default rate stops the run.
  • Zero rate: categories with a zero rate get no interest and no transaction.
  • Account update: ACCT-CURR-BAL += total interest for the account; ACCT-CURR-CYC-CREDIT and ACCT-CURR-CYC-DEBIT are set to zero - this job also closes the cycle.
  • Interest transaction ID: the run date from the PARM followed by a 6-digit sequence number (WS-TRANID-SUFFIX), counted across the whole run.
  • Errors: an account or cross-reference record that can't be found, or any file error, stops the run with an abend (9999-ABEND-PROGRAM, CEE3ABD code 999).
Notes for modernization
  • The last account is never updated. The update for the final account sits in a branch the read loop can't reach (the loop ends as soon as end of file is set), so the last account in the category balance file gets neither its interest added to the balance nor its cycle totals reset - its interest transactions are written, though, so the transactions and the balance disagree.
  • Interest is charged on the category balance as it stands, including negative (credit) balances, which produce negative interest; confirm with the business whether credits should earn or be excluded.
  • Cycle close is a side effect of the interest run (resetting the cycle totals); a modern design would make the cycle close an explicit step.
  • Fees are not implemented (1400-COMPUTE-FEES is empty).
  • The account's card number comes from the first cross-reference record for the account; an account with several cards gets its interest transactions under one of them.
  • The interest transactions go to a separate file (SYSTRAN) rather than the transaction master; another job has to post or merge them - see the job flow.
  • The open-error message for the disclosure group file says "DALY REJECTS FILE" (copy-and-paste slip).

Job INTRDRJ1

Refactor suggested - Only IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.

1
jobs
2
steps
2
system programs
3
datasets
14
lines of source
InputsStepsOutputsAWS.M2.CARDEMO.FTP.TESTAWS.M2.CARDEMO.FTP.TESTAWS.M2.CARDDEMO.JCLAWS.M2.CARDDEMO.JCLIDCAMS: IDCAMSIDCAMS: IDCAMSSTEP01: IEBGENERSTEP01: IEBGENERAWS.M2.CARDEMO.FTP.TEST.BKUPAWS.M2.CARDEMO.FTP.TEST.BKUP

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Job INTRDRJ1

Step 1 - IDCAMS: runs IDCAMS (IBM utility)

  • Comment: THIS INTRDR JOB WILL TRIGGER ANOTHER JCL
  • Copies AWS.M2.CARDEMO.FTP.TEST into AWS.M2.CARDEMO.FTP.TEST.BKUP
  • Reads: AWS.M2.CARDEMO.FTP.TEST (DD IN)
  • Writes: AWS.M2.CARDEMO.FTP.TEST.BKUP (DD OUT)
  • Control statements: REPRO IFILE(IN) OFILE(OUT)

Step 2 - STEP01: runs IEBGENER (IBM utility)

  • Reads: AWS.M2.CARDDEMO.JCL (DD SYSUT1)

Inputs from outside the job: AWS.M2.CARDDEMO.JCL, AWS.M2.CARDEMO.FTP.TEST Outputs it leaves behind: AWS.M2.CARDEMO.FTP.TEST.BKUP

Job INTRDRJ2

Refactor suggested - Only IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.

1
jobs
1
steps
1
system programs
2
datasets
9
lines of source
InputsStepsOutputsAWS.M2.CARDEMO.FTP.TEST.BKUPAWS.M2.CARDEMO.FTP.TEST.BKUPIDCAMS: IDCAMSIDCAMS: IDCAMSAWS.M2.CARDEMO.FTP.TEST.BKUP.INTRDRAWS.M2.CARDEMO.FTP.TEST.BKUP.INTRDR

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Job INTRDRJ2

Step 1 - IDCAMS: runs IDCAMS (IBM utility)

  • Comment: THIS JOB IS TO CREATE PHYSICAL VSAM FILE FOR IMS DEMODB / AND INDEX DEMODX
  • Copies AWS.M2.CARDEMO.FTP.TEST.BKUP into AWS.M2.CARDEMO.FTP.TEST.BKUP.INTRDR
  • Reads: AWS.M2.CARDEMO.FTP.TEST.BKUP (DD IN)
  • Writes: AWS.M2.CARDEMO.FTP.TEST.BKUP.INTRDR (DD OUT)
  • Control statements: REPRO IFILE(IN) OFILE(OUT)

Inputs from outside the job: AWS.M2.CARDEMO.FTP.TEST.BKUP Outputs it leaves behind: AWS.M2.CARDEMO.FTP.TEST.BKUP.INTRDR

Job LOADPADB

Rehost suggested - Uses IMS databases; rehost first and plan the data migration separately.

1
jobs
1
steps
1
programs
1
system programs
4
copybooks
2
datasets
2
IMS segments
2
record layouts
340
lines of source
InputsStepsOutputsAWS.M2.CARDDEMO.PAUTDB.CHILD.FILEOAWS.M2.CARDDEMO.PAUTDB.CHILD.FILEOAWS.M2.CARDDEMO.PAUTDB.ROOT.FILEOAWS.M2.CARDDEMO.PAUTDB.ROOT.FILEOSTEP01: PAUDBLODSTEP01: PAUDBLOD

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Job LOADPADB

Step 1 - STEP01: runs PAUDBLOD, through DFSRRC00

  • Comment: YLIBS JCLLIB ORDER=VIPINGP.CNTL.PROCLIB / EXECUTE IMS PROGRAM
  • Reads: AWS.M2.CARDDEMO.PAUTDB.CHILD.FILEO (DD INFILE2), AWS.M2.CARDDEMO.PAUTDB.ROOT.FILEO (DD INFILE1)
  • Adds records to IMS segment PAUTDTL1
  • Adds records to and reads IMS segment PAUTSUM0

Inputs from outside the job: AWS.M2.CARDDEMO.PAUTDB.CHILD.FILEO, AWS.M2.CARDDEMO.PAUTDB.ROOT.FILEO Outputs it leaves behind: none

Job MNTTRDB2

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

1
jobs
1
steps
1
programs
1
DCLGENs
1
datasets
1
Db2 tables
2
record layouts
200
lines of source
InputsStepsOutputsINPFILEINPFILESTEP1: COBTUPDTSTEP1: COBTUPDT

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Job MNTTRDB2

From the job's comments: USE THIS JOB TO MAINTAIN DB2 TRANSACTION TABLE, INSERTING, / UPDATING OR REMOVING RECORDS IN BATCH. / INPFILE - THE INPUT FILE TO USE FOR UPDATES. THE ALLOWED VALUES / ARE: / COLUMN 1 - A - ADD / D - DELETE / U - UPDATE / COMMENT

Step 1 - STEP1: runs COBTUPDT, through IKJEFT01

  • Comment: USE THIS JOB TO MAINTAIN DB2 TRANSACTION TABLE, INSERTING, / UPDATING OR REMOVING RECORDS IN BATCH. / INPFILE - THE INPUT FILE TO USE FOR UPDATES. THE ALLOWED VALUES / ARE: / COLUMN 1 - A - ADD / D - DELETE / U - UPDATE / COMMENT / COLUMNS 2-3 - TRANSACTION TYPE. NUMERIC VALUE / COLUMNS 4-53 - TRANSACTION DESCRIPTION
  • COBTUPDT's comments: Program: COBTUPDT.CBL / Layer: Business logic / Function: Update Transaction type based on user input
  • Reads: INPFILE (DD INPFILE)
  • Adds records to and updates and deletes from Db2 table TRANSACTION_TYPE

Inputs from outside the job: INPFILE Outputs it leaves behind: none

Job OPENFIL

Refactor suggested - Only IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.

1
jobs
1
steps
1
system programs
12
lines of source
InputsStepsOutputsOPCIFIL: SDSFOPCIFIL: SDSF

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Job OPENFIL

Step 1 - OPCIFIL: runs SDSF (IBM utility)

  • Comment: Open files in CICS region

Inputs from outside the job: none Outputs it leaves behind: none

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.

Job PRTCATBL

Refactor suggested - Only IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.

1
jobs
1
PROCs
3
steps
3
system programs
1
control cards
3
datasets
63
lines of source
InputsStepsOutputsdeletedeleteAWS.M2.CARDDEMO.TCATBALF.VSAM.KSDSAWS.M2.CARDDEMO.TCATBALF.VSAM.KSDSAWS.M2.CARDDEMO.TCATBALF.BKUPAWS.M2.CARDDEMO.TCATBALF.BKUPDELDEF: IEFBR14DELDEF: IEFBR14STEP05R.PRC001: IDCAMSSTEP05R.PRC001: IDCAMSSTEP10R: SORTSTEP10R: SORTAWS.M2.CARDDEMO.TCATBALF.REPTAWS.M2.CARDDEMO.TCATBALF.REPTAWS.M2.CARDDEMO.TCATBALF.BKUPAWS.M2.CARDDEMO.TCATBALF.BKUP

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Job PRTCATBL

Step 1 - DELDEF: runs IEFBR14 (IBM utility)

  • Deletes: AWS.M2.CARDDEMO.TCATBALF.REPT (DD THEFILE)

Step 2 - STEP05R.PRC001 (in PROC REPROC): runs IDCAMS (IBM utility)

  • Comment: Unload the processed transaction category balance file / REPRO UTILITY TO LOAD OR UNLOAD VSAM FILE
  • Copies AWS.M2.CARDDEMO.TCATBALF.VSAM.KSDS into AWS.M2.CARDDEMO.TCATBALF.BKUP
  • Reads: AWS.M2.CARDDEMO.TCATBALF.VSAM.KSDS (DD FILEIN)
  • Creates: AWS.M2.CARDDEMO.TCATBALF.BKUP (DD FILEOUT)
  • Control statements: REPRO INFILE(FILEIN) OUTFILE(FILEOUT)
  • Reads control card REPROCT (DD SYSIN)

Step 3 - STEP10R: runs SORT (IBM utility)

  • Comment: Filter the TCATBALFions for a the parm date and sort by card num
  • Sorts AWS.M2.CARDDEMO.TCATBALF.BKUP into AWS.M2.CARDDEMO.TCATBALF.REPT
  • Reads: AWS.M2.CARDDEMO.TCATBALF.BKUP (DD SORTIN)
  • Creates: AWS.M2.CARDDEMO.TCATBALF.REPT (DD SORTOUT)
  • Sort keys: TRANCAT-ACCT-ID (ascending, positions 1-11), TRANCAT-TYPE-CD (ascending, positions 12-13), TRANCAT-CD (ascending, positions 14-17).
  • Reformats the records (INREC/OUTREC) - see the control statements.
  • Control statements: SORT FIELDS=(TRANCAT-ACCT-ID,A,TRANCAT-TYPE-CD,A,TRANCAT-CD,A) OUTREC FIELDS=(TRANCAT-ACCT-ID,X, TRANCAT-TYPE-CD,X, TRANCAT-CD,X, TRAN-CAT-BAL,EDIT=(TTTTTTTTT.TT),9X)

Inputs from outside the job: AWS.M2.CARDDEMO.TCATBALF.VSAM.KSDS Outputs it leaves behind: AWS.M2.CARDDEMO.TCATBALF.REPT

Job READACCT

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

1
jobs
2
steps
2
programs
2
system programs
2
copybooks
4
datasets
6
record layouts
497
lines of source
InputsStepsOutputsdeletedeletedeletedeletedeletedeleteAWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDSAWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDSPREDEL: IEFBR14PREDEL: IEFBR14STEP05: CBACT01CSTEP05: CBACT01CAWS.M2.CARDDEMO.ACCTDATA.ARRYPSAWS.M2.CARDDEMO.ACCTDATA.ARRYPSAWS.M2.CARDDEMO.ACCTDATA.PSCOMPAWS.M2.CARDDEMO.ACCTDATA.PSCOMPAWS.M2.CARDDEMO.ACCTDATA.VBPSAWS.M2.CARDDEMO.ACCTDATA.VBPS

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Job READACCT

Step 1 - PREDEL: runs IEFBR14 (IBM utility)

  • Comment: PRE DELETE STEP
  • Deletes: AWS.M2.CARDDEMO.ACCTDATA.ARRYPS (DD DD02), AWS.M2.CARDDEMO.ACCTDATA.PSCOMP (DD DD01), AWS.M2.CARDDEMO.ACCTDATA.VBPS (DD DD03)

Step 2 - STEP05: runs CBACT01C

  • Comment: RUN THE PROGRAM THAT READS THE ACCOUNT MASTER VSAM FILE
  • CBACT01C's comments: PROGRAM : CBACT01C.CBL / Application : CardDemo / Type : BATCH COBOL Program / FUNCTION : READ THE ACCOUNT FILE AND WRITE INTO FILES.
  • Reads: AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS (DD ACCTFILE)
  • Creates: AWS.M2.CARDDEMO.ACCTDATA.ARRYPS (DD ARRYFILE), AWS.M2.CARDDEMO.ACCTDATA.PSCOMP (DD OUTFILE), AWS.M2.CARDDEMO.ACCTDATA.VBPS (DD VBRCFILE)

Inputs from outside the job: AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS Outputs it leaves behind: AWS.M2.CARDDEMO.ACCTDATA.ARRYPS, AWS.M2.CARDDEMO.ACCTDATA.PSCOMP, AWS.M2.CARDDEMO.ACCTDATA.VBPS

Job READCARD

Refactor suggested - 1 program(s), 146 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
1
copybooks
1
datasets
2
record layouts
146
lines of source
InputsStepsOutputsAWS.M2.CARDDEMO.CARDDATA.VSAM.KSDSAWS.M2.CARDDEMO.CARDDATA.VSAM.KSDSSTEP05: CBACT02CSTEP05: CBACT02C

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Job READCARD

Step 1 - STEP05: runs CBACT02C

  • Comment: RUN THE PROGRAM THAT READS THE CARD MASTER VSAM FILE
  • CBACT02C's comments: Program : CBACT02C.CBL / Application : CardDemo / Type : BATCH COBOL Program / Function : Read and print card data file.
  • Reads: AWS.M2.CARDDEMO.CARDDATA.VSAM.KSDS (DD CARDFILE)

Inputs from outside the job: AWS.M2.CARDDEMO.CARDDATA.VSAM.KSDS Outputs it leaves behind: none

Job READCUST

Refactor suggested - 1 program(s), 159 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
1
copybooks
1
datasets
2
record layouts
159
lines of source
InputsStepsOutputsAWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDSAWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDSSTEP05: CBCUS01CSTEP05: CBCUS01C

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Job READCUST

Step 1 - STEP05: runs CBCUS01C

  • Comment: RUN THE PROGRAM THAT READS THE CUSTOMER MASTER VSAM FILE
  • CBCUS01C's comments: Program : CBCUS01C.CBL / Application : CardDemo / Type : BATCH COBOL Program / Function : Read and print customer data file.
  • Reads: AWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDS (DD CUSTFILE)

Inputs from outside the job: AWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDS Outputs it leaves behind: none

Job READXREF

Refactor suggested - 1 program(s), 144 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
1
copybooks
1
datasets
2
record layouts
144
lines of source
InputsStepsOutputsAWS.M2.CARDDEMO.CARDXREF.VSAM.KSDSAWS.M2.CARDDEMO.CARDXREF.VSAM.KSDSSTEP05: CBACT03CSTEP05: CBACT03C

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Job READXREF

Step 1 - STEP05: runs CBACT03C

  • Comment: RUN THE PROGRAM THAT READS THE XREF MASTER VSAM FILE
  • CBACT03C's comments: Program : CBACT03C.CBL / Application : CardDemo / Type : BATCH COBOL Program / Function : Read and print account cross reference data file.
  • Reads: AWS.M2.CARDDEMO.CARDXREF.VSAM.KSDS (DD XREFFILE)

Inputs from outside the job: AWS.M2.CARDDEMO.CARDXREF.VSAM.KSDS Outputs it leaves behind: none

Job REPTFILE

Retire suggested - Only IBM utilities that define and delete data sets - housekeeping a database-backed platform doesn't need.

1
jobs
1
steps
1
system programs
1
datasets
10
lines of source
InputsStepsOutputsdefinedefineSTEP05: IDCAMSSTEP05: IDCAMSAWS.M2.CARDDEMO.TRANREPTAWS.M2.CARDDEMO.TRANREPT

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Job REPTFILE

Step 1 - STEP05: runs IDCAMS (IBM utility)

  • Comment: DELETE TRANSACATION MASTER VSAM FILE IF ONE ALREADY EXISTS
  • Defines: AWS.M2.CARDDEMO.TRANREPT
  • Control statements: DEFINE GENERATIONDATAGROUP (NAME(AWS.M2.CARDDEMO.TRANREPT) LIMIT(10) )

Inputs from outside the job: none Outputs it leaves behind: none

Job TCATBALF

Refactor suggested - Only IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.

1
jobs
3
steps
1
system programs
2
datasets
36
lines of source
InputsStepsOutputsdeletedeletedefinedefineAWS.M2.CARDDEMO.TCATBALF.PSAWS.M2.CARDDEMO.TCATBALF.PSSTEP05: IDCAMSSTEP05: IDCAMSSTEP10: IDCAMSSTEP10: IDCAMSSTEP15: IDCAMSSTEP15: IDCAMSAWS.M2.CARDDEMO.TCATBALF.VSAM.KSDSAWS.M2.CARDDEMO.TCATBALF.VSAM.KSDS

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Job TCATBALF

Step 1 - STEP05: runs IDCAMS (IBM utility)

  • Comment: DELETE TRANSACTION CATEGORY BALANCE VSAM FILE IF ONE ALREADY EXISTS
  • Deletes: AWS.M2.CARDDEMO.TCATBALF.VSAM.KSDS
  • Control statements: DELETE AWS.M2.CARDDEMO.TCATBALF.VSAM.KSDS CLUSTER SET MAXCC = 0

Step 2 - STEP10: runs IDCAMS (IBM utility)

  • Comment: DEFINE TRANSACTION CATEGORY BALANCE VSAM FILE
  • Defines: AWS.M2.CARDDEMO.TCATBALF.VSAM.KSDS
  • Control statements: DEFINE CLUSTER (NAME(AWS.M2.CARDDEMO.TCATBALF.VSAM.KSDS) CYLINDERS(1 5) VOLUMES(AWSHJ1 ) KEYS(17 0) RECORDSIZE(50 50) SHAREOPTIONS(2 3) ERASE

Step 3 - STEP15: runs IDCAMS (IBM utility)

  • Comment: COPY DATA FROM FLAT FILE TO VSAM FILE
  • Copies AWS.M2.CARDDEMO.TCATBALF.PS into AWS.M2.CARDDEMO.TCATBALF.VSAM.KSDS
  • Reads: AWS.M2.CARDDEMO.TCATBALF.PS (DD TCATBAL)
  • Writes: AWS.M2.CARDDEMO.TCATBALF.VSAM.KSDS (DD TCATBALV)
  • Control statements: REPRO INFILE(TCATBAL) OUTFILE(TCATBALV)

Inputs from outside the job: AWS.M2.CARDDEMO.TCATBALF.PS Outputs it leaves behind: AWS.M2.CARDDEMO.TCATBALF.VSAM.KSDS

Job TRANBKP

Refactor suggested - Only IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.

1
jobs
1
PROCs
3
steps
1
system programs
1
control cards
3
datasets
65
lines of source
InputsStepsOutputsdeletedeletedeletedeletedefinedefineAWS.M2.CARDDEMO.TRANSACT.VSAM.KSDSAWS.M2.CARDDEMO.TRANSACT.VSAM.KSDSSTEP05R.PRC001: IDCAMSSTEP05R.PRC001: IDCAMSSTEP05: IDCAMSSTEP05: IDCAMSSTEP10: IDCAMSSTEP10: IDCAMSAWS.M2.CARDDEMO.TRANSACT.BKUPAWS.M2.CARDDEMO.TRANSACT.BKUPAWS.M2.CARDDEMO.TRANSACT.VSAM.AIXAWS.M2.CARDDEMO.TRANSACT.VSAM.AIXAWS.M2.CARDDEMO.TRANSACT.VSAM.KSDSAWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Job TRANBKP

Step 1 - STEP05R.PRC001 (in PROC REPROC): runs IDCAMS (IBM utility)

  • Comment: Repro the processed transaction file / REPRO UTILITY TO LOAD OR UNLOAD VSAM FILE
  • Copies AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS into AWS.M2.CARDDEMO.TRANSACT.BKUP
  • Reads: AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS (DD FILEIN)
  • Creates: AWS.M2.CARDDEMO.TRANSACT.BKUP (DD FILEOUT)
  • Control statements: REPRO INFILE(FILEIN) OUTFILE(FILEOUT)
  • Reads control card REPROCT (DD SYSIN)

Step 2 - STEP05: runs IDCAMS (IBM utility)

  • Comment: DELETE TRANSACATION MASTER VSAM FILE IF ONE ALREADY EXISTS
  • Deletes: AWS.M2.CARDDEMO.TRANSACT.VSAM.AIX, AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS
  • Control statements: DELETE AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS CLUSTER IF MAXCC LE 08 THEN SET MAXCC = 0 DELETE AWS.M2.CARDDEMO.TRANSACT.VSAM.AIX ALTERNATEINDEX IF MAXCC LE 08 THEN SET MAXCC = 0

Step 3 - STEP10: runs IDCAMS (IBM utility)

  • Comment: DEFINE TRANSACATION MASTER VSAM FILE
  • Defines: AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS
  • Control statements: DEFINE CLUSTER (NAME(AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS) CYLINDERS(1 5) VOLUMES(AWSHJ1 ) KEYS(16 0) RECORDSIZE(350 350) SHAREOPTIONS(2 3) ERASE

Inputs from outside the job: AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS Outputs it leaves behind: AWS.M2.CARDDEMO.TRANSACT.BKUP

Job TRANCATG

Refactor suggested - Only IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.

1
jobs
3
steps
1
system programs
2
datasets
36
lines of source
InputsStepsOutputsdeletedeletedefinedefineAWS.M2.CARDDEMO.TRANCATG.PSAWS.M2.CARDDEMO.TRANCATG.PSSTEP05: IDCAMSSTEP05: IDCAMSSTEP10: IDCAMSSTEP10: IDCAMSSTEP15: IDCAMSSTEP15: IDCAMSAWS.M2.CARDDEMO.TRANCATG.VSAM.KSDSAWS.M2.CARDDEMO.TRANCATG.VSAM.KSDS

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Job TRANCATG

Step 1 - STEP05: runs IDCAMS (IBM utility)

  • Comment: DELETE TRANSACTION CATEGORY TYPE VSAM FILE IF ONE ALREADY EXISTS
  • Deletes: AWS.M2.CARDDEMO.TRANCATG.VSAM.KSDS
  • Control statements: DELETE AWS.M2.CARDDEMO.TRANCATG.VSAM.KSDS CLUSTER SET MAXCC = 0

Step 2 - STEP10: runs IDCAMS (IBM utility)

  • Comment: DEFINE TRANSACTION CATEGORY TYPE VSAM FILE
  • Defines: AWS.M2.CARDDEMO.TRANCATG.VSAM.KSDS
  • Control statements: DEFINE CLUSTER (NAME(AWS.M2.CARDDEMO.TRANCATG.VSAM.KSDS) CYLINDERS(1 5) VOLUMES(AWSHJ1 ) KEYS(6 0) RECORDSIZE(60 60) SHAREOPTIONS(2 3) ERASE

Step 3 - STEP15: runs IDCAMS (IBM utility)

  • Comment: COPY DATA FROM FLAT FILE TO VSAM FILE
  • Copies AWS.M2.CARDDEMO.TRANCATG.PS into AWS.M2.CARDDEMO.TRANCATG.VSAM.KSDS
  • Reads: AWS.M2.CARDDEMO.TRANCATG.PS (DD TRANCATG)
  • Writes: AWS.M2.CARDDEMO.TRANCATG.VSAM.KSDS (DD TCATVSAM)
  • Control statements: REPRO INFILE(TRANCATG) OUTFILE(TCATVSAM)

Inputs from outside the job: AWS.M2.CARDDEMO.TRANCATG.PS Outputs it leaves behind: AWS.M2.CARDDEMO.TRANCATG.VSAM.KSDS

Job TRANEXTR

Refactor suggested - Only IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.

1
jobs
5
steps
3
system programs
4
datasets
2
Db2 tables
83
lines of source
InputsStepsOutputsdeletedeletedeletedeleteAWS.M2.CARDDEMO.TRANTYPE.PSAWS.M2.CARDDEMO.TRANTYPE.PSAWS.M2.CARDDEMO.TRANCATG.PSAWS.M2.CARDDEMO.TRANCATG.PSCARDDEMO.TRANSACTION_TYPECARDDEMO.TRANSACTION_TYPECARDDEMO.TRANSACTION_TYPE_CATEGORYCARDDEMO.TRANSACTION_TYPE_CATEGORYSTEP10: IEBGENERSTEP10: IEBGENERSTEP20: IEBGENERSTEP20: IEBGENERSTEP30: IEFBR14STEP30: IEFBR14STEP40: DSNTIAULSTEP40: DSNTIAULSTEP50: DSNTIAULSTEP50: DSNTIAULAWS.M2.CARDDEMO.TRANTYPE.BKUPAWS.M2.CARDDEMO.TRANTYPE.BKUPAWS.M2.CARDDEMO.TRANCATG.PS.BKUPAWS.M2.CARDDEMO.TRANCATG.PS.BKUPAWS.M2.CARDDEMO.TRANCATG.PSAWS.M2.CARDDEMO.TRANCATG.PSAWS.M2.CARDDEMO.TRANTYPE.PSAWS.M2.CARDDEMO.TRANTYPE.PS

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Job TRANEXTR

Step 1 - STEP10: runs IEBGENER (IBM utility)

  • Comment: This JCL will extract reference data for use in Transaction / Report generation. It runs once a day. So changes will reflect / in report only after the daily batch is run. / Set Parms for this compile: / Db2 Unload using DSNTIAUL utility / STEP 10 : BACKUP THE PREVIOUS VERSION OF TRANTYPE FILE TO GDG
  • Copies AWS.M2.CARDDEMO.TRANTYPE.PS into AWS.M2.CARDDEMO.TRANTYPE.BKUP
  • Reads: AWS.M2.CARDDEMO.TRANTYPE.PS (DD SYSUT1)
  • Creates: AWS.M2.CARDDEMO.TRANTYPE.BKUP (DD SYSUT2)

Step 2 - STEP20: runs IEBGENER (IBM utility)

  • Comment: STEP 20 : BACKUP THE PREVIOUS VERSION OF TRANCATG FILE TO GDG
  • Copies AWS.M2.CARDDEMO.TRANCATG.PS into AWS.M2.CARDDEMO.TRANCATG.PS.BKUP
  • Reads: AWS.M2.CARDDEMO.TRANCATG.PS (DD SYSUT1)
  • Creates: AWS.M2.CARDDEMO.TRANCATG.PS.BKUP (DD SYSUT2)

Step 3 - STEP30: runs IEFBR14 (IBM utility)

  • Comment: STEP 30 : DELETE FILES FROM PREVIOUS RUN
  • Deletes: AWS.M2.CARDDEMO.TRANCATG.PS (DD DD02), AWS.M2.CARDDEMO.TRANTYPE.PS (DD DD01)

Step 4 - STEP40: runs DSNTIAUL (IBM utility), through IKJEFT01

  • Comment: STEP 40 : EXTRACT DATA FROM TRANSACTION TYPE TABLE
  • UNLOAD TABLE CARDDEMO.TRANSACTION_TYPE into AWS.M2.CARDDEMO.TRANTYPE.PS
  • Reads: CARDDEMO.TRANSACTION_TYPE
  • Creates: AWS.M2.CARDDEMO.TRANTYPE.PS (DD SYSREC00)

Step 5 - STEP50: runs DSNTIAUL (IBM utility), through IKJEFT01

  • Comment: STEP 50 : EXTRACT DATA FROM TRANSACTION TYPE TABLE
  • UNLOAD TABLE CARDDEMO.TRANSACTION_TYPE_CATEGORY into AWS.M2.CARDDEMO.TRANCATG.PS
  • Reads: CARDDEMO.TRANSACTION_TYPE_CATEGORY
  • Creates: AWS.M2.CARDDEMO.TRANCATG.PS (DD SYSREC00)

Inputs from outside the job: CARDDEMO.TRANSACTION_TYPE, CARDDEMO.TRANSACTION_TYPE_CATEGORY Outputs it leaves behind: AWS.M2.CARDDEMO.TRANCATG.PS, AWS.M2.CARDDEMO.TRANCATG.PS.BKUP, AWS.M2.CARDDEMO.TRANTYPE.BKUP, AWS.M2.CARDDEMO.TRANTYPE.PS

Job TRANFILE

Refactor suggested - Only IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.

1
jobs
8
steps
2
system programs
4
datasets
81
lines of source
InputsStepsOutputsdeletedeletedeletedeletedefinedefinedefinedefinedefinedefineAWS.M2.CARDDEMO.DALYTRAN.PS.INITAWS.M2.CARDDEMO.DALYTRAN.PS.INITAWS.M2.CARDDEMO.TRANSACT.VSAM.KSDSAWS.M2.CARDDEMO.TRANSACT.VSAM.KSDSCLCIFIL: SDSFCLCIFIL: SDSFSTEP05: IDCAMSSTEP05: IDCAMSSTEP10: IDCAMSSTEP10: IDCAMSSTEP15: IDCAMSSTEP15: IDCAMSSTEP20: IDCAMSSTEP20: IDCAMSSTEP25: IDCAMSSTEP25: IDCAMSSTEP30: IDCAMSSTEP30: IDCAMSOPCIFIL: SDSFOPCIFIL: SDSFAWS.M2.CARDDEMO.TRANSACT.VSAM.AIXAWS.M2.CARDDEMO.TRANSACT.VSAM.AIXAWS.M2.CARDDEMO.TRANSACT.VSAM.KSDSAWS.M2.CARDDEMO.TRANSACT.VSAM.KSDSAWS.M2.CARDDEMO.TRANSACT.VSAM.AIX.PATHAWS.M2.CARDDEMO.TRANSACT.VSAM.AIX.PATH

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Job TRANFILE

Step 1 - CLCIFIL: runs SDSF (IBM utility)

  • Comment: Close files in CICS region

Step 2 - STEP05: runs IDCAMS (IBM utility)

  • Comment: DELETE TRANSACATION MASTER VSAM FILE IF ONE ALREADY EXISTS
  • Deletes: AWS.M2.CARDDEMO.TRANSACT.VSAM.AIX, AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS
  • Control statements: DELETE AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS CLUSTER IF MAXCC LE 08 THEN SET MAXCC = 0 DELETE AWS.M2.CARDDEMO.TRANSACT.VSAM.AIX ALTERNATEINDEX IF MAXCC LE 08 THEN SET MAXCC = 0

Step 3 - STEP10: runs IDCAMS (IBM utility)

  • Comment: DEFINE TRANSACATION MASTER VSAM FILE
  • Defines: AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS
  • Control statements: DEFINE CLUSTER (NAME(AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS) CYLINDERS(1 5) VOLUMES(AWSHJ1 ) KEYS(16 0) RECORDSIZE(350 350) SHAREOPTIONS(2 3) ERASE

Step 4 - STEP15: runs IDCAMS (IBM utility)

  • Comment: COPY DATA FROM FLAT FILE TO VSAM FILE
  • Copies AWS.M2.CARDDEMO.DALYTRAN.PS.INIT into AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS
  • Reads: AWS.M2.CARDDEMO.DALYTRAN.PS.INIT (DD TRANSACT)
  • Writes: AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS (DD TRANVSAM)
  • Control statements: REPRO INFILE(TRANSACT) OUTFILE(TRANVSAM)

Step 5 - STEP20: runs IDCAMS (IBM utility)

  • Comment: CREATE ALTERNATE INDEX ON PROCESSED TIMESTAMP
  • Defines: AWS.M2.CARDDEMO.TRANSACT.VSAM.AIX
  • Control statements: DEFINE ALTERNATEINDEX (NAME(AWS.M2.CARDDEMO.TRANSACT.VSAM.AIX)- RELATE(AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS) KEYS(26 304) NONUNIQUEKEY UPGRADE RECORDSIZE(350,350) VOLUMES(AWSHJ1) CYLINDERS(5,1))

Step 6 - STEP25: runs IDCAMS (IBM utility)

  • Comment: DEFINE PATH IS USED TO RELATE THE ALTERNATE INDEX TO BASE CLUSTER
  • Defines: AWS.M2.CARDDEMO.TRANSACT.VSAM.AIX.PATH
  • Control statements: DEFINE PATH (NAME(AWS.M2.CARDDEMO.TRANSACT.VSAM.AIX.PATH) PATHENTRY(AWS.M2.CARDDEMO.TRANSACT.VSAM.AIX))

Step 7 - STEP30: runs IDCAMS (IBM utility)

  • Comment: BUILD ALTERNATE INDEX CLUSTER
  • BLDINDEX AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS into AWS.M2.CARDDEMO.TRANSACT.VSAM.AIX
  • Reads: AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS
  • Writes: AWS.M2.CARDDEMO.TRANSACT.VSAM.AIX
  • Control statements: BLDINDEX INDATASET(AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS) OUTDATASET(AWS.M2.CARDDEMO.TRANSACT.VSAM.AIX)

Step 8 - OPCIFIL: runs SDSF (IBM utility)

  • Comment: Opem files in CICS region

Inputs from outside the job: AWS.M2.CARDDEMO.DALYTRAN.PS.INIT Outputs it leaves behind: AWS.M2.CARDDEMO.TRANSACT.VSAM.AIX

Job TRANIDX

Refactor suggested - Only IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.

1
jobs
3
steps
1
system programs
3
datasets
30
lines of source
InputsStepsOutputsdefinedefinedefinedefineAWS.M2.CARDDEMO.TRANSACT.VSAM.KSDSAWS.M2.CARDDEMO.TRANSACT.VSAM.KSDSSTEP20: IDCAMSSTEP20: IDCAMSSTEP25: IDCAMSSTEP25: IDCAMSSTEP30: IDCAMSSTEP30: IDCAMSAWS.M2.CARDDEMO.TRANSACT.VSAM.AIXAWS.M2.CARDDEMO.TRANSACT.VSAM.AIXAWS.M2.CARDDEMO.TRANSACT.VSAM.AIX.PATHAWS.M2.CARDDEMO.TRANSACT.VSAM.AIX.PATH

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Job TRANIDX

Step 1 - STEP20: runs IDCAMS (IBM utility)

  • Comment: CREATE ALTERNATE INDEX ON PROCESSED TIMESTAMP
  • Defines: AWS.M2.CARDDEMO.TRANSACT.VSAM.AIX
  • Control statements: DEFINE ALTERNATEINDEX (NAME(AWS.M2.CARDDEMO.TRANSACT.VSAM.AIX)- RELATE(AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS) KEYS(26 304) NONUNIQUEKEY UPGRADE RECORDSIZE(350,350) VOLUMES(AWSHJ1) CYLINDERS(5,1))

Step 2 - STEP25: runs IDCAMS (IBM utility)

  • Comment: DEFINE PATH IS USED TO RELATE THE ALTERNATE INDEX TO BASE CLUSTER
  • Defines: AWS.M2.CARDDEMO.TRANSACT.VSAM.AIX.PATH
  • Control statements: DEFINE PATH (NAME(AWS.M2.CARDDEMO.TRANSACT.VSAM.AIX.PATH) PATHENTRY(AWS.M2.CARDDEMO.TRANSACT.VSAM.AIX))

Step 3 - STEP30: runs IDCAMS (IBM utility)

  • Comment: BUILD ALTERNATE INDEX CLUSTER
  • BLDINDEX AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS into AWS.M2.CARDDEMO.TRANSACT.VSAM.AIX
  • Reads: AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS
  • Writes: AWS.M2.CARDDEMO.TRANSACT.VSAM.AIX
  • Control statements: BLDINDEX INDATASET(AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS) OUTDATASET(AWS.M2.CARDDEMO.TRANSACT.VSAM.AIX)

Inputs from outside the job: AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS Outputs it leaves behind: AWS.M2.CARDDEMO.TRANSACT.VSAM.AIX

Job TRANREPT

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

1
jobs
1
PROCs
3
steps
1
programs
3
system programs
5
copybooks
1
control cards
8
datasets
15
record layouts
708
lines of source
InputsStepsOutputsAWS.M2.CARDDEMO.TRANSACT.VSAM.KSDSAWS.M2.CARDDEMO.TRANSACT.VSAM.KSDSAWS.M2.CARDDEMO.TRANSACT.BKUPAWS.M2.CARDDEMO.TRANSACT.BKUPAWS.M2.CARDDEMO.CARDXREF.VSAM.KSDSAWS.M2.CARDDEMO.CARDXREF.VSAM.KSDSAWS.M2.CARDDEMO.DATEPARMAWS.M2.CARDDEMO.DATEPARMAWS.M2.CARDDEMO.TRANCATG.VSAM.KSDSAWS.M2.CARDDEMO.TRANCATG.VSAM.KSDSAWS.M2.CARDDEMO.TRANSACT.DALYAWS.M2.CARDDEMO.TRANSACT.DALYAWS.M2.CARDDEMO.TRANTYPE.VSAM.KSDSAWS.M2.CARDDEMO.TRANTYPE.VSAM.KSDSSTEP05R.PRC001: IDCAMSSTEP05R.PRC001: IDCAMSSTEP05R: SORTSTEP05R: SORTSTEP10R: CBTRN03CSTEP10R: CBTRN03CAWS.M2.CARDDEMO.TRANSACT.BKUPAWS.M2.CARDDEMO.TRANSACT.BKUPAWS.M2.CARDDEMO.TRANSACT.DALYAWS.M2.CARDDEMO.TRANSACT.DALYAWS.M2.CARDDEMO.TRANREPTAWS.M2.CARDDEMO.TRANREPT

What it does

TRANREPT produces the Daily Transaction Report. It takes a backup copy of the transaction master file, keeps only the transactions processed within a date range, sorts them by card number, and prints a report listing each transaction with its account, type, category, source, and amount, with totals per card, per page, and overall. Each run creates new generations of the backup, the filtered extract, and the report, so earlier runs are kept.

Step by step
  1. Unload the transaction master (STEP05R, PROC REPROC, IDCAMS REPRO). Copies the whole VSAM transaction master file (TRANSACT.VSAM.KSDS) to a new generation of a sequential backup (TRANSACT.BKUP(+1)).
  2. Select and sort (STEP05R, SORT). From that backup, keeps only the transactions whose processing date (TRAN-PROC-DT, the date part of TRAN-PROC-TS) is between the start and end dates coded in the JCL - currently 2022-01-01 to 2022-07-06 - sorts them by card number (TRAN-CARD-NUM), and writes them to a new generation of the daily extract (TRANSACT.DALY(+1)).
  3. Print the report (STEP10R, CBTRN03C). Reads the extract in card-number order, reads its date range from the date parameter file (DATEPARM), looks up each card's account ID and each transaction's type and category descriptions, and writes the report (TRANREPT(+1)): a "Daily Transaction Report" heading with the date range, one line per transaction, an "Account Total" when the card number changes, a "Page Total" every 20 lines, and a "Grand Total" at the end.
What it needs
  • The transaction master file AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS, already updated by the posting job (POSTTRAN) - TRANREPT reports on processed transactions, so it should run after posting.
  • Reference files: card cross-reference (CARDXREF.VSAM.KSDS), transaction types (TRANTYPE.VSAM.KSDS), and transaction categories (TRANCATG.VSAM.KSDS). A card, type, or category missing from them stops the job.
  • The date range, in two places that must match: the SYMNAMES constants in the TRANREPT JCL (used by the SORT) and the first record of AWS.M2.CARDDEMO.DATEPARM (printed on the report and checked by the program).
What it produces
  • AWS.M2.CARDDEMO.TRANREPT(+1) - the printed report (133-character lines), for operations or finance to review.
  • AWS.M2.CARDDEMO.TRANSACT.BKUP(+1) - a full backup of the transaction master as of this run; other jobs (COMBTRAN) read this backup.
  • AWS.M2.CARDDEMO.TRANSACT.DALY(+1) - the filtered, sorted extract the report was printed from.
Notes for modernization
  • Two sources for the date range. The SORT's dates are hard-coded in the JCL while the program reads DATEPARM; if they differ, the report heading can show one range while the lines come from another. The program's own date check doesn't work as written (an out-of-range record would end the report early), so today only the SORT's dates actually select the data.
  • Totals are slightly off at the end: the last transaction is counted twice in the final page and grand totals, and the last card's total line is missing.
  • The first two steps (unload, filter, sort) and the report program together amount to "select transactions by processing date, ordered by card, with lookups and subtotals" - a single query and a reporting tool on a modern platform.
  • The full unload of the VSAM master on every run is mainly there to feed the SORT; a database-backed version wouldn't need it, but COMBTRAN also reads the backup generation, so that dependency has to move with it.
Step-by-step walkthrough from the source
Job TRANREPT

Step 1 - STEP05R.PRC001 (in PROC REPROC): runs IDCAMS (IBM utility)

  • Comment: Unload the processed transaction file / REPRO UTILITY TO LOAD OR UNLOAD VSAM FILE
  • Copies AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS into AWS.M2.CARDDEMO.TRANSACT.BKUP
  • Reads: AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS (DD FILEIN)
  • Creates: AWS.M2.CARDDEMO.TRANSACT.BKUP (DD FILEOUT)
  • Control statements: REPRO INFILE(FILEIN) OUTFILE(FILEOUT)
  • Reads control card REPROCT (DD SYSIN)

Step 2 - STEP05R: runs SORT (IBM utility)

  • Comment: Filter the transactions for a the parm date and sort by card num
  • Filters and sorts AWS.M2.CARDDEMO.TRANSACT.BKUP into AWS.M2.CARDDEMO.TRANSACT.DALY
  • Reads: AWS.M2.CARDDEMO.TRANSACT.BKUP (DD SORTIN)
  • Creates: AWS.M2.CARDDEMO.TRANSACT.DALY (DD SORTOUT)
  • Sort keys: TRAN-CARD-NUM (ascending, positions 263-278).
  • Keeps only records where TRAN-PROC-DT >= '2022-01-01' and TRAN-PROC-DT <= '2022-07-06'.
  • Control statements: SORT FIELDS=(TRAN-CARD-NUM,A) INCLUDE COND=(TRAN-PROC-DT,GE,PARM-START-DATE,AND, TRAN-PROC-DT,LE,PARM-END-DATE)

Step 3 - STEP10R: runs CBTRN03C

  • Comment: Produce a formatted report for processed transactions
  • What CBTRN03C does: CBTRN03C prints the Daily Transaction Report: every card transaction processed within a date range, one line per transaction with its account, type, category, source, and amount, with subtotals per card, per page, and a grand total. The date range comes from the date parameter file (DATEPARM), not from the program.
  • Reads: AWS.M2.CARDDEMO.CARDXREF.VSAM.KSDS (DD CARDXREF), AWS.M2.CARDDEMO.DATEPARM (DD DATEPARM), AWS.M2.CARDDEMO.TRANCATG.VSAM.KSDS (DD TRANCATG), AWS.M2.CARDDEMO.TRANSACT.DALY (DD TRANFILE), AWS.M2.CARDDEMO.TRANTYPE.VSAM.KSDS (DD TRANTYPE)
  • Creates: AWS.M2.CARDDEMO.TRANREPT (DD TRANREPT)

Inputs from outside the job: AWS.M2.CARDDEMO.CARDXREF.VSAM.KSDS, AWS.M2.CARDDEMO.DATEPARM, AWS.M2.CARDDEMO.TRANCATG.VSAM.KSDS, AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS, AWS.M2.CARDDEMO.TRANTYPE.VSAM.KSDS Outputs it leaves behind: AWS.M2.CARDDEMO.TRANREPT

Program CBTRN03C

CBTRN03C prints the Daily Transaction Report: every card transaction processed within a date range, one line per transaction with its account, type, category, source, and amount, with subtotals per card, per page, and a grand total. The date range comes from the date parameter file (DATEPARM), not from the program.

Inputs
  • Transaction file (DD TRANFILE, AWS.M2.CARDDEMO.TRANSACT.DALY) - the day's transactions, read in sequence. Layout TRAN-RECORD (CVTRA05Y). The program expects them grouped by card number; the job's SORT step sorts them by TRAN-CARD-NUM.
  • Date parameters (DD DATEPARM, AWS.M2.CARDDEMO.DATEPARM) - one record: start date in positions 1-10 and end date in 12-21 (WS-START-DATE, WS-END-DATE), as YYYY-MM-DD.
  • Card cross-reference (DD CARDXREF, VSAM, keyed by card number) - gives the account ID for each card (CVACT03Y).
  • Transaction types (DD TRANTYPE, VSAM, keyed by type code) - type descriptions (CVTRA03Y).
  • Transaction categories (DD TRANCATG, VSAM, keyed by type + category code) - category descriptions (CVTRA04Y).
Outputs
  • Report (DD TRANREPT, AWS.M2.CARDDEMO.TRANREPT, 133-byte print lines, layouts in CVTRA07Y): a title line "DALYREPT - Daily Transaction Report - Date Range: start to end", column headings (Transaction ID, Account ID, Transaction Type, Tran Category, Tran Source, Amount), one detail line per transaction, "Account Total" lines, "Page Total" lines every 20 lines, and a "Grand Total" at the end.
  • Each transaction record is also DISPLAYed to SYSOUT, along with start/end messages.
Processing
  1. Opens all six files; any open failure stops the program with an abend (0000-TRANFILE-OPEN through 0500-DATEPARM-OPEN).
  2. Reads the date range from the parameter file and displays "Reporting from ... to ..." (0550-DATEPARM-READ).
  3. Reads the transactions one at a time (1000-TRANFILE-GET-NEXT) and checks that the processing date (first 10 characters of TRAN-PROC-TS) is within the range (main loop).
  4. When the card number changes, writes the previous card's "Account Total" line and looks up the new card's account ID in the cross-reference file (1120-WRITE-ACCOUNT-TOTALS, 1500-A-LOOKUP-XREF).
  5. Looks up the transaction type and category descriptions (1500-B-LOOKUP-TRANTYPE, 1500-C-LOOKUP-TRANCATG).
  6. Writes the detail line, adding the amount to the page and card totals; before the first line it writes the report headings with the date range, and every 20 lines it writes a page total and the headings again (1100-WRITE-TRANSACTION-REPORT, 1120-WRITE-DETAIL, 1110-WRITE-PAGE-TOTALS, 1120-WRITE-HEADERS).
  7. At end of file, writes the last page total and the grand total, closes the files, and ends (main loop, 1110-WRITE-GRAND-TOTALS, 9000- to 9500- close paragraphs).
Business rules
  • Date selection: only transactions with TRAN-PROC-TS (date part) between WS-START-DATE and WS-END-DATE, inclusive, are meant to be reported.
  • Grouping: subtotals break on TRAN-CARD-NUM - one "Account Total" per card number, with the account ID from the cross-reference. An account with several cards gets several "account" totals.
  • Page size: 20 lines per page (WS-PAGE-SIZE); the page total is added to the grand total (WS-GRAND-TOTAL) when each page total is written.
  • Reference data must exist: a card number missing from the cross-reference, or a type or category code missing from its file, stops the job with an abend ("INVALID CARD NUMBER", "INVALID TRANSACTION TYPE", "INVALID TRAN CATG KEY"); so does any read, write, open, or close error (9999-ABEND-PROGRAM, which calls CEE3ABD).
  • An empty parameter file ends the run with no report lines.
Notes for modernization
  • The date filter doesn't work as written. An out-of-range transaction executes NEXT SENTENCE, which jumps past the end of the whole read loop, so the first out-of-range record would end the report early (the remaining transactions and the final totals are skipped). It works in practice only because the job's SORT step already keeps just the dates in range - so the range lives in two places that must agree: SYMNAMES constants in the TRANREPT JCL (hard-coded 2022-01-01 to 2022-07-06) and the DATEPARM file.
  • Totals at end of file are off: the last transaction's amount is added to the page and card totals a second time, and the last card's "Account Total" line is never written.
  • "Account Total" is really a card total (the break is on card number, not account).
  • Every transaction record is DISPLAYed, which can make SYSOUT very large.
  • Depends on the input being sorted by card number; on a modern platform this becomes an ORDER BY or a sort in the reporting tool.
  • Simple, self-contained report logic: a good candidate to replace with a query plus a reporting tool, once the two date-range sources are reconciled.

Job TRANTYPE

Refactor suggested - Only IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.

1
jobs
3
steps
1
system programs
2
datasets
36
lines of source
InputsStepsOutputsdeletedeletedefinedefineAWS.M2.CARDDEMO.TRANTYPE.PSAWS.M2.CARDDEMO.TRANTYPE.PSSTEP05: IDCAMSSTEP05: IDCAMSSTEP10: IDCAMSSTEP10: IDCAMSSTEP15: IDCAMSSTEP15: IDCAMSAWS.M2.CARDDEMO.TRANTYPE.VSAM.KSDSAWS.M2.CARDDEMO.TRANTYPE.VSAM.KSDS

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Job TRANTYPE

Step 1 - STEP05: runs IDCAMS (IBM utility)

  • Comment: DELETE TRANSACATION TYPE VSAM FILE IF ONE ALREADY EXISTS
  • Deletes: AWS.M2.CARDDEMO.TRANTYPE.VSAM.KSDS
  • Control statements: DELETE AWS.M2.CARDDEMO.TRANTYPE.VSAM.KSDS CLUSTER SET MAXCC = 0

Step 2 - STEP10: runs IDCAMS (IBM utility)

  • Comment: DEFINE TRANSACATION TYPE VSAM FILE
  • Defines: AWS.M2.CARDDEMO.TRANTYPE.VSAM.KSDS
  • Control statements: DEFINE CLUSTER (NAME(AWS.M2.CARDDEMO.TRANTYPE.VSAM.KSDS) CYLINDERS(1 5) VOLUMES(AWSHJ1 ) KEYS(2 0) RECORDSIZE(60 60) SHAREOPTIONS(1 4) ERASE

Step 3 - STEP15: runs IDCAMS (IBM utility)

  • Comment: COPY DATA FROM FLAT FILE TO VSAM FILE
  • Copies AWS.M2.CARDDEMO.TRANTYPE.PS into AWS.M2.CARDDEMO.TRANTYPE.VSAM.KSDS
  • Reads: AWS.M2.CARDDEMO.TRANTYPE.PS (DD TRANTYPE)
  • Writes: AWS.M2.CARDDEMO.TRANTYPE.VSAM.KSDS (DD TTYPVSAM)
  • Control statements: REPRO INFILE(TRANTYPE) OUTFILE(TTYPVSAM)

Inputs from outside the job: AWS.M2.CARDDEMO.TRANTYPE.PS Outputs it leaves behind: AWS.M2.CARDDEMO.TRANTYPE.VSAM.KSDS

Job TXT2PDF1

Refactor suggested - Only IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.

1
jobs
1
steps
1
system programs
2
datasets
14
lines of source
InputsStepsOutputsAWS.M2.CARDDEMO.STATEMNT.PSAWS.M2.CARDDEMO.STATEMNT.PSAWS.M2.LBD.TXT2PDF.EXECAWS.M2.LBD.TXT2PDF.EXECTXT2PDF: IKJEFT1BTXT2PDF: IKJEFT1B

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Job TXT2PDF1

Step 1 - TXT2PDF: runs IKJEFT1B (IBM utility)

  • Comment: CONVERT TEXT FILE TO A PDF FILE
  • Uses: AWS.M2.CARDDEMO.STATEMNT.PS (DD INDD), AWS.M2.LBD.TXT2PDF.EXEC (DD SYSEXEC)

Inputs from outside the job: none Outputs it leaves behind: none

Job UNLDGSAM

Rehost suggested - Uses IMS databases; rehost first and plan the data migration separately.

1
jobs
1
steps
1
programs
1
system programs
6
copybooks
4
datasets
4
IMS segments
311
lines of source
InputsStepsOutputsAWS.M2.CARDDEMO.PAUTDB.CHILD.GSAMAWS.M2.CARDDEMO.PAUTDB.CHILD.GSAMAWS.M2.CARDDEMO.PAUTDB.ROOT.GSAMAWS.M2.CARDDEMO.PAUTDB.ROOT.GSAMOEM.IMS.IMSP.PAUTHDBOEM.IMS.IMSP.PAUTHDBOEM.IMS.IMSP.PAUTHDBXOEM.IMS.IMSP.PAUTHDBXSTEP01: DBUNLDGSSTEP01: DBUNLDGS

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Job UNLDGSAM

Step 1 - STEP01: runs DBUNLDGS, through DFSRRC00

  • Comment: EXECUTE IMS PROGRAM
  • DBUNLDGS's comments: SELECT OPFILE1 ASSIGN TO OUTFIL1 / ORGANIZATION IS SEQUENTIAL / ACCESS MODE IS SEQUENTIAL / FILE STATUS IS WS-OUTFL1-STATUS.
  • Uses: AWS.M2.CARDDEMO.PAUTDB.CHILD.GSAM (DD PADFILOP), AWS.M2.CARDDEMO.PAUTDB.ROOT.GSAM (DD PASFILOP), OEM.IMS.IMSP.PAUTHDB (DD DDPAUTP0), OEM.IMS.IMSP.PAUTHDBX (DD DDPAUTX0)
  • Adds records to IMS segment (PCB PADFLPCB)
  • Adds records to IMS segment (PCB PASFLPCB)
  • Reads IMS segment PAUTDTL1
  • Reads IMS segment PAUTSUM0

Inputs from outside the job: none Outputs it leaves behind: none

Job UNLDPADB

Rehost suggested - Uses IMS databases; rehost first and plan the data migration separately.

1
jobs
2
steps
1
programs
2
system programs
4
copybooks
4
datasets
2
IMS segments
2
record layouts
312
lines of source
InputsStepsOutputsdeletedeletedeletedeleteOEM.IMS.IMSP.PAUTHDBOEM.IMS.IMSP.PAUTHDBOEM.IMS.IMSP.PAUTHDBXOEM.IMS.IMSP.PAUTHDBXSTEP0: IEFBR14STEP0: IEFBR14STEP01: PAUDBUNLSTEP01: PAUDBUNLAWS.M2.CARDDEMO.PAUTDB.CHILD.FILEOAWS.M2.CARDDEMO.PAUTDB.CHILD.FILEOAWS.M2.CARDDEMO.PAUTDB.ROOT.FILEOAWS.M2.CARDDEMO.PAUTDB.ROOT.FILEO

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Job UNLDPADB

Step 1 - STEP0: runs IEFBR14 (IBM utility)

  • Comment: EXECUTE IMS PROGRAM
  • Deletes: AWS.M2.CARDDEMO.PAUTDB.CHILD.FILEO (DD DD2), AWS.M2.CARDDEMO.PAUTDB.ROOT.FILEO (DD DD1)

Step 2 - STEP01: runs PAUDBUNL, through DFSRRC00

  • Creates: AWS.M2.CARDDEMO.PAUTDB.CHILD.FILEO (DD OUTFIL2), AWS.M2.CARDDEMO.PAUTDB.ROOT.FILEO (DD OUTFIL1)
  • Uses: OEM.IMS.IMSP.PAUTHDB (DD DDPAUTP0), OEM.IMS.IMSP.PAUTHDBX (DD DDPAUTX0)
  • Reads IMS segment PAUTDTL1
  • Reads IMS segment PAUTSUM0

Inputs from outside the job: none Outputs it leaves behind: AWS.M2.CARDDEMO.PAUTDB.CHILD.FILEO, AWS.M2.CARDDEMO.PAUTDB.ROOT.FILEO

Job WAITSTEP

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

1
jobs
1
steps
2
programs
35
lines of source
InputsStepsOutputsWAIT: COBSWAITWAIT: COBSWAIT

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Job WAITSTEP

Step 1 - WAIT: runs COBSWAIT

  • Comment: WAIT FOR CENTISECONDS IN THE PARM EG: 00003600 = 36 SECONDS
  • COBSWAIT's comments: PROGRAM : COBSWAIT.CBL / Application : CardDemo / Type : BATCH COBOL Program / FUNCTION : UTILITY PROGRAM TO WAIT (PARM IN CENTISECONDS)

Inputs from outside the job: none Outputs it leaves behind: none

Job XREFFILE

Refactor suggested - Only IBM utilities (copy, sort, unload): replace with SQL or the target platform's ETL and scheduling tools.

1
jobs
6
steps
1
system programs
4
datasets
68
lines of source
InputsStepsOutputsdeletedeletedeletedeletedefinedefinedefinedefinedefinedefineAWS.M2.CARDDEMO.CARDXREF.PSAWS.M2.CARDDEMO.CARDXREF.PSAWS.M2.CARDDEMO.CARDXREF.VSAM.KSDSAWS.M2.CARDDEMO.CARDXREF.VSAM.KSDSSTEP05: IDCAMSSTEP05: IDCAMSSTEP10: IDCAMSSTEP10: IDCAMSSTEP15: IDCAMSSTEP15: IDCAMSSTEP20: IDCAMSSTEP20: IDCAMSSTEP25: IDCAMSSTEP25: IDCAMSSTEP30: IDCAMSSTEP30: IDCAMSAWS.M2.CARDDEMO.CARDXREF.VSAM.AIXAWS.M2.CARDDEMO.CARDXREF.VSAM.AIXAWS.M2.CARDDEMO.CARDXREF.VSAM.KSDSAWS.M2.CARDDEMO.CARDXREF.VSAM.KSDSAWS.M2.CARDDEMO.CARDXREF.VSAM.AIX.PATHAWS.M2.CARDDEMO.CARDXREF.VSAM.AIX.PATH

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Job XREFFILE

Step 1 - STEP05: runs IDCAMS (IBM utility)

  • Comment: DELETE CARD XREF VSAM FILE IF ONE ALREADY EXISTS
  • Deletes: AWS.M2.CARDDEMO.CARDXREF.VSAM.AIX, AWS.M2.CARDDEMO.CARDXREF.VSAM.KSDS
  • Control statements: DELETE AWS.M2.CARDDEMO.CARDXREF.VSAM.KSDS CLUSTER IF MAXCC LE 08 THEN SET MAXCC = 0 DELETE AWS.M2.CARDDEMO.CARDXREF.VSAM.AIX ALTERNATEINDEX IF MAXCC LE 08 THEN SET MAXCC = 0

Step 2 - STEP10: runs IDCAMS (IBM utility)

  • Comment: DEFINE CARD XREF VSAM FILE
  • Defines: AWS.M2.CARDDEMO.CARDXREF.VSAM.KSDS
  • Control statements: DEFINE CLUSTER (NAME(AWS.M2.CARDDEMO.CARDXREF.VSAM.KSDS) CYLINDERS(1 5) VOLUMES(AWSHJ1 ) KEYS(16 0) RECORDSIZE(50 50) SHAREOPTIONS(2 3) ERASE

Step 3 - STEP15: runs IDCAMS (IBM utility)

  • Comment: COPY DATA FROM FLAT FILE TO VSAM FILE
  • Copies AWS.M2.CARDDEMO.CARDXREF.PS into AWS.M2.CARDDEMO.CARDXREF.VSAM.KSDS
  • Reads: AWS.M2.CARDDEMO.CARDXREF.PS (DD XREFDATA)
  • Writes: AWS.M2.CARDDEMO.CARDXREF.VSAM.KSDS (DD XREFVSAM)
  • Control statements: REPRO INFILE(XREFDATA) OUTFILE(XREFVSAM)

Step 4 - STEP20: runs IDCAMS (IBM utility)

  • Comment: CREATE ALTERNATE INDEX ON ACCT ID
  • Defines: AWS.M2.CARDDEMO.CARDXREF.VSAM.AIX
  • Control statements: DEFINE ALTERNATEINDEX (NAME(AWS.M2.CARDDEMO.CARDXREF.VSAM.AIX)- RELATE(AWS.M2.CARDDEMO.CARDXREF.VSAM.KSDS) KEYS(11,25) NONUNIQUEKEY UPGRADE RECORDSIZE(50,50) FREESPACE(10,20) VOLUMES(AWSHJ1)

Step 5 - STEP25: runs IDCAMS (IBM utility)

  • Comment: DEFINE PATH IS USED TO RELATE THE ALTERNATE INDEX TO BASE CLUSTER
  • Defines: AWS.M2.CARDDEMO.CARDXREF.VSAM.AIX.PATH
  • Control statements: DEFINE PATH (NAME(AWS.M2.CARDDEMO.CARDXREF.VSAM.AIX.PATH) PATHENTRY(AWS.M2.CARDDEMO.CARDXREF.VSAM.AIX))

Step 6 - STEP30: runs IDCAMS (IBM utility)

  • Comment: BUILD ALTERNATE INDEX CLUSTER
  • BLDINDEX AWS.M2.CARDDEMO.CARDXREF.VSAM.KSDS into AWS.M2.CARDDEMO.CARDXREF.VSAM.AIX
  • Reads: AWS.M2.CARDDEMO.CARDXREF.VSAM.KSDS
  • Writes: AWS.M2.CARDDEMO.CARDXREF.VSAM.AIX
  • Control statements: BLDINDEX INDATASET(AWS.M2.CARDDEMO.CARDXREF.VSAM.KSDS) OUTDATASET(AWS.M2.CARDDEMO.CARDXREF.VSAM.AIX)

Inputs from outside the job: AWS.M2.CARDDEMO.CARDXREF.PS Outputs it leaves behind: AWS.M2.CARDDEMO.CARDXREF.VSAM.AIX

Transaction CA00

Refactor suggested - Screen and navigation only (no data access): rebuild in the new user interface.

1
programs
7
copybooks
1
transactions
1
screens (mapsets)
695
lines of source
ScreensProgramsDatascreen COADM01screen COADM01COADM01CCOADM01C

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Transaction CA00

Starting transaction CA00 runs program COADM01C (from the CSD).

Program COADM01C

  • Its comments: Program : COADM01C.CBL / Application : CardDemo / Type : CICS COBOL Program / Function : Admin Menu for Admin users
  • Screen: sends and receives mapset COADM01
  • Ends the turn and waits for the user; the next input runs transaction CA00 again
  • Transfers control (XCTL) to COSGN00C (entry program of transaction CC00)
  • Transfers control (XCTL) to COTRTLIC (entry program of transaction CTLI)
  • Transfers control (XCTL) to COTRTUPC (entry program of transaction CTTU)
  • Transfers control (XCTL) to COUSR00C (entry program of transaction CU00)
  • Transfers control (XCTL) to COUSR01C (entry program of transaction CU01)
  • Transfers control (XCTL) to COUSR02C (entry program of transaction CU02)
  • Transfers control (XCTL) to COUSR03C (entry program of transaction CU03)

Where it connects to other work: XCTL PROGRAM COSGN00C (entry program of transaction CC00); XCTL PROGRAM COTRTLIC (entry program of transaction CTLI); XCTL PROGRAM COTRTUPC (entry program of transaction CTTU); XCTL PROGRAM COUSR00C (entry program of transaction CU00); XCTL PROGRAM COUSR01C (entry program of transaction CU01); XCTL PROGRAM COUSR02C (entry program of transaction CU02); XCTL PROGRAM COUSR03C (entry program of transaction CU03)

Transaction CAUP

Expose as API suggested - Reads or updates business data behind a 3270 screen: keep the logic as a service (API) and replace the screen with a web interface.

2
programs
1
system programs
16
copybooks
1
transactions
1
screens (mapsets)
3
datasets
5
record layouts
6,518
lines of source
ScreensProgramsDataread/updateread/updatereadreadread/updateread/updatescreen COACTUPscreen COACTUPCOACTUPCCOACTUPCCSUTLDTC (CALL)CSUTLDTC (CALL)AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDSAWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDSAWS.M2.CARDDEMO.CARDXREF.VSAM.AIX.PATHAWS.M2.CARDDEMO.CARDXREF.VSAM.AIX.PATHAWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDSAWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDS

What it does

CAUP lets a user look up an account and change it: the account's status, dates, credit limits, and balances, and the account holder's name, address, phone numbers, SSN, date of birth, FICO score, and EFT account. Changes are validated field by field, shown back for confirmation, and saved to the account and customer records together, with protection against two people updating the same account at once.

Step by step
  1. From the main menu (option 2), COACTUPC shows an empty screen asking for an account number.
  2. The user enters an account number; the program finds the account's customer through the card cross-reference, reads the account and customer records, and shows them.
  3. The user changes fields and presses Enter. If anything changed, every field is validated - required fields, dates, amounts, US state and ZIP consistency, phone format, SSN rules, FICO score 300-850 - and errors are shown on the screen.
  4. When the changes pass, the screen asks the user to press PF5 to save. PF12 cancels the changes and shows the stored data again.
  5. On PF5 the program locks both records, checks nobody changed them since they were shown, and rewrites the account and then the customer; if the customer can't be saved, both changes are rolled back. It reports success, a lock or update failure, or "changed by someone else" (showing the current data).
  6. PF3 returns to the main menu.
What it needs
  • The account master (ACCTDATA.VSAM.KSDS), the customer master (CUSTDATA.VSAM.KSDS), and the card cross-reference by account (CARDXREF.VSAM.AIX.PATH).
  • The date-checking routine CSUTLDTC (IBM CEEDAYS).
What it produces
  • Updated account and customer records - used by posting (POSTTRAN, credit limit and expiry checks), interest (INTCALC, balance and cycle totals), statements (CREASTMT, name, address, balance, FICO score), and the other account and card screens.
  • These files are also read by batch jobs outside this screen: the account file by ACCTFILE, CBEXPORT, CREASTMT, INTCALC, POSTTRAN, and READACCT, and the customer file by CBEXPORT, CREASTMT, CUSTFILE, and READCUST.
Notes for modernization
  • Balances and limits can be typed in: any user can change the current balance, cycle totals, and credit limits directly, bypassing posting - a control gap to raise with the client, and a rule to decide before building the new screen.
  • Strong update pattern to keep: confirmation, locking, the "changed by someone else" check, and the joint save map directly onto a database transaction with optimistic concurrency.
  • The business rules (state/ZIP check, SSN rules, FICO range, phone format) are worth extracting into a shared validation service; most of the program's 3,400 lines are screen handling that a web form replaces.
  • Expose as API: "get account with holder" and "update account with holder" are natural service operations behind a new web screen, with the batch jobs above reading the same data.
  • Leaving with PF3 resets the session's user type to regular user (see COACTUPC).
Step-by-step walkthrough from the source
Transaction CAUP

Starting transaction CAUP runs program COACTUPC (from the CSD).

Program COACTUPC

  • What it does: COACTUPC is the account update screen. A user enters an account number, sees the account and its customer's details, edits them, and confirms with PF5; the program validates every field, checks nobody else changed the records in the meantime, and saves the account and customer records together. It covers both account terms (status, dates, credit limits, balances) and customer details (name, address, phones, SSN, date of birth, FICO score, EFT account).
  • Screen: sends and receives mapset COACTUP
  • Reads and updates file AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS
  • Reads file AWS.M2.CARDDEMO.CARDXREF.VSAM.AIX.PATH
  • Reads and updates file AWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDS
  • Calls CSUTLDTC
  • Ends the turn and waits for the user; the next input runs transaction CAUP again
  • Transfers control (XCTL) to COMEN01C (entry program of transaction CM00)
  • Transfers control (XCTL) to COMEN01C (back to the caller)

Program CSUTLDTC (CALL from its caller)

  • What it does: CSUTLDTC is a small shared routine that checks whether a date is valid for a given format (for example YYYY-MM-DD). It asks the IBM Language Environment date service CEEDAYS to convert the date, and returns a readable result message and a severity as the return code. The account update, transaction add, and transaction report screens use it.
  • Calls CEEDAYS (IBM routine)
Program COACTUPC

COACTUPC is the account update screen. A user enters an account number, sees the account and its customer's details, edits them, and confirms with PF5; the program validates every field, checks nobody else changed the records in the meantime, and saves the account and customer records together. It covers both account terms (status, dates, credit limits, balances) and customer details (name, address, phones, SSN, date of birth, FICO score, EFT account).

Inputs
  • Account update screen (mapset COACTUP): the account number to look up, then the edited account and customer fields; Enter, PF5 (save), PF12 (cancel changes), or PF3 (exit).
  • Communication area (CARDDEMO-COMMAREA, COCOM01Y) plus this program's own saved state: the original values shown and where the user is in the update.
  • Card cross-reference by account (CICS file CXACAIX, the alternate index on the cross-reference) - finds the customer for the account.
  • Account master (CICS file ACCTDAT, CVACT01Y) and customer master (CICS file CUSTDAT, CVCUS01Y).
Outputs
  • The screen, showing the account and customer data, field-level error messages, and prompts ("Changes validated. Press F5 to save", confirmation or failure messages).
  • Updated account and customer records (CICS REWRITE of ACCTDAT and CUSTDAT).
  • PF3 returns (XCTL) to the program the user came from, or the main menu.
Processing
  1. On entry from the menu, shows an empty screen asking for an account number (0000-MAIN, 3000-SEND-MAP).
  2. On Enter with an account number, validates it, finds the customer through the cross-reference by account, reads the account and customer, and shows their details (1210-EDIT-ACCOUNT, 2000-DECIDE-ACTION, 9000-READ-ACCT, 9200-GETCARDXREF-BYACCT, 9300-GETACCTDATA-BYACCT, 9400-GETCUSTDATA-BYCUST, 9500-STORE-FETCHED-DATA).
  3. When the user changes fields and presses Enter, compares new values with the originals; if anything changed, validates every field and either shows the errors or asks for confirmation with PF5 (1200-EDIT-MAP-INPUTS, 1205-COMPARE-OLD-NEW, the 1210- to 1280- edit paragraphs).
  4. On PF5, reads both records for update (locking them), checks they still hold the values originally shown, and rewrites the account and then the customer; if the customer rewrite fails, rolls both back (9600-WRITE-PROCESSING, 9700-CHECK-CHANGE-IN-REC).
  5. Reports success, a lock failure, an update failure, or "data changed by someone else" (in which case it shows the current data again), and then asks for the next account (2000-DECIDE-ACTION).
  6. PF12 throws away the edits and re-reads the account; PF3 commits (SYNCPOINT) and returns to the caller. Each interaction ends by returning to CICS with transaction CAUP and the saved state.
Business rules
  • Account fields: active status Y or N; open, expiry, and reissue dates must be valid dates (YYYY-MM-DD); credit limit, cash credit limit, current balance, and current-cycle credit and debit must be signed amounts with two decimals.
  • Customer fields: first name, last name, city, state, and country required and alphabetic; middle name optional; address line 1 required; ZIP 5 digits and consistent with the state (first two ZIP digits checked against a state table); state a valid US state code; phone numbers in US format (area code, prefix, line number checked separately); SSN as three numeric parts, with the first part not 000, 666, or 900-999; date of birth a valid date that passes the birth-date check; FICO score between 300 and 850; EFT account ID 10 digits; primary card holder Y or N.
  • Nothing is saved without confirmation (PF5), and nothing is saved if either record changed since it was shown (optimistic locking).
  • Account and customer are saved together: if the customer can't be saved, the account change is rolled back.
Notes for modernization
  • Any user can change balances and limits from a screen: current balance, cycle credit and debit totals, and credit limits are editable with no extra authorization (and the main menu offers this screen to all users). Financial fields like the balance normally change only through posted transactions; decide with the business which fields should be editable and by whom.
  • Leaving the screen with PF3 sets the user type to "regular user" in the communication area, so an administrator passing through loses admin status for the rest of the session.
  • Well-designed update logic worth keeping: locking, the "changed by someone else" check, and the rollback map directly onto a database transaction with optimistic concurrency.
  • Most of the 3,400 lines of code are field validation and screen attribute handling, written out per field. A modern form with a validation library (and a shared US address/phone/SSN validator) replaces most of it; the business rules above are the part to carry over.
  • One screen updates two entities (account and customer); as an API this naturally becomes two resources, or one "account with holder" operation that keeps the single-transaction save.
  • Uses the CSUTLDTC routine (IBM CEEDAYS) for date checks - replace with the target language's date handling.
Program CSUTLDTC

CSUTLDTC is a small shared routine that checks whether a date is valid for a given format (for example YYYY-MM-DD). It asks the IBM Language Environment date service CEEDAYS to convert the date, and returns a readable result message and a severity as the return code. The account update, transaction add, and transaction report screens use it.

Inputs
  • The date to check (LS-DATE, 10 characters).
  • The date format, as a Language Environment picture string (LS-DATE-FORMAT, 10 characters, e.g. YYYY-MM-DD).
Outputs
  • An 80-character result message (LS-RESULT): the severity, the message number, a short result ("Date is valid", "Datevalue error", "Invalid month", "Nonnumeric data", ...), the date tested, and the format used.
  • The return code set to the severity from CEEDAYS: 0 when the date is valid.
Processing
  1. Copies the date and format into the variable-length strings CEEDAYS expects (A000-MAIN).
  2. Calls CEEDAYS, which converts the date to a day number (Lilian date) or reports why it can't.
  3. Translates the feedback code into a short message and returns it with the severity.
Business rules
  • A date is valid when CEEDAYS can convert it in the given format (real calendar dates only: month 1-12, a day that exists in that month, a supported year range).
  • The caller decides what to do with an invalid date; this routine only reports.
Notes for modernization
  • Depends on an IBM Language Environment service (CEEDAYS) that doesn't exist off the mainframe; replace it with the target language's date parsing (one line in Java, C#, or Python) - this routine then disappears.
  • Callers check the return code or the message text; when replacing it, make sure the callers' checks still mean the same thing (severity 0 = valid).

Where it connects to other work: XCTL PROGRAM COMEN01C (entry program of transaction CM00); XCTL PROGRAM COMEN01C (back to the caller)

Transaction CAVW

Expose as API suggested - Reads or updates business data behind a 3270 screen: keep the logic as a service (API) and replace the screen with a web interface.

1
programs
13
copybooks
1
transactions
1
screens (mapsets)
3
datasets
3
record layouts
1,745
lines of source
ScreensProgramsDatareadreadreadreadreadreadscreen COACTVWscreen COACTVWCOACTVWCCOACTVWCAWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDSAWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDSAWS.M2.CARDDEMO.CARDXREF.VSAM.AIX.PATHAWS.M2.CARDDEMO.CARDXREF.VSAM.AIX.PATHAWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDSAWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDS

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Transaction CAVW

Starting transaction CAVW runs program COACTVWC (from the CSD).

Program COACTVWC

  • Its comments: Program: COACTVWC.CBL / Layer: Business logic / Function: Accept and process Account View request
  • Screen: sends and receives mapset COACTVW
  • Reads file AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS
  • Reads file AWS.M2.CARDDEMO.CARDXREF.VSAM.AIX.PATH
  • Reads file AWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDS
  • Ends the turn and waits for the user; the next input runs transaction CAVW again
  • Transfers control (XCTL) to COMEN01C (entry program of transaction CM00)
  • Transfers control (XCTL) to COMEN01C (back to the caller)

Where it connects to other work: XCTL PROGRAM COMEN01C (entry program of transaction CM00); XCTL PROGRAM COMEN01C (back to the caller)

Transaction CB00

Expose as API suggested - Reads or updates business data behind a 3270 screen: keep the logic as a service (API) and replace the screen with a web interface.

1
programs
8
copybooks
1
transactions
1
screens (mapsets)
3
datasets
3
record layouts
774
lines of source
ScreensProgramsDataread/updateread/updatereadreadadd/readadd/readscreen COBIL00screen COBIL00COBIL00CCOBIL00CAWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDSAWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDSAWS.M2.CARDDEMO.CARDXREF.VSAM.AIX.PATHAWS.M2.CARDDEMO.CARDXREF.VSAM.AIX.PATHAWS.M2.CARDDEMO.TRANSACT.VSAM.KSDSAWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Transaction CB00

Starting transaction CB00 runs program COBIL00C (from the CSD).

Program COBIL00C

  • Its comments: Program : COBIL00C.CBL / Application : CardDemo / Type : CICS COBOL Program / Function : Bill Payment - Pay account balance in full and a
  • Screen: sends and receives mapset COBIL00
  • Reads and updates file AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS
  • Reads file AWS.M2.CARDDEMO.CARDXREF.VSAM.AIX.PATH
  • Adds records to and reads file AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS
  • Ends the turn and waits for the user; the next input runs transaction CB00 again
  • Transfers control (XCTL) to COMEN01C (entry program of transaction CM00)
  • Transfers control (XCTL) to COMEN01C (back to the caller)
  • Transfers control (XCTL) to COSGN00C (entry program of transaction CC00)

Where it connects to other work: XCTL PROGRAM COMEN01C (entry program of transaction CM00); XCTL PROGRAM COMEN01C (back to the caller); XCTL PROGRAM COSGN00C (entry program of transaction CC00)

Transaction CC00

Expose as API suggested - Reads or updates business data behind a 3270 screen: keep the logic as a service (API) and replace the screen with a web interface.

1
programs
6
copybooks
1
transactions
1
screens (mapsets)
1
datasets
1
record layouts
581
lines of source
ScreensProgramsDatareadreadscreen COSGN00screen COSGN00COSGN00CCOSGN00CAWS.M2.CARDDEMO.USRSEC.VSAM.KSDSAWS.M2.CARDDEMO.USRSEC.VSAM.KSDS

What it does

CC00 is how every CardDemo user starts: the sign-on screen. The user types a user ID and password; the program checks them against the user security file and sends administrators to the admin menu and everyone else to the main menu, carrying their identity and role to every screen after it. PF3 ends the session.

Step by step
  1. The user starts transaction CC00 (or returns to it from any screen with PF3); COSGN00C shows the sign-on screen with the date, time, and system name.
  2. The user enters a user ID and password and presses Enter. Both are required and are converted to upper case.
  3. The program reads the user's record from the user security file and compares the password.
  4. On a match it records the user ID and type in the communication area and transfers to the admin menu (transaction CA00, program COADM01C) for an administrator, or the main menu (CM00, COMEN01C) for a regular user.
  5. Otherwise it redisplays the screen with "Wrong Password", "User not found", or "Unable to verify the User", and waits for the next attempt.
What it needs
  • The user security file AWS.M2.CARDDEMO.USRSEC.VSAM.KSDS (user ID, names, password, user type), maintained by the admin user screens and loaded by batch.
What it produces
  • No data changes - only the user's identity and role in the communication area, which the menus and every function screen rely on.
Notes for modernization
  • Passwords are kept and compared in clear text, are case-insensitive, and are at most 8 characters; there's no lockout, and the messages reveal whether a user ID exists. Treat these as security findings for the client, separate from modernization.
  • On a modern platform sign-on is replaced by the organization's identity provider (single sign-on), and the user security file becomes user and role data there - this transaction is retired rather than converted.
  • Every other screen trusts the role set here; the target design should check authorization in the services, not only at sign-on.
Step-by-step walkthrough from the source
Transaction CC00

Starting transaction CC00 runs program COSGN00C (from the CSD).

Program COSGN00C

  • What it does: COSGN00C is the CardDemo sign-on screen. It asks for a user ID and password, checks them against the user security file, and sends the user on to the main menu - or, for administrators, the admin menu - passing who they are to every screen after it.
  • Screen: sends and receives mapset COSGN00
  • Reads file AWS.M2.CARDDEMO.USRSEC.VSAM.KSDS
  • Ends the turn and waits for the user; the next input runs transaction CC00 again
  • Transfers control (XCTL) to COADM01C (entry program of transaction CA00)
  • Transfers control (XCTL) to COMEN01C (entry program of transaction CM00)
Program COSGN00C

COSGN00C is the CardDemo sign-on screen. It asks for a user ID and password, checks them against the user security file, and sends the user on to the main menu - or, for administrators, the admin menu - passing who they are to every screen after it.

Inputs
  • Sign-on screen (mapset COSGN00, map COSGN0A): user ID and password typed by the user, and the key pressed (Enter, PF3, or another key).
  • User security file (CICS file USRSEC, AWS.M2.CARDDEMO.USRSEC.VSAM.KSDS, layout SEC-USER-DATA in CSUSR01Y): user ID, first and last name, password, and user type (A administrator, U regular user).
  • Communication area (CARDDEMO-COMMAREA, COCOM01Y) on the second and later interactions.
Outputs
  • The sign-on screen, with the title, transaction and program name, date, time, CICS application ID and system ID, and an error or guidance message.
  • On success, control passes (XCTL) to the main menu COMEN01C or the admin menu COADM01C with the communication area filled in: user ID, user type, and "came from" transaction CC00 / program COSGN00C.
  • On PF3, a plain "thank you" message and the end of the conversation.
Processing
  1. First entry (no communication area): sends an empty sign-on screen with the cursor on the user ID field (MAIN-PARA, SEND-SIGNON-SCREEN, POPULATE-HEADER-INFO).
  2. When the user presses Enter: receives the screen, requires both a user ID and a password, and converts both to upper case (PROCESS-ENTER-KEY).
  3. Reads the user's record from the security file by user ID and compares the password (READ-USER-SEC-FILE).
  4. If they match, fills in the communication area and transfers to COADM01C for an administrator or COMEN01C for anyone else.
  5. Otherwise redisplays the screen with "Wrong Password", "User not found", or "Unable to verify the User".
  6. PF3 ends the session with a thank-you message; any other key redisplays the screen with an invalid-key message.
  7. Ends each interaction by returning to CICS with transaction CC00, so the next keystroke comes back here (pseudo-conversational).
Business rules
  • User ID and password are both required.
  • Both are case-insensitive: each is upper-cased before the lookup and the comparison.
  • Passwords are compared directly with SEC-USR-PWD as stored in the file.
  • User type decides the destination: 'A' goes to the admin menu, everything else to the main menu.
Notes for modernization
  • Passwords are stored in clear text in the user security file (8 characters) and compared as plain text - a security finding in its own right; replace with the target platform's identity provider or at least salted hashes.
  • No lockout or attempt limit, and the messages tell a caller whether a user ID exists ("User not found" vs. "Wrong Password"), which helps guessing.
  • Passwords are effectively case-insensitive and limited to 8 characters.
  • The whole application relies on this program filling in the communication area (user ID and type); every other screen trusts it. A modern front end would use a session or token from a standard sign-in instead.
  • A good candidate to retire rather than convert: sign-on becomes the target platform's single sign-on, and the user file becomes identity data.

Where it connects to other work: XCTL PROGRAM COADM01C (entry program of transaction CA00); XCTL PROGRAM COMEN01C (entry program of transaction CM00)

Transaction CCDL

Expose as API suggested - Reads or updates business data behind a 3270 screen: keep the logic as a service (API) and replace the screen with a web interface.

1
programs
11
copybooks
1
transactions
1
screens (mapsets)
2
datasets
1
record layouts
1,180
lines of source
ScreensProgramsDatareadreadreadreadscreen COCRDSLscreen COCRDSLCOCRDSLCCOCRDSLCAWS.M2.CARDDEMO.CARDDATA.VSAM.AIX.PATHAWS.M2.CARDDEMO.CARDDATA.VSAM.AIX.PATHAWS.M2.CARDDEMO.CARDDATA.VSAM.KSDSAWS.M2.CARDDEMO.CARDDATA.VSAM.KSDS

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Transaction CCDL

Starting transaction CCDL runs program COCRDSLC (from the CSD).

Program COCRDSLC

  • Its comments: Program: COCRDSLC.CBL / Layer: Business logic / Function: Accept and process credit card detail request
  • Screen: sends and receives mapset COCRDSL
  • Reads file AWS.M2.CARDDEMO.CARDDATA.VSAM.AIX.PATH
  • Reads file AWS.M2.CARDDEMO.CARDDATA.VSAM.KSDS
  • Ends the turn and waits for the user; the next input runs transaction CCDL again
  • Transfers control (XCTL) to COCRDLIC (back to the caller)
  • Transfers control (XCTL) to COMEN01C (entry program of transaction CM00)
  • Transfers control (XCTL) to COMEN01C (back to the caller)

Where it connects to other work: XCTL PROGRAM COCRDLIC (back to the caller); XCTL PROGRAM COMEN01C (entry program of transaction CM00); XCTL PROGRAM COMEN01C (back to the caller)

Transaction CCLI

Expose as API suggested - Reads or updates business data behind a 3270 screen: keep the logic as a service (API) and replace the screen with a web interface.

1
programs
9
copybooks
1
transactions
1
screens (mapsets)
1
datasets
1
record layouts
2,149
lines of source
ScreensProgramsDatareadreadscreen COCRDLIscreen COCRDLICOCRDLICCOCRDLICAWS.M2.CARDDEMO.CARDDATA.VSAM.KSDSAWS.M2.CARDDEMO.CARDDATA.VSAM.KSDS

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Transaction CCLI

Starting transaction CCLI runs program COCRDLIC (from the CSD).

Program COCRDLIC

  • Its comments: Program: COCRDLIC.CBL / Layer: Business logic / Function: List Credit Cards / a) All cards if no context passed and admin user
  • Screen: sends and receives mapset COCRDLI
  • Reads file AWS.M2.CARDDEMO.CARDDATA.VSAM.KSDS
  • Ends the turn and waits for the user; the next input runs transaction CCLI again
  • Transfers control (XCTL) to COCRDLIC (VALUE of LIT-THISPGM via CCARD-NEXT-PROG)
  • Transfers control (XCTL) to COCRDSLC (entry program of transaction CCDL)
  • Transfers control (XCTL) to COCRDUPC (entry program of transaction CCUP)
  • Transfers control (XCTL) to COMEN01C (entry program of transaction CM00)

Where it connects to other work: XCTL PROGRAM COCRDSLC (entry program of transaction CCDL); XCTL PROGRAM COCRDUPC (entry program of transaction CCUP); XCTL PROGRAM COMEN01C (entry program of transaction CM00)

Transaction CCUP

Expose as API suggested - Reads or updates business data behind a 3270 screen: keep the logic as a service (API) and replace the screen with a web interface.

1
programs
11
copybooks
1
transactions
1
screens (mapsets)
1
datasets
2
record layouts
1,771
lines of source
ScreensProgramsDataread/updateread/updatescreen COCRDUPscreen COCRDUPCOCRDUPCCOCRDUPCAWS.M2.CARDDEMO.CARDDATA.VSAM.KSDSAWS.M2.CARDDEMO.CARDDATA.VSAM.KSDS

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Transaction CCUP

Starting transaction CCUP runs program COCRDUPC (from the CSD).

Program COCRDUPC

  • Its comments: Program: COCRDUPC.CBL / Layer: Business logic / Function: Accept and process credit card detail request
  • Screen: sends and receives mapset COCRDUP
  • Reads and updates file AWS.M2.CARDDEMO.CARDDATA.VSAM.KSDS
  • Ends the turn and waits for the user; the next input runs transaction CCUP again
  • Transfers control (XCTL) to COCRDLIC (back to the caller)
  • Transfers control (XCTL) to COMEN01C (entry program of transaction CM00)
  • Transfers control (XCTL) to COMEN01C (back to the caller)

Where it connects to other work: XCTL PROGRAM COCRDLIC (back to the caller); XCTL PROGRAM COMEN01C (entry program of transaction CM00); XCTL PROGRAM COMEN01C (back to the caller)

Transaction CDRA

Expose as API suggested - Reads or updates business data behind a 3270 screen: keep the logic as a service (API) and replace the screen with a web interface.

1
programs
4
system programs
1
copybooks
1
transactions
1
datasets
1
record layouts
514
lines of source
ScreensProgramsDatareadreadCOACCT01COACCT01AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDSAWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Transaction CDRA

Starting transaction CDRA runs program COACCT01 (from the CSD).

Program COACCT01

  • Reads file AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS
  • Calls MQCLOSE (IBM routine)
  • Calls MQGET (IBM routine)
  • Calls MQOPEN (IBM routine)
  • Calls MQPUT (IBM routine)

Transaction CDRD

Refactor suggested - Screen and navigation only (no data access): rebuild in the new user interface.

1
programs
4
system programs
1
transactions
409
lines of source
ScreensProgramsDataCODATE01CODATE01

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Transaction CDRD

Starting transaction CDRD runs program CODATE01 (from the CSD).

Program CODATE01

  • Calls MQCLOSE (IBM routine)
  • Calls MQGET (IBM routine)
  • Calls MQOPEN (IBM routine)
  • Calls MQPUT (IBM routine)

Transaction CDV1

Retire suggested - PROGRAM COCRDSEC isn't in the source: confirm with the client whether it's still used, and retire it if not.

1
transactions
0
lines of source

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Transaction CDV1

Starting transaction CDV1 runs program COCRDSEC (from the CSD).

Transaction CM00

Refactor suggested - Screen and navigation only (no data access): rebuild in the new user interface.

1
programs
7
copybooks
1
transactions
1
screens (mapsets)
751
lines of source
ScreensProgramsDatascreen COMEN01screen COMEN01COMEN01CCOMEN01C

What it does

CM00 is the main menu for regular users. It lists the eleven things a user can do - view or update accounts, list, view, or update credit cards, list, view, or add transactions, run transaction reports, pay bills, and view pending authorizations - and starts the chosen function. Each function returns here when the user presses PF3, and PF3 here returns to sign-on.

Step by step
  1. After sign-on (or on returning from a function), COMEN01C shows the numbered menu.
  2. The user types an option number and presses Enter.
  3. The program checks the number is between 1 and 11 and that the user's role allows the option, then transfers to that function's program - for example option 2 starts the account update (COACTUPC) and option 8 the transaction add (COTRN02C).
  4. For Pending Authorization View, it first checks the optional authorization module is installed, and says so if it isn't.
  5. PF3 returns to the sign-on screen.
What it needs
  • The user's identity and role from sign-on (communication area).
  • The menu options defined in copybook COMEN02Y - names, programs, and which user type may use each.
What it produces
  • No data changes - it only navigates to the eleven function screens.
Notes for modernization
  • Every option is open to every user: the menu supports admin-only options, but none is marked admin-only (Transaction Add's "Admin Only" label is commented out), so regular users can add transactions and update accounts, balances, and limits. Agree the intended permissions with the business and enforce them in the services.
  • The menu itself is navigation; in a web front end it becomes the application's navigation bar, and this transaction is retired.
  • The options table in a copybook is a simple, readable source for the target application's menu and permissions.
Step-by-step walkthrough from the source
Transaction CM00

Starting transaction CM00 runs program COMEN01C (from the CSD).

Program COMEN01C

  • What it does: COMEN01C is the main menu for regular CardDemo users. It lists eleven functions - account view and update, credit card list, view and update, transaction list, view and add, transaction reports, bill payment, and pending authorizations - and sends the user to the program for the option they pick.
  • Screen: sends and receives mapset COMEN01
  • Ends the turn and waits for the user; the next input runs transaction CM00 again
  • Transfers control (XCTL) to COACTUPC (entry program of transaction CAUP)
  • Transfers control (XCTL) to COACTVWC (entry program of transaction CAVW)
  • Transfers control (XCTL) to COBIL00C (entry program of transaction CB00)
  • Transfers control (XCTL) to COCRDLIC (entry program of transaction CCLI)
  • Transfers control (XCTL) to COCRDSLC (entry program of transaction CCDL)
  • Transfers control (XCTL) to COCRDUPC (entry program of transaction CCUP)
  • Transfers control (XCTL) to COPAUS0C (entry program of transaction CPVS)
  • Transfers control (XCTL) to CORPT00C (entry program of transaction CR00)
  • Transfers control (XCTL) to COSGN00C (entry program of transaction CC00)
  • Transfers control (XCTL) to COTRN00C (entry program of transaction CT00)
  • Transfers control (XCTL) to COTRN01C (entry program of transaction CT01)
  • Transfers control (XCTL) to COTRN02C (entry program of transaction CT02)
Program COMEN01C

COMEN01C is the main menu for regular CardDemo users. It lists eleven functions - account view and update, credit card list, view and update, transaction list, view and add, transaction reports, bill payment, and pending authorizations - and sends the user to the program for the option they pick.

Inputs
  • Communication area (CARDDEMO-COMMAREA, COCOM01Y) from the sign-on screen or the screen the user came back from: user ID and type, and whether the menu is being entered or re-entered.
  • Menu screen (mapset COMEN01, map COMEN1A): the option number typed and the key pressed.
  • Menu options table (CARDDEMO-MAIN-MENU-OPTIONS in copybook COMEN02Y): for each option its number, name, program, and the user type allowed ('U' or 'A').
Outputs
  • The menu screen: title, transaction and program name, date and time, the numbered options, and a message.
  • A transfer (XCTL) to the chosen program with the communication area, marked as coming from transaction CM00 / program COMEN01C.
  • PF3, or arriving without a communication area, returns to the sign-on screen (COSGN00C).
Processing
  1. Without a communication area, goes back to sign-on (MAIN-PARA, RETURN-TO-SIGNON-SCREEN).
  2. On first entry, marks the communication area as re-entered and shows the menu (SEND-MENU-SCREEN, POPULATE-HEADER-INFO, BUILD-MENU-OPTIONS).
  3. On Enter, receives the screen and reads the option number, right-aligning it and treating blanks as zeros (RECEIVE-MENU-SCREEN, PROCESS-ENTER-KEY).
  4. Rejects a non-numeric, zero, or too-large option, and an admin-only option for a regular user.
  5. For Pending Authorization View (COPAUS0C), first asks CICS whether the program is installed and says "not installed" if it isn't; for an option whose program name starts with DUMMY, shows "coming soon"; otherwise transfers to the option's program.
  6. PF3 returns to sign-on; any other key shows an invalid-key message. Each interaction ends by returning to CICS with transaction CM00.
Business rules
  • Valid options are 1 to the option count (11).
  • Access check: a regular user ('U') may not choose an option marked 'A' - but every option in the table is marked 'U', so in practice every user can reach every function, including Transaction Add (its "(Admin Only)" label is commented out in COMEN02Y).
  • The menu trusts the user type in the communication area set at sign-on.
  • Pending authorizations are an optional module: the menu checks it's installed before offering it.
Notes for modernization
  • Authorization is effectively off: the admin-only mechanism exists but no option uses it. Decide with the business which functions (adding transactions, account and card updates) should be restricted, and enforce it in the services rather than in the menu.
  • An invalid option number is still used to index the options table before the error takes effect (zero or above 11 reads outside the table); harmless in practice because the error stops the transfer, but sloppy.
  • The copybook holding these options is headed "Admin Menu Options" although it's the regular user menu.
  • A menu is navigation only: in a web front end it becomes the application's navigation, and this program is retired rather than converted.

Where it connects to other work: XCTL PROGRAM COACTUPC (entry program of transaction CAUP); XCTL PROGRAM COACTVWC (entry program of transaction CAVW); XCTL PROGRAM COBIL00C (entry program of transaction CB00); XCTL PROGRAM COCRDLIC (entry program of transaction CCLI); XCTL PROGRAM COCRDSLC (entry program of transaction CCDL); XCTL PROGRAM COCRDUPC (entry program of transaction CCUP); XCTL PROGRAM COPAUS0C (entry program of transaction CPVS); XCTL PROGRAM CORPT00C (entry program of transaction CR00); XCTL PROGRAM COSGN00C (entry program of transaction CC00); XCTL PROGRAM COTRN00C (entry program of transaction CT00); XCTL PROGRAM COTRN01C (entry program of transaction CT01); XCTL PROGRAM COTRN02C (entry program of transaction CT02)

Transaction CP00

Rehost suggested - 905 lines with IMS or heavy logic: rehost, then expose services.

1
programs
4
system programs
8
copybooks
1
transactions
3
datasets
2
IMS segments
3
record layouts
905
lines of source
ScreensProgramsDatareadreadreadreadreadreadaddaddadd/read/updateadd/read/updateCOPAUA0CCOPAUA0CAWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDSAWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDSAWS.M2.CARDDEMO.CARDXREF.VSAM.KSDSAWS.M2.CARDDEMO.CARDXREF.VSAM.KSDSAWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDSAWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDSPAUTDTL1PAUTDTL1PAUTSUM0PAUTSUM0

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Transaction CP00

Starting transaction CP00 runs program COPAUA0C (from the CSD).

Program COPAUA0C

  • Its comments: Program : COPAUA0C.CBL / Application : CardDemo - Authorization Module / Type : CICS COBOL IMS MQ Program / Function : Card Authorization Decision Program
  • Reads file AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS
  • Reads file AWS.M2.CARDDEMO.CARDXREF.VSAM.KSDS
  • Reads file AWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDS
  • Adds records to IMS segment PAUTDTL1
  • Adds records to and reads and updates IMS segment PAUTSUM0
  • Calls MQCLOSE (IBM routine)
  • Calls MQGET (IBM routine)
  • Calls MQOPEN (IBM routine)
  • Calls MQPUT1 (IBM routine)

Transaction CPVD

Rehost suggested - 1,461 lines with IMS or heavy logic: rehost, then expose services.

2
programs
8
copybooks
1
DCLGENs
1
transactions
1
screens (mapsets)
1
Db2 tables
2
IMS segments
1,461
lines of source
ScreensProgramsDataread/updateread/updatereadreadadd/updateadd/updatescreen COPAU01screen COPAU01COPAUS1CCOPAUS1CCOPAUS2C (LINK)COPAUS2C (LINK)PAUTDTL1PAUTDTL1PAUTSUM0PAUTSUM0AUTHFRDSAUTHFRDS

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Transaction CPVD

Starting transaction CPVD runs program COPAUS1C (from the CSD).

Program COPAUS1C

  • Its comments: Program : COPAUS1C.CBL / Application : CardDemo - Authorization Module / Type : CICS COBOL IMS BMS Program / Function : Detail View of Authorization Message
  • Screen: sends and receives mapset COPAU01
  • Reads and updates IMS segment PAUTDTL1
  • Reads IMS segment PAUTSUM0
  • Links COPAUS2C
  • Ends the turn and waits for the user; the next input runs transaction CPVD again
  • Transfers control (XCTL) to COPAUS0C (entry program of transaction CPVS)

Program COPAUS2C (LINK from its caller)

  • Its comments: Program : COPAUS2C.CBL / Application : CardDemo - Authorization Module / Type : CICS COBOL IMS DB2 Program / Function : Mark Authorization Message Fraud
  • Adds records to and updates Db2 table AUTHFRDS

Where it connects to other work: XCTL PROGRAM COPAUS0C (entry program of transaction CPVS)

Transaction CPVS

Rehost suggested - 2,218 lines with IMS or heavy logic: rehost, then expose services.

1
programs
12
copybooks
1
transactions
1
screens (mapsets)
3
datasets
2
IMS segments
3
record layouts
2,218
lines of source
ScreensProgramsDatareadreadreadreadreadreadreadreadreadreadscreen COPAU00screen COPAU00COPAUS0CCOPAUS0CAWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDSAWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDSAWS.M2.CARDDEMO.CARDXREF.VSAM.AIX.PATHAWS.M2.CARDDEMO.CARDXREF.VSAM.AIX.PATHAWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDSAWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDSPAUTDTL1PAUTDTL1PAUTSUM0PAUTSUM0

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Transaction CPVS

Starting transaction CPVS runs program COPAUS0C (from the CSD).

Program COPAUS0C

  • Its comments: Program : COPAUS0C.CBL / Application : CardDemo - Authorization Module / Type : CICS COBOL IMS BMS Program / Function : Summary View of Authoriation Messages
  • Screen: sends and receives mapset COPAU00
  • Reads file AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS
  • Reads file AWS.M2.CARDDEMO.CARDXREF.VSAM.AIX.PATH
  • Reads file AWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDS
  • Reads IMS segment PAUTDTL1
  • Reads IMS segment PAUTSUM0
  • Ends the turn and waits for the user; the next input runs transaction CPVS again
  • Transfers control (XCTL) to COMEN01C (entry program of transaction CM00)
  • Transfers control (XCTL) to COPAUS0C (VALUE of WS-PGM-AUTH-SMRY via CDEMO-TO-PROGRAM)
  • Transfers control (XCTL) to COPAUS1C (entry program of transaction CPVD)
  • Transfers control (XCTL) to COSGN00C (entry program of transaction CC00)

Where it connects to other work: XCTL PROGRAM COMEN01C (entry program of transaction CM00); XCTL PROGRAM COPAUS1C (entry program of transaction CPVD); XCTL PROGRAM COSGN00C (entry program of transaction CC00)

Transaction CR00

Refactor suggested - Screen and navigation only (no data access): rebuild in the new user interface.

2
programs
1
system programs
6
copybooks
1
transactions
1
screens (mapsets)
1,122
lines of source
ScreensProgramsDatascreen CORPT00screen CORPT00CORPT00CCORPT00CCSUTLDTC (CALL)CSUTLDTC (CALL)

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Transaction CR00

Starting transaction CR00 runs program CORPT00C (from the CSD).

Program CORPT00C

  • Its comments: Program : CORPT00C.CBL / Application : CardDemo / Type : CICS COBOL Program / Function : Print Transaction reports by submitting batch
  • Screen: sends and receives mapset CORPT00
  • Calls CSUTLDTC
  • Ends the turn and waits for the user; the next input runs transaction CR00 again
  • Transfers control (XCTL) to COMEN01C (entry program of transaction CM00)
  • Transfers control (XCTL) to COSGN00C (entry program of transaction CC00)

Program CSUTLDTC (CALL from its caller)

  • What it does: CSUTLDTC is a small shared routine that checks whether a date is valid for a given format (for example YYYY-MM-DD). It asks the IBM Language Environment date service CEEDAYS to convert the date, and returns a readable result message and a severity as the return code. The account update, transaction add, and transaction report screens use it.
  • Calls CEEDAYS (IBM routine)
Program CSUTLDTC

CSUTLDTC is a small shared routine that checks whether a date is valid for a given format (for example YYYY-MM-DD). It asks the IBM Language Environment date service CEEDAYS to convert the date, and returns a readable result message and a severity as the return code. The account update, transaction add, and transaction report screens use it.

Inputs
  • The date to check (LS-DATE, 10 characters).
  • The date format, as a Language Environment picture string (LS-DATE-FORMAT, 10 characters, e.g. YYYY-MM-DD).
Outputs
  • An 80-character result message (LS-RESULT): the severity, the message number, a short result ("Date is valid", "Datevalue error", "Invalid month", "Nonnumeric data", ...), the date tested, and the format used.
  • The return code set to the severity from CEEDAYS: 0 when the date is valid.
Processing
  1. Copies the date and format into the variable-length strings CEEDAYS expects (A000-MAIN).
  2. Calls CEEDAYS, which converts the date to a day number (Lilian date) or reports why it can't.
  3. Translates the feedback code into a short message and returns it with the severity.
Business rules
  • A date is valid when CEEDAYS can convert it in the given format (real calendar dates only: month 1-12, a day that exists in that month, a supported year range).
  • The caller decides what to do with an invalid date; this routine only reports.
Notes for modernization
  • Depends on an IBM Language Environment service (CEEDAYS) that doesn't exist off the mainframe; replace it with the target language's date parsing (one line in Java, C#, or Python) - this routine then disappears.
  • Callers check the return code or the message text; when replacing it, make sure the callers' checks still mean the same thing (severity 0 = valid).

Where it connects to other work: XCTL PROGRAM COMEN01C (entry program of transaction CM00); XCTL PROGRAM COSGN00C (entry program of transaction CC00)

Transaction CT00

Expose as API suggested - Reads or updates business data behind a 3270 screen: keep the logic as a service (API) and replace the screen with a web interface.

1
programs
6
copybooks
1
transactions
1
screens (mapsets)
1
datasets
1
record layouts
1,775
lines of source
ScreensProgramsDatareadreadscreen COTRN00screen COTRN00COTRN00CCOTRN00CAWS.M2.CARDDEMO.TRANSACT.VSAM.KSDSAWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Transaction CT00

Starting transaction CT00 runs program COTRN00C (from the CSD).

Program COTRN00C

  • Its comments: Program : COTRN00C.CBL / Application : CardDemo / Type : CICS COBOL Program / Function : List Transactions from TRANSACT file
  • Screen: sends and receives mapset COTRN00
  • Reads file AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS
  • Ends the turn and waits for the user; the next input runs transaction CT00 again
  • Transfers control (XCTL) to COMEN01C (entry program of transaction CM00)
  • Transfers control (XCTL) to COSGN00C (entry program of transaction CC00)
  • Transfers control (XCTL) to COTRN01C (entry program of transaction CT01)

Where it connects to other work: XCTL PROGRAM COMEN01C (entry program of transaction CM00); XCTL PROGRAM COSGN00C (entry program of transaction CC00); XCTL PROGRAM COTRN01C (entry program of transaction CT01)

Transaction CT01

Expose as API suggested - Reads or updates business data behind a 3270 screen: keep the logic as a service (API) and replace the screen with a web interface.

1
programs
6
copybooks
1
transactions
1
screens (mapsets)
1
datasets
1
record layouts
831
lines of source
ScreensProgramsDatareadreadscreen COTRN01screen COTRN01COTRN01CCOTRN01CAWS.M2.CARDDEMO.TRANSACT.VSAM.KSDSAWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Transaction CT01

Starting transaction CT01 runs program COTRN01C (from the CSD).

Program COTRN01C

  • Its comments: Program : COTRN01C.CBL / Application : CardDemo / Type : CICS COBOL Program / Function : View a Transaction from TRANSACT file
  • Screen: sends and receives mapset COTRN01
  • Reads file AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS
  • Ends the turn and waits for the user; the next input runs transaction CT01 again
  • Transfers control (XCTL) to COMEN01C (entry program of transaction CM00)
  • Transfers control (XCTL) to COMEN01C (back to the caller)
  • Transfers control (XCTL) to COSGN00C (entry program of transaction CC00)
  • Transfers control (XCTL) to COTRN00C (entry program of transaction CT00)
  • Transfers control (XCTL) to COTRN00C (back to the caller)

Where it connects to other work: XCTL PROGRAM COMEN01C (entry program of transaction CM00); XCTL PROGRAM COMEN01C (back to the caller); XCTL PROGRAM COSGN00C (entry program of transaction CC00); XCTL PROGRAM COTRN00C (entry program of transaction CT00); XCTL PROGRAM COTRN00C (back to the caller)

Transaction CT02

Expose as API suggested - Reads or updates business data behind a 3270 screen: keep the logic as a service (API) and replace the screen with a web interface.

2
programs
1
system programs
8
copybooks
1
transactions
1
screens (mapsets)
3
datasets
2
record layouts
1,381
lines of source
ScreensProgramsDatareadreadreadreadadd/readadd/readscreen COTRN02screen COTRN02COTRN02CCOTRN02CCSUTLDTC (CALL)CSUTLDTC (CALL)AWS.M2.CARDDEMO.CARDXREF.VSAM.AIX.PATHAWS.M2.CARDDEMO.CARDXREF.VSAM.AIX.PATHAWS.M2.CARDDEMO.CARDXREF.VSAM.KSDSAWS.M2.CARDDEMO.CARDXREF.VSAM.KSDSAWS.M2.CARDDEMO.TRANSACT.VSAM.KSDSAWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS

What it does

CT02 lets a user enter a card transaction by hand. The user picks the card (by account or card number), types the transaction details - type, category, source, description, amount, dates, merchant - confirms with Y, and the transaction is written to the transaction master with the next transaction number.

Step by step
  1. From the main menu (option 8), or from a transaction list with a card already selected, COTRN02C shows the add-transaction form.
  2. The user enters an account ID or a card number; the program looks up the other in the card cross-reference.
  3. The user fills in the transaction fields and presses Enter. Each field is checked in turn (required, numeric codes, amount format, real dates, numeric merchant ID) and the first problem is shown.
  4. The user confirms with Y. The program reads the highest transaction ID on the master, adds 1, and writes the new transaction, then shows the new transaction ID.
  5. PF5 copies the details of the most recent transaction into the form, PF4 clears it, and PF3 returns to the main menu.
What it needs
  • The card cross-reference (CARDXREF.VSAM.KSDS and its account index) and the transaction master (TRANSACT.VSAM.KSDS).
  • The date-checking routine CSUTLDTC.
What it produces
  • A new record on the transaction master - which the transaction report (TRANREPT), statements (CREASTMT), and the backup and combine jobs (TRANBKP, COMBTRAN, CBEXPORT) all read.
Notes for modernization
  • Manually added transactions skip posting: they aren't checked against the account (status, credit limit, expiration) and don't update the account balance or category balances, so balances, interest, and statements won't reflect them. Confirm with the business what this screen is for (adjustments? testing?) and route it through the same posting logic as the daily batch.
  • Next-ID-plus-one numbering can collide when two users add at once; use a database sequence.
  • Type and category codes aren't checked against the reference files, and the processing date is typed in rather than set by the system.
  • Available to all users (the menu's "Admin Only" restriction is commented out).
  • As an API this becomes "post a transaction", shared with batch posting so online and batch apply the same rules.
Step-by-step walkthrough from the source
Transaction CT02

Starting transaction CT02 runs program COTRN02C (from the CSD).

Program COTRN02C

  • What it does: COTRN02C is the "add transaction" screen. A user identifies a card (by account number or card number), types in a transaction - type, category, source, description, amount, original and processing dates, merchant details - confirms with Y, and the program writes it straight to the transaction master file with the next transaction number.
  • Screen: sends and receives mapset COTRN02
  • Reads file AWS.M2.CARDDEMO.CARDXREF.VSAM.AIX.PATH
  • Reads file AWS.M2.CARDDEMO.CARDXREF.VSAM.KSDS
  • Adds records to and reads file AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS
  • Calls CSUTLDTC
  • Ends the turn and waits for the user; the next input runs transaction CT02 again
  • Transfers control (XCTL) to COMEN01C (entry program of transaction CM00)
  • Transfers control (XCTL) to COMEN01C (back to the caller)
  • Transfers control (XCTL) to COSGN00C (entry program of transaction CC00)

Program CSUTLDTC (CALL from its caller)

  • What it does: CSUTLDTC is a small shared routine that checks whether a date is valid for a given format (for example YYYY-MM-DD). It asks the IBM Language Environment date service CEEDAYS to convert the date, and returns a readable result message and a severity as the return code. The account update, transaction add, and transaction report screens use it.
  • Calls CEEDAYS (IBM routine)
Program COTRN02C

COTRN02C is the "add transaction" screen. A user identifies a card (by account number or card number), types in a transaction - type, category, source, description, amount, original and processing dates, merchant details - confirms with Y, and the program writes it straight to the transaction master file with the next transaction number.

Inputs
  • Add transaction screen (mapset COTRN02): account ID or card number, transaction type and category codes, source, description, amount (format -99999999.99), original and processing dates (YYYY-MM-DD), merchant ID, name, city, and ZIP, and the confirmation (Y/N); keys Enter, PF3 (back), PF4 (clear), PF5 (copy the last transaction's details).
  • Communication area (COCOM01Y), optionally carrying a card selected on another screen.
  • Card cross-reference - by account (CICS file CXACAIX, the alternate index) or by card number (CICS file CCXREF) - to fill in the other of the two.
  • Transaction master (CICS file TRANSACT) - browsed backwards from the end to find the highest transaction ID.
Outputs
  • A new record on the transaction master (TRAN-RECORD, CVTRA05Y).
  • The screen with "Transaction added successfully. Your Tran ID is ..." or the first validation error found.
Processing
  1. On first entry, shows the screen; if a card was passed in from another screen, starts from it (MAIN-PARA, SEND-TRNADD-SCREEN).
  2. On Enter, checks the account or card number and looks up the other one in the cross-reference (VALIDATE-INPUT-KEY-FIELDS, READ-CXACAIX-FILE, READ-CCXREF-FILE).
  3. Checks the transaction fields: all required; type and category numeric; amount in the form sign, 8 digits, point, 2 digits; both dates in YYYY-MM-DD form and real dates (checked with CSUTLDTC); merchant ID numeric (VALIDATE-INPUT-DATA-FIELDS).
  4. If the user confirmed with Y, finds the highest transaction ID by reading the last record of the transaction master, adds 1, and writes the new transaction (ADD-TRANSACTION, STARTBR/READPREV/ENDBR-TRANSACT-FILE, WRITE-TRANSACT-FILE); otherwise asks for confirmation.
  5. PF5 fills the form with the details of the most recently added transaction (COPY-LAST-TRAN-DATA); PF4 clears it; PF3 returns to the calling program or the main menu. Each interaction ends by returning to CICS with transaction CT02.
Business rules
  • An account or a card number is required, and it must exist in the cross-reference; the screen fills in the other.
  • Every transaction field is required. Type and category codes only have to be numeric - they aren't checked against the transaction type and category files.
  • Amount must be entered as a signed number with exactly two decimals (e.g. +00000100.00).
  • Dates must be valid calendar dates, except that one particular result from the date check (message 2513) is let through.
  • Explicit confirmation (Y) is required before anything is written.
  • New transaction ID = highest existing transaction ID + 1.
  • Validation stops at the first error and shows only that one.
Notes for modernization
  • Added transactions don't update balances: the transaction goes straight onto the master file without the posting job's checks (card and account status, credit limit, expiration) and without updating the account balance or the category balances. Interest and statements will disagree with the balance for any account with manually added transactions - confirm with the business whether this screen is meant for adjustments that are posted some other way.
  • Transaction IDs can collide: "read the highest ID, add 1, write" isn't safe with two users adding at the same time - one of them gets "Tran ID already exist". Use a database sequence or identity column.
  • The user types in the processing date as well as the original date; normally the system sets the processing date.
  • Open to every user from the main menu (its "Admin Only" label is commented out).
  • Field-by-field validation with one error at a time maps to a standard form with validation; the "add a transaction" logic itself belongs in the same service as batch posting, so both apply the same rules.
Program CSUTLDTC

CSUTLDTC is a small shared routine that checks whether a date is valid for a given format (for example YYYY-MM-DD). It asks the IBM Language Environment date service CEEDAYS to convert the date, and returns a readable result message and a severity as the return code. The account update, transaction add, and transaction report screens use it.

Inputs
  • The date to check (LS-DATE, 10 characters).
  • The date format, as a Language Environment picture string (LS-DATE-FORMAT, 10 characters, e.g. YYYY-MM-DD).
Outputs
  • An 80-character result message (LS-RESULT): the severity, the message number, a short result ("Date is valid", "Datevalue error", "Invalid month", "Nonnumeric data", ...), the date tested, and the format used.
  • The return code set to the severity from CEEDAYS: 0 when the date is valid.
Processing
  1. Copies the date and format into the variable-length strings CEEDAYS expects (A000-MAIN).
  2. Calls CEEDAYS, which converts the date to a day number (Lilian date) or reports why it can't.
  3. Translates the feedback code into a short message and returns it with the severity.
Business rules
  • A date is valid when CEEDAYS can convert it in the given format (real calendar dates only: month 1-12, a day that exists in that month, a supported year range).
  • The caller decides what to do with an invalid date; this routine only reports.
Notes for modernization
  • Depends on an IBM Language Environment service (CEEDAYS) that doesn't exist off the mainframe; replace it with the target language's date parsing (one line in Java, C#, or Python) - this routine then disappears.
  • Callers check the return code or the message text; when replacing it, make sure the callers' checks still mean the same thing (severity 0 = valid).

Where it connects to other work: XCTL PROGRAM COMEN01C (entry program of transaction CM00); XCTL PROGRAM COMEN01C (back to the caller); XCTL PROGRAM COSGN00C (entry program of transaction CC00)

Transaction CTLI

Expose as API suggested - Reads or updates business data behind a 3270 screen: keep the logic as a service (API) and replace the screen with a web interface.

1
programs
1
system programs
11
copybooks
1
DCLGENs
1
transactions
1
screens (mapsets)
1
Db2 tables
2,674
lines of source
ScreensProgramsDataread/update/deleteread/update/deletescreen COTRTLIscreen COTRTLICOTRTLICCOTRTLICTRANSACTION_TYPETRANSACTION_TYPE

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Transaction CTLI

Starting transaction CTLI runs program COTRTLIC (from the CSD).

Program COTRTLIC

  • Its comments: Program: COTRTLIC.CBL / Layer: Business logic / Function: List Transaction Type for updates and deletes / Demonstrates paging with cursors in Db2
  • Screen: sends and receives mapset COTRTLI
  • Reads and updates and deletes from Db2 table TRANSACTION_TYPE
  • Calls DSNTIAC (IBM routine)
  • Ends the turn and waits for the user; the next input runs transaction CTLI again
  • Transfers control (XCTL) to COADM01C (entry program of transaction CA00)
  • Transfers control (XCTL) to COADM01C (back to the caller)
  • Transfers control (XCTL) to COTRTUPC (entry program of transaction CTTU)
  • Transfers control (XCTL) to COTRTUPC (entry program of transaction CTTU)

Where it connects to other work: XCTL PROGRAM COADM01C (entry program of transaction CA00); XCTL PROGRAM COADM01C (back to the caller); XCTL PROGRAM COTRTUPC (entry program of transaction CTTU)

Transaction CTTU

Expose as API suggested - Reads or updates business data behind a 3270 screen: keep the logic as a service (API) and replace the screen with a web interface.

1
programs
11
copybooks
2
DCLGENs
1
transactions
1
screens (mapsets)
1
Db2 tables
1,851
lines of source
ScreensProgramsDataadd/read/update/deleteadd/read/update/deletescreen COTRTUPscreen COTRTUPCOTRTUPCCOTRTUPCTRANSACTION_TYPETRANSACTION_TYPE

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Transaction CTTU

Starting transaction CTTU runs program COTRTUPC (from the CSD).

Program COTRTUPC

  • Its comments: Program: COTRTUPC.CBL / Layer: Business logic / Function: Accept and process TRANSACTION TYPE UPDATE
  • Screen: sends and receives mapset COTRTUP
  • Adds records to and reads and updates and deletes from Db2 table TRANSACTION_TYPE
  • Ends the turn and waits for the user; the next input runs transaction CTTU again
  • Transfers control (XCTL) to COADM01C (entry program of transaction CA00)
  • Transfers control (XCTL) to COADM01C (back to the caller)
  • Transfers control (XCTL) to COTRTLIC (back to the caller)

Where it connects to other work: XCTL PROGRAM COADM01C (entry program of transaction CA00); XCTL PROGRAM COADM01C (back to the caller); XCTL PROGRAM COTRTLIC (back to the caller)

Transaction CU00

Expose as API suggested - Reads or updates business data behind a 3270 screen: keep the logic as a service (API) and replace the screen with a web interface.

1
programs
6
copybooks
1
transactions
1
screens (mapsets)
1
datasets
1
record layouts
1,769
lines of source
ScreensProgramsDatareadreadscreen COUSR00screen COUSR00COUSR00CCOUSR00CAWS.M2.CARDDEMO.USRSEC.VSAM.KSDSAWS.M2.CARDDEMO.USRSEC.VSAM.KSDS

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Transaction CU00

Starting transaction CU00 runs program COUSR00C (from the CSD).

Program COUSR00C

  • Its comments: Program : COUSR00C.CBL / Application : CardDemo / Type : CICS COBOL Program / Function : List all users from USRSEC file
  • Screen: sends and receives mapset COUSR00
  • Reads file AWS.M2.CARDDEMO.USRSEC.VSAM.KSDS
  • Ends the turn and waits for the user; the next input runs transaction CU00 again
  • Transfers control (XCTL) to COADM01C (entry program of transaction CA00)
  • Transfers control (XCTL) to COSGN00C (entry program of transaction CC00)
  • Transfers control (XCTL) to COUSR02C (entry program of transaction CU02)
  • Transfers control (XCTL) to COUSR03C (entry program of transaction CU03)

Where it connects to other work: XCTL PROGRAM COADM01C (entry program of transaction CA00); XCTL PROGRAM COSGN00C (entry program of transaction CC00); XCTL PROGRAM COUSR02C (entry program of transaction CU02); XCTL PROGRAM COUSR03C (entry program of transaction CU03)

Transaction CU01

Expose as API suggested - Reads or updates business data behind a 3270 screen: keep the logic as a service (API) and replace the screen with a web interface.

1
programs
6
copybooks
1
transactions
1
screens (mapsets)
1
datasets
1
record layouts
573
lines of source
ScreensProgramsDataaddaddscreen COUSR01screen COUSR01COUSR01CCOUSR01CAWS.M2.CARDDEMO.USRSEC.VSAM.KSDSAWS.M2.CARDDEMO.USRSEC.VSAM.KSDS

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Transaction CU01

Starting transaction CU01 runs program COUSR01C (from the CSD).

Program COUSR01C

  • Its comments: Program : COUSR01C.CBL / Application : CardDemo / Type : CICS COBOL Program / Function : Add a new Regular/Admin user to USRSEC file
  • Screen: sends and receives mapset COUSR01
  • Adds records to file AWS.M2.CARDDEMO.USRSEC.VSAM.KSDS
  • Ends the turn and waits for the user; the next input runs transaction CU01 again
  • Transfers control (XCTL) to COADM01C (entry program of transaction CA00)
  • Transfers control (XCTL) to COSGN00C (entry program of transaction CC00)

Where it connects to other work: XCTL PROGRAM COADM01C (entry program of transaction CA00); XCTL PROGRAM COSGN00C (entry program of transaction CC00)

Transaction CU02

Expose as API suggested - Reads or updates business data behind a 3270 screen: keep the logic as a service (API) and replace the screen with a web interface.

1
programs
6
copybooks
1
transactions
1
screens (mapsets)
1
datasets
1
record layouts
683
lines of source
ScreensProgramsDataread/updateread/updatescreen COUSR02screen COUSR02COUSR02CCOUSR02CAWS.M2.CARDDEMO.USRSEC.VSAM.KSDSAWS.M2.CARDDEMO.USRSEC.VSAM.KSDS

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Transaction CU02

Starting transaction CU02 runs program COUSR02C (from the CSD).

Program COUSR02C

  • Its comments: Program : COUSR02C.CBL / Application : CardDemo / Type : CICS COBOL Program / Function : Update a user in USRSEC file
  • Screen: sends and receives mapset COUSR02
  • Reads and updates file AWS.M2.CARDDEMO.USRSEC.VSAM.KSDS
  • Ends the turn and waits for the user; the next input runs transaction CU02 again
  • Transfers control (XCTL) to COADM01C (entry program of transaction CA00)
  • Transfers control (XCTL) to COADM01C (back to the caller)
  • Transfers control (XCTL) to COSGN00C (entry program of transaction CC00)
  • Transfers control (XCTL) to COUSR00C (back to the caller)

Where it connects to other work: XCTL PROGRAM COADM01C (entry program of transaction CA00); XCTL PROGRAM COADM01C (back to the caller); XCTL PROGRAM COSGN00C (entry program of transaction CC00); XCTL PROGRAM COUSR00C (back to the caller)

Transaction CU03

Expose as API suggested - Reads or updates business data behind a 3270 screen: keep the logic as a service (API) and replace the screen with a web interface.

1
programs
6
copybooks
1
transactions
1
screens (mapsets)
1
datasets
1
record layouts
603
lines of source
ScreensProgramsDataread/deleteread/deletescreen COUSR03screen COUSR03COUSR03CCOUSR03CAWS.M2.CARDDEMO.USRSEC.VSAM.KSDSAWS.M2.CARDDEMO.USRSEC.VSAM.KSDS

A reviewed plain-English summary isn't available yet; the step-by-step walkthrough below is built from the source.

Step-by-step walkthrough from the source
Transaction CU03

Starting transaction CU03 runs program COUSR03C (from the CSD).

Program COUSR03C

  • Its comments: Program : COUSR03C.CBL / Application : CardDemo / Type : CICS COBOL Program / Function : Delete a user from USRSEC file
  • Screen: sends and receives mapset COUSR03
  • Reads and deletes from file AWS.M2.CARDDEMO.USRSEC.VSAM.KSDS
  • Ends the turn and waits for the user; the next input runs transaction CU03 again
  • Transfers control (XCTL) to COADM01C (entry program of transaction CA00)
  • Transfers control (XCTL) to COADM01C (back to the caller)
  • Transfers control (XCTL) to COSGN00C (entry program of transaction CC00)
  • Transfers control (XCTL) to COUSR00C (back to the caller)

Where it connects to other work: XCTL PROGRAM COADM01C (entry program of transaction CA00); XCTL PROGRAM COADM01C (back to the caller); XCTL PROGRAM COSGN00C (entry program of transaction CC00); XCTL PROGRAM COUSR00C (back to the caller)

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.

DataCBACT01CCBACT02CCBACT03CCBACT04CCBCUS01CCBEXPORTCBIMPORTCBPAUP0CCBSTM03ACBSTM03BCBTRN02CCBTRN03CCOACCT01COACTUPCCOACTVWCCOBIL00CCOBTUPDTCOCRDLICCOCRDSLCCOCRDUPCCOPAUA0CCOPAUS0CCOPAUS1CCOPAUS2CCOSGN00CCOTRN00CCOTRN01CCOTRN02CCOTRTLICCOTRTUPCCOUSR00CCOUSR01CCOUSR02CCOUSR03CDBUNLDGSPAUDBLODPAUDBUNL
AWS.M2.CARDDEMO.ACCTDATA.ARRYPS fileC
AWS.M2.CARDDEMO.ACCTDATA.IMPORT fileC
AWS.M2.CARDDEMO.ACCTDATA.PSCOMP fileC
AWS.M2.CARDDEMO.ACCTDATA.VBPS fileC
AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS fileRRURRRURRURRURR
AWS.M2.CARDDEMO.CARDDATA.VSAM.AIX.PATH fileR
AWS.M2.CARDDEMO.CARDDATA.VSAM.KSDS fileRRRRRU
AWS.M2.CARDDEMO.CARDXREF.IMPORT fileC
AWS.M2.CARDDEMO.CARDXREF.VSAM.AIX.PATH fileRRRRR
AWS.M2.CARDDEMO.CARDXREF.VSAM.KSDS fileRRRRRRRR
AWS.M2.CARDDEMO.CUSTDATA.IMPORT fileC
AWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDS fileRRRRURRR
AWS.M2.CARDDEMO.DALYREJS fileC
AWS.M2.CARDDEMO.DALYTRAN.PS fileR
AWS.M2.CARDDEMO.DATEPARM fileR
AWS.M2.CARDDEMO.DISCGRP.VSAM.KSDS fileR
AWS.M2.CARDDEMO.EXPORT.DATA fileCR
AWS.M2.CARDDEMO.IMPORT.ERRORS fileC
AWS.M2.CARDDEMO.PAUTDB.CHILD.FILEO fileRC
AWS.M2.CARDDEMO.PAUTDB.ROOT.FILEO fileRC
AWS.M2.CARDDEMO.STATEMNT.HTML fileC
AWS.M2.CARDDEMO.STATEMNT.PS fileC
AWS.M2.CARDDEMO.SYSTRAN fileC
AWS.M2.CARDDEMO.TCATBALF.VSAM.KSDS fileRCRU
AWS.M2.CARDDEMO.TRANCATG.VSAM.KSDS fileR
AWS.M2.CARDDEMO.TRANREPT fileC
AWS.M2.CARDDEMO.TRANSACT.DALY fileR
AWS.M2.CARDDEMO.TRANSACT.IMPORT fileC
AWS.M2.CARDDEMO.TRANSACT.VSAM.KSDS fileRCCRRRCR
AWS.M2.CARDDEMO.TRANTYPE.VSAM.KSDS fileR
AWS.M2.CARDDEMO.TRXFL.VSAM.KSDS fileR
AWS.M2.CARDDEMO.USRSEC.VSAM.KSDS fileRRCRURD
INPFILE fileR
(PCB PADFLPCB) segmentC
(PCB PASFLPCB) segmentC
PAUTDTL1 segmentRDCRRURCR
PAUTSUM0 segmentRDCRURRRCRR
AUTHFRDS tableCU
TRANSACTION_TYPE tableCUDRUDCRUD

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".

AUTHFRDS: DCLAUTHFRDS

FieldPICBytesValuesSet by
DCLAUTHFRDS1‑204
    CARD-NUMX(16)1‑16COPAUS2C
    AUTH-TSX(26)17‑42COPAUS2C
    AUTH-TYPEX(4)43‑46COPAUS2C
    CARD-EXPIRY-DATEX(4)47‑50COPAUS2C
    MESSAGE-TYPEX(6)51‑56COPAUS2C
    MESSAGE-SOURCEX(6)57‑62COPAUS2C
    AUTH-ID-CODEX(6)63‑68COPAUS2C
    AUTH-RESP-CODEX(2)69‑70COPAUS2C
    AUTH-RESP-REASONX(4)71‑74COPAUS2C
    PROCESSING-CODEX(6)75‑80COPAUS2C
    TRANSACTION-AMTS9(10)V9(2)81‑87COPAUS2C
    APPROVED-AMTS9(10)V9(2)88‑94COPAUS2C
    MERCHANT-CATAGORY-CODEX(4)95‑98COPAUS2C
    ACQR-COUNTRY-CODEX(3)99‑101COPAUS2C
    POS-ENTRY-MODES9(4)102‑103COPAUS2C
    MERCHANT-IDX(15)104‑118COPAUS2C
    MERCHANT-NAME119‑142COPAUS2C
                  MERCHANT-NAME-LENS9(4)119‑120
                  MERCHANT-NAME-TEXTX(22)121‑142COPAUS2C
    MERCHANT-CITYX(13)143‑155COPAUS2C
    MERCHANT-STATEX(2)156‑157COPAUS2C
    MERCHANT-ZIPX(9)158‑166COPAUS2C
    TRANSACTION-IDX(15)167‑181COPAUS2C
    MATCH-STATUSX(1)182‑182COPAUS2C
    AUTH-FRAUDX(1)183‑183COPAUS2C
    FRAUD-RPT-DATEX(10)184‑193
    ACCT-IDS9(11)V194‑199COPAUS2C
    CUST-IDS9(9)V200‑204COPAUS2C

CIPAUSMY: PENDING-AUTH-SUMMARY

FieldPICBytesValuesSet by
PENDING-AUTH-SUMMARY1‑100
  PA-ACCT-IDS9(11)1‑6COPAUA0C (transaction CP00), COPAUS0C (transaction CPVS), COPAUS1C (transaction CPVD)
  PA-CUST-ID9(09)7‑15COPAUA0C (transaction CP00)
  PA-AUTH-STATUSX(01)16‑16
  PA-ACCOUNT-STATUSX(02)17‑26
  PA-CREDIT-LIMITS9(09)V9927‑32COPAUA0C (transaction CP00)
  PA-CASH-LIMITS9(09)V9933‑38COPAUA0C (transaction CP00)
  PA-CREDIT-BALANCES9(09)V9939‑44COPAUA0C (transaction CP00)
  PA-CASH-BALANCES9(09)V9945‑50COPAUA0C (transaction CP00)
  PA-APPROVED-AUTH-CNTS9(04)51‑52CBPAUP0C (CBPAUP0J), COPAUA0C (transaction CP00)
  PA-DECLINED-AUTH-CNTS9(04)53‑54CBPAUP0C (CBPAUP0J), COPAUA0C (transaction CP00)
  PA-APPROVED-AUTH-AMTS9(09)V9955‑60CBPAUP0C (CBPAUP0J), COPAUA0C (transaction CP00)
  PA-DECLINED-AUTH-AMTS9(09)V9961‑66CBPAUP0C (CBPAUP0J), COPAUA0C (transaction CP00)

CSUSR01Y: SEC-USER-DATA

FieldPICBytesValuesSet by
SEC-USER-DATA1‑80
  SEC-USR-IDX(08)1‑8COUSR00C (transaction CU00)
  SEC-USR-FNAMEX(20)9‑28
  SEC-USR-LNAMEX(20)29‑48
  SEC-USR-PWDX(08)49‑56
  SEC-USR-TYPEX(01)57‑57
  SEC-USR-FILLERX(23)58‑80

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)

CVACT02Y: CARD-RECORD

One record per credit card: its number, the account it belongs to, the name embossed on it, its expiry date, and whether it's active. Kept in the card master file (AWS.M2.CARDDEMO.CARDDATA.VSAM.KSDS, keyed by card number), 150 bytes long, with an alternate index path (CARDDATA.VSAM.AIX.PATH) that the card screens use to find cards by account.

Fields
FieldMeaningNotes
CARD-RECORDThe whole card recordRead by the card list and card view screens (CCLI, CCDL) and the batch card report and export; rewritten by the card update screen (CCUP)
CARD-NUMCard number, 16 charactersThe file's key. Kept as text, not a number
CARD-ACCT-IDThe account the card belongs to, 11 digitsPoints to the account record (ACCT-ID). Probably the key of the alternate index the card screens use to list an account's cards
CARD-CVV-CDCard verification value (CVV), 3 digitsStored in clear - see the notes. Read by the card update screen
CARD-EMBOSSED-NAMECardholder name printed on the card, 50 charactersChanged on the card update screen (CCUP)
CARD-EXPIRAION-DATECard expiry date, 10 charactersProbably YYYY-MM-DD, kept as text. The name is misspelled ("EXPIRAION") in the source
CARD-ACTIVE-STATUSWhether the card is active, one characterProbably Y or N; the copybook defines no values. Changed on the card update screen (CCUP)
Notes for modernization
FieldPICBytesValuesSet by
CARD-RECORD1‑150
  CARD-NUMX(16)1‑16CBIMPORT (CBIMPORT)
  CARD-ACCT-ID9(11)17‑27CBIMPORT (CBIMPORT)
  CARD-CVV-CD9(03)28‑30CBIMPORT (CBIMPORT)
  CARD-EMBOSSED-NAMEX(50)31‑80CBIMPORT (CBIMPORT), COCRDUPC (transaction CCUP)
  CARD-EXPIRAION-DATEX(10)81‑90CBIMPORT (CBIMPORT)
  CARD-ACTIVE-STATUSX(01)91‑91CBIMPORT (CBIMPORT), COCRDUPC (transaction CCUP)

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)

CVCUS01Y: CUSTOMER-RECORD

One record per customer: name, address, phone numbers, identity details, and credit score. Kept in the customer master file (AWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDS, keyed by customer number), 500 bytes long.

Fields
FieldMeaningNotes
CUSTOMER-RECORDThe whole customer recordRead by the account view screen, authorization, the customer report, and the export; rewritten by the account update screen (CAUP)
CUST-IDCustomer number, 9 digitsThe file's key. The card cross-reference (XREF-CUST-ID) points to it
CUST-FIRST-NAMEFirst name, 25 characters
CUST-MIDDLE-NAMEMiddle name, 25 characters
CUST-LAST-NAMELast name, 25 characters
CUST-ADDR-LINE-1Address line 1, 50 characters
CUST-ADDR-LINE-2Address line 2, 50 characters
CUST-ADDR-LINE-3Address line 3, 50 charactersProbably the city, since there's no separate city field
CUST-ADDR-STATE-CDState code, 2 charactersProbably the US postal abbreviation
CUST-ADDR-COUNTRY-CDCountry code, 3 charactersProbably an ISO 3166 alpha-3 code such as USA
CUST-ADDR-ZIPZIP or postal code, 10 characters
CUST-PHONE-NUM-1Primary phone number, 15 charactersKept as formatted text
CUST-PHONE-NUM-2Second phone number, 15 charactersKept as formatted text
CUST-SSNSocial Security number, 9 digitsStored in clear - see the notes
CUST-GOVT-ISSUED-IDGovernment-issued ID number (driver's license, passport, ...), 20 charactersStored in clear
CUST-DOB-YYYY-MM-DDDate of birth, YYYY-MM-DD as textThe format is in the field's name
CUST-EFT-ACCOUNT-IDBank account for electronic funds transfer, 10 charactersProbably the account payments are drawn from; nothing in the source uses it for a payment
CUST-PRI-CARD-HOLDER-INDWhether the customer is the primary cardholder, one characterProbably Y or N; the copybook defines no values
CUST-FICO-CREDIT-SCOREFICO credit score, 3 digitsProbably 300-850. Displayed and editable on the account update screen; nothing in the source uses it to decide anything
Notes for modernization
FieldPICBytesValuesSet by
CUSTOMER-RECORD1‑500
  CUST-ID9(09)1‑9CBIMPORT (CBIMPORT)
  CUST-FIRST-NAMEX(25)10‑34CBIMPORT (CBIMPORT)
  CUST-MIDDLE-NAMEX(25)35‑59CBIMPORT (CBIMPORT)
  CUST-LAST-NAMEX(25)60‑84CBIMPORT (CBIMPORT)
  CUST-ADDR-LINE-1X(50)85‑134CBIMPORT (CBIMPORT)
  CUST-ADDR-LINE-2X(50)135‑184CBIMPORT (CBIMPORT)
  CUST-ADDR-LINE-3X(50)185‑234CBIMPORT (CBIMPORT)
  CUST-ADDR-STATE-CDX(02)235‑236CBIMPORT (CBIMPORT)
  CUST-ADDR-COUNTRY-CDX(03)237‑239CBIMPORT (CBIMPORT)
  CUST-ADDR-ZIPX(10)240‑249CBIMPORT (CBIMPORT)
  CUST-PHONE-NUM-1X(15)250‑264CBIMPORT (CBIMPORT)
  CUST-PHONE-NUM-2X(15)265‑279CBIMPORT (CBIMPORT)
  CUST-SSN9(09)280‑288CBIMPORT (CBIMPORT)
  CUST-GOVT-ISSUED-IDX(20)289‑308CBIMPORT (CBIMPORT)
  CUST-DOB-YYYY-MM-DDX(10)309‑318CBIMPORT (CBIMPORT)
  CUST-EFT-ACCOUNT-IDX(10)319‑328CBIMPORT (CBIMPORT)
  CUST-PRI-CARD-HOLDER-INDX(01)329‑329CBIMPORT (CBIMPORT)
  CUST-FICO-CREDIT-SCORE9(03)330‑332CBIMPORT (CBIMPORT)

CVEXPORT: EXPORT-RECORD

FieldPICBytesValuesSet by
EXPORT-RECORD1‑500
  EXPORT-REC-TYPEX(1)1‑1CBEXPORT (CBEXPORT)
  EXPORT-TIMESTAMPX(26)2‑27CBEXPORT (CBEXPORT)
  EXPORT-TIMESTAMP-R2‑27
    EXPORT-DATEX(10)2‑11
    EXPORT-DATE-TIME-SEPX(1)12‑12
    EXPORT-TIMEX(15)13‑27
  EXPORT-SEQUENCE-NUM9(9)28‑31CBEXPORT (CBEXPORT)
  EXPORT-BRANCH-IDX(4)32‑35CBEXPORT (CBEXPORT)
  EXPORT-REGION-CODEX(5)36‑40CBEXPORT (CBEXPORT)
  EXPORT-RECORD-DATAX(460)41‑500
  EXPORT-CUSTOMER-DATA41‑500
    EXP-CUST-ID9(09)41‑44CBEXPORT (CBEXPORT)
    EXP-CUST-FIRST-NAMEX(25)45‑69CBEXPORT (CBEXPORT)
    EXP-CUST-MIDDLE-NAMEX(25)70‑94CBEXPORT (CBEXPORT)
    EXP-CUST-LAST-NAMEX(25)95‑119CBEXPORT (CBEXPORT)
    EXP-CUST-ADDR-LINES120‑269
      EXP-CUST-ADDR-LINEX(50)120‑169CBEXPORT (CBEXPORT)
    EXP-CUST-ADDR-STATE-CDX(02)270‑271CBEXPORT (CBEXPORT)
    EXP-CUST-ADDR-COUNTRY-CDX(03)272‑274CBEXPORT (CBEXPORT)
    EXP-CUST-ADDR-ZIPX(10)275‑284CBEXPORT (CBEXPORT)
    EXP-CUST-PHONE-NUMS285‑314
      EXP-CUST-PHONE-NUMX(15)285‑299CBEXPORT (CBEXPORT)
    EXP-CUST-SSN9(09)315‑323CBEXPORT (CBEXPORT)
    EXP-CUST-GOVT-ISSUED-IDX(20)324‑343CBEXPORT (CBEXPORT)
    EXP-CUST-DOB-YYYY-MM-DDX(10)344‑353CBEXPORT (CBEXPORT)
    EXP-CUST-EFT-ACCOUNT-IDX(10)354‑363CBEXPORT (CBEXPORT)
    EXP-CUST-PRI-CARD-HOLDER-INDX(01)364‑364CBEXPORT (CBEXPORT)
    EXP-CUST-FICO-CREDIT-SCORE9(03)365‑366CBEXPORT (CBEXPORT)
  EXPORT-ACCOUNT-DATA41‑500
    EXP-ACCT-ID9(11)41‑51CBEXPORT (CBEXPORT)
    EXP-ACCT-ACTIVE-STATUSX(01)52‑52CBEXPORT (CBEXPORT)
    EXP-ACCT-CURR-BALS9(10)V9953‑59CBEXPORT (CBEXPORT)
    EXP-ACCT-CREDIT-LIMITS9(10)V9960‑71CBEXPORT (CBEXPORT)
    EXP-ACCT-CASH-CREDIT-LIMITS9(10)V9972‑78CBEXPORT (CBEXPORT)
    EXP-ACCT-OPEN-DATEX(10)79‑88CBEXPORT (CBEXPORT)
    EXP-ACCT-EXPIRAION-DATEX(10)89‑98CBEXPORT (CBEXPORT)
    EXP-ACCT-REISSUE-DATEX(10)99‑108CBEXPORT (CBEXPORT)
    EXP-ACCT-CURR-CYC-CREDITS9(10)V99109‑120CBEXPORT (CBEXPORT)
    EXP-ACCT-CURR-CYC-DEBITS9(10)V99121‑128CBEXPORT (CBEXPORT)
    EXP-ACCT-ADDR-ZIPX(10)129‑138CBEXPORT (CBEXPORT)
    EXP-ACCT-GROUP-IDX(10)139‑148CBEXPORT (CBEXPORT)
  EXPORT-TRANSACTION-DATA41‑500
    EXP-TRAN-IDX(16)41‑56CBEXPORT (CBEXPORT)
    EXP-TRAN-TYPE-CDX(02)57‑58CBEXPORT (CBEXPORT)
    EXP-TRAN-CAT-CD9(04)59‑62CBEXPORT (CBEXPORT)
    EXP-TRAN-SOURCEX(10)63‑72CBEXPORT (CBEXPORT)
    EXP-TRAN-DESCX(100)73‑172CBEXPORT (CBEXPORT)
    EXP-TRAN-AMTS9(09)V99173‑178CBEXPORT (CBEXPORT)
    EXP-TRAN-MERCHANT-ID9(09)179‑182CBEXPORT (CBEXPORT)
    EXP-TRAN-MERCHANT-NAMEX(50)183‑232CBEXPORT (CBEXPORT)
    EXP-TRAN-MERCHANT-CITYX(50)233‑282CBEXPORT (CBEXPORT)
    EXP-TRAN-MERCHANT-ZIPX(10)283‑292CBEXPORT (CBEXPORT)
    EXP-TRAN-CARD-NUMX(16)293‑308CBEXPORT (CBEXPORT)
    EXP-TRAN-ORIG-TSX(26)309‑334CBEXPORT (CBEXPORT)
    EXP-TRAN-PROC-TSX(26)335‑360CBEXPORT (CBEXPORT)
  EXPORT-CARD-XREF-DATA41‑500
    EXP-XREF-CARD-NUMX(16)41‑56CBEXPORT (CBEXPORT)
    EXP-XREF-CUST-ID9(09)57‑65CBEXPORT (CBEXPORT)
    EXP-XREF-ACCT-ID9(11)66‑73CBEXPORT (CBEXPORT)
  EXPORT-CARD-DATA41‑500
    EXP-CARD-NUMX(16)41‑56CBEXPORT (CBEXPORT)
    EXP-CARD-ACCT-ID9(11)57‑64CBEXPORT (CBEXPORT)
    EXP-CARD-CVV-CD9(03)65‑66CBEXPORT (CBEXPORT)
    EXP-CARD-EMBOSSED-NAMEX(50)67‑116CBEXPORT (CBEXPORT)
    EXP-CARD-EXPIRAION-DATEX(10)117‑126CBEXPORT (CBEXPORT)
    EXP-CARD-ACTIVE-STATUSX(01)127‑127CBEXPORT (CBEXPORT)

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)

CVTRA02Y: DIS-GROUP-RECORD

FieldPICBytesValuesSet by
DIS-GROUP-RECORD1‑50
  DIS-GROUP-KEY1‑16
    DIS-ACCT-GROUP-IDX(10)1‑10
    DIS-TRAN-TYPE-CDX(02)11‑12
    DIS-TRAN-CAT-CD9(04)13‑16
  DIS-INT-RATES9(04)V9917‑22

CVTRA03Y: TRAN-TYPE-RECORD

FieldPICBytesValuesSet by
TRAN-TYPE-RECORD1‑60
  TRAN-TYPEX(02)1‑2
  TRAN-TYPE-DESCX(50)3‑52

CVTRA04Y: TRAN-CAT-RECORD

FieldPICBytesValuesSet by
TRAN-CAT-RECORD1‑60
  TRAN-CAT-KEY1‑6
    TRAN-TYPE-CDX(02)1‑2
    TRAN-CAT-CD9(04)3‑6
  TRAN-CAT-TYPE-DESCX(50)7‑56

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

CVTRA07Y: REPORT-ACCOUNT-TOTALS, REPORT-GRAND-TOTALS, REPORT-NAME-HEADER, REPORT-PAGE-TOTALS, TRANSACTION-DETAIL-REPORT, TRANSACTION-HEADER-1

FieldPICBytesValuesSet by
REPORT-ACCOUNT-TOTALS1‑112
  REPT-ACCOUNT-TOTAL+ZZZ,ZZZ,ZZZ.ZZ98‑112CBTRN03C (TRANREPT)
REPORT-GRAND-TOTALS1‑112
  REPT-GRAND-TOTAL+ZZZ,ZZZ,ZZZ.ZZ98‑112CBTRN03C (TRANREPT)
REPORT-NAME-HEADER1‑115
  REPT-SHORT-NAMEX(38)1‑38
  REPT-LONG-NAMEX(41)39‑79
  REPT-DATE-HEADERX(12)80‑91
  REPT-START-DATEX(10)92‑101CBTRN03C (TRANREPT)
  REPT-END-DATEX(10)106‑115CBTRN03C (TRANREPT)
REPORT-PAGE-TOTALS1‑112
  REPT-PAGE-TOTAL+ZZZ,ZZZ,ZZZ.ZZ98‑112CBTRN03C (TRANREPT)
TRANSACTION-DETAIL-REPORT1‑114
  TRAN-REPORT-TRANS-IDX(16)1‑16CBTRN03C (TRANREPT)
  TRAN-REPORT-ACCOUNT-IDX(11)18‑28CBTRN03C (TRANREPT)
  TRAN-REPORT-TYPE-CDX(02)30‑31
  TRAN-REPORT-TYPE-DESCX(15)33‑47CBTRN03C (TRANREPT)
  TRAN-REPORT-CAT-CD9(04)49‑52
  TRAN-REPORT-CAT-DESCX(29)54‑82CBTRN03C (TRANREPT)
  TRAN-REPORT-SOURCEX(10)84‑93CBTRN03C (TRANREPT)
  TRAN-REPORT-AMT-ZZZ,ZZZ,ZZZ.ZZ98‑112CBTRN03C (TRANREPT)
TRANSACTION-HEADER-11‑114

DCLTRTYP: DCLTRANSACTION-TYPE

FieldPICBytesValuesSet by
DCLTRANSACTION-TYPE1‑54
    DCL-TR-TYPEX(2)1‑2COTRTLIC (transaction CTLI), COTRTUPC (transaction CTTU)
    DCL-TR-DESCRIPTION3‑54COTRTLIC (transaction CTLI), COTRTUPC (transaction CTTU)
                  DCL-TR-DESCRIPTION-LENS9(4)3‑4COTRTLIC (transaction CTLI), COTRTUPC (transaction CTTU)
                  DCL-TR-DESCRIPTION-TEXTX(50)5‑54

Findings

Serious 1 member(s) referenced but not in the source
These are called, run, or copied but weren't in any library provided. Ask the client for them before estimating the work that depends on them.
Serious 1 program(s) use ALTER
ALTER changes where a GO TO goes while the program runs, so the code doesn't show the real flow. Untangle it before converting.
Serious 1 file(s) a program uses that its job doesn't define
The program opens a DD name that no step running it defines; the job would fail or the file comes from somewhere not in the source.
Check COACTUPC writes AWS.M2.CARDDEMO.ACCTDATA.VSAM.KSDS back from a different structure
COACTUPC reads the record into one structure and writes it back from another; they don't line up field for field, so the record is written back with these bytes holding something else, or blank:
Check 1 program(s) with NEXT SENTENCE inside an END-IF
NEXT SENTENCE jumps past the END-IF to the next period, skipping statements after the IF that the indentation suggests will run. Check each one against the intended logic.
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.
Note Record CARD-RECORD coded inline in COCRDUPC
1 inline layout(s) have the same fields as CARD-RECORD in copybook CVACT02Y: COPY CVACT02Y instead, so a change to the record is made once.
Note Record CUSTOMER-RECORD coded inline in COACTUPC
1 inline layout(s) have the same fields as CUSTOMER-RECORD in copybook CVCUS01Y (also in CUSTREC): COPY CVCUS01Y instead, so a change to the record is made once.
Note Record INFIL2-REC coded inline in PAUDBLOD, PAUDBUNL
The same 206-byte record is coded inline in 2 programs: extract it into one copybook, so a change to the record is made once.
Note COACTUPC writes AWS.M2.CARDDEMO.CUSTDATA.VSAM.KSDS back from a different structure
COACTUPC reads the record into one structure and writes it back from another; the fields line up, so it's only a naming difference to tidy up.
Note COCRDUPC writes AWS.M2.CARDDEMO.CARDDATA.VSAM.KSDS back from a different structure
COCRDUPC reads the record into one structure and writes it back from another; the fields line up, so it's only a naming difference to tidy up.
Note 10 program(s) use GO TO
Jumps make the flow harder to follow and to convert to structured code.
Note 5 program(s) with paragraphs nothing reaches
No PERFORM, GO TO, or fall-through reaches these paragraphs: candidates to remove rather than convert (check for a reference the source doesn't show first).
Note 1 program(s) nothing in the source runs or calls
No JCL step, CSD transaction, or CALL / XCTL / LINK reaches these. They may be retired, or run from somewhere not provided (another application, a scheduler, an IMS or CICS definition); 11 dynamic call(s) couldn't be resolved and might reach one.
Note 4 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 3 scheduled order(s) with no shared data behind them
Compared the client's scheduler definitions with which jobs write and read each dataset and Db2 table.
Note 1 copybook(s) nothing uses
Candidates to retire rather than convert.
Note From the review of job CREASTMT
Note From the review of job INTCALC
Note From the review of job POSTTRAN
Note From the review of job TRANREPT
Note From the review of program CBACT04C
Note From the review of program CBSTM03A
Note From the review of program CBSTM03B
Note From the review of program CBTRN02C
Note From the review of program CBTRN03C
Note From the review of program COACTUPC
Note From the review of program COMEN01C
Note From the review of program COSGN00C
Note From the review of program COTRN02C
Note From the review of program CSUTLDTC
Note From the review of transaction CAUP
Note From the review of transaction CC00
Note From the review of transaction CM00
Note From the review of transaction CT02

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