Re: Problem with backup scripts

You indicate that you are using a script to launch dsmc, and that you are
getting RC 8. You next ask why the scheduled backup is failed instead of
completed. So I am wondering: are you using the TSM scheduler to schedule
ACTION=COMMAND where the command is your script? If so, then take another
look at the table in the "Automating tasks" chapter that describes the
return codes. The last row, "other", describes how return codes for
COMMAND actions are handled.

In general, for ACTION=COMMAND, any nonzero return code will be treated as
failed. The reason for this is that unlike commands such as SELECTIVE,
INCREMENTAL, ARCHIVE, etc., TSM has know knowledge of the internal
workings of commands launched via ACTION=COMMAND schedules. In reporting a
return code for these commands, the only convention we can observe is that
return code 0 is generally accepted as success. Thus anything else
(nonzero return code) is treated as a failure. If *you* know that your
scheduled command can exit with a nonzero return code, then in your script
you can test the return code from the command. If it meets your criteria
for success, you can exit the script with return code 0 and the scheduled
event will be reported as Complete. Otherwise you can exit with a nonzero
return code.

In your case, your script happens to launch the TSM client. Since we
*know* that RC 8 means at least one warning message was issued, I would
not advise that you translate this to return code 0 in your script,
although that is your option if you wish (do so at your own risk).
Instead, the reason for the RC 8 should be investigated and corrected.

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.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




Neilson Lui <nclui AT BPI.COM DOT PH>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
09/11/2003 00:49
Please respond to "ADSM: Dist Stor Manager"

        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: Problem with backup scripts


Have already looked at the manual... But how come the status of my
scheduled backup is FAILED instead of COMPLETED as indicated on the manual

09/11/2003 03:30:00  09/11/2003 03:30:05  OPICSFS_DAIL- OPXFS_AS
Failed
                                           Y_BACKUP



                    "Hooft, Jeroen"
                    <Jeroen.Hooft@ATOSO        To: ADSM-L AT VM.MARIST DOT EDU
                    RIGIN.COM>                 cc:
                    Sent by: "ADSM:            Subject:     Re: Problem
with backup scripts
                    Dist Stor Manager"
                    <[email protected]
                    DU>


                    09/11/2003 03:16 PM
                    Please respond to
                    "ADSM: Dist Stor
                    Manager"






Look in the Windows Client manual for returncodes:


RC 8: The operation completed with at least one warning message. For
scheduled events, the status will be Completed. Review dsmerror.log (and
dsmsched.log for scheduled events) to determine what warning messages were
issued and to assess their impact on the operation.





-----Original Message-----
From: Neilson Lui [mailto:nclui AT BPI.COM DOT PH]
Sent: donderdag 11 september 2003 2:13
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Problem with backup scripts


We just upgrade our clients from 5.1.5.0 to 5.1.6.6 and our server running
on Win2K from 5.1.5.0 to 5.1.7.2  , after the upgrade most of our backup
scripts fails with return code 8, can anyone help ? BTW, the backup was
complete with no errors:

scripts is

dsmc incr "c:\xxxx\*" -sudir=yes > c:/tsmscript/tsmdaily.log


and the message on the actlog is

09/11/2003 03:46:52   ANE4952I (Session: 5836, Node: OPXFS_AS)  Total
number of
                       objects inspected:   59,099

09/11/2003 03:46:52   ANE4954I (Session: 5836, Node: OPXFS_AS)  Total
number of
                       objects backed up:    5,822

09/11/2003 03:46:52   ANE4958I (Session: 5836, Node: OPXFS_AS)  Total
number of
                       objects updated:          0

09/11/2003 03:46:52   ANE4960I (Session: 5836, Node: OPXFS_AS)  Total
number of
                       objects rebound:          0

09/11/2003 03:46:52   ANE4957I (Session: 5836, Node: OPXFS_AS)  Total
number of
                       objects deleted:          0

09/11/2003 03:46:52   ANE4970I (Session: 5836, Node: OPXFS_AS)  Total
number of
                       objects expired:         13

09/11/2003 03:46:52   ANE4959I (Session: 5836, Node: OPXFS_AS)  Total
number of
                       objects failed:           0

09/11/2003 03:46:52   ANE4961I (Session: 5836, Node: OPXFS_AS)  Total
number of
                       bytes transferred:  1.23 GB

09/11/2003 03:46:52   ANE4971I (Session: 5836, Node: OPXFS_AS)  LanFree
data
                       bytes:                    1.23 GB

09/11/2003 03:46:52   ANE4963I (Session: 5836, Node: OPXFS_AS)  Data
transfer
                       time:                  332.89 sec

09/11/2003 03:46:52   ANE4966I (Session: 5836, Node: OPXFS_AS)  Network
data
                       transfer rate:        3,901.83 KB/sec

09/11/2003 03:46:52   ANE4967I (Session: 5836, Node: OPXFS_AS)  Aggregate
data
                       transfer rate:      1,292.12 KB/sec

09/11/2003 03:46:52   ANE4968I (Session: 5836, Node: OPXFS_AS)  Objects

                       compressed by:                    0%

09/11/2003 03:46:52   ANE4964I (Session: 5836, Node: OPXFS_AS)  Elapsed

                       processing time:            00:16:45


Thanks