Data Mirror start failure

[acentea@xxxxxxxxxxx (Centea, Andrei)]

Hi all.

We use Data Mirror (DM) for our synchronization purposes, on a temporary
basis ( 6-7 times a year, for one week each). Both source and target
systems are AS/400. We never had problems until now, DM was perfect for
us.

Last time it was used, versions were V3R1 for OS/400 and V4R0 for DM.

Meanwhile, I had upgraded both, OS/400 is gone to V3R2 and DM to V4R2.
Versions are compatible.

Still, the launch is getting me back with a communication error:
_________________________________________________

CPD3B53    Diagnostic              40

To module . . : 
DMXCOMM                                                      
To procedure  : 
rcv_sna                                                      
Statement . . : 
14                                                           
Message . . . . :   Remote system rejected attempt to start program for
conversation
A.                                                                            
Cause . . . . . :   The remote system has rejected the attempt by the
local program to start a program in that system with Systems Network
Architecture (SNA) sense data of 080F6051.  There is an interface
problem between the local and the target programs, as identified by the
following sense data: -- 080F6051 - The system did not accept the
supplied security value.

Job description  . . . . . . :   DMCJOBD
Recovery  . . . :   Perform one of the following recovery actions: --
080F6051 - The default security value for CPI-Communications
conversations is SAME. Either configure the target system to accept an
already verified user identifier or use a default user identifier.
_________________________________________________

A technical request made to their customer support was not yet solved.
The Help Desk guys are still dealing with the problem from last
thursday.

Extra info to complete the image:

- Data Mirror user configuration has not been changed (same tables, same
systems, same communication lines and descriptions). In fact only OS/400
and DM versions have changed.
- Product is well installed on both machines (as of authorization code
or other).
- Authorities are *ALL for the user who makes the launch.
- SNA is working well (passthru valid from each system to the other one)
- Same message comes when using different users, including QSECOFR.
- LIBL, QSNADS and D_MIRROR SBS settings, CTLD and DEVD were all checked
by their Help Desk.
- all implied users are *ENABLED, with password expiration set to *NOMAX

Until I receive a solution from their Help Desk guys (and they seem to
be late), I would appreciate any suggestion from other DM users ... 

Thanks,

Andrei Centea
The Forzani Group Ltd.
Montreal, QC
450-671-7007, ext. 241
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---