You know that ‘single user mode’ will change the runtime target of the target OS right ? i don’t think this is going to accomplish what you want. for a deploy job there is a ‘single job mode’ which is probably what you want.
In my case the 'enable single-job mode' is already enabled (I guess because I had selected the single-user mode which as per user guide would pre-select the the 'enable single-job mode').
Despite this, the jobs seem to run in parallel against the same target.
Could it be that it would show as 'running' but behind the scenes, the queue would kick in? If this is indeed the case, then I would be super happy to accept this behavior.
Also, just for the sake of my knowledge (sorry, I am bit of a newbie with BMC products and related concepts),
"You know that ‘single user mode’ will change the runtime target of the target OS right ?"
What do you mean by "changing the runtime target of the target OS"?
Thank you very much Bill
single user mode has nothing to do w/ single job mode. make sure we are taking about the same thing. for single job mode i'm not sure what the behavior is off the top of my head - it might sit in the running state and then actually execute when the 1st job is done. good look in the job run log in the gui and see if the 'simulate' for the 2nd job is running while the 1st one is running.
single user mode: Single user mode - Wikipedia, the free encyclopedia
single job mode
Thank you very much Bill,
This helped me look for what I wanted.
You are right, the job which is supposed to queue, shows the 'running' status but it actually waits in the 'commit' phase until the lock obtained by the currently executing job (against the same target) ends.
So it’s doing what you want ?