Instructions for Reading Flow Chart in the WBT...........................................................................................

2
Learning Objectives.........................................................................................................................................3
Introduction......................................................................................................................................................3
Non Monetary Batch Flow...............................................................................................................................3
ARU040 (Non Monetary User Input Pre-edit):......................................................................................4
ARD040 (File Maintenance Journal):.....................................................................................................5
ARU780 (Name Key Update):.................................................................................................................6
Monetary batch flow.........................................................................................................................................6
ARU020 ( Master file backup/reload):...................................................................................................8
ARD020 ( Online Transaction Extract ):................................................................................................8
ARD060/ARD065 (Date Roll/Date Roll Account):................................................................................8
ARD011 (Sort monetary file from TRAMS):..........................................................................................9
ARU080 (Monetary User Input Pre-edit):..............................................................................................9
ARD080 (Transaction Edit/Merge)........................................................................................................10
ARD100 (Sort transactions to posting).................................................................................................10
ARD140 (Posting)....................................................................................................................................11
ARD170 (Shopper Program Control Records Update).....................................................................12
ARD175 (Sort ATGT and create ABGT Backup)................................................................................12
ARD180 (Monetary History Update).....................................................................................................12
ARU060 (Initialize Transaction Files)...................................................................................................13
ARD185 (Multiple Reject Processing)..................................................................................................13
ARD190 (Build Multiple Reject AMM1 File)........................................................................................14
ARD200 (Build Reject Reentry)............................................................................................................14
CMS Daily Batch...........................................................................................................................................15
After Hours/ End of Day................................................................................................................................16
ARDAILY1 (Account Receivable Daily CMS1)...........................................................................................17
ARU000 (Control Card Load)................................................................................................................17
ARD000 (File Integrity)...........................................................................................................................18
ARU020 (Master File Before Backup/Reload)....................................................................................18
ARD020 (Online Transaction Extract)..................................................................................................19
ARD060 (Date Roll).................................................................................................................................19
Monetary User Input (ARD011, ARU080, ARD080)...........................................................................19
ARD065 (Date Roll – Account)..............................................................................................................20
User Non-monetary (ARU040, ARD040, ARU780)............................................................................21
ARD100 (Sort Transactions to posting)................................................................................................22
ARD140 (Posting)....................................................................................................................................23
ARDAILY2 (Account Receivable Daily CMS2)...........................................................................................24
ARD117 (Account/Card Quarterly report Sort)...................................................................................24
ARD118 (Update Cardholder Quarterly Report File).........................................................................24
ARD119 (Cardholder Quarterly Report File Update).........................................................................24
ARD144 (Split Relationship/Embosser Update File).........................................................................24
ARD150 (Update AMCR and produce daily balancing report).........................................................25
ARD159 (Open Item Transaction Tag Sort).........................................................................................25
ARD160 (Open Item Transaction File Update)...................................................................................25
ARD170 (Shopper Program Control Records Update).....................................................................26
ARD175 (Sort ATGT and Create ABGT Backup)...............................................................................26
ARD180 (Monetary History Update).....................................................................................................26
ARU060 (Initialize Transaction Files)...................................................................................................28
ARD185 (Multiple Reject Processing)..................................................................................................28
ARD190 (Build AMM1 File)....................................................................................................................28
ARD200 (Build Reject Reentry)............................................................................................................29
ARD210 (Fraud Reports Print)..............................................................................................................29
ARD250 (Active/Inactive Account Processing)..................................................................................29
ARD420 (Activity Recap Update).........................................................................................................29
ARD440 (Activity Recap Restore)........................................................................................................30
ARD600 (Promotion Statistical Update)..............................................................................................30
ARD220 (Set Condition Code for Online Statements)......................................................................30
 ARD240 (Small Statement/Online Statement 1 Processing)...........................................................31
ARD230 (Reset Condition Code to Zero)............................................................................................31
ARU020 (Master File After Backup/Reload).......................................................................................31
ARU190 (Sort/Merge Embossing ATEI and ATEO Files)..................................................................32
ARU200 (Card Issue)..............................................................................................................................32
ARDAILY3 (Account Receivable Daily CMS3)...........................................................................................33
ARD220 (Set Condition Code For Online Statements).....................................................................34
ARD245 (Generate AMLD File).............................................................................................................35
ARU000 (Control Card Load)................................................................................................................35
ARD020 (Online Transaction Extract for After Hours).......................................................................35
ARDAILY4 (Account Receivable Daily CMS4)...........................................................................................37
ARU900 (Initialize After hours Master Files).......................................................................................37
ARU060 (Initialize Shadow Transaction Files)....................................................................................37
ARU100 (Initialize Shadow Alpha Name key)....................................................................................38
ARU340 (Large Statement/Online Statement 2 Processing)...........................................................39
IMPORTANT NOTE......................................................................................................................................40

Instructions for Reading Flow Chart in the WBT

1. The flow chart for non-monetary and monetary batch flow is repeated twice in the WBT
as non-monetary and monetary flow is explained separately as also as part of the entire
batch flow.

2. Connector A is used across all the flow charts and its sole purpose is to maintain the
continuity of the batch flow. The connector in green indicates input and the connector in
violet indicates output.

Learning Objectives
Upon completion of this section, you will be able to:

 Understand CMS Batch Processing.

 Understand the Monetery and Non-Monetary transactions.
 Understand the Monetary batch processing.
 Understand the Non Monetary batch processing.
 Understand different phases of CMS Batch Cycle

Introduction

In CMS, a Batch process is required to post Monetary transactions (like sale/payment,

debit/credit adjustments or refunds etc) as well as Non Monetary transactions (like change of
address or telephone number) to the customer’s account, calculate date-driven delinquency,
calculate finance charges and late fees, generate statements, and other functions. The batch
process is streamlined and capable of processing large account bases within compressed nightly
batch windows. During the batch process, all master files are closed to online maintenance so
that the batch update can occur. To accommodate certain data processing requirements, Vision
PLUS enables the credit staff to access and/or manipulate cardholder account data after the
master files are closed and batch processing begins (in the after hours mode).

The batch processing of accounts can be classified into 2 broad categories as:

1) Non monetary batch flow

2) Monetary batch flow

Non Monetary Batch Flow

At any point of time, if the card holder would like to change his/her details in the master files of
the Issuer bank, he/she can call up the Customer Service Centre (also called ASM or Account
Service Management) of the Issuer Bank and request for the required change.

E.g.: Address, Telephone number etc.

These changes are directly updated to the original master files through the online by the
customer service representative and a log file (AML1 file that is extracted as ATL1 using the
ARD020 program in batch) will be maintained with the before and after value of each of the
changed fields. This activity would be performed online for the specific accounts requested for.

On the other hand, if the issuer bank would like to do bulk changes of field values for bunch of
accounts, instead of updating through online transactions, they are created through a User input
file (ATUD) and then fed into the batch for updating the master files.

E.g.: Postal code of a city changes, Name of a city changes etc.

Here it is important to make sure that the User provided ATUD files are pre-edited before they
are fed in the nightly batch to update the master files.
 Batch Processing of accounts

Non-Monetary User Input

ARU040
AMNA
AMBS
AMED
AMPM
ARD040

