Re: DDM over IP Problems

["Patrick Townsend" <patownsend@xxxxxxxxxxxxxx>]

Bill,

A couple of thoughts:

1. Could you be having a security problem in the direction that is failing?
DDM will validate the user ID of the source system. If the jobs on the
source system run under a different profile each time, you might be having
this type of problem.

2. When the job fails are you getting any messages in the job log? Normally
on the source system you will have one or more error messages about the DDM
failure. The second level text on these messages can be helpful in
diagnosing the cause of the problem. You can send them to me off line if you
need some help with the problem.

3. (OK, more than a couple) On the target system there will be a job in the
QSYSWRK or QSERVER subsystem that is servicing the DDM request. There can be
messages in the job log that are helpful.

Patrick
----- Original Message -----
From: "Bill Erhardt" <ERHARDT@BaldwinHQ.com>
To: "'Mid Range list - Questions'" <MIDRANGE-L@midrange.com>
Sent: Friday, November 16, 2001 1:30 PM
Subject: DDM over IP Problems


> This message is in MIME format. Since your mail reader does not understand
> this format, some or all of this message may not be legible.
> --
> [ Picked text/plain from multipart/alternative ]
> We have two AS/400's one runs our ERP the other runs our WMS.  We use DDM
> over an IP connection to access remote files.  When I access WMS files
from
> the ERP system everything is fine.  When I try to access ERP files from
the
> WMS system, the remote file is locked and applications running on the ERP
> system start failing.  Any ideas?
> Bill Erhardt
> --
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>