Not trying to be contrary, but have you tried using the integrated debugger in WDSc? I never use DISPLAY statements or printer files for obtaining debug type information anymore--I find it so much more flexible and powerful to use the debugger. I can stop at any line with one or two click of the mouse. I can display any elementary item value by simply hovering the mouse pointer of the variable name. You can also set up a monitor of an elementary or group item and watch the value change as I step through the program or run to any number of breakpoints. I prefer using the debugger, because I then have nothing to change once I'm ready to move a program to production. i.e., I've tested the exact code that will go into production without any changes. If I use DISPLAY statements or printer files for debugging information, I have to modify the code before promoting the code. These features can also be emulated from the green screen--albeit they are not as intuitive. Someone in Rochester also set up a graphical interface to the standard system debugger--I've tried it but I prefer the integrated debugger in WDSc since I'm always in that environment. If you're shying away from WDSc, then try the graphical interface to the system debugger. Either way--I think once you've tried them, you'll never want to go back. Just my 2 cents worth. Michael Quigley AS/400 Programming Section The Way International www.TheWay.org cobol400-l-bounces@xxxxxxxxxxxx wrote on 12/13/2006 01:00:03 PM:
date: Wed, 13 Dec 2006 06:18:09 -0500 from: "Michael Rosinger" <mrosinger@xxxxxxxxx> subject: [COBOL400-L] SYSOUT vs. QPRINT for debug-type information... List, Another ILE/COBOL newbie question. I was running a test program where I
issuing a lot of DISPLAY UPON SYSOUT messages for debug purposes. The
was cancelled by the system because "the size of the message queue for
xxx reached the maximum size". I see from the output that in addition to
lines I was interested in seeing there were lots of system-generated
that I did not care about. In the mainframe world, we are used to using a lot of DISPLAY UPON
(if need be) and they just get routed to a different spooled entry which
separate from any of the other reports the program may generate. It's readily accessible if you happen to need it to verify a problem and
discarded if you don't. So, in the iSeries world, what is the "acceptable" way to create printed
output for debug and tracking purposes? Coding a DISPLAY UPON SYSOUT is,
course, easier than defining and writing to a print file, but it's not a
deal if that is what must be done. Your suggestions please? TIA -- Regards, Michael Rosinger Systems Programmer / DBA Computer Credit, Inc. 640 West Fourth Street Winston-Salem, NC 27101 336-761-1524 m rosinger at cciws dot com
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.