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
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
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
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
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
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
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
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
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
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:
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
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
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
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.
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.
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
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
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
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
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
20 matches
Mail list logo
