|SAS Companion for the OS/390 Environment|
The V8 and V8TAPE engines access V8 and V8TAPE SAS data libraries, respectively. Overview of the V8 and V8TAPE Engines summarizes useful information about these engines. The V8 engine supports direct access to individual members of a library, without having to search through the entire library sequentially. The V8TAPE engine supports sequential format data libraries on tape or on disk.
In SAS Version 8, a SAS library can exist as one of the following:
For general information about SAS library engines, see SAS Library Engines and SAS Language Reference: Dictionary.
|V8 Engine||V8TAPE Engine|
|Member Types Supported||ACCESS||ACCESS*|
|OS/390-Specific Options for Bound Libraries (specified in LIBNAME statement)||BLKSIZE=||BLKSIZE=|
|OS-390-Specific Options for HFS Libraries (specified In LIBNAME statement)||HFS||HFS|
|Portable Data Set Options||All||All except for COMPRESS=, INDEX=, and REUSE=|
|OS/390 Specific Data Set Options||n/a||FILEDISP=|
|OS/390-Specific System Options||BLKSIZE=||FILEDEV=|
|DCB Attributes for Bound Libraries||DSORG=PS||DSORG=PS|
|BLKSIZE=<value>, where <value> is in the range 4096-32,256 in increments of 512. The default is 6144.||BLKSIZE=<value>, where <value> is up to the maximum for your device
|LRECL=<value>, same as BLKSIZE=||LRECL=any value|
Limited support: you can use the V8TAPE engine
to move or transport
these member types, but you cannot use the V8TAPE engine to access the information
within these members.
**Including indexing and audit trail capabilities.
|Utilities That You Can Use with Direct Access Bound Libraries|
You can use standard OS/390 utilities such as IEBGENER, ISPF/PDF 3.3, or DF/HSM to copy or move SAS data libraries that were created with the V8 engine or with the V8TAPE engine. As long as the block size of the data library that you are copying is not changed and not greater than the track capacity of the target device, a V8 or V8TAPE data library may be transferred between unlike device types (for example, 3350 to 3380). This makes it easier to use DASD management software such as IBM's DF/HSM, FDR by Innovation Data Processing, or DMS/OS by Sterling Software.
|SAS Data Sets in HFS Libraries|
SAS data sets in HFS libraries are stored as individual HFS files within the directory that defines the library. The filename format is lowercase, with a period and filename extension provided by SAS.
|Random Access Files||Sequential Access Files||SAS Member Type||Description|
|.sas7bdat||.sas7sdat||DATA||SAS data file|
|.sas7bndx||.sas7sndx||INDEX||Data file index; not treated by the SAS System as a separate file|
|.sas7bpgm||.sas7spgm||PROGRAM||Stored program (DATA step)|
|.sas7bvew||.sas7svew||VIEW||SAS data view|
|.sas7bacs||.sas7sacs||ACCESS||Access descriptor file|
|.sas7bods||.sas7sods||SASODS||Output delivery system file|
|.sas7bdmd||.sas7sdmd||DMDB||Data mining database|
|.sas7bitm||.sas7ssitm||ITEMSTOR||Item store file|
|.sas7bput||.sas7sput||PUTILITY||Permanent utility file|
When SAS creates or updates a member of an HFS library, it places an exclusive lock on the entire file. The lock prevents other jobs, processes, or SAS sessions from reading, writing, or updating that file until the lock is removed. The write lock is analagous to a DISP=OLD data set enqueue.
When SAS reads an existing member of an HFS library, it places a read (or shared) lock on the entire file, which prevents other jobs, processes, or SAS sessions from updating the file, though it is still possible for others to read the file. The read lock is analagous to DISP=SHR data set enqueing.
Top of Page
Copyright 1999 by SAS Institute Inc., Cary, NC, USA. All rights reserved.