If you live outside the United States, by submitting your email address you consent to having your personal data transferred to and processed in the United States.
I’ll post an answer again – the other question seems to have disappeared.
Example 1 – You use batch debugging for long running jobs which may need to run through a lot of processes before you get to the part which you need to debug – Otherwise your interactive job may be busy for a long time before you get to the code or program that you want to debug.
Example 2 – If you run a batch program it works perfectly, but it doesn’t work correctly if another user runs it, the other user is not authorised to debug the program, so you let the other user start the program in batch and you debug it there.
There are other times when you may want to use batch debug, but I think these examples should give you the idea.
Hi Martin,
I did get answer to my question even I did not get question too.
Excuse me and pls add answer hereif you do not mind
Hi,
I’ll post an answer again – the other question seems to have disappeared.
Example 1 – You use batch debugging for long running jobs which may need to run through a lot of processes before you get to the part which you need to debug – Otherwise your interactive job may be busy for a long time before you get to the code or program that you want to debug.
Example 2 – If you run a batch program it works perfectly, but it doesn’t work correctly if another user runs it, the other user is not authorised to debug the program, so you let the other user start the program in batch and you debug it there.
There are other times when you may want to use batch debug, but I think these examples should give you the idea.
Regards,
Martin Gilbert.
Well if your job is already running and its in MSGW then you have to use Batch debugg.