Migration Script reports as failed

Hi Everyone,

I am in the process of trying to clean-up some of the alerts generated by some of our scripts

One such alert we receive, is when the Migration script fails, for what I think is where Migration is already running.

A couple of questions -

1) If Migration is already running for any given STG Pool, and the script tries to invoke, is that enough of an issue for the overall script to report as a fail?

(Our Migration script invokes Migrations for a load of STG pools)

For example,

We see this -

ANR2753I (MIGRATION):currently running for the storage pool (SESSION: 55449)

and then -

ANR2752E Scheduled command MIGRATION failed. (SESSION: 55449)




2) Can we modify the script to check for an already running Migration for any given STG Pool


Help appreciated.
I am not a scripter, but happy to have a go!

Thanks