Re: BRMS SWA monitor using Control M

I (maybe) did something similar for another job automation piece of
software (Jams).
It depends a bit on what you are able to monitor from your software, in the
case of Jams (or maybe the administrator in this case) it could only easily
monitor jobs submitted from Jams.
What I did was write a small CL that created a data area, submitted the
BRMS job to batch and then monitored the existence of that data area. When
the data area no longer existed the job ended.
The BRMS control group had a MONSWBRM in it and when the SWA boundary was
reached it deleted the data area to signal the first job to go to end.
Jams submitted and then monitored the first job (the small CL) and when it
saw it end, carried on with the rest of the job stream while the save while
active carried on in the background.
Not saying this is the best way but it worked in this case.

On Sat, Apr 24, 2021 at 8:41 AM Amaljith PM <amaljithh@xxxxxxxxx> wrote:

Hi,

My intend was to have a separate job for backup from remaining cycle
process so that it's easy for operators to know which Team to contact just
by looking at the job.
So if I can use MONSWABRM command separately I can monitor that from
control M and kick off once its done.

On Sat, 24 Apr 2021, 12:39 am , <midrangel@xxxxxxxxxxxxxxxxx> wrote:

Why not just put MONSWABRM in as an exit in the control group and let it

do

its thing? The help text is fairly good on that command.

Yes, you could put it into a CL if need be.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Amaljith PM
Sent: Friday, April 23, 2021 1:55 PM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: BRMS SWA monitor using Control M

Hi, does anyone know how to monitor SWA checkpoint from control after

which

we can kick off another job.

Alternatively if that's not possible is there a way to include MONSWABRM

in

CL code

Regards,
Amaljith
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link:
https://amazon.midrange.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com