Re: outq order of spooled files

> If it wasn't broken, why fix it?
Many other changes made in logic & application in a rewrite (not simple
conversion)
of entire Order Entry system. Added subfiles, window popups, etc to greatly
enhance
app. (btw - i'm not the pgmr but do support them for system issues)

In testing, did not fail because (and we can duplicate this..) it will be in
correct order
if spooled files have ovrprtf that places on HOLD when generated.<crazy>

jim
----- Original Message ----- 
From: <pnelson@xxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Thursday, August 18, 2005 9:51 AM
Subject: Re: outq order of spooled files


>
> If it wasn't broken, why fix it? In my book, expedience trumps elegance
> every time.
>
> There is still a use for the RPG cycle from time to time.
> --
>
> Paul Nelson
> Arbor Solutions, Inc.
> 708-670-6978  Cell
> pnelson@xxxxxxxxxx
>
>
>
> -----midrange-l-bounces@xxxxxxxxxxxx wrote: -----
>
>
> To: <MIDRANGE-L@xxxxxxxxxxxx>
> From: "Jim Franz" <franz400@xxxxxxxxxxxx>
> Sent by: midrange-l-bounces@xxxxxxxxxxxx
> Date: 08/18/2005 09:43AM
> 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.
>
>