RE: QRG4033 - help needed -- RPG400-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.

Scott,

If it were my decision, I would have migrated the code to ILE a long time ago. Some people have no interest in the 21st century.

Regards
Darryl Freinkel
A4G.
Tel: 770.321.8562 Ext 111 | Cell: 678.355.8562

-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Scott Klement
Sent: Wednesday, April 15, 2020 11:32 AM
To: rpg400-l@xxxxxxxxxxxxxxxxxx
Subject: Re: QRG4033 - help needed

This certainly SOUNDS (albeit, I haven't looked at the code) like a coding error on your part. I suspect that's why IBM is offering their services team to fix it -- because it isn't technical support's job to fix your code, their job is to fix IBM's code.

IMHO, going back to OPM makes no sense.

OPM RPG hasn't been enhanced since 1993. It was already old back then. That's TWENTY-SEVEN YEARS AGO. More than a quarter of a century! This "solution" is not reasonable. You've already run into a technical reason why this is not so easy. But, think about the future... You are stuck in 1980's technology, with no future.

This is not a reasonable business decision. Whomever is making it is stuck in the past, or doesn't really understand the situation.

If you truly can't fix the coding error with OPNQRYF (which is also a legacy 1980's technology that you should be moving away from) then rewrite it to use SQL or some other, newer, better technology. Don't go backwards. And certainly not THAT far backwards.

-SK

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.