|
[EDI-L Mailing List Archive Home]
[Message List]
[Reply To This Message]
RE: <TECH> , TLE 5.0
Martin,
You are the winner of this mystery game!!! If I had a prize to award, you
would win it.. :-)
I just got a call from Peregrine and they just emailed me a patch.
Thanks for you reply.
Rich
-----Original Message-----
From: [mailto:
Sent: Monday, October 01, 2001 3:45 PM
To:
Subject: RE: [EDI-L] <TECH> | TLE 5.0
We have this same problem with our TLE 4.2 on NT. We are migrating to EV5
on NT. This invalid IEA.01 count problem has been corrected with a newer
version of XLATO sent to us by Peregrine.
-----Original Message-----
From: Taylor, Mike P. [mailto:
Sent: Monday, October 01, 2001 3:34 PM
To:
Subject: RE: [EDI-L] <TECH> | TLE 5.0
Try moving the "force reject" logic farther up in the map(but after the
writing of the 1st segment). I'm guessing that you "force reject" too late
for TLE to correctly process the partial accepts.
_____________________________________________________
EDI-Mike
Michael Taylor
EC Specialist
Banctec - Corporate Information Systems
(972)982-2815
-----Original Message-----
From: Legge Rich-WLRL04 [mailto:
Sent: Monday, October 01, 2001 2:07 PM
To:
Subject: [EDI-L] <TECH> | TLE 5.0
Symptom: Value in IEA01 field is incorrect, larger than it should be, for
outbound document.
Background:
- Harbinger TLE 5.0 running in HP-UX environment.
- Application file being passed to translator (Harbinger TLE)
contains multiple documents.
- Map checks "validity" of application records and rejects document
that fails validity checks.
- It seems that the store field "GS-sets" is being incremented when
documents reject even though the rejected documents do not appear in
the output file.
- The reason that I know the "GS-sets" store field is being used is
from the "debug log".
- The map does not explicitly use the store field "GS-sets" at all.
- All other segments are being written correctly except for the IEA.
Examples:
- Application file contains "Good doc., bad doc, bad doc, bad doc,
good doc, bad doc"
The IEA appears "IEA*4*000000061", what should appear is
"IEA*2*000000061"
- Application file contains "Good doc., bad doc, bad doc, good doc,
bad doc"
The IEA appears "IEA*3*000000061", what should appear is
"IEA*2*000000061"
I have opened a case with Peregrine, but I thought I would see if anyone
else has experienced this or any similar issues with TLE 5.0 in Unix
environment.
Additional:
In my analysis of the debug log, it appears that the GS-sets value is
incremented after each of the "bad docs" in the middle, but not the last
one... I have some more scenarios I want to run through to get a better
feel of why it increments on some "bad" documents, but not on the last
one...
To unsubscribe from this group, send an email to:
Message Identifiers: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>,
<PRODUCT>
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
To unsubscribe from this group, send an email to:
Message Identifiers: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>,
<PRODUCT>
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
To unsubscribe from this group, send an email to:
Message Identifiers: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>,
<PRODUCT>
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
|
 |
Subscribe in XML format
| RSS 2.0 |
|
| Atom 0.3 |
|
|
Cart
