Re: QUSRJOBI example - retrieve library list

Good point Scott....

That assumes of course that when the developer originally wrote the code
that he either allocated enough space for 1000 libraries or are dynamically
allocating the space needed at run time.

I don't think I bet willing to bet that many users of QUSRJOBI use dynamic
allocation or return data into a variable larger than 2826 bytes....<grin>

Getting back to the "modern" theme....
I suggest not retrieving the library list directly into your application at
all.
Instead, answer this question: Why were you planning on retrieving the
library list?
To Check for a libraries existence?
To Save/Set/restore it?
ect..

Now create a service program that provides procedures to handle the answers
above. That service program can call QUSRJOBI, you application will call
the service program procedures.

HTH,

Charles

On Tue, Jun 16, 2009 at 2:34 PM, Scott Klement
<midrange-l@xxxxxxxxxxxxxxxx>wrote:

The advantage to using QUSRJOBI over RTVJOBA is really compatibility.
let's say, hypothetically, IBM decides to increase the max size of a
library list again, thus time to 1000 libraries.

If you use RTVJOBA, then you'll probably have to rewrite your code. Or,
at a minimum, your existing code won't support the extra libraries in
the library list.

However, if you use QUSRJOBI, you can write your code so that it doesn't
have to be changed at all, and will automatically increase to the new
library list size. QUSRJOBI is more complex, but it's also more versatile.


Charles Wilt wrote:

There's nothing "unmodern" about CL itself...

Since QUSRJOBI is not a bound API call, there's little benefit to using

it

over a call to a CL program in the first place.

If you want to be "modern", instead of a CL program call a CLLE

procedure.

--
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.