Kednos PL/I for OpenVMS Systems
User Manual
NOCNDVAL, A value is required with the entity
condition.
Error: The ENDFILE, ENDPAGE, KEY, UNDEFINEDFILE, or
VAXCONDITION condition name is specified without a value.
User Action: Specify a value for the condition.
NODATATYP, Entity is declared without a data type. The
default data type FIXED BINARY has been supplied.
Warning: The indicated name has been declared, but is
declared without a data type attribute. The compiler provides the
default data type of FIXED BINARY.
User Action: If you want the variable to have the
default data type, you need do nothing. Otherwise, correct the
declaration of the variable so that it has a data type attribute.
NODFLOAT, The CDD description for structure item entity
specifies the D_Floating data type. The data cannot be represented when
compiled with /G_FLOAT.
Warning: The wrong PLI command qualifier was used to
compile the program.
User Action: Ignore the warning message or recompile
the program using the /NOG_FLOAT qualifier.
NODIM, Entity is an entry or file constant and cannot be
declared with a dimension.
Error: The ENTRY or FILE attribute was specified for
an array, but the VARIABLE attribute is not specified.
User Action: Specify the VARIABLE attribute to create
an array of file or entry variables.
NOGFLOAT, The CDD description for structure item entity
specifies the G_Floating data type. The data cannot be represented when
compiled with /NOG_FLOAT.
Warning: The wrong PLI command qualifier was used to
compile the program.
User Action: Ignore the warning message or recompile
the program using the /G_FLOAT qualifier.
NOHFLOAT, The CDD description for structure item entity
specifies the H_Floating data type. The data cannot be represented when
compiled with /NOG_FLOAT.
Warning: The wrong PLI command qualifier was used to
compile the program.
User Action: Ignore the warning message or recompile
the program using the /G_FLOAT qualifier.
NOINALL, The IN option is not allowed with CONTROLLED
variables.
Error: CONTROLLED variables cannot be allocated in an
AREA.
User Action: Either remove the IN option to allow the
variable to be allocated normally, or use a BASED variable instead of a
CONTROLLED variable if you really want the allocation to be inside the
specified area.
NOLABL, PROCEDURE, ENTRY, and FORMAT statements must have a
label.
Error: The indicated statement is not labeled.
User Action: Place a label on the statement that
caused the error.
NOLABSUB, This statement contains a reference to an undefined
subscripted label array element entity(entity).
Error: The compiler cannot resolve a reference to the
indicated subscripted program label.
User Action: Verify that the label is correctly
specified, and, if it is an element of an array of label constants,
that the label is properly subscripted in the source program.
NOLOCNEED, Entity is a nonbased variable referenced with a
locator qualifier.
Error: A locator-qualified reference is specified for
a variable that does not have the BASED attribute.
User Action: Remove the locator qualifier (->) from
the reference. If you expected that the variable needed a locator
qualifier, verify that the variable has the BASED attribute.
NONCONEXTN, Entity is declared with nonconstant extents
but is not an automatic, based, or defined variable.
Error: The indicated variable or descriptor for a
character-string, bit-string, or array variable used a variable instead
of a constant to define the extent. Variables are permitted for extents
only for automatic, BASED, and DEFINED variables.
User Action: Correct the declaration of the variable.
NONCONINIT, Entity has been declared with a nonconstant
initial value. Static variables must have constant initial values.
Error: A static variable is incorrectly initialized.
User Action: Correct the declaration so that it uses
only constant values in the INITIAL attribute.
NONCONUNION, Entity is a member of a UNION but does not
have constant size.
Error: A UNION is a variation of a structure in which
all immediate members occupy the same storage. Consequently, all
members of a UNION must have a constant size.
User Action: Remove the VARYING attribute from the
structure declaration.
NORETVAL, All RETURN statements in a function must return
values.
Error: A RETURN statement in a function does not
specify a value.
User Action: Specify a value on the RETURN statement,
ensuring that the data type of the value matches the data type
specified on the RETURNS option of the PROCEDURE statement.
NOSETALL, Entity is a CONTROLLED variable; this ALLOCATE
statement cannot have the SET option.
Error: The SET option sets a pointer variable to the
memory location of storage acquired for a BASED variable. A CONTROLLED
variable cannot be used in a pointer-qualified reference.
User Action: Remove the SET option or change the
variable declaration from CONTROLLED to BASED.
NOTARITH, Implicit conversion. A nonarithmetic expression,
entity, has been used in a context requiring an arithmetic
value.
Warning: A bit- or character-string expression was
used in a context where an arithmetic expression is required. The PL/I
compiler has converted the expression to arithmetic. This situation may
or may not constitute an error.
User Action: To avoid this message in circumstances in
which you want the compiler to convert the expression to the
appropriate arithmetic data type, use the BINARY built-in function to
convert a bit string, or use the BINARY, FIXED, DECIMAL, or FLOAT
built-in function to convert a character string. You can also suppress
the message by compiling the program with the /NOWARNINGS qualifier.
NOTARRAY, The first argument to an LBOUND, HBOUND, DIM, PROD, or
SUM built-in function must be an array reference.
Error: The argument list for one of the functions
listed is incorrectly specified.
User Action: Correct the argument list for the
built-in function.
NOTBASED, The variable entity is not a BASED or CONTROLLED
variable.
Error: The target variable specified in the ALLOCATE
statement does not have the BASED attribute.
User Action: Verify that the variable is specified
correctly. If so, correct the variable's declaration so that it
specifies BASED.
NOTBIT, Implicit conversion. A nonbit expression, entity,
has been used in a context requiring a bit-string value.
Warning: An arithmetic or character-string expression
was used in a context where a bit string is required. The PL/I compiler
has converted the expression to a bit string. This situation may or may
not constitute an error.
User Action: To avoid this message in circumstances in
which you want the compiler to convert the expression to a bit string,
use the BIT built-in function to convert the character-string or
arithmetic expression to a bit string. You can also suppress the
message by compiling the program with the /NOWARNINGS qualifier.
NOTCHAR, Implicit conversion. A noncharacter expression,
entity, has been used in a context requiring a
character-string value.
Warning: An arithmetic or bit-string expression was
used in a context where a character string is required. The PL/I
compiler has converted the expression to a character string. This
situation may or may not constitute an error.
User Action: To avoid this message in circumstances in
which you want the compiler to convert the expression to a character
string, use the CHARACTER built-in function to convert the arithmetic
or bit-string expression. You can also suppress the message by
compiling the program with the /NOWARNINGS qualifier.
NOTCONDVAL, The name given in the CONDITION condition must be a
declared CONDITION.
Error: Only names explicitly declared with the
CONDITION attribute in a DECLARE statement can be used with the
CONDITION condition.
User Action: Declare the condition name explicitly.
NOTCONNECT, This statement contains an invalid reference to an
unconnected array.
Error: A member of a structure that has the dimension
attribute is referenced in an invalid context. Because the storage of
such an array is not contiguous, the array cannot be referenced in any
of the contexts listed in the message.
User Action: If possible, change the declaration of
the structure so that the array that caused the error becomes a
connected array. Otherwise, do not reference the array in the context
that caused the error.
NOTDIM, Invalid dimension specified in HBOUND, LBOUND, DIM, PROD,
or SUM.
Error: The value specified for the dimension argument
of the built-in function that caused the error is invalid for the
array. For example, this error occurs if a value of 10 is specified for
an array that has only 5 dimensions.
User Action: Determine the number of dimensions in the
array and correct the argument.
NOTDIMVAL, The second argument of the LBOUND, HBOUND, or DIM
built-in function must be an integer constant.
Error: The dimension argument for one of the functions
listed is specified using a nonconstant expression.
User Action: Specify an integer constant for the
argument.
NOTEXEC, A FORMAT, ENTRY, PROCEDURE, END, or DECLARE statement
appears in a context that requires an executable single statement,
DO-group, SELECT-group, or begin block.
Error: ON statements and THEN, ELSE, WHEN, and
OTHERWISE clauses require that the target action be an executable
statement, a DO-group, SELECT-group, or a begin block.
User Action: Move the statement in error. If
appropriate, place the statement in a begin block.
NOTFILEVAL, The name given in an I/O condition must be the name of
a file value.
Error: The UNDEFINEDFILE, ENDFILE, or KEY condition
name is specified with a value that is not a file reference.
User Action: Verify that the reference in the
condition name is to a file constant or file variable that is declared
correctly.
NOTINT, Implicit conversion. A noninteger expression,
entity, has been used in a context requiring an integer
value.
Warning: A character-string, bit-string, or noninteger
arithmetic expression is used in a context where an integer is
required. The PL/I compiler has converted the expression to an integer.
This situation may or may not constitute an error.
User Action: To avoid this message in circumstances in
which you want the compiler to convert the expression to an integer,
use the BINARY built-in function to convert bit- or character-string
expressions to an integer. You can use the FIXED built-in function to
convert floating-point expressions or fixed-point decimal expressions
with a nonzero scale factor to integers. You can also suppress the
message by compiling the program with the /NOWARNINGS qualifier.
NOTINTBND, A constant has been used as an array bound, but it is
not an integer constant whose value is less than 2**29. If a constant
is used as a bound, it must be a valid integer.
Error: An invalid constant is specified for an array
bound.
User Action: Verify that the bound specified is within
the valid range for array bounds and correct the declaration. Note that
this error may occur when any parenthesized expression follows an
identifier in a declaration. In this context, the message indicates
that the statement syntax is in error and must be corrected.
NOTINTCON, An expected optionally signed integer was not found.
Error: A nonconstant expression is specified in a
context that requires an integer constant.
User Action: Specify an integer constant.
NOTLOCATOR, A value that is not a pointer or offset value has been
used in a context requiring a locator value.
Error: The reference specified as a locator qualifier
is not a pointer or offset value.
User Action: Correct the locator-qualified reference
so that the item on the left of the locator qualifier (->) is a
pointer or offset.
NOTPARAM, Illegal use of the PRESENT function. Its argument must be
a parameter.
Error: The argument of the PRESENT built-in function
is invalid. It must be a parameter. It cannot be a variable,
expression, or constant.
User Action: Change the argument of the PRESENT
built-in function to a parameter name.
NOTPLIDATA, BIT_FIELD and BYTE_FIELD data can be referenced only in
contexts that do not require a data type interpretation.
Error: A reference to data declared as BIT_FIELD or
BYTE_FIELD was made in an illegal context.
User Action: BIT_FIELD and BYTE_FIELD data can be
referenced only in the ADDR, INT, POSINT, BYTESIZE, SIZE, and UNSPEC
built-in functions, or as an ANY parameter. If a data type
interpretation is required, define a BASED or DEFINED variable that
overlays the storage of the variable.
NOTSCALAR, An array or structure value has been used in a context
that requires a scalar value.
Error: An array or structure reference is specified in
an invalid context, for example, as an operand of an arithmetic
operation.
User Action: Correct the statement so that it does not
contain a reference to an aggregate.
NOTSUBROUT, The reference in a CALL statement is not a subroutine
reference.
Error: A CALL statement specifies the name of an entry
that has the RETURNS attribute.
User Action: If the invoked procedure is a function,
correct the statement in error so that the procedure is invoked as a
function reference. Otherwise, delete the RETURNS option from the
PROCEDURE statement of the procedure so that it can be invoked by a
CALL statement.
NULLARG, Entity has been referenced with too many empty
argument lists.
Error: A procedure call or function reference
specified too many empty argument lists, for example, F()()(A,B).
User Action: Determine the correct number of empty
argument lists, and correct the reference.
NULLPTR, The pointer or offset in a reference to entity is
NULL.
Error: A pointer or offset reference in a
locator-qualified reference has a null value. The reference cannot be
resolved.
User Action: Verify that the correct pointer or offset
variable is referenced in the statement and that it was properly given
a value, either with a SET option of ALLOCATE or by assignment with an
ADDR, POINTER, or OFFSET built-in function.
OBJNOTDCL, The refer object entity is not declared.
Error: A refer object refers to a variable that has
not been declared, or the variable follows the refer object reference
in the source program.
User Action: Verify that the refer object reference
has been declared, or reposition the REFER option so that it follows
the declaration of the refer object reference.
OBJNOTMEM, The refer object entity is not a structure
member.
Error: The refer object must be a member of the
structure declared with the REFER option.
User Action: Declare the refer object within the
structure that contains the REFER option.
OFFBASINV, A base area was specified for the OFFSET parameter or
descriptor entity.
Error: An offset parameter or argument specifies a
base area.
User Action: Remove the area specification from the
parameter's declaration or from the parameter descriptor for the
argument.
OFFSETNOBASE, In a conversion between pointer and offset data, the
offset data does not have an associated base area.
Error: The compiler cannot resolve the location of the
specified offset without the specification of the area in which the
offset is based.
User Action: Correct the declaration of the offset so
that it specifies a base area.
ONUNIT, An IF, ON, RETURN, DO, or SELECT statement cannot be used
as the first statement of an ON-unit.
Error: An ON-unit contains an invalid action statement.
User Action: Correct the ON-unit so that the first
statement is not an IF, ON, RETURN, DO, or SELECT statement. To execute
more than one statement in an ON-unit, use a begin block.
ONUNITLABL, A label prefix cannot appear on a statement used as an
ON-unit.
Error: An ON-unit action statement contains a label.
User Action: Remove the label from the statement.
PICNOTALL, The CDD description for the structure item
entity specifies a PICTURE FOR PLI in conjunction with a data
type that is not a numeric string. PICTURE FOR PLI is being
ignored.
Informational: The picture specification in the Common
Data Dictionary description does not conform to PL/I picture
specifications.
User Action: Change the data type to conform to PL/I
pictures, remove PICTURE FOR PLI, or ignore the warning message.
PICNOTALW, The PICTURE variable entity has been used in a
context requiring a FIXED or FLOAT value.
Error: A variable having the PICTURE data type has
been used in a context requiring a FIXED or FLOAT variable.
Error: A variable having the PICTURE data type has
been used in a context requiring a FIXED or FLOAT variable.
User Action: Change the data type of the variable or
use one of the built-in conversion functions to convert the variable to
either FIXED or FLOAT.
PLACEEOL, Placeholder not terminated before end of line.
Error: Placeholders cannot cross line boundaries.
User Action: Modify the source code so that each
placeholder begins and ends on the same line.
PLACELONG, Placeholder too long.
Error: Placeholders are limited to 256 characters.
User Action: Reduce the length of the placeholder. The
256-character limit includes the outer brackets.
PLACENODESIGN, Placeholders invalid without
/DESIGN=PLACEHOLDERS.
Error: Placeholders are not allowed unless
/DESIGN=PLACEHOLDERS was specified.
User Action: Specify the /DESIGN=PLACEHOLDERS
qualifier or remove the placeholders from the source file.
PLACENODOT, Invalid pseudocode list placeholder detected.
Error: Pseudocode placeholders are not to have the
list option.
User Action: Remove the ellipsis (...) following the
placeholder.
PLACENOOBJ, Placeholders detected - no object code generated.
Warning: The compiler does not produce object code
when the source contains placeholders.
User Action: None.
PLACESYNTAX, Invalid placeholder syntax detected.
Error: Nesting of pseudocode placeholders is not
allowed, or a mismatch in outer brackets was detected.
User Action: Correct the invalid placeholder.
PLACEUNMAT, Unmatched placeholder delimiter.
Error: The placeholder delimiters do not match
correctly.
User Action: Correct the source code so the delimiters
match.
PLIG-I-UNREACH, Code can never be executed at label.
Error (AXP): The PLIG-I-UNREACH message is generated
by the code generator when it detects a body of code that could not be
entered. Causes include a GOTO statement that jumps over a section of
code, a RETURN statement with code that follows it, and IF statements
where the logical expression is a compile-time constant '0'B.
User Action: Examine the statements surrounding the
one that generated the error and for possible dead (unreachable) code.
PPARMDCL, The name entity has previously been declared as
a preprocessor procedure parameter. It cannot be declared as a
preprocessor label in this procedure.
Error: The same name was used for both a preprocessor
procedure parameter and a label.
User Action: Determine which name is correct; rename
either the label or the parameter.
PPBADPAREN, This preprocessor STATEMENT procedure invocation
contains unbalanced parentheses.
Error: The invocation of a preprocessor procedure as a
pseudo-statement contains unbalanced parentheses.
User Action: Examine the invocation and add or remove
opening or closing parentheses as necessary.
PPBADRET, %RETURNS cannot be used except in a preprocessor
procedure.
Error: A %RETURN statement appears in a context other
than in a preprocessor procedure.
User Action: Remove the %RETURN statement or
reposition it so that it is contained within a preprocessor procedure.
PPBIFARG, The entity preprocessor built-in function has
been referenced with the wrong number of arguments.
Error: An argument list for a preprocessor built-in
function contains an invalid number of arguments.
User Action: Correct the number of arguments to the
built-in function.
PPBIGEXPR, An expression or reference contained within this
preprocessor usage is excessively complex.
Error: The compiler cannot follow the flow of the
preprocessing due to an expression or reference that is too complex.
User Action: Simplify the preprocessor statement.
PPCONVERR, Evaluation of a preprocessor expression caused a
CONVERSION error.
Error: The indicated expression does not have a valid
preprocessor computational data type. The operands of a preprocessor
expression can consist only of unsubscripted references to preprocessor
variables, decimal integer constants, bit-string constants,
character-string constants, and references to preprocessor built-in
functions. For arithmetic operations, only decimal integer arithmetic
of precision (10,0) is performed.
User Action: Examine the expression and correct the
error.
PPDCLREP, The name entity has previously been declared as
a preprocessor variable. It cannot be declared as a %REPLACE
identifier.
Error: Preprocessor variables cannot have the same
name.
User Action: Rename one of the variables so that there
are no duplicate names.
PPDEFPARAM, A preprocessor procedure references the undeclared
preprocessor parameter entity. It is being declared as a FIXED
preprocessor parameter.
Warning: A preprocessor parameter that was not
declared has been referenced; the compiler gives the attribute FIXED by
default.
User Action: Check that the reference is correctly
spelled; if it is not, correct the spelling reference. If the parameter
was not declared, declare it with the appropriate attribute.