Hello Werner:

Your problem is with your command script:
      /usr/local/bin/test_adsm.sh
as you are not running any backup - just a scheduled command.
The error resulted when it tried to run the script you specified.

It's probably something simple, like,
      - did you "chmod 777  ... your script to make it executable?
     - does the user account that you used to start dsmc have write access
rights to /usr/local/log directory ?
     - Are you running in C-shell?  (it won't work if you are.  By default
the script uses the same shell you are running in   - to be safe, insert a
line at the very beginning of your script to run it in a borne-shell, as
follows:
#!/bin/sh

     - etc...

Hope this helps!  :-)

 ----------
From: owner-adsm-l
To: Multiple recipients of list ADSM-L
Subject: Re: ADSM - Scheduler
Date: Thursday, November 7, 1996 8:50AM

Paul Zarnowski wrote:
>
> On Mon, 4 Nov 1996 13:51:38 +0100 Werner Thoeni said:
> >So we have observed, that this schedule is executed on some of the nodes
> >but not on every node. The scheduler-log on the client says, that the
> >schedule has been executed, as defined, but not in reality. Has anybody
> >an idea, or has anybody had the same problem ??
>
> Werner,
>
> You don't say how you determined that the scheduler did not run in
reality.
> I have observed that at some level of the AIX ADSM client IBM changed the
> default logging option from -VERBOSE to -QUIET.  This makes the scheduler
> log very short, and might be interpreted as "not running in reality".
> Could this perhaps be what is happening?
>
> You might check (1) what QUERY EVENT reports, and (2) what the ADSM
> accounting log indicates (in terms of whether any files were actually
> backed up for the node), and (3) what QUERY FILESPACE F=D reports for
> the last backup completion date/time.  This should only be updated after
> a successfully completed backup.
>
> ..Paul
>
> Paul Zarnowski                     Phone:   607/255-4757
> Cornell Information Technologies   Fax:     607/255-6523
> Cornell University                 US Mail: 315 CCC, Ithaca, NY 14853-2601



Hi Paul,

Within the scheduler log we got the return code number "9" returned by
the scheduler. Afterwards you will get a listing from the AIX-scheduler
log:

11/04/96   11:29:14 Next operation scheduled:
11/04/96   11:29:14
 ------------------------------------------------------------
11/04/96   11:29:14 Schedule Name:         M086_CMD_TESTNODE2_MON1200
11/04/96   11:29:14 Action:                Command
11/04/96   11:29:14 Objects:               /usr/local/bin/test_adsm.sh
11/04/96   11:29:14 Options:
11/04/96   11:29:14 Server Window Start:   12:00:00  on 11/04/96
11/04/96   11:29:14
 ------------------------------------------------------------
11/04/96   11:29:14 Command will be executed in 48 minutes.
11/04/96   12:17:14
Executing scheduled command now.
11/04/96   12:17:14
Executing Operating System command or script:
   /usr/local/bin/test_adsm.sh
11/04/96   12:17:14 Finished command.  Return code is:
   9
11/04/96   12:17:14 Scheduled event 'M086_CMD_TESTNODE2_MON1200'
completed successfully.
11/04/96   12:17:14 Sending results for scheduled event
'M086_CMD_TESTNODE2_MON1
200'.



The script /usr/local/bin/test_adsm.sh does the following:

LOG=/usr/local/log/test_adsm.log

echo `date` >$LOG

exit 0


The script above never wrote any date to the LOG file.

Thanks for taking place to my problem,
Werner

 --
Dipl.-Ing. Werner THO"NI           INTERNET: Werner.Thoeni AT uklibk.ac DOT at
System Group

Tschamlerstrasse 2
A-6020 Innsbruck/Austria
PHONE    :   +43 512 5345 264       FAX      :   +43 512 5345 382