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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

System Options under z/<strong>OS</strong> FILEBLKSIZE(device-type)= System Option 429<br />

an explanatory message in the <strong>SAS</strong> log. <strong>SAS</strong> does not attempt to open the data set if the<br />

user ID does not have the proper authorization. However, the auditing requirements <strong>for</strong><br />

some installations cause unauthorized access attempts to be sent to the log <strong>for</strong> that<br />

site’s authorization facility. An attempt to open the data set must actually occur be<strong>for</strong>e<br />

a message is sent to the log of the authorization facility. Specify FILEAUTHDEFER <strong>for</strong><br />

unauthorized access attempts to be logged with the authorization facility at your site.<br />

The FILEAUTHDEFER option controls the checking of file authorization <strong>for</strong> external<br />

files and <strong>SAS</strong> data libraries. However, it only applies to files or libraries which reside in<br />

z/<strong>OS</strong> data sets. FILEAUTHDEFER does not apply to the processing of HFS files.<br />

FILEAUTHDEFER does not control the authorization checking <strong>for</strong> z/<strong>OS</strong> data sets<br />

that a <strong>SAS</strong> server accesses on behalf of a client. Such third-party authorization<br />

checking is per<strong>for</strong>med regardless of the FILEAUTHDEFER setting, and access failures<br />

are intercepted by <strong>SAS</strong> rather than resulting in abends or system errors. Nonetheless,<br />

FILEAUTHDEFER governs attempts by a <strong>SAS</strong> server to access a data set in a manner<br />

not authorized <strong>for</strong> the ID under which the server is running. However, the unauthorized<br />

access will be logged as having been attempted by the server ID, not the client ID.<br />

FILEBLKSIZE(device-type)= System Option<br />

Specifies the default maximum block size <strong>for</strong> external files<br />

Default: varies by device type<br />

Valid in: configuration file, <strong>SAS</strong> invocation, OPTIONS statement, OPTIONS window<br />

Category: File Control: EXTFILES<br />

PROC OPTIONS GROUP= EXTFILES<br />

z/<strong>OS</strong> specifics: all<br />

Syntax<br />

FILEBLKSIZE(device-type)=value<br />

device-type<br />

specifies any valid specific device number, as well as DASD, DISK, OTHER,<br />

SYSOUT, TAPE, and TERM.<br />

DASD or DISK<br />

sets values <strong>for</strong> the device types 2301, 2303, 2305-1, 2305-2, 2311, 2314, 2321, 3330,<br />

3330-1, 3340, 3350, 3375, 3380, 3390, and 9345.<br />

OTHER<br />

specifies the value that <strong>SAS</strong> uses when it is unable to determine the exact device<br />

type.<br />

SYSOUT<br />

sets values <strong>for</strong> SYSOUT data sets.<br />

TAPE<br />

sets values <strong>for</strong> the 2400, 3400, 3480, 3490E, and 3590 device types.<br />

TERM<br />

sets values <strong>for</strong> data sets that are directed to the terminal.

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

Saved successfully!

Ooh no, something went wrong!