Well, I thought I was keeping it simple until IBM throw a loop at me. Just
do one call to each API with *ALL and process list until it got this weird
error ended up using the generic support to get around it but creating a
list of objects and call the correct API for each type makes sense to.
On Thu, Mar 31, 2011 at 5:46 PM, James Lampert <jamesl@xxxxxxxxxxxxxxxxx>wrote:
Alan Campin wrote:
There is a problem. The user space can only be 16MB and if the data fromthe
system API calls exceeds that is blows up with a mysterious error. Tookdays
for IBM to finally come back to me and say what the problem was. This isdoesn't).
only a problem is you have a bunch of programs in a library (who
I don't think that's terribly likely to happen, given that I'm calling
QBNLPGMI separately, with a clean user space, for each program.
I didn't even know that it could take a generic, and if I did use a
generic, then I'd have to process more than just the first PGML0100 in
the user space, anyway, which violates the KISS principle. (Any
circumstance that would have the entry point anywhere but the first
module linked would put the program beyond the scope of this refresh
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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
This mailing list archive is Copyright 1997-2019 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