|
Whether or not you are going mad is a whole different subject. :)
In the meantime the chain without the 'K' on the F-spec is using the RCCus
as a Relative Record Number (RRN) which in your case is probably not
getting a hit.
Lucky nothing was updated and/or good testing. I seen this problem put a
hurt on some programmers before.
Patrick Conner
www.ConnecTown.com
(828) 244-0822
jjooste@omnia.co.
za To: RPG400-L@midrange.com
Sent by: cc:
owner-rpg400-l@mi Subject: Inconsistency ?
drange.com
10/25/00 10:00 AM
Please respond to
RPG400-L
Please can anybody give me advise on the weird situation.
FRARXX02 IP E DISK
FRCML01 UF E DISK
C***
C RCCUS CHAIN(E) RCML01
C IF %FOUND AND NOT %ERROR
C ADD RAMT CAMTD
C UPDATE(E) IPR100CM
C ENDIF
C***
Reading a file, chaining to another file without a K specified, and
updating it.
When compiling the pgm, not even a severity 10 error. Debugging it, it
shows the
data moving into the correct field, interrupting it, it also shows the file
and
record being accessed and updated.
Problem: After running the pgm, not one record were updated ?
Changing the 2nd line to this: FRCML01 UF E K DISK, with
the K
in place, it worked.
Am I going mad or what ?
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.