Yeah, I was really surprised by it too. Apparently, it's related to the way the network configurator part stores the configurations (or so IBM told me in a PMR, and their suggestion was to change the ownership of the filesystem).
On Fri, Dec 2, 2022 at 2:16 PM Mark Zelden <[email protected]> wrote: > On Fri, 2 Dec 2022 13:15:26 -0500, Justin Esposito < > [email protected]> wrote: > > >A little tip: > > > >If you're moving your z/OSMF instance around from lpar to lpar with the > >same userdir (default /global/zosmf), it's not a bad idea to change the > >owning system of said filesystem with a chmount -D. I've run into some > >performance issues when the owning lpar of the filesystem is not the same > >as the one running the started task, specifically with the network > >configurator. > > > > Even with RWSHARE active for the file systems or defaulted in the zFS > parms? Normally > zFS file system ownership shouldn't be a performance issue these days for > R/W file systems > and never was for R/O file systems. > > Regards, > > Mark > -- > Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS > ITIL v3 Foundation Certified > mailto:[email protected] > Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
