DFSMSHSM migration spanning volumes
I have ML2 data spanning volumes. My question is - does anyone know of a way to identify the dataset that is causing migration to span volumes?. I have used parameters to minimize the possibility of spanning volumes but I do get the occasional dataset that causes this situation. Any input would be appreciated. Thank you -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: DFSMSHSM migration spanning volumes
Try the following commands. HSEND LIST TTOC SELECT(CONNECTED) TERMINAL or HSEND LIST TTOC SELECT(CONNECTED) ODS(dsn) HSEND LIST TTOC SELECT(EXCESSIVEVOLUMES) ODS(dsn) http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/DGT2S440/24.4 .16?SHELF=EZ2ZO10GDT=2005071036 -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Aldridge Murrell Sent: Thursday, March 01, 2007 6:28 AM To: IBM-MAIN@BAMA.UA.EDU Subject: DFSMSHSM migration spanning volumes I have ML2 data spanning volumes. My question is - does anyone know of a way to identify the dataset that is causing migration to span volumes?. I have used parameters to minimize the possibility of spanning volumes but I do get the occasional dataset that causes this situation. Any input would be appreciated. Thank you -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: DFSMSHSM migration spanning volumes
i still do it the old fashion way. i list the second volume with 'list ttoc .dsi' and dsn 01 is the one that spanned. if i can, i recall that dsn and break the connectin. Jack Kelly LA Systems @ US Courts x 202-502-2390 Aldridge Murrell [EMAIL PROTECTED] Sent by: IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU 03/01/2007 07:27 AM Please respond to IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU To IBM-MAIN@BAMA.UA.EDU cc Subject DFSMSHSM migration spanning volumes I have ML2 data spanning volumes. My question is - does anyone know of a way to identify the dataset that is causing migration to span volumes?. I have used parameters to minimize the possibility of spanning volumes but I do get the occasional dataset that causes this situation. Any input would be appreciated. Thank you -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] 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 [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: DFSMSHSM migration spanning volumes
Jack, Do we assume that you have the RECONNECT option turned off? -Original Message- From: Jack Kelly Sent: Thursday, March 01, 2007 9:33 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: DFSMSHSM migration spanning volumes i still do it the old fashion way. i list the second volume with 'list ttoc .dsi' and dsn 01 is the one that spanned. if i can, i recall that dsn and break the connectin. Jack Kelly LA Systems @ US Courts -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: DFSMSHSM migration spanning volumes
no i use reconnect but the users usually change the large dsn, so it goes back to a different tape. now that i've said that, they'll always reconnect Jack Kelly LA Systems @ US Courts x 202-502-2390 O'Brien, David W. (NIH/CIT) [C] [EMAIL PROTECTED] Sent by: IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU 03/01/2007 09:49 AM Please respond to IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU To IBM-MAIN@BAMA.UA.EDU cc Subject Re: DFSMSHSM migration spanning volumes Jack, Do we assume that you have the RECONNECT option turned off? -Original Message- From: Jack Kelly Sent: Thursday, March 01, 2007 9:33 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: DFSMSHSM migration spanning volumes i still do it the old fashion way. i list the second volume with 'list ttoc .dsi' and dsn 01 is the one that spanned. if i can, i recall that dsn and break the connectin. Jack Kelly LA Systems @ US Courts -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] 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 [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: DFSMSHSM migration spanning volumes
Thank you - this works great. I will look into the reconnect. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: DFSMSHSM migration spanning volumes
Why are you concerned about the occasional spanned ML2 volume? -Original Message- From: Murrell, Aldridge (CDC) Sent: Thursday, March 01, 2007 10:31 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: DFSMSHSM migration spanning volumes Thank you - this works great. I will look into the reconnect. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] 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 [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: DFSMSHSM migration spanning volumes
We are using 40gb volumes for ML2 and am trying to minimize time for recall. Another reason is to keep all data on single volumes. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: DFSMSHSM migration spanning volumes
Likewise I am also using 40gb tape for my ML2 data. Recall of the second dataset on the second volume took 23 seconds, a bit below my average of 27 seconds. Recall of the dataset causing the connection took 1 min 15 seconds. Now I have 5 connected ML2 tape sets so I have 5 datasets that IF recalled will invoke 2 tape mounts taking significantly longer than average to recall. 5 datasets out of 1.3 million occurances. Somehow I don't see this as a significant problem. What is your tapespansize parameter set at? -Original Message- From: Murrell, Aldridge (CDC) Sent: Thursday, March 01, 2007 11:12 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: DFSMSHSM migration spanning volumes We are using 40gb volumes for ML2 and am trying to minimize time for recall. Another reason is to keep all data on single volumes. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] 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 [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
