Re: lazy, /dumb or inept programmer

Being one who used OPNQRYF a lot in days past and uses only SQL now for querying data, I can't agree that OPNQRYF is friendly. One just gets used to the oddities of having to do a very particular OVRDBF and all. You also often need a format file - none required with embedded SQL.

Perhaps the most significant factor is that IBM are not ever going to improve OPNQRYF (or RUNQRY or the QQQQRY API, as I recall) - all new query functionality will be found in regular SQL. And the new query engine is NOT used in OPNQRYF. So advances in performance will leave OPNQRYF far behind.

Is there any ROI on replacing existing usage of OPNQRYF? Probably not, certainly not if thinking of doing them all. But maybe one at a time, as time allows.

Syntax of SQL is SOOOO much easier to deal with than OPNQRYF - I once put together a mapping from certain parameters to clauses in a SELECT statement. Just to be helpful when converting, but it's been over 10 years since I even dealt with OPNQRYF.

HTH
Vern

Tom Deskevich wrote:

I am running the open source OS that is very OPNQRY friendly. :)

I know that the syntax is confusing. But you have to admit it is nice to
have an OPNQRY in the CL, then call the RPG that acknowledges all the
sorting and selection you performed. BAM!!!!

Tom Deskevich