If you have been following the predecessor thread you know I have had difficulty trying to copy PDS members to a zFS directory in batch. After having layers of difficulties trying to run OPUTX in batch Gil suggested cp. I was unable to get cp to work -- or so I thought. I would run cp from BPXBATCH and simultaneously use WS_FTP to observe the results. (Yes, I know to hit Refresh.) The files were not showing up in WS_FTP so I concluded cp was failing. This morning I ran cp with -v and it looked like it was working, so I used ls to double-check what I was seeing in WS_FTP, and sure enough the files are there!
Here is my BPXBATCH JCL: // SET Q='''' // SET P0='sh cp -Uv "//''''USERID.SMPE.INSTJCL''''" ' // SET P4='/u/userid/smpe/SCZA551/INSTJCL' //* //CP EXEC PGM=BPXBATCH, // PARM=&Q.&P0.&P4.&Q //STDIN DD DUMMY //STDOUT DD SYSOUT=* //STDERR DD SYSOUT=* Here is what ls -l shows for one of the copied members. Why should this file be invisible to WS_FTP? -rw-rw-r-- 1 USERID RESTRICT 1226 Dec 13 11:25 $$README FWIW, in the next jobstep I pax -wvf the parent folder and these members show up in the pax archive. Does anyone have some insight into this mystery? Charles ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
