Re: SYSOUT vs. QPRINT for debug-type information...

Just don't forget to recompile the program after you're done debugging
without the debug option.  


Basil Zangare
Applications Specialist
Nikon Inc
1300 Walt Whitman Road
Melville, New York 11747
phone: (631) 547-4389
fax: (631) 547-4026
bzangare@xxxxxxxxx


-----Original Message-----
From: cobol400-l-bounces@xxxxxxxxxxxx
[mailto:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of Rich Loeber
Sent: Wednesday, December 13, 2006 8:06 AM
To: COBOL Programming on the iSeries/AS400
Subject: Re: [COBOL400-L] SYSOUT vs. QPRINT for debug-type
information...

Michael,

If you're debugging, then I'd strongly recommend that you just try using
the
interactive source level debugger that is built into the OS on the
iSeries.  You
have to compile your program a little differently, specifying source
debugging.
Then, before you run your program test, just start the interactive
debugger
(STRDBG).  During the start process, the source for your program will be
displayed; just press the F10 key to continue.  Then, run your program.
When
the program gets called, the actual source statement will be displayed
and you
can use the F10 key to walk through the program on a step-by-step basis.
If you
want to view any of the variables, please the cursor over the variable
and press
the F11 key.  This just gets you started, but it is a much better form
of
program debugging.  If you want the program to run to a specific point,
then you
can set a breakpoint and the program will run until it reaches that
point and
then stop on the instruction that you set it for.  This, in my opinion,
is the
best way to debug on the iSeries in COBOL.  I can get a lot done in a
single
debugging session.  I came to iSeries COBOL years ago from mainframe
COBOL and
once I learned how to use the source debugger, I never looked back.

Rich Loeber
Kisco Information Systems
http://www.kisco.com
 
------------------------------------------------------------------------

Michael Rosinger wrote:

List,

Another ILE/COBOL newbie question. I was running a test program where

I was

issuing a lot of DISPLAY UPON SYSOUT messages for debug purposes. The

job

was cancelled by the system because "the size of the message queue for

job

xxx reached the maximum size". I see from the output that in addition

to the

lines I was interested in seeing there were lots of system-generated

stuff

that I did not care about.

In the mainframe world, we are used to using a lot of DISPLAY UPON

SYSLST

(if need be) and they just get routed to a different spooled entry

which is

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

easily

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, of

course, easier than defining and writing to a print file, but it's not

a big

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

--
This is the COBOL Programming on the iSeries/AS400 (COBOL400-L)

mailing list

To post a message email: COBOL400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/cobol400-l.