DLINITDEFER

DLINITDEFER

Suppresses synchronization of VTOC entry at library creation time

Default: NODLINITDEFER

Valid in: configuration file, SAS invocation, OPTIONS statement, OPTIONS window

Category: File Control: SASFILES

OS/390 specifics: all

Syntax
Details

Syntax

DLINITDEFER | NODLINITDEFER

Details

Creating a new SAS data library normally causes the operating environment to close and reopen the library data set in order to update the DS1LSTAR (last record) value in the VTOC (volume table of contents). Updating the VTOC prevents data loss if the library is not properly closed, as may happen in the event of an OS/390 system crash. Unfortunately, at sites with a system exit or SMS management class that releases unused space (blocks/tracks) when a data set is closed(footnote 1), a U315 abend may occur when creating a new data library. The associated error message text is of the form:

ERROR: Physical I/O error on SAS data library '<data set name>',
       on the volume VVVVVV JOBNAME,STEPNAME,DA,DDNAME,OO-OP,
       OUT OF EXTENT,NNNNNNNNNNNNN,EXCP

Note: This error and abend does not occur when creating temporary libraries (except for the WORK SAS library) or when the library allocation request includes the subparameter RLSE (RELEASE) SPACE. In these cases, the new library data set is not initially closed and reopened to update the VTOC. [cautionend]

Specifying the system option DLINITDEFER prevents the error and abend by preventing the initial closing and reopening of the new library.

Specifying DLINITDEFER does involve a risk of data loss for newly initialized libraries that are not successfully closed due to an OS/390 system crash.

FOOTNOTE 1: For example, a management class that specifies partial release = yes immediate.

Chapter Contents
Previous
Next
Top of Page

Default:	NODLINITDEFER
Valid in:	configuration file, SAS invocation, OPTIONS statement, OPTIONS window
Category:	File Control: SASFILES
OS/390 specifics:	all