|
Vern any reason why wrapping the command in a CL (or RPG for that matter) is not an option ? Then you could just lock the program you are calling. It seems to me that locking a CPP might be dangerous (for some reason I am getting the impression you are talking about an IBM CPP) as depending on the command the program could be in use elsewhere which might or might not cause unpredictable results - it might even be exactly what you want :). As to why it fails, an error message or some code showing what is happening might help suggest an answer. Regards Evan Harris >I want to have only one job runa program at a time. CL Programming >suggests ALCOBJ *EXCL on the program object. In this case, it's a >command processing program that I want to restrict. Calling it directly, >or trying to debug, fail. However, another job can run it through the >command. Is this normal? Is there a way around it?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
