[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

3055.0. "Fetch delay" by UTRTSC::SMEETS (Workgroup support) Thu Mar 13 1997 11:21

Hi,

I've two customers running both V2.1C VAX/VMS and reporting the following
intermittent problem.

Customer receives a TF which contains some 100 documents. After a certain time
all 100 documents have been succesfully translated and are available for 
fetching.

After this the trade fetch command is started and 99 documents are succesfully
fetched only one document isn't fetched and still has the status Available.

Several attempts to fetch the document result in the message "Map produced no
output".

The customer keeps trying to fetch the document and after a certain time 
(� 2 hrs) this will eventualy succeed.

e.g.:

+-------------+                     DEC/EDI                       NODE:AHEDI1:: 
|d|i|g|i|t|a|l|              Full Document Details                  12-MAR-1997 
+-------------+-----------------------------------------------------------------

 Document ID                          Status                                    
 AH-ORDERS_I_0000501418               PURGEABLE                                 

 Document Type             : EDIFACT-ORDERS                                     
 User Reference            :                                                    
 Partner ID                : 8710400000785                                      
 Storage Directory         : DECEDI$STORE_36:                                   
 Tracking Count            :                                                    
 Creation Date             : 10-MAR-1997 11:22                                  
 Last Modified Date        : 10-MAR-1997 14:54                                  
 Acknowledgement Status    :                                                    
 Message Router ID         :                                                    
 Priority                  : NORMAL                                             
 Test Indicator            : Live document                                      
 Transmission File         : 10MAR199711192654_999994                           
 Data Label Supersets      :                                                    


 Number of Characters      : 631                                                
 Number of Segments        : 25                                                 
 External Standard         : EDIFACT      901                                   
 External Document Type    : ORDERS                                             
 Document Control Number   : 132                                                
 Group Type                :                                                    
 Group Control Number      :                                                    
                                                                                
 Application Interchange ID        : 8710400000006                              
 Application Interchange Qualifier : 14                                         
 Partner Interchange ID            : 8710400000785                              
 Partner Interchange Qualifier     : 14                                         
 Interchange Control Number        : 50                                         

 Document ID                          Status                                    
 AH-ORDERS_I_0000501418               PURGEABLE                                 
                                                                                
 Tracking Date       Tracking Status                                            
                                                                                
 10-MAR-1997 11:22   Transmission file is being separated                       
 10-MAR-1997 11:24   Transmission file has been separated                       
 10-MAR-1997 11:25   Document file is being translated from external format int 
                     o internal file format                                     
 10-MAR-1997 11:25   Document available for fetching                            
 10-MAR-1997 14:54   Document is being processed                                
 10-MAR-1997 14:54   May be archived                                            

There's no entry in the DEC/EDI errorlog which indicates a problem. 

Anybody has an idea what could causing this behaviour.

Thanks,

Martin
T.RTitleUserPersonal
Name
DateLines
3055.1Try this work-around...SCASS1::EDITEX::GONYEAThu Mar 13 1997 17:5121
    Martin,
    
    This is a known problem.  We've experienced it at a number of sites. 
    I don't believe that the problem has been fixed, but there is a
    work-around that we've used that seems to resolve the problem.  There
    is a logical DECEDI$AFS_QUE_REFRESH which defines how often the search
    list is updated in CACHE (my technical explanation may be incorrect,
    but this is the "laymens" description!). If you reduce this (I believe
    the default is 6 hours) cache will be updated more often and the search
    list will hopefully contain all documents.  Mark Thompson can certainly
    provide you with a better technical explanation and let you know if
    this has been fixed or what the outlook is.  One note....my
    understanding is that lowering this can have a negative impact on
    performance, particularly in high-volume shops.
    
    Hope this helps.
    
    Paul Gonyea
    
    Electronic Commerce Practice Group
    Dallas TX
3055.2FORTY2::DALLASPaul Dallas, DEC/EDI @REO2-F/E2Fri Mar 14 1997 09:1111
    This won't be fixed until V3.2.
    
    The problem is caused by a change in the caching algorithm to cope with
    high-volume sites. The AFS used to clear its cache and reload every
    time it failed to find a requested document. Now it merely does an
    incremental update and only flushes the cache when the refresh timer
    expires. The problem is that some documents can miss this incremental
    update, because they take a longer time to translate. 
    
    The problem is very common if you run multiple translators, since the
    documents can easily get to AVAILABLE out of sequence.