× 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.



Jack,

Thanks for responding to my inquiry. I have been able to suppress the blank page by changing the COBOL code to print after advancing zero lines (rather than PAGE) for the very first line of print (if line count equal 99). Thanks, again.

Marge

cobol400-l-request@midrange.com wrote:

Send COBOL400-L mailing list submissions to
cobol400-l@midrange.com

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.midrange.com/mailman/listinfo/cobol400-l
or, via email, send a message with subject or body 'help' to
cobol400-l-request@midrange.com

You can reach the person managing the list at
cobol400-l-owner@midrange.com

When replying, please edit your Subject line so it is more specific
than "Re: Contents of COBOL400-L digest..."


Today's Topics:

1. Extra Print Lines (Margaret Rozmarynowycz)
2. Re: Extra Print Lines (welchj@kdsi.net)
3. R: Extra Print Lines (Finucci Domenico)


----------------------------------------------------------------------

message: 1
date: Wed, 12 Feb 2003 15:32:10 -0800
from: Margaret Rozmarynowycz <mrozmary@lorainccc.edu>
subject: Extra Print Lines

Greetings to all.

I have search the archives on this subject but have found no references to it. The problem is extra print lines at the top of QPRINT files. When the QPRINT file is copied to a physical file, it looks like this:

001 1 001 02/05/03 23:24:08 FAENRL 1 1CENSUS DATE USED 01/27/03 3PELL NMID NAME 2 * 246138 Sandra T. Angney

My program is not explicitly writing the '001' and '1' lines at the top of each QPRINT. This is not a big deal when printing a large batch run, but it is for individual random read and print runs. The problem involves various QPRINT files we have, some landscape, some portrait, with various settings. (It is not a problem with a program-generated print file we have from a third party vendor). Does anyone know how to get rid of these extra lines?

Marge Rozmarynowycz

------------------------------

message: 2
date: Wed, 12 Feb 2003 18:07:06 -0600 (CST)
from: <welchj@kdsi.net>
subject: Re: Extra Print Lines

Marge,

Did you use CPYSPLF CtlChar(*PRTCTL) to copy the spool file to a Phy File
or some other mechanism? I presume you did based on your example.

if so... the 001 is control to indicate report will jump to line 001 before
if prints. The first 001 would print a blank line on page 1. The second 001
would jump to page two, line 1 and print "02/05/03 23:24:08 FAENRL"

001 <--- jump to line 1 of page(new page)
1 <--- quantity of lines to skip before printing

It appears you have a blank page in front.

Are you using overflow processing that would cause a page jump at the
beginning of your output?
Do you have Seperator Pages designated on your print files, in overrides,
or on the OUTQ?

1. Have you actually printed this report? What does it look like?
2. If you display the spool file you can use the "Page/Line" info in the
top right of the screen to help debug.


Jack




Greetings to all.

I have search the archives on this subject but have found no references
to it. The problem is extra print lines at the top of QPRINT files.
When the QPRINT file is copied to a physical file, it looks like this:

001
1
001 02/05/03 23:24:08 FAENRL
1
1CENSUS DATE USED 01/27/03
3PELL NMID NAME
2 * 246138 Sandra T. Angney

My program is not explicitly writing the '001' and '1' lines at the top
of each QPRINT. This is not a big deal when printing a large batch run,
but it is for individual random read and print runs. The problem
involves various QPRINT files we have, some landscape, some portrait,
with various settings. (It is not a problem with a program-generated
print file we have from a third party vendor). Does anyone know how to
get rid of these extra lines?

Marge Rozmarynowycz

_______________________________________________
This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing
list To post a message email: COBOL400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/cobol400-l.


_______________________________________________
Jack Welch
welchj@kdsi.net
(308) 395-8708
_______________________________________________




------------------------------

message: 3
date: Thu, 13 Feb 2003 09:32:11 +0100
from: Finucci Domenico <Domenico.Finucci@Fiditalia.it>
subject: R: Extra Print Lines

Try CTLCHAR(*PRTCTL) option of CPYSPLF. Sincerely

Domenico Finucci
Fiditalia , Milano, 02- 4301-2494


-----Messaggio originale-----
Da: Margaret Rozmarynowycz [mailto:mrozmary@lorainccc.edu]
Inviato: giovedì 13 febbraio 2003 00.32
A: COBOL400-L@midrange.com
Oggetto: Extra Print Lines


Greetings to all.

I have search the archives on this subject but have found no references to it. The problem is extra print lines at the top of QPRINT files. When the QPRINT file is copied to a physical file, it looks like this:

001 1 001 02/05/03 23:24:08 FAENRL 1 1CENSUS DATE USED 01/27/03 3PELL NMID NAME 2 * 246138 Sandra T. Angney

My program is not explicitly writing the '001' and '1' lines at the top of each QPRINT. This is not a big deal when printing a large batch run, but it is for individual random read and print runs. The problem involves various QPRINT files we have, some landscape, some portrait, with various settings. (It is not a problem with a program-generated print file we have from a third party vendor). Does anyone know how to get rid of these extra lines?

Marge Rozmarynowycz
_______________________________________________
This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing list
To post a message email: COBOL400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/cobol400-l.


------------------------------

_______________________________________________
This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) digest list
To post a message email: COBOL400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/cobol400-l.



End of COBOL400-L Digest, Vol 1, Issue 203
******************************************








As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.