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.

48 Hiperspace and DIV Libraries Chapter 2<br />

in<strong>for</strong>mation about the xlat option, see the IBM documentation <strong>for</strong> the z/<strong>OS</strong><br />

Network File System (NFS).<br />

Table 2.2 File Extensions <strong>for</strong> <strong>SAS</strong> Files in HFS Libraries<br />

Random Access<br />

Files<br />

Sequential Access<br />

Files<br />

<strong>SAS</strong> Member<br />

Type Description<br />

.sas7bdat .sas7sdat DATA <strong>SAS</strong> data file<br />

.sas7bndx .sas7sndx INDEX data file index; not treated by <strong>SAS</strong> software as a<br />

separate file<br />

.sas7bcat .sas7scat CATALOG <strong>SAS</strong> catalog<br />

.sas7bpgm .sas7spgm PROGRAM stored program (DATA step)<br />

.sas7bvew .sas7svew VIEW <strong>SAS</strong> data view<br />

.sas7bacs .sas7sacs ACCESS access descriptor file<br />

.sas7baud .sas7saud AUDIT audit file<br />

.sas7bfdb .sas7sfdb FDB consolidation database<br />

.sas7bmdb .sas7smdb MDDB multidimensional database<br />

.sas7bods .sas7sods <strong>SAS</strong>ODS output delivery system file<br />

.sas7bdmd .sas7sdmd DMDB data mining database<br />

.sas7bitm .sas7ssitm ITEMSTOR item store file<br />

.sas7butl .sas7sutl UTILITY utility file<br />

.sas7bput .sas7sput PUTILITY permanent utility file<br />

.sas7bbak .sas7sbak BACKUP backup file<br />

Hiperspace and DIV Libraries<br />

A hiperspace library is a temporary library in which each library block resides in a<br />

4K block in a z/<strong>OS</strong> hiperspace, a <strong>for</strong>m of electronic storage internal to the processor.<br />

The hiperspace facility can be exploited <strong>for</strong> permanent data by defining a<br />

data-in-virtual (DIV) library in which the library blocks are loaded into the hiperspace<br />

<strong>for</strong> processing and saved permanently in a VSAM linear data set. Hiperspace and DIV<br />

libraries have the same internal <strong>for</strong>mat as that of a direct access bound library, and<br />

<strong>SAS</strong> automatically re-uses free space within the library.<br />

Placing small to moderately sized <strong>SAS</strong> data sets in a hiperspace or DIV library can<br />

dramatically decrease the elapsed time required <strong>for</strong> <strong>SAS</strong> to process such data sets. The<br />

per<strong>for</strong>mance increase is usually at least as great as <strong>for</strong> direct access bound libraries<br />

allocated to VIO and is particularly significant <strong>for</strong> data sets that are accessed randomly.<br />

However, the actual per<strong>for</strong>mance benefit depends on various factors, including the<br />

amount of z/<strong>OS</strong> expanded storage available to the <strong>SAS</strong> session. These benefits occur by<br />

default <strong>for</strong> hiperspace libraries, but the <strong>SAS</strong> system option NOHSSAVE must be<br />

specified in order to achieve the increase in I/O throughput <strong>for</strong> DIV libraries. When<br />

specifying NOHSSAVE, design your <strong>SAS</strong> application carefully to ensure that updates<br />

stored in the DIV library can be re-created, which might be needed if certain types of<br />

abends occur. See “HSSAVE System Option” on page 457 <strong>for</strong> in<strong>for</strong>mation on the<br />

NOHSSAVE <strong>SAS</strong> system option.<br />

The number of hiperspace pages used <strong>for</strong> hiperspace and DIV libraries is governed by<br />

the HSLXTNTS, HSMAXPGS, and HSMAXSPC <strong>SAS</strong> system options. When a

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

Saved successfully!

Ooh no, something went wrong!