IPVLANGX messages

This message shows the IPVLANGX program identification, version, and release date.

This message identifies the file to which the extract data information is written by IPVLANGX.

The member_name field is not included in the message if using a sequential file.

This message indicates that the information that was specified in txt1 is being read from the associated file and processed.

This message indicates that the information t at was specified in txt1 is checked for consistency.

This message indicates pass dec2 of the multi-pass processing task that is specified in txt1 is now being performed.

This message indicates that all necessary information was read from the associated files, and post-processing of this information is being performed.

This message indicates that the information that was specified in txt1 is now being correlated.

This message indicates that the processing step specified in txt1 is now being performed.

This message indicates that dec2 records were read from the txt1 file when the current compile unit was processed by IPVLANGX.

This message indicates that the current compile unit contained dec2 symbols with characteristics of type txt1

This message indicates that the current compile unit contained dec1 Long Name Resolution Identifiers.

This message indicates that the current compile unit contained dec1 symbols.

This message shows the number of records of extract data information which were written to the output file.

Processing was completed for the current compile unit.

This message identifies the input file(s) which were processed by IPVLANGX

The txt1 field is normally Input file: or Input files:.

The member_name field is not included in the message if using a sequential file.

This message is the last message to be displayed by IPVLANGX, and indicates that processing is completed for this IPVLANGX extract data file.

This message indicates that dec2 bytes of data were read from the txt1 file when the current compile unit was processed by IPVLANGX.

This message indicates that dec1 blocks of code which had been removed by optimization by the compiler have been identified. The source code and variables that are associated with these blocks have been eliminated from the extract data.

The argument for IPVLANGX option txt1 was not found during processing of the IPVLANGX invocation parameters.

The invocation parameter txt1 is not recognized as a valid IPVLANGX argument (or option). It exceeds the maximum length of a valid argument (or option), and might be spelled incorrectly.

The invocation parameter txt1 is not recognized as a valid IPVLANGX argument (or option).

An extra left parenthesis (after the initial left parenthesis which signals the start of the IPVLANGX options) was encountered during processing of the IPVLANGX invocation parameters.

The PDS or PDSE data set member name of the primary program information file from which source and variable data is to be extracted was not found during processing of the IPVLANGX invocation parameters.

The argument (or option) txt1 was encountered more than once during processing of the IPVLANGX invocation parameters.

A conflict between the argument (or option) txt1 and another previously specified argument (or option) was detected during processing of the IPVLANGX invocation parameters.

In the absence of an IPVLANGX option which explicitly specifies the application programming language, the IPVLANGX option txt1 was assumed.

The input file that was identified in txt1 did not contain the expected records. This could happen if, for example, the IDIADATA DDname was accidentally directed at a compiler listing data set.

The input file for IPVLANGX (the compiler listing) contains more output than just from the compile step. That is, there might be precompiler or postcompiler output, such as from a DB2® precompiler step or a link-edit step. Once this information is removed, the message is no longer be produced and the side file should be created as expected.

The format of the input file is insufficient for IPVLANGX processing because one or more of the required compiler options have not been specified.

txt1 specifies the compiler options that are required for a successful IPVLANGX execution. Source code information cannot be complete without these options. This message might be preceded by message IDISF8110W.

txt1 specifies the compiler options that are required for a successful IPVLANGX execution. Source code information cannot be complete without these options. This message is preceded by message IDISF8110W.

txt1 specifies the compiler options that are required for a successful IPVLANGX execution. Source code information cannot be complete without these options. This message is preceded by message IDISF8110W.

The format of the input file indicates that the specified option is no longer in effect.

The IPVLANGX input compiler listing or SYSADATA file txt1 could not be found to allow IPVLANGX processing to begin.

The IPVLANGX extract data file could not be found using either the primary file identifier txt1, or the alternative file identifier txt2 to allow IPVLANGX processing to begin.

The attributes or contents of a file have been found to be inappropriate, during IPVLANGX processing.

One or more preceding messages identify the file which was being processed when the error occurred or the reason for the failure. Reasons for this message might be error messages in the input compiler listing or missing required compiler options. For details on required compiler options, refer to Preparing your programs.

The Data Definition (DD) for the txt1 file was found to be unallocated.

The Data Definitions (DDs) for both the primary txt1 file and the alternative txt2 file were found to be unallocated.

The attributes of the txt1 file have been examined, and found to be inappropriate.

IPVLANGX had begun scanning the txt1 file data, but the file ended before all expected data records had been scanned.

There is insufficient space to write further records to the txt1 file.

There is insufficient free storage for IPVLANGX to continue processing.

The specified file was found to have a Fixed record format, and 1024-byte record length. It was likely compressed using TERSE or COPYFILE.

The maximum number of symbols that a single compile unit can contain is 65534. This limit is exceeded by the current compile unit.

During the extraction process, complete information was not available for the symbol shown. The extract data for unrelated symbols and program source is not affected.

Expected source column indicators were not found in the COBOL listing.

The name of a CSECT could not be determined.

The name of a CSECT could not be determined.

An invalid ESDID was encountered on a SYSADATA record read. The ESDID was ignored.