IPVLANGX messages

These messages are issued by the IPVLANGX program, which is used internally by Fault Analyzer or invoked by the user when creating side files.

IDISF8001I

IPVLANGX Version version (Release release)

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

Processing continues.

None

IDISF8002I

Output file: member_name DDname

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.

Processing continues.

None

IDISF8003I

... scanning txt1

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

Processing continues.

None

IDISF8004I

... checking txt1

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

Processing continues.

None

IDISF8005I

txt1 Pass dec2 processing begins

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

Processing continues.

None

IDISF8006I

Post-processing begins

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

Processing continues.

None

IDISF8007I

... matching txt1

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

Processing continues.

None

IDISF8008I

... performing txt1

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

Processing continues.

None

IDISF8010I

txt1 records scanned: dec2

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

Processing continues.

None

IDISF8011I

...Symbols txt1.. dec2

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

Processing continues.

None

IDISF8012I

...Long Name Resolution IDs: dec1

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

Processing continues.

None

IDISF8013I

...Total symbols: dec1

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

Processing continues.

None

IDISF8014I

Records written to output file: dec1

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

Processing continues.

None

IDISF8015I

Operation completed for this compile unit

Processing was completed for the current compile unit.

Processing continues if extra compile units are present.

None

IDISF8016I

txt1 member_name DDname

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.

Processing continues.

None

IDISF8017I

Operation completed for this extract file

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

Processing has completed.

None

IDISF8018I

txt1 bytes scanned: dec2

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

Processing continues.

None

IDISF8020I

...Blocks of dead code eliminated....... dec1

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.

Processing continues.

None

IDISF8050W

Argument missing for txt1 option. txt2

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

The default argument for the txt1 option is assumed.

If you are using IPVLANGX directly to create a side file, specify the invocation options as explained in IPVLANGX compiler listing to side file conversion utility. If the message is issued during fault analysis, contact your IBM® service representative.

IDISF8051S

Argument/Option too long, "txt1"

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.

Processing is terminated.

If you are using IPVLANGX directly to create a side file, specify the invocation options as explained in IPVLANGX compiler listing to side file conversion utility. If the message is issued during fault analysis, contact your IBM® service representative.

IDISF8052S

Argument/Option not recognized, "txt1"

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

Processing is terminated.

If you are using IPVLANGX directly to create a side file, specify the invocation options as explained in IPVLANGX compiler listing to side file conversion utility. If the message is issued during fault analysis, contact your IBM® service representative.

IDISF8055S

A left parenthesis was found inside options

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.

Processing is terminated.

If you are using IPVLANGX directly to create a side file, specify the invocation options as explained in IPVLANGX compiler listing to side file conversion utility. If the message is issued during fault analysis, contact your IBM® service representative.

IDISF8056S

No file name was specified

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.

Processing is terminated.

If you are using IPVLANGX directly to create a side file, specify the invocation options as explained in IPVLANGX compiler listing to side file conversion utility. If the message is issued during fault analysis, contact your IBM® service representative.

IDISF8057S

Argument/Option already specified, "txt1"

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

Processing is terminated.

If you are using IPVLANGX directly to create a side file, specify the invocation options as explained in IPVLANGX compiler listing to side file conversion utility. If the message is issued during fault analysis, contact your IBM® service representative.

IDISF8058S

Argument/Option "txt1" conflicts with previous Argument/Option

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

Processing is terminated.

If you are using IPVLANGX directly to create a side file, specify the invocation options as explained in IPVLANGX compiler listing to side file conversion utility. If the message is issued during fault analysis, contact your IBM® service representative.

IDISF8059I

Application language not specified, option "txt1" assumed

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

Processing continues.

If you are using IPVLANGX directly to create a side file, specify the invocation options as explained in IPVLANGX compiler listing to side file conversion utility. If the message is issued during fault analysis, contact your IBM® service representative.

IDISF8100S

txt1 contains NO recognized records

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.

Processing is terminated.

Ensure that the input file that was used is correct.

IDISF8103S

txt1 has unrecognized records following last valid section

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.

Processing is terminated.

Ensure that the input file that was used is correct.

IDISF8110W

Compiler option(s) incorrectly specified

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

Processing is terminated.

Recompile the module with the required compiler options as specified in Preparing your programs.

IDISF8114S

txt1 required for source support - fatal

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.

