Question & Answer
Question
How to code a process SYSOPTS parameters for a z/OS to UNIX file transfer
Cause
Answer
When using sysopts datatype text, it is not necessary to code the UNIX sysopts because the default for UNIX is datatype text and xlate yes.
When sending a text file from z/OS to UNIX, use sysopts=":datatype=binary:xlate=yes:" to prevent the addition of the line feed control character (X'0A' ) . Use sysopts=":datatype=text:" to have the line feed inserted at the end of each record.
Example 1 - Using variable block records and how to code sysopts:
If the mainframe uses a process coded such as this one, the BDWs and RDWs will be retained when the file arrives on UNIX:
TOUNIX PROCESS SNODE=UNIX.NODE
SNODEID=(user,xxxx)
* this will create the binary vb type file on UNIX to use
* datatype vb to send back to z/OS
COPY -
FROM (PNODE DSN=USERID1.VARI.TEST
DCB=(DSORG=PS,RECFM=U)
DISP=(SHR)) -
TO (SNODE
DSN='/home/userid1/vari'
disp=rpl -
sysopts=":datatype=binary:")
Example 2: Coding sysopts for UNIX including strip blanks=no and xlate=no
Each parameter has a default, but if changing the default when sending to UINX each parameter is separated with a colon and then the entire contents are enclosed between double quotes:
sysopts=":datatype=binary:strip.blanks=no:xlate=no:"
sysopts=":datatype=text:strip.blanks=no:xlate=no:"
Historical Number
PRI43028
Product Synonym
Connect:Direct UNIX All Releases; Connect:Direct for z/OS All Releases
Was this topic helpful?
Document Information
Modified date:
17 December 2019
UID
swg21532364