|
midrange.com
How many times is this argument going to flare up and down? Anything IBM
would have done to increase the size of the library list was going to
involve a code change to anyone using a larger library size. Putting it in
a separate area, increasing it where it was, whatever. Any location in
which anyone uses more than the previously available entries would have had
to change their code. There is no getting around that fact. Frankly I
applaud the fact they did it this way. (not that I had any say). Now, 6
releases later you won't have to retrieve it from two different places and
wonder why IBM didn't just do it right the first time. So big deal, they
have a data area. You can turn off the capability. Just wait until
management buys that package that has a honking big library list and be the
one person standing in the tracks waving a lantern at the train.
You're going to have this problem again and again as long as people insist
on using commands instead of API's. The API's to retrieve job information,
or retrieve job description information, didn't change. And I think that
the Change Job (QWTCHGJB) api is where you change a library list, (although
that one confuses me a little).
Rob Berendt
==================
A smart person learns from their mistakes,
but a wise person learns from OTHER peoples mistakes.
"Goodbar, Loyd
(AFS-Water Valley)" To:
"'MIDRANGE-L@midrange.com'" <MIDRANGE-L@midrange.com>
<LGoodbar@afs.bwaut cc:
o.com> Subject: RE: 250 libraries
again (was V3R1 QUSRTOOL, *PRDLOD)
Sent by:
owner-midrange-l@mi
drange.com
05/29/01 02:17 PM
Please respond to
MIDRANGE-L
I wonder why IBM didn't add an additional parameter to the RTVJOBA command
call LUSRLIBL (long user *LIBL). That way no existing code needed changing,
and forced you to modify the program only if you needed the additional
libraries. Just like any other enhancement should work. Lobotomies for all!
<stuff snipped>
DCL VAR(&USRLIBL) TYPE(*CHAR) LEN(275)
DCL VAR(&CMD) TYPE(*CHAR) LEN(6000)
RTVJOBA USRLIBL(&USRLIBL)
CHGLIBL LIBL(MYLIB1 MYLIB2 QGPL QTEMP)
/* Do my thing, sing my song, yada, yada, yada */
CHGVAR &CMD ('CHGLIBL LIBL(' *CAT &USRLIBL *TCAT ')')
CALL PGM(QCMDEXC) PARM(&CMD 6000)
<snip>
For this brilliant enhancement, we provide no award. The people who dreamt
this up have obviously already been to Mayo for their lobotomies.
I cannot believe that for the first time in 22 years, you have gone out of
your way to break certain users code, and I urge you to add the appropriate
support to the system to avoid this.
Al
Al Barsa, Jr.
Barsa Consulting Group, LLC
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---
As an Amazon Associate we earn from qualifying purchases.
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.
