02.05.2013 Views

SAS(R) 9.1.3 Companion for z/OS

SAS(R) 9.1.3 Companion for z/OS

SAS(R) 9.1.3 Companion for z/OS

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Statements under z/<strong>OS</strong> FILE Statement 367<br />

<strong>SAS</strong> assigns values to the variables that are defined by these options when it opens the<br />

data set. It updates the values every time it opens a new data set in a concatenation.<br />

You can use these options with all standard external files under z/<strong>OS</strong>.<br />

DEVTYPE=variable<br />

defines a character variable (minimum length 24) that <strong>SAS</strong> sets to the device type.<br />

<strong>SAS</strong> obtains the device type by using the z/<strong>OS</strong> operating environment DEVTYPE<br />

macro. For more in<strong>for</strong>mation, see the IBM documentation <strong>for</strong> your operating<br />

environment.<br />

DSCB=variable<br />

defines a character variable (minimum length 96) that <strong>SAS</strong> sets to the Data Set<br />

Control Block (DSCB) in<strong>for</strong>mation from a non-VSAM data set. For more<br />

in<strong>for</strong>mation, see the IBM documentation <strong>for</strong> your operating environment.<br />

JFCB=variable<br />

defines a character variable (minimum length 176) that <strong>SAS</strong> sets to the Job File<br />

Control Block (JFCB). For more in<strong>for</strong>mation, see the IBM documentation <strong>for</strong> your<br />

operating environment.<br />

UCBNAME=variable<br />

defines a character variable (minimum length 3) that <strong>SAS</strong> sets to the unit name<br />

(device address), which is derived from in<strong>for</strong>mation in the unit control block (UCB).<br />

VOLUME=variable | VOLUMES=variable<br />

defines a character variable (with a minimum length of 6 characters) that <strong>SAS</strong><br />

sets to the tape VOLSER or the disk volume serial number. In the case of a<br />

multivolume file, the VOLUME= variable contains the concatenated volume serial<br />

numbers up to the length of the variable or the first 30 volumes, whichever is less.<br />

The value in the VOLUME= variable contains the volume serial number of the<br />

first data set in the concatenation when the file is opened. This serial number<br />

changes if you open a subsequent data set in the concatenation.<br />

VSAM Options <strong>for</strong> the FILE and INFILE Statements under z/<strong>OS</strong><br />

You can use the following options <strong>for</strong> VSAM files in the FILE statement and in the<br />

INFILE statement. (Unless otherwise indicated, the option can be used in both.)<br />

BACKWARD | BKWD<br />

causes <strong>SAS</strong> to read the VSAM data set backwards (INFILE only).<br />

BUFND=value<br />

indicates how many data buffers to use <strong>for</strong> the VSAM data set.<br />

BUFNI=value<br />

indicates how many index buffers to use <strong>for</strong> the VSAM data set.<br />

CONTROLINTERVAL | CTLINTV | CNV<br />

indicates that you want to read physical VSAM control interval records rather<br />

than logical records. This is typically used <strong>for</strong> diagnostic purposes (INFILE only).<br />

ERASE=variable<br />

defines a numeric <strong>SAS</strong> variable that you must set to 1 when you want to erase a<br />

VSAM record (INFILE only).<br />

FEEDBACK=variable | FDBK=variable<br />

defines a numeric variable that <strong>SAS</strong> sets to the VSAM logical error code. This is<br />

similar to the _FDBK_ automatic variable. When <strong>SAS</strong> sets the FEEDBACK<br />

variable, you must reset it to 0 in order to continue.<br />

GENKEY<br />

causes <strong>SAS</strong> to use the KEY= variable as the leading portion of a record’s key.<br />

VSAM retrieves the first record whose key matches the generic key (INFILE only).

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!