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


  • Subject: RE: 250 libraries again (was V3R1 QUSRTOOL, *PRDLOD)
  • From: "Goodbar, Loyd (AFS-Water Valley)" <LGoodbar@xxxxxxxxxxxxxx>
  • Date: Tue, 29 May 2001 16:27:39 -0400

Title: RE: 250 libraries again (was V3R1 QUSRTOOL, *PRDLOD)
Not at all. You would not be required to use more than 25 libraries. I'm viewing this similar to an extension to an API. If you don't need the new fields, don't use them, but yes, you must do something special to use new fields.
 
If you have more than 25 libs in your library list, you need to revisit the CL programs ANYWAY to change the receiver variable size. You either need to have a SHORT/LONG type parameter, or separate parameters for the "original" library list and the "expanded" library list. Either way, code needs to be changed.
 
If you code in RPG/III, you accept that file names are 8 positions in the F-spec. When you migrate code to RPG/IV, did you complain that you now have 10 positions in the file? Forward compatibility, please.
 
You still only need to "fix" your code when you breach the 25 library limit.
 
Loyd
-----Original Message-----
From: Leland, David [mailto:dleland@Harter.com]
Sent: Tuesday, May 29, 2001 3:10 PM
To: 'MIDRANGE-L@midrange.com'
Subject: RE: 250 libraries again (was V3R1 QUSRTOOL, *PRDLOD)

So, what you're saying is that if you changed the user portion of your library list to have more than 25 libraries in it, you'd be satisfied to have an existing program only retrieve the first 25 using the RTVJOBA command?  All for the sake of not having to recompile your CL program?  Sheesh.  Think of the mess that could cause?

As I mentioned before, you only need to fix your CL programs if you start using more than 25 libraries in your library list.

Dave

-----Original Message-----
From: Goodbar, Loyd (AFS-Water Valley) [mailto:LGoodbar@afs.bwauto.com]
Sent: Tuesday, May 29, 2001 2:18 PM
To: 'MIDRANGE-L@midrange.com'
Subject: RE: 250 libraries again (was V3R1 QUSRTOOL, *PRDLOD)


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


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.