Robert Wright wrote:
Mark Vollmer wrote on 09/20/2005 10:00:41 AM:
My system did not allocate IPCSPARM for my IPCS sessions. It appeared
to get its various IPCS parm information from another DD.
IPCSPARM is optional and best omitted if you're looking at dumps from the
system on which you're running or another system at the same release and
service level. If IPCSPARM is not allocated when you start your IPCS
session, IPCS allocates an arbitrary ddname to the system parmlib
concatenation, reads the needed parmlib members, and frees the ddname
before commencing the main part of the session. The parmlib concatenation
allows your installation to keep its parmlib members, possibly including
BLSCUSER, separate from those that are replaced when you go from one system
level to another, and two DYNALLOCs these days don't hurt responsiveness
like they might have a few years ago.
Bob Wright - z/OS MVS Service Aids
Since I cannot edit a BLSCUSER member in the SYS1.PARMLIB dataset
without extra security authorization, I don't see any other alternative.
I tried just putting BLSCUSER (pds with a single member) in the the
IPCSPARM allocation, but that seemed to prevent the system from finding
other PARMLIB members it needed. That problem only went away after I
added the SYS1.PARMLIB to the concatenation of the IPCSPARM dataset list.
Do you have an alternative suggestion that does not require altering
system datasets?
-Mark Vollmer
----------------------------------------------------------------------
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
