RMM question
Is there a way to perform a "SCRATCH IMMEDIATE" in Batch? Environment is z/OS 1.9 or later. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
RMM Question.
I receive a lot of RACF violation messages (sample below) that I believe to be rooted in a tape label gone bad. The RMM FM is a little confusing on what is going on. My security czar is grumping about a cluttered violation report. Q1: Am I correct? Is this nothing more than a bad tape? Q2: What, if anything, should I be doing differently? Q3: Is RMM trying to correct (rewrite) the label, and should that be allowed? IEC512I LBL ERR 0580, ,NL,PRIVAT,SL,MYJOB,FULLBKP,MY.DSN ICH408I USER(BATCH ) GROUP(BATCH ) NAME(PRODUCTION USER) 829 STGADMIN.EDG.LABEL. CL(FACILITY) INSUFFICIENT ACCESS AUTHORITY FROM STGADMIN.EDG.* (G) ACCESS INTENT(ALTER ) ACCESS ALLOWED(NONE ) EDG4042I VOLUME REJECTED. NL OR NSL VOLUME NOT SUPPORTED FOR A NON-SPECIFIC REQUEST EDG4005E VOLUME NL ON 0580 REJECTED FOR USE BY MYJOB, FULLBKP, OFFSITE Thanks!! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: RMM question
Allan, If you are happy for a batch solution, you can simply run EDGHSKP with EXPROC parm and it will scratch all the volumes that are pending release. You can even limit the processing uusing the SYSIN file to a subset (1 or more) volumes. This can handle any type of volume. If the volume(s) is not yet pending release you can do that with: RMM DV volser RELEASE For a non batch solution, but only if the tape is system managed and library resident. Release the volume: RMM DV volser RELEASE Ensure that the only release action is 'return to scratch'. If any others, you must take care of them. Use ISMF to change the status to scratch, or for one or more volumes you could use EDGSPLCS utility. Mike Wood RMM Development On Thu, 25 Mar 2010 08:30:17 -0500, Staller, Allan wrote: >Is there a way to perform a "SCRATCH IMMEDIATE" in Batch? > >Environment is z/OS 1.9 or later. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: RMM question
Our challenge is to release all but 1 copy of a "duplicate" tape dsn. A job is run and creates "DATASET1" After the fact a problem is discovered and the job is re-run. The rerun uncatalogs DATASET1 and re-creates the same file. Call this version DATASET2 (same dsn as DATASET1). There are now two version of this file (DATASET1(uncataloged) and DATASET2(cataloged)) under RMM control. We can programmatically identify DATASET1, but need a way to issue the "SCRATCH IMMEDIATE" from within this process. I hope this clarifies the question, Thanks again for your time, -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Mike Wood Sent: Friday, March 26, 2010 12:34 PM To: IBM-MAIN@bama.ua.edu Subject: Re: RMM question Allan, If you are happy for a batch solution, you can simply run EDGHSKP with EXPROC parm and it will scratch all the volumes that are pending release. You can even limit the processing uusing the SYSIN file to a subset (1 or more) volumes. This can handle any type of volume. If the volume(s) is not yet pending release you can do that with: RMM DV volser RELEASE For a non batch solution, but only if the tape is system managed and library resident. Release the volume: RMM DV volser RELEASE Ensure that the only release action is 'return to scratch'. If any others, you must take care of them. Use ISMF to change the status to scratch, or for one or more volumes you could use EDGSPLCS utility. Mike Wood RMM Development On Thu, 25 Mar 2010 08:30:17 -0500, Staller, Allan wrote: >Is there a way to perform a "SCRATCH IMMEDIATE" in Batch? > >Environment is z/OS 1.9 or later. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: RMM question
If your RMM is configured to automatically protect all tapes (unless otherwise specified in JCL) for as long as the dataset is properly cataloged, then you don't have worry about tapes with duplicate datasets not expiring. When the dataset is recreated and recataloged, RMM-housekeeping will automatically expire and scratch the now uncataloged first copy (usually after xx days of grace period, depending on your settings). So there's no need to go after such beasts by means of running special searches, in order to recover scratch tapes. Check your RMM retention criteria and see what rules are in effect. Then see what RMM rules need to be changed to solve your problem for you. IMHO, for most run-of-the-mill tape datasets, the default should be "retain while cataloged". Of course, this excludes "special purpose tapes" like DFHSM tapes or tape datasets requiring explicitly specified retention periods or expiration dates. Regards, Ulrich Krueger -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Staller, Allan Sent: Friday, March 26, 2010 10:55 To: IBM-MAIN@bama.ua.edu Subject: Re: RMM question Our challenge is to release all but 1 copy of a "duplicate" tape dsn. A job is run and creates "DATASET1" After the fact a problem is discovered and the job is re-run. The rerun uncatalogs DATASET1 and re-creates the same file. Call this version DATASET2 (same dsn as DATASET1). There are now two version of this file (DATASET1(uncataloged) and DATASET2(cataloged)) under RMM control. We can programmatically identify DATASET1, but need a way to issue the "SCRATCH IMMEDIATE" from within this process. I hope this clarifies the question, Thanks again for your time, -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Mike Wood Sent: Friday, March 26, 2010 12:34 PM To: IBM-MAIN@bama.ua.edu Subject: Re: RMM question Allan, If you are happy for a batch solution, you can simply run EDGHSKP with EXPROC parm and it will scratch all the volumes that are pending release. You can even limit the processing uusing the SYSIN file to a subset (1 or more) volumes. This can handle any type of volume. If the volume(s) is not yet pending release you can do that with: RMM DV volser RELEASE For a non batch solution, but only if the tape is system managed and library resident. Release the volume: RMM DV volser RELEASE Ensure that the only release action is 'return to scratch'. If any others, you must take care of them. Use ISMF to change the status to scratch, or for one or more volumes you could use EDGSPLCS utility. Mike Wood RMM Development On Thu, 25 Mar 2010 08:30:17 -0500, Staller, Allan wrote: >Is there a way to perform a "SCRATCH IMMEDIATE" in Batch? > >Environment is z/OS 1.9 or later. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: RMM question
Allan, If 'DATASET1' is a GDG rmm will treat the older copy as a duplicate and you should get what you want. RMM now has a parmlib option to control how duplicate GDGs are handled - OPTION GDG If the data set is not a GDG, processing of the 'duplicates' depends on your managing VRS: A VRS with WHILECATALOG - the uncataloged data sets are not retained A VRS with CYCLES - you have to check the VRS COUNT and figure out whether the duplicate cycles will cause cycles you still need to be bumped from VRS. RMM has ways to help get volumes back to scratch. But it does this by first 'releasing'/expiring the volume. So instead of thinking how to 'scratch immediate' think about how to release the volume. 1. You can use the 'DELETE' VRS and mark the duplicate data sets as DELETED using CHANGEDATASET command 2. If this is only data set on the volume; issue RMM DV volser RELEASE Mike Wood RMM Development On Fri, 26 Mar 2010 12:55:13 -0500, Staller, Allan wrote: >Our challenge is to release all but 1 copy of a "duplicate" tape dsn. > >A job is run and creates "DATASET1" >After the fact a problem is discovered and the job is re-run. >The rerun uncatalogs DATASET1 and re-creates the same file. Call this >version DATASET2 (same dsn as DATASET1). >There are now two version of this file (DATASET1(uncataloged) and >DATASET2(cataloged)) under RMM control. > >We can programmatically identify DATASET1, but need a way to issue the >"SCRATCH IMMEDIATE" from within this process. > >I hope this clarifies the question, > >Thanks again for your time, -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: RMM Question.
I take it this is a tape not known by RMM? Outside tape? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: RMM Question.
Nope. It is internal. There apparently is an I/O error on the label. -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of salah Balboul Sent: Tuesday, May 24, 2005 10:41 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: RMM Question. I take it this is a tape not known by RMM? Outside tape? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: RMM Question.
STGADMIN.EDG.LABEL. gives you right to change label type from NL to SL (or AL). ALTER is required, when the requested tape is scratch one. Probably it was requested as "regular" scratch, and that's why it was rejected. A message EDG4042I says the same. You can check the tape - in RMM database (use panels) - what label type is on the tape ? - using any tool, or IEBGENER with BLP to check the labels on the tape. I don't know what about re-lablelling, probably the tape should be re-labelled using EDGINERS. HTH -- Radoslaw Skorupka Lodz, Poland -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: RMM Question.
Hal, unlabelled tapes in the scratch pool are not a good idea. How will RMM know what the volume is really called or which record in the CDS to use to record the metadata? I realize that the volume probably appears to have no label because of an I/O error, but it materializes as a NL tape mounted. The IEC512I message does not indicate an I/O error; it indicates there was no label read from the tape and that one was expected - I would expect additional message if there was in fact an error reading the tape volume. RMM does not normally support NL scratch tapes. However, there are 2 ways it can; 1. You are using IBM system managed, automated, tape library; rmm will use the volser obtained by the vision system and label the tape during open. 2. You exploit the IFG019VM installation exit (sample EDG019VM) to get the volser from the operator, rmm then gets the tape labelled during open. As Radoslaw has said, the ICH408I is issued because RMM attempts to see if the user is authorized to change the volume label. He also has good suggestion about EDGINERS. Set the volume INIT action and leave it to EDGINERS to label it correctly (once you figured out which volume was actually mounted). Mike WoodRMM Development -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
