SQL is a language unto itself requiring a separate set of skills that
combined with most any programming language today that use a relational
database means you can manipulate data as needed. I see SQL as a core skill
in todays' world, with the potential exception of the larger noSQL
databases.
As to the earlier comment that we should not use any feature in a language
that's not available in all other languages, that's taking the concept to
absurdity. They cycle has not been taught or commonly used in new
development in some time, aside from the quick utility programs that we all
occasionally write. Do you intentionally use program described files and
output specs in new development, ignoring the fact that SQL and other
programs could not access the data easily? No because we have moved past
those days. The cycle is in the same category.
Use the cycle if you wish, it's efficient and reasonably easy for simple
read, process, write programs. Then plan on never retiring, since you'll be
the only one to be able to maintain it.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan
Shore
Sent: Wednesday, June 13, 2018 7:52 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: RE: [EXTERNAL] RE: the cycle that never ends
Hi Jim
Even though Im not a fan of the cycle, I don't agree with this comment I was
a mainframe COBOL programmer when I was given a couple of manuals for the
AS/400 and told - here, learn this I was doing okay until I came across a
program that had no reads of a file Sent me up the wall - until days later -
I finally saw the p in the f-spec THAT was my introduction of the cycle
Traumatized me so much I even have flashbacks Oh the terror
Anyway, I use embedded SQL and I know there are quite a number of my fellow
compadres have a problem with SQL - period Because of that, should I never
use embedded SQL?
Alan Shore
E-mail : ASHORE@xxxxxxxx
Phone [O] : (631) 200-5019
Phone [C] : (631) 880-8640
'If you're going through hell, keep going.'
Winston Churchill
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim
Oberholtzer
Sent: Wednesday, June 13, 2018 8:37 AM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxx>
Subject: [EXTERNAL] RE: the cycle that never ends
Since no other language has the cycle (that I'm aware of) in today's world
where you might not be the one to maintain the program, more currently
traditional styles of managing I/O is vastly preferred. Regardless of your
adoration for the cycle, it's no longer commonly used. Sure it's easy in
the right circumstance, however 99.5% of the students coming out of school
have never seen a cycle program. That makes it your problem, not theirs, to
make sure they can maintain what you built.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James
H. H. Lampert
Sent: Tuesday, June 12, 2018 1:19 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: the cycle that never ends
On 6/12/18, 10:42 AM, dmmueller@xxxxxxx wrote:
and should I be embarrassed to say, we still have some of those cycle
programs still running.... and with each upgrade, they still work :)
Nothing to be embarrassed about.
What should be embarrassing is when people AVOID using The Cycle in
situations where it is the correct tool for the job . . . and end up
"walking" through a file when they can "ride" through it (or writing their
own "do until the user exits" loop when, simply by tying LR to whatever the
user does to exit, e.g., tying it to INKC, they can use a built-in
event-loop).
--
JHHL
--
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:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
http://amzn.to/2dEadiD
--
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:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
http://amzn.to/2dEadiD
--
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:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
http://amzn.to/2dEadiD
As an Amazon Associate we earn from qualifying purchases.