2100I INVALID INPUT CARD TYPE
content of statement in error

Explanation

Invalid input statement type. The identifier in character positions 2 through 4 is other than ESD, TXT, RLD, REP, or END.

System action

The invalid statement is ignored. Processing continues unless ACTION CANCEL was specified.

Operator response

None.

Programmer response

Refer to General Explanations for 21xx Messages . Compare the linkage editor input statement types with the SYSLST output. Remove the invalid input statement. Recompile (reassemble). If the invalid input statement is a REP statement, verify the letters REP in columns 2-4. Rerun the job.

2101I INVALID OPERATION IN CONTROL STATEMENTcontent of statementin error

Explanation

The operation code specified in the linkage editor control statement is other than PHASE, INCLUDE, MODE, ENTRY, or ACTION.

System action

The invalid statement is ignored. Processing continues unless ACTION CANCEL is specified.

Operator response

None.

Programmer response

Refer to General Explanations for 21xx Messages . Compare the required linkage editor control statement with the output on SYSLST. Correct the statement and rerun the job. Some possible errors are:
  • The operation code is misspelled.
  • The operation code begins in the first column.
  • A control statement is out of sequence.

2102I INVALID DECIMAL OR HEXADECIMAL FIELD content of statement in error

Explanation

A non-decimal character in a decimal field or a non-hexadecimal character in a hexadecimal field.

System action

The invalid statement is ignored. Processing continues unless ACTION CANCEL is specified.

Operator response

None.

Programmer response

Refer to General Explanations for 21xx Messages . Compare the required linkage editor input statement with the output on SYSLST. Some possible errors are:
  • Non-hexadecimal characters in the assembled address, in the ESD-ID number, or in data fields of the REP statement.
  • Non-hexadecimal characters in the origin field of the PHASE statement when hexadecimal format is used.
  • Non-decimal characters in the origin field of the PHASE statement when decimal format is used.

Correct the statement in error and rerun the job.

2110I INVALID OR MISSING DELIMITER content of statement in error

Explanation

Invalid or missing field delimiter in the control statement.

System action

The invalid statement is ignored. Processing continues unless ACTION CANCEL is specified.

Operator response

None.

Programmer response

Refer to General Explanations for 21xx Messages . Compare required linkage editor control statement with the output on SYSLST. Some possible errors are:
  • Imbedded blanks
  • Extraneous or missing commas
  • Missing apostrophe when using the hexadecimal format in a PHASE statement
  • Missing parenthesis in an INCLUDE statement

Correct the statement in error, and rerun the job.

2111I LENGTH OF AN OPERAND GREATER THAN EIGHT content of statement in error

Explanation

An operand specified in the currently processed control statement is longer than eight characters.

System action

The invalid statement, or part of it, is ignored. Processing continues unless ACTION CANCEL is specified.

Operator response

None.

Programmer response

Refer to General Explanations for 21xx Messages . Compare the required linkage editor control statement with the output on SYSLST. Correct the operand(s) that are longer than eight characters; then rerun the job.

2112I OPERAND FIELD MISSING content of statement in error

Explanation

Self-explanatory.

System action

The invalid statement is ignored. Processing continues unless ACTION CANCEL is specified.

Operator response

None.

Programmer response

Refer to General Explanations for 21xx Messages . Compare the required linkage editor control statement with the output on SYSLST. Some possible errors are:
  • In the control statement, a required operand was omitted by mistake.
  • A comma was coded after the last operand in the control statement.

Correct the statement in error, and rerun the job.

2113I STATEMENT EXTENDS BEYOND LIMIT content of statement in error

Explanation

The currently processed statement extends beyond column 71 or, in case of a REP statement, extents beyond column 70 (excluding identification information).

System action

The invalid statement is ignored. Processing continues unless ACTION CANCEL is specified.

Operator response

None.

Programmer response

Refer to General Explanations for 21xx Messages . Compare the required input or linkage editor control statement with the output on SYSLST. Correct the statement in error, and rerun the job.

2114I SUBMODULAR NAMELIST TOO LONG content of statement in error

Explanation

The list of control sections in the currently processed INCLUDE statement contains more than five names.

System action

The invalid statement is ignored. Processing continues unless ACTION CANCEL is specified.

Operator response

None.

Programmer response

Refer to General Explanations for 21xx Messages . Compare the required linkage editor control statement with the output on SYSLST. Correct the statement in error and rerun the job.

2116I CONTROL STATEMENT IN OBJECT MODULE content of statement in error

Explanation

The linkage editor found a control statement between the first ESD statement and the END statement of a module.

System action

The invalid statement is ignored. Processing continues unless ACTION CANCEL was specified.

Operator response

None.

Programmer response

Check for errors such as:
  • The statements in the input job stream are out of order.
  • A section of the object deck is missing (there is no END statement).