UPDATEU
JOURNAL
UPDATE

ATUT ATUD ATUI ATCC-2 ATNU

(ATL1) ATCC-2

ARU040 ARD040 ARU780

Nonmonetary Mater Files Alpha Search
Edit Update Update

AM* AT*
NA BS FR O1 TS AMNK
ATUI ED PM AMBX
NM NU

ARU040 (Non Monetary User Input Pre-edit):

ARU040 program will do the pre-edits of all the non-monetary User inputs.
All the non monetary user inputs are fed into the system through ATUD (Disk)/ ATUT (Tape) files
and they are pre-edited by the program ARU040.

Some examples of pre-edits are:

1. If the input record is an “Add New Account” and the account exists on either the AMBS or the
AMBI (Inactive Account Base Segment) files, the program reject the input record.

2. If the input record is a maintenance function to an existing account and if the account is not on
the Account Base Segment file or on the inactive file (if the maintenance is base segment
maintenance), the program rejects the input record.

3. The input record can also be rejected based on the Field Security Level record for this
organization and security user code, or if the data input is not valid for this field.

4. Also, if the value of the field being changed is identical to the value input, the program does
not generate a maintenance record.

All valid records that have passed the pre-edit are written into the ATUI file and for all the error
records a detailed invalid report is generated. The pre-edits are done only for records that belong
to AMNA, AMBS, AMED, AMPS, AMPM, AMLS files, and all other file records are bypassed from
the pre-edit.

ARU040 is composed of various dynamically called programs. Each of these called programs
pre-edit respective files and pass on information to ARU040. These programs are specifically
named as ARU040XX, where XX stands for the file name acronym.

E.g.: ARU040BS: (Account Base Segment User Non-Monetary Pre-edit) will be called from
ARU040 for AMBS file pre-edit.
ARU040NA: (Name and Address User Non-Monetary Pre-edit) will be called from ARU040
for AMNA file pre-edit.

ARD040 (File Maintenance Journal):

The actual non-monetary maintenance happens in the ARD040 program.

The valid ATUI file from ARU040 is fed as input to ARD040 program, and this program updates
the actual master files when it is run in the user-input mode. It also generates the detailed report
with before and after values of fields that are updated online, provided it is run in the journal
mode (the input file in this mode will be ATL1 which is extracted from AML1 using program
ARD020).

ARD040 can be run in three modes – JOURNAL, UPDATE U & UPDATE.

JOURNAL mode – generates report of all non monetary updates that have happened through
online. That means all online accepted non monetary transactions in the input ATL1 file, that
affects any of the master files will be reported.

UPDATE U mode – Updates the master files using ATUD (Disk File)/ ATUT (Tape File).
In the Update U (also called as user-input mode), the program can do selective updates on CMS
master files. In this mode, the program opens only the AMBS, AMEC, AMED, AMNA, AMPM,
and AMSC files for direct updates. Corresponding updates are made to AMNK (Name Key File)
and AMBX (Customer to Base Segment Cross reference file), if applicable. Also it creates
different output files like ATNU (Name Key Update File), ATTS (Promotion Statistics Tag File),
ATO1 (CTA Tag Maintenance File), ATNM (Daily Name/Address Maintenance File), ATFR (Fraud
Report File) which can be used by other subsystems for different purposes.
UPDATE mode - Is used for disaster recovery (Reload files from backup - ABTF). The update
mode can be used for data recovery operations. In this mode, the valid transactions that are
resident on the AML1 file will be applied to the concerned CMS master files during the execution
of ARD040.

ARD040 is composed of various dynamically called programs. Each of these called programs
processes and passes print file information to ARD040 in both the update and journal modes.
These programs are specifically named as ARD040XX, where XX stands for the file name
acronym.

E.g.: ARD040BS: (Account Base Segment Record Maintenance Journal) will be called from
ARD040 for AMBS file maintenance
ARD040NA: (Name and Address File Maintenance Journal) will be called from ARD040 for
AMNA file maintenance

ARU780 (Name Key Update):

The ATNU (Name Key Update File) file created by ARD040 will be fed as input to ARU780
program which handles Alpha search Update. It rebuilds AMNK (Name key file) and AMBX (base
customer XREF file) files. AMNK file is used to locate a customer by giving first few alphabets of
the name using the online ARNL transaction. Rebuilding of this file is required when there are
changes in Name and Address file AMNA.

Monetary batch flow

Monetary transactions are those which affect balances of CMS accounts. Monetary transactions
are typically authorized and input by tape or electronic transmission. Other monetary
transactions are input using CMS batch transactions (E.g.: Batch of transaction details that the
Merchant submits to the bank). These transactions do not affect the balances until a batch
processing run is completed. Monetary transactions can be fed to the system mainly through
online or through batch.

ARAT/ARAP transaction can be done online which will add a record to the AMT1 file that will be
fed to the nightly batch cycle for processing. A few monetary transactions that could be applied
through online could be interest adjustment, fee adjustment, re-entering rejected batches, adding
payments etc.

On the other hand, the ATTD (Disk)/ATTT (Tape) batch feed will come through TRAMS
(Transaction Management System). TRAMS will receive the settlement file from the network that
would contain all the monetary transactions that were processed during the day in the network
(Master or Visa).

All the monetary transactions are processed in batches and there can be only one batch
processed per organization in the batch, hence maximum number of batches would be 99998 in
any batch cycle. A batch of transaction consists of a header that contains the batch number, sum
totals of all transaction items and debit and credit amounts that are included in the batch, and
records of the individual transactions and details. During the daily run, CMS matches the
contents of the batch with the batch header. If the batch header does not match with the content,
CMS rejects that batch. Either the batch header or the batch will need to be corrected to balance
the batch, before CMS will process it.

Monetary extract Flow

ARD020
 ARD080
ARD100
ARD140 – Posting flag
ARD180
ARD185
ARD200 – reject re-entry
Trams input
ARD010
ARD011
ARU080

Monetary transaction flow in CMS is handled by the following programs. The AMT1 file is
processed through the following set of programs.

1) ARD020: Online Transaction Extract

2) ARD080: Transaction Edit Merge
3) ARD100: Sort Transactions to Posting
4) ARD140: Posting
5) ARD180: Monetary History Update
6) ARD185: Multiple Reject Processing
7) ARD200: Build Reject Reentry

The ATTD/ATTT file from TRAMS is initially processed through the following set of programs

• ARD010: TRAMS monetary balancing report

• ARD011: Sort ATTD file for CMS
• ARU080: Monetary user input pre-edit

The output of ARU080, ATTI file is fed to ARD080 along with ATT1 created by ARD020 and the
processing continues from ARD080 through ARD200.
 AM*
AM* L1 L3 J1
ATCC-1 T1 XT ATCC-1
ATCC-1

ARD020 ARD060/65
On-line Trans Date Roll
ARU020 Extract
Master File
Backup
AT*
L1 L3 J1
ABTF
T1 XT
AM*
ABMF

ARU020 ( Master file backup/reload):

