99 indicators was child's play! Didn't you ever come across a program
that would save indicator values in a array so it could re-use them for
other purposes and then set them back?
Trevor Briggs
Analyst/Programmer
Lincare, Inc.
(727) 431-1246
TBriggs2@xxxxxxxxxxx
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Cassidy
Sent: Tuesday, November 26, 2013 8:56 AM
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: RE: INLR no longer required?
Those were the days, yeah. But I'm glad to leave them behind. :-)
I learned RPG from a book meant for the System/3 but first practiced on
a System/34. Worked on a program once that used 99 indicators. Yuck.
Forward march!
Alan
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Mark S Waterbury
Sent: Monday, November 25, 2013 9:43 PM
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: Re: INLR no longer required?
Hi, Alan:
This got me interested ... I have an old System/3 RPG II textbook -- so
I looked up "Halt Indicators" -- here is what it says (reformatted):
It is the responsibility of the programmer to guard against all
possible mishaps that may occur in the execution of the program.
To facilitate the carrying out of this responsibility, RPG II
provides nine *halt indicators* that may be assigned as resulting
indicators.
Only at the end of the cycle of processing for a particular record
will a halt indicator cause System/3 to stop.
When System/3 does halt, it may be restarted by simply pressing the
"Start" button on the CPU. This gives the operator an opportunity
to retrieve the card in question and determine whether it was
mispunched or perhaps bears faulty data. After the problem is
solved,
the record may be replaced in the input file and processing
resumed.
Halt indicators may be set on or off using the SETON and SETOF
operations. Thus, a number of conditions may sponsor the
requirement
that a halt indicator be turned on.
Fascinating. Those were the days, eh?
Mark S. Waterbury
> On 11/25/2013 8:02 AM, Alan Cassidy wrote:
I think maybe that H1 indicator serving the purpose might have
started with what to do with running out of input cards in the
primary-file hopper, and giving you a chance to put more cards in.
Otherwise, letting it go straight to LR would not do if you had more
cards than fit in the hopper, and your program would print the grand
totals before you were ready! :-)
(Not knowing the "why" of something always bothered me..)
Alan
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Norm Dennis
Sent: Saturday, November 23, 2013 8:53 AM
To: 'RPG programming on the IBM i (AS/400 and iSeries)'
Subject: RE: INLR no longer required?
Halt indicators give options but I can't remember precisely.
(0 23) come to mind, maybe (0123), too much water under the bridge
(beer under the belt :-)
Norm Dennis
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Barbara Morris
Sent: Saturday, 23 November 2013 9:29 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: INLR no longer required?
On 11/22/2013 1:32 PM, Englander, Douglas wrote:
There is, however, an H1 (halt) indicator on a CHAIN statement that
gets
turned on if the CHAIN fails.
Learn something new every day! I had no idea that setting a halt
indicator would satisfy the compiler that the program could end.
--
Barbara
--
This is the RPG programming on the IBM i (AS/400 and 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.
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4158 / Virus Database: 3629/6852 - Release Date:
11/20/13
--
This is the RPG programming on the IBM i (AS/400 and 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.
---------------------------------------------------------------------
----------- Confidentiality Notice: This email may contain
confidential information or information covered under the Privacy
Act, 5 USC 552(a), and/or the Health Insurance Portability and
Accountability Act (PL 104-191) and its various implementing regulations
and must be protected in accordance with those provisions. It contains
information that is legally privileged, confidential or otherwise
protected from use or disclosure. This e-mail message, including any
attachments, is for the sole use of the intended recipient(s). Any
unauthorized review, use, disclosure or distribution is prohibited. You,
the recipient, are obligated to maintain it in a safe, secure and
confidential manner. If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of the
original message. Thank you.
---------------------------------------------------------------------
-----------
--
This is the RPG programming on the IBM i (AS/400 and 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.
------------------------------------------------------------------------
--------
Confidentiality Notice: This email may contain confidential information
or information covered under the Privacy Act, 5 USC 552(a), and/or the
Health Insurance Portability and Accountability Act (PL 104-191) and its
various implementing regulations and must be protected in accordance
with those provisions. It contains information that is legally
privileged, confidential or otherwise protected from use or disclosure.
This e-mail message, including any attachments, is for the sole use of
the intended recipient(s). Any unauthorized review, use, disclosure or
distribution is prohibited. You, the recipient, are obligated to
maintain it in a safe, secure and confidential manner. If you are not
the intended recipient, please contact the sender by reply e-mail and
destroy all copies of the original message. Thank you.
------------------------------------------------------------------------
--------
midrange.com
