Portal | Manuals | References | Downloads | Info | Programs | JCLs | Mainframe wiki | Quick Ref
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Profile Log in to check your private messages Log in
 
INSUFFICIENT SPACE IN A STORAGE GROUP

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM
View previous topic :: :: View next topic  
Author Message
lemon123

New User


Joined: 12 Feb 2013
Posts: 10
Location: India

PostPosted: Sat Feb 23, 2013 1:29 pm    Post subject: INSUFFICIENT SPACE IN A STORAGE GROUP
Reply with quote

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
XXX.XXX.XXX.XXXXX
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
XXX.XXX.XXX.XXXXX
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



Thanks in advance...

Regards,
lemon123
Back to top
View user's profile Send private message

Bill Woodger

DFSORT Moderator


Joined: 09 Mar 2011
Posts: 7315

PostPosted: Sat Feb 23, 2013 1:56 pm    Post subject: Reply to: INSUFFICIENT SPACE IN A STORAGE GROUP
Reply with quote

Perhaps the 25, 25, and 25 are not, despite what you think, the same 25 each time?
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8165
Location: East Dubuque, Illinois, USA

PostPosted: Sat Feb 23, 2013 5:34 pm    Post subject:
Reply with quote

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.
Back to top
View user's profile Send private message
Pete Wilson

Active User


Joined: 31 Dec 2009
Posts: 445
Location: London

PostPosted: Mon Feb 25, 2013 7:46 pm    Post subject:
Reply with quote

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)
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts sharing PLI storage Pedro PL/I & Assembler 2 Mon Oct 16, 2017 10:11 pm
No new posts The TS7720 is out of cache space. Rex Montemayor All Other Mainframe Topics 2 Mon Sep 25, 2017 7:18 am
No new posts column with count of rows within dist... ronald wouterson DB2 4 Sun Sep 17, 2017 9:48 pm
This topic is locked: you cannot edit posts or make replies. Limit access to certain RACF group cvnlynn CLIST & REXX 5 Wed Aug 23, 2017 2:28 am
No new posts Iterative use of a REXX script causin... bryonyh CLIST & REXX 4 Fri Jul 28, 2017 12:52 pm

Facebook
Back to Top
 
Job Vacancies | Forum Rules | Bookmarks | Subscriptions | FAQ | Polls | Contact Us