Program ARU020 is used to take backup or reload all master files. The backup will be taken into
tape file ABMF. This is a control card driven program in which we can specify options for
backup/reload as well as the file for which we need to perform the operation. If something goes
wrong during the batch or for any other reason, if it is required to restore all the master files as is
before the batch, ARU020 would be run in the reload mode and using the ABMF as the input file,
all the master files would be restored.

ARD020 ( Online Transaction Extract ):

Program ARD020 extracts all online monetary transactions that were fed through ARAT/ARAP
screens throughout the day. All these transactions will be added to the AMT1 file. Also we have
the rejected monetary transactions form the previous day's batch in the AMJ1file, the transferred
transactions in AMXT file. This program extracts all these files and will create output transactions
files ATT1, ATJ1 and ATXT.

Also this program takes the backup of all the transaction files into tape file ABTF. This tape
backup ABTF can be used to reload the transaction files in later stage if required .This Backup
and reload process is driven by setting the control card parameters.

ARD060/ARD065 (Date Roll/Date Roll Account):

All the master files in the system have a date and/or timestamp in the header record. In the
batch run, all the master files are updated with current system date and time on which the batch
is running.

User can make the system bump to any future date by giving a future date in the control card.
This would not happen in a normal production environment but would be required in the Test
Environment for testing specific functionality (like testing delinquency, calculating future interest
etc).

Otherwise the system will increment the date by one from the current date in the AMCR file.

ARD060/ARD065 programs will handle the date roll in CMS. This will update all the files with
correct processing date for the system and the organizations. ARD060 does the date and time
stamp updates for non segmented master files i.e. the control files. (E.g. AMCR) ARD065 does
the date and time stamp updates for all the account based master files. (E.g. AMBS, AMNA etc.,)
AM* AT* J1
CP CR T1 XT
TRAMS ATTI MC SD AM* CR
ATCC-1 MC WT

ARD011 ARU080 ARD080

Sort TRAMS User Monetary Monetary A
Edit Trans Merge

ATE1
ATNS ATBB
ATBB
ASM ATTD ATVT ATIB
ATTI ATIB
ATTT

ARD011 (Sort monetary file from TRAMS):

Program ARD011 sorts the monetary transaction coming from TRAMS and writes into ATTD file
and pass the file to program ARU080. ARD011 sorts the records in the correct sequence i.e.
batch headers at the top followed by the transaction records. The monetary data from the ASM
system is formatted in ATTD layout and passed into ARU080 program for further processing.

ARU080 (Monetary User Input Pre-edit):

Program ARU080 handles the pre-edit of monetary transactions from the user input files (ATTD,
ATTT or both) which are coming from different sources like TRAMS/ ASM, merges the files and
writes all valid transactions into ATTI file. It produces a report, listing valid and invalid batches
and transactions and corresponding error messages. ATTI file is then passed to program
ARD080.
ARD080 (Transaction Edit/Merge)

Program ARD080 merges all monetary transactions and creates the files ATE1 (transactions in
error are moved to ATE1), ATNS (all the New Sale transactions are moved to ATNS) and ATVT
(all other Various Transactions are moved to ATVT). All balanced batches will be written into
ATBB file and imbalance batches into ATIB file.

It merges the following files:

ATT1 (today’s transactions from the online system)

ATJ1 (reject reentry items from the online system)
ATTI (user input)
AMWT (warehoused monetary transactions)
ATXT (today’s transfer transactions)

AM**
ATNS
ATVT

ARD100 IDCAMS
A Sort Define Files A
Transactions

AT*
BS HB OA
ATPT PS TF SC

ARD100 (Sort transactions to posting)

ARD100 sorts & merge all monetary transactions from ATNS & ATVT and creates ATPT (Posted
Transactions File) which will be used as input for posting program (ARD140).   

ATNS contains all new sales transactions and ATVT contains all the various transactions.  
A delete define step runs that will delete and define all the temporary master files.

AM*
AMAH BS HB PS ATIA
AMIH OA ATCM

IDCAMS ARD140
A Copy Files Posting A

AT*
BS HB PS
ATAH ATPT
OA O2
ATIH
LTDT
ATRF
The intermediate copy step copies the Insurance history master file to the temporary insurance
history file.

ARD140 (Posting)

ARD140 is the Posting program with multiple functions.These functions include posting
transactions to customer accounts,examining each account for reportable conditions, generating
the necessary report tag records, producing statement records , calculating fees assessed by the
system , accrues the interest, applies the payments to the system, sends accounts for
collections and many other tasks.      

Program ARD140 does the posting of monetary transactions using ATPT as input and updates
the master files.Also ARD140 generates several transactions for assessing fees, billing interest,
interest adjustments etc and post to the customer accounts.These generated transacations will
be available in the ATGT file created by ARD140.It updates the posting flag in ATPT and
ATGTfiles with any value ranging from 00 to 99. If the posting flag is other than zero, then it
signifies that the transaction hasn’t been posted to the system. A transaction can be rejected (for
many reasons) or warehoused.. These transactions

ARD140 is a driver program which calls many sub modules like D140ATPT,D140DELQ,
D140INT, D140LM30 etc to handle different types of tasks in posting. Each copybook has a
prefix of D140 and a 3 or 4 character file name (such as AMBI) or function name (such as INS).
For example D140AMBI is the inactive account processing copybook and D140INS is the
Insurance processing copybook. ARD140 is the top level routine and controls the overall
processing flow, performing the various functions as necessary.

AMDI
AMCR ATGT ABAI
ATGT
ATSP ATPT

ARD170 ARD175 ARD180

A Frequent Sort/Backup Monetary A
Shopper Gen. Trans Trans. Update

ABGT ATOS ABAO

AMSP AMWT
ATST
ATTA

ARD170 (Shopper Program Control Records Update)

ARD170 updates the Frequent Shopper statistics that are accumulated as part of the program
after multiple postings are run. ARD170 updates the Frequent Shopper Program (AMSP) control
file using records in the Shopper Profile Update (ATSP) file.

ARD175 (Sort ATGT and create ABGT Backup)

ARD175 sorts and backs up the generated transactions which are created by posting in the
generated transaction ATGT file.

ARD180 (Monetary History Update)

ARD180 processes the various monetary transaction files after they have been processed by the
posting program ARD140. It distributes these items to various output files depending on whether
the:

 Transaction was posted or non-posted.

 Transactions are to be printed in a statement run today.

The program reads each of the four input files - ATGT, ATPT, ABAI and AMDI.
Depending on the posting status and the statement status, the transaction will be routed to either
of the five output files:

a) Unapplied or nonposted transactions from the ATPT file are routed to the ATTA file.
b) Monetary transactions from both ATPT and ATGT files to be warehoused are routed to the
AMWT file.
c) Accumulated history back up transactions are routed to the ABAO file. This file contains all
posted transactions from the ATPT file, the ATGT file, and the ABAI file for those accounts not
printing on statements today
d) Statement monetary transactions are routed to the ATST file. This file contains the same
transactions as the ABAO file described above for those accounts printing on statements today. It
also contains any disputed items from the AMDI file for the indicated accounts.
e) Unstatemented posted monetary transactions are routed to the AMOS file.

AMHB
AMMC AMDI
ATCC-1 AMBI AMOA
AMBS AMPS
AMCR AMRT

