BASE24 and BASE24-eps Overview

The Transact product suite provides data relating to Automated Teller Machine (ATM) and Point of Sale (POS) transactions as processed and recorded in the log files of the financial transaction software.


Transact uses a Generic Transaction Collector in conjunction with a Transaction Log Reader (TLR) to extract the financial transaction information from these log files.

Transact product suite - System Architecture

The Transaction Log Reader is started by the associated Generic Transaction Collector and continues operation until it is terminated by the collector.

Through a POS Transaction Summary record or an ATM Transaction Summary record, the required data is gathered from the collector and passed to the Web Application - View Systems. From the Web Application - View Systems operators can view the collected data through a range of Displays. Alerts can also be set up to notify of abnormal situations and data can be stored for future analysis.


ATM and POS transactions occurring in a BASE24-eps environment are logged to one of a number of sets of journal files. These sets of journal files are known as journal profiles. BASE24-eps can be configured so that transactions from different issuer ids can be logged to different journal profiles.

A journal profile consists of a configurable number of journal files (one for each day). One of these files is considered the 'current' file for today. At a specified time of day, known as the cutover time, transactions will cease to be written to the current file, and the next file will become the 'current' file. Prior to cutover, transactions may be written to the next day’s file, while other transactions are being written to the current file.

The journal profile definitions are contained in the Journal_Profile_Group (jpgd) and Journal_Profile_Group_Assign (jpgad) files. The physical file locations for the journal files are configured in the config.csv file (confcsv on HPE NonStop). The mdb.csv file (mdbcsv on HPE NonStop) provides information about the tables and columns in the BASE24-eps database.

A copy of irepstlr will be spawned for each journal profile to be monitored. Irepstlr will read transactions from journal files in this profile and send them to the Transaction Surveillance (IRTSVCOL*) or Transaction Manager (IRTXNCOL) collectors. These will be delivered as TransactionDetail, TransactionException, Base24epsPosTransactionSummary or Base24epsAtmTransactionSummary records to the rest of Transact. The journal profiles to be monitored need to be configured within the B24EPS configuration (for Transaction Manager) or the IRTSVCOL* ini file (for Transaction Surveillance).

* IRTSVCOI for Transaction Surveillance on HPE NonStop

Provide feedback on this article