This sounds like the track size problem.
There were a lot of shops that implemented a default track size of 47476 (3380)
rather than 56664 (3390). This ends up, after DADSM is finished with the
allocation, with your dataset 80% of the request size.
Check with your. Storage Admins.
(I forget
I found the answer to my question. In the SMS base config the Default device
geometry is set up for 3380 instead of 3390 :
Default Device Geometry
Bytes/track . . . . . : 47476
Tracks/cylinder . . . : 15
This is causing the allocation to be reduced. To bypass the problem I am using
Ted,
Thanks. Our e-mails crossed each other. Yes, it is set to 47476 tracks as you
had suggested.
Thanks for your help.
From: Ted MacNEIL eamacn...@yahoo.ca
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Thursday, October 3, 2013 1:37:15 PM
Subject: Re: SMS QUESTION - ACTUAL SPACE NOT ALLOCATED
The first thing I'd check is the Default Device Geometry defined in your
SMS Base configuration:
Mine:
Default Device Geometry
Bytes/Track . . . . . . . . 56664
Tracks/Cylinder . . . . . . 15
in ISMF - Option 8 Control Data Set
then Option 1 Display
Good Day All,
I am
willie bunter wrote:
I found the answer to my question. In the SMS base config the Default device
geometry is set up for 3380 instead of 3390 :
Thanks. I tried *really* to reproduce your problem but could not succeed in it.
I even RTFM everything about that guarantee space, but of course it is
