Explanation: The nesting depth of INCLUDE elements is limited to 9.
The specified Include object does not exist.
Object: '&01': Include '&02' not found in object '&03'.
The task could not be found in the activities. It was either already deactivated or a program error occured.
false
Explanation: A script that had been started via CallAPI was canceled by a user during generation.
Explanation: Script processing was stopped with the statement :STOP. Refer to the activation protocol for more detailed information. &01 = Object name
Explanation: Script processing was stopped with the statement :STOP NOMSG. The previously-defined message text provides additional information in the detail window. It is sent as part of the acknowledgement when calling the CallAPI and may be used to return the RunID of a started task to the CallAPI, for example.
Explanation: In order to find the error more easily, the object's name and line number in the script are output. Causes: The syntax check found an error &01 = Object name &02 = Script-line number
Explanation: Notification, Cockpit, Event, FileTransfer, Group, Job, ProcessFlow, QueueManager, Schedule and Script are executable objects. All other object types have a supportive function but cannot be executed. &01 = Object type
Explanation: An error occurred when attempting to open the file specified in the INCFILE statement. Status codes: see Knowledge-Base - Error codes - COBOL-File error
Explanation: An error occurred when reading from the file specified in the INCFILE statement. Status codes: see Knowledge Base - Error Codes - COBOL File Eerror (original text from Compiler Description)
Explanation: The statement :BEGIN_READ causes the DialogClient to create the form for the dialog. This was not possible. Possible reason: Probably a resource problem (non memory for form available). Solution: Close other applications or expand the memory of your PC.
Explanation: The object could not be inserted in the script. Possible reasons: In an INC/INCLUDE statement, the name of the include object was missing. Solution: * An INC/INCLUDE statement must contain the name of an existing include object. &01 = Name of the object &02 = Number of the script line &04 = Script element
Explanation: The replacement clause in the statement INC/INCLUDE/INCFILE was specified incorrectly. Possible reasons: * The string was not found. * A string of length zero (='') was specified. Solution: * The search string must be specified * The search string must be at least one character long. Syntax: :INC object name 'findstring' = 'replacestring' &01 = Name of the object &02 = Number of the script line &04 = Script element
Explanation: The replacement clause in the statement INC/INCLUDE/INCFILE was incorrectly specified. Possible reason: The search string and replacement string were not separated by "=". Solution: * The replace term must be fully specified. Syntax: :INC object name 'findstring' = 'replacestring' &01 = Name of the object &02 = Number of the script line &04 = Script element
Explanation: The length of a search string is limited. Possible reasons: * The specified string is too long * The delimiter at the end of the string is missing. Solution: Specify a shorter string or set the delimiter at the end of the string. Syntax: :INC object name 'findstring' = 'replacestring' &01 = Name of the object &02 = Number of the script line &04 = Invalid number of characters &05 = Maximum number of characters
Explanation: The length of the replacement string is limited. Possible reasons: * The specified string is too long * The delimiter at the end of the string is missing. Possible solution: * Specify a shorter string * Set the delimiter at the end of the string. Syntax: :INC object name 'findstring' = 'replacestring' &01 = Name of the object &02 = Number of the script line &04 = Invalid number of characters &05 = Maximum number of characters
Explanation: The underscore character "_" can be used for extra long lines to indicate that the text continues in the next line. The last character of a line should therefore be an underscore. The proximate line should start with a colon.
Explanation: Script lines must not exceed 255 characters. Lines may be split in order to keep a clear overview using the continuation character "_", but they are still regarded as one line. &01 = Object name &02 = Number of the script line
Use the service program DB Load to load the database.
Explanation: Search the task's script for possible constellations which might have produced this endless loop: 1) WHILE loops whose condition always apply, so they will never end. Check the condition and the Variables forming this condition. 2) Script whose processing takes long. Extremely long scripts which result in this message should be split to several objects. &01 = Name of the object &02 = Client &03 = Number of seconds
Permitted Include levels: "0" - Includes Pre Process (only in Jobs) and !Process (only in Events) "1" - Includes Process (only in Jobs and Events) "2" - Includes Post Process (only in Jobs) &01 = Name of the object &02 = Number of the script line