HZAC - Operation messages

These messages are issued by the HZAC - Computation phase.

Return codes

Table 1. Return codes and their meaning
Return code	Description
0	No errors encountered. All requests processed successfully.
16	Unrecoverable error. No requests processed. SYSIN or HZAPZIP or INQSOUT File cannot be used, or unsupported operating system.

Message suffix codes

Table 2. Message suffix codes and associated condition codes
Suffix	Meaning	Raises minimum condition code to:
I	Information message	0
W	Warning message	4
E	Error message	8
S	Severe error message	12
U	Unrecoverable error message	16

Message texts and explanations: All numeric completion codes of system services reported in these messages are in hexadecimal unless otherwise stated.

HZAC002E

A message is missing from the internal repository

A message is missing from the internal message repository. When the default language is not English, the translation of the given message might not exist. If the default language is English, the message indicates an error in the given application.

The application would normally continue ignoring the given message number, but the specific action depends on the code attempting to issue the message, which could also terminate the application.

Contact HCL support.

HZAC003U

The internal message repository is corrupted

When attempting to issue a message, the internal message repository layout did not follow the expected format.

The application terminates.

Contact HCL support.

HZAC020E

application-name encountered errors. Error code = errorcode

The Application has encountered errors during processing. This is a general message on completion indicating that an error has occurred.

Completes with given error code.

Refer to additional message, or to the section 6016, and to the log for more details on the specific error. Contact HCL support.

HZAC021S

application-name encountered fatal errors. Error code = error-code

The application has encountered fatal errors during processing.

Terminates with given error code.

Refer to additional message, or to the section 6016, and to the log for more details on the specific error. Contact HCL support.

HZAC023E

Inquisitor Import error occurred in opening: filename

The Inquisitor Import could not open the given file.

Terminates without processing any records.

Check that the file exists, and if it does, check for any additional log message identifying the error. Contact HCL support.

HZAC024E

Inquisitor Import input file is in error. It looks like a usage data file

The Inquisitor Import has encountered an invalid input file.

Terminates without processing any records.

Check that the input file is a valid file. Contact HCL support.

HZAC025E

Inquisitor Import input file is in error. It looks like a hardware data file

The Inquisitor Import has encountered an invalid input file.

Terminates without processing any records.

Check that the input file is a valid file. Contact HCL support.

HZAC026E

Inquisitor Import detected that table tablename is missing or invalid

The expected table is missing from the database or has invalid format. This suggests a mismatch between the database and this version of the product.

Terminates without processing any records.

Check for a version mismatch between the database and the version of the product. Contact HCL support.

HZAC027S

Inquisitor Import table tablename is missing a column

The given table is missing an expected column. This suggests a mismatch between the database and this version of the product.

The application terminates without processing any records.

Check for a version mismatch between the database and the version of the product. Contact HCL support.

HZAC028S

Inquisitor Import table tablename appears to be an old version

The given table in the database does not have the expected format.

The application terminates without processing any records.

Check for a version mismatch between the database and the version of the product. Contact HCL support.

HZAC029S

Inquisitor Import error when writing to table tablename

An SQL error occurred when attempting to write to the given table.

The application terminates.

Check the log for additional details about the given error. Contact HCL support.

HZAC030S

The Inquisitor Import did not find a valid system header record in the input file

The input file does not follow the expected format.

The application terminates.

Check that the correct input file is supplied and that there is no version mismatch. Contact HCL support.

HZAC034S

Error reading Repository TPARAM table

An error occurred while reading the TPARAM Repository table.

The application terminates.

Check the log for any additional messages indicating the cause of the error. Contact HCL support.

HZAC035E

The Repository is in use by the application-name

The application cannot run because the Repository is already in use by another application. Wait until application-name completes before running the current application. If the Repository is not in use by application-name, then the cause could be that it was previously run, but did not run to completion. To correct the problem, either rerun the application-name identified in this message, or alternatively, run the supplied HZASTPRM job to reset FVALUE to 0 where FKEY = PROCRUN in the TPARAM table.

The application terminates.

Check that the application is not already in use before running this application.

HZAC036E

Syntax error scanning TPARAMS file on line linenumber

The TPARAM file does not conform to the required syntax on the given line.

The specified option or value is ignored, and its default value is used where applicable.

