IS this zFS level thing a z/OS 2.2 and above issue? Or should I have noticed when moving to z/OS 2.1 from 1.13
> -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Jousma, David > Sent: Wednesday, June 13, 2018 8:56 AM > To: [email protected] > Subject: Re: How to move to zFS V5 - painlessly > > No. I converted all of our filesystems (except SMPE controlled filesystems) > via the command on all of our systems. Was very quick, chose specific path > hierarchies to do at a time. For all my z/OS supplied ZFS filesystems, I > converted my "maintenance" environment, and then let my cloning process > move it out at maintenance time since all of those are mounted read only, > and didn’t want to chance making them RDWR to do that live. > > zfsadm convert -path /your/path/names > > The IOEPRMxx entry is just a catchall for me, in case one of my team mates > allocates or has older filesystems laying around that are not normally > mounted anyway. > > ___________________________________________________________ > ______ > Dave Jousma > Manager Mainframe Engineering, Assistant Vice President > [email protected] > 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f > 616.653.2717 > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Blake, Daniel J [CTR] > Sent: Wednesday, June 13, 2018 11:48 AM > To: [email protected] > Subject: Re: How to move to zFS V5 - painlessly > > **CAUTION EXTERNAL EMAIL** > > **DO NOT open attachments or click on links from unknown senders or > unexpected emails** > > I used the IOEFSUTL to convert in our sand box. Worked well and the largest > zFS only took 33 seconds of batch runtime. > > Next up is a system covered under SLAs and I don't want it down for an > extended period of time while I run the batch jobs for 200+ aggregates. Did > you see an extended IPL time using the converttov5 in IOEPRMxx process? > > TIA, > > ;-D an > > > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Jousma, David > Sent: Wednesday, June 13, 2018 11:40 AM > To: [email protected] > Subject: Re: How to move to zFS V5 - painlessly > > Use the converttov5=on option in IOEPRMxx > ___________________________________________________________ > ______ > Dave Jousma > Manager Mainframe Engineering, Assistant Vice President > [email protected] > 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f > 616.653.2717 > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Jantje. > Sent: Wednesday, June 13, 2018 11:27 AM > To: [email protected] > Subject: Re: How to move to zFS V5 - painlessly > > **CAUTION EXTERNAL EMAIL** > > **DO NOT open attachments or click on links from unknown senders or > unexpected emails** > > On Wed, 13 Jun 2018 09:37:18 -0500, Jantje. <[email protected]> > wrote: > > > > >find . -type d -exec zfsadm convert -path {} \; > > > >comes pretty darn close. > > O, if anyone has a suggestion on how to get the not-mounted-automount file > systems (those are missed by the find command, because they are not > mounted, obviously) mounted without having to name them all by hand, I'd > love to hear. > > Jantje. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > [email protected] with the message: INFO IBM-MAIN **CAUTION > EXTERNAL EMAIL** > > **DO NOT open attachments or click on links from unknown senders or > unexpected emails** > > This e-mail transmission contains information that is confidential and may be > privileged. It is intended only for the addressee(s) named above. If you > receive this e-mail in error, please do not read, copy or disseminate it in > any > manner. If you are not the intended recipient, any disclosure, copying, > distribution or use of the contents of this information is prohibited. Please > reply to the message immediately by informing the sender that the message > was misdirected. After replying, please erase it from your computer system. > Your assistance in correcting this error is appreciated. > > > ---------------------------------------------------------------------- > 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 **CAUTION > EXTERNAL EMAIL** > > **DO NOT open attachments or click on links from unknown senders or > unexpected emails** > > This e-mail transmission contains information that is confidential and may be > privileged. It is intended only for the addressee(s) named above. If you > receive this e-mail in error, please do not read, copy or disseminate it in > any > manner. If you are not the intended recipient, any disclosure, copying, > distribution or use of the contents of this information is prohibited. Please > reply to the message immediately by informing the sender that the message > was misdirected. After replying, please erase it from your computer system. > Your assistance in correcting this error is appreciated. > > > ---------------------------------------------------------------------- > 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
