• Print |
• E-mail  |
• Bookmark

In Release 8.1 and above of the SAS System, a corrupt SAS data library
is created if you:

   1) use a STORCLAS with the GUARANTEED SPACE attribute enabled
      when allocating the library
and

   2) specify a NON-ZERO secondary space value in the SPACE= parameter
      when allocating the library.

GUARANTEED SPACE is not required when allocating a multivolume SAS data
library in Version 8.1 and above, as it was in Version 6.  Allocating
the library to a STORCLAS which does not have the GUARANTEED SPACE
attribute enabled is the recommended solution to this problem.

Attempting to process a library created as described above can generate
the following error messages in the SAS Log:

   Physical I/O error on SAS data library DATA.SET.NAME on
   volume volser,jobname,stepname,dev-addr,ddname,86-OP

and the JOB step ends with a USER 0315 abend. You may also receive:

   Expecting page NNN, got page -1 instead.
   Page validation error while reading LIBREF.DATASET.DATA
   File LIBREF.DATASET.DATA is damaged.
   I/O processing did not complete.

In this case, the step ends with a RC=8.

You can refer to the "SAS Companion for the OS/390 Environment, Version
8" manual for details on the recommended method for allocating
multivolume SAS data libraries.

NOTE:  Because GUARANTEED SPACE is not required when allocating
multivolume SAS data libraries in Release 8.1 and above, it is strongly
recommended that you refer to the SAS Companion and follow the
guidelines for allocating multivolume SAS data libraries.  Removing
GUARANTEED SPACE as a requirement in Release 8.1 and above, allows your
SAS data libraries to "grow" as needed instead of allocating all the
disk space up front.  This is potentially a significant decrease in the
amount of disk space that is required for your multivolume SAS data
libraries.

A Technical Support hot fix for Release 8.1 TSLEVEL 1M0 for this problem
is available at:

http://www.sas.com/techsup/download/hotfix/81_sbcs_prod_list.html#005642


A Technical Support hot fix for Release 8.2 TSLEVEL 2M0 for this problem
is available at:

http://www.sas.com/techsup/download/hotfix/82_sbcs_prod_list.html#005642

For customers running SAS with DBCS extensions, this hot fix should be
downloaded from:

http://www.sas.com/techsup/download/hotfix/82_dbcs_prod_list.html#005642

Operating System and Release Information

A zap for this issue for SAS 8.0(TSM0) on MVS is available at:

A zap for this issue for SAS 8.1(TS1M0) on MVS is available at: