Hi am facing insufficient space issue in a storage group.
IGD17288I DATA SET XXX.XXX.XXX.XXXXX 806
COULD NOT BE ALLOCATED NORMALLY AND IS NOT ELIGIBLE
FOR SPACE CONSTRAINT RELIEF (MULTI VOLUME) BECAUSE IT IS
A GUARANTEED SPACE DATA SET.
SPACE CONSTRAINT RELIEF (SPACE REDUCTION AND/OR 5 EXTENT
LIMIT RELIEF) WILL BE ATTEMPTED
IGD17272I VOLUME SELECTION HAS FAILED FOR INSUFFICIENT SPACE
DATA SET XXX.XXX.XXX.XXXXX
JOBNAME (XXXXXXXX) STEPNAME (IDCAM010)
PROGNAME (SSIDCAMS) DDNAME (N/A )
REQUESTED SPACE QUANTITY = 3652171 KB
0IGD17273I ALLOCATION HAS FAILED FOR ALL VOLUMES SELECTED FOR DATA SET
IGD17290I THERE WERE 1 CANDIDATE STORAGE GROUPS OF WHICH THE FIRST 1
WERE ELIGIBLE FOR VOLUME SELECTION.
THE CANDIDATE STORAGE GROUPS WERE:XXXXXSG
IGD17279I 25 VOLUMES WERE REJECTED BECAUSE THE SMS VOLUME STATUS WAS DISABLED
IGD17279I 25 VOLUMES WERE REJECTED BECAUSE THEY WERE NOT ONLINE
IGD17279I 25 VOLUMES WERE REJECTED BECAUSE THE UCB WAS NOT AVAILABLE
IGD17279I 348 VOLUMES WERE REJECTED BECAUSE THEY DID NOT HAVE SUFFICIENT SPACE
IGD17219I UNABLE TO CONTINUE DEFINE OF DATASET
0IDC3020I UNABLE TO ALLOCATE SPACE ON USER VOLUME
IDC3007I ** VSAM CATALOG RETURN CODE IS 68
0IDC3003I FUNCTION TERMINATED. CONDITION CODE IS 12
My request is..
1.we are having 375 volumes in that storage group out of that 25 volumes are disabled/not online....but as per the log why it is asking for that 25 volumes.
2.why its showing insufficient space at 348 volumes itself...why it's not using the last 2 volumes
Joined: 06 Jun 2008 Posts: 8491 Location: Dubuque, Iowa, USA
1. the log messages are NOT telling you that it attempted allocation on the 25 volumes; the messages tell you WHY it could not allocate space on those 25 volumes.
2. YOU may think the storage group has 375 volumes; the system thinks there are 373 volumes in the storage group. The remaining two may not have been set up correctly for the storage group; only by looking at the ISMF data for the storage group could that be determined. One possible reason, for example, is if the LPAR you are using is not enabled for new space allocation for those two volumes.
When SMS goes through it's volume selection it looks at ALL volumes in the Storgrp and goes through an elimination process. This is a simplified explanation of what it does:
Any that are offline or in DISNEW or suchlike are eliminated from the selection list.
It then looks at available volumes left and further eliminates any volumes whose high thresold (as defined by the Storgrp high threshold) would be exceeded if the allocation was put on them.
It then tries to select from the remaining available volumes based on SRM values, i.e. those that meet the Storclas performance criteria, and which are the least busy.
Any volumes that do not meet these previous two criteria are put in a secondary list.
In this case there were no volumes that had sufficient space available for the allocation in the primary list, even after Space Constraint Relief tried to cut down the allocations to fit available space. It must have also failed when it then went to the secondary list of remaining volumes, that had less space and were more busy.
Bottom line is the Storgrp is too full and needs more capacity added. (unless as Robert suggested the SMS status of the volumes or storgrp are different on particular LPARs, but that is an unusual practice and not normally recommended)