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.

424 DSRESV System Option Chapter 18<br />

Syntax<br />

DLTRUNCHK | NODLTRUNCHK<br />

Details<br />

The first time a <strong>SAS</strong> data library is accessed after it is assigned, <strong>SAS</strong> compares the<br />

external count of library blocks from the z/<strong>OS</strong> data set label with the internal count of<br />

library blocks from the library itself. If the external count is less, the library may be<br />

truncated, or the external count may merely be in error. In either of these cases<br />

(apparent or actual truncation), if the DLTRUNCHK option is in effect, <strong>SAS</strong> issues an<br />

error message and refuses to process the library in any manner. If NODLTRUNCHK is<br />

in effect, <strong>SAS</strong> attempts to continue processing; however, if the library is truncated, no<br />

write access is allowed. If you specify NODLTRUNCHK, <strong>SAS</strong> also attempts to correct<br />

the external count, if possible, when closing the library or when extending the library to<br />

a new volume. However, this repair is not possible if the library is actually truncated or<br />

the <strong>SAS</strong> session does not have write access to the library.<br />

DLTRUNCHK is the default setting, and it is recommended <strong>for</strong> all production<br />

applications <strong>for</strong> the following reasons:<br />

3 Attempting to read or update a library that is truncated might result in the <strong>SAS</strong><br />

session terminating with an abend. There<strong>for</strong>e, if you are running a <strong>SAS</strong>/SHARE<br />

server, it is recommended that you specify DLTRUNCHK to prevent the server<br />

from terminating <strong>for</strong> that reason.<br />

3 If you use NODLTRUNCHK, there is a small risk that <strong>SAS</strong> will accept as valid<br />

any residual data on a disk that is from a deleted z/<strong>OS</strong> data set.<br />

DSRESV System Option<br />

Requests exclusive use of shared disk volumes when accessing partitioned data sets on shared<br />

disk volumes<br />

Default: NODSRESV<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 />

DSRESV | NODSRESV<br />

DSRESV<br />

reserves the device, which prevents other processors from accessing the volume on<br />

which the partitioned data set resides.<br />

NODSRESV<br />

enqueues the resources that are defined by the operating environment.

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

Saved successfully!

Ooh no, something went wrong!