Re: External Stored Procedure writing to IFS Stream file

[Alan Campin <alan0307d@xxxxxxxxx>]

That does not make a lot of sense. I have used that trick all over the
place. Stored procedure writes to IFS and client reads the data from IFS.
Something else must be going on. Bet it is writing it somewhere else.

On Tue, Jun 22, 2010 at 2:02 PM, Neill Harper <neill.harper@xxxxxxxx> wrote:

> Good evening ladies and gents, hope you are all enjoying the world cup J
>
>
>
> I have a stored procedure (external written in RPGIV), that does some
> fairly
> trivial processing and writes its results to a stream file using the usual
> API's, i.e. open write and close.
>
>
>
> If I call the RPG program directly from the command line everything works
> perfectly, I get my stream file with the data in the ifs with the data I
> expect. If I call the stored proc from ops navigator the stored procedure
> runs and creates the file but it is empty.
>
>
>
> When I debug the stored procedure call, the call the write , returns the
> number of bytes written that I expect and the call to close does not return
> an error. There is nothing in the job log.
>
>
>
> If I tweak things in my stored proc to have it submit a job of to batch
> that
> performs the processing, the file is again created with the data I expect.
>
>
>
> This leads me to believe that the problem is being caused by the QUSER
> profile swapping that goes on in qzdasionit jobs.
>
>
>
> I am thinking write a small pgm that proves the problem and raise a PMR,
> but
> I wanted to put it out there and see if anybody had any views or simple
> solutions.
>
>
>
> Cheers
>
>
>
> Neill
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.