LSCI ILCLINK Messages

This chapter describes ILCLINK diagnostic messages, their severity levels, causes, and resolutions.

ILCLINK diagnostic messages have the form

   LSCI[num] [severity]: [message text]
where

  NOTE     0
  WARNING  4
  ERROR    8
  SEVERE   12
  INTERNAL (ABEND)
A NOTE usually displays information about the expected behavior of the linker. WARNING messages indicate an error has occurred that will not affect ILCLINK's processing but should be examined by the user. An ERROR or SEVERE message is produced if ILCLINK encounters a condition that will not allow processing to continue. An ERROR indicates a problem that is within the user's control, such as an invalid control statement. A SEVERE message indicates a problem with the environment, such as an out-of-memory condition. Finally, an INTERNAL message (of which 038 is the only example), indicates that ILCLINK has failed to process a correct input file. ILCLINK issues a user ABEND in this situation. ILCLINK will continue processing if no diagnostics are produced with a severity level greater than WARNING.

Unless otherwise indicated, these messages can occur in any operating environment.

Note: The ILCLINK message prefix LSCI has been omitted from the descriptions below.

ILCLINK Messages

000

SEVERE: Not enough memory to continue.

Explanation

An attempt to allocate memory failed.

Action

Under CMS, increase the size of the virtual machine. Under TSO and MVS-batch, increase the region size.

001

SEVERE: Internal error in [function]. Code [num] .

Explanation

An internal error was detected in the specified function.

Action

Report the function name and code to the Technical Support Department at SAS Institute.

002

WARNING: Input file name truncated to 8 characters.

Explanation

CMS only: The filename given as the name of the input file contains more than 8 characters. The name will be truncated to 8 characters.

Action

CMS filenames cannot have more than 8 characters.

003

ERROR: Missing input file name.

Explanation

CMS only: No input filename was specified on the command line.

Action

Re-invoke ILCLINK with the name of the input file as the first parameter.

004

WARNING: Unknown option [option] ignored.

Explanation

The specified option is not an option. The option may have been misspelled.

Action

Re-invoke ILCLINK with the correct option name.

005

ERROR: Missing right parenthesis.

Explanation

TSO, MVS-batch only: An option requiring a parenthesized value does not have the terminating right parenthesis.

Action

Re-invoke ILCLINK with the correct form of the option.

006

ERROR, WARNING: Unable to open [file].

Explanation

ILCLINK could not open the specified file. The error level is Warning if the file is an output file, and Error if the file is the input file.

Action

Refer to library messages on stderr for more information about the error.

007

ERROR: Invalid parameter [parameter] .

Explanation

CMS only: More than one non-option parameter was used.

Action

Re-invoke ILCLINK using the filename of the input file as the only non-option parameter.

008

SEVERE: Unable to determine operating system.

Explanation

ILCLINK cannot determine the operating system.

Action

Contact the Technical Support Department at SAS Institute.

009

ERROR: Expecting [statement-types] statement.

Explanation

The input file contains control statements that are not in the expected order. The message specifies the types of statements that can occur in the current context.

Action

Correct the statements in the input file.

010

ERROR: Incorrect or missing data in statement.

Explanation

The statement contains values that are misspelled, in the wrong order, or otherwise incorrect, or the statement does not contain an expected value or keyword.

011

ERROR: Only one entry point language may be specified.

Explanation

More than one language name was found in the FIRST statement.

Action

Correct the FIRST statement so that only one language name is used.

012

ERROR: Reading input file.

Explanation

An error occurred while reading the input file.

Action

Refer to library messages on stderr for more information about the error.

013

ERROR: Statement longer than [num] characters.

Explanation

A statement in the input file is longer than the maximum allowed. This can occur if the input file has a logical record length greater than 255.

Action

Reformat the input file to use only statements less than or equal to 255 characters.

014

ERROR: No PROCESS statements in input file.

Explanation

No PROCESS statement was found in the input file. A PROCESS statement must be used to produce useful results.

Action

Add PROCESS statements as required to link the program.

015

ERROR: Only one FIRST statement may be used.

Explanation

