× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Michael,

I don't uses SYSOUT for the same reason - the job log
gets full rather quickly.  IMO, adding a print file 
(like QPRINT) to the program is the easiest way to
accomplish the task. In fact, nearly all of my
programs (interactive and batch) have print files
defined "just in case" ;-)

Terry Winchester 
Programmer/Analyst
________________________________
The Raymond Corporation
terry.winchester@xxxxxxxxxxxxxxx 

-----Original Message-----
From: cobol400-l-bounces@xxxxxxxxxxxx 
[mailto:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of Michael Rosinger
Sent: Wednesday, December 13, 2006 6:18 AM
To: cobol400-l@xxxxxxxxxxxx
Subject: [COBOL400-L] SYSOUT vs. QPRINT for debug-type information...

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.



Confidentiality Notice:

The preceding e-mail message (including any attachments) contains information 
that may be confidential, protected by applicable legal privileges, or 
constitute non-public information. It is intended to be conveyed only to the 
designated recipient(s). If you are not an intended recipient of this message, 
please notify the sender by replying to this message and then delete it from 
your system. Use, dissemination, distribution or reproduction of this message 
by unintended recipients is 
not authorized and may be unlawful.





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.