I have learnt through Net that Debugging a Batch job involves
1. Submit the job with the HOLD (*YES) parameter:
SBMJOB HOLD(*YES) or Hold the job queue that before submitting the job
by using the HLDJOBQ command.
2. Determine the job name, user, and number of the submitted job by using the WRKSBMJOB command.
3. Type the Start Service Job command on your screen: STRSRVJOB JOB(job name/user/number)
4. Type the Start Debug command on your screen: STRDBG
5. Release the job in the jobq. Type WRKSBMJOB and then put a 6
beside the job to be released and press enter, or, if the job queue was
put on hold, release the job queue with the RLSJOBQ command.
6. A display appears when the job is ready to start, saying that you
can now begin debugging the job. Press F10 to show the Command Entry
display.
7. Now you can start debugging by entering an Add Break Point command:
ADDBKP
8.ENDDBG
9.ENDSRVJOB
I tried this for RPG/400 Program and up to six steps of the above it's ok,but for me no source is displayed and i typed DSPMODSRC in Command line but still i can't see the sourceif i press F.10 and enter command ADDBKP i don't know how to add break points through it,usually i add break points using F.6 for Interactive job debugs,but since this is batch i don't know sir,Please help me out.
for RPG/400 Program ...,but for me no source is displayed and i typed DSPMODSRC in Command line but still i can't see the source...
If it's RPG/400, DSPMODSRC can't be used because RPG/400 isn't created from modules. There is no module (MOD) source (SRC) to display (DSP).
Please verify that you are using RPG/400 rather than ILE RPG. The two are debugged in somewhat different ways. Are you comfortable that you know the difference between RPG/400 and ILE RPG?
Tom
Also, I haven't tried it for RPG/400, but I wouldn't debug a batch program that way for ILE. (I've only used ILE in the past 15 years or so.)
I would use a "service entry point" to do the work. That can be done through WDSC (or RSE) or it can be done through the use of two emulator sessions. It can be a little confusing through emulator sessions, but I see flaky behavior in WDSC that's hard for me to control.
If this turns into an ILE RPG discussion, I'll go through the steps for green-screen service entry points.
Tom
sir thanks for responding.I was asked this question in a interview,i know only RPG/400 and i'm asking for debugging of RPG/400 program only sir.
debugging batch job in rpg/400
is it only possible to debug BATCH RPG ILE JOB and it is not possible to debug BATCH RPG/400 JOB
The steps that you listed in your question will work for RPG/400. Testing shows that a service entry point can only be set for ILE programs.
That doesn't surprise me. It just shows me how far RPG/400 is in my past.
Tom
so we require ILE debugger or RPG debugger is enough
They are the same. You use the same debugger for both -- you just specify slightly different parameters.
ah,if i use RPG debugger i can’t see the source so as to add break points and debug
For RPG/400, the program must be compiled with the OPTION(*SRCDBG) option. This is similar to ILE RPG where you must compile with DBGVIEW(*SOURCE) in order to connect with the source for debugging.
Tom
Free Guide: Managing storage for virtual environments
Complete a brief survey to get a complimentary 70-page whitepaper featuring the best methods and solutions for your virtual environment, as well as hypervisor-specific management advice from TechTarget experts. Don’t miss out on this exclusive content!
Discuss This Question: 7  Replies