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.

38 Compatibility Engines Chapter 2<br />

V7 has the same effect as V8.<br />

V6 creates a V6 <strong>for</strong>mat library.<br />

The following sequential engine library <strong>for</strong>mats can be read and written by <strong>SAS</strong><br />

System 9:<br />

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

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

V6TAPE library These libraries were created using the default sequential engine in<br />

V6 or using the V6TAPE compatibility engine under a later version<br />

of <strong>SAS</strong>.<br />

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

V8TAPE creates a V9TAPE library but does not allow creation of members<br />

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

V7TAPE has the same effect as V8TAPE.<br />

V6TAPE creates a V6TAPE <strong>for</strong>mat library.<br />

Long Format Names<br />

The V9 and V9TAPE engines support long <strong>for</strong>mat names in data sets. These long<br />

<strong>for</strong>mat names can have a maximum length of 32 bytes. <strong>SAS</strong> Version 8 and Version 7<br />

can process V9 and V9TAPE <strong>for</strong>mat libraries, including new data sets created using<br />

<strong>SAS</strong> System 9, provided the data sets do not have <strong>for</strong>mat names longer than 8 bytes. If<br />

you are using <strong>SAS</strong> System 9 to create data sets that you intend to process using <strong>SAS</strong><br />

Version 8 or Version 7, specify the V8 or V8TAPE engine, as appropriate, to ensure that<br />

the <strong>for</strong>mat names do not exceed 8 characters.<br />

Release 6.06 Format Data Sets<br />

Data sets that were created under <strong>SAS</strong> Release 6.06 cannot be read or written by<br />

<strong>SAS</strong> System 9 because their storage <strong>for</strong>mat differs from that used in subsequent<br />

releases of <strong>SAS</strong> Version 6. To make a <strong>SAS</strong> Release 6.06 data set available <strong>for</strong> processing<br />

in <strong>SAS</strong> System 9, first use a later release of <strong>SAS</strong> Version 6 (6.07, 6.08, or 6.09) to copy<br />

the <strong>SAS</strong> Release 6.06 data set to a new <strong>SAS</strong> data set, either in the same library or in a<br />

new library. (<strong>SAS</strong> System 9 can process libraries originally created by <strong>SAS</strong> Release 6.06<br />

if the members contained therein have been converted to the engine <strong>for</strong>mat associated<br />

with a later release of <strong>SAS</strong>, such as <strong>SAS</strong> Release 6.09.) The newly copied data set<br />

automatically receives the new <strong>SAS</strong> Version 6 <strong>for</strong>mat, which allows the new data set to<br />

be processed by the V6 or V6TAPE engine in <strong>SAS</strong> System 9.<br />

V5 and V5TAPE Engines<br />

<strong>SAS</strong> System 9 can read, but not update, libraries that were created in the V5 and<br />

V5TAPE <strong>for</strong>mats. Note that the V5 and V5TAPE engines cannot be specified on the<br />

LIBNAME statement. However, <strong>SAS</strong> will identify the correct engine to use with these<br />

libraries if no engine is specified.

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

Saved successfully!

Ooh no, something went wrong!