> Why use "*" (which caused you problems previously) rather than "."
Not clear on the difference. See "not a UNIX professional." Did * cause me problems? I thought it was a file named -x that caused the problems. Deleting the file named -x sure solved the problem! I took care to put the archive outside of the archived path. Not THAT dumb. <g> > Fear of the unknown. Guilty as charged, your honor. Actually, how about "avoidance of unknown variables, seeing as how I already had enough on my plate"? Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Paul Gilmartin Sent: Friday, November 6, 2020 12:44 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: How best to copy all UNIX files one z/OS to another On Fri, 6 Nov 2020 10:58:46 -0800, Charles Mills wrote: >To close the loop on this, I ended up using >pax -wvzf /u/directory/myarchive.pax -x os390 * > Why use "*" (which caused you problems previously) rather than "." One hazard might be that the archive file lies within the hierarchy being archived. That's avoided if "*" is expanded by sh before pax opens the archive. >on the sending end, FTP STREAM/IMAGE, and >pax -rvf myarchive.pax >I eschewed the use of SSH because I am not super familiar with it and did >not want another variable. The negative of my method of course is disk >space: you need room for an additional 25% to 50% in the zFS file system, >beyond the actual files being moved. > Fear of the unknown. And for a one-off there's little point in comparing ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
