HFZLANGX messages

These messages are issued by the HFZLANGX utility.

HFZSF8001I   HFZLANGX Version version (Release release)

Explanation

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

System action

Processing continues.

User response

None

HFZSF8002I   Output file: member_name DDname

Explanation

This message identifies the file to which the extract data information is written by HFZLANGX. The member_name field is not included in the message if using a sequential file.

System action

Processing continues.

User response

None

HFZSF8003I   ... scanning txt1

Explanation

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

System action

Processing continues.

User response

None

HFZSF8004I   ... checking txt1

Explanation

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

System action

Processing continues.

User response

None

HFZSF8005I   txt1 Pass dec2 processing begins

Explanation

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

System action

Processing continues.

User response

None

HFZSF8006I   Post-processing begins

Explanation

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

System action

Processing continues.

User response

None

HFZSF8007I   ... matching txt1

Explanation

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

System action

Processing continues.

User response

None

HFZSF8008I   ... performing txt1

Explanation

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

System action

Processing continues.

User response

None

HFZSF8010I   txt1 records scanned: dec2

Explanation

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

System action

Processing continues.

User response

None

HFZSF8011I   ...Symbols txt1.. dec2

Explanation

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

System action

Processing continues.

User response

None

HFZSF8012I   ...Long Name Resolution IDs: dec1

Explanation

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

System action

Processing continues.

User response

None

HFZSF8013I   ...Total symbols: dec1

Explanation

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

System action

Processing continues.

User response

None

HFZSF8014I   Records written to output file: dec1

Explanation

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

System action

Processing continues.

User response

None

HFZSF8015I   Operation completed for this compile unit

Explanation

Processing was completed for the current compile unit.

System action

Processing continues if extra compile units are present.

User response

None

HFZSF8016I   txt1 member_name DDname

Explanation

This message identifies the input file(s) that were processed by HFZLANGX. 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.

System action

Processing continues.

User response

None

HFZSF8017I   Operation completed for this extract file

Explanation

This message is the last message to be displayed by HFZLANGX. It indicates that processing is completed for this HFZLANGX extract data file.

System action

Processing has completed.

User response

None

HFZSF8018I   txt1 bytes scanned: dec2

Explanation

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

System action

Processing continues.

User response

None

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

Explanation

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.

System action

Processing continues.

User response

None

HFZSF8050W   Argument missing for txt1 option. txt2

Explanation

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

System action

The default argument for the txt1 option is assumed.

User response

If you are using HFZLANGX directly to create a side file, specify the invocation options as explained in Creating side files with the HFZLANGX utility. If the message is issued during fault analysis, contact your service representative.

HFZSF8051S   Argument/Option too long, "txt1"

Explanation

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

System action

Processing is terminated.

User response

If you are using HFZLANGX directly to create a side file, specify the invocation options as explained in Creating side files with the HFZLANGX utility. If the message is issued during fault analysis, contact your service representative.

HFZSF8052S   Argument/Option not recognized, "txt1"

Explanation

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

System action

Processing is terminated.

User response

If you are using HFZLANGX directly to create a side file, specify the invocation options as explained in Creating side files with the HFZLANGX utility. If the message is issued during fault analysis, contact your service representative.

HFZSF8055S   A left parenthesis was found inside options

Explanation

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

System action

Processing is terminated.

User response

If you are using HFZLANGX directly to create a side file, specify the invocation options as explained in Creating side files with the HFZLANGX utility. If the message is issued during fault analysis, contact your service representative.

HFZSF8056S   No file name was specified

Explanation

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 HFZLANGX invocation parameters.

System action

Processing is terminated.

User response

If you are using HFZLANGX directly to create a side file, specify the invocation options as explained in Creating side files with the HFZLANGX utility. If the message is issued during fault analysis, contact your service representative.

HFZSF8057S   Argument/Option already specified, "txt1"

Explanation

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

System action

Processing is terminated.

User response

If you are using HFZLANGX directly to create a side file, specify the invocation options as explained in Creating side files with the HFZLANGX utility. If the message is issued during fault analysis, contact your service representative.

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

Explanation

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

System action

Processing is terminated.

User response

If you are using HFZLANGX directly to create a side file, specify the invocation options as explained in Creating side files with the HFZLANGX utility. If the message is issued during fault analysis, contact your service representative.

HFZSF8059I   Application language not specified, option "txt1" assumed

Explanation

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

System action

Processing continues.

User response

