Hi Tony,
While I certainly won't claim that the client is 100% bug free, this is
most likely "normal" (i.e. there is a logical explanation for the RC 8).
Did you review the documentation I recommended in my last note on this
thread (the one to which you replied)? If not, have a look, as it explains
in reasonable (I think) detail which RCs TSM issues, how the RC is
determined, and where to look to find out why the RC was issued.
If that does not shed any light, then let me know... please be sure to
provide sample output demonstrating the RC 8, and the pertinent log data,
as described in the aforementioned documentation.
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.eyebm DOT com (change eye to i to reply)
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
"Garrison, Tony" <Anthony.Garrison AT USAA DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
03/24/2003 17:01
Please respond to "ADSM: Dist Stor Manager"
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Re: Messages and return codes
Andy;
I have a number of Win2k nodes that are running 5.1.5.9 client.
these clients backup to 5.1.5.4 and 4.2.1.11 server versions (TSM servers
are AIX 4.3.3). We recently noticed that these clients complete with a
return code of 8. even when doing a simple q sched command. this has
screwed up all our Control-M jobs. is this normal or a bug in the 5.1.5.9
client?
T
-----Original Message-----
From: Andrew Raibeck [mailto:storman AT US.IBM DOT COM]
Sent: Friday, March 07, 2003 1:34 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Messages and return codes
You do not indicate which client version you are running, so it is
difficult to be specific in your case.
If you are running something below 5.1, then the return code should be
deemed undocumented and unpredictable.
If you are running 5.1, then the info on client return codes can be found
in the client manual, chapter 7 "Automating Tasks".
Information on message format and severities is in the Messages manual, in
the introduction chapter. 'ANSnnnnS' messages are considered a severe
error, and will generate an RC 12.
As you'll find in the client manual, the client return codes are tied very
strongly to the message severity. There is nothing in the client that
allows you to configure which messages will generate which return code. If
you think a message is generating the wrong return code, then you should
contact IBM support to see if there is an actual problem in the return
code processing. If you disagree with the severity level of a given
message (and thus the rc it generates), then you should open a requirement
and request the change. We are open to re-evaluating message severities.
For example, prior to 5.1, the message you got when a TCP/IP connection
was severed (but the client was able to re-establish the connection) was
treated as a severity of "error". In 5.1, we reduced it to a "warning"
level message since the client is able to re-establish the connection.
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.eyebm DOT com (change eye to i to reply)
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
David E Ehresman <deehre01 AT LOUISVILLE DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
03/07/2003 11:28
Please respond to "ADSM: Dist Stor Manager"
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Messages and return codes
Is there any documentation of what messages cause which numeric return
code to the client. In particular, I'm trying to determine what return
code a "ANS1492S Invalid virtual mountpoint /ps/epmtest/psoft: File not
found." returns to the client. Is there any way to change which return
code a message generates?
David
|
