Re: Development Standards

On Dec 12, 2016, at 12:50 PM, Rob Berendt <rob@xxxxxxxxx> wrote:

I did a read loop, with minimal other work.
As a cycle program it ran much faster than switching it to a SETLL/READ
loop.
Much faster.

I could play with the SETLL/READ type program, and after much dinking
around with blocking I could start to approach the efficiency of the cycle
program.

Simply compile a cycle program with a primary file and read the
informational messages for more details.

...
Busy day and I'm on hold with IBM on a sev 1 issue.
Had to drop the other sev 1 issue down to a sev 2 just to give the first
one my full effort.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Jon Paris <jon.paris@xxxxxxxxxxxxxx>
To: Midrange-L Midrange-l <midrange-l@xxxxxxxxxxxx>
Date: 12/12/2016 12:41 PM
Subject: Re: Development Standards
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



I don't understand this at all Rob. I can't think of a single thing the
cycle does that I cannot match in a non-cycle program. There no "special
sauce" there that I am aware of.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Dec 12, 2016, at 8:59 AM, Rob Berendt <rob@xxxxxxxxx> wrote:

While I've not done a cycle program in a long time I will agree they are

terrifically efficient. The blocking inherent in them is awesome. I

had

to do a bunch of manual adjustment of blocking to come even close to

what

a cycle program could do. I posted some time trials a long time ago to
this list


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: "Joni V." <joni_vanderheijden@xxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 12/11/2016 07:25 AM
Subject: Re: Development Standards
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



As a young one, the problem I have with cycle programs is not that I

don't

understand them or can't use them.

- They lead to monolithic programs

- Are harder to read

- More difficult to maintain

- Blocks the use of newer features

- The style of a cycle program is significantly different from linear
programs.


So taking the arguments above into account, our more experienced / older

technical experts agreed to disallow them in our coding standards.

I have seen one new cycle program in the last four years, it was a
one-shot program for a migration of the database where almost all

records

from a file had to be updated. I have to admit it was very performant.

Joni
________________________________
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx> on behalf of Jeff
Crosby <jlcrosby@xxxxxxxxxxxxxxxx>
Sent: Sunday, December 11, 2016 12:46
To: Midrange Systems Technical Discussion
Subject: Re: Development Standards

On Sat, Dec 10, 2016 at 10:20 AM, Raul A Jager W <raul@xxxxxxxxxx>

wrote:

If we, old ones, where able to learn it, the young should be able to.

It

is a tool specially designed to generate reports, probably the best in

the

industry, why not use it? The fact that other languages don't have it,

is

a dis advantage that we do not need to copy.

Agree 100%. Take the "don't use the cycle" to it's logical conclusion

and

you're saying "Don't use feature X because it's not available in every
language out there."

And no, the cycle is not the answer to every programming issue.



--


Jeff Crosby
VP Information Systems
UniPro FoodService/Dilgard
P.O. Box 13369
Ft. Wayne, IN 46868-3369
260-422-7531
www.dilgardfoods.com<http://www.dilgardfoods.com>

The opinions expressed are my own and not necessarily the opinion of my
company. Unless I say so.
--
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.

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: 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.

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: 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.

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: 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.

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: 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.

Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD