We are migrating from a legacy file transfer product to Co:Z SFTP. We discovered jobs reading tape datasets and sending them to a Unix server.
I need to ask...are there any plans to support tape?
Thanks.
Tape dataset support
Tape datasets are already supported, so long as they are cataloged.
If z/OS is the client, you can allocate the tape dataset with a DD in the Co:Z SFTP job step or use dynamic allocation by referencing the dataset by name.
If z/OS is the server, you can use dynamic allocation.
When using dynamic allocation, you need to enable the (BPXWDYN) "mount" setting:
ls /+mount (from a remote client to a z/OS server)
- or -
lzopts mount (from the Co:Z sftp client)
also: the job/user must have the authority to mount via dynamic allocation.
If z/OS is the client, you can allocate the tape dataset with a DD in the Co:Z SFTP job step or use dynamic allocation by referencing the dataset by name.
If z/OS is the server, you can use dynamic allocation.
When using dynamic allocation, you need to enable the (BPXWDYN) "mount" setting:
ls /+mount (from a remote client to a z/OS server)
- or -
lzopts mount (from the Co:Z sftp client)
also: the job/user must have the authority to mount via dynamic allocation.
For reading a dataset (tape or otherwise), none of the BPXWDYN dynamic allocation settings are used; we just use the catalog.
For reading a tape dataset, you can use:
lzopts mount
put //A.B.C(+0) remotefilename
The dataset will have to be cataloged in order to resolve unit, etc.
However, since you are using the client, you could put a DD card (with whatever you like) in the jobstep, and then do:
put //DD:MYTAPE remotefilename
For reading a tape dataset, you can use:
lzopts mount
put //A.B.C(+0) remotefilename
The dataset will have to be cataloged in order to resolve unit, etc.
However, since you are using the client, you could put a DD card (with whatever you like) in the jobstep, and then do:
put //DD:MYTAPE remotefilename