Rational Developer for System z
Enterprise PL/I for z/OS, Version 3.8, Messages and Codes Manual

Compiler Severe Messages (1500-2399)

IBM1500I S
Argument number argument-number in ENTRY reference ENTRY name has type source type, which is invalid for a parameter with type target type.
Explanation:

An argument must have a type that can be converted to the corresponding parameter’s type.

IBM1501I S
Argument number argument-number in ENTRY reference ENTRY name has a different strong type than the corresponding parameter.
Explanation:

If a parameter is strongly typed, any argument passed to it must have the same type.

IBM1502I S
Argument number argument-number in ENTRY reference ENTRY name has type source type, which is invalid for a parameter with type target type. If the ENTRY should be invoked, an argument list must be provided.
Explanation:

An argument must have a type that can be converted to the corresponding parameter’s type.

IBM1503I S
Argument number argument-number in ENTRY reference ENTRY name has type source type, which is invalid for a parameter with type LIMITED ENTRY.
Explanation:

Only an EXTERNAL ENTRY CONSTANT, an ENTRY CONSTANT representing a non-nested PROCEDURE, or an ENTRY VARIABLE with the LIMITED attribute can be passed to a LIMITED ENTRY parameter.

IBM1504I S
Argument number argument-number in ENTRY reference ENTRY name has type POINTER, which is invalid for an OFFSET parameter without an AREA qualifier.
Explanation:

POINTER expressions can be converted to OFFSET only if the OFFSET is declared with an AREA qualifier.

IBM1505I S
Argument number argument-number in ENTRY reference ENTRY name has type POINTER, which is invalid for a POINTER parameter since the OFFSET argument is not an OFFSET variable declared with an AREA qualifier.
Explanation:

OFFSET variables can be converted to POINTER only if the OFFSET is declared with an AREA qualifier.

IBM1506I S
Argument number argument-number in ENTRY reference ENTRY name has a different ORDINAL type than the corresponding parameter.
Explanation:

ORDINALs cannot be passed to other ORDINALs having different ORDINAL types.

IBM1507I S
Arrays of label constants may not be passed as arguments.
Explanation:

The array can be assigned to an array of LABEL variables, and that array can be passed.

 
 
    lx(1): ... ;
 
    lx(2): ... ;
 
    call x( lx );
 
IBM1508I S
Too few arguments have been specified for the ENTRY ENTRY name.
Explanation:

The number of arguments must match the number of parameters in the ENTRY declaration.

IBM1509I S
Argument to variable name pseudovariable must be ASSIGNABLE.
Explanation:

The target in an assignment through a pseudovariable must not have the NONASSIGNABLE attribute.

 
 
    dcl a static nonasgn char(7) init(’example’);
 
    unspec(a) = ’’b;
 
IBM1510I S
First argument to variable name pseudovariable must be ASSIGNABLE.
Explanation:

The target in an assignment through a pseudovariable must not have the NONASSIGNABLE attribute.

 
 
    dcl a static nonasgn char(7) init(’example’);
 
    substr(a,1,2) = ’tr’;
 
IBM1511I S
Argument number argument-number in ENTRY reference ENTRY name is an aggregate, but the parameter description specifies a scalar.
Explanation:

Scalars cannot be converted to aggregates.

 
 
    dcl a entry( fixed bin ), b(10) fixed bin;
 
    call a( b );
 
IBM1512I S
Argument number argument-number in ENTRY reference ENTRY name is a scalar, but the parameter description specifies an aggregate to which it cannot be passed.
Explanation:

Dummy aggregate arguments are not supported except when passing a non-AREA scalar to a non-CONTROLLED array of scalars, and the array must have no bounds specified as *. The scalar can be assigned to an aggregate, and that aggregate can be passed.

 
 
    dcl a entry( 1, 2 fixed bin, 2 fixed bin );
 
    call a( 0 );
 
IBM1513I S
Argument number argument-number in ENTRY reference ENTRY name is an aggregate that does not exactly match the corresponding parameter description.
Explanation:

Dummy aggregate arguments are not supported. If an entry description describes an aggregate parameter, then any argument passed must match that parameter’s description.

IBM1514I S
Argument number argument-number in ENTRY reference ENTRY name is an aggregate with more members than its corresponding parameter description.
Explanation:

Dummy aggregate arguments are not supported. If an entry description describes an aggregate parameter, then any argument passed must match that parameter’s description.

IBM1515I S
Argument number argument-number in ENTRY reference ENTRY name is an aggregate with fewer members than its corresponding parameter description.
Explanation:

Dummy aggregate arguments are not supported. If an entry description describes an aggregate parameter, then any argument passed must match that parameter’s description.

IBM1516I S
The number of dimensions in the subelements of argument number argument-number in ENTRY reference ENTRY name and in its corresponding parameter description do not match.
Explanation:

Dummy aggregate arguments are not supported. If an entry description describes an aggregate parameter, then any argument passed must match that parameter’s description.

IBM1517I S
The upper and lower bounds in the subelements of argument number argument-number in ENTRY reference ENTRY name and in its corresponding parameter description do not match.
Explanation:

Dummy aggregate arguments are not supported. If an entry description describes an aggregate parameter, then any argument passed must match that parameter’s description.

IBM1518I S
The number of dimensions for argument number argument-number in ENTRY reference ENTRY name and in its corresponding parameter description do not match.
Explanation:

Array arguments and parameters must have the same number of dimensions.

 
 
    dcl a entry( (*,*) fixed bin ),
        b (10) fixed bin;
 
    call a( b );
 
IBM1519I S
The upper and lower bounds for argument number argument-number in ENTRY reference ENTRY name and in its corresponding parameter description do not match.
Explanation:

Array arguments and parameters must have the same lower and upper bounds.

 
 
    dcl a entry( (0:10) fixed bin ),
        b (10) fixed bin;
 
    call a( b );
 
IBM1520I S
Charset 48 is not supported.
Explanation:

Charset 48 is no longer supported. The source code must be converted to charset 60.

IBM1521I S
Not enough virtual memory is available to continue the compile.
Explanation:

The compilation requires more virtual memory than is available. It may help to specify one or more of the following compiler options: NOTEST, NOXREF, NOATTRIBUTES, and/or NOAGGREGATE

IBM1522I S
variable cannot be SET unless an IN clause is specified.
Explanation:

If an offset variable is declared without an AREA reference, it cannot be set in an ALLOCATE or LOCATE statement unless an IN clause names an AREA reference.

IBM1523I S
Argument to BUILTIN name built-in must be an AREA reference.
Explanation:

The built-in function AVAILABLEAREA is defined only for AREAs.

IBM1524I S
BUILTIN name(x) is undefined if ABS(x) > 1.
Explanation:

An expression contains the built-in function ASIN or ACOS applied to a restricted expression that evaluated to a number outside the domain of that function.

IBM1525I S
ATANH(x) is undefined if x is REAL and ABS(x) >= 1.
Explanation:

An expression contains the built-in function ATANH applied to a restricted expression that evaluated to a number outside the domain of that function.

IBM1526I S
Argument to BUILTIN name must have derived mode REAL.
Explanation:

An expression contains the named built-in function with an argument having mode COMPLEX.

IBM1527I S
First argument to BUILTIN name built-in must have locator type.
Explanation:

An expression contains the named built-in function with its first argument having neither type POINTER nor OFFSET.

IBM1528I S
First argument to BUILTIN name built-in must have derived mode REAL.
Explanation:

An expression contains the named built-in function with its first argument having mode COMPLEX. This message applies, for example, to the ATAN and ATAND built-in functions when two arguments are given.

IBM1530I S
Second argument to BUILTIN name built-in must have derived mode REAL.
Explanation:

An expression contains the named built-in function, with its second argument having mode COMPLEX. This message applies, for example, to the ATAN and ATAND built-in functions when two arguments are given.

IBM1531I S
BUILTIN name argument has invalid type.
Explanation:

An expression contains the reference BINARYVALUE(x) where x has a type other than POINTER, OFFSET or ORDINAL.

IBM1532I S
E35 sort exit routines must use a 32-bit linkage.
Explanation:

Any other linkage is invalid.

IBM1533I S
BUILTIN name argument must have computational type.
Explanation:

An expression contains the named built-in function with an argument that has neither string nor numeric type.

IBM1534I S
BUILTIN name result would be too long.
Explanation:

The result of the REPEAT or COPY built-in function must not be longer than the maximum allowed for the base string type.

IBM1535I S
BUILTIN name argument must have type REAL FLOAT.
Explanation:

An expression contains the named built-in function with an argument having type other than REAL FLOAT. This message applies, for instance, to the floating-point inquiry built-in functions such as HUGE and RADIX, and to the floating-point manipulation built-in functions such as EXPONENT and SUCC.

IBM1536I S
BUILTIN name argument must be a reference.
Explanation:

An expression contains the named built-in function with an argument that is not a reference.

IBM1537I S
BUILTIN name argument must be an array expression.
Explanation:

An expression contains the named built-in function with an argument that is not an array expression. This message applies, for example, to the built-in functions ALL, ANY, SUM and PROD.

IBM1538I S
BUILTIN name argument must be a FILE reference.
Explanation:

An expression contains the named built-in function with an argument that is not a FILE. This message applies, for example, to the I/O built-in functions such as LINENO and PAGENO.

IBM1539I S
* is invalid as a BUILTIN function argument.
Explanation:

A value must be specified as an argument to a BUILTIN function unless the argument is optional.

 
 
    dcl a float;
 
    a = sqrt(*);
 
IBM1540I S
Argument number argument number to BUILTIN name built-in must have derived mode REAL.
Explanation:

An expression contains the named built-in function with the specified argument having mode COMPLEX. This message applies to the MAX and MIN built-in functions.

IBM1541I S
Argument number argument number to BUILTIN name built-in must have computational type.
Explanation:

An expression contains the named built-in function with the specified argument having noncomputational type. This message applies to the MAX and MIN built-in functions.

IBM1542I S
First argument to BUILTIN name built-in must have computational type.
Explanation:

An expression contains the named built-in function with a first argument that has neither string nor numeric type.

IBM1543I S
Argument to BUILTIN name built-in must have type CHARACTER(1) NONVARYING.
Explanation:

This applies to the RANK built-in function.

IBM1545I S
First argument to BUILTIN name built-in must be an array.
Explanation:

An expression contains the named built-in function with a first argument that is not an array. This message applies, for instance, to the DIMENSION, HBOUND, and LBOUND built-in functions.

IBM1546I S
Second argument to BUILTIN name built-in must have type CHARACTER(1) NONVARYING.
Explanation:

This applies to the PLIFILL built-in subroutine.

IBM1547I S
Second argument to BUILTIN name built-in must have computational type.
Explanation:

An expression contains the named built-in function with a second argument that has neither string nor numeric type.

IBM1548I S
BUILTIN function may not be used inside a BEGIN block.
Explanation:

The PLISTSIZE built-in functions may be used only in procedures.

IBM1549I S
BUILTIN function may be used only in procedures with LINKAGE(SYSTEM).
Explanation:

The PLISTSIZE built-in function may not be used in procedures with any of the linkages OPTLINK, PASCAL, etc.

IBM1550I S
Argument to the BUILTIN name pseudovariable must be an EVENT variable.
Explanation:

This message applies to the COMPLETION and STATUS pseudovariables.

IBM1551I S
Argument to the BUILTIN name pseudovariable must be a TASK variable.
Explanation:

This message applies to the PRIORITY pseudovariable.

IBM1552I S
Third argument to BUILTIN name built-in must have computational type.
Explanation:

An expression contains the named built-in function with a third argument that has neither string nor numeric type. This message applies, for example, to the SUBSTR and CENTER built-in functions.

IBM1554I S
Argument to BUILTIN name built-in must be either a NONVARYING BIT array reference or else an array expression with known length.
Explanation:

The ALL and ANY built-in functions are restricted to two types of array expressions: an array expression that is a NONVARYING BIT array reference or an array expression that has known length. The first five examples below meet these restrictions, but the remaining examples do not.

 
 
    dcl a(10) bit(16) varying;
    dcl b(10) bit(16);
 
    if all( b ) then ...
    if any( a ^= ’’b ) then ...
    if all( a = b & a ) then ...
    if any( ’’b ^= b ) then ...
    if all( a = ’’b | b = ’’b ) then ...
    if any( a ) then ...
    if all( substr(b,1,n) ) then ...
 
IBM1555I S
Second argument to BUILTIN name built-in must have computational type.
Explanation:

An expression contains the named built-in function with a second argument that has neither string nor numeric type.

IBM1556I S
Third argument to BUILTIN name built-in would force STRINGRANGE.
Explanation:

If a third argument is given for one of the built-in functions INDEX, SEARCH or VERIFYR, it must be positive. For SEARCHR and VERIFYR, it must be nonnegative.

IBM1557I S
Second argument to BUILTIN name built-in must be positive.
Explanation:

The second argument for the built-in functions CENTER, LEFT and RIGHT must not be zero or negative.

IBM1558I S
Argument to VALID built-in must have the attributes FIXED DECIMAL or PICTURE.
Explanation:

The argument to the VALID built-in function must have exactly the indicated attributes. It is not sufficient that it can be converted to these attributes.

IBM1559I S
SQRT(x) is undefined if x is REAL and x < 0.
Explanation:

An expression contains the BUILTIN function SQRT applied to a restricted expression that evaluated to a number outside the domain of that function.

IBM1560I S
BUILTIN function(x) is undefined if x is REAL and x <= 0.
Explanation:

An expression contains the named built-in function applied to a restricted expression that evaluated to a number outside the domain of that function. This message applies, for instance, to the LOG, LOG2, and LOG10 built-in functions.

IBM1561I S
RULES(ANS) does not allow ROUND to be applied to FIXED BIN.
Explanation:

RULES(ANS) dose not permit non-zero scale factors with FIXED BIN, and hence it does not allow ROUND to be applied to FIXED BIN (or BIT) arguments.

IBM1562I S
Argument to BUILTIN name built-in has invalid type.
Explanation:

The argument to the HANDLE built-in must be a structure type, and conversely the argument to the TYPE built-in must be a handle.

IBM1563I S
Second argument to BUILTIN name built-in must be nonnegative.
Explanation:

The second argument for the built-in functions CHARACTER, BIT, and GRAPHIC must be zero or greater.

IBM1564I S
Too few arguments have been specified for the BUILTIN name built-in.
Explanation:

Supply the minimum number of arguments required.

IBM1566I S
BUILTIN name(x) is undefined for x outside the supported domain.
Explanation:

An expression contains the named built-in function applied to a restricted expression that evaluated to a number outside the supported domain of that function.

IBM1568I S
BUILTIN function(x,y) is undefined if x=0 and y=0.
Explanation:

An expression contains the built-in function ATAN or ATAND applied to a restricted expression that evaluated to a number outside the domain of that function.

IBM1569I S
BUILTIN name argument must be a CONNECTED reference.
Explanation:

The argument to the named built-in function must be a reference (for example, not an expression or a literal), and that reference must be CONNECTED.

IBM1570I S
BUILTIN name argument must be a reference to a level 1 CONTROLLED variable.
Explanation:

The ALLOCATION built-in function cannot be used with structure members or with non-CONTROLLED variables.

IBM1571I S
BUILTIN name argument must be a reference to a level 1 BYADDR parameter.
Explanation:

The OMITTED built-in function cannot be used with BYVALUE parameters, structure members, or non-parameters.

IBM1573I S
The use of * as an argument is permitted only for parameters declared with the OPTIONAL attribute.
Explanation:

Add the OPTIONAL attribute to the entry declaration or replace the * by an actual argument.

IBM1575I S
Argument number argument number to BUILTIN name built-in must have type POINTER or OFFSET.
Explanation:

The indicated argument to built-in functions such as PLIMOVE and COMPARE must be a locator.

IBM1576I S
Third argument to BUILTIN name built-in must have type CHARACTER(1) NONVARYING.
Explanation:

This applies to the HEXIMAGE built-in subroutine.

IBM1577I S
First argument to BUILTIN name built-in must have type POINTER.
Explanation:

This applies to the OFFSET built-in function.

IBM1578I S
First argument to BUILTIN name built-in must have type OFFSET.
Explanation:

This applies to the POINTER built-in function.

IBM1579I S
Second argument to BUILTIN name built-in must have type AREA.
Explanation:

This applies to the OFFSET and POINTER built-in functions.

IBM1580I S
First argument to BUILTIN name built-in is an OFFSET value.
Explanation:

If the first argument to built-in functions such as PLIMOVE and COMPARE has the attribute OFFSET, it must be an OFFSET reference not an OFFSET value.

IBM1581I S
First argument to BUILTIN name built-in is an OFFSET variable declared without an AREA qualifier.
Explanation:

If the first argument to built-in functions such as PLIMOVE and COMPARE is an OFFSET variable, that OFFSET variable must be declared with an AREA qualifier so that the offset can be converted to an address.

IBM1582I S
Argument number argument number to BUILTIN name built-in is an OFFSET value.
Explanation:

If the indicated argument to built-in functions such as PLIMOVE and COMPARE has the attribute OFFSET, it must be an OFFSET reference not an OFFSET value.

IBM1583I S
Argument number argument number to BUILTIN name built-in is an OFFSET variable declared without an AREA qualifier.
Explanation:

If the indicated argument to built-in functions such as PLIMOVE and COMPARE is an OFFSET variable, that OFFSET variable must be declared with an AREA qualifier so that the offset can be converted to an address.

