CMS Questions:

Basic Questions:

1. Credit limit change via online screen is monetary or non-monetary change?

Answer: It is a non-monetary change.

2. What is the driver file for ARSD transaction? What is the driver file for ARTD
transaction?

Answer: AMSS/SL, It contains detailed statements of all the cycles of the account till date
along with the individual transactions.

ARTD : AMOS, It contains all the transaction on the particular account till date since last
cycle, AMOS is build daily.

3. When an Authorization is done through FAS how the OTB of the transaction
amount gets adjusted in CMS?

4. The transaction done in a particular day for the particular account can be visible
in which CMS screen after Batch Run (posting) and what is the file Name in which
it get stored?

Answer: ARTD and file Name is AMOS

5. What is the file in CMS in which the Customer Demographic information is

stored?

Answer: AMNA (Customer Name Address Information)

6. Where in CDM you can see the last account number generated for a given Logo
and Bin Range?

APTM17—Account Setup and Embossing

What are the different modules in vision plus and how one is connected with the
other?

What is a Grace period in Vision Plus?

grace period Number of days after a statement is produced during which a finance charge
is not assessed if the customer pays the statement balance in full.
What are the different D140 copybook components any three, tell the significance of
the same?

D140ATAR, D140ATPT, D140ATGT, D140ATSM, D140DELQ,

D140LM30 is a copybook in ARD140 that performs global payment processing.
**D140CCSI is a copybook in ARD140 that performs PaySys standard routines.
D140XFR is a copybook in ARD140 that performs account transfer processing.

7. Is it possible to set a new account directly in CMS through screens? If Yes How?

Answer: An established account for a customer consists of the following records:

1. Customer Name/Address record
2. Account Base Segment record
3. Embosser record (optional)
4. Credit Plan Segment record (after monetary activity occurs)
5. Relationship records (optional).
We can establish an account by using a single function, New Account Setup (ARSB).
The New Account Setup function enables you to choose the records you want to add
(Customer Name/Address record, Account Base Segment record, Embosser record, and
Relationship record), then prompts you to the online screens that correspond to the
records you selected.

8. In which file and in which Screen the transaction codes are defined?

Answer: You can define a Monetary Transaction Code record for each organization you
process. You can establish this control record only at the organization level. Use the
Monetary Transaction Control functions to add (ARAX), modify (ARMX), and view
(ARQX) the Monetary Transaction Code records.

9. Where the Block code Matrix is defined and how many block codes can be
defined in CMS? How we can control the priority of the block codes?

Answer: CMS enables you to define up to 27 block codes (A–Z and space) on ARML07
and ARML08. Each block code can indicate special conditions and automatic processing
activities that you can apply at the account level. You can apply up to two block codes to
an account (BLK CODE 1 / 2 on ARMB01).
When you define the block codes for a logo, you assign a priority to each block code PRI
on ARML07 and ARML08). Since you can apply two block codes to an account, the
priority indicates to CMS, which assigned block code to activate first.
CMS enables you to define up to four letter codes for each block code (LTR 1 to TR 4
on ARML09 and ARML10). CMS sends the letter codes to CTA or LTS to generate the
letters whenever a block code condition has been in effect for a specific number of days
(DAY 1 to DAY 4 on ARML09 and ARML10). For example, CMS sends the letter code
in LTR 1 when the block code has been in effect for the number of days in DAY 1. CMS
sends the letter code in LTR 2 when the block code has been in effect for the number of
days in DAY 2, and so on.
10. What do you mean by Outstanding authorization.
CMS accepts bankcard authorizations and keeps them as outstanding authorizations in
AMOA file until
• The user-defined expiration date
• In the case of Visa auto rental or hotel transactions, until the industry-standard
duration specified on the transaction itself has expired
• A match comes along for an actual transaction.

11. What is authorizations knocking off process where and when it happens?
Difference in processing if outstanding auth found & if not found.
When match comes for an actual transaction through TRAMS, outstanding authorization
from AMOA is knocked off.
If the match is not found, that transaction remains in AMOA file until the expiration date
for that transaction.

12. Explain terms like OTB, BLANACE and Credit LIMIT

OTB: Open To Buy
Balance: CR – OTB
Credit Limit: Total limit up to which customer can avail the credit.
OTB = The formula for the same is different for different banks.
OTB = 1.1 * Credit Limit – Total Amount Due.

13. What is the importance of Relationship record in CMS

Relationship record enables to process multiple cards issued under one account.

14. Explain control record hierarchy in CMS

Org->Logo->Relationship Number->Customer Number->Account Number-> Card
Number

15. Few ORG level, Logo Level system level screens in CMS
ARQO, ARQL, ARQS and corresponding Add, maintain screens.

16. How the Files are manipulated and used during after-hours processing (Shadow
file and temporary files for CMS master files etc.)

17. Explain the Reject reentry and screen and process associated with it in CMS
A batch of transactions consists of a batch header and the individual transactions. The
batch header contains the batch number used to identify the batch of transactions, the
number of transactions in the batch, the total number and amount of debit transactions in
the batch, and the total number and amount of credit transactions in the batch.
ARMT02—Monetary Batch Transactions Reject

REJECT DESCRIPTION Description of the posting action indicated by the posting

flag
that will be used for the reject reason. The screen displays up to five reject reasons.
POSTING FLAG Flag that identifies the posting action. The posting flag is also called a
reject code.
00 = Posted 01 = Account blocked
02 = Account closed or purged 03 = Invalid logic module
04 = Invalid transaction code 05 = Invalid effective date
06 = Account charged off 10 = Account not found
11 = Plan segment not found

18. Explain the concept of warehouse transaction in CMS.

In ARD180 the ATPT file is read as input and contains three types of records:
Posted Monetary Transactions
These are items that were received by posting from various external sources through the
Transaction Edit Merge program and were posted to the base segment and credit plan
segments of the account base. ATPT-POSTING-FLAG = 00.
Warehoused Transactions
These items were not posted or nonposted because (1) the organization was not
processing today, (2) they were against accounts that were transferred, or (3) postdated
transactions.
This file contains all transactions to be warehoused, received from both the ATPT and the
ATGT Input files. This transaction can be identified by ATPT-MT-POSTING-FLAG = 98.

Nonposted Transactions
These are items that could not be posted to an account due to an error condition.
ATPT-POSTING-FLAG = 01–97

ARTD04—Warehoused Transaction Select This screen displays the warehoused

transactions for the account.
ARTD05—Disputed Items Transaction Select
ARTD03a—Memo-posted Transaction Display
memo credits Payments received, but not yet posted to the account.

19. What is delinquency? Which screen displays delinquency information?

Delinquency identifies the number of billing cycles for which a payment is due.
ARQB (Page 3).
Recency delinquency Number of billing cycles since CMS posted the last qualified
payment to an account. The level of recency delinquency is indicated by a value 0–9.
Contractual delinquency The number of billing cycles for which a payment is due on an
account. The level of contractual delinquency is indicated by a value 0–9.

20. Explain the terms like Acquire and issuer in conjunction with MBS and CMS
module.
21. How we can identify replacement and add-on card from given card number?
Which is the check digit? What is BIN?
A particular customer may have multiple cards the different cards are distinguished
using digits 13 and 14.
Digit 15 is used to identify whether a card is replacement card.
Digit 16 is check digit.
Digits 2 through 6 are the bank number (BIN).
BIN is Bank Identification Number.

22. What does the first digit in the credit card number signify?
It signifies the System.
3 – Travel/entertainment card
4 – Visa
5 - Mastercard

23. What are all track data elements?

The magnetic stripe is used to capture data from the card to identify the card. It consists
of various tracks. The data present in the magnetic strip is called the track data.
Some of the Track Data Elements:
Primary account number - up to 19 characters
Country code - three characters
Name - two to 26 characters
Expiration date - four characters or one character
CVV- card verification value is used to identify validity of the card for the particular
issuer, this
validation is done at the issuer.
Note: CVV is for visa card but for a master card it is CVC.

24. Explain the steps involved in a normal credit card transaction.

Steps involved in a normal credit card transaction:

1. Merchant calculates the amount of purchase and asks buyer for payment
2. Buyer presents merchant with a credit card.
3. Merchant swipes credit card through the point of sale unit. The amount of the sale is
either hand-entered or transmitted by the cash register.
4. Merchant transmits the credit card data and sales amount with a request for
authorization
of the sale to their acquiring bank.
5. The acquiring bank that processes the transaction routes the authorization request to
the
card-issuing bank. This routing is done through the networks like
VISANET/BANKNET. The
credit card number identifies type of card, issuing bank, and the cardholder's account. If
the
cardholder has enough credit in their account to cover the sale, the issuing bank
authorizes the
transaction and generates an authorization code. This code is sent back to the acquiring
bank.

25. When a credit plan segment is created for a particular account?

When a sale (transaction) is posted to an account with a plan number, credit plan
segment is created for that account.
Plan number refers to a Credit Plan Master, a template that specifies processing
options.

Deep questions:

1. What is after hours processing?

