Re: OAM problem
When the OAM address space initializes we get the list of libraries that are "connected" to the system from the active SMS SCDS. Based on that list we try and obtain information about the library resulting in the error messages being displayed. Since the libraries no longer exist, you can either remove them from the SMS SCDS or indicate that they are not connected to the system and the error messages should go away. Also take a look at the tape storage groups to see which may still reference those libraries (in case those storage groups only use those libraries) and also the ACS routine logic if those storage groups are referenced. You may also need to update other information in the SCDS as it pertained to the usage of those libraries. When validating the SMS SCDS it will indicate if additional updates are needed when you remove the libraries. Also not 100% sure if you just update the library definition to indicate "not connected" on all the systems, if SMS will expect that at least one system has the libraries connected. Erika Dawson IBM DFSMS -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: RMM Roadmap
There is a new "What's New in RMM" Redbook that is currently in draft status and available externally to review: https://www.redbooks.ibm.com/redpieces/abstracts/sg248529.html In regards to conversion, I've reached out to one of our folks in the IBM Software Migration Project Office (SMPO) to respond to the initial question. There are several options available for converting whether it's done through them or directly by the client. Erika Dawson DFSMS Product Architecture IBM -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Physical Tape Ejection - RMM
I checked with the RMM service team and they had indicated that clients will typically generate the eject commands after the DSTORE HSKP has run. Here's some additional information from one of the RMM manuals if the volumes are being system-managed in an IBM tape library ... DFSMSrmm does not automatically eject volumes from a system-managed tape library as part of inventory management processing. To request that a volume is ejected from a system-managed tape library, use the DFSMSrmm Change Volume Details panel to change the location for a volume residing in a system-managed library or use the RMM CHANGEVOLUME subcommand to change the location or issue an eject request. Figure 1 shows how to use the CHANGEVOLUME subcommand to change a volume's location to its shelf location. The change to the SHELF causes the volume to be ejected from a system-managed tape library. Figure 1. Ejecting a volume from a system-managed library RMM CHANGEVOLUME volser LOCATION(SHELF) https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.4.0/com.ibm.zos.v2r4.idarm00/manejt.htm They had also suggested that you can open a Q PMR (Case) and they can verify what you may have setup to eject the tape volumes and answer any additional questions that you have. Erika Dawson (IBM) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Stop Tape Eject process
In my previous response, I was looking at this more from the perspective of what to do going forward to prevent this from happening again (assuming all of the volumes have already been ejected). Neither we or RMM have a cancel command that will take the eject requests off of our (OAM) queue or the libraries queue. It sounds like you needed the ability for OAM to have a cancel-type command which we do not currently have. If you would like that capability, please open a requirement for that. Erika Dawson OAM Product Owner (IBM) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Stop Tape Eject process
Unlike cartridge entry processing, OAM does not currently provide a way to disable cartridge eject processing. However, looking at the eject exit (CBRUXEJC) provided by RMM, if you want to prevent cartridge ejects, it's looks like there may be a way in that exit to have RMM invoke another exit and that exit could return back with RC=8 (which RMM would then pass back to OAM). A RC of 8 from the eject exit (CBRUXEJC) is an indication to OAM that the eject request should be failed. UXJFAIL EQU 8VOLUME NOT TO BE EJECTED If you would like OAM to provide a mechanism to disable cartridge ejects (similar to cartridge entry), please open a requirement. I'm also checking with RMM development/service to see if they have a way to ensure that RMM ejects are handled as NOEJECT (by default). Erika Dawson OAM Product Owner (IBM) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [EXTERNAL] Seeking help with DFSMSrmm
A good source of information on the different retention method options in RMM is the DFSMSrmm Primer: http://www.redbooks.ibm.com/abstracts/sg245983.html?Open ... this IBM Redbook provides a highlight of the different functions within RMM including the different retention methods that can be used ... retention through VRS policies RETENTIONMETHOD(VRSEL) and retention through expiration RETENTIONMETHOD(EXPDT). After that you can look at Chapter 3 Retention Methods in the following RMM manual ... https://www-01.ibm.com/servers/resourcelink/svc00100.nsf/pages/zOSV2R3sc236873/$file/idarm00_v2r3.pdf for an overview of each. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: TapeTools VEHSYNC job
Here is the email address for the IBM Tape Tools Team: tapet...@us.ibm.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMS for tape
With system-managed (SMStape), we SMS-manage the tape libraries and tape volumes and we do not manage the datasets on the tape volume (we leave this up to the tape management system and the application that owns the data). And though we use an ICF catalog for our meta data (tape volume and tape library-related information) we do not require that the tape datasets on an SMS-managed volume be cataloged. This is where we differ from SMS-managed disk where the datasets are cataloged. And with SMS-managed tape, the ACS routines and constructs are then used to manage the tape volumes and tape libraries. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
