Dave.. thanks to you input.
I am actually running this job in batch. But it causes this dump and ends
the program abnormally. Actually I clone this CL from a WORKING "live" CL
and just changing the File Name and RPG program Name. The Dream Writer
Parameters are Several times reviewed to be ok.
(BTW, I have been doing that all the time in my other programs and they are
working fine). It just that the file concern is coded/compile by my
"Systems Analyst". And therefore, I am thinking that there are "additional"
parameters were not set when creating this PF.
I believe the problem is caused when RPG tries to open/use it. But it is
SHARED in CL and therefore, there should be no problem. And also it should
be closed when the job ends.
This thing is making me go NUTS.
Cheers!
___________________
Marsh R Narewec
STC Computer Services
"Dave Kahn..."
<david.kahn@stoltoff To:
[email protected]
shore.com> cc:
Sent by: Subject: Re: Create PF in SVR - Additional
jdeworld-bounces@jde Parameters
list.com
26/08/2005 04:56
Please respond to JD
Edwards® World
This is basically sound advice but a few things could be clarified.
1. You only need to do a CLOF when you explicitly open the file in the CL,
usually with a shared open data path and OPNQRYF. In JDE this nearly always
means you are running under DreamWriter, and the JDE standard CL code
usually does a good job of tidying up after itself. You can generate a
standard CL program yourself by running the Quick Start CL Generator from
menu G93/5.
2. You should really be running these jobs in batch, so it normally doesn't
actually matter that much if the files get left open at job end as the open
data paths disappear with the job.
3. This problem occurs quite frequently in testing as the programmer runs
the DreamWriter interactively in order to use the interactive debugging
facilities. If the programmer terminates the program using the debugger the
CLOF in the CL gets bypassed anyway, so doesn't really help. The answer in
this situation when ! debugging is to close the file explicitly by
executing a CLOF from the command line.
Dave... Any views expressed are my own and do not necessarily reflect those
of Stolt Offshore