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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

RELEASE Procedure<br />

Releases unused space at the end of a disk data set<br />

z/<strong>OS</strong> specifics: all<br />

Syntax<br />

PROC RELEASE DDNAME=file-specification ;<br />

Details<br />

Procedures under z/<strong>OS</strong> RELEASE Procedure 333<br />

PROC RELEASE can be used with most sequential or partitioned data sets, not just<br />

with a <strong>SAS</strong> data library that contains <strong>SAS</strong> data sets. However, PROC RELEASE is not<br />

supported <strong>for</strong>, and cannot be used to release unused space from, the following types of<br />

data sets:<br />

3 the <strong>SAS</strong> WORK data library<br />

3 extended partitioned data sets (PDSEs)<br />

3 ISAM or VSAM data sets<br />

3 multivolume <strong>SAS</strong> data libraries<br />

3 external multivolume data sets.<br />

If you delete some members from a <strong>SAS</strong> data library (using the DATASETS<br />

procedure, <strong>for</strong> example), you can use the RELEASE procedure to release the unused<br />

space at the end of the last member. You cannot use PROC RELEASE to release<br />

embedded space. That is, you can release only space that follows the “Highest Used<br />

Block,” as indicated by the CONTENTS or DATASETS procedure.<br />

In order to use PROC RELEASE on a <strong>SAS</strong> data library, the data library must be<br />

closed. If the library is open, <strong>SAS</strong> generates an error message. If you have assigned a<br />

libref to the data library and have used some members of that library in your <strong>SAS</strong><br />

session, the library will be open. To close it, issue a LIBNAME statement of the<br />

following <strong>for</strong>m <strong>for</strong> each libref currently assigned to the library:<br />

LIBNAME libref CLEAR;<br />

Then issue a new LIBNAME statement <strong>for</strong> the data library and immediately run<br />

PROC RELEASE. As an alternative to issuing a second LIBNAME statement, you can<br />

simply specify the data library’s name (enclosed in quotation marks) as the value of the<br />

DDNAME= option in the PROC RELEASE statement.<br />

In the control language, you can release unused space by using specifications such as<br />

SPACE=(,,RLSE) in the DD statement (in batch mode), or you can use the RELEASE<br />

operand of the TSO ALLOCATE command. However, releasing unused space with<br />

PROC RELEASE offers several advantages over methods provided by the operating<br />

environment. For example, with PROC RELEASE, the user, not the operating<br />

environment, controls when unused space is released. This advantage is especially<br />

applicable to TSO users.<br />

Another advantage of PROC RELEASE is that you can use PROC RELEASE options<br />

to specify exactly how many tracks you want to keep or release. There is no danger of<br />

erasing all or part of a data set because PROC RELEASE frees only unused space.<br />

PROC RELEASE returns unused space to the pool of available space on the disk<br />

volume. Once released, the space is still available <strong>for</strong> allocation to the data set,

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

Saved successfully!

Ooh no, something went wrong!