IBM1584I S
Second argument to BUILTIN name built-in must have type OFFSET.
Explanation:

This applies to the OFFSETDIFF built-in function.

IBM1585I S
Second argument to BUILTIN name built-in must have type POINTER.
Explanation:

This applies to the POINTERDIFF built-in function.

IBM1586I S
Argument to STRING built-in function/pseudovariable must be CONNECTED.
Explanation:

The STRING built-in function and pseudovariable cannot be applied to discontiguous array cross-sections or to array parameters not declared with the CONNECTED attribute.

IBM1587I S
Argument number argument number to BUILTIN name built-in must have the ENTRY attribute.
Explanation:

Any other argument type is invalid. This message applies to the PLISRTx built-in functions.

IBM1588I S
First argument to BUILTIN name built-in must have type GRAPHIC.
Explanation:

This applies to the CHARGRAPHIC built-in function. For instance, in the following example, g should be declared as graphic, not as char.

 
 
    dcl c char(10);
    dcl g char(5);
 
    c = charg( g );
 
IBM1589I S
BUILTIN name argument must not have any subscripts.
Explanation:

The LOCATION and BITLOCATION built-in functions cannot be applied to subscripted references.

IBM1590I S
Argument to STRING built-in function/pseudovariable must not be a UNION and must not contain a UNION.
Explanation:

The STRING built-in function and pseudovariable cannot be applied to UNIONs or to structures containing UNIONs.

IBM1591I S
All members of an argument to the STRING built-in function/pseudovariable must have the UNALIGNED attribute.
Explanation:

The STRING built-in function and pseudovariable cannot be applied to structures or arrays containing elements with the ALIGNED attribute.

IBM1592I S
All members of an argument to the STRING built-in function/pseudovariable must have the NONVARYING attribute.
Explanation:

The STRING built-in function and pseudovariable cannot be applied to structures or arrays containing VARYING strings.

IBM1593I S
All members of an argument to the STRING built-in function/pseudovariable must have string type.
Explanation:

The STRING built-in function and pseudovariable cannot be applied to structures or arrays containing noncomputational types or arithmetic types other than pictures.

IBM1594I S
All members of an argument to the STRING built-in function/pseudovariable must have the same string type.
Explanation:

The STRING built-in function and pseudovariable cannot be applied to structures or arrays containing different string types, for example, BIT and CHARACTER strings.

IBM1595I S
First argument to BUILTIN name built-in must have type REAL FLOAT.
Explanation:

This applies to the floating-point inquiry and manipulation built-in functions such as HUGE and EXPONENT.

IBM1596I S
Second argument to BUILTIN name built-in must have type CHARACTER.
Explanation:

This applies to the EDIT built-in function.

IBM1597I S
BUILTIN name argument must have type TASK.
Explanation:

This applies to the PRIORITY built-in function.

IBM1598I S
BUILTIN name argument must have type EVENT.
Explanation:

This applies to the COMPLETION and STATUS built-in functions.

IBM1599I S
The BUILTIN function variable name may not be used as a pseudovariable.
Explanation:

The named built-in function is not a pseudovariable and may not be used as one.

IBM1600I S
Source to BUILTIN name pseudovariable must be scalar.
Explanation:

It is invalid to assign an array, structure, or union to one of the built-in functions ONCHAR, ONSOURCE, or ONGSOURCE.

IBM1601I S
The identifier identifier is not the name of a built-in function. Any use of it is unsupported.
Explanation:

The BUILTIN attribute can be applied only to identifiers that are the names of built-in functions or subroutines.

IBM1602I S
Fourth argument to BUILTIN name built-in must have the attributes REAL FIXED BIN(31,0).
Explanation:

This applies to the PLISRTx built-in functions. For instance, in the following example, rc should be declared as fixed bin(31), not fixed bin(15).

 
 
    dcl rc fixed bin(15);
 
    call plisrta( ’SORT FIELDS=(1,80,CH,A) ’,
                  ’RECORD  TYPE=F,LENGTH=(80) ’,
                  256000,
                  rc );
 
IBM1603I S
BUILTIN name argument must not have the CONSTANT attribute.
Explanation:

This applies to the ADDR and similar built-in functions. It is invalid, for instance, to apply the ADDR built-in function to a label constant.

IBM1604I S
BUILTIN function argument must be nonnegative.
Explanation:

The argument for the built-in functions LOW and HIGH must be zero or greater.

IBM1605I S
Argument to ENTRYADDR built-in must be an ENTRY variable or an EXTERNAL ENTRY constant.
Explanation:

The ENTRYADDR built-in function cannot be applied to non-ENTRYs or to INTERNAL ENTRY constants.

IBM1606I S
Argument to variable name pseudovariable must be a reference.
Explanation:

Pseudovariables cannot be applied to expressions.

 
 
    unspec( 12 ) = ’00’b4;
 
IBM1607I S
First argument to variable name pseudovariable must be a reference.
Explanation:

The SUBSTR pseudovariable cannot be applied to expressions.

 
 
    substr( ’nope’, 1, 1 ) = ’d’;
 
IBM1608I S
Argument to variable name pseudovariable must be a scalar.
Explanation:

The compiler does not support the named pseudovariable applied to arrays, structures, or unions.

IBM1609I S
First argument to variable name pseudovariable must be a scalar.
Explanation:

The compiler does not support the named pseudovariable applied to arrays, structures, or unions.

IBM1610I S
Argument to variable name pseudovariable must be COMPLEX.
Explanation:

The REAL and IMAG pseudovariable can be applied only to COMPLEX arithmetic variables.

IBM1611I S
First argument to SUBSTR pseudovariable must have string type.
Explanation:

The SUBSTR pseudovariable cannot be applied to numeric variables or to noncomputational values.

IBM1612I S
Argument to the ENTRYADDR pseudovariable must be an ENTRY variable.
Explanation:

The ENTRYADDR pseudovariable can be applied only to ENTRY variables.

IBM1613I S
Argument to BUILTIN name built-in has attributes that conflict with file attribute.
Explanation:

The indicated built-in function cannot be applied to file constants with attributes that conflict with the indicated attribute.

IBM1614I S
Argument to BUILTIN name built-in has attributes that conflict with STREAM.
Explanation:

The indicated built-in function cannot be applied to non-STREAM files.

IBM1615I S
Argument to BUILTIN name built-in has attributes that conflict with PRINT.
Explanation:

The indicated built-in function cannot be applied to non-PRINT files.

IBM1616I S
Attributes and ENVIRONMENT options for file file name conflict.
Explanation:

Specified file attributes and ENVIRONMENT options on a declaration statement are in conflict. The following DECLARE statement is an example of this type of conflict:

 
  dcl file f1 direct env(consecutive);
IBM1617I S
DIRECT attribute for file file name needs ENVIRONMENT option specification of INDEXED, REGIONAL, RELATIVE, or VSAM.
Explanation:

Use of the DIRECT file attribute needs an ENVIRONMENT option specification of INDEXED, REGIONAL, RELATIVE, or VSAM.

 
  dcl file f1 direct env(relative);
IBM1618I S
Syntax of the %INCLUDE statement is incorrect.
Explanation:

%INCLUDE must be followed by a name and either a semicolon or else a second name in parenthesis and then a semicolon.

IBM1619I S
File specification after %INCLUDE is too long.
Explanation:

The maximum length of the file specification is 8 characters.

IBM1620I S
File specification missing after %INCLUDE.
Explanation:

%INCLUDE must be followed by a file name, not just a semicolon.

IBM1621I S
NODESCRIPTOR attribute is invalid if any parameters have bit alignment.
Explanation:

If a parameter is an unaligned bit string or an array or structure consisting entirely of unaligned bit strings, then OPTIONS(NODESCRIPTOR) must not be specified or implied.

IBM1622I S
The number of elements and dimension specifications in an aggregate must not exceed 131071.
Explanation:

Aggregates with more than 131071 elements and dimension specifications would require descriptors that would require too much storage.

IBM1623I S
The dot-qualified reference reference name is unknown.
Explanation:

The named reference is not a member of any structure or union declared in the block in which it is referenced or declared in any block containing that block.

IBM1625I S
Extent must be a scalar.
Explanation:

An expression specifying an array bound, a string length or an AREA size must not be a reference to an array, a structure, or a union.

IBM1626I S
Extent must have computational type.
Explanation:

An expression specifying an array bound, a string length, or an AREA size must have numeric or string type.

IBM1627I S
Subscript expressions must be scalars.
Explanation:

An expression used as a subscript must not be an array, structure, or union reference.

IBM1628I S
Index number index number into the array variable name must have computational type.
Explanation:

Only expressions having numeric or string type may be used as subscripts.

IBM1629I S
Extents for STATIC variable are not constant.
Explanation:

Array bounds, string lengths, and AREA sizes in STATIC variables must evaluate at compile-time to constants.

IBM1630I S
Number of dimensions in arrays do not match.
Explanation:

In the assignment of one array to another, the two arrays must have the same number of dimensions.

IBM1631I S
Upper and lower bounds in arrays do not match.
Explanation:

In the assignment of one array to another, the two arrays must have the same lower and upper bound in each dimension.

IBM1632I S
Index number index number into the variable variable name is less than the lower bound for that dimension.
Explanation:

Executing such a program would most likely cause a protection exception.

 
 
    dcl a(5:10)  fixed bin(31);
 
    a(1) = 0;
 
IBM1633I S
Index number index number into the variable variable name is greater than the upper bound for that dimension.
Explanation:

Executing such a program would most likely cause a protection exception.

 
 
    dcl a(5:10)  fixed bin(31);
 
    a(20) = 0;
 
IBM1634I S
Number of dimensions in subelements of structures do not match.
Explanation:

In structure assignments and structure expressions, all subelements that are arrays must have the same number of dimensions.

 
 
    dcl
      1 a,
        2 b(8)     fixed bin,
        2 c        char(10);
 
    dcl
      1 x,
        2 y(8,9)   fixed bin,
        2 z        char(10);
 
    a = x;
 
IBM1635I S
Upper and lower bounds in subelements of structures do not match.
Explanation:

In structure assignments and structure expressions, all subelements that are arrays must have the same bounds.

 
 
    dcl
      1 a,
        2 b(8)     fixed bin,
        2 c        char(10);
 
    dcl
      1 x,
        2 y(9)     fixed bin,
        2 z        char(10);
 
    a = x;
 
IBM1636I S
Substructuring in subelements of structures do not match.
Explanation:

In structure assignments and structure expressions, if any element of one structure is itself a structure, then the corresponding element in all the other structures must also be a similar structure.

IBM1637I S
Number of subelements in structures do not match.
Explanation:

In structure assignments and structure expressions, all structures must have the same number of elements.

IBM1638I S
Structures and unions are not permitted in GENERIC descriptions.
Explanation:

Only scalars and arrays of scalars are permitted in GENERIC descriptions.

IBM1639I S
The aggregate aggregate-name contains only noncomputational values. The aggregate will be ignored.
Explanation:

Aggregates containing no strings or arithmetic variables cannot be used in PUT or GET statements.

IBM1640I S
The aggregate aggregate-name contains one or more unions and cannot be used in stream I/O.
Explanation:

Aggregates containing one or more UNION statements cannot be used in PUT or GET statements.

IBM1641I S
References to slices of the array of structures structure-name are not permitted.
Explanation:

An array of structures must be referenced in its entirety or element by element.

 
 
    dcl
      1 a(8,9),
        2 b        fixed bin,
        2 c        char(10);
 
    a(2,*) = 0;
 
IBM1642I S
References to slices of the array of unions union-name are not permitted.
Explanation:

An array of unions must be referenced in its entirety or element by element.

 
 
    dcl
      1 a(8,9) union,
        2 b        fixed bin,
        2 c        char(10);
 
    a(2,*) = 0;
 
IBM1643I S
Each dimension of an array must contain no more than 2147483647 elements.
Explanation:

It must be possible to compute the value of the DIMENSION built-in function for an array. In DECLARE x(x:y), ( y-x+1) must be less than 214748648.

IBM1644I S
Aggregate contains more than 15 logical levels.
Explanation:

The maximum physical level allowed is 255, but the maximum logical level is 15.

IBM1645I S
Data aggregate exceeds the maximum length.
Explanation:

Aggregates containing unaligned bits must be less than 2**28 bytes in size while all other aggregates must be less than 2**31.

IBM1646I S
SIZE would be raised in assigning TO value to control variable.
Explanation:

If the TO value is bigger than the maximum value that a FIXED or PICTURE variable can hold, then a loop dominated by that variable would cause SIZE to be raised. For example, in the first code fragment below, x can not be assigned a value bigger than 99. In the second code fragment below, y can not be assigned a value bigger than 32767.

 
 
     dcl x pic’99’;
 
     do x = 1 to 100;
       put skip list( x );
     end;
 
     dcl y fixed bin(15);
 
     do y = 1 to 32768;
       put skip list( y );
     end;
 
IBM1647I S
Too few subscripts specified for the variable variable name.
Explanation:

The number of subscripts given for a variable must match that variable’s number of dimensions

IBM1648I S
Too many subscripts specified for the variable variable name.
Explanation:

The number of subscripts given for a variable must match that variable’s number of dimensions

IBM1649I S
The number of inherited dimensions plus the number of member dimensions exceeds 15.
Explanation:

Arrays with more than 15 dimensions are not supported.

 
 
    dcl
      1 dim7(2,3,4,5,6,7,8),
        2 dim7more(2,3,4,5,6,7,8)
          3 dim2many(2,3)  fixed bin,
          3 *              fixed bin,
        2 *  char(10);
 
IBM1650I S
The LIKE reference is neither a structure nor a union.
Explanation:

The LIKE reference cannot be a scalar or an array of scalars.

 
 
    dcl
      a fixed bin,
      1 b like a;
 
IBM1651I S
The LIKE reference is ambiguous.
Explanation:

The LIKE reference needs enough qualification to be unique.

 
 
    dcl
      1 x like b,
      1 a,
        2 b,
          3 c,
          3 d,
        2 e,
          3 f,
          3 g,
      1 h,
        2 b,
          3 j,
          3 k;
 
IBM1652I S
Neither the LIKE reference nor any of its substructures can be declared with the LIKE attribute.
Explanation:

LIKE from LIKE is not supported.

 
 
    dcl
      1 a,
        2 b1 like c,
        2 b2 like c,
      1 c,
        2 d fixed bin,
        2 e fixed bin;
    dcl
      1 x like a;
 
IBM1653I S
The LIKE reference must not be a member of a structure or union declared with the LIKE attribute.
Explanation:

LIKE from LIKE is not supported.

 
 
    dcl
      1 a,
        2 b1 like c,
        2 b2 like c,
      1 c,
        2 d fixed bin,
        2 e fixed bin;
    dcl
      1 x like a.b1;
 
IBM1654I S
The LIKE reference is unknown.
Explanation:

The LIKE reference must be known in the block containing the LIKE attribute specification.

IBM1655I S
Only CONTROLLED variables can be passed to CONTROLLED parameters.
Explanation:

If a parameter is declared as controlled, non-controlled variables and expressions with operators cannot be passed to it.

 
   dcl c char(20);
 
   call a(c);
 
   a: proc( b );
     dcl b controlled char(*);
IBM1656I S
A CONTROLLED variable passed to a CONTROLLED parameter must have the same attributes as that parameter.
Explanation:

Differences in any arithmetic attributes are not permitted. The following example will emit this message.

 
   dcl x fixed bin(15) controlled;
 
   call a(x);
 
   a: proc( b );
     dcl b controlled fixed bin(31);
IBM1657I S
A subscript has been specified for the non-array variable variable name.
Explanation:

Subscripts are permitted only in array element references.

IBM1658I S
Argument number argument-number in ENTRY reference ENTRY name is an array expression requiring a temporary array with strings of unknown length.
Explanation:

Temporary arrays of strings are supported only if the string length is known.

 
 
    dcl a entry, (b(10),c(10)) char(20) var;
 
    call a( b || c );
 
IBM1659I S
After LIKE expansion, aggregate would contain more than 15 logical levels.
Explanation:

The total number of logical levels after LIKE expansion must not exceed 15.

IBM1660I S
The size ( record-size ) of the record conflicts with the RECSIZE ( recsize ) specified in the ENVIRONMENT attribute.
Explanation:

Execution of the statement would raise the RECORD condition.

 
 
    dcl datei       file record output
                    env( fb recsize (80) total );
 
    dcl satzaus     char (100);
 
    write file(datei) from(satzaus);
 
IBM1661I S
Aggregates cannot be assigned to scalars.
Explanation:

Only scalars can be assigned to scalars.

IBM1662I S
Unsupported use of union or structure containing a union.
Explanation:

Unions and structures containing unions may not be used in expressions except when used as an argument to a built-in function such as ADDR or UNSPEC.

IBM1663I S
Unsupported or invalid use of structure expression.
Explanation:

Structure expressions may not, for instance, be assigned to arrays of scalars.

IBM1664I S
Array expressions cannot be assigned to non-arrays.
Explanation:

Array expressions may not, for instance, be assigned to structures or scalars.

IBM1665I S
E15 sort exit routines must have the RETURNS attribute.
Explanation:

An E15 sort exit have the RETURNS attribute since it will be invoked as a function by the sort library routine.

IBM1666I S
E15 sort exit routines must return a CHARACTER string.
Explanation:

An E15 sort exit may return a NONVARYING, VARYING or VARYINGZ CHARACTER string, but it must be a character string.

