A fix is available
APAR status
Closed as program error.
Error description
Applying the OS Agent update 6.2.3.3-TIV-ITM_UNIX-IF0006 to an AIX endpoint and will result in the deployment transaction remaining in the INPROGRESS status indefinitely. Since the installation at the endpoint failed to restart the OS Agent following the update, the Deployment operation on the TEMS side continues to wait for the completion to occur (until the OS Agen restarts). The timeout does not expire for the operation. RECREATE INSTRUCTIONS: 1. Install ITM 623 FP3 TEMS 2. Install ITM 623 FP3 on AIX endpoint 3. Configure the OS Agent to enable Historical Collection. 4. Specify a value of 10KB for KHD_TOTAL_HIST_MAXSIZE="10" 5. Specify the following value: CTIRA_HIST_DIR="/var/opt/IBM/ITM/HIST" 6. Fill the "/var/opt/IBM/ITM/HIST" directory with dummy files so as to reduce the available space in this directory to less than 10KB. 7. Add the IFix package 6.2.3.3-TIV-ITM_UNIX-IF0006 to the TEMS Depot. 8. Execute tacmd updateagent -n <endpoint:UX> -t UX -v 0623030006, and note the Deployment transaction number. 9. Issue the command tacmd getdeploystatus and observe that the transaction associated with the agent update remains in the INPROGRESS status indefinitely.
Local fix
Execute the command tacmd cleardeploystatus -i <transaction number> to change the status of the transaction.
Problem summary
If, when performing an updateAgent command to upgrade the Unix OS Agent on a target system, the OS Agent fails to correctly initialize due to thread issued caused by APAR IV43114 and as a result the status of the updateAgent command remains as INPROGRESS, failing to complete. If the OS Agent generates Situation data which creates a Short-Term History file whose contents exceeds the maximum capacity as specified by the configuration OS Agent's configuration value KHD_TOTAL_HIST_MAXSIZE and the user executes the updateagent command to upgrade the OS Agent to the 06.23.03.00 release, the updateagent transaction status remains as INPROGRESS, never completing. Encountering APAR IV43114 results in one of OS Agent's thread abnormally terminating. Remote Deploy uses a polling algorithm to determine the completion status of updateagent commands. As a result of this termination, Remote Deploy is not able to obtain the status of the updateagent transaction from the OS Agent, and does not update the status of the transaction in the Deployment Status table.
Problem conclusion
Change the design Remote Deploy uses to determine the installation completion status on a target machine from polling to publish-subscribe. The fix for this APAR is contained in the following maintenance packages: | fix pack | 6.3.0-TIV-ITM-FP0004
Temporary fix
Use the command line interface command cleardeploystatus specifying the -i (remove INPROGRESS transactions) for the Remote Deploy transaction that continues to have the INPROGRESS status.
Comments
APAR Information
APAR number
IV57771
Reported component name
TEMS
Reported component ID
5724C04MS
Reported release
623
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-03-27
Closed date
2014-07-17
Last modified date
2014-12-14
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
TEMS
Fixed component ID
5724C04MS
Applicable component levels
R630 PSY
UP
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSCTLMP","label":"ITM Tivoli Enterprise Mgmt Server V6"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"623","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
14 December 2014