Has the question 1. How do I change it back? been
answered?
If the code cannot be changed as others suggested, then you most likely have
something like this:
Object Type Library Attribute
P5 *FILE #LIBRARY PRTF
P5 *DEVD QSYS PRTLAN
P5 *OUTQ QUSRSYS
....
PX *FILE #LIBRARY PRTF
PX *DEVD QSYS PRTLAN
PX *OUTQ QUSRSYS
WRKDEVD will allow a rename of a varied off native printer.
CRTDUPOBJ or RNMOBJ native commands can rename or create a new printer file
in #LIBRARY.
If the device description will vary on, and network person didn't do
something silly
Like make the device address assigned by dhcp (causing the OS to generate a
printer definition).... then you should be able to use
CHGS36 command to correct the link from S36 device to i5/OS device, back to
P5 = P5...
i5/OS S/36
Printer Printer ID
PX PX
P2 P2
P5 P5
Btw - the additional comments about moving M36 or S36 code to Power 8 - it
all depends on what you got, and what end result is desired. I've done
conversions that took no more than a couple days, while others were major
efforts, either due to excessive use of WSU or DFU programs, or the desire
for new features, convert to native db2 (and if multi format files).
RPGII batch and screen programs with proper source code, and not MRT, need
minor changes to compile and run in a S36 environment on Power 8. Most OCL
can run.
Its all in the details.
Even for S36 systems, you had to be pretty ancient to be on diskettes, most
had gone to 1/4 cartridge long ago, which I think was avail at least thru
Power 5.
Jim Franz
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 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.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
"CONFIDENTIALITY NOTICE: This e-mail transmission (and/or the attachments
accompanying it) contain confidential information belonging to the sender.
The information is intended only for the use of the intended recipient. If
you are not the intended recipient, you are hereby notified that any
disclosure, copying, distribution or the taking of any action in reliance on
the contents of the information is strictly prohibited. Any unauthorized
interception of this transmission is illegal under the law. If you have
received this transmission in error, please promptly notify the sender by
reply e-mail, and then destroy all copies of the transmission."
midrange.com
