Hi,
I WAS looking after scheduled method and used the commad line for testing
only ;=8)
Good news:
the crash is only related to my workstation.
Here even the
dsmc backup systemobject
command crashes. Since today..
Fyi:
I worked few things out:
dsmc incr -domain="systemobject -c: -d: -e: -f: -g: -h: -i: -j:"
works in 5.1.5.9 as expected,
unless the systemobject is excluded in the .OPT file:
domain -systemobject
In this case
ANS1149E No domain available for incremental backup
is the result.
I believe this to be a bug because
domains specified on the command line should be added
to those from OPT file,
but it is not a problem for me as far as I know about.
V 5,1,0.0 reports incorrect syntax
best regards
Juraj Salak
-----Urspr�ngliche Nachricht-----
Von: Andrew Raibeck [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 07. M�rz 2003 20:34
An: [EMAIL PROTECTED]
Betreff: 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/[EMAIL PROTECTED]
Internet e-mail: [EMAIL PROTECTED] (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 <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
03/07/2003 11:28
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
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
