I know that others have pointed you to the place in the documentation that explicitly states that OVR/NOOVR is not supported via PARMLIB.
HOWEVER, I thought that I would mention that it is my understand that not only is this intentional, but that IBM has an "undocumented statement of direction" that they want to "kill off" NOOVR functionality. Personally, I think this is a mistake, but your post seems to indicate that you DO want to allow applications to do "overriding" - so this may not be a problem for you. If, OTOH, you do want to "enforce" some shop standards and have the ability to specify NOOVR in PARMLIB or other enhancements to LE run-time options, then I would suggest that you communicate this to IBM - via SHARE requirements or via your branch submitting a formal "REQUEST" "Liliane L. Clever" <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>... > Hello EveryOne, > > I just IPL Z/OS 1.7 on my test LPAR and am using the new CEEPRMxx PARMLIB > member. My first try was unsuccessful. The system did not like my OVR > parameters. We currently (under Z/OS 1.4) allow users to overwrite the > majority of our default settings and we need to continue to do so. I > noticed that none of the CEEPRMxx examples have any OVR parameter. Does it > mean that if I want to use OVR that I am forced to stick to the macros? or > if using CEEPRMxx is OVR understood? Could anybody please set me > straight. Right now I have my CEEPRMxx PARMLIB member without any OVRs and > all is well as far as the system is concerned. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
