Re: Rmm and BLP
Mike, When you use BLP, RMM does still use the actual volser from the mounted volume for its processing. No matter what volser you code in your JCL, rmm checks both that volser against volumes in the CDS and also the mounted volume. If one of them matches an rmm managed volume you had better have the correct volser in JCL and mounted. You could use EXPDT=98000 to have rmm 'ignore' this request. You could also use the 'duplicate volume' support to define X00123 as a volume to RMM with an internal volser of 000123 and then do not need either BLP or EXPDT=98000. If you use ignore processing you must be authorized to do that. See STGADMIN.EDG.IGNORE.TAPE. . . . profiles in FACILITY class. See IC uide for details. The authorization is based on the MOUNTED volser by default, and whether we use RMM or NORMM in the authorization resource is based on what we find for THAT mounted volume. You can use EDGUX100 to request the REQUESTED volume is used instead. Mike Wood RMM Development On Wed, 9 Aug 2006 13:40:13 -0400, Martin, Mike [EMAIL PROTECTED] wrote: All, We have production jobs that read tapes that come from outside our company. Because we cannot predict what the internal tape volsers will be, our production jobs have been setup to use BLP. (the volsers for these tapes may or may not match a volser in our shop) The following DD is an example of how we use BLP for a tape from an outside source... //DOTIN DD DSN=OUTSIDE.TAPE, // VOL=SER=X00123, // DISP=OLD,LABEL=(2,BLP),UNIT=TAPE, // DCB=(RECFM=FB,BLKSIZE=4000,LRECL=50,DEN=3) But when we run this job with rmm active (warning mode), rmm indicates that the tape will be rejected... EDG4048I VOLUME 000123 REJECTED. MOUNTED VOLUME DOES NOT EQUAL REQUESTED VOLUME EDG4004I **WARNING** USE OF 000123 BY ABCR0254, STEP40, INTAPE ONLY PERMITTED BECAUSE DFSMSrmm RUNNING IN WARNING MODE Apparently, the internal volser for the tape happens to match one of our tapes (that rmm has in the CDS). I understand the message and I am looking for a simple solution so that the production jobs do not fail once we cutover to rmm. I am looking for a painless solution. My preference is to avoid making any JCL changes. (also, FYI we are using the supplied EDGUX100) We are z/OS 1.4 Mike Martin -- 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 and BLP
On Wed, 9 Aug 2006 13:40:13 -0400, Martin, Mike [EMAIL PROTECTED] wrote: All, We have production jobs that read tapes that come from outside our company. Because we cannot predict what the internal tape volsers will be, our production jobs have been setup to use BLP. (the volsers for these tapes may or may not match a volser in our shop) I am looking for a painless solution. My preference is to avoid making any JCL changes. (also, FYI we are using the supplied EDGUX100) We are z/OS 1.4 Mike Martin The supplied EDGUX100 supports using EXPDT=98000 to indicate a foreign tape that should be ingored by RMM. For example: LABEL=(2,BLP,EXPDT=98000) -Rob -- 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
Rmm and BLP
All, We have production jobs that read tapes that come from outside our company. Because we cannot predict what the internal tape volsers will be, our production jobs have been setup to use BLP. (the volsers for these tapes may or may not match a volser in our shop) The following DD is an example of how we use BLP for a tape from an outside source... //DOTIN DD DSN=OUTSIDE.TAPE, // VOL=SER=X00123, // DISP=OLD,LABEL=(2,BLP),UNIT=TAPE, // DCB=(RECFM=FB,BLKSIZE=4000,LRECL=50,DEN=3) But when we run this job with rmm active (warning mode), rmm indicates that the tape will be rejected... EDG4048I VOLUME 000123 REJECTED. MOUNTED VOLUME DOES NOT EQUAL REQUESTED VOLUME EDG4004I **WARNING** USE OF 000123 BY ABCR0254, STEP40, INTAPE ONLY PERMITTED BECAUSE DFSMSrmm RUNNING IN WARNING MODE Apparently, the internal volser for the tape happens to match one of our tapes (that rmm has in the CDS). I understand the message and I am looking for a simple solution so that the production jobs do not fail once we cutover to rmm. I am looking for a painless solution. My preference is to avoid making any JCL changes. (also, FYI we are using the supplied EDGUX100) We are z/OS 1.4 Mike Martin FONT SIZE=1 FACE=ARIAL^ This email may contain confidential and privileged material for the sole use of the intended recipient. If you are not the intended recipient, please contact the sender and delete all copies. Any review or distribution by others is strictly prohibited. Personal emails are restricted by policy of the State Employees' Credit Union (SECU). Therefore SECU specifically disclaims any responsibility or liability for any personal information or opinions of the author expressed in this email. /FONT -- 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 and BLP
I don't know RMM but some tape management systems have a method of identifying tapes that are not managed even if the volser matches one that is. EXPDT=98000 seems to be popular (based on the number of ISV products that include it in the installation JCL). -Original Message- From: Martin, Mike [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 09, 2006 10:40 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Rmm and BLP All, We have production jobs that read tapes that come from outside our company. Because we cannot predict what the internal tape volsers will be, our production jobs have been setup to use BLP. (the volsers for these tapes may or may not match a volser in our shop) The following DD is an example of how we use BLP for a tape from an outside source... //DOTIN DD DSN=OUTSIDE.TAPE, // VOL=SER=X00123, // DISP=OLD,LABEL=(2,BLP),UNIT=TAPE, // DCB=(RECFM=FB,BLKSIZE=4000,LRECL=50,DEN=3) But when we run this job with rmm active (warning mode), rmm indicates that the tape will be rejected... EDG4048I VOLUME 000123 REJECTED. MOUNTED VOLUME DOES NOT EQUAL REQUESTED VOLUME EDG4004I **WARNING** USE OF 000123 BY ABCR0254, STEP40, INTAPE ONLY PERMITTED BECAUSE DFSMSrmm RUNNING IN WARNING MODE Apparently, the internal volser for the tape happens to match one of our tapes (that rmm has in the CDS). I understand the message and I am looking for a simple solution so that the production jobs do not fail once we cutover to rmm. I am looking for a painless solution. My preference is to avoid making any JCL changes. (also, FYI we are using the supplied EDGUX100) -- 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 and BLP
In a recent note, Martin, Mike said: Date: Wed, 9 Aug 2006 13:40:13 -0400 //DOTIN DD DSN=OUTSIDE.TAPE, // VOL=SER=X00123, // DISP=OLD,LABEL=(2,BLP),UNIT=TAPE, // DCB=(RECFM=FB,BLKSIZE=4000,LRECL=50,DEN=3) EDG4048I VOLUME 000123 REJECTED. MOUNTED VOLUME DOES NOT EQUAL REQUESTED What interests me is that you specified X00123, yet the message refers to 000123. Is there, perhaps, an Exit which converts non-numeric characters in volsers to '0'? Ugh! Far too much DWIM for me. I would have suggested a lower case character: // VOL=SER='x00123', ... the defense by obfuscation; no one else is apt to use a lower case in a volser. I thought this used to work, but I just tried it, and in the mount message, at least, it was folded to upper. Still, too much DWIM. If the system thinks my _quoted_ string contains an invalid construct, I would prefer JCL error to the system's guess at a substitution. Wouldn't have worked anyway. The operator could never enter the correct reply to the Confirm VSN message. -- gil -- StorageTek INFORMATION made POWERFUL -- 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
