Re: Setting Interval Migration to 6 hour interval
And what's the time interval from when these 2 interval migrations started? I could be wrong, but I believe, the interval is calculated from one start time to the next start, not from one end time to the next start. Regards, Ulrich Krueger -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of O'Brien, David W. (NIH/CIT) [C] Sent: Thursday, August 05, 2010 09:35 To: IBM-MAIN@bama.ua.edu Subject: Setting Interval Migration to 6 hour interval We are recently upgraded to Zos 1.11. According to the manual: To calculate the value to use in a patch of the MGCB, start with the desired number of hours for your interval, multiply by 60, and then add 30. For example, if you want the interval to be two hours, the value is (2*60)+30 = 150. Issue the following PATCH command: E e e PATCH .MGCB.+60 X'0096'/* 150 minutes */ e If a 2 hour interval is 120 + 30 = 150 then it follows that a 6 hour interval would be (6x60) + 30 = 390 which converts to x'186' PATCH .MGCB.+60 X'0186' So why did I get the following: 06.01.33 STC07027 ARC0581I INTERVAL MIGRATION ENDED SUCCESSFULLY AT 133 133 ARC0581I (CONT.) 06:01:32 ON 2010/08/05 10.05.00 STC07027 ARC0581I INTERVAL MIGRATION ENDED SUCCESSFULLY AT 200 200 ARC0581I (CONT.) 10:04:59 ON 2010/08/05 4 hours is not 6, any suggestions as to what I did wrong? Thank You, Dave O'Brien NIH Contractor -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Setting Interval Migration to 6 hour interval
Ulrich, Good catch. My 4AM Interval ran for just over 2 hours. I never would have expected that. I think I'll add a subtask or two. Thank You, Dave O'Brien NIH Contractor From: Ulrich Krueger [u...@pacbell.net] Sent: Thursday, August 05, 2010 1:29 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Setting Interval Migration to 6 hour interval And what's the time interval from when these 2 interval migrations started? I could be wrong, but I believe, the interval is calculated from one start time to the next start, not from one end time to the next start. Regards, Ulrich Krueger -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of O'Brien, David W. (NIH/CIT) [C] Sent: Thursday, August 05, 2010 09:35 To: IBM-MAIN@bama.ua.edu Subject: Setting Interval Migration to 6 hour interval We are recently upgraded to Zos 1.11. According to the manual: To calculate the value to use in a patch of the MGCB, start with the desired number of hours for your interval, multiply by 60, and then add 30. For example, if you want the interval to be two hours, the value is (2*60)+30 = 150. Issue the following PATCH command: E e e PATCH .MGCB.+60 X'0096'/* 150 minutes */ e If a 2 hour interval is 120 + 30 = 150 then it follows that a 6 hour interval would be (6x60) + 30 = 390 which converts to x'186' PATCH .MGCB.+60 X'0186' So why did I get the following: 06.01.33 STC07027 ARC0581I INTERVAL MIGRATION ENDED SUCCESSFULLY AT 133 133 ARC0581I (CONT.) 06:01:32 ON 2010/08/05 10.05.00 STC07027 ARC0581I INTERVAL MIGRATION ENDED SUCCESSFULLY AT 200 200 ARC0581I (CONT.) 10:04:59 ON 2010/08/05 4 hours is not 6, any suggestions as to what I did wrong? Thank You, Dave O'Brien NIH Contractor -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Setting Interval Migration to 6 hour interval
The first one after midnight is always busy migrating those datasets that crossed the number of days boundary. On Thu, Aug 5, 2010 at 1:00 PM, O'Brien, David W. (NIH/CIT) [C] obrie...@mail.nih.gov wrote: Ulrich, Good catch. My 4AM Interval ran for just over 2 hours. I never would have expected that. I think I'll add a subtask or two. Thank You, Dave O'Brien NIH Contractor -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Setting Interval Migration to 6 hour interval
Yes, I would expect that the first occurance after midnight to be the busiest. Just not 2 hours worth. Thank You, Dave O'Brien NIH Contractor From: Mike Schwab [mike.a.sch...@gmail.com] Sent: Thursday, August 05, 2010 2:05 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Setting Interval Migration to 6 hour interval The first one after midnight is always busy migrating those datasets that crossed the number of days boundary. On Thu, Aug 5, 2010 at 1:00 PM, O'Brien, David W. (NIH/CIT) [C] obrie...@mail.nih.gov wrote: Ulrich, Good catch. My 4AM Interval ran for just over 2 hours. I never would have expected that. I think I'll add a subtask or two. Thank You, Dave O'Brien NIH Contractor -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
