Hi Radoslaw, RMM no longer recommends using REJECT commands for this purpose.
In the Implementation and Customization Guide, in Chapter 8, you can find the replacement functionality through OPENRULE and PRTITION statements Here is an excerpt from the book: Note: While the REJECT command is still supported by DFSMSrmm, you should use the OPENRULE (described in “Controlling the use of tape volumes: OPENRULE” on page 157) and PRTITION (described in “Partitioning tape volumes: PRTITION” on page 196) commands to prevent a range of tapes from being used on a particular system. If you are already using REJECT commands, you should consider converting them to OPENRULE and PRTITION commands. See “Converting REJECT commands to PRTITION and OPENRULE commands” on page 203. I believe what you would be looking for is this or something similar: OPENRULE VOLUMERANGE(‘start’:’end’) IGNORE TYPE(NORMM) There may be a more appropriate set of keywords for you, so I recommend looking into converting your REJECT statements, or reading on how OPENRULE works to best fit your situation. Feel free to reach out directly if you’d like to share more information away from the larger group. Cheers, Parker -- Parker Mathewson z/OS DFSMS RMM Product Owner IBM Denver, Colorado From: IBM Mainframe Discussion List <[email protected]> on behalf of Radoslaw Skorupka <[email protected]> Date: Tuesday, April 8, 2025 at 6:42 AM To: [email protected] <[email protected]> Subject: [EXTERNAL] Re: RMM automatically adds the volumes To clarify: ftp is not an option. Regarding security issues - I'm allowed to read the data on both systems and I am the RACF guy on both. Last, but not least, it is not production data. While data security is quite interesting topic, it is not an issue here. -- Radoslaw Skorupka Lodz, Poland W dniu 08.04.2025 o 14:23, Jousma, David pisze: > However I noticed every tape volume I read was automatically added to > > RMM database, which I don't want. > > Q: How to prevent it? > >>> Don’t read the tapes directly, FTP the contents from one environment to the >>> other. Separately, Doing what you did is likely a security exposure if >>> you are not sharing or propagating the RACF permits between the separate >>> environments, where you have access to the DSN on the local system, but not >>> on the remote system. > Dave Jousma > Vice President | Director, Technology Engineering > > > > > > From: IBM Mainframe Discussion List<[email protected]> on behalf of > Radoslaw Skorupka<[email protected]> > Date: Tuesday, April 8, 2025 at 8:09 AM > To:[email protected] <[email protected]> > Subject: RMM automatically adds the volumes > > > > The following scenario: > > VTS shared among several z/OS monoplex systems. Each system has it's own > > set of tape categories in DEVSUPxx. > > I had to read multiple tape volumes from other system. > > So I temporarily added the volumes to the VOLCAT, disabled "REJECT > > ANYUSE(*)" in EDGRMMxx and I read the tapes successfully. > > > > However I noticed every tape volume I read was automatically added to > > RMM database, which I don't want. > > Q: How to prevent it? > > > > The only method I'm aware now is to stop RMM and reset the subsystem, > > but it is not good idea, because some other users should be able to > > access the tapes under RMM control. > > > > BTW: a tape must be read to be added to RMM db. I did not read few tapes > > previously added to the VOLCAT and those tapes were not added to RMM. > > > > BTW2: I deleted the volumes automatically added to RMM. > > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
