LIKE is Not Allowed When Defining Variables Or Temp Table Fields

The rule “nolike” presents a warning when it encounters a definition of a variable, parameter, or temp-table field “like” a field in the database. Defining a temp table like another or like a database table is acceptable. It is variables, parameters, and fields that are not.
The Risk:
Using LIKE in code embeds the CRC of the referenced table in your program. If this is the only reference to the table in your program, it can be missed in cross-reference searches and not be noticed as needing a recompile when the table changes. It also requires the maintenance programmer to know the attributes of the table.field, and copies far more attributes into the r-code than is likely that the coder intended. It also expands the scope of any regression testing that may need to occur if the referenced table.field (or even table) is modified – often unnecessarily.
How to solve this:
Hand-write the variable/field specifications in your code.

How to suppress these warnings:
You can put the directive {&_proparse_prolint-nowarn(nolike)} directly before the statement that contains the LIKE keyword. See also: suppress warnings