× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



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.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.