KFA messages
Messages that begin with the KFA prefix are associated with the Tivoli Enterprise Monitoring Server on both z/OS® and distributed platforms.
KFAAL00E INVALID SE LOCK STATE IN module COUNTER=lockcounter
Explanation
An invalid state was detected in a shared or exclusive lock control block. An internal error has occurred that may cause integrity errors on shared resource access. The module value indicates the module where the problem was detected. The lockcounter value specifies the number of shared locks in progress. A lockcounter value of -1 means that a single user has an exclusive lock. A value of 0 means that no locks are in progress.
System action
Processing continues.
User response
Contact IBM® Software Support.
KFAA001W KFAASITR LOOKUP TABLE NOT LOADED
Explanation
The alert automation environment could not be initialized, and the Situation Trap table could not be loaded into storage for alert processing.
System action
Alert automation is disabled. No alerts are issued when events are detected.
User response
Review the messages issued before this message to determine the cause of environment initialization failure. This message is normal if no entries are specified in the KFAASITR runtime parameter file or if no KFAASITR parameter file is found.
KFAA002E THREAD CREATION ERROR ERROR= errno
Explanation
An attempt to start a thread of execution has failed. Threads are used to distribute action requests to alert emitters. The errno value indicates the status code issued by the POSIX pthread_create function.
System action
No further action is taken to transmit the action request to the alert emitter.
User response
Determine whether POSIX threading restrictions prevent the thread creation. If restrictions cannot be determined, contact IBM Software Support.
KFAA003E GET LOCK ERROR=status
Explanation
An attempt to acquire a lock (pthread_mutex_lock) has failed. POSIX mutex locks are used to serialize access and update to internal control blocks shared by multiple threads of execution. The status value indicates the error code issued by the POSIX pthread_mutex_lock function.
System action
Alert processing is terminated. No further action requests are sent to the alert emitter.
User response
Contact IBM Software Support.
KFAA004E COMMAND BUFFER OVERFLOW SITUATION=sitname DESTNODE=destnode ARG=arg
Explanation
An attempt to format the command string to be executed by an alert emitter has overflowed the internal buffer. The sitname and arg values indicate, respectively, the situation and argument being processed. The destnode value specifies the alert emitter.
System action
Alert processing for the event is terminated.
User response
Reduce the amount of data substituted into the command string by eliminating unnecessary attributes from the ARG n values specified for this event in the Situation Trap table (KFAASITR). If this error cannot be corrected, contact IBM Software Support.
KFAA005S UNABLE TO ALLOCATE KFAASITR TABLE
Explanation
An attempt to allocate a control block for the alert automation environment has failed. This error can occur when virtual storage is constrained.
System action
The automation environment cannot be initialized, and alert processing is disabled.
User response
Determine why the storage constraint occurred. If possible, increase storage limits for all the environments to be initialized, and then restart the Tivoli Enterprise Monitoring Server.
KFAA006S UNABLE TO INITIALIZE lockname ERRNO=status
Explanation
An attempt to initialize a lock (phtread_mutext_init) has failed. POSIX locks are used to serialize access and update to control blocks shared by multiple threads of execution. The lockname value specifies the lock whose initialization failed. The status value indicates the POSIX error code.
System action
No further attempt is made to initialize the lock, and alert automation initialization terminates. Alerts are not transmitted to alert emitters.
User response
Contact IBM Software Support.
KFAA008W KFAASITR LOOKUP TABLE IS EMPTY
Explanation
No destination node entries for alert emitters were specified in the Situation Trap table. This is a warning message.
System action
Alert automation is disabled until the table is refreshed.
User response
If alert automation is desired, review the contents of the Situation Trap table file, KFAASITR. Correct any syntax errors reported by messages issued previous to this message. After you correct the KFAASITR file, issue a KFAASITR REFRESH console command (z/OS Tivoli Enterprise Monitoring Server only) or restart the SMAF process to activate the new situation traps.
KFAA009W KFAASITR COULD NOT BE OPENED
Explanation
The Situation Trap table (KFAASITR file) could
not be found in the runtime parameter persistent data store (z/OS Tivoli Enterprise Monitoring Server)
or the /tables directory (UNIX Tivoli Enterprise Monitoring Server).
This is a warning message.
System action
Alert automation is disabled until the table is refreshed.
User response
If alert automation is desired, ensure that the Situation Trap table file KFAASITR exists and contains at least one destination node entry. After the KFAASITR file has been created, issue a KFAASITR REFRESH console command (z/OS Tivoli Enterprise Monitoring Server only) or restart the SMAF process to activate the new situation traps.
KFAA010E DESTNODE NOT SPECIFIED IN LINE line NEAR token
Explanation
The DESTNODE tag was not specified in an entry for the Situation Trap table (KFAASITR file). The DESTNODE tag must be specified for each entry in the table. The line value specifies the line number in the KFAASITR runtime parameter file in which the error was detected. The token value indicates text near the entry where the destination node was not specified.
System action
The current entry is ignored, and processing continues with the next entry in the table.
User response
Correct the invalid Situation Trap table entry by ensuring that a DESTNODE tag is specified. Also ensure that each entry ends with a semicolon (;).
KFAA011E INVALID KFAASITR PARM=parm
Explanation
An unexpected KFAASITR command parameter was specified.
A MODIFY command issued to the z/OS Tivoli
Enterprise Monitoring Server address space has the following
syntax:
MODIFY cmsjobname,CTDS KFAASITR parm
- REFRESH: Reread the contents of the KFAASITR file to reinitialize the Situation Trap table.
- DISPLAY: Display the current contents of the Situation Trap table in memory.
- TESTSIT: Simulate the detection of a situation (named TestSituation) to verify proper operation of the alert automation environment and the alert emitters.
System action
The KFAASITR console command is ignored.
User response
Change the KFAASITR command parameter to one of those listed above.
KFAA012W UNABLE TO ESTABLISH KFAASITR COMMAND STATUS=status REASON=reason
Explanation
An attempt to establish the KFAASITR console command in an z/OS Tivoli Enterprise Monitoring Server environment has failed. The status and reason values indicate the status code and reason issued by the internal service function, OPER_DefineCommand.
System action
The KFAASITR command will not be accepted for the life of the z/OS Tivoli Enterprise Monitoring Server address space.
User response
Contact IBM Software Support.
KFAA013E MISSING SEMICOLON IN LINE line NEAR token
Explanation
The end of the KFAASITR file containing Situation Trap table entries was found before the last entry in the table ended with a semicolon. The line value specifies the line number in the KFAASITR runtime parameter file in which the error was detected. The token value indicates text near the entry where the destination node was not specified. This is a warning message.
System action
The last entry is processed and accepted if no syntax errors are detected.
User response
Review the KFAASITR file and ensure that all entries in the file end with a semicolon (;).
KFAA014W MULTIPLE VALUES DETECTED FOR tage IN LINE line NEW VALUE=new OLD=old CHECK SEMICOLONS
Explanation
A duplicate tag was found for an entry in the Situation Trap table KFAASITR.
System action
The last value for the tag is accepted for the entry.
User response
Review the contents of the KFAASITR file and ensure that a single value is specified for each tag. Also check to ensure that all entries in the file end with a semicolon (;).
KFAA015E UNABLE TO LOAD mod entry STATUS=status REASON=reason
Explanation
An attempt to load a module into storage or to locate the address of a module in storage has failed. The mod entry value specifies the name of the module that could not be loaded. The status value is the STC1 status code associated with the error. The reason value is the RSN1 reason code associated with the error.
System action
The call to the module is aborted.
User response
Ensure that the libraries have been properly installed and configured. Contact IBM Software Support.
KFAA020E INVALID LENGTH=length FOR tag="value" IN LINE reason
Explanation
The value specified for a tag in the Situation Trap table KFAASITR has exceeded the maximum length for the tag. The maximum length varies for each tag. The length value specifies the maximum length acceptable for the tag. The tag and its value are specified in tag and value. The line value specifies the line number in the KFAASITR runtime parameter file in which the error was detected.
System action
The tag is ignored, and syntax checking continues with the next tag for the current entry. The current entry is not accepted.
User response
Correct the invalid length. After you update
the KFAASITR file, issue a KFAASITR REFRESH console
command (z/OS Tivoli
Enterprise Monitoring Server only) or restart the SMAF process
to activate the new situation traps.
KFAA021E INVALID VALUE FOR tag=value IN LINE line
Explanation
The value specified for a tag in the Situation Trap table KFAASITR is not acceptable. The tag and the value specified for it are shown in tag and value. The ling value specifies the line number in the KFAASITR runtime parameter file in which the error was detected.
System action
The tag is ignored, and syntax checking continues with the next tag for the current entry. The current entry is not accepted.
User response
Correct the invalid value. After the KFAASITR
file has been updated, issue a KFAASITR REFRESH console
command (z/OS Tivoli
Enterprise Monitoring Server only) or restart the SMAF process
to activate the new situation traps.
KFAA022E INVALID SYNTAX: badtag IN LINE line
Explanation
A tag specified in the Situation Trap table KFAASITR is not acceptable. The badtag value specifies the unexpected entry. The line value specifies the line number in the KFAASITR runtime parameter file in which the error was detected.
System action
The tag is ignored, and syntax checking continues with the next tag for the current entry. The current entry is not accepted.
User response
Correct the invalid tag. Ensure that the tag
is spelled properly and specified in upper case. After you update
the KFAASITR file, issue a KFAASITR REFRESH console
command (z/OS Tivoli
Enterprise Monitoring Server only) or restart the SMAF process
to activate the new situation traps.
KFAA023E UNABLE TO ALLOCATE tag=value
Explanation
The storage required to store the value associated with a tag in the Situation Trap table KFAASITR could not be allocated. The tag and its value are specified in tag and value.
System action
The tag is ignored, and syntax checking continues with the next tag for the current entry. The current entry is not accepted.
User response
Correct the invalid value. Ensure that the tag
is spelled properly and specified in upper case. After you update
the KFAASITR file, issue a KFAASITR REFRESH console
command (z/OS Tivoli
Enterprise Monitoring Server only) or restart the SMAF process
to activate the new situation traps.
KFAA024E ENDING QUOTE FOR TAG VALUE NOT FOUND IN LINE line
Explanation
The value specified for an entry in the Situation Trap table KFAASITR was not properly enclosed in quotes.
System action
The tag is ignored, and syntax checking continues with the next tag for the current entry. The current entry is not accepted. The line value specifies the line number in the KFAASITR runtime parameter file in which the error was detected.
User response
Make sure that end quotes are specified in quoted
values. Strings enclosed in quotes are processed as specified, and
no attribute substitution is performed for these values (if tags are
ARG1-ARG9). After you update the KFAASITR file, issue a KFAASITR
REFRESH console command (z/OS Tivoli
Enterprise Monitoring Server only) or restart the SMAF process
to activate the new situation traps.
KFAA025E WILDCARD NOT ALLOWED IN tag=value IN LINE line
Explanation
An asterisk was specified in the value associated with a tag in the Situation Trap table KFAASITR, but the value for this tag cannot be a wildcard. The tag and its specified value are shown in tag and value. The line value specifies the line number in the KFAASITR runtime parameter file in which the error was detected.
System action
The tag is ignored, and syntax checking continues with the next tag for the current entry. The current entry is not accepted.
User response
Correct the invalid value. After you update the
KFAASITR file, issue a KFAASITR REFRESH console command
(z/OS Tivoli Enterprise Monitoring
Server only) or restart the SMAF process to activate the new situation
traps.
KFAA026E TOO MANY WILDCARDS IN tag=value IN LINE line
Explanation
Two or more asterisks were specified in the value associated with a tag in the Situation Trap table KFAASITR, but only a single wildcard character is acceptable. The tag and its specified value are shown in tag and value. The line value specifies the line number in the KFAASITR runtime parameter file in which the error was detected.
System action
The tag is ignored, and syntax checking continues with the next tag for the current entry. The current entry is not accepted.
User response
Correct the invalid value. After you update the
KFAASITR file, issue a KFAASITR REFRESH console command
(z/OS Tivoli Enterprise Monitoring
Server only) or restart the SMAF process to activate the new situation
traps.
KFAA030E oper SQL ERROR ON hdsee sql1api STATUS=status
Explanation
An attempt to transmit an action request to an alert emitter has failed during SQL processing. The oper value specifies the SQL operation which failed. The sql1api value specifies the SQL1 service function which failed. The status value specifies the SQL1 status code returned by the function.
System action
The alert automation action is terminated, and no further attempt is made to transmit the request to the alert emitter.
User response
Contact IBM Software Support.
KFAA040I ACTION STARTED FOR SITNAME=sitname DESTNODE=destnode STATE=state REQUESTID=requestid
Explanation
An alert automation action request has been successfully transmitted to an alert emitter. This is an informational message.
The sitname value
specifies the situation associated with the alert. The destnode value
specifies the alert emitter. The state value specifies
the current state of the associated event:
- 1 The situation has become true.
- 2 The situation has become false.
System action
The alert emitter proceeds to issue alerts or execute automation scripts for the alert.
User response
None.
KFAA041I TEMS=commandstring
Explanation
This informational message follows message KFAA040I. The commandstring value specifies the formatted command string transmitted to the alert emitter.
System action
The alert emitter proceeds to issue alerts or execute automation scripts for the alert.
User response
None.
KFAA042E NO RESPONSE FROM DESTNODE=destnode FOR SITNAME=sitname ORIGINNODE=originnode STATE=state ERRNO=status REQUESTID=reqid
Explanation
This message follows messages KFAA040I and KFAA041I. No response was received within 60 seconds from the alert emitter responsible for alert automation requests.
The destnode value
specifies the alert emitter. The sitname value
specifies the situation associated with the alert. The originnode value
specifies the node from which the situation event was collected. The state value
specifies the current state of the associated event:
- 1 The situation has become true.
- 2 The situation has become false.
System action
No further action is taken to determine the final disposition of the alert action request.
User response
End-user automation scripts must be written to complete execution as soon as possible. If automation scripts cannot complete within 60 seconds, a new thread of execution should be started by the automation script so that the successful response of automation can be recorded in the Tivoli Enterprise Monitoring Server message log. If this error persists, review the execution log provided by the alert emitter to determine whether automation failures have occurred.
KFAA050I ACTION COMPLETED FOR SITNAME=sitname DESTNODE=destnode STATE=state RC=rc REQUESTID=requestid
Explanation
This informational message indicates the success or failure of an action request executed by an alert emitter, and marks the completion of the request.
The sitname value
specifies the situation associated with the alert. The destnode value
specifies the alert emitter. The state value specifies
the current state of the associated event:
- 1 The situation has become true.
- 2 The situation has become false.
- Zero: Successful completion. Other Automation or alert processing failure. You can find further information about the failure in the message log of the alert emitter.
- 2: The situation has become false.
System action
No further processing is performed for the event.
User response
None.
KFAA051W DESTNODE=destnode OFFLINE FOR SITNAME=sitname ORIGINNODE=originnode STATE=state REQUESTID=requestid
Explanation
An attempt to distribute an action request to an alert emitter has failed because the alert emitter is off-line and cannot be reached.
The destnode value
specifies the alert emitter. The sitname value
specifies the situation associated with the alert. The originnode value
specifies the node from which the situation event was collected. The state value
specifies the current state of the associated event:
- 1 The situation has become true.
- 2 The situation has become false.
System action
No further action is taken to transmit the action request to the alert emitter.
User response
If this message persists, ensure that the alert emitter is started and registered with the Tivoli Enterprise Monitoring Server. If the alert emitter is properly started, an entry for the emitter will appear in the Nodes folder on the Candle Management Workstations desktop.
If the emitter continues to remain off-line and alerts no longer need to be distributed to the emitter, update the Situation Trap table KFAASITR to remove the entry for the off-line alert emitter. After you update the KFAASITR file, issue a KFAASITR REFRESH console command (Tivoli Enterprise Monitoring Server on z/OS only) or restart the SMAF process to activate the new situation traps.
KFAA060W UNABLE TO READ kdscnfg FILE
Explanation
An attempt to read the kdscnfg file
from the Tivoli
Enterprise Monitoring Server configuration file directory (/tables directory)
has failed.
System action
No connection to Tivoli Enterprise Monitoring Server can be established for alert automation processing. Alert processing is disabled.
User response
Ensure that the SMAF process is started from the proper directory and that the kdscnfg file is present. Restart Tivoli Enterprise Monitoring Server after corrections have been made.
KFAA070I USING TEMS NODE=nodename
Explanation
The Tivoli Enterprise Monitoring Server node specified in the nodename value will be used to issue action requests to alert emitters. This is an informational message.
System action
Alert automation environment initialization continues.
User response
None.
KFAA090I KFAASITR REFRESHED. STATUS=status
Explanation
This message is issued to indicate the completion of a KFAASITR REFRESH command (z/OS Tivoli Enterprise Monitoring Server only) to refresh the Situation Trap table. The status value indicates the status code issued by refresh processing:
System action
If a zero value for the status is displayed, a new Situation Trap table is established, and subsequent events are processed from the updated entries in the table.
User response
If a non-zero value for the status is displayed, determine the cause of the failure by reviewing messages issued before this message.
KFAA091I TESTSIT INVOKED. STATUS=status
Explanation
This message is issued to indicate the completion of a KFAASITR TESTSIT command (z/OS Tivoli Enterprise Monitoring Server only) to simulate the occurrence of a real event and to test the current Situation Trap table entries. The command triggers a dummy situation named TestSituation. The status value indicates the status code issued by test processing:
System action
If a zero value for the status is displayed, the Situation Trap table was searched and action requests were issued (if the simulated event matched any entries in the table).
User response
If a non-zero value for the status is displayed, determine the cause of the failure by reviewing messages issued before this message.
KFAA092I ACTIONS HAVE BEEN DISABLED
Explanation
An attempt to initialize the alert automation environment or to read the KFAASITR file to initialize the Situation Trap table has failed.
System action
Alert automation is disabled.
User response
Review messages issued before this message, and take appropriate action based on those messages.
KFAA093I ACTION ENVIRONMENT INITIALIZE
Explanation
This informational message indicates that the alert automation environment has been successfully initialized.
System action
Situation events matching those defined in the Situation Trap table will cause action requests to be distributed to alert emitters.
User response
None.
KFAA094I KFAASITR LOOKUP TABLE:
Explanation
This informational message is issued in response to a KFAASITR DISPLAY console command (z/OS Tivoli Enterprise Monitoring Server only).
System action
The current contents of the Situation Trap table follow this message.
User response
None.
KFAA095I IF SITNAME=sitname AND ORIGINNODE=originnode AND STATE=state THEN
Explanation
This informational message displays the situation event data required to match the current entry in the Situation Trap table.
The sitname value specifies the situation name or name pattern for the entry. An asterisk indicates a wildcard character. The originnode value specifies the source where the situation data was collected. An asterisk indicates a wildcard character. The state value specifies the current state of the situation required to match an event. Valid values are TRUE, FALSE, UNKNOWN, or ANY.
System action
Message KFAA096I follows this message to display the action and alert emitter assigned to situation events that match this entry.
User response
None.
KFAA096I DESTNODE=destnode CALLTYPE=calltype SCRIPT=script
Explanation
This informational message, which follows message KFAA095I, displays the alert emitter destination node and the method to be used by the alert emitter to deliver the alert.
The destnode value
specifies the alert emitter name. The calltype value
specifies the call method to be used to deliver action requests and
alerts to the alert emitter:
- Zero: An automation script (REXX exec) is executed by the alert emitter.
- Non-zero: The alert is forward to an alert subagent by the alert emitter.
System action
Message KFAA097I follows this message to display the action arguments to be passed to the alert emitter.
User response
None.
KFAA097I ARGn=value
Explanation
This informational message, which follows message KFAA096I, lists all arguments to be passed in the formatted command string transmitted to alert emitters.
System action
The next Situation Trap table entry follows.
User response
None.
KFAA100I STACK SIZES: OG=curr/hih2o CT=curr/hih2o SNMP=curr/hih2o
Explanation
This informational message is issued after all
Situation Trap table entries are displayed in response to a KFAASITR
REFRESH console command (z/OS Tivoli
Enterprise Monitoring Server only). The message displays the
number of elements cached for OG/z/OS, CT, and SNMP alert emitters.
The curr value indicates the current number of cached SQL1 requests stored. The hih2o value indicates the highwater mark of cached SQL1 requests created since the start of the Tivoli Enterprise Monitoring Server.
System action
None.
User response
None.
KFAA193E ACTION ENVIRONMENT INITIALIZATION ERROR=errno
Explanation
The action environment could not be initialized because of a POSIX pthread_once service routine failure. The errno value shows the error number.
System action
No further action is taken to initialize the environment.
User response
Contact IBM Software Support.
KFAA200E ACTION ENVIRONMENT NOT INITIALIZED DISPLAY COMMAND ENDED
Explanation
This message is issued when a console command to display the situation trap table (as defined by the KFAASITR runtime parameter file) could not be executed because the action environment failed to initialize.
System action
No further action is taken to display the situation trap table.
User response
Review the messages issued before this message, to determine the cause of environment initialization failure.
KFAOT001 Starting TEC Event Integration facility. Time = <variable>
Explanation
TEC Event Integration facility initialization in progress.
KFAOT002 TEC Event Integration facility started successfully.
Explanation
TEC Event Integration facility has started successfully.
KFAOT003 TEC Event Integration facility startup failed. status = <variable>.
Explanation
TEC Event Integration facility has failed to initialize.
KFAOT004 TEC Event Integration facility has ended.
Explanation
TEC Event Integration facility has ended.
KFAOT005 Load KFAOTTEV failed, status = <variable>. TEC Event Integration disabled.
Explanation
Unable to load KFAOTTEV. KFAOMTEC dll may be missing or corrupt.
KFAOT006 TEC Event Integration entered quiesced mode
Explanation
TEC Event Integration is refreshing the EIF configuration or mapping files or both.
KFAOT007 TEC Event Integration exited quiesced mode
Explanation
TEC Event Integration finished refreshing the EIF configuration or mapping files or both.
KFAOT008 TEC Event Integration not enabled. Refresh command ignored.
Explanation
TEC Event Integration is not enabled. The refresh command is ignored.
KFAOT009 Refresh of EIF config and/or mapping files is successful.
Explanation
The refresh operation is successful.
KFAOT010 Refresh of EIF config and/or mapping files failed. Status <variable>.
Explanation
The refresh operation failed. See the Tivoli
Enterprise Monitoring Server logs for details. The most common
status codes follow:
- 1
- Bad input.
- 5
- No members found.
- 7
- No memory.
- 8
- Library I/O or system call error.
KFAOT011 Event destination <variable> no longer valid for situation <variable>.
Explanation
The specified event destination is no longer defined.
KFAOT012 <variable> attribute file <variable> successfully refreshed.
Explanation
TEC Event Forwarder has successfully processed the new or updated attribute file.
KFAOT013 Load KFAOTRFH failed, status=<variable>. The TEC Event Integration product refreshing is disabled.
Explanation
Unable to load KFAOTRFH. The KFAOMTEC library may be missing or corrupt.
KFAS001 Product <variable> cannot be seeded.
Explanation
The indicated product could not be seeded, because a required Tivoli Enterprise Monitoring Server (TEMS) service could not be loaded.
System action
None.
User response
Contact IBM Software Support.
KFASD001 Detected that product <variable> version <variable> id <variable> id version <variable> support files manually installed.
Explanation
During startup, the Tivoli Enterprise Monitoring Server (TEMS) determined that the support files for the specified product were manually installed.
System action
None.
User response
None.
KFASD002 Detected that product <variable> version <variable> id <variable> id version <variable> support files manually removed.
Explanation
During startup, the Tivoli Enterprise Monitoring Server (TEMS) determined that the version and catalog support files for the specified product were manually removed.
System action
None.
User response
If the specified version of this product is still in use, manually re-install the support files for the product and restart the Tivoli Enterprise Monitoring Server. Otherwise, no action is required.
KFASD003 Detected that product version was manually changed from <variable> to <variable> for product <variable> id <variable> id version <variable>.
Explanation
During startup, the Tivoli Enterprise Monitoring Server (TEMS) determined that a different version of an existing product was manually installed.
System action
None.
User response
If the new product support version does not match your product version, install the correct support files and restart the Tivoli Enterprise Monitoring Server. Otherwise, no action is required.
KFASD004 Detected that catalog version <variable>,<variable> was manually replaced with version <variable>,<variable> for product <variable> version <variable> id <variable> id version <variable>.
Explanation
During startup, the Tivoli Enterprise Monitoring Server (TEMS) determined that the catalog file for an installed product was manually replaced with a different catalog.
System action
None.
User response
If the new product catalog version is incorrect, install the correct support files for the product and restart the Tivoli Enterprise Monitoring Server. Otherwise, no action is required.
KFASD005 Detected that the catalog is missing for product <variable> version <variable> id <variable> id version <variable>. Catalog version was <variable>,<variable>, state <variable>, status <variable>.
Explanation
During startup, the Tivoli Enterprise Monitoring
Server (TEMS) determined that the catalog for an installed product
was removed. The most common status codes (the value of the STATUS
column in the TAPPLPROPS table) and their descriptions are:
- 0
- Operation successful
- 1001
- Request queued
- 1002
- Out of memory
- 1003
- Bad argument
- 1004
- Not found
- 1005
- System error
- 1006
- Request for same product already in progress or queued
- 1007
- KT1 error
- 1008
- Self-Describing Agent (SDA) feature disabled at TEMS
- 1009
- Hub not there
- 1010
- TEMS shutdown in progress
- 1011
- Invalid content in manifest file
- 1012
- Wrong TEMS version
- 1013
- Unsupported feature
- 1014
- Unknown error
- 1015
- Bad input argument
- 1016
- Record updated by the manual install detection process
- 1017
- Temp install error, agent expected to retry install request
- 1018
- Error refreshing catalog files
- 1019
- Error refreshing attribute files
- 1020
- Error refreshing Omegamon2TEC files
- 1021
- Time expired waiting for SDA install completion
- 1022
- Seeding error
- 1023
- SDA not initialized due to config error
System action
None.
User response
If the specified product is still in use, manually reinstall the support files and restart the Tivoli Enterprise Monitoring Server. Otherwise, no action is required.
KFASD006 Detected failure state <variable>, status <variable>, in a prior auto install of product <variable> version <variable> id <variable> id version <variable>. State changed to <variable>.
Explanation
During startup, the Tivoli Enterprise Monitoring Server (TEMS) determined that a prior attempt to automatically install the indicated product failed. Use tacmd listappinstallrecs to display the STATE of the application install records. The most common status codes (the value of the STATUS column in the TAPPLPROPS table) and their descriptions are listed in the description of message KFASD005.
System action
None.
User response
Follow the instructions in the IBM Tivoli Monitoring (ITM) documentation for recovering from automatic product installation failures.
KFASD007 Detected failure STATE <variable>, STATUS <variable>, SEEDSTATE <variable>, in a prior auto install of PRODUCT <variable> VERSION <variable> ID <variable> IDVER <variable>.
Explanation
During startup, the Tivoli Enterprise Monitoring Server (TEMS) determined that a prior attempt to automatically install the indicated product failed. The most common status codes (the value of the STATUS column in the TAPPLPROPS table) and their descriptions are listed in the description of message KFASD005.
System action
None.
User response
Use tacmd listappinstallrecs to display the STATE of the application install records. Follow the instructions in the IBM Tivoli Monitoring (ITM) documentation for recovering from automatic product installation failures.
KFASD008 Detected an incomplete automatic install of product <variable> version <variable> id <variable> id version <variable>: state <variable>, status <variable>. State promoted to <variable>.
Explanation
During startup, the Tivoli Enterprise Monitoring Server (TEMS) determined that a prior attempt to automatically install the indicated product did not finish. The most common status codes (the value of the STATUS column in the TAPPLPROPS table) and their descriptions are listed in the description of message KFASD005.
System action
None.
User response
Use tacmd listappinstallrecs to display the STATE of the application install records. Follow the instructions in the IBM Tivoli Monitoring (ITM) documentation for recovering from automatic product installation failures.
KFASD009 Self-Describing Agent feature enabled on local TEMS.
Explanation
Initialization of the Self-Describing Agent (SDA) feature has successfully completed on the local Tivoli Enterprise Monitoring Server (TEMS) and is available for use.
System action
None.
User response
If you do not want SDA to be enabled on the local
TEMS, you must set the KMS_SDA=N environment variable.
Otherwise, no action is required.
KFASD010 Self-Describing Agent feature disabled on local TEMS.
Explanation
The Self-Describing Agent (SDA) feature is disabled
on the local Tivoli Enterprise Monitoring Server (TEMS) because the KMS_SDA=N environment
variable has been specified.
System action
None.
User response
If you want SDA to be enabled on the local TEMS,
you must set the KMS_SDA=Y environment variable.
Otherwise, no action is required.
KFASD011 Self-Describing Agent feature disabled on local TEMS because of error during initialization.
Explanation
The Self-Describing Agent (SDA) feature is disabled on the local Tivoli Enterprise Monitoring Server (TEMS) because an error occurred while the components of the SDA feature were being constructed and initialized.
System action
None.
User response
View the TEMS product log to find specific information pertaining to the SDA initialization error.
KFASD012 Self-Describing Agent feature disabled on local TEMS because TEMS_MANIFEST_PATH length <variable> exceeds maximum length <variable>
Explanation
The Self-Describing Agent (SDA) feature is disabled on the local Tivoli Enterprise Monitoring Server (TEMS) because the length of the directory value specified in the TEMS_MANIFEST_PATH environment variable exceeds the 512 character limit.
System action
None.
User response
If you want to use the SDA feature, you must ensure that a valid TEMS_MANIFEST_PATH environment variable has been specified in the TEMS configuration file.
KFASD013 Self-Describing Agent feature disabled on local TEMS because TEMS_MANIFEST_PATH not specified.
Explanation
The Self-Describing Agent (SDA) feature is disabled on the local Tivoli Enterprise Monitoring Server (TEMS) because a required environment variable, TEMS_MANIFEST_PATH, has not been specified to indicate the directory where SDA files should be installed.
System action
None.
User response
If you want to use the SDA feature, you must ensure that a valid TEMS_MANIFEST_PATH environment variable has been specified in the TEMS configuration file.
KFASD014 Self-Describing Agent feature disabled on local TEMS because Distributed Request Manager failed to initialize.
Explanation
The Self-Describing Agent (SDA) feature is disabled on the local Tivoli Enterprise Monitoring Server (TEMS) because a vital component of the SDA feature, the Distributed Request Manager, failed to initialize.
System action
None.
User response
View the TEMS product log to find specific information pertaining to the Distributed Request Manager initialization error.
KFASD015 Self-Describing Agent feature disabled on local TEMS because Notification Manager failed to initialize.
Explanation
The Self-Describing Agent (SDA) feature is disabled on the local Tivoli Enterprise Monitoring Server (TEMS) because a vital component of the SDA feature, the Notification Manager, failed to initialize.
System action
None.
User response
View the TEMS product log to find specific information pertaining to the Notification Manager initialization error.
KFASD016 Self-Describing Agent feature disabled on local TEMS because SDM Request Manager thread failed to initialize.
Explanation
The Self-Describing Agent (SDA) feature is disabled on the local Tivoli Enterprise Monitoring Server (TEMS) because a vital component of the SDA feature, the SDM Request Manager thread, failed to initialize.
System action
None.
User response
View the TEMS product log to find specific information pertaining to the SDM Request Manager thread initialization error.
KFASD017 Self-Describing Agent feature disabled on local TEMS because of failure to allocate <&1> bytes for SDM Communication Area.
Explanation
The Self-Describing Agent (SDA) feature is disabled on the local Tivoli Enterprise Monitoring Server (TEMS) because a vital component of the SDA feature, the SDM Communication Area, could not be allocated.
System action
None.
User response
View the TEMS product log to determine if there is a severe memory shortage problem in this TEMS or if there are other errors relevant to the inability to allocate the SDM Communication Area.
KFASD018 Self-Describing Agent feature has config <variable> at hub TEMS. SDA also being disabled at this remote TEMS.
Explanation
While (re)connecting to the hub Tivoli Enterprise Monitoring Server (TEMS), this remote TEMS detected that the Self-Describing Agent (SDA) feature is not enabled at the hub because the environment variable, KMS_SDA=N, has been specified at the hub. Therefore, the SDA feature must also be disabled at this remote TEMS to prevent SDA requests from being sent to the hub.
System action
None.
User response
If you require SDA support at this remote TEMS, you must ensure that KMS_SDA=Y is also specified at the associated hub TEMS.
KFASD019 Self-Describing Agent feature has config <variable> status <variable> at hub TEMS. SDA also being disabled at this remote TEMS.
Explanation
While (re)connecting to the hub Tivoli Enterprise Monitoring Server (TEMS), this remote TEMS detected that the Self-Describing Agent (SDA) feature is not enabled at the hub because of an error encountered during the hub's SDA initialization. Therefore, the SDA feature must also be disabled at this remote TEMS to prevent SDA requests from being sent to the hub.
System action
None.
User response
The error status code value from the hub can
be one of the following:
- SDA initialization failed
- ITM_HOME/CANDLEHOME directory not specified
- TEMS_MANIFEST_PATH env var not specified
- TEMS_MANIFEST_PATH directory length exceeds maximum
- TEMS_MANIFEST_PATH directory doesn't exist
- KMS_SDA env var contains unexpected value
- SDA Distributed Request Manager failed to initialize
- SDA Notification Manager failed to initialize
- Unable to create SDA Request Manager thread
- SDA disabled at HUB, disabling at RTEMS
- SDA error status at HUB, disabling at RTEMS
- SDA status unknown at HUB, disabling at RTEMS
- Unable to contact HUB for SDA status, disabling at RTEMS
- SDA Broadcast Request Manager failed to initialize
- Unable to create SDA Broadcast Manager thread
- KMS_SDA=N configured on local TEMS
- CMS_FTO=YES configured on local TEMS
KFASD020 Self-Describing Agent feature has config <variable> at hub TEMS. SDA also being disabled at this remote TEMS.
Explanation
While (re)connecting to the hub Tivoli Enterprise Monitoring Server (TEMS), this remote TEMS was not able to obtain the status of the Self-Describing Agent (SDA) feature at the hub. Because the hub SDA feature may be inactive or non-responsive, the feature must also be disabled at this remote TEMS to prevent SDA requests from being sent to the hub.
System action
None.
User response
If you require SDA support at this local RTEMS, you should view the hub TEMS product log to find information pertaining to the status of SDA, and if there were errors encountered during SDA initialization or operation at the hub. After the problem at the hub has been corrected, the SDA feature will be enabled at this remote TEMS following the next hub connection.
KFASD021 Self-Describing Agent feature has been enabled at hub TEMS. SDA also being enabled at this remote TEMS.
Explanation
While (re)connecting to the hub Tivoli Enterprise Monitoring Server (TEMS), this remote TEMS detected that the Self-Describing Agent (SDA) feature has been enabled at the hub. Therefore, the feature can now be enabled at this remote TEMS.
System action
None.
User response
If you do not want SDA to be enabled at this remote TEMS, you must set the KMS_SDA=N environment variable. Otherwise, no action is required.
KFASD022 Unexpected value <variable> found in KMS_SDA environment variable. Self-Describing Agent feature disabled on local TEMS.
Explanation
The Self-Describing Agent (SDA) feature is disabled on the local Tivoli Enterprise Monitoring Server (TEMS) because the KMS_SDA environment variable has been assigned an undefined value. The only two supported values are Y for enabling the SDA feature, and N for disabling the feature.
System action
None.
User response
Correct the KMS_SDA environment variable to assign it either a Y or N value.
KFASD023 Unable to contact hub TEMS, status <variable>, to determine if Self-Describing Agent feature is enabled.
Explanation
This remote Tivoli Enterprise Monitoring Server (TEMS) was not able to communicate with its hub to obtain the status of the Self-Describing Agent (SDA) feature at the hub.
System action
None.
User response
View the TEMS product logs for both the hub and remote TEMS to determine the cause of the communication failure between the remote and hub TEMS.
KFASD024 Self-Describing Agent feature disabled on local TEMS because <variable> not specified.
Explanation
The Self-Describing Agent (SDA) feature is disabled on the local Tivoli Enterprise Monitoring Server (TEMS) because the required ITM home directory was not specified.
System action
None.
User response
Ensure that the ITM home directory has been properly specified in the Tivoli Enterprise Monitoring Server configuration file.
KFASD025 Self-Describing Agent feature disabled on local TEMS because TEMS_MANIFEST_PATH <variable> not found.
Explanation
The Self-Describing Agent (SDA) feature is disabled
on the local Tivoli Enterprise Monitoring Server (TEMS) because a
required environment variable, TEMS_MANIFEST_PATH,
has been assigned a directory that does not exist in the local file
system.
System action
None.
User response
If you want to use the SDA feature, you must ensure that a valid directory has been specified for the TEMS_MANIFEST_PATH environment variable in the Tivoli Enterprise Monitoring Server configuration file.
KFASD026 The remote TEMS has become disconnected from the HUB while performing a SDA synchronization.
Explanation
This remote Tivoli Enterprise Monitoring Server (TEMS) encountered a communication failure with the hub during a Self-Describing Agent (SDA) request. SDA requests cannot be honored until the connection is re-established.
System action
None.
User response
View the TEMS product logs for both the hub and remote TEMS to determine the cause of the communication failure between the remote and hub TEMS. Once the failure has been corrected, SDA request support can be resumed.
KFASD027 Unexpected failure <variable> during RTEMS SDA synchronization with the HUB.
Explanation
This remote Tivoli Enterprise Monitoring Server (TEMS) encountered an unexpected failure with the hub during the Self-Describing Agent (SDA) synchronization phase. The SDA feature is disabled at this remote TEMS.
System action
None.
User response
View the TEMS product logs for both the hub and remote TEMS to determine the location of the issue, and recycle the appropiate TEMS that is responsible for the issue. Once the remote TEMS reconnects, SDA request support can be resumed.
KFASD028 Self-Describing Agent feature disabled on local TEMS because Broadcast Manager failed to initialize.
Explanation
The Self-Describing Agent (SDA) feature is disabled on the local Tivoli Enterprise Monitoring Server (TEMS) because a vital component of the SDA feature, the Broadcast Manager, failed to initialize.
System action
None.
User response
View the Tivoli Enterprise Monitoring Server product log to find specific information pertaining to the Broadcast Manager initialization error.
KFASD030 Detected seeding error, SEEDSTATE <variable>, STATE <variable>, STATUS <variable>, in a prior auto install of PRODUCT <variable> VERSION <variable> ID <variable> IDVER <variable>.
Explanation
During startup, the Tivoli Enterprise Monitoring Server (TEMS) determined that a prior attempt to automatically Seed the indicated product encountered an error. Prior installation continued. Use the tacmd listappinstallrecs to display the STATE and SEEDSTATE of the application install records.
System action
None.
User response
View the previous TEMS product log to find specific information pertaining to the product seeding error.
KFASD031 variable Self-Describing Agent install configurations record after RTEMS reconnected to HUB failed. status variable
Explanation
Processing of install configruation records after RTEMS reconnects to the HUB has failed. See the RTEMS RAS1 log for details.
System action
None.
User response
None.
KFASD100 Self-Describing Install Started for PRODUCT <variable>, VER <variable>, ID <variable>, IDVER <variable>.
Explanation
Self-Describing Agent installation has begun for the specified product.
System action
None.
User response
None.
KFASD101 Self-Describing Install Completed Successfully for PRODUCT <variable>, VER <variable>, ID <variable>, IDVER <variable>.
Explanation
Self-Describing Agent installation has successfully completed for the specified product.
System action
None.
User response
None.
KFASD102 Self-Describing Install Failed with STATUS <&1> for PRODUCT <variable>, VER <variable>, ID <variable>, IDVER <variable>.
Explanation
Self-Describing Agent installation has failed for the specified product.
System action
None.
User response
View the TEMS product log to find specific information pertaining to the product installation error.
KFASD103 Self-Describing Agent Seeding Failed for PRODUCT <variable>, VER <variable>, ID <variable>, IDVER <variable>. Install continuing.
Explanation
Self-Describing Agent seeding has failed for the specified product. The installation process has ignored the error, and is continuing with the product install.
System action
None.
User response
View the TEMS product log to find specific information pertaining to the product seeding error.
KFASD106 FTO requested Self Describing Install at Mirror for PRODUCT <variable>, VER <variable>, ID <variable>, IDVER <variable>.
Explanation
Self-Describing Agent installation has been requested at the Mirror for the specified product.
System action
None.
User response
None.
KFASD107 Pending Self-Describing Install request is cancelled for PRODUCT <variable>, VER <variable>, ID <variable>, IDVER <variable> due to FTO hub switch.
Explanation
Pending Self-Describing Agent requests are cancelled when a hub switch takes place to avoid connection error.
System action
None.
User response
None.
KFASD108 Self-Describing Agent User Configuration Record variable Error detected by UserID <variable> at <variable> for PRODUCT <variable> ID <variable> OPTION <variable> reason <variable>.
Explanation
The User Configuration Record change was in error and not accepted. Note that this message is generated only for the hub monitoring server, not the remote monitoring server. For a hub monitoring server v6.3 or later, the tacmd resumeSda command and tacmd suspendSda command are available at the hub, but not at the downlevel remote monitoring server (for example, v6.2.3 Fix Pack 1).
System action
None.
User response
None.
KFASD109 Self-Describing Agent User Configuration Record variable by UserID <variable> at <variable> for GRPID <variable> PRODUCT <variable> ID <variable> CONFIG <variable>.
Explanation
The User Configuration Record was processed successfully. Note that this message is generated only for the hub monitoring server, not the remote monitoring server. For a hub monitoring server v6.3 or later, the tacmd resumeSda command and tacmd suspendSda command are available at the hub, but not at the downlevel remote monitoring server (for example, v6.2.3 Fix Pack 1).
System action
None.
User response
None.
KFASD110 Self-Describing Agent feature variable on local TEMS.
Explanation
The Self-Describing Agent (SDA) feature is suspended or resumed by a Suspend User Configuration Record change. Note that this message is generated only for the hub monitoring server, not the remote monitoring server. For a hub monitoring server v6.3 or later, the tacmd resumeSda command and tacmd suspendSda command are available at the hub, but not at the downlevel remote monitoring server (for example, v6.2.3 Fix Pack 1).
System action
None.
User response
None.
KFASD111 Self-Describing Agent Initialization variable Record Error detected for PRODUCT <variable> ID <variable> OPTION <variable> reason <variable>.
Explanation
The Initialization Record processing was in error and not completed.
System action
None.
User response
Review the TEMS product logs for the TEMS to determine the location of the issue. Correct the appropriate Record that is causing the issue. Restart the TEMS to initialize the SDA feature.
KFASD112 Self-Describing Agent Suspend/Install User Configuration Features are variable at the hub TEMS.
Explanation
This remote Tivoli Enterprise Monitoring Server (TEMS) has detected that the Self-Describing Agent (SDA) Suspend/Install User Configuration Features are <Not Supported> or <Now Available> at the hub (TEMS). Note that this message is generated only for the hub monitoring server, not the remote monitoring server. For a hub monitoring server v6.3 or later, the tacmd resumeSda command and tacmd suspendSda command are available at the hub, but not at the downlevel remote monitoring server (for example, v6.2.3 Fix Pack 1).
System action
None.
User response
The remote (TEMS) SDA feature will not process Suspend/Install User Configuration controls from the hub (TEMS) when it does not have support for the feature or will process Suspend/Install User Configuration Controls that the hub (TEMS) has recently upgraded support for.
KFASD190 Self-Describing Agent feature terminated on the local TEMS.
Explanation
The Self-Describing Agent (SDA) feature has been stopped.
System action
None.
User response
View the local TEMS product logs if the feature has not been stopped by normal TEMS shutdown to determine the location of the issue for SDA termination. Correct the appropriate issue. Start the local TEMS to restart the SDA feature.
KFAST001 Agent node name error- variable variable variable
Explanation
An agent has attempted to insert itself with an invalid node name. The values given are the NODE name, THRUNODE name and HOSTADDR. NODE name is the incorrect name and HOSTADDR is the address of the computer on which the agent resides.
KFAST002 Select request for the EIBLOG table cannot be performed at a remote TEMS.
Explanation
Select request for the TEIBLOGT table was issued to this Tivoli Enterprise Monitoring Server. The TEIBLOGT is a hub Tivoli Enterprise Monitoring Server-only table and therefore the request cannot be processed.
KFAST003 Take Action command variable completed with status of variable.
Explanation
The Take Action command specified was executed with the identified result. This message reflects that status of the Take Action command. The first variable represents the command that was executed. The second variable is the status code from the execution of the action. This status code is operating system- or application-specific and indicates whether or not this Take Action command was executed only. For determination regarding success or failure for the action, refer to documentation associated with the action.
Operator response
If the result is not as expected, verify that the command configured successfully execute by issuing the command manually. This will ensure any necessary platform resources are available for the command to complete.
The following list describes the
return codes for the KFAST003 message on z/OS systems:
- 0
- Operation completed successfully
- 1
- One or more attributes invalid
- 2
- USERID attribute not supplied
- 3
- COMMAND not supplied
- 4
- Command not successfully executed
- 5
- An unhandled exception occurred during command execution
- 6
- Process not authorized
- 7
- Command is too long
- 8
- Heap storage unavailable
- 9
- IBM Z® NetView PPI rejected request
- 10
- User ID is too long
- 11
- Unable to assume user profile
- 12
- Unable to restore user profile
- 13
- Unable to restore user profile
- 14
- An exception occurred during command execution
- 15
- Unable to release user profile
- 16
- Current profile unavailable
- 17
- IBM Z NetView PPI interface CNMCNETV not loaded
KFAST004 Unsupported Node or Nodelist request: variable
Explanation
A request to add a node or nodelist to the Tivoli Enterprise Monitoring Server contained unsupported characters in either the nodename, thrunode, nodelist, affinities or nodetype. Typically this request is made by an IBM Tivoli Monitoring agent or probe attempting to connect to the Tivoli Enterprise Monitoring Server. One or some of the required values provided contained unsupported characters.
Operator response
Refer to the Tivoli Enterprise Monitoring Server
log where the node, thrunode, nodelist, affinities, and nodetype values
have been dumped. These rules apply:
- The rule set for supported values for node, thrunode, and nodelist: A-Z, a-z, 0-9, *-_: and space.
- Affinities must be 43 characters, and the static affinity rule set is A-Z, a-z, 0-9, * #.
- A dynamic affinity is indicated when the first character is a
$ or %. For dynamic affinities, the initial 23 characters are validated
as follows:
- The valid dynamic affinity characters are A-Z, a-z, 0-9 and _.
- A single period is required to separate the vendor and app ID.
- Spaces are only supported as trailing characters in the dynamic portion before the static portion.
- The remaining 19 characters are validated using static affinity rules.
- The supported values for nodetype are: space, M and V.
- Additionally, nodelist, node, and thrunode values cannot start with a space, and node values cannot start with an *.
Examine the memory dump in the trace log to determine the illegal value that is being attempted. For further action, contact IBM.