Specifications

R-44
Application System
2-4-2. Shared check tracking requirement
The following definition of memory allocation is required in each terminal before you can
perform shared check tracking.
• Number of check tracking tables:
For satellite, minimum one, for master, more than the number of estimated open checks
should be defined.
*
*
In case of using the next block
**
, one more check tracking table is consumed.
• Number of items/tables (per one item block
**
):
This is not the maximum number of items or functions but the number ordinarily
registered items or functions per one table. If the number of items or functions exceeds
this value during registration, the next block is used automatically for the following
transactions.
**
Number of item blocks:
Ordinarily, the registration requires one item blocks—but in a party for example—more
items are registered per one table. So it is necessary to define how many item blocks can
be used.
The maximum number of items or functions per one check is defined by the formula:
= (Number of items / tables) × (Number of item blocks (1 ~ 10))
When memory near end and memory end happens during registration, an error occurs.
See section A-5. Error messages of this manual.
2-4-3. Data backup when the master goes down
When the system has the backup master for the check tracking system, registered check
tracking data are stored both master and backup master automatically.
As soon as the system detects master down, the backup master roles as master for the check
tracking system.
(It is necessary to switch to backup master manually. See the “System down & Recovery”
chapter on page 9 of the installation & down recovery manual.)
When the system has no backup master for the check tracking system or both master and
backup master become down, no more check tracking operation and clerk interrupt
operation can be made.