Well, first off... I'm embarrassed to realize I didn't even catch the subject of Joe's original email. Duh, he said *INZSR <head slap>.

Secondly... I know you're a fan but... Heck no!

I will tell you that when I learned RPG over 30 years ago, my instructor went over the cycle, had us write a program or two using it, and then said "you need to know about it as it is part of the language" but he would never accept a cycle program in production in his shop - where six of us from the class later got hired.

Programs doing magic stuff without me telling it to give me the willies.

Roger Harman
COMMON Certified Application Developer - ILE RPG on IBM i on Power



From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> on behalf of James H. H. Lampert <jamesl@xxxxxxxxxxxxxxxxx>
Sent: Wednesday, March 27, 2019 1:51 PM
To: RPG programming on IBM i
Subject: Re: Equivalent of *INZSR for service programs
On 3/27/19, 1:44 PM, Roger Harman wrote:
The idea of an auto-invoke makes me think of *INZSR which I detest.
"Magic" routines running on their own?  No thanks.

Just a wild guess, but I would imagine you don't "ride The Cycle" very much.


This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 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].