If I issue
put //hlq.seq.file //hlq.seq.file2
the result is I have a newly created HLQ.SEQ.FILE2 on the remote system
When I issue
put //hlq.pds.file //hlq.pds.file2
the result is that I have $HOME/mem1, $HOME/mem2, etc., on my remote system
It's not intuitive what I need to do to get an entire PDS from point a to point b
Moving an entire PDS to another LPAR
-
- Posts: 39
- Joined: Wed Feb 11, 2009 10:23 am
Re: Moving an entire PDS to another LPAR
Co:Z SFTP doesn't offer a way to transfer a PDS as a single file (unloading, etc). You can, of course, use XMIT to pack on the sending side and RECEIVE to unpack on the receiving side however.
PDS datasets are treated as pseudo directories, and you can transfer members using globbing:
put //hlq.local.pds(*) //hlq.remote.pds
PDS datasets are treated as pseudo directories, and you can transfer members using globbing:
put //hlq.local.pds(*) //hlq.remote.pds
-
- Posts: 39
- Joined: Wed Feb 11, 2009 10:23 am
Re: Moving an entire PDS to another LPAR
Thank you for the reply. Any particular release level for globbing to work?
A related question: Does the remote pds have to pre-exist or is there a way to have it allocated during the sftp session?
A related question: Does the remote pds have to pre-exist or is there a way to have it allocated during the sftp session?
David