RE: Data Mirror start failure

I think it's related to how jobs are started in response to incoming APPC
request.
It depends on how communication entries are set in subsystem description,
which should process the request.
All below is valid if remote partner sends APPC request with <security
same> and provides only userID.
If default userID was set for corresponding APPC device/mode, than SECURE
location can be *NO. Job will be started with specified default userID.
If there's no default userID then job should be started with the same
userID used on remote system.
If only userID was sent (and no password), then local system has no way to
verify the validity of request. You need to specify SECURE location *YES -
then local system will trust remote system verification.
Otherwise request will be rejected with SNA sense code 080F6051, which
means security violation.

You may want to check your subsystem description settings, to be sure that
job is started with intended userID.

Best regards
    Alexey Pytel



Joey Stasinakis <jstasinakis@datamirror.com> on 01/11/99 10:51:29 AM

Please respond to MIDRANGE-L@midrange.com

To:   "'MIDRANGE-L@midrange.com'" <MIDRANGE-L@midrange.com>
cc:   Joe Oliveira <joliveira@datamirror.com>, Ronald del Rosario
      <rrosario@datamirror.com> (bcc: Alexei Pytel/Rochester/IBM)
Subject:  RE: Data Mirror start failure





Hello,

My name is Joey and I work at DataMirror Corporation as a Senior Product
Support
Specialist.
The communications issue Andrei Centea was experiencing has been resolved.

In some circumstances OS/400 upgrades have subtle modifications in the
Communications modules.
The Secure location parameter in the APPC device configuration had to be
changed
to a value
of *YES.  Prior to the OS/400 upgrade the value was *NO and everything was
functional.

This parameter confirms whether the local system allows the remote system
to
verify user passwords and to send an already verified indicator with the
program
start requests.


  o  *YES: Security validation by the remote system should
     be accepted.


Regards,

Joey Stasinakis

Senior Product Support Specialist

Datamirror Corporation
3100 Steeles Ave. East,
Suite 700
Markham, Ontario, Canada
L3R 8T3
Phone: 905/415-0310
Fax:   905/415-0340


-----Original Message-----
From: acentea@forzani.com [mailto:acentea@forzani.com]
Sent: Monday, January 11, 1999 10:26 AM
To: MIDRANGE-L@midrange.com
Subject: Data Mirror start failure


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
+---
+---
| 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
+---



+---
| 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
+---