Thank you Neil,

I have implemented your very good advice.
 
For whatever reason I had expected that as my requirement exceeded a single 
Mod-27 my request would have simply been satisfied by  SMS using the volume 
count and performing a multi-volume allocation.  Learn something new every day.

Michael Geiger 


This email message is confidential, may be privileged, and is intended for the 
exclusive use of the addressee. Any other person is strictly prohibited from 
disclosing or reproducing it. If the addressee cannot be reached or is unknown 
to you, please inform the sender by return email and delete this email message 
and all copies immediately.

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Neil Duffee
Sent: Friday, February 05, 2016 4:32 PM
To: [email protected]
Subject: Re: IGD17279I due to insufficient space

Caveat:  as a daily digester, my responses are always behind-the-times...

The messages are perfectly correct and expected.  Your culprit is MB(86000) 
which would be similar to requesting CYL(110000).  None of the listed volumes 
have the required 86Gb of free space.  Rather they all show 27176309K (27Gb) 
available.  You need to specify a primary that is less than 27Gb or something 
like MB(26000 26000).

Advice/Suggestion:  You could eliminate the VOLUMES() option since 
DataClas(Extended) has VolCount=255 & SMS is going to ignore your request for 
USER13.  Personally, I leave all my DataClas's with small, reasonable VolCounts 
for typical allocations ie. 1-5, and use DynVolCount as the big limit.  Why?  
If you remove the Volumes() option, the catalogue will list 255 (VolCount) 
eligible volumes (yes, mostly asterisks).  If you retain the Volumes() option, 
you can't expand beyond the 5 volumes listed.  With DynVolCount, SMS uses 
Volumes('*' x VolCount) at initial allocation but allows as many volumes as 
desired (to max=DynVolCount) both during initial creation and at any time in 
the future.  The Catalogue entry will only list the actual volumes without 
additional, extraneous asterisks.  DynVolCount also helps to treat x37 problems 
in constrained pools. (or those of us who are stuck at Mod-3s for hysterical 
reasons)

-------->  signature = 8 lines follows  <--------
Neil Duffee, Joe Sysprog, uOttawa, Ottawa, Ont, Canada
telephone:1 613 562 5800 x4585                  fax:1 613 562 5161
mailto:NDuffee of uOttawa.ca     http:/ /aix1.uOttawa.ca/ ~nduffee
"How *do* you plan for something like that?"  Guardian Bob, Reboot "For every 
action, there is an equal and opposite criticism."
"Systems Programming: Guilty, until proven innocent"  John Norgauer 2004 
"Schrodinger's backup: The condition of any backup is unknown until a restore 
is attempted."  John McKown 2015


-----Original Message-----
From: Mike Geiger [mailto:[email protected]]
Sent: February 4, 2016 12:09
Subject: IGD17279I due to insufficient space

Looking for some insight.  I am configuring our new z/OS 2.2 ADCD at RSU1508 
system(already have a 2.1, 1.13 and 1.11) Why is the following define failing?  
Everything looks ok to me. Adequate space is available.

All multi-volume allocations of any type fail.  SMS seems to be attempting to 
define all the space on a single volume.

     DEFINE CLUSTER (NAME(USER.SPACE.ZFS)             -
            VOLUMES(USER13 * * * *)                  -
            DATACLASS(EXTENDED)                        -
            LINEAR MB(86000)  SHAREOPTIONS(3)) 

IGD17226I THERE IS AN INSUFFICIENT NUMBER OF VOLUMES IN THE ELIGIBLE STORAGE 
GROUP(S) TO SATISFY THIS REQUEST FOR DATA SET USER.SPACE.ZFS 

IGD17290I THERE WERE 1 CANDIDATE STORAGE GROUPS OF WHICH THE FIRST 1 WERE 
ELIGIBLE FOR VOLUME SELECTION.
THE CANDIDATE STORAGE GROUPS WERE:DEFAULT 

IGD17279I 5 VOLUMES WERE REJECTED BECAUSE OF INSUFF TOTAL SPACE 

IGD17219I UNABLE TO CONTINUE DEFINE OF DATA SET USER.SPACE.ZFS 

IDC3003I FUNCTION TERMINATED. CONDITION CODE IS 12


STORGRP  TYPE    SYSTEM= 1
DEFAULT  POOL            +
  SPACE INFORMATION:
  TOTAL SPACE = 132775MB USAGE% = 18 ALERT% = 0
  TRACK-MANAGED SPACE = 132775MB USAGE% = 18 ALERT% = 0
VOLUME   UNIT    SYSTEM= 1                               STORGRP NAME
USER10   0AA9            +                                 DEFAULT
USER11   0AAA            +                                 DEFAULT
USER12   0AAB            +                                 DEFAULT
USER13   0AAE            +                                 DEFAULT
USER14   0AAF            +                                 DEFAULT

VOLUME FREE       %     ALLOC      FRAG   LARGEST    FREE     INDEX     FREE    
 FREE
SERIAL SPACE      FREE  SPACE      INDEX  EXTENT     EXTENTS  STATUS    DSCBS   
 VIRS
-(2)-- ---(3)---  (4)-  ---(5)---  -(6)-  ---(7)---  --(8)--  --(9)---  -(10)-- 
 -(11)--
USER10 27176309K    99     15771K      0  27176309K        1  ENABLED      4446 
     909
USER11 27176032K    99     16048K      0  27176032K        1  ENABLED      4445 
     909
USER12 27187376K    99      4704K      0  27184609K        2  ENABLED      1446 
     909
USER13 27176309K    99     15771K      0  27176309K        1  ENABLED      4446 
     909
USER14 27176309K    99     15771K      0  27176309K        1  ENABLED      4446 
     909
[snip]

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
[email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to