[SOLVED] Interpreting a RHEL 5.7 Return Code

gjhuebschman · 10-12-2012, 02:27 PM

Environment RHEL 5.7
Application TSM Client 6.2, Archiving

I want to find out what "Return code = 126" means.
I just fixed an RC 127, now I have RC 126.
The problem is related to an archive operation that is run fron a script. The ONLY message in the application error log is:

10/12/2012 02:52:54 ANS1909E The scheduled command failed.
10/12/2012 02:52:54 ANS1512E Scheduled event 'ARCHXXXLOGS' failed. Return code = 126.

The TSM "ANS" error codes do not shed any real light.

"While you have a choice, spend your money where you'd rather work when you have no choice."

acid_kewpie · 10-13-2012, 03:15 PM

this is nothing to do with Redhat itself. This is arbitrary proprietary code. you need to ask IBM.

TB0ne · 10-13-2012, 04:53 PM

Quote:

Originally Posted by gjhuebschman

Environment RHEL 5.7
Application TSM Client 6.2, Archiving

I want to find out what "Return code = 126" means.
I just fixed an RC 127, now I have RC 126.
The problem is related to an archive operation that is run fron a script. The ONLY message in the application error log is:

10/12/2012 02:52:54 ANS1909E The scheduled command failed.
10/12/2012 02:52:54 ANS1512E Scheduled event 'ARCHXXXLOGS' failed. Return code = 126.

The TSM "ANS" error codes do not shed any real light.

Yes, it does:
http://publib.boulder.ibm.com/infoce...2FANS1512E.htm

Related to APAR IC46126 on the IBM knowledgebase for TSM. Essentially, the command you're trying to run on the RHEL server either can't BE run, or is somehow incorrect (bad permissions? Path? User?). Be sure to start the TSM scheduler as root, if you haven't already. What do the dsmerror and dsmsched logs say on the RHEL box? Can you back the system up manually? What does the ARCHXXXLOGS event do?

Checking those logs should be a starting point, as is running a manual backup via dsmadmc. There are times when the ANS1512 message comes up due to the TSM client not signing off correctly from the TSM server. If that's the case, the error can be ignored.

gjhuebschman · 10-15-2012, 11:33 AM

I did check IBM's error message before I posted.

But, THANKS!, you are correct, it was a permission issue. I copied this script from a similar server in another cluster in another environment.
I WinSCP'ed it to my destop then out to this server.
I had to chown it to get it my desktop.
I chown'ed it back to root, but forgot to chmod it. It did not have any execute permission.

Also, "dsmc" is the command to run (or "dsmc", then "archive"), it was an archive.
The command "dsmadmc" opens a session with the TSM Server application. "dsmc" starts the client application.

Thanks very much for the help.
George Huebschman

TB0ne · 10-16-2012, 10:38 AM

Quote:

Originally Posted by gjhuebschman

I did check IBM's error message before I posted.

But, THANKS!, you are correct, it was a permission issue. I copied this script from a similar server in another cluster in another environment.
I WinSCP'ed it to my destop then out to this server.
I had to chown it to get it my desktop.
I chown'ed it back to root, but forgot to chmod it. It did not have any execute permission.

Also, "dsmc" is the command to run (or "dsmc", then "archive"), it was an archive.
The command "dsmadmc" opens a session with the TSM Server application. "dsmc" starts the client application.

Thanks very much for the help.
George Huebschman

No worries...and I put the admin console command instead of the client. Shows you what force-of-habit can do.