Tony, The nice manual tells you to:
25, 26Reissue the command with one of the following valid MIGRATE commands for an SMS-managed volume: - MIGRATE VOLUME(volser) - MIGRATE VOLUME(volser MIGRATE(0)) [CONVERT] - MIGRATE VOLUME(volser) DAYS(0) [CONVERT] - MIGRATE VOLUME(volser MIGRATE) DAYS(0) [CONVERT] Richard Marchant RSA On Tue, Feb 21, 2017 at 4:46 PM, Tony Thigpen <[email protected]> wrote: > I just ran the following: > > MIGRATE VOLUME(HDGAC0 MIGRATE(365)) ML2 > > I got the following: > > ARC0570I COMMAND MIGRATION FOR HDGAC6 VOLUME(S) TERMINATED, RC=25 REASON=0 > > I don't understand what it is trying to tell me: > > 25 There is a space management request on an SMS-managed volume with DBA > or DBU specified, or a nonzero value of days on MIGRATE (days) or DAYS > (days) is specified on a MIGRATE command. > > Tony Thigpen > > Richards, Robert B. wrote on 02/05/2017 07:20 AM: > >> But, in my MGMTCLAS ACS routine, where everything is based on the storage >>> group setting, there are no specific IF statement for that storage group so >>> it appears that the default management class of "" (null) is assigned for >>> these files. >>> >> >> Don't you mean it is based on the SCyyyy setting? Because at this point, >> according to what you wrote, the SGYYYY has not been set because the SG >> routine sets it by the SC that was assigned in the SC routine. >> >> Sequence of invocation: DC to SC to MC to SG >> >> Based on this, MC can only set three ways: By DC, by SC or by the MC >> routine itself. >> >> 1) Changing the MC only affects NEWLY CREATED datasets >> 2) Yes >> >> -----Original Message----- >> From: IBM Mainframe Discussion List [mailto:[email protected]] On >> Behalf Of Tony Thigpen >> Sent: Friday, February 03, 2017 6:20 PM >> To: [email protected] >> Subject: HSM followup question >> >> For a specific file prefix, my STORCLAS ACS routine sets the storage >> class to SCyyyy. Then in my STORGRP ACS routine, that storage class causes >> the storage group to be set to SGyyyy. >> >> But, in my MGMTCLAS ACS routine, where everything is based on the storage >> group setting, there are no specific IF statement for that storage group so >> it appears that the default management class of "" >> (null) is assigned for these files. >> >> My assumption is that HSM is just going to ignore the files in this >> storage class and never migrate them. Yet, for these specific files, I >> actually want them migrated to tape so I think I need them assigned to a >> management class. (right/wrong?) >> >> Questions: >> 1) If I change the MGMTCLAS ACS routine so as to assign a real management >> class, will this affect existing files, or only newly created files? >> >> 2) These files are for an old system that is no longer used. Since I just >> want them migrated out to tape and left there forever, would it be better >> to just issue a: >> MIGRATE VOLUME(xxxxxx) MIGRATE(365) ML2 >> command and force the move to tape and not worry about setting up a valid >> management class for these files? >> >> -- >> Tony Thigpen >> >> ---------------------------------------------------------------------- >> 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 >> >> >> > ---------------------------------------------------------------------- > 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
