|
I'm kind of sorry I brought it up. Still I don't see this as a real problem. IBM hasn't broken anyone's code. Folks running legacy code can still run it as long as they recognize that a 25 library user library list is part of the legacy. Any solution IBM might offer would have to prevent the original code from bombing in the event that the user library list grew longer than the variable in the old program. This amounts to either allowing the list to be truncated or creating a mode bit to be carried through every aspect of work management to conditionally allow the list to be truncated. If I were to suggest any change it would be at the system level. Provide a system value that establishes 25 or 250 libraries in the user library list. If it were set at 250 the QUSRLIBL be open to more than 25 libraries. SBMJOB, CHGLIBL, etc. and JOBD commands would be opened accordingly. Those RTVJOBA programs using a 275 character variable would bomb the moment they encounter a job with more than 25 libraries. If the system value were set to 25 libraries the QUSRLIBL would have to first be trimmed to 25 libraries or less. The old RTVJOBA programs could run without fear of error, however, any job encountering a new CL statement, JOBD, or other reference to more than 25 libraries would bomb. No truncation would be permitted. If you've compromised your environment by running unsupportable software is it really a big deal to have to live with a 25 library user library list forever? I don't think IBM should put much development effort into letting this type of customer have their cake and eat it too. They have a bigger job to do just trying to remain (or become) competitive. -Jim James Damato Manager - Technical Administration Dollar General Corporation <mailto:jdamato@dollargeneral.com> -----Original Message----- From: York, Albert [mailto:albert.york@nissan-usa.com] Sent: Tuesday, May 29, 2001 5:05 PM To: 'MIDRANGE-L@midrange.com' Subject: RE: 250 libraries again (was V3R1 QUSRTOOL, *PRDLOD) From what I have been reading, it looks like this would be a problem only for those sites which don't have the ability to change their programs but will still insist on using more than 25 libraries in their library list. This sounds like a small group to me and I think IBM took the right approach. However, there is a simple solution. Create a version of RTVJOBD that does what is needed and put it in the library list above QSYS. With all the talent on this mailing list, I bet someone could come up with it in a couple of hours. Instead of a new value on the job description use the job switches. I don't think they are used for much else. Albert York -----Original Message----- From: barsa@barsaconsulting.com [SMTP:barsa@barsaconsulting.com] Sent: Tuesday, May 29, 2001 2:45 PM To: MIDRANGE-L@midrange.com Subject: RE: 250 libraries again (was V3R1 QUSRTOOL, *PRDLOD) I thought that I answered this before. A new job attribute should be created called User Library List Length (USRLIBLLEN ). '0' would be 25 and '1' would be 250. Jobs would get this job attribute when submitted from a job description, or it could be change with CHGJOB. The *JOBD would be populated from *SYSVAL at *JOBD creation time, not execution time. I have 3 sentences left! A technical nit: This change needs to be propagated into the System/38 environment. Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com Jim Damato <jdamato@dollargene To: "'MIDRANGE-L@midrange.com'" <MIDRANGE-L@midrange.com> ral.com> cc: Sent by: Subject: RE: 250 libraries again (was V3R1 QUSRTOOL, *PRDLOD) owner-midrange-l@mi drange.com 05/29/01 04:39 PM Please respond to MIDRANGE-L The point is that some folks with dinosaurs and legacies can't recompile. They either have lost source, don't have compilers, or are supporting packages that did not provide source and removed observability. I'm sure there are lots of users running applications where the support has lapsed or the provider has gone out of business. Al and others are suggesting that an OS/400 enhancement should "do no harm". In this situation the users' programs will crash due to an OS enhancement. I'm curious, Al. What should IBM have done? How would you have implemented an extension to the user library list? Please answer in 7 sentences or less :) -Jim James Damato Manager - Technical Administration Dollar General Corporation <mailto:jdamato@dollargeneral.com> -----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 +--- +--- | 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 +--- +--- | 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.
midrange.com
