That was 1983 at the Fall COMMON Conference in Phoenix.
To your question about "how" the change occurred: I'm still ruminating.
Offhandedly I'd have to guess that something changed on either the system or
the device. Mere power outages, no matter how severe, would not account for
it.
As to Rob's issue with RPG36 (i.e., II), I agree. At least as regards "new"
programs. I would not rewrite an RPG II program for a simple few lines fix;
that would be silly. New stuff, of course, should always be in ILE RPG
(unless, of course, Cobol is your bag). I've followed some @#$%
consultant(s) around TN who told their clients that "Well, since you're
sunning 36E, (a) we can't rationalize the DB and (b) everything has to be in
RPG II."
Jerry C. Adams
We can't be too careful in the choice of our enemies. -Oscar Wilde
IBM i Programmer/Analyst
--
NMM&D
615-832-2730
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Justin Taylor
Sent: Tuesday, November 01, 2016 12:28 PM
To: Midrange Systems Technical Discussion
Subject: RE: "S/36 Printer ID" changed?
It specifies:
// PRINTER NAME-x,DEVICE-P5,PRIORITY-0,LINES-42,FORMSNO-y
I have no idea what it "should" say. I'm not sure I was even born yet when
S/36 was released.
-----Original Message-----
From: broehmer@xxxxxxxxxxxxxxx [mailto:broehmer@xxxxxxxxxxxxxxx]
Sent: Tuesday, November 01, 2016 12:17 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: "S/36 Printer ID" changed?
Justin,
Now I'm curious. What kind of error are you getting? Is this because of
some OCL hard
coded printer file(s)? (// printer name-output,device-P5) Something
like that?
Because if that's the case shouldn't those be coded to point to outq's not
devices?
--
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.
As an Amazon Associate we earn from qualifying purchases.