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.

340 SOURCE Procedure Chapter 16<br />

3 route the members of a library to other programs <strong>for</strong> processing. By default, PROC<br />

SOURCE generates records <strong>for</strong> the IBM utility, IEBUPDTE, which reloads an<br />

unloaded data set.<br />

3 create a sequential, or unloaded, version of the library’s directory records.<br />

3 construct an unloaded data set from a library. The unloaded data set is suitable<br />

<strong>for</strong> reloading by IEBUPDTE or other source library maintenance utilities,<br />

including the ability to recognize and properly handle aliases.<br />

Using the SOURCE procedure, a source library can be copied into a sequential tape<br />

or disk data set to create either a backup or a manually transportable copy of the<br />

source data. This copy is called an unloaded data set; it consists of 80-byte records that<br />

contain the source data and the control in<strong>for</strong>mation that are needed to restore the<br />

source to its original organization. When an unloaded data set is restored by the proper<br />

utility to a device that will support the data in their original <strong>for</strong>m, the data is<br />

reconstructed, or loaded.<br />

An advantage of having an unloaded data set is that one or more members can be<br />

retrieved without reloading the entire library.<br />

PROC SOURCE has several advantages over IBM’s IEBPTPCH utility. With PROC<br />

SOURCE you can<br />

3 list members in alphabetical order<br />

3 select members by specifying a wildcard or range<br />

3 list the number of records in each member<br />

3 list each member on a new page<br />

3 produce an unloaded version of the library that can be ported to some other host<br />

systems.<br />

The model-control-statements in the FIRST, LAST, BEFORE, and AFTER<br />

statements are usually either utility or job control statements, depending on the<br />

destination given by the OUTDD= option in the PROC SOURCE statement.<br />

PROC SOURCE Statement<br />

PROC SOURCE ;<br />

The following options are used in the PROC SOURCE statement:<br />

DIRDD=file-specification<br />

specifies either the fileref or physical file name of the output data set to which<br />

PROC SOURCE writes a sequential, unloaded <strong>for</strong>m of the PDS directory. Each<br />

directory record is written into one 80-byte record. Records are left-aligned and<br />

padded on the right with blanks. If specified, the fileref must match the reference<br />

name that was used in the FILENAME statement, FILENAME function, JCL DD<br />

statement, or TSO ALLOCATE command that allocated the output data set.<br />

Note: The SELECT and EXCLUDE statements have no effect when the<br />

DIRDD= option is specified. R<br />

INDD=file-specification<br />

specifies the fileref or the physical file name of an input PDS that contains 80-byte<br />

fixed-length records. The fileref, if specified, must match the reference name that<br />

was specified in the FILENAME statement, FILENAME function, JCL DD<br />

statement, or TSO ALLOCATE command that allocated the input library. If the<br />

INDD= option is not specified, the default fileref is SOURCE.<br />

If OUTDD is specified, then the RECFM of the INDD file must be either F or<br />

FB. The fileref may not refer to a concatenation of data sets. If it does, then an<br />

error message is generated. If the member names in the INDD file are<br />

nonstandard, then specify FILEEXT=ASIS in an OPTIONS statement.

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

Saved successfully!

Ooh no, something went wrong!