Mark Zelden wrote:
On Tue, 15 Apr 2008 18:12:56 -0700, Edward Jaffe
<[EMAIL PROTECTED]> wrote:
Sheesh! I've never understood what some sysprog's think is so "secret"
about the contents of parmlib. IMHO, UACC(NONE) for parmlib is more
draconian paranoia than anything else. But, that's a discussion for
another thread...
I'm sure we've done this before. Auditors are paranoid ("need to know basis").
Some passwords (JES2 NJE for example) may be kept in parmlib.
PARMLIB is similar to LNKLST in concept. It is a concatenation of
libraries, specified via PARMLIB statements in the LOADxx member of
IPLPARM, and accessed via the IEFPRMLB service.
LNKLST has three libraries that are always present on the concatenation.
The only always-present library for PARMLIB is SYS1.PARMLIB on the IPL
volume. If this library is not explicitly specified via PARMLIB
statements, it is added by the system at the end of the concatenation.
JES does not use PARMLIB. It reads its configuration parameters via a
hard-wired DD statement in its JCL procedure. The specification looks like:
For JES2:
//HASPPARM DD DISP=SHR,DSN=any.data.set.name(memname)
For JES3:
//JES3IN DD DISP=SHR,DSN=any.data.set.name(memname)
A *sequential* (DSORG=PS) data set might even work here. (Don't know.
Never tried it.)
Some system programmers like to elevate JES to the level of a BCP
component by putting its configuration parameters into a library on the
PARMLIB concatenation. That's fine. But, totally unnecessary. And, if
some sort of password might be specified therein, arguably inappropriate.
--
Edward E Jaffe
Phoenix Software International, Inc
5200 W Century Blvd, Suite 800
Los Angeles, CA 90045
310-338-0400 x318
[EMAIL PROTECTED]
http://www.phoenixsoftware.com/
----------------------------------------------------------------------
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