Correct the input job stream or recompile (reassemble) your program, if necessary, or do both. Rerun the job.

2118I INVALID OPERAND IN MODE CONTROL STATEMENT content of statement in error

Explanation

An invalid operand or delimiter has been found in the MODE control statement.

System action

The MODE control statement in error is accepted as input up to the point of the error.

Operator response

None.

Programmer response

Correct the error in the MODE control statement.

2119I INVALID PARAMETER IN PARM FIELD OF EXEC LNKEDT STATEMENT

Explanation

An invalid parameter has been found in the PARM field of the EXEC LNKEDT statement.

System action

Processing continues, but the invalid parameter is ignored.

Operator response

None.

Programmer response

Correct the invalid parameter in the PARM field of the EXEC LNKEDT statement.

2120I DUPLICATE PHASE NAME content of statement in error

Explanation

At least two PHASE statements specify the same phase name.

System action

The invalid statement is ignored. Processing continues with the NOAUTO option active, unless ACTION CANCEL is specified.
Note: If, during link editing of a multiphase program, a phase is linked as not relocatable, subsequent phases of that program are also linked as not relocatable. A phase may be linked as not relocatable if either of the following occurs: an error causing any of the messages 2120I through 2125I to be issued; the specified phase origin (in the PHASE statement) is not relocatable.

Operator response

None.

Programmer response

Refer to General Explanations for 21xx Messages . Compare the required PHASE statement with the output on SYSLST. Check the linkage editor map for the preceding PHASE statement with the same name and rename subsequent phases as required.

2121I PHASE NAME INVALID content of statement in error

Explanation

