Reason:
The OML I/O manager has successfully initialized.
System Action:
None.
User Action:
None.
Reason:
The OML I/O manager has recovered from an I/O subtask abend. The abend code is shown in the message.
System Action:
The subtask is restarted.
User Action:
Examine the abend code and take corrective action if required.
Reason:
The OML I/O manager has detected an I/O error on a procedure library while attempting to load the named procedure. I/O error information is displayed.
System Action:
The load is retried.
User Action:
Examine the I/O error information and take corrective action if required.
Reason:
An OMLCTL CMDREPL command failed. The requested command procedure could not be found.
System Action:
The command replacement fails.
User Action:
Ensure that the command replacement procedure is in the COMMANDS library concatenation.
Reason:
An OML load request asked for a particular procedure type (eg FUNCTION). The loaded procedure type was not as expected.
System Action:
The load fails.
User Action:
Check that the procedure starts with the correct statement type, e.g., for a function, the FUNCTION statement.
Reason:
An OML procedure that had the 'CALLONLY' attribute was loaded for a non-callonly requestor, for example, to be executed as a command.
System Action:
The load fails.
User Action:
CALLONLY procedures cannot be executed from OCS, etc. Check the requirement to execute the procedure in this manner.
Reason:
On OMLCTL UNLOAD command requested that a procedure be purged from storage. This message confirms the request has been done.
System Action:
None.
User Action:
None.
Reason:
On OMLCTL UNLOAD command requested that a procedure be purged from storage. The procedure is currently in use and will be purged when its use count drops to 0. Any new requests for the procedure will trigger the loading of a new copy.
System Action:
None.
User Action:
None.
Reason:
An OMLCTL PRELOAD command has completed.
System Action:
None.
User Action:
None.
Reason:
An OMLCTL CMDREPL command has completed. The command has been replaced by an OML procedure.
System Action:
None.
User Action:
None.
Reason:
An OMLCTL CMDREPL command has failed. There is already a procedure of that command name loaded.
System Action:
None.
User Action:
Unload the old procedure if required and retry.
Reason:
An OMLCTL UNLOAD command has failed. You cannot unload a command replacement procedure with this command.
System Action:
None.
User Action:
Use the OMLCTL CMDREPL OPT=UNLOAD command if necessary.
Reason:
On OMLCTL PRELOAD command requested preloading of a procedure that is already preloaded.
System Action:
The command is ignored.
User Action:
Use OMLCTL UNLOAD to unload the preloaded procedure if a new copy is to be loaded.
Reason:
An OMLCTL CMDREPL command failed for one of the following reasons:
System Action:
The command is ignored.
User Action:
Use SHOW EQUATES, SHOW NCLSTAT, and SHOW OMLSTST to determine the cause of the problem.
Reason:
An OMLCTL UNLOAD command failed. The requested procedure is not presently loaded.
System Action:
The command is ignored.
User Action:
None.
Reason:
An OMLCTL CMDREPL UNLOAD command failed. The requested procedure is not presently loaded.
System Action:
The command is ignored.
User Action:
None.
Reason:
An OMLCTL CMDREPL UNLOAD command failed. The requested procedure is not a CMDREPL procedure.
System Action:
The command is ignored.
User Action:
None.
Reason:
An UNLOAD PROCEDURE= (or OMLCTL UNLOAD) command has been issued specifying a generic procedure or DD name. This message shows the total OML procedures unloaded as a result of the command.
System Action:
The procedures are reloaded, as required.
User Action:
None.
Reason:
An OML compile/load failed due to a shortage of storage.
System Action:
The OML compile or load fails.
User Action:
Investigate the storage shortage.
Reason:
An OML compile/load failed due to a problem opening the requested member. A reason is given.
System Action:
The OML compile or load fails.
User Action:
Investigate the reason for the failure.
Reason:
An OML compile/load failed due to the requested member being NCL.
System Action:
The OML compile or load fails.
User Action:
Convert the source to OML and re-compile.
Reason:
An OML compile/load failed due to an I/O error. A second attempt is made to compile after closing and reopening the library.
Note: This message is logged only.
System Action:
A second attempt is made to load the procedure.
User Action:
None.
Reason:
During compilation of an OML procedure an end-of-file condition was encountered before any statements were found. srcloc shows the source location of the end of file.
System Action:
Compilation of the procedure fails.
User Action:
Add some statements to the file.
Reason:
During compilation of an OML procedure an end-of-file condition was encountered during processing of a nested statement (eg IF/THEN/ELSE). srcloc shows the location of the statement in error
System Action:
Compilation of the procedure fails.
User Action:
Complete the nested statement.
Reason:
During compilation of an OML procedure an end-of-file condition was encountered either:
srcloc shows the source location of the statement in error
aaa shows the number of DO groups which have not been terminated
bbb shows the number of PROCEDUREs or FUNCTIONs which have not been terminated
System Action:
Compilation of the procedure fails.
User Action:
Add an END statement for each DO group, PROCEDURE or FUNCTION statement.
Reason:
The first statement in an OML procedure must be a PROCEDURE or FUNCTION statement. The procedure being compiled does not have one of these as the first statement. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Add a PROCEDURE or FUNCTION statement as the first executable statement in the procedure. Also make sure a corresponding END statement exists.
Reason:
During compilation of an OML procedure, statements were found after the END statement which terminated the source of the procedure or function. This is invalid. It indicates there may be incorrect pairing of DO/END statements. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Check the pairing of DO/END statements. If the code was not to be included in the procedure, remove it from the source file, or enclose the code in comment delimiters (/* comment */).
Reason:
During the compilation of an OML procedure, a label was found on a statement that is nested (for example, IF cond THEN LAB: IF ....). This construction is invalid. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Remove the label from the statement.
Reason:
During compilation of an OML procedure more than 16,000,000 lines of source text were found. 16,000,000 is the maximum number allowed.
System Action:
Compilation of the procedure fails.
User Action:
Divide the source file into several source files, each with not more than 16,000,000 lines.
Reason:
The first executable statement in an OML procedure was not a PROCEDURE statement, so one has been inserted automatically. A corresponding END statement is also inserted at the end of the source. This message is a warning only and does not cause a compilation failure. srcloc shows the source location of the PROCEDURE statement.
System Action:
Compilation of the procedure continues.
User Action:
None.
Reason:
During compilation of an OML procedure, a verb was encountered which had a compilation error.
srcloc shows the source location of the statement in error
verbname shows the name of the verb
reason shows the reason for the compilation failure
System Action:
Compilation of the procedure fails.
User Action:
Correct the syntax of the verb and retry.
Reason:
During compilation of an OML procedure, a statement was found which was not recognised as a valid OML statement type. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Remove or correct the statement.
Reason:
During compilation of an OML procedure, an assignment statement was found which attempted to update a system variable which cannot be updated.
srcloc shows the source location of the statement in error.
varname shows the name of the variable.
System Action:
Compilation of the procedure fails.
User Action:
Remove or correct the statement.
Reason:
During compilation of an OML procedure, an assignment statement was found which attempted to update a system variable with a null value. Null is not a valid value for the system variable.
srcloc shows the source location of the statement in error.
varname shows the name of the system variable.
System Action:
Compilation of the procedure fails.
User Action:
Remove or correct the statement.
Reason:
During compilation of an OML procedure, an assignment statement was found which attempted to update a variable with a null name.
srcloc shows the source location of the statement in error.
varname shows the name of the variable.
System Action:
Compilation of the procedure fails.
User Action:
Remove or correct the statement.
Reason:
During compilation of an OML procedure, a SELECT statement was found without a following WHEN statement. The statement following a SELECT statement must always be a WHEN statement. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Insert a WHEN statement following the SELECT statement.
Reason:
During compilation of an OML procedure, a WHEN statement was processed which was not followed by an allowable statement type. The statement following a WHEN statement must always be:
srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Insert a WHEN, OTHERWISE or END statement following the WHEN statement. This error can also indicate incorrect DO/END pairing in the logic of the WHEN statement.
Reason:
During compilation of an OML procedure, a statement was encountered which was not recognisable as a valid verb or assignment statement. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Correct the syntax of the statement, or remove it, or enclose it in comment delimiters (/* */).
Reason:
During compilation of an OML procedure, a statement was encountered which was not a recognisable verb or assignment statement. The syntax of the statement indicates it may be a verb which is not supported by the system on which the compilation is taking place. srcloc shows the source location of the statement in error
System Action:
Compilation of the procedure fails.
User Action:
Correct the syntax of the statement, or remove it, or enclose it in comment delimiters (/* */). This error can be caused by an incorrectly spelt verb name. If the verb is valid but not supported by the system, use %%OPTIONS DEFER to avoid compilation errors. If the verb is encountered during execution an error will be raised.
Reason:
During compilation of an OML procedure, a statement was encountered which was not recognisable as a valid verb or assignment statement. The syntax of the statement indicates it may be a verb which is not supported by the system on which compilation is taking place.
%%OPTIONS DEFER is in effect, so compilation does not fail for this error, but if the verb is encountered during execution an error will be raised. This message is sent as a warning of the situation.
srcloc shows the source location of the statement in error.
verbname shows the name of the verb.
System Action:
Compilation of the procedure continues.
User Action:
Make sure the verb name has been spelt correctly. If so, make sure the logic in the procedure will not execute the verb unless the verb is supported by the system (eg.if verb is an MAI verb, check that MAI is installed, using the ZFEATURE built-in function).
Reason:
During compilation of an OML procedure, a statement was encountered which was not recognisable as a valid verb or assignment statement. The syntax of the statement indicates it may be a verb which is not supported by the system on which the compilation is taking place.
%%OPTIONS DEFER is in effect, but is ignored because the compilation is producing executable object.
srcloc shows the source location of the statement in error.
verbname shows the name of the verb.
System Action:
Compilation of the procedure fails.
User Action:
Make sure the verb name is spelt correctly. If so, make sure the system is licensed for the feature to which the verb belongs.
Reason:
During compilation of an OML procedure, an IF statement was encountered which had invalid syntax or was not followed by a THEN statement. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Correct the syntax of the statement, or insert a THEN statement after the conditional expression.
Reason:
During compilation of an OML procedure, an ELSE statement was encountered which was not preceded by an IF/THEN statement combination. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Examine the preceding statements to locate the IF/THEN combination. If not found, insert them. If found, this could indicate incorrect DO/END pairing in the THEN logic.
Reason:
During compilation of an OML procedure, a WHEN statement was encountered which was invalid.
srcloc shows the source location of the statement in error.
reason shows the reason for the WHEN statement being invalid.
System Action:
Compilation of the procedure fails.
User Action:
Correct the syntax of the WHEN statement and retry.
Reason:
During compilation of an OML procedure, an OTHERWISE statement was encountered which was not preceded by a WHEN statement.
srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
This could indicate incorrect DO/END pairing in the logic of the WHEN statement if the statements preceding the OTHERWISE statement contain a WHEN statement.
Reason:
During compilation of an OML procedure, nesting of DO or SELECT statements exceeded the limit of 250 levels. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Alter the logic of the procedure to avoid so many nested DO or SELECT statements.
Reason:
During compilation of an OML procedure, a DO statement was encountered which specified an unrecognised or duplicated keyword, or contained data after the DO expression. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Correct the syntax of the DO statement and retry.
Reason:
During compilation of an OML procedure, a DO statement was encountered which specified a control variable, but the variable is not acceptable. Complex, global and system variables cannot be used. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Choose a different control variable name.
Reason:
During compilation of an OML procedure, a GOTO or GOSUB statement was encountered which is invalid.
srcloc shows the source location of the statement in error.
verbname shows the name of the verb (GOTO or GOSUB).
reason shows the reason the statement is invalid.
System Action:
Compilation of the procedure fails.
User Action:
Correct the statement and retry.
Reason:
During compilation of an OML procedure, a RETSUB statement was encountered which is invalid.
srcloc shows the source location of the statement in error.
reason shows the reason the statement is invalid.
System Action:
Compilation of the procedure fails.
User Action:
Correct the statement and retry.
Reason:
During compilation of an OML procedure, a RETURN statement was encountered which is invalid.
srcloc shows the source location of the statement in error.
reason shows the reason the statement is invalid.
System Action:
Compilation of the procedure fails.
User Action:
Correct the statement and retry.
Reason:
During compilation of an OML procedure, an ON statement was encountered which specified a condition name which is not valid. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Correct the condition name and retry.
Reason:
During compilation of an OML procedure, a SIGNAL statement was encountered which specified a condition name which is not valid, or null. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Correct the condition name by removing invalid characters. If it was null, add the condition name to the statement.
Reason:
During compilation of an OML procedure, a REVERT statement was encountered which specified a condition name which is not valid. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Correct the condition name and retry.
Reason:
During compilation of an OML procedure, an END statement was encountered which specified a label name which is invalid.
srcloc shows the source location of the statement in error.
labelname shows the invalid label name.
System Action:
Compilation of the procedure fails.
User Action:
Correct the label name and retry.
Reason:
During compilation of an OML procedure, an END statement was encountered but no corresponding DO, PROCEDURE, or FUNCTION statement exists. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Remove the END statement or add the required DO, PROCEDURE, or FUNCTION statement.
Reason:
During compilation of an OML procedure, an END statement was encountered which specified a label name. The corresponding DO statement does not specify a label name or specifies a different label name. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Correct the label name on either the DO statement or END statement. This error can also indicate incorrect DO/END pairing in the logic of the DO statement.
Reason:
During compilation of an OML procedure, an END statement was encountered which specified a label name, but the corresponding PROCEDURE or FUNCTION statement specifies a different label name. srcloc shows the source location of the statement in error
System Action:
Compilation of the procedure fails.
User Action:
Correct the label name on either the PROCEDURE/FUNCTION statement or DO statement. This error can also indicate incorrect DO/END pairing in the procedure.
Reason:
During compilation of an OML procedure, a LEAVE or ITERATE statement was encountered which was not inside an iterative DO loop. LEAVE and ITERATE are only valid inside an iterative DO loop.
srcloc shows the source location of the statement in error.
verbname shows the verb name (LEAVE or ITERATE).
System Action:
Compilation of the procedure fails.
User Action:
Remove the LEAVE or ITERATE statement, or enclose it in an iterative DO loop.
Reason:
During compilation of an OML procedure, a LEAVE or ITERATE statement was encountered which specified a label name which is invalid.
srcloc shows the source location of the statement in error.
verbname shows the verb name (LEAVE or ITERATE).
System Action:
Compilation of the procedure fails.
User Action:
Correct the label name by removing invalid characters.
Reason:
During compilation of an OML procedure, a LEAVE or ITERATE statement was encountered which specified a label name which does not match the label name on any preceding iterative DO statement which encloses the LEAVE or ITERATE statement.
srcloc shows the source location of the statement in error.
verbname shows the verb name (LEAVE or ITERATE).
System Action:
Compilation of the procedure fails.
User Action:
Correct the label name on either the iterative DO statement or the LEAVE or ITERATE statement.
Reason:
During compilation of an OML procedure, a quoted label name was encountered which was null. This is invalid. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Correct the label name and retry.
Reason:
During compilation of an OML procedure or function, a verb was encountered which is not supported in the specified procedure type.
srcloc shows the source location of the statement in error.
proctype shows the type of procedure (PROCEDURE or FUNCTION).
System Action:
Compilation of the procedure fails.
User Action:
Remove the verb from the procedure/function.
Reason:
During compilation of an OML procedure a verb was found to have an option specified that is not supported by that verb.
srcloc shows the source location of the statement in error.
verbname shows the name of the verb.
option shows the option that was specified.
System Action:
Compilation of the procedure fails.
User Action:
Correct the option.
Reason:
During compilation of an OML procedure a verb was found to have an operand specified that is not supported by that verb.
srcloc shows the source location of the statement in error.
verbname shows the name of the verb.
operand shows the operand that was specified.
System Action:
Compilation of the procedure fails.
User Action:
Correct the operand.
Reason:
During compilation of an OML procedure a verb was found to have an operand specified which has a null value, but null is not a valid value for the operand.
srcloc shows the source location of the statement in error.
operand shows the operand which was specified.
verbname shows the name of the verb.
System Action:
Compilation of the procedure fails.
User Action:
Correct the operand.
Reason:
During compilation of an OML procedure a verb was found to have an operand specified which has a value which is not constant. The operand must be specified as a constant in the source.
srcloc shows the source location of the statement in error.
operand shows the operand which was specified.
verbname shows the name of the verb.
System Action:
Compilation of the procedure fails.
User Action:
Correct the operand.
Reason:
During compilation of an OML procedure a verb was found to have an operand specified which has a value which is not in the list of valid keywords for this operand.
srcloc shows the source location of the statement in error.
keyword shows the invalid keyword which was specified.
operand shows the operand which was specified.
verbname shows the name of the verb.
System Action:
Compilation of the procedure fails.
User Action:
Correct the keyword.
Reason:
During compilation of an OML procedure a verb was found to have an operand specified which has an unexpected value following the expected value for this operand. For example, end of statement was expected but more text was found.
srcloc shows the source location of the statement in error.
operand shows the operand which was specified.
verbname shows the name of the verb.
System Action:
Compilation of the procedure fails.
User Action:
Remove the extraneous data.
Reason:
During compilation of an OML procedure a verb was found to have an operand specified which has a variable list. The list has an opening parenthesis and no closing parenthesis.
srcloc shows the source location of the statement in error.
operand shows the operand which was specified.
verbname shows the name of the verb.
System Action:
Compilation of the procedure fails.
User Action:
Add a closing parenthesis to the variable list.
Reason:
During compilation of an OML procedure a verb was found to have an operand specified which has a null value, but a null value is invalid for this operand.
srcloc shows the source location of the statement in error.
operand shows the operand which was specified.
verbname shows the name of the verb.
System Action:
Compilation of the procedure fails.
User Action:
Add the operand value.
Reason:
During compilation of an OML procedure, a verb was found to have an operand specified which has a numeric range specified. The first number in the range is greater than the second number in the range.
srcloc shows the source location of the statement in error.
operand shows the operand which was specified.
verbname shows the name of the verb.
System Action:
Compilation of the procedure fails.
User Action:
Change the range so that the second number is greater than the first number.
Reason:
During compilation of an OML procedure, a verb was found to have an operand specified which has an invalid variable name.
srcloc shows the source location of the invalid variable name.
reason shows the reason that the variable name is invalid.
System Action:
Compilation of the procedure fails.
User Action:
Correct the invalid variable name.
Reason:
During compilation of an OML procedure, a verb was found to have an operand specified which should have a variable name but one has not been supplied, or the one supplied is invalid. srcloc shows the source location of the operand.
System Action:
Compilation of the procedure fails.
User Action:
Add the variable or correct the name.
Reason:
During compilation of an OML procedure, a verb was found to have an operand specified which allows a list of entries, but the number of entries in the list exceeds the number allowed for the operand.
srcloc shows the source location of the invalid statement.
operand shows the operand which was specified.
verbname shows the name of the verb
System Action:
Compilation of the procedure fails.
User Action:
Reduce the number of entries in the list.
Reason:
During compilation of an OML procedure, a verb was found to have an operand specified which supports a datatype which is not supported by the compiler.
srcloc shows the source location of the invalid statement.
operand shows the operand which was specified.
verbname shows the name of the verb.
System Action:
Compilation of the procedure fails.
User Action:
Contact your product support representative.
Reason:
During compilation of an OML procedure, a verb was found to have an operand specified that has a value which is either too long or too short.
srcloc shows the source location of the invalid statement.
operand shows the operand which was specified.
verbname shows the name of the verb.
System Action:
Compilation of the procedure fails.
User Action:
Correct the operand value.
Reason:
During compilation of an OML procedure, a verb was found to have an operand specified which has a numeric value which is either too low or too high.
srcloc shows the source location of the invalid statement.
operand shows the operand which was specified.
verbname shows the name of the verb.
System Action:
Compilation of the procedure fails.
User Action:
Correct the operand value.
Reason:
During compilation of an OML procedure, a verb was found to have an operand specified which is required to be a specific data type other than character, but it is not. For example, required type is integer but its value is not an integer.
srcloc shows the source location of the invalid statement.
operand shows the operand which was specified.
verbname shows the name of the verb.
datatype shows the required data type for the operand.
System Action:
Compilation of the procedure fails.
User Action:
Correct the operand value.
Reason:
During compilation of an OML procedure, a verb was found to have an operand specified that is required to be a specific character data type but it is not. For example, the name must be a PDS name but contains invalid characters.
srcloc shows the source location of the invalid statement.
operand shows the operand which was specified.
verbname shows the name of the verb.
datatype shows the required data type for the operand.
System Action:
Compilation of the procedure fails.
User Action:
Correct the operand value.
Reason:
During compilation of an OML procedure, a verb was found to have an operand specified which is required to be a specific data type but it is not that type.
srcloc shows the source location of the invalid statement.
operand shows the operand which was specified.
verbname shows the name of the verb.
System Action:
Compilation of the procedure fails.
User Action:
Correct the operand value.
Reason:
During compilation of an OML procedure, a verb was found to have an operand specified which is required to be a specific type of variable name but it is a different type of variable name. For example, an MDO name is required but the name supplied is not a valid MDO name.
srcloc shows the source location of the invalid statement.
varname shows the variable name which was specified.
operand shows the operand which was specified.
verbname shows the name of the verb.
System Action:
Compilation of the procedure fails.
User Action:
Change the variable name to one of the required type.
Reason:
During compilation of an OML procedure, a verb was found to have an operand specified more than once, when this is not allowed.
srcloc shows the source location of the invalid statement.
operand shows the operand which was specified.
verbname shows the name of the verb.
System Action:
Compilation of the procedure fails.
User Action:
Remove all but one of the operand occurrences.
Reason:
During compilation of an OML procedure, a verb was found to have an operand specified, which is not allowed to be specified due to the presence of an earlier operand.
srcloc shows the source location of the invalid statement.
operand shows the operand which was specified.
verbname shows the name of the verb.
System Action:
Compilation of the procedure fails.
User Action:
Determine which earlier operand is causing the problem and either remove it or remove the operand indicated in this message.
Reason:
During compilation of an OML procedure, a verb was found to have an operand specified which allows a list of keywords. The named keyword occurs more than once in the list, which is not allowed.
srcloc shows the source location of the invalid statement.
keyword shows the keyword which has been duplicated.
operand shows the operand which was specified.
verbname shows the name of the verb.
System Action:
Compilation of the procedure fails.
User Action:
Remove all but one of the occurrences of the keyword.
Reason:
During compilation of an OML procedure, a verb with invalid syntax was found.
srcloc shows the source location of the invalid statement.
verbname shows the name of the verb.
System Action:
Compilation of the procedure fails.
User Action:
Correct the syntax of the statement.
Reason:
During compilation of an OML procedure, a verb was found that did not have all of the required operands specified.
srcloc shows the source location of the invalid statement.
verbname shows the name of the verb.
System Action:
Compilation of the procedure fails.
User Action:
Add the required operands.
Reason:
During compilation of an OML procedure, a PROCEDURE or FUNCTION statement was encountered which specifies a name that has already been used within the current procedure or function.
srcloc shows the source location of the invalid statement.
proctype shows the procedure type (PROCEDURE or FUNCTION).
procname shows the name of the procedure or function.
System Action:
Compilation of the procedure fails.
User Action:
Change the name of the procedure or function to make it unique.
Reason:
During compilation of an OML procedure, a PROCEDURE or FUNCTION statement was encountered which specifies a name which has already been found within the current procedure or function.
srcloc shows the source location of the invalid statement.
proctype shows the procedure type (PROCEDURE or FUNCTION).
procname shows the name of the procedure or function.
System Action:
Compilation of the procedure fails.
User Action:
Change the name of the procedure or function to make it unique.
Reason:
During compilation of an OML procedure, a PROCEDURE or FUNCTION statement was encountered which specifies either a duplicate operand, or an operand which cannot be specified because of the presence of an earlier operand.
srcloc shows the source location of the invalid statement.
proctype shows the procedure type (PROCEDURE or FUNCTION).
operand shows the operand which is invalid.
System Action:
Compilation of the procedure fails.
User Action:
Change the operand.
Reason:
During compilation of an OML procedure, a PROCEDURE or FUNCTION statement was encountered that specifies a shared variable list which contains conflicting variable names. For example, &A* and &AB* are specified. &AB* is unnecessary because of the presence of &A*.
srcloc shows the source location of the invalid statement.
proctype shows the procedure type (PROCEDURE or FUNCTION).
var shows the variable which conflicts with an earlier variable.
System Action:
Compilation of the procedure fails.
User Action:
Remove one of the variable names from the list.
Reason:
During compilation of an OML procedure, a CLASS statement was found that specified a list of object classes from which this class can inherit. Either no class name has been specified, or a name specified is invalid or has been duplicated.
srcloc shows the source location of the invalid statement.
class shows the class name which is invalid.
System Action:
Compilation of the procedure fails.
User Action:
Either add the required class name(s) or correct the one which is named in this message. The class name must be a valid PDS name up to 8 chars.
Reason:
During compilation of an OML procedure, a CALL statement was found that specified an unrecognised operand.
srcloc shows the source location of the invalid statement.
operand shows the operand which is unrecognised.
System Action:
Compilation of the procedure fails.
User Action:
Correct or remove the operand.
Reason:
During compilation of an OML procedure, a CALL statement was found that specified an operand which is duplicated or is invalid because of the existence of a previous operand.
srcloc shows the source location of the invalid statement.
operand shows the operand which is invalid or duplicated.
System Action:
Compilation of the procedure fails.
User Action:
Correct or remove the operand.
Reason:
During compilation of an OML procedure, a CALL statement was found that specifies a shared variable list which contains conflicting variable names. For example, &A* and &AB* are specified,&AB* is unnecessary because of the presence of &A*.
srcloc shows the source location of the invalid statement.
proctype shows the procedure type (PROCEDURE or FUNCTION).
var shows the variable which conflicts with an earlier variable.
System Action:
Compilation of the procedure fails.
User Action:
Remove one of the variable names from the list.
Reason:
During compilation of an OML procedure, a CALL statement was found that specified SHARE or NOSHARE but has no shared variable list. When SHARE or NOSHARE is specified, either NO or a variable list must also be specified. srcloc shows the source location of the invalid statement.
System Action:
Compilation of the procedure fails.
User Action:
Following SHARE or NOSHARE, specify NO or a variable list.
Reason:
During compilation of an OML procedure, a CALL statement was found that specified SHARE or NOSHARE. The NO keyword was specified and also a variable list was specified. This is invalid. The NO keyword cannot be specified with a variable list. srcloc shows the source location of the invalid statement.
System Action:
Compilation of the procedure fails.
User Action:
Remove either the NO keyword or the variable list.
Reason:
During compilation of an OML procedure, a CALL statement was found that is invalid for the reason shown.
srcloc shows the source location of the invalid statement.
reason provides a description of the error:
The first symbol after 'CALL' is not PROC or PROCEDURE, and is not either a symbol, quoted string, or opening parenthesis (indicating an expression procedure name).
If the first symbol is 'PGM' or 'SUBSYS' this is also an error, as OML does not presently support calls to a user program or subsystem. (If you wish to call a procedure called 'PGM' or 'SUBSYS' then use 'CALL PROC(PGM)' or 'CALL PROC(SUBSYS)').
The syntax <CALL '' ...> or <CALL PROC('')> is not allowed, as a null string is not a valid procedure name.
The procedure name expression evaluated to a constant null value during compilation, and this is not a valid procedure name.
CALL supports a maximum of 32000 arguments.
Package notation (package:procedure) may not be specified when calling a program or subsystem.
System Action:
Compilation of the procedure fails.
User Action:
Correct the CALL statement.
Reason:
During compilation of an OML PARSE statement, an invalid source token was found. srcloc shows the source location of the error.
System Action:
Compilation of the procedure fails.
User Action:
Correct the syntax of the PARSE statement.
Reason:
During compilation of an OML PARSE statement, an option that is not supported by OML was found.
word shows the option. The REXX PARSE statement options of EXTERNAL, NUMERIC, PULL, SOURCE, and VERSION are not supported by OML.
srcloc shows the source location of the error.
System Action:
Compilation of the procedure fails.
User Action:
Correct the syntax of the PARSE statement.
Reason:
During compilation of an OML PARSE statement with the VALUE option, invalid syntax was detected after the expression. token shows the invalid syntax.
System Action:
Compilation of the procedure fails.
User Action:
Correct the syntax of the PARSE statement.
Reason:
During compilation of an OML PARSE or ARG statement with the VAR option, invalid syntax was detected where a variable name was expected. token shows the invalid syntax.
System Action:
Compilation of the procedure fails.
User Action:
Correct the syntax of the PARSE statement.
Reason:
During compilation of an OML PARSE or ARG statement, an error in the template was found.
srclc identifies the location in the source where the error was detected.
n is the error code:
1 - An unrecognizable template token was encountered.
2 - Following an equal sign (=), the next token was neither a left bracket '(' nor a valid symbol/number.
3 - Following a plus sign (+), the next token was neither a left parenthesis '(' nor a valid symbol/number.
4 - Following a plus sign (-), the next token was neither a left parenthesis '(' nor a valid symbol/number.
5 - Following an opening left parenthesis '(', the next token was not a variable name.
6 - Following a variable name, the next token was not a closing right parenthesis ')'.
7 - A number was expected at the indicated location. (The current token was a symbol but not a valid number.)
9 - A comma was encountered in a template, but the current statement is neither PARSE (UPPER) ARG nor ARG. A comma is valid only for PARSE ARG or ARG.
System Action:
Compilation of the procedure fails.
User Action:
Correct the syntax of the PARSE statement.
Reason:
During compilation of an OML PARSE or ARG statement, a template that had a system variable name was found.
srclc identifies the location in the source where the error was detected.
varname is the system variable name that was found.
PARSE (or ARG) cannot set an OML system variable, even if the system variable is normally assignable.
System Action:
Compilation of the procedure fails.
User Action:
Correct the syntax of the PARSE statement.
Reason:
During compilation of an OML procedure, an expression was found that contains a syntax error.
srcloc shows the source location of the invalid statement.
reason shows the reason why the expression syntax is incorrect.
System Action:
Compilation of the procedure fails.
User Action:
Correct the syntax of the expression.
Reason:
During compilation of an OML procedure, an expression was found that contains a constant section which could be evaluated during compilation but during evaluation an error occurred.
srcloc shows the source location of the invalid statement.
reason shows the reason that the evaluation failed.
System Action:
Compilation of the procedure fails.
User Action:
The expression results in processing which cannot be performed by OML. The action to take will be dependant on the reason given.
Reason:
During compilation of an OML procedure, an expression was found that contained a logical operation (for example, comparison of two numbers) with both arguments being constant. This message is sent as a warning because this usually indicates a programming error as the result will already be known, which means the code is redundant. srcloc shows the source location of the expression.
System Action:
Compilation of the procedure continues.
User Action:
Check the expression. If you want the expression to remain in this format, no action is required. This warning is only sent during compilation due to the OMLCHECK command.
Reason:
During compilation of an OML procedure, an expression was found that contains only constant values. The expression is used for a function which would normally not have a constant value (e.g. IF 'A' = 'B'..). This warning message is sent because this usually indicates a programming error as the result will already be known, meaning the code is redundant. srcloc shows the source location of the expression.
System Action:
Compilation of the procedure continues.
User Action:
Check the expression. If you want the expression to remain in this format, no action is required. This warning is only sent during compilation due to the OMLCHECK command.
Reason:
During compilation of an OML procedure, an expression was found that contained an invalid component. The component is invalid for the reason shown.
srcloc shows the source location of the expression.
term shows the component which is invalid.
reason shows the reason why the component is invalid.
System Action:
Compilation of the procedure fails.
User Action:
Correct the expression.
Reason:
This message was sent during compilation of an OML procedure for OMLCHECK LIST=YES. It contains the listing of the procedure.
linenum shows the line number in the file.
text shows the source text for this line.
System Action:
None.
User Action:
None.
Reason:
This message is sent during compilation of an OML procedure when a new %%INCLUDE file is being processed, if requested via OMLCHECK LIST=YES.
filename shows the source file name of the included file.
level shows the depth of %%INCLUDE processing for this file.
System Action:
None.
User Action:
None.
Reason:
This message is sent during compilation of an OML procedure when the end of a %%INCLUDE file is encountered, if requested via OMLCHECK LIST=YES.
filename shows the source file name of the included file.
level shows the depth of %%INCLUDE processing for this file.
System Action:
None.
User Action:
None.
Reason:
During compilation of an OML procedure, the resolution of a symbol that was defined by %%DEFINE has caused more than 256 substitution passes to try to resolve the final string. This is considered to be an error because either a recursive definition has been entered or the string is so complex the author has no chance of understanding what the final string will be.
srcloc shows the source file location of the statement in error.
symbol shows the current %%DEFINEd symbol being resolved.
System Action:
Compilation of the procedure fails.
User Action:
Correct the %%DEFINE definitions to avoid the recursive definition, or make the definitions easier to understand.
Reason:
During compilation of an OML procedure, a string defined by %%DEFINE has been resolved, but the resulting string is more than 255 bytes long. The maximum length allowed is 255.
srcloc shows the source location of the statement in error.
symbol shows the name of the symbol being resolved when the error occurred.
System Action:
Compilation of the procedure fails.
User Action:
Redefine the %%DEFINEs to make sure the final string length cannot be more than 255 bytes.
Reason:
During compilation of an OML procedure, a preprocessor statement (that is, a statement starting with %%, for example %%DEFINE) was found to have a comment which was not closed by */. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Add a closing */ to the comment.
Reason:
During compilation of an OML procedure, a preprocessor statement (that is, a statement starting with %%, for example %%DEFINE) was found to have invalid syntax. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Correct the statement.
Reason:
During compilation of an OML procedure, a preprocessor statement (that is, a statement starting with %%, for example %%DEFINE) was found to have unrecognised word.
srcloc shows the source location of the statement in error.
word shows the word which is not recognised.
System Action:
Compilation of the procedure fails.
User Action:
Correct the statement.
Reason:
During compilation of an OML procedure, a preprocessor statement (that is, a statement starting with %%, for example %%DEFINE) was found to have a quoted string which with no closing quote. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Add a closing quote to the string.
Reason:
During compilation of an OML procedure, a preprocessor statement (that is, a statement starting with %%, for example %%DEFINE) was found to have unpaired DBCS shift characters. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Ensure that DBCS shift characters are correctly paired.
Reason:
During compilation of an OML procedure, end-of-file (EOF) was encountered whilst concatenating lines that end with '\'.
System Action:
Compilation of the procedure fails.
User Action:
Remove any redundant '\' character from the end of the last source line.
Reason:
During compilation of an OML procedure, end-of-file (EOF) in an included file (%%INCLUDE) was encountered whilst concatenating lines that end with '\'.
System Action:
Compilation of the procedure fails.
User Action:
Remove any redundant '\' character from the end of the include file source line.
Reason:
During compilation of an OML procedure, a set of concatenated lines has exceeded the maximum allowable buffer length. This length is 4000 characters.
System Action:
Compilation of the procedure fails.
User Action:
reduce the number of consecutive concatenated lines.
Reason:
During compilation of an OML procedure, a set of concatenated lines has exceeded the maximum allowable number of lines. This limit is 100 lines.
System Action:
Compilation of the procedure fails.
User Action:
Reduce the number of consecutive concatenated lines.
Reason:
During compilation of an OML procedure, a %%DEFINE or %%UNDEFINE statement was found which did not specify the symbol to be DEFINEd or UNDEFINEd. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Add the string to the statement.
Reason:
During compilation of an OML procedure, a %%DEFINE or %%UNDEFINE statement specified a symbol which was either too long, contained invalid characters or was numeric.
srcloc shows the source location of the statement in error.
symbol shows the invalid symbol.
System Action:
Compilation of the procedure fails.
User Action:
Correct the symbol.
Reason:
During compilation of an OML procedure, a %%DEFINE statement specified a symbol which had already been defined using %%DEFINE.
srcloc shows the source location of the statement in error.
symbol shows the symbol.
System Action:
Compilation of the procedure fails.
User Action:
Check that the symbol names are correct. If so, insert a %%UNDEFINE statement before the statement in error.
Reason:
During compilation of an OML procedure, a %%DEFINE statement specified a replacement value which was too long.
The limit for a %%define replacement value is approximately 4000 characters.
srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Reduce the length of the %%DEFINE replacement text.
Reason:
During compilation of an OML procedure, a %%UNDEFINE statement was found that had data after the symbol to be %%UNDEFINEd. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Remove the data following the symbol name or enclose it in comment delimiters (/* comment */).
Reason:
During compilation of an OML procedure, a %%UNDEFINE statement was found that specified the name of a symbol which had not been %%DEFINEd.
srcloc shows the source location of the statement in error.
symbol shows the name of the symbol.
System Action:
Compilation of the procedure continues.
User Action:
This is a warning message that only appears during compilation for an OMLCHECK command. Check that the symbol name is correct, and if a corresponding %%DEFINE has been omitted. Remove the %%UNDEFINE statement if it is not required.
Reason:
During compilation of an OML procedure, a %%INCLUDE statement was found that has no include file name, or an invalid include file name. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
If the name has been omitted, add it to the statement. If it is present make sure it is a valid PDS name which is up to 8 characters in length.
Reason:
During compilation of an OML procedure, a %%INCLUDE statement was found that has data after the include file name. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Remove the data after the include file name or enclose it in comment delimiters (/* comment */).
Reason:
During compilation of an OML procedure, the number of %%INCLUDE statements found was more than 256. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Restructure the procedure to use 256 %%INCLUDEs or less.
Reason:
During compilation of an OML procedure, the specified %%INCLUDE file could not be opened.
srcloc shows the source location of the statement in error.
filename shows the name of the file.
System Action:
Compilation of the procedure fails.
User Action:
Check that the name of the procedure is spelt correctly (this error could indicate a non- existent file was specified). Check the library concatenation used by your userID to ensure the required library is present.
Reason:
During compilation of an OML procedure, more than one %%PTF statement was found. This statement is used to record the maintenance level of a procedure. There can only be one maintenance level, therefore only one %%PTF statement is allowed per procedure. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Remove the unnecessary %%PTF statement(s).
Reason:
During compilation of an OML procedure, a %%PTF statement was found which specified an invalid PTF name. The name must be a PDS name up to 8 characters in length. srcloc shows the source location of the statement in error.
System Action:
Compilation of the procedure fails.
User Action:
Correct the PTF name.
Reason:
During compilation of an OML procedure, an invalid token was found, the reason is shown.
srcloc shows the source location of the token.
reason shows the reason why the token is invalid.
System Action:
Compilation of the procedure fails.
User Action:
Correct the token to make it valid.
Reason:
During compilation of an OML procedure, a quoted string was found which starts and ends on different lines. This warning message is sent to warn of the possibility that this is an accident. This message is only produced if the compilation is for an OMLCHECK command. srcloc shows the source location of the quoted string.
System Action:
Compilation of the procedure continues.
User Action:
Check if this is deliberate. If so, no further action is required.
Reason:
During compilation of an OML procedure, an abend occurred while the named file was being read.
System Action:
Compilation of the procedure is aborted immediately.
User Action:
Investigate the reason for the abend.
Reason:
During compilation of an OML procedure, an I/O error occurred while the named file was being read.
System Action:
Compilation of the procedure is aborted immediately.
User Action:
Investigate the reason for the I/O error.
Reason:
During compilation of an OML procedure a GOTO or GOSUB statement was found to be invalid for the reason shown.
srcloc shows the source location of the statement in error.
reason shows the reason that the statement is invalid.
System Action:
Compilation of the procedure fails.
User Action:
Correct the GOTO or GOSUB statement.
Reason:
During compilation of an OML procedure, a CALL statement was found to be invalid for the reason shown.
srcloc shows the source location of the statement in error.
reason shows the reason why the statement is invalid.
System Action:
Compilation of the procedure fails.
User Action:
Correct the CALL statement.
Reason:
During compilation of an OML procedure, a SIGNAL statement was found to be invalid. The reason is shown.
srcloc shows the source location of the statement in error.
reason shows the reason why the statement is invalid.
System Action:
Compilation of the procedure fails.
User Action:
Correct the SIGNAL statement.
Reason:
During compilation of an OML procedure, a function call was found but the target name is actually the name of a PROCEDURE. The target of a function call must be a FUNCTION.
srcloc shows the source location of the statement in error.
funcname shows the name of the target function.
System Action:
Compilation of the procedure fails.
User Action:
Correct the function name or change the target procedure to that of a function.
Reason:
During compilation of an OML procedure, a function call was found. The target name was not found in the source file, and is not a valid PDS name and as such is invalid.
srcloc shows the source location of the statement in error.
funcname shows the name of the target function.
System Action:
Compilation of the procedure fails.
User Action:
Correct the function name.
Reason:
During compilation of an OML procedure, a built-in function call was found. The number of arguments specified is more than 32000.
srcloc shows the source location of the statement in error.
funcname shows the name of the target function.
System Action:
Compilation of the procedure fails.
User Action:
Reduce the number of arguments on the call.
Reason:
During compilation of an OML procedure, a built-in function call was found. The named argument is invalid.
srcloc shows the source location of the statement in error.
argnum shows the argument number of the invalid argument.
funcname shows the name of the target function.
System Action:
Compilation of the procedure fails.
User Action:
Correct the argument.
Reason:
During compilation of an OML procedure, a built-in function call was found. The specified argument is null. This is not allowed.
srcloc shows the source location of the statement in error.
argnum shows the argument number of the invalid argument.
funcname shows the name of the target function.
System Action:
Compilation of the procedure fails.
User Action:
Correct the argument.
Reason:
An OML object load failed. The reason code provides a precise indication of the error.
Some of the error codes are:
001 to 011 - Invalid object header records (generally meaning that the object has been edited or file transferred with ASCII conversion, and so on).
012 - Object version mismatch. This object was compiled on an incompatible version of Management Services.
013 to 029 - See 001 through 011.
040 or 042 - Invalid record sentinel. The code could indicate that the object has been ASCII/EBCDIC translated.
501 - Storage shortage.
606 - See 012.
802 or 803 - Invalid checksum, indicating possible file transfer with ASCII translation, or tampering or editing of the object.
804 - Unexpected end-of-file condition.
805 - I/O abend.
806 - Unrecoverable I/O error.
807 - Not EOF when expected.
808 - Unrecoverable I/O error or abend.
810 - Invalid record sentinel. The code could indicate that the object has been ASCII/EBCDIC translated.
All other error codes indicate internal failures or errors.
System Action:
The object load fails.
User Action:
Examine the error code, and take the corrective action if possible.
Reason:
An OML object load failed. A problem was encountered while resolving a system variable.
System Action:
The object load fails.
User Action:
Examine the error description and take corrective action if possible.
Reason:
An OML object load failed. A problem was encountered while resolving a built-in function.
System Action:
The object load fails.
User Action:
Examine the error description and take corrective action if possible.
Reason:
An OML object load failed. A problem was encountered while resolving a verb.
System Action:
The object load fails.
User Action:
Examine the error description and take corrective action if possible.
Reason:
An OML object load failed. A problem was encountered while resolving a verb argument (operand).
System Action:
The object load fails.
User Action:
Examine the error description and take corrective action if possible.
Reason:
An OML object load failed. A problem was encountered while resolving a verb argument (operand) keyword.
System Action:
The object load fails.
User Action:
Examine the error description and take corrective action if possible.
Reason:
This is a warning message. During object loading, an unrecognised system variable name was found. If the statement(s) referencing it are executed, an error will occur.
System Action:
The object load continues.
User Action:
Ensure that this will not cause a runtime problem.
Reason:
This is a warning message. During object loading, an unrecognised built-in function name was found. If the statement(s) referencing it are executed, an error will occur.
System Action:
The object load continues.
User Action:
Ensure that this will not cause a runtime problem.
Reason:
This is a warning message. During object loading, an unrecognised verb name was found. If the statement(s) referencing it are executed, an error will occur.
System Action:
The object load continues.
User Action:
Ensure that this will not cause a runtime problem.
Reason:
An OML object reload failed due to a storage shortage.
System Action:
The object load fails.
User Action:
Investigate the storage shortage.
Reason:
The OML compiler has encountered a fatal storage shortage.
System Action:
The compile fails.
User Action:
Investigate the storage shortage.
Reason:
The OML compiler has detected errors or warnings while compiling a procedure. This message precedes the actual error messages.
System Action:
The compile error and warning messages follow.
User Action:
Examine the messages and take appropriate action.
Reason:
The OML compiler has encountered a fatal storage shortage.
System Action:
The compile fails.
User Action:
Investigate the storage shortage.
Reason:
The system I/O manager, used to load NCL procedures, has initialized successfully.
System Action:
None.
User Action:
None.
Reason:
This message indicates an unexpected subtask abend by a system I/O subtask.
System Action:
An attempt is made to restart the subtask.
User Action:
Determine the reason for the abend from the operating system log. Contact your product support representative.
Reason:
An I/O error was encountered whilst loading the indicated NCL procedure. I/O error information, as obtained by the SYNADAF function is displayed.
System Action:
The system will retry the load, if possible.
User Action:
None, unless the problem persists. If it does, investigate the problem.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|