[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

3122.0. "V3.1A + PEDI" by NNTPD::"[email protected]" (Nicolas) Wed May 07 1997 14:10

Hi

we have migrate a customer from VMS to UNIX V3.1.
He is comunication with X.400. Outgoing comunication works without any
problems.
Incoming he gets following error:

EDISP2ENVIN   error disassembling envelope
EMAPORPARTIN error mapping O/R name to connection-ID
ERRRCON  error reading connection record
DBERRREAD  error reading row in database table SCF 1
SQLERROR SQLCODE = -284 A subquery has returned not exactly one row

At the moment they have 9 Connection ID over a PEDI-Gateway:
-6 Conn.ID. belongs to partner connectet over IBM-IE, so they have 1 X.400 
Adress with differen DDA-Definitions.
-2 Conn.ID belongs to partner connectet over Swisscos, so they have 1 X.400 
Adress with no DDA-Definitions.
-1 Conn. ID with a direct X.400 connection.

The last one works out and in .
The other only out.

The configuration was working well with VMS, the customer is asking why not 
with with UNIX ?? 
Is there a way to solve the problem ??

Please answer ASAP it's a production environment !!!

Regards

Nicolas


[Posted by WWW Notes gateway]
T.RTitleUserPersonal
Name		DateLines
3122.1Some clues and a guessMETSYS::NELSONDavid, http://samedi.reo.dec.com/Wed May 07 1997 14:3261
    I'll try to provide some clues.
    
    The "DBERRREAD  error reading row in database table SCF 1" error
    message is generated when trying to match the following O/R name
    values:
    
    SURNAME
    GIVENNAME
    INITIALS
    GENERATION
    COUNTRY
    AMDNAME
    PRDNAME
    COMMONNAME
    X121ADDRESS
    TERMINALID
    ORGNAME
    UNIQUEUAID
    
    SQLCODE -284 seems to be saying that it found more then one record
    that matched.
    
    My suggestion to you is to compare the above values in all the
    PEDI connection detail records.  If you find two or more Connection
    Details that have the same values for the above fields, then this is
    probably the cause of the problem.
    
    This may be a bug in the PEDI gateway, because if the above search
    doesn't find anything, then another search is performed that tries
    to match on the following fields:
    
    SURNAME
    GIVENNAME
    INITIALS
    GENERATION
    COUNTRY
    AMDNAME
    PRDNAME
    COMMONNAME
    X121ADDRESS
    TERMINALID
    ORGNAME
    UNIQUEUAID
    ORGUNIT1
    DDTYPE1
    DDVALUE1
    ORGUNIT2
    DDTYPE2
    DDVALUE2
    ORGUNIT3
    DDTYPE
    DDVALUE3
    ORGUNIT4
    DDTYPE4
    DDVALUE4
    
    As you see, this search covers more fields and hence, is more specific.
    I would think the correct Connection Detail record would be found
    if the code was able to perform this search.  But it can't, because
    the PEDI gateway code considers SQLCODE -284 as a serious error and
    aborts before executing the second search.
3122.2pedi setupFLYWAY::BLATTERNMon May 12 1997 18:0842
    
    Hi
    
    hier what the customer has defined into the X.400 adress.
    
    The y are using the SAME fileds for:
    
    COUNTRY
    AMDNAME
    PRDNAME
    
    the difference is in the fileds:
    
    DDTYPE1
    DDVALUE1
    
    but it seems that UNIX can not mache these second choise.
    
    Here an example:
    
    
     Connids Elbatex and Normelec have in common  \C=CH \A=IBMX400
    \P=IEEUR,
     and for Elbatex DDAtype 1 = IE, DDAvalue 1 =CHKETX CHELBA01
     and for Normelec DDAtype 1 = IE, DDAvalue 1 =CHKABN ABN001
    
     The same problem occurs also for the German IBMIE addresses, which
    have country, admin domain, private domain and
     DDAtype in common.
    
    Looks like a Bug, can you please fix it ASAP, as I told we are in a
    production system and we are not more able to retourn on the VMS one.
    
    Can you please tell me wenn you think it will be solved ??
    
    Many thanks for your support.
    
    
    Regards 
    
    Nicolas Blatter
3122.3METSYS::NELSONDavid, http://samedi.reo.dec.com/Mon May 12 1997 18:136
    
    I know longer work in the EDI Engineering group.  I think
    you'll have to submit an IPMT.
    
    Mark Thompson, I can point you to the module where I think
    the error is.  Send me mail if you need my help.
3122.4Need bug fixedNNTPD::"[email protected]"NicolasTue May 13 1997 09:469
Mark

please correct these bug ASAP, the customer had already enought other problems
with DEC/EDI and I hope we can help them soon.

If you need more information please contact me !!

Nicolas
[Posted by WWW Notes gateway]
3122.5METSYS::THOMPSONTue May 13 1997 10:475
Nicolas, I would ipmt it. All other problems gets worked on after the
the ipmt's.

M
3122.6Call doneNNTPD::"[email protected]"NicolasWed May 14 1997 09:166
Mark

call 45910 will cover these problem

Nicolas
[Posted by WWW Notes gateway]
3122.7IPMT #NNTPD::"[email protected]"NicolasWed May 14 1997 16:428
Hi

I hope you get the ipmt, here the number BRO100982

Hope here something soon !!!

Nicolas
[Posted by WWW Notes gateway]
3122.8METSYS::THOMPSONThu May 15 1997 18:335
Nicolas

yes it has arrived.

M
3122.9METSYS::THOMPSONMon May 19 1997 12:454
Hi,

the case has been updated with an urgent request for more information.
M
3122.10Problem SolvedNNTPD::"[email protected]"NicolasTue Jun 03 1997 14:5813
Hi

for the rest of the EDI-people.

The problem is solved !!
Patch in the DEC/EDI patches areas for 3.1 and 3.1A 
(EDIENG::USER2:[DECEDI_V31_PATCHES] and 
EDIENG::USER2:[DECEDI_V31A_PATCHES]).

Many thank to all that helped.

Nicolas
[Posted by WWW Notes gateway]