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.

Using <strong>SAS</strong> Data Libraries Compatibility Engines 37<br />

Note: Use BASE as the engine name if you write programs that create new <strong>SAS</strong><br />

data libraries and you want to create the data libraries in the latest available <strong>for</strong>mat.<br />

In <strong>SAS</strong> System 9, BASE is an alias <strong>for</strong> V9, and it will be an alias <strong>for</strong> newer engines in<br />

subsequent releases of <strong>SAS</strong>. R<br />

The V9TAPE Engine<br />

The sequential engine <strong>for</strong> <strong>SAS</strong> data libraries is V9TAPE. The V9TAPE engine creates<br />

sequential libraries in the V9TAPE <strong>for</strong>mat, and it can also read and write libraries<br />

created using the V7TAPE and V8TAPE engines.<br />

The V9TAPE engine provides a way to store files on devices such as tape that do not<br />

support random access. Some of the uses of the V9TAPE engine on z/<strong>OS</strong> include<br />

3 archiving <strong>SAS</strong> files to tape <strong>for</strong> long-term storage.<br />

3 transporting <strong>SAS</strong> files between your z/<strong>OS</strong> system and another z/<strong>OS</strong> system or<br />

CMS system via tape.<br />

3 sending <strong>SAS</strong> data, via a pipe connection, <strong>for</strong> immediate consumption by another<br />

job running in parallel.<br />

In contrast to the V9 engine, V9TAPE has the following limitations:<br />

3 does not support indexing, compression of observations, or audit trail capabilities<br />

3 does not support direct access to individual observations (using the POINT= or<br />

KEY= options in the SET or MODIFY statements)<br />

3 provides limited support <strong>for</strong> the following types of <strong>SAS</strong> library members: ACCESS,<br />

CATALOG, PROGRAM, and VIEW. You can move or transport these member<br />

types, but you cannot use the V9TAPE engine to access the in<strong>for</strong>mation within<br />

these members.<br />

Note: Use TAPE as the engine name if you write programs that create new <strong>SAS</strong><br />

data libraries and you want to create the data libraries in the latest available <strong>for</strong>mat.<br />

In <strong>SAS</strong> System 9, TAPE is an alias <strong>for</strong> V9TAPE, and it will be an alias <strong>for</strong> newer<br />

sequential engines in subsequent releases of <strong>SAS</strong>. R<br />

Compatibility Engines<br />

<strong>SAS</strong> provides various compatibility engines <strong>for</strong> the purpose of processing libraries<br />

that were created by previous versions of <strong>SAS</strong>. The type of engine that should be used<br />

depends on the engine <strong>for</strong>mat of the library. In most cases, <strong>SAS</strong> can detect the engine<br />

<strong>for</strong>mat and automatically select the appropriate engine to use. However, if you are<br />

using <strong>SAS</strong> System 9 to create a new library or new members that will be processed by a<br />

prior version of <strong>SAS</strong>, you need to explicitly specify (on a LIBNAME statement or<br />

function) an engine that creates a library or members in a <strong>for</strong>mat that can be processed<br />

by the prior version of <strong>SAS</strong>.<br />

The following base engine library <strong>for</strong>mats can be read and written by <strong>SAS</strong> System 9:<br />

V9 library Libraries created by the default base engine in V8 or V7 are<br />

identified by <strong>SAS</strong> System 9 as being in V9 <strong>for</strong>mat.<br />

V6 library These libraries were created using the default base engine in V6 or<br />

using the V6 compatibility engine under a later version of <strong>SAS</strong>.<br />

Specifying one of the compatibility engines below has the indicated effect:<br />

V8 creates a V9 library but does not allow creation of members with<br />

<strong>for</strong>mat names longer than 8 bytes.

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

Saved successfully!

Ooh no, something went wrong!