|
If you attempt to "run" a command from QSYSV4R4M0, you get a diagnostic message CPD0118, and an escape message of CPF0001. My thought is that if you attempted to put this library higher in your library list that QSYS, you likely might crater your system. Anyone have thoughts???? 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 "jt" <jt@ee.net> Sent by: To: <midrange-l@midrange.com> midrange-l-admin@mi cc: drange.com Subject: RE: Modify SYSVAL QSYSLIBL 12/16/01 11:59 PM Please respond to midrange-l Frank, You wrote, "IBM should prevent the backwards compatibility libs getting into the SYSLIBL." Ya... I'd say I agree with that...! Can users implement this through security if IBM doesn't. RVKOBJAUT, but then you need a program that adopts, to run compiles... Kludge...? (Which I pronounce kloooodge...;-) jt | -----Original Message----- | From: midrange-l-admin@midrange.com | [mailto:midrange-l-admin@midrange.com]On Behalf Of | Frank.Kolmann@revlon.com | Sent: Sunday, December 16, 2001 11:32 PM | To: midrange-l@midrange.com | Subject: Modify SYSVAL QSYSLIBL | | | >I have not done this but I wonder what happens if | >I modify QSYSLIBL to put QSYSV4R4M0 at the top, | >on an OS at V4R5. Warning do not be tempted to try. | >Frank Kolmann | | | >>DON'T DO IT. QSYSV4R4M0 is a library provided for *PRV compilations | only. | >>Al | >>Al Barsa, Jr. | | >I, and I'm sure Jerry too, agree completely. | > | >Didn't catch the REASON behind the question... Maybe there's another way | to | >accomplish this, via LPAR. But don't know the original problem that was | >being addressed. | > | >jt | | I dont have a reason as such. One of our programmers | modified a jobs *LIBL (system portion) with CHGSYSLIBL. | Could not even do a SYS REQ cancel, or SIGNOFF. | It is simply something that is very easy to do and | I suspect will disable the AS400. | IBM should prevent the backwards compatibility libs | getting into the SYSLIBL. | | Frank Kolmann _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
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.