RE: "S/36 Printer ID" changed? -- MIDRANGE-L

Subject: RE: "S/36 Printer ID" changed?
From: Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
Date: Tue, 1 Nov 2016 19:35:14 +0000
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

The code's untouchable.

-----Original Message-----
From: broehmer@xxxxxxxxxxxxxxx [mailto:broehmer@xxxxxxxxxxxxxxx]
Sent: Tuesday, November 01, 2016 1:05 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: RE: "S/36 Printer ID" changed?

Oh wow. Those definitely should be changed to outq. It's fairly simple.
CLP overrides take care of that.

In your example both of the following lines would exist:

// PRINTER NAME-x,PRIORITY-0,LINES-42,FORMSNO-y
OVRPRTF FILE(X) OUTQ(P5)

This will simply change the output to outq P5. by removing the offending
device-p5 and a new line assigning the printer file X to outq P5.
We still have production code like this for about 10 OCL driven programs that nobody wants to change.

Bill

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: "S/36 Printer ID" changed? , broehmer

This mailing list archive is Copyright 1997-2025 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.