Check that valid options/values are supplied as specified in the documentation of the application that you are running.

HZAC037E

Schema schemavalue is too long in param param

A schema ID that is too long has been specified.

The application terminates.

Check that the schema ID does not exceed 8 characters in length.

HZAC038E

Unbalanced quote for value: value in param:param

A starting quote that has no matching end quote was found for the given parameter.

The application terminates.

Check that the given parameter has matching quotes.

HZAC039E

Illegal character in value:value of param:param

An invalid character was found in the given value.

The application terminates.

Check that the given parameter value is valid for its type.

HZAC040E

Reserved word: reservedword in param: param

A reserved word or system value schema ID was chosen as a parameter value.

The application terminates.

Specify a different parameter value.

HZAC041W

value:value in param:param is not a recommended schema ID

The value is not recommended because of possible conflicts with existing values.

The application continues.

Choose a different value to avoid conflicts.

HZAC042E

TPARAM file: param:param has an invalid proposed value: value

The parameter cannot be set to the given value because the value is not valid.

The value is ignored, and the application continues.

Choose a valid value as per the documentation of the given application.

HZAC043E

The application has failed to open the TPARAM file. Error: errordescription

The application could not open the TPARAM file. The error description contains more details regarding the reason for the error.

The application terminates.

Check that the TPARAM file exists and is valid.

HZAC045E

String string cannot exceed numberchars in length

A parameter length limit has been exceeded.

The application terminates.

Ensure that the specified parameter length is not exceeded.

HZAC050E

The program-name program has detected an invalid date parameter

A date parameter was found to be invalid.

The application terminates.

Ensure that the date format is valid, and start dates do not overlap end dates.

HZAC051S

Error adding record

An SQL error occurred when adding a record to a table.

The application terminates.

Check the log for additional information about the error. Contact HCL support.

HZAC052S

Error updating record

An SQL error occurred when updating a record in a table.

The application terminates.

Check the log for additional information about the error. Contact HCL support.

HZAC053S

Error deleting record

An SQL error occurred when deleting a record from a table.

The application terminates.

Check the log for additional information about the error. Contact HCL support.

HZAC055S

Table initialization failure during Repository Merge

At least one table initialization failed when merging repositories.

The application terminates.

Check the log for any additional details about this error. Contact HCL support.

HZAC056S

Some table destination fields are smaller than source

Some fields in the target repository are not large enough to fit the contents of fields in the source repository.

The application terminates, and the repositories are not merged.

Check that the destination repository is not an older version than the source repository. You can recreate the destination repository using the latest version of the product. If the problem persists, contact HCL support.

HZAC057E

A value for parameter: parameter-name must be specified

A mandatory parameter for this application has not been specified.

The application terminates during the syntax checking of input parameters.

Ensure that a value for the given parameter is specified. Refer to the documentation of the failing application for an explanation of the given parameter and/or valid parameter values.

HZAC058E

Could not open filename

File could not be opened.

The application terminates.

Check the log for additional information about the error. Contact HCL support.

HZAC059E

Could not read filename

File could not be read.

The application terminates.

Check the log for additional information about the error. Contact HCL support.

HZAC060E

IQDATA DD does not contain unzipped IQ data

The input IQDATA dataset does not contain unzipped IQ data.

The application terminates.

Check the log for additional information about the error. Contact HCL support.

HZAC061E

Internal error hcreate(number) phase1a failed

An internal error has occurred.

The application terminates.

Check the log for additional information about the error. Contact HCL support.

HZAC062E

No SMF 30-2 or 30-4 data matched IQ data

No match was found for the SMF data and IQ data.

The application terminates.

Check that the correct data sets have been used. Contact HCL support.

HZAC063E

Internal error hsearch(key) table add failed

An error occurred when inserting data into a table.

The application terminates.

Check the log for additional information about the error. Contact HCL support.

HZAC064E

Could not write type to FMOUT

Could not write to file FMOUT.

The application terminates.

Check the log for additional information about the error. Contact HCL support.

HZAC065E

SYSUT1 data Is not IQ text or UM text

The SYSUT1 dataset does not contain the expected data.

The application terminates.

Check that the SYSUT1 dataset is correct. Contact HCL support.

HZAC066E

