Re: EMC 6000 Virtual Tape Drive
Our DCC product gives you the ability to query the DLM. Tso, batch, pc GUI, ispf interface. It can clone tapes into the dlm. Also can direct allocation so smstape does not need to be used. Www.dtssoftware.com Tom -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: EMC 6000 Virtual Tape Drive
So it's been a really long time since I set all this up, but I do remember I had to have a couple of special volumes defined in the library. These volumes were used to 'communicate' with the Bustech hardware. Below is the display for the 2 volumes from ISMF. VOLUME USE VOLUME CHECKPT LIBRARY SERIAL ATTRERROR STATUSVOLUME NAME BFLDRL PRIVATE NO ERROR--- LIBMVTS1 BFLLCL PRIVATE NO ERROR --- LIBMVTS1 VOLUME MEDIA RECORDING SPECIAL SERIAL TYPE TECHNOLOGY COMPACTIONATTRIBUTE BFLDRL MEDIA4128TRACK --- RDCOMPAT BFLLCL MEDIA4128TRACK --- RDCOMPAT I dont know why the client chose 2 different tape sizes. Seems illogical to me. The NL tapes I referenced had to do with running DLMCMD JCL which for the life of me I don't get. All I want to do is ask the machine is 1 - are you working and 2- what tape VOLSERs do you think you have defined inside of you? -- This e-mail message and all attachments transmitted with it may contain legally privileged and/or confidential information intended solely for the use of the addressee(s). If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, forwarding or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete this message and all copies and backups thereof. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: EMC 6000 Virtual Tape Drive
These are also not defined to my TMM (CA1). So it's been a really long time since I set all this up, but I do remember I had to have a couple of special volumes defined in the library. These volumes were used to 'communicate' with the Bustech hardware. Below is the display for the 2 volumes from ISMF. VOLUME USE VOLUME CHECKPT LIBRARY SERIAL ATTRERROR STATUSVOLUME NAME BFLDRL PRIVATE NO ERROR--- LIBMVTS1 BFLLCL PRIVATE NO ERROR --- LIBMVTS1 VOLUME MEDIA RECORDING SPECIAL SERIAL TYPE TECHNOLOGY COMPACTIONATTRIBUTE BFLDRL MEDIA4128TRACK --- RDCOMPAT BFLLCL MEDIA4128TRACK --- RDCOMPAT I dont know why the client chose 2 different tape sizes. Seems illogical to me. The NL tapes I referenced had to do with running DLMCMD JCL which for the life of me I don't get. All I want to do is ask the machine is 1 - are you working and 2- what tape VOLSERs do you think you have defined inside of you? -- This e-mail message and all attachments transmitted with it may contain legally privileged and/or confidential information intended solely for the use of the addressee(s). If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, forwarding or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete this message and all copies and backups thereof. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: EMC 6000 Virtual Tape Drive
On Tue, 7 May 2013 19:15:55 -0500, Mike Wojtukiewicz mw...@attglobal.net wrote: I dont know why the client chose 2 different tape sizes. Seems illogical to me. The NL tapes I referenced had to do with running DLMCMD JCL which for the life of me I don't get. All I want to do is ask the machine is 1 - are you working and 2- what tape VOLSERs do you think you have defined inside of you? Now I know what you are referring to with the NL tapes. DLMCMD is a utility to basically run linux scripts from the mainframe and return the output to the mainframe. The scripts do various things like report on library usage (space, scratch tapes etc), gather logs, print tape headers, gather / display statistics. It can also issue commands to the VTE (virtual tape engine) console and return the output.The NL tape is a special work virtual tape on the DLm that has to be initialized and contains the output of the utility / command that is read by an IEBGENER step to spool the output. At least that is how it works in the version I am using, but from what I understand this is or has been re-written and doesn't need IEBGENER now. Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:m...@mzelden.com Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: EMC 6000 Virtual Tape Drive
Thanks, Mark - not an issue I had considered either but one I will definitely keep in mind. However, as we don't share the box, it's probably pretty unlikely we'll run into the issue. ddk On Mon, 6 May 2013 14:34:23 -0500, Darth Keller darth.kel...@assurant.com wrote: Question - why do you need 2 sizes of tape? Seems like unnecessary complication to me. We defined it with very large virtual tape as, unlike the B20's, there is no space (or very little space) required for the tape when it's not in use. It only uses space enough to hold the data when it's written. When the tape is scratched, the used space is released back and only a very small amount is used for the tape label.Of course, the difference is once a tape goes scratch and the space is recovered, there's no reading the scratch tape. I can answer that one - at least from an EMC DLm perspective. I (we) found out the hard way that one size did not fit all. My client shares the DLms with about 9 environments (sysplexes and monoplex LPARs). Most of those libraries have a 40G virtual tape size. That size was chosen based on the STK 9840s were were migrating from as we got rid of all physical tape (also had VSM virtual). Out of these 9 environments the larger ones have from 15-50 file systems of 3-5TB per DLm. Some of the smaller ones have about 5 file systems with anywhere from 100GB to 500GB. About a month after cut over (done via SMS ACS routine changes of esoterics) we had an out of space condition on one of the smaller environments trying to create a virtual tape - even though the file system was only 61% full. Well guess what - 61% full of a 100GB leaves 39GB free and of course the virtual tape system has no way of knowing you aren't going to really create a 40GB tape when you want a scratch tape mounted. We expanded the file systems for that library that evening and then after we figured out what the real reason was we changed the virtual tape size for all the small environments from 40GB to 5GB and for this very small environment we made it 2GB. 2GB matched the size of the large VSM (STK) virtual tapes we were using (although most were still 800MB VTVs at the time of the migration). EMC planned all the file system sizes etc. with us. The implementation team that worked with us never mentioned (or thought of) this caveat when we decided to use 40GB as the virtual tape size for all the different libraries sharing the DLms. Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:m...@mzelden.com Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN This e-mail message and all attachments transmitted with it may contain legally privileged and/or confidential information intended solely for the use of the addressee(s). If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, forwarding or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete this message and all copies and backups thereof. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: EMC 6000 Virtual Tape Drive
It isn't really about sharing, it's really a matter of not choosing to use a large virtual tape size in a very small environment. If the total backing file systems are only 500GB - 1TB, you really don't want your virtual tape size to be 50GB. I went back and re-read the original post and it talked about 2 different tape sizes in the same environment, a different situation than I posted about. I never see a reason to do that. Just pick the right size to begin with and use one size. The original post also mentioned something about NL tapes that I didn't really understand, but it reminded me of something else I found out in the migration to DLm that wasn't talked about during the planning. The DLm doesn't support NL tapes. We had some jobs creating NL tapes on STK VSM. No reason they had to, but we did have to change them. -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:m...@mzelden.com Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ On Tue, 7 May 2013 07:58:02 -0500, Darth Keller darth.kel...@assurant.com wrote: Thanks, Mark - not an issue I had considered either but one I will definitely keep in mind. However, as we don't share the box, it's probably pretty unlikely we'll run into the issue. ddk On Mon, 6 May 2013 14:34:23 -0500, Darth Keller darth.kel...@assurant.com wrote: Question - why do you need 2 sizes of tape? Seems like unnecessary complication to me. We defined it with very large virtual tape as, unlike the B20's, there is no space (or very little space) required for the tape when it's not in use. It only uses space enough to hold the data when it's written. When the tape is scratched, the used space is released back and only a very small amount is used for the tape label.Of course, the difference is once a tape goes scratch and the space is recovered, there's no reading the scratch tape. I can answer that one - at least from an EMC DLm perspective. I (we) found out the hard way that one size did not fit all. My client shares the DLms with about 9 environments (sysplexes and monoplex LPARs). Most of those libraries have a 40G virtual tape size. That size was chosen based on the STK 9840s were were migrating from as we got rid of all physical tape (also had VSM virtual). Out of these 9 environments the larger ones have from 15-50 file systems of 3-5TB per DLm. Some of the smaller ones have about 5 file systems with anywhere from 100GB to 500GB. About a month after cut over (done via SMS ACS routine changes of esoterics) we had an out of space condition on one of the smaller environments trying to create a virtual tape - even though the file system was only 61% full. Well guess what - 61% full of a 100GB leaves 39GB free and of course the virtual tape system has no way of knowing you aren't going to really create a 40GB tape when you want a scratch tape mounted. We expanded the file systems for that library that evening and then after we figured out what the real reason was we changed the virtual tape size for all the small environments from 40GB to 5GB and for this very small environment we made it 2GB. 2GB matched the size of the large VSM (STK) virtual tapes we were using (although most were still 800MB VTVs at the time of the migration). EMC planned all the file system sizes etc. with us. The implementation team that worked with us never mentioned (or thought of) this caveat when we decided to use 40GB as the virtual tape size for all the different libraries sharing the DLms. Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:m...@mzelden.com Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- 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: EMC 6000 Virtual Tape Drive
The client I work for got this thing for nothing so therefore since they're NOT a paying customer no userid/password. Nice huh? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
EMC 6000 Virtual Tape Drive
Does anyone out there have ANY experience with the EMC DLm6000 virtual tape server. I am working for a MAJOR software developer who got one of these for free. They provided almost NO documentation. What little doc I have only peripherally talks about SMS routines, RMM, and how to run utilities. From what I can see you have to run a utulity pointing to an offline drive and run the output out the a NON Labeled tape and that print it off (WTF?). We have it setup with 2 esoterics; say 1 set of UCBs UNIT=LARGE for big tapes and UNIT=SMALL for small tapes. When I try and run a job I get a mount message for the exact OPPOSITE set of UCBS. ie I say UNIT=LARGE and one of the SMALL ucbs gets allocated. To make matters worse I have NO IDEA if there actually tapes loaded in it despite RMM having the VOLSERs in the TAPE LIBRARY and OAM is running and SYS1.VOLCAT.GENERAL is defined. Any help would be appreciated -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: EMC 6000 Virtual Tape Drive
The manuals can be downloaded. EMC should have provided someone in your organization with an Id and password to their website. If they didn't just ask your EMC contact. Bob Shannon Rocket Software -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: EMC 6000 Virtual Tape Drive
Do you have any experience with virtual tapes? We went from a couple of IBM B20 libraries to an HDS MDL which uses the Bustech (now EMC) to front-end HDS storage. We had to switch from SMS Automated Tape Libraries to a Manual Tape Library. We defined new tape ranges, dataclas, and storclass for the MDL. The MDL is defined with it's own range of tape UCB's. Seems like we had a separate Esoteric to use for testing and once we were ready, we just swapped the old Esoterics over to the new addresses. There is no physical tape involved anymore - just a big DASD buffer. Bustech was involved defining the internals to the MDL, setting up the storage, defining volumes. We did all this a few years ago, so the exact sequence of events is now a bit of a blur. But as I remember it,, it was all pretty straight forward by the book. Question - why do you need 2 sizes of tape? Seems like unnecessary complication to me. We defined it with very large virtual tape as, unlike the B20's, there is no space (or very little space) required for the tape when it's not in use. It only uses space enough to hold the data when it's written. When the tape is scratched, the used space is released back and only a very small amount is used for the tape label.Of course, the difference is once a tape goes scratch and the space is recovered, there's no reading the scratch tape. ddk Does anyone out there have ANY experience with the EMC DLm6000 virtual tape server. I am working for a MAJOR software developer who got one of these for free. They provided almost NO documentation. What little doc I have only peripherally talks about SMS routines, RMM, and how to run utilities. From what I can see you have to run a utility pointing to an offline drive and run the output out the a NON Labeled tape and that print it off (WTF?). We have it setup with 2 esoterics; say 1 set of UCBs UNIT=LARGE for big tapes and UNIT=SMALL for small tapes. When I try and run a job I get a mount message for the exact OPPOSITE set of UCBS. ie I say UNIT=LARGE and one of the SMALL ucbs gets allocated. To make matters worse I have NO IDEA if there actually tapes loaded in it despite RMM having the VOLSERs in the TAPE LIBRARY and OAM is running and SYS1.VOLCAT.GENERAL is defined. Any help would be appreciated This e-mail message and all attachments transmitted with it may contain legally privileged and/or confidential information intended solely for the use of the addressee(s). If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, forwarding or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete this message and all copies and backups thereof. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: EMC 6000 Virtual Tape Drive
On Mon, 6 May 2013 14:34:23 -0500, Darth Keller darth.kel...@assurant.com wrote: Question - why do you need 2 sizes of tape? Seems like unnecessary complication to me. We defined it with very large virtual tape as, unlike the B20's, there is no space (or very little space) required for the tape when it's not in use. It only uses space enough to hold the data when it's written. When the tape is scratched, the used space is released back and only a very small amount is used for the tape label.Of course, the difference is once a tape goes scratch and the space is recovered, there's no reading the scratch tape. I can answer that one - at least from an EMC DLm perspective. I (we) found out the hard way that one size did not fit all. My client shares the DLms with about 9 environments (sysplexes and monoplex LPARs). Most of those libraries have a 40G virtual tape size. That size was chosen based on the STK 9840s were were migrating from as we got rid of all physical tape (also had VSM virtual). Out of these 9 environments the larger ones have from 15-50 file systems of 3-5TB per DLm. Some of the smaller ones have about 5 file systems with anywhere from 100GB to 500GB. About a month after cut over (done via SMS ACS routine changes of esoterics) we had an out of space condition on one of the smaller environments trying to create a virtual tape - even though the file system was only 61% full. Well guess what - 61% full of a 100GB leaves 39GB free and of course the virtual tape system has no way of knowing you aren't going to really create a 40GB tape when you want a scratch tape mounted. We expanded the file systems for that library that evening and then after we figured out what the real reason was we changed the virtual tape size for all the small environments from 40GB to 5GB and for this very small environment we made it 2GB. 2GB matched the size of the large VSM (STK) virtual tapes we were using (although most were still 800MB VTVs at the time of the migration). EMC planned all the file system sizes etc. with us. The implementation team that worked with us never mentioned (or thought of) this caveat when we decided to use 40GB as the virtual tape size for all the different libraries sharing the DLms. Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:m...@mzelden.com Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
