I do this, but I allocate the pax file before trying to write it. I also specify -x OS390 to be sure to get links and other attributes. Lloyd
Sent from AT&T Yahoo Mail for iPad On Monday, October 11, 2021, 4:00 PM, Paul Gilmartin <0000000433f07816-dmarc-requ...@listserv.ua.edu> wrote: On Mon, 11 Oct 2021 15:20:24 -0400, David Spiegel wrote: > >Every time I've used Windows as a "waystation", I've never had a problem >with TRS Files. > What are the attributes of your "pax -z" output data set? If RECFM=FB it ought to be comparably robust with BINARY transfers. Did you pre-allocate it? And it would save you the second job. And. I've extracted. pax -z output on a desktop by. piping through gunzip. Alas, TRSMAIN is UNIX-hostile. Wouldn't it be nice to pipe pax directly into TRSMAIN? (Cue Hobart Spitz.) Add Carmen's delay step. It won't solve your problem. But while it sleeps uou can display ENQs. -- gil ---------------------------------------------------------------------- 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
