Re: IGD17272I but lots of space in storgrp

2019-07-10 Thread Barbara Nitz
One problem we had was unequal usage on the available volumes. The first 
volumes considered by SMS were almost full, no way to fulfill the primary space 
allocation. There was enough space in volumes that SMS would have checked 
later, but before SMS got there, the volcount was reached. We ended up 
increasing the volcount to the number of volumes available in the storgroup (or 
some sort of maximum), and voila, allocation went through.

Regards, Barbara

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: IGD17272I but lots of space in storgrp

2019-07-10 Thread Pew, Curtis G
On Jul 10, 2019, at 12:51 PM, Elaine Beal 
mailto:elaine.b...@gxs.com>> wrote:

451-System completion code and reason: B37-04
451-Data set is out of space.
451 Transfer aborted due to file error.

This error means you didn’t ask for enough space. There can be plenty of space 
available, but if your allocation request is too small you will run out of 
available extents.


--
Pew, Curtis G
curtis@austin.utexas.edu






--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: IGD17272I but lots of space in storgrp

2019-07-10 Thread Rob Schramm
How about volumes in DISNEW or quiesed or not assigned to your system?

Rob Schramm



On Wed, Jul 10, 2019 at 3:04 PM Edward Finnell <
000248cce9f3-dmarc-requ...@listserv.ua.edu> wrote:

> Might want to look at fragmentation on target volumes. Even if it's
> available the primary needs to be satisfied in 5 extents or less. I forget
> which field it is but you can actually sort on it from ISMF to see which
> volumes need attention;i.e. DEFRAG.
>
> In a message dated 7/10/2019 1:50:04 PM Central Standard Time,
> stars...@mindspring.com writes:
> If you really think SMS is not honoring the space allocation, then you
> should open up a PMR to IBM to find out how to correct the behavior.
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: IGD17272I but lots of space in storgrp

2019-07-10 Thread Edward Finnell
Might want to look at fragmentation on target volumes. Even if it's available 
the primary needs to be satisfied in 5 extents or less. I forget which field it 
is but you can actually sort on it from ISMF to see which volumes need 
attention;i.e. DEFRAG. 

In a message dated 7/10/2019 1:50:04 PM Central Standard Time, 
stars...@mindspring.com writes:
If you really think SMS is not honoring the space allocation, then you should 
open up a PMR to IBM to find out how to correct the behavior.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: IGD17272I but lots of space in storgrp

2019-07-10 Thread Lizette Koehler
If you really think SMS is not honoring the space allocation, then you should 
open up a PMR to IBM to find out how to correct the behavior.

I expect based on how SMS selects volumes, you may SEE volumes that look 
eligible, but SMS will not

Lizette


> -Original Message-
> From: IBM Mainframe Discussion List  On Behalf Of
> Elaine Beal
> Sent: Wednesday, July 10, 2019 10:52 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: IGD17272I but lots of space in storgrp
> 
> Update- there're are actually two errors.
> the one that actually says out of space
> 
> 451-System completion code and reason: B37-04 451-Data set is out of space.
> 451 Transfer aborted due to file error.
> 
> and I found that the FTP does submit a job with the primary specified but
> cannot get it even though there are multiple volumes with the available space
> 
> Elaine
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send email to
> lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: IGD17272I but lots of space in storgrp

2019-07-10 Thread Elaine Beal
Update- there're are actually two errors.
the one that actually says out of space

451-System completion code and reason: B37-04
451-Data set is out of space.
451 Transfer aborted due to file error.

and I found that the FTP does submit a job with the primary specified
but cannot get it even though there are multiple volumes with the available 
space

Elaine

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: IGD17272I but lots of space in storgrp

2019-07-10 Thread Clifford McNeill
The error is

550-SVC99 RETURN CODE=4 S99INFO=0 S99ERROR=38668 HEX=970C S99ERSN code 
X'012C'.
550 Unable to create data set OY72364.APTAR.L1.AIBILL.EXT for APPE command.

It seems like SMS is not trying every volume in the storage group.

---

Based on the error codes this seems pretty serious, SMS is ABENDing.  That 
would explain why it is not trying every volume.  I suspect there is a volume 
in the group with a messed up VTOC.  I would find the dump and open a trouble 
ticket with IBM to enlist their aid.

S99ERROR x'970C' says

 Meaning: Severe SMS VTOC service error.

 Application Programmer Action: Check field S99ERSN for a  non-zero value. A 
non-zero value in S99ERSN is a reason code.

See "SMS reason code (S99ERSN)" in topic 26.2.1.1 for the possible 
reason codes.

S99ERSN x'12C' says

Meaning: An abend occurred during storage management subsystem processing. 
Message IGD300I will be issued to the operator with a symptom dump.
System Programmer Action: Examine message IGD300I and the symptom dump to 
determine why the abend occurred.

Cliff McNeill


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: IGD17272I but lots of space in storgrp

2019-07-10 Thread Elaine Beal
This is an FTP with I guess dynamic allocation (dataset does not exist)

There are multiple volumes with available space when requested.

The error is 

