Automic Workload Automation

I'm currently working on some Java applications to set the isActive or isBreakPoint values on given Jobs or Tasks within JobPlans (we want to restrict editing rights for various user groups but still require an ability to activate/deactivate otherwise essentially read-only objects), but I noticed a behavior where in the call to open an object failed if the object was already in use.  I've been looking through the API documentation and I haven't yet found the method call to test if an object is in use prior to attempting to open it.  I do note that there's a constructor to open an object read-only, so I figure if that option is available the fact that in-use objects cannot be accessed is known.  I'd wager it may be possible within the JCL (prior to calling my java code) in a Job but I haven't had the time to research that angle yet.

Short version: Does anyone know the proper method for testing if an object is in-use?

Edit: Additionally, is it possible to determine the user who has the object open so they can be notified?  It may be a rare instance, but there can occasionally be time-sensitive processes and it would be good to have the option.

Not sure how I overlooked it but it looks like getUC4Object will do the trick for testing whether an object is in use (it will return null if the object is not available).  Still would like to see if the user using the object can be determined.

Hi,

About checking whether an object is being used:

you can use the XMLRequest subclass called GetObjectProperties(UC4ObjectName name): it has a method called "getOpenByUser()" which should return the name of the user that has the object open in R/W mode (or nothing otherwise).


About forcing the API to take over an object that is opened by a User:

you can use the XMLRequest subclass called ResetOpenFlag(UC4ObjectName name): it will basically ensure that the "edit" flag is taken away from the user editing the object.. You can then use the OpenObject request to open the object in R/W with the API. Note that the user from which the edit flag is removed will get an error message that his/her modifications could not be saved.

bren