Synchronizing the Transaction Server with the CPCS Mass Data Set

In order to maintain data integrity between the MICR data on the Transaction Server and the MICR data on the customer’s check processing system, a synchronization process is essential between the two processing environments. The following descriptions detail how changes to CPCS MICR data can be synchronized to the Transaction Server.

Check Processing Control System (CPCS)

Each time the CPCS synchronize application (IZGSYNC) is executed, it transmits Mass Data Set (MDS) records and field update requirements to the Transaction Server. The synchronization of the MDS records to the Transaction Server is not immediate; the records are added to a processing queue and are applied to the Transaction Server in a controlled manner.

For more information on the IZGSYNC CPCS application, refer to the IBM® Payments Director Base for z/OS® manual.

Transaction Server

The Transaction Server provides a synchronize data queue that is used by the CPCS synchronize application (IZGSYNC) to queue work for synchronization to the Transaction Server.

The Transaction Server scans the synchronize queue on a periodic basis (default is every minute), looking for work that is in a pending synchronization status (see state descriptions below). If a pending record is found, the Transaction Server checks the capture status of the entry. If high-speed capture for the entry has completed, the Transaction Server applies the updates from the associated data items to the Transaction Server and marks the work as complete. If the high-speed capture for the entry has not completed, the work is left in a pending status.

Where multiple records for the same entry exist on the synchronization queue, these records are processed in the order they were received.

MICR Field Support

By default, the Transaction Server supports updating of MICR fields 1 through 7 using MDS records. Support for MICR fields 9 through 15 may be optionally added by configuring the database as described in Supporting Extended MICR Fields. Field 8 cannot be updated using MDS records.

Viewing the Synchronize Queue

The synchronize queue can be viewed from the Transaction Server user interface using the list syncqueue command. Table 1 describes the possible states of each record in the queue:

Table 1. Synchronization queue record states
State	Description
L	Data records are being loaded to the synchronize queue.
P	Work is available for synchronization.
A	Work is being synchronized to the Transaction Server.
C	Synchronization has completed.
E	Synchronization ended in error.

Restarting Sync Queue Records

When a synchronization fails due to an error condition, the sync queue record can be restarted using one of the following restart syncqueue commands:

restart syncqueue queuetime
restart syncqueue all

When using the queuetime option to restart a specific sync queue record, make sure to type the queue time exactly as it appears in the syncqueue report list. The all option restarts all sync queue records in the error state (E). Only sync queue records in error state can be restarted.

Updating the Communications Adapter Profile

To allow the CPCS Communications Adapter to call IZGIMAPI to retrieve a CIMS image, update the TCP/IP server (DKNIPSRV) configuration file. The sample profile shipped is in the APPLPROF data set, member DKNIPPRF.

In this version of this profile, add the following to the list of messages to invoke IZGIMAPI:

*
<MESSAGE>
   <TYPE>GET_CIMS_RECORD</TYPE>
   <TASK>IZGIMAPI</TASK>
</MESSAGE>
*
<MESSAGE>
   <TYPE>INIT_CIMS</TYPE>
   <TASK>IZGIMAPI</TASK>
</MESSAGE>
*
<MESSAGE>
   <TYPE>TERM_CIMS</TYPE>
   <TASK>IZGIMAPI</TASK>
</MESSAGE>
*