Hi listers,
Recently, we have added a list of SMS volumes to DB2's pool and they
were mod-9 volumes. The mgmtclass of these
DB2 archived logs is to migrate them after 1 day which is the same as
those that were migrated.
But..those they were on these mod-9 volumes did not get migrated...
DB2P.A
Chiam, Susan Mee-Shia wrote:
Hi listers,
Recently, we have added a list of SMS volumes to DB2's pool and they
were mod-9 volumes. The mgmtclass of these
DB2 archived logs is to migrate them after 1 day which is the same as
those that were migrated.
But..those they were on these mod-9 volumes
-- snip --
I could manually migrate the dataset off but what is stopping HSM doing
it automatically?
Any ideas? Thanking in advance.
-- snip --
Take a look at your SMS Storage Group Migrate High/Low settings.
John
--
For IBM-MAI
Probably the low theshold on the volume.
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Chiam, Susan Mee-Shia
Sent: Friday, November 18, 2005 4:29 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: HSM migrate
Hi listers,
Recently, we have
Try to change 'low theshold' in SG to value = 1
Chiam, Susan Mee-Shia wrote:
Hi listers,
Recently, we have added a list of SMS volumes to DB2's pool and they
were mod-9 volumes. The mgmtclass of these
DB2 archived logs is to migrate them after 1 day which is the same as
those that were migrat
ovember 2005 8:38 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: HSM migrate
Try to change 'low theshold' in SG to value = 1
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED]
I'm trying to clean up a mess.
I have same datasets that show up in P.3.4 as Migrat2
If I do a listcat of the user catalog they show as volser---migrat
But when I go to recall or hdelete them
ARC1001I KSPAINH.AAAMICH.SMF DELETE FAILED, RC=0002, REAS=
ARC1102I DATA SET IS NOT MIGRATED/BACKE
Mark,
to get rid of catalog entries that point to migrated, non-existent datasets, you
need to run a batch job IDCAMS and DELETE that dataset there. Using TSO or ISPF
commands will always fail ... they do more checking and are too smart for their
own good in this particular instance.
Regards,
Ulri
you'll need to be in the racf group ARCCATGP to do del noscr. see hsm
storage admin guide, 4.8.12
Jack Kelly
LA Systems @ US Courts
x 202-502-2390
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to
Yes I've tried a few different combinations of IDCAMS DELETE - most give me
IDC3007I ** VSAM CATALOG RETURN CODE IS 38
38 = Dataset has been migrated.
Mark D Pace
Senior Systems Engineer
Mainline Information Systems
1700 Summit Lake Drive
Tallahassee, FL. 32317
Office: 850.219.5184
Fax: 888.22
> -Original Message-
> From: IBM Mainframe Discussion List
> [mailto:[EMAIL PROTECTED] On Behalf Of Mark Pace
> Sent: Thursday, March 30, 2006 12:51 PM
> To: IBM-MAIN@BAMA.UA.EDU
> Subject: HSM Migrate issue
>
>
> I'm trying to clean up a mess.
>
>
> -Original Message-
> From: IBM Mainframe Discussion List On Behalf Of Mark Pace
>
> I'm trying to clean up a mess.
>
> I have same datasets that show up in P.3.4 as Migrat2
> If I do a listcat of the user catalog they show as volser---migrat
>
> But when I go to recall or hdelete the
>you'll need to be in the racf group ARCCATGP to do del noscr. see hsm
>storage admin guide, 4.8.12
Thanks!
Mark D Pace
Senior Systems Engineer
Mainline Information Systems
1700 Summit Lake Drive
Tallahassee, FL. 32317
Office: 850.219.5184
Fax: 888.221.9862
http://www.mainline.com
This e-mail
If you have RACF you can use a standard IDCAMS delete noscratch with
the
RACF storage admin parm in your job card.
// USER=userid,GROUP=ARCCATGP,PASSWORD=,
//*
//HSM EXEC PGM=IDCAMS
Listers,
Has anyone run into a problem with HSM Interval Migration (single task)
causing CPU to spike?
As reported by IOF monitor HSM is not using all that much <10% but the box
ifself is at 100% as reported CMF LPARSTAR cmd.
Stop Automigration and CPU immediately drops to 29.2 (combined prod
15 matches
Mail list logo