550-SVC99 RETURN CODE=4 S99INFO=0 S99ERROR=38668 HEX=970C S99ERSN code 
X'012C'.
550 Unable to create data set OY72364.APTAR.L1.AIBILL.EXT for APPE command.

It seems like SMS is not trying every volume in the storage group.

Elaine

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: IGD17272I but lots of space in storgrp

2019-07-10 Thread Andrew Rowley

On 10/07/2019 7:19 am, Mike Schwab wrote:

Could someone put in an RFE?  When a dataset is deallocated (usually
step end), there is a disposition message.  I would like to see added
to the message the ### Volumes, ### Extents, ###,###,###,### Tracks.
To help in cases like this.


There is information in SMF.

EasySMF has Allocation Failures and Non-VSAM Statistics reports which 
probably have the information you are looking for.


SMF is very useful for systems programmers trying to solve problems - 
it's not just about capacity planning and performance.


Andrew Rowley

Black Hill Software

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: IGD17272I but lots of space in storgrp

2019-07-10 Thread Vernooij, Kees (ITOP NM) - KLM
Elaine,

There can be enough space in the SG, but was the *requested* space available, 
on 1 volume, at that very moment?

Kees.

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Elaine Beal
> Sent: 09 July, 2019 21:08
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: IGD17272I but lots of space in storgrp
> 
> Thanks Mike.
> This is a new allocation and there are many volumes it could extend to.
> 
> Elaine
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

For information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message.

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its 
employees shall not be liable for the incorrect or incomplete transmission of 
this e-mail or any attachments, nor responsible for any delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch 
Airlines) is registered in Amstelveen, The Netherlands, with registered number 
33014286



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: IGD17272I but lots of space in storgrp

2019-07-09 Thread Lester, Bob

 In our shop, the magic bullet is:

1) Dataclass has 1 volume, with dynamic volume count of 20.
2) Dataset is (or can be made) PSE.

As others have said, check the allocation - both in the JCL and in the SMS 
data class used - if any.   If the DSN is grossly underallocated in the JCL, 
fix that first.

Other thoughts - have you made sure all of the volumes in your Storage 
Group are enabled?   Set as SMS?  Are your VTOC and VTOCIX not full and 
healthy?  (I've been bit by that one!).

Hope this helps!

BobL

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Lizette Koehler
Sent: Tuesday, July 9, 2019 5:00 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXT] Re: IGD17272I but lots of space in storgrp

So the key for this message is
REQUESTED SPACE QUANTITY =  {KB|MB}

What was in this message.

Typically I find this message occurs when the volumes being selected do not 
have sufficient space for allocation.  Also because the space parms are not 
tuned to handle daily usage vs. high water mark storage allocation.


What is the SPACE= parameters being use?

How many extents is the dataset going to

What does the pool look like?  Are there lots of volumes will less than 
adequate storage on them?

SMS is not always going to pick the volumes we think it should.  The algorithm 
can go after volumes less than optimal.

There is a Share presentation from 2011 that may help

DFSMS Basics: How SMS Volume Selection Works

Page 11 in this presentation shows a great graphic of how a volume is selected.

Hope this helps

Lizette




> -Original Message-
> From: IBM Mainframe Discussion List  On 
> Behalf Of Elaine Beal
> Sent: Tuesday, July 09, 2019 11:37 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: IGD17272I but lots of space in storgrp
> 
> We are getting this message even though there is a LOT of contiguous 
> space available in the storage group.
> We get this periodically and adding a volume seems to relieve the 
> immediate request.
> 
> Thanks,
> Elaine
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send 
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Confidentiality Note: The information contained in this 
message, and any attachments, may contain confidential 
and/or privileged material.  It is intended solely for the 
person(s) or entity to which it is addressed.  Any review, 
retransmission, dissemination, or taking of any action in
reliance upon this information by persons or entities other 
than the intended recipient(s) is prohibited.  If you received 
this in error, please contact the sender and delete the 
material from any device.



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: IGD17272I but lots of space in storgrp

2019-07-09 Thread Lizette Koehler
So the key for this message is
REQUESTED SPACE QUANTITY =  {KB|MB}

What was in this message.

Typically I find this message occurs when the volumes being selected do not 
have sufficient space for allocation.  Also because the space parms are not 
tuned to handle daily usage vs. high water mark storage allocation.


What is the SPACE= parameters being use?

How many extents is the dataset going to

What does the pool look like?  Are there lots of volumes will less than 
adequate storage on them?

SMS is not always going to pick the volumes we think it should.  The algorithm 
can go after volumes less than optimal.

There is a Share presentation from 2011 that may help

DFSMS Basics: How SMS Volume Selection Works

Page 11 in this presentation shows a great graphic of how a volume is selected.

Hope this helps

Lizette




> -Original Message-
> From: IBM Mainframe Discussion List  On Behalf Of
> Elaine Beal
> Sent: Tuesday, July 09, 2019 11:37 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: IGD17272I but lots of space in storgrp
> 
> We are getting this message even though there is a LOT of contiguous space
> available in the storage group.
> We get this periodically and adding a volume seems to relieve the immediate
> request.
> 
> Thanks,
> Elaine
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send email to
> lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: IGD17272I but lots of space in storgrp

