|
Hi Willie, > 2) I have never used the IBM Debug on a program. Can someone help > with setting up an IBM Debug on this program when the loop happens > again. I prefer using the STRDBG option. I used STRISDB a long time ago, but I don't remember how to use it, so I'll explain this using STRDBG. IMPORTANT: Before the problem occurs next, compile the RPGIII program with OPTION(*SRCDBG). (or if it's ILE, use DBGVIEW(*LIST)) Then, wait for the problem to happen again. When it does sign on to a different 5250 session, and do the following: a) Set up your library list & current library the same as the offending job. This is important, since it needs to be able to find the same program objects as the offending job. b) Use WRKACTJOB to find the offending job. Choose option 5 to display the job. At the top of the screen will be the job's name/user/number. At the command line at the bottom, type the following: (Note that the order of the fields is the exact opposite of what's at the top of the screen!) STRSRVJOB JOB(number/user/name) c) Start the debugger with (leave off the "OPMSRC" bit if this is an ILE program): STRDBG PGM(MYPGM) UPDPROD(*YES) OPMSRC(*YES) d) The program's source should display on the screen. Press F10 to step through the program, line by line. You can move the cursor to a variable and press F11 to display the variable's value, or type "eval VARIABLENAME" to see it's contents. Hopefully, by watching it run in that manner, you'll be able to see what it's stuck on / where it's looping.
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.