SAS(R) 9.1.3 Companion for z/OS

106 Host-Specific Options for UNIX System Services Files Chapter 5
All of the above specifications (x’15’, x’0C’, and x’25’) assume that the files use
an ENCODING= value whose short (12 byte) name is in the form open_ed-nnnn
and whose long (32 byte) name contains (OpenEdition), for example,
open_ed-1047 or Western(OpenEdition). These characters are automatically
transcoded to or from the file’s encoding if they are required by the ENCODING=
or LOCALE= options.
The last occurrence of FILEDATA= or TERMSTR= takes precedence.
Specification of one or the other of these options on a FILE or INFILE statement
takes precedence over the specification in a related FILENAME statement.
The full precedence order is as follows:
1 Specification of FILEDATA= or TERMSTR= on a FILE or INFILE statement.
2 Specification of FILEDATA= or TERMSTR= on a FILENAME statement.
3 Specification of FILEDATA= on a DD JCL statement when the file was
created by that DD statement
4 Implied by the RECFM= option in effect for the file.
The RECFM= option on the FILENAME, FILE, and INFILE statement can
imply the value assumed for the termination sequence. This implication is always
overridden by the presence of a TERMSTR= or FILEDATA= option for the file.
Here are the default values:
RECFM=V|D TERMSTR=NL is implied. (This is the default.)
RECFM=F TERMSTR=NONE is implied.
RECFM=P TERMSTR=NL implied, along with other formatting control
characters.
RECFM=N TERMSTR=NONE is implied.
Note: The FILEDATA= parameter on the DD JCL statement is only used by z/
OS when the file is being created by that JCL statement. For existing files, the
FILEDATA= parameter is ignored by z/OS, and SAS is informed of its value at file
creation time. Therefore, SAS cannot detect a change in the JCL. However, SAS
will honor the values of FILEDATA= or TERMSTR= specified on the FILENAME,
INFILE, or FILE statements when replacing an existing file or when reading a
file. R
CAUTION:
The combination of RECFM= and TERMSTR= provides much flexibility for reading and
writing many different file formats. It is possible to use these options in a way that
can produce a file that may be difficult to process in the future. For example, a
PRINT file may be created without record terminators, but this file would look strange
when printed on a printer or viewed in an editor. R