This substring is part of an error message relating to procedure calls. For instance, if a catalog item had a parameter <name> (for example, box), then the substring appears as following:

This error occurs when a field is expanded to a zero-length string, for example, if a parameter was inserted, but left blank.

Procedure names are not allowed to have spaces. A procedure string click from list is an invalid procedure. If the system detects a field with spaces, it issues an additional error message that is nested within the procedure error message.

This error occurs if the procedure name contains valid characters, but no procedure exists (procedure name) that can be called from within the system.

This error occurs if the procedure name contains valid characters (that is, no spaces) and the name is in scope, but it is not a procedure. For instance, the label could be trying to call procedure name design_name(), but the value of design_name could be Fred, which is a type string, not a procedure.

After the system confirms that the procedure to be called is a valid one, it parses each parameter to expand any fields or procedures that are embedded within the parameters. For instance, the format string [string_left (<name, 3)] would mean that the first parameter, <name>, needs to be expanded to obtain the value of the name parameter. However, the field cannot be expanded because it is missing its terminating bracket (>). The error message would then be *Invalid parameter <name at position 1, parse message *field not correctly terminated name’*’*. Because this error message also lists all the correctly parsed parameters, you can easily recognize the error’s position in the parameter list.