ARU060 ARD185
A Initialize Multiple A
Files Rejects

AML1-4
ATM1 ATTA
AMT1
AMXT
AMM1
AMBM
AMOM

ARU060 (Initialize Transaction Files)

ARU060 program initializes the transaction files of the system. It initializes the files like AMJ1,
AML1-4, AMM1, AMT1, AMXT, AMOM, AMBM, AMOM, AMBM, AMOM, ATTD, ATTT, ATUD and
ATUT to make them ready for the next day update/processing.

ARD185 (Multiple Reject Processing)

ARD185 takes all those transactions, that are rejected by posting for multiple reasons and
generates Multiple reject records in the ATM1 file. (one record each for each reject reason). This
will list the multiple reasons because of which an account got rejected in posting. This will be
useful when we correct the rejected transactions thru online for Reject re-entry.

It uses various input files (AMHB / AMMC/ AMBI/ AMBS/ AMCR/ AMDI/ AMOA/ AMPS/ AMRT)
to create ATM1 and the program also updates the ATTA file.
 AMCR AMCR
ATM1 ATE1
ATTA

ARD190 ARD200
A Build Multiple Reject
Reject File Reentry

AMM1 ABJ1
AMJ1

ARD190 (Build Multiple Reject AMM1 File)

ARD190 creates the Multiple Reject AMM1 file with one record each for every reject reason
using ATM1(temporary multiple reject reasons) file as input. It also generates the Multiple Reject
Report.     

ARD200 (Build Reject Reentry)

ARD200 loads the rejected transactions from the day’s batch run to the Reject Master (AMJ1)
file. It also generates the Reject Reentry Batches Report. It uses AMCR, ATTA and ATE1 as input
and generates AMJ1 and takes the tape backup in the Rejected Transactions Backup file ABJ1.
These rejected transactions can be corrected thru online (ARMT) baed on the reject reasons so
that they can come into the system in the next days batch processing.
 Begin After Updat Begin Online
Batch Hours e Day
ITS
1 TRAM
S ITS
2 AS
M
SS SSC Utility
C Loads
CMS 1
(FAS) CMS
2
CT
A
CD
M
MB
S CMS 3
LT(FAS)
S CMS
4
CMS Daily Batch

Files from different sub systems (like ITS, ASM etc) are fed to the CMS batch and hence those
jobs are executed first and and their ouputs are fed to the CMS batch.

The ITS batch is split up into 2 sub batches as also the CMS batch that is split up into 4 sub
batches (CMS1, CMS2, CMS3 and CMS4) depending upon the kind of processing that is done in
each batch.
FAS processing takes place along with CMS1 and CMS3 while the ASM (Account Service
Management), SSC (Security Sub System), CTA (Collection Tracking and Analysis), CDM (Credit
Decision Management), MBS (Merchant Banking Sub System) and LTS (Letter Tracking Sub
System) sub-system batches run only once during the nightly batch cycle at specific instances.

The batch cycle can be split up into 4 phases and different sub system jobs run in each phase as
detailed below:

Phase 1 : Begin Batch (CMS Onlines are still up and normal day processing still available)

ITS1  TRAMS  ITS2

Phase 2 : After Hours (CMS onlines are brought down, Selective file maintenance available)

ASM and SSC  CMS1 (FAS)  CMS2  CTA, CDM and MBS

Phase 3 : Update (CMS onlines still down, no processing available)

CMS3 (FAS) and LTS

Phase 4 : Begin Online Day (CMS onlines are brought up again and normal day processing
available)

CMS4

The processing done in each sub-system is briefly explained below:

ITS1 – The charge backs and retrieval requests that are entered online in CMS will be extracted
and routed to TRAMS.
TRAMS – The input monetary transactions are validated and routed to the various sub-systems
here. In addition to this the outgoing requests to various external interfaces like schemes are
also handled here.
ITS2 – The incoming retrieval requests and charge backs from other schemes and other sources
are routed to the ITS system.
ASM – The batch processing for ASM happens here. External inputs to ASM and the daily house-
keeping of ASM records occur here.
CMS1 – Non-monetary and monetary updates happen in this application. In addition to this
interface files to external systems like LMS and CTA get generated here.
CMS2 – Processing of Open item billing, update of frequent shopper points, Monetary
transaction update, Inactive file processing, Statement file generation, card issue and reject re-
entry processing happens here.
CMS3- All the monetary and non-monetary updates that happened during the after-hours mode
will be applied to the main CMS files during this period.

CMS4- Report and statement generation happens here.

FWCC

ARD000
AROC/ARC OFU000 OFD100
On-line Day Control card EOD batch A
H
Close CMS Files load create
Open After Hours
files

OFED FBLG ATIA

FAS
End of Day
ATUD
FTCC

FTRF

After Hours/ End of Day

During the day, when the onlines are up, all the master files are updated (addition of new
accounts, file maintainence etc). In order to trigger the nightly batch cycle AROC transaction
needs to be fired.

AROC transaction is the after hours processing screen used to select a processing mode for
CMS master files. Three processing modes are available in this :

1. Normal Processing - All CMS master files are open.

 2. After hours processing – All CMS master files are closed and After hours files are
opened for Read only.
Shadow files are opened for Updations.

3. No processing - All CMS master files are closed to all processing (ARCA mode).

AROC (or ARCH) transaction (Open For After Hours A-H Processing) is fired to close all the
CMS files and also open the after hours files. In after hours mode, only certain non-monetary
transactions are allowed, monetary transactions are not allowed. AROC internally triggers OFED
transaction that sets the End of Day for the FAS sub system (FAS and CMS go hand-in-hand
hence at any given point of time, they should be running in the same mode).

Program OFU000 loads control card FWCC into file FTCC. Various FAS programs read the
control cards file for execution control.

After the control card load , OFD100 is triggered. It is the first batch program in the FAS end-of-
day batch process. This program generates a user input file for the VisionPLUS CMS daily run
and generates a backup of the FAS log file (FBLG). This program also produces and passes a
report file to OFD110 where all reports are generated. It reads AMCR, FMSC, FMLA, FMLB and
FTCC control card file (that was generated by OFU000) and creates the following output files:

FBLG : Log file (Tape Backup)

ATIA : CMS authorization transactions to posting
ATUD: CMS non-monetary transactions
FTRF : FAS reports file

AMCR AMCR AMCR

AM*
SWCC SWCC SWCC

ARU000 ARU000 ARU000 ARD000

A Control card Control card Control card File A
Load #1 Load #1 Load #1 Integrity
check

ATCC-1 ATCC2 ATCC3

ARDAILY1 (Account Receivable Daily CMS1)

ARU000 (Control Card Load)

Execution of ARU000 program starts the CMS1.

ARU000 loads the program control cards (SWCC) to the control cards ATCC-1, ATCC-2 and
ATCC-3 files. Various programs read the control cards files for execution control.
ARD000 (File Integrity)

Before executing any batch it is important to verify that all the files used in the system are in
sync with each other i.e. the date and time stamp of these files should match with each other.
The program which does this file integrity check in CMS batch is ARD000. It ensures the integrity
of date and time stamps on all the master files. It also ensures the integrity of the General
Ledger (AMGL) file and the Monetary Transaction (AMMC) file.

