[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference rocks::dec_edi

Title:DEC/EDI
Notice:DEC/EDI V2.1 - see note 2002
Moderator:METSYS::BABER
Created:Wed Jun 06 1990
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:3150
Total number of notes:13466

3119.0. " duplicate transactions sent to trading partner" by GIDDAY::LEH () Thu May 01 1997 10:28

EDI 2.1B on VAX/VMS V6.1  - VAXstation 4000-90

As I'm new to EDI, so pls bear with me on basic questions.

There were reported of duplicate transactions that were sent out to trading 
partners; one of them was JBLACK who said to have received up to 20+ identical 
transactions. This problem has been intermittent for a couple of weeks, but 
only got worse since yesterday.

Thanks for any suggestions

Hong
CSC Sydney

==========
Some duplicate documents

 Document ID                          Status
 MMS-SEND-PO-APH_O_0000016912         PURGEABLE

 Document Type             : 850_HEMMP
 User Reference            : S1/466752
 Partner ID                : JBLACK
 Storage Directory         : DECEDI$STORE_19:
 Tracking Count            :
 Creation Date             : 30-APR-1997 18:06
 Last Modified Date        : 01-MAY-1997 12:00
 Acknowledgement Status    : No acknowledgement expected
 Message Router ID         :
 Priority                  : NORMAL
 Test Indicator            : Live document
 Transmission File         : 30APR199718104864_ADAIR
 Data Label Supersets      : DISABLED
 Number of Characters      : 707
 Number of Segments        : 24
 External Standard         : X12          002003
 External Document Type    : 850
 Document Control Number   : 0001
 Group Type                : PO
 Group Control Number      : 1776

 Application Interchange ID        : ALCOA.PTH.MB
 Application Interchange Qualifier : ZZ
 Partner Interchange ID            : AEBAKERCOIC
 Partner Interchange Qualifier     : ZZ
 Interchange Control Number        : 000001776

 Tracking Date       Tracking Status

 30-APR-1997 18:06   Document queued for outgoing conversion
 30-APR-1997 18:06   Document is being converted into external format
 30-APR-1997 18:06   Document converted by converter
 30-APR-1997 18:06   Transmission file is being built
 30-APR-1997 18:10   Transmission file delivered to the communication module
 01-MAY-1997 12:00   May be archived


 Document ID                          Status
 MMS-SEND-PO-APH_O_0000016913         PURGEABLE

 Document Type             : 850_HEMMP
 User Reference            : S1/466752
 Partner ID                : JBLACK
 Storage Directory         : DECEDI$STORE_20:
 Tracking Count            :
 Creation Date             : 30-APR-1997 18:06
 Last Modified Date        : 01-MAY-1997 12:00
 Acknowledgement Status    : No acknowledgement expected
 Message Router ID         :
 Priority                  : NORMAL
 Test Indicator            : Live document
 Transmission File         : 30APR199718104864_ADAIR
 Data Label Supersets      : DISABLED
 Number of Characters      : 707
 Number of Segments        : 24
 External Standard         : X12          002003
 External Document Type    : 850
 Document Control Number   : 0002
 Group Type                : PO
 Group Control Number      : 1776

 Application Interchange ID        : ALCOA.PTH.MB
 Application Interchange Qualifier : ZZ
 Partner Interchange ID            : AEBAKERCOIC
 Partner Interchange Qualifier     : ZZ
 Interchange Control Number        : 000001776
 Tracking Date       Tracking Status

 30-APR-1997 18:06   Document queued for outgoing conversion
 30-APR-1997 18:06   Document is being converted into external format
 30-APR-1997 18:06   Document converted by converter
 30-APR-1997 18:06   Transmission file is being built
 30-APR-1997 18:10   Transmission file delivered to the communication module
 01-MAY-1997 12:00   May be archived

and the next pairs with docID 914/915, 916/917...

 Document ID                          Status
 MMS-SEND-PO-APH_O_0000016914         PURGEABLE

 Creation Date             : 30-APR-1997 19:06
 Last Modified Date        : 01-MAY-1997 12:00
 Transmission File         : 30APR199719105115_ADAIR

 Document ID                          Status
 MMS-SEND-PO-APH_O_0000016915         PURGEABLE

 Creation Date             : 30-APR-1997 19:06
 Last Modified Date        : 01-MAY-1997 12:00
 Transmission File         : 30APR199719105115_ADAIR

........

 Document ID                          Status
 MMS-SEND-PO-APH_O_0000016916         PURGEABLE

 Creation Date             : 30-APR-1997 20:06
 Last Modified Date        : 01-MAY-1997 12:00
 Transmission File         : 30APR199720105347_ADAIR

 Document ID                          Status
 MMS-SEND-PO-APH_O_0000016917         PURGEABLE

 Creation Date             : 30-APR-1997 20:06
 Last Modified Date        : 01-MAY-1997 12:00
 Transmission File         : 30APR199720105347_ADAIR
.......

The partner was defined as

EDI> list conn/ful jblack

 Connection ID       : JBLACK

 Status              : ENABLED
 Window State        : ON
 Syntax              : MULTIPLE
 Current Error Count : 0
 Service Description : X.400 Communications

 MRX Route           : PHV016
 Message Type        : P2
 Message Encoding    : IA5TEXT
 Record Length       : 1024
 First Terminator    : 000  decimal
 Second Terminator   : 000  decimal

 MR Mailbox          : MRX_TELEMEMO

The application ID was

 Application ID      : MMS-SEND-PO-APH

 Application Name    : MMS SEND PURCHASE ORDER

 Address             : ....OF AUSTRALIA LIMITED
                     : P.O. BOX 460   

 Contact Name        : JIM CAIRNS / BOB FLETCHER
 Contact Phone       : ..
 Contact Address     : ..

 E Mail Address      : PH991JH
 E Mail Notification : YES

 Ordered Converter   : YES


Their params

digital         Import/Export Parameter Details             01-May-1997


 Status                   : ENABLED

 Connection Error Limit   : 20


 Default Import Directory : DECEDI$TOP:[IMPORT]
                          :

 Default Export Directory : DECEDI$TOP:[EXPORT]
                          :

digital           X400 Parameter Details - 1 of 2           01-May-1997


 Status                    : ENABLED

 Connection Error Limit    : 20

 Default MRX Route         : PHV016
 Local MR Mailbox          : DECEDI
 Local MR Mailbox Password :
         DECEDI_TPX400

 MR VMS Mailbox Name         : DECEDI$COMMS_MR_X400

 Local Country Code          : AU
 Local Administration Domain : TELEMEMO
 Local Private Domain        : ALCOA
 Local Organization          :
	ALCOA
 Local Unit Name 1  :
                 2  :
                 3  :
                 4  :

 Local Surname      : APHX400EDIGATEWAY
 Local Given Name   :
 Local Initials     :
 Local Generation   :

 Local Unique UAID  :

 Local X121 Address :
 Local Terminal ID  :

Their DECEDI$TOP:[ERROR]DECEDI$ERRORS.LOG showed a number of errors, but none 
seemed to match the problems with this partner

-SYSTEM-F-MBTOOSML, mailbox is too small for request
-DECEDI-I-CONDLOGGED, condition logged by DECEDI$X400 on node PHV016:: at
8-APR-1997 09:18:28.28

%DECEDI-E-UINOPRIVS, insufficient privilege to execute command
-DECEDI-I-CONDLOGGED, condition logged by X_1 on node PHV016:: at  9-APR-1997
17:08:00.38


%DECEDI-W-ERRMR_FETCH, Message Router fetch error
-MRIF-E-NOMESSAGE, the mailbox contains no message
-SYSTEM-F-MBTOOSML, mailbox is too small for request
-DECEDI-I-CONDLOGGED, condition logged by DECEDI$X400 on node PHV016:: at
11-APR-1997 01:05:40.58

%DECEDI-I-ORBSTATMSG, ObjectBroker status message = %ACAS-E-INV_TRANSERR,
Transport error `broken pipe'.
-DECEDI-I-ORBSTATMSG, ObjectBroker status message = %ACAS-E-INV_COMMFAIL,
Transport level communication failed.
-DECEDI-E-ORBERROR, An error was encountered calling the ObjectBroker routine
ACAS_InvokeMethod
-DECEDI-I-CONDLOGGED, condition logged by ACAS_000000CC on node PHV016:: at
28-APR-1997 06:37:23.78


%DECEDI-E-FILSRVERR, file server error detected
-DECEDI-I-CONDLOGGED, condition logged by ACAS_000000CC on node PHV016:: at
28-APR-1997 08:27:58.59

-SYSTEM-F-MBTOOSML, mailbox is too small for request
-SYSTEM-S-BUFFEROVF, output buffer overflow
-SYSTEM-S-BUFFEROVF, output buffer overflow
-SYSTEM-S-BUFFEROVF, output buffer overflow
-DECEDI-I-CONDLOGGED, condition logged by DECEDI$X400 on node PHV016:: at
30-APR-1997 14:30:12.57

and the mailbox

$ sh dev/ful DECEDI$COMMS_MR_X400

Device MBA101: is online, record-oriented device, shareable, mailbox device.

    Error count                    0    Operations completed              12573
    Owner process                 ""    Owner UIC                  [EDI,DECEDI]
    Owner process ID        00000000    Dev Prot    S:RWPL,O:RWPL,G:RWPL,W:RWPL
    Reference count                1    Default buffer size                 128

T.RTitleUserPersonal
Name
DateLines
3119.1METSYS::THOMPSONThu May 01 1997 11:3911
What;s being duplicated? The transaction (document) or transmission?


We have seen cases of duplicated transmissions before but only on the BISYNC
Gateway. 

At the one site I've seen this problem before, the customer was acutallu
posting them multiple times.

Mark
3119.2duplicated document, I believeGIDDAY::LEHThu May 01 1997 13:2731
Mark

>What;s being duplicated? The transaction (document) or transmission?

I may be confused with terminology here, but looked like to have been 
duplicated documents since the affected partner received multiple identical 
documents of the same (business) transaction

As said in the base note, I observed many pairs of 'duplicate' transmissions
such as 16912/16913 where all details were identical, incl. doco creation 
time, transmission file sent to comms module etc., except Doco Control Number.

 Document ID                          Status
 MMS-SEND-PO-APH_O_0000016912         PURGEABLE
 Document Control Number   : 0001

 Document ID                          Status
 MMS-SEND-PO-APH_O_0000016913         PURGEABLE
 Document Control Number   : 0002

Was this normal?

Customer had been suggested by previous branch support to upgrade to 2.1D and 
move off ACAS to Object Broker, but nothing happened to date. Any chance the 
current config might have caused the problems

Where else should I look for possible causes? 

Thanks

Hong
3119.3FORTY2::DALLASPaul Dallas, DEC/EDI @REO2-F/E2Fri May 02 1997 10:367
    Duplicate documents could well be caused by the customer's application
    posting the document twice. DEC/EDI does not check content of the
    information passed across the interface. As long as the control fields
    are OK, the document will be sent. 
    
    I've never seen DEC/EDI create duplicate documents. (That doen't mean
    it can't happen, but it would be very unusual).
3119.4IPMT case CFS.50917GIDDAY::LEHFri May 02 1997 13:301