At the end of each normal processing day, you must close the CMS master files for batch
processing and open the after-hours files by using the ARCH (Close for After Hours)
function or by selecting the OPEN FOR AFTER HOURS option on the AROC (After
Hours) screen. If you are using FAS, opening the after-hours files also initiates the FAS
transaction OFED (option 1 on OFSS). OFED sets the end-of-day switch and prepares the
files for after-hours processing. At this time, CMS uses “shadow” files to post
nonmonetary transactions. (“Shadow” files are duplicate files designated by an A at the
end of the usual master file name.) The system generates these files dynamically as it
processes account transactions. For any inquiry transaction, the appropriate CMS master
is accessed in a read-only fashion. If an update is required, the account record is written
to the shadow file.
Using the shadow files, customer service personnel have the online capability to update
account information while in after-hours mode. FAS also points to the shadow files to
make authorization decisions. For example, if you place a block on the account at 7:00
P.M. during after-hours, and an authorization request is attempted on the account at 7:01
P.M., FAS reads the shadow files, finds the account with the block code on it, and
responds
accordingly. If FAS does not find the account in the shadow files, it reads the read-only
master files. These files are available while CMS batch programs Daily 1 and 2 are run.
When after-hours activity ends, and CMS batch program Daily 3 is about to run, you
must
close the CMS files either by using the ARCA (Close All) function or by selecting the
CLOSE ALL option from the AROC (After Hours) screen. If you are using FAS, closing
the
files initiates the FAS transaction OFAH (option 2 on OFSS) which puts the files in
afterhours
mode.
CMS batch processing moves the after-hours log records from the shadow files to the
AML1 master files and renames the files. During this period, no FAS or CMS processing
can take place. Once the batch is completed, if you are using FAS, you must run the FAS
Daily 2 program to reinitialize the FAS log files and reopen the FAS files for processing.
After you complete this process, you can reopen the CMS files either by using the AROA
(Open All) function or by selecting the OPEN ALL option on the AROC screen. Either
action prompts the system to apply the AML1 files to the master files and return the
master files to ready-for-processing status.
Limitations
You cannot maintain the control records, credit plans, and delinquency adjustments in the
after-hours mode.

2. Which are maintain transactions that can be performed during after hours and
why?

Answer: ARMB, ARME, ARMN, ARME (As The files AMBS AMED AMNA AMRM
have their entries to in AROEXTI incase any changes are done during after hours)

3. How can we assign temporary credit limit to an account?

Answer: It can be done on ARMB 06 screen.

4. What is a Logic Module, what is the significance of the same in Batch Processing,
and in Vision Plus where it is defined?

Answer: CMS does not furnish a set of predefined transaction codes for your institution
to when entering monetary transactions. Instead, CMS includes logic modules that
Provide the effect of monetary transactions. The logic modules contain the programming
code that directs CMS to update account balance and plan balance information. Each
logic module performs a different action.
Logic modules allow you to develop a set of monetary transaction codes and determine
how each transaction code affects your accounts.

5. What is the Status Code for an Account, in which Screen you can see the same
and what are different status code for an Account?

Answer: Status codes represent the condition of an account and can affect the way an
account is processed. We can view the account’s status code on the Account Base
Segment screen (ARQB01) or on the Account Inquiry screen (ARIQ01).
When an account is first established, it is assigned a status code of N, to indicate that the
account was opened that day. The following day, CMS changes the account status to D,
indicating that the account is dormant unless the new account is accompanied by a
purchase transaction. The account remains in a dormant status until a purchase is posted
to a plan segment for the account.
The activity of the account’s plan segments control the status at the account level.
As long as the account maintains a balance and/or activity continues to occur on the
account, it remains in an active status until it is transferred (T), closed (C or 8),
inactivated (I) or charged off (X or Z –final charge off).

6. What is a Inactive account and how it will get treated in CMS?

Answer: Rather than process all accounts every day, CMS provides a feature that enables
you to move certain dormant accounts from the Account Base Segment file to an inactive
status file. There are a number of criteria that an account must meet before it is eligible to
move to the inactive file. The account must:
• Have a System Record (ARMS02) ACTIVE/INACTIVE field value of Y to
indicate that it can migrate
• Have an internal status of D to indicate the account is dormant, for the number of
months defined in the INACTIVE MONTHS field on ARML13
• Have a current balance of zero (the CURR BAL field on the Account Base
segment, shown on ARIQ01)
• Not be in collections (a DATE INTO COLL field value of zero on the Account
Base Segment, shown on ARIQ01)
• Have a collections COLL RS code of zero (meaning that the account is not in
collections) on the Account Base Segment (shown on ARIH01)
• Have no insurance
• Have no plan segments
• Have no outstanding authorizations
• Have a securitization POOL ID of zero on the Account Base Segment.
If an account passes the above criteria, the Posting (ARD140) program identifies it for
the Active/Inactive Account Processing (ARD250) program.
If the account is accessed online, CMS moves the account back to the active file, and
changes the status of the account from I to M (migrated).

7. What are the different sources through which CMS accepts incoming monetary
transactions?

Answer:
• Credit Management System (CMS)
• Account Services Management (ASM)
• TRAMS (ATTD file)
• User input.
Non-monetary input can be entered through CMS online, through ASM, or from user
input.

8. What is the Generated transactions in CMS? Give some examples of the same.

Answer: Generated transactions are automatically generated by CMS.

1. Fees and miscellaneous assessments Assess finance charges, late charges,
membership fees,
2. Charge-off adjustments Charge off fees
 3. Transfer generated Reallocate fees, charges for accounts transferred across
Logos
Internal fee adjustments Adjust fees or charges that have been assessed.

9. If we add new transaction codes using ARAX at Org level where do we need add
the same transaction codes? If not added there how will it affect the Batch?

Answer: We need to add the same transaction in AMGL file through ARAG for all the
Logos under the org. Else the file integrity program ARD000 will ABEND during the
batch.

10. What does posting debug flag on ARQS indicate and how does it work?

Answer: It indicates the CMS Posting program ARD140 is to be run in debug mode or
not. It actually gives the display of all the entry and exit of the paragraphs in the
SYSOUT.

11. How do we determine the interest table to be used for a particular transaction?

Answer: Once we find the correct PCT for an account on ARQF 01 screen we find
number RTOI with corresponding Interest Tables. To find which RTOI is to be used for a
particular transaction we have to see the screen ARQC (Credit plan segment) with plan
number of the transaction. Once we get the correct interest table we can go through the
details on ARQR screen.

12. What’s the difference between interest accrual methods for cash and retail
transaction?

Answer: For cash transactions interest is accrued right from the day of transaction even if
the amount is paid back before the due date. For retail transactions interest is charged
only on revolving amount.

13. When we need to add a new field in AMBS file what all programs do we need to
change?

Answer: If the new field added to the AMBS file is made editable on some screen say
ARMB 01 screen then following is the procedure that is to be followed.
a) Assign a field code to the field.
b) Change ARMB 01 map as well as AROMB 01 program.
c) ARFB map to handle the field security.
d) File Display program (ARU9**).
e) ARU040BS.
f) ARD040BS.
g) AR04PD (For the validations in AROEXTI).
h) AROEXTI.
Exam Data Dictionary program in case mass updating via online screen is to be accepted.
14. What is a balanced batch when it comes to monetary batch flow?

Answer: The transactions to CMS through TRAMS or ARMT screen are submitted in
terms of Batches (AMT1 format). A typical batch consists of a Header followed by
number of transactions.
A Batch is said to balanced when number of transaction following a header, Total
debit/credit amount of these transactions match with those mentioned in the Header.12) Deleted: ¶
¶
¶
15. Explain Monetary Batch flow in detail. ¶
¶
a) ARD010: Trams monetary input program, which produces the balancing
report.
b) ARD011: Takes the ATTI (AMT1 format) from ARD010 and sorts on Batch
number followed by sequence number as sequence number for headers is
zeros for a batch say batch number as 0001 output file ATTD will have
header at the top followed by the transactions for batch 0001.
c) ARU080: Monetary input pre-edit programs also called as User Monetary
Input program (takes input form ARD011 and passes accepted batches to
ARD080 as ATTI) which validates all the transaction those are coming from
TRAMS via CMSOUT file path in batches
• Checks for all the batches are complete and balanced. Rejects the
whole batch even if there is some error with one of the transactions.
• Transactions are scanned for proper plan number, store numbers,
transaction codes etc.
d) ARD080: Monetary transaction merge program, which performs similar
validations as ARU080 on the transaction coming, batch through online and
merge these transactions with those coming through TRAMS. Outputs are
ATEI (Rejected transaction) ATVT and ATNS (ATPT format).
e) ARD090: Takes the input from ARD080 as ATVT all payment transaction. It
primarily apportions the payment made under an account within its
relationship for all the subordinate accounts depending upon various factors
like Current balance of all the accounts, Cycle dues, Past dues etc.
f) ARD100: ATEV, ATEN created from ARD090 and ATNS from ARD080 are
merged so that one single ATPT is created by ARD100 and then fed to
Posting ARD140.
g) ARD140: It reads AMBS file sequentially for all the accounts and then
balances it with ATPT the output of ARD100. It posts all the today’s date
transactions, Creates ATSM on plan level for all the accounts getting
statemented today, Creates ATGT for generated transactions and also mark
the accounts in ATGT for the accounts, which are getting statemented. Apart
from the Report Tag file ATRF is created which is fed to ARD320 and the
ARD340 to print all CMS transaction related reports.
h) ARD180: Input to this program is AMDI, ATPT, ATGT and ABAI (GDG
with all the transactions of the account till yesterday). Outputs are ABAO,
AMOS, ATST (All the transactions of the account which got statemented
today).
ARD240: This program takes ATSM from ARD140 and ATST from ARD180 and builds
AMSS file so that statements can be seen online through ARSD transaction. Like AMOS
even AMSS is build daily.

16. Where the Payment application method and Payment hierarchy for billed-not-
paid components are defined and what is the significance of the same?
What is significance of payment apportionment rules?

