On 10/19/10 11:15 AM, "Kris Buelens" <[email protected]> wrote:
> Wasn't there a sample EXEC to rename a filespace? Then you could do the > rename before the FILEPOOL UNLOAD/RELOAD. Yes (there's actually a command to do it now: FILEPOOL RENAME), but then you lose all the authorizations and aliases, and apparently you can't use the CMS RELOCATE command to move a directory between two filespaces, even in the same filepool -- or at least I can't construct the right command line for it to work. There's also no admin version of CREATE ALIAS to create an alias on behalf of a user, so you can't restore aliases in the new filepool after you've relocated the files. You can't use CP FOR, because SFS isn't a CP thing, and short of autologging the user and driving the whole process via SCIF (thus producing a billable event and a lot of CPU and I/O charged to the user), there's no way short of scheduling a hands-on session with each user and a big set of credits to their bills to make this work. Oh, and by the way, none of the FILEPOOL commands can be used in CMSBATCH, so you get to leave a privileged id logged in some where for however long it takes to run the move process. Just to make the process more fun. Grr. The SFSTOOLS package has a COPYUSER EXEC that Scott Nettleship wrote that seems to be a pretty good base for starting into writing my own tool. I'll just modify that -- at least I won't be completely starting from scratch. What a PITA. Clearly I need to add porting rsync to CMS to my list of things to be done if IBM is going to continue to impose more SFS/BFS stuff on us. -- db
