Paul Gilmartin wrote:
In a recent note, R.S. said:
Date: Mon, 18 Sep 2006 19:24:56 +0200
I just encountered the following problem:
Restored production IODF from DSS dump and got two-extents file. For
obvious reason I didn't want more than 1 extent. <g> The primary
reason
was near-full, fragmented volume, which shouldn't have place, however
it
had place.
Q: how can I prevent such multi-extent allocation ?
I'd like to have something a'la CONTIG: single extent file or failure.
Did you specify CONTIG when you originally allocated the data set?
If so, it's a clear defect for restore not to honor the characteristics
of the initial allocation.
Try for an APAR.
Paul,
This is production IODF. It is allocated by HCD application, I cannot
provide any parameter except name & volser. It have to be single extent.
In case of lack of space HCD will *not* go into extents - you'll get
error message instead. That's good. Is it allocated with CONTIG? Well
...I don't know, I never tried to allocated VSAM with CONTIG.
Regarding APARs, PMRs and other fancy acronyms: I am in Poland. The
things are quite different. The software is the same (but we pay more),
but the service&support is not (we get less IMHO).
Regards
--
Radoslaw Skorupka
Lodz, Poland
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