Answer: At the logo level, you can select the method that CMS uses to apply payments
(APPLICATION METH on ARML12). You can use different methods for accounts-
receivable accounts (APPLICATION METH: A/R) and profit-and-loss accounts
(APPLICATION METH: P/ L). You can determine whether CMS applies payments to
each billed-not-paid component:
• Across all plans based on the plan priority and payment hierarchy
• By plan and payment hierarchy
• Across all billed-not-paid components based on payment hierarchy by plan
Priority, then to principal (prior and current) within each plan based on plan
priority.
For any method, you also define the sequence in which to apply payment to the
individual components, using the Payment Hierarchy controls.
We can even establish plan priority—the order in which CMS applies payments to
multiple credit plan segments on an account by using the Logo record payment
application fields on ARML14 or the Credit Plan Master record plan priority and control
option fields on ARMC06.

17. What are the different Billed not paid components, can we control the
application of payment to the different components?

Answer: The current balance of a credit plan consists of the following components:
1. Interest billed-not-paid (INT fields)
2. Service charges billed-not-paid (SVC fields)
3. Late charges billed-not-paid (LATE fields)
4. NSF (Non sufficient funds) fees billed-not-paid (NSF fields)
5. Over limit fees billed-not-paid (OVLM fields)
6. Insurance billed-not-paid (INS fields)
7. Collection expenses billed-not-paid (COLL fields)
8. Recovery expenses billed-not-paid (RCVY fields)
9. Membership fees billed-not-paid (MEMB fields)
10. User-defined fees 1 to 6 (FEE1 to FEE6)
11. Current month purchases (CURR fields)
12. Principal balance (PRIN fields).
We can control the application of payments to the components that make up the current
balance by typing a number from 01–17 for each component. You can define different
payment hierarchies for accounts-receivable accounts (A/R) and profit-and-loss accounts
(P/L). The component you designate as 01 is paid first, 02 second, and so on, until CMS
reaches 17 or the payment is depleted.
18. How can we control the individual fields the user can access when adding and
modifying records?

Answer: Field Security records that specify the type of input allowed in each field when
adding or modifying the Account Base Segment, Customer Name/Address, Embossing,
and Credit Plan Segment records. For example, a Field Security record can specify that
you must enter a particular field when adding a record and that you cannot edit that field
when modifying the record. Use the Field Security function (ARFS) to add, modify, and
view the Field Security records.

Establish Credit Plan Master records to define the various credit plans or methods that
you offer to your customers. The Credit Plan Master record contains the information
CMS needs to:
Define plan types
Process a request for credit authorization
Specify whether CMS consolidates credit plans when calculating payments for an
account that has multiple plans
Define the method and terms of repayment
Define special options you can provide your customers.

Use the Credit Plan Master functions to add (ARAC), modify (ARMC), and view
(ARQC) the Credit Plan Master records.

19. How do we find account control table or Service Fee table for a BANKCARD
account?

Answer: For all the accounts in the VISION Plus there are two active Processing Control
Table (PCT) Ids.
a) State of Residence
b) State of Issuance
The logo of the account decides whether the account is BANKCARD or not. For a
BANKCARD account we take the state of issuance as PCT ID.
After Find the PCT ID of an account we have to see ARQF screen to find the Account
Control Table or Service Fee table. The PCD ID active for the account is at Logo level or
Org level that can be seen on ARQL 13 screen.

There are separate screen for account control table ARQY , Insurance table ARQI ,
Service and Fee charge table ARVQ

20. If we want to issue the cards within a day’s run then how can it be achieved in
the batch?

Answer: The Card Embossing program ARU200 creates an ATUT file to update the
AMED and AMBS file. In some setups this ATUT is provided to ARU040 next day so
AMBS file for AMBS Issue flag and AMED file for Card action gets updated next day.
If ARU040 and ARD040 are run once again after ARU200 then these details get updated
immediately on the same day.

21. General ledger

CMS provides an interface to your general ledger system. All transactions, regardless of
their origination source, processed by CMS have general ledger records generated by the
Posting program. General ledger data is obtained from the Monetary Transaction Control
file where the respective transaction code was defined originally. CMS provides an
Activity Recap report that includes all general ledger activity for each organization and
the entire system.
To add a General Ledger record, type ARAG

22. Main programs in CMS?

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.

ARD140 Posting
ARD140 is a 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, and calculating
fees assessed by the system. This narrative describes the main program flow of ARD140.
Subsequent chapters describe each posting function.

23. What do we need to move to Sign on name in ATL1 or ATUT in case we are
creating an ATUT through our new program so that it goes through the validations
for sign on name?

Answer: We need to move ‘….’ (Four dots) to sign-on name.

 FAS Questions
1. Explain the authorization flow.

VisionPlus provides a module Financial Authorization System (FAS) to act as an

interface to external network like VISANET/BANKNET.
Once the customer's account is setup in CMS and a card is sent to the customer, the
customer is allowed to do transactions on his card.
Suppose he makes a purchase at a store the transaction hits VisionPlus in a module called
FAS.
Functions performed by FAS:
1. Check the validity of the card.
2. Check if the required amount is available in the customer's account to carry out this
transaction successfully.
3. If the customer has the amount available in his account, FAS approves the request
using CMS.
The balance amount in the customer's account number is present in CMS.
Please note that here the balance amount is not blocked on the customer's account
immediately.
This will not be done in online processing.

2. List the mostly used online screens in FAS.

OFCJ: Chronological journal

• Specify selection criteria FAS uses to chronologically display all authorization
activity for the current day
• Research an authorization issue on the same day instead of waiting for a batch
report.

OFDL: Authorization Detail

This function displays detailed information about transactions for a particular account
selected from the Credit Management System (CMS) Outstanding Authorizations file
(AMOA) or from the FAS log files.
You can access this function only through OFAL (Card Activity
Display Log), OFCJ (Chronological Journal), or OFML (Merchant
Activity Display Log). As a result, this function is not listed on
OFMU.

OFRQ: Authorization Request (used for manual authorizations).

Use the Authorization Request screens to perform the following actions:
• Request authorization
• Request address verification
• Force an authorization request
• Request information
 • Perform a credit adjustment
• Verify a check.

OFRS : Authorization response.

Use the Authorization Response screens to view information about a specific
authorization request.

OFAA: Card Activity.

OFAL: Card Activity.
Use the Card Activity screen (OFAA) and Card Activity Display Log screen (OFAL) to
display account activity. Using either function, you can:
• Examine all cards currently carried on the Card Activity file
• Request a specific transaction for which you want to display detailed information.
Use OFAA to process a reversal. Use OFAL to list all customer authorization activity
today (approvals and declines) and all accounts on the CMS Outstanding Authorizations
file (AMOA). OFAL highlights and displays accounts that are on the AMOA file first.
The center’s processing status must be in normal mode to use the OFAA or OFAL
functions. (End-of-day and after-hours modes do not allow display of card activity.)
All OFAA/OFAL fields are system-generated and cannot be modified unless the data
field is surrounded by parentheses ( ), indicating that the field is open for input.

OFSA: Card blocking and addition into special handling file.

OFSA enables you to add, change, delete, or make inquiries about special handling
accounts. Once you enter data on the first screen for a bankcard account, OFSA generates
the necessary transactions to forward the information to the Visa Exception file or the
MasterCard Authorization/AMS files. This information becomes part of stand-in
processing (STIP) when the member host is not signed on or is unavailable to the
network.

OFSS: Visa/Master Card SignOn / SignOff.

Use the System Status Menu screens to:
• Perform host functions that control the authorization system’s processing mode
• Establish communication between the institution and the Visa, MasterCard, and
Europay networks
• Set the operational modes of the networks.

3. What is the name of FAS log file? What is the significance of mirror files?

FMLA/FMLB.
FMLC is mirror file for FMLA
FMLD is mirror file for FMLB

These files (Log files A, B, C, and D) contain a complete audit trail of all transactions,
responses, and messages that flow through the online system. Only one of the log files (A
or B) is active (online) at any one time. The FAS System/Organization/Control file
determines which log file is currently in use. All log files are written during end-of-day
processing, and if 24x7 is installed the log files are also written to during after-hours.
Log File C is a duplicate of the Log File A, if it is active. Log File D is a duplicate of Log
File B, if it is active.

4. What is the outstanding authorization file in CMS (AMOA)? Which job

creates this file? What is its significance?

OFEOD creates this file.

CMS accepts bankcard authorizations and keeps them as outstanding authorizations in

AMOA file until
• The user-defined expiration date
• In the case of Visa auto rental or hotel transactions, until the industry-standard
duration specified on the transaction itself has expired
• A match comes along for an actual transaction.

5. What are special handling accounts? What is STIP?

Special handling accounts are those accounts, which are lost or stolen card accounts
or VIP accounts added to the special account-handling file.

As accounts are added to the Special Account Handling file, they are blocked and
flagged on the Account Base Segment file (AMBS) and simultaneously sent to the Visa
exception file or the MasterCard Authorization/AMS file.

This information becomes part of the STIP when the member host is not signed on or
is unavailable. This will restrict the user to do any further transactions.

FMSH is special account handling file.

6. What are different types of Authorizations?

On-us authorizations
Voice authorizations
Forced authorizations
Delayed advice authorizations

7. Explain the term ‘Velocity Parameters’?

Velocity parameters are the processing parameters, which determine credit decisions
and operating characteristics. These parameters can reside at the system, org or logo
level.
Ex:
Invalid Pin: Code that indicates the action FAS should take for cash authorizations on
accounts when an authorization fails PIN validation.

Exceed Number of PIN tries: Code that indicates the action FAS should take for cards
that have exceeded that allowable number of PIN attempts (as defined in ALLOWABLE
NBR OF PIN TRIES)

Invalid CVV/CVC: Code that indicates the action FAS should take when an
authorization fails card validation. CVV is for Visa while CVC is for MasterCard.

8. How Authorization reversal works?

