| SAS Companion for the OS/390 Environment |
The V7 and V7TAPE engines access V7 and V7TAPE SAS data
libraries, respectively. Overview of the V7 and V7TAPE Engines
summarizes useful information about these engines.
The V7 engine and the V6 engine (updated for SAS Version
7) support direct access to individual members of a library, without having
to search through the entire library sequentially. The V7TAPE and V6TAPE engines
support sequential format data libraries.
Starting in Version 7, a SAS library can exist as on
of the following:
- Direct Access Bound Library
- A SAS data library in a direct access engine format (V7
or V6 engine) that is implemented with a single specially formatted OS/390
disk data set.
- Sequential Access Bound Library
- A SAS data library which exists in a sequential engine format
(V7TAPE or V6TAPE), implemented within a single OS/390 disk or tape data set.
- HFS Library
- Is a collection of SAS files with the same engine format
(V7 or V7TAPE) that are stored in a directory of the hierarchical file system
of UNIX System Services.
- Hiperspace Library
- Is a collection of SAS files with the same engine format
that are loaded into an OS/390 hiperspace, which is virtual storage backed
by available expanded storage.
The V6 and V6TAPE engines supplied with SAS Version
7 support full access (read, write, and create) to all SAS Version 6 data
libraries. The V6 and V6TAPE engines take the same options as the V7 and V7TAPE
engines, so the V7 and V7TAPE information in this chapter also applies to
the V6 and V6TAPE engines.
Note that data sets created under SAS Release 6.06 cannot be processed by
SAS Version 7 because their storage format differs from that used in subsequent
releases of Version 6. To make a SAS 6.06 data set available for processing
in Version 7, first use a later release of SAS Version 6 (6.07, 6.08, or 6.09)
to copy the 6.06 data set to a new data set, either in the same library or
in a new library. You can copy the new data set into a 6.06 library because
all library formats are supported in Version 7. The new data set automatically
receives the newer Version 6 format, which allows the new data set to be processed
by the V6 or V6TAPE engine in SAS Version 7.
The V5 and V5TAPE engines in SAS Version 7 support read-only
access to SAS Version 5 data libraries. For information on V5 and V5TAPE engines,
see Appendix 1 of
SAS Companion for the MVS Environment, Version 6, Second Edition
.
For information about the portable features of the SAS
that are supported by these engines, see
SAS Language Reference: Dictionary.
For general information about SAS library engines, see SAS Library Engines
and
SAS Language Reference: Dictionary.
Overview of the V7 and V7TAPE Engines
|
V7 Engine |
VTAPE Engine |
| Member Types Supported |
ACCESS |
ACCESS* |
| CATALOG |
CATALOG* |
|
DATA** |
DATA |
|
ISTORE |
ISTORE |
|
PROGRAM |
PROGRAM* |
|
VIEW |
VIEW* |
| OS/390-Specific Options for Bound Libraries (specified in LIBNAME statement) |
BLKSIZE= |
BLKSIZE= |
| DATACLAS= |
DATACLAS= |
| DISP= |
DISP= |
| DLTRUNCHK |
n/a |
| EXTEND |
EXTEND |
| HIPERSPACE |
n/a |
| LABEL= |
LABEL= |
| LIKE= |
LIKE= |
| LINEAR |
LINEAR |
| MGMTCLASS= |
MGMTCLASS= |
| PROMPT |
PROMPT |
| SPACE= |
SPACE= |
| STORCLAS= |
STORCLAS= |
| UNIT= |
UNIT= |
| VOLSER= |
VOLSER= |
| WAIT= |
WAIT= |
| OS-390-Specific Options for HFS Libraries (specified In LIBNAME statement) |
HFS |
HFS |
| PROMPT |
PROMPT |
| 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= |
| BLKSIZE()= |
FILESPPRI= |
| FILEDEV |
FILESPEC= |
| FILESPPRI= |
FILEUNIT= |
| FILESPEC= |
FILEVOL= |
| FILEUNIT= |
SYSPREF= |
| FILEVOL= |
TAPECLOSE= |
| SYSPREF= |
|
| DCB Attributes for Bound Libraries |
DSORG=PS |
DSORG=PS |
| RECFM=FS |
RECFM=U |
| 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
type. |
| LRECL=<value>, same as BLKSIZE= |
LRECL=any value |
| *Limited support: you can use the V7TAPE engine to
move
or transport these member types, but you cannot use the V7TAPE engine to access
the information within these members.
**Including indexing and audit trail capabilities. |
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
V7 engine or with the V7TAPE 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 V7 or V7TAPE 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 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.
- CAUTION:
- Do not change the filename extensions of SAS files.
Filename extensions determine how SAS accesses
files; changing them can cause unpredictable results.
![[cautend]](../common/images/cautend.gif)
The
following table describes SAS filename extensions.
Copyright © 1999 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