Either of the following:
  • The phase name contains invalid characters (valid characters are: A-Z, 0-9, /, #, $, and @).
  • The phase name is 'ALL', 'ROOT' or 'S'.

System action

The job is canceled if ACTION CANCEL is specified. Otherwise, the invalid statement is ignored and processing continues. If the statement in error is not the first PHASE statement, processing continues with the NOAUTO option in effect. See also the Note under System Action for message 2120I.

Operator response

None.

Programmer response

Refer to General Explanations for 21xx Messages . Compare the required PHASE statement with the output on SYSLST. Possibly the phase name specified in the rejected statement is just misspelled. Correct the statement in error and rerun the job.

2122I ORIGIN IN PHASE CARD NOT PREVIOUSLY DEFINED content of statement in error

Explanation

The symbol or the phase name specified in the origin field of the PHASE statement is undefined.

System action

The job is canceled if ACTION CANCEL is specified. Otherwise, the invalid statement is ignored and processing continues. If the statement in error is not the first PHASE statement, processing continues with the NOAUTO option in effect. See also the Note under System Action for message 2120I.

Operator response

None.

Programmer response

Refer to General Explanations for 21xx Messages . Compare the required PHASE statement with the output on SYSLST. Possibly a typing error in the phase-origin specification is at fault. If the phase origin is undefined, check whether the statements in the job stream are out of sequence (the phase origin must be defined before the system reads the PHASE statement). Make corrections as necessary and rerun the job.

2123I PREVIOUS PHASE phasename WITHOUT VALID OBJECT CODE

Explanation

The phase processed and named in the message includes invalid or no object code. Some possible causes are:
  • The PHASE statement follows the associated INCLUDE statement.
  • The PHASE statement follows the associated object deck.
  • An object deck is missing or incomplete.
  • A missing INCLUDE statement.

TXT statements may be regarded as missing if they belong to a control section that is already contained in the root phase and, therefore, not duplicated in any other phase.

System action

The invalid statement is ignored. Processing continues with the NOAUTO option in effect, unless ACTION CANCEL is specified. See also the Note under System Action for message 2120I.

Operator response

None.

Programmer response

Refer to General Explanations for 21xx Messages . Compare the required PHASE control statement with the output on SYSLST. Correct the job stream and rerun the job.

2124I PHASE ORIGIN NEGATIVE content of statement in error

Explanation

The origin field of the PHASE statement specifies a negative value. Some of the possible causes are:
  • The symbolic origin specification represents too low a value.
  • The specified negative relocation factor is too large, causing the phase origin to be less than zero.

System action

The job is canceled if ACTION CANCEL is specified. Otherwise, the invalid statement is ignored and processing continues. If the statement in error is not the first PHASE statement, processing continues with the NOAUTO option in effect. See also the Note under System Action for message 2120I.

Operator response

None.

Programmer response

Refer to General Explanations for 21xx Messages . Compare the required PHASE control statement with the output on SYSLST. Correct the origin (second) operand in the PHASE statement or change the address of the symbolic origin. Rerun the job.

2125I PHASE STATEMENT IN AUTOLINKED MODULE content of statement in error

Explanation

The linkage editor found a PHASE statement in an auto-linked relocatable module.

System action

The invalid statement is ignored. Processing continues with the NOAUTO option in effect, unless ACTION CANCEL is specified. See also the Note under System Action for message 2120I.

Operator response

None.

Programmer response

Remove the PHASE statement(s) and recatalog the module. Rerun the job.

2132I MORE THAN 5 LEVELS OF NESTED INCLUDES content of statement in error

Explanation

More than five levels of nested INCLUDEs were attempted.

System action

The invalid statement is ignored. Processing continues unless ACTION CANCEL is specified.

Operator response

None.

Programmer response

Reorganize your program to avoid more than five levels of nested INCLUDEs. Rerun the job.

2133I NESTED SUBMODULAR INCLUDE content of statement in error

Explanation

While processing an INCLUDE statement the linkage editor found another INCLUDE statement with a name-list operand. The linkage editor cannot handle a nested INCLUDE that contains a name-list operand.

System action

The invalid statement is ignored. Processing continues unless ACTION CANCEL is specified.

Operator response

None.

Programmer response

Restructure the job stream to eliminate any nested INCLUDE specifying a name list.

2135I INVALID OPERAND IN ACTION STATEMENT content of statement in error

Explanation

The ACTION statement being processed contains an invalid operand.

System action

The invalid parameter in the statement is ignored. Processing continues unless ACTION CANCEL is specified.

Operator response

None.

Programmer response

Refer to General Explanations for 21xx Messages . Compare the required ACTION statement with the output on SYSLST. Make corrections as necessary and rerun the job.

2136I ACTION MAP INVALID IF SYSLST IS UNASSIGNED content of statement in error

Explanation

ACTION MAP was specified, but SYSLST was not assigned.

System action

The invalid statement is ignored. Processing continues unless ACTION CANCEL is specified. If processing continues, the option NOMAP is in effect.

Operator response

None.

Programmer response

Rerun the job after having ensured that SYSLST is assigned. If SYSLST cannot be assigned, rerun the job with an ACTION statement that does not include the CANCEL operand. This causes the job to complete for error diagnosis purposes.

2139I DUPLICATE SECTION DEFINITION: csectname **** SECTION IGNORED *****

Explanation

The linkage editor found the named control section to be duplicate in the currently processed phase. The message is issued as a warning; this need not be an error condition.

System action

The system ignores the duplicate section definition; processing continues.

Operator response

None.

Programmer response

If the phase should not include duplicate control sections, make necessary corrections in your source code and resubmit the job for assembly and link-editing.

2140I INVALID ESD TYPE content of statement in error

Explanation

One of the following:
  • The ESD type is other than:
    • X'00' = Section definition
    • X'01' = Label definition
    • X'02' = External reference
    • X'04' = Private code
    • X'05' = COMMON
    • X'06' = Pseudo register
    • X'0A' = Weak external reference
  • The name field of a private-code ESD statement is not blank.

System action

The invalid statement is ignored. Processing continues unless ACTION CANCEL is specified.

Operator response

None.

Programmer response

Recompile and link-edit the program; then rerun the job. If the problem recurs, consider contacting IBM® for a search of its known-problems data base. For error information to be collected and held available, see Solving Problems.

2141I DUPLICATE ESID NUMBER content of statement in error

Explanation

The linkage editor encountered an ESD statement with the same ESD-ID number as was contained in a previously processed statement. Possible cause: no END statement in the last module of a phase.

System action

The invalid statement is ignored. Processing continues unless ACTION CANCEL is specified.

Operator response

None.

Programmer response

Recompile and link-edit the program; then rerun the job. If the problem recurs, consider contacting IBM for a search of its known-problems data base. For error information to be collected and held available, see Solving Problems.

2143I DUPLICATE ENTRY POINT LABEL content of statement in error

Explanation

At least one of the entry point labels specified in the displayed statement is a duplicate. Possibly, an EXEC LNKEDT statement is missing within a set of INCLUDE statements.

System action

The invalid statement is ignored. Processing continues unless ACTION CANCEL is specified.

Operator response

None.

Programmer response

Correct your input to eliminate the duplication; reassemble and link-edit the job. The error message recurs if not all duplications are resolved.

2144I INVALID ESID NUMBER OR CONTROL DICTIONARY OR LINKAGE TABLE OVERFLOW content of statement in error

Explanation

An ESD-ID number is invalid or linkage-editor control areas (linkage table and control dictionary) have overlapped because insufficient storage has been allocated.

System action

The invalid statement is ignored. If a CONTROL DICTIONARY OVERFLOW had occurred, the linkage editor terminates the job with RC=16. In all other cases, processing continues, unless ACTION CANCEL is specified.

Operator response

None.

Programmer response

Do one of the following:
  • Rerun the job in a larger partition.
  • Reduce the number of phases to be link-edited and rerun the job.
  • Specify a larger value in the SIZE operand of the EXEC statement and rerun the job.

Have your operator provide you with a MAP command output, if necessary.

2145I CSECT ORIGIN NOT ON DOUBLEWORD BOUNDARY content of statement in error

Explanation

The specified origin of the currently processed control section does not fall on a doubleword boundary.

System action

The invalid statement is ignored. Processing continues unless ACTION CANCEL is specified.

Operator response

None.

Programmer response

Correct your original specification, recompile (reassemble) your program and rerun the job.

2146I COMMON HAS SAME LABEL AS ENTRY POINT content of statement in error

Explanation

A defined COMMON area has the same label as an entry point label.

System action

The invalid statement is ignored. Processing continues unless ACTION CANCEL is specified.

Operator response

None.

Programmer response

Rename the affected COMMON area or entry point; recompile (reassemble) and link-edit the program.

2147I ENTRY POINT LABEL NOT IN DEFINED CSECT content of statement in error

Explanation

The entry-point label in the END statement does not belong to a defined control section. Probably, an ESD statement is missing.

System action

The invalid statement is ignored. Processing continues unless ACTION CANCEL is specified.

Operator response

None.

Programmer response

Refer to General Explanations for 21xx Messages. Compare the required linkage editor input statement with the output on SYSLST. Recompile (reassemble) the program and rerun the job. If the problem recurs, consider contacting IBM for a search of its known-problems data base. For error information to be collected and held available, see Solving Problems.

2148I COMMON AREA areaname EXCEEDED SIZE OF CONTROL SECTION WITH IDENTICAL NAME

Explanation

A named COMMON area has been encountered that is larger than a control section with the same name.

System action

The linkage editor uses the length of the specified control section. Processing continues, unless ACTION CANCEL is specified.

Operator response

None.

Programmer response

Ensure that no named COMMON area is larger than the control section initiating it.

2149I THE DISPLACEMENT VALUE OF PSEUDO REGISTER name IS TOO LARGE FOR ITS Q-TYPE CONSTANT FIELD

Explanation

The maximum value for displacement or cumulative length is x'FFFFFFFF' (4,294,967,295 bytes). In case that the Q-type constant length was defined as 3 or 2 bytes, then the maximum displacement values are x'FFFFFF' (16,777,215 bytes) or x'FFFF' (65,535 bytes) respectively. Q-type constants of 1-byte length are not allowed.

System action

The linkage editor does not load the Q-type constant field. Processing continues, unless ACTION CANCEL is specified.

Operator response

None.

Programmer response

Ensure that either the Q-type constant length is large enough or reduce number and/or size of the external dummy sections.

2150I ASSEMBLED ORIGIN LOWER THAN START OF PHASE content of statement in error

Explanation

The load address in the TXT or REP statement is lower than the origin of the phase.

System action

The invalid statement is ignored. Processing continues unless ACTION CANCEL is specified.

Operator response

None.

Programmer response

Check your object code. Correct your program, if necessary; recompile (reassemble) and link-edit the program. If the problem recurs, consider contacting IBM for a search of its known-problems data base. For error information to be collected and held available, see Solving Problems.

2151I INVALID DELIMITER content of statement in error

Explanation

The currently processed REP statement contains a delimiter other than comma or blank. Probable errors are:
  • Missing commas between the data fields.
  • A character other than a comma is used as a delimiter between data fields.
  • A character other than blank is used as a delimiter before the first and after the last data field.

System action

The invalid statement is ignored. Processing continues unless ACTION CANCEL is specified.

Operator response

None.

Programmer response

Refer to General Explanations for 21xx Messages . Compare required REP statement with the output on SYSLST. Make the necessary corrections and rerun the job.

2155I ESID NUMBER DOES NOT POINT TO CSECT content of statement in error

Explanation

The ESD-ID number of the currently processed ESD statement does not belong to a defined control section.

System action

The invalid statement is ignored. Processing continues unless ACTION CANCEL is specified.

Operator response

None.

Programmer response

Refer to General Explanations for 21xx Messages. Compare the required linkage editor input statement type with the output on SYSLST. If a REP statement is in error, correct the ESD-ID field. If another statement is in error, recompile (reassemble) and link-edit the program. If the problem recurs, consider contacting IBM for a search of its known-problems data base. For error information to be collected and held available, see Solving Problems.

2156I INVALID FORMAT OF RLD CARD content of statement in error

Explanation

Self-explanatory.

System action

The invalid statement is ignored. Processing continues unless ACTION CANCEL is specified.

Operator response

None.

Programmer response

Refer to General Explanations for 21xx Messages. Compare the required RLD statement with the output on SYSLST. Correct the error; recompile (reassemble) the program and rerun the job. If the problem recurs, consider contacting IBM for a search of its known-problems data base. For error information to be collected and held available, see Solving Problems.

2158I NO CSECT LENGTH SUPPLIED content of statement in error

Explanation

An END statement is being processed, but the length of the associated control section has not been supplied (for example, the last CSECT or only CSECT prior to the end card has a length of zero).

System action

The invalid statement is ignored. Processing continues unless ACTION CANCEL is specified.

Operator response

None.

Programmer response

Submit the program for execution. If execution fails, recompile (reassemble) the program and rerun the job. If execution is successful, ignore the message. If recompilation and link-editing do not correct the problem, consider contacting IBM for a search of its known-problems data base. For error information to be collected and held available, see Solving Problems.

2160I SVA OPERAND IGNORED - PHASE NOT RELOCATABLE content of statement in error

Explanation

The SVA operand is specified in the PHASE statement for a phase that is not relocatable.

System action

The linkage editor ignores the specified SVA operand. Processing continues, unless ACTION CANCEL is specified.

Operator response

None.

Programmer response

If the affected phase is to be loaded into the SVA, make the necessary changes to ensure that the linkage editor builds a relocatable phase. Possible causes for non-relocatability of the affected phase are:
  • An absolute address is specified as origin in the PHASE statement. Change this specification to a relocatable address.
  • The entry-point name of a non-relocatable phase or the name of a CSECT of such a phase was used as symbolic origin specification in the PHASE statement. Replace the specification by a name that represents a relocatable address.

2161I INVALID OPTION OPERAND IN PHASE STATEMENT content of statement in error

Explanation

One of the optional operands of the currently processed PHASE statement (NOAUTO, SVA, and PBDY) is invalid. Probable errors are:
  • A misspelled option operand.
  • A missing comma between two of the option operands.

System action

The invalid PHASE statement is ignored. Processing continues unless ACTION CANCEL is specified.

Operator response

None.

Programmer response

Refer to General Explanations for 21xx Messages . Compare the required PHASE statement with the output on SYSLST. Correct the statement in error and rerun the job.

2165I WARNING - RMODE=ANY ASSIGNED TO PHASE, BUT THE PHASE CONTAINS 2 AND/OR 3 BYTE RELOCATABLE ADDRESS CONSTANTS

Explanation

An RMODE=ANY has been assigned to the phase, but the phase contains 2 and/or 3 byte relocatable address constants. This means that if the phase is loaded above the 16MB line, these address constants contain invalid values. This may lead to unpredictable results if these address constants are used during processing.

System action

Processing continues, unless ACTION CANCEL is specified.

Operator response

None

Programmer response

If necessary, do one of the following.
  • Remove the 2 and 3 byte relocatable address constants from your phase, or
  • Assign an RMODE=24 to the phase.

2166I WARNING - AMODE=ANY/RMODE=24 ASSIGNED TO PHASE FROM ESD DATA, BUT AT LEAST ONE CSECT OF THE PHASE HAS AN AMODE=24

Explanation

An AMODE=ANY/RMODE=24 combination has been assigned to the phase from the ESD data of the CSECT containing the entry point of the phase, but there is at least one CSECT contained in the phase which has an AMODE of 24. This may cause the program to fail during execution.

System action

Processing continues, unless ACTION CANCEL is specified.

Operator response

None.

Programmer response

Do one of the following:
  1. If the AMODE=ANY/RMODE=24 specification is incorrect:
    • Specify an AMODE of 24 on the PARM field of the EXEC LNKEDT or on a MODE control statement that overrides the MODE specifications from the ESD data, or
    • Recompile/assemble the source program to obtain an object module with the AMODE=24 indicator for the CSECT containing the entry point.
  2. If you only want to suppress this message:
    • Specify the MODE information on the PARM field of the EXEC LNKEDT statement or provide a MODE statement that overrides the MODE specifications from the ESD data, or
    • Recompile/assemble the source program to obtain an object module with the AMODE=ANY or AMODE=31 indicator for all CSECTS.

2167I RMODE=ANY FROM ESD DATA IS NOT ACCEPTED FOR A NON-RELOCATABLE PHASE

Explanation

A PHASE statement has been found in this linkage edit job step in which an absolute address is specified as origin, and the RMODE of ANY specified via the ESD data for the phase is not allowed for a non-relocatable phase.

System action

Processing continues (unless ACTION CANCEL is specified), but the phase is assigned an RMODE of 24.

Operator response

None

Programmer response

Either
  • recompile/assemble the source program to obtain an object module without the RMODE=ANY indicator, or
  • change the PHASE statement.

2168I RMODE=ANY IN MODE CONTROL STATEMENT IS NOT ACCEPTED FOR A NON-RELOCATABLE PHASE

Explanation

A PHASE statement has been found in this linkage edit job step in which an absolute address is specified as origin, and the RMODE of ANY specified in the MODE control statement for the phase is not allowed for a non-relocatable phase.

System action

Processing continues (unless ACTION CANCEL is specified), but the phase is assigned an RMODE of 24.

Operator response

None

Programmer response

Either
  • remove or change the MODE control statement, or
  • change the PHASE statement.

2169I RMODE=ANY IN PARM FIELD OF EXEC LNKEDT STATEMENT IS NOT ACCEPTED FOR A NON-RELOCATABLE PHASE

Explanation

A PHASE statement has been found in this linkage edit job step in which an absolute address is specified as origin, and the RMODE of ANY specified in the PARM field of the EXEC LNKEDT statement is not allowed for a non-relocatable phase.

System action

Processing continues (unless ACTION CANCEL is specified), but the phase is assigned an RMODE of 24.

Operator response

None

Programmer response

Either
  • remove or change the RMODE specification in the PARM field of the EXEC LNKEDT statement, or
  • change the PHASE statement.

2170I ESID NUMBER NOT PREVIOUSLY PROCESSED content of statement in error

Explanation

The ESD-ID number in the currently processed statement was not processed previously. This error may be the result of a previous error. Possible errors are:
  • An incorrect ESD-ID number in a REP statement.
  • A previous error such as duplicate entry point labels or an invalid input statement.

System action

The invalid statement is ignored. Processing continues unless ACTION CANCEL is specified.

Operator response

None.

Programmer response

Refer to General Explanations for 21xx Messages . Compare the required linkage-editor input statement with the output on SYSLST. If a REP statement is in error, determine the correct ESD-ID number from the external symbol dictionary, correct the REP statement, and rerun the job. Else, perform corrective action as required for the previous error(s) and rerun the job.

2171I DUPLICATE MODE CONTROL STATEMENT FOUND FOR CURRENT PHASE - IGNORED

Explanation

If more than one MODE control statement is encountered in the link-edit for a phase only the first MODE control statement following the PHASE statement of the phase used.

System action

Processing continues (unless ACTION CANCEL is specified), but this MODE control statement is ignored as a source of AMODE/RMODE data for the linked phase.

Operator response

None.

Programmer response

If the phase should not contain more than one MODE control statement, remove the unnecessary MODE control statements and resubmit the job for link-editing.

2172I MODE CONTROL STATEMENT FOUND BEFORE FIRST VALID PHASE STATEMENT

Explanation

The MODE control statement must follow the PHASE statement of the phase.

System action

Processing continues (unless ACTION CANCEL is specified), but this MODE control statement is ignored as a source of AMODE/RMODE data for the linked phase(s).

Operator response

None.

Programmer response

Either
  • remove the MODE control statement from the job, or
  • place the MODE control statement behind the PHASE statement of the phase.

2173I INVALID AMODE/RMODE COMBINATION FOUND IN PARAMETER LIST

Explanation

An invalid combination of AMODE and RMODE parameters was found in the parameter list (control block INLCPARB) for the linkage editor call interface.

System action

Processing continues (unless ACTION CANCEL is specified), but the call interface parameter list (control block INLCPARB) is ignored as a source of AMODE/RMODE data for the linked phase(s).

Operator response

None.

Programmer response

Correct the AMODE and RMODE specification(s) in the call interface parameter list INLCPARB so that the combination of AMODE/RMODE specifications is valid.

2174I INVALID AMODE/RMODE COMBINATION FOUND IN ESD DATA FOR CSECT csectname content of statement in error

Explanation

An invalid combination of AMODE=24 and RMODE=ANY was found in the ESD data.

System action

Processing continues (unless ACTION CANCEL is specified), but the control section is processed as having an AMODE of 24 and an RMODE of 24.

Operator response

None.

Programmer response

Either
  • correct the ESD data to indicate a valid AMODE/RMODE combination, or
  • correct the AMODE/RMODE statements in your source program and recompile/assemble the source program to obtain an object module without the erroneous AMODE/RMODE indicators.

2175I INVALID AMODE/RMODE COMBINATION FOUND IN PARM FIELD OF EXEC LNKEDT STATEMENT

Explanation

An invalid combination of AMODE and RMODE parameters was specified in the PARM field of the EXEC LNKEDT statement.

System action

Processing continues (unless ACTION CANCEL is specified), but the PARM field is ignored as a source of AMODE/RMODE data for the linked phase(s).

Operator response

None.

Programmer response

Either
  • remove the AMODE and RMODE specification(s) from the PARM field, or
  • correct the PARM field so that the combination of AMODE/RMODE specifications is valid.

2176I INVALID AMODE/RMODE COMBINATION FOUND IN MODE CONTROL STATEMENT content of statement in error

Explanation

An invalid combination of AMODE and RMODE parameters was specified on the MODE control statement.

System action

Processing continues (unless ACTION CANCEL is specified), but the MODE control statement is ignored as a source of AMODE/RMODE data for the linked phase.

Operator response

None.

Programmer response

Either
  • remove the MODE control statement, or
  • correct the MODE control statement so that the combination of AMODE/RMODE specifications is valid.

2177I RMODE=ANY FROM ESD DATA IS INCOMPATIBLE WITH OVERLAY PROGRAM STRUCTURE

Explanation

A PHASE statement has been found in this linkage edit job step in which as origin a "symbol" or "ROOT" is specified, or "*" is specified and it is not the first phase. The RMODE=ANY assigned from the ESD data to the phase is incompatible with this PHASE statement specification.

System action

Processing continues (unless ACTION CANCEL is specified), but all phases in this linkage edit job step are assigned an RMODE of 24.

Operator response

None.

Programmer response

Either
  • recompile/assemble the source program to obtain an object module without the RMODE=ANY indicator, or
  • change the PHASE statement(s).

2178I RMODE=ANY IN MODE CONTROL STATEMENT IS INCOMPATIBLE WITH OVERLAY PROGRAM STRUCTURE

Explanation

A PHASE statement has been found in this linkage edit job step in which as origin a "symbol" or "ROOT" is specified, or "*" is specified and it is not the first phase. The RMODE=ANY specified on the MODE control statement is incompatible with this PHASE statement specification.

System action

Processing continues (unless ACTION CANCEL is specified), but the RMODE specification on the MODE control statement is ignored and all phases in this linkage edit job step are assigned an RMODE of 24.

Operator response

None.

Programmer response

Either
  • remove or change the MODE control statement, or
  • change the PHASE statement(s).

2179I RMODE=ANY IN PARM FIELD OF EXEC LNKEDT STATEMENT IS INCOMPATIBLE WITH OVERLAY PROGRAM STRUCTURE

Explanation

A PHASE statement has been found in this linkage edit job step in which as origin a "symbol" or "ROOT" is specified, or "*" is specified and it is not the first phase. The RMODE=ANY specified in the PARM field of the EXEC LNKEDT statement is incompatible with this PHASE statement specification.

System action

Processing continues (unless ACTION CANCEL is specified), but the RMODE specified in the PARM field of the EXEC LNKEDT statement is ignored and all phases in this linkage edit job step are assigned an RMODE of 24.

Operator response

None.

Programmer response

Either
  • remove or change the RMODE specification in the PARM field of the EXEC LNKEDT statement, or
  • change the PHASE statement(s).

2180I NO COMPILER OUTPUT ON SYSLNK

Explanation

The linkage editor was invoked implicitly by a GO operand in an EXEC statement, but the SYSLNK file contained no compiler (or assembler) output. Possible errors are:
  • The language translator executed without the LINK option
  • The program specified in the EXEC statement was not a language translator.

System action

The linkage editor terminates the job with RC=16.

Operator response

None.

Programmer response

One of the following:
  • Specify the LINK option for your language translator run.
  • Correct the EXEC statement in your job stream if no language translator run is intended.

If the problem recurs, consider contacting IBM for a search of its known-problems data base. For error information to be collected and held available, see Solving Problems.

2181I LAST PHASE PROCESSED HAS NO VALID OBJECT CODE

Explanation

No valid storage assignment in the final phase of the object module. The reason may be, for example:
  • The PHASE statement is out of order: it follows rather than precedes the associated INCLUDE statement or the associated object deck.
  • INCLUDE statement is missing.
  • An object deck is missing completely or in part.
  • One or more TXT statements are missing (TXT statements may be regarded as missing if they belong to a control section which is already contained in the root phase and therefore is not duplicated in any other phase).
  • A compile job failed in a previous job step.
  • SYSIPT is not assigned correctly.
  • The name of the sublibrary to be used was misspelled in the SEARCH operand of the applicable LIBDEF statement.

System action

The linkage editor terminates the job with RC=16.

Operator response

None.

Programmer response

Check your input to the linkage editor for possible errors as listed above. Make corrections as necessary and rerun the job.

2182I NO END CARD BEFORE ENTRY STATEMENT

Explanation

No END statement encountered before an ENTRY statement. Possible errors are:
  • A portion of the object deck is missing.
  • The ENTRY statement is out of order.

System action

The linkage editor terminates the job with RC=16.

Operator response

None.

Programmer response

Correct the placement of the ENTRY statement or recompile (reassemble) the affected source code. Rerun the job.

2183I ERROR LIMIT EXCEEDED

Explanation

The total number of errors has exceeded the specified limit.

System action

The linkage editor terminates the job with return code 16.

Operator response

None.

Programmer response

The default limit is 256. Any other limit between 1 and 9999 may be set using the ERRLMT option in the ACTION statement.

2185I ERROR DURING LINK OF SYSTEM COMPONENT (DOLLAR PHASE)

Explanation

An error occurred during link-editing of a phase whose name starts with $ or of a phase structure containing such a phase.

System action

The linkage editor terminates the job with RC=16.

Operator response

None.

Programmer response

Review the error output on SYSLST. Make corrections as necessary and rerun the job. If IBM supplied code is involved, contact IBM for a search of its known-problems data base. For error information to be collected and held available, see Solving Problems.

2186I TOO MANY PHASES, ONLY ONE IS ALLOWED IF OPTION LINK USED

Explanation

An attempt was made to link two or more phases in one job for which OPTION LINK was specified.

System action

The linkage editor terminates the job with RC=16.

Operator response

None.

Programmer response

Use OPTION CATAL or run a separate job for each of the phases that are to be linked.

2187I PARTITION ALLOCATION TOO SMALL, NOT ALL CSECT NAMES CAN BE SORTED

Explanation

The space allocated to the partition is too small. The linkage editor cannot build the table needed for sorting the CSECT names of the currently processed phase.

System action

Processing continues (unless ACTION CANCEL is specified), but one or more CSECT names will not appear on the link map.

Operator response

None.

Programmer response

If you need a link map, rerun the job in a larger partition.

2188I TOO MANY RLD ITEMS, ONLY 65534 ITEMS ARE ALLOWED

Explanation

An attempt was made to link a phase with more than 65534 RLD items.

System action

The linkage editor terminates the job with RC=16.

Operator response

None.

Programmer response

Check your input for the linkage editor for possible errors or split the phase into two or more phases and rerun the job.

2189I CURRENT PHASE TOO LARGE, MAXIMUM PHASE SIZE IS: 16MB MINUS PHASE ORIGIN

Explanation

The maximum size of a linked phase is: 16MB minus the specified origin in the PHASE card. For example, this origin is the partition start address of the partition in which the linkage editor is running if S is specified as the origin, or if * is specified as the origin and it is the first PHASE statement processed.

System action

The linkage editor terminates the job with RC=16.

Operator response

None

Programmer response

Either
  • correct the specification of the origin in the PHASE statement, or
  • if applicable, link the phases in a partition with a lower partition start address, or
  • check your input to the linkage editor for possible errors.

2190I PARTITION IS TOO SMALL

Explanation

The storage space required by the linkage editor for processing is too small. Possible errors are:
  • The value specified for SIZE in the EXEC statement is too small.
  • SIZE=AUTO is specified in the EXEC statement.
  • If running REAL mode, too few pages can be fixed.

System action

The linkage editor terminates the job with RC=16.

Operator response

None.

Programmer response

Correct the input and rerun the job. If necessary, have the operator issue the MAP command and make the corresponding output available to you.

2191I END OF FILE REACHED ON SYS001

Explanation

while attempting to write to the disk extent assigned to SYS001, the linkage editor reached the end of that extent.

System action

The linkage editor terminates the job with RC=16.

Operator response

None.

Programmer response

Make a larger extent available and rerun the job.

2192I PHASE*** INVALID FOR OPTION CATAL

Explanation

OPTION CATAL was specified, but the PHASE statement is missing.

System action

The linkage editor creates a dummy PHASE statement (using PHASE*** as the name of the phase). Then the job is terminated with RC=16. The program with the phase name PHASE*** is not cataloged.

Operator response

None.

Programmer response

Insert a PHASE statement at the beginning of the object deck and rerun the job.

2193I VIRTUAL IO AREA FULL FOR OPTION LINK

Explanation

The system's virtual I/O area is too small to contain the phase that is being linked, or the system GETVIS area was exhausted during the operation.

System action

The linkage editor terminates the job with RC=16.

Operator response

None.

Programmer response

Either:
  • Rerun the job with OPTION CATAL specified.
  • Rerun the job after having defined a larger virtual I/O area.

2195I NO TARGET CATALOG SUBLIBRARY SPECIFIED

Explanation

The linkage editor requires, for OPTION CATAL, a CATALOG=library.sublibrary specification in a LIBDEF statement in order to catalog a phase.

System action

The linkage editor terminates the job with RC=16.

Operator response

None.

Programmer response

Rerun the job with a LIBDEF statement specifying a sublibrary for cataloging.

2197I READING PAST END OF FILE ON SYSLNK

Explanation

The linkage-editor reached the end of the SYSLNK extent without having encountered a software end-of-file indication.

System action

The linkage editor terminates the job with RC=16.

Operator response

None.

Programmer response

Review the output on SYSLST. One error may be that SYSLNK has been concurrently deleted or overwritten by another task. Make corrections as necessary and rerun the job. If the problem recurs, consider contacting IBM for a search of its known-problems data base. For error information to be collected and held available, see Solving Problems.

2199I ERROR HAS OCCURRED DURING LINKAGE EDITING

Explanation

The message informs the operator that the linkage editor found an error.

System action

The system continues processing after having written one of the following to the device assigned to SYSLST:
  • One of the messages 2100I through 2179I (except messages 2139I and 2171I)
  • The unnumbered message: ** MODULE modulename NOT FOUND **

The affected link-edit run may have been canceled.

Operator response

Report the message to your programmer.

Programmer response

Check your SYSLST output for information as indicated under System Action above.