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

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

My condolences.

From: Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 11/01/2016 02:35 PM
Subject: RE: "S/36 Printer ID" changed?
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>

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

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.