More than one FIRST statement was found in the input file. There may be only one FIRST statement.

Action

Remove extra FIRST statements from the input file.

016

ERROR: Writing to [file] .

Explanation

An error occurred while writing to the specified output file.

Action

Refer to library messages on stderr for more information about the error.

017

NOTE: No non-C languages defined.

Explanation

No languages other than C were named in any FIRST or LANGUAGE statement.

Action

None. This message is for information only.

018

ERROR: Unknown PROCESS keyword [keyword] .

Explanation

The PROCESS statement keyword is not CLINK, LINK, LKED, LOAD, or GENMOD. One of these keywords must be specified in a PROCESS statement.

Action

Correct the PROCESS statement.

019

ERROR: Opening utility file.

Explanation

An error occurred while opening the utility file.

Action

Refer to library messages on stderr for more information about the error.

020

NOTE/WARNING/ERROR: Return code from [command] was [num] .

Explanation

The return code from the specified operating system command or utility is the value shown in the message.

Action

If the return code is unexpected, consult the appropriate operating system documentation for the meaning of the return code. The operating system may have issued other messages, or the library may have issued a diagnostic message on stderr.

021

WARNING: SYSTEM command not issued due to [reason] .

Explanation

Either an error or attention prevented the command in the SYSTEM statement from completing.

Action

If an error occurred, refer to the library messages on stderr for more information.

022

WARNING: Entry point name longer than 8 characters. Using [name] as the entry point name.

Explanation

The entry point name specified in a FIRST statement, linkage editor ENTRY statement, or the RESET option for the LOAD command is longer than 8 characters.

Action

Shorten the entry point name.

023

NOTE: Languages in program are [language-list] .

Explanation

The list contains the language names specified in the FIRST and LANGUAGE statements.

Action

None. This message is for information only.

024

WARNING: Name [library] truncated to eight characters.

Explanation

A library name (a filename under CMS, or a DDname under MVS-batch and TSO) in an AUTOCALL statement is longer than eight characters. The maximum length of these names is eight.

Action

Correct the AUTOCALL statement.

025

ERROR: No more than [num] TXTLIBs may be GLOBALed.

Explanation

CMS only: Prior to VM/SP Release 5, the maximum number of GLOBALed TXTLIBs is 8. The total number of TXTLIB names found in the AUTOCALL statement exceeds this number.

Action

Remove TXTLIB names from the AUTOCALL statements. If the application requires more than 8 TXTLIBs, you must merge some.

026

NOTE: Echo [command] .

Explanation

This message is issued when the ECHO option is in effect. ILCLINK has issued the specified operating system command.

Action

None. This message is for information only.

027

ERROR: Unknown CLINK option [option] .

Explanation

The specified option in a PROCESS CLINK statement is not a CLINK option. The option may have been misspelled.

Action

Refer to CLINK documentation for a list of options.

028

ERROR: Entry point [name1] in [statement1] conflicts with entry point [name2] spec via [statement2] .

Explanation

Two conflicting entry point names have been detected. The name of the entry point may be specified by a FIRST statement, a linkage editor ENTRY statement, or the RESET option in a PROCESS LOAD statement.

Action

Check the specified statements and ensure that the entry point names do not conflict.

029

WARNING: You must specify an explicit entry point name for [language] programs.

Explanation

The FIRST statement specified a default entry point name and no default can be chosen. An explicit entry point name must be specified when the FIRST language is COBOL, FORTRAN, or a user-supported language.

Action

Determine the entry point name and add it to the FIRST statement.

030

WARNING: [DDname] FILEDEF is already in effect.

Explanation

CMS only: A FILEDEF for a TXTLIB named in an AUTOCALL statement has already been issued. ILCLINK will not reissue the FILEDEF.

Action

Clear conflicting FILEDEFs before invoking ILCLINK.

031

WARNING: Concatenated SYSLIB FILEDEFs are not supported by the LKED command.

Explanation

CMS only: More than one AUTOCALL library name was specified for a PROCESS LKED statement. As of Release 5 of CMS, the LKED command does not support concatentated SYSLIB libraries. ILCLINK will issue the FILEDEFs anyway.