With any reversal, the original authorization must be located to determine exactly what
needs to be reversed. For an authorization reversal, FAS determines if the record is on the
AMOA file or the Log file (FMLA/B) to find the matching original authorization. When
FAS finds a match, it writes out an authorization reversal (Action Reason = 97) to the
Log (FMLA/B) file for the original authorization. The authorization reversal causes FAS
to update the open-to-buy on the account, increasing it by the amount of the authorization
reversal.

9. Where Base1 & Base2 message formats are used in Bankcards.

Q.1.) What is EOD tag and after-hours tag? Which transaction sets this flag and in
which file?
Ans.) EOD tag is the End of Day tag. The EOD tag is added to the authorizations file at
the end of the day. The EOD record may be viewed by using the OFCJ screen and
specifying the Rec. Type as E. During EOD processing, FAS processing can continue but
authorizations will be posted to the shadow files. A system status of 1 indicates EOD
processing. 1 indicates that the online processing of FAS is suspended because of EOD
cutoff processing. 1 will not be visible on screen though. EOD processing can be initiated
using the ARCH screen of CMS.
After-hours processing can be initiated using the ARCA screen in CMS. In After-
hours processing, no FAS processing is allowed due to after hours transaction updates.
This is represented by a system status of 2 in OFCJ. ARCA is used to shut down the FAS
online functions and close authorization files. Performed when CMS batch daily
processing is complete.

Q.2.) What is the purpose of FAS log files? Why do we maintain 2 log files?
Ans.) We maintain 2 log files in FAS. They are FLMA and FLMB. The log files are used
for storing all the auth requests received by FAS during 1 day for which no settlement file
has been received yet. The settlement file contains the auth for the whole day from the
POS of the merchants and from VISANET and MASTERNET. These settlement files are
then compared against the log files and transactions are posted onto the customer
accounts in FAS. The log files contain authorization requests, auth reversal requests,
account information requests, etc.
During the night, certain batches have to run (for e.g. one batch has to run which
compare the settlement files against the log file that was maintained since morning).
Now, when this batch is running, the log file is not available for accepting auths at that
time. So, we maintain 2 log files. When one is being used for the batch processing the
other is available for accepting the auth requests from the online functions of FAS.

Q.3.) What are the different checks carried out during the processing of an
authorization request?
Ans.) The different checks that are carried out during the authorization are
• CVV
• Card Expiry date
• PIN(in case of ATM transaction)
• Merchant code
• Open-to-buy (OTB) limit
In case a referral is needed at the time of authorization (this can be specified in the
system), at the time of authorization, the merchant has to call an operator and tell
him/her the customers CVV2 number. The operator enters this into his online
screens. If there is a match, the system return a value of 2 otherwise it gives 1.

Q.4.) Describe how warning code-1 affects auths?

Ans.) Warning Code 1: (Block Code Interpretation)
0 = No action
1 = Block Code 1 or 2 set for decline
2 = Block Code 1 or 2 set for decline and pick-up
3 = Block Code 1 or 2 set for fraud code
4 = Block Code 1 or 2 set for referral
8 = User-defined algorithm
9 = Block Code 1 or 2 set for VIP (approve regardless).
Thus, if the warning code-1 is set to 9, block code 1 or 2 will be set for VIP and if
an auth comes on this account, it will be approved regardless.

Q.5.) Where do you set the verification flags of CVV and PIN?
Ans.) To set the verification flags of CVV and PIN we have to use the OFAP screen. This
screen lets us set the flag that tells the system to verify either the CVV or the PIN
whenever an auth hits the system. We can view the status of these flags for a predefined
logo using OFQP screens.

Q.6.) What is special handling file? Mention its use and how is it maintained?
Ans.) Sometimes some accounts need to be handled in a different manner. For example,
accounts for which VIP cards have been issued need to be handled differently. They must
be given accepted auth regardless of any pending queries in their accounts. We then need
to have some special parameters that will treat auths from these kinds of cards differently.
These parameters are defined in a special handling file. In the file we mention all such
special cards and the parameters for processing them are also set up here. The special
handling file may be maintained by using the online screen OFSA. The special handling
parameters can be viewed in the OFDS online screen. The special handling file in FAS is
called FMSH file.
Note: These files have to be synchronously maintained with VISANET and
MASTERNET too. These files will come in use when the system operates in STIP mode.
Special Account Handling file (FMSH)
This file stores information about customer accounts that require special handling for
authorization processing. Accounts that require a decline or pickup response and accounts
with VIP information are stored on this file.
Accounts are added to this file for the following reasons:
§ Lost card
§ Stolen card
§ Fraud
§ Counterfeit
§ Credit risk
§ Unauthorized use
§ Card pickup required
§ VIP customer
§ Gold card.
As accounts are added to the Special Account Handling file, they are blocked and flagged
on the Account Base Segment file (AMBS) and simultaneously sent to the Visa
Exception file or the MasterCard Authorization/AMS file.

VIP accounts remain in special handling as long as the account remains active or until the
account is removed from VIP status.

Q.7.) What is the reversal of an auth? How is a reversal done?

Ans.) Sometimes a customer may buy a product and after some time decide that he
doesn’t want that product. So he returns the product to the merchant. But he had already
paid for it by credit card i.e. an auth had already hit FAS and had been approved. So the
merchant now sends an auth reversal request to FAS. During a reversal FAS checks to
find the original auth. If it is not found then there is no question of a reversal and thus
FAS sends an appropriate error message back to the originator. If the original auth
existed, FAS sets a reversal indicator flag next to the original auth to specify that this
auth has been reversed. Next it increases the OTB of the customer by the amount of the
reversal. It also decreases the count and amount of the total auths done today. Similarly it
decreases the amount and number of memo debits by 1. Finally, acknowledgement of the
reversal is sent back to the originator.
There can come a case when the customer has bought 4 items and wants to return
only 1. This case is called as a partial auth reversal. In this case, FAS completely reverses
the original auth and makes a new auth for the balance amount.
Q.8.) Describe the different parameters in the following screens: OFAA, OFMP,
OFRD, OFCJ, OFDL, and OFRS.
Ans.) OFAA
The Card Activity/Card Activity Display Log (OFAA/OFAL) screens are used to
display customer card transaction activity. You can:
1. Examine all cards currently carried on the Card Activity file Request a specific
transaction for which you want to display detailed information.
2. The center’s processing status must be in normal mode to use this function.
(End-of-day and after-hours modes do not allow display of card activity.)

OFMP
The Processing Parameters screens are used to add (OFAP), maintain (OFMP), view
(OFQP), or delete (OFDP) parameters that determine credit decisions and operating
characteristics. These parameters reside at the system, organization, or logo level.

OFRD
The authorization Reason Codes/Descriptions (OFRD) screens are used to:
1. Change reason code descriptions
2. Define the sub panels to be displayed by reason codes on the Authorization Response
(OFRS and OFRF) screen.

OFCJ
The Chronological Journal (OFCJ) screens are used to:
1. Specify the selection criteria FAS uses to display all authorization activity
chronologically for the current day
2. Research an authorization issue on the same day instead of waiting for a batch report.

The information that displays on the detail screen is the same as that provided
by the Chronological Journal report. The center’s processing status must be in
normal mode to use this function. End-of-day and after-hours modes do not
allow the display of account activity.

OFDL
The Display Authorization Log Record (OFDL) screens are used to display information
that may be needed to analyze and resolve an existing problem for a selected transaction.
This function displays detailed information about transactions for a particular account
selected from the Credit Management System (CMS) Outstanding Authorizations
(AMOA) file or from the FAS log files.
You can access this function only through OFAL (Card Activity Display Log), OFCJ
(Chronological Journal), or OFML (Merchant Activity Display Log). As a result, this
function is not listed on OFMU. Using OFAL, OFCJ, or OFML, select the account for
which you want to view detailed information about a transaction. When you press Enter,
the OFDL screen displays.
 OFRS
The Authorization Response screens are used to view information about a specific
authorization request.

Q.9.) Explain all the warning codes and their purposes.

Ans.) There are basically 7 warning codes. The 1st one is WARN-1=8. The 2nd one is
DELQ LVL 1. Now this defines the delinquency level, as does DELQ LVL 2. These
define the various delinquency levels and the system can take action based on what is
specified if these warning codes are received. There can be 3 possible outcomes to the
situations in which warning codes are received. They are shown as A, B, and C in the
OFMP screens. The system takes action depending on which one of these is active at that
time. The warning codes 4 and 5 are user defined.

Q.10.) What is the purpose of OFSS screen?

Ans.) OFSS screen is the system status menu screen. The System Status Menu screen is
used to:
1. Perform host functions that control the authorization system’s processing mode
2. Establish communication between the institution and the Visa and MasterCard
networks
3. Set the operational modes of the networks.

Q.11.) What is STIP?

Ans.) Stand-in Processing (STIP):

In Visa’s BASE I, the function operating at all VICs that provides authorization decisions
on behalf of BASE I issuers. It acts for transactions in amounts under the issuer limit,
when the issuer is unavailable or when a request sent to the issuer center times out.
Stand-in service is based on the issuer’s parameters, customer information maintained by
the issuers, and activity maintained by BASE I STIP in the activity file. STIP generates
advice records for authorization requests it processes when applicable.
Log a record at Visa or MasterCard for each authorization decision made by STIP. FAS
can retrieve these records (called Delayed Advices) at the request of the issuing center.
As the Delayed Advices are retrieved, they automatically update the Account Base
Segment and are logged to the FAS log file.
For Visa, if a response is not received from an U.S. issuer within nine seconds, send an
Assured Transaction Response (ATR). For ATR responses, the Visa Delayed Advice is
matched with the response generated by FAS, (which was not returned to the acquirer)
and the FAS response is negated.

Q.12.) What is END OF DAY, AFTER HOURS MODE

Q13 ) What is FAS system control parameter file (FMSC)

System/Organization/Control file (FMSC)
This file contains the system, organization, and logo processing parameters.

Q14) What is the screen for maintaining FAS SYSTEM parameters

Answer : (OFMP)

Q 15) What is triad and basic functionality?

Q 16) Can we maintain the warning code through screens permanently?

Q 17) What are the warning codes not currently used in the vision plus? Can we use
them (user defined warning codes)?

Q18) Can we take manual authorizations for off-us cards?

Answer: Y

Q19) Can we rout the VISA transactions through MasterCard Network and vice-
versa and How?

Answer: Y

Q 20) What is ISO 8583 Message?

Q 21) What is message type indicator? Explain.

Q 22) What is Parsing and Formatting of the ISO-Message?

Q 23) What is VIP Block code? What are the benefits to the cardholder?

Q 24) What are advices? What are unprocessed advices?

Q 25) What is Delinquency? How the block code is assigned in batch run?

Q26) What is the difference between CVV and CVC and What is the difference
between CVV2 and CVC2?

Q26) What is CVV and CVV2? Explain the parameters used in the verification of
the same. How the CVV2 value is calculated?

Card VerificationValue (CVV)/ Card Validation Code(CVC)

Three-digit value (Visa only) calculated from the data encoded in the stripe using a
secure cryptographic process and the issuer’s secret DES keys. This value is verified in a
security module by the issuer or its agent and is used to detect alteration of the data
encoded on the stripe of counterfeit cards.
Card VerificationValue 2 (CVV2)/ Card Validation Code 2 (CVC2)

Three-digit value printed on the signature panel of the card (Visa only). This value is
used to validate a card and reduce the potential for fraud loss when the magnetic stripe
(including the original CVV information) cannot be read. The CVV2 is calculated using
the cardholder account number, the card expiration date, and an encryption key supplied
by the issuer.

Q 27) What is TRACK DATA? What is the content of it? Do you receive Track data
in Internet transactions?
Answer: We don’t receive track data in Internet transactions.

Q28) How the FAS log files are switched?

Q29) What are the different reports generated in FAS?

Q 30) What is the difference between the FAS log files (e.g FMLA) and other VSAM
files?
Ans : Fas log files are ESDS and other VSAM files are KSDS.

Q 31) During reversal transaction how do we find out the original transaction?

Q 32) List the various CMS files used by FAS during Authorization?
FAS uses the following CMS files and records:
v AMBS—Base Segment file
v AMSD—Store Demographics file (or MMMMRL—MBS Merchant Master file if
MBS is active)
v AMED—Embosser record
v AMNA—Name and Address file
v AMCP—Credit Plan Master file
v AMCR—System Control file.
These online files must be opened to CICS in order to sign onto the Visa, MasterCard.

Q 33) What is a Shadow file in Vision Plus and Where and How it is been used?
Answer:
In After Hours Mode in Batch Processing
CMS shadow files (for example AMBSS).

Q 34) What is a the Relative Byte Address (RBA) and Where this concept is used in
Vision Plus?
Account Activity file (FMAA) or (FMAB)
This file enables the system to access authorization requests by account. The key to the
file corresponds to the Credit Management System (CMS) Account Base Segment file
(organization and account number). Each record on this file contains the relative byte
address (RBA) of an Activity record on Log file A or B and C or D (if log C/D is used).
These account pointers eliminate the need to store redundant activity data. Since this
information is stored by account, it can be used to respond to repeat inquiry requests
received from Visa without requalifying the inquiry.

After (AROA), Resume Normal Processing, is entered after the CMS renaming-files job
has completed updating with after-hours transactions and reopened to CICS.
FAS then write an F record, marking the end of after-hours. The Relative Byte Address
(RBA) of this record is then updated on the system core area and the System Control File
record. The end-of-day tag RBA is set to zeros on the System record, the current log file
indicator is switched, and the system status is set to zero.

Q 35) What is BASE I / Banknet and BASE II in FAS ?

BASE I VisaNet data processing systems, networks, and operations used to support and
deliver authorization services, exception file services, PIN verification, and various other
authorization related services.

BASE II VisaNet data processing systems, networks, and operations used to support and
deliver the clearing and settlement services and other services related to the interchange
of paper.
SSC Questions
1. What are two main parts of SSC module?
Online Security Subsystem and common files and routines.

2. Define security supervisor and alternate security supervisor

Security supervisor controls access to all of the applications while alternate
supervisor cannot exceed or authorize access beyond their own parameters.

3. How many levels of security can be setup for V+ component

There are 17 levels of security.

4. Which screen is used to set up user level security?

SSSR

5. What are date routines for Greg to Jul and Jul to Greg conversion?
SS07PD-Greg to Jul
SS08PD-Jul to Greg
6. Differentiate SMSF and SMPT files.
In Vision Plus (version greater than or equal to 8), SMSF contains all user
information while SMPT is having all txn names and corresponding map and PGM
names.

7. Is it required always to sign on and sign off through SSC?

If company uses RACF, that eliminates the need to sign on through SSC.
 ASM Questions

1) Which program reports the Field maintenance in ASM like ARD040 does in
CMS?

Answer: ASD040

2) What decides the action to be performed on a particular account on ASMW

screen?

Answer: On ASMW 01 screen Action Code is a required field. This action code decides
what action is to be taken on the account. Like monetary action, Non-monetary action
(Address change) etc. Depending upon the action code ASMW 01 screen transfers
control to the next screens 2 or 3 or 4 or 5.

3) How do we find the action we were trying to perform on the account got rejected
or accepted or still in the queue?

Answer: Whatever is the action performed on the account AMHS file is update for that.
Status C (closed) tells that action is been performed. Status D is denied. Status R is for
referred and tells that because of operator limits the action in the queue of higher
authority operator. This status can be seen on ASHI.

4) How do we see the operator queue?

Answer: ASSQ screen, from there we can pickup the number of the account which needs
to be worked upon and the control transfers to the respective ASMW screen.

5) How do we define an action code in ASM?

Answer: Using ASAA screen we can add an action code and using ASMA we can
maintain the same accordingly.

6) Like we use LTOPGM1 for LTS and ITOPGM1 for ITS as program tables in
8.10 version of V+ what is used as program table for ASM?

Answer: AROPGM1.

7) What is the output of ASD080 User Monetary Transaction Program?

Answer: ASD080 begins by setting up its print headers and opening the files. It reads the
Monetary Transactions (AMTX) file sequentially, accumulates totals, and writes a record
to the User Monetary Batch (AMMX) file. When there is a change in the organization or
representative ID, the program writes a batch header to the AMMX file. Thus output of
ASD080 is then passed to ARU080 in CMS.
8) How can we check the ASM status of a representative?
Answer: After SSSN with that representative’s ID, ASRS is the transaction to be used.

9) If an account is transferred and we need to see the statement of the old account
how can it be achieve?

Answer: ASSD is the screen, which allows you to see statements of the old as well as
new account. As through this screen we can navigate in ARSD screen.

10) Which program creates LTDT file in ASM?

Answer: ASD010 is program that actually writes LTDT, It is called by ASU010 where
AMDS is read for letter requests. AMDS is updates daily online for letter requests
whenever ASMW (account work screen) performs some action on the account.

11) ARD140 writes the memos (like letter are sent) in ATGH file. How are they
incorporated into ASM so that they can be seen on ASHI?

Answer: Driver file for ASHI screen is AMHS. So it is required that ATGH contains
should get copied to AMHS file. It is done in ASM daily batch. The program ASD110
reads ATGH file and updates AMHS file with information necessary to record the fact
the letter was sent for a particular action and account.

12) How do we know which action codes are monetary?

Answer: For action codes, which are monetary TYPE, equals M.

13) How can we find out whether a letter was generated for an account (Asked by
ASM or CMS)?

Answer: ASD110 always updates AMHS for all the letters those are generated by reading
ATGH and LTLP (Letter Tag File). So if the letter is generated for an account (as asked
by CMS or ASM) then it can be seen on ASHI screen after a batch run.

14) ASSD 02 screen has only one maintainable field ACTION C/P what does it
indicate?

Answer: Action C/P tells whether to reprint statement with Current address or Prior
address when this statement was generated. To use P the prerequisite is the PRIOR
ADDRESS field on ARMO should be set to Y.

15. In ASM which program is responsible for processing and reorganizing Master
files.
Answer:ASD140 Master Files Processing
This program processes and reorganizes all ASM master files. ASD140 reads all files
and writes them to a corresponding master file if they are not marked to be purged.
ASD140 generates a history purge archive file and passes the file to ASD180.
ASD140 deletes the old master files and renames the new files to the current master
files.

16) How the History purging of the ASM master file will happen and what is the
name of the program, who does that?
ASD180 History Purge/History Purge/Archive Merge
This program merges the History Purge file generated by program ASD140 with the
History Purge Archive file by writing a new History Purge Archive file. The History
Purge Archive files use the GDG concept

17) What is a Action Code in ASM and what is the use of it and what are the
possible action codes types?
There are six types of action codes in ASM:
Ø Monetary
Ø Non-monetary
Ø Transcript
Ø Inquiry
Ø Point
Ø System-generated.
 CDM MODULE:

2. What is the difference between a normal application processing and a

Recaptured application processing?

In the Normal application processing the relationship number will get generated
after application processing while in Recaptured Application the Relationship
Number will remain same and the flow in the APOVPAO and AROEXTI to
generate a New Account number will be different then the Normal Application.

3. In which CDM Screen after pressing PF7/PF8 keys the application is

declined or approved?
APWL