Processing is terminated.

Recompile the module with the required compiler options as specified in Preparing your programs.

IDISF8115W

txt1 required for symbol support

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.

Processing continues, however, the analysis report might be missing information.

Recompile the module with the required compiler options as specified in Preparing your programs.

IDISF8116W

txt1 required for structure/union support

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.

Processing continues, however, the analysis report might be missing information.

Recompile the module with the required compiler options as specified in Preparing your programs.

IDISF8120W

txt1 detected. txt2 option assumed

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

Processing continues, assuming an appropriate option to match the format of the input file.

Use the correct compiler option, or make the compiler directive which adjusted the compiler option visible to IPVLANGX, as appropriate. If the problem persists, contact your IBM® service representative.

IDISF8130S

File not found "txt1"

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

Processing is terminated.

Correct the file specification, or make the file available to IPVLANGX, as appropriate. If the problem persists, contact your IBM® service representative.

IDISF8131S

Files not found "txt1", and "txt2"

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.

Processing is terminated.

Correct the file specification, or make the file available to IPVLANGX, as appropriate. If the problem persists, contact your IBM® service representative.

IDISF8132S

Input or Output file format invalid

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.

Processing is terminated.

Correct the problem that was identified in the preceding message. If the problem persists, contact your IBM® service representative.

IDISF8133S

File DD not allocated "txt1"

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

Processing is terminated.

Allocate the file, using a JCL DD statement, or TSO ALLOCATE statement, as appropriate. If the problem persists, contact your IBM® service representative.

IDISF8134S

File DDs not allocated "txt1", and "txt2"

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

Processing is terminated.

Allocate the file, using a JCL DD statement, or TSO ALLOCATE statement, as appropriate. If the problem persists, contact your IBM® service representative.

IDISF8135S

txt1 file incorrectly defined

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

Processing is terminated.

Ensure that the correct data set was specified in the txt1 file allocation. If the correct data set was specified, the data set was allocated with incorrect attributes, in which case it must be reallocated. If the problem persists, contact your IBM® service representative.

IDISF8136S

Premature txt1 End-of-File encountered

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

Processing is terminated.

Ensure that the correct data set was specified in the txt1 file allocation. If the correct data set was specified, the file might have been truncated and must be replaced with the complete data. If the problem persists, contact your IBM® service representative.

IDISF8137S

txt1 disk/directory is full

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

This might be caused by :
  • PDS directory has no free entries
  • data set has maximum number of extents
  • insufficient free space on the DASD volume for another extent

Processing is terminated.

Determine the resource which is exhausted, and correct as appropriate. If the problem persists, contact your IBM® service representative.

IDISF8138T

Insufficient virtual memory available

There is insufficient free storage for IPVLANGX to continue processing.

Processing is terminated.

Free up virtual storage which is in use, or make more virtual storage available, as appropriate. If the problem persists, contact your IBM® service representative.

Note: IPVLANGX uses storage above the 16MB line, if it is available.

IDISF8139S

File is TERSEd or PACKed "txt1"

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

Processing is terminated.

Restore the file to its original format, using the appropriate utility program. If the problem persists, contact your IBM® service representative.

IDISF8150T

Maximum number of symbols exceeded

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

Processing is terminated.

Reduce the number of symbols below the limit. If the problem persists, contact your IBM® service representative.

IDISF8152W

Incomplete info for symbol "txt1" (ident: dec2)

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.

Processing continues.

Use IPVLANGX to format the extract data, and determine the missing information. Given this, examine the IPVLANGX input file(s) and determine the cause of the problem. If the problem persists, contact your IBM® service representative.

IDISF8158T

Invalid COBOL source column indicators - fatal

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

Processing is terminated.

Check if the attributes of file read have changed from those of the original compiler listing file.

IDISF8231S

Missing txt1 ESD information

The name of a CSECT could not be determined.

Processing continues but analysis might be incomplete.

Ensure that CSECTs are named in accordance with the requirements in Preparing your programs.

IDISF8233S

Unable to determine identity of unnamed PC Section

The name of a CSECT could not be determined.

Processing continues but analysis might be incomplete.

Ensure that CSECTs are named in accordance with the requirements in Preparing your programs.

IDISF8250A

SYSADATA input record record-number, invalid ESDID ignored

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

Processing continues.

None.