|
|
|
Reason:
The named OML procedure was flushed before execution, as the region was terminated, for example, due to user logoff.
System Action:
None.
User Action:
None.
Reason:
The named OML procedure was not executed for the given reason.
System Action:
The procedure is not executed.
User Action:
Correct the problem and resubmit the procedure for execution if required.
Reason:
Data supplied for a verb operand was not of the indicated type.
System Action:
An error is raised.
User Action:
Correct the supplied data.
Reason:
An OML compiled procedure attempted to execute the named verb, The named verb is not known in this SOLVE system. This error can only occur for an OML procedure loaded from object code, not source code.
System Action:
An error is raised.
User Action:
Check to see if the INCLUDE/EXCLUDE JCL parms or licence have disabled a required feature.
Reason:
The indicated argument to the named built-in function is not a valid value.
System Action:
An error is raised.
User Action:
Correct the input value.
Reason:
An attempt to call the named external function failed. The external function could not be found in the procedure library.
System Action:
An error is raised.
User Action:
Check the spelling of the function name. If correct, ensure that the function code is in the procedure library.
Reason:
An attempt to load or compile the indicated function or package failed.
System Action:
An error is raised.
User Action:
Check the error messages for the compilation failure reason. Correct the problem and execute the procedure again.
Reason:
After loading the named file, it was not of the required type (function or package).
System Action:
An error is raised.
User Action:
Ensure that the name of the requested function or package is correct.
Reason:
An attempt was mode to perform a function call to an NCL procedure. NCL does not support user written functions.
System Action:
An error is raised.
User Action:
Check the requested function name.
Reason:
The named package does not contain a first-level function of the indicated name.
System Action:
An error is raised.
User Action:
Check the requested function name.
Reason:
The named package contains a first-level procedure of the indicated name, however a FUNCTION was requested. A non-function (such as PROCEDURE) cannot be executed by a function call.
System Action:
An error is raised.
User Action:
Check the requested function name.
Reason:
A compiled OML procedure attemped to execute the named builtin function. However, the named function is not known in this SOLVE system. This error can only occur for an OML procedure loaded from object code, not source code.
System Action:
An error is raised.
User Action:
Check to see if the INCLUDE/EXCLUDE JCL parms or licence have disabled a required feature.
Reason:
An attempt to call the named external procedure failed. The external procedure could not be found in the procedure library.
System Action:
An error is raised.
User Action:
Check the spelling of the procedure name. If correct, ensure that the procedure code is in the procedure library.
Reason:
An attempt to load or compile the named procedure or package failed.
System Action:
An error is raised.
User Action:
Check the error messages for the reason that the compilation failed. Correct the problem and execute the procedure again.
Reason:
The named file was loaded. It was not of the required type (procedure or package).
System Action:
An error is raised.
User Action:
Check the name of the requested procedure or package.
Reason:
The named package does not contain a first-level procedure with the indicated name.
System Action:
An error is raised.
User Action:
Check the name of the requested procedure.
Reason:
The named package contains a first-level function of the indicated name, however a PROCEDURE was requested. A non-procedure (such as FUNCTION) cannot be executed by a procedure call.
System Action:
An error is raised.
User Action:
Check that the name of the requested procedure is correct.
Reason:
This is a trace message for OML procedures. It traces labels.
System Action:
None.
User Action:
None.
Reason:
This is a trace message for OML procedures. It traces OML statements.
System Action:
None.
User Action:
None.
Reason:
This is a trace message for OML procedures. It traces the entry into new OML procedures or functions.
System Action:
None.
User Action:
None.
Reason:
This is a trace message for OML procedures. It traces OML expression processing.
The values for expression type are:
The expression source is displayed
A literal value has been pushed
A variable value has been pushed
The result of a binary operator has been pushed
The result of a prefix (unary) operator has been pushed
A function result has been pushed
This is the expression final result
If the 'value' is a null character string then is is represented by the string '<NULL>'
System Action:
None.
User Action:
None.
Reason:
This message provides a short description of an OML execution error.
System Action:
An error has been raised.
User Action:
Examine the message for the error reason and take appropriate corrective action.
Reason:
This message is used as the OML error description when no other message is available.
System Action:
An error has been raised.
User Action:
Use the error code and error location to determine the cause of the error.
Reason:
This message is produced when an OML process terminates.
System Action:
None.
User Action:
None.
Reason:
This message is produced when an OML process is flushed.
System Action:
None.
User Action:
None.
Reason:
This message is produced when an OML system procedure terminates in error.
System Action:
None.
User Action:
None.
Reason:
This message is produced when an OML procedure terminates in error. The NCLID (aaaaaa), file (bbbbbbbb), line (cccccccc), error code (ddd), and error condition (eeee) are displayed.
System Action:
None.
User Action:
None.
Reason:
This message is produced when an OML procedure terminates in error. Error information messages follow.
System Action:
None.
User Action:
None.
Reason:
This message is produced when an OML procedure terminates in error. An execution stack traceback follows.
System Action:
None.
User Action:
None.
Reason:
This message is part of the OML execution traceback. It shows the procedure type and name, source file, line, column and decompiled statement in error.
System Action:
None.
User Action:
None.
Reason:
This message is part of the OML execution traceback. It indicates that an ON-block was in the execution stack and the information that follows is derived from it.
System Action:
None.
User Action:
None.
Reason:
This message is part of the OML execution traceback. It indicates that a GOSUB statement was in the execution stack. A dump of the GOSUB statement is displayed.
System Action:
None.
User Action:
None.
Reason:
This message is part of the OML execution traceback. It indicates that a call from another procedure (which could be a function call) was found. The following information is about the calling procedure.
System Action:
None.
User Action:
None.
Reason:
This message is part of the OML execution traceback. It show the error code that raised an ON-BLOCK or terminated the procedure.
System Action:
None.
User Action:
None.
Reason:
This message is part of the OML execution traceback. It shows any available error message from the error that raised an ON-BLOCK or terminated the procedure.
System Action:
None.
User Action:
None.
Reason:
This message is part of the OML execution traceback. It shows the condition name from the error that raised an ON-BLOCK or terminated the procedure.
System Action:
None.
User Action:
None.
Reason:
This message is part of the OML execution traceback. It shows the location of the error that raised an ON-BLOCK or terminated the procedure.
System Action:
None.
User Action:
None.
Reason:
This message is part of the OML execution traceback. It shows the type and name of the procedure that had the error.
System Action:
None.
User Action:
None.
Reason:
This message is part of the OML execution traceback. It shows the source of the statement in error.
System Action:
None.
User Action:
None.
Reason:
This message is part of the OML execution traceback. It shows the verb keyword that caused the error.
System Action:
None.
User Action:
None.
Reason:
This message is part of the OML execution traceback. It shows the value that was in error.
System Action:
None.
User Action:
None.
Reason:
This message is part of the OML execution traceback. It shows the second value, if available, that was in error.
System Action:
None.
User Action:
None.
Reason:
This message is part of the OML execution traceback. It shows the source variable name, if available, that was in error.
System Action:
None.
User Action:
None.
Reason:
This message is part of the OML execution traceback. It shows the target variable name (after resolution, if available) that was in error.
System Action:
None.
User Action:
None.
Reason:
The OML procedure bbbbbbb set a return code aaa indicating that update of it's target object instance was to be ignored. Execution of the system method routine is bypassed and the object instance is not updated in the repository.
System Action:
The message is returned to the client in the reply SDU.
User Action:
None.
Reason:
The Object Services generated reply to the client failed.
System Action:
The message is logged.
User Action:
Check the activity log for possible causes.
Reason:
An Object Services request could not be processed due to insufficient virtual storage.
System Action:
The request is terminated.
User Action:
Look for possible causes of high storage utilisation. Increase virtual storage address space size.
Reason:
Object Services could not initialize the aaaaaa method for an object request. This usually indicates a problem with building the Mapped Data Objects (MDOs) or may indicate a resource shortage.
System Action:
The method is not executed.
User Action:
Check the object maps are valid. Check the activity log for additional messages.
Reason:
This message indicates that a variable name which was encountered during execution of an OML process is invalid. The text following the colon shows the reason why the variable name is invalid.
System Action:
An error is raised. If no relevant ON-BLOCK exists, the OML process is terminated.
User Action:
Correct the invalid variable name.
Reason:
This message indicates that the name passed for an MDO variable does not constitute a valid name for an MDO. This can be because the name contains invalid characters, or contains a name segment which is longer than 32 bytes.
System Action:
An error is raised. If no relevant ON-BLOCK exists, the OML process is terminated.
User Action:
Correct the MDO variable name.
Reason:
An attempt was made to assign data to an MDO variable, but the assignment was rejected by Mapping Services.
p1 is the return code,
p2 is the feedback code from the MDO assignment.
System Action:
An error is raised. If no relevant ON-BLOCK exists, the OML process is terminated.
User Action:
For an explanation of the return and feedback codes, see the NCL Reference Guide. See system variables &ZMDORC and &ZMDOFDBK.
For programmers, to find out the reason for the rejection, change the statement to use the ASSIGN verb with CONTROL MDOCHK in effect. This change will cause more error information to be produced.
Reason:
OML supports returning the value of many NCL system variables during substitution, for a PANEL or certain built-in functions. This error indicates that the variable being accessed is recognised as an NCL system variable, but is not one which OML supports.
System Action:
An error is raised. If no relevant ON-BLOCK exists, the OML process is terminated.
User Action:
Change the variable name to use the correct OML system variable name.
Reason:
This message is produced during processing of a DEBUG DISPLAY command. It shows the name of a variable which is included in the display. This message is followed by further messages which show the data for the variable.
System Action:
None.
User Action:
None.
Reason:
This message is produced during processing of a DEBUG DISPLAY command. It shows the length of data contained in a variable (aaaaaaaa), the MODFLD number for the variable (bbbbbb), and attributes for the variable (ccc). The attribute value can contain the following values:
M - the variable is flagged as being modified (e.g. ASSIGN OPT=SETMOD)
E - the variable is flagged as being in error (e.g. ASSIGN OPT=SETERR)
O - the variable is flagged as being output (e.g. ASSIGN OPT=SETOUT)
System Action:
None.
User Action:
None.
Reason:
This message is produced during processing of a DEBUG DISPLAY command. It shows the data assigned to a variable. The data will be in the format designated by the FMT= operand on the DEBUG DISPLAY command. If FMT=CHAR is specified, the data is in character format and may be up to 256 bytes long. If FMT=HEX is specified, the data can be up to 256 bytes long (which is 128 bytes of the data in hex-expanded format). If FMT=DUMP is specified, a dump of the variable data follows, with message number NM4020.
System Action:
None.
User Action:
None.
Reason:
This message is produced during processing of a DEBUG DISPLAY command. It shows the data assigned to a variable in hex dump format. ooo is the offset (in hexadecimal) in the variable, xxxxxxxx is the variable data in hex format, and cccccccc is the variable data in character format.
System Action:
None.
User Action:
None.
Reason:
An ASSIGN verb has specified the RANGE= operand with an MDO assignment, but the MDO name supplied does not support the RANGE= operand. The MDO name must be a variable indexed name (e.g. MDO=A.B.C{*} )
System Action:
An error is raised. If no relevant ON-BLOCK exists, the OML process is terminated.
User Action:
Correct the MDO name or remove the RANGE= operand.
Reason:
An ASSIGN verb has specified an MDO to MDO assignment, and one of the MDO names is variable indexed but the other is not. This is invalid. If a variable indexed name is specified, both names must be variable indexed.
System Action:
An error is raised. If no relevant ON-BLOCK exists, the OML process is terminated.
User Action:
Correct the MDO names and retry.
Reason:
An ASSIGN verb has specified the NOVALIDATE option on an assignment into an MDO variable, but the MDO name is variable indexed, which is invalid.
System Action:
An error is raised. If no relevant ON-BLOCK exists, the OML process is terminated.
User Action:
Correct the MDO name or remove the NOVALIDATE option and retry.
Reason:
An OML procedure has attempted to execute a MSGREAD, MSGCONT or MSGDEL verb, but the procedure is not executing as a MSGPROC. These verbs are only valid from a MSGPROC procedure.
System Action:
An error is raised. If no relevant ON-BLOCK exists, the procedure is terminated.
User Action:
Either remove the MSGREAD, MSGCONT or MSGDEL verb, or start the procedure as a MSGPROC using a PROFILE MSGPROC=procname command or defining the procedure as MSGPROC in the users UAMS definition.
Reason:
An OML procedure has attempted to execute a MSGREAD, or MSGCONT verb but the update of the $MSG MDO has failed. The message shows the return code (aa) and feedback (bb) values returned from Mapping Services which describe the error.
System Action:
An error is raised. If no relevant ON-BLOCK exists, the procedure is terminated.
User Action:
Investigate the reason for the failure using the return code and feedback values.
Reason:
The &$INT. MDO name cannot be used as the target of an INTREAD MDO= operation.
System Action:
The verb signals an error.
User Action:
Change the INTREAD statement to use some other MDO name.
Reason:
An INTCONT statement was issued when no message was available from an INTREAD statement.
System Action:
The verb signals an error.
User Action:
Check the procedure logic.
Reason:
A PANEL statement was executed in an environment that does not support full-screen panels (for example, BSYS).
System Action:
The verb signals an error.
User Action:
Check the procedure logic.
Reason:
A VARTABLE statement FIELDS or VARS list keywords error was detected. The reason for the error follows the dash (-).
System Action:
The verb signals an error.
User Action:
Correct the VARTABLE verb operands.
Reason:
A VARTABLE statement attempted to access or update an entry that contains an MDO, using relative field access.
System Action:
The verb signals an error.
User Action:
Correct the VARTABLE verb operands.
Reason:
Source data for a VARTABLE statement exceeds the maximum length that can be stored in an entry.
System Action:
The verb signals an error.
User Action:
Correct the VARTABLE verb operands.
Reason:
The limit on the number of locks for a process has been reached.
System Action:
The lock request is not honored.
User Action:
Determine the number of currently active LOCKs using the SHOW LOCKS command and determine if the number of requests is excessive.
The default is 32767 locks per executing region.
Reason:
An OML procedure has executed a PPI SEND or PPI ALERT verb with the VARS= operand specified. The total amount of data from the specified variables exceeds the maximum supported size.
System Action:
An error is raised. If no relevant ON Block exists the procedure is terminated.
User Action:
Reduce the amount of data to be sent.
Reason:
An OML procedure has executed a PPI RECEIVE verb with the MDO= operand specified. During assignment of the data to the MDO, Mapping Services encountered an error.
System Action:
An error is raised. If no relevant ON Block exists the procedure is terminated.
User Action:
Correct the mapping of the MDO.
Reason:
An OML procedure has executed a PPI RECEIVE verb to receive data via a PPI connection. The procedure currently has no connection to PPI.
System Action:
An error is raised. If no relevant ON Block exists the procedure is terminated.
User Action:
Ensure that a PPI DEFINE has been issued. If so, check that the return code from the PPI define indicated that the operation was successful.
Reason:
A LOGREAD, LOGDEL, or LOGCONT statement was issued from an NCL process other than LOGPROC.
System Action:
The verb signals an error.
User Action:
These statements are not valid unless used in the LOGPROC procedure. Check that SYSPARMS LOGPROC=xxxx was used to start the procedure.
Reason:
An OML procedure has attempted to execute a LOGREAD, or LOGCONT verb but the update of the $MSG MDO has failed. The message shows the return code (aa) and feedback (bb) values returned from Mapping Services which describe the error.
System Action:
An error is raised. If no relevant ON-BLOCK exists, the procedure is terminated.
User Action:
Investigate the reason for the failure using the return code and feedback values.
Reason:
The MDO supplied to an ENCODE or DECODE statement is invalid.
System Action:
None.
User Action:
Ensure that different source and target MDOs are used. Check the syntax of the MDO names and verify them against their respective MAP definitions.
Reason:
An internal MDS error has occurred.
System Action:
None.
User Action:
Contact your product support representative.
Reason:
The internal recursion stack limit was exceeded while processing an ENCODE or DECODE operation, possibly caused by too many segments in a compound name.
System Action:
None.
User Action:
Reduce number of name segments in mdo name. May require redefinition of the map.
Reason:
An ENCODE or DECODE statement has invalid syntax.
System Action:
None.
User Action:
Correct the statement and retry.
Reason:
The TRANSLATE= operand supplied to an ENCODE or DECODE statement is invalid.
System Action:
None.
User Action:
Check supported TRANSLATE operands, e.g. ISO, DEC, ASCII...
Reason:
The encoded string cannot be assigned to the target MDO of an ENCODE statement, possibly due to its defined type.
System Action:
None.
User Action:
Check the type definition of the target MDO and rectify as appropriate.
Reason:
The procedure has abended on an ENCODE or DECODE verb because an MDO was invalidly mapped because of one of the following:
. the map was not found on the mapping services database . it failed to load . it did not successfully attach to the MDO because it mismatched the data in the MDO.
System Action:
Procedure is flushed.
User Action:
Ensure map exists, loads and correctly maps the underlying MDO data.
Reason:
The specified target mdo contains invalid data.
System Action:
None.
User Action:
Delete the invalid component, or use a new MDO.
Reason:
An ENCODE or DECODE statement specified operands that indicate that ATF is to be used. However ATF is not available or is not licensed on this SOLVE system.
System Action:
An error is indicated.
User Action:
Check your SOLVE licence for ATF support.
Reason:
An ENCODE or DECODE statement has a SRC_CHARSET operand that names a character set that is not recognised by ATF.
System Action:
An error is indicated.
User Action:
Check the character set name.
Reason:
An ENCODE or DECODE statement has a TGT_CHARSET operand that names a character set that is not recognised by ATF.
System Action:
An error is indicated.
User Action:
Check the character set name.
Reason:
A SECCALL EXIT verb has been executed but the SOLVE system does not have a security exit to call.
System Action:
An error is raised. If no relevant ON-BLOCK exists, the OML process is terminated.
User Action:
If the SOLVE system should have a security exit, investigate why it is not active.
Reason:
A SECCALL EXIT verb has been executed but one of the parameters to be passed is too long. The maximum length of any single parameter is 256 bytes.
System Action:
An error is raised. If no relevant ON-BLOCK exists, the OML process is terminated.
User Action:
Investigate why the parameter is too long.
Reason:
The input mask to the EDIT built-in function is not valid. The exact reason follows the colon.
System Action:
The function signals an error.
User Action:
Correct the EDIT function operands.
Reason:
The number supplied to the EDIT built-in function was too large for the number of integer positions in the edit mask.
System Action:
The function signals an error.
User Action:
Check and correct the edit mask or number.
Reason:
The indicated parameter number (n) to the STCKFIX function is not valid.
System Action:
The function signals an error.
User Action:
Correct the indicated function operand.
Reason:
The indicated parameter number (n) (name also shown) requires a following value parameter.
System Action:
The function signals an error.
User Action:
Correct the indicated function operand.
Reason:
The indicated parameter number (n) (name of preceding parameter also shown) must be data of one of the following types:
s is +, -, E (meaning +), or W (meaning -)
hh is an hours value from 00 to 15
mm is a minutes value from 00 to 59
(maximum allowed is 1500).
System Action:
The function signals an error.
User Action:
Correct the indicated function operand.
Reason:
The input value to the STCKGEN function must be a date/time in one of the following formats:
yyyymmddhhmmss.ffffff
The value can be shortened, as long as it has at least the date (yyyymmdd).
unsigned packed decimal bytes, exactly 10 bytes long, in the format:
x'yyyymmddhhmmssffffff'
This is the same as the return format from the STCKFMT function when the P option is used.
The value must be in the following range:
19000101000000.000000 to 20420917235347.370495
This is the defined range for a STCK value from x'0000000000000000' to x'ffffffffffffffff'.
System Action:
The function signals an error.
User Action:
Correct the indicated function operand.
Reason:
An OML SELSTR or REMSTR builtin function is being processed with CONTROL DBCS in effect and SYSPARMS DBCS=YES. The delimeter character supplied is not a single SBCS character and is not a single DBCS character enclosed by shift out and shift in.
System Action:
An error is raised.
User Action:
Check why the character was not a valid SBCS or DBCS character.
Reason:
The indicated parameter number ('p') to the named Date-related function is not valid.
System Action:
The function signals an error.
User Action:
Correct the indicated function operand.
Reason:
An OML JCLXOPT built-in function was called, but the specified name of the JCL XOPT option is not in the name table of the function.
System Action:
An error is raised.
User Action:
Check the name of the specified option.
Reason:
The PLEXSUB OML builtin function can only be used if the operating system is OS/390 or later (such as z/OS).
System Action:
The function signals an error.
User Action:
Do not use the PLEXSUB function in this environment.
Reason:
The PLEXSUB OML builtin function could not load the MVS substitution service module, ASASYMBM.
System Action:
The function signals an error.
User Action:
Investigate why the ASASYMBM module is not accessible.
Reason:
The PLEXSUB OML builtin function requires user variable names to be 1 to 16 characters long (not including the &), and the first character must be alpha or national, the remainder being alpha, numeric, or national.
System Action:
The function signals an error.
User Action:
Correct the user variable name.
Reason:
The PLEXSUB OML builtin function requires user variable values to be no longer than the variable name including the leading &. (This is an MVS substitution service restriction).
System Action:
The function signals an error.
User Action:
Correct the user variable value. If a longer value is required, use a longer name.
Reason:
The PLEXSUB OML builtin function received a non-zero return code from the ASASYMBM MVS substution service module.
System Action:
The function signals an error.
User Action:
Contact your support representative. Non-zero return codes should not occur.
Reason:
The ASASYMBM MVS substitution service module ABENDed whilst processing a request for the PLEXSUB function.
System Action:
The function signals an error.
User Action:
Contact your support representative. An ABEND should not occur.
Reason:
The MIN and MAX operands of the RANDOM built-in function have a difference that is less than 1 or greater than 100000.
System Action:
The function signals an error.
User Action:
Correct the RANDOM function operands.
Reason:
An OML REMSTR builtin function has detected that the delimeter character supplied was not a single byte character.
System Action:
An error is raised.
User Action:
Check why the character was not a single byte character. The only situation in which the character can be longer is if CONTROL DBCS is in effect on a SOLVE system with SYSPARMS DBCS=YES, and the character is a single DBCS character enclosed by shift out and shift in.
Reason:
An OML SELSTR builtin function has detected that the delimiter character supplied was not a single byte character.
System Action:
An error is raised.
User Action:
Check why the character was not a single byte character. The only situation in which the character can be longer is if CONTROL DBCS is in effect on a SOLVE system with SYSPARMS DBCS=YES, and the character is a single DBCS character enclosed by shift out and shift in.
Reason:
An attempt has been made to share a variable or MDO from OML to NCL but the name is too long to be valid in NCL. The maximum name length for a variable is 12. The maximum name length for an MDO is 12 excluding the period.
System Action:
An error is raised. If no relevant ON-BLOCK exists, the OML procedure is terminated.
User Action:
Change the name of the variable or avoid sharing it to NCL.
Reason:
An attempt has been made to share a variable or MDO from OML to NCL but the name is not valid in NCL.
System Action:
An error is raised. If no relevant ON-BLOCK exists, the OML procedure is terminated.
User Action:
Change the name of the variable or avoid sharing it to NCL.
Reason:
An attempt has been made to share a variable from OML to NCL but the data contained in the variable is more than 256 bytes in length. This amount of data is not supported by NCL, so the request has been rejected.
System Action:
An error is raised. If no relevant ON-BLOCK exists, the OML procedure is terminated.
User Action:
Consider why the variable is being shared to NCL and why the variable has more than 256 bytes of data. If required, add logic to the OML procedure to limit the amount of data in the variable to 256 bytes.
| Copyright © 2012 CA. All rights reserved. |
|