Taken from Strategy Analysis
During every strategy analysis, CA RC/Migrator™ for DB2 for z/OS checks for DB2 features that are not currently supported. If the product detects an attempt to operate on objects that exploit unsupported features, warning messages are directed to an output data set named RCMTOLR. If you do not want to use RCMTOLR, you can disable RCMTOLR data set creation by customizing the MIGRATOR parmlib member in hlq.CDBAPARM. However, we strongly recommend using RCMTOLR and checking for warning messages generated by the analysis before executing the strategy.
When RC/Migrator performs an analysis the RCMTOLR DD is produced by all releases. It is dynamically allocated with this format:
Users want to avoid the creation of this dataset using a userid as a HLQ.
Security violations often happen when the user doing the analysis does not have authority to create such a dataset.
How can this be avoided?
DB2 for Z/OS
The purpose of RCMTOLR is documented in the RC/Migrator user Guide in the section titled 'Strategy Analysis'.
Here are three different methods to avoid this situation. The choice of these would depend on whether the user actually wants to see the messages sent to this DD or not. Normally the dynamically allocated dataset is not available for viewing after completion of the job.
These options may cause an impact on CPU time usage so that is also a choice.