IBM1667I S
Target in assignment is NONASSIGNABLE.
Explanation:

The target in an assignment statement must not have the NONASSIGNABLE attribute.

IBM1668I S
Target in assignment is a function reference.
Explanation:

The target of an assignment statement must be an array, structure, union or scalar reference. Function references are not permitted as target of assignments.

IBM1669I S
Target in assignment is a UNION.
Explanation:

Assignments to UNIONs are not supported.

IBM1670I S
A PROCEDURE containing ENTRY statements with differing RETURNS attributes must return values BYADDR.
Explanation:

In a PROCEDURE containing ENTRY statements, if the PROCEDURE and ENTRY statements do not all have the same RETURNS attributes, then all values must be returned BYADDR. You can compile with DFT(RETURNS(BYADDR)) to force this, or you can add the BYADDR attribute to each set of RETURNS attribute. For example, you must either compile the following program with DFT(RETURNS(BYADDR)) or change the "fixed bin" to "fixed bin byaddr".

 
 
    a: proc;
      return;
    b: entry returns( fixed bin );
      return( 1729 );
    end;
 
IBM1671I S
The source in a structure assignment must be a scalar expression or a matching structure.
Explanation:

The source in a structure assignment cannot be an array of scalars or a structure that does not match the target.

IBM1672I S
In multiple BY NAME assignments, if one target is an array of structures, then all must be.
Explanation:

A BY NAME assignment may have not have a mixture of array and non-array targets.

 
 
    dcl 1 a, 2 a1 fixed bin, 2 a2 fixed bin;
    dcl 1 b(3), 2 a1 fixed bin, 2 a2 fixed bin;
    dcl 1 c, 2 a1 fixed bin, 2 a2 fixed bin;
 
    a,b = c, by name;
 
IBM1673I S
The target in a compound concatenate and assign must be a VARYING or VARYINGZ string.
Explanation:

Only the simple assignment operator can be used to assign to a NONVARYING string.

IBM1674I S
Target in assignment contains UNIONs.
Explanation:

The target in an assignment must not contain any UNIONs.

IBM1675I S
FROMALIEN option cannot be used with MAIN.
Explanation:

These two options are mutually exclusive.

IBM1676I S
Source in assignment to LIMITED ENTRY must be either a non-nested ENTRY constant or another LIMITED ENTRY.
Explanation:

ENTRY constants representing nested procedures and ENTRY variables not declared with the LIMITED attribute cannot be assigned to variables with the attributes LIMITED ENTRY.

IBM1677I S
Assignment of ENTRY to target type is invalid. If the ENTRY should be invoked, an argument list must be provided.
Explanation:

An ENTRY constant or variable without an argument list will not be invoked and hence can be assigned only to an ENTRY variable.

IBM1678I S
Assignment of source type to target type is invalid.
Explanation:

The target attributes conflict with the source attributes.

IBM1679I S
Assignment of POINTER to OFFSET is invalid unless the OFFSET is declared with an AREA qualifier.
Explanation:

POINTER expressions can be converted to OFFSET only if the OFFSET is declared with an AREA qualifier.

IBM1680I S
Assignment of OFFSET to POINTER is invalid unless the OFFSET is declared with an AREA qualifier.
Explanation:

OFFSET variables can be converted to POINTER only if the OFFSET is declared with an AREA qualifier.

IBM1681I S
The number of preprocessor invocations specified exceeds the maximum number (25) allowed.
Explanation:

A maximum of 25 preprocessor invocations can be specified in the PP option or in combination with the MACRO option.

IBM1682I S
The target in a BY NAME assignment must be a structure.
Explanation:

The target in a BY NAME assignment cannot be an array or a scalar.

IBM1683I S
Set of matching names in the expansion of BY NAME assignment must contain either all structures or no structures.
Explanation:

For instance, in the assignment, x = y, by name, if both x and y immediately contain a member z, then either both x.z and y.z are structures or neither x.z and y.z is a structure.

IBM1684I S
Number of dimensions in the BY NAME corresponding elements variable name and variable name do not match.
Explanation:

In a BY NAME assignment, arrays with matching names must have the same number of dimensions.

 
 
    dcl
      1 a,
        2 b(4,5)  bin(31,0),
        2 c       bin(31,0);
    dcl
      1 x,
        2 b(4)    bin(31,0),
        2 c       bin(31,0);
 
    a = x, by name;
 
IBM1685I S
Upper and lower bounds in BY NAME corresponding elements variable name and variable name do not match.
Explanation:

In a BY NAME assignment, arrays with matching names must have the same lower and upper bounds.

 
 
    dcl
      1 a,
        2 b(1:5)  bin(31,0),
        2 c       bin(31,0);
    dcl
      1 x,
        2 b(0:4)  bin(31,0),
        2 c       bin(31,0);
 
    a = x, by name;
 
IBM1686I S
BY NAME assignment contains UNIONs.
Explanation:

The target structure in a BY NAME assignment must not contain any UNIONs even if no names in those UNIONs match names in the source. The source expression also must contain any unions or structures containing unions.

IBM1687I S
reserved name cannot be declared with OPTIONS other than ASM.
Explanation:

If the DLI compiler option is specified, PLITDLI cannot be declared with any OPTIONS other than OPTIONS(ASM).

IBM1688I S
reserved name cannot be declared with an entry description list.
Explanation:

If the DLI compiler option is specified, PLITDLI cannot be declared with an entry description list.

IBM1689I S
reserved name cannot be declared as a function.
Explanation:

If the DLI compiler option is specified, PLITDLI cannot be declared as a function.

IBM1690I S
OPTIONS(language-name) is not supported for functions.
Explanation:

Functions, i.e. entrys declared with the RETURNS attribute, cannot be declared with OPTIONS(ASM) or OPTIONS(COBOL).

IBM1691I S
Extents in ENTRY descriptors must be asterisks or restricted expressions with computational type.
Explanation:

In ENTRY descriptors, each array bound, string length and AREA size must be specified either with an asterisk or with a restricted expression that has computational type.

IBM1692I S
An ENTRY invoked as a function must have the RETURNS attribute.
Explanation:

There is no default RETURNS attribute.

 
 
    dcl e entry;
 
    a = e();
 
IBM1693I S
call-option option repeated in CALL statement.
Explanation:

The TASK, EVENT and PRIORITY options may be specified only once in any CALL statement.

IBM1694I S
Reference in CALL statement must not be a built-in function.
Explanation:

CALL x is invalid unless x is a built-in subroutine, an ENTRY constant, or an ENTRY variable. Built-in functions are not built-in references. For example, "Call SQRT(x)" is invalid.

IBM1695I S
Reference in CALL statement must either be a built-in subroutine or have type ENTRY.
Explanation:

CALL x is invalid unless x is a built-in subroutine, an ENTRY constant, or an ENTRY variable.

IBM1696I S
RETURN statement without an expression is invalid inside a subprocedure that specified the RETURNS attribute.
Explanation:

All RETURN statements inside functions must specify a value to be returned.

 
 
    a: proc returns( fixed bin );
 
      return;
 
IBM1697I S
RETURN statement is invalid inside a PROCEDURE that did not specify the RETURNS attribute.
Explanation:

A statement of the form RETURN(x) is valid inside only PROCEDUREs that are defined with a RETURNS attribute.

IBM1698I S
RETURN statement with an expression is invalid inside a BEGIN in a PROCEDURE that does not have the RETURNS(BYADDR) attribute.
Explanation:

A statement of the form RETURN(x) is valid inside a BEGIN block only if the PROCEDURE enclosing that BEGIN block has the RETURNS(BYADDR) attribute explicitly or by default.

IBM1699I S
Argument number argument-number in ENTRY reference ENTRY name is an aggregate. This conflicts with the BYVALUE option.
Explanation:

Arrays, structures, and unions cannot be passed BYVALUE.

IBM1700I S
Argument number argument-number in ENTRY reference ENTRY name is an AREA reference with unknown size. This conflicts with the BYVALUE option.
Explanation:

Only AREA variables with constant size can be passed BYVALUE.

IBM1701I S
Argument number argument-number in ENTRY reference ENTRY name is a string with unknown size. This conflicts with the BYVALUE option.
Explanation:

Only strings with constant size can be passed BYVALUE.

IBM1702I S
The attribute keyword attribute is invalid as a RETURNS subattribute.
Explanation:

Structures and union may not be returned.

IBM1703I S
Reference in CALL statement must not be an aggregate reference.
Explanation:

CALL references must be scalars.

 
 
    dcl ea(10) entry;
 
    call ea;
 
IBM1704I S
Too many argument lists have been specified for the variable variable name.
Explanation:

A function can have only one argument list unless it returns an ENTRY, in which case it can have only two argument lists unless the returned ENTRY returns an ENTRY, and so on.

IBM1705I S
RETURN expression with attribute source type is invalid for RETURNS options specifying the attribute target type.
Explanation:

The RETURN expression must have a type that can be converted to the type indicated in the RETURNS option.

 
 
    a: proc returns( pointer )
 
      return( 0 );
    end;
 
IBM1706I S
RETURN expression with attribute source type is invalid for RETURNS options specifying the attribute target type. If the ENTRY should be invoked, an argument list must be provided.
Explanation:

The RETURN expression must have a type that can be converted to the type indicated in the RETURNS option.

 
 
    a: proc returns( pointer )
 
      dcl f entry returns( pointer );
      return( f );
    end;
 
IBM1707I S
RETURN expression with attribute source type is invalid for RETURNS options specifying the attribute LIMITED ENTRY.
Explanation:

Only an EXTERNAL ENTRY CONSTANT, an ENTRY CONSTANT representing a non-nested PROCEDURE, or an ENTRY VARIABLE with the LIMITED attribute can be specified as the RETURNS expression in a function that returns a LIMITED ENTRY.

IBM1708I S
RETURN expression with attribute POINTER is invalid for RETURNS options specifying the attribute OFFSET since the OFFSET attribute is not declared with an AREA qualifier.
Explanation:

POINTER expressions can be converted to OFFSET only if the offset is declared with an AREA qualifier.

IBM1709I S
RETURN expression with attribute OFFSET is invalid for RETURNS options specifying the attribute POINTER since the OFFSET expression is not an OFFSET variable declared with an AREA qualifier.
Explanation:

OFFSET variables can be converted to POINTER only if the OFFSET is declared with an AREA qualifier.

IBM1710I S
ORDINAL type in RETURN expression and RETURNS option must match.
Explanation:

In a function that returns an ordinal, the ORDINAL type in any RETURN expression must be the same as returned by the function.

 
 
    a: proc returns( ordinal color );
 
      dcl i ordinal intensity;
      return( i );
    end;
 
IBM1711I S
Expression in RETURN statement must be scalar.
Explanation:

The expression in a RETURN statement must not be an array, a structure, or an union.

IBM1712I S
External name specification must be a non-null string.
Explanation:

EXTERNAL(’’) is invalid.

IBM1713I S
Function function name contains no RETURN statement.
Explanation:

Functions must contain at least one RETURN statement.

IBM1714I S
Extents in RETURNS descriptors must be constants.
Explanation:

In RETURNS descriptors, each array bound, string length, and AREA size must be specified with a restricted expression that has computational type. Unlike ENTRY descriptors, asterisks are not permitted.

IBM1715I S
Exit from an ON-unit via RETURN is invalid.
Explanation:

RETURN statements are not permitted in an ON-unit or any of its contained BEGIN blocks unless the contained block is also contained in a procedure defined in the ON-unit.

IBM1716I S
FORMAT expression must be a scalar value.
Explanation:

Expressions in FORMAT lists, including SKIP clauses, must represent scalar values.

IBM1717I S
FORMAT expression must have computational type.
Explanation:

Expressions in FORMAT lists, including SKIP clauses, must have computational type so that the expression can be converted to FIXED BIN(31).

IBM1718I S
source type is invalid as a boolean expression.
Explanation:

The expression in an IF, WHILE, UNTIL, SELECT, or WHEN clause must have computational type so that it can be converted to BIT(1).

IBM1719I S
ENTRY is invalid as a boolean expression. If an ENTRY should be invoked, an argument list must be provided.
Explanation:

The expression in an IF, WHILE, UNTIL, SELECT, or WHEN clause must have computational type so that it can be converted to BIT(1). An ENTRY cannot be used as a boolean expression. If the ENTRY is a function which should be invoked, an argument list, even if it consists only of a left and right parenthesis, must be provided.

IBM1720I S
Expression for calculating size of variable with adjustable extents is too complicated. Variable may be defined in terms of itself.
Explanation:

An expression used in calculating the size of a variable must not depend on any values that the variable may have because those values do not exist until storage can be allocated for the variable.

IBM1721I S
Expression contains too many nested subexpressions.
Explanation:

The compiler’s space for evaluating expressions has been exhausted. Rewrite the expression in terms of simpler expressions.

IBM1722I S
The number of error messages allowed by the MAXMSG option has been exceeded.
Explanation:

Compilation will terminate when the number of messages has exceeded the limit set in the MAXMSG compiler option.

IBM1723I S
Result of concatenating two literals is too long.
Explanation:

The length of the string literal produced by concatenating two string literals must not be greater than the maximum allowed for a literal with the derived string type.

IBM1724I S
Addition of source type and target type is invalid.
Explanation:

One of the operands in an addition must be computational and the other must be either computational or a locator.

IBM1725I S
Addition of source type and target type is invalid. If an ENTRY should be invoked, an argument list must be provided.
Explanation:

An ENTRY cannot be used as an arithmetic operand. If the ENTRY is a function which should be invoked, an argument list, even if it consists only of a left and right parenthesis, must be provided.

IBM1726I S
Subtraction of target type from source type is invalid.
Explanation:

The first operand in a subtraction must be computational or a locator. The second operand can be a locator only if the first is a locator. Otherwise, the second operand must be computational.

IBM1727I S
Subtraction of target type from source type is invalid. If an ENTRY should be invoked, an argument list must be provided.
Explanation:

An ENTRY cannot be used as an arithmetic operand. If the ENTRY is a function which should be invoked, an argument list, even if it consists only of a left and right parenthesis, must be provided.

IBM1728I S
Multiplication of source type by target type is invalid.
Explanation:

Both operands in a multiplication must be computational.

IBM1729I S
Multiplication of source type by target type is invalid. If an ENTRY should be invoked, an argument list must be provided.
Explanation:

An ENTRY cannot be used as an arithmetic operand. If the ENTRY is a function which should be invoked, an argument list, even if it consists only of a left and right parenthesis, must be provided.

IBM1730I S
Division of source type by target type is invalid.
Explanation:

Both operands in a division must be computational.

IBM1731I S
Division of source type by target type is invalid. If an ENTRY should be invoked, an argument list must be provided.
Explanation:

An ENTRY cannot be used as an arithmetic operand. If the ENTRY is a function which should be invoked, an argument list, even if it consists only of a left and right parenthesis, must be provided.

IBM1732I S
Unsupported use of aggregate expression.
Explanation:

Aggregate expressions are supported only as the source in an assignment statement and, with some limitations, as an argument to the ANY or ALL built-in functions.

IBM1733I S
Concatenate operands must have computational type.
Explanation:

Only expressions having string or numeric type may be concatenated.

IBM1734I S
Operand in a prefix expression is not computational.
Explanation:

The prefix operators (plus, minus, and logical not) may be applied only to expressions having string or numeric type.

IBM1735I S
AREA variables may not be compared.
Explanation:

No relational operations are defined for AREA variables.

IBM1736I S
Comparison of source type to target type is invalid.
Explanation:

Computational types can be compared only with other computational types, and non-computational types can be compared only with like non-computational types.

IBM1737I S
Comparison of ENTRY to target type is invalid. If the ENTRY should be invoked, an argument list must be provided.
Explanation:

ENTRYs can be compared only with other ENTRYs. If the ENTRY is a function which should be invoked, an argument list, even if it consists only of a left and right parenthesis, must be provided.

IBM1738I S
Comparison of source type to ENTRY is invalid. If the ENTRY should be invoked, an argument list must be provided.
Explanation:

ENTRYs can be compared only with other ENTRYs. If the ENTRY is a function which should be invoked, an argument list, even if it consists only of a left and right parenthesis, must be provided.

IBM1739I S
TASK variables may not be compared.
Explanation:

No relational operations are defined for TASK variables.

IBM1740I S
Comparison of an OFFSET to a POINTER is invalid since the OFFSET comparand is not an OFFSET variable declared with an AREA qualifier.
Explanation:

An OFFSET can be compared with a POINTER as long as the OFFSET can be converted to a POINTER. This requires that the OFFSET is declared with an AREA qualifier.

IBM1741I S
Operands in comparison have differing strong types.
Explanation:

Comparisons of strongly-typed variables are invalid unless both have the same type.

 
 
    dcl hp  handle point;
    dcl hr  handle rectangle;
 
    if hp = hr then
      ...
 
IBM1742I S
Compared ORDINALs must have the same ORDINAL type.
Explanation:

ORDINALs cannot be compared with other ORDINALs having a different ORDINAL type.

IBM1743I S
Source and target in assignment have differing strong types.
Explanation:

Assignments of strongly-typed variables are invalid unless both have the same type.

IBM1744I S
Conversion of ORDINALs is invalid unless both have the same ORDINAL type.
Explanation:

ORDINALs cannot be assigned to other ORDINALs having different ORDINAL type.

IBM1745I S
In a function that returns a strong type, the type in any RETURN expression must be the same as that returned by the function.
Explanation:

For instance, in a function that returns a typed structure, any RETURN expression must have the same structure type.

IBM1746I S
VALUE and STATIC INITIAL expressions must be constant.
Explanation:

These expressions must be reducible to a constant at compile-time.

 
 
    dcl a fixed bin static nonassignable init(0);
    dcl m fixed bin value( a );
    dcl n fixed bin static init( a );
 
IBM1747I S
Function cannot be used before the function’s descriptor list has been scanned.
Explanation:

This is a compiler restriction. Reorder the declarations and blocks in your program. For example, the following declarations should be in reverse order.

 
 
    dcl a char( csize( x, y ) );
    dcl csize entry( char(2), fixed bin )
               returns( fixed bin );
 
IBM1748I S
Extents of automatic variables must not depend on the extents of automatic variables declared later in the same block.
Explanation:

Reorder the declarations in your program. For example, the following declarations should be in reverse order.

 
 
    dcl a char( length(b) ) auto;
    dcl b char( 10 ) auto;
 
IBM1749I S
VALUE and INITIAL expressions must be scalars.
Explanation:

Aggregate expressions are not valid as INITIAL and VALUE expressions.

IBM1750I S
INITIAL attribute is invalid for the STATIC LABEL variable variable-name since it has the MEMBER attribute.
Explanation:

LABEL variables require block activation information; they cannot be initialized at compile-time. If the variable were not a member of a structure, the storage class would be changed to AUTOMATIC and an E-level message would be issued instead.

IBM1751I S
INITIAL attribute is valid for the STATIC ENTRY variable variable-name only if it has the LIMITED attribute.
Explanation:

ENTRY variables that don’t have the LIMITED attribute require block activation information, and hence they cannot be initialized at compile-time.

IBM1753I S
INITIAL attribute is invalid for the STATIC FORMAT variable variable-name.
Explanation:

FORMAT variables require block activation information, and hence they cannot be initialized at compile-time. If the variable were not a member of a structure, the storage class would be changed to AUTOMATIC and an error message would be issued instead.

IBM1754I S
An asterisk iteration factor can be applied only to the last expression in the INITIAL item list for variable-name.
Explanation:

Since an asterisk iteration factor completes the initialization of a variable, it cannot be followed by more initial values.

 
 
     dcl a(10)  fixed bin init( 1, 2, (*) 0, 8 );
 
IBM1755I S
An asterisk iteration factor cannot be used in the nested INITIAL item list for variable-name.
Explanation:

An asterisk iteration can be used only in a non-nested INITIAL item list. The following example is invalid.

 
 
     dcl a(20) fixed bin init( (2) ( 1, (*) 2 ) );
 
IBM1756I S
The scalar variable variable-name has an INITIAL list with more than one item.
Explanation:

Only arrays can have an INITIAL list with more than one element.

 
 
     dcl a  fixed bin init( 1, 2 );
 
IBM1757I S
LABEL constant in STATIC INITIAL for the variable variable-name must be in the same block as the LABEL being initialized.
Explanation:

Change the storage class to AUTOMATIC.

 
 
     lx:;
 
     subproc: proc;
 
       dcl la  static label init( lx );
 
     end;
IBM1758I S
Only one element in the STATIC UNION variable-name may have the INITIAL attribute.
Explanation:

If more than one element in a STATIC UNION had an INITIAL value, it would not be clear which should take precedence.

 
 
     dcl
       1 a union static,
         2 b   fixed bin(31) init( 17 ),
         2 c   fixed bin(15) init( 19 );
 
IBM1759I S
Non-null INITIAL values are not supported for the STATIC NONCONNECTED array variable-name since it has the attributes UNALIGNED BIT.
Explanation:

The only supported INITIAL values for a STATIC UNALIGNED BIT variable with inherited dimensions are bit strings equal to ’’b.

 
 
     dcl
       1 a(10,2) static,
         2 b1  bit(1) init( (20) ’1’b ),
         2 b2  bit(1) init( (20) ’0’b );
 
IBM1760I S
LABEL constant in the STATIC INITIAL list for variable-name must not be an element of a LABEL CONSTANT array.
Explanation:

Replace the subscripted LABEL with an unsubscripted one or change the storage class to AUTOMATIC.

 
 
     lx(1):;
     lx(2):;
 
     dcl la(2) static label init( lx(2), lx(1) );
IBM1761I S
ENTRY reference in INITIAL clause for the STATIC ENTRY variable variable-name must not be FETCHABLE.
Explanation:

The variable y in DCL x ENTRY LIMITED INIT(y) must not be FETCHABLE; y must not be used in a FETCH or RELEASE statement, and y must not have the OPTIONS(FETCHABLE) attribute.

IBM1762I S
INITIAL iteration factor must have computational type.
Explanation:

Iteration factors in INITIAL lists must have numeric or string types.

IBM1763I S
INITIAL iteration factor must be a scalar.
Explanation:

An iteration factor in an INITIAL list must not be an array, structure, or union.

IBM1764I S
The BYVALUE attribute is invalid for strings of nonconstant length.
Explanation:

Strings with nonconstant length must be passed and received by address.

 
 
    a: proc( x );
      dcl x char(*) byvalue;
 
IBM1765I S
Length of string with the VALUE attribute must be a constant or an asterisk.
Explanation:

Named strings must have a constant length or a length determined from their VALUE.

 
 
    dcl a fixed bin automatic;
    dcl s char(a) value(’variable length’);
 
IBM1766I S
VALUE for variable-name must be evaluated before its first use.
Explanation:

Named constants must be evaluated before they are used. Reorder the declarations so that each named constant is declared before its first use.

 
 
    dcl a char(n) static init( ’tooSoon’ );
    dcl n fixed bin value( 7 );
 
IBM1767I S
Control variable in DO statement must not be a named constant.
Explanation:

Named constants may not be used as control variables in DO loops.

 
 
    dcl n fixed bin value( 7 );
 
    do n = 1 to 5;
 
IBM1768I S
Control variable in DO statement must have VARIABLE attribute.
Explanation:

Constants may not be used as control variables in DO loops.

 
 
    dcl ex external entry, (ev1, ev2) entry;
 
    do ex = ev1, ev2;
 
IBM1769I S
Control variable has type POINTER, but TO expression does not.
Explanation:

If the control variable in a DO loop has POINTER type, the TO expression must have POINTER type. Implicit conversion from OFFSET to POINTER is not supported in this context.

IBM1770I S
Control variable in loop with TO clause must have computational or locator type.
Explanation:

In a DO loop with a TO clause, the control variable must have a type that allows a comparison of less than and greater than. This is possible only for computational and locator types.

IBM1771I S
The variable name BUILTIN function may be used as a pseudovariable in a DO-loop only if the length of the pseudovariable reference is known at compile time.
Explanation:

SUBSTR and UNSPEC may be used as pseudovariables in DO-loops only if their derived length is known at compile time.

IBM1772I S
Source in DO loop initialization must be scalar.
Explanation:

In a DO loop of the form DO a = b TO c, b must be a scalar.

IBM1773I S
Control variable in DO statement must be a scalar.
Explanation:

In a DO loop of the form DO x = .., x must be a scalar.

IBM1774I S
Compiler restriction: control variable in DO statement must not be a BASED or CONTROLLED string or area that has non-constant extent.
Explanation:

In a DO loop of the form DO x = .., if x is a string or an area, then it must have constant size or must be static, automatic, or defined.

IBM1775I S
BY expression must have computational type.
Explanation:

The expression in the BY clause of a DO loop must have a string or numeric type. It cannot have a locator type because it must be comparable to zero.

IBM1776I S
BY expression must not be COMPLEX.
Explanation:

The expression in the BY clause of a DO loop must be REAL.

 
 
    dcl z cplx float;
 
    do jx = 1 to 10 by z;
 
IBM1777I S
TO expression must not be COMPLEX.
Explanation:

The expression in the TO clause of a DO loop must be REAL

 
 
    dcl z cplx float;
 
    do jx = 1 to z;
 
IBM1778I S
Control variable in loop with TO clause must not be COMPLEX.
Explanation:

In a DO loop with a TO clause, the control variable must have a type that allows a comparison of less than and greater than. This is possible for numeric types only if the numeric type is REAL.

IBM1779I S
TO expression must have computational type.
Explanation:

The expression in the TO clause of a DO loop must have a string or numeric type.

IBM1780I S
SIGNAL ANYCONDITION is invalid.
Explanation:

ON ANYCONDITION may be used to trap conditions not otherwise trapped, but ANYCONDITION may not be signalled.

IBM1781I S
And, or and exclusive-or of source type and target type is invalid.
Explanation:

Bitwise operands must have a computational type.

IBM1782I S
And, or and exclusive-or of source type and target type is invalid. If an ENTRY should be invoked, an argument list must be provided.
Explanation:

An ENTRY cannot be used as a bitwise operand. If the ENTRY is a function which should be invoked, an argument list, even if it consists only of a left and right parenthesis, must be provided.

IBM1783I S
BASED variable without an implicit qualifier must be explicitly qualified.
Explanation:

A variable declared as BASED instead of as BASED( reference ) must always be explicitly qualified. This is necessary even when the variable is an argument to built-in functions such as STORAGE.

IBM1784I S
The ENTRY variable-name may not be used as a locator qualifier since it does not have the RETURNS attribute.
Explanation:

Functions, but not subprocedures, can be used as locator qualifiers (and then only if they return a locator).

IBM1785I S
The variable variable-name is used as a locator qualifier, but it is not a scalar.
Explanation:

Only scalars can be used as locator qualifiers.

IBM1786I S
BUILTIN name built-in may not be used as a locator qualifier.
Explanation:

The named built-in function cannot be used as a locator qualifier since it does not return a POINTER.

IBM1787I S
The ENTRY variable-name may not be used as a locator qualifier.
Explanation:

x(...)->y is invalid unless x returns a POINTER or an OFFSET declared with a qualifying AREA.

IBM1789I S
The qualifier variable-name does not have locator type.
Explanation:

Only POINTERs and OFFSETs declared with a qualifying AREA can be used as locator qualifiers.

IBM1790I S
Locator qualification is invalid for variable-name.
Explanation:

Locator qualification is valid only for BASED variables.

IBM1791I S
The locator qualified reference reference name is ambiguous.
Explanation:

All references must be unambiguous.

IBM1792I S
The locator qualified reference reference name is unknown.
Explanation:

Locator qualified references must be explicitly declared. BASED variables may not be implicitly declared.

IBM1793I S
The variable name BUILTIN function may not be used as a pseudovariable in a DO-loop.
Explanation:

Only IMAG, REAL, SUBSTR and UNSPEC may be used as pseudovariables in DO loops.

IBM1794I S
Too many implicit locators are needed to resolve the qualification for a variable. Variable may be based on itself.
Explanation:

An implicitly qualified variable must require no more than 15 qualifiers to be completely qualified. If it requires more, this may indicate its qualifiers are too interdependent.

 
 
    dcl a pointer based(b);
    dcl b pointer based(a);
    a = null();
IBM1795I S
The OFFSET variable variable-name may not be used as a locator qualifier since it was not declared with an AREA specification.
Explanation:

An OFFSET variable can be used as a locator qualifier only if it can be converted to a pointer value. This requires that the offset be declared with an AREA qualification.

IBM1796I S
Qualifier must be a scalar.
Explanation:

Arrays, structures, and unions may not be used as locator qualifiers.

IBM1797I S
BASED variables may not contain extents with nonconstant values if other extents use the REFER option.
Explanation:

The REFER option cannot be used in a BASED variable which also has an extent that is set by a non-constant expression.

IBM1798I S
Invalid scale factor in PICTURE specification.
Explanation:

The picture character F specifies a picture scaling factor for fixed-point decimal numbers. The number of digits following the V picture character, minus the integer specified with F, must be between -128 and 127.

IBM1799I S
Invalid characters in PICTURE specification.
Explanation:

The picture specification can contain only A X 9 for the Character Data, and only 9 V Z * , . / B S + - $ CR DB Y K E F < > for the Numeric Data. The characters between the insertion characters < > are not affected by this rule.

IBM1800I S
Invalid characters in the F scaling factor.
Explanation:

The picture character F specifies a picture scaling factor for fixed-point decimal numbers. The format is F(n) where n can be any signed integer between -128 and 127 inclusively.

IBM1801I S
A character PICTURE string may have only A, X, or 9.
Explanation:

The picture specification can contain only A, X, or 9 for the character data. Other characters are not permitted.

IBM1802I S
Invalid precision in PICTURE fixed decimal precision.
Explanation:

The number of digits for the precision field within a numeric data picture specification must be between one and the maximum allowed by the LIMITS(FIXEDDEC) option.

IBM1803I S
Too many T, I, or R appear in the PICTURE specification.
Explanation:

T, I, or R are the overpunched characters in the picture specification. Only one overpunched character can appear in the specification for a fixed point number. A floating-point specification can contain two (One in the mantissa field and one in the exponent field).

IBM1804I S
PICTURE specifications in C-format items must be arithmetic.
Explanation:

Character PICTURE specifications are not permitted in C-format items.

IBM1805I S
Precision in numeric PICTURE must NOT be less than 1.
Explanation:

The precision field within a numeric data picture specification must contain at least one digit.

IBM1806I S
The precision in FIXED DECIMAL PICTURE is too big.
Explanation:

The precision in the fixed decimal picture specification must not exceed that specified in the LIMITS compiler option.

IBM1807I S
Precision in FLOAT DECIMAL PICTURE is too big.
Explanation:

The precision in the float decimal picture specification is limited by the hardware to 18 digits.

IBM1808I S
PICTURE string is empty.
Explanation:

Null picture strings (’’P) are invalid.

IBM1809I S
Exponent in FLOAT PICTURE is too long. Exponent will be truncated to fit.
Explanation:

The number of digits in the exponent of the float decimal picture specification is limited to 4.

IBM1810I S
Exponent in FLOAT PICTURE has no digits.
Explanation:

The exponent in the float decimal picture specification is missing. It must be entered even if it is zero.

IBM1811I S
Exponent in PICTURE specification cannot contain V.
Explanation:

V specifies an implicit decimal point. Therefore, it is not permitted in the exponent field.

IBM1812I S
FLOAT PICTURE cannot contain CR, DB or F.
Explanation:

Credit (CR), debit (DB), and scale factor (F) are only allowed in the FIXED picture specification.

IBM1813I S
PICTURE specification is too long. Excess characters are truncated on the right.
Explanation:

The compiler restrictions on the length of the picture specification are:

 
 
    fixed decimal:  254
    float decimal:  253
    character data: 511
IBM1814I S
PICTURE string has an invalid floating insertion character string.
Explanation:

The floating insertion string is delimited by < >. Floating is done by the > character. The string can contain any character with one exception: the delimiters themselves. In order to include the characters < and > in the floating insertion string, these angle brackets must be used in an escaped format. << must be used to specify the character <, and <> must be used to specify the character >. So, for example, <aaa<<bbb<>ccc> denotes the insertion string aaa<bbb>ccc.

IBM1815I S
BUILTIN name is a built-in subroutine. It should be used only in CALL statements and not as a function.
Explanation:

Built-in subroutines cannot be used as functions - they can only be called. For instance, the following code is invalid

 
 
    dcl pliretc builtin;
 
    rc = pliretc( 16 );
 
IBM1816I S
keyword item variable name is not computational.
Explanation:

The expression must be arithmetic or string.

 
   dcl x label variable;
   put list( x );
IBM1817I S
The KEYTO reference must be of type CHARACTER or GRAPHIC.
Explanation:

The KEYTO reference should have the data type character or graphic. The reference can also be a variable with a non-numeric picture string specification.

IBM1818I S
I/O-option conflicts with previous options on the I/O-stmt statement.
Explanation:

An option on the I/O statement conflicts with prior options.

 
    open file(f1) input output;
    read file(f) into(x) set(p);
IBM1819I S
The I/O-option option is multiply specified on the I/O-stmt statement.
Explanation:

Each option may be specified only once.

 
    read file(f1) ignore(1) ignore(2);
IBM1820I S
Mandatory I/O-option option not specified on the I/O-stmt statement.
Explanation:

A required statement element has not been specified.

 
   open output;
   write file(x);
IBM1821I S
Reference for from-into-option is an invalid element or aggregate type.
Explanation:

An invalid scalar or aggregate reference has been specified for the FROM or INTO clause in a record I/O statement. The example below will cause this message to be issued.

 
  dcl f1 file;
  read file(f1) into(f1);
IBM1822I S
The keyword-type expression must be computational.
Explanation:

The expression in a KEY or KEYFROM record I/O statement option must be computational data.

IBM1823I S
SET reference must have locator type.
Explanation:

In the SET clause of an ALLOCATE or LOCATE statement, the reference must have the type POINTER or OFFSET.

IBM1824I S
keyword expression must be scalar.
Explanation:

The expression in the named keyword clause must be scalar. This keyword clause could be an IF, UNTIL, WHILE, WHEN, KEY, KEYFROM or KEYTO clause.

 
   dcl f1    file;
   dcl x     char(10);
   dcl z(10) char(10);
   read file(f1) into(x) key(z);
IBM1825I S
The reference in the keyword clause cannot be a built-in function reference.
Explanation:

The references for the KEYTO, FROM, INTO, and SET record I/O options cannot be built-in functions. The example below will cause this message to be issued.

 
   dcl f1    file;
   dcl x     char(10);
   read file(f1) into(hex(x));
