######################################################################

----------------- SECTION 1.0 - Introduction -----------------------

######################################################################

Electronic Data Capture (EDC) is a software application that operates

on a PC-based Automated Teller Machine (ATM). EDC imparts the ability
to store journal information electronically as a disk file at the ATM.
By virture of its functionality, EDC can be used in conjunction with
the journal printer or take the place of the journal printer.

EDC supports multiple operating modes that can be configured based on

the needs of the institution. The operating modes allow EDC to store
journal data locally on a hard disk, or in a file that can be
retrieved by a host application, or unsolicited messages can be sent
to the host on each print request.

EDC also supports remote command interface that allows commands to

be sent from a remote application to configure EDC or retrieve EDC
files. The remote command interface can be accessed through a dial-up
telephone line or a leased line. A supporting software application
called EdcDial supports remote commands sent through telephone line
when an optional PC dial-up feature is installed with the EDC
application.

######################################################################
--------- SECTION 2.0 - What's new in EDC Version 3.0? --------------
######################################################################

i) Installation and Configuration of EDC:

The installation and configuration of EDC 3.0 will be done
through the centralized interface provided by the ATM Configurator.
The EDCOPTN utility that was previously
used to configure EDC will no longer be available.

ii) User Exit conforming to the SXA product:

EDC 3.0 has been developed as a user exit (in the form of a DLL)
conforming to the new SXA application. The functionality
previously achieved through EDC.EXE in the earlier versions of
EDC will now be supported through EDC.DLL that will be
dynamically loaded by the SXA application. For information
about the procedure for loading EDC or any user exit through
SXA, refer the SXA product documentation.

iii) Software replacement of Message Build Utility (MBU):

The functionality of the message build files used by previous
versions of EDC are now handled internally by the software.
EDC 3.0 does not use MBU to build messages.

iv) Reconfiguration of EDC:

EDC 3.0 will permit application reconfiguration of an appropriate
subset of EDC's configurable options without the need to shutdown
EDC. The reconfiguration of EDC can be done using the
"Reconfigure" menu option in SXATRACE utility. For more
information about the procedure for reconfiguring user exits
loaded by SXA, refer the SXA product documentation.
######################################################################
------------ SECTION 3.0 - EDC Command Utility ---------------------
######################################################################
The EDC Command Utility is a supporting application that resides on the ATM.
It allows the user to issue remote commands to EDC.

The commands are sent to EDC through the application command LE "EDCEDCUSR".

The syntax for invoking the application is as follows:

EDC_CMD [/C:command ] [/P:password] [/1:param1] [/2:param2]
[/3:param3]

All the command-line arguments are optional.

command - The command to be issued. The default command is "archive".
password - The optional unencrypted password.
param1 - Parameter 1
param2 - Parameter 2
param3 - Parameter 3

The response received from EDC will be written to a text file "EDC_CMD.log".
This file will contain only one line; the response received from EDC to the
last command sent through this utility or an error message. The return value
to the operating system will be the "Status" field from the response.

######################################################################
----------------- SECTION 4.0 - Revisions --------------------------
######################################################################

Version 4.0.0
-------------
Bumped revision from 3.0.5.4 to 4.0.0.1 to show the product being released for
XVendor 2.0 platform. No code changes were done.