It seems that some other conversations have merged into this one. There was a question out there about software delivery on tape, which IBM is getting away from. This question was specifically about OAM and using object tape support. Even more specifically if we should consider using the parmlib member CBROAMXX for object tape support. Brian in your comments it does not sound like you are using that, and based on what other people have stated we do not need to use it. In that parmlib member you setup such things as MAXTAPERETRIEVETASKS and MAXTAPESTORETASKS, among other things. In your OAM startup you would than point to that member. I am by no means an OAM expert and just wanted to investigate if we could possibly see some performance benefits from some changes, but in reality we would not.
John Benik | Optum -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Brian Westerman Sent: Tuesday, April 24, 2018 12:58 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: OAM and Object Tape Support with an MTL OAM is pretty fast for SMS managed tape. For example, we have a client that uses literally thousands of really small tapes per day (it's a long sordid story as to why) with 512 virtual tape transports and an average of 156 in constant use, averaging 3 to 5 mounts per second, there is less than .25 second (wall clock) delay between the request for a tape and the mount being satisfied. If you define the tapes in your IODF with the following attributes: LIBRARY-ID somelibraryid <--same id and port for each device that will share that library LIBPORT-ID someport MTL YES then set up in ISMF option 10.3 (library mgmt|tape) that same libraryID and an initial status of "online" for each LPAR that needs it (if not sysplexed, each one is set separately on ISMF for that LPAR). and also set "MANUAL" for library type and device type, then set up a valid storage class (along with and ACS routine to control it) and storage group (and a SG ACS routine entry) (remembering on the ISMF storage group panel to select the "alter group status" option at the bottom of the page to a "y" and then specify the library name and that you "ENABLE" it for that specific LPAR). (since it's manual you will need to do this for each LPAR, but it's just because you can't do it for all of them at once, (not if you want it to work)). Once you complete those steps, OAM should reset itself and tell you it knows about your manual library and the tapes you vary online (the ones you defined in your IODF) will be SMS managed. The rest is done within your tape library system (setting up the tapes to your tape management system (CA-1 or RMM, etc.) is fairly simple but there are some settings that you don't want to forget and if it's CA-1 you need to make sure his OAM exits are active. Then inside the Virtual tape system itself, you have to define the tapes and make sure they are synced with your tape management system on the mainframe. It may seem like a lot of work, but it's all pretty straightforward. If you have any problems just contact me offline or via this list and I'll help you with it. Offline is quicker because I don't always check the list, but the list would be good so that it get documented for other people later on. I think most of the virtual tape vendors have a section in their installation guide that covers these steps (BUS-TECH had a really good one but they sold themselves to EMC who discontinued the device), but they are sometimes very difficult to follow and the vendors themselves sometimes don't know. Mostly because they stick you with the marketing people who don't want to admit they don't know how to set the libraries up. :) I've set things up for clients with about every virtual tape vendor that exists (and those that don't any more) so I know where most of the pitfalls are. Brian Westerman On Mon, 23 Apr 2018 18:47:14 +0000, Benik, John E <john_e_be...@optum.com> wrote: >Thank you for the replies. Yes we have implemented SMS tape with our MTL and >since the libraries have to be defined to SMS it is our understanding that OAM >would have to be used for allocation purposes. I attended an OAM session at >Share this year and was trying to investigate if there is anything we should >be doing in OAM to enhance performance. It does not sound like there is >however. > > > >John Benik > > >-----Original Message----- >From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] >On Behalf Of Brian Westerman >Sent: Saturday, April 21, 2018 7:07 PM >To: IBM-MAIN@LISTSERV.UA.EDU >Subject: Re: OAM and Object Tape Support with an MTL > >If you are going to use System Managed Tape with your MTL, then you do have a >couple of configuration options under ISMF you will need to update. > >Also, did you define you library(ies) in your IODF EDT? > >OAM is not really obsolete, it has a real purpose in some situations. The >above is just one of them. > >Brian > >---------------------------------------------------------------------- >For IBM-MAIN subscribe / signoff / archive access instructions, send >email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > >This e-mail, including attachments, may include confidential and/or >proprietary information, and may be used only by the person or entity >to which it is addressed. If the reader of this e-mail is not the >intended recipient or his or her authorized agent, the reader is hereby >notified that any dissemination, distribution or copying of this e-mail >is prohibited. If you have received this e-mail in error, please notify >the sender by replying to this message and delete this e-mail immediately. > > >---------------------------------------------------------------------- >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 This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
