I don't much of anything about the S/36 environment. It seems like a longshot that the timing of the power failure was just a coincidence.
-----Original Message-----
From: Jerry Adams [mailto:midrange@xxxxxxxx]
Sent: Tuesday, November 01, 2016 5:16 PM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxx>
Subject: RE: "S/36 Printer ID" changed?
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
As an Amazon Associate we earn from qualifying purchases.
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.