Re: RRN of an IP record -- MIDRANGE-L

It is my experience that if it has run 30 years and then failed, the pointer to the problem lies in the data.

I'd take a look at the raw data file and see if that provides one of those golden "*DUH!*" moments.

STRPDM, take a 12 on the the file itself (not on the source!), and then a 5 on the member in the file.
Then again, maybe that won't help. :)

Marchini, Richard wrote:

I've encountered a problem that I've never seen in 30+ years of RPG
development. This morning we had a program issue an error which gave
response options of (C G D F). The input file is an Input Primary file,
and contains 19 records. When we checked the Display Open Files screen
of the job, and it showed the file at RRN 19, but with an I/O count of
one. We determined it would not be harmful to skip the record that was
causing the error, so we answered the error message with a 'G'. Much to
our surprise, the program did not end (we assumed it had read the last
record in the file), but returned with the same error. Further
examination revealed that the program was re-processing the same input
record, which happened to be the 2nd. record in the file, not the 19th.

I surmised that the program had read all 19 records into the input
buffer(s), and when the cycle returned to GETIN, because it didn't have
to do another disk access, it didn't advance to the next record.
My question is, in the case of an Input Primary file, how can I
determine which record is actually being processed, short of dumping the
program? By the way, the program is vendor-written, and we cannot
rewrite it to not use the cycle.

I know this is really old stuff, but I will appreciate any information I
can get.

Thank you,

Rick Marchini
Associated Banc-Corp
IT Services
Mail Stop 7055
920-405-2587

*********************** NOTICE***********************

This e-mail and attachment(s) may contain information that is
privileged, confidential, and/or exempt from disclosure under
applicable law. If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination,
distribution, or copy of this message is strictly prohibited. If
received in error, please notify the sender immediately and
delete/destroy the message and any copies thereof. Although
Associated Banc-Corp and/or its affiliates (collectively
"Associated") attempt to prevent the passage of viruses via e-mail
and attachments thereto, Associated does not guarantee that either
are virus-free, and accepts no liability for any damage sustained
as a result of any such viruses.

Any federal tax advice contained in this communication (including
any attachments) is not intended or written to be used or referred
to in the promoting, marketing, or recommending of any entity,
investment plan or agreement, nor is such advice intended or written
to be used, and cannot be used, by a taxpayer for the purpose of
avoiding penalties under the Internal Revenue Tax Code
------------------------------------------------------------------------

No virus found in this incoming message.
Checked by AVG - http://www.avg.com Version: 8.0.176 / Virus Database: 270.9.14/1832 - Release Date: 12/5/2008 9:57 AM