RE: "S/36 Printer ID" changed?

The CHGS36 was all it took, thanks.

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

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