Re: SFS - Moving File Pool Minidisks to Different Physical Devices
One can move an SFS filepool to different disks without a regeneration; been there, done that, more than once (from FBA to 9345, from 3380 to 9345 and from 9345 to 3390). But, never try it with COPYFILE: the SFS server has RESERVEd disks, such minidisks look like one with just one file, but they are special: the records in the fm6 file will never move: the classic CMS minidisk structures (directory, allocation bitmap, ...) are placed in front of the minidisk, then follow the file's data; with the DISKID function one can obtain the block nr of the first data block). SFS nor DB2 do use the normal CMS file APIs, but the fm6 file can be used with the classic CMS file API too. Now to move a minidisk to another disk-type: - Make a new minidisk with at least as much blocks as the old one - If you have installed the full DFSMS product (free of charge), use DFSMS COPY fmOldDisk vdevNewDisk (RESERVED - Without DFSMS, use these commands -- Issue the RESERVE command to make the new minidisk RESERVED -- ACCESS new and old minidisks -- use FILELIST to verify that the fm6 file on the new mdisk has as least as much records as on the old mdisk -- copy the records one by one PIPE fn ft fmOldDisk |SPEC RECNO 1 1-* 11 |FILEUPDATE fn ft fmNewDisk SFS is very happy with the result, DB2 is not. 2009/7/30 Sterling James ssja...@dstsystems.com Thanks, I missed this. This method would be less disruptive. *O'Brien, Dennis L dennis.l.o'br...@bankofamerica.comdennis.l.o%27br...@bankofamerica.com * Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 07/28/2009 05:36 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: SFS - Moving File Pool Minidisks to Different Physical Devices You can create a storage group 3, move your filespaces to it with FILESERV MOVEUSER, then disable storage group 2 with FILEPOOL DISABLE GROUP 2 EXCLUSIVE DETACH. You can then replace the old storage group 2 minidisks with 1-cylinder minidisks. This isn’t completely transparent, because FILESERV is a dedicated maintenance mode command, but it does allow you to move users in batches, without requiring an outage long enough to back up, format, and restore the entire pool. I have code in the SFS server PROFILE EXEC to look for a move list and process it at system IPL time. Dennis O’Brien That's one small step for (a) man, one giant leap for mankind. -- Neil Armstrong, 20 July 1969, Sea of Tranquility -- Please consider the environment before printing this email and any attachments. * This e-mail and any attachments are intended only for the individual or company to which it is addressed and may contain information which is privileged, confidential and prohibited from disclosure or unauthorized use under applicable law. If you are not the intended recipient of this e-mail, you are hereby notified that any use, dissemination, or copying of this e-mail or the information contained in this e-mail is strictly prohibited by the sender. If you have received this transmission in error, please return the material received to the sender and delete all copies from your system. * -- Kris Buelens, IBM Belgium, VM customer support
Re: SFS - Moving File Pool Minidisks to Different Physical Devices
Thanks, I missed this. This method would be less disruptive. O'Brien, Dennis L dennis.l.o'br...@bankofamerica.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 07/28/2009 05:36 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: SFS - Moving File Pool Minidisks to Different Physical Devices You can create a storage group 3, move your filespaces to it with FILESERV MOVEUSER, then disable storage group 2 with FILEPOOL DISABLE GROUP 2 EXCLUSIVE DETACH. You can then replace the old storage group 2 minidisks with 1-cylinder minidisks. This isn’t completely transparent, because FILESERV is a dedicated maintenance mode command, but it does allow you to move users in batches, without requiring an outage long enough to back up, format, and restore the entire pool. I have code in the SFS server PROFILE EXEC to look for a move list and process it at system IPL time. Dennis O’Brien That's one small step for (a) man, one giant leap for mankind. -- Neil Armstrong, 20 July 1969, Sea of Tranquility - Please consider the environment before printing this email and any attachments. This e-mail and any attachments are intended only for the individual or company to which it is addressed and may contain information which is privileged, confidential and prohibited from disclosure or unauthorized use under applicable law. If you are not the intended recipient of this e-mail, you are hereby notified that any use, dissemination, or copying of this e-mail or the information contained in this e-mail is strictly prohibited by the sender. If you have received this transmission in error, please return the material received to the sender and delete all copies from your system.
Re: SFS - Moving File Pool Minidisks to Different Physical Devices
You would undoubtedly need to regenerate the file pool to change disk types instead of simply formatting the disks. Regards, Richard Schuh From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Sterling James Sent: Tuesday, July 28, 2009 2:21 PM To: IBMVM@LISTSERV.UARK.EDU Subject: SFS - Moving File Pool Minidisks to Different Physical Devices Hello, After reading the manual, it looks as if you want to change the storage group 2 + minidisk to different physical devices or (FBA to ECKD), The process is back it up, yank out the old, replace with the new, format it, and then restore. I did not see a less of a slash-and-bum method like add new, quiesce old for new files, migrate to new, then remove old. Did I miss it? Thanks Please consider the environment before printing this email and any attachments. This e-mail and any attachments are intended only for the individual or company to which it is addressed and may contain information which is privileged, confidential and prohibited from disclosure or unauthorized use under applicable law. If you are not the intended recipient of this e-mail, you are hereby notified that any use, dissemination, or copying of this e-mail or the information contained in this e-mail is strictly prohibited by the sender. If you have received this transmission in error, please return the material received to the sender and delete all copies from your system.
Re: SFS - Moving File Pool Minidisks to Different Physical Devices
I thought SFS used standard CMS mindisks with a single mode 6 file on them. If so, just create a new minidisk that has at least the same amount of 4k blocks and copy the CMS file to the new minidisk. Then swap the directory entries. Note that this is a physical copy and can't be used for expanding a pool. But I thought I used it when migrating from 3380s to 3390s a long time ago. You can't just drop a pool or disk as the space has been mapped. You can tell SFS not to use those blocks anymore and create new pools on the new devices. The logical backup and restore should do the trick. Tom Duerbusch THD Consulting Schuh, Richard rsc...@visa.com 7/28/2009 4:55 PM You would undoubtedly need to regenerate the file pool to change disk types instead of simply formatting the disks. Regards, Richard Schuh From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Sterling James Sent: Tuesday, July 28, 2009 2:21 PM To: IBMVM@LISTSERV.UARK.EDU Subject: SFS - Moving File Pool Minidisks to Different Physical Devices Hello, After reading the manual, it looks as if you want to change the storage group 2 + minidisk to different physical devices or (FBA to ECKD), The process is back it up, yank out the old, replace with the new, format it, and then restore. I did not see a less of a slash-and-bum method like add new, quiesce old for new files, migrate to new, then remove old. Did I miss it? Thanks Please consider the environment before printing this email and any attachments. This e-mail and any attachments are intended only for the individual or company to which it is addressed and may contain information which is privileged, confidential and prohibited from disclosure or unauthorized use under applicable law. If you are not the intended recipient of this e-mail, you are hereby notified that any use, dissemination, or copying of this e-mail or the information contained in this e-mail is strictly prohibited by the sender. If you have received this transmission in error, please return the material received to the sender and delete all copies from your system.
Re: SFS - Moving File Pool Minidisks to Different Physical Devices
You can create a storage group 3, move your filespaces to it with FILESERV MOVEUSER, then disable storage group 2 with FILEPOOL DISABLE GROUP 2 EXCLUSIVE DETACH. You can then replace the old storage group 2 minidisks with 1-cylinder minidisks. This isn't completely transparent, because FILESERV is a dedicated maintenance mode command, but it does allow you to move users in batches, without requiring an outage long enough to back up, format, and restore the entire pool. I have code in the SFS server PROFILE EXEC to look for a move list and process it at system IPL time. Dennis O'Brien That's one small step for (a) man, one giant leap for mankind. -- Neil Armstrong, 20 July 1969, Sea of Tranquility From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Sterling James Sent: Tuesday, July 28, 2009 14:21 To: IBMVM@LISTSERV.UARK.EDU Subject: [IBMVM] SFS - Moving File Pool Minidisks to Different Physical Devices Hello, After reading the manual, it looks as if you want to change the storage group 2 + minidisk to different physical devices or (FBA to ECKD), The process is back it up, yank out the old, replace with the new, format it, and then restore. I did not see a less of a slash-and-bum method like add new, quiesce old for new files, migrate to new, then remove old. Did I miss it? Thanks Please consider the environment before printing this email and any attachments. This e-mail and any attachments are intended only for the individual or company to which it is addressed and may contain information which is privileged, confidential and prohibited from disclosure or unauthorized use under applicable law. If you are not the intended recipient of this e-mail, you are hereby notified that any use, dissemination, or copying of this e-mail or the information contained in this e-mail is strictly prohibited by the sender. If you have received this transmission in error, please return the material received to the sender and delete all copies from your system.