The program opens and reads the first record which contains the current date and time stamps
from System Control Master (AMCR) file. The program then opens and reads the first record of
each master file. If it is a header record, the program checks the date and time stamps to ensure
that they match the date and time stamps on the System Control Master File. It generates a file
integrity report for each file with the reason of ‘MATCH’ or ‘NO MATCH’. Even if there is a single
'NO MATCH' the program abends.

File Integrity check ensures all the master files in the system has same date and time and
confirm that all the master files are in sync and last batch processing was successful.

AM*
L1 L3 J1
AM* T1 XT ATCC-1
ATCC-1 ATCC-1

ARU020 ARD020 ARD060

A Master File On-line Trans Date Roll B
Backup Extract

AT*
ABMF L1 L3 J1 ABTF AM*
T1 XT

ARU020 (Master File Before Backup/Reload)

ARU020 program performs either a backup of all the master files or a reload of the master files
to their appropriate segments. The option of taking the backup or reloading the data is controlled
by the ATCC control card. The control card also determines the files to be processed. The system
produces a report that shows the control card image used and the number of records processed
by file.

It takes the back up into the tape file ABMF. The backup of the master files needs to be taken
twice, once before the batch is triggered (i.e. after file integrity and before monetary and non
monetary updates are applied to the files) and once after the posting and statement jobs are
completed.
This is required because in case anything goes wrong during the batch run, system can get the
correct data before the batch started by reloading the master files from ABMF file

ARD020 (Online Transaction Extract)

ARD020 extracts the online transactions from VSAM files AML1, AML3, AMT1, AMJ1 and AMXT
and generates sequential files for batch processing. A backup function loads the transactions to a
tape file and a reload function generates the sequential disk files from the backup tape.

ARD060 (Date Roll)

ARD060 establishes the correct processing dates for the system and organizations. It also
updates the time and date stamps for the non segmented master files.

The program opens the ATCC and AMCR file and validates and sorts the control cards. If no
control card files are present, the program asumes next day processing and updates the required
date fields (today's date, previous process, next process and accrue-through dates) for system
and organization records. It also generates a statement indicating whether a specific
Organization is processing that day or not.

When the program completes this process, it prints the report line for this file and updates the
date and time stamps for non-segmented master files used by the system and also prints the
report line for all the files.
In the TEST environment (future interest or delinquency testing) some future date could be
entered in the control card file and the system would process for that future date.

TRAMS ATTD

ARD011 ARU080 ARD080

Sort TRAMS User Monetary Monetary A
Edit Trans Merge

ATEI
ASM ATTI ATNS ATBB
ATBB
ATTD AWT1 ATVT ATIB

ATTT
Monetary User Input (ARD011, ARU080, ARD080)

After the file integrity, master file backup and date roll, the batch does the processing of the
monetary user inputs (that are fed to the CMS through TRAMS). The monetary user inputs are
handled by the programs:

ARD011
ARU080 and
ARD080

Details of these programs has been already covered in the Monetary Batch Flow part earlier.
 AM*
(37 files)
AMCR ATL1
ATCC-1

ARD065 ARD040
A Date Roll File Maintenance B
Journal Report

AT*
AM* FR O1 TS
(22 files) NM NU

ARD065 (Date Roll – Account)

ARD065 updates the time and date stamps for the account-based master files of the system.

The program opens and reads the system record from the AMCR file. Then it opens and reads
each account based master file to ensure that it is a header record. It again does a date and time
stamp check and abends for mis-match. Here, since the date and time stamp of the AMCR file is
already rolled over (by ARD060) the check is done with the last processed date and last time
stamp from the AMCR file.

If the date and time stamps match, the program moves the new date and time stamp from the
system record to the file's PROC-DATE and TIME-STAMP fields and then closes the file.

ARD040 is run twice in a daily batch:

 once in the journal mode to generate a file maintenance journal report of the non
monetary updates that were done in onlines during the day.
 Once in the User Input (Update U) mode to update the master files.
 ATUT ATUI
ATUD ATCC-2 ATNU
(ATL1)
ATCC-2

ARU040 ARD040 ARU780

Nonmonetary User Input Mater Alpha Search A
Edit Files Update Update

AM* AT*
NA BS FR O1
ATUI ED PM TS AMNK
NM NU AMBX
User Non-monetary (ARU040, ARD040, ARU780)

Details of these programs has been already covered in the Non-Monetary Batch Flow part
earlier.
 AM**
ATNS AMIH
ATVT

ARD100
Sort IDCAMS
IDCAMS
Transactions Copy Files
Define Files

ATPT
AT* BS BT HB IC IH ATIH
LS OA PS TF SC PH

ARD100 (Sort Transactions to posting)

ARD100 sorts the monetary transactions to the Posting program – ARD140.

The program reads the records in the ATNS (New Sales) and ATVT (Various Transactions) files
along with the relevant master files, and passes the records to the sort file. The program assigns
each record a secondary key in addition to the primary sort key.

The sort sequence done by ARD100 is very important as it would decide the manner in which
various monetary transactions would be applied by posting in the system that would affect the
balances on which interest and other dues would be calculated. The initial sorting is done on the
organization, account and the effective date of the transaction and then in the following
sequence:

ATNS Credit Transactions: First, all the credits coming in for new sales needs to be applied in the
system as those would affect the balances on which interest and other due calculations are done.

ATNS Debit Transactions: It should be followed by new sales that come in on that day as these
need to be applied in second highest order of priority.

ATNS Memo Transactions: The next in sequence would be all the new sale memos.

ATVT Credit Transactions: All the credits coming in for various transactions need to be applied in
the system after all the new sale related transactions are applied..

ATVT Debit Transactions: Finally the various transactions debits need to be applied.
The output procedure of the sort builds the header record for the ATPT file, returns the sort
records and writes them to the ATPT file, and builds the trailer record for the ATPT file, which in
turn will be passed to the posting program – ARD140.

ATPT contains all the monetary records that are ready for posting into the master files.

A delete define step runs that will delete and define all the temporary master files.

The intermediate copy step copies the Insurance history master file to the temporary insurance
history file.

----------------------------------------------Page break in WBT ---------------------------------------------------

AM* AM*
BS HB PS ATIA BS BI
OA ATCM ED CR

ARDAILY
ARD140 1 ARD117
A Posting Complet Quarterly A
e: Report Sort
ARDAILY
2 Start

AT*
BS HB PS ATQR
OA O2 ATPT
LTDT
ATRF

ARD140 (Posting)

The ARD140 posting program is the most vital program in CMS and performs multiple functions.
These functions include posting transactions to the customer accounts, examining each account
for reportable conditions, generating the necessary report tag records, producing statement
records, and calculating fees assessed by the system.

The program can be run in two modes:

1) Disk-in-disk-out : In this mode, the master files are re-written to temporary datasets and the
rest of the CMS processing uses these temporary files for further processing and at the end of
the batch, the master files are rippled with these temporary files.

2) Update mode: In this mode, the master files are updated directly.

The execution of posting completes the CMS1 and CMS2 starts with the execution of ARD117.
ARDAILY2 (Account Receivable Daily CMS2)

