RE: INZSR weirdness

Thanks for the reply...  I also believe in the top-down method of
program. 

>Since we should all be avoiding the logic
>cycle (IMO)*INZSR is a relic
>that isn't necessary.

But we are also told to modularize all your code. 

>*INZSR has a purpose only when using
>the logic cycle

I guess I am old school, I still use the cycle if I am reading the
whole file and producing a report.  Why should I have to worry about
checking for level breaks when the system came handle it.  I use the
*InzSr to do all my setups and initialize my variable.

>(which the same purpose can be 
performed without *INZSR...)
>Just perform your initial code prior to your
>main processing loop.

Granted much of the initialization can be done in the D-spec and the
setup came be done at the start of the C-spec, but "IMHO" I would
just as soon, get that one time stuff out of my face and put it a
side in it own little space.

Thanks for your thoughts.

Eurrat

---- Original Message ----
From: Tommy.Holden@xxxxxxxxxxxxxxxxx
To: rpg400-l@xxxxxxxxxxxx
Subject: RE: INZSR weirdness
Date: Tue, 29 Nov 2005 08:43:42 -0600

>Most of the things found in *INZSR....
>
>KLISTs, PLISTs, etc.  When I go to *INZSR & there's nothing there but
>those 2 items it's overkill for one.  It's a preferential thing.  I
>prefer everything to be top down.  *INZSR has a purpose only when
>using
>the logic cycle (which the same purpose can be performed without
>*INZSR...) which is to process the initial code only upon entering
>the
>program.
>
>Since we should all be avoiding the logic cycle (IMO) *INZSR is a
>relic
>that isn't necessary.  Just perform your initial code prior to your
>main
>processing loop.  Serves the same purpose & all code is in a top down
>structure.  Just makes more sense IMO...(which apparently I'm full of
>opinions these days <VBG>) 
>
>
>Thanks,
>Tommy Holden
>
>
>-----Original Message-----
>From: rpg400-l-bounces@xxxxxxxxxxxx
>[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of
>endofthetrail@xxxxxxxxxxx
>Sent: Tuesday, November 29, 2005 6:59 AM
>To: rpg400-l@xxxxxxxxxxxx
>Subject: RE: INZSR weirdness
>
>>Generally I just hate using *INZSR....
>
>Okay, I bit... WHY?
>
>Eurrat Saylor, Jr.
>Walkerton, IN.
>
>---- Original Message ----
>From: cozzi@xxxxxxxxx
>To: rpg400-l@xxxxxxxxxxxx
>Subject: RE: INZSR weirdness
>Date: Mon, 28 Nov 2005 18:27:55 -0600
>
>>
>>Actually, *INZSR came out late in RPGIII (not RPGII) along with
>>XLATE,
>>CLEAR, RESET, SUBST, CHECK and a few others.
>>
>>-Bob Cozzi
>>www.RPGxTools.com
>>RPG xTools - Enjoy programming again.
>>
>>
>>-----Original Message-----
>>From: rpg400-l-bounces@xxxxxxxxxxxx
>>[mailto:rpg400-l-bounces@xxxxxxxxxxxx]
>>On Behalf Of Holden Tommy
>>Sent: Monday, November 28, 2005 5:17 PM
>>To: RPG programming on the AS400 / iSeries
>>Subject: RE: INZSR weirdness
>>
>>If it's running in ACTGRP *NEW then yep it could be your problem.
>>Generally I just hate using *INZSR....(just one of my not so
>favorite
>>"left-overs" from the RPG II days.IMO they should scrap it...) 
>>
>>
>>Thanks,
>>Tommy Holden
>>
>>
>>-----Original Message-----
>>From: rpg400-l-bounces@xxxxxxxxxxxx
>>[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of James H H
>Lampert
>>Sent: Monday, November 28, 2005 4:55 PM
>>To: rpg400-l@xxxxxxxxxxxx
>>Subject: INZSR weirdness
>>
>>I've just converted the prototype of my SQL project so 
>>that instead of looping on The Cycle, initializing SQL at 
>>the beginning of execution, setting LR on, and shutting 
>>down SQL at the end of execution, it now loops with 
>>DOxxx-loops and RETURNs with LR off, and SQL still 
>>connected.
>>
>>It works beautifully the first time it's called in a 
>>terminal session. It crashes and burns the second time.
>>
>>So far, I've tracked down the problem to the INZSR getting 
>>called in the second and subsequent invocations, even 
>>though LR was never set (and I've verified in the ILE 
>>Debugger that it was never set).
>>
>>According to everything I've read, and everything I've 
>>ever heard about INZSRs, they're not supposed to execute 
>>if the program is being called for a second or subsequent 
>>time in a job, if LR wasn't set in the previous 
>>invocation.
>>
>>Can anybody shed any light on this puzzle?
>>
>>Could it have anything to do with the activation group the 
>>program is running in?
>>
>>--
>>JHH
>>-- 
>>This is the RPG programming on the AS400 / iSeries (RPG400-L)
>mailing
>>list
>>To post a message email: RPG400-L@xxxxxxxxxxxx
>>To subscribe, unsubscribe, or change list options,
>>visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
>>or email: RPG400-L-request@xxxxxxxxxxxx
>>Before posting, please take a moment to review the archives
>>at http://archive.midrange.com/rpg400-l.
>>
>>
>>-- 
>>This is the RPG programming on the AS400 / iSeries (RPG400-L)
>mailing
>>list
>>To post a message email: RPG400-L@xxxxxxxxxxxx
>>To subscribe, unsubscribe, or change list options,
>>visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
>>or email: RPG400-L-request@xxxxxxxxxxxx
>>Before posting, please take a moment to review the archives
>>at http://archive.midrange.com/rpg400-l.
>>
>>
>>
>>
>>-- 
>>This is the RPG programming on the AS400 / iSeries (RPG400-L)
>mailing
>>list
>>To post a message email: RPG400-L@xxxxxxxxxxxx
>>To subscribe, unsubscribe, or change list options,
>>visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
>>or email: RPG400-L-request@xxxxxxxxxxxx
>>Before posting, please take a moment to review the archives
>>at http://archive.midrange.com/rpg400-l.
>>
>
>
>
>-- 
>This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing
>list
>To post a message email: RPG400-L@xxxxxxxxxxxx
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
>or email: RPG400-L-request@xxxxxxxxxxxx
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/rpg400-l.
>
>
>-- 
>This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing
>list
>To post a message email: RPG400-L@xxxxxxxxxxxx
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
>or email: RPG400-L-request@xxxxxxxxxxxx
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/rpg400-l.
>