I'll be the first to admit that I know just enough of what is in SYS1.PARMLIB to be dangerous, BUT . . .
What information could possibly be gleaned from reading PARMLIB that would require a knowledgeable auditor to insist on restricting read access (other than security by obscurity and sysprog/auditor job security)? Just curious, I don't plan on hacking anything. Peter -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
