Re: DDM over IP Problems

Bill,

This sounds like a problem with the trigger program. I'm sorry I'm not going
to be of much help in that area. If the trigger program is trapping the
error that causes the "Unable to allocate resources" message, you might
remove the trap and let it dump. You might get a bit more diagnostic
information. Perhaps others on the list can contribute more about the
vagaries of trigger programs.

Patrick
----- Original Message -----
From: "Bill Erhardt" <ERHARDT@BaldwinHQ.com>
To: <midrange-l@midrange.com>
Sent: Monday, November 19, 2001 5:08 AM
Subject: RE: 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 ]
> Patrick,
> The WMS system is running an RPGLE program that reads a file from the ERP
> system.  The RPGLE program is called from a CLP that does an OVRDBF
command
> to override the File to a DDM file.  The WMS system job does not receive
> errors, neither does the server job running on the ERP system.  The file
> being read is a logical over a physical file that is updated via a RPGLE
> trigger program.  The trigger program is receiving the unable to allocate
> resource message.
>
>
> > -----Original Message-----
> > From: Patrick Townsend [SMTP:patownsend@patownsend.com]
> > Sent: Sunday, November 18, 2001 11:07 AM
> > To: midrange-l@midrange.com
> > Subject: Re: DDM over IP Problems
> >
> > Bill,
> >
> > On the WMS system where the write to the file is happening, and you are
> > seeing the error message "Unable to allocate resources", is there any
> > diagnostic information in the second level text (put the cursor on the
> > message and press F1)? With DDM you may also find a message before or
> > after
> > that message with more diagnostic information.
> >
> > On the ERP system is the RMTSRV job getting any error messages in its
job
> > log?
> >
> > I'm not expert on trigger programs and what might cause errors on DDM
> > interfaces. Hopefully someone in the list will be able to help out.
> >
> > Patrick
> >
> > ----- Original Message -----
> > From: "Bill Erhardt" <ERHARDT@BaldwinHQ.com>
> > To: <midrange-l@midrange.com>
> > Sent: Saturday, November 17, 2001 2:52 PM
> > Subject: RE: 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 ]
> > > Patrick,
> > > I get confused with source and target, but let's say the source is our
> > ERP
> > > system and the target is the WMS system.  I have a DDM file pointing
to
> > the
> > > file on the ERP system (by the way it's a logical file).  The
> > application
> > > that fails is a trigger program that attempts to write to the file
that
> > is
> > > opened via DDM.  The error I get is - Unable to allocate the required
> > > resources.  As soon as I end the RMTSRV job in QSYSWRK the problem
goes
> > > away.  Can it be a problem because the target file is opened by a
> > trigger
> > > program?
> > >
> > > > -----Original Message-----
> > > > From: Patrick Townsend [SMTP:patownsend@patownsend.com]
> > > > Sent: Saturday, November 17, 2001 12:27 PM
> > > > To: midrange-l@midrange.com
> > > > Subject: Re: DDM over IP Problems
> > > >
> > > > 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.
> > > > >
> > > > >
> > > >
> > > > _______________________________________________
> > > > 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.
> > > --
> > >
> > >
> > > _______________________________________________
> > > 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.
> > >
> > >
> >
> > _______________________________________________
> > 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.
> --
>
>
> _______________________________________________
> 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.
>
>