ECRTP

This section describes resolved CRs, updates, and clarifications in ECRTP.


Resolved ECRTP CRs

Table 8: Resolved ECRTP CRs

CR#

Description

424929 and

430711

Problem: When you run a compliance map with an input file that does not contain any EDI data, the trace and long trace do not report any errors.

Resolution: Trace and long trace now report errors when there is no EDI data in the input file.

449759

Problem: Fatal error 6001 occurs if spaces follow the last segment terminator.

Resolution: You can now include trailing spaces following the last segment terminator.

461418 and

469169

Problem: When you use the PrintEDI command in EC Gateway, the output files for different trading partners are not being sorted into different mailboxes.

Resolution: This CR has been fixed.

469272

Problem: ODBC connections are not restored when a connection is taken out of the ODBC cache for reuse because these connections were not identified as bad connections.

Resolution: ECRTP now correctly identifies bad connections in the ODBC cache and then restores the connections.

470061

Problem: When you run large inbound map files on IBM AIX and use the -mm switch, memory usage increases and memory is not released until the map stops running.

Resolution: This memory leak has been fixed.

474015

Problem: SySAM license messages—SYSAM SUCCESS and SYSAM GRACE—are written to the text log, resulting in error messages, when you run a 997 map using a non-ODBC trading partner.

Resolution: SYSAM SUCCESS and SYSAM GRACE are no longer written to the text log.


Updates and clarifications


Multiple file processing and KeyField/Linkfield match

ECRTP uses KeyFields and LinkFields to process outbound user files. While being read a record remains in the buffer even if a KeyField/LinkField break was hit. The record remains in memory by design.

For example, if ECRTP processes a purchase order file and a line item file, RTP reads a purchase order number, and then starts to read line items from the line item file. When RTP reads a line item record that does not share the same link field with the purchase order, the program stops processing, but keeps the line item record in memory. Processing of the line item record occurs after RTP reads a new purchase order that matches the line item record’s link field.