Fast Path sample application

The Fast Path sample application demonstrates a banking application.

The IVP jobs and tasks set up the infrastructure that enables you to run the Fast Path sample application, but they do not run the sample application. The Fast Path sample application creates and uses four databases. Data is related to General Ledger (MSDB), Teller (MSDB), Loan (HDAM/VSAM), and Customer Account (DEDB) information for each account. DEDB and HDAM databases are loaded in the IVP offline using IMS-supplied utilities. All four databases are processed online using message processing regions (MPP) and Fast Path regions (IFP).

Two transaction codes are used in the Fast Path sample application:
  • FPSAMP1 - Executes in an IFP region
  • FPSAMP2 - Executes in an MPP region

The two transaction codes both execute the same application functions. The MOD name of the MFS format that is used by these transactions is DBFSMOUT. Use the IMS /FORMAT DBFSMOUT command to display this format.

The following figure shows the relationship of the four databases in the Fast Path sample application.

Figure 1. Relationship of the databases in the Fast Path sample application
Begin figure description. The general ledger and teller databases are inside a shaded box. A bank branch teller communicates with the teller database. The loans and customer account database are both outside the box but connected to it. End figure description.
The General Ledger database is a non-terminal-related MSDB. The DBD for the general ledger file contains a segment description that consists of the following items:
  • General ledger account number
  • General ledger account balance
  • Transaction count
  • Filler area
The Teller database is a terminal-related MSDB. The DBD for the teller file contains a segment description that consists of the following items:
  • Withdrawal amount
  • Deposit amount
  • Loan payment amount
  • Teller balance
  • Transaction code
  • Key to general ledger
  • Filler area

The Customer Account database (a DEDB) includes nine segment types in a three-level hierarchy, as represented in the following figure. The segment types include a root segment type, a sequential dependent segment type, and seven types of direct dependent segments. In addition, subset pointers point to the three account segment types that are represented in the database. This configuration allows the application to demonstrate the use of multiple SSAs and the use of command codes (including subset pointer references) for a DEDB.

Figure 2. A hierarchical diagram of the Customer Account database (a DEDB)
Begin figure description. This figure is described in the surrounding text. End figure description.

The second-level transaction segment is sequential dependent; all other segments are direct dependents.

The Loan database (HDAM) contains customer identification and transaction information. Transaction information includes all aspects of a banking scenario, including loan information, account numbers, and dates and times of transactions.

The hierarchical diagram in the following figure displays the segments (customer root and loan) of the HDAM/VSAM Loan database.

Figure 3. Segments of the HDAM/VSAM Loan database
Begin figure description. This figure is described in the surrounding text. End figure description.