We are doing just about the same thing and are handling it in this way:

We use OPC/ESA for our production schedule and rely on the pred/successor job
relationships to ensure that the commands are issued when the correct order.
We issue all these commands via batch jobs and use a different job for each
'grouping' of commands.  For commands that complete almost immediately, we just
issue the command.  For commands that may take from 5-10 minutes, we put a
'wait' step in the job that simply causes that job to just sit in the system
for the specified period of time and do nothing.  This gives ADSM enough time
to finish the command before the job finishes.  For commands that can take an
unknown amount of time (backup stgpool and backup db) we use the MPFLST00
member of sys1.parmlib to detect the message issued by ADSM indicating that the
function is complete which.  When it is detected, it marks a 'dummy' job in
OPC/ESA complete and then the next job can begin.  If you would like more
detailed info on any of this, please let me know.


In the previous Memo, dated, 06-27-97 05:48:06 PM, TEHorn @ COMPUSERVE.COM
(Thomas Horn) @ MGICSMTP wrote:

The ADSM server environment for this question is MVS.

I would like to be able to automatically schedule the following steps to be
executed one after another.
It is important that step 2 is not started until all the commands in step 1
are finished.  The same is
true for the rest of the steps.

Step1: Incremental backup of primary storage pools

ADSM commands:
backup stgpool backupppool disaster-recovery
backup stgpool archivepool disaster-recovery
backup stgpool spacemgpool disaster-recovery
backup tapepool disaster-recovery


Step 2: Update volumes to offsite status

ADSM command:
update volume * access=offsite location='vault site info' -
wherestgpool=disaster-recovery whereaccess=readwrite,readonly -
wherestatus=filling,full


Step 3: Backup ADSM database

ADSM command:
backup db type=incremental devclass=devclassname scratch=yes


Step 4: Backup volume history, device configuration and server options
files to be taken to disaster recovery site.

Use MVS utilities backup volume history, device configuration and server
options files to be taken to disaster recovery vault site


Step 5: Create a disaster recovery pull list from CA-1 TMS which lists all
ADSM
datasets with the disaster recovery dataset prefix which are on site.