We have a the same situation with a cyclical job that runs 22/7. We had to define 3 job definitions for the same job letting it run from 06:00 to 13:00, then from 14:00 to 18:00, and then from 20:00 to 05:00. It was the same job, that ran at different times.

Example: 1. Check if web site is up, send http request https://empower-central.ussco.com/healthcheck.jsp Returns http status code 200 if successful 2. Send URL request to web application to trigger request to refresh some data, etc. Http request would be something like https://empowercentral.ussco.c...

CONTROL-M/Enterprise Manager 7.0.00 400 I want to be able to kick off a control m job to kick off a script and use parameters to determine • which machine to run it on • pass arguments to the script the arguments are coming from WebSphere API and we are able to add conditions from the API successful...