OnDemand User Group
Support Forums => MP Server => Topic started by: JeanineJ on November 21, 2022, 10:38:28 AM
-
On Friday one of my customers attempted to load 2 small AFP document files from the mainframe to my QA environments and both files took 88 load failed errors.
The system log provided this information:
429 TSM Error: ANS1035S (RC406) Options file '*' could not be found, or it cannot be read., Return Code=406, Reason=0, File=arssmsms.cpp, Line=1603 Srvr->
I sent the error to my storage guy and he ended up requesting a server reboot. When the reboot occurred arssockd failed to start. I cannot start it manually. I'm wondering if anybody has run across this while I wait for IBM support to figure out the problem.
CMOD V10.5.0.4 running on a RHEL 7 server
DB2 V11.01.0406
Spectrum Protect (TSM) V8.1.12
-
There's a problem with your TSM Config files. Check for recent changes, and refer to your backups to pull earlier versions.
-JD.
-
That's the problem. This system has had few if any changes recently. I upgraded from 10.1 to 10.5 late in 2021 and that was AFTER my storage guy upgraded TSM to the compatible version with 10.5.
I'm good with posting diagnostics if you give me the complete command of what you need.
-
It's hard to tell, but I'd start with checking the TSM config file directory to see if there have been any changes you didn't know about:
# List the directory in reverse chronological order:
ls -ltr /usr/tivoli/tsm/client/api/bin64/
# See the contents of the TSM Options and System file:
cat /usr/tivoli/tsm/client/api/bin64/dsm.opt
cat /usr/tivoli/tsm/client/api/bin64/dsm.sys
-JD.
-
The root cause was my server admins updated the IBM licensing agent on the 2 non-prod servers and that changed the permissions to libApiTSM64.so. IBM support traced that problem after I called to escalate my case with the duty manager. I worked with my server admins this morning and they basically compared what was on my prod server with what was on the non-prod servers and found the problem immediately. Once the permissions were fixed I was able to stop and start arssockd then load documents to TSM on both servers.
The TL promised to notify me when are ready to update my production server and went so far as to make sure the licensing update wouldn't update the permissions.
-
Wow. That's second only to a customer's system administrator *uninstalling* the TSM Client from the server without telling anyone... Ouch.
I'm happy to hear you're back online!
-JD.