Internal error hsearch(key) table failed

An error occurred when retrieving data from a table.

The application terminates.

Check the log for additional information about the error. Contact HCL support.

HZAC067E

Unable to acquire storage

An error has occurred when attempting to acquire storage.

The application terminates.

Try increasing the region size specified in the region parameter on the JOB or EXEC statement in the JCL for the job. Contact HCL support.

HZAC068E

IBMMOD Internal error

An internal error has occurred.

The application terminates.

Check the log for additional information about the error. Contact HCL support.

HZAC069E

IBMMOD_INIT internal error

An error occurred when retrieving data from a table.

The application terminates.

Check the log for additional information about the error. Contact HCL support.

HZAC070I

A full rematch will be performed

A full import and rematch will be performed, which will not try to exclude modules of unchanged libraries. The default behavior is to exclude such libraries from matching, which would normally lead to faster processing.

The program performs a full rematch, if any of the following is true :

If requested by the FULLREMATCH option.
When the specified inventory is not found, for example on the first run when the inventory has not yet been created, and no previous match was done.
If it is safer to perform a full rematch, as when a GKB change is detected or the REPLACEFULL option is in effect.

More specific details on why a full rematch is being performed, can be found in the log.

A full rematch of the data is performed. All libraries are processed.

Ensure that a FULLREMATCH and the REPLACEFULL options are not in effect for better performance, unless a full rematch is desired.

If this is the first run of the Inquisitor Import, or there has been recent a change to the GKB, then no action is necessary; the program will try on subsequent runs (subsequent to loading the current data into the repository) to exclude unchanged libraries.

HZAC071I

&number_modules modules in &number_libraries unchanged libraries were ignored

This is a report of the number of the modules and libraries that are ignored when the FULLREMATCH option is not in effect. Details of these ignored libraries are in the log.

None.

HZAC073E

Usage Import for system SID on time is a duplicate and will be ignored.

This input file has already been processed.

The file is not processed. Processing is terminated.

Provide an input file that is the output of a more recent Usage Monitor output.

HZAC074E

IQ input file dated time1 is earlier than the latest os_type scan for SID sid dated time2.

The input file is earlier than an an input file that was already processed for this system.

The file is not processed. Processing is terminated.

Provide an input file that is the output of a more recent Inquisitor scan.

HZAC075I

num_libs libraries containing num_modules modules are mirrors.

The program encountered mirror libraries, which are libraries that are identical in name and volume to libraries that the program previously processed on different SIDs.

The program records the names and locations of such libraries but does not process their contents of modules. The program displays the names of such libraries in the log, as well as their current and base SIDs.

This operation is normal as long as the repository is set up correctly to receive SIDs containing libraries that are unique in library and volume name except when they are copies or shared, and no other SIDs that do not conform to these rules were mistakenly placed into the repository. Refer to the Inquisitor Import description for more information. Refer to the log for a list of mirror libraries and their base SIDs. You can run the System Deletion Job to remove any SIDs that have been placed recently but incorrectly into this repository.

HZAC076I

IQ input file dated time is a duplicate of the last OS_TYPE scan for SID SID_NAME.

This input file has already been processed.

The program continues and the file is processed.

None.

HZAC077I

Analyzer initialization complete.

The Analyzer has started.

Processing continues.

None.

HZAC078I

Analyzer has now terminated.

The Analyzer has stopped.

Processing continues.

None.

HZAC079I

Analyzer is unable to display URL because gethostname returned a null string for the host name.

The analyzer attempted to get the host name of the system it is running on using the z/OS C/C++ gethostname library function and a null string was returned. This may happen if the TCP/IP TCPIP.DATA configuration file does not have a HOSTNAME statement.

The analyzer is unable to display the url that clients can use to access it in its log. The analyzer continues processing and listening for connections from clients.

Add a HOSTNAME statement to the TCP/IP TCPIP.DATA configuration file. In order for this change to have an effect, the TCP/IP address space must be stopped and restarted. Refer to the z/OS Communications Server: IP Configuration Reference for more information on the HOSTNAME statement, on the TCPIP.DATA configuration file, and how to modify them.

HZAC080I

Analyzer is unable to display URL because getaddrinfo for host hostName failed with errno errnoNumericValue, errnoDescriptionString.

