The types of errors that are caught during processing of the command definition statements include syntax errors, references to keywords and labels not defined, and missing statements.
The following types of errors detected by the command definition compiler stop the command from being created (severity codes are ignored).
Even after an error that stops the command from being created is encountered, the command definition compiler continues to check the source for other errors. Syntax errors and fixed value errors prevent final checking that identifies errors in user names and values or references to keywords or labels. Checking for syntax errors and fixed value errors does continue. This lets you see and correct as many errors as possible before you try to create the command again. To correct errors made in the source statements, you use the EDTF (Edit File) command, or you can use the Source Entry Utility (SEU), which is part of the WebSphere® Development Studio (formerly known as ADTS for AS/400®).
In the command definition source list, an error condition that relates directly to a specific source statement is listed after that command. Messages that do not relate to a specific source statement but are more general in nature are listed in a messages section of the list, not inline with source statements.