If you are using HFZLANGX directly to create a side file, specify the invocation options as explained in Creating side files with the HFZLANGX utility. If the message is issued during fault analysis, contact your service representative.

HFZSF8100S   txt1 contains NO recognized records

Explanation

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

System action

Processing is terminated.

User response

Ensure that the input file that was used is correct.

HFZSF8103S   txt1 has unrecognized records following last valid section

Explanation

The input file for HFZLANGX (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 produced and the side file should be created as expected.

System action

Processing is terminated.

User response

Ensure that the input file that was used is correct.

HFZSF8110W   Compiler option(s) incorrectly specified

Explanation

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

System action

Processing is terminated.

User response

Recompile the module with the required compiler options as specified in Required compiler options for HFZLANGX.

HFZSF8114S   txt1 required for source support - fatal

Explanation

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

System action

Processing is terminated.

User response

Recompile the module with the required compiler options as specified in Required compiler options for HFZLANGX.

HFZSF8115W   txt1 required for symbol support

Explanation

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

System action

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

User response

Recompile the module with the required compiler options as specified in Required compiler options for HFZLANGX.

HFZSF8116W   txt1 required for structure/union support

Explanation

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

System action

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

User response

Recompile the module with the required compiler options as specified in Required compiler options for HFZLANGX.

HFZSF8120W   txt1 detected. txt2 option assumed

Explanation

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

System action

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

User response

Use the correct compiler option, or make the compiler directive that adjusted the compiler option visible to HFZLANGX, as appropriate. If the problem persists, contact your service representative.

HFZSF8130S   File not found "txt1"

Explanation

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

System action

Processing is terminated.

User response

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

HFZSF8131S   Files not found "txt1", and "txt2"

Explanation

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

System action

Processing is terminated.

User response

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

HFZSF8132S   Input or Output file format invalid

Explanation

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

One or more preceding messages identify the reason for the failure or the file that was being processed when the error occurred. This message might be caused by error messages in the input compiler listing or missing required compiler options. For details on required compiler options, refer to Required compiler options for HFZLANGX.

System action

Processing is terminated.

User response

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

HFZSF8133S   File DD not allocated "txt1"

Explanation

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

System action

Processing is terminated.

User response

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

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

Explanation

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

System action

Processing is terminated.

User response

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

HFZSF8135S   txt1 file incorrectly defined

Explanation

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

System action

Processing is terminated.

User response

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 service representative.

HFZSF8136S   Premature txt1 End-of-File encountered

Explanation

HFZLANGX had begun to scan the txt1 file data, but the file ended before all expected data records had been scanned.

System action

Processing is terminated.

User response

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 service representative.

HFZSF8137S   txt1 disk/directory is full

Explanation

There is insufficient space to write more records to the txt1 file. The cause might be:
  • The PDS directory has no free entries.
  • The data set has the maximum number of extents.
  • There is insufficient free space on the DASD volume for another extent.

System action

Processing is terminated.

User response

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

HFZSF8138T   Insufficient virtual memory available

Explanation

There is insufficient free storage for HFZLANGX to continue processing.

System action

Processing is terminated.

User response

Free up virtual storage that is in use, or make more virtual storage available, as appropriate. If the problem persists, contact your service representative.
Note: HFZLANGX uses storage above the 16 MB line, if it is available.

HFZSF8139S   File is TERSEd or PACKed "txt1"

Explanation

The specified file has a fixed record format and a 1024-byte record length. It was likely compressed using TERSE or COPYFILE.

System action

Processing is terminated.

User response

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

HFZSF8150T   Maximum number of symbols exceeded

Explanation

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

System action

Processing is terminated.

User response

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

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

Explanation

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.

System action

Processing continues.

User response

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

HFZSF8158T   Invalid COBOL source column indicators - fatal

Explanation

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

System action

Processing is terminated.

User response

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

HFZSF8231S   Missing txt1 ESD information

Explanation

The name of a CSECT could not be determined.

System action

Processing continues, but analysis might be incomplete.

User response

Ensure that CSECTs are named in accordance with the requirements in Naming CSECTs for Z Abend Investigator.

HFZSF8233S   Unable to determine identity of unnamed PC Section

Explanation

The name of a CSECT could not be determined.

System action

Processing continues, but analysis might be incomplete.

User response

Ensure that CSECTs are named in accordance with the requirements in Naming CSECTs for Z Abend Investigator.

HFZSF8250A   SYSADATA input record record-number, invalid ESDID ignored

Explanation

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

System action

Processing continues.

User response

None