IBM1826I S
The reference in the keyword clause cannot be a function invocation.
Explanation:

The references for the KEYTO, FROM, INTO, and SET record I/O options cannot be entry.

IBM1827I S
The reference in the keyword clause must have CHARACTER type.
Explanation:

The specified reference is invalid. It must be of type character. The example below will cause this message to be issued.

 
   dcl p     pointer;
   display (’what is your name?’) reply(p);
IBM1828I S
The reference in the keyword clause must be a scalar variable.
Explanation:

The specified reference is invalid. It must be a scalar. The example below will cause this message to be issued.

 
   dcl z(10) char(10);
   display (’what is your name?’) reply(z);
IBM1829I S
The attributes of the argument in the clause clause conflict with its usage.
Explanation:

The declared attributes conflict with their use in the statement.

 
   dcl f file stream;
   read file(f) into(x);
IBM1830I S
keyword expression is not computational.
Explanation:

The expression must be arithmetic or string.

 
   dcl p pointer;
   put list( ptradd(p,2) );
IBM1831I S
The LOCATE reference variable-name is not implicitly qualified and is invalid without a SET clause.
Explanation:

Provide a SET clause in the LOCATE statement.

 
 
   dcl f file;
   dcl x char(10) based;
   locate x file(f1);
 
IBM1832I S
SET reference must have POINTER type.
Explanation:

The reference in the SET clause of a FETCH statement must have the POINTER type. OFFSET types are not supported in this context.

IBM1833I S
The aggregate reference in the from-into clause clause must be CONNECTED.
Explanation:

The specified reference in the FROM or INTO record I/O option is invalid. The reference must be connected. The example below will cause this message to be issued.

 
   dcl f1 file;
   dcl 1 a(3),
        2 b(4) char(4),
        2 c(4) char(4);
 
   read file(f1) into(b);
IBM1834I S
The expression in IGNORE must be computational.
Explanation:

The specified expression in the IGNORE option of the READ statement must be computational. The example below will cause this message to be issued.

 
   dcl a  area;
 
   read file(f1) ignore(a);
IBM1835I S
The LOCATE reference variable-name is not a level-1 BASED variable.
Explanation:

The LOCATE reference may not be a structure member and must have the storage attribute BASED.

IBM1836I S
INITIAL attribute is invalid for structures.
Explanation:

The INITIAL attribute is valid only for scalars and arrays of scalars.

IBM1837I S
The reference in the keyword clause cannot be a named constant.
Explanation:

The specified reference is invalid. It cannot be a named constant. The example below will cause this message to be issued.

 
   dcl f1  file;
   dcl x   char(2);
   dcl val fixed bin(15) value(4);
 
   read file(f1) into(x) keyto(val);
IBM1838I S
The attributes of argument-number conflict with its usage in data directed I/O.
Explanation:

Only AUTOMATIC, CONTROLLED, PARAMETER, STATIC and and implicitly qualified BASED variables are supported in data directed I/O.

 
   dcl q based;
   put data(q);
IBM1839I S
DATA-directed I/O does not support references with locators.
Explanation:

Use a temporary or use LIST- or EDIT directed I/O.

IBM1840I S
Subscripted references are not allowed in GET DATA.
Explanation:

Use a temporary or use GET LIST or GET EDIT.

IBM1841I S
The first argument in the keyword-format item is invalid.
Explanation:

The format argument is outside the valid range.

 
   put edit(’hi’) (a( -1) );
IBM1842I S
The field width specified in the keyword-format item is too small for complete input or output of the data item.
Explanation:

The width specified is too small for complete processing.

 
    put edit(10190) (f(3));
IBM1843I S
The fractional digits specified in the keyword-format item is invalid.
Explanation:

The fractional number of digits must be less than or equal to the field width and non-negative.

IBM1844I S
The argument in the R-format item is not a format constant or format variable.
Explanation:

The argument to the R-format item must be either a format constant or a format variable.

IBM1845I S
The significant digits specified in E-format item is invalid.
Explanation:

The number of significant digits must be greater than or equal to the number of fractional digits, less than or equal to the field width and non-negative.

IBM1846I S
The format-item format item is invalid with GET/PUT STRING.
Explanation:

G, L, PAGE, LINE, SKIP, and COLUMN format items may not be used in GET/PUT EDIT statements using the STRING option.

IBM1847I S
GOTO target is inside a (different) DO loop.
Explanation:

The target of a GOTO cannot be inside a DO loop unless the GOTO itself is in the same DO loop.

IBM1848I S
The INCLUDE file for include-stmt-arg could not be found.
Explanation:

The INCLUDE file could not be found or opened.

IBM1849I S
Under CMPAT(V1), bounds must not be greater than 32767.
Explanation:

Under CMPAT(V1), bounds must be between -32768 and 32767 inclusive. To use bounds outside this range, specify a different CMPAT option.

IBM1850I S
Under CMPAT(V1), bounds must not be less than -32768.
Explanation:

Under CMPAT(V1), bounds must be between -32768 and 32767 inclusive. To use bounds outside this range, specify a different CMPAT option.

IBM1851I S
The INCLUDE file include-file-name could not be opened.
Explanation:

An unexpected error occurred while trying to open an include source file.

IBM1852I S
The preprocessor preprocessor is not known to the compiler.
Explanation:

A preprocessor specified in the PP compiler option is unknown.

IBM1853I S
Variable in statement statement must be a FETCHABLE entry constant.
Explanation:

The argument in the FETCH and RELEASE statements must be a FETCHABLE entry constant.

IBM1854I S
Fetch of the PP name preprocessor failed with ONCODE= oncode.
Explanation:

The compiler attempted to load the module specified in the PP-DEF installation option for the preprocessor.

IBM1855I S
Preprocessor PP name terminated abnormally with ONCODE= oncode-value.
Explanation:

A terminating error was detected in a preprocessor invoked by the compiler.

IBM1856I S
Fetch of the user exit initialization routine failed with ONCODE= oncode.
Explanation:

The compiler was unable to load the user exit.

IBM1857I S
User exit routine terminated abnormally with ONCODE= oncode-value.
Explanation:

The compiler detected a terminating error in the user exit.

IBM1858I S
Compile aborted by user exit.
Explanation:

The user exit aborted the compile by setting the return code to 16.

IBM1859I S
The first statement must be a PROCEDURE or PACKAGE statement.
Explanation:

All other statements must be enclosed in a PACKAGE or PROCEDURE statement.

IBM1860I S
PACKAGE statement must be the first statement in the program.
Explanation:

PACKAGE statements cannot follow any other statements in the program.

IBM1861I S
All statements other than DECLARE, DEFAULT and PROCEDURE statements must be contained inside a PROCEDURE.
Explanation:

This message can occur, for instance, if the first PROCEDURE statement is invalid or if a PROCEDURE contains too many END statements.

IBM1862I S
Statements are nested too deep.
Explanation:

The nesting of PROCEDURE, DO, SELECT and similar statements is greater than that supported by the compiler. Rewrite the program so that it is less complicated.

IBM1863I S
Variables declared in a PACKAGE outside of any PROCEDURE must have the storage class STATIC, BASED or CONTROLLED or must be DEFINED on STATIC.
Explanation:

AUTOMATIC variables must be declared inside a PROCEDURE, and DEFINED variables declared outside a PROCEDURE must be defined on STATIC.

IBM1864I S
The function name built-in is not supported.
Explanation:

Support for the indicated built-in function has been discontinued.

IBM1865I S
The only BASED variables supported in data-directed i/o are those that have constant extents and that are implicitly qualified by simple variables.
Explanation:

The variable implicitly qualifying the BASED variable must be a scalar that is not part of an array, structure or union, and it must be a POINTER with either the AUTOMATIC or STATIC storage attribute.

IBM1866I S
The keyword statement is not supported.
Explanation:

Support for the indicated statement has been discontinued.

IBM1867I S
The pseudovariable variable name is not supported.
Explanation:

Support for the indicated pseudovariable has been discontinued.

IBM1868I S
Invalid use of iSUB.
Explanation:

iSUB references are permitted only in DEFINED clauses.

IBM1869I S
ALLOCATE with attribute lists is not supported.
Explanation:

For example, neither of the following are supported.

 
 
    allocate x(5);
    allocate y char(10);
 
IBM1870I S
ON statement cannot specify both SYSTEM and an ON-unit.
Explanation:

If the SYSTEM action is specified in an ON statement, an ON-unit may not be specified as well.

 
 
    on error system stop;
IBM1871I S
The reference in the CONDITION condition must have type CONDITION.
Explanation:

x in CONDITION(x) refers to a variable that does not have the type CONDITION.

IBM1872I S
The reference in the condition-name condition must have type FILE.
Explanation:

The reference in the named FILE condition does not have the type FILE.

IBM1873I S
Nesting of DO statements exceeds the maximum.
Explanation:

DO statements can be nested only 50 deep. Simplify the program.

IBM1874I S
Nesting of IF statements exceeds the maximum.
Explanation:

IF statements can be nested only 50 deep. Simplify the program.

IBM1875I S
Nesting of SELECT statements exceeds the maximum.
Explanation:

SELECT statements can be nested only 50 deep. Simplify the program.

IBM1876I S
Nesting of blocks exceeds the maximum.
Explanation:

Blocks may be nested only 30 deep.

IBM1878I S
The reference in the EVENT clause must have type EVENT.
Explanation:

A reference of any other type is invalid and is invalid.

IBM1879I S
The reference in the TASK clause must have type TASK.
Explanation:

A reference of any other type is invalid and is invalid.

IBM1880I S
Reference must have FILE type.
Explanation:

A file variable or constant is required.

 
   dcl x format variable;
   open file(x);
IBM1881I S
The reference reference name is ambiguous.
Explanation:

Enough qualification must be provided to make any reference unique.

IBM1882I S
The ALLOCATE reference variable-name is not a level-1 BASED or CONTROLLED variable.
Explanation:

References in ALLOCATE statements must be level-1 variable names, and those variables must have the BASED or CONTROLLED attributes.

IBM1883I S
The ALLOCATE reference variable-name is not implicitly qualified and is invalid without a SET clause.
Explanation:

Provide a SET clause in the ALLOCATE statement.

 
 
    dcl a based;
 
    allocate a;
 
IBM1884I S
The reference variable-name in the GENERIC attribute list is not a scalar ENTRY reference.
Explanation:

A reference of any other type is invalid.

IBM1885I S
IN option reference must have AREA type.
Explanation:

A reference of any other type is invalid.

IBM1886I S
The REFER object name reference name is ambiguous.
Explanation:

Provide enough qualification to make the name unique.

 
 
    dcl
      1 a based,
        2 b1,
          3 c        bit(8) aligned,
          3 d        char(10),
        2 b2,
          3 c        bit(8) aligned,
          3 d        char(10),
        2 e( n refer(c)) char(10);
 
IBM1887I S
The REFER object reference name must be an element of the same structure where it is used, and must precede its first usage in that structure.
Explanation:

The named REFER object cannot be declared in another structure or in the same structure, but after its first usage.

IBM1888I S
The REFER object reference name must have computational type.
Explanation:

It must be possible to convert the REFER object safely to and from REAL FIXED BIN(31,0).

 
 
    dcl
      1 a based,
        2 b,
          3 c        pointer,
          3 d        char(10),
        2 e( n refer(c)) char(10);
 
IBM1889I S
The REFER object reference name must be a scalar.
Explanation:

The REFER object may not have any dimensions in its declaration and neither may any of its parents.

 
 
    dcl
      1 a based,
        2 b(8),
          3 c        fixed bin,
          3 d        char(10),
        2 e( n refer(c)) char(10);
 
IBM1890I S
The REFER object reference name must precede the first level-2 element containing a REFER.
Explanation:

Reorder the elements in the declaration so that all REFER objects precede the first level-2 element containing a REFER.

 
 
    dcl
      1 a based,
        2 b        fixed bin,
        2 c        char( n refer(b) ),
        2 d        fixed bin,
        2 e        char( n refer(d) );
 
IBM1891I S
REFER is not allowed on non-BASED variables.
Explanation:

REFER can be used only in declarations of BASED variables.

IBM1892I S
The REFER object reference name must have constant length.
Explanation:

If a REFER object is a string, it must have constant length.

IBM1893I S
REFER is allowed only on members of structures and unions.
Explanation:

REFER cannot be used only in declarations of scalars or arrays of scalars.

IBM1894I S
FREE references must not be subscripted.
Explanation:

In the statement FREE x, x must not have any subscripts or arguments.

IBM1895I S
Operations involving OPTIONS(language-name) routines are not supported if the DIRECTED option applies.
Explanation:

If the DIRECTED(ASM) option is used, comparisons and assignments are not supported for ENTRYs declared with OPTIONS(ASM). Similarly, if the DIRECTED(COBOL) option is used, comparisons and assignments are not supported for ENTRYs declared with OPTIONS(COBOL).

IBM1896I S
OPTIONS(language-name) is not supported for ENTRY VARIABLEs if the DIRECTED option applies.
Explanation:

If the DIRECTED(ASM) option is used, ENTRY VARIABLES may not be declared with OPTIONS(ASM). Similarly, if the DIRECTED(COBOL) option is used, ENTRY VARIABLES may not be declared with OPTIONS(COBOL).

IBM1897I S
Simple defining is supported only for scalars, for structures with constant extents matching those in the base variable, and for arrays of such scalars and structures as long as the array is not based on a controlled variable.
Explanation:

If simple defining is not intended, specify POSITION(1) to force string defining.

IBM1898I S
The base reference in the DEFINED attribute cannot be a built-in or type function.
Explanation:

You can define a variable only another user variable.

IBM1899I S
The base variable in the DEFINED attribute cannot be BASED, DEFINED or CONSTANT.
Explanation:

Convert the DEFINED and base variables into a UNION.

IBM1900I S
Extents for DEFINED bit structures must be constant.
Explanation:

All bounds and string lengths for DEFINED structures and unions consisting of bit strings must be constant.

IBM1901I S
POSITION attribute is invalid without the DEFINED attribute.
Explanation:

The POSITION attribute has no meaning without DEFINED attribute.

IBM1902I S
The expression in the POSITION attribute must have computational type.
Explanation:

The POSITION expression must have a numeric or string type.

IBM1903I S
The expression in the POSITION attribute for bit string-overlay defining must be an integer constant.
Explanation:

The compiler must be able to evaluate the expression to an integer constant when it scans the POSITION attribute.

IBM1904I S
Variable following the free clause clause must be level-1 and either BASED or CONTROLLED.
Explanation:

A variable that is either based or controlled should immediately follow the FREE keyword.

IBM1905I S
IN or SET option option invalid after the CONTROLLED variable in the ALLOCATE or FREE clause clause.
Explanation:

An invalid option immediately follows a controlled variable in an ALLOCATE or FREE statement.

IBM1906I S
The reference qualifying an OFFSET attribute must be a scalar AREA reference.
Explanation:

Using the specified AREA reference to qualify an OFFSET variable is invalid. The reference must be scalar. The following example will issue this message.

 
   dcl a(10) area;
   dcl o     offset(a);
IBM1907I S
Extents for CONTROLLED variables cannot be specified using asterisks or REFER.
Explanation:

The extent specified for the controlled variable is invalid. The following example will emit this message.

 
   dcl c(*)  char(10) controlled;
IBM1908I S
Extents for attribute variables cannot be specified using asterisks or REFER.
Explanation:

Extents for AUTOMATIC and DEFINED variables must be specified by expressions.

IBM1909I S
The attribute attribute conflicts with the attribute attribute.
Explanation:

The named attributes, for example PARAMETER and INITIAL, are mutually exclusive.

IBM1910I S
The attributes given in the declaration for identifier conflict with its use as a parameter.
Explanation:

Parameters can have no storage attributes other than CONTROLLED. Parameters also cannot have any of the attributes BUILTIN, CONDITION, CONSTANT, EXTERNAL, and GENERIC.

IBM1911I S
Repeated specifications of the unsubscripted statement label character are in error.
Explanation:

All statement labels in any block must be unique.

IBM1912I S
Indices specified for the LABEL character have already been specified.
Explanation:

All statement labels in any block must be unique.

IBM1913I S
ON-units may not be labeled. All such labels will be ignored.
Explanation:

A BEGIN block or a statement associated with an ON clause may not have a label.

IBM1914I S
GOTO target must be a LABEL reference.
Explanation:

x in GOTO x must have type LABEL. x must not have type FORMAT.

IBM1915I S
GOTO target must be a scalar.
Explanation:

x in GOTO x must not be an array.

IBM1916I S
The procedure/entry proc-name has already been defined.
Explanation:

Sister procedures must have different names.

 
 
    a: proc;
      b: proc;
      end;
      b: proc;
      end;
    end;
 
IBM1917I S
Program contains no valid source lines.
Explanation:

The source contains either no statements or all statements that it contains are invalid.

IBM1918I S
All the names in the ORDINAL ordinal-name have been previously declared.
Explanation:

None of the names in an ORDINAL should have been declared elsewhere. If they are, perhaps the ORDINAL definition has been accidentally repeated.

IBM1919I S
The EXTERNAL name string is specified for the differing internal names name and name.
Explanation:

Each EXTERNAL name must have only one INTERNAL name. So, for example, the following declares would be illegal since the external name Z is specified for two different internal names: X and Y.

 
 
    dcl X fixed bin(31) ext(’Z’);
    dcl Y fixed bin(31) ext(’Z’);
 