ARD117 (Account/Card Quarterly report Sort)

ARD117 reads all of the segments of the Account Base Segment file (AMBS), all of the
segments of the Inactive Account Base Segment file (AMBI), and the Embossing Data file
(AMED). The program creates a sorted sequential file (ATQR) that is input to the Cardholder
Quarterly Report File Update program (ARD119).

ATCQ AMCR AMCR

AMCR ATQR ATRT

ARD118 ARD119 ARD144

A Quarterly Cardholder Relationship A
Update Quarterly Embosser

AMCQ AT*
AMCQ
1T 2T
AMAX 3T 4T

ARD118 (Update Cardholder Quarterly Report File)

ARD118 updates the Cardholder Quarterly Report (AMCQ) file from the temporary quarterly
reporting file generated during posting.

ARD119 (Cardholder Quarterly Report File Update)

ARD119 updates the card totals and account totals for all regions of quarterly reporting.

The program processes each organization in the order they appear in the ATQR file. The
program loads affiliate records for Visa, MasterCard, and Europay and updates the account and
card totals.

Affiliate records by organization will be written to the AMCQ (Cardholder quarterly report) file

ARD144 (Split Relationship/Embosser Update File)

ARD144 examines relationship tag records based on record type(embosser or embosser

statistics or relationship or relationship statistics) and splits the records into the appropriate tag
files. These files are processed in the later CMS programs in the batch.
This program takes the ATRT (relationship tag) file and generates the embosser, relationship and
embosser statistics files. Relationship tag file is the output from the posting program which has
the data for the embosser and relationship statisitics.
This program also updates the relationship cross reference file (AMAX)

AMCR
AMDI
ATCU AMOI
ATOT

ARD150 ARD159 ARD160

A Update System Sort Open Open Item A
Control Item Trans Trans Update

AMCR ATOI
AMRT ATOS
ATOT

ARD150 (Update AMCR and produce daily balancing report)

After processing the ARD144 program, the next program in the flow is ARD150 program which
updates the system control record and the rate table file.
ARD150 performs the following functions:

1) Accumulates the balancing totals from the posting run and updates the system control file (i.e
AMCR) with these totals.
2) Resets the options on the processing control record on the system control file.
3) Produces the daily balancing report (R32).
4) The one time options which are set on AMCR will be discontinued.

ARD159 (Open Item Transaction Tag Sort)

ARD159 sorts the open item transaction tag (ATOT) records into a specific account number
sequence to support the open item billing transaction processing. ATOT file is a output file from
the posting program which contains the transactions for the open item billing account.
The records in the ATOT file are sorted in the ascending order and the primary sort key is org
and account number.

ARD160 (Open Item Transaction File Update)

ARD160 reads the Open Item Billing Transaction file (AMOI) and the open item transactions tag
(ATOT) file and will do the open item billing processing for the day. The open item billing
transactions will be written to the ATOI file. The open item statemented transactions are written to
ATOS file.
 AMCR AMDI
ATGT ABAI
ATSP ATGT
ATPT

ARD170 ARD175 ARD180

A Frequent Sort/Backup Monetary A
Shopper Gen. Trans Trans. Update

ABGT ATOS ABAO

AMSP AMWT
ATST
ATTA

ARD170 (Shopper Program Control Records Update)

ARD170 updates the Frequent Shopper statistics that are accumulated as part of the program
after multiple postings are run. The updates to the Frequent Shopper Program (AMSP) control
file will be done using records in the Shopper Profile Update (ATSP) file. ATSP file will be having
the updated data from the posting and applies the frequent shopper data to the AMSP file . The
previous redemption data will be updated in the AMSP file.

ARD175 (Sort ATGT and Create ABGT Backup)

ARD175 sorts the ATGT file. ATGT file is the generated transaction file which will contain the
data for the system generated transactions like membership fee, late charges, service charges
etc., The program also simultaneously generates a backup of the original, unsorted ATGT file
(called ABGT). The ABGT file may be dummy file that can be ignored. This file can be used
when this program abnormally terminates due to power failure, accidental cancellation and so
forth.

ARD180 (Monetary History Update)

ARD180 processes the various monetary transaction files after they have been processed by the
posting program ARD140.

It distributes these items to various output files depending on whether the:

 Transaction was posted or non-posted.

 Transactions are to be printed in a statement run today.

The program reads the each of the four input files - ATGT, ATPT, ABAI and AMDI
The input file files will have the following data:

ATPT
1) Posted monetary tranasactions (Posting flag = 00)
2) Warehoused tranasctions (posting flag = 98)
3) Nonposted tranasctions (Posting flag = 01 to 97)

AMDI
This file will contain the data for the disputed items

ATGT
1) Posted generated monetary transaction (posting flag = 00)
2) Statement notification (ATGT-MT-TYPE = S)
3) Warehoused ACH payments (Posting flag = 98)

ABAI
This file conatins all previously posted monetary transactions that were not billed or printed on
statements

Depending on the posting status and the statement status, the transaction will be routed to either
of the five output files.
a) Unapplied transactions are routed to the ATTA file.
b) Warehouse monetary transactions are routed to the AMWT file.
c) Accumulated history back up transactions are routed to the ABAO file.
d) Statement monetary transactions are routed to the ATST file.
e) Unstatemented posted monetary transactions are routed to the AMOS file.

AMHB
AMMC AMDI AMCR
ATCC-1
AMBI AMOA ATM1
AMBS AMPS
AMCR AMRT

ARU060 ARD185 ARD190

A Initialize Multiple Build Multiple A
Files Rejects Reject File

AML1-4 ATM1 ATTA

AMM1
AMT1
AMXT
AMM1
AMBM
AMOM
ARU060 (Initialize Transaction Files)

ARU060 program initializes the transaction files of the system. It initializes the files like AMJ1,
AML1-4, AMM1, AMT1, AMXT, AMOM, AMBM, AMOM, AMBM, AMOM, ATTD, ATTT, ATUD and
ATUT to make them ready for the next day update/processing.

The control card designates the files that the program initializes.

ARD185 (Multiple Reject Processing)

ARD185 program takes rejected transactions from the Unapplied Transaction (ATTA file) created
by posting and generates Multiple reject records. (one record each for each of reject reasons).

Using the Inputs shown in the slide, this program creates ATM1 (Multiple Reject Transaction) file
and updates ATTA files.

ARD190 (Build AMM1 File)

Program ARD190 builds Multiple reject transactions (AMM1) file with one record each for every
reject reason using file ATM1 as input. ATM1 is the multiple reject transactions file from ARD185
program. ARD190 program prints the multiple reject report (R36). The records written into the
AMM1 file will be in the sorted order of batch date, batch source, batch number and sequence of
report records.

----------------------------------------------Page break in WBT ---------------------------------------------------

AMCR
ATE1 AMCR
ATTA AMRC
AMZC
ATFR

ARD200 ARD210
A Reject Fraud A
Reentry Reports

Fraud Report
ABJ1 AMFF
AMJ1
ARD200 (Build Reject Reentry)

ARD200 handles the reject-reentry and also creates the rejected monetary transactions (AMJ1)
file taking the rejected transactions from today’s run. It also takes the backup of AMJ1 file into
ABJ1(tape file).

