A fix is available
APAR status
Closed as program error.
Error description
The attempt to update a backup-archive client installation via automatic deployment with update manager 8.1.2 fails in case of the existing backup-archive client installation is configured for SSL/TLS communication connecting to the dedicated SSL TCP port (SSLTCPPORT). If the existing configuration uses the standard TCP port (which is also able to accept SSL/TLS connections beginning with SP server 8.1.2 and 7.1.8) the issue will not occur. All Unix and Linux platforms are affected. After the failed deployment the existing backup-archive client remains operational. The root cause of the issue is that the update manager cannot connect to the server on the SSL specific port. As a consequence, it cannot report the issue back to the server so that the actlog does not show a clear indication of the incident. It will just miss the message that normally indicates success, as the following example shows: ANE4300I (Session: 11922, Node: BRECHT) powerpc, 8120_BRECHT, STANDARD: Client deployment was completed successfully. (SESSION: 11922) The logfile setup.log shows the following error message: "Thu Sep 14 10:01:30 MST 2017: The update completed with a failure. The updatemgr returned with failure code 8." The logfile updatemgr.log shows the following error messages: "09/14/17 10:01:30 ANS0361I DIAG: cucommon.cpp (3019): cuIdentifyResp(): Error -50 receiving IdentifyResp 09/14/17 10:01:30 ANS4218E The Deployment Manager received an error while initializing the client API. The standard API function being invoked was tsmInitEx."
Local fix
Before initiating the automatic deployment, the backup-archive client installation on the target machine needs to be reconfigured so that it uses the hybrid TCP port (former standard port) as introduced with SP server 8.1.2 and 7.1.8.
Problem summary
**************************************************************** * USERS AFFECTED: * * Users of client auto deployment deploying b/a client to Unix * * and Linux target machines. * **************************************************************** * PROBLEM DESCRIPTION: * * See ERROR DESCRIPTION * **************************************************************** * RECOMMENDATION: * * Apply fixing level when available. This problem is * * currently projected to be fixed in level 8.1.4 by * * downloading and importing the new update manager EXP file * * (this is done automatically when using Operation Center for * * client deployment). Note that this is subject to change at * * the discretion of IBM. * ****************************************************************
Problem conclusion
Once the fix is in place, target machines with backup archive client being configured for SSL/TLS configuration can be sucessfully updated.
Temporary fix
Comments
APAR Information
APAR number
IT22485
Reported component name
TSM CLIENT
Reported component ID
5698ISMCL
Reported release
81L
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-09-21
Closed date
2017-10-18
Last modified date
2017-10-18
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
updmgr
Fix information
Fixed component name
TSM CLIENT
Fixed component ID
5698ISMCL
Applicable component levels
R81L PSY
UP
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGSG7","label":"Tivoli Storage Manager"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"81L","Line of Business":{"code":"LOB26","label":"Storage"}}]
Document Information
Modified date:
08 January 2022