Академический Документы
Профессиональный Документы
Культура Документы
03.04.00
Release Bulletin
NCR and APTRA are trademarks of NCR Corporation.
Microsoft, Windows and Microsoft Visual Basic are either registered trademarks or
trademarks of the Microsoft Corporation in the United States and/or other countries.
This document and information herein is the property of NCR Corporation and all
unauthorized use and reproduction is prohibited. Copyright 2012 NCR Corporation,
Duluth, Georgia, USA. All rights reserved. Confidential property of NCR Corporation.
TABLE OF CONTENTS
1.
2.
3.
4.
5.
7.
8.
1.
INTRODUCTION
NEW FUNCTIONALITY
DEPENDENCIES
PROBLEMS
SPECIAL INSTALLATION INSTRUCTIONS
SECURITY IMPACTS
PREVIOUS RELEASES
INTRODUCTION
This is the Release Bulletin for NDC Business Services Component Release 03.04.00.
2.
NEW FUNCTIONALITY
This section describes any new functionality in this Release of the NDC Business
Services Component.
Internal Reference:
Functionality:
RFC 446053
Support PA-DSS (Payment Application - Data Security Standard) compliance
Internal Reference:
RFC 445261
Functionality:
Support native Bunch Cheque reporting to the host, and also support the new
SDM (Scalable Deposit Module) hardware as native Bunch Cheque and native
Cash Deposit.
-1 Support native bunch cheque deposit reporting to the host. Supports
only Buffer Identifier a in the Transaction Reply.
-2 Support the new SDM (Scalable Deposit Module) hardware as native
bunch cheque, native cash deposit and envelope emulation.
-3 There is no support for mixed media deposits. Support reporting the
hardware configuration variant as device identifier q when configured
for native cheque (cheque processor) and w when configured for
native cash (BNA).
-4 Support Option 83 for cheque processor configuration. This involves
reporting extra data in Terminal State messages (for bunch cheque
and single cheque configurations) and extra data in Device Status
messages (for a bunch cheque configuration).
Internal Reference:
Functionality:
RFC 451953
The IChequeMediaItem2 and IChequeMediaItemConfig2 interfaces should be
extended to include a MediaID property.
Internal Reference:
Functionality:
RFC 455868
Update native SCPM TrReq Message so different separators are used for
Cheques and Currency.
Internal Reference:
Functionality:
RFC 462547
NDC BS 3.4: Regression Test with APTRA Edge COM EMV Card Services
02.04.00.
Internal Reference:
Functionality:
RFC 480428
Added support for envelope emulation and night safe deposits on the same
machine.
Internal Reference:
Functionality:
RFC 475863
NDC BS 3.4: Deferred reporting of the envelope device status, which depends
on a TXO update.
Internal Reference:
Functionality:
RFC 492120
NDC BS 3.4: Added support for Voice Guidance in terminal commands.
Internal Reference:
Functionality:
RFC 502507
NDC BS 3.4: Support added for Enhanced Remote Keyloading - R, S and T
modifiers.
Internal Reference:
Functionality:
RFC 510683
NDC BS 3.4: Added support for SDM mixed media in envelope emulation
(updates to be done following code review and unit testing).
Internal Reference:
Functionality:
RFC 510680
NDC BS 3.4: Added support for NDC Device monitor - Extended diagnostics
support required for 03.02 SDM mixed media transaction.
Internal Reference:
Functionality:
RFC 533435
NDC BS 3.4: Added support to check for the availability of the devices for
envelope emulation mode.
Internal Reference:
Functionality:
RFC 543819
NDC BS 3.4: Added support for Native SDM MStatus required for Fault
Management.
Internal Reference:
Functionality:
RFC 579807
NDC BS 3.4: Added additional code behaviour for the CDM, IPM and CIM so
that they only attempt 2 Resets before declaring that the device is now FATAL
if the state persists. The time between Reset attempts should be configurable,
this should be done via NDCBSGeneralConfiguration.xml entry
<WincorSuspendTimer>300000<WincorSuspendTime/>.
Internal Reference:
Functionality:
RFC 510880
NDC BS 3.4: Added support to return EPP serial and FW version (Extended
Encryption Key Change) to NDC host through U modifier.
To report the Extended Encryption Key change data to host, ActiveXFS
controls version later than 02.11.00 needed.
Internal Reference:
Functionality:
RFC 605417
NDC BS 3.4: Edge NDC BS testing on Windows 7 Operating System.
This RFC involved running identified tests using Edge professional 03.00.00
and XFS 06.1.00 on Windows 7 Operating System. There are no code
changes done as part of this RFC.
-The testing is done on the following software stack:
Software
Windows 7 NCR OEM
APTRA XFS
APTRA XFS CDM SP (To test virtual cassette fix)
APTRA Edge Professional
Active XFS Controls
Advance Deposit & Payment
EMV Card Services
EMV Kernel
Version
SP1
06.01.00
96.01.00.06
93.00.00.51
93.00.00.01
93.00.00.51
93.04.00.54
06.00.01
-To run the XFS logical cassette fix (GR1T 599966) you need an updated
CDM SP 96.01.00.06.
Internal Reference:
RFC 608066
Functionality:
NDC BS 3.4: Added Support using Data ID 'a' in the transaction request
message for depositing a bunch of cheques.
If the field group with Data ID a is used to deposit a bunch of cheques (i.e.
use single cheque Transaction Request buffer) then no Codeline data is
provided and field cb2 in buffer a is set to 0.
Internal Reference:
Functionality:
3. DEPENDENCIES
This section details the NDC Business Services Component dependencies.
NDC Business Services Component has the following minimal dependencies:
1
2
3
4
5
6
7
8
CCM TCPIP 02.00.02 (Note that for PCI compliance, the version of TCP/IP
which supports Secure Sockets Layer (SSL) is required)
Business Service Interfaces 02.03.01
Data Manipulation 02.01.05
HICS Interfaces 02.02.02
Resource Manager 02.01.01
VDM Manager 02.01.03
NDC Business Services has a dependency on the Microsoft SNMP agent. Microsoft
SNMP agent must be installed on the target machine before installing the NDC
Business Services.
4.
Problems
This section describes the resolved and outstanding problems in this release of NDC
Business Services Component.
4.1.1 93.04.00.04
Internal Reference:
458788
Problem:
Resolution:
The translet 'resets' the validated array prior going to the host,
this no longer can be done as for native bunch cheque we look at
the validity to include the cheques in the transaction request or
count them as a cheque to return.
Internal Reference:
458574
Problem:
Resolution:
4.1.2 93.04.00.05
Internal Reference:
458937
Problem:
Resolution:
Internal Reference:
459880
Problem:
Resolution:
Internal Reference:
460886
Problem:
Resolution:
Internal Reference:
461523
Problem:
Resolution:
4.1.3 93.04.00.06
Internal Reference:
460144
Problem:
Resolution:
Internal Reference:
460569
Problem:
Internal Reference:
462144
Problem:
Resolution:
Internal Reference:
462380
Problem:
Resolution:
Internal Reference:
465599
Problem:
Resolution:
Internal Reference:
465673
Problem:
Resolution:
Internal Reference:
460559
Problem:
Resolution:
Changed the XML and XSD for M Status mapping of SCPM (Native
to Emulation mapping) Double feed defect.
Internal Reference:
466019
Problem:
Resolution:
4.1.4 93.04.00.07
Internal Reference:
465599
Problem:
Resolution:
Internal Reference:
461805
Problem:
Resolution:
Code updated for NOT to mask the field cb2--"code line flag in a
transaction request message for a Native cheque transaction.
Internal Reference:
462159
Problem:
Resolution:
Internal Reference:
466897
Problem:
Resolution:
Internal Reference:
456738
Problem:
Resolution:
Internal Reference:
467650
Problem:
NDCBS 3.4 Print and wait reply set up the CPM translet to expect
another reply.
Resolution:
Internal Reference:
461658
Problem:
Internal Reference:
460570
Problem:
Resolution:
The problem was due to the schema being incorrect and so these
updates were being ignored. The fix requires both these files: DeviceMonitorMapping.xsd - NDCDeviceMonitorMappings.xml
The SCPM MStatus 57 (double feed detect) should now be
mapped to Envelope MStatus 01 (jam).
Internal Reference:
460767
Problem:
Resolution:
4.1.5 93.04.00.08
Internal Reference:
470775
Problem:
Resolution:
Adding coin counts when BNA present and include direction byte
Internal Reference:
470899
Problem:
Resolution:
Internal Reference:
457436
Problem:
Resolution:
Internal Reference:
457436
Problem:
Device Monitor.
Resolution:
4.1.6 93.04.00.09
Internal Reference:
470999
Problem:
Resolution:
Internal Reference:
474250
Problem:
Resolution:
Internal Reference:
475664
Problem:
Resolution:
Internal Reference:
475683
Problem:
Resolution:
Internal Reference:
475799
Problem:
Resolution:
Internal Reference:
475804
Problem:
Resolution:
Internal Reference:
475807
Problem:
"Supplies Data" for Bin Full and Nearly Full scenarios for BNA is
not correct
Resolution:
Internal Reference:
476616
Problem:
Resolution:
Internal Reference:
478907
Problem:
Resolution:
Internal Reference:
478614
Problem:
Resolution:
4.1.7 93.04.00.10
Internal Reference:
470959
Problem:
Resolution:
Internal Reference:
481425
Problem:
Resolution:
Internal Reference:
483574
Problem:
Spawning for Trunk - FIT - Issuer ID retrieval from card track data
needs to be corrected.
Resolution:
Internal Reference:
483703
Device Status Messages not being sent for Depository. USPS
testing has found that device status messages for the DEP were
not getting sent when a reverse was executed by the TXO. The
error has been introduced while addressing RFC 480428, which
was to support envelope emulation and night safe deposits on the
same machine.
Problem:
Resolution:
Internal Reference:
480638
Problem:
Resolution:
Internal Reference:
471951
Problem:
Resolution:
4.1.8 93.04.00.11
Internal Reference:
486696
Problem:
Resolution:
Internal Reference:
487362
Problem:
4.1.9 93.04.00.12
Internal Reference:
489333
Problem:
Resolution:
4.1.10 93.04.00.13
Internal Reference:
484558
Problem:
Resolution:
FS should not be sent. Time Variant Number is not being sent but optional
FS is.
As per the spec, there should NOT be fourth FS and TVN for ready 9,B,
reject and specific reject.
Code updated in MessageInterfacepj to NOT include a fourth FS for a Ready
9,B, commandReject and specific command reject.
Internal Reference:
497767
Problem:
TAR 454944: NDC BS is not returning app back to In Service after comms
lost briefly (~1s). After re-establishing a lost comms connection the terminal
did not go into the last known status of Going Into Service and instead the
ATM stayed out of service. This was seen when connections were lost for
around 1 second and should have gone back in service and was working.
Resolution:
Code update Done in NDCProxy.cls to return the comms state to the last
previous knows status.
Internal Reference:
492110
Problem:
Resolution:
Internal Reference:
Problem:
498729
TAR 454716: NDC BS - ATM tries to contact NCR IP address.
Regions Bank have found that their ATMs sometimes try to contact an NCR
IP address. FGSC have found that the NDC BS DLLs for the version used
by Regions include the IP address in question. Further analysis has shown
that this was the IP address of the NDC BS build PC in Hyderabad at the
time. Older versions of NDC BS (included in US Edge 2.04) did not include
that IP address, so the problem was introduced in later releases of NDC
BS. On one occasion of the issue I have found so far in supplied logs,
there seems to have been an NDC BS / cash dispenser issue which results
in a UEH from NDC BS. An attempt is made at that point to contact NCR
IP address 153.58.35.111 (port 445), but it is blocked from doing so by the
bank's 3rd party CSAgent software. Port 445 is used for network shares.
Discussion with NDC BS development shows that the setup of the NDC
BS build PC seems to be the root cause of the issue.
Resolution:
4.1.11 93.04.00.14
Internal Reference:
503622
Problem:
TAR 456756: NDCBS missing Supplies Status field when cancel during
Night Safe Deposit.
Resolution:
Internal Reference:
503622
Problem:
TAR 459027: NDCBS NightSafe EMV transactions do not include CAM data
when cancel pressed.
Resolution:
Internal Reference:
492120
Problem:
Resolution:
Internal Reference:
502507
Problem:
Resolution:
Internal Reference:
510683
Problem:
Resolution:
4.1.12 93.04.00.15
Internal Reference:
497446
Problem:
Resolution:
Internal Reference:
484558
Problem:
Resolution:
Based on recent testing with NDC+ 7.0 and AANDC 4.0, we found that the
fourth FS is present in NDC+ and AANDC when MAC Flag 10 = 1. It means
the latest versions of COM NDC BS are now inconsistent with NDC+ and
AANDC. We have become aware the CIBC Base24 host is expecting to see
the fourth FS, and so they will not be able to move to the latest versions of
COM NDC BS. We will need to revert this change back, to be consistent
with NDC+ and AANDC, and the CIBC Base24 host. See the email attached
to 474072 for more info.
Internal Reference:
531162
Problem:
Resolution:
Internal Reference:
531162
Problem:
Resolution:
Internal Reference:
538721
Problem:
Resolution:
Internal Reference:
548302
Problem:
Resolution:
There has been an incorrect extension done to the NDCInterfaces.idl file for
recent voice guidance RFC (see attachment for details on the voice
guidance RFC). The breaking interface change was done to the
NDCInterfaces.idl file of NDCProxyInterfaces module in NDC BS.
Deposit
Interactive
Declined
4.1.13 93.04.00.16
Internal Reference:
552090
Problem:
An exception being seen while Host time out the SDM mixed media
transaction.
Resolution:
Code
updated
in
the
m_piTrxHandlerEvents_ReceiveTimeOut
and
557253
Problem:
Resolution:
4.1.14 93.04.00.17
Internal Reference:
510680
Problem:
Resolution:
Internal Reference:
552341
Problem:
Resolution:
Internal Reference:
557265
Problem:
Resolution:
4.1.15 93.04.00.18
Internal Reference:
543820
Problem:
TAR 462955: NDC BS : Change to have Command Reject not sent if msg
co-ord does not match
Resolution:
Code
Internal Reference:
562781
Problem:
NDC BS: DeviceMonitors should allow for BUSY status being returned at
start of day.
Resolution:
Internal Reference:
562982
Problem:
COM DM needs to handle a Busy device status returned while the TXO
resets the device. This has been seen on Wincor.
Resolution:
Unforeseen behaviour.
Internal Reference:
Problem:
566590
Remove EPP Serial Number from the Key Data sent in a Delete HSM/HSM
Root public key Extended Encryption Key Change message
Resolution:
Change in Requirement
Internal Reference:
563054
Problem:
Resolution:
Internal Reference:
557592
Problem:
Resolution:
4.1.16 93.04.00.19
Internal Reference:
RFC 575448
Problem:
Resolution:
4.1.17 93.04.00.20
Internal Reference:
552341
Problem:
Resolution:
Internal Reference:
RFC 576263
Problem:
Internal Reference:
576820
Problem:
Hyosung pin block generation, check digit needs removed as SP does not
expect it.
When we were doing the BOA proof of concept, we ran into the issue where
the vendors don't agree on whether or not the PAN should include the check
digit in the customer data field for the GetPINBlock. NCR ATMs assume the
check digit has been removed and Diebold and Wincor assume it is
included. So we had to check for "ServiceProvidedBy" to figure out whether
or not to include it. We do the same thing in the Edge NDC BS. It will only
remove the check digit if ServiceProvidedBy("NCR") is true. We just found
out that Hyosung apparantly works like NCR so the check digit needs to be
removed in both cases.
Updated the
NDCBusinessServiceSharedFunctions::BuildTransactionDataForPINBlockG
en method for service provider Nautilus Hyosung.
Resolution:
4.1.18 93.04.00.21
Internal Reference:
RFC 579807
Problem:
Resolution:
Internal Reference:
RFC 543819
Problem:
Resolution:
Added code in Wincor and Diebold vendor code to default the Native
MStatus to -1.
Internal Reference:
GR1T 475795
Problem:
Error reporting message sent to the host on more than one time.
Resolution:
Internal Reference:
GR1T 578759
Problem:
Resolution:
Internal Reference:
GR1T 579978
Problem:
Resolution:
4.1.19 93.04.00.22
Internal Reference:
RFC 579807
Problem:
Resolution:
Internal Reference:
GR1T 582117
Problem:
Resolution:
It has been found that US Standard edge uses a different TXO (which calls
reverse twice on failure) than BoA TXO (which calls reverse only once).
MultAccountCreditTranslet has been updated now to handle both the
scenarios effectively.
4.1.20 93.04.00.23
Internal Reference:
GR1T 475795
Problem:
Error reporting message sent to the host on more than one time.
Resolution:
Internal Reference:
RFC 543819
Problem:
Resolution:
Internal Reference:
GR1T 584398
Problem:
Resolution:
Added support in Device Monitor to check for the device busy status and
initiate the busy timer if the device is busy.
Internal Reference:
GR1T 585565
Problem:
Resolution:
Internal Reference:
GR1T 585996
Problem:
Resolution:
Internal Reference:
GR1T 586252
Problem:
Resolution:
Internal Reference:
GR1T 586939
Problem:
Resolution:
Internal Reference:
GR1T 586937
Problem:
Resolution:
Code
updated
to
call
ImportDESSignKey
StartKeyExchangeOK event handler.
command
from
4.1.21 93.04.00.24
Internal Reference:
RFC 510880
Problem:
TAR 457612: Request to add Extended Encryption Key Change msg with
modifier U to NDCBS.
Resolution:
Request to add Extended Encryption Key Change message with modifier 'U
-Send EPP Attributes' to NDCBS. This is not currently supported. The
customer requirement is to be able to return EPP serial and FW version to
NDC host in NDC message format but in an Edge environment
Internal Reference:
GR1T 588760
Problem:
NDC BS - COM Error being raised during FIT table search when non-ISO
standard Track 2.A COM Error is being raised when trying to process a FIT
search using invalid Track 2 data. The track 2 data has a valid PAN but no
field separator and so this causes the code to calculate the length incorrectly
and hence raise the exception.
Code updated in NDCFitTable.cls to append the FS when a Track 2 data
does not contain one.
Resolution:
Internal Reference:
GR1T 586006
Problem:
As part of PCI compliance code review we found some PCI issues with the
OLD RKL (NDCRemoteKeyLoading object). To address the PCI issue it has
been decided to remove the NCR Vendor Specific pre CEN 3.0 code in
NDCXFSRemoteKeyLoading.cls.
Removed the NCR Vendor specific pre CEN 3.0 code only.
(NCRRemoteKeyLoading)
We
still
support
pre
CEN
3.0
on
NON
NCR
ATMs.
Removed the code enclosed with in the bUseNCROnly flag.
(NDCXFSRemoteKeyLoading).
Resolution:
4.1.22 93.04.00.25
Internal Reference:
GR1T 592113
Problem:
Resolution:
IEMVTerminalConfig3_CheckSum
4.1.23 93.04.00.26
Internal Reference:
GR1T 596561
Problem:
Resolution:
to
check
against
the
4.1.24 93.04.00.27
Internal Reference:
GR1T 597843
Problem:
Resolution:
Internal Reference:
GR1T 598267
Problem:
Resolution:
4.1.25 93.04.00.28
Internal Reference:
GR1T 599080
Problem:
Resolution:
Internal Reference:
GR1T 597843
Problem:
Resolution:
4.1.26 93.04.00.29
Internal Reference:
GR1T 600723
Problem:
Hardware configuration data for Night safe deposit shows the device as NOT
configured when the Night safe is present and offering business deposit
transaction.
Code updated in CommandProcessor.cls to use the member variable
m_bNightSafePresent used for Night Safe deposit device.
Resolution:
4.1.27 93.04.00.30
Internal Reference:
GR1T 603315
Problem:
Resolution:
Internal Reference:
RFC 605417
Problem:
Resolution:
This is test only exercise where we ran the identified tests on the Windows 7
Operating system with Edge professional 03.00.00 and XFS 06.01.00
There were no code changes done as part of this RFC.
4.1.28 93.04.00.31
Internal Reference:
RFC 608066
Problem:
Support using Data ID 'a' in the transaction request message for depositing a
bunch of cheques.
Resolution:
Internal Reference:
GR1T 607778
Problem:
Resolution:
4.1.29 93.04.00.32
Internal Reference:
Bug - EDGNDCBS-1447
Problem:
Resolution:
While running one of EMV level 2 tests we found that solicited message that
we send to host after executing transaction is missing from proxy trace. We
can see this message in host simulator but it is not present in proxy trace.
Code updated in MaskCAMInDeviceSolMessage in GlobalFunctions.bas.
Internal Reference:
Improvement - EDGNDCBS-1448
Problem:
Resolution:
The limit of 128 bytes of Issuer Script length is removed from the EMV CS
02.04.00. Code updated in NDCBS to match the EMV CS. No limit is
imposed on the Issuer Script length data in Transaction reply and ITR
messages.
4.1.30 93.04.00.33
Internal Reference:
Bug - EDGNDCBS-1450
Problem:
PNC- During Native cash or Native cheque deposit on SDM, the unsol for
non active device should be sent by Translet in a controlled manner
Resolution:
Code updated to send the unsol conditionally when the IPM device (during
native cheque deposit) goes FATAL, check for the CIM device availability, If
FATAL send the unsol for CIM after completing the IPM transaction and vice
versa.
4.1.31 93.04.00.34
Internal Reference:
Bug - EDGNDCBS-1454
Problem:
Resolution:
Code updated in CIM monitor and SCPM monitor to deal with the
XFSCommandResult for the command code 1313 for CIM and 1610 for
SCPM respectively in order to send the FATAL unsol to host up on reset
failure.
Internal Reference:
Bug - EDGNDCBS-1457
Problem:
BSWT 612995 EMV - Hang on please wait screen when Mixed media
deposit is performed.
Resolution:
Internal Reference:
Bug - EDGNDCBS-1458
Problem:
BWT 613271 EMV SIT - Opcode for Check deposit with MagStripe is
different from Opcode for Check Deposit with Smart Card.
Resolution:
Code updated to set the destination account while build the EMV transaction
request.
Internal Reference:
Bug - EDGNDCBS-1459
Problem:
Resolution:
Internal Reference:
Bug - EDGNDCBS-1460
Problem:
BSWT 612718 Edge EMV - NDC BS doesn't mask card holder sensitive data
in CAM fields.
Resolution:
Internal Reference:
Bug - EDGNDCBS-1461
Problem:
BSWT 613179 EMV SIT - ATM rebooted after performing Check deposit
transaction with OAR account on CPM2 in Native mode.
Resolution:
Internal Reference:
Bug - EDGNDCBS-1462
Problem:
EMV SIT An exception raised from translet while doing a native cash
deposit transaction with EMV card
Resolution:
Internal Reference:
Bug - EDGNDCBS-1463
Problem:
EMV SIT Cant perform the chaining of deposit transactions with EMV card
in envelope emulation mode
Resolution:
4.1.32 93.04.00.35
Internal Reference:
Bug - EDGNDCBS-1461
Problem:
BSWT 613179 EMV SIT - ATM rebooted after performing Check deposit
transaction with OAR account on CPM2 in Native mode.
Resolution:
Internal Reference:
Bug - EDGNDCBS-1465
Problem:
Resolution:
Internal Reference:
Bug - EDGNDCBS-1466
Problem:
BSWT 613641 EMV SIT - Difference in behavior for Check Deposit with
Cash back transaction with Smart card and Magstripe card
Resolution:
Internal Reference:
Bug - EDGNDCBS-1467
Problem:
BSWT 613341 EMV SIT - ATM is rebooting if we not send authorised opcode
(after sending OAR2 and OAR22 opcodes) for transfer transaction using
CHIP card in Emulation mode.
Resolution:
Internal Reference:
Bug - EDGNDCBS-1468
Problem:
Resolution:
4.1.33 93.04.00.36
Internal Reference:
Bug - EDGNDCBS-1450
Problem:
PNC- During Native cash or Native cheque deposit on SDM, the unsol for
non active device should be sent by Translet in a controlled manner
Resolution:
Internal Reference:
Bug - EDGNDCBS-1466
Problem:
BSWT 613641 EMV SIT - Difference in behavior for Check Deposit with
Cash back transaction with Smart card and Magstripe card
Resolution:
Internal Reference:
Bug - EDGNDCBS-1470
Problem:
Resolution:
Internal Reference:
Bug - EDGNDCBS-1471
Problem:
Resolution:
Internal Reference:
Bug - EDGNDCBS-1472
Problem:
BSWT 615577 SMI Edge TDOL is a fixed value in the NDC BS, This needs
to be made configurable via an XML.
Resolution:
Code updated in Fittable.cls to make the TDOL as configurable via XML file.
4.1.33 93.04.00.37
Internal Reference:
Bug - EDGNDCBS-1473
Problem:
Resolution:
Internal Reference:
Bug - EDGNDCBS-1474
Problem:
Resolution:
Code updated ndcbs modules to not trace any transaction reply in any form
in PD trace.
4.1.34 93.04.00.38
Internal Reference:
Problem:
Resolution:
Code updated to send the specific command reject B97 when CAM data
contains invalid data.
Internal Reference:
Problem:
Resolution:
Internal Reference:
Problem:
Edge 05.00 - Created infeed jam near sensor 9 -SOH is not displaying the
SCPM fault (Another scenario Sensor12).
Resolution:
Code updated in Device monitor to store the recent XFS error so that a latest
device severity can be sent to host.
4.1.35 93.04.00.39
Internal Reference:
EDGNDCBS-1478
Problem:
Resolution:
When Chip card reader fails for some reason and fallback is configured and
Enhanced Config Option 69 bit 5 is set, fallback is reported to host through
CAM flags in a transaction request message.
Internal Reference:
EDGNDCBS-1482
Problem:
Resolution:
Support the Smart DIP card reader for fallback scenario and CAM flag
reporting in transaction request message for fallback when configured.
Internal Reference:
EDGNDCBS-1485
Problem:
Resolution:
Internal Reference:
EDGNDCBS-1486
Problem:
Byte 2 Bit 3 of CAM flags( Easy Entry processing not initiated) is set to True
for NON EMV transactions. A code correction required to set this bit to False
in case if fallback scenarios.
Code updated in NDCBSSharedFunctions.bas to set the Byte 2 bit 3 of CAM
flags to a correct value.
Resolution:
Boolean
4.1.36 93.04.00.40
Internal Reference:
EDGNDCBS-1480
Problem:
Resolution:
Internal Reference:
EDGNDCBS-1491
Problem:
Resolution:
4.1.37 93.04.00.41
Internal Reference:
EDGNDCBS-1495
Problem:
Card session is taking significant time to move to screen when EMV card is
inserted in IMCRW
Resolution:
4.1.38 93.04.00.42
Internal Reference:
EDGNDCBS-1494
Problem:
Resolution:
4.1.39 93.04.00.43
Internal Reference:
EDGNDCBS-1500
Problem:
When CPM4 depository goes down usually a jam, the hardware faults are
not going to host; due to the NDCDeviceMonitor not reporting the FATAL
device status properly (GEMS# 000000056315329)
Code updated in command processor to get the envelope emulation device
status from the device monitor.
Resolution:
4.1.40 93.04.00.44
Internal Reference:
Problem:
EDGNDCBS-1502
Cash Deposit is unavailable after performing timeout/cancel on Fee Screen
(GEMS#000000058467876)
Resolution:
Internal Reference:
EDGNDCBS-1503
Problem:
Resolution:
4.1.41 93.04.00.45
Internal Reference:
EDGNDCBS-1504
Problem:
Resolution:
Internal Reference:
EDGNDCBS-1505
Problem:
Resolution:
4.2
move
the
initialization
Problems Outstanding
The following problems are still outstanding in this release of NDC Business Services
03.04.00:
Internal Reference:
234985
Problem:
Impact:
Workaround:
N/A
Internal Reference:
237171
Problem:
Impact:
Workaround:
N/A
of
Internal Reference:
243674
Problem:
Impact:
Workaround:
N/A
Internal Reference:
309565
Problem:
Impact:
Workaround:
N/A
Internal Reference:
317860
Problem:
Impact:
Only seen with host simulator a real host would authorize the
correct amount.
Workaround:
N/A
Internal Reference:
337505
Problem:
Impact:
Workaround:
Internal Reference:
374517
Problem:
Impact:
Workaround:
N/A
Internal Reference:
342749
Problem:
Impact:
Workaround:
Internal Reference:
358815
Problem:
ATM does not send correct Solicited message when the last
cassette went empty.
Impact:
none
Workaround:
N/A
Internal Reference:
452564
Problem:
Impact:
none
Workaround:
N/A
Internal Reference:
475795
Multiple unsolicited device status messages can be raised for a
CIM and IPM when using an SDM device. This is due to the SDM
being a compound device and errors are common to both devices
being emulated and raised separately.
(i) A Fatal device unsolicited message may be sent more than
once based on error status changes reported by the device.
(ii) A second repeated IPM unsolicited message may be seen, due
to storing the message in the implementation for RFC 475863.
(i) The host will receive these messages but as they are updates
to the same fault and occur within a short time span there may be
no significant difference in the messages. Typically Fatal
messages are not repeated.
(ii) The repeated CPM message refers to the same error and
occurs within a short time span and so there is unlikely to be any
significant difference in the messages. Typically messages are not
repeated.
Problem:
Impact:
Workaround:
Internal Reference:
484558
Problem:
Impact:
Workaround:
SECURITY IMPACTS
7. PREVIOUS RELEASES
This section lists the complete history of new functionality & problems resolved in previous
releases of this component, in reverse chronological order.
Internal Reference:
Functionality:
RFC 368069
NDCBS to support sending of Application Status message by external
RFC 368070
NDCBS to support sending of Management Info message by external
application. Sending of Power-Up message can configured in XML
and be externally controlled.
Internal Reference:
Functionality:
RFC 371792
TAR 354700 / RAZCEPVL9 NDCBS to support Open Printer reporting
incorrect RSLen of 1.
Internal Reference:
Functionality:
RFC 381210
NDCBS to support multiple ITRs and requests to process each
cheque entered into the SCPM. The account used for first cheque
should be used for remaining. Fees are not supported.
Internal Reference:
Functionality:
RFC 381505
Coin Dispense to be supported in NDC BS for ChequeCashing. Coin
Dispense on Standard Message Interface.
Internal Reference:
Functionality:
RFC 381509
NDCBS to support dual dispense
Internal Reference:
Functionality:
RFC 384596
Support fallback after pre authorize failure.
Internal Reference:
Functionality:
RFC 392560
TAR 350034 / RAZCDCGQL Allow device monitor to run envelope
emulation with no envelope depository in the XML configuration
Internal Reference:
Functionality:
RFC 412351
Correct that the Credit Translet Doesn't Send Reply On FeeDenial
Internal Reference:
Functionality:
RFC 416139
NDCBS to support RKL EPP Serial Numbers greater than 8 bytes in
length
Internal Reference:
Functionality:
RFC 419109
TAR 393585 / RAZCZ6E9H Request to make max bunch size
accepted by NDCBS reflect the device capability.
Internal Reference:
Functionality:
RFC 424415
TAR 398131 /RAZCNY5NY Requested to prevent NDC BS sending D2
message to host for DASH
Internal Reference:
Functionality:
RFC 435200
Customiser requires to send the MICR of each cheque in Transaction
Requests to host when doing Envelop emulation using multiple requests.
Description Summary
370997
388145
Device monitor causes an exception if the vendor parser returns a NULL object.
Need to test multi cheque transaction replies for fee / account selection
need to see how silent fee denial effects multicheque / multi request transactions
TAR 370806 / RAZCQ3HVS NDCBS causes an exception when Post Auth return
invalid cryptogram with no issuer script results
Customizer Overdraft Fee processing
Host need to know when an invalid cryptogram has been returned on the ATM.
Cheque cash transaction is incorrectly completing without reporting an error when
the cash dispenser is failing.
CreateFeeTransactionRequest causes an exception when used with standard card
services.
Transaction handler should store lowercase HEX TVN as uppercase and not
lowercase.
Selective MACing code in the NDCMessageInterface needs updated to support new
message fields and extended cassette \ hopper usage
EJ and supervisor entry/exit messages not synchronized correctly.
EJ upload over power fail does not continue where it left off.
Cheque Cashing needs to handle MediaInKnownItems and MediaInUnknown items
of type "Nothing"
The ChequecashingTranslet function UpdateTransletProperties should only call
Calculate Amount when the Result is ATRESULT_Successful.
CompareFulfilmentItems function causes exception when attempting to access
MediaOutItem parameter properties
GetMediaOutReverseType function fails to check for correct Cash Retracted
reverse scenario
Cheque cashing should not populate AmountInAuthorised and
AmountOutAuthorised during Account Retrieval
Cheque cashing reversal logic not reporting proper type for cash present jam
TAR 369398 / RAZCPNC7L Supplies on CDM retract bin incorrect
TransactionHandler -GetNumberOfCoinsToDispenseFromHopper, hopper not
validated causing empty index read.
NDCBS 93.03.00.01 - DM crashes on low condition -native mode
Commit on fast cash on the ATM with the coin dispenser results in error
Merge GR1T for GR1T 395010 : BSWT 389827 - Huntington 3.0 - lockup after card
dip
TAR 378730 / RAZCRQ3M5 EJ comms loss not reported to EJ via the proxy
NDCBS 93.03 - Redistributables supplied with NDCBS MSI not registering the dll's
with proper information
Supervisor entry / exit requires SIU monitor to be present, this should not be
required.
Merge fix from NDCBS 93.02.00 to 93.03.00 - Tracking TD 4795: cancel of a
envelop Deposit transaction takes more than a minute
Alarms message does not report dual dispense cassette inserted / removed
correctly.
There was an exception reported when in session property was set true on proxy,
which is unnecessary.
Here the unsolicited message was not sent even when the device went fatal.
Ej Counters lost over power fail
Fittable PDing PAN data
388148
390479
390640
391396
392264
392722
395247
396020
396486
396488
397189
397290
397454
397490
397636
397716
398125
395828
398332
398339
398715
399836
399541
399673
400491
400644
400945
401283
401486
401548
401677
401858
401548
382197
403240
403833
404363
404721
405106
405355
405370
405926
406081
406675
406796
407204
407435
407474
404925
384596
408188
410151
410314
407713
410176
410331
411193
411831
410837
413298
413333
413658
411355
412351
414817
415485
405067
410622
413719
416139
417218
417640
417767
419725
408489
412437
420145
422055
422058
422213
420474
422502
422515
423717
423895
424865
425726
425332
426216
427066
429746
435200
438273
437721
433691
450844
445962
452171
TAR 391224 / RAZCYN9GZ EMV card did not eject after consecutive PIN error
ATM is not sending a R9 in response to a GIS Message from the host..
Tracking Basic SW Task: 394448 : Can't reverse ministatement if the last host message
doesn't have any print data.
While investigating 410401 the PD shows exceptions being thrown in Coin Monitor. The error
is a `subscript out of range in the GetSensorStatus method.
"Out of Memory " Exception thrown in the MultiAccountCredit Translet.
Update NDC BS to support RKL EPP Serial Numbers greater than 8 bytes in length.
TAR 393240 / RAZCZAET8 Tamper and Sensor Status reply does not reflect the correct value
of cassette in NDCBS 93.03.00.09
Adding a new CHM help file to NDCBS IT15
ENA - Pre-SIT - Hang on Please Wait Screen Due to Subscript Out of Range.
Default Cheque Destination needs to vary.
IDC Monitor - Card Jam - A0GetDiagnosticStatus
NDCBS 93.03.03 - Device monitor / journal monitor (JPTR) default mstatus is wrong.
Standard Base 3.0 drop 12 - Purge bin full error is reported 3 times in a row in the ej and
message trace - ATM 26 which is a P90 with EFunds CUP
EPP Variable Length Serial Number message is missing a group separator (GS) after the EPP
Serial Number field.
When running hardware faults on the CPM and BNA, the m-status that appeared in the
eventvwr was not the same as what appeared in the ej and msg trace. I saw an m-status 01
and mstatus 07 in the message trace and ej for a BNA validation jam. However, in the
eventvwr it shows the correct mstatus of 23.
Diebold Encryptor can be busy when leaving supervisor.
NDCBS COM coin monitor bug in coin mdata
EPP Variable Length Serial Number message information identifier is incorrect.
Incorrect property to check for the CDM type.
Coin Out causes ATM hang
GPTR - Duplicate diagnostic mapping
TAR: 398131 /RAZCNY5NY Urgent RFC requested to prevent NDC BS sending D2 msg to
host for DASH
TAR 398850 / RAZD425XC - EMV services not handling card without mag stripe data on Tk2
The global cashunits only gets updated on an availability changed this should also be updated
before getting the device status report information. The line m_vntCashUnits =
m_objCIM.CashUnits.Items needs to go in GetDeviceStatusReport before it starts to use the
variable
TAR RAZD38Y7M - Diebold Opteva Cassette Status P1 Not Reported to Host
This function does not check the CurrencyCassetteMapping offset in the Other Messages
setup for Selective MACing in order to determine whether selective MACing is to be done.
Similar mechanism to that used in adjacent functions for their own message type offsets.
SPAWNING - Need to make sure this is fixed in 3.0 RAZCY247U - Wachovia - Why didn't
Diebold atm notify host of Fatal problem with EPP--93.03 Trunk Version
Updated the MultiAccountCredit Translet to pass the current cheque via FulfilmentItems to the
Cusomiser so it can add the MICR as it sees fit.
TAR 409710 / RAZD8C6YQ Cached Note type invalid
Cash force deposit after denial
RAZD5XMSB Writing out ImageMark data on Cash Deposit when transaction had been
rejected at host with invalid PIN
TAR 421331 / RAZDCU637 Cached Note type invalid
During Supervisor if a device becomes FATAL then it is noted, but it is assumed that all device
should be fit on leaving supervisor so that should an error occur later it is action. Supervisor
does not appear to clear the last fitness string on exit so later errors are being ignored
TAR 421074 / RAZD7Q2B3 CIBC- Wrong Bin Status reported when cash unit is changed
RFC 340336
BNA driver introduced a new Mstatus 34 this should be directly mapped to
DEPEmulator Status 55.
Internal Reference:
Functionality:
RFC 361184
93.02.00 Support SCPM / bunch check module (envelope emulation mode
only).
Internal Reference:
Functionality:
RFC 339657
USPS: Extend configuration of NDC BS to allow Forced Deposit to be fully
configurable.
Internal Reference:
Functionality:
RFC 344995
NDC BS needs to report when forced deposit has occurred.
Internal Reference:
Functionality:
RFC 370374
TAR 349030 / RAZCD7EAQ Account translets should support customisation of
endorsement data.
Internal Reference:
Functionality:
RFC 361179
93.02.00 Account selection should complete before prompting for transaction
amount.
Internal Reference:
Functionality:
RFC 375705
93.02.02 - Reversal for Return Check Jam With No Valid Items Is Causing
Translet Runtime Error.
Description Summary
370997
Device monitor causes an exception if the vendor parser returns a NULL object.
325514
371007
371174
TAR 343256 / RAZC82LQE BSWT 365276 - BoA - August - Not all faults showing in
SOH/TTU.
360615
373774
Process outstanding ITR in the credit translet should not set the account.
374343
In the credit translet in envelope emulation when authorisation fails the cheque
376111
377458
376660
377453
should be invalid.
Transaction not recorded (No Passport files created in the C:\Passport\Upload
directory).
BoA Bulk Check is getting an exception in BOAChkAcctSvc: TransactionData when
trying to run NDCFITablePj.FITable: Exception:
Pin block failure does not invalidate all cheques.
378258
TAR 358891 / RAZCJ2MT NDCBS has to large a window from receiving a dispense
reply to sending the authorised event.
PD confusing as says sending CAM transaction request on Mag transaction.
377029
377347
TAR 360079 / RAZCKB27C ATM sent empty supplies status field for CDM.
378179
378257
377459
378364
377159
379409
379658
When check deposit denied by host the GetValidity returned from translet to txo
indicates that check valid even though the deposit was denied.
GR1T 376904 - BSWT 372457 TAR 349919 / RAZCDLK26 (& RAZCHMHPC)
Wachovia, Unknown Terminal Status Messages.
BSWT 376432 - RAZCKC2RV / REGIONS BANK problem with receiving 2 ready 9 at
the host.
377154
380175
319175
380705
378809
Account services not setting the cheque to valid after a forced deposit transaction.
378911
379219
379401
379406
376362
BSWT361627- Did not recover from comm loss ,eventhough after reconnected.
379518
BSWT : 373866 - RAZCDGHYG - North Fork Release 2.03 - Wrong Values shown on
Cassettees.
316583
380539
The counts message reports the number of notes rejected and dispensed in the
same field of dispensed count.
PAN and Buffer masking.
379416
380044
381627
381657
382062
383298
383570
Tracking BSWT 376692 - NDC BS Device Monitor does not report next "card
capture after unsuccessfull eject".
Application hang during PinChange transaction for EMV Card.
383874
383907
383314
383771
384419
384559
384812
387004
Merge into NDCBS 93.02.00.08 Tracking BSWT 382563 - Device Reset Mstatus
Logic Not Included in Check Cashing/Valuable Media Exchange Translet.
MStatus of zero is reported for some errors on BNA (Native mode) and CPM (Native
and Emulation mode) on Diebold Opteva.
TAR 370923 / RAZCQCM6R Deposit with Host timeout causes deposit details to be
added to next customers Passport xml file.
TAR 374482 / RAZCR3QM5 EJ upload stops after comms is lost and subsequently
restored.
387019
391462
396230
396231
399836
TAR 374952 / RAZCSCADH US - EDGE - PIN Change does not work inBofA 8.4
(bulk Check merge).
NDCBS 93.02 - Merge GR1T for GR1T 395010 : BSWT 389827 - Huntington 3.0 lockup after card dip.
NDCBS 93.02 - Redistributables supplied with NDCBS MSI not registering the dll's
with proper information.
NDCBS 93.03 - EJ comms loss not reported to EJ via the proxy.
396486
399889
398716
399516
402330
381768
TAR 361762 / RAZCLBCJC NDC Business Services requires update in order to detect
EPP-USB-2
RFC 313721
Support Cheque Cashing Transaction
Internal Reference:
Functionality:
RFC 361135
PCI-Mask PAN in logged files
Internal Reference:
Functionality:
RFC 361137
Merge all remaining 2.2 BoA RFC's
Internal Reference:
Functionality:
RFC 361253
Add support for device status objects for the BNA and CPM while in
envelope emulation mode
Description Summary
369574
TAR 353941: Not all EMV tags are present when chained transaction request sent
371795
373772
TAR 356691: Entries not being written to the EJ after a reversal due to timing
issue
374235
369188
370184
372723
373630
373635
374337
RFC 224239
The NDC Business Services must work together with the APTRA EMV
Card Services to provide an APTRA Edge application with EMV
functionality
Internal Reference:
Functionality:
321336
support rejecting cheques due to poor cheque images
Internal Reference:
Functionality:
337411
Passbook Support (print only)
Internal Reference:
Functionality:
337413
Support additional data recorded in the Imagemark XML files
Internal Reference:
Functionality:
337414
No Envelope Depository Faults in Envelope Emulation functionality
Internal Reference:
Functionality:
337709
Support extended length buffers
Internal Reference:
Functionality:
340939
For BNA and COM: only send device fatal state to NDC host after
unsuccessful device Reset
Internal Reference:
Functionality:
341787
Enable sending of transaction messages during supervisor mode
Internal Reference:
Functionality:
351180
Support journaling of cash unit removal and insertion
Internal Reference:
Functionality:
RFC 352170
Customiser needs notification of device status messages sent to the
host.
Internal Reference:
Functionality:
RFC 352382
Update Wincor support in NDCBS
Internal Reference:
Functionality:
RFC 356160
Add an option in account services to allow the customiser to choose
when CAM data is sent in a transaction request
Internal Reference:
Functionality:
RFC 358122
NCRaCSCore.StdCardTransletRecord object needs to be changed for
use with script languages
Description Summary
237014
323259
324893
335026
335036
335825
TAR 334381: Tamper and Sensor Status Data not reporting current state of Door
Contact Sensor
336438
336712
337501
337502
337564
337593
App fails to dispense due to hardware error (missing cassette) and M_Status 0
returned
337567
337665
337706
337991
338440
338642
338643
339593
TAR 325064: App fails to dispense due to hardware error (missing cassette) and
M_Status 0 returned
339610
339726
341074
341075
No status message sent if a failure occurs while retaining cash at boot in BNA
341076
341820
342075
342182
342331
342477
342484
342720
342738
342892
343195
Two m-statuses sent to the ej.xml and the msg trace during a pick failure
343712
CPM reported Warning Status for error but not follow-up Fatal Status
343943
Device Monitor does not always send a Fatal after sending a Warning
344463
344826
344925
BankNoteMApping can cause an exception when the session with the CIM is lost.
344927
BankNoteMApping can cause an exception when the session with the CIM is lost.
345394
346248
346420
346511
348196
348502
Session access token need to be dynamically check to work out what BSAT to use.
348908
349016
349504
NDC Proxy fails to send transaction to host after communications failure when
Consumer resource has been inhibited by another entity
350109
TAR 334172 and 343317 and 344134: NDCProxy gets in a confused state when
Connected event handler is interrupted by NotConnected event handler
350228
When a solicited status message is sent from the account service the STN is not
351183
When using the suppression of device errors the DeviceStatusEvent is not fired.
This is used by fault management, which still needs to know about device failures.
351209
351244
Wrong Device Status message has received after sending Refund message and
notes got retracted
351264
NDCBS seems to be the not sending response to encryption request and caused
hang up on a next TX.
351538
351791
351821
351824
352166
352192
TAR 342098: Loss of EJ Upload Data - requires reboot of ATM to restart EJ again.
352063
352219
352220
The Account services should now take care of following reverse scenario where in
"m_eFulfilmentException = ATFEXCEPTION_Cancelled",
"ATEXECSTATE_PreAuthorised" and "m_piFulfilmentItems" are set
353131
353300
When working with the US customiser we can not send a reply that gets a B97
reject and follow it up with a good reply
353452
353455
353507
Sending a transaction reply while not in a transaction request sends the wrong
reject
354164
TAR 347364: LastTransactionStatus does not match exact dispense mix when
multiple cassette types have same denomination
354642
355005
Should not use < and > in output to PD trace as this causes the trace to fail to
load.
355131
Cassette Low unsolicited and Cassette Fatal solicited not reported correctly
355397
355734
Setting of selective MACing causes an exception when previous mode was not
selective MAC.
356441
Pin change translet is using some account service ENUMS but should use the card
service ENUMS
356498
TAR 340272: NDC Business Services remains OOS if Key exchange arrives while in
Transaction
356504
Device vendor checks for an illegal mstatus of great than 80 decimal it should
check for greater than 80 hex
357695
A print and wait reply does not set up the translets to expect another reply
356706
Envelope dispenser unols should only ever send a device status of 0 as this is the
only valid unsol
357088
358958
Reversal of Translet
359882
Presenter error does not generate a presenter relevent MStatus for Wincor ATM
360136
No Device Status message sent to host for a CDM shutter jammed opened.
360307
TAR 345875: Unexpected currency reject bin out on supervisor screen after reboot
360451
TAR 345748: Wrong M-Status Sent to Base24 When CDM Interlock Disconnected
360615
361686
362125
TAR 347296: Hopper 2 pick failure results in dispenser grayed out and no ticket
opened at Gasper.
362360
329350
RFC 244699
Support the Night Safe Depository
Internal Reference:
Functionality:
RFC 301719
NDCBS should be enhanced to support the deposit transaction on the GBXX
hardware in BNA Emulation.
Internal Reference:
Functionality:
RFC 316809
NDCBS to support Envelope Deposit Emulation on GBXX Device
Internal Reference:
Functionality:
RFC 317595
Support cheque transaction recording.
Internal Reference:
Functionality:
RFC 318265
Accurate Dispensed values required to be printed on settlement transaction
receipts.
Internal Reference:
Functionality:
RFC 319944
CDMMonitor: Changed to support more than four physical cassettes.
Internal Reference:
Functionality:
RFC 319946
Raise the DeviceStatusChanged event on discarded UNSOLs.
Internal Reference:
Functionality:
RFC 321611
Support Terminal Service Interface in NDCBS.
Internal Reference:
Functionality:
RFC 322370
Support Cash Deposit Transaction Recorder.
Internal Reference:
Functionality:
RFC 322402
Allow resending of power up message if no response from host.
Internal Reference:
Functionality:
RFC 317276
A mechanism is required by which, when the NDC BS is installed onto an
NCR ATM, the vendor dependent error information provided by the XFS
platform is automatically turned on for every non-zero M-Status error
generated
Description Summary
248481
No receipt printed in a NDCBS will fail running debit transactions if configured with
less than four cassettes.type transaction
248481
NDCBS will fail running debit transactions if configured with less than four
cassettes.
302335
Advanced Deposit Translet throws exception when given >50 fulfillment items to
authorize.
247845
If an ITR is cancelled the transaction request sent contains the amount buffer.
302404
Night Safe device status message does not include supplies status.
301470
311758
312172
When message like GetHW, GetConfig etc are sent, the solicited message received
by the host does not report the availability of BNA and CPM device.
312332
313386
313486
313229
GBXX Transaction Status string created by device monitor does not map note
types.
313316
313293
313576
Transaction Handler Status Message for CDM validates supplies data incorrectly.
311831
A status message from a failed dispense is missing the required status fields.
314151
314262
315071
314595
315630
315710
316062
Reverse not supported correctly for note held at exit throat. Changes are required
due to new retract capabilities
315199
316086
There is an extra digit getting reported in the field g5 (supplies) message sent by
the ATM in return to the Hconf message sent by the host.
316264
When the CDM reject bin goes high device monitor report the replenishment state
as 5.
316671
The counts message did not report the last dispensed count for the CDM.
316271
If selective MACing is used on an ATM that does not have the extension set for
GBXX this will fail with an array subscript error.
317092
316950
317809
NDCDeviceMonitor CDM Monitor should retain first fatal MStatus to pass to the
Translet
315247
Completed updates for Remote Key operations to support NCR hardware on XFS 3.
319048
319949
320144
Wrong Status message when a cassette goes low when another goes empty.
322086
321609
319947
319948
322095
NDCProxy fails to release Consumer Token when GOOS sent and comms
immediately dropped.
322981
322982
323628
326302
Fitness terminal command is returning the wrong data for the fitness of the CDM
325667
326236
319675
326535
327447
327531
327533
324403
324076
324147
Debit Translet does not release control of CDM back to Device Monitor.
328829
328837
329258
328760
328606
329917
329954
Command processor is using the GBxx mapping in envelope emulation mode for
get CDM fitness.
329075
330649
330351
Transaction Request message does not have correct field separators before voice
guidance flag.
331104
331125
331280
331381
331467
331904
331903
Generate 6 spaces for the KVVs when the encryptor does not support KVVs.
331578
332163
Retract sends a Severity of Fatal when the device is still in a good state.
331560
NDC BS not reporting a BNA retract error status message to the host.
332465
332327
332322
333034
330296
333572
The Unsolicited message from device monitor may return counts data also the
translet needs to deal with this.
RFC 247065
Extend the interface to support additional options (JournalCommsStatus,
SendCameraNAK and CheckNightSafeAfterDeposit) for future development
Internal Reference:
Functionality:
RFC 247194
Support Advanced Deposit via Envelope Emulation and communicate using
ActiveX for CPM/BNA rather than ActiveXFS.
Internal Reference:
Functionality:
RFC 245653
Support Message Mode Option 4C Notes Dispensed for Spray Dispenser
Internal Reference:
Functionality:
RFC 237144
Support Angel Spray Dispenser
Internal Reference:
Functionality:
RFC 244636
Fees : NDC BS needs to support rejection of Fees that are specified by the
Host in a transaction reply
Internal Reference:
Functionality:
RFC 246313
Prevent NDCBS going in service when Pin Pad in unavailable at Start of Day
Internal Reference:
Functionality:
RFC 237118
Support Low Cost Dip Reader
Internal Reference:
Functionality:
RFC 311112
Require Edge NDC to go OOS on Exit from Supervisor
Description Summary
234016
235431
236187
236188
NDC Account Services : When the Consumer sets the FulfilmentItems, transaction
fails to complete, no further transactions can be performed
237648
238269
Remote Key Loading : Migration from BAPE Emulation cannot be performed due to
key library issue
238270
238450
239423
92.0.0.5 - EJ Upload code does not restart when new journal data is added to the
electronic journal data file.
243341
246314
247022
247067
Command Processor does not report any cassettes if less than 4 are defined in xml
247083
instead of 5
247680
247689
247736
248468
248457
248459
248021
Updated handling of fees to send correct response to host depending upon host
message that specified fees.
248304
248321
Updated handling of cash units to use the actual key names in the xfsdictionary
rather than assuming names of 1, 2, 3 and 4.
248494
248594
248600
248601
248613
248617
240210
247830
301640
301882
302389
302810
NDCBS Balance Translet Fails on some Double length PIN Block generation.
302842
302889
303244
304066
304067
Assign values from Device Monitor for MStatus, MData and suppplies in
BuildAndSubmitCardReaderDeviceSolic.
304068
304475
306653
308021
308092
308570
308518
303067
303735
304385
307736
308566
308865
309210
309301
309781
309782
310246
310275
Any mStatus over 80 will result in a reset of the ATM. These are not communicated
to the host and so are now filtered out (PD added to indicate this).
310305
Check IDC status when going in service and send device unsol on errors.
310307
311242
311314
Processing of CDM cassettes fails when XFS returns less than four cassettes
311647
Updated to not require a next state value with FunctionID P (Statement and Wait).
311749
311763
311940
The oos printimmediate message from a particular host has a space in the "Return
/ Retain Card" field - relaxed checking of Card Retain Flag in line with NDC+ code.
311941
248422
248614
312298
A host sends PrintImmediate while OOS without next state - added check to handle
this scenario.
313335
315001
Corrected error when EJ data length matches the exact block size then the record
was not deleted.
318797
Corrected size of message so that the NDCBS Download Manager does not send an
extra HEX character (NULL) in response to a 3<fs><fs><fs>4K command
318318
Updated to only process the Options and Timers optional field in an Enhanced
Configuration Parameters download message when they are specifically specified
in the host message.
318072
Updated NDCDeviceMonitor CDM Monitor to retain first fatal MStatus to pass to the
Translet. Otherwise additional commands to the device will generate XFS errors
(MStatus 10) and the host will be provided with a less meaningful error.
319109
Updated validation of FIT download to correctly check length of message and that
data is numeric.
319131
Added tracing to comms event handlers to add entries to Windows event log.
319153
320756
NDCProxy fails to release Consumer Token When GOOS sent and comms
immediately dropped.
321023
321424
Statement translet hangs if the last print message contains no statement data
321429
322207
322484
Handle Case where second terminal command sent without host waiting on
response to first
325075
320817
338654
TAR 323054: Tran/Device status 7 is being sent for too low a severity level
- End Of Document -