RE: Modify SYSVAL QSYSLIBL

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