4. What is the use of the transactions APL1, APL2, APL3 and APL4?
As most of the CDM processing happens online the different files attributes are
loaded into the DSECT tables so the application processing will be faster.
To load the different tables
APL1 Load the Classification Assignment Criteria DSECT
APL2 Load the Credit Limit Assignment Criteria DSECT
APL3 Load the Type Statistics DSECT
APL4 Load the Operator Statistics DSECT

5. What is the online program name for APWL Screen and how can we find the
program corresponding to a particular online Screen?

Screen Name for APWL: APOWP01

APPGM1 Online Program Table Control Cards

6. What is the Program which is responsible for account number generation in

CDM?
In order to generate an account number, CDM program APOPS (Account Setup)
links to APOVPAO which builds a COMMAREA record to request a CMS
account number (Base Segment, Customer, Embosser, Relationship, or
Secured/Collateral). CDM passes a CMS organization, logo, and flag to identify
the type of account number being requested and then calls to the CMS program
AROEXTI. The requested account numbers are generated in CMS and then
passed back to CDM.

7. What is cradle-to-grave processing? How we activate the same for a

particular type?
 If your operation processes instant credit applications, the applicant is typically
waiting for a quick response. The ability to work an application from beginning to
end, or cradle to- grave, provides you, or the operator who inputs the application,
immediate access to the work queue if an application has a queue status. If the
application reaches a final decision, you are transferred to the Application Status
Summary (APIS) to be notified of approval or decline. From APIS, you can return
to the Application Input screen (APIA) to continue entering applications, or you
can return to the Process Work queue (APWP) to continue working queued
applications.

To activate the Cradle to Grave Processing Make sure that your operator record
(APXM01) CRADLETO-GRAVE ALLOWED indicator is Y, and the Type
record (APTM02) PROCESS CRADLE-TO-GRAVE indicator is Y.

8. What is a Type control record?

Type control records define how CDM processes each credit application assigned to
that type. You can limit the classifications of accounts within a type, as well as
specify the number of associations that are processed in the type. You can also
specify, by type, the letters that are automatically sent to applicants for approvals,
declines, or missing information

9. What are the different steps in CDM that an application has to complete
before it can be approved?

In CDM, we can identify by type, the required processing steps and the sequence
that the steps are to follow.
Application edit
The Application Edit process is performed on any application that is input to CDM. If
data errors are detected in an application, CDM places the application in the
Application Edit Process Queue (APEP) to hold it for operator action. This process
step is set by CDM as the first processing step for all applications, although you can
prevent CDM from performing this step for co-applicants and guarantors.
Pre-validation
The pre-validation process examines the application policy issues that could decline
the application before the bureau reporting process begins. Using the Policy tables,
CDM checks each application to determine whether it meets the minimum
requirements for credit. You can control the associations (applicant, co-applicant,
and/or guarantor) against which these Policy tables are applied, as well as whether the
application is automatically declined if the Policy table fails.
Cross-checks
You can define which of the cross-checks (system and/or user-defined) are executed,
and for which of the associations each cross-check is performed. These cross-checks
compare specific data in the application fields to established cross-check tables
containing valid entries. Applications that fail these checks are flagged as declined or
are queued for operator attention. You can also identify a letter to send in the event
the application fails any of the crosschecks and identify a decline reason code for
each crosscheck.
Application scoring
CDM scores an application by interrogating fields on the application and calculating
accumulated points for those fields. The point values for selected fields are defined on
Score Table control records. Applications that score below a user-defined value are
either placed in a queue for operator action or are declined automatically by CDM,
depending on the controls you select on the Type record.
Data verification
By type, you can indicate the application fields that are verified if the application data
matches the specific criteria data range defined here. For each field you list, you can
indicate the association for which verification is performed, and determine whether a
letter is automatically generated or whether the application is queued. For
applications that are declined in this step, you can designate a letter to generate.
Credit bureau scoring
The parameters used to request credit bureau reports for an application are also
defined at the type level. Once a credit bureau report is received, CDM uses a
common, formatted record to interrogate and score fields on the credit report. Fields
that are scored, and the points associated with those fields, are defined on the Score
Table control records. For each Score table, you can indicate which of the
associations the table is to be executed for.
If the credit bureau score falls below a defined value, the application is either placed
in a queue for operator action or is declined automatically by CDM.
Combined scoring
You can define CDM action to be performed based on the total application score the
application has after the scoring steps. By type, you can define the score cutoff ranges
for Application Scoring, Credit Bureau Scoring, and/or Combined Scoring, and
indicate whether the application is automatically continued, queued, or automatically
declined, based on their score ranges.

Letters are designated for applications that are declined for application scoring
reasons only or for bureau or combined scoring reasons. If an application is declined
in the combined scoring step for application reasons, you can send a separate decline
letter that does not reflect the bureau name and address.
External scoring
You can add an external scoring option. The CDM/ScoreWare Interface allows the
capture of external scoring information through ScoreWare.

Final Judgement
Up to 50 Policy tables are identified for each type executed during the Final
Judgement process step. In addition, you can define the post-bureau, final judgement
criteria applied to applications in the final judgement step. This is typically set up as a
debt-to-income ratio calculation. The final judgement step is defined as the next-to-
last processing step for all applications.

Delayed setup for secured accounts

If you are processing secured accounts, you can set CDM to automatically delay the
final setup of such accounts to allow time for the securing check/funds to be
collected. To use this feature, you assign a field code to designate the account as a
secured account, indicate the credit classification you have designated for pending
delayed setup accounts, and define the number of days the application is held in the
delayed setup pending class prior to being automatically released to the Application
Setup processing step.

10. What are the different methods through which application can be entered
into the System?
Credit applications are input to CDM by three methods:
• Entering the data manually into the Application Input screens (APIA) following
the format defined in your Application Definition records (APYM)
• Loading the data from an external file, such as a solicitation file
• Loading the data via user input (usually on tape).
Having the capability to load data from an external file in a defined format enables
you to enter pre-approved solicitations into CDM.

11. How an Application is identified in the CDM system and what is the logic
behind it ?
Application identifiers

The identifier for an application is assigned by CDM. This number is based on the
date the application is first entered. The application identifier format is as shown here:
YYYYJJJHHMMSS (Year, Julian Date, Hour, Minutes, Seconds )
The application is subsequently queued in numerical order based on its identifier.
Applications forwarded to the Application Edit Process queue (APEP) to be
completed at a later time are assigned a reconsider date so the applications are queued
in the order of the reconsider date, rather than the date in the application identifier.

12. How a VIP Application is approved and for a particular type by a operator?
What are the prerequisite for the same?

Enter a vip application Make sure that your Operator record (APXM01) VIP
ALLOWED indicator is Y, and the options on the Type record (APTM02) are
defined for FORCE VIP APPROVE.

13. What are the different important Screens in the Application Processing in
CDM?
ü To enter an application, type APIA
ü To view an application, type APIQ
ü To modify an application, type APIM.
ü The Process Work Queue (APWP), if the application has a queue Status
ü The Edit Queue, if there is missing data
ü The Verification Queue if there is data verified (APVP)
ü The Application Status screen for logged errors (APIS)
ü The Vector Add screen, if you are using credit bureau report Simulation
ü The Set Up Queue (APWL), if the application is automatically approved, if in
manual setup mode.
ü The Application Status Summary screen (APIS) displays to notify you of
approval or decline.
When you have completed the application entry, a message displays that states
PROCESSING CRADLE-TO-GRAVE - AWAITING NEXT RESPONSE.

14. What is a Secured Card Application in CDM and How the setup for the same
can happen in CDM?
CDM provides the controls you need to process secured card applications
differently than your other credit applications. For these applications, CDM provides
the following parameters that you establish on the Type record (APTM):
• Identify specific field codes to designate that an application is for a
secured account
• Define the amount of time CDM delays account setup to allow bank
clearing of a check received as security for the account
• Define a Delayed Setup Pending Classification ID where the application is
held during the delay period
• Define the credit limit for a secured account based on a percentage of the
secured amount.

15. What is Selldown Processing in CDM?

We may have applicants who do not qualify for the credit type that was originally
applied for. You can use selldown processing to offer alternative products to these
applicants who have been declined for a particular type of credit. For example, you
could offer a Standard or Premier card (possibly with lower credit limits) to a
customer who did not qualify for your Gold card.

You can assign a severity level to decline reasons, which enables CDM to determine
when a selldown offer should not be made. If the customer does not qualify for the
selldown, the application is declined. For example, if an applicant’s credit bureau
report indicates that the applicant has been bankrupt, you may not want to offer
selldown.

When an application is approved as the result of a selldown, a letter generates stating

the decline reason for the original credit request, and an offer of credit is extended to
the customer in the approved type.

Tracking selldown processing

You can use the selldown Queue Summary screens (APBS) to display a list of
applications currently in a selldown state. From APBS, you can select an application
from the list, and display the Selldown Process Queue screen (APBP) to review the
selldown record for the application.
The Selldown Process Queue screen displays name and address details on the
applicant and co-applicant, and contains detailed information on the selldown status
of the application. A complete history, including previous selldown types and credit
amounts offered, letters sent, and details on original requests for credit, displays.

16. How can we locate a application by specifying the name and optional data of
an applicant?
We can use the Name Locate screens (APNL) to search your CDM Name Key file for
a matching name. In addition to the name, CDM displays the Organization number,
Type number, and Application number.

When we found the matching name, we can enter the screen code of the next
function, we want to perform into the NEXT TRANS field, and CDM transfers
directly to that transaction. CDM assumes that you are searching for a name prior to
checking the application status, and therefore, defaults to the Application Status
Summary screen (APIS) unless you enter a different screen code.

17. What is a logged error? How we can get the information for the same?
If an error occurs during the execution of a process step in CDM, the application is
halted from further processing. When the error occurs, details of the error are logged
and are viewed on the Logged Error Inquiry screens (APLE). A message displays on
the Application Status Summary screen (APIS) to notify you that an error exists.
Using APLE, you can display a list of the applications that have been stopped in
processing. For each application, the processing step in which the error occurred
displays.

