I don't have a good answer for you, sorry, but adding support for DATACLASS is on our short list to address before the root filesystem grows beyond 4 GB.
Kurt Quackenbush -- IBM, z/OS SMP/E and z/OSMF Software Management Chuck Norris never uses CHECK when he applies PTFs. -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Michael Babcock Sent: Wednesday, October 19, 2022 8:28 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [EXTERNAL] Re: z/OSMF PSWI Another issue. PSWI uses GIMUNZIP which invokes DFSMSDSS via API. We make all of our ZFS data sets VSAM Extended (EA and REQUIRED). Yes, this isn't necessary I know but we do have a few that are larger than the 4GB limit. Anyway, DFSMSDSS does not invoke the DATACLASS, so there is no way to assign a DATACLASS. So how in the world do we make our ZFS data sets VSAM Extended? What's going to happen when the root filesystem grows beyond the 4 GB limit in the future? So far z/OSMF PSWI is not helping. First, I couldn't select a Target system but tell it to use a different, existing master cat (like we could with ServerPac), now this? On 10/6/2022 10:15 AM, Kurt J. Quackenbush wrote: > As I understand your scenario, you have two z/OS systems, a driving system > (call it A) where the z/OSMF server is running and a target system (call it > B), and you want to install z/OS 2.5 into the existing master catalog for > system B. Currently you have selected A as the target system for the > deployment. Unfortunately Software Management does not have support for > installing into an existing alternate master catalog. Yes it can install > into the driving system's master catalog, or create and install into a brand > new master catalog, but it does not install into an existing master catalog > that is not the driving system's active master catalog. As a circumvention, > is B IPL’d? Is a z/OSMF server running on B? If so, then define system B in > the z/OSMF Systems task and select it as the target system for the deployment > instead of selecting A. > > Kurt Quackenbush -- IBM, z/OS SMP/E and z/OSMF Software Management > > Chuck Norris never uses CHECK when he applies PTFs. > > -----Original Message----- > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On > Behalf Of Michael Babcock > Sent: Wednesday, September 28, 2022 3:40 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: [EXTERNAL] Re: z/OSMF PSWI > > Okay, more issues. As I stated, we use a permanent maintenance > volume/system. With ServerPac, we could define an SSA and have the SYSRES > datasets cataloged in our maintenance systems master cat then ServerPac would > allocate the dataset using an SSA. later it would generate jobs to remove the > SSA. > > Unless I’m missing something, this doesn’t seem possible with z/OSMF because > the Modify Catalog section doesn’t let us change the master cat > (even though it says it will). The only way I see around that is to > rename the SYSRES dataset with the SSA. Of course we would then need to > create our own rename job to remove the SSA. Jeez, COME ON PEOPLE! > > We were told z/OSMF would provide the same functionality as ServerPac but I > guess not. > > On Wed, Sep 21, 2022 at 3:28 PM Michael Babcock > <bigironp...@gmail.com> > wrote: > >> We are installing z/OS 2.5 via z/OSMF and are using the Modify >> Deployment screens. We can easily change the volumes, HLQs, etc, but >> wanted to modify the Primary and/or secondary allocation and don’t see a way >> to do that. >> >> We have a case opened with IBM and have been told there is no way to do >> that and no plans for it in the future. What? We could do that with >> the ServerPac, why not with z/OSMF? I was under the impression that >> z/OSMF would provide most functions that ServerPac provided. >> >> So, is that capability not going to be provided? >> >> >> -- >> Michael Babcock >> OneMain Financial >> z/OS Systems Programmer, Lead >> > -- > Michael Babcock > OneMain Financial > z/OS Systems Programmer, Lead > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
