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.

Details<br />

System Options under z/<strong>OS</strong> VERB<strong>OS</strong>E System Option 523<br />

UTILLOC=’ALLOC UNIT(DISK) UCOUNT(2) CYL SPACE(20,100)’<br />

UTILLOC=’/dept/prod/utility’<br />

UTILLOC=(’ALLOC UNIT(SYSDA) UCOUNT(2) CYL SPACE(15,15)’)<br />

UTILLOC=(’ALLOC UNIT(SYSDA) VOL(SCR001) CYL SPACE(15,15)’,<br />

’ALLOC UNIT(SYSDA) VOL(SCR002) CYL SPACE(15,15)’)<br />

UTILLOC=(’/dept/prod/utility1’, ’/dept/prod/utility2’)<br />

UTILLOC=(’ALLOC UNIT(DISK) CYL SPACE(20,100)’,<br />

’/dept/prod/utility’)<br />

The following parameters must be specified on the ALLOC command:<br />

3 UNIT<br />

3 TRACKS, CYL, or BLOCK<br />

3 SPACE(primary[,secondary])<br />

One or more of the following options can be also specified on the ALLOC command:<br />

3 UCOUNT(number of devices)<br />

3 VOL(volser [,volser...])<br />

3 STORCLASS(storage class)<br />

3 MGMTCLAS(management class)<br />

3 DATACLAS(data class)<br />

Note: UCOUNT is recommended instead of VOL. R<br />

The ALLOC command options listed above have the same syntax and meaning as<br />

when specified on the TSO ALLOCATE command. See the IBM documentation about<br />

the ALLOCATE command <strong>for</strong> more in<strong>for</strong>mation.<br />

An ALLOC command can be specified as a utility file location even in the batch<br />

environment. It is not necessary to be running <strong>SAS</strong> under TSO when you specify an<br />

ALLOC command as a utility file location.<br />

When you specify multiple utility file locations, they are generally used in a<br />

round-robin fashion by <strong>SAS</strong> applications. For applications that use multiple utility files<br />

at once, it might there<strong>for</strong>e improve per<strong>for</strong>mance to specify locations that have separate<br />

I/O paths (such as locations on different DASD control units).<br />

Unique, system-generated names are used <strong>for</strong> each utility file required by <strong>SAS</strong>. This<br />

allows multiple distinct utility files to be in use at one time. It is not possible to specify<br />

the data set name to be used <strong>for</strong> the utility files.<br />

The utility files required by some applications might exceed the size of a z/<strong>OS</strong> disk<br />

volume. To allocate multiple volumes <strong>for</strong> a utility file, specify UCOUNT(n) where n is<br />

the maximum number of volumes. Or, specify an SMS data class (with the DATACLAS<br />

option), which in turn specifies a volume count greater than one. Specifying an explicit<br />

list of volumes with the VOL option is not recommended <strong>for</strong> multivolume utility files.<br />

The utility files specified with the UTILLOC option reside in regular <strong>for</strong>mat<br />

sequential data sets. Extended <strong>for</strong>mat sequential data sets are not currently supported.<br />

VERB<strong>OS</strong>E System Option<br />

Writes the settings of <strong>SAS</strong> system options either to the terminal or to the batch job log

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

Saved successfully!

Ooh no, something went wrong!