Problems
that occur when processing utility files that are specified by an
ALLOC command can be grouped into the following categories:
-
errors in the syntax of the ALLOC
command. These problems include errors such as misspelling the name
of an operand, failing to supply the required operands, and so on.
-
failure of the system to perform
the dynamic allocation requested by the ALLOC command. These problems
can occur because the requested resources are not available or because
names are specified that are not defined on the system.
-
insufficient space in the utility
file. These problems occur when SAS is writing data to the utility
file and the utility file becomes full, but the system is not able
to allocate additional space to the utility file data set. The failure
to allocate additional space can occur because no secondary space
amount was specified, because the maximum number of extents have been
allocated, or because no more disk space is available on the disk
volume or volumes allocated to the utility file.
SAS does not detect problems with UTILLOC location
specifications until an attempt is made to create a utility file.
The following example
shows the type of message that is issued if the ALLOC command has
a syntax error. In this case, the block length is omitted from the
BLOCK operand. BLOCK
(block length)
should have been specified instead:
Dynalloc syntax error: Unknown, or unsupported parm.
Invalid syntax for data set dynamic allocation specification.
Data set dynamic allocation specification: ALLOC UNIT(DISK)
UCOUNT(2) BLOCK SPACE(500,500) NEW DELETE
ERROR: Utility file open failed.
ERROR: Object creation failure.
ERROR: Sort initialization failure.
In the following example
the ALLOC command has valid syntax, but it refers to a unit name,
BADUNIT, that is not defined on the system:
SVC 99 could not process data set dynamic allocation
specification. R15: 0X4, Reason: 0X21C, Info: 0
Data set dynamic allocation specification: ALLOC UNIT(BADUNIT)
CYL SPACE(20,100) NEW DELETE
ERROR: Utility file open failed.
ERROR: Object creation failure.
ERROR: Sort initialization failure.
In the following example
no secondary space was specified, so SAS could not extend the utility
file after the primary space amount was consumed:
Data set SYS10321.T171203.RA000.USERID.R0106386 could not be extended.
Data set dynamic allocation specification: ALLOC UNIT(DISK)
UCOUNT(2) TRACKS SPACE(1,1) NEW DELETE
Space used on volume SCRAT2 = 16 tracks and 16 extents.
Space used on volume SCRAT1 = 16 tracks and 16 extents.
Total space used = 32 tracks and 32 extents.
ERROR: Unexpected error Filename = SYS10321.T171203.RA000.USERID.R0106386.
ERROR: No disk space is available for the write operation. Filename =
SYS10321.T171203.RA000.USERID.R0106386.
ERROR: Failure while attempting to write page 17 of sorted run 1.
ERROR: Failure while attempting to write page 17 to utility file 1.
Note: The operands NEW and DELETE
are shown as part of the dynamic allocation requests. These operands
should not be specified as part of the ALLOC command because they
are added automatically by SAS.
You can also use the
debug_utilloc command
to determine whether the syntax of your UTILLOC option is valid. Submit
the command from a line in the
SAS Program Editor window,
and SAS outputs the ALLOC command and any errors to the SAS log.