×
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.
"Winchester Terry" <terry.winchester@xxxxxxxxxxxxxxx> wrote in message
news:mailman.5442.1179339400.13580.cobol400-l@xxxxxxxxxxxxxxx
We have found it best to use CRTDUPOBJ and duplicate
QPRINT to another name like QPRINT1, QPRINT2, etc.
then change each SELECT statement to use the new
object name.
OK. I see that we already have QPRINT, QPRINTS and QPRINT2 output queues
defined on our system. They must be IBM-provided because I did not set them
up. I'm still too new to the iSeries to understand the ramifications of
this.
But does putting multiple reports from the same program/job to different
output queues make it difficult to keep up with and manage them?
What if you really needed to have both reports as multiple printer files
attached to the same job? Is that not possible? If it's a bad idea please
explain why.
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.
midrange.com
