I don't think so.
Or if you are right then there are some big issues in the next few
years that IBM's own products won't be able to support. As an example
IBM semi announced that soon there will be dynamic storage(DASD)
expansion and it will be done with volser (ex ABC001,ABC002 etc etc)
We put unused volsers into SMS Storage groups then init actual volumes
when more space is needed.
On Thu, Oct 30, 2014 at 12:20 PM, Ed Gould edgould1...@comcast.net wrote:
I don't think so.
Or if you are right then there are some big issues in the next few years
that IBM's own products won't
On Oct 30, 2014, at 5:33 PM, Mike Schwab wrote:
We put unused volsers into SMS Storage groups then init actual volumes
when more space is needed.
--SNIP---
You still have to put them in your ACS routines and DFDSS won't allow
patterning of
Correct. We put in a range of volumes. Example LGA 001-099. We then
initialize a few of the volumes, say LGA 001-009. When these volumes
get to 90% full, and allocations fail, we init volume LGA 010. Once
online it probably will be used for over half the allocations until it
becomes fairly
Esmie,
You are posing an invalid situation for what you specified.
After 4 days of non-usage, the dsn *will* migrate to ML1. After 7 more days of
non-usage, it will migrate to ML2. After 540 days, it will expire.
If the dataset has not migrated, numerous possible conditions exist:
1) it was
QUESTION - EXPIRATION OF DSN
To: IBM-MAIN@LISTSERV.UA.EDU
Received: Wednesday, October 29, 2014, 7:53 AM
Esmie,
You are posing an invalid
situation for what you specified.
After 4 days of non-usage, the dsn *will*
migrate to ML1. After 7 more days of non-usage, it will
migrate to ML2
:
Subject: Re: DFHSM QUESTION - EXPIRATION OF DSN
To: IBM-MAIN@LISTSERV.UA.EDU
Received: Wednesday, October 29, 2014, 7:53 AM
Esmie,
You are posing an invalid
situation for what you specified.
After 4 days of non-usage, the dsn *will* migrate to ML1. After 7 more days
of non-usage
Bob,
Thanks very much for your help.
On Wed, 10/29/14, Richards, Robert B. robert.richa...@opm.gov wrote:
Subject: Re: DFHSM QUESTION - EXPIRATION OF DSN
To: IBM-MAIN@LISTSERV.UA.EDU
Received: Wednesday, October 29, 2014, 8:50 AM
If the dsn
Bob,
We have a similar situation at our end. There is a dsn with the following
atribute:
Expire after Days Non-usage . : 365.
Migration Attributes
Primary Days Non-usage . : 2
Level 1 Days Date/Days . : 10
Command or Auto Migrate . : BOTH
What if the DSN
snip
After 4 days of non-usage, the dsn *will* migrate to ML1. After 7 more days of
non-usage, it will migrate to ML2. After 540 days, it will expire.
/snip
Minor correction:
After 4 days of non-usage, the dsn *will* migrate to ML1.
After 7 days of non-usage, it will migrate to ML2. If not
Yes.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Willie Bunter
Sent: Wednesday, October 29, 2014 9:14 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: DFHSM QUESTION - EXPIRATION OF DSN
Bob,
We have a similar situation at our end
There is a bit that can be set.
Check the dfHSM Implementation Guide for
Disabling delete-if-backed-up (DBU) processing for SMS data Sets
snip
We have a similar situation at our end. There is a dsn with the following
atribute:
Expire after Days Non-usage . : 365.
Migration Attributes
Hmmm, will this thread ever *expires* ? :-D ;-D :-D
Staller, Allan wrote:
Minor correction:
Thanks.
After 4 days of non-usage, the dsn *will* migrate to ML1.
After 7 days of non-usage, it will migrate to ML2. If not already migrated
to ML1, it will migrate directly to ML2.
After 540
Thank you Bob.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Expire means deleted and uncatalogued.
Backups (if any) are handled as described in the MGMTCLAS for the dataset.
This is an entirely different set of processing.
snip
Staller, Allan wrote:
Minor correction:
Thanks.
After 4 days of non-usage, the dsn *will* migrate to ML1.
After 7 days of
Staller, Allan wrote:
Expire means deleted and uncatalogued.
Thanks. That will settle some burning issues with my storage admin who think it
is RACF, but I could prove it is HSM.
Backups (if any) are handled as described in the MGMTCLAS for the dataset.
This is an entirely different set of
Thanks for the tip. This is very handy.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
]
On Behalf Of Willie Bunter
Sent: Wednesday, October 29, 2014 6:14 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: DFHSM QUESTION - EXPIRATION OF DSN
Bob,
We have a similar situation at our end. There is a dsn with the following
atribute:
Expire after Days Non-usage . : 365.
Migration
W dniu 2014-10-29 o 18:47, Gibney, Dave pisze:
HSM will happily back-up empty datasets. INVALID datasets are another matter.
But, it is an easy matter to define a DEFAULT DATACLAS with DSORG=PS and never
have another invalid dataset.
True.
However I would prefer to have some feature to avoid
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
On Behalf Of R.S.
Sent: Wednesday, October 29, 2014 2:39 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: DFHSM QUESTION - EXPIRATION OF DSN
W dniu 2014-10-29 o 18:47, Gibney, Dave pisze:
HSM
On Oct 29, 2014, at 4:39 PM, R.S. wrote:
W dniu 2014-10-29 o 18:47, Gibney, Dave pisze:
HSM will happily back-up empty datasets. INVALID datasets are
another matter. But, it is an easy matter to define a DEFAULT
DATACLAS with DSORG=PS and never have another invalid dataset.
True.
However
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
On Behalf Of Ed Gould
Sent: Wednesday, October 29, 2014 4:04 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: DFHSM QUESTION - EXPIRATION OF DSN
On Oct 29, 2014, at 4:39 PM, R.S. wrote:
W dniu
On Oct 29, 2014, at 6:14 PM, Gibney, Dave wrote:
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
On Behalf Of Ed Gould
Sent: Wednesday, October 29, 2014 4:04 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: DFHSM QUESTION - EXPIRATION OF DSN
On Oct
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
On Behalf Of Ed Gould
Sent: Wednesday, October 29, 2014 4:19 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: DFHSM QUESTION - EXPIRATION OF DSN
On Oct 29, 2014, at 6:14 PM, Gibney, Dave wrote
Esmie,
If I am you, I will do the following to find out for myself what the state
of affairs are.
I will create a dataset with
Expiration Attributes
Expire after Days Non-usage . : 10
Expire after Date/Days . . . . : NOLIMIT
Retention Limit . . . . . . . : 0
Migration Attributes
On Oct 29, 2014, at 6:44 PM, Gibney, Dave wrote:
--
SNIP-
-
From the comment it could have been a dataset that didn't have a
local
standard name.
I had a standard (DASD) that if it didn't have a
Ed Gould wrote:
There are still quite a few items that DFDSS hasn't caught up with but thats a
different horse to flog. Although I was reading an article about z/OS and
there are a few things percolating up the like dynamic DASD and the like that
will make us wonder why it took so long.
27 matches
Mail list logo