IBM1920I S
FIXED BINARY constant contains too many digits.
Explanation:

The maximum precision of FIXED BINARY constants is set by the FIXEDBIN suboption of the LIMITS compiler option.

IBM1921I S
FIXED DECIMAL constant contains too many significant digits.
Explanation:

The maximum precision of FIXED DECIMAL constants is set by the FIXEDDEC suboption of the LIMITS compiler option.

IBM1922I S
Exponent in FLOAT BINARY constant contains more digits than the implementation maximum.
Explanation:

The exponent in a FLOAT BINARY constant may contain no more than 5 digits.

IBM1923I S
Mantissa in FLOAT BINARY constant contains more significant digits than the implementation maximum.
Explanation:

The mantissa in a FLOAT BINARY constant may contain no more than 64 digits.

IBM1924I S
Exponent in FLOAT DECIMAL constant contains more digits than the implementation maximum.
Explanation:

The exponent in a FLOAT BINARY constant may contain no more than 4 digits.

IBM1925I S
Mantissa in FLOAT DECIMAL constant contains more significant digits than the implementation maximum.
Explanation:

The mantissa in a FLOAT DECIMAL constant may contain no more than maximum number of digits allowed on the platform.

IBM1926I S
Constants must not exceed 8192 bytes.
Explanation:

The number of bytes used to represent a constant in your program must not exceed 8192. This limit holds even for bit strings where the internal representation will consume only one-eighth the number of bytes as the external representation does.

IBM1927I S
SIZE condition raised by attempt to convert source-value to target-attributes
Explanation:

The source value is not in the domain of the target.

 
 
    dcl x fixed bin(15);
    x = 172900;
 
IBM1928I S
ERROR raised while building CEEUOPT from PLIXOPT.
Explanation:

The ERROR condition was while the compiler was trying to build CEEUOPT from PLIXOPT. There may an error in the Language Environment APIs used by the compiler. Contact IBM service.

IBM1929I S
Unable to open file file-name in routine proc-name(line-number).
Explanation:

The compiler was unable to open the named temporary file used to communicate with the code generation module. Check the value of the TMP environment variable.

IBM1930I S
Unable to write to file file-name . Disk may be full.
Explanation:

The compiler was unable to write to a temporary file used to communicate with the code generation module. The disk to which the TMP environment variable points may be full.

IBM1932I S
Unable to close file file-name in routine proc-name(line-number).
Explanation:

The compiler was unable to close the named temporary file used to communicate with the code generation module. Check the value of the TMP environment variable.

IBM1933I S
Unable to open temporary files because the path and filename are too long.
Explanation:

Shorten the name of the source file or the directory specified by the TMP variable.

IBM1934I S
If a parameter is a structure with nonconstant extents, only matching structures are supported as arguments.
Explanation:

Assign the structure to a temporary and pass the temporary, or omit the parameter description in the entry declaration.

IBM1935I S
Structure expressions as arguments are not supported for undescribed parameters.
Explanation:

Assign the structure to a temporary and pass the temporary, or describe the parameter in the entry declaration.

IBM1936I S
Invocation of compiler backend ended abnormally.
Explanation:

The back end of the compiler either could not be found or else it detected an error from which it could not recover. The latter problem can sometimes occur, on Intel, if your disk is short of free space and, on the z/Series, if your job’s region size is not large enough. Otherwise, report the problem to IBM.

IBM1937I S
Extents for parameters must be asterisks or restricted expressions with computational type.
Explanation:

For parameters, each array bound, string length and AREA size must be specified either with an asterisk or with a restricted expression that has computational type.

IBM1938I S
Message file file name not found.
Explanation:

The message must be in the current directory or in one of the directories specified in the DPATH environment variable.

IBM1939I S
Exponentiation operands must have computational type.
Explanation:

The operands in an exponentiation must have numeric or string type.

IBM1940I S
note
Explanation:

This message is used by %NOTE statements with a return code of 12.

IBM1941I U
note
Explanation:

This message is used by %NOTE statements with a return code of 16.

IBM1942I S
The scale factor specified in BUILTIN name built-in must be a restricted expression with integer type.
Explanation:

This applies to all the precision-handling built-in functions.

IBM1943I S
The number of error messages allowed by the FLAG option has been exceeded.
Explanation:

Compilation will terminate when the number of messages has exceeded the limit set in the FLAG compiler option.

IBM1944I S
The precision specified in BUILTIN name built-in must be a restricted expression with integer type.
Explanation:

This applies to all the precision-handling built-in functions.

IBM1945I S
Extents for BASED variable may not contain asterisks.
Explanation:

Extents in BASED variables must be either constants or specified with the REFER option.

IBM1946I S
Reference must be an AREA variable.
Explanation:

The specified reference is invalid. An AREA variable is needed.

IBM1947I S
The reference to the GENERIC variable GENERIC variable name cannot be resolved.
Explanation:

The argument list in a GENERIC reference must match one of the generic descriptors in one of that GENERIC’s WHEN clauses. If an OTHERWISE clause was specified, the argument list must have the same number of elements as the OTHERWISE entry reference.

IBM1948I S
condition-name condition with ONCODE=oncode-value raised while evaluating restricted expression.
Explanation:

Compile-time evaluation of a restricted expression raised a condition.

 
 
    display( 1/0 );
 
IBM1949I S
Parameter name identifier appears more than once in parameter list.
Explanation:

Each identifier in a parameter list must be unique.

 
 
    a: proc( b, c, b );
 
IBM1951I S
storage class variables must be named.
Explanation:

Variables with the CONTROLLED attribute must be named, and a variable with the EXTERNAL attribute may not have an * instead of a name unless a name is given with the EXTERNAL attribute itself.

IBM1952I S
INITIAL CALL cannot be used to initialize STATIC data.
Explanation:

An INITIAL CALL must be evaluated at run-time; it can be used to initialize only non-STATIC data.

IBM1953I S
The attributes of the EXTERNAL variable variable name do not match those in its previous declaration.
Explanation:

EXTERNAL variables can be declared in more than one procedure in a compilation unit, but the attributes in those declarations must match.

IBM1954I S
The base reference in the DEFINED attribute must be CONNECTED.
Explanation:

Variables cannot be DEFINED on NONCONNECTED references.

IBM1955I S
Repeated declarations of the EXTERNAL attribute variable name are not supported.
Explanation:

EXTERNAL FILE constants and CONDITIONs may be declared only once in a compilation unit. Remove all but the outermost declare.

IBM1956I S
ITERATE is valid only for iterative DO-groups.
Explanation:

ITERATE is not valid inside type-I do groups.

IBM1957I S
The WAIT event number specification must be computational.
Explanation:

The expression representing the number of items to wait for in a WAIT statement is invalid. The expression must be of computational type. The following example will issue this message.

 
   dcl e event;
   dcl p pointer:
   wait (e) (p);
IBM1958I S
References in the WAIT statement must be of type EVENT.
Explanation:

The event reference in the WAIT statement is invalid. It must be of type EVENT. The following example will issue this message.

 
   dcl e entry;
   wait (e);
IBM1959I S
Invalid aggregate expression specified in WAIT statement.
Explanation:

References in WAIT statements can be scalars. The only valid aggregate reference is a simple array of events. Structures, unions, and arrays of structures or unions would be flagged as as errors.

IBM1960I S
type type type type name is not defined.
Explanation:

If ORDINAL x is used in a declaration, x must be a defined ORDINAL type.

IBM1961I S
INITIAL values for type type type type name must be in increasing order.
Explanation:

Any values specified in INITIAL clauses in an ORDINAL definition must be in strictly increasing order.

IBM1962I S
INITIAL values for type type type type name must be less than 2G.
Explanation:

ORDINAL values must fit in the range of a FIXED BIN(31) variable.

IBM1963I S
BUILTIN name argument must have ORDINAL type.
Explanation:

An expression contains the named built-in function with an argument that is not an ORDINAL. This message applies, for example, to the ORDINALNAME, ORDINALPRED and ORDINALSUCC built-in functions.

IBM1964I S
The attributes derived from the PROCEDURE statement for the ENTRY constant variable name do not match those in its explicit declaration.
Explanation:

A label on a PROCEDURE statement constitutes a declaration for an ENTRY constant with that name. That name also appears in a DECLARE statement, but the attributes in those two declarations do not match.

IBM1965I S
There is more than one element named reference name in the class structure name.
Explanation:

All references must be unambiguous.

IBM1966I S
There is no element named reference name in the class structure name.
Explanation:

HANDLE qualified references must be explicitly declared.

IBM1967I S
The ENTRY variable-name may not be used as a handle since it does not have the RETURNS attribute.
Explanation:

Functions, but not subprocedures, can be used as handles (and then only if they return a handle).

IBM1968I S
The ENTRY variable-name may not be used as a handle.
Explanation:

x(...)=>y is invalid unless x returns a HANDLE.

IBM1969I S
The variable variable-name is used as a handle, but it is not a scalar.
Explanation:

Only scalars can be used as handles.

IBM1970I S
BUILTIN name built-in may not be used as a handle.
Explanation:

The named built-in function cannot be used as a handle.

IBM1971I S
The GENERIC variable variable-name may not be used as a handle.
Explanation:

GENERIC references may not be used as handles.

IBM1972I S
variable-name may not be used as a handle.
Explanation:

x=>y is invalid unless x has the HANDLE attribute

IBM1976I S
DBCS characters are allowed only in G and M constants.
Explanation:

Hex strings (strings ending in one of the suffixes X, BX, B4, GX or XN), bit strings, (strings ending in the suffix B), and character strings not ending in the suffix M must contain only SBCS characters.

IBM1977I S
SBCS characters are not allowed in G constants.
Explanation:

Mixed SBCS and DBCS is allowed only in M constants.

IBM1978I S
Invalid use of SBCS encoded as DBCS.
Explanation:

Outside of comments, SBCS can be encoded as DBCS only as part of an identifier.

IBM1981I S
BUILTIN function may not be used outside a procedure.
Explanation:

The named built-in function may be used only inside procedures.

IBM1984I S
File filename could not be opened.
Explanation:

The named file could not be opened. Make sure that the file is named correctly, that it exists, that it has the proper attributes and that you have the needed permissions to access it.

IBM1985I S
File filename could not be found.
Explanation:

The file does not exist in the current directory, in the path specified by the appropriate environment variable. Check to see that the file name was entered correctly.

IBM1986I S
The path for file filename could not be found.
Explanation:

The path does not exist for the drive specified, or the path was entered incorrectly.

IBM1987I S
File filename could not be opened because too many files have been opened.
Explanation:

The maximum number of open files has been reached. On some platforms, there is a system limit on the number of open files, but the compiler also has a limit of 2047 include files.

IBM1988I S
File filename could not be opened due to an access violation.
Explanation:

Either the file is in use or you tried to open a file for which you do not have sufficient privilege.

IBM1989I S
File name or extension for filename is too long.
Explanation:

The length of the file name or extension is greater than the maximum allowed.

IBM1990I S
File name filename has invalid format.
Explanation:

Apart from z/OS UNIX, file names should not contain quotes. Under z/OS UNIX, if the file name does contain quotes, it should specify a PDS member.

IBM1991I S
The load of the SQL preprocessor failed with ONCODE= oncode. DB2/2 must be properly installed before the SQL preprocessor can be loaded.
Explanation:

The compiler attempted to load the SQL preprocessor but was unable to do so. Check that DB2/2 is properly installed.

IBM1992I S
A file name must be specified.
Explanation:

The command syntax is:

 
  PLI {d:}{path}filename{.ext} {( options}
IBM1993I S
Compilation terminated by ATTENTION condition.
Explanation:

If you hit CTL-BRK during the compilation, the compilation will stop.

IBM1994I S
Internal compiler error: storage header has been overwritten
Explanation:

This message indicates that there is an error in the front end of the compiler. Please report the problem to IBM.

IBM1995I S
Internal compiler error: storage tail has been overwritten.
Explanation:

This message indicates that there is an error in the front end of the compiler. Please report the problem to IBM.

IBM1996I S
Internal compiler error: free amount free request size does not match allocated size allocated size.
Explanation:

This message indicates that there is an error in the front end of the compiler. Please report the problem to IBM.

IBM1997I S
Internal compiler error: no WHEN clause satisfied within module name
Explanation:

This message indicates that there is an error in the front end of the compiler. Please report the problem to IBM.

IBM1998I S
Internal compiler error: protection exception in module name
Explanation:

This message indicates that there is an error in the front end of the compiler. Please report the problem to IBM.

IBM1999I S
note
Explanation:

This message indicates that there is an error in the back end of the compiler. Please report the problem to IBM.

IBM2001I S
A LICENSE REQUEST WAS DENIED FOR PL/I, PID 5655-B22. THE REQUEST ENDED WITH STATUS CODE STATUS CODE AND RETURN CODE RETURN CODE. THE COMPILATION WILL BE TERMINATED.
Explanation:

IBM License Manager is installed on your system, but the request to verify that you have a license to use the PL/I compiler has failed.

IBM2002I S
Close of file filename failed. There may be a space problem.
Explanation:

An error has occurred while attempting to close a file.

IBM2003I S
Write to file filename failed. There may be a space problem.
Explanation:

An error has occurred while attempting to write to a file.

IBM2004I S
ATTACH reference must be declared with either a null argument list or with an argument list specifying only one argument.
Explanation:

If the ATTACH reference is declared without an argument list, change the declare to specify a null argument list by adding a pair of parentheses.

IBM2005I S
ATTACH reference must be an ENTRY reference.
Explanation:

GENERIC references and built-in subroutines may not be attached.

IBM2006I S
ATTACH reference cannot be a function reference.
Explanation:

An ATTACH reference must not have the RETURNS attribute, even if the value returned is an ENTRY.

IBM2007I S
ATTACH reference must use LINKAGE(SYSTEM).
Explanation:

Unless the default linkage is overridden, OPTIONS(LINKAGE(SYSTEM)) must be specified on the declare for the ATTACH reference.

IBM2008I S
ATTACH reference cannot be FETCHABLE.
Explanation:

An ATTACH reference may not be used in a FETCH or RELEASE statement.

IBM2009I S
ATTACH reference cannot be a nested procedure.
Explanation:

An ATTACH reference must be a level-1 procedure, although it does need to be external.

IBM2010I S
ATTACH reference, if an ENTRY variable, must be a LIMITED ENTRY.
Explanation:

Specify the LIMITED attribute in the declare for the ENTRY VARIABLE.

IBM2011I S
ATTACH reference, if it has an argument, must declare that argument as POINTER BYVALUE.
Explanation:

No other argument types are support in ATTACH statements.

IBM2012I S
The attribute keyword attribute is invalid in an ALIAS descriptor.
Explanation:

Like RETURNS descriptors, the attributes STRUCTURE, UNION and DIMENSION are not permitted. Hence, the following are invalid:

 
 
   define alias array (10) fixed bin;
 
   define alias point 1, 2 fixed bin, 2 fixed bin;
 
IBM2013I S
Only one description is allowed in an ALIAS definition.
Explanation:

The syntax allows the name in an alias definition to be followed by a description list, but that description list must consist of exactly one description. The following is invalid:

 
 
    define alias x fixed bin, float bin;
 
IBM2014I S
Extents in type descriptors must be constant.
Explanation:

In ALIAS and STRUCTURE descriptors, each string length and AREA size must be specified with a restricted expression. Like RETURNS descriptors, asterisks and non-constant expressions are not permitted.

IBM2015I S
VALUE attribute conflicts with data type.
Explanation:

The VALUE attribute is allowed only with computational data types as well as pointer, offset, handle and ordinal.

IBM2016I S
VALUE and INITIAL attributes are not allowed with typed structures.
Explanation:

The VALUE attribute is valid only on scalars, and the INITIAL attribute is not allowed on typed structures.

IBM2017I S
INITIAL TO is valid only for NATIVE POINTER.
Explanation:

INITIAL TO is not valid for NONNATIVE POINTERs. It is also invalid for non-POINTERs since they cannot be assigned addresses.

IBM2018I S
INITIAL TO is supported only for STATIC variables.
Explanation:

INITIAL TO is not supported for variables belonging to any storage class other than STATIC.

IBM2019I S
Unsupported LINKAGE used with the LIST attribute.
Explanation:

Specify OPTIONS(LINKAGE(OPTLINK)) or, on WINDOWS, OPTIONS(LINKAGE(CDECL)) on the PROCEDURE or ENTRY having a parameter with the LIST attribute and then recompile.

IBM2020I S
There is more than one element named reference name in the typed structure structure name.
Explanation:

All references must be unambiguous.

IBM2021I S
There is no element named reference name in the structure structure name.
Explanation:

All structure references must be explicitly declared.

IBM2022I S
The ENTRY variable-name may not be used as a typed structure qualifier since it does not have the RETURNS attribute.
Explanation:

Functions, but not subprocedures, can be used as typed structure qualifiers (and then only if they return a typed structure).

IBM2023I S
The ENTRY variable-name may not be used as a typed structure qualifier.
Explanation:

x(...)=>y is invalid unless x returns a typed structure.

IBM2024I S
The array variable variable-name may be used as a typed structure qualifier only if it is completely subscripted before its dot qualification.
Explanation:

For instance, if x is an array of structure t with member m, x.m(2) is invalid. However, x(2).m is valid.

IBM2025I S
BUILTIN name built-in may not be used as a typed structure qualifier.
Explanation:

The named built-in function cannot be used as a typed structure qualifier.

IBM2026I S
The GENERIC variable variable-name may not be used as a typed structure qualifier.
Explanation:

GENERIC references may not be used as typed structure qualifiers.

IBM2027I S
variable-name may not be used as a structure qualifier.
Explanation:

x.y is invalid unless x is a structure, a union or a function returning a typed structure.

IBM2028I S
TYPEs must be defined before their use.
Explanation:

The DEFINE STRUCTURE or DEFINE ALIAS statement for a type x must precede any of use of x as attribute type. The following two statements should be in the opposite order.

 
 
    dcl x type point;
 
    define structure
      1 point
        2 x  fixed bin(31),
        2 y  fixed bin(31);
 
IBM2029I S
DEFINE STRUCTURE must specify a structure or union type.
Explanation:

A DEFINE STRUCTURE statement must specify a structure or union type with level numbers.

 
 
    define structure int fixed bin;
 
IBM2030I S
INITIAL attribute is invalid in structure definitions.
Explanation:

Defined structure types must be initialized via assignments.

IBM2031I S
Storage attributes are invalid in structure definition.
Explanation:

Storage attributes, such as AUTOMATIC and BYADDR, must be specified with variables declared with structure type.

IBM2032I S
DEFINE STRUCTURE may not specify an array of structures.
Explanation:

The level 1 name in a structure definition may not have the DIMENSION attribute.

IBM2033I S
Only one description is allowed in a structure definition.
Explanation:

The syntax allows the name in a structure definition to be followed by a description list, but that description list must consist of exactly one structure description. The following is invalid:

 
 
    define structure
      1 point
        2 x  fixed bin(31),
        2 y  fixed bin(31),
      1 rectangle
        2 upper_left   type point,
        2 lower_right  type point;
 
IBM2034I S
The argument to the type function type function must be an ordinal type name.
Explanation:

The argument to the type functions FIRST and LAST must be a type name, and that type must be an ordinal type.

IBM2035I S
The argument to the type function type function must be a structure type name.
Explanation:

The argument to the type function NEW must be a type name, and that type must be a structure type.

IBM2036I S
The second argument to the type function type function must have locator type.
Explanation:

The second argument to the BIND type function must be a pointer or offset value that is to be converted to a handle to the structure type named as the first argument.

IBM2037I S
The first argument to the type function type function must be a structure type name.
Explanation:

The first argument to the type functions BIND must be a type name, and that type must be a structure type.

IBM2038I S
BUILTIN name argument must have HANDLE type.
Explanation:

An expression contains the named built-in function with an argument that is not a HANDLE.

IBM2039I S
Argument to variable name pseudovariable must be a HANDLE.
Explanation:

The TYPE pseudovariable can be applied only to HANDLEs.

IBM2040I S
The argument to the type function type function must be a defined type.
Explanation:

The first argument to the type function SIZE must be the name of a defined type.

IBM2041I S
The first argument to the type function type function must be a defined type.
Explanation:

The first argument to the type function CAST must be the name of a defined type.

IBM2042I S
The second argument to the type function type function must be a scalar.
Explanation:

The second argument to the type function CAST must be a scalar.

IBM2043I S
The second argument to the type function type function must have the same size as the first argument.
Explanation:

The second argument to the type function CAST must have the same size as the size of the type that is the first argument.

IBM2044I S
The get storage function to BUILTIN name must be a LIMITED ENTRY with LINKAGE(OPTLINK) and an appropriate entry description list.
Explanation:

The function should be declared as

 
  dcl get entry( pointer byvalue,
                 fixed bin(31) byaddr,
                 fixed bin(31) byaddr )
          returns( pointer );
IBM2045I S
The free storage function to BUILTIN name must be a LIMITED ENTRY with LINKAGE(OPTLINK) and an appropriate entry description list.
Explanation:

The function should be declared as

 
  dcl free entry( pointer byvalue,
                  pointer byvalue,
                  fixed bin(31) byvalue );
IBM2046I S
Descriptors must not be needed for any parameter to an ENTRY with a variable number of arguments.
Explanation:

If an entry has a variable number of arguments, i.e. its last parameter has the LIST attribute, OPTIONS(NODESCRIPTOR) must be specified (and valid) if any of the required parameters could have a descriptor.

IBM2047I S
The VARGLIST built-in function may be used only inside procedures whose last parameter had the LIST attribute.
Explanation:

The VARGLIST built-in function obtains the address of the variable argument list passed to procedures whose last parameter had the LIST attribute. It may not be used in subprocedures of such routines or in procedures having either no parameters or having no parameter declared with the LIST attribute.

IBM2048I S
The LIST attribute may be specified only on non-nested procedures, external entry constants, and limited entry variables.
Explanation:

The LIST attribute causes a variable argument list to be built, and such argument lists are permitted neither with nested procedures nor with entry variables declared without the LIMITED attribute.

IBM2049I S
The LIST attribute may be specified only on the last element of an entry description list.
Explanation:

The LIST attribute indicates that zero or more parameters may be specified after it, but those parameters may not be described.

IBM2050I S
Descriptors are supported for Fortran only for scalar character strings.
Explanation:

If OPTIONS( FORTRAN DESCRIPTOR ) applies, all parameters other than character strings must have constant extents.

IBM2051I S
Descriptors are not supported for Fortran for routines defined by or containing ENTRY statements.
Explanation:

If OPTIONS( FORTRAN DESCRIPTOR ) applies to an ENTRY statement or to a procedure containing an ENTRY statement, all parameters must have constant extents.

IBM2052I S
A function defined by a PROCEDURE containing ENTRY statements must return aggregate values BYADDR.
Explanation:

Either BYADDR must be specified in the RETURNS option of the PROCEDURE statement, or the RETURNS(BYADDR) suboption of the DEFAULT statement must be in effect.

IBM2053I S
A function defined by an ENTRY statement must return aggregate values BYADDR.
Explanation:

Either BYADDR must be specified in the RETURNS option of the ENTRY statement, or the RETURNS(BYADDR) suboption of the DEFAULT statement must be in effect.

IBM2054I S
A PROCEDURE containing ENTRY statements must receive all non-pointer parameters BYADDR.
Explanation:

Either BYADDR must be specified in the declares for the parameters, or the BYADDR suboption of the DEFAULT statement must be in effect.

IBM2055I S
An ENTRY statement must receive all parameters BYADDR.
Explanation:

Either BYADDR must be specified in the declares for the parameters, or the BYADDR suboption of the DEFAULT statement must be in effect.

IBM2056I S
ENTRY statement is not allowed in DO loops.
Explanation:

ENTRY statements are allowed in non-iterative DO groups, but not in iterative DO loops.

IBM2057I S
RETURN statement is invalid inside a BEGIN in a PROCEDURE that contains ENTRY statements.
Explanation:

A RETURN statement is valid inside a BEGIN block only if the PROCEDURE enclosing that BEGIN block contains no ENTRY statements.

IBM2058I S
In a PROCEDURE without the RETURNS option, any ENTRY statement must use BYADDR for its RETURNS value.
Explanation:

Either BYADDR must be specified in the RETURNS option of the ENTRY statement, or the RETURNS(BYADDR) suboption of the DEFAULT statement must be in effect.

IBM2059I S
OPTIONS(FORTRAN) is invalid if any parameters are UNALIGNED BIT.
Explanation:

Only ALIGNED BIT strings with constant length are valid with OPTIONS(FORTRAN).

IBM2060I S
Attributes may not be specified in ALLOCATEs of BASED variables.
Explanation:

Attributes may be specified only in ALLOCATEs of CONTROLLED variables.

IBM2061I S
Attributes specified for variable-name in ALLOCATE statement do not match those in its declaration.
Explanation:

An attribute, such as CHARACTER, may be specified in an ALLOCATE statement only if it is also specified in the declaration of the variable to be allocated.

IBM2062I S
Structuring specified in ALLOCATE of variable-name does not match that in its declaration.
Explanation:

In an ALLOCATE statement for a structure, all the levels specified in its declaration must be specified, and no new levels may be specified.

IBM2063I S
Specification of extent for variable-name in ALLOCATE statement is invalid since it was declared with a constant extent.
Explanation:

An attribute, such as CHARACTER, may be specified in an ALLOCATE statement only if it is also specified in the declaration of the variable to be allocated with either an asterisk or a non-constant expression.

IBM2064I S
The extent specified for the lower bound for dimension dimension-value of variable-name in ALLOCATE statement is invalid since that variable was declared with a different constant extent.
Explanation:

If a bound for a CONTROLLED variable is declared as a constant, then it must be specified as the same constant value in any ALLOCATE statement for that variable.

IBM2065I S
The extent specified for the upper bound for dimension dimension-value of variable-name in ALLOCATE statement is invalid since that variable was declared with a different constant extent.
Explanation:

If a bound for a CONTROLLED variable is declared as a constant, then it must be specified as the same constant value in any ALLOCATE statement for that variable.

IBM2075I S
ENTRY types and arguments in type function must be LIMITED.
Explanation:

A ENTRY type or argument used with the type function CAST must have the attribute LIMITED.

IBM2076I S
FLOAT types and arguments in type function must be NATIVE REAL.
Explanation:

A FLOAT type or argument used with the type function CAST must have the attributes NATIVE REAL.

IBM2077I S
FIXED BIN types and arguments in type function must be REAL with scale factor zero.
Explanation:

A FIXED BIN type or argument used with the type function CAST must have the attributes REAL PRECISION(p,0).

IBM2078I S
Types with the attributes attributes are not supported as the target of the type function function.
Explanation:

The first argument to the type function CAST must be a type with one of the following sets of attributes: REAL FIXED BIN(p,0) or NATIVE REAL FLOAT.

IBM2079I S
Arguments with the attributes attributes are not supported as the source in the type function function.
Explanation:

The second argument to the type function CAST must have one of the following sets of attributes: REAL FIXED BIN(p,0) or NATIVE REAL FLOAT.

IBM2080I S
DATE pattern is invalid.
Explanation:

See the Language Reference Manual for a list of the supported DATE patterns.

IBM2081I S
DATE attribute is valid only with NONVARYING CHARACTER, FIXED DECIMAL and arithmetic PICTURE.
Explanation:

The DATE attribute cannot be used on any other than the named types.

IBM2082I S
DATE attribute conflicts with non-zero scale factor.
Explanation:

The DATE attribute can be used on a numeric only if it has a scale factor of zero.

IBM2083I S
DATE attribute conflicts with COMPLEX attribute.
Explanation:

The DATE attribute can be used on a numeric only if it is REAL.

IBM2084I S
DATE attribute conflicts with PICTURE string containing characters other than 9.
Explanation:

The DATE attribute can be used on a PICTURE only if the PICTURE consists entirely of 9’s.

IBM2085I S
Length of DATE pattern and base precision do not match.
Explanation:

The DATE attribute can be used on a numeric only if its precision equals the length of the DATE pattern.

IBM2086I S
Length of DATE pattern and base length do not match.
Explanation:

The DATE attribute can be used on a string only if its length equals the length of the DATE pattern.

IBM2087I S
DATE attribute conflicts with adjustable length.
Explanation:

The DATE attribute can be used on a string only if the string is declared with a constant length.

IBM2088I S
Response file is too large. Excess will be ignored.
Explanation:

The options string built from the response file must be less than 32767 characters long.

IBM2089I S
Line in response file is longer than 100 characters. That line and rest of file will be ignored.
Explanation:

All lines in any response file must contain no more than 100 characters.

IBM2090I S
The keyword statement cannot be used under SYSTEM(CICS).
Explanation:

The named statement cannot be used under CICS.

IBM2091I S
DISPLAY with REPLY cannot be used under SYSTEM(CICS).
Explanation:

DISPLAY with REPLY cannot be used under CICS.

IBM2092I S
The BUILTIN name built-in function cannot be used under SYSTEM(CICS).
Explanation:

The named built-in function cannot be used under CICS.

IBM2093I S
The keyword statement cannot be used under SYSTEM(CICS) except with SYSPRINT.
Explanation:

The named I/O statement cannot be used under CICS unless the file used in the statement is SYSPRINT.

IBM2094I S
Source in CAST to FLOAT must be FLOAT, FIXED or ORDINAL.
Explanation:

The source in a CAST to a FLOAT must be FLOAT, FIXED or ORDINAL.

IBM2095I S
Target in CAST from FLOAT must be FLOAT, FIXED BIN or ORDINAL.
Explanation:

The target in a CAST from a FLOAT must be FLOAT, FIXED BIN or ORDINAL.

IBM2096I S
Target in CAST from FIXED DEC must be FLOAT, FIXED BIN or ORDINAL.
Explanation:

The target in a CAST from a FIXED DEC must be FLOAT, FIXED BIN or ORDINAL.

IBM2097I S
FIXED DEC types and arguments in type function must be REAL with non-negative scale factor.
Explanation:

A FIXED DEC type or argument used with the type function CAST must have the attributes REAL PRECISION(p,q) with p >= q and q >= 0.

IBM2098I S
Source in CAST to FIXED DEC must be FLOAT, FIXED or ORDINAL.
Explanation:

The source in a CAST to a FIXED DEC must be FLOAT, FIXED or ORDINAL.

IBM2099I S
CASEX strings must have the same length.
Explanation:

The two strings in the CASEX option must have the same length. The second argument is the uppercase value of the first. If a character in the first string does not have an uppercase value, use the character itself as the uppercase value.

IBM2100I S
The ORDINAL types do not match.
Explanation:

This message is issued in explanation of the message immediately preceding it in the listing.

IBM2101I S
The HANDLE types do not match.
Explanation:

This message is issued in explanation of the message immediately preceding it in the listing.

IBM2102I S
The STRUCTURE types do not match.
Explanation:

This message is issued in explanation of the message immediately preceding it in the listing.

IBM2103I S
Alignment does not match.
Explanation:

This message is issued in explanation of the message immediately preceding it in the listing.

IBM2104I S
Number and attributes of structure members do not match.
Explanation:

This message is issued in explanation of the message immediately preceding it in the listing.

IBM2105I S
Number of dimensions do not match.
Explanation:

This message is issued in explanation of the message immediately preceding it in the listing.

IBM2106I S
Lower bounds do not match.
Explanation:

This message is issued in explanation of the message immediately preceding it in the listing.

IBM2107I S
Upper bounds do not match.
Explanation:

This message is issued in explanation of the message immediately preceding it in the listing.

IBM2108I S
RETURNS attributes do not match.
Explanation:

This message is issued in explanation of the message immediately preceding it in the listing.

IBM2109I S
BYVALUE/BYADDR attributes in RETURNS do not match.
Explanation:

This message is issued in explanation of the message immediately preceding it in the listing.

IBM2110I S
LINKAGE values do not match.
Explanation:

This message is issued in explanation of the message immediately preceding it in the listing.

IBM2111I S
OPTIONS values do not match.
Explanation:

This message is issued in explanation of the message immediately preceding it in the listing.

IBM2112I S
Parameter counts do not match.
Explanation:

This message is issued in explanation of the message immediately preceding it in the listing.

IBM2113I S
BYVALUE/BYADDR attributes in parameter parameter-number do not match.
Explanation:

This message is issued in explanation of the message immediately preceding it in the listing.

IBM2114I S
Number of dimensions for parameter parameter-number do not match.
Explanation:

This message is issued in explanation of the message immediately preceding it in the listing.

IBM2115I S
Lower bounds for parameter parameter-number do not match.
Explanation:

This message is issued in explanation of the message immediately preceding it in the listing.

IBM2116I S
Upper bounds for parameter parameter-number do not match.
Explanation:

This message is issued in explanation of the message immediately preceding it in the listing.

IBM2117I S
Alignment of parameter parameter-number does not match.
Explanation:

This message is issued in explanation of the message immediately preceding it in the listing.

IBM2118I S
Number and attributes of structure members in parameter parameter-number do not match.
Explanation:

This message is issued in explanation of the message immediately preceding it in the listing.

IBM2119I S
Attributes of parameter parameter-number do not match.
Explanation:

This message is issued in explanation of the message immediately preceding it in the listing.

IBM2127I S
The ENTRY named ENTRY variable name matches the reference to the GENERIC variable GENERIC variable name, but while the GENERIC reference is used as a function, the matching ENTRY does not have the RETURNS attribute.
Explanation:

A match for the GENERIC reference has been found, but the match is not suitable because while the GENERIC reference is used as a function, the matching ENTRY is not a function. For example, the first GENERIC reference below is invalid, while the second is ok.

 
 
    dcl e1 entry( fixed bin );
    dcl e2 entry( fixed bin, fixed bin )
           returns( fixed bin );
    dcl gp generic( e1 when( * ),
                    e2 when( *, * ) );
 
    rc = gp( 0 );
 
    rc = gp( 0, 0 );
 
IBM2128I S
The ENTRY named ENTRY variable name matches the reference to the GENERIC variable GENERIC variable name, but while the GENERIC reference is used as a function acting as a locator qualifier, the matching ENTRY does not return a POINTER.
Explanation:

A match for the GENERIC reference has been found, but the match is not suitable because while the GENERIC reference is used as a locator, the matching ENTRY is not a function returning a POINTER. For example, the first GENERIC reference below is invalid, while the second is ok.

 
 
    dcl f1 entry( fixed bin )
           returns( fixed bin );
    dcl f2 entry( fixed bin, fixed bin )
           returns( pointer );
    dcl bx based fixed bin;
    dcl gf generic( f1 when( * ),
                    f2 when( *, * ) );
 
    rc = gf( 0 )->bx;
 
    rc = gf( 0, 0 )->bx;
 
IBM2129I S
The ENTRY named ENTRY variable name matches the reference to the GENERIC variable GENERIC variable name, but while the GENERIC reference is used as a repeating function reference, the matching ENTRY cannot be so used.
Explanation:

A match for the GENERIC reference has been found, but the match is not suitable because while the GENERIC reference is used as a function whose return value is a function that is invoked (and so on, as the number of argument lists mandates), the matching ENTRY cannot be so used. For example, the first GENERIC reference below is invalid, while the second is ok.

 
 
    dcl x1 entry( fixed bin )
           returns( entry );
    dcl x2 entry( fixed bin, fixed bin )
           returns( entry returns( fixed bin ) );
    dcl gx generic( x1 when( * ),
                    x2 when( *, * ) );
 
    rc = gx( 0 )();
 
    rc = gx( 0, 0 )();
 
IBM2130I S
iSUB defining is not valid with the POSITION attribute.
Explanation:

The POSITION attribute can be used only with string overlay defining.

 
 
    dcl b(4) char(2) pos(2) def( a(1sub,1sub) );
 
IBM2131I S
In iSUB defining, the base and DEFINED variables must match.
Explanation:

The defined and base arrays in iSUB defining must have identical attributes apart from the dimension attribute.

 
 
    dcl a(4) fixed bin(31);
    dcl b(4) fixed bin(15) def( a(1sub,1sub) );
 
IBM2132I S
The i in an iSUB reference must not exceed the dimensionality of the DEFINED variable.
Explanation:

The i in an iSUB reference must refer to a subscript of the DEFINED variable and hence must not be greater than the number of dimensions for that variable.

 
 
    dcl a(4,4) fixed bin(31);
    dcl b(4) fixed bin(15) def( a(1sub,2sub) );
 
IBM2133I S
An iSUB variable cannot be defined on a cross-section of its base.
Explanation:

In an iSUB variable, no asterisks may appear in the specification of the base array.

 
 
    dcl a(4,4) fixed bin(31);
    dcl b(4) fixed bin(15) def( a(1sub,*) );
 
IBM2134I S
iSUB defining is supported only for arrays of scalars.
Explanation:

iSUB defining is not supported for structures and unions.

IBM2135I S
DFT(DESCLIST) conflicts with CMPAT(cmpat-suboption).
Explanation:

If CMPAT(V1) or CMPAT(V2) is specified, then DFT(DESCLOCATOR) must be in effect (as it is by default on z/OS).

IBM2136I S
The number of indices specified for the LABEL identifier does not match the number previously specified.
Explanation:

The number of indices given for an element of a label constant array must not vary.

 
 
    a(1,1): ....
    a(1,2): ....
    a(3): ....
 
IBM2137I S
Indices have been specified for the LABEL identifier when it was previously specified without indices.
Explanation:

A label constant cannot be subscripted if its first use contains no subscripts.

 
 
    a: ....
    a(3): ....
 
IBM2138I S
Indices have not been specified for the LABEL identifier when it was previously specified with indices.
Explanation:

A label constant must be subscripted if its first use contains subscripts.

 
 
    a(3): ....
    a: ....
 
IBM2139I S
The Language Environment runtime is not current enough.
Explanation:

You are using Language Environment 2.10 (or earlier!), which is not supported by the compiler.

IBM2140I S
Length of second argument to the REPLACEBY2 built-in must be twice that of the third.
Explanation:

The second argument to the REPLACEBY2 built-in function provides the set of pairs of characters which are to replace the corresponding characters in the third argument, and hence the length of the second string must be twice that of the third.

IBM2141I S
First argument to the BUILTIN name built-in must be a structure.
Explanation:

The first argument to the named built-in subroutine must be a structure supplying the event handlers for the SAX parser.

IBM2142I S
Event structure argument to the BUILTIN name built-in has too few elements.
Explanation:

The first argument to the named built-in subroutine must be a structure supplying the event handlers for the SAX parser, and that structure must exactly the right number of members. See the Language Reference Manual for more details.

IBM2143I S
Event structure argument to the BUILTIN name built-in has too many elements.
Explanation:

The first argument to the named built-in subroutine must be a structure supplying the event handlers for the SAX parser, and that structure must exactly the right number of members. See the Language Reference Manual for more details.

IBM2144I S
Member member-number in the event structure argument to the BUILTIN name built-in is not a scalar.
Explanation:

The first argument to the named built-in subroutine must be a structure supplying the event handlers for the SAX parser, and each element of that structure must be a scalar. See the Language Reference Manual for more details.

IBM2145I S
Member member-number in the event structure argument to the BUILTIN name built-in must be a LIMITED ENTRY.
Explanation:

The indicated element of the structure supplying the event handlers for the SAX parser must be a LIMITED ENTRY. See the Language Reference Manual for more details.

IBM2146I S
Member member-number in the event structure argument to the BUILTIN name built-in must return BYVALUE a NATIVE FIXED BIN(31).
Explanation:

The indicated element of the structure supplying the event handlers for the SAX parser must be a function returning BYVALUE a NATIVE FIXED BIN(31). See the Language Reference Manual for more details.

IBM2147I S
Member member-number in the event structure argument to the BUILTIN name built-in must have a non-empty entry description list.
Explanation:

The indicated element of the structure supplying the event handlers for the SAX parser must have a non-empty entry description list. See the Language Reference Manual for more details.

IBM2148I S
Member member-number in the event structure argument to the BUILTIN name built-in has a parameter count of specified-parm-count when the correct parameter count is required-parm-count .
Explanation:

The indicated element of the structure supplying the event handlers for the SAX parser must have the correct number of parameters. See the Language Reference Manual for more details.

IBM2149I S
Member member-number in the event structure argument to the BUILTIN name built-in must have a BYVALUE POINTER as its first parameter.
Explanation:

The indicated element of the structure supplying the event handlers for the SAX parser must have a BYVALUE POINTER as its first parameter. See the Language Reference Manual for more details.

IBM2150I S
Member member-number in the event structure argument to the BUILTIN name built-in must have a BYVALUE POINTER as its second parameter.
Explanation:

The indicated element of the structure supplying the event handlers for the SAX parser must have a BYVALUE POINTER as its second parameter. See the Language Reference Manual for more details.

IBM2151I S
Member member-number in the event structure argument to the BUILTIN name built-in must have a BYVALUE NATIVE FIXED BIN(31) as its third parameter.
Explanation:

The indicated element of the structure supplying the event handlers for the SAX parser must have a BYVALUE NATIVE FIXED BIN(31) as its third parameter. See the Language Reference Manual for more details.

IBM2152I S
Member member-number in the event structure argument to the BUILTIN name built-in must have a BYVALUE POINTER as its fourth parameter.
Explanation:

The indicated element of the structure supplying the event handlers for the SAX parser must have a BYVALUE POINTER as its fourth parameter. See the Language Reference Manual for more details.

IBM2153I S
Member member-number in the event structure argument to the BUILTIN name built-in must have a BYVALUE NATIVE FIXED BIN(31) as its fifth parameter.
Explanation:

The indicated element of the structure supplying the event handlers for the SAX parser must have a BYVALUE NATIVE FIXED BIN(31) as its fifth parameter. See the Language Reference Manual for more details.

IBM2154I S
Member member-number in the event structure argument to the BUILTIN name built-in must have a BYVALUE POINTER as its second parameter.
Explanation:

The indicated element of the structure supplying the event handlers for the SAX parser must have a BYVALUE POINTER as its second parameter. See the Language Reference Manual for more details.

IBM2155I S
Member member-number in the event structure argument to the BUILTIN name built-in must have a BYVALUE NATIVE FIXED BIN(31) as its fourth parameter.
Explanation:

The indicated element of the structure supplying the event handlers for the SAX parser must have a BYVALUE NATIVE FIXED BIN(31) as its fourth parameter. See the Language Reference Manual for more details.

IBM2156I S
Member member-number in the event structure argument to the BUILTIN name built-in must have a BYVALUE NATIVE FIXED BIN(31) as its second parameter.
Explanation:

The indicated element of the structure supplying the event handlers for the SAX parser must have a BYVALUE NATIVE FIXED BIN(31) as its second parameter. See the Language Reference Manual for more details.

IBM2157I S
Member member-number in the event structure argument to the BUILTIN name built-in must have a BYVALUE CHAR(1) or BYVALUE WCHAR(1) as its second parameter.
Explanation:

The indicated element of the structure supplying the event handlers for the SAX parser must have a BYVALUE CHAR (or BYVALUE WIDECHAR) of length one as its second parameter. See the Language Reference Manual for more details.

IBM2158I S
Member member-number in the event structure argument to the BUILTIN name built-in has the wrong linkage.
Explanation:

The indicated element of the structure supplying the event handlers for the SAX parser must have the PL/I default linkage. See the Language Reference Manual for more details.

IBM2159I S
Member member-number in the event structure argument to the BUILTIN name built-in must have the NODESCRIPTOR option.
Explanation:

The indicated element of the structure supplying the event handlers for the SAX parser must have the NODESCRIPTOR option. See the Language Reference Manual for more details.

IBM2160I S
All members of the input structure to the BUILTIN name built-in must have computational type.
Explanation:

The XMLCHAR built-in function cannot be applied to structures containing noncomputational types.

IBM2161I S
The input structure to the BUILTIN name built-in must not be a UNION or contain any UNIONs.
Explanation:

The XMLCHAR built-in function cannot be applied to unions or to structures containing unions.

IBM2162I S
The input structure to the BUILTIN name built-in must not contain any GRAPHIC elements.
Explanation:

The XMLCHAR built-in function cannot be applied to structures containing any GRAPHIC data.

IBM2163I S
The input structure to the BUILTIN name built-in must not contain any WIDECHAR elements.
Explanation:

The XMLCHAR built-in function cannot be applied to structures containing any WIDECHAR data.

IBM2164I S
The input structure to the BUILTIN name built-in must not contain any unnamed substructures.
Explanation:

The XMLCHAR built-in function cannot be applied to structures containing substructures using an asterisk as a name.

IBM2165I S
PRV support is provided only if the LIMITS(EXTNAME(7)) option is in effect.
Explanation:

Support for long external names is incompatible with support for using the PRV to address CONTROLLED variables.

IBM2166I S
PRV support is provided only if the NORENT option is in effect.
Explanation:

Support for the RENT option is incompatible with support for using the PRV to address CONTROLLED variables.

IBM2167I S
PRV support is provided only if the CMPAT(V1) or CMPAT(V2) option is in effect.
Explanation:

Support for the CMPAT(LE) option is incompatible with support for using the PRV to address CONTROLLED variables.

IBM2170I S
Too many INTERNAL CONTROLLED variables.
Explanation:

When using the PRV to address CONTROLLED variables, there may be no more than 568 INTERNAL CONTROLLED variables.

IBM2171I S
Under the NOWRITABLE option, no FETCHABLE ENTRY may be declared at the PACKAGE level.
Explanation:

Under the NOWRITABLE option, every FETCHABLE ENTRY constant must be declared inside a PROCEDURE.

IBM2172I S
Under the NOWRITABLE option, no FILE CONSTANT may be declared at the PACKAGE level.
Explanation:

Under the NOWRITABLE option, every FILE CONSTANT must be declared inside a PROCEDURE.

IBM2173I S
Under the NOWRITABLE option, no CONTROLLED may be declared at the PACKAGE level.
Explanation:

Under the NOWRITABLE option, every CONTROLLED variable must be declared inside a PROCEDURE.

IBM2174I S
Result of REPLACEBY2 is too long.
Explanation:

The length of the string literal produced by applying the REPLACEBY2 built-in function to 3 literals must not be greater than the maximum allowed for a character literal.

IBM2175I S
The second and third arguments to REPLACEBY2 must be restricted expressions.
Explanation:

The REPLACEBY2 built-in function currently supports only second and third arguments that have a length and value known at compile time.

IBM2176I S
The result of the BUILTIN name built-in would require more than 32767 bytes.
Explanation:

The HEX and HEXIMAGE built-in functions cannot be applied to strings using more than 16383 bytes of storage.

IBM2177I S
The file filename is a PDS member and hence cannot be used for SYSADATA.
Explanation:

The named file is the file intended to be used as the SYSADATA file, but such a file must not be a member of a PDS.

IBM2178I S
INCLUDE statements are not supported when the LINEDIR option is in effect.
Explanation:

When the LINEDIR option is in effect, your source must contain no INCLUDE statements.

IBM2179I S
There is too little room between the margins for the LINE directive. The PPTRACE option will be turned off.
Explanation:

The %LINE directive generated by the PPTRACE must fit on one line. You must either make the margins wide enough to allow this or make the source file names short enough.

IBM2180I S
Use of the KEYED DIRECT file filename in a keyword statement without a KEY/KEYFROM clause is invalid.
Explanation:

Any input/output operation using a KEYED DIRECT file must include the key of the record to which the the operation is to be applied.

IBM2181I S
First argument to BUILTIN name built-in must have type CHARACTER.
Explanation:

This applies to the PICSPEC built-in function, for example.

IBM2182I S
Second argument to BUILTIN name built-in must be a constant.
Explanation:

This applies to the PICSPEC built-in function, for example.

IBM2183I S
The first argument to BUILTIN name built-in must have constant length equal to that of the second argument.
Explanation:

This applies to the PICSPEC built-in function, for example.

IBM2184I S
Compiler input files must have less then 1000000 lines.
Explanation:

Break up the source files into smaller files.

IBM2185I S
Argument to BUILTIN name built-in must have type REAL DECIMAL FLOAT, and the DFP option must be in effect.
Explanation:

This applies to the ISFINITE and similar built-in functions.

IBM2186I S
BUILTIN name is not supported for DFP.
Explanation:

The named built-in function is not supported for float using DFP. This message applies, for instance, to the SQRTF built-in functions

IBM2187I S
The exponent in the literal value is too large for DECIMAL FLOAT with precision precision.
Explanation:

A DFP literal value when adjusted to have no decimal point (e.g. 3.14E0 would be adjusted to 314E-2) must have an exponent no larger than the maximum for its precision. For precision <= 7, the maximum is 90. For 7 < precision <= 16, the maximum is 369. For 16 < precision, the maximum is 6111.

IBM2188I S
The exponent in the literal value is too small for DECIMAL FLOAT with precision precision.
Explanation:

A DFP literal value when adjusted to have no decimal point (e.g. 3.14E0 would be adjusted to 314E-2) must have an exponent no smaller than the minimum for its precision. For precision <= 7, the minimum is -95. For 7 < precision <= 16, the minimum is -383. For 16 < precision, the minimum is -6143.

IBM2189I S
Under CMPAT(V2) and CMPAT(LE), bounds must not be greater than +2147483647.
Explanation:

Under CMPAT(V2) and CMPAT(LE), bounds must be between -2147483648 and +2147483647.

IBM2190I S
Under CMPAT(V2) and CMPAT(LE), bounds must not be less than -2147483648.
Explanation:

Under CMPAT(V2) and CMPAT(LE), bounds must be between -2147483648 and +2147483647.

IBM2191I S
No valid character specified in the option option.
Explanation:

You must specify at least one valid character in each of the OR, NOT and QUOTE or NAMES compiler options.

IBM2192I S
Member member-number in the event structure argument to the BUILTIN name built-in must have a BYVALUE POINTER as parameter number parameter-number .
Explanation:

The indicated element of the structure supplying the event handlers for the SAX parser must have a BYVALUE POINTER in the specified parameter position. See the Programming Guide for more details.

IBM2193I S
Member member-number in the event structure argument to the BUILTIN name built-in must have a BYVALUE NATIVE FIXED BIN(31) as parameter number parameter-number .
Explanation:

The indicated element of the structure supplying the event handlers for the SAX parser must have a BYVALUE NATIVE FIXED BIN(31) in the specified parameter position. See the Programming Guide for more details.

IBM2194I S
Member member-number in the event structure argument to the BUILTIN name built-in must have a BYADDR POINTER as parameter number parameter-number .
Explanation:

The indicated element of the structure supplying the event handlers for the SAX parser must have a BYADDR POINTER in the specified parameter position. See the Programming Guide for more details.

IBM2195I S
Member member-number in the event structure argument to the BUILTIN name built-in must have a BYADDR NATIVE FIXED BIN(31) as parameter number parameter-number .
Explanation:

The indicated element of the structure supplying the event handlers for the SAX parser must have a BYADDR NATIVE FIXED BIN(31) in the specified parameter position. See the Programming Guide for more details.

IBM2196I S
Member member-number in the event structure argument to the BUILTIN name built-in must have a BYVALUE ALIGNED BIT(8) as parameter number parameter-number .
Explanation:

The indicated element of the structure supplying the event handlers for the SAX parser must have a BYVALUE ALIGNED BIT(8) in the specified parameter position. See the Programming Guide for more details.

IBM2197I S
Argument to BUILTIN name built-in must have type CHAR or WIDECHAR.
Explanation:

This applies to the UVALID and ULENGTH built-in functions, for example.

IBM2198I S
First argument to BUILTIN name built-in must have type CHAR or WIDECHAR.
Explanation:

This applies to the UPOS and UWIDTH built-in functions, for example.

IBM2199I S
The run-time option XPLINK(ON) must be in effect if object code is to be generated.
Explanation:

The compiler backend requires the XPLINK(ON) option to be in effect.


Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)