dsmapipw fails: tsm client v7.1.8

[vilius.m]

Hello,

TSM server: v7.1.8 Windows 2012 R2
TSM client: v7.1.8 AIX 7.1
DB2: v10.5 FP7

dsmapipw call to set password fails:

# /db2/db2xxx/sqllib/adsm/dsmapipw
*************************************************************
* Tivoli Storage Manager                                    *
* API Version = 7.1.8                                       *
*************************************************************
Enter your current password:
Enter your new password:
Enter your new password again:
*** Server signon failed: (-1) Unknown rc.
#
# cat /db2/db2xxx/tsm/db2/dsmerror.log
10/27/17   14:44:17 ANS1579E GSKit function GSKKM_ImportKeys failed with 17: GSKKM_ERR_DATABASE_INVALID_FILE_TYPE
10/27/17   14:44:17 ANS9020E A session could not be established with a TSM server or client agent.  The return code is -1.

Downgrading client to v7.1.6 solves the problem so this one clearly related to v7.18 security(ssl?) enhancements.
BA client connects to server just file, and preserves password using new (v7.1.8) format (TSM.KDB instead TSM.PWD).
dsm.sys:

SErvername server_db2xxx
  COMMMethod             TCPip
  TCPPort                1500
  TCPServeraddress       x.x.x.x
  NODename               sapxxx
  PASSWORDAccess         generate
  PASSWORDDIR            /db2/db2xxx/tsm/db2
  MANAGEDServices        schedule
  ERRORLOGName           /db2/db2xxx/tsm/db2/dsmerror.log
  SCHEDLOGName           /db2/db2xxx/tsm/db2/dsmsched.log
  ERRORLOGRetention      30
  SCHEDLOGRetention      30
  NRTABLEPath            /db2/db2xxx/tsm/db2

Any ideas ?

Thanks,
Vilius M.

 

[juliowest]

Hello,

TSM server: v7.1.8 Windows 2012 R2
TSM client: v7.1.8 AIX 7.1
DB2: v10.5 FP7

dsmapipw call to set password fails:

# /db2/db2xxx/sqllib/adsm/dsmapipw
*************************************************************
* Tivoli Storage Manager                                    *
* API Version = 7.1.8                                       *
*************************************************************
Enter your current password:
Enter your new password:
Enter your new password again:
*** Server signon failed: (-1) Unknown rc.
#
# cat /db2/db2xxx/tsm/db2/dsmerror.log
10/27/17   14:44:17 ANS1579E GSKit function GSKKM_ImportKeys failed with 17: GSKKM_ERR_DATABASE_INVALID_FILE_TYPE
10/27/17   14:44:17 ANS9020E A session could not be established with a TSM server or client agent.  The return code is -1.

Downgrading client to v7.1.6 solves the problem so this one clearly related to v7.18 security(ssl?) enhancements.
BA client connects to server just file, and preserves password using new (v7.1.8) format (TSM.KDB instead TSM.PWD).
dsm.sys:

SErvername server_db2xxx
  COMMMethod             TCPip
  TCPPort                1500
  TCPServeraddress       x.x.x.x
  NODename               sapxxx
  PASSWORDAccess         generate
  PASSWORDDIR            /db2/db2xxx/tsm/db2
  MANAGEDServices        schedule
  ERRORLOGName           /db2/db2xxx/tsm/db2/dsmerror.log
  SCHEDLOGName           /db2/db2xxx/tsm/db2/dsmsched.log
  ERRORLOGRetention      30
  SCHEDLOGRetention      30
  NRTABLEPath            /db2/db2xxx/tsm/db2

Any ideas ?

Thanks,
Vilius M.

Apparently this is caused by the fact that db2 is using a different version of gskit. I was to fix this by adding a link under $DB2_HOME/lib64
gskit -> /usr/local/ibm/gsk8_64/lib64
After this, the dsmapipw command executed successfully and db2 backups to TSM worked.

 

[apsbb]

Apparently this is caused by the fact that db2 is using a different version of gskit. I was to fix this by adding a link under $DB2_HOME/lib64
gskit -> /usr/local/ibm/gsk8_64/lib64
After this, the dsmapipw command executed successfully and db2 backups to TSM worked.

very good !!!
Solved my problem !!!