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 open the dataset until it needs its, so the last
referenced date field does not get updated untill you run your plans or a job
is submitted from it
(if its a job library).
Getting migrated is a big indicator that the dsn is free at that point and not
allocated.
As per other repliers, checking the hsm logs for the dataset will tell you the
reason for the migration.
Also, as the other repliers have said, the simple way round it is to change the
mgmtclass to one where primary days is a decent figure (i.e 9999) or
cmd/migrate is none.
If you've already got suitable mgmtclas's available, a simple alter against the
dataset can change it and bring in your new one.
kind regards
Dave
***********************************************************************************************
>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 expires, and blanks for
>'Primary Days'
>Partial Release is 'yes' so could hsm be migrating this dsn in Primary
>space mgmt, despite we have
>primary-days set to blanks???
>And if so, short of setting partial release to no, how can we keep an sms
>managed dataset from ever migrating at all?
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
