Hello, I also put this question to the BMC communities page but have not received any feedback.
I am looking for ideas or solutions for this problem - if I wish to develop an external application to Control-M that can modify folders or calendars (think home grown Workload Change Manager), how can I handle the problem of a user making a change in one system while another makes a change to the same folder/calendar in the other?
So far, I've logged an RFE QM002343551 to request for some API or CLI way to lock a folder or calendar.
I've also looked and found I can check for folder locks and updates from Control-M and utilities through the Database. I can likely workaround using these techniques by checking through the homegrown app for locks/updates, but a more ideal approach would be to simply lock it down.
If you've developed or been a part of this type of project before, how did you handle this concurrency problem? And of course, if you haven't, have you other ideas for how this could be implemented?