Using remote todsn and fromdsn clients requires that z/OS OpenSSH or IBM Ported Tools OpenSSH be available and configured on z/OS. z/OS V2R2 includes OpenSSH. Earlier versions of z/OS require IBM Ported Tools OpenSSH v1.2 (or later) to be installed. See the version of our Quick Install Guides matching your z/OS OpenSSH version for additional information.
The Dataset Pipes todsn and fromdsn commands may be used from any of the following z/OS Unix shell environments:
The TSO "OMVS" command
The BPXBATCH utility, running under MVS batch or TSO
Note:The BPXBATCH enhancement OA11699 significantly improves its usability.
The z/OS Unix Shell under a telnet or ssh console.
For more information on z/OS Unix, see:
The Dataset Pipes utilties open MVS datasets in "record mode" using the z/OS C library fopen() routine. For example:
fopen( name, mode);
"//dd:ddname"depending on whether BPXWDYN allocation keywords were used (Section D.4, “The z/OS BPXWDYN dynamic allocation service”).
"rb,type=record,noseek"- if reading (fromdsn)
"wb,type=record,noseek"- if writing (todsn)
"ab,type=record,noseek"- if appending (todsn -a)
Additional open mode options may be specifed by using the
The Dataset Pipes utilites read and write records using the z/OS C library
fwrite() routines. For more information on the capabilities of record-mode dataset
processing with the z/OS C library, see:
The Dataset Pipes utilities allow for flexible allocation of MVS Datasets through use of the
BPXWDYN text-based allocation service. If you specify allocation keywords,
either with the
-x option, or by using the
option, then a new system-assigned DDNAME will
be allocated with BPXWDYN and that DDNAME will be opened with Section D.3, “The z/OS C library fopen() routine”fopen().
You may use any allocation keywords defined by BPXWDYN, except the following:
DA(), DSN(), FI(), DD(), MSG(), or REUSE()(automatically supplied)
PATH() , PATHDISP(), PATHMODE(), PATHOPTS(), PATHPERM()
RTDDN, RTDSN, RTVOL(only works if called from REXX)
For more information on using BPXWDYN allocation keywords, see:
The Dataset Pipes utilities rely on the z/OS Unicode Conversion Service when possible, for codepage/character set translation.
This subsystem provides hardware-assisted high-performance codepage conversions services. This is the same service used by later versions of z/OS DB2, so many shops already have it configured in their environments. For z/OS 1.6 and later, the service is configured by default, with a starter set of codepage (CCSID) mappings.
For more information on configuring and customizing this subsystem:
When Unicode Conversion Services are not available, Dataset Pipes falls back to iconv for codepage translation