The analyzer attempted to get the fully qualified domain name and IP address for the host it is running on, which is named hostName. The z/OS C/C++ getaddrinfo library function was used, and it returned the error number shown.

The analyzer is unable to display the URL that clients can use to access it in its log. The analyzer continues processing and listening for connections from clients.

Refer to the z/OS Communications Manager: IP and SNA Codes manual for a description of Resolver return codes. It is possible that the host name could not be resolved due to a Resolver configuration problem or a Domain Name System (DNS) configuration problem. Refer to z/OS Communications Server: IP Configuration Guide and the z/OS Communications Server: IP Configuration Reference for information about how to configure Resolver and the BIND 9-based Domain Name System.

HZAC081E

Incompatible GKB level for gkb schema:schema. Expected level:expected_level_number, received::received_level_number.

A mismatch between the GKB level and the level expected by the program was found. This indicates that the GKB and the code are at different maintenance levels. If the received_level_number is greater than the expected_level_number, it indicates that a later level of the GKB is used than can be handled by the current maintenance level of the code.

If the received_level_number is less than the expected_level_number, it indicates that an old level of the GKB, that can no longer be handled by the current maintenance level of the code, is used.

The application terminates.

Apply GKB and code maintenance to the indicated GKB schema as required to ensure code and GKB are compatible. Contact HCL support for further assistance.

HZAC082E

Incompatible repository level for repository schema: schema. Expected level:expected_level_number, received::received_level_number.

A mismatch between the Database repository level and the level expected by the program was found. This indicates that the repository and the code are at different maintenance levels. If the received_level_number is greater than the expected_level_number, it indicates that a later level of the repository is used than can be handled by the current maintenance level of the code.

If the received_level_number is less than the expected_level_number, it indicates that an old level of the repository, that can no longer be handled by the current maintenance level of the code, is used.

The application terminates.

Apply Database repository and code maintenance to the indicated repository schema as required to ensure code and repository are compatible. Contact HCL support for further assistance.

HZAC083I

GKB schema: schema of version date:gkb_date is out of date. It is more than number of months old.

The used GKB of the given schema name is likely to be superseded and can be replaced by a more recent GKB containing more product updates. The GKB that is used is older than the default value of the number_of_months from the current date which means the latest identification changes may be missed.

The application continues.

Apply GKB maintenance as soon as possible.

HZAC084E

GKB schema: schema is missing configuration parameters.

The used GKB of the given schema name is missing configuration parameters that the program needs. This is most likely to occur if the GKB has not been loaded successfully.

The application terminates.

Ensure GKB is loaded successfully. Contact HCL support if the problem persists.

HZAC085E

GKB schema: schema does not have any scorecards.

The used GKB of the given schema name does not have any scorecards that can be used to match discovered modules. This is most likely to occur if the GKB has not been loaded successfully.

The application terminates.

Ensure GKB is loaded successfully. Contact HCL support if the problem persists.

HZAC086S

SCRT Import detected a configuration error.

An error occurred while reading the TPARAM dataset.

The application terminates.

Check the log for any additional messages indicating the cause of the error. Contact HCL support.

HZAC087E

SCRT Import detected an input data error.

The SCRT CSV file is invalid or does not follow the expected format.

The application terminates.

Check the log for additional information about the error. Contact HCL support.

HZAC088E

SCRT Import detected a database error.

An SQL error occurred.

The application terminates.

Check the log for additional information about the error. Contact HCL support.

HZAC089W

Hardware serial serial does not exist in the ZAO database.

The hardware serial has not been discovered by Inquisitor Import or Usage Monitor.

The application continues; SCRT data will not be imported for this hardware serial.

Ensure Inquisitor Import and Usage Monitor are run for the desired hardware serial prior to running SCRT Import.

HZAC090W

The following Systems do not exist in the ZAO database: systems

The systems have not been discovered by Inquisitor Import or Usage Monitor.

The application continues; SCRT data will not be imported for the systems.

Ensure Inquisitor Import and Usage Monitor are run for the desired systems prior to running SCRT Import.

HZAC091W

The following Products do not exist in the current GKB: products

The products could not be located in the current GKB.

The application continues; SCRT data will not be imported for the products.

Contact HCL support, supply the missing products information from the log, and request a GKB refresh.