Action

Put all autocalled object code into a single TXTLIB.

032

WARNING: Invalid DDname prefix [prefix] specified by FILES option.

Explanation

TSO, MVS-batch only: The value specified by the FILES option was greater than 3 characters long, or the first character was not A - Z, #, $, or @.

Action

Specify a valid DDname prefix with the FILES option.

033

ERROR: Dataset is already open.

Explanation

TSO, MVS-batch only: A data set referred to in the current statement is already open.

Action

Ensure that all data sets that will be used are closed before invoking ILCLINK.

034

ERROR: Specified DDname not found.

Explanation

TSO, MVS-batch only: A DDname specified in the current statement has not been allocated.

Action

Ensure that all DDnames that will be used are allocated before invoking ILCLINK.

035

SEVERE: In dynamic allocation. Return code [num], reason code [num], information reason [num].

Explanation

TSO, MVS-batch only: An unexpected error occurred while executing SVC 99 (dynamic allocation).

Action

Report the return code, reason code, and information reason code to the Technical Support Department at SAS Institute.

036

SEVERE: Dynamic allocation request denied by installation. Return code [num], reason code [num], information reason [num].

Explanation

TSO, MVS-batch only: An SVC 99 request for dynamic allocation failed due to an installation restriction.

Action

Consult a systems programmer at your site for more information.

037

ERROR: JOBLIB, STEPLIB, JOBCAT, or STEPCAT specified on [statement-type] statement.

Explanation

TSO, MVS-batch only: One of the above DDnames was used in a statement.

Action

Use another DDname to refer to the data set.

038

INTERNAL: Invalid dynamic allocation parameter list.

Explanation

TSO, MVS-batch only: ILCLINK created an invalid SVC 99 parameter list. ILCLINK will issue a user ABEND.

Action

Report the error, including the traceback, to the Technical Support Department at SAS Institute.

039

ERROR: Required DDname unavailable.

Explanation

TSO, MVS-batch only: A DDname in the current statement has not been allocated.

Action

Ensure that the DDnames used in the input file have been allocated before invoking ILCLINK.

040

ERROR: Unable to allocate [dsname] OLD. Allocated to another job or user.

Explanation

TSO, MVS-batch only: The specified data set is already in use by another job or session.

Action

Free any conflicting allocation(s) before invoking ILCLINK.

042

ERROR: Deconcatenation of DDname [ddname] would result in duplicate DDnames.

Explanation

TSO, MVS-batch only: A data set concatenation created by ILCLINK contains a DDname that has since been allocated.

Action

Use unique DDnames in ALLOCATE commands issued via the SYSTEM statement.

043

ERROR: SYSTEM statement too long to process.

Explanation

A command specified in a SYSTEM statement exceeds the limit of 500 characters.

Action

Reduce the number of characters in the command. This error is most likely caused by excessive blank space on the command.

044

WARNING: SYSTEM statements may not be issued in MVS-batch.

Explanation

MVS-batch only: ILCLINK will not issue a command in a SYSTEM statement under MVS-batch.

Action

Remove the statement.

045

ERROR: GENMOD command too long to issue.

Explanation

CMS only: A PROCESS GENMOD statement requires that a GENMOD command longer than 240 bytes be created. ILCLINK cannot create commands longer than 240 bytes.

Action

Re-code the PROCESS GENMOD statement. This error is most likely the result of excessive blank space in the statement.

046

ERROR: Cannot determine first CSECT name.

Explanation

CMS only: An error occurred while reading the LOAD MAP file.

Action

Refer to library messages for more information about the error.

047

ERROR: [utility] abnormally terminated.

Explanation

TSO, MVS-batch only: The utility (for example, the linker) invoked for the current process ABENDed.

Action

Refer to diagnostics issued by the utility for more information.

048

ERROR: Duplicate DDnames specified in concatenation.

Explanation

A DDname concatenation used the same DDname more than once. ILCLINK cannot deconcatenate these DDnames.

Action

Change the JCL used to run ILCLINK to specify unique DDnames.

Copyright (c) 1998 SAS Institute Inc. Cary, NC, USA. All rights reserved.