Hi Lars, global condition cleanup is no different than any other condition cleanup using ctmcontb.
thanks for your answer, but this is not really what I was looking for.
This is our problem:
- 1. A global condition is set by JOBA with Odate 3008, it looks like "G-JOBA 3008"
- 2. A JOBB should run on September 10th. The job waits for "G-JOBA ****". We have a
maintenance job that deletes all conditions older than 15 days, so normally, the
job should be running. But the condition "G-JOBA 3008" is not
existing any more. There's no entry in the Control-M log that "G-JOBA
3008" was deleted.
Like I said, I assume that there is an automatic routine in either the GCS on mainframe or distributed to delete Global conditions after X amount of days (I suppose 10). But
I don't know where I can find it and maybe even change it.
Hopefully it's easier
to understand my problem now.
Hi Lars, the only way I could see this happening is if the global condition was set prior to newday on the 30th August.
Does the newday on your source datacentre and destination datacentre run at the same time? Is it possible that:
Condition is added on datacentre A
Condition is passed to datacentre B (check the GCS logs to ensure this happened)
Newday for 30 August runs on datacentre B and performs future condition cleanup?
The condition delete should exist somewhere in the Control-M log, ctmcontb logs, or GCS logs over that 10 day period.
It might be worthwhile scheduling a database query over the 10 days to try and pinpoint when the condition is being deleted.