2019-07-09 Thread Mike Schwab
Could someone put in an RFE?  When a dataset is deallocated (usually
step end), there is a disposition message.  I would like to see added
to the message the ### Volumes, ### Extents, ###,###,###,### Tracks.
To help in cases like this.

On Tue, Jul 9, 2019 at 7:13 PM Elaine Beal  wrote:
>
> I see you said a new allocation so of course I can't migrate it.
> there are many volumes available in the storage group.
> it doesn't request multiple volumes..
> why does it not search the group until it gets the requested space?
>
> Elaine
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN



-- 
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: IGD17272I but lots of space in storgrp

2019-07-09 Thread Mike Schwab
What storage class is it assigned to, and what is the VOLCNT?  If the
VOLCNT is 1 then it must be allocated on 1 volume.

On Tue, Jul 9, 2019 at 7:13 PM Elaine Beal  wrote:
>
> I see you said a new allocation so of course I can't migrate it.
> there are many volumes available in the storage group.
> it doesn't request multiple volumes..
> why does it not search the group until it gets the requested space?
>
> Elaine
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN



-- 
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: [External] Re: IGD17272I but lots of space in storgrp

2019-07-09 Thread Wissink, Brad
Is your SMS routines setting the data set as multi-volume?  If not then you 
need to do an IDCAMS ALTER on the data set to add multiple volues.

Brad Wissink| Sr. Systems Programmer
Sammons® Financial Group Member Companies
4350 Westown Pkwy | West Des Moines | IA 50266
Phone 515-267-2735 | ext. 33735 | Cell: 515-231-1511 

bwiss...@sfgmembers.com  | www.SammonsFinancialGroup.com

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Elaine Beal
Sent: Tuesday, July 09, 2019 2:13 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [External] Re: IGD17272I but lots of space in storgrp

I see you said a new allocation so of course I can't migrate it.
there are many volumes available in the storage group.
it doesn't request multiple volumes..
why does it not search the group until it gets the requested space?

Elaine

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN


The information contained in this message is confidential, protected from 
disclosure and may be legally privileged.  If the reader of this message is not 
the intended recipient or an employee or agent responsible for delivering this 
message to the intended recipient, you are hereby notified that any disclosure, 
distribution, copying, or any action taken or action omitted in reliance on it, 
is strictly prohibited and may be unlawful.  If you have received this 
communication in error, please notify us immediately by replying to this 
message and destroy the material in its entirety, whether in electronic or hard 
copy format.  Thank you.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: IGD17272I but lots of space in storgrp [EXTERNAL]

2019-07-09 Thread Feller, Paul
Elaine, I'm sure you saw that the IGD17272I will tell you the allocation 
request (REQUESTED SPACE QUANTITY =  {KB MB}).  I'm sure you looked at that 
request size and at the time you looked the storage group had space.  

Could there be an issue that at the time of the failure the storage group was 
low on space?

Thanks..

Paul Feller
AGT Mainframe Technical Support

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Elaine Beal
Sent: Tuesday, July 09, 2019 2:13 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: IGD17272I but lots of space in storgrp [EXTERNAL]

I see you said a new allocation so of course I can't migrate it.
there are many volumes available in the storage group.
it doesn't request multiple volumes..
why does it not search the group until it gets the requested space?

Elaine

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
Please note:  This message originated outside your organization. Please use 
caution when opening links or attachments.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: IGD17272I but lots of space in storgrp

2019-07-09 Thread Elaine Beal
I see you said a new allocation so of course I can't migrate it.
there are many volumes available in the storage group.
it doesn't request multiple volumes..
why does it not search the group until it gets the requested space?

Elaine

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: IGD17272I but lots of space in storgrp

2019-07-09 Thread Elaine Beal
Thanks Mike.
This is a new allocation and there are many volumes it could extend to.

Elaine

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: IGD17272I but lots of space in storgrp

2019-07-09 Thread Mike Schwab
What would happen in our shop was the space request was for a small
primary and small secondary (eg (TRK,(1,1))) and multiple volumes.
The program writes the data, uses up all the extents, goes to the next
volume and uses up all the extents, and repeats until it runs out of
the number of volume online or allowed.  Quick fix is to migrate and
recall the dataset, often into 1 extent on 1 volume.  And the next
time the dataset is extended to another volume, this will be the
initial allocation on additional volumes.  Long term fix is for the
user to use a larger space allocation that won't run out, and release
unused space.

On Tue, Jul 9, 2019 at 6:36 PM Elaine Beal  wrote:
>
> We are getting this message even though there is a LOT of contiguous space 
> available in the storage group.
> We get this periodically and adding a volume seems to relieve the immediate 
> request.
>
> Thanks,
> Elaine
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN



-- 
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


IGD17272I but lots of space in storgrp

2019-07-09 Thread Elaine Beal
We are getting this message even though there is a LOT of contiguous space 
available in the storage group.
We get this periodically and adding a volume seems to relieve the immediate 
request.

Thanks,
Elaine

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN