Re: ML1 to ML2
For the current ML1 data, you can issue the commands directly (hsend migrate dsn(x) ML2). There is a variation of the HSM LIST command that will show only the datasets on ML1. You will still need (at least) 1 ML1 volume if you are using the AUTODUMP feature. This is where HSM stores the VTOC copies used in volume recovery. For the data on Primary, I would set ML1 days equal to ML2 days in the Management Class definition.. HTH, snip What I want to have happen All migrations go directly to tape, no longer go to ML1 DASD. But I still have a lot of migrated data on ML1 I need to get to ML2. For that I suppose I can wait for it to roll off to ML2. I changed the TAPEMIGRATION( DIRECT) thinking that anything that migrated from this point forward would go to ML2 and not ML1. But, nope, issued an HMIG command against a dataset and it went to ML1. /snip -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ML1 to ML2
Allan, I think you mean set ML1 days equal to Primary days as there is no ML2 days parameter. Once that is done, data currently on ML1 should become eligible for migration to ML2 thus eliminating the need to issue the HLIST and subsequent HMIG / ML2 commands. Mark, What is the threshold value for your ML1 volumes? That might also be limiting your ability to migrate off of those volumes. It should be 1% as I don't think zero is valid. Thank You, Dave O'Brien NIH Contractor From: Staller, Allan [allan.stal...@kbmg.com] Sent: Monday, May 13, 2013 9:07 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ML1 to ML2 For the current ML1 data, you can issue the commands directly (hsend migrate dsn(x) ML2). There is a variation of the HSM LIST command that will show only the datasets on ML1. You will still need (at least) 1 ML1 volume if you are using the AUTODUMP feature. This is where HSM stores the VTOC copies used in volume recovery. For the data on Primary, I would set ML1 days equal to ML2 days in the Management Class definition.. HTH, snip What I want to have happen All migrations go directly to tape, no longer go to ML1 DASD. But I still have a lot of migrated data on ML1 I need to get to ML2. For that I suppose I can wait for it to roll off to ML2. I changed the TAPEMIGRATION( DIRECT) thinking that anything that migrated from this point forward would go to ML2 and not ML1. But, nope, issued an HMIG command against a dataset and it went to ML1. /snip -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ML1 to ML2
Agreed. You are correct. I was just about to post an update. To my reponse.. Al Staller | Z Systems Programmer | KBM Group | (Tel) 972 664-3565 | allan.stal...@kbmg.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of O'Brien, David W. (NIH/CIT) [C] Sent: Monday, May 13, 2013 8:22 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ML1 to ML2 Allan, I think you mean set ML1 days equal to Primary days as there is no ML2 days parameter. Once that is done, data currently on ML1 should become eligible for migration to ML2 thus eliminating the need to issue the HLIST and subsequent HMIG / ML2 commands. Mark, What is the threshold value for your ML1 volumes? That might also be limiting your ability to migrate off of those volumes. It should be 1% as I don't think zero is valid. Thank You, Dave O'Brien NIH Contractor -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ML1 to ML2
Mark, When you altered your environment to ignore ML2, did you change any of your migration criteria such as ML1days for non-sms data or your SMS Management class Level 1 days value? These would need to be equal to your Primary days value to bypass ML1. Thank You, Dave O'Brien NIH Contractor From: Mark Pace [pacemainl...@gmail.com] Sent: Friday, May 10, 2013 4:43 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ML1 to ML2 What I want to have happen All migrations go directly to tape, no longer go to ML1 DASD. But I still have a lot of migrated data on ML1 I need to get to ML2. For that I suppose I can wait for it to roll off to ML2. I changed the TAPEMIGRATION( DIRECT) thinking that anything that migrated from this point forward would go to ML2 and not ML1. But, nope, issued an HMIG command against a dataset and it went to ML1. Guess I'll start fresh on Monday. :( On Fri, May 10, 2013 at 4:35 PM, Staller, Allan allan.stal...@kbmg.comwrote: I'm out of ideas here. snip Yes - those are defined. They worked previously. The only difference I can determine is that the old 3494 was an automated tape library, and the new VTS is a manual tape library. No I have to qualify that it worked. This command worked. hsend migrate dsname(MARPACE.Z114.IOCP) ml2 This command did not work. Once again it just moved datasets on that ML1 volume to another DASD volume, not to tape. hsend freevol mvol(big000) targetlevel(ml2(tape)) /snip The parameter TAPE(TAPELIB) is used to provide an esoteric name. Was TAPELIB a valid esoteric? This name must also be in the USERUNITTABLE. Otherwise, IIRC, only IBM generics can be used (e.g. 3590-1) e.g. SETSYS USERUNITTABLE(ECART,FAST,9940B,VIRT) HTH, snip Hmm - I changed SETSYS - TAPEMIGRATION(ML2TAPE(TAPE(TAPELIB)) RECONNECT(ALL)) SETSYS - TAPEMIGRATION(ML2TAPE RECONNECT(ALL)) And now it works. /snip -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- The postings on this site are my own and don’t necessarily represent Mainline’s positions or opinions Mark D Pace Senior Systems Engineer Mainline Information Systems -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
ML1 to ML2
A few months ago we removed out 3494 tape library. So I defined a bunch of 3390-54 DASD and moved all the ML2 data to ML1 DASD. We recenly installed a virtual tape system and now I want to move all of that ML1 back to ML2 tape. I've gone back through our old ARCCMDxx and updated the new one to enable ML2 tape again. Went through SMS and re-added everything tape relates. So now I want to move the data from ML1 to ML2 and tried this command. hsend freevol mvol(big000) targetlevel(ml2(tape)) But all the datasets are moved from BIG000 to another DASD volumes, not tape. so then I tried a single dataset hsend migrate dsname(MARPACE.Z114.IOCP) ml2 ARC1001I MARPACE.Z114.IOCP MIGRATE FAILED, RC=0034, REAS= ARC1234I LEVEL 2 NOT DEFINED FOR MIGRATION ARC1007I COMMAND REQUEST 3387 SENT TO DFSMSHSM Level 2 not defined? From my ARCCMDxx SETSYS TAPEMIGRATION(ML2TAPE(TAPE(TAPELIB)) RECONNECT(ALL)) /* TAPEMIGRATION(DIRECT(TAPE(TAPELIB)) RECONNECT(ALL)) */ I tried both of these parameters, but neither worked. I know this has to be something super easy and that's why I'm over looking it. -- The postings on this site are my own and don’t necessarily represent Mainline’s positions or opinions Mark D Pace Senior Systems Engineer Mainline Information Systems -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ML1 to ML2
F DFHSM,Q SETSYS will verify. SETSYS TAPEMIGRATION(ML2TAPE(TAPE(TAPELIB)) RECONNECT(ALL)) s/b SETSYS + (note plus sign = Continuation character) TAPEMIGRATION(ML2TAPE(TAPE(TAPELIB)) RECONNECT(ALL)) Al Staller | Z Systems Programmer | KBM Group | (Tel) 972 664-3565 | allan.stal...@kbmg.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Mark Pace Sent: Friday, May 10, 2013 2:13 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: ML1 to ML2 A few months ago we removed out 3494 tape library. So I defined a bunch of 3390-54 DASD and moved all the ML2 data to ML1 DASD. We recenly installed a virtual tape system and now I want to move all of that ML1 back to ML2 tape. I've gone back through our old ARCCMDxx and updated the new one to enable ML2 tape again. Went through SMS and re-added everything tape relates. So now I want to move the data from ML1 to ML2 and tried this command. hsend freevol mvol(big000) targetlevel(ml2(tape)) But all the datasets are moved from BIG000 to another DASD volumes, not tape. so then I tried a single dataset hsend migrate dsname(MARPACE.Z114.IOCP) ml2 ARC1001I MARPACE.Z114.IOCP MIGRATE FAILED, RC=0034, REAS= ARC1234I LEVEL 2 NOT DEFINED FOR MIGRATION ARC1007I COMMAND REQUEST 3387 SENT TO DFSMSHSM Level 2 not defined? From my ARCCMDxx SETSYS TAPEMIGRATION(ML2TAPE(TAPE(TAPELIB)) RECONNECT(ALL)) /* TAPEMIGRATION(DIRECT(TAPE(TAPELIB)) RECONNECT(ALL)) */ I tried both of these parameters, but neither worked. I know this has to be something super easy and that's why I'm over looking it. -- The postings on this site are my own and don't necessarily represent Mainline's positions or opinions Mark D Pace Senior Systems Engineer Mainline Information Systems -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ML1 to ML2
TAPEMIGRATION=NONE(ROUTETOTAPE(ANY)), MIGDENSITY=*, MIGUNIT=3590-1, (CONT.) ML2 RECYCLE PERCENTAGE=080%, TAPEMAXRECALLTASKS=01, ML2 (CONT.) PARTIALS NOT ASSOCIATED GOAL=000, RECONNECT(ALL) I had cut off part of the command there is a minus sign way out at the end. The comment is currently incorrect. But according that that query command it appears that tape migration is off. SETSYS /* NO ML2 MIGRATION */ - TAPEMIGRATION(ML2TAPE(TAPE(TAPELIB)) RECONNECT(ALL)) /* TAPEMIGRATION(DIRECT(TAPE(TAPELIB)) RECONNECT(ALL)) */ On Fri, May 10, 2013 at 3:32 PM, Staller, Allan allan.stal...@kbmg.comwrote: F DFHSM,Q SETSYS will verify. SETSYS TAPEMIGRATION(ML2TAPE(TAPE(TAPELIB)) RECONNECT(ALL)) s/b SETSYS + (note plus sign = Continuation character) TAPEMIGRATION(ML2TAPE(TAPE(TAPELIB)) RECONNECT(ALL)) Al Staller | Z Systems Programmer | KBM Group | (Tel) 972 664-3565 | allan.stal...@kbmg.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Mark Pace Sent: Friday, May 10, 2013 2:13 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: ML1 to ML2 A few months ago we removed out 3494 tape library. So I defined a bunch of 3390-54 DASD and moved all the ML2 data to ML1 DASD. We recenly installed a virtual tape system and now I want to move all of that ML1 back to ML2 tape. I've gone back through our old ARCCMDxx and updated the new one to enable ML2 tape again. Went through SMS and re-added everything tape relates. So now I want to move the data from ML1 to ML2 and tried this command. hsend freevol mvol(big000) targetlevel(ml2(tape)) But all the datasets are moved from BIG000 to another DASD volumes, not tape. so then I tried a single dataset hsend migrate dsname(MARPACE.Z114.IOCP) ml2 ARC1001I MARPACE.Z114.IOCP MIGRATE FAILED, RC=0034, REAS= ARC1234I LEVEL 2 NOT DEFINED FOR MIGRATION ARC1007I COMMAND REQUEST 3387 SENT TO DFSMSHSM Level 2 not defined? From my ARCCMDxx SETSYS TAPEMIGRATION(ML2TAPE(TAPE(TAPELIB)) RECONNECT(ALL)) /* TAPEMIGRATION(DIRECT(TAPE(TAPELIB)) RECONNECT(ALL)) */ I tried both of these parameters, but neither worked. I know this has to be something super easy and that's why I'm over looking it. -- The postings on this site are my own and don't necessarily represent Mainline's positions or opinions Mark D Pace Senior Systems Engineer Mainline Information Systems -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- The postings on this site are my own and don’t necessarily represent Mainline’s positions or opinions Mark D Pace Senior Systems Engineer Mainline Information Systems -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ML1 to ML2
Hmm - I changed SETSYS - TAPEMIGRATION(ML2TAPE(TAPE(TAPELIB)) RECONNECT(ALL)) SETSYS - TAPEMIGRATION(ML2TAPE RECONNECT(ALL)) And now it works. On Fri, May 10, 2013 at 3:42 PM, Mark Pace pacemainl...@gmail.com wrote: TAPEMIGRATION=NONE(ROUTETOTAPE(ANY)), MIGDENSITY=*, MIGUNIT=3590-1, (CONT.) ML2 RECYCLE PERCENTAGE=080%, TAPEMAXRECALLTASKS=01, ML2 (CONT.) PARTIALS NOT ASSOCIATED GOAL=000, RECONNECT(ALL) I had cut off part of the command there is a minus sign way out at the end. The comment is currently incorrect. But according that that query command it appears that tape migration is off. SETSYS /* NO ML2 MIGRATION */ - TAPEMIGRATION(ML2TAPE(TAPE(TAPELIB)) RECONNECT(ALL)) /* TAPEMIGRATION(DIRECT(TAPE(TAPELIB)) RECONNECT(ALL)) */ On Fri, May 10, 2013 at 3:32 PM, Staller, Allan allan.stal...@kbmg.comwrote: F DFHSM,Q SETSYS will verify. SETSYS TAPEMIGRATION(ML2TAPE(TAPE(TAPELIB)) RECONNECT(ALL)) s/b SETSYS + (note plus sign = Continuation character) TAPEMIGRATION(ML2TAPE(TAPE(TAPELIB)) RECONNECT(ALL)) Al Staller | Z Systems Programmer | KBM Group | (Tel) 972 664-3565 | allan.stal...@kbmg.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Mark Pace Sent: Friday, May 10, 2013 2:13 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: ML1 to ML2 A few months ago we removed out 3494 tape library. So I defined a bunch of 3390-54 DASD and moved all the ML2 data to ML1 DASD. We recenly installed a virtual tape system and now I want to move all of that ML1 back to ML2 tape. I've gone back through our old ARCCMDxx and updated the new one to enable ML2 tape again. Went through SMS and re-added everything tape relates. So now I want to move the data from ML1 to ML2 and tried this command. hsend freevol mvol(big000) targetlevel(ml2(tape)) But all the datasets are moved from BIG000 to another DASD volumes, not tape. so then I tried a single dataset hsend migrate dsname(MARPACE.Z114.IOCP) ml2 ARC1001I MARPACE.Z114.IOCP MIGRATE FAILED, RC=0034, REAS= ARC1234I LEVEL 2 NOT DEFINED FOR MIGRATION ARC1007I COMMAND REQUEST 3387 SENT TO DFSMSHSM Level 2 not defined? From my ARCCMDxx SETSYS TAPEMIGRATION(ML2TAPE(TAPE(TAPELIB)) RECONNECT(ALL)) /* TAPEMIGRATION(DIRECT(TAPE(TAPELIB)) RECONNECT(ALL)) */ I tried both of these parameters, but neither worked. I know this has to be something super easy and that's why I'm over looking it. -- The postings on this site are my own and don't necessarily represent Mainline's positions or opinions Mark D Pace Senior Systems Engineer Mainline Information Systems -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- The postings on this site are my own and don’t necessarily represent Mainline’s positions or opinions Mark D Pace Senior Systems Engineer Mainline Information Systems -- The postings on this site are my own and don’t necessarily represent Mainline’s positions or opinions Mark D Pace Senior Systems Engineer Mainline Information Systems -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ML1 to ML2
Yes - those are defined. They worked previously. The only difference I can determine is that the old 3494 was an automated tape library, and the new VTS is a manual tape library. No I have to qualify that it worked. This command worked. hsend migrate dsname(MARPACE.Z114.IOCP) ml2 This command did not work. Once again it just moved datasets on that ML1 volume to another DASD volume, not to tape. hsend freevol mvol(big000) targetlevel(ml2(tape)) On Fri, May 10, 2013 at 4:01 PM, Staller, Allan allan.stal...@kbmg.comwrote: The parameter TAPE(TAPELIB) is used to provide an esoteric name. Was TAPELIB a valid esoteric? This name must also be in the USERUNITTABLE. Otherwise, IIRC, only IBM generics can be used (e.g. 3590-1) e.g. SETSYS USERUNITTABLE(ECART,FAST,9940B,VIRT) HTH, snip Hmm - I changed SETSYS - TAPEMIGRATION(ML2TAPE(TAPE(TAPELIB)) RECONNECT(ALL)) SETSYS - TAPEMIGRATION(ML2TAPE RECONNECT(ALL)) And now it works. /snip -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- The postings on this site are my own and don’t necessarily represent Mainline’s positions or opinions Mark D Pace Senior Systems Engineer Mainline Information Systems -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ML1 to ML2
Okay - after a little more research on the ADDVOL command I think I am now up against an SMS problem. I thought I had put all the Management Class back to the way they were before, but I'm thinking I still have something wrong. On Fri, May 10, 2013 at 4:05 PM, Mark Pace pacemainl...@gmail.com wrote: Yes - those are defined. They worked previously. The only difference I can determine is that the old 3494 was an automated tape library, and the new VTS is a manual tape library. No I have to qualify that it worked. This command worked. hsend migrate dsname(MARPACE.Z114.IOCP) ml2 This command did not work. Once again it just moved datasets on that ML1 volume to another DASD volume, not to tape. hsend freevol mvol(big000) targetlevel(ml2(tape)) On Fri, May 10, 2013 at 4:01 PM, Staller, Allan allan.stal...@kbmg.comwrote: The parameter TAPE(TAPELIB) is used to provide an esoteric name. Was TAPELIB a valid esoteric? This name must also be in the USERUNITTABLE. Otherwise, IIRC, only IBM generics can be used (e.g. 3590-1) e.g. SETSYS USERUNITTABLE(ECART,FAST,9940B,VIRT) HTH, snip Hmm - I changed SETSYS - TAPEMIGRATION(ML2TAPE(TAPE(TAPELIB)) RECONNECT(ALL)) SETSYS - TAPEMIGRATION(ML2TAPE RECONNECT(ALL)) And now it works. /snip -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- The postings on this site are my own and don’t necessarily represent Mainline’s positions or opinions Mark D Pace Senior Systems Engineer Mainline Information Systems -- The postings on this site are my own and don’t necessarily represent Mainline’s positions or opinions Mark D Pace Senior Systems Engineer Mainline Information Systems -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ML1 to ML2
I'm out of ideas here. snip Yes - those are defined. They worked previously. The only difference I can determine is that the old 3494 was an automated tape library, and the new VTS is a manual tape library. No I have to qualify that it worked. This command worked. hsend migrate dsname(MARPACE.Z114.IOCP) ml2 This command did not work. Once again it just moved datasets on that ML1 volume to another DASD volume, not to tape. hsend freevol mvol(big000) targetlevel(ml2(tape)) /snip The parameter TAPE(TAPELIB) is used to provide an esoteric name. Was TAPELIB a valid esoteric? This name must also be in the USERUNITTABLE. Otherwise, IIRC, only IBM generics can be used (e.g. 3590-1) e.g. SETSYS USERUNITTABLE(ECART,FAST,9940B,VIRT) HTH, snip Hmm - I changed SETSYS - TAPEMIGRATION(ML2TAPE(TAPE(TAPELIB)) RECONNECT(ALL)) SETSYS - TAPEMIGRATION(ML2TAPE RECONNECT(ALL)) And now it works. /snip -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ML1 to ML2
What I want to have happen All migrations go directly to tape, no longer go to ML1 DASD. But I still have a lot of migrated data on ML1 I need to get to ML2. For that I suppose I can wait for it to roll off to ML2. I changed the TAPEMIGRATION( DIRECT) thinking that anything that migrated from this point forward would go to ML2 and not ML1. But, nope, issued an HMIG command against a dataset and it went to ML1. Guess I'll start fresh on Monday. :( On Fri, May 10, 2013 at 4:35 PM, Staller, Allan allan.stal...@kbmg.comwrote: I'm out of ideas here. snip Yes - those are defined. They worked previously. The only difference I can determine is that the old 3494 was an automated tape library, and the new VTS is a manual tape library. No I have to qualify that it worked. This command worked. hsend migrate dsname(MARPACE.Z114.IOCP) ml2 This command did not work. Once again it just moved datasets on that ML1 volume to another DASD volume, not to tape. hsend freevol mvol(big000) targetlevel(ml2(tape)) /snip The parameter TAPE(TAPELIB) is used to provide an esoteric name. Was TAPELIB a valid esoteric? This name must also be in the USERUNITTABLE. Otherwise, IIRC, only IBM generics can be used (e.g. 3590-1) e.g. SETSYS USERUNITTABLE(ECART,FAST,9940B,VIRT) HTH, snip Hmm - I changed SETSYS - TAPEMIGRATION(ML2TAPE(TAPE(TAPELIB)) RECONNECT(ALL)) SETSYS - TAPEMIGRATION(ML2TAPE RECONNECT(ALL)) And now it works. /snip -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- The postings on this site are my own and don’t necessarily represent Mainline’s positions or opinions Mark D Pace Senior Systems Engineer Mainline Information Systems -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
