I'm just completing the z/OS 2.2 ServerPac install, and everything is relatively smooth. I only defined one catalog, the new master. The only problem I had was with the new ZFS data sets. Using the SSA of Z220 appended to the standard names, gave me fits, as the ZFS format steps failed, stating the aggregate was not found. Turns out, the ZFS address space did not have access to Z220.**. The ServerPac generated job used the program IOEAGFMT, which causes the ZFS address space to do the work. I didn't see any RACF violations in the joblog of the job I submitted. But after a couple of hours I noticed the violations in syslog, and ultimately in the ZFS joblog. Updated my RACF data set profile for Z220.**, IPL'ed to cycle ZFS, and it worked fine.
--- [email protected] wrote: From: william janulin <[email protected]> To: [email protected] Subject: Re: ServerPac install Date: Tue, 27 Oct 2015 22:39:12 +0000 Oh, don't get me started on Serverpac. I am wrestling with it altering dataset names and defining paths. When I try anOMVS MOUNT on the renamed dataset, it does not find it.That plus the way they describe defining catalogs is ludicrous. It is hard to tell where you should use a user catalog as oppposed to the Master catalog. Needless to say, I have a PMR open with IBM ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN _____________________________________________________________ Netscape. Just the Net You Need. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
