Toleration messages and RCMTOLR Datasets.

Document ID : KB000011338
Last Modified Date : 14/02/2018
Show Technical Document Details
Introduction:

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.

Question:

Is there a flag to turn the RCMTOLR messages off so they are not displayed or written to a dataset?

 

Environment:
DB2 for Z/OS
Answer:

There is a hlq.CDBAPARM(MIGRATOR) parameter called TOLRMSGS. This parameter will enable a YES or NO flag which will either allow or disallow the generation of the messages.

TOLRMSGS indicates whether to create the RCMTOLR data set and populate it during analysis. If Y, the RCMTOLR data set is created and populated during analysis. Messages are written about each object that is not yet supported by CA RC/Migrator in the subsystem. This is the default.

If N, the RCMTOLR data set is not created.

The parameter can be found in the header of the MIGRATOR parmlib member and appears like this:

TOLRMSGS (YES)       /* TURN TOLERATION MESSAGES ON
 		     /* OR OFF. SPECIFY NO TO NOT
		     /* GENERATE THE MESSAGES/DATASET.

This parm can also be added to the MIGRATOR member via the EP(Edit Parmlib Members) function on the main menu.
When editing the MIGRATOR member using EP you will see "Generate toleration msgs?....> Y (Y/N)" as an option to set.
Additional Information:

Unsupported Features Detection

See also technical document : TEC474663 regarding allocation options for the RCMTOLR dataset.