Kednos PL/I for OpenVMS Systems
User Manual
SOURCETYPE, The CDD description for structure item entity
contains the Source Type attribute. Source Type is being ignored by
PL/I.
Informational: PL/I does not support the Common Data
Dictionary Source Type attribute.
User Action: None.
STAREAINIT, Entity has been declared with an invalid
initial value. Static AREAs can be initialized only to EMPTY().
Error: An invalid initial value has been specified for
the AREA variable referenced in the DECLARE statement. AREAs with the
STATIC attribute can be initialized only with the EMPTY() built-in
function.
User Action: Change the initial value to EMPTY() or
change the declaration so that the variable does not have the STATIC
attribute.
STMTOOBIG, A statement exceeds the implementation's limit of
constants, identifiers, operators, and punctuation symbols. Or, there
are more than approximately 4500 statements in the procedure.
Fatal: The statement contains more than 2048
constants, identifiers, and punctuation symbols, including operators.
User Action: Simplify the statement.
STMTSYNKEY, Invalid syntax in an entity statement.
Entity was found where the entity keyword was
expected.
Error: A statement is missing a keyword.
User Action: Correct the syntax of the statement as
indicated by the message.
STMTSYNTOK, Invalid syntax in an entity statement.
Entity was found where entity was expected.
Error: The compiler looks for specific types of tokens
within statements, attribute lists, and extents. This error occurs when
one type of token appears in an inappropriate context, for example, if
the ADDR built-in function occurs in an INITIAL attribute list or if
the required string is missing from a PICTURE attribute.
User Action: Determine what data the compiler expects
and correct the statement.
STPTOFINIT, Entity has been declared with an invalid
initial value. Static POINTERs or OFFSETs can be initialized only to
NULL().
Error: An invalid initial value has been specified for
the POINTER or OFFSET variable referenced in the DECLARE statement.
POINTERs and OFFSETs with the STATIC attribute can be initialized only
with the NULL() built-in function.
User Action: Change the initial value to NULL(), or
change the declaration so that the variable does not have the STATIC
attribute.
STRDEPTH, The depth of nesting of a structure exceeds the
implementation's limit of 16.
Fatal: A structure contains too many levels.
User Action: Correct the declaration of the structure.
If necessary, modify the structure so that it has no more than 16
levels.
STREFCNT, A structure-qualified reference contains more than 15
qualifying names.
Error: A reference in the form name1.name2.name3...
contains more than 15 names.
User Action: Examine the structure-qualified reference
and compare it with the declaration of the structure to ensure that
each qualifying name is specified correctly.
STRGTOOBIG, The length of a name or constant exceeds the
implementation limit of 32500 characters. Ensure that all string
constants are delimited with ' and that any contained 's occur in
pairs. Also check for unbalanced /* */.
Fatal: The compiler read more than 32500 characters
following the occurrence of an open apostrophe (') or comment (/*).
User Action: Terminate the unterminated string or
comment at the appropriate location.
STRINGBIF, The argument of the STRING built-in function must be a
variable that is suitable for use in string overlay defining. It must
contain only bit or only character data and must not be VARYING or
ALIGNED or be an unconnected array.
Error: The STRING built-in function is used
incorrectly.
User Action: Verify that the correct argument is
specified for the STRING built-in function. If the argument seems
correct, be sure that its declaration does not violate any of the rules
given in the message.
SUBRANGE, The integer value entity does not lie in the
range entity : entity.
Error: An integer constant appears in a context where
the value of the integer is outside the permissible range.
User Action: Check that the constant was specified
correctly and that it does not exceed the implementation limit for the
context.
SUBROUT, The subroutine entity has been called as a
function.
Error: The statement contains a reference to a
procedure that does not have the RETURNS attribute.
User Action: If the invoked procedure is a subroutine,
correct the statement in error so that the procedure is invoked with a
CALL statement. Otherwise, add the RETURNS attribute to the PROCEDURE
statement of the procedure so that it can be invoked by a function
reference.
TAGVALUES, The CDD description for structure item entity
contains the Tag Values attribute. Tag Values is being ignored by
PL/I.
Informational: PL/I does not support the Common Data
Dictionary Tag Values attribute.
User Action: None.
TAGVARIAB, The CDD description for structure item entity
contains the Tag variable attribute. Tag variable is being ignored by
PL/I.
Informational: PL/I does not support the Common Data
Dictionary Tag variable attribute.
User Action: None.
TOOFEWARG, Entity has been referenced with too few
arguments.
Error: The number of parameters in a parameter list or
parameter descriptor list exceeds the number of arguments specified in
the corresponding procedure reference.
User Action: Verify the number of arguments required
by the invoked procedure, and correct the argument list. If the
procedure has a variable-length argument list, specify the TRUNCATE
attribute on the proper formal parameters in the entry declaration.
TOOFEWSUB, Entity has been referenced with too few
subscripts. Subscripted references must have as many subscripts as the
array has dimensions, including any inherited dimensions.
Error: The number of subscripts specified in the
reference to the array variable is fewer than the number of dimensions
in the array.
User Action: Examine the declaration of the array to
determine the number of subscripts required, determine the missing
subscripts, and correct the statement. If the array is declared within
a structure that is dimensioned, be sure to include the structure
dimensions in the total dimensions of the array.
TOOFEWVAL, The INITIAL attribute specified for entity
contains fewer values than are required to fully initialize the
variable.
Warning: An INITIAL attribute specified for an array
specifies fewer items than there are elements of the array.
User Action: Verify that the program will execute
successfully without all array elements initialized. If not, correct
the declaration of the array so that all elements are initialized.
TOOMANYARG, Entity has been referenced with too many
arguments.
Error: The number of arguments in a procedure
reference exceeds the number of parameters in the corresponding
parameter list or parameter descriptor list.
User Action: Verify the number of arguments required
by the invoked procedure, and correct the argument list. If the
procedure is a non-PL/I procedure with a variable-length argument list,
specify the LIST attribute on the last parameter of the entry
declaration.
TOOMANYDIM, More than eight dimensions have been specified in the
declaration of an array.
Error: The parenthesized list of dimensions in the
declaration of the array contains more than eight items.
User Action: Correct the declaration of the array so
that it has no more than eight dimensions.
TOOMANYLBARS, Too many label arrays associated with GOTO OTHERWISES
and/or ASTERISK LABEL SUBSCRIPTS.
Error: The number of label arrays associated with GOTO
OTHERWISES and/or ASTERISK LABEL SUBSCRIPTS is limited to 500 per
compilation.
User Action: Reduce the number of label arrays
associated with GOTO OTHERWISES and/or ASTERISK LABEL SUBSCRIPTS.
TOOMANYOPS, More than 253 operands have been used with an operator,
function, or call.
Error: An expression contains more than 253 operands.
User Action: Simplify the statement in error.
TOOMANYSUB, Entity has been referenced with too many
subscripts.
Error: The number of subscripts in the reference to an
array element exceeds the number of dimensions of the array.
User Action: Examine the declaration of the array to
determine the number of subscripts required, determine the subscripts
in excess, and correct the statement.
TOOMANYVAL, Excess initial values have been specified for
entity.
Warning: An INITIAL list for an array declaration
specifies more constant values than array elements, or multiple values
were specified for a scalar constant. A list of values is valid only in
an array declaration. The declaration DCL (A,B)... INIT(1,2)
initializes both A and B to 1. The second value specified is ignored.
User Action: Delete the excess values.
TOTALDIM, More than eight dimensions have been specified for the
array entity. This may include dimensions inherited from
containing structures.
Error: An array has been declared with more than eight
dimensions, or an array is declared within a structure, and the sum of
the array's dimensions and those of the structure exceeds a total of
eight.
User Action: Correct the declaration of the array.
TYPEHASMEM, Only structures without members can be declared with
the entity TYPE attribute.
Error: The structure declaration containing the TYPE
attribute already contains other members.
User Action: Remove the members of the structure or
substructure containing the TYPE attribute.
UNALIGNED, Entity has been declared with the UNALIGNED
attribute. Only BIT or CHARACTER string variables can be declared
UNALIGNED.
Error: PL/I does not implement the UNALIGNED
attribute for types other than NONVARYING strings.
User Action: Remove the UNALIGNED attribute.
UNDCLBASE, Entity is undeclared and has been used in an
ALLOCATE statement as the name of a BASED or CONTROLLED variable.
Error: The target variable in the ALLOCATE statement
is a name that is not declared.
User Action: Verify that the variable is specified
correctly. If it is, declare it with the BASED or CONTROLLED attribute.
UNDCLPARM, Entity is an undeclared parameter. It has been
declared in its containing block and will acquire default
attributes.
Warning: A name specified in a parameter list is not
declared with data type attributes. The compiler gave the parameter the
attributes FIXED BINARY.
User Action: Declare the parameter with the
appropriate data type attributes.
UNLIKEREF, Entity, which has been declared with the LIKE
attribute, references a variable that is not known to this block.
Error: The major or minor structure referenced by the
LIKE attribute is not known to the current block. Therefore, the
compiler cannot locate the referenced structure.
User Action: Declare the referenced structure outside
of the procedure, if the STATIC storage class is acceptable. Otherwise,
declare the referenced structure within the appropriate block.
UNRATTR, Entity is an unrecognizable attribute.
Error: A declaration in a descriptor contains an
invalid keyword.
User Action: Check for typographical errors on the
statement. Verify the syntax of the descriptor, noting particularly
that commas, parentheses, and spaces appear where required.
UNRCNDNAME, Entity is an unrecognizable condition
name.
Error: An ON, SIGNAL, or REVERT statement specifies an
invalid condition name.
User Action: Check the statement for a typographical
error. Verify that the condition name specified is a valid
PL/I condition name.
UNRENV, Entity is an unrecognized ENVIRONMENT keyword.
Error: An ENVIRONMENT option list is incorrectly
specified or contains an invalid option.
User Action: Check the list of ENVIRONMENT options for
a typographical error, a missing underscore character, or an invalidly
abbreviated option name. Verify that all options specified are valid
ENVIRONMENT options in PL/I.
UNRFMT, Entity is an unrecognizable format item.
Error: A format list in a GET EDIT or PUT EDIT
statement contains a character that is not a valid PL/I format
item.
User Action: Verify the syntax of the format list and
ensure that the format item is a valid PL/I format item.
UNRLOCREF, A locator-qualified reference to entity cannot
be resolved to any declaration known to this block.
Error: A reference to a BASED variable is not valid.
User Action: Check the declaration of the variable to
ensure that it is correctly specified and that the qualified reference
specifies a valid pointer or offset value.
UNRPERSTMT, Entity is an unrecognizable preprocessor
statement.
Error: A statement beginning with a percent sign (%)
is not a valid PL/I preprocessor statement.
User Action: Check that a preprocessor keyword is
spelled correctly; or, if a percent sign is specified in a
character-string constant, verify that the string is properly delimited.
UNRSTMT, This is an unrecognizable statement. Starting at
entity.
Error: A statement does not contain any identifiable
PL/I statement keywords, or a statement contains extraneous tokens. For
example, the statement ON...THEN causes this error.
User Action: Examine the statement in error and
correct it.
UNRSTREF, A structure-qualified reference to entity cannot
be resolved to any declaration known to this block.
Error: A reference in the form name1.name2.name3...
cannot be resolved.
User Action: Examine the structure-qualified reference
in the statement that caused the error. Verify that the structure
member that is referenced is a part of the specified structure. Correct
the reference so that it refers to the correct structure or to the
correct member.
UNSUPPTYPE, The CDD description for structure item entity
specifies an unsupported data type.
Informational: The Common Data Dictionary description
for a structure item has attempted to use a data type that is not
supported by PL/I. The PL/I compiler has supplied the data type of
BYTE_FIELD or BIT_FIELD.
User Action: Change the data type to one which is
supported by PL/I, or use the PL/I built-in functions ADDR, SIZE,
BYTESIZE, or UNSPEC to manipulate BYTE_FIELD and BIT_FIELD.
UNTYPEREF, Entity has been declared with the TYPE
attribute; entity references a variable that is not known to
entity in this block.
Error: The major or minor structure referenced by the
TYPE attribute is not known to the current block. Therefore, the
compiler cannot locate the referenced structure.
User Action: Declare the referenced structure outside
of the procedure, if the STATIC storage class is acceptable. Otherwise,
declare the referenced structure within the appropriate block.
UPPRGTRLOW, One of the bounds declared for entity is
invalid because the lower bound is greater than the upper bound.
Error: An array is incorrectly declared.
User Action: Correct the declaration of the array
variable in error so that all bounds are valid. In the declaration of
the bound x:y, the value of x must be numerically less than the value
of y.
USERDIAG, Entity.
Error: The PL/I embedded preprocessor permits
you to write your own compile-time diagnostic messages. The text of the
message is user-specified and responds to a user-specified compile-time
condition. Error messages inhibit the production of an object file.
User Action: Determine the cause of the problem from
the source text and correct the error.
VALPARAM, The PRESENT function may return an unpredictable result
when its argument is a value parameter.
Warning: The argument to the PRESENT built-in function
is a parameter that is passed by value. Correct results may not be
returned by this function, because passing a zero will cause PRESENT to
return false.
User Action: Change the passing mechanism of the
parameter, or make sure that a zero is never passed as an argument to
this routine.
VALSIZE, The size or precision of entity is incompatible
with the VALUE attribute.
Error: A parameter descriptor or variable declared
with the VALUE attribute specifies a fixed binary value with a
precision not equal to 31 or a bit-string value with a length not equal
to 32.
User Action: Correct the declaration so that it
specifies a variable that requires 32 bits or less of storage.
VALTYPE, The data type of entity is incompatible with the
VALUE attribute.
Error: The VALUE attribute is specified for a variable
that does not have either the FIXED BINARY or BIT(32) ALIGNED attribute.
User Action: Correct the declaration.
VALUEBIF, Invalid use of the VALUE built-in function.
Error: The VALUE built-in function can be used only to
override the passing mechanism of an argument. This means it must be
used in an argument list and its parameter must be an argument.
User Action: Remove the reference to the built-in
function from the statement.
VARFORMAT, The Common Data Dictionary record description
entity specifies variable format.
Error: PL/I does not accept variable formats from the
Common Data Dictionary.
User Action: Rewrite the Common Data Dictionary record
description so that the format is fixed length.
VARYING, Entity has been declared with the VARYING
attribute. Only CHARACTER variables can be declared VARYING.
Error: The VARYING attribute is specified for a
variable to which it cannot be applied.
User Action: Correct the declaration so that it does
not specify VARYING.
VARYSCALE, The scale factor q specified for entity is not
in the range 0<=q<=p, where p is the variable's precision. The
scale factor has been set to zero.
Warning: A scale is specified for a variable that is
not in its declared range.
User Action: Specify a scale factor in the allowed
range.
WHATBIF, Entity is not a built-in function or procedure
known to this implementation. If this is an external entry, it must be
declared by a DECLARE statement with an ENTRY attribute.
Error: A reference to a procedure cannot be resolved.
User Action: Verify that the variable referenced in
the statement is a valid subroutine or function. If it is an external
function, declare it with the ENTRY attribute.
A.2 Run-Time Messages
This section lists the diagnostic messages produced by the
VAX and Alpha run-time systems.
ANYCOND, PL/I ANYCONDITION condition.
Fatal: This error message is displayed when
ANYCONDITION is specifically signaled and there is no ON-unit for
ANYCONDITION.
User Action: Write an ON-unit to handle ANYCONDITION,
or do not signal ANYCONDITION. Correct the source program.
AREA, PL/I AREA condition.
Fatal: The PL/I AREA condition was raised either by a
SIGNAL AREA statement, or by the PL/I run-time library.
User Action: If the exception was raised by the RTL,
see the secondary condition for more information.
AREA_ACTIVE, Operation attempted on an already active area.
Informational: The PL/I run-time library detected that
an area it was about to perform an operation on is already active. If
this condition occurs, it is typically because an operation is being
attempted on an area from both AST level and non-AST level
simultaneously, or because the area is in a shared memory environment
and being modified by more than one processor at once.
User Action: Rewrite the application to avoid
simultaneous modification of an area. If that is not desirable, you may
want to consider handling the condition with an ON-unit. See
Chapter 10 for more information.
AREA_ASSIGN, Target area in area assignment is too small.
Informational: An assignment was attempted, and the
size of the target area was insufficient to hold the extent of the
source area.
User Action: Correct the situation that caused the
problem to occur, or add an ON-unit to process the condition.
AREA_FORMAT, Operation attempted on an incorrectly formatted
area.
Informational: The PL/I run-time library detected an
area to be incorrectly formatted while attempting an allocation or
deallocation in the area, or while performing an area assignment from
the area.
User Action: The area may be corrupt because it was
never initialized with the EMPTY() built-in function, or because of
invalid pointer references or data access.
AREA_FREE, Error detected deallocating a variable in an area.
Informational: The PL/I run-time library detected that
a FREE operation in an area was not valid. For example, the variable
being freed incorrectly extends beyond the end of the area, extends
into a free section of the area, or is already in a free section of the
area. This problem normally arises when a variable of a different size
than the one originally allocated is used for the free operation, or
when the variable is freed more than one time.
User Action: Correct the logic problem in the source
program.
AREA_FULL, No room for variable allocation in area at address
entity.
Informational: An allocation was attempted in an area
that could not be performed because the area did not have enough
contiguous space to allocate the variable requested. The address of the
area is in hexadecimal.
User Action: Handle the condition. See Chapter 10
for more information.