|
Just a note... If your reports are ILE, make sure you account for programs that *may* run in separate activation groups... Say the cover sheet program PGMA runs in the DFTACTGRP but the report program PGMB runs in a named AG Ovrtprtf qsysprt share(*yes) Call PGMA Call PGMB Dltovr qsysprt You'll get 2 spooled files... Thanks, Tommy Holden -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Lapeyre, Francis Sent: Tuesday, July 11, 2006 3:40 PM To: 'RPG programming on the AS400 / iSeries' Subject: RE: Keeping QPRINT open We have a lot of report programs that work this way. We use one program as a "standard" cover sheet, using QSYSPRT. The actual program may or may not have additional parameters to show other than the ones produced by the cover sheet program. We override QSYSPRT with SHARE(*YES), call the cover page RPG, then call the regular report program, and it looks to the user like one program did everything. I checked our cover sheet program just now -- for the record, it does NOT set on *INLR. Francis Lapeyre IS Dept. Programmer/Analyst Stewart Enterprises, Inc. E-mail: flapeyre@xxxxxxxx -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of AGlauser@xxxxxxxxxxxx Sent: Tuesday, July 11, 2006 2:37 PM To: RPG programming on the AS400 / iSeries Cc: Midrange Systems Technical Discussion Subject: Re: Keeping QPRINT open --> Moved to RPG400-L at the request of the moderator <--
What language are the programs in? If RPG, I think it's as simple as leaving LR off until the last program. You might also have to override QPRINT to share(*yes) before you start(?).
It may not even be necessary to leave *INLR off. I had a similar problem recently: I wanted to have PGMA read through an IFS directory, passing each file (exluding . and ..) to PGMB for processing. PGMB produces an error report of records that need user attention, and I wanted all of the records from all calls to PGMB to show up on the same report. The trick was to override the print file to have SHARE(*YES), then open the file in PGMA (even though it was not used). This way, PGMB can open and close the print file at will, but the print file will not be handed over to the spooler because it is still in use by PGMA. If you have (or can add) a 'controller' program to the jobstream, you should be able to use a similar method. Hope this helps, Adam midrange-l-bounces@xxxxxxxxxxxx wrote on 11/07/2006 11:36:15 AM:
I tried using an indicatior on the line of code that sets on LR and
ran it
through the interactive source debugger. The program never exited.
It
just kept running and printing multiple copies of the report for
that
program. I cannot take out the "MOVE *ON *INLR" line because
the
program won't compile (of course). So, how do I exit the program
forcing
it to run only one time? Here's what I did... C*---------------------------------------------------------------- C*-M A I N L I N E C A L C U L A T I O N S- C*---------------------------------------------------------------- C EXSR DET90 C EXSR DET91 C SETON
50
C N50 MOVE *ON *INLR ----------------------------------------------------------------------
Reply-To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To: "Midrange Systems Technical Discussion"
<midrange-l@xxxxxxxxxxxx>
Subject: Re: Keeping QPRINT open Date: Mon, 05 Jun 2006 17:01:18 -0400 >What language are the programs in? If RPG, I think it's as simple
as
>leaving LR off until the last program. You might also have to
override
>QPRINT to share(*yes) before you start(?). > >Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
on
Monday, >June 05, 2006 at 3:19 PM -0500 wrote: > > I have a project where I need to convert spool files to PDF files. I > >have > > 13 programs that use QPRINT as the output file. Rather
than
create 13 > > seperate PDF files, I'd like to keep an instance of QPRINT
open
and > >create > > one large PDF file from the single spool file. Is there a
way (or
> > command) to keep the print file open through the duration
of the
13 > > progams? > > >Mike Naughton >Senior Programmer/Analyst >Judd Wire, Inc. >124 Turnpike Road >Turners Falls, MA 01376 >413-863-4357 x444 >mnaughton@xxxxxxxxxxxx > >-- >This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing
list >To post a message email: MIDRANGE-L@xxxxxxxxxxxx >To subscribe, unsubscribe, or change list options, >visit: http://lists.midrange.com/mailman/listinfo/midrange-l >or email: MIDRANGE-L-request@xxxxxxxxxxxx >Before posting, please take a moment to review the archives >at http://archive.midrange.com/midrange-l. > -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
######################################################################## #### ######### Attention: The above message and/or attachment(s) is private and confidential and is intended only for the people for which it is addressed. If you are not named in the address fields, ignore the contents and delete all the material. Thank you. Have a nice day. For more information on email virus scanning, security and content management, please contact administrator@xxxxxxxxxxxx ######################################################################## #### ######### -- This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.
As an Amazon Associate we earn from qualifying purchases.
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.