18. How can we restart the application that is having Logged Errors after
resolving the error?
Once you have recovered the problem, you can restart the processing of the
application using the PF6 key on the Logged Error Inquiry screen (APLE02). CDM
will not allow you to restart the application by going directly to APIR; you must press
PF6 on APLE02 to go to APIR and the restart function.

19. How can we cancel the application in CDM and after cancellation can we
restart the same?
The Cancel feature of CDM enables you to cancel (delete) an application.
Use caution when you cancel
CDM provides the Application Restart/Cancel feature for you to cancel You may
need to use this feature if you have a duplicate application on accidentally entered an
application into the wrong organization or type.
When you cancel an application, the Application record is removed from be
recovered. If you cancel an application by mistake, you need to reenter application
using the application Input screens (APIA).
Once an application is approved, it cannot be canceled.

20. How in CDM the operator’s access and authorities can be controlled?
An Operator record enables you to provide operator lending limit parameters. This
prevents an operator from approving an application for more than the operator is
allowed. When an operator is working in the Process Work Queue, the operator only
has access to the applications in the types and classes you have designated.

The Operator Record screens to add (APXA), maintain (APXM), and view (APXQ)
an Operator record for an organization currently on file in the CDM system.

21. How we can define the application inputs required for a particular Type
(Logo) in CDM?
We can use the Application Definition Directory screens to display a list of
application input definitions currently on the Application Definition file (APYD) for
an organization. From the directory, you can select to modify (APYM) or view
(APYQ) an application definition listed. The system displays the corresponding
screen for the selected application definition.

22. What is the APWP Screen in CDM and what information it contain and
what is the use of it?
Process Work Queue
We can use the Process Work Queue screens to access all queued applications for
which you have security, excluding those applications in the Edit, Selldown, Setup,
and Verification queues. This queue enables you to select detail screens on any of the
processing steps applied. There are information panels you can select to display
demographic, credit bureau, or memo information on APWP01.

IMPORTANT SCREENS and THEIR FUNTION

APTA, APTQ, APTM

The Type record defines the parameters and options CDM uses when processing this
type of credit application. You must complete all 20 screens to activate a new Type
record. If you do not complete all the screens before exiting the Type Record
function, the system tracks the last screen you were on. Then CDM returns you to that
screen when you use the Type Record function to complete the addition of the record.

PROCESSING CONTROL PARAMETERS

Processing parameters tell the system which of the nine application process steps to
perform. These parameters also define the sequence in which to perform the selected
process steps and the conditions that apply to each step.

DECLINED RETENTION Number of days declined applications remain in the

system’s online files before being purged

APPROVED RETENTION Number of days approved applications remain in the

system’s online files before being purged.
 PROCESS CRADLE TO GRAVE Code that indicates whether applications are
processed cradle to grave in this

APSM
Use the System Record screens to maintain (APSM) or view (APSQ) the System
control record. The System control record defines the overall characteristics for
processing applications in each organization and for each type.

APLR
Letter Request
Use the Letter Request screen to request a letter for a particular application. The letter
you request must have been previously added to the system using the Letter Record
add function (APLA).

APLM/APLA/APLQ
Letter Record
Use the Letter Record screens to add (APLA), maintain (APLM), or view (APLQ)
letter records for a particular type within an organization. A letter record contains the
exact wording to print when the system generates the letter for an application.

APIS
Application Status
Use the Application Status screens to display a status summary for an application that
the system is processing. The Application Status summary includes all application
participants (applicant, co applicants, and guarantors).

Designating an application for Secured Card

You designate an application a Secured Card application by defining any of the secured
card fields (801–809) on an initial input application definition (APYM Function I). Once
data is entered into any of the defined fields through initial input (APIA), CDM builds the
appropriate secured record to send to CMS if the application is approved.
Secured Card credit limit
To take advantage of the CDM Secured Card credit limit processing, the Application
Input screen (APIA) must include two field codes specifically designated for secured
accounts: Field Code 803, Security Percentage, and Field Code 804, Security Amount.
The credit limit is calculated based on a percentage (Field Code 803) of the secured
amount (Field Code 804). This calculated limit overrides the standard credit limit
assignment process result.
AD = Application Definition
AU = Accepted User Input
LE = Logged Errors
OS = Operator Statistics
SC = System Control
TC = Type Control
UI = User Input
AM = Application Master
ED = Edit Queue
LM = Letter Master
RU = Rejected User Input
SU = Setup Queue
TS = Type Statistics
VF = Verification Queue

01 APU600 Close files for batch run. JCL to execute an external CICS interface client
program to close files for the batch processing.

04 APU000 Control card load. Loads the control cards for subsequent steps. Program
header and control cards for subsequent steps

05 APU040 Backup online VSAM Files. Backs up online files before start of batch
processing.

06 APD020 Date roll. Advances system file processing dates on the System Control
record.

07 APU080 User input file create.

10 APD100 Sort/merge posting. Sorts and merges output of APD040 and APD080 for
input to Posting.
11 APD140 Type statistics update. Updates the type statistics by using the Type Statistics
Update file as input.

12 APD160 Operator statistics update. Updates the operator statistics by using the
Operator Statistics Update file as input.

Step Program Function Control cards

13 APD200 Posting. Performs the following functions using input from APD100:
Adds user input records from APD040 to the Application Master file and prepares
them for online processing
Ø Unlocks locked online Queue records
Ø Declines applications for excessive time in decision process
Ø Purges applications to Posting Archive History
Ø Deletes incomplete Application records
Ø Purges memos
 Ø Archives decline reason memos
Ø Purges Fraud records
Ø Cycles operator statistics
Ø Produces the Letter Request file, Credit Report Request file, and Visa Issuers’
Clearinghouse file
Ø Determines report requirements and produces Report File 03 (PR03)
Ø Produces Source Code Accumulator Update file
Ø Purges and archives Secured/Collateral records
Ø Purges and archives Supplemental Data records
Ø Purges Fraud Match records, Purges Edit Queue records
Ø Purges Verification Queue records, Purges Work Queue records
Ø Purges Selldown Queue records Purges, Name Key Records.

APD220 History file update. Merges Posting Archive

file from APD200 with Current History file
to produce New Current History file.

APD020
Date Roll
APD020 rolls the last, current, and next processing dates in the System Control file
(PMSC).
APD040
User Input Audit
APD040 sorts and edits applications provided as user input on either tape or disk. The
program generates two output files:
Accepted User Input (PTAU)
Rejected User Input (PTRU).
These files are input to APD100, which generates the Sort/Merge Posting file for the
Posting program (APD200). When finished, the program updates the Operator Statist

APOVPAO VisionPLUS Real-Time Update Routine Program This program is for auto
setup. Auto setup refers to the process of populating CMS fields with data that has been
entered in CDM. CDM application definitions include the desired information, and the
values for the CMS accounts are derived from the application information passed from
CDM to CMS.
 TRAMS

A) Explain what is significance of Institution and application in TRAMS?

(Ans) Every job in TRAMS is assigned a specific Institution and Application.
Institution signifies the Identification of the job and Application is 0001 for all jobs
except some ITS jobs.

In case of ITS jobs ---------> Job Inst Appl

ITSVSMC 9700 0001

ITSFFD 9700 0002
ITSFRD 9700 0003
B) What are the important functions TRAMS performs?
Ans. TRAMS is nothing but a data warehouse i.e., Collection of data from several
resources and sending the data to the respective destinations. It deals with several
Interfaces. It receives files from several sources like VISA, MASTERCARD, TIPSIN
team, ATMIN team, MERCHIN team, MISIN team . TRAMS processes these files.
Processing means checking for the file format and assigning destinations to the
transactions in those files.
C) Explain Destination assignment and Transaction mapping process of TRAMS.
. After processing these input files which are received from different sources, the
transactions are being destinated to several output files like VISAOUT,
MCARDOUT,CMSOUT,MBSOUT,ITSOUT.

We have PCRTRAN in trm/parm which contains input information & output

destination where it should go.

For ex. for ATMIN file ---------> i/p or o/p Inst Appl TC
(Transaction Code) DR/CR

01 6000 0001 0002

D

02 9450 0001 0001

D

01 --------> input

02 ---------> output

6000 -----> input Institution

9450 ------> output (destination) Institution

Similarly we have for all the other files.

D) What are the different types of TRAMS?

TRAMS DE, TRAMS AG, TRAMS EP explains the purpose?
Bank Card Module (TRAMS/BC)
Enables TRAMS to interface to the MasterCard, and Visa settlement networks.
 Data Entry Module (TRAMS/DE)
Provides the solution for situations where manual data entry is required. DE offers the
capability for high-speed entry of transactions into the system while protecting the
accuracy and integrity of the data.
Application Generator Module (TRAMS/AG)
Assists in the development and maintenance of TRAMS input and output (filepath)
programs
E) Explain concept of Suspense transaction with e.g.

F) What are FASTFILEPATH commands give some e.g.

G) What is MCC code and what its significance.

Ans. MCC - Merchant Category Code. It signifies the Class (type) of Merchant to
which he belongs. It represents Merchant Category Classification. We have the list of
(MCC) Codes Directory.

H) Any experience on AG development? Very Important

I) What are the various reasons for rejecting a file in TRAMS. (Duplicate / Outoff
balance)

J) How duplicate checking works in TRAMS (Hash total matching for file &
Batches)

K) What is Cash Letter?

L) Explain process of adding new transaction codes in TRAMS (PCRTRAN, LDAG job)

M) Explain format and significance if PCRTRAN file

N) What all different file status and Transaction status possible in TRAMS explain
meaning of them.
Ans. File Status Transaction Status

B A ---------Balance Active R ------ Released

D A --------- Duplicate S -------- Partial Released

O A ----------- Out of Balance

R A ----------- Reject

O) What will be impact on posting if file is got out of balance because of one
transaction

Ans. In our system if O A or D A or R A then posting will not be done.

If one of the batch got duplicated
If few transactions in file got rejected.
P) How many different destinations can be possible for single transaction?

Q) Explain the difference between File release status ‘R’ & ‘S’
R -------- Released completely
S -------- Partial Release
R) What is TRAMS warehouse file, Transaction code mapping file, jobschedule file,
trams calendar file
S) How TRAMS job understand which program to execute?
Ans. In NCPO511 program of every JCL we have in-line control Card. In this
control card the corresponding program to be executed is mentioned.
As in every TRAMS job transaction-processing step execute single program
NCPO511.

ITS Questions

A) What is purpose of ITS module in vision plus.

To raise chargebacks, retrieval requests for the disputed transactions.

B) What are the different type of transactions that can be raised via ITS also give
the screen names.
Copy requests or Retrieval Requests, Chargebacks etc

ITCV ----- Charge back VISA

ITCM ----------- Charge Back Master Card

ITRV ------- Retrieval requests VISA

ITRM ------- Retrieval requests MasterCard.

We can also raise Fraud Transactions And Fee Fund Disbursements.

C) Explain Chargeback / Presentment cycles with reference to ITS.

D) Explain the process of raising the chargeback with different screens. (CMS
screens to select the transaction then takes to ITS screen)
Ans. Goto ARTD/ARSD screens and select any transaction for which
Chargeback/RR has to be raised.
It will take you to ARTS screen which is the interface between ITS & CMS.
(x) Copy Request
(X) Charge Back
ansd so on.......
Then it will take you to either of the screens depending on the request made by you.
ITCV ITCM
ITRV ITRM

Enter the required details and press enter. Then CB/RR will be raised.
Note: All the Chargebacks/RR's reside in ITBL screen until we submit ITDAILY and
clear it.

D) When we move to ITS screen for raising chargeback from CMS , ITS screen comes
with prepopulated data for the transaction, from which file this data is picked, when this
file gets populated.

E)For particular transaction, if we are acting as a issuer for the card & acquirer for
the merchant then can we raise the charge back in this scenarion

No we can't raise chargebacks in this scenario.

F)What are the different jobs that need to be executed as part of ITS batch run

1) Jobs to receive transactions from ITS and send to TRAMS for sending to VISA
or MASTERCARD
ITSFFD --- Fees and Fund disbursment processing
ITSFRD --- Fraud transactions processing
ITSCV ---- ChargeBack processing

2) Jobs send transactions to ITS , which are received from VISA &
MASTERCARD.
ITSOUT

3) DAILY Prpocessing of ITS

ITDAILYP

Please note that job names may be different in different system but ITS should have all A
B & C jobs to run
Multi-purpose, front-end data collection, processing and routing system processes
transactions Accepts multiple transaction types and prepares the any destination
Provides extensive job tracking, settlement, warehousing, reporting, online reject and
suspense handling capabilities.

This multi-purpose, front-end data collection, processing and routing system processes
transactions from a variety of sources such as...
Check processing systems
ATMs
Bankcard associations- Visa / Mastercard
Merchant systems
Data entry
And other sources (both monetary and nonmonetary)
In addition to simplifying transaction processing, TRAMS supports bankcard
compliance reduces the cost of maintenance and helps implement changes quickly and
efficiently.
Handles High transaction volumes quickly and accurately
Flexible Input Processing
-- Lets data be entered and processed at multiple times throughout the day. This enables
error detection and correction before application production runs.

Institution
A single entity ( e.g VISA ) that’s ends data to or receives data from TRAMS .
Application
The specific subsystem( MBS, CMS , etc) within or associated with the institution that is
a source or destination of transaction data .
Destination
The point of posting for transactions . The target system to which a transaction is routed
from TRAMS .
dSourceID:NT0000292A

Some More Trams Question:

1) Before starting the Trams batch what are the files need to be updated?

Answer: We need to updated VISA Bin table file (NBVBINT), Account Range file
for VISA (NBVARDF), ICA numbers for Master Card (NBVICAT).
Apart from these files we need to update certain SSC file to make sure during the batch
we take the correct currency rates, Category codes. The SSC files are SMCA, SMCO,
SMCU, and SMRT.
For the updating of these files we get input from Master Card, VISA.

2) How can we comment by looking at the program name that program is online or
batch program?

Answer: In trams all the Online Programs have numbers ranging from 000 to 499 and
500 onwards are the batch program.
NCPO700 is the main reporting program.

3) What are the IPM preprocessing and post-processing programs in TRAM BC?

Answer: NBPO640 is the preprocessing program, which takes the input transaction file
send by Master Card, thus converting it into TRAMS understandable format and then
gives it to IPMIN file path, which is called by NCPO511.

After IPMOUT runs the Post processor run is NBPO641, the output file of which is sent
back to Master Card for the Off-us accounts.

4) What file path is run so that ATTD is created?

Answer: CMSOUT is run to create ATTD, which is passed to CMS through

ARD010.
Input file for CMSOUT is all the accepted transaction from NCVTRAN.
Following points are to be noted,
a) IPMIN always writes a memo transaction for the transaction with foreign
currency codes with amount as 0. These transactions are then passed to the CMS
via CMSOUT.
b) Plan number are hard coded by CMSOUT for Cash and Retail plans, so in case of
including number of plan numbers for different stores CMSOUT is customized.

5) What is the significance of NSVPRGM file?

Answer: NSVPRGM is the Program table for Trams and all the programs should be
defined in NSVPRGM. This is the part of initial parameter setup of the TRAMS.

6) Some file names and their functions:

File name Description

NCVSYSP System Parameter file which generally has 2 records one for
TRAMS and other for TRAMS DE. One of the parameters are
like Beginning of day is run or not, Settlement flag (like AMCR
system record in CMS). Tells about which Institutions we
running like VISA, MASTERCARD, EUROPAY, AMEX, IPM
NCVAPPLI This is the Institution /Application file. Several parameters like
source currency code, BIN number, ICA number etc are set in
this file (Like AMCR Org and Logo Record in CMS).
NSVFILE Trams File table all the files should be defined here or else
batch or online program will ABEND.
NSVPRGM Trams Program Table, all the program should be defined here.
NCVCALP Calendar file, Indicating which days are the workdays and
which are holidays.
NCVJSCH Job schedule file, Tells about which Jobs are scheduled for
today.
NCVLOGA Trams Online Log is kept here; this file can be browsed online.
NCVRPTP File tells about which reports to be printed daily. It is again a
part of Parameter setting.
NBVBINT Visa Bin Table.
NBVARDF Visa Account Range
NBVICAT Master ICA Table
NCVRDEF Record definition for all the files.
7) Some Important terms when it comes to TRAMS.

a) Institution: A single entity (e.g. VISA) that’s ends data to or receives data from
TRAMS.
Number 9000 is used by VISA as Institution Id.
Number 9001 is used by MASTERCARD.
The other institutions are like ITS, CMS input, CMS output, EUROPAY
b) Application: The specific subsystem within or associated with the institution that
is a source or destination of transaction data. Applications are individual software
systems that specialize in a particular type of account.
c) Destination: The point of posting for transactions, the target system to which a
transaction is routed from TRAMS.

8) What is TRAMS AG?

Answer: TRAMS AG is TRAMS application generator. It does the following

functions
1. Creating File paths like IPMIN, MSAFEIN, and CMSOUT so that can
be uploaded to mainframes.
2. Creating PCRHOST, PCRTRAN (transaction table).
3. Customizing the File-Paths.
Trams-AG is always kept in Synch with the version of TRAMS.

9) What are Mirror files and Mirror Records in TRAMS?

Answer: The mirror files are a set of files that are exact copies (with the exception of
mirrored or updated transactions) of files that are updated while the online system is
operating. During Process Input or Process Output batch runs, records are added to files
that require online maintenance. TRAMS perform all online maintenance to the batch
file’s mirror image. Only those records requested for update are mirrored; therefore, the
mirrored files are normally a minimal subset of the batch-maintained original file. When
a user requests to change one of these records online, TRAMS copies the original record
to the mirror file and presents it to the online user as if it is the original.
TRAMS include an online function to close and open (refresh) all original files that have
mirrors. This function is accessible through the Security Administration Menu, or by
entering REFRESHALL on the command line of any menu or action list, it can even be
achieved through the batch. This is particularly beneficial when running process input
File-Paths, as the batch job can follow the run to refresh files without requiring manual
intervention.
Mirror records are primarily created during reject corrections. As rejected transactions are
corrected, multiple mirrors may be written or updated. Once transactions have been
corrected and are ready to be sent to a destination (through Process Output), an
intermediate batch step is required to replace the original records with the corrected
mirrors. We use the term “reapply mirrors” to describe this function. Once mirrors are
reapplied, another process called “delete mirrors” deletes the mirror file (online only).
This is also done without TRAMS or through a stand-alone CICS transaction. This
function is also accessible through the Security Administration Menu or by entering
DELMIRRORS on the command line of any menu or action list.
A typical procedure consists of:

Run a process input file path to bring transactions into the TRAMS
1 BATCH database
2 ONLINE Refresh original files (close and open)
3 ONLINE Correct any rejects
4 BATCH Reapply mirrors
5 BATCH Process output (when needed; step 4 is required first)
6 ONLINE Refresh original files (required if performing step 7)
7 ONLINE Delete mirrors (not required but recommended).