Hi Mike,
i think you have 2 basic problems.
The first is that "primary days" in your mgmtclas definition is set to blank,
and as far as hsm is concerned, the default is 2 days if there is no entry.
Which leads onto the second problem, and it looks like your job scheduler
allocates but does not o
Another reason it can be migrated is by space migration due to the volume
passing the %use threshold. If that happens, then HSM will migrate data from
the volume until it reaches the low use threshold. It's easy to fix once you
realize what is happening.
Brian
Syzygy Inc.
---
595 Mobile
jo.skip.robin...@sce.com
From: Lizette Koehler
To: IBM-MAIN@LISTSERV.UA.EDU,
Date: 02/21/2014 08:33 AM
Subject: Re: Why does a dataset that should never migrate does
occassionally (hsm)
Sent by:IBM Mainframe Discussion List
Is it possible someone might b
to:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Michael Bieganski
> Sent: Friday, February 21, 2014 9:16 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Why does a dataset that should never migrate does occassionally
(hsm)
>
> Hi, we have a mainframe dataset that is used daily used in ou
: Michael Bieganski
To: IBM-MAIN
Sent: Fri, Feb 21, 2014 8:16 am
Subject: Why does a dataset that should never migrate does occassionally (hsm)
Hi, we have a mainframe dataset that is used daily used in our automated
cheduling processes.
ccassionally, our ops support gets paged out because a
We have an SMS management class which stops that. It does it by setting the
"CMD/AUTO MIGRATE" to NONE.
On Fri, Feb 21, 2014 at 10:15 AM, Michael Bieganski
wrote:
> Hi, we have a mainframe dataset that is used daily used in our automated
> scheduling processes.
> Occassionally, our ops support g
Hi, we have a mainframe dataset that is used daily used in our automated
scheduling processes.
Occassionally, our ops support gets paged out because a process is delayed
and it turns out it was because
said dataset was migrated and had to be recalled.
this dataset's management class has nolimit on