Sybase Business Intelligence Solutions - Database Management, Data Warehousing Software, Mobile Enterprise Applications and Messaging
Sybase Brand Color Bar
delete

Search for    in all of Sybase.com
view all search results right arrow
  blank
 
 
 
 
 
 
 
 
 
 
Support > Technical Documents > Document Types > Technote > EDI Problems Corrected in Release 4.0.1

EDI Problems Corrected in Release 4.0.1

This TechNote describes certain problems in the 4.0 release of EDI products that have been corrected in 4.0.1.
 
RSS Feed
 
 
 

Contents

Description

A number of Electronic Data Interchange (EDI) problems have been corrected in release 4.0.1. Here is a description of the problems ordered by Change Request (CR) number. Where appropriate, the nature of the problem and/or corrective action are described.

1. CR #291024
Value 150 is invalid for the retry indicator.

This problem has been fixed and wsprocs no longer rejects the constant retry number.

2. CR #292571
The EDI engine fails to catch the error in the compliance map when the maximum number of sub-elements is exceeded.

When the maximum number of sub-elements is exceeded, the error is now written to the trace file and the log during a compliance map run.

3. CR #295822
In certain situations, ECRTP does not catch missing mandatory elements. For example if you have the segment REF*1*2~, and the third element is mandatory, nothing is reported.

ECRTP has been updated to handle this situation.

4. CR #296257
Record types for EBCDIC are not handled correctly.

Record types, found as an attribute on the field/edit or field/new screens, now allow an ASCII value to be entered if the record is used in an EBCDIC file. The ASCII value is converted to the EBCDIC equivalent.

5. CR #296341
The EDI engine fails when it encounters a packed decimal value with leading 00 (null value in EBCDIC and ASCII character sets) since null is the terminating character.

ECRTP has been updated to decode this value into a normal number.

6. CR #300789
In an Oracle database, the transaction log report fails with the error message "error detected by database DLL." Reports other than management reports displayed blank.

This problem has been fixed by changing the SQL syntax behind the reports.

7. CR #301131
In command GetNextFile, if a parameter is used for the directory and for the file destination, EC Gateway throws a General Protection Fault (GPF) Dr. Watson error.

This problem was caused when the number of parameters increased from 20 to 40 in Version 4.0. It is fixed in Version 4.0.1.

8. CR #303750
RunMapOut Command values in the EC Gateway 4.0 Command Interface are incorrectly formatted.

This problem was caused when the number of parameters increased from 20 to 40 in Version 4.0. It is fixed in Version 4.0.1.

9. CR #303931
The RunWait command does not assign the exit code to the Count variable or RunWait command does not wait.

This problem has been corrected so that the RunWait command waits for the executable to exit and successfully assigns the exit code.

Solution from Sybase

Sybase has issued corrections to the above problems with EDI maintenance release 4.0.1. This maintenance release is now available and can be obtained by contacting Sybase Customer Service at 1-800-8SYBASE (USA) or your local Sybase office.


 

DOCUMENT ATTRIBUTES
Last Revised: Jan 10, 2003
Product: EDI Server, EDI Products
Technical Topics: Bug Information, Application Integration
  
Business or Technical: Technical
Content Id: 1023141
Infotype: Technote
 
 
 

© Copyright 2014, Sybase Inc. - v 7.6 Home / Contact Us / Help / Jobs / Legal / Privacy / Code of Ethics