The backup script, it is noting but the following:

#!/bin/sh
su - vram3 -c "/opt/lotus/bin/domdsmc_vram3 incremental \"*\"
/ADSMOPTF=/opt/tivoli/tsm/client/domino/bin/domdsmc_vram3/dsm.opt
/BUFF=8,8192 /SUBDIR=YES /MOUNTwait=no"

The archivelog script is similar.

The latest dsmerror.log entry for this system says:

11/01/06   06:06:03 ANS1909E The scheduled command failed.
11/01/06   06:06:03 ANS1512E Scheduled event 'VRAM3.ARCHLOG' failed.
Return code = 9.
11/01/06   06:06:44 ANS1909E The scheduled command failed.
11/01/06   06:06:44 ANS1512E Scheduled event 'VRAM3.INCR' failed.  Return
code = 9.

There is nothing in the domdsm.log files.  The only thing in the
dsmsched.log file around this time is:

11/01/06   03:43:04 --- SCHEDULEREC QUERY BEGIN
11/01/06   03:43:04 --- SCHEDULEREC QUERY END
11/01/06   03:43:04 Next operation scheduled:
11/01/06   03:43:04
------------------------------------------------------------
11/01/06   03:43:04 Schedule Name:         VRAM3.INCR
11/01/06   03:43:04 Action:                Command
11/01/06   03:43:04 Objects:               /notes/vram3/bkupall
11/01/06   03:43:04 Options:
11/01/06   03:43:04 Server Window Start:   03:00:00 on 11/01/06
11/01/06   03:43:04
------------------------------------------------------------
11/01/06   03:43:04
Executing scheduled command now.
11/01/06   03:43:04
Executing Operating System command or script:
   /notes/vram3/bkupall
11/01/06   06:06:03 Finished command.  Return code is: 9
11/01/06   06:06:03 ANS1909E The scheduled command failed.
11/01/06   06:06:03 ANS1512E Scheduled event 'VRAM3.ARCHLOG' failed.
Return code = 9.
11/01/06   06:06:03 Sending results for scheduled event 'VRAM3.ARCHLOG'.
11/01/06   06:06:03 Results sent to server for scheduled event
'VRAM3.ARCHLOG'.

11/01/06   06:06:03 ANS1483I Schedule log pruning started.
11/01/06   06:06:03 ANS1484I Schedule log pruning finished successfully.
11/01/06   06:06:03 Querying server for next scheduled event.
11/01/06   06:06:03 Node Name: VRAM3.LOGS
11/01/06   06:06:33 Session established with server TSM-CAPELLA:
AIX-RS/6000
11/01/06   06:06:33   Server Version 5, Release 3, Level 3.4
11/01/06   06:06:33   Server date/time: 11/01/06   06:06:33  Last access:
11/01/06   03:16:31

11/01/06   06:06:33 --- SCHEDULEREC QUERY BEGIN
11/01/06   06:06:33 --- SCHEDULEREC QUERY END
11/01/06   06:06:33 Next operation scheduled:
11/01/06   06:06:33
------------------------------------------------------------
11/01/06   06:06:33 Schedule Name:         VRAM3.ARCHLOG
11/01/06   06:06:33 Action:                Command
11/01/06   06:06:33 Objects:               /notes/vram3/domarchive
11/01/06   06:06:33 Options:
11/01/06   06:06:33 Server Window Start:   07:00:00 on 11/01/06
11/01/06   06:06:33
------------------------------------------------------------
11/01/06   06:06:33 Scheduler has been stopped.

11/01/06   06:06:44 Finished command.  Return code is: 9
11/01/06   06:06:44 ANS1909E The scheduled command failed.
11/01/06   06:06:44 ANS1512E Scheduled event 'VRAM3.INCR' failed.  Return
code = 9.
11/01/06   06:06:44 Sending results for scheduled event 'VRAM3.INCR'.
11/01/06   06:06:44 Results sent to server for scheduled event
'VRAM3.INCR'.

11/01/06   06:06:44 ANS1483I Schedule log pruning started.
11/01/06   06:06:44 ANS1484I Schedule log pruning finished successfully.
11/01/06   06:06:44 Querying server for next scheduled event.
11/01/06   06:06:44 Node Name: VRAM3.VCU.EDU





Del Hoobler <hoobler AT US.IBM DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
11/02/2006 12:05 PM
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
Re: [ADSM-L] Dictionary of TDP for Domino return codes - 2nd attempt






Zoltan,

For TSM ACTION=COMMAND schedules, the return code of the last
executing program within the script will be the error code
that gets bubbled back up to the scheduler and recorded
in the scheduler log. Make sure your scripts are
trapping that error code and return that code, if there
are other things in the script. Also... if you use the
Windows START command, that won't work to trap the error code.

To find out what is causing the errors you are seeing, I recommend
looking at the redirected output from the running command
(if you are not redirecting the output from the command, you should do so)
Also, the domdsm.log file should have recorded the errors it encountered.

Thanks,

Del

----------------------------------------------------

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 11/02/2006
11:32:40 AM:

> These are all Domino TDP backups. They are a simple, one-line DOMDSMC
> command-file/script.  No post/pre anything.  Just Domino voodoo.
>
> Nothing has changed on these systems, for a while.  Some days the
backups
> run fine, other days they fail.
>