HSIC - Operation messages

These messages are issued by the HSIC - 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.
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.

HSIC002E

A message is missing from the internal repository

Explanation: 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.
System action: 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.
Operator response: Contact IBM support.

HSIC003U

The internal message repository is corrupted

Explanation: When attempting to issue a message, the internal message repository layout did not follow the expected format.
System action: The application terminates.
Operator response: Contact IBM support.

HSIC020E

application-name encountered errors. Error code = errorcode

Explanation: The Application has encountered errors during processing. This is a general message on completion indicating that an error has occurred.
System action: Completes with given error code.
Operator response: Refer to additional message, or to the section 6016, and to the log for more details on the specific error. Contact IBM support.

HSIC021S

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

Explanation: The application has encountered fatal errors during processing.
System action: Terminates with given error code.
Operator response: Refer to additional message, or to the section 6016, and to the log for more details on the specific error. Contact IBM support.

HSIC023E

Inquisitor Import error occurred in opening: filename

Explanation: The Inquisitor Import could not open the given file.
System action: Terminates without processing any records.
Operator response: Check that the file exists, and if it does, check for any additional log message identifying the error. Contact IBM support.

HSIC024E

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

Explanation: The Inquisitor Import has encountered an invalid input file.
System action: Terminates without processing any records.
Operator response: Check that the input file is a valid file. Contact IBM support.

HSIC025E

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

Explanation: The Inquisitor Import has encountered an invalid input file.
System action: Terminates without processing any records.
Operator response: Check that the input file is a valid file. Contact IBM support.

HSIC026E

Inquisitor Import detected that table tablename is missing or invalid

Explanation: 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.
System action: Terminates without processing any records.
Operator response: Check for a version mismatch between the database and the version of the product. Contact IBM support.

HSIC027S

Inquisitor Import table tablename is missing a column

Explanation: The given table is missing an expected column. This suggests a mismatch between the database and this version of the product.
System action: The application terminates without processing any records.
Operator response: Check for a version mismatch between the database and the version of the product. Contact IBM support.

HSIC028S

Inquisitor Import table tablename appears to be an old version

Explanation: The given table in the database does not have the expected format.
System action: The application terminates without processing any records.
Operator response: Check for a version mismatch between the database and the version of the product. Contact IBM support.

HSIC029S

Inquisitor Import error when writing to table tablename

Explanation: An SQL error occurred when attempting to write to the given table.
System action: The application terminates.
Operator response: Check the log for additional details about the given error. Contact IBM support.

HSIC030S

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

Explanation: The input file does not follow the expected format.
System action: The application terminates.
Operator response: Check that the correct input file is supplied and that there is no version mismatch. Contact IBM support.

HSIC034S

Error reading Repository TPARAM table

Explanation: An error occurred while reading the TPARAM Repository table.
System action: The application terminates.
Operator response: Check the log for any additional messages indicating the cause of the error. Contact IBM support.

HSIC035E

The Repository is in use by the application-name

Explanation: 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 HSISTPRM job to reset FVALUE to 0 where FKEY = PROCRUN in the TPARAM table.
System action: The application terminates.
Operator response: Check that the application is not already in use before running this application.

HSIC036E

Syntax error scanning TPARAMS file on line linenumber

Explanation: The TPARAM file does not conform to the required syntax on the given line.
System action: The specified option or value is ignored, and its default value is used where applicable.
Operator response: Check that valid options/values are supplied as specified in the documentation of the application that you are running.

HSIC037E

Schema schemavalue is too long in param param

Explanation: A schema ID that is too long has been specified.
System action: The application terminates.
Operator response: Check that the schema ID does not exceed 8 characters in length.

HSIC038E

Unbalanced quote for value: value in param:param

Explanation: A starting quote that has no matching end quote was found for the given parameter.
System action: The application terminates.
Operator response: Check that the given parameter has matching quotes.

HSIC039E

Illegal character in value:value of param:param

Explanation: An invalid character was found in the given value.
System action: The application terminates.
Operator response: Check that the given parameter value is valid for its type.

HSIC040E

Reserved word: reservedword in param: param

Explanation: A reserved word or system value schema ID was chosen as a parameter value.
System action: The application terminates.
Operator response: Specify a different parameter value.

HSIC041W

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

Explanation: The value is not recommended because of possible conflicts with existing values.
System action: The application continues.
Operator response: Choose a different value to avoid conflicts.

HSIC042E

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

Explanation: The parameter cannot be set to the given value because the value is not valid.
System action: The value is ignored, and the application continues.
Operator response: Choose a valid value as per the documentation of the given application.

HSIC043E

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

Explanation: The application could not open the TPARAM file. The error description contains more details regarding the reason for the error.
System action: The application terminates.
Operator response: Check that the TPARAM file exists and is valid.

HSIC045E

String string cannot exceed numberchars in length

Explanation: A parameter length limit has been exceeded.
System action: The application terminates.
Operator response: Ensure that the specified parameter length is not exceeded.

HSIC050E

The program-name program has detected an invalid date parameter

Explanation: A date parameter was found to be invalid.
System action: The application terminates.
Operator response: Ensure that the date format is valid, and start dates do not overlap end dates.

HSICS

Error adding record

Explanation: An SQL error occurred when adding a record to a table.
System action: The application terminates.
Operator response: Check the log for additional information about the error. Contact IBM support.

HSIC052S

Error updating record

Explanation: An SQL error occurred when updating a record in a table.
System action: The application terminates.
Operator response: Check the log for additional information about the error. Contact IBM support.

HSIC053S

Error deleting record

Explanation: An SQL error occurred when deleting a record from a table.
System action: The application terminates.
Operator response: Check the log for additional information about the error. Contact IBM support.

HSIC055S

Table initialization failure during Repository Merge

Explanation: At least one table initialization failed when merging repositories.
System action: The application terminates.
Operator response: Check the log for any additional details about this error. Contact IBM support.

HSIC056S

Some table destination fields are smaller than source

Explanation: Some fields in the target repository are not large enough to fit the contents of fields in the source repository.
System action: The application terminates, and the repositories are not merged.
Operator response: 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 IBM support.

HSIC057E

A value for parameter: parameter-name must be specified

Explanation: A mandatory parameter for this application has not been specified.
System action: The application terminates during the syntax checking of input parameters.
Operator response: 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.

HSIC058E

Could not open filename

Explanation: File could not be opened.
System action: The application terminates.
Operator response: Check the log for additional information about the error. Contact IBM support.

HSIC059E

Could not read filename

Explanation: File could not be read.
System action: The application terminates.
Operator response: Check the log for additional information about the error. Contact IBM support.

HSIC060E

IQDATA DD does not contain unzipped IQ data

Explanation: The input IQDATA dataset does not contain unzipped IQ data.
System action: The application terminates.
Operator response: Check the log for additional information about the error. Contact IBM support.

HSIC061E

Internal error hcreate(number) phase1a failed

Explanation: An internal error has occurred.
System action: The application terminates.
Operator response: Check the log for additional information about the error. Contact IBM support.

HSIC062E

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

Explanation: No match was found for the SMF data and IQ data.
System action: The application terminates.
Operator response: Check that the correct data sets have been used. Contact IBM support.

HSIC063E

Internal error hsearch(key) table add failed

Explanation: An error occurred when inserting data into a table.
System action: The application terminates.
Operator response: Check the log for additional information about the error. Contact IBM support.

HSIC064E

Could not write type to FMOUT

Explanation: Could not write to file FMOUT.
System action: The application terminates.
Operator response: Check the log for additional information about the error. Contact IBM support.

HSIC065E

SYSUT1 data Is not IQ text or UM text

Explanation: The SYSUT1 dataset does not contain the expected data.
System action: The application terminates.
Operator response: Check that the SYSUT1 dataset is correct. Contact IBM support.

HSIC066E

Internal error hsearch(key) table failed

Explanation: An error occurred when retrieving data from a table.
System action: The application terminates.
Operator response: Check the log for additional information about the error. Contact IBM support.

HSIC067E

Unable to acquire storage

Explanation: An error has occurred when attempting to acquire storage.
System action: The application terminates.
Operator response: Try increasing the region size specified in the region parameter on the JOB or EXEC statement in the JCL for the job. Contact IBM support.

HSIC068E

IBMMOD Internal error

Explanation: An internal error has occurred.
System action: The application terminates.
Operator response: Check the log for additional information about the error. Contact IBM support.

HSIC069E

IBMMOD_INIT internal error

Explanation: An error occurred when retrieving data from a table.
System action: The application terminates.
Operator response: Check the log for additional information about the error. Contact IBM support.

HSIC070I

A full rematch will be performed

Explanation: 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.

System action: A full rematch of the data is performed. All libraries are processed.
Operator response: 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.

HSIC071I

&number_modules modules in &number_libraries unchanged libraries were ignored.

Explanation: 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.
System action: None.
Operator response: None.

HSIC073E

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

Explanation: This input file has already been processed.
System action: The file is not processed. Processing is terminated.
Operator response: Provide an input file that is the output of a more recent Usage Monitor output.

HSIC074E

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

Explanation: The input file is earlier than an input file that was already processed for this system.
System action: The file is not processed. Processing is terminated.
Operator response: Provide an input file that is the output of a more recent Inquisitor scan.

HSIC075I

num_libs libraries containing num_modules modules are shared.

Explanation: The program encountered shared libraries, which are libraries that are identical in name and volume to libraries that the program previously processed on different SIDs.
System action: 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.
Operator response: 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 shared 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.

HSIC076I

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

Explanation: This input file has already been processed.
System action: The program continues and the file is processed.
Operator response: None.

HSIC077I

Analyzer initialization complete.

Explanation: The Analyzer has started.
System action: Processing continues.
Operator response: None.

HSIC078I

Analyzer has now terminated.

Explanation: The Analyzer has stopped.
System action: Processing continues.
Operator response: None.

HSIC079I

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

Explanation: 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.
System action: 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.
Operator response: 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.

HSIC080I

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

Explanation: 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.
System action: 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.
Operator response: 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.

HSIC081E

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

Explanation: 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.

System action: The application terminates.
Operator response: Apply GKB and code maintenance to the indicated GKB schema as required to ensure code and GKB are compatible. Contact IBM support for further assistance.

HSIC082E

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

Explanation: 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.

System action: The application terminates.
Operator response: Apply Database repository and code maintenance to the indicated repository schema as required to ensure code and repository are compatible. Contact IBM support for further assistance.

HSIC083I

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

Explanation: 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.
System action: The application continues.
Operator response: Apply GKB maintenance as soon as possible.

HSIC084E

GKB schema: schema is missing configuration parameters.

Explanation: 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.
System action: The application terminates.
Operator response: Ensure GKB is loaded successfully. Contact IBM support if the problem persists.

HSIC085E

GKB schema: schema does not have any scorecards.

Explanation: 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.
System action: The application terminates.
Operator response: Ensure GKB is loaded successfully. Contact IBM support if the problem persists.

HSIC086S

SCRT Import detected a configuration error.

Explanation: An error occurred while reading the TPARAM dataset.
System action: The application terminates.
Operator response: Check the log for any additional messages indicating the cause of the error. Contact IBM support.

HSIC087E

SCRT Import detected an input data error.

Explanation: The SCRT CSV file is invalid or does not follow the expected format.
System action: The application terminates.
Operator response: Check the log for additional information about the error. Contact IBM support.

HSIC088E

SCRT Import detected a database error.

Explanation: An SQL error occurred.
System action: The application terminates.
Operator response: Check the log for additional information about the error. Contact IBM support.

HSIC089W

Hardware serial serial does not exist in the TADzZ SW Asset Mgmt database.

Explanation: The hardware serial has not been discovered by Inquisitor Z SW Asset Mgmt or Usage Monitor.
System action: The application continues; SCRT data will not be imported for this hardware serial.
Operator response: Ensure Inquisitor Import and Usage Monitor are run for the desired hardware serial prior to running SCRT Import.

HSIC090W

The following Systems do not exist in the TADzZ SW Asset Mgmt database: systems

Explanation: The systems have not been discovered by Inquisitor Z SW Asset Mgmt or Usage Monitor.
System action: The application continues; SCRT data will not be imported for the systems.
Operator response: Ensure Inquisitor Import and Usage Monitor are run for the desired systems prior to running SCRT Import.

HSIC091W

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

Explanation: The products could not be located in the current GKB.
System action: The application continues; SCRT data will not be imported for the products.
Operator response: Contact IBM support, supply the missing products information from the log, and request a GKB refresh.

HSIC092W

Node with plant: plant serial: serial type: type does not exist in the IBM database.

Explanation:

No node with the plant, serial, and type provided by SCRT data has been discovered by Inquisitor Import or Usage Monitor.

System action:

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

Operator response:

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