Rejected monetary transaction file (AMJ1) is build from the Edited transactions (ATE1) file and
Unapplied transactions (ATTA) file as input.
This program also generates the reject reentry batches report (R15).

ARD210 (Fraud Reports Print)

ARD210 program prints the non monetary fraud report from Fraud report (ATFR) file , updates
the fraud suspect (AMFF) file and clears the fraud file statistics at the month end and year end.

AMMC
AMCR AMCR
ATAM
ATAI AMAM
ATCC-1 ATAR
ATCC-1

ARD250 ARD420 ARD440

A Transfer Activity Recap Activity Recap A
Inactive/Active Update Restore

AMBI AMHB AMAM

AMHI ATAM
AMBS
AMSC
ARD250 (Active/Inactive Account Processing)

ARD250 processes the migration of base segment records between the Account Base Segment
(AMBS) and the Inactive Account Base Segment (AMBI) files. ARD250 also transfers account
history records from the Base History (AMHB) file to the Inactive History (AMHI) file when the
Account Base Segment record (AMBS) is transferred to the Inactive account base segment
record (AMBI) file.

The active and inactive account migration is driven by a control card which either migrates from
active to inactive or inactive to active.
ATAI (Active/Inactive tag) file will have the information of the accounts which need to be
migrated.

ARD420 (Activity Recap Update)

ARD420 posts the activity recap transactions generated by the Posting program (ARD140) to the
Activity Recap master file. This program is driven by the control card which designates the end
of month for the general ledger and the organisations to be extracted.
The ATAR file will be checked with the activity recap master file (AMAM) file and the data will be
written into the sequntial recap master file (ATAM) file. An updated version of the master file will
be generated in ARD440 program.

ARD440 (Activity Recap Restore)

ARD440 replaces the prior Activity Recap master file with the updated file generated by the
Activity Recap Update program (ARD420).

This program sorts the updated Activity Recap master (ATAM) file into key sequence and
generates the VSAM (AMAM) master file.

AMCR AMCR
ATTS ATSM

ARD600 ARD220 IDCAMS

A Promotional Set Condition Define A
Statistics Code

AMTP ATCC-5 AMDT ATSS

ARD600 (Promotion Statistical Update)

ARD600 updates the AMTP (Promotion statistics) file using the ATTS (promotion statistics tag)
file generated by ARD143. This program applies the statistical transactions generated by
ARD143 to the AMTP file.

ATCC control card is generated for each org at the end of the month which will be used by
ARU620 to print the promotional statistical analysis reports.

ARD220 (Set Condition Code for Online Statements)

ARD220 program sets a condition code in the daily batch run to zero or 004 to indicate whether
there is any statement activity to be merged. This return code will be used by ARD240 to
determine whether it should process the merging today or not.

The program checks the ATSM file for the detail records, if no detail records are found then it
sets the return code to 004 indicating there was no statement activity and ARD240 should be
bypassed.

If the detail record is present in the ATSM file, then it sets the return code to 000 and updates the
AMDT file with the system record date and time stamp.

The next step in the Batch flow is to define ATSS (temporary file for small statements) that would
be later renamed as AMSS.
 AMCR AM*
ABSI
AMDT ATSM ATCC-1
ATST
ATCC-1

ARD240 ARD230 ARU020

A Small Online (Re)set Master File A
Statements Cond. Code Backup

ATSS ABMF
(AMSS) ABSO

ARD240 (Small Statement/Online Statement 1 Processing)

ARD240 program maintains the small statement file (AMSS), also known as Online statement 1
file. On a daily basis the small statement file handles the statement records that were
accumulated by the online statement file.

The program has five functions which can be controlled by the Control card (ATCC-1). The
following are the options available:

1) Create – In this mode it creates the ABSO file (Small statement backup file).
2) Reload – In this mode it creates the AMSS file by taking the data from the ABSI file.
3) Backup – In this mode it takes the backup of AMSS file into ABSO.
4) Merge – In this mode it takes the ABSI, ATSM, ATST files to generate the ABSO and AMSS
file.
5) Reset – In this mode it generates an ABSO master file that contains only the file header and
trailer.

In the example shown on the screen, the ARD240 program runs in the merge mode. It creates
AMSS and ABSO files by taking ABSI, ATSM and ATST files as input.

ARD230 (Reset Condition Code to Zero)

ARD230 program unconditionally resets the condition code to zeros for the condition code set by
ARD220 program.

ARU020 (Master File After Backup/Reload)

ARU020 program does two functions :

As mentioned ARU020 is executed twice in any nightly batch. Here it executed the second time
to take the after backups of the master files.
 AMCR AMRM
AMCR AMBS AMAX
ATEI AMBI AMCC
ATEO ATCC-1 AMNA

ARU190 ARU200 ARDAILY

A Issue File Card Issue 2 A
Complet
Merge e

ATEM

ARU190 (Sort/Merge Embossing ATEI and ATEO Files)

ARU190 program sorts and merges the Embossing issue (ATEI) and Embosser issue multi
attempt (ATEO) files and creates the Embosser merged accounts (ATEM) file.
This program produces Merge ATEI/ATEO records report (T190).

ARU200 (Card Issue)

ARU200 program generates the embosser, card mailer, PIN mailer files required to satisfy the
card issue requirements.

ATCC control card is used to control the processing of card issue for all the orgs and logos or
selected orgs and logos.

It takes the ATEM file, AMED file based on the orgs and logos selected and determines the
action to be performed (new , replacement, additional cards or PIN mailer). AMBS, AMNA,
AMCR files are read to provide with the information which is missing from the embosser data
file.

If the new, replacement or additional card is requested then this program writes a user input tape
file (ATUT), which is used to update the issue flag on the AMBS file.

The output files generated from this program are:

1. Pin mailer issue file (ATI3)
2. Embossing tape file (ATET)
3. User input non monetary (ATUT) and
4. Embosser issue multi attempt (ATEO) files

The execution of ARU200 program completes CMS2 and CMS3 starts by firing the
AROC(ARCA) online transaction.
 Process FAS

ARDAIL
ARD000
AROC/ARCA A
Y3 A Close all CMS Files Rename CMS
Start Files

ARD000
OFAH Load Log
FAS End Files
Processing

ARDAILY3 (Account Receivable Daily CMS3)

AROC (Close all CMS files) – By selecting this option, it closes all the CMS files and after hours
files.

During this process it suspends the FAS online processing, delete the CMS master files,
renames the temporary CMS files, the fas log files will be switched off between FMLA and
FMLB.

ARCA initiates OFAH. This sets the FAS end of processing. This will suspend the online
processing due to after hours transaction update.

After this OFD200 is run which switches the log files, re-initialize the inactive log and pointer
files.

In this mode all the master and shadow files are closed, no authorization is given. Hence no
transaction can take place during this period. This condition will last for a short duration.

During this time all incoming authorizations are handled by Visa or Master card on behalf of the
issuer. This is called STIP (Stand In process).
 AMCR
ATSM

IDCAMS IDCAMS
A Delete Rename
Master Files Master Files
ARD220
Set Condition A
Code

