Re: DFRMM Request For Enhancement 106021
Tim, Yes as part of initialisation there is a check for licensing. And that is the result. If it is wanted to act differently, a change would be needed. I did not have those details about the specific situation, else would have stated something a little differently first time. Mike -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFRMM Request For Enhancement 106021
Arthur, You cannot take the snippets out of context. Each snippet is qualified. Remember that rmm is always on your system (s/w delivered and installed as part of z/os), you have to take steps to tell rmm that it turned on. Adding DFRM susbsystem + EDGSSSI to IEFSSNxx turns it on fully. Adding just the DFRMM without EDGSSSI allows you to run rmm but it is not in control until you issue the START command. Mike -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFRMM Request For Enhancement 106021
I have no access to the RFE, but, if you follow the installation instructions correctly you should not be able to write to a tape without rmm knowing about it. IFAPRDxx is simply a way to identify you have a license, it is not how you ensure that rmm is in control for all tape activity. IEFSSNxx and the definition of the subsystem starts to tell the system you want to actually use rmm. Adding EDGSSSI to that subsystem entry, or starting the started task, tells rmm that it MUST be in control. Prior to that the system allows tapes to be used without rmm knowing. The documentation for rmm implementation or migration to rmm should have made that clear. Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: RMM question
Richard, Just chanced upon this question from you . and cant see any reply yet, so will try to answer it. You cannot mix RETAINBY volume and RETAINBY set for VRS retention. However that does not really answer the question What rmm will do for a "set" of volumes depends on what is actually written to that set and how the files are retained. If you have a single file written on a "set" - i.e. multi-volume data set. and that is VRS retained - rmm retains all the volumes in that set. If multiple files are written to a multi-volume set, how many are retained by VRS in that set depends on each individual data sets' VRS retention - if all files (data sets) are retained by VRS the set should be retained. Mike (rmm - retired) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Detect Tape Volume Switch
Its been a while since the question was asked, but here is a definitive answer. Over z/OS R11, 12 and 13 new function was added in OPEN to improve recovery from incorrect multi-volume processing. RMM added support to exploit the new capabilities. OPTCODE=B is a user way to control what happens. A system level control is available with TAPE_MULTI_VOLUME_ANOMALY keyword. More details are available for programming level control of EOV and abends in processing during EOV. Mike -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: How do I setup an DFRMM Vault with VRS
To apply the VRS to a dataset you need to run inventory management (VRSEL), and to get moves triggered i.m. DSTORE. Depending on when those are run there are different ways to generate the pick list. You probably dont need the first VRS with COUNT(1) - set it to go 'locdef' for 35 days, run VRSEL after creation and when you want to create the pick list you can do so with SEARCHVOLUME command using REQUIRED(locdef) operand with LOCATION(home), and even perhaps use CLIST operand to create the needed CHANGEVOLUME commands to set the location to locdef once moved. Then you can kinda skip DSTORE. Alternatively run DSTORE and use the movement report to pick volumes. Hope that helps, Mike -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: RMM OAM and 3494
Radoslaw, yup, as well as that EDGUTIL reference, look at EDGUTIL SYSIN statements which allows you to even process just a single volume Also, although it seems not completely documented the EDGSPLCS utility documents that EDGUTIL can write to a file with commands to that EDGSPLCS can process So, perhaps run VERIFY(SMSTAPE) regularly, or at least once now on the whole shooting match, include EDGSPLCS DD. Based on the results either run MEND(SMSTAPE) with SYSIN, or edit the EDGSPLCS file if needed and run EDGSPLCS. Mike -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: QUESTION ABOUT RMM
Willie, As specified in the rmm IC Guide Chapter 16. Performing inventory management - You can backup direct to tape when using EDGHSKP utility BACKUP(DSS) parm. Also, when you restore from tape, as long as you use EDGBKUP you will be able to use an rmm backup tape even if rmm is not active. Mike -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: How do we add private volumes in SMS Tape Library to RMM as status MASTER
Minoru, Ever since I designed it that way, that is what rmm has done. I had a choice - either make them MASTER or USER, or provide and option so you could pick - went with USER. The difference between a MASTER volume and one defined as USER is small, but it may be a key difference for you. That difference is that on a USER volume rmm allows overwriting of the existing files without insisting on the use of the exact same data set name. However, your security system should also be able to prevent this as to change a data set name you would need access to both existing and new data sets (assuming rmm knows what the existing data set name was after you have converted.) In all the years since first shipped in a release, no-one, to my knowledge ever asked for anything different. You could always use the output from a listcat to build the ADDVOLUME commands instead of STATUS(VOLCAT) Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: How do we add private volumes in SMS Tape Library to RMM as status MASTER
... and 1 more reason MASTER volumes should normally have all data sets seen and recorded while rmm (or another tms) is in control - so we would know exactly what is on a tape. When you add volumes using commands rmm has no knowledge of the data set names and so cannot enforce the difference between MASTER and USER. Mike -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NL Virtual Tape
Roger, The TS7700 doesn't care what you write on the tape, but the system tends to want them all to be standard label. However, I do recall that we made specific support in DFSMSrmm to support both non-specific NL and specific NL processing in all system managed tapes. However, you do need the correct authorization through rmm to be able to change an SL tape to NL (facility class profiles specific to rmm) rmm uses the volser provided by the TS7700 via OAM to track what you are doing and does whatever is necessary to allow the change to NL and, probably unfortunately, I suspect it will insist on relabelling back to SL on return to scratch . If you dont use rmm, you need to ask your vendor. If you use rmm, just try it by coding LABEL=NL in your JCL. and see what EDGI messages are issued Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Performance for DFDSS with ORACLE Tape Drives VSM5 ( was Change tape block size)
Victor, IEC205I gets the TOTALBLOCKS from system control blocks. It should match what rmm records (gets it from same place.. Actually it depends on access method and whether that method maintains the block count fields. EXCP does not and the application must maintain it. The block count is application block count sent to the device. what is on the tape depends on the tape device Mike -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: RMM and tape dataset block size
Victor, You should be able to reply on the blocksize recorded in rmm. Just like other tape systems it gets it from the system. Assuming you are on a supported level of z/OS, rmm should record all you need to know about logical and physical view of the data sent to tape by the application and actually on tape. You dont say what the actual tape drive is - somewhere you should 3490 I think. I suspect you are using virtual tape - is that correct? If so, how compression is handled depends on the tape 'hardware' you are using . an appliance like IBMs TS77xx, or software like VTAPE . Compression done in s/w will really hurt you. The hardware compression should barely be seen by the host system measurements. Modern tape drives (non-virtual) dont care about your/application choice of blocksize and will write larger blocks to the tape media - Russell already told you that .. If you need help - we all want to offer it, but if you dont give enough details you will never get a correct answer - just guesses. Mike -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Change tape block size
Victor, You still haven't provided details of what the 'tape drive' really is. Virtual or a real drive - and then which virtual system/physical drive type and media type - It can make a big difference Mike -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: RMM question about adding VRS
...small addendum to my reply re: step #2 Without checking the full flow of command processing I cant be absolutely certain any more of what rmm does. However, as I said, it should allow you to change the location information to reflect the actual situation via commands. You might have to add NOEJECT operand because rmm believes the volume is library resident - depends how you 'manually' ejected it. If RMM shows volume is 'in transit' you dont need NOEJECT. I know that when the TCDB is not connected or library is off-line you can even add FORCE operand that enables some subset of failing commands to work in any case. Hope that helps, Mike -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: RMM question about adding VRS
Wayne, You should not need to retrieve the volumes, re-insert them, and do it all again under VRS control. RMM should be smart enough to make sense of what it finds in the library and what the VRS policy decides. I suggest you 1. Add the rule that will cause rmm to identify what should be in the offsite location. 2. Get a list of the off-site volumes, and for each one issue rmm tso command: RMM CV volser LOCATION(offsite) CMOVE I would expect that rmm command processing will find the volume not in the library and allow the location change without an error msg. 3. run EDGHSKP VRSEL processing. As a result, as documented in the rmm IC Guide the 'required location' will be updated to show what VRS decides. 4. You can check the VRSEL decision against actual location using SEARCHVOLUME for example: RMM SV VOLUME(*) LOCATION(LIBATL1) REQUIRED(offsite) RMM SV VOLUME(*) LOCATION(offsite) REQUIRED(LIBATL1) 5. Run EDGHSKP DSTORE which initiates the movement by setting LOCATION from REQUIRED location. 6. Eject the volumes from the library and move them/return volumes from offsite if needed. 7. Confirm the moves to offsite to rmm / enter returning volumes into the library Normally you can run EDGHSKP options all in the same run, not step by step. Mike WoodRMM expert -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: AWS Header 2 Block Count
Willie, Regardless of whether you are building and AWS tape or not, when it is IBM Standard Label format, the details of the labels you generate must be as per the IBM specification documented herre (for R12 - later versions of the book exist) http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/dgt2m330/2.2.3?SHELF=EZ2ZBK0KDT=20100701110050 For EOF2 there is no block count - that is in EOF1 Did you also see Sam Golobs write up about AWS tapes? http://www.cbttape.org/awstape.htm Mike Wood rmm tape management consultant -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: assign userid to SMS system address space
Wilco, you dont show the commands you issued, nor mention refreshing the
STARTED class details .
Something like this 'should' do the job
RDEFINE STARTED SMS.* -
STDATA(USER(=MEMBER ) -
GROUP(SYS1) -
PRIVILEGED(NO) -
TRACE(YES) -
TRUSTED(NO) )
ADDUSER SMS NAME('SMS SUBSYS STC') -
DFLTGRP(SYS1) OWNER(SYS1) -
NOPASSWORD
SETROPTS RACLIST(STARTED) REFRESH
Also see this article thrown up by a google search
http://www.ibmsystemsmag.com/mainframe/administrator/security/RACF,-Started-Tasks-and-System-Privileges/
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFHSM RECYCLE PROBLEM
Could it be that the MCV record is serialized by hsm - because of the way hsm was abruptly stopped, and you just need to reset the hostid in the record? Its been a long time for me, but have you looked at LIST command used with RESET and MIGRATIONVOLUME(volser) ??? Mike -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFSMSrmm Command Log for audit
Massaki-san, When you have the SMF recording turned on as recommended by Tom, take a look at EDGAUD reporting utility; it can be selective about which SMF records it reports on. For example, you can specify a userid or list of user IDs and report on their updates. Mike -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Maximum Capacity Feature
Well, no prizes to Oracle for document clarity. A better description is here http://docs.oracle.com/cd/E19772-01/TM0002revEF/TM0002revEF.pdf in an older document. I would assume the technique required is the same for T1C T1D drives as well. The application (for example hsm or similar) needs to be modified to exploit it. Mike -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Maximum Capacity Feature
Radoslaw, Try here http://www.oracle.com/us/products/servers-storage/storage/clipper-t1d-2009307.pdf It says that the feature ensures that cartridges written by an older drive, such as T1C can be rewritten to maximum capacity on a T1D for example. I dont think they word it very well... older cart/newer cart. Sounds a bit like IBMs' recording technology which can increase the capacity of an existing cartridge by rewriting in a newer format with a newer drive Mike -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFSMSHSM TAPESECURITY(RACF)
Arye, In general, if you value the data that hsm has placed on tape, you should ensure that the data is protected. This means there has to be some RACF profile (or equivalent) protecting the volume or the data, and the system (or some other involved party) has to make the RACROUTE call to check the person opening the data set on the tape volume is authorized to do so. I would always recommend you protect hsm tapes. Depending on your security product this might be TAPEVOL profles or DATASET profiles or even a combination. The choices for protecting hsm tapes are given in the hsm books, where it even describes when hsm will automatically protect its own tapes using TAPEVOL profiles. Some tape management products, such as CA-1, have options to control if security checks are issued - If you are not using RACF TAPEDSN option, or RACF TAPEVOL class you need to look at this. z/OS also has a DEVSUPxx option TAPEAUTHDSN which is described in the z/OS Init Tuning guide. Remember that hsm runs with OPERATIONS and PRIVLEGED - so gains access to anyone elses data if it tries.. So you tape management system has to ensure complete 44 character dsname checking. I would also check if your tape management system issues RACROUTE checks for 'EDMs' and also does full 44 character dsname checking. It is not straightforward, but well worth doing and getting correct. Mike Wood - rmm expert and tape management security consultant -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: LTO 5 in 3584 tape library and z/OS
I found a list of supported device types here http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/iea2g610/D.0?ACTION=MATCHESREQUEST=magnetic+tape+devicesTYPE=EXACTNSHELF=all13be9DT=20050713135418CASE=searchTopic=TOPICsearchText=TEXTsearchIndex=INDEXrank=ScrollTOP=FIRSTHIT#FIRSTHIT Strictly speaking, that is all that is supported. However, any device that can successfully emulate one of those device types is supported. Hence, all the latest IBM tape drives emulate 3590-1 and the system can even tell you what they are - TS1120 etc. Virtual tape has to emulate also one of these devices - most are emulating 3490, and to be correctly reported as a virtual library some OAM support is needed to recognise them. Any non-IBM tape can only be reported by z/OS as an IBM 'equivalent' - whatever the manufacturer chose to report to z/OS. Tape management systems attempt to navigate their way through all this to tell you what is really going on out there. Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ca - reclaim for hsm, rmm, cdses (and ucats??)
Michael, for any KSDS, whether catalog or not, CA reclaim is never used for those with IMBED. So, you simply forget those with IMBED unless you can remove that in order to get CA reclaim benefit. Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: RMM CDS utilization vs 3.4 utilization
Wayne, I am not sure you understood what I said about REPRO use of dss to copy/move/backup the cds does nothing to consolidate the space within the CDS (KSDS) Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Partition a VTS 7720
Jerry, The partitioning available to the host systems is only by category numbers. You dont have to partition, but reasons to create 2 partitions in your case include: - tape management system - if not a single VMF shared between test/prod - TCDB - this must be shared to avoid conflicts of volume status - ICF catalogs containing tape data sets - if not online to both partitions you can get inconsistencies after tape management returns a volume to scratch, or a data set is created on 1 lpar but managed from another. That is why most people partition their system managed tape libraries including those which are virtual and have the dasd cache online to all system. Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Partition a VTS 7720
Radoslaw, #4) rmm use of REJECT ANYUSE had some limitations. You now have the option of using PRTITION statements in rmm parmlib for more effective partitioning. Use in conjunction with OPENRULE. Mike -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: RMM v/s TS7740 VTS
Best refer to this section http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/dgt2r3a0/1.3.11?SHELF=all13be9DT=20110602105512 in the rmm MURM. It was added 2-3 years ago when rmm team shipped some extra device support exploiting some tape drive/ h/w capabilities. I dont currently have a way to test for TS7740, but would expect rmm to be getting number of post compression bytes to nearest 1K or 4K value. Mike Woodrmm expert -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DCOLLECT QUESTION
If your sys progs used the default names, you might find the exec EDGRMLIB (SYS1.SEDGEXE1) will dyanmically allocate the data sets needed and take you to the rmm dialog where option R will also be the report generator. Its so easy to use, you shouldn't even need to RTM. Mike -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: RMM CDS utilization vs 3.4 utilization
Wayne, It is best to follow the recommendations in the DFSMSrmm Implementation Customization Guide. They were written based on lots of experience with many different installation. The CDS utilization is simply HURBA/HARBA * 100 It makes no account for empty space in CIs or CAs, nor for the potential to grow the CDS into multiple extents. To determine really what space is actually used, you could define a VSAM KSDS like the CDS and repro the records from the CDS to the new KSDS and see what the HURBA/HARBA is then. VSAM is now very good at reusing empty space within already used CAs and CIs (CAs with R12+). Mike Wood rmm expert -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: How to determine tape dataset blksize
Victor, RMM always records a blksize. You can see the value in the LISTDATASET output/display. The value might be zero as mentioned by Radoslaw. Since the system provided support for large blocks (LBI) and the application correctly exploits it, rmm records all values. For older data sets, the rmm extract process will convert zero values to 64K and recalculate data set size and volume usage. So a report from the extract would provide the corrected values. Mike Wood rmm expert -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DCOLLECT QUESTION
ESmie, Look at the report generator available under ISMF dialog. There are some sample reports based on DCOLLECT, and the report generator allows you to use 'generic' field comparisons (sub strings).. Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: RMM common practices
Michael, Hopefully I can help you with this. 1. This difference in catalog status is only a problem if you are retaining them by catalog in rmm. In all other cases, when the data expires and volume is returned to scratch the difference should be resolved. (depends on UNCATALOG parmlib option) To make rmm match the catalog you need to run CATSYNCH - this can be either done manually with EDGHSKP, or, use EDGUTIL to reset the CATSYNCH state to NO so rmm EDGHSKP automatically includes CATSYNCH next time it is run (The latter requires parmlib option CATSYSID(*) to be in use. 2. EDGHSKP requires rmm to be active. The only reasons to quiesce or stop rmm are: i) EDGBKUP with BACKUP(REORG), and ii) EDGBKUP RESTORE to the active CDS. 3. My thoughts about CDS percentage used are documented here http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/dgt2c8a0/17.7?SHELF=all13be9DT=20110609111302 The answer to your question is 'it depends'! If you follow the recommendations I made in the rmm IC Guide, including sufficient secondary space etc.. neither reorg nor percentage full are an issue until you run out of space in VSAM limits or available DASD space. Consider this - how much space in MB is 10% of your CDS? . How many data sets/volumes might fit in that space? ... are you growing in number of volumes/data sets Reaching an limits? Mike Woodrmm expert -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Method to measure usage of a physical tape
Russell, 95% full 4TB tape cartridge would have around 200GB space available Thats a lot of space I know hsm had a lot of thoughts on that kind of subject. Mike -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Method to measure usage of a physical tape
Victor, Radoslaw already mentioned some of the data that rmm records, and I know CA-1 does similar. However, rmm actually now has much more and very interesting data about what is written by the app and what has happened to it in the hardware. For the details you need to be using tapes that report to the host system the correct information.. So that includes IBM drives since 3590, and other manufacturer drives that correctly emulate 3590. See this section in the rmm MURM http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/dgt2r3a0/1.3.11?SHELF=all13be9DT=20110602105512 This was new capability introduced via an APAR to rmm at the time of TS1140 support - so should be available on all supported releases. Mike Wood rmm expert -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Breaking unit AFF in SMS for Tape
Did you see this? http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/iea2b560/4.4.3.3?ACTION=MATCHESREQUEST=AFFTYPE=EXACTWSHELF=EZ2ZBK0KDT=20100701093058CASE=searchTopic=TOPICsearchText=TEXTsearchIndex=INDEXrank=ScrollTOP=FIRSTHIT#FIRSTHIT -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Question on TS7720 and J70/J1A connections
Lizettte, The J70 is a controller for attaching the J1A drives to the host system (ie z/OS). The J1A when attached to TS7700 virtual tape library is attached to the virtual library not to the host. To use J70+J1A host attached you could copy from virtual tape to physical tape using the host system and whatever tools/products you might have. To look at upgrading a TS7720 to TS7740 you would best ask IBM. You could start here http://pic.dhe.ibm.com/infocenter/ts7700/cust/index.jsp?topic=%2Fcom.ibm.storage.ts7740.doc%2Fts7740_grid_mes_clusters.html Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: LifeCycle or RoadMap for TS7700 Tape Hardware
Lizette, As I have no future IBM product knowledge in this area, - just can base thoughts on what has happened in recent years.. I cant get in trouble - hopefully! TS7700 is a family of products made up of different product parts - both hardware and software. Each piece can be upgraded - for example the server running the virtualization engine, the disk subsystem used for tape cache, the physical tape library, the tape drives, the micro-code. IBM has been successfully offering upgrade path enabling larger, faster,grid improvements, function improvements for a few years now I dont see a need for a replacement product given that all parts can be changed and it still be TS77xx. Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: rmm variable
Kurt, You should refer to the z/OS Migration books for the releases you skip and your target release. See http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/e0z2m171/9.2.26?SHELF=EZ2ZBK0IDT=20100128170349 It is the documented migration item related to the rexx stem variables. There is even a health checker check to help check through home written execs. Since R11 the only stem variable with stem .0 is the one directly related to the the SEARCH subcommand issued. So edg@vol.0 for SV, edg@dsn.o for SD etc. So, depending on the command issued, probably SD in your case, use edg@dsn.0 to find how many data sets(files) are on the volume. Or, you could use LV and then edg@dsc for number of data sets on volume - adding 1 for the next physical file on the volume. Mike Wood (rmm architect in a previous life) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: How to list all tape volumes the shows UNKNOWN on the D SMS,VOL cmd ??
Hi, Do you want to change status from private to scratch, and as part of that to set SG=*SCRTCH* ?? Or something else? If you have rmm as tape manager you can make the change driven from rmm commands, That will update TCDB and LM. Any change from private to scratch for a system managed volume also changes the storage group name to '*SCRTCH*' This is not a mask/generic value. It really is this value. In ISMF you can use a primary command to apply to all those tape volumes in the search results list. Once started, just walk away and dont worry about the batch. Hope that helps, Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: How to list all tape volumes the shows UNKNOWN on the D SMS,VOL cmd ??
If you use rmm, you can use rmm SEARCHVOLUME with CLIST to create the ALTER IDCAMS commands needed Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: How to list all tape volumes the shows UNKNOWN on the D SMS,VOL cmd ??
... as prompted by another post . yes IDCAMS ALTER only changes the TCDB - There is no outboard communication. To change a category outboard you have to go via OAM Iether from ISMF or rmm (or another tms perhaps - some have sync options) All you can do is change the STATUS o PRIVATE/SCRATCH and OAM uses the DEVSUPxx specified values to set the outboard category. So DEVSUPxx must be correct and you have to be on the correct partition. ISMF allows you to change the STATUS to the same value it already is.. which can result in category change. rmm will not direct via OAM unless the status really changes - so you may need to go scratch- master-scratch Usually 000F category is PRIVATE on all partitions - only SCRATCH volumes have different categories based on the partition. Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: How to list all tape volumes the shows UNKNOWN on the D SMS,VOL cmd ??
Hi, I suspect your DEVSUPxx MEDIAx values dont contain the values being used for LM categories. You can see that OAM is getting back 000F as the LM catgeory. It then uses the DEVSUPxx (or default) values to translate that to something meaningful. i.e The volume belongs to another partition. Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: OAM - CBR0054I
After reading all the related appends about this I would think many would still be confused about OAM. The specific message is related to OAM 'object tape support'. This is nothing to do with OAM system managed tape library support. Try this EA session which explains more http://publib.boulder.ibm.com/infocenter/ieduasst/stgv1r0/index.jsp?topic=/com.ibm.iea.zos/zos/1.0/DFSMS/V1R0-General-OAMSupport/player.html OAM provides 2 main functions - tape library support, and Object support. You can exploit one without the other. If using Objects, you can optionally use its Object tape support to store objects on tape. Only worry about this message if you are using the Object support and want to store some of the objects on tape. Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: RMM: Best, safest way to mass delete tape volumes
Jeff, leaving all the concerns alone at the moment . Deleting volumes should be straightforward. You do need to consider the scratch volumes and non-scratch volumes separately. Scratch volumes should already have been through release processing and any cataloged data sets uncataloged. RACF profiles deleted (if any). To delete scratch volumes - use the RMM DV volser REMOVE command. Non-scratch volumes you still have this consideration. You can cause the volumes to go through release processing and allow rmm to uncatalog and cleanup RACF. Use the RMM CV volser RELEASE command. Using the RMM DV volser FORCE may not do these tasks for you. You also have some possible cleanup of the VRSes that are causing these non-scratch volumes still to be retained even though they no longer exist. You can use the SEARCHVOLUME subcommand with CLIST to help build the commands needed. It is very powerful, can be run in TSO or batch, or even with the help of the dialog. Also in the dialog, within search results list, you can use the SELECT primary command to set the line commands for selected entries in the list, then press ENTER to process them. When you are making changes to volumes and other things defined to rmm, it normally creates journal records, and processing also should be creating PDA trace records, Either journal or trace data sets can become full when making mass changes - as others have mentioned. In a well-run environment there should already be automation to take care of these things. Deleting volumes should not usually cause space problems in the CDS. Rather it should free up space that can be reused. However, depending on how old the volumes are, and when the records were last updated, causing a change to a record may cause the record to be stored back larger than before . Again, usually, this extra space can be accommodated by VSAM without needing to split CIs/CAs. Another way to delete volumes, which was added more recently to rmm, is to use the REPLACE release action. Probably best for non-scratch volumes, use RMM CV volser RELEASE(REPLACE) command then release the volume. Once pending release you can use RMM DV volser REPLACE to delete them without going through return to scratch process. Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: 3494 Utilization
saurabh khandelwal, The sources of information include the 3494 Library Manager, DFHSM and your tape management system. Each will have its own view about what data is in the library. 3494 LM will know what data is valid, but some of this may be on tapes already expired. You can ask 3494 for details of what it knows - tools include the user interface and the BVIR utility. See IBM White paper for 3494 BVIR. DFHSM will know what volumes are in the 3494 and can tell you how much valid data is on each - it tracks a percentage valid data to aid with recycling. Your tape management system should support reporting on non-scratch (and scratch too if you wish) volumes and be able to tell you data set size and maybe even compression ratios depending on your release and product. For example, with rmm you can use the report generator to create a custom report from one of the samples quite easily that shows how much data is on volumes in the library. See Rexx based report REPORT05 which includes data set size, and a similar report from report generator EDGGR05. You could make an assumption about compression ratios if necessary. I recently did such a report for a client and the ICETOOL very readily gave a total size of all application data at the bottom of the report. Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Strange Behaviour with DFRMM and catalog
Jerome, Call IBM and report the problem. Seems similar to apar OA35183 There may already be a fix. With UNCATALOG(Y) or UNCATALOG(S) you should expect data sets to be uncataloged if still in the catalog at time of return to scratch. Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Sharing TS7700 across sms plex
Victor, Follow the first two results from google search for 'specific volcat' http://www.google.co.uk/search?q=specific+volcat If you need more help than this please contact me directly. Mike Wood (blatant plug - Independent tape management consultant) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: blksize for ML2 migrated dataset via HSM
The DCBE where the larger block size is stored when the LBI is used (ie Application supports it). Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Sharing TS7700 across sms plex
On Wednesday, 16 January 2013 07:39:01 UTC, Victor Zhang wrote: Hello, I have a request to sharing TS7700 across lpars belonging to different sms plex, one lpar created data and the other lpar,away from 2000km+ need restore the data, how to accomplish this? How to maintain TCDB? Regards Victor Victor, Setting up the TS7700 grid and having logical volumes replicated between the clusters is well documented - as referenced in another response. The harder part is setting up TCDB and your tape management system correctly to enable cross-LPAR/sms access to data created in another LPAR. With no shared DASD between the LPARs your tape system data base (rmm cds/CA-1 TMC) is specific to the LPAR and has no knowledge what the other LPAR wrote to tape - however, you can configure the TS770 to access the logical volumes between the LPARs. Same problem with the TCDB. I can speak for the rmm solution: you could consider rmm client/server support - enabling a single rmm CDS and either LPAR to know details of what is on each volume. Else you can only use 'ignore' support (foreign tape processing). This requires you to know what volumes and what the data set names are on tape. Alos requires authorisation for use. rmm supports either EXPDT=98000 or in more recent releases you can use OPENRULE definitions to allow this processing for ranges of volumes automatically - but still requiring authorization. For OAM, the TCDB cannot be shared, and what I normally recommend is that the system from which you want to read the data you have a specific volcat for the range in question, and pre-define all the volumes you plan to allow to be read as PRIVATE volumes. Together this 2 parts of the solution should enable an easily managed setup. Other options could be available depending on the details. Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FREEVOL=EOV on R1.13
I dont have any more information than others about this R13 new function However... Allocation and ENQ processing are not changed. So you should expect all specified volumes to be ENQd and serialised until used. At EOV, the used volume will be DEQd. Another job that specifies the same volume list would have to wait until CLOSE time and the last volume is DEQd to get going. So whats the benefit? Also look at a related new function 'LABAN exit enhancement for multi-volume'. This is exploited by rmm in R13. You specify a single volume of a set, or an incomplete list of volsers at OPEN time the wrong sequence is detected and your tape management system can provide the correct list of volsers. I dont know, and no longer have a way to test this, but could this be a way to avoid the serialisation of all volumes at the start? For a complete answer best go to IBM and hope they ask the developer. Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Automation for IGD17272I
Antonio, are you really on z/OS V1.2 If you were on a supported release you would have some of the newer SG related capabilities in DFSMS to help - such as overflow and extend storage groups. You would not need to automate - simply define the available volumes that you would add, and tell DFSMS how you want them used/added. Start here ... www.redbooks.ibm.com/redbooks/pdfs/sg246979.pdf Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IBM 3584/3953
Sharon, Depending on how you are able to share things between the LPARS you will have to consider whether to partition the library. For example, you have a TCDB - can it be shared by all LPARs that share the library. If not you will need partitioning. There are (red)books to help with this. Be sure to also consider your tape management system. Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Adding SCRATCH tapes to DFRMM
On Thursday, 13 December 2012 00:52:11 UTC, Mike Wojtukiewicz wrote: I am going batsh*t crazy trying to add tapes to the RMM scratch tape list. I use the panel to add a scratch tape and it shows in INIT status. I can't change it to scratch status cause the panels work against me. Is there a STRAIGHFORWARD way to just add VOLSERS that are immediately ready to be SCRATCH status. I'm no CA fanboy but boy was it easy to add scratches to TMS. Thanks in advance Mike, Tom already covered the why and what to do next time For those defined already, you just have to confirm the tapes have been INIT'd - in The panels go to volume search and list the added volumes. Issue the CI line command for each one. You should find the SELECT * CI primary command useful here. Alternatively, use the Librarian panels, 9/CONFIRM. Select INIT in the resulted list to see all the volumes. Then take the same action as above with CI. rmm allows you to dynamically add from 1 to many volumes by tso command, by the panels, etc.. What could be simpler. Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: TS7740 and VTS B20
On Tuesday, 20 November 2012 16:04:18 UTC, Steve Finch wrote: Has anyone ever done a IMPORT on TS7740 of a EXPORT tape from a VTS B20 ? Steve Steve, The export formats are not compatible between those libraries. IBM provides a utility to allow you to copy a VTS exported logical volume from the container volume - you could use that to copy an entire logical volume to a new logical volume in the TS7740. A slow process if you have many exported logicals to recover. Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Scratch pool names in rmm
Monika, I need to know more about your current implementation with CA-1 to provide a complete answer. You say you have multiple LPARs, are these linked in a JES3 complex with JES3 Global system and 1 or more Local systems? Does CA-1 today modify the IAT messages to overlay the 6 character SCRTCH/PRIVAT text with a 7 character pool name? Which virtual tape solution are you using, and can it be tailored to look for the pool name at the end of the fetch/mount message? The best way to handle scratch pool selection with JES3 is to use IATUX71 - a JES3 installation exit created by JES3 development for use with tape management systems but designed with me for rmm specifically. When this is used (via the USERMOD provided with rmm) JES3 knows the message text is updated and makes the text updates itself in IAT msgs and in the tape drive display via MSGDISP. The updates are limited to be max of 6 characters when overlaying the volser, but can be longer when added to the end of the msg. The rmm IC Guide has information about setting up rmm with JES3, and does provide some various options to get what you want. as well as the JES3 chapter, look at MNTMSG and VLPOOL in the parmlib chapter. If each JES3 LPAR is independent, ie not in a JES3 complex, you can easily get what you want. In a JES3 complex the same pool definitions must be used on all systems because JES3 fetch processing occurs on the Global and tape mounts must happen on each individual system. Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: New DFSMSrmm retention method
On Tuesday, 23 October 2012 08:17:09 UTC+1, Walter Marguccio wrote:
Mike,
I understand that, for cataloged datasets, the WHILECATALOG keyword,
specified
in a single VRS or in a VRS chain, always wins. Am I correct ?
Correct. while a data set is cataloged and matching to the example VRS it will
be VRS retained.
Ever since we migrated to rmm, we have:
a) RETPD(5) in EDGPRMxx and
b) one VRS defined as: dsname('**') WHILECATALOG LOCATION(HOME)
with this setup, a cataloged dataset with a given RETPD/EXPDT will never be
deleted.
If I want RETPD/EXPDT to be honored for a dataset, and want to stick to VRSEL
retention method, I suppose I need to change:
a) RETPD in EDGPRMxx from 5 to 93000 (keep the data almost forever)
b) update my only VRS as: dsname('**') UNTILEXPIRED LOCATION(HOME)
Making the above change will ensure that VRS retention is assured until the
EXPDT is reached
Or, I change the global retention method from VRSEL to EXPDT, and still need
to change
a) RETPD in EDGPRMxx from 5 to 93000
Are my assumptions correct ?
Looks like it. Once the parmlib OPTION RETENTIONMETHOD(RETPD) is in use, any
volumes that use this retention method will not be considered by VRSEL
processing and only the volume EXPDT used to determine when EXPROC will expire
the volume.
I am sceptical about using RETPD(93000) as a default retention for all new tape
data sets. But, if that works for you . . . . .
I hope that helps you,
Mike Wood
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: New DFSMSrmm retention method
On Monday, 22 October 2012 10:08:36 UTC+1, Walter Marguccio wrote: Hello all, ever since we migrated from CA-1 to rmm in 2008, I have been told that the latter would never delete a cataloged dataset, even if the dataset had a RETPD or EXPDT specified at allocation time. In other words, the VRSEL retention method would never allow the above, no matter which combination of VRS(es) was used. Has the new EXPDT retention method (introduced at z/OS 1.13 level) been implemented in order to satisfy such requirement ?� Walter Marguccio Walter, What you remember/were told, about cataloged tape data sets is not in fact true. rmm can delete a cataloged tape data set if the matching VRS includes some other retention type than WHILECATALOG. When VRSes are used, and in recent releases, when VRSEL retention method is used, all the retention types in the VRS must be true for a data set to be retained. So, if still cataloged, and the VRS specifies WHILECATALOG, a data set will be retained regardless of the EXPDT/RETPD. The EXPDT retention method was introduced to provide an option for retention that did not require post processing other than simply checking the volume EXPDT vs the current date. Thus reducing the overhead of determining whether to scratch a tape. Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: New DFSMSrmm retention method
Rex, The only way to link a VRS to the volume EXPDT is to use the UNTILEXPIRED retention type in the VRS. So, unless, UNTILEXPIRED is used, the WHILECATALOG VRS retains the data set until it is uncataloged, and only then, when the data set is dropped from VRS retention is the volume EXPDT considered. From R13, with EXPDT retention method you can ensure that only the volume EXPDT is considered. Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Is there a way to RMM deletevolume a volser from a VTL that is no longer available?
reason code 401 from OAM tape processing means the library is not accessible - well, we knew that, but there are certain paths in the rmm code that should allow the rmm processing when this happens - allowing CDS cleanup. . . . Well at least the DV worked - so that was good news. Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Is there a way to RMM deletevolume a volser from a VTL that is no longer available?
Mike, I dont have a means to test each of these, but, working from memory about the design and implementation in rmm - If the TCDB entries still existed, you could simply add the NOEJECT operand to the DV commands - so that no attempt is made to go to the library. However, since you have no TCDB (and this is the reason the volumes dont go to scratch as well), you will have to follow the guidelines from the GR about situations when a library/tcdb is not available. See the CV FORCE operand description items 2 3. - Issue RMM CV volser LOCATION(SHELF) FORCE or - RMM CV volser EJECT FORCE or - Issue RMM CV volser LOCATION(SHELF) FORCE TYPE(PHYSICAL) See the requirements in the book about authorization. (ie CONTROL and FORCE authority) Once the volume is not known to be system managed by rmm, you can use the DV volser FORCE commands to get rid of them from CDS. Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: How to get a tape's DSCB
Robin, If you have a tape manager such as rmm or CA-1, from ISPF you can normally issue the TI line command; both rmm and CA-1 support that. You can easily get data set details without mounting the tape. In addition, ISPF supports line commands for tape - but they have to be enabled via the configuration table and someone has to provide the code to support them. See http://publib.boulder.ibm.com/infocenter/zos/v1r11/index.jsp?topic=/com.ibm.zos.r11.idarc00/enabsup.htm. Once enabled, for rmm case, just use the line commands as if its a dasd data set and equivalent/relevant info is displayed. e.g. 'S' displays tape data set details Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Syncronize between CA-1 and IBM ATL and VTS
On Thursday, 20 September 2012 12:30:01 UTC+1, גדי בן אבי wrote: Hi, I am supporting a customer that has CA-1 and an IBM ATL and VTS. Their main site has no syncronization problems, but at the backup site, CA-1 and the ATL are out of sync. CA-1 reports many virtual scratch tapes, while the VTS reports none. There is no online communication between the two sites. Once every few months, the backup site is restored from tapes. This restore includes the CA-1 TMC and AUDIT datasets. How do I sync the ATL and VTS with CA-1? I tried using the CTSSYNC utility, but it doesn't seem to work. Any help would be apprreciated. Thanks Gadi Gadi, Without knowing more details about your 2 sites configuration related to ATL and VTS, what is shared, what is not, any movement of physical tapes between sites, export/import, how scratch tapes are used at each site, no-one could offer you best advice about what is wrong nor how to correct it. If you could describe more details about tape usage, TMC backup/restore, running CA-1 on backup site, who updates TCDB on backup site . you might get better help and advice. Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFSMSRmm cds reorg getting full and is it unwise to code secondary space for a cds?
Guide. Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Possible to change availablity of tape volume in RMM?
Mike, Issue this command RMM CV volser RETPD(1) before running any other rmm batch processing. This will return it from pending release. This is covered in the rmm GR CHANGEVOLME command 'Changing pending actions To reclaim volumes: . . . .' You could do the same under the dialog - VOLUME CHANGE and enter a period in the Retention Period field. Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: How to retain volumes by days when VOLUME VRS is used in DFSMSrmm
Massaki-san said : But I could not find out the description or the explanation regarding to type of retention for the COUNT in VOLUME VRS. I have checked R6, R10, R13 RMM GR manuals. I you point out where the description in the manual, I really appreciate it. A: It is kind-of in the GR under ADDVRS COUNT explanation. Use COUNT(number_of_days) to request that DFSMSrmm retain all cycles or copies of a data set, bor a volume for the number of days you require. /b Use COUNT(number_of_volumes) to request that DFSMSrmm retain bthe number of volumes you want. /b Down with STORENUMBER operand it is much clearer Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: How to retain volumes by days when VOLUME VRS is used in DFSMSrmm
Massaki-san, you said Thank you very much for informing me that COUNT(0) is available only above z/OS V1.9. A customer wants to use both volume and data set name VRS. I don't know its detailed reason. The customer just ask us how to retain volumes by days. They also use data set VRSs. I guess that if a volume doesn't match data set VRSs, they want to retain the volume by volume VRS. A: There are multiple ways to address the requirement, but knowing which would be best requires detailed knowledge about the customers situation and system release levels. You already have indicated that its an older, perhaps out of normal support release Using volume VRSes you can either use generic volume and rmm retains cycles - i.e. a number of volumes, or you can sue specific volume VRSes and rmm will retain based on DAYS. This is explained in the rmm GR for ADDVRS subcommand. To retain by DAYS you also have options such as: - use the default retention period such as OPTION RETPD(5) - use a data set VRS with DAYS COUNT(5) - This requires that you know the data set names of the files you plan to place on those volumes. Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: RMM conversion to Common Time Support (UTC GMT)
Jeff, We are going to have to change one our SYSPLEX members from MST to CEST. To do this we will need to convert DFSMSRMM to Common Time Support. not sure what you mean exactly by change.. Could this simply be changing the time zone offset, or changing the processor/hardware clock? Regardless, there is no NEED to change rmm - rmm continues to record times using local time - so, assuming you are going forward by 9 hours - no times will repeat . However, be sure to see the warning in the book about the pre-reqs for running rmm with UTC(YES) - especially about the TOD clock being GMT and then using TIMEZONE offset to set local time Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: How to report catalogued dsns on tape ? ICF Catalogs
A.Cecelio, For the rmm system, you do not need to write any code/rexx, simply run EDGHSKP utility with PARM='CATSYNCH,VERIFY'. rmm will assume you have catalogs fully shared and will cross-check all your connected ICF catalogs with the rmm CDS data set records. rmm reports mismatches, and, because you run with VERIFY, will also report all data sets in the catalog on tape that are not defined to rmm. On your non-rmm system - it would be quicker to convert the existing tape systems' data base to rmm CDS, run rmm in parallel, using CATSYNCH,VERIFY to get the comparison, than to write your own tool Mike Wood :: rmm expert -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFHSM and CBRUXVNL - VOLUME NOT IN LIBRARY INSTALLATION EXIT
Tom, I cant find that post from Karthick anywhere .. Ok, here's what I can remember ;-) about VNL exit hsm avoids the VNL exit being called because it does its own checking before attempting dynamic allocation of a system managed volume. It knows from its own volume record that the volume is system managed, and checks residency before allocation attempted. So, for hsm's processing there is nothing a product like rmm can do in VNL exit to help . So any SYSZTIOT ENQ is purely something to address to hsm. I did one-time suggest they changed the processing so there was a common path via VNL to resolve the error situation cheers, Mike -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Replacing CA products
Mitch, As an example, IBM does not have an internal solution but instead uses other vendors. I dont know where you get that information. My recent past and present experience is that IBM has a strong presence in this area - The SMPO (Systems Migration Project Office) provides strong and experienced services in this area. I am not saying they always do it themselves - I also know they can contract out .. Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: 6 Member Parallel Sysplex - timezone
Jeff, I believe hsm runs using local times, so you could have data created on one LPAR migrated/deleted earlier/later on another LPAR in different time zone. rmm has an option to use a common time (UTC/GMT) instead of local time, avoiding similar problems during retention/expiration. See rmm books for use of UTC and TZ. Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IGGCSI to retrieve tape volume serial
Victor, yes, you can do that. the rmm CATSYNCH function does just that - retrieves all tape data sets from the catalogs and compares the results with the data sets known in its own CDS. You need to retrieve generation data sets as well as non-vsam, request at least the devtype and volser. Check the devtyp includes the tape bit (see ucb device type for details), and ignore hsm migrated data sets (because they have a devtyp that can look like tape). Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: TS7700: is there a z/OS interface to the TS3500 tape library?
Kees, I dont know of good interface. The books do mention a CLI which is available via Java. http://publib.boulder.ibm.com/infocenter/ts3500tl/v1r0/index.jsp?topic=%2Fcom.ibm.storage.ts3500.doc%2Fipg_3584_cli.html OAM provides possible alternatives: 1. D SMS LIBRARY(),DETAIL output contains a status line when there are no cleaner cartridges. 2. The library issues an alert to the host systems when something happens with cleaner cartridges, these are issued by OAM with CBR3750I, and contains things like OP0008 * The library is out of CST/ECCST cleaner cartridges. There are many alerts related to cleaner carts, see here http://publib.boulder.ibm.com/infocenter/ts7700/cust/index.jsp?topic=%2Fcom.ibm.storage.ts7740.doc%2Fts7740_ua_operator_info.html You could use automation to detect and parse the message and create your own alert to ops. Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Rmm extended dataset
Victor,
If your volumes have only a single file/data set one each volume you can use
the volume extract record ('V' - macro EDGRVEXT). If there are more data
sets/files, you should use extended extract records ('X' - macro EDGRXEXT).
Also if, 'volcnt' is supposed to be the number of volumes in the multi-volume
set, you need X records, and to use XVVOLCNT field.
RVUSE is the number of time a volume has been used - it equates to the number
of times any data set on the volume has been opened.
Look at the multi-volume, multi-data set report created by the Rexx reporting -
REPORT11.
And if you want something different but similar, start with EDGGR11 in the
report generator.
Mike Wood
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
