On Mon, 11 Oct 2021 14:03:11 -0400, David Spiegel wrote: > >I am trying to PAX and TRS a zFS. > >When I run a Step to PAX followed by a Step to TRS, I get: >pax: //'MY.PAX': EDC5061I An error occurred when attempting to define a >file to the system. > "An error occurred" is woefully inadequate. Were other errors logged?
Why bother with TRS? Doesn't your "pax -z" achieve comparable compression? (Often a second compression expands the file. Or, pax without the -z, then TRS.) Time warp? A subsequent TRS step causes the earlier pax step to fail!? Does the initiator issue an ENQ because of TRS that somehow causes pax to fail? (Remember pax probably forks to a separate ASID.) (Is /src/ really mounted on root?) (It's regrettable that pax doesn't support a temp DSN.) >(I tried TAR and got the same result.) >When I run the PAX in one job and the TRS in another job, it works. >Has anyone seen this behaviour? (I'm on z/OS V2.4) > >Here is the JCL: >//STEP001 EXEC PGM=BPXBATCH >//STDOUT DD SYSOUT=* >//STDERR DD SYSOUT=* >//STDPARM DD * >SH pax -wzvf "//'MY.PAX'" /src/ >//STEP002 EXEC PGM=AMATERSE,PARM=SPACK >//SYSPRINT DD SYSOUT=* >//SYSUT1 DD DISP=SHR,DSN=MY.PAX >//SYSUT2 DD DISP=(,CATLG), >// UNIT=SYSALLDA, >// DATACLAS=DCZFSEXT, >// STORCLAS=SCZFSEXT, >// SPACE=(CYL,(1000,500),RLSE), >// RECFM=FB,LRECL=1024,BLKSIZE=27648, >// DSN=MY.PAX.TRS > -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