AM*
AT* > AM*
BS HB OA OI AMDT
OS PS SC TF

During the ARCA mode (Close All No Processing), the CMS master files (AMBS, AMNA etc.,) will
be deleted. This will only happen if the update switch on the system record (AMCR-S-ACCT-
MSTR-UPDATE-SW is set to ‘D’) is DISK IN DISK OUT.

The CMS temporary files thus created in the nightly batch cycle ( like ATBS, ATNA etc.,) will be
renamed to the CMS master files (like AMBS etc.,).

ARD220 (Set Condition Code For Online Statements)

ARD220 program sets the condition code in the daily batch run to zero or 004 to indicate whether
there is any statement activity to be merged.

AMSL SWCC
AMOS AMSS AMCR
AMPS

IDCAMS ARD245 ARU000

A Rename AMLD build Control card A
Master File load

AMLD ATCC -3
Delete AMSS
ATSS > AMSS
The old AMSS file is deleted and the temporary Small Online Statements file ATSS is renamed
as AMSS through IDCAMS.

ARD245 (Generate AMLD File)

The next program that gets executed is the ARD245 program. ARD245 program generates the
life to date transaction (AMLD) file from the data in the online accumulated transactions (AMOS)
file, small online statement (AMSS) and the large statement (AMSL) file.

It checks for the eligible transactions and non disputed transactions and writes them into the
AMLD file. AMPS file is used to pick the loan data.

ARU000 (Control Card Load)

The ARU000 program loads the program control cards (SWCC) to the control cards (ATCC) file.
Various programs read the control cards file for execution control.

AML1(S) ATL1(S)
AML3(S) ATL3(S)

ARD020 IDCAMS
A After Hours Repro A
Trans. Extract

ATL1(S) ABTF AML1

ATL3(S) AML3

ARD020 (Online Transaction Extract for After Hours)

ARD020 program does the online transaction extract from VSAM files. This generates sequential
files for batch processing. This step in the after hours processing will copy the after hours log
files i.e AML1(S) and AML3(S) into ATL1(S) and ATL3(S). The program also takes a tape backup
on ABTF(S).

Next, IDCAMS Repro step would be executed that will repro ATL1S to AML1 and ATL3S to
AML3.
In this way all the information will be updated in the log files. Although, the master files would be
updated just before onlines are brought up, the actual reporting (of the logs that written in AML1S
and AML3S) would be done in the next day’s batch.

ARUP
After Hours
Update

AROC/ARO
ARD000 ARDAILY
A 3
A Open On- A
Complet
line Files e

OFRN OFAU
Resume After Hours
Normal Update

AROC (Open online files Normal Processing) is another mode of processing in the batch. It is
also referred to as AROA mode. In this mode it opens all the CMS files and closes all the after
hours files. The system is live in this mode.

This mode initiates the OFRN transaction which sets the FAS processing mode to normal.

OFAU runs in the background and will attempt to repost the transactions that were entered during
the end of day in the master files from FAS log files FMLA/B/C/D.

ARUP transaction runs in the background to put the updates from AML1 and AML3 (updates to
various master files which took place during after hours) into the master files.

Firing AROC(AROA) transaction completes CMS3 and CMS4 starts.

 ATCC3 ATCC-3
AMCR

ARU900
ARDAILY A Initialize After A
4 Start Hours Master Files

AML1 -
AM*(S) 4(S)

ARDAILY4 (Account Receivable Daily CMS4)

ARU900 (Initialize After hours Master Files)

After the online are brought up by triggering AROC/AROA, all the After Hours Shadow Master
Files need to be initialized for the next day After Hours processing. ARU900 program initializes
all the CMS master files (Shadow). It reads the ATCC-3 control card to establish which master
files are to be initialized. The program then performs the following sequence for each master file
specified on the control card:

The program then opens the file, generates a header record and writes it to the file, generates a
trailer record and writes it to the file (when applicable).

The exceptions to this are the AMCR and AMDT files.

For the AMCR file, along with the header and trailer, the program writes a system-level
statement message for the statement program, which requires at least one statement message
record to be present for statement processing.

ARU900 generates the entire AMDT file. In addition to the header and trailer, the program also
generates three detail records.

ARU060 (Initialize Shadow Transaction Files)

The next program that gets executed is ARU060. It initializes the transaction files (shadow) of the
system i.e. AML1S, AML2S, AML3S, AML4S. It reads the control card to identify the transaction
files to be initialized. The program will write a header record in each of the requested file.
 ATCC-3 AMCR ARDAILY
4
AMBS/ED/NA(S) Complet
AMBI AMSD e

ARU100 IDCAMS
A Alpha Name Key On-line Day
Initialize Delete Define
Files

AMBX(S) AMAX(S)
AMNK(S) AMCX(S)
AMRX(S)

ARU100 (Initialize Shadow Alpha Name key)

The next program in sequence is the ARU100 that initializes the shadow Base/Customer Cross
reference file AMBX(S) and Shadow Alpha Name Key file AMNK(S).

After the shadow master, shadow transaction and Alpha name key initialize, IDCAMS
Delete/Define step is executed that deletes/defines the following shadow files:

Shadow Account-to-Card Cross Reference file AMAX(S)

Shadow Customer Relationship Cross Reference file AMCX(S)
Shadow Account/Relationship Cross Reference file AMRX(S)

In this way, all the shadow files are made ready for next day after hours processing.

While all the shadow file processing is taking place, it is already online day for CMS sub-system.
 AMCR
ABLI
AMDT
AMSS
ATCC-1

ARU340
Large Online
Statement Merge

AMSL ABLO
ATSH

ARU340 (Large Statement/Online Statement 2 Processing)

ARU340 maintains the Large Statement (AMSL) file, also known as the Online Statement
2 file. The program maintains the accumulated online statement records that need to be
reviewed for recap or deletion on a periodic basis.

This program has the following main functions, all invoked by a control card:

Create: This function initializes the Large Statement Backup Output (ABLO) file, which is
normally a tape file. This file is considered to be the Large Statement master file, and the
AMSL file is a copy of this file placed on VSAM disk for access by the online portion of
the system. Once the ABLO file is generated, the Reload function of this program must be
run to initialize the disk file.

Reload: This function takes the ABLO file and copies it to the AMSL VSAM disk file.

Backup: This function takes the AMSL VSAM disk file and copies it to the ABLO file.

Merge: This function takes the ABLI (ABLO from previous run) file and the AMSS (Small
Statement master file) to generate the ABLO (tape) and AMSL (VSAM disk) files as output. This
process updates the Large Statement master file. The Merge function is run strictly on a request
basis.

IMPORTANT NOTE

There are certain programs like ARD117/ ARD118/ ARD119/ ARD159/ ARD160/ ARD170/
ARD420/ ARD440/ ARD600 and a few other programs for which every installation will decide
their use based on the features they plan to use from Base V+ product.

The above Batch Cycle briefs the core V+ Batch Cycle provided by Paysys, hence it is not
mandatory that every program would get executed in a specific installation Batch Cycle. Certain
programs will get executed only if that feature is turned on at installation or there could still be
some new installation specific programs (In house /custom programs) that are outside of the core
batch cycle.