ATM Transaction Anayzer User and Installation Guide

Appendix B 153
Parameter Description
MAX-DATAFLOW-MSGS How Many Messages to avoid flood during long outage problem
Default: 10
AUTO-RECV-TIME
To enable recovery of data for specified duration of hours in online mode
Default: 0
CUSTOM-DATA-LEN
To specify the size in bytes of the customer specific extra tokens or data
Default: 0
RECOVERY
To enable/disable the recovery of missing transactions. ON|OFF
Default: OFF
SAF-CATCHUP-CONFIG
To configure the catchup process.
SYNTAX:
SAF-CATCHUP-CONFIG: <ActionThreshold>
<OVERWRITE|SHUTDOWN> <WarningThreshold>
<WarningRepeatSecs> <ANY|ALL>
Where,
• <ActionThreshold> is the percentage value of SAF file to catch-up when
violated. Either the collectors are shutdown or continue with possible
OVERWRITE based on what action is specified. In case of a violation the
backend agent logs the EMS event (SAF Full Action Threshold has been
reached for a FE. Shuting down Collectors or continue with OVERWRITE based
on the selected action.). If this value is set to 0 then there is no action, i.e.
continue with overwrite.
• <OVERWRITE|SHUTDOWN> is the action to be taken on above action
threshold violation. The possible values are OVERWRITE or SHUTDOWN.
• <WarningThreshold> is the percentage value when violated will log the
notification EMS events. Upon violation the backend agent will log the EMS
event (SAF Full Warning Threshold has been reached for a FE.). If this value is
set to 0 then there is no warning logged.
• <WarningReapetSecs> is the value in seconds to repeat the warning event in
case the SAF FULL is pending for long period. If this value is 0 then there will
be no repeat alert.
• <ALL|ANY>is used in case there are multiple front-end being fed by the
NonStop backend. ANY will trigger the action if there is a single FE need to
catchup xx%. ALL is used if all the fron-end catchup is true.
The collectors will not be started unless operator sends the “START_COLLECTORS”
command to the MAIN process. Once main process receives the command, it starts
the collectors and collectors resume processing either from current time or where
they left off based on the RECOVERY parameter configuration (ONLINE vs.
OFFILINE recovery).
Suspend data collection functionality will be disabled if the configured value for “%
Data-pending ” is 0
ENABLE-CUTOVER
It enables the collector not to close today's TLF file until it finds a customer record in
new TLF file. ON|OFF
Default: OFF
Appendix B