it's my understanding that SMS passes a list of eligible devices to be
used in allocation based on the request, I believe, and I could be
wrong, those eligible devices pass some scrutiny based on the allocation
request. the QUINEW devices are placed last in the list of eligible
devices and if there's enough space to satisfy a large secondary
allocation the allocation would be satisfied on that volume.
if my understanding is wrong please correct me.
Carmen
On 7/21/2022 2:43 PM, Pommier, Rex wrote:
That's a very interesting question that I would like to know the answer to as
well. In addition, will QUINEW volumes subsequently allow large secondary
extents to go onto these volumes?
Rex
-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of
Michael Watkins
Sent: Thursday, July 21, 2022 2:17 PM
To: [email protected]
Subject: [EXTERNAL] Re: SMS volume status of QUINEW?
So QUNEW can function to 'reserve' volumes for datasets with very large primary
allocations, requests that might not be satisfied if free space was not
consolidated on the QUINEW volume?
-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of
Mike Schwab
Sent: Thursday, July 21, 2022 2:13 PM
To: [email protected]
Subject: Re: SMS volume status of QUINEW?
CAUTION: This email originated from outside of the Texas Comptroller's email
system.
DO NOT click links or open attachments unless you expect them from the sender
and know the content is safe.
QuiNew keeps volumes as empty as possible, but if a dataset cannot be allocated
on all the other volumes it will be allocated on a QuiNew volume. VS a DisNew
volume is destined to be taken offline when empty and new datasets cannot be
allocated on the volume..
On Thu, Jul 21, 2022 at 10:32 AM Claude Richbourg
<[email protected]> wrote:
Good morning all,
We are curious about the reasoning behind the QUINEW status for SMS volume(s).
We use DISNEW for SMS volumes that we want to eventually phase out and we
discovered there were older volumes that had an existing assignment of QUINEW
within some storage groups.
It appears that the status of QUINEW would allow SMS to allocate space on those
volumes if needed. I had never heard of that status before until recently when
I was cleaning up the different storage pools.
Imagine my surprise when I set the volume status of those that had QUINEW to
DISNEW and a couple of batch jobs failed. I had to throw a few mod-27’s into
the pool to bring up the free space.
Apparently, QUINEW works differently then DISNEW and we were wondering about
the history and reasoning behind that status?
Does anyone know why it was created and to what purpose would it serve, or does
it pre-date DISNEW?
Thanks up front.
Claude
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send
email to [email protected] 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
[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
----------------------------------------------------------------------
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 [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
