Specifying an undefined custom field keyword

If you attempt to add data specifying an undefined custom field keyword, a message similar to the following is issued:

Example:

IKJ56702I INVALID OPERAND, HOMEADDR

The custom field operand might be undefined for any one of several reasons. For example, one of the following errors might have occurred:

The custom field was not defined using the RDEFINE command.
The custom field was defined with attributes that are inconsistent with its data type.
The IRRDPI00 UPDATE command was not issued to refresh the dynamic parse definitions. (Use the IRRDPI00 LIST command to determine if the custom field is active.)
The CFIELD class was not active when the IRRDPI00 UPDATE command was issued.
The custom field keyword was incorrectly specified due to a typographical error and does not match the custom field name.