Hi Tony,
  We don't use Autosys, whatever that is, nor do we use ADSM's built in
scheduler.  Instead, we've written a series of shell scripts which are
launched from cron.  For actions like stgpool and database backups, the
scripts generally have to cycle, doing "query process" until the activity is
finished.  I don't see how you can avoid such checking - as you note,
commands like "backup stgpool" start a background process which must
complete (or be cancelled).  Maybe if there were a toggle to force such
commands to wait until their requested action was completed - wouldn't it
want it to be the default behavior, though (and what about interrupt
signals?)...

Jim

> ----------
> From:         Sinclair, Tony[SMTP:TJSinclair AT SNOPUD DOT COM]
> Sent:         Tuesday, March 03, 1998 3:31 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      ADSM & Autosys
>
> Hello,
>
> This message is directed to those of you that have your ADSM commands
> and backups being scheduled through Autosys.
>
> I am currently running ADSM v 1.12 on a AIX 4.1 server with Autosys v
> 3.4.
> It has been discussed that we should use Autosys to handle our ADSM
> Command Schedule and Backup functions.  I would like from those of you
> that use Autosys to input on how this is accomplished.  I have one major
> concern  with this, and that is the condition code checking issue..
> Once a command is passed from Autosys to ADSM and the command is
> processed and completed a "0" condition code is passed back to Autosys,
> but yet the backup process is still executing and probable won't finish
> for some time.  It does not seem to me I can schedule jobs on succession
> of a proceeding job based on just condition code checking.
> I will be asking Platinum the same question, but have more confidence in
> the user community.  So any information you can provide would be greatly
> appreciated.
>
> Thanks   Tony..
>
> Tony Sinclair
> ADSM Admin.
> Snohomish County PUD
> tjsinclair AT snopud DOT com
>