Mark Vollmer wrote on 09/21/2005 10:06:45 AM: > > 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? >
The comment about letting IPCS allocate the parmlib concatenation being a good thing was not specifically directed at your situation. You and I are treated as end-users on our production z/OS systems, and using ddname IPCSPARM is the way that you and I need to personalize parmlib member access. Many other IPCS users are in a support capacity where their systems have copies of IPCS for multiple release levels of z/OS and major products. They, too, need to use IPCSPARM as well as the TSOLIB command to access the right level of IPCS for their needs. The folks supporting your system who screen dumps produced by the system are the ones for whom letting IPCS use the parmlib concatenation tends to be the right thing. Bob Wright - z/OS MVS Service Aids ---------------------------------------------------------------------- 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
