This has been asked before,....here On Thu, 8 Jan 2009 16:34:41 +0100, Miklos Szigetvari Post by Miklos Szigetvari Hi We have a number of user ZFS datasets, in NON EXTENDED format , and already has reached the 4Gbyte limit Till now we have allocated a new extended format ZFS and copied into it via USS copytree. I would use PAX instead ... probably quicker.
I've used this rexx program to do copies from one file system to another in batch, but you certainly can do it interactively with the commands or running the rexx program in a shell. /* rexx */ /*=================================*/ fromdir = '/from_dir/' todir = '/service/' /*=================================*/ call syscalls 'ON' address syscall 'geteuid' uidval = retval say 'Current UID = 'uidval if uidval <> 0 then do say 'Attempting to set to UID=0' address syscall 'setreuid 0 0' uidval2 = retval if uidval2 <> 0 then do say 'Unable to set to UID=0' exit 12 end Else say 'New UID = 'uidval2 end address syscall 'chdir' fromdir say 'Copying files from' fromdir 'to' todir call bpxwunix 'pax -rwvCMX -p eW . ' todir Post by Miklos Szigetvari Can the REPRO do the same ? I wouldn't. Search the archives. I have repro'd a zfs to a new zfs and was able to mount and see the data, but someone else tried it (to go to extended) and it didn't work. Also remember a zfs is a formatted data set. Post by Miklos Szigetvari Can I restore a NON extended into an extended ? No. There is no "DATACLAS" to assign / convert to on logical restore. Also this from the DFSMSdss Storage Admin Reference: When performing a logical or physical data set restore operation of a VSAM extended-format data set, the target data set allocation must be consistent with the source data set allocation as follows: - If the source is an extended-format VSAM, then the target must be an extended-format VSAM. - If the source is a compressed VSAM KSDS, then the target must be a compressed VSAM KSDS. - If the source is an alternate index for an extended-format KSDS, then the target must be an alternate index for an extended-format KSDS. - The target control interval size must be equal to the source. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:***@zurichna.com z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to ***@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html Scott ford www.identityforge.com from my IPAD > On Jan 17, 2014, at 10:23 AM, "van der Grijn, Bart (B)" > <bvandergr...@dow.com> wrote: > > John, > >> I think you can make a single change to your REXX program >> >> paxRC=bpxwunix(wCMD,,"DD:PAX",stderr.) > > I tried that. In my original note: >> (I also tried it by specifying a ddname in the bpxwunix call instead of >> the stdout., but got a truncation error. I suspect that's because it >> exceeded the 2048 limit) > More specifically: > 317 *-* wCMD = "pax -w -X -z -x pax" aDir >> L> "pax -w -X -z -x pax" >> V> "/sap/D6B" >> O> "pax -w -X -z -x pax /sap/D6B" > 318 *-* "ALLOC DD(PAX) DSN('"aBackupDsn"') OLD release" >> L> "ALLOC DD(PAX) DSN('" >> V> "PSUSS.INTR.KD6BXS.USRSAP.A" >> O> "ALLOC DD(PAX) DSN('PSUSS.INTR.KD6BXS.USRSAP.A" >> L> "') OLD release" >> O> "ALLOC DD(PAX) DSN('PSUSS.INTR.KD6BXS.USRSAP.A') OLD release" > 319 *-* paxRC = bpxwunix(wCMD,,"DD:PAX",stderr.) >> V> "pax -w -X -z -x pax /sap/D6B" >> L> "" >> L> "DD:PAX" >> L> "STDERR." > DD:PAX truncation: rc=16 > Line too long > > The Usage note for BPXWUNIX: > STDOUT lines cannot exceed 2048 characters. > > Elardus, > >> Then I suspect the ALLOC command is not working 100% with that keyword >> combination. Could you try out >> TRACE in your REXX program to see what is happening when REXX is trying to >> execute ALLOC command? > > I put a LISTA STATUS in to verify the ALLOC worked and it shows the DDName in > question. > > > > I believe that the pax will work if I can force _BPX_SHAREAS=YES, but I don't > see how I can code this with an IKJEFT01 job step. The alternative would be > to run the rexx under USS to start with, but the way I read the manual, the > TSO ALLOC would then run under a different AS, so I assume my DDName would > still not be available (but I guess I should test that). > > Thanks, > Bart > > ---------------------------------------------------------------------- > 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
