AutoSys Workload Automation

CA Tuesday Tip: (CA 11) How to avoid leaving the LOCKs in place in AL7BKUP

  • 1.  CA Tuesday Tip: (CA 11) How to avoid leaving the LOCKs in place in AL7BKUP

    Broadcom Employee
    Posted 05-20-2014 05:06 PM

    CA Workload Automation Restart Option for z/OS Schedulers Tuesday Tip by Alisa Puckett, Sr. Support Engineer for May 20, 2014

     

    The AL7BKUP job contains LOCK and UNLOcK statements in the DBUTLTY step.
    If for some reason the BACKUP job does not  complete successfully (i.e., the
    BACKUP portion failed) then the UNLOCK doesn’t execute leaving the LOCKs in
    place. This is  because the LOCK/BACKUP/UNLOCK are in the same DBUTLTY step,


    The  AL7BKUP job can be adjusted to separate the LOCK and BACKUP statements
    into one step, and the UNLOCK statements into a second step with a COND=EVEN
    which will allow it to run regardless of what happens prior.


    For additional information, please visit the support.ca.com website to view tech doc
    TEC610646 entitled 'Updated version of AL7ADUP to avoid leaving the LOCKs in place' at
    the link below for an updated version of AL7BKUP. 

    https://comm.support.ca.com/?legacyid=TEC610646