On Mon, 11 Oct 2021 14:03:11 -0400, David Spiegel wrote:
>
>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.
>(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)
>
Open an SR with IBM Support. Insufficient information to solve a problem
ought to be an APARable defect. Almost certainly Allocation issued explicit
messages which pax intercepted and discarded.
This is a recurrent problem:
<https://bit.listserv.ibm-main.narkive.com/C0I1uLDC/bpxbatch-copy-to-mvs-ds-fsum6259>
>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
