|
> Which one is closed first? Was closing when pgm ended (not a specific close in rpg code). Let me try that (actually passing this on to another pgmr). The priority will not work - 10 order entry clerks all banging in orders, the print is in shipping & each order has to stay together. jim ----- Original Message ----- From: <rob@xxxxxxxxx> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> Sent: Thursday, August 18, 2005 9:50 AM Subject: Re: outq order of spooled files > Which one is closed first? > > Rob Berendt > -- > Group Dekko Services, LLC > Dept 01.073 > PO Box 2000 > Dock 108 > 6928N 400E > Kendallville, IN 46755 > http://www.dekko.com > > > > > > "Jim Franz" <franz400@xxxxxxxxxxxx> > Sent by: midrange-l-bounces@xxxxxxxxxxxx > 08/18/2005 08:43 AM > Please respond to > Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> > > > To > <MIDRANGE-L@xxxxxxxxxxxx> > cc > > Subject > outq order of spooled files > > > > > > > RPG pgm has 2 reports. In order to force the order of spooled files, > F spec for printer files has "UC" for user control. > Begin of program opens print1, then print2, then excpt the headings for > print1. > Print2 is an optional report and only sometimes has any detail. > On outq, PRINT2 is consistently printing first (when has data). > Same form type. > OVRPRTF only overrides the outq. > > File File Nbr Job User Number Date Time > PRINT2 2 L17 JIML 434569 08/18/05 07:36:52 > PRINT1 1 L17 JIML 434569 08/18/05 07:36:52 > > Outq definition - order of spooled files is *FIFO. > > btw - older version of this app was running in S36 environment, > and was always working just fine, print1 was always 1st. > > Creating major disruption & confusion of order tickets - has been > print1 then print2 since S/34 days. Native RPG went live Monday. > > jim > -- > 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. > >
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.