| Text | Error in ACTION clause of PROCESS COMMAND statement. |
| Expl. | One of the following errors has occurred in a PROCESS COMMAND
statement: - The keyword "ACTION" is missing. - No action or an invalid action has been specified after the keyword "ACTION". See the Natural documentation for the correct PROCESS COMMAND syntax. |
| Actn. | Correct error in program. |
| Text | Error in USING clause of PROCESS COMMAND statement. |
| Expl. | One of the following errors has occurred in a PROCESS COMMAND statement: - The keyword "USING" is missing. - The USING operand conflicts with the specified action. - One of the values specified in the USING clause does not agree with the field to which it is assigned. - An equal sign "=" is missing between a field and its value. |
| Actn. | Correct error in program. |
| Text | Error in GIVING clause of PROCESS COMMAND statement. |
| Expl. | One of the following errors has occurred in a PROCESS COMMAND
statement: - The keyword "GIVING" is missing. - One of the fields specified in the GIVING clause conflicts with the action specified in the ACTION clause. - One of the fields required for the specified action has not been defined (in the DEFINE DATA statement or GIVING clause). - If a DEFINE DATA statement is used, the GIVING clause is not allowed. |
| Actn. | Correct error in program. |
| Text | Processor name is invalid or missing. |
| Expl. | In the USING clause of a PROCESS COMMAND statement, you have specified the name of a Command Processor which is invalid or does not exist. |
| Actn. | Either specify the correct name or specify the name of an existing Command Processor. |
| Text | Specified object is not a Command Processor. |
| Expl. | In the USING clause of a PROCESS COMMAND statement, you have specified the name of an object which is not a Command Processor. |
| Actn. | Use a Command Processor name. Check also your ampersand "&" notation. |
| Text | Processor ... not found. |
| Expl. | In the USING clause of a PROCESS COMMAND statement, you have
specified the name of a Command Processor which does not exist. |
| Actn. | Specify an existing Command Processor. |
| Text | Command not accepted. |
| Expl. | Possible reasons for this error: - the command line is empty - the command line contains special characters (such as underscores). |
| Actn. | Correct the command line input. |
| Text | Invalid use of field .... |
| Expl. | For valid usage, see the Natural documentation, PROCESS COMMAND statement, ACTION GET/SET and in particular the list of possible values for GETSET-FIELD-NAME. |
| Actn. | Correct values. |
| Text | Contents of field ... not accepted. |
| Expl. | The format/length of the field does not conform to the
definitions as listed for the PROCESS COMMAND statement, action SET, in the Natural documentation. |
| Actn. | Check format/length of field. |
| Text | Invalid field name ... for action ... . |
| Expl. | There is a conflict between the GETSET-FIELD-NAME used in the GET and the SET actions, or the value used in the SET action is invalid. In case the GET action refers to the LAST-BUFFER, this error indicates that this buffer is not available. |
| Actn. | Check program syntax. |
| Text | Command Data error ... . |
| Expl. | This error occurs at runtime when the command line contains data that are in conflict with the Command Processor definition. This might occur, for example, if a delimiter is missing. The data that cannot be interpreted are indicated in the variable ... . |
| Actn. | Check command line input against the Command Processor definition and correct error. |
| Text | Natural Command Processor - security error ... . |
| Expl. | This error is caused by Natural Security. |
| Actn. | Contact your Natural Security administrator. |
| Text | Command Processor ... not allowed. |
| Expl. | You are not authorized to use this Command Processor. |
| Actn. | Contact your Natural Security administrator. |
| Text | Keyword ... not allowed. |
| Expl. | You are not authorized to use this keyword. |
| Actn. | Contact your Natural Security administrator. |
| Text | This command is not allowed. |
| Expl. | You are not authorized to use this command. |
| Actn. | Contact your Natural Security administrator. |
| Text | Inconsistent security definition for Command Processor. |
| Expl. | The command processor was cataloged after the functional security was defined. Therefore the processor and the functional security information don"t match. |
| Actn. | Contact your Natural Security administrator. |
| Text | Cannot ... PRIVATE synonyms. |
| Expl. | Either you do not have authorization for this function; or the Command Processor header definition does not permit this function |
| Actn. | Contact your Natural Security administrator. |
| Text | PRIVATE synonym ... not found. |
| Expl. | The PRIVATE synonym you have specified cannot be found. |
| Actn. | For details on PRIVATE synonyms, see the PROCESS COMMAND
statement, PRIVATE clause, in the Natural documentation. |
| Text | Keyword ... not found. |
| Expl. | This may be because you have not specified the keyword correctly. |
| Actn. | Check that you have entered the keyword name correctly,
particularly regarding upper and lower case characters, and the length of an abbreviated keyword. |
| Text | Keyword ... is not used in the correct context. |
| Expl. | This is a semantic error. For example, it does not make sense to say: UPDATE DELETE |
| Actn. | Check and correct the semantics. |
| Text | Keyword of type :1: is missing. |
| Expl. | The command you issued is missing an essential keyword. Without this keyword the command cannot be interpreted. |
| Actn. | Check to see which keywords of the type mentioned can be used together with the keyword(s) entered. Choose the appropriate one. |
| Text | Keyword sequence error. |
| Expl. | You have entered keywords in a sequence other than that specified in the Command Processor header. For example, you may have specified keywords in the order: ACTION OBJECT where the order OBJECT ACTION is required. |
| Actn. | Enter keywords in the correct sequence. |
| Text | This command is not defined. |
| Expl. | You have specified a command that is not defined. For example, you might have entered DELETE CUSTOMER but no such command exists, even though the keywords DELETE and CUSTOMER do exist. |
| Actn. | Specify a valid command. |
| Text | Command Data disallowed. |
| Expl. | No data can be entered with this command. |
| Actn. | Enter the command without data. |
| Text | Data element with more than :1: characters found. |
| Expl. | The data element entered contains more than the legal number of characters. |
| Actn. | Check the legal range of input for the data element and correct your input. |
| Text | Data element contains non-numeric character :1:. |
| Expl. | A non-numeric character was entered as part of the data element. A data element can contain only numeric characters. |
| Actn. | Correct the data element input. |
| Text | Error ... in buffer for Natural Command Processor. |
| Expl. | This is an unexpected error. NCPWORK cannot be accessed. |
| Actn. | Contact Software AG support. |
| Text | Invalid GETMAIN request for Natural Command Processor. |
| Expl. | NCPWORK cannot be opened. This may be because the thread is exhausted. |
| Actn. | Reduce ESIZE/FSIZE. Use the BUS command to find out how much space you have. |
| Text | GETMAIN failed for ... KB for Command Processor buffer. |
| Expl. | There is not enough space in your Natural thread. The value ... indicates the number of KB you cannot request. |
| Actn. | Ask your Natural administrator to decrease ESIZE or FSIZE. |
| Text | Buffer for Natural Command Processor is not allocated. |
| Expl. | Either: The NCPWORK buffer has been overwritten so the GET / SET action cannot be fulfilled. Or: The Command Processor has been closed. |
| Actn. | Open the Command Processor using the PROCESS COMMAND statement ACTION EXEC. |
