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
performance of ssh vs. FTP, or the cpu cost of compression vs. bandwidth,
or noting that the archive file doubles the disk I/O; network IO might be
similar.
Solaris FTP has an extension supporting pipes, but not on the server end,
such as:
ftp other-lpar
put |"xpax -wvzf /u/directory/myarchive.pax -x os390 *" remote-archive
... presumably for the ssh-shy.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
