TSM Client Error

[ravi3010]

Hi All,

We are running TSM 5.5 on AIX 5.3.

Now one of the client is unabale to connact to the TSM server.While trying to connect by dsmc its throughing an error TCP/IP error.

But when I see in dsmerrordb2.log its showing an error as follows...

07/07/10 11:00:41 ANS1036S The option 'ISK' or the value supplied for it is not valid. It was found in options file 'OPTIONS STRING'
at line number: 1
The complete entry: 'disk'
07/07/10 11:00:41 ANS1038S Invalid option specified
07/07/10 11:01:02 ANS1036S The option 'ISK' or the value supplied for it is not valid. It was found in options file 'OPTIONS STRING'
at line number: 1
The complete entry: 'disk'
07/07/10 11:01:02 ANS1038S Invalid option specified


When I see in dsm.opt there is no option specified like ISK...The dsm.opt file is as follows...

SErvername ***tsmdb2
COMMmethod TCPip
TCPPort 1500
TCPServeraddress ***.***.***.**(IP Defined)
TCPbuffsize 64
TCPNodelay yes
* TXNByteLimit 25600
NODENAME qtstdb2
* PASSWORDACCESS prompt
PASSWORDACCESS generate
resourceutilization 8
* schedmode prompted
inclexcl /usr/tivoli/tsm/client/ba/bin/inclexcldb2
schedlogname /usr/tivoli/tsm/client/ba/bin/dsmscheddb2.log
errorlogname /usr/tivoli/tsm/client/ba/bin/dsmerrordb2.log
tcpwindowsize 128
LARGECOMMBUFFERS NO
* compression yes
* tcpbuffsize 512
* INCLUDE /db2/JSM/log_archive/.../* db2logmgm
* INCLUDE "/.../C*_S*.LOG" db2logmgm
* INCLUDE "/.../S*.LOG" db2logmgm


Any help.....

 

[whitepup]

Do you have two opt files? One named "dsm.opt" and one named "options string"?

 

[ravi3010]

Do you have two opt files? One named "dsm.opt" and one named "options string"?

We are having only dsm.opt file none other than this...

Can you please let me know how to check client or user TSM parameters..?

Thank You

 

[whitepup]

My bad on the second opt file.

Can you try commenting everything out of your dsm.opt file except for:

SErvername ***tsmdb2
COMMmethod TCPip
TCPPort 1500
TCPServeraddress ***.***.***.**(IP Defined)

just to see if it will connect?

 

[ravi3010]

My bad on the second opt file.

Can you try commenting everything out of your dsm.opt file except for:

SErvername ***tsmdb2
COMMmethod TCPip
TCPPort 1500
TCPServeraddress ***.***.***.**(IP Defined)

just to see if it will connect?

I have commented but no result the same issue...

 

[dms19]

didnt you say this was AIX? Whats in the dsm.sys file?

Was there confirmation on whether or not a client option set is being used on this client?

do a q node clientname f=d and post

 

[ravi3010]

didnt you say this was AIX? Whats in the dsm.sys file?

Was there confirmation on whether or not a client option set is being used on this client?

do a q node clientname f=d and post

yes this is AIX client...Below is the output...

Want to mention one more thing that this happening for only db2 user.The db2 user not able to connect to TSM and as a root we are able to connect to TSM server from this client....

tsm: SERVER1>q node qtstdb2 f=d
Node Name: QTSTDB2
Platform: AIX
Client OS Level: 6.1
Client Version: Version 5, release 4, level 0.0
Policy Domain Name: R3DDOM
Last Access Date/Time: 06/21/10 11:15:32
Days Since Last Access: 16
Password Set Date/Time: 07/07/10 10:47:10
Days Since Password Set: <1
Invalid Sign-on Count: 0
Locked?: No
Contact:
Compression: Client
Archive Delete Allowed?: Yes
Backup Delete Allowed?: No
Registration Date/Time: 03/03/08 11:20:34
Registering Administrator: ADMIN
Last Communication Method Used: Tcp/Ip
Bytes Received Last Session: 64.00 M
Bytes Sent Last Session: 3,737
Duration of Last Session: 2.90
Pct. Idle Wait Last Session: 2.38
Pct. Comm. Wait Last Session: 18.32
Pct. Media Wait Last Session: 0.00
Optionset:
URL:
Node Type: Client
Password Expiration Period:
Keep Mount Point?: No
Maximum Mount Points Allowed: 5
Auto Filespace Rename : No
Validate Protocol: No
TCP/IP Name: qtst
TCP/IP Address: ###.###.##.87
Globally Unique ID: d5.59.dc.5c.5b.db.11.d7.b5.f3.08.63.a0.d4.30.c7
Transaction Group Max: 0
Data Write Path: ANY
Data Read Path: ANY
Session Initiation: ClientOrServer
High-level Address:
Low-level Address:
Collocation Group Name:
Proxynode Target:
Proxynode Agent:
Node Groups:
Email Address:

 

[dms19]

Whats in your dsm.sys file on the client node?

What you have in your opt file should be in your sys file.

 

[sjarking]

I had the same problem.

It seemed I mixed up the dsm.sys and the dsm.opt. I exchanged both names and it worked.