Problem Note 9352: Multivolume sequential file with 0 space on first volume cannot be read
This is a carryover from V6 SAS Note v6-sys.file-5637 and is still an
issue in Version 7 and above of the SAS System. This note will further
explain and clarify the details of this problem.
When a multivolume sequential file is allocated and has no space used
on the first volume, SAS will not attempt to read any further.
Typically multivolume data sets are expected to have used space on
initial volumes. However, one such scenario where this can occur is
when the data set is allocated with the primary space of 0. The data
set is allocated to the volume. However, if during EXTENT processing
the secondary space cannot be allocated on that volume, the system will
go to the subsequent volume in the list. If the secondary space can be
allocated there, then I/O begins. Thus, the first volume will have no
space allocated to it, but there is in fact data for the library on
subsequent volume(s).
A circumvention is to specify primary space for the data set being
allocated.
A Technical Support hot fix for Release 8.2 (TS2M0) for this issue is
available at:
http://www.sas.com/techsup/download/hotfix/82_sbcs_prod_list.html#009352
For customers running SAS with Asian Language Support (DBCS), this hot
fix should be downloaded from:
http://www.sas.com/techsup/download/hotfix/82_dbcs_prod_list.html#009352
Operating System and Release Information
| SAS System | Base SAS | z/OS | 8 TS M0 | 9.1 TS1M0 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
| Type: | Problem Note |
| Priority: | medium |
| Topic: | Data Management ==> Access ==> External I/O
|
| Date Modified: | 2003-04-14 12:57:23 |
| Date Created: | 2003-02-05 12:39:42 |
