APAR status
Closed as program error.
Error description
When installing AD , the folders of some of the new services are not created by the installer but the installation status file mentions that these services have been installed successfully The installation status file is not reflecting the correct status for the failed install
Local fix
This symptom may occur if %SystemRoot%\System32 (for example, C:\Windows\System32) is not present in the system PATH variable. Adding %SystemRoot%\System32 to the system PATH variable and then re-running the ADDI installer may allow you to work around the issue and get the additional services installed.
Problem summary
IBM_ADDI_Installation_Status.txt file says the new services were installed successfully eventhough the folders for the new services were not created.
Problem conclusion
This issue has been successfully resolved from AD 5109 by having the installer add the %SYSTEMROOT%\system32 information to the end of the PATH environment variable it uses, but note that that addition is for the current task and does not permanently affect the server system or its PATH statement after rebooting. Installation logging was also improved.
Temporary fix
Comments
APAR Information
APAR number
PH26909
Reported component name
APPL DISCOVERY
Reported component ID
5737B1600
Reported release
510
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2020-06-30
Closed date
2021-01-08
Last modified date
2021-01-26
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
APPL DISCOVERY
Fixed component ID
5737B1600
Applicable component levels
[{"Line of Business":{"code":"LOB35","label":"Mainframe SW"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSRR9Q","label":"IBM Application Discovery for IBM Z"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"510"}]
Document Information
Modified date:
27 January 2021